Thanks a lot! I will try it! :) Lawrence
-----Original Message----- From: Eric W. Biederman [mailto:firstname.lastname@example.org] Sent: 2003?1?10? 15:38 To: LinuxBIOS Cc: Lawrence LL. Dai Subject: Re: Boot from etherboot - blocked by INT 10
"Lawrence LL. Dai" email@example.com writes:
I suppose that mknbi and mkelf would also cause this problem.Because they both tag a kernel, but the kernel must be the one like vmlinuz and vmlinux needs BIOS functions such as INT 10. (I know vmlinux does not need INT X, but vmlinux can not be tagged by mknbi and mkelf. Or I have missed something else?)
The difference is mknbi/mkelf that come standard with etherboot when the process the linux kernel start the kernel in 16bit mode and run it's BIOS code, mkelfImage simulates the effect of the 16bit BIOS code by reading LinuxBIOS tables or making the needed BIOS calls itself, and then it enters Linux at it's unofficial 32bit entry point.
mkelfImage can take either a bzImage or a vmlinux.