-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wlan0: CTRL-EVENT-SCAN-FAILED ret=-1 #69
Comments
Hi @MephresGH I need you to run and post the results of the following: sudo uname -a; mokutil --sb-state; lsusb; rfkill list all; dkms status; iw dev |
Linux 5.18.15-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 29 Jul 2022 22:52:39 +0000 x86_64 GNU/Linux zsh: command not found: iw |
Hmmm... Confirm for me what distro you are using? Arch, Manjaro or ? Is it a rolling distro? I see some things that are of concern but it is not clearn what yet. |
The distribution of choice is vanilla Arch Linux. I have manually installed packages that are required for the compilation and installation of kernel drivers, too. The system is up-to-date and the 88x2bu.ko driver was installed via DKMS installation script. The configuration file was not modified. |
Okay... let's try some things.
If Arch does not have When did you download this repo? The reason I ask is because the download on your hd remains static. i can't fix it and almost every Linux kernel release requires some updating so anytime you upgrade kernel, you first need to uninstall and delete the previous version and come get a new download. |
iw does not work because I deactivated it manually; iwd and wpa_supplicant are known to conflict with each other at times. It is still installed on my system. |
...Actually, nevermind. I understood iw as part of iwd, my mistake. This is what iw spit out:
|
Okay. Now we see a wifi interface so that tells us the driver is installed and at least working somewhat. Still not sure why
I also see that mokutil must not be installed. I can't see if secure mode is enabled without it. It also means that if you are in secure mode, dkms can't key the driver resulting in a driver that will not load. Are you sure you have your country code set properly? When I see 2.4 GHz working and 5 GHz not working, that is generally the problem.
Something is messed up. dkms is bitching. Would you be willing to use the remove script and then try a manual installation so we can have better vis on what is going on? |
I installed mokutil.
I also do not know why dkms is bitching, as I installed it the way it should be. And I don't know about setting a country code, since I am from Germany and saw no anomalies in this regard 1-2 months ago. |
Run and post the results of the following: iw reg get
Nice place. I enjoyed my time there.
Have you updated your system since then? Are you on the same kernel as then? These bloody Realtek out-of-kernel drivers can be difficult to keep going. If you get pissed, relax and go to the follow link and read the first two menu items: |
Yes, I update my system regularly. The kernel was 5.10 or something when I first went back to Linux. 5.18.15 is my current Linux kernel, as I posted above. |
That explains why you have no 5 GHz. See mine below:
What you probably need to do, since most of my experience is in the Debian world, is go to the appropriate Arch forum and show them the result of your We can explore why dkms is bitching anytime you want. Even if you don't get pissed, reading my suggested reading above might be a good idea as it contains a lot of good info for Linux users that use usb wifi adapters. Regards |
I will talk in a forum later, but I'd prefer to get my hands on the dkms issue first. Are there any suspicions why the installation might have been incomplete or faulty? |
I'm not saying that the installation is incomplete or faulty. In fact, you were able to show me a wifi interface and use 2.4 Ghz so that tells me the driver is working. That you can't use 5 GHz is not the driver's fault as it is doing what it should be doing if the OS doesn't provide country information. Why dkms is bitching is unknown but I can guess: Your installation was originally using kernel 5.10 and now has 5.18 installed. I classify that as a hybrid installation in that it may haves parts from widely different time periods and changes that are not fully compatible. The best idea I have right now if for you to use the dkms removal script: $ sudo ./remove-driver.sh Reboot and then we can see what a manual install does: $ make clean |
Alright, I have followed up with what you recommended, and it seems to work a bit better now. 5GHz seems to work fine, too. However, manual connecting and disconnecting still causes for stability issues and for "device could not be configured" and "secrets were required but not provided" errors, which is odd. I haven't checked for a regional fix in that regard, as that seems to not be required at all from what I have tested so far. It merely seems like either the driver is unstable, or my device is, even though my device never overheats and behaves quite normally, even being connected on a USB3.0 port while having USB2.0-USB3.0 options in the driver enabled. |
Status? |
Greetings. I have been facing odd issues as of late with my TP-LINK Archer T3U; WiFi would randomly cut off, stutter throughout the day, and behave weird as a whole. While looking in confusion into the systemd logs, i found that wpa_supplicant spams the error message mentioned in the title. NetworkManager says the following:
platform-linux: do-change-link[3]: failure changing link: failure 1 (Operation not permitted)
device (wlan0): set-hw-addr: failed to set MAC address to ((blank)) (scanning) (NME_UNSPEC)
device (wlan0): supplicant ninterface state: disconnected - inactive
I installed the driver without modifying any settings later on or while having installed said driver. Is there a fix for this issue? Thank you.
PS: disabling random MAC address configurations did not help.
The text was updated successfully, but these errors were encountered: