Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - Bundabrg

Pages: [1] 2
Zaurus - pdaXrom / Pdaxrom Development
« on: July 20, 2006, 10:34:50 pm »
Hi All,

I'd like to discuss a few things that I think are basically some inherent weaknesses in pdaXrom, or rather its development philosophy. Please don't get me wrong as I actually quite like pdaXrom and I think there’s been an exceptional amount of good work put into it by the developer(s), and I must also applaud those who package and contribute applications. You just need to look at to see the amount of good work put in.

However my concern is that the design of pdaXrom currently prohibits its expansibility and has some pretty big risks.

What are some of the big questions that are always asked in the forums? They are things like this: -
  - Where do I find the feed for (some older version)?
  - Please could someone port app from (newer/older) feed to (older/newer) feed?
  - Where can I find (appname)? It used to be here, but its not here any more.

Currently, from my perspective, an image of a version of pdaXrom is released periodically through the efforts of sashz and Laze. These may or may not work with existing feeds (including contributed ones), and generally kind developers on the forums scramble to ensure that packages they've released still work and still have the proper dependencies etc..

My worry is that this process has the following flaws: -
  - The 'hit by the bus' issue - What if a core developer disappears/gets sick of the project. What happens to the project? Is it capable of surviving? What happens if sashz is burned out and feels that he is obligated now to keep developing since everyone is depending on him? That’s quite a bit of stress!
  - Effort to create a package - There seems to be a lot of effort needed to generate packages. Once generated, people are reluctant to necessarily update these packages unless they are actively using them as they need to almost reproduce the effort to create it in the first place unless they're smart enough to keep good logs or have a good make script.
  - Effort to create a public package - Due to the above point, it’s possible that people who could package something for the public may decide against doing it as the effort may only work for the current release of the 'rom'.
  - Lost Compiling Information/Source code - How someone packaged something (including patches) seems to be lost. This actually breaks GPL. It also means that should this person be 'hit by a bus' etc.. someone else has to re-work out how to package the app.
  - Old Version Maintenance - Old versions. Most distributions will 'backport' fixes to old versions for a period of time. Currently as soon as a release is made in pdaXrom, the old feed is 'frozen' and it used to be lost. I'm talking about non-core feeds here as well (i.e. contributed ones that may/may not with other versions of pdaXrom). No back porting is really done.
  - Dependancy Change Issue - If a major library changes (IE, say libc, glibc or something everything depends on), too many contributed packages will break! Same old story, who will go through the steps to repackage them (talking about contributed as well as core feeds)? In fact, it may take a while before someone realises the package doesn't work if it’s not too popular a package.

I really don't wish to see a project like this die because of one of these flaws. Something that most distributions have is the following: -
  - Version control with full logging and accessible access to the code. All of it!
  - A method of generating a new feed (by compiling everything based on rules/recipes) when new versions that may break old feeds come out

The advantages, especially of the latter point are: -
  - Rule based packaging - If I want to package something, I create a recipe/rule for it safe in the knowledge that most likely this same rule/recipe will work to recompile the package for future versions. I can submit this somewhere and know that someone else can run the 'rule' and get a package. This takes lots of things out of the equation
  - Effort expended only once - Because I only really have to use the effort once to create the rule/recipe I'm more likely to create packages. If I'm bored, I'll just randomly pick one and create it. Then forever more that package (possibly with minor tweaks to the rule/recipe) will be available.

What I'm describing as most of you may already know is already provided in the OpenEmbedded framework. I realise there has also be friendly (and some unfriendly) rivalry between OpenZaurus and pdaXrom, but I think that no one can disagree that OpenEmbedded does a pretty good job and takes a lot of risk away. I'm not saying this is the only way, but a lot of the work is already done here.

I decided the other day to backup my pdaXrom installation, install OZ/GPE and try out OpenEmbedded to compile things. I haven’t before because its scary learning something new and I'd heard that OpenEmbedded was a bit difficult. I took my time tracking app (Gtimer) that I use (and normally use in a debian chroot) as my challenge to package. It’s a bit of a complicated package in that debian provides quite a big patch for it (the author no longer maintains it), it’s still packaged for the older debian system (IE, the original_tar is a tar of a tar.bz2) and uses libgtk1.2. It took me 30 minutes to work out how to use OpenEmbedded (to compile nano as an example...), then 1 hour to muddle my way through to create a recipe that downloads, extracts, patches, compiles and packages gtimer (and the end recipe is only 14 lines long!!). I can submit this and know that gtimer will always be around now (since the whole feed is compiled for each version), and if I get 'hit by a bus', someone else surely can fix a 14 line file. And someone will KNOW it breaks because the WHOLE feed is compiled every version and non-compiling packages will be flagged. I also don't have to figure out how to create a tool-chain or any of the dependency libraries as they are compiled by OE automatically as part of creating my package.

What I would like to ask is if pdaXrom developers please (please!) could seriously consider using this valuable tool (or an equivalent if it exists). You can (and probably should) have a totally separate 'branch' from OpenZaurus dedicated to the pdaXrom style that people could contribute recipes to... and it also means that probably with minimal tweaking, rules can be take from the '.dev' and '.oz354x' branches and vice versa. It means that you're still 'separate' but that everyone can contribute and maintain what is a very good OS.

What do other developers and users think? This is NOT a flame starter and NOT a this-rom is better than that-rom thread! It is simply my concern that I wish to express!

 - Bundabrg

Angstrom & OpenZaurus / Keylaunch And Keylaunchrc
« on: July 17, 2006, 05:18:52 am »
Ok, I've searched everywhere and simply can't find documentation on keylaunch. So I've pulled apart the code and worked it out. To save someone else the same frustration, here are my notes.

Firstly, for those who don't know, keylaunch is used to bind 'commands' to hotkeys. For example, pressing 'Calendar' can load Calendar, and pressing 'Fn 3' can lower the brightness.

Keylaunch uses /etc/keylaunchrc, and can also be (overridden? in addition?) by ~/.keylaunchrc.

A typical keylaunchrc may look like this: -
Code: [Select]
# Comment

key=...*1:chvt 1
key=....Released F9:anothercommand

Each line has the following format ([]'s means optional. {} means its a variable):
Code: [Select]
key={flag}[{option} ]{keyname}[ {combinekeyname}][:-]:[~]{command}

Lets look at each bit seperately: -
key= - This is always the same.

{flag} - 4 characters, normally ....
 - Each character corresponds to a modifier. If the modifier is pressed at the same time, then this key will be triggered. IE, Control + 1 can give a chvt 1.
 - If the FIRST character is '?', then all the flags are ignored, and it will trigger on ANY modifier
 - OTHERWISE, each character can be '.' (not selected) or '*' (selected), and the modifiers are as follows: -
*... - Control
.*.. - Shift
..*. - Alt
...* - Fn
 - I'm pretty sure you can have more than one modifier.

[{option} ] - Optional Option. Note the SPACE afterwards if used!
  - This dictates on what event the key must trigger. If you don't specify an option it assumes when the key is pressed.
  - The events can be one of the following: -
Pressed - Occurs when the key is pressed
Released - Occurs when the key is released
Held - Occurs if the key is held for a bit
Combine - Occurs when you press TWO keys (IE Calendar+AddressBook} You MUST provide {combinekeyname}.
  - Don't forget the space!!!

{keyname} - The name of the key to trigger on
  - The names are defined in /etc/

[ {combinekeyname}] - Iff (if and only if) the Combine option is used you specify a second key here.
  - Don't forget the space BEFORE this (ie, between key and combinekeyname}

[:-] - Try to raise an existing window
  - If this exists then when the key is triggered keylaunch will first see if there is already a running instance of the command, and if so, just bring it into focus.
  - If it is omitted, then it will load a new instance every time.

[~] - Disable startup notify
  - If this exists (IE, a tilda before the commandname), then startup notify will not be used. I think this means that you won't see the hourglass in the corner.

{command} - Command to run
  - What command to run.

Feel free to post your changes you've made to your keylaunchrc files. I'd be interested in getting some ideas.

 - Bundabrg

Angstrom & OpenZaurus / Cx60 Sltime Not Working (3.5.4)
« on: June 30, 2006, 04:55:25 am »
Ok, back to the same old problem I had last time I installed OZ. Every restart my Z resets its time to some abituary time (but not 1970, so its reading some stored time from somewhere)

I installed slutils, which normally fixed the problem, but under the new OZ (3.5.4) I get the following error if I set or read the so called 'hardware' clock: -
Code: [Select]
ioctl(MEMWRITELADDR): Inappropriate ioctl for device
I'm assuming the new kernel doesn't allow this anymore. How do I store the time, and how do I read it?

 - Bundabrg

Angstrom & OpenZaurus / Opie/gpe
« on: June 29, 2006, 02:45:38 am »
Hi All,

(C860, 1Gb SD, Symbol24 Wifi CF)

OK, I'm doing a 'rom' tryout, and have now setup OZ Opie and GPE to run at the same time on VT2 and VT3. Also edited the relevant files so pressing <ctrl><alt>#num on any VT will change VT's fine. Oh, and switched / and ,.
The only thing I needed to do to really get this to work different from the wiki is to chmod u+s /usr/bin/chvt as chvt needs to run with root privs.
Oh, I also did it from the GPE image and then installing the Opie packages. The other way just seemed not to work well for me and indeed its interesting the number of differences the two ways gives (ie, /etc/ipkg/* versus /etc/ipkg.conf is one example).

Now I realise Opie/GPE is not a supported option, fair enough so I'm looking for what people who HAVE got it running did. Maybe some tricks and tips etc. I almost think that bar running qt4 under X instead, having a dual image would be useful, though installing it was fairly easy anyway.

My questions: -
  - I've had to disabled ALL idle suspends etc under both GPE and Opie. Is there anyway that the idle checker can determine if there is activity on another VT? Currently if they are enabled, then if say I'm in GPE, and Opie suddenly realises there is no activty on it for 5 minutes, it suspends.

  - Feeds. ipkg is really really REALLY slow. I think because of the base feed. However I can live with this. My issue is knowing if a package is opie or GPE when installing. Currently I comment out the opie feed, update then install when wanting to install a GPE app, and vice versa for opie. (IE, kopi is a good example). My question I guess is, are there any collisions of names between the feeds (the official OZ ones, not 3rd party).

  - I have set my sd to be default install (after installing most OPIE and GPE apps to root first). However I have one of those annoying SD cards that comes up with Input/Output error frequently if under usage (even mounted sync). I solved this by forcing a sync every 1 second when installing packages and hopefully will get another card one day. When I restart, the SD card is never automatically checked, and I can't unmount it as its always in use now (applets running etc...). Any proper way of getting round this? I've updated the insert scripts so when an SD/CF is inserted, it runs a filesystem check on it, then plays a 'sound' when its done.

Oh and finally, why gpe-bootsplash? I always just remove this because I like to see whats happening. Why cover up nice the really nice main splash screen with the whiteout splash of GPE (though I now see that the boot messages come up through it, which is an improvement).

EDIT: Excuse typos. I've just had a daughter and am very sleep deprived (and hence why I have the time to reflash ;-)

 - Bundabrg

Zaurus - pdaXrom / Z Freeze When Unsuspend And Resume
« on: December 20, 2005, 08:55:35 pm »
Ok, I'd like to check with anyone who is running kopi. I'm running the one that was posted in This thread.

Does your Z lock up if you suspend, then quickly resume again straight away (IE, within about 5 seconds).?

If I close everything but kopi (and its a kopi with events and alarms in it, not a blank one), my Z does this. Does it every time. I just hit suspend button, wait for the screen to go black, then hit the button again... screen comes on, everything is locked up (can't move mouse, can't ctrl-alt-backspace).

If I open LOTS of other apps, but not kopi, then it works fine.

Interestingly, if I run kopi, suspend, then wait at least 60 seconds, then resume, its ok.

This behaviour occurs under both matchbox (openbox) and xfce4

I have a C860 running RC12
End Edit

 - Bundabrg

Zaurus - pdaXrom / An Idea
« on: December 09, 2005, 10:01:36 am »
Just wanted to put this down before I forget... Its niggling me in the back of the head and perhaps it might spark something off for someone else. I'll work on it a bit after I've slept on it.

We've (and by we've, I mean all except 6000 users :-P) gotten apmsleep going and thus the Z should be able to wake when needed. So far only kopi alarms are used as described in another thread.

I was toying with my Z and lamanting a bit how useless really a wireless card + email is on it, since using wireless I get at most 1.5 hours of use out of it. Its simply not possible to walk around the office and have the Z beep me when an email comes in. In fact, apart from updating the Z, I find wireless to be almost totally useless as when I use it I can feel the time ticking away.

Thats when I wondered that maybe there is a way to do it. What would happen is to have the Z suspend for say 5 mintutes, wake up... check emails (say with screen off to further preserve battery), and if nothing, suspend straight away again. This way you leave the wireless CF card in it, and as long as you're near your wireless net, it will act similar to a blackberry.

It would be relatively simply to have a script in wakeup.d that checks if OMPI is open, and if so, give a 5 minute timeout. Then have a script in resume.d that detects this particular event and triggers OMPI (or whatever) to check mail and force a quicker suspend if no event.

On a similar note, I'm proposing a slight change to the wakeup.d scripts, such that they can return a time AND a paramter (say 'kopi' if the kopi event is triggered), such that when a resume script is run it knows which wakeup even got triggered. I hope that makes sense. This means that if kopi was triggered, then a resume script can check to see if KOPI is even loaded, and if not, to also load it up (and thus trigger the alarm). Working this into the plan above, you'd have the 5 minute script pass a parameter of 'mail', and have a resume script detect this parameter and perform the mail check.

Just an idea. I'm thinking this way you get to keep the battery life, be able to have a mobile tool that can check for stuff like emails etc... Maybe there could be other users for peridic wakeup checks?

 - Bundabrg

Zaurus - pdaXrom / Feeds Feeds All Over The Place
« on: December 09, 2005, 05:12:10 am »
Ok, I've updated my Z to RC12. After hunting over all the groups for the new kdepim (Really REALLY good compile btw!), the patched apmsleep, the new this and the new that, its really difficult for someone to easily add packages to their Z.   In fact, upgrading from RC9 to RC12 was particularly painful simply because I spent so much time looking for the custom packages.

The ones in the stock unstable feed are quite old or have duplicates or simply fail with the latest RC.

Is there any reason that People don't upload their new packages to the pdaXrom unstable feed? Is the upload and updating part of it still working?

I think we really need a single site where anyone can upload a package, versioning is taken care of, and the feed is automatically generated from those files. Perhaps even have it so 'debian style' people can 'own' a package and be responsible for maintaining its version, and if someone doesn't update it for ages, someone else can take it over.

I also feel that the above could be improved, also 'debian style', in that the pristine source + diff-to-make-it-work-under-pdaxrom can be attached such that one can download either the binary ipkg or the .tgz file containing the source.

Your comments please,
 - Bundabrg

PS - I would have no problems coding something above if that is what is needed, but I do not have the bandwidth to host such a site, though I could naturally put up a proof of concept site.

Zaurus - pdaXrom / What Feeds Are Out There?
« on: August 29, 2005, 07:30:27 am »
Ok, this is a call to everyone who has their own feeds, and who have posted links to their feeds in other threads to put it down here. I keep coming across messages that have links to these really good feeds, and keep forgetting them.

The ones I have on my Z is as follows: -  - rgrep
 - burgerspace - This is a clone of the classic game "BurgerTime".  In it, you play the
 part of a chef who must create burgers by stepping repeatedly on the
 ingredients until they fall into place.  And to make things more
 complicated, you also must avoid evil animate food items while performing
 this task, with nothing but your trusty pepper shaker to protect you.

 - dosfstools - Utilities to create and check MS-DOS FAT filesystems
 Inside of this package there are two utilities to create and to
 check MS-DOS FAT filesystems on either harddisks or floppies under
 Linux.  This version uses the enhanced boot sector/superblock
 format of DOS 3.3+ as well as provides a default dummy boot sector

 - drsync - Two-way remote file synchronisation uses rsync to synchronise between two directories
 (local or remote), but stores state information for files,
 so that it can be used in both directions, and can
 cope with files created, modified or deleted in either

 - e2fsprogs - The EXT2/EXT3 file system utilities.
 EXT2 stands for "Extended Filesystem", version 2. It's the main
 filesystem type used for hard disks on Debian and other Linux systems.
 This package contains programs for creating, checking, and maintaining EXT2
 and EXT3 filesystems, and the generic `fsck' wrapper.

 - fdisk - Description: Disk partition table manipulation utilities
   fdisk  - Partition table manipulator
   cfdisk - Curses based disk partition table manipulator

 - flite - A small run-time speech synthesis engine
 Flite is a small fast run-time speech synthesis engine.  It is the
 latest addition to the suite of free software synthesis tools
 including University of Edinburgh's Festival Speech Synthesis System
 and Carnegie Mellon University's FestVox project, tools, scripts and
 documentation for building synthetic voices.  However, flite itself
 does not require either of these systems to run.

 - gnupg - GNU privacy guard - a free PGP replacement
 GnuPG is GNU's tool for secure communication and data storage.
 It can be used to encrypt data and to create digital signatures.
 It includes an advanced key management facility and is compliant
 with the proposed OpenPGP Internet standard as described in RFC2440.

 - kismet - Wireless 802.11b monitoring tool
 Kismet is a 802.11b wireless network sniffer.  It is capable of sniffing
 using almost any supported wireless card using the Airo, HostAP, Wlan-NG,
 and Orinoco (with a kernel patch) drivers.

 - msmtp - light SMTP client with support for server profiles
 msmtp is an SMTP client that can be used to send mails from Mutt, other
 MUAs (mail user agents), or the command-line. It forwards mails to an SMTP
 server (for example at your ISP or a free mail provider), which takes care
 of the final delivery.
 Using profiles, it can be easily configured to use different SMTP servers
 with different configurations, which makes it ideal for mobile clients.

 - mutt - Text-based mailreader supporting MIME, GPG, PGP and threading
 Mutt is a sophisticated text-based Mail User Agent. Some highlights:
  * MIME support (including RFC1522 encoding/decoding of 8-bit message
    headers and UTF-8 support).
  * PGP/MIME support (RFC 2015).
  * Advanced IMAP client supporting SSL encryption.
  * POP3 support.
  * Mailbox threading (both strict and non-strict).
  * Default keybindings are much like ELM.
  * Keybindings are configurable; Mush and PINE-like ones are provided as
  * Handles MMDF, MH and Maildir in addition to regular mbox format.
  * Messages may be (indefinitely) postponed.
  * Colour support.
  * Highly configurable through easy but powerful rc file.

 - offlineimap - IMAP/Maildir synchronization and reader support
 OfflineIMAP is a tool to simplify your e-mail reading.  With
 OfflineIMAP, you can:
  * Read the same mailbox from multiple computers, and have your
    changes (deletions, etc.) be automatically reflected on
    all computers
  * Use various mail clients to read a single mail box
  * Read mail while offline (on a laptop) and have all changes
    synchronized when you get connected again
  * Read IMAP mail with mail readers that do not support IMAP
  * Use SSL (secure connections) to read IMAP mail even if your reader
    doesn't support SSL
  * Synchronize your mail using a completely safe and fault-tolerant
    algorithm.  (At least I think it is!)
  * Customize which mailboxes to synchronize with regular expressions
    or lists.
  * Synchronize your mail two to four times faster than with other tools
    or other mail readers' internal IMAP support.
 In short, OfflineIMAP is a tool to let you read mail how YOU want to.

 - paketto - he Paketto Keiretsu is a collection of tools that use new and unusual
 strategies for manipulating TCP/IP networks.
 This package includes:
   * scanrand - a very fast port, host, and network trace scanner
   * minewt - a user space NAT/MAT (MAC Address Translation) gateway
   * lc (linkcat) - provides direct access to the network (Level 2)
   * paratrace - a "traceroute"-like tool using existing TCP connections
   * phentropy - plots a large data source onto a 3D matrix

 - putty-tools - command-line tools for SSH, SCP, and SFTP

 - putty - Telnet/SSH client for X

 - rsync - fast remote file copy program (like rcp)

Zaurus - pdaXrom / Matchbox Applets Disappearing
« on: December 30, 2004, 04:06:39 am »
Since RC8 I've noticed a bug where the applets for matchbox die and disappear when changing screen resolution. This occurs when running xrand -s 0 and xrandr -s 1.

The only workaround Ive found is to do the following: -
Code: [Select]
touch /mnt/.mb-restart
killall matchbox-panel

I was going to wrap xrandr to do this but Im sure there is a better way since the panel takes a while to restart.

Does anyone have any suggestions?

Zaurus - pdaXrom / Rc8 - Personal Updates
« on: December 30, 2004, 03:58:24 am »
Ok, every version of a rom I put on I tend to put in changes that I feel make things slightly more comfortable for me. In case anyone else would find them useful I will be putting them into ipks and putting them in my cookpot feed directory.

The feed URL is:

Currently I have the following there:

  apmwrapper - Creates directories suspend.d, resume.d and scripts.d under /etc/apm. Then wraps apm so that files in suspend.d and resume.d are executed when the device enters each state. Detects if apm is already wrapped (as it is under rc8) and backs up the original wrapper. Will also work with an unwrapped apm.

  chkhinge-scripts - Creates directories closed.d, landscape.d, portrait.d and scripts.d under /etc/sysconfig/clamshell. Then backs up the existing shell scripts in that dir, links them into the new directory structure and creates new shell scripts to call the files in each dir when the device changes into closed, lanscape or portrait. I got the idea from the pdaxrom bugs page.

  hotfix-pdaxrom - My personal fixes to problems as I see them. Currently creates a cron.hourly job that sets the "hardware" clock to minimize timeloss on a crash; adds scripts to /etc/apm directories to unmount all smbfs mounts before a suspend and to set the "hardware" clock on both suspend and resume to minimize time loss on crash

All of the above should install and uninstall cleanly.

 - Bundabrg

Zaurus - pdaXrom / Timidity
« on: December 28, 2004, 05:25:03 am »
I thought I'd try out Timidity as its in the feed for RC8.

However, playing ANY midi file on my C860, even when overclocked, just stutters or is quite choppy.

I've also tried dropping from X and doing it straight from the command line. Also tried outputting in Mono, 8 bit etc... to no avail.

Is there anything I can do to get this going ok? The only thing I've come up with that may work is to convert my midis to wav using timidity and then play them. I think its the 'on-the-fly' conversion that is causing the problems.

 - Bundabrg

Angstrom & OpenZaurus / C7x0 C8x0 Series And Time Issue
« on: December 09, 2004, 01:11:23 am »
Ok, this was the first thing I ever saw when I first installed OZ on my pda. The fact that the date was 1970.

This is because the chipset simply has no hardware clock. However there is a 'kinda' fix that is quite easy to install into OZ.

First, install the 'slutils' ipk from the feed (might be called sltools, can't remember). This installs 'sltime' into /usr/bin.

Now, the way sltime works is as follows:-
  - If you run 'sltime -set' then the current time is stored somewhere on the flash (I havn't worked out where yet actually ;-).
  - If you run 'sltime' then the time that was stored in flash is set to the current clock.

So, I did the following: -
  1. Edited /etc/init.d/ so that it also runs 'sltime -set' when a 'START' even occurs, and 'sltime' when a STOP event occurs.
  2. Symlinked to /etc/rcS.d/S90hwclock
  3. Symlinked to /etc/rc0.d/K10hwclock

I didn't do the following, but would recommend:
  1. Add a cron job that executes 'sltime -set' every 30 minutes.
  2. AND/OR executes 'sltime -set' each time the unit is unsuspended/suspended

 - Bundabrg

Cxx0 General discussions / Info: Charging and Ghosting
« on: November 13, 2004, 01:22:37 am »
Hi All,

I've had a hectic week with my Z and I thought I'd post what happened and how I fixed it. A lot of info I got from this group so it really is a good repositry of information.

Anyway, for some reason my 'Digicom Universal Charger' 5V 1.0Amp decided to quit it and didn't charge my Z. I didn't notice till the battery actually went totally flat. After paying $50AUD on my charger I was a bit annoyed that it decided to quit, but apparently the eletronics shop won't replace a charger (Which I guess I can understand). I bought another one, same V same Amp.

Now I accidently reversed the polarity and my Z didn't start charging. After quickly realising my mistake (with heart in my throat and sweaty palms now), I switched the polarity so that the 'Center' is positive and the 'Outside' is negative.

Now my Z charged for maybe 2 minues, then the charge light started flashing on and off slowly. It certainly didn't charge enough to even start. I'm not sure even now if this was caused by the reversed polarity or the fact that it totally flattened.

Anyway,  I suppose I should mention that my battery is an EA-BL08, that is supposed to charge to 4.2V apparently. Measuring between + and - with a multimeter showed a voltage of about 2.2V.

Now I can of course boot up fine with  'D+B', logging in as root and issueing a 'reboot' with the power plugged in.

I plugged it into the power and brought up the diagnostic screen with 'D+M'. Went to page 3, EXTRAS, 'Normal Diag Mode' and hit 'Clear Adjust Values', which blanked out 'Tablet' 'COM' and 'PHASE' on the main screen. This did not help (and in fact I think this has nothing to do with the battery charging).

Then went to Page 2, Batt Voltage Adjust, 'Battery Voltage Check'. It showed the following: -
Code: [Select]
Main Bat AD: 113 (2.2V)

Flash Data: ----
Seemed that the unit didn't know how much to charge the battery to. So I pulled the battery and connected the + terminal from the charger to the + on the battery and the - from the charger to the - on the charger and charged it manually, as per

Aussies HOWTO

When it hit 4.2V, I put it into the Zaurus, did D+M, page 2, Batt Voltage Adjust, 'Battery Voltage Adj' and hit 'S' to flash in the current voltage. Now a check shows the following: -
Code: [Select]
Main Bat AD:  208 (2.6V)

Flash Data:  213
   delta:  +439

ADJUST AD:  208->  647
                 :  (4.1V)

And everything works fine. Phew.

However the 'Clear Adjust Values' step came back to haunt me when I booted into pdaXrom. I had a major ghosting effect, mainly seen down near the task bar. Also I had screen flicker. And now this is important, and probably also why some Z users see screen flicker in pdaXrom and others don't.

Went to D+M. Of course 'Tablet', 'COM' and 'Phase' are still '---'. So I went into Page 1, 'COM ADJ Setting', and set it to '114' which resulted in the image not flickering at all!. Then went into Page 1 'LCD Phase setting', and set it to '8' so I didn't have ghosting.  No idea how I set 'Tablet', probably 'Touch Pane (VGA)', and its now currently 0.

Booted back into pdaXrom, and voila, no ghosting, no flickering.

My story. Hope it helps anyone in a similar situation.

I can't remember all the links to the posts that helped me, but I googled using both the terms 'Zaurus not charging' and 'Zaurus won't charge'.

 - Bundabrg

Cxx0 General discussions / sltime - Date loss issue
« on: September 24, 2004, 05:04:15 am »
Hi All,

Running OZ3.5.1, C860. (Gotta love the Zaurus, most flashed tool I own now ;-)

I'm trying to work out exactly what 'sltime' from 'slutils' actually _does_. This filename simply does not come up with ANYTHING relevant on google (apart from changelogs).

I suspect it has something to do with storing the date between a hard reset, something the PXA-255 chipset is apparently incapable of doing (though running under linux one would think that a hard-reset would be rare). I'm assuming this is a general problem with StrongARM in that RTC is reset on any hard-reset?

My questions are: -
  1. What is sltime?
  2. What does it do when you issue a --set and a --clear

I havn't been able to find any source for it, and performing a strings on it shows that it is possibly writing to NAND.

Under pdaXrom, I'm assuming it was used to store the time. The one bug under pdaXrom is that it kept resetting it to a funny time (I suspect it was setting it back to GMT, and then using the time as if it was local time).

Under OpenZaurus, which does not use it, the date is reset to the beginning of the epoch, 1/1/1970, and of course opie complains bitterly.

 - BRG

Zaurus - pdaXrom / [RC3]: Misc Questions
« on: September 13, 2004, 01:56:49 am »
Hi All,

Just have some misc queries. My apologies if they are a FAQ or located somewhere, but with extensive googling I've been unable to find an answer to them yet.

I have a C860, running pdaXrom Katherin RC3
90Mb Root partition, rest user
1Gb SD Card mounted /mnt/card
Till my wireless CF card arrives, I'm using the usb cable through my notebook (Debian Sid) running NAT iptables.

1. I notice that the silkscreen buttons are usable in RC3. How do I remap them to other commands?

2. I'm not sure if this is a problem with the ROM or something up with the USB network connection between the C860 and my notebook (Debian Sid). When I try to use ipkg (or even just wget) to get some ipk files (from the, when its uncompressing the file, I get the following error:-
Code: [Select]
tar: Skipping to next header

gzip: stdin: invalid compressed data--crc error

gzip: stdin: invalid compressed data--length error
tar: Child returned status 1
tar: Error exit delayed from previous errors

If I wget the same file on my laptop, and scp it to the C860, it installs/untars fine. Performing a 'diff' of the two files shows that they are different (though both have the same size).
I know that pdaXrom has an older ipkg and that some ipk are 'ar' files. The files I'm testing are definately tgz. Just so you know I've symlinked /home/tmp to /mnt/card/tmp so its got the whole 1Gb of SD avail for use (and I've tried the same thing with a 512Mb CF I've got here as well). My df  as well is:-
Code: [Select]
# df
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/mtdblock/2          92160     48016     44144  52% /
none                     12288         0     12288   0% /dev/shm
/dev/mtdblock/3          31744      1952     29792   6% /home
/dev/mmcd/disc0/part1   987720      1212    936336   0% /mnt/card

3. Is it worth upgrading ipkg to the newer one? If so, how? (This one I've been unable to find anywhere, just hints thats its possible by downgrading

4. How do I access the F1-F10 keys.

5. Matchbox seems to allow right-clicks by simply holding a click on an item (like the old single button macs). However, this delay is sometimes really short (especially when using Xstroke as it cuts the letters in half). How do I change this delay?

Things I've noticed
a. RC3 definately has a slight screen flicker. It can be hard to see sometimes but at othertimes its quite noticable. (This has been reported many times. I'm just adding that I've seen it as well).

b. Sometimes auto-rotate doesn't work (Need to click it into the portrait/landscape mode twice for it to recognize the change).

c. Performing a 'dmesg' gives LOTS and LOTS of the following line: -
Code: [Select]
-W- Don't delete.
If I scroll back, the last lines from dmesg that are not like this are: -

Code: [Select]
devfs_register(part1): could not append to parent, err: -17
w100fb set 640x480 (VGA 90 degrees)

d. When the screen blanks AND the pda is plugged into power, I can hear a high pitched noise, similar to the noise you hear if you put your monitor onto a frequency that is too high.

Final Word
Ok thats everything I can think of. Thanks to those who have helped so far and to those who have put all the work into these interesting devices. Its quite nifty to see my tetrinetx server run on a palm sized device .  


Pages: [1] 2