This is exactly what I want to hear...
I want a small SSD ~64-128GB for OS, then have the 1.2 TB array for storage after I reformat.
Printable View
Got myself M5A97 PRO and I have an issue with it - can't fully unlock 3rd core of my PII 550. It works fine as tri-core with cores 1, 2 and 4 enabled. Strange thing is that I used ASRock A780GXH/128M for two years before which unlocked both 3rd and 4th core and ran stable since day one.
What's happening - everything seems to run fine in quad-core setup, but OCCT or Prime95 Blend fail instantly. I suspected memory, but 4 hours of testing with builtin Windows Memory Diagnostics make me believe that mems are fine. What's more interesting is that I can run Prime's Small FFT for hours without errors.
I am priming for an hour as tri-core - no problems so far.
Settings I use: 200x17, 1.4 Vcore, NB@2400@1,2V, VCPU/NB = 1,2V.
Got any clues? Is it because of unlock stability thing?
The newer AGESA versions don't sit well with core unlocking - AMD has configured things for Bulldozer. I know HQ are working on BIOSes at present for all boards (the BIOSes are while off yet as they will have a few changes). The core unlocking should improve on the newer BIOSes, but ultimately the 9 series boards are very much geared towards Bulldozer first and foremost.
-Raja
Mine is 0924 CPMW, so it's not a new one. I hope it will be fixed in the future.
F.A.O. Raja@ASUS
My query is in relation to your current AMD-9xx motherboards, specifically the implementation of eSATAp. As a current owner of ASUS hardware, and a potential future customer, I would like some clarification on this feature and how it is implemented in ASUS hardware, specifically in the context of my findings outlined below.
To my understanding, eSATAp or Power eSATA combines both the SATA data and power connections into a single connector. Looking at the storage section within the specification for the M5A99X EVO motherboard, it states for the JMicron® JMB362 controller: “1 x Power eSATA 3Gb/s port(s), green; 1 x eSATA 3Gb/s port(s), red”. And in the overview section: “Power eSATA - The Power eSATA solution combines the eSATA connector and power source together, allowing you to use external SATA devices without the need of additional power source”.
This seems clear enough.
Recently, I purchased an eSATAp cable for my M4A89GTD PRO/USB3 motherboard – I am, of course, aware that this ‘board is based on an AMD 800 series chipset, however I feel that my findings have relevance not only to this product but also 900 series chipset products and, perhaps, future ASUS products.
Before purchasing the cable, I consulted the storage section of the specification in the user manual (ref. E5471 First Edition V1, April 2010) which states, for the JMicron® JMB361 PATA and SATA controller: “1 x Power eSATA 3.0 Gb/s port”. In the overview section for the motherboard on the ASUS UK website it states: “Power eSATA - The Power eSATA solution combines the eSATA connector and power source together, allowing users to use external SATA devices without the need of additional power source”. Having read both pieces of information, I felt confident that I could go ahead and purchase an eSATAp cable (not cheap) to connect my 3.5 inch HDD without issue.
As I write, I am unable to get the eSATAp functionality working on my M4A89GTD PRO/USB3 motherboard. I have tried altering the relevant BIOS settings and tried reinstalling the JMicron driver but to no avail. I have actually shone a torch into the eSATAp connector (coloured green) on the motherboard I/O panel but I could not see any electrical connectors that would indicate Power eSATA connectivity, i.e. the two tabs on the outside extremities appear to be absent. It would appear that the product documentation and marketing material (website) seem to be at odds with the product that has been supplied to me, and that is still available for sale, as far as I know.
I have raised the matter with ASUS Customer Service who, in the first instance, claimed they could not find the relevant user manual for the product, at the same time stating that the port in question was an “ESATA port rather than ESATAp port”, and in their second response – after I sought clarification – stated that: “It is a ordinary ESATA port without power pin. It is an (External Power) eSATA rather than External (Power eSATA). (External Power) eSATA: an ESATA port needs External Power.” Their second response is, presumably, in reference to the fact that the storage specification section for the M4A89GTD PRO/USB3 motherboard on the ASUS UK website states, for the JMicron® JMB361 PATA and SATA controller: “1 xExternal Power eSATA 3.0Gb/s port”. This is different to what is stated in the user manual and in the overview section of the website (see above), this being the information I based my purchase decision around.
In conclusion, I am left somewhat disappointed by the fact that there are conflicting specifications and marketing material for the product, and by the fact that my M4A89GTD PRO/USB3 motherboard apparently does not, after all, support eSATAp when it clearly states in the user manual and on the ASUS UK website that it does. How can this be accounted for? It comes across as a trade descriptions issue. Of equal concern is the fact that my confidence in ASUS products, product documentation, marketing material and customer service has been diminished by this experience. Is the Power eSATA implementation on the new AMD-9xx motherboards true eSATAp, and if so does it support only 5V devices or can it support 12V devices also?
I would appreciate your comments on this matter.
Regards
ASUS M4A89GTD Pro/USB3; AMD Phenom II X6 1055T 95W; 8GB Patriot Viper II Sector 5 DDR3 2250LLK; Crucial RealSSD C300 128GB; 2 x 1TB Western Digital WD1002FAEX SATA 6Gbps Caviar Black; 1TB Samsung F3 HD103SJ; Lite-On iHAS124; Creative Sound Blaster X-Fi Titanium HD; Noctua NH-D14; 1 x Arctic F12 PWM, 2 x Arctic F9 PWM; Edimax EN-9235TX-32; Corsair HX450; Windows 7 Ultimate 64-bit.
Two new beta BIOSes for the CVF.
Fix improves NB Core frequency stability after making changes in UEFI:
51 is with S3:
http://www.mediafire.com/file/2ni62j...-ASUS-0051.rar
52 is without S3, for extreme overclocking:
http://www.mediafire.com/file/o2a4dt...-ASUS-0052.ROM
Thats it, ive decied. When im going to upgrade im going for CVF!
Im tired of theese gigabyte motherboards that refuses to run 8gb ram with anything else but auto settings. never any bios updates either...
I'm wondering if I made the wrong choice with the Sabertooth, I haven't seen as hard of work going into BIOS updtes. I really like the board.
Any news on changes coming?
Issues so far
Can't OC past 4.2ghz with Intell SSD (can with HDD with same controller settings)
AOD does not change clocks, Fan control not working
Memory OC with G-Skill RipJaws 7.8.7 24 1600 1.6v kit is not working for me :p: CHIV F still closks this RAM much better
That is all I have seen. It has been a lot more stable then my CHIV F with the same CPU and hardware in general though.
Thanks for all the hard work ASUS!
Im working with these sticks now and they WILL take some time to get stable so far I have them at 1848 8-9-8-24-32-1T@ 1.60 volts I am working through the drive strengths systematically until they are stable and then will up the clocks a little more my goal is 1880 8-9-824-1T@1.60 with my NB above 3K. My sticks will do 1600 7-8-7 without any changes I verified that before moving on.
Hey Raja, one thing I really miss comparing AISuite II to the old AI Suite that was used on the C4F, is the ability to save the settings to Bios... :yepp:
That was a nice feature! If your team could get that to work again I'd really appreciate it!
Asus seems to be one of the few mobo manufactureres who has decent OC software (even better than AOD).
I miss the option to save Windows/OS tweaks to bios!
If your guys could add the button to "save to bios" agian under AI Suite II, I'm sure I wouldn't be the only happy camper.... :D
Dave, you are OCing with AI II? Am i dumb, I can't find Clock settings......:shrug:
On the AI toolbar click the tools button and it's the top one. ;)
The CPU Ratio button will let you change core multis too.
http://i30.photobucket.com/albums/c3...080611_Evo.png
mine doesn't have turbo evo.. must have missed it on the install
I had to do a fresh OS install to get it to work Jay.
Didn't really want to, but no matter what I did I couldn't get it working otherwise...
Bah.. crap. I guess I could reload....
is it me or CHV doesn't like psc sticks? I have 2 pair of psc sticks namely OCZ XTE Plat DDR3 2000 CL9 & Gskill Flare DDR3 1800 CL9, both having problem runnin DDR3 2000 @ 7-9-7... hmmmm... :shakes:
Did they run 2000 @ 7-9-7 on your last board ah_koo?
That seems pretty fast and tight for an X6.... Unless ofcourse you have an ES chip. :p:
Beep says my Mushkin Lovo Blacks are PSC, and I think he's right (even though they're older and I thought they were BBSE).
The best I could get out of them was ~2030 @ 7-10-7. That was stable enough for 32m SPi, but still not good enough for 24/7... :rolleyes:
yes sir, 2k @ 7-9-7 on 990X Evo was a breeze using Dom GT (ver 7.1, confirmed PSC sticks). what confused me was Flare (which supposedly optimized for AMD) should be able to do same timing on CHV without sweat, but what i got was errors in memtest (what's more P95 in windows). :(
when it comes to Ram friendliness, IMO 990X Evo is d best so far... :)
my findin on bbse & psc on 990fx boards (GD80 & CHV in my case) is d former tends to be able to do tighter timing below 2k if compared to psc. for eg: bbse managed a 1600 @ 6-7-6 (vs psc @ 6-8-6), while on 2k, bbse sticks have no issue runnin 7-9-7 w/o much tweaks which some psc sticks (like d ocz xte plat 2k cl9 & flare 1800 cl9) need some amount of workarounds > i'm still workin on this... :shakes:
That's really nice man!
I haven't done any serious testing yet, but my MEM actually seems to act a little better on the Sabertooth 990FX (compared to the C4F)...
I'm bored anyway, I'll try pushing it a little more tonight and see what I can get. ;)
My chips may not be quite as good though, they were only rated @ 1600 7-8-7 1.35v.
Might help give you a better idea if the problem lies with the C5F though. :)