Skip to content

Boot failure in Legacy BIOS mode after remixing with Cubic : initrd name hardcoded in core.img #346

@melodie11

Description

@melodie11

Hello,

I recently remixed AnduinOS using Cubic, and met with a boot failure in Legacy BIOS mode.

After investigation and a detailed exchange with PJ-Singh-001, the developer of Cubic, the root cause has been identified.

Please refer to the full exchange here: PJ-Singh-001/Cubic#480

In summary:
Cubic correctly updates the text grub.cfg file with initrd.gz.

However, AnduinOS generates a binary boot image isolinux/core.img using grub-mkstandalone, which embeds the original grub.cfg with initrd hardcoded (without extension).

This binary file is used when booting in Legacy BIOS mode, and it cannot be easily edited after the fact.

As a result, booting in UEFI mode works fine (the text grub.cfg is used), but booting in Legacy BIOS mode fails with "initrd not found".

My workaround has been to duplicate initrd.gz as initrd (without extension) in the /casper directory using Isomaster, after the ISO is generated by Cubic.

With both files present, the ISO boots successfully in both contexts.

Since you are currently working on the 26.04 version, this would be nice if you could build it in a way that works in both cases.

A fix in your build script could be to copy initrd.gz as initrd in the /casper directory during the generation of the ISO, I guess, to cover both boot contexts without any further intervention when remixing AnduinOS with Cubic?

Thanks for your work, and best regards!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions