@Erica.vH
So sorry to hear about this.
Unfortunately these problems can come when you work at(beyond) the edge of what
Qubes supports.
This is why Qubes provides the HCL, to guide user purchases.
That said, the pace of development is quite fast, so it may be that in
short order, the problem you encountered will be resolved.
Can you give some more information here? What is the error?
Can you provide specs for your P15?
I never presume to speak for the Qubes team.
When I comment in the Forum or in the mailing lists I speak for myself.
Hi UnMan and Confused,
Thks for your posts, both.
The spec for the P15 are in my previous post.
I don’t blame Qubes, I blame the laptop !
When installing Qubes, it goes through material check up and then stops with a ctrl-D option at the end. I’ve tried to save the log, but LS gives me no otpion (no disk to save it to)
For now, I’m following this lead 4.1 Installation Trouble On ThinkPad P15, Gen. 2 but the normal bios update is giving me trouble, so I’m trying off-line … if it works
Cheers,
This thread is headed slightly out of primary scope, anyone @off-topic-moderators could help moving it all (the last 3-4 posts) to a thread on its own ? “Setting up Qubes on a P15 gen2 128GB ram 4TB NVMe”
I’ve updated the bios, and gave it another try, but to no avail, it crashes during pre-test
First, it holds for about 3min (first pix), then it flows tons of lines until giving me the D. (ctrl-D option on 2nd pix)
Hi @Renehoj,
Thks for your input.
As I am currently installing Suse, I see that the RAID is indeed not recognized, the installer only sees two 2TB NVMe as “empty”.
But these 2 NVMe in RAID.0 should not prevent install as I’m targeting the small 512GB NVMe standalone (not part of the RAID)
Suse install = 1
Qubes install = 0
I’ve solved this part of the problem.
As all my network is wired, all m ThinkPads are set to Airplane mode.
But as I was poking around, I stumbled on the Airplane mode … for power !
I turned it off, and sure enough, the battery started charging !
Hi,
I’ve removed the RAID0, and started the instal with choice “Boot verbose and debug” (or something like that)
Here is where the install hang for 2min
not sure if the lack of EFI variable comes from my USB stick (Via Rufus) or the current disk (Where Win10 and Suse are installed)
Assuming right
Disabled VMD as well. Actually, pretty much every option in the bios are off.
Tomorrow I will remove RAM and remove NVMe 1 by 1 and keep trying.
I bought this machine only for Qubes, I’m not turning back !
Test 2:
Thks to Hiren Boot CD, I’ve managed to change one of the 2x 2TB NVMe into MBR, the other stayed GPT
Removed all remaining 32G RAM, reinstalled original 16G RAM
Install failed.
I’m not sure it is about neither the RAM nor the NVMe … It seems there is some about the UEFI … dracut initqueue hook …
EFI partition unknown; exiting, EFI varia not set by bootloader
don’t know, haven’t tried yet, didn’t even purchased the flasher yet.
alt-ctrl during Qubes install you mean ? let me try that
But so far, haven’t been able to save any log as there is no accessible disk (>LS = empty)
I had the same problem when trying to install qubes on KCMA-D8 (Your errors look very similar). Just run the first half of the install on a different computer and then move the disk to the computer you actually want to run qubes on. Goes like this:
Start qubes install on “Other” computer
When prompted to restart after grub install, shutdown computer instead of restarting. (You can let it try to restart, just unplug the computer while it’s cycling the power)
Move your fresh “qubes just installed” disk and boot it on the “new” computer
If I’m not mistaken, on these newer Thinkpad laptops like the P53 or P15 it is possible to disable Intel ME in the bios, but it’s not possible to flash coreboot on them.
