You are not logged in.
Hi, I recently switched to arch from garuda. I have a issue with wifi not connecting now. I tried hard enough to look for this issue on the internet, I tried to boot into live arch iso and connecting to my wifi using iwctl (results in "Operation failed"), even asked a few friends, no profit. Whereas when I just boot into live garuda, wifi works just fine.
-Technical details-
Host: Arch Linux x86_64
Kernel: 5.16.14-zen1-1-zen
CPU: Intel Pentium G4400 (2) @ 3.300GHz
lsmod: https://bin.garudalinux.org/?8b71736388 … zs1rMwKnYE
lspci: https://bin.garudalinux.org/?c4b65550e0 … kj4piZZ9Je
Wifi adapter: Realtek 802.11n WLAN Adapter
Wifi device: JioFi3
-The issue with my wifi-
Most of the time, my wifi device isn't even spotted when I see on NetworkManager, I then unplug and plug in my adapter, and that at a rare case spots my device and I try to connect, sometimes connects and sometimes just fails after a few seconds and the device is again gone from the list. Another thing I noticed is that, when nm detects my device, nm-applet shows that my device range is too far away ( https://i.imgur.com/o1V42nQ.png ), even though my device is kept right next to my desk.
What exactly am I doing wrong? Help would be highly appreciated!
Last edited by EkaSaffronGaruda (2022-03-18 05:36:04)
Offline
There's neither a wifi controller nor an unassigned device in the lspci and "unplug and plug in my adapter" sounds like it's USB connected.
"Realtek 802.11n WLAN Adapter" is meaningless and so is the wifi router you're probably trying to connect to.
Please post the output of "lsusb" and a complete system journal "sudo journalctl -b"
Online
lsusb -v: http://0x0.st/oNKJ.txt
sudo journalctl -b: http://0x0.st/oNKy.txt
Offline
Bus 001 Device 010: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter
Mar 18 09:01:13 eka-arch-1337 wpa_supplicant[415]: wlp0s20f0u3: CTRL-EVENT-CONNECTED - Connection to 9c:30:5b:99:f1:1a completed [id=0 id_str=]
You do connect to the AP, though?
Based on
…
Mar 18 13:59:51 eka-arch-1337 NetworkManager[378]: <info> [1647592191.2867] device (wlp0s20f0u3): set-hw-addr: set MAC address to 26:28:DD:52:40:7E (scanning)
Mar 18 13:59:54 eka-arch-1337 NetworkManager[378]: <info> [1647592194.4405] device (wlp0s20f0u3): supplicant interface state: disconnected -> interface_disabled
Mar 18 13:59:54 eka-arch-1337 NetworkManager[378]: <info> [1647592194.4409] device (p2p-dev-wlp0s20f0u3): supplicant management interface state: disconnected -> interface_disabled
Mar 18 13:59:54 eka-arch-1337 NetworkManager[378]: <info> [1647592194.4410] device (wlp0s20f0u3): supplicant interface state: interface_disabled -> disconnected
Mar 18 13:59:54 eka-arch-1337 NetworkManager[378]: <info> [1647592194.4410] device (p2p-dev-wlp0s20f0u3): supplicant management interface state: interface_disabled -> disconnected
Mar 18 14:06:47 eka-arch-1337 NetworkManager[378]: <info> [1647592607.2872] device (wlp0s20f0u3): set-hw-addr: set MAC address to DE:44:C3:99:38:6B (scanning)
Mar 18 14:06:50 eka-arch-1337 NetworkManager[378]: <info> [1647592610.5371] device (wlp0s20f0u3): supplicant interface state: disconnected -> interface_disabled
Mar 18 14:06:50 eka-arch-1337 NetworkManager[378]: <info> [1647592610.5372] device (p2p-dev-wlp0s20f0u3): supplicant management interface state: disconnected -> interface_disabled
Mar 18 14:06:50 eka-arch-1337 NetworkManager[378]: <info> [1647592610.5382] device (wlp0s20f0u3): supplicant interface state: interface_disabled -> disconnected
Mar 18 14:06:50 eka-arch-1337 NetworkManager[378]: <info> [1647592610.5382] device (p2p-dev-wlp0s20f0u3): supplicant management interface state: interface_disabled -> disconnected
Mar 18 14:13:43 eka-arch-1337 NetworkManager[378]: <info> [1647593023.2939] device (wlp0s20f0u3): set-hw-addr: set MAC address to 46:AA:5F:C1:4C:F7 (scanning)
Mar 18 14:13:46 eka-arch-1337 NetworkManager[378]: <info> [1647593026.4830] device (wlp0s20f0u3): supplicant interface state: disconnected -> interface_disabled
Mar 18 14:13:46 eka-arch-1337 NetworkManager[378]: <info> [1647593026.4833] device (p2p-dev-wlp0s20f0u3): supplicant management interface state: disconnected -> interface_disabled
Mar 18 14:13:46 eka-arch-1337 NetworkManager[378]: <info> [1647593026.4911] device (wlp0s20f0u3): supplicant interface state: interface_disabled -> disconnected
Mar 18 14:13:46 eka-arch-1337 NetworkManager[378]: <info> [1647593026.4914] device (p2p-dev-wlp0s20f0u3): supplicant management interface state: interface_disabled -> disconnected
…
I'd try to disable https://wiki.archlinux.org/title/Networ … domization
Online
Mar 18 09:01:13 eka-arch-1337 wpa_supplicant[415]: wlp0s20f0u3: CTRL-EVENT-CONNECTED - Connection to 9c:30:5b:99:f1:1a completed [id=0 id_str=]
Yeah as I mentioned it connects sometimes, although with poor network connection.
And I just added these lines
[device]
wifi.scan-rand-mac-address=no
to /etc/NetworkManager/NetworkManager.conf and restarted the NetworkManager service. Didn't help
Offline
I would boot the machine from a garuda live medium and compare the WiFi situation (driver, firmware) to arch.
Offline
I am a newbie so I am a bit confused so sorry about that.
Garuda lsmod: http://0x0.st/oNZx.txt
Arch lsmod: attached in the first post
Offline
Unsurprisingly they're using the same modules.
Post the journal from the garuda system - and try the vanilla and/or LTS kernel on arch instead of the zen one…
Online
Is that necessary, I was using zen kernel too on garuda
Offline
Posting the journal is is necessary for sure and testing a different kernel always a good idea to isolate the cause …
Online
The issue is no more, I don't know what was causing the issue but, now I can connect to my wifi and use the internet with no trouble. Appreciate your time, thanks a lot!
Offline
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Online