On 02/01/2013 12:56 PM, gogalthorp wrote:
>
> As I understand it it happens on the install so you would have to make a
> install disk with the kernel that avoids the problem . Note the problem
> is still there just the newer kernels will avoid triggering it. The
> problem is in the uEFI code and it still could be triggered by
> something.
That may or may not be correct. As I understand it, the bug is in the BIOS, and
is triggered by the samsung-laptop module when it is probing the BIOS. As long
as that module is not loaded, then everything should be OK. The Linux EFI core
will not map the BIOS memory and thus cannot trigger the bug. Of course, as was
noted earlier, any hacker wanting to cause problems can use the samsung-laptop
code as a prescription on how to brick the laptop, and could easily write
malware to do that from Windows. To do the same under Linux would require kernel
privilege, and would be a lot less likely.
I’m sure Samsung is tired of replacing motherboards under warranty, and should
have a BIOS fix available soon.