[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Paul (sabret00the) (#190): All good - stackexchange doesn't make that detail (the fact that the direct URL only loads for you) obvious. Not sure why, I presume to combat spam or something. -- Hmm. Quoting a bit of #193 (uocc4me / uoccdisp-uone): > After clobbering the bios during the 17.10 install, I erased 17.10 and installed 16.04. The machine has been running Ubuntu 16.04 just fine for several weeks now (many reboot cycles), although things like hibernate and suspend don't work, presumably because the bios is stuck in legacy mode (can't switch to UEFI). This (and the rest of the report) seems to disprove the "two full reboots" theory. :( I wonder what chip models that Mika Westerberg was dealing with (re #169 and #173) and whether they were Winbond or not. The links from those comments are only about the Yoga, there's no mention of the actual vendor type. If the SPI Flash model is different in Mika's case then maybe there are different solutions for different Flash chips. -- >From #193 allen (krell): > I think we are off on the wrong track. This is fundamentally a CVE against Insyde Software BIOS and possibly other vendors. In the same class as the Samsung samsung-laptop bricking in 2013 (https://bugs.launchpad.net/ubuntu-cdimage/+bug/1040557?comments=all) and the systemd EFI bricking in 2016 (https://github.com/systemd/systemd/issues/2402). -- >From #192 Miguel Alejandro Roche Villarreal (exploud345): > I have a Acer Aspire E5-511-C5QS with the same issue with BIOS, i try solution from TOXIC (toxicpublic) in #185, but says invalid EFI file path, also i can't try solution from Paul Sladen(#173) because i can't boot Ubuntu, only Grub Shows and allow me to boot my Windows 10 partition, i hope someone finds a solution for Windows I may be wrong as I'm still learning the intricacies of EFI, but it's possible GRUB is simply confused about your partition structure and you can tell it where to find and boot Linux. Figuring out where it glitched is beyond the scope of this thread - you'll want to go hunting online for this info - but here is a POTENTIALLY DANGEROUS trick that may make the process easier if you just have the one computer. You don't have to continually reboot between Windows and GRUB to test things out, you can simply create a new virtual machine in eg virtualbox and point the VM at your computer's hard drive. The only dangerous part is accidentally selecting to boot Windows in the VM: running two operating systems off of one disk is going to mean corrupted files, as both OSes compete for raw access to the disk (and have increasingly different ideas of what data is where). So if you can carefully make sure you don't boot Windows from GRUB (and maybe even keep task manager open to kill virtualbox instantly in case you do), I'm reasonably confident (standard disclaimers apply) that you may be able to fiddle around and get GRUB booting Linux. Booting Linux inside the VM should be safe, as it's the only copy of Linux running off that particular partition. The idea is to figure out what to do in GRUB to make Linux boot, write the commands down, then reboot and apply the commands. The above being said, standard disclaimers do apply, there are many little unforeseen things that could go wrong with this. I don't know what EFI information Ubuntu saves between reboots; what happens when the system is rebooted from a VM onto bare metal may be worth reasoning through. I also WOULD NOT recommend getting GRUB to save the EFI information _from inside the VM_ - both because this will rewrite the boot sector and EFI partition and this might give Windows indigestion, and also because virtualbox's EFI setup is going to be different to the real hardware. ** Bug watch added: github.com/systemd/systemd/issues #2402 https://github.com/systemd/systemd/issues/2402 -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Installed Ubuntu 17.10 (no dual boot, no EFI) on my Lenovo G50-70. Ubuntu successfully installed, Laptop boots, Ubuntu works well. But * No longer able to boot from USB (tried several different devices) * Boot from CD works, (can boot any OS from CD) * BIOS settings are not being saved. I somehow managed to boot from USB https://gist.github.com/ankurk91/e91ae91a445cd46ba54b5548793966f3#file- grub-boot-from-usb-md -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
** Description changed: 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 - Dell Insperion 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: Not 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:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
** Description changed: 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 (01/12/2017) + 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 - Dell Insperion (with Insyde Software BIOS) + Dell Insperion + + 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: Not 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:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
I have the problem with unchangable bios settings. I can still boot from a USB thumb drive, so I can help with testing if someone prepares a bootable image I can put on my USB thumb drive. some details: Acer Aspire ES1-111M-C7DE I have this chip inside my computer: Winbond 25Q64FWSIG (I will try to attach a picture) Insyde bios: InsydeH2O Setup Utility Rev. 5.0 bios version 1.08 After clobbering the bios during the 17.10 install, I erased 17.10 and installed 16.04. The machine has been running Ubuntu 16.04 just fine for several weeks now (many reboot cycles), although things like hibernate and suspend don't work, presumably because the bios is stuck in legacy mode (can't switch to UEFI). When I try to change bios settings, it says they are saved, but actually they do not change. Even if I remove the hard drive and the USB drive and boot into the bios, it still shows the hard drive and USB stick even though they are not there. If I try to boot with a different hard drive installed, the bios does not detect it (and still shows the old hard drive). Can't boot from the different hard drive. I booted with a Windows USB stick and tried to re-flash the bios, but at the point it is about to begin writing the bios, the machine just reboots. Many thanks to those making efforts... ** Attachment added: "chip inside my Acer Aspire ES1-111M-C7DE" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+attachment/5025433/+files/SAM_3163.JPG.small.jpg -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
I have a Acer Aspire E5-511-C5QS with the same issue with BIOS, i try solution from TOXIC (toxicpublic) in #185, but says invalid EFI file path, also i can't try solution from Paul Sladen(#173) because i can't boot Ubuntu, only Grub Shows and allow me to boot my Windows 10 partition, i hope someone finds a solution for Windows -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
I think we are off on the wrong track. This is fundamentally a CVE against Insyde Software BIOS and possibly other vendors. Any attacker with kernel mode access could do the same thing, regardless of Linux install. I am not sure, but it is possible someone with admin access to Windows could create a driver to do the same thing. Any brave pentesters out there want to give it a try and write it up? If Paul Sladen in #173 is correct, this is definitely a CVE against the BIOS. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
To Paul (sabret00the), #158: FWIW, if you want everyone to be able to see your askubuntu post you'll need to post a screenshot of it (just attach it - not going to hurt anything...). The question was deleted so it only loads for you. As for the deletion/closure, that sort of thing happens a _lot_ on stackexchange sites; don't take it personally. As for everyone else: I've just reread through this entire thread and thought I'd reiterate some of the highlights: In comment #141 Anthony Wong explained that the SPI Flash is somehow being write-protected. In comments #164, #169 and #173 Paul Sladen (sladen) copied some potentially interesting thoughts from Mika Westerberg regarding the Flash chip vendors/models. It would be very interesting if someone could post how to dig the Flash chip vendor info out of a running system - perhaps via dmidecode? Those with "kickstart-able" machines could then provide this info. (Not sure if this isn't perhaps already happening via email.) The question at this point is whether the write-protect bit is a fuse that can't be unset. If it can be unset, and some convoluted process can be executed to get bricked machines to somehow boot, well, that'll be very interesting. :) One last thing for developers/anybody who might need to coach someone through PXE booting: I found http://brokestream.com/netboot.c some time ago while looking for a tiny PXE server. This one handles DHCP+TFTP (make sure you have no DHCP server or relay running!), happily boots PXELINUX, runs great on Linux and probably other UNIX-likes, and is very simple to use. Presuming 10.42.x.x isn't in use, - ifconfig up 10.42.0.1 - (find broadcast address (not netmask :D) via ifconfig) - ./netboot 10.42.0.1 10.42.0.2 - The last dash translates to a fully ambiguous MAC address, ie so you don't have to specify that too. And 10.42.0.2 is of course the IP the PXE-ing machine will get. Installing syslinux will provide a copy of pxelinux.0 (mine was in /usr/share/syslinux). In any random dir (I used ~), if you create the directory "pxelinux.cfg" and then create the file "pxelinux.cfg/default" with the contents "default vmlinuz initrd=initrd.img" and then copy vmlinuz and initrd.img to the same root dir (~ in my case), everything should work. This PXE info may prove to be irrelevant, but I thought I'd include it just in case it turns out to be useful to have in the thread. It's also good to know that PXE is not hard to do. (It isn't, but most PXE servers presume large-scale enterprise scenarios...) As for where to get a kernel and initrd, https://help.ubuntu.com/community/Installation/MinimalCD provides an ISO file you can mount and copy the "linux" and "initrd.gz" files out of. CTRL+ALT+F2 gives you a console on this ISO. Note that this one contains _no utilities_ but is a workable start to test with. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
A method to repair machines was posted earlier, but may have been missed in the noise. Paul Sladen in #173 suggests that blacklisting the kernel module, and then doing TWO COMPLETE REBOOTS will allow the BIOS to recover. Looking at the code, this seems plausible. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Can anyone confirm whether this only happens with laptops with Insyde Software based BIOS? Or does it effect BIOS derived from AMI/Pheonix? My Dell had Insyde Software BIOS instead of normal Dell AMI based BIOS seen on business class laptops/desktops. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Just FYI, if you have access to grub, you can enter command monde by typing c and then you can boot from USB : set root=(hd1,1) chainloader +1 boot Le 20 déc. 2017 22:21, "ilmondo" <1734...@bugs.launchpad.net> a écrit : > Same problem on my Lenovo G50-70 doesn't save anymore BIOS settings > > -- > You received this bug notification because you are subscribed to the bug > report. > 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 (01/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 > Dell Insperion (with Insyde Software BIOS) > > --- > > 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: Not 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:rvrNotDefined: > 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 > -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Same problem on my Lenovo G50-70 doesn't save anymore BIOS settings -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Have encountered this issue on a Lenovo G70-80 80FF Laptop, Windows 10 was already installed and wanting to install (dual boot) Linux, which I have had no problems before until Ubuntu 17.10 was installed, and when trying to enter System Settings in Grub is still showing, Error: could not set EFI variable 'OsIndications' managed to boot from DVDROM from Grub command, though USB booting is impossible. Even replacing the HDD does not get around the problem. Removing the HDD completely only end with a Boot Menu that is empty, no way to enter BIOS, and on the note main Function Keys, ie F2 and F12 lock up the booting to Grub. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
** Description changed: 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 (01/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 + Dell Insperion (with Insyde Software BIOS) --- 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: Not 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:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
My Lenovo ideapad 510-15IKB (BIOS Version 3JCN29WW; EC Version 3JEC29WW) does NOT seem to be affected... so far. I can still change my UEFI settings and boot Windows from GRUB. I am currently using Linux 4.13.0-19-generic on Ubuntu 17.10. Is it safe to update to 4.13.0-21.24 now? @orthocube I think something is wrong with your Windows USB drive. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Sorry, I meant "Booting Ubuntu 17.10 from USB flash drive works" -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Okay, so I rebooted and here is what I found (Acer Aspire E5-575G-52DA): - Booting from Ubuntu 17.10 from USB flash drive works - I can change UEFI settings - I can reorder the boot device order - I can change boot mode from UEFI to BIOS (legacy) and vice versa - However, I have a Windows 10 bootable USB flash drive, and no matter the boot mode (legacy or UEFI), it isn't detected, even in the F12 boot menu. Am I affected? I'm literally afraid right now. This is a brand new laptop, and the last thing I want is getting it bricked. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
So, how to fix laptops? Do we need to get out flash chip, reprogram it using special device, and put it back? -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1734147] [NEW] Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
You have been subscribed to a public bug by Rik Mills (rikmills): 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 (01/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 --- 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: Not 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:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ** Affects: linux (Ubuntu) Importance: Critical Status: Confirmed ** Affects: linux-hwe-edge (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-oem (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: Invalid ** Affects: linux-hwe-edge (Ubuntu Xenial) Importance: Undecided Status: Fix Committed ** Affects: linux-oem (Ubuntu Xenial) Importance: Undecided Status: Fix Committed ** Affects: linux (Ubuntu Artful) Importance: Critical Status: Fix Released ** Affects: linux-hwe-edge (Ubuntu Artful) Importance: Undecided Status: Invalid ** Affects: linux-oem (Ubuntu Artful) Importance: Undecided Status: Invalid ** Affects: linux (openSUSE) Importance: Undecided Status: New ** Tags: apport-collected artful kernel-key verification-done-artful wayland-session -- Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models https://bugs.launchpad.net/bugs/1734147 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1739416] Re: panoramagui 4.12.0 broken/unusable for hugin 2015.0.0 in Ubuntu 16.04
** Package changed: ubuntu => digikam (Ubuntu) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to digikam in Ubuntu. https://bugs.launchpad.net/bugs/1739416 Title: panoramagui 4.12.0 broken/unusable for hugin 2015.0.0 in Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/digikam/+bug/1739416/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1739416] [NEW] panoramagui 4.12.0 broken/unusable for hugin 2015.0.0 in Ubuntu 16.04
You have been subscribed to a public bug: I recently upgraded from 14.04 LTS to 16.04 LTS and had to notice, that panoramagui is broken/unsuable/worthless. Hugin 2015 changed from pto2mk to hugin_executor but panoramagui (or "Panorama Creator Wizard" or "Panorama tool") still wants to use pto2mk. Because there's no pto2mk anymore one can't stitch panos with panoramagui. Hugin itself works as you can read here: https://answers.launchpad.net/hugin/+question/402693 Without manually downloading/upgrading/downgrading hugin or digikam one cannot get panoramagui working anymore. This is quite annoying. I don't know if this is worth a bug report because I don't know if it is really a "bug" or more a problem of packaging the wrong versions for Ubuntu. Any help appreciated. Versions: - (X)Ubuntu 16.04.3 LTS - panoramagui 4.12.0 (digikam 4.12.0) - huigen 2015.0.0.cdefc6e53a58 Start panoramagui and you'll get the first screen listing the (needed) hugin binaries (autooptimiser, cpcloean, cpfind, enblend, make, nona, pano_modify, pto2mk). Because pto2mk is not available anymore (has been replaced by hugin_executor) one cannot proceed. A manual upgrade of digikam or downgrade of hugin would be necessary. Proposal: Ubuntu 16.04 could distribute a younger version of digikam and its panoramagui with support for "hugin_executor" instead of "pto2mk". ** Affects: digikam (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- panoramagui 4.12.0 broken/unusable for hugin 2015.0.0 in Ubuntu 16.04 https://bugs.launchpad.net/bugs/1739416 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to digikam in Ubuntu. -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 1070873] Re: kde-telepathy, impossible to connect to gmail accounts
On 20/12/17 09:15, MarcoPau wrote: > Hi, I have artful and I have build kio-gdrive-1.1.80. > > Don't know if kio-gdrive is related with the userActionFinished error: 2 > while trying to add the Google account. I am stuck there. > > Do you have any hint? > > Thanks! > > @Rik Mills, your link does not work any more. > A working signon-ui can be found in our updates PPA https://launchpad.net/~kubuntu- ppa/+archive/ubuntu/ppa?field.series_filter=artful It is also in our backports PPA, along with kio-gdrive 1.2.1 prebuilt .deb https://launchpad.net/~kubuntu- ppa/+archive/ubuntu/backports/+packages?field.name_filter=kio-gdrive -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to meta-kde-telepathy in Ubuntu. https://bugs.launchpad.net/bugs/1070873 Title: kde-telepathy, impossible to connect to gmail accounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-kde-telepathy/+bug/1070873/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
