| Last online: 01.10.2017
If I would insert the latest rng image into the guid of the backup firmware, would that help in not triggering a refash of the me?
solved it with my spi programmer.
I also unlocked the descriptor with fitc, asrock had locked the descriptor.
But when I update the me, the darn bios overwrites it when I reboot :s
Is this something that I can modify somewhere?
@lordkag , can you shine in on this? :-)
seems like I need to change something in the amitse module?
god damn it, and the copy that the bios seems to flash, locks de descriptor again. grrr :-D
Here is my custom bios, amitse uncompressed and compressed module:
Hope that someone can help me out on this one :-)
I already did :-(
fptw -greset didn't work. got the warning that I had to shut down the pc instead.
I've got a fixed bios now.
But next week they will modify that one to enable the me again.
I wanted to fool around, to get the bclk unlocked in the intel xtu.
So I hope we can get a newer leaked fitc.
Is there any newer version of fitc for this me, that you are aware of?
I only flashed the cleaned image you provided me, when we tought the me was not functioning anymore. We didn't knew that the oem had disabled it in the bios.
After that I only flashed the me once. I changed 2 min and max clock values and flashed that me. ( me only)
I build that one with the latest 8.1 tools we have on the forum.
So we should be looking for a newer 8.1 toolkit?
P.s. do you have a x79 bringup guide as well?
Because the 7 series bringup guide we use, only seem to have documentation for all 7-series chipset except the x79 series.
Ah, ok. I'll wait for your result.
I was allready thinking, I was loosing my mind ;)
I noticed something else as well.
If I open the original bios. Or every full spi dump in fitc, I close fitc.
I reopen fitc and open the ME Region.bin in the Decomp folder, then the ME Region.bin shows other values as the full dump as well.
ok, so I reflashed the full dump.
I couldn't do a -greset after. it gave an error that the me was in bring up state. So I powered the machine down.
After booting again, I get exactly the same results. so I'm realy puzzled now :(
the -greset had no effect.
I'll try the full flash again followed by a -greset.
is there a way to check if there are multiple spi chips?
C:\Users\jo\Downloads\Intel ME System Tools v8 r1\Flash Programming Tool\Windows64>fptw64.exe -spibar
Intel (R) Flash Programming Tool. Version: 18.104.22.1681
Copyright (c) 2007 - 2014, Intel Corporation. All rights reserved.
Platform: Intel(R) Patsburg Chipset - Reserved DID 0x1D41
Reading HSFSTS register... Flash Descriptor: Valid
--- Flash Devices Found ---
EN25F64 ID:0x1C3117 Size: 8192KB (65536Kb)
SPI BAR: FED1F800
Well, I started over and did exactly what you said. I've edited my previous post with clickable images.
it realy beats me.
Now I've did the same but with a bootable usb stuck and the dos tools. Same result
Zitat von plutomaniac im Beitrag #21
That makes no sense, not possible. The full SPI image dump and the ME region dump taken from the same system without any reflashes in between should have the same ME region as far as settings are concerned. You must have confused some file with another.
No need to tag me with @username, I follow replies regardless.
sorry for the tagging.
Well, thats what I tought it should be.
if you open them, are those settings I mentioned different for you?
Because at first I was thinking I might need some glasses
I hope I'm doing it the right way.
full spi: fptw64.exe -d full.bin
me: fptw64.exe -d me.bin -ME
that's all I did. I ran 2 instances of fitc next to eachother and compared both the me.bin and the full.bin
unless I'm doing something wrong, I'm puzzled.
So I started over:
opened in fitc:
full.bin to the left, me.bin to the right:
Zitat von plutomaniac im Beitrag #19@plutomaniac
That's due to something you did recently. You flashed some SPI or ME region which has completely different settings. The previous files you provided (dump, backup, my cleanup fix) as well as the last ones (full = dump, x7909_PCI_0929_bios = backup) have the exact same settings. The me.bin dump is completely different so it's something you flashed recently. Restore back to the previous ME regions we were working with.
I think you might have misunderstand me.
Both the me.bin and the full.bin are dumps I took now from my running system.
first I did the full dump and after that I dumped only the me.
but fitc is showing different settings. the full spi is supposed to have the exact same me settings like the me dump right?
I noticed something weird.
If I only dump my me (fptw64.exe -d me.bin -ME) a lot of values (in fitc), are different then when I open a full spi dump in fitc.
Is this normal behaviour?
Because now, i'm a bit confused about what my real me settings are.
both files are in my drive:
me.bin and full.bin
for instance: the icc data - icc profile 0 - Fcim/BTM specific ICC registers are totaly different.
I'm a bit puzzled now.
I just got a reply from the manufacturer:
The me is disabled from within the bios, because some clients can't find the ME driver.
They will say our motherboard has a problem, so our engineer disablet it.
now they ask if I use the me.
Don't know what to answer realy :s
I did. But it's a chinese company.
Don't even know if the lady understands what I mean.
I requested them with a new bios because the autofan control (pwm) with preset temps and fanspeeds didn't work. It was 100% all the time.
The new bios was the so called solution their engineer had written...
I asked for a changelog but she told me that the only thing he changed was the fancontroll issue.
With the new bios, the fan turns slower but the preset temps and according fan speeds still don't work. So I don't have high expectations anymore.
The x79 board was €150 and that pulled me over the line to buy and try it.
I had a e5-2690 xeon for cheap out of an obsolete blade server.
@plutomanica: how did you compare them?
Well, I've opened the bios with amibcp. There is an me page under chipset. but in the bios it's hidden. It's set to visible in amibcp but I guess they use a bitmask to hide it. The same applies for the 1-core till 10-core turbo option. A lot of options are masked. Anyone here knows how to unhide them?
I've read something about extracting the setup ifr en looking for the options and then searching for the bitmasks with a hex editor. But I'm afraid that it goes beyond my knowledge.
I flashed back my old bios with the -bios option and now the me is functional again :s
In the new bios, they fixed the automatic fanspeedcontrol in bios but it seem to screw up the me :s
Zitat von plutomaniac im Beitrag #9
I just followed the cleanup guide and produced a ME region for you to reflash. Use "fpt -f me_fix.bin -me" followed by "fpt -greset" command.
thnx @plutomaniac. flashing went ok.
The -greset doenst work :(
Still the same message:
Could not set the globalReset bit
Current me state (0x1): bring up
The me is not in a functional state. cannot execute me reboot.
The me could not be reset from the program. The system requires a manual power off.
The poweroff didn't help either :(