Missing 4G decoding on Gigabyte Z97X-Gaming 3 #14

BartekJablonski · 2022-11-11T10:32:06Z

MOBO: Gigabyte Z97X-Gaming 3
BIOS: F8e (not available on GB page, i got it from Support. This bios add TPM 2.0)
CPU: Intel Xeon E3-1285L v4
GPU: RX 6900XT
CSM disabled, SecureBoot enabled, TPM 2.0 Enabled

Im curious to check if Re-Bar can work on my motherboard using this instruction:
https://github.com/xCuri0/ReBarUEFI/wiki/Enabling-hidden-4G-decoding

Im stuck on 4 step. I find 4G Decod using UEFITOOL, extracted body, next i used [IRFExtractor_0.3.6] to save output file.
Output file doesn't contain "4G Decod".

I attached original bios file and txt output.

Z97XGAMING3.zip
Section_Freeform_subtype_GUID_97E409E6-4CC1-11D9-81F6-000000000000_Setup_Setup_body IFR.txt

sidex15 · 2022-11-12T01:16:41Z

seems like the it is not included in the setup configuration in the bios... and only counted as a Bios String...

BartekJablonski · 2022-11-12T08:14:54Z

I checked older bioses. F8d and F7 do not include 4G Decod as a string. F6 have one mention, but still not included in txt output.

ysc3839 · 2022-11-25T13:30:59Z

My motherboard is MSI B75A-G43. GPU-Z says above 4G decode is disabled and I found "Above 4G" in step 1 but nothing in step 4. Is this mean there's is no way to make rebar work?

magicalz · 2022-12-21T07:47:00Z

My Gigabyte B85M-D3H(rev.1.2) has the same issue. "4G Decod" string exist but IRFExtractor can not extract it to txt.

magicalz · 2022-12-25T07:29:41Z

Update: when I locate the offset in hex-editor which has been found in UEFITool, I can see a string "Above 4G Decoding. Enables or Disables 64bit capable Devices to be Decoded in Above 4G Address Space".

It looks like just a description string but not a configuration.

97E409E6-4CC1-11D9-81F6-000000000000_Setup_Setup_body.zip

BTW, actually the Resizable BAR is working(<= 1G) after I added the FFS module, even if Above 4G decoding is disable.
My modded bios: modded_bios_F3_ReBar_patched.zip

BartekJablonski · 2023-02-15T11:35:43Z

I did the same thing. Added FFS module unlock ReBar <= 1GB without 4G Decoding.

I will try do patch for Broadwell

BartekJablonski · 2023-02-16T08:28:37Z

Unfortunately, I have not been able to get ReBar to run above 1GB. Nevertheless I have a higher minimum FPS.

NoUserNameForYou · 2023-03-04T18:14:24Z

A guy on winraid has added options from strings into his settings

https://winraid.level1techs.com/t/add-option-in-ami-uefi-bios-menu-how-to/31609/15

Perhaps we can do the same for 4g decode?

xCuri0 · 2023-03-06T04:50:54Z

@NoUserNameForYou Can you try this in grub-mod-setup_var

setup_var 0x3 0x0
Reboot
setup_var 0x3 0x1
Reboot and see if you have 4G decode working

Make sure you're running patched BIOS also before doing this. There's also another method directly manipulating PCH and PCI setup variables to enable 4G decoding which we can try if this doesn't work

xCuri0 · 2023-03-07T08:17:39Z

@NoUserNameForYou don't really think anything more can be tried other than swapping pcihostbridge or maybe pcibus modules with a similar motherboard that supports 4g decoding.

asm patching is complicated because it would require addition of code which isn't easy

BartekJablonski · 2023-03-18T18:12:52Z

The Grub mod setup var method did not unlock 4G Decoding. I also discovered a strange bug with Unreal Engine games. When I have ReBar enabled for 1GB, games on UE can only allocate 1GB of VRAM, causing performance to drop dramatically. It affected Sea of Thieves, Contraband Police and Chernobylite, propably every UE4 games. Other engine e.g: Dying Light 2 gain performance and the game can allocate more than 6+GB VRAM, as it should.

EDIT: I did more tests. Other ReBar size for example manual 256MB, 512MB causing 256MB and 512MB max allocation of memory in Unreal Engine games.
Im thinking about TOLUD method, to get 2GB BAR, but now im not sure now.

xCuri0 · 2023-03-18T18:22:09Z

@BartekJablonski I've seen others report similar issues on Polaris GPUs but didn't know it happened on RDNA too. Also 2GB does have this issue too just that it will happen at 2GB VRAM.

Sucks that AMD doesn't allow for per game rebar like NVIDIA so this issue could be mitigated

BartekJablonski · 2023-03-18T18:26:55Z

It was a fun adventure to squeeze the last sweat out of that Broadwell. I am glad that I was able to participate in this :)

xCuri0 · 2023-03-18T18:28:18Z

@BartekJablonski You mention 256mb causes the issue, but isn't that the default size no rebar ?

BartekJablonski · 2023-03-18T18:49:56Z

I'll straighten the whole thing out a bit
In ReBar 9 and 10 AMD Settings says that ReBar is supported and I can turn it off via drivers. Disabling it will allocate up to 256MB, although GPU-Z will not change the BAR0 and BAR1 values
ReBar State: 0 (disabled). AMD Settings: ReBar Unsupported. UE Games can allocate all memory.
ReBar State: 8 (256MB). AMD Settings: ReBar Unsupported. UE Games can allocate all memory.
ReBar State: 9 (512MB). AMD Settings: ReBar Supported. UE Games can allocate 512MB Only.
ReBar State: 10 (1024MB). AMD Settings: ReBar Supported. UE Games can allocate 1024MB Only.
Also check out the pics of what it looks like.
https://imgur.com/a/Zdr5n52

EDIT: I'm curious about the difference in performance with ReBar 8 and ReBar 0. The difference is in the BAR1 values.

BartekJablonski · 2023-03-27T10:00:16Z

Source 2 games are also affected to this VRAM allocation bug.

BartekJablonski · 2023-05-07T08:29:27Z

Unity Engine game are also affected to this VRAM allocation bug, but i find out workaround for this. DXVK fixed it. Contraband Police (Unity Game) had this bug. I tried DXVK and now game can utilize more than 1GB VRAM :p
In general, the game itself runs better on DXVK, even without ReBar enabled

BartekJablonski · 2023-05-07T17:34:30Z

Yeah, DXVK also fixed allocation bug in Sea of Thieves (UE4 game)

xCuri0 · 2023-05-07T18:05:42Z

@BartekJablonski dxvk often reduces performance tho, we are enabling rebar to get more fps

BartekJablonski · 2023-05-07T18:14:00Z

I know that, but it depends on hardware. Obviously im cpu bottlenecked and take f.e Contraband Police.
Native DX11 65FPS -> DXVK 85FPS -> DXVK+ReBar 1GB 92FPS
Sea of Thieves Native VS DXVK+ReBar 1GB gave very similar results.
I wanted to share this finding

ghost · 2023-08-21T12:08:40Z

DSDT.aml.zip
Hi Everyone, need some help with DSDT. (my motherboard doesn't have 4G decoding, and would like to attempt with Linux)
I am getting errors after doing iasl DSDTMod.dsl, initially it was just a Syntax error, but after I removed ARG0, now I am getting 1 error, but a bunch of warnings and remarks. I'm not sure If I did anything wrong or how about to fixing this. I've attached the files. If anyone can help me or guide me through this is appreciated.

I7-4770 Haswell CPU
Asus Z87-A motherboard

Thanks!

CNduan · 2023-10-06T01:21:05Z

试试 UEFITool 替换附件中 pcibus模块我的主板用的是同样技嘉品牌Z97-HD3 2.1 可以打开1G 以上 Bar 这个模块是我从华擎Z97-EXTREME 中已启用 Bar 中提取这似乎是技嘉主板PCIBUS模块的问题地址是：https://winraid.level1techs.com/t/request-resizable-bar-added-to-asrock-z97-extreme-6-v2-80a/91036/2
PCIBUS.zip

xCuri0 · 2023-10-23T15:34:27Z

@xYuuna go to the lines mentioned and remove Arg0, it says this at the bottom of the DSDT editing wiki page.

xCuri0 · 2023-10-23T15:55:38Z

If anyone wants to try a project of getting 4G decoding on these motherboards here's what you have to do

Here are comparisons of BIOS with vs without 4G decoding

Gigabyte B75M-D3H (Good)

ASRock IMB-180 (Bad)

You can see the check for 4G decoding DAT_800028e9 == '\x01' on the B75 used to increase the maximum address from 0xffffffff (4GB) to the maximum 64-bit for AllocateMemorySpace (0x20)

Also in the main function you can see the AddMemorySpace (0x18) doesn't add the Above 4GB MMIO region.

Gigabyte B75M-D3H (Good)

ASRock IMB-180 (Bad), there's an error with the disassembly on 32-bit AddMemorySpace but it doesn't matter.

These are the hooks needed, you can find alot of examples on hooking UEFI services.

AddMemorySpace hook

Check if it is type 3 (MMIO) to additionally add another AddMemorySpace call (make sure to use the original function!) which extends from top of memory (end of last type 2 region) to 64GB, there have been issues trying to patch Haswell to use full 512GB so stick to 64GB for now. Here is UEFI memory map which should help understanding this

It should check if the new memory space was already added as the function gets called multiple times, if so it should not add it again.

AllocateMemorySpace hook

Check an NVRAM variable which can be configured by user, similar to ReBarState (can also take the CMOS reset protection from ReBarUEFI too) and check if enabled. If so, when type is 3 (MMIO) and maximum address equals 0xffffffff (4GB) change it to 0xffffffffffffffff (maximum UINT64).

This will allocate resources in the 64-bit region added by the previous hook. It needs to be user configurable with NVRAM variable to allow CSM to be disabled in BIOS before.

Last (and easiest) step would be adding the DSDT for it which you can find in the wiki.

@sidex15 @ysc3839 @magicalz @NoUserNameForYou @xYuuna @AbraxasVi @LordAdo96

jakeman2048 · 2024-03-03T20:00:44Z

@xCuri0 :)
MOBO: Gigabyte Z97X-UD5H-BK
BIOS: F8
CPU: Intel i5-4670K
GPU: Intel A380

I'm also unable to find the 4G Decode option with UEFITool. The stock DSDT seems to account for 4G Decoding, but when I bypass that M64L conditional I get the expanded root bus in the OS, but anything above 1G resizebar won't POST. I'm guessing that M64L bit needs to be actually toggled somehow, instead of bypassed in order for the PCIBus to work? Either that or find/hack together a PCIBus module?

Stock DSDT section:

                If ((Local1 >= 0x07D9))
                {
                    If ((M64L == Zero))
                    {
                        CreateDWordField (BUF0, \_SB.PCI0._Y1E._LEN, MSLN)  // _LEN: Length
                        MSLN = Zero
                    }
                    Else
                    {
                        CreateQWordField (BUF0, \_SB.PCI0._Y1E._LEN, M2LN)  // _LEN: Length
                        CreateQWordField (BUF0, \_SB.PCI0._Y1E._MIN, M2MN)  // _MIN: Minimum Base Address
                        CreateQWordField (BUF0, \_SB.PCI0._Y1E._MAX, M2MX)  // _MAX: Maximum Base Address
                        M2LN = M64L /* External reference */
                        M2MN = M64B /* External reference */
                        M2MX = ((M2MN + M2LN) - One)
                    }
                }

My attempt at bypassing:

               If ((Local1 >= 0x07D9))
                {
                        CreateQWordField (BUF0, \_SB.PCI0._Y1E._LEN, M2LN)  // _LEN: Length
                        CreateQWordField (BUF0, \_SB.PCI0._Y1E._MIN, M2MN)  // _MIN: Minimum Base Address
                        CreateQWordField (BUF0, \_SB.PCI0._Y1E._MAX, M2MX)  // _MAX: Maximum Base Address

                        // 39-bit for Haswell and up
                        M2MX = 0x8000000000 - One
                        If ((TUUD >= 0x1000))
                        {
                            M2MN = (TUUD << 0x14)
                        }
                        Else
                        {
                            M2MN = 0x100000000
                        }
                }

Joris-truly · 2024-03-24T14:08:08Z

MOBO: GA-X99-Gaming 5
BIOS F23c
CPU: Intel i7-5930K
GPU: RTX 3070

Same issue, stuck on finding the '4G Decod in txt' step.
I appreciate the support and write-up above, @xCuri0, but it's a bit too impenetrably written for non-programmers. I'm unsure where to start :)

I've added my extracted text. Perhaps it could serve as an example of how to trace the '4g decod' flag?

Section_PE32_image_Setup_Setup_body.efi.0.0.en-US.ifr.txt

ziddey · 2024-04-02T20:24:33Z

@jakeman2048 aren't you then missing M2LN = ((M2MX - M2MN) + One)

Also, after removing the stray Arg0, I still can't compile:

PS D:\Work> D:\Programs\iasl.exe -ve .\DSDT.dsl

Intel ACPI Component Architecture
ASL+ Optimizing Compiler/Disassembler version 20230628
Copyright (c) 2000 - 2023 Intel Corporation

./DSDT.dsl   9112:         Device (SDMA)
Error    6141 -   Missing dependency ^  (Device object requires a _HID or _ADR)

./DSDT.dsl   9161:         Device (I2C0)
Error    6141 -   Missing dependency ^  (Device object requires a _HID or _ADR)

./DSDT.dsl   9282:         Device (I2C1)
Error    6141 -   Missing dependency ^  (Device object requires a _HID or _ADR)

./DSDT.dsl   9400:         Device (SPI0)
Error    6141 -   Missing dependency ^  (Device object requires a _HID or _ADR)

./DSDT.dsl   9481:         Device (SPI1)
Error    6141 -   Missing dependency ^  (Device object requires a _HID or _ADR)

./DSDT.dsl   9574:         Device (UA00)
Error    6141 -   Missing dependency ^  (Device object requires a _HID or _ADR)

./DSDT.dsl   9655:         Device (UA01)
Error    6141 -   Missing dependency ^  (Device object requires a _HID or _ADR)

./DSDT.dsl   9748:         Device (SDHC)
Error    6141 -   Missing dependency ^  (Device object requires a _HID or _ADR)

ASL Input:     ./DSDT.dsl -  596415 bytes   7624 keywords      0 source lines

Compilation failed. 8 Errors, 134 Warnings, 169 Remarks
No AML files were generated due to compiler error(s)

Is it safe to force with -f? Or should I be doing something with these:

Scope (_SB.PCI0)
{
    Device (SDMA)
    {
    }
}

Since I'm using a 4gb rx480, I was hoping reducing tolud would be enough for 2gb rebar. I have tolud set to 1gb (minimum option), but still no post :(

ZLHuo · 2024-05-02T15:47:49Z

试试 UEFITool 替换附件中 pcibus模块我的主板用的是同样技嘉品牌Z97-HD3 2.1 可以打开1G 以上 Bar 这个模块是我从华擎Z97-EXTREME 中已启用 Bar 中提取这似乎是技嘉主板PCIBUS模块的问题地址是：https://winraid.level1techs.com/t/request-resizable-bar-added-to-asrock-z97-extreme-6-v2-80a/91036/2 PCIBUS.zip

I've attempted to replace the pcibus module in the Z97-HD3 firmware; however, I'm still unable to set BAR larger than 1G. Could you provide a more detailed explanation on how to successfully implement this?

xCuri0 · 2024-05-02T16:06:11Z

@ZLHuo there a bunch of other modules too not just pcibus

i think pcihostbridge and some sa related module.

i dont think it will be easy to implement tbh

ZLHuo · 2024-05-02T16:54:29Z

@xCuri0
I understand, there's a lot of work to be done.
Achieving a BAR size of 1 GB is truly satisfying. Thank you for your exceptional project!

SaulGoodman1337 · 2024-05-14T08:39:00Z

@ZLHuo there a bunch of other modules too not just pcibus

i think pcihostbridge and some sa related module.

i dont think it will be easy to implement tbh

Hi,
I have a GA-Z97N-Gaming 5 here that I would like to use. I can't quite get my head around the patching here yet.
Can you tell me roughly whether it works with my board? I was able to add the module to the bios, but I've already failed with the 4G.
I can't find anything with UEFITool. Will DSDT patching help me here?
I am not planning to use windows, only Linux.

xCuri0 · 2024-05-14T13:03:32Z

if you're using linux you don't need to even flash rebardxe, there's a linux section on dsdt patching wiki just follow that

ivan49k · 2024-06-01T09:03:09Z

@xCuri0 Can you tell me about method directly manipulating PCH and PCI setup variables to enable 4G decoding?

xCuri0 · 2024-06-01T12:55:42Z

@ivan49k someone tried and it doesn't work, the uefi has been built without the code for 4g decoding.

Shranobxtha · 2024-11-27T15:56:16Z

@xCuri0 I am able to reach till here by following the guide, I'm using the motherboard GA-H81M-DS2 rev 3.0, couldn't enable Above 4G decode through grub tho sadly.

geotaxho · 2024-12-08T21:32:54Z

I have the same mb and result as @Shranobxtha. However i found above 4g in grub but changing it seems do no effect in gpu-z report (tried both setupvar/setupvar3).
I also found somebody else with a same mb who successfuly enabling above 4g decoding, but i dont understand what he mean with replacing the pcibus and the PciHostBridge.
Can anybody help? i attached grub txt and my patched bios in case.

#231
5.bin.1.0.en-US.ifr.txt
REBAR.zip

Shranobxtha · 2024-12-12T13:46:46Z

@geotaxho I got the same result again with a different motherboard this time with an MSI-H81M-P33, I swapped my board with this cause it lets me set all core multipler.

GTX1080Ti11G · 2025-01-08T07:32:47Z

Just thought I'd chime in here as I'm on a haswell platform as well. I own a Gigabte Z87X-OC. For me I had 4G Decod visible in the body, it was called Memory Remap in the extracted text file at 0x2FE offset. It was also set to enable by default.

I compiled the DSDL using the steps, and it compiled successfully. My bios has both the nvme & rebar dxes. I proceeded to use the UEFI patches and then flash the bios, it surprisingly worked.

Above 4G Decoding is now enabled, I don't have a rebar gpu to test yet, but if I do in the future I'll be sure to update it in the list of working motherboards.

Large Memory in device manager was not visible prior to all this.

yonexsp11 · 2025-01-10T20:32:56Z

MOBO: Gigabyte Z97X-Gaming 3 BIOS: F8e (not available on GB page, i got it from Support. This bios add TPM 2.0) CPU: Intel Xeon E3-1285L v4 GPU: RX 6900XT CSM disabled, SecureBoot enabled, TPM 2.0 Enabled

Im curious to check if Re-Bar can work on my motherboard using this instruction: https://github.com/xCuri0/ReBarUEFI/wiki/Enabling-hidden-4G-decoding

Im stuck on 4 step. I find 4G Decod using UEFITOOL, extracted body, next i used [IRFExtractor_0.3.6] to save output file. Output file doesn't contain "4G Decod".

I attached original bios file and txt output.

Z97XGAMING3.zip Section_Freeform_subtype_GUID_97E409E6-4CC1-11D9-81F6-000000000000_Setup_Setup_body IFR.txt

Hi,

Did you ever figure it out? I have th esame board and am anbout to junk it as I can;t get it to work.

It keeps reverting back to th ebackup BIOS file after not being able to boot

GTX1080Ti11G · 2025-01-11T15:40:01Z

@yonexsp11 I took the bios in the zip of the first post F8e, the 4G is located at the offset 0x309. It is enabled by default, you can try the setup_var offset method to see if it works, and whether you get Large Memory enabled in Control panel.

Else you can try to flash the bios I attached, I added the UEFI patches, patched the DSDT and I added the ReBar dxe to it. This is onto the same bios shared in the OP.
modZ97XGaming3.zip

yonexsp11 · 2025-01-12T05:33:09Z

Thx! I will give it a try & let you know. The challenge continues! Cheers, Ken./

…

On Sat, 11 Jan 2025 at 10:40, GTX1080Ti11G ***@***.***> wrote: @yonexsp11 <https://github.com/yonexsp11> I took the bios in the zip of the first post F8e, the 4G is located at the offset 0x309. It is enabled by default, you can try the setup_var offset method to see if it works, and whether you get Large Memory enabled in Control panel. 4goffset.JPG (view on web) <https://github.com/user-attachments/assets/ab82cce8-44eb-41c6-99d2-6a1a7fe7cb15> Else you can try to flash the bios I attached, I added the UEFI patches, patched the DSDT and I added the ReBar dxe to it. This is onto the same bios shared in the OP. modZ97XGaming3.zip <https://github.com/user-attachments/files/18386354/modZ97XGaming3.zip> — Reply to this email directly, view it on GitHub <#14 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BOMIPINK7J4OAVMPOPG3FQD2KE3OTAVCNFSM6AAAAABSTF2DWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBVGMYDMMRWHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

yonexsp11 · 2025-01-15T02:12:51Z

Alas that bricked my MB and it reverted back to F6 after failing to boot, even without the Video card installed in the machine. I think the modded FM that was posted that you used as a base is messed up. The stock F8e is probably a better bet. Cheers, Ken./

…

On Sat, Jan 11, 2025, 10:40 AM GTX1080Ti11G ***@***.***> wrote: @yonexsp11 <https://github.com/yonexsp11> I took the bios in the zip of the first post F8e, the 4G is located at the offset 0x309. It is enabled by default, you can try the setup_var offset method to see if it works, and whether you get Large Memory enabled in Control panel. 4goffset.JPG (view on web) <https://github.com/user-attachments/assets/ab82cce8-44eb-41c6-99d2-6a1a7fe7cb15> Else you can try to flash the bios I attached, I added the UEFI patches, patched the DSDT and I added the ReBar dxe to it. This is onto the same bios shared in the OP. modZ97XGaming3.zip <https://github.com/user-attachments/files/18386354/modZ97XGaming3.zip> — Reply to this email directly, view it on GitHub <#14 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BOMIPINK7J4OAVMPOPG3FQD2KE3OTAVCNFSM6AAAAABSTF2DWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBVGMYDMMRWHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

GTX1080Ti11G · 2025-01-15T15:45:50Z

Sorry to hear that, As per my understanding, there is no stock F8e. The one posted in the OP is a modified F8d with just TPM enabled. I can try working off the F8d from the motherboard's page if you'd like to try again.

yonexsp11 · 2025-01-15T16:45:08Z

Yes, please!

…

On Wed, Jan 15, 2025, 10:46 AM GTX1080Ti11G ***@***.***> wrote: Sorry to hear that, As per my understanding, there is no stock F8e. The one posted in the OP is a modified F8d with just TPM enabled. I can try working off the F8d from the motherboard's page if you'd like to try again. — Reply to this email directly, view it on GitHub <#14 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BOMIPILFVKBA5PZ6HPO37RL2KZ7ENAVCNFSM6AAAAABSTF2DWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJTGI3TINRZHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

yonexsp11 · 2025-01-15T18:28:15Z

Sorry to hear that, As per my understanding, there is no stock F8e. The one posted in the OP is a modified F8d with just TPM enabled. I can try working off the F8d from the motherboard's page if you'd like to try again.

True, but F8e did come form Gigabyte, and does work on my MB, as long as I am not using the Intel ARC B580. Then nothing works properly.

Bit the other user modded that version with microcode etc, which I suspect is breakign things properly.

GTX1080Ti11G · 2025-01-15T19:17:56Z

I'm a bit confused with the F8d bios. It has memory remap at 0x302.

The DSDT shown in the body is different than the code as per the guide. The code segment is within an IF block so I am confused how to modify it. I tried adding it only to the first block and got 14 errors. The 1st edit is already present as Y1E instead of YAF so its off by 2 bytes only. There are too many duplicate checks for Local1 >= 0x07D9, maybe the bios already has above 4G enabled.

Also F8e is not on the motherboard support page, and as per user in the OP, its just got TPM. We can try the F8e you might have. You can try the grub-setup method with 0x302 offset however its enabled by default.

yonexsp11 · 2025-01-15T19:21:13Z

Ok, I also got that value with version D. Perhaps just the version e, the first link in that page. https://winraid.level1techs.com/uploads/short-url/9XOmzxAQaoEB0q6pdu366UT2cVe.zip

…

On Wed, Jan 15, 2025, 2:18 PM GTX1080Ti11G ***@***.***> wrote: I'm a bit confused with the F8d bios. It has memory remap at 0x302. remap.JPG (view on web) <https://github.com/user-attachments/assets/c0ddcf7a-dc14-4d74-9b6a-141c6fa006fd> The DSDT shown in the body is different than the code as per the guide. The code segment is within an IF block so I am confused how to modify it. I tried adding it only to the first block and got 14 errors. The 1st edit is already present as Y1E instead of YAF so its off by 2 bytes only. There are too many duplicate checks for Local1 >= 0x07D9, maybe the bios already has above 4G enabled. DSDT.JPG (view on web) <https://github.com/user-attachments/assets/8136ee69-3fe6-4bd2-a8df-062c81cffeb7> Also F8e is not on the motherboard support page, and as per user in the OP, its just got TPM. We can try the F8e you might have. You can try the grub-setup method with 0x302 offset however its enabled by default. — Reply to this email directly, view it on GitHub <#14 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BOMIPIJCN62EIHXIXCMVPQ32K2X7ZAVCNFSM6AAAAABSTF2DWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJTG42TAMRVGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

yonexsp11 · 2025-01-15T19:30:09Z

https://winraid.level1techs.com/uploads/short-url/9XOmzxAQaoEB0q6pdu366UT2cVe.zip

…

On Wed, 15 Jan 2025 at 14:18, GTX1080Ti11G ***@***.***> wrote: I'm a bit confused with the F8d bios. It has memory remap at 0x302. remap.JPG (view on web) <https://github.com/user-attachments/assets/c0ddcf7a-dc14-4d74-9b6a-141c6fa006fd> The DSDT shown in the body is different than the code as per the guide. The code segment is within an IF block so I am confused how to modify it. I tried adding it only to the first block and got 14 errors. The 1st edit is already present as Y1E instead of YAF so its off by 2 bytes only. There are too many duplicate checks for Local1 >= 0x07D9, maybe the bios already has above 4G enabled. DSDT.JPG (view on web) <https://github.com/user-attachments/assets/8136ee69-3fe6-4bd2-a8df-062c81cffeb7> Also F8e is not on the motherboard support page, and as per user in the OP, its just got TPM. We can try the F8e you might have. You can try the grub-setup method with 0x302 offset however its enabled by default. — Reply to this email directly, view it on GitHub <#14 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BOMIPIJCN62EIHXIXCMVPQ32K2X7ZAVCNFSM6AAAAABSTF2DWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJTG42TAMRVGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

yonexsp11 · 2025-01-17T19:47:23Z

I'm a bit confused with the F8d bios. It has memory remap at 0x302.

The DSDT shown in the body is different than the code as per the guide. The code segment is within an IF block so I am confused how to modify it. I tried adding it only to the first block and got 14 errors. The 1st edit is already present as Y1E instead of YAF so its off by 2 bytes only. There are too many duplicate checks for Local1 >= 0x07D9, maybe the bios already has above 4G enabled.

Also F8e is not on the motherboard support page, and as per user in the OP, its just got TPM. We can try the F8e you might have. You can try the grub-setup method with 0x302 offset however its enabled by default.

How did oyu make out with that basic verison of F8e? I think if like the OP of this thread, we can get the FFS module to stick at least that woudl be a win :)

edisionnano · 2025-01-22T19:10:03Z

Just thought I'd chime in here as I'm on a haswell platform as well. I own a Gigabte Z87X-OC. For me I had 4G Decod visible in the body, it was called Memory Remap in the extracted text file at 0x2FE offset. It was also set to enable by default.

I compiled the DSDL using the steps, and it compiled successfully. My bios has both the nvme & rebar dxes. I proceeded to use the UEFI patches and then flash the bios, it surprisingly worked.

Above 4G Decoding is now enabled, I don't have a rebar gpu to test yet, but if I do in the future I'll be sure to update it in the list of working motherboards.

Large Memory in device manager was not visible prior to all this.

I own a GA-H97-D3H (Rev. 1.0) and am on the latest BIOS. Using UEFITool I also found Memory Remap which also seems enabled by default. Since it says Enabled is the default value I expected Above 4G Decoding to say Yes in GPU-Z but it says No. Do I need to do anything to get it to say Yes?

xCuri0 added the help wanted Extra attention is needed label Nov 11, 2022

magicalz mentioned this issue Dec 25, 2022

List of working motherboards #11

Open

This was referenced Mar 4, 2023

ReBar on my ga-z97x Gaming5 #15

Closed

Asus B85-Plus : "4GB decoding" feather failed #25

Closed

Enabled it thanks #36

Closed

xCuri0 mentioned this issue Aug 16, 2023

ASUS Z87-A - No 4G Decode option/support? #76

Closed

xCuri0 added the bios issue with firmware that needs patching label Dec 3, 2023

xCuri0 mentioned this issue Jan 6, 2024

MSI Z87-G43 Gaming - Haswell Mobo without 4G Decoding Entry #112

Closed

xCuri0 changed the title ~~Gigabyte Z97X-Gaming 3 hidden 4G Decoding~~ Missing 4G decoding on Gigabyte Z97X-Gaming 3 Feb 8, 2024

xCuri0 mentioned this issue Feb 13, 2024

I'm kinda new to this but on step 4 in ReBarUEFI wiki it says to open the IRFExtractor extracted file and find "4G Decod" which I'm stuck on. #150

Closed

Missing 4G decoding on Gigabyte Z97X-Gaming 3 #14

Missing 4G decoding on Gigabyte Z97X-Gaming 3 #14

Comments

BartekJablonski commented Nov 11, 2022 • edited Loading

sidex15 commented Nov 12, 2022

BartekJablonski commented Nov 12, 2022

ysc3839 commented Nov 25, 2022

magicalz commented Dec 21, 2022 • edited Loading

magicalz commented Dec 25, 2022 • edited Loading

BartekJablonski commented Feb 15, 2023 • edited Loading

BartekJablonski commented Feb 16, 2023

NoUserNameForYou commented Mar 4, 2023

xCuri0 commented Mar 6, 2023 • edited Loading

xCuri0 commented Mar 7, 2023 • edited Loading

BartekJablonski commented Mar 18, 2023 • edited Loading

xCuri0 commented Mar 18, 2023 • edited Loading

BartekJablonski commented Mar 18, 2023

xCuri0 commented Mar 18, 2023

BartekJablonski commented Mar 18, 2023 • edited Loading

BartekJablonski commented Mar 27, 2023 • edited Loading

BartekJablonski commented May 7, 2023 • edited Loading

BartekJablonski commented May 7, 2023

xCuri0 commented May 7, 2023

BartekJablonski commented May 7, 2023

ghost commented Aug 21, 2023 • edited by ghost Loading

CNduan commented Oct 6, 2023

xCuri0 commented Oct 23, 2023

xCuri0 commented Oct 23, 2023 • edited Loading

Here are comparisons of BIOS with vs without 4G decoding

AddMemorySpace hook

AllocateMemorySpace hook

jakeman2048 commented Mar 3, 2024 • edited Loading

Joris-truly commented Mar 24, 2024

ziddey commented Apr 2, 2024 • edited Loading

ZLHuo commented May 2, 2024 • edited Loading

xCuri0 commented May 2, 2024

ZLHuo commented May 2, 2024

SaulGoodman1337 commented May 14, 2024

xCuri0 commented May 14, 2024

ivan49k commented Jun 1, 2024

xCuri0 commented Jun 1, 2024

Shranobxtha commented Nov 27, 2024

geotaxho commented Dec 8, 2024

Shranobxtha commented Dec 12, 2024

GTX1080Ti11G commented Jan 8, 2025

yonexsp11 commented Jan 10, 2025

GTX1080Ti11G commented Jan 11, 2025

yonexsp11 commented Jan 12, 2025 via email

yonexsp11 commented Jan 15, 2025 via email

GTX1080Ti11G commented Jan 15, 2025

yonexsp11 commented Jan 15, 2025 via email

yonexsp11 commented Jan 15, 2025 • edited Loading

GTX1080Ti11G commented Jan 15, 2025 • edited Loading

yonexsp11 commented Jan 15, 2025 via email • edited Loading

yonexsp11 commented Jan 15, 2025 via email

yonexsp11 commented Jan 17, 2025

edisionnano commented Jan 22, 2025

BartekJablonski commented Nov 11, 2022 •

edited

Loading

magicalz commented Dec 21, 2022 •

edited

Loading

magicalz commented Dec 25, 2022 •

edited

Loading

BartekJablonski commented Feb 15, 2023 •

edited

Loading

xCuri0 commented Mar 6, 2023 •

edited

Loading

xCuri0 commented Mar 7, 2023 •

edited

Loading

BartekJablonski commented Mar 18, 2023 •

edited

Loading

xCuri0 commented Mar 18, 2023 •

edited

Loading

BartekJablonski commented Mar 18, 2023 •

edited

Loading

BartekJablonski commented Mar 27, 2023 •

edited

Loading

BartekJablonski commented May 7, 2023 •

edited

Loading

ghost commented Aug 21, 2023 •

edited by ghost

Loading

xCuri0 commented Oct 23, 2023 •

edited

Loading

jakeman2048 commented Mar 3, 2024 •

edited

Loading

ziddey commented Apr 2, 2024 •

edited

Loading

ZLHuo commented May 2, 2024 •

edited

Loading

yonexsp11 commented Jan 15, 2025 •

edited

Loading

GTX1080Ti11G commented Jan 15, 2025 •

edited

Loading

yonexsp11 commented Jan 15, 2025 via email •

edited

Loading