[SOLVED] did I lock myself out of passing kernel parameters??

seth · 2025-08-26 20:46:05

https://0x0.st/KomW.txt
The only thing w/ a recent timestamp is /boot/efi/loader - I'd assume you did not correctly mount the partition when chrooting into the system and before regenerating the UKI?

Moonveil · 2025-08-26 20:52:27

I mounted it the same way I did when I started installing the OS. I opened the luks partition and then mounted the two partitions. It's possible I did it wrong but I don't know how I should have done it otherwise, I'm still learning. I was able to chroot and reach all my files from the archiso

Last edited by Moonveil (2025-08-26 20:53:27)

seth · 2025-08-26 20:57:40

You, Today 18:44 UTC wrote:

Afterwards it created the image file /boot/efi/EFI/Linux/bootx64.efi without any error.

/boot/efi/EFI/Linux:
total 62816
-rwxr-xr-x 1 root root 64323192 Aug 25 12:15 bootx64.efi

There's an obvious disparity here and the most likely explanation is that the UKI wasn't created in the correct location.
If you umount nvme0n1p1, are there any files in/boot/efi ?

Moonveil · 2025-08-26 21:05:08

Yes, /boot/efi/EFI/Linux/bootx64.efi is still there if I umount /dev/nvme0n1p1. The rest is gone

https://0x0.st/KomI.txt this is what is left after the umount

Last edited by Moonveil (2025-08-26 21:08:31)

seth · 2025-08-26 21:31:57

Look at the timestamp - you think /that's/ the file you created?
Have you tried to regenerate the UKI from the actual system (no chroot) while nvme0n1p1 is mouted into /boot/efi?

Moonveil · 2025-08-26 21:35:09

seth wrote:

Look at the timestamp - you think /that's/ the file you created?

That's the one I created earlier in chroot when I used pacman -S Linux

Have you tried to regenerate the UKI from the actual system (no chroot) while nvme0n1p1 is mouted into /boot/efi?

I have not. How do you do that?

seth · 2025-08-26 21:55:41

https://bbs.archlinux.org/viewtopic.php … 5#p2258655

I used pacman -S Linux.
I had one package that was required to install 6.16.3-arch1-1.
It executed dracut --force --uefi --kver "6.16.3-arch1-1" /boot/efi/EFI/Linux/bootx64.efi during the installation and dracut finished without any error.
Afterwards it created the image file /boot/efi/EFI/Linux/bootx64.efi without any error.

Just don't do that from the chroot, though I suspect that the problem w/ the latter was that you mounted nvme0n1p1 into the /boot/efi path of the install iso (ie. before the chroot) or the mount failed because you tried to mount the partition from the chroot but lacked the vfat module?

Moonveil · 2025-08-26 22:04:37

I mounted it before chroot. I haven't done much from chroot before, I'm still learning. I mounted nvme0n1p1 into /boot/exit, unlocked nvme0n1p2, I think it got mounted after that and I chrooted.

I will try running pacman -S linux from konsole and see what happens

That broke it lol.

I'm greeted by orange text talking about amdgpu LOAD_TA01 failed and response status is (0x1).
INVOKE_CMD failed and response status is (0x3)

Red text saying amdgpu: Secure Display: Generic Failure.
Amdgpu: SECUREDISPLAY: query screen display TA failed. Ret 0x0

Orange text timekeeping watchdog on CPU3 marking clocksource 'tsc' as unstable because the skew is too large. TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'.

I haven't even unlocked the disk yet.

It did boot, cat /proc/cmdline is showing ipv6.disabled=1 and lsm=landlock,lockdown,yama,integrity,apparmor,bpf.

aa-enabled
Yes

aa-status
apparmor module is loaded.
162 profiles are loaded.
79 profiles are in enforce mode.
5 profiles are in complain mode.
0 profiles are in prompt mode.
0 profiles are in kill mode.
78 profiles are in unconfined mode.

That is some progress

Last edited by Moonveil (2025-08-26 22:24:06)

Arch Linux

#26 2025-08-26 20:46:05

Re: [SOLVED] did I lock myself out of passing kernel parameters??

#27 2025-08-26 20:52:27

Re: [SOLVED] did I lock myself out of passing kernel parameters??

#28 2025-08-26 20:57:40

Re: [SOLVED] did I lock myself out of passing kernel parameters??

#29 2025-08-26 21:05:08

Re: [SOLVED] did I lock myself out of passing kernel parameters??

#30 2025-08-26 21:31:57

Re: [SOLVED] did I lock myself out of passing kernel parameters??

#31 2025-08-26 21:35:09

Re: [SOLVED] did I lock myself out of passing kernel parameters??

#32 2025-08-26 21:55:41

Re: [SOLVED] did I lock myself out of passing kernel parameters??

#33 2025-08-26 22:04:37

Re: [SOLVED] did I lock myself out of passing kernel parameters??

Board footer