From: Tomasz Torcz <zdzichu@irc.pl>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fw: 2.6.8.1-mm2: floppy magically disappaperd
Date: Mon, 23 Aug 2004 02:18:05 +0200 [thread overview]
Message-ID: <20040823001805.GA11315@irc.pl> (raw)
In-Reply-To: <200408201122.45779.bjorn.helgaas@hp.com>
On Fri, Aug 20, 2004 at 11:22:45AM -0600, Bjorn Helgaas wrote:
> > My flopped disappeared with this kernel becaouse of ACPI. It was
> > working earlier revisions. Modprobing floppy.ko fails:
> >
> > (in dmesg)
> > #v+
> > inserting floppy driver for 2.6.8.1-mm2
> > floppy: controller ACPI FDC0 at I/O 0x3f7-0x3f7 irq 6 dma channel 2
> > Floppy drive(s): fd0 is 1.44M
> > floppy0: Floppy io-port 0x03f7 in use
> > #v-
> I'm interested in the dmesg output whether it works or not.
>
> I suspect your ACPI is reporting two I/O regions for the floppy
> controller: 0x3f2-0x3f5, and 0x3f7. Strictly speaking, that's
> probably the correct thing. It happens that my box (an HP DL360)
> only reports 0x3f2-0x3f5. The driver uses 0x3f7, and I don't see
> how it could get along without it, so I think the HP BIOS is broken.
>
> In any case, the patch below should deal better with two I/O regions
> being reported.
Good news! With your patch floppy works:
#v+
inserting floppy driver for 2.6.8.1-mm2
acpi_floppy_resource: 4 ioports at 0x3f2
acpi_floppy_resource: 1 ioports at 0x3f7
floppy: controller ACPI FDC0 at I/O 0x3f2-0x3f5, 0x3f7-0x3f7 irq 6 dma
channel 2
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
#v-
Thank you!
--
Tomasz Torcz Only gods can safely risk perfection,
zdzichu@irc.-nie.spam-.pl it's a dangerous thing for a man. -- Alia
next prev parent reply other threads:[~2004-08-23 0:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040819121035.035be585.akpm@osdl.org>
2004-08-20 17:22 ` Fw: 2.6.8.1-mm2: floppy magically disappaperd Bjorn Helgaas
2004-08-23 0:18 ` Tomasz Torcz [this message]
2004-08-20 19:00 O.Sezer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040823001805.GA11315@irc.pl \
--to=zdzichu@irc.pl \
--cc=bjorn.helgaas@hp.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.