Message boards :
Number crunching :
I've almost been talked into purchasing a Threadripper 2950X CPU... Pro's & Con's?
Message board moderation
Previous · 1 · 2 · 3 · 4 · 5 · 6 · Next
Author | Message |
---|---|
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 |
Okay, I've received everything but my CPU for my new rig and haven't put it together yet. I also received my SSD for my old rig, installed it and loaded Linux Cinnamon on it. I then tried to download the graphics card driver for my RTX 2060 GPU, twice, and both times after a slow download it shows me a screen which says (I'm paraphrasing) that a few characters are indecipherable and can't be read. I also tried twice to download BOINC Manager but I received the same reading.Once you have Mint loaded you go to the Driver Manager and select the Nvidia driver over the Nouveau driver and once that is done you will then need to open a Terminal and type, Hopefully he will get the OpenCL component installed with the new drivers automatically. I have received them lately with no issues on the last few release versions. If not, then use your provided Terminal installation. One way of checking to be sure you always have all of the drivers installed, both CUDA and OpenCL, is to do a sanity check with clinfo. That quickly tests for and reports what driver components are installed. sudo apt install clinfo Every time I reboot the computer after some software installation, one of the first things I do is open Terminal and enter clinfo just to be sure all my drivers are loaded in the kernel. No surprises with BOINC that way. Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
George Send message Joined: 23 Oct 17 Posts: 222 Credit: 2,597,521 RAC: 13 |
Where and which BOINC Manager are you trying to install. I would recommend using TBar's All-in-One installer to install BOINC along with the optimized applications. Well, I've tried all of your tips but I'm a bit confused still. After using "Terminal" for <http://www.arkayn.us/lunatics/BOINC.7z> I couldn't find the "Software&Updates" application to open the Additional Drivers tab. I did find "Software Manager" and "Software Sources", when I opened the sources folder I went to the PPAs tab on the left and chose "graphics-drivers" on the right. I then chose "libnvidia-fbc1-435 435.21-0ubuntu0~18.04.2" and I got this: "Package dependencies cannot be resolved This error could be caused by required additional software packages which are missing or not installable. Furthermore there could be a conflict between software packages which are not allowed to be installed at the same time." I currently have the version 430.26-0buntu0. 18.04.2 installed. When I ran <clinfo> I got this: george@GWG-PC-Linux:~$ sudo apt install clinfo [sudo] password for george: Reading package lists... Done Building dependency tree Reading state information... Done clinfo is already the newest version (2.2.18.03.26-1). 0 upgraded, 0 newly installed, 0 to remove and 25 not upgraded. george@GWG-PC-Linux:~$ clinfo Number of platforms 1 Platform Name NVIDIA CUDA Platform Vendor NVIDIA Corporation Platform Version OpenCL 1.2 CUDA 10.2.120 Platform Profile FULL_PROFILE Platform Extensions cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_copy_opts cl_nv_create_buffer Platform Extensions function suffix NV Platform Name NVIDIA CUDA Number of devices 1 Device Name GeForce RTX 2060 Device Vendor NVIDIA Corporation Device Vendor ID 0x10de Device Version OpenCL 1.2 CUDA Driver Version 430.26 Device OpenCL C Version OpenCL C 1.2 Device Type GPU Device Topology (NV) PCI-E, 03:00.0 Device Profile FULL_PROFILE Device Available Yes Compiler Available Yes Linker Available Yes Max compute units 30 Max clock frequency 1680MHz Compute Capability (NV) 7.5 Device Partition (core) Max number of sub-devices 1 Supported partition types None Max work item dimensions 3 Max work item sizes 1024x1024x64 Max work group size 1024 Preferred work group size multiple 32 Warp size (NV) 32 Preferred / native vector sizes char 1 / 1 short 1 / 1 int 1 / 1 long 1 / 1 half 0 / 0 (n/a) float 1 / 1 double 1 / 1 (cl_khr_fp64) Half-precision Floating-point support (n/a) Single-precision Floating-point support (core) Denormals Yes Infinity and NANs Yes Round to nearest Yes Round to zero Yes Round to infinity Yes IEEE754-2008 fused multiply-add Yes Support is emulated in software No Correctly-rounded divide and sqrt operations Yes Double-precision Floating-point support (cl_khr_fp64) Denormals Yes Infinity and NANs Yes Round to nearest Yes Round to zero Yes Round to infinity Yes IEEE754-2008 fused multiply-add Yes Support is emulated in software No Address bits 64, Little-Endian Global memory size 6221463552 (5.794GiB) Error Correction support No Max memory allocation 1555365888 (1.449GiB) Unified memory for Host and Device No Integrated memory (NV) No Minimum alignment for any data type 128 bytes Alignment of base address 4096 bits (512 bytes) Global Memory cache type Read/Write Global Memory cache size 491520 (480KiB) Global Memory cache line size 128 bytes Image support Yes Max number of samplers per kernel 32 Max size for 1D images from buffer 134217728 pixels Max 1D or 2D image array size 2048 images Max 2D image size 32768x32768 pixels Max 3D image size 16384x16384x16384 pixels Max number of read image args 256 Max number of write image args 32 Local memory type Local Local memory size 49152 (48KiB) Registers per block (NV) 65536 Max number of constant args 9 Max constant buffer size 65536 (64KiB) Max size of kernel argument 4352 (4.25KiB) Queue properties Out-of-order execution Yes Profiling Yes Prefer user sync for interop No Profiling timer resolution 1000ns Execution capabilities Run OpenCL kernels Yes Run native kernels No Kernel execution timeout (NV) Yes Concurrent copy and kernel execution (NV) Yes Number of async copy engines 3 printf() buffer size 1048576 (1024KiB) Built-in kernels Device Extensions cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_copy_opts cl_nv_create_buffer NULL platform behavior clGetPlatformInfo(NULL, CL_PLATFORM_NAME, ...) NVIDIA CUDA clGetDeviceIDs(NULL, CL_DEVICE_TYPE_ALL, ...) Success [NV] clCreateContext(NULL, ...) [default] Success [NV] clCreateContextFromType(NULL, CL_DEVICE_TYPE_DEFAULT) No platform clCreateContextFromType(NULL, CL_DEVICE_TYPE_CPU) No devices found in platform clCreateContextFromType(NULL, CL_DEVICE_TYPE_GPU) No platform clCreateContextFromType(NULL, CL_DEVICE_TYPE_ACCELERATOR) No devices found in platform clCreateContextFromType(NULL, CL_DEVICE_TYPE_CUSTOM) Invalid device type for platform clCreateContextFromType(NULL, CL_DEVICE_TYPE_ALL) No platform ICD loader properties ICD loader Name OpenCL ICD Loader ICD loader Vendor OCL Icd free software ICD loader Version 2.2.11 ICD loader Profile OpenCL 2.1 george@GWG-PC-Linux:~$ When I installed BOINC Manager from the "<http://www.arkayn.us/lunatics/BOINC.7z>" link you gave, I then had the BOINC folder in which I moved it to the HOME directory. But I don't know how to get it to run, and if it is running, how do I see what it is doing? George |
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 |
Well you have the 430 drivers installed which are good enough for the 2060. You also have both the CUDA and OpenCL components installed. Did you unpack the archive? If you double click the archive it should automatically unpack itself into a BOINC directory. My understanding is that Mint knows how to handle the 7zip compression protocol already and you don't have to install the p7zip archiver separately. Then read the documents in the projects/setiathome.berkeley.edu folder to understand how to use the AIO. The archive does not install BOINC to run automatically like Windows. You need to double click the boincmgr file in the BOINC directory and that will start the boinc client and the Manager up. The Manager looks the same as it does in Windows. The client will give you the standard dialog to join a project. Then just join Seti normally with your normal account email and password and the client will contact the project and download work for your cpu and gpu. You will be running the CUDA90 special app on your 2060. It will be much faster than the SoG app in Windows. Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
George Send message Joined: 23 Oct 17 Posts: 222 Credit: 2,597,521 RAC: 13 |
Well you have the 430 drivers installed which are good enough for the 2060. You also have both the CUDA and OpenCL components installed. Did you unpack the archive? Yes I did unpack the archive. And yes, Mint does know how to handle the 7zip compression protocol already. I am waiting for SETI to send me some work, currently there is no work units available for Nvidia GPUs, only ATI and Intel GPUs. It's too bad that I can't transfer any work units from another computer. I thank you once again for helping me get up and running... eventually... with my SETI project. I can't wait until I get my new CPU for my new computer, I'm checking AMDs website, Amazon & Newegg twice a day for any news or sign that the 3950X is available. George |
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 |
Well you have the 430 drivers installed which are good enough for the 2060. You also have both the CUDA and OpenCL components installed. Did you unpack the archive? You must have something wrong with your setup. There is plenty of work available. You are getting cpu tasks but for some reason you are not asking for gpu tasks. What does the startup of BOINC show in the Event Log? Does the client detect your gpu? Post the first 30 lines of the Event Log after restarting BOINC. Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
George Send message Joined: 23 Oct 17 Posts: 222 Credit: 2,597,521 RAC: 13 |
Wed 11 Sep 2019 02:11:30 AM CDT | | Starting BOINC client version 7.14.2 for x86_64-pc-linux-gnu Wed 11 Sep 2019 02:11:30 AM CDT | | log flags: file_xfer, sched_ops, task, sched_op_debug Wed 11 Sep 2019 02:11:30 AM CDT | | Libraries: libcurl/7.58.0 GnuTLS/3.5.18 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3 Wed 11 Sep 2019 02:11:30 AM CDT | | Data directory: /home/george/BOINC Wed 11 Sep 2019 02:11:30 AM CDT | | CUDA: NVIDIA GPU 0: GeForce RTX 2060 (driver version 430.26, CUDA version 10.2, compute capability 7.5, 4096MB, 3970MB available, 6451 GFLOPS peak) Wed 11 Sep 2019 02:11:30 AM CDT | | OpenCL: NVIDIA GPU 0: GeForce RTX 2060 (driver version 430.26, device version OpenCL 1.2 CUDA, 5933MB, 3970MB available, 6451 GFLOPS peak) Wed 11 Sep 2019 02:11:30 AM CDT | | [libc detection] gathered: 2.27, Ubuntu GLIBC 2.27-3ubuntu1 Wed 11 Sep 2019 02:11:30 AM CDT | | Host name: GWG-PC-Linux Wed 11 Sep 2019 02:11:30 AM CDT | | Processor: 12 GenuineIntel Intel(R) Core(TM) i7 CPU X 990 @ 3.47GHz [Family 6 Model 44 Stepping 2] Wed 11 Sep 2019 02:11:30 AM CDT | | 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 ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt aes lahf_lm pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid dtherm ida arat flush_l1d Wed 11 Sep 2019 02:11:30 AM CDT | | OS: Linux LinuxMint: Linux Mint 19.2 Tina [4.15.0-62-generic|libc 2.27 (Ubuntu GLIBC 2.27-3ubuntu1)] Wed 11 Sep 2019 02:11:30 AM CDT | | Memory: 15.65 GB physical, 2.00 GB virtual Wed 11 Sep 2019 02:11:30 AM CDT | | Disk: 109.53 GB total, 86.55 GB free Wed 11 Sep 2019 02:11:30 AM CDT | | Local time is UTC -5 hours Wed 11 Sep 2019 02:11:30 AM CDT | | Config: use all coprocessors Wed 11 Sep 2019 02:11:30 AM CDT | | Last benchmark was 18150 days 07:11:30 ago Wed 11 Sep 2019 02:11:30 AM CDT | | No general preferences found - using defaults Wed 11 Sep 2019 02:11:30 AM CDT | | Preferences: Wed 11 Sep 2019 02:11:30 AM CDT | | max memory usage when active: 8015.26 MB Wed 11 Sep 2019 02:11:30 AM CDT | | max memory usage when idle: 14427.47 MB Wed 11 Sep 2019 02:11:30 AM CDT | | max disk usage: 86.60 GB Wed 11 Sep 2019 02:11:30 AM CDT | | don't use GPU while active Wed 11 Sep 2019 02:11:30 AM CDT | | suspend work if non-BOINC CPU load exceeds 25% Wed 11 Sep 2019 02:11:30 AM CDT | | (to change preferences, visit a project web site or select Preferences in the Manager) Wed 11 Sep 2019 02:11:30 AM CDT | | Setting up project and slot directories Wed 11 Sep 2019 02:11:30 AM CDT | | Checking active tasks Wed 11 Sep 2019 02:11:30 AM CDT | | Setting up GUI RPC socket Wed 11 Sep 2019 02:11:30 AM CDT | | Checking presence of 0 project files Wed 11 Sep 2019 02:11:30 AM CDT | | This computer is not attached to any projects Wed 11 Sep 2019 02:11:30 AM CDT | | Suspending GPU computation - computer is in use Wed 11 Sep 2019 02:12:01 AM CDT | | Fetching configuration file from http://setiathome.berkeley.edu/get_project_config.php Wed 11 Sep 2019 02:13:09 AM CDT | | Running CPU benchmarks Wed 11 Sep 2019 02:13:09 AM CDT | | Suspending computation - CPU benchmarks in progress Wed 11 Sep 2019 02:13:40 AM CDT | | Benchmark results: Wed 11 Sep 2019 02:13:40 AM CDT | | Number of CPUs: 12 Wed 11 Sep 2019 02:13:40 AM CDT | | 2981 floating point MIPS (Whetstone) per CPU Wed 11 Sep 2019 02:13:40 AM CDT | | 10629 integer MIPS (Dhrystone) per CPU Wed 11 Sep 2019 02:13:41 AM CDT | | Resuming computation Wed 11 Sep 2019 02:13:41 AM CDT | SETI@home | sched RPC pending: Project initialization Wed 11 Sep 2019 02:13:41 AM CDT | SETI@home | [sched_op] Starting scheduler request Wed 11 Sep 2019 02:13:41 AM CDT | SETI@home | [sched_op] Fetching master file Wed 11 Sep 2019 02:13:42 AM CDT | SETI@home | [sched_op] Got master file; parsing Wed 11 Sep 2019 02:13:42 AM CDT | SETI@home | [sched_op] Found 1 scheduler URLs in master file Wed 11 Sep 2019 02:13:42 AM CDT | SETI@home | Master file download succeeded Wed 11 Sep 2019 02:13:47 AM CDT | SETI@home | sched RPC pending: Project initialization Wed 11 Sep 2019 02:13:47 AM CDT | SETI@home | [sched_op] Starting scheduler request Wed 11 Sep 2019 02:13:47 AM CDT | SETI@home | Sending scheduler request: Project initialization. Wed 11 Sep 2019 02:13:47 AM CDT | SETI@home | Requesting new tasks for CPU and NVIDIA GPU Wed 11 Sep 2019 02:13:47 AM CDT | SETI@home | [sched_op] CPU work request: 1.00 seconds; 0.00 devices Wed 11 Sep 2019 02:13:47 AM CDT | SETI@home | [sched_op] NVIDIA GPU work request: 1.00 seconds; 0.00 devices Wed 11 Sep 2019 02:13:50 AM CDT | SETI@home | Scheduler request completed: got 0 new tasks Wed 11 Sep 2019 02:13:50 AM CDT | SETI@home | [sched_op] Server version 709 Wed 11 Sep 2019 02:13:50 AM CDT | SETI@home | No tasks sent Wed 11 Sep 2019 02:13:50 AM CDT | SETI@home | No tasks are available for AstroPulse v7 Wed 11 Sep 2019 02:13:50 AM CDT | SETI@home | No tasks are available for SETI@home v8 Wed 11 Sep 2019 02:13:50 AM CDT | SETI@home | Tasks for AMD/ATI GPU are available, but your preferences are set to not accept them Wed 11 Sep 2019 02:13:50 AM CDT | SETI@home | Tasks for Intel GPU are available, but your preferences are set to not accept them Wed 11 Sep 2019 02:13:50 AM CDT | SETI@home | This computer has reached a limit on tasks in progress Wed 11 Sep 2019 02:13:50 AM CDT | SETI@home | Project requested delay of 303 seconds This is more than 30 lines but I thought you'd like to read them. I'm lost at this point. I have updated this file after merging with another Linux computer from when I was using only the USB stick and didn't have a GPU, and it did have some work units though not being processed. After the merge I updated the SETI project and it still does not show any work units. George |
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 |
Wed 11 Sep 2019 02:11:30 AM CDT | | Starting BOINC client version 7.14.2 for x86_64-pc-linux-gnu This connect was the first one since installing and connecting to the project. It needed to get the master file and all the supporting files. For the very first connection to the project from a new host, the scheduler will send one cpu task and one gpu task for the first 24 hours. The scheduler needs to see the work sent returned and ostensible valid before sending any more work. This is done to be sure the host is capably set up to process work. The main problem you have is your preferences are set to: Wed 11 Sep 2019 02:11:30 AM CDT | | don't use GPU while active This is preventing the client from asking for gpu work. Wed 11 Sep 2019 02:13:47 AM CDT | SETI@home | [sched_op] NVIDIA GPU work request: 1.00 seconds; 0.00 devices And even if you get gpu work, you can't process it. Wed 11 Sep 2019 02:11:30 AM CDT | | Suspending GPU computation - computer is in use Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
George Send message Joined: 23 Oct 17 Posts: 222 Credit: 2,597,521 RAC: 13 |
In my global preferences my SETI@Home project preferences are set to receive CPU tasks and Nvidia GPU tasks from this project, and the Computing preferences for Suspend when computer is on battery, Suspend when computer is in use, and Suspend GPU computing when computer is in use are all NOT checked. I don't understand why I'm not receiving any tasks. George |
George Send message Joined: 23 Oct 17 Posts: 222 Credit: 2,597,521 RAC: 13 |
For my computer I.D., 8813159, the Linux Mint computer, it shows 100 CPU tasks and nothing for the GPU. George |
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 |
Then the host must be set to a different venue. You did say you merged the old configuration files from the old host. I see this: Wed 11 Sep 2019 02:11:30 AM CDT | | No general preferences found - using defaults The BOINC defaults are all of those things you mentioned being toggled on. You need to go the to project preferences and resave your general defaults. If needed toggle one setting from its current value to something else, then change it back and save it. Then make sure you restart BOINC or at least do an Update to pick up the new general preferences. Look at the Event Log startup again after restarting BOINC and make sure all the proper preferences are set now to use the gpu when active. Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 |
For my computer I.D., 8813159, the Linux Mint computer, it shows 100 CPU tasks and nothing for the GPU. Until you get the client to ask for your gpu work you won't get gpu tasks. Your preferences are preventing that. Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 |
Or set up a new venue with brand new defaults enabling the gpu and then make the change of the host location to the new venue to pick up the new preferences. https://setiathome.berkeley.edu/show_host_detail.php?hostid=8813159 You still have only contacted the project once so far. Make the preference changes and update the client using the Manager on the Projects tab. Set the Event Log logging options to include the sched_ops_debug flag. That prints out in the log exactly how many seconds of cpu work and gpu work is requested from the scheduler at every connection. Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
George Send message Joined: 23 Oct 17 Posts: 222 Credit: 2,597,521 RAC: 13 |
After changing preferences, updating SETI, and changing them again back to where they were, updating SETI again, and then exiting BOINC Manager and rebooting my computer and re-launching BOINC Manager this is what I have in the event log - all of it: Wed 11 Sep 2019 03:11:29 PM CDT | | Starting BOINC client version 7.14.2 for x86_64-pc-linux-gnu Wed 11 Sep 2019 03:11:29 PM CDT | | log flags: file_xfer, sched_ops, task, sched_op_debug Wed 11 Sep 2019 03:11:29 PM CDT | | Libraries: libcurl/7.58.0 GnuTLS/3.5.18 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3 Wed 11 Sep 2019 03:11:29 PM CDT | | Data directory: /home/george/BOINC Wed 11 Sep 2019 03:11:29 PM CDT | | CUDA: NVIDIA GPU 0: GeForce RTX 2060 (driver version 430.40, CUDA version 10.1, compute capability 7.5, 4096MB, 3970MB available, 6451 GFLOPS peak) Wed 11 Sep 2019 03:11:29 PM CDT | | OpenCL: NVIDIA GPU 0: GeForce RTX 2060 (driver version 430.40, device version OpenCL 1.2 CUDA, 5933MB, 3970MB available, 6451 GFLOPS peak) Wed 11 Sep 2019 03:11:29 PM CDT | SETI@home | Found app_info.xml; using anonymous platform Wed 11 Sep 2019 03:11:29 PM CDT | SETI@home | Syntax error in app_info.xml Wed 11 Sep 2019 03:11:29 PM CDT | | [libc detection] gathered: 2.27, Ubuntu GLIBC 2.27-3ubuntu1 Wed 11 Sep 2019 03:11:29 PM CDT | | Host name: GWG-PC-Linux Wed 11 Sep 2019 03:11:29 PM CDT | | Processor: 12 GenuineIntel Intel(R) Core(TM) i7 CPU X 990 @ 3.47GHz [Family 6 Model 44 Stepping 2] Wed 11 Sep 2019 03:11:29 PM CDT | | 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 ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt aes lahf_lm pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid dtherm ida arat flush_l1d Wed 11 Sep 2019 03:11:29 PM CDT | | OS: Linux LinuxMint: Linux Mint 19.2 Tina [4.15.0-62-generic|libc 2.27 (Ubuntu GLIBC 2.27-3ubuntu1)] Wed 11 Sep 2019 03:11:29 PM CDT | | Memory: 15.65 GB physical, 2.00 GB virtual Wed 11 Sep 2019 03:11:29 PM CDT | | Disk: 109.53 GB total, 86.25 GB free Wed 11 Sep 2019 03:11:29 PM CDT | | Local time is UTC -5 hours Wed 11 Sep 2019 03:11:29 PM CDT | | Config: use all coprocessors Wed 11 Sep 2019 03:11:29 PM CDT | SETI@home | URL http://setiathome.berkeley.edu/; Computer ID 8813159; resource share 100 Wed 11 Sep 2019 03:11:29 PM CDT | SETI@home | General prefs: from SETI@home (last modified 11-Sep-2019 14:46:14) Wed 11 Sep 2019 03:11:29 PM CDT | SETI@home | Computer location: home Wed 11 Sep 2019 03:11:29 PM CDT | SETI@home | General prefs: no separate prefs for home; using your defaults Wed 11 Sep 2019 03:11:29 PM CDT | | Preferences: Wed 11 Sep 2019 03:11:29 PM CDT | | max memory usage when active: 8015.26 MB Wed 11 Sep 2019 03:11:29 PM CDT | | max memory usage when idle: 16030.52 MB Wed 11 Sep 2019 03:11:29 PM CDT | | max disk usage: 85.79 GB Wed 11 Sep 2019 03:11:29 PM CDT | | suspend work if non-BOINC CPU load exceeds 35% Wed 11 Sep 2019 03:11:29 PM CDT | | (to change preferences, visit a project web site or select Preferences in the Manager) Wed 11 Sep 2019 03:11:29 PM CDT | | Setting up project and slot directories Wed 11 Sep 2019 03:11:29 PM CDT | | Checking active tasks Wed 11 Sep 2019 03:11:29 PM CDT | | Setting up GUI RPC socket Wed 11 Sep 2019 03:11:29 PM CDT | | Checking presence of 4 project files Wed 11 Sep 2019 03:20:54 PM CDT | | Re-reading cc_config.xml Wed 11 Sep 2019 03:20:54 PM CDT | | Config: use all coprocessors Wed 11 Sep 2019 03:20:54 PM CDT | | log flags: file_xfer, sched_ops, task, app_msg_receive, app_msg_send, cpu_sched Wed 11 Sep 2019 03:20:54 PM CDT | | log flags: cpu_sched_debug, cpu_sched_status, sched_op_debug Wed 11 Sep 2019 03:20:54 PM CDT | | [cpu_sched_debug] Request CPU reschedule: Core client configuration Wed 11 Sep 2019 03:21:02 PM CDT | | Re-reading cc_config.xml Wed 11 Sep 2019 03:21:02 PM CDT | | Config: use all coprocessors Wed 11 Sep 2019 03:21:02 PM CDT | | log flags: file_xfer, sched_ops, task, app_msg_receive, app_msg_send, cpu_sched Wed 11 Sep 2019 03:21:02 PM CDT | | log flags: cpu_sched_debug, cpu_sched_status, sched_op_debug Wed 11 Sep 2019 03:21:02 PM CDT | | [cpu_sched_debug] Request CPU reschedule: Core client configuration I'm concerned with: <Wed 11 Sep 2019 03:11:29 PM CDT | | CUDA: NVIDIA GPU 0: GeForce RTX 2060 Wed 11 Sep 2019 03:11:29 PM CDT | | OpenCL: NVIDIA GPU 0: GeForce RTX 2060 > ...where "NVIDIA GPU 0: GeForce RTX 2060" is displayed. Does the "0" (zero) mean there isn't a GPU? I don't understand because I haven't changed my venue yet, but it is set to "home", not "default". And using your link I have contacted the server 3 times, not once. George |
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 |
Something changed. You either touched app_info.xml or something corrupted it. You didn't show using an anonymous platform in your earlier event log dump. You are showing it in this latest however but there is a problem with the app_info.xml file. Wed 11 Sep 2019 03:11:29 PM CDT | SETI@home | Syntax error in app_info.xml Unpack the boinc.7z archive and copy and paste the app_info.xml file from the archive into your seti projects directory. Restart BOINC and see if the syntax error message goes away. BOINC counts the first gpu as GPU0. That is normal for a single gpu host. Your card is detected for both CUDA and OpenCL. It is ready to process gpu work if you ask for it. What does the Event Log show for the scheduler connection? You chopped that off from your post. Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 |
Post the contents of app_info.xml You likely have a truncated delimiter on one of the xml sections. If app_info isn't formatted correctly, then you are not picking up all the parts of it. Probably the gpu section. Did you edit it by chance? You should use it as delivered by TBar to begin with before tampering with it. Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
George Send message Joined: 23 Oct 17 Posts: 222 Credit: 2,597,521 RAC: 13 |
Here is the app_info.xml file as it is now: # # /home/george/BOINC/projects/setiathome.berkeley.edu/app_info.xml # # Configuration file for nvidia-settings - the NVIDIA X Server Settings utility # Generated on Wed Sep 11 00:43:07 2019 # # ConfigProperties: RcFileLocale = C DisplayStatusBar = Yes SliderTextEntries = Yes IncludeDisplayNameInConfigFile = No ShowQuitDialog = Yes UpdateRulesOnProfileNameChange = Yes Timer = PowerMizer_Monitor_(GPU_0),Yes,1000 Timer = Thermal_Monitor_(GPU_0),Yes,1000 Timer = Memory_Used_(GPU_0),Yes,3000 # Attributes: 0/SyncToVBlank=1 0/LogAniso=0 0/FSAA=0 0/TextureClamping=1 0/FXAA=0 0/AllowFlipping=1 0/FSAAAppControlled=1 0/LogAnisoAppControlled=1 0/OpenGLImageSettings=1 0/FSAAAppEnhanced=0 0/XVideoSyncToDisplayID=HDMI-0 [DPY:DVI-D-0]/Dithering=0 [DPY:DVI-D-0]/DitheringMode=0 [DPY:DVI-D-0]/DitheringDepth=0 [DPY:DVI-D-0]/ColorSpace=0 [DPY:DVI-D-0]/ColorRange=0 [DPY:DVI-D-0]/SynchronousPaletteUpdates=0 [DPY:HDMI-0]/RedBrightness=0.000000 [DPY:HDMI-0]/GreenBrightness=0.000000 [DPY:HDMI-0]/BlueBrightness=0.000000 [DPY:HDMI-0]/RedContrast=0.000000 [DPY:HDMI-0]/GreenContrast=0.000000 [DPY:HDMI-0]/BlueContrast=0.000000 [DPY:HDMI-0]/RedGamma=1.000000 [DPY:HDMI-0]/GreenGamma=1.000000 [DPY:HDMI-0]/BlueGamma=1.000000 [DPY:HDMI-0]/Dithering=0 [DPY:HDMI-0]/DitheringMode=0 [DPY:HDMI-0]/DitheringDepth=0 [DPY:HDMI-0]/ColorSpace=0 [DPY:HDMI-0]/ColorRange=0 [DPY:HDMI-0]/SynchronousPaletteUpdates=0 [DPY:DP-0]/Dithering=0 [DPY:DP-0]/DitheringMode=0 [DPY:DP-0]/DitheringDepth=0 [DPY:DP-0]/ColorSpace=0 [DPY:DP-0]/ColorRange=0 [DPY:DP-0]/SynchronousPaletteUpdates=0 [DPY:DP-1]/Dithering=0 [DPY:DP-1]/DitheringMode=0 [DPY:DP-1]/DitheringDepth=0 [DPY:DP-1]/ColorSpace=0 [DPY:DP-1]/ColorRange=0 [DPY:DP-1]/SynchronousPaletteUpdates=0 And here is the app_info.xml file from TBar: <app_info> <app> <name>setiathome_v8</name> </app> <file_info> <name>setiathome_x41p_V0.98b1_x86_64-pc-linux-gnu_cuda90</name> <executable/> </file_info> <app_version> <app_name>setiathome_v8</app_name> <platform>x86_64-pc-linux-gnu</platform> <version_num>801</version_num> <plan_class>cuda90</plan_class> <cmdline></cmdline> <coproc> <type>NVIDIA</type> <count>1</count> </coproc> <avg_ncpus>0.1</avg_ncpus> <max_ncpus>0.1</max_ncpus> <file_ref> <file_name>setiathome_x41p_V0.98b1_x86_64-pc-linux-gnu_cuda90</file_name> <main_program/> </file_ref> </app_version> <app> <name>astropulse_v7</name> </app> <file_info> <name>astropulse_7.08_x86_64-pc-linux-gnu__opencl_nvidia_100</name> <executable/> </file_info> <file_info> <name>AstroPulse_Kernels_r2751.cl</name> </file_info> <file_info> <name>ap_cmdline_7.08_x86_64-pc-linux-gnu__opencl_nvidia_100.txt</name> </file_info> <app_version> <app_name>astropulse_v7</app_name> <platform>x86_64-pc-linux-gnu</platform> <version_num>708</version_num> <plan_class>opencl_nvidia_100</plan_class> <coproc> <type>NVIDIA</type> <count>1</count> </coproc> <avg_ncpus>0.1</avg_ncpus> <max_ncpus>0.1</max_ncpus> <file_ref> <file_name>astropulse_7.08_x86_64-pc-linux-gnu__opencl_nvidia_100</file_name> <main_program/> </file_ref> <file_ref> <file_name>AstroPulse_Kernels_r2751.cl</file_name> </file_ref> <file_ref> <file_name>ap_cmdline_7.08_x86_64-pc-linux-gnu__opencl_nvidia_100.txt</file_name> <open_name>ap_cmdline.txt</open_name> </file_ref> </app_version> <app> <name>setiathome_v8</name> </app> <file_info> <name>MBv8_8.22r3711_sse41_intel_x86_64-pc-linux-gnu</name> <executable/> </file_info> <app_version> <app_name>setiathome_v8</app_name> <platform>x86_64-pc-linux-gnu</platform> <version_num>800</version_num> <file_ref> <file_name>MBv8_8.22r3711_sse41_intel_x86_64-pc-linux-gnu</file_name> <main_program/> </file_ref> </app_version> <app> <name>astropulse_v7</name> </app> <file_info> <name>ap_7.05r2728_sse3_linux64</name> <executable/> </file_info> <app_version> <app_name>astropulse_v7</app_name> <version_num>704</version_num> <platform>x86_64-pc-linux-gnu</platform> <plan_class></plan_class> <file_ref> <file_name>ap_7.05r2728_sse3_linux64</file_name> <main_program/> </file_ref> </app_version> </app_info> I'll replace the app-info.xml file with TBar's and let you know what happens next. George |
George Send message Joined: 23 Oct 17 Posts: 222 Credit: 2,597,521 RAC: 13 |
Okay, it's working now. Downloading as we chat... I'll let you know later how the projects are doing. I don't know what I did, but I'm glad it's working now. Once again, I thank you. I really mean it. George |
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 |
The nvidia settings config file is not really useful. But I see no syntax error in the app_config.xml file as posted. But it is possible that there are some hidden characters in the files like a Windows CR-LF character in the file that is upsetting Linux when it parses the file. Please unpack the virgin app_info.xml file from the archive and replace the existing one. Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 |
OK, George. Glad you got it working. My last post was delayed by a yak from Zalster. So ignore. See a gpu task already returned and everything looks fine with it using the defaults. If you feel brave, you can speed it up a bit more by changing some values in the app_info.xml file. I would first back up the file before editing. You have plenty of cpu cores available as long as you are not trying to run 12 cpu tasks along with the gpu task. Your gpu task time looks a little bit long I think for what a 2060 should be doing. So first thing it to set the "Use at most cpu%" for the host at 90% either on the website preferences or the local preferences in the Manager. You need to free up one cpu core to support the gpu task. Do that first and then see if that speeds up the gpu computation. Then you can add the -nobs parameter to the command line entry in the app_info.xml file. <app_info> <app> <name>setiathome_v8</name> </app> <file_info> <name>setiathome_x41p_V0.98b1_x86_64-pc-linux-gnu_cuda90</name> <executable/> </file_info> <app_version> <app_name>setiathome_v8</app_name> <platform>x86_64-pc-linux-gnu</platform> <version_num>801</version_num> <plan_class>cuda90</plan_class> <cmdline>-nobs</cmdline> Save the edit with the Text Editor. Then see what kind of times you can now manage. Then the next thing to try is to change to the CUDA101 app that is also provided by TBar in the project directory. That would be a bit faster than the CUDA90 app that is the default. You would again use the Text Editor and use the Find and Replace function swap out the filename of the CUDA90 app for the filename of the CUDA101 app and then save the file. There are two places in the file the that the filenames are referenced. </app> <file_info> <name>setiathome_x41p_V0.98b1_x86_64-pc-linux-gnu_cuda90</name> <executable/> </file_info> and here: <file_ref> <file_name>setiathome_x41p_V0.98b1_x86_64-pc-linux-gnu_cuda90</file_name> <main_program/> </file_ref> You would be replacing those filename entries with: setiathome_x41p_V0.98b1_x86_64-pc-linux-gnu_cuda101 Save the file and restart BOINC and you would now be running the CUDA101 app. Make no other changes to the app_info.xml file. Just change the file name and save. That is all. Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
Zalster Send message Joined: 27 May 99 Posts: 5517 Credit: 528,817,460 RAC: 242 |
My last post was delayed by a yak from Zalster. See...I am good for something...Bahahaha |
©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.