On Sat, Sep 23, 2000 at 02:01:49PM +0200, Soren Schmidt wrote:
> 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".
OK, just to follow up on things. After a make world and a kernel upgr
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
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
On Fri, Sep 22, 2000 at 09:48:42AM -0500, Mark Hittinger wrote:
>
> I am also seeing the fdc0 problem "fdc0: cannot reserve I/O port range".
I am also seeing this with a kernel and world from today... also, are there
any issues with mount_cd9660? When I issue the following command:
# mount -t c
I am also seeing the fdc0 problem "fdc0: cannot reserve I/O port range".
The same kernel that I began to see the fdc0 problems I also lost the ability
to use devices on ata1. Ata1 seems to probe OK but I get I/O errors on the
ata1 drives all of a sudden. A kernel from a week ago is OK.
Later
