From: Mate Kukri <mate.kukri@canonical.com>
To: Tobias Powalowski <tobias.powalowski@googlemail.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: BUG: Bisection finished: Re: Cannot boot from IA32 system a 64bit x86_64 kernel.
Date: Thu, 4 Sep 2025 13:29:12 +0100 [thread overview]
Message-ID: <CAAfJHtrTcP-TxqMvGZzoRwiQGFzgYbf0t8_HVVLd8hBJfMyOEQ@mail.gmail.com> (raw)
In-Reply-To: <da65d6cb-eee2-43df-8af6-186f78a2b1d6@googlemail.com>
I am not 100% against keeping 32-bit EFI support but there is no
reason to try debugging NX on it, just ifdef it out in GRUB, it is a
broken mess of a platform that won't get better.
On Thu, Sep 4, 2025 at 11:05 AM Tobias Powalowski
<tobias.powalowski@googlemail.com> wrote:
>
> Am 04.09.25 um 11:57 schrieb Mate Kukri:
> > Are you really running on 32-bit IA32 UEFI? Because that is legacy and
> > deprecated and runs with paging disabled and never had nor ever will
> > have NX support.
> >
> > So it should probably have NX compiled out in GRUB anyways, I don't
> > think any UEFI grub maintainers test 32-bit IA32 UEFI these days
> > because it is a dead platform.
> >
> Well there are still some old boards with such setups out there.
>
> I don't own any of those physically, so my only way to test this for
> archboot is the qemu way.
>
> EDK2 OVMF with qemu-x86_64-system. My project and Arch Linux itself
> supports x86_64 machines from 2007 up to now.
>
> I think some popular Surface or Intel Macs had this combination of
> UEFI-32 and not UEFI-64.
>
> Sure in the future, I'll strip out the UEFI MIX MODE and I don't have to
> care about it anymore.
>
> Best regards
>
> Tobias
>
> --
> Tobias Powalowski
> Arch Linux Developer (tpowa)
> https://www.archlinux.org
> tpowa@archlinux.org
>
> Archboot Developer
> https://archboot.com
>
> St. Martin-Apotheke
> Herzog-Georg-Str. 25
> 89415 Lauingen
> https://www.st-martin-apo.de
> info@st-martin-apo.de
>
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
next prev parent reply other threads:[~2025-09-04 12:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-31 15:26 Cannot boot from IA32 system a 64bit x86_64 kernel Tobias Powalowski via Grub-devel
2025-09-02 21:03 ` BUG: Bisection finished: " Tobias Powalowski via Grub-devel
2025-09-03 4:55 ` Glenn Washburn
2025-09-03 6:06 ` Tobias Powalowski via Grub-devel
2025-09-03 16:09 ` Tobias Powalowski via Grub-devel
2025-09-04 9:14 ` Tobias Powalowski via Grub-devel
2025-09-04 9:57 ` Mate Kukri
2025-09-04 10:05 ` Tobias Powalowski via Grub-devel
2025-09-04 10:49 ` Toomas Soome via Grub-devel
2025-09-04 12:29 ` Mate Kukri [this message]
2025-09-03 9:11 ` Mate Kukri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAfJHtrTcP-TxqMvGZzoRwiQGFzgYbf0t8_HVVLd8hBJfMyOEQ@mail.gmail.com \
--to=mate.kukri@canonical.com \
--cc=grub-devel@gnu.org \
--cc=tobias.powalowski@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).