Can't boot install-USB on LENOVO ThinkPad T14s Gen6 (21QX00HECK)

juba · August 8, 2025, 2:06pm

Hello, I just bought computer LENOVO ThinkPad T14s Gen6 (21QX00HECK)
CPU:Intel Core Ultra 7 258V (VT-x, VT-d included)
RAM:32GB LPDDR5 8533MHz
BIOS:Disabled Secure Boot

I’m trying to install QubesOS 4.2.4 from install-USB, but I have a problem. The boot process of install-USB always stops at the same place:
“Started systemd-rfkill.service - Load/Save RF Kill Switch Status.”

I tried to choose standard boot, boot with self-check and verbose boot… with same result. Boot process of install-USB is always stopped.

I assume the bootable USB is fine:

I used new USB SanDisk 64GB memory (no bad blocks)
I used balenaEtcher to create a bootable USB
USB self-check gone correct
I was able to install QubesOS on an older computer from this USB.

Thank you for any recommendations.

catacombs · August 8, 2025, 2:22pm

Welcome to the group.

Which Operating system did you use while installing the USB?

Edit:
Is there more than one drive in the computer?
Are either drives brand new?
Are you trying to accomplish a dual boot?

ChrisA · August 8, 2025, 2:52pm

Hi Juba - and welcome to the forum.

Did you use the default kernel … or kernel-latest?

If you edit the GRUB options, can you try and add nomodeset to the kernel-line?

juba · August 8, 2025, 3:26pm

catacombs, ChrisA, thank you for the welcome.

For catacombs:

I created bootable install-USB by “Ubuntu 24.04.3 LTS”.
In computer is just original 1TB NVME disc (with installed Win11…just this os, no dual boot) + 64GB SanDisk USB (QubesOS installation USB). I had same problem, when primary OS was Ubuntu 24.04.3 LTS.
I used current version “Etcher for Linux x64 (64-bit) (zip)” available at balenaEtcher - Flash OS images to SD cards & USB drives version: 37.2.4
No dual boot.

For ChrisA:

I also try to used last boot option "Install Qubes OS R4.2.4 using kernel-latest (6.12.11-1.qubes.fc37). There boot process is auto-restarted after lines:

…in progress…

ChrisA · August 8, 2025, 3:35pm

Hi juba

When the machine reboots automatically, you should be able to add:

console=vga vga=,keep loglvl=all guest_loglvl=all noreboot=1 earlyprintk=xen

to the Xen line in GRUB and get a chance to see what goes wrong. Note: The boot will be slloooowww

catacombs · August 9, 2025, 12:23am

ChrisA sounds more knowledgeable than myself.

I never had good experiences with Balena Etcher. Has so many options.

If your installation is -Mission Critical- absolutely must not be compromised. Then you should use dd. In my humble, not reliable opinion. Use most secure option.

Else, there is in Ubuntu, several USB tools, which I believe can be added.

USB stick formatter.
USB image writer.

Gparted.

While it likely has nothing to do with your problem, being thorough. I have sometimes found reformatting the computer drive to be helpful in getting around some problems. Not sure how to define detecting them

Reformat the USB Drive as well.

Use the USB Image Writer. It is already installed Mint. I think it is the repository of Ubuntu -latest.

I have also used easy-dd: Which Barry Kauler (creator of Puppy Linux, and Easy OS, (what is meant as a secure version of a Puppy like distro)

Easy dd works in the versions of Linux I tried.

https://www.bkhome.org/linux/easydd-write-image-file-to-drive.html

Also, I am not knowledgeable enough. there is the possibility that your computer has a graphics chip, and or card that is not automatically starting with the USB Install.

Then there is also whether you are using a Linux kernel that matches your processor. I am too lazy to look it up.

but if you are really highly security conscious. Then write the USB using dd. Also explicitly write all over the computers drive.

Yes I have seen issues which were solved by reformatting the USB, reformatting the drive in the computer. Some things Edit"Already Installed software" do “does” not like to be overwritten. I guess it comes from Linux being polite and allowing for dual boot. While Qubes, for security reasons, wants, expects to be the only thing on the drive.

Probably working with ChisA will lead to a solution as well. I am just more for trying different options than reading possible error messages to figure things out, which I mostly have to look up.

I use Mint Linux, Edit"in creating Install USB" which is derived off Ubuntu.

Edit"I suspect, in earlier efforts, Fedora Media Writer can create the Qubes Install USB. I have never had good experiences in trying to build the Qubes Install USB from Windows. I suspect might have to do with the size of Qubes. " " "

Jnoon10 · September 28, 2025, 8:41pm

@Juba hi if you got it fixed can you tell me how long battery life and how many VMs you are using

Daniel3 · September 29, 2025, 12:03pm

Hello Juba

Did you manage to solve this problem?
I encountered the same problem.

MellowPoison · September 29, 2025, 12:29pm

Try to boot the Qubes OS 4.3.0-rc2 installer with kernel-latest for a test.

juba · October 17, 2025, 9:21pm

Hi all

Thank you for suggestion. With QubesOS-4.3.rc2 (and also rc1) Now I’m able to install QubesOS, but I can’t boot them:

I used two methods to create a installation USB-key: balenaEther tool and “dd” command.
Before every installation I used “dd” command to clean first cca 10GB of disc.
During installation I choose default configuration (I created just user and choose automatic creation of partitions (with “Click here to create them automatically”) with one variation: some installation was with and some without “Encrypt my data”.
…totally maybe 10 installations…some of these installation was experiments with partitions and encryption

After every installation I also try to run all GRUB options. Results of default setup:

QubesOS-4.3.rc2:
Grub:Qubes, with Xen hypervisor:

[4.179539] dracut-cmdline[347]: Warning: USB in dom0 is not restricted. Consider rd.qubes.hide_all_usb or usbcore.authorized_default=0.

Grub:Advanced Options|Xen hypervisor version 4.19.3|Qubes with Xen 4.19.3 and Linux 6.12.47.1.qubes.fc41.x86_64

[4.469741] dracut-cmdline[346]: Warning: USB in dom0 is not restricted. Consider rd.qubes.hide_all_usb or usbcore.authorized_default=0.

Grub: Qubes, with Xen hypervisor (without grub “quiet” parameter):

Grub: Qubes, with Xen hypervisor (without grub “rhgb quiet” parameters):

MellowPoison · October 17, 2025, 9:37pm

Try to install the Qubes OS 4.3.0-rc2 with kernel-latest as I suggested previously.

juba · October 22, 2025, 9:19pm

I tried to install QubesOS with “R4.3.0-rc2 using kernel-latest 6.15.11-1.qubes.fc41”…Installation is working correctly.

But booting of installed QubesOS stop with same error:

dracut-cmdline[353]: Warning: USB in dom0 is not restricted. Consider rd.qubes.hide_all_usb or usbcore.authorized_default=0.

Same error for other grub-options (different is just line number):

Grub option "Qubes with Xen hypervisor" ...line 353 (default grub option)
Grub option "Advanced|Xen4.19.3, Linux 6.15.11.1" ...line 356
Grub option "Advanced|Xen4.19.3, Linux 6.12.47.1" ...line 342