-
Notifications
You must be signed in to change notification settings - Fork 280
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
Effect on Acer Aspire S3-371 #4
Comments
Your reports of ME on for OEM BIOS are very strange. 1.
I had problems with me_cleaner only once after applying the modification, after a complete power cycle (power off and power on, not just reboot) everything worked perfectly (including the NIC). 2.
I am going to upgrade this tool with an additional cleaning step, we can try again and see if the MEI disappears |
(to keep #3 clean I removed your post there) |
body p { margin-bottom: 0cm; margin-top: 0pt; }
In reality, such NIC behavior remains
even after I successfully flashed coreboot on by x220, of course,
with me neutralized.
在 2016年12月01日 00:09, Nicola Corna 写道:
Your reports of ME on for OEM BIOS are very strange.
1.
From hardenedlinux: what do you mean with
The NIC doesn’t work after a cold boot (it cannot even be
recognized as an NIC), but does after a warm boot. (It may be
possible to add some code to Coreboot to work around this, but
it has not yet been done.)
I had problems with me_cleaner only once after applying the
modification, after a complete power cycle (power off and power
on, not just reboot) everything worked perfectly (including the
NIC).
The Acer's PCH is HM77. Unlike QM67, it is designed for IvB
originally, which I believe is the main difference.
在 2016年12月01日 00:09, Nicola Corna 写道:
2.
I have no idea about this Acer: maybe the i3 line behaves
differently, but it indeed appears that ME is broken on this
device
Intel ME reset due to exception
I am going to upgrade this tool with an additional cleaning
step, we can try again and see if the MEI disappears
|
Seems working on:
MEI device has NOT disappeared on this platform, but seems to have been neutralized according to intelmetool's output.
superiotool.txt
lspci.txt
dmidecode.txt
intelmetool_deme.txt
The text was updated successfully, but these errors were encountered: