Tiny Core Linux

Tiny Core Extensions => TCE Bugs => Topic started by: jls on January 25, 2010, 05:54:36 PM

Title: alsa doesn't work
Post by: jls on January 25, 2010, 05:54:36 PM

after the update of alsa  I don't have sound:

Code: [Select]

tc@box:~$alsamixer
ALSA lib conf.c:3009:(snd_config_update_r) Cannot access file /usr/local/share/alsa/alsa.conf
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL default

alsamixer: function snd_ctl_open failed for default: No such file or directory


Title: Re: alsa doesn't work
Post by: Jason W on January 25, 2010, 06:21:01 PM

Those with existing alsa.tcz extensions need to also download alsa-config.tcz for it to function.

Title: Re: alsa doesn't work
Post by: jur on February 08, 2010, 05:24:15 PM

My alsa is not working after updating this morning; I did have it working after the alsa-config change. I didn't have to do anything else such as change config files or anything then.

Now, this morning after updating alsa, no sound. Does anything need to be configured in alsa-config?

Title: Re: alsa doesn't work
Post by: curaga on February 08, 2010, 05:33:44 PM

Any errors? Are your sound modules still loaded?

How does alsamixer look?

Title: Re: alsa doesn't work
Post by: maro on February 08, 2010, 06:09:14 PM

I've just done a quick comparison (using QEMU 0.11.1) between TC 2.9rc1 and 2.0rc2:

(1) For RC1 'tce-load -wi alsa' fails with:

Code: [Select]

/usr/local/tce.installed/alsa: line 6: udevadm: not found
/usr/local/tce.installed/alsa: line 7: udevadm: not found
I suspect that a recent change of that startup file to deal with the new udev (in RC2) has "broken" all older versions (e.g. 2.8.1). I guess this startup script has to "become aware" of which udev version is in use. BTW, I've just also checked TC 2.8.1: It shows (as expected) the same error messages.

(2) When using RC2 the tce-load does work, but when I try to start alsa I get the following:

Code: [Select]

tc@box:~$ sudo /usr/local/etc/init.d/alsasound start
Starting sound driver: snd-intel8x0
ALSA lib control.c:874:(snd_ctl_open_conf) Cannot open shared library /usr/local/lib/alsa-lib/libasound_module_ctl_oss.so
amixer: Mixer attach default error: No such file or directory
AFAIK this shared library is part of the alsa-plugins.tcz extension. I've therefore loaded this extension and can report that 'speaker-test' seems to be working again.

[Edited: update of the analysis for RC2]

Title: Re: alsa doesn't work
Post by: jur on February 09, 2010, 02:25:19 AM

I get this when running speaker-test:

Code: [Select]

ALSA lib pcm_direct.c:1605:(snd1_pcm_direct_parse_open_conf) The field ipc_gid must be a valid group (create group audio)
Playback open error: -22,Invalid argument

Same result after loading alsa-plugins.

amixer and alsamixer appear to work as intended.

Title: Re: alsa doesn't work
Post by: jur on February 09, 2010, 03:58:21 AM

Had a look at the startup script, and ran these 2 commented-out lines manually:

Code: [Select]

sudo addgroup audio > /dev/null 2>&1
sudo addgroup "$USER" audio > /dev/null 2>&1

then my sound worked.

Title: Re: alsa doesn't work
Post by: curaga on February 09, 2010, 05:15:07 AM

OK, please see if things now work. Hopefully fixed for all now.

maro, do you have OSS loaded? I think those plugins are only needed if they are specified in the alsa config file.

Re udevadm not found, that's a harmless one, as the extension didn't call udev at all before. Failing to do those calls on pre-rc2 shouldn't cause anything, except those not found messages. I do agree they shouldn't be shown.

Title: Re: alsa doesn't work
Post by: jur on February 09, 2010, 06:09:09 AM

Quote from: curaga on February 09, 2010, 05:15:07 AM

OK, please see if things now work. Hopefully fixed for all now.

Mine works now, thanks.

Title: Re: alsa doesn't work
Post by: maro on February 09, 2010, 06:48:12 PM

I've repeated the tests from yesterday and can now confirm that the alsa.tcz extention works fine for TC 2.8.1, 2.9rc1, and 2.9rc2 (using QEMU 0.11.1). At least as far as 'speaker-test' is concerned.

I'm very sorry for reporting a misleading issue. It is possible that I had initially OSS installed in the VM and after uninstalling that extension attempted to load alsa.tcz. I guess that could be a possible explanation. But since things look to be resolved now I can only hope that not too much time was wasted in investigating my earlier findings.