[SOLVED] Cannot get Ly to work with Nvidia proprietary driver

Histole · 2025-08-06 22:00:25

Been banging my head against the wall with this one. I can’t figure it out.

So I have a 1080 Ti, I used archinstall, selected the proprietary nvidia drivers, selected desktop with KDE, for the greeter I select SDDM. Everything works perfectly, I’m able to log in, switch to sway once that’s installed, etc.

BUT, if I try to use Ly instead of SDDM, the system doesn’t get past the initial initialization. Once I do archinstall, but select Ly instead of SDDM, and reboot, it gets stuck around “loading initial ramdisk” or a few lines after that. No matter what I do.

Then, again, same settings but switch to SDDM on archinstall and it works. I tried even going from sddm to ly afterwards and the same issue occured.

I did notice if I choose the driver package for Turing+ GPUs that it ends up working with Ly, but once I’m in the DE my monitor settings are all wonky.

Any thoughts? Thanks.

Last edited by Histole (2025-08-08 13:33:04)

seth · 2025-08-07 07:43:30

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
Can you boot the multi-user.target (2nd link below)?
Can you reboot from the failin ly by frenetically pressing cltr+alt+del?
Please post your complete system journal for the previous boot:

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

Histole · 2025-08-07 15:06:41

seth wrote:

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
Can you boot the multi-user.target (2nd link below)?
Can you reboot from the failin ly by frenetically pressing cltr+alt+del?
Please post your complete system journal for the previous boot:
sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

I could not go into another TTY by pressing ctrl alt del FX. Ctrl alt del did restart the system.

I was able to reboot, I tried to remove the quiet flag upon boot and it simply got stuck at “Press Ctrl D to continue”.

Logs are here: https://0x0.st/8hUu.txt

seth · 2025-08-07 19:04:50

Not sure whether that's relevant, but some USB device is actiing up

Aug 07 01:01:36 pc kernel: usb 1-7: new full-speed USB device number 5 using xhci_hcd
Aug 07 01:01:36 pc kernel: usb 1-7: device descriptor read/64, error -110
Aug 07 01:01:36 pc kernel: usb 1-7: device descriptor read/64, error -110
Aug 07 01:01:36 pc kernel: usb 1-7: new full-speed USB device number 6 using xhci_hcd
Aug 07 01:01:36 pc kernel: usb 1-7: device descriptor read/64, error -110
Aug 07 01:01:36 pc kernel: usb 1-7: device descriptor read/64, error -110
Aug 07 01:01:36 pc kernel: usb 1-7: new full-speed USB device number 7 using xhci_hcd
Aug 07 01:01:36 pc kernel: usb 1-7: Device not responding to setup address.
Aug 07 01:01:36 pc kernel: usb 1-7: device not accepting address 7, error -71
Aug 07 01:01:36 pc kernel: usb 1-7: WARN: invalid context state for evaluate context command.
Aug 07 01:01:36 pc kernel: usb 1-7: new full-speed USB device number 8 using xhci_hcd
Aug 07 01:01:36 pc kernel: usb 1-7: Device not responding to setup address.
Aug 07 01:01:36 pc kernel: usb 1-7: device not accepting address 8, error -71
Aug 07 01:01:36 pc kernel: usb 1-7: WARN: invalid context state for evaluate context command.

Try to add "nvidia_drm.modeset=1 nvidia_drm.fbdev=0" to the https://wiki.archlinux.org/title/Kernel_parameters (must be the kernel commandline, modprobe.conf will not work for this) to block the simpledrm device and deactivate fbdev.
There's otherwise no obvious error and there's also only the nvidia GPU (ie. it's not a hybrid system where the from drm device gets used… except for maybe the simpledrm one)

Histole · 2025-08-07 20:08:17

seth wrote:

Not sure whether that's relevant, but some USB device is actiing up

Aug 07 01:01:36 pc kernel: usb 1-7: new full-speed USB device number 5 using xhci_hcd
Aug 07 01:01:36 pc kernel: usb 1-7: device descriptor read/64, error -110
Aug 07 01:01:36 pc kernel: usb 1-7: device descriptor read/64, error -110
Aug 07 01:01:36 pc kernel: usb 1-7: new full-speed USB device number 6 using xhci_hcd
Aug 07 01:01:36 pc kernel: usb 1-7: device descriptor read/64, error -110
Aug 07 01:01:36 pc kernel: usb 1-7: device descriptor read/64, error -110
Aug 07 01:01:36 pc kernel: usb 1-7: new full-speed USB device number 7 using xhci_hcd
Aug 07 01:01:36 pc kernel: usb 1-7: Device not responding to setup address.
Aug 07 01:01:36 pc kernel: usb 1-7: device not accepting address 7, error -71
Aug 07 01:01:36 pc kernel: usb 1-7: WARN: invalid context state for evaluate context command.
Aug 07 01:01:36 pc kernel: usb 1-7: new full-speed USB device number 8 using xhci_hcd
Aug 07 01:01:36 pc kernel: usb 1-7: Device not responding to setup address.
Aug 07 01:01:36 pc kernel: usb 1-7: device not accepting address 8, error -71
Aug 07 01:01:36 pc kernel: usb 1-7: WARN: invalid context state for evaluate context command.

Try to add "nvidia_drm.modeset=1 nvidia_drm.fbdev=0" to the https://wiki.archlinux.org/title/Kernel_parameters (must be the kernel commandline, modprobe.conf will not work for this) to block the simpledrm device and deactivate fbdev.
There's otherwise no obvious error and there's also only the nvidia GPU (ie. it's not a hybrid system where the from drm device gets used… except for maybe the simpledrm one)

Yeah I've been trying to figure out why I get those erros for USB on this machine, I don't get them on my laptop. Regardless, I tried to add the lines you said, but I get the same thing. Just hangs and never actually displays Ly.
I did notice that the machine takes much longer to boot into Arch versus windows per se, if that hints at anything...

Thanks for the help regardless though.

seth · 2025-08-07 20:36:04

Please avoid bloating the thread with pointless full quotes.
Post the journal of the nvidia_drm.modeset=1 attempt and certainly see the 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Then abandon ly, only try to boot the multi-user.target for now.
Btw

Then, again, same settings but switch to SDDM on archinstall and it works.

don't re-install arch to do any of this…

About the misbehaving usb device: assuming it's not because of windows, detach all external devices resp. replace keyboard and mouse w/ $5 office supply (might actually be one of them)

Histole · 2025-08-07 22:24:36

seth wrote:

Please avoid bloating the thread with pointless full quotes.

My apologies.

seth wrote:

Post the journal of the nvidia_drm.modeset=1 attempt and certainly see the 3rd link below

You know what, I had actually made a typo when I initially typed in "nvidia_drm.fbdev=0" fixed it and it booted up fine with Ly.

seth wrote:

About the misbehaving usb device: assuming it's not because of windows, detach all external devices resp. replace keyboard and mouse w/ $5 office supply (might actually be one of them)

USB device ended up being my Yeti Nano, sort of odd, was just working fine. Coincidence I suppose. Have to figure that out next, thanks a lot for the help.

seth · 2025-08-08 07:05:27

"nvidia_drm.fbdev=0" fixed it and it booted up fine with Ly

\o/
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

There have been longtime issues reported w/ fbdev (do you have multiple monitors?) and there are suggestions for a fix appearing in the 580xx drivers - so once released you might want to test that, but it's as vague as it sounds.

Arch Linux

#1 2025-08-06 22:00:25

[SOLVED] Cannot get Ly to work with Nvidia proprietary driver

#2 2025-08-07 07:43:30

Re: [SOLVED] Cannot get Ly to work with Nvidia proprietary driver

#3 2025-08-07 15:06:41

Re: [SOLVED] Cannot get Ly to work with Nvidia proprietary driver

#4 2025-08-07 19:04:50

Re: [SOLVED] Cannot get Ly to work with Nvidia proprietary driver

#5 2025-08-07 20:08:17

Re: [SOLVED] Cannot get Ly to work with Nvidia proprietary driver

#6 2025-08-07 20:36:04

Re: [SOLVED] Cannot get Ly to work with Nvidia proprietary driver

#7 2025-08-07 22:24:36

Re: [SOLVED] Cannot get Ly to work with Nvidia proprietary driver

#8 2025-08-08 07:05:27

Re: [SOLVED] Cannot get Ly to work with Nvidia proprietary driver

Board footer