Yes, it seems to be more like a BIOS problem. What exactly does
the kernel loader depend on? How could I get a non-compressed version of
the bootimage?
Just for information: zImage gets loaded by BOOTP/TFTP, I don't know
anything special about the BIOS of the machine (apart from its TCP
support), but I think there could be some essential features missing
(which features does the kernel loader depend on?).
As I understand from the code, in the 'Loading Linux...' stage, the
kernel gets loaded (err yes, if from floppy, it gets loaded from
floppy, but if already recieved via TFTP, what does happen at this
stage? Does it get just copied? I think this part is BIOS dependend?
Are those BIOSes just simulating a floppy disk? Could the image
get corrupted in the copying process (i.e. overlapping regions)?
How could I verify this?) - lots of questions, no answers for now :)
Thanx, Richard.
PS: tried 2.1.9[012345], all failed with 'invalid compressed format',
2.0.xx instantly reboot after 'Loading Linux...' (2.0.31 too -
dunno what this 2.0.31 image exactly is that I have lying around...)
PPS: dunno about TFTP, is this a secure transfer? could the image
get corrupted (unnoticed) during the transfer?
-- Richard Guenther <richard.guenther@student.uni-tuebingen.de> PGP: 2E829319 - 2F 83 FC 93 E9 E4 19 E2 93 7A 32 42 45 37 23 57 WWW: http://www.anatom.uni-tuebingen.de/~richi/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu