Jump to content

HWSensors3

Slice

By Slice,
in Hardware Sensors

 Share
2,189 posts in this topic

Recommended Posts

SavageAUS
SavageAUS
Posted
Posted

Revision 51 available on sf.net. Link in my signature.

There is no package, just dmg image. 

Don't install all kexts! Choose only those you needed!

For the desktop in my signature I would only need FakeSMC, IntelCPUMonitor and GeforceSensor? Is this correct?

Are these kexts ok in CLOVER/kexts/other or install to S/L/E?

And Laptop: FakeSMC, IntelCPUMonitor and VoodooBatterySMC?

 

And another question, what is AppleSMC for?

Link to comment
Share on other sites
Slice
Slice
Posted
  • Author
Posted

For the desktop in my signature I would only need FakeSMC, IntelCPUMonitor and GeforceSensor? Is this correct?

Are these kexts ok in CLOVER/kexts/other or install to S/L/E?

And Laptop: FakeSMC, IntelCPUMonitor and VoodooBatterySMC?

 

And another question, what is AppleSMC for?

For desktop you may add ITE87x.kext for System Fan monitoring.

 

For laptop you may add ACPIMonitor.kext and SSDT as you can find here.

 

AppleSMC is just a version from stable system to replace beta kext with large messages count.

Link to comment
Share on other sites
Cyberdevs
Cyberdevs
Posted
Posted

What means with "new geforce" here? I have no problem with it

I guess what it mean is that the "GeforceSensor.kext" which is a new version of Kozlek's previous sensor is still causing the kernel panic on Pascal GPUs. The only version of the GPUSensors.kext that I was able to use is the one I attached here. It's also by kozlek but I guess it's been updated and I have no problem using it.

 

But the thing is I wasn't able to get it to work with the new FakeSMC.kext v. 3.5.0 yet.

GPUSensors.kext.zip

  • Like 1
Link to comment
Share on other sites
Cyberdevs
Cyberdevs
Posted
Posted

This kext is fake working. It shows a value having no relation to real temperature.

As well compare frequencies if any.

Yes I know about the fake/inaccurate readings. but when I use your version of the GeForeceSensor.kext it gives me the kernel panic. Is there anything that can be done?

 

Can you please tell me which of these sensors I should use on my SkyLake machine? I tried using the ACPIMonitor, GeforeceSensor, ITEIT87x and it either reboots the system or it will end up in kernel panic.

Link to comment
Share on other sites
Slice
Slice
Posted
  • Author
Posted

Yes I know about the fake/inaccurate readings. but when I use your version of the GeForeceSensor.kext it gives me the kernel panic. Is there anything that can be done?

 

Can you please tell me which of these sensors I should use on my SkyLake machine? I tried using the ACPIMonitor, GeforeceSensor, ITEIT87x and it either reboots the system or it will end up in kernel panic.

My Skylake machine works with HWSensors3.

But GeforceSensors seems unsupported Pascal cards. Remove this kext.

I have the Skylake Asus H170I-PLUS desktop. Unfortunately, my dsdt doesn't have an embedded controller, or a method TACH for the fan speed.

 

My SuperIO chip is the Nuvoton NCT6793D.

 

I tried the latest revision 51 of HWSensor3, FakeSMC.kext, ACPIMonitor.kext, IntelCPUMonitor.kext, and W836x.kext. But, I get 0 rpm for the CPU Fan speed.

 

I'm trying to get the fan rpm, but either my dsdt is missing the proper code for the fan speed, or the W836x.kext doesn't support my Nuvoton NCT6793D.

The kext supports NCT6793D

        case 0xD1:
            model = NCT6793D;
            break;

Did you see any kernel messages like this?

DebugLog("found unsupported chip ID=0x%x REVISION=0x%x", id, revision);

Link to comment
Share on other sites
Slice
Slice
Posted
  • Author
Posted

What is the differences with the FakeSMC RehabMan ➤ 6.25-333-g05e0f4be.1759

 

the FakeSMC 3.5.0 does not boot Snow Leopard 10.6.8

I compile it for 64bit only and set minimum OS 10.8.

3.5.0 contains compatibility with High Sierra.

For Snow you may use older 3.4.1 with HWInfo.kext. 

  • Like 2
Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

I compile it for 64bit only and set minimum OS 10.8.

3.5.0 contains compatibility with High Sierra.

For Snow you may use older 3.4.1 with HWInfo.kext. 

 

i tested 10.6~10.13 on my sandy laptop

 

i checked 10.8 mountain lion. failed load fakesmc.

10.9~10.13 no problem.

 

For Snow you may use older 3.4.1 with HWInfo.kext. 

-checked.

 

 

what is 3.4.1 latest version? HWSensors3-rev43.pkg.zip right?

 

thanks in advance.

 

EDIT1.

also i wonder one

if has FakeSMC.kext in other folder and 10.6 folder, what is happen?

other fakesmc 3.5.0

10.6  fakesmc 3.4.1

 

loaded fake 3.4.1 right if boot 10.6?

Link to comment
Share on other sites
Riley Freeman
Riley Freeman
Posted
Posted

I just updated my X79 to the latest rev51 from the rev33 that I've been using for the past year or so.

 

GeforceSensors is showing 10x the speeds for Core and Shaders (should be 405 and 810). Rolling back to the older kext fixed this.

 

Also, is there any way to have the Batteries section in HWMonitorSMC not show up while running on a desktop? Again, rolling back to the older version fixed this for me.

post-267996-0-88050300-1507388475_thumb.png

Link to comment
Share on other sites
Slice
Slice
Posted
  • Author
Posted

I just updated my X79 to the latest rev51 from the rev33 that I've been using for the past year or so.

 

GeforceSensors is showing 10x the speeds for Core and Shaders (should be 405 and 810). Rolling back to the older kext fixed this.

 

Also, is there any way to have the Batteries section in HWMonitorSMC not show up while running on a desktop? Again, rolling back to the older version fixed this for me.

GeforceSensors is wrong. For my case it shows 2050MHz while it must be 625MHz as Windows said.

I know about Battery section but I very poor know Objective-C and can't correct this.

There is no problem to use on desktop older version. This version has a difference only for laptops.

  • Like 1
Link to comment
Share on other sites
Allan
Allan
Posted
Posted

PS. Using VoodooBatterySMC assumes you need no double it by ACPIBatteryManager.

So, If I'll use your kext, I need to delete the RehabMan's kext?

i reworked the app, now show voltage and amperage using rehabman's kext by just reading kIOPMPSVoltageKey and kIOPMPSCurrentCapacityKey.

If I use the HWMonitorSMC.app after extractin it, I've got this error message:

Screen Shot 2017-10-14 at 22.47.58.png

Link to comment
Share on other sites
vector sigma
vector sigma
Posted
Posted

So, If I'll use your kext, I need to delete the RehabMan's kext?

If I use the HWMonitorSMC.app after extractin it, I've got this error message:

attachicon.gifScreen Shot 2017-10-14 at 22.47.58.png

don't know, it tells you is damaged, but redownloading it is fine here.

No, mA means current in units "milliAmpers".

mAh means capacity in units mA * hours.

How many hours the laptop can work with battery can be calculated from capacity and current

Hours = mAh/mA 

ok got it. So the one attached is now perfect, tested with VoodooBatterySMC.kext and ACPIBatteryManager.kext.

P.S. I introduced I little bug and by clicking voltage it may be always displayed in the top bar. Don't panic I'll fix it.... now I'v to go. please let me know

Have to correct myself, this bug was already there: fixed.

Also, is there any way to have the Batteries section in HWMonitorSMC not show up while running on a desktop? Again, rolling back to the older version fixed this for me.

Well, I think should be easy, but no time today. I'll looking into this later.

hwmonitor.zip

HWMonitorSMC.app.zip

  • Like 1
Link to comment
Share on other sites
vector sigma
vector sigma
Posted
Posted

You will be very useful.

Explain me please these issues

attachicon.gifСнимок экрана 2017-10-17 в 22.53.31.png

Is my corrected sources differ from your? attachicon.gifhwmonitor.zip

I have Xcode 9.0.1, in OS 10.12.6.

in IOBatteryStatus.h you should add these function's declaration:

+(NSDictionary *)getIOPMPowerSource;
+(int) getBatteryVoltageFrom:(NSDictionary *)IOPMPowerSource;
+(int) getBatteryAmperageFrom:(NSDictionary *)IOPMPowerSource; 

and in IOBatteryStatus.m the corresponding functions:

+ (NSDictionary *) getIOPMPowerSource
{
    CFMutableDictionaryRef matching , properties = NULL;
    io_registry_entry_t entry = 0;
    matching = IOServiceMatching( "IOPMPowerSource" );
    entry = IOServiceGetMatchingService( kIOMasterPortDefault , matching );
    IORegistryEntryCreateCFProperties( entry , &properties , NULL , 0 );
    
    NSDictionary * dict = CFBridgingRelease(properties);
    IOObjectRelease( entry );
    return dict;
}

// Voltage measured in mV
+ (int) getBatteryVoltageFrom:(NSDictionary *)IOPMPowerSource
{
    if (IOPMPowerSource && [IOPMPowerSource objectForKey:@kIOPMPSVoltageKey]) {
        return [[IOPMPowerSource objectForKey:@kIOPMPSVoltageKey] intValue];
    }
    
    return 0;
}

// Capacity measured in mA
+ (int) getBatteryAmperageFrom:(NSDictionary *)IOPMPowerSource
{
    if (IOPMPowerSource && [IOPMPowerSource objectForKey:@kIOPMPSAmperageKey]) {
        int mA = [[IOPMPowerSource objectForKey:@kIOPMPSAmperageKey] intValue];
        return (mA > 0) ? mA : (0 - mA);
    }
    
    return 0;
}

both before @end.

More, on top of the .h or the .m file (better the .m) you must add:

#import <IOKit/pwr_mgt/IOPM.h>

Only needed to get the keys kIOPMPSAmperageKey and kIOPMPSVoltageKey (or all the others in the IOPMPowerSource dictionary). Their strings can change in time, who knows, but not the macros.

 

 

Your original project does not use default Xcode settings so little differences in the "Build Settings" to avoid common clang's warnings.. so to restore them. it should work anyway.

Latest project I posted was just the one in:

../hwsensors-hwsensors3-code/trunk/hwmonitor 

+ my modification. Basically this code will work with voodoo, rehabman's kext... or just in a real mac, since all kexts publish the same thing in IOPMPowerSource.

See that this time I used kIOPMPSAmperageKey (mA) as suggested by you.

Link to comment
Share on other sites
Slice
Slice
Posted
  • Author
Posted

Good! Your changes accepted.

See Battery section is empty. 

Снимок экрана 2017-10-18 в 8.17.49.png

can we make it invisible if no batteries found?

 

And do you want to be a developer of the project? I can give you commit access to sf.net just tell me your nickname there.

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