Damn Felix, you get around!
Printable View
Damn Felix, you get around!
Randy, don't do that, the BT is a good board, don't run it over...
Intel has some design flaws in the SmackOver, I guess X58 by Intel is out of the question. I think 'll stick with my dear old BoneTrail for a while.
Still no signs of the DX58SO SmackOver in Intel site, guess only on the 17th when it's official.
However, lots of reviews already, performance is good but in some games at low res.
Don't like the 4 DIMM slots and the x4 PCIe slot, the blue heatsinks also don't cut it for me.
New LAN drivers v13.3 out. Can't download them though.
Funny, you can download drivers for the DX58SO already but if you try and find the board it's still not there. It seems to use a Realtek sound chip instead now, I guess the drivers would be better than IDT's anyway. I wonder if the most recent chipset INF files for this board will work with ours, although Intel states it doesn't support it?
I still didn't flash my BIOS to new 1893, but I got this MemSet MCHBar locked in My WinXP since BIOS 1782Quote:
Originally Posted by Sean-E-Boy
Smackover has four DIMM Connectors. Populate 3 for triple channel operation. Two or four will get you dual channel.
yes djs, that's correct. It does somewhat limit you with the max mem you can throw at it. OK, enthusiasts usually don't populate all sockets, it'll load your controller and hinder your oc, but still it's a bit of a bad option by Intel, in my opinion. If you want to add some more memory in the future you'll have to go for higher density modules, if possible.
In the end, I guess you'll not need the full bandwidth of triple channel anyway, but still...
Still can't dl the latest LAN drivers v13.3.
I see no one mentioning the issue with the power off and no boot resolved with the 1893 BIOS, well is it or not?
I have 1893 in place and when I cold boot it hangs and I must shut down
and then restart and it will finish booting. This has been with me from the
start.
Hi Sarge, long time no see.
It seems the bug is still there, Intel doesn't seem to be able to squash it.
Thanks.
Have come to the conclusion with my configuration with 4 DIMMs that the x38 mch just cant handle (and I am not really sure how to quantify this) what I am trying to throw at it.
Max stable FSB 450 @ 400x1333 = resulting in DDR3-1500 with average everest throughputs on the mem @ read: 9200MB/s write 9500 copy 8000
I know the memory is capable of more…rated @1800…but just cant coax the mch to allow it. Tried vmch up to 1.55 (not really sure how high I can go here, any idea?) and tweaked MCH GTL Ref some, but merely delayed the inevitable Prime95 failure.
Would be nice if you 2 things were possible with this board:
1) could save BIOS configurations (at least 2), and
2) could disable one pair of DIMMs from within the BIOS so you could have a superfast, rocketship configuration for gaming, etc. and a slower, yet more total memory configuration for other uses.
And sure, I could just buy a 2x2gb kit…if I just had a few hundo laying around.
Sean
Yes, that would be cool being able to switch off mem modules from within BIOS (or Windows, better yet). I don't think I have seen any mobo doing that, that would be Intel first I guess.
Can't remember right now but I believe we can save a profile in BIOS and use other settings, not sure though. Anyway, it's not exactly the same you want.
Don't know the voltage limits really but you must be close for sure. I believe someone (guess gtj) has already posted voltage limits for this board, not sure though.
Anyone tried populating all sockets with 2G sticks, for a grand total of 8G? Does it work? I believe the X38 chipset can only address 4G, correct?
What I found is if you populate all four, it greatly decreases your overclocks.Quote:
Originally Posted by Manel
Manel! Try to download drivers from here. Ppl at Intel's website support smoking something strange...Quote:
Originally Posted by Manel
Hiya! And this is happening only after cold boot?Quote:
Originally Posted by oldsarge
Is your memory running at 1600? Try to run it at 1333 Mhz. And maybe it is a good idea - to reset BIOS settings to default?
Thanx petr0id, I ended up being able to dl after a while.
Yes, I guess those guys at Intel must be on something sometimes, at least from some of their questions and remarks...
How come no one has confirmed that the no boot after power off issue is still there or not?
And are there any new settings in this release, like tRD?
ok, DX58SO is in Intel's site already.
Those guys have been hard at work on it, a few BIOS have already been released. I guess now they won't be releasing any new versions for our boards, not so often at least.
New version of IDCC for it too, v4.3.0.530.
Still, they haven't decided which audio it uses, acording to specs page it's Sigmatel (go figure, it's been IDT for ages now) but drivers are for Realtek. Usual Intel mess.
I was hoping this was the time Intel would go UEFI for the consumer boards, seems not.
Lots of fixes and new stuff, DDR3 1866 support...
Hi Friends,
I have been given the chance to change my DX38BT with another Mobo (X48 maybe) :D
and please accept my apologize to tell these here.
My reasons:
{
-I just wanted to install WinServer OS on this board, but intel doesn't support it (I know it could be installed somehow)
-Overclocking with this MoBo is not very high as others (I just heard)
-New Zalman 9700 Series clips don't fit on this MoBo (should be modded or buy a intel S-Type clip for it)
-And it has no SLI support, nor other X38/X48 MoBos have :D
- and other things that you surely know better than me (like Bios updates, and Specially IDCC, ...)
}
But I surely aware of the ability and power this Desktop board has in comparison with other MoBos.:up:
So I just wanted your suggestions on another X48 MoBo to buy (no DX48BT2).
I just want to have a benchmark of the new MoBo for myself and then go on stock for the remaining lifetime.
I have suggestions on Foxconn Blackops, but also saw other posts that say this board have often been used for benchmark world records only and not good for stock using.:shrug:
I would appreciate your suggestions.
Thanks
Hey guys. I've been an AMD guy for the last 10 years so bear with this Intel Noob. :p: I just built a system with the DX48BT2 and a QX9650. I'm trying to change the VID but no matter what I change it to, CPU-Z always says 1.238V! Is there something I need to change in the BIOS to change the VID? :help:
Thanks in advance. :)
System specs:
Intel DX48BT2
Intel QX9650
Patriot DDR3 1333 4GB (2x2GB)
Gigabyte 4870X2 2GB
Thermaltake 1200W PSU
WD 300G Velociraptor
Plextor PX-755SA
Asus DVD-E616A3T
CPUZ reads VID which doesn't change. I have never been able to
get it to read Vcore which is normal I guess. Get Everest to get an
accurate reading.
Thanks! I used Everest and could see what the actual vcore was compared to what I was setting in the BIOS. My QX9650 is now happily cruising along at 4GHz@1.35V in Everest (set to 1.4250V in BIOS) :D I'm not sure I want to go any higher because the temps are getting high. I'm using an old Danger Den TDX so maybe it's time to retire it and get a new more efficient water block.Quote:
Originally Posted by oldsarge
New Intel LAN drivers 13.4, guys at Intel are working hard on these drivers, so many released latelly.
Too bad they don't do it on other things, like IDCC that's been beta all it's life and will remain so I guess. It's no even supported under the newer 1893 BIOS.
Mahyar, too bad you're moving out. This is a good mobo, specially for stock settings. I can understand your reasons though.
Count on having issues with others boards also though. It's a matter of luck (or something) I guess, some people might say wonders of certain board while others have all sorts of issues with the same board. Sometimes it might be hardware issues, others it could be installed software, maybe others just pure luck (or lack of it).
Anyway, good luck with the new mobo, whatever you get. Asus is maybe the top dog, although I stop used Asus gear for long now. The Black Ops looks cool but I'm a bit tired of the marketing bull from those makers from that side of the world, with the fancy colors and pipes and the kitchen sink and whatever else they remember to throw in.
Moose, nice oc. Voltage is not critical still but you already have it quite up there.
feeling a little confused here...working with memory settings and pulled 2 of my 1gb dimms out just to see how much it is limiting me. anyway, was running at 333x1333 on the ram and had some stability issues, so i went to go (as i understand) looser to 400x1600, but freezes on windows boot up. tried several times and no go. but changed mem again, but now tighter to 266x1066 and loads, just as would 333x1333, but 400x1600 doesnt.
am i not understanding the straps correctly, or is there a fsb limitation to the 400 ref freq or something? trying to run at 460fsbx8.5 or even 8
also having the issue again where in bios, have cpu and mem settings to manual, but once windows loads, system is running at default. ??? very frustrating, have to pull the power and the button battery, allow complete power drain and cmos to reset (~1 hour) then it will apply.
I had this issue once I had DX38BT,Quote:
Originally Posted by Sean-E-Boy
it seems that Memory Frequency of 1600 is some fancy thing in DX38BT.
I never had a chance to boot up using 1600 Memory Freq set @ Bios.
Guys, remember this chipset (X38) was not originally intended for 1600 mem freq, only X48. Since both BoneTrails, DX38B and DX48BT2, share the same BIOS this was some sort of inheritance for our board, Intel would probably say the X38 doesn't support 1600 anyway.
Still, I believe some people run this 400x1600 ratio fine, it could be your particular board, or maybe your mem, this board is picky. Probably not.
Just another one of those things that make this board so particular.
There was way back some discussion regarding the different ratios I believe.
ok, and i dont know if anyone else has experienced this, but it really pisses me off.
changed something, wont boot, need to go to maintenance mode, and it freezes in the BIOS or before that even...have to restart like 20 times to be able to change setting back.
ok, back to the real purpose of this thread...
When stressing in Everest and have hardware failures when just testing the cache, is that going to be a vcore or vmch deficiency issue or maybe even GTL? reducing ram speed helps the problem, which makes me think mch, but not sure.
sean