Bug#421338: this ia64/amd64 issue comes up really often.
reassign 421338 debian-installer
thanks
On Mon, Apr 30, 2007 at 11:09:12AM +0200, Geert Stappers wrote:
> reopen 421338
> submitter 421338 !
> retitle 421338 this ia64/amd64 issue comes up really often
> reassign 421338 efi-reader
> severity 421338 wishlist
> thanks
> Op 29-04-2007 om 18:58 schreef Eddy Petri??or:
> > Geert Stappers wrote:
> > > Op 29-04-2007 om 14:28 schreef Eddy Petri??or:
> > >> Julien BLACHE wrote:
> > >>> Apple machines aren't ia64, they're i386/amd64 machines.
> > >>> So, you used the wrong architecture, grab an i386 or amd64
> > >>> installation media instead.
> > >> Maybe we could add a warning in the ia64 images
> > >> when such an image is used on an amd64 machine;
> > > Please elaborate your proposal.
> > what's not clear?
> > if you try to boot an ia64 image and it fails, the error message should
> > suggest (if clear detection is not possible) that the user might be
> > trying to boot the wrong type of image and maybe he/she should try an
> > amd64 image which is the proper image for Intel Core 2 processors
> It would be nice if the string
> "Error: unsupported while loading bootia64.efi"
> would be changed in
> "Error: unsupported while loading bootia64.efi. Try an amd64 image"
FWIW, I have some prelim code which allows putting both an x86 and an ia64
el torito boot image on an ISO and booting the correct one per architecture.
Perhaps it would be worth creating a stub el torito image that pops up an
explanation, and shipping it on the ia64 images.
I imagine efi-reader is the wrong package for this, you'll never get to the
point of seeing an error message from a udeb if the kernel itself isn't
bootable. Reassigning to debian-installer, though ultimately debian-cd may
be the right place for it.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
vorlon@debian.org http://www.debian.org/
Reply to: