Jump to content

2,089 posts in this topic

Recommended Posts

1 hour ago, vector sigma said:

I wrote it in my last post, you can't see 'lm_sensors' :whistle:

 

On Mint it seems to be 'sensors-detect', I think :huh:

At least it said that thats how it is called when trying to execute 'lm_sensors'.

Here is the output with the --auto option: https://pastebin.com/Gs1jHCkY

Edit: I ran it again in manual mode, accepting everything. Here's the output:

https://pastebin.com/ahZUYDAD

Edited by unixb0y

Share this post


Link to post
Share on other sites
Advertisement
Just now, vector sigma said:

model NCT6793D, supported.

 

Great! Where to go from there? Wrong kext? Or need DSDT patch?

Share this post


Link to post
Share on other sites
25 minutes ago, unixb0y said:

 

Great! Where to go from there? Wrong kext? Or need DSDT patch?

In the W836x.kext/Contents/Info.plist navigate to:

IOKitPersonalities->Winbond W836x Monitor Plugin->Sensors Configuration->ASUS.

Start by creating your motherboard settings by copying the one most similar or search for a similar configuration on the net:

716233546_Schermata2019-03-04alle21_52_50.thumb.png.a479cbe599074104125998e6aceb14ea.png

 

Or just edit the default configuration. Good luck!

 

P.S. Use a plist editor and don't use mine. If you want to try the Z370-A configuration copy the node I made (by copying another Zxxx) to your existing Info.plist.

 

Info.plist.zip

Edited by vector sigma

Share this post


Link to post
Share on other sites
8 minutes ago, vector sigma said:

In the W836x.kext/Contents/Info.plist navigate to:

IOKitPersonalities->Winbond W836x Monitor Plugin->Sensors Configuration->ASUS.

Start by creating your motherboard settings by copying the one most similar or search for a similar configuration on the net:

716233546_Schermata2019-03-04alle21_52_50.thumb.png.a479cbe599074104125998e6aceb14ea.png

 

Or just edit the default configuration. Good luck!

 

P.S. Use a plist editor and don't use mine. If you want to try the Z370-A configuration copy the node I made (by copying another Zxxx) to your existing Info.plist.

 

Info.plist.zip

 

Yeah I opened both with Xcode and copied just the Z370-A line over from your plist over to mine. Unfortunately didn't do anything, it seems! Do I need to do the DSDT thing? If so, is there a good guide?

Share this post


Link to post
Share on other sites
4 minutes ago, unixb0y said:

 

Yeah I opened both with Xcode and copied just the Z370-A line over from your plist over to mine. Unfortunately didn't do anything, it seems! Do I need to do the DSDT thing? If so, is there a good guide?

You have to read back in the topic, and firstly ensure the kext is loaded:

kextstat | grep org.mozodojo.W836x

 

Share this post


Link to post
Share on other sites
1 minute ago, vector sigma said:

You have to read back in the topic, and firstly ensure the kext is loaded:


kextstat | grep org.mozodojo.W836x

 

 

Indeed, it's not loaded, thanks for the hint!

Share this post


Link to post
Share on other sites

and another way should beof copying (and replace) the content of Z370-A inside "Default"

Just now, unixb0y said:

 

Indeed, it's not loaded, thanks for the hint!

There will be a reason. permissions? is injected by Clover? any in the kernel log? Are you using FakeSMC.kext from the same project? etc

Share this post


Link to post
Share on other sites
12 minutes ago, vector sigma said:

and another way should beof copying (and replace) the content of Z370-A inside "Default"

There will be a reason. permissions? is injected by Clover? any in the kernel log? Are you using FakeSMC.kext from the same project? etc

 

Permissions were fine, copied FakeSMC from the project (a few months newer than my version) and rebooted. bang! everything works! I'm not sure about the fans (all on "16383 rpm" which is a little high :lol:) but I'm glad about the core temps and clock speeds, thank you very much!

"Main logic board" also says 0°C for "North Bridge" and "Ambient" ¯\_(ツ)_/¯ 

 

Any chance you know how to disable specific entries like in my case: battery and hdd status? I don't have a battery at all LOL and don't need to check hdd health every day. I have another software for that and use it periodically.

If needed I can also compile from source if you tell me where to remove those items and how to compile it :D Most of my work with Xcode was for iOS App development.

Edited by unixb0y

Share this post


Link to post
Share on other sites
4 minutes ago, unixb0y said:

Any chance you know how to disable specific entries like in my case: battery and hdd status?

If you use one of the latest betas I posted here since last saturday you can disable each group you want by disabling the relative checkbox:

1192467620_Schermata2019-03-04alle22_30_57.png.bc2f9dcf2605d8b972ee021d04b9e65d.png

 

I'll do a commit in a short time, maybe tomorrow.

Share this post


Link to post
Share on other sites
10 minutes ago, unixb0y said:

about the fans (all on "16383 rpm" which is a little high :lol:)

not sure about it, but don't forget to set the FANINLIMIT to the real fan number you have. Don't know if the order is important as well... as I'm not the devel of those plugins (ask @Slice).

Share this post


Link to post
Share on other sites
3 minutes ago, vector sigma said:

not sure about it, but don't forget to set the FANINLIMIT to the real fan number you have. Don't know if the order is important as well... as I'm not the devel of those plugins (ask @Slice).

 

Thanks, I will wait for his reply then :-) The fans are not urgent anyway! 

Share this post


Link to post
Share on other sites
5 hours ago, vector sigma said:

 

Mine is ASUS, so I chose W836x.kext, 

it CAN be Winbond but it is not a rule

Here is mine from Windows HWINFO

 

[Winbond/Nuvoton W83627DHG]
  Motherboard                         42.0 ∞C
  CPU                                     46.0 ∞C


  Vcore                                   1.208 V
  VIN1                                    3.504 V
  +3.3V                                   3.312 V
  +3.3V                                   3.312 V
  +5V                                     5.064 V
  VIN2                                    3.376 V
  VIN6                                    3.344 V
  3VSB                                    3.312 V
  VBAT                                    2.960 V


  CPU1                                    439 RPM
  Power                                   1240 RPM
  Auxiliary                               1318 RPM
 

2 hours ago, vector sigma said:

not sure about it, but don't forget to set the FANINLIMIT to the real fan number you have. Don't know if the order is important as well... as I'm not the devel of those plugins (ask @Slice).

I use FANLIMIT = 5 from the number of MB connectors 

3 real FANS, works OK, the rest are ignored

Edited by Rodion2010

Share this post


Link to post
Share on other sites
1 hour ago, Rodion2010 said:

it CAN be Winbond but it is not a rule

Here is mine from Windows HWINFO

 

[Winbond/Nuvoton W83627DHG]
  Motherboard                         42.0 ∞C
  CPU                                     46.0 ∞C


  Vcore                                   1.208 V
  VIN1                                    3.504 V
  +3.3V                                   3.312 V
  +3.3V                                   3.312 V
  +5V                                     5.064 V
  VIN2                                    3.376 V
  VIN6                                    3.344 V
  3VSB                                    3.312 V
  VBAT                                    2.960 V


  CPU1                                    439 RPM
  Power                                   1240 RPM
  Auxiliary                               1318 RPM
 

I use FANLIMIT = 5 from the number of MB connectors 

3 real FANS, works OK, the rest are ignored

 

Unfortunately, the FANLIMIT setting didn't change the fact that the RPM values of the fans are wrong and that it says the mainboard temp is 0°C.

What's interesting though is that it only shows 3 fans and I also only have 3 connected, so it seems to definitely recognise them.

I'm not sure what you are trying to say with that windows HWINFO output.

Share this post


Link to post
Share on other sites
1 minute ago, unixb0y said:

 

Unfortunately, the FANLIMIT setting didn't change the fact that the RPM values of the fans are wrong and that it says the mainboard temp is 0°C.

I'm not sure what you are trying to say with that windows HWINFO output.

 

"My values" are OK, RPMs and TEMPs are approx the same in both OS X and Windows

What model of SuperIO Chip do you have?

Share this post


Link to post
Share on other sites
1 minute ago, Rodion2010 said:

 

"My values" are OK, RPMs and TEMPs are approx the same in both OS X and Windows

What model of SuperIO Chip do you have?

 

I see! How to know the SuperIO chip? I posted output of something like hardware info from linux earlier, maybe it's in there?

Share this post


Link to post
Share on other sites
9 minutes ago, unixb0y said:

 

I see! How to know the SuperIO chip? 

that is exactly what i waned to say to those who are not sure what i am trying to say :)

You can find it and other info in windows HWINFO reports

my is [Winbond/Nuvoton W83627DHG] etc

Edited by Rodion2010

Share this post


Link to post
Share on other sites
1 minute ago, Rodion2010 said:

that is exactly what i waned to say to those who are not sure :)

You can find it and other info in windows HWINFO reports

 

Is it possible without Windows, pls? :frantics::D

What does the SuperIO chip affect?

Share this post


Link to post
Share on other sites
1 minute ago, unixb0y said:

 

Is it possible without Windows, pls? :frantics::D

What does the SuperIO chip affect?

it is possible with Linux or Google about your MB details...

You need to install kext for YOUR SuperIO  to measure RPM and TEMP

Share this post


Link to post
Share on other sites
25 minutes ago, Rodion2010 said:

it is possible with Linux or Google about your MB details...

You need to install kext for YOUR SuperIO  to measure RPM and TEMP

 

I was able to take this image of the chip:

IMG_0879.thumb.jpg.b4e3d9d3be9759c5ba7433c19c235506.jpg

 

Looks like a "Nuvoton NCT6793D".

 

Nuvoton

NCT6793D

274680Z4

817A9AFA

 

Edited by unixb0y

Share this post


Link to post
Share on other sites
9 hours ago, unixb0y said:

 

I was able to take this image of the chip:

IMG_0879.thumb.jpg.b4e3d9d3be9759c5ba7433c19c235506.jpg

 

Looks like a "Nuvoton NCT6793D".

 

Nuvoton

NCT6793D

274680Z4

817A9AFA

 

Yes, didn't already told you that here?

 

15 hours ago, vector sigma said:

model NCT6793D, supported.

In your pastebin log we found:

Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found unknown chip with ID 0xd121
    (logical device B has address 0x290, could be sensors)

id 0xd121 that is already supported in WindbondW836x.h:

NCT6793D   = 0xD121,

:P

Share this post


Link to post
Share on other sites
On 3/5/2019 at 3:00 AM, Rodion2010 said:

 

"My values" are OK, RPMs and TEMPs are approx the same in both OS X and Windows

What model of SuperIO Chip do you have?

Mobo Fans depend on this:

const UInt16 NUVOTON_TACHOMETER[]			= { 0x4C0,  0x4C2,  0x4C4,  0x4C6, 0x4C8, 0x4CA};

maybe that are not correct values for every mobo or revision of the chip?

6 registers for 5 fans?

 

looks like the registers are seven

Edited by vector sigma

Share this post


Link to post
Share on other sites
26 minutes ago, vector sigma said:

Yes, didn't already told you that here?

 

In your pastebin log we found:


Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found unknown chip with ID 0xd121
    (logical device B has address 0x290, could be sensors)

id 0xd121 that is already supported in WindbondW836x.h:


NCT6793D   = 0xD121,

:P

 

You did :D For whatever reason, @Rodion2010 still wanted me to make sure it was that chip ¯\_(ツ)_/¯ didn't understand myself why. But thanks also for the explanation on how you figured out the model :)

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.
       
×