On Sun, Nov 30, 2008 at 11:33:41AM +0100, Christian Perrier wrote: > (CC to people I need specific input from) > > Please find attached a proposal for an update to the errata file, > taking care to remove outdated issues and add new ones. > > Please comment: for some of these, I wrote the entry quite blindly... > > Bastian: please check the s390 entries.... > > Jurij: same request for Sparc
Looks good. There is also an issue with installs from terminal which I'm encountering on my box: presumably, due to lack of kernel framebuffer support for Expert3D line of graphic cards (commonly found in SunBlade 1000/1500/2500), the console remains in some kind of dumb mode, in which the installer is all black-and-white and the highlighted item on the menu cannot be seen. Installer is functional though, and I hope that this is just due to some missing config options in the kernel [0]. I plan to build a modified kernel to test this fix. [0] http://lists.debian.org/debian-sparc/2008/10/msg00024.html > Martin: same request for the RAID auto-assembling in rescue. > > > -- > > > > > > > #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> > The rescue mode should be used with great care when logical RAID > arrays were in use on the system to rescue. The rescue mode scripts > do arrays auto-assembly, which could lead to data corruption in > case the RAID IDs are invalid. > </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>Fallback languages not used as planned</dt> > <dd> > For some languages (namely Northern Sami and Wolof), a fallback > language different from English should be used. However, only > English is used as fallback for these language. Users choosing > these languages, particularly Northern Sami will be > presented with many screens in English. > </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/401435";>#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: no installation from floppy disk</dt> > <dd> > 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. > </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> > --- errata.wml 2008-11-27 20:56:02.313635674 +0100 > +++ errata-new.wml 2008-11-30 11:29:31.789334574 +0100 > @@ -1,26 +1,22 @@ > #use wml::debian::template title="Debian-Installer errata" > #use wml::debian::recent_list > > -<h1 id="lenny-rc1">Errata for lenny release RC1</h1> > +<h1 id="lenny-rc1">Errata for lenny release RC2</h1> > > <p> > -This is a list of known problems in the lenny RC1 release of > +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>Outdated Installation Guide on installation media</dt> > + <dt>Auto-assembly of RAID arrays in rescue mode can corrupt data</dt> > <dd> > - The copy of the Installation Guide that's included on > - installation media is outdated. Users are suggested to use > - <a href="http://www.debian.org/releases/lenny/installmanual";>the > updated copy on the website</a>. > - </dd> > - <dt>Multiarch CD boots the AMD64 installer directly</dt> > - <dd> > - The multiarch CD doesn't show the boot menu but rather boots directly > - into the AMD64 installer (Bug #505243). > + The rescue mode should be used with great care when logical RAID > + arrays were in use on the system to rescue. The rescue mode scripts > + do arrays auto-assembly, which could lead to data corruption in > + case the RAID IDs are invalid. > </dd> > <dt>Corrupted display of messages in Dzongkha installs</dt> > <dd> > @@ -38,16 +34,6 @@ > presented with many screens in English. > </dd> > > - <dt>Marvell disk controllers not supported in CD-ROM media</dt> > - <dd> > - Due to a missing pata-modules package on i386 and amd64 media, > - peripherals driven by Marvell disk controllers are not detected. > - As a workaround, you can manually download the > - udeb package for <a > href="http://http.us.debian.org/debian/pool/main/l/linux-kernel-di-i386-2.6/pata-modules-2.6.26-1-486-di_1.72_i386.udeb";>i386</a> > or <a > href="http://http.us.debian.org/debian/pool/main/l/linux-kernel-di-amd64-2.6/pata-modules-2.6.26-1-amd64-di_1.72_amd64.udeb";>amd64</a>, > put it on a removable > - medium and manually install it with 'udpkg -i' from the second > - console. Then run 'depmod -a ; modprobe pata_marvell'. > - </dd> > - > <dt>Disk devices may change on reboot</dt> > <dd> > On systems with multiple disk controllers, the kernel/udev may assign > @@ -105,7 +91,7 @@ > switches to the next kernel version. > </dd> > > - <dt>powerpc: various issues</dt> > + <dt>PowerPC: various issues</dt> > <dd> > The PowerPC port has several issues in this release: > <ul> > @@ -118,11 +104,22 @@ > </ul> > </dd> > > - <dt>sparc: fails to recognize ESP/FAS SCSI controller</dt> > + <dt>Sparc: various issues</dt> > <dd> > - 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. > + 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> -- Jurij Smakov [EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
