Ah!
I feel a bit dumb now :P lol
Thanks for the quick replies! Will have to get myself a QX series processor once they come down in price!
Cheers
Printable View
Ah!
I feel a bit dumb now :P lol
Thanks for the quick replies! Will have to get myself a QX series processor once they come down in price!
Cheers
Quote:
Originally Posted by evaninspain
the manual for the IP35 Pro is excellent with text description and diagrams to show the correct orientation...the audio, 1394 and USB cables can only be plugged in one way.
i think i will go back to 16.B04 to get my multi back above default....it is a bit frustrating that abit can not solve the unlocking of the full multi range of the QX9650.Quote:
Originally Posted by strange|ife
i, too, had a similar problem with vista64 with re-activation...i had to do it by phone since i swapped out some hardware, like the VC...i probably complicated my problem by swapping PCIe slots between the VC and Areca card since the current VC has a larger backside heatsink which interferes with my NB cooling fan.
Case: Cooler Master PraetorianQuote:
Originally Posted by Ace-a-Rue
Front panel has the following cables:
1) One thick grey cable with blue connector at end (connector has 5 pins on one side and 4 on the other). It looks like this might be the IEEE1394.
2) Two medium grey cables with a black connector at end (same type of connector as #1 above with 5 pins on one side and 4 on the other).
3) Two small grey cables with individual pins at the end with the following labels:
Small grey cable #1
a) MIC-POWER
b) MIC-IN
c) GROUND
Small grey cable #2
a) GROUND
b) R-OUT
c) L-OUT
d) L-RET
e) R-RET
Is my front panel a (HD AUDIO) or a (AC’97 AUDIO)? This doesn’t match up with the manual instructions on page 1.15 (section 1.8.6)..
I also have the standard rear panel that comes with the Abit IP-35 Pro MB that has three thick cables, two with red connectors and one blue connector
AND, I’m trying to connect a USB card reader with a single grey cable with a black connector at the end (connector has 5 pins on one side and 4 on the other).
WHERE DO I PUT ALL THESE CABLES ON THE MOTHERBOARD???
17 Beta bios:
http://myfreefilehosting.com/f/9f4bcadcd3_1MB
just tried it, bios shows cpu at 57C and thats running at 2.4 stock voltage! 16b3 shows 32C... its impossible to use fanEQ when the idle temp is so high.. i'm thinking this bug is a v1 issue, i got this board soon after it came out in the UK.
I am using IP35 Pro 14 bios and E8400.I set 1.325v in bios,bios status screen show 1.18v or so,CPUZ under load show 1.15v.What is the vcore i am running?Who have vcore reading point for IP35 Pro?Under load,temp is 52 C using Xigmatek SHDT1283,180cfm NMB fan and 32 C or so ambient.Any idea of what vcore i am running?
Can you give me the link to 16 official?Need that soon.Thanks.Is it safe to flash using flashmenu?I have kill 2 IP35 E from DOS flashing,stock speed!:shrug:Quote:
Originally Posted by fornowagain
ftp://ftp.abit.com.tw/pub/download/b...ro/m629b16.zip
flashing using DOS is usually safer, what are you doing (or not) that you've borked BIOS flashes on 2 boards?
evaninspain, looks like your CM probably uses AC'97 cable for FP audio.
You don't need to connect all the cables if you don't need the ports, e.g. I rarely install the PCI plate with extra USB/firewire ports.
Your USB card reader will plug into 1 of the USB headers along the bottom of the board cunningly labelled FP-USB ;)
Flashmenu is useless and an excellent way to force yourself to buy a new BIOS online. I used to use it all the time on my NF7-S back in the day and had no problems with it, but on this board its outright dangerous to include it on the CD!
Twice I had Windows crash on my WHILE it was flashing the BIOS. The first time Windows managed to come back out of the crash. The second time it BSODed right in the middle of doing its business.
The second time I lucked out since the boot block of the BIOS was functioning properly, I was able to boot the system into DOS using a floppy (which the BIOS demanded - a floppy is the only thing it'll let you boot from) and flash it properly.
I've used Flashmenu several times on the IP35 Pro without problems although I still recommend doing it in DOS.
Admittedly I use XP & I have a suspicion that it may not play as well with Vista, particularly 64-bit.
At any rate you don't want the version on the CD but 3.107.
What is going on with my mobo? I have ver 16 bios and c2d 8400 processor. Will be adding information on signature soon. My bios and uGuru shows cpu temp to be 30°C all the time. RealTemp shows 39°C. It does not change if I stress the cpu or anything. And why does cpu-z show my multiplier to be x6 when i'm not stressing cpu?
Sorry about my bad english :)
EDIT:
Got around that multiplier problem by disabling c1e and speedstep, also updated to 17 beta bios, still only temperature reading I got from processor is that 30°C. And now cpu-z shows core voltage to be 1.344V and uGuru shows 1.2 V as it should be.
3.107 refers to the latest version uGuru software (& device driver).Quote:
Originally Posted by Heidfirst
FlashMenu's latest version is 1.507:
http://www.abit.com.tw/page/en/downl...ET_TYPE=LGA775
the link doesn't work.Quote:
Originally Posted by 18 is # 1
Beta Bios Releases (includes IP-35 Pro - V1.7 Beta 02):
http://forum.abit-usa.com/showthread.php?t=122393
went there after posting my post..got it!
I tried the new Beta Bios 17. The bios is a little different with what it displays, but other than that no changes in temp readings. I'll do some prime95 occt stress testing and report back.
I however have successful flash IP35E in window but fail 2 times in DOS.I guess i will do it in window since i am more used to that.
It seems that with the new bios that cpuz doesnt read my voltage correctly any more. Other then that havnt scene any differences. Ofcourse Im just using a B3 3220.
I get this problem every now and then, sometimes after a reboot the CPU temp will stay stuck at 30°C on my board with 16B09. What I do to fix it is power off the PSU with it's switch on the back (Or just unplug it), wait 15 seconds, then hold down the power button on the front of the computer for 15-30 seconds. Switch the PSU back in or plug it back in, and then power up the system, this should fix it for you.Quote:
Originally Posted by natech
Kind of a minor annoyance, hopefully future updates will straighten that out.
Thanks for your help, but unfortunately it didn't help on my case :\Quote:
Originally Posted by HaTaX
Still getting 30°C. I think it has never shown anything else on my computer :(
Quote:
Originally Posted by natech
Quote:
Originally Posted by HaTaX
One of the sensors in the chip tends to stick in the wolfdales. Run coretemp or real temp and see if one of yours is stuck. My core #1 is stuck and doesn't change when under full load.Quote:
Originally Posted by natech
I'm not sure which sensor abit eq or the bios uses.
Real Temp 2.24 shows 39°C for both cores. And does not change :\
This is really irritating becourse this is my first WC rig and it would have been nice to get even idea of what the temp is. And how it changes if I change thermal paste to MX-2 and so on.
Do you guys think that the problem is in sensor which is located in processor? I have read many problems with wolfdale temp sensors but I'm not seeing any other with completely :banana::banana::banana::banana:ed up sensor :|
i hope you are not trying to take an "IP35 Pro" beta bios and flashing it to the IP35E board!...could be the reason why you have failed two times in DOS...Quote:
Originally Posted by OC4/3
Copy of a question posted on another form:
http://forums.anandtech.com/messagev...readid=2174615
.................................
ip35 pro + corsair XMS2 RAM, appropriate BIOS settings?
I understand that the timing for this RAM is incorrectly detected as 5-5-5-18, but is intended to be 4-4-4-12. I've heard as well that the voltage is off too. It's been a long while since I put a machine together from scratch, and I need some hand-holding on this one.
My processor is an e8400, nothing is overclocked.
These are the options under ADVANCED CHIPSET FEATURES:
CAS Latency Time (tCL)
RAS# to CAS# Delay (tRCD)
RAS# Precharge (tRP)
Precharge Delay (tRAS)
(I know that these are represented by the four numbers 4-4-4-12, but there are also the following options
Refresh Cycle Time (tRFC)
Write REcovery Time (tWR)
Write to Read Delay (tWTR)
Act to Act Time (tRRD)
Read to Precharge (tRTP)
Currently, all settings above are set to 'AUTO,' by the SPD. If I manually change them, I know what to do with the first four settings, but what do I do with the other 5?
I tried to just change the first four options to 4-4-4-12, left the rest to AUTO (and I forgot to change the voltage). Windows refused to boot up, informing me that config.sys was missing or broken. changing all the settings back to AUTO allowed for a successful boot to the OS.
What are my settings? Is there an article i can read? Does anyone have this config already who could help?
.................................................. ..
This is what memory he's probably referring to:
http://www.newegg.com/Product/Produc...82E16820145034
I'm using the same memory, and would also appreciate having the same information.
It seems like the bios "ought to": automatically detect and then enable the correct timing and voltage settings.
Thanks in advance.