@Kyle Alexander Buan It sounds like you are probably fine. If you are able to make(and save) changes to UEFI then I don't think you are in the same boat as those of us who have been bit by this bug. You may have an affected model, but as of now you don't seem to have hit the wall so to speak.
I also wanted to add a few details clarifying the status on my Toshiba Satellite S55T-B5233. I don't have as much time to really pay attention to what's going with my computers as I might like these days. Too many distractions with all the kids at home and learning new things for work. I didn't initially make the connection that my UEFI firmware was broken by the Ubuntu 17.10 install. I was going to try Solus and could not get my thumbdrive to boot. From there things went south quickly.I tried to enter the UEFI firmware settings to check legacy mode and secure boot, but inputting F2 to enter setup just caused a reboot. I tried using grub to manually boot the thumbdrive, but without luck despite the device showing up in ls on the grub command line. I tried installing refind, flashing a "bios" update from windows 10, reading boot entries with efibootmgr and then trying to modify them. I broke my grub entries and nothing worked. Then finally I copied the boot structure from another Ubuntu install by mounting the hdd on that computer to fix the entries GRUB2 boot cfg entries and get it booting again. Then I decided that since (in my mind) Windows 10 was somehow responsible for everything that I should just chainload my Windows 10 USB install media from GRUB (the only USB boot that I could actually get working correctly) blow away my ubuntu install, then let Windows delete all the partitions and re-install, magically fixing the UEFI settings on the way. Despite already clearly understanding that the partition table and boot files were critical I did not back up the necessary information. What an idiot! So here I am with a completely non-booting machine. I can't enter UEFI Firmware Settings. I can't boot from USB. I have had zero success getting the HDD to boot again. I have an arduino Uno and was thinking about buying a soic8 test clip to read and reprogram the chip. I don't often work low level, but have on many occasions. In the past I have hardmodded and recovered Original Xbox game consoles using a homemade Serial programmer. Recently I dug into my ankercam and wired in a connection to the debug console. So direct soldering isn't out of the question, but I'd like to avoid it if possible. Maybe I can use a potato chip bag clip and some spare wire to make my own clip on adapter. My best assessment is that the UEFI is located on a chip with the following text: AH1430 258648SIC E57651 I can't seem to come up with anything while searching though. Any thoughts are welcome. I'm happy to be a guinea pig. Any useful links or information is greatly appreciated. Sorry if this post is incoherent or rambling, but it's late here and my brain doesn't seem to be working quite right. -- 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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Xenial: Invalid Status in linux-hwe-edge source package in Xenial: Fix Committed Status in linux-oem source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Released Status in linux-hwe-edge source package in Artful: Invalid Status in linux-oem source package in Artful: Invalid Status in linux package in openSUSE: New Bug description: SRU Justification 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. Fix: Disable this driver. Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! #### UPDATE (20/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-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 TravelMate B113 Toshiba Satellite S55T-B5233 Bug may effect machines from any manufacturer that uses BIOS based on Insyde Software --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- Architecture: amd64 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: 00000000Not Defined dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvr00000000NotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+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
