Package Details: rtl8814au-dkms-git 4.3.21.r34.ga0c4479-2

Git Clone URL: https://aur.archlinux.org/rtl8814au-dkms-git.git (read-only)
Package Base: rtl8814au-dkms-git
Description: RTL8814AU and RTL8813AU chipset driver with firmware v4.3.21
Upstream URL: https://github.com/zebulon2/rtl8814au
Licenses: GPL2
Conflicts: rtl8814au
Submitter: zebulon
Maintainer: zebulon (erkexzcx)
Last Packager: erkexzcx
Votes: 15
Popularity: 0.336172
First Submitted: 2017-09-18 20:21
Last Updated: 2018-08-19 22:11

Dependencies (3)

Required by (0)

Sources (3)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

itsmattson commented on 2019-01-29 03:56

Thanks @zebulon! I learned something from that so I uninstalled it and reinstalled it your way via downloading snapshot, untarring, and using makepkg -i and r40 came down as you suggested which is great! I thought I had to go via github to get the latest because package details at the top of page says "rtl8814au-dkms-git 4.3.21.r34.ga0c4479-2". Apologies for the misunderstanding - This has certainly simplified AUR package updates for me :)

zebulon commented on 2019-01-28 15:16

@itsmattson: good to hear. Regarding the best practice: I think you confused the source for the driver and the source for the PKGBUILD. You do not need to git clone https://github.com/zebulon2/rtl8814au and make a package out of it, but only of the PKGBUILD snapshot https://aur.archlinux.org/cgit/aur.git/snapshot/rtl8814au-dkms-git.tar.gz which you untar somewhere and then run makepkg -i inside (as explained in the AUR wiki page). makepkg will handle the download of the source from github (the latest revision by default). The thing is, the PKGBUILD is not updated each time the Github driver source is (this is normal and an Arch guidance). Hence, if you wish to use the latest version of the driver, clean up your PKGBUILD snapshot folder (or reexpand it again) and run makepkg -i from time to time (or each time you see the Github driver has been updated). Hope this helps.

itsmattson commented on 2019-01-28 13:20

Hey @zebulon, on latest git pull a moment ago I got "rtl8814au-dkms-git-4.3.21.r40.ge217689-1" and it installed perfectly (the one I got the error with this afternoon was r35). Thank you! Any tips on how to know if latest kernel is supported before I do a system upgrade next time?

itsmattson commented on 2019-01-28 13:10

Thanks @zebulon!

I think I did it right so maybe you can tell me where I went wrong? Maybe I just tried to upgrade (git pull) too soon (before your merge) - Is that what you mean?

This is the order I did things: Updated system (sudo pacman -Syu), noticed Wi-Fi no longer working so pulled latest changes in cloned repo (git pull), remade the package (makepkg -Acs), and finally reinstalled it to Pacman (sudo pacman -U <package>.pkg.tar.xz). This was second time I got the error (first during pacman -Syu) so decided to come here and ask for help :p

Can I bother you to advise what best approach would be in future when looking to upgrade? Thanks!

zebulon commented on 2019-01-28 08:41

@itsmattson: I just read again your message. Indeed, you have the r35 version of the repository, that is before I merged the support for kernel 4.20 (see the source history at https://github.com/zebulon2/rtl8814au/commits/master). Note that AUR packages do not update automatically with pacman, and that secondly a -git package needs to be rerun some time to time to get the latest git sources, since the PKGBUILD is not necessarily changed, while the original sources are. I invite you to read the Wiki for more info about AUR, starting at https://wiki.archlinux.org/index.php/Arch_User_Repository#Installing_packages. Once you have well understood the concept, then you can use a pacman wrapper that helps installing AUR packages automatically, such as pikaur, but only after you have understood the "manual" way! ;)

zebulon commented on 2019-01-28 07:45

@itsmattson: normally support for 4.20 has been added. Looks it does not compile with 4.20.4, but I can only diagnose the problem if you give me the content of /var/lib/dkms/rtl8814au/4.3.21.r35.g7dde5bd/build/make.log. Can you please avoid pasting a long text here, and instead send a pastebin (or equivalent) link?

itsmattson commented on 2019-01-28 04:43

Made the decision to upgrade system via pacman -Syu, knowing I'd probably have issues with this package but did it anyway... but came across an issue I don't think I can fix myself. Part of the upgrade seems to have been Arch itself to 4.20.4. Any ideas?

(1/2) Install DKMS modules ==> dkms install rtl8814au/4.3.21.r35.g7dde5bd -k 4.20.4-arch1-1-ARCH Error! Bad return status for module build on kernel: 4.20.4-arch1-1-ARCH (x86_64) Consult /var/lib/dkms/rtl8814au/4.3.21.r35.g7dde5bd/build/make.log for more information. (2/2) Arming ConditionNeedsUpdate...

Thanks in advance!

zebulon commented on 2019-01-24 10:01

@SeeLook: you're welcome. When you say "before it just worked out of a box" you are probably speaking about another adapter, because the RTL88xxau USB adapters have never worked out of the box (i.e. the Linux kernel does not come with the drivers). I have another USB adapter (EDIMAX EW-7318USg) which works without external driver, but this is an 802.11n (2.4GHz only) adapter with chipset Ralink RT2571W, which uses the rt73usb module, available in Linux kernel source.

SeeLook commented on 2019-01-23 19:48

Thanks for clues. Usually it is not often thing to change wifi adapter and with other ones before it just worked out of a box. So I will read that closely to fix my issues.

Also thank you for developing and packing it for Arch.

zebulon commented on 2019-01-23 12:49

@SeeLook: well, the number of devices is extremely high, and it is impossible to list them all or to keep the list complete. There are other resources for this, such as https://wikidevi.com. What is really important is the chipset (8812, 8814, 8821, etc.) A lot of people mistakenly use the wrong driver due to the fact they do not identify correctly their chipset. The Arch wiki section on rtl88xxau on the WiFi page is very helpful in that sense. Finally, a list of hardware IDs can be found in the driver code in file /os_dep/linux/usb_intf.c.