Hi. I have the same problem here, but I've traced it back to also causing aplay
to hang:
I have a machine running both Warty and Hoary (on different partitions) and alsa
seems to be borked on the Hoary installation. I've made a test wav file using:
sox -t nul /dev/null sine.wav synth 1.0 sine 1000.0
and then tried to play it using aplay on both systems. On Warty it works fine
(and plays, audibly):
user@poota:~ $ aplay sine.wav
Playing WAVE 'Desktop/sine.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
Trying the same on Hoary, aplay just hangs (I get no output at the command line,
and I don't get the command prompt back) and no sound is produced.
user@poota:~$ cat /proc/asound/cards
0 [SI7012 ]: ICH - SiS SI7012 SiS SI7012 with CMI9739 at 0xdc00, irq 18
The sound card is built-in on an Asrock K7S8X motherboard. Are there any
commands I can use to work out whether the problem is in alsa or in the kernel?
BTW, This bug looks similar to #6476 (although that bug has been marked as a
duplicate of #1351, which is different to this bug) and possibly also #8049
(although I'm not sure).
Hi. I have the same problem here, but I've traced it back to also causing aplay
to hang:
I have a machine running both Warty and Hoary (on different partitions) and alsa
seems to be borked on the Hoary installation. I've made a test wav file using:
sox -t nul /dev/null sine.wav synth 1.0 sine 1000.0
and then tried to play it using aplay on both systems. On Warty it works fine
(and plays, audibly):
user@poota:~ $ aplay sine.wav
Playing WAVE 'Desktop/sine.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
Trying the same on Hoary, aplay just hangs (I get no output at the command line,
and I don't get the command prompt back) and no sound is produced.
user@poota:~$ cat /proc/asound/cards
SiS SI7012 with CMI9739 at 0xdc00, irq 18
0 [SI7012 ]: ICH - SiS SI7012
The sound card is built-in on an Asrock K7S8X motherboard. Are there any
commands I can use to work out whether the problem is in alsa or in the kernel?
BTW, This bug looks similar to #6476 (although that bug has been marked as a
duplicate of #1351, which is different to this bug) and possibly also #8049
(although I'm not sure).
Jaime