-
Notifications
You must be signed in to change notification settings - Fork 198
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
Comfast CF-951AX & CF-953AX not functioning in AP/Master mode in OpenWrt 22.03 using Luci on Raspberry Pi 4B (N,AC, or AX) #110
Comments
Just a couple of big picture thoughts:
|
Done, thx. It's great to hear how well they work on certain devices, hopefully we can accomplish the same with the Raspberry Pi 4B, I'd be happy with Wifi 6 capabilities but 6e makes me drool, I've been following your other thread with excitement. Thanks for testing it out on your end. I will open a thread on the OpenWrt forum also. |
Short follow on. I've been testing the 951AX on my ZyXEL NBG6817 router in AX in the 2.4 band today. It is strange to see anything other than N for the 2.4 band. No problems noted. So far OpenWRT 22.03 is working very well with the 951AX with the exception that Luci can't do 6 GHz yet Now I just need a mt7921au based adapter that actually has some range. This little Comfast adapter is good for testing but it is a medium range adapter. Come on Alfa, we are waiting on the high power adapter. |
@amisix can you try to open an 11n AP first? then AC, then AX. if N and AC works and AX fails, hostapd needs to be rebuilt with AX support. |
@ayyyuki1 Yes, same issue with N, AC, and AX. Slightly different error message for each, but they have in common hostapd "invalid argument" and permission errors. Thanks. N 2.4Ghz (20Mhz channel width):
AC 5Ghz (40Mhz channel width):
AX 5Ghz (40Mhz channel width):
|
I installed the 64 bit, ext4, factory img of OpenWRT 22.03 for Raspberry Pi 4B today. I configured it to be a dumb ap. There are some serious problems. This is nowhere near the the smooth performance I saw on my Zyxel router. As I have time this week, I will sort through the logs and see what I can figure out. |
@morrownr Same version as what I ran, yes. Thanks much for confirming & taking the time to test it out. The Zyxel experience sounded great when I read of it.. |
@amisix |
I decided to clean things out and get to the bottom of some of the things I am seeing. OpenWRT for the Pi4B has problems. Example: I can't get 2.4 GHz going with the internal wifi and it appears nobody else can either. I did put the 951ax adapter in a usb3 port and load the drivers. Wow. That did not work well. It was nothing like what I saw on my ZyXEL NBG6817. 22.03 for the Pi4B appears to not be ready for prime time. |
@morrownr RE: onboard 2.4Ghz. Yeah... I kinda bumped into that issue too, thanks for linking the thread as it was exactly what I was looking for at the time. The latest poster is right about Legacy not even working like in did in previous RCs. And no fix in sight. It's a shame these issues are occurring given the support Raspberry Pi & OpenWrt have in the community. |
Yes, it is. However, stuff happens. This stuff will be fixed. We have to remember that OpenWRT is designed for dedicated wireless routers and the Pi4B is not a wireless router, it is a general purpose computing device. We also have to remember that this edition of OpenWRT had some rather big changes. We are on the bleeding edge of the new OpenWRT distro. We are only the bleeding edge of the mt7921au chip and we are on the bleeding edge of the mt7921u driver. All problems should settle down over the next few months.
That is a good question. I don't have the answer. |
Eh, maybe I worded that poorly. No blame, just general disappointment. Making good things takes time. It's great that there's more than 1 person troubleshooting it. Maybe if the Alfa adapter is impacted it could put more eyes on obtaining a solution. |
I certainly was not expecting the Pi4B version of OpenWRT to be in this bad of shape. I don't see the mt7921u driver as the problem as it is working fine on my router. Something I have noticed when I stop by the OpenWRT forums is not much traffic by Pi users. I have to wonder if the Pi versions get much testing. I like to use my Pi4B as an AP but I use my own guide which uses hostapd. |
I tried running mt7921au on a ryzen system and on two routers (ipq40xx/armv7l and mt7621a/mips). All on OpenWrt with Linux 5.15. Those worked fine, however on my intel laptop I got some issues with AP mode. Yup, we are really on the bleeding edge. This will take some time to settle down... |
@ayyyuki1 @amisix
Agree. I was pondering the best way to make a little progress with the Pi4B since amisix is trying to test on a Pi4B. I have an idea. I'm throwing together a simply guide to compiling kernel v6.0 on standard 64 bit RasPiOS installation. I can see a couple of other things we could test as well. The reason for this is that the 5.15 kernel in the standard RasPioS distro does not have the mt7921u driver yet. Okay, yes, still bleeding edge but could help with what we are trying to do. |
$ uname -a You also need to upgrade the 3 firmware files. My Pi4B is running kernel 6.0. |
Please direct me to it when available and I will follow it. Thanks |
Building the 64 bit RasPiOS kernel on the Pi3, Pi3+, Pi4, 400, Zero 2 W, Note: Compiling the kernel on a RasPi can take a long time.
$ sudo apt install git bc bison flex libssl-dev make libncurses5-dev Note: libncurses5-dev is required for menuconfig (not used in this guide yet.).
Note: change "rpi-6.0.y" to the branch you want in the command below. $ git clone --depth=1 --branch rpi-6.0.y https://github.com/raspberrypi/linux Note: Omitting --depth=1 will download the entire repository, including the Refer to the original GitHub repository for information about the available branches. https://github.com/raspberrypi/linux
If you want to apply the Default Configuration: (I'll add options later.) Prepare the default configuration by running the following commands $ cd linux
Build and install the kernel, modules, and Device Tree blobs; this step can take a long time For the 64-bit kernel: $ make -j4 Image.gz modules dtbs If KERNEL was not set above, set it now: $ sudo cp arch/arm64/boot/Image.gz /boot/$KERNEL.img Reboot. Your Raspberry Pi should be running your freshly-compiled kernel! Let me know how it goes. |
After setting up the new flash and update of the 64 bit RasPiOS, I noticed Chromium running like honey on a cold winter day. The fix: Settings > System > Use hardware acceleration when available Turn it off! Oh, and the RasPiOS does need the 3 firmware files for the mt7921au updated. Remember that I have a checklist in the Main Menu. Cheers |
Heads up. New firmware files as of less than 24 hours ago: 525870 Sep 24 00:55 BT_RAM_CODE_MT7961_1_2_hdr.bin |
Status update: My Pi4B now shows the below wifi interface using the CF-951AX adapter. RasPiOS is updated to kernel 6.0. The hot new firmware has been installed. The mt7921u driver is working well.
What I am thinking about doing is working this until I have a tri-band wifi router or AP. Yes, 3 usb wifi adapters on the Pi4B. What are the issues we are likely to see:
This could be a cool project. Should I start a new issue dedicated to this project? |
got my CF-951AX, and put it to a x86 OpenWRT, and load newest firmware, and try to get to AP mode. 2.4 GHz band AP mode can bring up interface but client never see it, very strange
|
Hi @copyliu Strange is what we do around here. Try limiting both radios to WPA2 AES. Make sure the country code is set for both radios. It should not matter for 2.4 but will for 5. Are you using AC or AX? If AX, try AC for now and see if it helps. Do you have other wifi radios in the box? Did you have the adapter in a usb3 port when you booted the os the first time as a new burn? Luci is not 100% good with WiFi 6 yet and is a no-go with WiFi 6e so I am mostly only using ssh to change wireless setting instead of Luci. This will change with time but for now... |
I can see only 1 radio on my openWRT, and country code is set. |
Take a look at both log files after a reboot. Status > System log Are you seeing any ERRORs or WARNs or anything that looks wrong? I have no experience with OpenWRT on x86. only on ARM so I have no background of where bugs for that platform may be. |
from logread
it looks nothing wrong but client just drop connection |
I took at look at my log file using this same adapter and I don't see the following line:
Could it be a security related setting? |
I think I was misconfig something before, and now I can bring up AP with a separate bridge,
also try with debian testing
|
I'm unable to get either Comfast adapter to initialize (device is not active/wireless is not associated) in OpenWrt 22.03 in N, AC, or AX mode. It's plugged into a USB3 port.
I was able to progress past the first error (in AX mode) "daemon.err hostapd: Driver does not support configured HT capability [LDPC]" by adding option ldpc '0' to /etc/config/wireless... Only to come up with 3 more errors. Adding the below options bypassed those errors:
option ldpc '0'
option tx_stbc '0'
option rx_stbc '0'
option max_amsdu '0'
Once I got past those errors I receive this error:
Configured VHT capability [VHT_CAP_MAX_MPDU_LENGTH_MASK] exceeds max value supported by the driver (2 > 0)
And don't know how to proceed.
logread:
The text was updated successfully, but these errors were encountered: