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?

[grzelu]

It's not router specific, it's a bug in SteamOS. I tested it on multiple routers (mine, my parents, my friend and my sister), personally I have TP-Link AX50 (which I bought myself, it's not a router from ISP) and there are 2 problems to be exact:

1. U can't connect to Wi-Fi if it uses 160MHz AND WiFi6 (AX feature)
2. U can connect, but connection is unstable (timeouts every 10-20s for duration of 30-60s) when you use merged bands. So whenever you have 2.4GHz and 5GHz under the same SSID or using mesh setup like Ubiquiti.

People here and on GH confirmed they have issues with mesh Ubiquiti as well. It's not router specific. It's SteamDeck issue in those 2 specific scenarios and I guarantee that if you say that you don't have a problem and it's working fine for you, just set your router to appropriate config and see that you will have the same issue. If you do not have mesh at home, you will get unstable connection in any hotel, shopping centre etc. because in those places there is always a mesh setup. Also as I said, remember that there are 2! issues that have a little different behaviour.

I believe some people might not even notice the issue no. 2 because if you only download Steam games and don't go to desktop, Steam automatically handles reconnects and download resumes without error. I had that issue and noticed that because games took really long to download. Here is my GH issue https://github.com/ValveSoftware/SteamOS/issues/1256.

It's not like - it works with my router then there is no problem. NO! Just because you don't use WiFi6 or merged SSIDs doesn't mean there isn't an issue! There IS a driver/firmware problem and you can easily verify that with your router:
1. Enable 160MHz AND AX feature in the router (the AX part is crucial) OR
2. Merge SSIDs if you have both 2.4 and 5GHz

And remember that issue will present differently for 1. and 2.

-- EDIT --
BTW changing your router config JUST to use SD is pointless. I could get it working when I disabled 160MHz and AX and split my SSIDs, BUT I have a family of 4, >30 devices in network with many smart devices that need to easily communicate between each other and some of them use 2.4GHz and some 5GHz. Also I need 160MHz channel performance with that many devices. I won't cripple my network and reconfigure everything just for 1 device. But I see that there a people with mindset, easy reconfigure whole network, split SSIDs, change 20 devices to other network (new SSID) and then you can use your glorious problemless SD. I knew there are many SD fanboys, but reading this thread (and others also) made me thinking how is it possible that there so many people are in love with Valve.

[Buju]

Thanks for all your info.

Nguyên văn bởi grzelu:

BTW changing your router config JUST to use SD is pointless. I could get it working when I disabled 160MHz and AX and split my SSIDs, BUT I have a family of 4, >30 devices in network with many smart devices that need to easily communicate between each other and some of them use 2.4GHz and some 5GHz. Also I need 160MHz channel performance with that many devices. I won't cripple my network and reconfigure everything just for 1 device. But I see that there a people with mindset, easy reconfigure whole network, split SSIDs, change 20 devices to other network (new SSID) and then you can use your glorious problemless SD. I knew there are many SD fanboys, but reading this thread (and others also) made me thinking how is it possible that there so many people are in love with Valve.

With this quote, it looks like you've misunderstood the purpose of my comments suggesting trying different router configurations. I suggested trying those things to be able to find what triggers the bug in the Steam Deck, not to suggest using a workaround and letting the whole issue go ignored. The idea is to, as a community, help Valve figure out exactly what they need to do to fix the issue, closing the gap so that everyone can have a working Steam Deck OLED.

[AustralOK]

Nguyên văn bởi grzelu:

It's not router specific, it's a bug in SteamOS. I tested it on multiple routers (mine, my parents, my friend and my sister), personally I have TP-Link AX50 (which I bought myself, it's not a router from ISP) and there are 2 problems to be exact:

1. U can't connect to Wi-Fi if it uses 160MHz AND WiFi6 (AX feature)
2. U can connect, but connection is unstable (timeouts every 10-20s for duration of 30-60s) when you use merged bands. So whenever you have 2.4GHz and 5GHz under the same SSID or using mesh setup like Ubiquiti.

People here and on GH confirmed they have issues with mesh Ubiquiti as well. It's not router specific. It's SteamDeck issue in those 2 specific scenarios and I guarantee that if you say that you don't have a problem and it's working fine for you, just set your router to appropriate config and see that you will have the same issue. If you do not have mesh at home, you will get unstable connection in any hotel, shopping centre etc. because in those places there is always a mesh setup. Also as I said, remember that there are 2! issues that have a little different behaviour.

I believe some people might not even notice the issue no. 2 because if you only download Steam games and don't go to desktop, Steam automatically handles reconnects and download resumes without error. I had that issue and noticed that because games took really long to download. Here is my GH issue https://github.com/ValveSoftware/SteamOS/issues/1256.

It's not like - it works with my router then there is no problem. NO! Just because you don't use WiFi6 or merged SSIDs doesn't mean there isn't an issue! There IS a driver/firmware problem and you can easily verify that with your router:
1. Enable 160MHz AND AX feature in the router (the AX part is crucial) OR
2. Merge SSIDs if you have both 2.4 and 5GHz

And remember that issue will present differently for 1. and 2.

-- EDIT --
BTW changing your router config JUST to use SD is pointless. I could get it working when I disabled 160MHz and AX and split my SSIDs, BUT I have a family of 4, >30 devices in network with many smart devices that need to easily communicate between each other and some of them use 2.4GHz and some 5GHz. Also I need 160MHz channel performance with that many devices. I won't cripple my network and reconfigure everything just for 1 device. But I see that there a people with mindset, easy reconfigure whole network, split SSIDs, change 20 devices to other network (new SSID) and then you can use your glorious problemless SD. I knew there are many SD fanboys, but reading this thread (and others also) made me thinking how is it possible that there so many people are in love with Valve.

Blows my mind how a ♥♥♥♥♥♥ android can connect to my network without problem but the steam deck makes so much drama, after doing some test trying to connect via -NMCLI i found out that wpa_supplicant doesn`t want to work with my ISP/router, what`s even weird, that the error that i see is the one of incorrect password, that`s why i logged over konsole and sudo nmcli to check 100 times if i was typing a wrong one

and yet Valve is being SO quiet about this issue! why is so difficult for them to tell us if it`s a software/firware problem or hardware/cheap ♥♥♥♥♥♥ cringe qualcom chips? they re waiting for two weeks to pass so we wont be able to return this brick or what? that`s what bother me the most, not having problem with the WIFI per se, but the fact that Valve doesn`t say ♥♥♥♥ to us about this

[PopinFRESH]

Nguyên văn bởi grzelu:

It's not router specific, it's a bug in SteamOS. I tested it on multiple routers (mine, my parents, my friend and my sister), personally I have TP-Link AX50 (which I bought myself, it's not a router from ISP) and there are 2 problems to be exact:

1. U can't connect to Wi-Fi if it uses 160MHz AND WiFi6 (AX feature)
2. U can connect, but connection is unstable (timeouts every 10-20s for duration of 30-60s) when you use merged bands. So whenever you have 2.4GHz and 5GHz under the same SSID or using mesh setup like Ubiquiti.

People here and on GH confirmed they have issues with mesh Ubiquiti as well. It's not router specific. It's SteamDeck issue in those 2 specific scenarios and I guarantee that if you say that you don't have a problem and it's working fine for you, just set your router to appropriate config and see that you will have the same issue. If you do not have mesh at home, you will get unstable connection in any hotel, shopping centre etc. because in those places there is always a mesh setup. Also as I said, remember that there are 2! issues that have a little different behaviour.

I believe some people might not even notice the issue no. 2 because if you only download Steam games and don't go to desktop, Steam automatically handles reconnects and download resumes without error. I had that issue and noticed that because games took really long to download. Here is my GH issue https://github.com/ValveSoftware/SteamOS/issues/1256.

It's not like - it works with my router then there is no problem. NO! Just because you don't use WiFi6 or merged SSIDs doesn't mean there isn't an issue! There IS a driver/firmware problem and you can easily verify that with your router:
1. Enable 160MHz AND AX feature in the router (the AX part is crucial) OR
2. Merge SSIDs if you have both 2.4 and 5GHz

And remember that issue will present differently for 1. and 2.

-- EDIT --
BTW changing your router config JUST to use SD is pointless. I could get it working when I disabled 160MHz and AX and split my SSIDs, BUT I have a family of 4, >30 devices in network with many smart devices that need to easily communicate between each other and some of them use 2.4GHz and some 5GHz. Also I need 160MHz channel performance with that many devices. I won't cripple my network and reconfigure everything just for 1 device. But I see that there a people with mindset, easy reconfigure whole network, split SSIDs, change 20 devices to other network (new SSID) and then you can use your glorious problemless SD. I knew there are many SD fanboys, but reading this thread (and others also) made me thinking how is it possible that there so many people are in love with Valve.

First, Ubiquity is a brand, not a router/AP model and they offer several WiFi systems; some of which are able to do a mesh WiFi configuration. I do concur that it seems like there are multiple similar / related issues that people are facing with different configurations, however, your point number 2 is not just "mesh networks" and that point is also likely multiple different issues. I have a UniFi network with a WiFi 6E AP and a WiFi 6 AP that is configured with a wireless uplink to the WiFi 6E AP and in a mesh with that AP. I've been doing some testing to try to replicate the issues, however, I'm able to use my Steam Deck OLED 1TB LE on 5GHz 160MHz channels with WPA3 personal on my mesh network; so it is not as simple as just "these configurations don't work".

when I say "works without issue" below, I mean it is not having the issues and tested by running an MTR to 1.1.1.1 while also downloading a 20GB padding file from a local server on my network, which the server is wired, and sending it to /dev/null; and also monitoring the logs for my Steam Deck OLED on my router. No disconnection, no packet loss.

Separate SSIDs

Running separate networks for each band and testing each channel width for each band.

2.4GHz with 20MHz or 40MHz channel width. Both APs configured for auto channel select; using either channel 1 or channel 6. WPA2 or WPA3 personal. BSS enabled or disabled. Works without issue.

5GHz with 80MHz or 160MHz channel width. Both APs configured for auto channel select; using channel 48. WPA2 or WPA3 personal. BSS enabled or disabled. works without issue.

6GHz with 160MHz channel width. WiFi 6E AP configured for auto channel select; using channel 37. WPA3 personal. BSS enabled or disabled (irrelevant as this is the only AP that is on the 6GHz band). works without issue.

Single SSID for 2.4GHz and 5GHz, WiFi 6E on 6GHz separated

2.4GHz with 20MHz or 40MHz channel width. Both APs configured for auto channel select; using either channel 1 or channel 6. WPA2 or WPA3 personal. BSS enabled or disabled. The Steam Deck will not use this band and latches to 5GHz pretty much exclusively unless band-steering is enabled and set to prefer 2.4GHz band.

5GHz with 80MHz channel width. Both APs configured for auto channel select; using channel 40. WPA2 or WPA3 personal. BSS enabled or disabled. works without issue; and the Steam Deck will pretty much exclusively latch to this unless band-steering is enabled to prefer the 2.4GHz network.

5GHz with 160MHz channel width. Both APs configured for auto channel select; using channel 48. WPA2 or WPA3 personal. BSS enabled or disabled. This works without issues, however, configuring WPA2/WPA3 has issues which appear to be due to PMF

6GHz with 160MHz channel width. WiFi 6E AP configured for auto channel select; using channel 37. WPA3 personal. BSS enabled or disabled (irrelevant as this is the only AP that is on the 6GHz band). works without issue.

Single SSID for all bands

2.4GHz with 20MHz or 40MHz channel width. Both APs configured for auto channel select; using either channel 1 or channel 6. WPA2 or WPA3 personal. BSS enabled or disabled. The Steam Deck will not use this band and latches to 5GHz pretty much exclusively unless band-steering is enabled and set to prefer 2.4GHz band.

5GHz with 80MHz channel width. Both APs configured for auto channel select; using channel 48. WPA2 or WPA3 personal. BSS enabled or disabled. works without issue; and the Steam Deck will pretty much exclusively latch to this unless band-steering is enabled.

5GHz with 160MHz channel width. Both APs configured for auto channel select; using channel 48. WPA2 or WPA3 personal. BSS enabled or disabled. This works without issues, however, configuring WPA2/WPA3 has issues which appear to be due to PMF

6GHz with 160MHz channel width. WiFi 6E AP configured for auto channel select; using channel 37. WPA3 personal. BSS enabled or disabled (irrelevant as this is the only AP that is on the 6GHz band). The Steam Deck will not connect to this and will always latch to the 5GHz band. I have to enable band-steering to get it to move to the 6GHz band.

With WPA2/WPA3 configured and the 5GHz band using 160MHz channel width the Steam Deck will intermittently connect to the 6GHz band without issue, however, when it first tries to connect to 5GHz it will fail and will continue flapping trying to latch on to the 5GHz band.

Testing without Mesh

Removed the WiFi 6 AP from the configuration temporarily and re-tested the same as above and it did not change the behavior

Summary

There definitely appears to be multiple issues, and further I suspect that one or more of these issues is partially due to router vendors improperly implementing certain features such as WPA2/WPA3 Transitional (mixed mode), Protected Management Frames (PMF), etc.

I think this is a large part of the issue, where by Valve just assumed wifi device vendors would properly and fully implement all of the features for a specific standard and so they just implemented things "by the book" for the relevant standards without handling incompatibilities.

The issue where people no longer are able to see any networks after connection failure until they reboot the Steam Deck appears to be the Steam Decks WiFi controller firmware crashing when it is encountering whatever of these issues is triggering that to occur.

I haven't yet had time to finish testing configuring WPA3 and requiring PMF as I'll need to setup a separate network for that testing because many of my older IoT things don't support WPA3/PMF.

I believe the issue with "mesh" networks is either/or router vendor and/or Valve implementation with SAE-PK, and transition disable when BSS is enabled for meshing; BSS Fast Transitioning; or some combination resulting in invalid or no secret being provided when the Steam Deck is transitioning radios.

[AustralOK]

Nguyên văn bởi PopinFRESH:

Nguyên văn bởi grzelu:

It's not router specific, it's a bug in SteamOS. I tested it on multiple routers (mine, my parents, my friend and my sister), personally I have TP-Link AX50 (which I bought myself, it's not a router from ISP) and there are 2 problems to be exact:

1. U can't connect to Wi-Fi if it uses 160MHz AND WiFi6 (AX feature)
2. U can connect, but connection is unstable (timeouts every 10-20s for duration of 30-60s) when you use merged bands. So whenever you have 2.4GHz and 5GHz under the same SSID or using mesh setup like Ubiquiti.

People here and on GH confirmed they have issues with mesh Ubiquiti as well. It's not router specific. It's SteamDeck issue in those 2 specific scenarios and I guarantee that if you say that you don't have a problem and it's working fine for you, just set your router to appropriate config and see that you will have the same issue. If you do not have mesh at home, you will get unstable connection in any hotel, shopping centre etc. because in those places there is always a mesh setup. Also as I said, remember that there are 2! issues that have a little different behaviour.

I believe some people might not even notice the issue no. 2 because if you only download Steam games and don't go to desktop, Steam automatically handles reconnects and download resumes without error. I had that issue and noticed that because games took really long to download. Here is my GH issue https://github.com/ValveSoftware/SteamOS/issues/1256.

It's not like - it works with my router then there is no problem. NO! Just because you don't use WiFi6 or merged SSIDs doesn't mean there isn't an issue! There IS a driver/firmware problem and you can easily verify that with your router:
1. Enable 160MHz AND AX feature in the router (the AX part is crucial) OR
2. Merge SSIDs if you have both 2.4 and 5GHz

And remember that issue will present differently for 1. and 2.

-- EDIT --
BTW changing your router config JUST to use SD is pointless. I could get it working when I disabled 160MHz and AX and split my SSIDs, BUT I have a family of 4, >30 devices in network with many smart devices that need to easily communicate between each other and some of them use 2.4GHz and some 5GHz. Also I need 160MHz channel performance with that many devices. I won't cripple my network and reconfigure everything just for 1 device. But I see that there a people with mindset, easy reconfigure whole network, split SSIDs, change 20 devices to other network (new SSID) and then you can use your glorious problemless SD. I knew there are many SD fanboys, but reading this thread (and others also) made me thinking how is it possible that there so many people are in love with Valve.

First, Ubiquity is a brand, not a router/AP model and they offer several WiFi systems; some of which are able to do a mesh WiFi configuration. I do concur that it seems like there are multiple similar / related issues that people are facing with different configurations, however, your point number 2 is not just "mesh networks" and that point is also likely multiple different issues. I have a UniFi network with a WiFi 6E AP and a WiFi 6 AP that is configured with a wireless uplink to the WiFi 6E AP and in a mesh with that AP. I've been doing some testing to try to replicate the issues, however, I'm able to use my Steam Deck OLED 1TB LE on 5GHz 160MHz channels with WPA3 personal on my mesh network; so it is not as simple as just "these configurations don't work".

when I say "works without issue" below, I mean it is not having the issues and tested by running an MTR to 1.1.1.1 while also downloading a 20GB padding file from a local server on my network, which the server is wired, and sending it to /dev/null; and also monitoring the logs for my Steam Deck OLED on my router. No disconnection, no packet loss.

Separate SSIDs

Running separate networks for each band and testing each channel width for each band.

2.4GHz with 20MHz or 40MHz channel width. Both APs configured for auto channel select; using either channel 1 or channel 6. WPA2 or WPA3 personal. BSS enabled or disabled. Works without issue.

5GHz with 80MHz or 160MHz channel width. Both APs configured for auto channel select; using channel 48. WPA2 or WPA3 personal. BSS enabled or disabled. works without issue.

6GHz with 160MHz channel width. WiFi 6E AP configured for auto channel select; using channel 37. WPA3 personal. BSS enabled or disabled (irrelevant as this is the only AP that is on the 6GHz band). works without issue.

Single SSID for 2.4GHz and 5GHz, WiFi 6E on 6GHz separated

2.4GHz with 20MHz or 40MHz channel width. Both APs configured for auto channel select; using either channel 1 or channel 6. WPA2 or WPA3 personal. BSS enabled or disabled. The Steam Deck will not use this band and latches to 5GHz pretty much exclusively unless band-steering is enabled and set to prefer 2.4GHz band.

5GHz with 80MHz channel width. Both APs configured for auto channel select; using channel 40. WPA2 or WPA3 personal. BSS enabled or disabled. works without issue; and the Steam Deck will pretty much exclusively latch to this unless band-steering is enabled to prefer the 2.4GHz network.

5GHz with 160MHz channel width. Both APs configured for auto channel select; using channel 48. WPA2 or WPA3 personal. BSS enabled or disabled. This works without issues, however, configuring WPA2/WPA3 has issues which appear to be due to PMF

6GHz with 160MHz channel width. WiFi 6E AP configured for auto channel select; using channel 37. WPA3 personal. BSS enabled or disabled (irrelevant as this is the only AP that is on the 6GHz band). works without issue.

Single SSID for all bands

2.4GHz with 20MHz or 40MHz channel width. Both APs configured for auto channel select; using either channel 1 or channel 6. WPA2 or WPA3 personal. BSS enabled or disabled. The Steam Deck will not use this band and latches to 5GHz pretty much exclusively unless band-steering is enabled and set to prefer 2.4GHz band.

5GHz with 80MHz channel width. Both APs configured for auto channel select; using channel 48. WPA2 or WPA3 personal. BSS enabled or disabled. works without issue; and the Steam Deck will pretty much exclusively latch to this unless band-steering is enabled.

5GHz with 160MHz channel width. Both APs configured for auto channel select; using channel 48. WPA2 or WPA3 personal. BSS enabled or disabled. This works without issues, however, configuring WPA2/WPA3 has issues which appear to be due to PMF

6GHz with 160MHz channel width. WiFi 6E AP configured for auto channel select; using channel 37. WPA3 personal. BSS enabled or disabled (irrelevant as this is the only AP that is on the 6GHz band). The Steam Deck will not connect to this and will always latch to the 5GHz band. I have to enable band-steering to get it to move to the 6GHz band.

With WPA2/WPA3 configured and the 5GHz band using 160MHz channel width the Steam Deck will intermittently connect to the 6GHz band without issue, however, when it first tries to connect to 5GHz it will fail and will continue flapping trying to latch on to the 5GHz band.

Testing without Mesh

Removed the WiFi 6 AP from the configuration temporarily and re-tested the same as above and it did not change the behavior

Summary

There definitely appears to be multiple issues, and further I suspect that one or more of these issues is partially due to router vendors improperly implementing certain features such as WPA2/WPA3 Transitional (mixed mode), Protected Management Frames (PMF), etc.

I think this is a large part of the issue, where by Valve just assumed wifi device vendors would properly and fully implement all of the features for a specific standard and so they just implemented things "by the book" for the relevant standards without handling incompatibilities.

The issue where people no longer are able to see any networks after connection failure until they reboot the Steam Deck appears to be the Steam Decks WiFi controller firmware crashing when it is encountering whatever of these issues is triggering that to occur.

I haven't yet had time to finish testing configuring WPA3 and requiring PMF as I'll need to setup a separate network for that testing because many of my older IoT things don't support WPA3/PMF.

I believe the issue with "mesh" networks is either/or router vendor and/or Valve implementation with SAE-PK, and transition disable when BSS is enabled for meshing; BSS Fast Transitioning; or some combination resulting in invalid or no secret being provided when the Steam Deck is transitioning radios.

"" without handling incompatibilities""
So basically they rushed a unfinished product hoping that every person in the world haves the same router lmao

It's fckng stressing how all my devices get to connect to my wifi except the deck, and i dont think that they re so stupid to give green light to launch something that will have incompatibilities for some users, so i will say that they did it on purpose, and for what? Idk they still dont talk about this issue and its getting very annoying

[PopinFRESH]

Nguyên văn bởi AustralOK:

...
"" without handling incompatibilities""
So basically they rushed a unfinished product hoping that every person in the world haves the same router lmao

It's fckng stressing how all my devices get to connect to my wifi except the deck, and i dont think that they re so stupid to give green light to launch something that will have incompatibilities for some users, so i will say that they did it on purpose, and for what? Idk they still dont talk about this issue and its getting very annoying

Your whining and crying about it contributes nothing to users trying to look for solutions.

[AustralOK]

Nguyên văn bởi PopinFRESH:

Nguyên văn bởi AustralOK:

...
"" without handling incompatibilities""
So basically they rushed a unfinished product hoping that every person in the world haves the same router lmao

It's fckng stressing how all my devices get to connect to my wifi except the deck, and i dont think that they re so stupid to give green light to launch something that will have incompatibilities for some users, so i will say that they did it on purpose, and for what? Idk they still dont talk about this issue and its getting very annoying

Your whining and crying about it contributes nothing to users trying to look for solutions.

clearly u have some kind of lack of attention or u read what u want to read, i already added github links adressing the problem, system reports, github threads, linux probes, evidence that the oled is unable to connect via sudo nmcli device, if u don`t have the problem and u re just a DE little fanboy, i recommend u to move out from this thread because is none of your business, thanks

[GeoVD]

So today i've received my OLED Steam deck and guess what? I have the same wi-fi issue. Can't connect for the love of god, no matter what method I tried. I've already ordered another unit and I will return my defective one asap. Such a dissapointment this being my first experience with valve hardware

[AustralOK]

Nguyên văn bởi GeoVD:

So today i've received my OLED Steam deck and guess what? I have the same wi-fi issue. Can't connect for the love of god, no matter what method I tried. I've already ordered another unit and I will return my defective one asap. Such a dissapointment this being my first experience with valve hardware

hey , are u able to connect to wifi of any laptop or ur mobile hotspot? or not wifi at all?

[Yunalesco]

Same.
New SD today and WiFi problem

[AustralOK]

Nguyên văn bởi Yunalesco:

Same.
New SD today and WiFi problem

hey , are u able to connect to wifi of any laptop or ur mobile hotspot? or not wifi at all?

[Yunalesco]

Nguyên văn bởi AustralOK:

Nguyên văn bởi Yunalesco:

Same.
New SD today and WiFi problem

hey , are u able to connect to wifi of any laptop or ur mobile hotspot? or not wifi at all?

With Mobil it’s okay :o

[j.holski]

Can not we just politely wait for system update? It's not a simple issue to solve by Valve crew. Better for us is write them for support and let know that is a serious issue.

[AustralOK]

Nguyên văn bởi j.holski:

Can not we just politely wait for system update? It's not a simple issue to solve by Valve crew. Better for us is write them for support.

as i said before, i can wait all the time of the world if Valve wants, but they dont tell us if its software or hardware related issue, if its hardware we only have 2 weeks to return and get full refund by EU law, we want a update from them telling us what the hell is going on with these devices

[AustralOK]

Nguyên văn bởi Yunalesco:

Nguyên văn bởi AustralOK:

hey , are u able to connect to wifi of any laptop or ur mobile hotspot? or not wifi at all?

With Mobil it’s okay :o

same here, im only able to use my wifi if i connect it to hotspot of mobile or my laptop with windows 11, but no case if i want to plug it directly to the router