I’ve noticed this issue since I installed EnOS. I have a USB-connected WiFi network card or a dongle. Card gets detected and gets powered on when I do a shutdown and boot or in other words a cold boot. But when I do an EnOS restart card doesn’t get detected. But when I remove the card and insert it, EnOS detects the card and starts working flawlessly until I do a reboot.
This is the details of my card,
sinux at sinux-pch in ~
↪ ethtool -i wlan0
driver: mt7601u
version: 5.10.54-1-lts
firmware-version: N/A
expansion-rom-version:
bus-info: 1-9.2:1.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
While searching I found another thread with the same issue but I think that person described the issue wrongly.
He’s describing the same issue but he’s saying WiFi drops. It’s not the connection it’s the card not getting loaded or powered on when rebooted. When a shutdown and boot happens it works without any issue. Actually, it works better than my LAN.
I’m also sorry if I’m double posting, I didn’t want to necrobump the post, and that post is still open.
Yes my friend. It’s not a new chip, it’s old but it supports monitor mode (you know what I mean ). It’s strange why it works when rebooted or reinserted after a reboot but not after an actual reboot.
You are probably right I just wanted you to check if it’s older or same driver version. There is a driver in the AUR which is the dkms version. Not sure it’s any better or worse.
I tried @Dev0ut suggestion which didn’t work. Because the USB dongle is not detected. Below is the output.
sinux at sinux-pch in ~
↪ ifconfig wlan0 disable
disable: Unknown host
ifconfig: `--help' gives usage information.
sinux at sinux-pch in ~
↪ sudo ifconfig wlan0 disable
[sudo] password for sinux:
disable: Unknown host
ifconfig: `--help' gives usage information.
sinux at sinux-pch in ~
↪ sudo ifconfig wlan0 enable
enable: Unknown host
ifconfig: `--help' gives usage information.
I’ve to try the drivers and see but I’m kind of scared because AUR seems to have caused an issue and don’t know if compiling from source would end up my wifi disabled.
@Dev0ut
If you read through which i just quickly skimmed it say’s.
The USB specification states that all USB devices must support power
management. Nevertheless, the sad fact is that many devices do not
support it very well. You can suspend them all right, but when you
try to resume them they disconnect themselves from the USB bus or
they stop working entirely. This seems to be especially prevalent
among printers and scanners, but plenty of other types of device have
the same deficiency.
For this reason, by default the kernel disables autosuspend (the
power/control attribute is initialized to “on”) for all devices other
than hubs. Hubs, at least, appear to be reasonably well-behaved in this regard.
Well that’s just what the documentation say’s and i only skimmed it real quick. It’s quite a few pages so i didn’t read it all only what i picked up on quickly with a glance.
Do you think that it’s worth trying that parameter?
If a driver knows that its device has proper suspend/resume support,
it can enable autosuspend all by itself. For example, the video
driver for a laptop's webcam might do this (in recent kernels they
do), since these devices are rarely used and so should normally be
autosuspended.
From what I’ve understood the driver might force it
). It’s strange why it works when rebooted or reinserted after a reboot but not after an actual reboot.
