@scorp : Thanks for the links to both BIOSes named BACKUP.ROM and NVMMOD.ROM. Result of my analysis: The modded BIOS is not ok, because a "Pad-file" has been added at a wrong location (has obviously been done by the used BIOS tool). Here you can see the differences between both BIOSes (left pic: BACKUP.ROM, right pic: your modded NVMMOD.ROM):
Questions: 1. Who is the mainboard manufacturer and what model is it? 2. Why didn’t you use an original BIOS as source for the NVMe modification? 3. Which BIOS tool did you use?
Request: To be able to help you I need the latest original BIOS for your mainboard.
Fernando states that the mod is “valid for all Intel/AMD chipset systems with an AMI UEFI BIOS”. I’ve so far been unable to determine if my C600 Intel chipset qualifies. This is a dual processor motherboard with a pair of Intel Xeon E5-2687W (8-core) processors. The current A16 bios, like previous versions, allows a selectable boot list option of either legacy or EUFI.
I have always used the default setting of ‘legacy’. If I select EUFI, the boot devices disappear from the menu, and I now have the choice of ‘Add Boot Option’ or ‘Delete Boot Option’. The Add option produced a warning of ‘File system not found’. The Delete option does nothing.
I would be delighted if someone else has been able to mod this bios for NVMe and could steer me in the right direction.
Hm, strange, BACKUP.ROM is the one I read from the flash and NVMMOD.ROM is the patched one on top. I’ll take a look once again. So far, to your questions:
1) The mainboard is from Acer Veriton M4620G, as far as I know, it is the same as ECS B75H2-M however I can’t find any official ROMs for that model. Probably it was OEM only, so I have to stick on what is in the flash IC. 2) I also found another version on Acer forums and also tried that without any success. I’ll take a look once again at BACKUP.ROM vs NVMMOD.ROM, not that I mixed the backup and the one from forum as a basis. 3) If you mean patching, I used UEFITool (Linux through wine however), for flashing I used AFUDOS
That is strange, I just tried it once again. As far as I try to insert NVM module into BACKUP.ROM, I’m getting that Pad-file thing. All the DXE-driver parts are in a compressed section, but in your how to, they aren’t. Could this be a problem?
P.S. let’s assume, that BACKUP.ROM is the latest version of BIOS I have (except someone here knows how to get the ECS version of it).
@scorp : Meanwhile I found >here< a download link to the latest original BIOS named P01-A2.2M dated 02/27/2013 and I hope, that it is exactly for your system. The related BIOS is attached. Interesting find: The attached original BIOS contains a Pad-file at the same location as your modded BIOS.
@Guswah : I have moved your 2 posts, which you had posted within the "Storage Drivers" Sub-Forum, into this much better matching thread. Now to your request: After having set the BIOS to boot in UEFI mode, you will not see any bootable device unless you add one, which has been prepared for being bootable in UEFI mode. Please let the tool Rufus create a bootable FAT32 formatted USB flash drive with Win10 on it and choose the "GPT" partition scheme. Insert it, enter the BIOS and choose the "UEFI boot" option. Now you will see the USB Flash Drive as bootable device.
Yes, this is exactly the one I mentioned. I tried that one also with the same result, however your observation is interesting. I’ll try once again to patch this instead of BACKUP.ROM and see what I’ll get then. Thank you very much!
@scorp : The structure of your "BACKUP.ROM" and of the original BIOS, which has been attached by me, is completely different. The "DXE Drivers" of your BACKUP.ROM file are located within the Volume number "03:02-00", whereas the same files are located within the Volume number "02:01.00" of the previously attached original BIOS.
Sorry, I suppose, I was a little bit confusing. You are absolutely right, my BACKUP.ROM has different structure from the one you’ve sent, because the one is the original from the flash and the other is from the forum. However, by “the one I mentioned” I meant, that this BIOS which you found, is the very same one, which I also found on that forum and I tried the NVM modification on that also. It seemed not to work there either, or better to say, I see no difference in the BIOS settings regarding NVM. Anyway, I’ll try to redo the modification on the BIOS you’ve found once again. May be I was blind or just stupid
As a newcomer, I’m a little confused in this process. I’ve made the Win10 USB drive with Rufus – great. And just as Fernando says, inserting this solves the problem with BIOS recognition of EFI.
Where I’m confused now is that if I boot with the USB stick inserted, the system wants to install Win10 (to the old hard drive, of course). But the point of this is to create a bootable NVMe. Is this just a sacrificial installation to the old drive? Not sure, so I’ve aborted at this point. Next will come the issue of creating folders … which suggests that an OS is present, but of course it’s not. I checked out the UEFItool on a separate computer. The UEFItool app is looking for a raw BIOS file. Where does someone normally get that? (I flashed the current BIOS in the target computer from an .exe file – I doubt that UEFItool is looking for an executable file.)
@Guswah : As first step you have to insert the NVMe module into the original “pure” BIOS file. If the manufacturer of your mainboard just offers a complete BIOS Installer (as *.EXE file), you have to extract the real BIOS file from it. If you don’t know how to do it, please tell us the manufacturer and the model of your mainboard and give us a link to the Installer.
@Guswah : Since the question “How to extract a certain DELL BIOS” has nothing to do with the topic of this thread, you should better have a look into >this< specific thread, where you can find some solutions. If you have any additional question regarding the extraction of the “pure” BIOS file, please post it into the linked thread.
@Salvatore21872 : Welcome to the Win-RAID Forum! I do not modify any BIOS upon request. That is why I have written the related detailed guide about how to do it. The modification of an ASRock AMI IV UEFI BIOS and the flashing of it (after having removed the capsule via the UBU tool) is very easy. Good luck! Dieter (alias Fernando)
@scorp : Since the correct modification of your specific BIOS seems to be very tricky regarding the Pad-file, I have attached a BIOS, which has been modded by me on the basis of the original BIOS without touching the related Pad-file. You can flash this BIOS at own risk. Don’t forget to rename the modded BIOS and to flash it a proper way. After the successful flash of the modded BIOS you shold see a Disk Drive named “PATA” or “PATA_SS” within the “BOOT” section of the BIOS. Good luck!
Thanks a lot once again, however, unfortunately that seems also not to work. Just flashed the image and there is nothing regarding “PATA” or “PATA_SS” in the list. Also my operation system doesn’t see the drive… may be it just doesn’t work on this mainboard I’m still waiting for m.2 to SATA Adapter to check if the drive is working at all.
@scorp : Thanks for having tested the BIOS, which had been modded by me. It is a pity, that it didn’t work either. Questions: 1. How did you flash the modded BIOS? 2. What makes you so sure, that the flashing procedure was successful? 3. How is the NVMe SSD connected to the mainboard? 4. Do your BIOS settings allow to boot off devices in UEFI mode? 5. How many other HDDs/SSDs are running within your computer and to which ports are they connected?
You cannot connect an NVMe SSD to a SATA port. That will not work.
However, to your questions: 1) From a freedos usb stick, running: afudos FERNBIOS.ROM /p /b /n /r 2) I read the ROM from the flash again and looked if the NVM module is there 3) PCIe x16 slot with a m.2 adapter in it 4) I do boot using EFI into my OS all the time 5) I have two SATA connected, one SSD and one mechanical SATA drive
@scorp : Thanks for your additional information. To exclude, that the NVMe SSD is not detected by the BIOS, because the related PCIe slot uses the same data transfer lanes as any of the SATA ports, I suggest to temporarily unplug both SATA connected Disk Drives and to look, whether the BIOS detects the NVMe SSD under these conditions.
I’m still waiting for m.2 to SATA Adapter to check if the drive is working at all.
I thought something like this will do: