No fallback kernel #66
No reviewers
Labels
No labels
P0
P1
P2
P3
audio
bakery
boot
breadbug
bug
build
ci
dependencies
design
disk
docs
encryption
final
firewall
graphics
hardware
idle
installer
keybinds
nvidia
packages
phase-1
polish
recovery
reliability
reproducibility
secure-boot
security
shell
signing
snapshots
supply-chain
swap
tech-debt
theming
ux
website
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Breadway/bos!66
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/bos-33-fallback-kernel"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Stages a signed
linux-ltspackage in an installer-only ISO cache, installs it into the target before mkinitcpio and GRUB generation, and saves its kernel with sbctl after the Secure Boot finalizer when keys exist.Verified with shell syntax and diff checks, a successful
FAST_BUILD=1ISO build, an offline package-install simulation from the built ISO, initramfs generation, GRUB configuration containing LTS entries, and a QEMU boot of the LTS kernel and initramfs to the BOS tty login prompt. The LTS package is cached in the live ISO but is not installed in its package database.A full GUI Calamares install was not exercised because desktop control could not connect to Hyprland. BOS-24 PR #54 remains open; the separate signing step runs after its finalizer. BOS-32 follow-up must select DKMS and provide headers for both installed kernels.
Closes #33
PR #66 is linked to BOS-33. The independent reviewer hit its usage limit before completing review. Returning this PR card to TODO to match the parent pending review and VM-install acceptance.
PR #66 has the implementation and offline package/initramfs/GRUB checks recorded on the rebased head. The full Calamares install and selecting the LTS entry from installed GRUB remain outstanding; BOS has no ordinary push CI. Moving the implementation to REVIEW for the requested handoff. Do not treat as verified or done until those acceptance checks are recorded.