Network Adapter - CTRL EVENT SCAN FAILED (unstable hardware)

salmanahmed · 08-07-2021, 07:19 AM

Hi
I am using Manjaro Linux over an old HP Laptop (HP Pavilion G6 2298SE). This Laptop has following Network Adapter:

Code:

07:00.0 Network controller: Ralink corp. RT5390R 802.11bgn PCIe Wireless Network Adapter

The problem is that I am frequently being disconnected from internet (4-5 times a day). When this happens then the NetworkManager shows no wireless connection in its list. After disconnection, the "lspci" shows the Network Adapter in its results. However, "ifconfig" does not show the Network Adapter in its result. And "journalctl -xe" show following messages at the instance of disconnection:

Code:

Aug 07 16:18:36 pc wpa_supplicant[860]: wlo1: CTRL-EVENT-DISCONNECTED bssid=11:22:33:44:55:66 reason=4 locally_generated=1
Aug 07 16:18:36 pc wpa_supplicant[860]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Aug 07 16:18:36 pc NetworkManager[805]: <info>  [1628335116.4861] device (wlo1): supplicant interface state: completed -> disconnected
Aug 07 16:18:36 pc NetworkManager[805]: <info>  [1628335116.6025] device (wlo1): supplicant interface state: disconnected -> scanning
Aug 07 16:18:51 pc NetworkManager[805]: <warn>  [1628335131.8396] device (wlo1): link timed out.
Aug 07 16:18:51 pc NetworkManager[805]: <info>  [1628335131.8400] device (wlo1): state change: activated -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Aug 07 16:18:51 pc NetworkManager[805]: <info>  [1628335131.8404] manager: NetworkManager state is now DISCONNECTED
Aug 07 16:18:53 pc avahi-daemon[801]: Interface wlo1.IPv6 no longer relevant for mDNS.
Aug 07 16:18:53 pc avahi-daemon[801]: Leaving mDNS multicast group on interface wlo1.IPv6 with address 1111:2222:3333:4444:5555:6666.
Aug 07 16:18:53 pc avahi-daemon[801]: Interface wlo1.IPv4 no longer relevant for mDNS.
Aug 07 16:18:53 pc avahi-daemon[801]: Leaving mDNS multicast group on interface wlo1.IPv4 with address 192.168.10.100.
Aug 07 16:18:53 pc avahi-daemon[801]: Withdrawing address record for 1111:2222:3333:4444:5555:6666 on wlo1.
Aug 07 16:18:53 pc NetworkManager[805]: <info>  [1628335133.4017] device (wlo1): set-hw-addr: set MAC address to 54:CA:64:85:34:E2 (scanning)
Aug 07 16:18:53 pc avahi-daemon[801]: Withdrawing address record for 192.168.10.100 on wlo1.
Aug 07 16:18:54 pc kernel: ieee80211 phy0: rt2800_wait_csr_ready: Error - Unstable hardware
Aug 07 16:18:54 pc NetworkManager[805]: <warn>  [1628335134.4128] platform-linux: do-change-link[2]: failure changing link: failure 16 (Device or resource busy)
Aug 07 16:18:54 pc NetworkManager[805]: <warn>  [1628335134.4131] device (wlo1): Activation: failed for connection 'Home'
Aug 07 16:18:54 pc wpa_supplicant[860]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-100
Aug 07 16:18:54 pc dbus-daemon[803]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=805 comm="/usr/bin/NetworkManager --no-daemon ")
Aug 07 16:18:54 pc NetworkManager[805]: <info>  [1628335134.4144] device (wlo1): supplicant interface state: scanning -> interface_disabled
Aug 07 16:18:54 pc NetworkManager[805]: <info>  [1628335134.4147] device (wlo1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Aug 07 16:18:54 pc systemd[1]: Starting Network Manager Script Dispatcher Service...

Few months back, this used to happen rarely (once a week or bi-weekly), but now the problem is more frequent (4-5 times a day). In order to fix it, I have to reboot my Laptop then the Network Adapter again started to work fine (for a while).
So, the question is that: Is my Network Adapter dying? or Is there any other problem with it (driver, power management etc.)?
Can you help me in this regard?
Thanks

salmanahmed · 08-07-2021, 12:27 PM

After posting the above message, the problem occurred again (just now), so I ran the necessary commands to gather information:

Code:

[user:pc:~]lshw -class network
  *-network DISABLED        
       description: Wireless interface
       product: RT5390R 802.11bgn PCIe Wireless Network Adapter
       vendor: Ralink corp.
       physical id: 0
       bus info: pci@0000:07:00.0
       logical name: wlo1
       version: 00
       serial: 11:22:33:44:55:66
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi pciexpress cap_list ethernet physical wireless
       configuration: broadcast=yes driver=rt2800pci driverversion=5.4.135-1-MANJARO firmware=0.40 latency=0 link=no multicast=yes wireless=IEEE 802.11
       resources: irq:16 memory:c3500000-c350ffff

and:

Code:

[user:pc:~]lspci | grep -i wireless
07:00.0 Network controller: Ralink corp. RT5390R 802.11bgn PCIe Wireless Network Adapter

"wlo1" is missing in "ifconfig" output:

Code:

[user:pc:~]ifconfig
eno1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 11:22:33:44:55:66  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

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 555  bytes 46097 (45.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 555  bytes 46097 (45.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

But "wlo1" is present and DOWN in "ip" output:

Code:

[user:pc:~]ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlo1: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 11:22:33:44:55:66 brd 11:22:33:44:55:66
3: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether 11:22:33:44:55:66 brd 11:22:33:44:55:66

But unable to bring it UP:

Code:

[user:pc:~]sudo ip -force link set up wlo1
RTNETLINK answers: Device or resource busy

kamazeuci · 06-28-2023, 12:22 PM

I am having the same problem on an HP laptop with a Realtek RTL8111/8168/8411

Code:

ieee80211 rt2800_wait_csr_ready error unstable hardware

On MX Linux Wildflower
it happens on both XFCE and KDE version

any ideas?

business_kid · 06-28-2023, 01:37 PM

@salmanahmed: You don't say whether you're on 2.4GHz or 5GHz channels. It matters because the 2.4GHz band is very crowded and you could be having amazing difficulties because of that. Try

Code:

sudo iwlist wlo1 scan |grep -A3 Frequency |less

That should give you a section like this

Code:

 Frequency:2.452 GHz (Channel 9)
                    Quality=70/70  Signal level=-40 dBm  
                    Encryption key:on
                    ESSID:*************

Notice the channel number on the frequency line. On the 2.4GHz channels, nearby channels interfere. Many routers put on 'automatic channel selection' sit on channel 1 and never move. Let's see what your setup is doing.

@kamazeuci: you have an RJ45 wired network. This is a thread about wifi, which is completely different. Start your own separate thread and give full details there, not here. It's rude to post your problem on top of someone else's. It's called thread hijacking.

Arnulf · 06-28-2023, 01:44 PM

WLAN adapter cards Ralink RT5390R & Ralink RT2800:

Open laptop.
Remove WLAN adapter card.
Unplug antenna from WLAN adapter card.
Clean contacts of WLAN adapter card.
Plug antenna to WLAN adapter card.
Insert WLAN adapter card.
Test it again.

If error occurs again WLAN adapter card is dying.

Hint: Realtek RTL8111 & RTL8168 are 1000base-T LAN devices, not WLAN devices, and RTL 8411 is a card reader.

kamazeuci · 06-28-2023, 03:45 PM

I'm sorry.
RT3290 is the wifi adapter. the other is the ethernet, but the wifi is what is giving problems.
I was not hijacking the thread, I was resurrecting it from death because it had no solution nor replies and I had the same problem.

I tried installing 6.10 kernel but problem persisted.
Turns out I installed Linux Mint and now problem went away.
I don't know what it is exactly, maybe a different firmware/driver being used by Linux Mint?

anyway

The problem was not that the adapter was not finding networks or having low radio signal. The problem was that it went totally off.

thanks for your help

kamazeuci · 06-29-2023, 08:58 AM

So, I was wrong.
The problem persisted in Linux Mint. It's just that I tested it for 3 hours and nothing happened... but then the next day it happened again.
I edited

Code:

/etc/NetworkManager/conf.d/default-wifi-powersave-on.conf

and changed

Code:

wifi.powersave = 3

to

Code:

wifi.powersave = 2

and now if I type

Code:

iwconfig

I get the message that power management is off, but it seems to turn back on again.

business_kid · 06-29-2023, 09:15 AM

In the edit you show, the two entries are the same. I'd remove that file altogether, or move it to another directory and see if that helps. I should tell you that one great advantage of my distribution of choice is that I can and do avoid networkmanager and systemd altogether. I use Slackware64.

kamazeuci · 06-29-2023, 10:37 AM

oops sorry Again
I made a mistake, again
Now I corrected it
I changed the file to

Code:

wifi.powersave = 2

onebuck · 06-29-2023, 11:03 AM

Quote:

Originally Posted by kamazeuci

I'm sorry.
RT3290 is the wifi adapter. the other is the ethernet, but the wifi is what is giving problems.
I was not hijacking the thread, I was resurrecting it from death because it had no solution nor replies and I had the same problem.

I tried installing 6.10 kernel but problem persisted.
Turns out I installed Linux Mint and now problem went away.
I don't know what it is exactly, maybe a different firmware/driver being used by Linux Mint?

anyway

The problem was not that the adapter was not finding networks or having low radio signal. The problem was that it went totally off.

thanks for your help

It would have been better to create a new thread with relative information instead of resurrecting & hijacking a necro thread. Please keep that in mind when posting here at LQ.

You might consider looking at LQ Rules again so you can post properly. Plus this may help you in the future; https://www.linuxquestions.org/questions/faq.php?faq=welcome

kamazeuci · 07-02-2023, 09:13 AM

I'm sorry if I hijacked the thread. I have read the rules and I think my problem is the same that @salmanahmed had, and he had no answers, so I thought the best was to post here inside creating a new post. Maybe the solution would serve the OP.

Anyway, problem is persisting, this computer will be brought to me again tomorrow and I will try what appears here:
https://unix.stackexchange.com/quest...nt-permanently
In order to try to make power management disabling permanent.
Although this might not be the solution...
Anyway, I'll post the results here.