Einstein@Home GPU/APU Application for AMD/ATI Graphics Cards: discussion thread
Language
Copyright © 2024 Einstein@Home. All rights reserved.
Copyright © 2024 Einstein@Home. All rights reserved.
RE: ...upon
)
If the GPUs are installed properly then Boinc should recognize all of them.
After that it decides witch is the most powerful if more than one is installed and limit itself to only use that one.
RE: Hello World! No GPU
)
Since you're running Boinc downloaded from the repositories you'll need to follow the GPU recognition fixes in this thread:
Debian/Ubuntu/Mint/Derivatives - GPU recognition fixes
Edit: While you're at it, I'd upgrade your Boinc to the latest your repository has, probably 7.0.65
Claggy
RE: RE: ...upon
)
The key word there is "should." The bottom line is that BIONC is imperfect and Often times does not detect all GPUs in a machine even if they are installed correctly...hence the possibility that he'll have to use a config file to force BOINC to recognize all GPUs in the event that it doesn't. Also, consider that some folks may choose to install their GPUs in a way that the system may deem incorrect, but they have no choice due to spacing or bandwidth limitations...in that case one would have to use a config file to make BOINC see all the GPUs.
RE: RE: RE: ...upon
)
As Holmis said: there is a difference between 'detecting/recognizing' a GPU and 'using' a GPU.
Playing around with cc_config.xml won't help BOINC detect anything at all: but it might affect BOINC's choices about what to do with the devices it has already detected.
RE: As Holmis said: there
)
but is there a difference?
i've had instances where BOINC did not detect all GPUs in the system, and only the addition of a cc_config.xml file containing a 1 statement fixed it. now if BOINC had detected more than one GPU at start-up in the first place, and then subsequently chosen the most powerful GPU (as Holmis suggested it would), then the BOINC event log on start-up would have shown all GPUs, the less powerful ones being shown as ignored by BOINC. and yet before the addition of a cc_config.xml containing the appropriate statements, my BOINC event log would not show one enabled GPU and multiple disabled GPUs - it would only show a single GPU on start-up. now maybe things aren't supposed to happen this way, but as i said before, BOINC doesn't always function as it should, and it is a constant work in progress as i'm sure you know. so while this may not happen to others, its happened to me on more than one occasion, and i can only speak from experience. hopefully xmal won't have to use a cc_config.xml at all. honestly it looks like he just accidentally installed BOINC as a service, not as a standard app, which means BOINC can't use GPUs to crunch. i'm fairly confident he'll be able to crunch on the GPU just fine once he reinstalls BOINC with the "Protected application execution" box unchecked.
Interesting. I was about to
)
Interesting. I was about to say that the contents of cc_config.xml couldn't possibly affect GPU detection, because detection is complete before cc_config is read:
But then I double-checked an older version of BOINC, and found that the order has changed:
So, maybe it can happen sometimes?
To avoid confusing our questioner: yes, that second log shows an NVIDIA card running as a daemon. Under Windows, that is possible using BOINC v6.12.34 and Windows XP: it can't be done with a later version of either BOINC or Windows. I can't comment for Linux.
RE: 12-Sep-2013 19:06:11
)
GUI RPCs allowed isn't done by cc_config.xml, but by using a remote_hosts.cfg file, and possibly telling boinc.exe --gui_rpc_port N
But there is an entry to
)
But there is an entry to allow unrestricted access:
0|1
If 1, allow GUI RPCs from any remote host (see Controlling BOINC remotely) New in 6.10.46.
(I don't know the generated message in stdoutdae, though ;-)
Gruß
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
Hold on, I am confusing two
)
Hold on, I am confusing two things, I think.
The GUI RPC allowed: line tells which remote IP addresses are allowed through to connect to this client. That's set through the remote_rpc.cfg file. In my case that's:
That's in line with the contents of my remote_hosts.cfg file. Nowhere in my cc_config.xml file do I point to IP address 192.168.1.4
My apologies for an
)
My apologies for an over-hasty post leading you all off in the wrong direction. I'm away from my main crunchers at the moment (the reason for the haste), but that that leaves the originial question open: is there anything, even potentially, in cc_config.xml which could interfere with the detection, as opposed to usage, of any GPUs? I'll try to work out a proper answer when I get back to base.