Jump to content
vit9696

VirtualSMC — SMC Emulator

643 posts in this topic

Recommended Posts

Posted (edited)
16 hours ago, holyfield said:


Yes, you are correct!

Unfortunately I got the same issue on my old laptop (5200U) running latest Clover + Lilu + VSMC. (I didn't migrate to newer OC since I'm unable to find equivalent parameter combination to AptioMemoryFix.efi that can boot the system even with manual slide calc.)

The same configuration can boot Mojave 10.14.6 successfully but got exactly the same KP when booting a Catalina 10.15.2 Installer. Backtrace about VirtualSMC both reached _VirtualSMC_kern_start and stopped there. So I suppose here VirtualSMC is not involved by other kexts but itself while loading.

17163..jpg

Edited by gongzhen

Share this post


Link to post
Share on other sites
Advertisement

Hello Vector Sigma

New using the latest VirtualSMC, I get most temps I need from HWMonitorSMC2.

However, I would like to continue using Istat, but there nothing is shown.

My preferred temp app is still Istat. The main reason is the HWMonitorSMC2 is missing some key information like:

- Battery of Keyboard and Mouse (!)

- Network Traffic

 

Is there a way that these values can be translated so other Mac Software can work with the Sensor readings as well?

 

Thanks, Mike

 

Share this post


Link to post
Share on other sites

I am a bit confused about versions 1.0.9 and 1.1.0. With 1.0.9 I was able to get most of the sensors to read on my system. With 1.1.0 I see none. I assume that I now have to include the SMC*.kexts in order to see them? I put SMCProcessor.kext and SMCSuperIO.kext in the Kext>Other folder (I don’t believe I need SMCBatteryManager.kext or SMCLightSensor.kext) and now I see most of the sensor readouts.

 

What I don’t see are Core Frequencies or anything in the Main Logic board sections (although I do see frequencies in iStat). I'm guessing this is a HWMonitor issue?

588035254_ScreenShot2020-01-13at1_27_46PM.thumb.jpg.f6e3a5902d57660d46f57f4284ae8fb7.jpg

937971322_ScreenShot2020-01-13at1_30_22PM.thumb.jpg.f9a1cb53e2f0141c11bff301b635768f.jpg

Share this post


Link to post
Share on other sites
4 hours ago, pkdesign said:

I am a bit confused about versions 1.0.9 and 1.1.0. With 1.0.9 I was able to get most of the sensors to read on my system. With 1.1.0 I see none. I assume that I now have to include the SMC*.kexts in order to see them? I put SMCProcessor.kext and SMCSuperIO.kext in the Kext>Other folder (I don’t believe I need SMCBatteryManager.kext or SMCLightSensor.kext) and now I see most of the sensor readouts.

 

What I don’t see are Core Frequencies or anything in the Main Logic board sections (although I do see frequencies in iStat). I'm guessing this is a HWMonitor issue?

588035254_ScreenShot2020-01-13at1_27_46PM.thumb.jpg.f6e3a5902d57660d46f57f4284ae8fb7.jpg

937971322_ScreenShot2020-01-13at1_30_22PM.thumb.jpg.f9a1cb53e2f0141c11bff301b635768f.jpg

 

Enable Intel Power Gadget in Preferences and restart app.

Edited by Andrey1970

Share this post


Link to post
Share on other sites

It maybe because that VirtualSMC.efi is now "included /inside code " of OpenCore 0.54. So that OC Users  dont need that VirtualSMC.efi driver anymore. 

But i may be wrong;) 

Share this post


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

How come there's no VirtualSMC.efi in the latest release? Are we meant to carry the .efi forward from the last release?

 

check opencore changelog, virtualsmc.efi is moved into opencore.efi and represented in config.plist with 2 newly added options. 

Share this post


Link to post
Share on other sites
23 minutes ago, vit9696 said:

One can still get the standalone EFI module for unsupported bootloaders

Hi @vit9696 so do you feel OpenCore (not used yet by me) is the ideal match for VirtualSMC instead of Clover? Do you see Clover as becoming rather "unsupported" for VirtualSMC in the near future? Just to know so I may switch back to FakeSMC until I learn how to master OpenCore... Thank you! 

Edited by MacKonsti

Share this post


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

 

check opencore changelog, virtualsmc.efi is moved into opencore.efi and represented in config.plist with 2 newly added options. 

So is there any reason to set "AppleSmcIo" to true/yes if your system boots without it enabled?

Share this post


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

So is there any reason to set "AppleSmcIo" to true/yes if your system boots without it enabled?

 

No need, it is basically used for File Vault 2. if you don't enable FV2, then i don't think it is needed at the moment. 

Share this post


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

Thanks, this is the selector that crash:

GetThresholds

..from IntelPowerGadget.framework...

1 hour ago, pkdesign said:

When I enable Intel Power Gadget it causes HWMonitor to crash on startup. See crash report attached.

 

Then I have to completely uninstall in order to get it to work again.

HWMonitorSMC2_2020-01-13-200445_iMac.crash

Please create a file or directory in to your Desktop:

touch ~/Desktop/HWIgnoreIPG

restart HWMonitorSMC2.app. Should not crash anymore. If that is true,  please , delete the HWIgnoreIPG file, and rebuild your prelinked kernel:

sudo touch /System/Library/Extensions && sudo kextcache -u /

reboot. See if the problem persist.

Share this post


Link to post
Share on other sites

@vit9696 Noticed VSMC added the MacPro7,1 SMC dump in the latest commit but was wondering if those SMC keys are being added the system when using the master? Still getting this error in kernel logs.

 

2020-01-14 16:12:59.373648-0500  localhost kernel[0]: (IOPlatformPluginFamily) <IOPlatformPluginFamily`DebugPrint> HE2N_Key Does Not Exist, use kSMCPStatesEGPU for External GPU
2020-01-14 16:12:59.373649-0500  localhost kernel[0]: (IOPlatformPluginFamily) <IOPlatformPluginFamily`DebugPrint> HE2N_Key Does Not Exist, use kSMCPStatesEGPU for External GPU

Latest commit compiled from master on GitHub.

59    0 0xffffff7f86f04000 0x1e000    0x1e000    as.vit9696.VirtualSMC (1.1.0) 555F60E2-F4D9-3846-B68C-FB7BB906BD6B <42 12 8 6 5 3 2 1>

 

Share this post


Link to post
Share on other sites
21 minutes ago, Pavo said:

@vit9696 Noticed VSMC added the MacPro7,1 SMC dump in the latest commit but was wondering if those SMC keys are being added the system when using the master? Still getting this error in kernel logs.

 


2020-01-14 16:12:59.373648-0500  localhost kernel[0]: (IOPlatformPluginFamily) <IOPlatformPluginFamily`DebugPrint> HE2N_Key Does Not Exist, use kSMCPStatesEGPU for External GPU
2020-01-14 16:12:59.373649-0500  localhost kernel[0]: (IOPlatformPluginFamily) <IOPlatformPluginFamily`DebugPrint> HE2N_Key Does Not Exist, use kSMCPStatesEGPU for External GPU

Latest commit compiled from master on GitHub.


59    0 0xffffff7f86f04000 0x1e000    0x1e000    as.vit9696.VirtualSMC (1.1.0) 555F60E2-F4D9-3846-B68C-FB7BB906BD6B <42 12 8 6 5 3 2 1>

Don't you realize that your "AGPM" is the same.

 

Share this post


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

Don't you realize that your "AGPM" is the same.

Not sure I understand what you mean by this?

 

1 minute ago, Andrey1970 said:

 

It Doc only.

So not implemented yet, got it.

 

Share this post


Link to post
Share on other sites
On 1/14/2020 at 2:42 PM, vector sigma said:

Thanks, this is the selector that crash:


GetThresholds

..from IntelPowerGadget.framework...

Please create a file or directory in to your Desktop:


touch ~/Desktop/HWIgnoreIPG

restart HWMonitorSMC2.app. Should not crash anymore. If that is true,  please , delete the HWIgnoreIPG file, and rebuild your prelinked kernel:


sudo touch /System/Library/Extensions && sudo kextcache -u /

reboot. See if the problem persist.

When I create the file on the desktop and restart HWMonitor it fine. If I delete the file on the desktop it crashes.

HWMonitorSMC2_2020-01-14-171321_iMac.crash

 

 

UPDATE:
I figured it out. I had to update Intel Power Gadget to 3.7. It now works.

Edited by pkdesign
FIX

Share this post


Link to post
Share on other sites

Hi @vit9696 VirtualSMC Team

 

I've got a issue on Catalina 10.15.3 Beta 2 with latest release v1.1.0 (Clover Bootloader)

 

(AppleSMCLMU) AppleLMUController::smcGetKeyInfo Error: received error 0x84 when getting key info for 'ALRV'
(AppleSMCLMU) AppleLMUController::smcReadKey Error: received error 0x84 when reading key 'MSLD'
(AppleSMCLMU) AppleLMUController::smcReadKey Error: received error 0x84 when reading key 'ALV0'

 

Edited by Matgen84

Share this post


Link to post
Share on other sites

Can anyone try the command line attached to see if lpcb sensors are shown? Thanks in advace

 

 Removed (Mojave 10.14.4+ or any old OS with the swift runtime installed)

Edited by vector sigma
program removed, see next page

Share this post


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

Can anyone try the command line attached to see if lpcb sensors are shown? Thanks in advace

 

SMCSuperIO.zip  (Mojave 10.14.4+ or any old OS with the swift runtime installed)

SMCSuperIO not found.

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

×