Since last kernel update, Wifi adapter stopped working.

Wifi USB adapter: Wavlink AC1300 Dual Band USB Adapter
Model # WL-WN688U8 (Rev.A)

I am using the proposed additional open-source driver:

Linux Kernel version and Ubuntu version:

~$ uname -a  
Linux PC 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

USB Wifi adapter is recognized as RTL8812AU:

~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
(...)
Bus 001 Device 007: ID 0bda:8812 Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac WLAN Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Albeit, there is no wireless interface:

~$ lshw -C network
WARNING: you should run this program as super-user.
  *-network                 
       description: Ethernet interface
       product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: enp3s0
       version: 0c
       serial: 1c:1b:0d:df:16:70
       size: 10Mbit/s
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=half firmware=rtl8168g-2_0.0.1 02/06/13 latency=0 link=no multicast=yes port=MII speed=10Mbit/s
       resources: irq:16 ioport:d000(size=256) memory:f7c00000-f7c00fff memory:f0000000-f0003fff
WARNING: output may be incomplete or inaccurate, you should run this program as super-user.

Seems like dkms module is not installed:

~$ dkms status
rtl8812au, 4.3.8.12175.20140902+dfsg: added

Trying to reinstall:

~$ sudo dkms build -m rtl8812au -v 4.3.8.12175.20140902+dfsg
[sudo] password for user:  

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
'make' all......(bad exit status: 2)
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/rtl8812au-dkms.0.crash'
Error! Bad return status for module build on kernel: 5.0.0-23-generic (x86_64)
Consult /var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/make.log for more information.

Error output in make.log:

/var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/os_dep/linux/os_intfs.c:779:22: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
  .ndo_select_queue = rtw_select_queue,
                      ^~~~~~~~~~~~~~~~
/var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/os_dep/linux/os_intfs.c:779:22: note: (near initialization for ‘rtw_netdev_ops.ndo_select_queue’)
cc1: some warnings being treated as errors
scripts/Makefile.build:284: recipe for target '/var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/os_dep/linux/os_intfs.o' failed
make[2]: *** [/var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/os_dep/linux/os_intfs.o] Error 1
Makefile:1606: recipe for target '_module_/var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build' failed
make[1]: *** [_module_/var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-5.0.0-23-generic'
Makefile:1457: recipe for target 'modules' failed
make: *** [modules] Error 2

Any help welcome!

Problem

I would like to share an Ethernet connection with two other Network Interfaces. So one source, and two shared connections.

Background

Here is a screencap of my Advanced Network Configuration nm-connection-editor:

The InternetSource is on device enp0s31f6, a ethernet NIC.

The SharedInternet, which provides for my subnet, is on device enx000dad2c7da0, a USB NIC.

And the Wifi hotspot is on device wlp3s0

Attempts to solve the problem

I have been able to share the internet with each of these individually, but when I try to have them share the internet source at the same time, one will break.

Here is my USB NIC setting. it works fine:

But my wifi hotspot only works when I disable the USB NIC and stop sharing with my subnet. Here are those settings below:

Question

Is there a way I can share my Ubuntu 19.04's internet with two different interfaces at the same time?

In previous version of Ubuntu I had a firewall rule to block all internet access for my child's account. I just upgraded to 19.10 and the system has changed such that my old method doesn't work anymore. My previous method was to add the following line to /etc/network/interfaces

pre-up iptables -A OUTPUT -p tcp -m owner --uid-owner 1001 -j DROP

In 19.10 it looks like /etc/network/interfaces does not exist. I discovered this guide and have tried to implement the solution using /etc/network/if-pre-up.d but am still having trouble. I've created a file called /etc/iptables.userblock.rules using iptables-save that looks like this:

*filter
:INPUT ACCEPT [11:831]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [18:2303]
-A OUTPUT -m owner --uid-owner 1001 -j DROP
COMMIT

and I've created a file called /etc/network/if-pre-up.d/iptablesload that looks like this:

#!/bin/sh
iptables-restore < /etc/iptables.userblock.rules
exit 0

If I run sudo /etc/network/if-pre-up.d/iptablesload after I log in the rules apply just fine, but it appears the script is not being run upon the network interface being loaded at boot, which is what I assume is supposed to happen. I've ensured permissions are 755. Am I missing something?

Infrastructure : Microsoft Azure OS : Ubuntu 18.04

Issue : We have assigned 2 NIC card (same subnet). We are able to SSH with primary IP (20.71.0.21) address but unable to connect with secondary address (20.71.0.22). This is working on Ubuntu 16.04. I would like to set the route.

> :~# ip r l  
> default via 10.171.0.1 dev eth0 proto dhcp src 20.71.0.21
> metric 100
> 20.71.0.0/24 dev eth0 proto kernel scope link src 20.71.0.21
> 20.71.0.0/24 dev eth1 proto kernel scope link src 20.71.0.22
> 168.63.129.16 via 20.71.0.1 dev eth0 proto dhcp src 20.71.0.21 metric 100
> 169.254.169.254 via 20.71.0.1 dev eth0 proto dhcp src 20.71.0.21 metric 100

> :~# route -n
> Kernel IP routing table Destination    Gateway        
> Genmask         Flags Metric Ref    Use Iface
> 0.0.0.0         20.71.0.1       0.0.0.0         UG    100    0        0 eth0
> 20.71.0.0       0.0.0.0         255.255.255.0   U     0      0        0 eth0
> 20.71.0.0       0.0.0.0         255.255.255.0   U     0      0        0 eth1
> 168.63.129.16   20.71.0.1       255.255.255.255 UGH   100    0        0 eth0
> 169.254.169.254 20.71.0.1       255.255.255.255 UGH   100    0        0 eth0

:~# cat /etc/netplan/50-cloud-init.yaml

ethernets:
    eth0:
        dhcp4: true
        dhcp4-overrides:
            route-metric: 100
        dhcp6: false
        match:
            macaddress: 00:0d:3a:ab:xx:xx
        set-name: eth0
    eth1:
        dhcp4: true
        dhcp4-overrides:
            route-metric: 200
        dhcp6: false
        match:
            macaddress: 00:0d:3a:xx:xx:xx
        set-name: eth1
version: 2

> :~# cat /etc/netplan/60-static.yaml network:
>     version: 2
>     ethernets:
>         eth0:
>             addresses:
>                 - 20.71.0.21/24
>         eth1:
>             addresses:
>                 - 20.71.0.22/24

How can we resolve this issue?

I read https://help.ubuntu.com/community/VNC/Servers to configure vino server on my ubuntu 16.04.LTS desktop.
Using other vnc servers, I used to connect to 129.254.xxx.yyy:1 (when the vnc session is 1. I can set the port).
But with this vino server, from my vnc client on my windows10 machine, what am I supposed to connect to? how do I know the port number?
I tried vnc to 129.254.xxx.yyy:1 but didn't work.
picture below is the response seen from the client when I tried to connect to 129.254.xxx.yyy:1 but failed.
My setting on my ubuntu 16.04 looks like this :

and my response at the client side(Real vnc client, on windows 10) when I tried 129.254.xxx.yyy:0 is like this

and the message I saw when I tried 129.254.xxx.yyy:1 is like this

and the message seen at the server side (for the two incidents) is like this

What should I change at the settings?

ADD :
After posting this question, I read http://ubuntuhandbook.org/index.php/2016/07/remote-access-ubuntu-16-04/ and turned off the encryption using dconf-editor. When I connect to 129.254.xxx.yyy:1, I finally got connected and could use the vnc for maybe a minute? but then the connection was closed by the server. I don't know what the problem is.

every time windows get an update my Ubuntu (which is installed in another partition of another disk) loses his Wirelless drivers so i don't have any chance of conecting to the internet.

I had a problem a couple months ago where my PC couldn't find the drivers of the card and it said "No wifi adapter found" but i fixed it. But now i dont even have the symbol of the wifi in the settings.

My wirelles card is Intel Wi-Fi 6 AX201(2*2 ax) and my laptop is the MSI Prestige 15

I have installed a VBOX virtual machine with Ubuntu 18.04.03 LTS in which I want to use 2 network connections, a NAT and a Bridge ones.

Show when I enable this adapters and start Ubuntu virtual machine, I try to see all the network cards I have, using:

lshw -c network -businfo

With that, i see that I have 2 devices, enp0s3 and enp0s8, but when I use the ifconfig, only the enp0s3 is shown.

How can I enable the enp0s8? I have tried adding to

netplan 50-cloud-init.yml 

and executing sudo netplan apply

But nothing changes for me

Thanks!

I really need assistance in setting up SNMP to work with Zabbix on my dashboard. I have set up an Ubuntu 18.04 Zabbix server and have added over 18 agents. All virtual machines with Zabbix agents and they are working great!

Now I have gotten to the point where I need to have the AP's set up for Zabbix. I have followed the instructions and did the following so far:

sudo apt-get update
sudo apt-get install snmp snmp-mibs-downloader
sudo apt-get update
sudo apt-get install snmpd

I opened sudo nano /etc/snmp/snmp.conf and commented the following line:

#mibs :

Then I went into the configuration file:

sudo nano /etc/snmp/snmpd.conf

And from there I made changes to the following lines:

Listen for connections from the local system only
agentAddress  udp:127.0.0.1:161  <--- commented this part.
Listen for connections on all interfaces (both IPv4 and IPv6)
agentAddress udp:161,udp6:[::1]:161  <--remove the comment from this line to make it work.

Then I set up the Zabbix dashboard side. I will attach pictures of the set-up.

1st zabbix dashboard menu:

2nd dashboard set-up menu:

I get the following error:

I will also attach picture that shows my meraki access point set-up.

Meraki AP SNMP set-up:

Lastly, I will add a picture that shows the Linux Zabbix server terminal set up on that config file.

Linux Zabbix Server:

I am stumped and cannot figure out why Zabbix still throwing out that error.

I have gone thru the Zabbix documentation but cannot find a solution to my problem.

I'm returning to Ubuntu after many years, but in my LAN I still need some machines with Windows 7.

Right now I'm running Ubuntu 19.10 and I want to share a folder. I did the following steps:

1. browse to the desired folder
2. right click and select "share"
3. enable the sharing (it installed samba) and the read/write access (but not the free access flag)

Because my installation is in Italian, I don't know the exact words in the English version, I hope it's clear what I'm saying.

Then I powered up my Windows machine and in the network places I saw my Ubuntu machine. Double click and it showed the shared folder. To enter it, it requested a login. Good.

Well, I entered the username/password of my Ubuntu user, because the "free access" flag says: "who haven't a user account". I have it, and I know the credentials, but they are refused.

Hence, I wonder what does "user account" actually mean in this context. It isn't referred to the Ubuntu account (the owner of the shared folder) ?

I have more than two users on my system and two different network interfaces and I would like to make my second user to preferre one of them.

One of these devices are eth0 and tun1. Is it possible to achieve this or are options like these systemwide?

The other user should continue using eth0.

Yes I am using ubuntu. (18.04)

I've just started setting up a multi-gig network. I've found some nice USB to 2.5GBASE-T adapters.

Now whilst they do run out-of-the-box, they seem to be using cdc-ncm as their driver which can't fully utilize the capabilities of the NIC (Limited to 1500MTU and hampered performance)

This is solved by installing the now outdated Realtek drivers for this chip. Problem is, I need to kick both cdc-mbim and cdc-ncm with modprobe -r before attaching the device since otherwise the modules will conflict and cdc-ncm will win. However I don't just want to blacklist those two modules since I also have a LTE modem installed which uses those modules.

My two questions:

1. How can I prevent cdc-ncm from overtaking the device without just ripping it out?
2. How can I patch the driver to work with the latest kernel versions?

System info:

• uname -r: 5.3.8-050308-generic
• Realtek driver: r8152_2.12.0
• dmesg output after connecting with cdc-ncm:

[  556.959398] usb 3-3.2: New USB device found, idVendor=0bda, idProduct=8156, bcdDevice=30.00
[  556.959400] usb 3-3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[  556.959401] usb 3-3.2: Product: USB 10/100/1G/2.5G LAN
[  556.959402] usb 3-3.2: Manufacturer: Realtek
[  556.959403] usb 3-3.2: SerialNumber: 000000001
[  556.984103] cdc_ncm 3-3.2:2.0: MAC-Address: a0:ce:c8:cb:7c:ca
[  556.984105] cdc_ncm 3-3.2:2.0: setting rx_max = 16384
[  556.984172] cdc_ncm 3-3.2:2.0: setting tx_max = 16384
[  556.984445] cdc_ncm 3-3.2:2.0 usb0: register 'cdc_ncm' at usb-0000:00:14.0-3.2, CDC NCM, a0:ce:c8:cb:7c:ca
[  557.009821] usbcore: registered new interface driver r8152
[  557.012312] cdc_ncm 3-3.2:2.0 enxa0cec8cb7cca: renamed from usb0
[  557.062459] usb 2-3.1.1: new high-speed USB device number 8 using xhci_hcd
[  557.062510] cdc_ncm 3-3.2:2.0 enxa0cec8cb7cca: network connection: disconnected
[  557.094515] cdc_ncm 3-3.2:2.0 enxa0cec8cb7cca: network connection: disconnected
[  557.126508] cdc_ncm 3-3.2:2.0 enxa0cec8cb7cca: network connection: disconnected
[  557.158506] cdc_ncm 3-3.2:2.0 enxa0cec8cb7cca: network connection: disconnected
[  557.190514] cdc_ncm 3-3.2:2.0 enxa0cec8cb7cca: network connection: disconnected

• dmesg output after kicking the two modules:

[  624.246651] usb 3-3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[  624.246653] usb 3-3.2: Product: USB 10/100/1G/2.5G LAN
[  624.246654] usb 3-3.2: Manufacturer: Realtek
[  624.246655] usb 3-3.2: SerialNumber: 000000001
[  624.330110] usb 3-3.2: reset SuperSpeed Gen 1 USB device number 5 using xhci_hcd
[  624.444293] r8152 3-3.2:1.0 eth0: v2.12.0 (2019/04/29)
[  624.444295] r8152 3-3.2:1.0 eth0: Hello 
[  624.606497] usbcore: registered new interface driver cdc_ncm
[  624.608322] usbcore: registered new interface driver cdc_wdm
[  624.656599] cdc_mbim 2-4:1.0: setting rx_max = 16384
[  624.657267] cdc_mbim 2-4:1.0: cdc-wdm0: USB WDM device
[  624.657816] cdc_mbim 2-4:1.0 wwan0: register 'cdc_mbim' at usb-0000:00:14.0-4, CDC MBIM, d2:c8:53:b2:65:df
[  624.659148] usbcore: registered new interface driver cdc_mbim
[  624.661511] cdc_mbim 2-4:1.0 wwp0s20u4: renamed from wwan0
[  624.675680] r8152 3-3.2:1.0 enxa0cec8cb7cca: renamed from eth0
[  628.423530] IPv6: ADDRCONF(NETDEV_CHANGE): enxa0cec8cb7cca: link becomes ready
[  628.423959] r8152 3-3.2:1.0 enxa0cec8cb7cca: carrier on

Any help is greatly appreciated!

I am facing an issue in my HP laptop which is running Ubantu 18.04.3 when I connect with my cellphone hotspot it is running fine but in case of router it is not even connecting. I have tried alot of troubleshoot for last 2 days but alas!.

FYR

sudo iwconfig 

lo1      IEEE 802.11  ESSID:"xxxxxx"  
          Mode:Managed  Frequency:2.417 GHz  Access Point: xxxxxxxxxx  
          Bit Rate=72.2 Mb/s   Tx-Power=20 dBm   
          Retry short limit:7   RTS thr=2347 B   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=45/70  Signal level=-65 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:650   Missed beacon:0

This info I got when I have connected with my cellphone hotspot.

Thanks in advance.

result of below given command

lspci -knn | grep Net -A3

libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/rtl8723be.conf line 1: ignoring bad line starting with '“options'
03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec:d723]
    Subsystem: Hewlett-Packard Company Device [103c:8319]
    Kernel driver in use: rtl8723de
    Kernel modules: rtl8723de

I have an existing Thunderbird profile that I use across several devices (keeping in sync the directory). Today I installed Ubuntu 19.10 and Thunderbird 68.4.1. I imported the existing profile with no problems.

But it refuses to connect to any account. I have three different emails account (POP and IMAP, on different providers) and for all three it fails to accept the password for both POP/IMAP and SMPT.

Hence I'm sure I'm missing something obvious.

What I've already checked:

• account credentials
• Internet connection
• ip6 disabled

If I import the very same profile in a Windows machine, Thunderbird connects to all accounts, so I think there's something wrong in the Ubuntu setup.

Actually, it doesn't return any error. It just swallows the password silently, and requests it again next time it tries to connect.

A couple of months ago, I got a new XPS 15 (7590).

I immediately installed Ubuntu 19.10, and had no problems, everything worked great.

Yesterday, after not using it for several days, I attempted to do so, and I was surprised I had no internet. I thought maybe my configuration lost WiFi password, and I'd have to re-enter it.

But no, when I went to do that, I got message that the WiFi was not detected.

ifconfig -a shows only lo.

It seems the WiFi driver is missing.

Is this some kind of regression? Did a kernel or firmware upgrade break my WiFi?

Any clues?

Thanks!

So here we go again. Yet another WiFi problem in a clean Ubuntu installation. I installed 18.04 LTS

dmesg | grep iwl gives me this-

[    1.674861] iwlwifi 0000:00:14.3: loaded firmware version 43.95eb4e97.0 op_mode iwlmvm
[    1.694573] iwlwifi 0000:00:14.3: Detected Intel(R) Dual Band Wireless AC 9462, REV=0x354
[    6.709017] iwlwifi 0000:00:14.3: Failed to load firmware chunk!
[    6.709020] iwlwifi 0000:00:14.3: iwlwifi transaction failed, dumping registers
[    6.709021] iwlwifi 0000:00:14.3: iwlwifi device config registers:
[    6.709093] iwlwifi 0000:00:14.3: 00000000: 02f08086 00100406 02800000 00800000 a1218004 00000000 00000000 00000000
[    6.709094] iwlwifi 0000:00:14.3: 00000020: 00000000 00000000 00000000 42a48086 00000000 000000c8 00000000 000001ff
[    6.709095] iwlwifi 0000:00:14.3: iwlwifi device memory mapped registers:
[    6.709123] iwlwifi 0000:00:14.3: 00000000: 58489004 00000040 00000000 00000000 00000000 00000000 00000000 00000000
[    6.709124] iwlwifi 0000:00:14.3: 00000020: 00000011 0c040005 00000351 d55555d5 d55555d5 d55555d5 80008040 001f0040
[    6.709141] iwlwifi 0000:00:14.3: Could not load the [0] uCode section
[    6.709161] iwlwifi 0000:00:14.3: Failed to start INIT ucode: -110
[    6.709162] iwlwifi 0000:00:14.3: Collecting data: trigger 15 fired.
[    6.916301] iwlwifi 0000:00:14.3: Failing on timeout while stopping DMA channel 8 [0x0bad1122]
[    6.928661] iwlwifi 0000:00:14.3: Failed to run INIT ucode: -110

and the network controller in the lspci is, for some reason, listed as 02f0 instead of Intel Dual Band Wireless 9462-

00:14.3 Network controller: Intel Corporation Device 02f0

I'm currently trying to create a setup that forwards traffic through a Ubuntu server to a switch, which then multiple servers will be connected to (each assigned an individual IP(s)) The Ubuntu server has a PCI NIC and a on-board port.

The PCI NIC (enp0s25) is connected to the outside world, then it should pipe out of the on-board port (enp1s0) to the switch.

I was reading into network bridges but I can't seem to figure out how to bridge two interfaces together like that. The reason for this server is to act as a firewall above the switch (running stuff with XDP/eBPF for advanced filtering).

My current netplan config looks as the following:

network:
    version: 2
ethernets:
    enp1s0:
        dhcp4: true
    enp0s25:
        dhcp4: true
bridges:
    br0:
        interfaces: [enp1s0]
        dhcp4: true
        optional: true

This obviously isn't working. I'm quite new to networking so interested in learning all of this.

I was installing Octave on Ubuntu 19.10 based on instructions available here http://ubuntuhandbook.org/index.php/2019/07/gnu-octave-install-snap-ubuntu/

so after doing

sudo snap install --beta octave
Download snap "octave" (10) from channel "beta"

download has been happening and it took a couple of hours and at some point internet connection broke.The machine has not been powered off for more than 15 hours and for 5-6 hours there was no internet connectivity. I was sleeping and when I woke up and then after a couple of hours when internet is back I have this so I want to know what can I do in this situation I know that my connection is fast because other devices I have are enjoying fast speed. Only this virtual machine on vmware is stuck at a point. What can I do in this situation to may be stop this and start downloading or installing from where ever it left in between and continue with full speed rather than a hanged installation ?

I had set suspend.disable="TRUE" in virtual machines .vmx file https://kb.vmware.com/s/article/2056501 so machine did not suspended that I am sure also the gui icon for vmware is greyed out due to this

my wifi adapter somehow stopped working (together with my graphics card) on my Ubuntu 18.04 machine. After reinstalling my Nvidia driver my graphics are working again, thats not a problem. But somehow I can't get the USB adapter working again.

Outpu of lshw:

 *-usb UNCLAIMED                                                                                                                      
      description: Generic USB device                                                                                                 
      product: 802.11ac NIC                                                                                                           
      vendor: Realtek                                                                                                                 
      physical id: 3                                                                                                                  
      bus info: usb@3:b.3                                                                                                             
      version: 2.10                                                                                                                   
      serial: 123456                                                                                                                  
      capabilities: usb-2.10                                                                                                          
      configuration: maxpower=500mA speed=480Mbit/s 

In lsusb the wifi adapter shows like that:

Bus 003 Device 017: ID 0bda:b812 Realtek Semiconductor Corp. 

• I tried installing the drivers from this repo: https://github.com/lwfinger/rtlwifi_new -> No success
• I followed this article which helped in the first setup https://rehmann.co/blog/drivers-wifi-usb-adapter-osxmac-linux-windows/ -> No success
• Tried different USB ports without success either.

Using an HP 245 G6 laptop with AMD A9 APU and Realtek 8723de wireless running Ubuntu 19.04.

To resolve an issue with the laptop being unable to resume from suspend properly (AMDGPU crashing on resume) I've manually installed Linux kernel 5.3 (rc6 currently - I found some info on the issue I was having here https://bugzilla.redhat.com/show_bug.cgi?id=1704792).

However I can't install the driver for the Wi-Fi from https://github.com/lwfinger/rtlwifi_new.git on kernel 5.3 - any ideas on how to get this working in the newer kernel would be appreciated.

Specifically, during the rtlwifi install, after running:

sudo dkms install rtlwifi-new/0.6

I get:

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area....
make -j4 KERNELRELEASE=5.3.0-050300rc6-generic -C /lib/modules/5.3.0-050300rc6-generic/build M=/var/lib/dkms/rtlwifi-new/0.6/build.............(bad exit status: 2)
ERROR (dkms apport): binary package for rtlwifi-new: 0.6 not found
Error! Bad return status for module build on kernel: 5.3.0-050300rc6-generic (x86_64)
Consult /var/lib/dkms/rtlwifi-new/0.6/build/make.log for more information.

The log at /var/lib/dkms/rtlwifi-new/0.6/build/make.log contains:

DKMS make.log for rtlwifi-new-0.6 for kernel 5.3.0-050300rc6-generic (x86_64)
Mon Sep  2 14:42:59 NZST 2019
make: Entering directory '/usr/src/linux-headers-5.3.0-050300rc6-generic'
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/btcoexist/halbtc8192e2ant.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8188ee/dm.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/halmac/halmac_api.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/phydm_debug.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/halmac/halmac_88xx/halmac_api_88xx_usb.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8188ee/fw.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/btcoexist/halbtc8723b1ant.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/halmac/halmac_88xx/halmac_api_88xx_sdio.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/phydm_antdiv.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8188ee/hw.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/phydm_soml.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/halmac/halmac_88xx/halmac_api_88xx.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/btcoexist/halbtc8723b2ant.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/phydm_smt_ant.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8188ee/led.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/phydm_interface.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/btcoexist/halbtc8821a1ant.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/halmac/halmac_88xx/halmac_api_88xx_pcie.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8188ee/phy.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/phydm_phystatus.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/halmac/halmac_88xx/halmac_func_88xx.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/btcoexist/halbtc8821a2ant.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/phydm_hwconfig.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8188ee/pwrseq.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/phydm.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/btcoexist/halbtc8822b1ant.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/halmac/halmac_88xx/halmac_8822b/halmac_api_8822b_pcie.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8188ee/rf.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8188ee/sw.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/halmac/halmac_88xx/halmac_8822b/halmac_func_8822b.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/phydm_dig.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/btcoexist/halbtc8822b2ant.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8188ee/table.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/halmac/halmac_88xx/halmac_8822b/halmac_api_8822b_sdio.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8188ee/trx.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/phydm_pathdiv.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/halmac/halmac_88xx/halmac_8822b/halmac_api_8822b.o
  LD [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8188ee/rtl8188ee.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/phydm_rainfo.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192c/main.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/halmac/halmac_88xx/halmac_8822b/halmac_8822b_phy.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/btcoexist/halbtc8822bwifionly.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192c/dm_common.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/phydm_dynamictxpower.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/halmac/halmac_88xx/halmac_8822b/halmac_8822b_pwr_seq.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/btcoexist/halbtc8723d1ant.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/phydm_adaptivity.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192c/fw_common.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/halmac/halmac_88xx/halmac_8822b/halmac_api_8822b_usb.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/halmac/rtl_halmac.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/btcoexist/halbtc8723d2ant.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/phydm_cfotracking.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192c/phy_common.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/phydm_noisemonitor.o
  LD [M]  /var/lib/dkms/rtlwifi-new/0.6/build/halmac/halmac.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192ce/dm.o
  LD [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192c/rtl8192c-common.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192cu/dm.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/phydm_dfs.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192ce/hw.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/btcoexist/halbtcoutsrc.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192cu/hw.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/phydm_adc_sampling.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/btcoexist/rtl_btc.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192ce/led.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/phydm_ccx.o
  LD [M]  /var/lib/dkms/rtlwifi-new/0.6/build/btcoexist/btcoexist.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192de/dm.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192ce/phy.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192cu/led.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/phydm_psd.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192cu/mac.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192ce/rf.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192de/fw.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/phydm_primary_cca.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192ce/sw.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192cu/phy.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192de/hw.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/phydm_cck_pd.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192ce/table.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192ce/trx.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192cu/rf.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/phydm_rssi_monitor.o
  LD [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192ce/rtl8192ce.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192ee/dm.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192de/led.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192cu/sw.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/phydm_auto_dbg.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192de/phy.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192cu/table.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/phydm_math_lib.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192cu/trx.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192ee/fw.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/phydm_api.o
  LD [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192cu/rtl8192cu.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192se/dm.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192ee/hw.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/phydm_pow_train.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192se/fw.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192de/rf.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/halrf/halrf.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192se/hw.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192ee/led.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192de/sw.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192ee/phy.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192de/table.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/halrf/halphyrf_ce.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192de/trx.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192se/led.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/halrf/halrf_powertracking_ce.o
  LD [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192de/rtl8192de.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723ae/dm.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192se/phy.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192ee/pwrseq.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/halrf/halrf_powertracking.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723ae/fw.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192ee/rf.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/halrf/halrf_kfree.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192se/rf.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723ae/hal_btc.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192ee/sw.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/halrf/rtl8822b/halrf_8822b.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192se/sw.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192ee/table.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192ee/trx.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723ae/hal_bt_coexist.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192se/table.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/halrf/rtl8822b/halrf_iqk_8822b.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192se/trx.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723ae/hw.o
  LD [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192ee/rtl8192ee.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723be/dm.o
  LD [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8192se/rtl8192se.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723com/main.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/rtl8822b/halhwimg8822b_bb.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723com/dm_common.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723be/fw.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/rtl8822b/halhwimg8822b_mac.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723ae/led.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723com/fw_common.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723be/hw.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/rtl8822b/halhwimg8822b_rf.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723ae/phy.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723com/phy_common.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723ae/pwrseq.o
  LD [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723com/rtl8723-common.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/rtl8822b/phydm_hal_api8822b.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723de/fw.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723be/led.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723ae/rf.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723be/phy.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723de/hw.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/rtl8822b/phydm_regconfig8822b.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723ae/sw.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/rtl8822b/phydm_rtl8822b.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723ae/table.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723ae/trx.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723be/pwrseq.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723de/led.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/rtl8723d/halhwimg8723d_bb.o
  LD [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723ae/rtl8723ae.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8821ae/dm.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723be/rf.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723de/phy.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/rtl8723d/halhwimg8723d_mac.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723be/sw.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8821ae/fw.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/rtl8723d/halhwimg8723d_rf.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723de/pwrseq.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723be/table.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723be/trx.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723de/rf.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/rtl8723d/phydm_regconfig8723d.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8821ae/hw.o
  LD [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723be/rtl8723be.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8822be/fw.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723de/sw.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/rtl8723d/phydm_rtl8723d.o
/var/lib/dkms/rtlwifi-new/0.6/build/rtl8821ae/hw.c: In function ‘_rtl8821ae_mrate_idx_to_arfr_id’:
/var/lib/dkms/rtlwifi-new/0.6/build/rtl8821ae/hw.c:3453:8: warning: this statement may fall through [-Wimplicit-fallthrough=]
    ret = 7;
    ~~~~^~~
/var/lib/dkms/rtlwifi-new/0.6/build/rtl8821ae/hw.c:3454:2: note: here
  case RATR_INX_WIRELESS_AC_5N:
  ^~~~
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/halrf/rtl8723d/halrf_8723d.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723de/table.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8822be/hw.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723de/trx.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8821ae/led.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/rtl_phydm.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8821ae/phy.o
  LD [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8723de/rtl8723de.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/base.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8822be/led.o
/var/lib/dkms/rtlwifi-new/0.6/build/rtl8821ae/phy.c: In function ‘_rtl8812ae_phy_set_rfe_reg_24g’:
/var/lib/dkms/rtlwifi-new/0.6/build/rtl8821ae/phy.c:389:6: warning: this statement may fall through [-Wimplicit-fallthrough=]
   if (rtlpriv->btcoexist.bt_coexistence) {
      ^
/var/lib/dkms/rtlwifi-new/0.6/build/rtl8821ae/phy.c:397:2: note: here
  case 0:
  ^~~~
  LD [M]  /var/lib/dkms/rtlwifi-new/0.6/build/phydm/phydm_mod.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8822be/phy.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/cam.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/core.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/debug.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8822be/sw.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8821ae/pwrseq.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/efuse.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/ps.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8822be/trx.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8821ae/rf.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rc.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/regd.o
  LD [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8822be/rtl8822be.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/stats.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8821ae/sw.o
/var/lib/dkms/rtlwifi-new/0.6/build/rc.c: In function ‘rtl_get_rate’:
/var/lib/dkms/rtlwifi-new/0.6/build/rc.c:191:6: error: implicit declaration of function ‘rate_control_send_low’; did you mean ‘rate_control_set_rates’? [-Werror=implicit-function-declaration]
  if (rate_control_send_low(sta, priv_sta, txrc))
      ^~~~~~~~~~~~~~~~~~~~~
      rate_control_set_rates
cc1: some warnings being treated as errors
make[1]: *** [scripts/Makefile.build:281: /var/lib/dkms/rtlwifi-new/0.6/build/rc.o] Error 1
make[1]: *** Waiting for unfinished jobs....
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8821ae/table.o
  CC [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8821ae/trx.o
  LD [M]  /var/lib/dkms/rtlwifi-new/0.6/build/rtl8821ae/rtl8821ae.o
make: *** [Makefile:1624: _module_/var/lib/dkms/rtlwifi-new/0.6/build] Error 2
make: Leaving directory '/usr/src/linux-headers-5.3.0-050300rc6-generic'

I bring my laptop along between different locations and networks, and in order to print, I have a separate .cups/client.conf (specifying the ServerName and user) for each network, with client.conf being a symlink to the appropriate config. This works, but it is cumbersome to update the symlink manually, is there a better way to do this?