from:"gamdow"

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-02-02 Thread gamdow

> #556
? Please explain how to fix it is i cant boot to ubuntu only access to live
without previous OS

It sounds like you have the same issue as me (only boot from Live USB),
but you don't have an (inaccessible) installation of Ubuntu on the
laptop's HDD? Do you have access to another computer where you could do
an installation to the laptop's HDD or another USB stick perhaps? It's
pretty straight forward (though I always end up breaking the other
computers grub, but you can fix that with 'update-grub'). Once you have
the bootable Live USB and another device (HDD/USB) accessible from the
laptop with the full installation, you should then be able to follow the
instructions in my post, #554 (use the Live USB's grub terminal to
select and boot from an installation drive and update the kernel there).

--
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:
corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
Unknown
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-edge source package in Xenial:
Fix Released
Status in linux-oem source package in Xenial:
Fix Released
Status in linux source package in Artful:
Fix Released

Bug description:
An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
drivers results in a serial flash that is read only in Intel Broadwell
and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

1. Boot into Ubuntu
2. Download
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
3. Install the downloaded package:
$ sudo dpkg -i
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
4. Make sure the kernel is installed without any error. Once installed,
reboot.
5. At grub, choose the newly installed kernel. You can choose the "recovery"
mode.
6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
7. In case your BIOS is not recovered, reboot to the new kernel, then reboot
*once again* to the new kernel, do not enter BIOS settings before the reboot.
After the second reboot, check BIOS.
8. If your BIOS issue remains, download another kernel from
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
and use dpkg to install it, then repeat steps 4 to 6.

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found
at https://goo.gl/xUKJFR.

---

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.

---

Affected Machines:

Lenovo B40-70
Lenovo B50-70
Lenovo B50-80
Lenovo Flex-3
Lenovo Flex-10
Lenovo G40-30
Lenovo G50-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 Yoga 3 11"
Lenovo Z50-70
Lenovo Z51-70
Lenovo ideapad 100-15IBY

Acer Aspire E5-771G
Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
Acer TravelMate B113
Acer Swift SF314-52 (Fixed by 4.14.9)
Toshiba Satellite S55T-B5233
Toshiba Satellite L50-B-1R7
Toshiba Satellite S50-B-13G
Toshiba Satellite L70-A-13M
Dell Inspiron 15-3531
Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix)
Acer Aspire E3-111-C0UM
HP 14-r012la

---

Affected serial flash devices by manufacturer part number, JEDEC ID
(SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c)
/* ESMT */
f25l32pa, 0x8c2016
f25l32qa, 0x8c4116
f25l64qa, 0x8c4117
/* GigaDevice */
gd25q16, 0xc84015
gd25q32, 0xc84016
gd25lq32, 0xc86016
gd25q64, 0xc84017
gd25lq64c, 0xc86017
gd25q128, 0xc84018
gd25q256, 0xc84019
/* Winbond */
w25q16dw, 0xef6015
w25q32dw, 0xef6016
w25q64dw, 0xef6017
w25q128fw, 0xef6018

---

Original Description:

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

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-02-01 Thread gamdow

> #548
> Is it possible to create some sort of persistence on the liveusb, install the 
> latest kernel, then change my settings upon reboot? 

So I had the variety of this issue where I could only boot from the
particular Ubuntu 17.10 Live USB I did the original install with (BIOS
locked to a particular vendor/iso ID?). After quite a wild journey
trying to find a way to update the Live USB kernel (without modifying
the ID) I discovered a far simpler solution.

0. Presumably you have an installation of the bad 17.10 on the laptop HDD. If 
not, use the Live USB to do that (or another USB stick if you like)
1. Boot from the Live USB. When you reach the grub boot menu, hit 'c' to access 
the grub terminal.
2. Try to find the device id of the partition (e.g. '(hd0,1)') where the Ubuntu 
installation is located. Probe around with commands like 'ls (hd0,1)', 'ls 
(hd1,2)', etc. If SecureBoot is preventing you from using 'ls' try 'cat 
(hd0,1)/etc/issue', it should return something like 'Ubuntu 17.10 \n \l'.
3. Now issue the following commands to set and boot boot from that installation;
  'grub> set root=(hd1,2)' # replace with the id you found in step 2
  'grub> linux /vmlinuz root=/dev/sda2' # While sdb2 is the equivalent of 
(hd1,2), the root for this command is not necessarily the same as the previous 
one. The boot drive will be promoted to sda, replacing the USB stick. So root 
here should be sda2 for an installation with the default partitioning. Getting 
this wrong will result in init script error along the lines of 'can't mount 
/dev to /root/dev'. You may be able to figure out the correct root from the 
(initrmfs) terminal you end up in, try 'ls' there.
  'grub> initrd /initrd.img'
  'grub> boot'
4. Follow the OP's instructions for updating the Kernel, up to and including 
the reboot. However, you will end up back at the Live USB grub menu, but this 
is fine an you are nearly done.
5. Execute steps 1 to 3 again. This will boot the installation with the new 
kernel.
6. Reboot, access BIOS menu and check you can modify settings.
7. Pull the Live USB and burn it in a fire.

At this point, my BIOS was fixed, but I was still booting to the grub
menu. So I just did a fresh install of the fixed Ubuntu (17.10.1).

-- 
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:
  corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
  drivers results in a serial flash that is read only in Intel Broadwell
  and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

  Symptoms:
   * BIOS settings cannot be saved
   * USB Boot impossible
   * EFI entries read-only.

  ---

  Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
  the kernel so it is not compiled with Intel SPI support. But previous
  affected machines still suffered from a broken BIOS.

  Repair: If you still can boot into Ubuntu, you can recover your BIOS
  with the following steps:

  1. Boot into Ubuntu
  2. Download 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  3. Install the downloaded package:
    $ sudo dpkg -i 
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  4. Make sure the kernel is installed without any error. Once installed, 
reboot.
  5. At grub, choose the newly installed kernel. You can choose the "recovery" 
mode.
  6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
  7. In case your BIOS is not recovered, reboot to the new kernel, then reboot 
*once again* to the new kernel, do not enter BIOS settings before the reboot. 
After the second reboot, check BIOS.
  8. If your BIOS issue remains, download another kernel from 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
 and use dpkg to install it, then repeat steps 4 to 6.

  After your BIOS is fixed, the kernel packages you just installed are
  no longer needed, you can remove it by running 'sudo dpkg -r linux-
  image-4.15.0-041500rc6-generic'.

  The patch used to build the linux v4.15 kernel in step 8 can be found
  at https://goo.gl/xUKJFR.

  ---

  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.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-02-04 Thread gamdow

@fardin

Happy to hear you're making progress, though I won't be able to help you
as much at this stage because your system is setup up differently from
mine.

Since you've reached the initrmfs terminal, you just need to locate
"vmlinuz" now that the drives have been reordered. That should be
wherever the root of filesystem has been mounted (e.g. "/"). Thankfully
initrmfs will have all the basic functions of a standard terminal. So
try "lsblk" to list all the drives/partitions and their ids, and look
for the partition that has the "/" MOUNTPOINT. That should be the name
you use for the root in the second grub command.

Failing that, you could use other basic terminal commands like "ls
/dev", 'find / -name "vmlinuz"', etc. to figure out your particular
setup.

--
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:
corrupted BIOS due to Intel SPI bug in kernel

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found
at https://goo.gl/xUKJFR.

---

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.

---

Affected Machines:

---

Original Description:

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

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-02-03 Thread gamdow

@fardin

I'm no expert on the grub terminal, but you should be able to access all
the attached devices even if you couldn't boot from them. There's maybe
a command that lists all the partitions, but I was locked out of using
modules thanks to SecureBoot. So I used the following method;

The device id (hdn,m) represents drive number 'n' and partition 'm'. So
starting with drive 0, partition 1, try 'cat (hd0,1)/etc/issue'. If you
get a 'file not found' error increment the partition, e.g. 'cat
(hd0,2)/etc/issue'. If you get a 'drive not found' error increment the
drive number and reset the partition, e.g. 'cat (hd1,1)/etc/issue'. Once
you find the id that returns something ('Ubuntu 18.04 \n \l', I'm
guessing in your case), continue onto step three.

This is the brute force method, but you can probably calculate the right
drive number base on the number of devices on the laptop (0=Boot device
(USB), 1=HDD, etc.). The partition number will be the partition of the
root filesystem '/' where you installed. So, best guess for you is
(hd1,2). If that doesn't work you'll have to use the brute force method.
If *that* doesn't work, then I'm afraid I'm at the limit of my
knowledge. Maybe some research into the grub terminal will help you
figure out if you can access and boot from the installed drive. It
should be possible based on my experience.

--
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:
corrupted BIOS due to Intel SPI bug in kernel

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found
at https://goo.gl/xUKJFR.

---

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.

---

Affected Machines:

---

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

4 matches

Site Navigation

Mail list logo

Footer information