Wired Xbox One X Controller not powering on at system boot

[Ecophagy]

I have Xbox One X Controller that does not power on (but does vibrate) when the system it is connected to by USB C is powered on. Pressing the central "xbox" button causes the light to slowly flash but that's it (like it's waiting for a wireless connection?). If you unplug and plug it back in it powers on and works perfectly.

While in this connected-but-powered off state, it is visible as /dev/input/js* and shows up in both jstest-gtk and jstest. In both cases pressing buttons on the controller does not do anything - the axes/buttons are all listed but do not pick up any signals. Dmesg contains no errors.

The controller is listed as "Generic X-Box pad" rather than its proper name, but I'm unsure if that's a red herring because I'm assuming any identifaction would be done on the ID rather than name.

lsusb output: Bus 001 Device 006: ID 045e:0b12 Microsoft Corp.

Kernel version: 5.4.0-87-generic on Ubuntu 18.04. I have also tried Ubuntu 20.04, with xboxdrv installed and uninstalled, and installing the latest xpad version as described in the README - all to no changein behaviour.

I have connected it to Windows as well (where it also listed as "Xbox Controller" rather than any specific model). The Firmware version is 10.0.19041.610 (from 22/10/2020).

My assumption is that either the packet required to wake up/connect the controller isn't being sent at boot, or it is being mis-read as a generic controller and not sent the correct packet. But only at boot for some reason. Any ideas? It's not a disaster but it is very annoying having to replug the controller every time I boot the computer.

I did comb through the issues and couldn't see any pre-existing ticket (most of them appear to refer to not-yet-supported third-party controllers), but I think this could be the same issue as #170.

[KuleRucket]

I just raised #181 for this controller. This is how the device appears for me when it's connected via bluetooth.