u say it man !!!Quote:
Originally Posted by Zucker2k
Printable View
u say it man !!!Quote:
Originally Posted by Zucker2k
Should it be said … or not. Of course, it should. First off, the difference between diplomacy and “social etiquette” is the difference between truth and untruth. Truth, which is another word for unity and untruth, which is another word for division, is also the difference between real power [or reality] and relative power [or imagination]. For those coughing blood and fuming about religion, crapola and similar at this stage, cough more [the whole lot, if possible] for it has to get worse before it gets better.
Nobody needs to be diplomatic about a “secret” bios as if such a nonsense exist. It’s about relative power [yeah man, feeel the powahar] which is selfish empowerment to the detriment of others’ feelings. The feeling that you’ve paid a lot for some pipe-dream and all because pimps and their whores have done a good job on you. If those with some brains still intact were to take a step back and reflect, none of the so-called overclocking boards make much of a difference when it comes to performance and there are no exceptions here. They perform much the same in real world applications, clock-for-clock. The idiots and lunatics with their great technical write-ups are part of the selling food-chain. The selling of dreams of Bushido [a real con relative power crapola and used to good effect by gangsters and the military all over].
Take a realistic view and that is you are only as good as the lottery-strike CPU followed by expensive memory and that’s just the silicon, not forgetting even more expensive cooling. It has little to do with a human being. Where the human comes in is when imaginations start flying. Nobody is going to con Intel out of a few hundred bucks worth of performance because they’ve already sold you something that costs little in the grand scheme/scale of things. That’s why they’ve locked the multiplier. Let the juvenilles and their self-perceived greatness justify their need to play with their danglies but don’t let them persuade you that they are not actually playing with their tiny dangly bits. They are. Don’t beg and fuel their aggression/disrespect for others. Enhance your self-respect instead and vote with your pocket…. next time for there will always be a next time for what goes around, really do comes around.
A secret is when you do not know about it but disrespect/aggression is when you’ve been lured by it. Ever heard of the whore that you can never buy? That’s called a time bomb. That’s the one that wants to own you, not just some of your money. Some might even sceptically call that a spouse.
I didnt know Xs had a pulpit. Whens the next service? :stick:
well, some would kill for first spot on 3dmark06 page, others not..
as for the new bios, still tons of issues to fix before 1333 strap which abit sayed on release that the board will get it, so no big secret here..
i just want an bios which dosnt require phase to make the board be highly ocable
Quote:
Originally Posted by cir108
clock for clock comparisons are valid on xs when the cooling limits are similar, for those with superior cooling capacity the maximum speed a board can run at becomes important (if it pull away in performance at higher fsb's), if you look around you'll see threads comparing straps and performance, so people are not really too blinded here, not too mention the mentallity of how much is enough or too much..;)
regards
Raja
what 's going on here ?....http://i51.photobucket.com/albums/f3.../surrender.gif
I got a p5w dh dlx and that is totaly fubar.
How is this abit card ?
i've had p5w dh dlx before and it's just couse trouble to me, this Abit aw9d-max is much better and more stable, it boots up just fine and no waiting minutes to se a screen, i am more satisfied with this board than p5w dh dlx because it was the worst crap i ever had..
no more asus=anus in my house :(
Phase really has nothing to do with the oc'ability right now as the limiting factor is the mobo and not the CPU. It's the boards lack of adjustments and lack of high of FSB's which are attainable only through vmodding which are making awesome overclocks unattainable.Quote:
Originally Posted by Hilfiger
Board isnt doing too shabby on water :D
http://www.sspmustang.com/OT/x6800/4...n-32m-run1.JPG
Man, that is some serious voltage ur giving that poor cpu.. mine is Pi 32 stable @4113 (457*9) and 1.55V. Have you tried lower?
That voltage looks a bit much for water :/
Quote:
Originally Posted by FragTek
He's only at 50c, whats the big deal? Have you even seen a dead conroe from voltage?
Anyways, if this board gets the 1333 strap that would be very good, hopefully DFI does it with the infinity too and we will have some king 975 boards. Maybe some new SLi drivers for it and then things would be great.
i get that fsb at 1.6v, but i cant go over 410 for some reason, and i have 50c on airQuote:
Originally Posted by Revv23
that's very strange. have you tried messing with the trfc value?Quote:
Originally Posted by Hilfiger
i've found that in order to boot above 405, i'd have to loosen it up quite a bit.
also, i think a default 9x chip seems to obtain higher fsb's than a default 10x chip.
i had a hard time booting at 420 with my 6700... now i can easily boot 425 with my 3060, vmch = 1.85, and vfsb = 1.49.
ehem, hes at 50C IDLE, not load. That indeed is pretty dang high...
...that may be, but aren't the AW9-D's temp sensors like ~20C on the high side?
CoreTemp shows core1 @ 63*c... AT IDLE. That's burnin up, kick down ur voltage man.Quote:
Originally Posted by Budwise
yea, they do read high but id still be dropping those volts down regardless...
No, I don't think they are THAT off.Quote:
Originally Posted by ErikaeanLogic
between core temp and uguru, temp differences are only 2-3C's.
My idle temps are usually around 35-37C's with room temp of 24-26C's.
It is only 1.68v load and about 1.7v idle, what is so bad about that :toast:Quote:
Originally Posted by Revv23
Core temp shows 77c priming 1.63v, I have had cpus that show 20+ less or so!
I will say it again!
THE ONBOARD SENSORS INCLUDING CORE TEMP ARE NOT ACCURATE!
Could someone who has done the vfsb mod answer a question for me please. I know the only way to get a true reading after the mod is with a digital mm but since I've completed the mod the board has been reporting 1.9v in uguru no matter what the vr is set at.
I'm just trying to make sure I'm not the only one getting a wrong reading because if I'm still supposed to be able to see a correct or close to correct reading there may be something wrong with my mod.
Has anyone actuly tried to load saved settings by pressing F7 ?
Swaped in a new VC, and like all ways my settings were lost, pressed F7 chose to load saved settings, escaped back to main menu and chose save settings and exit. Greeted to a blank screen, and thats as far as it goes :confused: waited a good 4 mins and nothing at all happened, reset does nothing, holding power button does nothing.
Powered off {by PSU} swaped back to old VC, power up and nothing power button dont work, reset dont work.
Cleared CMOS, still same thing, pressing power button does nata.
Yes. I have used F7 before and it worked! :) and loaded fine as well.Quote:
Originally Posted by Blue078
the vfsb is cpu vtt i believe in uguru.Quote:
Originally Posted by MrDeeds
i've measured it with a DMM and using uguru and they are only 0.02 volts different.
@ MrDeeds, I set with uguru the mch to 1.72v and it measured the same with DMM. Voltage reading in uguru "voltage" = 1.81v. Repeated with 1.83 and uguru "voltage" page showed 1.92v. So it does change, but mine at least, reads high. (.09v for both).
doh *edit* I will now confirm what shimmishim found and answer the original question as well.
Yes, vfsb=1.242 dmm and vtt 1.2 = 1.28v
vfsb=1.250 dmm and vtt 1.2 = 1.29v
I'm using bios 1.2 atm. I don't know if calibrations are different between versions.
@ shimmishim, (below) my first board died Sunday (sad). It just would not boot..stopped at 9.0. I had the vfsb and mch up, 1.489 and 2.025 respectively. I was trying to go faster. I did the same thing with a really good 7800gt a few weeks ago. Anyway I had another one from an rma replacement I was going to sell and never did, so I unsoldered all the vr's and put them on the one I have now. You can adj. all volts till it shuts off basically. I can't really say what happened to my first one but hi vfsb and or vmch may not be to good. All my temps are always below 40c for the uguru temp readings.
I'm using beta13b03Quote:
Originally Posted by coop
i set 1.49 DMM = 1.51 uguru
vmch doesn't change when you set it. but from what i've seen, when set at 2.0 volts, real is 1.89, a droop of .11.
if you do the booster mod, the droop is only about 0.03 which i have measured before with a DMM
Woosh! Pulled battery and cleard CMOS ate a bite, and replaced battery and whala she boots again. Holy crap thought the board was a gonner.
Wounder why my board dont load the F7 save?
was it from saved settings or changes you made bedore you save settings and THEN pressed f6, i save and exit my settings then re-enter and f6 to save, also it may not work if it was saved from a previous bios and then you upgraded bioses and try f7... just a guess... f6 and f7 work fine for me.Quote:
Originally Posted by Blue078
No they were settings I had saved last week {same BIOS} But I did find out I hadnt flashed to the 13-B03 BIOS :slapass: I was still on the 13-b2, maybe that had something to do with it?
I've flashed to 13-B03, will try tomorrow and see if saveing a new set with this BIOS works. Sure thought I'd lost the board for awile their. Despit the BIOS issues I like this board better than any C2D board I've had to date.
Heres my first test after full V-mod not that high volt on it and with single EXTREEM PC2-6400 my other stick died before on my asus board.
VCORE- 1.55v
MVCH- 1.60v
VFSB- 1.35v
VDIMM- 2.25v
real volt.
timings 4-4-4-10
http://img150.imageshack.us/img150/6...lockie6.th.jpg
All is on air..
...so whats up now with that 1333 strap? When do we all get a Bios with this strap. I don´t even know why now there is such a mystery ´bout this alpha bios with that strap. Think we have to call Special Agent Moulder and Scully to find out whats up with our strap. :D
Maybe those Aliens kidnapped that strap or the :usa: Gouvernment likes to get real high FSB at AW9D-Max first.
I want that strap NOW !!! :)
If a bios is ALFA version, this means that it's on testing......Beta is a "pre-final" release......Now imagine that you get an ALFA bios and you burn your mobo!......What would you say?....:)
Do you think it's gonna be released an beta bios with the 1333 strap ?
I´d say: "F**k! Now I gotta do a hotswap with my other AW9D-Max. But I didn´t do that a long time ago. So I wanted to do a hotswap again anyway." :DQuote:
Originally Posted by hipro5
So, everyone himself (and only himself) is responsible for flashing BIOS. No matter if alfa, beta or final. If I burn my BIOS by flashing an alfa then its me I´m gonna thank for this and not abit, xs or hipro5. As I know flashing bios always voids warranty, does it?
So, I think I´m a little experienced with flashing bios. Did that about 500 - 1000 times already and about 5 times I really flashed some bull:banana::banana::banana::banana: into the CMOS. But that doesnt`t mean that the board is fuc*ed up. Almost in that Case I did a hotswap and all was fine again. In the remaining cases I programmed that eeprom in an eeprom-burner.
My warranty is allready void by doing all your cool mods to my AW9D-Max, just like I did to my former systems board, the IC7-G. It did about 1 year 24/7 running with your mods and now it´s retarded but still runs fine. Thanks again for inventing those excellent mods.
...at last, I´d be really happy by getting a pm from that little birdie you told us. ;)
Whats all the damn begging about.:horse: It obviously hasnt gotten any of you the bios, so share relevant info pertinent to the board or shutup.
Back Ot:
I didnt measure my vfsb before i did the mod :slap: and i havent used this multimeter in months so i removed the mod and measured the vfsb stock and i got a reading of 1.38. So im not sure if i've got a bum multimeter or if my board is overvolting the vfsb.
More than likely its the multimeter, i'll check later when i get home.
are you sure? you have to be really accurate with where you place the DMM... i found that moving it like a tiny tiny amount will cause the voltage to change by a lot at times.Quote:
Originally Posted by MrDeeds
the stock voltage is around 1.2-1.22. try to measure it again. this time measure it at the leg where it touches the mobo pcb. that's where i measure it.
any improvement with the new 1333strap bios?
Quote:
Originally Posted by tictac
is there any beta out now?
not yet.Quote:
Originally Posted by Nitemare
hipro has an alpha bios with the 1333 strap but it hasn't been released to the public yet.
Watching this thread like a hawk....
...I already knew...Quote:
Originally Posted by shimmishim
waiting for that strap sucks
I know that patience is a virtue, but waiting for the next official BIOS release is just unbearable already. I know they are making sure things will work out, but hey September to December (see the gap?) isn't necessarily a short time. Given, they may have seen the issues sometime October, it's still such a long time.
This board works great with Conroe, but I wish it'll work just as well with Kentsfield without hard modding it. CPU VTT is just too low for Kentsfield to sustain high FSB :(.....
I guess I'll be waiting for the next top of the line mobo instead of hoping for this board to get a boost for Kentsfield.
Guys, how much vMCH are you guys pumping to get 400FSB pass ORTHOS stable?
I could run memtest all day long and 2xSPI32M with just 1.6vmch but it will fail ORTHOS in a matter of seconds.
I'm on E6300 that does 3GHz Orthos stable on stock Vcore and OCZ PC8000 Ti Alpha VX2.
As for the RAM, I couldn't get it to run 500MHz at 4-4-4.. even if I gave it 2.65VDIMM.
If the AW9D-MAX wants 2.0vMCH to do 429FSB Orthos stable, I'll start to bang my head against the wall.
IIRC, I had an Asus 975X board that does 429FSB Orthos stable with just 1.8vMCH.
Look forward for your input...
You won't be running your ram on this board at 500, 1:1 anyway. Different ratios no problem though. Around 1.86v to 1.92 should be ok esp. with stock cooling on the chips. More has not been much benefit to most. If you can keep your board/chips cool you can try up to 2.0v for max fsb runs. I found that at 1:1 quite a bit of vdimm is needed.
Quote:
Originally Posted by pcmoddingmy
i dont get at 400fsb with 2,0 vmch orthos stable, so thats me, others might get stable
Ok... I know it wont do 500MHz mem on 1:1. Tried 4:5 and 2:3 for 500MHz mem, getting errors on memtest, lots of em'. I heard this board is good up to 470MHz mem stable only... sighz
Anyways, back to the FSB thingy. Swapped out the stock NB cooler and hooked up a Thermalright HR-05 onto it. Its cooling well and I booted at 429FSB (1:1) with 1.7vMCH (did that on the stock cooler too).
Fired up Orthos, errored out after 5 minutes.
Bumped to 1.8vMCH (via uGuru), ran Orthos but errored out after 5 mins again. Same thing at 1.9vMCH too.. error after 5 mins.
So gave it all I've got and ran 2.0vMCH.. guess what, error after 5mins of Orthos. So much for AW9D-MAX... Bumping vCore or even vDIMM didn't help me get past 5 mins in Orthos without errors.
However, it passed memtest #5 and dual Super PI 32M easily.
Currently on BIOS 13.B04. Originally was on BIOS 12...
Hilfiger: 2.0vMCH at 400FSB still ain't ORTHOS stable? Man... I miss that Asus P5W64 WS PRO :(
I did achive orthos stable at 410fsb have you tried lowering your vmch to 1.60 thats good spot for me.
Hmm.. 1.60vMCH = 410FSB Orthos stable? I don't think I can do that as even at 1.60vMCH, it was not Orthos stable.
Anyways, a little update. Gave it 2.0vMCH and now at 400FSB. 25mins into Orthos and no errors yet. Will let it burn-in until the next 12 hours or so, with TR HR-05 on the NB of coz.
THIS NEEDS TO BE SAID... I HOPE NO MOD GRINDS MY :banana: :banana: :banana: FOR SAYING IT.Quote:
Originally Posted by death metal
Ridiculous isn't it? I mean you have to wonder how certain people in this same thread TOUTED this board as the king of 'em all which influenced some of us to buy the board in the first place. Then we followed up with petitions for the 1333 strap. Finally, when the bios arrives, we are left begging to try it. Needless to say, we know you have the bios going around in that little circle of yours - which is all good. But remember that the next time you PROMOTE a board, we will be taking it with a pinch of salt.
Finally, finally. When I joined this forum, I thought that this was about community? In a community, we share ideas and resources to help each other overcome computing difficulties. It seems that this is not the case at all. I am waiting to be proven wrong. This is really frustrating. Don't get me wrong, I love this forum and will continue to be a member for a long time to come. Also, all of us, well, the majority of us who come here, know about the risks of modding and voiding warranties, but we come here because we have decided it is worth the risk. So stop giving us lectures. Thank you.
PS: Hope I haven't stepped on any toes too hard.
...did that birdie tell you a release date of any BIOS ( Beta or Final ) including the 1333 strap? Maybe before Christmas or even next year? Wish I´d try that strap myself finally.Quote:
Originally Posted by hipro5
greetz
Your talking just right outta my soul my friend.Quote:
Originally Posted by Zucker2k
Sharing interests, knowledge and resources is the heartbeat of any Community. Just like this. But maybe that screenshot including that strap was just the result of a little photoshop session ;) !?
Greetz!
@pcmoddingmy, did you happen to note any before and after temp changes with the pwm's in uguru after changing to the Thermalright?
Do u know the word responsibility? If someone gives u an Alpha bios and your board dies, what are u going to say then...?Quote:
Originally Posted by Nitemare
BTW thinking this way about someone else just defeats your own "Community theory"... ;)
Come on man, you should know better. We all know how these things are done... they always come with a disclaimer. Anyway, even final release bios have been known to kill mobos if not done right. Save us the lecture.Quote:
Originally Posted by JoeBar
If your so concerned about contributing to the community then why dont you find a way to get the bios by yourself rather than just whining about what somebody else isnt giving you. Nobody owes you a thing. Your not concerned about the community, your concerned about yourself and what your not getting.Quote:
Originally Posted by Zucker2k
If you bought the board based on the fact that someone hit 470fsb with a heavily modded board and your not happy that your stock board will only go up to the 440s then i think your not making some very good decisions. I havent seen one review where the board got over 450fsb stock. Its no revelation, if you did your own research you'd know thats as far your probably going to get stock. Its a strap and chipset limitation. When the board was released it came with no 1333strap and if they choose to give us that now thats just gravy. You should have known what you were getting yourself into.
There are some very legit issues with the board and we are all itching for a bios update but a alpha bios with a 1333 strap probably isnt going to do many of us any good unless you get high on benching. Most alpha and even beta bioses have bugs that make them worse than a lower clocking but more functional bios. This is Xs, where people have es cpus that arent going to be released for months. Boards that we cant even touch for weeks. It shouldnt be that big of a deal that someone has a bios that you cant have, at least not yet. As long as they are willing to share those results then thats all i care about because i know that the bios will eventually be released.
Very well said ;)Quote:
Originally Posted by MrDeeds
...persons that are able to read got a big advantage. ;)Quote:
Originally Posted by JoeBar
So please read what I`d say a few posts ago. I think you´re able to, aren´t you!?
Quote:
Originally Posted by Nitemare
a. IF you take a GOOD look at this shot, it was taken with a digicamQuote:
Originally Posted by Nitemare
b. IF you knew me better, you would have known I don't BSing around.
c. You just CAN'T accuse someone in an open forum without evidence...While you say that the screenshot IS a photoshop, you're accusing me that I photoshop it..........SO little brain in your head.....Jesus!.....:(
Do not worry about it hipro :|Quote:
Originally Posted by hipro5
6*451 with X6800 will not even pass 1m :(
I wish there was a pencil vfsb mod, would you know of the proper resistor to pencil hipro?
...just said MAYBE and signed with a " ;) ". So everyone should get me right.Quote:
Originally Posted by hipro5
sry if u misunderstood.
But thanks for small brain compliment. :banana:
GreetZ!
We could do a pensil mod as for the VMCH but not for the VFSB.....:(Quote:
Originally Posted by fhpchris
I can`t go above 451Mhz FSB. Can you show the vmch pencil mod?:)Quote:
Originally Posted by hipro5
Well, what does PWM temps has got to do with the NB heatsink?Quote:
Originally Posted by coop
This board doesn't report NB temps at all. In fact, I don't remember seeing a 975 or 965 mobo that has NB temp readout.
Anyways, PWM temp looks kinda similar as it was before the HR-05.
Anyways, a little update...
Overclocked it to 400FSB at 2.0vMCH and left Orthos running while I went to bed. Came back the next morning and saw Orthos had failed after about 3 hours into it. Damn...
So, did another run at 400FSB but with 1.9vMCH and errored out on the 58th minute in Orthos. :brick:
Quote:
Originally Posted by Lalaboy
Haven't tested so be carefull.....This is the spot......When I say be carefull, I mean don't drop too much "pencil" on it.....
Drop a bit and look into bios the VMCH and again and again.......
DON'T do it "onthefly".....I mean don't do it with your mobo powered on.....
http://www.thelab.gr/images/Hipro5/A...Pencil_mod.jpg
Thank you HYPRO!:up:
One of my Redline death. (3.1V) I bought Team Xtreem 6400 C3 2x1Gb. Only with 1 BIOS working good. The biggest problem is, that if I OC the rams and the win. is crashing, the mobo load bios defaults, I can boot into the bios with only 1 modul.:confused:
Anyone run SLI on this board yet?
Heya hipro5, did your birdie mentioned about vFSB? I have been dying to get it this settings on the BIOS. I posted previously here: http://xtremesystems.org/forums/show...postcount=1595Quote:
Originally Posted by hipro5
I have no problems running Conroe XE with 440+ FSB on this board, but Kentsfield stability is tough beyond 325FSB (350FSB max at Bad Axe 1, 390FSB max at Bad Axe 2).Quote:
Please request to add support for FSB vTT adjustment up to 1.8v (currently 1.2v only). I'm too lazy to vMod a board nowadays, so I hope they will add that option to help Kentsfield with better FSB.
I know this board isn't designed for Kentsfield OCing (it will OC, but not as high as Conroe) but I am still hoping they can do the fix. If not, like I already said, waiting for the next bios is unbearable (and very few who knows if and when they are going to release it) and I might as well wait for a newer board.
It's been awhile, but yes. I ran 2 7900GT's for awhile.................Quote:
Originally Posted by G H Z
http://img.techpowerup.org/061117/42...hmark Abit.jpg
The word responsibility wasn't meant for u... ;)Quote:
Originally Posted by Nitemare
Anybody tried a Kentsfield on this board? Has the problem with the unlocked multis been resolved? (only 2 out of the 4 cores responding to multiplier changing)
Is ABIT planning to release any new BIOSes, or they just dropped the whole AW9D line?
So,did you notice if it helped or not? The reason I'm asking is I have sanded my nb sink and have a strong fan on top with no heatpipe. If an aftermarket cooler don't help then I will keep the one I have.Quote:
Originally Posted by pcmoddingmy
**EDIT** I mentioned earlier that my first board would no longer boot. I was looking at it Friday and found this. The label has warped fron heat and a hole was burnt into it. I tried to hotflash with present board but it was not recognized during flash.
:( How did the BIOS chip get that hot?Quote:
Originally Posted by coop
No idea. My new board though, I finally got a 32m @ 470. Time is slow and took 1.85 vcore 2.0v mch and 1.457 vfsb. Vdimm required is alot. Over 2.65v. But as noted before 1:1 takes alot compared to 2:3 or other ratio.
I don't believe that its Vfsb can be controled within bios or proggie......It's circuit is plain and simple so don't expect that....Quote:
Originally Posted by death metal
That´s so poor for a mobo at such a value.Quote:
Originally Posted by hipro5
I´ve done ur vfsb mod too. To get 5 minutes orthos stable at 400 it needs to get 1,5V vfsb. What do you think it´s safe for 24/7?
Just want to run at 400 24/7.
Greetz!
Quote:
Originally Posted by Nitemare
As for me, mobo worths every penny as is......;)
I've worked with Bad Axe, P5W-DH, P5B-Deluxe, P5W-64, Most of the Gigabytes and NONE of them can't touch it when it's moded.....
P.S. ALL of the mobos moded too.....;)
ONLY thing I wish is that the 975 chipset could work SLI........:(
1.45VFSB - 1.5VFSB it's OK for ever on air...... ;)
Try to work it with ONLY ONE DDR Module to see if it raise it's fsb.....If yes, then try other timmings/subtimmings for your rams...... ;)
Quote:
Originally Posted by hipro5
...I´m on water all the way. What ya think is safe for that?
Before I´ve done vfsb I´ve tried what you say but didnt raise just 1 MHz. Tried any timings / subtimings.
My last hope is just finally getting that strap will help raisin´fsb. Dont know what to if it won´t help. Buying 6600 instead of 6300 or buying p5bd.
Don´t think my 6300 is causing me that trouble. It reaches 3200 at stock vcore on p5bd.
Greetz!
My board actually clocks better with lower vFSB, well maybe not "better" but its more stable @ 1.35V then 1.45V for example
The VFSB is clearly CPU depented....Either your CPU can "listen" to it or not.....There are CPU's that could be better with 1.75VFSB (subzero)....The one I have got now, performs better at 1.5VFSB max (subzero) weither my previus one, was better with 1.75VFSB......Quote:
Originally Posted by zeeke
This has nothing to do with the board.......;)
Hipro..... any result on the new 1333strap? issue or improvement?
Hi guys
i have a few days with this mb and 6600 after a long period with AMD and i must say i'm impressed.
I replaced stock cooling with aftermarket to the n/b,mosfets and s/b.I can do 450 bus with 2V but i have a lot of memory errors even if i try scruing with memset.I'm sitting at 420x9 for now quite stable.
One question...........can someone show me where exactly PWM1 is?......cause when i give 1.57V and over to cpu, uGuru reports temps over 82 even 85 when the other 3 PWMs are at about 65-70.
Thanks a lot.
Quote:
Originally Posted by Varsos
copy/paste from other place:D
PWM control is powerful technique for driving analog circuits with digital outputs.
--------------------------------------------------------------------------------
Pulse width modulation (PWM) is a powerful technique for controlling analog circuits with a processor's digital outputs. PWM is employed in a wide variety of applications, ranging from measurement and communications to power control and conversion.
Analog circuits
An analog signal has a continuously varying value, with infinite resolution in both time and magnitude. A nine-volt battery is an example of an analog device, in that its output voltage is not precisely 9V, changes over time, and can take any real-numbered value. Similarly, the amount of current drawn from a battery is not limited to a finite set of possible values. Analog signals are distinguishable from digital signals because the latter always take values only from a finite set of predetermined possibilities, such as the set {0V, 5V}.
Analog voltages and currents can be used to control things directly, like the volume of a car radio. In a simple analog radio, a knob is connected to a variable resistor. As you turn the knob, the resistance goes up or down. As that happens, the current flowing through the resistor increases or decreases. This changes the amount of current driving the speakers, thus increasing or decreasing the volume. An analog circuit is one, like the radio, whose output is linearly proportional to its input.
As intuitive and simple as analog control may seem, it is not always economically attractive or otherwise practical. For one thing, analog circuits tend to drift over time and can, therefore, be very difficult to tune. Precision analog circuits, which solve that problem, can be very large, heavy (just think of older home stereo equipment), and expensive. Analog circuits can also get very hot; the power dissipated is proportional to the voltage across the active elements multiplied by the current through them. Analog circuitry can also be sensitive to noise. Because of its infinite resolution, any perturbation or noise on an analog signal necessarily changes the current value.
Digital control
By controlling analog circuits digitally, system costs and power consumption can be drastically reduced. What's more, many microcontrollers and DSPs already include on-chip PWM controllers, making implementation easy.
In a nutshell, PWM is a way of digitally encoding analog signal levels. Through the use of high-resolution counters, the duty cycle of a square wave is modulated to encode a specific analog signal level. The PWM signal is still digital because, at any given instant of time, the full DC supply is either fully on or fully off. The voltage or current source is supplied to the analog load by means of a repeating series of on and off pulses. The on-time is the time during which the DC supply is applied to the load, and the off-time is the period during which that supply is switched off. Given a sufficient bandwidth, any analog value can be encoded with PWM.
Figure 1 shows three different PWM signals. Figure 1a shows a PWM output at a 10% duty cycle. That is, the signal is on for 10% of the period and off the other 90%. Figures 1b and 1c show PWM outputs at 50% and 90% duty cycles, respectively. These three PWM outputs encode three different analog signal values, at 10%, 50%, and 90% of the full strength. If, for example, the supply is 9V and the duty cycle is 10%, a 0.9V analog signal results.
Figure 1. PWM signals of varying duty cycles
Figure 2 shows a simple circuit that could be driven using PWM. In the figure, a 9 V battery powers an incandescent lightbulb. If we closed the switch connecting the battery and lamp for 50 ms, the bulb would receive 9 V during that interval. If we then opened the switch for the next 50 ms, the bulb would receive 0 V. If we repeat this cycle 10 times a second, the bulb will be lit as though it were connected to a 4.5 V battery (50% of 9 V). We say that the duty cycle is 50% and the modulating frequency is 10 Hz.
Figure 2. A simple PWM circuit
Most loads, inductive and capacitative alike, require a much higher modulating frequency than 10 Hz. Imagine that our lamp was switched on for five seconds, then off for five seconds, then on again. The duty cycle would still be 50%, but the bulb would appear brightly lit for the first five seconds and off for the next. In order for the bulb to see a voltage of 4.5 volts, the cycle period must be short relative to the load's response time to a change in the switch state. To achieve the desired effect of a dimmer (but always lit) lamp, it is necessary to increase the modulating frequency. The same is true in other applications of PWM. Common modulating frequencies range from 1 kHz to 200 kHz.
Hardware controllers
Many microcontrollers include on-chip PWM units. For example, Microchip's PIC16C67 includes two, each of which has a selectable on-time and period. The duty cycle is the ratio of the on-time to the period; the modulating frequency is the inverse of the period. To start PWM operation, the data sheet suggests the software should:
Set the period in the on-chip timer/counter that provides the modulating square wave
Set the on-time in the PWM control register
Set the direction of the PWM output, which is one of the general-purpose I/O pins
Start the timer
Enable the PWM controller
Although specific PWM controllers do vary in their programmatic details, the basic idea is generally the same.
Communication and control
One of the advantages of PWM is that the signal remains digital all the way from the processor to the controlled system; no digital-to-analog conversion is necessary. By keeping the signal digital, noise effects are minimized. Noise can only affect a digital signal if it is strong enough to change a logic-1 to a logic-0, or vice versa.
Increased noise immunity is yet another benefit of choosing PWM over analog control, and is the principal reason PWM is sometimes used for communication. Switching from an analog signal to PWM can increase the length of a communications channel dramatically. At the receiving end, a suitable RC (resistor-capacitor) or LC (inductor-capacitor) network can remove the modulating high frequency square wave and return the signal to analog form.
PWM finds application in a variety of systems. As a concrete example, consider a PWM-controlled brake. To put it simply, a brake is a device that clamps down hard on something. In many brakes, the amount of clamping pressure (or stopping power) is controlled with an analog input signal. The more voltage or current that's applied to the brake, the more pressure the brake will exert.
The output of a PWM controller could be connected to a switch between the supply and the brake. To produce more stopping power, the software need only increase the duty cycle of the PWM output. If a specific amount of braking pressure is desired, measurements would need to be taken to determine the mathematical relationship between duty cycle and pressure. (And the resulting formulae or lookup tables would be tweaked for operating temperature, surface wear, and so on.)
To set the pressure on the brake to, say, 100 psi, the software would do a reverse lookup to determine the duty cycle that should produce that amount of force. It would then set the PWM duty cycle to the new value and the brake would respond accordingly. If a sensor is available in the system, the duty cycle can be tweaked, under closed-loop control, until the desired pressure is precisely achieved.
PWM is economical, space saving, and noise immune. And it's now in your bag of tricks. So use it.
Personally, I find 435 fsb stable (~445ish 1m) rather crappy...Quote:
Originally Posted by hipro5
I really need ~445 stable and ~475 1m :(
does just the vmch droop mod and vfsb really help that much?
same question, hipro. we need some input please. :DQuote:
Originally Posted by tictac
Phill gained about 30 - 35MHz more with the VFSB and the "cable mod" as for the VMCH.....;)Quote:
Originally Posted by fhpchris
From a glance I had, I realy didn't gain much out of it......Maybe coz of the devider used lower than CPU's fsb.....Quote:
Originally Posted by Virtual
To be sure though, I'll re-check tomorrow that I'll have more time to play with......
The CPU I now have, is capable of doing 552MHz fsb on an P5B-Deluxe mobo, so I'm sure that it won't ba a CPU fsb limitation.... ;)
Can someone answer a quick question: Which temp monitoring should I be using, CoreTemp94 or ABIT Guru, ABIT Guru reads the temps higher (5C) then Core temp??? THANKS
use guru...
why use Guru? I thought that CoreTemp94 measured the actual core temp which is usually hotter
i keep an eye on both, but use guru. According to core temp my E6600 is idle at 57C right now with high end watercooling. Yes it is rather toasty in this room at the moment but i dont really believe 57C idle... Uguru reads 39C idle which i would guess is more likely than 57 in my opinion.
Unmodded, my board did Spi 1mb @425, with cable mod, vfsb and vmch I pass 1mb @ 473,Quote:
Originally Posted by hipro5
Nice, tell us what you find out hiproQuote:
Originally Posted by hipro5
Thanks, a new motherboard maker and model awaits me then. Bad Axe 2 gives me better FSB than this board, using four(4) Kentsfield Extreme and all behaves similarly in both boards.Quote:
Originally Posted by hipro5
hey guys
I've a little question:
Is the MCH Voltage always undervolting?
My AW9D Guru say 1,85V MCH when I've set 1,85V in the bios
And I need the 1,85V for 400Mhz. That isn't normal or?
i don't knw what the minimum vmch you need for 400 mhz is.Quote:
Originally Posted by t-bone
However, uguru is wrong, it always shows the voltage you set in the bios but the actual is a bit lower than what's shown.
i didn't measure the vmch before the booster mod but after the booster mod, the mch is only .03 lower than what's set in bios.
i've heard that when you set 2.0 it is actually 1.89.
i use to run 1.70-75 on vmch with e66 @ 400, 1.85v sounds high but not impossible that you need that.
Raising vfsb to 1.475v gave me better results than 1.457v by quite a bit. Able to run 32m@471 4-4-4-6 then one at 472 with 4-4-3-5. Never have been able to do that high with timings that tight before. Vcore 1.792 vmch 2.001v vdimm 2.8v. I did cpuid screen first then cpuz of same. Cpuz sometimes is a little shakey trying to do capture. Oh yes, core temp shows actual boot up speeds.
**edit** I don't know why "tt" only shows 471 for system clock.
Oh, I just remembered. Is there any program out there that is reading somewhat correct temps on this board subzero?
Right now uGuru is reading 120, Coretemp 8 on both cores and thermal tool doesnt really start properly..
Is that on air?Quote:
Originally Posted by coop
I just wanted to post since I have just registered with Extreme Systems. I have had this board for over a month and I am still learning about OC'ing my PC. I have been following this thread since the beginning and I would have to say that I have really enjoyed following peoples successes with this board. I am a proud owner and hope to eventually get some nice results with it as well.
I just want to add that I personally think you will not see 1333 strap until ABIT releases the IN9 32X-MAX. I just think for the most part it is more of a marketing thing. So in the meantime they are perfecting the BIOS. Nothing wrong with perfection, sometimes waiting and getting what you really want as opposed to getting new BIOS and complaining about something else. Human nature working here, as soon as we fix one problem we look for another.
Then again, what do I know about what is going on over at ABIT.
I hope I'm wrong about marketing thing and we get the new BIOS soon.
Thanks everyone for the time you have put in, I have enjoyed reading all the posts. You'll be hearing from me again in this thread. :toast: