public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shérab <Sebastien.Hinderer@ens-lyon.org>
To: Matthew Ranostay <mranostay@embeddedalley.com>,
	Takashi Iwai <tiwai@suse.de>, 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
Cc: linux-kernel@vger.kernel.org
Subject: PC Beeps not working with HDA Intel module
Date: Sat, 26 Jun 2010 13:25:04 +0200	[thread overview]
Message-ID: <20100626112504.GA3365@pema> (raw)

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 ?

Should you need any additional bit of information or testing, please ask.

Many thanks in advance for your help,
Shérab.

             reply	other threads:[~2010-06-26 11:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-26 11:25 Shérab [this message]
2010-07-05  6:11 ` PC Beeps not working with HDA Intel module Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
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=20100626112504.GA3365@pema \
    --to=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 \
    --cc=tiwai@suse.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