You are not logged in.

Pages: 1

#1 2026-03-15 11:29:26

Antares2619
Member
Registered: 2026-03-15
Posts: 6

Mouse not correctly recognized during boot

Issue
I use a wireless 2.4Ghz USB mouse with an up-to-date Arch system. The mouse used to work as expected in wireless mode for several weeks, but starting few days ago, the cursor became unresponsive when entering KDE after system boot, as if the mouse and the 2.4Ghz dongle were not communicating.

Debugging

  • The cursor works as expected inside the motherboard UEFI.

  • The cursor works as expected in the desktop environment after I unplug and replug the 2.4Ghz dongle.

  • Below, I compare dmesg output at boot for the mouse (and wireless keyboard with separate dongle) with the same output for the mouse if I plug its 2.4Ghz dongle after boot. The printed serial number for the mouse is different in the two cases, and the serial number printed at boot seems wrong and varies too.


At boot (for mouse and keyboard cause of overlap):

    0.956047] usb 3-4: new full-speed USB device number 2 using xhci_hcd
[    0.962790] ata1: SATA link down (SStatus 0 SControl 330)
[    1.009044] usb 1-3: new full-speed USB device number 2 using xhci_hcd
[    1.105239] usb 3-4: New USB device found, idVendor=0b05, idProduct=1a94, bcdDevice= 6.02
[    1.105242] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    1.105245] usb 3-4: Product: ROG HARPE ACE AIM LAB EDITION
[    1.105247] usb 3-4: Manufacturer: ASUSTeK
[    1.105248] usb 3-4: SerialNumber: NAMPGDD09721\xc2\x9c\x17
[    1.127370] hid-generic 0003:0B05:1A94.0001: hiddev96,hidraw0: USB HID v1.11 Device [ASUSTeK ROG HARPE ACE AIM LAB EDITION] on usb-0000:2d:00.3-4/input0
[    1.135349] input: ASUSTeK ROG HARPE ACE AIM LAB EDITION as /devices/pci0000:00/0000:00:08.1/0000:2d:00.3/usb3/3-4/3-4:1.1/0003:0B05:1A94.0002/input/input2
[    1.135404] hid-generic 0003:0B05:1A94.0002: input,hidraw1: USB HID v1.11 Mouse [ASUSTeK ROG HARPE ACE AIM LAB EDITION] on usb-0000:2d:00.3-4/input1
[    1.143375] input: ASUSTeK ROG HARPE ACE AIM LAB EDITION Consumer Control as /devices/pci0000:00/0000:00:08.1/0000:2d:00.3/usb3/3-4/3-4:1.2/0003:0B05:1A94.0003/input/input3
[    1.194099] input: ASUSTeK ROG HARPE ACE AIM LAB EDITION System Control as /devices/pci0000:00/0000:00:08.1/0000:2d:00.3/usb3/3-4/3-4:1.2/0003:0B05:1A94.0003/input/input4
[    1.194147] input: ASUSTeK ROG HARPE ACE AIM LAB EDITION as /devices/pci0000:00/0000:00:08.1/0000:2d:00.3/usb3/3-4/3-4:1.2/0003:0B05:1A94.0003/input/input5
[    1.194199] input: ASUSTeK ROG HARPE ACE AIM LAB EDITION Keyboard as /devices/pci0000:00/0000:00:08.1/0000:2d:00.3/usb3/3-4/3-4:1.2/0003:0B05:1A94.0003/input/input6
[    1.194284] hid-generic 0003:0B05:1A94.0003: input,hiddev97,hidraw2: USB HID v1.11 Keyboard [ASUSTeK ROG HARPE ACE AIM LAB EDITION] on usb-0000:2d:00.3-4/input2
[    1.274780] ata2: SATA link down (SStatus 0 SControl 330)
[    1.378508] usb 1-3: New USB device found, idVendor=0b05, idProduct=193e, bcdDevice= 3.04
[    1.378514] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    1.378516] usb 1-3: Product: ROG FALCHION
[    1.378518] usb 1-3: Manufacturer: ASUSTeK
[    1.404662] input: ASUSTeK ROG FALCHION as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3:1.0/0003:0B05:193E.0004/input/input7
[    1.455761] hid-generic 0003:0B05:193E.0004: input,hidraw3: USB HID v1.11 Keyboard [ASUSTeK ROG FALCHION] on usb-0000:02:00.0-3/input0
[    1.460628] hid-generic 0003:0B05:193E.0005: hiddev98,hidraw4: USB HID v1.11 Device [ASUSTeK ROG FALCHION] on usb-0000:02:00.0-3/input1
[    1.470419] input: ASUSTeK ROG FALCHION Consumer Control as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3:1.2/0003:0B05:193E.0006/input/input8
[    1.521609] input: ASUSTeK ROG FALCHION System Control as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3:1.2/0003:0B05:193E.0006/input/input9
[    1.521665] input: ASUSTeK ROG FALCHION as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3:1.2/0003:0B05:193E.0006/input/input10
[    1.521718] input: ASUSTeK ROG FALCHION Mouse as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3:1.2/0003:0B05:193E.0006/input/input11
[    1.521798] hid-generic 0003:0B05:193E.0006: input,hiddev99,hidraw5: USB HID v1.11 Mouse [ASUSTeK ROG FALCHION] on usb-0000:02:00.0-3/input2
[    1.525324] input: ASUSTeK ROG FALCHION as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3:1.3/0003:0B05:193E.0007/input/input12
[    1.576597] hid-generic 0003:0B05:193E.0007: input,hidraw6: USB HID v1.11 Keyboard [ASUSTeK ROG FALCHION] on usb-0000:02:00.0-3/input3
[    1.589892] ata3: SATA link down (SStatus 0 SControl 330)

After boot (for mouse):

[  311.967559] usb 3-4: new full-speed USB device number 3 using xhci_hcd
[  312.117262] usb 3-4: New USB device found, idVendor=0b05, idProduct=1a94, bcdDevice= 6.02
[  312.117268] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  312.117270] usb 3-4: Product: ROG HARPE ACE AIM LAB EDITION
[  312.117272] usb 3-4: Manufacturer: ASUSTeK
[  312.117274] usb 3-4: SerialNumber: NAMPGDD09721
[  312.139425] hid-generic 0003:0B05:1A94.0009: hiddev96,hidraw0: USB HID v1.11 Device [ASUSTeK ROG HARPE ACE AIM LAB EDITION] on usb-0000:2d:00.3-4/input0
[  312.147373] input: ASUSTeK ROG HARPE ACE AIM LAB EDITION as /devices/pci0000:00/0000:00:08.1/0000:2d:00.3/usb3/3-4/3-4:1.1/0003:0B05:1A94.000A/input/input26
[  312.147489] hid-generic 0003:0B05:1A94.000A: input,hidraw1: USB HID v1.11 Mouse [ASUSTeK ROG HARPE ACE AIM LAB EDITION] on usb-0000:2d:00.3-4/input1
[  312.155397] input: ASUSTeK ROG HARPE ACE AIM LAB EDITION Consumer Control as /devices/pci0000:00/0000:00:08.1/0000:2d:00.3/usb3/3-4/3-4:1.2/0003:0B05:1A94.000B/input/input27
[  312.205755] input: ASUSTeK ROG HARPE ACE AIM LAB EDITION System Control as /devices/pci0000:00/0000:00:08.1/0000:2d:00.3/usb3/3-4/3-4:1.2/0003:0B05:1A94.000B/input/input28
[  312.205835] input: ASUSTeK ROG HARPE ACE AIM LAB EDITION as /devices/pci0000:00/0000:00:08.1/0000:2d:00.3/usb3/3-4/3-4:1.2/0003:0B05:1A94.000B/input/input29
[  312.205901] input: ASUSTeK ROG HARPE ACE AIM LAB EDITION Keyboard as /devices/pci0000:00/0000:00:08.1/0000:2d:00.3/usb3/3-4/3-4:1.2/0003:0B05:1A94.000B/input/input30
[  312.206012] hid-generic 0003:0B05:1A94.000B: input,hiddev97,hidraw2: USB HID v1.11 Keyboard [ASUSTeK ROG HARPE ACE AIM LAB EDITION] on usb-0000:2d:00.3-4/input2

Last edited by Antares2619 (2026-03-15 13:05:34)

Offline

#2 2026-03-15 14:19:36

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 73,785

Re: Mouse not correctly recognized during boot

The cursor works as expected in the desktop environment after I unplug and replug the 2.4Ghz dongle.

https://wiki.archlinux.org/title/Power_ … utosuspend
Though because of

the cursor became unresponsive when entering KDE after system boot

this could also be powerdevil

Below, I compare dmesg output at boot for the mouse

Random isolated lines from dmesg (the second set just shows the dongle being recognized, it's way too late to explain why it would not work before; the first one ends 1.5s into the boot, so likely way before you log into KDE) won't help anything here.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#3 2026-03-15 19:33:36

Antares2619
Member
Registered: 2026-03-15
Posts: 6

Re: Mouse not correctly recognized during boot

I have added a udev rule to blacklist the mouse from autosuspend. Below is where I looked for verification: 

$ cat /sys/bus/usb/devices/3-4/product
ROG HARPE ACE AIM LAB EDITION
$ cat /sys/bus/usb/devices/3-4/idProduct
1a94
$ cat /sys/bus/usb/devices/3-4/idVendor
0b05
$ cat /sys/bus/usb/devices/3-4/power/autosuspend
-1

Unfortunately this change did not solve the issue. I will try to look further into power management and powerdevil.

seth wrote:

Random isolated lines from dmesg (the second set just shows the dongle being recognized, it's way too late to explain why it would not work before; the first one ends 1.5s into the boot, so likely way before you log into KDE) won't help anything here.

For clarity, the sequence of events is the following:

  1. The system starts booting with dongle plugged and mouse ON. This is when the kernel prints the first set.

  2. The system starts the desktop environment.

  3. I verify that the cursor is not responsive.

  4. I unplug and re-plug the dongle. This is when the kernel prints the second set.

  5. I verify that the cursor is responsive.

Anyway I am posting the entire dmesg output of a similar session where I replicated the same sequence of events. Perhaps it's more helpful: https://pastebin.com/mwkdpN6A

Last edited by Antares2619 (2026-03-15 19:37:22)

Offline

#4 2026-03-15 21:38:21

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 73,785

Re: Mouse not correctly recognized during boot

The system journal for the boot will put this into userspace context

sudo journalctl -b | curl -F 'file=@-' 0x0.st
[   16.920906] warning: `conky' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
[   39.650296] usb 3-4: USB disconnect, device number 2
[   42.159841] usb 3-4: new full-speed USB device number 3 using xhci_hcd

17s in conky starts (indicating your session?), 24s later the dongle disconnects (likely you pulling it), 3s later it's plugged back.

The system starts the desktop environment.

Do you autologin? Does the mouse work before your start the GUI session (either in the DM or you can test "evtest" or "libinput debug-events" on the console)

Do you use any bluetooth devices?
Can you disable the BT chip? (It will operate on the same radio band as the dongle)

Is this a dual-boot system (ie. is there a parallel windows)?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#5 2026-03-16 12:02:17

Antares2619
Member
Registered: 2026-03-15
Posts: 6

Re: Mouse not correctly recognized during boot

I think we are making progress smile The mouse input seems to reach the OS, but for some reason it is not reflected on the cursor.

The mouse seems to work in tty according to evtest, and evtest also shows mouse inputs being received correctly at boot in Alacritty inside KDE! However, the cursor won't move neither in KDE nor in the DM (plasma login) until I unplug and replug the dongle...
Here is journalctl following the same 1-5 sequence of events from my previous post. To answer the rest, yes I normally use autologin and I disabled it while testing with evtest. I keep bluetooth and wlan disabled by default through rfkill. And no dual boot, but the mouse works as expected in a different computer with windows.

Last edited by Antares2619 (2026-03-16 14:25:45)

Offline

#6 2026-03-16 14:28:24

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 73,785

Re: Mouse not correctly recognized during boot

What if you only start the multi-user.target 2nd link below) and
1. explicitly start plasmalogin from there
2. start kde manually, https://wiki.archlinux.org/title/KDE#From_the_console
3. startx some X11 session (openbox or naked X11 server will do - we only care whether the mouse moves)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#7 2026-03-16 19:35:07

Antares2619
Member
Registered: 2026-03-15
Posts: 6

Re: Mouse not correctly recognized during boot

I booted into TTY and tried the different cases below. In all of those cases, the mouse pointer did not move until I unplugged and replugged the dongle.

1) Plasmalogin from TTY: 

$ sudo systemctl start plasmalogin

2) Plasma/Wayland from TTY: 

$ /usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland

3) Plasma/X11 from TTY (I have also tried a minimal X11 case with openbox): 

$ sudo pacman -Sy xorg-server xorg-xinit openbox
$ echo "export DESKTOP_SESSION=plasma
exec startplasma-x11" > ~/.xinitrc
$ startx

###
On a side note, this might be nothing, but it still seems strange to me that this line during boot: 

[1.105248] usb 3-4: SerialNumber: NAMPGDD09721\xc2\x9c\x17

becomes this second line when I unplug and replug the dongle after boot: 

[312.117274] usb 3-4: SerialNumber: NAMPGDD09721

And that difference is more starking in journalctl, where that first line is reported as: 

archlinux kernel: [38B blob data]

Last edited by Antares2619 (2026-03-16 20:00:12)

Offline

#8 2026-03-16 20:33:41

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 73,785

Re: Mouse not correctly recognized during boot

On a side note, this might be nothing, but it still seems strange to me that this line during boot:

That's usually a sign that the controller hasn't fully/properly initialized when the device is probed - do you have this (and the symptoms) also on warm boots (reboot w/o powering off)
Can you try the dongle in a different slot?

Plasma/X11 from TTY (I have also tried a minimal X11 case with openbox):

And please post your ~/.local/share/xorg/Xorg.0.log

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#9 2026-03-17 17:24:53

Antares2619
Member
Registered: 2026-03-15
Posts: 6

Re: Mouse not correctly recognized during boot

That's usually a sign that the controller hasn't fully/properly initialized when the device is probed - do you have this (and the symptoms) also on warm boots (reboot w/o powering off)
Can you try the dongle in a different slot?

The dongle is usually in the front panel. I just tried a USB port in the back panel with same result. I have the same result also during warm boots.

And please post your ~/.local/share/xorg/Xorg.0.log

The log prints some error about the mouse starting at [768.826] as x11 initializes, and no error later when I remove and insert the dongle. That seems informative to me, but you would know better: https://0x0.st/P9Ke.txt

Last edited by Antares2619 (2026-03-17 17:31:57)

Offline

#10 2026-03-17 20:54:03

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 73,785

Re: Mouse not correctly recognized during boot

There's first some "ASUSTeK ROG FALCHION", then 

[   768.827] (EE) libinput: ASUSTeK ROG HARPE ACE AIM LAB EDITION: Failed to create a device for /dev/input/event2
[   768.827] (EE) PreInit returned 2 for "ASUSTeK ROG HARPE ACE AIM LAB EDITION"

and only when you re-plug the device

[   790.371] (II) config/udev: Adding input device ASUSTeK ROG HARPE ACE AIM LAB EDITION (/dev/input/mouse0)
[   790.403] (II) config/udev: Adding input device ASUSTeK ROG HARPE ACE AIM LAB EDITION Consumer Control (/dev/input/event3)
[   790.403] (**) ASUSTeK ROG HARPE ACE AIM LAB EDITION Consumer Control: Applying InputClass "libinput keyboard catchall"
[   790.403] (II) Using input driver 'libinput' for 'ASUSTeK ROG HARPE ACE AIM LAB EDITION Consumer Control'
[   790.404] (**) ASUSTeK ROG HARPE ACE AIM LAB EDITION Consumer Control: always reports core events

so this checks out.

Does https://www.baeldung.com/linux/usb-devi … et-command suffice to make the mouse work in the display server?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#11 2026-03-19 21:12:46

Antares2619
Member
Registered: 2026-03-15
Posts: 6

Re: Mouse not correctly recognized during boot

It seems no sad The pointer refuses to move even after I try to reset the device via software. I tried with the 'usbreset', 'sysfs', and 'udevadm' methods in order. 

Mar 19 22:08:36 pc-nico sudo[1979]:     nico : TTY=pts/1 ; PWD=/home/nico ; USER=root ; COMMAND=/usr/bin/usbreset 001/002
Mar 19 22:08:36 pc-nico sudo[1979]: pam_unix(sudo:session): session opened for user root(uid=0) by nico(uid=1000)
Mar 19 22:08:36 pc-nico kernel: usb 1-3: reset full-speed USB device number 2 using xhci_hcd
Mar 19 22:08:37 pc-nico sudo[1979]: pam_unix(sudo:session): session closed for user root
Mar 19 22:09:05 pc-nico sudo[2020]:     nico : TTY=pts/1 ; PWD=/home/nico ; USER=root ; COMMAND=/usr/bin/tee /sys/bus/usb/devices/1-3/authorized
Mar 19 22:09:05 pc-nico sudo[2020]: pam_unix(sudo:session): session opened for user root(uid=0) by nico(uid=1000)
Mar 19 22:09:05 pc-nico sudo[2020]: pam_unix(sudo:session): session closed for user root
Mar 19 22:09:10 pc-nico sudo[2033]:     nico : TTY=pts/1 ; PWD=/home/nico ; USER=root ; COMMAND=/usr/bin/tee /sys/bus/usb/devices/1-3/authorized
Mar 19 22:09:10 pc-nico sudo[2033]: pam_unix(sudo:session): session opened for user root(uid=0) by nico(uid=1000)
Mar 19 22:09:10 pc-nico kernel: hid-generic 0003:0B05:1A94.000D: hiddev98,hidraw3: USB HID v1.11 Device [ASUSTeK ROG HARPE ACE AIM LAB EDITION] on usb-0000:02:00.0-3/input0
Mar 19 22:09:10 pc-nico kernel: input: ASUSTeK ROG HARPE ACE AIM LAB EDITION as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3:1.1/0003:0B05:1A94.000E/input/input37
Mar 19 22:09:10 pc-nico kernel: hid-generic 0003:0B05:1A94.000E: input,hidraw4: USB HID v1.11 Mouse [ASUSTeK ROG HARPE ACE AIM LAB EDITION] on usb-0000:02:00.0-3/input1
Mar 19 22:09:10 pc-nico kernel: input: ASUSTeK ROG HARPE ACE AIM LAB EDITION Consumer Control as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3:1.2/0003:0B05:1A94.000F/input/input38
Mar 19 22:09:10 pc-nico kernel: input: ASUSTeK ROG HARPE ACE AIM LAB EDITION System Control as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3:1.2/0003:0B05:1A94.000F/input/input39
Mar 19 22:09:10 pc-nico kernel: input: ASUSTeK ROG HARPE ACE AIM LAB EDITION as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3:1.2/0003:0B05:1A94.000F/input/input40
Mar 19 22:09:10 pc-nico kernel: input: ASUSTeK ROG HARPE ACE AIM LAB EDITION Keyboard as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3:1.2/0003:0B05:1A94.000F/input/input41
Mar 19 22:09:10 pc-nico sudo[2033]: pam_unix(sudo:session): session closed for user root
Mar 19 22:09:10 pc-nico kernel: hid-generic 0003:0B05:1A94.000F: input,hiddev99,hidraw5: USB HID v1.11 Keyboard [ASUSTeK ROG HARPE ACE AIM LAB EDITION] on usb-0000:02:00.0-3/input2
Mar 19 22:09:10 pc-nico kernel: usb 1-3: authorized to connect
Mar 19 22:09:10 pc-nico kwin_wayland[909]: Failed to open /dev/input/event9 device (No such device)
Mar 19 22:09:10 pc-nico systemd-logind[747]: Watching system buttons on /dev/input/event10 (ASUSTeK ROG HARPE ACE AIM LAB EDITION Keyboard)
Mar 19 22:09:10 pc-nico kwin_wayland[909]: Failed to open /dev/input/event10 device (No such device)
Mar 19 22:09:10 pc-nico systemd-logind[747]: Watching system buttons on /dev/input/event8 (ASUSTeK ROG HARPE ACE AIM LAB EDITION System Control)
Mar 19 22:09:10 pc-nico kwin_wayland[909]: Failed to open /dev/input/event7 device (No such device)
Mar 19 22:09:10 pc-nico kwin_wayland[909]: Failed to open /dev/input/event8 device (No such device)
Mar 19 22:09:10 pc-nico kwin_wayland[909]: Failed to open /dev/input/event6 device (No such device)
Mar 19 22:09:33 pc-nico sudo[2088]:     nico : TTY=pts/1 ; PWD=/home/nico ; USER=root ; COMMAND=/usr/bin/udevadm trigger --action=add /sys/bus/usb/devices/1-3
Mar 19 22:09:33 pc-nico sudo[2088]: pam_unix(sudo:session): session opened for user root(uid=0) by nico(uid=1000)
Mar 19 22:09:33 pc-nico sudo[2088]: pam_unix(sudo:session): session closed for user root
Mar 19 22:09:33 pc-nico mtp-probe[2093]: checking bus 1, device 2: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3"
Mar 19 22:09:33 pc-nico mtp-probe[2093]: bus: 1, device: 2 was not an MTP device
Mar 19 22:09:33 pc-nico systemd-logind[747]: Watching system buttons on /dev/input/event8 (ASUSTeK ROG HARPE ACE AIM LAB EDITION System Control)
Mar 19 22:09:33 pc-nico kwin_wayland[909]: Failed to open /dev/input/event8 device (No such device)
Mar 19 22:09:33 pc-nico systemd-logind[747]: Watching system buttons on /dev/input/event10 (ASUSTeK ROG HARPE ACE AIM LAB EDITION Keyboard)
Mar 19 22:09:33 pc-nico kwin_wayland[909]: Failed to open /dev/input/event10 device (No such device)
Mar 19 22:09:33 pc-nico kwin_wayland[909]: Failed to open /dev/input/event7 device (No such device)
Mar 19 22:09:33 pc-nico kwin_wayland[909]: Failed to open /dev/input/event9 device (No such device)
Mar 19 22:09:33 pc-nico kwin_wayland[909]: Failed to open /dev/input/event6 device (No such device)

I have the same issue with this mouse on a separate Arch system too. It worked just fine until a couple of weeks ago, so the issue is likely either something broken with the mouse, or a software update somewhere that broke the functionality.

Last edited by Antares2619 (Yesterday 16:00:09)

Offline

#12 Yesterday 16:23:03

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 73,785

Re: Mouse not correctly recognized during boot

so the issue is likely either something broken with the mouse, or a software update somewhere that broke the functionality

https://grml.org/

Only writing /sys/bus/usb/devices/1-3/authorized caused a response, what if you only boot the multi-user.target (2nd link below) re-authorize the device and then manually progress to the graphical.target (or start plasma)?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

Pages: 1

Board footer

Powered by FluxBB