public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: the <the.guard@mail.ru>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Continuous beeping with kernel 3.10 and 3.11
Date: Tue, 15 Oct 2013 22:23:02 +0400	[thread overview]
Message-ID: <525D8806.3030903@mail.ru> (raw)
In-Reply-To: <500ea694f3d63d674d59c1d6c24469a7@weilbacher.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/15/13 16:44, Peter Weilbacher wrote:
> On 2013-09-26 14:42, Peter Weilbacher wrote:
>> On one of my machines, I get continuous beeping from the
>> internal loudspeaker when I boot a newer kernel (I'm using
>> vanilla-sources). I first had that with 3.10.8 and also with
>> 3.10.10, and it continues with 3.11.1.
> [...]
>> In the meantime I left the machine on long enough to discover
>> that it stops beeping whenever it is idle long enough and blanks
>> the display.
> 
> Well, this is embarrassing: Since this began I switched the machine
> on even less often than before, but yesterday I found out by chance
> that the sound did not come from the internal speaker but from the
> speakers built into my screen. Now I traced it to the snd-hda-intel
> kernel module (noise there if loaded, sound gone when removed with
> |modprobe -r|).
> 
> Why was the sound never heard on bootup in 3.8.x kernels but is
> starting with 3.10.1?
> 
> Peter.
> 
> P.S.: At least now I know that the easy workaround is to tune the 
> (hardware) speaker volume down to 0...
> 
nice joke
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJSXYgFAAoJEK64IL1uI2haeSMIAJbsbjekIbOGvAtKyPKl/8s9
QEtMdQnzFZNPI4TbqgXHR8Qqms/8mA8JHUgY0RkuuLoXoGzInhQi5elkUujloLgY
QlW8uYoneLWFljmgapseNtn+HE2hZTSB4fcSzAx0jwu4fEMVV4YpkiltA/1gSp7m
hX76pMLKcTRjMz7w9rh75pebHY94HzD+x8BX02Jq1VsaD9xzfXlhFj4Aerl5E6s3
E1RGhZ39b15AbBidkJwxSXK5f/4g4EDWOL69JiVRNycc2gz/NBJGSJYFjdD107Xo
GpmNxqs02M0EJGh4xLoe1y+icFlkB65PDC9DwR2gHOyoBm5E4KkLuTkonsrdJoo=
=cMwT
-----END PGP SIGNATURE-----


      parent reply	other threads:[~2013-10-15 18:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-26 12:42 [gentoo-user] Continuous beeping with kernel 3.10 and 3.11 Peter Weilbacher
2013-09-26 13:24 ` the
2013-10-01 19:33   ` Peter Weilbacher
2013-09-26 13:35 ` Bruce Hill
2013-10-01 19:29   ` Peter Weilbacher
2013-10-02  2:09 ` Dale
2013-10-02  8:43   ` Neil Bothwick
2013-10-02 12:23     ` J. Roeleveld
2013-10-02 15:34       ` Neil Bothwick
2013-10-03 16:10         ` joost
2013-10-03 16:24           ` Tanstaafl
2013-10-03 16:29           ` Neil Bothwick
2013-10-03 20:03             ` joost
2013-10-15 12:44 ` [gentoo-user] " Peter Weilbacher
2013-10-15 12:58   ` Alan McKinnon
2013-10-15 18:23   ` the [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=525D8806.3030903@mail.ru \
    --to=the.guard@mail.ru \
    --cc=gentoo-user@lists.gentoo.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