Ross Brown

> @RobotRoss I closed your other report as duplicate then. You can apply the setting permanently: > > ``` > # /etc/modprobe.d/xpadneo.conf > options hid-xpadneo ff_connect_notify=0 > ``` > >...

Sorry - this is an issue separate to that. Rumble no longer works regardless of the status of that setting. The controller is fully charged. Rumble works on the controller...

I think I may have randomly stumbled into what may be causing the issue, seems like xpadneo isn't always taking control of the controller, so the generic kernel driver is...

The bug hasn't been patched by the latest commit. Vibration in hidraw works fine, but game rumble doesn't work. Occasionally game rumble might work, but I'd say that there's a...

I'm using the dkms install via source. The udev rules are present in the correct directory and aren't duplicated.

I've attached the requested files. I couldn't find anything under `DEVPATH=/devices/virtual/misc`, so I took a swing at one of the devices under /devices/pci0000:00/ [udevadm.log](https://github.com/atar-axis/xpadneo/files/14463140/udevadm.log) [udevinfo.log](https://github.com/atar-axis/xpadneo/files/14463141/udevinfo.log) dmesg: ``` [ 264.106758] Bluetooth:...

> Is it possible that only the first connect after a reboot ends up in the `hid-microsoft` driver and successive connections properly use `hid-xpadneo`? Unfortunately not. It's seemingly random if...

Compiled in kernel by the look of it: ``` modinfo hid-microsoft filename: /lib/modules/6.7.6-200.fc39.x86_64/kernel/drivers/hid/hid-microsoft.ko.xz license: GPL rhelversion: 9.99 alias: hid:b0005g*v0000045Ep000002E0 alias: hid:b0005g*v0000045Ep00000B22 alias: hid:b0005g*v0000045Ep00000B05 alias: hid:b0005g*v0000045Ep00000B13 alias: hid:b0005g*v0000045Ep00000B20 alias: hid:b0005g*v0000045Ep000002FD alias:...

> One other thing, please check if this file (https://github.com/atar-axis/xpadneo/blob/master/hid-xpadneo/etc-modprobe.d/xpadneo.conf) has been installed in these directories without duplicates, and identical contents: > > 1. `/usr/lib/modprobe.d` or > > 2. `/etc/modprobe.d`...

Near as I can tell, this issue is now resolved and I haven't had any more issues with the controller in the past couple weeks. Closing!