Hi there.
I just figured that my thread subscription got lost. I had the impression nobody was using the script any longer. ;)
aplay works on .wav only.
Printable View
Oh ok thanks, but my sound still do not work!
I am sure it is. As I mentioned, I have a fresh installation on Intrepid and when I played a song I HAD SOUND for about 2 minutes and froze - never
recovered sound since. I know it generally works, but something IS wrong!!
Quote:
root@AbleBlue:/home/moon# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: SB [HDA ATI SB], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: SB [HDA ATI SB], device 1: ALC268 Digital [ALC268 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: SB [HDA ATI SB], device 6: Si3054 Modem [Si3054 Modem]
Subdevices: 1/1
Subdevice #0: subdevice #0
root@AbleBlue:/home/moon#
http://img50.imageshack.us/img50/136/83041271.jpg
As you can see. Alsamixer is still "1.0.17". The upgrade did not run through (properly). The logfile will tell us more about it.
Then you got "pulseaudio" as mixer-device defined. You need to get rid
of it. You need to set your default device to Alsa under
System/Preferences/Sound.
Hint: You can start alsamixer on a dedicated device if you type
alsamixer -c0
for your card 0. It would be -c1 for your 2nd card.
It shows Alsamixer 1.0.19, so how do I get hold of log file? And should I remove all pulseaudio packages?
OK. "Now" it shows 1.0.19. There was a different screen-shot before showing 1.0.17 and pulse . ;)
No you don't have to remove pulseaudio. This is gonna be a difficult task anyhow. Its integration into Intrepid is a mess. The guys didn't seem to follow any rules when doing it.
There are open trouble-tickets about this. It seems that they have done something about it in Jaunty.
If you disable pulseaudio under preferences it should be OK.
The upgrade-logfile is stored under /var/log you'll see a file starting with "Alsa...$date-timestamp".
All right, I have removed pulseaudio completely. Going for a reboot, let's pray for the best :)
Sorry about that, yes it was a wrong screen shot I uploaded before, and since edited.
I found the log file,, but cant attach it since the size it way too huge. But I guess the installation has come out fine.