Jump to content
About Just Joined group Read more... ×

2,089 posts in this topic

Recommended Posts

ok @vector sigma, with VirtualSMC I see dynaminacally increase core package wattage (very useful for me)

I would like to show you a little incongruent data in log:

under CPU 18/36 is correct

Under POWER I see CPUs available is 32.

not important because in app I see all cores from 0 to 17

HWMonitorSMC2 v2.4.3 v5t

MACHINE STATUS:

CPU:
	Name:		Intel(R) Core(TM) i9-7980XE CPU @ 2.60GHz
	Vendor:		GenuineIntel
	Physical cores:	18
	Logical cores:	36
	Family:		6
	Model:		0x55
	Ext Model:		0x5
	Ext Family:		0
	Stepping:		4
	Signature:		0x50654
	Brand:		0
	Features:  FPU VME DE PSE TSC MSR PAE MCE
	                CX8 APIC SEP MTRR PGE MCA CMOV PAT
	                PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2
	                SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON
	                DSCPL VMX EST TM2 SSSE3 FMA CX16 TPR
	                PDCM SSE4.1 SSE4.2 x2APIC MOVBE POPCNT AES PCID
	                XSAVE OSXSAVE SEGLIM64 TSCTMR AVX1.0 RDRAND F16C
	Ext Features:  SYSCALL XD 1GBPAGE EM64T LAHF LZCNT PREFETCHW RDTSCP
	                      TSCI
	Microcode version:	33554509
	Thermal sensors:		1
	Thermal APIC timer:	1

	System:	32%
	User:		0%
	Idle:		66%
	Nice:		0%

LPCB:
	IOName:			pci8086,a2d2
	name:			70 63 69 38 30 38 36 2c 61 32 64 32 00
	device-id:			d2 a2 00 00
	vendor-id:			86 80 00 00
	revision-id:		00 00 00 00
	subsystem-id:		01 50 00 00
	subsystem-vendor-id:	58 14 00 00

MEMORY:
	Physical size:	128.0GB
	Free:			118.32GB
	Wired:		5.18GB
	Active:		4.05GB
	Inactive:		440MB
	Compressed:	0MB

SYSTEM:
	Model:		iMacPro1,1
	Sys name:		Darwin
	OS Version:	10.13.6
	Node name:	fabios-iMac-Pro.lan
	Release:		17.7.0
	Version:		Darwin Kernel Version 17.7.0: Wed Oct 10 23:06:14 PDT 2018; root:xnu-4570.71.13~1/RELEASE_X86_64
	Machine:		x86_64
	Uptime:		0d 0h 5m 40s
	Processes:		291
	Threads:		1107
	Load Average:	[1.48, 1.12, 0.55]
	Mach Factor:	[34.521, 34.44, 34.331]

POWER:
	CPU Speed limit:		100.0%
	CPUs available:		32
	Scheduler limit:		100.0%
	Thermal level:		Not Published

VIDEO CARD 1:
	Model:				NVIDIA TITAN Xp COLLECTORS EDITION
	Vendor ID:				de 10 00 00 (NVidia)
	Device ID:				02 1b 00 00
	Revision ID:			a1 00 00 00
	Subsystem Vendor ID:		de 10 00 00
	Subsystem ID:			10 00 00 00
	class-code:				00 00 03 00
	IOName:				display
	pcidebug:				193:0:0
	built-in:				00
	compatible:			pci10de,123epci10de,1b02pciclass,030000SL05GFX0
	acpi-path:				IOACPIPlane:/_SB/PC02@0/BR2A@0/SL05@ffff
	hda-gfx:				onboard-1
	rm_board_number:		00 00 00 00
	NVDA,noEFI:			true
	NVArch:					GP100
	rom-revision:				VBIOS 86.02.4c.00.01
	NVCLASS:				NVDA
	NVCAP:				05 00 00 00 00 00 ff ff ff ff 00 00 00 00 00 0e 00 00 00 00
	pci-aspm-default:				0x0
	VRAM,totalMB:			ff 2f 00 00
	device_type:			NVDA,Parent
	NVDA,accel-loaded:		01 00 00 00
	vbios-revision:			01 00 4c 02 86
	vNVDA,Features:			00 08 00 00
	IONVRAMProperty:			true
	NVDAinitgl_created:		yes
	IOPCIMSIMode			true
	NVDAType:				Web
	Additional Properties:
		AAPL,slot-name:  	53 6c 6f 74 2d 31 00
		AAPL,ndrv-dev:   	1
	Metal support: true
	Metal properties:
		Max Threads Per Thread group: width 1024, height 1024, depth 64
		Max Thread group Memory Length:	49152
		Recommended Max Working Set Size:	0x0
		Depth 24 Stencil 8 Pixel Format:		true
		Programmable Sample Positions:		false
		Read-Write Texture:				1
		Headless:						false
		Is Low Power:					false
		Removable:						false
	Performance Statistics:
		hardwareWaitTime:                                  	0
		agprefTextureCreationCount:                   	68
		Device Utilization %:                                 	3
		freeSurfaceSwapBufferWaitTime:              	0
		agpTextureCreationBytes:                        	0
		stdTextureCreationBytes:                         	0
		orphanedReusableSysMemoryCount:        	62
		gartCacheBytes:                                       	33554432
		gartMapInBytesPerSample:                       	15896576
		surfaceWriteLockIdleWaitTime:                 	0
		swapCompleteGLWaitTime:                      	0
		vramLargestFreeBytes:                             	11287289856
		finishAll2DWaitTime:                                	0
		vramEvictionWaitTime:                             	0
		dataBufferCount:                                      	0
		surfaceBufferPageOutBytes:                      	0
		stdTextureCreationCount:                        	0
		ioSurfacePageOutBytes:                            	0
		iosurfaceTextureCreationCount:               	1
		ioSurfaceReadOutBytes:                           	0
		orphanedNonReusableVidMemoryBytes:   	0
		agprefTextureCreationBytes:                    	2334720
		oolTextureCreationBytes:                         	0
		freeDataBufferWaitTime:                          	0
		swapCompleteVideoWaitTime:                 	0
		agpTextureCreationCount:                       	0
		volatileSurfaceCount:                               	0
		iosurfaceTextureCreationBytes:                	458752
		bufferFlipCount:                                       	0
		context2DCount:                                      	6
		GPU Core Utilization:                                	120000000
		surfaceCopyInWaitTime:                           	0
		swapBytesPerSample:                               	0
		stdTexturePageInBytes:                            	0
		finishGLWaitTime:                                    	0
		vramFreeBytes:                                         	11703222272
		gartSizeBytes:                                          	45812985856
		orphanedReusableVidMemoryBytes:         	0
		orphanedReusableVidMemoryHitRate:      	2
		surfaceTextureCreationCount:                 	0
		surfaceCount:                                          	8
		textureReadOutBytes:                               	0
		bufferSwapCount:                                    	0
		freeSurfaceBackingWaitTime:                   	0
		hardwareSubmitWaitTime:                        	0
		surfaceBufferPageInBytes:                        	0
		vramUsedBytes:                                        	1181351936
		sysmemUsedBytes:                                   	0
		clientGLWaitTime:                                    	0
		finishCLWaitTime:                                    	0
		gartFreeBytes:                                          	45761064960
		finishVideoWaitTime:                               	0
		inUseSysMemoryBytes:                             	880525312
		orphanedNonReusableSysMemoryBytes:   	0
		orphanedReusableSysMemoryBytes:         	315924480
		surfaceBufferReadOutBytes:                     	0
		finish2DWaitTime:                                    	0
		orphanedReusableSysMemoryHitRate:      	2
		contextVideoCount:                                 	0
		surfaceBufferTextureCreationCount:        	0
		orphanedReusableVidMemoryCount:        	0
		recoveryCount:                                         	0
		freeToAllocGPUAddressWaitTime:            	0
		oolTexturePageInBytes:                            	0
		gartMapOutBytesPerSample:                     	14589952
		gartUsedBytes:                                         	51920896
		texturePageOutBytes:                               	0
		textureCount:                                          	978
		oolTextureCreationCount:                        	0
		inUseVidMemoryBytes:                             	1196449792
		GPU Memory Utilization:                           	100000000
		contextGLCount:                                      	2
		orphanedNonReusableVidMemoryCount:  	0
		textureVolunteerUnloadBytes:                  	0
		surfaceSetShapeIdleWaitTime:                  	0
		dataBytesPerSample:                                	0
		ioSurfacePageInBytes:                              	458752
		contextCLCount:                                      	2
		swapComplete2DWaitTime:                      	0
		surfaceCopyOutWaitTime:                        	0
		orphanedNonReusableSysMemoryCount:  	0
		surfaceReadLockIdleWaitTime:                 	0

SCREEN 1:
	Framebuffer:	0x1B5611B5
	EDID contents:

	Header:		00 ff ff ff ff ff ff 00
	Serial number:	f4 d3 05 00
	Version:		01 04
	Basic params	b5 3c 22 78 9e
	Chroma info:	30 35 a7 55 4e a3 26 0f 50 54
	Established:	21 08 00
	Standard:		71 40 81 80 81 c0 a9 c0 d1 c0 81 00 01 01 01 01
	Descriptor 1:	4d d0 00 a0 f0 70 3e 80 30 20 65 0c 58 54 21 00 00 1a
	Descriptor 2:	28 68 00 a0 f0 70 3e 80 08 90 65 0c 58 54 21 00 00 1a
	Descriptor 3:	00 00 00 fd 00 38 3d 1e 87 38 00 0a 20 20 20 20 20 20
	Descriptor 4:	00 00 00 fc 00 4c 47 20 55 6c 74 72 61 20 48 44 0a 20
	Extension:		01
	Checksum:		c8

	Manufacturer: 1e6d (8=8)
	Model: 095b
	Serial Number: 381940
	Resolution: 3840x2160
	Made week 12 of 2017
	EDID version: 1.4
	Digital display
	Established Timings:
		640×480 @ 60 Hz
		800×600 @ 60 Hz
		1024×768 @ 60 Hz
	Detailed mode (descriptor 1):
		Pixel Clock:		199.2MHz
		Horizontal Active:	3840
		Horizontal Blanking:	160
		Vertical Active:		2160
		Vertical Blanking:	62
		Horizontal Sync Offset:	48
		Horizontal Sync Pulse:	32
		Vertical Sync Offset:	54
		Vertical Sync Pulse:	5
		Interlaced:			false
		Is preferred timing:	true
	Detailed mode (descriptor 2):
		Pixel Clock:		103.44MHz
		Horizontal Active:	3840
		Horizontal Blanking:	160
		Vertical Active:		2160
		Vertical Blanking:	62
		Horizontal Sync Offset:	56
		Horizontal Sync Pulse:	144
		Vertical Sync Offset:	54
		Vertical Sync Pulse:	5
		Interlaced:			false
		Is preferred timing:	false
	Maximum image size: 600mm x 340mm
	Gamma: 2.20
	Model: LG Ultra HD
	Checksum: 0xC8 (valid)

	EDID comes from EEPROM
SCREEN 2:
	Framebuffer:	0x43301DE2
	EDID contents:

	Header:		00 ff ff ff ff ff ff 00
	Serial number:	a3 33 00 00
	Version:		01 03
	Basic params	80 3c 22 78 2a
	Chroma info:	ee d5 a3 56 50 9f 26 10 50 54
	Established:	bd 4b 00
	Standard:		d1 c0 81 80 95 0f 95 00 b3 00 81 c0 01 01 01 01
	Descriptor 1:	02 3a 80 18 71 38 2d 40 58 2c 45 00 56 50 21 00 00 1e
	Descriptor 2:	00 00 00 ff 00 55 48 42 31 34 33 38 30 31 33 32 31 39
	Descriptor 3:	00 00 00 fc 00 50 68 69 6c 69 70 73 20 32 37 38 47 34
	Descriptor 4:	00 00 00 fd 00 18 4c 1a 53 17 00 0a 20 20 20 20 20 20
	Extension:		01
	Checksum:		21

	Manufacturer: 410c (Philips 278)
	Model: b9c0
	Serial Number: 13219
	Resolution: 1920x1080
	Made week 38 of 2014
	EDID version: 1.3
	Digital display
	Established Timings:
		720×400 @ 70 Hz
		640×480 @ 60 Hz
		640×480 @ 67 Hz
		640×480 @ 72 Hz
		640×480 @ 75 Hz
		800×600 @ 60 Hz
		800×600 @ 75 Hz
		1024×768 @ 60 Hz
		1024×768 @ 75 Hz
		1280×1024 @ 75 Hz
	Detailed mode (descriptor 1):
		Pixel Clock:		5.7MHz
		Horizontal Active:	1920
		Horizontal Blanking:	280
		Vertical Active:		1080
		Vertical Blanking:	45
		Horizontal Sync Offset:	88
		Horizontal Sync Pulse:	44
		Vertical Sync Offset:	4
		Vertical Sync Pulse:	5
		Interlaced:			false
		Is preferred timing:	true
	Maximum image size: 600mm x 340mm
	Gamma: 2.20
	Model: LS
	Checksum: 0x21 (valid)

	EDID comes from EEPROM

Serial ATA controller:
	Name:				pci8086,a282
	Vendor ID:				86 80 00 00
	Device ID:				82 a2 00 00
	Revision ID:			00 00 00 00
	Subsystem Vendor ID:		58 14 00 00
	Subsystem ID:			05 b0 00 00
	class-code:				01 06 01 00
	IOName:				pci8086,a282
	pcidebug:				0:23:0
	built-in:				00
	compatible:			pci1458,b005pci8086,a282pciclass,010601SATA
	acpi-path:				IOACPIPlane:/_SB/PCI0@0/SATA@170000


NVMe controller:
	Name:				pci144d,a804
	Vendor ID:				4d 14 00 00
	Device ID:				04 a8 00 00
	Revision ID:			00 00 00 00
	Subsystem Vendor ID:		4d 14 00 00
	Subsystem ID:			01 a8 00 00
	class-code:				02 08 01 00
	IOName:				pci144d,a804
	pcidebug:				2:0:0
	built-in:				00
	compatible:			pci144d,a801pci144d,a804pciclass,010802PXSX
	acpi-path:				IOACPIPlane:/_SB/PCI0@0/RP21@1b0004/PXSX@0


MEDIA:
	BSD Name: disk0
	Product Name: Samsung SSD 960 PRO 1TB
	Product Revision Level: 2B6QCXP7
	Medium Type: SSD
	Capacity: 1024.21 GB 1024209543168 bytes
	Physical Interconnect: PCI-Express (NVMe)
	Physical Interconnect Location: Internal
	Temperature: 36°C
	Life: 100%
	Critical Warning: 0%
	Available Spare: 100%
	Available Spare Threshold: 10%
	Unsafe Shutdowns: 786
	S.M.A.R.T. status: Ok
	
	BSD Name: disk1
	Product Name: Samsung SSD 850 PRO 512GB
	Product Revision Level: EXM04B6Q
	Medium Type: SSD
	Capacity: 512.11 GB 512110190592 bytes
	Physical Interconnect: SATA
	Physical Interconnect Location: Internal
	Temperature: 33°C
	Life: 99%
	S.M.A.R.T. status: Ok
	
	BSD Name: disk2
	Product Name: ST4000DM005-2DP166
	Product Revision Level: 0001
	Medium Type: HDD
	Capacity: 4000.79 GB 4000787030016 bytes
	Physical Interconnect: SATA
	Physical Interconnect Location: Internal
	Rotation Rate: 5980rpm
	Temperature: 30°C
	S.M.A.R.T. status: Ok
	
	BSD Name: disk3
	Product Name: ST10000VX0004-1ZE101
	Product Revision Level: AV01
	Medium Type: HDD
	Capacity: 10000.83 GB 10000831348736 bytes
	Physical Interconnect: SATA
	Physical Interconnect Location: Internal
	Rotation Rate: 7200rpm
	Temperature: 36°C
	S.M.A.R.T. status: Ok
	
	BSD Name: disk4
	Product Name: ST10000VX0004-1ZE101
	Product Revision Level: AV01
	Medium Type: HDD
	Capacity: 10000.83 GB 10000831348736 bytes
	Physical Interconnect: SATA
	Physical Interconnect Location: Internal
	Rotation Rate: 7200rpm
	Temperature: 34°C
	S.M.A.R.T. status: Ok
	
	BSD Name: disk5
	Product Name: ST4000DM005-2DP166
	Product Revision Level: 0001
	Medium Type: HDD
	Capacity: 4000.79 GB 4000787030016 bytes
	Physical Interconnect: SATA
	Physical Interconnect Location: Internal
	Rotation Rate: 5980rpm
	Temperature: 31°C
	S.M.A.R.T. status: Ok
	
	
USB 3.0 controller:
	Vendor ID:				86 80 00 00
	Device ID:				af a2 00 00
	Revision ID:			00 00 00 00
	Subsystem Vendor ID:		58 14 00 00
	Subsystem ID:			07 50 00 00
	class-code:				30 03 0c 00
	IOName:				pci8086,a2af
	pcidebug:				0:20:0
	built-in:				00
	compatible:			pci1458,5007pci8086,a2afpciclass,0c0330XHCI
	acpi-path:				IOACPIPlane:/_SB/PCI0@0/XHCI@140000
USB devices:
	Name: USB-PS/2 Optical Mouse
	Vendor: Logitech
	idProduct: c05027
	idVendor: 46d27
	Port Num.: 7
	Bus Power Available: 250
	Speed: 0
	Device Speed: 0
	bcdDevice: 10016
	Serial Number: 0
	non-removable: yes
	
	Name: USB Keyboard
	Vendor:  
	idProduct: 170227
	idVendor: 4d927
	Port Num.: 6
	Bus Power Available: 250
	Speed: 0
	Device Speed: 0
	bcdDevice: 257
	Serial Number: 0
	non-removable: yes
	
	Name: 4-Port USB 2.0 Hub
	Vendor: Generic
	idProduct: 541127
	idVendor: bda27
	Port Num.: 5
	Bus Power Available: 250
	Speed: 2
	Device Speed: 2
	bcdDevice: 291
	Serial Number: 0
	non-removable: yes
	
	Name: 4-Port USB 3.0 Hub
	Vendor: Generic
	idProduct: 41127
	idVendor: bda27
	Port Num.: 15
	Bus Power Available: 450
	Speed: 3
	Device Speed: 3
	bcdDevice: 291
	Serial Number: 0
	non-removable: yes
	
	Name: AppleUSBXHCI Root Hub Simulation
	Vendor: Apple Inc.
	idProduct: 800727
	idVendor: 5ac27
	Speed: 3
	Device Speed: 3
	Serial Number: 0
	non-removable: yes
	
	

LAN controller:
	Name:				ethernet
	Vendor ID:				86 80 00 00
	Device ID:				b8 15 00 00
	Revision ID:			00 00 00 00
	Subsystem Vendor ID:		58 14 00 00
	Subsystem ID:			00 e0 00 00
	class-code:				00 00 02 00
	IOName:				ethernet
	pcidebug:				0:31:6
	built-in:				00
	compatible:			pci1458,e000pci8086,15b8pciclass,020000GBE1
	acpi-path:				IOACPIPlane:/_SB/PCI0@0/GBE1@1f0006

WIFI controller:
	Name:				pci8086,24fd
	Vendor ID:				86 80 00 00
	Device ID:				fd 24 00 00
	Revision ID:			78 00 00 00
	Subsystem Vendor ID:		86 80 00 00
	Subsystem ID:			10 10 00 00
	class-code:				00 80 02 00
	IOName:				pci8086,24fd
	pcidebug:				3:0:0
	built-in:				00
	compatible:			pci8086,1010pci8086,24fdpciclass,028000PXSX
	acpi-path:				IOACPIPlane:/_SB/PCI0@0/RP01@1c0000/PXSX@0


SMC DUMP:

	key: #KEY, size: 04, type: ui32, attr: 00, value: <00000074>
	key: $Num, size: 01, type: ui8 , attr: 00, value: <01>
	key: ACID, size: 08, type: ch8*, attr: 00, value: <babe3c45 c0031043>
	key: ALI0, size: 04, type: {ali, attr: 00, value: <06010200>
	key: ALRV, size: 02, type: ui16, attr: 00, value: <0001>
	key: ALV0, size: 10, type: {alv, attr: 00, value: <010103b7 00a30015 6af4>
	key: CLKH, size: 08, type: {clh, attr: 00, value: <00007080 00011940>
	key: CLKT, size: 04, type: ui32, attr: 00, value: <0000ffb9>
	key: EPCI, size: 04, type: flag, attr: 00, value: <0970f000>
	key: FNum, size: 01, type: ui8 , attr: 00, value: <03>
	key: LSOF, size: 01, type: flag, attr: 00, value: <01>
	key: LSSB, size: 02, type: {lso, attr: 00, value: <0101>
	key: LsNM, size: 01, type: ui8 , attr: 00, value: <01>
	key: LsbV, size: 05, type: {rev, attr: 00, value: <01040a00 06>
	key: MOST, size: 02, type: ui16, attr: 00, value: <8003>
	key: MSDW, size: 01, type: ui8 , attr: 00, value: <01>
	key: MSPS, size: 01, type: {msp, attr: 00, value: <00>
	key: MSSD, size: 01, type: si8 , attr: 00, value: <03>
	key: NATJ, size: 01, type: ui8 , attr: 00, value: <02>
	key: NTOK, size: 01, type: ui8 , attr: 00, value: <01>
	key: NVPR, size: 01, type: ui8 , attr: 00, value: <00>
	key: OSK0, size: 32, type: ch8*, attr: 00, value: <6f757268 61726477 6f726b62 79746865 7365776f 72647367 75617264 6564706c>
	key: OSK1, size: 32, type: ch8*, attr: 00, value: <65617365 646f6e74 73746561 6c286329 4170706c 65436f6d 70757465 72496e63>
	key: REV , size: 06, type: {rev, attr: 00, value: <02410f00 0001>
	key: RMde, size: 01, type: char, attr: 00, value: <41>
	key: RPlt, size: 08, type: ch8*, attr: 00, value: <6a313337 00000000>
	key: RBr , size: 08, type: ch8*, attr: 00, value: <6a313337 00356100>
	key: BEMB, size: 01, type: flag, attr: 00, value: <00>
	key: NATi, size: 02, type: ui16, attr: 00, value: <001e>
	key: TN0P, size: 02, type: sp78, attr: 00, value: <2400>
	key: Th0H, size: 02, type: sp78, attr: 00, value: <3100>
	key: TA0P, size: 02, type: sp78, attr: 00, value: <1a00>
	key: VS0C, size: 02, type: fp2e, attr: 00, value: <7958>
	key: VM0R, size: 02, type: fp2e, attr: 00, value: <828f>
	key: F0Ac, size: 02, type: fpe2, attr: 00, value: <0dec>
	key: F0Tg, size: 01, type: ui8 , attr: 00, value: <d0>
	key: F0St, size: 01, type: ui8 , attr: 00, value: <14>
	key: F0Ss, size: 01, type: ui8 , attr: 00, value: <00>
	key: F0Ft, size: 01, type: ui8 , attr: 00, value: <41>
	key: F0Pt, size: 01, type: ui8 , attr: 00, value: <46>
	key: F0Fo, size: 01, type: ui8 , attr: 00, value: <03>
	key: F0Ct, size: 01, type: ui8 , attr: 00, value: <1c>
	key: F1Ac, size: 02, type: fpe2, attr: 00, value: <0a08>
	key: F1Tg, size: 01, type: ui8 , attr: 00, value: <c0>
	key: F1St, size: 01, type: ui8 , attr: 00, value: <14>
	key: F1Ss, size: 01, type: ui8 , attr: 00, value: <00>
	key: F1Ft, size: 01, type: ui8 , attr: 00, value: <3c>
	key: F1Pt, size: 01, type: ui8 , attr: 00, value: <46>
	key: F1Fo, size: 01, type: ui8 , attr: 00, value: <03>
	key: F1Ct, size: 01, type: ui8 , attr: 00, value: <1c>
	key: F2Tg, size: 01, type: ui8 , attr: 00, value: <e0>
	key: F2St, size: 01, type: ui8 , attr: 00, value: <5a>
	key: F2Ss, size: 01, type: ui8 , attr: 00, value: <59>
	key: F2Ft, size: 01, type: ui8 , attr: 00, value: <64>
	key: F2Pt, size: 01, type: ui8 , attr: 00, value: <b2>
	key: F2Fo, size: 01, type: ui8 , attr: 00, value: <00>
	key: F2Ct, size: 01, type: ui8 , attr: 00, value: <7d>
	key: F2Ac, size: 02, type: fpe2, attr: 00, value: <0864>
	key: F3Tg, size: 01, type: ui8 , attr: 00, value: <02>
	key: F3St, size: 01, type: ui8 , attr: 00, value: <00>
	key: F3Ss, size: 01, type: ui8 , attr: 00, value: <00>
	key: F3Ft, size: 01, type: ui8 , attr: 00, value: <00>
	key: F3Pt, size: 01, type: ui8 , attr: 00, value: <00>
	key: F3Fo, size: 01, type: ui8 , attr: 00, value: <10>
	key: F3Ct, size: 01, type: ui8 , attr: 00, value: <ff>
	key: F4Tg, size: 01, type: ui8 , attr: 00, value: <30>
	key: F4St, size: 01, type: ui8 , attr: 00, value: <97>
	key: F4Ss, size: 01, type: ui8 , attr: 00, value: <40>
	key: F4Ft, size: 01, type: ui8 , attr: 00, value: <00>
	key: F4Pt, size: 01, type: ui8 , attr: 00, value: <00>
	key: F4Fo, size: 01, type: ui8 , attr: 00, value: <2b>
	key: F4Ct, size: 01, type: ui8 , attr: 00, value: <40>
	key: FMCL, size: 01, type: ui8 , attr: 00, value: <77>
	key: FMCR, size: 01, type: ui8 , attr: 00, value: <c7>
	key: TC0D, size: 02, type: sp78, attr: 00, value: <1e00>
	key: FRC0, size: 02, type: freq, attr: 00, value: <0a28>
	key: VC0C, size: 02, type: fp2e, attr: 00, value: <2f0a>
	key: TC1D, size: 02, type: sp78, attr: 00, value: <1d00>
	key: FRC1, size: 02, type: freq, attr: 00, value: <04b0>
	key: TC2D, size: 02, type: sp78, attr: 00, value: <1a00>
	key: FRC2, size: 02, type: freq, attr: 00, value: <04b0>
	key: TC3D, size: 02, type: sp78, attr: 00, value: <1a00>
	key: FRC3, size: 02, type: freq, attr: 00, value: <04b0>
	key: TC4D, size: 02, type: sp78, attr: 00, value: <1b00>
	key: FRC4, size: 02, type: freq, attr: 00, value: <04b0>
	key: TC5D, size: 02, type: sp78, attr: 00, value: <1c00>
	key: FRC5, size: 02, type: freq, attr: 00, value: <04b0>
	key: TC6D, size: 02, type: sp78, attr: 00, value: <1900>
	key: FRC6, size: 02, type: freq, attr: 00, value: <04b0>
	key: TC7D, size: 02, type: sp78, attr: 00, value: <1a00>
	key: FRC7, size: 02, type: freq, attr: 00, value: <04b0>
	key: TC8D, size: 02, type: sp78, attr: 00, value: <1d00>
	key: FRC8, size: 02, type: freq, attr: 00, value: <04b0>
	key: TC9D, size: 02, type: sp78, attr: 00, value: <1c00>
	key: FRC9, size: 02, type: freq, attr: 00, value: <04b0>
	key: TCAD, size: 02, type: sp78, attr: 00, value: <1d00>
	key: FRCA, size: 02, type: freq, attr: 00, value: <0a28>
	key: TCBD, size: 02, type: sp78, attr: 00, value: <1d00>
	key: FRCB, size: 02, type: freq, attr: 00, value: <04b0>
	key: TCCD, size: 02, type: sp78, attr: 00, value: <1a00>
	key: FRCC, size: 02, type: freq, attr: 00, value: <04b0>
	key: TCDD, size: 02, type: sp78, attr: 00, value: <1a00>
	key: FRCD, size: 02, type: freq, attr: 00, value: <04b0>
	key: TCED, size: 02, type: sp78, attr: 00, value: <1b00>
	key: FRCE, size: 02, type: freq, attr: 00, value: <04b0>
	key: TCFD, size: 02, type: sp78, attr: 00, value: <1c00>
	key: FRCF, size: 02, type: freq, attr: 00, value: <04b0>
	key: TCGD, size: 02, type: sp78, attr: 00, value: <1900>
	key: FRCG, size: 02, type: freq, attr: 00, value: <04b0>
	key: TCHD, size: 02, type: sp78, attr: 00, value: <1a00>
	key: FRCH, size: 02, type: freq, attr: 00, value: <04b0>
	key: MPkC, size: 02, type: ui16, attr: 00, value: <7800>
	key: TG0P, size: 02, type: sp78, attr: 00, value: <2900>
	key: QENA, size: 01, type: ui8 , attr: 00, value: <01>
	key: MSTS, size: 01, type: ui8 , attr: 00, value: <0d>
	key: MSPC, size: 01, type: ui8 , attr: 00, value: <0f>
	

 

Share this post


Link to post
Share on other sites
Advertisement
36 minutes ago, vector sigma said:

"Pakage Total" will work if you install VirtualSMC

I at all did not know that these keys are not present in FakeSMC. :)

It is necessary to ask @Slice, to add keys:
CPU Package Core

CPU Package GPU  

CPU Package Total

Share this post


Link to post
Share on other sites

838163886_ScreenShot2018-11-23at6_36_20PM.png.4c6875567f4dd22db3a691fcc3c01f0b.png

Max Temperature and thresholds are not good in this case

I think are influenced in a bad way from my multiplier overclock on bios (put manually at 39 instead of auto)

In auto value I see correct values in that IPG tab

 

Share this post


Link to post
Share on other sites
11 minutes ago, Andrey1970 said:

@vector sigma

That there was no confusion, it is necessary to rename group "IPG info" in "Reference info".

I have another idea: HWMonitorSMC2.app.zip

 

35 minutes ago, fabiosun said:

838163886_ScreenShot2018-11-23at6_36_20PM.png.4c6875567f4dd22db3a691fcc3c01f0b.png

Max Temperature and thresholds are not good in this case

I think are influenced in a bad way from my multiplier overclock on bios (put manually at 39 instead of auto)

In auto value I see correct values in that IPG tab

 

Bro, they are as they are declared by Intel, nothing you can do.

Share this post


Link to post
Share on other sites
6 minutes ago, vector sigma said:

I have another idea: HWMonitorSMC2.app.zip

 

Bro, they are as they are declared by Intel, nothing you can do.

Thank you bro..but here are the specs

https://ark.intel.com/products/126699/Intel-Core-i9-7980XE-Extreme-Edition-Processor-24-75M-Cache-up-to-4-20-GHz-

and I can see it @92° if I do not OC cpu multiplier on bios..so can't say why it happens if those value are only read from app

 

Share this post


Link to post
Share on other sites
29 minutes ago, fabiosun said:

Thank you bro..but here are the specs

https://ark.intel.com/products/126699/Intel-Core-i9-7980XE-Extreme-Edition-Processor-24-75M-Cache-up-to-4-20-GHz-

and I can see it @92° if I do not OC cpu multiplier on bios..so can't say why it happens if those value are only read from app

 

It says 94°, but there is also a clickable question mark where it says "Junction Temperature is the maximum temperature allowed at the processor die." The die have always lower temperature because is a heatsink itself. And if you did not understand, the value reported by the app are taken from IntelPowerGadget.framework (Intel support: https://software.intel.com/en-us/forum) and they are just easy, ready.. with no way to be wrong. Most of them are also reported exactly the same by sysctl, example for frequency:

sysctl hw.cpufrequency

so that you that you go to Apple to report wrong values as well and receive the same answer:hysterical:.

 

Edited by vector sigma
typo

Share this post


Link to post
Share on other sites
19 hours ago, Pavo said:

So for individual core frequencies to show up, it requires FakeSMC + IntelCPUMonitor. Got it thanks. Guess I'll have to be happy with not seeing individual cores freqs then. I am really liking VirtualSMC over FakeSMC.

 

OT, but I have ask. I've been away from here for some time. Why should one use VirtualSMC?

Share this post


Link to post
Share on other sites
21 minutes ago, vector sigma said:

It says 94°, but there is also a clickable question mark where it says "Junction Temperature is the maximum temperature allowed at the processor die." The die have always lower temperature because is a heatsink itself. And if you did not understand, the value reported by the app are taken from IntelPowerGadget.framework (Intel support: https://software.intel.com/en-us/forum) and they are just easy, ready.. with no way to be wrong. Most of them are also reported exactly the same by sysctl, example for frequency:


sysctl hw.cpufrequency

so that you that you go to Apple to report wrong values as well and receive the same answer:hysterical:.

;)

 

Screen Shot 2018-11-23 at 8.02.08 PM.png

Share this post


Link to post
Share on other sites
13 minutes ago, Amble said:

 

OT, but I have ask. I've been away from here for some time. Why should one use VirtualSMC?

Honestly, I think it's a better way of implementing the SMC for hacks. It also gives me a better GB score than FakeSMC, not a huge bigger core but about 1000 more.

Share this post


Link to post
Share on other sites
24 minutes ago, vector sigma said:

@fabiosun, 始終是來自IntelPowerGadget.framework的數據,您決定發布的任何照片。:)

funny..but I am here to understand and now I know why app say 92° and in other situation 110° in IPG tab

Maybe you are understanding in other ways my way to debug or help..so I stop here :)

to be clear is not an app problem..but  more deepest

 

 

 

Edited by fabiosun

Share this post


Link to post
Share on other sites
2 minutes ago, fabiosun said:

is not an app problem..but  more deepest

Agreed, but not my fault. there were two hours to explain that these values are under the control of IntelPowerGadget.framework

 

5 minutes ago, fabiosun said:

funny

Yep, tried with chinese, last resource to capture your attention :D...but no offenses :wink_anim:

Share this post


Link to post
Share on other sites
4 hours ago, fabiosun said:

Funny.. but I am here to understand, now I know why the application says 92°, in other cases the IPG tag is 110°

Maybe you are understanding my debugging or help in other ways. So I stopped here.

To be clear is not an application problem.. but deeper

 

 

This app just gets the data from "IntelPowerGadget" and renders if you think it is wrong. That is also a problem with the data provided by "IntelPowerGadget". You can find INTEL's development feedback questions.

In fact, the work done by sigma is controlled by the sensor provided by slice, sigma breaks through the original thinking, adding "Intel" to get more and more accurate data, this is a great improvement. We should respect the labor of sigma!

Edited by Allan
Translated

Share this post


Link to post
Share on other sites
11 minutes ago, vector sigma said:

 the second doesn't have the vertical grid.

Thanks, now I see a difference. :)

But I do not see a difference between "Dashed Horizontally" and "No Grid".

Share this post


Link to post
Share on other sites
18 minutes ago, jinbingmao said:

这个程序只是从“ IntelPowerGadget“获取数据并呈现,如果你认为是错的。那也是” IntelPowerGadget“提供的数据有问题。你可以找INTEL的开发反馈问题。

事实上,sigma所做的工作,受制与 slice提供的传感器驱动,sigma突破原来的思维,加入“Intel”获取更多而更准确的数据,这是一个伟大的进步。我们应该尊重sigma的劳动!

sorry but where I was unrespectable of vector sigma job?

I am trying to understand different value exposed in my system from vector sigma app (IPG do not expose those value) and now I know it is a gigabyte bios "features"

So I do not understand your thought completely ;)

 

to help other people with x299 gigabyte Designare ex:

Latest bios for this motherboard produce different value for Tj injunction and others value which we can check with @vector sigma app in OSX

Latest bios adds compatibly for new Intel cpu like 99xx series but introduce this "features"

 

Share this post


Link to post
Share on other sites
2018/11/24 PM12点00分,e14883362说:

嗨,大家好。

 

蓝宝石脉冲RX 560 4GOC(45W)无法看到风扇速度(0rpm)和百分比(0%)。但是图形风扇实际上正在旋转(机箱打开),大约1200 rpm -1400 rpm。待机也在旋转,好像没有官方的自动启停功能。如果在非待机状态下温度达到55-60摄氏度,您将看到风扇速度和百分比。当温度降至30-35时,数据将返回其先前的状态(风扇仍在旋转)。怎样才能解决这个问题?

 

哦,顺便说一下,你偶尔可以看到待机模式下的速度(没有百分比)。

 

另一个问题是,在唤醒后,您无法看到CPU和机箱中的风扇的速度。睡觉前是正常的,例如840转。但是当它醒来时,它变为0转。但是,风扇并没有停止。它仍在旋转,但没有数据。

hehe

Edited by jinbingmao

Share this post


Link to post
Share on other sites

I thank Sigma for her great work. At present, only slice's "ITE" motherboard sensor is used, and there is a lack of "South Bridge" sensor. I hope Sigma can help me recover the missing "key" and view the running power of the CPU easily.

1.png

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

Announcements

  • Similar Content

    • By miliuco
      Install macOS 10.15 Catalina on Gigabyte P55-USB3 with Radeon RX 580 graphics card using a USB device created with the createinstallmedia command and Clover as bootloader. Instructions to install macOS 10.14 Mojave on this computer are almost identical, replacing Catalina app with Mojave, so this article is suitable for both versions of macOS. The Gigabyte P55-USB3 motherboard (and some others from the same brand with the P55 / H55 chipset) have made it easy to build a hackintosh and install macOS since 10 years ago. Although it is an old motherboard, the behavior with Mojave or Catalina is very good after changing the classic hard drive (HDD) for a solid state drive (SSD).

      Components of the hackintosh
      Gigabyte GA-P55-USB3 motherboard: P55 chipset, 1156 socket, ALC892 audio, Gigabit RTL8111D network, DDR3 RAM Intel Core i5-750 processor for socket 1156: 4 cores, 8MB cache, clock rate 2.66 GHz Fenvi FV-T919 wireless + Bluetooth card: PCI-Express, wifi is ac type, detected by macOS as Airport and Apple Bluetooth Radeon RX 580 8 GB graphics card: works OOB but with a few details to be considered, it has its own article.  
      Previous requirements
      Install macOS Catalina app in /Applications folder USB flash drive with at least 16GB prepared from Disk Utility with MBR partition scheme and formatted as Mac Os Plus (on older Gigabyte boards like mine, USB sticks partitioned with GUID scheme instead of MBR usually hang the system when booting) Recent version of Clover (I have used r5117) Recent versions of Lilu (at least 1.4.4) and WhateverGreen (at least 1.3.9) to fine-tune the behavior of the graphics card Recent version of RealtekRTL8111 (I have used 2.2.2) FaceSMC version 6.26-322 (newer versions disable automatic mounting of USB devices on my system).  
      Create install USB
      Run this command from Terminal (assuming the target device is called USB):
      Bash: sudo /Applications/Install\ macOS\ Catalina.app/Contents/Resources/createinstallmedia --volume /Volumes/USB /Applications/Install\ macOS\ Catalina.app
      Clover must be installed on the USB memory, I choose the following options:
      Bootloader > Install boot0af on the MBR CloverEFi > CloverEFI 64-bit SATA BIOS Drivers, 64 bit > Recommended drivers > FSInject + SMCHelper + XhciDxe BIOS Drivers, 64 bit > File System drivers > ApfsDriverLoader Install RC scripts on selected volume Optional RC scripts > Disable sleep proxy client.  
      You have to copy 4 kexts to the EFI/CLOVER/kexts/Other folder of the USB device: FaceSMC 6.26-322, Lilu 1.4.4, WhateverGreen 1.3.9 and RealtekRTL8111 2.2.2. Regarding the config.plist file, the most significant is:
      Boot > kext-dev-mode = 1 in Boot arguments GUI > Theme embedded, EmbeddedThemeType Dark, Screen Resolution 1920x1080, Preboot in Hide Volume Graphics > blank, nothing is checked except if foxbox solution is used to have more than 2 connectors enabled RT Variables > 0x28 in BooterConfig and 0x67 in CsrActiveConfig SMBios > iMac14,2 Sytem Parameters> Yes in Inject Kexts and check Inject System ID.  
      Install macOS Catalina

      Boot from the USB device and choose Install macOS from Install macOS Catalina. The installation program runs until the PC restarts. Here choose Install macOS from HDD (the name of the volume you are installing macOS on). With RX 580 graphics card, the screen goes black in this second phase of the installation, it is a phase in which the user has nothing to do until the PC is restarted so you can let it work until the Clover menu again. You have to choose Boot macOS from HDDto boot the installed system from the hard disk, the screen is recovered and you can configure the account and the initial options. From this moment the screen works fine.

      In summary:
      Boot from USB > Clover menu > Install macOS from Install macOS Catalina > screen works fine Boot from USB > Clover menu > Install macOS from HDD > black screen Boot from USB > Clover menu > Boot macOS from HDD > screen works fine.  
      Install Clover and kexts on the hard drive

      Clover needs to be installed on the disk where we just installed macOS. Options are the same as when installing it on the USB memory. You also have to copy the 4 kexts (FaceSMC 6.26-322, Lilu 1.4.4, WhateverGreen 1.3.9 and RealtekRTL8111 2.2.2) into the EFI/CLOVER/kexts/Other folder on the EFI partition of the disk. And review the config.plist file remembering the comments for the USB.

      If everything goes well, the computer starts from the hard disk with a running copy of macOS Catalina.
       
       

    • By Slice
      The thread splitted from HWSensors3.
       
      Tools to testing Radeon state.
      Load RadeonPCI.kext  
      RadeonPCI.kext.zip
       
      How to load
      sudo chown -R root:wheel ~/Downloads/RadeonPCI.kext sudo chmod -R 755 ~/Downloads/RadeonPCI.kext sudo kextutil -v ~/Downloads/RadeonPCI.kext and use RadeonDump utility
      RadeonDump1.zip
       
      Commands to see temperature
      Polaris
      ./RadeonDump1 -n 6b0,c0300014
      SeaIsaland
      ./RadeonDump1 -n 200,c0300014
       
      Old families
      ./RadeonDump1 -r 714,7f4
       
      Other possible methods to find a register for temperature
      ./RadeonDump1 -n 6b0,c0300e0c
      ./RadeonDump1 -n 6b0,1c5
      ./RadeonDump -n 6b0,d8200ca4
      ./RadeonDump -r 59800,59810
      ./RadeonDump -r 678,680

       
       
       
      01.12.2017
      Latest solution RadeonMonitor.kext here
      works for RX 460,480,580
      not works for HD7790, R9 290X?
       
      06.12.2017
      Here works also with HD7790, R9 290X
       
      14.12.2017
      Support VEGA here
       
      13.12.2017
      Version for test modern cards
      RadeonPCI5.kext.zip
       
      06.04.2020
      Version for Catalina
      RadeonPCI5-v2.kext.zip
    • By kevin_1351
      tl;dr: VirtualSMC causes me a flood of log messages and correlated cpu spikes. FakeSMC doesn't.
       
      Hi, I have almost finalized my Huawei Matebook X Pro Opencore setup and everything is working very well besides wifi/bt ofc (which is about to change).
       
      However, I noticed how the cpu usage sometimes went up a little and when looking at the Console I could see a never-ending flood of:
      default 14:05:05.983292+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:05.982975+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:05.982996+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:06.985932+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:06.985949+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:06.986134+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:39.426574+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:39.426729+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:39.426585+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:41.431085+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:41.431097+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:41.431246+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:42.433068+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:42.433227+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:42.433078+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:43.434453+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:43.434465+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:43.434622+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:44.436155+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:44.436166+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0  
      As you can see, multiple of these per second. Another guy with the same computer is also having this issue and posted a dsdt change to fix it. This fix didn't solve anything though
      He tried to limit the Notify call by implementing a state change requirement before calling Notify.
       
      Here is the original acpi:
      Scope (_SB) { Device (LID) { Name (_HID, EisaId ("PNP0C0D") /* Lid Device */) // _HID: Hardware ID Method (_LID, 0, NotSerialized) // _LID: Lid Status { Local0 = One Local0 = ^^PCI0.LPCB.EC0.RPIN (0x05, 0x06) If ((Local0 == 0x55)) { Local0 = Zero } Else { Local0 = One } ^^PCI0.GFX0.CLID = Local0 Return (Local0) } } Device (PWRB) { Name (_HID, EisaId ("PNP0C0C") /* Power Button Device */) // _HID: Hardware ID Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0B) } } } Scope (_SB.PCI0.LPCB.EC0) { Method (_Q81, 0, NotSerialized) // _Qxx: EC Query, xx=0x00-0xFF { Local0 = ^^^^LID._LID () If ((Local0 == Zero)) { ADBG ("LID-OFF") SGOV (0x02030009, Zero) SGOV (0x02060000, Zero) } Else { ADBG ("LID-ON") SGOV (0x02030009, One) SGOV (0x02060000, One) Notify (ALSD, 0x80) // Status Change } Notify (LID, 0x80) // Status Change } } Which he changed to: 
      Scope (_SB) { Device (LID) { Name (_OLD, One) // assuming everything else.. the lid should start open? Name (_HID, EisaId ("PNP0C0D") /* Lid Device */) // _HID: Hardware ID Method (_LID, 0, NotSerialized) // _LID: Lid Status { Local0 = One Local0 = ^^PCI0.LPCB.EC0.RPIN (0x05, 0x06) If ((Local0 == 0x55)) { Local0 = Zero } Else { Local0 = One } Return (Local0) } } Device (PNLF) { Name (_HID, EisaId ("APP0002")) // _HID: Hardware ID Name (_CID, "backlight") // _CID: Compatible ID Name (_UID, 0x0A) // _UID: Unique ID Name (_STA, 0x0B) // _STA: Status } Device (PWRB) { Name (_HID, EisaId ("PNP0C0C") /* Power Button Device */) // _HID: Hardware ID Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0B) } } } Scope (_SB.PCI0.LPCB.EC0) { Method (_Q81, 0, NotSerialized) // _Qxx: EC Query, xx=0x00-0xFF { Local0 = ^^^^LID._LID () If ((Local0 == Zero)) { ADBG ("LID-OFF") SGOV (0x02030009, Zero) SGOV (0x02060000, Zero) } Else { ADBG ("LID-ON") SGOV (0x02030009, One) SGOV (0x02060000, One) Notify (ALSD, 0x80) // Status Change } If ((^^^^LID._OLD != Local0)) { Notify (LID, 0x80) // Status Change ^^^^LID._OLD = Local0 } } } Besides me not seeing any reason to declare _OLD in LID. The idea itself shouldn't be too bad right? Well, as I said, his fix didn't work.
       
      In fact, to prove that Method _Q81 doesn't have anything to do with the issue at all, I created a Clover/Opencore patch to change _Q81 to XQ81. This resulted in my lid not working at all of course, but the log flooding still persisted!
      So _Q81 doesn't have anything to do with the issue afaik.
       
      Now, further Google searches led me to a chinese post where he tied the issue to VirtualSMC. And indeed, by migrating to FakeSMC the issue is no more.
       
      Unfortunately, I'm very fond of VirtualSMC for various reasons. So I would very much like to keep it. If not I'd have to implement the old way of doing Battery monitoring etcetc. Which isn't very elegant and update proof as it requires DSDT patching.
       
      So, I do believe that the issue may very well be in the DSDT code, perhaps in the ambient light part. I'm not very skilled at this and just started studying the ACPI spec 3 days ago.
       
      Could someone please help me out? Thanks a lot in advance
       
       
      origin.zip
      OC.zip
    • By Slice
      Guys,
      Don't mix 6.18 and 3.41.
       
      There are three different projects for monitoring temperatures, voltages, fans speed and other hardware parameters:
      Initially it was FakeSMC with plugins for producing SMC keys for hardware parameters for different hardware. But sometimes ago Kozlek separated own version of FakeSMC and producing new set of plugins while I stay with good working version 3. So..
      1. FakeSMC v3 with Hardware Sensors3  which I still supported.
      2. FakeSMC v6 (rev1800) by Kozlek and supported by Rehabman. AFAIK both are abandoned and the project is not supported. Or may be maintained by coauthors.
      3. New VirtualSMC by vit9696 with own set of sensors kexts. It depends on Lilu.kext. The project is in active development.
      All three project have incompatible interfaces sensors<->SMC so they are incompatible with each other.
       
      There are applications for monitoring hardware parameters and they commonly depends on these projects.
      1. iStat, iStatMenu, iStatPro compatible with real Macs because they use SMC keys just like those presents in real Macs.
      2. HWMonitorSMC by Navi (initial codes from Kozlek)  used in my HWSensors3.
      3. HWMonitor by Kozlek with graphics like in IntelPowerGadget used in his HWSensors version.
      4. HWMonitorSMC2 by Vector_Sigma tends to be universal supporting all project. It also may use sensors information produces by Apple graphics and by IntelPowerGadget.
       
      Let us discuss here differences and common ideas for this projects.
       
×