Jump to content

2,085 posts in this topic

Recommended Posts

dopo la befana e non natale :D e cambia croccantini al micio che mi pare incazzato :hysterical:

 

after the befana and not Christmas and change croccantini to the cat that I think pissed off

 

PS: buone vacanze :)

Edited by iCanaro

Share this post


Link to post
Share on other sites
Advertisement
On 12/21/2018 at 6:09 PM, vector sigma said:

 

These values are just read from the ioreg with no interpretation, i.e. HWMonitorSMC2.app just read what your driver says just as you can do using the Terminal. But, why do you think they are wrong?

 

@vector sigma

 

MonkeyMac-Pro-2018:~ Jay$ ioreg -l |grep \"PerformanceStatistics\" | cut -d '{' -f 2 | tr '|' ',' | tr -d '}' | tr ',' '\n'|grep 'Temp\|Fan\|Power'
"Fan Speed(%)"=45
"Fan Speed(RPM)"=1501
"Temperature(C)"=33
"Total Power(W)"=683
MonkeyMac-Pro-2018:~ Jay$ 

No way the Total Power reading is correct, if Vega was really drawing 683W it would explode .... :lol::lol:

 

When running a Open GL App (like FurMark) the Total Power data point appears to scale with the rendered output window size, for instance if you run the MacOS version of FurMark at the default size of 1024 x 640 the Total Power Reading (on my system) will be around 330W if you resize the window the Total Power data point changes depending upon the size of the FurMark output window ... if i make it smaller it will drop below 330W if i make it full screen it goes up to 680W !!! ... The rendered output window size seems to dictate the Total Power data point, which is totally incorrect ... if you do the same thing under windows it will always be the same value no matter the resolution of the furMark output window which is what one would expect.

 

When running a Open CL App (like LuxMark) the Total Power power is pegged at 680W (on my system) or the same value as when running Open GL app at full screen.

 

It's not an issue with HWMonitorSMC2 but due to a bug/error in Apples IOAccelerator module ... hopefully Apple will fix it in the next release of Mojave.

 

Quite why/how Apple managed this is beyond belief ... clearly MacOS is calculating the value by some sort of multiplier rather than reading it direct from the Vega's on board diagnostic sensors.

 

Cheers

Jay

Edited by jaymonkey

Share this post


Link to post
Share on other sites
On 12/20/2018 at 11:09 AM, Slice said:

It is already great achievement if you can start macOS on such hardware. Sensors monitoring looks to be a minor problem.

Test HWMonitorSMC2.app and report what is wrong.

 

@Slice
any support for this cpu ? : )


1123550161_ScreenShot2018-12-24at1_44_45PM.png.ceaab129e5bf589760ac9a1ee3a5e1ab.png

 

here is the pics you asked from HWMonitorSMC2.app  :


2146167607_ScreenShot2018-12-24at1_45_47PM.png.8d1918666680f8cafe67ba14fb49c76d.png


and from HWMonitorSMC.app :

586195050_ScreenShot2018-12-24at1_45_35PM.png.8846701115c178871a8ba77198cb6a9f.png

here are the kext using from latest release :

1954362515_ScreenShot2018-12-20at5_33_26PM.png.912b537da190d34b81eb0396da7cf1f3.png.e7d1b3f11f0446ff1bf979ee69440883.png


https://www.insanelymac.com/forum/topic/299861-hwsensors3/?do=findComment&comment=2654617

Edited by XLNC

Share this post


Link to post
Share on other sites

I noticed today that my Samsung 1TB 970 EVO M.2 temperature was over 80°C after gaming.

 

I checked what kind of reading I get in Windows using HWinfo.

 

For example when just idling, CPU Package is 40°C. While idling in macOS there's 62°C on CPU heatsink with HWmonitorSMC2. Would it be possible to get CPU Package reading?

 

Radeon temperature is about the same +4°C compared to HWinfo.

 

On Samsung SSD's there are two sensors, would it be possible to get both readings?

 

 

 

 

 

 

Share this post


Link to post
Share on other sites
On 12/28/2018 at 5:28 PM, Amble said:

I noticed today that my Samsung 1TB 970 EVO M.2 temperature was over 80°C after gaming.

 

I checked what kind of reading I get in Windows using HWinfo.

 

For example when just idling, CPU Package is 40°C. While idling in macOS there's 62°C on CPU heatsink with HWmonitorSMC2. Would it be possible to get CPU Package reading?

 

Radeon temperature is about the same +4°C compared to HWinfo.

 

On Samsung SSD's there are two sensors, would it be possible to get both readings?

 

 

 

 

 

 

 

NM the CPU Package, I see it now on HWmonitor. It's just missing often with several other entries when HWmonitor is set as autostart and I have close and start it again to see all entries.

Share this post


Link to post
Share on other sites

Very nice app as I'm getting used to it! Only one thing, the fonts look very tiny on my 4K 24'' monitor so can you please give us an option to use larger fonts?

 

Edit: I mean fonts in the menu bar

308933711_ScreenShot2018-12-30at7_10_43PM.png.ea74d6401087e2902f9230e5ec77f447.png

Edited by RandomTech

Share this post


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

Very nice app as I'm getting used to it! Only one thing, the fonts look very tiny on my 4K 24'' monitor so can you please give us an option to use larger fonts?

 

Edit: I mean fonts in the menu bar

308933711_ScreenShot2018-12-30at7_10_43PM.png.ea74d6401087e2902f9230e5ec77f447.png

 

I would prefer that too.

 

One thing i've been wondering also.

 

I was a programmer on my previous life. C# mostly, so I have no idea about GUI stuff on xcode. Would it be a hard job to redo the GUI?

 

It just seems like it's really old or not made with new GUI elements or whatever there is on apple's world. Comparing it to iStat sensors GUI for example, the iStat is much cleaner looking and much "snappier" when you interact with the GUI. 

 

Edited by Amble

Share this post


Link to post
Share on other sites

Also imo the sensors should be under the device the sensor is located. For example in HWinfo in Windows there is device and it's sensors below like this:

 

CPU: Intel i7-7700K

 Package temperature

 Core temperature

 ...

 

Motherboard: Gigabyte GA-Z270N-WiFi

 CPU heatsink temperature

 Ambient temperature

 ...

 

Now on HWmonitor for example the CPU heatsink temperature is under the CPU and if I understood correctly from the sources, it comes from the motherboard ITEIT87x.kext.

Edited by Amble

Share this post


Link to post
Share on other sites
On 12/30/2018 at 10:44 PM, Amble said:

 

I would prefer that too.

 

One thing i've been wondering also.

 

I was a programmer on my previous life. C# mostly, so I have no idea about GUI stuff on xcode. Would it be a hard job to redo the GUI?

 

It just seems like it's really old or not made with new GUI elements or whatever there is on apple's world. Comparing it to iStat sensors GUI for example, the iStat is much cleaner looking and much "snappier" when you interact with the GUI. 

 

The GUI of HWMonitorSMC2 is very new. It is still under development provided by Vector Sigma.

Share this post


Link to post
Share on other sites
On 12/21/2018 at 7:18 PM, vector sigma said:

Guys I will resume the development of HWM2 after the Christmas holidays (after January 6) as very soon I'll be out of Italy. See you, Merry Christmas and Happy New Year to all!

Are you ok? Do you have a New Year smoothly flowing to Easter? :)

Share this post


Link to post
Share on other sites
On 12/30/2018 at 9:22 PM, Amble said:

Now on HWmonitor for example the CPU heatsink temperature is under the CPU and if I understood correctly from the sources, it comes from the motherboard ITEIT87x.kext.

This is a point of view. Depends if you want to see CPU related stuff under the CPU group or CPU's related stuff under the Motherboard group. Honestly I can't see so much difference and what HWInfo really doesn't influence me, but then I have to ask you a question:

during a CPU test stress is better to watch in a place only, or in more than one place? ... I made my self this question and why it is under the CPU group.

though the ITE chip (isn't a kext but is read by him) is soldered in to the motherboard and a group exchange is possible for this reason.

On 12/30/2018 at 8:44 PM, Amble said:

Very nice app as I'm getting used to it! Only one thing, the fonts look very tiny on my 4K 24'' monitor so can you please give us an option to use larger fonts?

Tried the gadget? It was made for that purpose since you can enlarge the view and the font becomes bigger...

EDIT

anyway to change font you have just to edit one line:

let f = NSFont(name: "Lucida Grande Bold", size: 9.0)!

EDIT 2

That last was also for @RandomTech, I quoted Mr. Amble's post by mistake

Edited by vector sigma

Share this post


Link to post
Share on other sites
On 12/30/2018 at 8:44 PM, Amble said:

One thing i've been wondering also.

 

I was a programmer on my previous life. C# mostly, so I have no idea about GUI stuff on xcode. Would it be a hard job to redo the GUI?

 

It just seems like it's really old or not made with new GUI elements or whatever there is on apple's world. Comparing it to iStat sensors GUI for example, the iStat is much cleaner looking and much "snappier" when you interact with the GUI. 

the GUI is very new as Slice already said. Honestly what iStat do is to use iPhone buttons like which imho is orrific and I really hate them. You will have noticed that this project is free and opensource so that anyone can fork and made a request and sure I will be glad to implement someone else ideas also because I have a job that keeps almost all my time and no one ask for a donation or for money... just because we are enthusiasts, but not more. Consider also that the code I made lately is the only you can see (at least in swift) unlike happens for others.

Share this post


Link to post
Share on other sites
On 12/28/2018 at 4:28 PM, Amble said:

For example when just idling, CPU Package is 40°C. While idling in macOS there's 62°C on CPU heatsink with HWmonitorSMC2. Would it be possible to get CPU Package reading?

 

Radeon temperature is about the same +4°C compared to HWinfo.

What is stopping you to install the InstelPowerGadget.framework that enable the reading of all these things??

Share this post


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

anyway to change font you have just to edit one line:

let f = NSFont(name: "Lucida Grande Bold", size: 9.0)!

is it in the Info.plist ? :blush:

Share this post


Link to post
Share on other sites
On 12/9/2018 at 6:34 PM, vector sigma said:

The app read everythings is connected through pci and has a gpu compatible class-code. Everything is fine becouse macOS connect thunderbolt devices like that as pci devices. The IOAccelerator is what we need to show properties of your card because contains the "PerformanceStatistics", but eGPU doesn't respond to this class and "PerformanceStatistics" is published under a children of display0 (or whatever it is connected).

So, I need to think on how retrieve those info before, and then create code to try:)

Do you habe any ideas about two Vega cards? Thank you.

Share this post


Link to post
Share on other sites

I updated FakeSMC on my laptop from r167 to r184 last night. Booted back into Mojave no problem but it hung going into Sierra. Rolled back and it was fine. I checked the plist of the new FakeSMC kext and it shows it was built with the 10.14 SDK. Perhaps this has broken backwards compatibility?

 

Running r173 now (which uses 10.11 SDK) and all is well again. Just letting you know ahead of the next official release.

Share this post


Link to post
Share on other sites
On 2/17/2019 at 9:14 PM, losinka said:

Do you habe any ideas about two Vega cards? Thank you.

Vega cards aren't the problem, but egpus are apparently. Unfortunately, lately I have little time for this, also a apfs corruption happens here so I lost some files. Anyway before cristmass I do a test code without implementing it in any app, but you can run in this command line:

 

vclist.zip

 

run it and post the Terminal output.... hoping for :) 

 

11 hours ago, Riley Freeman said:

I updated FakeSMC on my laptop from r167 to r184 last night. Booted back into Mojave no problem but it hung going into Sierra. Rolled back and it was fine. I checked the plist of the new FakeSMC kext and it shows it was built with the 10.14 SDK. Perhaps this has broken backwards compatibility?

 

Running r173 now (which uses 10.11 SDK) and all is well again. Just letting you know ahead of the next official release.

I have an idea on why this happen but I need some tests to be done (... when I'll have time) anyway in which OS isn't working?

Share this post


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

I have an idea on why this happen but I need some tests to be done (... when I'll have time) anyway in which OS isn't working?

 

FakeSMC built with 10.14 SDK does not work in Sierra

The same built with 10.10...10.11 SDK works for any OS (Mavericks ... Mojave)

not sure about very old OSes

Edited by Rodion2010

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