Where in Puppy do I need to be to recompile Alsa and do I need to uninstall it first?
 

I've been trying to get the sound to work now for ages, I've followed so many threads and tried the advice given. So far it has either done nothing at all, or worse. My last attempt was to download three files, I think they were all .pets. It replaced my version of Alsa from 1.0.16 to 1.0.8 but still has not solved the problem of finding my ISA AWE64 gold sound card, and I am left unable to uninstall Alsa 1.0.8.

I've tried downloading the latest Alsa source code and recompiling it from scratch, but I'm still left with Alsa sound wizard 1.0.8 after I've rebooted and the new Alsa gets put into a file of its own "alsa-driver-1.0.19" and I've no idea of where to put this? It seemed to compile OK and there are a lot of folders and files inside, I thought about replacing the files manually but I'm not sure if this would work?

I'm running Puppy 4.1.2 full install on the hard drive 64MB ram ISA sound blaster AWE64 gold sound card. I don't have a live Cd, but I have the .ISO somewhere, I think I can just click on it and it mounts. Could I restore Alsa by replacing all the folders like for like that have anything to do with Alsa, or would that maybe mess something else up in the process?

Any help appreciated.

did you do
./configure
make
make install ?

Hi repo, thanks for the reply. Yep that's exactly what I did, I even went to the Alsa website and copied their instructions and gave it its own folder named alsa in usr/scr, but still no sound.

I did managed to get rid of alsa 1.0.8 though, in my frustration of trying everything and everything failing I deleted alsawizard and alsaconf (I'd usually just rename them and put them elsewhere, safe, but I was blinded with rage and just wanted them gone). After that nothing would work at all, even after I recompiled everything from scratch again. It turns out AlsaWizard is just a script to run Alsaconf, so it was not included with the Alsa I downloaded and everything has compiled fine, its just that it hasn't been integrated with Puppy and even though I deleted all mention of the .PETS some old files were still left and given priority over the newer files (like the alsaconfig I deleted) I found the new alsaconfig and put it where it belongs and now when I type alsaconf in a terminal I get alsaconfig 1.0.19 but... still no sound. The new Alsa folders I now have do not directly correspond with the Alsa folders I have already in Puppy, so its hard for me substitute the folders and to find what belongs where.

On an ironic note the only sound on my CPU that does work is the annoyingly loud internal speaker. I read about the code modprobe -r pcspkr and that works nicely, but I can't find a way of getting this done automatically when Puppy boots, so I have to type it in each time after I boot up (which has been a lot recently). I've tried adding "options modprobe -r pcspkr" to the modprobe.conf but that didn't work and I tried renaming the file pcspkr to spcspkr and that worked for a couple of boots but it didn't stick, I don't want to delete it, just disable it.
Any suggestions?

try adding it to /etc/rclocal
or add
in /etc/modprobe.d/blacklist

Hi repo, I tried adding modprobe -r pcspkr to /etc/rclocal, but it didn't work.

Puppy didn't have the folder modprobe.d or a blacklist file for modprobe, so I created them and added blacklist pcspkr to blacklist, but that didn't work either.

Do I need to add a symlink somewhere or set the blacklist file in any way? I noticed when comparing the blacklist file to the modprobe.conf file that they both have ASCII text but the blacklist file has no line terminators, could this be the problem?

Hi,

Sorry,

The file in puppy is
put the whole path

Thank you that worked great. It used to really bug me because I have no mouse and I have to use mousekeys, but mousekeys keeps timing out, and turning it back on was noisy.

I would suggest you delete the files you created, to avoid confusion in the future