Fujitsu D3348-A23 Bios mod, menu unlock

Hello, I have read everything I could on this forum and elsewhere, I added the new Microcodes with UBU, did not update the SATA drivers because after contrasting performance between the updated and those that brought the original bios, I did not notice any difference in performance. I added the Rebar driver, and it works with the usual problem of no image until the Windows login.
My problem is to unlock the hidden menus of the BIOS, with AMIBCP, you can unlock a hidden menu called Admin in the Advanced menu, and it would be a breakthrough if it did not have the problem that when unlocked; with rebar activated windows hangs a few seconds after login.
In AMIBCP you can also see an IntelRCSetup tab that is hidden and seems to have everything that interests me; the configuration of RAM timings and voltage, and IIO settings where you can activate the PCIE bifurcation.
I have tried with UEFI Editor, but I have not been able to understand how it works.
If someone could help me by enabling access to these two menus, I would appreciate it very much.
Thank you very much for reading.
d3348_current.zip (4.0 MB)

hikaruichijo.zip 4MB on Mega.

========== Section_Freeform_subtype_GUID_setupdata_AMITSE_body.bin ==========
Onboard Devices Configuration | QuestionId 0xD: Ref from 0800 to 4100, Onboard Devices Configuration to Intel RC Setup  Configuration
Admin | QuestionId 0x2791: Access Level 21 -> 01

========== Section_PE32_image_Setup_Setup.sct ==========
Admin | Unsuppressed
1 Like

Impressive, that was really fast, it works perfectly.
Thank you very much.
Any possible solution to the problem of no image during boot with Rebar enabled? I have not been able to find anything, I know it is a common problem, but it strikes me that another X99 motherboard I have, a Jingsha X99-D8, does not have this problem.

Disabling Above 4G decoding may help. But then you’ll be limited to smaller bars.

1 Like

It seems to me that when I activate rebar, the bios does not detect the graphics card and boots as if it were not there, then the OS takes over and starts the graphics card. I wonder why the bios does not recognize the graphics card. What changes the rebar driver so that the bios can’t recognize the graphics card. Maybe the routine in the bios looking for the graphics card, looks for it at a specific memory address and when rebar is activated, the memory address where the graphics card bios shows up changes. I have no idea how the graphics card startup routine in the bios works, but it might be something like that?
Could it be that the bios does not find the card’s GOP after enabling rebar?
The Graphics card is an ASUS RX 6700 TUF.

I have a Fujitsu D3128-B25 (X79) with an XFX RX580 and when I enable Vbios boot on Uefi only, it makes the same beeps as the D3348 with rebar enabled, but at the end it automatically disables Vbios Uefi boot and sets it to Legacy. I tried Radeon pro W2100 and with that graphics card if you can activate the Vbios start in Uefi only.