Howto: Dynamic CPU speed with Athlon XP and nForce2 boards

Message

Jinidog · Post by **Jinidog** » Wed Sep 28, 2005 5:53 am

My nforce2-board (N2U400) can bring the clock down, but not bring it up again.
It freezes when I try so.
Has someone a hint?

Jase · Post by **Jase** » Thu Sep 29, 2005 6:26 pm

Cpufreq seems to work nicely or atleast I think so. When I set my fsb to minimum the CPU MHz in /proc/cpuinfo doesn't update, but the bogomips drop 4400 to 3300. So I think it works.

On the other hand atxp1 doesn't work at all. I get kernel oops when trying to change the voltage. Dmesg shows this when I load the atxp1 modules "atxp1 2-004e: Using VRM: 9.0" There's no " .... atxp1: Detected on SMBus nForce2 adapter at 5000, address 0x37" like in the first post of this thread.

I use 2.6.13.2-nitro1 kernel and atxp1-0.6.

Here's the oops

Code: Select all

Unable to handle kernel paging request at virtual address 30353631
 printing eip:
b019e953
*pde = 00000000
Oops: 0000 [#1]
PREEMPT SMP
Modules linked in: atxp1 ppp_synctty ppp_async crc_ccitt ppp_generic slhc w83781d i2c_sensor i2c_isa cpufreq_nforce2 i2c_nforce2 spca5xx budget_av saa7146_vv video_buf v4l1_compat v4l2_common videodev budget_core dvb_core saa7146 ttpci_eeprom stv0299 tda10021 tda1004x firmware_class nvidia shfs
CPU:    0
EIP:    0060:[<b019e953>]    Tainted: P      VLI
EFLAGS: 00210246   (2.6.13.2-nitro1)
EIP is at sysfs_readdir+0xb3/0x230
eax: 00000000   ebx: ea189d5c   ecx: ffffffff   edx: ea189d58
esi: ea189d58   edi: 30353631   ebp: 30353631   esp: de449f30
ds: 007b   es: 007b   ss: 0068
Process bash (pid: 8682, threadinfo=de448000 task=da0d1aa0)
Stack: ea189d58 b04f2b02 00000002 00000001 00000000 000027b9 00000004 ea189bd4
       00000000 ea189d0c d4bdb7e8 cdcad4c0 fffffffe cdcad4c0 b0175909 cdcad4c0
       de449fa0 b0175bf0 00001000 08127f0c fffffff7 b0175d62 cdcad4c0 b0175bf0
Call Trace:
 [<b0175909>] vfs_readdir+0x79/0xa0
 [<b0175bf0>] filldir64+0x0/0xf0
 [<b0175d62>] sys_getdents64+0x82/0xe2
 [<b0175bf0>] filldir64+0x0/0xf0
 [<b01031ab>] sysenter_past_esp+0x54/0x75
Code: 75 16 8b 1b 39 5c 24 1c 75 ee 83 c4 28 31 c0 5b 5e 5f 5d c3 8d 74 26 00 89 34 24 e8 28 e5 ff ff 89 c5 b9 ff ff ff ff 31 c0 89 ef <f2> ae f7 d1 49 89 4c 24 20 8b 46 20 85 c0 0f 84 42 01 00 00 8b

Here's the compiler errors

Code: Select all

make -C /lib/modules/2.6.13.2-nitro1/build SUBDIRS=/usr/src/atxp1-0.6 modules
make[1]: Entering directory `/usr/src/linux-2.6.13.2-nitro1'
  CC [M]  /usr/src/atxp1-0.6/atxp1.o
/usr/src/atxp1-0.6/atxp1.c:169: warning: initialization from incompatible pointer type
/usr/src/atxp1-0.6/atxp1.c:169: warning: initialization from incompatible pointer type
/usr/src/atxp1-0.6/atxp1.c:211: warning: initialization from incompatible pointer type
/usr/src/atxp1-0.6/atxp1.c:211: warning: initialization from incompatible pointer type
/usr/src/atxp1-0.6/atxp1.c:251: warning: initialization from incompatible pointer type
/usr/src/atxp1-0.6/atxp1.c:251: warning: initialization from incompatible pointer type
  Building modules, stage 2.
  MODPOST
  CC      /usr/src/atxp1-0.6/atxp1.mod.o
  LD [M]  /usr/src/atxp1-0.6/atxp1.ko
make[1]: Leaving directory `/usr/src/linux-2.6.13.2-nitro1'

And here's my kernel configs of I2C and SENSORS

Code: Select all

# I2C support
CONFIG_I2C=y
CONFIG_I2C_CHARDEV=y
# I2C Algorithms
CONFIG_I2C_ALGOBIT=m
CONFIG_I2C_ALGOPCF=m
CONFIG_I2C_ALGOPCA=m
# I2C Hardware Bus support
CONFIG_I2C_ISA=m
CONFIG_I2C_NFORCE2=m
CONFIG_I2C_SENSOR=m

# Hardware Monitoring support
CONFIG_HWMON=y
CONFIG_SENSORS_EEPROM=m
CONFIG_SENSORS_ATXP1=m
CONFIG_SENSORS_IT87=m
CONFIG_SENSORS_W83781D=m
CONFIG_SENSORS_W83627HF=m
CONFIG_SENSORS_W83627EHF=m

Hasw · Post by **Hasw** » Thu Sep 29, 2005 7:14 pm

@Jinidog: What's your Boot-FSB and your lowest value?

@Jase: cpufreq should update /proc/cpuinfo...hm. The "Detected on..." message was removed. Also they changed somewhere between 2.6.11 and 2.6.12-13 the sysfs-interface ("warning: initialization from incompatible pointer type"...not good), so it will crash if someone tries to write to the device...
Have you checked if the ATXP1 module is maybe already in your kernel?

Jinidog · Post by **Jinidog** » Thu Sep 29, 2005 7:17 pm

I have a AthlonXP 2800+.
Normally it runs with 2070 MHz and I can scale it down to 1512500 Hz.

Jase · Post by **Jase** » Thu Sep 29, 2005 8:10 pm

Hasw wrote:Have you checked if the ATXP1 module is maybe already in your kernel?

Yes, it wasn't there so I patched the kernel. The patch applied with some minor changes. I'll take a look at the sysfs changes and try to solve it by my self. I just didn't know where to start from. Thanks anyway.

stealth_br · Post by **stealth_br** » Thu Sep 29, 2005 8:30 pm

Any tool to change vcore on asus motherboard ?
atxp1 doesn't work.

stealth_br · Post by **stealth_br** » Thu Sep 29, 2005 8:33 pm

I forgot to ask.
does anyone have 8rdavcore for linux. They released a 0.5.5 version , but after GPL problems it has disappeared and i can find nowhere.

Hasw · Post by **Hasw** » Fri Nov 18, 2005 7:51 pm

8rdavcore 0.5.5 was a userspace ATXP1 driver. Since there's now a ATXP1 module for the kernel the old cold isn't required any more. Maybe when I get the time I'll finish the successor of 8rdavcore, which will run on linux.

alphonsebrown · Post by **alphonsebrown** » Sun Nov 20, 2005 10:40 am

I have some problem with the kernel patches

# pwd
/usr/src/kernels/2.6.14-1.1637_FC4-i686

# patch -Np1 < atxp1-0.6.patch
patching file drivers/i2c/chips/Kconfig
Hunk #1 succeeded at 74 (offset -319 lines).
patching file drivers/i2c/chips/Makefile
Hunk #1 FAILED at 11.
1 out of 1 hunk FAILED -- saving rejects to file drivers/i2c/chips/Makefile.rej
patching file drivers/i2c/chips/atxp1.c

# patch -Np1 < i2c-vid-vrm90.patch
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- linux-2.6.11-rc4-mm1-orig/include/linux/i2c-vid.h 2005-02-26 16:12:23.710354080 +0100
|+++ linux-2.6.11-rc4-mm1/include/linux/i2c-vid.h 2005-02-26 16:13:27.690627600 +0100
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored

please any suggestions are welcome

PrakashP · Post by **PrakashP** » Sun Nov 20, 2005 11:14 am

2.6.14 doesn't need patching.

alphonsebrown · Post by **alphonsebrown** » Sun Nov 20, 2005 12:06 pm

PrakashP wrote:2.6.14 doesn't need patching.

wow that was fast, thank you!

edit: btw: PrakashP, I'm not good with ebuild, how can I use your cpufreq patch? http://punnoor.de/nvfreqd/nvfreqd-overlay.tar.bz2 <- is it this file? Thanks in advance!

so should I worry about:

Code: Select all

# patch -Np1 < atxp1-0.6.patch
patching file drivers/i2c/chips/Kconfig
Hunk #1 succeeded at 74 (offset -319 lines).

alphonsebrown · Post by **alphonsebrown** » Sun Nov 20, 2005 12:12 pm

micmac wrote:Btw without C1 Disconnect my system doesn't freeze with atxp1/cpufreq_nforce2 (well, until now at least ). Furthermore C1 Disconnect seems redundant while using atxp1/cpufreq_nforce2, the analog out of my soundcard sounds much better without it and my system doesn't feel laggy anymore while running at low speed (1.1V & 770MHz here).

Sorry is that C1:

Code: Select all

Query Athlon powersaving mode...
[b]athcool version 0.3.11[/b] - control power-saving mode on AMD Athlon/Duron CPUs


nVIDIA nForce2 (10de 01e0) found
'Halt Disconnect and Stop Grant Disconnect' bit is enabled.

zensoni · Post by **zensoni** » Fri Nov 25, 2005 1:46 pm

Hi there

I have been playing around with cpufreq-nforce2. It has great potential, but I am not satisfied yet

On my ASUS A7N8X-X, I can bring my Barton 2800+ (2083 = 12.5 * 166) down to 625Mhz. But I can not bring it up again. When I cross around 1000MHz on the way down I cannot go up again.

Scenario: From 2083 -> 1500Mhz -> 1200Mhz -> 800Mhz -> 625Mhz -> 700 -> 800 -> 900 -> 1000 -> 1100 -> 1200 -> 1300 -> 1400 -> boom (1500)
Scenario: 2083 -> 1600 -> 1200 -> 1600 -> 2083 totally stable
Scenario: 2083 -> 1600 -> 1200 -> 1000 -> 1200 (boom)

I then tried another board. Aopen AK79D-400VN. There I can do whatever I desire, but the MHz does not go down in /proc/cpuinfo ALTHOUGH the bogomips does!!! The bogomips value gets updated, but the system remains at 2083. I then tried another CPU. Same deal. I don't get it. AK79D-400VN is listed as supported. I can see that other ppl in this thread have had simelar problems.

Any clues? Ideas? solutions? Ohh yes, stock voltage, no overclocking, no out of bounds on ram and so forth, and the latest 2.6.14.2 kernel.

Regards Thomas, Denmark

woZa · Post by **woZa** » Mon Nov 28, 2005 4:39 pm

Hasw wrote:8rdavcore 0.5.5 was a userspace ATXP1 driver. Since there's now a ATXP1 module for the kernel the old cold isn't required any more. Maybe when I get the time I'll finish the successor of 8rdavcore, which will run on linux.

That would be really good... I had all this working perfectly on my 8rda+ but have since replaced it with an abit nf7s-v2 which it won't work with (crashes when increasing voltage after lowering...)

soql · Post by **soql** » Sat Dec 10, 2005 10:16 am

Hello !! Sorry for my very poor english.
Could you tell me which version of bios you use in yours 8rda+, because on my computer (gentoo,8rda+) cpufreq works but I can change FSB only with 20Mhz. If I have default FSB on 200 and I change to 180 everything ok, but

cpufreq-set -s 1700000

makes my gentoo halt immidietly

I use 2.6.14.3

anilan · Post by **anilan** » Wed Feb 22, 2006 11:54 am

Hallo,
I'm using an Epox 8RDA6+ Pro with Mobile-Barton 2500+ and changing FSB and voltage is possible and work fine, but I can't go below 1.325V. When I set Vcore to 1.300V the system hangs. I think 1.100V must be possible. What is wrong or has anybody an idea?

Thanks!

woZa · Post by **woZa** » Fri Mar 03, 2006 5:42 pm

Hmmm, autocpufreq scripts lowers voltage and cpu frequency when run but never raises either again. It is as if it doesn't realise that the cpu is at 100% load... Anyone else experience this? Doing things manually seems to work ok now...

luisfeser · Post by **luisfeser** » Wed Apr 05, 2006 12:17 pm

Anybody can change vcore in an Abit an7 mobo?
I can change the fsb, but not the vcore, so the temperature don't down

I think this is about uguru chip, that i can't see voltages or temperatures of my mobo.

luisfeser · Post by **luisfeser** » Wed Apr 05, 2006 7:09 pm

this is the error:
i can see the vcore:

Code: Select all

root@pcluisfe linux # cat /sys/bus/i2c/devices/9191-0290/driver/9191-0290/cpu0_vid
1850

(it's correct because overclocking)

but i can't change it

Code: Select all

root@pcluisfe linux # echo 1750 > /sys/bus/i2c/devices/9191-0290/driver/9191-0290/cpu0_vid
bash: /sys/bus/i2c/devices/9191-0290/driver/9191-0290/cpu0_vid: Permiso denegado

Any idea?

Mi pc is an athlon xp barton mobile 2500+ @ 2000Mhz in an Abit an7, with fsb 400

parism_s · Post by **parism_s** » Fri Jun 09, 2006 2:53 pm

Hi, is there any way to manually change the maximum_fsb frequency so that it is above the boot_fsb? The only option I see is the min_fsb=..
I have got a shuttle an35n ultra and I want to scale from 66Mhz to 200Mhz Fsb. However if I boot at 200Mhz it only goes down to 150Mhz. If I boot at 133 Mhz I am limited to an 133Mhz maximum but can scale down to 66Mhz. Using 8rdvcore in windows only booting at 133Mhz I can scale from 66 to 200 and back without any problems. Any recommendations? Unforunately I know nothing about programming so I don't have the knowledge to modify the cpufreq-nforce2 source.

fysa · Post by **fysa** » Wed Aug 16, 2006 7:26 pm

luisfeser wrote:this is the error:
i can see the vcore:
Code: Select all
root@pcluisfe linux # cat /sys/bus/i2c/devices/9191-0290/driver/9191-0290/cpu0_vid
1850
(it's correct because overclocking)

but i can't change it
Code: Select all
root@pcluisfe linux # echo 1750 > /sys/bus/i2c/devices/9191-0290/driver/9191-0290/cpu0_vid
bash: /sys/bus/i2c/devices/9191-0290/driver/9191-0290/cpu0_vid: Permiso denegado
Any idea?

Mi pc is an athlon xp barton mobile 2500+ @ 2000Mhz in an Abit an7, with fsb 400

Did you ever figure thisout? I have the same issue. 9191-0290 and cpu0_vid shows 1750 but I cannot modify it. This is a NF7-S2.

brucer · Post by **brucer** » Mon Sep 18, 2006 8:17 pm

I can setup the most modules and use the cpufreq-nforce2 for changing my CPU-Speed.
If i load the modules for atxp1 it says:

cpufreq: Detected nForce2 chipset revision C1
cpufreq: FSB changing is maybe unstable and can lead to crashes and data loss.
cpufreq: FSB currently at 100 MHz, FID 10.0
i2c_adapter i2c-1: nForce2 SMBus adapter at 0x5000
i2c_adapter i2c-2: nForce2 SMBus adapter at 0x5040

in your Howto it should be like that with dmesg:
atxp1: Detected on SMBus nForce2 adapter at 5000, address 0x37

after loading the modules I can see in the location /sys/bus/i2c/devices/9191-0290
all neccesary files and read out the /in1_input, but even with setting the file-rights correct
it is not possible to change the volt.

in my bios i set the core volt at 1.6
on my motherboard is a chip its named attansic so i expected this to work
my linux is gentoo, kernel 2.6.16

may be anyone of yours find some mistakes here
thanks

kondzik · Post by **kondzik** » Tue Sep 19, 2006 2:33 pm

luisfeser wrote:this is the error:
i can see the vcore:
Code: Select all
root@pcluisfe linux # cat /sys/bus/i2c/devices/9191-0290/driver/9191-0290/cpu0_vid
1850
(it's correct because overclocking)

but i can't change it
Code: Select all
root@pcluisfe linux # echo 1750 > /sys/bus/i2c/devices/9191-0290/driver/9191-0290/cpu0_vid
bash: /sys/bus/i2c/devices/9191-0290/driver/9191-0290/cpu0_vid: Permiso denegado
Any idea?

Mi pc is an athlon xp barton mobile 2500+ @ 2000Mhz in an Abit an7, with fsb 400

I've had similiar problem. I couldn't change Vcore through /sys/bus/i2c/devices/9191-0290/cpu0_vid but it is possible to do that thorugh /sys/bus/i2c/devices/0-004e/cpu0_vid. I have nf7-s board but i think it doesn't matters.

Howto: Dynamic CPU speed with Athlon XP and nForce2 boards

Various problems

what is about MSI K7N2 Delta-L and lowering vcore?