Opened Bug report https://bugs.launchpad.net/bugs/1938983
no solutions as yet.
Losing WiFi connectivity after an update to the latest HWE kernel :
Has this happened to anyone else and (more important) is there a non-complicated way out of this? What I found on Google on how to
back out of HWE seems a bit iffy.
To downgrade from HWE/OEM to GA kernel:
sudo apt install --install-recommends linux-generic
The Ubuntu LTS enablement (also called HWE or Hardware Enablement)
stacks provide newer kernel and X support for existing Ubuntu LTS
releases. These enablement stacks can be installed manually but are
also available when installing with Ubuntu LTS point release media.
These newer enablement stacks are meant for desktop and server and
even recommended for cloud or virtual images. However, if one wants
to remain on the original GA (General Availability) stacks, the
options are:
Henry Crun wrote:
Opened Bug report https://bugs.launchpad.net/bugs/1938983That msg says you have a USB rtl8188.
no solutions as yet.
Losing WiFi connectivity after an update to the latest HWE kernel :
My understanding is that you can use the command:
ubuntu-drivers list-oem
... to see if there are any meta packages listed.
Has this happened to anyone else and (more important) is there a non-complicated way out of this? What I found onI see a command to back out:
Google on how to
back out of HWE seems a bit iffy.
To downgrade from HWE/OEM to GA kernel:
sudo apt install --install-recommends linux-generic
There is a page:
https://wiki.ubuntu.com/Kernel/LTSEnablementStack
The Ubuntu LTS enablement (also called HWE or Hardware Enablement)
stacks provide newer kernel and X support for existing Ubuntu LTS
releases. These enablement stacks can be installed manually but are
also available when installing with Ubuntu LTS point release media.
These newer enablement stacks are meant for desktop and server and
even recommended for cloud or virtual images. However, if one wants
to remain on the original GA (General Availability) stacks, the
options are:
Whenever I have a network issue, I like to see what inxi says, because it tells me what I have and what driver.
$ inxi -Nn
Some Ub/s don't have the inxi script by default and some Ub/s don't have the universe repo by default. Personally I
don't know why that would be.
sudo add-apt-repository universe
(likewise multiverse, but that is less often needed)
Then update and install inxi.
root@alpha:/home/mike# /usr/bin/inxi -Nn
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
driver: r8168
IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: 4c:ed:fb:bf:7f:ac
Henry Crun wrote:
root@alpha:/home/mike# /usr/bin/inxi -Nn
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
driver: r8168
IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: 4c:ed:fb:bf:7f:ac
That is only showing your ethernet, not your usb wifi. There is also a discrepancy between its alleged gigabit and up
speed 100.
What does lsusb show?
It does not show the WiFi unless I plug in the USB card. But if I do
that, things start locking up (e.g ifconfig, wavemon, any sudo command)
and the only way out is to unplug the USB WIFi and reboot.
Being basically a lazy person, I think I'll just leave the WiFi
unplugged, and hope for a kernel fix.
Sorry if I appear ungrateful, becase I'm not - thank you for your input,
but I will just leave the Ethernet cable plugged in and wait for a fix.
After all, this is a bug of sorts, and 20.04 LTS should be supported (he
says hopefully)
Henry Crun wrote:
It does not show the WiFi unless I plug in the USB card. But if I do
that, things start locking up (e.g ifconfig, wavemon, any sudo command)
and the only way out is to unplug the USB WIFi and reboot.
Being basically a lazy person, I think I'll just leave the WiFi
unplugged, and hope for a kernel fix.
Sorry if I appear ungrateful, becase I'm not - thank you for your input,
but I will just leave the Ethernet cable plugged in and wait for a fix.
After all, this is a bug of sorts, and 20.04 LTS should be supported (he
says hopefully)
I was just having a discussion in another group about a msg I posted
over 6 mo ago about updating. I posted links to several different
articles pro and con on the updating business and the reflection on that
old msg caused me to read a msg I posted in a mint group related to Clem Lefebvre's admonitions in the Mint blog in favor of updating.
However, the Mint update tool is designed to encourage each user to dev
a 'strategy' for how they are going to update and in all cases are
encouraged to employ the Timeshift snapshot tool to enable easily
regressing to an earlier system.
Mike Easter wrote:
I was just having a discussion in another group about a msg I
posted over 6 mo ago about updating. I posted links to several
different articles pro and con on the updating business and the
reflection on that old msg caused me to read a msg I posted in a
mint group related to Clem Lefebvre's admonitions in the Mint blog
in favor of updating.
However, the Mint update tool is designed to encourage each user
to dev a 'strategy' for how they are going to update and in all
cases are encouraged to employ the Timeshift snapshot tool to
enable easily regressing to an earlier system.
That's assuming you can get the machine to boot to a desktop so you
can run Timeshift. If you can't (and remembering this thread is
about a problem with a new kernel), surely the first thing to try is
to pause boot and select the previous kernel to see if the machine
will continue to boot ok from that. If it does, you know where the
problem lies, and should perhaps just wait for the next version of
the kernel and hope that boots without problem.
If it doesn't, then Timeshift will be the way to go. It's a great
tool.
These newer HWE kernels are accompanied by a collection of userspace
tools closely tied to the kernel and hardware, specifically X
display enablement on newer graphics cards.
Ubuntu updated to kernel 5.11.0-25-generic and will no longer load.
It goes through the non graphic stuff and eventually goes to a
flashing _ . That _ eventually disappears and vertical green lines
flash on my screen.
If I tell GRUB to load kernel 5.8.0-63-generic-boot, Ubuntu 20.04.2
loads correctly. I am fairly new with Linux so please be patient with
me.
That is, it isn't clear at all to me why one would make that kernel
'upgrade' that apparently led to the breakage.
Mike Easter wrote:
That is, it isn't clear at all to me why one would make that kernel
'upgrade' that apparently led to the breakage.
Apparently the kernel update had a 'security' label on it.
Mike Easter wrote:
Mike Easter wrote:
That is, it isn't clear at all to me why one would make that kernel
'upgrade' that apparently led to the breakage.
Apparently the kernel update had a 'security' label on it.
Where does that label appear?
Package: linux-image-5.11.0-25-generic (5.11.0-25.27~20.04.1) [security]
I just had the Mint Update Manager let me know a kernel update is
available (5.4.0-81.91. I'm still using LM 20.1). Of course, as usual it
says "No changelog available" when you click on that tab on the lower
half of the window. There is a changelog available, but getting to it is
not exactly transparent, and when you've got it be prepared for a lot of reading!
In the Update Manager window:
View | Linux kernels | Continue | (Select kernel version group) |
(Left-click specific kernel) | Left-click on changelog
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 293 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 224:32:57 |
| Calls: | 6,623 |
| Calls today: | 5 |
| Files: | 12,171 |
| Messages: | 5,318,481 |