Message boards : GPUs : Ubuntu 15.10 and BOIC
Message board moderation
Author | Message |
---|---|
Send message Joined: 7 Mar 12 Posts: 67 |
I just installed 64-bit Ubuntu 15.10 Gnome and set BOINC up on a machine. I installed the NVidia proprietary driver from the repo. I don't see any GPU usage happening. Regrettably, I don't remember the name of the log file or where it is to see if BOINC identified any GPUs, but I suspect it did not. This is a 384 CUDA core card. I remember it was a bit of a pain to get working under Mint 17 KDE a few years ago. Any help? |
Send message Joined: 20 Nov 12 Posts: 801 |
If you have Manager open it's Event log that you are looking for. Tools menu or ctrl+shift+e . The same messages as well as older ones are in stdoutdae.txt . |
Send message Joined: 7 Mar 12 Posts: 67 |
If you have Manager open it's Event log that you are looking for. Tools menu or ctrl+shift+e . Thank you for your response. Yes, I found it some time after I posted that question. None of the NVidia drivers appear to actually work in Ubuntu 15.10. If you use them Xorg has to keep sending crash reports back to Ubuntu developers. Not to mention BOINC cannot see the CUDA cores. Once the current work units complete I will try solusproject then 4MLinux on that machine to run BOINC. If neither of them work hopefully the new Mint will be out and work. Mint 17 used to work, had it on a few machines, but it was quit a trick to get the drivers to work in a manner which let the CUDA core be used by BOINC. I have high hopes for 4MLinux as it is supposed to be for multimedia. |
Send message Joined: 7 Mar 12 Posts: 67 |
Here is how things currently stand: Ubuntu 15.10 64-bit Gnome: * Both proprietary Nvidia driver and the opensource nvidia-modprobe can be easily installed. nvidia-modprobe is actually listed in the SoftwareCenter * Once installed BOINC will identify CUDA cores and use them. * Once installed Xorg and other "internal system components" will regularly popup dialogs about crashes and needs to file bug reports. * Once nvidia-modprobe is installed onboard network port will take hours to establish a connection. I don't know exactly how long. It was mid afternoon and I left the office after an hour. When I came in some time after 2:30am it said it was established. * Once nvidia-modprobe is installed plugging in a wireless usb stick will cause various "internal system error" and "crash" requests to file bug reports, but wireless will work while wired network connection is all discombobulated. 4MLinux 64-bit: Would not boot to install. Complained about some CMenuText file (or some name like that) missing. It may simply not be configured correctly for Rufus to put on a thumb drive. I didn't take the time to burn a DVD to find out. solusproject 64-bit: Looked absolutely beautiful on old monitor. Did not have an option to install BOINC. Not certain if it had NVidia drivers. Both of these conditions seemed odd since this is supposed to be a YABU (Yet Another uBUntu). Perhaps there is a magic incantation one has to have to also look at Ubuntu repos. Ubuntu 15.10 Ugly/Unity 64-bit * Driver is easily installed, but nvidia-modprobe not listed in SoftwareCenter. You have to install Synaptic package manager in order to find nvidia-modprobe. * GPU "seems" to be accessible. * Have not noticed a significant number of bug report/crash dialogs so Ugly/Unity seems to have actually had "some" testing and Gnome not-so-much. * Wired network connection still takes quite a few minutes to establish itself once nvidia-modprobe is installed. Prior to that the network connects instantaneously at boot as one expects. Mint 17 is several days late now. I suspect they are trying to work around these Ubuntu problems. |
Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.