I need help with using Etherboot with LinuxBIOS to boot a Linux kernel over a network using an e1000 NIC and DHCP + TFTP. Using an old EEPro100 payload, I can get this far:
Welcome to elfboot, the open sourced starter. January 2002, Eric Biederman. Version 1.3
Searching for linuxbios tables... lb: ram start: 0000000000000BDC size: 000000000009F424 high: 00000000000A0000 lb: ram start: 00000000000C0000 size: 0000000000030000 high: 00000000000F0000 lb: ram start: 00000000000F0400 size: 000000003FF0FC00 high: 0000000040000000 base_mem_k = 640 high_mem_k = 1047552 ROM segment 0x0000 length 0x0000 reloc 0x9400 end 00000003:df08d339, start 00000002:f628d237 32-bit delta 3726 calibrate_tsc 32-bit result is 1152701 clocks_per_tick = 1152701 Etherboot 5.0.5eb1 (GPL) ELF (Multiboot) for [EEPRO100] bus 00, function C0, vendor 1022, device 1100 . . . bus 04, function 30, vendor 1002, device 4752 Probing...[EEPRO100]No adapter found
Here is the output when I run "file" on the eepro100 payload: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, stripped
This payload won't work since I have an e1000, not an eepro100. But when I use the e1000 ELF file generated by Etherbot 5.2.4 (make bin/e1000.elf) I get almost no useful output to help in troubleshooting:
Welcome to elfboot, the open sourced starter. January 2002, Eric Biederman. Version 1.3
Loading Etherboot version: 5.2.4
Here is the output when I run "file" on this payload: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linkedfile: corrupted section header size.
Perhaps someone on this list can help me figure out what I am doing wrong?