Jump to content
About Just Joined group Read more... ×

1,164 posts in this topic

Recommended Posts

Yes, it's working. I tested it. But It has some changes in info.plist format. Ask me if you'll need info about this

 

thanks

 

here is my dsdt plus ssdt that i think it contain monitoring info

can you check them and tell me if acpi monitor will work with or not as my dsdt isn't direct :(

 

DSDT.aml.zip

 

SSDT.aml.zip

Share this post


Link to post
Share on other sites
Advertisement

I'd like to try to help and get a configuration for the Gigabyte GA-Z68MA-D2H-B3 motherboard (w/ITE8728), but I'm not sure how best to go about doing it since I don't own a copy of Windows to install on it (all of the programs you list for dumping the values for are Windows-based and the BIOS seems to be missing a number of the voltages.)

 

Is there any other good way of going about it? Thanks and keep up the really great work on this project!

Share this post


Link to post
Share on other sites

I'd like to try to help and get a configuration for the Gigabyte GA-Z68MA-D2H-B3 motherboard (w/ITE8728), but I'm not sure how best to go about doing it since I don't own a copy of Windows to install on it (all of the programs you list for dumping the values for are Windows-based and the BIOS seems to be missing a number of the voltages.)

 

Is there any other good way of going about it? Thanks and keep up the really great work on this project!

 

What we need is a reference point. Only manufacturer knows multipliers it uses to get proper voltages. We could obtain it inderectly by checking bios values or using other software. Other software available only for Windows. Also if you are an engeneer of electronics etc. you could obtain divisor resistors values.. It's a hard way.

 

 

Another way is much simple - usebios or windows. Another problem here is to use proper voltage input for proper voltage type (3.3g, 12v, cpu vcore etc). Thats why I am used windows programs - to find proper voltage inputs.

Share this post


Link to post
Share on other sites

evga x58 classified e760 panics on superiosensors.kext.

I can boot into os without superiosensors.

10.7.3 lion.

Share this post


Link to post
Share on other sites

+1 here with the latest version 8c1cc53

Several panics at boot on first system in signature.

sorry but in the hurry i haven't made a screenshot of the error, maybe i'll try it again in the afternoon.

In the meanwhile I had to revert to previous version.

cheers

 

here's the screenshot

post-449896-0-92326400-1333726902_thumb.jpg

Share this post


Link to post
Share on other sites

evga x58 classified e760 panics on superiosensors.kext.

I can boot into os without superiosensors.

10.7.3 lion.

 

Same trouble here.

 

Regards

Share this post


Link to post
Share on other sites

Hi kozlek

 

I have collected all the data that you ask for. :)

 

I want to send you the information with a PM, but it seems your inbox is full.

Do you have another address where I can send it to?

 

Thanks! :)

Share this post


Link to post
Share on other sites

Hi kozlek

 

I have collected all the data that you ask for. :)

 

I want to send you the information with a PM, but it seems your inbox is full.

Do you have another address where I can send it to?

 

Thanks! :)

 

Post it here or pm me - I have deleted all old conversations

Share this post


Link to post
Share on other sites

Hi, i have a P5KC motherboard with Lion 10.7.3 installed. I can't get voltage neither fans speed. I've installed:

 

ACPISensors.kext

FakeSMC.kext

IntelThermal.kext

RadeonX.kext

 

I've downloaded them from https://github.com/k...aster/Binaries. I've noticed now that you have fixed some kind of kernel panic with SuperIOSensors. Maybe the version in this repository is not stable?!. If so where can i download a stable one?

 

I think the board sensor is the Winbond W83627DHG.

 

I would appreciate some help on this please :P

Share this post


Link to post
Share on other sites

Hi, i have a P5KC motherboard with Lion 10.7.3 installed. I can't get voltage neither fans speed. I've installed:

 

ACPISensors.kext

FakeSMC.kext

IntelThermal.kext

RadeonX.kext

 

I've downloaded them from https://github.com/k...aster/Binaries. I've noticed now that you have fixed some kind of kernel panic with SuperIOSensors. Maybe the version in this repository is not stable?!. If so where can i download a stable one?

 

I think the board sensor is the Winbond W83627DHG.

 

I would appreciate some help on this please :P

 

You have to install SuperIOSensors instead of ACPISensors

Share this post


Link to post
Share on other sites

You have to install SuperIOSensors instead of ACPISensors

 

Ok i've done that with version 82aaec0. Still no luck :(

 

i went to the kernel log and i get this:

 

Apr  6 21:05:02 localhost kernel[0]: FakeSMC: Opensource SMC device emulator. Copyright 2009 netkas. All rights reserved.
Apr  6 21:05:02 localhost kernel[0]: FakeSMC: Supports hardware monitoring plugins. Copyright 2012 kozlek, usr-sse2, slice. All rights reserved.
Apr  6 21:05:02 localhost kernel[0]: FakeSMCDevice: 19 preconfigured key(s) added
Apr  6 21:05:02 localhost kernel[0]: FakeSMCDevice: successfully initialized
Apr  6 21:05:02 localhost kernel[0]: IntelThermal: CPU family 0x6, model 0xf, stepping 0xb, cores 2, threads 2, TJmax 90
Apr  6 21:05:02 localhost kernel[0]: RTC: Only single RAM bank (128 bytes)
Apr  6 21:05:02 localhost kernel[0]: SuperIO: found Winbond W83627DHG on port=0x2e address=0x290
Apr  6 21:05:02 localhost kernel[0]: Found ATI Radeon 6738
Apr  6 21:05:02 localhost kernel[0]: mbinit: done [96 MB total pool size, (64/32) split]
Apr  6 21:05:02 localhost kernel[0]: Pthread support ABORTS when sync kernel primitives misused
Apr  6 21:05:02 localhost kernel[0]: SuperIOMonitor: [Warning] no sensors configuration provided

Share this post


Link to post
Share on other sites
Ok i've done that with version 82aaec0. Still no luck :( i went to the kernel log and i get this:
 Apr 6 21:05:02 localhost kernel[0]: FakeSMC: Opensource SMC device emulator. Copyright 2009 netkas. All rights reserved. Apr 6 21:05:02 localhost kernel[0]: FakeSMC: Supports hardware monitoring plugins. Copyright 2012 kozlek, usr-sse2, slice. All rights reserved. Apr 6 21:05:02 localhost kernel[0]: FakeSMCDevice: 19 preconfigured key(s) added Apr 6 21:05:02 localhost kernel[0]: FakeSMCDevice: successfully initialized Apr 6 21:05:02 localhost kernel[0]: IntelThermal: CPU family 0x6, model 0xf, stepping 0xb, cores 2, threads 2, TJmax 90 Apr 6 21:05:02 localhost kernel[0]: RTC: Only single RAM bank (128 bytes) Apr 6 21:05:02 localhost kernel[0]: SuperIO: found Winbond W83627DHG on port=0x2e address=0x290 Apr 6 21:05:02 localhost kernel[0]: Found ATI Radeon 6738 Apr 6 21:05:02 localhost kernel[0]: mbinit: done [96 MB total pool size, (64/32) split] Apr 6 21:05:02 localhost kernel[0]: Pthread support ABORTS when sync kernel primitives misused Apr 6 21:05:02 localhost kernel[0]: SuperIOMonitor: [Warning] no sensors configuration provided 

 

Could you provide, please, IORegistryExplorer dump?

 

?

 

Sorry, I have not time and intention to make proper SSDTs or DSDTs for ACPISensors.

Share this post


Link to post
Share on other sites

Could you provide, please, IORegistryExplorer dump?

 

 

 

Sorry, I have not time and intention to make proper SSDTs or DSDTs for ACPISensors.

 

ok no problem but can you just tell me if i can do it or no ? :)

as there is no EC on acpi tables :(

Share this post


Link to post
Share on other sites

ok no problem but can you just tell me if i can do it or no ? :)

as there is no EC on acpi tables :(

 

As I remember in your AIDA or HWMon dump it was EC controller methods for temperatures, fans and maybe voltages. You could try it. I have tested APCISensors with code like this inside LPCB device:

 

Device (MON0)
{
Name (_HID, "monitor")
Method (VIN0, 0, NotSerialized)
 {
  Store (0x2FCF, Local0)
  Return (Local0)
 }

 Method (VIN1, 0, NotSerialized)
 {
  Store (GO02, Local0)
  Return (Local0)
 }

 Method (VIN2, 0, NotSerialized)
 {
  Store (GO03, Local0)
  Return (Local0)
 }

 Method (VIN3, 0, NotSerialized)
 {
  Store (GO04, Local0)
  Return (Local0)
 }

 Method (VIN4, 0, NotSerialized)
 {
  Store (GO05, Local0)
  Return (Local0)
 }
			}

 

Generally it's not important where you going to insert monitor device. In the code above I was checking GPIO methods returning values. They already was in my DSDT:

				OperationRegion (GPIO, SystemIO, 0x0800, 0x05)
				Field (GPIO, ByteAcc, NoLock, Preserve)
				{
					GO01,   8,
					GO02,   8,
					GO03,   8,
					GO04,   8,
					GO05,   8
				}

 

For this monitoring ACPI code I have modified "Keys Associations" node in ACPISensor's info.plist like this (thought it is voltages so it's Voltages section):

 

<dict>
<key>VVBS</key><string>VIN0</string>
<key>VVCS</key><string>VIN1</string>
<key>VVDS</key><string>VIN2</string>
<key>VVFS</key><string>VIN3</string>
<key>VVAS</key><string>VIN4</string>
</dict>

 

There is in the left side is valid SMC keys and in the right side monitor ACPI device methods to read values from

 

 

Thank you, should be completely fixed now in the latest rev.

Share this post


Link to post
Share on other sites

Hi,

 

I'm trying to get fans and voltages working, these are handled by SuperIOSensors.kext correct?

This kext does not seem to be loading at boot, as it is not listed in the output of the kextstat command.

If I load it manually via kextload it appears in the kexstat output but nothing shows up in dmesg about it.

The following is from dmesg for the other plugins:

FakeSMC: Supports hardware monitoring plugins. Copyright 2012 kozlek, usr-sse2, slice. All rights reserved.
FakeSMCDevice: 19 preconfigured key(s) added
FakeSMCDevice: successfully initialized
IntelThermal: CPU family 0x6, model 0x2a, stepping 0x7, cores 4, threads 4, TJmax 98
NVClockX: Card: 0, Device ID: e22, Architecture: 1000000, GF100 [GeForce GTX 460]
NVClockX: BIOS successfully read
NVClockX: Parsing BIOS complete
NVClockX: Adding temperature sensors

 

Here is a screenshot from HWMonitorExtra

HWMonitor.png

 

Do I need to edit the Info.plist in SuperIOSensors.kext before it will load?

Here are my DSDT, IORegistryExplorer dump ans lspci info, along with AIDA64 and OpenHardwareMonitor reports from Windows

http://dl.dropbox.co...%20Pro3%20M.zip

Share this post


Link to post
Share on other sites

Hi,

 

I'm trying to get fans and voltages working, these are handled by SuperIOSensors.kext correct?

This kext does not seem to be loading at boot, as it is not listed in the output of the kextstat command.

If I load it manually via kextload it appears in the kexstat output but nothing shows up in dmesg about it.

The following is from dmesg for the other plugins:

FakeSMC: Supports hardware monitoring plugins. Copyright 2012 kozlek, usr-sse2, slice. All rights reserved.
FakeSMCDevice: 19 preconfigured key(s) added
FakeSMCDevice: successfully initialized
IntelThermal: CPU family 0x6, model 0x2a, stepping 0x7, cores 4, threads 4, TJmax 98
NVClockX: Card: 0, Device ID: e22, Architecture: 1000000, GF100 [GeForce GTX 460]
NVClockX: BIOS successfully read
NVClockX: Parsing BIOS complete
NVClockX: Adding temperature sensors

 

Here is a screenshot from HWMonitorExtra

 

 

Do I need to edit the Info.plist in SuperIOSensors.kext before it will load?

Here are my DSDT, IORegistryExplorer dump ans lspci info, along with AIDA64 and OpenHardwareMonitor reports from Windows

http://dl.dropbox.co...%20Pro3%20M.zip

 

Thank you for report. Please, try the latest revision.

Share this post


Link to post
Share on other sites

@kozlek, thank you now it's working :).

 

1ceacd183674172.jpg

 

I just have some questions cause i'm a noob on this stuff. Can you explain me what are these:

  • Power/Battery
  • VRM Supply 3
  • Power Supply 2
  • Power Supply 5
  • Power Supply 6
  • Power Supply 7

I've seen in previous posts, that some of you have also Main 12v and Main 5v. How can i get them?

 

thank you once again :P, you're awesome

Share this post


Link to post
Share on other sites

Well done kozlek, with the latest 0b6d9a6 version it works all perfectly!

 

One question... i've got an intel quad 45nm q9300 processor that has a tjmax of 100 (at least from official intel specifications) but intelthermal detects it as 95, until now every time that i download a new version i have to change the field manually in info.plist.

I ask you since now that we have automatic detection in superiosensors, this is the only change that i have to do and... what about get rid of it? :P :P

How about change it from the source database?? Am i wrong?

 

I don't want to be misunderstood, you've already made absolutely a good work with it! ;)

Share this post


Link to post
Share on other sites

evga x58 sli classified e760

I can't upload screenshot. I just keep getting upload error message .

But It seems everything is working.

in voltages category , I think power supply2 is cpu core voltage.

and other voltages I don't recognize proper name for them.

I have 9 voltages showning.

Currently I don't have windows installed.

I found out that there's evga x58 sli configuration in sensors configuration section.

Is there anyway to load superiosensors in that configuration?

in kernel log

kernel: SuperIO:found fintek F71882 on port=0x4e address=0x290

Edited by kdtt

Share this post


Link to post
Share on other sites

Kozlek, would it be at all possible to reimplement the formerly supported and currently defunct SuperIO plugin for the NSCPC8739x chipset which is still available in the Slice/Navi FakeSMC HWSensors branch and If so, then what do you require for such a reimplementation?

Thank You.

Share this post


Link to post
Share on other sites

It seems everything is working nicely.

I changed configuration default value to that of evga.

I can't get screenshot upload working.

One question

VRM Supply 1 1.458v

VRM Supply 2 1.140v

There's quite difference there. Is that normal?

Share this post


Link to post
Share on other sites

As I remember in your AIDA or HWMon dump it was EC controller methods for temperatures, fans and maybe voltages. You could try it. I have tested APCISensors with code like this inside LPCB device:

 

Device (MON0)
{
Name (_HID, "monitor")
Method (VIN0, 0, NotSerialized)
 {
  Store (0x2FCF, Local0)
  Return (Local0)
 }

 Method (VIN1, 0, NotSerialized)
 {
  Store (GO02, Local0)
  Return (Local0)
 }

 Method (VIN2, 0, NotSerialized)
 {
  Store (GO03, Local0)
  Return (Local0)
 }

 Method (VIN3, 0, NotSerialized)
 {
  Store (GO04, Local0)
  Return (Local0)
 }

 Method (VIN4, 0, NotSerialized)
 {
  Store (GO05, Local0)
  Return (Local0)
 }
			}

 

Generally it's not important where you going to insert monitor device. In the code above I was checking GPIO methods returning values. They already was in my DSDT:

				OperationRegion (GPIO, SystemIO, 0x0800, 0x05)
				Field (GPIO, ByteAcc, NoLock, Preserve)
				{
					GO01,   8,
					GO02,   8,
					GO03,   8,
					GO04,   8,
					GO05,   8
				}

 

For this monitoring ACPI code I have modified "Keys Associations" node in ACPISensor's info.plist like this (thought it is voltages so it's Voltages section):

 

<dict>
<key>VVBS</key><string>VIN0</string>
<key>VVCS</key><string>VIN1</string>
<key>VVDS</key><string>VIN2</string>
<key>VVFS</key><string>VIN3</string>
<key>VVAS</key><string>VIN4</string>
</dict>

 

There is in the left side is valid SMC keys and in the right side monitor ACPI device methods to read values from

 

 

 

Thank you, should be completely fixed now in the latest rev.

 

thanks will try to simulate it on my notebook

Share this post


Link to post
Share on other sites

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