Advanced search

Message boards : Graphics cards (GPUs) : 190.32 and x64 linux

Author Message
pwolfe
Send message
Joined: 24 Mar 09
Posts: 54
Credit: 16,186,927
RAC: 0
Level
Pro
Scientific publications
watwatwatwatwatwat
Message 12732 - Posted: 25 Sep 2009 | 3:50:23 UTC

Hello I am using the 190.32 drivers on a 295gtx in on ubuntu 9.04 x64 with boinc x.36. Whenever I load boinc, I get the no cuda devices found stuff. But I have read threads where other have this working. Are there some settings im missing or something?

RalphEllis
Send message
Joined: 11 Dec 08
Posts: 43
Credit: 2,216,617
RAC: 0
Level
Ala
Scientific publications
watwatwatwatwat
Message 12754 - Posted: 26 Sep 2009 | 2:08:14 UTC - in response to Message 12732.

Are the binary drivers for Ubuntu from an earlier Nvidia version such as 180 or 185 installed at the same time as the 190 drivers installed from the Nvidia website?
If you had the other drivers installed before, you may need to remove them and reboot.

CTAPbIi
Send message
Joined: 29 Aug 09
Posts: 175
Credit: 259,509,919
RAC: 0
Level
Asn
Scientific publications
watwatwatwatwatwatwatwatwatwat
Message 12765 - Posted: 26 Sep 2009 | 5:52:50 UTC

Running ubuntu 9.04, 190.32 driver and BOINC 6.10.6 on GTX275. works fine.

install driver in this way:
sudo sh NVIDIA....run --no-x-check

when it will ofer to remove previous driver - say yes and then reboot (or restart X). that should works. If not - remove old driver usinf envy (it's in repos).

download and install CUDA 2.3. Here I'm not sure if you need it or not, but "just in case" I've got it.

Skip Da Shu
Send message
Joined: 13 Jul 09
Posts: 38
Credit: 41,955,165
RAC: 0
Level
Val
Scientific publications
watwatwatwatwatwatwat
Message 12852 - Posted: 28 Sep 2009 | 7:49:57 UTC

Does it not find it ONLY on the initial start up and then find it if you do a:

sudo /etc/init.d/boinc-client restart

? Or does the restarted boinc also say no cuda.

IF on a restart it finds them then the problem is with boinc starting before the xorg.conf has been processed thru this can be helped (but not completely resolved in all cases) by starting boinc later in the boot sequence via:

cd /etc/rc2.d
sudo mv -v S20boinc-client S32boinc-client


If you get the same error again on the 'restart' then the prior posts are the right direction.

Did you install the 190.32 drivers over the 180.44 driver from the repository by chance? That's another situation... I screwed that one up pretty good first time around and so did a how-to on it after I'd figured it out and did 3 correctly. I'd have to pull it out into a public forum. Lemme know if that's your scenario and I can move that post and give you a link to it.



____________
- da shu @ HeliOS,
"A child's exposure to technology should never be predicated on an ability to afford it."

pwolfe
Send message
Joined: 24 Mar 09
Posts: 54
Credit: 16,186,927
RAC: 0
Level
Pro
Scientific publications
watwatwatwatwatwat
Message 13233 - Posted: 19 Oct 2009 | 13:31:00 UTC - in response to Message 12852.

I would like to see that thread please

Ingvar
Send message
Joined: 7 Sep 09
Posts: 5
Credit: 2,308,660
RAC: 0
Level
Ala
Scientific publications
watwatwatwatwatwatwat
Message 13570 - Posted: 16 Nov 2009 | 0:45:41 UTC - in response to Message 12852.

cd /etc/rc2.d
sudo mv -v S20boinc-client S32boinc-client


With the above solution, on my system BOINC will usually find the GPU while booting, but not always. I tried adding also a sleep delay within the startup file /etc/init.d/boinc-client. With the above change plus the sleep delay, so far it has always found the GPU.

The delay comes at a cost. Booting takes longer.

In the startup file /etc/init.d/boinc-client, where it says:

case "$1" in
start)
start
;;

I inserted "sleep 5" for a 5-second delay:

case "$1" in
start)
sleep 5
start
;;

I also changed S20boinc-client to S95boinc-client rather than S32boinc-client.

I don't know if my changes are healthy or cause some hidden problems. It seems very unlikely that they'll cause any problems, but still, my knowledge about this is very limited indeed. Use at your own risk.

Rabinovitch
Avatar
Send message
Joined: 25 Aug 08
Posts: 142
Credit: 24,808,559
RAC: 8
Level
Pro
Scientific publications
watwatwatwatwatwatwatwatwat
Message 13598 - Posted: 18 Nov 2009 | 15:34:40 UTC

Just try a new certified 190.42 drivers.
____________
From Siberia with love!

pwolfe
Send message
Joined: 24 Mar 09
Posts: 54
Credit: 16,186,927
RAC: 0
Level
Pro
Scientific publications
watwatwatwatwatwat
Message 13611 - Posted: 19 Nov 2009 | 4:50:47 UTC - in response to Message 13598.

190.42 does not help me

Post to thread

Message boards : Graphics cards (GPUs) : 190.32 and x64 linux