Help - Search - Members - Calendar
Full Version: Overclocking Beta3...
OESF Forums > Distros, Development, and Model Specific Forums > Distro Support and Discussion > pdaXrom
neo_com_3
I do not want to break your balls but even after I search, I cannot find how to over clock my Z 3200 using beta3. I found on a post somewhere here, that I can use the "set" command, but it is not working for me - it does not give me the option for clock...

Can someone explain what do I have to do, and is there any ipk that I need?

Tnx...
daniel3000
AFAIK it is just a matter of writing some numerical value into some "file" in the /proc file system.
But I don't know any details...
InSearchOf
From what I heard... since the 3200 has a different CPU, the stablity after overclocking is horrid!...

But try for yourself... if I had my Z with my I would tell you the value to change... But it doesnt work form the CPU Config utility?

Late
zi99y
I use the following aliases on my C3200:

# set cpu clock speed
# "104", "208", "312", "416", "520", "624"
alias cpu1="echo '2000204' > /proc/zaurus/CCCR; echo '04' > /proc/zaurus/VCORE"
alias cpu2="echo '2000206' > /proc/zaurus/CCCR; echo '06' > /proc/zaurus/VCORE"
alias cpu3="echo '2000208' > /proc/zaurus/CCCR; echo '08' > /proc/zaurus/VCORE"
alias cpu4="echo '2000210' > /proc/zaurus/CCCR; echo '0a' > /proc/zaurus/VCORE"
alias cpu5="echo '2000214' > /proc/zaurus/CCCR; echo '0c' > /proc/zaurus/VCORE"
alias cpu6="echo '2000218' > /proc/zaurus/CCCR; echo '0e' > /proc/zaurus/VCORE"
alias cpumin="echo '2000204' > /proc/zaurus/CCCR; echo '04' > /proc/zaurus/VCORE"
alias cpunormal="echo '2000210' > /proc/zaurus/CCCR; echo '0a' > /proc/zaurus/VCORE"
alias cpumax="echo '2000218' > /proc/zaurus/CCCR; echo '0e' > /proc/zaurus/VCORE"

I've not done too much experimenting, but it did lockup once on the 620Mhz setting. I have switched to 520Mhz a fair bit and it works fine, the speed difference is very noticeable.

Credit for this goes elsewhere, I just use it as the python script doesn't work for me.
desertrat
QUOTE(zi99y @ Nov 2 2006, 08:23 PM)
Credit for this goes elsewhere

That's me smile.gif

QUOTE
I just use it as the python script doesn't work for me.

I believe the script does some sanity checks to see what machine/cpu is in use and maybe it hasn't been updated for the C3200.
neo_com_3
Tnx m8s...

@zi99y:This might sound wierd, but where shall I type all the above lines? In a terminal or in a file?

Tnx...
zi99y
either actually, I have a file in my home directory called .alias which is sourced from the bash profile file - sorry that's probably too much info. Go here for a quick explaination of aliases.

Basically you could paste the block into the terminal and then type the commands cpu3 cpu4 etc. to change the cpu clocking, but it's easier to have them load automatically - there's tons of bash help out there if you want to do it that way, but let me know if you have trouble.
neo_com_3
QUOTE(zi99y @ Nov 4 2006, 12:16 PM)
either actually, I have a file in my home directory called .alias which is sourced from the bash profile file - sorry that's probably too much info. Go here for a quick explaination of aliases.

Basically you could paste the block into the  terminal and then type the commands cpu3 cpu4 etc. to change the cpu clocking, but it's easier to have them load automatically - there's tons of bash help out there if you want to do it that way, but let me know if you have trouble.
*

Tnx m8...

I got it...

I would like to set my speed to 520 all the time. Can I do it or do I risk to burn my cpu?
Tnx for all...
neo_com_3
Hi there again...

Well It is working faster in 520, but I want to know if I can have it working there all the time. I do not care about power consuming, I do not want to "burn" my Z...

By accident i typed 200210 instead of 2000210 and the screen stared to flashing. I reboot and everything was ok. Once I change te speed to 624 and Z's screen turned white, so I reset it. Do you think that I did any damage on the cpu? Now I have it on 520...

After hardware reset, is the speed going to 416 by default?

Tnx, I really app your answers...
zi99y
No one here will tell you "Yes it's 100% fine" because you don't get guaruntees with overclocking.

But experience tells us that it is not fatal if the cpu crashes while overclocking, I've never seen any posts about people frying their Z on this forum, but you could do a few searches to see. It stands to reason if it starts to crash regularly due to the cpu overheating then it will eventually damage it.

The white screen you mentioned happened to me also and I reset and it was fine, I just don't clock that high anymore.

Is there any way to check the cpu temperature? If so it may give an idea if you're in the danger zone or not, and useful to monitor.

I personally don't bother overclocking unless there's something I really want it faster for, battery life is more important to me.
daniel3000
I even thought about an underclocking mechanism in case you close the screen.
pdaXrom by default does not suspend the Z but only switches off the screen, which is quite nice because if you open it you don't have to wait for the resume proces (which can take quite a lot of time of many applicatoins are open) but you can simply comtinue to work.
In order to save even more battery power while the screen is closed it would be nice to clock down the CPU to minimum speed.

However, I have seen more crashes of the Z when underclocking than when overclocking, so I hesitate to put the underclocking commands into the clamshell/close rc scripts.

Has anyone done this already with success?

And another questoin: Is there a command to halt the CPU entirely, but without suspending?

daniel
zi99y
interesting idea, does the microdrive "park" itself somehow to protect it when suspended? I would be nervous having it on the whole time.

as for halting the cpu, I don't think you would be able to execute a command to change the clock speed again afterwards!
daniel3000
QUOTE(zi99y @ Nov 7 2006, 06:28 PM)
interesting idea, does the microdrive "park" itself somehow to protect it when suspended? I would be nervous having it on the whole time.


well, it parks if it is unused and spins down. It should be unused during the lid is closed, but of course, especially in the first seconds after closing, it might still be active. So in order to protect the MD it would be better to somehow actively deactivate it (cardctl eject / insert?)
I suspect this might liead to problems with swap partitions and mounted file systems / open files.
Good point.
I will consider exchanging the MD with a flash card.
OTOH: How many people use their Zaurus as an MP3 player carrying it around in a pocket with active MD? ...

QUOTE
as for halting the cpu, I don't think you would be able to execute a command to change the clock speed again afterwards!
*



oops. Of course. rolleyes.gif
So it had to be trigger form outside hardware interrupt?).
I don't know at all if something like that is possible on the Zaurus.

daniel
Lemuus
this is strange,
when i overclock my zaurus (3200), at 614, with the python script, works very well, stable, i had it overclocked for a few hours and works perfect. But if i do the same thing with the alias above, my zaurus freeze almost immediately. i searched the script, but didn`t found anything diferent in the way it change the cpu frecuency...
i think i missed something...
Daniel.
klatt
Here is a modified version of cpuoverclock.py that works with the 3200. All I had to do was change one line smile.gif. If you really wanted to get lazy all you had to do was change 3100 to 3200 in this one spot.

I'll still probably use the aliases a lot because those are quick and more easily scriptable, but it's nice to have the GUI util also.

Enjoy.

Frank
daniel3000
QUOTE(klatt @ Nov 9 2006, 02:46 AM)
Here is a modified version of cpuoverclock.py that works with the 3200.  All I had to do was change one line smile.gif.  If you really wanted to get lazy all you had to do was change 3100 to 3200 in this one spot.

I'll still probably use the aliases a lot because those are quick and more easily scriptable, but it's nice to have the GUI util also.

Enjoy.

Frank
*



hmmm - don't understand.
Lemuus said that the py script wrks well on his 3200, but the aliases don't.
So for what reason did you fix the py script?
Any solution for the aliases?

Thanks
daniel
klatt
QUOTE(daniel3000 @ Nov 9 2006, 05:31 AM)
QUOTE(klatt @ Nov 9 2006, 02:46 AM)
Here is a modified version of cpuoverclock.py that works with the 3200.  All I had to do was change one line smile.gif.  If you really wanted to get lazy all you had to do was change 3100 to 3200 in this one spot.

I'll still probably use the aliases a lot because those are quick and more easily scriptable, but it's nice to have the GUI util also.

Enjoy.

Frank
*



hmmm - don't understand.
Lemuus said that the py script wrks well on his 3200, but the aliases don't.
So for what reason did you fix the py script?
Any solution for the aliases?

Thanks
daniel
*




Hmm I'm not sure, maybe he modified his?

I have never been able to get it working in many installs of pdaxrom. The reason for this was that it checks for a 1000, 3100, or a 3000 but completely leaves out the 3200. I just added the 3200 in the statement that assigns the values to set and it worked perfectly.

The aliases also work for me so I'm not sure how to "fix" those.

Frank
desertrat
QUOTE(daniel3000 @ Nov 9 2006, 09:31 AM)
Lemuus said that the py script wrks well on his 3200, but the aliases don't.

Maybe the python script fails silently - ie under C3200 it does nothing because it's not a recognised model - and Lemuus assumed that it worked?

QUOTE
Any solution for the aliases?

The aliases does exactly what the python script does (the values were copied from there), but without the gui overhead.
daniel3000
QUOTE(desertrat @ Nov 9 2006, 04:52 PM)
QUOTE(daniel3000 @ Nov 9 2006, 09:31 AM)
Lemuus said that the py script wrks well on his 3200, but the aliases don't.

Maybe the python script fails silently - ie under C3200 it does nothing because it's not a recognised model - and Lemuus assumed that it worked?



hehe biggrin.gif fake overclock mode?

QUOTE
QUOTE
Any solution for the aliases?

The aliases does exactly what the python script does (the values were copied from there), but without the gui overhead.
*



May it be a timing issue? Each alias writes into two proc entries. Can the time difference between writing into one and the other make the difference? The py script may be slower in that than the shellscript.

daniel
Lemuus
i's not a fake overclock mode, i had already changed the script, so it really overclock the zaurus.

QUOTE
May it be a timing issue? Each alias writes into two proc entries. Can the time difference between writing into one and the other make the difference? The py script may be slower in that than the shellscript.

daniel


Maybe... i will make a script to make a pause between the two proc entries
neo_com_3
Well...

If I reboot my Z 3200, it is going to go to 416 by default, right?

Is there any way to check the speed of my cpu?

Tnx...
klatt
QUOTE(neo_com_3 @ Nov 10 2006, 10:30 AM)
Well...

If I reboot my Z 3200, it is going to go to 416 by default, right?

Is there any way to check the speed of my cpu?

Tnx...
*



Yup it will go back. And I suppose you could read the values from where cpuoverclock.py and the aliases write to and interpret them back into the clock speed.

What I was wondering last night was: After a suspend does the clock speed get reset? I guess an easy way to test would be to lower it to something ridiculous like 100 MHZ so you can definitely tell the difference and suspend it and bring it out of suspend. Then you can see if it still acts ridiculously slow.

Frank
Lemuus
CODE
# set cpu clock speed
# "104", "208", "312", "416", "520", "624"
alias cpu1="echo '2000204' > /proc/zaurus/CCCR;sleep 10; echo '04' > /proc/zaurus/VCORE; echo '104'"
alias cpu2="echo '2000206' > /proc/zaurus/CCCR;sleep 10; echo '06' > /proc/zaurus/VCORE; echo '208'"
alias cpu3="echo '2000208' > /proc/zaurus/CCCR;sleep 10; echo '08' > /proc/zaurus/VCORE; echo '312'"
alias cpu4="echo '2000210' > /proc/zaurus/CCCR;sleep 10; echo '0a' > /proc/zaurus/VCORE; echo '416'"
alias cpu5="echo '2000214' > /proc/zaurus/CCCR;sleep 10; echo '0c' > /proc/zaurus/VCORE; echo '520'"
alias cpu6="echo '2000218' > /proc/zaurus/CCCR;sleep 10; echo '0e' > /proc/zaurus/VCORE; echo '624'"
alias cpumin="echo '2000204' > /proc/zaurus/CCCR;sleep 10; echo '04' > /proc/zaurus/VCORE; echo '104'"
alias cpunormal="echo '2000210' > /proc/zaurus/CCCR;sleep 10; echo '0a' > /proc/zaurus/VCORE; echo '416'"
alias cpumax="echo '2000218' > /proc/zaurus/CCCR;sleep 10; echo '0e' > /proc/zaurus/VCORE; echo '624'"


No problems now..., i don't understand why the delay between writes in the proc entries works..... but works!!
Daniel.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2015 Invision Power Services, Inc.