Jump to content

2,082 posts in this topic

Recommended Posts

Advertisement

I created a plugins folder under Contents,  then added the kexts I loaded the pkg file to an USB drive, then moved the FakeSMC.kext and the plugin files i needed to the relevant EFI kext directories in Clover. This was to avoid the installer writing to S/L/E.

 

See here what I mean - it appears to work very well.

 

http://d.pr/i/ISFA

Thanks, this is what I wanted to do.

Share this post


Link to post
Share on other sites

Thanks  Slice, working with iStat Menus 5 on 10.10 public beta, all sensor of my motherboard ,  GPU does not show thats iStat menus 5 issue , with HWMonitor GPU and all mobo sensor give temps. FakeSMC.kext was going to EFI/CLOVER/kexts/Other on my HD,  move it to HD EFI partition EFI/CLOVER/kexts/Other to make it work. i don't know how to attach a image.

 

Thank you Slice 

 

 

Share this post


Link to post
Share on other sites

@iAstroboyid,

 

I have an older version of iStat Menus (4.1) which shows incorrect frequencies with Slice's HWSensors/FakeSMC but OK with Kozlek's (but Kozlek's doesn't have motherboard sensors for my laptop).  Haven't upgraded iStat since reports of it crashing in 10.9.1 & 10.8.5.

post-846696-0-08234500-1406553121_thumb.

 

but frequencies are correctly shown with the included NWMonitor in Slice's package ...

 

post-846696-0-30836400-1406552947_thumb.

 

Does iStat Menus v5 show frequencies correctly for you with Slice's FakeSMC?  Thanks in advance.

Share this post


Link to post
Share on other sites

Hi! Very much a Hackintosh beginner here, so I probably did some obvious mistake..

 

Anyway, I'm running 10.10 on a Gigabyte GA-Z87MX-D3H with ATI graphics. I installed with CPU type = Intel, LPC = ITE87xx, GPU = ATI/AMD, and ofc the FakeSMC kext. Made sure to rebuild caches, repair permissions and such. The computer boots fine, but I have no sensor values at all. I have tried with iStat Menus, HWMonitorSMC and K-Stat-i, same thing in all of them (no sensor value at all). HWMonitorSMC says "No sensors found or FakeSMCDevice unavailable". I have done no other dsdt / ssdt patching, just some minor things in config.plist to ger graphics running and such.

 

Any suggestions where to go from here? I have no clue what the problem might be.

Share this post


Link to post
Share on other sites

does this branch support fan control like kozlek's?

No.

There was Navi's utility to fan control but the work was not finished.

For me there is no sense to control fan.

Share this post


Link to post
Share on other sites

Hi all,

 

I created an installer for my version of FakeSMC with plugins and applications latest revision.

 

Compatibility from 10.6 up to 10.10.

Test, please.

attachicon.gifScreen Shot 2014-07-28 at 13.04.43.png

Download here: HWSensors.pkg.zip

 

Thank you Slice. It works great for me on Mavericks 10.9.5 with my Core i7 Nehalem laptop.

 

This is a much needed upgrade for me. I was still using your old FakeSMC v4 rev 725, but it never let me down.

 

Unfortunately, my Asus laptop ITE chip is unsupported. I got the ITE8502E according to my laptop schematics.

 

I was previously using ACPISensors. Is there a difference with your current ACPIMonitor?

 

For some reason, in the latest HW Monitor and IStat Menus v5.0.2, the CPU multiplier is in the x17000-33000 range. The Kozlek branch shows the correct cpu multiplier values. It apparently has something to do with your branch.

Share this post


Link to post
Share on other sites

Real MAC is not generated and check Frequency/CPUMuliplier. It is for our choice how to code this. Some day kozlek decided to change definition 1000 times in both kext and in monitor. If you want correct value you should use kext and monitor from the same package my or kozlek. And same version.

Share this post


Link to post
Share on other sites

Slice do your fakesmc supports 771 xeons? I got x5472 same as real Mac pro 3,1 and I need tscsync package to enable 4 cores. Kozlek's hw monitor worked in Mavericks but in Yosemite fan speed is missing.

Share this post


Link to post
Share on other sites

Slice do your fakesmc supports 771 xeons? I got x5472 same as real Mac pro 3,1 and I need tscsync package to enable 4 cores. Kozlek's hw monitor worked in Mavericks but in Yosemite fan speed is missing.

What about your question? tscsync? monitor? fakesmc? IntelCPUmonitor? fan speed?

My IntelCPUmonitor supports xeons. This is the direct answer to your question.

Share this post


Link to post
Share on other sites

Hello slice

Question: HWSensors you can use destination kext EFI/Clover/kext/10.10

or no, the EFI folder hidden

Thanks

 

Fabio

mkdir /Volumes/TEFI
mount -t msdos /dev/disk1s1 /Volumes/TEFI

 

 
 
This is very old cult of Vanilla System: "I want to not place anything into SLE to keep the system as vanilla as possible".
I think this is very wrong idea comes from restricted bootloaders.
When you install drivers into Windows it becames hacked windows? 
When you install VBox or Intel Power Gadget you broke vanillaness?
Why do you want to boot without kernelcache? I shall remind that kernelcache contains all drivers from SLE but not from Extra.
Do you know about kexts dependencies and order of booting?
 
My claim: do not use extra folders to load kexts except installation process when you need only FakeSMC.kext separately. Install other into SLE after full installation complete.

Share this post


Link to post
Share on other sites

 

mkdir /Volumes/TEFI
mount -t msdos /dev/disk1s1 /Volumes/TEFI

 

 
 
This is very old cult of Vanilla System: "I want to not place anything into SLE to keep the system as vanilla as possible".
I think this is very wrong idea comes from restricted bootloaders.
When you install drivers into Windows it becames hacked windows? 
When you install VBox or Intel Power Gadget you broke vanillaness?
Why do you want to boot without kernelcache? I shall remind that kernelcache contains all drivers from SLE but not from Extra.
Do you know about kexts dependencies and order of booting?
 
My claim: do not use extra folders to load kexts except installation process when you need only FakeSMC.kext separately. Install other into SLE after full installation complete.

 

 

maybe I explained evil 
I meant that from your .pkg HWSensors could give the destination EFI/Clover/Kext/10.10 
 
SLE vanilla 
kext installed in EFI / Clover / kext / 10.10 / FakeSMC and other
 
Thanks
 
Fabio

Share this post


Link to post
Share on other sites

maybe I explained evil 

I meant that from your .pkg HWSensors could give the destination EFI/Clover/Kext/10.10

I don't want this.

SLE vanilla 

kext installed in EFI / Clover / kext / 10.10 / FakeSMC and other

 

 

Thanks

 

Fabio

I explained why I hate "vanilla".

Share this post


Link to post
Share on other sites

 

 

 

Thank you Slice, works fine. Tested on my Laptop running 10.9.4

 

P.D.

For MacBookPro6,1-6,2 (Arrandale CPU) "RPlt"="k74"="6B373400 00000000" can be added to FakeSMC "Info.plist" as:

<key>RPlt</key>
<array>
<string>ch8*</string>
<data>azc0AAAAAAA=</data>
</array>
 

Also, the most recent from Apple MBP6,1-6,2 "REV"="1.58f17"="01580F00 0017" as:

<key>REV </key>
<array>
<string>{rev</string>
<data>AVgPAAAX</data>
</array>
 
Another data is:
<key>smc-compatible</key>
<string>smc-piketon</string>

 

Additionally, to avoid some startup (console log) error related to SMC key, we can add the "lightshow-version"="LsbV"="1.4a6"="01040A00 06" as:

<key>LsbV</key>
<array>
<string>{rev</string>
<data>AQQKAAY=</data>
</array>

 

 

 

Hi,

Do you have more keys for MBP6,1? I need a original dump.

Thx.

Share this post


Link to post
Share on other sites

Hi Bungo. No, my friend. That is only what I have collected from the MBP6,1-6,2 in internet. Would be great a original dump. Good luck with that.

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