Need help with UEFI Tool #49
-
|
I want to add nvstrap on my uefi bios, but I have a problem. When i try to add dxe nvstraps i get a error on uefi tool and mmtool, as I understand this happening because I don't have much free space in bios, rebar take 2 kb, when nvstrap about 14 kb. I can fix it? Bios 8 mb |
Beta Was this translation helpful? Give feedback.
Replies: 10 comments 29 replies
-
|
On the 1st screenshot, Strap driver is not the last one in the volume list, perhaps this causes an error? |
Beta Was this translation helpful? Give feedback.
-
|
You may get a smaller .ffs file if you manually compile v0.1 from github. But make sure this is really the issue, because v0.1 uses hard-coded values for the GPU BAR0 address on the PCI bus (plus the PCI bridge memory mapped address), that you need to fill in manually into the source code. Also see the video guide (thanks to @UnidentifiedTag for providing it). Maybe you can try an older UEFI image for your motherboard, with a smaller size, just to confirm that size is the problem. Make sure the older version still supports your CPU ! To further decrease the .ffs size, you could manually remove all the IDs from DeviceRegistry.c source file, except the PCI device ID for your GPU |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
If you can help with that (make .ffs smaller 9 kb) I will be very grateful. I can send hex values of my system. I will try tomorrow, but i dont sure about success |
Beta Was this translation helpful? Give feedback.
-
|
@666cloudyy i saw on win-raid forum that some users delete unwanted modules relating to network boot to free up space for nvme dxe on old motherboards. maybe that can work in this case too |
Beta Was this translation helpful? Give feedback.
-
|
What does the python error say? |
Beta Was this translation helpful? Give feedback.
-
|
say this errors |
Beta Was this translation helpful? Give feedback.
-
|
It’s obvious to me what the problem is, you didn’t follow the instructions exactly on the YouTube video when installing cmake or python, hence the script is giving you errors, you need to add the directory’s of all installed tools, this isn’t something that is magically done for you https://youtu.be/ldnC18u8FI0?si=bU75GSRVM0yYu5iJ Run these commands with the correct location to python, cmake, nasm set PATH=%PATH%;%ProgramFiles%\NASM\ set PATH=%PATH%;pathtoyourepythoninstall set PATH=%PATH%;%ProgramFiles%\pathtoyourecmakeinstall Note : it might be a sub directory with in the install, is normally where the .exe is located so python.exe or cmake.exe so look for .exe files with in where the installs were then add that directory to each command example “set PATH=%PATH%;” then you’re path this should clear some of the errors if not all, |
Beta Was this translation helpful? Give feedback.
-
|
To check each programs path has been fixed you run nasm --version @terminatorul could you add the rest, because you’re deleted the compile instructions the compile video doesn’t have the commands now… really on the main GitHub you could of kept both this new method you want everyone to use and the old method and just titled each under what they are |
Beta Was this translation helpful? Give feedback.
-
|
The only other advice I can give you @666cloudyy is start again and follow exactly what happens in the video, you’ll have to manually copy by eye each command that is used, because they have disappeared from where they were located |
Beta Was this translation helpful? Give feedback.
-
|
I was able to advance almost to the end, but still something is going wrong. I have this problem after build .ffs and reflash UEFI, i tested several values in LocalPciGPU.h, but he writes this error everywhere |
Beta Was this translation helpful? Give feedback.
-
|
You’ve not compiled your values correctly, using incorrect number, watch the YouTube video about how to get the correct values make sure to search the full sentences and not just the word, “vga controller” read the featured comment on the video to learn more |
Beta Was this translation helpful? Give feedback.
-
|
i must use decimal values or hex in localpcigpu? |
Beta Was this translation helpful? Give feedback.
-
|
it's just that in the video I saw that there were three different options and I didn't understand which one to use |
Beta Was this translation helpful? Give feedback.
-
|
You can use any of the 3, try any of the 3, the 1st one is obviously recommended that’s why it’s 1st, it goes in order of best too least best. You use the website to calculate the numbers you need to enter https://www.save-editor.com/tools/wse_hex.html I’d say your problem lays in getting the correct digits using the search option in notepad, After cpuid. “vga controller” Again with the correct values you need to copy you’ll see the manufacturers name listed, amd, intel, Nvidia so on… one will be the motherboard manufacturer the other you’re gpu manufacturer |
Beta Was this translation helpful? Give feedback.
-
|
what steps can we follow to help isolate the problem if our system fails to post with any size ReBAR set? |
Beta Was this translation helpful? Give feedback.
-
|
@Black6spdZ Are you compiling v0.1 as well ? Usually your simptoms (fail to POST) would indicate the wrong hard-coded values, like for GPU BAR0 base address, or the bridge address range |
Beta Was this translation helpful? Give feedback.
-
|
I'm the one with the dual xeon Z10PE board and I tried the first iteration of the auto driver unless anything substantial has come since then |
Beta Was this translation helpful? Give feedback.
-
|
I do not know what I am doing wrong, i tested all 3 variants of localpcigpu in .ffs, with or without uefi patch Description PCI to PCI Bridge |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
The above are the numbers you put in to Visual studios, unless you want me to do that for you as well? please could @terminatorul or @xCuri0 check that I gave the right numbers to the end user, otherwise it might be a case of the blind leading the blind let us know the results @666cloudyy after I have followed my own YouTube video on an iPhone editing you’re cpuid results |
Beta Was this translation helpful? Give feedback.
-
|
I tested this values, but I have the same result |
Beta Was this translation helpful? Give feedback.
-
|
This will need to be escalated to the next support agent thank you for you’re patience |
Beta Was this translation helpful? Give feedback.
-
|
Hi @666cloudyy Your LocalPciGpu.h file should have the values below. I used hexadecimal values, but you can freely use the equivalent decimal values if you want. #define TARGET_GPU_PCI_VENDOR_ID 0x10DEu
#define TARGET_GPU_PCI_DEVICE_ID 0x2188u
#define TARGET_GPU_PCI_BUS 0x02u
#define TARGET_GPU_PCI_DEVICE 0x00u
#define TARGET_GPU_PCI_FUNCTION 0x00u
// PCIe config register offset 0x10
#define TARGET_GPU_BAR0_ADDRESS UINT32_C(0xFA00'0000) // Should fall within memory range mapped by the bridge
#define TARGET_GPU_BAR1_SIZE_SELECTOR _4G // Desired size for GPU BAR1, should cover the VRAM size
// Secondary bus of the bridge must match the GPU bus
// Check the output form CPU-Z .txt report
#define TARGET_BRIDGE_PCI_VENDOR_ID 0x8086u
#define TARGET_BRIDGE_PCI_DEVICE_ID 0x0E08u
#define TARGET_BRIDGE_PCI_BUS 0x00u
#define TARGET_BRIDGE_PCI_DEVICE 0x03u
#define TARGET_BRIDGE_PCI_FUNCTION 0x00u
// Memory range and I/O port range (base + limit) mapped to bridge
// from CPU-Z .txt report of the bridge and GPU
// PCIe config register offset 0x20
#define TARGET_BRIDGE_MEM_BASE_LIMIT UINT32_C(0xFB00'FA00) // Should cover the GPU BAR0
// PCIe config register offset 0x1C
#define TARGET_BRIDGE_IO_BASE_LIMIT 0xE0E0uAbout your error about the Please manually modify the file DeviceList.cc at the following line:
The initial version v0.1 was written for the regular expression to match the English language, but later versions no longer depend on language. |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Yeah you can’t use any other language than English, with 0.1v, so rebar is working ? Not sure what you mean by regexp |
Beta Was this translation helpful? Give feedback.
-
|
I was in a hurry, it turns out that after choosing the rebar size, I have such an error |
Beta Was this translation helpful? Give feedback.
-
|
Looks to me like you haven’t disabled csm or enabled above 4g encoding in the bios. go confirm the above options are enabled and disabled respectively, open settings, go to recovery, reboot in to recovery mode, don’t press the reset one, when the computer reboots press more options then uefi / bios menu I have no idea about the last question maybe you could answer that for us? @terminatorul is the user able to use a different ui language with in windows or is this also messed up in v0.1 ? Sleep won’t also work @666cloudyy |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
yeah |
Beta Was this translation helpful? Give feedback.
-
|
I am happy things worked for you. You can stil enable ReBAR with other languages, if you use the right regular expression. This is why I needed a screenshot with the property value in Device Manager on your system. But anyway a regular expression like the following should work for almost any language: Remember the hard-coded values that you filled in will change if you change settings in UEFI Setup, or if you change your hardware, like adding a new GPU. So you should disable ReBAR before making such changes, then find the new hard-coded values after the changes, and enable ReBAR again |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Yes, the old v0.1 has an issue like this, and other users reported the same output. But it works. The issue was fixed later, unfortunately I do not remember what the problem was in the first place |
Beta Was this translation helpful? Give feedback.
Yes, the old v0.1 has an issue like this, and other users reported the same output. But it works. The issue was fixed later, unfortunately I do not remember what the problem was in the first place