Archlinux freezes after kexec

[lynxred]

How to disable adding extra kernel options? intel_iommu=on intel_iommu=igfx_off were added to the other from the file grub.cfg. As a result, the system does not load on and freeze on the message Starting new kernel. My system archlinux with luks conteiner. i trying delete quiet option but without a result

[tlaurion]

@lynxred Those options come from the board configuration in ADD_KERNEL boot option. Those are the parameters passed to the final OS cmd line.

What board are we talking about?

[lynxred]

Hi @tlaurion! My board is x230. I am facing the same problem both when booting the OS from the ssd and when installing the OS cube. laptop freeze after the message Starting new kernel.

[lynxred]

I I added the parameters to the config.user file and yes, when they are loaded, they are no longer there. But the laptop freezes at the same step

[tlaurion]

I'm confused about your report on Qubes installer not booting, since I tested a couple of days ago on i5 with latest commit containing microcode updates for both 4.1 and 4.0.4 installer from iso with detached signatures.
The problem at that moment was not booting the iso, but getting past Qubes welcome screen and clicking continue. On i5, microcode updates were needed to have Qubes pass the vmx tests on reported present extensions from Xen.

Can you flash CircleCI build to confirm its not the locally built ROM that is at fault?

Are you booting from ISO or dd'ed image?

[lynxred]

I try in dd and use iso file https://ftp.qubes-os.org/iso/Qubes-R4.1.0-x86_64.iso

[tlaurion]

I I added the parameters to the config.user file and yes, when they are loaded, they are no longer there. But the laptop freezes at the same step

So we can agree that those parameters are not at fault

[lynxred]

So we can agree that those parameters are not at fault

and now I don't understand what the problem is

[lynxred]

I I added the parameters to the config.user file and yes, when they are loaded, they are no longer there. But the laptop freezes at the same step

So we can agree that those parameters are not at fault

Now I am compiling your forked repo. I'll let you know the results later

[tlaurion]

The reason I prefer booting with iso and detached signature is that it confirms there is no integrity problem nor flash memory issue from booted medium.

For Qubes, having the ISO and .asc accompanying file, and booting from USB will validate the integrity and authenticity of the image prior of booting.

For Arch, I would recommend verifying the iso saved on flash media as well from external OS.

I could try to test booting from dd'ed verified qubesos image in the next days, while present hypothesis is probably integrity problem?

On arch already installed on disk, I would love to see the frozen kexec command at the bottom since I'm not a arch user. But Qubes works. I remember having seen other arch issues in the past, have you reviewed them?

[lynxred]

Yes, I've looked at other threads. I can record a video booting from an ssd disk installed archlinux and booting a cube from a flash drive and iso

[tlaurion]

Now I am compiling your forked repo. I'll let you know the results later

Please follow those instructions to test builds from CircleCI.
This is what I tested, so we have the same ROM tested.

linuxboot/heads-wiki#88

[tlaurion]

Now I am compiling your forked repo. I'll let you know the results later

My master is really old, I create branch there and push them as pull requests only. Building that will not represent anything useful!

[lynxred]

Cool! Thanks. And I compile the firmware in a local docker container

[lynxred]

I tried the following firmware:
heads-x230-v0.2.0-1153-gc1409a8.rom: I didn't see any changes in the loading iso. The laptop freeze after the message and then turns off after 5 minutes.
heads-x230-hotp-maximized-v0.2.0-1153-gc1409a8.rom: Ooooops Black screen after flashing.....

[tlaurion]

... Maximized builds need to be externally flashed on both SPI initially, from the two top and bottom flash images, or internally from the 12 mb image once Heads is running on maximized build.

So to get things straight: x230 i5 or i7.
Booting from qubes 4.0.4 being first verified and then dd'ed on USB thumb drive.

Will retest x230 image produced from CI on dd'ed USB drive when I have a chance.

[tlaurion]

HOTP are different the non HOTP in the sense they require HOTP compliant USB security dongles (Librem Key/ Nitrokey pro/ Nitrokey Storage)

[lynxred]

It's normal that hotp has a black screen after loading? Okay... I figured out where my mistake is...

[lynxred]

My board x230 i7. heads-x230-v0.2.0-1153-gc1409a8.rom i try loading ISO file (no dd). I have backup files of the lower and upper chip. Can you tell me how to restore them using raspberry pi?) Can we continue the conversation in my telegram?))

[tlaurion]

No, it's not.

I would suggest flashing x230-maximized build from CircleCI on top and bottom SPI. Those are the most tested ROMs.

x230 rom or x230-hotp-verification ROMs are to be flashed internally from x230-flash.

Your laptop shutdowning after 5 minutes is also not normal. Last time From memory, ME being invalid would shutdown the main CPU after 30 minutes.

From past observed failures of kexec not being able to boot OS kernel and initrd, it normally just hangs there forever.

[tlaurion]

@lynxred

My board x230 i7. heads-x230-v0.2.0-1153-gc1409a8.rom i try loading ISO file (no dd). I have backup files of the lower and upper chip. Can you tell me how to restore them using raspberry pi?) Can we continue the conversation in my telegram?))

Restoring it the other way around.
Flash original 4mb on top SPI, 8mb on bottom SPI.

[lynxred]

I would suggest flashing x230-maximized build from CircleCI on top and bottom SPI. Those are the most tested ROMs.

Good! I try this.
Tell me. Is it possible to flash with raspberry pi? Are there detailed instructions on how to do this?

[tlaurion]

How did you flashed Heads ?

[lynxred]

I updated from the skulls firmware. https://github.com/merge/skulls/tree/master/x230#moving-to-heads

[lynxred]

I dont see x230-maximized build o_O.....
https://app.circleci.com/pipelines/github/osresearch/heads/379/workflows/ad993019-d3bb-4bea-abe7-041e43cd273d

[tlaurion]

I dont see x230-maximized build o_O.....
https://app.circleci.com/pipelines/github/osresearch/heads/379/workflows/ad993019-d3bb-4bea-abe7-041e43cd273d

Damnit. Seems like I forgot to add it back on CI....

[tlaurion]

Tell me. Is it possible to flash with raspberry pi? Are there detailed instructions on how to do this?

Instructions can easily found in the internet

One example is from the Skulls project

https://github.com/merge/skulls/blob/master/x230/README.md

[lynxred]

okay okay) I think it's a good idea to add it to the wiki?)

[tlaurion]

I updated from the skulls firmware. https://github.com/merge/skulls/tree/master/x230#moving-to-heads

Ha. Then having flashed blindly maximized build has caused a brick :/

[lynxred]

-_- I wait x230-maximized build and I'm trying to restore this brick. the laptop was for $50 and I gained experience in many areas)

[tlaurion]

Build happening under #1119

[tlaurion]

Artifacts for x230-maximized board configuration are here: https://app.circleci.com/pipelines/github/tlaurion/heads/978/workflows/ab9dff67-6362-4cca-b46e-b31d25b8508e/jobs/4515/artifacts

Flash top and bottom

[lynxred]

good news! i flashed the bios chips using my raspberry. so. i am testing iso boot and boot my arch
iso boot: working(freeze in boot graphical mose).
usb dd image: working(freeze in boot graphical mode)
my archlinux start: nope.....
Can you help setting boot parameter for my arch?
my arch boot parameter next:

[tlaurion]

@lynxred

Let's do this correctly step by step:

Flashed externally (commit 7601400 as in firmware name):

• https://4515-103208611-gh.circle-artifacts.com/0/build/x230-maximized/heads-x230-maximized-v5.0.1-102-g7601400-bottom.rom
• https://4515-103208611-gh.circle-artifacts.com/0/build/x230-maximized/heads-x230-maximized-v5.0.1-102-g7601400-top.rom

You are now in a clean state (without public key injected, not TPM sealed TOTP/HOTP. Here no HOTP support in).

What interests me here is what is happening and why you can't boot Q4.1 or Q4.0.4, which are the most tested. What is different on your side? Please share screenshots in portrait mode.

1. Power on laptop.
   
2. Validate system info, send capture.
   
3. Here testing i5, but i7 is just the same and was tested previously.
   
4. Boot from Qubes 4.0.4 ISO (with detached signature in the same directory)
   
   
   
   
   
5. Enjoy the installer (kexec call takes approximately 5 seconds prior of screen flickering to Qubes console in the background, then the Qubes logo with a progression bar...)
   

[lynxred]

I flashed 760140

and working in type 7 and freeze type 9

It looks like I need to test the work on other distributions (non-qube). but I think that this topic can be closed since I managed to install the qube os.

[tlaurion]

Qubes OS doesn't even install in basic graphic mode. So totally irrelevant. Not sure why they even propose the option.

[tlaurion]

@lynxred please close after having given short version of what solved the issue for you, or what user error was linked to opening the issue at first place.

Arch is still unfixed AFAIK, while I just gave it a bit of love to boot ISO under #1120

[lynxred]

tell me how to configure boot os with these grub parameters. qube os working but I need archlinux with encrypted root. in attachment screenshot boot parameter

[tlaurion]

@lynxred I have pushed a PR yesterday that fixes the ISO booting from Archlinux under #1120 which is currently under review. That doesn't mean that booting installed Archlinux will work, but that is a good step in that direction.
I am not using Archlinux unfortunately, but have changed the name of your issue to attract other users having the same needs.

At first view of last screenshot, it seems that only intel-ucode is passed as initrd, but I may be talking over my head completely here. The issue #702 covered a bit an issue with Archlinux. You might want to tag other people having reported issues in the past to get some help?

The ISO booting lets us believe that latest installer should include the i915 driver in their provided initrd.
So having the installer do its magic on a clean install might resolve your issue.

Please report back your results for others to jump in under #702

[tlaurion]

As far as I know reading #702, this issue is a duplicate of #702.