From owner-freebsd-stable Tue Apr 7 23:16:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25545 for freebsd-stable-outgoing; Tue, 7 Apr 1998 23:16:04 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA25520 for ; Tue, 7 Apr 1998 23:15:54 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yMo8j-0005lP-00; Tue, 7 Apr 1998 23:15:17 -0700 Date: Tue, 7 Apr 1998 23:15:13 -0700 (PDT) From: Tom To: Mike Smith cc: "Jeays, Mike" , freebsd-stable Subject: Re: ATAPI devices - more problems In-Reply-To: <199804080335.UAA00284@antipodes.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Tue, 7 Apr 1998, Mike Smith wrote: > > > > I can only get an ATAPI device (CD-ROM or Zip drive) to work if it is the > > only device on an IDE controller. If I put two ATAPI devices on the same > > controller, "mount" hangs, and causes the entire system to crash if I try a > > second time. > > This appears to be a feature of some CDROM-Zip combinations. I've > both personally and in reports seen Zip and CDROM drives running > happily side-by-side. It would be fair to say that this highlights > defects in our current ATAPI support. Could it not be IDE chipset issue? Perhaps type of motherboard is relevant? It wouldn't be the first time broken IDE chips have been put on motherboards (ex. CMD640). Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message