Bug#381658: [Pkg-alsa-devel] Bug#381658: After installing alsa-utils, sound no longer works

[Vincent Lefevre]

On 2006-08-06 17:42:30 +0200, Elimar Riesebieter wrote:
> Which plattform?

PowerBook G4 (PowerBook3,2).

> Which drivers?

I don't know what you mean exactly by that, but I usually use oss or
esd. I've never managed to use the ALSA device; that's why I've tried
alsaconf, but this doesn't solve the problem, I always get:

ALSA lib confmisc.c:670:(snd_func_card_driver) cannot find card '0'
ALSA lib conf.c:3479:(_snd_config_evaluate) function snd_func_card_driver returned error: No such device
ALSA lib confmisc.c:391:(snd_func_concat) error evaluating strings
ALSA lib conf.c:3479:(_snd_config_evaluate) function snd_func_concat returned error: No such device
ALSA lib confmisc.c:1070:(snd_func_refer) error evaluating name
ALSA lib conf.c:3479:(_snd_config_evaluate) function snd_func_refer returned error: No such device
ALSA lib conf.c:3947:(snd_config_expand) Evaluate error: No such device
ALSA lib pcm.c:2146:(snd_pcm_open_noupdate) Unknown PCM default
ALSA snd_pcm_open error: No such device
Error: Cannot open device alsa09.

when using ogg123 or mpg123.

> Is libao2 installed?

Yes, it is required by the vorbis-tools package.

> What tells lsmod | grep snd?

I've reinstalled alsa-utils and rerun alsaconf, and sound (with oss
and esd) is working again! "lsmod | grep snd" currently says:

snd_pcm_oss            49440  1 
snd_mixer_oss          21280  1 snd_pcm_oss
snd_powermac           50364  1 
snd_pcm                99684  2 snd_pcm_oss,snd_powermac
snd_timer              26404  1 snd_pcm
snd                    66452  5 snd_pcm_oss,snd_mixer_oss,snd_powermac,snd_pcm,snd_timer
soundcore              11140  2 snd
snd_page_alloc         11080  1 snd_pcm

The OSS mixer (gnome-volume-control) is working too. I can't change
the volume with the special keys via pbbuttons (though I could with
my customized 2.6.12 kernel), but I assume that this is a bug in
pbbuttons or in the 2.6.17 kernel package.

Hmm... If I rerun alsaconf without configuring anything, the same
problem occurs again. And:

ay:~> lsmod | grep snd
snd_pcm_oss            49440  0 
snd_pcm                99684  1 snd_pcm_oss
snd_timer              26404  1 snd_pcm
snd_page_alloc         11080  1 snd_pcm
snd_mixer_oss          21280  1 snd_pcm_oss
snd                    66452  4 snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss
soundcore              11140  1 snd

If I choose PowerMac again, I get:

ay:~> lsmod | grep snd
snd_powermac           50364  0 
snd_pcm                99684  1 snd_powermac
snd_timer              26404  1 snd_pcm
snd                    66452  3 snd_powermac,snd_pcm,snd_timer
soundcore              11140  1 snd
snd_page_alloc         11080  1 snd_pcm

and OSS is working. So, the problem seems to be that alsaconf destroys
the current config even though one chooses not to change the config.

> Customized kernel?

No, the linux-image-2.6.17-1-powerpc package (current version: 2.6.17-5).

-- 
Vincent Lefèvre <vincent at vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / SPACES project at LORIA