Due to the extremely limited space within the compressed DXE Driver Volume of your mainboard BIOS it is impossible to properly insert the NvmExpressDxe_4 or NvmExpressDxe_5 module without removing any other module.You are right - the correct insertion of any NVMe module without touching/creating a Pad-file is not easy with your specific mainboard BIOS. G1sniperz87.f4.zip (5.61 : Welcome to the Win-RAID Forum and thanks for your detaild information. G1sniper_padfile_properies.png - info about original pad-file and newly created on the upper branch G1sniper_padfile.png - selected duplicated pad-file G1sniperz87.f4.zip - modded bios with replaced SataDriver Thank you in advance, any help is welcome! Then deep inside there are guid’s that we want to update, but other than that everything looks like it should work. ![]() ![]() Gigabyte bios structure looks a bit different from the one from the tutorial, becouse it contains “Compressed section”. ![]() So I ask you to help and tell me if it is safe to load that changed bios rom or not with only “pad-file” new entry or if you have a better image for me that I could try with. So I tried another one with replacing SataDriver, and after replacing it looked well… until I checked for “pad-file” entries with uefitool… /o\ it’s the same as all the previous tries. I was about to surrender and create a post here, but after some minutes of refresh I asked myself maybe I was missing something, so i started another way to make it, and found that it could be possible to exchange NVMe module with other module that I could not need. With small variant it said “ Error in Inserting file”. Next tries were with newly posted v5 and small version, which ended the same.Īfter that I said ok, let’s try different method, so I used MMTool 4.50.0.23, with v4 and v5 it said “ file size exceeds the volume size”. I don’t want to write too much, becouse it will flood the forum, but I always want to describe as much as I can to help anybody with processing my problem.įirstly I tried with uefitool v0.28 with standard v4 module and everything looked good, until I checked saved file and found like duplicated pad-file in other branch. I tried to add drivers to the lates bios that I could find on official website, but my hope was lost, when I found additional “Pad-File” entries in new rom image. I need to add NVMe capability to an old Gigabyte G1.Sniper Z87 rev 1.1 board. But this time I must surrender and ask for your help. I rarely ask for help, becouse I try to do things on my own instead of bringing others to spend their time on my tasks. The BIOS that I produced works so far, but I haven’t installed the NVMe drive yet.Īlso the link in the first post appears to be broken, about how to compare the BIOS files in UEFItool to check for problems with the padding files.I’m writing here, becouse I used all possible methods that I could find. ![]() What are the advantages of the large one? I read an opinion on the forum that the small one might even be faster. with UBU and then tried to add the NVMe driver with MMtool but it reported ‘not enough space’, even with the small compressed driver, but UEFItool inserted even the large driver without error message, however I then went with the small one. I guess the DXE drivers from the forum have no disadvantages compared to those provided by Asrock? Thanks if there’s no specific problem with Secure Boot I’ll just use the latest BIOS version.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |