Re: Broken PST for Sony Vaio FX-502 with Athlon XP 1900+ fixed !

Re: Broken PST for Sony Vaio FX-502 with Athlon XP 1900+ fixed !

[Alex Simonov]

--- Ducrot Bruno <ducrot@poupinou.org> wrote:
> On Wed, Oct 01, 2003 at 07:13:13AM -0700, Alex
> Simonov wrote:
> 
> I think you can replace the powernow-k7.c of
> your kernel
> with the cvs version, without changing all.
> 
> There are not enough change in core (yet) with
> the one
> you have I guess.


Hi Bruno, 

Thank you very much for the advice. I took the
powernow-k7.c from the CVS, and compiled it with
my "fake" PST. I had to fix only the missing
define for the wrmsrl and rdmsrl symbols. So far
the powernow scaling for my XP 1900+ seems to
work. 
Just one question-the x86info utility displays
either "Voltage changes wont happen" or Frequency
changes wont happen" depending on that if you're
changing the speed up or down, because of the
CVID and CFID bits set to 0 in each change_fid or
change_vid function? Does this mean that VID/FID
is not changing? The MSR register values are set
anyway, is there any definitive way to make sure
if I have the correct voltage output?

Thank you very much,

Alex


__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

Re: Broken PST for Sony Vaio FX-502 with Athlon XP 1900+ fixed !

[Dave Jones]

On Mon, Oct 06, 2003 at 08:37:29AM -0700, Alex Simonov wrote:

 > Thank you very much for the advice. I took the
 > powernow-k7.c from the CVS, and compiled it with
 > my "fake" PST. I had to fix only the missing
 > define for the wrmsrl and rdmsrl symbols. So far
 > the powernow scaling for my XP 1900+ seems to
 > work. 
 > Just one question-the x86info utility displays
 > either "Voltage changes wont happen" or Frequency
 > changes wont happen" depending on that if you're
 > changing the speed up or down, because of the
 > CVID and CFID bits set to 0 in each change_fid or
 > change_vid function? Does this mean that VID/FID
 > is not changing? The MSR register values are set
 > anyway, is there any definitive way to make sure
 > if I have the correct voltage output?

Add printk's to change_VID() ?

		Dave

-- 
 Dave Jones     http://www.codemonkey.org.uk

Re: Broken PST for Sony Vaio FX-502 with Athlon XP 1900+ fixed !

[Ducrot Bruno]

On Mon, Oct 06, 2003 at 08:37:29AM -0700, Alex Simonov wrote:
> 
> --- Ducrot Bruno <ducrot@poupinou.org> wrote:
> > On Wed, Oct 01, 2003 at 07:13:13AM -0700, Alex
> > Simonov wrote:
> > 
> > I think you can replace the powernow-k7.c of
> > your kernel
> > with the cvs version, without changing all.
> > 
> > There are not enough change in core (yet) with
> > the one
> > you have I guess.
> 
> 
> Hi Bruno, 
> 
> Thank you very much for the advice. I took the
> powernow-k7.c from the CVS, and compiled it with
> my "fake" PST. I had to fix only the missing
> define for the wrmsrl and rdmsrl symbols. So far
> the powernow scaling for my XP 1900+ seems to
> work. 
> Just one question-the x86info utility displays
> either "Voltage changes wont happen" or Frequency
> changes wont happen" depending on that if you're
> changing the speed up or down, because of the
> CVID and CFID bits set to 0 in each change_fid or
> change_vid function?

Bug in x86info perhaps?
Ah yes.  that look like this, in AMD/powernow.c:

     62         if (read_msr(cpu->number, MSR_FID_VID_CTL, &vidctl.val) != 1) {
     63                 printf ("Something went wrong reading MSR_FID_VID_CTL\n");
     64                 return;
     65         }
     66 
     67         printf ("FID changes %s happen\n", vidctl.FIDC ? "will" : "won't");
     68         printf ("VID changes %s happen\n", vidctl.VIDC ? "will" : "won't");
     69 
     70         if (vidctl.VIDC)
     71                 printf ("Current VID multiplier code: %0.3f\n", mobile_vid_table[vidctl.VID]);
     72         if (vidctl.FIDC)
     73                 printf ("Current FSB multiplier code: %.1f\n", fid_codes[vidctl.FID]);

but that is wrong.

> Does this mean that VID/FID
> is not changing?

They do.

> The MSR register values are set
> anyway, is there any definitive way to make sure
> if I have the correct voltage output?
> 

As pointed by Dave, just add some printk() (or dprintk) to print
raw MSR_K7_FID_VID_STATUS, or fields from a union msr_fidvidstatus.

-- 
Ducrot Bruno

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.

RE: Release 1.00.08 of the AMD64 Frequency Driver

[paul.devriendt]

[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]

Hi Dave,

Attached is a bzipped tar file containing frequency support for 
AMD's Athlon 64 and Opteron. There are 2 .c files in the tarball 
- one for 2.4 and one for 2.6.

I believe this is it for now, but there will be more updates coming
soon. (Sorry, can not define soon). There are some hardware changes
coming that will impact this, and also adding code for battery
detection with ACPI.

Paul.

> -----Original Message-----
> From: Pavel Machek [mailto:pavel@suse.cz]
> Sent: Friday, September 26, 2003 3:40 AM
> To: Devriendt, Paul
> Cc: Langsdorf, Mark; Brunner, Richard
> Subject: Re: Release 1.00.08 of the AMD64 Frequency Driver
> 
> 
> Hi!
> 
> > Ok, but Dominik is not around until Oct 2nd. When he gets back,
> 
> That's next week :-(.
> 
> Anyway Dave Jones is listed as maintainer of cpufreq, so it should be
> okay to go to Dave, directly, Cc: to cpufreq@www list. Perhaps it is
> good idea to try sending it with him? [Or should I do the pushing?]
> 
> CPU FREQUENCY DRIVERS
> P:      Dave Jones
> M:      davej@codemonkey.org.uk
> L:      cpufreq@www.linux.org.uk
> W:      http://www.codemonkey.org.uk/cpufreq/
> S:      Maintained
> 
> 
> 								Pavel
> -- 
> When do you have a heart between your knees?
> [Johanka's followup: and *two* hearts?]
> 


[-- Attachment #2: amd64freq.08.tar.bz2 --]
[-- Type: application/octet-stream, Size: 10136 bytes --]

[-- Attachment #3: Type: text/plain, Size: 143 bytes --]

_______________________________________________
Cpufreq mailing list
Cpufreq@www.linux.org.uk
http://www.linux.org.uk/mailman/listinfo/cpufreq

Broken PST for Sony Vaio FX-502 with Athlon XP 1900+ fixed !

[Alex Simonov]

Hello guys,

Thanks to the all people, contributing to the
CPUFREQ project, finally I have powernow working
on my Vaio with upgraded Athlon 1900+ CPU! Thank
you guys, you're great!

This weekend I installed the 2.4.22-10mdk
Mandrake
kernel on my Linux system, and spent some time
tweaking the cpufreq driver. The problem was that
there was no suitable for my CPU PST table in the
BIOS. I modified a little bit the powernow-K7
module to hardwire the FID and VID values (not
forgetting to fix also the change_fid (VID) and
change_VID (FID) bug, which for some reason the
mandrake developers haven't fixed), and
guess what-I got the powernow working! Below is
the dmesg printout for the powernow module:

powernow: AMD K7 CPU detected.
powernow: PowerNOW! Technology present. Can
scale: frequency and voltage.
powernow: Found PSB header at c00f74d0
powernow: Table version: 0x12
powernow: Flags: 0x0 (Mobile voltage regulator)
powernow: Settling Time: 100 microseconds.
powernow: Has 28 PST tables. (Only dumping ones
relevant to this CPU).
powernow: Sorry, no relevant to this CPU PST
found!
powernow: Trying to apply mobile Athlon XP 1900+
workaround..
powernow:    FID: 0x4 (5.0x [500MHz])   VID: 0xd
(1.350V)
powernow:    FID: 0x6 (6.0x [600MHz])   VID: 0xd
(1.350V)
powernow:    FID: 0xa (8.0x [800MHz])   VID: 0xd
(1.350V)
powernow:    FID: 0xe (10.0x [1000MHz]) VID: 0xd
(1.350V)
powernow:    FID: 0x2 (12.0x [1200MHz]) VID: 0xd
(1.350V)
powernow:    FID: 0x16 (14.0x [1400MHz])       
VID: 0xd (1.350V)
powernow:    FID: 0x1a (16.0x [1600MHz])       
VID: 0xd (1.350V)

powernow: Minimum speed 500 MHz. Maximum speed
1600 MHz.

After the command echo -n "0%100%userspace" >
/proc/cpufreq I'm able to control manually the
speed petween 500 and 1600 MHz in seven steps,
using the /proc/sys/cpu/0/cpufreq interface. The
frequency change is confirmed also by x86info
utility.

This week I'll play a little bit with the VID
values of the "faked" PST table trying to see if
I  can scale down also the voltage-at the moment
I took the "safe" approach to use always the
nominal voltage.  

Thank you all once again,

Regards,

Alex


__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

Re: Broken PST for Sony Vaio FX-502 with Athlon XP 1900+ fixed !

[Ducrot Bruno]

On Mon, Sep 29, 2003 at 03:10:02AM -0700, Alex Simonov wrote:
> Hello guys,
> 
> Thanks to the all people, contributing to the
> CPUFREQ project, finally I have powernow working
> on my Vaio with upgraded Athlon 1900+ CPU! Thank
> you guys, you're great!
> 
> This weekend I installed the 2.4.22-10mdk
> Mandrake
> kernel on my Linux system, and spent some time
> tweaking the cpufreq driver. The problem was that
> there was no suitable for my CPU PST table in the
> BIOS. I modified a little bit the powernow-K7
> module to hardwire the FID and VID values (not
> forgetting to fix also the change_fid (VID) and
> change_VID (FID) bug, which for some reason the
> mandrake developers haven't fixed), and
> guess what-I got the powernow working! Below is
> the dmesg printout for the powernow module:

Warn: there are other bugs that you have to fix, or
any experiment with vid values will not work.

-- 
Ducrot Bruno

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.