Jump to content

1,165 posts in this topic

Recommended Posts

Dear Kozlek,

HWMonitor shows a value for my GPU 0 Fan : 12288rpm ; but considering my card is fanless, how to fix this please ?

 

EDIT : apparently the problem came with a non native fanless card. I have switched with a genuine fanless and no more GPU fan value.

 

 

Sorry :)

Share this post


Link to post
Share on other sites
Advertisement

Temperature sensors are disabled on your notebook.

 

Later I plan to add check for disabled sensors to not to show them for users.

 

 

no the sensors are enable on the Motherboard

this is a windows snapshot for the hardware monitor

post-216126-0-66608600-1330547896_thumb.jpg

Share this post


Link to post
Share on other sites

 

 

 

no the sensors are enable on the Motherboard

this is a windows snapshot for the hardware monitor

 

Ok, Iam working on it.

Share this post


Link to post
Share on other sites

Everything works fine except one thing. Cpu frequency shows only 12x and 21x , though I have turbo ratio 1112 in log file and aicpmvers and performance array in ioregistry. Cpu voltage varies lot more.

I have i7 920 and evga x58 with cstate and pstate generated by chameleon and using drop ssdt .

 

Hi

 

with imac11,2 profile multiplier is x9 (lowest) or x22(highest)

with macpro3,1 I can see sometimes x9 x10 x11 x12 x13 and x22

never reached x14...x21 but that is OK for me :)

 

I can see 14 states with IORegistryExplorer

 

maybe you should try with diff. smbios profiles

 

I can't check Turbo Mode because of i3-530 :(

Share this post


Link to post
Share on other sites

Hi

 

with imac11,2 profile multiplier is x9 (lowest) or x22(highest)

with macpro3,1 I can see sometimes x9 x10 x11 x12 x13 and x22

never reached x14...x21 but that is OK for me :)

 

I can see 14 states with IORegistryExplorer

 

maybe you should try with diff. smbios profiles

 

I can't check Turbo Mode because of i3-530 :(

Thanks, I will try other smbios.plists

Share this post


Link to post
Share on other sites

Hi,

 

 

Mar 2 17:29:44 localhost kernel[0]: AppleIntelCPUPowerManagementClient: ready

Mar 2 17:29:44 localhost kernel[0]: FireWire (OHCI) TI ID 8023 built-in now active, GUID 0011d800012e2a2c; max speed s400.

Mar 2 17:29:44 localhost kernel[0]: W836x: found Winbond W83627DHG

Mar 2 17:29:44 localhost kernel[0]: FakeSMCPlugin: [Warning] error reading FNum value

Mar 2 17:29:44 localhost kernel[0]: W836x: [Warning] error adding tachometer sensor 1

Mar 2 17:29:44 localhost kernel[0]: FakeSMCPlugin: [Warning] error reading FNum value

Mar 2 17:29:44 localhost kernel[0]: W836x: [Warning] error adding tachometer sensor 4

 

With last revision.

 

Regards

Share this post


Link to post
Share on other sites

Hi,

 

 

Mar 2 17:29:44 localhost kernel[0]: AppleIntelCPUPowerManagementClient: ready

Mar 2 17:29:44 localhost kernel[0]: FireWire (OHCI) TI ID 8023 built-in now active, GUID 0011d800012e2a2c; max speed s400.

Mar 2 17:29:44 localhost kernel[0]: W836x: found Winbond W83627DHG

Mar 2 17:29:44 localhost kernel[0]: FakeSMCPlugin: [Warning] error reading FNum value

Mar 2 17:29:44 localhost kernel[0]: W836x: [Warning] error adding tachometer sensor 1

Mar 2 17:29:44 localhost kernel[0]: FakeSMCPlugin: [Warning] error reading FNum value

Mar 2 17:29:44 localhost kernel[0]: W836x: [Warning] error adding tachometer sensor 4

 

With last revision.

 

Regards

 

It was a few latest versions after :whistle:

Share this post


Link to post
Share on other sites

Hi kozlek, i would like to inform you that now, the gpu sensor works great here on my 9800gt GFX card.

p.s. is it right that my ssd reports (0) in the remaining life field?

cheers. and thanks for your work

 

post-449896-0-55372400-1330715492_thumb.png

Share this post


Link to post
Share on other sites

Hi kozlek, i would like to inform you that now, the gpu sensor works great here on my 9800gt GFX card.

p.s. is it right that my ssd reports (0) in the remaining life field?

cheers. and thanks for your work

 

post-449896-0-55372400-1330715492_thumb.png

 

I've noticed the same problem now, and it was working fine until the last update (6 days ago) I'm using the ITE plugin on my Z68AP-D3.

 

post-158318-0-43420800-1330719972_thumb.jpg

Share this post


Link to post
Share on other sites

I've noticed the same problem now, and it was working fine until the last update (6 days ago) I'm using the ITE plugin on my Z68AP-D3.

 

post-158318-0-43420800-1330719972_thumb.jpg

 

It's ok. This is raw SMART attribute value. I don't know the format for that value so I am simply show it as is. I have the same zero value for my two months old Intel ssd.

Share this post


Link to post
Share on other sites

Thanks Kozlek

 

yes correct now

thanks for your help

 

But I see system chipset reports only 17C. As I remember in windows this temperature was reported higher?

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