When you start swapping GPUs you may have problems. On a First Install it's best to only have One GPU in the main slot where you intend to keep it. After you get it installed and running then you can start adding GPUs. That's the best way, other ways may work, but you might have problems.

Well, I didn't have a problem with multiple GPUs on the first two boxes and, since the 3rd one is an xw9400 like one of the others, I didn't anticipate problems with that one either. Apparently though, according to several posts I found online, the Live CD just doesn't play well with some GPUs, hence the tip I found for that "nomodeset" option in the hidden menu, which works fine (once you stumble across it).

EDIT: Anyway, the scheduler just sent me 33 MB tasks for NVIDIA and the first ones seem to be running smoothly. Hopefully it'll go smoothly from here on. (Oh, wait.......it's LINUX!)

When something doesn't run it's usually caused by a missing dependency or permission setting. Is this machine the one that had the BOINC folder in Downloads?
Move the downloaded boinc_7.2.42....sh file to your Home folder next to your Current BOINC folder and run the .sh file again so it updates your BOINC folder.
Check the following files for Execute bits and Dependencies;
boinc
boinccmd
boincmgr
boincscr
Install any missing Dependencies using the Package Manager.
That's All it should take to get it running. Double click boincmgr to run it.
If it doesn't work, open a Terminal, cd to the BOINC folder, and run each App from the Terminal and note the remarks.
./boincmgr

. . Hi TBar,

. . That's the machine. OK I will run the distro shell again and try running each app separately. Thanks for the tips.

Stephen

..

. . With Linux everytime there is something different, some problem I didn't have on the previous effort. :(

Stephen

:(

Ain't that the truth. After having fewer than usual PITA moments setting up my first two Linux boxes this time around (this being my 5th foray into the funhouse that is Linux World), I thought I was well prepared for the third box. Wrong!

. . Though your experiences were different to mine in the details it all seems soooo familiar.

. . One thing I will mention about Coolbits is that with multiple GPUs of different types and/or memory sizes there is a value to use that "adapts" coolbits to deal with the variations. So it would not be 28 but another value. I posted a listing of those values but I cannot find that post ....

. . Amen brother.

Stephen

..

. . Hi TBar

. . I did that and it is now running, but I picked a bad time to do it. Not getting any work with the servers the way they are. I will return to it later on when work is flowing more readily again.

Stephen

:(

. . @ All,

. . Linux is not my friend. I have Boinc running but cannot get any GPU work.

. . I also get these error messages ...

Sun 25 Jun 2017 22:07:26 AEST | SETI@home | [error] merge_info(): failed to change permissions of setiathome_8.00_x86_64-pc-linux-gnu
Sun 25 Jun 2017 22:07:26 AEST | SETI@home | [error] merge_info(): failed to change permissions of setigraphics_8.00_x86_64-pc-linux-gnu
Sun 25 Jun 2017 22:07:26 AEST | SETI@home | [error] merge_info(): failed to change permissions of seti_800.jpg
Sun 25 Jun 2017 22:07:26 AEST | SETI@home | [error] merge_info(): failed to change permissions of setiathome-8.00_AUTHORS
Sun 25 Jun 2017 22:07:26 AEST | SETI@home | [error] merge_info(): failed to change permissions of setiathome-8.00_COPYING
Sun 25 Jun 2017 22:07:26 AEST | SETI@home | [error] merge_info(): failed to change permissions of setiathome-8.00_COPYRIGHT
Sun 25 Jun 2017 22:07:26 AEST | SETI@home | [error] merge_info(): failed to change permissions of setiathome-8.00_README
Sun 25 Jun 2017 22:07:26 AEST | SETI@home | [error] merge_info(): failed to change permissions of bl_bkg_800.jpg
Sun 25 Jun 2017 22:07:26 AEST | SETI@home | [error] merge_info(): failed to change permissions of bl_800.jpg

. . Flumoxed again .... :(

. . OK, this is weird! I just experienced the phenomenon Grant has been having of late. I have not received any GPU work at all today since trying to finish configuring Linux for CUDA80, and it has been over several hours. I begin to write this message about the problem and eerily I suddenly receive a dozen GPU WUs. Hmmm spooky.

Stephen

??

Just saw this while I was perusing ZDnet, and came across this article about the new 4.12 kernel: Linux just got one of its biggest kernel updates yet says Linus Torvalds

Being at best a struggling Linux Newb, I was wondering if it makes sense to try to apply the new kernal to an existing release, or to just wait until the majors (Ubuntu, Mint, etc) push out a new release with it in it? From the sounds of it, it should be something that can be installed on existing installations, but not being a command line warrior, that sounds like something I'd rather avoid. What are you guys' thoughts on it? Sounds like it was a pretty big deal, adding a lot of support to newer hardware, as well as needed updates.

---

. . Hi Al

. . Being a very low level Linux user like yourself I like to have things automated so they get done correctly. If I tried to do them manually Iknow there would be problems. So I will wait for a package to take care of any updates. Also there needs to be a version of BOINC compatible with the new release that allows me to choose the installation location unlike the repo version which does not. But who know what tomorrow will bring :)

Stephen

<shrug>

. . Linux continues to frustrate me. Another kind user posted a script to provide intelligent fan control for nVidia GPUs running under Linux. But if I try to sudo it (yes the 'run as a program' permission is set) I get the response 'no such file or directory' even though I am looking right at it. If I try to bash it then I get I get all sorts of errors. How do you convince Linux to run a shell script?

Stephen

??

'no such file or directory'

That usually means you've either entered the wrong Name or Location.
By default the Terminal opens to your Home directory. If the File is Not there you must tell the Terminal the Location of the File you wish to run, or, move the File to your Home directory to run it.
An example would be to run a File Located in your Downloads Folder/Directory. Open the Terminal, enter cd and a space afterwards, then drag and drop the Downloads folder into the Terminal window.
Make sure the Terminal is the front application, then hit enter. You will now be in the Downloads directory and can run a file located in that directory.
Sudo means SuperUser Do, it allows you to run the file as Root. To run the file as Root you would enter sudo ./filename, provided you are in the directory where the file is located.

This. Me. Linux. Ugg.

I know I have to get past all that, but I'm really not looking forward to installing and maintaining it. Brings back such frustrating memories... :-/ Yes, with Linux there were Definitely times I'd like to just BASH it, that's true... ;-) lol

*edit* But thanks for the great explanation, Tbar, I think I'm going to put a cheat sheet together with helpful nuggets like this one.

---

. . Linux continues to frustrate me. Another kind user posted a script to provide intelligent fan control for nVidia GPUs running under Linux. But if I try to sudo it (yes the 'run as a program' permission is set) I get the response 'no such file or directory' even though I am looking right at it. If I try to bash it then I get I get all sorts of errors. How do you convince Linux to run a shell script?

Stephen

??

I don't think you should even need sudo for that script, but are you including the file extension (.sh) in your command? In other words, if you just enter ./gpufanspeed, you'll probably get that error message you're seeing, but if you enter ./gpufanspeed.sh, it should work just fine. Linux == Gotcha.

EDIT: Example

jeff@xw9400L:~$ cd Desktop
jeff@xw9400L:~/Desktop$ ./gpufanspeed
bash: ./gpufanspeed: No such file or directory
jeff@xw9400L:~/Desktop$ ./gpufanspeed.sh
  Attribute 'GPUFanControlState' (xw9400L:0[gpu:0]) assigned value 1.
  Attribute 'GPUFanControlState' (xw9400L:0[gpu:1]) assigned value 1.
  Attribute 'GPUFanControlState' (xw9400L:0[gpu:2]) assigned value 1.
  Attribute 'GPUFanControlState' (xw9400L:0[gpu:3]) assigned value 1.

  Attribute 'GPUTargetFanSpeed' (xw9400L:0[fan:0]) assigned value 20.
  Attribute 'GPUTargetFanSpeed' (xw9400L:0[fan:1]) assigned value 20.
  Attribute 'GPUTargetFanSpeed' (xw9400L:0[fan:2]) assigned value 40.
  Attribute 'GPUTargetFanSpeed' (xw9400L:0[fan:3]) assigned value 20.

^C
jeff@xw9400L:~/Desktop$ 

or
type ./gp and hit <tab> to autocomplete the filename ...

---

To overcome Heisenbergs:
"You can't always get what you want / but if you try sometimes you just might find / you get what you need." -- Rolling Stones

For those that like Debian I managed to update my GPU crunchers to Stretch using pretty much the same instructions to install apart from changing Jessie to Stretch.

One gotcha was my firewall script wouldn't execute any more. I used to have it in rc.local. I followed the suggestions on the Debian wiki which run it as a service which still seems to work, however you also have to set execute permissions on a couple of files. I didn't have to do that under Jessie.

Also tried clean-installing Stretch on iGPU machines and can't get a desktop (mate) any more. I've raised a bug with Debian for that one.

---

BOINC blog

. . Hi everyone,

. . Thanks for all the advice, I have learned or re-learned a couple of things about Linux.

. . But ... (isn't there always one of those?)

That usually means you've either entered the wrong Name or Location.
By default the Terminal opens to your Home directory. If the File is Not there you must tell the Terminal the Location of the File you wish to run, or, move the File to your Home directory to run it.
An example would be to run a File Located in your Downloads Folder/Directory. Open the Terminal, enter cd and a space afterwards, then drag and drop the Downloads folder into the Terminal window.
Make sure the Terminal is the front application, then hit enter. You will now be in the Downloads directory and can run a file located in that directory.
Sudo means SuperUser Do, it allows you to run the file as Root. To run the file as Root you would enter sudo ./filename, provided you are in the directory where the file is located.

. . I now know that dropping a folder into an open terminal window takes the terminal to that folder ... neat trick. And I also learned what Sudo means ... that actually does help trying to understand what I am doing. I was also reminded about the short cut of using the first few characters then tabbing, that is very handy. The 'but' is that this is pretty much what I was doing. I placed the file on the desktop as originally suggested, then opened the terminal and executed 'ls -l' to check the directory name, then cd'd to that directory, repeated 'ls -l' to confirm the file was there and it was with all the read/write/execute permissions set. I then sudo'd it with ./<filenname>. But error, no file or directory found.

. . I retried it after reading your comments and got only a slight variation which I will post in the next message. I shortened the file name for ease of use in the retry.

Stephen

??

Possibility ... Linux IS CaSe SeNsItIvE

Possibility ... Linux IS CaSe SeNsItIvE

. . Yep, that is why I did the ls -l before trying to change directories, I have been bitten by that one before.

Stephen

:(

. . This is how it goes for me.

stephen@Mi-Burrito:~$ ls -l
total 75724
drwxr-xr-x 3 stephen stephen 4096 Jul 8 10:35 Desktop
drwxr-xr-x 2 stephen stephen 4096 Jun 24 16:26 Documents
drwxr-xr-x 7 stephen stephen 4096 Jun 27 10:43 Downloads
stephen@Mi-Burrito:~$ cd Desktop
stephen@Mi-Burrito:~/Desktop$ ls -l
total 8
-rwxr-xr-x 1 stephen stephen 1860 Jul 8 10:37 GPU_fan-control.sh
drwxrwxr-x 2 stephen stephen 4096 Jul 7 21:59 Things to remember
stephen@Mi-Burrito:~/Desktop$ sudo ./GPU_fan-control.sh
sudo: unable to execute ./GPU_fan-control.sh: No such file or directory
stephen@Mi-Burrito:~/Desktop$ ./GPU_fan-control.sh
bash: ./GPU_fan-control.sh: /bin/bash^M: bad interpreter: No such file or directory

. . The small difference is that I also tried it without the 'sudo' but that failed as well.

Stephen

:(

Try moving the file to your Home folder and run it from there.
Right click on the file, choose Properties, copy the name, and paste it into the terminal. Look for a space before or after the name that shouldn't be there.

Try moving the file to your Home folder and run it from there.
Right click on the file, choose Properties, copy the name, and paste it into the terminal. Look for a space before or after the name that shouldn't be there.

. . OK, thanks.

. . I did that (moved it to the home folder) and this time it ran but sadly there is a problem with the script ...

stephen@Mi-Burrito:~$ ./GPU_fan-control.sh 

(nvidia-settings:23079): Gtk-WARNING **: Unable to locate theme engine in module_path: "hcengine",

  Attribute 'GPUFanControlState' (Mi-Burrito:0[gpu:0]) assigned value 1.

./GPU_fan-control.sh: line 12: syntax error near unexpected token `elif'
./GPU_fan-control.sh: line 12: `	elif (("$current_temp" > 40)) && (("$cur'ent_temp" < 51)); then

. . Sadly I don't know what this means, though it seems something is missing or different in my setup from the one that this was working on.

. . Oh well it was worth a shot ...

Stephen

:(

./GPU_fan-control.sh: line 12: ` elif (("$current_temp" > 40)) && (("$cur'ent_temp" < 51)); then

That looks like a simple typo when you edited the script. Just change "$cur'ent_temp" to "$current_temp" and try again.