30 January 2013

Linux booting UEFI can scrap Samsung notebooks

Various Samsung notebooks are damaged by the time you boot a Linux distribution using UEFI so that the devices do not work now. This is from several reports suggest the Ubuntu bug tracker. The problem may also occur in other Linux distributions, because they appeared to cause a competent for Samsung Notebooks drivers in the Linux kernel problem. The kernel developers are discussing a change that cripples the driver at boot via UEFI.

Just last year, a user has informed the Ubuntu developers about the problem after Ubuntu 12.04 and 12.04.1 in live operation was run on a Samsung 530U3C [1], the launch took place on UEFI from a USB stick. Ubuntu hung on shortly after the start of the kernel, and then the owner turned off the notebook by pressing and the A / blanker. Then started the notebook - not even the firmware showed yet. Samsung has repaired the unit under warranty and it replaced the motherboard. When the whole thing happened again with the repaired unit, informed users of the Ubuntu developers about the problem.

Since then, a number have reported other users that have disrupted their notebooks by booting Linux so that they no longer start. The problem does seem to with Ubuntu 12.10 and other Samsung models, in the bug report [2] report concerned that the model lines 300E5C [3], NP700Z5C, NP700Z7C [4] and NP900X4C [5] show the problem. It only occurs, however, when Linux starts by UEFI, whether Secure Boot it is on or off, seem to care. The problem can circumnavigate when you start Linux on the Compatibility Support Module (CSM), the UEFI firmware of many current systems containing a CSM to start about operating systems as it does a PC with a traditional BIOS and firmware. During the boot via CSM, Linux can not install easily into a parallel in UEFI mode installed Windows.

The Ubuntu developers have been replaced with Samsung employees who have formed the kernel driver "samsung laptop" as the main suspect. The had other owners of Samsung notebooks causes problems [6], when Linux was started by UEFI. In the analysis of this error the Intel developer Matt Fleming is involved, a week ago made ​​two changes to the kernel discussion has [7]. You should create the problem of the world, for one of them [8] ensures that the Samsung drivers do not even active when Linux was started by UEFI. According to current knowledge should prevent damage to Samsung notebooks. The patches are available but not yet in the main development branch [9] recovered from Linux, also in the recently released stable and long-term kernels 3.0.61 [10], 3.4.28 [11] and 3.7.5 [12] they are not included.

According to Canonical employee Steve Langasek the Samsung developers have been trying for several weeks to develop a firmware update that prevents the problem. Langasek also recommends Ubuntu on Samsung notebooks installation of a recent Daily Image to start [13]. There, the Ubuntu developers have taken steps to prevent the problem - but it is still not entirely clear whether they are sufficient. There may be triggered by other than the Samsung laptop driver bug that is still other ways in which to make the hardware or firmware disturb some Samsung notebooks so that they no longer boot.

No comments:

Post a Comment