Ubuntu 17.10 corrupting BIOS of many Lenovo laptop models

Re:Ubuntu 17.10 corrupting BIOS of many Lenovo laptop models by codemac on Wednesday December 20, 2017 @11:45AM (#15971177)

EFI allows for OS's to modify probably too much, and the state of EFI implementations aren't defensive enough.

I personally would blame Lenovo for releasing something so brick-able.

[ Parent | on HN ]

Re:Ubuntu 17.10 corrupting BIOS of many Lenovo laptop models by mcny on Wednesday December 20, 2017 @11:56AM (#15971297)

I managed to brick my Asus N61JV-X2 by updating the bios using their official bios update software. (Specs if you're curious https://www.anandtech.com/show/2962/asus-n61j-x2-optimus-gt3... )

I also learned that backup bios chips were a thing but not usually available on a notebook PC

[ Parent | on HN ]

Re:Ubuntu 17.10 corrupting BIOS of many Lenovo laptop models by vetinari on Wednesday December 20, 2017 @12:38PM (#15971799)

I managed to brick Thinkpad X230, flashing BIOS update that came via TVSU. Now, that's an achievement :/

[ Parent | on HN ]

Re:Ubuntu 17.10 corrupting BIOS of many Lenovo laptop models by ct0 on Wednesday December 20, 2017 @01:46PM (#15972498)

Here I was thinking that the 230 was indestructible

[ Parent | on HN ]

Re:Ubuntu 17.10 corrupting BIOS of many Lenovo laptop models by Crontab on Wednesday December 20, 2017 @03:16PM (#15973378)

EFI is a fucking soup sandwich. In my opinion, it suffers from complexity and too much ambition.

[ Parent | on HN ]

Re:Ubuntu 17.10 corrupting BIOS of many Lenovo laptop models by discreditable on Wednesday December 20, 2017 @12:21PM (#15971599)

OSes tickling the BIOS is nothing new. Vendors have been providing Windows-based flashing utilities for a long time. Even most of the special bootable flashing disks run freedos.

[ Parent | on HN ]

Re:Ubuntu 17.10 corrupting BIOS of many Lenovo laptop models by JdeBP on Wednesday December 20, 2017 @01:14PM (#15972183)

As pointed out several times in the headlined bug report, this is not an EFI problem. Several people reproduced this problem on systems either that were booting using the CSM or that did not have EFI firmwares in the first place.

[ Parent | on HN ]