Jump to content
2,150 posts in this topic

Recommended Posts

What is changed except the kext? Something else? 

The main difference is reporting SMC keys, but it is not influencing on system.

May be broken permissions?

 

Nothing else has changed. I have tried your latest HWSensor automatic installation package as well as extracting the package with Pacifist and then installing the resulting appropriate kexts via Chameleon Wizard. I have installed both versions several times using the same installation methods, and rolled them back to the previous version several times even running Disk Utility each time for good measure.

 

In both instances, there are no permission errors and kextstat and System Information both show the FakeSMC.kext and its plugins installed correctly. Each time, the latest FakeSMC.kext version 3.4.0 causes a black screen upon system Wake while FakeSMC.kext 3.3.1 presents no such issue.

 

In the past several years, I have never experienced any issues with your branch of FakeSMC HWSensors, and I have also never experienced black screen upon system Wake for any reason.

FakeSMC:

  Version: 3.3.1
  Last Modified: 12/11/14 4:16 PM
  Kind: Intel
  Architectures: i386, x86_64
  64-Bit (Intel): Yes
  Location: /System/Library/Extensions/FakeSMC.kext
  Kext Version: 3.3.1
  Load Address: 0xffffff7f81a04000
  Valid: Yes
  Authentic: Yes
  Dependencies: Satisfied

 

Nothing else has changed. I have tried your latest HWSensor automatic installation package as well as extracting the package with Pacifist and then installing the resulting appropriate kexts via Chameleon Wizard. I have installed both versions several times using the same installation methods, and rolled them back to the previous version several times even running Disk Utility each time for good measure.

 

In both instances, there are no permission errors and kextstat and System Information both show the FakeSMC.kext and its plugins installed correctly. Each time, the latest FakeSMC.kext version 3.4.0 causes a black screen upon system Wake while FakeSMC.kext 3.3.1 presents no such issue.

 

In the past several years, I have never experienced any issues with your branch of FakeSMC HWSensors, and I have also never experienced black screen upon system Wake for any reason.

FakeSMC:

  Version: 3.3.1
  Last Modified: 12/11/14 4:16 PM
  Kind: Intel
  Architectures: i386, x86_64
  64-Bit (Intel): Yes
  Location: /System/Library/Extensions/FakeSMC.kext
  Kext Version: 3.3.1
  Load Address: 0xffffff7f81a04000
  Valid: Yes
  Authentic: Yes
  Dependencies: Satisfied

Compare, please, Info.plist's of these two versions of FakeSMC.kext.

I see no reason for different behavior other then different info.plist.

The version changed because of new output but system can't see it.

Compare, please, Info.plist's of these two versions of FakeSMC.kext.

I see no reason for different behavior other then different info.plist.

The version changed because of new output but system can't see it.

 

Both FakeSMC.kext versions Info.plists appear to be identical short of the version number and yet the problem persists.

For now, I will simply continue using the older FakeSMC.kext version 3.3.1.

 

Thank You for your work!

  • 3 weeks later...

Hey

 

thanks for your great work. I have a question. Do you have any idea when and/or if the gm204 chipsets might be supported in the future?

Jan  3 15:39:14 localhost kernel[0]: GeForceSensors (pci1): [Fatal] GM204 not supported yet
Jan  3 15:39:14 localhost kernel[0]: GeForceSensors (pci1): [Fatal] unsupported chipset, 0x124020a1

Cheers

Hey

 

thanks for your great work. I have a question. Do you have any idea when and/or if the gm204 chipsets might be supported in the future?

Jan  3 15:39:14 localhost kernel[0]: GeForceSensors (pci1): [Fatal] GM204 not supported yet
Jan  3 15:39:14 localhost kernel[0]: GeForceSensors (pci1): [Fatal] unsupported chipset, 0x124020a1

Cheers

Yes, I think it may be supported in future... but I see these messages not from my project...

  • 2 weeks later...

Revision 11.

Yes, I change project home and begin numeration from zero. Link is in the topic.

 

Change log:

- support more hardware, more NVidia cards, more SMBus chips;

- installer has more options to install. Silent AppleSMC included to not spam in system.log;

- corrected numerous bugs existing here from initial.

  • Like 5
  • 3 weeks later...

Can anybody test debug version of new plugin DIMMSensor? It should monitor temperature on DIMM sensors.

SMC keys will be TM0P, TM1P, ...

sudo chown -R root:wheel DIMMSensor.kext
sudo kextutil -v DIMMSensor.kext

There will be many messages in kernel.log

 

It doesn't work for me and  I think you mean this messages.

 

 

Jan 30 21:32:23 localhost kernel[0] <Notice>: ARPT cannot assert wake from D3cold
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] init
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] probe
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] start
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] conf: 0x1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] IRQ: 19
Jan 30 21:32:23 localhost kernel[0] <Notice>: Controller: Intel 82801H (vendor ID: 8086, device ID: 284b)
Jan 30 21:32:23 localhost kernel[0] <Notice>: FakeSMC: opensource SMC device emulator by netkas © 2009
Jan 30 21:32:23 localhost kernel[0] <Notice>: FakeSMC: plugins & plugins support modifications by mozodojo, usr-sse2, slice © 2010
Jan 30 21:32:23 localhost kernel[0] <Notice>: FakeSMCDevice: 21 preconfigured key(s) added
Jan 30 21:32:23 localhost kernel[0] <Notice>: FakeSMCDevice: successfully initialized
Jan 30 21:32:23 localhost kernel[0] <Notice>: IntelCPUMonitor: CPU family 0x6, model 0xf, stepping 0xd, cores 2, threads 2
Jan 30 21:32:23 localhost kernel[0] <Notice>: FireWire runtime power conservation disabled. (3)
Jan 30 21:32:23 localhost kernel[0] <Notice>: IntelCPUMonitor: Using efi
Jan 30 21:32:23 localhost kernel[0] <Notice>: IntelCPUMonitor: BusClock=166MHz FSB=665MHz
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: op 1, addr 0x18, cmdlen 1, len 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: St 0x40
Jan 30 21:32:23 localhost kernel[0] <Notice>: IntelCPUMonitor: CPU Tjmax 100
Jan 30 21:32:23 localhost kernel[0] <Notice>: HWInfo: SMC Platform: M75
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: Ctl 0x49
Jan 30 21:32:23 localhost kernel[0] <Notice>: VoodooPS2SynapticsTouchPad Version 1.8.12 loaded...
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] Register decoded: 0x44<BUSY=0,INTR=0,DEVERR=1,BUSERR=0,FAILED=0,SMBAL=0,INUSE=1,BDONE=0>
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] marker = 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: op 1, addr 0x19, cmdlen 1, len 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: St 0x0
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: Ctl 0x49
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] Register decoded: 0x44<BUSY=0,INTR=0,DEVERR=1,BUSERR=0,FAILED=0,SMBAL=0,INUSE=1,BDONE=0>
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] marker = 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: op 1, addr 0x1a, cmdlen 1, len 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: St 0x0
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: Ctl 0x49
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] Register decoded: 0x44<BUSY=0,INTR=0,DEVERR=1,BUSERR=0,FAILED=0,SMBAL=0,INUSE=1,BDONE=0>
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] marker = 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: op 1, addr 0x1b, cmdlen 1, len 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: St 0x0
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: Ctl 0x49
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] Register decoded: 0x44<BUSY=0,INTR=0,DEVERR=1,BUSERR=0,FAILED=0,SMBAL=0,INUSE=1,BDONE=0>
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] marker = 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: op 1, addr 0x1c, cmdlen 1, len 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: St 0x0
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: Ctl 0x49
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] Register decoded: 0x44<BUSY=0,INTR=0,DEVERR=1,BUSERR=0,FAILED=0,SMBAL=0,INUSE=1,BDONE=0>
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] marker = 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: op 1, addr 0x1d, cmdlen 1, len 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: St 0x0
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: Ctl 0x49
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] Register decoded: 0x44<BUSY=0,INTR=0,DEVERR=1,BUSERR=0,FAILED=0,SMBAL=0,INUSE=1,BDONE=0>
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] marker = 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: op 1, addr 0x1e, cmdlen 1, len 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: St 0x0
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: Ctl 0x49
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] Register decoded: 0x44<BUSY=0,INTR=0,DEVERR=1,BUSERR=0,FAILED=0,SMBAL=0,INUSE=1,BDONE=0>
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] marker = 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: op 1, addr 0x1f, cmdlen 1, len 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: St 0x0
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] exec: Ctl 0x49
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] Register decoded: 0x44<BUSY=0,INTR=0,DEVERR=1,BUSERR=0,FAILED=0,SMBAL=0,INUSE=1,BDONE=0>
Jan 30 21:32:23 localhost kernel[0] <Notice>: [iCHSMBus] marker = 1
Jan 30 21:32:23 localhost kernel[0] <Notice>: FireWire (OHCI) VendorID 1180 ID 832 PCI now active, GUID 00241b002fd83c00; max speed s400.
Jan 30 21:32:23 localhost kernel[0] <Notice>: [DIMM] Device matching failed.
 

46395098.png

 

Apparently it doesn't work with my GTX 970.

 

 

I installed it like this:

 

CPU -> Intel CPU

LPC chip type -> winbond

GPU type -> Nvidia -> New Geforce

FakeSMC

SMBus chip type

It is a conflict with Kozlek's HWMonitor application.

There is another one HWMonitor in the package.

Hi Slice,

Does this application works if FakeSMC is an injected kext (Clover and 10.10 folder routine) via clover on USB pen?

Yes, as usual.

These kexts will work if injected by a bootloader.

I prefer place all kexts into SLE because injection requires additional time while SLE will be cached.

  • 2 weeks later...
  • 2 weeks later...

i cant get my cpu fan reading in fake smc 

pls help me 

my dump and screenshot is added

OK.

You are using kexts and HWMonitor application v6.x from Kozlek while the thread about HWSensors3 by me.

There is a difference.

×
×
  • Create New...