There are hints that the Ubuntu kernel update to K5.15.0-112 can cause severe system problems to users having specific AMD GPUs.
"AMD Picasso/Raven 2 [Radeon Vega Series / Radeon Mobile Series]"
"AMD Raven Ridge [Radeon Vega Series / Radeon Mobile Series]"
Update 2024-07-16: Kernel update K5.15.0-116 holds the fix for the regression introduced in K5.15.0-112.
Update 2024-06-26:
There are hints that the most recent Ubuntu kernel update K5.15.0-113 does not hold any bugfix for the reported AMD graphics problems, yet.
Threads about startup problems caused by kernel 5.15.0-112:
.
Click to expand the list of threads
Failed to boot after upgarding to 5.15.0-112-generic from 5.15.0-107-generic viewtopic.php?t=421441
(specific AMD video card: "AMD Picasso/Raven 2 [Radeon Vega Series / Radeon Mobile Series]")
In case K5.15.0-112 has been installed already:
1. Power on you machine.
2. Invoke the Grub boot menu.
3. In the Grub boot menu select "Advanced options for Linux Mint 21.3".
4. In the "Advanced options for Linux Mint 21.3" select the previous kernel, not 5.15.0-112. (5.15.0-107 or lower)
5. Boot the selected previous kernel.
6. If the system comes up properly, launch Update Manager. Go to "View" => "Kernels".
7. Select kernel 5.15.0-112 and click on [Remove].
8. Once the kernel 5.15.0-112 has been removed, UM will refresh the list of available updates.
9. UM will offer kernel 5.15.0-112 for installation again. Do not install it. Instead proceed as explained in the section below.
.
In case K5.15.0-112 has not been installed, yet:
Those of you, who have not installed kernel update K5.15.0-112, yet, may like to blacklist the current kernel update temporarily.
Temporarily means: either until yet another update will have been published, which is confirmed to resolve any regression introduced by K5.15.0-112, or until it has been found out that only specific hardware is affected and that your hardware is unaffected.
Steps how to do so in the post below.
Last edited by karlchen on Tue Jul 16, 2024 5:58 pm, edited 9 times in total.
Reason:Kernel update K5.15.0-116 holds the fix for the regression introduced in K5.15.0-112.
The people of Alderaan have been desperately fighting back the clone warriors sent out by the unscrupulous Sith Lord Palpatine for 944 days now. Might Just Take Your Life
Linux Mint Update Manage presents a list of available software updates to you for installation.
Among them kernel update K5.15.0-112.122
.
.
Block this specific kernel update.
Right-click on the line displaying "Linux kernel 5.15.0-112.122" and select "Ignore the current update for this package"
.
.
Note:
"Ignore the current update for this package" will blacklist precisely this update to K5.15.0-112.122. Future updates to higher versions will be offered again.
"Ignore all future updates for this package" will blacklist all future kernel updates forever. This will be a bit too drastic, because a future kernel update may fix the regression introduced by K5.15.0-112.122 and you may want to be offered such a future kernel update for installation in the future.
.
Update Manager will refresh the list of available updates.
This will take a few seconds.
It will then display the list again. Note:
"Linux kernel 5.15.0-112.122" will no longer be displayed, because it has just been blocked.
.
.
Where has it gone?
Click on "Edit" => "Preferences", then on the tab "Packages".
In the lower part of the screen you see the kernel update entries, which you have just blocked.
.
.
You can revert your action by selecting the 2 entries "linux=5.15.0-112.122" and "linux-meta=5.15.0-112.122" and clicking on the [-] icon.
.
Beware: The Update Manager will not offer the current kernel update any longer. And it will not install it. - Unless you revoke the blacklist operation.
The terminal command sudo apt upgrade, however, does not honour the Update Manager blacklist, it does not even know it.
Therefore in case you execute sudo apt upgrade, it will want to install kernel update 5.15.0-112 .
Therefore use Update Manager to install available updates only.
.
The Potential Update Manager "Apply Updates Automatically" Pitfall
The warning in blue colour above plus a nasty issue where kernel 5.15.0-112 kept on returning mysteriously shortly after having been uninstalled in Update Manager reminded me to add the following warning/instruction here:
Launch Update Manager. Inside Update Manager go to EditPreferences.
Inside the Preferences window click on the Automation tab.
In this dialogue box, Update Manager can be instructed to do specific operations automatically.
With respect to the blacklisted kernel 5.15.0-112 only the topmost section titled Packages Updates is relevant.
In case the setting Apply updates automatically has been enabled (disabled in the screenshot), then you must click on the wide button below it, labelled Export blacklist to /etc/mintupdate.blacklist.
Why? You have blacklisted kernel K5.15.0-112 inside Update Manager. This blacklist is located inside your personal profile.
If Apply updates automatically has been enabled, the automatic update installation is done by user root. root does not check user profiles for blacklists. Therefore exporting your personal blacklist into the file /etc/mintupdate.blacklist will make automatic software updates honour your blacklist as well.
If you do not synchronize your personal blacklist with the file /etc/mintupdate.blacklist and if you have enabled "Apply updates automatically" at the same time, the automatic updates will keep on re-installing kernel K5.15.0-112.
Of course, you can also disable Apply updates automatically. No blacklist conflict and no returning K5.15.0-112 if you do so.
Last edited by karlchen on Mon Jun 10, 2024 8:46 am, edited 1 time in total.
Reason:Added section about potentially returning blacklisted kernel, in case personal blacklist has not been exported to /etc/mintupdate.blacklist
The people of Alderaan have been desperately fighting back the clone warriors sent out by the unscrupulous Sith Lord Palpatine for 944 days now. Might Just Take Your Life
That sounds like a different issue from the ones with the 5.15 kernels. I checked the log of one of the 5.15 problems and it is an issue with graphics which makes it appear the system is not booting (it is booting). Freezing of the operating system while using it is not what is happening to those with 5.15 kernel issues, but that is what the one person with 6.5 is experiencing.
Hello, SMG.
Kernel 6.5.0-35 removed from this announcement (thread).
Karl
The people of Alderaan have been desperately fighting back the clone warriors sent out by the unscrupulous Sith Lord Palpatine for 944 days now. Might Just Take Your Life
Thank god it is not related to mu pc gettting bad, but I won the jackpot after the update to K5.15.0-112
MY HP has:
"AMD Picasso/Raven 2 [Radeon Vega Series / Radeon Mobile Series]"
"AMD Raven Ridge [Radeon Vega Series / Radeon Mobile Series]"
Would not boot up, so reverting to a previous kernelversion solved it. But is a huge regression, I am sure the gods will fix it soon. Thanks for the support!
Foretelling the future is never 100% reliable. Yet, based on experience, I will word it like this:
It is pretty unlikely that any future software update will depend on K5.15.0-112. What is imaginable is that in future some piece of software, most likely some hardware driver e.g., might require kernel K5.15.0-112 or higher.
Yet, blocking K5.15.0-112 is meant as a temporary measure. This means K5.15.0-112 will be skipped, not installed, hoping and waiting for a future kernel update like e.g. K5.15.0-113 or higher to fix the regression introduced by K5.15.0-112. As soon as such a fixed kernel update is available, installing kernel updates can be done again.
Karl
The people of Alderaan have been desperately fighting back the clone warriors sent out by the unscrupulous Sith Lord Palpatine for 944 days now. Might Just Take Your Life
Hello, I also had problems today after kernel update to 5.15.0 - 112.
Linux Mint did not boot anymore. Black screen
With recoverery it worked. I have downgraded to 5.15.0 - 91
Info about my machine:
HP ProBook 455R G6
CPU: AMD Ryzen 5 3500U with Radeon Vega Mobile
karlchen wrote: ⤴Fri Jun 07, 2024 8:25 am... In case the setting Apply updates automatically has been enabled (disabled in the screenshot), then you must click on the wide button below it, labelled Export blacklist to /etc/mintupdate.blacklist.
Why? You have blacklisted kernel K5.15.0-112 inside Update Manager. This blacklist is located inside your personal profile.
If Apply updates automatically has been enabled, the automatic update installation is done by user root. root does not check user profiles for blacklists. Therefore exporting your personal blacklist into the file /etc/mintupdate.blacklist will make automatic software updates honour your blacklist as well.
If you do not synchronize your personal blacklist with the file /etc/mintupdate.blacklist and if you have enabled "Apply updates automatically" at the same time, the automatic updates will keep on re-installing kernel K5.15.0-112.
Of course, you can also disable Apply updates automatically. No blacklist conflict and no returning K5.15.0-112 if you do so.
Unfortunately, the /etc/mintupdate.blacklist part of this procedure does not work. I have done this and it still reinstalls. I have gone into the etc directory the file does not exist/not created . It keeps on reinstalling 112. Therefore, I am unable to use autoupdates so am updating manually which is the only way to stop 112 being installed.
Last edited by SMG on Wed Jun 12, 2024 3:26 pm, edited 1 time in total.
Reason:Shortened quote to the applicable part being referenced in the response.
I have mint installed on a computer with an AMD 3750H and this kernel update caused issues for me.
Initially, I thought it was failing to boot due to a blank black screen after the POST screen. Normally, my computer goes from POST to a LM splash screen. I followed some instructions online about using a Live USB to get to a terminal and reinstall the boot loader. This did not fix my issue, but it did make grub show up after the POST screen so I was able to go into recovery mode and then resume to normal boot from there. I thought things were back to normal as I was able to get back to my regular desktop and all of my files were intact. I surfed the web for a few minutes and tried to watch a video online when I noticed I had no sound and my video playback was like watching a slideshow. I opened the system monitor and clicked on the resource tab to find my CPU pegged at 100% utilization yet none of the processes showed high CPU usage. This led me to discover that I was running without hardware acceleration so maybe the kernel was the issue. I rolled back to 5.15.0-107 rebooted and was met by that beautiful LM splash screen. I logged in and CPU usage was back to normal. Video and sound are working again as well. I temporarily blocked this update like the OP instructed. I am not sure if grub continue showing up after POST, but that is a small price to pay to be back up and running again.
I am pretty new to the world of Linux, but I have been daily driving Mint (mostly just firefox) for a year or two now and this forum has saved my bacon more times than I can count so I finally decided to register so I can post a big THANK YOU to everyone that helps answer questions. This is a fantastic resource.
Last edited by spacerazor on Fri Jun 14, 2024 1:49 pm, edited 1 time in total.
spacerazor wrote: ⤴Fri Jun 14, 2024 1:48 pm...This did not fix my issue, but it did make grub show up after the POST screen so I was able to go into recovery mode and then resume to normal boot from there. I thought things were back to normal ...
Welcome to the forum, spacerazor.
They were not back to normal. You booted in recovery mode which automatically adds the nomodeset kernel parameter and that disables hardware acceleration. That is why you were having issues.
What is the output of inxi -Gx? You can run that in a terminal or you can go to the System Reports app, click the System Information tab on the left, and copy the Graphics section here.
SMG wrote: ⤴Fri Jun 14, 2024 2:33 pm
What is the output of inxi -Gx? You can run that in a terminal or you can go to the System Reports app, click the System Information tab on the left, and copy the Graphics section here.
This is my current inxi -Gx output. I didn't run this command with the 112 kernel. If you think it will be a benefit to others, I can update the kernel and run it again.
spacerazor wrote: ⤴Fri Jun 14, 2024 2:41 pmThis is my current inxi -Gx output. I didn't run this command with the 112 kernel. If you think it will be a benefit to others, I can update the kernel and run it again.
I think you will run into the problem again if you try the 112 kernel. Your computer has the same graphics as other who have run into this issue. Your output verifies that.
The information at the beginning of this topic explains the options to put the -112 kernel on hold so you can wait and try again with a newer one. We do not know when the fix will come through so it is possible the next kernel or two might also have the issue.
