undervolting the Turion Ultra

Discussion in 'Hewlett Packard' started by Seketh, Oct 19, 2011.

  1. 970261

    970261 Scribbler - Standard Member

    Messages:
    334
    Likes Received:
    0
    Trophy Points:
    31
    got it. also, do we need to leave the window open after it starts up? or can we close it?

    just a quick ques. b/c i got it to work after extracting to the desktop.

    will wait tho, and keep it up...others *cough*Guests*cough* are probably seeing this or keeping tabs on this thread.
     
  2. Mr.Systematic

    Mr.Systematic Pen Pal - Newbie

    Messages:
    15
    Likes Received:
    0
    Trophy Points:
    6
    If you close the window the program exits and then after a standby and I think also after hibernation the default voltages for the p-states are restored (you can check this with the AMD power monitor). So then there is no more undervolting by PumaStateCtrl.
    YES, a system tray icon would be better but: I need time for this, so the most urgent at first.

    I don't completely understand your last paragraph (I am not an English native speaker).

    So, I just now added a 64 bit version under http://sourceforge.net/project/showfiles.php?group_id=246625&package_id=302910&release_id=647433
    If somebody tests it: a feedback here if it works or not (then maybe in my sourceforge.net forum) is appreciated. I can't test it because I have only 32 bit Vista, but it might function.
     
  3. miner

    miner Scribbler - Standard Member

    Messages:
    276
    Likes Received:
    0
    Trophy Points:
    31
    Thanks! I can confirm that it works in 64bit version of Vista. I'm using a ZM-86 and the default voltage you set in the program seem to be the best I could get out of my cpu as well.
     
  4. 970261

    970261 Scribbler - Standard Member

    Messages:
    334
    Likes Received:
    0
    Trophy Points:
    31
    it means "keep up the good work because other people are probably hoping a program like this will be developed"
     
  5. 2.0™

    2.0™ Been Inkin' Staff Member

    Messages:
    396
    Likes Received:
    90
    Trophy Points:
    41
  6. ChronoReverse

    ChronoReverse Pen Pal - Newbie

    Messages:
    49
    Likes Received:
    0
    Trophy Points:
    15
    Doesn't seem to work for my RM-70 (also Griffin core) in Vista 64.

    It says "p-state 0 for core 0 is not set because of overvoltage protection: the core voltage is too high for the core frequency" for all three p-stats and both cores.

    I even tried "64" for all three states and it still says that.

    Code:
    after executing InitializeOls
    model specific register exist
    Function "RdmsrEx" exists within DLL
    ExtendedModel: 0 BaseModel: 3  byModel: 3 byFamily:17
    handleCmdLineArgs()--argc:2
    strNumber:"0"
    strNumber:"1"
    strNumber:"2"
    void ApplyAllPStates()--address of THIS PumaStateCtrl object:000000000249A350
    void ApplyAllPStates()--address of m_pstates:000000000249A388
    void PSC::ApplyAllPStates(const PStates & pstates) begin
    void PSC::ApplyAllPStates(const PStates &) address of pstates.m_arp_pstate:000000000249A390
    void PSC::ApplyAllPStates(const PStates &) p-state index:0
    void PSC::ApplyAllPStates(const PStates &) p_pstateCurrent's address:00000000024973B0
    GetPStateFromMSR(...) for p-state #0:
    Reading from MSR succeeded
    GetPStateFromMSR(...)--FID:12 DivID:0 VID:38
    PState::AssignChangesToPstateFromMSR(PState & r_pstateFromMSR)
    setVidAndFrequencyForPState_Puma
    PumaStateCtrl::IsSafe(byVID:64, byFrequencyID:12, byDivisorID:0)--begin
    Resulting freq in MHz is:2000, VID is:64
    PumaStateCtrl::GetCPUID--Got function for CPUID
    PumaStateCtrl::GetCPUID--Calling CPUID succeeded:dwEDX:0
    PumaStateCtrl::GetMaximumFrequencyInMHz()--Calling GetCPUID succeeded
    get max freq--EDX register of function 4: 0 2nd byte: 0
    Setting P-state is NOT safe
    GetPStateFromMSR(...) for p-state #0:
    Reading from MSR succeeded
    GetPStateFromMSR(...)--FID:12 DivID:0 VID:38
    PState::AssignChangesToPstateFromMSR(PState & r_pstateFromMSR)
    setVidAndFrequencyForPState_Puma
    PumaStateCtrl::IsSafe(byVID:64, byFrequencyID:12, byDivisorID:0)--begin
    Resulting freq in MHz is:2000, VID is:64
    PumaStateCtrl::GetCPUID--Got function for CPUID
    PumaStateCtrl::GetCPUID--Calling CPUID succeeded:dwEDX:0
    PumaStateCtrl::GetMaximumFrequencyInMHz()--Calling GetCPUID succeeded
    get max freq--EDX register of function 4: 0 2nd byte: 0
    Setting P-state is NOT safe
    void PSC::ApplyAllPStates(const PStates &) p-state index:1
    void PSC::ApplyAllPStates(const PStates &) p_pstateCurrent's address:00000000024973D0
    GetPStateFromMSR(...) for p-state #1:
    Reading from MSR succeeded
    GetPStateFromMSR(...)--FID:12 DivID:1 VID:48
    PState::AssignChangesToPstateFromMSR(PState & r_pstateFromMSR)
    setVidAndFrequencyForPState_Puma
    PumaStateCtrl::IsSafe(byVID:64, byFrequencyID:12, byDivisorID:1)--begin
    Resulting freq in MHz is:1000, VID is:64
    PumaStateCtrl::GetCPUID--Got function for CPUID
    PumaStateCtrl::GetCPUID--Calling CPUID succeeded:dwEDX:0
    PumaStateCtrl::GetMaximumFrequencyInMHz()--Calling GetCPUID succeeded
    get max freq--EDX register of function 4: 0 2nd byte: 0
    Setting P-state is NOT safe
    GetPStateFromMSR(...) for p-state #1:
    Reading from MSR succeeded
    GetPStateFromMSR(...)--FID:12 DivID:1 VID:48
    PState::AssignChangesToPstateFromMSR(PState & r_pstateFromMSR)
    setVidAndFrequencyForPState_Puma
    PumaStateCtrl::IsSafe(byVID:64, byFrequencyID:12, byDivisorID:1)--begin
    Resulting freq in MHz is:1000, VID is:64
    PumaStateCtrl::GetCPUID--Got function for CPUID
    PumaStateCtrl::GetCPUID--Calling CPUID succeeded:dwEDX:0
    PumaStateCtrl::GetMaximumFrequencyInMHz()--Calling GetCPUID succeeded
    get max freq--EDX register of function 4: 0 2nd byte: 0
    Setting P-state is NOT safe
    void PSC::ApplyAllPStates(const PStates &) p-state index:2
    void PSC::ApplyAllPStates(const PStates &) p_pstateCurrent's address:00000000024973E0
    GetPStateFromMSR(...) for p-state #2:
    Reading from MSR succeeded
    GetPStateFromMSR(...)--FID:12 DivID:2 VID:60
    PState::AssignChangesToPstateFromMSR(PState & r_pstateFromMSR)
    setVidAndFrequencyForPState_Puma
    PumaStateCtrl::IsSafe(byVID:64, byFrequencyID:12, byDivisorID:2)--begin
    Resulting freq in MHz is:500, VID is:64
    PumaStateCtrl::GetCPUID--Got function for CPUID
    PumaStateCtrl::GetCPUID--Calling CPUID succeeded:dwEDX:0
    PumaStateCtrl::GetMaximumFrequencyInMHz()--Calling GetCPUID succeeded
    get max freq--EDX register of function 4: 0 2nd byte: 0
    Setting P-state is NOT safe
    GetPStateFromMSR(...) for p-state #2:
    Reading from MSR succeeded
    GetPStateFromMSR(...)--FID:12 DivID:2 VID:60
    PState::AssignChangesToPstateFromMSR(PState & r_pstateFromMSR)
    setVidAndFrequencyForPState_Puma
    PumaStateCtrl::IsSafe(byVID:64, byFrequencyID:12, byDivisorID:2)--begin
    Resulting freq in MHz is:500, VID is:64
    PumaStateCtrl::GetCPUID--Got function for CPUID
    PumaStateCtrl::GetCPUID--Calling CPUID succeeded:dwEDX:0
    PumaStateCtrl::GetMaximumFrequencyInMHz()--Calling GetCPUID succeeded
    get max freq--EDX register of function 4: 0 2nd byte: 0
    Setting P-state is NOT safe
    void PSC::ApplyAllPStates(const PStates &) p-state index:3
    void PSC::ApplyAllPStates(const PStates &) p_pstateCurrent's address:0000000000000000
    void PSC::ApplyAllPStates(const PStates &) p-state index:4
    void PSC::ApplyAllPStates(const PStates &) p_pstateCurrent's address:0000000000000000
    void PSC::ApplyAllPStates(const PStates &) p-state index:5
    void PSC::ApplyAllPStates(const PStates &) p_pstateCurrent's address:0000000000000000
    void PSC::ApplyAllPStates(const PStates &) p-state index:6
    void PSC::ApplyAllPStates(const PStates &) p_pstateCurrent's address:0000000000000000
    void PSC::ApplyAllPStates(const PStates &) p-state index:7
    void PSC::ApplyAllPStates(const PStates &) p_pstateCurrent's address:0000000000000000
    
     
  7. 970261

    970261 Scribbler - Standard Member

    Messages:
    334
    Likes Received:
    0
    Trophy Points:
    31
    ...wait, is the RM-70 an Turion Ultra? never bothered to check, but...that MIGHT the problem...

    tired atm from work...
     
  8. there148

    there148 Pen Pal - Newbie

    Messages:
    19
    Likes Received:
    0
    Trophy Points:
    5
    yep this program doesnt work with rm70. overvoltage protection window keeps popping up.
     
  9. Mr.Systematic

    Mr.Systematic Pen Pal - Newbie

    Messages:
    15
    Likes Received:
    0
    Trophy Points:
    6
    The RM-70 may be a Greif (griffin) CPU but if you look here: http://products.amd.com/en-us/NotebookCPUResult.aspx
    you see that that "X2" of RM-70's processor name is NOT suffixed by "Ultra" so it is currently not supported.

    The "p-state 0 for core 0 is not set because of overvoltage protection: the core voltage is too high for the core frequency" seems to be a "falsche Fehlermeldung" (=wrong error message) because the unknown CPU is not handled correctly.

    Doesn't RMClock (www.rightmark.org) work with this type of CPU? I am relatively sure it would. If not I can think about supporting it.
     
  10. there148

    there148 Pen Pal - Newbie

    Messages:
    19
    Likes Received:
    0
    Trophy Points:
    5
    hi

    the rm series is just a puma variant with a smaller l2 cache, ie 1mb instead of 2mb as seen in the ultra versions. it has all the features of the ultra, 3 step cpu throttle(500mhz, 1000mhz, 2000mhz), the independent core voltage control and hypertransport 3.

    no none of the cpu voltage program work with this processor. rmclock, notebook hardware control, crystalcpuid. the only software to work with this is the amd overdrive version 2.1.4 but that one is too resource intensive to be of any use. please consider adding support for the rm because these cpu are also extremely hot when under load. i have seen 90c just playing wow.
     

Share This Page