Re: [Etherboot-developers] Problem with mknbi-linux-1.2-4
Brought to you by:
marty_connor,
stefanhajnoczi
|
From: <ke...@us...> - 2001-09-19 21:02:17
|
> mknbi-linux --output=vmlinuz.ltsp \ > --append="init=/linuxrc " \ > --rootdir="/dev/ram0" \ > bzImage \ > /tmp/initrd.ltsp.gz > > >bzImage is 658631 bytes >initrd.ltsp.gz is 864103 bytes > >When I run disnbi -e vmlinuz.ltsp, I get this: > >-rw-r--r-- 1 root root 512 Sep 19 16:21 nbidir >-rw-r--r-- 1 root root 4608 Sep 19 16:21 segment0 >-rw-r--r-- 1 root root 512 Sep 19 16:21 segment1 >-rw-r--r-- 1 root root 512 Sep 19 16:21 segment2 >-rw-r--r-- 1 root root 4608 Sep 19 16:21 segment3 >-rw-r--r-- 1 root root 653824 Sep 19 16:21 segment4 >-rw-r--r-- 1 root root 864256 Sep 19 16:21 segment5 > >I don't know enough about the segments, but it looks like segment4 is >the kernel, but >it is somewhat smaller. That's ok, the segment excludes the bootblock and the setup blocks. >And, segment5 is the initrd image, and it is slightly larger. That's ok, it's padded up 4k. >I can continue using mknbi-1.2-2, but I figure there may be a problem that >you all need to take a look at. That's strange because there have been no changes in that area. Also I just tested mknbi-1.2.4 with a 5.0.4 bootrom and the images load with no problems, both NBI and ELF images. You're sure your kernel is not too large and colliding with Etherboot? Is it a zImage or a bzImage? |