Oz3.5.3 (collie) On/off Button Problem

[grog]

I haven't installed at (yet) on my poodle, so the problem isn't coming from that (at least not for me).

[Cwiiis]

Whaaaaaaaaaaaaaaaaat ? atd is in our Opie image?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=77097\"][{POST_SNAPBACK}][/a][/div]

Ah, perhaps not then... Maybe I should actually try this image before advising on it

[MOCKBA]

I have this problem too, opie 32-0.

[Mickeyl]

Well, all kind of things can happen. I can't confirm right now, but I know that atd really steps over apmd's toes, so we made both packages CONFLICTing each other. If atd managed to get into the base image, I'm not surprised that we have suspend/resume problems.

[ironstorm]

Well, all kind of things can happen. I can't confirm right now, but I know that atd really steps over apmd's toes, so we made both packages CONFLICTing each other. If atd managed to get into the base image, I'm not surprised that we have suspend/resume problems.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=77321\"][{POST_SNAPBACK}][/a][/div]

atd is not part of the opie image:

Code: [Select]

root@collie:~# find / | grep atd
root@collie:~#

[infoape]

Same issue's issues here. The little guy  would not wake up  *sometimes* after being put to sleep and the only way to get them up would be to flip the "replace" battery switch.  I also get the suspend on holding "right".  I've made the change to comment out the /dev/apm_bios line in the device table and things seem stable, but I still get the sleeping when holding "right".  Is there some way I can help to figure out what's wrong?
 
Oz 3.5.3
SL-5500
root on SimpleTech 1Gb SD
Socket 10/100 CF
Netgear MA701 wireless CF

[Mickeyl]

Yes, you could try to discover the instruction path from the keyboard driver to the suspend code by inserting printk's all over the suspicious places. This would help to find out where things are going wrong.

[adoptductee]

Hello everybody! I am the happy owner of a new to me collie, and I think the thing is awesome. I took me a few days of mucking around to figure out that the 32 meg SD card I bought was too small for what I wanted to do. A 128 does the job nicely, now running Hentges 3.5.3 quite happily. I do have a problem with the suspend issue though. I would like to play games and it kinda sux when I'm driving and reach down to seek ahead in xmms and the thing locks. I removed the apm line from the /etc/device_table file and the on/off button seems to work better now. Before that fix I had some luck fiddling with the buttons (press power, hold and release menu a few times, press ok, press power, life!), but that was diiiirty and it would be cool to avoid such methods.
I would love to help in any way I can, though I cannot afford to donate anything but time right now. Mickeyl: Wanna drop a hint as to where the printk's should go? I have not really moved out of my palm yet due to these issues so I can flash and reflash anything that won't make a brick. Would it be possible to replace (or cripple) apm with a dummy that catches and logs signals (from the keyboard?) but won't actually turn the unit off? Sorry if I am displaying my ignorance here. Other than the above, OZ + OPIE rocks so far.
Cheers  
-Anthony

[meyerm]

@cwiiis: How much does such a cable costs where you live? And do you have Paypal? Everybody having this problem could donate 5 or 10 €/$/... so we could get a working solutions and not just hacks ;-)

I'm willing to help buying you a serial cable for getting a better OZ. Anybody else?


PS for german readers: Was ist nun eigentlich mit zaurus.help4free.de? Ist oesf.org die neue, bevorzugte Plattform oder sind beide gleichwertig?

[Gouri]

Summary :
-synthesis of symptoms seen on my zaurus, consequences of fix
-suggestion : use old kernel (of OZ3.5.1 ?) on OZ3.5.3 ?

Standard OpenZaurus setup freshly flashed from the release :
Zaurus SL-5500
2.4.18-rmk7-pxa3-embedix-3.5.3
Opie 1.2.0 Apr 8, 2005
upgrade on 07.05.2005

The "On/off button problem" is confirmed here, too. It's rather a suspend/resume problem. I normally use the suspend menu to stop the zaurus and the same problems happen.

* Symptoms :
-Z doesn't turn on quickly using the On/Off button. I have to insist, press several times and longer. It eventually goes on.
-Z doesn't always turn off when idle (has to be confirmed). Anyway, I had it hang several times, staying on and screen lit until battery runs out or I notice and switch to "replace battery", only way to switch it off (no touchscreen, no keyboard work).
-after suspend and resume, sometimes not always, inner keyboard and/or outer buttons don't work (not always both), but touchscreen does. I think that suspending again and re-resuming fixed the keyboard at least once (unsure)
-holding right button suspends here, too
-holding contextmenu button (to switch off backlight) suspends also
-clock problems
-tried apm -S and apm -s to suspend instead. Doesn't fix.

* Tried the fix about commenting apm entry in /etc/device_table and rebooted.
Fixes all problems above, but introduces new ones :
-Z doesn't turn off when idle.
-suspend menu doesn't work
-alarm can't wake the zaurus, they only wait and fire when I resume using the button
-apm -S or apm -s don't work

* Other information
Used OZ 3.5.1 before. Never had the problem. It appears after flashing OZ-Opie image.
MD5 ok, flashed again for other reason. Problem remains.

* Suggestion
I need alarms to ring on time so I can't afford the fix.
I'm considering reflashing only the kernel part to put the kernel that was part of OZ 3.5.1 . Anyone has advice about it ? Good idea ? Dangerous ?
(I have backup of all my data of course.)

* For the curious
I upgraded from 3.5.1 because
-Konqueror did not work well on 3.5.1 (crashed on page bigger than about 15k)
-dropbear sshd did not support key-based identification
-some minor issues with USB (7 seconds to configure is a bit long, transfers a bit slow about 160-200kbyte/s, I had 600kbyte/s two years ago with exact same hardware)
I'd like to have apache+php+mysql+konqueror working well as it dit in late 2003, will try again after fixing this problem.


Thank for any advice.

[grog]

FYI. I've ran a few tests with the device_table fix & have noticed that with the fix applied the display backlight will turn off when it's set to, but then will come back on when after the same timespan, almost as if when the instruction is reached to suspend the process crashes/fails & the whole thing starts over. So the Z never does suspend by itself.

Of course without the 'fix' the Z will suspend as it's set to, but then I still get the lock up problem.

[Gouri]

So far the problem is confirmed on the OPIE image, kernels 2.4.18-rmk7-pxa3-embedix-3.5.3 with 64-0, 32-32 and 40-24 (my case).

I tried a workaround : assigning to a long press of the "home" key an "off.desktop" that does
sh -c "echo 1 >/proc/sys/pm/suspend"

which fixes symptoms (I've let /etc/device_table with its original content).
It is handy but prevents alarms to wake up the Zaurus (showstopper for a PDA).

This problem seemed never to happen till openzaurus 3.5.1 included.

I'd be happy to test any new kernel and report.

[grog]

I tried a workaround : assigning to a long press of the "home" key an "off.desktop" that does
sh -c "echo 1 >/proc/sys/pm/suspend"[div align=\"right\"][a href=\"index.php?act=findpost&pid=79564\"][{POST_SNAPBACK}][/a][/div]

I've implemented this workaround on my 5600 & IMHO it works better than altering the device_table 'cause at least my Z will suspend itself now. Thanks Gouri.

[Mickeyl]

If it works for you, it's fine - however most people will notice problems when their suspend/resume scripts don't run.

Looks like I can't encourage people to find out where the problem exactly lays, instead of trying potentially dangerous hacks and workarounds :/

(No, I can't spend the time myself, because I even can't reproduce the problem with my hardware)

[grog]

Looks like I can't encourage people to find out where the problem exactly lays, instead of trying potentially dangerous hacks and workarounds :/[div align=\"right\"][a href=\"index.php?act=findpost&pid=79591\"][{POST_SNAPBACK}][/a][/div]

I'd love to fix this problem & I'll do what I can, but I'll need guidance since I'm not a Z developer. What do you suggest? What tests can I run & what debugging info would be helpful?