I'm running on a T460s with NVMe storage (after market Samsung 950 Pro) and Intel 8260 wireless with relatively few problems. Here are a few notes on the settings and changes that were required to get things up and running. I haven't tested battery life in detail but the system did hold up for more than an hour while under somwhat heavy load.
BIOS These should be every changed setting, please update the list if they don't work for you, unfortunately when you reset the BIOS to defaults it doesn't reset most of the security settings. Be aware that resetting to defaults will clear the UEFI boot loader settings required to allow Qubes to boot. I wasn't able to recover from this and was forced to reinstall; I'm fairly certain that I could have fixed it with enough effort but as I was just working on getting qubes installed it was easier. Security > Secure Boot: Disabled Startup > UEFI Only with CSM Support: Yes Security > Security Chip : Discrete TPM or Disabled, Intel PTT prevents shutdown/standby Security > Virtualization > Virt, VT-d: Enabled Security > Anti-Theft > Computrace : Disabled (This may not be mandatory) Qubes Installed with sys-usb enabled Updated both dom0 and guest kernel, dom0 for suspend, graphics and many other reasons, guest for Intel 8260 Wireless. sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable kernel sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable kernel-qubes-vm Switched all service VMs to debian 8 In order to support the Intel 8260 Wireless I had to enable the jessy-backports repo (including non-free) by adding the following to /etc/apt/sources.list: deb http://ftp.debian.org/debian jessie-backports main contrib non-free I was then able to install the latest firmware-iwlwifi package: sudo apt-get -t jessie-backports install firmware-iwlwifi With this and the guest kernel wireless works properly. The firmware updates and drivers date from around Novemeber of 2015 if you are using another distro. More than happy to help anyone who has questions, thanks for the amazing secure OS. -JohnF On Sun, May 29, 2016 at 7:34 PM, Marek Marczykowski-Górecki <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On Thu, May 26, 2016 at 08:25:48PM -0700, [email protected] > wrote: >> 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). > > Was that patch backported also to 4.4.11? > >> 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. > > Yes, ignore it. In fact it is already commented out in series.conf file > for some time. > >> - 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. > > Are those artifacts across the whole screen, or only particular windows? > >> - 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? > > Generally the rule is "enable all drivers are modules". > >> - 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 >> > > > - -- > Best Regards, > Marek Marczykowski-Górecki > Invisible Things Lab > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iQEcBAEBCAAGBQJXS3yPAAoJENuP0xzK19cs388H/jpa1S1hCKYp965Srdij+1OC > dPNBWL6jRr7zWlel38vyCaAbhB1/TN8C7NCkthz6B423hsN2+GE1PD/lK3bQe+ia > Xif7tzWQwNAhc7KOi8DNyftWUPdc4NZ1AhcT8+Cav5abACJhkzwS6uYI9RNDWiSG > o6+CP5K6aNAuOpruLjKbJImT/qr7pKu8R9Ry4uPeJTCC+tbhLANgwRODTEWzJPEa > jDZlJfUivjXDGKNumwoA2pdSghGX9aJJN3x+bfjxKatJs1NAmDOHUTastlAqIzUF > a1CMqI2jZflK4WTQ1A2oEXzel+dT+a0hmrjcOQIlOijrYdmEp2pDmveCF8DK/xg= > =96Y/ > -----END PGP SIGNATURE----- > > -- > 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/20160529233439.GC2191%40mail-itl. > For more options, visit https://groups.google.com/d/optout. -- 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/CAAafysGSGH0aaJjJ1fLW2CgXgOZYsukrNVgp%2BLdSGP%3Dact19pg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
