Jump to content

1,165 posts in this topic

Recommended Posts

Install OpenHardwareMonitor on windows. It will tell you the model number of your SuperIO chip.

For LPC I can't get more information with the tool. It says:

 

LPCIO
 
Chip ID: Unknown ITE with ID 0x8613 at 0x2E/0x2F
 
What I already know. Maybe I can get more information in Manufacter site.
 
The computer is the one in my signature.

Share this post


Link to post
Share on other sites
Advertisement

Your signature doesn't say which motherboard you're using, and that's what matters here.  Look around on your motherboard with a flashlight and a magnifying glass, and you should see the SuperIO model number printed on the IC somewhere.  It should say ITE or Winbond or Fintek.  If you have more than one chip, it's probably the largest one.

Share this post


Link to post
Share on other sites

Your signature doesn't say which motherboard you're using, and that's what matters here.  Look around on your motherboard with a flashlight and a magnifying glass, and you should see the SuperIO model number printed on the IC somewhere.  It should say ITE or Winbond or Fintek.  If you have more than one chip, it's probably the largest one.

I couldn't find anything on the board, but dumping the bios and opening with AMIBCP showed a hidden menu that says IT8615 SuperIO Configuration 

 

So I guess that it's an ITE model, IT8615.

Share this post


Link to post
Share on other sites

Hi, I'm after a bit of help getting fans and voltages reading correctly.

I'm using a Gigabyte EX58-UD5 which has an ITE it8720f SMC IC, shown top left in this photo:

post-729266-0-49090200-1484355445_thumb.jpg

 

This is what I'm starting with:

post-729266-0-93034700-1484354187_thumb.png

 

I'm using FakeSMC v6.23.1417 with CPUSensors, GPUSensors and LPCSensors

 

Fans:

What I would like is to move and rename the labels shown:

GPU Fan @ ~ 4500rpm should be 'Water Pump', this is on the CPU FAN header

CPU Fan @ ~ 1750rpm is my 'Rear Case Fans' connected to SYS FAN 2 (2 fans on a Y cable to PWM header)

System Power Fan 2 @ ~ 1337rpm is my 'Upper Case Fan' connected to SYS FAN 1

Power Fan @ ~ 1348 rpm is my 'Lower Case Fan' connected to PWR FAN (correct)

 

I don't have a GPU fan as I'm water cooled

 

Voltages:

GPU Core (correct)

CPU Core (correct)

Memory Modules (correct)

Main 3.3V - Completely wrong

Main 5V (correct)

Power Supply 2-5 - no idea what these should be

CMOS Battery (correct)

 

Here are my voltages and fan speeds shown in BIOS:

post-729266-0-33133500-1484355037_thumb.jpg

 

 

Any help would be appreciated

Share this post


Link to post
Share on other sites

Your signature doesn't say which motherboard you're using, and that's what matters here.  Look around on your motherboard with a flashlight and a magnifying glass, and you should see the SuperIO model number printed on the IC somewhere.  It should say ITE or Winbond or Fintek.  If you have more than one chip, it's probably the largest one.

 

A little bit late, but the chip is actually ITE IT8613E, and it's not inside LPC sensors source code. Do you know if it is possible to add it?

Share this post


Link to post
Share on other sites

A little bit late, but the chip is actually ITE IT8613E, and it's not inside LPC sensors source code. Do you know if it is possible to add it?

It is possible modify sources by existing samples, for example 8718.

Share this post


Link to post
Share on other sites

As already else where explained in this topic: For Clover use

 

First : Uninstall all the kexts (FakeSMC+ 4 sensors kexts)  from S/L/E !

 

  1. Extract the .pkg with Pacifist in a new folder ( Then you get: HWMonitor.app;FakeSMC.kext and 4 sensors kexts (Acpi, Cpu, Gpu and LPC) )
  2. Create a  "PlugIns" subfolder inside FakeSMC.kext/Contents
  3. Copy the 4 sensors.kexts inside that folder
  4. Copy the "New" FakeSMC.kext inside the EFI/CLOVER/KEXTS/10.12
  5. reboot

Good luck

hi,

 

it did not work. after doing that, my hackintosh got loop boot.

 

i put FakeSMC.kext and its plugin into EFI/C/K/10.12 and it works but only show CPU and keyboard/mouse information. SSD and fan not shows.

 

how to fix?

 

thanks.

Share this post


Link to post
Share on other sites

Hi, I'm after a bit of help getting fans and voltages reading correctly.

I'm using a Gigabyte EX58-UD5 which has an ITE it8720f SMC IC, shown top left in this photo:

attachicon.gif82948_2245_draft.jpg

 

This is what I'm starting with:

attachicon.gifScreen Shot 2017-01-14 at 00.42.50.png

 

I'm using FakeSMC v6.23.1417 with CPUSensors, GPUSensors and LPCSensors

 

Fans:

What I would like is to move and rename the labels shown:

GPU Fan @ ~ 4500rpm should be 'Water Pump', this is on the CPU FAN header

CPU Fan @ ~ 1750rpm is my 'Rear Case Fans' connected to SYS FAN 2 (2 fans on a Y cable to PWM header)

System Power Fan 2 @ ~ 1337rpm is my 'Upper Case Fan' connected to SYS FAN 1

Power Fan @ ~ 1348 rpm is my 'Lower Case Fan' connected to PWR FAN (correct)

 

I don't have a GPU fan as I'm water cooled

 

Voltages:

GPU Core (correct)

CPU Core (correct)

Memory Modules (correct)

Main 3.3V - Completely wrong

Main 5V (correct)

Power Supply 2-5 - no idea what these should be

CMOS Battery (correct)

 

Here are my voltages and fan speeds shown in BIOS:

attachicon.gifIMG_0034.jpg

 

 

Any help would be appreciated

Hello,

 

I'm using FakeSMC.kext v 6.24.1421 ; HWSensors.app with LPC,GPU,CPU and ACPI Sensors kext (Plugins )

 

I did some editing and created a specific Platformprofil ( inside LPCSensors.kext//Info.plist/IOKitPersonalities/ITE IT87xMonitor/Platformprofil/Gigabyte/  ) for my GA-EX58-UD5 MOBO

 

You'll find hereby my complete FakeSMC.kext (wich I put in EFI/C/K/10.12)

 

Image  what I see with HWSensors.app (6.24.1421)

post-305243-0-81525700-1490456743_thumb.png

 

 

FakeSMC.kext.zip

 

Perhaps this can help !

 

To do Fan name editing, you can do this in the the EX58-UD5 profil /Info.plist.... and the same in IT8720F dictionary

 

Good luck

Share this post


Link to post
Share on other sites

hi,

 

it did not work. after doing that, my hackintosh got loop boot.

 

i put FakeSMC.kext and its plugin into EFI/C/K/10.12 and it works but only show CPU and keyboard/mouse information. SSD and fan not shows.

 

how to fix?

 

thanks.

 

You could try with the FakeSMC.kext posted in post #1111.  ( Perhaps a permissions and (kernel) (cache rebuild...)

 

;)

Share this post


Link to post
Share on other sites

There is a new version out !

HWSensors 6.25.1426

 

  • New Feature:  CPUSensors: Added KabyLake support
  • New FeatureLPCSensors: Added support for NCT6793D (thanks to Sergey @ctich from applelife.ru for help with integration)
  • Bug Fix:          HWMonitor: Fixed some SMART attribute values formatting for Seagate HDDs

 

:)

Share this post


Link to post
Share on other sites

There are some little but nice improvements with the latest HWsensors 6.25.1426 compared to 6.24.1421(even with an old X58 mobo...)

 

6.24.1421           6.25.1426

post-305243-0-39417600-1491847017_thumb.png      post-305243-0-26461000-1491847067_thumb.png

Share this post


Link to post
Share on other sites

Hello,
I would like to ask if there are any ideas regarding the following (Gigabyte specific) issue:

FakeSMC 6.25-12-g2303970.1438 with GPU, CPU and LPC PlugIns and GA-Z97X-Gaming GT board.

This Gigabyte board has 2 LPC chips (detected on Windows using HWINFO64 or SIV64):

 

ITE IT8620E-04 Gigabyte Z97X-Gaming GT BIOS F7  Chip ID 86200400 (4)  LPC 002E  Port 0000 0A35 0A36

 

and

 

ITE IT8790E-DX Gigabyte Z97X-Gaming GT BIOS F7  Chip ID 87900300 (4)  LPC 004E  Port 0000 0A45 0A46

 

The IT8620E is found and temperature readings appear all right.

Problem is that all my 3 fans (AIO water pump, front and rear/heat exchanger fans) are attached to the IT8790E headers.

So obviously there aren't any fan speed sensors visible with this setup as detection stops after the IT8620E chip is discovered.

 

Moving over to the IT8620E headers is not an option because for reasons unknown this causes random speed jumps and instable fan control.

Only the IT8790E fan headers work normally, tried all BIOS settings and also not OS dependent as fans behave not differently when running Windows.

 

I've attempted to add the definitions for the IT8790E controller as another generic/compatible IT87xx chip.

Now I'm not a developer but as far as I understood what is going on in SuperIODevice.cpp the case of having more than one IT87xx is not covered.

 

However it would be fine to just attach to the second IT8790E and ignore the primary IT8620E.

Would there be a way to enable this kind of 'chip select' in LPCSensors plugin?

Thanks.

Share this post


Link to post
Share on other sites

Hello,

I would like to ask if there are any ideas regarding the following (Gigabyte specific) issue:

 

FakeSMC 6.25-12-g2303970.1438 with GPU, CPU and LPC PlugIns and GA-Z97X-Gaming GT board.

This Gigabyte board has 2 LPC chips (detected on Windows using HWINFO64 or SIV64):

 

ITE IT8620E-04 Gigabyte Z97X-Gaming GT BIOS F7  Chip ID 86200400 (4)  LPC 002E  Port 0000 0A35 0A36

 

and

 

ITE IT8790E-DX Gigabyte Z97X-Gaming GT BIOS F7  Chip ID 87900300 (4)  LPC 004E  Port 0000 0A45 0A46

 

The IT8620E is found and temperature readings appear all right.

Problem is that all my 3 fans (AIO water pump, front and rear/heat exchanger fans) are attached to the IT8790E headers.

So obviously there aren't any fan speed sensors visible with this setup as detection stops after the IT8620E chip is discovered.

 

Moving over to the IT8620E headers is not an option because for reasons unknown this causes random speed jumps and instable fan control.

Only the IT8790E fan headers work normally, tried all BIOS settings and also not OS dependent as fans behave not differently when running Windows.

 

I've attempted to add the definitions for the IT8790E controller as another generic/compatible IT87xx chip.

Now I'm not a developer but as far as I understood what is going on in SuperIODevice.cpp the case of having more than one IT87xx is not covered.

 

However it would be fine to just attach to the second IT8790E and ignore the primary IT8620E.

Would there be a way to enable this kind of 'chip select' in LPCSensors plugin?

Thanks.

Ask this person for help, he has the same MOBO as you ...

Share this post


Link to post
Share on other sites

My GTX 1080 Ti is not working. I am getting a panic after typing my password. Im a noob. Please help me.

I used the latest webdriver. 10.12.5 

Regards
Hunk

Share this post


Link to post
Share on other sites

My GTX 1080 Ti is not working. I am getting a panic after typing my password. Im a noob. Please help me.

I used the latest webdriver. 10.12.5 

Regards

Hunk

Remove GPUSensor.kext from /EFI/Clover/kexts or /System/Library/Extensions

GPUSensor.kext for Pascal is causing the Kernel Panic.

 

or you can give this one a try:

http://hwsensors.com/public/HWSensors.6.25-12-g23039705.1438.Binaries.dmg

Share this post


Link to post
Share on other sites

and what about those 54Mhz? Does it reduce the performance of the graphicscard?

 

 

Gesendet von iPhone mit Tapatalk

Share this post


Link to post
Share on other sites

In comparison to windows no!

In macOS my 1070 stays around 60 to 63 while idle and reaches around 72 under load but in windows it stays around 45 while idle and reaches around 71 under load.

 

Edit:

 

And some times it crashes the macOS just before it loads the desktop. So I just removed the GPUSensor.kext 

Share this post


Link to post
Share on other sites

It worked however the fans are not running. How do you measure the temperature when gpusensors.kext is deleted?

 

Should i try some benchmark to check if they run under load? Which benchmark is good?

THX

Share this post


Link to post
Share on other sites

It worked however the fans are not running. 

Not even under load?

 

For some GPUs with the smart fans, the fans won't start unless needed, put some load on your GPU for instance run LuxMark or Cinebench and see if the fans start or not.

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