From: Russell Coker <russell@coker.com.au>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.0-test9 and HDD LED
Date: Fri, 21 Nov 2003 19:30:30 +1100 [thread overview]
Message-ID: <200311211930.30241.russell@coker.com.au> (raw)
In-Reply-To: <20031121082027.A5090@flint.arm.linux.org.uk>
On Fri, 21 Nov 2003 19:20, Russell King <rmk+lkml@arm.linux.org.uk> wrote:
> On Fri, Nov 21, 2003 at 01:27:00PM +1100, Russell Coker wrote:
> > When running 2.4.0-test9 on my Thinkpad T20 the HDD LED usually stays on
> > all the time. It seems random, some boots the LED will operate normally,
> > but most boots the LED will go on continually.
>
> Is the HDD led separate from the floppy LED? On my thinkpad, they're
> one of the same.
You are so smart! I never even looked at the side to see whether the floppy
disk access light was on.
The floppy disk access light (that's part of the floppy drive) was on as well
as the system disk access light (I almost never use the floppy drive).
> If yes, I'd guess that you've built a kernel without floppy support
> built in.
You are correct. "modprobe floppy" restored the operation of the disk access
light to normal.
> The kernel used to turn the floppy motor off itself even
> without floppy support, but this has been removed. IIRC it is now
> the responsibility of the boot loader to do this.
Hmm. LILO bug then I guess.
--
http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/ My home page
prev parent reply other threads:[~2003-11-21 8:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-21 2:27 Russell Coker
2003-11-21 8:20 ` Russell King
2003-11-21 8:30 ` Russell Coker [this message]
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=200311211930.30241.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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®