Hidden SSID WiFi issues

[VanDaGo]

I know some have WiFi connection issues. When using the deck UI you do not have that fine grained settings option as you have in desktop mode, with NetworkManager.

I solved my issues switching to desktop mode and setting it up there. And since I also use hidden SSID I also defined it there.

Maybe this can help some.

[intenselygoodtime]

This was helpful (you still have to go through the first setup tool once before you can access the Linux Desktop mode), however the Steam Deck simply will not connect to either of my SSIDs. WPA supplicant fails -- and I have literally dozens of other lesser Linux boxes (servers, Raspberry Pi boxes, Intel NUCs) all connected fine using wpasupplicant.

[Turbo]

Don't know if this is related, but my Linux Laptop with Broadcom hardware stopped working with hidden SSID's a while back. There was some change in the driver which broke connecting to hidden networks.

[Léon Scarlet]

Same for me but nothing work
its kinda piss me off considering how long the download on steam deck is.
(2mb) when i download at 15 mb at house

[intenselygoodtime]

Originally posted by Turbo:

Don't know if this is related, but my Linux Laptop with Broadcom hardware stopped working with hidden SSID's a while back. There was some change in the driver which broke connecting to hidden networks.

That is actually VERY helpful to know. As soon as I can get a persistently-working on-screen-keyboard, I can start troubleshooting the driver and wpasupplicant properly.

[Turbo]

Sounds like we're talking the same thing. I'm on Fedora 36 now on the laptop and have stopped using hidden networks because of wider ranging hidden network issues which might be related.

I first noticed this I think with Fedora 30. The solution was to uninstall wpa_supplicant and install this one: wpa_supplicant-2.6-17.fc29.x86_64.rpm. After doing that, the hidden networks would work again.

This worked for a few more major releases of Fedora, but I stopped using hidden networks at some point as I said.

Hope this helps!
Regards, Patrick

[SneakyJoe.RU 🌐 #StopWar]

It's still not fixed after half a year...

[Turbo]

The was an update to the Broadcom drivers at some point which caused this problem on many different devices. It's been like this for years. Probably not likely to be fixed.