Absurd WiFi connection issues on Steam Deck OLED 1TB LE

[DoomTheRobot]

EDIT 7/9/2024: A new developer option in the 3.6 Beta (and now in the latest stable) seems to have fixed my connectivity issues. I can now connect to my Nighthawk RAX35. Here's the process if you want to give it a try:

1. Update your Steam Deck to the latest version
   
2. Enable Developer Mode in System tab
   
3. Go to new Developer settings tab at the bottom
   
4. Enable "Force WPA Supplicant WiFi backend" option
   
5. Reboot

This is what worked for me.

EDIT 5/4/2024: I should've done this way earlier but here is a list of routers that seem to be having issues:

• NETGEAR Nighthawk RAX35 (v1.0.5.104_1.0.1)
  
• NETGEAR Nighthawk RAX30 (v1.0.10.94)
  
• ASUS RT-AX86U Pro
  
• ASUS RT-AX88U
  
• ASUS Rapture GT-AX6000
  
• TP-Link Deco M4
  
• TP-Link AX50
  
• TP-Link AX6000
  
• Telekom's "Speedport Pro Plus"
  
• Sagemcom CS50001

If you're still having issues even after updating to the latest stable, post your router info and firmware version here so I can include it in this list.

EDIT 3/30/2024: If you are still having connection issues, try finding a way to update to 3.5.17 stable, as it contains various WiFi fixes which may fix the problems you could be facing. If not, head over to this GitHub issue[github.com] and leave a comment about the issue you're having.

Just got mine yesterday and have been having off-and-on issues with WiFi connectivity that never happened at all with my previous Steam Deck LCD 512GB model. This is not an issue with my connection as none of this has ever happened over the two or so years of using my original Steam Deck.

During the initial setup process, it refused to connect to my WPA2 secured WiFi network with nothing other than "Failed to connect" when attempting to connect to it. I'd enter my password and it'd sit for a while until it eventually fails. Despite this, I connected to my mobile hotspot perfectly fine to finish the setup process.

Here's what I've done so far:

• Rebooted the Router (obviously)
  
• Re-imaged SteamOS
  
• Disabled WiFi Power Saving
  
• Tried switching between 2.4GHz and 5GHz connections

I even went into Desktop mode and tried messing with the settings there. No luck.

For whatever reason though, and this is the confusing part: After multiple restarts it automatically connects to the WiFi network with no issues. It's almost completely random whether or not it wants to connect on boot. After connecting it works perfectly fine. No "Failed to connect", no loss of speed, works just as it did like the previous Steam Deck.

But once I eventually shutdown, it just happens again until I restart the system multiple times until it works again. Absolutely no clue why. I didn't mind it at first as I assumed it was just a software bug that would eventually go away, but now it's becoming extremely frustrating.

So what's the deal here? Is this a hardware issue or is my network just messed up somewhere? Where do I even start?

[Tungulus]

This worked for me when I switched my internet. Only problem is in beta mode I can't use any Decky plugins. Is it ok to switch back to stable after it establishes connection or will the "force WPA" option disappear again?

[SaltedOil]

I tried out the 3.6.8 beta, but on my OLED, every single game I tested had a bad audio crackle. I switched back to Stable on 3.5 and it resolved the crackles.

[Tadrith]

Frankly, why do I have to mess with any of this? I bought a product, it should work out of the box. My phone has no issues with WiFi, my computer has no issues with WiFi, and I'm jumping through hoops to make this device even remotely get the speed it should.

[☜☆Oblivion☆☞]

Diposting pertama kali oleh Tadrith:

Frankly, why do I have to mess with any of this? I bought a product, it should work out of the box. My phone has no issues with WiFi, my computer has no issues with WiFi, and I'm jumping through hoops to make this device even remotely get the speed it should.

just refund it bro waste of your time its almost 1 year and valve dont care

[Tadrith]

Further note -- this worked. But I shouldn't have to do any of this to make WiFi work properly. I'm now pulling >300Mbps. Thank you so much! I'm able to connect to all of my access points (of which, all but one failed), and I have my speed.

It's interesting because it warns you that you might experience slower connections from sleep, but it actually made it so that everything actually worked...

I loaded Windows, I reloaded steamOS, I've gone through so much just to make the damn thing work, and nothing has helped until this.

[Tadrith]

Diposting pertama kali oleh ☜☆mkmiaz8☆☞:

Diposting pertama kali oleh Tadrith:

Frankly, why do I have to mess with any of this? I bought a product, it should work out of the box. My phone has no issues with WiFi, my computer has no issues with WiFi, and I'm jumping through hoops to make this device even remotely get the speed it should.

just refund it bro waste of your time its almost 1 year and valve dont care

Frankly... you're not wrong. But it's working, now. Might still refund -- I feel like the other options out there might actually work a lot better. Trying to get remote access to the steam deck, even in desktop mode, ended up in my using my employers' support software. Windows? Enable RDP, done. But the Windows experience on the deck is not ideal, either.

[GeneralLee]

Yeah I've tried all of the suggested fixes and I'm still not getting my deck to connect. It connected just gone to my old wi-fi, but since switching to quantum fiber internet, it no longer connects. Any help?

[Dragon Protector]

Might just be the bad chip they use that linux hates.

[MrH]

Diposting pertama kali oleh DoomTheRobot:

EDIT 7/9/2024: A new developer option in the 3.6 Beta seems to have fixed my connectivity issues. I can now connect to my Nighthawk RAX35. Here's the process if you want to give it a try:

1. Go to Settings in Game Mode
   
2. In System tab, change System Update Channel to Beta and update
   
3. Enable Developer Mode in System tab
   
4. Go to new Developer settings tab at the bottom
   
5. Enable "Force WPA Supplicant WiFi backend" option
   
6. Reboot

This is what worked for me.

EDIT 5/4/2024: I should've done this way earlier but here is a list of routers that seem to be having issues:

• NETGEAR Nighthawk RAX35 (v1.0.5.104_1.0.1)
  
• NETGEAR Nighthawk RAX30 (v1.0.10.94)
  
• ASUS RT-AX86U Pro
  
• ASUS RT-AX88U
  
• ASUS Rapture GT-AX6000
  
• TP-Link Deco M4
  
• TP-Link AX50
  
• TP-Link AX6000
  
• Telekom's "Speedport Pro Plus"
  
• Sagemcom CS50001

If you're still having issues even after updating to the latest stable, post your router info and firmware version here so I can include it in this list.

EDIT 3/30/2024: If you are still having connection issues, try finding a way to update to 3.5.17 stable, as it contains various WiFi fixes which may fix the problems you could be facing. If not, head over to this GitHub issue[github.com] and leave a comment about the issue you're having.

Just got mine yesterday and have been having off-and-on issues with WiFi connectivity that never happened at all with my previous Steam Deck LCD 512GB model. This is not an issue with my connection as none of this has ever happened over the two or so years of using my original Steam Deck.

During the initial setup process, it refused to connect to my WPA2 secured WiFi network with nothing other than "Failed to connect" when attempting to connect to it. I'd enter my password and it'd sit for a while until it eventually fails. Despite this, I connected to my mobile hotspot perfectly fine to finish the setup process.

Here's what I've done so far:

• Rebooted the Router (obviously)
  
• Re-imaged SteamOS
  
• Disabled WiFi Power Saving
  
• Tried switching between 2.4GHz and 5GHz connections

I even went into Desktop mode and tried messing with the settings there. No luck.

For whatever reason though, and this is the confusing part: After multiple restarts it automatically connects to the WiFi network with no issues. It's almost completely random whether or not it wants to connect on boot. After connecting it works perfectly fine. No "Failed to connect", no loss of speed, works just as it did like the previous Steam Deck.

But once I eventually shutdown, it just happens again until I restart the system multiple times until it works again. Absolutely no clue why. I didn't mind it at first as I assumed it was just a software bug that would eventually go away, but now it's becoming extremely frustrating.

So what's the deal here? Is this a hardware issue or is my network just messed up somewhere? Where do I even start?

I have aruba instant on 4 access points around the house, no other devices having issues BUT steam deck, 500mbps cox(it sucks) and have similar issues, I have to connect steam deck to Hotspot to get minecraft load, or it just get stuck on loading page, been frustrating dealing with steam deck connectivity issues for over 2 years now!

Steam deck 512gb(first gen).

[DoomTheRobot]

It's been a hot minute but I'd like to comment that the latest stable update now includes the "Force WPA Supplicant WiFi backend" option in the Developer settings tab, as it was only in the beta branch previously.

So if you'd like to go back to the stable branch instead of using the beta branch to enable the "fix" then you can now.

Some have been reporting that this recent stable update fixes all their connection issues, this of course still doesn't fix my connection issues. Though it doesn't hurt to check...

[EternalGaia]

Diposting pertama kali oleh DoomTheRobot:

It's been a hot minute but I'd like to comment that the latest stable update now includes the "Force WPA Supplicant WiFi backend" option in the Developer settings tab, as it was only in the beta branch previously.

So if you'd like to go back to the stable branch instead of using the beta branch to enable the "fix" then you can now.

Some have been reporting that this recent stable update fixes all their connection issues, this of course still doesn't fix my connection issues. Though it doesn't hurt to check...

My wifi was fine but this update (3.6.19 stable) actually broke it. I am now forced to use the wpa supplicant

[Patschge]

the update broke my WIFI too

[EternalGaia]

Diposting pertama kali oleh EternalGaia:

Diposting pertama kali oleh DoomTheRobot:

It's been a hot minute but I'd like to comment that the latest stable update now includes the "Force WPA Supplicant WiFi backend" option in the Developer settings tab, as it was only in the beta branch previously.

So if you'd like to go back to the stable branch instead of using the beta branch to enable the "fix" then you can now.

Some have been reporting that this recent stable update fixes all their connection issues, this of course still doesn't fix my connection issues. Though it doesn't hurt to check...

My wifi was fine but this update (3.6.19 stable) actually broke it. I am now forced to use the wpa supplicant

Just noticed that enabling the option "Enable WiFi debug data collection" is enough to fix wifi for me. No need to change to wpa supplicant or mess with power energy.. strange.
I'm guessing it will create logs and since i'm not sure how big they will be, i won't go with that workaround.
Just mentioning it because i find it odd.

[Patschge]

Diposting pertama kali oleh EternalGaia:

Diposting pertama kali oleh EternalGaia:

My wifi was fine but this update (3.6.19 stable) actually broke it. I am now forced to use the wpa supplicant

Just noticed that enabling the option "Enable WiFi debug data collection" is enough to fix wifi for me. No need to change to wpa supplicant or mess with power energy.. strange.
I'm guessing it will create logs and since i'm not sure how big they will be, i won't go with that workaround.
Just mentioning it because i find it odd.

sadly did not help

[☜☆Oblivion☆☞]

i just cant its one year since this problem over 600 coments and people still cant use wifi to use this cursed device XD