On Fri, Dec 14, 2012 at 12:16:46PM -0600, Bruce Hill wrote: > On Fri, Dec 14, 2012 at 11:18:21AM -0500, [email protected] wrote: > > > > I will try some more desperate tricks today, like reconnecting the USB pile > > to see if it at least boots the disks again - is my choice between disks > > and keyboard? I will find out. My best guess right now is that booting > > 3.7.0 is what clobbered things; whether I added a option which loaded bad > > firmware, or 3.7.0 is broken, I have no idea. It could well be something > > unrelated to 3.7.0. My goal for today is to try to get keyboard and disk > > working, then boot with 3.6.8. > > Whatever you think of logic, it is entirely illogical that a kernel could kill > your BIOS, or any hardware ... at least, just booting into it. > > The southbridge is a good thing to look at, esp for a burned spot/pit. > > My suggestion is http://www.sysresccd.org/SystemRescueCd_Homepage
That's what I've been using. But the hardware failure is illogical too; why would USB and SATA fail at the same time? Or why would southbridge fail when it had been running perfectly fine? I don't really think it was 3.7.0, but who knows, did I answer some config question incorrectly and tell it to load some firmware? Without access to the disk, I can't tell. I don't remember any question about loading BIOS firmware, and can't see why the kernel would even care about that. The whole mess makes no sense. -- Felix Finch, a la mode
