Description of problem: As summary. Wi-Fi seems to connect for about 10 seconds and then drop repeatedly . I am attaching all the files suggested in the wi-fi triage notes. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
Created attachment 10065 [details] dmesg output
Created attachment 10066 [details] iw dev wlp2s0 scan output
Created attachment 10067 [details] iwconfig output
Created attachment 10068 [details] iwlist scan output
Created attachment 10069 [details] journalctl output
Created attachment 10070 [details] lspcidrake output
This looks like the same issue, however the fix did not work for me: https://markandruth.co.uk/2015/06/04/solved-problems-with-connecting-ath9k-to-802-11n-network Does Mageia 6 require the options in a different file? I created the ath9k.conf manually as in the blog.
Assigning to the kernel & drivers maintainers.
Assignee: bugsquad => kernelCC: (none) => marja11
It will read the ath9k.conf on boot (or if you rmmod/modprobe ath9k again) however the contents of the file is not correct. for 4.14 series it should be: nohwcrypt=1 btcoex_enable=0 Also, are you using drakx-net or networkmanager to manage your wireless?
CC: (none) => tmb
Thanks Thomas, however changing the syntax in ath9k.conf has not changed anything. NetworkManager is not installed - this is a pristine default Plasma5 Mga6 net-install done 7 days ago with only one new updated package since then. Using DHCP it fails with "no dhcpoffers received" Using a fixed IP we get further and the connection is made for about 4 seconds (displayed by net_applet systray pop-up) but then is dropped. It then re-connects after a minute or so for another 4 seconds. etc... I am attaching journalctl -b as it is now. (journalctl1.txt)
Keywords: (none) => PATCH
Created attachment 10071 [details] journalctl -b output with fixed IP Removed patch keyword that appeared from nowhere :\
Keywords: PATCH => (none)
It seems that at some point the wifi key got corrupted, despite my checking it at least once during these investigations. All is now working. I have removed ath9k.conf and it still works OK - also tested with latest kernel. I had been setting up this connection using the 'manage wireless networks' option from the context menu of the net_applet systray icon. I finally successfully configured it using the page by page set-up in drakx_net via MCC which is where I discovered the corrupted key. I fail to understand why I was seeing "wlp2s0: authenticated" messages if the key was wrong, but assuming user error for now and closing. Closing as invalid.
Status: NEW => RESOLVEDResolution: (none) => INVALID