Closed nianyush closed 8 months ago
If secureboot is enabled, just the booting of the iso means that the keys are ok, otherwise with secureboot enabled and no custom keys, the iso would not even load (systemd-boot in the iso is signed with the same custom keys) so the key enrollment does not seem to be the problem here, unless secureboot is not enabled?
If secureboot is disabled then yeah, it doesnt seem to be installing the keys directly.
@nianyush can you check if secureboot is enabled on the firmware?
If it is then it may be a size issue that the firmware is not properly dealing with somehow. Is there any firmware updates for it? What year is the firmware from?
@Itxaka secure boot is enabled and i have installed keys manually. Its supermicro x10 series
EFI image size is 771MB
@nianyush this was Ubuntu right? @mudler said you tried with Fedora and it worked. What was the size of the Fedora version? If it was smaller than 771Mb it's probably the size of the image again.
@jimmykarily yes, i can confirm that this is related to size issue. Fedora image is around 260MB.
closing then as it is a Firmware/Hardware issue as we can't really do anything about it for the moment
Kairos version:
CPU architecture, OS, and Version:
Describe the bug
I tried both auto-enroll and manually enrolling the keys via BIOS on a supermicro box, but neither of them worked. The behavior is that after I choose the boot entry to install mode, it just went into black screen for 3-4min and then automatically rebooted And after reboot, i could not see any bootable medium other than the installer iso itself. To Reproduce
Expected behavior
Logs
Additional context