It seems Donn Miller wrote:
> In article <[EMAIL PROTECTED]> 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....


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to