lkml.org 
[lkml]   [2003]   [Dec]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: PROBLEM: floppy motor spins when floppy module not installed
On Fri, 12 Dec 2003, John Bradford wrote:

> Quote from "Richard B. Johnson" <root@chaos.analogic.com>:
> > On Fri, 12 Dec 2003, [iso-8859-1] M=E5ns Rullg=E5rd 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 priorit=
> > y
> > > 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.
> > >
> > > --
> > > M=E5ns Rullg=E5rd
> > > mru@kth.se
> >
> > 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.
>
> We discussed almost exactly the same problem at length on LKML just
> two months ago:
>
> http://marc.theaimsgroup.com/?l=linux-kernel&m=106545766213063&w=2
>
> John.

Yes, and I recall we agreed to disagree where the FDC stop must
be put, but we both agreed that it must be stopped. I still contend
that since the Linux startup code takes control away from the BIOS,
it's that codes responsibility to turn OFF things that the BIOS
might have left ON.

Funny thing. It's so trivial, anybody/everybody could turn the
floppy motor off, but all the fingers point to somebody else's
code.

It's a bug in Linux, not in a boot-loader. That bug was covered up
until the FDC code got modularized. Once we were able to compile
a kernel without the FDC, the bug was exposed. So, I suggest that
we just fix the bug and be done with it. It's not a performance
problem, the write to the port occurs exactly once during the nest
999 days of up-time. It's just an attempt to make a mountain out
of a mole-hill.

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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:59    [from the cache]
©2003-2014 Jasper Spaans. Advertise on this site