I also have a t460s and encountered many of the problems above.  I updated the 
qubes patches (excluding pvusb) to apply against kernel v4.5.2 and tossed in an 
out-of-tree patch for Skylake.  Bumping to 4.5.5 didn't require any further 
patch-wrangling (except that the Skylake patch had been merged in the meantime).

I've been running the result for a few days and everything seems to be working 
well.

https://github.com/patientnil/qubes-linux-kernel/tree/devel-4.5

Notes:

- The pvusb patch looks the trickiest to port, and the associated tools show 
that scary experimental warning. I didn't pursue it, it's sitting there 
commented out.

- Sound, trackpoint buttons, wifi, suspend all work (though I haven't tried 
reenabling TPM yet).  

- I get occasional screen artifacting (horizontal lines) but I am using the 
qubes-R3.1 display packages - before a reinstall I had better luck with updates 
in the unstable repo.

- While updating the kernel config, I had some sort of snafu, and I later had 
to go reenable a bunch of fundamental things like IP_MASQ.  The config should 
be reexamined (I'm planning to pare it down to just the things I need).  If 
this was to be merged to the main tree it should be redone.  Presumably there 
are rules of some sort as to what to include?

- I'm not sending a pull request since Marek mentioned the preference for 
longterm kernels - but perhaps the updated can be useful anyway if the next 
target is similar enough to 4.5?  

- If there's interest I could post RPMs and could possibly update this 
occasionally to keep up with 4.5 (which seems to be the sweet spot for Skylake 
right now)

-tom

-- 
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/eebdd41a-f746-4be6-a357-de936b85db43%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to