SETI@home v8.22 Windows GPU applications support thread

Message boards : Number crunching : SETI@home v8.22 Windows GPU applications support thread
Message board moderation

To post messages, you must log in.

Previous · 1 . . . 19 · 20 · 21 · 22

AuthorMessage
Profile Mike Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 17 Feb 01
Posts: 31865
Credit: 75,336,373
RAC: 25,308
Germany
Message 2010819 - Posted: 5 Sep 2019, 22:20:04 UTC - in response to Message 2010815.  

Thanks for the replies. , too bad about nobs. whats it do anyways? A few things to mention. I would still love it if someone would cough up a list of cmd line switches. I have seen references and hints on this very forum as well as a few other boinc related forums about the existence of undocumented switches but so far I havent been able to get anyone to divulge what they know. I guess its like a secret sauce....

ok so on my system the GPU #0 is integral with the cpu. What is called an "apu" system. GPU #0 is physically on the same chip as the 4 core CPU and so it gets first dibs on everything, bandwidth included. otoh, GPU #1 is on a pcie x16 link thats currently stuck at x8 while I work out some issues with the modified bios I made for myself. But even when it was at x16 it barely made a difference according to gpu-z. I guess im stuck for now as I dont want the headache of multipule boincs. Again, Thanks to all who replied.

The command line switches have been documented by the Developer for years. Always been available.
Re: Some considerations regarding OpenCL MultiBeam app tuning from algorithm view


For those GPU`s not very helpful.
It requires a lot of testing to find sweet spot and would not be faster than cmdlines offered in the read me`s.

Example

-sbs 384 -spike_fft_thresh 2048 -tune 1 64 1 4 -oclfft_tune_gr 256 -oclfft_tune_lr 16 -oclfft_tune_wg 256 -oclfft_tune_ls 512 -oclfft_tune_bn 32 -oclfft_tune_cw 32
With each crime and every kindness we birth our future.
ID: 2010819 · Report as offensive     Reply Quote
Kathy Project Donor
Avatar

Send message
Joined: 5 Jan 03
Posts: 338
Credit: 27,750,768
RAC: 2,292
United States
Message 2014124 - Posted: 4 Oct 2019, 4:06:46 UTC

I lost my Nvidia GPU (recognition) after the Windows 10 update. I have tried all the suggestions from Nvidia, updating drivers, etc to no avail. Any suggestions? I have a boatload of GPU wu to crunch.
ID: 2014124 · Report as offensive     Reply Quote
Grant (SSSF)
Volunteer tester

Send message
Joined: 19 Aug 99
Posts: 11654
Credit: 173,791,341
RAC: 118,267
Australia
Message 2014127 - Posted: 4 Oct 2019, 5:17:21 UTC - in response to Message 2014124.  
Last modified: 4 Oct 2019, 5:18:35 UTC

I lost my Nvidia GPU (recognition) after the Windows 10 update. I have tried all the suggestions from Nvidia, updating drivers, etc to no avail. Any suggestions? I have a boatload of GPU wu to crunch.
With your computers hidden, it's hard to offer any useful suggestions, not having any idea of what we're dealing with.
There have been issues with any driver later than 431.60 on some Work Units, so I would suggest downloading driver v 431.60 from Nvidia (not Microsoft or any other 3rd party site), suspend crunching in BOINC, install the driver (selecting the clean install option), re-boot, wait a bit & check that the driver has installed OK (use Nvidia Control Panel) and then exit BOINC (if it starts automatically), then wait a bit, restart it, check in the Event log that your video card(s) has (have) been detected correctly, then unsuspend processing.
If it's working again, excellent. If not, unhide your system(s), and post the first 30 lines or so of the event log from after BOINC has started & we'll see what we can do.
Grant
Darwin NT
ID: 2014127 · Report as offensive     Reply Quote
Kathy Project Donor
Avatar

Send message
Joined: 5 Jan 03
Posts: 338
Credit: 27,750,768
RAC: 2,292
United States
Message 2015678 - Posted: 17 Oct 2019, 3:15:25 UTC - in response to Message 2014127.  

I lost my Nvidia GPU (recognition) after the Windows 10 update. I have tried all the suggestions from Nvidia, updating drivers, etc to no avail. Any suggestions? I have a boatload of GPU wu to crunch.
With your computers hidden, it's hard to offer any useful suggestions, not having any idea of what we're dealing with.
There have been issues with any driver later than 431.60 on some Work Units, so I would suggest downloading driver v 431.60 from Nvidia (not Microsoft or any other 3rd party site), suspend crunching in BOINC, install the driver (selecting the clean install option), re-boot, wait a bit & check that the driver has installed OK (use Nvidia Control Panel) and then exit BOINC (if it starts automatically), then wait a bit, restart it, check in the Event log that your video card(s) has (have) been detected correctly, then unsuspend processing.
If it's working again, excellent. If not, unhide your system(s), and post the first 30 lines or so of the event log from after BOINC has started & we'll see what we can do.



Thanks, Grant! Much appreciated. Still can't get the system to recognize the GPU's even though they are working perfectly fine. Will contact Dell for a reset maybe, it should still be under warranty.
ID: 2015678 · Report as offensive     Reply Quote
Profile Jimbocous Project Donor
Volunteer tester
Avatar

Send message
Joined: 1 Apr 13
Posts: 1444
Credit: 169,373,314
RAC: 318,002
United States
Message 2015698 - Posted: 17 Oct 2019, 8:02:46 UTC - in response to Message 2014124.  

I lost my Nvidia GPU (recognition) after the Windows 10 update. I have tried all the suggestions from Nvidia, updating drivers, etc to no avail. Any suggestions? I have a boatload of GPU wu to crunch.

Does the BOINC Manager Tools>Event log show them on start-up? Should be in the first 10 lines or so right after start-up.
ID: 2015698 · Report as offensive     Reply Quote
rob smith Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer moderator
Volunteer tester

Send message
Joined: 7 Mar 03
Posts: 17794
Credit: 406,976,138
RAC: 158,678
United Kingdom
Message 2015712 - Posted: 17 Oct 2019, 11:42:51 UTC

The clue to your problem may be that this started just after a Windows update. Windows updates are notorious for updating drivers with ones that are lacking everything needed to do computation. While the GPU(s) will continue to display properly they cannot do work for SETI as BOINC won't detect them as being there. The solution is do get a fresh set of drivers from the nvidia website - don't go for the latest as they appear to have an issue, but for the 430.x family, do a "clean" installation (option is in the "advanced" or "custom" menu), and make sure you turn off Windows Driver up dates.
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?
ID: 2015712 · Report as offensive     Reply Quote
Profile Bernie Vine
Volunteer moderator
Volunteer tester
Avatar

Send message
Joined: 26 May 99
Posts: 9862
Credit: 84,745,726
RAC: 53,245
United Kingdom
Message 2015758 - Posted: 17 Oct 2019, 17:41:49 UTC

Well recently my 2 Windows 10 PC's and my laptop all updated to Windows 1903.

And surprise, all of them had the correct driver still in place afterwards, with Open CL, detected correctly by Boinc, pity I don't crunch on GPU anymore ;-)
ID: 2015758 · Report as offensive     Reply Quote
Previous · 1 . . . 19 · 20 · 21 · 22

Message boards : Number crunching : SETI@home v8.22 Windows GPU applications support thread


 
©2019 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.