check the directories /sys/class/leds/pandora::*
Those are all the LEDs you can currently manipulate. Manually set "brightness" file (echo 255 > brightness) to a value between 0 and 255 to change the brightness (duh). Not all of them support brightness though: the ones on the left (sd1, sd2, wifi, and bluetooth) are just off or on. The power and charge leds on the right can be dimmed.
Another useful file to manipulate is "trigger". A trigger is a bit of code that will control the LED in specific ways. If your brightness value isn't sticking, it may be because there's a trigger overwriting the value. Try
Code:
cd /sys/class/leds/pandora\:\:power
echo timer > trigger
echo 1000 > delay_on
echo 100 > delay_off
and BLINK, BLINK, BLINK...
do "cat triggers" to see all the currently available triggers you can set it to. Most of them should be pretty obvious what they do. "none" for example stops all triggers and allows you to manually control the LED with the brightness file, so you can simply shut it off. It's possible to write new triggers, but Google is a better place to learn about how to do that.
To set an LED when overclocked, you can edit the file /usr/pandora/scripts/op_cpuspeed.sh to set one of the LEDs to do something, like set the power LED to blink as above, when overclocked, and reset it when dropping back below 500Mhz.