Arch Linux

paulr

Member

Registered: 2007-03-23

Posts: 59

Unsolved:Block individual hardware from USBHID

Morning.

I have an Arch System with a hardwired keyboard and a bluetooth mouse. It works fine.

However, there's a really annoying 24 second delay on boot because USBHID insists on checking the bluetooth device in the boot sequence, and it is timing out (YICHIP Wireless device ID 3151:3020). This seems to be a 6.18 change as I noticed it's doing the same thing on the Arch downloadable boot image now, and it didn't beforei (Jan->Feb 26). It gives an error -110 which I can't find much about.

I think it's an initialisation thing as it sometimes is okay from power on, but never on a reboot.

I tried blacklisting USBHID but this didn't work (and is too aggressive a solution anyway ?), may not be a module ?

Is there a way of getting USBHID to simply ignore this device ? Or would this disable the mouse ?

I did wonder if it's trying to find a bluetooth keyboard on the same adapter ? The weird thing is despite the error messages it works absolutely perfectly. It's just annoying

Thanks for any suggestions.

Last edited by paulr (2026-03-08 18:59:36)

paulr

Member

Registered: 2007-03-23

Posts: 59

Re: Unsolved:Block individual hardware from USBHID

Added a rule to /etc/udev/rules.dc called 81-yichip.rules

# Disable YICHIP
SUBSYSTEM=="usb", ATTRS{idVendor}=="3151", ATTRS{idProduct}=="3020", ATTR{authorized}="0"

paulr

Member

Registered: 2007-03-23

Posts: 59

Re: Unsolved:Block individual hardware from USBHID

Seemed to work initially, but didn't. I suspect some sort of initialisation state issue

mmy8x

Member

Registered: 2025-03-02

Posts: 93

Re: Unsolved:Block individual hardware from USBHID

However, there's a really annoying 24 second delay on boot because USBHID insists on checking the bluetooth device in the boot sequence, and it is timing out (YICHIP Wireless device ID 3151:3020). This seems to be a 6.18 change as I noticed it's doing the same thing on the Arch downloadable boot image now, and it didn't beforei (Jan->Feb 26). It gives an error -110 which I can't find much about.

Can you post the exact message if it's not a secret?
110 is an errno number which means timeout.

Did you try restoring 6.17 (or whatever used to work) from pacman cache or the package archive? If this helps then you have encountered a kernel regression which needs to be reported upstream.

If it doesn't help, we have recently seen many cases of USB bluetooth chips getting stuck and delaying boot until they are power cycled, which may require unplugging the machine from power and disconnecting the battery (if it has one).

Last edited by mmy8x (2026-03-09 06:43:42)

paulr

Member

Registered: 2007-03-23

Posts: 59

Re: Unsolved:Block individual hardware from USBHID

Doesn't really seem to be one

[    1.958479] hid-generic 0003:3151:3020.0004: input,hidraw3: USB HID v2.00 Keyboard [YICHIP Wireless Device] on usb-0000:08:00.3-4/input0

which I think is failing - is it looking for a keyboard which isn't there (I have a hardwired keyboard) ; shortly after there's a 20+ second delay ending with

[   27.607222] usbhid 5-4:1.1: can't add hid device: -110
[   27.607271] usbhid 5-4:1.1: probe with driver usbhid failed with error -110

6.17 worked okay. There was a point - not quite sure when - when the problem surfaced in the Arch Install image.

The odd thing is, it works perfectly. There's just an annoying 24 second delay on bootup (the timeout) - sometimes, well mostly - which explains the power cycling - but it always works.

mmy8x

Member

Registered: 2025-03-02

Posts: 93

Re: Unsolved:Block individual hardware from USBHID

I doubt that this dongle works, maybe your wired keyboard does but not this thing, unless somehow usbhid probes it later and succeeds on the second try.

It looks like a kernel bug or hardware gone bad (and kernel upgrade was unrelated). You can tell these cases apart by downgrading the kernel back to 6.17 or whichever version worked. If it still works on 6.17 then it's a bug and I'm afraid your only hope will be reporting it upstream. You can disconnect this dongle perhaps?

paulr

Member

Registered: 2007-03-23

Posts: 59

Re: Unsolved:Block individual hardware from USBHID

Oh it definitely works.  It works perfectly ; it just times out for 24 seconds on boot up. Sometimes it doesn't which suggests the same problem you describe, unplugging the battery, some sort of initialisation problem I presume. Every so often it boots perfectly, and there is no pattern (e.g. it sometimes happens on a reboot, sometimes on power up). Either way when it starts there is no problem.

It seems to be a Linux issue ; the same problem occurs on Fedora boot, but not on Ubuntu boot which is 6.17.something.

I noticed sometimes in the last 3-4 months it came into the Arch USB key boot, so I should be able to figure out the Kernel it was introduced in approximately by going back until it boots correctly. It's 6.18.something