You are not logged in.
Pages: 1
After making a fresh automatic install on an x86 machine with everything going smoothly an error appeared trying to connect to a wireless network:
SSID not found
This is despite the network having been selected from the list of available ones.
What's going on?
Last edited by PoofyGummy (2022-10-06 12:34)
Offline
You could try to bypass TDE network manager and use lower level utility "nmtui", what is not dependent on Trinity desktop at all. Just run in terminal as a user:
$ nmtui
and post back the result.
Offline
Same error. Could not activate connection: Activation failed: The Wi-Fi network could not be found
Which is odd, considering I had selected it from the list of available networks, and it asked for the password and everything.
I would assume it to be a driver thing because the TP-Link TL-WN8200ND ver1 device is not the newest, but not only did Windows manage to connect, but even the network manager itself did, in order to find out that I needed a password.
How do I access the network manager logs?
Last edited by PoofyGummy (2022-10-06 13:52)
Offline
How do I access the network manager logs?
Run in terminal:
$ sudo journalctl
for the complete system log
Offline
The one that stands out is:
<warn> [timestamp] device (wlx30b5c2141692): Activation: (wifi) association took too long, failing activation
As a stopgap measure I managed to make a wired connection, and that works without issues. It's something with the wifi.
Last edited by PoofyGummy (2022-10-08 00:25)
Offline
This issue still persists by the way.
Offline
2 seconds work with Google tells us that this adapter has always been a pain with linux. There was a linux driver for the V2 adapter but that only worked with kernels in the 2.x range.
Just accept that it doesn't/won't work and get one of these https://www.amazon.co.uk/gp/product/B008FZO1A2
They're cheap as cheap can be and DO work with linux out of the box.
Offline
I want to utilize existing infrastructure, not refurbish a computer that could legally drink...
I also thought there was a driver for v1.0.
Plus i thought a working driver was already installed since the wifi network detection clearly works, and none of my problems are similar to problems reported with the same chip.
And i've seen driver issues with plenty of devices under linux hence why i wanted help with fixing them. Not just the advice to give up, lol.
Last edited by PoofyGummy (2022-10-19 04:47)
Offline
Pages: 1