the strap is still 1066 not 1033
the strap is still 1066 not 1033
Typo fixed. :)Quote:
Originally Posted by heikis
So the memory divider is tied in with the NB "strap"? I thought they were separate.Quote:
Originally Posted by gtj
What confuses me I guess is the NB frequency (or "strap", I don't know what to call it, lol). I always thought the bus between the CPU and chipsets was the FSB.
I guess the bottom line is, if I'm running 400x9, I should run the 1066 "strap" with a 1:1 memory divider (if that's possible with the 1066 strap). Going up to the 1333 strap will require looser timings which = less performance?
Your last statement is correct.Quote:
Originally Posted by Eluzion
There are 4 relevant settings in the XBX2 BIOS.
Host Clock Frequency (FSB) sets the actual FSB clock frequency. Since the FSB is quad pumped, the default of 266 will give you an data rate of 1066. Setting 400 will give you 1600.
Processor Multiplier: On an E6600 it's 9 so again at 400 MHz FSB Clock, that puts your CPU speed at 400 x 9 = 3600 MHz
Reference Frequency: Badly named. It sets the NB Strap. It does NOT set any actual frequency.
333 = 1333 strap
266 = 1066 strap
200 = 800 strap
133 = 533 strap
They should have just named them Really Loose, Loose, Tight, and Really Tight. :)
Memory Frequency: Again badly named. The values are only valid if both the reference frequency and the fsb are set to 266 (which are the defaults).
To find your actual memory frequency, the formula is
Ratio = ( ref_freq / (mem_freq / 2))
Actual Mem Freq = FSB * Ratio
Check here for a calculator...
http://www.peakin.com/xbx2/calculator.html
Ok that was an awesome post..
hey btw is there a way to see on what strap you are on if there is no manual control over the strap like the badaxe2 with another board? Or you have to calculate manually?
From what I've read, you just have to run SuperPI and find where it starts losing performance. ;)Quote:
Originally Posted by shogo_ca
its great to see this. i cancelled my commando and keep this xbx2 :DQuote:
Originally Posted by Supertim0r
Good choice...... :)Quote:
Originally Posted by irenic
New bios 2507 released.
http://downloadfinder.intel.com/scri...ional&lang=eng
About This BIOS:
January 23, 2007
BX97520J.86A.2507.2007.0123.0952
SATA RAID info:
Intel(R) RAID for SATA - v5.6.2.1002
Marvell* 88SE6145 SATA BIOS – v1.1.0.34
PXE UNDI: Initializing Intel(R) Boot Agent GE v1.2.28
PXE Base Code: Intel(R) Boot Agent GE v1.2.42
Intel® Active Management Technology info:
Intel® AMT BX Firmware: v1.2.3
New Fixes/Features:
Fixed issue where ECC Mode was not properly displayed when
Performance Memory Profiles set to Manual in BIOS Setup.
Added workaround for HDD LED always being lit when Secondary SATA
Controller is disabled in BIOS Setup.
Fixed boot order for add-in SCSI controller.
Added support for certain SAS controller.
IRQ Fix for USB Interrupts.
Fixed failures seen with Vista* DTM BitLocker Drive Encryption
BIOS Interface Logo Test.
Fixed issue where Microsoft* Vista BitLocker System Check would
not pass.
Fixed issue where system would not recognize CTRL+ALT+DEL key
sequence from boot cycling machine.
Fixed failures with the TCG ACPI Event Log when running the Vista
DTM TCG TPM BIOS Interface Test.
Fixed issue where system hangs when trying to load FreeDOS*
bootable CD from a USB CD drive.
Fixed ACPI failures when running the Vista DTM TCG TPM Integration
Test.
Make sure to use memset with this board.
The BX2 will set your tRFC to 42 which is good for stability and not so hot for performance. Try moving progressively tighter in these steps, 35, 28, 21. If 21 is fine keep dropping the value by one til it isn't stable. Trying to set less than 14 will crash my system immediately. On the Abit AW9D Max less than 21 would do the same.
This version seems to be fixing a lot of x64 problems. :clap:Quote:
Originally Posted by Zucker2k
I'm going to try it.:)
WARNING!
Recovery jumper doesn't work in the new BIOS!
Overclocking sucked just like the last couple BIOSs and now I have a paperweight.
I'll have to try the floppy recovery method.
Ughh, these guys are as bad as nvidia anymore. Each release gets worse than the previous...
I was looking forward to this fixing the HDLED issue. Looks like 2333 is the only BIOS capable of running with a decent overclock.
The jumper is working just fine for me and it did fix the hdd led.Quote:
Originally Posted by clark_carty
Yes it did fix the harddrive led. :clap: The bios is dated on my birthday too.:woot: Everything is working fine for me now except it freezes up when you try to get temps from Everest Ultimate.Quote:
Originally Posted by gtj
They jumper works fine, the hard drive led finally works, the OC is the same as every bios release since 2333... :)
It's always done that for me. Somehow reading the sensors causes the vcore to drop to the default. There's something going on either in the BIOS or in Intel's SMBus driver.Quote:
Originally Posted by badboy
Oh, and Happy Birthday!!
Thank You. :) I was just wondering why it freezes up.Quote:
Originally Posted by gtj
does idcc work on your system?Quote:
Originally Posted by gtj
because it doesn't work in my system and i was thinking about a problem whit SMBus...
Sounds good then. It looked bad from the first post. Maybe I will give this BIOS a try this weekend then since it fixes the HDLED and doesn't affect the OC.
Any ideas if 4GB of memory can be seen by the bios on the bX2? Would I still need to move to 64-bit OS or does Vista 32-bit (what I'm running) able to address the 4GB?:confused:
It's not a problem at all for the bios since day 1. :fact:Quote:
Originally Posted by theonlybabyface
My Bx2 is running 4Gb with x64.
Yes, I know x64 will see it and I know that xp 32-bit will not. Question is...whether or not Vista 32-bit will see it? :rolleyes:Quote:
Originally Posted by GPSeek
According to this it should.Quote:
Originally Posted by theonlybabyface
http://support.teloep.org/vistaver.htm