The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    rmClock

    Discussion in 'Apple and Mac OS X' started by masterchef341, Jan 5, 2008.

  1. masterchef341

    masterchef341 The guy from The Notebook

    Reputations:
    3,047
    Messages:
    8,636
    Likes Received:
    4
    Trophy Points:
    206
    im not getting good results with rmclock?

    is this an apple hardware problem? anyone else share this?

    how do you undervolt your macbook pro in both windows and osx?
     
  2. mrg666

    mrg666 Notebook Evangelist

    Reputations:
    147
    Messages:
    376
    Likes Received:
    0
    Trophy Points:
    30
    The only software, that I know, for undervolting the Powerbook in MacOSX is CoolBook. But new Macbook Pro's have Santa Rosa chipset, which has more advanced Speedstep, EIST characteristics than previous generation Intel chipsets. The Santa Rosa platform scales the FSB as well as CPU multiplier and core voltage but previous generation chipsets were only scaling the multiplier and voltage. I am not sure how CoolBook would work on Macbook Pro, since I do not have access to MacOSX on any Santa Rosa notebook. On the Windows platform, the developers of RMClock were still working on Santa Rosa compatibility and RMClock was not working well on that platform last time I checked. I am eagerly waiting for the Santa Rosa compatible version of RMClock for my Vostro 1500. I wish they would have released a MacOSX version as well.
     
  3. mrg666

    mrg666 Notebook Evangelist

    Reputations:
    147
    Messages:
    376
    Likes Received:
    0
    Trophy Points:
    30
    I was checking the RMClock forum and I saw that RMClock 2.35 Beta 2 now supports the Santa Rosa platform. I downloaded and tested on my Vostro 1500 with T5470 processor: IT IS WORKING!

    I did the followings.
    - selected CPU type as "Mobile" in Advanced CPU Settings.
    - in Profile selection, chose "Performance on demand" for AC Power and Battery at both Current and Startup lines.
    - noticed that there are now two more performance states
    --- SuperLFM, scales FSB down to 100 from 200 (i.e. 4x200 -> 4x100) when there is no CPU demand​
    --- IDA, Intel Dynamics Acceleration, higher multiplier when only single threaded applications are running​
    - set the VID to 0.9 at SuperLFM and lowest FID and tested with orthos by disabling the other states in Performance on Demand section
    - set the VID to 0.925 to last two states after testing for stability with orthos. RMClock adjusted the VID for the intermediate states.
    - checked the "Use P-state transitions" in Performance on demand section for both AC power and Battery.
    - checked "start minimized to tray" and "run at windows startup" in settings.

    I tested the new settings with Kill-a-Watt power measurement device on the wall.
    CPU Idle:
    With RMClock = 27W
    Without RMClock = 30W

    Orthos running on both cores:
    With RMClock = 40W
    Without RMClock = 50W

    I have not measured the battery life. But I think there will be about minimum 10% and maximum 20% longer battery life according to above wattage measurements. Last but most importantly, the CPU temperature reduced to 63C from 75C while running Orthos as measured by CoreTemp. There is not much change in the idle CPU temperature.

    That is it for now, please let me know if I missed any details.
     
  4. kgeier82

    kgeier82 Notebook Deity

    Reputations:
    129
    Messages:
    757
    Likes Received:
    0
    Trophy Points:
    30
    RMCLOCK working fine here in xp.

    i had some issues when i booted up my osx partition, and used parallels to boot into my VM/bootcamp. that was interesting.