From owner-freebsd-questions Tue May 9 08:10:56 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA16806 for questions-outgoing; Tue, 9 May 1995 08:10:56 -0700 Received: from nak.berkeley.edu (nak.Berkeley.EDU [128.32.136.21]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA16800 for ; Tue, 9 May 1995 08:10:54 -0700 Received: from olac.Berkeley.EDU by nak.berkeley.edu (8.6.10/1.40) id IAA13898; Tue, 9 May 1995 08:10:53 -0700 Received: by olac.Berkeley.EDU (5.0/SMI-SVR4) id AA03244; Tue, 9 May 1995 08:08:43 +0800 Date: Tue, 9 May 1995 08:08:42 -0700 (PDT) From: "Erik A. Pearson" X-Sender: epearson@olac To: Terry Lambert Cc: questions@FreeBSD.org Subject: Re: FreeBSD 2.0 & mitsumi lu002 Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII content-length: 1626 Sender: questions-owner@FreeBSD.org Precedence: bulk Terry, Thanks for answering my question so quickly! > > I've got another question. I'm attempting to install freebsd on an ide > > drive from the walnut creek cdrom in a mitsumi lu002 cdrom drive. The > > floppies install fine, but the cdrom does not work well enough to allow > > installation. The drive will mount, and I can ls & cat around the drive, > > but the installation gets hung up on 'time out' errors. This is probably > > due to the fact that the only the mcd0 device is hardwired for 300/10 -- > > but the only irq settings allowed on the lu002 8-bit board are 2,3 and > > 5!! Is there some way around this -- e.g. a device that can copied into > > /dev? > > Boot the kernel with the -c option and change the interrupt on the > built in driver. > > I'd suggest changing the one that probes it successfully (look at your > current boot messages) so that it will be found for sure. However, last night I was poking around the BSD Web Page for information on this problem, and ran into your suggestion, as put forth in the usenet archives by Sean Kelly (12/28/94). However, after trying this there was no discernable improvement -- I tried all available irqs on the card with the matching irq on the card -- the io address is fine too since the probe reveals the "version information is 0 M 2" etc. message. Some of the responses to the usenet threads indicated that this solution may not work. Have you found that this actually works? Are there other settings on the card or driver that should be changed? Should the DMA channel on the card be set to 1, 3, or none? Thanks again, Erik Pearson.