In article <dingelde.719765444@putzl> dingelde@igd.fhg.de (Dennis Dingeldein) writes:Hmm. While it's entirely possible that linux won't work on the machines (it does happen), the fact that it doesn't work on *any* of them makes me wonder about your boot-disk (and possibly root-disk) integrity. Linux does work on most AT-386's it seems, and the above seems a bit too unlucky (although at least some Compaq machines are known for doing things their own way: Compaq has this IBM-complex and thinks it can change the standards to suit itself. I think it's gotten better). The easiest way to prove there is no problem with a boot floppy is to find a computer it boots on: if you cannot, you should make sure you downloaded the images in binary mode all the way etc. If the bootimage is corrupted (or only partly written or similar: rawrite seems to have problems with some machines), the normal result is the reboot you describe. Don't be fooled by the fact that "Loading..." appears to work: that is handled by only the first 512 bytes, so even if they are good, the rest may not be. Linus
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Christoph Lameter | [00/41] Large Blocksize Support V7 (adds memmap support) |
| Linus Torvalds | Linux 2.6.27-rc5 |
git: | |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Nick Piggin | Re: Mainline kernel OLTP performance update |
