Repository navigation
Description
Category
Driver loading/installation
Description
Hello,
I'm back with a new problem. When I power up my wheel for the first time after a restart, it does not connect. The small display on the wheel is stuck in the loading animation (3 dots) until it automatically powers off. sudo dmesg | grep logitech does not show anything besides the kernel module is loaded, aka. hid_logitech_dd: hid-logitech-dd v0.42.6 loaded.
It only connects to the pc, when I pull the usb & power cable for a few seconds and then replug them and power the wheel.
After that sudo dmesg | grep logitech looks like this:
[ 6.201427] hid_logitech_dd: hid-logitech-dd v0.42.6 loaded
[ 2528.457227] logitech-dd 0003:046D:C276.0009: RS50 (native): Claiming interface 0 for steering-position tracking
[ 2528.457307] logitech-dd 0003:046D:C276.0009: input,hidraw8: USB HID v1.11 Joystick [Logitech RS50 Base for PC] on usb-0000:00:14.0-7/input0
[ 2528.528918] logitech-dd 0003:046D:C276.000A: hiddev101,hidraw9: USB HID v1.11 Device [Logitech RS50 Base for PC] on usb-0000:00:14.0-7/input1
[ 2528.531887] logitech-dd 0003:046D:C276.000A: HID++ 4.2 device connected.
[ 2528.551966] logitech-dd 0003:046D:C276.000A: RS50 (native): Initializing force feedback...
[ 2528.552750] logitech-dd 0003:046D:C276.000B: RS50 (native): Letting hid-generic handle interface 2
[ 2528.552782] logitech-dd 0003:046D:C276.000B: hiddev102,hidraw10: USB HID v1.11 Device [Logitech RS50 Base for PC] on usb-0000:00:14.0-7/input2
[ 2528.706432] logitech-dd 0003:046D:C276.000A: RS50 (native): Effect timer ready (interval=1ms, 4 texture samples/tick, starts on effect play)
[ 2529.769862] logitech-dd 0003:046D:C276.000A: RS50 (native): serial 2528WDF083C8, base FW U1 65.04.B0039, motor FW SC 02.01.B0042
[ 2529.884874] logitech-dd 0003:046D:C276.000A: HID++ features (base): 8040=0A 807A=0B 807B=0C 80A4=0D 80D0=0E 8120=0F 8123=10 8127=11 8130=12 8132=13 8133=14 8134=15 8136=16 8137=17 8138=18 8139=19 8140=1A
[ 2529.932889] logitech-dd 0003:046D:C276.000A: RS50 (native): OLED: 10 layouts (wheel_oled)
[ 2529.939873] logitech-dd 0003:046D:C276.000A: RS50 (native): Current mode: onboard (profile 1)
[ 2530.011886] logitech-dd 0003:046D:C276.000A: RS50 (native): Force feedback initialized (full effect palette; conditions emulated host-side, textures via TrueForce)
[ 2546.817494] logitech-dd 0003:046D:C276.000A: RS50 (native): Force feedback unloaded
The wheel powers off from time to time and I have to restart it, but I can't reproduce that. It happens spontaneously.
Regards,
Johannes
Steps to Reproduce
- Load the driver
- Power on the wheel
Kernel Version
7.2.14-arch1-1
Driver version
v0.42.6
Distribution
Arch Linux
Installation Method
DKMS
dmesg Output
Current sysfs Values (if relevant)
Game/Application
No response
USB capture (recommended for FFB / wheel-state bugs)
No response
Checklist
- I installed the driver via setup.sh (or dkms-update.sh)
- I verified the driver loaded (
lsmod | grep hid_logitech_dd) - I checked dmesg for errors
Additional Context
No response
Activity
mescon commentedon Nov 2, 2026
Thanks, Johannes. In that log the wheel never reaches the driver: a module binds only after the USB device enumerates, and the grep hides the USB lines. One round, please:
sudo modprobe -r hid_logitech_ddbefore powering the wheel, then the same two commands.journalctl -k -frunning when it happens, and the lines around it.kangaro0 commentedon Nov 3, 2026
Hey, I took the wheel from power over night and also disconnected the usb cable. Right now it booted up perfectly fine and also a power cycle worked. So I just let it sit there powered on and read some news. After a while the wheel turned off and now it's not coming back up again. These are the logs:
Is this any helpful? I'll restart my pc next and then try to power on the wheel and come back with the new outputs.
kangaro0 commentedon Nov 3, 2026
Alright, I read your full comment after I rebooted. Sorry about that..
It was indeed the usb port. I connected the wheel to the front of my case, when I was testing for my earlier issue, because I can't reach the back so well.. I'm using a case with two usb 3.0 connectors at the front. I switched it now to the back of the pc into a usb 3.2 port and the wheel directly booted up without a problem.
Also the power offs are gone. I let it run for half an hour now and it's still up.
What I'm still wondering why the front is not working? Can it be power management? But that may be out of the scope of this issue. For now it's working as expected.
mescon commentedon Nov 3, 2026
Glad it is sorted, and thanks for the logs, they settle it. This is not power management:
disabled by hub (EMI?)and theerror -71descriptor reads are the host controller giving up on a link that is corrupting packets, so the kernel never gets as far as our driver. Front-panel ports sit at the end of a long internal header cable, and that is the first link to fail on a device like this. A rear port on the motherboard is the right home for the base.Closing as resolved. If it ever recurs on the rear port, reopen with the same two commands and we pick it up from there.