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

2,089 posts in this topic

Recommended Posts

Hi Slice

No way to compile to have both 32 & 64 arch supported?

It is possible but I have no 10.7 for this now. If you have it then you can compile the project to 32/64 fat.

Share this post


Link to post
Share on other sites
Advertisement

Hi,

 

I found this forum when I was looking for a temperature monitor solution for my Gigabyte AMD RX Vega 64 GPU.

 

You’re latest HwSensor pluing’s and Apps is working just fine (GPU temp), but I can’t control any fans at all.

I’m not looking solution for gpu fan controller, since it is not possible I guess?

I just need Cpu, System and Aux Fan controller to get it work.

I installed a new cooling system to my Vega, with Morpheus II Core Editionin, and it would be great to get temp monitor.

 

Cpu, System and Aux Fan control is just working nice with Rehabman FakeSMC and plugins, but Gpu monitor missing!

 

I've been trying all day to get it work even with dsdt patch, with no luck!

I'm I missing someting?

if possible, you could help a bit?

Here is my dsdt, and ioreg files if needed?

Thanks a lot for the great work!

iMac17,1.zip

Share this post


Link to post
Share on other sites

post-2200747-0-64378300-1518082174_thumb.pngpost-2200747-0-61450400-1518082195_thumb.png

No way to get AMD Radeon FAN monitoring.

May be some new developer will think about.

Thanks slice,

but I did not mean to control Vega gpu fan at all! 

Just to monitoring gpu temperature.

Like I said, I have I changed the original fan system (which is like a jet-plane most of the time) to

Raijintek MORPHEUS II Core Edition, and Fans are hook up to CHA_FAN (pwn mode 4-pin) at mobo.

 

I can control all the fans with Rehabman FakeSMC, but not with you’re latest HwSensor. And RehabMan Fakesmc Gpu temp monitor is missing, and your HwSensor plugins are showing all the fans and GPU monitor, but can’t change them CPU Fan, System Fan and Aux Fan (where is my gpu fans pluged)

 

Thanks a lot Slice!

Share this post


Link to post
Share on other sites

How can I write dual gpu support? 

This is open-source project

        if ((vendor_id==0x1002) && (class_id == 0x030000)) {
          InfoLog("found Radeon chip id=%x ", (unsigned int)device_id);
          VCard = device;
          ret = 1; //TODO - count a number of cards
          break;
        }

Share this post


Link to post
Share on other sites

 

This is open-source project

        if ((vendor_id==0x1002) && (class_id == 0x030000)) {
          InfoLog("found Radeon chip id=%x ", (unsigned int)device_id);
          VCard = device;
          ret = 1; //TODO - count a number of cards
          break;
        }

Ok. I add 2 in this section. 

if ((vendor_id==0x1002) && (class_id == 0x030000)) {
          InfoLog("found Radeon chip id=%x ", (unsigned int)device_id);
          VCard = device;
          ret = 2; //TODO - count a number of cards
          break;
        }

But still only one gpu in hwMonitor.post-916820-0-53203000-1519309352_thumb.png

Share this post


Link to post
Share on other sites

..hey devs, looking for an assist getting sensors read... chipset SCH5617...not currently supported by LPCSensors plugin....I've found some info, and an app in windows that does read from the chip (Hmonitor Version 4.5.4.2) but I'm not knowledgeable enough to tear into the app and see how it works.....

 

 

Hmonitor Version 4.5.4.2 Pro 02ACFA04

(Trial)

H/W diagnostics info:

Windows 8 Professional x64 Version 6.2.9200 

Manufacturer: LENOVO

Board model: ThinkCentre M57

Version: LENOVO

BIOS vendor: LENOVO

BIOS version: 2RKT64AUS, Release date: 11/24/2011

Chipset: 29B08086

Vendor ID: 303817AA

SouthBridge: 29148086

SMB port used: 1C20

CPU:Intel® Core2 Quad CPU  Q9550 @ 2.83GHz

CPUId:0-6-7-A

Cores:1

Internal Freq=2826.0 MHz

External Freq=403.71 MHz

Multiplier=7.0

SystemBus Freq=21.801 GT/s 

Thermo control configuration:

Full Throttle:100.0%

AMD Low Power mode:Disabled

Device:None Throttle:25.0% Enable at:70.0°C Disable at:65.0°C

Main Sensor: SCH5617

Poll intervals: Sensors=5 sec, HDDs=5 min, Warnings=5 sec

EventLog: Disabled, EventLog.txt

DataLog: Disabled, DataLog.txt

Loginterval=1 min, LogRotation=Never

 

Monitored data values:

Mainboard=xx.x°C (0,Auto,0.0°C)

CPU1=xx.x°C (1,Auto,0.0°C)

CPU1 Core=41.0°C (1,CoreTemp,0.0°C)

CPU0 Core=44.0°C (0,CoreTemp,0.0°C)

Chassis=1449 rpm

CPU1=xxxx rpm

CPU2=337 rpm

Power=xxxx rpm

Core=+x.xxV

Aux=+x.xxV

+3.3V=+x.xxV

+5V=+x.xxV

+12V=+xx.xxV

-12V=-xx.xxV

-5V=-x.xxV

HDD1 temp=27.0°C ST9500420AS 0003LVM1 SATA

HDD2 temp=40.0°C ST380815AS 3.CCA SATA

VGA device: NVIDIA GeForce GTX 745

VGA Device ID: 138210DE,106510DE.A2

VGA Acceleration Level: 0

VGA sensor: ForceWare

VGA GPU=50.0°C

VGA Env=xx.x°C

VGA Fan=xxxx rpm (xx%)

VGA Core=+x.xxV

VGA Bus=+x.xxV

 

 

 

 

I'll include what info I could find...please find attached 2 pdf files, one relates specifically to the SCH5617, the other is data sheet for SCH5627P but refers to SCH5617 differences (hoping it supplies some useful tidbits)
 
 
 
 
 
 
 
...hoping for a reply...thx

 

 

Edited by RobertX
re-attached files...waiting for replies

Share this post


Link to post
Share on other sites

Already done.

 

Right, sorry. I did't see any mention of 0x67EF, particularly at radeon_chipinfo_gen.h, so didn't expect it to work. But now I see that it does.

Share this post


Link to post
Share on other sites

Hi. Sorry if I this has been already asked... Is there  some version of gpu sensors to read clocks and usage of 1080ti?

 

I'm using binaries from HWSensors.6.26.1440 (last version) . Now the sensor only reads temps. I know that in this version,  this options are deactivated to avoid KP. I don´t know if there is some version patched.

Share this post


Link to post
Share on other sites

Very nice look in HWMmonitorSMC v2 beta. Good job @Slice.

Except new GUI what is the differences? 

attachicon.gifZrzut ekranu 2018-02-28 o 14.35.12.png

I made this new app in swift 4 and is marked as beta because has bugs that I have solved locally (later changes will be online). I've added in the meantime also the read of the RAM (total, free inactive and available).

 

  • 10.10 is the minimum OS version
  • translated in English, Italian and Russian (may be that Slice needs to look at it and correct where needed), but every languages supported by macOS can be added. When I finished to add functionalities I'll let you know for the localizable files.
  • CPU frequencies/temperatures are now separated from other stuff.
  • HD/ssd (life or temperature) are now on the same group called "Media healt"
  • The popover (the view) can be detached to become a normal window that you can size as you wish (persistent after a restart). At the bottom right there's a lock.. if unlocked (as per default) you can drag the popover to become a window, if loked you can resize it when still appended, idea that @fabiosun gave me.
  • Auto detection of dark appearance of macOS so that the view will follow him (vibrant ligh or vibrant dark).
  • By double clicking on any row of the view you can expand or collapse a group or if you do that on a sensor you can make it favorite and see values on the top bar as for the usual app.
  • At bottom left there's a gear, the Preferences: post-2078499-0-28347800-1520006561_thumb.png. You can see new options, but the best for me is the new slider to determine the interval to update sensors. 3 seconds is the minimum (default) to 10 seconds. Also you can force dark appearance on a normal system if you like it.

 

 

 

more images:

 

 

post-2078499-0-12897100-1520007538_thumb.png

post-2078499-0-67501500-1520007546_thumb.png

post-2078499-0-11126900-1520007558_thumb.png

 

 

 

 

@Slice, after uploaded the new app os sourceforce I've immediately sent you an email through sf itself, but something tells my that you did not see this message. Anyway tell me what you think.

 

TODO:

 

s.m.a.r.t. sensors need an update for new ssd because the bit for the temperature is somewhere else. 

Add s.m.a.r.t. reading for nvme drives

..tell something to me. 

 

 

EDIT 

 

Its on SourceForge?

 

app attached

HWMonitorSMC_v2.0.1_Beta.app.zip

Edited by vector sigma

Share this post


Link to post
Share on other sites

@vector sigma

 

Nice job! thanks man :)

 

Just out of curiosity can we ever have control of the speed of fans? specially GPU fans?

 

for NVidia we should read/set the cool-bit 0x04 and not sure is in the video bios/gop. (no idea for AMD).

Share this post


Link to post
Share on other sites

for NVidia we should read/set the cool-bit 0x04 and not sure is in the video bios/gop. (no idea for AMD).

Where exactly should we implement this code? sorry for being such a noob  :blush:

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