From: Alessandro Suardi <alessandro.suardi@oracle.com>
To: linux-kernel@vger.kernel.org
Subject: Re: modular floppy broken in 2.5.3
Date: Sun, 03 Feb 2002 21:48:14 +0100 [thread overview]
Message-ID: <3C5DA20E.6D503E66@oracle.com> (raw)
In-Reply-To: <3C5B4326.856A09E6@oracle.com>
Alessandro Suardi wrote:
>
> Trying to modprobe it yields
>
> [root@dolphin root]# modprobe floppy
> /lib/modules/2.5.3/kernel/drivers/block/floppy.o: init_module: Device or resource busy
> Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
> /lib/modules/2.5.3/kernel/drivers/block/floppy.o: insmod /lib/modules/2.5.3/kernel/drivers/block/floppy.o failed
> /lib/modules/2.5.3/kernel/drivers/block/floppy.o: insmod floppy failed
>
> and dmesg says
>
> inserting floppy driver for 2.5.3
> Floppy drive(s): fd0 is 1.44M
> floppy0: Floppy io-port 0x03f0 in use
>
A simple but nice hint by Pierre Rousselet suggested the I/O port
is in use - I plain assumed it broke because I have been loading
modular floppy for the last 36 months or so without specifying
any parameters...
It turns out this is due to the new PnPBIOS kernel config option:
[asuardi@dolphin asuardi]$ grep PnPBIOS /proc/ioports
03f0-03f1 : PnPBIOS PNP0c01
0600-067f : PnPBIOS PNP0c01
0680-06ff : PnPBIOS PNP0c01
0800-083f : PnPBIOS PNP0c01
0840-084f : PnPBIOS PNP0c01
0880-088f : PnPBIOS PNP0c01
f400-f4fe : PnPBIOS PNP0c01
But since modular floppy was working before without setting any
ioport parameter I'm not entirely sure this is a "feature".
Thanks,
--alessandro
"this machine will, will not communicate
these thoughts and the strain I am under
be a world child, form a circle before we all go under"
(Radiohead, "Street Spirit [fade out]")
next prev parent reply other threads:[~2002-02-03 20:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-02 1:38 modular floppy broken in 2.5.3 Alessandro Suardi
2002-02-03 20:48 ` Alessandro Suardi [this message]
2002-02-03 21:22 ` Alan Cox
2002-02-04 17:29 ` Gunther Mayer
2002-02-04 23:58 ` Thomas Hood
2002-02-05 10:13 ` Alessandro Suardi
-- strict thread matches above, loose matches on Subject: below --
2002-02-04 19:26 Thomas Hood
2002-02-07 1:30 Thomas Hood
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=3C5DA20E.6D503E66@oracle.com \
--to=alessandro.suardi@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox