On 11/18/2014 12:00 PM, ClairelyClaire wrote:
> ETA: whether or not the 64-bit OS can make calls to the 32-bit
> UEFI doesn't prevent the OS from booting.
Actually, it does. It has to call on the UEFI firmware to obtain the
system memory map. Then of course, the installer has to make uefi
calls to point the boot catalog at grub.
So, you booted the 64 bit cd, and manually installed 32 bit grub? And
that worked fine, including being able to run efibootmgr? If so then
I guess the kernel is smart enough to thunk the 32 bit firmware calls
and so adding the 32 bit signed grub to the 64 bit cd should be fairly
simple.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/18/2014 12:00 PM, ClairelyClaire wrote:
> ETA: whether or not the 64-bit OS can make calls to the 32-bit
> UEFI doesn't prevent the OS from booting.
Actually, it does. It has to call on the UEFI firmware to obtain the
system memory map. Then of course, the installer has to make uefi
calls to point the boot catalog at grub.
So, you booted the 64 bit cd, and manually installed 32 bit grub? And
that worked fine, including being able to run efibootmgr? If so then
I guess the kernel is smart enough to thunk the 32 bit firmware calls
and so adding the 32 bit signed grub to the 64 bit cd should be fairly
simple.
-----BEGIN PGP SIGNATURE-----
Ua6qMAAoJEI5FoC IzSKrw81QH/ AvS+DgXni/ jsrsLPe/ cX/mb WgV6fcLZnbMnewi ISgqbc6bN5DhTlC 7ASdW1XK1+ xNSDbLv1Z 075b7LiWF+ aJjcpJ4uyLEgrwO aGyvQtKbE2WkZw5 RSvPMTeo/ 2wEmw7P Q0WCDTeGAokFpcA 83IOTpkrPvH6li2 0h1Qx2izK+ 1k7E79FTe leZq21lFbmMavb+ hbzFGXiHXaDzjip 2Dy7ukOeffOD4Af HxZ+ NYWdwBTSh8ZRLmc 2uLzDHXFoJ+ rWGAegdtK/ Rnk2efESjV4I=
Version: GnuPG v2.0.17 (MingW32)
iQEcBAEBAgAGBQJ
P7vutk5QnX5voyz
jz9oLRY+
x6ZudcRxXqBFL4t
RbN96CCnBCbm4LX
sYXm0VYl8Q0OkXe
=wbmI
-----END PGP SIGNATURE-----