Been right busy with trying to do three other 'puter projects last weekend as well as work with the Foxconn, so this is sort of an update.......:roll:
What I have now will be a review of the bios screens and for me after playing with the Biostars and the nViews this will take some getting used to! Also there seems, to me anyway, things I can?t get to?..more on that as we go along. So in the beginning and in theoretical order
http://i34.photobucket.com/alb...ns/BiosStartScreen.jpg http://i34.photobucket.com/alb.../BiosSysInfoScreen.jpg http://i34.photobucket.com/alb...BiosFeaturesScreen.jpg http://i34.photobucket.com/alb...ns/FoxCCUnitScreen.jpg
then under Fox Control Center???
http://i34.photobucket.com/alb...ns/SmartBiosScreen.jpg http://i34.photobucket.com/alb...ntelSteppingScreen.jpg http://i34.photobucket.com/alb...ltOptionsScreenCPU.jpg http://i34.photobucket.com/alb...ltOptionsScreenMem.jpg http://i34.photobucket.com/alb...ns/CPUConfigScreen.jpg
Now for Advanced Chipset Features??..
http://i34.photobucket.com/alb...pSetFeaturesScreen.jpg
Which has??..
http://i34.photobucket.com/alb...ns/MemConfigScreen.jpg http://i34.photobucket.com/alb...TimingConfigScreen.jpg
Skipped over a few ?minor? areas and finished with???.
http://i34.photobucket.com/alb...HealthStatusScreen.jpg
Did some playing with OC?ing initially and was able to get an 8M run of SPi @ 275 FSB, 1.45V Vcore, 2.1V vdmm, timing divider at 667 with everything else mem wise at ?default?. However could not get past 10 minutes of OCCT. Currently my perceived limit is the mem set at a 1T command rate which I can seem to be able to change to 2T. Any foxconn gurus out there that might know? Also had an issue of where I had finished doing the Windows Update download and rebooted the system. I took the opportunity to reset the mem divider to 533, and it wouldn?t boot! CMOS time??..
I will be setting up an overclocking thread so anymore of that will be there. As soon as that is done I give a link.
Update, just flashed the P05 bios and it gave me a wee bit more dram thingies??but still no command rate control!
http://i34.photobucket.com/alb...NewBiosMemSettings.jpg
After working with the board for a day or so, just some simple observations. The area around the cpu is a bit tight for my liking. It eliminated the original hsf and that will be a problem for me later on if it goes where I think it is going. This might end up replacing the Biostar / Sandy combo in BHrDx so that also gives me concern about the location of the mobo 4-oin +12 connector. The PSU in BH is on the bottom and the connector is on the top. However this is not the board fault. Something that is nice as I have more than one monitor is the analog and digital video outputs. All in all it comes across as a well constructed board with options for the average person. Well worth the $50 I have in it and even better if the $10 MIR works!
Finally got around to attempting the oc?ing with hopes of coming close to what I had the Brisbane at in the nView. First and foremost the killer here is THERE IS NO WAY TO ADJUST THE MEM COMMAND RATE. Now that?s over lets get on with it, learn where stuff is and isn?t! Something else I had to get used to is that ClockGen doesn?t work with ATI. So that was ye old boot up run SPi, reboot ? adjust FSB - run SPi, reboot ? adjust FSB, reboot?.you get the picture. Now here?s were reading the back of the manual would have been nice if I had done it in the beginning. Foxconn has two utilities (would have been nice if the system cd had worked might have looked sooner!) one of which is called Fox + One. This is what works like ClkGen and would have made life a lot easier. It even more useful as you can also adjust vcore and vdmm on the fly.
http://i34.photobucket.com/alb...bane/OCing/FoxOne1.jpg http://i34.photobucket.com/alb...OneInsteadofClkGen.jpg
Because of the command rate being locked at 1T if you use manual mem settings I ultimately had to go all the way down to 400MHz @ 5-5-5-18-1T for clock speed to get anywhere near a decent OC. Started out at 1.425V vcore, 2.1V vdmm and left all other values at auto. Then starting at 250 FSB I would bump it up about 10 ? 15 each time and so a 4m run of SPi and when that would cap, back down about 15 and try for an 8M run. When that survived I?d drop 5 and try OCCT.
When it was all said and done I ended up with a 6hr run of OCCT @ 285FSB / 2.99GHz. Unfortunately I forgot to do a screen shot of that, but here are the core temp reports from OCCT?.
http://i34.photobucket.com/alb...9-01-17-22h00-CPU1.png http://i34.photobucket.com/alb...9-01-17-22h00-CPU2.png
Just for S&Gs but not going too high with the vcore, went to 1.475V and this is the furthest I reach doing 1M runs of SPi?? 305FSB for 3.20GHz.
http://i34.photobucket.com/alb...05FSBSPi1M1475VCut.jpg
So now I need to figure out what I?m going to do with the board and how to explain it being here to the wife! Again not bad for a cheap mobo and can only hope the next bios will give me command rate control.
Well after finding out about MemSet40 that allowed me to change the command rate, all else was forgotten and I was off to the races. The only biggie is it seems I can not boot at 553 mem divider, so ran this part of the testing @667.
Know one thing for sure Fox + One is one hell of a utility!! Made the testing a whole lot easier. Again I?ll skip the details as I spent over 2 hours bumping up the FSB and ultimately vcore to get a lot further at 667 @ 2T than I thought possible. Again the test was SPi with 1M runs until I arrived at a ?desired? setting at which time I would do an 8M run. If that worked I would then boot into that value. Ultimately I was able to boot into 290 / 3.045 and run an 8M run so then it was back to Fox + One and this is about it as 305 would reboot.
http://i34.photobucket.com/alb...3-3186672T1MSPiCut.jpg
Oh most of the early stuff was done at 1.45V vcore but had to bump it to 1.475V later one. The one exception is when using F + 1 I went down to 1.44V to try an 8M run at 295FSB, which??.
http://i34.photobucket.com/alb...76672T8MSPi144VCut.jpg
How ever when I tried to boot in at 295 or 290 it would continually reboot regardless of the vcore. I have managed to boot in to 285 @ 1.44V and now trying a 6hr run of OCCT. Something of interest here is I watching the core temps using SpdFan, CoreTemp, Fox + One, and of course OCCT. OCCT & CT agree on the low to mid 20sC while F+1 and SF agree at the low to mid 40sC.
While this may not seem like much, remember I?m now matching the 400 @ 1T with 667 @ 2T. It also just occurred to me that a limiting factor on the OC is the 740 (690) ATI 2100 on board video as it may be fighting for memory. Thoughts??
Well going to call it a night (morning!) while the system runs the OCCT for 6 (5.5 now) hours. If it lasts it will match the OCCT of the 400 @ 1T.
This mobo has kinda become a mystery for me. 400 @ 1T seems fine up to its limit, while the 553 @ 2T setting will let me boot up at 250FSB but nothing higher. Also when the 553 setting ?locks up on reboot? I have a note something like ?ATI 2100 ???.seahorse? on the screen. Now there is the 667 @ 2T which has a boot cap of 285 (with one exclusion at 290) but will not last OCCT or Prime. Also instead of the tests just stopping as normal with a bad setting I end up with a blank screen that requires a reboot. Another interesting quirk is sometimes after I exit the bios I have to hit the reset button to get it to boot as it seems to hang.
Will need to give this a rest for a while as other things demand my time, so have time for some input!