Re: !!!checksum problem of network boot image for linux!!!

Hi Jan,

thanks for your proposal. But it doesn't work. I tried to build  
several etherbootkernel by the following issues of wraplinux commands:
1)
wraplinux --params "root=/dev/nfs  
nfsroot=192.9.200.137:/svr1/rootfilesystem/pilas5  
ip=192.9.200.155:192.9.200.137:192.9.200.129:255.255.255.192:pilas5:eth0:off"  
--initrd initrd-2.6.31 --output vmlinuz.etherboot.pilas5_103 --elf  
vmlinuz-2.6.31

2)
wraplinux --params "root=/dev/nfs  
nfsroot=192.9.200.137:/svr1/rootfilesystem/pilas5 ip=::::::dhcp"  
--initrd initrd-2.6.31 --output vmlinuz.etherboot.pilas5_103 --elf  
vmlinuz-2.6.31

3)
wraplinux --params root=/dev/nfs --params  
nfsroot=192.9.200.137:/svr1/rootfilesystem/pilas5 --params  
ip=192.9.200.155:192.9.200.137:192.9.200.129:255.255.255.192:pilas5:eth0:off  
--initrd initrd-2.6.31 --output vmlinuz.etherboot.pilas5_103 --elf  
vmlinuz-2.6.31

4)
wraplinux -E -p "root=/dev/nfs  
nfsroot=192.9.200.137:/svr1/rootfilesystem/pilas5,tcp,vers=3 ip=dhcp"  
-i initrd-2.6.31 -o vmlinuz.etherboot.pilas5_103 vmlinuz-2.6.31

It seems that the problem is that kernel lose the network information  
after loading and starting the kernel or that the information in  
kernel parameter "ip=dhcp" has no effect. The kernel is not able to  
mount the rootfilesystem in case of missing network information (no  
IP, no netmask, no gateway, just nothing). So the questions are: Why  
does the kernel not hand over the network information from  
etherboot/BIOS? Or why does the kernel make no new DHCP request resp.  
why does the kernel parameter "ip=dhcp" or  
"ip=192.9.200.155:192.9.200.137:192.9.200.129:255.255.255.192:pilas5:eth0:off"  
have no effect?

With the kernel 2.4.32 and mkelf-linux it was so easy.

Thanks.
Best regards,
Torsten B.


Zitat von Jan <[email protected]>:

> Hello Torsten,
>
> if you are having trouble with wraplinux and need to provide kernel
> parameters, here is the command that works for my setup:
>
> # wraplinux -E -p "root=/dev/nfs nfsroot=/localnfs,tcp,vers=3 ip=dhcp"
>
> On Fri, 30 Oct 2009 14:23:03 +0100
> Thomas Miletich <[email protected]> wrote:
>> As far as I know the linux kernel has a option called 'ip'. You can
>> set it to something like 'ip=dhcp'.
>
>> On Fri, Oct 30, 2009 at 11:15 AM,  <[email protected]> wrote:
>> > thanks for your answer. You are right, after using "wraplinux" the
>> > etherbootkernel will be load. But now I running into the next problem.
>> > "wraplinux" doesn't provide the option "--ip" or a similar option.
>
> You use "-p <kernel parameters>" to add anything wraplinux needs to
> provide for the kernel, which in my case is:
> "root=/dev/nfs nfsroot=<path>,<NFS-parameters> ip=dhcp"
>
> The wraplinux parameters shown above work with a fairly old etherboot
> ROM I never bothered to update, hence the "-E".
>
> Hope this helps,
> Jan
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Etherboot-discuss mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/etherboot-discuss
>
>




------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference