Important Alert
Do not upgrade your MX 17 or MX18 system installed or live until further notice. A problem with a kernel upgrade has occurred. A fix will be posted when available.
I unfortunately upgraded today, as there is no alert messages in MXPackae Manager so I didnt see the alert until reading it on the usergroup.
But didnt reboot yet.
What is the nature of the problem and how can I undo the kernel upgrade without breaking things.
Luckily I didnt reboot.
Would be great to get some help to get the previous kernel reinstalled if the new kernel is going to break the system.
Status: Before uninstall, this module version was ACTIVE on this kernel.
wl.ko:
- Uninstallation
- Deleting from: /lib/modules/4.19.0-1-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod...
Backing up initrd.img-4.19.0-1-amd64 to /boot/initrd.img-4.19.0-1-amd64.old-dkms
Making new initrd.img-4.19.0-1-amd64
(If next boot fails, revert to initrd.img-4.19.0-1-amd64.old-dkms image)
update-initramfs........
Status: Before uninstall, this module version was ACTIVE on this kernel.
wl.ko:
- Uninstallation
- Deleting from: /lib/modules/4.19.0-5-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod.....
Backing up initrd.img-4.19.0-5-amd64 to /boot/initrd.img-4.19.0-5-amd64.old-dkms
Making new initrd.img-4.19.0-5-amd64
(If next boot fails, revert to initrd.img-4.19.0-5-amd64.old-dkms image)
update-initramfs........
DKMS: uninstall completed.
------------------------------
Deleting module version: 6.30.223.271
completely from the DKMS tree.
------------------------------
Done.
Loading new broadcom-sta-6.30.223.271 DKMS files...
Building for 4.19.0-1-amd64 4.19.0-5-amd64
Building initial module for 4.19.0-1-amd64
Done.
wl:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-1-amd64/updates/dkms/
depmod...
Backing up initrd.img-4.19.0-1-amd64 to /boot/initrd.img-4.19.0-1-amd64.old-dkms
Making new initrd.img-4.19.0-1-amd64
(If next boot fails, revert to initrd.img-4.19.0-1-amd64.old-dkms image)
update-initramfs........
DKMS: install completed.
Building initial module for 4.19.0-5-amd64
Done.
wl:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-5-amd64/updates/dkms/
depmod...
Backing up initrd.img-4.19.0-5-amd64 to /boot/initrd.img-4.19.0-5-amd64.old-dkms
Making new initrd.img-4.19.0-5-amd64
(If next boot fails, revert to initrd.img-4.19.0-5-amd64.old-dkms image)
update-initramfs........
Status: Before uninstall, this module version was ACTIVE on this kernel.
ndiswrapper.ko:
- Uninstallation
- Deleting from: /lib/modules/4.19.0-1-amd64/updates/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
/usr/sbin/dkms: line 2007: echo: write error: Broken pipe
/usr/sbin/dkms: line 2009: echo: write error: Broken pipe
Status: Before uninstall, this module version was ACTIVE on this kernel.
ndiswrapper.ko:
- Uninstallation
- Deleting from: /lib/modules/4.19.0-5-amd64/updates/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod...
DKMS: uninstall completed.
------------------------------
Deleting module version: 1.61
completely from the DKMS tree.
------------------------------
Done.
Loading new ndiswrapper-1.61 DKMS files...
Building for 4.19.0-1-amd64 4.19.0-5-amd64
Building initial module for 4.19.0-1-amd64
Done.
ndiswrapper:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-1-amd64/updates/
depmod...
DKMS: install completed.
Building initial module for 4.19.0-5-amd64
Done.
ndiswrapper:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-5-amd64/updates/
Status: Before uninstall, this module version was ACTIVE on this kernel.
vhba.ko:
- Uninstallation
- Deleting from: /lib/modules/4.19.0-1-amd64/
rmdir: failed to remove '': No such file or directory
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
/usr/sbin/dkms: line 2007: echo: write error: Broken pipe
/usr/sbin/dkms: line 2009: echo: write error: Broken pipe
Status: Before uninstall, this module version was ACTIVE on this kernel.
vhba.ko:
- Uninstallation
- Deleting from: /lib/modules/4.19.0-5-amd64/kernel/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod...
DKMS: uninstall completed.
------------------------------
Deleting module version: 20170610
completely from the DKMS tree.
------------------------------
Done.
modprobe: FATAL: Module vhba is in use.
WARNING: Failed to unload running module.
Loading new vhba-20170610 DKMS files...
Building for 4.19.0-1-amd64 4.19.0-5-amd64
Building initial module for 4.19.0-1-amd64
Done.
vhba:
Running module version sanity check.
Good news! Module version 20170610 for vhba.ko
exactly matches what is already found in kernel 4.19.0-1-amd64.
DKMS will not replace this module.
You may override by specifying --force.
depmod...
DKMS: install completed.
Building initial module for 4.19.0-5-amd64
Done.
vhba:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-5-amd64/kernel/updates/dkms/
depmod...
DKMS: install completed.
modprobe: FATAL: Module vhba is in use.
WARNING: Failed to unload running module.
WARNING: Configuration already exists.
Please place the text output within the < / > brackets that you can see in the editing toolbar in the forum.
If you already installed the updates to the 4.19 kernel, you won't see that the kernel has been removed in Synaptic. The removed package was an update to the same 4.19 kernel with the same version number (that was what caused the issue).
So since you have already installed the updates, you can only rebuild modules for this existing kernel in your system and/or install another kernel (DEbian Stable 4.9, MXPI Popular apps) or the latest 5.1+ liquorix (MXPI Test Repo).
If a user hadn't yet installed all the updates before the hooha, when they now check for updates, they won't find any update to that 4.19 kernel in the list of updates, which means they are still on their old, no-issue 4.19 kernel.
But I'm afraid I don't know enough to read your output. YOu'll have to wait for the experts to wake up in their timezone.
Have you even rebooted to see if it works? If not, I suggest you take the opportunity to install another kernel first, as suggested above. Then reboot and see what happens. If it doesn't work, you'll have another kernel(s) to boot into.
BTW, I sometimes get alarming warnings when I install new liquorix kernels, but after rebooting, it's fine.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
zimbodel wrote: ↑Fri Jun 28, 2019 10:12 pm
I dont want to boot as what I am doing on this system is too crytical to risk having downtime.
From what you say, it seems that all the advice posted is not going to help...
Ok, so where do I find an older(previous) or the correct kernel. ?
I have no idea where to find it.
I guess I need a link and instructi9ons to the kernel just before this broken one.
This is what is running, and should be the old kernel that worked spectacularly well.
Linux version 4.19.0-1-amd64 (stevep@mxlinux.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP Debian 4.19.5-2~mx17+1 (2018-12-12)
So how do I get back to this.
The problem with the 4.19.05 kernel was resolved over a week ago and the red alert message removed from the forum. There's an announcement in the MX News & Announcements forum.
If you still want to change kernels just install the one you want, then in MX Boot Options check the checkbox by "Enable saving last boot choice" then click Apply then Close, reboot, and select the kernel you want from the grub boot menu.
If you want to prevent a kernel from being updated (not recommended as you'll miss out on critical security and bugfix patches) you can easily do that in Synaptic Package Manager. Search for your kernel, which should be named starting with "linux-image", select it, then click the Package dropdown menu and click Lock Version.
The issue with 4.19.05 was a one time "oopsie" by the upstream (Debian Stable.) This is the first time in almost 20 years of using Linux that I've seen this happen with a stable kernel from a reliable source. I wouldn't worry about it happening again as the odds are slim to none. So feel free to install the recommended updates and/or reboot whenever you want. It's safe now.
Is there any way to upgrade to the new kernel that has been corrected ? given I still have the defect one installed ?
If it is as easy as going to Mx-package manager and just install the kernel update it might be the easiest way.
I went to look in the package manager and I could only find linu8x=-source 4.19+105 as upgradeable which is listed as linux kernel source. this was in the MX Test Repo.
Do you maybe have the exact kernel version I should upgrade to unless debian foolishly named it exact the same which would be a disaster. then I will have to downgrade to my previous version as listed above in a previous post.
What I have in MX-Packagemanager which is upgradeable is: Stable Repo: Linux-source-4.9 Version 4.9.168-1+deb9u3 Mx Test Repo; 4.19+105 Debian Backports: 4.19+105~bp09+1
Why is the kernel in the test repo a lower issue number that the stable !? Doesnt seem right !
Note if I run apt list upgradeable I get
linux-headers-4.9.0-9-amd64/stable 4.9.168-1+deb9u3 amd64 [upgradable from: 4.9.168-1+deb9u2]
linux-headers-4.9.0-9-common/stable,stable 4.9.168-1+deb9u3 all [upgradable from: 4.9.168-1+deb9u2]
linux-kbuild-4.9/stable 4.9.168-1+deb9u3 amd64 [upgradable from: 4.9.168-1+deb9u2]
linux-source-4.9/stable,stable 4.9.168-1+deb9u3 all [upgradable from: 4.9.168-1+deb9u2]
Would upgrading to stable 4.9.168-1+deb9u3 solve the problem ??
What should my strategy be for the three options, back or forward ?
Kernel problems are serious an difficult to fix once it freezes, so I rather ask dead dumb questions to make sure I get the correct kernel installed that will at least boot.
I have no idea what problem you're trying to solve by changing to an older kernel, since you didn't mention that something on your computer wasn't working.
The MX Update Manager will upgrade your 4.19.0-1 kernel to 4.19.0-5 for you as long as you haven't locked or pinned the 0-1 kernel in Synaptic as I explained how earlier. If you did, just un-pin it.
