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 74 of 380 � Page 1 ... 69 70 71 72 73 74 75 76 77 78 ... 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

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

Thu Apr 09, 2015 10:58 pm (Last edited: Thu Apr 09, 2015 11:21 pm)

Zitat von lordkag im Beitrag #1101
Maybe plat_n_sku and bup_sku?

I searched for the string SKU as well but it's different from the previous SKU formats. I'm not sure.

bup_sku = BringUp SKU

Mmm, where the sku strings are: I think each section starts after

So:

00 00 00 00 80 01 01 00 00 00 03 --> plat_n_sku
00 00 00 00 00 44 43 00 00 C0 13 01 00 00 00 03 --> bup_sku

I don't know. Maybe plat_n_sku. I'll check the length of the previous SKUs.

EDIT 1 : 04 00 00 00 C0 BA 11 F1 13 22 00 00 --> ME10 (size [4] etc)

EDIT 2 : Nah, the image is wrong. Doesn't make sense.

EDIT 3 : Platform_SKU may be the FITC Emulation SKU (the drop-down list at the top) - just a guess

reply

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

Fri Apr 10, 2015 9:09 pm (Last edited: Tue Apr 14, 2015 1:37 am)

@Pacman @lordkag

I was wrong. The ME11 firmware is not ROM-Bypass, not Pre-Production but actually Production.

It seems that in the new ME firmware structure all partitions are accounted for at the Flash Partition Table ($FPT) header. However, those that are missing do not have a pointer or size. Also, the empty/missing partitions are signified by the 00 00 00 FF flag at the end. I don't know why this flag is not set for the last empty partition though which is 00. Here:

To be certain, I manually extracted & cut all partitions from the ME11 firmware to detect any remaining parts. Of course the resulting file is 315KB (0x4EE00) and consists of the $FPT header (0x190) and FF padding (0x4EC70). There is no ROMB inside and nothing else for that matter. The partitions that include data/code are FTPR, NFTP = FTUP & MFS. The partitions PSVN, IVBP, FLOG & UTOK exist but are empty (FF padding). The partitions DLMP, ROMB & ISHC are missing from the image (no pointers & size). All the files are attached below for anyone interested.

Also, the $MN2 manifest headers have the Production-Signed flag of 00 00 00 00 so the image can be neither Pre-Production nor ROM-Bypass (00 00 00 80 flags respectively) as I originally claimed.

ME Analyzer is now able to detect empty/missing ROMB partitions but it's not released yet because I cannot figure out where the SKU is mentioned. I apologize for any misinformation given earlier. The structure is new so I wasn't expecting that change.

Since the ME11 firmware we have is Production, it can be added to this thread as well.

Updates:

NEW! ME 11.0 Consumer Firmware v11.0.0.1120

Source: Station-Drivers

Warning: This firmware's targeted platform is Skylake. Since Skylake is not even released yet, it's provided here for research purposes.

Note: ME Analyzer has not been publicly updated to properly detect ME11 firmware yet. Any errors & notes reported are normal.

plutomaniac has attached files to this post

ME11_Partitions.rar

reply

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

Fri Apr 10, 2015 9:36 pm

So there can be empty partitions and also present, filled with padding? I thought that this was a signed that the base for pointer is not the FPT header, but something else. I trust your judgement and analysis, though. This probably happens with all those images that I thought are using other base for pointer calculation.

One suggestion: the flag is not a byte [0x80], but a single bit = 0x80 - 0b10000000. So to test this and also be future-proof for any new property added to that byte, test with "if test_prod & 0x80 : is PRE/ROMB", where test_prod is that byte containing the flag.

reply

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

Fri Apr 10, 2015 11:03 pm (Last edited: Fri Apr 10, 2015 11:07 pm)

Zitat von lordkag im Beitrag #1104
So there can be empty partitions and also present, filled with padding? I thought that this was a signed that the base for pointer is not the FPT header, but something else. I trust your judgement and analysis, though. This probably happens with all those images that I thought are using other base for pointer calculation.

We already had partitions that are present but filled with padding. A quick way to check that is to use Igor's me_unpack tool for ME2-ME10.0 firmware. ME11 does not work due the different structure so I had to do it manually.

But I haven't seen a missing (but mentioned at $FPT) partition before. The logical conclusion is that. Truth is, until we have a ME11 firmware that we know for sure that it's Production, I may be wrong. But I don't think so, the $MN2 flag at the header (which seems to be the only thing that hasn't changed) also hopefully proves my point.

According to Igor's notes/presentations, the ME firmware has a lot of jumps to code that is not available at the SPI image. Those jumps go to the bootrom, kernel or whatever is stored at the actual ME co-processor. To save space, the rest of the code is stored at the SPI flash image. The whole purpose of ROM-Bypass though is to keep all code (including the one inside the ME co-processor) at the SPI image due to early/buggy silicon. That way they can bypass any faulty hardware and test needed changes with ROMB firmware. So in theory ROMB does not have any jumps? I don't know. When you mentioned "base for pointer calculation" those "jumps" came to mind but I highly doubt it has anything to do with what were are looking into right now ($FPT, $MN2 headers). Those jumps must be elsewhere and I don't have the knowledge/experience to track them down. Thankfully we have Igor for that.

Zitat von lordkag im Beitrag #1104
One suggestion: the flag is not a byte [0x80], but a single bit = 0x80 - 0b10000000. So to test this and also be future-proof for any new property added to that byte, test with "if test_prod & 0x80 : is PRE/ROMB", where test_prod is that byte containing the flag.

You lost me here. I assume you are talking about ME Analyzer and how it detects the PRD/PRE/BYP flag? We know that the flag consists of 4 hex bytes. The last one in which we are interested in (0x00 or 0x80) is a byte which when converted to 8 bits in binary we get 0b10000000 (or 10000000b). I assume you meant 0x80 = 0b10000000 and not subtraction (-). Still, how is that a bit?

The command you wrote, is it a different "if" format? My python knowledge is kind of crappy.

Keep in mind that the release flag is not the same for all $MN2 headers around the firmware. You may find at one $MN2 header a flag of 04 00 00 40, 00 00 00 C0 or something like that. However, the rule of thumb is that if you find a flag 00 00 00 00 the image is Production-signed whereas if you find 00 00 00 80 it's Pre-Production or ROM-Bypass. This applies to whole firmware images no matter how many different $MN2 regions exist.

reply

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

Fri Apr 10, 2015 11:32 pm (Last edited: Fri Apr 10, 2015 11:34 pm)

Then all those 4 bytes are used for image attributes, but only the last one is for production type. Yes, it should have been 0x80 = 0b10000000. But the thing is, only the first bit from the left or MSB is important for release type. So, when you test, you test that bit alone and ignore the full byte. Using bitwise operators you can target that bit alone. For MSB you use "ord(byte) & 0x80", which results in 0x80 if MSB is 1, or 0 if MSB is 0.

0x40 & 0x80 = 0, 0xC0 & 0x80 = 0x80. It is still a regular "if ..." statement, but any value different than 0 is considered true, while 0 is false.

reply

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

Fri Apr 10, 2015 11:46 pm (Last edited: Tue Apr 14, 2015 2:46 am)

Oh you were talking about the Most Significant Bit, alright. Got it now. So that way it shouldn't matter what $MN2 header ME Analyzer scans. Currently, it has to take that into consideration. Whether it's C0 or whatever it'll detect that it's not Production. Basically Production is 0 and PRE/ROMB are 1 when looking at the MSB. I'll see if I can add that to ME Analyzer. Thanks for the suggestion.

reply

#1102 | . datum

Sat Apr 11, 2015 6:40 am (Last edited: Mon Dec 23, 2019 2:31 am)

reply

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

Sat Apr 11, 2015 10:17 am

Zitat von Oubadah im Beitrag #1108
Is the 10.0.30.1054 drivers only one just a way to avoid bloatware?

Yes. Only the Intel MEI driver is required, not the additional software.

Zitat
Where did you get that smaller 10.0.30.1054 installer?

Pure drivers don't have and don't need an installer. You can install all drivers directly from within the Device Manager (by doing a right-click onto the related device and choosing the option "Update Driver Software...").

My current System:
MB: ASRock X570 Pro4, CPU: AMD Ryzen 5 3600, System Drive: 500 GB Samsung 980 Pro, Graphics: Sapphire Radeon RX570, OS: Win10 x64 Pro
Donation Link:
If you are satisfied with my Forum activities, you can send a donation to my personal PayPal account by clicking onto >this< link.

reply

#1104 | . datum

Sat Apr 11, 2015 11:06 am (Last edited: Mon Dec 23, 2019 2:31 am)

reply

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

Sat Apr 11, 2015 11:41 am

Zitat von Oubadah im Beitrag #1110
I'm talking about the 10.0.30.1054 download in the OP that says 'drivers only'. It's still an installer just like the other one (MEISetup.exe), but it's much smaller (~20MB vs ~70MB for the full 10.0.39.1003 installer).
Where did the 20MB installer come from?

Since the OP has been created by plutomaniac, only he knows the answer, but I suspect, that this is the original installer of the complete Intel MEI Drivers & Software Set v10.0.39.1003. The size difference is obviously caused by the removal of the other MEI Software components.
If you want to get the pure Intel MEI drivers v10.0.30.1054 without using any installer, please use the attached package.

Fernando has attached files to this post

Intel MEI Drivers v10.0.30.1054 WHQL.rar

reply

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

Sat Apr 11, 2015 3:00 pm

Regarding the installer: Oubadah is right. The installer is not a modded version of the full driver. At the 5MB kits there is a folder called MEI-Only Installer. It contains usually only one small file that directly installs the MEI & SOL drivers.

Regarding which driver to install: Fernando is right. For your Z97 system (1.5MB ME firmware) only the installer is really needed.

reply

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

Sat Apr 11, 2015 4:37 pm

Zitat von plutomaniac im Beitrag #1112
Regarding which driver to install: Fernando is right. For your Z97 system (1.5MB ME firmware) only the installer is really needed.

Small correction: Really needed is only the driver and not any installer.
By the way: Both Intel ME architectures (1.5M and 5M) are using the same Intel MEI Driver, but different Intel ME Software..

reply

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

Sat Apr 11, 2015 9:27 pm (Last edited: Sat Apr 11, 2015 9:29 pm)

Updates:

Re-Upload: Intel MEI Driver v10.0.30.1054 MEI-Only Installer (repacked to reduce size from 9.24MB / 45% --> 6.39MB / 31%)
Added: Intel MEI Driver v10.0.30.1054 INF for manual installation
Added: Intel MEI Driver v9.5.24.1790 INF for manual installation
Added: Intel MEI Driver v9.0.0.1287 (8.1.40.1416) INF for manual installation
Added: Notice regarding KMDF 1.11 driver under Windows 7 (section A)
Redesigned: Section A (MEI Drivers) to fix all misunderstandings

Before:

After:

reply

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

Sun Apr 12, 2015 6:35 pm

Is this the latest IME firmware for my Msi Mpower Max ac z97 mb.Me anilizer showes I have firmware version: 9.1.25.1005 .

reply

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

Sun Apr 12, 2015 6:40 pm

Zitat von NIK1 im Beitrag #1115
Is this the latest IME firmware for my Msi Mpower Max ac z97 mb.Me anilizer showes I have firmware version: 9.1.25.1005 .

So yes

reply

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

Page 74 of 380 � Page 1 ... 69 70 71 72 73 74 75 76 77 78 ... 380 Page �

Please enter a reason for warning.