This bug is old and Lenovo fixed the issue upstream with a corrected BIOS that users can optionally install, which enables AHCI mode.
Also, from my understanding, Linux installs even in the default configuration now, including on the more recent Yoga 910 and 920 models thanks to some patches from Intel that went into the upstream Linux kernel. Unless anyone objects, I think this should be closed as fixed upstream. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F.... pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/14/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 2UCN10T dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK2 dmi.modalias: dmi:bvnLENOVO:bvr2UCN10T:bd10/14/2016:svnLENOVO:pn80UE:pvrLenovoYOGA900-13ISK2:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK2: dmi.product.name: 80UE dmi.product.version: Lenovo YOGA 900-13ISK2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
