Jump to content
vit9696

VirtualSMC — SMC Emulator

709 posts in this topic

Recommended Posts

@Andrey1970, looks like you cannot receive private messages, otherwise all these tests will not mess this topic Lol.

 

Something get auto released so early, otherwise you should be able to see vendor and board in the preferences. Please put the app in your Desktop and run it with the Terminal:

~/Desktop/HWMonitorSMC2.app/Contents/MacOS/HWMonitorSMC2

Please post the result

 

[REMOVED]

 

Edited by vector sigma
beta app removed

Share this post


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

@Andrey1970, looks like you cannot receive private messages, otherwise all these tests will not mess this topic Lol.

 

Something get auto released so early, otherwise you should be able to see vendor and board in the preferences. Please put the app in your Desktop and run it with the Terminal:


~/Desktop/HWMonitorSMC2.app/Contents/MacOS/HWMonitorSMC2

Please post the result

 

 

HWMonitorSMC2.app.zip

 

I now enable private messages. It is possible to write now.

 

Last login: Sat Jan 25 20:45:33 on ttys000

andrey@iMac-Andrej ~ % ~/Desktop/HWMonitorSMC2.app/Contents/MacOS/HWMonitorSMC2

board = Z87X-UD4H-CF

vendorShort = NULL

Share this post


Link to post
Share on other sites

I got different Order of sensors with 2 scenario boot,,

Windows Boot Manager => enter, and
OpenCore BOotloader => enter

Which one should i use???

HWInfo-Ori.png

HWInfo.png

Share this post


Link to post
Share on other sites
12 minutes ago, Andres ZeroCross said:

I got different Order of sensors with 2 scenario boot,,

Windows Boot Manager => enter, and
OpenCore BOotloader => enter

Which one should i use???

HWInfo-Ori.png

HWInfo.png

 

 

Use Windows Boot Manager, don't use OpenCore -> Windows, because HWiNFO will think that at you real Mac, which you don't have.

Share this post


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

 

 

Use Windows Boot Manager, don't use OpenCore -> Windows, because HWiNFO will think that at you real Mac, which you don't have.

Thanks,, so still need some "magic touch" from @vector sigma

Untitled.jpg

Share this post


Link to post
Share on other sites
1 minute ago, vector sigma said:

Delete name=VBAT under the VBAT dictionary as is already VBAT, give me the plist. (with the help of Andrey I solved the autodetection problem)


Just little different from Z87X-UD4H-CF,, here is the plist file

 

Z170X-Gaming 7.plist

Share this post


Link to post
Share on other sites
58 minutes ago, Andres ZeroCross said:

Which version HWMonitorSMC2 did you use???

I give him in PM. But is not finished.

 

@Andrey1970 have you SMCSuperIO.kext v1.1.1 already built for me? built!

Edited by vector sigma

Share this post


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

I give him in PM. But is not finished.

 

@Andrey1970 have you SMCSuperIO.kext v1.1.1 already built for me?

 

I have used SMCSuperIO v1.1.1

image.thumb.png.e7d8e97f7dd60801f4489393c4dfc62e.png
 

Edited by Andres ZeroCross

Share this post


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



Which version HWMonitorSMC2 did you use???

 

In OpenCore necessary to set ExposeSensitiveData=14

Version in Vector PM.

Edited by Andrey1970

Share this post


Link to post
Share on other sites
 

In OpenCore necessary to set ExposeSensitiveData=14

Version in Vector PM.

 

 

I have done it, i have set 15 in my ExposeSensitive data from last night.

 

 

Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites

@joedm ru i had a lot of problems in retrieve the ChipName property, until i realize that the key is published this way:

\U0421hipName

and even the ioreg command line refuse to show it, so I made the code this way:

if (ioreg) {
    auto chipName = OSString::withCString(dataSource->getModelName());
    const OSSymbol *cn = OSSymbol::withCString("ChipName");
    ioreg->setProperty(cn, chipName);
    chipName->release();
}

This is the fixed file SMCSuperIO.cpp.zip (please don't copy/paste from the forum)

 

 

Guys, try the following app and the following SMCSuperIO.kext, otherwise wont work:

 

 

 

 

 

Help in making the configuration:

use this command line:  to create the right  directory structure for HWMonitorSMC2.app. The program will show OEM informations and not last the LPC chip name needed to correctly place the configuration in the appropriate sub directory. ~/Desktop/LPC/Vendor/ChipName/Board.plist will be created. Of course this is not a valid configuration: you have to correct it with real values.

 

Note: users that already posted their configurations should run hwmlpcconfig and tell me the new path to make them working again.

 

P.S. the autodetection will work only with Clover and with very last OpenCore.

Edited by vector sigma
Beta app removed

Share this post


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

users that already posted their configurations should run hwmlpcconfig and tell me the new path to make them working again.

 

LPC/Gigabyte/ITE IT8728F/Z87X-UD4H-CF.plist

 

1427325231_2020-01-2620_52_25.png.a690a1135f2c68ccd51a3abbdffd16c2.png

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

×