So by reading omgubuntu I came across this bug report:
https://bugs.launchpad.net/ubuntu/+sour ... ug/1734147
This makes me lose faith in hardware and software. It's so crazy I had to share it.
One guy fixed his laptop - reply #110
"I got my y50-70 fixed today.
The FIX was to change the BIOS chip with a new one! Costs me 100€.
Good bye ubuntu, let the Windows headaches come back again. This is too bad situation."
Saddest bug ever?
Re: Saddest bug ever?
Wow, is that a linux kernel problem or something that Ubuntu enabled? Are those drivers in an experimental section in kernel options?
Re: Saddest bug ever?
I only know what the bug description says:
"Impact: Many users are reporting issues with bios corruption with 17.10. This seems to stem from enabling the intel-spi-* drivers in the kernel, which don't appear to be ready for use on end-user machines."
Installing in Legacy mode should be safe (although some reports state otherwise), writing to BIOS NVRAM is riskier. But who knows what that driver really did? It wasn't just Lenovo laptops that were affected. The problem seems more Intel specific than Ubuntu specific. I still wonder how a driver can cause BIOS corruption. Crazy.
"Impact: Many users are reporting issues with bios corruption with 17.10. This seems to stem from enabling the intel-spi-* drivers in the kernel, which don't appear to be ready for use on end-user machines."
Installing in Legacy mode should be safe (although some reports state otherwise), writing to BIOS NVRAM is riskier. But who knows what that driver really did? It wasn't just Lenovo laptops that were affected. The problem seems more Intel specific than Ubuntu specific. I still wonder how a driver can cause BIOS corruption. Crazy.
Re: Saddest bug ever?
Thankfully, it doesn't look like those drivers are in the Debian or Liquorix kernels.
- dolphin_oracle
- Developer
- Posts: 19925
- Joined: Sun Dec 16, 2007 1:17 pm
Re: Saddest bug ever?
I had a kernel panic spam garbage data into my nvram once. totally hosed my bootloaders. I had to use the settings utility to clear the nvram and start over. luckily since the efi boot loaders are not stored there, but rather just pointers, it was easy to add them back.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Re: Saddest bug ever?
Thanks for the feedback.
The main problem is that the NVRAM became non-writable. So instead of just dealing with a software bug you are dealing with broken hardware and replacing the BIOS chip is a lot more hassle than let's say replace a faulty drive.
@Stevo Good to know. Thanks.
The main problem is that the NVRAM became non-writable. So instead of just dealing with a software bug you are dealing with broken hardware and replacing the BIOS chip is a lot more hassle than let's say replace a faulty drive.
@Stevo Good to know. Thanks.