From: Takashi Iwai <tiwai@suse.de>
To: "Mario 'BitKoenig' Holbe" <Mario.Holbe@TU-Ilmenau.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 17:35:10 +0200 [thread overview]
Message-ID: <s5hzkxbtya9.wl%tiwai@suse.de> (raw)
In-Reply-To: <20100728144903.GA18170@darkside.kls.lan>
At Wed, 28 Jul 2010 16:49:03 +0200,
Mario 'BitKoenig' Holbe wrote:
>
> Hello,
>
> My PC-Speaker Beep control worked in 2.6.34, but is gone in 2.6.35-rc6.
> The sound device is an Asus P5E-V HDMI (Intel G35) onboard Intel HDA w/
> Realtek ALC883 codec.
>
> The driver does still register a PCBeep input, but the Controls as well
> as the sound (:)) are gone.
>
> HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
> HDA Intel 0000:00:1b.0: irq 47 for MSI/MSI-X
> HDA Intel 0000:00:1b.0: setting latency timer to 64
> input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input5
>
> $ diff card0-codec#0-2.6.34 card0-codec#0-2.6.35-rc6
> 111,114d110
> < Control: name="Beep Playback Volume", index=0, device=0
> < ControlAmp: chs=3, dir=In, idx=5, ofs=0
> < Control: name="Beep Playback Switch", index=0, device=0
> < ControlAmp: chs=3, dir=In, idx=5, ofs=0
>
> Attached /proc/asound/card0/codec#0 from 2.6.35-rc6.
It's because now the driver checks the SSID your board sets up.
Realtek codecs suppose SSID containing some useful bits to inform
the h/w setups. The presence of PC beep is one of it.
So, it's actually BIOS that clears it.
In the earlier version, the driver didn't check this.
Actually, the real bug is that it still creates a beep device without
mixers. This should be avoided...
thanks,
Takashi
next prev parent reply other threads:[~2010-07-28 15:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 14:49 Mario 'BitKoenig' Holbe
2010-07-28 15:35 ` Takashi Iwai [this message]
2010-07-28 16:03 ` [alsa-devel] " 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
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=s5hzkxbtya9.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Mario.Holbe@TU-Ilmenau.DE \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
/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®