Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About twotimes

  • Rank
    InsanelyMac Protégé
  1. I've been playing around with my setup (3770k - gigabyte z77x-ud5h - Sapphire 7970 with GOP-capable bios), dual booting between OSX (Mavericks/Yosemite) and Windows 8.1. I noticed that the power consumption measured at-the-wall is lower for Windows 8.1. I blame it mainly on inflexible clock/voltage management of the AMD 7970 GPU under OSX. Below are some numbers. OSX idle power use: dual display setup, HDMI+DVI - 105 W single display setup, HDMI only - 71W Win 8.1 idle power use: dual display setup, HDMI+DVI - 79 W (vCore=0.95V, CoreFreq=300MhZ, MemFreq=450MhZ) single display setup, HDMI only - 61W (vCore=0.85V, CoreFreq=300MhZ, MemFreq=150MhZ) In Windows 8.1 I can monitor/control GPU core and memory clock frequencies and voltages with tools like MSI Afterburner and Catalyst Control Center. Seems like the idle clock used by OSX are the default max values defined by vBios (1050MhZ core/1500MhZ mem). Is there any way to monitor/change the clock and voltage values under OSX for AMD GPUs?
  2. my bad, had too much focus on the word "kernel" lately . Anyway, AFAIK Atom270 has only one physical core with HT (thus the second "core" in the istat). The only process causing the cpu hog is kernel_task, constantly loading one of the "cores" to 70%
  3. Noticed one strange thing: for some reason i always get one of the cpu's "kernels" loaded at 100%, according to the iStat menus. Kernel_task eats up the entire virtual kernel of Atom270. Maybe I just missed something during/post the installation, though.
  4. I've tried installing Leopard on Sony Vaio FW 140, but although the installation went well (i used iDeneb 1.3), most of the peripherials weren't detected (no lan/wifi/audio). But the dealbreaker is the Intel 4500 graphics: there's neither driver nor workaround available so far to circumvent the 1024x768 resolution... So i didn't even bother looking for drivers for other hardware parts- it's no use trying when you're stuck at 1024x768 on 1600x900 screen.