Re: Mounting Root on NFS problem (kernel 2.4.18)

[Mohd-Hanafiah Abdullah <napi@cs.indiana.edu>]

In message <Xns924BA47E3385gerogkminixhande@192.168.99.100>you write:
 >
 >Hello,
 >
 >napi@cs.indiana.edu (Mohd-Hanafiah Abdullah) wrote in
 >200207130328.g6D3SJi03076@tcserver.school1.edu.my:">news:200207130328.g6D3SJi03076@tcserver.school1.edu.my: 
 >> But, when upgrading to kernel 2.4.18 and configuring the kernel for
 >> diskless booting the same way as before, a problem appeared while
 >> booting complaining that it couldn't mount root on NFS since no NFS
 >> server was available, and it gave up immediately asking to insert a
 >> floppy as an alternative mount point. 
 >
 >That's a known bug in netboot and it will be fixed in the next
 >version. Until then, you can use the -d option to mknbi-linux
 >as follows:
 >
 >mknbi-linux -d <server-ip>:<root-path> [... other options ...]
 >
 >for example, if your NFS server has address 192.109.10.20 and the
 >root path for the client is /tftpboot/client-root, then use:
 >
 >mknbi-linux -d "192.109.10.20:/tftpboot/client-root" [...other options...] 

I did the above and got this:

% mknbi-linux -d "192.168.1.250:/tftpboot/client1" -o vmlinuz-2.4.18-client bzImage-linux-2.4.18-client 
mknbi-linux: kernel image too large

The size of bzImage-linux-2.4.18-client is 1,574,439 bytes.
Is there anyway to bypass the restriction?

Napi
===========================================================================
This Mail was sent to netboot mailing list by:
Mohd-Hanafiah Abdullah <napi@cs.indiana.edu>
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.