rpms/nvidia-470
2
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

Installs fine, boot fails #1

New Issue
Closed
opened 2025-02-03 19:16:41 +01:00 by einar · 14 comments
einar commented 2025-02-03 19:16:41 +01:00
Copy Link

This package nuked my openmamba install.
It doesn't show any error during the install process, after installing it openmamba fails to boot.
Package version 1:470.256.02-1mamba

This package nuked my openmamba install. It doesn't show any error during the install process, after installing it openmamba fails to boot. Package version `1:470.256.02-1mamba`
silvan commented 2025-02-03 19:55:51 +01:00
Owner
Copy Link

Legacy nvidia-470 has been updated so that the kernel module builds and a theoretical list of needed libraries and files are installed.

Unfortunately compatible hardware is not available for the packager to test and nvidia drivers are not provided with distribution friendly install scripts so that every library and component needs to be manually installed when packaged and may change from a version to another. Because of this the driver needs beta testing support to ensure it works and to keep it working with future updates.

You might want to provide information on how the boot fails in order to understand at which boot stage the problem happens and which kind of investigation and possible recover can be performed.

If instead you are looking for a system ready with nvidia-470 driver support, switching to another Linux distribution may be recommended until there is the opportunity to test and fix the nvidia-470 driver in openmamba.

Legacy nvidia-470 has been updated so that the kernel module builds and a theoretical list of needed libraries and files are installed. Unfortunately compatible hardware is not available for the packager to test and nvidia drivers are not provided with distribution friendly install scripts so that every library and component needs to be manually installed when packaged and may change from a version to another. Because of this the driver needs beta testing support to ensure it works and to keep it working with future updates. You might want to provide information on how the boot fails in order to understand at which boot stage the problem happens and which kind of investigation and possible recover can be performed. If instead you are looking for a system ready with nvidia-470 driver support, switching to another Linux distribution may be recommended until there is the opportunity to test and fix the nvidia-470 driver in openmamba.
einar commented 2025-02-03 20:31:07 +01:00
Author
Copy Link

I would like to provide information, but I don't know how. Please direct me on how to provide information that may be helpful.

Currently, after reboot, I see the "openmamba is starting..." message on a black screen, it disappears and appears back I believe 3 times, and then it is stuck on the screen, nothing else happens.
The first time it flashes, the (usb) keyboard turns on.
The system does restart when I press ctrl+alt+del, so the system responds to keyboard input, but I can't see anything besides that message.
I have tried to boot with the debug flag, but nothing else appears on screen.

I would like to provide information, but I don't know how. Please direct me on how to provide information that may be helpful. Currently, after reboot, I see the "openmamba is starting..." message on a black screen, it disappears and appears back I believe 3 times, and then it is stuck on the screen, nothing else happens. The first time it flashes, the (usb) keyboard turns on. The system does restart when I press ctrl+alt+del, so the system responds to keyboard input, but I can't see anything besides that message. I have tried to boot with the debug flag, but nothing else appears on screen.
silvan commented 2025-02-03 21:07:02 +01:00
Owner
Copy Link

Ok.
Does pressing Ctrl + Alt + F2 (or F3, F4, etc.) not work to open a console?
If not, you may retry after adding this to the grub kernel command line:
nvidia_drm.modeset=1 nvidia_drm.fbdev=1

Ok. Does pressing Ctrl + Alt + F2 (or F3, F4, etc.) not work to open a console? If not, you may retry after adding this to the grub kernel command line: nvidia_drm.modeset=1 nvidia_drm.fbdev=1
einar commented 2025-02-03 21:08:35 +01:00
Author
Copy Link

I can confirm ctrl+alt+f2 (or f3...) does not change what I see on the screen.

I have added the nvidia_drm.modeset=1 nvidia_drm.fbdev=1 kernel flags using grub's menu. Now instead of "openmamba starting..." I see "booting a command list". I believe this is because I also added debug and removed quiet. The text flashes 5 times in total. ctrl+alt+f2 (or f3...) remain unresponsive, ctrl+alt+del results in the computer rebooting.

I have also tried with nvidia-drm.modeset=1 nvidia-drm.fbdev=1 because both _ and - came up on google search results. No difference.

I can confirm ctrl+alt+f2 (or f3...) does not change what I see on the screen. I have added the `nvidia_drm.modeset=1 nvidia_drm.fbdev=1` kernel flags using grub's menu. Now instead of "openmamba starting..." I see "booting a command list". I believe this is because I also added `debug` and removed `quiet`. The text flashes 5 times in total. ctrl+alt+f2 (or f3...) remain unresponsive, ctrl+alt+del results in the computer rebooting. I have also tried with `nvidia-drm.modeset=1 nvidia-drm.fbdev=1` because both `_` and `-` came up on google search results. No difference.
silvan commented 2025-02-04 09:30:56 +01:00
Owner
Copy Link

Assuming that nvidia module loading is causing the issue you might try to disable loading from initramfs and/or modprobe with this kernel command line options:

rd.driver.blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm modprobe.blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm

Just a subset of the above line should be needed but I put all options for completeness.

Assuming that nvidia module loading is causing the issue you might try to disable loading from initramfs and/or modprobe with this kernel command line options: `rd.driver.blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm modprobe.blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm` Just a subset of the above line should be needed but I put all options for completeness.
einar commented 2025-02-05 19:10:46 +01:00
Author
Copy Link

I've been busy, I'm sorry for the late reply.

rd.driver.blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm modprobe.blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm

I have attempted this change, with them the screen does not flash while starting openmamba, however it is still stuck in the same screen.

Is there any information that I could attempt to fetch from the os, such as logs that may contain more information on the issue? I can try to run a live cd, mount the partition and get the potentially relevant information.

I've been busy, I'm sorry for the late reply. > `rd.driver.blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm modprobe.blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm` I have attempted this change, with them the screen does not flash while starting openmamba, however it is still stuck in the same screen. Is there any information that I could attempt to fetch from the os, such as logs that may contain more information on the issue? I can try to run a live cd, mount the partition and get the potentially relevant information.
silvan commented 2025-02-05 20:01:57 +01:00
Owner
Copy Link

You might try to boot in non-graphical mode adding a 3 to the kernel command line or init=/bin/bash,

If you boot from a livecd and have automatic login into KDE Plasma you may try to disable it because the problem might be with Wayland. To do so, comment the [Autologin] block in file /etc/sddm.conf.d/kde_settings.conf .

I have no clues on where the boot stops, if before or after mounting the root filesystem, in the latter case you might find something in the log files, by the way you should mount the openmamba rootfs, bind mount /dev/, /sys, /proc, /run etc. and chroot and see the last boot journal with journalctl.

From chroot you might also uninstall the package and attempt to reinstall and do tests later, although the nvidia modules might still be in the initramfs, which should be regenerared with dracut providing the appropriare options to match the correct kernel version. Not very easy though.

You might try to boot in non-graphical mode adding a `3` to the kernel command line or `init=/bin/bash`, If you boot from a livecd and have automatic login into KDE Plasma you may try to disable it because the problem might be with Wayland. To do so, comment the `[Autologin]` block in file `/etc/sddm.conf.d/kde_settings.conf `. I have no clues on where the boot stops, if before or after mounting the root filesystem, in the latter case you might find something in the log files, by the way you should mount the openmamba rootfs, bind mount /dev/, /sys, /proc, /run etc. and chroot and see the last boot journal with `journalctl`. From chroot you might also uninstall the package and attempt to reinstall and do tests later, although the nvidia modules might still be in the initramfs, which should be regenerared with dracut providing the appropriare options to match the correct kernel version. Not very easy though.
einar commented 2025-02-05 22:05:41 +01:00
Author
Copy Link

Honestly I don't know if the issue was this package any more.
I could not find useful information on the logs. I did find that openmamba received my ctrl+alt+f2 but failed there.
I have then reinstalled openmamba, after openmamba was installed I did dnf update -y. During this update I got a lot of linker errors, then on reboot bash would crash: whenever I opened a terminal emulator I would get "warning: /bin/bash has crashed after a few seconds of hanging. At that point I could not even install nvidia-470 again to perform further testing.

Honestly I don't know if the issue was this package any more. I could not find useful information on the logs. I did find that openmamba received my ctrl+alt+f2 but failed there. I have then reinstalled openmamba, after openmamba was installed I did `dnf update -y`. During this update I got a lot of linker errors, then on reboot bash would crash: whenever I opened a terminal emulator I would get `"warning: /bin/bash has crashed` after a few seconds of hanging. At that point I could not even install `nvidia-470` again to perform further testing.
silvan commented 2025-02-05 23:26:44 +01:00
Owner
Copy Link

I have tested an installation from the latest livecd in VirtualBox and then run sudo dnf update. Yes, there are a lot of linker warnings which are all related to libvtk* but this is not related to any critical issue. The updates completed successully and the system rebooted to the desktop with no problems also running a console, so I cannot reproduce this problem.
It may be an issue with the hardware but it is difficult to get information if bash crashes, You might check if the probem is reproducible after a reinstallation and/or check from a livecd that bash binary and anything else do not result corrupted. Quite weird problem BTW.

I have tested an installation from the latest livecd in VirtualBox and then run `sudo dnf update`. Yes, there are a lot of linker warnings which are all related to `libvtk*` but this is not related to any critical issue. The updates completed successully and the system rebooted to the desktop with no problems also running a console, so I cannot reproduce this problem. It may be an issue with the hardware but it is difficult to get information if bash crashes, You might check if the probem is reproducible after a reinstallation and/or check from a livecd that bash binary and anything else do not result corrupted. Quite weird problem BTW.
einar commented 2025-02-06 16:34:55 +01:00
Author
Copy Link

I have installed openmamba again, updatd with sudo dnf update successfully. Nothing crazy happened. No idea why the outcome is different this time. I did notice all the ld warnings disappeared, because some package was in an awkward stage?

I am now installing nvidia-470. Running scriptlet: nvidia-470-1:470.256.02-1mamba.x86_64 is taking a very long time.

Before this, please note the line find: ‘/var/lib/dkms/*/*/source’: No such file or directory

[einar@ws00 ~]$ sudo dnf install nvidia-470
Last metadata expiration check: 0:02:03 ago on Thu 06 Feb 2025 04:14:18 PM CET.
Dependencies resolved.
==========================================================================================================================
 Package                              Architecture    Version                                      Repository        Size
==========================================================================================================================
Installing:
 nvidia-470                           x86_64          1:470.256.02-1mamba                          rolling          270 M
Installing dependencies:
 dkms                                 noarch          3.1.5-1mamba                                 rolling           64 k
 gcc                                  x86_64          14.2.1+20240909git.3951efed-2mamba           rolling          187 M
 gcc-cpp                              x86_64          14.2.1+20240909git.3951efed-2mamba           rolling          985 k
 kernel-mamba-x86_64-headers          x86_64          6.6.67-1mamba                                rolling           19 M
 libgo                                x86_64          14.2.1+20240909git.3951efed-2mamba           rolling          8.0 M
 libisl                               x86_64          0.27-1mamba                                  rolling          890 k
 libmpc                               x86_64          1.3.1-1mamba                                 rolling           97 k

Transaction Summary
==========================================================================================================================
Install  8 Packages

Total download size: 486 M
Installed size: 1.2 G
Is this ok [y/N]: y
Downloading Packages:
(1/8): dkms-3.1.5-1mamba.noarch.rpm                                                       210 kB/s |  64 kB     00:00    
(2/8): gcc-cpp-14.2.1+20240909git.3951efed-2mamba.x86_64.rpm                              2.7 MB/s | 985 kB     00:00    
(3/8): kernel-mamba-x86_64-headers-6.6.67-1mamba.x86_64.rpm                                20 MB/s |  19 MB     00:00    
(4/8): libgo-14.2.1+20240909git.3951efed-2mamba.x86_64.rpm                                7.8 MB/s | 8.0 MB     00:01    
(5/8): libisl-0.27-1mamba.x86_64.rpm                                                      5.5 MB/s | 890 kB     00:00    
(6/8): libmpc-1.3.1-1mamba.x86_64.rpm                                                     2.4 MB/s |  97 kB     00:00    
(7/8): gcc-14.2.1+20240909git.3951efed-2mamba.x86_64.rpm                                   23 MB/s | 187 MB     00:08    
(8/8): nvidia-470-470.256.02-1mamba.x86_64.rpm                                             20 MB/s | 270 MB     00:13    
--------------------------------------------------------------------------------------------------------------------------
Total                                                                                      31 MB/s | 486 MB     00:15     
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                                  1/1 
  Installing       : libmpc-1.3.1-1mamba.x86_64                                                                       1/8 
  Running scriptlet: libmpc-1.3.1-1mamba.x86_64                                                                       1/8 
  Installing       : libisl-0.27-1mamba.x86_64                                                                        2/8 
  Installing       : libgo-14.2.1+20240909git.3951efed-2mamba.x86_64                                                  3/8 
  Installing       : gcc-cpp-14.2.1+20240909git.3951efed-2mamba.x86_64                                                4/8 
  Installing       : gcc-14.2.1+20240909git.3951efed-2mamba.x86_64                                                    5/8 
  Installing       : dkms-3.1.5-1mamba.noarch                                                                         6/8 
  Running scriptlet: dkms-3.1.5-1mamba.noarch                                                                         6/8 
Created symlink '/etc/systemd/system/multi-user.target.wants/dkms.service' → '/usr/lib/systemd/system/dkms.service'.

  Installing       : kernel-mamba-x86_64-headers-6.6.67-1mamba.x86_64                                                 7/8 
  Running scriptlet: kernel-mamba-x86_64-headers-6.6.67-1mamba.x86_64                                                 7/8 
  Running scriptlet: nvidia-470-1:470.256.02-1mamba.x86_64                                                            8/8 
  Installing       : nvidia-470-1:470.256.02-1mamba.x86_64                                                            8/8 
  Running scriptlet: dkms-3.1.5-1mamba.noarch                                                                         8/8 
find: ‘/var/lib/dkms/*/*/source’: No such file or directory

  Running scriptlet: nvidia-470-1:470.256.02-1mamba.x86_64                                                            8/8 
  Running scriptlet: nvidia-470-1:470.256.02-1mamba.x86_64                                                                                   8/8 
warning: posix.fork(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.spawn() or rpm.execute() instead
warning: posix.wait(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.spawn() or rpm.execute() instead
warning: posix.exec(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.spawn() or rpm.execute() instead
New leaves:
  nvidia-470.x86_64

Installed:
  dkms-3.1.5-1mamba.noarch                                                gcc-14.2.1+20240909git.3951efed-2mamba.x86_64                         
  gcc-cpp-14.2.1+20240909git.3951efed-2mamba.x86_64                       kernel-mamba-x86_64-headers-6.6.67-1mamba.x86_64                      
  libgo-14.2.1+20240909git.3951efed-2mamba.x86_64                         libisl-0.27-1mamba.x86_64                                             
  libmpc-1.3.1-1mamba.x86_64                                              nvidia-470-1:470.256.02-1mamba.x86_64                                 

Complete!

I am about to reboot, pray for me.

Update: unfortunately it didn't go well. Just like before, I see "openmamba starting..." flashing.

I think I can try this whole thing again tonight and I am looking forward to being told what to do to provide as much information as needed in order to get this package working right. (I also think that it would be nice to get nouveau to work right, because I know it can work right with this hardware)

I have uploaded the systemd logs to my google drive here. I tried to view them with journalctl --file <file> | grep nvidia
These were the only available logs, I admittedly tried to start openmamba twice and while the first time I let it attempt to start for 20 full minutes, I have it far less time the second time, and I believe these logs are from the second time only, unfortunately.

I have installed openmamba again, updatd with `sudo dnf update` successfully. Nothing crazy happened. No idea why the outcome is different this time. I did notice all the ld warnings disappeared, because some package was in an awkward stage? I am now installing nvidia-470. `Running scriptlet: nvidia-470-1:470.256.02-1mamba.x86_64` is taking a very long time. Before this, please note the line `find: ‘/var/lib/dkms/*/*/source’: No such file or directory` ```bash [einar@ws00 ~]$ sudo dnf install nvidia-470 Last metadata expiration check: 0:02:03 ago on Thu 06 Feb 2025 04:14:18 PM CET. Dependencies resolved. ========================================================================================================================== Package Architecture Version Repository Size ========================================================================================================================== Installing: nvidia-470 x86_64 1:470.256.02-1mamba rolling 270 M Installing dependencies: dkms noarch 3.1.5-1mamba rolling 64 k gcc x86_64 14.2.1+20240909git.3951efed-2mamba rolling 187 M gcc-cpp x86_64 14.2.1+20240909git.3951efed-2mamba rolling 985 k kernel-mamba-x86_64-headers x86_64 6.6.67-1mamba rolling 19 M libgo x86_64 14.2.1+20240909git.3951efed-2mamba rolling 8.0 M libisl x86_64 0.27-1mamba rolling 890 k libmpc x86_64 1.3.1-1mamba rolling 97 k Transaction Summary ========================================================================================================================== Install 8 Packages Total download size: 486 M Installed size: 1.2 G Is this ok [y/N]: y Downloading Packages: (1/8): dkms-3.1.5-1mamba.noarch.rpm 210 kB/s | 64 kB 00:00 (2/8): gcc-cpp-14.2.1+20240909git.3951efed-2mamba.x86_64.rpm 2.7 MB/s | 985 kB 00:00 (3/8): kernel-mamba-x86_64-headers-6.6.67-1mamba.x86_64.rpm 20 MB/s | 19 MB 00:00 (4/8): libgo-14.2.1+20240909git.3951efed-2mamba.x86_64.rpm 7.8 MB/s | 8.0 MB 00:01 (5/8): libisl-0.27-1mamba.x86_64.rpm 5.5 MB/s | 890 kB 00:00 (6/8): libmpc-1.3.1-1mamba.x86_64.rpm 2.4 MB/s | 97 kB 00:00 (7/8): gcc-14.2.1+20240909git.3951efed-2mamba.x86_64.rpm 23 MB/s | 187 MB 00:08 (8/8): nvidia-470-470.256.02-1mamba.x86_64.rpm 20 MB/s | 270 MB 00:13 -------------------------------------------------------------------------------------------------------------------------- Total 31 MB/s | 486 MB 00:15 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Installing : libmpc-1.3.1-1mamba.x86_64 1/8 Running scriptlet: libmpc-1.3.1-1mamba.x86_64 1/8 Installing : libisl-0.27-1mamba.x86_64 2/8 Installing : libgo-14.2.1+20240909git.3951efed-2mamba.x86_64 3/8 Installing : gcc-cpp-14.2.1+20240909git.3951efed-2mamba.x86_64 4/8 Installing : gcc-14.2.1+20240909git.3951efed-2mamba.x86_64 5/8 Installing : dkms-3.1.5-1mamba.noarch 6/8 Running scriptlet: dkms-3.1.5-1mamba.noarch 6/8 Created symlink '/etc/systemd/system/multi-user.target.wants/dkms.service' → '/usr/lib/systemd/system/dkms.service'. Installing : kernel-mamba-x86_64-headers-6.6.67-1mamba.x86_64 7/8 Running scriptlet: kernel-mamba-x86_64-headers-6.6.67-1mamba.x86_64 7/8 Running scriptlet: nvidia-470-1:470.256.02-1mamba.x86_64 8/8 Installing : nvidia-470-1:470.256.02-1mamba.x86_64 8/8 Running scriptlet: dkms-3.1.5-1mamba.noarch 8/8 find: ‘/var/lib/dkms/*/*/source’: No such file or directory Running scriptlet: nvidia-470-1:470.256.02-1mamba.x86_64 8/8 Running scriptlet: nvidia-470-1:470.256.02-1mamba.x86_64 8/8 warning: posix.fork(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.spawn() or rpm.execute() instead warning: posix.wait(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.spawn() or rpm.execute() instead warning: posix.exec(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.spawn() or rpm.execute() instead New leaves: nvidia-470.x86_64 Installed: dkms-3.1.5-1mamba.noarch gcc-14.2.1+20240909git.3951efed-2mamba.x86_64 gcc-cpp-14.2.1+20240909git.3951efed-2mamba.x86_64 kernel-mamba-x86_64-headers-6.6.67-1mamba.x86_64 libgo-14.2.1+20240909git.3951efed-2mamba.x86_64 libisl-0.27-1mamba.x86_64 libmpc-1.3.1-1mamba.x86_64 nvidia-470-1:470.256.02-1mamba.x86_64 Complete! ``` I am about to reboot, pray for me. Update: unfortunately it didn't go well. Just like before, I see "openmamba starting..." flashing. I think I can try this whole thing again tonight and I am looking forward to being told what to do to provide as much information as needed in order to get this package working right. (I also think that it would be nice to get nouveau to work right, because I know it can work right with this hardware) I have uploaded the systemd logs to my google drive [here](https://drive.google.com/drive/folders/16X4GhmPulK5aZ4SB28Dwz72fYAQEWYdd?usp=sharing). I tried to view them with `journalctl --file <file> | grep nvidia` These were the only available logs, I admittedly tried to start openmamba twice and while the first time I let it attempt to start for 20 full minutes, I have it far less time the second time, and I believe these logs are from the second time only, unfortunately.
silvan commented 2025-02-06 20:09:57 +01:00
Owner
Copy Link

The ldconfig warning may depend on the different packages installation ordering and when ldconfig command is triggered and are not relevant, also the error reported by dkms is about a legacy cleanup command and is not a problem.

The system log shows that nvidia, nvidia-drm and nvidia-modeset modules are loaded without apparent errors but the sddm is failing with this error:
feb 06 17:03:01 ws00 sddm[5275]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_mJlXnd -noreset -displayfd 16 feb 06 17:03:06 ws00 sddm[5275]: Failed to read display number from pipe

So first, it seems that the system is running but there is nothing on screen because there is not a working framebuffer device. I'm trying here a fix setting the option fbdev=1 which we altready tried to set from the kernel command line by the way.

For the sddm problem I don't know exaclty, but I ported from the current nvidia driver in openmamba (which works) a fix to the installation of nvidia-drm_gbm.so, although I think it is only related to Wayland and Arch Linux has commented it in its nvidia-470 package.

These changes are in the nvidia-470-470.256.02-2mamba package which will be available as an update in 1-2 hours.

The ldconfig warning may depend on the different packages installation ordering and when ldconfig command is triggered and are not relevant, also the error reported by dkms is about a legacy cleanup command and is not a problem. The system log shows that `nvidia`, `nvidia-drm` and `nvidia-modeset` modules are loaded without apparent errors but the `sddm` is failing with this error: `feb 06 17:03:01 ws00 sddm[5275]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_mJlXnd -noreset -displayfd 16 feb 06 17:03:06 ws00 sddm[5275]: Failed to read display number from pipe` So first, it seems that the system is running but there is nothing on screen because there is not a working framebuffer device. I'm trying here a fix setting the option `fbdev=1` which we altready tried to set from the kernel command line by the way. For the `sddm` problem I don't know exaclty, but I ported from the current nvidia driver in openmamba (which works) a fix to the installation of `nvidia-drm_gbm.so`, although I think it is only related to Wayland and Arch Linux has commented it in its nvidia-470 package. These changes are in the `nvidia-470-470.256.02-2mamba` package which will be available as an update in 1-2 hours.
🚀 1
einar commented 2025-02-07 16:13:47 +01:00
Author
Copy Link

Good news: I am able to see and log in with sddm.
Bad news: kwin uses 100% of all my cores at all times now. There is a baloo_file_extractor too taking some processor time, but nothing like kwin. This causes the computer to be unresponsive, mouse pointer movement is rendered once every 6 or 7 seconds.
How can we debug this?

Good news: I am able to see and log in with sddm. Bad news: kwin uses 100% of all my cores at all times now. There is a baloo_file_extractor too taking some processor time, but nothing like kwin. This causes the computer to be unresponsive, mouse pointer movement is rendered once every 6 or 7 seconds. How can we debug this?
silvan commented 2025-02-07 16:47:17 +01:00
Owner
Copy Link

The official and general information say that nvidia legacy drivers < 495 only provide a wayland support mechanism which is not supported by KDE Plasma, so you may want to login in X11 mode.

If you want next to debug the problem with the nouveau driver I suggest to open a issue in the xf86-video-nouveau project page.

The official and general information say that nvidia legacy drivers < 495 only provide a wayland support mechanism which is not supported by KDE Plasma, so you may want to login in X11 mode. If you want next to debug the problem with the nouveau driver I suggest to open a issue in the [xf86-video-nouveau](https://src.openmamba.org/rpms/xf86-video-nouveau) project page.
👍 1
einar commented 2025-02-07 21:31:14 +01:00
Author
Copy Link

You are correct. This issue is solved.

You are correct. This issue is solved.
einar closed this issue 2025-02-07 21:31:14 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: rpms/nvidia-470#1
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?