I have found a few threads about the installation of Qubes OS on a Dell XPS 13, but they are at least several months old.
I'm trying to install Qubes 3.2 onto Dell XPS 13 9350, which has a running Ubuntu 16.04 LTS. The hardware matrix is,
* BIOS 1.2.3
* CPU i5-6200U @ 2.30 GHz
* Skylake
* FHD (mine is not QHD)
* Memory 8GB
* M.2.PCIe SSD
* TPM 1.2
* VT + DIO
I disabled secure boot and successfully booted in UEFI. Anaconda was running well, GUI showed, but keyboard and mouse don't work in the screen of language selection.
I wanted to try adding options in GRUB, but [Tab] gave me "chainloader /EFI/BOOT/xen.efi". I mounted USB disk with Qubes in Ubuntu, but its filesystem is ISO9660. I can't change /EFI/BOOT/xen.cfg.
I thought I had a chance to use Qubes OS, since XPS 13 9350 is well supported by kernels newer than 4.4. Any comments, please?
Thanks!
miaoski
I booted to BIOS and added FS0:/EFI/qubes/xen-4.6.1.efi.
There's no problem booting to Dom0 and create default qubes + sys-usb.
Internal touchpad works as well.
Internal WiFi doesn't work as expected. Mitigating with a USB dongle.
Thanks!
miaoski
I think BCM4350 has some issue with kernel 4.4.14. dmesg shows,
[ 3.558678] brcmfmac 0000:00:00.0: Xen PCI mapped GSI16 to IRQ22
[ 3.560707] brcmfmac: brcmf_chip_recognition: SB chip is not supported
[ 3.560724] brcmfmac: brcmf_pcie_probe: failed 14e4:43a3
Thanks.
miaoski
Thanks for the suggestion. Just tried kernel 4.8.12_12 but same dmesg popped up.
Will try to copy a working firmware and parameters tonight.
Thanks
Miaoski
But I'm not good at driver debugging ... Help is much appreciated.
Thanks,
miaoski.
A simple solution is to use PCIe permissive mode, which weakens device isolation.
Please refer to "PCI passthrough issues" of https://www.qubes-os.org/doc/assigning-devices/
Although there is a dmesg saying
[ 2.411487] brcmfmac 0000:00:00.0: Direct firmware load for brcm/brcmfmac4350-pcie.txt failed with error -2
wlan0 works as expected.
Thanks,
miaoski.
I am in the same situation, xps 9350, the permissive trick fixed the issue in 3.2 but got the problem back in the 4.0 rc3 and rc4.
However I got it working by trying to attach the device to a PV Qube, so I switched sys-net to PV in the meantime, it works.
No luck in HVM mode with the current-testing repo.
qubes-core-dom0 4.0.21
vm kernel 4.14.13-3
Thank you in advance.
Can you please help with connecting to wifi for the first time?