Author Topic: ATI and NV GPUs in same host (Read 50319 times)

Raistmer · « **on:** 07 Jun 2010, 09:42:17 am »

Host config:
Windows 2003 server x64, 2 PCI-E slots. First slot occupied with NV GSO9600, second - with HD4870.
GSO9600 works well, Cat 10.4/10.5 refuses to install drivers for HD4870.

Will try different configs and update post. Some advises, please?

UPDATE:
1) NV driver uninstalled - cat 10.5 fails, no image at boot time
2) GSO9600 removed from first slot, HF4870 leaved in second slot - screen became active.
(and windows requested re-activation! WTF! )
Catalyst still doesn't see GPU

3) HD4870 moved to first PCI-E slot. Cat 10.4/10.5 still doesn't see it

Cat 9.10 installed, but BOINC says no usable GPU found.
Cat 10.5 still doesn't see GPU .

Ghost0210 · « **Reply #1 on:** 07 Jun 2010, 02:22:42 pm »

Hi Raistmer,

I'm running:
Win7 x64
1 * HD5670 Cat 10-4 drivers PCIe Slot 1
1 * GT240 197.45 Drivers PCIe Slot 2
1 * GTX260 197.45 drivers PCIe Slot 3
Was a pain to get installed - had to install nV cards first then, install Cat 10-2 then step through the drivers and control centre. Cat 10-5 will not work with nV drivers - just got white screens at boot
Extract the drivers from the .exe but cancel the install as I had to install each from the command line, the install app just won't work.
Have to install from the bin64 folder, on mine was C:\ATI\Support\10-4_vista64_win7_64_dd_ccc_wdm_enu\Bin64 then run the atisetup.exe -install command and should work fine

Hope this helps

Raistmer · « **Reply #2 on:** 07 Jun 2010, 02:37:13 pm »

Thanks, but I was not able to install Cat 10.4/10.5 even when NV card and drivers were removed

Claggy · « **Reply #3 on:** 07 Jun 2010, 03:59:36 pm »

Which drivers were you tring to install? the Win Vista/Win 7 version or the XP version?
I couldn't find drivers for Windows 2003 server x64,

Claggy

Raistmer · « **Reply #4 on:** 07 Jun 2010, 04:31:10 pm »

XP version of course

Ghost0210 · « **Reply #5 on:** 08 Jun 2010, 09:17:30 am »

not sure then
I know OzzFan had a similar problem with nVida and ATI graphics drivers not working on WHS (basically Server 2003 repackaged) on Seti Main
Have you tried with any older drivers apart from 9-10 - I had to start with 10-2 for Win7 to accept the drivers and work up from there

Claggy · « **Reply #6 on:** 23 Jun 2010, 06:44:47 am »

Raistmer,

Slicker at Collatz posted this snippet about Win2K3:

Quote

Here's a piece of FAQ from the ATI website:

ATI driver information for Microsoft Windows Server 2003

All drivers for Windows Server 2003 are maintained and deployed by Microsoft. This operating system currently provides drivers for RAGE XL products only.

While Windows Server 2003 display drivers are not available from ATI directly, you may obtain updates through Windows Update, or other deployment option from Microsoft.

Windows Server 2003 is positioned as a business and corporate enterprise server Operating System. It is not intended for home or personal use.

Please refer to Microsoft's website for detailed information.
http://www.microsoft.com/windowsserver2003/default.mspx

INFO-BASE# 4227

KEYWORDS: Windows Server 2003 Driver

Claggy

Raistmer · « **Reply #7 on:** 23 Jun 2010, 08:03:29 am »

@#$%^& this M$ OS positioning!
We use Win2003 x64 server here as OS for quantum chemistry calculations, host accessed mostly remotely by few peoples so terminal server needed, not for "personal use". Moreover, soon we will need GPU power for non-SETI related stuff too (molecular dynamics). And what? No ATI GPU support?! Just have no words....
[Interesting, what about Windows Server 2008? Same rules? Maybe it's time to make upgrade?... ]
Thanks for info, btw... $:-\$

Jason G · « **Reply #8 on:** 23 Jun 2010, 10:40:14 am »

IIRC the 'rules' were something like the drivers are all supposed to be signed ones from Microsoft site. Having said that, if you disable the requirement for driver signing, then normal XP drivers should work ... Though I guess video might be a special case, worth a try. [Before you ask I don't remember how to turn off the driver/signing requirement in 2003 (too long ago), or whether it can be done for Video drivers, or whether the ATi drivers are some special case for some other reason entirely. ]

Raistmer · « **Reply #9 on:** 23 Jun 2010, 02:18:54 pm »

Some makes me think it's just a lame excuse from ATI actually. I remember times where such statements were made from Nvidia. Then they take enough of bravery to pass required certification and what we have now? Video drivers from NV site, not from M$ one, works just fine on Server 2003.
ATI as usually trudges in a tail of software achievements $:-\$

Claggy · « **Reply #10 on:** 27 Jun 2010, 10:08:58 am »

Found an Anonymous host on Seti Beta with mixed Nvidia / ATI cards, he's managed to get Boinc to work in this config, (with recent drivers)
but he errors out all his Stock ATI Hybrid Astropulse work, and optimised ATI Astropulse work too, (same result as i got when running offline runs)

hostid=46515

Claggy

Ghost0210 · « **Reply #11 on:** 27 Jun 2010, 11:39:11 am »

Quote from: Claggy on 27 Jun 2010, 10:08:58 am

Found an Anonymous host on Seti Beta with mixed Nvidia / ATI cards, he's managed to get Boinc to work in this config, (with recent drivers)
but he errors out all his Stock ATI Hybrid Astropulse work, and optimised ATI Astropulse work too, (same result as i got when running offline runs)

hostid=46515

Claggy

Hi Claggy, Raistmer,

Thats my host I'm running the 10-4 cat drivers and the 257.21 nV drivers
I've unhidden my host on Beta, but all ATI ap tasks did error. Stopped testing that app due to every single task erroring (including stock)
Figured that it was down to having both nV and Cat drivers on the rig

corsair · « **Reply #12 on:** 27 Jun 2010, 12:32:48 pm »

New computer with windows 7 pro x64, two hours running in MOBO ATI HD 4250,
by a problem of DVI socket (not compatible with the KVM wire I have, some holes
missing from the connection that the wire has), I've to exchange my KVM from DVI
to VGA (I had the previous one with VGA connection), ok, no problem, 4250 only
single precision painful slow with Collatz, no capability for Milkyway.

next step, I'd had in warehouse one brand new NVidia GT9800, inserted in slot and
started up OS:

CCC saying me that there is no hardware compatible with it ?? (where is the HD 4250)
downloaded last bundle for NVidia GT9800 for windows 7 x64
setup and running NVidia GPU and un-installed ATI drivers and software
No problem crunching with NVidia (Seti and Collatz only)
checked in BIOS and activated the ATI GPU in the MOBO.
started and checked in the hardware configuration that HD4250 is visible, Ok.
installed last software bundle for ATI HD4250 for windows 7 x64
reboot, nothing works.
uninstalled all ATI bundle and with driver sweeper too
deactivated MOBO GPU (ATI HD4250) in BIOS
reinstalled NVidia driver
, BOINC doesn't start, reinstalled BOINC, it doesn't start.
uninstalled NVidia driver and in the same moment BOINC start crunching.
no way of running BOINC with NVidia GPU (no restore point as computer brand new and no registry of setups)
removed NVidia card and drivers and with driver sweeper too.
activated again MOBO GPU in BIOS.
installed again ATI GPU software & driver.
BOINC started normally and crunching with single precision only (Collatz and I hope that Seti@home_Beta)

what happens for not being able to setup again the NVidia GPU card that was working first??

I'll leave then all for the next weekend as I'm going for leaves in this week with family to Ibiza,
I'll need some fresh air to know what happens with it.

P.D. - BTW:
Nvidia 257.21 windows 7 x64
ATI 10.6 windows 7 x64

Claggy · « **Reply #13 on:** 27 Jun 2010, 01:01:48 pm »

The last Catalyst driver that i have been able to run (with 9800GTX+ fitted) is Cat 10.2,
anything newer and i have to physically remove the 9800GTX+ to get Brook+ or OpenCL apps to run correctly,
(that is all Brook+ or OpenCL offline runs fail) Boinc client also crashes on start, even GPU-Z crashes,
i think i could get GPU-Z to work by uninstalling the SDK2.1, (but that removed the OpenCL support for my 9800GTX+ too)

the problem with running Cat 10.2 is it limits me to just running the Brook+ Hybrid builds,
as Cat 10.4 & SDK2.1 is required for the OpenCL builds.

Claggy

corsair · « **Reply #14 on:** 27 Jun 2010, 02:39:02 pm »

Quote from: Claggy on 27 Jun 2010, 01:01:48 pm

Boinc client also crashes on start, even GPU-Z crashes,

Claggy

the same happens to me too, BOINC try to start but can not as per some error is stderr....
GPU-Z started but some seconds after running crashes.

after holydays, I'll try in the other of my desktops exchanging the HD3870 to the new
one and doing a fresh clean install of windows 7 pro x64 in the old one with the Nvidia
GPU since the beggining.