I see. My mac has no problem with that and when a click on it in XOpup/Fedora/Ubuntu Midori/html viewer/Browser just opens it so I did not consider it an issue, but you are right should be corrected.

01micko wrote:

I think we should stick with this kernel/aufs patch for awhile and work out the bugs.

I would agree with the kernel, but there is now Aufs2.1 that might address some of these issues. I'll give it a try and see if things improve at all._________________Kids all over the world go around with an XO laptop. They deserve one puppy (or many) too

there is now Aufs2.1 that might address some of these issues. I'll give it a try and see if things improve at all.

Quoting myself...

I did make a new kernel with Aufs2.1 and now the devious powerapplet pet leaves no trace behind after installation .
I also have the sense that on "bad" cards/usbs corruption of the savefile during suspend is not that often but I did not check enough to verify.
Please download the new /boot10 folder (is only for the XO-1 not XO-1.5) and test.
You may need a new lupsave file though.
The new "boot10" folder with the new kernel vmlinuz/initrd.img is HERE

With this kernel "uname -r" should be: 2.6.31_xo1-20101006.1917.1.olpc.12d6406_PupAufs21_________________Kids all over the world go around with an XO laptop. They deserve one puppy (or many) too

Here is a pet that in my hands solves most (if not all) of the squashfs corruption issues observed at times, when waking up from suspend.
What it does is a) to snapmerge whatever is in RAM before going to sleep and b) add a 5 sec delay between the final sync and device powerdown allowing any caches to be written.

As a result it takes up to 15sec longer for the XO to actually go to suspend but this is happening after the screen goes black or the lid closed. It just takes longer for the powerlight to start blinking (the indication of suspend) and you will see USB activity (if your stick has a light) the first few seconds after the "suspend"

Now if someone (hi Mick ) can write a script that could do that in XOpup, or check and correct during shutdown, wouldbe nice.
Though is not trivial since white space files are not shown because of Aufs configuration and changing that opens the door for all kind of user messups _________________Kids all over the world go around with an XO laptop. They deserve one puppy (or many) too Edited_time_total

Here is a pet that in my hands solves most (if not all) of the squashfs corruption issues observed at times, when waking up from suspend.
What it does is a) to snapmerge whatever is in RAM before going to sleep and b) add a 5 sec delay between the final sync and device powerdown allowing any caches to be written.

As a result it takes up to 15sec longer for the XO to actually go to suspend but this is happening after the screen goes black or the lid closed. It just takes longer for the powerlight to start blinking (the indication of suspend) and you will see USB activity (if your stick has a light) the first few seconds after the "suspend"

Pls test with your "bad" media and report

Clarification, are the files inside the readonly squash file system getting corrupted? or is the sfs file itself getting corrupted? If the sfs file itself is getting corrupted, I think the file system itself would be corrupted; therefore, any file located on the boot media might be corrupted?

Clarification, are the files inside the readonly squash file system getting corrupted? or is the sfs file itself getting corrupted? If the sfs file itself is getting corrupted, I think the file system itself would be corrupted; therefore, any file located on the boot media might be corrupted?

Regards, Ron

Actually the corruption is in RAM! Because probably some device may try to direct access memory (DMA) while the machine is asleep forcing a memory self refresh that generates the corruption (something like that was explained to me ).

Short answer, NONE of the actual lupu-511.sfs, lupusave.3fs of any other sfs is corrupted, UNLESS you save them.
The lupu-511.sfs is read-only so does not get corrupted anyway but the lupusave is read-write and gets corrupted on save after the RAM corruption.

My advice. If you see that something is "wrong" just "hard reboot" pressing the powerd button for 5sec so changes will not have the chance to be saved into the files. On reboot should be fine, but the session data will be lost

However, the new powerd_xo.pet should eliminate these instances since saves all the RAM data before suspend and adds 5 extra seconds after the save step and before device(usb/card) poweroff

I hope this is clear_________________Kids all over the world go around with an XO laptop. They deserve one puppy (or many) too

I replaced the boot10 folder, cleaned up the wh files and loaded the powerd/powerapp pet files. After doing this using a new pupsave file, everything seems to be working fine. Thanks for the clarification on the corruption problem. I knew the pupsave file and /mnt/home were the only entities mounted read/write; therefore, your explanation of the corruption problem makes total sense.

BTW, all this was done booting from the same flaky usb stick.

Thanks for all the hard work!!!
Regards, Ron
Time for RC4??

UPDATE: The powerapp has two battery symbols on the desktop and ps indicates there are TWO copies of powerapplet_xo running. I

We are cooking 1.0! but the power management although improved is not there yet

rrolsbe wrote:

UPDATE: The powerapp has two battery symbols on the desktop and ps indicates there are TWO copies of powerapplet_xo running. I

Does it persists through reboot?
There is a problem with PPM in puppy/lupu in recent releases. Till the next release try installing the file from HERE (is not a pet). Works much better in my hands_________________Kids all over the world go around with an XO laptop. They deserve one puppy (or many) too

We have XOpup-1.0_RC3 on a usb stick booting on Cl1 Q2E45. When it gets to switch root, we get a kernel panel, not syncing message. Has anyone had this problem and is there a solution for it? Thanks

Something is messed up with your setup/stick but without any info we can not know what. Kernel panic can happen for many reasons so if you want to get at the bottom of it provide some more info about the problem and the setup (a good idea in general when reporting problems)
So do the following
1) Boot in Sugar and verify that XOpup-1.0_RC3.tar.gz that you downloaded in intact eg has the correct md5sum. In sugar terminal type "md5sum /path_to_file/XOpup-1.0_RC3.tar.gz". The output sould be: bc3f733dfb90f139a5f34cb75077a37d
2) while still in Sugar put your usb stick in and from the terminal issue

Code:

su
fdisk -l /dev/sda

Post the output (copy/paste) here so we can see how your stick looks like partition/filesystem-wise
3) still in the terminal type

Code:

ls -al /media/stick_name/

where stick_name is the actual name of your stick, and post the output here so we can see what other files my be missing of conflict with XOpup.

Another common source of problems when writing/extracting something in a USB/SDcard on the XO, is that the device may be removed before it has the chance to be written fully (I did it few times ).
Just type "sync" in the terminal when you copy extract something to make sure everything is in sync_________________Kids all over the world go around with an XO laptop. They deserve one puppy (or many) too

Problem solved: In summary you need the developer key, the correct firmware installed, the right md5sum on your XOpup download. We extracted to /media/disk on a formatted usb stick with partition 1 as ext3 and partition 2 as swap. (This was done on another computer running Mepis Linux 8.5 so does not have to be on the OLPC). Everything seemed to work OK including sound and wifi (as eth1). This transforms the OLPC from a Fedora novelty toy to something that would be very useful with super wifi, office suite, ability to add more programs, etc. and it is lightweight, rugged, waterproof, dirt proof, etc. Thanks again.

XOpup gained some more stability and features and is out as XOpup-1.0
Check the top post for more info and download.

So now what...?
For v2 we* are thinking decreasing the size of the build while keeping Ubuntu compatibility is a main goal.
To that extend we think to remove the IceWM, the CD and DVD related applications, PPLOG and server apps and other not likely to be often used apps.
Replace Abiword, Calculate and paint with lighter versions etc.
The originals are going to be available as a separate sfs or pets but not in the build.
The idea is to build a small and even more efficient/fast base and allow users to customize it according to their needs by adding on top anything, from OpenOffice to... Sugar!!! while the base remains sufficient for most daily uses.

If you have any suggestions fore or against specific apps, or better yet can help out, let us know.

* we = 01micko and me _________________Kids all over the world go around with an XO laptop. They deserve one puppy (or many) too