Fwd: "Ubuntu 17.10 Temporarily Pulled Due To A BIOS Corrupting Problem"

Bob Jonkman bjonkman at sobac.com
Tue Dec 26 16:28:10 UTC 2017

Hash: SHA1

- From the GTALUG mailing list:

- -------- Forwarded Message --------
Date: Mon, 25 Dec 2017 17:24:54 -0500 (EST)
To: Toronto Linux Users Group <talk at gtalug.org>
Subject: [GTALUG] "Ubuntu 17.10 Temporarily Pulled Due To A BIOS
Corrupting Problem"
<https://gtalug.org/mailman/listinfo/talk>,<mailto:talk-request at gtalug.org?subject=subscribe>
From: D. Hugh Redelmeier via talk <talk at gtalug.org>

This is scary but hard to evaluate.

The best guess is that there is an oddity in the Lenovo firmware that
interacts with a recent Linux kernel change in a bad way.

- - it is not specific to Ubuntu: it also effects some Acer, Toshiba,
Dell,   and other notebooks.  See the list in the Launchpad report.

- - Maybe the problem is fixed by this or something related

We should let wizards work on this.

If it hits you, it seems that your current setup will be very
important to preserve until there is a fix.  In particular, you will
only be able to boot from the current boot entry, and that means your
EFI partition's GUUID is important and the path to the .efi file
(shim?) that gets booted is important.  If you wipe your disk you may
never be able to boot again.

Much of this is guesswork on my part.
- ---
Talk Mailing List
talk at gtalug.org
Version: GnuPG v2
Comment: Ensure confidentiality, authenticity, non-repudiability


More information about the ubuntu-ca mailing list