Jump to content
2,189 posts in this topic

Recommended Posts

Ideally, HWSensors could be configured (e.g. by plist) to only show values of interest.

So I can select what information I can display in what order.

As an example... most fans are not active or relevant, so it makes a lot of sense to only pick the relevant ones.

 

Link to comment
Share on other sites

9 hours ago, tyufhl said:

@vector sigma hi, after the launch of DarwinDumper / CPU 2077731448_2020-01-2322_04_32.png.7c4ab1ff3615431c17ec53f828b3f261.pngsuch a picture 

DarwinDumper contains Pike R. Alpha's' AppleIntelInfo.kext v2.9. which is very wrong and dangerous.

Exclude it from

/DarwinDumper.app/Contents/Resources/public/drivers/AppleIntelInfo.kext

Move to trash!

 

  • Like 1
Link to comment
Share on other sites

On 1/22/2020 at 7:18 AM, jinbingmao said:

 

On 1/22/2020 at 7:26 AM, Andrey1970 said:

Thanks, but wait a moment. If we are going to create a database, we need rules naming things:

 

1)

SYS_FAN2 or Sys Fan 2?

What is CPU_OPT?

What to do with unconnected sensors? My NTC sensor has more fans than the motherboard have, so I'm going to skip the sensor:

2129907392_Schermata2020-01-24alle12_58_50.png.60ee7df4c521cb3c273ab4e10c508d40.png

Is that the case for your CPU_OPT? I mean, if the LPC chip has has an unused line (no connector on the motherboard), this must be skipped.... my 2 cents.

 

2) if we have a convention for naming things, and we follow it, the app can translate SYS_FAN2 (or Sys fan 2) into your native language. 

 

What do you think?

 

On 1/22/2020 at 7:33 PM, ctich said:

@vector sigma

Thanks! :thumbsup_anim:

Tell me, is it difficult to add the ability to sort sensors? To install in the correct order.

Example:

CPUVCORE

+12V

+5V

3VCC

3VSB

VIN0

....

VIN8

 

It can be done at app initialization, in alphabetical order, what ever will be. I'll take a look on it when I have more time with out priority.

  • Like 1
Link to comment
Share on other sites

On 1/23/2020 at 1:03 AM, Mike Ranger said:

Ideally, HWSensors could be configured (e.g. by plist) to only show values of interest.

So I can select what information I can display in what order.

As an example... most fans are not active or relevant, so it makes a lot of sense to only pick the relevant ones.

 

That is why I say we need rules. Once a configurations is made, that configuration must contains all the fans that a motherboard can really have: you cannot have the chassys Fan for your own purpose (the noise) but the configuration must include it because this will help other users.

 

Later I'll add the possibility to load a config from the nvram (a path to a plist), so anyone can customize even more names or skip unused sensors. This can be usefull when you doesn't have Fans... but Pumps.

 

Link to comment
Share on other sites

2 minutes ago, vector sigma said:

 

Thanks, but wait a moment. If we are going to create a database, we need rules naming things:

 

1)

SYS_FAN2 or Sys Fan 2?

What is CPU_OPT?

What to do with unconnected sensors? My NTC sensor has more fans than the motherboard have, so I'm going to skip the sensor:

2129907392_Schermata2020-01-24alle12_58_50.png.60ee7df4c521cb3c273ab4e10c508d40.png

Is that the case for your CPU_OPT? I mean, if the LPC chip has has an unused line (no connector on the motherboard), this must be skipped.... my 2 cents.

 

2) if we have a convention for naming things, and we follow it, the app can translate SYS_FAN2 (or Sys fan 2) into your native language. 

 

What do you think?

 

 

I wrote as on the motherboard. CPU_OPT it for cpu pump or cpu fan2.

Parameter skip is good idea.

I offer such names:

System Fan Х
CPU Fan Х

Link to comment
Share on other sites

20 minutes ago, zkingtut said:

Hi guys 

I am currently using VirtualSMC v1.1.0 with HWMonitorSMC2.app_v2.5.1Beta by@vector sigma 

So far everything seems to be OK .

But I can't monitor Fan Speed 

I don't know where should I start to make fan appear in HwMonitor ? How to add it ? 

How to customize SMCsuperIO.kext for my fan ?

 

I had the same issue with FakeSMC.kext as well 

 

( Laptop is Lenovo ThinkPad  P50 , Catalina 10.15.2 , Clover 5103 )

 

 

Thank you 

I think you can't. Slice made possible for Dell only, but usually laptop's fans can't be controlled, or at least is not clear how.

But if you want only to show them, you should take a look at ACPIMonitor.kext, but require acpi knowledge and skills.

  • Like 1
Link to comment
Share on other sites

16 hours ago, vector sigma said:

@Slice, I propose to do that as well:

 

429681868_Schermata2020-01-24alle13_23_23.thumb.png.555b2951f97b361904e5000f4ad4d8b2.png

maybe we can switch from smc keys to that using a boot flag  ..like '-hwnokeys'

Real Macs have SMC keys for FAN, temperatures, voltages.

Why we should take values from ioreg data that absent in real Mac?

  VC0C  [flt ]  (bytes 80 14 85 3f)
  VC0G  [flt ]  (bytes 42 f4 05 3b)
  VD2R  [flt ]  (bytes dc ab 41 41)
  VG0C  [flt ]  (bytes b0 d1 5a 3f)
  VG0I  [flt ]  (bytes af 12 63 3f)
  VM0R  [flt ]  (bytes c0 5c 99 3f)
  F0AB  [sp78]  (bytes e5 00)
  F0AH  [spf0]  (bytes 0e 10)
  F0AL  [spf0]  (bytes 0a 8c)
  F0AP  [spf0]  (bytes 00 71)
  F0AS  [sp78]  (bytes 22 80)
  F0Ac  [fpe2]  1197 (bytes 12 b4)
  F0ID  [{fds]  (bytes 00 00 10 00 4d 61 69 6e 20 00 00 00 00 00 00 00)
  F0Mn  [fpe2]  1200 (bytes 12 c0)
  F0Mt  [ui16]  0 (bytes 00 00)
  F0Mx  [fpe2]  2700 (bytes 2a 30)
  F0Tg  [fpe2]  1200 (bytes 12 c0)
  FNum  [ui8 ]  1 (bytes 01)
  FOff  [ui8 ]  0 (bytes 00)
  FPDc  [fp79]  (bytes 21 34)
  FRmn  [ui16]  0 (bytes 00 00)
  FRmp  [ui16]  0 (bytes 00 00)
  FS!   [ui16]  0 (bytes 00 00)
  FSDc  [ui16]  0 (bytes 69 00)
etc....

 

  • Like 1
Link to comment
Share on other sites

5 hours ago, Slice said:

Real Macs have SMC keys for FAN, temperatures, voltages.

Why we should take values from ioreg data that absent in real Mac?

Oh no, I did not suggest to abandon SMC keys, otherwise third party Monitors will stop working, of course. But I ask for a possibility to do that (with a boot flag? and switch from fakeSMC->callPlatformFunction to something else?) and so reuse common configurations (Raw data should be the same, I guess)...  which I see peoples start posting... . 

Other than that there will be no encoding and so no decoding, no open and closed of the smc driver, with a little visible cpu usage in less (is not my imagination, in my lappy is).

 

P.S. HWMonitorSMC2 looks (once) for a children of IOPCIDevice->LPCB that contains "Sensors", if present, it will not search for SMC keys. Will do it otherwise, as usual.

  • Like 1
Link to comment
Share on other sites

×
×
  • Create New...