-
Notifications
You must be signed in to change notification settings - Fork 73
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
Cudy WU1300S (rtl8822bu) Problems #31
Comments
Tried disabling power saving using sudo ./edit-options.sh but after a reboot it has not had any effect on the poor performance |
Near the end of the README.md (the main screen) are two sections that might be of interest. One is about recommended router settings and the other is info regard USB. Given those a look and also make sure you delete any old networks connections:
See if any of that helps. |
I can use both 5GHz and 2.4GHz connections fine and at full speed when using other devices so I think my router settings are okay. My issue with swapping USB ports seems to be because of putting in my front ports instead of the rear, though. I cleared all my current connections and rebooted then re-added the 2.4GHz connection but my issue with poor speeds and being unable to connect to my router's 5GHz connection still persist. Both connections have different names, too. |
is what |
Set the log level to 4 and reboot. Use the system for about 5 minutes and then run save-log.sh. The log will be called rtw.log. Post the contents here. Let's see if we can see anything in the log. Post the contents of 88x2bu.conf...not the one in the driver directory but the one that is operating on the driver. iwconfig is telling us that you don't have an 802.11ac connection. That is interesting. |
Here is config
Here is log at level 4 whilst being connected to 2.4ghz connection |
Good job providing information. Here are some thoughts:
options 88x2bu rtw_drv_log_level=4 rtw_led_ctrl=1 Yes, delete the last 3 items and then do a cold boot. See what happens.
For what it is worth: I have tested this driver with kernel 5.4 and with kernel 5.8. With kernel 5.8, the testing was done on Ubuntu 20.10, not Mint 20. Ubuntu 20.10 was tested extensively with kernel 5.8 and that is the stable kernel that it uses. Mint 20.1 is due out soon and it will still use kernel 5.4. I'd recommending sticking with the kernel that the Mint developers use. Question: This adapter is USB 3 capable. How are you connecting to your computer? Directly or with a cable? If you are using a cable, is the cable USB 3 capable? Is the slot you are hooking it into a USB 3 port? |
I set my configuration options to what you listed and haven't experienced any change. Reverting to kernel 5.4.0-58 still doesn't anything, either. I'm using a USB 3.0 port at the rear of my computer for the wifi adapter, it's connected directly. |
Here is a new log with the aforementioned changes, after a coldboot and running for 5 mins: |
There is no doubt that there is a problem. You have selected the right driver based on the device ID. The driver is installing. I am currently checking your log vs mine as I am using the same driver on this system I am typing on right now. I am also using Linux Mint 20. I am now asking myself, what would I do if I faced the same situation. The answer is that I would immediately dive into the router... remember the part where I recommended that you look at the section in the README that talks about router settings? I remember you saying something like "my other things work with the router therefore it can't be the router." Okay, I get that what you said seems to make sense... the problem is that it isn't true. I've been using Linux for about 25 years now. Please humor me and use my list of recommended routers settings so we can eliminate that as a possible problem. I'm here if you need to ask questions. |
I cycled through all of your recommended router settings, and by doing so I was able to get my 5GHz connection working and at full-speed too. Apologies for not doing this sooner. I still have the same problems with my 2.4GHz connection though, even after cycling through all of the recommended settings the speed is still incredibly poor and I struggle to load websites |
Okay, it is good to make a little progress. No need to apologize, we all get locked in once in a while. The next thing I would do at this point is load up a "wifi analyzer" app on my smart phone to take a look at congestion on the 2.4g band. Figure out which of the channels 1, 6 and 11 is least congested and set that as a fixed channel in the router. Reboot the router. Recommend you read this article: https://metis.fi/en/2017/10/txpower/ I had noticed your signal was very strong...maybe too strong. Also, recommend you add "rtw_switch_usb_mode=1" to your 88x2bu.conf and reboot. Make sure that your adapter is in a USB 3 port. Let's see what happens. |
Thank you for sharing the article regarding transmit power, but even after decreasing the power transmitted it didn't help much with the connection. It's definitely something I'll keep on a lower setting though, now that I've read more about it. I also didn't experience any change after editing the configuration and changing the USB mode. I think I'll just close this issue and stick with using the 5GHz connection. I doubt I will end up at all needing the 2.4GHz connection with this adapter and it seems almost certain that this is an issue with my setup, not an issue with the driver. If for whatever reason someone else has this problem, this issue could always just be referenced. I hope I did not take up too much of your time, thank you so much for all of your help. |
Hey, I've tried using this driver with my Customer WU1300S and haven't been able to get it work in a proper manner
I'm on Linux Mint 20 with kernel 5.8.0-33 generic. The ID in lsusb is just 0bda:b812
I tried also using the driver listed on Cudy's website but I am having the same issues with that driver too, so I'm not certain this is an issue with this driver or if it's something related to my machine causing this. I did use a different wifi adapted previously and that worked fine, though (with in-kernel drivers). Any help would be greatly appreciated.
The text was updated successfully, but these errors were encountered: