Puppy Linux Discussion Forum

[live]

Stupid, but I lost the sound after some install, uninstall (none about sound drivers).

Where do i see if the sound is not simply muted?

[shadow of viper`]

hello,

have you tried alsamixer?

open a tern=minal and type

alsamixer

check if all the values (bars) are non-zero in the window that opens up

if that dint work for you, please post your hardware configuration and puppy version and how you use puppy (frugal or full install etc)

i am sure someone here would be able to help, cheers!

[Sylvander]

I had the same when I updated from Lupu-526 to Lupu-528.

Needed to run "Menu->Setup->Alsa_sound_wizard".
That detected my sound card[s]...
I chose a driver to use [the correct one]...
Alsa set it up for use, then generated 2-barks sound to indicate success.
Sound was OK after that.

Reason for needing to do this was:
Alsa had been updated in Lupu-528...
So the previous Alsa sound configurations had been wiped at the update.

[live]

Hummmm...

>have you tried alsamixer?
sh-4.1# alsamixer
cannot open mixer: No such device
sh-4.1#

When I launch the Alsa Sound wizard and select the correct drive, after a while I get:

Loading driver...
Setting default volume...
amixer: Mixer attached default error: No such device

Strange alsamixer whipped out and cannot be re-installed?

[Sylvander]

Search HERE...

Using the following term EXACTLY:
"Mixer attach default error: No such device"
Copy and paste it.
[Include the quotes]

[loubapache]

First post here.

Have been a long time Ubuntu user but played with Puppy Linux and really liked it. However the sound issue in 5.2.8 forced me back to 5.2.5. I am convinced that there is some problem with sound in 5.2.8.

After some software install or removal, the sound would not work again in 5.2.8. I can get it back by using the Alsa_sound_wizard even though alsamixer would give an error (it won't run). That would work for the session. Even if I SAVE the session, the next reboot would lose sound again. I can repeat this a couple of times then eventually even Alsa_sound_wizard would not bring back the sound (Mixer attach default error: No such device). It is really strange.

5.2.5 does not have any of these issues.

[playdayz]

[live]

Playdaz

It was from a fresh install.

It worked until I install & uninstall some soft, which one I do not know, but it not the 1st time I bang into this, even with 5.2.5 but as I said I didn't notice which apps did that as I installed and bunch at once.

I think I'll wait for the next release of upu_528_k3.0.4_SMP(cpu)
and will restart the process and keep an eye on that.

[loubapache]

Thanks, playdayz. I have restarted everything.

fresh install of 5.2.8
Instant Update 001
installed all the PETs, SFSs, and potable Linux Apps.

All good so far. I took a painstaking approach to backup the savefile in every single step. So at this point I remaster the setup.

Now, the sound problem started when I try to do either of the following:

1) edit the "/etc/inittab" file in order to put a password for the install (root).

2) edit the "/etc/rc.d/rc.shutdown" file to disable the autosave at shutdown.

Somehow either one of the above is also changing the sound configuration setup. A bit strange.

Alsa_sound_wizard would not bring back the sound.

When I go back to the previous savefile. Sound came back (of course).

So my question is:

How is sound conf saved in the system? Maybe I can manually back that up, do all the changes I want, then restore the sound conf setting.

Thanks,

[loubapache]

When the sound is not working (no volume icon in tray either) and run retrovol, this is the error msg:

retrovol: hcontrol.c:573: snd_hctl_load: Assertion `hctl->count == 0' failed.
Aborted

[loubapache]

An update to my sound issue. For the time being, it is solved but I still do not understand why it behaves this way.

Setup -> Default Applications Chose -> Audio Mixer to Retrovol (from alsamixter).

Then I can do whatever and the sound always come back after reboots. So I have finally a working copy of 5.2.8.

My 5.2.5 worked great without problems but I saw a nicer Chinese PET for 5.2.8 and really want to use it.

Just a few more treaks here and there and I will be using 5.2.8.

Thank to all the helpful people on this forum.

[moijdikssekool]

i still have this problem. I'm not sure, but the problem has appeared one time when my ram reached a temporary maximum (total used memory increased till a moment it goes down, some caches are automatically deleted). Perhaps, some files related to sound are loaded without protection in RAM and are considered as caches by the system
it's a suggestion, no more

[PaulBx1]

I have the problem in lupu 528 on my Dell Mini 9. Alsa sound wizard finds the intel sound hardware but cannot play a sound. Amixer flashes on the screen and exits (too fast to see any error message)' No sound icon on the task bar. When booting windows, this machine plays sound fine.

[PaulBx1]

OK, I played with this some more, booting 528 (without the update) and nothing else installed either. When it first comes up I see the speaker in the taskbar and can aplay 2barks. If I run alsa sound wizard or /etc/init.d/10alsa stop, the speaker goes away, and I never can get it back. Running stop sometimes generates error messages, but most of the time I can still aplay 2barks (which I'm guessing means it really didn't stop due to the error messages). This also generates more error messages, and if aplay fails the first time it will usually work again the 2nd time. So anyway, the speaker goes away but aplay still works, but not like you'd expect it.

I haven't yet figured out what makes sound die completely, still working...

[PaulBx1]

Well, I rebooted with the original pupsave and now have my sound back, don't know why. However the speaker icon still is missing except right after a boot.