Open rene-72 opened 2 months ago
@rene-72
Just to double check, did you move all the jumpers as required?
Hi, I got this board the E14 BB header has normally no jumper I placed a jumper on those 2 pins The ME/AMT FD override has 3 pins normally the jumper is on the 2 pins close to the chip above I moved it to the two lower pins close the sata ports.
The only thing I see it seems fpt wants to write on different adresses what is strange because I give the corect -A and -L parameters I also cannot program the BIOS from the files the backup.bat did make. ME seems to be no problem. What do I miss here. Also I havenot got the board in that special ME mode that allows full flash access.' Could you write your steps with photo's so I can see what should be shown on screen because following your written steps didnot work for me now. Also the system stays at 3.96 even after flashing the bios chip and that it throws errors. I really hope you can help me with my Z620
Hi
Did everything again after meblast j61_0396.bin I have done a warmboot the dosflash it worked this time after that reboot and did see the special amt mode Flashed the boot block 2013, nvme modded rom and restored ME and GBE from first backup. Reboot and yes I got it finally I can order xeon v2 chips
@rene-72
Happy to hear it worked on your machine!
You might have missed the password recovery jumper the first time, but not an issue anymore.
@rene-72
For v2, single chip Xeons - 1650v2, 1660v2, 1690v2, all enable clock boost through Intel Extreme Tuning Utility. Up to ~4.4Ghz.
In more stock config - 2667v2, 2673v2, or 2690v2 seem the beefiest.
Probably want 4 1866Mhz DDR3 DIMMs (PC3-14900R) of ~16GB each.
I am planning to use the e5-2697v2 dual and get 1866mhz ram 384gb should work I get me another z620 next month that will be build with the same config. I tested the z620 with esxi 8 and it works great even the two onboard nics show up on my z400 server the onboard nics is not supported I put a quad nic in that system to get supported nics
I am planning to use the e5-2697v2 dual and get 1866mhz ram 384gb should work
Well - looks like you have a solid plan there, will be fully stocked up ! :) Use PCIE4 nvme drives - they should fully saturate PCIE3 connection up to 3GB read/write.
More life for this excellently designed and built hardware - less e-waste
Do you know if tpm chip can be flashed to 2 0 and maybe me 9.0 or higher can be done ?
Do you know if tpm chip can be flashed to 2 0 and maybe me 9.0 or higher can be done ?
No, the chip on this board is v1.2 max. But I read there are cheap pcie boards out there with tpm 2 0 chips.
I saw on Z640 ME 9 flash area is a little bigger than on z620 - so don't recommend any experimenting with ME 9 :)
@rene-72
Did you get your v2 Xeons and new Z620s yet? What's happening on your side?
If you do need to reflash those, I wonder if you could flash the 2023 bootblock first, and then swap to v2 Xeon and try to flash the modded bios.
The question is whether 2.07 bios will totally refuse to boot on v2 Xeon, or it would just instruct you to press F1, and will proceed. If the process does work with v2 installed, that'd be the shortcut to flash the modded bios on the machine that already has v2 Xeon.
Just got two new z620 here v1 and v2 will try it what you ask for
Send from mobile phone
Op 3 okt 2024 20:27 schreef bibikalka1 @.***>:
@rene-72https://github.com/rene-72
Did you get your v2 Xeons and new Z620s yet? What's happening on your side?
If you do need to reflash those, I wonder if you could flash the 2023 bootblock first, and then swap to v2 Xeon and try to flash the modded bios.
The question is whether 2.07 bios will totally refuse to boot on v2 Xeon, or it would just instruct you to press F1, and will proceed. If the process does work with v2 installed, that'd be the shortcut to flash the modded bios on the machine that already has v2 Xeon.
— Reply to this email directly, view it on GitHubhttps://github.com/bibikalka1/HP_Z420_Z620_Z820_BOOTBLOCK2013_BIOS_mod/issues/4#issuecomment-2392056407, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARJ76G2T5TIXJDSX64WYXMDZZWEBRAVCNFSM6AAAAABOA5L5AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJSGA2TMNBQG4. You are receiving this because you were mentioned.Message ID: @.***>
@rene-72
Any luck having v2.07 bios boot into DOS on a v2 Xeon already installed? Would it run at all after complaining about the missing microcode, or not?
No 2.07 is no go with v2 processors
Send from mobile phone
Op 14 okt 2024 18:50 schreef bibikalka1 @.***>:
@rene-72https://github.com/rene-72
Any luck having v2.07 bios boot into DOS on a v2 Xeon already installed? Would it run at all after complaining about the missing microcode, or not?
— Reply to this email directly, view it on GitHubhttps://github.com/bibikalka1/HP_Z420_Z620_Z820_BOOTBLOCK2013_BIOS_mod/issues/4#issuecomment-2411757525, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARJ76GYRHLWPBK2ALY7MCELZ3PX5FAVCNFSM6AAAAABOA5L5AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJRG42TONJSGU. You are receiving this because you were mentioned.Message ID: @.***>
No 2.07 is no go with v2 processors
@rene-72
OK, thanks! So it gave you missing microcode, and refused to boot at all? No option to press F1 and continue? Any pictures you might have taken?
@bibikalka1 Additional info :
Just did 2x Z420 and a Z620.
The 2 with a v2 processors never accepted the v2.07 bios constantly giving the : "Error ! System ROM image is invalid" message.
After many tries, I used the v1 processor turn by turn and everything worked perfectly.
Note : The workstations with the v2 CPU pre-installed refusing the bios v2.07 step were running bios v3.65 and v3.96.
@rene-72
The 2 with a v2 processors never accepted the v2.07 bios constantly giving the : "Error ! System ROM image is invalid" message.
Is this when you were trying to flash 2.07, or after you flashed 2.07 it refused to boot with this message? I guess, will all the jumpers set correctly too?
Note : The workstations with the v2 CPU pre-installed refusing the bios v2.07 step were running bios v3.65 and v3.96.
Interesting! I guess if it does not flash 2.07, maybe trying to revert first to v3.5, and try it there. It's possible there are v2 checks during the flashing process.
@rene-72
The 2 with a v2 processors never accepted the v2.07 bios constantly giving the : "Error ! System ROM image is invalid" message.
Is this when you were trying to flash 2.07, or after you flashed 2.07 it refused to boot with this message? I guess, will all the jumpers set correctly too?
It was while trying to flash to 2.07.
Jumpers were Ok since the flashes worked with just swapping the v1 CPU in.
Thanks for the guide !
@rene-72
OK - I see your point, there are google results for this specific message on HP forum! It does happen from time to time!
If you ever need to reflash v2 again, please try installed v3.50 first. Then reboot, and try the procedure when going to v2.07. The thinking here is that v3.50 may not have the same verification code.
@bibikalka1 Hi, i cannot get into amt special mode. I can flash the ME8 After that I use dosflash to program 2.07 but that fails Error! System Rom image is invalid Also fpt flash fails :-(
See pictures.
Can you tell me how I must continue and how I get 2.07 flashed to update the final 396 rom with BB2013 ?
I use: dosflash /f flshuefi.cpu J61_0207.bin cannot find other method for dosflash