Monitoring Temps?

[RubberShoes]

Disclaimer: I'm rather new at all this, please bear with me and feel free to heckle the **** out of me for misstating something.

Spent the weekend rebuilding my hackintosh and got my 3770K running smoothly on my GA-Z77X-UP4 TH and integrated HD 4000 graphics acceleration running on 10.8 with the newest Multibeast/Chimera (was previously using Lion's Multibest which screwed some things up, namely sleep)

Overall everything is great!

However, I installed iStat Menus 3.something and it's reporting everything accurately except temperatures. It only shows Hard drive temps.

I remember having HWMonitor at some point on my previous installation, but now with my configuration of Multibeast 5.0.2 and the UP4 TH I seem to not have it or any idea if I should install FakeSMC or what to get this feature?

tl;dr

How do I enable monitoring of system temps like CPU/GPU and RAM in iStat or any OS X program for that matter?

Thanks for the help!

-
RS

 

[vanwinkle]

Download MultiBeast 5.0.2 for Mountain Lion, and install the following on your system:

FakeSMC
FakeSMC Plugins: Motherboard Plugins
FakeSMC Plugins: HWMonitor Application

The last one is actually an application that gets installed on your Applications folder, called HWMonitor.app. Running it creates a tab on your top toolbar that displays all your motherboard temps.

If you have a Radeon or Nvidia video card, you can install the Radeon or Nvidia plugin, also.

 

[RubberShoes]

Thank you. I installed those and now I have monitoring temps but now, at least on my mono (Z77X-UP4 TH) I now have no working sleep anymore.

I know this is what caused the sleep issues because I woke the machine up from sleep to read this solution.

I'm really angry at myself because I didn't think something this trivial would throw my machine off, so I didn't back it up.

Thanks for the response, and does anybody know how I could enable sleep again? It was working perfectly before based on these settings:

http://www.tonymacx86.com/mountain-lion-desktop-guides/67883-guide-ga-z77x-up4-th-i5-2500k.html

Except ignoring any HD3000/Sandy Bridge customizations because I'm on a 3770K.

 

[Asus-Freak]

Does sleep/wake work OK from the apple menu?

 

[RubberShoes]

No. It turns the display off and never actually sleeps and I have to force restart it to bring it back again.

What do?

 

[Asus-Freak]

Not sure, sleep is ofter an pain to figure out, so many variables... I had a machine doing the same thing and found out the problem was my Sony Bluray drive. Replaced it with a Liteon DVD and resolved the issue.

 

[Asus-Freak]

You might start by looking at the console logs and look for. Wake reason:

 

[Hybrid]

No. It turns the display off and never actually sleeps and I have to force restart it to bring it back again.

What do?

I think I have the same problem - sleep worked fine (well mostly, aside from occasional times where it wouldn't wake at all) in 10.6.6.

I just updated to 10.8.1 on a spare drive and I didn't test sleep before installing the FakeSMC and HWMonitor extras in Multibeast. Now when I try to put it to sleep, it just hangs like you describe.

@kduvernay: I looked in my console for "wake reason" but it doesn't appear at all, maybe because it has never slept properly.

This is what I see in the console when I put it to sleep:

28/08/12 2:42:51.255 PM WindowServer[81]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
28/08/12 2:42:51.273 PM loginwindow[58]: find_shared_window: WID -1
28/08/12 2:42:51.273 PM loginwindow[58]: CGSGetWindowTags: Invalid window 0xffffffff
28/08/12 2:42:51.273 PM loginwindow[58]: find_shared_window: WID -1
28/08/12 2:42:51.273 PM loginwindow[58]: CGSSetWindowTags: Invalid window 0xffffffff
28/08/12 2:42:51.517 PM WindowServer[81]: Created shield window 0x5d for display 0x2b3c350d
28/08/12 2:42:51.521 PM WindowServer[81]: Created shield window 0x5e for display 0x2b3c350c
28/08/12 2:42:51.521 PM WindowServer[81]: device_generate_desktop_screenshot: authw 0x7f9bad036b40(2000), shield 0x7f9ba9c1c0f0(2001)
28/08/12 2:42:51.580 PM WindowServer[81]: device_generate_desktop_screenshot: authw 0x7f9bad036b40(2000), shield 0x7f9ba9c1c0f0(2001)
28/08/12 2:42:51.604 PM WindowServer[81]: device_generate_lock_screen_screenshot: authw 0x7f9bad036b40(2000), shield 0x7f9ba9c1c0f0(2001)
28/08/12 2:49:00.000 PM bootlog[0]: BOOT_TIME 1346129340 0
28/08/12 2:49:16.000 PM kernel[0]: Darwin Kernel Version 12.1.0: Tue Aug 14 13:29:55 PDT 2012; root:xnu-2050.9.2~1/RELEASE_X86_64

As you can see, it starts preparing for sleep and then.... nothing, until I power it off and it reboots automatically. The reboot looks pretty normal and I don't see any errors or warnings. It's weird... When it starts again, OS X restores what I had open before sleeping.

I'm wondering if I should somehow try removing the FakeSMC and hardware monitoring kexts? I'd much rather have sleep than monitoring (although both worked in 10.6.6 so that would be nice in 10.8...)

Thanks!

 

[RubberShoes]

Yes I too have nothing under "wake reason" and nothing particularly weird shows up in Console between hard restarts to bring it back to life.

I'm just reinstalling 10.8.1 now and I'm avoiding FakeSMC and I'm curious is this an issue for a lot of people?

But for future reference, how would one uninstall FakeSMC? I'm reinstalling because restarts, startups and shutdowns have all been affected by this change.

In all, avoid anything related to fakeSMC for the Z77X0UP4 TH mobo?

 

[Going Bald]

FakeSMC is required to allow you to boot the hackintosh in the first place. What you can do though, is open finder, navigate to S/L/E and delete FakeSMC.kext. empty trash to make sure it is gone. Then run MultiBeast and select only fakesmc.kext to install and run it. Repair permissions.
Reboot with -f boot flag.

This gets rid of the plugins that you installed and puts the original fakesmc back in place.

You could probably just run MB and select fakesmc and install and it would replace the kext in S/L/E, but if you delete it first and then check to make sure it is back after install, then you know you replaced it.