Jump to content

2,087 posts in this topic

Recommended Posts

34 minutes ago, vector sigma said:

@thenightflyer, please try that: HWMonitorSMC2.app_beta5.zip (a doubt that this is cause by the localization system), let me know

I compiled source from github but i only get "HWMonitorSMC2.app version 2.3.1. Did you put the source for Beta 5 at Github???
Nice sensor with VirtualSMC.kext version 1.0.1

Screen Shot 2018-10-12 at 23.11.44.png

Share this post


Link to post
Share on other sites
Advertisement
2 minutes ago, Andres ZeroCross said:

How to get fan rpm be detected with this app?? What did you need?? Can i give my smc dump?

Sent from my Mi Note 2 using Tapatalk
 

There should be something to follow at first post. Honestly I never used it due to lack of hardware.

Share this post


Link to post
Share on other sites
30 minutes ago, fabiosun said:

here you can see also other results with HWsensorSMC2 old and new release with Virtulasmc on the left

Fakesmc on right part of my image

Yep, I had never seen Hex values with G and H (missing cores)

Quote

TCGC
TCHC

:hysterical:... just because they aren't. Il'' fix it.

Edited by vector sigma

Share this post


Link to post
Share on other sites
There should be something to follow at first post. Honestly I never used it due to lack of hardware.
But with FakeSMC.kext and plugin, all my fan is detected well. So i don't need dsdt patch ofcourse. Maybe related to keys of smc. I don't know

Sent from my Mi Note 2 using Tapatalk

Share this post


Link to post
Share on other sites
Just now, Andres ZeroCross said:

But with FakeSMC.kext and plugin, all my fan is detected well. So i don't need dsdt patch ofcourse. Maybe related to keys of smc. I don't know

Sent from my Mi Note 2 using Tapatalk
 

Hi, ask Slice for these kind of things as I'm really noob as I don't care personally, the app show datas from what plugins provide but really I can't help for that.

Share this post


Link to post
Share on other sites
Hi, ask Slice for these kind of things as I'm really noob as I don't care personally, the app show datas from what plugins provide but really I can't help for that.
Thanks for the response, maybe i should wait for new plugin for VirtualSMC.kext. again, thanks very much

Sent from my Mi Note 2 using Tapatalk

Btw,, My F200 is SSD too. But Life value is not shown. Any clue???

Screen Shot 2018-10-12 at 23.32.53.png

Share this post


Link to post
Share on other sites
6 minutes ago, Andres ZeroCross said:

Thanks for the response, maybe i should wait for new plugin for VirtualSMC.kext. again, thanks very much

Sent from my Mi Note 2 using Tapatalk
 

Btw,, My F200 is SSD too. But Life value is not shown. Any clue???

Screen Shot 2018-10-12 at 23.32.53.png

Here I can help. Mechanical hard drives do not have a life to read, so you'll never see it. This happens also with some old ssd, and also some unknown ssd, that, because any vendor can set the life attribute in any places in a sub structure called "vendor specific data" inside the 512 bytes of the S.M.A.R.T atrributes. Therefore it is not guaranteed that Life will always be displayed even for them.

Share this post


Link to post
Share on other sites
14 minutes ago, vector sigma said:

Here I can help. Mechanical hard drives do not have a life to read, so you'll never see it. This happens also with some old ssd, and also some unknown ssd, that, because any vendor can set the life attribute in any places in a sub structure called "vendor specific data" inside the 512 bytes of the S.M.A.R.T atrributes. Therefore it is not guaranteed that Life will always be displayed even for them.

Owh, but i am pretty sure life value is shown with FakeSMC.kext and plugin. Do you think this issue is related to plugin of FakeSMC.kext too??

image.png.c0f27aace7f6c77d7fd70707adb5e363.pngI use HW Monitor with VirtualSMC.kext and plugin (not FakeSMC.kext). See this

Also my Galax SSD is not shown status of life (my notebook) :)

Just for information

photo_2018-10-12_23-00-56.thumb.jpg.390742ca10cf24fe4c189ee46b44d9ae.jpg

 

 

 

Edited by Andres ZeroCross
Change picture

Share this post


Link to post
Share on other sites
4 minutes ago, Andres ZeroCross said:

Owh, but i am pretty sure life value is shown with FakeSMC.kext and plugin

I don't think this is due to the SMC keys, but from S.M.A.R.T instead. As I said the app should know where to look for the life attribute, and your F200 then is an SSD... unknown at least for me. Can you point me to the data sheet of that disk?

Share this post


Link to post
Share on other sites
5 minutes ago, vector sigma said:

I don't think this is due to the SMC keys, but from S.M.A.R.T instead. As I said the app should know where to look for the life attribute, and your F200 then is an SSD... unknown at least for me. Can you point me to the data sheet of that disk?


Fujitsu F100 = https://www.fujitsu.com/hk/Images/F100-SSD-datasheet.pdf

Galax 240GB Gamer series : http://www.galax.com/en/ssd/gamer-series/galax-gamer-ssd-l-240gb.html

Sorry i can't search data sheet for GALAX, just official site :)

Share this post


Link to post
Share on other sites
2 minutes ago, vector sigma said:

No luck finding it, but I'll take into account to let you dump the smart attributes with a test version of HWMonitorSMC soon.

 

Thanks you

Share this post


Link to post
Share on other sites
6 hours ago, fabiosun said:

less of usual..but maybe new one cores appear (16 and 17)

new function I created was bad:

- (NSString *)smcFormat:(int)num {
  if (num > 15) {
    for (char c = 'A'; c <= 'Z'; c++) {
      int i = (int)c - 55;
      if (i == num) {
        return [NSString stringWithFormat:@"%c", c];
      }
    }
  }
  return [NSString stringWithFormat:@"%d", num];
}

corrected:

- (NSString *)smcFormat:(int)num {
  if (num > 15) {
    for (char c = 'A'; c <= 'Z'; c++) {
      int i = (int)c - 55;
      if (i == num) {
        return [NSString stringWithFormat:@"%c", c];
      }
    }
  }
  return [NSString stringWithFormat:@"%.1X", num];
}

should work now.

HWMonitorSMC2.app_IPG_beta6.zip

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