You are not logged in.
KERNEL PANIC FIXED!
For some reason, openrazer broke with the update, and that meant that the initramfs could not be rebuilt. I uninstalled all openrazer-associated packages, and rebuilt.
Why openrazer does not work and whether it's related to some of the disfunction I'm seeing, I don't know. But my computer is bootable again.
Offline
I have made the edits to my Nvidia configuration as suggested. I can successfully enter a suspend state. Resuming from suspend is still broken; it appears to leave suspend, but nothing appears on any monitor, as before.
Here is the last journal from the last experiment.
I may roll back my drivers to the old ones at least temporarily, because now they just don't work and I cannot play games; prime-run glxgears is not working, and sometimes hangs the whole system.
Last edited by NTGuardian (2026-05-15 18:50:04)
Offline
[Edit: there're no obvious problems w/ the wakeup, so we go for a general cleanup spree]
nvidia_drm.modeset=1 nvidia_drm.fbdev=0
"nvidia_drm.modeset=1" is default, don't disable "nvidia_drm.fbdev=0"
May 15 14:43:02 ArkhamComputing pipewire-media-session[1460]: Failed to get percentage from UPower: org.freedesktop.DBus.Error.NameHasNoOwner
https://wiki.archlinux.org/title/PipeWi … ia_Session is deprecated bitrot
You're concurrently running dhcpcd and systemd-networkd, pick one, disable the other.
Disable asusd and nvidia-powerd, https://wiki.archlinux.org/title/CPU_fr … dia-powerd
May 15 14:42:41 ArkhamComputing nvidia-powerd[840]: ERROR! DC power limits table is not supported
May 15 14:42:41 ArkhamComputing nvidia-powerd[840]: ERROR! Failed to get SysPwrLimitGetInfo!!
May 15 14:42:41 ArkhamComputing nvidia-powerd[840]: ERROR! Client (presumably SBIOS) has requested to disable Dynamic Boost DC controllerand certainly plymouth!
Then disable https://wiki.archlinux.org/title/NVIDIA … er_suspend
nb. next to the "nvidia.PreserveVideoMemoryAllocations=0" kernel parameter you also *have* to disable the userspace services
(The background here is that nvidia needs to switch the VT, what we know triggers then problem when attempting to return to X11, cause pending)
Last edited by seth (2026-05-15 21:39:21)
Offline
[Edit: there're no obvious problems w/ the wakeup, so we go for a general cleanup spree]
I believe I have done everything you requested in the clean-up spree.
Because the 580xx drivers do not always seem to work for my computer, sometimes I uninstall them between experiments, then reinstall them when trying to resolve this issue. So I am using the 580xx packages for the attached logs, but will uninstall them once this is done (and reinstall when trying to fix this again) if they seem to not be working, since I want to be able to use the Nvidia graphics card to play games.
Here are the logs for a failed hibernate attempt. Same behavior.
Last edited by NTGuardian (2026-05-18 05:38:07)
Offline
May 18 01:14:34 ArkhamComputing systemd[1]: Starting Terminate Plymouth Boot Screen...
May 18 01:14:34 ArkhamComputing systemd[1]: Received SIGRTMIN+21 from PID 598 (plymouthd).
May 18 01:14:34 ArkhamComputing systemd[1]: Finished Terminate Plymouth Boot Screen.
May 18 01:17:55 ArkhamComputing sudo[3157]: curtis : TTY=pts/0 ; PWD=/home/curtis/Documents ; USER=root ; COMMAND=/bin/systemctl hibernate
May 18 01:17:55 ArkhamComputing systemd-logind[842]: The system will hibernate now!
May 18 01:17:55 ArkhamComputing systemd[1]: Starting System Hibernate...
May 18 01:17:55 ArkhamComputing systemd-sleep[3161]: in suspend-then-hibernate operations or setups with encrypted home directories.
May 18 01:17:55 ArkhamComputing systemd-sleep[3161]: Performing sleep operation 'hibernate'...
May 18 01:18:46 ArkhamComputing systemd-sleep[3161]: System returned from sleep operation 'hibernate'.
May 18 01:18:46 ArkhamComputing systemd[1]: systemd-hibernate.service: Deactivated successfully.
May 18 01:18:46 ArkhamComputing systemd[1]: Finished System Hibernate.
May 18 01:18:46 ArkhamComputing systemd[1]: systemd-hibernate.service: Consumed 2.089s CPU time over 7.517s wall clock time, 2.9M memory peak.
May 18 01:18:46 ArkhamComputing kernel: efivarfs: removing variable HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67
May 18 01:18:46 ArkhamComputing systemd-logind[842]: Operation 'hibernate' finished.
May 18 01:19:11 ArkhamComputing systemd[1]: plymouth-quit.service: Deactivated successfully.
May 18 01:19:11 ArkhamComputing systemd[1]: Stopped Terminate Plymouth Boot Screen.
May 18 01:19:11 ArkhamComputing mkinitcpio[3514]: -> Running build hook: [plymouth-shutdown]
May 18 01:19:12 ArkhamComputing systemd[1]: Starting Show Plymouth Power Off Screen...Disable … certainly plymouth!
W/ the VT switching condition and absent any other explanation for the failure it's the single most suspicious element.
Edit: for clarification, I mean to boot with out it, no plymouth anywhere, including not in the initramfs.
Last edited by seth (2026-05-18 08:55:11)
Offline
W/ the VT switching condition and absent any other explanation for the failure it's the single most suspicious element.
Edit: for clarification, I mean to boot with out it, no plymouth anywhere, including not in the initramfs.
I don't know why Plymouth is still showing up; I removed it from my mkinitcpio.conf.
HOOKS=(base systemd autodetect modconf keyboard sd-vconsole block filesystems fsck)It is no longer in the boot options:
options root=PARTUUID=9f614fa0-75cd-4c1a-bf3f-4fee468145de resume=PARTUUID=9f614fa0-75cd-4c1a-bf3f-4fee468145de resume_offset=189797632 rcutree.gp_init_delay=1 rw quiet(Yes, I rebuilt, using mkinitcpio -P.) As an extra precaution, I also masked all Plymouth systemd services, with the following command:
sudo systemctl mask $(for f in $(ls /usr/lib/systemd/system/plymouth-*); do; basename $f; done)Here is the new set of logs. Plymouth shows up once:
May 18 15:39:52 ArkhamComputing mkinitcpio[2065]: -> Running build hook: [plymouth-shutdown]I don't know why that's there or how to remove it.
Last edited by NTGuardian (2026-05-18 19:49:56)
Offline
So, assuming it still fails, it's not plymouth either.
(You btw. don't have to hibernate for testing, pretty sure that causes the same problem as the VT switch)
Returning to the input device vector, we tested w/o the external keyboard/mouse but there's oc
May 18 15:38:12 ArkhamComputing kernel: i2c_dev: i2c /dev entries driver
May 18 15:38:12 ArkhamComputing systemd-modules-load[542]: Inserted module 'i2c_dev'
May 18 15:38:13 ArkhamComputing kernel: input: ELAN1201:00 04F3:3098 Mouse as /devices/platform/AMDI0010:03/i2c-0/i2c-ELAN1201:00/0018:04F3:3098.000C/input/input24
May 18 15:38:13 ArkhamComputing kernel: input: ELAN1201:00 04F3:3098 Touchpad as /devices/platform/AMDI0010:03/i2c-0/i2c-ELAN1201:00/0018:04F3:3098.000C/input/input25
May 18 15:38:13 ArkhamComputing kernel: hid-generic 0018:04F3:3098.000C: input,hidraw11: I2C HID v1.00 Mouse [ELAN1201:00 04F3:3098] on i2c-ELAN1201:00
May 18 15:38:13 ArkhamComputing kernel: i2c i2c-1: Successfully instantiated SPD at 0x51
May 18 15:38:13 ArkhamComputing kernel: i2c i2c-3: Successfully instantiated SPD at 0x50
May 18 15:38:13 ArkhamComputing kernel: i2c i2c-3: Successfully instantiated SPD at 0x51
May 18 15:38:13 ArkhamComputing kernel: input: ELAN1201:00 04F3:3098 Mouse as /devices/platform/AMDI0010:03/i2c-0/i2c-ELAN1201:00/0018:04F3:3098.000C/input/input27
May 18 15:38:13 ArkhamComputing kernel: input: ELAN1201:00 04F3:3098 Touchpad as /devices/platform/AMDI0010:03/i2c-0/i2c-ELAN1201:00/0018:04F3:3098.000C/input/input28
May 18 15:38:13 ArkhamComputing kernel: hid-multitouch 0018:04F3:3098.000C: input,hidraw11: I2C HID v1.00 Mouse [ELAN1201:00 04F3:3098] on i2c-ELAN1201:00and i assume
May 18 15:38:10 archlinux kernel: usb 1-3: Product: N-KEY Device
May 18 15:38:10 archlinux kernel: input: ASUSTeK Computer Inc. N-KEY Device as /devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-3/1-3:1.0/0003:0B05:19B6.0002/input/input6
May 18 15:38:10 archlinux kernel: input: ASUSTeK Computer Inc. N-KEY Device Consumer Control as /devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-3/1-3:1.0/0003:0B05:19B6.0002/input/input7
May 18 15:38:10 archlinux kernel: input: ASUSTeK Computer Inc. N-KEY Device as /devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-3/1-3:1.0/0003:0B05:19B6.0002/input/input8
May 18 15:38:10 archlinux kernel: input: ASUSTeK Computer Inc. N-KEY Device as /devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-3/1-3:1.0/0003:0B05:19B6.0002/input/input9
May 18 15:38:10 archlinux kernel: hid-generic 0003:0B05:19B6.0002: input,hiddev97,hidraw1: USB HID v1.10 Device [ASUSTeK Computer Inc. N-KEY Device] on usb-0000:04:00.3-3/input0
May 18 15:38:10 archlinux kernel: hid-generic 0003:0B05:19B6.0003: hiddev98,hidraw2: USB HID v1.10 Device [ASUSTeK Computer Inc. N-KEY Device] on usb-0000:04:00.3-3/input1
May 18 15:38:10 archlinux kernel: input: ASUSTeK Computer Inc. N-KEY Device as /devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-3/1-3:1.2/0003:0B05:19B6.0004/input/input10
May 18 15:38:10 archlinux kernel: hid-generic 0003:0B05:19B6.0004: input,hidraw3: USB HID v1.10 Keyboard [ASUSTeK Computer Inc. N-KEY Device] on usb-0000:04:00.3-3/input2
May 18 15:38:10 archlinux kernel: asus 0003:0B05:19B6.0002: Fixing up Asus N-Key report descriptor
May 18 15:38:10 archlinux kernel: input: ASUSTeK Computer Inc. N-KEY Device as /devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-3/1-3:1.0/0003:0B05:19B6.0002/input/input11
May 18 15:38:10 archlinux kernel: asus 0003:0B05:19B6.0002: input,hiddev97,hidraw1: USB HID v1.10 Device [ASUSTeK Computer Inc. N-KEY Device] on usb-0000:04:00.3-3/input0
May 18 15:38:10 archlinux kernel: asus 0003:0B05:19B6.0003: hiddev98,hidraw2: USB HID v1.10 Device [ASUSTeK Computer Inc. N-KEY Device] on usb-0000:04:00.3-3/input1
May 18 15:38:10 archlinux kernel: input: ASUSTeK Computer Inc. N-KEY Device as /devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-3/1-3:1.2/0003:0B05:19B6.0004/input/input12
May 18 15:38:10 archlinux kernel: asus 0003:0B05:19B6.0004: input,hidraw3: USB HID v1.10 Keyboard [ASUSTeK Computer Inc. N-KEY Device] on usb-0000:04:00.3-3/input2
May 18 15:38:14 ArkhamComputing systemd-logind[736]: Watching system buttons on /dev/input/event5 (ASUSTeK Computer Inc. N-KEY Device)
May 18 15:38:14 ArkhamComputing systemd-logind[736]: Watching system buttons on /dev/input/event6 (ASUSTeK Computer Inc. N-KEY Device)
May 18 15:38:27 ArkhamComputing systemd-logind[736]: Watching system buttons on /dev/input/event6 (ASUSTeK Computer Inc. N-KEY Device)
May 18 15:38:27 ArkhamComputing systemd-logind[736]: Watching system buttons on /dev/input/event5 (ASUSTeK Computer Inc. N-KEY Device)
May 18 15:38:40 ArkhamComputing systemd-logind[736]: Watching system buttons on /dev/input/event5 (ASUSTeK Computer Inc. N-KEY Device)
May 18 15:38:40 ArkhamComputing systemd-logind[736]: Watching system buttons on /dev/input/event6 (ASUSTeK Computer Inc. N-KEY Device)
May 18 15:39:36 ArkhamComputing systemd-logind[736]: Watching system buttons on /dev/input/event5 (ASUSTeK Computer Inc. N-KEY Device)
May 18 15:39:36 ArkhamComputing systemd-logind[736]: Watching system buttons on /dev/input/event6 (ASUSTeK Computer Inc. N-KEY Device)
May 18 15:39:52 ArkhamComputing systemd-logind[736]: Watching system buttons on /dev/input/event5 (ASUSTeK Computer Inc. N-KEY Device)
May 18 15:39:52 ArkhamComputing systemd-logind[736]: Watching system buttons on /dev/input/event6 (ASUSTeK Computer Inc. N-KEY Device)is the internal keyboard?
What if you disable those (for libinput)
https://wiki.archlinux.org/title/Libinp … t_variable
04F3:3098
0B05:19B6
Keyboard btw. also shows up in https://bbs.archlinux.org/viewtopic.php?id=308256
Offline