Biggest difference is all the CPU governors have been added back in - as well, TUN is back to being a module and not included in the kernel - weirdest thing, but once I enabled the other governors, and built TUN internally, the kernel would not boot. Make tun a module, or turn off governors, no issues. WEIRD.

All Kernels

Thanks installing ulv 1.25Ghz now.

I couldnt get any of ur 1.2ghz to work from your old kernels, but i can get 1.2ghz lw from P3 to install fine. Should i try them again? Or if they didnt work last time, they wont work this time?

Since it is a new compile - I think it is worth trying again ...

How do you load a module again? I forget.

Ah ok good! Maybe, just maybe, I can find a working 1.25ghz *cross fingers*

insmod /system/lib/modules/cifs.ko

Although - I have provided scripts to load all of these (as some things, such as nfs, require several modules)

You can also add this to csm.sh and have it load automagically at boot-up

What if I selected the modules from ROM Manager, do they come preloaded or do I have to load them with your scripts?

Amazing work btw

You would still have to load them - this just gives you the support

Thanks!

One more question I promise! Once I load them, I only have to do that once right? Never again? Sorry for sounding so n00bish but TUN is important to me.

now that you added all the cpu governors, does it conflict with the setcpu governors?

another super n00b question but what is TUN?

No .. this is making MORE governors available to you in SetCPU - therefore giving it more functionality

It is for tunneling, ie. vpnc

Is TUN absolutely necessary to run the kernal?

Nope, only necessary if you want to tunnel, ie vpnc Most people (myself included) do not use it. It's useful for logging into corporate networks, etc

Any chance to see 125mhz as an option in the future?

What are the modules for? Like the cifs.ko and such

Explain why the quadrant scores are so high esp at 550Mhz

Something very weird is going on and I hope you can explain it. I'm running Kangarade's latest froyo, 1.1 along w/ Chevy ulv 1.2Ghz.

I ran quadrant scores for 4 slots; 550, 800, 1.0 and 1.2Ghz

550: 1050, 1196, 1204, 1123.

800: 1163,1323,1386,1298,1180.

1.0Ghz: 1484,1480,1439,1249,1486.

1.2Ghz: 1413, 1511, reboot, reboot (did all these tests right in a row)

550: Avg 1147 which is 2.08x as fast as it should be and what I have it set at in setcpu. That's nice that it's fast, but when I want to save battery life I dial it down to around 550? Why is it running 2x as fast as it "should?" (fyi I performed these tests w/ the kernels before 7/1 update and after 7/1 update at least for 550Mhz and it was always running this fast)

800: Avg 1270, 1.59x as fast

1.0Ghz Avg 1428, 1.43x as fast

I'm happy that I can dial it way up at 1.0Ghz, however why doesn't the 550Mhz run closer to where it should?

So in SetCPU you set both min/max to 550, and it still is that fast?