In the Etherboot Src/arch/i386/Config
There is an option -DCOFIG_X86_64.
You need to enable it to use Etherboot boot elf with X86-64 kernel.
Regards
YH
-----Original Message----- From: ebiederman@lnxi.com [mailto:ebiederman@lnxi.com] Sent: Friday, August 20, 2004 10:11 AM To: dbs@stonekeep.com Cc: linuxbios@clustermatic.org Subject: Re: Opteron / Tyan motherboard fault on boot.
Dave Belfer-Shevett dbs@stonekeep.com writes:
On Thu, 2004-08-19 at 19:29, Eric W. Biederman wrote:
mkelf-linux --rootdir=rom --ip=rom ./bzImage > vmlinuz.tyan
This is your first problem.
mkelf-linux does not know how to bypass the BIOS calls so it will not work under LinuxBIOS.
Ahhhh.
Please get mkelfImage 2.5 ftp://ftp.lnxi.com/pub/mkelfImage.
Done, compiled, and installed. I'm a little worried here though:
./mkelfImage --kernel=/tftpboot/bzImage --output=/tftpboot/vmlinuz-2.tyan
When I do a 'file' on the new image, I see:
/tftpbot/vmlinuz-2.tyan: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, corrupted section header size
This image (bzImage) is an Opteron compiled kernel, which should be 64 bit, unless there's no real difference in the elf header.
Stefan already gave the practical explanation. The small bit beyond that is the x86_64 kernel does not even have a valid 64bit entry point.
The code is actually present in the 32bit etherboot to cope with an 64bit in for x86_64. But except for test programs I have not been able to find any native ones.
Eric _______________________________________________ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios