. . For BOINC he recommends this version as opposed to the one in the Linux Software repository. Having accidentally used the other one I have to agree with his recommendation. This one allows you to install BOINC into /home/<username>/BOINC where you can work with it freely while the other version installs under identity ROOT in /var/lib/boinc-client and creates hassles with access and permissions. That is best avoided.

boinc_7.2.42_x86_64-pc-linux-gnu.sh

. . He has a link to the BOINC version in his thread, I will see if I can copy it to here.
Stephen

:)

This one? http://www.bc-team.org/downloads.php?view=detail&df_id=15&sid=c9a35920f823db9c27e994901cee4881

. . I am pretty sure there is a later version which TBar feels is more suitable. I am about to check it out again as I have a new box to convert to Linux myself.

Stephen

. .

. . Here is his link to the CUDA60/80 Special app:-

http://www.arkayn.us/forum/index.php?topic=197.msg4499#msg4499

Is NVIDIA-Linux-x86_64-375.39.run still most suitable driver?
Found CUDA 6/CUDA9 but no CUDA8. Is it obsolette?

. . Yes sort of. version zi3v Cuda80 has been superceded by zi3v Cuda90. I am still running 80 and it is giving very good results but the new box will be the Cuda90 version. All reports say it is as stable and gives even less inconclusives, though I get very few with 80. I am running the 80 version with much later video drivers, 384.130, with no problems.

Stephen

. .

. . Here is his link to the CUDA60/80 Special app:-

http://www.arkayn.us/forum/index.php?topic=197.msg4499#msg4499

Is NVIDIA-Linux-x86_64-375.39.run still most suitable driver?
Found CUDA 6/CUDA9 but no CUDA8. Is it obsolette?

It looks like the discrete CUDA8 special app link didn't get created after the rebuild of the website after recovery. The CUDA8 is rolled up into the All-in-One BOINC7.4.44/CUDA8 special app package. It is available as a 3 part download.
BOINC All-in-One

[Edit]You still need to read the README_x41p_zi3v.txt document to find the Google Drive links for the CUDA8 dll libraries. The CUDA9 special app download already includes the CUDA9 dll libraries.

I fixed the broken links by uploading the packages so they should download now.

As Stephen said, either the CUDA8 or CUDA9 special app is returning very good statistics with low inconclusives and invalids.

The main repositories are shipping out Nvidia-390 as the current long lived release. The current short term release is Nvidia-396.51 and is available via the graphics-drivers team ppa.

sudo add-apt-repository ppa:graphics-drivers/ppa

sudo apt-get update

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

I find it easiest to install the Nvidia drivers via the Software Updater application. As long as you have added the graphics-drivers ppa to the Other Software tab, then you should find links for both Nvidia-390 and Nvidia-396 on the Additional Drivers tab of the Software Updater application.

What's nice is that it grabs the metapackage of the Nvidia driver which includes all the ancillary compute parts as well as all the normal ancillary Nvidia utilities along with the main graphics drivers. No chance of not loading the CUDA and OpenCL components of which both are needed for MB and AP tasks and the special apps.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

. . Hi people,

. . It is time to configure the new rig as a Linux box. I will be loading Cuda9.0 but I am unsure as to which flavour of Linux to use. Ubuntu 18.04 seems pretty rock solid but I am leaning towards Lubuntu 18.04 because I have heard it has a more "Windows User" friendly interface/desktop.

. . Does anyone have any ideas on which would be better as a purely user friendly platform for a dedicated cruncher host? Any Pros or Cons about either OS?

Stephen

? ?

. . Hi people,

. . It is time to configure the new rig as a Linux box. I will be loading Cuda9.0 but I am unsure as to which flavour of Linux to use. Ubuntu 18.04 seems pretty rock solid but I am leaning towards Lubuntu 18.04 because I have heard it has a more "Windows User" friendly interface/desktop.

. . Does anyone have any ideas on which would be better as a purely user friendly platform for a dedicated cruncher host? Any Pros or Cons about either OS?

Stephen

? ?

Lubuntu was originally developed for "light-weight" hardware. They now have proclaimed they want to get away from that association.
lubuntu-no-more-old-distro
They also have stated they are dropping support for 32bit systems as most of the distributions also have.

See that Dropbox is dropping support for sync on Linux for nothing but ext4 filesystems.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

If you want a " look and feel" similar to Windows just use a Gnome theme that looks like Windows on Ubuntu 18.04.
how-to-make-ubuntu-look-more-like-windows

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

If you want a " look and feel" similar to Windows just use a Gnome theme that looks like Windows on Ubuntu 18.04.
how-to-make-ubuntu-look-more-like-windows

. . Well I just fired up the Lubuntu 'live' disk and I must say I do like the look of it. I will try the Ubuntu 'live' disk and see how that compares. I can't remember though which version of Boinc is the current recommendation.

. . I have a time limit because I want CUDA 9.0 up and running for WOW :)

Stephen

:)

I just installed Lubuntu and the "Special Sauce"/CUDA90 on my Win10. It is a dual-boot arrangement. Yes the gpu tasks are running almost 50% less time. (7 odd min vs. 4 odd min).

All the install discussion was in the 16c/32t thread.

It sounds like I should move over here though.

1) What is the equivalent of TThortle under Linux?
2) I installed the "alternate" Nvidia drivers and it seems to be working. Should I have left in the "original" X-server drivers?
3) The screen is "wavy" when I scroll. I am running two gtx 1060 3GB cards. Is there a way to fix this?
4) I have already put in an app_config.xml file so that I have 1 core driving each card.
Should I be looking for the equivalent of the "MB*Sog.txt" command file so I can put in my Nvidia parameters? Or was that taken care of in the "app_info.xml" file that came with the "special sauce" setup?

Thank you,
Tom

---

A proud member of the OFA (Old Farts Association).

If you want a " look and feel" similar to Windows just use a Gnome theme that looks like Windows on Ubuntu 18.04.
how-to-make-ubuntu-look-more-like-windows

. . Well I just fired up the Lubuntu 'live' disk and I must say I do like the look of it. I will try the Ubuntu 'live' disk and see how that compares. I can't remember though which version of Boinc is the current recommendation.

. . I have a time limit because I want CUDA 9.0 up and running for WOW :)

Stephen

:)

Well the BOINC 7.44/CUDA80 All-in-One links are working again after I uploaded the missing files. But I was told today the CUDA80 libraries that are listed for download at Google Drive in the readme docs are broken now.

So that is not really an option for the CUDA80 special app. You can still install the All-in-One and just copy the unpacked CUDA90 files into the Seti project folder and it will run the CUDA90 special app on BOINC 7.44. The BOINC 7.8.3 link was always working. The CUDA90 special app works plus it contains the CUDA90 libraries in the zip file already.

Or install the BOINC 7.8.3 version and install the CUDA90 special app. You just have to make the project folder and create the setiathome.berkeley.edu folder in the project folder.

Caveat. MilkyWay@home will not run on any BOINC less than 7.6.2 so the BOINC 7.4.44 is not usable for that project.

Follow all instructions for checking dependencies. Install the libwebkitgtk-1.0-0 package and the libcurl3 package. Make sure that boinc and boincmgr have the "allow executing as program" checked in the file permissions. Double click boincmgr, launch the Manager and join the project. Crunch tasks.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

I just installed Lubuntu and the "Special Sauce"/CUDA90 on my Win10. It is a dual-boot arrangement. Yes the gpu tasks are running almost 50% less time. (7 odd min vs. 4 odd min).

All the install discussion was in the 16c/32t thread.

It sounds like I should move over here though.

1) What is the equivalent of TThortle under Linux?
2) I installed the "alternate" Nvidia drivers and it seems to be working. Should I have left in the "original" X-server drivers?
3) The screen is "wavy" when I scroll. I am running two gtx 1060 3GB cards. Is there a way to fix this?
4) I have already put in an app_config.xml file so that I have 1 core driving each card.
Should I be looking for the equivalent of the "MB*Sog.txt" command file so I can put in my Nvidia parameters? Or was that taken care of in the "app_info.xml" file that came with the "special sauce" setup?

Thank you,
Tom

1) No similar utility like TThrottle in Linux for gpu use. Cpus are limited by their own design and system governors. You can use nvidia-smi for power limit control of the gpu. Example power limit set to 85%.

nvidia-smi -pm 1 # enable persistance mode
nvidia-smi -pl 85

2) The original Nouveau drivers are always installed and can be reverted to at any times. The Nouveau drivers will not allow compute on any gpu. Not usable for crunching.

3) There shouldn't be any 'waviness' Sounds like the card or monitor were not interrogated for correct horizontal and vertical drive frequencies. Or the gpu is set for incorrect screen resolution. Run xrandr in Terminal to set custom screen resolution. Or insufficient power supply to drive two 1060's.

4) No special tuning options for the special app. It determines the best settings automatically for every card type. You can put the -nobs option into the command line in either the app_info or your app_config.<cmdline>-nobs</cmdline> This will use one full cpu core for each gpu task and speed up calculation by 10-15%.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Crunchers Anonymous links for the AMD and Intel AVX2 Linux MB cpu apps have been fixed and the files are downloadable again.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Crunchers Anonymous links for the AMD and Intel AVX2 Linux MB cpu apps have been fixed and the files are downloadable again.

. . In SoG the specs for the Ryzen 7-1700 do not list AVX2 as one of its features, just AVX. I thought the Ryzens all had AVX2 ...

. . So should I try the AVX2 setup or would that be a bad, bad thing?

Stephen

? ?

. . Well I just fired up the Lubuntu 'live' disk and I must say I do like the look of it. I will try the Ubuntu 'live' disk and see how that compares. I can't remember though which version of Boinc is the current recommendation.

. . I have a time limit because I want CUDA 9.0 up and running for WOW :)

Stephen

:)

Well the BOINC 7.44/CUDA80 All-in-One links are working again after I uploaded the missing files. But I was told today the CUDA80 libraries that are listed for download at Google Drive in the readme docs are broken now.

So that is not really an option for the CUDA80 special app. You can still install the All-in-One and just copy the unpacked CUDA90 files into the Seti project folder and it will run the CUDA90 special app on BOINC 7.44. The BOINC 7.8.3 link was always working. The CUDA90 special app works plus it contains the CUDA90 libraries in the zip file already.

Or install the BOINC 7.8.3 version and install the CUDA90 special app. You just have to make the project folder and create the setiathome.berkeley.edu folder in the project folder.

Caveat. MilkyWay@home will not run on any BOINC less than 7.6.2 so the BOINC 7.4.44 is not usable for that project.

Follow all instructions for checking dependencies. Install the libwebkitgtk-1.0-0 package and the libcurl3 package. Make sure that boinc and boincmgr have the "allow executing as program" checked in the file permissions. Double click boincmgr, launch the Manager and join the project. Crunch tasks.

. . I have heard that the Gnome interface for Ubuntu slows things down but that may be wrong. Boinc 7.8.3, that was the version I was trying to remember. I plan to go with 7.8.3 and Cuda 9.0. Are ALL the dependencies covered in the CUDA90 package? I am making a list of all the things I need to do to try and avoid missing anything ...

Stephen

. .

Yes, the Ryzens can all do AVX2. I however did extensive benchmark testing of the AVX vs. AVX2 vs. the SSE41 apps and decided that the SSE41 was consistently fastest across all tasks types. Which I must state was when we still got Arecibo regularly. The mix has changed now and Arecibo is rare these days. I even decided the SSE41 was better on my Intel than either of the AVX apps. Juan decided just the opposite on his Intel with his benchmarking. All I can suggest is you do your own testing. Either in real time on current tasks or use current tasks in the offline benchmark app.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

. . I have heard that the Gnome interface for Ubuntu slows things down but that may be wrong. Boinc 7.8.3, that was the version I was trying to remember. I plan to go with 7.8.3 and Cuda 9.0. Are ALL the dependencies covered in the CUDA90 package? I am making a list of all the things I need to do to try and avoid missing anything ...

Stephen

. .

Gnome is the heaviest of display managers but I don't find it particularly slow at any time. There are others that are considered lighter in resource use. You can always change to some different display manager by installing it. Use the same instructions for 7.4.44 with 7.8.3. It will have the same missing dependencies that TBar mentioned in the message for 7.4.44. You WILL have to install both libwebkitgtk-1.0-0 and libcurl3 packages. That normally satisfies both boinc and boincmgr. You can always double check with a Terminal and the ldd command. Open a Terminal and type ldd and a space. Open the Boinc folder and drag and drop boinc into the Terminal window. Make the Terminal window have focus and hit Enter. The ldd command will print out any missing dependencies at the very beginning of the list of dependencies. Do the same with the boincmgr file. If you install the libwebkitgtk and libcurl packages you should have no missing dependencies and BOINC is ready to run. Unpack the CUDA9 special app and copy all its contents into the setiathome.berkeley.edu folder you create in the projects folder you create. Double click boincmgr and join the project and get the normal BOINC startup files and download new tasks and start crunching.

Of course you need to be running the Nvidia drivers already. Either install the main repository 390 drivers or install the graphics-drivers ppa which will get you the latest short term release 396 drivers. When Petri and TBar finally release the static loaded library 1.0 version of the special app, it will require the minimum of the 396 drivers.
Ubuntu Now Has An Official PPA For Graphics Drivers

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Yes, the Ryzens can all do AVX2. I however did extensive benchmark testing of the AVX vs. AVX2 vs. the SSE41 apps and decided that the SSE41 was consistently fastest across all tasks types. Which I must state was when we still got Arecibo regularly. The mix has changed now and Arecibo is rare these days. I even decided the SSE41 was better on my Intel than either of the AVX apps. Juan decided just the opposite on his Intel with his benchmarking. All I can suggest is you do your own testing. Either in real time on current tasks or use current tasks in the offline benchmark app.

. . Even in Lunatics they note that SSE4.2 seems to be better on AMD chips than AVX. So I guess I will go with that and see. I can always try AVX later if I am unhappy with it.

. . BTW, I had decided to go with Lubuntu but the installation crashed and even the bug report failed. So the decision was made for me, Ubuntu it is. <shrug>

. . Damn, Murphy's Law is my bible! Ubuntu install also crashed, but at least the bug report worked this time. Instead of installing to a flash drive like the other two systems I decided to put it on an SSD. Seems not to be ... OK another Flashdrive install then.

Stephen

:)

I just installed Lubuntu and the "Special Sauce"/CUDA90 on my Win10. It is a dual-boot arrangement. Yes the gpu tasks are running almost 50% less time. (7 odd min vs. 4 odd min).

All the install discussion was in the 16c/32t thread.

It sounds like I should move over here though.

1) What is the equivalent of TThortle under Linux?
2) I installed the "alternate" Nvidia drivers and it seems to be working. Should I have left in the "original" X-server drivers?
3) The screen is "wavy" when I scroll. I am running two gtx 1060 3GB cards. Is there a way to fix this?
4) I have already put in an app_config.xml file so that I have 1 core driving each card.
Should I be looking for the equivalent of the "MB*Sog.txt" command file so I can put in my Nvidia parameters? Or was that taken care of in the "app_info.xml" file that came with the "special sauce" setup?

Thank you,
Tom

1) No similar utility like TThrottle in Linux for gpu use. Cpus are limited by their own design and system governors. You can use nvidia-smi for power limit control of the gpu. Example power limit set to 85%.

nvidia-smi -pm 1 # enable persistance mode
nvidia-smi -pl 85

2) The original Nouveau drivers are always installed and can be reverted to at any times. The Nouveau drivers will not allow compute on any gpu. Not usable for crunching.

3) There shouldn't be any 'waviness' Sounds like the card or monitor were not interrogated for correct horizontal and vertical drive frequencies. Or the gpu is set for incorrect screen resolution. Run xrandr in Terminal to set custom screen resolution. Or insufficient power supply to drive two 1060's.

4) No special tuning options for the special app. It determines the best settings automatically for every card type. You can put the -nobs option into the command line in either the app_info or your app_config.<cmdline>-nobs</cmdline> This will use one full cpu core for each gpu task and speed up calculation by 10-15%.

#3 sounds like a Driver issue. The waviness could be caused by the Screen Acceleration not working correctly. I don't know how you're connecting to the monitor, but, sometimes I've noticed strange behavior with some New GPUs when using the DVI connection. Using the HDMI connection instead solved the problem. If that doesn't work you might need a different driver. I always used the download from nVidia except when that one didn't work once or twice...it usually works the best. If you can't get it working I'll go through the steps for installing the driver from Recovery mode, which seems to be the easiest for installing the DL from NV.

I think 10-15% using -nobs is stretching it a bit, at least on my GPUs. On mine it's much less of a speedup.

I needed to move my Gtx 1060's cards off the current machine in preparation to move them onto a larger/faster motherboard.

I installed a couple of GTX 750Ti's. They have been running Seti@Home forever. Boinc doesn't consider the gpu's to be "useable".

I have tried removing and then re-installing the Seti@Home via Bonic Manager. I re-ran the "setup" and then re-copied the CUDA90 files into the seti@home project folder.

I have tried to update the video drivers through the "update software" program.

What am I missing? I don't really want to reload Lubuntu with the "new" video cards in place to "fix" everything but I guess I will if no one has a better idea.

:(

Thank you.
Tom

---

A proud member of the OFA (Old Farts Association).

I needed to move my Gtx 1060's cards off the current machine in preparation to move them onto a larger/faster motherboard.

I installed a couple of GTX 750Ti's. They have been running Seti@Home forever. Boinc doesn't consider the gpu's to be "useable".

I have tried removing and then re-installing the Seti@Home via Bonic Manager. I re-ran the "setup" and then re-copied the CUDA90 files into the seti@home project folder.

I have tried to update the video drivers through the "update software" program.

What am I missing? I don't really want to reload Lubuntu with the "new" video cards in place to "fix" everything but I guess I will if no one has a better idea.

:(

Thank you.
Tom

What is meant by "unuseable"? What does the Event Log say?

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)