Re: [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2018-01-03 Thread Leó Kolbeinsson
On 3.1.2018 10:06, Mika Westerberg wrote:
> Sorry about the delay but we wanted to make sure the proposed fix can
> recover the two test systems we have reliably before asking others to
> try it.
>
> I've attached a patch to this bug that should fix the still affected
> systems. It applies on top of v4.15-rc6 and I'll be sending it upstream
> as well. Canonical already created a kernel package including the fix
> and it can be installed from the following link:
>
> http://people.canonical.com/~ypwong/lp1734147/linux-
> image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
>
> The reason why v4.14.9 which includes 9d63f17661e2 ("spi-nor: intel-spi:
> Fix broken software sequencing codes") recovers many systems but not all
> is because:
>
>   - These systems have CMP=1 in the other status register (SR2) making
> the flash read-only (this is the symptom).
>
>   - Linux SPI-NOR core clears status register properly for flash chips
> that have SPI_NOR_HAS_LOCK set.
>
>   - Serial flashes automatically clear CMP and few other bits if 0 is
> written to the first status register using WRSR command.
>
>   - In order to WRSR take effect the serial flash need to be write
> enabled (WREN must have been issued before WRSR at some point).
>
>   - The systems that recovered the WREN was in effect (probably issued
> by the BIOS before handing off to the OS) so when Linux writes 0 to
> the status register CMP bit is also automatically cleared and the
> problem goes away.
>
> Those systems that were not recovered WREN was not in effect so clearing
> the status register and CMP bit was ignored by the serial flash chip.
>
> Normally WREN is send as a preopcode part of an atomic sequence when
> software sequencing is used. This has been enabled since commit
> 8c473dd61bb5 ("spi-nor: intel-spi: Don't assume OPMENU0/1 to be
> programmed by BIOS").
>
> However, many systems have two write enable preopcodes available the
> PREOP_OPTYPE register:
>
>   0x50 - Write enable for volatile status register
>   0x06 - Write enable (WREN)
>
> The current code picks the former which does not enable write for
> non-volatile bits so any writes to the status register non-volatile
> bits, including BP0/1/2 protection bits do not take effect.
>
> The attached patch changes the driver so that it prefers WREN over other
> write enable preopcodes. Booting to the kernel with the patch applied on
> a system where the issue still persists should reset the protection bits
> and allow the BIOS to save settings again.
>
> ** Patch added: 
> "0001-spi-nor-intel-spi-Prefer-WREN-over-other-write-enabl.patch"
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+attachment/5030406/+files/0001-spi-nor-intel-spi-Prefer-WREN-over-other-write-enabl.patch
>
Hi Mika,

The new kernel is installed and up and running.

Still unable to save settings in BIOS.

Leo

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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/linux/+bug/1734147/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-31 Thread Steve Langasek
On December 31, 2017 12:43:20 PM PST, Bassem Gamea <1734...@bugs.launchpad.net> 
wrote:
>The fix 4.14.9 not working for DELL Inspiron 5551 , I also removed
>17.10 and installed 16.04 from CD , USB still can't boot , and the same
>, no change

If you are able to boot from cd and install Ubuntu 16.04, which requires
making changes to settings in the firmware if you are running in UEFI
mode, are you sure you are affected by this bug?


-- 
Steve Langasek

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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/linux/+bug/1734147/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-28 Thread Leó Kolbeinsson
Exit from grub will also boot linux on a USB stick or CD-rom...

On 28.12.2017 12:05, olekcz wrote:
> What can I do with Lenovo Y50-70 with Windows 10 Only? Ubuntu is
> removed. I have secure boot enabled. Cannot boot from any option, tried
> all of the boot possibilities. Luckily after "exit" from grub I'm able
> to select Windows boot.
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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/linux/+bug/1734147/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-22 Thread Steve Langasek
On Fri, Dec 22, 2017 at 04:27:56AM -, Turbo wrote:
> My two cents would be -now that the ISO was pulled- that a warning with
> big red letters or something shows up when you do "sudo apt-get dist-
> upgrade". In my particular case I had no idea things were so wrong when
> I pressed the Enter key.

We have not done this because the kernel you get with a dist-upgrade is
/fixed/ to no longer trigger this issue.  The problem only remains with the
kernel that was published in 17.10 at release time, which is on the ISOs.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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/linux/+bug/1734147/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-21 Thread Steve Langasek
On Fri, Dec 22, 2017 at 04:18:31AM -, Jared Dominguez wrote:
> (NB: superm1 and I work for Dell)

> Can anyone provide confirmation on this affecting them with the Dell XPS
> 13 (9350) with Intel i7? That's actually exactly what I'm running with
> Artful without issue, and we have not seen any escalations from Dell
> support on this issue on any Dell systems. Additionally, the 9350 does
> not have a BIOS core from Insyde.

This information was added to the bug description by user vitaly.v.ch with
no explanatory comment on the bug that would allow us to confirm he's seeing
the same issue.

So from my POV this is unsubstantiated and the model should be dropped from
the list in the bug description.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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/linux/+bug/1734147/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-20 Thread TOXIC
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-17 Thread Steve Langasek
> It happened again right now, on another G40-30 Lenovo laptop, running
> Windows 10 and Ubuntu 16.04, both in legacy mode. As soon as we inserted
> an Ubuntu 17.10 live USB, the boot setup had the USB listed twice. One
> in legacy and another as EFI (I repeat, the OSs on that laptop are
> installed in legacy mode). By selecting to boot the live USB which was
> listed as EFI, it booted fine. We did not install the new OS, but after
> shutting down the laptop, the BIOS refused to save any changes and also
> refused to read that same USB flash drive in boot options. There has to
> be something very seriously wrong here.

Given the evidence of this to date, I would not suggest that anyone do
further investigation on this problem with their own hardware that would
require expensive professional recovery.  A probable fix is in progress for
the kernel package.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-14 Thread Steve Langasek
On Thu, Dec 14, 2017 at 09:21:31PM -, Pavel wrote:
> I'm wondering, is it realy ubuntu 17.10 bug, or it may be just a
> symptom... and our BIOSes was corrupted erlier? Before we noticed the
> disease.

With so many users reporting this only after using Ubuntu 17.10, and at
least one user reporting it after only booting the live CD without
installing, it is quite likely that this is an Ubuntu 17.10 bug.  We are
continuing to investigate.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-14 Thread TOXIC
No, I've enabled virtualization technology just a bit before installing
Ubuntu, and Ubuntu did manage to write it's name into one of the boot
entries in my bios

Le 14 déc. 2017 22:30, "Pavel" <1734...@bugs.launchpad.net> a écrit :

> I'm wondering, is it realy ubuntu 17.10 bug, or it may be just a
> symptom... and our BIOSes was corrupted erlier? Before we noticed the
> disease.
>
> --
> 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 source package in Artful:
>   Confirmed
>
> Bug description:
>   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 Y50-70
>   Lenovo G40-30
>   Lenovo U31-70
>   Lenovo G50-70
>   Lenovo Z50-70
>   Lenovo Yoga Thinkpad (20C0)
>   Lenovo G50-80
>   Lenovo S20-30
>   Lenovo Yoga 2 11" - 20332
>   Lenovo B40-70
>   Lenovo Z51-70
>   Lenovo B50-70
>   Lenovo Flex-10
>
>   The bug also affects Acer Aspire E5-771G.
>
>   ---
>
>   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:
>
>   ---
>
>   ApportVersion: 2.20.7-0ubuntu3.5
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1:  tob1608 F pulseaudio
>/dev/snd/controlC0:  tob1608 F pulseaudio
>   CurrentDesktop: ubuntu:GNOME
>   DistroRelease: Ubuntu 17.10
>   InstallationDate: Installed on 2017-10-22 (37 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64
> (20171018)
>   MachineType: LENOVO 20378
>   Package: linux (not installed)
>   ProcFB: 0 inteldrmfb
>   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
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>   dmi.bios.date: 08/12/2015
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: 9ECN43WW(V3.03)
>   dmi.board.asset.tag: No Asset Tag
>   dmi.board.name: Lenovo Y50-70
>   dmi.board.vendor: LENOVO
>   dmi.board.version: Not Defined
>   dmi.chassis.asset.tag: No Asset Tag
>   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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-13 Thread kevh
Hello Anthony,

My situation is:

Lenovo Ideapad Flex 10. Came with windows 8 installed and updated to windows 
10. I then installed Ubuntu 14.04 as dual boot and had each release of Ubuntu 
updated since 14.04.
I was dual booting using legacy for Ubuntu and UEFI for occasional access to 
windows 10. Only recent change has been upgrade to version 17.10. I can no 
longer save changes to the boot order in the BIOS. I cannot therefore boot from 
USB and am not able to boot into windows. I can boot into 17.10.
The trigger for this problem arising was clearly the upgrade from 17.04 to 
17.10.

I also have a Lenovo G710 with Xubuntu installed and no other OS. It is
booting using "Legacy". I have also upgraded this from 17.04 to 17.10
and do not have a problem with the BIOS on this laptop.

I live in Cologne, Germany but work away in Mainz-Kastel, Germany during
the week.

My telephone number is 00491713568623.

Kev Hennessey



From: boun...@canonical.com  on behalf of Anthony Wong 

Sent: 13 December 2017 08:10
To: kevhennes...@hotmail.com
Subject: [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops 
models

Dear users,

We are treating this issue very seriously and sorry that this has
happened. We have been working with Lenovo in China at full speed since
last week to find out the root cause. Meanwhile, if you hit this issue,
please send me an email at anthony.w...@canonical.com with your laptop's
model name and the city where you live, optionally you can leave your
phone number so that Lenovo can call you back if they need more
information.  It will also be very helpful if you can also provide a
brief description of what you did (e.g. upgrade from 17.04 to 17.10, or
fresh install 17.10, etc).

Regards,
Anthony

--
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

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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-11-28 Thread Steve Langasek
On Tue, Nov 28, 2017 at 08:57:08PM -, Alexis Rico wrote:
> @Mathieu Trudel-Lapierre Yes, I have two issues:

> 1) BIOS Doesn't work fine. Same problem as @bruno USB Boot doesn't work,
> DVD boot doesn't work and saving bios settings are lost of exit and
> save. No white screen just the changes don't persist across reboots.

> 2) The hard drive failed leaving system non-bootable.

> Today I've also tried installing the OS on a new drive and a different
> computer, booting through PXE to a Ubuntu Live CD and trying to insert a
> new entry for the new os through efibootmgr.

> So far I've learnt that efibootmgr is unable to create a new entry as it
> errors No such File. And deleting the old EFI entries seems to work but
> when rebooting to bios the old EFI entries are still there.

All of this appears to point to a firmware implementation that does not
conform to the EFI standard.  If Ubuntu is doing something "wrong" here, it
is very difficult to discern what it is.

In the past, we have seen problems with the Linux kernel filling up the
firmware's available nvram space and as a result causing boot problems. 
This could be another instance of that problem, but that doesn't seem to fit
with the idea of efibootmgr successfully allowing boot entries to be
deleted.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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/grub2/+bug/1734147/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs