On 01/22/2018 04:42 PM, rysiek wrote:
Hey all,
R4.0 rc3 used to work pretty well, but with recent updates (yes, I have
testing repos enabled), I started having some serious issues around Suspend-
to-RAM:
1. Suspend-to-RAM does not work reliably
When trying to suspend for the first time after a full reboot, the screen goes
blank for a few seconds and then immediately I am greeted with the lock
screen. The system does not suspend at all.
After unlocking the screen and trying again, system suspends to RAM, but after
wake-up the screen is *not* locked.
This happens on other systems with R4, too. But I think the reliability
has gone up since rc1, especially if you switch to kernel 4.14.13.
Also, try adding your wifi drivers to
/rw/config/suspend-module-blacklist. In my case the drivers are
'iwlwifi' and 'iwldvm'.
2. No networking after suspend
After suspend-to-RAM (even unsuccessful, like the first scenario described
above), the system completely loses networking; sys-net becomes unresponsive
(and with it, the NetworkManager applet), restarting it does not seem to work,
it is also impossible to start a terminal in sys-net.
See above, especially the blacklist tip.
3. USB mouse becomes unusable
After suspend-to-RAM (again, including the first scenario from the top of this
e-mail), the USB mouse becomes unusable, as if the system was not aware it is
plugged in. Unplugging it and plugging it back in does not solve the issue.
If you're using sys-usb, the same issues that apply to network cards
(above) may apply to USB.
The only way to fix these is to reboot the machine.
That used to be the case for me. Since updating dom0 and templates with
the Qubes testing repositories, I am at least able to kill sys-net and
restart it in a working state. Of course, its wise to backup before
trying out updates from 'testing' in case your system doesn't work with
them.
--
Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/15b1b1f4-d61b-834a-fce7-2049afdc630b%40posteo.net.
For more options, visit https://groups.google.com/d/optout.
