Jump to content

2,079 posts in this topic

Recommended Posts

Advertisement
18 minutes ago, Rodion2010 said:

YES! This version works OK

Sensors were ok and correctly read, only wasn't added to any group.

 

@Andrey1970, I've just tried VirtualSMC and CPU plugin but honestly I wasn't satisfied about power keys, so I made a modification as to me seem to be correct. Try and let me know.

 

 

HWMonitorSMC2.app_2.4.1.zip

Edited by vector sigma

Share this post


Link to post
Share on other sites

The first one with FakeSMC.kext + IntelCPUMonitor.kext + ACPIMonitor.kext, the second with VirtualSMC.kext + SMCProcessor.kext. Actually you have a lot of more sensors with FakeSMC..

 

Guys, I don't think to make any other modification. Looks good to you now?

Edited by vector sigma
typo

Share this post


Link to post
Share on other sites
1 hour ago, vector sigma said:

The first one with FakeSMC.kext + IntelCPUMonitor.kext + ACPIMonitor.kext, the second with VirtualSMC.kext + SMCProcessor.kext. Actually you have a lot of more sensors with FakeSMC..

 

Guys, I don't think to make any other modification. Looks good to you now?

“VBAT”=?"cpu VID"=? "pch"=?

Edited by jinbingmao

Share this post


Link to post
Share on other sites
13 hours ago, vector sigma said:

Sensors were ok and correctly read, only wasn't added to any group.

 

@Andrey1970, I've just tried VirtualSMC and CPU plugin but honestly I wasn't satisfied about power keys, so I made a modification as to me seem to be correct. Try and let me know.

 

 

HWMonitorSMC2.app_2.4.1.zip

 

Earlier I wrote that keys power, show the underestimated indications, but you to me did not check and referred to the different moments of reading. :)

Now everything is correct. :thumbsup_anim:

 

Look where this Russian translation of this word was lost.

1282218728_2018-11-0615_02_49.png.14c009ee25f7af090c82561ccfde8f4c.png

I think there is which character it is not visible.
I entered a new line "Purgeable" = "Очищаемая"; again and having deleted an old line "Purgeable" = "Очищаемая"; and the translation appeared.

959169363_2018-11-0615_28_57.png.ed35af546e35d04526397980f0079112.png

Localizable.strings.zip

Share this post


Link to post
Share on other sites
5 hours ago, Andrey1970 said:

 

Earlier I wrote that keys power, show the underestimated indications, but you to me did not check and referred to the different moments of reading.

I've installed VirtualSMC so I see something wrong. Probably I was stated that you can never see the same exact thing in IntelPowerGadget.app and HWMonitorSMC due to the different start polling time interval (as I explained to someone pages back HWMonitorSMC start from 100 milliseconds instead of 50 in IPG.app), but without a try I wasn't able to see that.

5 hours ago, Andrey1970 said:

I think there is which character it is not visible.
I entered a new line "Purgeable" = "Очищаемая"; again and having deleted an old line "Purgeable" = "Очищаемая"; and the translation appeared.

Don't know why, but this already happened multiple times, probably some hidden characters.

5 hours ago, Andrey1970 said:

Now everything is correct. :thumbsup_anim:

Good, the new app engine is a total refactoring made in swift instead of objective-c and c, and that has causing a new debugging also due to my lack of hardwares to test with, but you guys helped a lot ;).

Share this post


Link to post
Share on other sites
17 hours ago, jinbingmao said:

“VBAT”=?"cpu VID"=? "pch"=?

VBAT is the cmos battery voltage? Really I don't know how to read it but IMHO who cares? a spare CR2032 will solve all problems, however it will work for years.. 

cpu VID: Is determined by Intel, but you should see the "voltage" currently in use if you have the correct kext plugin for FakeSMC or VirtualSMC. For the pch I need your SMC dump and see if you have these keys ready.

Share this post


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

@vector sigma

It is necessary to separate a gap value and dimensionality.
For example: now 1200MHz, but 1200 MHz are necessary.

Already tried in past and looks bad, at least not for everything.

Edited by vector sigma

Share this post


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

Already tried in past and looks bad, at least not for everything.

 

Bad looks or not bad looks, so it is impossible to argue.
Believe me, I am an engineer and I know as correctly.
The gap is not necessary only for °C and %.

Edited by Andrey1970

Share this post


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

I am an engineer and I know as correctly.
 

Me as well, but what you proposed cause the top bar to contain less sensors due to additional spaces and a bad look. More for doing that we should introduce more useless calculations to ensure that 2400MHz will become 2400 MHz but 1% will remain 1% and not 1 % depending on what will be shown in the top bar or in the popover. More some existing functions that autocalculate MB and GB from bytes using Apple API already shown the correct unit.... but without spaces and I don't know how to fix as the source code is closed. 

If you want that for Russian why you didn't insert a space in the Localizable.strings  that you give me that is enough? (but if will not work in any places due to Apple API please don't claim at me).

Last night (or the day before) I'll notice that you use translated unit of measurement, but if my name is "Alessandro Volta" for us non Russian guys is a bit strange since to see our names to not be our name any more (never saw in any book here).... but we leave in peace with every one else ways of doing things.:wink_anim:

So, do you want a space also before %? EDIT ok no space for % and °C.

Edited by vector sigma

Share this post


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

Me as well, but what you proposed cause the top bar to contain less sensors due to additional spaces and a bad look. More for doing that we should introduce more useless calculations to ensure that 2400MHz will become 2400 MHz but 1% will remain 1% and not 1 % depending on what will be shown in the top bar or in the popover. More some existing functions that autocalculate MB and GB from bytes using Apple API already shown the correct unit.... but without spaces and I don't know how to fix as the source code is closed. 

If you want that for Russian why you didn't insert a space in the Localizable.strings  that you give me that is enough? (but if will not work in any places due to Apple API please don't claim at me).

Last night (or the day before) I'll notice that you use translated unit of measurement, but if my name is "Alessandro Volta" for us non Russian guys is a bit strange since to see our names to not be our name any more (never saw in any book here).... but we leave in peace with every one else ways of doing things.:wink_anim:

So, do you want a space also before %?

 

Now I understood that the reason in a top bar. Then let remains as is.

"Алессандро Вольта" - it not the translation into Russian, it is so written with the Russian alphabet, we speak in Russian "Alessandro Volta". :)

Share this post


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

"Алессандро Вольта" - it not the translation into Russian, it is so written with the Russian alphabet, we speak in Russian "Alessandro Volta". :)

For me is fine, wanted to say that in Europe the units will remain as is no matter the nationality, and was just curious how "Volta" that has medieval origins can be translated literally when the true meaning is really something else :D.

So 'л' is 'l' 'c' is 's'. Easy now I can talk Russian :D

8 minutes ago, Andrey1970 said:

Now I understood that the reason in a top bar. Then let remains as is.

I've already done that:

 

"+12V Bus Voltage" = "Напряжение +12 В";

"+5V Bus Voltage" = "Напряжение +5 В";

"-12V Bus Voltage" = "Напряжение -12 В";

"-5V Bus Voltage" = "Напряжение -5 В";

"3.3 VCC Voltage" = "Напряжение 3.3 В VCC";

"3.3 VSB Voltage" = "Напряжение 3.3 В VSB";

"3.3 AVCC Voltage" = "Напряжение 3.3 В AVCC";

// Units of measurement

"GHz" = " GHz"; // Giga Hertz

"MHz" = " МГц"; // Mega Hertz

"MB"  = " МБ";  // Mega byte

"GB"  = " GB";  // Giga byte

"°C"  = "°C";  // Celsius

"W"   = " Вт";  // Watt

"mWh" = " mWh"; // milli Watt per hour

"J"   = " J";   // Joule

"V"   = " В";   // Volt

"mV"  = " мВ";  // milli Volt

"mA"  = " мА";  // milli Ampere

"rpm" = " об/мин"; // revolutions per minute

 

should I leave it as is or not?

Share this post


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

should I leave it as is or not?

No, I looked at the top bar, it looks bad.

Correct please

"GHz" = "ГГц"

"GB"  = "ГБ"

"mWh" = "мВт⋅ч"

"J"  = "Дж"

Edited by Andrey1970

Share this post


Link to post
Share on other sites

imageproxy.php?img=&key=c17464ef1b1b51c7QQ20181107-082834@2x.thumb.png.627eca57ca0f4bd87becdcfe766ab8d6.png

6 hours ago, vector sigma said:

VBAT is the cmos battery voltage? Really I don't know how to read it but IMHO who cares? a spare CR2032 will solve all problems, however it will work for years.. 

cpu VID: Is determined by Intel, but you should see the "voltage" currently in use if you have the correct kext plugin for FakeSMC or VirtualSMC. For the pch I need your SMC dump and see if you have these keys ready.

SMC DUMP:

	key: #KEY, size: 04, type: ui32, attr: 00, value: <0000005d>
	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: <00005a60>
	key: EPCI, size: 04, type: flag, attr: 00, value: <07b0f000>
	key: FNum, size: 01, type: ui8 , attr: 00, value: <02>
	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: <02300f00 0002>
	key: RMde, size: 01, type: char, attr: 00, value: <41>
	key: RPlt, size: 08, type: ch8*, attr: 00, value: <74390000 00000000>
	key: RBr , size: 08, type: ch8*, attr: 00, value: <7439006a 31370000>
	key: BEMB, size: 01, type: flag, attr: 00, value: <01>
	key: NATi, size: 02, type: ui16, attr: 00, value: <001e>
	key: TC0D, size: 02, type: sp78, attr: 00, value: <2000>
	key: FRC0, size: 02, type: freq, attr: 00, value: <06a4>
	key: VC0C, size: 02, type: fp2e, attr: 00, value: <3687>
	key: TC1D, size: 02, type: sp78, attr: 00, value: <1600>
	key: FRC1, size: 02, type: freq, attr: 00, value: <06a4>
	key: TC2D, size: 02, type: sp78, attr: 00, value: <1700>
	key: FRC2, size: 02, type: freq, attr: 00, value: <06a4>
	key: TC3D, size: 02, type: sp78, attr: 00, value: <1a00>
	key: FRC3, size: 02, type: freq, attr: 00, value: <06a4>
	key: MPkC, size: 02, type: ui16, attr: 00, value: <aa00>
	key: TN0P, size: 02, type: sp78, attr: 00, value: <1600>
	key: Th0H, size: 02, type: sp78, attr: 00, value: <1b00>
	key: TA0P, size: 02, type: sp78, attr: 00, value: <1300>
	key: Vp3C, size: 02, type: fp2e, attr: 00, value: <d883>
	key: VP0R, size: 02, type: sp4b, attr: 00, value: <61eb>
	key: Vp1C, size: 02, type: sp4b, attr: 00, value: <290a>
	key: VS0C, size: 02, type: fp2e, attr: 00, value: <7333>
	key: VM0R, size: 02, type: fp2e, attr: 00, value: <5f3b>
	key: Vp4C, size: 02, type: fp2e, attr: 00, value: <d70a>
	key: VBAT, size: 02, type: fp2e, attr: 00, value: <c937>
	key: F0Ac, size: 02, type: fpe2, attr: 00, value: <0fbc>
	key: F0ID, size: 16, type: {fds, attr: 00, value: <00010000 43505520 e9a38ee6 89870000>
	key: F0Tg, size: 01, type: ui8 , attr: 00, value: <82>
	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: F1Tg, size: 01, type: ui8 , attr: 00, value: <80>
	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: <32>
	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: F1Ac, size: 02, type: fpe2, attr: 00, value: <0554>
	key: F1ID, size: 16, type: {fds, attr: 00, value: <00010035 e590b8e6 b094e9a3 8ee68987>
	key: F2Tg, size: 01, type: ui8 , attr: 00, value: <80>
	key: F2St, size: 01, type: ui8 , attr: 00, value: <14>
	key: F2Ss, size: 01, type: ui8 , attr: 00, value: <00>
	key: F2Ft, size: 01, type: ui8 , attr: 00, value: <32>
	key: F2Pt, size: 01, type: ui8 , attr: 00, value: <46>
	key: F2Fo, size: 01, type: ui8 , attr: 00, value: <03>
	key: F2Ct, size: 01, type: ui8 , attr: 00, value: <1c>
	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: <ff>
	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: <00>
	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: <eb>
	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: TG0D, size: 02, type: sp78, attr: 00, value: <1d00>
	key: QENA, size: 01, type: ui8 , attr: 00, value: <01>
	key: HE0N, size: 01, type: ui8 , attr: 00, value: <10>

 

QQ20181107-081725@2x.png

QQ截图20181107080342.jpg

 

 

"Pxh" is there, I'm sorry!!

Edited by jinbingmao

Share this post


Link to post
Share on other sites
20 hours ago, jinbingmao said:

imageproxy.php?img=&key=c17464ef1b1b51c7QQ20181107-082834@2x.thumb.png.627eca57ca0f4bd87becdcfe766ab8d6.png


SMC DUMP:

	key: #KEY, size: 04, type: ui32, attr: 00, value: <0000005d>
	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: <00005a60>
	key: EPCI, size: 04, type: flag, attr: 00, value: <07b0f000>
	key: FNum, size: 01, type: ui8 , attr: 00, value: <02>
	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: <02300f00 0002>
	key: RMde, size: 01, type: char, attr: 00, value: <41>
	key: RPlt, size: 08, type: ch8*, attr: 00, value: <74390000 00000000>
	key: RBr , size: 08, type: ch8*, attr: 00, value: <7439006a 31370000>
	key: BEMB, size: 01, type: flag, attr: 00, value: <01>
	key: NATi, size: 02, type: ui16, attr: 00, value: <001e>
	key: TC0D, size: 02, type: sp78, attr: 00, value: <2000>
	key: FRC0, size: 02, type: freq, attr: 00, value: <06a4>
	key: VC0C, size: 02, type: fp2e, attr: 00, value: <3687>
	key: TC1D, size: 02, type: sp78, attr: 00, value: <1600>
	key: FRC1, size: 02, type: freq, attr: 00, value: <06a4>
	key: TC2D, size: 02, type: sp78, attr: 00, value: <1700>
	key: FRC2, size: 02, type: freq, attr: 00, value: <06a4>
	key: TC3D, size: 02, type: sp78, attr: 00, value: <1a00>
	key: FRC3, size: 02, type: freq, attr: 00, value: <06a4>
	key: MPkC, size: 02, type: ui16, attr: 00, value: <aa00>
	key: TN0P, size: 02, type: sp78, attr: 00, value: <1600>
	key: Th0H, size: 02, type: sp78, attr: 00, value: <1b00>
	key: TA0P, size: 02, type: sp78, attr: 00, value: <1300>
	key: Vp3C, size: 02, type: fp2e, attr: 00, value: <d883>
	key: VP0R, size: 02, type: sp4b, attr: 00, value: <61eb>
	key: Vp1C, size: 02, type: sp4b, attr: 00, value: <290a>
	key: VS0C, size: 02, type: fp2e, attr: 00, value: <7333>
	key: VM0R, size: 02, type: fp2e, attr: 00, value: <5f3b>
	key: Vp4C, size: 02, type: fp2e, attr: 00, value: <d70a>
	key: VBAT, size: 02, type: fp2e, attr: 00, value: <c937>
	key: F0Ac, size: 02, type: fpe2, attr: 00, value: <0fbc>
	key: F0ID, size: 16, type: {fds, attr: 00, value: <00010000 43505520 e9a38ee6 89870000>
	key: F0Tg, size: 01, type: ui8 , attr: 00, value: <82>
	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: F1Tg, size: 01, type: ui8 , attr: 00, value: <80>
	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: <32>
	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: F1Ac, size: 02, type: fpe2, attr: 00, value: <0554>
	key: F1ID, size: 16, type: {fds, attr: 00, value: <00010035 e590b8e6 b094e9a3 8ee68987>
	key: F2Tg, size: 01, type: ui8 , attr: 00, value: <80>
	key: F2St, size: 01, type: ui8 , attr: 00, value: <14>
	key: F2Ss, size: 01, type: ui8 , attr: 00, value: <00>
	key: F2Ft, size: 01, type: ui8 , attr: 00, value: <32>
	key: F2Pt, size: 01, type: ui8 , attr: 00, value: <46>
	key: F2Fo, size: 01, type: ui8 , attr: 00, value: <03>
	key: F2Ct, size: 01, type: ui8 , attr: 00, value: <1c>
	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: <ff>
	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: <00>
	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: <eb>
	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: TG0D, size: 02, type: sp78, attr: 00, value: <1d00>
	key: QENA, size: 01, type: ui8 , attr: 00, value: <01>
	key: HE0N, size: 01, type: ui8 , attr: 00, value: <10>

 

QQ20181107-081725@2x.png

QQ截图20181107080342.jpg

 

 

"Pxh" is there, I'm sorry!!

Hi, I did not yet investigate your SMC dump, but is the above picture coming from Aida in Windows as I suspect? If yes I'm very sorry that Hackintoshes produces tiny informations about your hardware, but the fact is that if we need something almost always we have to write a driver from scratch. Example for VBAT:

 

PC = CMOS battery (value ready to be read)

Mac = PRAM battery (published by SMC?? I don't think)

Hackintosh = CMOS battery ?? pity, how to read?

 

The same for GPU Power and voltages. in Windows is ready to be read, but in macOS need a driver to be written by someone. Geforce & ATI plugins should show something when the hardware is known, but that should be a job for Slice as I haven't knowledge in this area.

You enlight the "-5 volts bus voltage", what is wrong? The "wording" looks more correct than in Aida to me since is a differential voltage that should let you understand if there is a short to ground or else.

Basically on a hackintosh everithing must be written. Later or tomorrow I'll study your dump to see if there is something usefull to be added to the app.

Edited by vector sigma
typos

Share this post


Link to post
Share on other sites
2 hours ago, vector sigma said:

Hi, I did not yet investigate your SMC dump, but is the above picture coming from Aida in Windows as I suspect? If yes I'm very sorry that Hackintoshes produces tiny informations about your hardware,but the fact is that if we need something almost always we have to write a driver from scratch. Example for VBAT:

 

PC = CMOS battery (value ready to be read)

Mac = PRAM battery (published by SMC?? I don't think)

Hackintosh = CMOS battery ?? pity, how to read?

 

The same for GPU Power and voltages. in Windows is ready to be read, but in macOS need a driver to be written by someone. Geforce & ATI plugins should show something when the hardware is known, but that should be a job for Slice as I haven't knowledge in this area.

You enlight the "-5 volts bus voltage", what is wrong? The "wording" looks more correct than in Aida to me since is a differential voltage that should let you understand if there is a short to ground or else.

Basically on a hackintosh everithing must be written. Later or tomorrow I'll study your dump to see if there is something usefull to be added to the app.

You said all right! I see. Thanks for your help!

Share this post


Link to post
Share on other sites

The second graphic card (Thunderbolt-3 Vega FE) shows the wrong information - same as on the main graphic card (Vega RX 64). 0rpm on the RX Vega 64 - correct.

 

screenshot.png.0ef080418e7153bc332a7a0a8ad4a9b8.png

Share this post


Link to post
Share on other sites
1 hour ago, losinka said:

The second graphic card (Thunderbolt-3 Vega FE) shows the wrong information - same as on the main graphic card (Vega RX 64). 0rpm on the RX Vega 64 - correct.

 

screenshot.png.0ef080418e7153bc332a7a0a8ad4a9b8.png

Please, post a ioreg

Share this post


Link to post
Share on other sites
On 11/8/2018 at 8:08 PM, losinka said:

attached. Thank you!

2xGPU.ioreg.zip

Hi. Please create a directory in to your Desktop called HWGraphics, this will enable the dump of graphics cards info using the IO. Use the attached app, the dump will occour once at the application start up. Post here the entire directory.

 

@jinbingmao (and anyone intrested), I've added back some sensors reading, please tell me if you notice them (cpu proximity/Heatsink/North Bridge temperature, VBAT voltage (i.e. Battery under "Motherboards"), GPUs proximity temperature, GPU memory frequency. ... (require these keys to be existing). Corrected some typos.

HWMonitorSMC2.app_debug_IO_1.zip

Share this post


Link to post
Share on other sites
1 hour ago, vector sigma said:

你好。请在桌面中创建名为HWGraphics的目录,这将使用IO启用图形卡信息的转储。使用附加的应用程序,转储将在应用程序启动时出现一次。在这里发布整个目录。

 

@jinbingmao  (以及任何有兴趣的人),我添加了一些传感器读数,请告诉我你是否注意到它们(cpu proximity / Heatsink / North Bridge温度,VBAT电压(即“主板”下的电池),GPU接近温度,GPU记忆频率......(要求这些密钥存在)。纠正了一些拼写错误。

HWMonitorSMC2.app_debug_IO_1.zip

 

1.png

2.png

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • 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.
       
×