What we need is someone who is proficient in assembly language to find the conditional argument in the orom or driver that checks those device ids and force it off so all intel boards older or not are supported.
That might work davidm71. My guess is in earlier boards, pre PCH, the alternate ID was never passed on so that the OROM firmware could use it. IOW having the correct ID will not help in this case.
If you are really curious to find out the real ID it might be possible to activate it by setting the proper register on the SATA controller, if not locked by the BIOS.
How do I get SRT working with this? Most of the discussion seems to be TRIM in RAID.
I have an ASUS P67 board as well. (but not the Evo) Controller ID 2822, Alternate ID 1C04.
NotSmart, unfortunately SRT needs more than just OROM support, which is why my first test failed, it also need BIOS support and adding that is not so simple and will vary from BIOS to BIOS.
Which software can display Trim execute status?
I need it test why Trim does not work in my IRST array SSD.
In the first screenshot, I see a software can show information like:
"Trim command completed in 0.0000x Seconds
Intel RAID 0 Volume - RAID 00x The request is not supported"
I tried HxD, it does not has feature to detect TRIM command; WinHax also does not provide such feature
Latituder, I wrote my own software for doing this and the times help not only to get an idea of trim performance but also in a case where RSTe drivers are used. With RSTe and iastorF a failed trim command gets changed to successful when reported back. Failures tend to return very quickly so by using the time a very quick response of just a few microseconds can be an indication that it actually failed.
At the moment the test software is not suitable for distribution as it has little in the way of error checking and is fixed to test just a few LBA's outside of my file system. IOW it could easily mess things up on a different system where variables are not known.
I would like to produce something that could be used by everyone and provide some certainty of trim test but the deeper I dig into it the more problems I seem to find, even RST driver bugs and SSD firmware bugs. I have not given up this idea yet but have little time to spend on it right now.
Fernando, I ran across
this
The other thing is, Fernado actually came up this about a hex editor a long time ago, and at the point when the 11.5 OROM came out, so Dufus is way behind in the times. He even posted on the anandtec forum, he should have said stop stealing his ideas.
posting as CPL0 I was asked by Yavi back in May on
hardforum how to test for trim and while using my own methods said that Winhex could be used to check LBA's. I certainly was not aware of someone having already posted this method so I apologize if it seems I was stealing your ideas without giving credit.