Jump to content

1,603 posts in this topic

Recommended Posts

Advertisement

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
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 1/17/2019 at 9:08 AM, losinka said:

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

Yes I'm ok thanks.... only I have more job than I expected for the beginning of the year :rofl:

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

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 DaHarry
      I have installed Hackintosh on to my System, but the CPU cooler is obviously louder then on Windows.
      I am using right now VirtualSMC.kext, but since FakeSMC provides temperature measurement tools, and VirtualSMC not, I asked my self if that might be a hint for my loud cooler?
      My question, has somebody tried maybe both and even compared them? And is FakeSMC maybe less noisy?
      Is it enough to just mount EFI partition, and delete the VirtualSMC.kext and put instead FakeSMC.kexts ? Without any fancy kext installation tool or terminal commands, just replace files and restart in enough?
      My System:
      Mainboard: Gigabyte Aorus Z390 Ultra
      CPU: Intel i9 9900k
      CPU Cooler: BeQuiet! Dark Rock 4
      GPU: Vega 64
      Ram: 2x16GB Corsair 3200
      SSD: 1TB Adata M.2
       
      The Tutorial i have used - https://github.com/cmer/gigabyte-z390-aorus-master-hackintosh/blob/master/STEP_BY_STEP.md
       
      Really works like a charm besides, the more noisy cooler, which i bought because it is extra quietly.
      I asked first at tonymac's forum, but they deleted the post because I haven't used their tool, really disgustig.. I really hope to never use their tools, and I hope here the information freedom is more respected.
      #f. tonyhoremacs
    • By fusion71au
      This is a brief guide on how to create a vanilla El Capitan (also same process for Sierra) OS X Installer USB with an updated prelinked kernel containing FakeSMC.

      It is tailored for those users who want to understand the “nuts and bolts” of how to create an installer and also to help brush up on their terminal skills (rather than have one made for them with the numerous automated “tools” available or even Apple’s createinstallmedia) :
       
       
      Specifically, it is also a “Proof of Concept” which shows that installation is possible without even having to rely on boot loader kext injection.

      Prerequisites
      Existing Yosemite installation (or Mavericks - see post#4 for steps 7,8) “Install OS X El Capitan.app" downloaded to the Applications folder Pacifist FakeSMC.kext - Slice or Kozlek branch Bootloader - Clover or Chameleon 8GB or larger USB drive (16GB recommended), formatted HFS+ (MBR or GUID) named “Installer”  
      Procedure
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Open OS X terminal and type the following lines, followed by <Enter> after each line.
          The image restore and file copying may take a while to complete, and at the end of the process, the Installer volume is renamed to “OS X Base System"....
       
      sudo -s hdiutil attach /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/SharedSupport/InstallESD.dmg asr restore -source /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg  -target /Volumes/Installer -erase -format HFS+ -noprompt -noverify rm /Volumes/OS\ X\ Base\ System/System/Installation/Packages cp -av /Volumes/OS\ X\ Install\ ESD/Packages /Volumes/OS\ X\ Base\ System/System/Installation cp -av /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg /Volumes/OS\ X\ Install\ ESD/BaseSystem.chunklist /Volumes/OS\ X\ Base\ System diskutil unmount /Volumes/OS\ X\ Install\ ESD exit 3.  Right click on the “OS X Base System” Volume and click “Get Info”
       

      4.  Click on the lock icon and untick “Ignore ownership on this volume”
       

      5.  Extract/Copy the El Capitan Kernels folder into /System/Library/ of the USB with Pacifist.  NB It is found in the "Essentials.pkg" in /System/Installation/Packages
       

      6.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel —> OG.prelinkedkernel
       

      7.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of the installer USB using Finder.
       

      8.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel…..
       
      sudo -s chmod -R 755 /Volumes/OS\ X\ Base\ System/Library/Extensions chown -R 0:0 /Volumes/OS\ X\ Base\ System/Library/Extensions touch /Volumes/OS\ X\ Base\ System/System/Library/Extensions kextcache -u /Volumes/OS\ X\ Base\ System exit Any errors should be noted but the output below is normal e.g.


      9. Install your Bootloader targeting the OS X Base System volume
       
       
       
       
      10.  Boot your system with the USB without injected kexts into the OS X Installer GUI....
       
       
       
       
       
      Post Install
      The original prelinked kernel in a fresh install of El Capitan will also lack FakeSMC ie it will only be linked to Apple signed kexts.  In order to boot into El Capitan the first time around without boot loader kext injection, the PLK needs to be rebuilt for the El Capitan volume like we did for the installer:
       
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel for the El Capitan volume —> OG.prelinkedkernel
      3.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of El Capitan using Finder
      4.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel.  In this example, the El Capitan volume is named "El_Capitan" - change if you have named it something else...
      sudo -s chmod -R 755 /Volumes/El_Capitan/Library/Extensions chown -R 0:0 /Volumes/El_Capitan/Library/Extensions touch /Volumes/El_Capitan/System/Library/Extensions kextcache -u /Volumes/El_Capitan exit 5. Install your Bootloader targeting the El Capitan volume.  This step is only necessary if you are installing El Capitan on a new drive without existing boot loader (not required if installing on a disk with existing boot loader beside Yosemite).
      6. Reboot your system without injected kexts into El Capitan!
       
       
      Other links
      The All-In-One Guide to Vanilla OS X for beginners
       
      Updates for Sierra and High Sierra   Custom Prelinkedkernel Generator Tool I have made a custom prelinkedkernel generator "PLK.tool" for Sierra + El Capitan.  Instructions:   1.  Download and extract the attached BaseSystem_PLK.tool.zip into your ~/Downloads folder.   2.  Copy any extra kexts necessary for booting your hack to ~/Downloads/BaseSystem/ExtraKexts (e.g. FakeSMC, VoodooPS2Controller), making sure SIP is disabled. 3.  Copy BaseSystem.dmg to ~/Downloads/BaseSystem  4.  Open terminal and run the following commands... cd ~/Downloads/BaseSystem chmod +x PLK.tool ./PLK.tool ---> supply your admin password ---> will place your new custom prelinkedkernel on the desktop.       macOS High Sierra bypass Firmware and MBR checks in post#13.
      BaseSystem_PLK.tool_ElCap.zip
      BaseSystem_PLK.tool_Sierra.zip
      BaseSystem_PLK.tool_Mojave.zip (need to run in Mojave to avoid dependency errors)
       
    • By vector sigma
      HWSensor Features
      Control temperature of Intel and AMD CPU Control temperature of AMD, Intel and NVidia cards Control temperature of motherboard Control FANS Control Voltages Control HDD/SSD state (SATA & NVMe) with S.M.A.R.T. monitoring  Control frequencies Laptop Battery Monitoring Different applications support High Sierra compatible Installation to /S/L/E or in the ESP (Clover only)  
      Supported languages:
      English (base), Russian, Italian, Korean and semplified Chinese
       
      Source code: at https://sourceforge.net/p/hwsensors/hwsensors3/code3/HEAD/tree/
      Bugs report at https://sourceforge.net/p/hwsensors/hwsensors3/tickets/
      Topic for discussion at: https://www.insanelymac.com/forum/topic/299861-hwsensors3/
       
      Chief Developer @Slice, new HWMonitorSMC2.app and package by @vector sigma
    • By Slice
      Laptop battery monitoring

       
       
       
      Using this driver you have to exclude other battery drivers: ACPIBatteryManager, AppleSmartBattery and so on.
      This driver assumes to using HWSensors3 with FakeSMC 3.5 as being part of it.
       
      19.01.2018
      Updated version of VoodooBatterySMC will get extended battery information and so it will be more exact.
      VoodooBatterySMC.kext.zip
       
      Updated HWMonitorSMC by vector-sigma
      HWMonitorSMC.app.zip
       
      HWMonitor2 by vector-sigma
      https://sourceforge.net/projects/hwsensors3.hwsensors.p/files/latest/download
×