New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rtl8821ae constantly dropping connection #235

Closed
pgueckel opened this Issue Apr 26, 2017 · 45 comments

Comments

Projects
None yet
@pgueckel

pgueckel commented Apr 26, 2017

I filed a bugzilla report at Fedora:

https://bugzilla.redhat.com/show_bug.cgi?id=1435793

but there has been no action. I was finally told to contact upstream if I wanted this fixed.

This morning I upgraded to kernel 4.11.0-0.rc8.git0.1.fc26.x86_64, but it has not changed—the problem persists.

@pgueckel

This comment has been minimized.

Show comment
Hide comment
@pgueckel

pgueckel Apr 27, 2017

There is a suggestion that fedora bug 1382741 (https://bugzilla.redhat.com/show_bug.cgi?id=1382741) is the same as the one I reported above. There has been some discussion, so maybe someone will be able to help.

pgueckel commented Apr 27, 2017

There is a suggestion that fedora bug 1382741 (https://bugzilla.redhat.com/show_bug.cgi?id=1382741) is the same as the one I reported above. There has been some discussion, so maybe someone will be able to help.

@pgueckel

This comment has been minimized.

Show comment
Hide comment
@pgueckel

pgueckel Apr 27, 2017

It is now thought that fedora bug 1382741 is not the same as this, but this is exactly the same bug as fedora bug 1435793 (since I reported it!).

pgueckel commented Apr 27, 2017

It is now thought that fedora bug 1382741 is not the same as this, but this is exactly the same bug as fedora bug 1435793 (since I reported it!).

@wyldcard

This comment has been minimized.

Show comment
Hide comment
@wyldcard

wyldcard Apr 28, 2017

I have the same problem on my ubuntu 16.04 machine. Its almost unusable. I'm also forced to use 2.4ghz because it simply wont connect to 5ghz even tho its visible. Im using the ASUS PCE-AC51 card.

wyldcard commented Apr 28, 2017

I have the same problem on my ubuntu 16.04 machine. Its almost unusable. I'm also forced to use 2.4ghz because it simply wont connect to 5ghz even tho its visible. Im using the ASUS PCE-AC51 card.

@lwfinger

This comment has been minimized.

Show comment
Hide comment
@lwfinger

lwfinger Apr 28, 2017

Owner

You do realize that this kind of complaint with no documentation does no good. Which card do you have? RTL8821AE or RTL8812AE? What country code does the card report?

On my RTL8821AE, I can connect to either of my 5G APs. The connection does drop, but that is nothing I can fix. The internal workings of the chip are unknown to me, thus only Realtek can fix that part.

I do not have an RTL8812AE.

Owner

lwfinger commented Apr 28, 2017

You do realize that this kind of complaint with no documentation does no good. Which card do you have? RTL8821AE or RTL8812AE? What country code does the card report?

On my RTL8821AE, I can connect to either of my 5G APs. The connection does drop, but that is nothing I can fix. The internal workings of the chip are unknown to me, thus only Realtek can fix that part.

I do not have an RTL8812AE.

@wyldcard

This comment has been minimized.

Show comment
Hide comment
@wyldcard

wyldcard Apr 28, 2017

Im sorry I realized that I wrote in haste with no feedback. I pulled your drivers I think 4 days ago, and I did not see your update to the RTL8821AE 2 days ago. Google led me straight when I were researching and I posted a quick heads up comment.

I tried your updated driver and I can now connect to the 5Ghz! Your comment popped up as I were typing to let you know your update works. Sorry for the crap comment, you are doing a fantastic job!

EDIT: Connection seems stable aswell. My fractal design chassi totally blocked my twin asus antennas also. Ookla speedtest went from 7mbit to 108mbit just by turning the case 90 degrees.

wyldcard commented Apr 28, 2017

Im sorry I realized that I wrote in haste with no feedback. I pulled your drivers I think 4 days ago, and I did not see your update to the RTL8821AE 2 days ago. Google led me straight when I were researching and I posted a quick heads up comment.

I tried your updated driver and I can now connect to the 5Ghz! Your comment popped up as I were typing to let you know your update works. Sorry for the crap comment, you are doing a fantastic job!

EDIT: Connection seems stable aswell. My fractal design chassi totally blocked my twin asus antennas also. Ookla speedtest went from 7mbit to 108mbit just by turning the case 90 degrees.

@pgueckel

This comment has been minimized.

Show comment
Hide comment
@pgueckel

pgueckel Apr 28, 2017

KDE KInfocenter reports that I have the RTL8821AE 802.11ac PCIe wireless adapter. My computer is an Asus F555LA laptop. I bought it new in Canada in August 2016. I have no idea how to determine the country code or how to get it to "report".

I am running Fedora 26 alpha, with all of the updates/test updates current to this minute. The current kernel is 4.11.0-0.rc8.git0.1.fc26.x86_64. Further network-related: wpa_supplicant-2.6-6.fc26.x86_64, NetworkManager-1.8.0-0.2.rc3.fc26.x86_64.

I have disabled 2.4G on my router and use only 5G (both work, both have the same problem). I just don't want to unnecessarily clog the airwaves in my building with signals I never use. I only have 3 devices that connect wirelessly: a Panasonic Blu-ray player, a Moto G4 Plus smart phone, and this Asus F555LA laptop. They can all use 802.11n. Only the laptop can use 802.11ac, so I decided to select 802.11n for the broadcasting (I read that, despite backward compatibility, it is better that all devices use the same protocol. Is it really necessary?).

Anyway, the phone and the blu-ray player have absolutely no problem connecting and maintaining a connection at 5G (and, formerly, at 2.4G). The laptop establishes a connection and it is sort of steady for a bit, a few minutes, a few web pages, sometimes barely a couple of seconds, and then NetworkManager suddenly displays no strength bars at all and the network is blocked (for the laptop, only!). It takes about a minute for NetworkManager then to display a message stating that the network is unavailable and that it has been disconnected. Then, it just meditates for another minute or so (seems like a ridiculously long time, on both counts!) and then it attempts to reconnect, succeeds instantly and the same symptoms start over again.

I don't know who is spreading this dyslexic info about RTL8812AE, because this is not! It is RTL8821AE.

pgueckel commented Apr 28, 2017

KDE KInfocenter reports that I have the RTL8821AE 802.11ac PCIe wireless adapter. My computer is an Asus F555LA laptop. I bought it new in Canada in August 2016. I have no idea how to determine the country code or how to get it to "report".

I am running Fedora 26 alpha, with all of the updates/test updates current to this minute. The current kernel is 4.11.0-0.rc8.git0.1.fc26.x86_64. Further network-related: wpa_supplicant-2.6-6.fc26.x86_64, NetworkManager-1.8.0-0.2.rc3.fc26.x86_64.

I have disabled 2.4G on my router and use only 5G (both work, both have the same problem). I just don't want to unnecessarily clog the airwaves in my building with signals I never use. I only have 3 devices that connect wirelessly: a Panasonic Blu-ray player, a Moto G4 Plus smart phone, and this Asus F555LA laptop. They can all use 802.11n. Only the laptop can use 802.11ac, so I decided to select 802.11n for the broadcasting (I read that, despite backward compatibility, it is better that all devices use the same protocol. Is it really necessary?).

Anyway, the phone and the blu-ray player have absolutely no problem connecting and maintaining a connection at 5G (and, formerly, at 2.4G). The laptop establishes a connection and it is sort of steady for a bit, a few minutes, a few web pages, sometimes barely a couple of seconds, and then NetworkManager suddenly displays no strength bars at all and the network is blocked (for the laptop, only!). It takes about a minute for NetworkManager then to display a message stating that the network is unavailable and that it has been disconnected. Then, it just meditates for another minute or so (seems like a ridiculously long time, on both counts!) and then it attempts to reconnect, succeeds instantly and the same symptoms start over again.

I don't know who is spreading this dyslexic info about RTL8812AE, because this is not! It is RTL8821AE.

@pgueckel

This comment has been minimized.

Show comment
Hide comment
@pgueckel

pgueckel Apr 28, 2017

I am very interested in this new driver you have and have no idea how to get it or how to install it. Is it in the Fedora repository?

pgueckel commented Apr 28, 2017

I am very interested in this new driver you have and have no idea how to get it or how to install it. Is it in the Fedora repository?

@pgueckel

This comment has been minimized.

Show comment
Hide comment
@pgueckel

pgueckel Apr 28, 2017

Oh, and I never had any problems at all with this card (no network loss, etc) until the last of the 4.9 kernels. I don't recall if it was the last 4.9 that still worked or the second-last 4.9. At first, I guess it just started dropping the connection and I didn't think too much of it, except that "this is new and never happened before", but it kept reconnecting, so I brushed it off as not noteworthy. I should have kept more accurate track :-( Kernels were issued every day or two or three from the fedora updates-testing repo (I was still using Fedora 25 then, back in March) and I upgraded as they came out. In any case, from kernel 4.10 onward, this problem has been persistent and unchanging. It was then that I realized that this was a problem that wasn't going away. I panicked and disabled the fedora updates-testing repo altogether and did a distro-sync to get my system back to the official updates (no more testing!). It didn't help, since the straight repo was pretty much caught up, with a lag of a day or three, to the updates-testing repo. I decided to post a bug report.

Pretty much the day after posting the report, I learned that Fedora 26 alpha had been released. I always keep a spare partition for testing, so I overwrote the old Fedora 24 with Fedora 26 alpha, keeping my working Fedora 25 system intact. Well, since swap and efi got reformatted, I was unable to get back into Fedora 25 (lol I got it working again a couple of days later, but there is no longer any point in me using an old release), so I have been using Fedora 26 ever since.

So, the problem began with the last of the Fedora 4.9 kernels in Fedora 25 and it was present in Fedora 26 from the get go.

pgueckel commented Apr 28, 2017

Oh, and I never had any problems at all with this card (no network loss, etc) until the last of the 4.9 kernels. I don't recall if it was the last 4.9 that still worked or the second-last 4.9. At first, I guess it just started dropping the connection and I didn't think too much of it, except that "this is new and never happened before", but it kept reconnecting, so I brushed it off as not noteworthy. I should have kept more accurate track :-( Kernels were issued every day or two or three from the fedora updates-testing repo (I was still using Fedora 25 then, back in March) and I upgraded as they came out. In any case, from kernel 4.10 onward, this problem has been persistent and unchanging. It was then that I realized that this was a problem that wasn't going away. I panicked and disabled the fedora updates-testing repo altogether and did a distro-sync to get my system back to the official updates (no more testing!). It didn't help, since the straight repo was pretty much caught up, with a lag of a day or three, to the updates-testing repo. I decided to post a bug report.

Pretty much the day after posting the report, I learned that Fedora 26 alpha had been released. I always keep a spare partition for testing, so I overwrote the old Fedora 24 with Fedora 26 alpha, keeping my working Fedora 25 system intact. Well, since swap and efi got reformatted, I was unable to get back into Fedora 25 (lol I got it working again a couple of days later, but there is no longer any point in me using an old release), so I have been using Fedora 26 ever since.

So, the problem began with the last of the Fedora 4.9 kernels in Fedora 25 and it was present in Fedora 26 from the get go.

@wyldcard

This comment has been minimized.

Show comment
Hide comment
@wyldcard

wyldcard Apr 28, 2017

The driver is here on lwfinger's gitgub repo.
A quick rundown how I did it...

git clone http://github.com/lwfinger/rtlwifi_new.git
cd rtlwifi_new
make
sudo make install

Load the module with:
modprobe rtl8821ae

You might want to add the module for loading upon boot, and if the old driver keeps loading blacklist it

wyldcard commented Apr 28, 2017

The driver is here on lwfinger's gitgub repo.
A quick rundown how I did it...

git clone http://github.com/lwfinger/rtlwifi_new.git
cd rtlwifi_new
make
sudo make install

Load the module with:
modprobe rtl8821ae

You might want to add the module for loading upon boot, and if the old driver keeps loading blacklist it

@lwfinger

This comment has been minimized.

Show comment
Hide comment
@lwfinger

lwfinger Apr 28, 2017

Owner

@pgueckel: If you want to help debug the problem, you need to obtain the git repo for the Fedora kernels and bisect the problem. If that is beyond your technical skills then you need to tell me exactly which Fedora kernel started the failure. No, 4.9 is not sufficient.

@wyldcard: Once you do the "sudo make install" step, the original (kernel) driver is overwritten. Adding a blacklist at that point will just cause no driver to load.

Owner

lwfinger commented Apr 28, 2017

@pgueckel: If you want to help debug the problem, you need to obtain the git repo for the Fedora kernels and bisect the problem. If that is beyond your technical skills then you need to tell me exactly which Fedora kernel started the failure. No, 4.9 is not sufficient.

@wyldcard: Once you do the "sudo make install" step, the original (kernel) driver is overwritten. Adding a blacklist at that point will just cause no driver to load.

@pgueckel

This comment has been minimized.

Show comment
Hide comment
@pgueckel

pgueckel Apr 28, 2017

@lwfinger I would like to help debug the problem. I have the computer with the affected hardware. I don't have a clue how to "obtain the git repo for the Fedora kernels" and I don't have a clue what it is to "bisect" the problem.

I can also not tell you exactly which Fedora (25) kernel started the failure. I am just looking through koji and I can see that the last two 4.9 kernels for Fedora 25 were kernel-4.9.13-201.fc25 and kernel-4.9.14-200.fc25. The first 4.10 kernel for Fedora 25 was kernel-4.10.4-200.fc25. It pretty much has to be one of these. I know that I was onto the problem pretty quickly, even if I did dally (convince myself that there was nothing wrong :-( ) for a few days.

pgueckel commented Apr 28, 2017

@lwfinger I would like to help debug the problem. I have the computer with the affected hardware. I don't have a clue how to "obtain the git repo for the Fedora kernels" and I don't have a clue what it is to "bisect" the problem.

I can also not tell you exactly which Fedora (25) kernel started the failure. I am just looking through koji and I can see that the last two 4.9 kernels for Fedora 25 were kernel-4.9.13-201.fc25 and kernel-4.9.14-200.fc25. The first 4.10 kernel for Fedora 25 was kernel-4.10.4-200.fc25. It pretty much has to be one of these. I know that I was onto the problem pretty quickly, even if I did dally (convince myself that there was nothing wrong :-( ) for a few days.

@pgueckel

This comment has been minimized.

Show comment
Hide comment
@pgueckel

pgueckel Apr 28, 2017

Correction: the first 4.10 kernel was kernel-4.10.3-200.fc25. So, the closest I can get is the last two 4.9s listed above and this one.

pgueckel commented Apr 28, 2017

Correction: the first 4.10 kernel was kernel-4.10.3-200.fc25. So, the closest I can get is the last two 4.9s listed above and this one.

@lwfinger

This comment has been minimized.

Show comment
Hide comment
@lwfinger

lwfinger Apr 28, 2017

Owner

You should be able to reinstall the 4.9.13 and 4.9.14 kernels from koji and test each of them to see if that is where the problem occurs. As to obtaining the git repo for Fedora, that is a question for Fedora. I do not use that repo.

Owner

lwfinger commented Apr 28, 2017

You should be able to reinstall the 4.9.13 and 4.9.14 kernels from koji and test each of them to see if that is where the problem occurs. As to obtaining the git repo for Fedora, that is a question for Fedora. I do not use that repo.

@pgueckel

This comment has been minimized.

Show comment
Hide comment
@pgueckel

pgueckel Apr 29, 2017

@lwfinger I did as you suggested—in Fedora 25!!! That is where the problem first occurred and it has never NOT OCCURRED in Fedora 26.

I installed:

kernel-4.9.13-200.fc25.x86_64 (works just fine, tested over an hour)
kernel-4.9.13-201.fc25.x86_64 (seems to work fine, but only tested for about 5-10 minutes)
kernel-4.9.14-200.fc25.x86_64 (HAS THE BUG)
kernel-4.10.3-200.fc25.x86_64 (not tried, but all subsequent kernels were tainted during the period I used Fedora 25, prior to migrating to Fedora 26 alpha)

This problem has also been manifest on ALL Fedora 26 kernels since the release of Fedora 26 alpha. What this means is that ALL Fedora kernels on both Fedora 25 and Fedora 26 since early March 2017 are BAD!

I hope this narrows it down enough for you to establish the error. If you wish, I can test 4.9.13-201 a little more, but, as I indicated, it seemed to be fine during the few minutes I did try it.

I do not use Fedora 25 any more, but this problem affects Fedora 26 from the get go (from the release of alpha, anyway), so this is most dire.

pgueckel commented Apr 29, 2017

@lwfinger I did as you suggested—in Fedora 25!!! That is where the problem first occurred and it has never NOT OCCURRED in Fedora 26.

I installed:

kernel-4.9.13-200.fc25.x86_64 (works just fine, tested over an hour)
kernel-4.9.13-201.fc25.x86_64 (seems to work fine, but only tested for about 5-10 minutes)
kernel-4.9.14-200.fc25.x86_64 (HAS THE BUG)
kernel-4.10.3-200.fc25.x86_64 (not tried, but all subsequent kernels were tainted during the period I used Fedora 25, prior to migrating to Fedora 26 alpha)

This problem has also been manifest on ALL Fedora 26 kernels since the release of Fedora 26 alpha. What this means is that ALL Fedora kernels on both Fedora 25 and Fedora 26 since early March 2017 are BAD!

I hope this narrows it down enough for you to establish the error. If you wish, I can test 4.9.13-201 a little more, but, as I indicated, it seemed to be fine during the few minutes I did try it.

I do not use Fedora 25 any more, but this problem affects Fedora 26 from the get go (from the release of alpha, anyway), so this is most dire.

@pgueckel

This comment has been minimized.

Show comment
Hide comment
@pgueckel

pgueckel Apr 30, 2017

I haven't tried wyldcard's solution. I did build the module, but I'd like to back up the files that get overwritten before running make install. It is pretty confusing: there are some files in /usr/lib/firmware and some in /usr/lib/modules, too, I think. I don't have a clue what would end up getting overwritten.

Since we are having this issue, maybe our kernels already have this driver/firmware? Like I said, the 4.9.13-20x kernels and earlier did not have the bug, only 4.9.14-200 and later.

pgueckel commented Apr 30, 2017

I haven't tried wyldcard's solution. I did build the module, but I'd like to back up the files that get overwritten before running make install. It is pretty confusing: there are some files in /usr/lib/firmware and some in /usr/lib/modules, too, I think. I don't have a clue what would end up getting overwritten.

Since we are having this issue, maybe our kernels already have this driver/firmware? Like I said, the 4.9.13-20x kernels and earlier did not have the bug, only 4.9.14-200 and later.

@wyldcard

This comment has been minimized.

Show comment
Hide comment
@wyldcard

wyldcard May 3, 2017

lwfinger's driver did improve the sitiation. However there are still issues Realtek need to fix. Im basically experiencing the same issues as noted by @ferviron . Im ordering in a new wifi card and washing my hands of this.

wyldcard commented May 3, 2017

lwfinger's driver did improve the sitiation. However there are still issues Realtek need to fix. Im basically experiencing the same issues as noted by @ferviron . Im ordering in a new wifi card and washing my hands of this.

@matchaniat

This comment has been minimized.

Show comment
Hide comment
@matchaniat

matchaniat May 3, 2017

I have the same problem with rtl8821ae, i use ArchLinux with 4.10.13-1-ARCH kernel. The connection drops after some time, the networkmanager disconnect and reconnect to the network some seconds after. Ater installing the lwfinger's driver, the situation didn't change... I can give you some logs if you want.

matchaniat commented May 3, 2017

I have the same problem with rtl8821ae, i use ArchLinux with 4.10.13-1-ARCH kernel. The connection drops after some time, the networkmanager disconnect and reconnect to the network some seconds after. Ater installing the lwfinger's driver, the situation didn't change... I can give you some logs if you want.

@Oden1

This comment has been minimized.

Show comment
Hide comment
@Oden1

Oden1 May 7, 2017

I had problems with my rtl8821ae 1a3b:2161 (ASUS X550IU laptop) that was dropping connection all the time, so often that it wasn't usable,
I have found int_clear=0 to be the parameter that makes it dropping the connection much more seldom.
"sudo modprobe -r rtl8821ae && sudo modprobe rtl8821ae ips=0 fwlps=0 swlps=1 disable_watchdog=1 int_clear=0"
But i still have problems with it disconnecting.
I know how to bisect kernels but i haven't used any kernel that was good yet.
Is there anything i can do to help or is it an firmware bug?
wireless-info.txt

Oden1 commented May 7, 2017

I had problems with my rtl8821ae 1a3b:2161 (ASUS X550IU laptop) that was dropping connection all the time, so often that it wasn't usable,
I have found int_clear=0 to be the parameter that makes it dropping the connection much more seldom.
"sudo modprobe -r rtl8821ae && sudo modprobe rtl8821ae ips=0 fwlps=0 swlps=1 disable_watchdog=1 int_clear=0"
But i still have problems with it disconnecting.
I know how to bisect kernels but i haven't used any kernel that was good yet.
Is there anything i can do to help or is it an firmware bug?
wireless-info.txt

@pgueckel

This comment has been minimized.

Show comment
Hide comment
@pgueckel

pgueckel May 7, 2017

I now run the 4.11.0-1.fc26.x86_64 kernel. I don't know if anything changed in the kernel modules, but things have gotten so bad that I have had to resort to restarting Network Manager and alternating with removing and loading the rtl8821ae kernel module. This barely works any longer and I am repeatedly asked for the network password, even though the Plasma Network Manager widget clearly shows that the password is stored. I read somewhere that one must restart it twice (a reason for why it fails the first time was given and why it works on the second try, but I don't recall what it was), so I have done this, having appended @Oden1's int_clear=0 solution. Amazingly, once I get past the double restarts (a game of trying to beat it before it asks for the already known password), this really does work! Nevertheless, there are still some disconnection problems, but they are drastically reduced.

pgueckel commented May 7, 2017

I now run the 4.11.0-1.fc26.x86_64 kernel. I don't know if anything changed in the kernel modules, but things have gotten so bad that I have had to resort to restarting Network Manager and alternating with removing and loading the rtl8821ae kernel module. This barely works any longer and I am repeatedly asked for the network password, even though the Plasma Network Manager widget clearly shows that the password is stored. I read somewhere that one must restart it twice (a reason for why it fails the first time was given and why it works on the second try, but I don't recall what it was), so I have done this, having appended @Oden1's int_clear=0 solution. Amazingly, once I get past the double restarts (a game of trying to beat it before it asks for the already known password), this really does work! Nevertheless, there are still some disconnection problems, but they are drastically reduced.

@gyuris

This comment has been minimized.

Show comment
Hide comment
@gyuris

gyuris Jul 16, 2017

My distro is Ubuntu 17.04.
Unit is Lenovo IdeaPad 700-15
Chipset and driver is:

02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8821AE 802.11ac PCIe Wireless Network Adapter [10ec:8821]
	Subsystem: Lenovo RTL8821AE 802.11ac PCIe Wireless Network Adapter [17aa:a814]
	Kernel driver in use: rtl8821ae

The workaround for me is running 4.9.13 kernel. Everything after that is wrong or worse. I tested also 4.12.2. I need to reset the driver with command mentioned above sometimes (2 or 3 times per day):

sudo modprobe -r rtl8821ae && sudo modprobe rtl8821ae int_clear=0

wireless-info.txt (4.9.13)
wireless-info.txt (4.12.2)

gyuris commented Jul 16, 2017

My distro is Ubuntu 17.04.
Unit is Lenovo IdeaPad 700-15
Chipset and driver is:

02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8821AE 802.11ac PCIe Wireless Network Adapter [10ec:8821]
	Subsystem: Lenovo RTL8821AE 802.11ac PCIe Wireless Network Adapter [17aa:a814]
	Kernel driver in use: rtl8821ae

The workaround for me is running 4.9.13 kernel. Everything after that is wrong or worse. I tested also 4.12.2. I need to reset the driver with command mentioned above sometimes (2 or 3 times per day):

sudo modprobe -r rtl8821ae && sudo modprobe rtl8821ae int_clear=0

wireless-info.txt (4.9.13)
wireless-info.txt (4.12.2)

@hyaochn

This comment has been minimized.

Show comment
Hide comment
@hyaochn

hyaochn Jul 26, 2017

wireless-info.txt

Same issue here.
Lenovo y520. Ubuntu 17.04
Everytime drops, I have to type
sudo service network-manager restart

hyaochn commented Jul 26, 2017

wireless-info.txt

Same issue here.
Lenovo y520. Ubuntu 17.04
Everytime drops, I have to type
sudo service network-manager restart

@chilek

This comment has been minimized.

Show comment
Hide comment
@chilek

chilek Jul 29, 2017

Lenovo y520 Fedora 26 rtlwifi_new driver.
For me connection stability problem resolves:

# cat /etc/modprobe.d/rtl8821ae.conf 
options rtl8821ae int_clear=0 fwlps=0 ips=0

chilek commented Jul 29, 2017

Lenovo y520 Fedora 26 rtlwifi_new driver.
For me connection stability problem resolves:

# cat /etc/modprobe.d/rtl8821ae.conf 
options rtl8821ae int_clear=0 fwlps=0 ips=0
@pgueckel

This comment has been minimized.

Show comment
Hide comment
@pgueckel

pgueckel Aug 22, 2017

I was reading about int_clear and it got me thinking about msi. Why had I dismissed msi from consideration? I was stuck on thinking the problem was power save [scratches head].

I have been running the computer for a few hours and the only option I have in /etc/modprobe.d/rtl8821ae.conf is:

options msi=0

msi needs to be disabled to make wifi work.

[By the way, I am now using kernel-4.12.8-300.fc26.x86_64 from koji.]

pgueckel commented Aug 22, 2017

I was reading about int_clear and it got me thinking about msi. Why had I dismissed msi from consideration? I was stuck on thinking the problem was power save [scratches head].

I have been running the computer for a few hours and the only option I have in /etc/modprobe.d/rtl8821ae.conf is:

options msi=0

msi needs to be disabled to make wifi work.

[By the way, I am now using kernel-4.12.8-300.fc26.x86_64 from koji.]

@pgueckel

This comment has been minimized.

Show comment
Hide comment
@pgueckel

pgueckel Aug 23, 2017

Unfortunately, my assumption has not held. I think that there might be two issues, one being the msi setting and the other being the power saving. I have tried every possible combination of the power saving settings—ips, swlps and fwlps—that I can think of (without making a rigorous study of all of the possible combinations).

I have also expanded the msi issue, if it really is a separate case, so my options have now expanded, but there is still no lasting solution:

options fwlps=0 msi=0 disable_watchdog=1 int_clear=0

What seems to work works for a little while and then the same syndrome begins anew.

pgueckel commented Aug 23, 2017

Unfortunately, my assumption has not held. I think that there might be two issues, one being the msi setting and the other being the power saving. I have tried every possible combination of the power saving settings—ips, swlps and fwlps—that I can think of (without making a rigorous study of all of the possible combinations).

I have also expanded the msi issue, if it really is a separate case, so my options have now expanded, but there is still no lasting solution:

options fwlps=0 msi=0 disable_watchdog=1 int_clear=0

What seems to work works for a little while and then the same syndrome begins anew.

@chilek

This comment has been minimized.

Show comment
Hide comment
@chilek

chilek Aug 24, 2017

@pgueckel did you try all of you described with lwfinger rtlwifi?

chilek commented Aug 24, 2017

@pgueckel did you try all of you described with lwfinger rtlwifi?

@pgueckel

This comment has been minimized.

Show comment
Hide comment
@pgueckel

pgueckel Aug 24, 2017

I cannot make sense of your question @chilek
I tried int_clear=0 fwlps=0 ips=0, but not by themselves, yet. I have given up on msi being a culprit, despite initial hopefulness. Currently, I have:

options fwlps=0 disable_watchdog=1 int_clear=0

This morning, that is working very well, but these same options last night gave me nothing but dropped connections every 1-2 minutes.

Is there somewhere where I can set the timeout so that the network doesn't disconnect right away, when the signal strength varies? I notice that the indicator (NetworkManager) sometimes shows 4 or 5 bars, typically only shows 3 bars and, just before the connection is dropped, will suddenly show 0 bars—and this while the signal strength of the wifi router has not even changed! Both my phone and blueray player indicate the highest signal strength and they connect without issue.

pgueckel commented Aug 24, 2017

I cannot make sense of your question @chilek
I tried int_clear=0 fwlps=0 ips=0, but not by themselves, yet. I have given up on msi being a culprit, despite initial hopefulness. Currently, I have:

options fwlps=0 disable_watchdog=1 int_clear=0

This morning, that is working very well, but these same options last night gave me nothing but dropped connections every 1-2 minutes.

Is there somewhere where I can set the timeout so that the network doesn't disconnect right away, when the signal strength varies? I notice that the indicator (NetworkManager) sometimes shows 4 or 5 bars, typically only shows 3 bars and, just before the connection is dropped, will suddenly show 0 bars—and this while the signal strength of the wifi router has not even changed! Both my phone and blueray player indicate the highest signal strength and they connect without issue.

@pepa65

This comment has been minimized.

Show comment
Hide comment
@pepa65

pepa65 Sep 9, 2017

He says here he's been building from this repo here: #235 (comment)

pepa65 commented Sep 9, 2017

He says here he's been building from this repo here: #235 (comment)

@silgon

This comment has been minimized.

Show comment
Hide comment
@silgon

silgon Sep 13, 2017

@chilek answer is a nice workaround, at least for the most of the uses. However, when you download a file, the speed continues to fluctuate more that it should. Also when tested with pinging a domain, there are mini spikes of slow connectivity (but not as slow as before).

silgon commented Sep 13, 2017

@chilek answer is a nice workaround, at least for the most of the uses. However, when you download a file, the speed continues to fluctuate more that it should. Also when tested with pinging a domain, there are mini spikes of slow connectivity (but not as slow as before).

@djhogan

This comment has been minimized.

Show comment
Hide comment
@djhogan

djhogan Sep 13, 2017

@pepa65 @pgueckel sorry, I thought this was a different repo

djhogan commented Sep 13, 2017

@pepa65 @pgueckel sorry, I thought this was a different repo

@draskolnikova

This comment has been minimized.

Show comment
Hide comment
@draskolnikova

draskolnikova Oct 17, 2017

Sorry for jump in, I am using FC26 and stay using kernel 4.12.14-300.fc26.x86_64 for stability using options rtl8821ae int_clear=0 on modprobe options. Have tried using latest kernel 4.13.5-200.fc26.x86_64 but it's unstable.

draskolnikova commented Oct 17, 2017

Sorry for jump in, I am using FC26 and stay using kernel 4.12.14-300.fc26.x86_64 for stability using options rtl8821ae int_clear=0 on modprobe options. Have tried using latest kernel 4.13.5-200.fc26.x86_64 but it's unstable.

@christianmtr

This comment has been minimized.

Show comment
Hide comment
@christianmtr

christianmtr Oct 20, 2017

I just comment in other issue that my connection works fine on Ubuntu Mate 16.04.

christianmtr commented Oct 20, 2017

I just comment in other issue that my connection works fine on Ubuntu Mate 16.04.

@gyuris

This comment has been minimized.

Show comment
Hide comment
@gyuris

gyuris Nov 13, 2017

Today I run Ubuntu 17.10 on new 4.14 kernel. WIFI works without any problem :-).
wireless-info.txt

gyuris commented Nov 13, 2017

Today I run Ubuntu 17.10 on new 4.14 kernel. WIFI works without any problem :-).
wireless-info.txt

@matchaniat

This comment has been minimized.

Show comment
Hide comment
@matchaniat

matchaniat Nov 13, 2017

@gyuris I think it's thanks to this commit: torvalds/linux@b8b8b16

matchaniat commented Nov 13, 2017

@gyuris I think it's thanks to this commit: torvalds/linux@b8b8b16

@pgueckel

This comment has been minimized.

Show comment
Hide comment
@pgueckel

pgueckel Nov 16, 2017

@matchaniat @lwfinger

I resorted to buying a cable and have not used wifi all summer, as I had gotten so frustrated by the unusable connection. I upgraded to Fedora 27β when it came out about a month ago and gave wifi another try: it was worse than ever!

The new commit sounds REALLY convincing!!!

Which kernel will be the one to get it? Will it be backported to other kernels? When will it hit the fedora repo kernels?

pgueckel commented Nov 16, 2017

@matchaniat @lwfinger

I resorted to buying a cable and have not used wifi all summer, as I had gotten so frustrated by the unusable connection. I upgraded to Fedora 27β when it came out about a month ago and gave wifi another try: it was worse than ever!

The new commit sounds REALLY convincing!!!

Which kernel will be the one to get it? Will it be backported to other kernels? When will it hit the fedora repo kernels?

@nikolas

This comment has been minimized.

Show comment
Hide comment
@nikolas

nikolas Nov 16, 2017

I was having this issue too, and the b8b8b16 commit didn't resolve it for me on my Lenovo Ideapad 320-15ABR laptop. For anyone still having trouble with this, try turning off ASPM. See the thread here:

https://marc.info/?l=linux-wireless&m=150994142316118&w=2

I had to actually remove the enable_aspm() call in the driver to get this working properly.

nikolas commented Nov 16, 2017

I was having this issue too, and the b8b8b16 commit didn't resolve it for me on my Lenovo Ideapad 320-15ABR laptop. For anyone still having trouble with this, try turning off ASPM. See the thread here:

https://marc.info/?l=linux-wireless&m=150994142316118&w=2

I had to actually remove the enable_aspm() call in the driver to get this working properly.

@meowsus

This comment has been minimized.

Show comment
Hide comment
@meowsus

meowsus Nov 24, 2017

I too am running Ubuntu 17.10 with the newest kernel and I've noticed a bit more reliability. Oddly, though, it's only stable when I run my connection through wpa_cli.

meowsus commented Nov 24, 2017

I too am running Ubuntu 17.10 with the newest kernel and I've noticed a bit more reliability. Oddly, though, it's only stable when I run my connection through wpa_cli.

@kladier

This comment has been minimized.

Show comment
Hide comment
@kladier

kladier Dec 15, 2017

Same problem for me for a while.
Are you sure it's a problem of rtl8821ae driver and not due to NetworkManager ?

kladier commented Dec 15, 2017

Same problem for me for a while.
Are you sure it's a problem of rtl8821ae driver and not due to NetworkManager ?

@lwfinger

This comment has been minimized.

Show comment
Hide comment
@lwfinger

lwfinger Dec 15, 2017

Owner

That is a very good question. Using openSUSE Tumbleweed with a 4.14 kernel and NetworkManager, the device is rock solid. Performance is sometimes low, but the connection never drops.

Owner

lwfinger commented Dec 15, 2017

That is a very good question. Using openSUSE Tumbleweed with a 4.14 kernel and NetworkManager, the device is rock solid. Performance is sometimes low, but the connection never drops.

@nikolas

This comment has been minimized.

Show comment
Hide comment
@nikolas

nikolas Dec 15, 2017

I'm using Debian with XFCE. I'm not using NetworkManager.

nikolas commented Dec 15, 2017

I'm using Debian with XFCE. I'm not using NetworkManager.

@lwfinger

This comment has been minimized.

Show comment
Hide comment
@lwfinger

lwfinger Dec 15, 2017

Owner

XFCE is a desktop, The critical user code is the network control software. What one are you using? The problem report was with wicd, and the problem went away when the user switched to NetworkManager.

Owner

lwfinger commented Dec 15, 2017

XFCE is a desktop, The critical user code is the network control software. What one are you using? The problem report was with wicd, and the problem went away when the user switched to NetworkManager.

@nikolas

This comment has been minimized.

Show comment
Hide comment
@nikolas

nikolas Dec 15, 2017

I have all that disabled - I'm not using NetworkManager or wicd. I tried wicd once to see if that solved my problem, but it didn't, so I uninstalled it. I'm configuring my network through debian's standard configuration files in /etc/network/interfaces.d/, via systemd commands like service networking restart, which control the interface with ifup and ifdown.

nikolas commented Dec 15, 2017

I have all that disabled - I'm not using NetworkManager or wicd. I tried wicd once to see if that solved my problem, but it didn't, so I uninstalled it. I'm configuring my network through debian's standard configuration files in /etc/network/interfaces.d/, via systemd commands like service networking restart, which control the interface with ifup and ifdown.

@pgueckel

This comment has been minimized.

Show comment
Hide comment
@pgueckel

pgueckel Dec 16, 2017

@lwfinger et al.

I loaded fedora kernel 4.14.6-300.fc27.x86_64 today. I disconnected the wired connection and tried out the wireless, albeit only for about 30 minutes so far, but I am pleasantly surprised: I have had no dropped connection occurrences! I am so optimistic that I think it has finally been resolved.

If problems resume, I will report here.

pgueckel commented Dec 16, 2017

@lwfinger et al.

I loaded fedora kernel 4.14.6-300.fc27.x86_64 today. I disconnected the wired connection and tried out the wireless, albeit only for about 30 minutes so far, but I am pleasantly surprised: I have had no dropped connection occurrences! I am so optimistic that I think it has finally been resolved.

If problems resume, I will report here.

@kladier

This comment has been minimized.

Show comment
Hide comment
@kladier

kladier Dec 17, 2017

@nikolas which kernel version ?

At each time you upgrade your kernel, you have to rebuild rtlwifi_new and modprobe -r rtl8821ae && modprobe rtl8821ae

kladier commented Dec 17, 2017

@nikolas which kernel version ?

At each time you upgrade your kernel, you have to rebuild rtlwifi_new and modprobe -r rtl8821ae && modprobe rtl8821ae

@nikolas

This comment has been minimized.

Show comment
Hide comment
@nikolas

nikolas Dec 17, 2017

@kladier I'm on kernel 4.14.7.

Interestingly, with the same configuration on kernel 4.15.0-rc2 and 4.15.0-rc3, I am getting frequent disconnects.

nikolas commented Dec 17, 2017

@kladier I'm on kernel 4.14.7.

Interestingly, with the same configuration on kernel 4.15.0-rc2 and 4.15.0-rc3, I am getting frequent disconnects.

@pgueckel

This comment has been minimized.

Show comment
Hide comment
@pgueckel

pgueckel Dec 24, 2017

Reported issue is resolved.

pgueckel commented Dec 24, 2017

Reported issue is resolved.

@pgueckel pgueckel closed this Dec 24, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment