SOLVED - GPUs missing starting boinc with command line; GPUs present when boinc started with BOINC manager


Advanced search

Questions and Answers : GPU applications : SOLVED - GPUs missing starting boinc with command line; GPUs present when boinc started with BOINC manager
Message board moderation

To post messages, you must log in.

AuthorMessage
bwm

Send message
Joined: 19 Jun 03
Posts: 14
Credit: 35,547,575
RAC: 118
United States
Message 1880420 - Posted: 26 Jul 2017, 16:20:00 UTC

When I start BOINC via the BOINC Manager, GPUs are recognized and all is well. When I start BOINC from a command line in "c:\program files\boinc" with either the command "boinc", or "boinc --detach_console", BOINC runs, but in the BOINC manager indicates the GPUs as "missing". Running under the same local user account in both situations.

When BOINC is started via the BOINC Manager:

    7/26/2017 12:04:40 PM | | cc_config.xml not found - using defaults
    7/26/2017 12:04:40 PM | | Starting BOINC client version 7.6.33 for windows_x86_64
    7/26/2017 12:04:40 PM | | log flags: file_xfer, sched_ops, task
    7/26/2017 12:04:40 PM | | Libraries: libcurl/7.47.1 OpenSSL/1.0.2g zlib/1.2.8
    7/26/2017 12:04:40 PM | | Data directory: C:\ProgramData\BOINC
    7/26/2017 12:04:40 PM | | Running under account user1
    7/26/2017 12:04:41 PM | | CUDA: NVIDIA GPU 0: Quadro M2200 (driver version 382.16, CUDA version 8.0, compute capability 5.2, 4096MB, 3416MB available, 2122 GFLOPS peak)
    7/26/2017 12:04:41 PM | | OpenCL: NVIDIA GPU 0: Quadro M2200 (driver version 382.16, device version OpenCL 1.2 CUDA, 4096MB, 3416MB available, 2122 GFLOPS peak)
    7/26/2017 12:04:41 PM | | OpenCL: Intel GPU 0: Intel(R) HD Graphics P630 (driver version 21.20.16.4664, device version OpenCL 2.1, 6485MB, 6485MB available, 211 GFLOPS peak)
    7/26/2017 12:04:41 PM | | OpenCL: Intel GPU 1: Intel(R) HD Graphics P630 (driver version 21.20.16.4664, device version OpenCL 2.1, 6485MB, 6485MB available, 211 GFLOPS peak)
    7/26/2017 12:04:41 PM | | OpenCL CPU: Intel(R) Xeon(R) CPU E3-1505M v6 @ 3.00GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 6.8.0.2, device version OpenCL 2.1 (Build 2))
    7/26/2017 12:04:41 PM | | OpenCL CPU: Intel(R) Xeon(R) CPU E3-1505M v6 @ 3.00GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 6.8.0.2, device version OpenCL 2.1 (Build 2))
    7/26/2017 12:04:41 PM | | Host name: redacted
    7/26/2017 12:04:41 PM | | Processor: 8 GenuineIntel Intel(R) Xeon(R) CPU E3-1505M v6 @ 3.00GHz [Family 6 Model 158 Stepping 9]
    7/26/2017 12:04:41 PM | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 fma cx16 sse4_1 sse4_2 movebe popcnt aes f16c rdrandsyscall nx lm avx avx2 vmx smx tm2 pbe fsgsbase bmi1 hle smep bmi2
    7/26/2017 12:04:41 PM | | OS: Microsoft Windows 10: Professional x64 Edition, (10.00.15063.00)
    7/26/2017 12:04:41 PM | | Memory: 15.85 GB physical, 18.23 GB virtual
    7/26/2017 12:04:41 PM | | Disk: 236.60 GB total, 137.47 GB free
    7/26/2017 12:04:41 PM | | Local time is UTC -4 hours
    7/26/2017 12:04:41 PM | SETI@home | URL http://setiathome.berkeley.edu/; Computer ID redacted; resource share 100
    7/26/2017 12:04:41 PM | SETI@home | General prefs: from SETI@home (last modified 11-Apr-2012 09:15:03)
    7/26/2017 12:04:41 PM | SETI@home | Host location: none
    7/26/2017 12:04:41 PM | SETI@home | General prefs: using your defaults
    7/26/2017 12:04:41 PM | | Reading preferences override file
    7/26/2017 12:04:41 PM | | Preferences:
    7/26/2017 12:04:41 PM | | max memory usage when active: 8116.73MB
    7/26/2017 12:04:41 PM | | max memory usage when idle: 14610.11MB
    7/26/2017 12:04:41 PM | | max disk usage: 137.56GB
    7/26/2017 12:04:41 PM | | don't use GPU while active
    7/26/2017 12:04:41 PM | | suspend work if non-BOINC CPU load exceeds 50%
    7/26/2017 12:04:41 PM | | (to change preferences, visit a project web site or select Preferences in the Manager)
    7/26/2017 12:04:41 PM | | Suspending GPU computation - computer is in use



log file lines starting via boinc --detach_console:

    7/26/2017 11:43:32 AM | | cc_config.xml not found - using defaults
    7/26/2017 11:43:32 AM | | Starting BOINC client version 7.6.33 for windows_x86_64
    7/26/2017 11:43:32 AM | | log flags: file_xfer, sched_ops, task
    7/26/2017 11:43:32 AM | | Libraries: libcurl/7.47.1 OpenSSL/1.0.2g zlib/1.2.8
    7/26/2017 11:43:32 AM | | Data directory: C:\ProgramData\BOINC
    7/26/2017 11:43:32 AM | | Running under account user1
    7/26/2017 11:43:32 AM | | No usable GPUs found
    7/26/2017 11:43:32 AM | | app version refers to missing GPU type intel_gpu
    7/26/2017 11:43:32 AM | SETI@home | Application uses missing intel_gpu GPU
    7/26/2017 11:43:32 AM | | app version refers to missing GPU type NVIDIA
    7/26/2017 11:43:32 AM | SETI@home | Application uses missing NVIDIA GPU
    7/26/2017 11:43:32 AM | | app version refers to missing GPU type NVIDIA
    7/26/2017 11:43:32 AM | SETI@home | Application uses missing NVIDIA GPU
    7/26/2017 11:43:32 AM | | app version refers to missing GPU type NVIDIA
    7/26/2017 11:43:32 AM | SETI@home | Application uses missing NVIDIA GPU
    7/26/2017 11:43:32 AM | | app version refers to missing GPU type NVIDIA
    7/26/2017 11:43:32 AM | SETI@home | Application uses missing NVIDIA GPU
    7/26/2017 11:43:32 AM | | app version refers to missing GPU type intel_gpu

    Followed by a long list of things like:

    7/26/2017 11:43:32 AM | SETI@home | Missing coprocessor for task blc05_2bit_guppi_57835_08850_HIP39595_0033.16602.818.23.46.93.vlar_1
    7/26/2017 11:43:32 AM | SETI@home | Missing coprocessor for task 09mr17aa.733.192338.12.39.239_0

    Eventually followed by:

    7/26/2017 11:43:32 AM | | Host name: redacted
    7/26/2017 11:43:32 AM | | Processor: 8 GenuineIntel Intel(R) Xeon(R) CPU E3-1505M v6 @ 3.00GHz [Family 6 Model 158 Stepping 9]
    7/26/2017 11:43:32 AM | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 fma cx16 sse4_1 sse4_2 movebe popcnt aes f16c rdrandsyscall nx lm avx avx2 vmx smx tm2 pbe fsgsbase bmi1 hle smep bmi2
    7/26/2017 11:43:32 AM | | OS: Microsoft Windows 10: Professional x64 Edition, (10.00.15063.00)
    7/26/2017 11:43:32 AM | | Memory: 15.85 GB physical, 18.23 GB virtual
    7/26/2017 11:43:32 AM | | Disk: 236.60 GB total, 137.48 GB free
    7/26/2017 11:43:32 AM | | Local time is UTC -4 hours
    7/26/2017 11:43:33 AM | SETI@home | URL http://setiathome.berkeley.edu/; Computer ID redacted; resource share 100
    7/26/2017 11:43:33 AM | SETI@home | General prefs: from SETI@home (last modified 11-Apr-2012 09:15:03)
    7/26/2017 11:43:33 AM | SETI@home | Host location: none
    7/26/2017 11:43:33 AM | SETI@home | General prefs: using your defaults
    7/26/2017 11:43:33 AM | | Reading preferences override file
    7/26/2017 11:43:33 AM | | Preferences:
    7/26/2017 11:43:33 AM | | max memory usage when active: 8116.73MB
    7/26/2017 11:43:33 AM | | max memory usage when idle: 14610.11MB
    7/26/2017 11:43:33 AM | | max disk usage: 137.58GB
    7/26/2017 11:43:33 AM | | don't use GPU while active
    7/26/2017 11:43:33 AM | | suspend work if non-BOINC CPU load exceeds 50%
    7/26/2017 11:43:33 AM | | (to change preferences, visit a project web site or select Preferences in the Manager)
    7/26/2017 11:43:33 AM | SETI@home | Sending scheduler request: To fetch work.



Reasons for my wanting to run from command line aside, are there any suggestions as to how to get the GPUs recognized when starting boinc from the command line?

Thx much.

ID: 1880420 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15184
Credit: 4,362,181
RAC: 3
Netherlands
Message 1880548 - Posted: 27 Jul 2017, 7:55:14 UTC - in response to Message 1880420.  

Start the command from the commandline as boinc.exe --detach_console, then it'll work.
ID: 1880548 · Report as offensive
bwm

Send message
Joined: 19 Jun 03
Posts: 14
Credit: 35,547,575
RAC: 118
United States
Message 1880574 - Posted: 27 Jul 2017, 13:49:21 UTC - in response to Message 1880548.  
Last modified: 27 Jul 2017, 13:58:22 UTC

Start the command from the commandline as boinc.exe --detach_console, then it'll work.

Many thanks. That did the trick. "boinc --detach_console" fails, but "boinc.exe --detach_console" works.

Donating in your honor.
ID: 1880574 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15184
Credit: 4,362,181
RAC: 3
Netherlands
Message 1880589 - Posted: 27 Jul 2017, 15:21:18 UTC - in response to Message 1880574.  
Last modified: 27 Jul 2017, 15:21:54 UTC

I've gone further than that and posted it to the BOINC alpha list. There, between some detailed posts I made and a couple of volunteer developers answering they managed to find what possibly causes this - a missing argument in the BOINC code that states that the boinc executable can just be boinc, not always needs to be boinc.exe - so they're testing that now and that will probably lead to this being fixed in a future version of BOINC.

So thank you for reporting it.
ID: 1880589 · Report as offensive
bwm

Send message
Joined: 19 Jun 03
Posts: 14
Credit: 35,547,575
RAC: 118
United States
Message 1880609 - Posted: 27 Jul 2017, 18:07:17 UTC - in response to Message 1880589.  

A good day. GPUs on the target machine now working, I gave them $75 in honor of "SETI@HOME user Ageless", and maybe even a tweek to the code. Cheers. Now if only I could figure out how to edit the thread title and add "solved".
ID: 1880609 · Report as offensive
Profile Mr. Kevvy Crowdfunding Project Donor*Special Project $250 donor
Volunteer moderator
Volunteer tester
Avatar

Send message
Joined: 15 May 99
Posts: 3776
Credit: 1,114,826,392
RAC: 3,319
Canada
Message 1880613 - Posted: 27 Jul 2017, 18:43:55 UTC - in response to Message 1880609.  

Done. :^)
ID: 1880613 · Report as offensive
Profile BilBg
Volunteer tester
Avatar

Send message
Joined: 27 May 07
Posts: 3720
Credit: 9,385,827
RAC: 0
Bulgaria
Message 1881375 - Posted: 31 Jul 2017, 19:22:45 UTC

That was discussed earlier in:
"BOINC portable" for Windows hosts
https://setiathome.berkeley.edu/forum_thread.php?id=81632

The same answer:
https://setiathome.berkeley.edu/forum_thread.php?id=81632&postid=1876642#1876642

My normal BOINC startup .bat file:
pushd %~dp0
boinc.exe --detach
Result: GPUs detected, data folder the same as boinc.exe

A BOINC startup .bat w/o specifying extension for boinc.exe
pushd %~dp0
boinc --detach
Result: No GPUs detected, data folder the same as boinc.exe


(Anyone interested can read the entire thread for more info.
Two important posts by Juha:
https://setiathome.berkeley.edu/forum_thread.php?id=81632&postid=1875986#1875986
https://setiathome.berkeley.edu/forum_thread.php?id=81632&postid=1876279#1876279
)
 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 
ID: 1881375 · Report as offensive

Questions and Answers : GPU applications : SOLVED - GPUs missing starting boinc with command line; GPUs present when boinc started with BOINC manager


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