Debian-Installer errata
Errata for Wheezy Release Candidate 3 release
This is a list of known problems in the wheezy Release Candidate 3 release of the Debian Installer. If you do not see your problem listed here, please send us an installation report describing the problem.
- Installation of GRUB bootloader may fail if more than one disk device is available.
- When there is more than one disk available during installation
(for example one hard disk and one USB stick, as it is commonly the case when
booting the installer from a USB stick),
grub-installmay run into problems: it was reported several times, that the GRUB bootloader was installed onto the USB stick instead of the hard disk containing the newly-installed system.
To avoid running into this, make sure to answerNo
when the following question is asked during the installation process:Install the GRUB boot loader to the master boot record?
; it should be possible to specify the right device at the next step:Device for boot loader installation
.
If the installation finished successfully despite a wrong GRUB configuration, it should be possible to recover using the rescue mode of the installer: chroot into the root filesystem, mount any additional boot partition if applicable, and rungrub-installwith the proper device as parameter.
Status: This issue will hopefully be fixed in the first Wheezy point release. - Desktop installations on i386 do not work using CD#1 alone
- Due to space constraints on the first CD, not all of the expected GNOME desktop
packages fit on CD#1. For a successful installation, use extra package sources (e.g.
a second CD or a network mirror) or use a DVD instead.
Status: It is unlikely more efforts can be made to fit more packages on CD#1. - Potential issues with UEFI booting on amd64
- There have been some reports of issues booting the Debian Installer in UEFI mode
on amd64 systems. Some systems apparently do not boot reliably using
grub-efi, and some others show graphics corruption problems when displaying the initial installation splash screen.
If you encounter either of these issues, please file a bug report and give as much detail as possible, both about the symptoms and your hardware - this should assist the team to fix these bugs. As a workaround for now, try switching off UEFI and installing usingLegacy BIOS
orFallback mode
instead.
Status: More bug fixes might appear in the various Wheezy point releases. - Broken grub boot menu entry for Windows 8 in UEFI mode
- The installer automatically searches for other operating
systems to add them to the grub boot menu. When booting in
UEFI mode, the code does not correctly detect the presence of
Windows 8 and will most likely add a menu entry that does not
work. As a workaround, it is possible to add such an entry by
hand.
Status: This bug is fixed in the third Wheezy Release Candidate. - Erroneous firmware prompt with some Intel Wireless cards
- If you have an Intel Wireless 6005 or 6205 card then the installer will
prompt for the firmware file
iwlwifi-6000g2a-6.ucode. This file is not included in thefirmware-iwlwifipackage and is not actually needed. You must answernoto continue with installation.
Status: This issue will hopefully be fixed in the first Wheezy point release. - Missing beep at installer startup
- For accessibility reasons, a beep should be emitted when
the installer’s bootloader is waiting for input. Unfortunately,
a bug made it disappear in the first Wheezy Alpha release, and that
was only reported right before the third Wheezy Release Candidate.
Status: This issue will be fixed in the first Wheezy point release.
