[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On 09/04/2020 21:49, comrade meowski wrote:
Done.. I saw a line stating the module was 'ACTIVE' prior to uninstall.. is that OK?On 09/04/2020 16:36, Julian Hall wrote: <snip>Damn, we may well have been wasting time because we didn't research well enough to start with... You'd think I'd know better than that by now but never mind.Ok, proper solution #take2: Let's dump out the old driver entirely, it's not working: sudo dkms remove -m 8812au -v 4.2.2 --all
Following more up to date information from this year and inline with my own advice about using injection-capable hacked up drivers instead let's crib from here:https://askubuntu.com/questions/1042310/install-driver-rtl8814au-on-ubuntu-18-04 https://forum.mxlinux.org/viewtopic.php?f=107&t=55348&sid=4b730bff9198f5203bcde57b11d90424&start=10#p552025Presuming you're working in /home/Julian/SRC remove or delete the old rtl8812au directory as it will clash with the new one we'll download:cd ~/SRC mv rtl8812au rtl8812au-NOPE Clone the new repo from aircrack-ng: git clone https://github.com/aircrack-ng/rtl8812au.git cd rtl8812au sudo apt install bc build-essentials -y #just prereq installs Use their handy dkms setup script: sudo ./dkms-install.sh * dkms statusOn my system (I've grepped just the relevant results, your kernel will be different) this looks like:comrade@drone:~/SRC/rtl8812au$ dkms status | grep coldwar nvidia, 440.82, 5.6.0-pf2-coldwar+, x86_64: installed rtl8812au, 5.6.4.2, 5.6.0-pf2-coldwar+, x86_64: installed zenpower, 0.1.10, 5.6.0-pf2-coldwar+, x86_64: installed zfs, 0.8.3, 5.6.0-pf2-coldwar+, x86_64: installed
base) julian@CERCE:~/rtl8812au$ dkms status nvidia, 435.21, 4.15.0-96-generic, x86_64: installed nvidia, 435.21, 5.3.0-45-generic, x86_64: installed nvidia, 435.21, 5.3.0-46-generic, x86_64: installed rtl8812au, 5.6.4.2, 5.3.0-46-generic, x86_64: installed
Pretty much the same as before, but note the much higher revision number for the driver (5.6.4.2 vs 4.2.2). Now all of this worked perfectly for me but please bear in mind I don't have the actual wifi unit and am working blind so who knows how it will go with the real one. Let's find out I guess?Finally, I'd just leave it in place and reboot the whole box to see what happens on login. If you don't have an available wifi network device pop up as usual then we're back to examining what went wrong and examining the options.Fingers crossed, this one looks more promising.
*rebooting, saving email*
Good luck chief.
This sent by WIRELESS Internet connection!! Even before I rebooted I plugged it in and a blue light started flashing which has never happened before! Network connections showed my WiFi networks (I also have a Guest network), so I rebooted, popped in my password, turned off the Ethernet and Bob's your father's brother! Technically my granddad but I digress!
You sir are a genius, and a very very patient one at that! Thank you ever so much, I really needed a win in /something/ of late... this is brilliant! :)
Kind regards, Julian -- “The great tragedy of Science — the slaying of a beautiful hypothesis by an ugly fact.” ― Thomas Henry Huxley -- The Mailing List for the Devon & Cornwall LUG https://mailman.dcglug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq