boot: 045e:02e6 still fails cold-boot initialization on v0.5.8 (-108), replug recovers

[cehovan]

Old dongle 045e:02e6 still fails on cold boot with v0.5.8.

Before v0.5.8 I had the repeated disconnect/reconnect boot loop until unplug/replug.
After updating to v0.5.8, the behavior changed: I no longer see the same loop, but cold boot still fails with:

xone_mt76_write_register: control message failed: -121
xone_dongle_fw_load: load firmware failed: -19
xone_dongle_fw_load: init radio failed: -108

If I unplug and replug the dongle after boot, it works normally.

Tested on both Arch kernel 6.19.x and LTS 6.18.x.
Firmware file for 02e6 is present and matched correctly.

[Lawstorant]

You know what's stupid? I cannot reproduce this on any of my machines. I have the fat and slim dongles and they all work correctly. I wish I could find a PC that has the same issues so I could at least try to debug it.

Could you maybe try some older versions to see if there's one that could work?

[TomaszBojanowski]

Yes, I have the same problem. I'm using the V1 fat dongle. The last version that worked without issues was 0.5.5 (I don't remember how version 0.5.6 worked, but 0.5.5 definitely worked fine). Latest openSUSE TW / 6.19.x kernel.

[xvil]

I am running CachyOS.

Currently, it's using 6.19 latest kernel but the behaviour was similar if not identical with 6.18.

Since 0.5.6 I have issues on cold boot and on resume from sleep: the xbox usb stick is detected then the driver fails with some firmware loading issue (error -19), then detected again and failure again, and like that in a loop until I unplug the USB adapter and replug it. Only then it's stable until the next sleep or the next reboot.

0.5.8 seems to worse than 0.5.6 or 0.5.7 as it fails instantly and each iteration of the failure loop is much faster.

For now, I have reverted to 0.5.5 and all is working fine.
I don't know what happened in between but all subsequent releases fail one way or another for me.

I did try to uninstall the xone-dkms and the xone-dongle-firmware packages and reinstall them in their latest version.
Unfortunately, it did not fix anything.

There's something wrong, for sure.

My version of the adapter seems to be v2 (the thin one).
As reported by sudo lsusb -v (using 0.5.5):

Bus 003 Device 003: ID 045e:02e6 Microsoft Corp. Xbox Wireless Adapter for Windows
Negotiated speed: High Speed (480Mbps)
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.10
  bDeviceClass            0 [unknown]
  bDeviceSubClass         0 [unknown]
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x045e Microsoft Corp.
  idProduct          0x02e6 Xbox Wireless Adapter for Windows
  bcdDevice            1.00
  iManufacturer           1 MediaTek Inc.
  iProduct                2 802.11ac WLAN
  iSerial                 3 000000000
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x004a
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          2 802.11ac WLAN
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower              200mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           8
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              2 802.11ac WLAN
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x85  EP 5 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x08  EP 8 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x05  EP 5 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x06  EP 6 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x07  EP 7 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x09  EP 9 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Binary Object Store Descriptor:
  bLength                 5
  bDescriptorType        15
  wTotalLength       0x0016
  bNumDeviceCaps          2
  USB 2.0 Extension Device Capability:
    bLength                 7
    bDescriptorType        16
    bDevCapabilityType      2
    bmAttributes   0x0000f41e
      BESL Link Power Management (LPM) Supported
      Baseline BESL value    400 us 
      Deep BESL value      10000 us 
  SuperSpeed USB Device Capability:
    bLength                10
    bDescriptorType        16
    bDevCapabilityType      3
    bmAttributes         0x00
    wSpeedsSupported   0x000e
      Device can operate at Full Speed (12Mbps)
      Device can operate at High Speed (480Mbps)
      Device can operate at SuperSpeed (5Gbps)
    bFunctionalitySupport   1
      Lowest fully-functional device speed is Full Speed (12Mbps)
    bU1DevExitLat          10 micro seconds
    bU2DevExitLat         180 micro seconds
Device Status:     0x0002
  (Bus Powered)
  Remote Wakeup Enabled

[Lawstorant]

Would you be able to test a custom branch with some changes I'll do?

[Lawstorant]

I'm hunting this down. I will fix it

[xvil]

Hi @Lawstorant,

I'll gladly help and test from a branch.
I am familiar with building kernel modules so that won't be a problem.

If I need to downgrade to a different kernel I suppose I can do that as well, if not on my main machine, I can find another one.

Cheers!

[cehovan]

I’ve forked this repo and am playing around with a fix. It’s not commited/pushed yet and I’m not at my PC at the moment to be able to share it. It seems to fix the issue, but I need more testing.

I will share it as soon as I’m able to get to my PC.

Also I can test a branch if you need me to.

[cehovan]

Quick update: I spent some time trying to fix this on my side. I got some partial improvements, but I also ran into extra issues and I’m not fully sure which of them were caused by my experimental fixes versus the original regression.

So I’ve dropped the fix attempts for now and switched to finding the regression point first.

Current result:

• I tested a clean v0.5.8-based branch with one suspect change reverted
• the suspect commit I tested was 7ee0ce1
• cold boot on 045e:02e6 still fails
• I still see repeated xone_mt76_*register control message failed: -121 followed by xone_dongle_fw_load: load firmware failed: -19

So at least from this test, 7ee0ce1 does not look like the sole cause of the regression.

Next I’ll try to narrow it down by focusing on the v0.5.5 -> v0.5.6 range, since v0.5.5 was the last version that worked for me without the boot-loop behavior.

[Lawstorant]

v0.5.5 -> v0.5.6 is all me. It's the 2 second delay when loading firmware, but it was removed afterwards.

[xvil]

v0.5.5 is not entirely issue-free for me either.
Since I reverted back to it, I notice disconnections from time to time.
Those disconnections were no longer happening in more recent versions for sure.

But no cold boot or after resume issues like with v0.5.6+

[Lawstorant]

Yes, that's why we need to single out what broke the cold boot. I've been trying out commits one by one.

[Lawstorant]

Fun fact, I cannot reproduce this on my laptop, only on my PC. Weird

[Lawstorant]

@cehovan could you test the cold-boot-fixes branch? I think it's a bit better #193

[TomaszBojanowski]

On my PC, I have issues when I plug the adapter into a USB 3.0 Type-A port, but the issues don't happen when I plug it into a USB 3.2 Type-A port. That's strange, too.

[TomaszBojanowski]

I installed the driver from the test branch, and I do feel that the connection between the controller and the adapter has improved (I have the v1=fat version). However, I noticed that the LED on the adapter flashes even after it has connected properly to the controller; it only starts to glow with a steady light after a dozen or so seconds.

EDIT: oh no, it failed to connect after third reboot of the system