You are not logged in.

#1 2020-08-31 02:41:04

bassp
Member
Registered: 2019-04-11
Posts: 8

If I move my mouse during startup, kernel cannot detect it as input.

My mouse is a Logitech G305 wireless.

The issue can be consistently reproduced when I move my mouse during the kernel splash screen, before the X server starts.

during the times when it is unsuccessful (the cursor gets stuck and it cannot do anything), this shows up in dmesg:

[    4.260080] logitech-djreceiver 0003:046D:C53F.0008: hidraw7: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:14.0-5/input0
[    4.486422] logitech-djreceiver 0003:046D:C53F.0009: hiddev2,hidraw8: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:14.0-5/input1
[    4.542883] logitech-djreceiver 0003:046D:C53F.000A: hiddev3,hidraw9: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-5/input2

during the times when it is successful (if I don't move it):

[   94.833015] logitech-djreceiver 0003:046D:C53F.0008: hidraw7: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:14.0-5/input0
[   95.143876] logitech-djreceiver 0003:046D:C53F.0009: hiddev2,hidraw8: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:14.0-5/input1
[   95.200547] logitech-djreceiver 0003:046D:C53F.000A: hiddev3,hidraw9: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-5/input2
[   95.258018] input: Logitech Wireless Mouse PID:4074 Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.2/0003:046D:C53F.000A/0003:046D:4074.000E/input/input39
[   95.258642] input: Logitech Wireless Mouse PID:4074 Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.2/0003:046D:C53F.000A/0003:046D:4074.000E/input/input40
[   95.259003] hid-generic 0003:046D:4074.000E: input,hidraw13: USB HID v1.11 Keyboard [Logitech Wireless Mouse PID:4074] on usb-0000:00:14.0-5/input2:1
[   95.631523] input: Logitech G305 as /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.2/0003:046D:C53F.000A/0003:046D:4074.000E/input/input44
[   95.632251] logitech-hidpp-device 0003:046D:4074.000E: input,hidraw13: USB HID v1.11 Keyboard [Logitech G305] on usb-0000:00:14.0-5/input2:1

I've tried the fix with adding hid-logitech-hidpp to the kernel modules, but that didn't fix anything. The problem continues. Installing solaar didn't fix the issue (since it still gets stuck, it begins to move after 30 seconds after logging in)


these commands allows me to reload the mouse:
sudo rmmod hid_logitech_dj
sudo modprobe hid_logitech_dj

This doesn't happen with wired mice.

I am unsure about the exact cause, but I suspect libinput. Maybe there is a race condition where if I flood the logitech djreceiver with inputs, it prevents libinput from identifying the device.

Can someone help me?

Last edited by bassp (2020-08-31 02:43:14)

Offline

#2 2020-08-31 02:47:48

Ropid
Member
Registered: 2015-03-09
Posts: 1,069

Re: If I move my mouse during startup, kernel cannot detect it as input.

I think I might have the same problem. I also have a G305 and sometimes it's not there when I boot and log in. I never thought about this being because of the mouse moving, I thought the problem was random. When the problem happens here for me, I unplug the receiver and plug it back in, this then makes it show up in the Xorg log and in xinput and start working.

Offline

#3 2020-08-31 05:52:41

bassp
Member
Registered: 2019-04-11
Posts: 8

Re: If I move my mouse during startup, kernel cannot detect it as input.

Yeah. Try moving it precisely before xorg boots up.

I tried the archwiki page describing Logitech's unifying usb, but none of the configurations worked.

Offline

#4 2020-08-31 08:38:11

bassp
Member
Registered: 2019-04-11
Posts: 8

Re: If I move my mouse during startup, kernel cannot detect it as input.

I did some further research, it seems that this is a bug that appeared all the way back in 2012, and it seems that by moving the mouse before hid_logitech_dj is loaded, the entire process fails.

https://bugs.launchpad.net/ubuntu/+sour … bug/958174

Comment #40

Offline

Board footer

Powered by FluxBB