[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Booting debian on mipsel custom kernel 2.4.0



I am trying to boot woody/main/disks-mipsel/3.0.14-2001-09-30's
root.tar.gz using a custom kernel built for the Galileo Gt-64240 system
controller and a QED-RM5261A cpu.

I have successfully run RedHat-based distros on this board with this
kernel.

I always end up with:

------------------------------------------------------------------------------
IP-Config: Got RARP answer from 192.168.100.182, my address is
192.168.100.43
IP-Config: Guessing netmask 255.255.255.0
IP-Config: Downing eth1
gtIntDisable(CAUSE 1.): Mask@0xb4000c6c, old=0x00000003, new=0x00000001
request_irq: irq=1, flags=0x00000000, devname=<NULL> at 0x81148000
gtIntDisable(CAUSE 1.): Mask@0xb4000c6c, old=0x00000001, new=0x00000001
free_irq: irq=1, action =8111a2e0, devname=<NULL> at 0x81148000
IP-Config: device=eth0, local=2b64a8c0, server=b664a8c0, boot=b664a8c0,
gw=fffff
fff, mask=00ffffff
IP-Config: host=192.168.100.43, domain=(none), path=`'
kmem_create: Forcing size word alignment - nfs_fh
Root-NFS: Mounting /tftpboot/debian-el on server 192.168.100.182 as root
Root-NFS:     rsize = 4096, wsize = 4096, timeo = 7, retrans = 3
Root-NFS:     acreg (min,max) = (3,60), acdir (min,max) = (30,60)
Root-NFS:     nfsd port = -1, mountd port = 0, flags = 00000200
Looking up port of RPC 100003/2 on 192.168.100.182
Root-NFS: Portmapper on server returned 2049 as nfsd port
Looking up port of RPC 100005/2 on 192.168.100.182
Root-NFS: mountd port is 901
NFS:      nfs_mount(c0a864b6:/tftpboot/debian-el)
VFS: Mounted root (nfs filesystem) readonly.
FreeImem
Freeing prom memory: 0kk freed
Freeing unused kernel memory: 176k freed
OpenCons
ExecInit
ExecIni1
serial console detected.  Disabling virtual terminals.
init started:  BusyBox v0.60.1 (2001.09.24-21:03+0000) multi-call binary
E: /proc does not appear to be mounted (No such file or directory)
E: /proc does not appear to be mounted (No such file or directory)
E: /proc does not appear to be mounted (No such file or directory)

            <<< infinitely repeating .... >>>

E: /proc does not appear to be mounted (No such file or directory)
E: /proc does not appear to be mounted (No such file or directory)
-------------------------------------------------------------------------------- 
 
I have tried various changes to fstab such as:

     none   /proc   proc   defaults   0 0
and
     proc   /proc   proc    defaults  0 0
.

I do not have an initrd set up, but what I've read in the mail archives
leads me to believe that that is not necessary.  I also have not enabled
kernel modules in my kernel build. 

I'm not very familiar with busybox.  Is that where I should
concentrate?  Are there debug message switches for it?

Or, is a 2.4.0-based kernel more likely to be the problem?

--
 /"\ . . . . . . . . . . . . . . . /"\
 \ /   ASCII Ribbon Campaign       \ /     Paul R. Kasper
  X    - NO HTML/RTF in e-mail      X      Patton Electronics Co.
 / \   - NO MSWord docs in e-mail  / \     301-975-1000 x173



Reply to: