Messages

1

Angstrom & OpenZaurus / Oz3.5.3 (collie) On/off Button Problem

« on: June 23, 2005, 01:14:26 pm »

What is surprising is why this bug should creep in to OZ in the first place. This bug has not been in previous versions upto know.
The problem should be easy to trace,  its either a kernel bug or a bug in one of the programs that are running from the  filesystem(s).
 
Its unlikely that this could be a kernel bug, as i am assuming that no one has done any changes to the ancient kernel 2.4.18-rmk etc which is in use on collie for a long time. So if we use the same kernel that is used for a previous OZ release (3.5.2) we should be able to see if the bug occurs in it too.

Someone did it and the problem occured, see https://www.oesf.org/forums/index.php?showtopic=11948&st=75.

The kernel is reponsible for the stability of the system and peripherals (including power management). So when this fails, the kernel has to be corrected.

Nevertheless, some incorrect usage of some kernel API brought in by some recent change in OZ may have triggered a problem that was invisible before.

2

Angstrom & OpenZaurus / Oz3.5.3 (collie) On/off Button Problem

« on: June 20, 2005, 05:29:53 pm »

I finally downgraded to OZ3.5.2 . Now my Zaurus is back to a usable state (the buggy state reminded me of Windows 95 :-p ). I had to add the missing "devel" feed to ipkg.conf for libstdc++ and could reinstall iqnotes and other useful apps.

If you can vote or comment on the bug report on
http://bugs.openembedded.org/show_bug.cgi?id=54
it might somehow attract more attention among openembedded developpers, at least going from NEW state to ASSIGNED.

Regards,

3

Angstrom & OpenZaurus / Oz3.5.3 (collie) On/off Button Problem

« on: June 03, 2005, 04:39:09 pm »

I've filed a bug report about the problem, see
http://bugs.openembedded.org/show_bug.cgi?id=54
and add possible relevant comments there.

4

Angstrom & OpenZaurus / Oz3.5.3 (collie) On/off Button Problem

« on: May 13, 2005, 03:45:43 am »

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.

5

Angstrom & OpenZaurus / Oz3.5.3 (collie) On/off Button Problem

« on: May 10, 2005, 07:25:58 am »

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.