Anyone have success overclocking their 5600?

[Hybrid]

Ive tried it usin both the official sharp rom, and zynergy5600... I can update the kernel ok, but I cant for the life of me get the qclockchange app to install.

whenever I open it, the package manage doesnt display it as something availible to be installed.

anyone know whats going on? (or is there any other way I can adjust the clock speed?)

[dz]

try running it from the command prompt and seeing what it says it cant find

[tapjpa]

I have installed on the sharp rom no prob\'s, try redownloading?

[tumnus]

This ipk works fine:
http://www.piro.hopto.org/~piro/zaurus/qcl...ge_0.1a_arm.ipk

You need the Special kernel though, like the one available in the 5600 patches section of the ZUG downloads.

In the end all QClockchange does is read and write the CCCR register from /proc/cccr_register. Look at ced\'s howto for the values to write:

http://www.zaurususergroup.com/modules.php...0%28by%20Ced%29

 If you cannot see /proc/cccr_register then you aren\'t using a kernel that gives you the overclock abilities.

[orthogonal]

Ive tried it usin both the official sharp rom, and zynergy5600... I can update the kernel ok, but I cant for the life of me get the qclockchange app to install.

whenever I open it, the package manage doesnt display it as something available to be installed.

anyone know whats going on? (or is there any other way I can adjust the clock speed?)

It\'ll install on anything, but it only runs on kernels that accommodate it.

The.ipk is not gziped, so Add/Remove programs won\'t show it -- to fix this, just gzip it:

# gzip qclockchange_0.1a_arm.ipk
# mv qclockchange_0.1a_arm.ipk.gz qclockchange_0.1a_arm.ipk

Then run AddRemovePrograms (or just install from the prompt, and restart qtopia).

At this point, if you don\'t have a kernel that works with it, it will do nothing when you run it -- it won\'t even emit any error messages, it will just exit after a second or two.

[orthogonal]

This ipk works fine:
http://www.piro.hopto.org/~piro/zaurus/qcl...ge_0.1a_arm.ipk

You need the Special kernel though, like the one available in the 5600 patches section of the ZUG downloads.

In the end all QClockchange does is read and write the CCCR register from /proc/cccr_register. Look at ced\'s howto for the values to write:

http://www.zaurususergroup.com/modules.php...0%28by%20Ced%29

 If you cannot see /proc/cccr_register then you aren\'t using a kernel that gives you the overclock abilities.

The qclockchage app will display the current values, but any changes are silently discarded, I presume because /proc/cccr_register isn\'t writable by user zaurus.

Running qclockchange as root is problematic for the usual reasons: it complains the \"Qt?Embedded data directory is not owned by user 0\". I suspect this can be \"fixed\" the usual way,  by chowning the right file:
#chown root:qpe /tmp/qtembedded-zaurus
but of course the next app to run from the gui will fail and complain that the owner should be zaurus and you\'ll have to change it back.

Easier is just changing the value in /proc/cccr_register as shown in the post tumnus references:

#echo $value ] /proc/cccr_register.

See that post for appropriate values.

I don\'t frankly see much of a difference at the higher clock speed.

prboom just started ignoring input (but is still updating the screen, and I can still ssh into the zaurus and kill it an d qpe to get the input back).

But on re-running it, prboom is working ok. May have been having opera open at the same time.

qt-reader is always a bit slow on page-ups, but I think that it\'s io bound, reading from the sd card, although it gets slower while playing xmms, even if xmms is reading from the cf wifi rather than the sd card.

playing a java game (ZTailGunner) while playing internet radio on xmms is somewhat faster -- performance was noticeably degraded at the standard clock speed, but was only a bit degraded when overclocked to 472.

On balance, I\'m not seeing a great deal of difference with the higher clock speed.

It should be noted I\'m using the version 1.3 special rom with the chip defect workaround turned off, which is presumably already providing a boost in speed.

Anyone else have any subjective impressions of overclocking?

[Greg2]

The qclockchage app will display the current values, but any changes are silently discarded, I presume because /proc/cccr_register isn\'t writable by user zaurus.

With the sharp v1.32 rom or the zynergy v1.1 rom and the special kernel v1.3 you must hold icon for Qclockchange until it opens to details and settings, then check the execute with root privilege box.

Greg