Jump to content

1,165 posts in this topic

Recommended Posts

Hello,

 

W83627DHG device id is 0xA020

P5B hardware report 0xA023.

Fan and Voltage stop working a week ago.

 

Regards

Share this post


Link to post
Share on other sites
Advertisement

Hello,

 

W83627DHG device id is 0xA020

P5B hardware report 0xA023.

Fan and Voltage stop working a week ago.

 

Regards

 

Show me, please, your ioreg with the latest revision drivers

Share this post


Link to post
Share on other sites

 

Thanks for this, now HWS is working here like a charm.

 

10fz607.jpg

 

First, this is really a great piece of software, but it needs a better description in the OP, so people know how to use it. ;)

 

Second, in a earlier version I could check the CPU MHz, but now it's missing?! Or just me doing something wrong?

 

Mhz showing IntelCPUMonitor that's not included in my branch.

 

What does it means "better description in the OP"?

Share this post


Link to post
Share on other sites

Show me, please, your ioreg with the latest revision drivers

 

Here's the file.

 

I forgot to say that since last version all power supply report 0 Volts.

 

So, i've solved Fan trouble. Missing FANINLIMIT in plist, i put 5.

and do that

 

UInt8 W836x::tachometerSensorsLimit()

{

return 5; //fanLimit;

}

 

Working but not really beautiful ! must investigate.

 

Try to look at Voltage and report.

 

Regards

Mac Pro de Frédéric.zip

Share this post


Link to post
Share on other sites

perfect as usual ;-)

 

Do you still see this "wrong vendor" warning in kernel.log?

 

Here's the file.

 

I forgot to say that since last version all power supply report 0 Volts.

 

So, i've solved Fan trouble. Missing FANINLIMIT in plist, i put 5.

and do that

 

UInt8 W836x::tachometerSensorsLimit()

{

return 5; //fanLimit;

}

 

Working but not really beautiful ! must investigate.

 

Try to look at Voltage and report.

 

Regards

 

The new revision should fix this problem. If it will be any problems please report back.

Share this post


Link to post
Share on other sites

Do you still see this "wrong vendor" warning in kernel.log?

 

 

 

The new revision should fix this problem. If it will be any problems please report back.

 

Hum there is a timing trouble ! if i remove trace iv'e added in this function it does not work. bool SuperIOMonitor::addTachometerSensors(OSDictionary *configuration)

 

i'll look at code in new version

 

Regards

Share this post


Link to post
Share on other sites

Do you still see this "wrong vendor" warning in kernel.log?

 

 

 

no errors

 

SuperIO: found Fintek F71869A on port=0x4e address=0x290

Share this post


Link to post
Share on other sites

Do you still see this "wrong vendor" warning in kernel.log?

 

 

 

The new revision should fix this problem. If it will be any problems please report back.

 

 

So i've test.

To make it work with winbond need to change many things.

First this in SuperIO.h

// Winbond

W83627DHG = 0xA023

 

After that, Kext is loaded and all power sensors working.

But still no Fans sensors, i've made some change to make it work.

 

You load value from Key "FANINLIMIT" witch is initialized with 0 in WinbondW836x-Info.plist

OSNumber* fanlimit = OSDynamicCast(OSNumber, configuration->getObject("FANINLIMIT"));

So first put 5. this is not enough to make it works.

 

Make some change in function:

bool SuperIOMonitor::addTachometerSensors(OSDictionary *configuration)

{

DebugLog("adding tachometer sensors...");

 

WarningLog("adding tachometer sensors... %d\n", tachometerSensorsLimit());

 

for (int i = 0; i < tachometerSensorsLimit(); i++) {

OSString* name = NULL;

 

char key[7];

 

snprintf(key, 7, "FANIN%X", i);

 

name = OSDynamicCast(OSString, configuration->getObject(key));

 

UInt64 nameLength = name ? name->getLength() : 0;

 

WarningLog("adding tachometer sensors... %d %f\n", i,readTachometer(i));

 

if (readTachometer(i) > 10 || nameLength > 0)

if (!addTachometer(i, (nameLength > 0 ? name->getCStringNoCopy() : 0)))

WarningLog("error adding tachometer sensor %d", i);

}

 

return true;

}

i've added two lines in red.

Call to ReadTachometer(i) it necessary to get success.

 

Seems to be timing trouble, just like i wrote a few post below.

 

Regards

Share this post


Link to post
Share on other sites

I still don´t get it ! :(

 

ioreg seems fine and Plugin loads correctly, but no multiplier and no hdd´s are shown! Fans and all other temps incl. GPU are just fine ... did you Guys install anything else beside new FakeSMC and plugins (e.g. Bresinks Hardwaremonitor, Temperature monitor, iStat, ...) ???

 

Cheers

 

Goron

Share this post


Link to post
Share on other sites

hello, the same for me with W83627DHG

 

behind this postet before:

SuperIO.h

// Winbond

W83627DHG = 0xA023

SuperIO: found Winbond W83627DHG on port=0x2e address=0x290

 

sinze i use this plugin i allways have to chance the Sensors Configursystem, FANIN1 to CPU

and FANINLIMIT to 2

 

with the older ones i could chose with TEMPIN 0/1 if want ambient or system chipset but never both.

 

here is my HWMonitor.txt from winxp hopefully you could use it

 

thx a lot as allways

post-282470-0-98837000-1331544890_thumb.png

HWMonitor.txt

hwm_smbus.txt

Share this post


Link to post
Share on other sites

hello, the same for me with W83627DHG

 

behind this postet before:

SuperIO.h

// Winbond

W83627DHG = 0xA023

SuperIO: found Winbond W83627DHG on port=0x2e address=0x290

 

sinze i use this plugin i allways have to chance the Sensors Configursystem, FANIN1 to CPU

and FANINLIMIT to 2

 

with the older ones i could chose with TEMPIN 0/1 if want ambient or system chipset but never both.

 

here is my HWMonitor.txt from winxp hopefully you could use it

 

thx a lot as allways

 

Thank you for your report. Also I see voltages is not correct. Will see today what could I do.

Share this post


Link to post
Share on other sites

kozlek-HWSensors-522c655

 

still wrong in SuperIO.h

// Winbond

W83627DHG = 0xA020 has to be 0xA023

 

buttons missing in HWMonitor and the same voltages as before

Share this post


Link to post
Share on other sites

HI! Can you help me to detect my mobility radeon 4570 on GPU stat? (id 95531002)

Thank you very much

Share this post


Link to post
Share on other sites

Thank you for your report. Also I see voltages is not correct. Will see today what could I do.

 

Hello,

 

Every thing is ok for Winbond.

Except Fan detection.

Must add line in red to make monitor see Fan. Timing trouble ?

 

bool SuperIOMonitor::addTachometerSensors(OSDictionary *configuration)

{

DebugLog("adding tachometer sensors...");

 

for (int i = 0; i < tachometerSensorsLimit(); i++) {

OSString* name = NULL;

 

char key[7];

 

snprintf(key, 7, "FANIN%X", i);

 

name = OSDynamicCast(OSString, configuration->getObject(key));

 

UInt64 nameLength = name ? name->getLength() : 0;

 

 

WarningLog("Reading tachometer sensor %d", readTachometer(i));

 

if (readTachometer(i) > 10 || nameLength > 0)

if (!addTachometer(i, (nameLength > 0 ? name->getCStringNoCopy() : 0)))

WarningLog("error adding tachometer sensor %d", i);

}

return true;

}

 

Regards

Share this post


Link to post
Share on other sites

 

 

Hello,

 

Every thing is ok for Winbond.

Except Fan detection.

Must add line in red to make monitor see Fan. Timing trouble ?

 

bool SuperIOMonitor::addTachometerSensors(OSDictionary *configuration)

{

DebugLog("adding tachometer sensors...");

 

for (int i = 0; i < tachometerSensorsLimit(); i++) {

OSString* name = NULL;

 

char key[7];

 

snprintf(key, 7, "FANIN%X", i);

 

name = OSDynamicCast(OSString, configuration->getObject(key));

 

UInt64 nameLength = name ? name->getLength() : 0;

 

 

WarningLog("Reading tachometer sensor %d", readTachometer(i));

 

if (readTachometer(i) > 10 || nameLength > 0)

if (!addTachometer(i, (nameLength > 0 ? name->getCStringNoCopy() : 0)))

WarningLog("error adding tachometer sensor %d", i);

}

return true;

}

 

Regards

 

Please check latest version, the problem shoud gone

Share this post


Link to post
Share on other sites

Hi kozlek, i would like to inform you that now, the gpu sensor works great here on my 9800gt GFX card.

 

Hi

the same problem here (8800gs g92)

gpu temp shows 15 should be something about 42-45

 

what change did you make???

new version of nvclockx or something else????

 

thank you for help

Share this post


Link to post
Share on other sites

Thanks, kozlek, plugins and app work well in my system with the only change of adding a spanish localization.

Share this post


Link to post
Share on other sites

Thanks, kozlek, plugins and app work well in my system with the only change of adding a spanish localization.

 

If you have translated HWMonitor, could you send me please your localization? I'll add it to the project

Share this post


Link to post
Share on other sites

Hello Kozlek

 

this is the French localization

 

 

 

 

"TEMPERATURES" = "ТЕMPERATURE";

"DRIVES TEMPERATURES" = "ТЕМPERATURE DD";

"SSD REMAINING LIFE" = "VIE RESTANTE SSD";

"MULTIPLIERS" = "МULTIPLICATEUR";

"FREQUENCIES" = "FRÉQUENCES";

"VOLTAGES" = "VOLTAGES";

"FANS" = "VENTILATEURS";

"CPU Heatsink" = "CPU Dissipateur";

"GPU %X Board" = "Carte VidÉo %X";

"GPU %X Core" = "Graphiques de Base %X";

"GPU %X Proximity" = "Capteur De Carte %X";

"Northbridge" = "Northbridge";

"System Chipset" = "Système Chipset";

"CPU Package" = "Processeur";

"CPU %X" = "Processeur %X";

"CPU Core %X" = "Core CPU %X";

"Fan %X" = "Ventilateur %X";

"CPU" = "Processeur";

"DIMM Modules" = "Modules de MÉmoire";

"Power/Battery" = "Alimentation / Batterie";

"Quit HWMonitor" = "Quiter HWMonitor";

"No sensors found" = "Il n'y a pas de capteurs disponibles";

French_Translation .txt

Share this post


Link to post
Share on other sites

Hello Kozlek

 

this is the French localization

 

 

Thank you! Added to the project.

 

bipffs.png

 

HWMonitor.app can`t start on my system

 

What is your system? Mac OS X 10.6, 10.7, 10.8?

Share this post


Link to post
Share on other sites

Lion 10.7.2 in extra / extentions folder:

 

ACPIMonitor.kext

ACPISensors.kext

ALC8xxHDA.kext

AppleACPIPlatform.kext

ElliottForceLegacyRTC.kext

FakeSMC.kext

IntelCPUMonitor.kext

IntelThermal.kext

IOPCIFamily.kext

JMicronATA.kext

NullCPUPowerManagement.kext

NuvotonNCT677x.kext

NVClockX.kext

SleepEnabler.kext

SuperIOFamily.kext

WinbondW836x.kext

 

installed istat menues 3.19 (without GPU or MoBo temp. indicator)

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.

Announcements

  • Similar Content

    • By miliuco
      Install macOS 10.15 Catalina on Gigabyte P55-USB3 with Radeon RX 580 graphics card using a USB device created with the createinstallmedia command and Clover as bootloader. Instructions to install macOS 10.14 Mojave on this computer are almost identical, replacing Catalina app with Mojave, so this article is suitable for both versions of macOS. The Gigabyte P55-USB3 motherboard (and some others from the same brand with the P55 / H55 chipset) have made it easy to build a hackintosh and install macOS since 10 years ago. Although it is an old motherboard, the behavior with Mojave or Catalina is very good after changing the classic hard drive (HDD) for a solid state drive (SSD).

      Components of the hackintosh
      Gigabyte GA-P55-USB3 motherboard: P55 chipset, 1156 socket, ALC892 audio, Gigabit RTL8111D network, DDR3 RAM Intel Core i5-750 processor for socket 1156: 4 cores, 8MB cache, clock rate 2.66 GHz Fenvi FV-T919 wireless + Bluetooth card: PCI-Express, wifi is ac type, detected by macOS as Airport and Apple Bluetooth Radeon RX 580 8 GB graphics card: works OOB but with a few details to be considered, it has its own article.  
      Previous requirements
      Install macOS Catalina app in /Applications folder USB flash drive with at least 16GB prepared from Disk Utility with MBR partition scheme and formatted as Mac Os Plus (on older Gigabyte boards like mine, USB sticks partitioned with GUID scheme instead of MBR usually hang the system when booting) Recent version of Clover (I have used r5117) Recent versions of Lilu (at least 1.4.4) and WhateverGreen (at least 1.3.9) to fine-tune the behavior of the graphics card Recent version of RealtekRTL8111 (I have used 2.2.2) FaceSMC version 6.26-322 (newer versions disable automatic mounting of USB devices on my system).  
      Create install USB
      Run this command from Terminal (assuming the target device is called USB):
      Bash: sudo /Applications/Install\ macOS\ Catalina.app/Contents/Resources/createinstallmedia --volume /Volumes/USB /Applications/Install\ macOS\ Catalina.app
      Clover must be installed on the USB memory, I choose the following options:
      Bootloader > Install boot0af on the MBR CloverEFi > CloverEFI 64-bit SATA BIOS Drivers, 64 bit > Recommended drivers > FSInject + SMCHelper + XhciDxe BIOS Drivers, 64 bit > File System drivers > ApfsDriverLoader Install RC scripts on selected volume Optional RC scripts > Disable sleep proxy client.  
      You have to copy 4 kexts to the EFI/CLOVER/kexts/Other folder of the USB device: FaceSMC 6.26-322, Lilu 1.4.4, WhateverGreen 1.3.9 and RealtekRTL8111 2.2.2. Regarding the config.plist file, the most significant is:
      Boot > kext-dev-mode = 1 in Boot arguments GUI > Theme embedded, EmbeddedThemeType Dark, Screen Resolution 1920x1080, Preboot in Hide Volume Graphics > blank, nothing is checked except if foxbox solution is used to have more than 2 connectors enabled RT Variables > 0x28 in BooterConfig and 0x67 in CsrActiveConfig SMBios > iMac14,2 Sytem Parameters> Yes in Inject Kexts and check Inject System ID.  
      Install macOS Catalina

      Boot from the USB device and choose Install macOS from Install macOS Catalina. The installation program runs until the PC restarts. Here choose Install macOS from HDD (the name of the volume you are installing macOS on). With RX 580 graphics card, the screen goes black in this second phase of the installation, it is a phase in which the user has nothing to do until the PC is restarted so you can let it work until the Clover menu again. You have to choose Boot macOS from HDDto boot the installed system from the hard disk, the screen is recovered and you can configure the account and the initial options. From this moment the screen works fine.

      In summary:
      Boot from USB > Clover menu > Install macOS from Install macOS Catalina > screen works fine Boot from USB > Clover menu > Install macOS from HDD > black screen Boot from USB > Clover menu > Boot macOS from HDD > screen works fine.  
      Install Clover and kexts on the hard drive

      Clover needs to be installed on the disk where we just installed macOS. Options are the same as when installing it on the USB memory. You also have to copy the 4 kexts (FaceSMC 6.26-322, Lilu 1.4.4, WhateverGreen 1.3.9 and RealtekRTL8111 2.2.2) into the EFI/CLOVER/kexts/Other folder on the EFI partition of the disk. And review the config.plist file remembering the comments for the USB.

      If everything goes well, the computer starts from the hard disk with a running copy of macOS Catalina.
       
       

    • By Slice
      The thread splitted from HWSensors3.
       
      Tools to testing Radeon state.
      Load RadeonPCI.kext  
      RadeonPCI.kext.zip
       
      How to load
      sudo chown -R root:wheel ~/Downloads/RadeonPCI.kext sudo chmod -R 755 ~/Downloads/RadeonPCI.kext sudo kextutil -v ~/Downloads/RadeonPCI.kext and use RadeonDump utility
      RadeonDump1.zip
       
      Commands to see temperature
      Polaris
      ./RadeonDump1 -n 6b0,c0300014
      SeaIsaland
      ./RadeonDump1 -n 200,c0300014
       
      Old families
      ./RadeonDump1 -r 714,7f4
       
      Other possible methods to find a register for temperature
      ./RadeonDump1 -n 6b0,c0300e0c
      ./RadeonDump1 -n 6b0,1c5
      ./RadeonDump -n 6b0,d8200ca4
      ./RadeonDump -r 59800,59810
      ./RadeonDump -r 678,680

       
       
       
      01.12.2017
      Latest solution RadeonMonitor.kext here
      works for RX 460,480,580
      not works for HD7790, R9 290X?
       
      06.12.2017
      Here works also with HD7790, R9 290X
       
      14.12.2017
      Support VEGA here
       
      13.12.2017
      Version for test modern cards
      RadeonPCI5.kext.zip
       
      06.04.2020
      Version for Catalina
      RadeonPCI5-v2.kext.zip
    • 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.
       
×