mirror of
https://github.com/morrownr/8812au-20210820.git
synced 2026-10-14 21:38:30 +00:00
[GH-ISSUE #45] [Bug]: #40
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Jussi73 on GitHub (Jan 2, 2025).
Original GitHub issue: https://github.com/morrownr/8812au-20210820/issues/45
Checklist
Is Secure Boot enabled?
No
uname
Linux KodiBox 6.6.62+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.62-1+rpt1 (2024-11-25) aarch64 GNU/Linux
lsusb
rfkill
0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: phy1: Wireless LAN Soft blocked: no Hard blocked: no
dkms
iw
git status
install-driver.sh
What happened?
I have installed these drivers on a fresh Pi4 (64bit). All updates are performed according to instructions here. Compile and install ran without errors.
The AC56 device shows up if I run LSUSB, but it does not show up under WLAN devices. I have the onboard Pi4 wifi, and a crappy TPlink dongle in the Pi now and they both show up - see LSUSB output above.
How do I get it to show up as a WLAN device that I can actually use?
Thanks!
@morrownr commented on GitHub (Jan 2, 2025):
Hi @Jussi73
Install the correct driver. You have installed the rtl8821au driver. You need the rtl8812au driver:
https://github.com/morrownr/8812au-20210820
@Jussi73 commented on GitHub (Jan 3, 2025):
Ahh, thank you - sorry for asking a stupid question - had not noticed it was the wrong driver, but makes sense. I will give this a go now and report back.
@Jussi73 commented on GitHub (Jan 3, 2025):
Uninstalled RTL8821au driver using the uninstall script. Ran the process again as outlined above. Adapter is up and running good now. Thanks :-)
I dunno how I got 8821au installed. This was a fresh Pi, and I could have sworn that I ran everything as outlined in the readme, but apparently something went haywire there, but that was a pretty dumb mistake....
Anyway, thank you for answering and thank you for your work. Much appreciated - this solves a network issue I had in the simplest possible way with hardware I had laying around.
Will close this thread - obviously not a bug.
@morrownr commented on GitHub (Jan 3, 2025):
FYI: A new in-kernel driver for this chip was added with kernel 6.13. I'd say once are using kernel 6.14 or later, you won't need to find a driver anymore.