[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: 22 | Last online: 03.22.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" 03.21.2017

      Zitat von nikos xatz im Beitrag #2759
      Usually when you get this error after post ''Me FW Downgrade - Request Me Spilock Failed'' the ME Version in Bios should be ''ME FW Version 0.0.0.0'' but you said that your's is ''11.6.0.1126'' i don't get it how is this possible ?!?!?!?!?
      anyway your problem(usually) can be fixed with a Bios update through Bios Flashback or with a ME Firmware Update through Windows... but it seems that your problem is more strange.....
      I have read somwhere that other people have issues with the same error and it was the ''Secure Boot'' option in Bios , have you tried this???
      it's in the Boot Section under Secure Boot and in OS Type select UEFI Windows mode....


      Ive posted the rsults of MEinfo and MEmanuf in that post I linked, so the information is all there...
      According to plutomanica this ME bios is locked, which I have also confirmed by gathering info on the bios and ME firmware with the tools (results which I posted)

      now the error happens with UEFI secure boot ON or OFF (different OS installs of course)

      @nikos xatz read plutomaniacs replies to me, Im willing to try many things but flashing ME bios doesnt seem possible from windows.

      See Intel Management Engine: Drivers, Firmware & System Tools (183)

      anyway @plutomaniac Asus have replied to me telling me they cant duplicate issue and that they dont suspect bios issues and thus they wont be passing the issue to headquarters, meaning they dont give a s**t.

      Ive complained off course not that it matters. So unless this is fixed by magic, I doubt I will ever see a fix, but Im still waiting for Asus reply to my last email, which they will reply in around 4/5 days.

      ASUS boycote.

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

      @plutomaniac some update on my tribulation with Asus not-support.

      So after much waiting and a extremely thorough report that Asus "requested" that took me some I received this reply after some days.

      Zitat von Asus NOT Support

      Dear Sir/Madam,

      Thank you for your emai


      Please be advised that you can disable F1 Promption in the BIOS settings to get rid of the notification.

      Once this is disabled, the notifcation will no longer show up and it should boot normally again.

      It is often called wait for F1 on error.

      The error message itself does not indicate any faults or issues with the system


      Kind Regards,



      This of course is total nonsense, and the issue still persists., clearly they are not taking this seriously and hope to get lucky. (just my cynical side talking ;) )

      IMO the suggestion is just as broken as the English used in reply :D

      I have replied to Asus letting them know of my findings and await another round of hopefully not nonsense, but hey, Im doubt it and fully expect to have this issue forever.

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

      Zitat von plutomaniac im Beitrag #2739
      The ME is in Recovery state due to that error you see before booting so that's why the MEInfo/MEManuf messages. Nothing invasive can be done and system up-time is important so you need to wait for ASUS to release a new BIOS for that board.


      Ill keep you posted on what happens, but Im not holding my breath.

      I was speaking with a friend who bought 3 of these boards and they all out of the blue decided to spit this error out with no good reason whatsoever, one of them he has the factory bios 0505, never been flashed and error still there.

      Like you say its new kit, but its sold as 24/7 boards, so I hope Asus do the right thing, though neither him or I are holding our breaths.

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

      Yea its definitely locked Meinfo spits this out

      @plutomaniac I was reading those posts you suggested and grabbed some outputs.

      1
      2
      3
      4
      5
      6
      7
      8
      9
      10
      11
      12
      13
      14
      15
      16
      17
      18
      19
      20
      21
      22
      23
      24
      25
      26
      27
      28
      29
      30
      31
      32
      33
      34
      35
      36
      37
      38
      39
      40
      41
      42
      43
      44
      45
      46
       
              MEBx Version found is 0.0.0.0000
      MEBx Version 0.0.0.0000
      GbE Version 0.2
      Vendor ID 8086
      PCH Version 0
      FW Version 11.6.0.1126 H
      LMS Version Not Available
      MEI Driver Version 11.6.0.1042
      Wireless Hardware Version Not Available
      Wireless Driver Version Not Available
       
      FW Capabilities 0x31111140
       
      Intel(R) Capability Licensing Service - PRESENT/ENABLED
      Protect Audio Video Path - PRESENT/ENABLED
      Intel(R) Dynamic Application Loader - PRESENT/ENABLED
      Service Advertisement & Discovery - NOT PRESENT
      Intel(R) NFC Capabilities - NOT PRESENT
      Intel(R) Platform Trust Technology - PRESENT/DISABLED
       
      TLS Disabled
      Last ME reset reason Firmware reset
      Local FWUpdate Enabled
      BIOS Config Lock Enabled
      GbE Config Lock Enabled
      Get flash master region access status...done
      Host Read Access to ME Disabled
      Host Write Access to ME Disabled
      Get EC region access status...done
      Host Read Access to EC Disabled
      Host Write Access to EC Disabled
      Protected Range Register Base #0 0x0
      Protected Range Register Limit #0 0x0
      Protected Range Register Base #1 0x0
      Protected Range Register Limit #1 0x0
      Protected Range Register Base #2 0x0
      Protected Range Register Limit #2 0x0
      Protected Range Register Base #3 0x0
      Protected Range Register Limit #3 0x0
      Protected Range Register Base #4 0x0
      Protected Range Register Limit #4 0x0
      SPI Flash ID 1 EF4018
      SPI Flash ID 2 Unknown
      BIOS boot State Pre Boot
      OEM ID 00000000-0000-0000-0000-000000000000
      Capability Licensing Service Enabled
       



      then MEManuf spits this out

      1
      2
      3
      4
      5
      6
      7
      8
      9
      10
      11
      12
      13
      14
      15
      16
      17
      18
      19
      20
      21
      22
      23
      24
      25
      26
      27
      28
      29
      30
      31
      32
      33
      34
      35
      36
      37
      38
      39
      40
      41
      42
      43
       

      Intel(R) MEManuf Version: 11.6.10.1198
      Copyright(C) 2005 - 2016, Intel Corporation. All rights reserved.
       
      FW Status Register1: 0x90202242
      FW Status Register2: 0x04F60406
      FW Status Register3: 0x00000020
      FW Status Register4: 0x00080000
      FW Status Register5: 0x00000000
      FW Status Register6: 0x00000000
       
      CurrentState: Recovery
      ManufacturingMode: Disabled
      FlashPartition: Valid
      OperationalState: CM0 with UMA
      InitComplete: Complete
      BUPLoadState: Success
      ErrorCode: Disabled
      ModeOfOperation: Normal
      SPI Flash Log: Not Present
      Phase: ROM/Preboot
      ICC: Valid OEM data, ICC programmed
      ME File System Corrupted: No
      PhaseStatus: AFTER_SRAM_INIT
       
      FPF and ME Config Status: Not committed
       
      FW Capabilities value is 0x31111140
      Feature enablement is 0x11111140
      Platform type is 0x724F0322
      No Intel Wireless device was found
      Feature enablement is 0x11111140
      ME initialization state valid
      ME operation mode valid
      Current operation state valid
      ME error state invalid
       
      Error 235: Internal error
       

       
      Error 117: MEManuf Operation Failed
       
       



      So it seems that ME is in an invalid state, still no idea how that happened.

      Im somewhat intrigued by this message FPF and ME Config Status: Not committed though to me that means onions.

      At least I hope this helps some, in what way idk.

      thanks again.

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

      Zitat von plutomaniac im Beitrag #2735

      Yeap, as I said, BIOS related. That's what I've observed as well from past experience.


      Yes but its strange that nothing happens for ober two weeks after bios upgrade, then suddenly this? Odd to say the least, I did notice that after upgrade the only quirk was an increased POST time of extra 6+ seconds, but Asus support via email, dismissed it, but that was level 1, they dismiss pretty much everything.

      Zitat von plutomaniac im Beitrag #2735

      Well you can try to see if you have read/write access to the ME region but don't get your hopes up as it's common practice and an Intel recommendation to do the opposite for security purposes. Just run "fptw -d spi.bin" command and if you see CPU Access Error then you cannot do anything via software. I can already see from the MEInfo report you posted that it is locked so that's a bust too. Another way to enable read/write access is by doing the "pinmod" which requires shorting two pins of the audio chip while the system boots but in your case it's not possible because the board has a) a shroud and b) the audio chip has an EMI shield which does not allow pin shorting. Now that I think about it, the SPI chip is probably also under the board shroud so you wouldn't be able to get to it without first going through the trouble of removing that, let alone buying and using a programmer.


      I can throw system down for 2 hours tops, assuming that I know everything to do, which I dont and everything goes right the first time, which no one can say for sure, this sounds more than 2 hours.

      Zitat von plutomaniac im Beitrag #2735

      That error should not cause any actual issues to the system, meaning that you can use it. It must be that ASUS has messed something up and the BIOS is trying to restore an older ME firmware version which is not possible as long as there is no read/write access there (locked SPI Flash Descriptor, FD) and thus the "Request Me Spilock Failed" message.



      Ive let them know whats what, but Im not holding my breath, from many years of Asus lack of support personal experience (maybe Im unlucky) they just dont seem to ever correct the serious issues.

      Zitat von plutomaniac im Beitrag #2735

      The KBL boards are new so such bugs can happen. ASUS should fix it soon enough, hopefully. You can try updating the ME via FWUpdate as well just in case this will help the BIOS get over it. Who knows. I assume you have tried doing a clear CMOS, right?


      Of course, CMOS clearing is the goto step as I did that first before anything in post #2731 more than once in two different ways, one was shorting the pins, the other short + battery out.
      I reflashed 0701 previous bios and restored a 0701 compatible config (currently running) no dice.
      Ill reflash the 0801 later on and restore the config for 0801 (which is incompatible with 0701 config too many changes)
      and no making fresh configs makes no difference either, been there.

      Zitat von plutomaniac im Beitrag #2735

      I don't honestly remember how I ended up using that avatar years ago but that's news to me. Ha-ha, thanks for letting me know.


      If it wasnt Don Quixote and Rocinate, it is now :D

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

      Thx for repIy,

      I managed to speak to someone at Aus live Chat Germany (useless), but they will offer RMA, tbh Im not interested in RMA or downtime longer than 2 hours as this is a critical system, therefore its cheaper to buy a new board replace it and burn the old.

      I havent tried to flash anything ME related, Or even touched anything ME related until you asked me to do the -greset, the only thing Ive updated was the the board bios from 0701 to 0801, which neither have the issue, then suddenly out of the blue this msg appears.

      so what youre saying is Im stuffed without a hw programmer ;)

      Ive reported the issue after the live chat, to Asus, as a form of complaint, because theres no other way to get to level 2 support, level one's reason for existing is (it seems) to make you lose the will to live.

      Ill have a read of those posts you suggest, thank you so much for pointing, if for no other reason but to further my education in this matter.
      I dont get that 2nd message though Error sending End Of Post message to ME, so its not a OS boot stopper.

      In meanwhile I would like to either reflash the ME only or if thats not possible get another board, replace it and hope Asus release a bios with a fix, Im not holding my breath.

      What a waste of time though in 2017 youd think resolving something like this would be simple, yet its like the dark ages, which is probably why your avatar is, Don Quixote de'la Mancha and his trusted Rocinate.

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

      Anyone have any advice at all other than whats been said?

      Sorry to seem impatient but, Im out of ideas and web results dont yield anything that seems to work or has nothing to do with Asus anything. The explanations to what that message means are also no clew to the possible causes hence no solution gleamed thus far.

      EDIT

      Reading http://forums.aria.co.uk/showthread.php/...-SPilock-failed seems to indicate a reflash is needed for ME, so again I go back to my first post, as Ive simply no idea how to mod the ME FW for this mobo or if I just flash the one thats on the 1st post without modifications...

      Also not being familiar with tools doesnt help...

      :(

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

      Zitat von plutomaniac im Beitrag #2730
      @ atomota:

      This is a brand new desktop motherboard so this is what you should do:

      1) (Re-)Apply the latest BIOS from ASUS as provided at their site via the in-BIOS menu
      2) If the error persists, try running Flash Programming Tool with parameter fptw -greset
      3) If the error persists, contact ASUS support


      1) While waiting for a reply, I reset CMOS and reflashed the latest BIOS, 0801 which was already in there but none-the-less reflashed and reconfigured -- Result no dice -- (A7) Me FW Downgrade - Request Me Spilock Failed still prints after POST
      2) I used the 64bit version as well FPTW64.exe -greset, it was way to fast to see what popped up in terminal, but, the first line was yellow text, second some green text and system rebooted --- Result no dice -- (A7) Me FW Downgrade - Request Me Spilock Failed still prints after POST
      3) Contact Asus, hahahahahahahahaha you are the most hilarious person yet, may as well ask Elvis. Level 1 support dont care, and in order to get to level 2 you need to complain and they never reply... been there done that.

      Any other ideas short of replacing the motherboard?

      I read somewhere about disabling Intel C-state in Bios, but my Hardware and Bios configuration is unchanged since build and this never happened. it just literally started showing up without any apparent reason.

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

      Hi guys.

      This thread is 182 pages long so I didnt read all of it. but I did read main posts and warnings etc.
      Im new at this, have some idea what Im doing but never done this bit before. So some guidance or help please?

      Yesterday for no apparent reason (there were no drivers of this nature installed or upgraded), I get this error/notification just after POST

      (A7) Me FW Downgrade - Request Me Spilock Failed

      The system boots fine, Ive not yet taken steps to try remedy this... So please some advice.

      Now, if I go the root of firmware upgrade, can I just grab the Intel ME 11.6 Consumer PCH-H Firmware v11.6.20.1221 and flash that as is?
      Ive no idea how to modify firmwares or flashing this type of firmwares, but certainly would like to get rid of that notification.


      Ive analysed by system (Asus TUF Mark 1 + kaby lake i7-7700K (socket 1151) with the MEInfoWin64 r6 the result is as below.

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

      If there is any other information you guys need let me know.

      Really appreciate this guys, thanks in advance

      atomota

    • atomota has written a new post "AHCI & RAID ROM Modules" 06.27.2016

      Howdy fellows :)

      I have one of These PCI cards, Its flashed with 0.951 from station drivers, however I see main post has newer rom, but cant flash it via that tool since these are for Motherboards with built in chipset?

      Anyone know of any standalone flasher or knows how to flash this newer FW into the PCI card?

    • atomota has written a new post "[Discussion] Marvell 91xx/92xx SATA3 Controller BIOS modules" 02.01.2016

      Zitat von Gast im Beitrag #184
      does it matter if you flash 9123' to 9128?

      does a 9128 need updated? how can i tell what to just put on my marvell? what if parts are missing? is there only 1 file to flash?


      read this it explains the ID's the best way I have heard it explained by a person who knows these things backwards

      Zitat von lordkag im Beitrag #162
      The ID is selected depending on the controller's mode: 91A3 in IDE, 9123 in AHCI, 9128 in RAID. If you have a controller only capable of IDE or AHCI, it will have the right ID. If you have a controller capable of RAID, like 9128, it will use an OROM with 9123 ID and switch it on the fly to match the mode. Use 9123 ROM/BIOS if you have 9128 controller - this is Marvell's way of doing things. As for the IDE label, haven't seen anyone else mentioning it, don't know if it is something you can fix. Use proper ID as explained above, check in mainboard BIOS, check in Marvell BIOS.

    • atomota has written a new post "[Discussion] Marvell 91xx/92xx SATA3 Controller BIOS modules" 12.19.2015

      Zitat von lordkag im Beitrag #166


      @atomota

      I don't think this has to do with Marvell. It looks like your mainboard is showing those tags. Are 1st Drive and 6th Drive connected to same Marvell controller? If not, then you have your answer. Even if it will be true, the fact that you have AHCI in Windows (or any other OS), it makes this a cosmetic issue and not an important bug.


      @lordkag

      Ist drive is attached to the marvel controller port 1 (port 2 is empty atm)
      6th Drive is attached to a external pci-e sata 3 controller

      Yes I think its not significant bug and does seem to be cosmetic.

      Is there anything that cna be done to improve the write speed on the Marvel controller? I have minus ~30Mb/s write speed on the Samsung 840 Pro on the sata 3 controller then on the sata 2 controller. Ive been told this is marvels convoluted way of dealing with these things on this controller, if you say nothing can be done about it I wouldn't be surprised., ill now test which FW/Bios versions provide better results here and report back on the appropriate thread.

      thanks again have definitely learned a few things about this bios, and mostly a renewed lesson, not to buy new tech when it first comes out :p hahaha

    • atomota has written a new post "[Discussion] Marvell 91xx/92xx SATA3 Controller BIOS modules" 12.18.2015

      Zitat von lordkag im Beitrag #162
      The ID is selected depending on the controller's mode: 91A3 in IDE, 9123 in AHCI, 9128 in RAID. If you have a controller only capable of IDE or AHCI, it will have the right ID. If you have a controller capable of RAID, like 9128, it will use an OROM with 9123 ID and switch it on the fly to match the mode. Use 9123 ROM/BIOS if you have 9128 controller - this is Marvell's way of doing things. As for the IDE label, haven't seen anyone else mentioning it, don't know if it is something you can fix. Use proper ID as explained above, check in mainboard BIOS, check in Marvell BIOS.


      @lordkag @wasisdn See attached collage, its probably nothing unusual but I wouldnt know, you can see the versions and the IDE think and though Im missing a screenshot from admin tab thats also in AHCI, on bios POST, those drives on P1 P2 P3 (attached to sata2 ) fly past as IDE, but obviously in OS its all AHCI/SCSI, the bottom drive in the boot tab as IDE is attached to a PCI-e sata 3 card also in AHCI mode but in motherboard bioa it all shows as IDE... Again that probably means nothing, but its really odd.

      /me shrugs and rolls eyes at Asus expertise.

      If anyone has any ideas or suggestions Ill welcome them iwith open arms.

    • atomota has written a new post "[Discussion] Marvell 91xx/92xx SATA3 Controller BIOS modules" 12.17.2015

      Zitat von Fernando im Beitrag #158
      @ atomota:
      As wasisdn has already mentioned, your posts regarding the Marvell SATA Firmware match much better the topic of this thread.
      That is why I have moved your discussion with wasisdn here.
      This way it is much easier for wasisdn and other visitors of this thread to find your discussion.

      @Fernando

      Thx, because I had questions that are probably not specific I wasnt sure, but OK, Im happy with your decision.

      Zitat von wasisdn im Beitrag #159

      The correct Firmware for Marvell ROM 1.0.0.1038 is 2.3.0.1007 with Bootloader 1.0.1.0002bv5, your older FW and BL is actually for Mavel ROM 1.0.0.1033.

      I have used same Bios like you but lordkag was so kind to extract the 3 single modules for the Marvell controller with correct header from the bin update file (same as you have attached before) to insert them in the sabertooth bios.

      For JMicron I can also give you a Bios with this 1.0.8.01 ROM module but I've tested it allready and found my externel RAID5 Box connectet to JMicron eSATA initializing much faster with 1.0.7.28 ROM during boot.

      I don't run any SSD on the Marvell but I have tested a Crucial m550 in single AHCI mode. What I can say is the seq. read rate is higher but overall the drive run much smoother and faster with the Intel SATA2 controller. But if I run the Marvell in AHCI mode there is no IDE prefix listet, just showing me the HDD size and AHCI.

      About the Device ID I'am not sure, better ask lordkag. What I know is the ROM and FW for ID9128 and ID9123 is same, just have to open the module with Hexeditor and correct the Device-ID.


      Am now running your rom mod for the X58 you posted above, but sadly, I actually lost a few Mb/s write speed... At this stage Im open to PEBCAK type considerations.
      After flashing rom and going though the update firmware screen on reboot, Booted into Marvel rom on POST Ctrl+M and confirmed indeed the infor is Marvel 1038 + FW 2301007

      So thanks to you and lordkag for that nugget, well, tbh Im more happy to have joined here, you guys are more active and seemingly know what youre doing better :D

      Im happy for the JMicron to stay at that version in your mod, as I dont use it and its disabled in Bios...

      So, to confirm: when you are in your motherboard bios boot menu not the marvel menu the drives attached to the Marvel controller dont have IDE prefix? I dont mean on the marvel menu that is indeed AHCI I mean the bios bios ;P Not sure if its relevant.

      As for the 9128 listed specs vs actual ROM ID 9123, I realize that their the same flash per say—as you explained— its just the ID, but even Asus official fw list as 9123, now I cant remember off hand what the chip itself on the motherboard actually says, but if its 9128 even if just a cosmetic thing, surely for the pedantic folk that matters also, to me Im OK personally.

      Here attached is a comparative benchmark for your mod (dark blue) vs the mod I was running before(light blue), BTW thanks again for the mod, I hope you'll continue providing updated roms for this mobo, you have one FAN here already ;)

    • atomota has written a new post "[Discussion] Marvell 91xx/92xx SATA3 Controller BIOS modules" 12.17.2015

      Thanks for that, now I dont really use raid on this machine but I shall give that a try.
      Ill also follow that thread link (I have already read it before joining) and join into the discussion.

      Thanks again. ;)

Recipient
atomota
Subject:


text:
{[userbook_noactive]}


Xobor Forum Software von Xobor