Overclock.net › Forums › Components › Hard Drives & Storage › SSD › How to get your Kingston 40GB SSD to support TRIM
New Posts  All Forums:Forum Nav:

How to get your Kingston 40GB SSD to support TRIM - Page 11

post #101 of 285
Thread Starter 
Quote:
Originally Posted by Rivethead View Post
Well I tried flashing the drive while hooked up to an older socket 939 motherboard.

It won't flash. This time, instead of not finding a Intel SSD, it tells me my SSD has "Pre - production firmware" and that I should contact Intel.

I also tried using the Intel SSD Toolbox with the hex editor fix. No luck - it says "Error reading drive"

So it looks like you HAVE to flash your Kingston SSD with the iSSDFUT to get the Toolbox to work. You can't just enable TRIM (as I have somehow done) on the 02HA firmware. I figured this would be the case, but thought I'd give it a shot.

Bottom line: I'm "stuck" (LOL) with a Kingston SSD with 02HA firmware but with TRIM enabled. But I can't use the Intel SSD Toolbox.

Oh well. This is kind of like hoping to OC to a certain speed, but only getting stability at 10% less than your target.
Sounds to me as if you have a first release firmware on your drive. Perhaps it may be in your interest to contact Kingston regarding this issue. However I would expect them to tell you that this is your problem as they do not officially support the updating of this SSD.

If it is indeed the case that the 02HD Firmware MUST be flashed for the SSD toolbox then I will make amends to the guide. However as it is, with this guide we are just looking at TRIM rather than the SSD Toolbox.
post #102 of 285
Quote:
Originally Posted by ENTERPRISE View Post
Sounds to me as if you have a first release firmware on your drive. Perhaps it may be in your interest to contact Kingston regarding this issue. However I would expect them to tell you that this is your problem as they do not officially support the updating of this SSD.
I would expect every version of firmware to have it's own designation. I have the 02HA firmware.

I would expect pre production firmware to be something like "01HA" or "02GZ"

But who knows.

My rough theory is this: when I used HDAT 2 and did the "Restore" at the DCO menu, it enabled TRIM on my 02HA firmware. But it also must have did something to make it look different than the original 02HA that the iSDDFUT is looking for.

However, I'm not technically knowledgeable enough to really know what's going on!
    
CPUMotherboardGraphicsRAM
Athlon II x4 620 Propus (not yet Oc'd) MSI 785GM-E65 Radeon 4200 (Integrated) GSkill 2x2GB DDR3 1600 
Hard DriveOptical DriveOSMonitor
Boot: Kingston SSDNow 40GB NEC DVD Windows 7 Home Premium (64bit) Hyundai 19" LCD 
KeyboardPowerCaseMouse
Logitech Antec 350W Antec SBQE Mid tower Logitech 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
Athlon II x4 620 Propus (not yet Oc'd) MSI 785GM-E65 Radeon 4200 (Integrated) GSkill 2x2GB DDR3 1600 
Hard DriveOptical DriveOSMonitor
Boot: Kingston SSDNow 40GB NEC DVD Windows 7 Home Premium (64bit) Hyundai 19" LCD 
KeyboardPowerCaseMouse
Logitech Antec 350W Antec SBQE Mid tower Logitech 
  hide details  
Reply
post #103 of 285
Thread Starter 
Quote:
Originally Posted by Rivethead View Post
I would expect every version of firmware to have it's own designation. I have the 02HA firmware.

I would expect pre production firmware to be something like "01HA" or "02GZ"

But who knows.

My rough theory is this: when I used HDAT 2 and did the "Restore" at the DCO menu, it enabled TRIM on my 02HA firmware. But it also must have did something to make it look different than the original 02HA that the iSDDFUT is looking for.

However, I'm not technically knowledgeable enough to really know what's going on!
Indeed they are usually names differently from a final release firmware. As for DCO restore changing something radical in the firmware parameters I find that difficult to believe really. Changing the firmware to the point of it being recognised as pre-production is unlikely. That's just how I see it though.
post #104 of 285
Quote:
Originally Posted by Sampler View Post
When I run the command prompt to ensure I have TRIM enabled it comes back as a 0 even though I'm currently on RAID0 Raptors as the Kingston is in my HP tablet (trying out how it improves battery performance, so far looking like a threefold increase - 1.5 hrs into 4.5hrs )
I read elsewhere that the command actually just tells you whether the controller and/or OS support TRIM but not whether it's actually enabled and working or not. I'm not sure how CrystalMark handles or arrives at it's TRIM flag...

The only sure-fire way I know of confirming that TRIM support is working on a SSD is to fill it up, delete the stuff, and then benchmark it... If TRIM isn't enabled performance would drop noticeably (as far as the benchmark is concerned anyway, real world it might still take a few write cycles before you'd notice it).
post #105 of 285
Quote:
Originally Posted by Telnet View Post
DisableDeleteNotify just indicates that TRIM is enabled in the OS, not necessarily in the drive. The real test is reading the value of Word 169 from the drive's IDENTIFY DEVICE data that really tells if TRIM is enabled or not. CrystalDiskInfo reads this value.
Ah, I wrote my previous post before reading yours, good to know... Good to have some clarification on the matter actually, I hadn't seen any conclusive info on that elsewhere. Thanks!
post #106 of 285
Quote:
Originally Posted by Rivethead View Post
It won't flash. This time, instead of not finding a Intel SSD, it tells me my SSD has "Pre - production firmware" and that I should contact Intel.

I also tried using the Intel SSD Toolbox with the hex editor fix. No luck - it says "Error reading drive"
This is quite strange, as I removed other checks from the firmware loader but left the one that checks if the firmware is 02HB, 02HA, 02G9 or 02G2. If the firmware loader tells you that your current f/w version is 02HA, then it shouldn't have problems at this stage either.

Your drive must differ from the other drives in some way, or there are compatibility problems with the other motherboard's chipset too.
post #107 of 285
Thread Starter 
Quote:
Originally Posted by Telnet View Post
This is quite strange, as I removed other checks from the firmware loader but left the one that checks if the firmware is 02HB, 02HA, 02G9 or 02G2. If the firmware loader tells you that your current f/w version is 02HA, then it shouldn't have problems at this stage either.

Your drive must differ from the other drives in some way, or there are compatibility problems with the other motherboard's chipset too.
Odd indeed. I would try flashing on another Motherboard that's for sure. Other than that I cannot think of much else other than contacting Kingston. Like I said they will likely question to how you found this issue out and then refuse a replacement.
post #108 of 285
Looking for some help. I used iSSDFUT to flash and it went perfect. Now i'm trying to use the HDAT2 utility but I don't know what it's doing. It just gives me a bunch of error messages and leads to a cmd prompt, so I can't get TRIM. (pictured) Any idea what's going on?

PC
(0 items)
  
Reply
PC
(0 items)
  
Reply
post #109 of 285
Thread Starter 
Have you typed HDAT2 and hit Enter ?

If this is not working make sure your SATA is set to IDE mode in the BIOS.
post #110 of 285
I finally updated the firmware via USB with the technique described here:

http://communities.intel.com/thread/8906?tstart=60

(replacing issdfut.exe with Telnet's version).

SSD was on an ACHI configured controller (Gigabyte) and was detected successfully.

As I had already restored DCO, TRIM was already enabled. CrystalDiskInfo confirms new firmware and TRIM.

Finally I feel relaxed and happy, safe in the knowledge that Intel have failed in their bullying attempt to deny me the full functionality of my SSD.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: SSD
Overclock.net › Forums › Components › Hard Drives & Storage › SSD › How to get your Kingston 40GB SSD to support TRIM