Help needed please

Questions and Answers : GPU applications : Help needed please
Message board moderation

To post messages, you must log in.

AuthorMessage
Paul Klimczak

Send message
Joined: 1 Jun 04
Posts: 3
Credit: 44,257,146
RAC: 1,176
United Kingdom
Message 1760338 - Posted: 29 Jan 2016, 12:30:34 UTC

I have a laptop with a AMD A10-8700P Quad core processor and Radeon R6 Graphics 6 core GPU. I am running Boinc 7.6.22 on Windows 10 64bit, although I can only get 32 bit Boinc to run.
What do I need to do to get maximum usage out of the CPU & GPU.
I see old messages about cc_config.xml and app_config.xml but I'm not sure if they still apply or where they go, different people seem to put them in different places

Thank you
ID: 1760338 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15183
Credit: 4,362,181
RAC: 3
Netherlands
Message 1760357 - Posted: 29 Jan 2016, 14:13:16 UTC - in response to Message 1760338.  

I am running Boinc 7.6.22 on Windows 10 64bit, although I can only get 32 bit Boinc to run.

32bit BOINC can run 64bit science applications. So that's not really a problem, unless you really want to run a 64bit BOINC. Try https://boinc.berkeley.edu/dl/boinc_7.6.22_windows_x86_64.exe, but do know that for it to be able to install on your Windows you have to change the path to the Programs Install directory from the default C:/Program Files (x86)\BOINC\ to C:\Program Files\BOINC\

You can do this on the third screen in the installer, click Advanced, then change the path for the Programs directory only.
This is a Windows secure measure, that it doesn't allow 64bit programs to be installed in the 32bit programs directory C:\Program Files (x86)\

The BOINC installer isn't that intelligent, it reads the registry to check if there is a path to the previous version of BOINC available and reuses that. But since the installer only unpacks files in a sort of database within itself, it does not know if the contents it unpacks are 32bit or 64bit. Therefore you will have to change the path to the correct directory yourself.

As for the rest of your question, I'll leave that to someone else to answer, as the way I run Seti on my hardware differs greatly from how you want to run it on yours and I don't feel I can give you advice on that.
ID: 1760357 · Report as offensive
Paul Klimczak

Send message
Joined: 1 Jun 04
Posts: 3
Credit: 44,257,146
RAC: 1,176
United Kingdom
Message 1760369 - Posted: 29 Jan 2016, 14:37:56 UTC - in response to Message 1760357.  

Thank you for your comments Jord. I can get 64bit boinc to install, it just will not connect to "localhost" for some reason 32 bit boinc has no problem connecting.

Cheers
ID: 1760369 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15183
Credit: 4,362,181
RAC: 3
Netherlands
Message 1760382 - Posted: 29 Jan 2016, 15:16:29 UTC - in response to Message 1760369.  

Problems with not connecting to localhost are normally attributed to BOINC not being able to communicate amongst its parts. the client (boinc.exe) and manager/GUI (boincmgr.exe) need access through the firewall on the localhost, if specified on TCP port 31416.

When just using the Windows firewall, do know that it has to have entries for a 64bit BOINC separate from a 32bit BOINC. Again due to the path that the executables are in. C:\program files\BOINC\boinc.exe differs in path from C:\program files (x86)\BOINC\boinc.exe

Windows firewall does not check the paths, as far as I know. It only checks if programs of a certain name are allowed to pass.

So if an earlier installation only allowed C:\program files (x86)\BOINC\boinc.exe and C:\program files (x86)\BOINC\boincmgr.exe through the firewall under the names boinc.exe and boincmgr.exe, a next start of C:\program files\boinc.exe and C:\program files\boincmgr.exe will result in neither being able to communicate with each other, because these aren't allowed through the Windows firewall.

Manually adding a new BOINC and BOINCMGR with the correct paths is necessary here.

Start->type Windows firewall in Search, hit Enter.
Click Inbound Rules.
Click New Rule.
Program->Next.
This program path->path to 64bit boinc.exe->Next.
Allow the connection->Next.
Check Public and Private->Next.
Name: what you want, e.g. BOINC.exe
Finish.

Do the same for boincmgr.exe, but here check the Private rule only. BOINC Manager only needs access to the localhost, private network. It does not need internet an connection.

When done, no need to reboot, you should be able to start BOINC Manager now and have it connect to the client.
If that still doesn't work, exit BOINC completely, navigate to its data directory (default a hidden directory at C:\Programdata\BOINC\, when you fill in the path in Windows Explorer and hit Enter you'll get there) and delete the gui_rpc_auth.cfg file.
Then restart BOINC Manager and try again.
ID: 1760382 · Report as offensive
Paul Klimczak

Send message
Joined: 1 Jun 04
Posts: 3
Credit: 44,257,146
RAC: 1,176
United Kingdom
Message 1761683 - Posted: 2 Feb 2016, 16:20:48 UTC - in response to Message 1760382.  

Thanks for your help again...........I'm now running 64bit Boinc with no problems

Cheers
ID: 1761683 · Report as offensive

Questions and Answers : GPU applications : Help needed please


 
©2022 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.