Cliff
November 8, 2024, 4:29am
1
I first installed KDE Neon 5.25 in June 2023, one of three Linux distros I use. When it upgraded to version 6, it would freeze on bootup and required a hard restart almost half the time.
On another forum, it was suggested that my Nvidia card collides with Wayland. When I switched to X11, the bootup crashes went way down, but it still crashes in unpredictable ways. When I open system monitor, when I have six windows open, and sometimes when I reboot after updating. I thought, be patient, maybe one of these updates will fix the problem.
Just yesterday, and for me the last straw, it froze when I put it to sleep and never woke up.
Which crash logs will show me the issue? If the problem is the Nvidia card, I would just as soon replace Neon (top candidate is Pop! OS with Nvidia drivers). I like Plasma, but do not really depend on Neon. No distro is worth this much headache.
1 Like
What is your Nvidia drivers version? Also, what card are you using? What are showing up in your journalctl logs?
Cliff
November 8, 2024, 4:49am
3
The card is G92, GeoForce GTS 240. An older model, but I donāt need more power than that.journalctl?
1 Like
I think that says itā¦ IIRC, Nouveau drivers doesnāt work well with Wayland. Also, I think until NVK comes in, you should give the proprietary or open-kernel drivers a try.
Yes, itās journalctl
Cliff
November 8, 2024, 4:55am
5
Maybe a foolish question, but if it crashes and I reboot, wonāt that command only record events AFTER the crash?
1 Like
It records everything, every log the kernel ever emitts
Cliff
November 8, 2024, 4:57am
7
Then I should copy only those lines around the moment of crashing. Iāll boot into it and try to replicate a crash, then reboot and copy those lines.
1 Like
Sure, and if you see anything, related to Nvidia, be sure itās with Nouveau.
Cliff
November 8, 2024, 5:07am
9
Here is the output, using only the likely lines.
Nov 07 21:02:33 cliff-neon drkonqi-coredump-processor[1331]: ā/usr/bin/plasma-discoverā 1245 "/var/lib/system>ntp.ubuntu.com ).
Try this,
journalctl -o verbose and try to write it in a file, because the lines get cut in the last in this.
Canāt see any error here. But, one thing, there seems to be issues with discover. Can you just once try installing a proprietary driver for NVIDIA?
Cliff
November 8, 2024, 5:17am
12
Sorry for the naive detail, but can I write the output to a file without paging through the lines?
Cliff
November 8, 2024, 5:21am
13
Soumya-ji, It only seems like a problem because Discover was refreshing the list of updates when I opened the terminal. I ignored it because I had more important stuff to do.
1 Like
I think the bigger problem is something different. I am also not sure, why the crash reporter isnāt collecting any logsā¦
Cliff
November 8, 2024, 5:24am
15
I recreated the crash by simply opening System Monitor. The window flashed, different colors appeared and after a minute it had frozen. Telltale clues of a GPU issue.
Try this,
journalctl -p err | tee crash.log
This will only print logs that have high priority errors and the log will be written to a file named crash.log, which you can later upload to dpaste or somewhere. Similarly you can do,
journalctl -b | tee crash.log
This will show every log since last boot.
Do you regularly update your system? Also, it seems nouveau problem itās
Jul 02 09:03:24 cliff-neon kernel: nouveau 0000:01:00.0: chrome[6738]: channel failed to initialise, -17
Jul 02 09:03:24 cliff-neon kernel: nouveau 0000:01:00.0: vp: init failed, -2
Jul 02 09:05:40 cliff-neon kernel: nouveau 0000:01:00.0: fifo: CACHE_ERROR - ch 19 [Renderer[7323]] subc 0 mthd 0060 data beef0201
Jul 02 09:06:13 cliff-neon kernel: nouveau 0000:01:00.0: chrome[8330]: channel failed to initialise, -17
Jul 02 09:06:13 cliff-neon kernel: nouveau 0000:01:00.0: vp: init failed, -2
Cliff
November 8, 2024, 5:40am
19
At least one or 2 times a week
Yes, Nouveau isnāt really a driver to be daily drivedā¦ until NVIDIA doesnāt support your GPU at all. Itās there just to get the display light up.