WhyNotWin11 icon indicating copy to clipboard operation
WhyNotWin11 copied to clipboard

Improve ARM Processor CPU Speed Detection

Open I-Rinka opened this issue 4 years ago • 16 comments

This software is good but it only works on x86 processors. Even though it can run on WOA because of the compatibility layer, it can't provide comprehensive information. The WOA ecosystem is growing, so native ARM64 version may be needed.

image

The supported Qualcomm processors are shown below.

https://docs.microsoft.com/en-us/windows-hardware/design/minimum/supported/windows-11-supported-qualcomm-processors

I-Rinka avatar Jun 27 '21 00:06 I-Rinka

I don't think that native is possible, because autoit does not support support arm.

micwoj92 avatar Jun 27 '21 00:06 micwoj92

I won't be able to make a native ARM64 version, but I can implement improvements for proper detection on Supported Qualcomm Processors. I'm assuming this is in regards to the Architecture check. Odd that it wasn't able to mark the CPU as Compatible as it's in the Qualcomm list. Finally, can you send me a copy of Save All Information from dxdiag?

rcmaehl avatar Jun 27 '21 00:06 rcmaehl

Sure : ) But my Windows is in Chinese. Hoping it would not trouble you.

DxDiag.txt

I won't be able to make a native ARM64 version, but I can implement improvements for proper detection on Supported Qualcomm Processors. I'm assuming this is in regards to the Architecture check. Odd that it wasn't able to mark the CPU as Compatible as it's in the Qualcomm list. Finally, can you send me a copy of Save All Information from dxdiag?

I-Rinka avatar Jun 27 '21 00:06 I-Rinka

Driver Model: 2.6 WDDM

DXDIAG WHYYYYY. Will fix this in an upcoming build to pass WDDM check

rcmaehl avatar Jun 27 '21 00:06 rcmaehl

@I-Rinka Could you test latest stable release, are there any improvements?

micwoj92 avatar Jul 01 '21 11:07 micwoj92

image The left one is x64 version and the right is x86 version. Only CPU frequency has problem.

I-Rinka avatar Jul 01 '21 11:07 I-Rinka

So a regression then :/

micwoj92 avatar Jul 01 '21 11:07 micwoj92

image The left one is x64 version and the right is x86 version. Only CPU frequency has problem.

This is probably the same issue that intel chips have where it reports current speed as max speed instead of max possible speed.

rcmaehl avatar Jul 25 '21 04:07 rcmaehl

@rcmaehl is the cpu speed exact same issue as with intel x86_64 cpus? if yes then this issue should be closed, because the applications works/detects same on arm and on x86_64

micwoj92 avatar Aug 24 '21 14:08 micwoj92

@I-Rinka can you try the latest build:

https://nightly.link/rcmaehl/WhyNotWin11/workflows/wnw11/main/WNW11.zip

rcmaehl avatar Sep 27 '21 20:09 rcmaehl

image

It works.

I-Rinka avatar Sep 29 '21 10:09 I-Rinka

Oh, the CPU Frequency is still not a correct value when I look close to it. It just turns green.

I-Rinka avatar Sep 29 '21 10:09 I-Rinka

Should be fixed in the latest build.

https://nightly.link/rcmaehl/WhyNotWin11/workflows/wnw11/main/WNW11.zip

rcmaehl avatar Sep 29 '21 12:09 rcmaehl

image

Basically it's right. But.. I don't know, probably the emulated processor has a slightly lower frequency.

I-Rinka avatar Sep 29 '21 13:09 I-Rinka

Not sure how to improve this unfortunately, just glad it's properly passing now.

rcmaehl avatar Sep 29 '21 17:09 rcmaehl

the CPU Speed detects on registry only and it may inaccurate

WilloIzCitron avatar Mar 18 '22 14:03 WilloIzCitron