Bug 879776

Summary:	GPU not detected until boinc service is restarted
Product:	[Fedora] Fedora	Reporter:	Germano Massullo <germano.massullo>
Component:	boinc-client	Assignee:	Milos Jakubicek <xjakub>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	18	CC:	cheekyboinc, floydbarber, g.laurent, mattia.verga, mmahut, xjakub
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	boinc-client-7.2.33-2.git1994cc8.fc19	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	719878	Environment:
Last Closed:	2013-12-27 05:58:47 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1039258
Bug Blocks:

Description Germano Massullo 2012-11-24 09:41:01 UTC

The problem is still here on Fedora 17


+++ This bug was initially created as a clone of Bug #719878 +++

I have a nVidia Geforce GTX 260 with 275.09.07 drivers.
When I start the computer, BOINC tolds me that there is not a GPU for GPU computing.
If I restart the BOINC service, BOINC reconnize correcyl the GPU and does all the calculus.
I think this problem is caused by the fact that BOINC server is loaded before nVidia drivers during boot sequence. Is it possible?

--- Additional comment from Milos Jakubicek on 2011-08-20 08:22:28 EDT ---

By GPU computing you mean that you manually installed the CUDA library?

--- Additional comment from Germano Massullo on 2011-08-20 09:31:56 EDT ---

I installed akmod-nvidia from rpm fusion months ago when I setted up the computer

--- Additional comment from Milos Jakubicek on 2011-08-20 12:29:51 EDT ---

Interesting, looks like this is now enough to enable GPU computing. Unfortunately I have no access to a machine where I could test this (no Nvidia/ATI). In another forum I've found some suspect that X server must be already running in order to recognize the GPU, that's sort of a problem: we do not want to start boinc after X server (for CPU computing it does not make sense, it should be enough that you power on the machine). So probably the best solution would be to REstart boinc when the X starts, it is certainly not optimal but I cannot come up with anything better than that. I'll try to get to a machine where I could test this.

--- Additional comment from Germano Massullo on 2011-08-23 06:37:54 EDT ---

I suggest you to talk with other BOINC developers, they may have the same our problem on other distros.

--- Additional comment from GuL on 2011-12-23 05:14:36 EST ---

(In reply to comment #3)
> In another forum I've found some suspect that X server must be
> already running in order to recognize the GPU

I confirm. And it is not possible using sysV or rc.local as in F16 X server is started by systemd and explicity waiting for rc.local to finish (/lib/systemd/system/prefdm.service), even if we add a sleep 30 line inside rc.local.

That's the reason why I am trying to launch boinc using systemd. See https://bugzilla.redhat.com/show_bug.cgi?id=754600

> that's sort of a problem: we do
> not want to start boinc after X server (for CPU computing it does not make
> sense, it should be enough that you power on the machine).

I can understand that on a machine without X. But if you've got X and the default runlevel is graphical, what is the problem ? What I can suggest is to have two different policies, one in the package boinc-client for the cpu only and one in the package boinc-manager for the cpu+gpu.

> So probably the best
> solution would be to REstart boinc when the X starts, it is certainly not
> optimal but I cannot come up with anything better than that. I'll try to get to
> a machine where I could test this.

If I can test something, tell me

--- Additional comment from Milos Jakubicek on 2012-02-08 09:23:38 EST ---

Hopefully this should be fixed with the upcoming switch to systemd that I just built for F17/F18, please reopen otherwise.

Comment 1 Milos Jakubicek 2013-05-01 11:04:49 UTC

Would you please retry on F18 (which now uses systemd)?

Comment 2 Germano Massullo 2013-05-01 16:05:50 UTC

the problem persists on fedora 18

Comment 3 GuL 2013-05-01 16:53:25 UTC

Hello,
unfortunately, I haven't installed fedora 18 and I can't test it.
Cheers

Comment 4 Germano Massullo 2013-06-02 08:19:05 UTC

On Fedora 18 it seems to be fixed

Comment 5 Lorenzo Mastrogiacomi 2013-06-02 20:21:30 UTC

Germano, can you tell me what is changed from one mounth ago, when you wrote "the problem persists on fedora 18"?

I have an AMD card and nothing is changed for me. Still need to restart boinc client.
I have also changed systemd dependencies with something like:
After=display-manager.service
WantedBy=graphical.target

but all seems useless unless i add a long sleep time and make the login immediately

Thanks

Comment 6 Germano Massullo 2013-06-02 21:46:58 UTC

I did not change anything, I simply maintain my Fedora updated
Today I found out that BOINC was operating with GPU even if I did not restarted BOINC service, so the cause should be one of updates I installed.
You should ask admins for bugreport re-opening

Comment 7 Germano Massullo 2013-06-03 13:02:12 UTC

I demand admins to reopen this bugreport, because the ""fix"" worked only once

Comment 8 Germano Massullo 2013-07-10 08:13:30 UTC

On nVidia cards, the problem seems to be fixed in Fedora 19.
Can you confirm on AMD/ATI cards?

Comment 9 Lorenzo Mastrogiacomi 2013-07-17 14:08:34 UTC

Still present in Fedora 19 with AMD card

Comment 10 Germano Massullo 2013-11-09 08:23:17 UTC

I want to provide a little info, I don't know if it can be useful or not.
On F19, days ago I experienced the bug
https://bugzilla.redhat.com/show_bug.cgi?id=967521
and one of the other problems it gave to my computer, was that BOINC did not reconnize the GPU, until I do the well-known boinc service restart. The moment the bug has been fixed, the problem disappereaded again.

Comment 11 Mattia Verga 2013-12-19 18:42:34 UTC

*** Bug 926961 has been marked as a duplicate of this bug. ***

Comment 12 Fedora Update System 2013-12-19 18:58:59 UTC

boinc-client-7.2.33-2.git1994cc8.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/boinc-client-7.2.33-2.git1994cc8.fc19

Comment 13 Fedora Update System 2013-12-19 18:59:36 UTC

boinc-client-7.2.33-2.git1994cc8.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/boinc-client-7.2.33-2.git1994cc8.fc20

Comment 14 Fedora Update System 2013-12-21 02:21:42 UTC

Package boinc-client-7.2.33-2.git1994cc8.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing boinc-client-7.2.33-2.git1994cc8.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-23720/boinc-client-7.2.33-2.git1994cc8.fc19
then log in and leave karma (feedback).

Comment 15 Fedora End Of Life 2013-12-21 15:42:29 UTC

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 16 Fedora Update System 2013-12-27 05:58:47 UTC

boinc-client-7.2.33-2.git1994cc8.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 17 Fedora Update System 2013-12-27 05:59:49 UTC

boinc-client-7.2.33-2.git1994cc8.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.