kexec can't boot qubes 4.1 iso

Hi @tlaurion any chance to boot from heads? Did you try 4.1 iso?
I use master branch. 4-14.62-heads

[MrChromebox]

where are you seeing Qubes 4.1? 4.0.3 is the latest release

edit: would also help to mention what hardware is in use

@MrChromebox

laptop : x220
install media: https://openqa.qubes-os.org/tests/5493/asset/iso/Qubes-4.1-20200113-x86_64.iso
firmware: heads - boot fails.

laptop : x220-tablet
install media: https://openqa.qubes-os.org/tests/5493/asset/iso/Qubes-4.1-20200113-x86_64.iso
Rufus MBR/Legacy method dd (only legacy mode, uefi stuck before Anaconda start)
bios: modified 1.46 (unlocked RAM and whitelist wifi) NOT coreboot (http://www.mcdonnelltech.com/X220_v1.46_Modified_BIOS.zip) - boot success

[MrChromebox]

any reason you're using a nightly build instead of the 4.0.3 release? Can you test that so we know if it's version-specific?

any reason you're using a nightly build instead of the 4.0.3 release? Can you test that so we know if it's version-specific?

Yes. fedora-25 on dom0 is totally outdated and not supported (status on December 12th, 2017)
Qubes 4.1 runs fedora-31, xfce-4.14, new features, include installation, a lot of fresh packages etc.
Qubes builder works good for 4.1. Ok, i will try.

[MrChromebox]

I'll test both here as well and see if I can replicate on a Librem

[tlaurion]

@0rb677 @MrChromebox I confirm install works on my branch (not main Heads) for x230 for latest official QubesOS release (4.0.3). I didn't test any 4.1 release yet, while there are another issue linked to LUKS V2 not being supported (#669) which would probably fail to boot Fedora-31(?) based QubesOS install anyway until resolved (upgraded cryptsetup module, reproducibility of produced ROM images confirmed on CI for different host builders configs ( ubuntu, debian, fedora etc).

There was a fix a while back to be able to boot fedora-30 (#553) that I tested but your issue seems to be related to igfx corruption, which is supposed to be fixed under x220, but i'm not the best to confirm this.

Unfortunately, I just own x230 for testing. Will put that in my todo list but i'm quite busy right now.
If you want to ship a x220 to me, be my guest but reading QubesOS release schedule shows that we are far from 4.1. (So this is not a priority for me to test this now).

Please check in other issues for t420 and x220 users and ping them here. If you can confirm that their patchwork work, poke me in those PR and I will merge them asap. I lost track of the current t420 and x220 statuses, being more interested in 9elements work to port coreboot 4.11 correctly for those boards with VBOOT+measured boot with IFD and ME cleaned out so we have enough space to do interesting things for those boards.

We might as well open an issue to track who tests what hardware. That would be really helpful.

[MrChromebox]

Installers for both Qubes 4.0.3 and 4.1-20200113 boot fine on a Librem 13v4 running Heads master (bcf522c) + the handful of branding changes from Purism's tree. Given the display artifacts, there's at least an IOMMU config issue at play, perhaps more. I'd start by adding intel_iommu=igfx_off to the x220's coreboot config CONFIG_LINUX_COMMAND_LINE param, which both the x230 and Librems already use. That param only affects the Heads payload, not any kexec'd kernels.

[tlaurion]

See here

[tlaurion]

Personally, I would remove the quiet there for all the boards.

[MrChromebox]

Personally, I would remove the quiet there for all the boards

I'll push a PR after testing

[MrChromebox]

Personally, I would remove the quiet there for all the boards.

hmm, it's pretty verbose w/o 'quiet' and not in a particularly useful way

[tlaurion]

Agreed. Tested too. Nope!

@MrChromebox @tlaurion thanks, i just woke up, now i will reflash my laptop today.

Also changed chip to Winbond W25Q64.V and added iomem=relaxed

[tlaurion]

@0rb677 I wouldn't recommend 4.1:
QubesOS/qubes-doc#828

Fedora-25 on dom0 is not problematic, all needed packages are backported and all your actions should be in AppVMs, not dom0 anyway.

I would stick to 4.0.3 if I were you.