<Edit: Courtesy of LWhitten., there is a copy of part 1 of this thread in doc format here. >.
Very nice! If you set the undocumented jumper above the CPU socket/left from the 3 voltage jumpers to "0vervoltage enbable" (position 1-2), you get the vcore voltage to 2.3 volt! It's not selectable anywmore, but works in jumper/and jumper-free mode.My locked XP 1700+ is now running at 11x159MHz (with Samsung PC2700).
Last edited by Senor Panadero : 03-15-2005 at 01:52 AM.
Ok, after much fun with the jumperfree mode issues, I have a problem with WinXP.
I can't seem to get WinXP installed properly on my system. I have two Maxtor D740X-6L 40 GB ATA 133 drives in a RAID array, and a Radeon 8500 graphics card. Plus a 56X CD in IDE0, and a Plextor 16X CD-RW in IDE1.
I build a floppy for the raid driver on another system (thanks Asus for not including this - the CD isn't helpful because XP wants the driver in A. It loads it fine, sees the array, and then proceeds to write a bunch of files to it.
Then the system reboots, and the the 2nd phase of the install comes up. The system finds a device with no name, and asks if I want to load it since it's not a windows certified driver. I say no. Everything then proceeds fine, but the system blue screens during the next boot into XP , and even in safe mode, I get a blue screen, just after loading the Mup.sys driver.
I'm stumped. I deactivated the 1394, sound, USB, etc... using the jumpers, and still no go.
Does anyone know how to tell the load order for drivers in XP? Preferably using the receovery console?
The error on the Blue Screen is the dreaded 0x7B.... error, and the message seems to point at something wrong with the disks, but it didn't seem to have issues during previous phases.
And did anyone else see this odd device with no name message during install? Does anyone have RAID running fine with XP?
Originally posted by frobnitz Ok, after much fun with the jumperfree mode issues, I have a problem with WinXP.
I can't seem to get WinXP installed properly on my system. I have two Maxtor D740X-6L 40 GB ATA 133 drives in a RAID array, and a Radeon 8500 graphics card. Plus a 56X CD in IDE0, and a Plextor 16X CD-RW in IDE1.
I build a floppy for the raid driver on another system (thanks Asus for not including this - the CD isn't helpful because XP wants the driver in A. It loads it fine, sees the array, and then proceeds to write a bunch of files to it.
Are you sure you are using the correct drivers? It's the PDC20276 controller on the A7V333, that is a different RAID controller from previous boards with the on-board LITE controller such as the A7V266. You HAVE to use the drivers from the A7V333 CD, including the "Txtsetup.oem" file.
Hi !!
I've got a strange problem ...
I've a A7V333 and 2x256Mo DDR.
But in the BIOS and in Win2K, it show me only 256 Mo.
The Asus Monitor in Win2K knows my RAM as SingleBank ...
And it's Double Bank !!
I've test the RAM on another computer and there were 512 Mo.
So the RAM is good ...
Is there a specific thing to do ?
Originally posted by frobnitz Ok, after much fun with the jumperfree mode issues, I have a problem with WinXP.
I can't seem to get WinXP installed properly on my system. I have two Maxtor D740X-6L 40 GB ATA 133 drives in a RAID array, and a Radeon 8500 graphics card. Plus a 56X CD in IDE0, and a Plextor 16X CD-RW in IDE1.
I build a floppy for the raid driver on another system (thanks Asus for not including this - the CD isn't helpful because XP wants the driver in A. It loads it fine, sees the array, and then proceeds to write a bunch of files to it.
Then the system reboots, and the the 2nd phase of the install comes up. The system finds a device with no name, and asks if I want to load it since it's not a windows certified driver. I say no. Everything then proceeds fine, but the system blue screens during the next boot into XP , and even in safe mode, I get a blue screen, just after loading the Mup.sys driver.
I'm stumped. I deactivated the 1394, sound, USB, etc... using the jumpers, and still no go.
Does anyone know how to tell the load order for drivers in XP? Preferably using the receovery console?
The error on the Blue Screen is the dreaded 0x7B.... error, and the message seems to point at something wrong with the disks, but it didn't seem to have issues during previous phases.
And did anyone else see this odd device with no name message during install? Does anyone have RAID running fine with XP?
Thanks,
Frob
OK, I have installed WinXP on a Gigabyte 7DXR that uses the same RAID chip and it gave me the same message as you got, i.e. it asks if it is OK to install a driver that has no name. You need to say YES to this, as it is indeed the RAID driver but XP doesn't seem to know this (!). I also have exactly the same issue with my Iwill board and that uses a completely different RAID chip but the same message comes up - I guess it must be XP being stupid...
I am watching this thread very carefully as I am about to upgrade to a very similar system setup (A7V333, 2xATA133 40GB, XP1800+) !!!! Due to upgrade beginning of April when I get paid, and when I can see if this mobo is good or not (used to have Asus mobo and it was the best I've ever had (P3B-F), but there seem to be quite a few complaints about documentation and jumpers for this board)
HTH
P69
__________________
Intel Core2Duo E6850 3GHz 1333MHz FSB | Asus P5-E | Radeon HD3870 | 2GB PC8500 CL5 DDR2 | Optiarc 20xDVD+-RW DL | Toshiba HD-DVD ROM | 2xHitatchi 320GB SATA2 HDD (RAID0)| Samsung 959NF 19" Monitor | ADSL+54g WiFi Router AP | Bluetooth | Enermax Pro 82+ 535W | Windows Vista Ultimate x64 + WindowsXP Pro SP2| 8Mbps ADSL
<b>Problem:</b>
System wont POST on each boot up (no video, no beeps, etc). To get the system to boot up, you must restart it many many times, and when it does POST, it brings you to the BIOS and says the CPU settings are incorrect and caused the system to hang on the last startup.
<b>Possible solutions:</b>
•Set to JumperMode with the correct dipswitches set to adjust to the correct CPU clock speed (<i>see your manual for the dip switch/SYSCLK location & diagram to adjust speed, pages 19-20</i>). Make sure the two undocumented Jumpers just above the AGP port (JP1 & JP2) are set closest to the CPU (JP1= 1-2, JP2= 1-2).
•Make sure you have <u>at least</u> a 300watt PSU! 350-400 is recommended for this board it seems.
•Check for lose connections on the motherboard -- take it out and reinstall it if you have to.
•Make sure your ram is a reputable brand -- with <a href="http://www.crucial.com/" target="new1">Crucial</a> being one of the best. <i><font color="maroon">Generic will almost always be a problem at some point!</font></i>
•Also make sure your ram is supported by your motherboard (non-ecc, ecc, the right speed [pc1700,2100,2700,etc]).
•Update to the latest BIOS -- at the time of this writing, the current BIOS for the A7V333 is 1005, which does not fix this specific issue.
I have seen posted on different forums very conflicting info about what jumper positions give which voltages.
I have mine set on the two pins nearest the AGP (pins 1-2) which according to some people gives 2.5V to others its 2.8V!!!. I can run totally stable with this setting with any memory timing (although enabling 1T setting won't work for me)
If I set them on the two pins nearest the CPU (pins 2-3), XP stacks as soon as it starts to boot regardless of memory timings. Total lock up. Again according to other people this should be 2.5V, to others its 2.8V!
Has anybody got a voltmeter to measure this? Please state your board revision just in case!!!
ASUS A7V333 rev 1.07 / 1.05 Bios
AMD1.4 T-Bird
2xCrucial 256Mb PC2100 set as 2 2 2 5 (1T enabled causes system to freeze/not post)
OK, I have installed WinXP on a Gigabyte 7DXR that uses the same RAID chip and it gave me the same message as you got, i.e. it asks if it is OK to install a driver that has no name. You need to say YES to this, as it is indeed the RAID driver but XP doesn't seem to know this (!). I also have exactly the same issue with my Iwill board and that uses a completely different RAID chip but the same message comes up - I guess it must be XP being stupid...
Thanks for the note. I discovered this last night about 2 AM. The thing is, XP crashes a couple times during the install, but after it all, it seems to work! Ugh. This is pretty strange.
I also fought through the jumperfree issue on initial startup, but that seems have been cured once to disable it and then renable it again. (!)
The board is pretty neat, but I still have one nagging problem. The CPU temp seems awfully high. It idles around 44 degrees, and that's with an 1900+ (no OC'ing yet), and a AX-7 heatsink with a panaflo Ultra 80mm fan on it that puts out about 44 CFM of air on it. I have heard others complain on other sites about this board reporting high temps, but I don't know if it's the MB or that I screwed up the heatsink install. I'm using artic silver III, and I think I applied it right.
Anyone else seeing this problem?
Oh one more thing - the MB can't seem to read the fan speed off the panaflo's. And it doesn't even read the fan speed off the special cable from my Antec 400W PS. Go figure.
Well, my system was so unstable that I almost gave up, but wound up removing one stick of the Samsung PC2700 DDR, and now it's steady as a rock under XP! These intermittent hardware errors can drive you crazy! Anyways - I'm running with 256 MB now, and very solid.
A few problems still though, that maybe others have found answers to.
One, the documentation says that the suspend to RAM in the bios isn't available under jumperfree mode. This is true even with v1005 of the BIOS. I have it running now with jumperfree disabled, but for later OC'ing, I'd like to have be in jumperfree mode. If I have installed the OS with this ACPI option available and turn then go to jumperfree mode, will this still work, or will this break suspend? STR seems to be the only to sleep with no fans running, so I'd really like that.
Also, I can't seem to to get the Asus PC Probe to report anything. It says it couldn't find any compatible devices on the baseboard. Did anyone here have that problem? Did I miss a step in loading a driver?
Re probe issue, I'm running version 2.16.01 and it appears to running fine so far. Didn't try to load the version on the mobo cd 2.15.08, so can't say that there is a problem with that one.
Re probe issue, I'm running version 2.16.01 and it appears to running fine so far. Didn't try to load the version on the mobo cd 2.15.08, so can't say that there is a problem with that one.
Hmm, not on mine. I have 2.16.01 installed (I removed the old one and then loaded it). It complains anout no LMinfo, and then says it doesn't see the two chips it's looking for, and doesn't try and load any probe monitor.
I wonder if I undid a jumper that it needs? Any ideas?
hmm, wonder if it's anything to do with the problem you also have with not reading the fans also.Maybe problem is not with probe but bios.
If you updated the bios at any point, did you load setup defaults after flashing? Possibly something was changed in the hardware monitoring in the new bios and needs to be reset before it functions correctly ???
Try unplugging the power supply fan monitor plug and if you have something connected to the jtpwr then try removing that plug as well....maybe they are causing the bios hardware monitoring to take a dump ??
Long shot's I know, but worth checking out.
You aren't running any other monitor like mbm are you ? As probe will not work if other monitor is in use.
Processors
Motherboards
Chipsets
Memory
Graphics Cards
Storage
Cases and Cooling
Mobile
Systems
Displays
Shows and Expos
Linear Mode
