Puppy Linux Discussion Forum

[tempestuous]

I see quite a few problems with ALSA setup on the forum, and I'm now wondering if some might be caused by the mismatch of ALSA modules, libraries, and utilities currently in Puppy.

What commonly happens is that with each kernel upgrade the ALSA modules are also upgraded, but there can then be compatibility problems with the older ALSA libraries.
alsamixer, for example, can start to display the sound card's features incorrectly. Or in one case I (when I compiled a new kernel in Vector Linux) alsamixer failed to launch with many error messages.
It appears to be good practice to match the version of ALSA libraries, utilities, and kernel modules.

So what's the current situation in Puppy?
Puppy 2.14 has ALSA modules from ALSA 1.0.12rc1, which it inherits from its 2.6.18.1 kernel. This can be seen in /<kernelsource>/include/sound/version.h

I don't know what source was used for the ALSA libraries and utilities, but I suspect that it was from the T2 source repository that Barry used to compile the main libraries when Puppy moved from version 2.02 to 2.10.
alsaconf is v1.0.8
alsamixer is v1.0.11

I suggest that it would be worthwhile upgrading the ALSA libraries and utilities to 1.0.12rc1, to match the ALSA modules.

[tempestuous]

Well, it seems my suggestion did not resonate with anyone having audio problems.
I have gone ahead and compiled the compatible ALSA libraries and utilites, and I suggest anyone having ALSA setup problems might do well to try them.
UPDATE: these ALSA libraries are compatible ONLY WITH Puppy 2.12-2.16.

EDIT March 28 2007: alsa-lib package fixed and re-attached.

EDIT April 15 2007: alsa-utils package fixed to remove "standard" alsaconf.
If you already installed this package earlier, re-install the Puppy-compatible alsaconf, available as attachment to later post.

[WhoDo]

[tempestuous]

Oh, I was assuming that these packages might be tried in Puppy 2.14, rather than being added to a new Puppy version.
OK, it seems that Puppy 2.15 now includes these libraries.

[tempestuous]

A symlink was wrong in the alsa-lib package above. I just fixed it.
This problem was small, but serious.
The original package was downloaded 8 times, why did no one report the problem?

[Lobster]

Have put a link here
http://puppylinux.org/wikka/sound

[tempestuous]

WhoDo,
Apologies! My alsa-utils package installed the "standard" alsaconf, which overwrote the customised version Barry provided to accommodate the way that Puppy's drivers load from the zdrv file.
Thus, alsaconf from my package will fail to work, and setup of the ALSA drivers will fail in many cases.

I have just fixed the alsa-utils package (April 15 2007) and re-attached it.
I now also attach the original alsaconf, which is Puppy-compatible, and should fix the problem in recent releases of 2.15, and for anyone else who installed my alsa-utils package before April 15.

[cegil]

I did the three ALSA downloads, but I don't know what to do or which/what to run? I ran the ALSA sound wizard, but it looks like
it is running what was already included in the distribution, huh?

[Sit Heel Speak]

[cegil]

I just did the above steps, but when I start ALSA setup, it still
shows as ALSA WIZARD ver 1.0.8 ... looks like I have to do
something else to force it to ver 1.0.12, huh?

[Sit Heel Speak]

What I give above is a "one-size-fits-all" fix. I designed it to correct every problem I could think of and (***EDITED: well, actually that's giving myself too much credit; I should say, "I'm suggesting you install tempestuous's packages in this order and stop at the original alsaconf, because I believe this will solve the problem and just..."***) work no matter which of the various reported ways people have tangled their shoelaces. It addresses actually several reported losses of alsaconf or sound capability, some of which happened after a version upgrade, and others of which seem to spring from a conflict somehow with xvesa which I'm still tracking down.

If you want to see "version 1.0.12rc1" when you start alsaconf, so everything seems consistent, you can carry it one step further: do the above procedure, and then copy /usr/sbin/alsaconf in from the liveCD of 2.15CE. It may work. But I wouldn't guarantee it, particularly if you are using a version of 2.15CE prior to the last Final, or if you are using 2.14 or earlier, or if the problem stems from the xvesa bug.

If the procedure (without copying the 2.15CE alsaconf in) makes alsaconf work OK, and you then copy the 2.15CE alsaconf over, and now it doesn't work, then I would like to know:

1. In what manner does it fail?
and
2. What version of Puppy do you have, and how installed? Clean install, or an upgrade?
and
3. Are you using xorg or xvesa?

Rgds,
SHS

[tempestuous]

The correct version of alsaconf to use is the original one which Barry modified to be Puppy-compatible.
The actual version of this utility does not really matter. It's just a script.

The updated ALSA 1.0.12rc1 packages are most important for the core ALSA library, libasound.so.2.0.0, and alsamixer. All other ALSA utilities are not so important.

[jonyo]

I haven't sorted out alsa..as in when it doesn't work on various setups, I don't know how to go about fixing it.. It either works or doesn't when I run live cd save file to HD on boot.

Mentioned it in another thread that on this desktop, had no sound with 2.12 &3 but once I booted with 2.15 Bingo had sound for the first time.
--------------------------------------------
Compaq Presario SR 2020NX Athlon 64

[tempestuous]

[jamesbond]

Hi,

I've just upgraded my box. Now it runs on nForce405 with ALC883 codec. I read in many places that:
1) the correct driver is snd-hda-intel
2) that it only works starting with 1.0.13

Unfortunately puppy 2.15CE only has 1.0.12 (thanks to tempestuous), and as a result = no sound in the new box. Running alsaconf doesn't detect it, and running modprobe snd-hda-intel loads the module but /proc/asound/cards shows nothing.

How difficult is it to upgrade to alsa 1.0.13 ?

Thanks !