OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Debian => Topic started by: ZDevil on September 27, 2007, 12:08:41 pm
-
Rereading the comments section in titchy wiki, I saw somebody mentioning an alternative 2.6.17 kernel with fastfpe support: http://www.bigbridgezau.sakura.ne.jp/dev/debian/ (http://www.bigbridgezau.sakura.ne.jp/dev/debian/)
There are two versions:
zImage-2.6.17-cpufreq-fastfpe-hda3.bin
zImage-2.6.17-cpufreq-fastfpe.bin
It is supposed to be renamed to "zImage.bin" and then flashed with updater.sh in the OK flash menu.
Which one should we use for C3x00 models?
And there is a separate tarball containing the kernel modules for 2.6.17, which don't seem to be included in the kernel image. I extracted the tarball and saw all the kernel modules inside one big folder without the hierarchy we find in /lib/modules/2.x.xx .
I will try this to see if it fares better than the current kernel.
Any hint?
-
Rereading the comments section in titchy wiki, I saw somebody mentioning an alternative 2.6.17 kernel with fastfpe support: http://www.bigbridgezau.sakura.ne.jp/dev/debian/ (http://www.bigbridgezau.sakura.ne.jp/dev/debian/)
There are two versions:
zImage-2.6.17-cpufreq-fastfpe-hda3.bin
zImage-2.6.17-cpufreq-fastfpe.bin
It is supposed to be renamed to "zImage.bin" and then flashed with updater.sh in the OK flash menu.
Which one should we use for C3x00 models?
And there is a separate tarball containing the kernel modules for 2.6.17, which don't seem to be included in the kernel image. I extracted the tarball and saw all the kernel modules inside one big folder without the hierarchy we find in /lib/modules/2.x.xx .
I will try this to see if it fares better than the current kernel.
Any hint?
the -hda3 image will probably boot from hda3 ?
I suggest trying the other one.
Not sure about the modules, but I would create the hierarchy.
There also seems to be a 2.6.20 kernel ?
Chero.
-
(sorry, chero ) I zipped the modules with the correct hierarchy here. See how far we can go ...
Unzip the file under /lib/modules/ and reboot.
Not sure about the 2.6.20 kernel as it doesn't seem to have fastfpe though ...
-
Report after a brief trial for two hours:
The 2.6.17 kernel did flash. And I could play with dvfm.
But the tradeoff was my wifi CF no longer works. It was loaded with hostap. Blacklisting hostap made the wifi card undetectable at all.
Recovery procedure:
#0. No need to panic when things fail.
#1. Just go back to http://www.bigbridgezau.sakura.ne.jp/dev/debian/ (http://www.bigbridgezau.sakura.ne.jp/dev/debian/)
#2 Download zImage-2.6.20-cpufreq.bin.
#3 Rename it to zImage.bin
#4 Put this and updater.sh on SD.
#5 Flash this kernel just like any other usual Zaurus rom in the OK flash mode.
#6 Reboot the machine.
#7 Find your copy of zaurus-hardware-support.deb
#8 Run dpkg-deb -x zaurus-hardware-support.deb . to reinstall the kernel modules for the Z.
#9 Run pccardctl eject 1 and take out the wifi cf.
#10 Wait a few seconds and reinsert the wifi cf.
#11 Your card should be able to connect to the network again.
Well, then ...
Don't know if dvfm can work on the zImage-2.6.20-cpufreq.bin or not.
Or has anyone come up with a new kernel for more fun?
-
Report after a brief trial for two hours:
The 2.6.17 kernel did flash. And I could play with dvfm.
But the tradeoff was my wifi CF no longer works. It was loaded with hostap. Blacklisting hostap made the wifi card undetectable at all.
Recovery procedure:
#0. No need to panic when things fail.
#1. Just go back to http://www.bigbridgezau.sakura.ne.jp/dev/debian/ (http://www.bigbridgezau.sakura.ne.jp/dev/debian/)
#2 Download zImage-2.6.20-cpufreq.bin.
#3 Rename it to zImage.bin
#4 Put this and updater.sh on SD.
#5 Flash this kernel just like any other usual Zaurus rom in the OK flash mode.
#6 Reboot the machine.
#7 Find your copy of zaurus-hardware-support.deb
#8 Run dpkg-deb -x zaurus-hardware-support.deb . to reinstall the kernel modules for the Z.
#9 Run pccardctl eject 1 and take out the wifi cf.
#10 Wait a few seconds and reinsert the wifi cf.
#11 Your card should be able to connect to the network again.
Well, then ...
Don't know if dvfm can work on the zImage-2.6.20-cpufreq.bin or not.
Or has anyone come up with a new kernel for more fun?
In connection with a comment by jpmatrix elsewhere in this forum: Neil said on his site that the kernel was the angstrom one. Do you think that is the case? The ones you are talking about here aren't angstrom are they? I'm wondering about flashing the zImage-2.6.20-cpufreq.bin one. Which updater.sh should I use, the one from TitchyLinux, the one from the same site as this kernel, or does it not matter? I did download some file from Neil'ssite which are meant to let you tweak the updater.sh. Would they be useful?
Sorry for all the questions!
Any other problems with using this zImage-2.6.20-cpufreq.bin than you mention above?
Cheers
-
updater.sh:
Always use the one in the same download location as the zImage.bin.
You can tell it is really the Angstrom kernel by typing:
ls -l /lib/modules/2.6.20/build and ls -l /lib/modules/2.6.20/source
Then you'll see:
/lib/modules/2.6.20/build -> /data/build/koen/OE/build/tmp/angstrom/work/spitz-angstrom-linux-gnueabi/linux-rp-2.6.20-r2/linux-2.6.20
/lib/modules/2.6.20/source -> /data/build/koen/OE/build/tmp/angstrom/work/spitz-angstrom-linux-gnueabi/linux-rp-2.6.20-r2/linux-2.6.20
-
updater.sh:
Always use the one in the same download location as the zImage.bin.
You can tell it is really the Angstrom kernel by typing:
ls -l /lib/modules/2.6.20/build and ls -l /lib/modules/2.6.20/source
Then you'll see:
/lib/modules/2.6.20/build -> /data/build/koen/OE/build/tmp/angstrom/work/spitz-angstrom-linux-gnueabi/linux-rp-2.6.20-r2/linux-2.6.20
/lib/modules/2.6.20/source -> /data/build/koen/OE/build/tmp/angstrom/work/spitz-angstrom-linux-gnueabi/linux-rp-2.6.20-r2/linux-2.6.20
but then--titchy would be using eabi, wouldn't it?
-
Did a further simple try of adjusting CPU frequency with zImage-2.6.20-cpufreq.bin.
I checked out more info about this kernel. It seems to be it is possible to do both over/underclocking and scaling.
cat /sys/devices/system/cpu/cpu0/cuqfreq/cpu_max_freq
624000cat /sys/devices/system/cpu/cpu0/cuqfreq/cpu_min_freq
13000cat /sys/devices/system/cpu/cpu0/cuqfreq/show_frequency_and_voltage
Freq Vol
26000 900
104000 1100
208000 1200
312000 1300
416000 1350
520000 1450
624000 1550cat /sys/devices/system/cpu/cpu0/cuqfreq/scaling_available_freq
L 2N Freq
2 2 26000
3 2 39000
4 2 52000
5 2 65000
6 2 78000
7 2 91000
8 2 104000
9 2 117000
10 2 130000
11 2 143000
12 2 156000
13 2 169000
14 2 182000
15 2 195000
16 2 208000
17 2 221000
18 2 234000
19 2 247000
20 2 260000
21 2 273000
22 2 286000
23 2 299000
24 2 312000
25 2 325000
26 2 338000
27 2 351000
28 2 364000
29 2 377000
30 2 390000
31 2 403000
2 3 39000
3 3 58500
4 3 78000
5 3 97500
6 3 117000
7 3 136500
8 3 156000
9 3 175500
10 3 195000
11 3 214500
12 3 234000
13 3 253500
14 3 273000
15 3 292500
16 3 312000
17 3 331500
18 3 351000
19 3 370500
20 3 390000
21 3 409500
22 3 429000
23 3 448500
24 3 468000
25 3 487500
26 3 507000
27 3 526500
28 3 546000
29 3 565500
30 3 585000
31 3 604500
2 4 52000
3 4 78000
4 4 104000
5 4 130000
6 4 156000
7 4 182000
8 4 208000
9 4 234000
10 4 260000
11 4 286000
12 4 312000
13 4 338000
14 4 364000
15 4 390000
16 4 416000
17 4 442000
18 4 468000
19 4 494000
20 4 520000
21 4 546000
22 4 572000
23 4 598000
24 4 624000
2 5 65000
3 5 97500
4 5 130000
5 5 162500
6 5 195000
7 5 227500
8 5 260000
9 5 292500
10 5 325000
11 5 357500
12 5 390000
13 5 422500
14 5 455000
15 5 487500
16 5 520000
17 5 552500
18 5 585000
19 5 617500
2 6 78000
3 6 117000
4 6 156000
5 6 195000
6 6 234000
7 6 273000
8 6 312000
9 6 351000
10 6 390000
11 6 429000
12 6 468000
13 6 507000
14 6 546000
15 6 585000
16 6 624000
2 7 91000
3 7 136500
4 7 182000
5 7 227500
6 7 273000
7 7 318500
8 7 364000
9 7 409500
10 7 455000
11 7 500500
12 7 546000
13 7 591500
2 8 104000
3 8 156000
4 8 208000
5 8 260000
6 8 312000
7 8 364000
8 8 416000
9 8 468000
10 8 520000
11 8 572000
12 8 624000
cat /sys/devices/system/cpu/cpu0/cuqfreq/scaling_governor
pdaX27_governor
cat /sys/devices/system/cpu/cpu0/cuqfreq/scaling_available_governor
pdaX27_governorperformance
There is a command line tool "cpufreq-selector" in gnome-applets, which has very simple syntax (cpufreq-selector -o CPU -g GOVERNOR -f FREQUENCY) but i tried like
cpufreq-selector -o 0 -g pdaX27_governor -f 520000
cpufreq-selector -o 0 -g pdaX27_governorperformance -f 520000
cpufreq-selector -o 0 -f 520000
cpufreq-selector -f 520000
...
etc
All combinations failed... Either I got "Invalid governor" or "Cannot set frequency xxxxxx"... and hint?
-
And I got this bit from http://ftp.kelp.or.kr/pub/arm-linux/people...2004/README.txt (http://ftp.kelp.or.kr/pub/arm-linux/people/xscale/mainstone/04-28-2004/README.txt)
freq: the desired frequnecy in khz;
n_value: the N value in CCCR;
fast_bus_mode: [0|1], to specify switch to fast bus mode or not.
For example,
# dvfm 104000 2 0
will switch the system to 104Mhz, with N=2 means RUN mode,no fast bus mode.
# dvfm 65000 5 1
will switch the system to 65Mhz, with N=5 means TURBO mode,fast bus mode.
Note: Please refer to Intel PXA27x Process Developer's Kit manual to know the combination of freq N and fast_bus_mode, incorrect combination will hang the system, or even damage the hardware!
So, how to use dvfm to set the clock precisely?
[EDIT]
I tool a look at the cpuoverclock.py script and found the relevant chunk:
FREQ_TAB = ["104", "208", "312", "416", "520", "624"]
CCCR_L_TAB = [ "8", "16", "16", "16", "16", "16"]
CCCR_2N_TAB = [ "2", "2", "3", "4", "5", "6"]
...
...
...
CMD = "dvfm " + self.CPU_CCCR_L + " " + self.CPU_CCCR_2N + " 1 2 1"So I tried dvfm 16 5 1 2 1
(the spaces are important!)
(I notice that in the titchy wiki comments someone called ip-206-32 has posted similar things, but perhaps due to the display problem his commands are not shown properly with irregular spacing.)
L:16 ZN:5 b:1 t:2
vm_setvoltage: write 0C
Set frequency to 520000 with L:16 ZN:5 B:1 Turbo Mode, A:1
Calibrating delay loop... 517.73 BogoMIPS (lpj=2588672)(Don't ask me what's going on here as I am no computer guru)
Then I got 520 (517.73) mhz, as confirmed by cat /proc/cpuinfo.
dvfm 16 4 1 2 1 (again, mind the spacing!) brings me back to 416 (415.33) mhz. And so on.
But still there is screen flickering after overclocking...
-
(sorry, chero ) I zipped the modules with the correct hierarchy here. See how far we can go ...
Unzip the file under /lib/modules/ and reboot.
Not sure about the 2.6.20 kernel as it doesn't seem to have fastfpe though ...
I installed 2.6.20 kernel.can I use your modules and how to unzip correctly?
-
The kernel modules seem to be version/build specific and are for 2.6.17 and so won't work under 2.6.20 kernels. (You'll get lots of dmesg errors when booting).