BHARATHWAJ MUTHUSWAMY <[EMAIL PROTECTED]> writes: > Hello, > > Thanks to Eric's advice, etherboot goes a LOT further, but doesn't > work.... > > I have attached a dump from minicom again.. > > The command I used for generating the kernel elf image: > > mkelfImage --kernel=bzImage-2.4.14 --command="console=ttyS0,115200 single > ro root=/dev/hda1" --output=kernel > >Entering udp_transmit >transmitting type 0800 packet (32 bytes). status = 7048, cmd=0100 >ioaddr: 0x00001040 >txfd: >000999C0 00 00 0C 40 C0 99 09 00 D0 99 09 00 00 80 20 02 >000999D0 18 90 09 00 0E 00 00 00 D0 90 09 00 20 00 00 00 >s1 = 0048, s2 = 2048. >\done >Firmware type: linuxBIOS
O.k. So etherboot successfully loaded the kernel, convert_params.c from mkelfImage runs and detects linuxBIOS, and then we don't have any output from the linux kernel on the serial port. My hunch is that you are in the stage of a linuxBIOS port where you haven't yet gotten the kernel to run under linuxBIOS. So this could be all kinds of things. Things to try. 1) verify that you actually have serial console support compiled into the kernel. 2) use vmlinux instead of bzImage. It is bigger but as it isn't compressed, and won't fail silently if the when decompressing the kernel you might be able to see something useful. 3) Try netbooting memtest86 and see if your memory is actually o.k. It certainly looks close but ruling out possiblities is always helpful. Eric
