#275
Very similar procedure I have shared with few of other Lenovo forum members
(and few others from here).
Sadly, did not receive feedback or some were not able to follow my instructions.
Key was to force BIOS recognizing changes by replacing hard drive. My
trick was to have same partitions map
@toxicpublic
If you dare, you can download the BIOS exe from Lenovo site, extract the
content and take the binary firmware file and next follow the service recovery
guide:
https://www.bios-mods.com/bios-recovery/insyde-bios-recovery/
However, I doubt this will help. This is not touching the now-
I don't think this fix is meant to repair already affected systems rather to
avoid this event in fresh installs.
But as it has been software induced the good news is that this can be
restored... As long as you still have running system available.
--
You received this bug notification because yo
Dear Colleagues.
TL;DR - there is hope!
I've been approached by Anthony from Canonical and later Brian from
Lenovo. We have agreed I will send my Laptop to Lenovo for
investigations. So I wanted to prepare fresh system (clean my personal
data, naturally). After making the hacks and changes I did r
Since people don't care to read whole discussion I'm going to repeat myself
here every few posts.
It is not caused by Ubuntu 17.10
It is general Linux issue (I was Antergos user when it hit me)
Solution is to physically replace NVRAM chip and reflash it with the content
from the old one.
Workarou
5 matches
Mail list logo
