Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
1) enable developer mode, then go to the new "developer" tab in steam settings and disable wifi power savings
2) unhide your wifi ssid if hidden (hiding it is well know to not really be useful for privacy nor for security, by the way)
3) if 2,4GHz and 5GHz bands are joined in a single ssid, split them in the router configs and use only one of them
4) choose a fixed wifi channel instead of leaving it in auto (configure the same channel in both the router and the deck)
5) try a different router brand/model or a smartphone wifi hotspot... some people have issues only with certains devices but not with others
6) try an ethernet dongle instead of the deck's wifi
7) try a wifi dongle with well-known good linux support instead of using the built-in wifi chip
Mines done that a few times after an update
https://help.steampowered.com/en/faqs/view/1B71-EDF2-EB6D-2BB3
Usually it should look like this but there was only the loopback interface shown.
1: lo:
2: wlan0:
I somehow was able to get it fixed again by re-imaging the Steam Deck and doing some magic stuff. But at some point the wifi got dropped again and "no networks found" error was displayed when I switched back to the network selection of the setup wizard.
When the Steam Deck arrived yesterday it worked pretty well and I downloaded a lot of games until the evening when I tried to connect my headphones via Bluetooth. I've some feelings that this might caused the connectivity issues but I have no evidence.
Unfortunately my Steam Deck is now unusable and hope that Valve is working on a fix.
being held up during initial setup due to unsuccessful download of updates is probably due to interrupted download
random short drops are one of the common manifestations of the Deck's wifi instabilities, which can look like what you described during that update download
when the download stagnates you should also check wether the wifi is disconnected and unable to auto-reconnect (another common behaviour)
if that doesn't work and Valve support gives you a hard time, you can rule out some hardware issues by flashing a linux liveboot .iso to an usb stick anb booting to a "normal" linux PC distro on the deck from usb paired with a keyboard and mouse... Linux Mint is very easy to work with:
https://linuxmint.com/
edit: i just remembered some people fixed initial setup issues by placing the deck back in battery storage mode then booting it again... not sure it helps your issue but not hard to try
Hope this helps
- Wiping everything with a GParted live iso before restoring
- Connecting to a hard-wired ethernet jack with a USB-C adapter
- Using my phone as a hotspot
- Switching my router to 2.4 GHz and 5 GHz exclusively
- Assigning a static IP to my wireless connection
Returning this craphole and gonna hold out for a switch 2
a few brands get mentioned more often because tgere are more models doing things the way the Deck can't handle properly, but it's model/revision/firmware-version-specific not everything from brand X and nothing from brand Y
It affects proportionally few people because it works fine with most other hardware, but when you sell millions those things end up being noticed by enough people (looks like hundreds of folks by the amount of buzz in the Steam Deck discussions)...
people who are affected aren't usually willing to change all their other gear to escape the issue (which is totally understandable... it should just work), so it's not going to change until actually fixed, which has proven to be really really hard!
We already have solid info that Valve put their engineers on it since the early days of Decks being shipped and there was even users with related background volunteering to help debug it... there has been noticable improvents (less frequent issues, less people complaining, updates with wifi fixes on the changelogs), but nothing definitive yet after several months...
...hence why I always mention the workarounds
Meanwhile others have zero issues and some have issues only with one other device but not the rest, so are OK living with it. It's probably ok for most folks to change to a better home router if the current one is crap and they were already thinking of changing it before running into the Deck issue, etc, etc
Yes, you're right, this is not a negligible issue. But Valve isn't neglecting it, they're just having their hides flayed by it and unable to end it yet. Given the absurdly nice price vs. performance ratio the Deck offers otherwise, I can't be surprised so many folks chose to live with this, but neither is it surprising that people more completely prevented to use it are returning their units.
Each use-case is different, each user has different priorities, such is the world.
If you're on the more unfortunate group, make your return request. AFAIK they have been honoring those without fuss just like the replacement ones.