From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@TU-Ilmenau.DE>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] Regression 2.6.35-rc6: ALSA Intel HDA/Realtek: missing Beep
Date: Thu, 29 Jul 2010 10:09:30 +0200 [thread overview]
Message-ID: <20100729080930.GA20619@darkside.kls.lan> (raw)
In-Reply-To: <s5hd3u6alkp.wl%tiwai@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 1784 bytes --]
On Thu, Jul 29, 2010 at 07:44:38AM +0200, Takashi Iwai wrote:
> Mario 'BitKoenig' Holbe wrote:
> > But the BIOS itself beeps through the sound-card at boot :/
> But BIOS tells that the HD-audio codec shouldn't use, so the driver
> follows it.
Even grub's beep (play 480 440 1) goes through the sound-card. So it
seems like the BIOS leaves everything set up working as well.
Please don't get me wrong. I'm not saying the driver does something
wrong, I'm sure it doesn't. I'm just sure that if I could convince it to
behave as if it would have detected the Beep pin everything would work
fine again because it did before...
> Please give alsa-info.sh output instead of codec proc file. It's more
> comprehensive.
Attached.
This is from a kernel with both patches applied you sent me.
> With the patch below, you'll likely have back the system beep sound.
Nope, no sound. But I guess this wasn't the intention of the patch. Now,
no beep input is registered anymore - which was the intention, I guess.
> But it doesn't go through codec, thus no volume control.
If you mean it should go through the 5V PC Speaker (i.e. pcspkr) - I
don't have such a thing connected. I always appreciated having volume-
and mute control over the beep at night when you can't get away from
work but don't like to wake up anybody just because command completion
beeps, because you pasted something in the wrong window, or whatever.
regards
Mario
--
Independence Day: Fortunately, the alien computer operating system works just
fine with the laptop. This proves an important point which Apple enthusiasts
have known for years. While the evil empire of Microsoft may dominate the
computers of Earth people, more advanced life forms clearly prefer Macs.
[-- Attachment #1.2: alsa-info.out.gz --]
[-- Type: application/octet-stream, Size: 3433 bytes --]
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 482 bytes --]
next prev parent reply other threads:[~2010-07-29 8:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 14:49 Regression 2.6.35-rc6: ALSA Intel HDA/Realtek: missing Beep Mario 'BitKoenig' Holbe
2010-07-28 15:35 ` [alsa-devel] " Takashi Iwai
2010-07-28 16:03 ` Takashi Iwai
2010-07-28 21:27 ` Mario 'BitKoenig' Holbe
2010-07-29 5:44 ` Takashi Iwai
2010-07-29 8:09 ` Mario 'BitKoenig' Holbe [this message]
2010-07-29 8:26 ` Takashi Iwai
2010-07-29 8:41 ` Mario 'BitKoenig' Holbe
2010-07-29 8:52 ` Takashi Iwai
2010-07-29 9:15 ` Mario 'BitKoenig' Holbe
2010-07-29 9:42 ` Takashi Iwai
2010-07-29 13:25 ` Mario 'BitKoenig' Holbe
2010-07-29 13: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=20100729080930.GA20619@darkside.kls.lan \
--to=mario.holbe@tu-ilmenau.de \
--cc=alsa-devel@alsa-project.org \
--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