2 machines with creative sound cards was not recognized by alsa in setup
1 card awe64.

This is my workaround which worked for me, it is work but works .
I deleted the files in the root on hard drive <live cd boot> the 202ce
was used as the puppy candidate. This also has alsa 1.0.8 which doesnt work,
so I downloaded alsa 1.0.1 & installed pup file overwriting originals.
http://dotpups.de/dotpups/Libraries/alsacore-1.0.10-0124.pup

The newer 800 machine with awe64 card is a live cd boot.
Next I was able to upgrade to 2.13 puppy, but if you try to use alsa 1.0.8
in new version there goes sound reinstalling old alsa will bring it back though.

You may be asking why didnt I just use alsa 1.0.1 on new version 2.13, well I did but wouldnt work & I did reboot machine.

Only into puppy linux for 4 months or so I do not know how how to fix via the alsa web site, there may be a fix other than this one above.So this is
my work around & hope it will help others.

2 machines with creative sound cards was not recognized by alsa in setup 1 card awe64.

You sound experienced (no pun intended) so I hesitate to ask, but for the sake of completeness: Did you use alsaconf from from the rxvt terminal to find a legacy driver for your cards, and were you using the zdrv or fulldrivers versions of 2.12 and 2.13 respectively?

My workaround was to copy /lib/modules folder from Puppy 2.02 (opera, John Murga work, ¡sound distro!) in the /lib/ directory.
This put to work the Alsa sound wizard O.K., in the 2.13, 2.14 and Pizzapup final.
Xan.

John Murga's MeanPuppy-2.02 http://www.murga-linux.com/puppy/viewtopic.php?t=10427
was based on Puppy 2.02, which had a 2.6.16.7 kernel.
But xandas' package when uncompressed indicates the modules are from a 2.6.18.1 kernel, which is what Puppy 2.12/2.13/2.14 has.
I compared several kernel modules in this package to those in 2.14, and they are size-identical.

What I'm saying is that this module package appears to be no different to the modules already in Puppy 2.14 ... except that Puppy's ALSA modules are stored separately in the compressed "zdrv" file, and maybe this is the real cause of the problem. alsaconf may have a problem extracting the modules it needs from the zdrv file. If this is true, the solution would be to "pre-uncompress" the ALSA modules from the zdrv and copy them into the appropriate locations in /lib/modules/...
WhoDo explained how to do this here http://www.murga-linux.com/puppy/viewtopic.php?p=91735#91735

Anyway, mixing modules from different kernel versions is likely to result in WORSE results, not better.
In fact, in many instances, an ALSA module from a different kernel will fail to load altogether.

If ALSA is being troublesome, rather than messing with the modules I believe a sensible approach is to match the ALSA libraries and utilities to the version of ALSA modules currently in Puppy 2.14 - http://www.murga-linux.com/puppy/viewtopic.php?t=16495

Also, alsaconf is not the holy grail. It's perfectly feasible to configure ALSA manually.
For Creative AWE64, since this card is ISA, first find out its hardware settings - irq, dma1, dma2
Now to /etc/modprobe.conf add this -

Also, alsaconf is not the holy grail. It's perfectly feasible to configure ALSA manually.
For Creative AWE64, since this card is ISA, first find out its hardware settings - irq, dma1, dma2
Now to /etc/modprobe.conf add this -

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum