Jump to content

Photo

Ubuntu corrupted BIOS?


  • Please log in to reply
13 replies to this topic

#1 Mr.J

Mr.J

    Member

  • Members
  • 41 posts

Posted 27 December 2017 - 01:58 PM

Hello everybody,

 

this bug here is a big one. Meanwhile I have had to realize that my Bodhi install is affected as well and no help is in sight. My BIOS simply is not working properly; no install media is detected and I have to think about a few scenarios:

 

http://www.omgubuntu...ovo-laptop-bios

 

https://bugs.launchp...ux/ bug/1734147

 

For some people the install of Kernel 4.14.9 has solved the issue, not for me. Question:

Hopefully my Bodhi system will work for a while. But what will happen if a simple update may break something?

 

 





A big thank you to everyone who contributes to Bodhi Linux


#2 Jeff

Jeff

    Lead Developer

  • Developer
  • 12582 posts
  • LocationBloomington, IL

Posted 27 December 2017 - 05:44 PM

Honestly at a skim it doesn't sound like anything we can do anything about. Your system isn't going to randomly stop working from normal use and you'll just need to wait for Lenovo to work with the upstream Ubuntu folks to fix their hardware. 



#3 Charles@Bodhi

Charles@Bodhi

    Old Faithful

  • Moderators
  • 4677 posts
  • LocationZeist, The Netherlands

Posted 27 December 2017 - 07:11 PM

Just had a long read at Launchpad about this. The cause is the kernel Ubuntu 17.10 ships with. I'm not sure Bodhi uses the same kernel version for Bodhi 4.4.0 or not.

 

@ Mr.J 

Using the kernel version that caused the broken bios, can you post the outcome of the command

uname -pir

@ Jeff

If this matches the default kernel for 4.4.0 we should do something about it, I don't want people holding us responsible for bricking their machines while we know this happens with a number of Lenovo , Acer and Toshiba models and some more having the same Uefi chip with Intel-spi firmware.

 

Seems like kernel version 4.13.0-21 does not show the braking behavior, so that should be a good alternative stable kernel.

 

For fixing the affected machines people should install kernel version 4.14.9 and reboot once or twice to get a working UEFI again. After that installing 4.13.0-21 and removing all other versions would be a good idea to have a stable situation again.

Alas this 4.14.9 version is not in the Xenial repos, might be a great service to put it in the Bodhi repos.

 

Enjoy,

Charles



#4 Charles@Bodhi

Charles@Bodhi

    Old Faithful

  • Moderators
  • 4677 posts
  • LocationZeist, The Netherlands

Posted 27 December 2017 - 09:10 PM

On an affected machine you should look closely as to what is to be updated. If it is related to the bootloader don't do it (Grub & efi packages & signed stuff). Has to do with the fact that the uefi returns to an old state because of the bug, but grub is updated and that causes conflicts.

 

Possibly you will need to install the linux-headers for the 4.14.9 kernel too in order to have it working.

 

Enjoy,

Charles



#5 Mr.J

Mr.J

    Member

  • Members
  • 41 posts

Posted 27 December 2017 - 09:14 PM

Jeff, Charles,

 

I appreciate your help, thank you. My kernel is 4.10.0-42 generic, because I have come to the conclusion that 4.13 is not a good choice at the moment. All Lenovo users should wait a little bit. A lot of smart guys are working on this.

 

Personally speaking my BIOS is locked. Absolutely nothing works. I realized this a few months ago. Nothing worked so far and I think it is not only a matter of Ubuntu 17.10, there are some more cases. The good news is: My Bodhi system is working and I am updating more conservative than before.



#6 graywizardlinux

graywizardlinux

    Bodhi Supporter

  • Members
  • 1090 posts

Posted 27 December 2017 - 09:18 PM

i updated this am. i hope mine are not affected.  i hate to turn them off now.

 

 

i appreciate all your help and info charles - but would not know how to do all of that if needed.  I guess we will see!



#7 Charles@Bodhi

Charles@Bodhi

    Old Faithful

  • Moderators
  • 4677 posts
  • LocationZeist, The Netherlands

Posted 27 December 2017 - 10:09 PM

Well, there were no older thinkpads mentioned as affected machines, only a Yoga Thinkpad. I thought that had a touchscreen.

Your laptops are probably sound and safe.

The 4.13 kernel was only introduced in Bodhi Linux with the 4.4.0 release and I doubt the earlier releases were having a buggy kernel.

 

Enjoy,

Charles



#8 graywizardlinux

graywizardlinux

    Bodhi Supporter

  • Members
  • 1090 posts

Posted 28 December 2017 - 12:28 AM

Thank you!

 

:-)))



#9 BeGo

BeGo

    Member

  • Members
  • 162 posts
  • LocationBogor, Indonesia

Posted 28 December 2017 - 05:21 AM

Regarding kernel, 

 

for some reason the ubuntu kernel lowlatency 16.04 hwe-edge (4.13.x) can't play nicely with virtualbox (I need it for hosting my Windows 10)

 

dkms and initframs problem + can't install guest addition, yikes!  :wacko:  :wacko:  :wacko:

 

So I revert to hwe without edge (4.10.x).  ;)



#10 graywizardlinux

graywizardlinux

    Bodhi Supporter

  • Members
  • 1090 posts

Posted 28 December 2017 - 11:59 AM

jus saw this:

 

https://www.phoronix...7.10-Laptop-Fix



#11 Oblio

Oblio

    Bodhi Team

  • Team
  • 240 posts

Posted 31 December 2017 - 08:05 PM

As a longtime system builder, I still really cannot fathom that an OS would kill a BIOS.  The only way I have found to kill a BIOS is through a bad flash/losing power while performing a flash (lightning does a decent job too!).

 

Pretty odd.

 

Thank you everyone for sharing!


Xeon E3-1220 v3 3.1GHz Quad, ASRock Rack E3C224, 2x 8GB Kingston KVR16E11/8I DDR3-1600 ECC CL11 Intel Chips (Dual Channel), EVGA GeForce GTX 570, Samsung SM863 120GB OS SSD, 2x WD RED 3TB HDDs (Raid 0), Focusrite Scarlett 2i4, Antec Earthwatts EA-750 80 Plus Platinum 750w PSU - Bodhi 4.4.0 64

AMD Phenom II X4 940 3.0GHz Quad, Gigabyte GA-MA78GPM-DS2H, 2x 2GB Kingston KHX8500D2K2 DDR2-1066 (Dual Channel), EVGA GeForce GTX 570, Intel 40GB OS SDD, Seagate ST31000340AS 1TB HDD, Seagate STBD4000400 4TB HDD, EVGA 500w Bronze Plus 80+ PSU - Bodhi Linux 3.2.1 64


#12 Charles@Bodhi

Charles@Bodhi

    Old Faithful

  • Moderators
  • 4677 posts
  • LocationZeist, The Netherlands

Posted 31 December 2017 - 09:10 PM

AFAIK It boils down to an Intel module called spi and the driver for it. Intel had noticed that this was flashed to ROM by vendors with one byte off, which likely would cause issues. So Intel had sent out a warning to not activate this driver in the kernel. In the vanilla 4.13.0 kernel it is set to disabled.

Ubuntu modifies their kernels to better suit their releases, nothing wrong with that. But then someone in the Ubuntu kernel team decided to set the spi-driver to enabled very short before the final release of 17.10. Now we all know that the module really causes issues! 

Bodhi Linux uses the ubuntu kernels and often chooses the kernel from the latest release for an update-release so we have the latest hardware support. Reading the OP our kernel has the same behavior as the 17.10 kernel. So please for now don't use it in UEFI mode for the time being. For what I gather installing in Legacy mode should be safe.

 

Enjoy,

Charles



#13 SRYoung

SRYoung

    Member

  • Members
  • 30 posts

Posted 08 January 2018 - 12:38 AM

you can update to the newer kernel with ukuu  http://www.teejeetec...de-utility.htmland bypass this problem



#14 Charles@Bodhi

Charles@Bodhi

    Old Faithful

  • Moderators
  • 4677 posts
  • LocationZeist, The Netherlands

Posted 10 January 2018 - 08:34 PM

For those interested, the Ubuntu folks have declared the latest 4.13.0 kernel is no longer qualified as "hwe-edge", but just "hwe", so it should be stable.

After apt-get update you can install linux-image-extra-4.13.0-26-generic and linux-headers-4.13.0-26-generic. It should also bring you two dependencies.

AFAIK this kernel does not have the Bios corruption, has a fix for the Spectre/Meltdown processorflaws and brings virtualization support.

 

 

As for fixing a "broken Bios" the summary at launchpad for this bug has a link to a more recent kernel made available that should work, give it a try. 

 

Enjoy,

Charles






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users