Jump to content
2,189 posts in this topic

Recommended Posts

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?

 

 

 

 

 

 

Link to comment
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.

Link to comment
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
Link to comment
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
  • Like 1
Link to comment
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
Link to comment
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.

  • Like 1
Link to comment
Share on other sites

  • 3 weeks later...
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? :)

Link to comment
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
Link to comment
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.

Link to comment
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??

Link to comment
Share on other sites

  • 4 weeks later...
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.

Link to comment
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.

  • Like 1
Link to comment
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?

Link to comment
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
Link to comment
Share on other sites

42 minutes ago, vector sigma said:

Is kextload complain about any? (e.g. running a plugin built in Mojave)

kextload - just failed to load

here is more detailed  kexlibs output

7 symbols not found in any library kext:

__ZN16IOPlatformDevice26_RESERVEDIOPlatformDevice1Ev

__ZN16IOPlatformDevice26_RESERVEDIOPlatformDevice0Ev

__ZN16IOPlatformDevice13matchLocationEP9IOService

___memmove_chk

__ZN9IODTNVRAM9metaClassE

__ZN16IOPlatformDevice26_RESERVEDIOPlatformDevice3Ev

__ZN16IOPlatformDevice26_RESERVEDIOPlatformDevice2Ev

  • Like 1
Link to comment
Share on other sites

18 hours ago, vector sigma said:

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 :) 

 

----------------------------------------------------
vclist (vector sigma 2018), found 2 graphics cards!
----------------------------------------------------
Model               = Radeon RX Vega 64
vendor ID           = <02100000>
vendor ID           = <7f680000>
revision ID         = <c1000000>
subsystem ID        = <7fe30000>
sub system VendorID = <a21d0000>


Device Utilization  = 0%
Total Power         = 10 Watts
Temperature         = 35°
Fan Speed           = 0 RPM
Fan Speed           = 40%
vram Used           = 61300736 bytes
vram Free           = 2120420800 bytes
----------------------------------------------------
Model               = Radeon Vega Frontier Edition
vendor ID           = <02100000>
vendor ID           = <63680000>
revision ID         = <00000000>
subsystem ID        = <766b0000>
sub system VendorID = <02100000>


Device Utilization  = 0%
Total Power         = 7 Watts
Temperature         = 18°
Fan Speed           = 2011 RPM
Fan Speed           = 41%
vram Used           = 4063232 bytes
vram Free           = 16935099840 bytes

 

  • Like 1
Link to comment
Share on other sites

15 minutes ago, losinka said:

 


----------------------------------------------------
vclist (vector sigma 2018), found 2 graphics cards!
----------------------------------------------------
Model               = Radeon RX Vega 64
vendor ID           = <02100000>
vendor ID           = <7f680000>
revision ID         = <c1000000>
subsystem ID        = <7fe30000>
sub system VendorID = <a21d0000>


Device Utilization  = 0%
Total Power         = 10 Watts
Temperature         = 35°
Fan Speed           = 0 RPM
Fan Speed           = 40%
vram Used           = 61300736 bytes
vram Free           = 2120420800 bytes
----------------------------------------------------
Model               = Radeon Vega Frontier Edition
vendor ID           = <02100000>
vendor ID           = <63680000>
revision ID         = <00000000>
subsystem ID        = <766b0000>
sub system VendorID = <02100000>


Device Utilization  = 0%
Total Power         = 7 Watts
Temperature         = 18°
Fan Speed           = 2011 RPM
Fan Speed           = 41%
vram Used           = 4063232 bytes
vram Free           = 16935099840 bytes

 

So we have the code :thumbsup_anim:. I hope to have time this weekend to implement this change also because require a total refactoring of what already exist.

Wait, you don't have an IGPU?

Link to comment
Share on other sites

5 minutes ago, vector sigma said:

So we have the code :thumbsup_anim:. I hope to have time this weekend to implement this change also because require a total refactoring of what already exist.

Thank you!

 

5 minutes ago, vector sigma said:

Wait, you don't have an IGPU?

now I have :) (0-connector)

Edited by losinka
  • Like 1
Link to comment
Share on other sites

×
×
  • Create New...