Jump to content
About Just Joined group Read more... ×

1,164 posts in this topic

Recommended Posts

Advertisement

Worked a treat thank you for this great utility. I for one would not be comfortable building my mhac without this great tool. It gives me the piece of mind that my machine is running as expected so thank you again.

Share this post


Link to post
Share on other sites

hi Kozlak

 

strange think after crossing the 45 C i get a strange value

please can you check this

 

Sorry, sacaman1, I can't help you now. Looks like your hardware reports wrong values.

 

Hi kozlek.

Will you add support of HWMonitor to Snow Leopard 10.6.x?

 

Did you tested it on 10.6.x? Not to compile for 10.6 but use binaries from the package?

Share this post


Link to post
Share on other sites

Kozlek, here's a more complete spanish Localizable.strings, it contains all the LocalizedStrings existing in the HWMonitorEngine.m file. As you can see, all is working perfectly, thanks again.

 

"TEMPERATURES" = "TEMPERATURAS";

"DRIVES TEMPERATURES" = "TEMPERATURAS DISCOS";

"SSD REMAINING LIFE" = "DURACIÓN PREVISTA SSD";

"MULTIPLIERS" = "MULTIPLICADORES";

"FREQUENCIES" = "FRECUENCIAS";

"VOLTAGES" = "VOLTAJES";

"FANS" = "VENTILADORES";

"CPU Heatsink" = "Disipador CPU";

"GPU %X Board" = "GPU %X";

"GPU %X Core" = "GPU %X Core";

"GPU %X Proximity" = "Sensor de GPU %X";

"Northbridge" = "Northbridge";

"System Chipset" = "Chipset del Sistema";

"Ambient" = "Ambiente";

"CPU Package" = "CPU";

"CPU %X" = "CPU %X";

"CPU Core %X" = "CPU Core %X";

"Fan %X" = "Ventilador %X";

"CPU" = "CPU";

"Memory" = "Memoria RAM";

"Power/Battery" = "AlimentaciÓn/Batería";

"Quit HWMonitor" = "Salir de HWMonitor";

"No sensors found" = "No hay sensores disponibles";

"Main 12V" = "Principal 12V";

"PCIe 12V" = "PCIe 12V";

"Main 5V" = "Principal 5V";

"Standby 5V" = "Reposo 5V";

"Main 3.3V" = "Principal 3,3V";

"Auxiliary 3.3V" = "Auxiliar 3,3V";

"VRM Supply %X" = "AlimentaciÓn VRM %X";

"Power Supply %X" = "Fuente de alimentaciÓn %X";

 

hwmonitor.png

Share this post


Link to post
Share on other sites

no problem if you have time please take a look to it

 

And what's showing OpenHardwareMonitor in Windows, could you check please?

 

Kozlek, here's a more complete spanish Localizable.strings, it contains all the LocalizedStrings existing in the HWMonitorEngine.m file. As you can see, all is working perfectly, thanks again.

 

 

Thank you, added with latest revision.

Share this post


Link to post
Share on other sites

Hi Kozlek :)

 

this is the Italian translation

 

"TEMPERATURES" = "ТЕMPERATURE";

"DRIVES TEMPERATURES" = "ТЕМPERATURE HDD";

"SSD REMAINING LIFE" = "STATO DI SALUTE SSD";

"MULTIPLIERS" = "MOLTIPLICATORI";

"FREQUENCIES" = "FREQUENZE";

"VOLTAGES" = "VOLTAGGI";

"FANS" = "VENTOLE";

"CPU Heatsink" = "Dissipatore CPU";

"GPU %X Board" = "Scheda Video %X";

"GPU %X Core" = "GPU %X Core";

"GPU %X Proximity" = "Sensore GPU%X";

"Northbridge" = "Northbridge";

"System Chipset" = "Chipset di Sistema";

"CPU Package" = "CPU";

"CPU %X" = "CPU %X";

"CPU Core %X" = "CPU Core %X";

"Fan %X" = "Ventola %X";

"CPU" = "CPU";

"DIMM Modules" = "Moduli di Memoria";

"Power/Battery" = "Alimentazione / Batteria";

"Quit HWMonitor" = "Esci da HWMonitor";

"No sensors found" = "Nessun sensore disponibile";

 

 

Italian_Translation.txt.zip

Share this post


Link to post
Share on other sites

And what's showing OpenHardwareMonitor in Windows, could you check please?

 

 

 

this is the windows data

post-216126-0-69586100-1332282257_thumb.jpg

post-216126-0-60363500-1332282266_thumb.jpg

Share this post


Link to post
Share on other sites

this is the result

 

And it's ok? Seems system temperature is lower then it should be..

 

P.S. Sorry, sacaman1, I erroneously tought that you have Nuvoton chip. Still no changes for you.

Share this post


Link to post
Share on other sites

no it's the same wrong value again

 

don't worry i will wait until a new solution from your side

in all cases thanks a lot for your time and help

;-)

 

sacaman

Share this post


Link to post
Share on other sites

My results (System specs in my signature):

 

Build 8d05bbd

 

post-516935-0-75150300-1332440649_thumb.png

 

 

Build 0d2a0b1

 

 

post-516935-0-42555200-1332440633_thumb.png

 

 

 

 

Localization to PT (Português)

 

 

"TEMPERATURES" = "TEMPERATURAS";

"DRIVES TEMPERATURES" = "TEMPERATURAS DOS DISCOS";

"SSD REMAINING LIFE" = "DURAÇÃO PREVISTA DO SSD";

"MULTIPLIERS" = "MULTIPLICADORES";

"FREQUENCIES" = "FREQUêNCIAS";

"VOLTAGES" = "VOLTAGENS";

"FANS" = "VENTILADORES";

"CPU Heatsink" = "Dissipador da CPU";

"GPU %X Board" = "GPU %X Placa";

"GPU %X Core" = "GPU %X Núcleo";

"GPU %X Proximity" = "Sensor %X da GPU";

"Northbridge" = "Northbridge";

"System Chipset" = "Chipset do Sistema";

"Ambient" = "Ambiente";

"CPU Package" = "CPU";

"CPU %X" = "CPU %X";

"CPU Core %X" = "Núcleo da Cpu %X";

"Fan %X" = "Ventilador %X";

"CPU" = "CPU";

"Memory" = "Memoria RAM";

"Power/Battery" = "AlimentaÇÃo/Bateria";

"Quit HWMonitor" = "Sair do HWMonitor";

"No sensors found" = "NÃo há sensores disponíveis";

"Main 12V" = "Principal 12V";

"PCIe 12V" = "PCIe 12V";

"Main 5V" = "Principal 5V";

"Standby 5V" = "Repouso 5V";

"Main 3.3V" = "Principal 3,3V";

"Auxiliary 3.3V" = "Auxiliar 3,3V";

"VRM Supply %X" = "AlimentaÇÃo VRM %X";

"Power Supply %X" = "Fonte de alimentaÇÃo %X";

Share this post


Link to post
Share on other sites

The same situation also on my system in rig. With the latest revision no more power supply voltages

 

Also another question: how can i force to display all cpu cores in the HWmonitor app?

tnx

Share this post


Link to post
Share on other sites

HI! Can you help me to detect my mobility radeon 4570 on GPU stat? (id 95531002)

Thank you very much

Share this post


Link to post
Share on other sites

The same situation also on my system in rig. With the latest revision no more power supply voltages

 

Also another question: how can i force to display all cpu cores in the HWmonitor app?

tnx

 

Try latest revision.

 

HI! Can you help me to detect my mobility radeon 4570 on GPU stat? (id 95531002)

 

Thank you very much

 

 

This ID is already in the supported list in RadeonX plugin. HWMonitor should show GPU temperature and you should see RadeonMonitor related messages in kernel log.

Share this post


Link to post
Share on other sites

Working fine now.

 

I have several other fans that are not showing. Is there a way I can contribute ?

 

 

Revision c273f7d:

 

 

post-516935-0-02064000-1332517307_thumb.png

Share this post


Link to post
Share on other sites

I just added new feature to Super I/O plugins - value modifiers. Modifiers could be set in "Sensors Configuration" section of SuperIOFamily's info.plist.

 

It's impossible to use universal modifiers because different motherboard manufacturers have different implementations also for the same Super I/O chip models on different mobos. So it's up you to found proper modifiers values. There is couple of well known modifiers values for some mobos and Super I/O chipsets could be obtained from OpenHardwareMonitor project (see SuperIOHardware.cs file).

 

The formula used is: offset + value + (value - reference) * gain, there is value is the unmodified value read from the registers. The formula used in OpenHardwareMonitor for voltage is a bit different. For example in OpenHardwareMonitor: v.Add(new Voltage("+12V", 5, 27, 9.1f)) , second parameter (5) is VIN5, the 3rd parameter and 4th is the gain = 27 / 9.1 = 2.967. In the info.plist you should set 2.967 * 1000 (because of info.plist's Number could get only integer values):

 

post-258361-0-59368600-1332594885_thumb.png

 

At the end you could get a picture like this:

 

post-258361-0-98873900-1332594914_thumb.png

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

Announcements

  • Similar Content

    • By miliuco
      Install macOS 10.15 Catalina on Gigabyte P55-USB3 with Radeon RX 580 graphics card using a USB device created with the createinstallmedia command and Clover as bootloader. Instructions to install macOS 10.14 Mojave on this computer are almost identical, replacing Catalina app with Mojave, so this article is suitable for both versions of macOS. The Gigabyte P55-USB3 motherboard (and some others from the same brand with the P55 / H55 chipset) have made it easy to build a hackintosh and install macOS since 10 years ago. Although it is an old motherboard, the behavior with Mojave or Catalina is very good after changing the classic hard drive (HDD) for a solid state drive (SSD).

      Components of the hackintosh
      Gigabyte GA-P55-USB3 motherboard: P55 chipset, 1156 socket, ALC892 audio, Gigabit RTL8111D network, DDR3 RAM Intel Core i5-750 processor for socket 1156: 4 cores, 8MB cache, clock rate 2.66 GHz Fenvi FV-T919 wireless + Bluetooth card: PCI-Express, wifi is ac type, detected by macOS as Airport and Apple Bluetooth Radeon RX 580 8 GB graphics card: works OOB but with a few details to be considered, it has its own article.  
      Previous requirements
      Install macOS Catalina app in /Applications folder USB flash drive with at least 16GB prepared from Disk Utility with MBR partition scheme and formatted as Mac Os Plus (on older Gigabyte boards like mine, USB sticks partitioned with GUID scheme instead of MBR usually hang the system when booting) Recent version of Clover (I have used r5117) Recent versions of Lilu (at least 1.4.4) and WhateverGreen (at least 1.3.9) to fine-tune the behavior of the graphics card Recent version of RealtekRTL8111 (I have used 2.2.2) FaceSMC version 6.26-322 (newer versions disable automatic mounting of USB devices on my system).  
      Create install USB
      Run this command from Terminal (assuming the target device is called USB):
      Bash: sudo /Applications/Install\ macOS\ Catalina.app/Contents/Resources/createinstallmedia --volume /Volumes/USB /Applications/Install\ macOS\ Catalina.app
      Clover must be installed on the USB memory, I choose the following options:
      Bootloader > Install boot0af on the MBR CloverEFi > CloverEFI 64-bit SATA BIOS Drivers, 64 bit > Recommended drivers > FSInject + SMCHelper + XhciDxe BIOS Drivers, 64 bit > File System drivers > ApfsDriverLoader Install RC scripts on selected volume Optional RC scripts > Disable sleep proxy client.  
      You have to copy 4 kexts to the EFI/CLOVER/kexts/Other folder of the USB device: FaceSMC 6.26-322, Lilu 1.4.4, WhateverGreen 1.3.9 and RealtekRTL8111 2.2.2. Regarding the config.plist file, the most significant is:
      Boot > kext-dev-mode = 1 in Boot arguments GUI > Theme embedded, EmbeddedThemeType Dark, Screen Resolution 1920x1080, Preboot in Hide Volume Graphics > blank, nothing is checked except if foxbox solution is used to have more than 2 connectors enabled RT Variables > 0x28 in BooterConfig and 0x67 in CsrActiveConfig SMBios > iMac14,2 Sytem Parameters> Yes in Inject Kexts and check Inject System ID.  
      Install macOS Catalina

      Boot from the USB device and choose Install macOS from Install macOS Catalina. The installation program runs until the PC restarts. Here choose Install macOS from HDD (the name of the volume you are installing macOS on). With RX 580 graphics card, the screen goes black in this second phase of the installation, it is a phase in which the user has nothing to do until the PC is restarted so you can let it work until the Clover menu again. You have to choose Boot macOS from HDDto boot the installed system from the hard disk, the screen is recovered and you can configure the account and the initial options. From this moment the screen works fine.

      In summary:
      Boot from USB > Clover menu > Install macOS from Install macOS Catalina > screen works fine Boot from USB > Clover menu > Install macOS from HDD > black screen Boot from USB > Clover menu > Boot macOS from HDD > screen works fine.  
      Install Clover and kexts on the hard drive

      Clover needs to be installed on the disk where we just installed macOS. Options are the same as when installing it on the USB memory. You also have to copy the 4 kexts (FaceSMC 6.26-322, Lilu 1.4.4, WhateverGreen 1.3.9 and RealtekRTL8111 2.2.2) into the EFI/CLOVER/kexts/Other folder on the EFI partition of the disk. And review the config.plist file remembering the comments for the USB.

      If everything goes well, the computer starts from the hard disk with a running copy of macOS Catalina.
       
       

    • By Slice
      The thread splitted from HWSensors3.
       
      Tools to testing Radeon state.
      Load RadeonPCI.kext  
      RadeonPCI.kext.zip
       
      How to load
      sudo chown -R root:wheel ~/Downloads/RadeonPCI.kext sudo chmod -R 755 ~/Downloads/RadeonPCI.kext sudo kextutil -v ~/Downloads/RadeonPCI.kext and use RadeonDump utility
      RadeonDump1.zip
       
      Commands to see temperature
      Polaris
      ./RadeonDump1 -n 6b0,c0300014
      SeaIsaland
      ./RadeonDump1 -n 200,c0300014
       
      Old families
      ./RadeonDump1 -r 714,7f4
       
      Other possible methods to find a register for temperature
      ./RadeonDump1 -n 6b0,c0300e0c
      ./RadeonDump1 -n 6b0,1c5
      ./RadeonDump -n 6b0,d8200ca4
      ./RadeonDump -r 59800,59810
      ./RadeonDump -r 678,680

       
       
       
      01.12.2017
      Latest solution RadeonMonitor.kext here
      works for RX 460,480,580
      not works for HD7790, R9 290X?
       
      06.12.2017
      Here works also with HD7790, R9 290X
       
      14.12.2017
      Support VEGA here
       
      13.12.2017
      Version for test modern cards
      RadeonPCI5.kext.zip
       
      06.04.2020
      Version for Catalina
      RadeonPCI5-v2.kext.zip
    • 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.
       
×