No Wifi and Bluetooth in system tray (KDE, Manjaro)

Leviathan42 · 10-02-2021, 03:49 AM

As the title says, the wifi and bluetooth symbol wont show up in my system tray after i reinstalled my distro. I already found out that i had to manually install plasma-nm but even after that it didnt work. Both things work fine inside the live-usb and on Windows, so i can rule out any hardware issues.

Here you have the outputs of lspci, ifconfig and iwconfig:

lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d4)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d4)
00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d4)
00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 (rev d4)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 04)
00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04)
01:00.0 VGA compatible controller: NVIDIA Corporation GK106M [GeForce GTX 770M] (rev ff)
01:00.1 Audio device: NVIDIA Corporation GK106 HDMI Audio Controller (rev ff)
03:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 13)
04:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01)
05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader (rev 01)

ifconfig
enp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.203 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::8e89:a5ff:fe0c:5cfe prefixlen 64 scopeid 0x20<link>
ether 8c:89:a5:0c:5c:fe txqueuelen 1000 (Ethernet)
RX packets 3643471 bytes 3678112738 (3.4 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 240391 bytes 32453142 (30.9 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 18

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 8 bytes 400 (400.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8 bytes 400 (400.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlp4s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 0c:84:dc:03:ae:53 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

iwconfig
lo no wireless extensions.

enp3s0 no wireless extensions.

wlp4s0 IEEE 802.11 ESSID

ff/any
Mode:Managed Access Point: Not-Associated Tx-Power=16 dBm
Retry short limit:7 RTS thr

ff Fragment thr

ff
Power Management

ff

camorri · 10-02-2021, 01:04 PM

It appears your wired ethernet has an IP address, do you have communication with your netowrk?

Your wireless adapter is probably your bluetooth adapter also. The ath9k driver is listed as the correct driver. Is it loaded? If not, as root, ( or sudo ) you can load it. The other possibility is missing or down level firmware.

You have not told us if they worked before on the same hadrware system and same level of operating system. So, exactly, what version oversion of Manjaro are you running?

Leviathan42 · 10-02-2021, 01:27 PM

Quote:

Originally Posted by camorri

It appears your wired ethernet has an IP address, do you have communication with your netowrk?

yes, wired internet works fine.

Quote:

Originally Posted by camorri

Your wireless adapter is probably your bluetooth adapter also. The ath9k driver is listed as the correct driver. Is it loaded? If not, as root, ( or sudo ) you can load it. The other possibility is missing or down level firmware.

how can i load it or check whether it is?

Quote:

Originally Posted by camorri

You have not told us if they worked before on the same hadrware system and same level of operating system. So, exactly, what version oversion of Manjaro are you running?

21.1.4

camorri · 10-02-2021, 04:03 PM

Quote:

how can i load it or check whether it is?

The lsmod command will list the loaded modules. Look for ath9k.

Leviathan42 · 10-02-2021, 04:12 PM

Quote:

Originally Posted by camorri

The lsmod command will list the loaded modules. Look for ath9k.

found it:

ath9k 188416 0
ath9k_common 40960 1 ath9k
ath9k_hw 544768 2 ath9k_common,ath9k

camorri · 10-02-2021, 06:02 PM

What have you done to configure the wi-fi adapter?

If you run the lsmod command like this:

Code:

lsmod | grep blue
bluetooth             503808  39 btrtl,btintel,btbcm,bnep,btusb,rfcomm
ecdh_generic           16384  1 bluetooth
rfkill                 28672  5 bluetooth

do you see something similar for bluetooth?

Leviathan42 · 10-02-2021, 06:03 PM

Quote:

Originally Posted by camorri

What have you done to configure the wi-fi adapter?

Nothing special. It should usually work out of the box after setting up the distro.

camorri · 10-02-2021, 06:07 PM

Quote:

Nothing special.

That means you are relaying on getting an address via dhcp from your router.

Have you any other wireless devices working?

Leviathan42 · 10-02-2021, 06:13 PM

Quote:

Originally Posted by camorri

That means you are relaying on getting an address via dhcp from your router.

To get an ip address via dhcp i'd first need to be able to connect to my router, which i am not able to do via wifi. lol

Quote:

Originally Posted by camorri

Have you any other wireless devices working?

As mentioned, my wifi works fine when i boot either windows or a live-usb.

computersavvy · 10-02-2021, 07:17 PM

The fact it works in windows and from the live usb tells me the device is working fine.

We just need to identify it to make sure the proper driver is installed.
Please post the output of "inxi -Nxx" You may need to install inxi first.
Also the output of "uname -a"

Please post everything you copy from the screen within code tags so it retains the formatting you see on the screen. The code tag is gotten by using the # seen on the top bar after you select the "go advanced" button at the bottom of the text window where you enter your post.

Leviathan42 · 10-02-2021, 07:51 PM

Code:

Network:   Device-1: Qualcomm Atheros Killer E220x Gigabit Ethernet vendor: Micro-Star MSI driver: alx v: kernel port: d000 
           bus-ID: 03:00.0 chip-ID: 1969:e091 
           Device-2: Qualcomm Atheros AR9462 Wireless Network Adapter 
           vendor: Rivet Networks Killer Wireless-N 1202 Half-size Mini PCIe Card driver: ath9k v: kernel port: d000 
           bus-ID: 04:00.0 chip-ID: 168c:0034

Code:

Linux abyss 5.14.7-2-MANJARO #1 SMP PREEMPT Wed Sep 22 12:22:56 UTC 2021 x86_64 GNU/Linux

computersavvy · 10-02-2021, 08:55 PM

I did some searching using the info you provided for that qualcom atheros wifi card and found this. The driver used (ath9k) seems the proper one for most of the atheros cards.
https://forum.manjaro.org/t/slow-int...-adapter/43610

There are many other links for similar issues.
Apparently there is an issue with using bluetooth and wifi at the same time on the atheros wifi chips in Linux.

I have a similar card and have never had an issue with mine, but I also never have tried using bluetooth with my laptop.

I would suggest that you make certain you have disabled bluetooth then see if the wifi will work properly.

camorri · 10-03-2021, 04:34 AM

Quote:

To get an ip address via dhcp i'd first need to be able to connect to my router, which i am not able to do via wifi.

No, that is not how it works. If your system activates the wi-fi link, and dhcp is the default, it puts out a broadcast message looking for a dhcp server. Assuming the server is working, it will return an IP address for the system to use. This is all done using MAC ( burned addressing ). You do not need an IP address to get an IP address. Same on any system using dhcp.

computersavvy · 10-03-2021, 10:16 AM

Quote:

Originally Posted by camorri

No, that is not how it works. If your system activates the wi-fi link, and dhcp is the default, it puts out a broadcast message looking for a dhcp server. Assuming the server is working, it will return an IP address for the system to use. This is all done using MAC ( burned addressing ). You do not need an IP address to get an IP address. Same on any system using dhcp.

Not quite how it works with wifi (although correct with ethernet).
The OP is correct in that the wifi link has to be functional before an address can be assigned with DHCP.

The PC first looks for a wifi access point. If available then it checks if it already has credentials for that AP. If it has credentials it will ask for the connection to be established. If it does not have the credential then it will not try to connect. The wifi card has to be functional and communication possible before the connection can be established. Signal strength and quality are critical.

Only when it actually authenticates the credentials and communication is established does it do the DHCP handshake. The AP will not respond to a DHCP request until it has authenticated the connection request and already approved the connection.

If the AP is unknown to the PC then the user has to initiate the connection request.

Ethernet is hardwired so authentication is normally not required there. Wifi has 2 steps involved: first the authentication followed by DHCP.

camorri · 10-03-2021, 10:39 AM

computersavvy,

Thank-you for the clarification on wi-fi; authentification.

Since the OP stated he/she has not done any configuration, it has no chance of working unless this is a wide open access point. ( Not even sure if that exists ).

Possibly the OP needs to let us know a little bit about the sccess point that is being used.