telepati Posted January 21, 2020 Share Posted January 21, 2020 VirtualSMC plugins working with Sensei.app 1 Link to comment Share on other sites More sharing options...
vector sigma Posted January 21, 2020 Share Posted January 21, 2020 3 hours ago, Andrey1970 said: @vector sigma multi it not always integer. It's a double, so you can write what you want, e.g. something like 0.009. Actually doesn't accept <= 0, but In HWMonitorSMC2.app will accept negative numbers also. 0 is treated as 1. Additionally there will be a new "skip" key... so that you'll be able to hide sensors you don't want to show. Usefull if you don't have an AUXFAN3 (for example) and you don't want to see "0 RPM" . 50 minutes ago, telepati said: VirtualSMC plugins working with Sensei.app No voltages. It just read smc keys published. 3 Link to comment Share on other sites More sharing options...
vector sigma Posted January 21, 2020 Share Posted January 21, 2020 (edited) 20 hours ago, rramon said: VIN6 = 1.212 Volts Sorry, still don't get what I need to do with the .plist Gigabyte Z370N Wifi.ioreg.zip Suppose VIN6 is it your +12V sensor.. you have to create a Dictionary named VIN6 that will contains name as String and multi as Number: VIN6 name = +12V multi = 10 where name will take the place of VIN6. Since your value is 1.212 multi will multiply 10 times (1.212x10) i.e. 12.12 Volts. The result will be: +12 = 12.12 Volts instead of 'VIN6 = 1.212 Volts'. The multi value depends by motherboards resistors I cannot know. Edited January 21, 2020 by vector sigma Link to comment Share on other sites More sharing options...
vector sigma Posted January 21, 2020 Share Posted January 21, 2020 13 hours ago, Regi Yassin said: because virtualsmc doesn't set IODeviceTree:/efi/platform/oem information, so we need lpc.plist? there is no way to auto detect the board itself? OEM informations are injected by Clover, so I'm pretty sure you're using Open Core. Should be nice to have the same informations somewere in nvram or ioreg. WAIT! Did Open Core have a boot log with such info? 1 Link to comment Share on other sites More sharing options...
ctich Posted January 21, 2020 Share Posted January 21, 2020 22 minutes ago, vector sigma said: OEM informations are injected by Clover, so I'm pretty sure you're using Open Core. Should be nice to have the same informations somewere in nvram or ioreg. WAIT! Did Open Core have a boot log with such info? Hi, according to the information from @vit9696, the "board" and "vendor" data can be obtained using variables: nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:oem-board nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:oem-vendor Variables will be added to OpenCore in a few days. 1 Link to comment Share on other sites More sharing options...
vector sigma Posted January 21, 2020 Share Posted January 21, 2020 5 minutes ago, ctich said: Hi, according to the information from @vit9696, the "board" and "vendor" data can be obtained using variables: nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:oem-board nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:oem-vendor Variables will be added to OpenCore in a few days. nice and easy, thanks! 1 Link to comment Share on other sites More sharing options...
vector sigma Posted January 21, 2020 Share Posted January 21, 2020 44 minutes ago, ctich said: Hi, according to the information from @vit9696, the "board" and "vendor" data can be obtained using variables: nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:oem-board nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:oem-vendor Variables will be added to OpenCore in a few days. Than this:SMCSuperIO.zip is ready for the new OC. 1 Link to comment Share on other sites More sharing options...
telepati Posted January 21, 2020 Share Posted January 21, 2020 (edited) 5 hours ago, vector sigma said: It's a double, so you can write what you want, e.g. something like 0.009. Actually doesn't accept <= 0, but In HWMonitorSMC2.app will accept negative numbers also. 0 is treated as 1. Additionally there will be a new "skip" key... so that you'll be able to hide sensors you don't want to show. Usefull if you don't have an AUXFAN3 (for example) and you don't want to see "0 RPM" . No voltages. It just read smc keys published. BTW I don't get it why one of mine fan shows 0 RPM? is it because of my H80i corsair? This cooler has two fans and I connected this cooler to AiO Pump header. Edited January 21, 2020 by telepati Link to comment Share on other sites More sharing options...
vector sigma Posted January 21, 2020 Share Posted January 21, 2020 (edited) [REMOVED] with Intel Power gadget v3.7+ support (adviced) and SMCSuperIO.kext support with autodetection Configurations must be made in: HWMonitorSMC2.app/Contents/SharedSupport/LPC/ Please, share your configurations, once made, at https://github.com/CloverHackyColor/HWMonitorSMC2, code wll be online tomorrow.. now I go to sleep Edited February 2, 2020 by vector sigma Beta app removed 2 Link to comment Share on other sites More sharing options...
jinbingmao Posted January 21, 2020 Share Posted January 21, 2020 (edited) resolved Edited January 24, 2020 by jinbingmao Link to comment Share on other sites More sharing options...
telepati Posted January 22, 2020 Share Posted January 22, 2020 @vector sigma is these volts are OK? Link to comment Share on other sites More sharing options...
vector sigma Posted January 24, 2020 Share Posted January 24, 2020 @rramon, @telepati, your sensors needs to be configured. If you have Windows, you can sync data with the help of this software: https://www.hwinfo.com/ ... and you will found so easy translating the output as sensors are (looks ) in the same exact order. Once you made yours, please share. Link to comment Share on other sites More sharing options...
Nuacho Posted January 24, 2020 Share Posted January 24, 2020 9 hours ago, vector sigma said: Once you made yours, please share. ASUS ROG STRIX Z370-F GAMING lpc.plist.zip 1 Link to comment Share on other sites More sharing options...
telepati Posted January 25, 2020 Share Posted January 25, 2020 10 hours ago, vector sigma said: @rramon, @telepati, your sensors needs to be configured. If you have Windows, you can sync data with the help of this software: https://www.hwinfo.com/ ... and you will found so easy translating the output as sensors are (looks ) in the same exact order. Once you made yours, please share. I dont have a Windows Link to comment Share on other sites More sharing options...
Andrey1970 Posted January 25, 2020 Share Posted January 25, 2020 @vector sigma I suggest not to use folders of vendors, and to use folders of SuperIO chips. If mobo.plist is absent, to apply default.plist for this SuperIO chip. For SuperIO chip determination: log show --predicate "processID == 0" --debug --last boot | grep SuperIO Look at attachment. LPC.zip 1 Link to comment Share on other sites More sharing options...
Andrey1970 Posted January 25, 2020 Share Posted January 25, 2020 I here thought, it is better to use the vendor too. Link to comment Share on other sites More sharing options...
vector sigma Posted January 25, 2020 Share Posted January 25, 2020 (edited) 2 hours ago, Andrey1970 said: @vector sigma I suggest not to use folders of vendors, and to use folders of SuperIO chips. If mobo.plist is absent, to apply default.plist for this SuperIO chip. For SuperIO chip determination: log show --predicate "processID == 0" --debug --last boot | grep SuperIO Look at attachment. LPC.zip 2 hours ago, Andrey1970 said: I here thought, it is better to use the vendor too. Hi, I agree with you, but: 1) at least the chip name should be posted in the same path of the "Sensors" dictionary as I cannot use "log show --predicate .." in a program. 2) It is also true that a default configuration will bring to no where as well, as a motherboard always have the same chip and a working solution there will be for a matching file. Edited January 25, 2020 by vector sigma Link to comment Share on other sites More sharing options...
joedm ru Posted January 25, 2020 Share Posted January 25, 2020 11 minutes ago, vector sigma said: at least the chip name should be posted in the same path of the "Sensors" dictionary as I cannot use "log show --predicate .." in a program. What would be the best option for you? Just chip ID or chip name, or both? I think I can either just add it as a key-value pair or even do it as a separated child item with chip id and sensors dictionary. 4 Link to comment Share on other sites More sharing options...
vector sigma Posted January 25, 2020 Share Posted January 25, 2020 (edited) 33 minutes ago, joedm ru said: What would be the best option for you? Just chip ID or chip name, or both? I think I can either just add it as a key-value pair or even do it as a separated child item with chip id and sensors dictionary. Sensors-->chipName = "ITEXXXXXXXX", so there will be all in the same place . Edited January 25, 2020 by vector sigma see next posts Link to comment Share on other sites More sharing options...
vector sigma Posted January 25, 2020 Share Posted January 25, 2020 (edited) 13 hours ago, Nuacho said: ASUS ROG STRIX Z370-F GAMING lpc.plist.zip Thanks. Anyway this lpc.plist.zip should be better? I.e. for example, there is no need to add the "name" if the key is already the same: Then I skipped VIN3 and VIN4 as both looks unused: Also sould be nice for the auto detection, to know what Clover say about your motherboard model name. If it is exactly 'ROG STRIX Z370-F GAMING', than the file should be named 'ROG STRIX Z370-F GAMING.plist' and so all the users with your motherboards will have your configuration loaded. P.S. Looks like the auto detection will work soon with OC as well. Edited January 25, 2020 by vector sigma 1 Link to comment Share on other sites More sharing options...
vector sigma Posted January 25, 2020 Share Posted January 25, 2020 (edited) 45 minutes ago, vector sigma said: Sensors-->chipName = "ITEXXXXXXXX", so there will be all in the same place . @joedm ru, forget the above, it is better this way: SMCSuperIO Sensors -> Dictionary chipName -> ITE[VenIdDevId] (string or data) i.e both are separate childs. thanks Edited January 25, 2020 by vector sigma Link to comment Share on other sites More sharing options...
Andrey1970 Posted January 25, 2020 Share Posted January 25, 2020 52 minutes ago, vector sigma said: It is also true that a default configuration will bring to no where as well, as a motherboard always have the same chip and a working solution there will be for a matching file. If there is no the configuration file for the motherboard, use default.plist for same vendor and same IO chip - it with big probability will yield the correct result. Link to comment Share on other sites More sharing options...
vector sigma Posted January 25, 2020 Share Posted January 25, 2020 6 minutes ago, Andrey1970 said: If there is no the configuration file for the motherboard, use default.plist for same vendor and same IO chip - it with big probability will yield the correct result. I have some doubts (may be something will be reported correctly), but ok. Link to comment Share on other sites More sharing options...
Andrey1970 Posted January 25, 2020 Share Posted January 25, 2020 9 minutes ago, vector sigma said: I have some doubts (may be something will be reported correctly), but ok. I saw different Gigabyte mobo with the IT8728F chip, worked with an identical configuration IT8728F chip. I won't tell that everything will always match, but it would simplify life to some users who won't be able to make the configuration file. Link to comment Share on other sites More sharing options...
Andrey1970 Posted January 25, 2020 Share Posted January 25, 2020 (edited) @vector sigma In master OpenCore andrey@iMac-Andrej ~ % nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:oem-vendor 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:oem-vendor Gigabyte Technology Co., Ltd. andrey@iMac-Andrej ~ % nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:oem-product 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:oem-product Z87X-UD4H andrey@iMac-Andrej ~ % nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:oem-board 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:oem-board Z87X-UD4H-CF andrey@iMac-Andrej ~ % But it doesn't work in v2.5.1beta from Edited January 25, 2020 by Andrey1970 1 Link to comment Share on other sites More sharing options...
Recommended Posts