@Sierra
Try this BIOS for Gigabyte GA-P55A-UD4.
This build was created for NVMe ven_1344 dev_5405.
I am not responsible for the BIOS firmware.
p55aud4.rar (813.5 KB)
Hello @Dagal
Thank you very much for being so kind of providing me a modded BIOS for my board
Due to my job I’m away from home until friday and can’t do any testing until then.
So I will test the file this weekend and tell you if it works.
Hello @Dagal
I returned from my business trip yesterday and flashed the BIOS file you kindly provided to my board and tested it.
Turns out I have partial success using this file
The NVMe gets detected by the BIOS and somehow it’s even possible to boot into Windows from this drive.
But the problem is, it’s booting very, very slow. It takes about 4 minutes until I see the desktop.
Crosschecking with another Board proves that the SSD is not faulty.
When installed to an ASUS P7P55 LX with modded AMI BIOS the same drive boots into Windows within seconds
So what is going wrong here?
How can boot time be improved?
Would you please tell me what you did different than me to get the drive even detected in BIOS in the first place?
Hello,
I am trying to add an nvme module to the bios of my gigabyte “GA-P35-DS4 (rev. 2.1)” motherboard. I enter vid and did with opromcfg.exe and save them. Then I add the PCI module with cbrom. But the disk does not appear in the bios. I think award bios and gigabyte are problematic in this regard. The last point I noticed in my research is that NvmeOpRom.bin is 8kb, while the nvme modules I see on this site are 18kb. Even the nvme module made in Sierra’s bios is the same way. This is the last point I came to and got stuck in my research in my free time from work. What should I do after modding with opromcfg.exe? Where does this data size difference come from? I would be very happy if there was a source link or an explanation on this subject.
Although I do not have enough knowledge about modding bios, I would be happier if you could guide me on how to do it rather than making a modded bios. It is fun to deal with and spend time with the Bios mod.
Thank you.
motherboard “https://www.gigabyte.com/Motherboard/GA-P35-DS4-rev-21#ov”
original bios file “https://download.gigabyte.com/FileList/BIOS/motherboard_bios_ga-p35-ds4_f14.exe?v=05708e6b4ecca86aa34e96264113d1b8”
The modded bios I found except nvme is “P35DS4_mod2_15b”
PCI vendor ID 1C5C Device ID 1327
oprom I created
“NvmeOpRom”
Hello @cmz
Didn’t notice the difference in file size until I read your post,
but yes, in the BIOS @Dagal provided, wich is partially working for me,
the oprom has 17,5kb instead of 8kb
@Dagal did you use a different file than NvmeOpRom.bin of the start post?
Could you please specify the site you’re referring to?
Personally I haven’t seen any NVMe Modules of 18kb file size yet
(except the one in Dagal’s BIOS)
Same opinion for me.
For my personal understanding, the effect of learning something
and to solve possible future upgrade wishes by myself I would highly appreciate a detailed How To - Guide
Also this would be a great help for anyone with the same problem who might read this thread in the future
Is there anyone who’s been succesful with this mod on an Award BIOS / Gigabyte board
who would be willing to share his experience?
The procedure you all understood… the thing is this was developed/tested, aiming primary AMI8 core bios.
Users of Award bioses suffers the same “instability” results, just by trying basic mods like updated Oprom modules or cpu mcodes, the NVMe induction is not different.
Then the most unexpected results, is how each OEM Award bios version/release/mb model reacts to all this, against a modern tecnology/controller/modern OS… speaking for myself, i can say that there’s no “stable” method of expected results on AWARD bios mod users, regarding guidance.
We do see better results/expectations on AMI8…
Its only my opinion, good luck for both.
But the SEC 950 PRO has its own OpRom embedded, still its only loaded by UEFI environment, the mod in legacy bioses is still needed to add its ID, if i’m not mistaken.
EDIT: Correction in the above 2 posts.
OPROM from Samsung 950 PRO just had the ability to boot in an environment without UEFI. For each bios I edit ven dev NVMe and checksum.
@Sierra
You can make a mod from the Experimental NVMe mod, but I don’t think anything will change.
Which PCIe version is used on GA-P55A-UD4 and ASUS P7P55 LX?
AFAIK the Option ROM modules (incl. the NVMe one) are not used at all while booting or running the OS in UEFI mode. They are only needed while booting in LEGACY mode.
Users of a Samsung 950 Pro SSD can boot their NVMe SSD in LEGACY mode (due to the NVMe Option ROM within the SSD’s Chip), but to be able to boot in UEFI mode, they need an NVMe EFI module within their mainboard BIOS.
Thats it Fernando, you recall me, i was wrong, so my point was to prove in this case and correct if im wrong, users don’t need modding Legacy bios, if they get a 950 PRO?
But do need the mod for disk outside this one or both in editing the ID just like Dagal stated?
No, they don’t need and should not do that.
Only the NVMe Option ROM needs the HardwareIDs of the NVMe Controller. The NVMe EFI modules do support all NVMe Controllers (the manufacturer/model of the SSD doesn’t matter).
1 Like
hello @Sierra
Actually, the ROMs we both mentioned are the same size, the 17.5 KB visible in your cbro and the 18 KB visible in my windows explorer. I apologize if there was any mistake about this.
There are examples in the cbrom image shared by Fernando in section 5.
Hello everyone
Thank you
AFAIK it’s PCIe Gen 2 for both
I did some tinkering:
I’ve got my hands on an old 950pro 512GB drive, which is supposed to work without modding the BIOS due to it’s onboard OpRom.
I gave it a try. It’s working perfectly fine with (unmodded) AMI BIOS, but when I installed it to my Gigabyte board somehow I wasn’t even able to get into BIOS menu.
After POST screen it leaves me with a blank screen and a blinking curser in the top left corner.
Very strange behavior
(BIOS was original / not modded when I tried the 950pro on the Gigabyte board)
But however, with this drive in my hands I was able to recreate the route @Dagal went
First I dumped the ROM of the SSD to a bin file using a Linux system.
After that I opened the RomDump in HxD Hexeditor.
There seem to be two OpRoms in that file. Maybe one for Legacy and one for UEFI ???
I’ve noticed that the Checksum-8 of this file is 3F
I assume it should be 00 ?? Maybe that’s the reason why the Gigabyte board freezes with this drive installed? But then, why does it work with the ASUS board / AMI BIOS ??
First attempt:
I’ve changed Vendor / Device ID to match my Micron drive manually and corrected the bit at offset 0x45FF to match the original checksum of 3F
Trying the Micron SSD with this file patched to BIOS gave me the same result as the 950pro (blank screen / blinking curser)
Second attempt:
For the second try I’ve removed all the code behind 0x45FF, which I assume is the second “OpRom” stored in this file.
Doing so resulted in Checksum-8 = 00
Comparing to extracted NVMe.bin from the BIOS file provided by @Dagal proved me that I’ve created a perfect clone of Dagal’s file.
Patched second 950pro mod to my BIOS and violá:
Micron NVMe is recognized in BIOS and is bootable.
But, however, still with very slow boot time comparable to an ancient IDE hardrive.
That’s frustrating! Why is it that slow ??
My original dump of the 950pro rom has a file size of 32kb
Removing “unnecessary” code as mentioned above reduces the file size to exact 17,5kb
So I guess the files you are referring to were created the same way
In fact, not all NVMe works well on older boards. You mentioned that you have a samsung 950 pro or another NVMe (not Micron), prepare a mod for it and see the result.
Hello, I have an Asus P6T and I would like it to boot with my nvme…
I have updated the bios of my motherboard with this rom
2022/ASUS P6T NVMe SSD BIOS MOD (TEST OK)
but I think I am missing insert this : PCI\VEN_1E4B&DEV_1202&CC_0108
my ssd nvme is this : DiskNVMe__Acer_SSD_FA100_256GB
can you help me ?
do in have to pay something for this work ??
let me know !
Thanks
@c3rb3r0 Welcome to the Win-Raid Forum!
To be able to help you we need to do a look into
- a) the latest original BIOS for your mainboard and
- b) the modded BIOS you have recently flashed (your posted link doesn’t work for me).
Please attach both BIOS files or give us links to them.
The HardwareIDs of the in-use NVMe SSD Disk doesn’t matter, but the HardwareIDs of the NVMe Controller has to be within the NVMe Option ROM before you are going to modify and flash the BIOS.
No, but you can give a donation to the person who may do the work for you.
Good luck!
Dieter (alias Fernando)
this is the last bios version of my mainboard:
http://www.tecnicobenidorm.com/site/P6T-ASUS-1408.zip
And this is the link of the bios i recented flashed but doesnt work:
http://www.tecnicobenidorm.com/site/2022_ASUS-P6T-1409-NVME_M.2_SSD_BIOS_MOD.rar
password rar : ismailTPC_Hastanesi
Thanks a lot !! i will give a donation to the person who do this work.
Hello @c3rb3r0
If you want you can try if this works for you
ASUS-P6T-1408_NVMe.zip (985.4 KB)
BIOS modding and flashing always contains some risks.
I am not responsible if something goes wrong.
With best regards
Sierra