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.
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
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
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.
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
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.
@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.
@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
@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
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
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
** 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
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
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.
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
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
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
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.
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.
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
** 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
** 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
** 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)
** 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
** 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.
** 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.
+
+
** 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)
** 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)
> 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
>
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
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
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
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
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,
** 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)
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
@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
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
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
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
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.
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'
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
** 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)
@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
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
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 -
+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)
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
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
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:
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
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
** 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)
** 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)
** 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)
** 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)
I wonder where's the guy who used to discover the critical bugs during
beta release...
Wait, it's me! Happily writing from Manjaro KDE
DM!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I just installed Ubuntu 17.10 on my Lenovo G50-80, and after intallation I
restarted and didn't see grub, so I wasn't able to load Windows, I tried Boot
Repair and it said that I wasn't on a EFI session or something... I went to the
BIOS, changed it back to UEFI, saved, booted, still the
Same problem here. Lenovo Ideapad Flex 10. Came with windows 8 installed and
updated to windows 10. Had Ubuntu 14.04 installed 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 10. Only recent
** 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)
@Kai-Heng Feng: Lenovo in Greece has been notified about the problem and
they have said that the factory will be notified. After telling them
that the Lenovo forums are full of posts referring to the issue, they
said that they did not know anything about it, as Lenovo Forums are not
part of the
** 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)
Has anyone filed an upstream bug yet?
Is Lenovo aware of 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
I am so done with ubuntu/linux. My Y50-70 goes to repair shop tomorrow
to have BIOS chip replaced, approx. cost 100+ euro. Wonderfull!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Can confirm for Z50-70. The "bug" occurs just after Ubuntu 17.10
installation and makes UEFI useless except for booting Ubuntu itself.
What is interesting for me is that, my prior linux installations did not
create a new label in the boot menu. After any os installation I would
get a boot entry
Lenovo y50-70, same problem. But i'm faced with a little different
situation. I didn't install 17.10, just booted in "Try Ubuntu 17.10"
mode. After that, i have decided to backup some files from existing
Windows OS. When there was all ready to go, i simply couldn't to boot
from usb with ubuntu
Lenovo Z51-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
** Changed in: linux (Ubuntu)
Importance: High => Critical
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Artful)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu Artful)
Status: New => Confirmed
**
I'm trying to use the bios flash procedure for lenovo (fn+R + power on)
, and it seems to read my usb key but i can't find the right file/the
right name for file to flash in the cmos. Someone know the right
combination filesystem/biosfile/filename to completely overwrite the
cmos? I'm trying this
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.
Hi, also happened to my lenovo y50-70 after upgrade ubuntu
--
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
Hi, I got the same problem as well. It is not just limited to bios
v3.03, I al so got that on bios v3.00. Bios flashing doesn't work in
anways, i have booting windows and when i try to update it to 3.03
nothing happens. It just passes to booting
--
You received this bug notification because you
Hi, i have the same issue on a lenovo y50-70. After upgrade to ubuntu 17.10 my
bios is corrupted and i can only boot from my hdd.
I'm trying to flash bios by lenovo crash(?) mode but i'm not able to do this .
Can anyone help me with this procedure?
--
You received this bug notification because
Workaround for reference to install Windows with the broken BIOS.
If you try to install through PXE Windows you'll see that it errors when
trying to bcdedit the entry to BIOS and the process fails.
A nasty workaround that works is:
- Create a raw Virtual Disk that points to the physical drive
-
@britgreek
The message "dpkg-query: no packages found matching linux" is exactly what it
means, because there is no package called "linux". What did you do when you saw
this message?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
** 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)
I'm on a Lenovo B40-70, I have this issue 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
Okay, I'm "unbricked" now as I can finally boot up my system but BIOS is
still corrupted.
I've instaled a new hard drive, with the help of a PXE environment I've
set up partitions so that matches my old drive configuration and
overriden the ESP UUID to the old drive UUID with gdisk and finally
Terminal message says "dpkg-query: no packages found matching linux" and
the same is mentioned in the apport log. What does this mean? I have
ubuntu 17.10 installed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The problem occurs both in Legacy and in UEFI mode, as I can see. My
dual boot setup is in legacy mode.
--
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
The same exact issue here I'm on Lenovo Y50-70 too & this happened just
after the installation of ubuntu 17.10
--
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
I see Tobia already submitted apport-collect 1734147.
Would you like a second set from me as well or is one set of data enough?
--
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
Regarding UEFI vs Legacy mode. If I understand it correctly it happened
in UEFI and not Legacy mode. I am not sure but I think my Lenovo Yoga 2
doesn't have Legacy "old school" BIOS and it only has UEFI. It has
"BIOS backport" feature but I don't know if that's what you mean. In
either case BIOS
Steve Langasek (vorlon) wrote 1 hour ago: #48
Based on the description of how the problem arises - Ubuntu 17.10 installed on
a system booted in legacy mode, not in UEFI mode.
The problem appeared to me in UEFI mode, not Legacy.
--
You received this bug notification because you are a member of
Logs sent via apport-collect
status changed
--
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
apport information
** Tags added: apport-collected wayland-session
** 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
@vorlon, sorry that I haven't mentioned that, but the Ubuntu 17.10 and
other distributions that I mentioned before were installed in the UEFI
mode every time.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Based on the description of how the problem arises - Ubuntu 17.10
installed on a system booted in legacy mode, not in UEFI mode, and the
problem showing up only after upgrade to Ubuntu 17.10 when Ubuntu 17.04
was running fine - it is likely that any problems here are in the Linux
kernel rather
301 - 393 of 393 matches
Mail list logo
