[Hydraulix989]

I'm afraid you're misguided here.

Lenovo initially released a BIOS with a goto statement added to jmp out of the disk controller mode setting (which is normally present and allows the user to change back to AHCI mode). Reverse engineers on the Lenovo forums discovered this modification while studying the disassembly.

Then, one user patched the BIOS and manually reflashed it using an SPI flasher and some soldering, and Linux worked just fine by detecting the drive.

Yes, the ideal solution is that Intel gives specs to OSS devs to build a driver (or even builds on themselves), but the path of least resistance is to have Lenovo unblock that BIOS setting, which amounts to changing one line of code, or 15 minutes of one engineer's time.

[creshal]

> Lenovo initially released a BIOS with a goto statement added to jmp out of the disk controller mode setting

Because switching to AHCI mode with Windows installed would brick the machine (Yay, Microsoft), and Lenovo foolishly assumed that people who wanted to use Linux would buy one of the Linux certified machines instead (X1 Yoga and 60 series Yoga devices are all certified: https://support.lenovo.com/us/en/documents/pd031426 – but I'm sure that's just more proof that Lenovo hates Linux for some reason).

> the path of least resistance is to have Lenovo unblock that BIOS setting, which amounts to changing one line of code, or 15 minutes of one engineer's time.

Which is exactly what Lenovo did: https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Yo...

[Hydraulix989]

"Because switching to AHCI mode with Windows installed would brick the machine"

There are tons of BIOS settings that could "brick" my machine though, it's a weak argument, really. My car didn't come with a lock on the hood.

"Which is exactly what Lenovo did"

Okay, you're acting like it didn't require any teeth pulling on our end to get them to release it (check out the 30+ page forum topics).