Jump to content

HWSensors3

Slice

By Slice,
in Hardware Sensors

 Share
2,189 posts in this topic

Recommended Posts

vector sigma
vector sigma
Posted
Posted
Just now, Andres ZeroCross said:

But with FakeSMC.kext and plugin, all my fan is detected well. So i don't need dsdt patch ofcourse. Maybe related to keys of smc. I don't know

Sent from my Mi Note 2 using Tapatalk
 

Hi, ask Slice for these kind of things as I'm really noob as I don't care personally, the app show datas from what plugins provide but really I can't help for that.

  • Like 1
Link to comment
Share on other sites
Andres ZeroCross
Andres ZeroCross
Posted
Posted
Hi, ask Slice for these kind of things as I'm really noob as I don't care personally, the app show datas from what plugins provide but really I can't help for that.
Thanks for the response, maybe i should wait for new plugin for VirtualSMC.kext. again, thanks very much

Sent from my Mi Note 2 using Tapatalk

Btw,, My F200 is SSD too. But Life value is not shown. Any clue???

Screen Shot 2018-10-12 at 23.32.53.png

  • Like 1
Link to comment
Share on other sites
vector sigma
vector sigma
Posted
Posted
6 minutes ago, Andres ZeroCross said:

Thanks for the response, maybe i should wait for new plugin for VirtualSMC.kext. again, thanks very much

Sent from my Mi Note 2 using Tapatalk
 

Btw,, My F200 is SSD too. But Life value is not shown. Any clue???

Screen Shot 2018-10-12 at 23.32.53.png

Here I can help. Mechanical hard drives do not have a life to read, so you'll never see it. This happens also with some old ssd, and also some unknown ssd, that, because any vendor can set the life attribute in any places in a sub structure called "vendor specific data" inside the 512 bytes of the S.M.A.R.T atrributes. Therefore it is not guaranteed that Life will always be displayed even for them.

Link to comment
Share on other sites
Andres ZeroCross
Andres ZeroCross
Posted
Posted (edited)
14 minutes ago, vector sigma said:

Here I can help. Mechanical hard drives do not have a life to read, so you'll never see it. This happens also with some old ssd, and also some unknown ssd, that, because any vendor can set the life attribute in any places in a sub structure called "vendor specific data" inside the 512 bytes of the S.M.A.R.T atrributes. Therefore it is not guaranteed that Life will always be displayed even for them.

Owh, but i am pretty sure life value is shown with FakeSMC.kext and plugin. Do you think this issue is related to plugin of FakeSMC.kext too??

image.png.c0f27aace7f6c77d7fd70707adb5e363.pngI use HW Monitor with VirtualSMC.kext and plugin (not FakeSMC.kext). See this

Also my Galax SSD is not shown status of life (my notebook) :)

Just for information

photo_2018-10-12_23-00-56.thumb.jpg.390742ca10cf24fe4c189ee46b44d9ae.jpg

 

 

 

Edited by Andres ZeroCross
Change picture
Link to comment
Share on other sites
vector sigma
vector sigma
Posted
Posted
4 minutes ago, Andres ZeroCross said:

Owh, but i am pretty sure life value is shown with FakeSMC.kext and plugin

I don't think this is due to the SMC keys, but from S.M.A.R.T instead. As I said the app should know where to look for the life attribute, and your F200 then is an SSD... unknown at least for me. Can you point me to the data sheet of that disk?

Link to comment
Share on other sites
Andres ZeroCross
Andres ZeroCross
Posted
Posted
5 minutes ago, vector sigma said:

I don't think this is due to the SMC keys, but from S.M.A.R.T instead. As I said the app should know where to look for the life attribute, and your F200 then is an SSD... unknown at least for me. Can you point me to the data sheet of that disk?


Fujitsu F100 = https://www.fujitsu.com/hk/Images/F100-SSD-datasheet.pdf

Galax 240GB Gamer series : http://www.galax.com/en/ssd/gamer-series/galax-gamer-ssd-l-240gb.html

Sorry i can't search data sheet for GALAX, just official site :)

Link to comment
Share on other sites
vector sigma
vector sigma
Posted
Posted
6 hours ago, fabiosun said:

less of usual..but maybe new one cores appear (16 and 17)

new function I created was bad: 

- (NSString *)smcFormat:(int)num {
  if (num > 15) {
    for (char c = 'A'; c <= 'Z'; c++) {
      int i = (int)c - 55;
      if (i == num) {
        return [NSString stringWithFormat:@"%c", c];
      }
    }
  }
  return [NSString stringWithFormat:@"%d", num];
}

corrected: 

- (NSString *)smcFormat:(int)num {
  if (num > 15) {
    for (char c = 'A'; c <= 'Z'; c++) {
      int i = (int)c - 55;
      if (i == num) {
        return [NSString stringWithFormat:@"%c", c];
      }
    }
  }
  return [NSString stringWithFormat:@"%.1X", num];
}

should work now.

HWMonitorSMC2.app_IPG_beta6.zip

Link to comment
Share on other sites
Guest
Guest
Posted
Posted

Hi @vector sigma

two minor details

Igpu utilization in HWmonitor SMC Beta 7(also in beta 5 but there is named GPU utilization  ) IPG tab has always a value of 0 in my case (right because my cpu as no IGPU inside)

During CPU benchmark it show a value of 1 (alternatively to 0%)

 

in CPU Power tab I see CPU Package Core always to 0,00 W (V2.3.0 IPG 3.5.5 beta 7 and 5)

Also if can be useful to check see this picture

 

250067684_ScreenShot2018-10-13at6_06_43PM.png.ca4ce99a342d96e887409b50ee82da61.png

I would like also to ask in CPU Power tab what is CPU Package total

thank you

 

Link to comment
Share on other sites
Andrey1970
Andrey1970
Posted
Posted

@vector sigma

1. 

Delete all parameters from group "Intel® Power Gadget", except "CPU Frequency" and "IGPU Frequency".

Rename group "Intel® Power Gadget" in "CPU Frequencies".

Allow the user to activate "Show CPU Frequencies from Intel® Power Gadget" in settings.

 

2.

In group "CPU Power", rename "CPU Package GFX" in "CPU Package IGPU".

 

3.

Delete "Device Unit 0 Utilization" from group GPUs IGPU.

 

4. Move it.

1594047997_2018-10-142_42_05.png.3860b2bd7328284dd960cedcf7c6f610.png

Link to comment
Share on other sites
vector sigma
vector sigma
Posted
Posted (edited)
10 hours ago, thenightflyer said:

did you remove cpu frequencies? I see no more frequency core multiplier....

no. But with IntelCPUMonitor.kext always worked, isn't?

9 hours ago, fabiosun said:

Igpu utilization in HWmonitor SMC Beta 7(also in beta 5 but there is named GPU utilization  ) IPG tab has always a value of 0 in my case (right because my cpu as no IGPU inside)

Solved in next beta8

Edited by vector sigma
Link to comment
Share on other sites
vector sigma
vector sigma
Posted
Posted
8 hours ago, fabiosun said:

in CPU Power tab I see CPU Package Core always to 0,00 W (V2.3.0 IPG 3.5.5 beta 7 and 5)

Also if can be useful to check see this picture

Those keys are provided by FakeSMC/VirtualSMC and I have no idea how to fix them. anyway the code check for a null value and the sensor it is added because has a valid value, even if 0. If doesn't change I have no idea  but looking at an smc dump will make things clear (i.e if it is always 0).

Those keys are redundant with the one provided by Intel Power Gadget, I guess. CPU Package Total is the Core Power + NB Power and it is usefull to see under a test stress if your cpu goes nearly the limit of the thermal design point.

 

Link to comment
Share on other sites
vector sigma
vector sigma
Posted
Posted (edited)
6 hours ago, Slice said:

Why GPU 18160?

It is Nvidia GTX650.

Strange, this is the code: 

- (NSArray *)getOtherFrequencies {
  NSMutableArray *arr = [NSMutableArray array];
  for (int i = 0; i < 0xA; i++) {
    [self validateSensorWithKey:[NSString stringWithFormat:@KEY_FAKESMC_FORMAT_GPU_FREQUENCY, i]
                         ofType:@TYPE_FREQ
                       forGroup:FrequencySensorGroup
                     andCaption:[[NSString alloc] initWithFormat:NSLocalizedString(@"GPU %d Core",nil)]
                        logType:NoLog
                       intoList:arr];
    
    [self validateSensorWithKey:[NSString stringWithFormat:@KEY_FAKESMC_FORMAT_GPU_SHADER_FREQUENCY, i]
                         ofType:@TYPE_FREQ
                       forGroup:FrequencySensorGroup
                     andCaption:[[NSString alloc] initWithFormat:NSLocalizedString(@"GPU %d Shaders",nil), i]
                        logType:GPULog
                       intoList:arr];
    
    [self validateSensorWithKey:[NSString stringWithFormat:@KEY_FAKESMC_FORMAT_GPU_MEMORY_FREQUENCY,i]
                         ofType:@TYPE_FREQ
                       forGroup:FrequencySensorGroup
                     andCaption:[[NSString alloc] initWithFormat:NSLocalizedString(@"GPU %d Memory",nil), i]
                        logType:GPULog
                       intoList:arr];
  }
  return arr;
}

this is the format argument:

#define KEY_FAKESMC_FORMAT_GPU_FREQUENCY        "CG%XC"

 

and as you can see the loop repeat 10 times (0xa). Please check "GPU %d Core" in the Russian Localizable.strings has a good format at the right.

The name of the card is unknown as provided by HWSensor, and for multiple cards I cannot be sure of which one could be.

6 hours ago, Slice said:

"Частоты" = "Frequencies" - good translation

Ok, next beta8

Edited by vector sigma
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...