Hello!
I have an old Dell Inspiron 5537 with Manjaro KDE. Since a couple of weeks, wifi doesn’t work properly with other users anymore, only for myself (the admin). In other users, our home networks gets automatically connected as expected, works for something like half a minute, then disconnects. At this point, most networks disappear from the list of available networks as well. After maybe half a minute, all become listed again, and the network manager reconnects to our home network. After some 10 or less seconds, it disconnects again, and the cycle restarts.
There has been no change in the enviroment (router, ISP) and no concious change in the software, but probably regular Manjaro updates. As said, my user has no issue. Works as expected.
Any help on how to fix this issue?
Thanks!
More information is likely needed.
- Are you multi-booting with Windows?
Please provide system information as described (below) according to forum guidelines.
Regards.
[MiniHowTo] Provide System Information
Basic details provided by *-fetch type apps might give enough information for someone wishing to buy a computer, however, for Support purposes it’s best to ask your system directly.
Output of the inxi command will generate more useful and detailed information for those who may wish to help:
Suggested inxi command (use either):
inxi -zv8 |
(short-form) |
inxi --filter --verbosity=8 |
(long-form) |
- man inxi (The
inximanual)
Command output should be presented as pre-formatted text in accordance with forum guidelines. ![]()
Running inxi within a chroot environment
- Add
--color=0to the long-form command, or… - Change the short-form command to
inxi -zv8c0
Your privacy is respected
[MiniHowTo] Present code or command output
Note: Grave accent (or, backtick) characters are used. ![]()
For inline code or to show a single command:
- please follow this simple example:
code here.
For multi-line command output:
- place text beween two rows of three (```) backtick characters to form a scrollable text box, or …
- use the </> button in the Compose window to achieve the same result.
The empty row between these rows of backtick characters is where to paste any multi-line command output (such as inxi).
An example of a pre-formatted text enclosure:
What is a Quark?
A. In Physics, an elementary particle and fundamental constituent of matter.
B. A character from the Star Trek: "Deep Space Nine" television series.
C. A soft, creamy, usually unsalted cheese traditional to central Europe.
Which make and model of the wifi
Is it a multi user system or are you the sysadmin at a small office?
This is all too vague to have any idea - so everything is guesswork at best.
Linux kernel is monolithic - meaning - one kernel to provide all drivers (except Nvidia).
Do you have the linux-firmware packages relating to your hardware?
It is possible that an upstream change in the kernel as changed how your devices is recognised or work.
But if it were an upstream change it would affect all users not a subset thereof - given this is only your system and not an office fleet.
Tuotteen Inspiron 15R 5537 tuki | Ajurit ja ladattavat tiedostot | Dell Suomi
Please provide some system info - simply provide the link returned from the below command formatted in a similar way
``` inxi -Fxxxc0 | curl -F'file=@-' https://0x0.st ```
Thanks!
This link:
https://0x0.st/P8Ei.txt
(I assume I have now provided the system info in the right way. If instead I was supposed to copy the text from the link file, let me know and I will do right next time)
Oh yeah, forgot to address this. This is a home computer, used only by family members (me, wife & daughter). I’m the admin and original user. Later I’ve created my wife’s, also given her admin rights. Despite this, wifi stopped working for her (as well as for my daughter, who’s no admin at all).
Thank you - exactly what was expected.
The interesting part is the Network/Bluetooth section
Network:
Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell
driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: 4000
bus-ID: 01:00.0 chip-ID: 10ec:8136 class-ID: 0200
IF: enp1s0 state: down mac: 78:2b:cb:ed:aa:35
Device-2: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter
vendor: Dell driver: ath9k v: kernel pcie: speed: 2.5 GT/s lanes: 1
bus-ID: 02:00.0 chip-ID: 168c:0036 class-ID: 0280
IF: wlan0 state: up mac: 00:71:cc:8a:68:0b
Bluetooth:
Device-1: Qualcomm Atheros AR9462 Bluetooth driver: btusb v: 0.8 type: USB
rev: 1.1 speed: 12 Mb/s lanes: 1 bus-ID: 2-1.5:8 chip-ID: 0cf3:0036
class-ID: e001
Report: rfkill ID: hci0 rfk-id: 2 state: up address: see --recommends
Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter
Search results for 'QCA9565 order:latest' - Manjaro Linux Forum
I don’t think the wifi card or the driver is causing this. I am thinking some personal user configuration may affect this - but I dont’ know what or why.
If using NetworkManager (most do) a default user will be allowed to connect to network, without further configuration.
The troubleshooting section at Network configuration/Wireless - ArchWiki may provide clues.
I am totally guessing - I have no clues - the rest is me brainstorming on what you could check.
I would check if there is hardware switch - like Fn+F<num> - or similar.
I would check power save settings affect the wifi connection - when signed in as the affected user.
I would create a new default user/password combination, and attempt to replicate the issue.
Indeed, this was one of the first things I did, as I also suspected that personal user configurations could be the reason. But unfortunately it didn’t work. I went through the troubleshooting section you mentioned. I tried some things, like the Power saving, but no success. It seems that most explanations there make more sense when network is not working at all, while in my case it’s an issue with the other users. Well, I’m completely lost…
What if, the trigger part is bluetooth ?
Does any of your users connect a bluetooth device ?
I had to search more deeply for this one, but I found a mention stackexchange of a user which only begot internet issues when a bluetooth headset was connected.
One suggestion was to create a drop-in configuration to specifically enable bluetooth co-exist. It was never marked as answer to it may not work at all
As root - create a file in /etc/modprobe.d/ name it ath9k.conf with content
options ath9k btcoex_enable=1
Remove the module (as root)
modprobe -r -v -w 1000 ath9k
Load the module (as root)
modprobe ath9k
You can use modinfo ath9k to get an extensive list of options the module supports