Jump to content

1,165 posts in this topic

Recommended Posts

Localization for italian language!

 

it.lproj.zip

 

I added/modified this in the:

 

line 101 of the file DefaultTestingPlatform.h

   {"MlC%X", "ui8", 1, "CPU Multiplier %X", kSMCKeyGroupMultiplier, 8, 0, 1},

 

line 68 of the file HWMonitorProfiles.m

		 [NSArray arrayWithObjects:@"MlC:081",    @"CPU Multiplier %X", nil],

 

in localizable.strings

"CPU Multiplier %X" = "Moltiplicatore CPU %X";

Edited by Marchrius

Share this post


Link to post
Share on other sites
Advertisement

Hi everybody!

I decided to ponder over sensors again.

I wanna to get voltage of something, GPU, CPU, Ram and so on.

1) Is it possible to commit it with Laptops. Because I understand the LPCSensors works only for Desktops and maybe some laotops. By default it gives me nothing

2) Can ACPISensors give some voltage of something? If so how can I find necessary registers? I tried to do it with the aim of RWE under Windows 8 but it is a dark forest where so easy get lost

Share this post


Link to post
Share on other sites

hello kozlek

booting 10.9 dp1

my dmesg is full of this

SMC::smcReadKeyAction ERROR CG3S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8025871800
SMC::smcReadKeyAction ERROR CG1R kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8025871800

and say msg

revert to old smc mode

 

12/06/13 00:00:28,000 kernel[0]: SMC::smcInitHelper ERROR: MMIO regMap == NULL - fall back to old SMC mode

this with last version

thanks

Share this post


Link to post
Share on other sites

hello kozlek

 

booting 10.9 dp1

 

my dmesg is full of this

 

SMC::smcReadKeyAction ERROR CG3S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8025871800

SMC::smcReadKeyAction ERROR CG1R kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8025871800

 

and say msg

 

revert to old smc mode

 

12/06/13 00:00:28,000 kernel[0]: SMC::smcInitHelper ERROR: MMIO regMap == NULL - fall back to old SMC mode

 

this with last version

 

thanks

Same here, and +10C temps for the CPU on 10.9

Share this post


Link to post
Share on other sites

I cannot remember which version of fake smc I was using on maverick and it showed ambient sensor on my  pro book 4430s

 

then I installed another version maybe a later one but cannot seem to get sensor showing anymore in hwmonitor

 

I have tried many fakesmc no luck......

Share this post


Link to post
Share on other sites

I cannot remember which version of fake smc I was using on maverick and it showed ambient sensor on my  pro book 4430s

 

then I installed another version maybe a later one but cannot seem to get sensor showing anymore in hwmonitor

 

I have tried many fakesmc no luck......

Probably my fork: https://github.com/RehabMan/OS-X-FakeSMC-kozlek

 

You need correctly patched DSDT as well.  See: https://github.com/RehabMan/HP-ProBook-4x30s-DSDT-Patch

Share this post


Link to post
Share on other sites

I have tried yours and also my dsdt is patched with maciasl with your repo in sources but I cannot get it to show it again. :-( :-(

Share this post


Link to post
Share on other sites

I have tried yours and also my dsdt is patched with maciasl with your repo in sources but I cannot get it to show it again. :-( :-(

Depends on what you're using out of my repo (or not using).  You need to do one of the fan patches, otherwise no SMCD/TAMB.

And you need my fork of FakeSMC including ACPISensors.kext, because only mine has the entry for TAMB.

 

Good luck...

Share this post


Link to post
Share on other sites

Well I have quiet fan patch on my dsdt and fakesmc is from you repo too
Will check my dsdt for TAMB.....

I have got it showing again thanks RehabMan you need fan only reading patch…. :)

Share this post


Link to post
Share on other sites

I edited my dsdt so will show ambient and fan patch

fan kick in at higher temps than normal but of course go off at lower temps e.g. 44 degrees

Share this post


Link to post
Share on other sites

Hi REhabman now I get this error I was not getting b4

 

 

23/06/2013 12:11:43.000 kernel: SuperIODevice: [Fatal] found unsupported ship ID=0x701
 
Any ideas what is is for?????

Share this post


Link to post
Share on other sites

 

Hi REhabman now I get this error I was not getting b4

 

 

23/06/2013 12:11:43.000 kernel: SuperIODevice: [Fatal] found unsupported ship ID=0x701
 
Any ideas what is is for?????

 

It is from LPCSensors.kext.  You can remove it, as there is no support for the ProBook's LPC chipset.

Share this post


Link to post
Share on other sites

Thanks for that I looked  in there and gathered it was that one the culprit...

Share this post


Link to post
Share on other sites

Hi, HWSensors/HWMonitor see only one of two processor on EVGA SR-2 (dual processor mobo, chipset 5520/ICH10R). Kozlek, can You fix it ? What kind of dump you need ? I have everything from darwindumper 2.7.5 except bioses.

Share this post


Link to post
Share on other sites

Hello Kozlek,

Do you plan to add Haswell support ?

 

Here is some of my logs (Z87-UD3H and i5 4670K)

02/07/13 18:55:20,000 kernel[0]: CPUSensors: [Fatal] found unsupported Intel processor, using default Tjmax
02/07/13 18:55:20,000 kernel[0]: CPUSensors: CPU family 0x6, model 0x3c, stepping 0x3, cores 16, threads 16, TJmax 0

If you need something, i will help with pleasure.

 

 

Thanks.

 

 

Project 5.1.71

post-497804-0-60497000-1372784601_thumb.jpg

Share this post


Link to post
Share on other sites

Hello Kozlek,

Do you plan to add Haswell support ?

 

Here is some of my logs (Z87-UD3H and i5 4670K)

02/07/13 18:55:20,000 kernel[0]: CPUSensors: [Fatal] found unsupported Intel processor, using default Tjmax
02/07/13 18:55:20,000 kernel[0]: CPUSensors: CPU family 0x6, model 0x3c, stepping 0x3, cores 16, threads 16, TJmax 0

 

My 4770K is also model 3C. I looked through the FakeSMC source and found that it only has model ids for ultrabook and laptop haswell cpus, not the regular LGA1150 desktop. 

 

Here's a kext compiled for 10.9 with model 3c support. http://www.insanelymac.com/forum/files/file/107-fakesmckext/

Share this post


Link to post
Share on other sites

 

Thanks a lot. 

 

What's the purpose of this code please :

diff --git a/CPUSensors/CPUSensors.cpp b/CPUSensors/CPUSensors.cpp

it just tells you the difference between these two C++ code files (the original and the one that had changes done to it).

Share this post


Link to post
Share on other sites

Hey Real Deal, have you had success with that kext? Someone else with a 4670K just reported failure on the download page... so I'm curious... I might look at exploring other haswell holes in the code this evening. Unfortunately I only have the one CPU to test on. I only just noticed CPUSensors reporting 16 cores & 16 threads for your cpu... I have a few ideas of where to look.

 

Edit: well apparently the other guy with a 4670K got it working and I just misunderstood his first post.

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.
       
    • By Slice
      This thread devoted to share information about different SMC keys found or investigated anywhere.
       
      What are they?
      SMC keys is a somehow language to speak between macOS and hardware microcontroller presented in real Mac and absent in Hackintosh.
      They inform macOS about Hardware ID and current status. Moreover macOS can write something through SMC protocol to control hardware.
      FakeSMC ( ©Netkas) is the driver to emulate this microcontroller on PC having no such device which is necessary to boot macOS here.
      But FakeSMC contain only ~20 keys while real Mac answers ~200 keys.
      Some keys we added by HWSensors project reporting temperatures, FAN speeds, voltages etc.
      Some keys are model dependent was added by Clover to be sure if user changed model in GUI then corresponding keys will be changed automatically.
      Clover sets
      LogDataHub(&gEfiMiscSubClassGuid, L"RPlt", &gSettings.RPlt, 8);
      LogDataHub(&gEfiMiscSubClassGuid, L"RBr", &gSettings.RBr, 8);
      LogDataHub(&gEfiMiscSubClassGuid, L"EPCI", &gSettings.EPCI, 4);
      LogDataHub(&gEfiMiscSubClassGuid, L"REV", &gSettings.REV, 6);
      LogDataHub(&gEfiMiscSubClassGuid, L"BEMB", &gSettings.Mobile, 1);
      BEMB - is a mobility sign. =0 -desktop, =1 - mobile.
      REV - SMC hardware revision, changes sometimes with Apple updates.
      RPlt, RBr and EPCI is hardware capabilities, noticed used in Intel HD drivers.
       
      Structure.
      All SMC keys consists of name 4 ascii chars as 32bit integer, type and value.
      Types:
       "flag", len 1
       "ui8 ", len 1
       "ui16", len 2
       "sp78", len 2
       "ui32", len 4
      "fp2e", len 2
      "fpe2", len 2
      "{rev", and others...
       
      List of known keys
      SMC_list.plist.zip
      More keys will be discussed in the thread
       
       
      Feel free to share you knowledge and ask about noticed keys.
×