Possible USB file missing?

WilsonPhillips · September 22, 2026, 3:36pm

This is a fresh install from a week ago. Wootility can see the keyboard, but cannot sync it. Worked fine on OpenMandriva installed in June. OpenRGB can see motherboard and works fine, but it doesn’t see USB devices and gives me the error about i2c-dev modules not loaded. This used to work on Tumbleweed with no issues.

I have tried everything I can think of. I tried everything I read to do. I am down to thinking that I am missing a file, but I don’t know which file it might be. What command do I need to run, to see what I am missing?

Kernel: Linux 7.2.6-1.0.10.sr20260901-default
Uptime: 3 hours, 24 mins
Packages: 17 (flatpak), 2901 (rpm)
Shell: bash 5.3.15
Display (AW3423DWF): 3440x1440 in 34", 100 Hz [External]
DE: KDE Plasma 6.7.5
WM: KWin (Wayland)
WM Theme: Breeze
Theme: Breeze (openSUSEdark) [Qt], Breeze-Dark [GTK2], Breeze [GTK3/4]
Icons: breeze-dark [Qt], breeze-dark [GTK2/3/4]
Font: Liberation Sans (12pt) [Qt], Liberation Sans (12pt) [GTK2/3/4]
Cursor: Breeze_Light (30px)
Terminal: konsole 26.8.1
Terminal Font: Liberation Mono (13pt)
CPU: AMD Ryzen 9 7900X (24) @ 5.74 GHz
GPU 1: Intel Arc B580 @ 2.85 GHz [Discrete]
GPU 2: AMD Raphael [Integrated]
Memory: 3.60 GiB / 30.50 GiB (12%)
Swap: 0 B / 30.50 GiB (0%)
Disk (/): 63.20 GiB / 952.87 GiB (7%) - btrfs
Disk (/4TB-HDD): 1.17 TiB / 3.64 TiB (32%) - fuseblk
Disk (/4TB-SSD1): 68.34 GiB / 3.67 TiB (2%) - ext4
Disk (/4TB-SSD2): 64.71 GiB / 3.67 TiB (2%) - ext4
Disk (/Windows): 73.88 GiB / 930.70 GiB (8%) - fuseblk

╔═⦗😀wilson@heisenberg⦘ Tue Sep 22, 10:31:50 [~]
╚═⦗<$> lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 13d3:3571 IMC Networks Bluetooth Radio
Bus 001 Device 003: ID 31e3:1232 Wooting Wooting Two HE (ARM)
Bus 001 Device 004: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 005 Device 003: ID b58e:9e84 Blue Microphones Yeti Stereo Microphone
Bus 005 Device 004: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 005 Device 005: ID 30be:100c Schiit Audio Schiit Modi+
Bus 005 Device 006: ID 0bda:5409 Realtek Semiconductor Corp. USB2.1 Hub
Bus 005 Device 007: ID 1532:0098 Razer USA, Ltd Razer DeathAdder Essential
Bus 005 Device 008: ID 1050:0407 Yubico.com Yubikey 4/5 OTP+U2F+CCID
Bus 005 Device 009: ID 187c:100e Alienware Corporation HID Device
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Any clues?

Yes, I have 60-openrgb.rules and it installed with OpenRGB.
Yes, I have 51-wooting.rules and it installed with the Wooting utility from brave.
Yes, I did the modprobe command.

WilsonPhillips · September 22, 2026, 7:06pm

I was looking at zypper-rdepends-plugin, but it is not available in Slowroll. Besides, I wouldn’t know where to start with it. How many days would it take to run it on glibc? Or would another package be suspect?

deano_ferrari · September 22, 2026, 7:44pm

The lsusb output shows that both the Wooting keyboard and the other USB devices are being detected, so not a missing USB driver.

Show the results from

lsmod | grep -E 'i2c|hid'
ls -l /dev/i2c-* /dev/hidraw*

WilsonPhillips · September 22, 2026, 7:52pm

<$> lsmod | grep -E 'i2c|hid'
hid_generic            12288  0
usbhid                 94208  0
i2c_algo_bit           24576  2 amdgpu,xe
usbcore               487424  7 xhci_hcd,snd_usb_audio,usbhid,snd_usbmidi_lib,btmtk,btusb,xhci_pci
i2c_piix4              40960  0
i2c_smbus              20480  1 i2c_piix4
i2c_dev                28672  0

⦗<$> ls -l /dev/i2c-* /dev/hidraw*
crw-rw----@ 1  244,0 root 22 Sep 07:07 /dev/hidraw0
crw-rw----@ 1  244,1 root 22 Sep 07:07 /dev/hidraw1
crw-rw----@ 1  244,2 root 22 Sep 07:07 /dev/hidraw2
crw-rw----@ 1  244,3 root 22 Sep 07:07 /dev/hidraw3
crw-rw----@ 1  244,4 root 22 Sep 07:07 /dev/hidraw4
crw-rw----@ 1  244,5 root 22 Sep 07:07 /dev/hidraw5
crw-rw----@ 1  244,6 root 22 Sep 07:07 /dev/hidraw6
crw-rw----@ 1  244,7 root 22 Sep 07:07 /dev/hidraw7
crw-rw----@ 1  244,8 root 22 Sep 07:07 /dev/hidraw8
crw-rw----@ 1  244,9 root 22 Sep 07:07 /dev/hidraw9
crw-rw----@ 1 244,10 root 22 Sep 07:07 /dev/hidraw10
crw-rw----@ 1 244,11 root 22 Sep 07:07 /dev/hidraw11
crw-rw----@ 1 244,12 root 22 Sep 07:07 /dev/hidraw12
crw-rw----@ 1   89,0 root 22 Sep 07:07 /dev/i2c-0
crw-rw----@ 1   89,1 root 22 Sep 07:07 /dev/i2c-1
crw-rw----@ 1   89,2 root 22 Sep 07:07 /dev/i2c-2
crw-rw----@ 1   89,3 root 22 Sep 07:07 /dev/i2c-3
crw-rw----@ 1   89,4 root 22 Sep 07:07 /dev/i2c-4
crw-rw----@ 1   89,5 root 22 Sep 07:07 /dev/i2c-5
crw-rw----@ 1   89,6 root 22 Sep 07:07 /dev/i2c-6
crw-rw----@ 1   89,7 root 22 Sep 07:07 /dev/i2c-7
crw-rw----@ 1   89,8 root 22 Sep 07:07 /dev/i2c-8
crw-rw----@ 1   89,9 root 22 Sep 07:07 /dev/i2c-9
crw-rw----@ 1  89,10 root 22 Sep 07:07 /dev/i2c-10
crw-rw----@ 1  89,11 root 22 Sep 07:07 /dev/i2c-11
crw-rw----@ 1  89,12 root 22 Sep 07:07 /dev/i2c-12
crw-rw----@ 1  89,13 root 22 Sep 07:07 /dev/i2c-13
crw-rw----@ 1  89,14 root 22 Sep 07:07 /dev/i2c-14
crw-rw----@ 1  89,15 root 22 Sep 07:07 /dev/i2c-15
crw-rw----@ 1  89,16 root 22 Sep 07:07 /dev/i2c-16
crw-rw----@ 1  89,17 root 22 Sep 07:07 /dev/i2c-17
crw-rw----@ 1  89,18 root 22 Sep 07:07 /dev/i2c-18
crw-rw----@ 1  89,19 root 22 Sep 07:07 /dev/i2c-19

WilsonPhillips · September 22, 2026, 7:57pm

Thanks for looking at this @deano_ferrari . Maybe you will see something. To me, it just looks like it should work.

deano_ferrari · September 22, 2026, 8:47pm

The permissions look a bit different than what I expected. No group assigned?

Post the output from id as well.

Also

udevadm test /sys/class/hidraw/hidraw0 2>&1 | grep -E 'wooting|openrgb|GROUP|MODE|uaccess'

…to see if the udev rules are being applied to the device, and what permissions/tags any matching udev rules are applying.

deano_ferrari · September 22, 2026, 8:52pm

Could you also show us

cat /etc/udev/rules.d/60-openrgb.rules
cat /etc/udev/rules.d/51-wooting.rules

I’m not familiar with either OpenRGB or Wootility, so just trying to help with some low-level device diagnostics. Hopefully, others can chime in with further advice.

WilsonPhillips · September 22, 2026, 9:11pm

⦗<$> id
uid=1000(wilson) gid=1000(wilson) groups=1000(wilson),1001(i2c),1002(plugdev) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023

/etc/udev/rules.d/60-openrgb.rules
If I put it here, I get an error that I can't have two of them. The other one was placed at /usr/lib/udev/rules.d/ and I will attach it as a text file.

/etc/udev/rules.d/51-wooting.rules
ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="ff01", TAG+="uaccess"
ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="ff02", TAG+="uaccess"

deano_ferrari · September 22, 2026, 10:48pm

At first glance, the wooting.rules don’t match your keyboard hardware product code reported from lsusb…
Bus 001 Device 003: ID 31e3:1232 Wooting Wooting Two HE (ARM)

WilsonPhillips · September 22, 2026, 11:33pm

I did some more digging on their side and found another set of rules to apply. The keyboard is connected as soon as I open the web app in the browser.

# Wooting Two HE (ARM) - Standard Mode
SUBSYSTEM=="hidraw", ATTRS{idVendor}=="31e3", ATTRS{idProduct}=="1230", MODE:="0660", GROUP="input"
SUBSYSTEM=="usb", ATTRS{idVendor}=="31e3", ATTRS{idProduct}=="1230", MODE:="0660", GROUP="input"

# Wooting Two HE (ARM) - Update Mode
SUBSYSTEM=="hidraw", ATTRS{idVendor}=="31e3", ATTRS{idProduct}=="123f", MODE:="0660", GROUP="input"
SUBSYSTEM=="usb", ATTRS{idVendor}=="31e3", ATTRS{idProduct}=="123f", MODE:="0660", GROUP="input"

One or more I2C/SMBus interfaces failed to initialize.
Depending on which interfaces failed to initialize, some RGB DRAM modules, some motherboards' onboard RGB lighting, and RGB graphics cards may not be available in OpenRGB.
On Linux, this is usually because the i2c-dev module is not loaded.
For OpenRGB to access these devices, you must load the i2c-dev module along with the correct I2C driver module for your motherboard. This is usually i2c-piix4 for AMD systems and i2c-i801 for Intel systems.

I still get the error on OpenRGB when I open it, but it keeps the LEDs in the case from the default rainbow colors. It doesn’t see the LEDs on everything, but I can live with it and ignore the error message.

Thanks @deano_ferrari for the help.

deano_ferrari · September 23, 2026, 1:40am

Glad you got it working. Those additional udev rules explain why the keyboard can be accessed when the web app switches between its normal and update modes.

system · September 30, 2026, 1:41am

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.