Printable View
Good day-
I current run a P6T Deluxe with a i7 920. Because of the way things are, I need to be able to have the computer suspend to S3. However, the P6T board I have does not come out of S3 correctly 95% of the time. I understand the Gigabyte boards have the same issue.
My question: are there any X58 boards that actually do NOT have any issues with S3 suspend?
Thank you,
Chris
I have used the P6T Deluxe and the eVGA X58 and both do not S3 correctly. The Asus will go into S3 once per boot and the eVGA won't do S3 above 180 BCLK.
Anandtech reported that the eVGA Classified does fix the suspend issue that the previous eVGA x58 board had. I'm not sure about others.
The Foxconn BloodRage with the P06 BIOS is supposed to go S1 & S3 and wake up fine.
I will give it a go later on with Windows XP for starters and 220MHz BCLK.
The resume with Gigabyte is broke when HT is off, when it's on all is fine.
My Gigabyte works fine. EX58-EXTREME with Windows Vista, but seems borked with Server 2008.
Never tried turning HT off.
I think the main concern with S3 is overclocking period, HT technically shouldn't have anything to do with it.
I wish it was that easy for me... I'm have everything at default settings and S3 still doesn't work for me.Quote:
Originally Posted by ReverendMaynard
Thank you all for the comments. If Asus can't figure out what's going on, I'll have to try another board. I would assume S3 would just work at this point but I guess not.
Does someone tested the S3 on Asus Rampage Extreme II?
I don't understand why S3 is so neglected by board manufacturers. I find it essential for my way to use the PC, especially with modern computers that get at least 150 W when idle from mains.
I think my grammar checked went bonkers when it scan the thread title! :D "x58 board that suspends properly"
I would kinda expect/accept this with a board that costs say $50 but these boards are costing in the $200-$300 range and should be the cream of the crop.
I plan to stick with my Asus boards as they've been great and this seems to be a fairly universal issue with x58 so hopefully it'll be resolve eventually.
Look to DFI for that, S3 functions work great on both UT and DK X58 series.
Yes, absolutely.Quote:
Originally Posted by Schlotkins
many of the posts in this thread are incorrect, here are the facts based on my testing S3 SM on seven different x58 boards over the last 5 months.
note: "properly" is defined as going into and resuming from SM at any BCLK, and HT can be either enabled or disabled
the short list of boards that unconditionally do S3 SM properly are:
Gigabyte ex58 UD5 with F5E BIOS. Other BIOS work only if HT is enabled.
DFI UT Lanparty T3EH8
Boards that do not do SM: (always hangs with blank screen upon resume)
Giga ex58 UD3r
MSI Platinum SLI
MSI Eclipse
DFI LP DK T3EH6
The Biostar Tpower x58 is a special case...it seemed to work, except it would randomly fail SM after working for a number of resumes. Typically, I could reset my BIOS and it would start working again, but always would eventually fail. Once it failed, it would always fail until reset. I tried three different BIOS including the latest on the Bio website. This could be a bad board but I sent it back in favor of the giga UD5 since the UD5 always works.
Above all, the DFI LP DK was the biggest disppointment because it was reported to work, it didn't. Smart fan also doesn't work, and the DK has the worst AC characteristics of the seven I tested. The UD5 has the best AC, just a hair better than the Biostar. In fact, it was so close I'd call it a tie. Biostar tech wrote me to say that they reported my S3 experience to their design team and they'll try to reproduce the failure.
Except for the Biostar, the success or failure is 100% repeatable. That is, if a board fails at 'X' Bclk, it always fails. In the case of the two working boards, they always work right 100% of the time, any Bclk.
As to the Giga UD5, using the F5E BIOS isn't a restriction because there is no bad side effect of the BIOS, it works as well as any of the others that have the "HT on" requirement, so just use it.
Just did a test on the Foxconn BloodRage with the P06 BIOS, a i7 920 and Windows XP.
Booted at 220MHz BCLK and set it to sleep ( STR aka S3 ).
Pressed the power button to power on again and it worked fine ;)
I have the giga UD5 and am running F5e Bios and it does suspend correctly now but I have to wait 30 seconds before waking or I will get the blank screen issue. I have seen this come and go with different BIOS since the board came out. If it matters My i7 is overclocked to 4.095 with HT on.
Terlcartman...for a while, I too was having extremely long resume times, 18 seconds. Others were reporting 5 second times with the UD5.
I reformated and reinstalled Vista and poof, problem solved. Since then, 5 second boot times with the UD5. And I haven't seen that HT has any affect on resume time. BTW, SM works on win7 just as it does under vista, 4.5 - 6 seconds resume.
Useful info, thanks for the post.Quote:
Originally Posted by BenchZowner
How many seconds till desktop reappears? Also, are there any bad side effects with the P06 BIOS?
I don't know of any ASUS x58 that does suspend properly. Pisses me the F off too.
:rofl:Quote:
Originally Posted by Brahmzy
No Asus board period I've used does S3 suspend correctly period. They are all broken and Asus choose to ignore this and not fix their AMI bios code time and time again. Their guys have known it's messed up for a while and well...it's still broken to this day.
I don't have any problems at all with S3 on either my p5k-e and p5k-deluxe, hardly ever do full power downs on them, always put them to sleep.
Perhaps it wasn't broken until after P35 then. The P45, X38, X48, X58 boards I've used had broken S3 resume.Quote:
Originally Posted by highoctane
I have no problems at all with the P06 BIOS.Quote:
Originally Posted by roller11
Average wakeup time is approx. 2.5s
Here's a video of the BloodRage booting at 220MHz BCLK, then going into S3 ( Sleep Mode ) and then back into Windows.
ahhh bench you always just lay it out how it is bro. Love it.
My Asus P5E with X38 never resumed correctly.Quote:
Originally Posted by mikeyakame
My Asus Rampage Formula (X48) resumes correctly the 80% of the times.
Nobody knows how Rampage Extreme II resumes? Never, half of times, nearly every time...
Thank you all for the replies. I am really surprised all of these boards are having problems. How are they allowed to put an energy star logo on these boards when they can't even suspend properly?! Asus is supposedly trying to 'reproduce' my problem, but it seems to be widely known so I'm not sure why they are surprised. It looks like I'll have to move to the DFI board.
The S3 performance of the giga UD5 is exactly the same as the DFI UT Lanparty. Both handle SM flawlessly, every time, at any Bclk, with HT either on or off. And the resume time is 4.5-6 seconds on both boards. I used the DFI for about one month, the Giga for 2 months.
My results are exactly the same as others who have reported S3 performance, read
through the posts on the giga UD5 thread. Of course the DFI UT Lanparty works too, but has a couple of significant draw backs:
Smart Fan doesn't work at all, the AC characteristics are slightly worse than the giga especially at low voltage, and the 1366 socket is ill-placed.
All and all, the DFI is a good board, but not the equal of the giga UD5. And whatever you do, DO NOT get the DFI DK lanparty...it's the
motherboard from hell, broken sleep mode is just the beginning.
Thanks roller11. I just heard back from Asus support and they say they can't duplicate any sleep problems so it must be something on my end. This seems like a fairly common problem with this board so I'm a bit taken aback by that statement. Oh well.
This is how much Asus's technical support dpt. is worth:Quote:
Originally Posted by Schlotkins
http://www.benchzone.com/datas/users...l-score--1.jpg
( Clicking on the image transfers you to the related article )
Tell them to do 200bclk and they have to resume twice. It will go into S3 and then wake up ONCE. The second time you S3, the screen will go black and your vid card fan will go full blast.Quote:
Originally Posted by Schlotkins
I'm not sure how you got in touch with them to try and replicate the issue. When I tried, they told me they had no way to contact the BIOS department.
I just wanted to let you know that F5d bios for the UD3R appears to have fixed the S3 resume issue. I have not had much time to try it out but appears to work correctly whereas F5c and earlier did not.
http://forums.tweaktown.com/f69/giga...st-bios-28441/
Of course SM works.....if you cripple the performance by underclocking the board to 133 Bclk.Quote:
Originally Posted by Schlotkins
I too got the UD3R to work, but only if I underclocked it. What Bclk value did you use in your test?Quote:
Originally Posted by jcotran
Funny, my P5E x38 works perfectly, heavily OC'd.Quote:
Originally Posted by Brama
My P5Q-E p45 works perfectly, heavily OC'd
My P6T WS Pro x58 doesn't even try to work. It sucks.
I am using 21x196. Like I said only briefly tried it out but plan on testing it further soon.Quote:
Originally Posted by roller11
I had the same problem with my Rampage II Extreme. If I did as little as a single reboot (Vista 64), it wouldn't resume after S3. It was completely unrelated to overclocking. Once I figured it out I could reproduce the problem 100% of the time. I contacted Asus and they gave me a fix. Since BIOS 1104 S3 works perfectly (for me).
Running at 21x200 on my evga x58 i get the black screen if it tries to resume. I just turned off the ability to let it hibernate because if i happened to forget and it suspended i'd have to do a hard power off which usually resulted in an angry windows boot up.
GA-EX58-UD4P resume is fine here at 190-210 Blck with the latest BIOS (F7e)
So it appears they should have all the X58 series corrected, if they have not already
I'm expecting to see all the Award BIOS based x58 boards to be able to suspend to ram ( S3 ) and wake up properly with the new BIOS releases ;) ( that's a hint, not a 100% one, but a 95% one for sure ) [ I'm not just making an educated guess ;) ]
I'm going to assume with my luck that my Asus board does not use an Award BIOS...Quote:
Originally Posted by BenchZowner
We have been working ASUS and they will have BIOS releases for the P6T, P6T Deluxe,and Rampage II Extreme shortly that address the S3 resume problems, especially those with BCLKs over 170. The BIOS releases are in validation now but I can tell you at this point, they all work. ;)
I hope Evga will do the same with their boards as well.Quote:
Originally Posted by bingo13
Nice! Please keep us informed of their progress.Quote:
Originally Posted by bingo13
Supposedly on the eVGA X58 SLI, the S3 bug at 183+ BCLK is hardware related and cannot be fixed via software. The classified fixed this issue.Quote:
Originally Posted by Big Myke
dfi ut has no problems
just make sure to install the inf patch for usb devices
That's great to hear. They actually provided me a beta 1401 BIOS (build date is 3/13) but it didn't help me unfortunately so I'm hoping it's later than that. :)Quote:
Originally Posted by bingo13
Thanks,
Chrs
I have the Gigabyte UD5 (F5 bios) and my CPU is overclocked to 4.0GHz with HT off. When I resume from sleep (S3 suspend), all I get is a black screen. I have not tried if the same happens at stock settings (or with HT on) and really need to get the sleep function to work properly. Using Vista Ultimate x64 and not too keen on reinstalling the entire OS.
Any help would be much appreciated. :)
My BIOS builds are from 3/20, it has been a long road though to get to this point. ;)Quote:
Originally Posted by Schlotkins
Can any of these builds be provided to the public for evaluation? (I understand the risks.)Quote:
Originally Posted by bingo13
That's good to hear. I'm looking forward to it being released that's for sure! :)Quote:
Originally Posted by bingo13
That makes two of us, really looking forward to this issue being resolved!! :up:Quote:
Originally Posted by Schlotkins
DFI, MSI, EVGA, Gigabyte...all have boards that can't do SM because of bclk limitation. All have tried to fix the bug with updated BIOS, all have failed. Clearly, it's a hardware deficiency, not fixable in BIOS. Now there's is a rumor that ASUS has done a bios that will allow their boards to do S3 SM, reliably, at any Bclk up to the limits of the CPU, with no side effects. I wouldn't get my hopes up.
Any news on whether there will be BIOS updates for Gigabyte as well? Can't get S3 resume to work with my EX58-UD5... :(Quote:
Originally Posted by bingo13
My ASUS P6T WS Pro just got a brand new BIOS today (0602) and S3 is still broken at BCLK 211. :(
Works fine at stock clocks.
The latest Beta, as well as a few before it resume from S3 just fine in the UD5 >>Quote:
Originally Posted by PC_User
http://forums.tweaktown.com/f69/giga...st-bios-28441/
This is of course only if your overclock is stable though.
They are working out a few more bugs with Qflash, and a newer AHCI BIOS and then I believe the next Final will be ready
Thanks for the update. I hear that the S3 problem kicks in when there is a bclk over a certain amount. There's also apparently a problem with Q-Flash and the F6E bios.Quote:
Originally Posted by Lsdmeasap
I guess I'll just wait until the next final BIOS...hopefully it won't be long.
Yes S3 is closely tied to your overclock, they are trying to work it out. My Boards BIOS they have finally got it, I can resume at any Blck (Only used 190-211 though)
And yes, they are still working out the Qflash issues as well. That is not a reason to not use a newer Beta, just keep in mind if you want to go backwards in revisions you will need to use FlashSPI. I'm using the latest Beta, guess I should test if the Qflash issue is present, but I have not found a reason to go back so I just had not tested that yet.
If S3 is that important to you, I would advise you try out the latest Beta. Or like you said, you will need to wait for a final
The weird thing for me is I can't even get it to work on defaults. Is that unique to me or do other people have problems even at stock? Probably not a lot of people have tried that here. :)Quote:
Originally Posted by Brahmzy
This is incorrect, the S3 problem does not "kick in " at a certain Bclk on the UD5. It does on most other boards, so people paint the UD5 with the same brush as these other defective boards, guilt by association I suppose.Quote:
Originally Posted by PC_User
Qflash doesn't work with F6E, but this is a non-issue because there is no reason to change away from the F6E. Even if you decide to change, you can do so easily, just use @bios, a util on the giga site. I did this myself and it is actually easier than using Qflash.
There's no such thing as a 'final' BIOS. What you are refering to is the next bios that does not have a lower case letter after the numeral and even if such a bios appears, there is no reason to think that it won't have the S3 bug.Quote:
I guess I'll just wait until the next final BIOS...hopefully it won't be long.
There are only bios that work and bios that have a severe bug. People have told you time and again that the solution to your problem is to use one of many bios that are bug free, available, and will totally solve your problem. You then say, with no explanation, "no, I'll stick with the defective bios that has this bug", and then continue to complain that S3 doesn't work on the UD5. If you want to deliberately cripple your board by choosing to use a defective BIOS, that's your choice, but you should stop posting on this topic.
My only complaint about the UD5 is that EIST doesn't work right. When enabled, it doesn't lower Vcore as it should. This feature does work on other mobos, like the MSI, Biostar, DFI, etc. so there's no excuse for Giga to botch this. Actually, EIST does work, but only if you underclock your CPU down to 139 Bclk, an unacceptable penalty to pay.Quote:
Originally Posted by Lsdmeasap
Gigabyte tech support is in denial about this bug. They claim that as long as a feature works at 'some' Bclk value, however low, they lack the will to fix it within the normal Bclk range. Do you think this bug can be fixed with a bios change, or is it a hardwired into the boards logic? EIST is an extremely useful feature because it results directly into decreased fan noise, or at least it does if it works.
Why is only the F6A bios listed on Gigabyte's website?Quote:
Originally Posted by roller11
Good question. If I were you, I'd contact tech support via Email. They have been very helpful with my inquiries, alway get back to me in one business day.
Is there any ETA on the Asus BIOSes? Thanks!
This bug frikin sucks!
Someone found a workaround for the Gigabyte boards, might want to give it a try on Asus and others that have the issue.
SourceQuote:
I had to go into the power settings and change Hard Disk > Turn off hard drive after and change it to never. I do not prefer this setting because the HD does not go into sleep mode but oh well. It works.
So if HDD isn't off, it isn't in SM.
But it's a moot point because SM works on the UD5, UD4P.
Yes the S3 works on the Giga board but the Turbo mod went back to default isnt it after wake it up ? ( x21 back to x20 after wake it up )Quote:
Originally Posted by roller11
Did I miss something ?
No, the turbo mode remains at 21x after S3 resume.Quote:
Originally Posted by Sparda
Hmm that wierd. I did saw this problem when using f6g. Turn off turbo since then since my cpu capped around 4.2 without pumping more juice.Quote:
Originally Posted by roller11
I agree, sadly! I was happy to see S3 working for the UD4P with BIOS F7e onwards, not because I use it but just because it means progress is being made for others.Quote:
Originally Posted by Sparda
But, you are correct. I just tested with my board using F8a and Multi drops from x21 to x20 after a resume.
I will pass this along to the BIOS engineers, they may not be aware of the issue yet as I just noticed it due to your posts
I have a UD4P and if I set turbo mode in bios, I get 21x multi before and after S3 sleep. i.e. sleep has no affect. However, ET6 has exactly this bug you describe. If I change bclk using ET6, multi always drops instantly to 20x and there is no way to restore it to 21x other than rebooting. This bug can prevent you from attaining your max OC cause often a board will hang in the boot process, whereas once in windows, it is stable enough to get a validation. And there's no work around cause setfsb doesn't recognize any x58 giga board.
Quote:
Originally Posted by roller11
Come on man, you're so sure of that?
ICS9LPRS18BKL with setfsb works perfectly.
Just tried the "Sleep" function on the Blood Rage, works perfectly. I wish I had tried it before, saves so much time booting up.
Quote:
Originally Posted by roller11
Ya, I thought so too until I checked the real CPU Multi with Uncleweb's tool i7 Turbo.
http://www.xtremesystems.org/forums/...postcount=2579
Have you checked with this tool? I am using F8a BIOS by the way, seems to me it drops to 20 no matter the Blck after a resume, but I have only tested S3 at 190 and 200
Ya, I did notice the issue you are describing with ET, but that is not what I am referring to though.
The best way to check is to run superpi. If before and after runs are about the same, the multi isn't changing. I'll have my UD4P up on monday or tuesday at the latest (5/4 or 5/5/09) and I'll prove conclusively what's happening with the multi.Quote:
Originally Posted by Lsdmeasap
Really? That's huge if true, I'll know in a few days when I reinstall my UD4P. Now my only complaint about the UD5 is that EIST is broken.Quote:
Originally Posted by ReverendMaynard
Quote:
Originally Posted by roller11
OK, I will do that right now. I assure you it goes to 20, at least on F8a, I did not realize this until I was using F8a so I did not test F7e. I might test it later this week.
Will edit this post with pics of before and after with i7 Turbo tool and SuperPi ran for each
*EDIT*
Not a huge PI difference, but it is for sure a difference and you can see several programs also pickup the multi drop as well. Easytune was never opened and is removed from startup by StartupCPL and ET's own menu in the toolbar, so no part of it is loaded ever without starting it manually.
Click Images to enlarge
Before S3 (21 Multi BIOS F8a)
http://img27.imageshack.us/img27/969...ores3small.jpg
After S3 (20 Multi BIOS F8a)
http://img87.imageshack.us/img87/517...ters3small.jpg
I have reinstated my UD4P and just as I said, I get full 21x multi before and after S3 resume. The 'turbo' tool works great, BTW. I'm using bios F7E. The screen shot is after I resumed from S3 sleep mode. I have no idea why you are disengaging 21x when you resume, but this is not normal. I've had three different UD5s and now a UD4P, and they all retained 21x after SM. Try F7e, and if we still get different results, , upon request I'll install F8a and see what happens.
I didn't attach screen shot because attachments don't seem to be working right now.
Rev,Quote:
Originally Posted by ReverendMaynard
I don't see ICS9LPRS18BKL on the setfsb clock gen pulldown, I'm using setfsb_2_1_100_0. I see something close, ICS9LPRS918BKL, which semi works. That is, it finds current fsb correctly, but any adjustment up or down results immediately in bclk=210. From there, I can go down only to 209, or up as high as I want. So it does work, but you're limited to Bclk=209 or greater.
Is ICS9LPRS18BKL the correct part number? If so, how did you get it?
K, Roller! I will go back to F7e, I do not mind at all, just always trying the latest and S3 worked in both. One thing I can say about F8a though for those interested the voltages seems to be alot better, meaning the Vcore is tighter to what you set and the dram is spot on what you set.
Back to F7e tonight it is then, if this F7e works correctly I will report to Gigabyte. Which only means prolonged S3 issues again for F8 beta's onward, but hey at least it is working now so they are getting close.
Roller, you still get double/triple boots at startup? I always have, and I can really tell bad due to my GFX Fans and Tracer ram
Yes, multiple boots on UD5 and UD4P. Depends on how close I am to a bad OC. Also, I find that I cannot boot into windows at the same OC that I can validate. That is, if the max
I can boot into windows is X Mhz Bclk, I can then use setfsb to get another 2-5 more Bclk once in Vista until I lock up. That means I cannot reach my actual max OC unless I do it on the fly in Vista.
Since ET6 is broken, I must use setfsb. Is this the case with you?
As to using F8a, do you find the tighter voltage helps OC, or is it merely a convenience because you don't have to compensate for the inaccuacy ?
Ahh, glad to hear I am not alone. I get them stable or unstable, anything over 190 Blck (Haven't used less much so not sure where it starts).
I can boot in at 220, but not 222. I do know what you mean though, there for a while I had to boot at 215-217 until I found the culprit, which ended up being IOH on my board, needed 1.36+ for 220 Blck boot.
I have not done any max clock tests or validations as I have been very busy lately. I have done some Max Blck Validations and testing and use ET without issue, but I was only using the 19 multi so the multi drop would not have been an issue and I may have been using a older ET anyway. Which reminds me I need to reinstall a few older versions of ET and see if the 20 Multi issue is the caused by the new ET or if it is the F8a BIOS.
I think the voltage tightness with F8a helps with a little of both things you asked, it just feels better to see it closer ya know.
I will try to get some tests done tomorrow with older ET's and see if the multi drop happens, and then move to F7e again to test the S3 multi issue
Roller, I'd like to see some of your test images on the UD4P with F7e. I just did some testing and have the same results as F8a >>>
F7e
Before S3 (21 Multi BIOS F7e)
http://img90.imageshack.us/img90/313...1multismal.jpg
After S3 (20 Multi BIOS F7e)
http://img26.imageshack.us/img26/465...21not20mul.jpg
You can see my full report here, including thoughts about this and Easytune dropping the multi as I done some testing on that as well >>
http://forums.tweaktown.com/f69/giga...tml#post296954
Asus realized the issue with reboot. I am able to suspend at a 211 Bclk.
*Needs new bios update.*
Lsdmeasap,
I'd like to post some screens, but I cannot. When I click "go advanced" then the "attachments" pull down, I get the 'manage attachments' box, but it only has a space for typing in a URL, not a 'browes' option so I can navigate to a file on my computer. I've posted many attachments in the past and always gotten the space where I can navagate, but not now. Others are able to, so I'll work on this problem. Meanwhile, is anyone else having the problem of decreased multi after S3 resume?
Yeah this has been broken since the last crash as far as I know. Hope XS fixes it.Quote:
Originally Posted by roller11
Me obviously :( But not UD4P but UD5.Quote:
Originally Posted by roller11
@Lsdmeasap
Whatever that is I hope it get fixed since the D0 can clock better. Need the extra multi without scratching my head on bclk. Thanks.
I can vouch that the Classified resumes properly from S3. I have been involved in fixing some S3 related issues on that board but they were relatively small such as fan headers not restoring properly if manual fan settings are used. Otherwise, S3 works great on the Classified board.
Also works perfectly on the Asus Rampage II Extreme with latest Bios (1306). :D
Quote:
Originally Posted by Sparda
Man, I just don't get it. I've had 3 UD5s and a UD4P...all resumed properly after SM. Only SM prob I've had, I've had with every x58 mobo...about 1 time in 15 on average, it hangs when going into SM. I've gone 72 straight SM cycles with no hangs, and then I'll get 2 hangs in 10 attempts. it is totally random and unpredictable when this happens, and has happened on Biostar, ASUS, giga boards. But I've never had it disable the 21x multi. If I could post attachments, I'd show my before and after screens.
Broken fan headers is a HUGE issue, means everytime you resume you have to go back and redo your smart fan settings, totally unacceptable. But it's fixed now, right?Quote:
Originally Posted by dejanh
Care to share your bios settings. Probably we might missed something though I never had the S3 hang ; only the multi drop.Quote:
Originally Posted by roller11
PHP Code:Advanced CPU Features:
CPU Clock Ratio ................................ [19x]
Intel(R) Turbo Boost Tech ...................... [Enabled]
CPU Cores Enabled .............................. [All]
CPU Multi Threading .............................[Enabled]
CPU Enhanced Halt (C1E) ........................ [DISABLED]
C3/C6/C7 State Support ......................... [DISABLED]
CPU Thermal Monitor ............................ [DISABLED]
CPU EIST Function .............................. [Disabled]
Virtualization Technology ...................... [Enabled]
Bi-Directional PROCHOT ......................... [DISABLED]
Uncore & QPI Features:
QPI Link Speed .............................. X36
Uncore Frequency ............................(16x)
Isonchronous Frequency ......................[Enabled]
Standard Clock Control:
Base Clock (BCLK) Control .......................... [Enabled]
BCLK Frequency (MHz) ................................[218]
PCI Express Frequency (MHz) ........................ [100]
C.I.A.2........................................... .. [Disabled]
Advanced Clock Control:
CPU Clock Drive ..............................[800mV]
PCI Express Clock Drive ................... [900mV]
CPU Clock Skew ............................. [0ps]
IOH Clock Skew ............................. [0ps]
Advanced DRAM Features:
Performance Enhance ...................... [TURBO]
Extreme Memory Profile (X.M.P) ........... [Disabled]
System Memory Multiplier (SPD) ........... [8x]
DRAM Timing Selectable (SPD) ............. [QUICK]
Channel A + B + C
Channel A Timing Settings:
##Channel A Standard Timing Control##
CAS Latency Time ......................8
tRCD ..................................8
tRP ...................................8
tRAS ..................................24
CR.....................................1
Advanced Voltage Control:
CPU
Load Line Calibration ................. [ENABLED]
CPU Vcore ..............................[1.3312]
QPI/VTT Voltage 1.150v .................[1.300]
CPU PLL 1.800v .........................[1.800]
MCH/ICH
PCIE 1.500v ...........................AUTO
QPI PLL 1.100v ........................AUTO
IOH Core 1.100v .......................AUTO
ICH I/O 1.500v ........................AUTO
ICH Core 1.1v .........................AUTO
DRAM
DRAM Voltage 1.500v ..............[1.660V]
DRAM Termination 0.750v.......... [AUTO]
Ch-A Data VRef. 0.750v ...........[AUTO]
Ch-B Data VRef. 0.750v ...........[AUTO]
Ch-C Data VRef. 0.750v ...........[AUTO]
Ch-A Address VRef. 0.750v ........[AUTO]
Ch-B Address VRef. 0.750v ........[AUTO]
Ch-C Address VRef. 0.750v ........[AUTO]
EVGA X58 SLI works too, but only rev. 1.1
Nevermind. I already found the culprit for the multi drop after S3 resume when using turbo. It the CPU EIST Function. It should be enable.
Other power saving function doesnt matter much since it only save about 5 - 8 Watt.
Dont mind the big bios template in previous post. It wasnt mine. I got it somewhere in tweaktown.PHP Code:Advanced CPU Features:
CPU EIST Function .............................. [Enabled]
Use an Image host, I use this one often >>Quote:
Originally Posted by roller11
http://tinypic.com/
Then just put the direct image URL into image tags >>
[img]Direct URL Here[/img]
I do hope you mean S3 sleep and not Standby mode (SM)? I am testing S3 issues, not S1, so just wanted to check that we are discussing the same mode. Your "SM" Comment just threw me off so I thought I had better askQuote:
Originally Posted by roller11
Quote:
Originally Posted by Sparda
It should be endabled? What do you mean by "SHOULD"? You mean for the multi to not drop? If so, thanks for your testing and letting us know this, I will pass it along
In reality, it should not matter as the setting disabled should be always make the multi drop disabled (Full Multi always). So if this is the issue causing it, then there is a bug in this setting
Yes it "must" be enable for the multi not to drop back to x20 after S3. Just realize it after update to f7d and load default settings which enable the eist by default.
It kind of habit to turn power saving off when oc. I think you can try it on ud4p since it the same issue.
I dont know ; it probably bug since the eist broken after after certain bclk. If I am not mistaken dfi ut board also must enable the eist in order to use the turbo but it already known long ago.
Quote:
Originally Posted by Sparda
Thanks for the clarification! If this is the case/cause of the issue then this info may help the BIOS engineers fix the problem. So I will test if that is the case on my end as well, then pass along this info the the engineers
Hey, at least for the masses S3 is working now. That is a step in the right direction that should make plenty of users happy. I do not use S3, but test everything in New BIOS's as I support MANY Gigabyte users so I am always having to test this or that.
Thanks for the info, I will let you know my findings on this as well. Maybe they can correct this, add in the New AHCI ROM and have a perfect BIOS for the UD5 and UD4P soon! :up:
Thanks for the image host, I'll try it. And yes, SM to me means sleep mode. :)Quote:
Originally Posted by Lsdmeasap
Whelp, even with the latest BIOS, I can not get my Asus P6T deluxe to wake properly all the time so I'm going to move on shortly. Any updates/comments on the Gigabyte ex58 ?
Thanks,
Chris
I've tested 9 different x58 mobos and so far, none resume from SM 100% of the time, the UD5 is as good as any.
I had no failed resumes at all with the BloodRage.Quote:
Originally Posted by roller11
Did you try one ?
No, I haven't tried the BR, but I've tried various boards from giga, MSI, DFI, ASUS. Since I updated my BIOS on the Classified 760, I haven't gotten a failed resume, but the performance is very poor. Power button to full resume is 5-9 seconds on every board except the 760, the 760 is twice that, 13-18 seconds. So depending on your definition of "working" the classified either works 0% of the time, or 100%.
How many seconds from power button to full resume on BR? Full resime= desktop reappears, cursor moves and double clicking on an icon creates an action.