From owner-freebsd-current  Sat Sep 23  4:57:26 2000
Delivered-To: freebsd-current@freebsd.org
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
	by hub.freebsd.org (Postfix) with ESMTP id 1293C37B424
	for <current@FreeBSD.ORG>; Sat, 23 Sep 2000 04:57:24 -0700 (PDT)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id OAA40391;
	Sat, 23 Sep 2000 14:01:49 +0200 (CEST)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <200009231201.OAA40391@freebsd.dk>
Subject: Re: fdc0 and ata1 issues
In-Reply-To: <200009231131.e8NBVGI01531@acs-24-154-25-35.zoominternet.net> from Donn Miller at "Sep 23, 2000 07:31:16 am"
To: dmmiller@zoominternet.net (Donn Miller)
Date: Sat, 23 Sep 2000 14:01:49 +0200 (CEST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

It seems Donn Miller wrote:
> In article <200009221448.JAA20935@freebsd.netcom.com> you wrote:
> 
> 
> > I am also seeing the fdc0 problem "fdc0: cannot reserve I/O port range".
> 
> What's up with the fdc driver?  I'm seeing the exact same thing.  There was
> never any heads-up about this.  Surely, the person who broke it knows about
> it. :-(  It's nice to have a warning before I go and recompile my kernel.
> But then again, I wouldn't be running -current if I didn't expect problems.

Its not the fdc driver, its the ata driver. The reason is I usr the
altport address no in a different manner, that causes the conflict.

I'm working on a solution....

-Søren


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message