Re: bug in install
This goes along with a bug report I filed a few months back. The WD7000
auto-probe will cold-lock many systems with an Adaptec SCSI controller(including
2940), but only on certain systems. I suspect this is a BIOS/chipset bug, which
I havn't heard of any firm resolution on. This is a NASTY problem which will
prevent initial installation. There was some talk of ways to work around this,
including using RAMDISK as a way to mount the root filesystem during install and
then selecting which SCSI controller you have, rather than doing a compiled-in
approach to the install kernel image. My own feeling is to just remove the
WD7000 support from the base kernel since I have yet to hear of ANYONE who uses
such a controller. Oh well....
On 6 Jun 1999, Adam Di Carlo wrote:
> Date: 06 Jun 1999 14:08:54 -0400
> From: Adam Di Carlo <firstname.lastname@example.org>
> To: "Phillip R. Jaenke" <email@example.com>
> Cc: firstname.lastname@example.org, email@example.com
> Subject: Re: bug in install
> Resent-Date: 6 Jun 1999 17:47:51 -0000
> Resent-From: firstname.lastname@example.org
> Resent-cc: recipient list not shown: ;
> Ben Pfaff <email@example.com> writes:
> > "Phillip R. Jaenke" <firstname.lastname@example.org> writes:
> > Folks, there's a nasty ugly bug at install that's pissing me off.
> > [...]
> > Install expects the 'rescue' disk you provide with the kernel on it to be
> > *EXT2*.
> > The rescue disk is NOT ext2. It is either msdos, minix, or syslinux. Never
> > ext2.
> > No, Debian uses ext2. There is no reason not to use ext2.
> Some architectures use ext2 and some use minix. In potato, all willl
> use ext2, I think.
> Phillip, please let me know which version of the boot floppies you are
> using, and which architecture. I've never heard of this problem, but
> I assure you the current (slink) rescue disks do work (um, unless
> perhaps you have an adaptec driver).
> .....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>
> To UNSUBSCRIBE, email to email@example.com
> with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org