Zitat von plutomaniac im Beitrag #1777

---

@ Bersekz:

Yes, you can update both ME firmware and MEI drivers based on what I provide at the first post. You have a 6-series HM65 Sandy Bridge system. That's 1.5MB ME SKU so the latest ME firmware is "1.5MB 7.1.80.1214" and the latest MEI drivers are "11.0.0.1172 INF". You don't need the software so I suggest you update the driver via Device Manager using the latest 1172 INF package I provide at the first post.

---

In the first post it's just said that it re-flash the firmware, not why you should do it? I'd like to understand what's the purpose in flashing it twice.

Why do I get the errors in the screenshot attached when I run MEManuf and MEInfo only when I'm in EFI mode in Windows? I notcied that there is an EFI folder in the tools provided here but how do I use a .efi file?

Got it, thanks.

Hi Guys,

first of all great thread.
Did just update ME Firmware on 2 systems today, worked like a charm.

I also wanted to update ME Firmware on my personal rig.
But I am not sure which Firmware I should use.

HWInfo says it is "Lynx Point Server Advanced" Chipset.
So I am wondering what Firmware fits to this?

What I found out yet is, that the Board only has the 1.5MB Firmware.
I guess it should be "B.1 Consumer Systems" ? (What irony for a server chipset -.-)
But which one?
It is Lynx Point, and no Apple...

But this firmware should be wrong since I am on 9.0 Firmware and not 9.5
Intel ME 9.5 Consumer 1.5MB Firmware v9.5.55.1948
For Lynx Point Haswell systems which come with ME firmware v9.5.x

So should I take the one for 8 Series chipset?
Intel ME 9.0 Consumer 1.5MB Firmware v9.0.31.1487
For 8-series systems which come with ME firmware v9.0.x

What I've read, the 9.1 Firmware would not be suitable, I should stick to the 9.0 ?

Until now i thought since it is kind of "servergrade" i would at least get
the full "vpro experience" on it, what is one reason why i chose this board :/
Latest BIOS is installed on the board.

Here's what MEInfo says:

GBE Region does not exist.
Intel(R) ME code versions:

BIOS Version: 2202
MEBx Version: 0.0.0.0000
Gbe Version: Unknown
VendorID: 8086
PCH Version: 5
FW Version: 9.0.30.1482 H
LMS Version: 11.0.0.1167
MEI Driver Version: 11.0.0.1166
Wireless Hardware Version: Not Available
Wireless Driver Version: Not Available

FW Capabilities: 0x01101940

Intel(R) Capability Licensing Service - PRESENT/ENABLED
Protect Audio Video Path - PRESENT/ENABLED
Intel(R) Dynamic Application Loader - PRESENT/ENABLED

TLS: Disabled
Last ME reset reason: Power up
Local FWUpdate: Enabled
BIOS Config Lock: Enabled
Host Read Access to ME: Disabled
Host Write Access to ME: Disabled
SPI Flash ID #1: EF4017
SPI Flash ID VSCC #1: 20252025
SPI Flash BIOS VSCC: 20252025
BIOS boot State: Post Boot
OEM Id: 00000000-0000-0000-0000-000000000000
Capability Licensing Service: Enabled
OEM Tag: 0x00000000
Localized Language: Unknown
Independent Firmware Recovery: Disabled


My system:
Xeon E3-1245v3
Asus P9D WS
16 GB Kingston RAM
Crucial M500 960GB
MSI GTX770 2GB

And some screenshots of HWInfo





Hope u could help me with this :-)

@realmax
It may be a server chipset but it's more a workstation MB hence the name.
You will have difficulty to find a server motherboard with a "corporate" ME, because on servers OOB management is provided by BMC which exposes IPMI implementations like ILO, DRAC etc.

Concerning ME 9.1, it is required to support Broadwell CPUs. As of now, your motherboard doesn't support them so BIOS has no be re-engineered/customized to accept ME 9.1.
You could ask Asus to support them because for me this situation is in contradiction with http://www.asus.com/News/3py20jkmnhleyK52

HTH

@plutomaniac
OK, thanks for the info.
If I upgrade ME then I will stick to 9.0, not 9.1

So if I understand that correct I dont't even have the possibility to configure
an IP adress under ME and at least use features like power-on/shutdown/rest via
that browserbased interface?
If that isn't possible, what is that 1.5 MB ME Firmware good for? nothing?


Is there kind of a changelog available for the ME firmware versions?

@shroeder
I wanted a kind of professional board with ecc ram and the possibility of kvm.
so I thought that board was a good choice. I knew that kvm would not work,
since it requires intel as primary graphics which it is not the case.
But at least I thought I'd get that webinterface to at least see some status infos
and power up the rig remote :/

What are you referring to that news link? I only see the main page...
Broadwell is Core iX-5xxx CPUs? Board seems not to support those (yet)...
Don't know that is even compatible with chipset/socket?

@realmax

There seems to be some stange url rework here. Copy and paste the URL in a browser window.
Basically it says "5th Core CPUs are supported via BIOS update on all 9th Asus motherboard". But not yours. That's why I said you should ask Asus. Thus you will be able to have ME 9.1.
FIY, a comparable MB from ASRock (with a BMC) support them so it's not a chipset or whatever issue (http://www.asrockrack.com/general/produc...#Specifications)

1.5MB MEs lack MEBx which enable AMT which is the key to remote operations. WOL excepted, of course.
KVM support requires Intel Integrated Graphics, you're right, but to have remote capabilities, your LAN chip must be also vPro compatible, which means, on C226, I217-LM. Asus has chosen to use I210-AT (hence the "Gbe Version: Unknown").
To sum it up, vPro requires : a compatible CPU, a compatible chipset, a BIOS including ME with AMT (5MB), VT-x enabled, VT-d enabled, a compatible LAN (LM suffix).
KVM : all these plus Integrated Graphics.

From an end-user perspective, 1.5MB ME mostly deals with DRMs. In the words of Intel, it :
.tune series Chipset Family clock silicon to the parameters of a specific board, configure clocks at run time, and power management clocks.
.have limited capabilities to perform targeted workarounds for silicon issues.

Some sort of changelog is available for 5MB ME but local fixes applies to 1.5 MB. For example, see https://download.lenovo.com/pccbbs/mobiles/glrg17ww.txt