X58 board that suspends properly

[Lsdmeasap]

Any news on whether there will be BIOS updates for Gigabyte as well? Can't get S3 resume to work with my EX58-UD5...

The latest Beta, as well as a few before it resume from S3 just fine in the UD5 >>
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

[PC_User]

The latest Beta, as well as a few before it resume from S3 just fine in the UD5 >>
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.

I guess I'll just wait until the next final BIOS...hopefully it won't be long.

[Lsdmeasap]

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

[Schlotkins]

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 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.

[roller11]

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. .

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.
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.

I guess I'll just wait until the next final BIOS...hopefully it won't be long.

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.
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.

[roller11]

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

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.
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.

[PC_User]

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.

Why is only the F6A bios listed on Gigabyte's website?

[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.

[Schlotkins]

Is there any ETA on the Asus BIOSes? Thanks!

[davewolfs]

This bug frikin sucks!

[naokaji]

Someone found a workaround for the Gigabyte boards, might want to give it a try on Asus and others that have the issue.

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.

Source

[roller11]

So if HDD isn't off, it isn't in SM.
But it's a moot point because SM works on the UD5, UD4P.

[Sparda]

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 )
Did I miss something ?

[roller11]

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 )
Did I miss something ?

No, the turbo mode remains at 21x after S3 resume.

[Sparda]

No, the turbo mode remains at 21x after S3 resume.

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.

[Lsdmeasap]

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 )
Did I miss something ?

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.

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

[roller11]

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.

[ReverendMaynard]

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.

Come on man, you're so sure of that?

ICS9LPRS18BKL with setfsb works perfectly.

[Utnorris]

Just tried the "Sleep" function on the Blood Rage, works perfectly. I wish I had tried it before, saves so much time booting up.

[Lsdmeasap]

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.

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.

[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.

[roller11]

Come on man, you're so sure of that?

ICS9LPRS18BKL with setfsb works perfectly.

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.

[Lsdmeasap]

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.

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)




After S3 (20 Multi BIOS F8a)

[roller11]

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.

[roller11]

I didn't attach screen shot because attachments don't seem to be working right now.