i just got an TUXEDO InfinityBook S 17 - Gen7 with
Intel Core i7-1260P (max. 4.70 GHz | 12 Core | 16 Threads) | Intel Iris Xe Graphics G7
Intel Wi-Fi 6 AX200 (802.11ax | 2,4 & 5 GHz | Bluetooth 5.2)
I used the Qubes-R4.1.2-x86_64.iso on an USB-Stick for installation.
The boot-process logs are the following:
dracut-pre-udev[644]: modprobe: FATAL: Module cramfs not found in directory /lib/modules/6.1.12-1.qubes.fc32.x86_64
dracut-pre-udev[695]: modprobe: FATAL: Module floppy not found in directory /lib/modules/6.1.12-1.qubes.fc32.x86_64
[OK] Started **Show Plymouth Boot Screen.**
[OK] Started **Forward Password Requests to Plymouth Directory Watch.**
[OK] Reached target **Local Encrypted Volumes.**
c
[FAILED] Failed to start **udev Wait for Complete Device Initialization.**
See 'systemctl status systemd-udev-settle.service' for details.
Starting **Device-Mapper Multipath Device Controller...**
[OK] Started **Device-Mapper Multipath Device Controller.**
[OK] Reached target **Local File Systems (Pre).**
[OK] Reached target **Local File Systems.**
Starting **Open-iSCSI...**
Starting **Create Volatile Files and Directories...**
[OK] Started **Open-iSCSI.**
Starting **dracut initqueue hook...**
[OK] Finished **Create Volatile Files and Directories.**
[OK] Reached target **System initialisation.**
[OK] Reached target **Basic System.**
Before the FAILED-Message it stuck about 2 minutes. At the last OK-message the system freezes.
I tried from adding by editing the use-last-kernel-option in the grub menu an aing dom0_max_vcpus=1 dom0_vcpus_pin=1 from Qubes on Ryzen 7 pro 6850U elitebook 845 g9 - #5 by Cpotts without any changes
I tried to addin irqpoll according to GPD Win Max 2 - Unable to boot installer - #4 by lrvick .
Now i think my hardware is incompatible with qubes at the time.
Does anyone has additional tipps to got the installation?
I am grateful for any help!
I have that exact laptop and used the same .ISO. did you boot the PC in the newer GRUB?
Sorry, i dont understand. I dd-ed the iso to the USB-Stick. How can i use another GRUB?
thanks for the advice. I will try the newer test-iso .
Do you have RAID enabled in BIOS?
qanboy
May 27, 2023, 12:45pm
7
with Qubes-4.2.202305221524-x86_64.iso nothing changed, same FAILED on Device Initialization and freezing at basic.target
qanboy
May 27, 2023, 12:46pm
8
no, i have 2 ssds but without a raid.
Just to make sure, even if you didn’t specifically configured the RAID for your drives, in some BIOS it’s the default SATA mode:
qanboy
May 27, 2023, 6:05pm
10
My Bios looks like that:
I have only the possibility to create a raid-1 or a raid-0, but cannot choose an AHCI-Mode.
I don’t know about this specific BIOS, you can try to find your BIOS manual and see if the default SATA mode is AHCI or RAID and maybe there’s a way to change this hidden option somehow.
Related issue:
opened 11:37AM - 18 Aug 21 UTC
T: bug
P: default
hardware support
needs diagnosis
C: storage
### Qubes OS release
R4.1.0 beta (downloaded August 18th 2021)
(need to us… e that version because R4.0.4 uses an older kernel that does not support the new Intel Integrated Graphics chip in the CPU, see #6839)
### Brief summary
Qubes does not support any of the laptop's internal NVMe slots.
laptop model: Dell Latitude 5521
CPU: Intel 11th generation i7-11850H "Tiger Lake"
`lspci` output (created with Debian 11 (testing)):
```text
[...]
0000:00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller
Subsystem: Dell Volume Management Device NVMe RAID Controller
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
IOMMU group: 9
Region 0: Memory at 6072000000 (64-bit, non-prefetchable) [size=32M]
Region 2: Memory at a4000000 (32-bit, non-prefetchable) [size=32M]
Region 4: Memory at 6075100000 (64-bit, non-prefetchable) [size=1M]
Capabilities: <access denied>
Kernel driver in use: vmd
Kernel modules: vmd
[...]
10000:e1:00.0 Non-Volatile memory controller: Toshiba Corporation Device 0116 (prog-if 02 [NVM Express])
Subsystem: Toshiba Corporation Device 0001
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 0
NUMA node: 0
IOMMU group: 9
Region 0: Memory at a4000000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: nvme
Kernel modules: nvme
```
### Steps to reproduce
1. have the specified laptop model (or only the specified NVMe Raid controller, I guess)
2. boot from Qubes R4.1.0 beta boot medium
3. select verbose mode ("Troubleshooting")
### Expected behavior
Anaconda starts and presents SSD to select
### Actual behavior
- boot hangs at starting `systemd-udev-settle.service` for two minutes (timeout is 186 s)
- boot continues and then hangs at "Reached target Basic System"
- debug message `nvme0: I/O 25 QID 0 timeout, completion polled` gets printed to the screen every 30 seconds or so
- boot does not continue
If I add `pci=nomsi` to the boot options, the system boots and Anaconda starts but says it says "No disks detected" and offers network volumes instead.
### Additional information
- That exact same setup works just fine with Debian 11 (testing) but not with Debian 10.10
- That same NVMe SSD has worked fine with Qubes R4.0.3 in a Dell Latitude 7480
Cpotts
May 27, 2023, 9:02pm
12
When booting initially, there is an advanced boot screen that should allow you to toggle between the stable or latest kernel. Choose the latest kernel.
qanboy
May 27, 2023, 10:18pm
13
Since you have the same computer as me, you should also have the same BIOS. Have you changed any settings for the installation?
I have only deactivated the Intel Management Engine.
qanboy
May 27, 2023, 10:21pm
14
thanks for your advice. i will try to find a manual for the BIOS.
Cpotts
May 28, 2023, 3:17am
15
I did not change anything, Qubes booted on the computer with no changes to the BIOS. The only thing I did was when the computer initially booted with the qubes USB, was select the newest kernel.
qanboy
May 28, 2023, 4:32pm
16
Thanks @Cpotts
I played around with the bios a bit and tried RAID for a short time. I then switched it off again. Maybe I shouldn’t have done that and something was changed that I can’t reset via the BIOS GUI.
I only found a white paper on https://www.insyde.com/ . I asked Tuxedo for a BIOS manual.
I thought that if I bought this computer I would be able to install Qubes. If nothing turns up, I’ll probably have to do without Qubes.
You can try to reset BIOS to factory defaults.
1 Like
qanboy
May 29, 2023, 4:16pm
18
Even a factory reset does not lead to any change in the installation behaviour.
Can you check the boot log for more precise errors?
After:
[OK] Reached target **Basic System.*
If you wait for some more minutes then dracut will timeout and you’ll be able to enter shell to get the logs.
Like this:
ok so I tried to take photos while booting the install usb/iso. I also tried ocr’ing the output so it might be easier to read/parse (though keep in mind its ocr so unlikely to be perfect). Any other ideas would of course really really be appreciated!
First I got:
9.055346] dracut-pre-udevt6231: modprobe: FATAL: Module crams not found in
directory /lib/modules/5.18.16-1.fc32.qubes.x86_64
9.1947093 dracut-pre-udevt6741: modprobe: FATAL: Module floppy not found in
OR
] Started Show Plymouth Boot …
qanboy
May 29, 2023, 5:35pm
20
I have now waited half an hour after the “reached target basic system”. No further messages came. I then pressed STR-ALT-DEL and more messages appeared (see screenshots).
More “completion polled” messages then appear, but the system does not restart.
There is also no shell prompt.