Debian-Installer errata
Errata for Wheezy Release Candidate 1 release
This is a list of known problems in the wheezy Release Candidate 1 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-install
may 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-install
with the proper device as parameter.
This issue will hopefully be fixed in the next Release Candidate. - 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.
This issue will hopefully be fixed in the next Release Candidate. - 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.
These issues will hopefully be fixed in the next Release Candidate.