(12-02-2018, 05:31 PM)pane Wrote: 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

(12-02-2018, 05:42 PM)evilbunny Wrote:

(12-02-2018, 05:31 PM)pane Wrote: 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.

(12-03-2018, 07:13 PM)pane Wrote: 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?

(12-03-2018, 07:28 PM)evilbunny Wrote:

(12-03-2018, 07:13 PM)pane Wrote: 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"
}

(12-03-2018, 08:38 PM)pane Wrote:

(12-03-2018, 07:28 PM)evilbunny Wrote:

(12-03-2018, 07:13 PM)pane Wrote: 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

(12-18-2018, 06:22 PM)pane Wrote: 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?