Date: Sat, 19 Jun 1999 16:26:36 -0500 (EST) From: Alfred Perlstein <bright@rush.net> To: Kent Stewart <kstewart@3-cities.com> Cc: "James A. Mutter" <jmutter@netwalk.com>, freebsd-questions@FreeBSD.ORG Subject: Re: Questions about the acd driver (IDE CD-ROM) Message-ID: <Pine.BSF.3.96.990619162415.14320U-100000@cygnus.rush.net> In-Reply-To: <376C09C0.5C874C94@3-cities.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 19 Jun 1999, Kent Stewart wrote:
>
>
> Alfred Perlstein wrote:
> >
> > On Sat, 19 Jun 1999, James A. Mutter wrote:
> >
> > >
> > > Hi all,
> > >
> > > I finally broke down and bought an IDE CDROM for my system today. I
> > > don't plan to do much of anything with it except make copies of my
> > > cd's into mp3 format. I'm having a problem with the IDE driver.
> > >
> > > I've added these lines into my kernel config file:
> > >
> > > *****
> > > options ATAPI_STATIC
> > > controller wdc1 at isa? port "IO_WD2" bio irq 15 flags
> > > 0x80ffa0ff vector
> > > wdintr
> > > disk wd2 at wdc1 drive 0
> > > disk wd3 at wdc1 drive 1
> > > device acd0
> > > device acd1
> > > device acd2
> > > device acd3
> > > *****
> > >
> > > I know I went a little overboard with the acd devices, I figure _one_
> > > of them will be correct, and I can remove the bad ones later. :)
> > >
> > > Anyhow, when I boot the system I get this:
> > >
> > > *****
> > > wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ffa0ff on isa
> > > wdc0: unit 0 (wd0): <WDC AC22500L>, DMA, 32-bit, multi-block-16
> > > wd0: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S
> > > wdc0: unit 1 (wd1): <Maxtor 90340D2>, 32-bit, multi-block-16
> > > wd1: 3242MB (6640704 sectors), 6588 cyls, 16 heads, 63 S/T, 512 B/S
> > > wdreset: error1: 0x0
> > > wdreset: error1: 0x0
> > > wdc1 not found at 0x170
>
> I just noticed this and wonder if he has enabled the 2nd IDE controller
> in the BIOS. You have to set up the IDE in two places. The first place
> is for the drives. The second setting determines whether one or both
> controllers are active. If the second controller was active, he would
> have seen something at 0x170.
I know FreeBSD will spit out all kinds of weird errors when the
drives aren't jumpered properly, it's really annoying how a bios
will not even complain when things are mis-wired and happily boot
you into a broken system.
You could be correct about it being off though, checking both would
be a good idea as well as your previous suggestion about adding
options ATAPI
options ATAPI_STATIC
to the kernel, good call.
-Alfred Perlstein - [bright@rush.net|bright@wintelcom.net]
systems administrator and programmer
Win Telecom - http://www.wintelcom.net/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.990619162415.14320U-100000>