Jump to content

VirtualSMC — SMC Emulator

vit9696

By vit9696,
in VirtualSMC

 Share
760 posts in this topic

Recommended Posts

ammoune78
ammoune78
Posted
Posted (edited)

Hi guy's, anybody knows how i can add MacBookPro7,1 support in the VirtualSMC=info.plist? Don't know which value to add!

Edited by ammoune78
Link to comment
Share on other sites
ammoune78
ammoune78
Posted
Posted

I'm having problem :wallbash: with Xcode 9.2 to build the latest release, it's about macbuild.tool that exit with code 1. Can someone share the latest build, from the source please, or to show the trick of that error?

Thanks

Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted
2 hours ago, ammoune78 said:

I'm having problem :wallbash: with Xcode 9.2 to build the latest release, it's about macbuild.tool that exit with code 1. Can someone share the latest build, from the source please, or to show the trick of that error?

Thanks

I use Xcode 10.2

here the latest build

Package-VSMC.zip

  • Thanks 2
Link to comment
Share on other sites
ammoune78
ammoune78
Posted
Posted
3 hours ago, chris1111 said:

I use Xcode 10.2

here the latest build

Package-VSMC.zip

 

Thank you @chris1111 so much, you helped me wasting time! Currently i'm updating Xcode, however, App Store said that i cannot install the 10.2 only 10.1, because i'm on 10.13.6. All my apps are stored in it, don't want to boot up Mojave now, because i'll have to install them all. I'll try with 10.13.6, if cannot I'll stick it with Mojave. Now that you uploaded the latest, i'll wait, until the next VirtualSMC update. I need to test it on an old HP Pavilion DV6-1380ek Core 2 Duo P8800 DDR3 1333 MHz ATI Mobility Radeon HD 4650, booting Clover in UEFI mode hhh, with MacBook Pro 7,1 spec :hysterical: .

  • Like 1
Link to comment
Share on other sites
Modmike
Modmike
Posted
Posted
41 minutes ago, Andrey1970 said:

There it is written that everything is good.
This message debug version.

 

If I understand properly I am getting this because I used debug version?  I was wondering about that when I used it.

Link to comment
Share on other sites
Tony Arnold
Tony Arnold
Posted
Posted
On 4/4/2019 at 11:00 AM, Modmike said:

No idea what that is. You have an X299, no idea what sensor chip they use. Hopefully, @vit9696 will know.

 

On the ASUS Prime X299 Deluxe I have, it appears to be a NCT6796D. 

 

I'd like to get all of the fans showing up if I can - would I do this by adding additional support to VirtualSMC for them, or is this an SSDT-fixable issue (the iMacPro1,1 SMBIOS I'm using appears to only recognise F1Ac and F2Ac for Fan 0 and Fan 1 RPMs.

Link to comment
Share on other sites
Modmike
Modmike
Posted
Posted (edited)
On 4/5/2019 at 8:03 PM, Tony Arnold said:

 

On the ASUS Prime X299 Deluxe I have, it appears to be a NCT6796D. 

 

I'd like to get all of the fans showing up if I can - would I do this by adding additional support to VirtualSMC for them, or is this an SSDT-fixable issue (the iMacPro1,1 SMBIOS I'm using appears to only recognise F1Ac and F2Ac for Fan 0 and Fan 1 RPMs.

 

That chip is already supported.  I’m not sure why, but not every HWMonitor or iStat shows all the fans.  Try HWMonitorSMC2 to see if you see more.

Edited by Modmike
Link to comment
Share on other sites
MacKonsti
MacKonsti
Posted
Posted (edited)

Hi everyone, I decided to give VirtualSMC a go on my NUC8i7BEH2 running Mojave 10.14.4 and Clover r4910.

 

Runs well and the CPU plugin shows values but there are CPU1 temperatures shown twice in HWSensors.app (v6.26.357 used) I think it's either "Ambient" or "Motherboard Proximity" but cannot be sure.

 

I would also like to ask you how to find the chipset so we can add FAN support, please, is there some Terminal executable that would reveal this chipset? The motherboard NUC8BEB specs PDF has no mention...

 

I am not a n00b hackintosher but when it came to SMC I did not fiddle about, as FakeSMC and plugins worked on my two older Haxies.

 

Thank you in advance for pointing me to the right tool so that I can report it and kindly ask anyone of you accessing Acidanthera's repo or @vit9696 to add the values officially...

Edited by MacKonsti
Link to comment
Share on other sites
Modmike
Modmike
Posted
Posted
38 minutes ago, MacKonsti said:

Hi everyone, I decided to give VirtualSMC a go on my NUC8i7BEH2 running Mojave 10.14.4 and Clover r4910.

 

Runs well and the CPU plugin shows values but there are CPU1 temperatures shown twice in HWSensors.app (v6.26.357 used) I think it's either "Ambient" or "Motherboard Proximity" but cannot be sure.

 

I would also like to ask you how to find the chipset so we can add FAN support, please, is there some Terminal executable that would reveal this chipset? The motherboard NUC8BEB specs PDF has no mention...

 

I am not a n00b hackintosher but when it came to SMC I did not fiddle about, as FakeSMC and plugins worked on my two older Haxies.

 

Thank you in advance for pointing me to the right tool so that I can report it and kindly ask anyone of you accessing Acidanthera's repo or @vit9696 to add the values officially...

 

What motherboard do you have?  4 sensors were just added but you will need to compile yourself, there is no release yet. You can use Hackintool to quickly and easily compile it if you want.

Link to comment
Share on other sites
Tony Arnold
Tony Arnold
Posted
Posted
26 minutes ago, Modmike said:

What motherboard do you have? 

 

I have the ASUS Prime X299 Deluxe, and I can only see Fan0 and Fan1, despite having fans attached to Fan2 and Fan3 - how can I work out the info needed to figure out which chipset is not supported on my board?

Link to comment
Share on other sites
MacKonsti
MacKonsti
Posted
Posted (edited)
52 minutes ago, Modmike said:

What motherboard do you have?  4 sensors were just added but you will need to compile yourself, there is no release yet. You can use Hackintool to quickly and easily compile it if you want.

 

Hi @Modmike I saw that you were pushing some Winbond additions to the repo :)

I have the Intel NUC mini-PC, the model is NUC8i7BEH2 and the motherboard is NUC8BEB per Intel that's Bean Canyon generation; it runs a Coffee Lake CPU i7-8559U.

My other NUC that's Haswell generation, has Nuvoton chipset detected per FakeSMC's original kext plugin. Could be that Intel stil uses this brand in the latest NUC models.

 

I had already ran lspci but not sure if this helps, I am attaching this here. You're referring to the "PCI" section of Hackintool? It's a rather new tool and I need to figure out a way to get familiar with it :D

 

Also, can we build the project from Terminal with Command Line Tools instead of getting Xcode, like in the good old days? Any ideas?

Thank you and everyone again!

 

lspci-nn.txt

Edited by MacKonsti
Link to comment
Share on other sites
MacKonsti
MacKonsti
Posted
Posted (edited)
On 4/8/2019 at 12:06 AM, Modmike said:

What motherboard do you have?

 

Hi @Modmike and @vit9696 I have been reading last night the whole thread but could not find a proposed way to extract the chipset info, e.g. via some Linux distro?

 

I booted up my Intel NUC8i7BEH2 with Ubuntu 18.04.02 and in Terminal, installed some packages (proposed on other websites) like lshw and inxi but to no avail. No LPC or I/O chipset found.

I have not tried dmidecode or hw-probe to be honest, they are so many, can't see which one is more recent/best. Only trying out sensors while setting them up, I got:

  

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): y
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Intel digital thermal sensor...                             Success!
    (driver `coretemp')
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               Yes
Found unknown chip with ID 0x8987

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): y
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): y
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): y
Found unknown SMBus adapter 8086:9da3 at 0000:00:1f.4.
Sorry, no supported PCI bus adapters found.

 

Any suggestion what tool is best to use to determine the chipset that may be available for fans? I am afraid on this NUC, Intel is not passing control at all to any OS.

 

Also, I have installed the latest Intel Power Gadget v3.3.5 but I don't get CPU Frequency and Multiplier, should we do something more? What is the framework to check is properly installed? Running 10.14.4 with simple boot in Clover r4910 no FileVault etc. therefore sans VirtualSMC.efi.

 

Many thanks to both and everyone here for your input. I se the NUC as Macmini8,1

 

UPDATE: On a Polish website https://forum.dug.net.pl/viewtopic.php?id=29814 there is a mention of "ITE IT8987D" that some member calls it "a strange chipset" so could that be it? Any idea if it could be supported?

 

NEW UPDATE: The mention if ITE made me seek again the PDF specs of the motherboard NUC8BEB so there is now a clear mention. Who can please help to add it on the repo code?

 

Quote

Hardware monitoring subsystem, based on an ITE Tech. IT8987E-VG embedded controller, including:

  • Voltage sense to detect out of range power supply voltages

  • Thermal sense to detect out of range thermal values

  • One processor fan header

  • Fan sense input used to monitor fan activity

  • Fan speed control

 

Edited by MacKonsti
Found the chipset = ITE IT8987E-VG
Link to comment
Share on other sites
steve3d
steve3d
Posted
Posted

Hi there, I have a gigabyte z390 aorus master board with i9-9900k, and I'm running 10.14.5 beta, because I have Radeon VII card, so after I change my smbios to iMac19,1, all my sensors are gone now with iStat menu, I can only get the temperature of my ssd and hd drive, and when os is booting there is a log says:

`kernel: (kernel) SMCSuperIO:    ssio @ failed to detect supported SuperIO chip`

 

but if I change smbios to iMac18,x, all sensors except fan speed are good.

Link to comment
Share on other sites
Modmike
Modmike
Posted
Posted
On 4/9/2019 at 4:47 PM, MacKonsti said:

 

Hi @Modmike and @vit9696 I have been reading last night the whole thread but could not find a proposed way to extract the chipset info, e.g. via some Linux distro?

 

I booted up my Intel NUC8i7BEH2 with Ubuntu 18.04.02 and in Terminal, installed some packages (proposed on other websites) like lshw and inxi but to no avail. No LPC or I/O chipset found.

I have not tried dmidecode or hw-probe to be honest, they are so many, can't see which one is more recent/best. Only trying out sensors while setting them up, I got:

  


Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): y
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Intel digital thermal sensor...                             Success!
    (driver `coretemp')
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               Yes
Found unknown chip with ID 0x8987

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): y
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): y
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): y
Found unknown SMBus adapter 8086:9da3 at 0000:00:1f.4.
Sorry, no supported PCI bus adapters found.

 

Any suggestion what tool is best to use to determine the chipset that may be available for fans? I am afraid on this NUC, Intel is not passing control at all to any OS.

 

Also, I have installed the latest Intel Power Gadget v3.3.5 but I don't get CPU Frequency and Multiplier, should we do something more? What is the framework to check is properly installed? Running 10.14.4 with simple boot in Clover r4910 no FileVault etc. therefore sans VirtualSMC.efi.

 

Many thanks to both and everyone here for your input. I se the NUC as Macmini8,1

 

UPDATE: On a Polish website https://forum.dug.net.pl/viewtopic.php?id=29814 there is a mention of "ITE IT8987D" that some member calls it "a strange chipset" so could that be it? Any idea if it could be supported?

 

NEW UPDATE: The mention if ITE made me seek again the PDF specs of the motherboard NUC8BEB so there is now a clear mention. Who can please help to add it on the repo code?

 

 

 

You can try this but I don't have high hopes, I am pretty sure the registers are different.  Let me know if it worked, bonne chance!

Archive.zip

Link to comment
Share on other sites
hackattak
hackattak
Posted
Posted
On 4/9/2019 at 7:46 PM, steve3d said:

Hi there, I have a gigabyte z390 aorus master board with i9-9900k, and I'm running 10.14.5 beta, because I have Radeon VII card, so after I change my smbios to iMac19,1, all my sensors are gone now with iStat menu, I can only get the temperature of my ssd and hd drive, and when os is booting there is a log says:

`kernel: (kernel) SMCSuperIO:    ssio @ failed to detect supported SuperIO chip`

 

but if I change smbios to iMac18,x, all sensors except fan speed are good.

 

Are you using only that Radeon VII now?

Everything working totally natively with the beta version?

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...