RTL8812AU driver and connection issues

[pane]

Hi All,

I managed to get the RTL8812AU driver working with the help of evilbunny. However, I am having connection issues, and power saving issues.

Power save issues seem to occur when the driver is not connecting to wifi. Fair enough, but when I use nmtui to connect to the wifi, my gui gets spammed with the "nolinked power save leave/enter" messages. It would be nice if there was a way to disable this either in startup or the driver itself.

Additionally, is there a process which works better than others for connections? I am unable to connect to networks 95% of the time with nmtui. Would anyone advocate for using wpa_supplicant or something else entirely for stable connections?

Thanks for your time
pane

[evilbunny]

Hi All,

I managed to get the RTL8812AU driver working with the help of evilbunny. However, I am having connection issues, and power saving issues.

Power save issues seem to occur when the driver is not connecting to wifi. Fair enough, but when I use nmtui to connect to the wifi, my gui gets spammed with the "nolinked power save leave/enter" messages. It would be nice if there was a way to disable this either in startup or the driver itself.

Additionally, is there a process which works better than others for connections? I am unable to connect to networks 95% of the time with nmtui. Would anyone advocate for using wpa_supplicant or something else entirely for stable connections?

Thanks for your time
pane

You can disable the power saving mode by editing the Makefile and turning power saving off

CONFIG_POWER_SAVING = n


Then recompile etc.

[pane]

Hi All,

I managed to get the RTL8812AU driver working with the help of evilbunny. However, I am having connection issues, and power saving issues.

Power save issues seem to occur when the driver is not connecting to wifi. Fair enough, but when I use nmtui to connect to the wifi, my gui gets spammed with the "nolinked power save leave/enter" messages. It would be nice if there was a way to disable this either in startup or the driver itself.

Additionally, is there a process which works better than others for connections? I am unable to connect to networks 95% of the time with nmtui. Would anyone advocate for using wpa_supplicant or something else entirely for stable connections?

Thanks for your time
pane

You can disable the power saving mode by editing the Makefile and turning power saving off

CONFIG_POWER_SAVING = n


Then recompile etc.

Thanks evilbunny I will recompile, I found that the output stream from power saving would spam the SSID key box in nmtui. What is your preferred process for connecting to networks? I have had limited success with nmtui - do you use wpa_supplicant or something else to reliably connect to networks?

Thanks

[evilbunny]

Thanks evilbunny I will recompile, I found that the output stream from power saving would spam the SSID key box in nmtui. What is your preferred process for connecting to networks? I have had limited success with nmtui - do you use wpa_supplicant or something else to reliably connect to networks?

I use network manager when I use a gui, but use /etc/network/interfaces.d/ on headless systems.

# cat /etc/network/interfaces.d/wlan0

Code:

auto wlan0
allow-hotplug wlan0
iface wlan0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

# cat /etc/wpa_supplicant/wpa_supplicant.conf

Code:

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
network={
       ssid="myaccesspoint"
       psk="mypassword"
}

[pane]

Thanks evilbunny I will recompile, I found that the output stream from power saving would spam the SSID key box in nmtui. What is your preferred process for connecting to networks? I have had limited success with nmtui - do you use wpa_supplicant or something else to reliably connect to networks?

I use network manager when I use a gui, but use /etc/network/interfaces.d/ on headless systems.

# cat /etc/network/interfaces.d/wlan0

Code:

auto wlan0
allow-hotplug wlan0
iface wlan0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

# cat /etc/wpa_supplicant/wpa_supplicant.conf

Code:

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
network={
       ssid="myaccesspoint"
       psk="mypassword"
}

Thanks for that evilbunny, your advice is always helpful - I consider my issue solved now, I will use wpa_supplicant then instead of nmtui as I am using headless debian

[pane]

Thanks evilbunny I will recompile, I found that the output stream from power saving would spam the SSID key box in nmtui. What is your preferred process for connecting to networks? I have had limited success with nmtui - do you use wpa_supplicant or something else to reliably connect to networks?

I use network manager when I use a gui, but use /etc/network/interfaces.d/ on headless systems.

# cat /etc/network/interfaces.d/wlan0

Code:

auto wlan0
allow-hotplug wlan0
iface wlan0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

# cat /etc/wpa_supplicant/wpa_supplicant.conf

Code:

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
network={
       ssid="myaccesspoint"
       psk="mypassword"
}

Thanks for that evilbunny, your advice is always helpful - I consider my issue solved now, I will use wpa_supplicant then instead of nmtui as I am using headless debian

Hi evilbunny - have finally found the time to try this rock64 stuff again - I am still having trouble with connecting to wifi using the rtl8812au driver. I am attempting to use your interface.d method with wpa_supplicant, and get a whole lot of "IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready". HOWEVER, I notice that my wifi adapter is not called wlan0 but is instead wlxFFFFFFFFFF etc dependent on MAC address. So I think the reason my connection is not working is because wlan0 is hard coded into the driver somewhere, while my adapter itself is wlxFFFFFFFF. Would you agree?

[evilbunny]

Hi evilbunny - have finally found the time to try this rock64 stuff again - I am still having trouble with connecting to wifi using the rtl8812au driver. I am attempting to use your interface.d method with wpa_supplicant, and get a whole lot of "IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready". HOWEVER, I notice that my wifi adapter is not called wlan0 but is instead wlxFFFFFFFFFF etc dependent on MAC address. So I think the reason my connection is not working is because wlan0 is hard coded into the driver somewhere, while my adapter itself is wlxFFFFFFFF. Would you agree?

wlan0 shouldn't be hard coded anywhere. You can for the time being disable netbios names by editing /etc/default/extlinux and I'm not sure what the command is to make it update the current config so I manually edit /boot/extlinux/extlinux.conf for good measure by adding the following on the end of the append line:

Code:

net.ifnames=0 biosdevname=0

[pane]

Hi evilbunny, I believe I found the source of my errors and connection problems... MAC address filtering. Your dkms wifi drivers seem to work straight out of the box when I connect to my LAN AP, but not my office internet. Hence, my link was not ready as it was being denied by the routers MAC address filtering - when the network admin returns from holidays, I will confirm this. Thanks for your patience again in helping me debug.