Spectacle is not working here:
kpipewire_vaapi_logging: VAAPI: VA-API NVDEC driver [direct backend] in use for device "/dev/dri/renderD128"
Correction, it does load, then greys out, then sort of works.
Spectacle is not working here:
kpipewire_vaapi_logging: VAAPI: VA-API NVDEC driver [direct backend] in use for device "/dev/dri/renderD128"
Correction, it does load, then greys out, then sort of works.
This is like the 10th thread with this issue. Looks like I’m gonna wait a week to update. Happy I updated just before these nvidia/SDDM updates were pushed.
Ah okay, i tried that but nothing happened. Am i meant to do this on the black screen?
Yes, on a black screen like on the picture you sent.
If it does not work make sure that you have enabled SysRq
then when you get the freeze do a Alt+PrtScr+R+E
That should terminate all processes and restart the SDDM
without forcing you to do a hard reboot
Also, it would not hurt if both of you guys send your journals and inxi outputs for further analysis.
And again everything is working fine for me. Both on Arch and Fedora with the latest drivers.
Ah okay so i enabled the SysRq by adding in the conf file as explained in the wiki, rebooted after doing a sudo apply on on ctl
Encountered the freeze again after logging in to plasma wayland, and hit those keys, it then spent a little while with a black screen and a cursor that moves. Then come back to the login screen.
Could you direct me to what logs i need to post exactly?
Dont want to provide useless logs if it can be avoided
Hold on, I think I get your issue with the while line at the top left if I disable nvidia_drm.modeset=1. I think we have the same problem which is cool because this makes things easier
Got them here, figured out what you need
https://pastebin.com/iCPB1KmX This is the journal output of my latest boot
[luke@luke-ms7c91 ~]$ inxi
CPU: 8-core AMD Ryzen 7 5800X (-MT MCP-) speed/min/max: 2595/2200/4850 MHz
Kernel: 6.9.7-arch1-1 x86_64 Up: 2m Mem: 5.46/31.27 GiB (17.4%)
Storage: 4.09 TiB (5.6% used) Procs: 397 Shell: Bash inxi: 3.3.35
One thing to note, when running nvidia-inst i get an error around conflicts between 2 drivers.
[luke@luke-ms7c91 ~]$ nvidia-inst
2024-06-29 21:03:02: Info: Running: nvidia-inst v24-1
2024-06-29 21:03:02: Info: Command line: nvidia-inst
2024-06-29 21:03:02: Info: Selected mode: nvidia
NVIDIA card id: 2704
Fetching driver data from nvidia.com ...
2024-06-29 21:03:04: Info: Installing packages: nvidia-dkms nvidia-settings
2024-06-29 21:03:04: Info: Removing packages: lib32-nvidia-utils nvidia
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
COMMANDS TO RUN:
pacman -Rs --noconfirm --noprogressbar --nodeps lib32-nvidia-utils nvidia
pacman -Syuq --noconfirm --noprogressbar --needed nvidia-dkms nvidia-settings
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> NOTE: running the commands may take several minutes...
Root Password:
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing lib32-nvidia-utils breaks dependency 'lib32-vulkan-driver' required by steam
:: Synchronising package databases...
endeavouros downloading...
core downloading...
extra downloading...
multilib downloading...
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
:: nvidia-dkms-555.58-1 and nvidia-555.58-2 are in conflict (NVIDIA-MODULE). Remove nvidia? [y/N]
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: nvidia-dkms-555.58-1 and nvidia-555.58-2 are in conflict
Ive had to remove steam to remove the lib32 issue, then ran nvidia-inst, which ran through okay. Im not sure if this is a no go or the wrong approach but do correct me if im wrong?
Just run pacman -Rdd nvidia
and ignore the lib32-nvidia-utils issue. You should be fine.
Yeh tried that and now i can no longer get into x11 session either now. Going to take the nuclear approach now and reinstall the OS, its only the 12th time in two weeks ive reinstalled linux cause of these drivers
Right okay think im getting to the issue atm, i did a full reinstall of the OS. I installed all the drivers for NVIDIA checked that they were the latest revision of 555-2 or something along those lines I then did a reboot of the system which point it entered into the plasma Wayland session okay. I then proceeded with my regular install of steam which required me to choose from a selection of options I selected the lib32 Nvidia utils option at which point I then rebooted the PC after running through the initialization of starting up Steam I then try to log in to a plasma wayland session and I was met with the same black screen error. I think theres some form kf clash due to the requirements for lib32 nvidia utils for steam?
Might not be on the right lines however
Yeah it could be 32 bit libraries installed from Steam screwing things up. I have Steam installed too.
Uninstalling Steam with its dependencies did nothing. What can I do now???
Not sure if this is helpful;
for me the current stable 6.9 kernel doesn’t play nice with the nvidia proprietary driver under wayland at all (black screen). Lts 6.6 kernel works fine booting into an usable desktop; steam gaming is doing great since the 555 driver dropped.
I am on vanilla arch though.
sudo downgrade lib32-nvidia-utils nvidia-dkms nvidia-utils opencl-nvidia lib32-opencl-nvidia
(or the combination of packages you have installed)
Select the 550 drivers, Answer yes to add <package> to IgnorePkg? [y/N]
- reboot
Yeah fine I give up. These drivers are driving me insane.
You lasted longer than me - I gave up after the notifications that stuck on screen and tried to screenshot and spectacle turned it’s toes up!
The shit show gets a full run down here:
I am still ploughing through it, nothing so far.
I had the same issue and this fixed it:
https://bbs.archlinux.org/viewtopic.php?id=297236
Obviously this is not an actual fix but more of a work-around. Seems like HDR is causing Wayland to hang on Nvidia 555.
You know what i think your bang on with that. Ive not re enabled hdr yet, let me try it reboot and see if it hangs if it does we have found the problem