site  contact  subhomenews

Sound Wizard frontend window

May 13, 2011 — BarryK
When someone boots Puppy for the first time and sound does not work, the natural thing to do is to run the "ALSA Wizard". However, that may not be the best thing to do.

When a user chooses "ALSA Sound Wizard" from the Setup menu, or via the 'setup' icon on the desktop, the script that runs is /usr/sbin/alsawizard, and up until now that just launches /usr/sbin/alsaconf, the full ALSA setup script.

One of the problems with 'alsaconf' is that it hard-codes the audio driver selection into /etc/modprobe.d/alsa.conf, whereas Puppy normally detects the audio hardware freshly at every boot -- which is good if you are booting from a USB drive on different computers.

Another problem with 'alsaconf' is that it may be unnecessary to run it. Audio may actually be working, just need a checkbox ticked and/or a level adjusted in the mixer. Also, on rare occasions it may actually require a reboot for sound to work, due to other peripherals (especially modems) having conflicting audio driver requirements which Puppy might not be able to sort out until the second boot.

Therefore, I have created a preliminary window in /usr/sbin/alsawizard, that enables you to run the mixer, play a test sound, consider the reboot option, before choosing to run the full ALSA Wizard.


that will help

Is sound done differently in ...
Username: GCMartin
"[url=][b]One Puppy member reviewed a Live media standalone security distro called LPS in the forum[/b].[/url] That member's position in the report indicates that this distro "seemed" to have solved the infamous sound problems which are traditional with Puppy. I, by no means, am an expert. [u][b]If[/b][/u], though, they have found a way to be more successful in their Live media implementation for audio operation, then, the LPS method could offer some useful insights for us, here in Puppyland. Hope this helps.

Tags: woof