[b][/b]
[i][/i]
[u][/u]
[s][/s]
[code][/code]
[quote][/quote]
[spoiler][/spoiler]
[url][/url]
[img][/img]
[video][/video]
Smileys
smile
smile2
spook
alien
zunge
rose
shy
clown
devil
death
flash
sick
heart
idee
frage
blush
smokin
mad
sad
wink
frown
crazy
grin
hmm
laugh
mund
oh
rolling_eyes
lil
oh2
shocked
cool
[mail][/mail]
[pre][/pre]
Farben
[rot][/rot]
[blau][/blau]
[gruen][/gruen]
[orange][/orange]
[lila][/lila]
[weiss][/weiss]
[schwarz][/schwarz]
plutomaniac
Posts: 2640 | Points: -1 | Last online: 06.22.2017
Date registered
09.16.2014
Sex
not specified
    • plutomaniac has written a new post "Intel Management Engine: Drivers, Firmware & System Tools" Yesterday

      That's what we need. Give him some instructions on how to use an EFI shell to change whatever setup_var controls that option. Is it permanent though? I'm asking because that option needs a restart to work after being set.

    • plutomaniac has written a new post "Intel Management Engine: Drivers, Firmware & System Tools" 06.20.2017

      You can either temporarily (until next reboot) enable read/write access by sorting two pins of the audio chip while the system starts or you can use a hardware programmer to manually desolder, program and resolder the BIOS/SPI chip of the board. I avoid saying more to not waste my time as most less-knowledgeable/handy people refuse to continue with such solutions.

    • plutomaniac has written a new post "Intel Management Engine: Drivers, Firmware & System Tools" 06.20.2017

      Then the ME firmware is corrupt. To repair it you would need read/write access to its region at the BIOS/SPI chip. That can only happen, if warranty is not valid anymore, by physically opening the laptop and doing some actions.

    • plutomaniac has written a new post "Intel Management Engine: Drivers, Firmware & System Tools" 06.20.2017

      It's not dangerous but you can always do the "manual" method outlined above.

    • plutomaniac has written a new post "Intel Management Engine: Drivers, Firmware & System Tools" 06.20.2017

      Zitat von fylgja im Beitrag #3084
      file time stamp was missing.

      Yes, by design. The current OS date/time will be applied upon extraction.

    • plutomaniac has written a new post "MC Extractor: Intel, AMD & VIA Microcode Extraction Tool" 06.20.2017

      Alright, thank you for your feedback rygar. I'll make it easier to understand where the pre-built/"compiled" executable can be found.

    • plutomaniac has written a new post "Intel Management Engine: Drivers, Firmware & System Tools" 06.20.2017

      @ forceadmin:

      Before the problem appeared, what BIOS version did you have? With that previous BIOS, did you have any issues? Had you checked, before the problem appeared, whether the ME was working properly before (MEInfo, MEManuf)? From some google searching I can see that those random reboots may have to do with the battery connection being lose or something, not ME related. As far as the ME is concerned, you can do a manual -greset by removing all power from the laptop (cord + battery) for 1 minute. After that, try to rerun MEInfo and MEManuf in DOS, is there any change? Meaning, is the ME out of "Recovery" mode?

      @ The Engineer:

      Never try again what you were about to do as it could have lead to a lot of problems. To understand your mistake, read "Firmware Regions (RGN/EXTR)" found at Section B of the first post. In your case, you wouldn't have been able to continue regardless, because you have no read/write access to the ME region (error 26). If the BIOS shows N/A at the ME version, it means that the latter is probably corrupted and a reflash is needed (which requires read/write access to its region, things will become harder if that's the case). If it's not corrupted (fingers crossed), it may be stuck (uncommon unfortunately). First run "fptw -greset" command via Flash Programming Tool and test if the problem persists after the reboot. If the command fails, try a manual "-greset" by shutting down the system and removing all power (cord + battery) for 1 minute.

    • plutomaniac has written a new post "MC Extractor: Intel, AMD & VIA Microcode Extraction Tool" 06.20.2017

      That's the thing, MCE is pre-compiled by me to help others by not having to go through that trouble. It's here. Since other people seem to miss that fact (even though it is explained at the readme of Github), I am interested in knowing how you (and thus others) look for the pre-compiled executables so that I can guide you better. Did you miss the Releases page, did you visit it but saw "DB" at the top and did not scroll down etc?

      Now, as far the MC are concerned, i7-920 has CPUID 106A5 or 106A4 and W3690 has 206C2.

    • plutomaniac has written a new post "MC Extractor: Intel, AMD & VIA Microcode Extraction Tool" 06.19.2017

      Hello rygar,

      Thank you for your interest in MCE. What processor do you have? Only one of those is used at your system, no need to deal with the rest. Also, did you know that MCE has pre-built images or did you just decide to build it for your own needs?

    • plutomaniac has written a new post "Intel Management Engine: Drivers, Firmware & System Tools" 06.19.2017

      Intel ME 9.0 5MB Firmware v9.0.31.3488 (INTEL-SA-00075/CVE-2017-5689)

      [[File:Capture.PNG|none|fullsize]]

      Intel ME System Tools v11.6 r14
      Intel ME System Tools v11.0 r8


      Updated the notice regarding INTEL-SA-00075/CVE-2017-5689 (found 9.0.31.3488 5MB from Toshiba, added 8th Gen 11.7 entries):

      [[File:bug.PNG|none|auto]]

    • plutomaniac has written a new post "Intel Management Engine: Drivers, Firmware & System Tools" 06.19.2017

      Download them and check for yourself, mup.xml or the driver/executable versions. They're 11.7-based, as can be found here or at SD.

    • plutomaniac has written a new post "Intel Management Engine: Drivers, Firmware & System Tools" 06.19.2017

      @ myDNA:

      Update to the latest 11.6 firmware. Read the first post to understand whether the vulnerability even applies to your case.

      @ Ataemonus:

      Nothing new.

    • plutomaniac has written a new post "Intel Management Engine: Drivers, Firmware & System Tools" 06.18.2017

      @ Jerok:

      The answer to your question can be clearly found at the start post, please read it.

      @ e1D:

      I added two new notes at the start post to explain fully what the three ME firmware Types are, what is offered for which platform and what is used with what tool.

      [[File:Capture.PNG|none|auto]]

      @ forceadmin:

      Thank you for your prior research and detailed report forceadmin, that's not common. Now, try to run the DOS or EFI versions of the tools which I'll mention below to exclude the OS and/or drivers causing issues. Download the ME System Tools v9.1 (they work with 9.0 and are a lot newer). Run (under EFI/DOS) Flash Programming Tool with command "fpt -greset" and check if the problem persists after the reset. If it does, boot into EFI/DOS and run MEInfo -verbose and MEManuf -verbose and save their results (example: MEInfo -verbose > result.txt) in two files which you can later compress and attach here for me to check out. Does your BIOS has any option to Disable the ME such as "ME Reflash", "ME Disable", "HMRFPO" or similar?

      @ DioExtreme:

      Soft-of. At post-SKL FD, the region access settings are 3-bytes long (0 reserved & 1-3 access, in Big-Endian reading). The first dword is CPU/BIOS, the second ME, the third GbE and the fourth EC, whenever the last two exist of course. Thus, in your case, you need to replace these:

      [[File:Capture2.PNG|none|auto]]

      To verify your changes, you can use ME Analyzer > FD field (Locked --> Unlocked).

    • plutomaniac has written a new post "Intel Management Engine: Drivers, Firmware & System Tools" 06.14.2017

      Intel MEI Driver v11.7.0.1017 MEI-Only Installer
      Intel MEI Drivers & Software v11.7.0.1017 for Consumer systems


      Intel ME 11.10 Consumer PCH-H Firmware v11.10.0.1287

      [[File:Capture.PNG|none|fullsize]]

      Thanks to SD for the new drivers.

    • plutomaniac has written a new post "Intel Management Engine: Drivers, Firmware & System Tools" 06.14.2017

      Sounds like an electrical short circuit to me, maybe some USB port is malfunctioning. Don't always trust what "support" says. Unless you go way up the chain, they usually don't know what the problem is and suggest whatever comes to mind.

    • plutomaniac has written a new post "Intel Management Engine: Drivers, Firmware & System Tools" 06.13.2017

      @ andr84:

      Your previous post showed that the problem is not ME related but something with the USB and/or USB hubs. I don't have something to suggest which is ME related.

      @ xZaggin:

      The onboard graphics are in the CPU, not motherboard. What did you change exactly, CPU or Mobo? No matter what though, what I said above still applies. You need to reflash the ME which can only happen as described above.

    • plutomaniac has written a new post "Intel Chipset Device "Drivers" (= INF files)" 06.13.2017

      There is nothing for Fernando to check out, you are good to go. Just ignore the Chipset INF Utility.

    • plutomaniac has written a new post "Intel Management Engine: Drivers, Firmware & System Tools" 06.13.2017

      @ all:

      It looks like (at least) 11.7 was also vulnerable to INTEL-SA-00075/CVE-2017-5689. The presence of 11.7 firmware with build 3000-something proves that. So use 11.6 firmware as provided at the first post, not 11.7 yet. As always, this is relevant to systems with Corporate firmware only, not Consumer.

      @ xZaggin:

      When you say "failed and I had it replaced", I assume you mean that you had to replace the entire motherboard. In that case, there is a high chance that the ME firmware is not behaving properly as explained at Section A here. Basically you would need to follow that guide and repair the ME firmware. However, that won't be possible because ASUS always locks read/write access to the ME firmware, per Intel's recommendations, so you would need physical access to the board in order to remove the SPI/BIOS chip and reflash it with a hardware programmer. To verify the read/write access lock, just download Intel ME System Tools v8 and run Flash Programming Tool with command "fptw -d spi.bin" and you'll see a CPU access error or similar. You should try running "fptw -greset" command and see if the problem is solved after the reboot but I highly doubt it will be effective in your case.

    • plutomaniac has written a new post "Intel Chipset Device "Drivers" (= INF files)" 06.13.2017

      You should never bother unless there is any unknown Intel device at Device Manager.

Recipient
plutomaniac
Subject:


text:
{[userbook_noactive]}


Xobor Forum Software von Xobor