Jump to content

2,089 posts in this topic

Recommended Posts

Advertisement
Just now, vector sigma said:

@jinbingmao, can I have a translation for:


 


"North Bridge" = "North Bridge";
"Total Power" = "Total Power";

"Total Power" is referred to the Watts consumed by the GPU.

 

And, is Battery correct?

"Battery" = "电池"; // singular

 

"Total Power"="显卡总功率"   

 

"North Bridge"="北桥"  "Battery"="coms电池"
5 minutes ago, vector sigma said:

@jinbingmao, can I have a translation for:


 


"North Bridge" = "North Bridge";
"Total Power" = "Total Power";

"Total Power" is referred to the Watts consumed by the GPU.

 

And, is Battery correct?

"Battery" = "电池"; // singular

 

Revise

Localizable.strings.zip

Share this post


Link to post
Share on other sites
5 hours ago, vector sigma said:

Understood. Please run this in terminal:


defaults read org.slice.HWMonitorSMC2

post the result

{

    BatteryTimeInterval = 3;

    CPUTimeInterval = "1.5";

    "CPU_Frequency_MAX" = 0;

    Dark = 1;

    FansTimeInterval = 3;

    GPUTimeInterval = 3;

    MediaTimeInterval = "297.4747474747475";

    MoBoTimeInterval = 3;

    RAMTimeInterval = 3;

    UseIPG = 1;

    dontshowEmpty = 1;

    expandAll = 1;

    expandCPUFrequencies = 1;

    expandCPUTemperature = 1;

    expandVoltages = 0;

    popoverHeight = 976;

    popoverWidth = 450;

    runAtLogin = 0;

    useGPUIOAccelerator = 1;

    useMemoryPercentage = 1;

}

需要点击一下,就可以显示出来了

Share this post


Link to post
Share on other sites

原来的版本启动后自动展开 “Intel Power Gadget“内容,后续版本需要鼠标点击一下才可以显示。原来是这样,是我没有细心的操作啊!

1.thumb.png.c2d207fe35a579cddb84fd20483e9d18.png

Edited by jinbingmao

Share this post


Link to post
Share on other sites
2 minutes ago, jinbingmao said:

原来的版本启动后自动展开 “Intel Power Gadget“内容,后续版本需要鼠标点击一下才可以显示。原来是这样,是我没有细心的操作啊!

这是想要的。 “Intel Power Gadget info”组仅包含永不更改的静态值。 我希望它保持这种状态,你还好吗?

This is wanted. The "Intel Power Gadget info" group contains static values that never change. I'd like it to stay that way, is it okay for you?

6 minutes ago, Amble said:

Is there english language file i can use to translate strings to another language?

Sure can be translated in any language, let me collect all the files to be translated. BTW what's the language?

Share this post


Link to post
Share on other sites
8 minutes ago, vector sigma said:

这是想要的。 “Intel Power Gadget info”组仅包含永不更改的静态值。 我希望它保持这种状态,你还好吗?

This is wanted. The "Intel Power Gadget info" group contains static values that never change. I'd like it to stay that way, is it okay for you?

Sure can be translated in any language, let me collect all the files to be translated. BTW what's the language?

这个无所谓,只是开始没有注意到,所以误以为不能显示。现在知道需要鼠标点击操作了,那就满意了。感谢你的劳动!

Share this post


Link to post
Share on other sites
1 hour ago, jinbingmao said:

这个无所谓,只是开始没有注意到,所以误以为不能显示。现在知道需要鼠标点击操作了,那就满意了。感谢你的劳动!

好。 无论如何,每个组都是可扩展的或可聚类的

Good.  Anyway each group are expandable or collassable :wink_anim:

1 hour ago, Amble said:

Is there english language file i can use to translate strings to another language?

I've just opened a topic here on how to make translations. I'm doing this in this moment, files will be there in few minutes. DONE!

Edited by vector sigma

Share this post


Link to post
Share on other sites
23 hours ago, vector sigma said:

好。 无论如何,每个组都是可扩展的或可聚类的

Good.  Anyway each group are expandable or collassable :wink_anim:

I've just opened a topic here on how to make translations. I'm doing this in this moment, files will be there in few minutes. DONE!

 

23 hours ago, vector sigma said:

这是想要的。 “Intel Power Gadget info”组仅包含永不更改的静态值。 我希望它保持这种状态,你还好吗?

This is wanted. The "Intel Power Gadget info" group contains static values that never change. I'd like it to stay that way, is it okay for you?

Sure can be translated in any language, let me collect all the files to be translated. BTW what's the language?

 

Thx. Finnish. I'll post it when it's done.

Share this post


Link to post
Share on other sites

This may be obvious to most, but exactly what is needed to run HWMonitorSMC2?  I can seem to successfully run it.  I've installed FakeSMC r.177 along with the appropriate KEXTs for my system.  HWMonitorSMC works but HWMonitorSMC2 does not.  

 

 

Share this post


Link to post
Share on other sites
15 hours ago, mbrettweigel said:

This may be obvious to most, but exactly what is needed to run HWMonitorSMC2?  I can seem to successfully run it.  I've installed FakeSMC r.177 along with the appropriate KEXTs for my system.  HWMonitorSMC works but HWMonitorSMC2 does not.  

 

 

The app at sourceforge require IntelPowergadget to work and you can find it here. I've fixed this already (lazy linking) but changes aren't committed because I was waiting the guy here that has problem with an external GPU but actually has not yet answered with the requested files.... and so to avoid repetitive big changes.

Anyway to night I'll finally do that commit since I've wait enough. In the mean time try this one:

 

HWMonitorSMC2.app_2.4.1.zip

 

... that has all the latest changes done until now. 

@Andrey1970, please check that app where I fixed spaces beteween the values and the units of measurement. Let me know.

 

Edited by vector sigma

Share this post


Link to post
Share on other sites
5 hours ago, vector sigma said:

please check that app where I fixed spaces beteween the values and the units of measurement. Let me know.

Looks good.

 

You added the Diode in group CPU. Now I see a double.

1835571660_2018-11-1421_25_19.png.612af79e3fc5328461fed3db6313740a.png

 

 

You can move DRAM power in RAM group? It would be good.

Share this post


Link to post
Share on other sites
6 hours ago, vector sigma said:

The app at sourceforge require IntelPowergadget to work and you can find it here. I've fixed this already (lazy linking) but changes aren't committed because I was waiting the guy here that has problem with an external GPU but actually has not yet answered with the requested files.... and so to avoid repetitive big changes.

Anyway to night I'll finally do that commit since I've wait enough. In the mean time try this one:

 

HWMonitorSMC2.app_2.4.1.zip

 

... that has all the latest changes done until now. 

@Andrey1970, please check that app where I fixed spaces beteween the values and the units of measurement. Let me know.

 

Hi vector sigma

with this version I have lost 2 cores again :)

(same behavior with fakesmc/virtualSMC and relative cpu kext)

previous 2.4.1 is ok for me

 

Screen Shot 2018-11-14 at 7.41.59 PM.png

Edited by fabiosun
whit-->with

Share this post


Link to post
Share on other sites
29 minutes ago, Andrey1970 said:

You added the Diode in group CPU. Now I see a double.

I think is a translation problem:

"Proximity" = "Датчик";     // CPU or GPU
"Diode %d" = "Датчик %d"; // CPU or GPU

The first is outside the CPU (Proximity = near), the second is inside the CPU. I think that Proximity translation is bad (the sensor I've added) .

29 minutes ago, Andrey1970 said:

You can move DRAM power in RAM group? It would be good.

I've already answered days ago. The fact is that this is inefficent because we have to query the driver and the framework multiple times for the CPU group and the RAM group, would like to avoid doing that or to make a new test version... but later :)

Edited by vector sigma

Share this post


Link to post
Share on other sites
9 minutes ago, fabiosun said:

Hi vector sigma

with this version I have lost 2 cores again

I've only make the code able to read sensors with new SMC keys with lower cases letters (i.e. "TC0c" vs "TC0C"). This is due to new iMac Pros that apparently uses the new lower one. Probably I've introduced a new bug, but in the meantime can you show me the SMC dump from the app?

Share this post


Link to post
Share on other sites
20 minutes ago, vector sigma said:

I think is a translation problem:

"Proximity" = "Внешний датчик";     // CPU or GPU
"Diode %d" = "Встроенный датчик %d"; // CPU or GPU
23 minutes ago, vector sigma said:

I've already answered days ago. The fact is that this is inefficent because we have to query the driver and the framework multiple times for the CPU group and the RAM group, would like to avoid doing that or to make a new test version... but later

OK, later. You not against if I will remind you of it?

Share this post


Link to post
Share on other sites
7 hours ago, vector sigma said:

sourceforge上的应用程序需要IntelPowergadget才能工作,您可以在此处找到它我已经解决了这个问题(延迟链接),但是没有提交更改,因为我在这里等待 外部GPU有问题,但实际上还没有回答所请求文件的人....所以为了避免重复大变化。

无论如何到了晚上,我终于做了那个承诺,因为我已经等了。同时试试这个:

 

HWMonitorSMC2.app_2.4.1.zip

 

...到目前为止已完成所有最新更改。 

@ Andrey1970,请检查该应用程序,我在值和测量单位之间固定了空格。让我知道。

 

“Proximity ” ? “Heatsink”?

1.png

在中文里 “Heatsink“指散热器    "Proximity" = "CPU表面温度"   "Heatsink" = "散热器"。这里是不是同一个意思。

Share this post


Link to post
Share on other sites
25 minutes ago, jinbingmao said:

“Proximity ” ? “Heatsink”?

Heatsink (CPU side)--> 1132307-a.jpg

 

 

 

Proxymity --> (sorry no image), can be just soldered in the motherboard very close to the CPU for example.

Edited by vector sigma

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