public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Joshua Wise <joshua-NtISFavHD68j5TC/SZClsA@public.gmane.org>
To: Jeff Pitman <symbiont-tdrK/OAtAx2ELgA04lAiVw@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Source of buzzing determined for hp tc1100
Date: Mon, 06 Dec 2004 19:00:50 -0500	[thread overview]
Message-ID: <41B4F2B2.8080206@joshuawise.com> (raw)
In-Reply-To: <200412070728.57179.symbiont-tdrK/OAtAx2ELgA04lAiVw@public.gmane.org>

> I still think it's thermal.ko, but i've got it statically compiled in 
> here.
Well, recall that thermal.ko depends on processor.ko. rmmod'ing one 
implies rmmod'ing the other.

> I'm going to recompile as module tonight and play around with the 
> throttling. I think most people have too much ambient noise in their 
> work areas to hear it.  Otherwise, this has got to be happening all the 
> time.
The buzzing is actually fairly loud on this device - I can hear it in a 
moderately noisy bus. It's definately audible over the fan (which seems 
to be constantly running when the display is on on this thing...).

I'd get a recording of it, but of course the noise goes away when I try 
to record using the internal sound card. I assume that is for the same 
reason as the USB causing the buzz to cease. Perhaps later, I will fire 
up my big desktop and record from there.

joshua



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

      parent reply	other threads:[~2004-12-07  0:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-06 23:11 Source of buzzing determined for hp tc1100 Joshua Wise
     [not found] ` <41B4E721.1040601-NtISFavHD68j5TC/SZClsA@public.gmane.org>
2004-12-06 23:28   ` Nate Lawson
     [not found]     ` <41B4EB17.5010702-Y6VGUYTwhu0@public.gmane.org>
2004-12-06 23:54       ` Joshua Wise
     [not found]         ` <41B4F13B.6060304-NtISFavHD68j5TC/SZClsA@public.gmane.org>
2004-12-07  3:43           ` Jeff Pitman
     [not found]             ` <200412071143.13460.symbiont-tdrK/OAtAx2ELgA04lAiVw@public.gmane.org>
2004-12-07 15:42               ` Nate Lawson
2004-12-06 23:28   ` Jeff Pitman
     [not found]     ` <200412070728.57179.symbiont-tdrK/OAtAx2ELgA04lAiVw@public.gmane.org>
2004-12-07  0:00       ` Joshua Wise [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=41B4F2B2.8080206@joshuawise.com \
    --to=joshua-ntisfavhd68j5tc/szclsa@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=symbiont-tdrK/OAtAx2ELgA04lAiVw@public.gmane.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