Printable View
I assume he has since he recommended it. Let's hope he has at least used it ;)Quote:
Originally Posted by Randy
I was thinking of picking up one of these boards myself a small while ago, but now I'm not too sure. I'd like to see a lot more quad results before I jump on board.
I wont have access to that computer until Wednesday. At that point I can give first hand impressions of the MST Tool.Quote:
Originally Posted by Randy
Aside from people having good things to say about the latest version of the tool in Vista, here is the other reason I feel there is a chance it will help solve the S3 problem:
At first glance it seems obvious that the new Intel BIOS has made a firmware level (BIOS) change that leads to the malfunctioning of S3 sleep state. So at first glance it is reasonable to just chalk it up to a BIOS bug and not consider the software environment.
However, recall that under WinXP, for example, if you installed XP with S3 enabled in the BIOS - your computer would enter S3 sleep just fine. If you later disabed S3 in the BIOS and booted fully into Windows, S3 would be disabled. Subsequent to that, however, if you re-enabled S3 in the BIOS, unfortunately the computer does not return to being able to enter S3.
S3 sleep state, even though its being disabled was caused by a BIOS change, the only way to re-enable S3 was by using a software tool called dumppo.exe (provided by Microsoft.)
So, there is a scenario where a BIOS settings change made changes to a hidden part of the power management system in Windows. Putting the BIOS settings back proper made no difference - S3 remained disabled. But using a software tool to repair hidden power management settings was effective in re-enabling S3 capability.
Bringing things full circle? The MST Tool was developed to perform dumppo.exe functions on Windows MCE and later Windows Vista. For this reason, and considering the scenario above, there is a reasonable chance it could solve the S3 problems with the latest Intel BIOS update.
Where I am skeptical is if the change in the BIOS setup makes changes to the hardware timeouts which prevent S3 from even being possible in the first place. (Firmware bug prevents certain hardware from shutting down.)
Right now I am slightly more confident than not.
Feel free to wait until later this week when I can report back first hand.
Or if you want to give it a try in the meantime, just make a quick image with "Complete PC Back Up / Back Up My Computer" and give the tool a try. (Vista Business and Ultimate only.) I know a number of folks who have had no problem with the tool, so I highly doubt you are going to damage your PC. But it is always wise to have a backup image before making base level OS changes.
gtj I'd be very interested in trying out your Linux driver. Is it available anywhere?Quote:
Originally Posted by gtj
I'll upload it and post the link when I get home from work tonight.Quote:
Originally Posted by vipertwo
First I want to apologize for how long this post is going to be. First the highlights of my system;
Intel DX38BT motherboard with bios version 1478
QX9650 CPU (I had a QX6850 in it and all the problems I’m having I had with that CPU as well)
4 gig of Corsair WIN3X40961600C7DHXIN memory
2 ATI HD3870 Video Cards
Watercooled CPU
I have several problems that I cannot seem to resolve. The first problem is more of an annoyance but maybe someone knows what to do. Sometimes when it boots, just about 100% of the time after it sits for a bit (I travel quite a bit) and you turn it on, it turns itself on and off several times and then eventually boots. It will also do this after changes to the bios. During the changes to the bios sometimes it will boot, sometimes it won’t. When it won’t it just keeps turning on and off and eventually if I shut off the power supplies and give it about 5 minutes, it will boot ok, even if you change nothing in the bios. Even if I leave the bios at default settings it will do this after it sits for a few days and you turn it on. I contacted Intel and they told me it was the memory because the board is only designed for 1.5 volt memory and that memory runs at 1.9. I also tried some of the same memory but not Intel “certified” and had the same problem. (I also had this issue with another DX38BT board. The initial board I received did this, but the chipset drivers were messed up and it would not recognize the USB ports. Something when very wrong in the bios recovery (probably the fact that the optical drives were not really recognized during boot) so I sent that board back).
Second problem.
I have an issue, or really several issues overclocking the CPU. The main problem, I think, is the fact that I can’t seem to be able to actually change the CPU core voltage. I can change it in the bios, but when looking at CPU-Z it doesn’t show any change in voltage. In addition to this the CPU core temp agrees with the fact that voltage is not changing. When running at 100% load I do not see any change in core temp (averages about 100 F at full load no matter what CPU voltage is set at). However when I use the 300 mV offset there is clearly a significant increase in CPU core temp at 100% load (CPU core temp goes to about 140F with the offset at full load). Both the QX6850 and the QX9650 exhibited these characteristics.
From an overclocking standpoint with stock voltage I can get it about 3.65 GHz. With the 300 mV offset I can actually go to 4.42 GHz. No matter what combination of voltages, bus speeds, CPU multiplier, etc, I cannot set the bus speed faster than about 360 MHz or it is not stable. From a memory standpoint I normally just use XMP Profile 1, which is automatic memory overclocking. But I’ve had the same problem when I use my own memory timings.
Of course I talked to Intel about this issue as well and they won’t even talk to you if you are overclocking. I don’t want their help, I just want to know if there an issue with their hardware or something with my system.
I hope there is something easy that I have messed up or am overloocking. If anyone can offer help I would really appreciate it.
jerry
Oh, I can't use the Intel IDCC because I'm running XP Pro 64 bit and they don't support this OS. So I can't use that to verify anything.
j
Don't listen to Intel.Quote:
Originally Posted by GJW
I have the same problem. It's an annoyance I don't deal with by just leaving it on and crunching for WCG. :)
It's got something to do with the board resetting the voltage regulators.
Don't listen to Intel.Quote:
Originally Posted by GJW
CPU-Z and CoreTemp report the VID that's requested, not the actual voltage. Get Everest. It'll show you the actual voltages as reported by the sensor chip. The guide in my sig talks about this and even though it's for the D975XBX2, 99% applies to the DX38BT.
STAY AWAY FROM THE 300MV OFFSET UNLESS YOU ARE BENCHING WITH SUB-ZERO COOLING. Think about it...If you have voltage set at 1.5000 and set the 300mv offset, you're pumping 1.8v to the processor. Not good.
You have to manually set the memory timings or you won't be successful. Use the calculator in my signature to see what results from various FSB, Reference Frequency and Memory Frequency settings. Also DDR3 memory is VERY sensitive to voltage, both under and over. You really have to take your time with this board.
What are you goals for the board? It'll help us give you some guidance.
Oh yeah, :welcome:
IDCC is also useless. Get Everest. It does everything you need.Quote:
Originally Posted by GJW
http://www.lavalys.com/forum/
Ok, thanks for the help so far.
I have Everest but I just have not installed it on that machine yet. I'm not running the 300 mV offset, I just tried it to see what would happen. I do have a sub zero cooling system ordered but it won't be here for about a month (Cooler Express 2009). Goals for the board, that's a good question. To be totally honest it's a toy for me. The only thing I've done well consistantly in my life is make money so I decided I just wanted to build something really fast and cost was/is not an issue. I do play a few games with it (CoD4, Halo 1&2 and a few others), but it's mainly just for messing around with. I just want it to be around 4 gig, that's my personal goal.
I had a D975XBX2 with a QX6700 and had pretty good luck with it, which is what made me buy this board.
I won't be able to play with it again until this weekend, as usual I am going out of town to Dallas tomorrow morning. I will install Everest and play some more this weekend and report back. I'm gone again all next week as well, so I only have two days to play with it over the next 10-12 days.
Thanks for the help so far.....
jerry
I just wanted to step in and show off a bit of hardware I won... The Bonetrail V2... X48 chipset.
This is the Bonetrail Version Two that uses a X48 chipset instead of the X38... It is, of course, an unreleased Engineering sample... as far as I can tell, the board looks the same, but the chipset is obviously different.
The Proc is an Engineering sample QX9650... I had it up to 4.7 on water, after only 30 minutes with it in an Asus P5K premium, so I can't wait to see what it does with this. I will keep you posted :)
Lucky U ^^Quote:
Originally Posted by dexaroni
Hey was it hard to get those, from intel?
If not i'll try get one ES proc from northen HQ, when i'm ready with my waterchiller project :D
:ROTF: IDCC is USELESS, U CAN only RAISE FSB 10MHz per BOOT :ROTF:Quote:
Originally Posted by gtj
Use newest SetFSB and use this setting: SLG505YC256BT IF u want to OC from windows.
I know people who know people who sponsored an overclocking contest that I won.Quote:
Originally Posted by s0lid
That is where the proc came from... the mobo came from a friend, and he got it from an intel rep... I don't know where it came from before that... not entirely sure that I want to either lol.
OK ty and welcome to XS m8 =)Quote:
Originally Posted by dexaroni
:welcome:
E: oh i only looked ur amount of posts not ur join date but what ever =D
In installed Everest this morning, set the CPU voltage to 1.3 and sure enough it shows voltage as 1.238. Same problem I had before.....Stuck on stock voltage for the CPU no matter what the settings.Quote:
Originally Posted by gtj
jerry
No dice on my first try with the MST Tool.
This is frustrating. I can't believe Intel would leave a BIOS that creates true power management problems considering their boards go into so many mainstream consumer PCs.
Like many of you I keep this computer in one of two states: Always on, or fully shut off when I am away. So functionalyy for my own situation this is not a huge deal.
But in the past I have had scenarios where S3 / Suspend to RAM was a necessity. And ironically, after struggling with S3 on some Taiwanese brand mobos; part of the reason I switched to Intel mobos was for their excellent power management handling. So, yeah, I get the general disappointment with this latest BIOS.
I just cant help but feel I / we are missing something here. Intel has always been good about keeping power management working properly, even innovating (Intel QUick Resume Technology.) And dumppo.exe tools like MST Tool have been so extremely useful in the past.
Im gonna try tweaking around with thw MST Tool and some different BIOS settings.
Ill keep yall posted.
Voltage control may still be on auto in your BIOS. Double check that. If it is on auto, set it to manual and then you should be good to go :up:Quote:
Originally Posted by GJW
I was chalking it up to a temporary "cold boot" bug. In the past few years I've seen Intel fix these with BIOS updates - like on Dragontail Peak and Blue Mountain2 mobos.Quote:
Originally Posted by gtj
But from what you are saying, maybe with this mobo there is nothing TO fix here? (A normal stage stepping operation of the VRs?)
Not to sound too stupid but where does one set this from auto to manual? I go into the bios, open up the CPU voltage menu and then pick the voltage. I have been through the bios and I didn't see a way to do this. I could certainly have overlooked something, I hope I did.Quote:
Originally Posted by Ymir
jerry
The actual voltage will show lower than what's set. Try bumping it up to 1.4000 and see what Everest reads. Also read the voltage when the CPU is under load to make sure it's not keeping the voltage low because it's idle.Quote:
Originally Posted by GJW
Thanks, looking forward to giving it a go.Quote:
Originally Posted by gtj
New IDCC with bug fixes here: https://download.desktopboards.com/idcc/
This one holds my customized fan settings between reboots now. It claims it needs BIOS 1478, but works fine with 1379 since I'm not updating due to the S3 Standby Failure in 1478.
And of course I totally forgot to upload it so I'll do that now and post the link in about 30 minutes. :)Quote:
Originally Posted by vipertwo
OK, posted at http://www.peakin.com/x38/asc76xx.zip
Unzip it in an empty directory and read README and INSTALL
Thank you very much!Quote:
Originally Posted by gtj
At first I just saw this error in dmesg:
The chip seems to be an aSC7621a (with an a on the end), i.e. COMPANY=0x61 and VERSTEP=0x6d. I wasCode:[ 4558.898570] i2c-adapter i2c-1: asc76xx not found at 1,0x2e.
not able to make your kernel module work unless I patched it like this. The kernel is linux version 2.6.24.
Then afterCode:--- a/asc76xx.c 2008-02-22 11:23:17.000000000 +0000
+++ b/asc76xx.c 2008-02-22 14:17:07.000000000 +0000
@@ -37,7 +37,7 @@
};
/* Insmod parameters */
-I2C_CLIENT_INSMOD_2(asc7611, asc7621);
+I2C_CLIENT_INSMOD_3(asc7611, asc7621, asc7621a);
#define INTERVAL_HIGH (HZ + HZ / 2)
@@ -46,7 +46,7 @@
#define PRIORITY_LOW 1
#define PRIORITY_HIGH 2
#define FIRST_CHIP asc7611
-#define LAST_CHIP asc7621
+#define LAST_CHIP asc7621a
#define MASK_ASC7611 0x01
#define MASK_ASC7621 0x02
@@ -80,7 +80,7 @@
.addresses = {0x2c, 0x2d, 0x2e, 0x00},
},
{
- .name = "asc7621a",.chip_type = asc7621,
+ .name = "asc7621a",.chip_type = asc7621a,
.chip_mask = MASK_ASC7621,
.company_reg = 0x3e,.company_id = 0x61,
.verstep_reg = 0x3f,.verstep_id = 0x6d,
I see the following (with debugging messages turned on):Code:modprobe asc76xx
dmesg
Which looks ok. ThenCode:[ 267.141938] i2c-adapter i2c-1: Autodetecting device at 1,0x2e ...
[ 267.157915] i2c-adapter i2c-1: Checking 0x2e,0x61,0x6d against 0x61,0x69
[ 267.157918] i2c-adapter i2c-1: Didn't match asc7611
[ 267.173897] i2c-adapter i2c-1: Checking 0x2e,0x61,0x6d against 0x61,0x6c
[ 267.173900] i2c-adapter i2c-1: Didn't match asc7621
[ 267.189888] i2c-adapter i2c-1: Checking 0x2e,0x61,0x6d against 0x61,0x6d
[ 267.189891] i2c-adapter i2c-1: Matched asc7621a
[ 267.189893] i2c-adapter i2c-1: Detected asc7621a device at 1,0x2e with COMPANY: 0x61 and VERSTEP: 0x6d
gives the followingCode:sensors
I only have a fan connected to the MCH fan header on the motherboard so I would haveCode:asc7621a-i2c-1-2e
Adapter: SMBus I801 adapter at 2000
in0: +1.21 V (min = +0.00 V, max = +3.31 V)
in1: +1.01 V (min = +0.00 V, max = +2.99 V)
in2: +3.24 V (min = +0.00 V, max = +4.36 V)
in3: +4.99 V (min = +0.00 V, max = +6.61 V)
in4: +11.84 V (min = +0.00 V, max = +15.94 V)
fan1: 0 RPM (min = 0 RPM)
fan2: 0 RPM (min = 0 RPM)
fan3: 0 RPM (min = 0 RPM)
fan4: 0 RPM (min = 0 RPM)
temp1: -62.0°C (low = -127.0°C, high = +0.0°C)
(crit = -21.0°C) sensor = diode
temp2: +44.2°C (low = -127.0°C, high = +127.0°C)
(crit = +65.0°C) sensor = thermal diode
temp3: +46.5°C (low = -127.0°C, high = +127.0°C)
(crit = +65.0°C) sensor = transistor
temp4: +41.8°C (low = -127.0°C, high = +127.0°C)
(crit = -128.0°C) sensor = Intel PECI
temp5: -62.0°C sensor = Intel PECI
temp6: -85.0°C sensor = Intel PECI
temp7: +96.0°C sensor = Intel PECI
temp8: +118.0°C sensor = Intel PECI
expected to see one non-zero fan speed -- but actually I don't see it in
the bios (v1397) either.
Does that look ok to you? Do you know how to interpret the figures -- i.e. which fans and temps are which? The CPU is a QX9650.
I only have a fan connected to the MCH fan header on the motherboard so I would have
expected to see one non-zero fan speed -- but actually I don't see it in
the bios (v1397) either.
Latest IDCC docs state that MCH header RPMs are not monitored.