Re: [cobalt-users] Raq4 - Kernel 2.4 Upgrade Woes

["Josh Trutwin" <josh@xxxxxxxxxxxxxxxxxxx>]

> JT> S$%t.  I'm using 2.3.40.
>
> Uh, someone correct me if I'm wrong... but I thought the RaQ4
> _had_ to run 2.3.x, and would be in deep desoldering doodoo if
> one loaded non-2.3.x ROM.  I'd better go back and check.

Yup, the 2.9 I think was labeled "beta" so I went with 2.3.40.  The
explitive was because the instructions didn't work for 2.3.40, not because
I had the wrong BIOS....

> JT> Apr  9 20:53:00 skinner dhcpd-2.2.x: BOOTREQUEST from
> 00:10:e0:02:59:13 JT> via eth0
> JT> Apr  9 20:53:00 skinner dhcpd-2.2.x: BOOTREPLY on 192.168.0.200 to
> JT> 00:10:e0:02:59:13 via eth0
>
> How is this a problem?

Because I don't know enough to know it's not a problem!  I'm reading more
on DHCP as we speak....

> JT> And here is the output from the Raq:
> JT>
> JT> <snip>
> JT> Partition check:
> JT>  hdc: [PTBL] [1027/255/63] hdc1 hdc2 hdc3 hdc4 < hdc5 hdc6 hdc7 hdc8
>> JT> autodetecting RAID arrays
> JT> autorun ...
> JT> ... autorun DONE.
> JT> Looking up port of RPC 100003/2 on 192.168.0.1
> JT> request_module[bandwidth_mgr]: Root fs not mounted
> JT> portmap: RPC call returned error 111
> JT> RPC: task of released request still queued!
> JT> RPC: (task is on xprt_pending)
> JT> Root-NFS: Unable to get nfsd port number from server, using default
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
I suspect this is what I should be looking into.

> JT> Looking up port of RPC 100005/1 on 192.168.0.1
> JT> portmap: RPC call returned error 111
> JT> RPC: task of released request still queued!
> JT> RPC: (task is on xprt_pending)
> JT> Root-NFS: Unable to get mountd port number from server, using
> default JT> mount: RPC call returned error 111
> JT> RPC: task of released request still queued!
> JT> RPC: (task is on xprt_pending)
> JT> Root-NFS: Server returned error -111 while mounting /nfsroot-x86 JT>
> VFS: Unable to mount root fs via NFS, trying floppy.
> JT> request_module[block-major-2]: Root fs not mounted
> JT> VFS: Cannot open root device 02:00
> JT> Kernel panic: VFS: Unable to mount root fs on 02:00
> JT> disabling network interfaces.
> JT> Rebooting in 5 seconds..
> JT> </snip>
> JT>
> JT> Looks like it's close, any thoughts?  I'll start reading
> JT> dhcpd man pages...
>
> Hmmmm.  Trying to mount root via NFS, then via floppy.  Lemme
> read your previous post... I still suspect it's unhappy with the
> CHS translations, but could be wrong.

Any thoughts on why it's failing the NFS boot?  I am able to mount the
/nfsroot-86 drive on another box using mount 192.168.0.4:/nfsroot-86
/somedir.  Anything I can provide regarding the CHS translations?

Thanks,

Josh