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

LP linuxpusher2 at gmail.com
Tue Dec 26 17:03:52 UTC 2017

I guess I will Report a Bug next time even if unsure.
I am not that experienced but thought  it was corrupting bios.
Others confirmed I should try update the Dell Latitude D531bios firmware.
At first I could not get any Linux to install, I forgot "nomodeset"
Stars have a bunch of donated laptops that are Dell Latitude D531 giving a
Bios error but I was more concerned with getting bcm4311 wifi working
I had been struggling for weeks off and on to get Any New Linux Distro to
work with D531 & bcm without the Errors.
This post explains a lot.
Thank you.

*bcm4311 fix*:


sudo apt-get remove bcmwl-kernel-source broadcom-sta-common
sudo apt-get install firmware-b43-installer
sudo modprobe b43
grep [[:alnum;]] /etc/modprobe.d/* | grep ssb

On 26 December 2017 at 11:28, Bob Jonkman <bjonkman at sobac.com> wrote:

> 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"
> List-Subscribe:
> <https://gtalug.org/mailman/listinfo/talk>,<mailto:talk-request at gtalug.org
> ?subject=subscribe>
> From: D. Hugh Redelmeier via talk <talk at gtalug.org>
> <https://www.phoronix.com/scan.php?page=news_item&px=
> Ubuntu-17.10-BIOS-Corrupter>
> <https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147>
> 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
> <https://github.com/torvalds/linux/commit/d9018976cdb6eefc62a7ba79a405f6
> c9661b08a7>
> 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
> https://gtalug.org/mailman/listinfo/talk
> Version: GnuPG v2
> Comment: Ensure confidentiality, authenticity, non-repudiability
> vR0AoNmcwSQpUMuctzEQqXa4DkGqFOfH
> =mNmS
> --
> ubuntu-ca mailing list
> ubuntu-ca at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-ca
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-ca/attachments/20171226/5a7ed5ae/attachment.html>

More information about the ubuntu-ca mailing list