I hope you are all having a good day.
I recently managed to get myself a new Clevo laptop and I have run into some issues trying to get Qubes to boot, which led me to wonder if the hardware is supported. I know Qubes has a narrow range of support for hardware, and my laptop does not show up in the HCL. I would still like to try and get Qubes working, and I don’t mind a good challenge! Could the following system specs possibly support Qubes?
Hardware:
CLEVO NS50MU
Intel Core i7-1165G7
Intel Iris Xe Graphics
32 GB RAM
1 TB SSD
BIOS:
Insyde H2O BIOS Version:1.07.06
Things tried so far:
I have made sure to verify the signature of the Qubes image. I’ve created the bootable USB both with BalenaEtcher and the dd command provided on the site:
sudo dd if=Qubes-RX-x86_64.iso of=/dev/sdY status=progress bs=1048576 && sync
When trying to boot from USB, no boot screen is presented and I am not able to change boot options. All advice is welcome, thank you in advance!
What iso images have you tried?
I advise trying to install Qubes 4.1 (if you haven’t already)
You can also build isos, (though the iso-builder works out-of-the-box about 1% of the time, and atm is a pain because of an RPM issue):
opened 03:19PM - 12 Apr 21 UTC
C: builder
P: major
T: bug
diagnosed
**Qubes OS version**
R4.0
**Affected component(s) or functionality**
… Qubes Builder
**Brief summary**
When trying to build a new iso for R4.1 following the docs (https://www.qubes-os.org/doc/qubes-builder, https://www.qubes-os.org/doc/qubes-iso-building) it fails at `make qubes` (specifically, when `Building core-libvirt (libvirt.spec) for fc32 dom0`) with:
```
-> Building core-libvirt (libvirt.spec) for fc32 dom0 (logfile: build-logs/core-libvirt-dom0-fc32.log)
--> build failed!
(48/87): isns-utils-libs-0.97-10.fc32.x86_64.rp 341 kB/s | 107 kB 00:00
(49/87): libacl-devel-2.2.53-5.fc32.x86_64.rpm 215 kB/s | 68 kB 00:00
(50/87): libaio-0.3.111-7.fc32.x86_64.rpm 77 kB/s | 24 kB 00:00
(51/87): libattr-devel-2.4.48-8.fc32.x86_64.rpm 81 kB/s | 25 kB 00:00
(52/87): libbasicobjects-0.1.1-44.fc32.x86_64.r 85 kB/s | 26 kB 00:00
(53/87): libcollection-0.7.0-44.fc32.x86_64.rpm 130 kB/s | 44 kB 00:00
(54/87): libev-4.31-2.fc32.x86_64.rpm 174 kB/s | 55 kB 00:00
(55/87): libini_config-1.3.1-44.fc32.x86_64.rpm 211 kB/s | 67 kB 00:00
(56/87): libpath_utils-0.2.1-44.fc32.x86_64.rpm 93 kB/s | 29 kB 00:00
(57/87): libpciaccess-0.16-2.fc32.x86_64.rpm 84 kB/s | 27 kB 00:00
(58/87): libpciaccess-devel-0.16-2.fc32.x86_64. 39 kB/s | 12 kB 00:00
(59/87): libref_array-0.1.5-44.fc32.x86_64.rpm 83 kB/s | 27 kB 00:00
(60/87): libssh2-1.9.0-5.fc32.x86_64.rpm 354 kB/s | 119 kB 00:00
(61/87): libssh2-devel-1.9.0-5.fc32.x86_64.rpm 176 kB/s | 54 kB 00:00
(62/87): libtool-2.4.6-33.fc32.x86_64.rpm 1.7 MB/s | 579 kB 00:00
(63/87): libverto-libev-0.3.0-9.fc32.x86_64.rpm 41 kB/s | 13 kB 00:00
(64/87): lvm2-2.03.09-1.fc32.x86_64.rpm 3.6 MB/s | 1.3 MB 00:00
(65/87): lzo-2.10-2.fc32.x86_64.rpm 220 kB/s | 67 kB 00:00
(66/87): lvm2-libs-2.03.09-1.fc32.x86_64.rpm 2.5 MB/s | 897 kB 00:00
(67/87): netcf-devel-0.2.8-15.fc32.x86_64.rpm 34 kB/s | 11 kB 00:00
(68/87): netcf-libs-0.2.8-15.fc32.x86_64.rpm 212 kB/s | 70 kB 00:00
(69/87): numactl-devel-2.0.12-4.fc32.x86_64.rpm 70 kB/s | 22 kB 00:00
(70/87): numactl-libs-2.0.12-4.fc32.x86_64.rpm 101 kB/s | 30 kB 00:00
(71/87): numad-0.5-31.20150602git.fc32.x86_64.r 132 kB/s | 40 kB 00:00
(72/87): parted-3.3-3.fc32.x86_64.rpm 1.7 MB/s | 591 kB 00:00
(73/87): parted-devel-3.3-3.fc32.x86_64.rpm 112 kB/s | 34 kB 00:00
(74/87): polkit-0.116-7.fc32.x86_64.rpm 469 kB/s | 146 kB 00:00
(75/87): mozjs60-60.9.0-5.fc32.x86_64.rpm 4.3 MB/s | 6.6 MB 00:01
(76/87): polkit-libs-0.116-7.fc32.x86_64.rpm 213 kB/s | 68 kB 00:00
(77/87): polkit-pkla-compat-0.1-16.fc32.x86_64. 145 kB/s | 45 kB 00:00
(78/87): python3-docutils-0.15.2-4.fc32.noarch. 4.3 MB/s | 1.5 MB 00:00
(79/87): python3-pyparsing-2.4.7-1.fc32.noarch. 469 kB/s | 149 kB 00:00
(80/87): radvd-2.18-3.fc32.x86_64.rpm 290 kB/s | 94 kB 00:00
(81/87): readline-devel-8.0-4.fc32.x86_64.rpm 596 kB/s | 192 kB 00:00
(82/87): rpcbind-1.2.5-5.rc1.fc32.1.x86_64.rpm 193 kB/s | 60 kB 00:00
(83/87): rpcgen-1.4-4.fc32.x86_64.rpm 158 kB/s | 53 kB 00:00
(84/87): xfsprogs-5.4.0-3.fc32.x86_64.rpm 2.9 MB/s | 1.1 MB 00:00
(85/87): xfsprogs-devel-5.4.0-3.fc32.x86_64.rpm 246 kB/s | 83 kB 00:00
(86/87): xml-common-0.6.3-54.fc32.noarch.rpm 99 kB/s | 31 kB 00:00
(87/87): zfs-fuse-0.7.2.2-14.fc32.x86_64.rpm 3.9 MB/s | 1.5 MB 00:00
--------------------------------------------------------------------------------
Total 2.4 MB/s | 30 MB 00:12
Package xen-devel-4.14.1-3.fc32.x86_64.rpm is not signed
Package xen-libs-4.14.1-3.fc32.x86_64.rpm is not signed
Package xen-licenses-4.14.1-3.fc32.x86_64.rpm is not signed
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: GPG check FAILED
make[2]: *** [/home/user/qubes-builder/qubes-src/builder-rpm/Makefile-legacy.rpmbuilder:51: dist-build-dep.spec] Error 1
make[2]: Leaving directory '/home/user/qubes-builder'
make[1]: *** [Makefile.generic:191: packages] Error 1
make[1]: Leaving directory '/home/user/qubes-builder'
make: *** [Makefile:266: core-libvirt-dom0] Error 1
```
**How Reproducible**
100%
**To Reproduce**
Steps to reproduce the behavior:
1. Follow the steps in the docs
2. run `make qubes`
3. notice the error
**Expected behavior**
builder should complete without issues
**Actual behavior**
builder errors out
**Screenshots**
**Additional context**
The build takes place in a `fedora-32`, it's worth nothing that this was working 3 days ago, but seems something has changed that prevents the build from complete
**Solutions you've tried**
No solution yet
**Relevant [documentation](https://www.qubes-os.org/doc/) you've consulted**
- https://www.qubes-os.org/doc/qubes-builder/
- https://www.qubes-os.org/doc/qubes-iso-building/
- https://github.com/marmarek/qubes-builder/blob/master/doc/Configuration.md
**Related, [non-duplicate](https://www.qubes-os.org/doc/reporting-bugs/#new-issues-should-not-be-duplicates-of-existing-issues) issues**
#5526
1 Like
Thanks for your advice! I haven’t tried Qubes 4.1 yet! I’ll make sure to give that a go as well, that has me hopeful
After looking into it some more I suspect it could also be the BIOS so if the images don’t work, I could look into replacing it with the open source BIOS that system 76 uses
Thank you again, I’ll let you know if it works
1 Like
Are you using a legacy bios and a UEFI bio, you can try to switch from one to an other if you can and start to boot again
Sven
June 17, 2021, 2:35am
5
There is a Dell XPS 13 9310 with a HCL report that shares your
CPU and therefore chipset and graphics:
It needs i915.alpha_support=1
The corresponding thread starts off with:
I found it very difficult to get Qubes installed and usable. These
are some notes I made at the time and may need some adjustment for
other scenarios.
https://groups.google.com/g/qubes-users/c/P5oXyk7QOFE/m/hEROXm0tBQAJ
It contains specific instruction on how to prepare the install media,
these will likely help you get Qubes OS installed.
1 Like
And to cover all bases, are you sure you are hitting the right key to get into the BIOS and/or boot menu to select a different boot device?
1 Like
Yup, the menu pops up successfully and I am able to select the USB
Insyde H2O BIOS is proprietary, so that might be causing issues as well. I’ll try to change the boot settings first and if that doesn’t work, try to switch to the BIOS of System 76 for the laptop
1 Like
Hello Sven,
Thank you for your detailed and specific reply! I have tried this approach but I have run into some problems.
I have tried setting up the Qubes Builder on Fedora 34, following the steps described here: qubes-builder .
Everything works like a charm up until make qubes
, when I get the following error:
home/username/qubes-builder/qubes-src/builder-rpm/chroot-dom0-fc32/var/lib/rpm/.rpm.lock (permission denied)
I have changed the /etc/sudoers
file by adding the following line so sudo root works without any prompt
username ALL=(ALL) ALL
I know there is a known bug in RPM at the moment, linked by Quser59: issue 6522 , but this doesn’t seem to completely describe my error. Do you have a suggestion on how to proceed?
Kind regards and thank you in advance!
Sven
June 22, 2021, 6:39pm
10
Thank you for your detailed and specific reply! I have tried this
approach but I have run into some problems.
Can you be a bit more specific? Have you been able to install Qubes OS
with the modified install media?
I have tried setting up the Qubes Builder on Fedora 34,
I don’t quite see how you get from our discussion to setting up a Qubes
Builder. If it’s unrelated, please start a new topic.
Hello Sven,
I’m afraid I misunderstood what you meant in your original post. When I tried modifying the iso file, I got an error saying the partition table was missing and it wouldn’t result in a valid bootable USB, so I assumed I had to go through the build process. Thank you for pointing me in the right direction
1 Like