From: Frans Pop <elendil@planet.nl>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PC speaker beeps in 2.6.30?
Date: Mon, 15 Jun 2009 18:57:35 +0200 [thread overview]
Message-ID: <200906151857.36576.elendil@planet.nl> (raw)
In-Reply-To: <4A365DA6.8000102@msgid.tls.msk.ru>
Michael Tokarev wrote:
> Anyone know what happened with PC speaker in 2.6.30?
> Basically, it does not work anymore here, with the
> config which is very similar to the one used for
> previous 2.6.29 kernel (where PC speaker worked).
> At least I don't see any relevant differences and
> the (seemengly) relevant symbols -- which are
> INPUT_PCSPKR and PCSPKR_PLATFORM -- are both set
> to 'y' for both 2.6.29 and 2.6.30.
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?
Cheers,
FJP
next prev parent reply other threads:[~2009-06-15 16:57 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 [this message]
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
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=200906151857.36576.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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.