Closed StanislavNikolov closed 6 years ago
Output after adding print(val, pack('Q', val))
above line 45:
stjo@swanky undervolt $ sudo ./undervolt.py -r
temperature target: -0 (100C)
9223374304597508096 b'\x00\x00\x00\x00\x10\x02\x00\x80'
Traceback (most recent call last):
File "./undervolt.py", line 286, in <module>
main()
File "./undervolt.py", line 281, in main
voltage = read_offset(plane)
File "./undervolt.py", line 171, in read_offset
write_msr(value_to_write)
File "./undervolt.py", line 46, in write_msr
os.write(f, pack('Q', val))
OSError: [Errno 5] Input/output error
See https://github.com/georgewhewell/undervolt#troubleshooting
Have you checked secure boot? I guess we can probably detect this and tell the user
I am facing the same issue on Thinkpad T430 with i7-3610qm. Secure boot and the security chip are turned off in the BIOS. is there any workaround?
I only just saw @StanislavNikolov is using Atom CPU- I think these are pretty different from Core series, probably don't have the same FIVR. I will update compatibility table to show these CPUs are not supported.
@v-marinkov Hm, it looks like your config should be working. Can you post distro and kernel version? I have a T520 I can test at the weekend. Does dmesg | grep -i lockdown
show anything?
https://github.com/mihic/linux-intel-undervolt says only
Intel CPUs with an integrated voltage controller (FIVR)
are supported and FIVR was introduced in Haswell cpus (4th gen). Could this be the reason we get these errors on our Bay Trail and Ivy Bridge?
dmesg | grep -i lockdown
shows nothing regardless of sudo.
Kernel is 4.15.0-38-generic
Pop!_OS 18.04 LTS
Ah, I think you are right- the earliest CPU this is confirmed to work on is i5-4xxx which is indeed Haswell. Thanks for report- you can make PR to add i7-3610 as unsupported if you want
@georgewhewell
I am facing literally the same issue, I have a Lenevo thinkpad X250, running intel i5-5300u.
on doing dmesg | grep -i lockdown
i get the following result regardless of sudo.
dmesg | grep -i lockdown
[ 0.000000] Kernel is locked down from EFI secure boot; see man kernel_lockdown.7
[ 1.268717] Lockdown: Hibernation is restricted; see man kernel_lockdown.7
[ 4.391632] Lockdown: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7
[ 18.609578] Lockdown: ioperm is restricted; see man kernel_lockdown.7
[ 6799.454517] Lockdown: Direct MSR access is restricted; see man kernel_lockdown.7
Here some (hopefully) useful info: uname
/proc/cpuinfo
I'm using a toshiba chromebook 2 (2014 edition, codename swanky), model CB35-B{4 numbers that I don't think anyone cares about}.