Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

i7z works incorrectly if UEFI Secure Boot enabled #25

Open
okudayukiko opened this issue Dec 28, 2019 · 6 comments
Open

i7z works incorrectly if UEFI Secure Boot enabled #25

okudayukiko opened this issue Dec 28, 2019 · 6 comments

Comments

@okudayukiko
Copy link

okudayukiko commented Dec 28, 2019

My PC:HP notebook,Core i5-1035G1 CPU.
Ubuntu 19.10/Debian 10.0(UEFI Secure Boot enabled):Execute "sudo i7z",it prompt:
WAIT ...
True Frequency (without accounting Turbo) 1190 MHz
wrmsr:pwrite:Operation not permitted
Quitting i7z

Linux(UEFI Secure Boot disabled):i7z works correctly.

@okudayukiko okudayukiko changed the title i7z doesn't support Intel Ice Lake processor? Bug? Dec 28, 2019
@okudayukiko okudayukiko changed the title Bug? Bug report Dec 29, 2019
@okudayukiko okudayukiko changed the title Bug report Works incorrectly if UEFI Secure Boot enabled Jan 2, 2020
@okudayukiko okudayukiko changed the title Works incorrectly if UEFI Secure Boot enabled i7z works incorrectly if UEFI Secure Boot enabled Jan 2, 2020
@afifahtaat
Copy link

Hi,
do you solve this?

@KastB
Copy link

KastB commented Jul 6, 2021

Did you try the custom msr-module?
https://github.com/intel/intel-cmt-cat/wiki/UEFI-Secure-Boot-Compatibility

@mecjuszfufecjusz
Copy link

Is there no other way around it, e.g. patching something minor in the i7z code? Why do you have to write to read CPU frequency, actually?

@KastB
Copy link

KastB commented Jan 4, 2022

Probably there is nothing easier than this:
https://github.com/KastB/msr_no_lockdown

@BoredDebugger
Copy link

BoredDebugger commented Feb 7, 2023

Is there no other way around it, e.g. patching something minor in the i7z code?
Why do you have to write to read CPU frequency, actually?

It configures the performance counters, writing to IA32_PERF_GLOBAL_CTRL and IA32_FIXED_CTR_CTL - the former is probably a no-op but the latter is needed. I haven't quite figured out how it gets the values as the code is a bit convoluted to say the least but it definitely doesn't work if it can't write to IA32_FIXED_CTR_CTL

The code is all a bit of a mess anyway, no CPU newer than about 2015 is correctly detected and I suspect coverage before that is not 100%, it doesn't understand CPUs with more than 6 cores for reporting max turbo boost multipliers, there's loads of dead code just left but commented out. Needs a thorough clean up.

@fatemeh-mohseni-AI
Copy link

fatemeh-mohseni-AI commented Jan 31, 2024

I have faced the problem when I disabled vmd on my Asus laptop.
it was working fine while vmd was active
(I've changed vmd status in Bios)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants