The problem is that, perhaps as a result of that complexity, it's been badly implemented on a lot of hardware, and also that the manufacturers are only testing it with the software they expect it to run on. And since we're talking about laptop hardware, that software is Windows.
We don't have to even go to mess of not being able to install and run software you want on hardware just because of UEFI. And all that bullshit how "it is possible IF blabla IF blabla IF, and IF You just do this and that and pray" is just bullshit because people should never ever have problems what UEFI delivers.
I had got a black screen on an acer laptop which was quite frustrating but if you press the FN key then the brightness up button, it would show the startup ubuntu desktop. it reads the lowest dim setting as off instead of what it should be. don't know if thats the same for these samsungs but its worth a shot.
A similar case several years ago... lmsensors could brick some IBM Thinkpad laptops while probing for sensors. While the software developers quickly blacklisted the hardware and put up dire warnings, it's not their fault that it was trivially possible to corrupt firmware.
My Linux server uses UEFI just fine. In fact, it makes things easier with GPT partitioning on 3TB hard drives.
In fact, when I was helping out other customers on NewEgg's tech support site.. Somebody came to the forum who had decided to use a 3rd party utility to flash a BIOS to his motherboard that wasn't even the right BIOS for the Asus Motherboard.. It flashed OK but then the board wouldn't power up, but the key-combo worked to get his mobo to install the correct BIOS from removable media. Surprise surprise, he used the 3rd party utility because Asus's BIOS updater refused to flash the wrong BIOS to the board. Yet he was still able to recover his hardware.
It's not hard to make hardware that's idiot-proof.
Dell's BIOS recovery is even easier... You just put the disk in and it will install the BIOS from the disk automatically if the currently flashed BIOS is corrupted.
On the overwhelming majority of Android devices and tablets these days, even if you have a bad firmware flash, you can put the device into a mode such that the PC can write directly to the device's memory allowing you to flash it remotely,... simply by holding down a couple buttons while the device is powering up..Insert the diskette into the diskette drive of the malfunctioning computer. Then turn the computer on.
The computer automatically regenerates the BIOS from the diskette.
Any device that bricks from software, is a defective hardware design. There is ZERO excuses. This is 2013 and customers don't need to put up with crap hardware and they can vote with their wallet.
Two words can describe these Samsung devices.. GARBAGE HARDWARE.
It's 100% Samsung's fault. Not only did they make crappy hardware, but they trusted other people to provide the linux support for their hardware instead of doing it themselves.. They were practically begging for this kind of problem to happen.
I'm so glad I didn't buy a Samsung ultrabook now, was really close to buying one last month. I'll probably still buy a Samsung phone though, as they don't brick.
Last edited by Sidicas; 01-30-2013 at 10:02 PM.
(I have heard of coreboot and knew there was a flashing program but didn't clue in on the name)