From your comments and diag file I conclude that you have installed many packages and then upgraded from 526. Did you upgrade to get to 526? This presents a confounding situation, in that much can have happened that will not be revealed by the usual diags. I think we need to try to start fresh to determine whether your particular sound driver is a factor.Sylvander wrote:1. Oh dear! The problem has returned.
2. What to do now?
Please create a clean puppy and try that for a while, to see if you can break it:
- Boot from CD or a frugal installation of the original lupu 528 iso, with pfix=ram (or pupsave 0, if that is an option).
- Immediately reboot and create a pupsave file (so that any IU2 file removals will stay removed).
- Then install Instant Update 002 and rerwin_patch-1
- Immediately reboot.
- After waiting 5 minutes without doing anything else, run pmodemdiag and rename its tar.gz file slightly, to make it unique.
- Assuming the speaker icon is still there, do some reboots and try alsawizard (always running it to completion - woof-woof) to see if the icon will disappear.
- Whenever the speaker disappears -- other than during running of alsawizard -- immediately get another pmodemdiag file.
- If the speaker icon behaves as you expect, try doing more of your usual activities that lead up to its disappearance. That could include installing some of the packages you need, but try only a few at a time, interleaved with reboots and alsawizard.
And then there is a desperation measure: list the names of all files in the pupsave file. The command to do this might be:
ls -AR /initrd/pup_rw > /tmp/ls_pup_rw.txt
Then gzip the txt file for attachment. That will entail looking for "a needle in a haystack", but it might show some left-over files from the upgrade process(es) that could confuse puppy.
I think our best course is to methodically (tediously) add to your pupsave until we find what breaks retrovol. BTW, do you ever cancel/bail out of alsawizard? That could be important.
Richard