Control: tag -1 - wontfix
On Sun, 2013-05-12 at 07:59 +0200, Christian PERRIER wrote:
> reassign 707844 debian-installer
> tags 70784 wontfix
> thanks
>
> Quoting Salvo Tomaselli (tiposchi@tiscali.it):
> > Package: di-utils
> > Version: 1.92+deb7u1
> > Severity: minor
> >
> > Dear Maintainer,
> > I've downloaded Debian 7.0 to use in a virtual machine.
> >
> > I downloaded an amd64 image, and by mistake used qemu for i386.
> >
> > I had the normal grub and then when selecting whether I wanted graphical
> > or normal installation, it would just hang and do nothing.
This would actually be syslinux (GRUB is only used in the installer for
UEFI boot).
> > When trying to do an "expert install" it finally showed me what was
> > going on, and I could start qemu with the appropriate command line.
> >
> > Could you make it print an error message in these cases, for any kind
> > of chosen kind of installation?
> > If a CD doesn't do anything but just hangs I could assume there is
> > something wrong with it, or the problem lies somewhere else.
>
> That happened to me sometimes also, indeed.
>
> Well, it's a chicken and egg problem.
>
> To print something, you need a minimal system able to print
> something (and make the minimal checks about host architecture). So you need a kernel....but this is precisely the kernel
> that hangs when you boot an amd64 kernel on a non 64-bit machine.
>
> The fact that it "hangs" silently is because by default the kernel is
> booted with the "quiet" option so that very verbose boot messages are
> silented out. This is a design choice (and this is why you get these
> messages when booting in expert mode).
This has nothing to do with 'quiet', as that does not suppress error
messages.
> I don't think we can do more than we're already doing.
The kernel already does this. When I run:
kvm -cpu pentium2 -kernel /boot/vmlinuz-3.2.0-4-amd64 -append quiet
the kernel prints:
This kernel requires an x86-64 CPU, but only detected an i486 CPU.
Unable to boot - please use a kernel appropriate for your CPU.
But this is printed through BIOS calls and doesn't appear to work when
the display has been switched to framebuffer mode (as syslinux does).
If I use 'Expert install' (or 'Graphical expert install') instead of the
regular 'Install' option, syslinux switches back to text mode before
booting the kernel, and the kernel error message can be seen.
Ben.
--
Ben Hutchings
Always try to do things in chronological order;
it's less confusing that way.
Attachment:
signature.asc
Description: This is a digitally signed message part