qubes 3.2 flaw with wifi stoping to work after power safe mode (laptop lid closed)

[ludwig jaffe]

Hi, I bought a new cheap laptop, Lenovo 110 that uses an SOC with i3.
The wifi is
00:01.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821AE 802.11ac PCIe Wireless Network Adapter

After a while of using wifi, it just stops to work and sometimes reconnecting the wifi works sometimes one need to reboot the net-vm and sometimes this also does not help and one needs to reboot the whole machine in order to get wifi working again.
I saw such flaws once with kali but never investigated too much on it.

Any ideas on this problem?

[Andrew Morgan]

Would it be similar to this issue?
https://groups.google.com/d/msg/qubes-users/LkP-6ORGwME/AQLyuqvnCAAJ

Andrew Morgan

[Unman]

It's a generic problem with those cheap realtek devices and the linux
drivers. It's not Qubes specific.
If you google for the problem you can find a variety of proposed
solutions. I've tried some (most) of them with little success - but a
clean install of buster seems rock solid, and stretch seems ok too.
Try a stretch netvm and see if that helps.

[ludwig jaffe]

I had the Problem with Kali and Intel WiFi.

--
Send from mobile phone with autocorrection / autofill. Blame my phone for typos.

[Yuraeitha]

In most cases, it should be relatively easy to fix.
Here is the official Qubes guide to this very problem https://www.qubes-os.org/doc/wireless-troubleshooting/

I can rapport it certainly worked for me, having had exact same issue as you describe. No more loose of internet connection after suspend/hibernate, quick internet after suspend or hibernate, and no more dom0 kernel panic reboots out of nowhere.

I also discovered if you keybind the rmmod/modprobe wifi module process in addition to putting them on the blacklist as described in the list, you can force your network to quickly regain network, if it happens to be slow to connect or the discover is slow to become available when suddenly in range. But mostly the blacklist is sufficient enough.

Even if it's happening outside hibernate/suspend, a keybind to the rmmod/modprobe process can in many cases quickly fix it, without having to type it manually or reboot your entire system. I never have to reboot anymore, having been in your shoes once. Hopefully this works for you too.

[Yuraeitha]

On Wednesday, November 8, 2017 at 8:42:12 PM UTC, ludwig jaffe wrote:

Here's the keybind
"qvm-run sys-net 'bash wifi-resume' "
Add it in Qubes menu --> Systems Tools --> Keyboard --> Application Shortcuts.

Then in your wifi-resume script, throw it in your sys-net home folder.
Write something akin to in the script, albeit with your own wifi hardware module names.

sudo rmmod iwlmvm
sudo rmmod iwlwifi
sudo modprobe iwlwifi
sudo modprobe iwlmvm

But try the blacklisting first before making a keybind, since the automatic process is easier than a keybind, and it may be sufficient. The keybind is just for extra control or in situations it was not caused by suspend/hibernate.