Forum - RE: Intel Management Engine: Drivers, Firmware & System Tools

Win-Raid Forum (Drivers - Firmware - Modding) � Special Topics � Intel Management Engine � Intel (Converged Security) Management Engine: Drivers, Firmware and Tools

Page 349 of 380 � Page 1 ... 344 345 346 347 348 349 350 351 352 353 ... 380 Page �

Topic settings

Print view

Jump to forum

General & Forum related Topics News / Announcements Forum-related Questions & Suggestions Off Topic Important Drivers (AHCI/RAID, NVMe, USB etc.) General: Storage Drivers (AHCI/RAID, NVMe and USB) Specific: Intel AHCI/RAID Drivers Specific: NVIDIA nForce Chipset Drivers (incl. AHCI/RAID) Specific: NVMe Drivers Other Drivers System Performance RAID Performance AHCI/NVMe Performance Solid State Drives BIOS Modding BIOS Modding Guides and Problems BIOS modules (PCI ROM, EFI and others) BIOS Modding Requests Reports: BIOS Modding Results Offers: Already modded special BIOSes Special Topics Intel Management Engine CPU Microcodes NVMe Support for old Systems Other Tools (not BIOS modding related) Interesting PC Hardware & Software OS related Topics Windows 11 Windows 8-10/Server 2012-2019 Windows 7/Vista/Server 2008 Windows XP/2000/Server 2003 DOS/Windows 3.X/9X/ME - Retro Gaming Other Operating Systems

#5221 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Fri Nov 13, 2020 2:28 pm (Last edited: Fri Nov 13, 2020 2:33 pm)

Intel CSME 15.0 Consumer PCH-LP B Firmware v15.0.10.1414

Intel CSME 15.0 Corporate PCH-LP B Firmware v15.0.10.1414

Intel PMC TGP PCH-LP C (B) Firmware v150.1.20.1026

Zitat von wasisdn im Beitrag #5219
What about the new MEI version 2041.15.0.1893 on Station Driver?
Including new MEI driver with the strange number 2036.100.0.1024

Intel seems to be changing their mind on MEI drivers every month at this point. I don't know what that is. I know that "CSE" (GSC) 100 is for Dedicated Xe Graphics. Why is Intel using 100 for CSE is a good question. I see references to CSME 16 (Alderlake), CSME 17.30 (???) and CSME 18.30 (???) in those drivers. Maybe early test drivers for upcoming platforms. Maybe a change in driver versioning. Who knows outside of Intel & OEMs. For now, I will keep the current drivers and will revise if more of these 100 appear in the future.

reply

#5222 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Sat Nov 14, 2020 12:03 am

@ plutomaniac: Remember that one?

Zitat von lfb6 im Beitrag #5201
....ME 14, dump from this thread, machine bricked after just reading? bios chips
After reading BIOS chips, Dell Latitude 3510 won't start.....

We got a ME region from a working identical machine, i simply exchanged the complete ME- region, not yet tested if this unbricks the machine.

Funny thing:
Bios with good ME gives exact same errors when trying to open in FIT 4.0.36.1158 as the bios with corrupt MFS
Bios with good ME opened in FIT 4.0.11.1205 gives same configuration as the bios with corrupt MFS. Compared the saved xml- files and it's just the paths for the file locations that are different. (I know there was a slight chance, but one should anyway not trust this configuration read from a corrupt region)

MEA reads now of course region as configured, no error.

I wonder why the Intel tools don't complain about the corrupt MFS partition? MEA seems to be a quite sensible tool, I wasn't aware of that MEA reads/ checks the subpartitions of the ME region so thoroughly!

reply

#5223 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Sat Nov 14, 2020 12:29 am

If a dump was used, MEA should report "Initialized", not "Configured". The image was built with 4.0.11 so it should be opened with the old tools. The FW is newer due to FWUpdate tool usage, as I said above. I would need to see those two SPI "dumps" together to check how & why FIT behaves like that. MEA is a beast, I'm proud of it. And yes, it goes into crazy amount of detail without the user noticing. You can see some of that detail by trying to unpack the firmware using "-unp86" parameter.

reply

#5224 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Sat Nov 14, 2020 5:24 am (Last edited: Sat Nov 14, 2020 6:04 am)

Hi! I'm getting this error: Error 639: Loader failed to verify manifest signature of PPHY. Thanks in advance!

reply

#5225 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Sat Nov 14, 2020 11:23 am

My bad, I used "Configured" in the meaning of "Initialized", sorry for having been imprecise.

And yes, the output of MEA with this option is quite amazing Not less impressing the unpacked content! Thanks a lot for all this work!!

I'll attach the complete images and the ME regions, not sure if just ME region was enough. Tried to open xml- configuration file generated with 4.0.11 with newer FIT version, but gives same error as opening the bios file? Would've expected that a later version at least could read an existing config...

(System isn't booting/ still completely dead with copied good ME-region, so I assume it was not corrupted MFS/ is not at all the UEFI firmware)

lfb6 has attached files to this post

reply

#5226 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Sat Nov 14, 2020 3:28 pm

Zitat von Leoplate25 im Beitrag #5224
Hi! I'm getting this error: Error 639: Loader failed to verify manifest signature of PPHY. Thanks in advance!

Please give me more info. What exact system do you have? What firmware are you trying to update? What tool did you use? What did you choose from the OP? I cannot guess these things.

@lfb6

Oh... Upon comparing the two images (good & bad), this is clearly a MEA oversight. It turns out that the MFS is not corrupted at all. Removing the check for "unrecognized MFS" completes the analysis properly and shows Initialized at the state. I know how to fix it, very simple. TLDR, the MFS has 3 types of Pages: System, Data & Scratch. Only 1 Scratch/Temporary page exists and it's normally filled with padding and placed at the end. But in this case, the Scratch page was being in use when the dump was made and it had data (what looked like "corruption" to me before) and was also placed at the top of the MFS. Since MEA checks the top of the MFS for "unrecognized" structure, it would skip it incorrectly. Nice find! I'll consider this an indirect MEA bug report. Thank you very much lfb6 for bringing this to my attention. I'll push an update to MEA later today which addresses that oversight.

reply

#5227 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Sat Nov 14, 2020 6:15 pm (Last edited: Sat Nov 14, 2020 7:16 pm)

Zitat von plutomaniac im Beitrag #5226
[quote=Leoplate25|p128787]Hi! I'm getting this error: Error 639: Loader failed to verify manifest signature of PPHY. Thanks in advance!
Please give me more info. What exact system do you have? What firmware are you trying to update? What tool did you use? What did you choose from the OP? I cannot guess these things.

Sorry. I'm new with these and i followed your instructions. I have an i5-10600K on an Asus Z490 Tuf Gaming Plus, 2x8gb 2933MHz Predator, H100i RGB Pro XT, m.2 Kingston A2000 250GB, Samsung EVO 860 1TB, Zotac RTX 2060 Super Mini. I'm trying to update the ME Firmware (i have version 14.0.45.1389). The driver version is dated on May 19th (version 2021.14.0.1615). I used the tools you provided in this post. I got to the end but i'm having another error. It started reading the file but it says is corrupted or something like that.
From ASUS i updated the ME firmware, but you have a later one. How do i know i have the latest ME driver installed? How to install it?
I tried to update the CPU microcode, but i can't make it work, the new python method is giving me a headache. I'm concerned about the new platypus vulnerability and the others vulnerabilities too. Thanks!

EDIT:

C:\Intel CSME System Tools v14.0.20+ r10\FWUpdate\WIN64>FWUpdLcl64.exe -f FWUpdate.bin
Intel (R) Firmware Update Utility Version: 14.0.45.1389
Copyright (C) 2005 - 2020, Intel Corporation. All rights reserved.

Checking firmware parameters...

Warning: Do not exit the process or power off the machine before the firmware update process ends.
Sending the update image to FW for verification: [ COMPLETE ]

FW Update: [ 0% (/)] Do not Interrupt

Error 639: Loader failed to verify manifest signature of PPHY.

Same thing if i do it with WIN32 and FWUpdLcl.exe

What should i put on BIOS binary file? If i don't put anything i can't build the image.
I'm also getting this: "Warning: OEM Signing is Disabled".

reply

#5228 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Sat Nov 14, 2020 7:35 pm

Alright, follow the discussion between Ataemonus and me from a few days ago. This is either an ASUS issue or something specific to FWUpdate v14.0.45 tool and/or CSME firmware 14.0.46. I don't have a solution for that. We'll have to wait for a newer FWUpdate or firmware version or reports from other systems as well.

reply

#5229 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Sat Nov 14, 2020 7:50 pm (Last edited: Sat Nov 14, 2020 8:05 pm)

ASUS launched this the day before yesterday:

Version 14.0.45.1389V2.1
2020/11/12 5.34 MBytes
MEUpdateTool
Intel has identified security issue that could potentially place impacted platform at risk.
Use ME Update tool to update your ME.
*We suggest you update ME Driver to the latest Version 14.0.45.1389V2.1 simultaneously.
Please download the file and check the MD5 code first.
MD5: 010ebfd94977a4aea551fc79a9b892e2

I updated it, but it says: 14.0.45.1389 (but the v2.1 doesn't appear on the description). And they say that i should update the driver to the same version, but my driver version is: 2021.14.0.1615 (dated May). Where can i find the latest ME driver? Am i ok with this firmware posted by ASUS? Should i wait for a BIOS update with a new microcode? Because in my laptop i updated the cpu microcode via Windows Update and all done. Thanks again.

What should i put on BIOS binary file? If i don't put anything i can't build the image.

reply

#5230 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Sat Nov 14, 2020 11:19 pm

Zitat von plutomaniac im Beitrag #5226
...... Nice find! I'll consider this an indirect MEA bug report. .......

I wonder actually who might be able to give you direct MEA bug rapports, that's probably not a really large number of people.....

Thanks a lot for the explanation, and for looking into these files!

reply

#5231 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Sun Nov 15, 2020 9:30 pm (Last edited: Sun Nov 15, 2020 9:32 pm)

Zitat von lfb6 im Beitrag #5230
that's probably not a really large number of people.....

That's true unfortunately. I don't think I've ever received an actual report for a logical code bug report. I can probably count the amount of people, who I know and could do that, in one hand.

Anyway, thank you a lot for your help lfb6, especially at the various Engine-related topics which I can't keep up with anymore.

reply

#5232 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Sun Nov 15, 2020 11:34 pm

Zitat von plutomaniac im Beitrag #5228
Alright, follow the discussion between Ataemonus and me from a few days ago. This is either an ASUS issue or something specific to FWUpdate v14.0.45 tool and/or CSME firmware 14.0.46. I don't have a solution for that. We'll have to wait for a newer FWUpdate or firmware version or reports from other systems as well.

ASUS launched this the day before yesterday:

Version 14.0.45.1389V2.1
2020/11/12 5.34 MBytes
MEUpdateTool
Intel has identified security issue that could potentially place impacted platform at risk.
Use ME Update tool to update your ME.
*We suggest you update ME Driver to the latest Version 14.0.45.1389V2.1 simultaneously.
Please download the file and check the MD5 code first.
MD5: 010ebfd94977a4aea551fc79a9b892e2

I updated it, but it says: 14.0.45.1389 (but the v2.1 doesn't appear on the description). And they say that i should update the driver to the same version, but my driver version is: 2021.14.0.1615 (dated May). Where can i find the latest ME driver? Am i ok with this firmware posted by ASUS?
I updated the CPU microcode too via CMD, but HWInfo shows version B0 and BIOS and Windows registry shows C8.
I updated the me firmware on my laptop with your steps. I think is an ASUS problem/issue.

Could you help me? Thanks?

reply

#5233 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Mon Nov 16, 2020 1:12 am (Last edited: Mon Nov 16, 2020 1:12 am)

Zitat von Leoplate25 im Beitrag #5232
Where can i find the latest ME driver?

Uhhmmm, in this thread you're posting?

Zitat von Leoplate25 im Beitrag #5232
Am i ok with this firmware posted by ASUS?

Yes, leave is at it is.

Zitat von Leoplate25 im Beitrag #5232
I updated the CPU microcode too via CMD, but HWInfo shows version B0 and BIOS and Windows registry shows C8.

Off-Topic.

reply

#5234 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Mon Nov 16, 2020 12:31 pm

You're very welcome. I think ME is a quite interesting area, but I have only very basic knowledge, and even less for newer versions, since I'm personaly still work with SNB/ IVB/ HSW systems. Thank a lot for these very detailed and understandable guides- they make it possible to get some people going again

reply

#5235 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Mon Nov 16, 2020 6:53 pm (Last edited: Mon Nov 16, 2020 6:54 pm)

Intel CSME 12.0 Corporate PCH-LP C Firmware v12.0.71.1681

Note: Update ME Analyzer to v1.174.1 or newer due to a hotfix at the main Engine firmware detection.

Zitat von lfb6 im Beitrag #5234
since I'm personaly still work with SNB/ IVB/ HSW systems.

Ahh, I know that pain as a "proud" owner of a SNB i7-2760QM and an IVB i5-3570K.

reply

Repair MEI on Samsung NP550P7C-S04PL � � Strange ME Region size mismatch after reconfiguring and rebuilding

Page 349 of 380 � Page 1 ... 344 345 346 347 348 349 350 351 352 353 ... 380 Page �

Please enter a reason for warning.