| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 129276 | 2013-02-14 06:42:00 | Buying a new laptop with Win8 | --Wolf-- (128) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1328092 | 2013-02-16 08:51:00 | KarameDave, I'm saying that Microsoft's approach is bossy. :) | bk T (215) | ||
| 1328093 | 2013-02-16 09:07:00 | I used capitals because this issue has permanently bricked a number of samsung laptops, if you think it's bossy then you are mistaken. OK? Totally agree with that comment. The HP Laptop I had to turn off the UEFI Secure Boot certainly didn't like it. It popped up a couple of very serious looking warnings about disabling it, including one something along the lines of your OS may not boot if doing so. |
wainuitech (129) | ||
| 1328094 | 2013-02-16 19:14:00 | KarameDave, I'm saying that Microsoft's approach is bossy. :) Oh! OK, just thought you were having a go. The big problem with the Samsung ones is not just 'secure boot' though. They have a bug in the UEFI that bricks them if you try loading other OS's This is from www.h-online.com "UEFI variables enable operating systems to deposit data for the firmware that will still be available after a reboot. Microsoft's Windows 8 Hardware Certification Requirements stipulate that at least 64KB of storage must be available for this purpose. When a crash occurs in certain configurations, the Linux kernel uses this storage to deposit information that allows the cause of the crash to be investigated later; Linux places about 10KB of data in a UEFI variable for such a "crash dump". According to Garrett's analysis, this is the actual reason why some Linux distributions destroy Samsung notebooks. The samsung-laptop driver that was previously considered to be the main cause of the disruptions only contributes to the problem through the way it works on UEFI systems: it causes the crash which results in a crash dump being written. How large an amount of data is required to cause firmware malfunction remains unknown; Garrett says that he generated 36 one-kilobyte variables in the tests that resulted in a notebook being disabled under Windows." nmercers suggestion of using legacy BIOS should prevent the issue I think (but I'm uncertain) |
KarameaDave (15222) | ||
| 1328095 | 2013-02-16 20:38:00 | KarameDave, I'm saying that Microsoft's approach is bossy. :) this is all about protecting PCs from malware and rootkits in particular |
nmercer (3899) | ||
| 1 2 | |||||