Forum RSS Feed Follow @ Twitter Follow @ Twitter

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Asus Rampage V Edition 10 Supports ES CPU e5-2699 v4
#21
(02-11-2018, 08:20 AM)DeathBringer Wrote: Show a new photo of modded BIOS page with version.

Hi,

I'm flashed your second mod, and NO SCREEN only looping Qcodes waited 5minutes and more to boot but fail.

You can watch this video : https://drive.google.com/open?id=17FuC0m...uhacVL3s8z

Thank you.
find
quote
#22
Well, flash back BIOS version 0502
find
quote
#23
(02-11-2018, 08:24 AM)DeathBringer Wrote: Well, flash back BIOS version 0502

Hi,

Done flashed original 0502 version.

   
find
quote
#24
Try to flash my 3rd mod.
find
quote
#25
(02-11-2018, 08:59 AM)DeathBringer Wrote: Try to flash my 3rd mod.

Hi,

Flashed your 3rd mod, boot OK, photo attached.

Still stuck on Q19 error after quit bios.

Thank you.

   
find
quote
#26
So no more ideas.
find
quote
#27
Hi,
Thank you for all DeathBringer.
I have one question.
This problem is software based like BIOS right?
Asus will fix this issue if do?
Thank you.
find
quote
#28
Asus will not do anything about it.
find
quote
#29
(02-11-2018, 10:37 AM)DeathBringer Wrote: Asus will not do anything about it.

I have a similar issue of combination form RAMPAGE V EXTREME with XEON 2680 V4 (QHV7)

restart post fail at Q code 19, I had to use reset button on each bootup

but I find out later ASUS board, for example, E10PE-D8-WS did list on supported MB in that vender's description page

hance I start my little research on this boards' BIOS use MC extractor I find out something

[Image: 46340380651_40d45abb90_b.jpg]

For the E10PE-D8-WS support of XEON V4 ES (QHxx)processor based on that vendor start from version 3204

 it can be easily discovered the difference are adding microcode for #406F1 variant in version 3204 (see upper left two pics)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

then on R5E's side, starts it's supports multiple XEON V4 and some V3 processors form version 1701 (according to ASUS page)

BUT I did not find ANY new microcode variant added form 1601 to 1701 for R5E (forget to make the snapshot for that, but did check thou)
(is that possible add CPU support without new microcode variant in BIOS ??)

Not until v 2301 to 3008 ASUS did add microcode for #406F1 and #406F2 variant "Improve system stability." by ASUS

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Back to microcode compare for two boards 

I find out that there is a one variant #306F0 microcode did show off in beginning of E10PE-D8-WS BIOS but don't appear in R5E

my theory was that by adding variant #306F0 u-code (or some BIOS MOD) into some X99 board can't support XEON V4 ES (QHxx) processor

could be possible to fix this issue? but sad for me lake skill for bios modding (UBU, UEFITool versions make me sick ) 

is that a possible lead for this research?


BTY: there are some information from CPU world for CPUID #306F0, #306F1, #306F2, #406F0 and #406F1

 #306F0> guess early Haswell ES
not found 

 
 #306F1> Haswell ES shard spec (QExx)
http://www.cpu-world.com/cgi-bin/CPUID.pl?MANUF=&FAMILY=&MODEL=&SIGNATURE=198385&PART=&ACTION=Filter&STEPPING=


 #306F2> Retail Haswell chips and QS (QFxx QGxx)
http://www.cpu-world.com/cgi-bin/CPUID.pl?MANUF=&FAMILY=&MODEL=&SIGNATURE=198386&PART=&ACTION=Filter&STEPPING=


 #406F0> guess early Broadwell ES (QHxx) we are dealing with (confirm by my test with it on R5E)
http://www.cpu-world.com/cgi-bin/CPUID.pl?MANUF=&FAMILY=&MODEL=&SIGNATURE=263920&PART=&ACTION=Filter&STEPPING=


 #406F1>  Retail Broadwell chips and QS (QKxx) 
http://www.cpu-world.com/cgi-bin/CPUID.pl?MANUF=&FAMILY=&MODEL=&SIGNATURE=263921&PART=&ACTION=Filter&STEPPING=
find
quote
#30
craftoscar
Your Xeon E5-2680 v4 (QHV7) and micenx's Xeon E5-2699 v4 (QHUP) has the same CPUID=0x406F0
So it's not a microcode problem.
find
quote


Forum Jump:


Users browsing this thread: 1 Guest(s)
Expand chat
Expand chat
Expand chat

To join us in the community live chat, please register or log-in