#Realtek rtl8821ae ubuntu 16.04 issues driver#
#Realtek rtl8821ae ubuntu 16.04 issues Patch#

Then shutdown the computer for at least 15 seconds. If the signal is too low, then (as root) create a file named /etc/modprobe.d/nf containing a line that contains 'options rtl8723be ant_sel=1'.

#Realtek rtl8821ae ubuntu 16.04 issues driver#

That is OK however, they incorrectly encoded the EFUSE, which is the information used by the driver to select the antenna. How does this happen? The most common cause is that your computer vendor saved a few pennies by only installing one antenna, not two. If it is much more negative than -50, then your device has no antenna selected. If your wifi device is not called wlan0, then make the appropriate change. Sudo iw dev wlan0 scan | egrep 'SSID|signal'

#Realtek rtl8821ae ubuntu 16.04 issues Patch#

It is defined in an earlier patch to fix rtl8821ae, but rtl8723be has the same problem on some platforms. If your kernel does not have a definition for ASPM_L1_LATENCY, substitute 7 for it. * Configuration Space offset 0x719 Bit3 is for L1 * Configuration Space offset 0x70f BIT7 is used to control L0S */

a/drivers/net/wireless/realtek/rtlwifi/rtl8723be/hw.c The patch isДrivers/net/wireless/realtek/rtlwifi/rtl8723be/hw.c | 3 ++-ДЎ file changed, 2 insertions(+), 1 deletion(-)Дiff -git a/drivers/net/wireless/realtek/rtlwifi/rtl8723be/hw.c b/drivers/net/wireless/realtek/rtlwifi/rtl8723be/hw.c There is a patch pending for kernel 4.16 and all stable kernels. Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort+ SERR. Subsystem: Hewlett-Packard Company Device 2231Д¬ontrol: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx. Kernel version: mainline 3.19.0, lwfinger's rtlwifi_new 15f04b7Д 1:00.0 Network controller: Realtek Semiconductor Co., Ltd. I've also added the 'fwlps=0' and 'ips=0' options to the module opts, with marginal improvement. I can now go several hours without the connection requiring a reset, but occasionally the connection will stop working despite NetworkManager etc still reporting the interface as associated.

I may not be experiencing the same bug, but lwfinger's rtlwifi_new package doesn't seem to fix the problem entirely, only partially.