Bugzilla – Bug 116095
Audigy2 gets detected by YaST, but no sound
Last modified: 2007-08-11 15:38:22 UTC
Hi, I have an audigy 2 soundcard, which gets detected by YaST, but I cannot play any sound. modules: snd_pcm_oss 87200 0 snd_mixer_oss 38272 1 snd_pcm_oss snd_emu10k1 154820 0 snd_rawmidi 49184 1 snd_emu10k1 snd_seq_device 27152 2 snd_emu10k1,snd_rawmidi snd_ac97_codec 133700 1 snd_emu10k1 snd_pcm 137608 3 snd_pcm_oss,snd_emu10k1,snd_ac97_codec snd_timer 47240 2 snd_emu10k1,snd_pcm snd_ac97_bus 19584 1 snd_ac97_codec snd_page_alloc 29456 2 snd_emu10k1,snd_pcm snd_util_mem 22656 1 snd_emu10k1 snd_hwdep 28704 1 snd_emu10k1 snd 96768 10 snd_pcm_oss,snd_mixer_oss,snd_emu10k1,snd_rawmidi,snd_seq_device,snd_ac97_codec,snd_pcm,snd_timer,snd_util_mem,snd_hwdep soundcore 28448 1 snd f172:~ # rcalsasound restart Shutting down sound driver done Starting sound driver: emu10k1 done /usr/sbin/alsactl: load_state:1236: No soundcards found... f172:~ # f172:~ # cat /proc/asound/cards --- no soundcards --- f172:~ # You can grab missing info from f172, but tell me before rebooting, it's my desktop
Here is what I found in /var/log/messages: Sep 9 13:29:00 linux alsactl: resmgr: communication failure: Broken pipe Sep 9 13:29:02 linux alsactl: resmgr: communication failure: Broken pipe Sep 9 13:29:06 linux alsactl: resmgr: communication failure: Broken pipe Sep 9 13:30:11 linux alsactl: resmgr: communication failure: Broken pipe and after rcalsasound restart: Sep 9 13:52:25 linux resmgr[5263]: set_facl() - ACL error on /dev/snd/timer, acl_set_file: No such file or directory but the file is there.
The error messages are irrelevant. If it's detected and probed, the entry must appear in /proc/asound/cards. Any other error messages when you run "rcalsasound restart"? Also show the output of "hwinfo --sound".
hwinfo --sound doesn't show anything f172:~ # rcalsasound restart Shutting down sound driver done Starting sound driver: emu10k1 done /usr/sbin/alsactl: load_state:1236: No soundcards found... f172:~ # That's all, besides the error in /var/log/messages
Then please show the output of "lspci -nv".
I have abnsolutely no idea what is happening here: after looking in lspci, I didn't find the card; so I rebooted 9.3 (where it always worked) to see wether it is broken. No, worked with 9.3. Then I rebooted again with 10.0 - and there it was. Now it's working. What you wanted to see in lspci-nv is problably this: 00:08.0 Class 0401: 1102:0004 (rev 04) Subsystem: 1102:1002 Flags: bus master, medium devsel, latency 32, IRQ 193 I/O ports at b000 [size=64] Capabilities: [dc] Power Management version 2 00:08.1 Class 0980: 1102:7003 (rev 04) Subsystem: 1102:0060 Flags: bus master, medium devsel, latency 32 I/O ports at b400 [size=8] Capabilities: [dc] Power Management version 2 00:08.2 Class 0c00: 1102:4001 (rev 04) (prog-if 10) Subsystem: 1102:0010 Flags: bus master, medium devsel, latency 32, IRQ 185 Memory at 00000000fa014000 (32-bit, non-prefetchable) [size=2K] Memory at 00000000fa010000 (32-bit, non-prefetchable) [size=16K] Capabilities: [44] Power Management version 2 Still remains the question: where was it gone?
Hmm, it's really weird. Problems with something deep in the PCI core stuff? Sorry, I have no clue... Is it reproducible after a cold reboot?
I am getting the same problem: I hear choppy "Login" sound, but the sound players and recorders have no sound. It's Audigy 2 on Dell with Pentium D.
Try to play a WAV file via aplay % aplay -vv foo.wav It shows VU meter. If it's proceeding without stall but no sound comes out, check the mixer status. If the playback stops, it's an IRQ problem.
As I stated in comment #5, This problem disappeared after a warm reboot. since then it always worked. I have no idea why this changed.
aplay -vv foo.wav works fine as well.
Does this still appear in the recent version?
Sorry - I don't have this machine anymore. Setting needinfo to Joseph.
No reaction since more than 2 months, therefore closing as CANTFIX (aka WONTFIX). If you can provide the needed information, feel free to reopen the bug.