[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]
atomota
Posts: 52 | Last online: 05.15.2017
Location
Mad Milkyway, looney town
Date registered
12.16.2015
Sex
male
    • atomota has written a new post "Intel Management Engine: Drivers, Firmware & System Tools" 05.12.2017

      Zitat von plutomaniac im Beitrag #2921
      Intel ME 11.6 Consumer PCH-LP Firmware v11.6.29.3287




      There you say the PCH-H Firmware v11.6.29.3287 was found, but only the LP is up?

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

      Zitat von plutomaniac im Beitrag #2909
      Zitat von atomota im Beitrag #2908
      [quote=Pacman|p38505]@atomota the chipsets are different enough not to risk that sort of thing

      It is fully compatible, the FIT SKU has nothing to do with compatibility. Only the actual firmware SKU has.


      Are you sure about this, (dont take it personally I need to be sure beyond any doubt) if that is not right, there is no way back from that(except hw programmers and thats not possible). But if your 100% positive then Ill trust your word for it.

      The other question is, flashing a ME FW doesn't seem to reset the recovery state, as last flash did nothing to correct my issue.

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

      Zitat von Pacman im Beitrag #2906
      @atomota

      Have you tried it? just because the FIT SKU say H110 doesn't mean it will not work for other SKU's.
      I don't see why it would not work on Z270.


      Considering there is no going back from that, I rather not risk breaking more shit, the chipsets are different enough not to risk that sort of thing, Im trying to fix something not break more.

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

      Zitat von plutomaniac im Beitrag #2902
      Intel ME 11.6 Consumer PCH-H Firmware v11.6.27.3264

      Sadly for me that only for the H110 chipset not for Z270

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

      Zitat von davidm71 im Beitrag #2861
      @plutomaniac

      Stupid question: If someone messes up their bios by a bad ME flash like Atomato did can't they pull their cmos chip and wipe it with a cmos writing stick like a CH341A and reflash stock firmware back onto it?


      You make too many assumptions, because I never even touched or flashed the ME to cause the problem, this is a problems with these motherboards by default, I came here trying to find some help since Asus are a POS and dont support or provide support for their product.

      I have kept plutomaniac up-to-date with my Attempts to fix it and am still trying to get answers to some questions. (he answered main question) Ad nauseam but I still have ME related questions.
      As to your suggestion- "They" cant be taking 24/7 systems off-line for that long until an alternative is possible that allows your kind of suggestion which plutomaniac already provided answer for.

      @plutomaniac
      Could I flash the 1.7.0.1229 ME on this board?
      also if the VCN is what prevents ME downgrades is it safe to assume that as long as VCN is the same then a downgrade is possible?
      Could I flash the corporate ME on this?

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

      Zitat von plutomaniac im Beitrag #2840


      @ atomota:

      If that was the case the problem would have been solved after updating to 11.6.25.1229. Remember that if the problem is at the ME data then ASUS won't be able to fix it remotely by a BIOS update (as we extensively discussed before). If the problem is at the ME firmware then a simple update will solve it. Also, no need to tag me at this thread, I monitor it regardless.


      Im not sure about this whole endeavour is new terrain, because the changelog of that version doesnt specify the bug fix required, and previous versions dont have changelogs on the consumer firmware.

      Sure Version 11.6.21.1228 corporate fixes the issue, but I cant see that firmware anywhere either and Ive no idea if I can goto corporate FW or Back or what the limitations are.
      - Fixes fail to boot issues in certain corner case scenarios.
      - Resolves an issues pertaining to clearing CMOS variables.
      - Resolves an issue where ME will enter recovery mode after power cycling.

      Im not sure how fixes are disseminated across all releases, I have a feeling they dont. What are your thoughts on that?

      In any case I have now flashed 11.6.25.1229 and the problem persists. :( so the theory that this version would fix the issue is confirmed not to be the case.

      I cant downgrade the ME firmware either as it wont accept the previous version as compatible with platform. Is it possible to downgrade at all? (for purposes of not breaking warranty)? (not that its worth a fart Asus and retailer not fulfilling the obligations anyway.


      >FWUpdLcl64.exe -F 11.6.0.1126_CON_H.bin

      Intel (R) Firmware Update Utility Version: 11.6.27.3264
      Copyright (C) 2007 - 2017, Intel Corporation. All rights reserved.

      Communication Mode: MEI
      Checking firmware parameters...

      Warning: Do not exit the process or power off the machine before the firmware update process ends.

      Are you sure you want to perform a Firmware Downgrade? (Y/N): y
      Sending the update image to FW for verification: [ COMPLETE ]

      FW Update: [ 0% (/)] Do not Interrupt
      Error 8758: The image provided is not supported by the platform.


      Im somewhat lost here so any advice on either how to downgrade or how to remove the ME from recovery mode (with exception of what we discussed already would be welcome)

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

      Zitat von plutomaniac im Beitrag #2840


      @ atomota:

      If that was the case the problem would have been solved after updating to 11.6.25.1229. Remember that if the problem is at the ME data then ASUS won't be able to fix it remotely by a BIOS update (as we extensively discussed before). If the problem is at the ME firmware then a simple update will solve it. Also, no need to tag me at this thread, I monitor it regardless.


      I never updated to 11.6.25.1229, I was under the impression my board doesnt allow that so I never tried.

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

      @plutomaniac at last I found cause/culprit.

      The first clew I have as to what caused my issue with (A7) Me FW Downgrade - Request Me Spilock Failed was when I read the change-log on Intel Management Engine (ME) Firmware Version 11.6.27.3264 (S & H) (5 MB)
      found at http://www.station-drivers.com/index.php...id=2829&lang=fr

      OK that seems to be a corporate ME but none-the-less it has the clew I needed.

      Zitat

      Version 11.6.21.1228 -Fixes fail to boot issues in certain corner case scenarios.
      -Resolves an issues pertaining to clearing CMOS variables.
      -Resolves an issue where ME will enter recovery mode after power cycling.



      So a simple power cycle caused this issue of sending the ME on my board into recovery mode which results in above message being displayed.
      We had already established that the ME was in recovery mode, but I never found the reason. and its absurd.

      Asus still jerking me around. The ideal would be to get in direct contact with someone in Asus Taiwan, since US/EMEA are independent and do whatever they like i.e. burying head in sand and not being helpful, after 5 reports and ever increasing data attached to bug report (8 pages of logs/reports gathered with various tools.) at least I know what Im reporting is the issue with some relief and certainty.

    • atomota has written a new post "BIOS Company" 04.07.2017

      you could zip that bios and upload it here attaching it to your reply, maybe people with access to tools will try to run that by those tools.

      Without knowing where the BIOS dump came from its impossible otherwise or advising which tool to use. so best provide the file and any information like which system and details about that system where this dump came from. If you dont know this best look at a hex editor.

      Best results maybe upload the dump here.

    • I think I extracted some newer microcode see attachment. On the other hand Im quite sure this means nothing, in that case I apologise and ignore it as the UBUntool reporting the new microcode is likely too old.

      This is related to post Intel CPU Microcode modules (2)

    • atomota has written a new post "[Guide] How to insert pictures or attach files to a post" 04.07.2017

      Zitat von Fernando im Beitrag #7
      Zitat von atomota im Beitrag #6
      Thats unfortunate.
      If you pay the new hoster and do the required work (incl. a frequent backup, which is now done by my current hoster Xobor.de), I will think about a move to another hoster.



      Well, what I meant by unfortunate is that https://www.xobor.de/ claim this is a professional forum software and yet have clearly quite buggy Language support and feature wise seems fairly impaired (from my non admin ability in this forum).

      I would argue that it is their responsibility to deliver on the promise of this so called professional forum software and fix those bugs, unless of course their support is like Asus, Corsair and such many terrible companies that provide bad support and have no interest in their customers.

      However looking at https://www.xobor.de/ they clearly also only target German consumers and have no English on their website, which probably means that wont get any better soon.

      On the subject of moving these boards to another hoster:

      This would be a challenge without knowing what compatibility or migration systems exists if any, because I assume you would want to import user accounts, all posts and databases. I imagine much if not everything would break, especially if this forum software is unique to Xobor.

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

      Theres a new ME Driver Intel Management Engine Interface (MEI/AMT) Version 11.7.0.1010 WHQL


      Seems driver version remains same that one you blocked though 11.7.0.1002


    • atomota has written a new post "Intel CPU Microcode modules" 04.07.2017

      According to UBU tool 1.65 > This MSI 7A69_223.zip Download < has found new CPU microcode


      Select option for update

      1 - Intel RST(e) OROM and EFI SataDriver
      OROM IRST RAID for SATA - 15.5.0.2813
      EFI IRST RAID for SATA - 15.5.0.2813
      EFI AMI NVME Driver present
      2 - Intel OROM VBIOS and EFI GOP Driver
      OROM VBIOS SKL-KBL - 1046
      EFI GOP Driver SKL-KBL - 9.0.1052
      3 - LAN OROM PXE and EFI UNDI - Intel, RTK, BCM, QCA
      OROM Intel Boot Agent CL - 0.1.10
      EFI Intel Gigabit UNDI - 0.0.09
      7 - Update Intel CPU MicroCode
      Kabylake CPUID 0906E9 - 48
      Skylake CPUID 0506E3 - A6
      Found new Microcode 000906E9000000220000004811152016000178004761D4C9
      9 - ME Analyzer
      FW ME of scanned BIOS File 11.6.25.1229 CON_H_D0
      i - Versions, HomePages and etc.
      0 - Exit
      Press ENTER - Re-Scanning ALL EFI modules.

      Enter number:

    • atomota has written a new post "ME Analyzer: Intel Engine Firmware Analysis Tool" 04.06.2017

      Whats does PV FD and VCN stand for?

      Some of the outputs of this tool are somewhat clear, but others are clear as mud, both the label like above or the values it reports.
      Could you clarify the meaning of these?

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

      Zitat von plutomaniac im Beitrag [Discussion] UBU Tool related Questions, Reports and Suggestions
      Updating and Servicing/Repairing the ME firmware are not the same thing. For the former everyone (OEM & end users) uses Intel's FWUpdate tool (clearly explained at the ME thread). For the latter, which is what you need, other methods are required.


      So I can flash the updated version? (I know its not what I need but Im willing to try) OK, since all 5 motherboards tested with same issue here and another umpteen at my friends and Asus is diddling both of us, I guess in that case I can try the upgrade to latest ME firmware and see what gives.

      I already have the right FW image.

      Current

      -------[ ME Analyzer v1.10.2 ]-------
      Database r82

      File: TUF-Z270-MARK-1-ASUS-0906.CAP

      Family: ME
      Version: 11.6.0.1126
      Release: Production
      Type: Region, Extracted
      FD: Locked
      SKU: Consumer H
      Rev: D0
      VCN: 120
      PV: Yes
      Date: 20/09/2016
      FIT Ver: 11.6.0.1126
      FIT SKU: KBP-H Z270
      Size: 0x1F0000
      Platform: SPT/KBP
      Latest: No

      Press enter to exit


      Newer target ME update

      -------[ ME Analyzer v1.10.2 ]-------
      Database r82

      File: 11.6.25.1229_CON_H.bin

      Family: ME
      Version: 11.6.25.1229
      Release: Production
      Type: Region, Extracted
      SKU: Consumer H
      Rev: D0
      VCN: 178
      PV: Yes
      Date: 12/02/2017
      FIT Ver: 11.6.25.1229
      FIT SKU: KBP-H Z270
      Size: 0x1BF000
      Platform: SPT/KBP
      Latest: Yes

      Press enter to exit



      By the way @plutomaniac what does the VCN: 178 mean? The original is VCN: 120

      The size is obviously different but Im assuming this is normal.

      Ill let you know what the result is.

    • atomota has written a new post "[All about] Intel Ethernet/LAN Drivers" 04.06.2017

      No idea really of the cause, Im fully blocking all telemetry, CEIP and anything else under the sun, unfortunatly I dont have the patience to reinstall the OS just because the version went from 14393.0 to 14393.959.

      On my Virtual machines all is fair game, in fact Im running various virtual OS of 1703 build 15063.14, Pro and Enterprise 2016 LTSB flavours, but the virtual hardware is not same so the issue doesnt apply.

      My motherboard though has two NICS so I wonder :/ anyway, Im fixed ;)

    • atomota has written a new post "[Discussion] UBU Tool related Questions, Reports and Suggestions" 04.05.2017

      Zitat von plutomaniac im Beitrag #2860
      No you cannot "swap" via UBU, that will never happen, and no you cannot do anything to fix that problem without having FD read/write access. Neither UBU nor MEA can help you, the tools are unrelated. It has already been discussed elsewhere, end of story.
      Yes I read that on the description on main page.
      I know Im stuffed.
      The question is, how would Asus update the ME firmware then? If it cant be done via mainboard bios and the FD is locked, then this means that the ME firmware will always be that version?
      Somehow I have a hard time believing this, sadly I lack the skills at this moment to investigate this further.
      Unless of course Asus can release a mainboard bios that unlocks the ME FD for update and locks it back up after. No idea, Ill have to research this elsewhere.
      Edit:
      I downloaded the UBU tool version 1.65 from somewhere else and confirmed that it has no facility to swap the ME module.

      @plutomaniac I know the MEA only analyses the ME bios, I only used it to confirm that the mainboard bios ships with the broken ME version I have.
      I will investigate the possibility of how to unlock the FD via mainboard bios and swap the ME Module via other means other than this forums. There simply has to be a way Asus can perform this update other than direct HW flash.
      Sadly the Intel ME is shrouded in secrecy and conjecture and if such way exists to do via mainboard bios, no one that knows will speak up.
      Yes, yes, I know, theres nothing you can do, I remember what you said, Im just verbalizing my thoughts as I cant give up on trying to fix my issue.

    • atomota has written a new post "[Guide] How to insert pictures or attach files to a post" 04.05.2017

      Thats unfortunate.

Recipient
atomota
Subject:


text:
{[userbook_noactive]}


Xobor Forum Software von Xobor