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: Wed, 28 Jul 2010 23:27:46 +0200 [thread overview]
Message-ID: <20100728212745.GA15394@darkside.kls.lan> (raw)
In-Reply-To: <s5htynjtwz2.wl%tiwai@suse.de>
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
On Wed, Jul 28, 2010 at 06:03:29PM +0200, Takashi Iwai wrote:
> I wrote:
> > Mario 'BitKoenig' Holbe wrote:
> > > My PC-Speaker Beep control worked in 2.6.34, but is gone in 2.6.35-rc6.
> > It's because now the driver checks the SSID your board sets up.
> > So, it's actually BIOS that clears it.
But the BIOS itself beeps through the sound-card at boot :/
> Or, does the following patch fix? It's already in sound git tree,
Nope, unfortunately it doesn't. Still no Beep controls, no beep through
sound-card.
May I somehow provide any further data?
Or am I somehow able to tweak it? Is there a module parameter to set
this SSID bit? I mean, it did work before... :)
Thanks for you help & regards
Mario
--
Why did the tachyon cross the road?
Because it was on the other side.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 482 bytes --]
next prev parent reply other threads:[~2010-07-28 21:27 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 [this message]
2010-07-29 5:44 ` Takashi Iwai
2010-07-29 8:09 ` Mario 'BitKoenig' Holbe
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=20100728212745.GA15394@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