Jump to content

Search the Community: Showing results for tags 'HWMonitor'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace

Categories

  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 5 results

  1. Slice

    HWSensors3

    Hi all, I created an installer for my version of FakeSMC with plugins and applications latest revision. Compatibility from 10.6 up to 10.11. Test, please. Download here: HWSensors.pkg.zip See my signature FakeSMC 3.4.0 revision 751 HWSensors.pkg-751.zip New project home is https://sourceforge.net/projects/hwsensors3.hwsensors.p/ where you can download most recent versions. Now it is FakeSMC 3.4.1 Explanations about the difference between versions 3 and 6 #137 20.05.2016 Revision 32 with explanation at #220 10.10.2017 FakeSMC is 3.5.0 compatible with High Sierra. New plugin VoodooBatterySMC created on the base of VoodooBattery by Superhai but with SMC keys generating to show Battery voltage and amperage. As well it created key BATP needed for right speedstep and FileVault2. Other kexts revised.
  2. This is the guide how to make monitoring of hardware parameters (temperatures, fan speeds, voltages etc) using DSDT programming. The method invented by me with THeKiNG presence and improved by Kozlek. Prerequisites There is FakeSMC plugin named ACPImonitor in my branch or renamed to ACPISensors in kozlek's branch. They are the same. HWMonitor or other monitoring application: iStat, K-Stat-i, ... How it works. HWMonitor or other software make a request for known SMC key, for example TA0P (ambient temperature), every 1 seconds. The request catched by FakeSMC which knows that the key registered by ACPImonitor plugin. This plugin knows that the value for the key must be read from ACPI device "monitor" by method "TCRR" and make a request to AppleACPIPlatform for evaluate this method. AppleACPIPlatform interpretates AML codes written into DSDT, finds the method and calculates the value using hardware access. The value return back to ACPImonitor -> FakeSMC -> AppleSMC -> HWMonitor which shows the "temperature". The kext ACPImonitor will not work OOB. It will work only with DSDT patches for the usage. Simple example DSDT. Device (FSAM) { Name (_HID, EisaId ("APP0111")) Name (_CID, "monitor") Name (TCRK, Zero) Method (TCRR, 0, NotSerialized) { Return (TCRK) } Method (TCRW, 1, NotSerialized) { Store (Arg0, TCRK) Return (TCRK) } Method (TCPP, 1, NotSerialized) { Store (\_TZ.THM._TMP (), Local0) Return (Local0) } } You have to create new device. It must have Name (_CID, "monitor") This is the key for ACPImonitor attached to it. Then see Method (TCRR,0, NotSerialized) mentioned above. It will return a value or variable TCRK. In this demo I made a method TCRW which will fill the variable TCRK from SMC key. The I have to make correspondence ACPI_methodSMC_key in ACPImonitor.kext/info.plist I can write values to the SMC key TA1P ./SMC_util3 -kTA1P -w28 and see the value 28 appears in HWMonitor as "Ambient temperature" Value conversions must be provided in DSDT. Predefined keys ACPI SMC Name TCPU Th0H CPU heatsink TSYS TN0P Northbridge temperature TDIM Tm0P DIMM temperature TAMB TA0P Ambient TCPP TC0P CPU proximity VCPU VC0C CPU voltage VMEM VM0R DIMM voltage ACDC ACIN, ACEN Presence of AC power FAN0 - FAN9 for FAN speed FTN0 -FTN9 for FAN rotation time In the case of FAN reading we also want to assign name to them. It is also possible with the Info.plist What to monitor in real DSDT? This is individual. So why the ACPImonitor will not work OOB. See example from my notebook. looking through DSDT I found the follow region. OperationRegion (TMIF, SystemMemory, 0xFF800160, 0x20) Field (TMIF, ByteAcc, Lock, Preserve) { THS0, 8, THS1, 8, THS2, 8, Offset (0x08), FAN1, 8, Offset (0x10), TSP0, 8, TSC0, 8, TSP1, 8, TSC1, 8 } Looks like three temperatures and one FAN. As well I found ThermalZone Scope (_TZ) { ThermalZone (THM) { Method (_CRT, 0, NotSerialized) { Store (\_SB.PCI0.LPCB.WSEC.C2K (\_SB.PCI0.LPCB.WSEC.TSC0), Local0) Return (Local0) } Method (_TMP, 0, NotSerialized) { Store (\_SB.PCI0.LPCB.WSEC.C2K (\_SB.PCI0.LPCB.WSEC.THS0), Local0) Return (Local0) } _CRT - critical temperature _TMP - current temperature _SB.PCI0.LPCB.WSEC.C2K is a method to convert Celsius to Kelvin degrees. So I see that the field THS0 is really CPU temperature. Using ACPImonitor is only way to do monitoring on notebooks because no other methods works and because it usually contains ThermalZone. I know my guide is too short and hope some users shows own examples how to do ACPI monitoring. Note. This method is useful mostly for notebook where temperature and FANs control present in DSDT. For desktops there are plugins like ITE87xx, Winbond, Fintek depending on you LPC chip installed. 10.10.2017 ACPIMonitor version 1.0.3 There is a possibility to define some types and sizes for custom keys <key>keysToAdd</key> <dict> <key>TCRR</key> <string>TA0P-2</string> <key>TCRW</key> <string>TA1P-3</string> <key>MSLD</key> <string>MSLD-1</string> </dict> The number after key name means follow 0 -> "flag", len 1 1 -> "ui8 ", len 1 2 -> "ui16", len 2 3 -> "sp78", len 2 4 -> "ui32", len 4
  3. Version

    6,219 downloads

    Fixes CPU temperature and multiplier readings in HWMonitor and iStat on model 0x3C (LGA1150 Desktop Form) Haswell CPUs, including i7-4770K and i5-4670K. The larger of the two downloads was compiled on 10.8.4 with the 10.8 sdk. I have not tested this build. The second and smaller file was compiled on 10.9 with the 10.9 sdk and has been confirmed to work in Mavericks with i7-4770K and i5-4670K. Kozlek has since merged this patch with his master branch, you can download and compile it yourself at https://github.com/kozlek/HWSensors Wait for hwmonitor to prompt you to update, or wait for binaries to be available at https://bitbucket.org/kozlek/hwsensors/downloads diff --git a/CPUSensors/CPUSensors.cpp b/CPUSensors/CPUSensors.cpp index 3af1039..54b9d60 100755 --- a/CPUSensors/CPUSensors.cpp +++ b/CPUSensors/CPUSensors.cpp @@ -363,6 +363,7 @@ bool CPUSensors::start(IOService *provider) readTjmaxFromMSR(); break; + case CPUID_MODEL_HASWELL_DT: case CPUID_MODEL_HASWELL_MB: case CPUID_MODEL_HASWELL_ULT: case CPUID_MODEL_HASWELL_ULX: diff --git a/Shared/cpuid.h b/Shared/cpuid.h index 4bcba2f..9c17cb1 100755 --- a/Shared/cpuid.h +++ b/Shared/cpuid.h @@ -151,6 +151,7 @@ #define CPUID_MODEL_NEHALEM_EX 0x2E #define CPUID_MODEL_WESTMERE_EX 0x2F #define CPUID_MODEL_IVYBRIDGE 0x3A +#define CPUID_MODEL_HASWELL_DT 0x3C #define CPUID_MODEL_HASWELL_MB 0x3F /* Haswell MB */ //#define CPUID_MODEL_HASWELL_H 0x?? // Haswell H #define CPUID_MODEL_HASWELL_ULT 0x45 /* Haswell ULT */ @@ -457,6 +458,7 @@ static void cpuid_update_generic_info() cpufamily = CPUFAMILY_INTEL_IVYBRIDGE; break; + case CPUID_MODEL_HASWELL_DT: case CPUID_MODEL_HASWELL_MB: case CPUID_MODEL_HASWELL_ULT: case CPUID_MODEL_HASWELL_ULX:
  4. For the most part I've had a 100% working build since 10.8.2. I've done every point update and nothing has broken until now. (Well except iMessage, but we know that's a different story) First my build - Chimera 4.1.0 Gigabyte GA-Z77X-UD5H (F14 bios) 3770K @ 4.5GHz Gigabyte GeForce GTX 670 2GB 32GB 1600MHz RAM OC to 1867MHz 256GB Samsung 840 Pro In the past I've never had an issue with all of my system stats showing up in HWMonitor or iStat Menus so long as FakeSMC Plugins are installed. My CPU has always reported at the correct frequency under HWMonitor and iStat, and my RAM showed up as the correct frequency in "About this Mac". However as soon as I updated to 10.10.3, this was no longer the case. HWmonitor and iStat show my CPU running at 3.46GHz (stock clock for the 3770K), and "About this Mac" shows my RAM as running at 0 MHz. All my other stats show up fine. At first I thought maybe my OC got wiped out somehow, so I booted into the bios and they're still there. So I booted up Windows 8.1 to double-check what frequencies it's detecting and it reports them correctly at 4.5GHz for the CPU and 1867MHz for the RAM. So I think my OC is still in tact. Although even if it was wiped out... that wouldn't explain the RAM reporting at 0 MHz. On the surface I think this is just a cosmetic issue, however my concern is that maybe it's not... maybe my CPU is running at 3.5GHz and not 4.5GHz in 10.10.3, which is quite a huge performance difference and more of a legitimate concern. However even if it is just cosmetic I'd still like to uncover the cause of this. FakeSMC and the 4 FakeSMC plugins are all loaded according to System Information, and they're all running the latest versions (1364). HWMonitor and iStat Menus are also fully updated. Booting with Chimera 4.1.0. Is anyone having similar issues? Anyone got any suggestions on where I can start to try to solve this issue? Thanks guys edit: So now I have reason to believe this isn't just a cosmetic issue. I just ran Geekbench and I'm only getting 13925 - http://browser.primatelabs.com/geekbench2/view/2552061 Previously whenever I ran Geekbench I'd get between 16500 and 17000. So I think my CPU actually is running at stock clocks... ugh
  5. I made new kext as an addition to HWSensors v3.3. Compatibility with OS 10.6 - 10.10 Currently it show only CPU temperature. May be later I make voltage and frequencies. Voluntaries welcomed. I am not sure with kozlek's project compatibility. Test with precations. (kozlek's version is not newer. It is a branch with own enumeration) Manual testing without installation: sudo -s chown -R root:wheel ~/Downloads/AmdCPUMonitor.kext chmod -R 755 ~/Downloads/AmdCPUMonitor.kext kextutil -v ~/Downloads/AmdCPUMonitor.kext This kext v1.0 AmdCPUMonitor.kext.zip Other files in the project (don't install all of them! For example you don't need IntelCPUMonitor) FakeSMC_plugins_746.zip New FakeSMC with Illumination version in System Profiler and no warnings in kernel.log FakeSMC.kext_Illumination.zip Minimum set includes FakeSMC+HWInfo Recommended installation (I have no installer so I propose you will use Terminal.app) sudo -s cp -r -v ~/Downloads/HWSensors/AmdCPUMonitor.kext /System/Library/Extensions/ and so on for all kexts that will have a sense for you ACPIMonitor.kext - for devices in DSDT. Only for advanced users! AmdCPUMonitor.kext - temperature for AMD CPU Andigilog.kext - for andigilog chip. Found on some Intel motherboard AnalogDevices.kext - for chips like ADT7470-7475 F718x.kext - for Fintek chip FakeSMC.kext - obligatory for any Hackintosh GeforceSensor.kext - for new NVidia Geforce cards HWInfo.kext - if you use Clover bootloader ICHSMBus.kext - an addition for Andigilog.kext IntelCPUMonitor.kext - temperature, voltage and frequencies for Intel CPU up to Haswell ITEIT87x.kext - for ITE chip, found on most Gigabyte motherboards NuvotonNCT677x.kext - for Nuvotone chip, found on new ASUS motherboards NVClockX.kext - for old NVidia cards PC8739x.kext - for NSC chip, found on Dell Inspiron only RadeonMonitor.kext - for Radeon videocard HD4000+ W836x.kext - for Winbond chips found on old ASUS motherboards X3100.kext - for Intel X3100 (GM965 chip) Monitor application to be used HWMonitor.app_731.zip New version andigilog.kext supports EMC6D103 chip. Advantages: - no spam in system.log - CPU usage only 0.1% - no panics - supported wide range of chips. Sources are available here https://www.assembla.com/code/fakesmc/subversion/nodes/738/HWSensors
×