I'll check that out, since my pandora stopped booting (after a hard crash), I had to reflash and got struck with the "Please select date..., Please select date..., Please select date..." bug so I'll flash with the latest image, to get rid of this problem. At least until the final HotFix 4 comes aroundJdbye said:I noticed a max OPP setting has been added to the GIT, I think that's also been added to the latest ubifs image/rootfs at http://openpandora.org/firmware/images/ (they were modified on the same date) - meaning overvolting if you have the latest rootfs is as simple as echo 5 > /proc/pandora/cpu_opp_max
Strictly speaking, you don't, which is why OPT has discouraged changing the voltage. I suspect allowing custom voltages will not be making it into the official firmware. If a processor does burn out, it is just an (exceptionally challenging) exercise in soldering to get the firmware off the NAND and they can determine whether you installed a custom firmware that allows custom voltage or not.Blue Ion said:
Really? So far from what I've heard all could do 800.Blue Ion said:
Well the kernel image is updated at least, I'm happily overvolting to OPP4 at 925Mhz right now using http://openpandora.org/firmware/ima...c890d6b47ac7959354cdf34-r21-omap3-pandora.binBlue Ion said:
Having to use echo 5 > /proc/pandora/cpu_opp_max every time I want to overvolt can get annoying but at least then I have more control over which OPP level it uses at say, 925Mhz. I don't think it will run fullspeed even at 1Ghz, maybe at 1.1Ghz. 
Blue Ion said:
When I compiled the kernel myself, wifi didn't work, but when I used the precompiled kernel in openpandora.org/firmware built from the same source it did, so I think it might have more to do with the way it's compiled than the differences in the code - of course, I might be wrong, but at least I had great success with using the prebuilt aug 22th kernel with the aug 15th rootfs and modules - older versions of the rootfs might not work so well with the latest kernel.urjaman said:
Actually, that was the problem. I forgot to flash the uImage as well that was why I wasn't getting the cpu_opp_max and the 3d acceleration problem, my uImage came from the Hotfix 3 which is older. I guess mixing uImage and rootfs would work as long as there aren't any showstopping mismatchs, like in my case the video driver.urjaman said:
Ah, I didn't realize they were separate, that makes sense.Blue Ion said:
#!/bin/bash
#get value range
minmhz=14
safemhz=600
maxmhz=1000
curmhz="$(cat /proc/pandora/cpu_mhz_max)"
newmhz="$(cat /proc/pandora/cpu_mhz_max)"
curopp="$(cat /proc/pandora/cpu_opp_max)"
newopp="$(cat /proc/pandora/cpu_opp_max)"
#at what mhz should it change the voltage?
opp2mhz=125
opp3mhz=250
opp4mhz=800
opp5mhz=900
device=/proc/pandora/cpu_mhz_max
oppdevice=/proc/pandora/cpu_opp_max
if [ ! $1 ]; then
if [ $DISPLAY ]; then
newmhz=$(zenity --scale --text "Set CPU clockspeed" --min-value=$minmhz --max-value=$maxmhz --value=$curmhz --step 1)
else
newmhz=$(read -p "Please enter the desired clockspeed")
fi
else
newmhz=$1
fi
if [ $newmhz ]; then
if [ $newmhz -gt $opp2mhz ]; then
if [ $newmhz -gt $opp3mhz ]; then
if [ $newmhz -gt $opp4mhz ]; then
if [ $newmhz -gt $opp5mhz ]; then
newopp=5
else
newopp=4
fi
else
newopp=3
fi
else
newopp=2
fi
else
newopp=1
fi
if [ $newmhz -gt $safemhz ]; then
if [ $DISPLAY ]; then
answer=$(zenity --question --title "alert" --text "You are trying to set the CPU clock to $newmhz which is above its specification of $safemhz, doing so may burn down your house, sour milk, or just blow up (OK, not that likely)! Proceed?";echo $?)
echo $answer
if [ $answer = 1 ]; then exit 1; fi
else
answer="n";read -p "You are trying to set the CPU clock to $newmhz which is above its specification of $safemhz, doing so may burn down your house, sour milk, or just blow up (OK, not that likely)! Proceed? [y/n]" -t 10 answer
echo $answer
if [ $answer = n ]; then exit 1; fi
fi
fi
if [ $newopp -gt $curopp ]; then
if [ $newopp -gt 3 ]; then
if [ $DISPLAY ]; then
answer=$(zenity --question --title "alert" --text "You are trying to set the CPU clock to $newmhz, this will increase the CPU voltage from OPP${curopp} to OPP${newopp} and may shorten the life of your CPU. Proceed?";echo $?)
echo $answer
if [ $answer = 1 ]; then exit 1; fi
else
answer="n";read -p "You are trying to set the CPU clock to $newmhz, this will increase the CPU voltage from OPP${curopp} to OPP${newopp} and may shorten the life of your CPU. Proceed? [y/n]" -t 10 answer
echo $answer
if [ $answer = n ]; then exit 1; fi
fi
fi
fi
if [ $newopp -gt $curopp ]; then
echo $newopp > $oppdevice
echo cpu_opp_max set to $(cat /proc/pandora/cpu_opp_max)
else
if [ $newopp -lt $curopp ]; then
echo $newopp > $oppdevice
echo cpu_opp_max set to $(cat /proc/pandora/cpu_opp_max)
else
echo cpu_opp_max not changed (current setting: $(cat /proc/pandora/cpu_opp_max))
fi
fi
if [ $newmhz -le $minmhz ]; then newmhz=$minmhz; fi
if [ $newmhz -ge $maxmhz ]; then newmhz=$maxmhz; fi
echo $newmhz > $device
echo cpu_mhz_max set to $(cat /proc/pandora/cpu_mhz_max)
fisudo cp /path/to/modified/op_cpuspeed.sh /usr/pandora/scripts
That's great.Jdbye said:
, while at the other side, run 500 mhz at opp2 or even opp1.I made it 800 because psx4all crashes at 850 at OPP3 for me where other apps are stable, I don't think anyone can reach 1Ghz at OPP4, not the OPP4 that is defined in the kernel at least (54 vsel). I don't know anything about what kind of speeds you can run stable at OPP2 or OPP1 so I didn't include those voltages at all.Blue Ion said:That's great.Jdbye said:
Perhaps you could make the opp changing limits more edition friendly and allow undervolt as well.
Like 4 variables that are the limits of speed between voltages.
I mean this because almost everyone can hit 800 or even 900 at opp3, perhaps 1 ghz at opp4 (sadly not me D
This way everyone should be able to use their speed at their minimum voltage, minimizing battery use and damage to the cpu.
Being able to boot at such opp would be best, but that opens the door for all sorts of hell.
Thanks for the script anyway.
With, I don't play without soundPleng said:Jdbye said:Mario Kart 64 however is fullspeed
Wow I just... hmm... never mind.
Is that with or without sound?
Jdbye said:With, I don't play without sound
It's almost the same, the characters are different in the DS version and they added a few extra features. I never cared much for the adventure mode, actually I used a cheat to unlock all the tracks then just played them in the tracks modePleng said:Jdbye said:With, I don't play without sound
Awesome. I wonder if it would still be full speed with 2-4 players? Once external joypad support has been implemented, of course!
Meh. I tried to play diddy kong on the DS. I don't know if it's the same as the N64 version but I got tired of being forced to ead a story before I could actually play, I like games you can just pick up and play. I mean, come on, it's a racing game!!
