The errata page hasn't changed since December, when I cooked it and asked for a review. This is probably the last chance to get it fixed in case it's missing something or it has inaccuracies. Please review! --
#use wml::debian::template title="Debian-Installer errata"
#use wml::debian::recent_list
<h1 id="lenny-rc1">Errata for lenny release RC2</h1>
<p>
This is a list of known problems in the lenny RC2 release of
Debian Installer. If you do not see your problem listed here,
please send us an <a href="report-template">installation report</a>
describing the problem.
</p>
<dl class="gloss">
<dt>Auto-assembly of RAID arrays in rescue mode can corrupt data</dt>
<dd>
Rescue mode should be used with great care when software RAID
arrays were in use on the system to rescue. The rescue mode scripts
automatically assemble arrays, which could lead to data corruption in
the presence of invalid or obsolete RAID superblocks.
</dd>
<dt>Marvell disk controllers not fully supported</dt>
<dd>
Due to a pata_marwell module not begin properly autoloaded
on i386 and amd64 media,
peripherals driven by Marvell disk controllers are not detected. If
IDE is used in legacy mode with these controllers, switch to
console 2 when the installer boots (Alt+F2) and
run 'modprobe -r ahci; modprobe pata_marvel; modprobe ahci' before
continuing.
</dd>
<dt>Corrupted display of messages in Dzongkha installs</dt>
<dd>
When the password chosen for root and its confirmations do not
match, the display of screens that follow is garbled, during
installs in Dzongkha language (broken display of italic
font).
</dd>
<dt>Disk devices may change on reboot</dt>
<dd>
On systems with multiple disk controllers, the kernel/udev may assign
a different device node on reboot of the system than was used during
installation due to difference in load order of drivers.<br />
This can lead to failure to boot the system. In most cases this can be
corrected by changing the bootloader configuration and /etc/fstab,
possibly using the rescue mode of the installer.<br />
Note however that this problem may occur again on subsequent boots.
</dd>
<dt>Reboot problems when installing from a USB stick</dt>
<dd>
The former problem may also happen when installing from a USB stick.
Temporarily keeping the USB stick in place will allow you
to boot the installed system and correct the bootloader
configuration file. See
<a href="http://bugs.debian.org/506263";>#506263</a>
for details about such workaround.
</dd>
<dt>Buggy routers may cause network problems</dt>
<dd>
If you experience network problems during the installation, this may be
caused by a router somewhere between you and the Debian mirror that
doesn't correctly handle window scaling.
See <a href="http://bugs.debian.org/401435";>#401435</a> and this
<a href="http://kerneltrap.org/node/6723";>kerneltrap article</a> for
details.<br />
You can work around this issue by disabling TCP window scaling. Activate
a shell and enter the following command:<br />
<tt>echo 0 > /proc/sys/net/ipv4/tcp_window_scaling</tt><br />
For the installed system you should probably not completely disable TCP
window scaling. The following command will set ranges for reading and
writing that should work with almost any router:<br />
<tt>echo 4096 65536 65536 >/proc/sys/net/ipv4/tcp_rmem</tt><br />
<tt>echo 4096 65536 65536 >/proc/sys/net/ipv4/tcp_wmem</tt>
</dd>
<!-- leaving this in for possible future use...
<dt>i386: more than 32 mb of memory is needed to install</dt>
<dd>
The minimum amount of memory needed to successfully install on i386
is 48 mb, instead of the previous 32 mb. We hope to reduce the
requirements back to 32 mb later. Memory requirements may have
also changed for other architectures.
</dd>
-->
<dt>i386: few issues</dt>
<dd>
The i386 port has some known issues in this release:
<ul>
<li>Due to an increase in the size of the 2.6.24 kernel, we are unable
to provide installation images for installs from floppy disk. We
expect to be able to support floppy installs again when the installer
switches to the next kernel version.</li>
<li>We had at least one report about the installer crashing at
the network hardware detection step on some Dell Inspiron laptops.
See <a href="http://bugs.debian.org/509238";>bug #509238</a>
for details. A workaround seems to be booting the installer with
the "vga=771" parameter.</li>
</ul>
</dd>
<dt>PowerPC: various issues</dt>
<dd>
The PowerPC port has several issues in this release:
<ul>
<li>installation from floppy on OldWorld PowerMac is broken
because no device node is created for the swim3 module
and as miboot is not included</li>
<li>the snd-powermac module is no longer loaded by default as
it will lock up some systems; you will need to add it to
<tt>/etc/modules</tt> manually</li>
</ul>
</dd>
<dt>Sparc: various issues</dt>
<dd>
The Sparc port has several issues in this release:
<ul>
<li>Broken serial console support. In some situations
(see <a href="http://bugs.debian.org/504721";>bug #504721</a>
for details), the serial console used may not
be properly re-opened and therefore become non
responding. Passing 'console=ttyS0' (or whichever
device the console is attached to) may we used
as a workaround.</li>
<li>fails to recognize ESP/FAS SCSI controller:
installer images are missing the <tt>sun_esp</tt>
kernel module which is needed to support CD and disc
drives connected to an ESP or FAS controller.</li>
</ul>
</dd>
<dt>s390: unsupported features</dt>
<dd>
<ul>
<li>support for the DASD DIAG discipline is currently not
available</li>
<li>support for LCS network interfaces is no longer available</li>
</ul>
</dd>
</dl>
Attachment:
signature.asc
Description: Digital signature