[–]▶ No.842494>>842505 >>842522 >>842665 [Watch Thread][Show All Posts]
https://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-17.10-BIOS-Corrupter
>Canonical has temporarily pulled the download links for Ubuntu 17.10 "Artful Aardvark" from the Ubuntu website due to ongoing reports of some laptops finding their BIOS corrupted after installing this latest Ubuntu release. The issue is appearing most frequently with Lenovo laptops but there are also reports of issues with other laptop vendors as well.
>This issue appears to stem from the Intel SPI driver in the 17.10's Linux 4.13 kernel corrupting the BIOS for a select number of laptop motherboards. Canonical is aware of this issue and is planning to disable the Intel SPI drivers in their kernel builds. Canonical's hardware enablement team has already verified this works around the problem, but doesn't provide any benefit if your BIOS is already corrupted.
>A respun Ubuntu 17.10 release with the updated kernel is expected, but as of writing the download page is still discouraging the use of 17.10.
<Should your BIOS be corrupted, you may need to replace your motherboard if there is not a removable flash chip. There are some reports that resetting the BIOS does work, but it's too early to know if that works for everyone. This issue has been confirmed for several different lines of Lenovo laptops including the Yoga and IdeaPad products. There is also the reports of it affecting a few Acer, Toshiba and Dell laptops.
https://wiki.ubuntu.com/ArtfulAardvark/ReleaseNotes#Known_issues
▶ No.842505>>842772
>>842494 (OP)
I upgraded to that version on my thinkpad, so far no issues but this kind of retarded stuff is quite worrying.
I guess I'll be switching back to Debian.
▶ No.842515
#### UPDATE (22/12/2017) ####
LENOVO machines affected so far (please add your affected model to this list):
Lenovo B40-70
Lenovo B50-70
Lenovo B50-80
Lenovo Flex-3
Lenovo Flex-10
Lenovo G40-30
Lenovo G50-30
Lenovo G50-70
Lenovo G50-80
Lenovo S20-30
Lenovo U31-70
Lenovo Y50-70
Lenovo Y70-70
Lenovo Yoga Thinkpad (20C0)
Lenovo Yoga 2 11" - 20332
Lenovo Z50-70
Lenovo Z51-70
Lenovo ideapad 100-15IBY
The bug also affects:
Acer Aspire E5-771G
Acer Aspire ES1-111M-C1LE
Acer TravelMate B113
Toshiba Satellite S55T-B5233
Toshiba Satellite L50-B-1R7
Toshiba Satellite S50-B-13G
Dell Inspiron 15-3531
Mediacom Smartbook 14 Ultra M-SB14UC
Bug may effect machines from any manufacturer that uses BIOS based on Insyde Software. Insyde is responding to emails acknowledging that they are aware of issue but are not providing details.
>https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147
▶ No.842522>>842524 >>842529
>>842494 (OP)
Can someone enlighten me here - is it possible this is a backdoor gone wrong?
Why would the kernel need to write to the BIOS?
▶ No.842524>>842562 >>842645 >>842820 >>842959
>>842522
>Impact: Many users are reporting issues with bios corruption with 17.10. This seems to stem from enabling the intel-spi-* drivers
▶ No.842529
>>842522
Intel chipset driver. My guess is the bios manufacturer's chips either don't follow their published specs or they're non standard and they just ship black box drivers to MS. Or Canonical just stumbled on some Chinese hardware backdoor on accident.
▶ No.842534>>842540 >>842836
What the FUCK am I reading, how did this reach production code?
▶ No.842540
>>842534
Ask the bios devs
▶ No.842544>>842607
▶ No.842562>>842915
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/comments/169
>Normally Linux only reads JEDEC ID of the chip and nothing else.However, in this case it may be possible that Linux does unlock + operation + lock which leaves the flash locked and confuses BIOS.
This is actually a linux kernel (((bug))). Ubuntu just enabled the driver.
>>842524
>intel.com
>berg
Totally not a back door.
Linux is total botnet now.
▶ No.842599
>blaming Linux or Ubuntu for a BIOS that can be destroyed by software
I wonder why the Lenovo chinks made a BIOS software could "corrupt". I'm sure it was an accident.
▶ No.842607
>>842544
>On embedded it's not really common on low-end stuff where Linux dominates, but on more powerful embedded systems like firewalls/routers and Sony consoles yeah it's used.
As someone who's been doing embedded development for 20 years, the most powerful embedded boxes you'll find use Linux. And Windows. Simultaneously. And several other operating systems. The Big Boy Boxes literally have vmware under the hood with entire instances of OSes to handle drivers that are only available on one platform and also to handle all the other embedded companies they've acquired and "integrated" the firmware of. And then often another OS that acts as a UI and orchestrator of the rest of them.
When the company I was at was acquired I was the one responsible for overseeing that "integration" process of our firmware from our side, and I was horrified. A large conference room full of Indians on their side was the team responsible for duct-taping all that shit together.
▶ No.842642
I don't know why you would ever use a non-LTS version anyway.
▶ No.842645>>842667
>>842524
>intel-spi.c
If they had written it in Rust this would not have happened.
Take this as a wake up call people. Rewrite it in Rust!
▶ No.842665
>>842494 (OP)
>Jewbuntu
Haha, Ubuntu niggers get what they deserve, like (((amazon))) pillaging their data like the good soyim they are
▶ No.842667
>>842645
>Rewrite it in Rust!
HA! You're actually right! C fags btfo!
▶ No.842669>>842670 >>842685
Wow, what a perfect storm.
Ubuntu pajeets rush out software they can't bug fix so they don't test.
Linux follows specs without testing on real hardware.
Intel and chinks lazily shit out proprietary BIOS that is confused and hangs itself when some firmware is locked after flashing for some reason.
I still have no idea why the fucking BIOS should be needing write access to flashed SPI firmware but w/e.
▶ No.842670
>>842669
oh and to top it all off, the only way to fix the problem is to BUY A NEW FUCKING MOTHERBOARD! God damn.
▶ No.842685>>842729
>>842669
You don't even understand the bug, and you're forming an opinion on why it happened... You're a dumbass.
▶ No.842729>>842738
>>842685
>oy vey your too dumb to have an opinion ignore your bricked hardware and kernel that writes your bios so hard it bricks that driver is only there for perfectly acceptable reasons like writing to your bios without the users knowledge to install (((upgrades)))
▶ No.842738>>842750
>>842729
You're a retard. The BIOS isn't writing to any firmware. SPI is the process through which one flashes the BIOS firmware. It's not "without the user's knowledge", it's a well documented interface, in an open source kernel, which just happened to have a bug. You're a fucking retard.
▶ No.842750>>842758
>>842738
>install jewbuntu
>jewbuntu writes to the bios, locking it, without the user initiating it.
<oy vey it's not "without the user's knowledge" it's in the source goy! just read the whole kernel source code and every drivers source code it's plain as day! you gave consent to write to your bios when you installed the operating system.
▶ No.842758>>842762
>>842750
Why are you making this about "Jewbuntu", when it's a kernel bug?
>Without the user initiating it
It's called running the fucking kernel, retard
▶ No.842762>>842771 >>842777
>>842758
>It's called running the fucking kernel
the kernel is not expected to write to your bios without you directly initiating it and if this was standard practice it would have been disabled years ago due to outcry. someone fucked up and your a shill.
▶ No.842766
The Year of the Linux Desktop is at hand!
They fixed the videocard problems!
They fixed the soundcard problems!
They fixed the WiFi problems!
Now they're fixing the BIOS corruption problems!
Only a few more years of polishing needed!
Hang in there... hang...
<Braveheart voice and heroic battle music
Haaaaaaaaaannnnnnng!!!
▶ No.842771>>842830
>>842762
The kernel is expected to do whatever's in the code running on it. Read the fucking bug report, it's not even the kernel's fault, but Lenovo's.
▶ No.842772>>843068
>>842505
>switching back to Debian.
Good choice. It respects your freedom better too.
▶ No.842773>>842781
Guys, it may actually be a Systemd problem too!
https://github.com/systemd/systemd/issues/2402
▶ No.842777>>842827
>>842762
>your a shill
Keep trying to shift the blame, Pajeet.
▶ No.842781
>>842773
lol what a faggot
▶ No.842820>>850099
>>842524
>>intel.com
>INTEL gets caught installing IME backdoor.
>INTEL gets commit access to linux kernel.
>ubunpoo exposes kernel unlocking bios for write access for (((reasons)))
>of fucking course poettering is in on it too.
▶ No.842827
>>842777
i thought canonical was a hub of diversity ubuntukike
▶ No.842830
▶ No.842836
>>842534
>intel in charge of drivers
This isn't the first time they've bricked hardware like this.
▶ No.842840
>>842774
Is that using Enlightenment?
▶ No.842856
>>842774
>clover
>not ribbon
▶ No.842915>>842969
>>842562
<<berg
<Totally not a back door.
>Westerberg
<<berg
<Totally not a back door.
>Westerberg
<<berg
<Totally not a back door.
>Westerberg
Learn your jew names, burger anon.
▶ No.842959
>>842524
Intel wasn't satisfied with having a botnet on just the motherboard. Now they are up in the leeenux kernel.
▶ No.842971
▶ No.842980
>>842969
This is true for 4/pol/ and 8/pol/ honestly.
▶ No.843000>>843047
Intel is fucking cancer no matter where they touch. May God have mercy on our souls.
▶ No.843045
▶ No.843047>>843050
>>843000
Fun fact: I was at a big store a few days ago and went to browse their computer section. All the laptops were Intel/AMD shit. Dozens and dozens of models, maybe 40 or so different laptops but all Intel/AMD shit, not even an ARM in sight, much less MIPS or anything more exotic. How depressing! In the 80's and even early 90's that same store was filled with all kinds of different computers, from ZX-81 to Amiga.
Anyway I don't feel comfortable if any firmware can be flashed without the user setting a jumper on the mobo. Not that I'm confortable with Intel to begin with, but this is ridiculous. Anyway I'm done, moving to ARM SBC and old computers. Hasta la vista, Intel! I'm gonna pretend you never even existed.
▶ No.843050>>843051
>>843047
That's not a "fun fact", just your autism leaking.
>implying it would be even remotely profitable to sell MIPS or ARM based personal computers to normies in a big box retail store.
▶ No.843051
>>843050
Ever heard of chromebook? It runs web browser for facebook normie stuff. Some of the have ARM chip and better battery life than Intel shit. Well that store didn't even have those. Just Intel/AMD. And if you think about it, what's even the point of 40+ different models of the same fucking architecture? It makes no sense. How the fuck is that in any way profitable? It's like trying to sell 40+ different kind of oatmeal. Not even different breakfast cereals that are fundamentally different grains, but just dozens of fucking oatmeal brands. Yeah, it's retarded. But such is the state of moderm computing.
▶ No.843068
>>842772
>It respects your freedom better too.
Does not respect your init freedom.
https://devuan.org/
▶ No.843113
>>842969
You didn't get my post, did you? "Westerberg" is as non-jewish as a berg can be.
▶ No.850099
>>842820
>>ubunpoo exposes kernel unlocking bios for write access for (((reasons)))
Systemd does that actually. It's been reported many times. EWONTFIX.