composefs: Type 1 kernel path on the ESP is too long for HP G10 firmware, boot hangs

Open
#2,585 8 comments 4 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
49/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
linux, rust

Research direction

Start by tracing how the composefs backend creates the Type 1 kernel directory and loader entry; the issue does not name source files or tests. The evidence points to the ESP path length as the cause: shortening the directory lets the same kernel boot on affected HP G10 firmware. Done means choosing and implementing a path that avoids the reported hang, then validating it on the affected hardware.

Written by the indexing model from the issue text.

Description

What happened?

On several HP G10 business laptops, firmware hangs (black screen, hard lock) when systemd-boot loads the kernel from the Type 1 directory that the composefs backend writes to the ESP. Every stock install produces a path like this:

/EFI/Linux/bootc_composefs-<128 hex verity>/vmlinuz

That is 163 characters. Reporters in projectbluefin/dakota#1648 bisected the limit by truncating the directory name by hand: a 160 character kernel path boots, 163 hangs. The kernel, initrd and kernel arguments were unchanged, only the directory was renamed.

Affected so far:

  • HP EliteBook 845 G10 (AMD, BIOS V82)
  • HP EliteBook 840 G10 (Intel graphics)
  • HP ZBook Firefly 14 G10 A

We ship Dakota with --composefs-backend and systemd-boot by default, which is probably why this has not shown up elsewhere.

Loader entries

Original entry generated by bootc (hangs):

title Bluefin
version 20260921
linux /EFI/Linux/bootc_composefs-023cf0e317ee0f30a2f8229ed4734a136a406ed38e46abc7406948c732f23071a7b13ca652775b32d540c8b7eaba8f540fb0f479f39527fd2d2ef05094d2e050/vmlinuz
initrd /EFI/Linux/bootc_composefs-023cf0e317ee0f30a2f8229ed4734a136a406ed38e46abc7406948c732f23071a7b13ca652775b32d540c8b7eaba8f540fb0f479f39527fd2d2ef05094d2e050/initrd
options root=LABEL=root rw composefs=023cf0e317ee0f30a2f8229ed4734a136a406ed38e46abc7406948c732f23071a7b13ca652775b32d540c8b7eaba8f540fb0f479f39527fd2d2ef05094d2e050 <image kargs> rd.luks.name=<uuid>=root
sort-key bootc-bluefin-dakota-0

Longest entry that boots, with the last three hex characters of the directory removed (160 characters):

linux /EFI/Linux/bootc_composefs-023cf0e317ee0f30a2f8229ed4734a136a406ed38e46abc7406948c732f23071a7b13ca652775b32d540c8b7eaba8f540fb0f479f39527fd2d2ef05094d2e/vmlinuz
initrd /EFI/Linux/bootc_composefs-023cf0e317ee0f30a2f8229ed4734a136a406ed38e46abc7406948c732f23071a7b13ca652775b32d540c8b7eaba8f540fb0f479f39527fd2d2ef05094d2e/initrd

A fully short directory (/EFI/Linux/bootc_composefs-dakota/) also boots.

I don't have one of these machines myself, but I can build a Dakota image with a candidate fix and ask the reporters in #1648 to verify it on the affected hardware.

Versions
  • bootc v1.17.1
  • systemd-boot, Type 1 BLS entries, composefs backend
  • Image: ghcr.io/projectbluefin/dakota:stable
Dominant language
Rust
Stars
2.3k
Forks
230
Avg merge
2d 11h
Merged PRs (30d)
42

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bootc-dev/bootc

All issues in bootc-dev/bootc

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.