Puppy Linux Discussion Forum

pup2learn222 · Joined: 22 Aug 2006 Posts: 15

no sound in 2.12 & 2.13

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 Laughing

.
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

Now alsa 1.0.1 recognized both machines isa sound card.

Note on old machine 350,284ram was hd drive install,just backdated
alsa software & it worked.

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.

WhoDo

pup2learn222 · Joined: 22 Aug 2006 Posts: 15

yes I tried in console which is rxvt terminal.
zdr 2.12 and 2.13 fulldrivers iso & md5 ok & so was burn checked ok.

xandas · Joined: 23 Jun 2006 Posts: 37

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.

DavidMaas · Posted: Wed 07 Mar 2007, 13:47 Post_subject:

So isn't it possible to put that modules folder from pup202-opera somewhere online? so not everybody has to download extra iso and burn it to just get the sound working?
Just an idea, Greetz
Dave

xandas · Joined: 23 Jun 2006 Posts: 37

Sorry for the delay, here is the "modules" folder from John Murga Puppy 2.02 .
Replace the /lib/modules folder with the unzipped one.

This workaround allows Alsa detect legacy sound cards in Puppy versions 2.12, 2.13, 2.14 and 2.15

Xan

WhoDo

DavidMaas · Posted: Thu 22 Mar 2007, 11:35 Post_subject:

Yes, very nice, works perfect. Also nice to hear that it will be incorporated in 2.15
Greetz

tempestuous · Joined: 10 Jun 2005 Posts: 4950 Location: Australia

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 -

alias snd-card-0 snd-sbawe
alias sound-slot-0 snd-sbawe
options snd-sbawe isapnp=no irq=? dma8=? dma16=?

Now reboot.

pup2learn222 · Joined: 22 Aug 2006 Posts: 15

Thank you xandas will try later tonight will let you know, I was able to get sound by doing modprobe sb & editing a file for bootup rc.local, dont remember but will undo that to try your module thing.

DemertX · Joined: 29 Apr 2007 Posts: 27 Location: Napoli,Italia

tempestuous · Joined: 10 Jun 2005 Posts: 4950 Location: Australia

Yes. It's just a question of exactly which model of sound card you have, and what is the correct driver.
If your card is the Sound Blaster 32 AWE PnP, then the correct driver is snd-sbawe

DemertX · Joined: 29 Apr 2007 Posts: 27 Location: Napoli,Italia

tempestuous · Joined: 10 Jun 2005 Posts: 4950 Location: Australia

Check the Creative listings on the ALSA website -
http://www.alsa-project.org/alsa-doc/index.php?vendor=vendor-Creative_Labs

I don't see "Sound Blaster 32 Isa" listed, so it might be best to visually identify the name printed on the chipset on your sound card.
Examples - emu8000, ES1370

bobn9lvu · Joined: 11 Jul 2006 Posts: 173

The SB 32 and SB AWE 32 used the same EMU chips.
Here is the differences;
http://en.wikipedia.org/wiki/Sound_Blaster#Sound_Blaster_AWE32 Shocked

Bob