Jump to content

1,165 posts in this topic

Recommended Posts

Hi Mozodojo,

I installed IntelThermal and ACPISensors. On Lenovo G470 i5-2410M here I got:

post-706563-0-36690700-1328362496_thumb.png

Did I install wrong plug-ins?

 

Thanx..

 

ACPISensors only for advanced users and programmers. Check topics on projectosx.com.

Share this post


Link to post
Share on other sites
Advertisement

hello mozodojo

 

i get this in log

 

 

 

10:48 imac kernel[0]: F718x: [Warning] found unsupported chip ID=0x10 REVISION=0x7

Feb 4 19:10:48 imac kernel[0]: W836x: [Warning] found unsupported chip ID=0x10 REVISION=0x7

Feb 4 19:10:48 imac kernel[0]: RadeonMonitor: found 6759 Radeon chip

Feb 4 19:10:48 imac kernel[0]: IT87x: [Warning] invalid super I/O chip ID=0xffff

Feb 4 19:10:48 imac kernel[0]: RadeonMonitor: Unknown DeviceID!

 

 

how i can solve this issue

Share this post


Link to post
Share on other sites
Thanks mozodojo. my screenshot: Z68XP-UD3R & 2500K post-93383-0-65584600-1328372443_thumb.jpg

 

So TMPIN0 is System and TMPIN2 is Processor for IT8728F. Will fix it later.

Share this post


Link to post
Share on other sites

Wreid: I lost speedstepping using that FAKESMC + IntelThermal plugin. Always multi 10. I cheked with MSRDumper but same.

Then i guess it was by new AppleIntelCPU.kext 10.7.3 and reinstalled that kext from 10.7.2 . NO help.

Then i installed "old"/ other FakeSMC 3.1.0 without Intelthermal (but IntelCPUMonitor) and now stepping worked again. Also MSRDumper shows now multi 6...10, depend on cpu loads.

Perhaps other can check if multi stays fixed (highest multi) with that new set of FakeSMC + IntelThermal ?

Share this post


Link to post
Share on other sites

hello mozodojo

 

i get this in log

 

 

 

10:48 imac kernel[0]: F718x: [Warning] found unsupported chip ID=0x10 REVISION=0x7

Feb 4 19:10:48 imac kernel[0]: W836x: [Warning] found unsupported chip ID=0x10 REVISION=0x7

Feb 4 19:10:48 imac kernel[0]: RadeonMonitor: found 6759 Radeon chip

Feb 4 19:10:48 imac kernel[0]: IT87x: [Warning] invalid super I/O chip ID=0xffff

Feb 4 19:10:48 imac kernel[0]: RadeonMonitor: Unknown DeviceID!

 

 

how i can solve this issue

No problem.

New Radeon.kext rev509 at project.

 

Mozo, we should synchronize the projects.

Share this post


Link to post
Share on other sites

Mozo, thank you. Now my Winbond detected correctly:

Kernel.log: W836x: found Winbond W83667HG-B

 

All looks fine except number of fans:

post-21904-0-95702800-1328429325_thumb.png

 

How I can increase number of fans to 4? Now I changed value "FANINLIMIT" to 4, but no success.

 

Спасибо ).

Share this post


Link to post
Share on other sites

@Slice

 

i am totally with you, PLEASE SYNCHRONIZE YOUR PROJECTS.

 

@mozodojo

we all want to use monitoring, we all rely on values posted,

but dealing such a sensitive case with various versions, compatible and incompatible ones, older, newer,

makes it difficult.

 

and even god made a mistake with inventing humans.

Share this post


Link to post
Share on other sites

Not working for me.

No CPU multipier, no fan speed, no GPU...

Anyway, Thanks Mozodojo !

 

80046163.png

Share this post


Link to post
Share on other sites

thanks Mozodojo

 

my notebook is dell inspiron n5110

 

here is kernel log

 

Feb  5 17:39:29 localhost kernel[0]: PC8739x: NSC: Found supported chip ID=0xfc REVISION=0x1b
Feb  5 17:39:29 localhost kernel[0]: PC8739x: slice (C) 2011
Feb  5 17:39:29 localhost kernel[0]: FakeSMC: opensource SMC device emulator by netkas (C) 2009
Feb  5 17:39:29 localhost kernel[0]: FakeSMC: plugins & plugins support modifications by mozodojo, usr-sse2, slice (C) 2010
Feb  5 17:39:29 localhost kernel[0]: FakeSMCDevice: 17 preconfigured key(s) added
Feb  5 17:39:29 localhost kernel[0]: FakeSMCDevice: successfully initialized
Feb  5 17:39:29 localhost kernel[0]: PXSX cannot assert wake from D3cold
Feb  5 17:39:29 localhost kernel[0]: NVClockX: [Warning] no nVidia graphics adapters found
Feb  5 17:39:29 localhost kernel[0]: NVClockX: [Warning] 0>/y������a
Feb  5 17:39:29 localhost kernel[0]: PC8739x: found NSC PC8739xx, revision 0x1b
Feb  5 17:39:29 localhost kernel[0]: IntelThermal: CPU family 0x6, model 0x2a, stepping 0x7, cores 2, threads 4, TJmax 100
Feb  5 17:39:29 localhost kernel[0]: AppleIntelCPUPowerManagement: (built 18:56:37 Jan 12 2012) initialization complete
Feb  5 17:39:29 localhost kernel[0]: NVClockX: Card: 0, Vendor ID: 10de, Device ID: df5, Architecture: 1000000, GF100 [GeForce GT 525M]
Feb  5 17:39:29 localhost kernel[0]: PXHCD	0xffffff807ee85000:UIMInitialize xHC addressing capability 64 bit register
Feb  5 17:39:29 localhost kernel[0]: PXHCD	0xffffff807ee85000:UIMInitialize HCSParams2 = 0x11
Feb  5 17:39:29 localhost kernel[0]: PXHCD	0xffffff807ee85000:UIMInitialize MAX SCRATCH PAD = 0
Feb  5 17:39:29 localhost kernel[0]: NVClockX: Error reading BIOS
Feb  5 17:39:29 localhost kernel[0]: NVClockX: Adding temperature sensors
Feb  5 17:39:29 localhost kernel[0]: NVClockX: Adding frequency sensor
Feb  5 17:39:29 localhost kernel[0]: NVClockX: Overclocking...

 

and here is the result

 

post-378955-0-83561300-1328457186_thumb.png

 

fan wrong & fixed

 

no multipler no volt no chipset temp :(

Share this post


Link to post
Share on other sites

Hi mozo

Most new Asus boards have Nuvoton IO chips, owned by Winbond. Do you have any plans to add support for these? Data sheets are on the net, the open source Hw monitor code does contain support for them. I'd be happy to help with testing, thanks for all your work so far

Why not? Will add it later.

 

Hi,

 

I already did it but forgot to release it rolleyes.gif

In attached zip you will find all the stuff I made.

Also for those who like to play with ACPI http://www.projectosx.com/forum/index.php?showtopic=1593&view=findpost&p=16787

 

Enjoy!

NCT677x.zip

Share this post


Link to post
Share on other sites
Hi, I already did it but forgot to release it rolleyes.gif In attached zip you will find all the stuff I made. Also for those who like to play with ACPI http://www.projectosx.com/forum/index.php?showtopic=1593&view=findpost&p=16787 Enjoy! NCT677x.zip

 

Cool stuff!

 

I also implemented it yesterday, but not tested. I'll merge our plugins, you have things I want to add to another plugins - like more voltage keys..

Share this post


Link to post
Share on other sites
No problem. New Radeon.kext rev509 at project. Mozo, we should synchronize the projects.

 

Thanks Slice but i don't get any value on the Istate program

Share this post


Link to post
Share on other sites

No problem.

New Radeon.kext rev509 at project.

 

Mozo, we should synchronize the projects.

 

Hi, slice!

 

Yes, but only on GitHub. it has cool mac app... I don't want to get back to SVN.

 

thanks Mozodojo

 

my notebook is dell inspiron n5110

 

here is kernel log

 

Feb  5 17:39:29 localhost kernel[0]: PC8739x: NSC: Found supported chip ID=0xfc REVISION=0x1b
Feb  5 17:39:29 localhost kernel[0]: PC8739x: slice (C) 2011
Feb  5 17:39:29 localhost kernel[0]: FakeSMC: opensource SMC device emulator by netkas (C) 2009
Feb  5 17:39:29 localhost kernel[0]: FakeSMC: plugins & plugins support modifications by mozodojo, usr-sse2, slice (C) 2010
Feb  5 17:39:29 localhost kernel[0]: FakeSMCDevice: 17 preconfigured key(s) added
Feb  5 17:39:29 localhost kernel[0]: FakeSMCDevice: successfully initialized
Feb  5 17:39:29 localhost kernel[0]: PXSX cannot assert wake from D3cold
Feb  5 17:39:29 localhost kernel[0]: NVClockX: [Warning] no nVidia graphics adapters found
Feb  5 17:39:29 localhost kernel[0]: NVClockX: [Warning] 0>/y������a
Feb  5 17:39:29 localhost kernel[0]: PC8739x: found NSC PC8739xx, revision 0x1b
Feb  5 17:39:29 localhost kernel[0]: IntelThermal: CPU family 0x6, model 0x2a, stepping 0x7, cores 2, threads 4, TJmax 100
Feb  5 17:39:29 localhost kernel[0]: AppleIntelCPUPowerManagement: (built 18:56:37 Jan 12 2012) initialization complete
Feb  5 17:39:29 localhost kernel[0]: NVClockX: Card: 0, Vendor ID: 10de, Device ID: df5, Architecture: 1000000, GF100 [GeForce GT 525M]
Feb  5 17:39:29 localhost kernel[0]: PXHCD	0xffffff807ee85000:UIMInitialize xHC addressing capability 64 bit register
Feb  5 17:39:29 localhost kernel[0]: PXHCD	0xffffff807ee85000:UIMInitialize HCSParams2 = 0x11
Feb  5 17:39:29 localhost kernel[0]: PXHCD	0xffffff807ee85000:UIMInitialize MAX SCRATCH PAD = 0
Feb  5 17:39:29 localhost kernel[0]: NVClockX: Error reading BIOS
Feb  5 17:39:29 localhost kernel[0]: NVClockX: Adding temperature sensors
Feb  5 17:39:29 localhost kernel[0]: NVClockX: Adding frequency sensor
Feb  5 17:39:29 localhost kernel[0]: NVClockX: Overclocking...

 

and here is the result

 

post-378955-0-83561300-1328457186_thumb.png

 

fan wrong & fixed

 

no multipler no volt no chipset temp :(

 

No multiplier, what the CPU you have?

 

This plugin is totally made by slice, I really don't know how to fix it.

Share this post


Link to post
Share on other sites

Hi, slice!

 

Yes, but only on GitHub. it has cool mac app... I don't want to get back to SVN.

 

 

 

No multiplier, what the CPU you have?

 

This plugin is totally made by slice, I really don't know how to fix it.

 

sandybridge core i5 2410

 

hope slice fix it :)

 

thanks

Share this post


Link to post
Share on other sites

Probably just cos its unfinished or I grabbed it too early? But I got a KP using the Nuvoton kext.

 

Not sure if it'll help but I took a pic in case there's something useful there: link

 

Github rev: cf90527

SuperIO chip: Nuvoton NCT6776F

My specs are in my sig VV

Share this post


Link to post
Share on other sites

sandybridge core i5 2410

 

hope slice fix it :)

 

thanks

 

So the latest IntelThermal still not showing multipliers for you?

 

Probably just cos its unfinished or I grabbed it too early? But I got a KP using the Nuvoton kext. Not sure if it'll help but I took a pic in case there's something useful there: link Github rev: cf90527 SuperIO chip: Nuvoton NCT6776F My specs are in my sig VV

 

Something wrong with configuration reading from plist. Will check it later.

 

Do you have CPU multipliers showing correctly?

Share this post


Link to post
Share on other sites

Something wrong with configuration reading from plist. Will check it later.

ok thanks. :)

 

Do you have CPU multipliers showing correctly?

You mean with HWMonitor?

 

No

Share this post


Link to post
Share on other sites

ok

 

Feb  6 21:27:37 localhost kernel[0]: IntelThermal: CPU family 0x6, model 0x2a, stepping 0x7, cores 2, threads 4, TJmax 100

Feb  6 21:28:02 The-Kings-MacBook-Pro kernel[0]: IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00
Feb  6 21:28:05 The-Kings-MacBook-Pro kernel[0]: IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00
Feb  6 21:28:07 The-Kings-MacBook-Pro kernel[0]: IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00

Share this post


Link to post
Share on other sites

Latest Nuvoton kext didn't KP. Seems to be misreading though...

iStat

HWMonitor

Could you run for me, please, this debug version of IntelThermal.kext and show me kernel log after?

ok

 

Feb  6 21:27:37 localhost kernel[0]: IntelThermal: CPU family 0x6, model 0x2a, stepping 0x7, cores 2, threads 4, TJmax 100

Feb  6 21:28:02 The-Kings-MacBook-Pro kernel[0]: IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00
Feb  6 21:28:05 The-Kings-MacBook-Pro kernel[0]: IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00
Feb  6 21:28:07 The-Kings-MacBook-Pro kernel[0]: IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00IntelThermal: MSR_IA32_PERF_CONTROL 0x1D00

 

Odd...

Didn't get anything extra in my kernel.log when I used the debug version :/

Installed with Kext Wizard, tried manually installing it too.

Share this post


Link to post
Share on other sites

Latest Nuvoton kext didn't KP. Seems to be misreading though...

 

Nuvoton fixed now (on github), it was copy/past bug. Should work now.

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.

  • Similar Content

    • 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.
       
    • By Slice
      This thread devoted to share information about different SMC keys found or investigated anywhere.
       
      What are they?
      SMC keys is a somehow language to speak between macOS and hardware microcontroller presented in real Mac and absent in Hackintosh.
      They inform macOS about Hardware ID and current status. Moreover macOS can write something through SMC protocol to control hardware.
      FakeSMC ( ©Netkas) is the driver to emulate this microcontroller on PC having no such device which is necessary to boot macOS here.
      But FakeSMC contain only ~20 keys while real Mac answers ~200 keys.
      Some keys we added by HWSensors project reporting temperatures, FAN speeds, voltages etc.
      Some keys are model dependent was added by Clover to be sure if user changed model in GUI then corresponding keys will be changed automatically.
      Clover sets
      LogDataHub(&gEfiMiscSubClassGuid, L"RPlt", &gSettings.RPlt, 8);
      LogDataHub(&gEfiMiscSubClassGuid, L"RBr", &gSettings.RBr, 8);
      LogDataHub(&gEfiMiscSubClassGuid, L"EPCI", &gSettings.EPCI, 4);
      LogDataHub(&gEfiMiscSubClassGuid, L"REV", &gSettings.REV, 6);
      LogDataHub(&gEfiMiscSubClassGuid, L"BEMB", &gSettings.Mobile, 1);
      BEMB - is a mobility sign. =0 -desktop, =1 - mobile.
      REV - SMC hardware revision, changes sometimes with Apple updates.
      RPlt, RBr and EPCI is hardware capabilities, noticed used in Intel HD drivers.
       
      Structure.
      All SMC keys consists of name 4 ascii chars as 32bit integer, type and value.
      Types:
       "flag", len 1
       "ui8 ", len 1
       "ui16", len 2
       "sp78", len 2
       "ui32", len 4
      "fp2e", len 2
      "fpe2", len 2
      "{rev", and others...
       
      List of known keys
      SMC_list.plist.zip
      More keys will be discussed in the thread
       
       
      Feel free to share you knowledge and ask about noticed keys.
×