-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GA-X79-UP4 (Sandy Bridge-E) semi-working with ReBAR ≤1GB #9
Comments
I`ve checked the bios, seems like i do not have any options called CSM, or above 4G decode. Update: It did nothing, still the same behaviour :( |
@aquamacho1 you need to enable the hidden 4G Decoding setting. i can't be replying to everyone so i created a wiki page detailing how to do it Enabling hidden 4G decoding. i'm closing this issue since your board does have 4g decoding just that it's a hidden setting. if there are any problems still after 4g decoding enabled i can re open it |
@xCuri0 thx for your help, but it seems i have a problems with enabling it.
|
Or i messed up 5. step in the guide, do i rename |
@aquamacho1 GUID mismatch doesn't matter. 0x04 and 0x4 are the same number so not a problem Yes you do have to rename it |
Well, either i did something wrong or it just doen`t work, 1024mb is still my limit. |
@aquamacho1 did you try setting it to 0x0, rebooting, setting it to 0x1 and then again rebooting ? that's what i had to do to get it working on my mobo if that doesn't work you can try using |
Yes, i did tried doing that method to, but still nothing (i mean black screen after increasing value of rebar to more than 1GB), i will try |
Nope, i think |
@aquamacho1 if pcie 3.0 wasn't working you wouldn't be able to use rebar at all. your screenshot also shows working pcie 3.0 maybe you could try using AMIBCP to change it's |
is this important? its off by default to, but i think i need enable this to right to get 4g decode?
Din`t help. |
@aquamacho1 probably not needed as it's disabled by default on my motherboard and 4g decode with 8gb bar still works |
@xCuri0 AMIBCP can`t open my bios file, or i dont know how to open it |
@aquamacho1 correct AMIBCP version for your board is v4.55 it opens for me. Also did you try using the newer F7 version bios maybe it fixes this issue ? |
@aquamacho1 don't change anything except Access/Use to USER on Above 4G decoding. Otherwise you might get no boot. All this will do is make the option visible in the BIOS |
Flashed modded bios with 4G enabled by dafault, but no dice, checked with the grub console, it is was enabled right after bios flash. @xCuri0 i have dual bioses on this board, i flashed M bios like 30 times in the past two days XD |
I guess you can try the F7 bios then |
Nope, all the same, can you give me your mobo name? i will check what options are enabled between your and mine. Maybe will find something. |
@aquamacho1 Gigabyte B75M-D3H |
what rev?, i dont think its matters. Mine mobo has 2 rev. and both of them have same bioses, i literally flashed bios from another rev. |
iirc it's 1.1 |
So using your guide on DSDT patching from wiki, i`ve extracted and decoded AmiBoardInfo --> DSDT.aml --> DSDTMod.dsl
Does this somehow related to the issue? Anyway, here is full file if you wanna look at it I do not have anything similar to this in my DSDT file :(
|
@xCuri0 i don`t have large memory :cry |
@aquamacho1 4G decoding is on ? if you were getting resources error in windows with 4g decoding on that means the BIOS is still allocating the device properly and can be fixed with DSDT. otherwise it's very hard to fix (BIOS patching) |
I don't think that's the cause. 2GB would work then You can download the BIOS for an Ivy bridge mobo with the code such as B75M-D3H or P8Z77-V Pro and extract the PE32 module from PciHostBridge with UEFITool to see it. |
@xCuri0 so i think i maybe found the problem in my case, on my mobo ReBarUEFI driver is allocating its space not from virtual space, but from System Board Resources instead
Those two sections is what appears to be my ReBAR values (1GB and 256M respectively)
|
And i think this section probably is what responsible for mine problems booting bigger ReBAR values.
This code is missing on Jingsha and supermicro boards. Also, i think another reason is to do with this name IOHM:
Mine X79 - Name (IOHM, ResourceTemplate () IOHM is not used anywhere but in this script and name. |
@xCuri0 when im trying rebuild DSDT.dsl, im getting so much errors, do you by any chance know why there are so many? |
@aquamacho1 you have to manually fix each error which isn't easy tbh especially when there are so many. my DSDT only had 2 and were fixable with a few google searches. |
@xCuri0 i can't find any of the code from badcode file in the stock file O_o, there is something wrong here. Oh wait, nvm i'm trolling, badcode came with iasl :D, but still. |
@xCuri0 i did compiled DSDT with both 2013 and 2022 IASL without an errors, but resulting files are identical to decompiled. Amiboardinfotool creates amiboardinfo.efi from compiled before DSDT, but its 325kb in size and its has some spagetti code at the beginning and the rest is similar to decompiled. |
Update: So from MacOS using MaciASL in legacy mode i`ve edited and recompiled DSDT with those lines removed/edited below and some more, but no luck, these related to something else i guess. |
@aquamacho1 to my knowledge DSDT editing won't solve problems where you can't even POST. Only if you can't boot OS or OS gives no resources error it can help |
@xCuri0 i was thinking about replacing PCIBus or Rootbridge\other drivers from another mobo, but im scared it may cause damage to the board or gpu :( |
@xCuri0 do you know if there is a way to modify This part is probably why i have no boot after entering values above 1GB.
|
@aquamacho1 the problem is it's not allocating addresses in the 64-bit region. i don't know anything about modifying PciRootBridge though |
Just a consideration...while the x79 platform supports PCIE 3.0... the 3930K supports only PCIe 2.0 as per the Ark website; try using a 22nm chip that supports PCIe 3.0 and you may get your ReBAR working. It does require 3.0 as far as I understand. |
@XManPro79 PCIe Gen3 isn't needed for rebar. Rebar does work here but not at full size because of firmware bug |
Well, out of complete boredom, and after AMD borked my 1G rebar, i have returned to this, and i have some progress:
And
And now i have this: Any ideas @xCuri0 ? |
@aquamacho1 With 4G decode on and BAR set to 4GB or larger it will show in Large Memory. Also DSDT editing won't fix POST issues, only if you can't boot Windows it's DSDT related. Try setting these BIOS settings: 4G Decode: On |
I had these enabled like this from the start |
@xCuri0 Does it matter in which PCI slot my gpu is plugged in? All this time my gpu was in slot 5 (second x16 slot) |
@aquamacho1 i don't think so but sometimes these HEDT boards have different MMIO allocation per slot |
@aquamacho1 you can try these patches
maybe it will get video output working |
@xCuri0 Im sorry, but i can't test this right now, that X79 board currently not in use anymore. But i can tell atleast that patches are working on X79 bios file using UEFIPatch. |
Hello! Also trying to enable greater than 1GB ReBar on x79. As you can see, only PCI Bus is in large memory area. With ReBar size of 16GB, I can see low res windows boot screen and can get display out, although probably 640x480 black and white. Some parts of GPU are in large area, some not. As mentioned, I have dual BIOS and CH341 so if you think we can work this out, I'm willing to test. Thank you! |
Disable CSM and all legacy stuff
This is normal You need to figure out why it's code 43ing, maybe Linux dmesg can help |
Sorry for delay, I'm short on time. |
I'm closing this because I think we've solved it at #48 |
REBAR Legacy On.reg
file, without it there are no option to enable bar in amd control panel.Hi, so i did manage to unlock ReBAR on my Sandy Bridge - E motherboard (GA-X79-UP4), by modding bios with UEFITool, but values greater than 1GB = my motherboard just straight trying recovery from second bios, which it fails, then reboots and tries again to ∞, until i manually do recovery by pressing reset and power buttons at the same time for 10 seconds, then it flashes 2nd bios to M.
I've also tried those secret setup_var's
The text was updated successfully, but these errors were encountered: