From: Petr Vandrovec <vandrove@vc.cvut.cz>
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 17:05:46 +0100 [thread overview]
Message-ID: <20031212160546.GA6363@vana.vc.cvut.cz> (raw)
In-Reply-To: <yw1xr7zaxd7e.fsf@kth.se>
On Fri, Dec 12, 2003 at 04:33:57PM +0100, 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:
> >
> >> "Richard B. Johnson" <root@chaos.analogic.com> writes:
> >>
> >> > 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.
>
> IMHO a ridiculous design, as is most of the PC.
>
> >> > 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.
>
> I'm running 2.6.0-test11 on a machine with modular floppy driver,
> without any spinning motors. I think it boots from floppy before HD,
> but I'm not certain (can't check right now).
Maybe because you run patched LILO which works around this 2.6.x
brokeness. Debian's #221967 says that 'reset disk subsystem' should
stop floppy motor. I'd like to see this black on white...
Fortunately Andreas Roland accepted patch instead of reassigning
bug to 2.6.x kernel package where it belongs - if kernel does
not pass timer IRQ to the BIOS, it is kernel's responsibility
to do tasks which BIOS scheduled for future...
lilo (1:22.5.8-6) unstable; urgency=low
* Now LILO can disable FDC on (weird?) BIOS using 2.6 kernel.
(closes: #221967)
Petr Vandrovec
next prev parent reply other threads:[~2003-12-12 16:06 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
2003-12-12 15:33 ` Måns Rullgård
2003-12-12 16:05 ` Petr Vandrovec [this message]
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=20031212160546.GA6363@vana.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--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®