Greetings

Woohoo Keith, excellent news to hear.

Whats next, getting one of your dual 1070 machines over onto the Cuda special app lol.

Regards
Mark

. . When he sees the results he will get with 3x GTX970s I think the others will follow suit before too long :)

Stephen

:)

Maybe on Pipsqueek .... defininitely NOT my daily driver. And probably not on Numbskull, the Win10 system since I am still evaluating Windows 10. I like it in a lot of ways but I also don't like the heavy-handed way M$ goes about maintaining it on my system.

What I should do is use one of the systems as a test bed for evaluating all the various linux desktop GUIs to see which one I like the best by using the test run in place installations.

. . Hi Keith,

. . Like you I favour continuing with Windows on the 'daily driver'. And like you I really love the user parts of Win10, it is a great OS, but also like yourself the way 'big brother' M$ goes about administering the system ( user tracking and privacy invasion) and updates really gets up my nose. Since using Win10 I have spoken their name frequently, almost always surrounded by a cloud of invectives that would make a sailor blush. Especially the way they trash the working Nvidia video drivers by replacing them with their own crappy versions.

. . I also have contemplated experienting with the various Linux GUIs to find the most comfortable one for my liking. I may yet get around to it.

Stephen

:)

Win 10 on the Ryzen system has been rock solid ... at least with regard the OS. I had a lot of 'teething' issues with the Ryzen hardware and it took a long time to get the hardware stable. If you don't try to push the hardware too far beyond its comfort zone, it will reward you with a very capable and trouble-free system.

I had only one time that Win10 updated the video drivers on me without asking and fortunately without consequence since they had OpenCL support which is not the norm from all the forum posts about the opposite occurring most of the time. O&O Shutup has taken care of most of my privacy concerns. Since it is just a cruncher and not a daily driver, I just let it run and have very little interaction with it.

I may revisit Mint or Ubuntu Mate looks interesting. There are so many flavors of linux out there, that could be a year long project for evaluations. This is just the beginning of my Linux education. I should hope to be as knowledgeable as Dallasdawg, Tbar and the others that have helped in this thread, in 5 years if I keep tinkering.

---

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

A proud member of the OFA (Old Farts Association)

Oh yes, yet another new build with the same old warts;

Sun 23 Jul 2017 10:22:49 PM EDT | | Starting BOINC client version 7.8.0 for x86_64-pc-linux-gnu
Sun 23 Jul 2017 10:22:49 PM EDT | | Data directory: /home/tbar/BOINC
Sun 23 Jul 2017 10:22:50 PM EDT | | CUDA: NVIDIA GPU 0: GeForce GTX 1050 (driver version 381.22, CUDA version 8.0, compute capability 6.1, 1991MB, 1651MB available, 1976 GFLOPS peak)
Sun 23 Jul 2017 10:22:50 PM EDT | | CUDA: NVIDIA GPU 1: GeForce GTX 1050 (driver version 381.22, CUDA version 8.0, compute capability 6.1, 1999MB, 1950MB available, 1960 GFLOPS peak)
Sun 23 Jul 2017 10:22:50 PM EDT | | OpenCL: NVIDIA GPU 0: GeForce GTX 1050 (driver version 381.22, device version OpenCL 1.2 CUDA, 1991MB, 1651MB available, 1976 GFLOPS peak)
Sun 23 Jul 2017 10:22:50 PM EDT | | OpenCL: NVIDIA GPU 1: GeForce GTX 1050 (driver version 381.22, device version OpenCL 1.2 CUDA, 1999MB, 1950MB available, 1960 GFLOPS peak)
Sun 23 Jul 2017 10:22:50 PM EDT | | OS: Linux Ubuntu: Ubuntu 16.04.2 LTS [4.8.0-58-generic]

Just Compiled in Ubuntu 12.04.5 with static wxWidgets 3.0.3 Libraries. Works like a charm in 12.04.5 and 16.04.2, if it weren't for those warts.
Should I post for those that don't care about Warts, or throw it in the trash with all the others. The trash is getting full.
I suppose if you just clicked on that Show active tasks button you wouldn't see the warts.
I know they're there though ;-)

I finally did it. I tried setting up the current release of LUbuntu (Light Ubuntu) for Boinc/SetiBeta using the bonic installs for manager/client via the Package manager.

Even got a full set of SetiBeta cpu tasks downloaded and processing. Then I started mucking around with trying to get the gpu recognized.

Thud. Now it won't even boot.

Fortunately it was pretty painless to set it up on the flashdrive. So I will rebuild everything and confirm it works for the cpu's again.

Then I will re-read the thread looking for pointers/ideas.

Will see.

I have one proposal. This thread needs to be segmented into separate threads for each flavor of Linux. Because each one is "different."

Tom

---

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

Just a question about an anomaly that I see from your last post. Not important evidently on my system. Why do you show a driver version for both CUDA and OpenCL? But I don't. I normally see driver versions for both platforms on my Windows systems.

Sun 23 Jul 2017 12:27:20 AM PDT |  | CUDA: NVIDIA GPU 0: GeForce GTX 970 (driver version unknown, CUDA version 9.0, compute capability 5.2, 4034MB, 3843MB available, 6385 GFLOPS peak)
Sun 23 Jul 2017 12:27:20 AM PDT |  | CUDA: NVIDIA GPU 1: GeForce GTX 970 (driver version unknown, CUDA version 9.0, compute capability 5.2, 4037MB, 3965MB available, 6385 GFLOPS peak)
Sun 23 Jul 2017 12:27:20 AM PDT |  | CUDA: NVIDIA GPU 2: GeForce GTX 970 (driver version unknown, CUDA version 9.0, compute capability 5.2, 4037MB, 3965MB available, 6385 GFLOPS peak)
Sun 23 Jul 2017 12:27:20 AM PDT |  | OpenCL: NVIDIA GPU 0: GeForce GTX 970 (driver version 384.47, device version OpenCL 1.2 CUDA, 4034MB, 3843MB available, 6385 GFLOPS peak)
Sun 23 Jul 2017 12:27:20 AM PDT |  | OpenCL: NVIDIA GPU 1: GeForce GTX 970 (driver version 384.47, device version OpenCL 1.2 CUDA, 4037MB, 3965MB available, 6385 GFLOPS peak)
Sun 23 Jul 2017 12:27:20 AM PDT |  | OpenCL: NVIDIA GPU 2: GeForce GTX 970 (driver version 384.47, device version OpenCL 1.2 CUDA, 4037MB, 3965MB available, 6385 GFLOPS peak)

---

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

A proud member of the OFA (Old Farts Association)

I finally did it. I tried setting up the current release of LUbuntu (Light Ubuntu) for Boinc/SetiBeta using the bonic installs for manager/client via the Package manager.

Even got a full set of SetiBeta cpu tasks downloaded and processing. Then I started mucking around with trying to get the gpu recognized.

Thud. Now it won't even boot.

Fortunately it was pretty painless to set it up on the flashdrive. So I will rebuild everything and confirm it works for the cpu's again.

Then I will re-read the thread looking for pointers/ideas.

Will see.

I have one proposal. This thread needs to be segmented into separate threads for each flavor of Linux. Because each one is "different."

Tom

. . The original thread was Linux as proposed by TBar (Ubuntu 14.04.05 LTS with the Berkeley BOINC version). The objective being a simple installation free of hassles and relatively friendly to Windows users so they can be productive without too much stress. LOL. Well it does seem to have sparked a good deal of interest but seems to have failed with the hassle free part of the objective. I guess Linux has a long way to go before it reaches that plateau.

. . But there are now more Linux machines with increased productivity so that part is good.

Stephen

:)

It's as was said earlier, the newer versions of BOINC still have bugs but they do solve some older bugs as well. The version you're running is an older version that doesn't have one particularly annoying bug, but it has other bugs. The not showing the Driver version bug was fixed somewhere around 7.4.xx. There are a few new features in the newer version that aren't in the older versions. This version doesn't have any trouble Stopping boinc in 16.04.2, while even the 7.4.53 build has problems with stopping in the newest OS versions.

BOINC 7.8 is posted here; http://www.arkayn.us/forum/index.php?topic=197.msg4519#msg4519

The Latest version of BOINC for Testing in Linux. You should check the Dependencies and Execute bits before running. This version should work in Ubuntu 12.04 and above without any additional packages, however, Mint users will need to install libcurl3 from the Package Manager. This version has the same BOINC Manager Tasks view problem as all the newer versions, the View in the Tasks tab will be focused on the bottom of the page. Select Show active tasks to keep active tasks in view. This version will Stop boinc in newer Linux versions by simply Exiting the BOINC Manager.
To expand the 3 files in Linux you need to have 7zip installed, double click the first file and Archive Manage will combine the 3 parts automatically.

The BOINC 7.8 folder will have the same files as in the Berkeley Downloads. If you already have a BOINC folder in your Home folder, Stop BOINC and copy the 5 executable files in BOINC_7.8 and paste them into your existing BOINC folder. You will need to Stop all running versions, including boinc, before pasting the files into your existing folder. To start BOINC, double click on boincmgr, if it doesn't start, check the Execute bit and Dependencies.

I'll give your new BOINC a tryout today, TBar. Thanks for being a developer.

---

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

A proud member of the OFA (Old Farts Association)

It doesn't start. I stopped both BOINC and BOINC Manager and the rebooted. Upon restart I checked System Monitor to make sure neither BOINC or BOINC Manager were not running. I copied the new executables from the BOINC_7.8 folder into my existing BOINC_7.2.47 folder. I checked all five new files that the executable was set. Double-clicked on BOINC Manager and nothing happens. I checked System Monitory and neither BOINC nor BOINC Manager are running.

Ideas for a quick fix. Or do I download the BOINC_7.2.47 files again and reinstall?

---

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

A proud member of the OFA (Old Farts Association)

I tried one more time with a complete reboot again. New BOINC_7.8 files won't run. Another interesting fact is when I drop either BOINC or BOINC Manager on the Terminal with ldd, there is no directory found for BOINC and BOINC Manager shows a missing library.

keith@Darksider:~$ ldd'/home/keith/Desktop/BOINC_7.8/boinc' 
bash: ldd/home/keith/Desktop/BOINC_7.8/boinc: No such file or directory
keith@Darksider:~$ ldd '/home/keith/Desktop/BOINC_7.8/boincmgr' 
	linux-vdso.so.1 =>  (0x00007ffc6bf1d000)
	libwebkitgtk-1.0.so.0 => not found

---

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

A proud member of the OFA (Old Farts Association)

Check the Dependencies again. Open a Terminal, type ldd and a space, then drag and drop boincmgr into the window. Click on the Terminal window and hit enter. If you don't have any missing files, type cd and a space into the Terminal, then drag and drop the BOINC_7.2.47 folder into the window and hit enter. This will change the directory to your BOINC folder. Type ./boincmgr into the Terminal and hit enter, see what the remarks say.

libwebkitgtk-1.0.so.0 => not found

Hmmm, open the Package Manager and search for and install libwebkitgtk
Then run the ldd again. Strange Mint didn't complain about libwebkitgtk, I suppose Mint has it installed already.

Thanks TBar, making the BOINC_7.8 directory local in Terminal solved the issue of ldd reading BOINC. Installed the libwebkitgtk-1.0 package and ran ldd against BOINC Manager again and it came back with all the libraries found. Clicked on BOINC Manager and it came up with BOINC 7.8 in Help/About.

Nice to get back to Menus that I am used to in 7.6.33. I always run with Show Active Tasks so the bouncing Tasks list shouldn't bother me.

---

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

A proud member of the OFA (Old Farts Association)

Quick question guys, following this thread with interest, hopefully will soon have time to reinstall Mint, and noticed a few posts up that someone had mentioned Mint 18.3. I thought Hmm, that's a new one, as 18.2 was just released recently, was there already a point update for it so soon? Took a quick Google around, and couldn't find any .3 version, so was that reference a typo possibly?

---

I finally did it. I tried setting up the current release of LUbuntu (Light Ubuntu) for Boinc/SetiBeta using the bonic installs for manager/client via the Package manager.

Even got a full set of SetiBeta cpu tasks downloaded and processing. Then I started mucking around with trying to get the gpu recognized.

Thud. Now it won't even boot.

Fortunately it was pretty painless to set it up on the flashdrive. So I will rebuild everything and confirm it works for the cpu's again.

Then I will re-read the thread looking for pointers/ideas.

Well the good news is I have the current release of Lubuntu installed, Nvidia drivers for a GT 720 installed, Boinc-client installed, Boinc-Manager installed and Boinc/SetaBeta is crunching along happily with CUDA 60 humping along too. All w/o using a terminal. I installed "everything" through the GUI's of Lubuntu including the Nvidia drivers, the Boinc pieces and updating the Lubutu I had to a current version. The ISO had about 195MB of updates needed.

So I got my Z600 running (with a dual boot) Lubuntu.

Now I have to re-read the thread and begin to understand how/where to put the app/where I get the app from, to upgrade to the CUDA 80. aka: "secret sauce".

And if necessary replace the GT 710 with a GTX 750 Ti if the CUDA 80 gets cranky.

Tom

---

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

Quick question guys, following this thread with interest, hopefully will soon have time to reinstall Mint, and noticed a few posts up that someone had mentioned Mint 18.3. I thought Hmm, that's a new one, as 18.2 was just released recently, was there already a point update for it so soon? Took a quick Google around, and couldn't find any .3 version, so was that reference a typo possibly?

Hi Al, no it was a typo by Brent. Latest and greatest is Mint 18..2

---

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

A proud member of the OFA (Old Farts Association)

Yes, 18.3 was a mistake on my part sorry :(
18.2 is the one to install.

Oh, no worries, I was just thinking maybe the quick point release squashed some critical bugs, but I'm not yet familiar on how Mint/Linux does it's updates, I've been spoiled by the ease of Windows Updates for so long now. Although the interesting decisions MS has made the last couple years on forced updates and other nefarious activities (see the massive Windows 10 - Yea or Nay? for MUCH more discussion on these topics and many more) has me questioning the advantage of this ease. I believe I tried 10 once, about a year or so ago, and that lasted I think for about 30 minutes before the drive was wiped and I have never let it's dark, hideous shadow cross the path of any of my computes since. And hopefully never will (we'll see when 2020 comes, as I remember XP's slow death, but MS seems to have learned from that one, sadly). Now if only Linux could take the good parts from it 3-4 or more years ago a implement it somehow, they would be Golden!

---

Hope that Petri or Jeff can point out where I'm going astray with my gpu fan control/memory offset script.

Fan control is working fine and automatically gets set to my desired 100% fan speed.

What isn't working is trying to get the cards to work at full memory speed in P2 power state. I do that in Windows with Nvidia Inspector. I looked at Petri's examples and thought it looked simple enough. I did get it to apply the offset in P3 state when I set it for an offset of 500, I ended up with a memory clock in Nvidia Settings of 7510 Mhz for P3.

But as soon as I started BOINC and got gpu tasks running, Nvidia Settings showed me in the normal P2 state with memory at the normal 6008 Mhz. So thinking I understood the command syntax, this is what I wrote.

#!/bin/bash
/usr/bin/nvidia-smi -pm 1

/usr/bin/nvidia-settings -a "[gpu:0]/GPUFanControlState=1" -a [fan:0]/GPUTargetFanSpeed=100
/usr/bin/nvidia-settings -a "[gpu:1]/GPUFanControlState=1" -a [fan:1]/GPUTargetFanSpeed=100
/usr/bin/nvidia-settings -a "[gpu:2]/GPUFanControlState=1" -a [fan:2]/GPUTargetFanSpeed=100

/usr/bin/nvidia-settings -a "[gpu:0]/GPUMemoryTransferRateOffset[2]=1000"
/usr/bin/nvidia-settings -a "[gpu:1]/GPUMemoryTransferRateOffset[2]=1000"
/usr/bin/nvidia-settings -a "[gpu:2]/GPUMemoryTransferRateOffset[2]=1000"

Can someone show me where I've gone wrong? TIA.

---

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

A proud member of the OFA (Old Farts Association)