Package Details: xone-dongle-firmware 2.0.0-1

Git Clone URL: https://aur.archlinux.org/xone-dongle-firmware.git (read-only, click to copy)
Package Base: xone-dongle-firmware
Description: Xbox Wireless Controller Adapter firmware
Upstream URL: https://support.xbox.com/en-US/help/hardware-network/browse
Licenses: LicenseRef-Microsoft
Submitter: None
Maintainer: xiota (Lawstorant)
Last Packager: Lawstorant
Votes: 25
Popularity: 1.51
First Submitted: 2022-06-27 19:29 (UTC)
Last Updated: 2025-12-08 11:54 (UTC)

Latest Comments

1 2 3 Next › Last »

syrinx20xx commented on 2025-12-11 06:54 (UTC)

@Lawstorant I replied to you on GitHub, let's discuss there.

Lawstorant commented on 2025-12-09 22:05 (UTC)

@syrinx20xx I saw your issue on github and replied there. Since then, I added more firmware I found in the MS update registry. I'd love to hear from you there and maybe test the newest (0.5.0) version with the newest firmwares

syrinx20xx commented on 2025-12-07 02:40 (UTC) (edited on 2025-12-07 02:42 (UTC) by syrinx20xx)

Microsoft actually released two entirely different versions (with different internal hardware/chipsets, requiring entirely different drivers) of the Xbox One Wireless USB Dongle. They are both authentic products and they look identical, so you can't tell them apart by looking at them, and they have identical product and vendor IDs, so Windows auto-detects them as being the same device (which they aren't) and always installs the wrong (later revision's) driver regardless of which revision you actually have.

My older revision dongle is an authentic Microsoft product, purchased directly from Microsoft's employee company store many years ago, and it does not work with this 1.0.46.1-2 firmware at all. My dongle requires me in Windows to forcibly remove and block the driver version (21.50.45.656 or later) that Windows Update insists on installing, and I have to manually install the older driver version (18.31.1.43) to get it to work correctly under Windows.

This very non-obvious situation is probably why this Linux driver seems to work for some people and not for others.

tsndr commented on 2025-11-30 19:28 (UTC)

Controller not connecting with xone-dongle-firmware installed and rebooted. Dongle is an genuine Microsoft one and is recognized correctly in dmesg. Also tried xone-dkms-git instead of xone-dkms-git, but no difference either.

Lawstorant commented on 2025-04-17 12:43 (UTC) (edited on 2025-04-17 12:43 (UTC) by Lawstorant)

Hi! It's me again haha

There was a recent finding that some knockoff adapters need a different firmware to work properly. This alternative fw is already supported by upstream driver. Could you add this second firmware to this package?

https://github.com/dlundqvist/xone/commit/0dbd56e51118a5e7d3a4cecad255d99835985680

https://github.com/dlundqvist/xone/commit/ffe1251c7c518574bf409f7e915fab8c532544c0

shuino commented on 2025-04-06 18:24 (UTC) (edited on 2025-04-06 18:30 (UTC) by shuino)

If anyone is using Endeavor, the "yay -S xone-dongle-firmware" install and xone-dkms-git you'll need to reboot before it works.

xiota commented on 2025-02-07 21:56 (UTC)

@FrancisMH I suspect you have some local config issue. However, I've added a variable to make skipping license download easier and limited the number of redirects. Did not bump pkgrel because there's no need for anyone to rebuild.

base-devel is a prerequisite to using AUR. It is not added to package (make) depends.

FrancisMH commented on 2025-02-06 01:26 (UTC) (edited on 2025-02-06 01:30 (UTC) by FrancisMH)

I had to remove the terms of use stuff for the PKGBUILD to work.

I was getting this error.

curl: (47) Maximum (50) redirects followed

You should also add base-devel to the dependencies.

merlinf commented on 2025-01-24 17:42 (UTC)

@xiota could you please add yourself as maintainer in the PKGBUILD if you're assuming maintainership?

1 2 3 Next › Last »