mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: "Måns Rullgård" <mru@kth.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: floppy motor spins when floppy module not installed
Date: Fri, 12 Dec 2003 10:20:25 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.53.0312121018450.10945@chaos> (raw)
In-Reply-To: <yw1xy8tixe96.fsf@kth.se>

On Fri, 12 Dec 2003, [iso-8859-1] Måns Rullgård wrote:

> "Richard B. Johnson" <root@chaos.analogic.com> writes:
>
> > On Fri, 12 Dec 2003, [iso-8859-1] Måns Rullgård wrote:
> >
> >> Dale Mellor <dale@dmellor.dabsol.co.uk> writes:
> >>
> >> > 1. Floppy motor spins when floppy module not installed.
> >>
> >> It's a known problem.  Some broken BIOSes don't turn off the motor
> >> after probing for a disk.  One solution is to change the boot priority
> >> in the BIOS settings so the hard disk is tried before floppy.  If you
> >> ever need to boot from a floppy, you can change it back.
> >
> > It is not a broken BIOS! The BIOS timer that ticks 18.206 times
> > per second has an ISR that, in addition to keeping time, turns
> > OFF the FDC motor after two seconds of inactivity. This ISR is taken
> > away by Linux. Therefore Linux must turn off that motor! It is a
> > Linux bug, not a BIOS bug. Linux took control away from the BIOS
> > during boot.
>
> OK, but why doesn't it affect all machines?
>
If you leave the FDC software in the kernel, the FDC software
sets up everything and turns off the motor. If you have the
FDC as a module, you have nothing in there to turn off the
motor until you install the module.

Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (797.90 BogoMips).
            Note 96.31% of all statistics are fiction.



  reply	other threads:[~2003-12-12 15:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-12 13:57 Dale Mellor
2003-12-12 14:18 ` Måns Rullgård
2003-12-12 15:04   ` Richard B. Johnson
2003-12-12 15:11     ` Måns Rullgård
2003-12-12 15:20       ` Richard B. Johnson [this message]
2003-12-12 15:33         ` Måns Rullgård
2003-12-12 16:05           ` Petr Vandrovec
2003-12-12 16:27             ` Måns Rullgård
2003-12-12 16:41               ` Petr Vandrovec
2003-12-12 16:00       ` Matthew Kirkwood
2003-12-12 19:28     ` John Bradford
2003-12-12 19:47       ` Richard B. Johnson
2003-12-13  6:18         ` Joshua Schmidlkofer
2003-12-15 14:37           ` Richard B. Johnson
2003-12-13 10:40         ` John Bradford
2003-12-15 14:50           ` Richard B. Johnson
2003-12-15 20:24             ` John Bradford
2003-12-13 13:18   ` Helge Hafting
2003-12-13 16:42     ` Joshua Schmidlkofer
2003-12-12 14:59 ` Richard B. Johnson

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.0312121018450.10945@chaos \
    --to=root@chaos.analogic.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mru@kth.se \
    /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®