[Solved] Black screen when resuming from suspend (Keychron keyboard)

r0cz · 2025-11-05 15:53:54

Hello!

I've recently run in to some issues with resuming Arch.
I don't remember exactly when it started happening, and I've made no recent hardware changes.

I'm on a desktop PC. I have an NVIDIA card (3060Ti) and have all the related systemd units enabled (nvidia-suspend.service, nvidia-hibernate.service, and nvidia-resume.service).

My PC starts up and monitors power on, but I just have a black screen, and no inputs work - not even ctrl+alt+F-keys to switch TTY.

Here's my journal from the moment I run `systemctl suspend`, then the resume:

Nov 04 23:59:48 n0va systemd-logind[645]: The system will suspend now!
Nov 04 23:59:48 n0va systemd[1]: Created slice Slice /system/resume.
Nov 04 23:59:48 n0va systemd[1]: Reached target Sleep.
Nov 04 23:59:48 n0va systemd[1]: Starting NVIDIA system suspend actions...
Nov 04 23:59:48 n0va suspend[488017]: nvidia-suspend.service
Nov 04 23:59:48 n0va logger[488017]: <13>Nov  4 23:59:48 suspend: nvidia-suspend.service
Nov 04 23:59:49 n0va systemd[871]: Reached target Sound Card.
Nov 04 23:59:49 n0va systemd-logind[645]: Watching system buttons on /dev/input/event5 (Keychron Keychron Q3 Max System Control)
Nov 04 23:59:50 n0va systemd[1]: nvidia-suspend.service: Deactivated successfully.
Nov 04 23:59:50 n0va systemd[1]: Finished NVIDIA system suspend actions.
Nov 04 23:59:50 n0va systemd[1]: nvidia-suspend.service: Consumed 1.259s CPU time, 884.2M memory peak.
Nov 04 23:59:50 n0va systemd[1]: Starting System Suspend...
Nov 04 23:59:50 n0va systemd-sleep[488095]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
Nov 04 23:59:50 n0va systemd-sleep[488095]: This is not recommended, and might result in unexpected behavior, particularly
Nov 04 23:59:50 n0va systemd-sleep[488095]: in suspend-then-hibernate operations or setups with encrypted home directories.
Nov 04 23:59:50 n0va systemd-sleep[488095]: Performing sleep operation 'suspend'...
Nov 04 23:59:50 n0va kernel: PM: suspend entry (deep)
Nov 04 23:59:50 n0va kernel: Filesystems sync: 0.300 seconds

-- KEYBOARD PRESSED TO WAKE UP --

Nov 05 16:14:53 n0va kernel: Freezing user space processes
Nov 05 16:14:53 n0va kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Nov 05 16:14:53 n0va kernel: OOM killer disabled.
Nov 05 16:14:53 n0va kernel: Freezing remaining freezable tasks
Nov 05 16:14:53 n0va kernel: Freezing remaining freezable tasks completed (elapsed 0.000 seconds)
Nov 05 16:14:53 n0va kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Nov 05 16:14:53 n0va kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache
Nov 05 16:14:53 n0va kernel: sd 2:0:0:0: [sdc] Synchronizing SCSI cache
Nov 05 16:14:53 n0va systemd-sleep[488095]: System returned from sleep operation 'suspend'.
Nov 05 16:14:53 n0va kernel: ata2.00: Entering standby power mode
Nov 05 16:14:53 n0va systemd-resolved[517]: Clock change detected. Flushing caches.
Nov 05 16:14:53 n0va kernel: ata3.00: Entering standby power mode
Nov 05 16:14:53 n0va systemd-networkd[516]: enp6s0: Lost carrier
Nov 05 16:14:53 n0va kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Nov 05 16:14:53 n0va systemd-networkd[516]: enp6s0: Failed to send DHCP RELEASE, ignoring: Invalid argument
Nov 05 16:14:53 n0va kernel: ata1.00: Entering standby power mode
Nov 05 16:14:53 n0va systemd-networkd[516]: enp6s0: DHCP lease lost
Nov 05 16:14:53 n0va kernel: ACPI: PM: Preparing to enter system sleep state S3
Nov 05 16:14:53 n0va kernel: ACPI: PM: Saving platform NVS memory
Nov 05 16:14:53 n0va kernel: Disabling non-boot CPUs ...
Nov 05 16:14:53 n0va kernel: smpboot: CPU 15 is now offline
Nov 05 16:14:53 n0va kernel: smpboot: CPU 14 is now offline
Nov 05 16:14:53 n0va kernel: smpboot: CPU 13 is now offline
Nov 05 16:14:53 n0va kernel: smpboot: CPU 12 is now offline
Nov 05 16:14:53 n0va kernel: smpboot: CPU 11 is now offline
Nov 05 16:14:53 n0va kernel: smpboot: CPU 10 is now offline
Nov 05 16:14:53 n0va kernel: smpboot: CPU 9 is now offline
Nov 05 16:14:53 n0va kernel: smpboot: CPU 8 is now offline
Nov 05 16:14:53 n0va kernel: Spectre V2 : Update user space SMT mitigation: STIBP off
Nov 05 16:14:53 n0va kernel: smpboot: CPU 7 is now offline
Nov 05 16:14:53 n0va kernel: smpboot: CPU 6 is now offline
Nov 05 16:14:53 n0va kernel: smpboot: CPU 5 is now offline
Nov 05 16:14:53 n0va kernel: smpboot: CPU 4 is now offline
Nov 05 16:14:53 n0va kernel: smpboot: CPU 3 is now offline
Nov 05 16:14:53 n0va kernel: smpboot: CPU 2 is now offline
Nov 05 16:14:53 n0va kernel: smpboot: CPU 1 is now offline
Nov 05 16:14:53 n0va kernel: ACPI: PM: Low-level resume complete
Nov 05 16:14:53 n0va kernel: ACPI: PM: Restoring platform NVS memory
Nov 05 16:14:53 n0va kernel: AMD-Vi: Virtual APIC enabled
Nov 05 16:14:53 n0va kernel: AMD-Vi: Virtual APIC enabled
Nov 05 16:14:53 n0va kernel: LVT offset 0 assigned for vector 0x400
Nov 05 16:14:53 n0va kernel: Enabling non-boot CPUs ...
Nov 05 16:14:53 n0va kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Nov 05 16:14:53 n0va kernel: CPU1 is up
Nov 05 16:14:53 n0va kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Nov 05 16:14:53 n0va kernel: CPU2 is up
Nov 05 16:14:53 n0va kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Nov 05 16:14:53 n0va kernel: CPU3 is up
Nov 05 16:14:53 n0va kernel: smpboot: Booting Node 0 Processor 4 APIC 0x8
Nov 05 16:14:53 n0va kernel: CPU4 is up
Nov 05 16:14:53 n0va kernel: smpboot: Booting Node 0 Processor 5 APIC 0xa
Nov 05 16:14:53 n0va kernel: CPU5 is up
Nov 05 16:14:53 n0va kernel: smpboot: Booting Node 0 Processor 6 APIC 0xc
Nov 05 16:14:53 n0va kernel: CPU6 is up
Nov 05 16:14:53 n0va kernel: smpboot: Booting Node 0 Processor 7 APIC 0xe
Nov 05 16:14:53 n0va kernel: CPU7 is up
Nov 05 16:14:53 n0va kernel: smpboot: Booting Node 0 Processor 8 APIC 0x1
Nov 05 16:14:53 n0va kernel: Spectre V2 : Update user space SMT mitigation: STIBP always-on
Nov 05 16:14:53 n0va kernel: CPU8 is up
Nov 05 16:14:53 n0va kernel: smpboot: Booting Node 0 Processor 9 APIC 0x3
Nov 05 16:14:53 n0va kernel: CPU9 is up
Nov 05 16:14:53 n0va kernel: smpboot: Booting Node 0 Processor 10 APIC 0x5
Nov 05 16:14:53 n0va kernel: CPU10 is up
Nov 05 16:14:53 n0va kernel: smpboot: Booting Node 0 Processor 11 APIC 0x7
Nov 05 16:14:53 n0va kernel: CPU11 is up
Nov 05 16:14:53 n0va kernel: smpboot: Booting Node 0 Processor 12 APIC 0x9
Nov 05 16:14:53 n0va kernel: CPU12 is up
Nov 05 16:14:53 n0va kernel: smpboot: Booting Node 0 Processor 13 APIC 0xb
Nov 05 16:14:53 n0va kernel: CPU13 is up
Nov 05 16:14:53 n0va kernel: smpboot: Booting Node 0 Processor 14 APIC 0xd
Nov 05 16:14:53 n0va kernel: CPU14 is up
Nov 05 16:14:53 n0va kernel: smpboot: Booting Node 0 Processor 15 APIC 0xf
Nov 05 16:14:53 n0va kernel: CPU15 is up
Nov 05 16:14:53 n0va kernel: ACPI: PM: Waking up from system sleep state S3
Nov 05 16:14:53 n0va kernel: xhci_hcd 0000:01:00.0: xHC error in resume, USBSTS 0x401, Reinit
Nov 05 16:14:53 n0va kernel: usb usb1: root hub lost power or was reset
Nov 05 16:14:53 n0va kernel: usb usb2: root hub lost power or was reset
Nov 05 16:14:53 n0va kernel: nvme nvme0: D3 entry latency set to 8 seconds
Nov 05 16:14:53 n0va kernel: nvme nvme0: 16/0/0 default/read/poll queues
Nov 05 16:14:53 n0va kernel: usb 1-9: WARN: invalid context state for evaluate context command.
Nov 05 16:14:53 n0va kernel: ata6: SATA link down (SStatus 0 SControl 330)
Nov 05 16:14:53 n0va kernel: ata4: SATA link down (SStatus 0 SControl 300)
Nov 05 16:14:53 n0va kernel: ata5: SATA link down (SStatus 0 SControl 330)
Nov 05 16:14:53 n0va kernel: usb 1-9: reset full-speed USB device number 4 using xhci_hcd
Nov 05 16:14:53 n0va kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Nov 05 16:14:53 n0va systemd[1]: Starting Rotate log files...
Nov 05 16:14:53 n0va kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Nov 05 16:14:53 n0va kernel: ata1.00: supports DRM functions and may not be fully accessible
Nov 05 16:14:53 n0va kernel: ata3.00: supports DRM functions and may not be fully accessible
Nov 05 16:14:53 n0va kernel: sd 2:0:0:0: [sdc] Starting disk
Nov 05 16:14:53 n0va kernel: sd 0:0:0:0: [sda] Starting disk
Nov 05 16:14:53 n0va kernel: ata3.00: supports DRM functions and may not be fully accessible
Nov 05 16:14:53 n0va kernel: ata1.00: supports DRM functions and may not be fully accessible
Nov 05 16:14:53 n0va kernel: ata3.00: configured for UDMA/133
Nov 05 16:14:53 n0va kernel: ata1.00: configured for UDMA/133
Nov 05 16:14:53 n0va kernel: ahci 0000:01:00.1: port does not support device sleep
Nov 05 16:14:53 n0va kernel: ahci 0000:01:00.1: port does not support device sleep
Nov 05 16:14:53 n0va kernel: ata3.00: Enabling discard_zeroes_data
Nov 05 16:14:53 n0va kernel: ata1.00: Enabling discard_zeroes_data
Nov 05 16:14:53 n0va kernel: usb 1-7: reset high-speed USB device number 3 using xhci_hcd
Nov 05 16:14:53 n0va kernel: usb 1-6: WARN: invalid context state for evaluate context command.
Nov 05 16:14:53 n0va kernel: usb 1-6: reset full-speed USB device number 2 using xhci_hcd
Nov 05 16:14:53 n0va systemd[1]: Starting Update the plocate database...
Nov 05 16:14:53 n0va kernel: OOM killer enabled.
Nov 05 16:14:53 n0va kernel: Restarting tasks: Starting
Nov 05 16:14:53 n0va kernel: Restarting tasks: Done
Nov 05 16:14:53 n0va kernel: random: crng reseeded on system resumption
Nov 05 16:14:53 n0va kernel: PM: suspend exit
Nov 05 16:14:53 n0va systemd[1]: Started Verify integrity of password and group files.
Nov 05 16:14:53 n0va systemd[1]: Starting Hostname Service...
Nov 05 16:14:53 n0va systemd-timesyncd[412]: No network connectivity, watching for changes.
Nov 05 16:14:53 n0va sh[488224]: no matching password file entry in /etc/passwd
Nov 05 16:14:53 n0va sh[488224]: delete line 'testuser:!:19078:0:99999:7:::'? No
Nov 05 16:14:53 n0va sh[488224]: pwck: no changes
Nov 05 16:14:53 n0va sh[488225]: group media: no user testuser
Nov 05 16:14:53 n0va sh[488225]: delete member 'testuser'? No
Nov 05 16:14:53 n0va sh[488225]: shadow group media: no user testuser
Nov 05 16:14:53 n0va sh[488225]: delete member 'testuser'? No
Nov 05 16:14:53 n0va sh[488225]: grpck: no changes
Nov 05 16:14:53 n0va systemd[1]: logrotate.service: Deactivated successfully.
Nov 05 16:14:53 n0va systemd[1]: Finished Rotate log files.
Nov 05 16:14:53 n0va systemd[1]: shadow.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Nov 05 16:14:53 n0va systemd[1]: shadow.service: Failed with result 'exit-code'.
Nov 05 16:14:53 n0va systemd[1]: Started Hostname Service.
Nov 05 16:14:53 n0va systemd-hostnamed[488196]: Hostname set to <n0va> (static)
Nov 05 16:14:54 n0va systemd[1]: systemd-suspend.service: Deactivated successfully.
Nov 05 16:14:54 n0va systemd[1]: Finished System Suspend.
Nov 05 16:14:54 n0va systemd[1]: systemd-suspend.service: Consumed 1.247s CPU time, 3.2M memory peak.
Nov 05 16:14:54 n0va systemd[1]: Stopped target Sleep.
Nov 05 16:14:54 n0va systemd[1]: Reached target Suspend.
Nov 05 16:14:54 n0va systemd[1]: Starting NVIDIA system resume actions...
Nov 05 16:14:54 n0va systemd[1]: Started Resume triggers.
Nov 05 16:14:54 n0va systemd[1]: Stopped target Suspend.
Nov 05 16:14:54 n0va systemd-logind[645]: Operation 'suspend' finished.
Nov 05 16:14:54 n0va systemd-resolved[517]: Closing all remaining TCP connections.
Nov 05 16:14:54 n0va systemd-networkd[516]: enp6s0: Reconfiguring with /etc/systemd/network/10-wired.network.
Nov 05 16:14:54 n0va systemd-resolved[517]: Resetting learnt feature levels on all servers.
Nov 05 16:14:54 n0va suspend[488261]: nvidia-resume.service
Nov 05 16:14:54 n0va logger[488261]: <13>Nov  5 16:14:54 suspend: nvidia-resume.service
Nov 05 16:14:54 n0va systemd[1]: nvidia-resume.service: Deactivated successfully.
Nov 05 16:14:54 n0va systemd[1]: Finished NVIDIA system resume actions.
Nov 05 16:14:54 n0va systemd-logind[645]: Watching system buttons on /dev/input/event5 (Keychron Keychron Q3 Max System Control)
Nov 05 16:14:54 n0va wireplumber[889]: s-monitors: ALSA card/device alsa_card.usb-046d_HD_Pro_Webcam_C920-02 disabled
Nov 05 16:14:54 n0va wireplumber[889]: spa.bluez5: BlueZ system service is not available
Nov 05 16:14:55 n0va wireplumber[889]: m-portal-permissionstore: <WpPortalPermissionStorePlugin:0x55ec1bf70f80> Lookup: The name is not activatable (org.freedesktop.DBus.Error.ServiceUnknown)
Nov 05 16:14:56 n0va systemd-networkd[516]: enp6s0: Gained carrier
Nov 05 16:14:56 n0va kernel: igc 0000:06:00.0 enp6s0: NIC Link is Up 2500 Mbps Full Duplex, Flow Control: RX
Nov 05 16:14:56 n0va systemd-timesyncd[412]: Network configuration changed, trying to establish connection.
Nov 05 16:14:56 n0va systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
Nov 05 16:14:57 n0va kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Nov 05 16:14:57 n0va kernel: sd 1:0:0:0: [sdb] Starting disk
Nov 05 16:14:57 n0va kernel: ata2.00: configured for UDMA/133
Nov 05 16:14:59 n0va systemd-timesyncd[412]: Network configuration changed, trying to establish connection.
Nov 05 16:14:59 n0va systemd-networkd[516]: enp6s0: DHCPv4 address 10.0.0.48/24, gateway 10.0.0.1 acquired from 10.0.0.1
Nov 05 16:15:02 n0va systemd-timesyncd[412]: Contacted time server 217.198.219.102:123 (0.arch.pool.ntp.org).
Nov 05 16:15:06 n0va systemd[1]: plocate-updatedb.service: Deactivated successfully.
Nov 05 16:15:06 n0va systemd[1]: Finished Update the plocate database.
Nov 05 16:15:06 n0va systemd[1]: plocate-updatedb.service: Consumed 4.686s CPU time, 959.9M memory peak.
-- POWER RESET BUTTON PRESSED --

One part looked weird to me:

Nov 04 23:59:50 n0va systemd-sleep[488095]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
Nov 04 23:59:50 n0va systemd-sleep[488095]: This is not recommended, and might result in unexpected behavior, particularly
Nov 04 23:59:50 n0va systemd-sleep[488095]: in suspend-then-hibernate operations or setups with encrypted home directories.
Nov 04 23:59:50 n0va systemd-sleep[488095]: Performing sleep operation 'suspend'...

So I looked around and found this thread: https://bbs.archlinux.org/viewtopic.php?id=296954
They specifically mention a drop-in to set this, which I guess is already merged into the nvidia packages since I have it.

Anything else I can try?

Last edited by r0cz (2025-12-12 07:43:09)

seth · 2025-11-05 21:26:18

Sounds similar to https://bbs.archlinux.org/viewtopic.php?id=309900 - but apparently no intel device.
The system wakes up.

Nov 04 23:59:49 n0va systemd-logind[645]: Watching system buttons on /dev/input/event5 (Keychron Keychron Q3 Max System Control)

Do you have a $5 office supply keyboard?
https://bbs.archlinux.org/viewtopic.php?id=309618

From what context are you suspending? Does it work from the multi-user.target (2nd link below)?

r0cz · 2025-11-05 23:05:20

I tried a different keyboard but nothing changed.

What do you mean context? I just run "systemctl suspend" as my own user.

seth · 2025-11-06 08:24:53

What do you mean context?

console, X11 session (which) or wayland compositor (which)

r0cz · 2025-11-07 16:03:43

Oh, I suspend from a normal user session in i3 (Xorg)

seth · 2025-11-07 18:56:27

seth wrote:

Does it work from the multi-user.target (2nd link below)?

Do you run picom next to i3?

r0cz · 2025-12-10 21:40:03

seth wrote:

seth wrote:
Does it work from the multi-user.target (2nd link below)?
Do you run picom next to i3?

No, I don't run picom.

It works fine if I don't launch Xorg.

If my keyboard is disconnected when `systemctl suspend` happens, everything works as expected, interestingly.

Last edited by r0cz (2025-12-10 22:26:29)

seth · 2025-12-10 22:29:26

If my keyboard is disconnected when `systemctl suspend` happens, everything works as expected, interestingly.

seth wrote:

Do you have a $5 office supply keyboard?
https://bbs.archlinux.org/viewtopic.php?id=309618

I tried a different keyboard but nothing changed.

What was the "different keyboard"?

r0cz · 2025-12-10 22:31:56

seth wrote:

What was the "different keyboard"?

I didn't try a different keyboard (don't have one), but if I just do `sleep 5 && systemctl suspend`, then disconnect it before 5s, it will wake up normally.

It's a Keychron Q3 Max

seth · 2025-12-10 23:07:21

Can we please try to not intentionally mislead the thread?

It's a Keychron Q3 Max

Which fits the pattern perfectly.
See the other thread, check your xorg log whether it's also "Keyboard Joystick" and then adapt the udev rule at the tail of the thread.

r0cz · 2025-12-11 15:53:28

seth wrote:

See the other thread, check your xorg log whether it's also "Keyboard Joystick" and then adapt the udev rule at the tail of the thread.

Sorry, I completely missed the second link you posted..
I tried the test with chvt, and sure enough, it's the same problem as the tail mentions.

However, after applying the hwdb rule, nothing changed :(

There are a bunch of entries for the Keyboard as expected, and they all have the same ID_VENDOR_ID and ID_MODEL_ID. Here's one its built-in mouse:

P: /devices/pci0000:00/0000:00:01.2/0000:01:00.0/usb1/1-9/1-9:1.2/0003:3434:0831.0009/input/input22
M: input22
R: 22
J: +input:input22
U: input
E: DEVPATH=/devices/pci0000:00/0000:00:01.2/0000:01:00.0/usb1/1-9/1-9:1.2/0003:3434:0831.0009/input/input22
E: PRODUCT=3/3434/831/111
E: NAME="Keychron Keychron Q3 Max Mouse"
E: PHYS="usb-0000:01:00.0-9/input2"
E: UNIQ=""
E: PROP=0
E: EV=17
E: KEY=ff0000 0 0 0 0
E: REL=1943
E: MSC=10
E: MODALIAS=input:b0003v3434p0831e0111-e0,1,2,4,k110,111,112,113,114,115,116,117,r0,1,6,8,B,C,am4,lsfw
E: SUBSYSTEM=input
E: USEC_INITIALIZED=52080420
E: ID_INPUT=1
E: ID_INPUT_MOUSE=1
E: ID_BUS=usb
E: ID_MODEL=Keychron_Q3_Max
E: ID_MODEL_ENC=Keychron\x20Q3\x20Max
E: ID_MODEL_ID=0831
E: ID_SERIAL=Keychron_Keychron_Q3_Max
E: ID_VENDOR=Keychron
E: ID_VENDOR_ENC=Keychron
E: ID_VENDOR_ID=3434
E: ID_REVISION=0110
E: ID_TYPE=hid
E: ID_USB_MODEL=Keychron_Q3_Max
E: ID_USB_MODEL_ENC=Keychron\x20Q3\x20Max
E: ID_USB_MODEL_ID=0831
E: ID_USB_SERIAL=Keychron_Keychron_Q3_Max
E: ID_USB_VENDOR=Keychron
E: ID_USB_VENDOR_ENC=Keychron
E: ID_USB_VENDOR_ID=3434
E: ID_USB_REVISION=0110
E: ID_USB_TYPE=hid
E: ID_USB_INTERFACES=:030101:030000:
E: ID_USB_INTERFACE_NUM=02
E: ID_USB_DRIVER=usbhid
E: ID_PATH_WITH_USB_REVISION=pci-0000:01:00.0-usbv2-0:9:1.2
E: ID_PATH=pci-0000:01:00.0-usb-0:9:1.2
E: ID_PATH_TAG=pci-0000_01_00_0-usb-0_9_1_2
E: ID_FOR_SEAT=input-pci-0000_01_00_0-usb-0_9_1_2
E: TAGS=:seat:
E: CURRENT_TAGS=:seat:

I added the rule in /etc/udev/hwdb.d/70-keyboard.hwdb as mentioned:

id-input-modalias:input:*v3434p0831*
  ID_INPUT_JOYSTICK=

But the issue persists..

seth · 2025-12-11 16:25:00

stat /etc/udev/hwdb.d/70-keyboard.hwdb

and try

evdev:input:*v3434p0831*

That'd be the common pattern, there's no id-input-modalias anywhere in /usr/lib/udev/hwdb.d/ so I'm not sure the suggestion there is actually correct (sorry, didn't closely read the post before sharing it)

x-ref, https://bbs.archlinux.org/viewtopic.php … 5#p2277315

r0cz · 2025-12-11 16:48:50

seth wrote:

try

evdev:input:*v3434p0831*

It works!

Thank you so much

seth · 2025-12-11 17:20:43

In case this ends up being a fluke (the other thread does not work on the evdev pattern)

id-input-modalias:input:*v3434p0831*

should be

id-input:modalias:input:*v3434p0831*

(nb. the colon instead of dash before "modalias")

Otherwise and 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.

r0cz · 2025-12-12 07:42:27

Sure, thanks again for all the work you do for the Arch community!

Arch Linux

#1 2025-11-05 15:53:54

[Solved] Black screen when resuming from suspend (Keychron keyboard)

#2 2025-11-05 21:26:18

Re: [Solved] Black screen when resuming from suspend (Keychron keyboard)

#3 2025-11-05 23:05:20

Re: [Solved] Black screen when resuming from suspend (Keychron keyboard)

#4 2025-11-06 08:24:53

Re: [Solved] Black screen when resuming from suspend (Keychron keyboard)

#5 2025-11-07 16:03:43

Re: [Solved] Black screen when resuming from suspend (Keychron keyboard)

#6 2025-11-07 18:56:27

Re: [Solved] Black screen when resuming from suspend (Keychron keyboard)

#7 2025-12-10 21:40:03

Re: [Solved] Black screen when resuming from suspend (Keychron keyboard)

#8 2025-12-10 22:29:26

Re: [Solved] Black screen when resuming from suspend (Keychron keyboard)

#9 2025-12-10 22:31:56

Re: [Solved] Black screen when resuming from suspend (Keychron keyboard)

#10 2025-12-10 23:07:21

Re: [Solved] Black screen when resuming from suspend (Keychron keyboard)

#11 2025-12-11 15:53:28

Re: [Solved] Black screen when resuming from suspend (Keychron keyboard)

#12 2025-12-11 16:25:00

Re: [Solved] Black screen when resuming from suspend (Keychron keyboard)

#13 2025-12-11 16:48:50

Re: [Solved] Black screen when resuming from suspend (Keychron keyboard)

#14 2025-12-11 17:20:43

Re: [Solved] Black screen when resuming from suspend (Keychron keyboard)

#15 2025-12-12 07:42:27

Re: [Solved] Black screen when resuming from suspend (Keychron keyboard)

Board footer