[Git-commits] [grml/grml-live] 1a9a78: Rework memtest handling, incl. usage of latest ava...

Michael Prokop noreply at github.com
Mon Oct 16 20:29:28 CEST 2023


  Branch: refs/heads/master
  Home:   https://github.com/grml/grml-live
  Commit: 1a9a788fa46053e882e7332c6403b59ff8d437f1
      https://github.com/grml/grml-live/commit/1a9a788fa46053e882e7332c6403b59ff8d437f1
  Author: Michael Prokop <mika at grml.org>
  Date:   2023-10-16 (Mon, 16 Oct 2023)

  Changed paths:
    M grml-live
    M templates/boot/grub/addons.cfg

  Log Message:
  -----------
  Rework memtest handling, incl. usage of latest available memtest file

If we try to copy the memtest86+.bin file as shipped with memtest86+
versions <=5.01-3.1, we either copy such an old file from the build
directory (grml_chroot), or if that doesn't exist (e.g. because the
memtest86+ package isn't installed), we might end up copying an old
memtest file from the build host system instead.

AS ${BUILD_OUTPUT}/boot/addons/memtest exists already then, we don't
update the file any longer (e.g. from a more recent memtest86+ package),
and therefore end up with an old and outdated memtest version in BIOS
boot, while EFI boot provides a more recent memtest version. This is
inconsistent and unexpected behavior.

So instead try to use the most recent version of memtest86* files first,
and only then fall back to the old memtest86+ <=5.01-3.1 file behavior.

While looking into this, I also noticed that until memtest86+ versions
<=6.10-2 it used to be named memtest86+x32.bin, while as of memtest86+
versions >=6.10-3 it's memtest86+ia32.bin instead. As we have version
6.10-4 in bookworm/stable and only pre-6 version 5.01-3.1 in e.g.
bullseye/oldstable, let's skip any backwards compatibility for
memtest86+x32.bin.

Furthermore while at it, drop duplicate execution of `copy_addon_file
memtest86+x64.bin /boot addons` and `copy_addon_file memtest86+x32.bin
/boot addons` to avoid ending up with further duplicate files on the
ISO. So related to https://github.com/grml/grml-live/issues/128, we now
ship /boot/addons/memtest on each of grml64 + grml32, and respectively
only /boot/addons/memtest86+x64.efi on grml64 only and
/boot/addons/memtest86+ia32.efi on grml32 only. To rename the files into
FAT16/8.3 compatible "/boot/addons/memtest", let's provide a proper
return code from within copy_addon_file() if we couldn't find any
matching file.

Related to https://github.com/grml/grml-live/issues/128

Closes: https://github.com/grml/grml/issues/178


  Commit: e57c3ad94e5fc7a2a4e83ef6c80c0caeb5eedea6
      https://github.com/grml/grml-live/commit/e57c3ad94e5fc7a2a4e83ef6c80c0caeb5eedea6
  Author: Michael Prokop <mika at grml.org>
  Date:   2023-10-16 (Mon, 16 Oct 2023)

  Changed paths:
    M templates/boot/grub/addons.cfg

  Log Message:
  -----------
  templates/boot/grub/addons: use chainloader instead of linuxefi

As of grub2 2.12~rc1-1 the linuxefi module is no longer available:

| grub2 (2.12~rc1-1) experimental; urgency=medium
|
|   [ Julian Andres Klode ]
|   * New upstream version, 2.12~rc1
|   * build-efi-images: Drop linuxefi, using new loaders now
| [...]

So loading the memtest EFI file then fails with:

| error: can't find command `linuxefi'.

Use chainloader instead, to boot into the memtest EFI.


Compare: https://github.com/grml/grml-live/compare/f365415eff8a...e57c3ad94e5f


More information about the Git-commits mailing list