5600 won\'t suspend!?!?

[Ethereal]

OK, was messing around trying to get kismet installed on my SL-5600, and have noticed that the device won\'t go into suspend, either via a long press on the Cancel key, or by selecting \"Suspend\" from the QT menu in the lower left corner of the GUI.  

I\'ve uninstalled the kismet .ipk, I\'ve restored a backup (using the Sharp PC-based Backup-Restore) from a couple of days ago--when I know the On-Off button was working (hard to miss a thing like that), but the problem persists.

Next on the to-try list is a complete reflash of the stock ROM, but I was hoping someone here might have a suggestion to spare such drastic measures...

[w4lna]

OK, was messing around trying to get kismet installed on my SL-5600, and have noticed that the device won\'t go into suspend, either via a long press on the Cancel key, or by selecting \"Suspend\" from the QT menu in the lower left corner of the GUI.  

I\'ve uninstalled the kismet .ipk, I\'ve restored a backup (using the Sharp PC-based Backup-Restore) from a couple of days ago--when I know the On-Off button was working (hard to miss a thing like that), but the problem persists.

Next on the to-try list is a complete reflash of the stock ROM, but I was hoping someone here might have a suggestion to spare such drastic measures...

Did you try ejecting or removing the network card?

I\'ve noticed that the card\'s status seems to be persistent even through a reboot cycle.

[Ethereal]

Yes, I removed all cards, first CF and then SD.  Nothing helps.  I have actually gone ahead and re-flashed back to stock ROM, which still didn\'t fix the problem.  I went back into the update menu and formatted the Zaurus, which finally remedied the problem.

Then I restored from a 2-day-old backup--and the problem is back!

I am absolutely sure that suspend worked when I made this backup--kinda hard to overlook a device that can\'t be turned off!

I am now wondering if there is something about the PC-based restore program itself that breaks something QTopia is trying to do to go into suspend.  (I used the restore program earlier today to fix some wierdness that a misguided .ipk had caused.)

The actual suspend function appears intact: any read access to /proc/sys/pm/suspend will put the device into suspend, and the power (Cancel) button brings it out appropriately.

So, can anyone offer advice as to where QTopia hides its config file defining what it does to go into suspend, and how it might be fixed?

[Ethereal]

Update: I\'ve slogged blindly through the inner working of the Z\'s suspend and resume scripts, and it appears that /usr/local/bin/apm.rom is missing.  

I made a calculated guess that this was supposed to be a symlink to /usr/local.rom/apm

...drumroll, please...

The suspend button works!

I\'m not opening the champagne yet, but the problem seems to be fixed, which leaves me wondering: how did this happen in the first place?  How did this one lonely item (please, please, please let it be just this one) get excluded from the backup?  Perusing the \"All Data\" tab of the backup, I see no symlinks whatsoever listed, although it appears all others were restored normally...

[Anonymous]

Ive noticed many files ( i had searched for certain file types) that are present when you do a find.  

cd /
find . -name *.png  lets say

and then search the backups synching to desktop and I see some missing.

Interestingly after changing roms, from sharp to oz to zynergy, and then reinstalling gaim, i still have my profiles from round 1. Which leads me to believe that the format does not format the entire rom, that the backups do not backup everything, so ...

[Ethereal]

This is a guess (based on observed results), but I believe:

Upgrade (Flash) ROM--erases/rewrites the read-only portions of the zaurus filesystem

Format--erases (and rewrites to some default state?) the read-write portions of the zaurus filesystem.

[Optogeek]

I have just had the same problem with my SL-5500 (UK with 3.13 rom).    Same situation, after recovering from a back-up suspend stopped working.  After I fixed the link it now works.

[Ethereal]

Is this some sort of pervasive bug (since we\'re not even using the same SL devices) in the Shap backup-restore program?  Anyone else out there experienced this?

[tumnus]

The apm.rom file is created by installing the Suspend/Resume ipks. It gets moved from \'apm\' to make way for a script that is necessary for the suspend/resume stuff. Once it\'s installed ok with sudo it should work and stay working. If files like these move or sym links start pointing at the wrong place, then something wierd is going on. I\'ve never seen it though.

Anyway, your summary of the Update and Format processes are correct, Ethereal.