I have an external USB antenna whose driver was installed, yet does not appear in System Settings/Connections in Kubuntu 17.04. More information can be found in the original question about this issue (How Can I Enable a Realtek USB Antenna?).
Output of lsmod | grep 8812
& rfkill list all
$ lsmod | grep 8812
$ rfkill list all
$: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Output of sudo dkms status
:
bbswitch, 0.8, 4.10.0-24-generic, x86_64: installed
bbswitch, 0.8, 4.10.0-26-generic, x86_64: installed
nvidia-381, 381.22, 4.10.0-24-generic, x86_64: installed
nvidia-381, 381.22, 4.10.0-26-generic, x86_64: installed
rtl8812au, 4.3.8.12175.20140902+dfsg, 4.10.0-24-generic, x86_64: installed
rtl8812au, 4.3.8.12175.20140902+dfsg, 4.10.0-26-generic, x86_64: installed
Outpus of modinfo 8812au | grep A811
:
alias: usb:v7392pA811d*dc*dsc*dp*ic*isc*ip*in*
Output of lsmod | grep 8812
:
Nothing Displayed
Output of lsmod | grep 8812
:
modprobe: ERROR: could not insert '8812au': Exec format error
Output of dmesg | grep -i -e rtl -e 8812
:
[22538.388812] usb 2-14: Device not responding to setup address.
[65970.179027] 8812au: version magic '4.10.0-24-generic SMP mod_unload ' should be '4.10.0-26-generic SMP mod_unload '
Output of iwconfig
& dmesg | grep 8812
:
sarah@ConvergentRefuge:~$ iwconfig
eno1 no wireless extensions.
lo no wireless extensions.
sarah@ConvergentRefuge:~$ dmesg | grep 8812
[ 2028.287249] RTL871X: rtl8812au v4.3.8_12175.20140902
[ 2028.287338] usbcore: registered new interface driver rtl8812au
[ 2033.979052] audit: type=1400 audit(1499387534.619:709): apparmor="DENIED" operation="mknod" profile="webbrowser-app" name="/dev/shm/lttng-ust-wait-7" pid=8812 comm="QQmlThread-ust" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
[ 2623.150998] audit: type=1400 audit(1499388123.752:1185): apparmor="DENIED" operation="mknod" profile="webbrowser-app" name="/dev/shm/lttng-ust-wait-7-1000" pid=9914 comm="QQmlThread-ust" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
[ 2623.170431] audit: type=1400 audit(1499388123.772:1186): apparmor="DENIED" operation="mknod" profile="webbrowser-app" name="/dev/shm/lttng-ust-wait-7-1000" pid=9915 comm="QQmlThread-ust" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
[ 2623.252008] audit: type=1400 audit(1499388123.856:1187): apparmor="DENIED" operation="mknod" profile="webbrowser-app" name="/dev/shm/lttng-ust-wait-7" pid=9916 comm="QQmlThread-ust" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
[ 2623.295266] audit: type=1400 audit(1499388123.900:1188): apparmor="DENIED" operation="mknod" profile="webbrowser-app" name="/dev/shm/lttng-ust-wait-7" pid=9917 comm="QQmlThread-ust" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
[ 2628.207767] audit: type=1400 audit(1499388128.812:1189): apparmor="DENIED" operation="mknod" profile="webbrowser-app" name="/dev/shm/lttng-ust-wait-7-1000" pid=9918 comm="QQmlThread-ust" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
[ 2628.252204] audit: type=1400 audit(1499388128.856:1190): apparmor="DENIED" operation="mknod" profile="webbrowser-app" name="/dev/shm/lttng-ust-wait-7-1000" pid=9919 comm="QQmlThread-ust" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
[ 2628.302456] audit: type=1400 audit(1499388128.904:1191): apparmor="DENIED" operation="mknod" profile="webbrowser-app" name="/dev/shm/lttng-ust-wait-7" pid=9920 comm="QQmlThread-ust" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
[ 2628.341144] audit: type=1400 audit(1499388128.944:1192): apparmor="DENIED" operation="mknod" profile="webbrowser-app" name="/dev/shm/lttng-ust-wait-7" pid=9921 comm="QQmlThread-ust" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
Best Answer
First, verify that the module installed correctly:
We hope we see:
Or similar.
Verify that the installed module covers your device, which is:
Run, in the terminal:
We hope we see:
Note that the second alias, 0BDA with A811 covers your device.
Is the module loaded?
If not, load it:
Are there any errors or warnings you can post? Or does the wireless come to life? If not, check the log for informative messages:
EDIT: We see the problem here:
I suggest that you correct it with:
If there are errors or warnings, please post them.
EDIT2: I suggest that we try another approach.
Reboot and let us hear your report.