Open xCuri0 opened 1 year ago
Chinese Unbranded X79 motherboard, RX 570 8GB...
Huananzhi X99-TF Vega 64
Registry editing is required to allow drivers to enable the ReBar.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000]
"KMD_EnableRebarForLegacyASIC"=dword:00000001
"KMD_RebarControlMode"=dword:00000001
"KMD_RebarControlSupport"=dword:00000001
Would my Z97-Pro be considered working? I haven't tried the 16GB patch (only tested to 8GB), but it needs the replacement of the older 1204 NvramSmi module and the PciBus UEFIPatch to work. The GPU tested is the Intel Arc A380 (will test the A770 once I get a replacement power supply).
@Tokobotenkai anything 4GB or higher is considered working but if you find a larger size doesn't I can add a note
Hi, i have z270 m7 with 7700k. my motherboard has 4G decoding in bios. i also have gtx 1080. how to patch my bios? here my bios link: https://download.msi.com/bos_exe/mb/7A57v10.zip
@EDK-Rise GTX 1080 doesn't support resizable bar
Chinese Unbranded X79 motherboard, RX 570 8GB...
@sidex15 But can you actually check what a name of this board?, im trying figure out how to patch mine X79, checking whats the difference between them, maybe i will find something. Or even better, save a bios file, and upload here.
@aquamacho1 well after deep diving in the russian overclocking forums I found that my board is Jingsha X79M-S 1.0 the Picture is the same as mine...
I just followed the X99 guide from Miyconst and use Enabling hidden 4G decoding...
@sidex15 This is awesome, thx. I will just buy this mobo then :), im just kidding.
Chinese Unbranded X79 motherboard, RX 570 8GB...
Add to note that macOS(Hackintosh) didn't boot after enabling Rebar..
@sidex15 I think macOS doesn't support large BARs not a problem with the bios or anything
@sidex15 I think macOS doesn't support large BARs not a problem with the bios or anything
Yeah i'm using opencore 0.8.3 even with resizeapplegpubars set to 0 won't even boot to macOS... I guess it's still using the max BARs... I'll try lowering the BAR size see if it boots...
@sidex15 I think macOS doesn't support large BARs not a problem with the bios or anything
@xCuri0 yep you're right setting a rebar size of 256mb boots to macOS... I also found out that my motherboard is Jingsha X79M-S 1.0 after digging in the Russian overclocking forum...
ASUS Z170-WS & Intel ARC A770, BAR size set to unlimited and the full 16GB worked
Also works on a ASUS Z170 Sabertooth MK1
A big thank you @xCuri0 and @Mak3rde Asus z170-a, 5700xt and use patch "Don't downgrade 64-bit BARs to 32-bit (by @Mak3rde)"
MZ32-AR0 (rev. 1.0) +ARC A380 +TESLA M40 Before:
(A380 has a 43 code after installing any driver later than 31.0.101.3277 on my platform. I don't know why Tesla M40 has "large memory range" by default. Does that mean there is a white list inside the bios for some rebar cards? )
After inserting ReBarDxe.ffs and running ReBarState.exe BAR size set to unlimited :
(A380 works with the latest driver after doing these. A small issue i found is that Intel® Arc™ Control refuse to start. )
@gyhmz Tesla M40 doesn't have ReBar it just has a large BAR by default.
I can confirm it works on a Supermicro H11DSi-NT (tested with bios v1.3, should work with the v2.4 as well). Tested with a 4090 FE. No patches needed, 256GB ram installed. GPU-Z says 3 bars are available - 16MB, 32MB, and 32GB. (before it was 16,32,256MB, and it said "disabled in bios")
Thanks a lot for making this tool.
@Tokobotenkai Hey! Do you mind sharing modified bios for z97-pro, please?
@Tokobotenkai Hey! Do you mind sharing modified bios for z97-pro, please?
There you go: https://drive.google.com/file/d/1yZb9LkaTvvBjAkJfGSO-hPgm2L_W9SWH/view?usp=sharing
I have random issues where my keyboard and mouse is not detected on boot, not sure if it is a dying USB or a BIOS issue though.
@Tokobotenkai Hey! Do you mind sharing modified bios for z97-pro, please?
There you go: https://drive.google.com/file/d/1yZb9LkaTvvBjAkJfGSO-hPgm2L_W9SWH/view?usp=sharing
I have random issues where my keyboard and mouse is not detected on boot, not sure if it is a dying USB or a BIOS issue though.
@Tokobotenkai I have them on my Hero too. Funny enough they only occur after setting rebar state value.
@Tokobotenkai Hey! Do you mind sharing modified bios for z97-pro, please?
There you go: https://drive.google.com/file/d/1yZb9LkaTvvBjAkJfGSO-hPgm2L_W9SWH/view?usp=sharing I have random issues where my keyboard and mouse is not detected on boot, not sure if it is a dying USB or a BIOS issue though.
@Tokobotenkai I have them on my Hero too. Funny enough they only occur after setting rebar state value.
I suspect it is some device being mapped in the same error, but the error is intermittent. I workaround it by using a PS2 keyboard.
@Tokobotenkai Thank you! If I'm going flash bios with programmer CH341A so I'll need to uncapsule bios into ROM format, right?
machinist mr9a pro v2 work with re bar
@supermanz87 you have to use UEFIPatch. it's described in the README how to use it
Asus Z170-P D3 : requires patch "Don't downgrade 64-bit BARs to 32-bit (by @Mak3rde)"
@xCuri0 I found this: https://github.com/LongSoft/UEFITool/pull/116#issuecomment-370165778
842A454A-75E5-408B-8B1C-36420E4E3F21 10 P:9801000072:0000000072
Vit9696's code allows for nvramsmi to write on UEFI for Z97's Asus motherboards like my Maximus VII hero. Already tested it, and it works.
Saved me from extracting nvramsmi from 1104 and replacing it on 3503.
@cursemex thanks for finding this. i've added it to patches.txt
So I've modified my Asus Z97 Deluxe bios with FFS DXE module, then patched it with those patches: # NvramSmi NVRAM whitelist unlock (by @vit9696) and # PciBus | Don't downgrade 64-bit BARs to 32-bit (Haswell).
All successful, flushed bios - it loaded. Enabled 4G Decoding and disable CMS. Although I'm not sure if some ReBar option should appear in bios menu as well? Because it doesn't.
But after using ReBarState.exe and setting value to 32(also tried 16) mobo won't boot after I restart it. At first it makes singe beep with pc-speaker as if its OK, but after 2 seconds there goes another 3 beeps and thats it. Any suggestions?
@Divin1ty666 No, you shouldn't see any options for ReBar. Once you've set your Rebar Value, you should aee it in GPU-Z.
If you can't get into windows, then that's because you jumped to a high value than to try smaller values to see which one is more stable. Try clearing CMOS, if that doesn't work, disconnect your GPU (Removing power cable from it should suffice), then connect your display cable into your motherboard if it has that option and reset the value to something smaller.
You didn't mention how much ram you have installed. If it is 16-24GB use this patch too:
# PciHostBridge | Replace 8-16GB MMIO region with complete use of 64GB address space (Haswell).
If you are at 32GB, it won't work as it needs further modification. I have mine working with 16GB rebar at 24GB of ram. I guess I'll open a new thread today so we can see if we can fix that 32GB.
Here are the patches I've used: ` ># PciBus | Remove <16GB BAR size limit (Ivy Bridge/Haswell) 3C1DE39F-D207-408A-AACC-731CFB7F1DD7 10 P:B8FFFFFFFF030000004C3B:B8FFFFFFFFFFFFFF004C3B
PciBus | Don't downgrade 64-bit BARs to 32-bit (Haswell)
3C1DE39F-D207-408A-AACC-731CFB7F1DD7 10 P:833E067506C70604000000833E077506C70605000000:66906690669066906690669066906690669066906690
PciHostBridge | Replace 32/48GB - 63GB MMIO region with 32/48GB - 64GB (Haswell)
8D6756B9-E55E-4D6A-A3A5-5E4D72DDF772 10 P:3BC3771548BE000000C00F000000482B:3BC3771548BE0000000010000000482B
Fix Nvramsmi
842A454A-75E5-408B-8B1C-36420E4E3F21 10 P:9801000072:0000000072 `
The "norm" is to have 1 beep after the normal post after you set the rebar value. There will be an issue of USB not working in bios. So set your overclocking, rebar, csm before applying the value of rebar. It'll mess with entering safe mode of windows too, check my win-raid post for guides to workaround it if you need it.
@cursemex I have 16Gb, but # PciHostBridge | Replace 8-16GB MMIO region with complete use of 64GB address space (Haswell). patch cannot be applied: No patches can be applied to input file, all other patches are applied already.
@Divin1ty666 what's your GPU ? If it's a 32GB BAR such as 3090 it won't work even with 16GB RAM
@Curi0 rx 6700 xt
@Divin1ty666 do smaller bar sizes atleast work ? start with 512mb and increase till you get the issue
@Curi0 So should I start with "1"? Or what value should enter for 512mb? I don't get I how they correspond, I know 0 means disable and 32 is max, right?)))
ps. and what about patch PciHostBridge | Replace 8-16GB MMIO region with complete use of 64GB address space (Haswell) - do I need it? Or it's not for z97 motherboards?
@Curi0 So should I start with "1"? Or what value should enter for 512mb? I don't get I how they correspond, I know 0 means disable and 32 is max, right?)))
ps. and what about patch PciHostBridge | Replace 8-16GB MMIO region with complete use of 64GB address space (Haswell) - do I need it? Or it's not for z97 motherboards?
This is in terms of power of 2, as in 2^x. In this case, two to the power of eight would be two hundrend and fifty six. 2^8 = 256MB, therefore the value we put in ReBarState.exe should be 8. For 512MB it'll be 9, 1024MB will be 10, and so on.
@xCuri0 can confirm that ASUS X99-DELUXE II works with Intel A770 with 16GB BAR0! Required the Nvramsmi patch! Thanks again for putting this together :)
Hello, I believe I have rebar (8GB) working on my MSI Z97 Gaming 5 w/ HP 3060 Ti (OEM) and 32GB RAM
@Intelevande did you need to use UEFIPatch ? all other Z97 users had to
@Intelevande did you need to use UEFIPatch ? all other Z97 users had to
I didn't use UEFIPatch, I followed your instructions on inserting the FFS and enabling the hidden 'Above 4G Decoding' option, set 32 in the rebarstate.exe program and it seemed to be working for me. Do you think I should expect some issues even though gpuz says it's enabled?
Edit: I guess I should also note for anyone else who has my board the offsets for 4g decoding and csm that I used Above 4G Decoding: 0x1 CSM: 0x596
Hi everyone, I ran into a problem when using UEFI Patch. When trying to apply patches.txt PowerShell writes a message 'patches.txt file not found or can't be read'. UEFIPatch, UEFITool 0.28.0 and patches.txt are located in the same directory. Asus x99 Strix
Hi everyone, I ran into a problem when using UEFI Patch. When trying to apply patches.txt PowerShell writes a message 'patches.txt file not found or can't be read'. UEFIPatch, UEFITool 0.28.0 and patches.txt are located in the same directory. Asus x99 Strix
Use Command Prompt with admin privilage instead. You can search up CMD in the task bar search, then right click it and run as admin. Then "cd [UEFIPatch.exe directory]". And follow the rest of the instructions from here. Make sure to use "UEFIPatch.exe [filename] [patches.txt] -O [output file]" during the commands with the ".exe" included in the command.
@Divin1ty666 No, you shouldn't see any options for ReBar. Once you've set your Rebar Value, you should aee it in GPU-Z.
If you can't get into windows, then that's because you jumped to a high value than to try smaller values to see which one is more stable. Try clearing CMOS, if that doesn't work, disconnect your GPU (Removing power cable from it should suffice), then connect your display cable into your motherboard if it has that option and reset the value to something smaller.
You didn't mention how much ram you have installed. If it is 16-24GB use this patch too:
# PciHostBridge | Replace 8-16GB MMIO region with complete use of 64GB address space (Haswell).
If you are at 32GB, it won't work as it needs further modification. I have mine working with 16GB rebar at 24GB of ram. I guess I'll open a new thread today so we can see if we can fix that 32GB.Here are the patches I've used: ` ># PciBus | Remove <16GB BAR size limit (Ivy Bridge/Haswell) 3C1DE39F-D207-408A-AACC-731CFB7F1DD7 10 P:B8FFFFFFFF030000004C3B:B8FFFFFFFFFFFFFF004C3B
PciBus | Don't downgrade 64-bit BARs to 32-bit (Haswell)
3C1DE39F-D207-408A-AACC-731CFB7F1DD7 10 P:833E067506C70604000000833E077506C70605000000:66906690669066906690669066906690669066906690
PciHostBridge | Replace 32/48GB - 63GB MMIO region with 32/48GB - 64GB (Haswell)
8D6756B9-E55E-4D6A-A3A5-5E4D72DDF772 10 P:3BC3771548BE000000C00F000000482B:3BC3771548BE0000000010000000482B
Fix Nvramsmi
842A454A-75E5-408B-8B1C-36420E4E3F21 10 P:9801000072:0000000072 `
The "norm" is to have 1 beep after the normal post after you set the rebar value. There will be an issue of USB not working in bios. So set your overclocking, rebar, csm before applying the value of rebar. It'll mess with entering safe mode of windows too, check my win-raid post for guides to workaround it if you need it.
but where to apply those patches? Im using haswell too, mobo is GA-Z97X-Gaming
@LordAdo96 do you see the name of this issue? It's "List of working motherboards", not "Support for people who don't understand a thing".
@xCuri0 I think with rising popularity such people will swarm this repository. Maybe redirect them somewhere?
@SEt-t i do think that's starting to be a problem but i don't know where they can create support questions. maybe github discussions or setting up a discord ? i also can't be responding to all of them
It's "List of working motherboards", not "Support for people who don't understand a thing".
@SEt-t Fail insert clapping GIF
@xCuri0 I'll be down to help with a discord. I was on the verge of writing a dummy's guide on patching, or just refer them to my winraid step-by-step.
@LordAdo96 You already opened an Issue, I'll just reply there.
My bad sorry guys really
@cursemex already made a dummy's guide on patching including the MMTool workaround. It's on the wiki linked in README
will see about creating a discord server later
Thanks for the advice. CMD turned out, + UEFIPatch. ASUS STRIX X99 GAMING + MSI RTX 3050 GAMING X
Gigabyte X470 AORUS GAMING 5 WiFi + Ryzen 7 2700X + Intel Arc A770 LE 16GB
Worked with 16GB BAR and unlimited BAR (select input value 32 for ReBarState.exe) Specific UEFI patch required to write the new image with Qflash.
Motherboards which don't support at least 2GB BAR size are considered not working.
If you're having any issues please see Common issues (and fixes) before replying.
Use this format in your comment:
lspci
(Linux) shows)