Puppy Linux Discussion Forum

[alejobar]

Hi there,

I just tried puppy 4.1 in two old Pemtium 2 pcs, one I used Puppy 4.1 regular and I had to use Puppy 4.1 retro for the other one because it didn't start after installation. The one that I used Puppy retro have a Creative Sound blaster sound card, when I used puppy 4 I had to change manually the Modprobe file to snd -sbawe to get the sound working, now with the new puppy I just run alsaconf and puppy found the correct card, then I set up the volume in Alsa mixer, Master 90% PCM 90%, close and reboot.
After reboot I can see now the the speaker in the tray, but its marked with a red X, so click it turn up the volume, no sound! , run alsamixer again master was up, PCM was in zero, again I change it manually, this time I type alsactl store to save the settings, reboot and again the red X and no sound , so I run alsactla restore and settings are back but why they don't stay after reboot? how can I fix this? I hope someone can help me

[alienjeff]

Once your levels are set to your liking, ESC alsamixer. Then type: alsactl store

See if that works.

[alejobar]

[`f00]

Sometimes the tray applet (usually absvolume) plays nice with alsamixer, sometimes not - sometimes absvolume disappears - it'd be wonderful if all hwr worked oob, but then how would the user ever learn cli

Thanks for the tip to 'lock in' alsamixer settings, AJ - yep, sometimes they get deprecated if the pup 'finds' etwas anders 1st (like an old usb headset that's still plugged in, lol) hint that something's off - 1 setting vs the many sliders and mutes on an emu10k

[alejobar]

Still no luck! I tried all the commands and Alsa don't seem to keep the settings after boot, even they are stored , everything seems to wor fine with puppy 4.0 but know I have this problem with puppy 4.1 retro, I guess this will q be a bug or something. I hope someone else could give me a possible solution

[Pizzasgood]

Hmm... Looks like the script /etc/rc.d/rc.alsa is set up to save and restore the settings on shutdown and bootup. But it has some if statements. It won't even attempt to restore the sound unless these conditions are met:
the sound driver was started successfully
alsactl is located at /usr/sbin/alsactl specifically and is executable
the directory /proc/asound exists
the file /etc/asound.state exists and is readable

My guess is one of those isn't being satisfied properly, causing Puppy to not even try restoring the sound settings.

If you can't track down what exactly the problem is, you should be able to workaround it by adding the command alsactl restore to /etc/rc.d/rc.local.

[alejobar]

thanks Pizzasgood, I'm going to check all that and see what could be the problem.
Yesterday I installed a cheap PCI audio card and puppy recognized at boot up and everything seems to work, but the sound is not as great as the old HUGE creative Awe card, I took it off the computer and its really a HUGE card hahahaha, so I will try to install it again and see what happen.

I really think its a bug, because I tried in another computer, an old Compaq Armada M700, I remember I had to edit modprobe manually with Puppy 4.00 to make the sound work, now Puppy 4.1 seems to find the card after alsaconf, but again I have trouble with the volume settings and with absvolume in the taskbar.

[smagin]

Hi.
That's what I did to overcome muting volume every reboot. i have Crystal CS3247B ISA, Puppy 4.3

1. Switch off PNP OS in bios
2. add pnpbios=off to /boot/grub/menu.lst to the end of linux kernel boot string
3. Install sound with alsaconf (run "alsaconf" in terminal)
4. Run alsamixer, unmute all channels and maximize them. Check if sound works.
5. Exit alsamixer and run "alsactl store"
6. Add "alsactl restore" to the end of /etc/init.d/rc.local
7. Reboot

By the way, the zmixer's icon in tray stays X-ed after reboot but sound works actually.