This subject has probably been dropped by now, but my experience might apply to someone else in future. I encountered a situation where I burned an older bios than what I was currently using. This went OK. After I was done with my experiment, I re-burned the newer bios that I had previously replaced. This was with an A31 in good working order. But following the 2nd bios burn, I couldn't get it to go to bios, couldn't get it to boot, eventually couldn't get any response at all. It just sat there like dead.
I replaced the motherboard with a used one from Ebay, but let the old one sit around for months. Then when I lost video on an A31p, I decided to test that old A31 m.b. and surprisingly it worked great. I think this was a case of the bios having to reconfigure itself, to relearn what's in the system, and after that exercise it just took longer than usual. James On Mon, Apr 12, 2010 at 4:53 AM, <[email protected]> wrote: > I did, last night. I have a W500 running OpenBSD which is getting > better ACPI support. That doesn't work yet, but its close. Thinking > about things, it dawned on me to see how old my bios was, and its > pretty ancient. > > I got the iso image and roasted it, and booted it following the > usual directions. It never booted after that, and a call to ez-serve > got me into the queue for a box to send it off to the hospital. > > This is the first time I've managed to brick a thinkpad. What will > happen when it gets to the repair depot? Do they have a test jig > that will fix this, or is the system board trashed? > > All in all, very distrurbing. Does this happen often? > > --STeve Andre' > _______________________________________________ > Thinkpad mailing list > [email protected] > http://stderr.org/cgi-bin/mailman/listinfo/thinkpad > _______________________________________________ Thinkpad mailing list [email protected] http://stderr.org/cgi-bin/mailman/listinfo/thinkpad
