From: Michael Tokarev <mjt@tls.msk.ru>
To: Frans Pop <elendil@planet.nl>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
alsa-devel@vger.kernel.org
Subject: Re: PC speaker beeps in 2.6.30?
Date: Mon, 29 Jun 2009 18:29:21 +0400 [thread overview]
Message-ID: <4A48CFC1.2040103@msgid.tls.msk.ru> (raw)
In-Reply-To: <200906291447.08249.elendil@planet.nl>
Frans Pop wrote:
> Michael Tokarev wrote:
>> Am I the only concerned about this? My 2.6.30 is still
>> silent w.r.t. old good PC speaker beeps, and I wasn't
>> able to make it to produce any sound. Yes, as pointed
>> out by others there is a control now, in alsa,
>
> Did you actually try compiling a kernel without CONFIG_SND_HDA_INPUT_BEEP
> set? If you do, does your PC speaker work again?
Yes it works. Even with CONFIG_SND_HDA_INPUT_BEEP set,
but without the module loaded. See all the details at
http://bugzilla.kernel.org/show_bug.cgi?id=13651
> If it does work again, I don't think there is a bug, at least not in the
> fact that the old PC speaker beep no longer works: if you have a HDA
> soundcard in the system _and_ the driver is loaded _and_
> CONFIG_SND_HDA_INPUT_BEEP is set, then it seems logical to me that that
> takes over system beeps.
> The fact that the config option also existed in 2.6.29 but did not work
> the same seems a minor issue to me.
Original issue was that I didn't know what to do.
[]
> If it really does sound bad, maybe the ALSA developers could look into
> that, but you will have to describe it better (or maybe make a
> recording?).
There was another, unrelated bug, fixed for 2.6.31-tobe.
/mjt
next prev parent reply other threads:[~2009-06-29 14:29 UTC|newest]
Thread overview: 23+ 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
2009-06-15 18:00 ` Michael Tokarev
2009-06-15 18:10 ` Michael Tokarev
2009-06-26 6:03 ` Michael Tokarev
2009-06-27 7:36 ` [alsa-devel] " Takashi Iwai
2009-06-27 10:33 ` Michael Tokarev
2009-06-28 6:39 ` Paul Vojta
2009-06-28 8:38 ` Takashi Iwai
2009-06-28 11:09 ` Kurt J. Bosch
2009-06-29 23:24 ` Paul Vojta
2009-06-30 5:57 ` Takashi Iwai
2009-06-30 11:31 ` Kurt J. Bosch
2009-06-30 12:53 ` Takashi Iwai
2009-06-30 15:35 ` Kurt J. Bosch
2009-06-30 15:40 ` Takashi Iwai
2009-06-30 16:31 ` Kurt J. Bosch
2009-06-30 19:33 ` Takashi Iwai
2009-06-29 12:47 ` Frans Pop
2009-06-29 14:29 ` Michael Tokarev [this message]
2009-06-26 6:03 ` 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=4A48CFC1.2040103@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=alsa-devel@vger.kernel.org \
--cc=elendil@planet.nl \
--cc=linux-input@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.