[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#702395: marked as done (debian-installer: When booting with EFI, only the first console works)

Your message dated Sat, 13 May 2017 12:51:00 +0000
with message-id <fd7e3c72-2e6c-5146-2d4a-ae0f0dc5e385@a4nancy.net.eu.org>
and subject line Closing obsolete bug report
has caused the Debian Bug report #702395,
regarding debian-installer: When booting with EFI, only the first console works
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

702395: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702395
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Severity: normal

I just installed a new laptop with the Debian installer rc1.
I put the netinst img raw on a usbkey and boot from it.

First, I boot with the legacy BIOS. Here, the installer works
as always. I can access (with Alt-Fx) to two more consoles
(F2 and F3) and to the log (F4).
As I was using a gpt partition table, my BIOS was complaining
about an invalid partition table (I had to type 'enter' but
then grub-pc loads itself and all was working).

So, I decided to try to boot in UEFI mode. So I use the
installer rc1 from my usbkey again in rescue mode.
And here, only the first console works. When switching to
Alt-Fx x>1, the screen does not change but some glitches
at the top of the screen (the first lines). Comming back
to Alt-F1 remove the glitches and give me hand back.
  I think this is "only" a display problem because I've been
able to type (without anything to see) in the second console
to mount a usbkey to copy a firmware in /lib/firmware (and
creating this directory before). As the wifi driver has been
able to work, it means that my commands have really been


-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message ---
Thanks for having taken the time to report this issue with UEFI in
Debian 7 ("Wheezy").

During last years, UEFI support has improved and we believe this bug is
likely to be solved in the current stable version of Debian 8 ("Jessie")
or in the upcoming Debian Stretch.

I'm thus closing this bug report. If you can reproduce this issue with
Debian 8 installer[1] or better with the release candidate installer for
the upcoming Debian Stretch[2], please file a new bug report.

Thanks again for your contribution!

1. https://www.debian.org/distrib/
2. https://www.debian.org/devel/debian-installer/

--- End Message ---

Reply to: