Problem installing Qubes 4.2 (fresh install) - When Install using latest Kernel is selected. (6.6.1) #8895
Labels
affects-4.2
This issue affects Qubes OS 4.2.
C: installer
C: kernel
hardware support
needs diagnosis
Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed.
P: default
Priority: default. Default priority for new issues, to be replaced given sufficient information.
T: bug
Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
How to file a helpful issue
Qubes OS release
4.2.0 RELEASE from ISO, booted/mounted using Ventoy.
Brief summary
Installing on a partition on an internal spinning disk.
There are three OS on separate partitions (subdivided using LVM)
Prior installs seem to work but the Boot with latest kernel option fails with a timeout.
Steps to reproduce
Put Ventoy on a USB stick
Load the ISOs from your favourite OS's
Edit the Ventoy config file
Boot into Ventoy
Select "Install Qubes OS 4.2.0 (release)"
...Wait for next boot....
Choose "Install Qubes OS R4.2.0 using Kernel Latest (6.6.2-1.qubes.fc37)"
Expected behavior
As per "Install Qubes OS R.4.2.0"
Actual behavior
R4.1.?? Installed previously fine (though has serious stability and GUI scaling issues) I have used it for a couple years.
R4.2 RC5 Installer starts, but the RC did not understand the disks, so I got no further
R4.2 1st/top Install option installer starts
R4.2 last/bottom install option ("using latest kernel 6.6.2-1") fails with an error similar to this error
It puts up hundreds of that error, I mashed keys and pressed esc, ctrlc and ctrlz lots and eventually it did a file not found and dropped into a shell. I was able to capture some logs if that helps?
Looking at the log file the Kernel 6.6 seems not to have fixed my reason for re-installing (to get a newer Kernel version).
_Note: Slightly off topic; But here for completeness... Kernel 6.6+ is required due to a bug that effects PCI NVME with certain controller chips being not recognised that appeared in 5.. Apparently this is supposed to be fixed in Kernel 6.6, from what I see perhaps that is not the case?
See Kernel Bug and
Similar issue and Similar issue
The text was updated successfully, but these errors were encountered: