linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tuncer M "zayamut" Ayaz <tuncer.ayaz@gmx.de>
To: Ahmed Masud <masud@googgun.com>
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: 2.5.69 strange high tone on DELL Inspiron 8100
Date: Sat, 10 May 2003 17:46:31 +0200	[thread overview]
Message-ID: <S264402AbTEJPgJ/20030510153609Z+7028@vger.kernel.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0305101138110.24188-100000@marauder.googgun.com>

On Sat, 10 May 2003 11:39:12 -0400 (EDT)
Ahmed Masud <masud@googgun.com> wrote:

> 
> 
> On Sat, 10 May 2003, Tuncer M zayamut Ayaz wrote:
> 
> > On Sat, 10 May 2003 17:07:51 +0200
> > Tuncer M "zayamut" Ayaz <tuncer.ayaz@gmx.de> wrote:
> >
> > > On 10 May 2003 14:59:31 +0100
> > > Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > >
> > > > On Sad, 2003-05-10 at 14:57, Tuncer M zayamut Ayaz wrote:
> > > > > description of the strange sound:
> > > > >   - high tone
> > > > >   - permanent
> > > > >   - happens before loading ALSA modules
> 
> Is this high tone comming out of external speakers or is it from
> internal speaker?

definitely not external speaker.
can't say whether there is an internal speaker it could come
from. source of sound is right beneath the keyboard,
and creating load aka moving an x11 window around produces
funny patterns --> no high tone, it almost disappears,
but just low-volume sound reacting to when I move the
window around.
for a non-hardware-expert this is strange stuff.

  reply	other threads:[~2003-05-10 15:36 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-10 13:57 2.5.69 strange high tone on DELL Inspiron 8100 Tuncer M zayamut Ayaz
2003-05-10 13:59 ` Alan Cox
2003-05-10 15:07   ` Tuncer M zayamut Ayaz
2003-05-10 15:28     ` Tuncer M zayamut Ayaz
2003-05-10 15:39       ` Ahmed Masud
2003-05-10 15:46         ` Tuncer M zayamut Ayaz [this message]
2003-05-10 16:25       ` Jamie Lokier
2003-05-10 16:51         ` Tuncer M zayamut Ayaz
2003-05-10 17:35           ` Tuncer M zayamut Ayaz
2003-05-10 17:47             ` Xavier Bestel
2003-05-10 20:06               ` Tuncer M zayamut Ayaz
2003-05-10 20:23                 ` Tuncer M zayamut Ayaz
2003-05-10 21:13                   ` Tuncer M zayamut Ayaz
2003-05-11 10:50                     ` Dumitru Ciobarcianu
2003-05-11 13:11                       ` Tuncer M zayamut Ayaz
2003-05-11 11:28 ` Andrew McGregor
2003-05-11 13:03   ` Tuncer M zayamut Ayaz
2003-05-12  0:34     ` Andrew McGregor
2003-05-12  6:17       ` Tuncer M zayamut Ayaz
     [not found]       ` <200305120620.h4C6K64j061741@ns.indranet.co.nz>
2003-05-12 20:11         ` Andrew McGregor
2003-05-13  6:20           ` Tuncer M zayamut Ayaz
2003-05-11 20:48   ` Valdis.Kletnieks
2003-05-12  0:41     ` Andrew McGregor
2003-05-13 12:43   ` Troels Walsted Hansen
2003-05-13 12:50     ` Tuncer M zayamut Ayaz
     [not found] <20030510154639.02DDC32C9@marauder.googgun.com>
2003-05-10 15:52 ` Ahmed Masud
2003-05-10 16:04   ` Tuncer M zayamut Ayaz
2003-05-10 18:33     ` Jos Hulzink
2003-05-10 16:46       ` Tuncer M zayamut Ayaz
2003-05-10 19:46 Chuck Ebbert
2003-05-10 20:06 ` Tuncer M zayamut Ayaz
2003-05-11  2:28 Chuck Ebbert
2003-05-11 19:27 ` Tuncer M zayamut Ayaz

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=S264402AbTEJPgJ/20030510153609Z+7028@vger.kernel.org \
    --to=tuncer.ayaz@gmx.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masud@googgun.com \
    /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;
as well as URLs for NNTP newsgroup(s).