|
From: vlok s. <iv...@ve...> - 2004-06-14 19:43:37
|
Hi and Thank You, Still can't boot. Error msg = kernel panic no init
found. try passing init= to kernel. it does mount nfs. so that's good.
I think I need to know how to build the root fs and where it goes.
What does your root fs look like. Or how I pass init= to the kernel (
and which kernel do I pass it to? kernel.1000?)
thanks again in advance. I got the kernel and config file from coruna.
just having trouble w/ initial console.
Vlok
Hi again,
I am not sure what is going wrong with your setup.
Enclosed you will find the bits, which work for me.
###########
The relevant bits during startup look like this:
Linux version 2.4.21 (root@debian) (gcc version 2.95.4 20011002 (Debian
prerelease)) #2 Tue Aug 5 23:25:22 CEST 2003
...
Kernel command line: console=ttyS0,9600 console=tty0 root=/dev/nfs
nfsroot=/home/NetworkStation ip=dhcp
...
Sending DHCP requests ., OK
IP-Config: Got DHCP answer from 10.0.1.100, my address is 10.0.1.50
IP-Config: Complete:
device=eth0, addr=10.0.1.50, mask=255.255.255.0, gw=10.0.1.1,
host=10.0.1.50, domain=buxhoeveden.net, nis-domain=(none),
bootserver=10.0.1.100, rootserver=10.0.1.100, rootpath=
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Looking up port of RPC 100003/2 on 10.0.1.100
Looking up port of RPC 100005/1 on 10.0.1.100
VFS: Mounted root (nfs filesystem).
Freeing unused kernel memory: 136k init 36k pmac 8k chrp 4k openfirmware
############
#/etc/exports on the computer that acts as dhcp and nfs server:
/netstation/prodbase 10.0.1.50(rw) #that is where my kernel.1000 lives
/home/NeworkStation 10.0.1.50(rw,no_root_squash) # that is root i.e. "/"
for the Netstation
/home/geltmar 10.0.1.50(rw) #my home directory on the server
#############
#/etc/hosts.allow on dhcp/nfs server
ALL: 10.0.1.*
#############
#/etc/dhcp3/dhcpd.conf on dhcp/nfs server
option domain-name "buxhoeveden.net";
option name-name-servers 145.253.2.11;
default-lease-time 600;
max-lease-time 7200;
host netstation {
hardware ethernet 0:0:a7:24:17:4b;
fixed-address 10.0.1.50;
filename "kernel.1000";
server-name "10.0.1.100";
}
the filename "kernel.1000" is
probably not necessary, if you configure the NVRAM in the netstation itself
???
to boot a kernel from a specified location,
but the kernel is configured to use dhcp for an IP, so I guess it is needed
in the
second phase of booting to get the nfs stuff running.
#############
My kernel is 2.2.21 self compiled, as I had to change the
nfsroot=/home/Networkstation bit
for the kernel command line. Other changes are, that I compiled drivers for
the
parallel port as modules to keep the kernel small, as I don"t use a printer.
Have a look in /var/log/syslog et al on your dhcp server and try to find outJun 14 15:55:53 localhost rpc.mountd: authenticated mount request from 192.168.1.102:608 for /netstation/Prodbase (/netstation)
mounting nfs works. I used to get "permission denied for..." errors by the
nfs server,
nfs gets mounted , but the weird thing is this
how farJun 14 15:55:08 localhost rpc.mountd: authenticated mount request from 192.168.1.102:1023 for /netstation/Prodbase (/netstation)
Jun 14 15:55:09 localhost rpc.mountd: authenticated unmount request from 192.168.1.102:1023 for /netstation/Prodbase (/netstation)
Jun 14 15:55:20 localhost rpc.mountd: authenticated mount request from 192.168.1.102:604 for /NetworkStationV2/prodbase/linuxppc (/NetworkStationV2/prodbase/linuxppc)
Jun 14 15:55:21 localhost rpc.mountd: authenticated mount request from 192.168.1.102:608 for /netstation/Prodbase (/netstation)
Jun 14 15:55:41 localhost rpc.mountd: authenticated mount request from 192.168.1.102:1023 for /netstation/Prodbase (/netstation)
Jun 14 15:55:41 localhost rpc.mountd: authenticated unmount request from 192.168.1.102:1023 for /netstation/Prodbase (/netstation)
Jun 14 15:55:53 localhost rpc.mountd: authenticated mount request from 192.168.1.102:604 for /NetworkStationV2/prodbase/linuxppc (/NetworkStationV2/prodbase/linuxppc)
does it have to mount on 1023? Which it does w/ the regular kernel.63a
if the IP address of the Networkstation and the lines in /etc/exports did
not match.
Did you have a working 2.4.19 kernel, as another user reported and it
stopped
working once you switched to 2.4.21? Or did the station not boot at all?
the regular kernel.63a boot fine. but I want to get the sound going :-)
No I never tried the 2.4.19.
Maybe having the kernel "ouside" nfsroot as in my configuration is
necessary, I am not sure?
I had to move nfsroot to a disk partition with more space so I ended up with
this configuration.
Maybe you can find any differences to your configuration.
Good luck
Geltmar
|