Skip to content

[Bug] Wheel not connecting properly #141

Closed

Description

@kangaro0

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

  1. Load the driver
  2. 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

  1. mescon commented on Nov 2, 2026

    @mescon
    Owner

    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:

    1. After a failed power-up, the unfiltered tail and the tree:
    sudo dmesg | tail -60
    lsusb -t
    
    1. Does it still happen with the module out of the picture? sudo modprobe -r hid_logitech_dd before powering the wheel, then the same two commands.
    2. Is the base's USB cable in a motherboard port or a hub, and does another port change it? Was the cable plugged in before the PC booted?
    3. For the spontaneous power-offs: journalctl -k -f running when it happens, and the lines around it.
  2. kangaro0 commented on Nov 3, 2026

    @kangaro0
    Author

    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:

    sudo dmesg | tail -60
    [  213.283211] logitech-dd 0003:046D:C276.000B: RS50 (native): Letting hid-generic handle interface 2
    [  213.283400] 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
    [  213.435335] logitech-dd 0003:046D:C276.000A: RS50 (native): Effect timer ready (interval=1ms, 4 texture samples/tick, starts on effect play)
    [  214.204686] logitech-dd 0003:046D:C276.000A: RS50 (native): serial 2528WDF083C8, base FW U1 65.04.B0039, motor FW SC 02.01.B0042
    [  214.340684] 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
    [  214.390717] logitech-dd 0003:046D:C276.000A: RS50 (native): OLED: 10 layouts (wheel_oled)
    [  214.397714] logitech-dd 0003:046D:C276.000A: RS50 (native): Current mode: onboard (profile 1)
    [  214.475714] logitech-dd 0003:046D:C276.000A: RS50 (native): Force feedback initialized (full effect palette; conditions emulated host-side, textures via TrueForce)
    [  309.689695] usb 1-7: USB disconnect, device number 15
    [  309.702087] logitech-dd 0003:046D:C276.000A: RS50 (native): Force feedback unloaded
    [  321.183265] usb 1-7: new full-speed USB device number 16 using xhci_hcd
    [  321.295378] usb 1-7: Device not responding to setup address.
    [  321.508626] usb 1-7: device descriptor read/all, error -71
    [  321.620155] usb 1-7: new full-speed USB device number 17 using xhci_hcd
    [  321.732367] usb 1-7: device descriptor read/64, error -71
    [  321.952447] usb 1-7: Device not responding to setup address.
    [  322.172066] usb 1-7: New USB device found, idVendor=046d, idProduct=c276, bcdDevice=65.04
    [  322.173358] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [  322.173359] usb 1-7: Product: RS50 Base for PC
    [  322.173359] usb 1-7: Manufacturer: Logitech
    [  322.173360] usb 1-7: SerialNumber: 2528WDF083C8
    [  322.176902] logitech-dd 0003:046D:C276.000C: RS50 (native): Claiming interface 0 for steering-position tracking
    [  322.176930] input: Logitech RS50 Base for PC as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/0003:046D:C276.000C/input/input25
    [  322.177202] logitech-dd 0003:046D:C276.000C: input,hidraw8: USB HID v1.11 Joystick [Logitech RS50 Base for PC] on usb-0000:00:14.0-7/input0
    [  322.252208] logitech-dd 0003:046D:C276.000D: hiddev101,hidraw9: USB HID v1.11 Device [Logitech RS50 Base for PC] on usb-0000:00:14.0-7/input1
    [  322.254798] logitech-dd 0003:046D:C276.000D: HID++ 4.2 device connected.
    [  322.281018] logitech-dd 0003:046D:C276.000D: RS50 (native): Initializing force feedback...
    [  322.281807] logitech-dd 0003:046D:C276.000E: RS50 (native): Letting hid-generic handle interface 2
    [  322.281936] logitech-dd 0003:046D:C276.000E: hiddev102,hidraw10: USB HID v1.11 Device [Logitech RS50 Base for PC] on usb-0000:00:14.0-7/input2
    [  322.435115] logitech-dd 0003:046D:C276.000D: RS50 (native): Effect timer ready (interval=1ms, 4 texture samples/tick, starts on effect play)
    [  323.510913] logitech-dd 0003:046D:C276.000D: RS50 (native): serial 2528WDF083C8, base FW U1 65.04.B0039, motor FW SC 02.01.B0042
    [  323.648813] logitech-dd 0003:046D:C276.000D: 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
    [  323.696701] logitech-dd 0003:046D:C276.000D: RS50 (native): OLED: 10 layouts (wheel_oled)
    [  323.703696] logitech-dd 0003:046D:C276.000D: RS50 (native): Current mode: onboard (profile 1)
    [  323.779697] logitech-dd 0003:046D:C276.000D: RS50 (native): Force feedback initialized (full effect palette; conditions emulated host-side, textures via TrueForce)
    [  668.389722] usb usb1-port7: disabled by hub (EMI?), re-enabling...
    [  668.389728] usb 1-7: USB disconnect, device number 17
    [  668.407841] logitech-dd 0003:046D:C276.000D: RS50 (native): Force feedback unloaded
    [  668.624577] usb 1-7: new full-speed USB device number 18 using xhci_hcd
    [  668.737600] usb 1-7: device descriptor read/64, error -71
    [  668.970345] usb 1-7: device descriptor read/all, error -71
    [  669.081581] usb 1-7: new full-speed USB device number 19 using xhci_hcd
    [  669.193602] usb 1-7: device descriptor read/64, error -71
    [  669.413808] usb 1-7: Device not responding to setup address.
    [  669.633257] usb 1-7: device descriptor read/all, error -71
    [  669.633300] usb usb1-port7: attempt power cycle
    [  670.009573] usb 1-7: new full-speed USB device number 20 using xhci_hcd
    [  670.009806] usb 1-7: Device not responding to setup address.
    [  670.213673] usb 1-7: Device not responding to setup address.
    [  670.421565] usb 1-7: device not accepting address 20, error -71
    [  670.421625] usb 1-7: WARN: invalid context state for evaluate context command.
    [  670.534584] usb 1-7: new full-speed USB device number 21 using xhci_hcd
    [  670.546477] usb 1-7: device descriptor read/all, error -71
    [  670.546519] usb usb1-port7: unable to enumerate USB device
    
    lsusb -t
    /:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/16p, 480M
        |__ Port 002: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 004: Dev 003, If 0, Class=Hub, Driver=hub/6p, 480M
            |__ Port 001: Dev 005, If 0, Class=Human Interface Device, Driver=usbhid, 12M
            |__ Port 001: Dev 005, If 1, Class=Human Interface Device, Driver=usbhid, 12M
            |__ Port 002: Dev 006, If 0, Class=Human Interface Device, Driver=usbhid, 12M
            |__ Port 002: Dev 006, If 1, Class=Human Interface Device, Driver=usbhid, 12M
            |__ Port 002: Dev 006, If 2, Class=Human Interface Device, Driver=usbhid, 12M
            |__ Port 006: Dev 007, If 0, Class=Human Interface Device, Driver=usbhid, 480M
        |__ Port 005: Dev 004, If 0, Class=Audio, Driver=snd-usb-audio, 480M
        |__ Port 005: Dev 004, If 1, Class=Audio, Driver=snd-usb-audio, 480M
        |__ Port 005: Dev 004, If 2, Class=Audio, Driver=snd-usb-audio, 480M
        |__ Port 005: Dev 004, If 3, Class=Audio, Driver=snd-usb-audio, 480M
        |__ Port 005: Dev 004, If 4, Class=Audio, Driver=snd-usb-audio, 480M
        |__ Port 005: Dev 004, If 5, Class=Audio, Driver=snd-usb-audio, 480M
        |__ Port 005: Dev 004, If 6, Class=Audio, Driver=snd-usb-audio, 480M
        |__ Port 005: Dev 004, If 7, Class=Human Interface Device, Driver=usbhid, 480M
        |__ Port 011: Dev 008, If 0, Class=Vendor Specific Class, Driver=xpad, 12M
        |__ Port 011: Dev 008, If 1, Class=Vendor Specific Class, Driver=[none], 12M
        |__ Port 011: Dev 008, If 2, Class=Vendor Specific Class, Driver=[none], 12M
        |__ Port 012: Dev 009, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 013: Dev 010, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 014: Dev 011, If 0, Class=Wireless, Driver=btusb, 12M
        |__ Port 014: Dev 011, If 1, Class=Wireless, Driver=btusb, 12M
    /:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/9p, 20000M/x2
        |__ Port 002: Dev 002, If 0, Class=Audio, Driver=snd-usb-audio, 5000M
        |__ Port 002: Dev 002, If 1, Class=Audio, Driver=snd-usb-audio, 5000M
        |__ Port 002: Dev 002, If 2, Class=Audio, Driver=snd-usb-audio, 5000M
        |__ Port 002: Dev 002, If 3, Class=Audio, Driver=snd-usb-audio, 5000M
        |__ Port 003: Dev 003, If 0, Class=Hub, Driver=hub/3p, 5000M
    

    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.

  3. kangaro0 commented on Nov 3, 2026

    @kangaro0
    Author

    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.

  4. mescon commented on Nov 3, 2026

    @mescon
    Owner

    Glad it is sorted, and thanks for the logs, they settle it. This is not power management: disabled by hub (EMI?) and the error -71 descriptor 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions