Jump to content

1,167 posts in this topic

Recommended Posts

Hello every one

 

please how i can know what kind of chip i have

i have only one partition with OSX and no windows to test

my Mobo is MSI H67MA-E35 B3

and this is the log

 

Feb 10 21:21:02 imac kernel[0]: W836x: [Warning] found unsupported chip ID=0x10 REVISION=0x7

Feb 10 21:21:02 imac kernel[0]: NCT677x: [Warning] found unsupported chip ID=0x10 REVISION=0x7

Feb 10 21:21:02 imac kernel[0]: IT87x: [Warning] invalid super I/O chip ID=0xffff

Feb 10 21:21:02 imac kernel[0]: F718x: [Warning] found unsupported chip ID=0x10 REVISION=0x7

Feb 10 21:21:06 imac kernel[0]: W836x: [Warning] found unsupported chip ID=0x10 REVISION=0x7

Feb 10 21:21:06 imac kernel[0]: NCT677x: [Warning] found unsupported chip ID=0x10 REVISION=0x7

Feb 10 21:21:06 imac kernel[0]: IT87x: [Warning] invalid super I/O chip ID=0xffff

Feb 10 21:21:06 imac kernel[0]: F718x: [Warning] found unsupported chip ID=0x10 REVISION=0x7

Feb 10 21:21:08 imac kernel[0]: W836x: [Warning] found unsupported chip ID=0x10 REVISION=0x7

Feb 10 21:21:08 imac kernel[0]: NCT677x: [Warning] found unsupported chip ID=0x10 REVISION=0x7

Feb 10 21:21:08 imac kernel[0]: IT87x: [Warning] invalid super I/O chip ID=0xffff

Feb 10 21:21:08 imac kernel[0]: F718x: [Warning] found unsupported chip ID=0x10 REVISION=0x7

Feb 10 21:21:09 imac kernel[0]: W836x: [Warning] found unsupported chip ID=0x10 REVISION=0x7

Feb 10 21:21:09 imac kernel[0]: NCT677x: [Warning] found unsupported chip ID=0x10 REVISION=0x7

Feb 10 21:21:09 imac kernel[0]: IT87x: [Warning] invalid super I/O chip ID=0xffff

Feb 10 21:21:09 imac kernel[0]: F718x: [Warning] found unsupported chip ID=0x10 REVISION=0x7

Feb 10 21:21:09 imac kernel[0]: W836x: [Warning] found unsupported chip ID=0x10 REVISION=0x7

Feb 10 21:21:09 imac kernel[0]: NCT677x: [Warning] found unsupported chip ID=0x10 REVISION=0x7

Feb 10 21:21:09 imac kernel[0]: IT87x: [Warning] invalid super I/O chip ID=0xffff

Feb 10 21:21:09 imac kernel[0]: F718x: [Warning] found unsupported chip ID=0x10 REVISION=0x7

Feb 10 21:21:10 imac kernel[0]: W836x: [Warning] found unsupported chip ID=0x10 REVISION=0x7

Feb 10 21:21:10 imac kernel[0]: NCT677x: [Warning] found unsupported chip ID=0x10 REVISION=0x7

Feb 10 21:21:10 imac kernel[0]: IT87x: [Warning] invalid super I/O chip ID=0xffff

Feb 10 21:21:10 imac kernel[0]: F718x: [Warning] found unsupported chip ID=0x10 REVISION=0x7

 

 

thanks for your help

Share this post


Link to post
Share on other sites
Advertisement
New Nuvoton doesn´t seem to work on Sabertooth P67:

 

I get this same message with the new Nuvoton, the chip does not appear to be identified, exactly the same entry in kernel log.

Share this post


Link to post
Share on other sites

Newest version doesn´t change anything on Sabertooth P67, sadly sad.png

OK,

 

I fixed NCT677x plugin, at least for my setup but IMHO should work for others too.

 

Limited the temperatures to 2: Sytem and CPU,, the Auxiliary, as rest of NCT677x capable sensors reading temperature require a much elaborated code since it depends on Vendor implementation (if more then 2 fans are implemented and stuff like that).

OpenHardwareMonitor as Linux code is as best in beta stage, anyway they try to get max 3.

 

Voltages, only CPU and 3V one are correct, rest require a math(see datasheet and programming guide) and since I cant bet on iStat(it does own math depending on specific key) I need to have them implemented in monitoring app/menuextra, or figure out how to compile those, if possible...

 

Fans, only 2 are set for now, if you have more just add the desired name on FANINx entry in info.plist.

 

Enjoy!

 

post-53345-0-01215600-1329179003_thumb.png

post-53345-0-44800900-1329179020_thumb.png

NuvotonNCT677x.kext.zip

NCT677X_fsmc4_source.zip

Share this post


Link to post
Share on other sites

OK,

 

I fixed NCT677x plugin, at least for my setup but IMHO should work for others too.

 

Limited the temperatures to 2: Sytem and CPU,, the Auxiliary, as rest of NCT677x capable sensors reading temperature require a much elaborated code since it depends on Vendor implementation (if more then 2 fans are implemented and stuff like that).

OpenHardwareMonitor as Linux code is as best in beta stage, anyway they try to get max 3.

 

Voltages, only CPU and 3V one are correct, rest require a math(see datasheet and programming guide) and since I cant bet on iStat(it does own math depending on specific key) I need to have them implemented in monitoring app/menuextra, or figure out how to compile those, if possible...

 

Fans, only 2 are set for now, if you have more just add the desired name on FANINx entry in info.plist.

 

Enjoy!

 

Works fine for me, thanks. :)

 

post-413183-0-12777300-1329183232_thumb.png post-413183-0-13818800-1329183300_thumb.png

Share this post


Link to post
Share on other sites

Hi Mozodojo!

 

 

sorry, I did not write English well...

 

I've got two kinds of motherboards( ASUS P8P67 Pro Rev 3.1(use mobo) and ASUS Maximus4 Gene-z(use mobo) )

The boards using Nuvoton NCT6776F sensor chip.

i installed ACPISensors.kext, FakeSMC.kext, RadeonX.kext, IntelThermal.kext, NuvotonNCT677x.kext and HWMonitor.app

However, the latest version of the chip will not recognize in NCT677x.kext

 

KernelLog output this message:

NCT677x: [Warning] wrong vendor chip ID = 0xc3 REVISION = 0x33 VENDORID = 0xffff

 

Please help me. Thank you!

 

 

 

1.png?w=e3e860d12.png?w=af2ed048

Share this post


Link to post
Share on other sites

Should work now. Seems some chips returning 0xffff instead of proper vendor-id.

Heh, including the plug-in as was uploaded could save some time/trouble ;)

 

About IntelThermal, now it does read the multiplier but not turbo ones

If we can add those and rest of the stuff from OpenHardwareMonitor would be great! :)

Share this post


Link to post
Share on other sites

Heh, including the plug-in as was uploaded could save some time/trouble ;)

 

About IntelThermal, now it does read the multiplier but not turbo ones

If we can add those and rest of the stuff from OpenHardwareMonitor would be great! :)

Now we are working together. IntelThermal is excluded from the project by IntelCPUmonitor.

Check rev530.

What stuff did you find in OpenHardwareMonitor?

Share this post


Link to post
Share on other sites

What stuff did you find in OpenHardwareMonitor?

post-53345-0-75768100-1329493922_thumb.png

So github is gone and we are back to assembla, good!

Didn't have time to check IntelCpuMonitor, I will check.

 

P.S. A little organization in folders for each one as was on mozo would be great.

Share this post


Link to post
Share on other sites

post-53345-0-75768100-1329493922_thumb.png

So github is gone and we are back to assembla, good!

Didn't have time to check IntelCpuMonitor, I will check.

 

P.S. A little organization in folders for each one as was on mozo would be great.

 

Yes, but I am leaving the scene.

Share this post


Link to post
Share on other sites

Yes, but I am leaving the scene.

Good job, mozo!

Don't rely on, I'll come back later.

I am confused...

Anyway good luck with your plans mozo and thanks for the work you did/share so far.

Share this post


Link to post
Share on other sites

I only want to remember to check real stepping after using new fakesmc + intelthermal by msrdumper.

For me it was not only an cosmetic problem - showing an fixed 10* multiplier , it was real fixed multiplier problem. Stepping stopped working.

For me, IntelThermal shows fixed multiplier 10* and that was real - no stepping shown also in msr dumper. Went back to older fakesmc + InteCPUMonitor = stepping works again with same OSX and same dsdt.

Dont know if maybe bit newer builds or other C2D cpus like mine (E7400) dont have that effect but i would cross check stepping with msrdumper.

my first thinking: could it be that IntelThermal MSR reads can block the native AppleIntelCPU.kext in changing the MSR stepping tasks by timing problems / interrupt problems in the msr read code (maybe depends on CPU type also if problem happens) ?

 

@mitch_de

 

After some fixes that seem to be made is this working for you now in 10.7.3? I know you had a problem with speedstepping with this newer version but since it seems some mods were made were you able to try it since then to get it to work with speedstepper for 10.7.3?

 

Thanks

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 Slice
      Hi all,
       
      I created an installer for my version of FakeSMC with plugins and applications latest revision.
       
      Compatibility from 10.6 up to 10.15.
      Test, please.

      Download here: HWSensors.pkg.zip
      See my signature
       
      02.11.2019
      New project home
      https://github.com/CloverHackyColor/FakeSMC3_with_plugins
      FakeSMC v3.5.3 and plugins
       
      HWMonitorSMC2 at
      https://github.com/CloverHackyColor/HWMonitorSMC2
       
       
      FakeSMC 3.4.0 revision 751
      HWSensors.pkg-751.zip
       
      New project home is
      https://sourceforge.net/projects/hwsensors3.hwsensors.p/
      where you can download most recent versions.
      Now it is FakeSMC 3.4.1
       
      Explanations about the difference between versions 3 and 6
        #137 
       
      20.05.2016
      Revision 32 with explanation at    #220 
       
      10.10.2017
      FakeSMC is 3.5.0 compatible with High Sierra.
      New plugin VoodooBatterySMC created on the base of VoodooBattery by Superhai but with SMC keys generating to show Battery voltage and amperage. As well it created key BATP needed for right speedstep and FileVault2.
      Other kexts revised.
    • By fusion71au
      This is a brief guide on how to create a vanilla El Capitan (also same process for Sierra) OS X Installer USB with an updated prelinked kernel containing FakeSMC.

      It is tailored for those users who want to understand the “nuts and bolts” of how to create an installer and also to help brush up on their terminal skills (rather than have one made for them with the numerous automated “tools” available or even Apple’s createinstallmedia) :
       
       
      Specifically, it is also a “Proof of Concept” which shows that installation is possible without even having to rely on boot loader kext injection.

      Prerequisites
      Existing Yosemite installation (or Mavericks - see post#4 for steps 7,8) “Install OS X El Capitan.app" downloaded to the Applications folder Pacifist FakeSMC.kext - Slice or Kozlek branch Bootloader - Clover or Chameleon 8GB or larger USB drive (16GB recommended), formatted HFS+ (MBR or GUID) named “Installer”  
      Procedure
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Open OS X terminal and type the following lines, followed by <Enter> after each line.
          The image restore and file copying may take a while to complete, and at the end of the process, the Installer volume is renamed to “OS X Base System"....
       
      sudo -s hdiutil attach /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/SharedSupport/InstallESD.dmg asr restore -source /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg  -target /Volumes/Installer -erase -format HFS+ -noprompt -noverify rm /Volumes/OS\ X\ Base\ System/System/Installation/Packages cp -av /Volumes/OS\ X\ Install\ ESD/Packages /Volumes/OS\ X\ Base\ System/System/Installation cp -av /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg /Volumes/OS\ X\ Install\ ESD/BaseSystem.chunklist /Volumes/OS\ X\ Base\ System diskutil unmount /Volumes/OS\ X\ Install\ ESD exit 3.  Right click on the “OS X Base System” Volume and click “Get Info”
       

      4.  Click on the lock icon and untick “Ignore ownership on this volume”
       

      5.  Extract/Copy the El Capitan Kernels folder into /System/Library/ of the USB with Pacifist.  NB It is found in the "Essentials.pkg" in /System/Installation/Packages
       

      6.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel —> OG.prelinkedkernel
       

      7.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of the installer USB using Finder.
       

      8.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel…..
       
      sudo -s chmod -R 755 /Volumes/OS\ X\ Base\ System/Library/Extensions chown -R 0:0 /Volumes/OS\ X\ Base\ System/Library/Extensions touch /Volumes/OS\ X\ Base\ System/System/Library/Extensions kextcache -u /Volumes/OS\ X\ Base\ System exit Any errors should be noted but the output below is normal e.g.


      9. Install your Bootloader targeting the OS X Base System volume
       
       
       
       
      10.  Boot your system with the USB without injected kexts into the OS X Installer GUI....
       
       
       
       
       
      Post Install
      The original prelinked kernel in a fresh install of El Capitan will also lack FakeSMC ie it will only be linked to Apple signed kexts.  In order to boot into El Capitan the first time around without boot loader kext injection, the PLK needs to be rebuilt for the El Capitan volume like we did for the installer:
       
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel for the El Capitan volume —> OG.prelinkedkernel
      3.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of El Capitan using Finder
      4.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel.  In this example, the El Capitan volume is named "El_Capitan" - change if you have named it something else...
      sudo -s chmod -R 755 /Volumes/El_Capitan/Library/Extensions chown -R 0:0 /Volumes/El_Capitan/Library/Extensions touch /Volumes/El_Capitan/System/Library/Extensions kextcache -u /Volumes/El_Capitan exit 5. Install your Bootloader targeting the El Capitan volume.  This step is only necessary if you are installing El Capitan on a new drive without existing boot loader (not required if installing on a disk with existing boot loader beside Yosemite).
      6. Reboot your system without injected kexts into El Capitan!
       
       
      Other links
      The All-In-One Guide to Vanilla OS X for beginners
       
      Updates for Sierra and High Sierra   Custom Prelinkedkernel Generator Tool I have made a custom prelinkedkernel generator "PLK.tool" for Sierra + El Capitan.  Instructions:   1.  Download and extract the attached BaseSystem_PLK.tool.zip into your ~/Downloads folder.   2.  Copy any extra kexts necessary for booting your hack to ~/Downloads/BaseSystem/ExtraKexts (e.g. FakeSMC, VoodooPS2Controller), making sure SIP is disabled. 3.  Copy BaseSystem.dmg to ~/Downloads/BaseSystem  4.  Open terminal and run the following commands... cd ~/Downloads/BaseSystem chmod +x PLK.tool ./PLK.tool ---> supply your admin password ---> will place your new custom prelinkedkernel on the desktop.       macOS High Sierra bypass Firmware and MBR checks in post#13.
      BaseSystem_PLK.tool_ElCap.zip
      BaseSystem_PLK.tool_Sierra.zip
      BaseSystem_PLK.tool_Mojave.zip (need to run in Mojave to avoid dependency errors)
      BaseSystem_PLK.tool_Catalina.zip
    • By Slice
      Dell laptops and desktop can be monitored by SMM methods as mentioned is the old topic
       
      I made a plugin SMIMonitor for FakeSMC in 2014 but it was 32bits and was not working. Only now I made it to be 64bits (as darkvoid did with kozleks branch) and got positive results
        
      and after heating 
      So I have monitoring of 4 additional temperature sensors (CPU Proximity, GPU, DIMM, and Motherboard) and a CPU fan which initially stay at 0 rpm and start rotating after heating with 2882rpm.
       
      Moreover I implemented a function for brave people to control fans
      sudo SMC_util3 -kF0As -w2 The last digit 2 is a FAN speed you want to set
      0 = Off
      1 = Low
      2 = High
      If you have more then 1 fan then you can manage other one by choosing next key F1As, F2As etc.
       
      Precaution! Writing the fan speed is dangerous and may cause a computer damage. Do this at your own risk!
      Note. SMIMonitor.kext will work only with FakeSMC v3 provided with HWSensors3 in my signature.
      Official release at sf.net contains SMIMonitor without write possibility.
       
      Please test and report your successes and fails.
       
       
      SMIMonitor.kext-110.zip
      SMC_util3.zip
      smcwrite.zip
×