Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

See closed question - this is a less localised version of the same question.

Summary: changing CMS support in BIOS after attempting dual boot Windows 8 and Ubuntu 12.10 bricked my laptop.

While looking into this today I came across this as well - that bug relates to Samsungs, but that model of Samsung has a very similar motherboard to my Asus, and similar problems were reported with Lenovo Ideapads.

There seems to be some way in which the interaction of OS installers with UEFI motherboards ends up bricking machines. Does anyone know why this might happen and how it can be avoided?

share|improve this question
up vote 1 down vote accepted

That is impossible to answer as it stands. UEFI is a very new "standard", traditionally BIOSes (and similar setups) have only been tested with the Windows du jour, and used to break with strictly conforming use by Linux (and often still does, Linux has either talked some sense into the BIOS writers or has learnt to kludge around the worst offenders by now). So it is certainly possible that a non-standard UEFI configuration bricks the machine, though unlikely.

Before any experiments, check it there is a clear path for unbricking (or untying knots it might get tied into), ask your pal Google for experiences from others with the same machine (or whatever UEFI version is in the box). Check the documentation for whatever shim you want to use carefully.

[Probably overly paranoid...]

share|improve this answer
I think you did answer the headline question - basically yes! The question of how it can be avoided doesn't seem to have any solution so far. My original question was because I wanted to know whether it was something I did, or because the motherboard was faulty - it almost certainly was something I did. I did try Googling every variation I could think of that might be relevant, and nothing came up. The closest was the Samsung issue, for which no clear solution seems to be available. – sybilsleaf Jan 31 '13 at 19:40

Looks like your original question should not have been closed, check this out:

share|improve this answer
Ha yeah I saw that, I think the problem was that my question referenced a particular model or something. – sybilsleaf Jan 31 '13 at 19:37

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .