However, in order to use all available features of this hardware, you must install the appropriate drivers.Įnabling the wireless card allows systems to read chipset information and manufacturer name, as well as connect to a network without using an Ethernet cable.
Windows OSes usually apply a generic driver that allows systems to recognize the wireless component. Browse to the folder where you extracted the driver and click Ok About Wireless LAN Drivers:
If you already have the driver installed and want to update to a newer version got to "Let me pick from a list of device drivers on my computer"ħ. Choose to select the location of the new driver manually and browse to the folder where you extracted the driverĥ. Right click on the hardware device you wish to update and choose Update Driver SoftwareĤ. Go to Device Manager (right click on My Computer, choose Manage and then find Device Manager in the left panel), or right click on Start Menu for Windows 10 and select Device Managerģ. In order to manually update your driver, follow the steps below (the next steps):ġ. Take into consideration that is not recommended to install the driver on Operating Systems other than stated ones.
If the driver is already installed on your system, updating (overwrite-installing) may fix various issues, add new functions, or just upgrade to the available version. It is really too bad they're not more open with their drivers and firmware.The package provides the installation files for Realtek 8723DU Wireless LAN 802.11n USB NIC Driver version 1030.41.514.2020. I'm just glad to year that AC is finally stable for any of these Realtek chipsets. I'm hopeful that by the time Libreelec releases 9.0 that the driver will either be split or the 88 chipsets will be included in 5.2.9 at that point. For now, I think it makes sense to get as much testing as possible with the 5.2.9 driver in your test builds (not that my opinion counts anyway ). Ideally the HAL support for the other chipsets would be merged into this newer driver, giving the same support as before, but it appears that chipset support is becoming a little fragmented with the more recent drivers provided by Realtek.
I don't know if it will be possible to continue using the older 5.1.5 driver for non-rtl8812au users - we may need to investigate that - or else we stick with the older and somewhat broken driver as that "works" for everyone. So at the moment a switch away from the old 5.1.5 driver would mean your hardware is no longer supported, but rtl8812au users would have working AC (based on feedback so far). The new rtl8812au driver doesn't include the HAL support for 8821AU/8814AU, and that's the only drawback to this driver. It's possible, but not looking terribly likely at the moment. Is there any hope in getting the 8821 device(s) working with 5.2.9? Excited that AC might finally work for others, but for now I guess I'm capped at 5.1.5. Which apparently uses the 8821 and not 8812 driver. Here is my log: kodi.log - Google Drive (didn't use pastebin because of the size of the log - 413 Request Entity Too Large) I've seen that someone else pointed out a similar problem in this thread: thread-3467-post-29019.htmlĪccording to bd0426, this problem was not present running OpenELEC 6.0.3 I've also tried to run the movies from a directly connected hard drive and in that case the playback went well. I've experienced the problem both with 7.0.3 and 8.0.1 version using smb and nfs. The messages from the logs are quite similar to the ones giannia posted. Going back to the file I was playing, it asks me to restart from where leaved and the playback goes well for other few minutes.
The video freeze for 30 seconds and then goes back to the main menu without restarting the GUI.
Every now and then (a very variable time from 2 to 30 minutes) happens that the stream of mkv files at 720p or 1080p stops. I am running LibreELEC on a RPi3 streaming through smb protocol from a RPi2 that I use as a NAS, among other things, with an Edimax EW-7811UTC that uses a rtl8812au chip.
RTL871X: set group key camid:5, addr:40:5d:82:d8:ed:e1, kid:1, type:AES Display More IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready RTL871X: rtw_cfg80211_indicate_connect(wlan0) BSS not found !!
IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready usbcore: registered new interface driver rtl8812au Code 8812au: loading out-of-tree module taints kernel.