[Help]: Alfa AWUS036AXM device not recognized #478
Comments
|
In a terminal type |
|
Hi @laubblaeser My thoughts after looking over the info you posted: This is not a driver or firmware issue as usb adapters will show with Is there a problem with the usb port? Maybe you should try a different port if the system has multiple ports. Do you have another Linux system to test? Is it possible that some bios usb settings could be causing the problem? Can you backup your kernel to an earlier version like say 6.6? We have been seeing a LOT of problems related to wifi lately with all of the modernization that is going on. You can always burn a flash drive with a Ubuntu 24.04 image and boot to the desktop to test. That would allow you to test a different distro and kernel without installing anything. Cheers |
Sure, here's the output: |
Yeah, I figured as much but thought it's worth a shot asking here if anyone else ever experienced such a problem.
Well, only other systems with Tumbleweed on them. 😄 Certainly worth a shot to try the USB dongle on another device just to rule out that the hardware isn't failing or BIOS settings aren't blocking anything. But to be honest that shouldn't be the case as it works on the same machine under Windows without any issues. |
Interesting that this line shows in the log but not with |
Forgot to answer this. I've tried 7 different ports on the machine so far. The dongle always lights up but doesn't show up in |
That just means it is getting power.
Had to try it. |
|
Type |
|
So it just worked while I plugged it in and out multiple times in a row. Here's a bit more dmesg output showing the failed and successful attempts. It seems as if sometimes the stack doesn't properly load and some probing fails? Does this help in any way? So this means that
|
I would try booting a different kernel via USB. |
|
Is your cpu amd or intel? |
Currently have to deal with data limits from a metered connection. Maybe it's really worth a shot at some point but maybe this regression (?) will be fixed at some point in the near future.
|
I have emailed a person that can provide a workaround for us to try. Standby. FYI: This seems to only happen on AMD cpus. No idea why at this point... and it is only with the Alfa adapters... the AXM and ACML. This is the first time, if this is the issue i think it is, that I have seen a report from an AXM owner. |
|
@laubblaeser I don't expect any fix in the next time: You can try to bisect the Linux kernel to identify the patch that caused this issue. |
|
The quick way to test and see if we are the right track is to delete the bluetooth firmware: $ sudo rm /usr/lib/firmware/mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin* Thanks for @ZerBea for helping out. Evidently this only shows up on AMD systems. Until very recently I only had Intel and ARM64 systems and had not ran into this issue. I have an AMD mini pc now but am not configured to test yet. This is really a mystery. We really could use feedback at to where deleting the firmware as shown above is a good workaround. |
|
Sorry for the late reply. The workaround (removing the BT driver from the firmware folder) indeed provides a good result as a workaround. The dongle instantly connects in that case and WiFi works without any issue, also for prolonged time. Haven't tested for multiple day uptimes because that's not my use case but it does work without issues for multiple hours. It's stable as far as I can tell (tested with video streaming, video calls, big downloads). Another remark on the usage in dual mode where Bluetooth stays enabled: It works after 2-3 replugs in most cases. Sometimes already on first try and sometimes after four tries. The BT driver seems to work fine at first but then causes issues as it drops its connection to the device. The devices (in my case a PS4 dual shock controller that works perfectly fine otherwise with a separate BT dongle) need to be reconnected afterwards. It's a hassle and really annoying. I hope this issue gets fixed at some point in the future because habing one dongle for both BT and WiFi would be nice. But for now there's not really anything we can do as it seems. Hope this helps. |
|
I noticed a patch that should fix this issue the other day. Hopefully it works. |
Checklist
uname
Linux ferdux 6.10.2-1-default #1 SMP PREEMPT_DYNAMIC Mon Jul 29 08:51:47 UTC 2024 (65a34e2) x86_64 x86_64 x86_64 GNU/Linuxlsusb
rfkill
dkms
iw
What happened?
The OS doesn't recognize the USB WiFi dongle at all. After plugging it in, I can run
lsusb, which takes about 60-90 seconds until it returns anything and then the listed USB ports are "empty".There's no problem with the stick itself as I've tested it on the same machine with a Windows dualboot where it gets recognized and works fine after installing the drivers. The stick was recognized exactly once after letting it plugged in when shutting down the PC from Windows and letting it reboot into Linux. Once I removed the stick and put it in any USB port of my PC again, it is not recognized again.
So, I can imagine that this is a really weird issue but it's worth a shot: Has anyone had this problem or a similar one? What can I do to track down the root of this issue?
System info
Operating System: openSUSE Tumbleweed 20240801
KDE Plasma Version: 6.1.3
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2
Kernel Version: 6.10.2-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 7800 XT
Edit@16:07: A bit of formatting.
Edit@21:54: Clarify that Windows is dual-booted on the same machine.
The text was updated successfully, but these errors were encountered: