Hi, On Sun, Jan 15, 2017 at 10:24:01PM +0100, Robin Schneider wrote: > Adding to the reports about the Thinkpad X1 Carbon 4th gen (20FB), here are my > experiences with the ThinkPad X1 Yoga 20FQ005UGE: another skylake system here…
> ### Kernel update
the default 4.4.38-11 kernel worked mostly nicely for me, until it suddenly
went into suspend and wouldnt wake up anymore…
so I switched to 4.8.12-12 like this:
> `qubes-dom0-update --enablerepo=qubes-dom0-unstable kernel` and `dnf upgrade
> kernel` worked!
which gave me somewhat higher battery life and so far no sudden suspend. But:
> WLAN works after installing firmware-iwlwifi in Debian 9. The only problem is
> that almost all times after resuming from S3, the net VM needs to be restarted
> to get wlan working again. The following is logged in sys-net:
I have the same problem with WLAN :/ After suspend I need to restart sys-net,
which requires shutting down all VMs using it, so that's pretty super annoying
:/
My sys-net VM still runs fedora-23…
> [14543.999216] e1000e: eth0 NIC Link is Down
> [14548.117695] e1000e: eth0 NIC Link is Down
> [14548.314301] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> [23785.273315] e1000e: eth0 NIC Link is Down
> [23785.307940] wlan0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice
> (Reason: 3=DEAUTH_LEAVING)
> [23786.152843] Freezing user space processes ... (elapsed 0.001 seconds) done.
> [23786.154342] Freezing remaining freezable tasks ... (elapsed 0.000 seconds)
> done.
> [23786.155692] PM: freeze of devices complete after 0.347 msecs
> [23786.155697] suspending xenstore...
> [23786.155764] PM: late freeze of devices complete after 0.065 msecs
> [23786.171420] PM: noirq freeze of devices complete after 15.649 msecs
> [23786.172443] xen:grant_table: Grant tables using version 1 layout
> [23786.172443] PM: noirq thaw of devices complete after 0.708 msecs
> [23786.172443] PM: early thaw of devices complete after 0.086 msecs
> [23786.172846] PM: thaw of devices complete after 0.407 msecs
> [23786.172846] Restarting tasks ... done.
> [23809.722077] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> [23810.002035] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> [23810.006535] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [23810.008657] iwlwifi 0000:00:01.0: L1 Enabled - LTR Enabled
> [23810.010616] iwlwifi 0000:00:01.0: L1 Enabled - LTR Enabled
> [23815.012114] iwlwifi 0000:00:01.0: Failed to load firmware chunk!
> [23815.012150] iwlwifi 0000:00:01.0: Could not load the [0] uCode section
> [23815.012182] iwlwifi 0000:00:01.0: Failed to start INIT ucode: -110
> [23815.012208] iwlwifi 0000:00:01.0: Failed to run INIT ucode: -110
> [23815.042145] iwlwifi 0000:00:01.0: L1 Enabled - LTR Enabled
> [23815.044004] iwlwifi 0000:00:01.0: L1 Enabled - LTR Enabled
> [23820.043139] iwlwifi 0000:00:01.0: Failed to load firmware chunk!
> [23820.043194] iwlwifi 0000:00:01.0: Could not load the [0] uCode section
> [23820.043230] iwlwifi 0000:00:01.0: Failed to start INIT ucode: -110
> [23820.043249] iwlwifi 0000:00:01.0: Failed to run INIT ucode: -110
> [23820.049489] iwlwifi 0000:00:01.0: L1 Enabled - LTR Enabled
> [23820.051445] iwlwifi 0000:00:01.0: L1 Enabled - LTR Enabled
> [23825.054064] iwlwifi 0000:00:01.0: Failed to load firmware chunk!
> [23825.054078] iwlwifi 0000:00:01.0: Could not load the [0] uCode section
> [23825.054088] iwlwifi 0000:00:01.0: Failed to start INIT ucode: -110
> [23825.054093] iwlwifi 0000:00:01.0: Failed to run INIT ucode: -110
> [23835.017335] iwlwifi 0000:00:01.0: L1 Enabled - LTR Enabled
> [23835.019072] iwlwifi 0000:00:01.0: L1 Enabled - LTR Enabled
basically the same with f23:
[ 1656.511666] iwlwifi 0000:00:01.0: L1 Enabled - LTR Enabled
[ 1656.514413] iwlwifi 0000:00:01.0: L1 Enabled - LTR Enabled
[ 1661.517205] iwlwifi 0000:00:01.0: Failed to load firmware chunk!
[ 1661.517248] iwlwifi 0000:00:01.0: Could not load the [0] uCode section
[ 1661.517283] iwlwifi 0000:00:01.0: Failed to start INIT ucode: -110
[ 1661.517308] iwlwifi 0000:00:01.0: Failed to run INIT ucode: -110
[ 1661.522957] iwlwifi 0000:00:01.0: L1 Enabled - LTR Enabled
[ 1661.524946] iwlwifi 0000:00:01.0: L1 Enabled - LTR Enabled
[ 1666.527193] iwlwifi 0000:00:01.0: Failed to load firmware chunk!
[ 1666.527240] iwlwifi 0000:00:01.0: Could not load the [0] uCode section
[ 1666.527292] iwlwifi 0000:00:01.0: Failed to start INIT ucode: -110
[ 1666.527326] iwlwifi 0000:00:01.0: Failed to run INIT ucode: -110
and then I noted this:
[user@sys-net ~]$ uname -a
Linux sys-net 4.4.38-11.pvops.qubes.x86_64 #1 SMP Mon Dec 12 23:24:39 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
while uname -a in dom0 shows the 4.8.12-12.pvops.qubes.X86_64 kernel.
Could this be related? And how do I upgrade the kernel in sys-net?
"rpm -qa | egrep (kernel|linux)" doesnt show it installed, how come it's
4.4 and not 4.8?
Is the solution to upgrade the iwl$Bla-firmware package in sys-net?
Shall I file a github issue?
--
cheers,
Holger
--
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/20170202144453.GB22207%40layer-acht.org.
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Digital signature
