Hello,
opening a new thread for discussion about several problems I have with pdaXrom 1.1.0beta3 on the SL-C3100.
Flashed it with 121MB root fs size.
* Setting date and time:
After a suspend it always falls back to some date like August 17th 2005 and time 23:50 or similar. I have tried setting the time via the GUI and via "date -s" command.
When I set the time via date -s prior to "startx", it does not suspend and reports the time correctly. But after a reboot (without startx in between), it falls back to Aug 17 00:24:54 UTC 2005!
(Seems as if two parallel times are counting: a hardware clock which is not updated when using time -s and the software clock which uses the date -s time... I have seen something like that on MS-DOS machines before)
EDIT: This issue is solved:
I had to stop the atd daemon in order to let the hwclock tool access /dev/rtc. then, after setting the software time with "date -s", a "hwclock --systohc" also set the hw clock correctly, and the time survives a reboot!
* After setting the time with date -s or the GUI, the Z suspends. When using the GUI it wakes up again, when using date -s it doesn't.
* The Z sometimes suspends without me having told it to and no suspend timeout could have elapsed. Maybe has to do with date/time issues (timeouts running too quickly?)
* When installing packages via the ipkg command or package manager GUI, the root fs fills up and packages cannot be installed because IPK files are stored in the root fs before they are installed. Any way to tell the package manager to use another temp storage for the IPK files?
* When installing using the ipkg install [packagename] command, I often get 404 errors when it tries to download package with name "__.ipk". Why does it try that?
I have set up quite some feeds and with "ipkg update" they are correctly read in, no communication errors when updating.
* Sometimes after a suspend the taskbar applets are almost all gone (including the clock). Only the card eject applet is still there. What could be the reason?
* Once on poweron after a suspend the GUI was not operable at all. Time counted on the clock and mouse cursor moved when I moved the USB mouse, but nothing else worked. Even after subsequent suspend / wakeup cycles this didn't change. required a reset. (Not even Ctrl-Alt-Del etc. worked).
* After installing kdepim/pi 2.2.7, kopi-apm and atd (dependency of kopi-apm), kopi alarms do NOT wake up the zaurus (ko/pi running, Z suspended, ko/pi configured to use internal alarm feature). Did I miss something or does this not work reliably?
EDIT: This is solved now with the issue above setting date and time. Alarm now works!
* Where to start if I want to develop on-board (mainly for compiling ready-made console applications such as mutt, nano etc.)? Is it snough to install the relevant packages such as gcc, make etc.? Or is there an all-in-one package somewhere?
...well, if I cannot resolve some of these problems, I may have to switch back to Cacko again, because I need a reliable machine. I need my calendar and contacts one keystroke away, but I'd have found it nice to have a full-featured X system as well because of the compatibility and the large software base which can be used. So please, could you help me with these issues? It would be so nice if I could stay with pdaXrom!
Once everything is up and running I will provide a detailed description of all problems and solutions, and my setup in general, similar to the Cacko description I have published here:
http://www.daniel-hertrich.de/zaurus/zpsThanks a lot
daniel