Installation Problems: Dell XPS 13 (9350) +1

[R.B.]

Hi there,

I managed to install Qubes-OS 3.1 rc1 on my XPS 13 (9350).

What I did:
Enable boot in Legacy mode.
Start the install media from an USB storage device. This was a SD-card
in a USB card reader in my case.
Note that starting from an SDcard in the laptop won't work, because the
boot images don't look for mmcblk0 devices (Ubuntu does however).

Select Install Qubes-OS and press TAB to edit the boot-config.
Add i915.enable_ips=0 i915.preliminary_hw_support=1 to the kernel options.
Press enter to boot.

Once you see the pretty screen, press escape before the screen freezes.
This way you can follow whats happening in the background.
You'll see anaconda starting. Happy installing ;-)

Then you reboot..... Which you might need to help a hand....
This is where I am stuck in a grub rescue stub. It cannot find the device.
Is the supplied grub too old for the M.2 PCIe SSD as in nvme0n1p1? If I
do an 'ls' it just gives me (hd0) and nothing else.

So, I managed to install it but not to use it (yet) ;-)

I did try to do a grub-install from an Ubuntu Live image:
mount /dev/nvme0n1p1 /mnt/tmp
grub-install --boot-directory=/mnt/tmp /dev/nvme0n1

It does give me grub and I get to see the whole disk, but the config
(grub.cfg) is somehow missed...

Thank you and I hope this helps others too.


R.B.

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Have you tried in UEFI mode? 3.1 have support for it, and then UEFI is
responsible for accessing your disk, so it may be better.

- --
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

iQEcBAEBCAAGBQJWfx2gAAoJENuP0xzK19cs20cH/02BFtmw1VCoBzzw9HJqVrYx
RFL1XQAnLJGOJ9hF76icS3/Q3Y086XUCHh4wAxg5KmAw750QsIFBc/sdBXTBTTt4
S6BWw1w4t5Bc1KAB5Qdzkx6XHY6YX076FSB6cI2bSLnD47TrUmVERsQ/CXyEvanU
buFMJm6UWEuA2ucc09/ksygBicWKV4lWUQ8Xmyrt8+Bo3jE0/1FT4P/JJs3+Jqqo
CIrVJ5+Evuz8txagCfYhn1Uusg8S4k23fRy2Ugd/r6aYE7R78I5HxNvYfs3HFHPx
mA4OINMF9m54JUnxK1GfIHG2jyUUV8mbdsSkCgF+bBHcREbF0wFUiKE6cq/1WdY=
=ysAY
-----END PGP SIGNATURE-----

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

If the standard R3.1-rc1 image fails to boot in UEFI for you, try image
from here:
https://github.com/QubesOS/qubes-issues/issues/794#issuecomment-167327017

- --
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

iQEcBAEBCAAGBQJWfx4VAAoJENuP0xzK19cslQgIAJXW8WKYSO8fXChxmMF8cT2I
8AYuGnihnqlRse0XfP3U0euwTvaZOPTu3i2yzf7K5TR7aUYEnkFliRGAdyUKSK8z
pt0fq5XKu4YP/7cOQKt49EalXP0Beq5J9fBBBQe2KL5pAwkU6+7rI2qhxvz8y84E
PfwqDYjSNy+pScNRqd75iQQVdkaytJsGaAxFakgGreKELKVac+FF8DeFdbVfdnoX
LFhYPBN+3neIWbTC/KEmpSZcpyHp3rpv0nt1KoWW9u45nExkTZw1syJaNFbiLZIY
vzzW9c2TkjjCiJ2oVVFCPL6KKuR/n4IXE7auwkJjjA79RLkTbsIl+GJZFtfA8nU=
=OBUp
-----END PGP SIGNATURE-----

[R.B.]

On 12/27/2015 12:09 AM, Marek Marczykowski-Górecki wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On Sun, Dec 27, 2015 at 12:07:12AM +0100, Marek Marczykowski-Górecki wrote:
>> On Sat, Dec 26, 2015 at 10:59:50PM +0100, R.B. wrote:
>>> I managed to install Qubes-OS 3.1 rc1 on my XPS 13 (9350).
>>>
>>> What I did:
>>> Enable boot in Legacy mode.
>>> Start the install media from an USB storage device. This was a SD-card in a
>>> USB card reader in my case.
>>> Note that starting from an SDcard in the laptop won't work, because the boot
>>> images don't look for mmcblk0 devices (Ubuntu does however).
>>>
>>> Select Install Qubes-OS and press TAB to edit the boot-config.
>>> Add i915.enable_ips=0 i915.preliminary_hw_support=1 to the kernel options.
>>> Press enter to boot.

>> Have you tried in UEFI mode? 3.1 have support for it, and then UEFI is
>> responsible for accessing your disk, so it may be better.
>
> If the standard R3.1-rc1 image fails to boot in UEFI for you, try image
> from here:
> https://github.com/QubesOS/qubes-issues/issues/794#issuecomment-167327017

Thank you for the informative link. I tried the image which booted fine
with EFI enabled. However, I get stuck on the moment anaconda is
started. Although it gives me no error, the screen goes blank with only
an unresponsive cursor at the top-left. I suspect it started the
installer on an non-existing display - on the ips....

I couldn't find a quick way to add a boot option at run-time in rEFIned,
like i was able in legacy mode.

For some reason, I managed to get a dmesg off of the laptop while
booting in legacy mode. Could still be useful. Especially the Invalid
opcode.

Regards,

R.B.

[R.B.]

On 12/27/2015 03:04 PM, R.B. wrote:
> On 12/27/2015 12:09 AM, Marek Marczykowski-Górecki wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>> On Sun, Dec 27, 2015 at 12:07:12AM +0100, Marek Marczykowski-Górecki
>> wrote:
>>> On Sat, Dec 26, 2015 at 10:59:50PM +0100, R.B. wrote:
>>>> Add i915.enable_ips=0 i915.preliminary_hw_support=1 to the kernel
>>>> options.

>>> Have you tried in UEFI mode? 3.1 have support for it, and then UEFI is
>>> responsible for accessing your disk, so it may be better.
>>
>> If the standard R3.1-rc1 image fails to boot in UEFI for you, try image
>> from here:
>> https://github.com/QubesOS/qubes-issues/issues/794#issuecomment-167327017
>

> I couldn't find a quick way to add a boot option at run-time in rEFIned,
> like i was able in legacy mode.

Hello Marek,

I'm new to UEFI, so I had something new to learn. I got the stuff going
by simply make an EFI partition on the USB stick for the EFI folder and
put the other files on a second partition. Editing the configfiles, to
point to the right partition and adding the i915 options was easy.

Unfortunately it didn't work. Neither the original image or the 20151226
image with rEFInd worked out. In both cases I got no anaconda.
Not sure what goes wrong here.

I did get the output from dmesg, by starting up in rescue mode. Just in
case someone can use it....


Regards,

R.B.

[R.B.]

On 12/28/2015 10:47 PM, R.B. wrote:
> On 12/27/2015 03:04 PM, R.B. wrote:
>> On 12/27/2015 12:09 AM, Marek Marczykowski-Górecki wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA256
>>>
>>> On Sun, Dec 27, 2015 at 12:07:12AM +0100, Marek Marczykowski-Górecki
>>> wrote:
>>>> On Sat, Dec 26, 2015 at 10:59:50PM +0100, R.B. wrote:
>>>>> Add i915.enable_ips=0 i915.preliminary_hw_support=1 to the kernel
>>>>> options.
>>>> Have you tried in UEFI mode? 3.1 have support for it, and then UEFI is
>>>> responsible for accessing your disk, so it may be better.
>>>
>>> If the standard R3.1-rc1 image fails to boot in UEFI for you, try image
>>> from here:
>>> https://github.com/QubesOS/qubes-issues/issues/794#issuecomment-167327017
>>>
>>
>> I couldn't find a quick way to add a boot option at run-time in rEFIned,
>> like i was able in legacy mode.
>

> Unfortunately it didn't work. Neither the original image or the 20151226
> image with rEFInd worked out. In both cases I got no anaconda.
> Not sure what goes wrong here.

Hello everyone,

I figured it might be a better idea to install under legacy and change
the boot method after the install attempt. At first I thought I could
get away with using the UEFI bootconfig from the installation medium,
but I couldn't make it fit. I would need to know:
- Which files are used in the EFI partition?
- How is the boot process setup? What calls what? And how?
- Maybe, a view in the files used in the boot partition in so far it
differs from the legacy boot configuration.
- Is the EFI image mounted? If so, how?

Ubuntu works on UEFI, but is no reference to Qubes-OS ;-)

Thanks

R. B.

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Generally it is hard to install UEFI system, not running in UEFI mode.
Mostly because running legacy mode you don't have access to UEFI
configuration, so can't register the system there.

That said, it is possible, having some UEFI compatible live system...

> I would need to know:
> - Which files are used in the EFI partition?

xen.efi
xen.cfg (check example from #794 ticket linked above)
vmlinuz
initramfs

> - How is the boot process setup? What calls what? And how?

You need to register xen.efi as boot application. Some BIOSes allow to
do that from configuration menu. If not, get some UEFI system and use
efibootmgr. Something like this (untested):

efibootmgr -c -d /dev/sda -p 1 -l '\EFI\qubes\xen.efi' -L Qubes

Then adjust boot order to have it as default (if you want).

> - Maybe, a view in the files used in the boot partition in so far it differs
> from the legacy boot configuration.
> - Is the EFI image mounted? If so, how?

If you install in legacy mode, by default it will not create EFI boot
partition. You need to take care of it yourself. It needs to be on GPT
partition table, partition type "EFI system", with vfat filesystem.
It is common to mount it in /boot/efi.

- --
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

iQEcBAEBCAAGBQJWhHEtAAoJENuP0xzK19csomwH/2M21EN0snuCHg1DKVDal3Ak
GKy7r3JkOoGXotQR0Pj/o0CwozvURBSYQjIFTg4nMLqWJ0A4SImxc5qMk82hqgor
m2/S40X50oRm+a4ThmAGONacySR7jPY4Qb1M//y+orEweRIsu4Vwh2MC69LGkWri
P7B5DxkvslCDsmrV8LYwe5KtvFEs2M/5PcdYXUziMq03j8VhE3XpasrOTJCLAR5r
KUmh3tUGokbCbI9CTQLpjsmzFBgNpP5Ne3NvLr1niZGuUQVAVpGgULDG2Xtmlacq
90fuuTvgaF8NPS7g3SOrC730GNwZ1QMyDex/LF339zufeX5B7N9VX1bY/G7Je8Y=
=cSuv
-----END PGP SIGNATURE-----

[R.B.]

On 12/31/2015 01:05 AM, Marek Marczykowski-Górecki wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>

> On Wed, Dec 30, 2015 at 09:11:27PM +0100, R.B. wrote:
>> Hello everyone,
>>
>> I figured it might be a better idea to install under legacy and change the
>> boot method after the install attempt. At first I thought I could get away
>> with using the UEFI bootconfig from the installation medium, but I couldn't
>> make it fit.

>> I would need to know:
>> - Which files are used in the EFI partition?
>
> xen.efi
> xen.cfg (check example from #794 ticket linked above)
> vmlinuz
> initramfs
>
>> - How is the boot process setup? What calls what? And how?
>
> You need to register xen.efi as boot application. Some BIOSes allow to
> do that from configuration menu.

Seems I got lucky with the XPS 13 9350 since it was very easy to
register new efi files from the BIOS.

>> - Maybe, a view in the files used in the boot partition in so far it differs
>> from the legacy boot configuration.
>> - Is the EFI image mounted? If so, how?
>
> If you install in legacy mode, by default it will not create EFI boot
> partition. You need to take care of it yourself. It needs to be on GPT
> partition table, partition type "EFI system", with vfat filesystem.
> It is common to mount it in /boot/efi.

Thank you for the directions.

I got it starting. I have a dualboot with Ubuntu, which enables me to
edit the start-up files from a persistent environment.

Unfortunately it hangs on various programs according to the NMI
watchdog: Xorg on one CPU and Systemd on the other.
looks like this needs to wait for a new kernel version.

I stole some extra boot parameters from a forum of archlinux:
elevator=noop pcie_aspm=force i915.enable_rc6=7 i915.enable_execlists=0
i915.enable_execlists=0 i915.enable_psr=1 i915.enable_fbc=1

Forum: https://bbs.archlinux.org/viewtopic.php?id=205147

Nothing worked. I'll have to wait for a next version or abuse another
Qubes machine that does work on this version and transfer the files from
there after an update. Hopefully with a 4.2+ kernel...

Anyone else have more luck with getting Qubes running on this laptop?

Thanks

R.B.

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I've just uploaded 4.3.3 kernel to qubes-dom0-unstable repo (for R3.1).
You can install it with:
sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable kernel

- --
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

iQEcBAEBCAAGBQJWim6GAAoJENuP0xzK19cst9cH/3bwxfLVX/r3C+TCwmGm04vN
rNbkLkxbHGAM1ineENYkkHgb97SUjI3KEbbykxVOl7GVDuHgTpgoi2xakYc+0klh
wFLJyOyfcEd1Y0zLhfMtjIFRN+57Q/hxbxd3ZX6WgVOqrNwVRug6SKpF7t13LsCc
ysoVARd19nAkPBtMCTJ7ik99x0X8GqAQnYi7FJN8WMUpyDBGiU32wps8LbiZlFod
mxMEXPtxlwSdlV6Zu3R/Nyh6pf3hUsIPj+wuliTHpeJ/CMlYsz+o2xpdDI3Ulwxl
O6tMSZI5iRWi1ivdHMaSCc4kv9vY8Hdkr5noN67AeHawHAnxksLBhzJNOtW7nB0=
=OJWS
-----END PGP SIGNATURE-----

[R.B.]

On 01/04/2016 02:07 PM, Marek Marczykowski-Górecki wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>

> I've just uploaded 4.3.3 kernel to qubes-dom0-unstable repo (for R3.1).
> You can install it with:
> sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable kernel

Unfortunately 4.2.8-8 is the highest I get.

Regards,

R.B.

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Yes, 4.3.3 was removed from there, because cause some problems. Details
in this thread:
https://groups.google.com/d/msgid/qubes-users/20160105032207.GL1101%40mail-itl

4.2.8 hopefully will also fix your problems.

- --
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

iQEcBAEBCAAGBQJWjYfEAAoJENuP0xzK19csSq8H/jtZkPdj5n7z/+eoz6LNGyK6
v5IA2vJmcs/utDZ908RBFRsriFne1a6lPukgjJ1IhF2cg4WfFgRl6AINGiH7mp5p
+r2PbIFFj2lhe8SMQ8U0g6OkinV1rqXe2gSlw8Ho6mzGx5gk5xn+aajhu6BdlhBv
PBl2luncYKlE7Z3G0UDvork3puIcbC1cyWt5yUD9MKPu86DmYphtEuK2lqqFXfGb
RCGlvdCodJiUWpavuOrFpFDYvdTrhbBARHTFsJN+WoItzvHUt6M5IRSuTNLA8wFd
6NSVPFzHUilL6/Bo0v3YGYaKIeMerfW0Whaqwm2glanQSxcwnsmMoAYA4DVJJyA=
=eIem
-----END PGP SIGNATURE-----

[R.B.]

Hello fellow users,

An update with some more specifics I ran into and identified:
- Intel X-d => Disable
- Boot/Install in legacy mode since EFI mode won't allow you to add
kernel options.
- Disable secureboot
- Set disk from RAID to AHCI

How far I got with the 4.2 kernel:
- I have a Qubes installation running on a Lenovo X200T which allowed me
to install the 4.2.* kernel. I copied the files that got installed to a
USB stick including a xen.cfg from ticket
https://github.com/QubesOS/qubes-issues/issues/794#issuecomment-167327017
- Then started the installation by booting in Legacy mode. In grub I
added the kernel options i915.preliminary_hw_support=1 i915.enable_ips=0
and pressed enter.
- For the disk, I chose manual partitioning. There I could partition the
disk automatically and shrink the boot partition to make place for an
EFI partition.
- Start the installation.
- After a (forced) reboot, it won't boot because grub seems broken on
this machine. Known error thus far.
- Start a liveCD with Ubuntu.
- Mount the boot partition and search for the boot options in grub.cfg
- Mount the EFI partition and place the kernel files under EFI/qubes
- Edit the xen.cfg to add the right kernel files and options. Copy
options from grub to make sure the kernel knows what the luks partition
and root is.
- Save the files and reboot in UEFI mode.

Here I'm stuck. While the system boots just fine, it cannot find the
luks partition. It looks like the nvme disk is not recognized :-S

When I start with the 4.1.13-6 it does see the nvme disk and I can enter
my key, but it fails horribly at detecting where root, boot or swap
volumes are...

I'll have to wait and see what a later versions brings. Until then thank
you Marek for your help. I learned a lot about UEFI and I hope someone
else does find a way to get Qubes running and leaves a note on how it
was done. In the mean time I'll keep trying every now and then.

Best regards,

R.B.

[R.B.]

On 01/09/2016 09:08 PM, R.B. wrote:
> Hello fellow users,

>
> How far I got with the 4.2 kernel:
> - I have a Qubes installation running on a Lenovo X200T which allowed me
> to install the 4.2.* kernel. I copied the files that got installed to a
>

> Here I'm stuck. While the system boots just fine, it cannot find the
> luks partition. It looks like the nvme disk is not recognized :-S

Even though it's it a debian bugreport, it might be relevant since the
effect is the same. Plust I can confirm with 4.2.8-8. No nvme module in
the initramfs.

The relevant link:
https://lists.debian.org/debian-kernel/2015/12/msg00539.html

Best regards,


R.B.

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

In 4.2 the module is still in drivers/block. You can regenerate
initramfs explicitly including nvme module: dracut -f -d nvme

- --
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

iQEcBAEBCAAGBQJWktJRAAoJENuP0xzK19csfwkH/2J7xdjl4xU3PMsyj5/ZEEee
69jO2AahwUXa1r9+AMojAGXDCXiyLARfR3LhTkBiWLoeRws06eGGfXvqyhI30U/U
WWZXblvuoIBMvgQWwtroq6hZtkgbE9H/su3dnrn5JMrlMcDTdqcWZ+pGsAZ8JTcd
ZKPXm5fQ9UB5ZX++m3gs0ioZzUmfT38JeBlzmNtSjJ9tU2LTpOSUkkooK6LTYBcM
oZBI7RmFhfRlfhcf078+7mMFp42ZxfmWbaBXNEJgjJToM0YwCDE1fv6umYNcpH05
BCTNWC7yr94HQT6A8Nq0wvrtv5GnrX1FIoP44Lw/VOKTwhxKzmcnCwjDYrqRk9o=
=FR1b
-----END PGP SIGNATURE-----

[li...@mullvad.net]

Interesting thread. I'm interested in hearing if you get it working. I'm thinking about buying the 15" version (9550) and would like some hints on whether or not it might be working before spending the money. I'll start a separate thread on that machine if it becomes relevant.

Do they have the keyboard and touchpad connected via PS/2 or USB? Relevant since I want to isolate USB to a USBVM.

[R.B.]

On 01/11/2016 03:40 PM, li...@mullvad.net wrote:
> Interesting thread. I'm interested in hearing if you get it working. I'm thinking about buying the 15" version (9550) and would like some hints on whether or not it might be working before spending the money. I'll start a separate thread on that machine if it becomes relevant.
>
> Do they have the keyboard and touchpad connected via PS/2 or USB? Relevant since I want to isolate USB to a USBVM.
>

Hi Linus,

Only the touchscreen, Webcam and some bcm module (BT?) is USB. Not sure
in what way keyboard/touchpad is connected.

So far the installation media for qubes won't work in UEFI or legacy
mode. By that I mean getting Qubes installed & running. Same goes for
rc2. As you might have noticed, I try to work around it, but it looks
more like shooting in my foot. Just a feeling...

I did get the nmve module in the initramfs for kernel version 4.2.8-8
and the partitions are shown, but somehow lvm and/or luks won't work. I
don't get a prompt yet. Could be anything ranging from PEBKAC to GPT
issues... Ubuntu/UEFI likes GPT, Qubes "want" BIOS, but plays along when
forced by installing next to Ubuntu...

In my opinion it due to the nature of the "very well tested" versions
used of fedora - which is a plus, just not for this laptop. UEFI and
nvme are just getting momentum.

Maybe Qubes-OS 4.0?

If you can wait a bit like me, you could still run Ubuntu on it (works
out of the box), getting used to working with the laptop. Then again I
have the luxury of having a working Qubes-R3.1rc2 installation. Play
with the new one, but working on the old.

If you're more knowledgeable then me, with working with Linux/Xen, you
might get it working and spill the beans here ;-)

Best regards,

R.B.

[li...@mullvad.net]

Hi again,

No success with your XPS yet? I don't know if R3.1-rc3 included anything new around lvm/luks, but I guess you have given it a try? I see other Skylake laptops on this list who are able to get up and running with Qubes, but I think most of those are not using a NMVe disk on the other hand.

Regards,
Linus

[R.B.]

On 03/08/2016 08:12 AM, li...@mullvad.net wrote:
> Hi again,
>
> No success with your XPS yet? I don't know if R3.1-rc3 included anything
> new around lvm/luks, but I guess you have given it a try? I see other
> Skylake laptops on this list who are able to get up and running with
> Qubes, but I think most of those are not using a NMVe disk on the other
> hand.
>
> Regards,
> Linus

Hi Linus,

I checked the list of HCL reports, but could find only one Skylake based
system which was a desktop. Every now and then I try updating the system
I installed on a USB-disk with my trusty-old Lenovo-x200t and try to run
it with the kernel options I discussed in the beginning, and variated a
bit with them.

Still no luck.

The system boots, I can unlock my encrypted disk, but at some points it
won't move on with running a gui. When the system starts to freeze I get
a call trace that tells me that several services entered the failed state.

As reference - both ways:
System on the USB-disk runs fine on my Lenovo
The ubuntu system I installed on the nvme ssd runs fine. I even have
whonix running, based on KVM, but is somewhat slow compared to what I'm
used to in Qubes.

If those systems are there, I must have missed them. The qubes-users
archive won't let me search on skylake, and the systems I did check had
no skylake CPU's like i7-6xxxx. In my case a:
i7-6500U with "intel Skylake graphics".

I do wonder what difference makes the librem 13 running, and the Dell
not. Oh, wait... Found it... Broadwell i5-5200U.

I.O.W.... Skylake has to wait a while for qubes-os.

Thanks for your bump though ;-)

I'll put up an HCL of my older laptop... Waited too long for that.

Best regards,

R.B.

[li...@mullvad.net]

 
Thank you for the update. Oh, I thought lots of people got it working on skylake, strange that you can't search the archives/maillist.

Here is a thread discussing upgrading the kernel so you get Qubes running on a Skylake CPU:

https://groups.google.com/forum/#!searchin/qubes-users/skylake/qubes-users/ttStZXy_PPY/-mmQ6PfdBAAJ

From my understanding some people got it working under some kernel versions.

Regards,
Linus

[R.B.]

On 03/10/2016 09:34 AM, li...@mullvad.net wrote:
> On Wednesday, March 9, 2016 at 8:24:51 PM UTC+1, R.B. wrote:
>

Thank you for the link. A new thread about a NUC got me thinking to try
once more.
https://groups.google.com/forum/#!topic/qubes-users/uKzBAjiAHv8

Maybe the way I test is not valid. As I wrote, I installed Qubes-OS
3.1.rc2 with an older system. Also I run it with booting in legacy mode
instead of UEFI.

The nmve part is no problem at the moment since I use an external HDD.

Regards,

R.B.

[R.B.]

On 03/10/2016 09:38 PM, R.B. wrote:
> On 03/10/2016 09:34 AM, li...@mullvad.net wrote:
>>
>> Thank you for the update. Oh, I thought lots of people got it working on
>> skylake, strange that you can't search the archives/maillist.

I tried searching the HCL mails, but they don't really tell you what
chipset/cpu is in it until you download.

>> Here is a thread discussing upgrading the kernel so you get Qubes
>> running on a Skylake CPU:
>>
>> https://groups.google.com/forum/#!searchin/qubes-users/skylake/qubes-users/ttStZXy_PPY/-mmQ6PfdBAAJ
>>
>>
>> From my understanding some people got it working under some kernel
>> versions.
>>
>> Regards,
>> Linus
>>
>
> Thank you for the link. A new thread about a NUC got me thinking to try
> once more.
> https://groups.google.com/forum/#!topic/qubes-users/uKzBAjiAHv8

Tried and failed. It does seem to work better, but I still get hung up
on the console. I have a dmesg log output attached for those who are
interested in troubleshooting.

I see two problems in the log.
1. ACPI errors.
Is the ACPI table from Dell unreadable by the kernel 4.1.13-9?
Not sure what I can do about it with boot options.
Tried pci=nocrs but it was no help.

2. I keep getting a trace log with
int3403 thermal: probe of INT3403:03 failed with error -22
And then a call trace to cut out. Not sure about what went wrong
here or if it is even related.

Regards,

R.B.

[R.B.]

Hi there,

Here's an update with a HCL - for reference purposes only - of Qubes
running on a Dell XPS 13 9350 with the development kernel 4.4.10-9
running from a USB Disk.

I get no problems with the GUI unlike I described earlier. Touchscreen
works out of the box.

I do use boot flags like:
i915.preliminary_hw_support=1
i915.enable_ips=0

Wifi won't work, but that's a driver issue. I would need a way of
compiling kernel drivers with newer sourcecode of the driver. The way to
boot this instance of Qubes at the moment is legacy instead of UEFI.

Since USB is occupied by the external drive, I have - atm - no way of
getting network connectivity through a USB network adapter.

Just in case you're still wondering, I did NOT install Qubes on the
laptop. I merely run it from an external drive. Installation was done
via a Lenovo Thinkpad X200t which has no UEFI.

This was a little update. Maybe I find a way and time to compile a
different driver for the kernel unless a newer unstable kernel is
released for Qubes-3.1 with the right driver version. That would be the
moment for me to get Qubes really running on the XPS from the nvme drive.

Found one little bug. The script to generate the HCL doesn't like
spaces. It tried to redirect data to "Qubes-HCL-Dell Inc.-XPS 13
9350-20160601-001910.yml" and failed of course.


Regards,

R.B.