Re: Problem booting Linux

[Crispin Murphy <crispin@myra.com>]

You have build a non-modular kernel (as modules can only be loaded off 
of the filesystem) with the network card drivers, bootp IP 
autoconfiguration enabled, and the 'root filesystem on NFS' kernel 
parameters.

You can actually test this kernel and bypass the whole netboot scenario 
by doing a 'dd if=/usr/src/linux/arch/i386/boot/bzImage of=/dev/fd0' and 
have a network bootable kernel on a floppy disk - then it grabs the 'rp' 
tag (root path) out of the dhcp/bootp response and mounts that from the 
network.  Note that you need to fiddle the mounted /etc/fstab to point 
to the right place as well otherwise strange things might happen...

Its really good to use tcpdump to watch the packets to see exactly what 
is failing (or in my case, where my nfs server was solaris, 'snoop')

Crispin

Irving I. Lopez C. wrote:

>>I didn't have any problems with just using the raw compiled kernel - no
>>mknbi-linux required (but this was a while ago, and I haven't played
>>around with netbooting a 2.4 kernel)
>>
>>Crispin
>>
>
>
>How ?  
>what parameter i must send to kernel to boot over network (NFS, DHCP...) 
>===========================================================================
>This Mail was sent to netboot mailing list by:
>"Irving I. Lopez C." <ilopez@unisistems.com.pa>
>To get help about this list, send a mail with 'help' as the only string in
>it's body to majordomo@baghira.han.de. If you have problems with this list,
>send a mail to netboot-owner@baghira.han.de.
>


-- 
Complexity Happens



===========================================================================
This Mail was sent to netboot mailing list by:
Crispin Murphy <crispin@myra.com>
To get help about this list, send a mail with 'help' as the only string in
it's body to majordomo@baghira.han.de. If you have problems with this list,
send a mail to netboot-owner@baghira.han.de.