public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Linux-kernel <linux-kernel@vger.kernel.org>
Cc: linux-input <linux-input@vger.kernel.org>, alsa-devel@vger.kernel.org
Subject: Re: PC speaker beeps in 2.6.30?
Date: Fri, 26 Jun 2009 10:03:54 +0400	[thread overview]
Message-ID: <4A4464CA.4060006@msgid.tls.msk.ru> (raw)
In-Reply-To: <4A365DA6.8000102@msgid.tls.msk.ru>

[Adding some more Cc's...]

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, and I
can hear ugly and scary beeps from my stereo speakers
(when they're turned on and when the control is un-muted).
But that's.. not a solution/answer to the original
question... ;)

Thanks!

Michael Tokarev wrote at Mon, 15 Jun 2009 18:41:42 +0400:
> 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.
> 
> Help? :)
> 
> Thanks.
> 
> /mjt


  parent reply	other threads:[~2009-06-26  6:04 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
2009-06-15 18:00   ` Michael Tokarev
2009-06-15 18:10     ` Michael Tokarev
2009-06-26  6:03 ` Michael Tokarev [this message]
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=4A4464CA.4060006@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=alsa-devel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox