Re: replace memtest86+ with pcmemtest, needs maintainer

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On 8/30/21 9:35 PM, Gordon Messmer wrote:
> On 8/30/21 12:08 PM, Hans de Goede wrote:
>>
>> I checked the entry on a Windows multiboot system and it does not have the
>> "insmod chain" line, maybe droppint that helps?
> 
> 
> Same result.  GRUB returns immediately to its menu.  I'm certain the path is correct, because GRUB will report an error if it is wrong.

So I took a quick look myself and I could not get this to work either,
the EFI binary is weird and the talk of "Linux handoff protocol" in the
README makes me think that the grub menu entry actually should look
like this:

	linux <path>/pcmemtest.efi

I tried that, with Fedora's grub but it does not work either
(the screen goes black IIRC).

Still I believe this is how it is supposed to work, also because
of this:

[root@x1 ~]# file /boot/efi/EFI/fedora/pcmemtest.efi 
/boot/efi/EFI/fedora/pcmemtest.efi: Linux kernel x86 boot executable bzImage, version \353fHdrS\014\002, RW-rootFS,

I believe this is not working with Fedora's EFI grub binaries
because we patch grub to not use the handover protocol when
running in EFI mode. The Linux x86_64 vmlinuz image actually
has an EFI stub, so that it can be executed as an EFI
executable without needing a bootloader at all. And AFAIK that
stub actually works better / on more hw then letting grub
do the BIOS oriented handover-protocol thingie on EFI.

So the Fedora EFI grub is patched to treat a "linux" line
as a chainload line (more or less) with the exception of
doing some stuff to pass the cmdline + initrd.

It might be interesting to try and using e.g. an EFI
grub binary from Ubuntu with a:

	linux <path>/pcmemtest.efi

menu entry, to confirm my theory and after that it is probably
best to reach out to pcmemtest's upstream about this.

Regards,

Hans



p.s.

Note that pcmemtest does not really seem to be a "proper"
EFI app instead it just contains the bare essentials to run,
but e.g. keyboard input does not work unless the BIOS compat
module of the EFI is enabled, which now a days usually it is
not. So I'm afraid that getting this ready will require a
fair amount of work.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux