public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Ken Witherow <ken@krwtech.com>
Cc: Frans Pop <elendil@planet.nl>, linux-kernel@vger.kernel.org
Subject: Re: PC speaker beeps in 2.6.30?
Date: Mon, 15 Jun 2009 22:22:53 +0400	[thread overview]
Message-ID: <4A36917D.5090305@msgid.tls.msk.ru> (raw)
In-Reply-To: <Pine.LNX.4.64.0906151336010.28623@death.krwtech.com>

Ken Witherow wrote:
> On Mon, 15 Jun 2009, Frans Pop wrote:
> 
>> For me the system beep has been replaced by a beep in ALSA with .30.
>>
>> Do you have soundcard that uses HDA? Is CONFIG_SND_HDA_INPUT_BEEP set?
>> Does alsamixer show a "beep" control? Is that not muted and does it have
>> volume set?
> 
> I had this exact same problem. I ran make oldconfig and was never 
> prompted for the new HDA config options. I could be wrong, but I can't 
> remember make oldconfig behaving this way in the past (or maybe it 
> resulted in changes that didn't have any noticeable effect). Having to 
> reconfigure the kernel over not being prompted for a new config option 
> which changed established behavior was annoying to say the least.

As I noted in my other email, this option (CONFIG_SND_HDA_INPUT_BEEP)
is not new, it is present in 2.6.29 too.  So it's a behavor change which
is not "backed up" by a config option -- there's no option to prompt
for.

/mjt

  reply	other threads:[~2009-06-15 18:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-15 14:41 PC speaker beeps in 2.6.30? Michael Tokarev
2009-06-15 16:57 ` Frans Pop
2009-06-15 17:39   ` Ken Witherow
2009-06-15 18:22     ` Michael Tokarev [this message]
2009-06-15 18:00   ` Michael Tokarev
2009-06-15 18:10     ` Michael Tokarev
2009-06-26  6:03 ` Michael Tokarev
2009-06-29 12:47   ` Frans Pop
2009-06-29 14:29     ` Michael Tokarev

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=4A36917D.5090305@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=elendil@planet.nl \
    --cc=ken@krwtech.com \
    --cc=linux-kernel@vger.kernel.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