Jump to content

DemonEyez_NL

Members
  • Content Count

    48
  • Joined

  • Last visited

About DemonEyez_NL

  • Rank
    New Member
  1. 280MHz!? :eek: Damn Yes, please post you're settings because whatever I do, my sticks will not run higher than 255MHz, even when i'm running one on one, without a divider. I'm at the point, that I'm pulling the hair out of my skull of frustration :sad:
  2. I was wondering if it were possible someone could mod the 28/7 bios so that the DRAM Response Time option (normal, fast and fastest) is available. In the current CFX3200-DR biosses it's missing. It's an option that always was present back on the DFI nF4 platform. Reason I'm asking, is that with my Crucial Ballistix i have serious trouble to get it over the 255MHz, even on 3-4-4-8 timings I had the same problem on my DFI nF4 Ultra-D, but after changing DRAM Response time from Fast (default) to Normal I was able to run 275MHz. So this option seems to have a lot of influence on stability when running with Crucial Ballistix PC4000 (Micron 5B -F chips). However, the option is not available on the CFX3200-DR
  3. I'm kind of having trouble with running dividers as well now I have an Opteron 165. Those timings I posted earlier were with my old X2 4600+ running 1:1 at 11x260HTT I got my Opteron 165 last week and it does 3000Mhz with 1.44v Right now I'm running with 150 (3:4) divider at 9x333HTT, my Crucials are running at 250MHz 3-3-3-8-1T This is all Memtest and Prime stable, so far so good The problems arise when going over the 255MHz on the ram (with or without a divider). I can't seem to get 260-266MHz stable One other thing I noticed, is that my bandwidth is rather low when running the sticks at 250MHz 3-3-3-8-1T Sandra reports 6400MB/s in the buffered test, in comparison with 6700-6800MB/s I find in reviews of other Micron 5B- F based 2GB kits Here is as you requested my stable settings : [B]Genie BIOS Settings:[/B] [COLOR=red] FSB Bus Frequency............................. - 333 LDT/FSB Frequency Ratio....................... - 4 CPU/FSB Frequency Ratio....................... - 9 RD580 HT PLL Speed............................ - High HT Bus MMOS Drive Strength.................... - 01 HT Bus PMOS Drive Strength.................... - 04 HT Bus Receiever Impedance.................... - 10 CPU HT Bus Drive Strength..................... - Strong CPU VID Control............................... - 1.475v (gives 1.44 in WinXP) CPU VID Special Control....................... - auto DRAM Voltage Control.......................... - 2.74v SB PCIE Voltage............................... - 1.84v NB Analog Voltage............................. - 1.34v LDT Bus Voltage............................... - 1.34v NB Core Voltage............................... - 1.34v [/COLOR] [B]DRAM Configuration Settings:[/B] [COLOR=red] DRAM Frequency Set............................ - 150=RAM/FSB:03/04 Command Per Clock (CPC)....................... - Enabled CAS Latency Control (Tcl)..................... - 3 RAS# to CAS# delay (Trcd)..................... - 3 Min RAS# active time (Tras)................... - 8 Row precharge time (Trp)...................... - 3 Row Cycle time (Trc).......................... - 7 Row refresh cyc time (Trfc)................... - 14 Row to Row delay (Trrd)....................... - 2 Write recovery time (Twr)..................... - 2 Write to Read delay (Twtr).................... - 1 Read to Write delay (Trwt).................... - 2 Refresh Period (Tref)......................... - 3072 Cycles DRAM Bank Interleave.......................... - Enabled Errata 94 Enhancement......................... - Disable Errata 123 Enhancement........................ - auto Odd Divisor Correct........................... - Disable DQS Skew Control.............................. - Off DQS Skew Value................................ - 0 DRAM Drive Strength........................... - level 5 (always weak) DRAM Data Drive Strength...................... - Level 2 (Reduce 30%) DIMM 1/3 Clock Timing Skew.................... - auto DIMM 2/4 Clock Timing Skew.................... - 450 delay Max Async Latency............................. - 8 Read Preamble Time............................ - 6 IdleCycle Limit............................... - 16 Cycles Dynamic Counter............................... - Disable R/W Queue Bypass.............................. - 16 x Bypass Max.................................... - 07 x Burst Length.................................. - Disable (4 Bursts) [/COLOR]
  4. No, they are not. Crucial is playing on safe so it stopped using Micron 5b-D and is now using Micron 5b-F, which are more stable but can't take as much. For running Micron 5b-F 275MHz @ 3-3-3-7-1T you'll need 2.80-2.85v in comparison to 2.7v for the Micron 5b-D There are some reports of failing TD1. I think that's because although it's the new revison of the PCB, those sticks still use Micron 5b-D chips and not the new Micron 5b-F chips. I myself bought two TD sticks last year in March. Around the beginning of december they finally started to give me problems. I did a RMA and am now running with TF2Y, which has a new revision of the PCB and has Micron 5b-F chips. Running 260MHz @ 3-3-3-7-1T with 2.78v Drive Strength 5 and data Strength 2 (it has been hell to work out the correct settings in my CFX3200-DR to get it stable)
  5. To me it seems that messing with Pmos, Nmos and HTTBus Reciever only effects the stability of the CPU and the LDT speed, and has really no effect on the Uli errors. I've been running 15-15-25 but those settings are not stable when Priming at 11x257HTT @ 1.488v and 5x257 LDT I've read on Xtreme that keeping Pmos higher than Nmos can help a lot when running a high HTT en high CPU clcok. It was suggested that 4-1-10 is a good setting when running high HTT with TCCD based sticks. It works for me, but only if do 4x257LDT, 5x is not possible (then again, I don't have TCCD in my system but Micron 5B-F) At the moment I'm doing 11x257HTT @ 1.488v and 5x257LDT with 5-5-10 and it works like a charm I'm still searching for a good guide (or any info for that matter) that explains how Pmos, Nmos and HTTBus Reciever have to be adjusted/are related to different CPU and Ram combo's
  6. Just wanted to let you people know that it IS possible run with both a Raid controller add-on card and with the ULi (non-raid) SATA ports enabled with bios 28/7 To work around the m5288 freezing problem with two SATA2 disks, I decided to buy a PCIe 1x Raid SATA2 card for 40 euro's to connect my two SATA2 Seagate Barracuda's in Raid0. But I've also got an Samsung SATA burner, which is connected to port 4 of the Uli controller. I disabled the Raid function of the Uli in the bios and changed the SATA-mode to "AHCI". During boot, the sub-bios of my add-on Raid card is loaded, but NOT the Uli sub-bios, so I don't get the "Option ROM can not invoke error" Tried it again, but now with the SATA-burner connected to the Silicon Image controller. But that didn't work, even when you're not using the Raid function of this controller and the Silicon Image chip is set to non-raid mode, the sub-bios is still loaded, and you'll end up with the invoke error. I ended up with the following: Raid Add-on card + Uli non-raid AHCI mode -> Works Raid Add-on card + Uli non-raid PATA mode -> Works Raid Add-on card + Silicon Image non-raid mode -> Invoke error Raid Add-on card + Uli Raid enabled -> Invoke error Silicon Image non-raid mode + Uli non-raid AHCI mode -> Works Silicon Image Raid enabled + Uli non-raid PATA mode -> Works Silicon Image non-raid mode + Uli Raid enabled -> Invoke error Silicon Image Raid enabled + Uli Raid enabled -> Invoke error I noticed one other thing, even with the Uli SATA functions totally disabled in the bios, my SATA is still recognised during boot and works fine in Windows
  7. Mailed DFI tech support last friday about the option ROM can not be invoke message this what is wrote and what i got back: They replied as follows: Very strange, because in beta Bios 5/19 the issue was resolved, only to come back in the later bios releases. I find it very strange to say the least that they not willing to resolve the issue again. Because what does the release notes say with this bios: Major Reasons of Change: 1. Fixed Silicon image ( SATA) + Uli (Raid ) combination. 2. Turn on ULI and silicon image raid at same time but Silicon image just support Raid5 only at the combination .
  8. Dear Rgone thanx for sharing the info, but what about the "Option ROM can not invoke" error? In the latest beta bios (28/7) it's still not possible to run the Silicon chip together with the Uli chip enabled. When will that issue be resolved? I mean, the only thing that the error is telling you, is that there's not enough room in the bios to load both chip biosses, surely that can be resolved
  9. Yeah, I was wonbering about that myself. In the latest beta (28/7) there's still the Option ROM can not invoke issue. When will that be resolved???Now I'm not using the Sil right now, but to avoid conflicts in the futute with SATA2 drives I was planning to buy a PCIe 1x Raid0 Controller add-on card. It's my understanding that you also cannot run with the Uli raid bios enabled and with an Add-on card Raid bios at the same time, it produces the same error as with Uli + Sil. I mean, the only thing that the error is telling you, is that there's not enough room in the bios to load both chip biosses, surely that can be resolved
  10. Yes, I tried this. I did a repair install, and before installed Windows from CD, I disabled Marvell Lan port 2, put my X1900XT in PCIe 16x #1 as usual and set the Uli chip in Raid0 mode. During setup I pressed F5, and choose "ACPI Multi Processor HAL" This resulted in Uli Raid on IRQ 19 and Marvell Lan port 1 on IRQ 18
  11. I thinks it's very simple. Before you do a install of Windows (Clean or Repair), first disable Marvell LAN port 2 in the bios and have the Uli Raid function enabled. Put you're graphic card in PCIe 16x slot one (upper slot). Now, let Windows install and you'll end up with The Marvell LAN port 1 on IRQ 18 and Uli Raid Controller on IRQ 19. Btw, where can I change the PCIe bus speed, I can't seem to find it anywhere? I'm using bios 28/7
  12. You were right! In the Uli Raid Bios config, my Samsung SATA burner is recognized and works perfectly. I'm running the following combo: Bios 28/7 + Beta 6.2.2.1. Uli Raid0 (Stripe 64K) 2x 120Gb SATA1 Maxtor Silicon Image Disabled No freezes at all
  13. @ RGone and Happy_Games Do you guys know when the "Rom option can not be invoked" issue wil be fixed in the 28/7 bios? With that bios you still can't run the Sil and the Uli controllers at the same time, but is seems to be the best bios to avoid the Uli errors.
  14. Okay thanx! I'll see if it's recognised in the Uli Raid Bios On my Ultra-D it worked flawlessly. I'm looking at you're sig, and noticed that you use bios 28/7 and have both the Sil and the Uli chips enabled. So you must be getting the "Invoke errors". I was wondering, are there any consequences due to this error once Windows is loaded or can you just ignore it?
  15. I was wondering, is it possible to attach an SATA DVD-burner to SATA-1 of the Uli Chip while at the same using the Raid0 function of this chip on SATA-3 and SATA-4. I was planning to connect my SATA burner to the Sil chip, but i'm running bios 7/28 and when both chips (Uli and Sil) are enabled, I get the "option ROM can not invoke" error.
×
×
  • Create New...