Jump to content

1,165 posts in this topic

Recommended Posts

Advertisement

Can you add a monitor for hard drive temperatures like this one in iStat ?

 

HWMonitor work on MSI P55-GD65 + i7-870, doesn't works on P8Z68 Deluxe Gen3 + i5-2500K

post-250582-0-53400800-1328278559_thumb.png

Share this post


Link to post
Share on other sites

Can you add a monitor for hard drive temperatures like this one in iStat ?

 

Maybe in future.

 

HWMonitor work on MSI P55-GD65 + i7-870, doesn't works on P8Z68 Deluxe Gen3 + i5-2500K

 

P8Z68 - it is Asus mobo? Asus usually using Winbond chip for monitoring. Show me your kernel log please.

 

Also I could see your CPU have 4 cores and IntelThermal erroneously shows 10.

Share this post


Link to post
Share on other sites

Works on my notebook (NvClock, IntelThermal, SuperIO and Winbond).

I have my CPU and GPU shown in HWMonitor, does it need to show some more sensors from the Winbond.kext? (like Mobo sensors)

It seems like it doesnt load on boot (not shown in kernel.log) or it loads but doesnt work, i have an ASUS notebook,

 

Cheers

 

Thanks for your work mozodojo :)

Share this post


Link to post
Share on other sites

Works on my notebook (NvClock, IntelThermal, SuperIO and Winbond).

I have my CPU and GPU shown in HWMonitor, does it need to show some more sensors from the Winbond.kext? (like Mobo sensors)

It seems like it doesnt load on boot (not shown in kernel.log) or it loads but doesnt work, i have an ASUS notebook,

 

Cheers

 

Thanks for your work mozodojo :)

 

If one of superio plugins detected something, in kernel log should be a message starting with It87x, W836x, F718x or NSCPC8729x.

 

Nothing in kernel log?

Share this post


Link to post
Share on other sites

I want to introduce new "old" opensource fakemsc project with hardware monitoring plugins with new GUI utility - HWMonitor.

 

Please, leave requests and issues on project's home on GitHub: https://github.com/Mozodojo/HWSensors

 

Use GitHab utility or other git tool to clone repository on your computer. Project includes sources, installer and compiled binaries. If you want manually install kexts they are located in "Binaries" folder. Installer package located in "Installer" folder.

 

Project will not be in existence without revolutional SMC emulator (fakesmc) by netkas. Special thanks to slice and user-sse2 for plugins. Big part of this project based on OpenHardwareMonitor opensource project by Michael Möller.

 

How does your FakeSMC hardware sensors iteration differ from that of Slice's FakeSMC branch? Also, where is the IntelCPUMonitor.kext? Thank You.

Share this post


Link to post
Share on other sites

If one of superio plugins detected something, in kernel log should be a message starting with It87x, W836x, F718x or NSCPC8729x.

 

Nothing in kernel log?

 

if i run it with It87x, it shows unsuported chipset detected, with W826x doesnt show anything and havent tried the last two.

NvClock and IntelThermal show that are loaded and working in kernel.log. Anything i should try?

 

Cheers

Share this post


Link to post
Share on other sites

if i run it with It87x, it shows unsuported chipset detected, with W826x doesnt show anything and havent tried the last two.

NvClock and IntelThermal show that are loaded and working in kernel.log. Anything i should try?

 

Cheers

 

Yes you could try to install all of the Super I/O plugins together. If you're lucky you'll get monitoring.

Share this post


Link to post
Share on other sites

Looks like this with Z68XP-UD4. Should have only 4 core temperatures and multipliers are not showing. Cpu heatsink temperature is really Ambient, Motherboard should be Cpu temperature and 3rd sensor that now says Ambient is probably really disconnected, that 25 C never changes on Windows or OS X.

 

post-375259-0-62101700-1328307699_thumb.png

Share this post


Link to post
Share on other sites

Is there a proper way to install this via the installer. I tried installing it over my existing FakeSMC kexts and it didnt reboot after the install. Booting into windows and replacing the old kexts allowed me to boot again.

 

Thanks!

Share this post


Link to post
Share on other sites

Looks like this with Z68XP-UD4. Should have only 4 core temperatures and multipliers are not showing. Cpu heatsink temperature is really Ambient, Motherboard should be Cpu temperature and 3rd sensor that now says Ambient is probably really disconnected, that 25 C never changes on Windows or OS X.

 

post-375259-0-62101700-1328307699_thumb.png

 

I could add your Super I/O's profile with proper temperatures translation into kext config. But first I should to know which chip manufacturer and revision you have. Show me your kernel log, please.

 

Is there a proper way to install this via the installer. I tried installing it over my existing FakeSMC kexts and it didnt reboot after the install. Booting into windows and replacing the old kexts allowed me to boot again.

 

Thanks!

 

Remove old FakeSMC before instilling new one. Just move it to trash and run installer.

Share this post


Link to post
Share on other sites

Hi Mozo!

 

In kernel.log i get this message:

W836x: [Warning] wrong vendor chip ID=0xb3 REVISION=0x53 VENDORID=0xffff

My sensor-chip is Winbond W83667HG-B.

 

post-21904-0-66483900-1328335012_thumb.png

 

Thank you.

Share this post


Link to post
Share on other sites

Also, where is theIntelCPUMonitor.kext? Thank You.

Also my question.

I use now the new fakesmc and started with the ITEIT87x.kext first

But said cant load by problem in the depenences. Can it be that it also needs the other SuperIOFamily.kext installed too?

After installing both it worked.

Which plugin is needed to show that seen multipliers?

Share this post


Link to post
Share on other sites

Also my question.

I use now the new fakesmc and started with the ITEIT87x.kext first

But said cant load by problem in the depenences. Can it be that it also needs the other SuperIOFamily.kext installed too?

After installing both it worked.

 

SuperIOFamily.kext is necessary to run superio plugins. If you manually install kexts you should know what you do. Otherwise use installer.

 

Which plugin is needed to show that seen multipliers?

 

IntelThermal

 

Hi Mozo!

 

In kernel.log i get this message:

W836x: [Warning] wrong vendor chip ID=0xb3 REVISION=0x53 VENDORID=0xffff

My sensor-chip is Winbond W83667HG-B.

 

post-21904-0-66483900-1328335012_thumb.png

 

Thank you.

 

wrong vendor error - will think about it. Try the new version I'll upload today later.

Share this post


Link to post
Share on other sites

I could add your Super I/O's profile with proper temperatures translation into kext config. But first I should to know which chip manufacturer and revision you have. Show me your kernel log, please.

 

This what you need ?

Feb  4 13:25:37 localhost kernel[0]: IT87x: based on code from Open Hardware Monitor project by Michael Möller (C) 2010
Feb  4 13:25:37 localhost kernel[0]: IT87x: mozodojo (C) 2011
Feb  4 13:25:37 localhost kernel[0]: IT87x: found ITE IT8728F

Share this post


Link to post
Share on other sites

This what you need ?

Feb  4 13:25:37 localhost kernel[0]: IT87x: based on code from Open Hardware Monitor project by Michael Möller (C) 2010
Feb  4 13:25:37 localhost kernel[0]: IT87x: mozodojo (C) 2011
Feb  4 13:25:37 localhost kernel[0]: IT87x: found ITE IT8728F

 

I added your chipset profile into plugin. Check the repository.

Share this post


Link to post
Share on other sites

Hi mozo

Most new Asus boards have Nuvoton IO chips, owned by Winbond. Do you have any plans to add support for these? Data sheets are on the net, the open source Hw monitor code does contain support for them. I'd be happy to help with testing, thanks for all your work so far

Share this post


Link to post
Share on other sites

Hi mozo

Most new Asus boards have Nuvoton IO chips, owned by Winbond. Do you have any plans to add support for these? Data sheets are on the net, the open source Hw monitor code does contain support for them. I'd be happy to help with testing, thanks for all your work so far

 

Why not? Will add it later.

Share this post


Link to post
Share on other sites

I added your chipset profile into plugin. Check the repository.

 

Now Cpu heatsink is showing value that is labeled as System in Windows programs, Motherboard is showing that disconnected sensor and real Cpu heatsink is missing. I had Prime95 running in background and I know that real Vcore value on full load is 1.380 V, correct Dimm voltage is probably 1.64 V, it is set to 1.65 V in bios. I have a feeling that now only temperatures of first two cores are shown two times, third core on my cpu always runs warmer than others. Fan speed reading and Radeon temperature seem to be correct.

 

post-375259-0-06107700-1328362537_thumb.png

 

Here is same situation with old FakeSMC:

 

post-375259-0-67803400-1328364127_thumb.png

 

Voltages are wrong here also but temperatures are correct because I rearranged names in IT87x.kext

Info.plist.zip

Share this post


Link to post
Share on other sites

Now Cpu heatsink is showing value that is labeled as System in Windows programs, Motherboard is showing that disconnected sensor and real Cpu heatsink is missing. I had Prime95 running in background and I know that real Vcore value on full load is 1.380 V, correct Dimm voltage is probably 1.64 V, it is set to 1.65 V in bios. I have a feeling that now only temperatures of first two cores are shown two times, third core on my cpu always runs warmer than others. Fan speed reading and Radeon temperature seem to be correct.

 

post-375259-0-06107700-1328362537_thumb.png

 

Here is same situation with old FakeSMC:

 

post-375259-0-67803400-1328364127_thumb.png

 

Voltages are wrong here also but temperatures are correct because I rearranged names in IT87x.kext

Info.plist.zip

 

DIMM voltage is really could be something else. Could you run OpenHardwareMonitor in Windows and get a screenshot?

Share this post


Link to post
Share on other sites

Would be extra nice, mozodojo, if you add,

that your version is not compatible with slice´s project on projectosx ( intelcpumonitor !!!)

it totally bombed my system and as fakesmc is urgently needed to start, its a mess to repair.

 

and i like to install it on /extra, what your installer doesnt allow.

Share this post


Link to post
Share on other sites

DIMM voltage is really could be something else. Could you run OpenHardwareMonitor in Windows and get a screenshot?

 

I see now what is happening, you are using channels 1 & 2 as Vcore and Dimm voltage, but they are actually on channels 6 & 7.

post-375259-0-70992800-1328370919_thumb.png

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By kevin_1351
      tl;dr: VirtualSMC causes me a flood of log messages and correlated cpu spikes. FakeSMC doesn't.
       
      Hi, I have almost finalized my Huawei Matebook X Pro Opencore setup and everything is working very well besides wifi/bt ofc (which is about to change).
       
      However, I noticed how the cpu usage sometimes went up a little and when looking at the Console I could see a never-ending flood of:
      default 14:05:05.983292+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:05.982975+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:05.982996+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:06.985932+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:06.985949+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:06.986134+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:39.426574+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:39.426729+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:39.426585+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:41.431085+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:41.431097+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:41.431246+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:42.433068+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:42.433227+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:42.433078+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:43.434453+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:43.434465+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:43.434622+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:44.436155+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:44.436166+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0  
      As you can see, multiple of these per second. Another guy with the same computer is also having this issue and posted a dsdt change to fix it. This fix didn't solve anything though
      He tried to limit the Notify call by implementing a state change requirement before calling Notify.
       
      Here is the original acpi:
      Scope (_SB) { Device (LID) { Name (_HID, EisaId ("PNP0C0D") /* Lid Device */) // _HID: Hardware ID Method (_LID, 0, NotSerialized) // _LID: Lid Status { Local0 = One Local0 = ^^PCI0.LPCB.EC0.RPIN (0x05, 0x06) If ((Local0 == 0x55)) { Local0 = Zero } Else { Local0 = One } ^^PCI0.GFX0.CLID = Local0 Return (Local0) } } Device (PWRB) { Name (_HID, EisaId ("PNP0C0C") /* Power Button Device */) // _HID: Hardware ID Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0B) } } } Scope (_SB.PCI0.LPCB.EC0) { Method (_Q81, 0, NotSerialized) // _Qxx: EC Query, xx=0x00-0xFF { Local0 = ^^^^LID._LID () If ((Local0 == Zero)) { ADBG ("LID-OFF") SGOV (0x02030009, Zero) SGOV (0x02060000, Zero) } Else { ADBG ("LID-ON") SGOV (0x02030009, One) SGOV (0x02060000, One) Notify (ALSD, 0x80) // Status Change } Notify (LID, 0x80) // Status Change } } Which he changed to: 
      Scope (_SB) { Device (LID) { Name (_OLD, One) // assuming everything else.. the lid should start open? Name (_HID, EisaId ("PNP0C0D") /* Lid Device */) // _HID: Hardware ID Method (_LID, 0, NotSerialized) // _LID: Lid Status { Local0 = One Local0 = ^^PCI0.LPCB.EC0.RPIN (0x05, 0x06) If ((Local0 == 0x55)) { Local0 = Zero } Else { Local0 = One } Return (Local0) } } Device (PNLF) { Name (_HID, EisaId ("APP0002")) // _HID: Hardware ID Name (_CID, "backlight") // _CID: Compatible ID Name (_UID, 0x0A) // _UID: Unique ID Name (_STA, 0x0B) // _STA: Status } Device (PWRB) { Name (_HID, EisaId ("PNP0C0C") /* Power Button Device */) // _HID: Hardware ID Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0B) } } } Scope (_SB.PCI0.LPCB.EC0) { Method (_Q81, 0, NotSerialized) // _Qxx: EC Query, xx=0x00-0xFF { Local0 = ^^^^LID._LID () If ((Local0 == Zero)) { ADBG ("LID-OFF") SGOV (0x02030009, Zero) SGOV (0x02060000, Zero) } Else { ADBG ("LID-ON") SGOV (0x02030009, One) SGOV (0x02060000, One) Notify (ALSD, 0x80) // Status Change } If ((^^^^LID._OLD != Local0)) { Notify (LID, 0x80) // Status Change ^^^^LID._OLD = Local0 } } } Besides me not seeing any reason to declare _OLD in LID. The idea itself shouldn't be too bad right? Well, as I said, his fix didn't work.
       
      In fact, to prove that Method _Q81 doesn't have anything to do with the issue at all, I created a Clover/Opencore patch to change _Q81 to XQ81. This resulted in my lid not working at all of course, but the log flooding still persisted!
      So _Q81 doesn't have anything to do with the issue afaik.
       
      Now, further Google searches led me to a chinese post where he tied the issue to VirtualSMC. And indeed, by migrating to FakeSMC the issue is no more.
       
      Unfortunately, I'm very fond of VirtualSMC for various reasons. So I would very much like to keep it. If not I'd have to implement the old way of doing Battery monitoring etcetc. Which isn't very elegant and update proof as it requires DSDT patching.
       
      So, I do believe that the issue may very well be in the DSDT code, perhaps in the ambient light part. I'm not very skilled at this and just started studying the ACPI spec 3 days ago.
       
      Could someone please help me out? Thanks a lot in advance
       
       
      origin.zip
      OC.zip
    • By Slice
      Guys,
      Don't mix 6.18 and 3.41.
       
      There are three different projects for monitoring temperatures, voltages, fans speed and other hardware parameters:
      Initially it was FakeSMC with plugins for producing SMC keys for hardware parameters for different hardware. But sometimes ago Kozlek separated own version of FakeSMC and producing new set of plugins while I stay with good working version 3. So..
      1. FakeSMC v3 with Hardware Sensors3  which I still supported.
      2. FakeSMC v6 (rev1800) by Kozlek and supported by Rehabman. AFAIK both are abandoned and the project is not supported. Or may be maintained by coauthors.
      3. New VirtualSMC by vit9696 with own set of sensors kexts. It depends on Lilu.kext. The project is in active development.
      All three project have incompatible interfaces sensors<->SMC so they are incompatible with each other.
       
      There are applications for monitoring hardware parameters and they commonly depends on these projects.
      1. iStat, iStatMenu, iStatPro compatible with real Macs because they use SMC keys just like those presents in real Macs.
      2. HWMonitorSMC by Navi (initial codes from Kozlek)  used in my HWSensors3.
      3. HWMonitor by Kozlek with graphics like in IntelPowerGadget used in his HWSensors version.
      4. HWMonitorSMC2 by Vector_Sigma tends to be universal supporting all project. It also may use sensors information produces by Apple graphics and by IntelPowerGadget.
       
      Let us discuss here differences and common ideas for this projects.
       
    • By Slice
      This thread devoted to share information about different SMC keys found or investigated anywhere.
       
      What are they?
      SMC keys is a somehow language to speak between macOS and hardware microcontroller presented in real Mac and absent in Hackintosh.
      They inform macOS about Hardware ID and current status. Moreover macOS can write something through SMC protocol to control hardware.
      FakeSMC ( ©Netkas) is the driver to emulate this microcontroller on PC having no such device which is necessary to boot macOS here.
      But FakeSMC contain only ~20 keys while real Mac answers ~200 keys.
      Some keys we added by HWSensors project reporting temperatures, FAN speeds, voltages etc.
      Some keys are model dependent was added by Clover to be sure if user changed model in GUI then corresponding keys will be changed automatically.
      Clover sets
      LogDataHub(&gEfiMiscSubClassGuid, L"RPlt", &gSettings.RPlt, 8);
      LogDataHub(&gEfiMiscSubClassGuid, L"RBr", &gSettings.RBr, 8);
      LogDataHub(&gEfiMiscSubClassGuid, L"EPCI", &gSettings.EPCI, 4);
      LogDataHub(&gEfiMiscSubClassGuid, L"REV", &gSettings.REV, 6);
      LogDataHub(&gEfiMiscSubClassGuid, L"BEMB", &gSettings.Mobile, 1);
      BEMB - is a mobility sign. =0 -desktop, =1 - mobile.
      REV - SMC hardware revision, changes sometimes with Apple updates.
      RPlt, RBr and EPCI is hardware capabilities, noticed used in Intel HD drivers.
       
      Structure.
      All SMC keys consists of name 4 ascii chars as 32bit integer, type and value.
      Types:
       "flag", len 1
       "ui8 ", len 1
       "ui16", len 2
       "sp78", len 2
       "ui32", len 4
      "fp2e", len 2
      "fpe2", len 2
      "{rev", and others...
       
      List of known keys
      SMC_list.plist.zip
      More keys will be discussed in the thread
       
       
      Feel free to share you knowledge and ask about noticed keys.
×