Bernat

> @berarma i think other modes (G29,G25, etc) needs to be removed from G923, what do you think? None of the compatibility rules applicable to wheel (bcdDevice is the same),...

Those usbhid messages look like another module is trying to access the device and failing. This doesn't happen with the G29. I could take a look and see why this...

Ok, after researching a bit I think I have a deeper understanding. It turns out that the G29 uses the same command for switching from PS4 mode to Classic/PC mode...

I've found an easier solution. Write a file `/etc/modprobe.d/g923.conf` with contents: ``` usbhid quirks=0x046d:0xc267:0x0800 ``` Reboot after creating the file. This instructs the usbhid module to ignore the G923 device...

> Didnt work for me. I dont see any difference. There's two device ids involved, so it should be: `usbhid quirks=0x046d:0xc267:0x0800,0x046d:0xc266:0x0800` I can't try it but I hope someone can...

> I will try again. > > But, to understand it better, what does `0x0800` stand for as a quirk? It is not listed here: > > https://github.com/torvalds/linux/blob/5f53fa508db098c9d372423a6dac31c8a5679cdf/include/linux/hid.h#L340 Yes, sorry,...

> `HID_QUIRK_IGNORE=0x4`! > > In this case, it only gets this far. > > ``` > Nov 25 21:19:44 amd-arch kernel: usb 1-3: new full-speed USB device number 4 using...

> @berarma, big thanks for possible solution! > But isn't it supposed to be `HID_QUIRK_HAVE_SPECIAL_DRIVER` instead of ignorance? > https://elixir.bootlin.com/linux/latest/source/drivers/hid/hid-quirks.c#L212 > So like.. `modprobe` option will be like `usbhid quirks=0x046d:0xc267:0x80000`?...

> Logs are same with no quirk. > > ``` > cat /sys/module/usbhid/parameters/quirks > 0x046D:0xC267:0x080000,0x046D:0xC266:0x080000,(null),(null) > ``` Did you rebuild the initramfs?

What should we do now? Do I merge it even if it isn't completely fine for everyone or wait until a solution is found?