Jump to content

HWSensors3

Slice

By Slice,
in Hardware Sensors

 Share
2,189 posts in this topic

Recommended Posts

AKlion
AKlion
Posted
Posted
On 3/3/2019 at 2:37 AM, Rodion2010 said:

it is a good idea to make some hwinfo, hwmonitor and hwsensors dumps in Windows and/or Linux

you will see there exact model of your Super IO chip and number of available sensors

How can i do this? What is this done?

Link to comment
Share on other sites
Alpha22
Alpha22
Posted
Posted
On 2/23/2019 at 5:40 PM, vector sigma said:

@losinka and all, I've just finished to rewrite the video cards detection with a simplified code but I need to see if is ok. In that program I've also added the "Metal" ability detection:

vclist.zip

 

Thanks in advance!

 

P.S. you can run the program in 10.9 +

 

Last login: Mon Mar  4 10:56:06 on ttys000

Fabios-iMac:~ fabio$ /Users/fabio/Downloads/vclist 

----------------------------------------------------

vclist (vector sigma 2018), found 1 graphics card!

----------------------------------------------------

Model               = Intel HD Graphics 4600

vendor ID           = <86800000>

vendor ID           = <12040000>

revision ID         = <06000000>

subsystem ID        = <34850000>

sub system VendorID = <6b100000>

 

 

Device Utilization  = 0%

vram Used           = 252534784 bytes

vram Free           = 1358077952 bytes

  • Like 1
Link to comment
Share on other sites
unixb0y
unixb0y
Posted
Posted (edited)

Hello everybody, I just got linked to this thread and installed these kext files into EFI/CLOVER/kexts/Other:

ACPIMonitor.kext

FakeSMC.kext

IntelCPUMonitor.kext

RadeonMonitor.kext

W836x.kext

The HWMonitorSMC2 unfortunately shows empty "CPU → Core Frequencies" and "CPU → Core Temperatures". Intel Power Gadget Info works. "Main Logic Board" and "Fans or Pumps" are empty. "Media Health" works, but I don't need it (can you disable it?).

Most important for me are the CPU frequencies and temperatures as well as GPU info which doesn't show up at all right now. edit: GPU info works perfectly! I only needed to activate it in the App's settings after rebooting.

I still need to do the DSDT; is it possible that it will solve all of this or do you only need that patch for the fans? Because those aren't that crucial for me and I haven't messed with DSDT patching yet. Don't want to break anything :P

Edited by unixb0y
Link to comment
Share on other sites
Slice
Slice
Posted
  • Author
Posted
9 minutes ago, unixb0y said:

Hello everybody, I just got linked to this thread and installed these kext files into EFI/CLOVER/kexts/Other:

ACPIMonitor.kext

FakeSMC.kext

IntelCPUMonitor.kext

RadeonMonitor.kext

W836x.kext

The HWMonitorSMC2 unfortunately shows empty "CPU → Core Frequencies" and "CPU → Core Temperatures". Intel Power Gadget Info works. "Main Logic Board" and "Fans or Pumps" are empty. "Media Health" works, but I don't need it (can you disable it?).

Most important for me are the CPU frequencies and temperatures as well as GPU info which doesn't show up at all right now.

I still need to do the DSDT; is it possible that it will solve all of this or do you only need that patch for the fans? Because those aren't that crucial for me and I haven't messed with DSDT patching yet. Don't want to break anything :P

What is your CPUID? You can find it in clover boot-log or elsewhere.

Link to comment
Share on other sites
unixb0y
unixb0y
Posted
Posted (edited)
30 minutes ago, Slice said:

What is your CPUID? You can find it in clover boot-log or elsewhere.

 

0:101  0:000  === [ GetCPUProperties ] ==================================
0:101  0:000  CPU Vendor = 756E6547 Model=906EA
0:101  0:000   The CPU supported SSE4.1
0:101  0:000  BrandString = Intel(R) Core(TM) i5-8600K CPU @ 3.60GHz
0:101  0:000   The CPU supported turbo
0:101  0:000  MSR 0x35               60006
0:101  0:000   TSC/CCC Information Leaf:
0:101  0:000    numerator     : 300
0:101  0:000    denominator   : 2
0:101  0:000   Calibrated ARTFrequency: 24003251
0:101  0:000  MSR 0xE2 before patch 1E000000
0:101  0:000  MSR 0xCE              08080838_F1012400
0:101  0:000  corrected FLEX_RATIO = E0000
0:101  0:000  MSR 0x1B0             00000000
0:101  0:000  FSBFrequency = 100 MHz, DMI FSBFrequency = 100 MHz, Corrected FSBFrequency = 100 MHz
0:101  0:000  MaxDiv/MinDiv: 36.0/8
0:101  0:000  Turbo: 42/42/43/43
0:101  0:000  Features: 0xBFEBFBFF
0:101  0:000  Threads: 6
0:101  0:000  Cores: 6
0:101  0:000  FSB: 100 MHz
0:101  0:000  CPU: 3600 MHz
0:101  0:000  TSC: 3600 MHz
0:101  0:000  PIS: 100 MHz

 

I think the CPU ID is 906EA ?

Edited by unixb0y
Link to comment
Share on other sites
unixb0y
unixb0y
Posted
Posted

Another question is: how to know which LPC chip my mainboard has? Mine is ASUS, so I chose W836x.kext, but I'm not sure that it is the right one since I don't get sensor info. 

Link to comment
Share on other sites
vector sigma
vector sigma
Posted
Posted
3 hours ago, unixb0y said:

Another question is: how to know which LPC chip my mainboard has? Mine is ASUS, so I chose W836x.kext, but I'm not sure that it is the right one since I don't get sensor info. 

as already suggested by Rodion2010 why not make a dump of Super-I/O in linux or Windows using some programs able to do that?

 

example output of lm_sensors in Linux: 

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): 
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               Yes
Found unknown chip with ID 0x1a11
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

 

Link to comment
Share on other sites
unixb0y
unixb0y
Posted
Posted
6 minutes ago, vector sigma said:

as already suggested by Rodion2010 why not make a dump of Super-I/O in linux or Windows using some programs able to do that?

 

example output of lm_sensors in Linux: 


Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): 
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               Yes
Found unknown chip with ID 0x1a11
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

 

 

I didn’t know he was referring to me. My main issue is getting the CPU info. I don’t have Dual Boot but I can probably boot a live Linux USB, execute the commands and let you know. 

Would anything speak against just trying every one of the kext files on its own?

Link to comment
Share on other sites
vector sigma
vector sigma
Posted
Posted
16 minutes ago, losinka said:

Yes, it works :)

Good ;-)

12 minutes ago, unixb0y said:

 

I didn’t know he was referring to me. My main issue is getting the CPU info. I don’t have Dual Boot but I can probably boot a live Linux USB, execute the commands and let you know. 

Would anything speak against just trying every one of the kext files on its own?

No because each plugin is configurable, may be that you need additional info to let the kext to work.... and in cases is not supported you will know why.

 

Link to comment
Share on other sites
unixb0y
unixb0y
Posted
Posted
3 minutes ago, vector sigma said:

Good ;-)

No because each plugin is configurable, may be that you need additional info to let the kext to work.... and in cases is not supported you will know why.

 

 

I see thanks! Then I will do that. What’s the tool again?

Link to comment
Share on other sites
vector sigma
vector sigma
Posted
Posted
24 minutes ago, ctich said:

hi, wrong data.

RX 550 4Gb.

It perfectly reads what is in your ioreg, but the question is another:

why gartFreeBytes and gartUsedBytes are present inside your ioreg if the RX 550 isn't a card that share memory with the System? (e.g. that is expected for IGPUs). At least correct me if I'm wrong.

 

In fact usually there should be vramFreeBytes and vramUsedBytes, see the documentation:

Quote

Current Mapped AGP Memory

The total number of bytes mapped into AGP Graphics Address Remapping Table (GART). gartUsedBytes

 

Current Free AGP Memory

The total number of free bytes in the AGP Graphics Address Remapping Table (GART). gartFreeBytes

 

 

Current Video Memory in Use

The total number of bytes of VRAM in use. This parameter is vendor specific and not available for all drivers. vramUsedBytes

 

Current Free Video Memory

The total number of bytes of free VRAM. This parameter is vendor specific and not available for all drivers. vramFreeBytes

see here: https://developer.apple.com/library/archive/documentation/GraphicsImaging/Conceptual/OpenGLDriverMonitorUserGuide/Glossary/Glossary.html

Link to comment
Share on other sites
vector sigma
vector sigma
Posted
Posted (edited)

@ctich

no, it's the same. vramFreeBytes is present, but no vramUsedBytes. so gartUsedBytes is used instead... can't match with real value.

 

theory (теория):

I cannot found the "VRAM,totalMB" key. Can you try to inject it with Clover or by DSDT to see if something change?

 

..don't know.. something like that: 

"VRAM,totalsize", 
Buffer (0x04)
{
0xFF, 0xFF, 0xFF, 0xFF
},

(not sure)

 

or maybe in Clover(@Slice is right??): 

<dict>
	<key>Graphics</key>
	<dict>
		<key>VRAM</key>
		<integer>4096</integer>
	</dict>
</dict>

 

Edited by vector sigma
typo
Link to comment
Share on other sites
unixb0y
unixb0y
Posted
Posted (edited)
1 hour ago, vector sigma said:

I wrote it in my last post, you can't see 'lm_sensors' :whistle:? 

 

On Mint it seems to be 'sensors-detect', I think :huh:

At least it said that thats how it is called when trying to execute 'lm_sensors'.

Here is the output with the --auto option: https://pastebin.com/Gs1jHCkY

Edit: I ran it again in manual mode, accepting everything. Here's the output:

https://pastebin.com/ahZUYDAD

Edited by unixb0y
Link to comment
Share on other sites
unixb0y
unixb0y
Posted
Posted
Just now, vector sigma said:

model NCT6793D, supported.

 

Great! Where to go from there? Wrong kext? Or need DSDT patch?

Link to comment
Share on other sites
vector sigma
vector sigma
Posted
Posted (edited)
25 minutes ago, unixb0y said:

 

Great! Where to go from there? Wrong kext? Or need DSDT patch?

In the W836x.kext/Contents/Info.plist navigate to:

IOKitPersonalities->Winbond W836x Monitor Plugin->Sensors Configuration->ASUS.

Start by creating your motherboard settings by copying the one most similar or search for a similar configuration on the net:

716233546_Schermata2019-03-04alle21_52_50.thumb.png.a479cbe599074104125998e6aceb14ea.png

 

Or just edit the default configuration. Good luck!

 

P.S. Use a plist editor and don't use mine. If you want to try the Z370-A configuration copy the node I made (by copying another Zxxx) to your existing Info.plist.

 

Info.plist.zip

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