Bug#421338: this ia64/amd64 issue comes up really often.

2007-04-30 Thread Geert Stappers
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


Rationalate, courtisity of Eddy Petri??or:

 You can't expect everybody to know how debian called its amd64/x86_64
 architecture. Even the people that are close to debian might not
 know the difference (I know I also was confused). And since Intel
 Core 2 processors are produced by Intel, people *expect* the arch
 to be called something along the lines of i386, i486, and not k6,
 k7 or amd*, so ia64 - oh Intel architecture, 64 bits, that's it
 is the first thing that springs to mind.
 
 This is the reason behind many choices made in all kinds of places
 which are taken on the account of the element of the least surprise.
 
 Not knowing the history of the x86_64 arch is NOT plain ignorance. You
 can't expect everybody to know such things.
 
 I appreciate what Debian wanted to do (pay a tribute to amd), but we
 have to admit the choice backfired. I would be really curious about
 some comparative graphs about the downloads of the ia64 images around
 the release of etch and around the release of sarge (also in comparison
 with i386, amd64 and other images)... I wouldn't be surprised if there
 was a big difference since Intel Core 2 processors became more common
 place during sarge's lifetime and is *easy* to make the wrong choice...



The reassign to 'efi-reader' was to get this BR away from
'installation-reports', but I couldn't find the efi bootloader


Cheers
Geert Stappers



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#421338: this ia64/amd64 issue comes up really often.

2007-04-30 Thread Steve Langasek
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.
[EMAIL PROTECTED]   http://www.debian.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Processed: Re: Bug#421338: this ia64/amd64 issue comes up really often.

2007-04-30 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 reassign 421338 debian-installer
Bug#421338: this ia64/amd64 issue comes up really often
Bug reassigned from package `efi-reader' to `debian-installer'.

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]