Closed morrownr closed 3 months ago
hi, I'm here.
Hi, I'm here.
Hi @morrownr, pardon if I sound naive but can we do something so that RTL8812AU can also support VIF. It really plays a crucial role after all, although I am not pretty sure about the firmware support but in any-case the firmware gives a green flag we might be able to add some changes to drivers later on to accomplish the VIF support. Also if you see any positive scope from your expertise, I will be willing to help with your guidelines. And also I'm not forgetting our first priority is to successfully test for the updated version.
I just installed the new driver but it doesn't seem to detect the Wi-Fi adapter.
[franco@pc ~]$ cd 8812au-20210820/
[franco@pc 8812au-20210820]$ ll
total 212K
drwxr-xr-x 9 franco franco 4,0K ene 3 16:03 .
drwx------ 24 franco franco 4,0K ene 3 16:25 ..
-rw-r--r-- 1 franco franco 4,0K ene 3 16:03 8812au.conf
drwxr-xr-x 7 franco franco 4,0K ene 3 16:03 core
-rw-r--r-- 1 franco franco 5 ene 3 16:03 default-editor.txt
-rw-r--r-- 1 franco franco 202 ene 3 16:03 dkms.conf
-rwxr-xr-x 1 franco franco 654 ene 3 16:03 dkms-make.sh
drwxr-xr-x 2 franco franco 4,0K ene 3 16:03 docs
-rwxr-xr-x 1 franco franco 1,9K ene 3 16:03 edit-options.sh
-rw-r--r-- 1 franco franco 7,1K ene 3 16:03 FAQ.md
drwxr-xr-x 8 franco franco 4,0K ene 3 16:03 .git
drwxr-xr-x 7 franco franco 4,0K ene 3 16:03 hal
drwxr-xr-x 5 franco franco 12K ene 3 16:03 include
-rwxr-xr-x 1 franco franco 14K ene 3 16:03 install-driver.sh
-rw-r--r-- 1 franco franco 110 ene 3 16:03 Kconfig
-rw-r--r-- 1 franco franco 656 ene 3 16:03 LICENSE
-rw-r--r-- 1 franco franco 75K ene 3 16:03 Makefile
drwxr-xr-x 3 franco franco 4,0K ene 3 16:03 os_dep
drwxr-xr-x 2 franco franco 4,0K ene 3 16:03 platform
-rw-r--r-- 1 franco franco 22K ene 3 16:03 README.md
-rwxr-xr-x 1 franco franco 4,5K ene 3 16:03 remove-driver.sh
-rwxr-xr-x 1 franco franco 655 ene 3 16:03 save-log.sh
-rw-r--r-- 1 franco franco 1,4K ene 3 16:03 supported-device-IDs
[franco@pc 8812au-20210820]$ sudo ./install-driver.sh
[sudo] contraseña para franco:
: ---------------------------
: install-driver.sh v20231227
: x86_64 (kernel architecture)
: x86_64 (architecture to send to gcc)
: 4/4 (in-use/total processing units)
: 8020452 (total system memory)
: 6.6.9-arch1-1 (kernel version)
: gcc (version of gcc used to compile the kernel)
: gcc (GCC) 13.2.1 20230801
: dkms-3.0.12
: mokutil not installed
: ---------------------------
Checking for previously installed drivers...
Finished checking for and removing previously installed drivers.
: ---------------------------
Starting installation.
Installing 8812au.conf to /etc/modprobe.d
The dkms installation routines are in use.
Copying source files to /usr/src/rtl8812au-5.13.6
Creating symlink /var/lib/dkms/rtl8812au/5.13.6/source -> /usr/src/rtl8812au-5.13.6
The driver was added to dkms successfully.
: ---------------------------
Sign command: /usr/lib/modules/6.6.9-arch1-1/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Certificate or key are missing, generating self signed certificate for MOK...
Building module:
Cleaning build area...
kernelver=6.6.9-arch1-1 ./dkms-make.sh.......................
Signing module /var/lib/dkms/rtl8812au/5.13.6/build/8812au.ko
Cleaning build area...
Compile time: 195.82 seconds
The driver was built by dkms successfully.
: ---------------------------
8812au.ko.zst:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /usr/lib/modules/6.6.9-arch1-1/updates/dkms/
depmod....
The driver was installed by dkms successfully.
: ---------------------------
Info: Update this driver with the following commands as needed:
$ git pull
$ sudo sh install-driver.sh
Note: Updates to this driver SHOULD be performed before distro
upgrades such as Ubuntu 23.10 to 24.04.
Note: Updates can be performed as often as you like. It is
recommended to update at least every 2 months.
Note: Work on this driver, like the Linux kernel, is continuous.
Enjoy!
Do you want to edit the driver options file now? (recommended) [Y/n]
Do you want to apply the new options by rebooting now? (recommended) [Y/n] y
[franco@pc ~]$ iw list
[franco@pc ~]$ uname -a
Linux pc 6.6.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Tue, 02 Jan 2024 02:28:28 +0000 x86_64 GNU/Linux
[franco@pc ~]$ lsusb -t
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 003: Dev 002, If 0, Class=Vendor Specific Class, Driver=[none], 480M
|__ Port 007: Dev 004, If 0, Class=Vendor Specific Class, Driver=[none], 480M
|__ Port 008: Dev 005, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 008: Dev 005, If 1, Class=Wireless, Driver=btusb, 12M
|__ Port 011: Dev 006, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 011: Dev 006, If 1, Class=Human Interface Device, Driver=usbhid, 12M
/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/6p, 5000M
@castillofrancodamian
Can I get you to start a new issue with an appropriate title for the problem you are reporting above? That should help us stay more organized.
@0-xeno-0
No problem with your VIF question being here but it may be tomorrow before I have time to address it.
All: Let's try to keep this issue for check-ins and general discussion. Specific bugs need their own Issue.
FYI: There are 4 of us here so far but I expect others to come onboard as time passes.
Thanks,
@morrownr
Hi, I'm here.
Hi @morrownr, I have got a few findings which needs to be shared, should I post it here as a comment or in some other format, waiting for your guidelines.
Brief Summary:
Modules are loaded correctly and the device is been detected correctly.
@0-xeno-0
Open a new issue with a title something like `I have a few findings".
Thanks,
@morrownr
@castillofrancodamian
I just installed the new driver but it doesn't seem to detect the Wi-Fi adapter.
I have updated the VID/PID code in the driver now so try the following:
$ git pull $ sudo sh install-driver.sh
Your adapter may have had one of the numerous VID/PID's that have to be added.
@morrownr
@0-xeno-0
Open a new issue with a title something like `I have a few findings".
Thanks,
@morrownr
Hi @morrownr , I have added my findings as per best of my knowledge, waiting for your review and further guidance on what I could have looked for or what my next approach should be towards. Also I have logs saved from the script provided.
Hi there :)
@michelwi
Welcome. The biggest needs are:
Reading and making suggestions to for the docs: README.md, FAQ.md and 8812au.conf. If anything is not clear, please create an issue. I think it is good to look at the docs with eye toward reducing the size of the docs so if you see anything that is redundant or can be said in fewer words, please speak up.
Test the installation and removal. The following scripts need to be tested a lot: install-driver.sh, remove-driver.sh and edit-options.sh. Test on as many different distros and platforms as you can. Create an issue if you see problems. You can run install-driver.sh 30 times in a row if you want as that script detects an already installed driver and removes it so removing a previously installed driver is not necessary.
Testing the manual installation and removal needs to be done as well. Follow the instructions in README.md.
Test managed (client) mode, AP mode and P2P mode with as many systems as you can and report problems with new issues.
With my latest merge, I cleaned up something things in the docs and scripts. I also turned monitor mode off for now. We can discuss whether to turn it back on at some point in the future.
Test with APs/routers that are using WPA2-AES, WPA2/WPA3 mixed mode and WPA3. All show work fine but testing is needed.
You can follow what I am doing by reading Issue number 1 or by reading what I have merged,
Everyone is welcome to submit PRs. There are guides to creating PRs if you do not yet know how.
Let know if there are questions.
@morrownr
Will there be / should we create a thread where we post things that we successfully tested and which worked fine? (e.g. I used the install script today. It removed the old version, finished successfully and managed mode so far works fine.)
should we create a thread where we post things that we successfully tested and which worked fine?
Good idea. I created a section just for these types of reports in message 1 of Issue 1. Scroll to the bottom and check it out. You did not mention your distro and version nor the hardware so if you can provide that I will add it.
We do need successful reports so that we can see what is working which should give us an idea of what is not being tested. I might move this good reports section to message 2 in Issue 1 but let's see how things work.
I'm sure we need testing of AP mode and P2P modes. I know I will test AP mode but more testing on different setups is needed. We really do need P2P testing.
There is on one that I currently do not list but it is in the driver according to Realtek: IBSS. I used to list it based on what Realtek said but I have never had a user say anything about it and I removed it from README based on it not being tested, If someone wants to test IBSS, that would be great. If it tests good, I will add it back to the README.
I used the install script today. It removed the old version, finished successfully and managed mode so far works fine
I have been testing installation and managed mode myself and I am not seeing any problems so far so I will likely move my testing to AP mode soon. Others need to continue testing and reporting on their setups.
FYI: This driver is the best out-of-kernel driver I have ever seen from Realtek. That is not to say that there are things to fix or make better. I hope to fix beamforming. I was able to fix it in the 88x2bu driver after much research and testing so we have some deep dives that we need to do as we get to the point of working on certain issues.
@morrownr
Hi! I used the old public 8812au driver. This one is a drop-in replacement and it works flawlessly (Raspberry Pi, Raspbian 10, hostapd).
I can't seem to get AP mode (5GHz 80MHz channel) working on any other channel than 36.
I can't seem to get AP mode (5GHz 80MHz channel) working on any other channel than 36.
Post a new issue. Include info:
I may need to update the docs.
Welcome.
@morrownr
I have added what I think is good support for kernel 6.8. Please test and report with kernel 6.8 as able.
@morrownr
Hi there. I am checking in. I will be testing tonight.
What I forgot to add - speed works well enough, 250MBit/s (one-way) with iperf3. My pings are also normal, will post an image in the other issue.
@dsvf
speed works well enough, 250MBit/s (one-way) with iperf3.
I've been beating up managed mode myself and I'm not seeing any problems so far. iperf3 is showing 450-500 Mbps but the channel has very low congestion. Is USB3 mode working?
$ lsusb -5
I'm also seeing WPA/AES, mixed and WPA3 working well. How about you?
I'm ruuning my adapter to do most of my daily work to see if I see the latency.dropping out problem. I'm not seeing it so far but have another couple of systems to test on when I have time. Hopefully everyone can test and keep an eye out for this.
@morrownr
I just posted more info and two ping tests on the other issue. lsusb -5
returns an error for me. There was no speed difference between the USB2 and USB3 modes, but I'm satisfied with 250MBits (wouldn't say no to more). I'm using it as a WPA2 access point.
I'll open ann issue concerning other channels once I've done some more testing, since I'm not sure if my AP is the problem or my devices, and if I've configured all region stuff correctly.
[...]Is USB3 mode working?
It is not, the stick runs at 480Mbps
@dsvf
lsusb -5 returns an error for me.
My eyes are not that good anymore...
$ lsusb -t
It is not, the stick runs at 480Mbps
Run the following in the driver folder and paste the contents of the options
line:
$ sudo ./edit-options.sh
It is good to see you will be testing AP mode.
@morrownr
options 8812au rtw_drv_log_level=1 rtw_vht_enable=2 rtw_switch_usb_mode=1 rtw_dfs_region_domain=1 rtw_country_code=US
The USB3 port works fine with some random USB3 stick. I'll see if I can check it on my other (x86) laptop
Here 👋
👋
@Dan-Milne
Good to see you here. Please read Issue 1 to keep up with activity and status. Also, it might help if you take notes while reading the docs and installing so as to help with recommendations. I need the docs to be very clear and in English that translates very well to other languages.
Currently we need testing on ad-hoc mode and both P2P modes so I encourage you and the others to give both as try as you have time.
@morrownr
@morrownr But how do we test those modes?
@morrownr
Will do, if you do need help with the docs I am more than happy to help and will continue to test this version. I will also update the tested kernel versions for the Arch distro once 6.8 releases etc. (e.g , commit 7f5185d). See you around :)
@castillofrancodamian
But how do we test those modes?
I am going to be changing my adapter into a setup where I can test P2S-client tomorrow. I have a hp Printer that has WiFi Direct P2P-GO support so that is where I am going to start. To test P2P-GO, I'll probably have to do some googling.
IBSS (ad-hoc) ? Never used it here but some people do at times but I think it is rare. I noticed that the mt7921u driver does not even support it and I have seen no calls for it in that driver. I would entertain the idea of shutting it down and removing it from the README as a supported mode. Thoughts?
@morrownr
@Dan-Milne
if you do need help with the docs I am more than happy to help
Yes, please do so. The docs for the driver are in 3 files: README.md, FAQ.md and 8812au.conf. Take your time and take notes so we discuss the things you bring up. I'll create an Issue for the docs so we can discuss things there.
I will also update the tested kernel versions for the Arch distro once 6.8 releases etc.
Sounds good. I saw the pr that you submitted. Looks good. I am going to be making updates to the doc files so please git pull
often.
@morrownr
With the merge today I am declaring RC1.
The only issue that is unresolved in my mind is the issue of whether to list IBSS as supported in the README. I will plan on deleting the mention of it in the docs unless someone steps up and tests the function of it very soon.
The only open issue is the one about Interruptions continue every few seconds
. I have tested and tested and a few others have taken a look as well. There could be a problem in specific situations but until we have a way to duplicate the issue reliably, it is hard to determine the cause. What I have seen appears to be normal operation. We can leave this issue open and hope that additional information is added once the repo is open to the public.
The work on this driver has progressed faster than I have anticipated so I am looking at moving the proposed release date up to March 31. Please continue to test and report.
@morrownr
The only issue that is unresolved in my mind is the issue of whether to list IBSS as supported in the README. I will plan on deleting the mention of it in the docs unless someone steps up and tests the function of it very soon.
Think I've got IBSS working. If you need me to test anything specifically to make sure let me know.
Hi @Dan-Milne
Think I've got IBSS working.
That is great. Once you are happy with the results, tell me to add it back to the README and I will.
If you need me to test anything specifically to make sure let me know.
I've never used IBSS so I would not know what to ask for. Maybe someone else can help. What I think might be handy is if we could add IBSS setup instructions to the README. Are you up for doing that?
Hi @morrownr,
Sorry for the late reply. I'll try and get a setup guide drafted up by the end of the week and submit a PR.
Hi @Dan-Milne
That is great. I'm still looking at going public by the end of the month that depends on whether anyone comes up with a problem. Having an IBSS guide would be great. Since a lot of people do not know what it is, can the guide start with a short blurb and what it is and what it can be used for.
@morrownr
@Dan-Milne
For an example, look in the docs folder for a guide for concurrent mode. You can put the IBSS guide in the docs folder also and we can add a pointer to it in the README.
I am going to change this repo to public today as I think we are to the point that it is time. I appreciate the testing and input from each of you.
@morrownr
Closing this issue...
I would appreciate it if you would post a message here so that I know you successfully made it to the repo.