xCuri0 / ReBarUEFI

Resizable BAR for (almost) any UEFI system
MIT License
1.31k stars 59 forks source link

Asus X99-A II Working ready to use file download and tutorial - unlocked NVram / modified pcibusdxe / injected rebardxe #13

Closed Mak3rde closed 1 year ago

Mak3rde commented 1 year ago

EDIT:

Working Rebar with Unlimited Size.

Notice:

MAKE THE BIOS BACKUP FIRST

Tools:

ready to use efi Downloads:

X99-A-II-ASUS-2101_CAP_STOCKROM_64-bit_BAR_ENABLED_rebar_driver_injected_barsize_Patched.zip

X99-A-II-ASUS-2101_ROM_STOCKROM_64-bit_BAR_ENABLED_rebar_driver_injected_barsize_Patched.zip

If You want to diy

How To:

1

MAKE THE BIOS BACKUP FIRST

2

OR

-create a new txt file in you folder

4

5

A:

System

xCuri0 commented 1 year ago

Hi the problem here is with NvramSmi not allowing EFI variables to be written. Other users were able to fix this by downgrading NvramSmi or BIOS with one from 2014. But you have a motherboard from 2016 so that won't work

A patch needs to be developed for your NvramSmi to remove the variable name restriction. I do think those on Hackintosh forums have already figured it out.

Mak3rde commented 1 year ago

@xCuri0 got it working.

edited initial post.

xCuri0 commented 1 year ago

@Mak3rde your patch for PciBus has been added in commit 16712446c800707822dc4e37964abe0c85fc6e50

Mak3rde commented 1 year ago

@xCuri0 nice!

Maybe you should add the info that this patch is specifically for the Asus X99a-II because the other patch that already was in the patch.txt and had Haswell written to it wasn't working on my bios, so I would assume that my patch won't work on other platforms too. Maybe it's working for other Asus x99 boards, but I could not test that.

xCuri0 commented 1 year ago

@Mak3rde actually it does seem to apply to an ASUS Z170-WS board with similar issue. waiting to see if it works for them

Mak3rde commented 1 year ago

oh nice, thats awesome! lets hope it works for them aswell

dawenhaozx commented 1 year ago

Thank you very much for your efforts to fix this issue. I tried it but it didn't work.

setup_var_cv IntelSetup 0x10E2 0x04 0x00(0x00~0x07)

0x11339 VarStore: VarStoreId: 0x1 [EC87D643-EBA4-4BB5-A1E5-3F3E36B20DA9], Size: 0x17D6, Name: IntelSetup {24 21 43 D6 87 EC A4 EB B5 4B A1 E5 3F 3E 36 B2 0D A9 01 00 D6 17 49 6E 74 65 6C 53 65 74 75 70 00}

0x15351 One Of: MMIOHBase, VarStoreInfo (VarOffset/VarName): 0x10E2, VarStore: 0x1, QuestionId: 0x1A8, Size: 4, Min: 0x0, Max 0x7, Step: 0x0 {05 9A 0C 00 0D 00 A8 01 01 00 E2 10 10 12 00 00 00 00 07 00 00 00 00 00 00 00} 0x1536B One Of Option: 56T, Value (32 bit): 0x0 (default) {09 0A 14 11 32 02 00 00 00 00} 0x15375 One Of Option: 40T, Value (32 bit): 0x1 {09 0A 13 11 02 02 01 00 00 00} 0x1537F One Of Option: 24T, Value (32 bit): 0x2 {09 0A 12 11 02 02 02 00 00 00} 0x15389 One Of Option: 16T, Value (32 bit): 0x3 {09 0A 11 11 02 02 03 00 00 00} 0x15393 One Of Option: 12T, Value (32 bit): 0x4 {09 0A 10 11 02 02 04 00 00 00} 0x1539D One Of Option: 4T, Value (32 bit): 0x5 {09 0A 0F 11 02 02 05 00 00 00} 0x153A7 One Of Option: 2T, Value (32 bit): 0x6 {09 0A 0E 11 02 02 06 00 00 00} 0x153B1 One Of Option: 1T, Value (32 bit): 0x7 {09 0A 0D 11 02 02 07 00 00 00}

xCuri0 commented 1 year ago

@dawenhaozx have you verified that the address is actually changing in Windows

Because iirc there are multiple entries for each PCIe port.

Also there's an option to change the MMIOH region size (default 256GB) which you can try changing.

Also FYI this is the wrong issue