From: Frederik Himpe <fhimpe@telenet.be>
To: alsa-devel@alsa-project.org
Subject: Missing pcmC0D0p on Intel HDA with Alsa 20090327 snapshot
Date: Fri, 3 Apr 2009 07:20:40 +0000 (UTC) [thread overview]
Message-ID: <gr4dc8$aph$1@ger.gmane.org> (raw)
Hi, I'm using Mandriva kernel 2.6.29-tmb-desktop-2mdv, which according to
the changelog contains Alsa 1.0.19+ snapshot 20090327 and Alsa 1.0.19+
unstable addons snapshot 20090327.
With this kernel, I have no sound working on my Intel HDA device on a
Dell Latitude E6400 system, while sound is working fine with standard
2.6.29 kernel.
aplay gives this output:
ALSA lib pcm_dmix.c:1008:(snd_pcm_dmix_open) unable to open slave
aplay: main:590: audio open error: No such file or directory
According to strace, this is because of a missing /dev/snd/pcmC0D0p.
# ls /dev/snd
controlC0 hwC0D0 hwC0D2 seq timer
Some dmesg related output:
HDA Intel 0000:00:1b.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
HDA Intel 0000:00:1b.0: setting latency timer to 64
input: HDA Digital PCBeep as /class/input/input9
hda_codec: formats == 0 (nid=0x10, val=0xe07e0, ovrd=0, streams=0xe07e0)
hda_codec: cannot attach PCM stream 0 for codec #0
hda_codec: formats == 0 (nid=0x2, val=0x1e07f0, ovrd=1, streams=0x1e07f0)
hda_codec: cannot attach PCM stream 3 for codec #2
input: HDA Intel Mic at Sep Left Jack as /class/input/input10
input: HDA Intel Mic at Ext Right Jack as /class/input/input11
input: HDA Intel Line Out at Sep Left Jack as /class/input/input12
input: HDA Intel HP Out at Ext Right Jack as /class/input/input13
lspci:
00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD
Audio Controller [8086:293e] (rev 03)
# lsmod | grep snd
snd_hda_codec_intelhdmi 13856 1
snd_hda_codec_idt 69004 1
snd_hda_intel 29128 0
snd_hda_codec 68864 3
snd_hda_codec_intelhdmi,snd_hda_codec_idt,snd_hda_intel
snd_hwdep 8488 1 snd_hda_codec
snd_seq_dummy 3140 0
snd_seq_oss 31456 0
snd_seq_midi_event 7296 1 snd_seq_oss
snd_seq 56704 5
snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 7156 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss 43392 0
snd_pcm 80520 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_timer 22832 2 snd_seq,snd_pcm
snd_mixer_oss 16512 1 snd_pcm_oss
snd 65192 12
snd_hda_codec_intelhdmi,snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss
soundcore 7648 1 snd
snd_page_alloc 9680 2 snd_hda_intel,snd_pcm
--
Frederik Himpe
reply other threads:[~2009-04-03 7:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='gr4dc8$aph$1@ger.gmane.org' \
--to=fhimpe@telenet.be \
--cc=alsa-devel@alsa-project.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