From: Paul Vojta <vojta@math.berkeley.edu>
To: "Kurt J. Bosch" <kjb-temp-2006@gmx.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: PC speaker beeps in 2.6.30?
Date: Mon, 29 Jun 2009 16:24:14 -0700 [thread overview]
Message-ID: <20090629232414.GA4234@math.berkeley.edu> (raw)
In-Reply-To: <h27j15$g1d$1@ger.gmane.org>
On Sun, Jun 28, 2009 at 01:09:26PM +0200, Kurt J. Bosch wrote:
> On 2009-06-28 10:38, Takashi Iwai wrote:
> > At Sat, 27 Jun 2009 23:39:08 -0700,
> > Paul Vojta wrote:
> >>
> >> On Sat, Jun 27, 2009 at 09:36:42AM +0200, Takashi Iwai wrote:
> >>> At Fri, 26 Jun 2009 10:03:54 +0400,
> >>> Michael Tokarev wrote:
> >>>>
> >>>> [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... ;)
> >>>
> >>> Try 2.6.31-rc1. There was a fix regarding beep frequency.
> >>
> >> Not necessarily. Based on the OP's original post, as well as his mails
> >> to the LKML (Google the subject line to find them), he has a desktop
> >> system with external powered speakers connected to a sound card, and also
> >> a small PC speaker inside the system case. He wants to hear the beeps
> >> coming out of the small speaker, since the external speakers (and/or sound
> >> card) are not always turned on.
> >
> > To avoid someone misunderstanding: the beep routed through HD-audio
> > can also go to the built-in speaker. It's just mixed up with the
> > normal audio output, and the volume is controlled via ALSA mixer
> > volume element.
> >
> > But, once after it's hooked up to the codec, the beep can't be output
> > separately to the speaker. It's always with other audio signal to the
> > same output target.
> >
> > Or, on some systems (mostly laptops), the beep is hooked up to the
> > codec automatically no matter whether you set
> > CONFIG_SND_HDA_INPUT_BEEP once when the codec chip is initialized.
> > So, the behavior depends pretty much on the hardware implementation.
> >
> I face the same problem as the OP since kernel 2.6.30 on ArchLinux on
> a desktop machine. I was able to get beep working through the built in
> speaker again by doing a 'modprobe -r pcspkr' followed by a
> 'modprobe pcspkr' after sysinit. It seems there is some kind of
> struggle goinig on here between alsa and pcspkr. Isn't there any
> kernel line or modules configuration option to disable the alsa pc-beep?
Hm... apparently not. Probably there should be a module option for this, though.
--Paul Vojta, vojta@math.berkeley.edu
next prev parent reply other threads:[~2009-06-29 23:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A365DA6.8000102@msgid.tls.msk.ru>
2009-06-26 6:03 ` PC speaker beeps in 2.6.30? Michael Tokarev
[not found] ` <4A4464CA.4060006@msgid.tls.msk.ru>
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 [this message]
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
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=20090629232414.GA4234@math.berkeley.edu \
--to=vojta@math.berkeley.edu \
--cc=alsa-devel@alsa-project.org \
--cc=kjb-temp-2006@gmx.de \
/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