Jump to content

1,165 posts in this topic

Recommended Posts

Hi, my Z77X-UD3H (IT8728F) isn't in LPCSensors and was showing incorrect sensors data, eg memory modules at 2.016 instead of 1.524.

 

I made a change in LPCSensors.kext/Contents/Info.plist and now HWSensors is showing correct data.

 

With the default Info.plist (loading the Default Platform Profile from ITE IT87x Monitor):

 

 

    <key>Default</key>
    <dict>
        <key>FANIN0</key>
        <string></string>
        <key>FANIN1</key>
        <string></string>
        <key>FANIN2</key>
        <string></string>
        <key>FANIN3</key>
        <string></string>
        <key>FANIN4</key>
        <string></string>
        <key>TEMPIN0</key>
        <string>Mainboard</string>
        <key>TEMPIN1</key>
        <string>CPU Heatsink</string>
        <key>TEMPIN2</key>
        <string>Ambient</string>
        <key>VIN0</key>
        <string>CPU Core</string>
        <key>VIN1</key>
        <string>Memory</string>
        <key>VIN2</key>
        <string>Power Supply</string>
        <key>VIN3</key>
        <string>Power Supply</string>
        <key>VIN4</key>
        <string>Power Supply</string>
        <key>VIN5</key>
        <string>Power Supply</string>
        <key>VIN6</key>
        <string>Power Supply</string>
        <key>VIN7</key>
        <string>Power Supply</string>
        <key>VIN8</key>
        <string>CMOS Battery</string>
    </dict>

 

post-1042363-0-68142500-1409115630_thumb.png

 

With modified Info.plist (Replaced the Default Platform Profile under ITE IT87x Monitor with the IT8728F Platform Profile):

 

 

    <key>Default</key>
    <dict>
        <key>FANIN0</key>
        <string></string>
        <key>FANIN1</key>
        <string></string>
        <key>FANIN2</key>
        <string></string>
        <key>FANIN3</key>
        <string></string>
        <key>FANIN4</key>
        <string></string>
        <key>TEMPIN0</key>
        <string>Mainboard</string>
        <key>TEMPIN1</key>
        <string>PCH Die</string>
        <key>TEMPIN2</key>
        <string>CPU Heatsink</string>
        <key>VIN0</key>
        <string>CPU Core</string>
        <key>VIN1</key>
        <string>Power Supply</string>
        <key>VIN2</key>
        <string>Power Supply</string>
        <key>VIN3</key>
        <string>Power Supply</string>
        <key>VIN4</key>
        <string>CPU GFX</string>
        <key>VIN5</key>
        <string>CPU VRM</string>
        <key>VIN6</key>
        <string>Memory</string>
        <key>VIN7</key>
        <dict>
            <key>gain</key>
            <integer>1000</integer>
            <key>name</key>
            <string>Auxiliary 3V</string>
            <key>offset</key>
            <integer>0</integer>
            <key>reference</key>
            <integer>0</integer>
        </dict>
        <key>VIN8</key>
        <dict>
            <key>gain</key>
            <integer>1000</integer>
            <key>name</key>
            <string>CMOS Battery</string>
            <key>offset</key>
            <integer>0</integer>
            <key>reference</key>
            <integer>0</integer>
        </dict>
    </dict>

 

post-1042363-0-09034400-1409116243_thumb.png

 

I don't know if it's 100% correct for Z77X-UD3H but is showing correct data. Hope that helps for future releases.

 

And thanks for this work. Regards.

Share this post


Link to post
Share on other sites
Advertisement

Hello. Couple months ago I posted for help about Asus gryphon and Nuvoton NCT6791D but there was no help. Problem is related with all voltages. In other words only voltages stuck and no change values, other sensors like temp or hdd info are ok. After that all voltage values are wrong and I can post picture for that and all Dumps from Aida64. If Kozlek can help that will be nice.  

Dumps.rar

post-1080457-0-59523300-1412758922.png

Share this post


Link to post
Share on other sites

I'm injecting FakeSMC.kext with Clover.

 

How do I install the plugin in the kext that's in Clover directory?

 

I think the package installer available in your repository looks for FakeSMC.kext in S/L/E folder.

Share this post


Link to post
Share on other sites

I'm injecting FakeSMC.kext with Clover.

 

How do I install the plugin in the kext that's in Clover directory?

 

I think the package installer available in your repository looks for FakeSMC.kext in S/L/E folder.

 

Put it the Plugins directory if it is not there create it, that would be FakeSMC.kext/Contents/Plugins/, alternatively you could run the installer then move the .kext from the S/L/E to the clover directory.

Share this post


Link to post
Share on other sites

No temps/freqs in HWMonitor, RadeonSensors attached to PEGP@0, IOReg attached

Sapphire HD 7750 Low Profile, Device_ID: 683F,

FakeSMC_v5.3.820, GPUSensors_v5.3.820, HWMonitor 6.3.1211

Suggestions?

Edit -  4/3/14, corrected HWMonitor version

Same issue here HD5850...

Also, i got insane temp for main board proximity (126ºC). Do you know something about this?

post-1128367-0-79033400-1413954053_thumb.png

Share this post


Link to post
Share on other sites

Cannot build HWMonitor.app on 10.10 with latest Xcode.

 

I keep getting this error:

HWMonitor/PopupFanCell.m:116:31: error: implicit conversion of 'NSInteger'

      (aka 'long') to 'NSAppearance *' is disallowed with ARC
  ...fan.engine.configuration.colorTheme.useBrightIcons.boolValue ?  NSPopoverAppearanceHUD : NSPopoverAppearanceMinimal;
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
Any idea?

Share this post


Link to post
Share on other sites

Hi Kozlek,

Latest revision (6.11.1328) works great here. I just noticed something.

 

GPU Fan rpm of my GTX 780 was correctly detected for some hours. Now the rpm info is stuck at 19 rpm, no matter what. I don't know how i could help if it's an issue dependent on HWSensors. Thanks.

Share this post


Link to post
Share on other sites

Hi,

 

I recently installed my 10.10 and noticed something. In the HWMonitor app all my info is OK but for my GPU it shows 0. I have a amd 7790 graphics card. How can I solve/debug this issue?

 

Here is a section from my syslog, might be useful:

10/11/14 18:52:17,000 kernel[0]: RadeonSensors (pci1): found ATI Radeon ID: 0x665c, ATOM BIOS: C58203
10/11/14 18:52:17,000 kernel[0]: RadeonSensors (pci1): using device-id to resolve temperature sensor type
10/11/14 18:52:17,000 kernel[0]: RadeonSensors (pci1): adding Sea Islands (CI) thermal sensor
10/11/14 18:52:17,000 kernel[0]: RadeonSensors (pci1): started
10/11/14 18:53:40,000 kernel[0]: RadeonSensors: still waiting for accelerator to start...
10/11/14 18:53:45,000 kernel[0]: RadeonSensors (pci1): found ATI Radeon ID: 0x665c, ATOM BIOS: C58203
10/11/14 18:53:45,000 kernel[0]: RadeonSensors (pci1): using device-id to resolve temperature sensor type
10/11/14 18:53:45,000 kernel[0]: RadeonSensors (pci1): adding Sea Islands (CI) thermal sensor
10/11/14 18:53:45,000 kernel[0]: RadeonSensors (pci1): started
 

Also a screenshot of HW mon:

post-1078586-0-21713200-1415651114_thumb.png

Share this post


Link to post
Share on other sites

My heatsink always "0". How can i fix this?

Im using latest Clover with latest FakeSMC.kext. My FakeSMC and Plugins inside Clover EFI/Kext/10.10 folder.. Many times I deleted and Reinstall FameSMC but never changed always "0".

 

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

Share this post


Link to post
Share on other sites

Hello. Couple months ago I posted for help about Asus gryphon and Nuvoton NCT6791D but there was no help. Problem is related with all voltages. In other words only voltages stuck and no change values, other sensors like temp or hdd info are ok. After that all voltage values are wrong and I can post picture for that and all Dumps from Aida64. If Kozlek can help that will be nice.  

 

I'm having the same issue! (Asus Maximus VI Impact Z87 - i7 4790k)

 

post-260373-0-75497200-1418460160_thumb.png

 

Something I've noticed is that Power Supply 6 seems to correlate with my cpu multiplier. It ramps up to 0.63V when turbo boost is on and if I lower my voltage with an offset, it also drops.

I was experiencing overheating, so I dropped vcore to 1.04V and now Power supply 6 goes between 0 and 0.58V.

 

I'd love to be able to see the actual Vcore.

 

post-260373-0-13001600-1418460132_thumb.png

 

My CPU frequency is also spiking to 1000THz every so often.

 

post-260373-0-17760600-1418460176_thumb.png

Share this post


Link to post
Share on other sites

I'm running 10.7.5 in 32-bit kernel & drivers mode on a Thinkpad T61 with X3100 graphics (device ID 2A02). T8100 CPU.

 

I tried a couple of older versions of HWSensors and also managed to do a 32-bit build from the latest sources. But the GPUSensors plugin doesn't want anything to do with the X3100.

 

I know this is stoneage equipment but it should work right? I get readings from ACPISensors and CPUSensors just fine. Any special requirements for GPUSensors to attach?

 

I keep a copy of fakesmc (with plugins inside) in both /Extra/Extensions (for booting into my installer partition) and in /S/L/E on the OS partition.

 

Not a peep from gpusensors during boot. com.apple.driver.AppleHWSensor and "gpu-sensor" are attached to AppleIntelGMAX3100FB in ioreg.

 

If anyone is interested in taking a look at this...let me know what else you need.

Share this post


Link to post
Share on other sites

I'm running 10.7.5 in 32-bit kernel & drivers mode on a Thinkpad T61 with X3100 graphics (device ID 2A02). T8100 CPU.

 

I tried a couple of older versions of HWSensors and also managed to do a 32-bit build from the latest sources. But the GPUSensors plugin doesn't want anything to do with the X3100.

 

I know this is stoneage equipment but it should work right? I get readings from ACPISensors and CPUSensors just fine. Any special requirements for GPUSensors to attach?

 

I keep a copy of fakesmc (with plugins inside) in both /Extra/Extensions (for booting into my installer partition) and in /S/L/E on the OS partition.

 

Not a peep from gpusensors during boot. com.apple.driver.AppleHWSensor and "gpu-sensor" are attached to AppleIntelGMAX3100FB in ioreg.

 

If anyone is interested in taking a look at this...let me know what else you need.

Hey,

Kozlek decided do not support old hardware such as X3100. 

It is my branch that supports it. See my signature.

Share this post


Link to post
Share on other sites

Thanks Slice, will do. I'm using Kozlek's branch out of habit. I was already thinking about trying your version next, seeing your Inspiron 1525 has the X3100.

 

/Edit #1

 

Cool, it works, I have GPU temp reading. Thanks!

 

/Edit #2

 

Woah, spoke too soon. Rebooting with External display connected I get a Kernel Panic: "AppleIntelGMAX3100FB GPU parser error".. then a ton of:

 

SMC::smcReadKeyAction ERROR TGxx (a screenful of keys starting with TG) kSMCBadArgumentError (0x89) fkeyHashTable 0x0x5b28a00

 

/Edit #3

 

Can't reproduce... odd

Share this post


Link to post
Share on other sites

Thanks Slice, will do. I'm using Kozlek's branch out of habit. I was already thinking about trying your version next, seeing your Inspiron 1525 has the X3100.

 

/Edit #1

 

Cool, it works, I have GPU temp reading. Thanks!

 

/Edit #2

 

Woah, spoke too soon. Rebooting with External display connected I get a Kernel Panic: "AppleIntelGMAX3100FB GPU parser error".. then a ton of:

 

SMC::smcReadKeyAction ERROR TGxx (a screenful of keys starting with TG) kSMCBadArgumentError (0x89) fkeyHashTable 0x0x5b28a00

 

/Edit #3

 

Can't reproduce... odd

We should move the discussion to another topic as this is OT here.

"AppleIntelGMAX3100FB GPU parser error". - is related to SMC keys that will be correctly produced by Clover+myFakeSMC+HWInfo. I am not sure other solutions do this.

"SMC::smcReadKeyAction ERROR TGxx" - this is spam version of AppleSMC.kext. See a replacement in my package HWSensors-rev15.

What is the best place to get the latest FakeSMC?

Latest Kozlek's version see links in topic.

Latest my version see in my signature.

Share this post


Link to post
Share on other sites

@kozlek

I encountered some KP on boot randomly...

Could you build the binary with latest OS X 10.10 SDK? :)  I'm guessing this may solve my issues. ^_^

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