Linux kernel signing process
Linux kernel signing process
Hi! Your laptop's BIOS got damaged a year ago due to an unstable Ubuntu kernel. I won’t go into the specifics, but you almost fixed it using the provided guide: https://bugs.launchpad.net/ubuntu/+sourc...ug/1734147. The main issues are that the kernel isn’t signed and secure boot can’t be disabled because of the corrupted BIOS. You might need to sign the kernel yourself, but your current tools can’t access the EFI system partition for signing. Do you have any other options or alternatives in mind?
You're asking about the specifics of a BIOS issue. It sounds like you're trying to understand what's happening when your system fails to load properly. Can you clarify if you're experiencing any error messages, a boot loop, or unusual behavior during startup? Knowing more details will help pinpoint the problem.
The bios is damaged in two ways: 1. I can't save any configurations, so I'm limited to what existed before the corruption. 2. The EFI section or something similar is also corrupted, meaning I can't write to it or use it. My Grub2 was there too and got affected, leaving me with a minimal text-based editing experience. I managed to boot from a live USB into Ubuntu and even installed it on the laptop, getting into Grub2 from a standard partition instead of EFI. I'm unsure if my approach was reasonable, but I can now access Ubuntu from a live USB and install it on the laptop. My goal is to get into Grub2 from a regular partition, not EFI. I don't know if I did that correctly, but I'm open to suggestions. Please feel free to share any logs or details that might help. Thank you for your assistance and I hope this resolves the issue.
The system logs errors when using efi-readvar -v KEK, indicating a breach of secureboot. This suggests unauthorized access or tampering during the USB boot process.
I've included images demonstrating the process of booting from a USB into Ubuntu. There are several screenshots available, including one showing the USB boot sequence and another displaying the EFI-readvar command output. The fourth image captures the kernel signing attempt, which encountered errors. If you'd like, I can walk through the steps again to clarify what happened.
You mentioned you can't save settings. Are you sure you can access the BIOS to check them? What happens if you try to modify or save settings then? Did you attempt to reset the CMOS on your laptop? If you want to review your boot logs, "journalctl -xb" might provide helpful details. Honestly, if your boot partition is damaged or the kernel is broken, it might not be worth trying to fix it. You could instead use a live USB to back up your data, save your configurations, and reinstall after formatting. Is there a reason this isn't possible for you?
Hello, the issue and its symptoms are outlined here: https://bugs.launchpad.net/ubuntu/+sourc...ug/1734147. There’s no error when saving BIOS settings, but they don’t persist. Clearing CMOS won’t help, and starting the laptop normally works—either via the minimal GRUB or by selecting Windows Boot Manager. I don’t have any critical data on the machine, and wiping the drive isn’t advisable since it could render the device unusable. I’m aiming to fix the BIOS so the system runs smoothly. I’m almost there; the only hurdle is secure boot remains enabled, and I can’t modify it right now due to corruption.
It's strange you're missing Canonicals keys in your EFI settings, and it seems the 4.18 kernel won't boot either. The absence of the "manufacturer" key is preventing you from saving BIOS configurations. Could you tell me what system you were using when you installed the 4.15 kernel, the 4.18 release, or a USB boot drive?
I placed it on the 4.18 edition (it came from a USB drive, though it was a complete setup)