At Mon, 21 Apr 2008 13:02:40 +0100, Andy Green wrote:
Hi folks -
I have a new 8920g on Fedora development running 2.6.25 which has
$ cat /proc/asound/version Advanced Linux Sound Architecture Driver Version 1.0.16rc2 (Thu Jan 31 16:40:16 2008 UTC).
I get a decent looking set of alsa things in /proc/asound
$ cat /proc/asound/cards 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xfc300000 irq 22
and dmesg says that model=acer was selected reasonably enough.
First of all, do you need to pass model=acer at all?
I can play audio down the logical sound devices, including cat /dev/urandom > /dev/dsp and the interrupt count goes up in /proc/interrupts.
Alsamixer shows a bunch of things and I twiddled them all to no avail. There has never been even a click from the speakers or headphone jack on this machine.
At least three funnies on this machine:
- It is confused if it has ALC889 or ALC883 in there
$ grep ALC /proc/asound/* -R /proc/asound/card0/codec#0:Codec: Realtek ALC889 <==== 889 /proc/asound/card0/pcm2c/sub0/info:id: ALC883 Analog <=== 883...
This doesn't matter. ALC889 is compatible with ALC883, and the driver uses the same string inside.
- from dmesg
ALSA sound/pci/hda/hda_intel.c:1810: chipset global capabilities = 0x4401 ALSA sound/pci/hda/hda_intel.c:749: codec_mask = 0x3 ALSA sound/pci/hda/hda_codec.c:2211: hda_codec: model 'acer' is selected ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Headphone Playback Volume, skipped ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Speaker Playback Volume, skipped ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Mono Playback Volume, skipped ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Line-Out Playback Volume, skipped ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Speaker Playback Switch, skipped ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Mono Playback Switch, skipped ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave IEC958 Playback Switch, skipped
- there is a funny embedded capacitive volume control thing on this
device, whether it gates output by itself or is just a bunch of special keyboard keys, I dunno.
Any ideas, more information needed?
alsa-info.sh (found in www.alsa-project.org debug page) would give more detailed debug information. Please show that output.
thanks,
Takashi