From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Emmanuel Fleury <fleury@cs.auc.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Floppy disk working constantly
Date: Fri, 3 Oct 2003 09:14:08 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0310030909040.12482@chaos> (raw)
In-Reply-To: <1065186072.6517.44.camel@rade7.s.cs.auc.dk>
On Fri, 3 Oct 2003, Emmanuel Fleury wrote:
> Hi,
>
> I am testing the 2.6.0-test6 and I noticed that my floppy driver is
> working constantly.
>
> More details:
>
> I have compiled the floppy driver as a module:
> CONFIG_BLK_DEV_FD=m
>
> I noticed that the floppy drive was constantly on and when a disk was in
> it was acting as it was reading (but no request to do so was sent).
>
> Then I noticed that the module was not loaded, so I did a "modprobe
> floppy" and instantly the floppy driver shot down and act normally...
>
> I guess that this problem has been already reported, but I didn't manage
> to find it in the mailing-list archive, so I am submitting it in doubt.
>
[SNIPPED...]
What are you using as a boot loader? This may be a problem with
the boot loader not turning off the floppy drive motor before
it transfers control to Linux. With no built-in floppy driver,
the motor would never turn off. With quick boot hard-disks,
the floppy motor may still be ON from the initial BIOS access.
Just for kicks, change the order of boot devices in your
BIOS so that the floppy is never accessed during boot. This
should verify the problem.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2003-10-03 13:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-03 13:01 Emmanuel Fleury
2003-10-03 13:14 ` Richard B. Johnson [this message]
2003-10-03 14:55 ` Emmanuel Fleury
2003-10-05 17:42 ` Floppy disk working constantly [PATCH] Emmanuel Fleury
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=Pine.LNX.4.53.0310030909040.12482@chaos \
--to=root@chaos.analogic.com \
--cc=fleury@cs.auc.dk \
--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
all inboxes | Powered by JetHome®