Hello all

I'm trying to build from 0.6. The only change I am making to the
config is to change the target device to net5501. The build completes.
I then drag the built files into the OS directory of an existing
Astlinux (net5501) CF card's Runnix partition (clearing the 0.6.7
files out of the way) but when I try to boot the Soekris, all seems
well until we get as far as this:

Looking for AstLinux image...
AstLinux image found!
Configuring for unionfs...
Checking asturw filesystem
ext2fs_check_if_mount: No such file or directory while determining
whether /dev/hda2 is mounted.

Fsck detected and repaired errors on /dev/hda2
Copying AstLinux files to RAM...
unmounting squashfs image
unmounting /cdrom
Pivoting...

init started: Bunionfs: new lower inode mtime (bindex=1, name=console)
usyBox v1.8.2 (2009-08-17 10:24:46 BST)
unionfs: new lower inode mtime (bindex=1, name=etc)
FATAL: Could not open 'kernel/drivers/char/cs5535_gpio.ko': No such
file or directory
BusyBox v1.8.2 (2009-08-17 10:24:46 BST) multi-call binary

Usage: mknod [OPTIONS] NAME TYPE MAJOR MINOR

Create a special file (block, character, or pipe)

Options:
        -m      Create the special file using the specified mode (default a=rw)

TYPEs include:
        b:      Make a block (buffered) device
        c or u: Make a character (un-buffered) device
        p:      Make a named pipe. MAJOR and MINOR are ignored for named pipes

unionfs: new lower inode mtime (bindex=1, name=etc)
Runnix vfat partition re-mounted read-only
going to runlevel default...
No Zap hardware - loading ztdummy
WARNING: Could not open 'kernel/drivers/net/slhc.ko': No such file or directory
WARNING: Could not open 'kernel/drivers/net/ppp_generic.ko': No such
file or directory
WARNING: Could not open 'kernel/drivers/net/wan/hdlc.ko': No such file
or directory
WARNING: Could not open 'misc/zaptel.ko': No such file or directory
WARNING: Could not open 'kernel/drivers/char/rtc.ko': No such file or directory
FATAL: Could not open 'misc/ztdummy.ko': No such file or directory
WiFi not enabled
udhcpc: SIOCGIFINDEX: No such device
Configuring sensors...
WARNING: Could not open 'kernel/drivers/i2c/i2c-core.ko': No such file
or directory
WARNING: Could not open 'kernel/drivers/i2c/busses/i2c-isa.ko': No
such file or directory
WARNING: Could not open 'kernel/drivers/hwmon/hwmon.ko': No such file
or directory
WARNING: Could not open 'kernel/drivers/hwmon/hwmon-vid.ko': No such
file or directory
FATAL: Could not open 'kernel/drivers/hwmon/pc87360.ko': No such file
or directory
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
Starting syslogd...
Starting crond...
WiFi not enabled
Starting ntpd...
Starting sshd...
Starting inetd...
Starting Asterisk...
Starting mISDN
misdn-init.conf already exists on /mnt/kd, skipping config.
WARNING: Could not open 'kernel/drivers/isdn/capi/kernelcapi.ko': No
such file or directory
WARNING: Could not open 'kernel/drivers/isdn/capi/capifs.ko': No such
file or directory
FATAL: Could not open 'kernel/drivers/isdn/capi/capi.ko': No such file
or directory
FATAL: Could not open 'extra/mISDN_core.ko': No such file or directory
WARNING: Could not open 'extra/mISDN_core.ko': No such file or directory
FATAL: Could not open 'extra/mISDN_l1.ko': No such file or directory
WARNING: Could not open 'extra/mISDN_core.ko': No such file or directory
FATAL: Could not open 'extra/mISDN_l2.ko': No such file or directory
WARNING: Could not open 'extra/mISDN_core.ko': No such file or directory
FATAL: Could not open 'extra/l3udss1.ko': No such file or directory
WARNING: Could not open 'extra/mISDN_core.ko': No such file or directory
WARNING: Could not open 'kernel/drivers/isdn/capi/kernelcapi.ko': No
such file or directory
FATAL: Could not open 'extra/mISDN_capi.ko': No such file or directory
-----------------------------------------
 Loading module(s) for your misdn-cards:
-----------------------------------------
/sbin/modprobe --ignore-install hfcmulti type=0x1 protocol=0x2
layermask=0xf poll=128 debug=0
WARNING: Could not open 'extra/mISDN_core.ko': No such file or directory
FATAL: Could not open 'extra/hfcmulti.ko': No such file or directory
/sbin/modprobe mISDN_dsp debug=0x0 options=0 poll=128 dtmfthreshold=100
WARNING: Could not open 'extra/mISDN_core.ko': No such file or directory
FATAL: Could not open 'extra/mISDN_dsp.ko': No such file or directory
[i] creating device node: /dev/mISDN

WARNING WARNING WARNING

YOU STILL HAVE NOT CHANGED YOUR ASTERISK MANAGER PASSWORD
ANYONE THAT KNOWS YOU ARE USING ASTLINUX CAN DESTROY YOUR
SYSTEM. PLEASE CHANGE THIS IN /etc/asterisk/manager.conf
IMMEDIATELY!

WARNING WARNING WARNING

FATAL: Could not open 'kernel/fs/binfmt_misc.ko': No such file or directory
mount: mounting none on /proc/sys/fs/binfmt_misc failed: No such device
/etc/runlevels/default/S80mini_httpd: line 20:
/proc/sys/fs/binfmt_misc/register: No such file or directory
Starting mini_httpd...
Starting mini_httpd (HTTP only)...
cat: can't open '/tmp/mydhcpip': No such file or directory


This is backuppbx (Linux i586 2.6.20.21-astlinux) 15:56:11

backuppbx login: root
Password:
backuppbx ~ # lsmod
Module                  Size  Used by
backuppbx ~ #

Can anyone help? Has there been development in the 0.6 branch since
0.6.7? If so, is it possible to check out specifically 0.6.7, rather
than just the 0.6 branch?

Thanks

Tom

PS  Also tried building from trunk, but, despite my having installed
git, make immediately fails with "Host tool missing: git".

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Astlinux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to 
[email protected].

Reply via email to