S
Schroedinger
Guest
Hi
it seems thats also with Apollo (since this drives is part of image) the rt8812au chipset driver is not working properly.
See output messages/dmesg/opkg
Mar 6 07:25:51 vusolo2 user.info kernel: usb 4-1: new high-speed USB device number 2 using ehci-brcm
Mar 6 07:25:51 vusolo2 user.warn kernel: 8812au: Unknown symbol rtw_proc_remove_one (err 0)
Mar 6 07:25:51 vusolo2 user.warn kernel: 8812au: Unknown symbol rtw_proc_init_one (err 0)
usb 4-1: USB disconnect, device number 2
usb 4-1: new high-speed USB device number 3 using ehci-brcm
8812au: Unknown symbol rtw_proc_remove_one (err 0)
8812au: Unknown symbol rtw_proc_init_one (err 0)
root@vusolo2:~# opkg list_installed|grep 8812au
enigma2-plugin-drivers-network-usb-rtl8812au - 1.0-r1
kernel-module-8812au - 4.2.2-r4
rt8812au - 4.2.2-r4
It is an Edimax EW-7822UAC usb wlan stick (AC-1200), which is supposed to work with this box/driver. AFAIK the driver implementation in BH image had same issues. In last update of BH the driver was updated. I'm not aware, if BH has fixed this issue (last image did update this driver), but was the same problem.
Could one review this issue and provide help on this?
Thank you
Best regards
it seems thats also with Apollo (since this drives is part of image) the rt8812au chipset driver is not working properly.
See output messages/dmesg/opkg
Mar 6 07:25:51 vusolo2 user.info kernel: usb 4-1: new high-speed USB device number 2 using ehci-brcm
Mar 6 07:25:51 vusolo2 user.warn kernel: 8812au: Unknown symbol rtw_proc_remove_one (err 0)
Mar 6 07:25:51 vusolo2 user.warn kernel: 8812au: Unknown symbol rtw_proc_init_one (err 0)
usb 4-1: USB disconnect, device number 2
usb 4-1: new high-speed USB device number 3 using ehci-brcm
8812au: Unknown symbol rtw_proc_remove_one (err 0)
8812au: Unknown symbol rtw_proc_init_one (err 0)
root@vusolo2:~# opkg list_installed|grep 8812au
enigma2-plugin-drivers-network-usb-rtl8812au - 1.0-r1
kernel-module-8812au - 4.2.2-r4
rt8812au - 4.2.2-r4
It is an Edimax EW-7822UAC usb wlan stick (AC-1200), which is supposed to work with this box/driver. AFAIK the driver implementation in BH image had same issues. In last update of BH the driver was updated. I'm not aware, if BH has fixed this issue (last image did update this driver), but was the same problem.
Could one review this issue and provide help on this?
Thank you
Best regards