AMD dual socket thread

[Eternalightwith]

Enzo makes some blocks. In fact when I saw the one heatsink that was over the CPU1 socket I thought it was Enzo. Might want to browse through their stuff at Petras or Sidewinders.

PS. ANy motherboards out there that don't require registered ram?
GRR, come ON AMD! I want a black dual socket mb with SB750 and nonreg ram friendly! Like now, dudes

[karbonkid]

All right, I got my board.

One of the memory controller heatsinks is missing-what can I do? Glu BGA sinks to it, make a custom block, or what?

eek.. that sucks. Where did you get it? I'd return it if I were you. I was afraid of things like this, which is why i was weary of getting mine off ebay, but it worked out ok. Plus, £90 shipped (brand new and boxed) wasn't a bad price .

PS. ANy motherboards out there that don't require registered ram?
GRR, come ON AMD! I want a black dual socket mb with SB750 and nonreg ram friendly! Like now, dudes

A lot of the boards including the K9ND series (and the equivalent Tyan board - they're pretty much the same boards; AMD reference design) will work with standard DDR2 if you turn off all ECC and Reg. options in BIOS. Apprently, though, Barcelona does not support non-registered memory.

P.S. I might be able to get some cheap FX-74s - Anyone think they'll work in the K9ND?

[Eternalightwith]

A lot of the boards including the K9ND series (and the equivalent Tyan board - they're pretty much the same boards; AMD reference design) will work with standard DDR2 if you turn off all ECC and Reg. options in BIOS. Apprently, though, Barcelona does not support non-registered memory.

P.S. I might be able to get some cheap FX-74s - Anyone think they'll work in the K9ND?

That's what Kayin said. He mentioned fx-74s working too.

The thing I don't understand about barcs not working with non-reg ram is that you can put a barc in a regular mb and use non-reg ram. So it's it the mbs fault?

[karbonkid]

The thing I don't understand about barcs not working with non-reg ram is that you can put a barc in a regular mb and use non-reg ram. So it's it the mbs fault?

You can't put a Barcelona in a "regular" Motherboard - Socket F is a dedicated platform for servers and QuadFX (2 Northbridges + Dual Athlon64 FX), basically the modern-day socket 940. Consumer-level Barcelona is Phenom on AM2, which does, of course support non-reg, but it's still a different platform. Anyway, with anything over 4GB you pretty much need ECC and reg.

[karbonkid]

OK, so I bought the FX-74s. I've never had anything even close to top-of-the-line hardware before, and it feels good. Hope it's not an addiction!

[msimax]

im not to sure fx74 can run on that board without being coded in the bios , i could be wrong though

[Xanadu]

I know that this is a dual socket thread, but Newegg has a couple of quad socket motherboards. It would be fun to see what could be done with one of those!

[karbonkid]

im not to sure fx74 can run on that board without being coded in the bios , i could be wrong though

I sure hope you are.... :S


EDIT:
Eek.. I just checked the MSI forums, and it seems it won't work..

Thank you for your support to MSI.
Sorry, MS-9652 can not support Athlon series CPU, which supports Opteron and Barcelona CPU.
Thank you

Still gonna give it a go though.. hopefully it'll just pick them up as the equivalent opterons. I paid good money for these processors
I don't really see any reason it shouldn't work; K8 doesn't need anything as complex as AGESA code to be recognised, and in effect all an FX-74 is just an 8222 with an unlocked multiplier.

If anyone has any more info i'm missing, please let me know

[msimax]

Yankee: Got the solution for memclk 266. It is easy, too easy for spotting it at once as it was very obvious.

Trfc is set too tight on memslot1. It is set to 75ns, and needs to be higher (105ns works fine for me). So as long as you can boot into win, wich is doable if I enable tristating and disabling rank interleaving.

This is a problem with many boards, especially the Abit AX78 wich I had earlier.

One "not so positive" thing: Clockgen freezes my system if I try to increase HTT by 1 above 250. Then I need another way of overclocking beyond 250HTT

i been fiddling with my computer and i found a way to set trfc on all slot using wpcreidt first i open up systools or memset that allows you to change timings





now im going to change it higher notice when i change it to 195 the program only sets to cpu1 but now using wpcredit i know where and what settings changed





now lets change cpu2 slots







you can see that device 25 function 2 is still stock so now ill add 6db21320



you see that it changes cpu2 slots and now that we got that out of the way im gonna see what changes the mem dividers so that you guys with barcy's can boot normally then change the trfc and other timings then switch the div to 800 and see what happens

[msimax]

just set it to what ever trfc you want in the program just to get the changes it made then allpy them to cpu2 in device25 func 2. also i used this table to help me where to look for the timings

http://www.rebelshavenforum.com/sis-...;f=52;t=000028 the am2 table

[msimax]

again just showing where to look for the changes

[msimax]

testing the div sometimes i get lockups so i used R/W everthing and found out those registers change every second on their own

[yankeex86x]

Thanks for the tips msimax!
but i don't think that the trfc is giving problems....
I just installed the 32bit verson of Vista Ultimate and now I have both: 32 & 64 Bit.
The common bootable set for DDR is 667MHz, and both OSs runs just fine.
When setting the DDR to 533 the 64bit system don't boot, while the 32bit boots.
In both OSs the 800MHz DDR setting didn't work, but this setting works flawlessy with Mandriva One 2007 Live32Bit.....
So.... where is the main problem?????
I think that this WS/b is too experimental for standard use....
I'm thinking about getting a Supermicro H8DA3-2 with the MCP55Pro (L1N64 has the MCP55) chipset.... ASUS has made too many bad promises with our board.....

[msimax]

yankee are you able to run memtest with with the 800 div or better yet windows ver. of memtest thats on the UBCD??

[msimax]

as you can see this bios is garbage for memory clocking because the timings you need to loosen cant be done in the bios. i just tried 280x12 800 div @1120mhz in the bios with no boot up the same settings with the 667 div i can boot up normally. i tried contacting asus but they treat like a idiot with copy paste answers but wont update with a better bios.. so since im getting no support with board my next build will be a single socket probably Foxconn A79-S or dfi with a 9950. dont get me its a good board to play with stable as a rock if you dont overboard but without support i wont spend no more money on it.

this is ex. on how the bios keeps everything to tight

[karbonkid]

Some very useful tips there, msimax, thanks. Hopefully I'll be able to put them to good use in the overclocking tool i am planning to make.

Are you using L1N64? That board has 2 nforce 680a chipsets, right? Could it be that the changes you make with memset are only being applied to one memory bank because of that, because it is only looking at one of the 680a chips? ie., maybe on MCP55/MCP55pro, you will only have to apply the settings once?

[knopflerbruce]

I tried my K8N-DL a week ago, btw. Nice board, but there are NO locks on it - which I think is the main reason for the maxhtt @ 275MHz

I've heard that NF3 pro 250 has a pci lock, is that correct? If so, it should be alt better than K8N-DL for OC'ing? I know NF3 is a very good chipset, and I don't need pcie anyway

[msimax]

i think the programs were designed with one cpu in mind except RMMA which you can change timings on both mem controllers but their timings are so basic. i need the timings like aod in the bios or a ntune hack that allows more than 250 theirs gotta be a way for that because if you set higher in the bios ntune is also higher i might just email nvidia for help with that.or somebody can come up with a clockgen themselves, theres something in ntune that lets you clock with 2cpus installed

[karbonkid]

Yeah, hopefully if I can find the right registers my linux tool will be able to clock both CPUs by using the different offsets (like you did manually). In your experience, does the am2 table on rebels haven correspond also with socket f, or are some things different?

[msimax]

right now im not sure but just using it as a reference to see were to look for specific timings. now i just use r/w everything change settings using aod a watch what changed in real time then apply it to the second cpu

[karbonkid]

Yeah. It would be a lot easier if AOD, ntune and memset worked in WINE, then i could do the same as you. i guess i'll be digging through AMD tech-docs instead...

[karbonkid]

So, I got the FX-74s today.

I put one in the CPU0 slot, put 2 sticks of 512mb PC3200 ECC reg. memory in, fire it up.. here's what happened:

1. Enters VGA BIOS.. ok
2. Phoenix BIOS - "Unrecognized CPU", "1024mb memory" (at this point I think it's working and I am happy.. still no POST beeps though)
3. I press F2 to enter setup
4. Enters SCSI RAID controller BIOS, scans LUNs... fair enough
5. screen goes grey.. freezes (at this point I am sad)

So I figure it has to be the RAID controller causing the problems.. I remove all the add-in cards except for graphics, clear CMOS etc. Turn it on again and
get as far as the VGA BIOS (which slowly flickers on and off for a bit) and then the screen goes black.

I clear CMOS and try again. When I turn it on, I get nothing on the screen. The board does give a beep code this time though.. it goes BEEP (pause) BEEEEP BEEP BEEP and then keeps repeating BEEEEP BEEP BEEP.

I tried eveything.. swapping in the other CPU, putting in 2 CPUs instead of 1, different RAM, one stick of RAM, different graphics card, graphics card in different slots, no graphics card, putting the RAID controller back in.. same problem.

Anyway, I'm guessing the beep code I'm getting is classified as:

1-1-2 CPU test failure The CPU is faulty. Replace the CPU

Which is fair enough - there's no microcode for FX-74 - but how come it actually got as further than the Phoenix BIOS screen first time round? How come it just shrugged that off with an "unrecognised CPU" message but now refuses to do anything?

EDIT:
I found a bent pin in the CPU1 socket. Fixed it without a problem. Then, when I was putting a processor in CPU0, I dropped it and bent some more pins . I managed to fix most of them but one of them is missing that tiny bit that curls over at the top to contact the CPU - I think it will still make contact, but not by much... I guess I need to find an opteron to test with...

EDIT EDIT: After looking at it some more, it seems it's not going to make contact after all. Contacting MSI to see if they can fix it / replace the socket...

[yankeex86x]

Hey MsiMax!
forgive me for my late response...
I tried the memtest 2 times for every divisor.... (vista mem test)
It gave me no errors for all settings (533,667,800) .....
The second test is and in depth test... so ram modules has no problem to work with barcelona even at 800MHz....
I think that AMD has serious problem with that barcelona IMC.....
However I can confirm that Vista 32 boots with 533 memory setting while Vista 64 didn't....
With Vista 32 I could reach 2.6GHz stable using clockGen (I've only 1 CPU).
I'll try using Systool....
NB: It's known that 64Bit OSs give more stress at the IMC, maybe we need to wait for Shangai/Deneb to reach some higher frequencies... For now I'm hold behind 32bit systems and 6Gb of wasted memory ram (only If I want to overclock).

Update:
There is a difference between Slot A1 and B1:
When I install only 1 Ram dimm in solt A1 the OS won't boot with 533 while putting it into the B1 slot the system boots flawlessy....
Likmark may try installing dimms in B1 A2 and B2 leaving the A1 free... and the system might boot with 533 setting too

[yankeex86x]

@Karbonkid
Hey! the first time I swapped my bios into the WS/B the system booted up with my old FX-74 once a time, then It never booted again (with FX-74).
I had to wait for Opterons to make it bootable.
Try these steps:
a) Fx74 don't support Registered memory modules, try putting standard unregistered ECC/nonECC memory.
b) If it won't boot again, find a compatible opteron and your original mobo's bios; after that go to the ASUS website an download the L1N64WS bios and extract the FXs microcode (I may send it to you if you'll need it), then place the FX microcode in your mobo bios. It will work with no problems with unregistered memories, even with PC2-6400(800MHz)
Transferring CPU microcode is not hard to do..... either is not so easy....

Lastest Update: FX microcode is also present in L1N64-SLI WS/B .... but the WS/B works only with reg dimms....

[karbonkid]

@Karbonkid
Hey! the first time I swapped my bios into the WS/B the system booted up with my old FX-74 once a time, then It never booted again (with FX-74).
I had to wait for Opterons to make it bootable.
Try these steps:
a) Fx74 don't support Registered memory modules, try putting standard unregistered ECC/nonECC memory.
b) If it won't boot again, find a compatible opteron and your original mobo's bios; after that go to the ASUS website an download the L1N64WS bios and extract the FXs microcode (I may send it to you if you'll need it), then place the FX microcode in your mobo bios. It will work with no problems with unregistered memories, even with PC2-6400(800MHz)
Transferring CPU microcode is not hard to do..... either is not so easy....

Lastest Update: FX microcode is also present in L1N64-SLI WS/B .... but the WS/B works only with reg dimms....

I didn't know they didn't support registered memory.. that kind of ruined my plan . I did try with some standard DDR2, the board just kept bleeping at me - it will only support non-ECC (and probably non-reg.) after it has been disabled in BIOS, and of course I can't get into BIOS if I can't POST...
I had assumed that since WS/B only work with registered modules, and that it "supported" FX chips, that FX chips should support registered memory?

Hopefully MSI will agree to repair my board and I can do what you said, use a cheap opteron to start with. How could I be stupid enough to break a pin! I still don't get why they don't still put pins on the CPUs - much easier for us end users. Must be a cost thing I suppose; gold ain't cheap...

I'm working on inserting the microcode, but it's going to be a little more difficult because L1N64 uses Award BIOS and K9ND uses phoenix...