[SOLVED] Suspend and Wake Up Issues

axsc · 2024-11-11 03:23:58

I recently made a fresh install of Arch on a brand new SSD. I followed exactly this tutorial here: https://www.youtube.com/watch?v=FxeriGuJKTM
I chose KDE as my desktop environment, and SDDM as the display manager. Now I'm having a few issues I hope to resolve.

1. After putting my PC to sleep, upon wakeup all I get is a black screen. My cursor is visible and responsive but everything else is black. I can actually hover over the password bar and see the cursor change. I can log in, but the screen is still black. The only "fix" I've been able to figure out is to switch TTY and then switch back. Upon doing this, my GUI returns but it's extremely slow and I'm forced to reboot anyway.

2. When booting my PC to the SDDM login screen, my keyboard doesn't work at all. My mouse works fine and I can click the password bar but I can't type anything. This only lasts for about 30 seconds and I'm able to use my keyboard normally. This is strange because my keyboard is fully functional during the systemd bootloader screen.

This is the output of lsusb:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 413c:1003 Dell Computer Corp. Keyboard Hub
Bus 001 Device 003: ID 0b05:1a52 ASUSTek Computer, Inc. USB Audio
Bus 001 Device 004: ID 413c:2010 Dell Computer Corp. Keyboard
Bus 001 Device 005: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
Bus 001 Device 006: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 009: ID 1e71:2012 NZXT NZXT RGB Controller
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 006 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 046d:c53f Logitech, Inc. USB Receiver
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

This is lsusb -t:

/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/12p, 480M
    |__ Port 005: Dev 002, If 0, Class=Hub, Driver=hub/3p, 12M
        |__ Port 001: Dev 004, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 001: Dev 004, If 1, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 006: Dev 003, If 0, Class=Audio, Driver=snd-usb-audio, 480M
    |__ Port 006: Dev 003, If 1, Class=Audio, Driver=snd-usb-audio, 480M
    |__ Port 006: Dev 003, If 2, Class=Audio, Driver=snd-usb-audio, 480M
    |__ Port 006: Dev 003, If 3, Class=Audio, Driver=snd-usb-audio, 480M
    |__ Port 006: Dev 003, If 4, Class=Audio, Driver=snd-usb-audio, 480M
    |__ Port 006: Dev 003, If 5, Class=Audio, Driver=snd-usb-audio, 480M
    |__ Port 006: Dev 003, If 6, Class=Audio, Driver=snd-usb-audio, 480M
    |__ Port 006: Dev 003, If 7, Class=Human Interface Device, Driver=usbhid, 480M
    |__ Port 007: Dev 005, If 0, Class=Vendor Specific Class, Driver=[none], 12M
    |__ Port 007: Dev 005, If 2, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 008: Dev 006, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 004: Dev 009, If 0, Class=Human Interface Device, Driver=usbhid, 12M
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/5p, 20000M/x2
/:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M
/:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M
/:  Bus 005.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M
    |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M
/:  Bus 006.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M
    |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/4p, 5000M
/:  Bus 007.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
    |__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 001: Dev 002, If 1, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 001: Dev 002, If 2, Class=Human Interface Device, Driver=usbhid, 12M
/:  Bus 008.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/0p, 5000M

This is the output of 'dmesg | grep -i usb':

[    0.297955] ACPI: bus type USB registered
[    0.297955] usbcore: registered new interface driver usbfs
[    0.297955] usbcore: registered new interface driver hub
[    0.297955] usbcore: registered new device driver usb
[    0.449748] usbcore: registered new interface driver usbserial_generic
[    0.449752] usbserial: USB Serial support registered for generic
[    1.831519] xhci_hcd 0000:0a:00.0: new USB bus registered, assigned bus number 1
[    1.887760] xhci_hcd 0000:0a:00.0: new USB bus registered, assigned bus number 2
[    1.887762] xhci_hcd 0000:0a:00.0: Host supports USB 3.2 Enhanced SuperSpeed
[    1.888428] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.11
[    1.888430] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.888431] usb usb1: Product: xHCI Host Controller
[    1.888432] usb usb1: Manufacturer: Linux 6.11.6-arch1-1 xhci-hcd
[    1.888433] usb usb1: SerialNumber: 0000:0a:00.0
[    1.888585] hub 1-0:1.0: USB hub found
[    1.891714] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[    1.891729] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.11
[    1.891730] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.891731] usb usb2: Product: xHCI Host Controller
[    1.891732] usb usb2: Manufacturer: Linux 6.11.6-arch1-1 xhci-hcd
[    1.891733] usb usb2: SerialNumber: 0000:0a:00.0
[    1.891912] hub 2-0:1.0: USB hub found
[    1.893409] xhci_hcd 0000:0c:00.3: new USB bus registered, assigned bus number 3
[    1.893969] xhci_hcd 0000:0c:00.3: new USB bus registered, assigned bus number 4
[    1.893970] xhci_hcd 0000:0c:00.3: Host supports USB 3.1 Enhanced SuperSpeed
[    1.893991] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.11
[    1.893993] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.893994] usb usb3: Product: xHCI Host Controller
[    1.893995] usb usb3: Manufacturer: Linux 6.11.6-arch1-1 xhci-hcd
[    1.893996] usb usb3: SerialNumber: 0000:0c:00.3
[    1.894070] hub 3-0:1.0: USB hub found
[    1.894587] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[    1.894601] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.11
[    1.894603] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.894604] usb usb4: Product: xHCI Host Controller
[    1.894605] usb usb4: Manufacturer: Linux 6.11.6-arch1-1 xhci-hcd
[    1.894605] usb usb4: SerialNumber: 0000:0c:00.3
[    1.894668] hub 4-0:1.0: USB hub found
[    1.895217] xhci_hcd 0000:0c:00.4: new USB bus registered, assigned bus number 5
[    1.895767] xhci_hcd 0000:0c:00.4: new USB bus registered, assigned bus number 6
[    1.895769] xhci_hcd 0000:0c:00.4: Host supports USB 3.1 Enhanced SuperSpeed
[    1.895795] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.11
[    1.895796] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.895797] usb usb5: Product: xHCI Host Controller
[    1.895798] usb usb5: Manufacturer: Linux 6.11.6-arch1-1 xhci-hcd
[    1.895799] usb usb5: SerialNumber: 0000:0c:00.4
[    1.895870] hub 5-0:1.0: USB hub found
[    1.896370] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
[    1.896384] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.11
[    1.896385] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.896386] usb usb6: Product: xHCI Host Controller
[    1.896387] usb usb6: Manufacturer: Linux 6.11.6-arch1-1 xhci-hcd
[    1.896388] usb usb6: SerialNumber: 0000:0c:00.4
[    1.896451] hub 6-0:1.0: USB hub found
[    1.896992] xhci_hcd 0000:0d:00.0: new USB bus registered, assigned bus number 7
[    1.898263] xhci_hcd 0000:0d:00.0: USB3 root hub has no ports
[    1.898463] xhci_hcd 0000:0d:00.0: new USB bus registered, assigned bus number 8
[    1.898464] xhci_hcd 0000:0d:00.0: Host supports USB 3.0 SuperSpeed
[    1.898488] usb usb7: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.11
[    1.898490] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.898491] usb usb7: Product: xHCI Host Controller
[    1.898492] usb usb7: Manufacturer: Linux 6.11.6-arch1-1 xhci-hcd
[    1.898492] usb usb7: SerialNumber: 0000:0d:00.0
[    1.898861] hub 7-0:1.0: USB hub found
[    1.899133] usb usb8: We don't know the algorithms for LPM for this host, disabling LPM.
[    1.899147] usb usb8: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.11
[    1.899148] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.899149] usb usb8: Product: xHCI Host Controller
[    1.899150] usb usb8: Manufacturer: Linux 6.11.6-arch1-1 xhci-hcd
[    1.899151] usb usb8: SerialNumber: 0000:0d:00.0
[    1.899219] hub 8-0:1.0: USB hub found
[    2.143589] usb 5-2: new high-speed USB device number 2 using xhci_hcd
[    2.147205] usb 7-1: new full-speed USB device number 2 using xhci_hcd
[    2.213592] usb 1-5: new full-speed USB device number 2 using xhci_hcd
[    2.296163] usb 5-2: New USB device found, idVendor=174c, idProduct=2074, bcdDevice= 0.01
[    2.296166] usb 5-2: New USB device strings: Mfr=2, Product=3, SerialNumber=0
[    2.296167] usb 5-2: Product: ASM107x
[    2.296169] usb 5-2: Manufacturer: ASUS TEK.
[    2.317446] usb 7-1: New USB device found, idVendor=046d, idProduct=c53f, bcdDevice=44.01
[    2.317449] usb 7-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.317450] usb 7-1: Product: USB Receiver
[    2.317451] usb 7-1: Manufacturer: Logitech
[    2.344175] hub 5-2:1.0: USB hub found
[    2.417220] usb 6-2: new SuperSpeed USB device number 2 using xhci_hcd
[    2.470734] usb 6-2: New USB device found, idVendor=174c, idProduct=3074, bcdDevice= 0.01
[    2.470737] usb 6-2: New USB device strings: Mfr=2, Product=3, SerialNumber=0
[    2.470739] usb 6-2: Product: ASM107x
[    2.470741] usb 6-2: Manufacturer: ASUS TEK.
[    2.479265] usbcore: registered new interface driver usbhid
[    2.479267] usbhid: USB HID core driver
[    2.507546] hub 6-2:1.0: USB hub found
[    2.522172] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:08.3/0000:0d:00.0/usb7/7-1/7-1:1.0/0003:046D:C53F.0001/input/input4
[    2.532043] usb 1-5: New USB device found, idVendor=413c, idProduct=1003, bcdDevice= 2.00
[    2.532046] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.532048] usb 1-5: Product: Dell USB Keyboard Hub
[    2.532049] usb 1-5: Manufacturer: Dell
[    2.554466] hub 1-5:1.0: USB hub found
[    2.740587] hid-generic 0003:046D:C53F.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:0d:00.0-1/input0
[    2.740704] input: Logitech USB Receiver Mouse as /devices/pci0000:00/0000:00:08.3/0000:0d:00.0/usb7/7-1/7-1:1.1/0003:046D:C53F.0002/input/input11
[    2.740797] input: Logitech USB Receiver Consumer Control as /devices/pci0000:00/0000:00:08.3/0000:0d:00.0/usb7/7-1/7-1:1.1/0003:046D:C53F.0002/input/input12
[    2.770266] usb 1-6: new high-speed USB device number 3 using xhci_hcd
[    2.797237] input: Logitech USB Receiver System Control as /devices/pci0000:00/0000:00:08.3/0000:0d:00.0/usb7/7-1/7-1:1.1/0003:046D:C53F.0002/input/input13
[    2.797361] hid-generic 0003:046D:C53F.0002: input,hiddev96,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:0d:00.0-1/input1
[    2.797485] hid-generic 0003:046D:C53F.0003: hiddev97,hidraw2: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:0d:00.0-1/input2
[    3.243807] logitech-djreceiver 0003:046D:C53F.0001: hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:0d:00.0-1/input0
[    3.463818] usb 1-5.1: new full-speed USB device number 4 using xhci_hcd
[    3.500682] logitech-djreceiver 0003:046D:C53F.0002: hiddev96,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:0d:00.0-1/input1
[    3.557101] logitech-djreceiver 0003:046D:C53F.0003: hiddev97,hidraw2: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:0d:00.0-1/input2
[    3.615680] input: Logitech Wireless Mouse PID:4074 Keyboard as /devices/pci0000:00/0000:00:08.3/0000:0d:00.0/usb7/7-1/7-1:1.2/0003:046D:C53F.0003/0003:046D:4074.0004/input/input15
[    3.672433] usb 1-5.1: New USB device found, idVendor=413c, idProduct=2010, bcdDevice= 2.00
[    3.672436] usb 1-5.1: New USB device strings: Mfr=1, Product=3, SerialNumber=0
[    3.672438] usb 1-5.1: Product: Dell USB Keyboard
[    3.672440] usb 1-5.1: Manufacturer: Dell
[    3.710589] input: Dell Dell USB Keyboard as /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0a:00.0/usb1/1-5/1-5.1/1-5.1:1.0/0003:413C:2010.0005/input/input20
[    3.763926] input: Logitech Wireless Mouse PID:4074 Mouse as /devices/pci0000:00/0000:00:08.3/0000:0d:00.0/usb7/7-1/7-1:1.2/0003:046D:C53F.0003/0003:046D:4074.0004/input/input16
[    3.764023] hid-generic 0003:046D:4074.0004: input,hidraw3: USB HID v1.11 Keyboard [Logitech Wireless Mouse PID:4074] on usb-0000:0d:00.0-1/input2:1
[    3.930326] hid-generic 0003:413C:2010.0005: input,hidraw4: USB HID v1.10 Keyboard [Dell Dell USB Keyboard] on usb-0000:0a:00.0-5.1/input0
[    3.958541] input: Dell Dell USB Keyboard Consumer Control as /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0a:00.0/usb1/1-5/1-5.1/1-5.1:1.1/0003:413C:2010.0006/input/input21
[    4.116987] input: Dell Dell USB Keyboard System Control as /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0a:00.0/usb1/1-5/1-5.1/1-5.1:1.1/0003:413C:2010.0006/input/input22
[    4.117029] hid-generic 0003:413C:2010.0006: input,hidraw5: USB HID v1.10 Device [Dell Dell USB Keyboard] on usb-0000:0a:00.0-5.1/input1
[    4.195598] input: Logitech G305 as /devices/pci0000:00/0000:00:08.3/0000:0d:00.0/usb7/7-1/7-1:1.2/0003:046D:C53F.0003/0003:046D:4074.0004/input/input23
[    4.380563] logitech-hidpp-device 0003:046D:4074.0004: input,hidraw3: USB HID v1.11 Keyboard [Logitech G305] on usb-0000:0d:00.0-1/input2:1
[    5.132908] usb 1-6: New USB device found, idVendor=0b05, idProduct=1a52, bcdDevice= 0.02
[    5.132911] usb 1-6: New USB device strings: Mfr=3, Product=1, SerialNumber=0
[    5.132913] usb 1-6: Product: USB Audio
[    5.132914] usb 1-6: Manufacturer: Generic
[    5.198167] hid-generic 0003:0B05:1A52.0007: hiddev98,hidraw6: USB HID v1.11 Device [Generic USB Audio] on usb-0000:0a:00.0-6/input7
[    5.386944] usb 1-7: new full-speed USB device number 5 using xhci_hcd
[    5.764746] usb 1-7: config 1 has an invalid interface number: 2 but max is 1
[    5.764752] usb 1-7: config 1 has no interface number 1
[    5.776700] usb 1-7: New USB device found, idVendor=0b05, idProduct=19af, bcdDevice= 1.00
[    5.776705] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    5.776707] usb 1-7: Product: AURA LED Controller
[    5.776709] usb 1-7: Manufacturer: AsusTek Computer Inc.
[    5.776710] usb 1-7: SerialNumber: 9876543210
[    5.792765] hid-generic 0003:0B05:19AF.0008: hiddev99,hidraw7: USB HID v1.11 Device [AsusTek Computer Inc. AURA LED Controller] on usb-0000:0a:00.0-7/input2
[    5.980283] usb 1-8: new high-speed USB device number 6 using xhci_hcd
[    6.213936] usb 1-8: New USB device found, idVendor=05e3, idProduct=0608, bcdDevice=60.90
[    6.213943] usb 1-8: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    6.213945] usb 1-8: Product: USB2.0 Hub
[    6.225052] hub 1-8:1.0: USB hub found
[    6.444009] usb 1-11: new high-speed USB device number 7 using xhci_hcd
[   11.830588] usb 1-11: device descriptor read/64, error -110
[   27.403957] usb 1-11: device descriptor read/64, error -110
[   27.703875] usb 1-11: new high-speed USB device number 8 using xhci_hcd
[   32.950653] usb 1-11: device descriptor read/64, error -110
[   48.677741] usb 1-11: device descriptor read/64, error -110
[   48.788438] usb usb1-port11: attempt power cycle
[   48.868665] usb 1-8.4: new full-speed USB device number 9 using xhci_hcd
[   49.184263] usb 1-8.4: New USB device found, idVendor=1e71, idProduct=2012, bcdDevice= 1.04
[   49.184269] usb 1-8.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   49.184271] usb 1-8.4: Product: NZXT RGB Controller
[   49.184273] usb 1-8.4: Manufacturer: NZXT, Inc.
[   49.184274] usb 1-8.4: SerialNumber: 0403B009AB75B0825EFC5C53
[   49.230661] hid-generic 0003:1E71:2012.0009: hiddev100,hidraw8: USB HID v1.00 Device [NZXT, Inc. NZXT RGB Controller] on usb-0000:0a:00.0-8.4/input0
[   49.453995] usb 1-11: new high-speed USB device number 10 using xhci_hcd
[   54.253972] usb 1-11: Device not responding to setup address.
[   59.263814] usb 1-11: Device not responding to setup address.
[   59.473974] usb 1-11: device not accepting address 10, error -71
[   59.667455] usb 1-11: new high-speed USB device number 11 using xhci_hcd
[   64.467811] usb 1-11: Device not responding to setup address.
[   69.477734] usb 1-11: Device not responding to setup address.
[   69.688581] usb 1-11: device not accepting address 11, error -71
[   69.692615] usb usb1-port11: unable to enumerate USB device
[   75.773467] usbcore: registered new interface driver snd-usb-audio

I was wondering if anyone could help me out with this. I've already had an SSD abruptly die on me a few days ago so I'm really hoping I can get this sorted out. Thanks

-------------------------------------------------------
EDIT:
The keyboard issue was solved by simply changing my login screen theme.

As for the suspend and wake issue, Seth's solution worked. Here is exactly what I did:
1. Added some kernel parameters. I'm using systemd-boot so I edited the file '/boot/loader/entries/2024-11-09_18-48-54_linux.conf', adding the following parameters to the options line:

nvidia-drm.modeset=1 nvidia_drm.fbdev=0 nvidia.NVreg_PreserveVideoMemoryAllocations=0

So my '/boot/loader/entries/2024-11-09_18-48-54_linux.conf' file now looks like:

# Created by: archinstall
# Created on: 2024-11-09_18-48-54
title   Arch Linux (linux)
linux   /vmlinuz-linux
initrd  /initramfs-linux.img
options root=PARTUUID=8098ee8e-3804-47d0-8d35-5d5d65548a5a zswap.enabled=0 rw rootfstype=ext4 nvidia-drm.modeset=1 nvidia_drm.fbdev=0 nvidia.NVreg_PreserveVideoMemoryAllocations=0

2. I then disabled the following systemd services (systemd disable): nvidia-suspend.service, nvidia-hibernate.service, and nvidia-resume.service
3. Reboot

Thanks Seth for the solution!

Last edited by axsc (2024-11-12 23:50:41)

seth · 2024-11-11 08:33:23

I followed exactly this tutorial here: https://www.youtube.com/watch?v=FxeriGuJKTM

Which was a mistake.
https://wiki.archlinux.org/title/Installation_guide

upon wakeup all I get is a black screen. My cursor is visible and responsive but everything else is black

That's the screenlocker, possibly kwin - not SDDM.
And probably related to gpu/driver and display server.

This only lasts for about 30 seconds and I'm able to use my keyboard normally.

Sounds like some dbus timeout (25s)

I was wondering if anyone could help me out with this.

Check the system journal on both conditions.
For the black lockscreen: wayland + nvidia? Same w/ X11?
The sleep services might cause trouble, https://bbs.archlinux.org/viewtopic.php?id=300895

axsc · 2024-11-11 19:50:32

seth wrote:

I followed exactly this tutorial here: https://www.youtube.com/watch?v=FxeriGuJKTM
Which was a mistake.
https://wiki.archlinux.org/title/Installation_guide
upon wakeup all I get is a black screen. My cursor is visible and responsive but everything else is black
That's the screenlocker, possibly kwin - not SDDM.
And probably related to gpu/driver and display server.
This only lasts for about 30 seconds and I'm able to use my keyboard normally.
Sounds like some dbus timeout (25s)
I was wondering if anyone could help me out with this.
Check the system journal on both conditions.
For the black lockscreen: wayland + nvidia? Same w/ X11?
The sleep services might cause trouble, https://bbs.archlinux.org/viewtopic.php?id=300895

Hey Seth, I was able to resolve the keyboard issue by changing my login screen theme.
For the lockscreen issue: I'm using nvidia proprietary drivers w/ X11.
What's the best way to record my journal after I attempt to wake my PC up from sleep? My PC is very slow and almost unresponsive if I manage to make the GUI reappear. Would 'journalctl -b' from another TTY work?

When I get home I'll try to set the kernel parameters you gave in the thread you linked. Could you explain how to do this with systemd-boot? The wiki pages https://wiki.archlinux.org/title/Kernel_parameters and https://wiki.archlinux.org/title/System … protection are really not helpful.

Last edited by axsc (2024-11-11 20:06:00)

seth · 2024-11-11 20:15:07

Would 'journalctl -b' from another TTY work?

Yes. You can uploade your complete system journal for the boot from the console:

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

It's also ok to restart or shutdown the display server or even reboot and access the journal of the previous (… -b -1 …) boot.
The journal won't go away unless you reboot w/ the power button.

Unless there's aynthing special about your setup that you didn't mention, why did https://wiki.archlinux.org/title/Kernel … stemd-boot not work?

axsc · 2024-11-12 00:09:46

seth wrote:

Would 'journalctl -b' from another TTY work?
Yes. You can uploade your complete system journal for the boot from the console:
sudo journalctl -b | curl -F 'file=@-' 0x0.st
It's also ok to restart or shutdown the display server or even reboot and access the journal of the previous (… -b -1 …) boot.
The journal won't go away unless you reboot w/ the power button.
Unless there's aynthing special about your setup that you didn't mention, why did https://wiki.archlinux.org/title/Kernel … stemd-boot not work?

https://wiki.archlinux.org/title/Kernel … stemd-boot references '/boot/loader/entries/arch.conf' which doesn't exist on my system. However, a reddit post (https://www.reddit.com/r/archlinux/comm … temd_boot/) mentions '/boot/loader/loader.conf'. These are the contents of that file on my PC:

timeout 3
#console-mode keep

Do I just append the line 'nomodeset nvidia-drm.modeset=1 nvidia_drm.fbdev=1' to the bottom of that file? Or would it be 'options nomodeset nvidia-drm.modeset=1 nvidia_drm.fbdev=1'? That's what I'm not clear about.

In my /boot/loader/entries directory there are 4 files:

2024-11-09_18-48-54_linux.conf  2024-11-09_18-48-54_linux-fallback.conf  2024-11-09_18-48-54_linux-lts.conf  2024-11-09_18-48-54_linux-lts-fallback.conf

The contents of the first file (2024-11-09_18-48-54_linux.conf) are:

# Created by: archinstall
# Created on: 2024-11-09_18-48-54
title   Arch Linux (linux)
linux   /vmlinuz-linux
initrd  /initramfs-linux.img
options root=PARTUUID=8098ee8e-3804-47d0-8d35-5d5d65548a5a zswap.enabled=0 rw rootfstype=ext4

Last edited by axsc (2024-11-12 00:13:19)

seth · 2024-11-12 09:26:21

You append that to the existing options line.
The systemd-bood config files are generic and freeform, the one in the wiki is more or less a placeholder
You've 4 for the regular and the LTS kernel and their failsave variants and have to edit at least the one you're planning to boot.

axsc · 2024-11-12 13:09:04

seth wrote:

You append that to the existing options line.
The systemd-bood config files are generic and freeform, the one in the wiki is more or less a placeholder
You've 4 for the regular and the LTS kernel and their failsave variants and have to edit at least the one you're planning to boot.

Ok so I appended 'nomodeset nvidia-drm.modeset=1 nvidia_drm.fbdev=1' to the options line of 2024-11-09_18-48-54_linux.conf and that didn't change anything.

# Created by: archinstall
# Created on: 2024-11-09_18-48-54
title   Arch Linux (linux)
linux   /vmlinuz-linux
initrd  /initramfs-linux.img
options root=PARTUUID=8098ee8e-3804-47d0-8d35-5d5d65548a5a zswap.enabled=0 rw rootfstype=ext4 nomodeset nvidia-drm.modeset=1 nvidia_drm.fbdev=1

When I suspend and wake my PC it's still the same black screen with my cursor. I tried the same with 'nvidia-drm.modeset=1 nvidia_drm.fbdev=0' with the same outcome except now when switching back TTY my GUI does not reappear.
Another thing that happens (regardless of the edit to the 2024-11-09_18-48-54_linux.conf file) is that when I switch TTY from the black screen it takes me to the login shell, but I also get an error message in the shell:

[    141.980032] usb 1-11: device not accepting address 13, error -71
[    141.983301] usb usb1-port11: unable to enumerate USB device

I'm not sure if this is related or a separate issue.

Here's my journal when I boot into my PC: https://0x0.st/XkTb.txt
Here's my journal after I boot, suspend, then wake: https://0x0.st/XkTQ.txt
Here's my journal after I boot, suspend, wake, switch TTY, then switch TTY back to get into the GUI: https://0x0.st/XkT2.txt

At the bottom of these journals are error messages related to my graphics:

Nov 12 05:54:12 archlinux kscreenlocker_greet[2158]: QRhiGles2: Context is lost.
Nov 12 05:54:12 archlinux kscreenlocker_greet[2158]: Graphics device lost, cleaning up scenegraph and releasing RHI

Any ideas?

Last edited by axsc (2024-11-12 13:20:53)

seth · 2024-11-12 14:12:26

I missed that but when did "nomodeset" get introduced?
Don't use that.

Also it would be "nvidia-drm.modeset=1 nvidia_drm.fbdev=0", nvidia_drm.fbdev=1 is default anyway, we try what if it's not and the explicit nvidia-drm.modeset=1 helps to suppress the simpledrm device.
Then you're supposed to also add "nvidia.NVreg_PreserveVideoMemoryAllocations=0" to the kernel parameters and DISable all of nvidia-suspend.service, nvidia-hibernate.service, and nvidia-resume.service

axsc · 2024-11-12 23:52:48

seth wrote:

I missed that but when did "nomodeset" get introduced?
Don't use that.
Also it would be "nvidia-drm.modeset=1 nvidia_drm.fbdev=0", nvidia_drm.fbdev=1 is default anyway, we try what if it's not and the explicit nvidia-drm.modeset=1 helps to suppress the simpledrm device.
Then you're supposed to also add "nvidia.NVreg_PreserveVideoMemoryAllocations=0" to the kernel parameters and DISable all of nvidia-suspend.service, nvidia-hibernate.service, and nvidia-resume.service

That did it! The only "issue" now is that upon wakeup, only one of my two monitors shows the login screen. This is fine; everything else works as it should. I updated my original post with the exact steps that solved the issue.
Thank you Seth!!

seth · 2024-11-13 07:05:13

The kscreen daemon probably removes that output when it powers down (or because it's not powered up in time)

You can force the nvdia driver to report the output as enabled at all times, see /usr/share/doc/nvidia/README

FREQUENTLY ASKED TWINVIEW QUESTIONS

Q. Nothing gets displayed on my second monitor; what is wrong?

A. Monitors that do not support monitor detection using Display Data Channel
   (DDC) protocols (this includes most older monitors) are not detectable by
   your NVIDIA card. You need to explicitly tell the NVIDIA X driver what you
   have connected using the "ConnectedMonitor" option; e.g.,
   
       Option "ConnectedMonitor" "CRT, CRT"

The "CRT" there are placeholders.

Arch Linux

#1 2024-11-11 03:23:58

[SOLVED] Suspend and Wake Up Issues

#2 2024-11-11 08:33:23

Re: [SOLVED] Suspend and Wake Up Issues

#3 2024-11-11 19:50:32

Re: [SOLVED] Suspend and Wake Up Issues

#4 2024-11-11 20:15:07

Re: [SOLVED] Suspend and Wake Up Issues

#5 2024-11-12 00:09:46

Re: [SOLVED] Suspend and Wake Up Issues

#6 2024-11-12 09:26:21

Re: [SOLVED] Suspend and Wake Up Issues

#7 2024-11-12 13:09:04

Re: [SOLVED] Suspend and Wake Up Issues

#8 2024-11-12 14:12:26

Re: [SOLVED] Suspend and Wake Up Issues

#9 2024-11-12 23:52:48

Re: [SOLVED] Suspend and Wake Up Issues

#10 2024-11-13 07:05:13

Re: [SOLVED] Suspend and Wake Up Issues

Board footer