I seem to be having issues with both ath10k and ath11k firmware connecting a specific device for me.
I have tried a few OpenWrt devices with ath10 and 11k chips and they have problems with the Xbox360.
It connects gets an IP address and all seems working but no communication.
If I switch to legacy mode instead of 802.11n or ax in OpenWrt the problem is resolved.
I have tried several Xbox360 consoles as there is several different Wi-Fi chipsets noting that two specific chips work without issue, but all the others fail.
The Xbox supports 802.11abg and N on the 2.4ghz band only with the built in adaptor.
with the external adaptor there is two models one works on the 2.4 and 5g bands (dual antenna), and a single antenna 2.4g only band.
The external adaptor with two antennas works and one of the internal models with out issue.
I'm wondering if I can increase the debug level or something to see why this is happening or if anyone has any pointers, the log as it does not really point out any issue.
The Xbox wireless adaptor is based on the Marvell 88W8388 88W8030 chipsets the firmware has a custom usb id specific to the device.
Microsoft 802.11 a/b/g USB 2.0 Wireless Networking Adapter WKS168 FCC ID C3K-WKS168
IIRC - the XBOX360 issues where around LDPC negotiation when the setting was true on the AP side...
LDPC = this is optional for HT mode - it's "Low Density Parity Check" coding
I know in 802.11N they added block ack, aggregation, mimo 40mhz channels and a few power saving features but for all purposes it should be backwards compatible.
If I disable that feature in OpenWrt will it fix my issues or is it a firmware issue on the Microsoft adaptor?
I'm thinking I may be able to change the device id and flash an alternative firmware.
It was a quirk in the Marvell client chip/driver for xbox360 wireless adapter
The default here is enabled/true (1)
uci set wireless.radio1.ldpc='0'
uci set wireless.radio0.ldpc='0'
uci commit wireless
and restart the interfaces - should work, and doesn't cause any harm for other client
3 Likes
I can confirm you are correct disabling that setting enables a Xbox 360 console to operate on a wireless N and above network without issue.
The problem is quite widespread as almost all of the xbox360 slim consoles use the marvell chipset, it also seems that setting is almost never exposed on router firmware and is highly likely a user will encounter this issue.
2 Likes
thx for the follow up - good to hear it's working for you
Were going to update the console modes wiki with this information it should help future users.
Would it be possible to cross flash these devices with alternative firmware and change the device ID's to fix this issue or is it kernel/ hardware related?
Microsoft - TechInfoDepot
1 Like
Hmm - not sure for client stations - e.g. the Xbox devices...
Might be useful as a notation - for OpenWRT, there is the fix for pretty much every supported platform.
As a special note - Some of the Asus Routers have a WebUI switch that does the same thing - "xbox compat" I'm told...
1 Like
Honestly - I'm not sure for the client side...
Just happy to sort things on the AP side, to be honest..
well - someone was looking in to this item - and exposed the feature switches to enable/disable the LDPC function from LUCI.
Nicely done...
commit 65a80284cfc4cbef4d6d2dbc85423fef561ac0ea
Author: Paul Donald <newtwen+github@gmail.com>
Date: Sat Apr 5 16:04:37 2025 +0200
luci-mod-network: wireless: add LDPC capability flags (X-Box compat)
Signed-off-by: Paul Donald <newtwen+github@gmail.com>
Yes I put in a request in luci and systemcrash came through.
I'm not having so much luck with Microsoft in fixing the actual problem tho:
XBOX 360 wifi bug console won't connect to modern wireless networks. - Microsoft Community
Only the LDPC fix is needed - the current PR includes the VHT specific RXLDPC function... I've added my comment to @systemcrash pull request...
I have found this issue on other devices too, I tried it on an older Epsom wireless home office printer we retired at work I knew had issues connecting to a wifi network and it fixed the issue there too.
Hmm - Might be helpful to add a note under the setting about stuff like this. Institutional knowledge, as it were. Hope the change is useful 
I can update the wiki, if deemed a good idea, it was something I was looking at doing to mention Xbox360 but 'there was not really a place to put this info from a quick look.
It may be better to be a separate troubleshooting informational page/ thing if you have problems connecting devices it is something one could try?
I do know some devices don't like mixed mode wifi security my Sony tv won't connect to wpa2/3 mixed mode Wi-Fi but works fine with wpa2.
Greybeard - yeah - these things happen, and appreciate the effort to address it...
See my comment on the PR - and yes, the change is useful, but let's limit the scope as mentioned...
That's another discussion 
FWIW - my insight on this particular issue - it was years ago when we were doing a 4g/WiFi gateway, and we caught this fairly quickly, so we dropped the fix in - nothing like what we have these days with wireless support and config...
we were netbsd based, so never thought about kicking the fix upstream...
For now, the Xbox seems to be the only device I know of that needs this setting off due to its chipset. It's trivial to add a description under the setting to mention a device, and so would aid in discoverability. Put a note in the wiki for now. I figure the Xbox nerds will know what to do with that setting
It will also be going in the console mods wiki, but I did observe this issue with an epsom wireless printer, maybe it is a chipset fault?
This part from an epson uses the same chipset as the Xbox360:
Wi-Fi Module for Epson SP88W8786-MD0-2C2T00 2135226-00, Original! | eBay