I'm in the same boat, and it's taking on water :-(. Short of hooking the
machine up to the logic analyzer I don't have, the "bad things" happen too
quickly to give a would-be detective any information other than what was
repeated above. No combination of gcc/binutils seems to make any difference.
Someone will probably suggest "broken hardware". They might even be correct,
but that won't fix the problem that didn't exist until we starting tinkering
with the boot code.
In that vein, pending a proper diagnosis and fix, I intend to try backing
out the suspect portions of the 2.3.22-2.3.23 patch set until I can get my
machine to boot. If I can identify the changes that cause the "no boot"
condition, maybe a workaround can be found.
--Bob
rct@wlk.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/