33
[Weekly thread] GNU+Linux help: ask anything!
(programming.dev)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 01 Sep 2024
33 points (97.1% liked)
Linux
5484 readers
450 users here now
A community for everything relating to the linux operating system
Also check out !linux_memes@programming.dev
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
Do you see any overlap on yours in the graph view?
Some, at much lower strengths. Most of the graph is covered though, and the access point is using the recommended channel. It has band steering so automatically changes the channel to optimise.
So there's a few issues at play.
That automatic channel changing feature is more harmful than helpful in this context.
If you're able to lock it onto an entirely empty channel it'll help. Try for channel 106
I have the ISP router and two AmpliFi mesh access points to provide the wifi. The ISP router also has a wifi network, this is the 2.4Ghz one for the IoT devices.
When I try to change the channel for the access points, I don't get the option for channel 106. I only get the option for 36, 40, 44, 48, 149, 153, 157, 161.
I also noticed that I had missed that there's a little button in the wifi scanning app to toggle between 2.4Ghz and 5Ghz. I noticed if I change the channel, a whole bunch of hidden networks come with it. I think this must be related to the mesh network, it's a lot of networks though! 8 or 9 of them, two separate ones with the same network name (I presume the two access points), and the rest all marked as hidden.
In the app, what does the width of the bar represent? It says something like Wifi_Network 157 (155) and has a big flat top that seems to cover a range. Is that indicating that nearby channels can interfere with each other?
Another thought of mine is that wireless devices can perform poorly if they are too close to the AP. (Like less than a meter)
Assuming you're not in a country that blocks the use of those channels. There is a bunch of corner cutting gear out there that won't let you use a big chunk of the 5ghz spectrum.
If you're shopping for new stuff look for gear that supports DFS channels in the future.
Mesh networks can perform poorly for applications that are sensitive to latency and jitter. (Such as steam's remote play)
It's possible that some of those are related. My assumption is that there's interference from your own devices and the neighbours. But a mesh network isn't an ideal environment.
This is indicative of the channel width. It's a common occurrence to have a network use overlapping channels to increase performance.
The take away is that not all channels are isolated from one another and it's possible for a network to have many of them bonded together.
With Wifi_Network 157 (155). It's indicating that the network's real channel 155 with a 80mhz channel width. But it's configured to channel 157 for its beacon as not all devices will connect in 80mhz mode. 157 represents the 20mhz channel it's configured to camp on.
Yes.
Channel chart source: https://readus247.com/best-5ghz-channel/
Wow thanks for all the info!
Huh, I wouldn't have thought of that. I'm pretty close! I'll try moving it a bit further away.
Last night it was much more stable, I didn't have any Steam dropouts (only the BG3 crashes which seem pretty common in Act 3 after having none until then, and I'm not the only one). But I do have the option to create a separate non-mesh network from the AP if I need to. If I have further trouble I'll give that a go.
When I changed the channel, the whole lot came with it, hence my assumption.
Channel 165 tends to be empty if you do try that.
If your core problem is bg3 itself crashing then I've gone on a silly tangent here.
You might find act 3 is more stable in dx11 mode assuming proton is up for the challenge.
Two issues here: Issue one, BG3 itself crashes all the time. This most likely isn't linux related, because it's been rock solid up to Act 3 and everyone across all platforms complains about all the crashing in Act 3. Solution - quick save all the time.
Issue two, sometimes Steam Remote Play will disconnect from the game. The game continues to play on the remote PC but the connection is lost, and it won't let me reconnect (which is something Steam normally lets you do, but this might be because it's a non-steam game).
Your info on wifi networks to prevent the connection dropping has definitely been relevant and helpful!
Now that patch 7 has landed has your experience improved?
Oh I hadn't realised it had! I'll have to make sure I update before I play again.
The release notes seem to cover lots of specific crashes, but I'd guess my issue is more generally that if it's trying to shoe too much stuff on the screen (like a crowded city) then it crashes. I have turned the graphics settings right down and it happens less, but still happens at least once each time I play. I'm keen to check out that patch and see if it helps. Thanks for letting me know about it!