Errata for Bullseye RC 3
This is a list of known problems in the Bullseye RC 3 release of the Debian Installer. If you do not see your problem listed here, please send us an installation report describing the problem.
- Broken rescue mode with the graphical installer
- It was discovered during Bullseye RC 1 image testing that
the rescue mode seems broken (#987377).
Additionally, the “Rescue” label in the banner needs to be
adjusted for the Bullseye theme.
Status: Fixed in Bullseye RC 2.
- amdgpu firmware required for many AMD graphic cards
- There seems to be a growing need to install amdgpu firmware
(through the non-free
firmware-amd-graphicspackage) to avoid a black screen when booting the installed system. As of Bullseye RC 1, even when using an installation image that includes all firmware packages, the installer doesn't detect the need for that specific component. See the umbrella bug report to keep track of our efforts.
Status: Fixed in Bullseye RC 3.
- Firmwares required for some sound cards
- There seems to be a number of sound cards that require loading a firmware to be able to emit sound. As of Bullseye, the installer is not able to load them early, which means that speech synthesis during installation is not possible with such cards. A possible workaround is to plug another sound card which does not need such firmware. See the umbrella bug report to keep track of our efforts.
- Desktop installations may 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.
- LUKS2 is incompatible with GRUB's cryptodisk support
- It was only lately discovered that GRUB has no support for
LUKS2. This means that users who want to use
GRUB_ENABLE_CRYPTODISK and avoid a separate,
unencrypted /boot, won't be able to do so
setup isn't supported in the installer anyway, but it would
make sense to at least document this limitation more
prominently, and to have at least the possibility to opt for
LUKS1 during the installation process.
Status: Some ideas have been expressed on the bug; cryptsetup maintainers have written some specific documentation.