The Change to Plasma 6.2.0 and shortly after to 2024-04 LTE went flawlessly.
I got an upgrade notice today with a new kernel (6.8.0.47.47) and installed it. The system boots to a black screen now. The OS is running, I can log in using putty and do an orderly shut down that way. In GRUB, I went back and booted using 6.8.0-45-generic and it works fine.
GRUB runs OK. The SDDM graphic login screen appears, but when I log in, the sceeen just goes black and stays that way.
My system
2024-04 LTE
Plasma 6.2.0 under X11
KDE Frameworks 6.6.0
QT Vesion 8.7.2
NVIDIA Graphics card
Here was what I got with todayās upgradeā¦
binutils (2.42-4ubuntu2) to 2.42-4ubuntu2.3
binutils-common (2.42-4ubuntu2) to 2.42-4ubuntu2.3
binutils-x86-64-linux-gnu (2.42-4ubuntu2) to 2.42-4ubuntu2.3
gcc-14-base (14-20240412-0ubuntu1) to 14.2.0-4ubuntu2~24.04
gcc-14-base:i386 (14-20240412-0ubuntu1) to 14.2.0-4ubuntu2~24.04
libasan8 (14-20240412-0ubuntu1) to 14.2.0-4ubuntu2~24.04
libatomic1 (14-20240412-0ubuntu1) to 14.2.0-4ubuntu2~24.04
libbinutils (2.42-4ubuntu2) to 2.42-4ubuntu2.3
libcc1-0 (14-20240412-0ubuntu1) to 14.2.0-4ubuntu2~24.04
libctf-nobfd0 (2.42-4ubuntu2) to 2.42-4ubuntu2.3
libctf0 (2.42-4ubuntu2) to 2.42-4ubuntu2.3
libgcc-s1 (14-20240412-0ubuntu1) to 14.2.0-4ubuntu2~24.04
libgcc-s1:i386 (14-20240412-0ubuntu1) to 14.2.0-4ubuntu2~24.04
libgfortran5 (14-20240412-0ubuntu1) to 14.2.0-4ubuntu2~24.04
libgomp1 (14-20240412-0ubuntu1) to 14.2.0-4ubuntu2~24.04
libgprofng0 (2.42-4ubuntu2) to 2.42-4ubuntu2.3
libhwasan0 (14-20240412-0ubuntu1) to 14.2.0-4ubuntu2~24.04
libitm1 (14-20240412-0ubuntu1) to 14.2.0-4ubuntu2~24.04
liblsan0 (14-20240412-0ubuntu1) to 14.2.0-4ubuntu2~24.04
libquadmath0 (14-20240412-0ubuntu1) to 14.2.0-4ubuntu2~24.04
libsframe1 (2.42-4ubuntu2) to 2.42-4ubuntu2.3
libstdc++6 (14-20240412-0ubuntu1) to 14.2.0-4ubuntu2~24.04
libtsan2 (14-20240412-0ubuntu1) to 14.2.0-4ubuntu2~24.04
libubsan1 (14-20240412-0ubuntu1) to 14.2.0-4ubuntu2~24.04
linux-generic (6.8.0-45.45) to 6.8.0-47.47
linux-generic-hwe-24.04 (6.8.0-45.45) to 6.8.0-47.47
linux-headers-generic (6.8.0-45.45) to 6.8.0-47.47
linux-headers-generic-hwe-24.04 (6.8.0-45.45) to 6.8.0-47.47
linux-image-generic (6.8.0-45.45) to 6.8.0-47.47
linux-image-generic-hwe-24.04 (6.8.0-45.45) to 6.8.0-47.47
linux-libc-dev (6.8.0-45.45) to 6.8.0-47.47
linux-tools-common (6.8.0-45.45) to 6.8.0-47.47
nano (7.2-2build1) to 7.2-2ubuntu0.1
Installed the following packages:
linux-headers-6.8.0-47 (6.8.0-47.47)
linux-headers-6.8.0-47-generic (6.8.0-47.47)
linux-image-6.8.0-47-generic (6.8.0-47.47)
linux-modules-6.8.0-47-generic (6.8.0-47.47)
linux-modules-extra-6.8.0-47-generic (6.8.0-47.47)
linux-tools-6.8.0-47 (6.8.0-47.47)
linux-tools-6.8.0-47-generic (6.8.0-47.47)
Wonder if anyone else has had a problem, or am I alone on this ??
Maybe try reinstalling your Nvidia graphics drivers? I think I had this issue when I was an Nvidia user. Iād upgrade to the new kernel, and then my drivers would break. It was a pain (and thatās when I used X11 no less). So, Iām not surprised that Nvidia still causes these kinds of problems.
Also, the older the Nvidia graphics card is, the harder it will be to use a newer kernel. I learned that with my momās old Thinkpad laptop. I couldnāt use the old driver anymore with the new kernel. So, the only option was to get second hand laptop for her with AMD graphics.
I had enough of Nvidiaās nonsense and switched to AMD or Intel graphics on all of my computers due to their drivers being better optimized for Linux users. That, and no messing with drivers. Just plug it in and forget it for the most part.
Also, still using X11? Might want switch over to Wayland eventually (as X11 is on its last leg). But Iāll tell you that Nvidia still doesnāt make it easy for Nvidia users to use Wayland. So, you may want to start weighing your options; if anything, to have less headaches whenever you upgrade to a newer kernel. And Nvidia is still a barrier when it comes to a headache free setup.
Anyway, just ctrl+alt+f2 into a new tty. Uninstall the Nvidia drivers using apt, and then reinstall them and reboot. Do that while using the latest kernel. See if that works.
And if all else fails, revert back to the old kernel for now.
OK thanks for the replyā¦ I posted this in case this was a general problem, but I guess it;s unique to meā¦
I really am considering losing the NVIDIA cardā¦ Iāve been running Neon since pretty well the beginning and the only issues Iāve had with upgrades and changes were video related.
Iām running X because I canāt run Waylandā¦ It locks up the processorā¦ All cores run at 100% I was running it at one time, but on a previous upgrade, it broke. I guess if I worked hard enough I could get Wayland running, but Iām not up to the work just nowā¦ X is running fine
I think the writing is on the wall to be more than just considering swapping GPUs at this point. And I say this as someone who had their own experiences with Nvidia GPUs on Linux for 5 of the years I have been on Linux for. And Iāve been using Linux as my daily for over 8 years. And what I learned is to avoid Nvidia like the plague. That, and avoiding Realtek as much as I can (namely the cheap WiFi cards and audio chipsets; shockingly enough, their LAN adapters work well).
Well, up to you. Iām just saying that X11 is dead. So, swap out the Nvidia card and switch to an AMD one if you want actual support for Wayland (and to have better drivers). Because as much as people say that Nvidia has gotten better, and that Nvidia is open sourcing their drivers for newer cards on Linux, I still consider Nvidia problematic.
The Nvidia card is the source of much of your problems. That much I can surmise already. And if itās a really old Nvidia card, youāre going to end up having more problems along the way. As I mentioned, the older the card, and if there are no more up to date drivers being pushed out by Nvidia, then your GPU wonāt work at all should choose to use an up to date kernel. Because the older drivers wonāt work with the new kernel.
Anyway, itās very simple:
Linux: AMD = Good, Intel = Good, Nvidia = Bad
Windows: AMD = bad, Intel = Good, Nvidia = Good
You have to adjust your hardware depending on the OS you use. In turn, this means less headaches for you.
Iāve got this same issue, but Iām on AMD. I have an AMD RX 6950 XT which works fine on every other edition of Ubuntu, but every distro Iāve tried has failed to have working graphics drivers for this card. sadly KDE Neon has finally followed suit in joining 2024 and now I have a bricked OS again.
This issue is common with a Linux and Nvidia pairing in general. If you eliminate that (Nvidia), youāll solve your issues regarding this particular issue.
Choosing hardware that is much more compatible makes for a better outcome in terms of stability.
And this is why I keep telling people to make a backup of their OS drive before upgrading to the newer Ubuntu base.
I made a backup of my system recently and restored the image to a virtual machine just to test how the upgrade would go. So far, it was rough. The upgrader even crashed just before configuring packages. So, I had to run dpkg --configure -a to configure them. I even had to run apt autoremove to clean up the obsolete packing afterward.
So, given this, I am just going to stick to 22.04 for now until the kinks get worked out.
Again, this is why I say backing up is paramount. Because a huge upgrade like this can cause serious problems. And this advice isnāt just for Linux users. Iāll even say the same thing to Windows users.
Also, Iād like to point out that youād be wise to keep your OS partition and your user profile separate. That, and keep your data on a separate drive in your system if you can. Doing this reduces the amount of time to backup and restore the partition that the OS is on. But also, this ensures your data doesnāt get lost (make backups of your data as well on an external drive too!).
Anyway, if you want a full drive backup solution, I recommend Rescuezilla. Itās a fork of Clonezilla that uses a GUI.
As for your graphics driver issue, youāll need to make sure to upgrade the Mesa packages that provides drivers for your GPU. Also, upgrade your kernel to the latest one. That generally fixes the issue.
You can do this by switching over to another tty session (ctrl+alt+f2 and then log in), running apt update, then apt upgrade. Or, in Neonās case, pkcon refresh and then pkcon update
Sometimes, Iāve had to do that to fix this issue of lacking drivers for newer hardware. But this is why I tend to avoid getting really new hardware. And another example is GPUs like the Nvidia 4090ās catching fire.
I have the same issue on a stock Dell Latitude 7400 laptop. I donāt think it has anything to do with the Nvidia gpu as this old laptop is running an Intel UHD 620. Reverting back to kernel version 6.8.0-45 is the only way I could see anything.
Iām not sure. Neon had another update today, and it updated the kernel again to the .47 version. Back to a black screen. Had to restart in advanced mode and choose .46 version and ran the pkg command to scan and reinstall any broken packages. The scan found three packages it āfixedā. Restarted again once I could see the screen. It then said the computer was running in safe graphic mode. I restarted after the fix and now it is using the .47 version. So, it seems to be fixed, but we will see.
KDE Neon user here with the Canonical Launchpad PPA added re: Nvidia drivers. Been running Nvidia for as long as Iāve been running KDE Neon (about five years now), and Iāve never once had an issue with drivers with the exception of the update to 24.04 - Which was resolved quite easily.
Just updated to KDE Neon 6.2.1 running kernel 6.8.0-47-generic without issue.
The history of the last kernel update shows 6.8.0-47.47 was installed. The full name appears to be: linux-generic-hwe-24.04_6.8.0-47.47_amd64.deb
But uname -a shows 6.8.0-47-generic so they must be the same.
For what itās worth, I have an AMD graphics card literally in the mailā¦ Iām getting rid of the old NVIDIA cardā¦ Hopefully that will solve my problems.
same problem here, basically fried my fiances pc.
i feel like ive tried a ton to fix it, so im trying to install a the newest kde iso off of usb - cant for the life of me get it to work, it constantly crashes on step 1 (partitioning the chosen drive), no matter the drive chosen. been going through the entire book of chatgpt suggestions and cannot make this pc work at allā¦
Please let us know if this works - or not?
I have a similar problem with a Dell Latitude E6520 and on-board nvidia graphics - so I canāt change that!
Everything was working fine until the 6.8.0-47 kernel update - which gave the black screen - so I have reverted to -44 using the info supplied at āaddictive tips dot comā with the title ādowngrade-ubuntu-kernelā. For some reason -45 was unavailable to me as an option even though it was the previous working version. In future I wonāt take the prompt to delete the old files quite so soon.
I am hoping the next kernel iteration will fix thingsā¦
i have solved this problem. Ubuntu comes with some random kernel that is going to be installed on your hardware. what you do is this.
start with:
sudo apt update && sudo apt install -y linux-generic
next:
sudo nano /etc/default/grub
next:
edit GRUB_DEFAULT=0 to
GRUB_DEFAULT=āAdvanced options for Ubuntu>Ubuntu, with Linux ā
for exaplme: GRUB_DEFAULT=āAdvanced options for Ubuntu>Ubuntu, with Linux 5.15.0-76-genericā
then save and exit
next:
sudo update-grub
and last one: sudo reboot
no more freezing and no more black screen. You might need to reload your nvidia drivers to make them run on a nwe kernel. for this you do this:
dpkg -l | grep nvidia
next
dpkg -l | grep linux-modules-nvidia
next
sudo apt install linux-headers-$(uname -r)
next
sudo apt remove --purge ā^nvidia-.*ā
next
sudo apt install nvidia-driver-550
(or any other desired driver)
next
sudo modprobe nvidia
next
sudo dmesg | grep nvidia
next
sudo reboot
So, I gave up trying to get my nVidia GeForce GT720 graphics card working with Plasma. It worked great up to about a year ago, but after that, nothing but problems. I ordered an AMD Radeon RX580 card from Amazon.
I swapped the cards and tapped the power switchā¦ The computer booted straight to SDDM without skipping a beat. (I figured the system might take some time to recognize and configure the new hardware, but it was seamless, as if I never installed a new card)ā¦ I logged in to an X session with no problems.
I wondered if Wayland would work, (Itās been a year since I could run Wayland)ā¦ So I logged out of X and went back in under Wayland. Again, no problems. Hopefully this is the last of my Video issues.
Thanks to all who repliedā¦ And to dreaperxz for convincing me to ditch the nVida card
sadly KDE Neon has finally followed suit in joining 2024 and now I have a bricked OS again.