@DanNOG Funny, I was just about to write here that the arguments were causing problems for me. I had some weird CPU lockups, which I intuited that they might be caused by those args. When I removed them, things went fine. My wifi works fine as well. In fact, it seems some of the latency issues have lessened as well but I might be hallucinating.
But at any rate, if the args work for you, I am glad.
@joekamprad Ooooh, I seem to recall I have searched the AUR for this package and found nothing, but I might have only dreamt it then .
@DanNOG Heya, sorry for the delay, I had some stuff iRL. Anyways, Arch Linux (and thus Antergos) has an lts (long-term stable) kernel, that is basically an older version of the kernel that nontheless keeps getting security and bugfix updates, and is slowly getting updated (mine switched from 4.9.35-1-LTS to 4.9.36-1-LTS recently).
If you don’t have it already installed, you should install the linux-lts and linux-lts-headers via pacman or pamac, and if you use proprietary nvidia drivers (probably the same shizzle for AMD drivers but I don’t use AMD GPU) you should install nvidia-lts as well (it will replace the current nvidia drivers).
Afterwards, when you boot, grub should look something like
- Advanced options for Antergos
- Other shizzle like Windows Boot Loader etc.
I am only paraphrasing here, don’t remember the exact menu titles. You should go into Advanced options, and there you’ll have something like
- Antergos (fallback)
- Antergos (LTS kernel)
- Antergos (LTS kernel, fallback)
and you should choose the LTS kernel as boot option.
Note the following things:
- I don’t think it actually makes the difference, but certainly doesn’t hurt, make a file
and into it write
options rtl8821ae ips=0 fwlps=0 swlps=1 disable_watchdog=1 int_clear=0
- It seems to me that every time there is a kernel update, you need to recompile the driver you have downloaded from the github repo. So every time you receive a kernel update do
sudo modprobe -r rtl8821ae make && sudo make install sudo modprobe rtl8821ae
all while your terminal is open in the rtlwifi_new folder. Based on the files there and the make and make install output, I think compiling will take the currently active kernel into account, but I am not sure. At any rate, even the update to the LTS kernel borked my wifi again, but doing this restored it.
I dunno if the drivers in the repo work with the latest kernel or not, I have only tried with the LTS kernel after my recent fiasco with the latest kernel, but I do would like to say that after the third bleeding edge kernel update, I didn’t even try recompiling, at the time I didn’t realize that would help. But it should, by all means, work with the LTS kernel.
This solution is not perfect, I still get occasional 9-10 sec drops in the connection, but unlike how it was previously, it won’t disconnect me from the network or make the network manager go crazy. This drop is only visible in the sense that sometimes pages will take long to load and if you do a ping to some website you will occasionally see like 4-5 packets have like 9-10k ms latencies.
@DanNOG Did you also try it with
sudo modprobe rtl8821ae ips=0 fwlps=0 swlps=1 disable_watchdog=1 int_clear=0
? I kept having issues though, which I could not fix after a while, so I ended ué using the LTS kernel. Which did work for me, but I also had to download the rpo and run it with the parameters I have given. But it does work now.
@kellyhose201 If the gnome screenlocker works for you right now, then disable it to potentially avoid conflict.
You need to download the following packages if you don’t already have them:
$ sudo pacman -S scrot i3lock xautolock
Scrot is a screenshot-taking utility, i3lock is a screenlocking utility of the tiling window manager i3 (but it works without i3 too!) and xautolock is a tool for automatic screenlocking.
What you need to do now is to write a shell script with the following in it (for example place it in your home folder for now) (Note: In case you are unfamiliar, you must NOT type out the $ signs, I just use them in this post to indicate script):
$ scrot /tmp/screenshot.png
$ convert /tmp/screenshot.png -blur 0x5 /tmp/screenshotblur.png
$ i3lock -i /tmp/screenshotblur.png
Now save this script with some name that doesn’t conflict with other apps (I named it blurlock, it should be fine) and do
$ sudo cp blurlock /bin
(run this command only if you are in the same directory blurlock is now, otherwise you need to give a path for the source file too)
This command will move the shell script “blurlock” to the /bin folder, which means you can execute it without giving a full path. Try it out, open a terminal and type
Now your screen should look like your desktop but blurred. To exit the screen lock, you need to type your password and press enter. Note: There is no prompt to enter your password. You just need to type it. The locking app WILL however give feedback on your typing.
If you are satisfied with the blur effect, cool. If not, you can edit the “convert” part in the shell script. Or, if you don’t want to blur, then you can use a fixed image as the locking screen by omitting every command in the shell script except for the last one, but change the path to an image you’d like to use.
We are almost done, but we want the screen locking to happen automatically after a time. We will use xautolock for that.
In some less complicated desktop environment, this would be simpler but on gnome this will be more complicated.
Creat a file autolock.desktop in ~/.config/autostart (so that the path is ~/.config/autostart/autolock.desktop)
and put into that file the following (once again, no $):
$ [Desktop Entry]
$ Exec=xautolock -time 5 -locker blurlock
Then save the file. Btw, the “5” in the Exec xautlock… command means that autolocking will happen after 5 minutes of idle, modify it if you want.
Afterwards, this should show up in the Gnome Tweak Tools, in the startup applications pane. Set this on startup, logout then login.
Now, after 5 minutes of idle, i3lock should work.
Note: I haven’t tested the whole automatic startup thingy, I used to use this with i3, but running on startup is simpler there. I still use the script on Gnome, but only manually. If the startup thingy doesn’t work, write here and I’ll check it out.
I don’t particularily know the standard gnome locker (does it even work without gdm? It doesn’t for me), but if you are interested in a custom solution, write here and I’ll tell you how to whip up a nice screen-locking mechanism that does keep playing music (well, I tested with youtube, I don’t have music on my rig atm).
I have redownloaded the git repo (probably pointless) and recompiled the driver. I did
$ sudo modprobe -r rtl8821ae && sudo modprobe rtl8821ae ips=0 fwlps=0 swlps=1 disable_watchdog=1 int_clear=0
I have no idea what this does, but the situation seems marginally better. With that said, I am running a pinging session of a website in a terminal and periodically I see the ping time jump up to 8-9000 ms, though the network manager doesn’t seem to disconnect me anymore.
I guess I could roll back the kernel update and wait a bit with updating, but I am disappoint.
There was a kernel upgrade today, and yup, it’s doing it again. I simply reloaded the module and I’ll see how it goes. The git repo was updated 2 months ago, so unless the reloading fixes it again, I’ll be fucked till Mr. Finger decides to update the repo.
@eleius I am a linux newb, so I don’t actually know. However I suspect nothing will happen and the kernel will keep using the driver. If that fails, I guess one can reload the kernel module. If the kernel upgrade would break the driver, then I assume Mr. Finger will update his repo.
Now, I don’t particularily understand git, but afaik it allows for dynamic updates, but because I had to make install, I’m not sure. With that said, in this case, probably redownloading the updated archive and then make installing would work fine.
Waiting for a more experienced user to confirm or deny.