Jump to content

1,165 posts in this topic

Recommended Posts

Advertisement

I can't make HWmonitors to read my cpu frequencies correctly. Everything else is fine. I have a i5-6600k and it only shows 800mhz as frequency for all cores.

I have fakesmc.kext and plugins in the efi/clover/kexts/10.12/ installed.

If I want to reinstall from scratch, I delete the current fakesmc file on efi/clover/kexts/10.12/ and install the ones in the hwmonitors installer. I then take the fakesmc and extensions in s/l/e and copy it back to efi/clover/kexts/10.12 and reboot? 

Will gpusensors.kext make my computer go crazy? 

Share this post


Link to post
Share on other sites

I can't make HWmonitors to read my cpu frequencies correctly. Everything else is fine. I have a i5-6600k and it only shows 800mhz as frequency for all cores.

I have fakesmc.kext and plugins in the efi/clover/kexts/10.12/ installed.

If I want to reinstall from scratch, I delete the current fakesmc file on efi/clover/kexts/10.12/ and install the ones in the hwmonitors installer. I then take the fakesmc and extensions in s/l/e and copy it back to efi/clover/kexts/10.12 and reboot? 

Will gpusensors.kext make my computer go crazy? 

 

You don't need to put the kext in both clover and /s/l/e having them in one path is enough 

 

run these command one by one in terminal

 

1. sudo nvram -c

2. sudo purge

3. sudo rm -f /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache && sudo touch /System/Library/Extensions && sudo kextcache -u /

sudo update_dyld_shared_cache -force

 

and reboot to see if the sensors work.

Share this post


Link to post
Share on other sites

Hello there,

 

I'm trying to get to work my SuperIO chip from a time now, and I can get more than fake values in HWMonitor.

I've tried to add the chips to source and only I can get fake values.

 

Information of my chips from CPU-Z are the following:


LPCIO
-------------------------------------------------------------------------

LPCIO Vendor			ITE
LPCIO Model			IT8613
LPCIO Vendor ID			0x90
LPCIO Chip ID			0x8613
LPCIO Revision ID		0x3
Config Mode I/O address		0x2E
Config Mode LDN			0x4
Config Mode registers	
		00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 
	00	00 00 00 00 00 00 00 04 00 00 00 00 00 00 00 00 
	10	00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
	20	86 13 03 59 00 00 F7 00 08 00 01 48 01 00 00 00 
	30	01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
	40	00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
	50	00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
	60	0A 30 02 30 00 00 00 00 00 00 00 00 00 00 00 00 
	70	09 02 00 00 04 04 00 00 00 00 00 00 00 00 00 00 
Register space			LPC, base address = 0x0A30


Hardware Monitors
-------------------------------------------------------------------------

Hardware monitor		ITE IT8625
	Voltage 0		1.12 Volts [0x66] (CPU VCORE)
	Voltage 1		1.09 Volts [0x63] (VIN1)
	Voltage 2		2.04 Volts [0xB9] (+3.3V)
	Voltage 3		3.42 Volts [0xB9] (+5V)
	Voltage 4		7.79 Volts [0xB1] (+12V)
	Voltage 7		2.79 Volts [0x97] (+5V VCCH)
	Voltage 8		1.55 Volts [0x8D] (VBAT)
	Temperature 0		23 degC (73 degF) [0x17] (TMPIN0)
	Temperature 1		32 degC (89 degF) [0x20] (TMPIN1)
	Temperature 2		28 degC (82 degF) [0x1C] (TMPIN2)
	Fan 1			882 RPM [0x2FD] (FANIN1)
	Fan PWM 0		0 pc [0x0] (FANPWM0)
	Fan PWM 1		0 pc [0x0] (FANPWM1)
	Fan PWM 2		0 pc [0x0] (FANPWM2)
Register space			LPC, base address = 0x0A30

		00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 
	00	13 1D FF 00 FF FF 9C 00 00 C0 64 00 58 FF FC FF 
	10	C7 FD AC 70 C0 00 94 94 FF 02 FF 67 FF BF 84 00 
	20	66 63 B9 B9 B1 FF FF 97 8D 17 20 1C 17 17 17 97 
	30	76 7D FE FC 63 9B CF F1 77 7F BF 3A 50 FD 6B EF 
	40	26 E0 5A E0 3C 1E 7F 00 AD 6A D4 00 5F 40 FD 75 
	50	FF 07 7F 7F 7F 40 00 00 90 64 00 12 60 00 00 00 
	60	7F 7F 7F 80 00 00 0F 80 00 32 7F 19 86 02 0F 46 
	70	00 32 7F 19 85 02 0F FF 00 23 7F 19 8F 02 0F FF 
	80	FF FF 00 00 00 00 00 00 02 30 01 02 01 E8 E0 00 
	90	00 00 00 00 00 00 00 FF 40 00 00 00 00 BD 00 02 
	A0	7F 7F 7F 80 00 00 0F 80 7F 7F 7F 80 00 00 0F 80 
	B0	B8 7F 00 00 7F 00 7F 00 5F B3 FF FF FF FF FF FF 
	C0	FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
	D0	FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 01 
	E0	FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
	F0	FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 

Thanks

Share this post


Link to post
Share on other sites

Anyone else having an issue with the latest hwsensor binaries release for Skylake processor/motherboard in OSX Sierra 10.12.5, system definition iMac 17,1 with the Asus Maximus Hero Alpha and Intel i7-6700k and with the newest release "HWSensors.6.25.1426.Binaries" my CPU temperatures are slowly getting higher and eventually over 90c. I replaced the binaries with version "HWSensors.6.23.1417.Binaries" two versions below and no issues, that build was released to support more skylake processors. Is the latest release not backward compatible for this motherboard/processor in OSX Sierra 10.12.5?

Share this post


Link to post
Share on other sites

Anyone else having an issue with the latest hwsensor binaries release for Skylake processor/motherboard in OSX Sierra 10.12.5, system definition iMac 17,1 with the Asus Maximus Hero Alpha and Intel i7-6700k and with the newest release "HWSensors.6.25.1426.Binaries" my CPU temperatures are slowly getting higher and eventually over 90c. I replaced the binaries with version "HWSensors.6.23.1417.Binaries" two versions below and no issues, that build was released to support more skylake processors. Is the latest release not backward compatible for this motherboard/processor in OSX Sierra 10.12.5?

 

I have an i3-6100 and I have not issues with CPUSensors. Even it shows 33ºC if idle. The odd thing is that I can't control fan speed (but my motherboard has smart fan feature so isn't really an issue for me) because of unsupported SuperIO. If you have trouble with it, try to build the last source:

https://sourceforge.net/p/hwsensors/code/ci/master/tree/

Just open with Xcode and build.

Share this post


Link to post
Share on other sites

I have an i3-6100 and I have not issues with CPUSensors. Even it shows 33ºC if idle. The odd thing is that I can't control fan speed (but my motherboard has smart fan feature so isn't really an issue for me) because of unsupported SuperIO. If you have trouble with it, try to build the last source:

https://sourceforge.net/p/hwsensors/code/ci/master/tree/

Just open with Xcode and build.

 

I found the bug you must not be using a header designated "pump" for liquid coolers is why you do not see this issue!

 

https://github.com/kozlek/HWSensors/issues/363

Share this post


Link to post
Share on other sites

To get my X299 rig to work I had to delete the plugins from fakesmc.

I'd love them back! I feel the need to keep tabs on this cpu as it can pull 300 watts at full load.

 

Is there any way I can help you guys with data to get it going?

 

This might be the first clue - a pic from a kernel panic before I deleted the plugins.

post-1564334-0-44534500-1502006632_thumb.jpg

 

Thanks :)

Share this post


Link to post
Share on other sites

To get my X299 rig to work I had to delete the plugins from fakesmc.

I'd love them back! I feel the need to keep tabs on this cpu as it can pull 300 watts at full load.

 

Is there any way I can help you guys with data to get it going?

 

This might be the first clue - a pic from a kernel panic before I deleted the plugins.

attachicon.gif20170806_083556.jpg

 

Thanks :)

I think you are seeing this because CPUSensors.kext has no definition for you CPU yet. It is so new that hasn't been added. Try including the other kexts but not CPUSensors. This is the price of getting latest hardware haha. Just wait a little for the community to develop new kexts.

Share this post


Link to post
Share on other sites

To get my X299 rig to work I had to delete the plugins from fakesmc.

I'd love them back! I feel the need to keep tabs on this cpu as it can pull 300 watts at full load.

 

Is there any way I can help you guys with data to get it going?

 

This might be the first clue - a pic from a kernel panic before I deleted the plugins.

attachicon.gif20170806_083556.jpg

 

Thanks :)

You could use a more recent FakeSMC.kext  ( 6.25.1426)  !

 

Yours is 6.16.1394  !  ^_^

HWSensors 6.25.1426

Share this post


Link to post
Share on other sites

 

You could use a more recent FakeSMC.kext  ( 6.25.1426)  !

 

Yours is 6.16.1394  !  ^_^

HWSensors 6.25.1426

 

Didn't make any difference.

It's ok, eventually it'll get going and now I have speedstep it's running really cool, so I'm not worried now :)

Share this post


Link to post
Share on other sites

Didn't make any difference.

It's ok, eventually it'll get going and now I have speedstep it's running really cool, so I'm not worried now :)

Do you use the plugins inside FakeSMC.kext ?

 

 

Stated by oSxFr33k #1136:

Apparently there is a bug only in LPCSensors.kext with  "W_PUMP headeré  that shuts off water pump completely.

 

Share this post


Link to post
Share on other sites

 

Do you use the plugins inside FakeSMC.kext ?

 

 

Stated by oSxFr33k #1136:

Apparently there is a bug only in LPCSensors.kext with  "W_PUMP headeré  that shuts off water pump completely.

 

 

I tried the plugins inside Fake SMC then tried the other kexts outside.

Share this post


Link to post
Share on other sites

The domain's registration has expired, most probably because payment was not renewed...

 

Try here as an alternative: https://sourceforge.net/projects/hwsensors/

Those are deprecated ! (6.16.13.72) from 2015-06-13 ..

 

The latest is here ...

 

https://github.com/kozlek/HWSensors/releases

 

HWSensors.6.26.1440.pkg.zip

Share this post


Link to post
Share on other sites

Sure, but they still work perfectly for systems up to that era, i.e. up to Haswell/Broadwell...

NB: 'seems there is a typo in your 1st link; makes it unusable.

Edited by Hervé

Share this post


Link to post
Share on other sites

I was checking to see if there was a more recent version of HWMonitor and FakeSMC since it hasn't been updated in a while.  While reviewing this thread, I saw that the most recent version listed was 6.26.1440, which has a creation date of August 26, 2017.

For some reason that I don't recall, I have a later version - 6.26.1765, with a creation date of October 17, 2017.  I don't remember where I got it from and I can't find the original binary files I must have downloaded but I am posting this version for those who want to try it out.  It's been working for me just fine.  I modified it for my own use but have removed my modifications in the files uploaded here.

HWSensors 6.26.1765.zip

If you tried to download this file and couldn't, it is because the forum doesn't yet allow the uploading of files other than image files for now.  That will be fixed in time.  Until then, I have uploaded the file to another service for file hosting.  Enjoy.

Edited by mnfesq

Share this post


Link to post
Share on other sites

Hi...i am a new user here. I want to know 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.

 

assembly circuit board

Edited by CoraDias

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