Puppy Linux Discussion Forum

Sylvander · Posted: Wed 07 Dec 2011, 16:36 Post subject:

ASAP....

I'll try this new ISO...
Using a lupusave file on a Flash Drive.

smokey01 · Joined: 30 Dec 2006 Posts: 1605 Location: South Australia

playdayz · Joined: 25 Apr 2008 Posts: 3705

mavrothal, There is a new lupu_devx_528-4.sfs with /usr/share/libtool/config.guess. Thanks.

ftp://distro.ibiblio.org/puppylinux/puppy-5.2.8/lupu_devx_528-4.sfs
bf14b9eea9d67ad2f58dd11dc15832f7 lupu_devx_528-4.sfs

shinobar · Joined: 28 May 2009 Posts: 2256 Location: Japan

I upload my proposal of /etc/init.d/10alsa and /usr/sbin/snapmergepuppy for your testing. I hope rechard will review them.
EDIT(2011-12-10): merged rerwin's patch-4 but skipped some:

10alsa:

Sylvander · Posted: Wed 07 Dec 2011, 20:15 Post subject:

A. I downloaded test01-lupu-528x.iso and burned it to a CD-RW as per usual.

B. Booted it using the command:
puppy pfix=ram
So as not to use any of the existing lupusave files.

C. Once into the desktop of this Lupu:
1. Made various necessary config changes [language, region, keyboard].
2. Installed Pupsaveconfig-1.9.9 using the PPM, and used it to make a lupusave file [in a suitably named folder in the root of the ext3 only partition] on my 4GB Flash Drive, and rebooted.
The loudspeaker icon was still there after reboot.
3. Installed Xfe.
4. Installed Firefox-3.6.13-Lucid, and updated to 3.6.24.
5. Installed Wine-1.3.13-Lucid52.
6. Installed Frisbee-beta-2-Lucid52.
7. Installed Parcellite-0.9.3-lucid.

D. On the 4th reboot...
Prior to shutdown, I clicked the "Save" icon, to save during the session.
At shutdown, when the Pupsaveconfig->Save?=y/n was displayed I CHOSE TO SAVE...
Once back into the Lupu desktop, the loudspeaker icon was GONE.
I'm typing this whilst in the session after 4th reboot.

shinobar · Joined: 28 May 2009 Posts: 2256 Location: Japan

rerwin · Joined: 24 Aug 2005 Posts: 1317 Location: Maine, USA

Here is a significant fix for USB flash-drive installations. It corrects the management of whiteout files, to avoid upsetting the layered file system (aufs/unionfs). It should be installed after Instant Update 002 (or 003).

The patch package is cumulative, containing patch-3 plus an upgrade to shutdown to support user-controlled saving of personal data. That feature is tested for the case where only the personal data is stored in a flash drive pup_save file. I am unable to try a flash-drive installation or the partition save on a flash drive, so welcome feedback from anyone needing that option for such installations.

Also, I include the more recent version of usb_modeswitch, 1.2.0, since it is already in wary. Keeping up.

After installing patch-4, clean out any residue from two /dev directories from the save layer. Run these commands:

Then reboot. There will be no visible difference until the reboot is done. When you shut down after the reboot, you will be asked whether to save automatically or not. If "not", you will be asked whether to save the data now. Subsequently, no periodic automatic saves will be done. Click the "save" icon to cause saving, at any time. On new installations, to avoid any automatic saving, reboot again within a half hour, before the first automatic save, to see the "save" option request.

Next, I will check shinobar's latest offering, to see how it relates to what I have done.
Richard

Sylvander · Posted: Thu 08 Dec 2011, 05:17 Post subject:

@rerwin

A. OUCH!
I've only just deleted my latest lupusave for Lupu-528.003-ataflash...
But I have FIVE backup copies made at earlier points in time.
Number 5 [the latest] includes a state where the loudspeaker icon was still present.

B. Would this be suitable as a copy to try your fix upon?
No need to install instant update 002 or 003? [Because this ISO includes those, right?]

C. Should I be trying your fix before attempting that suggested by shinobar?

D. At this moment [typing this], I'm back using Lupu-526-ataflash, which is [of course] WORKING JUST FINE! Very Happy

playdayz · Joined: 25 Apr 2008 Posts: 3705

Thanks for testing that test01 iso Sylvander. It seems to me that you could try shinobar's test easily (about deleting the /dev/snd). You could try it on any installation you have that is broken.

You could also try rerwin's patch-4 on an installation of lupu-528.003.

I will wait for any information from you plus for rerwin to examine shinobar's fix and see if he wants to incoporate it, then I will make a new iso from it and we can see about that.

Test01 does have Update 002 in it, but as I say, I think you could try shinobar's test on any one that is broken.

For general info, I think we are making some progress. At least we have determined several things that are not causing the problem. If the latest from rerwin and shinobar gets it then we will be in good shape. If not, ugh, we will try to revert various items to 526.

bigpup · Posted: Thu 08 Dec 2011, 14:52 Post subject:

Sylvander,

We all thank you, in willingness to help, as the lost sound test mouse. Your system seems to be the best test bed.

Just hang in there and be resolved to the final found fix.

To all that are working on the sound lost problem.
WE ALL THANK YOU!!
The easy answer is not always the best.
Do not be overcome by impatience, like our last test mouse. Wink

ETP · Joined: 19 Oct 2010 Posts: 310 Location: UK

Hunt script
The attached script when placed in the startup folder provides an early warning of possible corruption in the aufs filesystem and may prove useful for testing purposes. It could easily be modified to run a series of different tests. Please go easy on me as its my first bash at bash!

Karl Godt · Joined: 20 Jun 2010 Posts: 2676 Location: Kiel,Germany

ETP · Joined: 19 Oct 2010 Posts: 310 Location: UK

Karl
Thanks for pointing out my error which I have corrected in the post and attached file.
I take onboard your points and will examine the areas that you suggest.

Given my post on page 50 of this thread however, this script was only intended as a quick & dirty litmus test for possible corruption. Do you consider that as such it is a valid test? (i.e. is there ever any legitimate reason for the appearance of "whiteout" in the log?)

ETP · Joined: 19 Oct 2010 Posts: 310 Location: UK

Karl
Thanks for pointing out my error which I have corrected in the post and attached file.
I take on board your points and will examine the areas that you suggest.

Given my post on page 50 of this thread however, this script was only intended as a quick & dirty litmus test for possible corruption. Do you consider that as such it is a valid test? (i.e. is there ever any legitimate reason for the appearance of "whiteout" in the log?)

Karl Godt · Joined: 20 Jun 2010 Posts: 2676 Location: Kiel,Germany

I can not remember many hassles for whiteout files , but one I will always remember :
I made an adjustment to rc.shutdown to save a copy of /etc/rc.d/PUPSTATE .

This is one of the most important configuration files , sourced by nearly every puppy.sh script .

This file gets created every time new @boot .

I made the copy using the mv command like
mv /etc/rc.d/PUPSTATE /etc/rc.d/PUPSTATE.prev
at the end of rc.shutdown .
mv deleted the /etc/rc.d/PUPSTATE file and created /etc/rc.d/PUPSTATE.prev but left a whiteout file .

This got me a corrupted /etc/rc.d/PUPSTATE file at boot and no fsck could help it . It took me a while to figure out , that i had to remove a/some whiteout files to make fsck work correctly .

Without knowing its PUPMODE Puppy will hang/crash/not work .

Until i recognized the whiteout file
i started to adjust the main boot/X/shutdown scripts with lots of unecessary code like
[ -f /etc/rc.d/PUPSTATE ] && . /etc/rc.d/PUPSTATE
if [ -z "$PUPMODE" ] ; then
dolotsofcode(){
#rdev,df,mount to guess the PUPMODE
}
fi

Laughing