It’s direct rendering manager. Basically it’s what kernel GPU drivers are called in linux

Hello, I have had a “similar” issue. In my case a program didn’t recognise my controller as the first one because my motherboard’s led controller (!!!) pretended to be a controller.

One very good and useful thing you can do is:

• Verify that is really the problem, use udevadm info <device path> and see if it has ID_INPUT_JOYSTIC=1 or something similar.
• Write an udev rule to unset the variable (e.g. ID_INPUT_JOYSTIC=) to remove the 1 without actually setting it to 0
• Send the rule to systemd in an issue so they add it to a list of known hardware quirks. This way everyone with your keyboard will get the fix