Jump to content

2,079 posts in this topic

Recommended Posts

Advertisement

Hello Vector Sigma

 

I have a strange problem with alpha 9. 

The application produces an annoying pulsation in the taskbar. As you can see from the attached video. If i close HMSC2 the pulsation disappears and everything returns to normal

 

Video proof here:

https://streamable.com/7euvh

 

EDIT: Back to beta 7 and no pulsation problem

Edited by Extreme™

Share this post


Link to post
Share on other sites
On 10/29/2018 at 2:46 AM, vector sigma said:

This one: HWMonitorSMC2.app_Alpha8.zip, should now show Fans, even if "FNum" is absent. If the Fan name isn't present (e.g F0ID, F1ID, etc..)  the name will be just "Fan 0", "Fan 1" etc.

 

With this version,, my RX 580 is not detected

Share this post


Link to post
Share on other sites
20 hours ago, Andrey1970 said:

ОК tomorrow.

Hi, I forgot 3/4 translations.. see the new incoming app

13 hours ago, Extreme™ said:

The application produces an annoying pulsation in the taskbar. As you can see from the attached video. If i close HMSC2 the pulsation disappears and everything returns to normal

EDIT: Back to beta 7 and no pulsation problem

I hope that I have fix it, but after seeing this an idea was coming.. let see a new functionality :D of the new app.

P.S. beta 7 is no more, all is rewritten from scratch.

2 hours ago, Andres ZeroCross said:

 

With this version,, my RX 580 is not detected

Please a ioreg can't say mutch without it.

Share this post


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

Hi, I forgot 3/4 translations.. see the new incoming app

I hope that I have fix it, but after seeing this an idea was coming.. let see a new functionality :D of the new app.

P.S. beta 7 is no more, all is rewritten from scratch.

Please a ioreg can't say mutch without it.

 

Attached..

 

And this is screenshot of the HWMonitorSMC2 Alpha 9

image.thumb.png.c11398a6142f630417ed3413593106a7.png

Andres’s iMac.ioreg.zip

Edited by Andres ZeroCross

Share this post


Link to post
Share on other sites

New app promoted to Beta:

  1. Added new translations in Russian by Andrey1970, Italian and English by me.
  2. Added check for Intel Power Gadget: cpu must be Intel (Lol), family 6, model > 42, i.e >= 2nd generation of "Core" models. Xeon models 42, 46 and 47 are supported as I see that they can work (anyway SMC keys if present will be entirely read).
  3. Moved CPU Package IGPU inside the GPU group. If the IOAccelerator's monitoring is turned on that key will be added inside the Intel sub group.
  4. Tried to fix pulsations of the text in the top bar. Need a confirmation.
  5. New: instead of display sensors in the top bar, you can now display a gadget that you can place where you like. This gadget is always on top of other windows... so that you can now compare, run programs or make a test stress cosily observing the value you need. see the pictures:

 

1.png.a4bf19c452f3b4604b6fcd806ddbf79f.png2.png.9d3feecaa0104cd77d38b01ae8c6649f.png3.png.c22f075a324284990d36092fd83bbf76.png4.png.78f138f3da72004d197c1ab2fbb87ea3.png

 

5.png.7bb91f16cb8c097228aa9d2c0d5e4f19.png

 

Let me know.

 

One problem. DRAM is still under the CPU group due to the fact that is really inefficent to move it under the memory group. To do that a second call to the IntelPowerGadget.framework and its driver is needed and basically is a second call of all of its functionality. Really heavy, wont do that sorry.

 

HWMonitorSMC2.app_SMC_swift4.2_Beta1.zip

 

Edited by vector sigma
added missing Russian translations

Share this post


Link to post
Share on other sites
// Fans
"Fans or Pumps" = "Вентиляторы и помпы";
"Fan/Pump speed" = "Вентилятор обороты";
"Fan %d" = "Вентилятор %d";
"speed" = "обороты"; // rpm, all in lower case letters
"min speed" = "мин. обороты"; // rpm, all in lower case letters
"max speed" = "макс. обороты"; // rpm, all in lower case letters

Temporarily so.

I thinking that the translation will need to be corrected after I will see application.

I do not see some parameters, you possibly forgot still.

Share this post


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

// Fans
"Fans or Pumps" = "Вентиляторы и помпы";
"Fan/Pump speed" = "Вентилятор обороты";
"Fan %d" = "Вентилятор %d";
"speed" = "обороты"; // rpm, all in lower case letters
"min speed" = "мин. обороты"; // rpm, all in lower case letters
"max speed" = "макс. обороты"; // rpm, all in lower case letters

 

Thanks. Please I need also "Max Frequency" = "Max Frequency";

2 minutes ago, Andrey1970 said:

I do not see some parameters, you possibly forgot still.

Sorry which one? I didn't understand..

Share this post


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

New app promoted to Beta:

  1. Added new translations in Russian by Andrey1970, Italian and English by me.
  2. Added check for Intel Power Gadget: cpu must be Intel (Lol), family 6, model > 42, i.e >= 2nd generation of "Core" models. Xeon models 42, 46 and 47 are supported as I see that they can work (anyway SMC keys if present will be entirely read).
  3. Moved CPU Package IGPU inside the GPU group. If the IOAccelerator's monitoring is turned on that key will be added inside the Intel sub group.
  4. Tried to fix pulsations of the text in the top bar. Need a confirmation.
  5. New: instead of display sensors in the top bar, you can now display a gadget that you can place where you like. This gadget is always on top of other windows... so that you can now compare, run programs or make a test stress cosily observing the value you need. see the pictures:

 

1.png.a4bf19c452f3b4604b6fcd806ddbf79f.png2.png.9d3feecaa0104cd77d38b01ae8c6649f.png3.png.c22f075a324284990d36092fd83bbf76.png4.png.78f138f3da72004d197c1ab2fbb87ea3.png

 

5.png.7bb91f16cb8c097228aa9d2c0d5e4f19.png

 

Let me know.

 

One problem. DRAM is still under the CPU group due to the fact that is really inefficent to move it under the memory group. To do that a second call to the IntelPowerGadget.framework and its driver is needed and basically is a second call of all of its functionality. Really heavy, wont do that sorry.

 

HWMonitorSMC2.app_SMC_swift4.2_Beta1.zip

 

Working good,, but my SSD (Fujitsu F200) still not get health status

image.thumb.png.d00f9b8bfceba22c19340cdecf2aa6d4.png

Share this post


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

 

Attached..

 

And this is screenshot of the HWMonitorSMC2 Alpha 9

 

Andres’s iMac.ioreg.zip

Thanks I'll take a look tomorrow

1 minute ago, Andres ZeroCross said:

Working good,, but my SSD (Fujitsu F200) still not get health status

Sorry I really did not found any specification for that. Can you show me a dump from Windows where I can take a look on the attributed used for the values you are looking for?

Share this post


Link to post
Share on other sites
Sorry I really did not found any specification for that. Can you show me a dump from Windows where I can take a look on the attributed used for the values you are looking for?
Can i dump data from AIDA64???

Sent from my Mi Note 2 using Tapatalk

Share this post


Link to post
Share on other sites
Don't know, but I need the S.M.A.R.T. attributes
May i know "what attribute value" did you use to detect life for reguler ssd in your code?

Sent from my Mi Note 2 using Tapatalk

Share this post


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

May i know "what attribute value" did you use to detect life for reguler ssd in your code?

If I knew it, I would not have asked you :wink_anim:. Usually they are under "vendor specific data" that for ATA/SATA any Vendors can place where they like since the standard allow that (allow even to omit them). 

Anyway, most of the programs that dump smart attributes usually publish the attribute for temperature, life etc.. just find one.

Share this post


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

If I knew it, I would not have asked you :wink_anim:. Usually they are under "vendor specific data" that for ATA/SATA any Vendors can place where they like since the standard allow that (allow even to omit them). 

Anyway, most of the programs that dump smart attributes usually publish the attribute for temperature, life etc.. just find one.

 

Just for your information, this screenshot from HWMonitor from FakeSMC

 

A. This is for ESA3SMD2ISJB120GB (Life percentage is detected with HWMonitorSMC2 too)
307880579_ScreenShot2018-10-31at04_35_37.png.5e18319c867512dcac2b79b8ea82d2bc.png


 

A. This is for Fujitsu F200 (Life percentage is not detected with HWMonitorSMC2)

1954774842_ScreenShot2018-10-31at04_37_51.png.8d9f2ce8d867fe96e37a3593a7474899.png

 

I think id 173 from F200 (Wear leveling count) is as reference for life percentage,, many SSD use id 177 as Wear Leveling Count. Sorry, just my opinion

Edited by Andres ZeroCross

Share this post


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

Moved CPU Package IGPU inside the GPU group. If the IOAccelerator's monitoring is turned on that key will be added inside the Intel sub group.

 IGPU Packages does not change the indication. 

It is not necessary to remove IGPU Packages when IOAccelerator's monitoring is turned off.

Most likely a bug because of it.

Share this post


Link to post
Share on other sites
1 hour ago, vector sigma said:

Nuova app promosso a Beta:

  1. Aggiunte nuove traduzioni in russo da Andrey1970, italiano e inglese da me.
  2. Aggiunto il controllo per Intel Potenza Gadget: CPU deve essere Intel (Lol), famiglia 6, il modello> 42, vale a dire> = 2 ° generazione di modelli di "Core". modelli Xeon 42, 46 e 47 sono supportati come vedo che possono lavorare (tasti comunque SMC se presente sarà interamente lettura).
  3. Spostato iGPU CPU pacchetto all'interno del gruppo GPU. Se il monitoraggio del IOAccelerator è acceso quel tasto verrà aggiunto all'interno del gruppo sub Intel.
  4. Ha cercato di risolvere pulsazioni del testo nella barra in alto. Hai bisogno di una conferma.
  5. Nuovo: invece di sensori di visualizzazione nella barra in alto, è ora possibile visualizzare un gadget che è possibile inserire in cui ti piace. Questo gadget è sempre in cima ad altre finestre ... in modo che ora è possibile confrontare, eseguire programmi o fare uno stress test di cosily osservando il valore desiderato. vedere le immagini:

 

1.png.a4bf19c452f3b4604b6fcd806ddbf79f.png2.png.9d3feecaa0104cd77d38b01ae8c6649f.png3.png.c22f075a324284990d36092fd83bbf76.png4.png.78f138f3da72004d197c1ab2fbb87ea3.png

 

5.png.7bb91f16cb8c097228aa9d2c0d5e4f19.png

 

Fammi sapere.

 

Un problema. DRAM è ancora sotto il gruppo di CPU a causa del fatto che in realtà è inefficent per spostarlo sotto il gruppo di memoria. Per fare questo è necessaria una seconda chiamata al IntelPowerGadget.framework e il suo driver e fondamentalmente è una seconda chiamata di tutte le sue funzionalità. Davvero pesante, non farà che mi dispiace.

 

HWMonitorSMC2.app_SMC_swift4.2_Beta1.zip

 

 

Thank you for reply and new beta Vector Sigma.

 

Tried  but pulsation effect persists:

 

https://streamable.com/8v6yx

Edited by Extreme™

Share this post


Link to post
Share on other sites
19 hours ago, Andres ZeroCross said:

 

Just for your information, this screenshot from HWMonitor from FakeSMC

Sorry  but, this surely is not from FakeSMC: S.M.A.R.T in macOS is a library embedded with the OS itself and the only way is to query the dedicated driver, no need to reinvent the wheel ;).

Anyway It is a losed war. If you know where they are you can read it, otherwise there are tens and tens of ssds who no one knows where to look because these values aren't mostly never published. The attribute 173 (not 177 which is already taken into account) is really uncommon from the rest of the world and in fact I have my doubts that HWSensor can read S.M.A.R.T from every ssd in commerce, and as far as I know he cannot read S.M.A.R.T from NVME while HWMonitorSMC2 can :wink_anim:.

 

Try that: HWMonitorSMC2.app_SMC_swift4.2_Beta2.zip (may be the need of more attempts if some bytewise is needed)

18 hours ago, Andrey1970 said:

Maybe it was not necessary to move IGPU Packages? 

In group CPU it worked without bug.

I forgot to add the reading when the Timer call the function that update the sensor:hysterical:

Edited by vector sigma
monitor of new values added in beta3

Share this post


Link to post
Share on other sites
8 minutes ago, Extreme™ said:

 

Thank you for reply and new beta Vector Sigma.

 

Tried  but pulsation effect persists:

 

https://streamable.com/8v6yx

I have a vaguely Idea on why that doesn't happen to me: I don't have the dropbox icon or any other at left. Anyway this is not simple to solve (don't tell me the old app was able because is dead and because it just use different system, in fact you now have a lot of timers instead of only one, that's the cause). I'll look into this at the week end.

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

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