4 ms·
"This guy" is relatively known for hacking on Linux laptop drivers and a long relationship with Intel hardware and power management in particular, so I'll stop
by jsmthrowaway 10y ago
"This guy" is relatively known for hacking on Linux laptop drivers and a long relationship with Intel hardware and power management in particular, so I'll stop short of appealing to authority and just say I value his speculation even if it is that. (Which I don't think it is.)
- guelo 10y agoThis guy is so knowledgable that he says > Why not offer the option to disable it? A user who does would end up with a machine that doesn't boot But the modder that flashed the custom BIOS was able to boot linux on the first attempt.
- teraflop 10y agoThat comment was clearly referring to the common case of ordinary Windows users, who could easily render their existing systems unbootable by changing the driver mode after Windows was already installed.
- michaelmrose 10y agoRandom joe user should probably not be messing around with his bios or should at least be smart enough to know what he changed or at worst reset his bios to default. If not use the tech support you pay for.
- digi_owl 10y agoHe also seems to have a severe hardon for EFI...
- seba_dos1 10y agoThen obviously Intel providing the drivers is what he'd like to see happening, regardless of what and why Lenovo did here. With the driver, it doesn't matter if Lenovo did it to lock out older Windows versions, Linux users or just to screw with their customers for fun - because it would work. However, it's still Lenovo who's playing bad here. Intel provides a mode in their controller that works with everything. It's Lenovo who deliberatelly made it almost impossible to access.