From: acyr@alumni.uwaterloo.ca
To: linux-kernel@vger.kernel.org
Subject: ACPI + Floppy detection problem in 2.6.8.1-mm4
Date: Wed, 25 Aug 2004 10:40:28 +0900 [thread overview]
Message-ID: <20040825014028.GA14286@alumni.uwaterloo.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
Since patching from 2.6.8.1 to -mm4 I noticed that I can no longer
modprobe the floppy driver. It is failing to detect the floppy drive
and controller it seems. Looking at the output from dmesg I have
this:
[-snip-]
inserting floppy driver for 2.6.8.1-mm4
acpi_floppy_resource: 6 ioports at 0x3f0
acpi_floppy_resource: 1 ioports at 0x3f7
floppy: controller ACPI FDC0 at I/O 0x3f0-0x3f5, 0x3f7-0x3f7 irq 6 dma channel 2
Floppy drive(s): fd0 is 1.44M
floppy0: no floppy controllers found
[-snip-]
I saw in the -mm4 changelog that ACPI-based floppy detection was
added, which seems to be working, but the floppy driver doesn't seem
to think the controller/drive exists once the ACPI enumeration is
done. I just noticed the no_acpi floppy module param in the source,
so I will give that a try. Since the ACPI code seems to be picking up
the controller and drive just fine, I doubt this is limited to just my
system (i.e. my ACPI tables are screwy etc.).
--
Aric Cyr <acyr at alumni dot uwaterloo dot ca> (http://acyr.net)
gpg fingerprint: 943A 1549 47AC D766 B7F8 D551 6703 7142 C282 D542
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-08-25 1:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 1:40 acyr [this message]
2004-08-25 2:09 ` ACPI + Floppy detection problem in 2.6.8.1-mm4 Aric Cyr
[not found] <20040825002220.4867cd17.akpm@osdl.org>
2004-08-25 16:28 ` Bjorn Helgaas
2004-08-25 20:24 ` Bjorn Helgaas
2004-08-26 7:04 ` Aric Cyr
2004-08-26 16:17 ` Bjorn Helgaas
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=20040825014028.GA14286@alumni.uwaterloo.ca \
--to=acyr@alumni.uwaterloo.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox