From: Takashi Iwai <tiwai@suse.de>
To: Shérab <Sebastien.Hinderer@ens-lyon.org>
Cc: Matthew Ranostay <mranostay@embeddedalley.com>,
PeiSen Hou <pshou@realtek.com.tw>,
matt.jared@intel.com, andy.kopp@intel.com, dan.d.kogan@intel.com,
Jaroslav Kysela <perex@perex.cz>,
Wu Fengguang <fengguang.wu@intel.com>,
Daniel T Chen <crimsun@ubuntu.com>,
Lydia Wang <lydiawang@viatech.com.cn>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: PC Beeps not working with HDA Intel module
Date: Mon, 05 Jul 2010 08:11:40 +0200 [thread overview]
Message-ID: <s5hy6dqbgpv.wl%tiwai@suse.de> (raw)
In-Reply-To: <20100626112504.GA3365@pema>
At Sat, 26 Jun 2010 13:25:04 +0200,
Shérab wrote:
>
> Dear all,
>
> The problem is on a computer with an HDA Intel sound card, Intel G45
> DEVCTG chip and appears will all version s of the kernel.
>
> Running e.g.
> beep 440
> produces a beep whose audible frequency is very low, definitely not 440
> Hz.
>
> However, it is worth notiing that grub is able to produce a beep of the
> right frequency at boot time.
>
> Can this problem be fixed ?
There are a few ways.
If you build your kernel with SND_HDA_INPUT_BEEP_MODE=2, or set the
option of snd-hda-intel module beep_mode=2, you'll be able to switch
to the native beep from HD-audio codec digital beep via muting "Beep"
mixer switch.
Or, if the value above is 0, it'll be always the system-native beep.
This can be done also via writing sysfs codec hint, as documented in
HD-Audio.txt.
Alternatively, you can reload pcspkr module so that it grabs the beep
output again over snd-hda-intel, "modprobe -r pcspkr; modprobe pcspkr"
Takashi
next prev parent reply other threads:[~2010-07-05 6:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-26 11:25 Shérab
2010-07-05 6:11 ` Takashi Iwai [this message]
2010-07-05 11:20 Daniel J Blueman
2010-08-02 18:14 ` Shérab
2010-08-02 21:41 ` Daniel J Blueman
2010-08-02 21:44 ` Takashi Iwai
2010-08-03 8:17 ` Shérab
2010-08-03 9:02 ` Daniel J Blueman
2010-08-03 10:09 ` Daniel J Blueman
2010-08-03 10:59 ` Takashi Iwai
2010-08-03 11:42 ` Shérab
2010-08-03 11:40 ` Shérab
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=s5hy6dqbgpv.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Sebastien.Hinderer@ens-lyon.org \
--cc=alsa-devel@alsa-project.org \
--cc=andy.kopp@intel.com \
--cc=crimsun@ubuntu.com \
--cc=dan.d.kogan@intel.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lydiawang@viatech.com.cn \
--cc=matt.jared@intel.com \
--cc=mranostay@embeddedalley.com \
--cc=perex@perex.cz \
--cc=pshou@realtek.com.tw \
/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
all inboxes | Powered by JetHome®