You are not logged in.

#1 2023-08-10 21:43:56

jdb78
Member
Registered: 2023-08-10
Posts: 1

[SOLVED] Arch won't boot after update - keyboard does not work

Hello there. I use Arch for almost a year now and an update did not break my system up to now. I installed the update via pacman -Syu as usual and after a reboot I was stuck with the emergency rootfs. My keyboard does not work anymore. I do not have a PS/2 connector at my computer. Legacy USB is enabled in BIOS. I only have a photograph of the screen but I do not seem to be able to upload pictures here. The text goes something like:

Waiting 10 seconds for device /dev/disk/by-partuuid/2d9093a8-3b9f-494c-9a6e-83fd332e8cab ...
Waiting 10 seconds for device /dev/disk/by-partuuid/2d9093a8-3b9f-494c-9a6e-83fd332e8cab ...
ERROR: device 'PARTUUID=2d9093a8-3b9f-494c-9a6e-83fd332e8cab' not found. Skipping fsck.
: : mounting 'PARTUUID=2d9093a8-3b9f-494c-9a6e-83fd332e8cab' on real root
mount: /new_root: can't find PARTUUID=2d9093a8-3b9f-494c-9a6e-83fd332e8cab.
ERROR: Failed to mount 'PARTUUID=2d9093a8-3b9f-494c-9a6e-83fd332e8cab'  on real root
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off
[rootfs ~]#

But my keyboard does not even light up (RGB). I was able to create a new install pendrive with my laptop and boot it on my computer. I did manage to mount the btrfs NVME and chroot into the system. But I do not know how to fix my issue. Among the updated packages were the amd microcode and systemd package. New message when using mkinitcpio - p linux is "missing firmware xhci_pci". I use an Asus ROG Crosshair VII Hero with a Ryzen 7 2700X CPU if that is helpful.

Any help is appreciated since this is my main system.

EDIT: after I used the mkinitcpio -p linux I tried the bootctl install and after exiting the chroot and rebooting the system arch booted again. I don't know why this works but it does. I appreciate everybody who read this.

Last edited by jdb78 (2023-08-11 00:36:31)

Offline

#2 2023-11-09 14:16:44

NathanPB
Member
Registered: 2021-03-19
Posts: 1

Re: [SOLVED] Arch won't boot after update - keyboard does not work

Similar issue: After updating the system today and rebooting, my keyboard is acting unusable weird. Most of the keys don't even work and the ones that do are swapped between each other (Logitech G915), however I plugged in another old keyboard and it works just fine. Also, I tested the Logitech keyboard on my Windows side OS, and it works fine as well.

The rest of the system seems ok tho

UPDATE: I downgraded my kernel from 6.6.1 back to 6.5.9 and the issue was gone

Last edited by NathanPB (2023-11-09 14:25:16)

Offline

#3 2023-11-09 14:29:51

loqs
Member
Registered: 2014-03-06
Posts: 17,579

Re: [SOLVED] Arch won't boot after update - keyboard does not work

Offline

#4 2023-11-09 19:13:26

ArthurBorsboom
Member
Registered: 2014-05-20
Posts: 56

Re: [SOLVED] Arch won't boot after update - keyboard does not work

I am guessing that a similar problem exists for the Logitech G510s keyboard on kernel 6.6.1.

[    7.990759] sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:08.0/0000:07:00.0/0000:08:0c.0/0000:0c:00.0/usb1/1-3/1-3:1.1/0003:046D:C22D.000B/leds/g15::kbd_backlight/color'
[    7.990762] CPU: 4 PID: 451 Comm: (udev-worker) Tainted: G           OE      6.6.1-arch1-1 #1 be166a630cd909acf8820643140e9106c6ea80e6
[    7.990766] Hardware name: ASUS System Product Name/TUF GAMING X670E-PLUS WIFI, BIOS 1813 10/13/2023
[    7.990767] Call Trace:
[    7.990769]  <TASK>
[    7.990771]  dump_stack_lvl+0x47/0x60
[    7.990778]  sysfs_warn_dup+0x5a/0x70
[    7.990783]  sysfs_add_file_mode_ns+0x11a/0x130
[    7.990786]  internal_create_group+0x125/0x3b0
[    7.990789]  internal_create_groups+0x42/0xa0
[    7.990791]  device_add+0x5ad/0x8a0
[    7.990794]  ? srso_alias_return_thunk+0x5/0x7f
[    7.990798]  ? kstrdup+0x4c/0x70
[    7.990802]  device_create_groups_vargs+0xce/0xf0
[    7.990805]  device_create_with_groups+0x4b/0x70
[    7.990808]  led_classdev_register_ext+0x1d2/0x470
[    7.990812]  ? devm_led_classdev_register_ext+0x3a/0x90
[    7.990817]  devm_led_classdev_register_ext+0x50/0x90
[    7.990820]  lg_g15_probe+0x667/0x770 [hid_lg_g15 4a43fb61ec72c8e966287bea16924535918cb678]
[    7.990826]  hid_device_probe+0x10e/0x1a0
[    7.990829]  really_probe+0x19b/0x3e0
[    7.990833]  ? __pfx___device_attach_driver+0x10/0x10
[    7.990835]  __driver_probe_device+0x78/0x160
[    7.990838]  driver_probe_device+0x1f/0x90
[    7.990841]  __device_attach_driver+0x89/0x110
[    7.990844]  bus_for_each_drv+0x92/0xf0
[    7.990847]  __device_attach+0xb2/0x1b0
[    7.990850]  ? __pfx___hid_bus_reprobe_drivers+0x10/0x10
[    7.990853]  device_reprobe+0x4e/0x90
[    7.990855]  ? __hid_bus_reprobe_drivers+0x39/0x60
[    7.990857]  bus_for_each_dev+0x85/0xd0
[    7.990860]  ? __pfx___hid_bus_driver_added+0x10/0x10
[    7.990862]  __hid_bus_driver_added+0x2c/0x40
[    7.990865]  bus_for_each_drv+0x92/0xf0
[    7.990868]  __hid_register_driver+0x74/0x80
[    7.990871]  ? __pfx_ms_driver_init+0x10/0x10 [hid_microsoft a9a7eb35e2e5d1c3f68fd046c8c3a94730fe7fdb]
[    7.990876]  do_one_initcall+0x5a/0x320
[    7.990883]  do_init_module+0x60/0x240
[    7.990888]  init_module_from_file+0x89/0xe0
[    7.990894]  idempotent_init_module+0x120/0x2b0
[    7.990898]  __x64_sys_finit_module+0x5e/0xb0
[    7.990901]  do_syscall_64+0x5d/0x90
[    7.990904]  ? do_syscall_64+0x6c/0x90
[    7.990906]  ? srso_alias_return_thunk+0x5/0x7f
[    7.990908]  ? exit_to_user_mode_prepare+0x132/0x1f0
[    7.990911]  ? srso_alias_return_thunk+0x5/0x7f
[    7.990914]  ? syscall_exit_to_user_mode+0x2b/0x40
[    7.990916]  ? srso_alias_return_thunk+0x5/0x7f
[    7.990918]  ? do_syscall_64+0x6c/0x90
[    7.990920]  ? syscall_exit_to_user_mode+0x2b/0x40
[    7.990922]  ? srso_alias_return_thunk+0x5/0x7f
[    7.990924]  ? do_syscall_64+0x6c/0x90
[    7.990927]  entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[    7.990930] RIP: 0033:0x7f4ef790773d
[    7.990947] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 95 0c 00 f7 d8 64 89 01 48
[    7.990948] RSP: 002b:00007ffe65533e38 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
[    7.990951] RAX: ffffffffffffffda RBX: 000056078c53f520 RCX: 00007f4ef790773d
[    7.990952] RDX: 0000000000000004 RSI: 00007f4ef7e05376 RDI: 000000000000000e
[    7.990953] RBP: 00007f4ef7e05376 R08: 00005602ec2c7357 R09: fffffffffffffe90
[    7.990954] R10: 0000000000000050 R11: 0000000000000246 R12: 0000000000020000
[    7.990956] R13: 000056078c52e2f0 R14: 0000000000000000 R15: 000056078c527640
[    7.990960]  </TASK>

Offline

#5 2023-11-09 19:17:48

loqs
Member
Registered: 2014-03-06
Posts: 17,579

Re: [SOLVED] Arch won't boot after update - keyboard does not work

@ArthurBorsboom is the issue only present when using bluetooth?  Can you reproduce the issue with 9d1bd9346241cd6963b58da7ffb7ed303285f684 reverted?  Do you need such a kernel to test?

Offline

Board footer

Powered by FluxBB