public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shérab <Sebastien.Hinderer@ens-lyon.org>
To: Daniel J Blueman <daniel.blueman@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Takashi Iwai <tiwai@suse.de>
Subject: Re: PC Beeps not working with HDA Intel module
Date: Mon, 2 Aug 2010 20:14:49 +0200	[thread overview]
Message-ID: <20100802181449.GA3071@pema> (raw)
In-Reply-To: <AANLkTild_NZP5B33ITuaS67bvuREiukbQCtcguKEO4XG@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1835 bytes --]

Dear Daniel,

Many thanks for your helpful e-mail and sorry for the delay, it was hard
to find the time for testing.

Daniel J Blueman (2010/07/05 12:20 +0100):
> 
> On Jun 26, 12:40 pm, Shérab <Sebastien.Hinderer@ens-lyon.org> 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 ?
> >
> > Should you need any additional bit of information or testing, please ask.
> 
> I was finding the same with my Dell Studio 1557.

Good to know one is not alone.

> It may be worth using some printk calls [1] showing what frequency
> value is sent to the codec,

I applied your patch on top of
9fe6206f400646a2322096b56c59891d530e8d51

When a console bell is produced, one gets:
HDA beep: linear value 241

And running the command
beep 440
produces the following output:
HDA beep: linear value 248

Aso, the printk you added saying "printk(KERN_ERR "HDA beep: standard
value" never appears in the logs.
Was this result predictable ?
I thought that to each standard value one linear value would correspond,
or something like that.

> then checking with the codec datasheet -
> we'll need to know which one, eg from 'dmesg' or 'alsa-info.sh' (from
> http://www.alsa-project.org/alsa-info.sh).

I attach the bzipped alsa-info.txt, hope this will help you guys.

> We'll probably need to check the configuration registers of the beep
> widget to check what divider it's using...

That I don't know how to do, sorry. Any clue would be warmly
appreciated.

Thanks again,
Shérab.

[-- Attachment #2: alsa-info.txt.bz2 --]
[-- Type: application/octet-stream, Size: 5962 bytes --]

  reply	other threads:[~2010-08-02 18:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-05 11:20 PC Beeps not working with HDA Intel module Daniel J Blueman
2010-08-02 18:14 ` Shérab [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2010-06-26 11:25 Shérab
2010-07-05  6:11 ` 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=20100802181449.GA3071@pema \
    --to=sebastien.hinderer@ens-lyon.org \
    --cc=daniel.blueman@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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