Now I understand why I can no longer boot any USB drive. >:(
--
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:
Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Stat
Can anyone confirm whether this only happens with laptops with Insyde
Software based BIOS? Or does it effect BIOS derived from AMI/Pheonix?
My Dell had Insyde Software BIOS instead of normal Dell AMI based BIOS
seen on business class laptops/desktops.
--
You received this bug notification becau
Just FYI, if you have access to grub, you can enter command monde by typing
c and then you can boot from USB :
set root=(hd1,1)
chainloader +1
boot
Le 20 déc. 2017 22:21, "ilmondo" <1734...@bugs.launchpad.net> a écrit :
> Same problem on my Lenovo G50-70 doesn't save anymore BIOS settings
>
> --
Same problem on my Lenovo G50-70 doesn't save anymore BIOS settings
--
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:
Ubuntu 17.10 corrupting BIOS - many LENOVO laptops model
Have encountered this issue on a Lenovo G70-80 80FF Laptop, Windows 10
was already installed and wanting to install (dual boot) Linux, which I
have had no problems before until Ubuntu 17.10 was installed, and when
trying to enter System Settings in Grub is still showing,
Error: could not set EFI v
** Description changed:
SRU Justification
Impact: Many users are reporting issues with bios corruption with 17.10.
This seems to stem from enabling the intel-spi-* drivers in the kernel,
which don't appear to be ready for use on end-user machines.
Fix: Disable this driver.
Tes
My Lenovo ideapad 510-15IKB (BIOS Version 3JCN29WW; EC Version 3JEC29WW)
does NOT seem to be affected... so far. I can still change my UEFI
settings and boot Windows from GRUB.
I am currently using Linux 4.13.0-19-generic on Ubuntu 17.10. Is it safe
to update to 4.13.0-21.24 now?
@orthocube I thi
Sorry, I meant "Booting Ubuntu 17.10 from USB flash drive works"
--
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:
Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Okay, so I rebooted and here is what I found (Acer Aspire E5-575G-52DA):
- Booting from Ubuntu 17.10 from USB flash drive works
- I can change UEFI settings
- I can reorder the boot device order
- I can change boot mode from UEFI to BIOS (legacy) and vice versa
- However, I have a Windows 1
I am currently running Ubuntu 17.10 on an Acer E5-575G-52DA, and I am
very, very anxious. Trying to restart to see if UEFI is affected...
--
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/1734
So, how to fix laptops? Do we need to get out flash chip, reprogram it
using special device, and put it back?
--
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:
Ubuntu 17.10 c
Having same issue after installing Ubuntu 17.10 on Acer ES1-512. Can't
change any settings in BIOS. Moreover, system don't recognize any DVD or
USB. However, i still can add trusted .efi files, so i installed Windows
10 directly form HDD and doing fine.
Personally, i don't find this problem very c
Lenovo 100-15iby with Kubuntu 17.10
No errors
-I can access to usb in boot menu
(tested in a usb with guadalinex v9. I can use in live mode)
-I can change options in bios and save correctly
(tested with sound beeper option. Changing "disabled" to "enabled", save
changes and exit)
One last thing
** Description changed:
SRU Justification
Impact: Many users are reporting issues with bios corruption with 17.10.
This seems to stem from enabling the intel-spi-* drivers in the kernel,
which don't appear to be ready for use on end-user machines.
Fix: Disable this driver.
Tes
This has also broken UEFI on my Toshiba Satellite S55T-B5233.
--
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:
Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Sta
Could somebody with the hardware also do a test with the following lines
commented out in 'intel-spi.c', commenting out the writel() that
disables SMI interrupt generation, re-compile the kernel and retest:
https://github.com/torvalds/linux/blob/8afda8b26d01ee26a60ef2f0284a7f01a5ed96f8/drivers/mtd
Mika Westerberg emailed again with a pointer to the commit from a few
months ago, specifically dealing with a similar issue on Lenovo Yoga
machines:
"""
mfd: lpc_ich: Do not touch SPI-NOR write protection bit on Haswell/Broadwell
At least on Lenovo Thinkpad Yoga, the BIOS seems to monitor the SPI
and thereby none of these sellers
print(fsfe.web_link)
# https://tehnoetic.com/laptops
--
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:
Ubuntu 17.10 corrupting BIOS - m
This is an ubuntu 17.10 bug, although, Can I report that it doesnot
affect the Lenovo X201.
--
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:
Ubuntu 17.10 corrupting BIOS - m
@Paul (sabret00the) Me too. They simply ignored those reports.
BTW.. This issue also occurs on Flex 2 with linux Mint 18.x (16.04 based).
It started to appear on my machine about half a year ago.
The first symptom was a lack of autoadding entries in the grub menu after the
kernel update.
Everythi
[The two theories provided by Mika Westerberg, verbatim]
"""
Instead I have a theory since as far as I know there have been to kinds
of issues.
1. Flash is left locked. This makes the BIOS impossible to save
settings.
This seems to happen only for GigaDevice flashes and for all of thos
(For clarity the above upload of linux (kernel)=4.13.0-21.24) is a
workaround that just disables compiling in of the module under
suspicion. Because the module is not compiled it, it will not therefore
be loaded either).
--
You received this bug notification because you are a member of Kernel
Pa
This bug was fixed in the package linux - 4.13.0-21.24
---
linux (4.13.0-21.24) artful; urgency=low
* linux: 4.13.0-21.24 -proposed tracker (LP: #1738823)
* Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models (LP: #1734147)
- [Config] CONFIG_SPI_INTEL_SPI_PLATFORM=n
-
** Description changed:
SRU Justification
Impact: Many users are reporting issues with bios corruption with 17.10.
This seems to stem from enabling the intel-spi-* drivers in the kernel,
which don't appear to be ready for use on end-user machines.
Fix: Disable this driver.
Tes
@Paul, Acer TravelMate B113 has 'Winbond' flash chips. Just checked.
--
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:
Ubuntu 17.10 corrupting BIOS - many LENOVO laptops mode
This bug was fixed in the package linux - 4.13.0-21.24
---
linux (4.13.0-21.24) artful; urgency=low
* linux: 4.13.0-21.24 -proposed tracker (LP: #1738823)
* Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models (LP: #1734147)
- [Config] CONFIG_SPI_INTEL_SPI_PLATFORM=n
-
Have received an excellent reply from Mika Westerberg (thank you!). One
with a suggestion regarding 'GigaDevice' flash chips, and one regarding
certain 'Winbond' flash chips.
Is somebody with access or one of more of these machine(s) able to
provide insight into what flash parts are in their mach
Acer TravelMate B113 also affected. This is 2010-2011 laptop.
--
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:
Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Sta
Page 5 of:
http://opensecuritytraining.info/IntroBIOS_files/Day2_03_Advanced%20x86%20-%20BIOS%20and%20SMM%20Internals%20-%20SPI%20Flash%20Protection%20Mechanisms.pptx
Talks about "Flash Protection Mechanism";
"Write Protect / Writes blocked / Not Range Specific / SMI# override:
Same as Write P
I've emailed Mika Westerberg (author of the module) to ask to share
anything further documentation they've got that would allow a better
understanding of the (intended) operation of the 'intel-spi' module.
--
You received this bug notification because you are a member of Kernel
Packages, which is
FWIW, the Intel-SPI Readme contains:
https://github.com/torvalds/linux/blob/master/Documentation/mtd/intel-
spi.txt
"makes it possible to read and write the SPI serial flash, if certain
protection bits are not set and locked."
"… If it finds any of them set, the whole MTD device is made re
@depaulicious You are unaffected then, not all Lenovo notebooks are
affected, actually many Lenovo machines that we originally tested are
good.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
Link to my report that got closed:
https://askubuntu.com/questions/939961/ubuntu-17-10-update-broke-my-bios
--
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:
Ubuntu 17.10 cor
I tried to report this ages ago. The people at AskUbuntu shut my request
for help down.
--
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:
Ubuntu 17.10 corrupting BIOS - many
i had the same problem in Toshiba L50B-23G this is not a lenovo fail
--
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:
Ubuntu 17.10 corrupting BIOS - many LENOVO laptops mode
I'm running Linux 4.13.0-17-generic (nov 6th) on Bionic on a Lenovo Thinkpad X1
Yoga 1st (20FR) and with this kernel version it seems *UNaffected*. I'm not
going to upgrade it now that I know of this issue.
However, if anybody knows whether this kernel version already triggers the bug,
we can te
** Description changed:
SRU Justification
Impact: Many users are reporting issues with bios corruption with 17.10.
This seems to stem from enabling the intel-spi-* drivers in the kernel,
which don't appear to be ready for use on end-user machines.
Fix: Disable this driver.
Tes
Can anyone clarify if this issue is caused by simply having the intel
SPI kernel driver enabled & loaded into the kernel, or does this kernel
driver need to be also combined with something in userspace that does
something with the device before the BIOS gets affected?
--
You received this bug not
Lenovo ideapad 100-15IBY was affected too. I installed Ubuntu 17.10 and
day after that I booted via PXE to systemrescuecd and wipe HDD. After
that I tried to install Win10, but USB drive is not recognized by the
BIOS. I can't change anything in BIOS, efibootmgr -b 2 -B failed with
error: "Could not
FWIW, I installed Kubuntu 17.10 on a brand-new Lenovo Flex 5 several
days ago before I knew about this issue and did not experience any
problems.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
If the bios is corrupted, the solution is reset bios.
In Dell page support there is the process
--
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:
Ubuntu 17.10 corrupting BIOS
XPS 13 9350 I7 BIOS corrupted
Same problem with bios
--
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:
Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Status in li
I am planning to install 17.10 on my Lenovo Ideapad S400 , should I
proceed? Does this bug damages the BIOS ROM permanently? Thanks in
advance.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
I UNFORTUNATELY can not remember what distro I may have just installed
to trigger this bug on my Lenovo (I multibooted), though this exact
issue happened to me on my Lenovo Z70. It happened to me long before
17.10 was out and to be fair before 17.04. I used (still do ..) many
different distro a
Hello! Adding my Acer E3-111-C9GN (Motherboard part NX.MNTEH.003) with
last BIOS 1.37 beign corrupted either. All u can change is a time.
Removing CMOS battery has no use. Tampering with anything does not help.
Crysis flash mode recovery does not proceed. Insyde tools from windows
doesnt proceed. D
@anthonywong - is the intention to respin just the 17.10 Ubuntu image
with a fix ... or will all flavours also be respun at the same time?
--
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/173
@anthonywong Thank you for your reply. Please allow me to say that after
contacting Lenovo to request support and notify them about the current
problem, they clearly stated that they are unaware of the issue and that
absolutely no report has been made to Lenovo. This is what worries me.
They refuse
@britgreek Even though we now have a kernel that can prevent the issue
happening, we are still finding the root cause with Lenovo, please be patient.
@fardinbehboud There is no software fix yet for machines that already have been
affected, no matter 17.10 or 18.04.
--
You received this bug noti
but I am still confused how to solve the problem for versions other than
17.1 because i am running 18.04 !
--
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:
Ubuntu 17.10 corr
Contacting the vendor and sending computers in, means paying a lot of
money for something that the end-users haven't caused on their hardware.
What is more, Lenovo clearly states that Linux is unsupported so, their
options are limited in terms of providing support. That is why they have
advised me
I have verified linux-image-4.13.0-21-generic on a 'good' Lenovo S20-30,
BIOS still works fine after rebooted many times so this kernel can
prevent the issue from happening.
As Thadeu and Marcin said above, this kernel is not meant to fix BIOS
that already have the issue. From our investigation wi
** Tags removed: verification-failed-artful
** Tags added: verification-done-artful
--
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:
Ubuntu 17.10 corrupting BIOS - many LENO
The fix on linux-image-4.13.0-21-generic will just prevent this from
happening on fresh installs. It will not repair systems that had already
been affected. BIOS recovery needs to be done some other way.
As we want to prevent other users from hitting this, a new artful image
will be generated with
Tried -proposed updates but bug still persist.
Lenovo y50-70 ubuntu 17.10
** Tags removed: verification-needed-artful
** Tags added: verification-failed-artful
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
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
Am i right that the fix is included in linux-image-4.13.0-21-generic?
This update just arrived on my ThinkPad Yoga S1, but sadly it didn't
change anything. Still bios changes disappear after booting Xubuntu
17.10.
--
You received this bug notification because you are a member of Kernel
Packages,
Any way to do this without access to Ubuntu? I have been locked out of
Ubuntu because something triggered the secure boot flag (got enabled)
and now the BIOS settings won't change. Booting now goes to grub-rescue
by default
--
You received this bug notification because you are a member of Kernel
** Also affects: linux (openSUSE)
Importance: Undecided
Status: New
--
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:
Ubuntu 17.10 corrupting BIOS - many LENOVO lap
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verifica
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-hwe-edge (Ubuntu)
Status: New => Confirmed
--
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/
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-oem (Ubuntu)
Status: New => Confirmed
--
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/17341
I tried to disable drivers putting intel_spi_platform, intel_spi, spi_nor, mtd
in blacklist (/etc/modprobe.d/blacklist.conf) but the bios bug is not resolved.
Lenovo y50-70 Ubuntu 17.10
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
** Changed in: linux (Ubuntu Xenial)
Status: New => Invalid
** Changed in: linux-hwe-edge (Ubuntu Xenial)
Status: New => Fix Committed
** Changed in: linux-oem (Ubuntu Xenial)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ker
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux-hwe-edge (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux-oem (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notifica
** Also affects: linux-oem (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-hwe-edge (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe-edge (Ubuntu Artful)
Status: New => Invalid
** Changed in: linux-oem (Ubuntu Artful)
Status:
** Changed in: linux (Ubuntu Artful)
Status: Confirmed => Fix Committed
--
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:
Ubuntu 17.10 corrupting BIOS - many LENOVO la
** Description changed:
SRU Justification
Impact: Many users are reporting issues with bios corruption with 17.10.
This seems to stem from enabling the intel-spi-* drivers in the kernel,
which don't appear to be ready for use on end-user machines.
Fix: Disable this driver.
Tes
** Description changed:
+ SRU Justification
+
+ Impact: Many users are reporting issues with bios corruption with 17.10.
+ This seems to stem from enabling the intel-spi-* drivers in the kernel,
+ which don't appear to be ready for use on end-user machines.
+
+ Fix: Disable this driver.
+
+ Tes
** Description changed:
Hi all,
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) US
** Description changed:
Hi all,
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) US
> It happened again right now, on another G40-30 Lenovo laptop, running
> Windows 10 and Ubuntu 16.04, both in legacy mode. As soon as we inserted
> an Ubuntu 17.10 live USB, the boot setup had the USB listed twice. One
> in legacy and another as EFI (I repeat, the OSs on that laptop are
> installe
It happened again right now, on another G40-30 Lenovo laptop, running
Windows 10 and Ubuntu 16.04, both in legacy mode. As soon as we inserted
an Ubuntu 17.10 live USB, the boot setup had the USB listed twice. One
in legacy and another as EFI (I repeat, the OSs on that laptop are
installed in legac
My Acer e5-471 is affected here. After installing ubuntu 17.10 my bios
won't save any changes except the date and time. It won't boot from
either HDD or USB. I still can boot from live cd though.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
Lenovo B50-80 is also affected by this issue.
--
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:
Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Status in linux pac
Also affects Lenovo Flex 3-1120 with BIOS C0CN31WW (v 4.5). Problem
presented after installing latest system updates for Ubuntu 17.10.
Symptoms are exactly the same; BIOS can be entered from system hotkey
F12, but changes to BIOS settings cannot be saved.
--
You received this bug notification bec
Lenovo z50-70 (20354) corrrupted bios, can modify only date and time.
Lastest version of bios allready installed.
I've only tried ubuntu 17.10. My luck is I've installed grub2, so from usb I
can load conf and boot all my operative systems. No way to do something for
rewrite from the laptop.
So, i
** Description changed:
Hi all,
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) US
in answer to post #120
I am not affected by ubuntu 17.1
I got affected by ubuntu 18.04(developers version).
in fact i start to install it 4 hours after release.
if there is a problem in ubuntu 17.1 development then it is logical also for
18.04 users.
--
You received this bug notification becau
@Steve Langasek (vorlon)
I am a user your talking about, "least one user reporting it after only booting
the live CD without
installing" - it's about me (#100 post). @Anthony Wong (and his teammates)
already contact me and with China Lenovo techics. At this moment my laptop is
in hands of serti
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
No, I've enabled virtualization technology just a bit before installing
Ubuntu, and Ubuntu did manage to write it's name into one of the boot
entries in my bios
Le 14 déc. 2017 22:30, "Pavel" <1734...@bugs.launchpad.net> a écrit :
> I'm wondering, is it realy ubuntu 17.10 bug, or it may be ju
On Thu, Dec 14, 2017 at 09:21:31PM -, Pavel wrote:
> I'm wondering, is it realy ubuntu 17.10 bug, or it may be just a
> symptom... and our BIOSes was corrupted erlier? Before we noticed the
> disease.
With so many users reporting this only after using Ubuntu 17.10, and at
least one user report
I'm wondering, is it realy ubuntu 17.10 bug, or it may be just a
symptom... and our BIOSes was corrupted erlier? Before we noticed the
disease.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
I am also affected. :(
4 days ego I was Installing ubuntu 18.04 developer version.on my Lenovo E40-70
I was running win 10 upgraded from 8.1, I erased my hard disk and tried to
install ubuntu with new partitioning from ubuntu install wizard. and while
installation I got 'grub efi boot error' an
I wonder what ist done to prevent any other Lenovo über to run into that
issue. As it is not yet sure if this issue can be solved, Canonical
should do something to make sure that no other Lenovo owner installs or
updates to 17.10, no matter if it's their fault at all.
--
You received this bug not
** Description changed:
Hi all,
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) US
@Eden bar: If you are asking me:
I got it fixed by local computer shop. By local I mean I found 3 in
Slovakia capable of changing BIOS chip and this one was the cheapest and
able to send courier to pick it up at bring it back with no hassle...
I beleive you can find a guy capable of replacing BIO
This is also affecting Alpha Litebooks. After installed Ubuntu 17.10 I
now get UEFI errors every time my computer starts and cannot restore
UEFI boot entries from command line, it's bricked. Luckily I can still
boot if I manually choose the grubx64 file on the EFI partition. My USB,
PXE boot option
Yoga 33-11 IBR affected - result is absolute brick without any signs of
life. Totally dead.
--
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:
Ubuntu 17.10 corrupting BIOS - m
+1 for this. Tried the BIOS recovery process for bricked laptop (Fn - R
with BIOS in USB) completed successfully but settings still remained and
can not be modified. Laptop is bricked. Device details below:
Product Name: Lenovo Y50-70
BIOS Version: 9ECN43WW(v3.03)
EC Version: 9EEC43WW(v3.03)
MTM
Hello Anthony,
My situation is:
Lenovo Ideapad Flex 10. Came with windows 8 installed and updated to windows
10. I then installed Ubuntu 14.04 as dual boot and had each release of Ubuntu
updated since 14.04.
I was dual booting using legacy for Ubuntu and UEFI for occasional access to
windows 1
Dear users,
We are treating this issue very seriously and sorry that this has
happened. We have been working with Lenovo in China at full speed since
last week to find out the root cause. Meanwhile, if you hit this issue,
please send me an email at anthony.w...@canonical.com with your laptop's
mod
Hi where you fix it?
--
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:
Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Status in linux package in Ubuntu:
Confirm
I got my y50-70 fixed today.
The FIX was to change the BIOS chip with a new one! Costs me 100€.
Good bye ubuntu, let the Windows headaches come back again. This is too
bad situation.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
My lenovo y7070 also dead any way to fix this?
--
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:
Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Status in linux pa
Lenovo B50-70 is affected too.
--
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:
Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Status in linux package in Ubuntu:
** Description changed:
Hi all,
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) US
** Description changed:
Hi all,
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) US
** Description changed:
Hi all,
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) US
** Description changed:
Hi all,
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) US
501 - 600 of 665 matches
Mail list logo
