@Lost_N_BIOS

Zitat von Lost_N_BIOS

---

@opencomputeguy - this is second reply I've posted for you in past hour or so, no need to post in multiple location for the same issue.
Please link me to the stock BIOS download from manufacturer for the board you have, and tell me what exact CPUID's you want added and I can make you BIOS, if that fails then you need more than just microcode mod to use those CPU's

---

Ok so not to post in two threads I'll just post in this one.

There is no longer an official download of this bios from the manufacturer, they consider it obsolete so they have removed everything from their site for this server.
The latest bios from Wiwynn is EP_P09RG.02 that I downloaded a couple of years ago.
The bios I updated works fine as long as I do not try to add 306E4, 306E3, 306E2 ect.
306E4 cpuid is the one I am trying to get to work.

It's not real important to keep the 206E7, 206E6 or 206E5 or lower since I do not have a problem updating the bios with the latest version of those and if I need to swap in the V1 cpu's I can just reflash with the updated bios that does work with the v1 cpu's..

@opencomputeguy - Thanks for more info. So, when you do add 306E4, 306E3, 306E2 does this break the BIOS totally, you can't use it with the other CPU's too? If yes, then it's just failed BIOS mod causing it to be broken BIOS.
You did test your mod BIOS with the original older CPU's correct? I think you said you did on your post at #250, but unsure what all that applied to since you were trying a few mod BIOS there and few methods, so it's not clear if you tested each post edit with the V1 CPU's or not.

Fan ramp up usually means ME FW issue, such as failed ME FW or corrupted ME FW etc, in this case it may mean you need to use different/upgraded ME FW for the Ivy (which is common and often has to be done by the manufacturer if higher major ME FW version # is required for CPU's you are wanting to use)
For this, you will need to research and find what ME FW is required for the CPU's you are trying to use, google will usually lead you to a good answer on this. In some instances you may even need to disable ME FW via reserved bit using FITc ME tool, but if this is case for your V2 CPU's I'm sure you'll find mention of it in your research.
I suspect you need a higher ME FW version, this was common with many Sandy >> Ivy updates, and first requires a BIOS with initial major ME FW update from the manufacturer before we could further update that later on (Due to many modules also needing updated at same time, not just ME FW region)

Please test both of these BIOS with V1 CPU and 306E4 V2 CPU, what is outcome on each, with each CPU If fan ramp up on both BIOS, and no boot on Ivy only, then it's a ME FW issue
http://s000.tinyupload.com/index.php?fil...710228094167192

I see this is using SPS FW V2, so not same as V7 need update to V8 for Ivy type issue, but may need update to SPS V3 for Ivy

plutomaniac Do you know what is required for E5 Xeon Sandy V1 >> E5 Xeon Ivy V2?

@Lost_N_BIOS

First test.

EP_P09RG.14.bin - boots with V1 cpu's into the bios and then into windows 7 fine.
-- does not boot with V2 cpu's, powers on, cpu activity led flickers once, fans ramp up to the
usual slow speed, lan power light at the rj 45 port lights up and flashes normally.

EP_P09RG.19.bin - boots with V1 cpu's into the bios and then into windows 7 fine.
-- does not boot with V2 cpu's, powers on, cpu activity led flickers once, fans ramp up to the
usual slow speed, lan power light at the rj 45 port lights up and flashes normally.

Fan not at full speed? Ramp up means ramp up, not "usual slow speed" that sounds so confusing
Anyway, this is likely due to ME FW or other possible changes also need made in BIOS, that I am not aware of right now. If you research and find info I can do most any mod, but I need to know what needs done here first, if it's possible.

I found many posts from some guy at serverthehome forums, and one of the threads he was doing mod BIOS, and had this board/BIOS and was supposed to test V2 mods, but I looked all the way to end of thread and it wasn't clear if he had it working or not (unfamiliar with their terms/references etc)
Maybe you can join, and PM that guy, and see if he ever did actually get it working with V2, if he did ask him either for the BIOS or for what needs changed and then I can change it for you.
Here is the thread, member Klee was discussing - https://forums.servethehome.com/index.ph...ld.15021/page-4

EFI AMD GOP Driver - 1.68.0.15.50_signed (>1.67.0.15.50_signed)

New Realtek UEFI Undi DXE rom 2.049 (and accompanying new driver).

Unknown Lx Killer Metwork LAN version.
(Metwork? :D)

error: bad_alloc

@Fernando:
No, not identical. I look at a lot of BIOS. I don't remember which is which.
1st is MSI motherboard, 2nd is Lenovo ThinkPad tablet. Maybe.

@SoniX how are you? 1,5 month passed, at least microcode database have to be updated. How are your eyes? Did you get well?

Fernando you may delete this message, I know, my personal message to SoniX not reached, or he is not capable of reading. :(

OROM VBIOS Stoney - 015.049.000.017.000000 (>015.049.000.016.007161)
OROM VBIOS Picasso - 016.002.000.010.038962 (>016.002.000.010.000000)
OROM VBIOS Mullins - 015.042.000.003.000000 (>new item)
EFI Marvell SATA AHCI - 1.1.0.1029 (>1.1.0.1020)
EFI Marvell SATA RAID - 1.1.0.1026 (>1.1.0.1020)