1rst link of what… the links in the OP is not my posting.
EDIT: Nex time point the post number… or do you think i live just looking indefinitely to that post or its my only post on this forum???
The link is up.
Sorry I thought I quoted your post. New to this forum. I was looking for the modified nvme bios for the p8p67 ws revolution you posted to pCloud. I have a 2700k so the one with sandybridge still in it.
P8P67-WS-REVOLUTION-ASUS-2105_NVMe5stdLang.rar
Hi, its late but can you please give info waht did you do. Im new in here and dont know what to do. I have same mobo as you and i have pcie m2 adapter in 3 x16 slot.
Hi all.
So, I decided to embrace modern technology and see for myself what it’s like to have a system on an NVMe drive.
I have a SABERTOOTH P67 motherboard, so I couldn’t avoid some tinkering, which is how I came across these discussions.
Unfortunately, I found no confirmation that the firmware posted in this thread is working and does not brick the motherboard (the disappearance of user @Potter, who promised to share the results of his firmware, but never did, only added to the concerns).
I decided to analyze the structures of both the stock and modified firmware (from the first post of this thread). It turned out that the modified firmware has what is called a “Padding bug.” The modding utility may attempt to fix the firmware structure on its own (by adding or removing padding files).
Comparing1: On the screenshot, you can see that after adding a module (lines 775-777), there’s a recalculation of the remaining free space in the volume (which is normal), then a new volume begins, and the padding file disappears (line 784), which leads to a recalculation of addresses in the firmware structure of the other modules.
Whether this is a 100% guarantee that you will brick your motherboard after flashing, I don’t know. But @Fernando himself said that this needs to be checked and that firmware with such modifications should be avoided…
So, I decided to do the modding myself and added the NvmExpressDxe_Small.ffs module to the firmware, because the full-sized version doesn’t fit into our firmware.
Comparing2: This is how the structure should look if everything went well (only the differing lines are shown; matching lines are hidden)
New module lines appear, the line with remaining free space in the volume changes, and three lines with recalculated checksums are updated.
P.S. I don’t know if this information will be useful to anyone, but I decided to contribute a little as a thank you to this community, without which I wouldn’t have been able to do what I did.
small_SABERTOOTH-P67-ASUS-3602.zip
Good luck to everyone!