I see petri33 is using Cuda 9.20 special of the 0.97b1 app, since all my cards are 10x0 wouldn't that be better than the Cuda 9.10 special posted by TBar?

. . The apps posted by Petri need a very late release of the libstdc++.so.6 libraries and must have the GLIBCXX_3.4.20 and GLIBCXX_3.4.21 extensions or they will not run, as I found out the hard way :) The package posted by TBar will run on probably any system with Linux 4.04.1 kernel or better. It certainly does on mine.

Stephen

:)

yes i think there needs to be more clarity about what version is what and what impacts they have.

is v0.97b1 any faster than v0.97?
does v0.97b1 include support for cards down to CC 5.0?

i know there are 2 versions of v0.97, one for multi SM and one for only 10x0 cards. but the multi sm version is significatly slower. so i've actually been using a version of v0.96 on my machine with 750tis and 1060s because it is still faster to throw away a few jobs that only take 5s to run, vs adding 25-30% to my total run times for every job.

also this thread needs some heavy cleaning in general.
all updated info needs to be added to the OP, or create a new sticky thread that can be managed by someone.
the existing sticky for "optimized" app, only lists windows lunatics builds, and stops at v0.43, there has to be a better way
it's a very common problem here to have information either missing to lost members, or scattered throughout a multi-hundred post thread such as this one.
combining all recent info into a single thread would make the life of everyone easier, especially newcomers that "dont know what they dont know"

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

yes i think there needs to be more clarity about what version is what and what impacts they have.

also this thread needs some heavy cleaning in general.
all updated info needs to be added to the OP, or create a new sticky thread that can be managed by someone.
the existing sticky for "optimized" app, only lists windows lunatics builds, and stops at v0.43, there has to be a better way
it's a very common problem here to have information either missing to lost members, or scattered throughout a multi-hundred post thread such as this one.
combining all recent info into a single thread would make the life of everyone easier, especially newcomers that "dont know what they dont know"

. . So, are you applying for the job ? :)

. . Personally I would recommend starting a new thread and trying to keep it up to date and relevant. But since no one can delete messages and only moderators can hide messages, good luck trying to keep it lean and tidy.

. . Another approach is if you are scrounging through the older messages and find something that is relevant but needs updating, quote it to bring it to the top of the thread and edit it to make it up to date.

Stephen

:)

@ all who have experienced problems installing Ubuntu/Lubuntu 18.04 in UEFI BIOS machines.

. . I have been offered many suggestions that didn't pan out and read several solutions that involved ridiculously complicated programming and manipulation (and may or may not actually work) but the solution is ssooooooo simple and I finally found a post that provided it.

. . If you boot the "Ubuntu Live Disk" in UEFI mode then you will have trouble making the installation bootable, getting a GRUB error about not being able to find /target/. Instead, when you are going to install, first enter the BIOS Setup mode and open the boot menu; find the listings for the 'Live' disk and there will be 2 of them, one marked UEFI and one not. Select the non-UEFI listing to boot and then proceed as normal, and bobs-your-uncle, a nice new bootable Ubuntu installation.

. . Way to go ...

Stephen

:)

@ all who have experienced problems installing Ubuntu/Lubuntu 18.04 in UEFI BIOS machines.

. . I have been offered many suggestions that didn't pan out and read several solutions that involved ridiculously complicated programming and manipulation (and may or may not actually work) but the solution is ssooooooo simple and I finally found a post that provided it.

. . If you boot the "Ubuntu Live Disk" in UEFI mode then you will have trouble making the installation bootable, getting a GRUB error about not being able to find /target/. Instead, when you are going to install, first enter the BIOS Setup mode and open the boot menu; find the listings for the 'Live' disk and there will be 2 of them, one marked UEFI and one not. Select the non-UEFI listing to boot and then proceed as normal, and bobs-your-uncle, a nice new bootable Ubuntu installation.

. . Way to go ...

Stephen

:)

I thought that this was so obvious, I didn't bother mentioning it as I assumed everyone would know how to enter BIOS and select the Override boot target.

---

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

A proud member of the OFA (Old Farts Association)

@ all who have experienced problems installing Ubuntu/Lubuntu 18.04 in UEFI BIOS machines.

. Instead, when you are going to install, first enter the BIOS Setup mode and open the boot menu; find the listings for the 'Live' disk and there will be 2 of them, one marked UEFI and one not. Select the non-UEFI listing to boot and then proceed as normal, and bobs-your-uncle, a nice new bootable Ubuntu installation.

. . Way to go ...

Stephen

:)

I thought that this was so obvious, I didn't bother mentioning it as I assumed everyone would know how to enter BIOS and select the Override boot target.

. . Coulda, shoulda ...

. . The critical thing is not knowing how to enter BIOS to change something but knowing that making that selection will get you past the 18.04 bug with UEFI installs. With the previous discussions of the problem I am surprised no one simply said that.

Stephen

:(

Yes, thought of mentioning it earlier to Raistmer but I assumed he being a developer, his knowledge level was way past me. Plus, I only know what a ASUS BIOS looks like. And other manufacturer BIOS' often don't have nearly the same kind of fine controls that ASUS boards do. So the boot target override may not be available to everyone on all the different systems.

---

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

A proud member of the OFA (Old Farts Association)

Just going to mention that the latest Nvidia short term release is up in the ppa repositories for download and install via your favorite method. Was supposed to plug a long running resource leak in the drivers and supposedly faster for graphics. No idea yet whether that is true of compute. Just installed them. I also am trying out TBar's latest special 0.97b1 app.

Don't know which if any thing has caused the change, rebooting the system, changing graphics drivers or the special application, but my cpu utilization has dropped significantly from 75-80% down to 50%. Not enough tasks done yet with the new app to say it is faster or slower yet.

[Edit]Cpu usage mystery solved. For some reason restart of BOINC didn't pick up my command line nobs parameter in app_config even though app_config was read in Event Log.

Added -nobs to the command line in app_info and will restart and see if it gets picked up there.

---

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

A proud member of the OFA (Old Farts Association)

yes i think there needs to be more clarity about what version is what and what impacts they have.

also this thread needs some heavy cleaning in general.
all updated info needs to be added to the OP, or create a new sticky thread that can be managed by someone.
the existing sticky for "optimized" app, only lists windows lunatics builds, and stops at v0.43, there has to be a better way
it's a very common problem here to have information either missing to lost members, or scattered throughout a multi-hundred post thread such as this one.
combining all recent info into a single thread would make the life of everyone easier, especially newcomers that "dont know what they dont know"

. . So, are you applying for the job ? :)

. . Personally I would recommend starting a new thread and trying to keep it up to date and relevant. But since no one can delete messages and only moderators can hide messages, good luck trying to keep it lean and tidy.

. . Another approach is if you are scrounging through the older messages and find something that is relevant but needs updating, quote it to bring it to the top of the thread and edit it to make it up to date.

Stephen

:)

i'd absolutely update it if i had access to edit the OP.

i dont want to delete all the thread content. i just want all the up to date content added to the first post of this whole thread.

or a sticky thread that only has a single post, locked topic, as a repository for all the current information and links to the apps (lots of old links out there, some work some dont)

that way when someone clicks this, they dont get outdated info. say someone new to seti reads this thread, they start at the beginning and start downloading all the old links (which may or may not even work anymore), and they start running cuda80 apps. that's a waste of time when they should be skipping all that to begin with.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

Hi all,
I think I managed to have Xorg on the Intel iGPU and CUDA on Nvidia.

It costed me yet another OS reinstall, though... and 70 trashed WUs (could be worse) and yet another Computer ID. I hope they will be the last. Proper back-up will help.

In any case:

- To be safe, remove your nVidia card and install your flavour of Ubuntu (and possibly any Linux). This may be overkill, but I will not try again without removing the card, unless with a loaded gun at my head.

- Shutdown and replace the card.

- Follow the installation of nVidia drivers and CUDA as in:
https://gist.github.com/alexlee-gk/76a409f62a53883971a18a11af93241b

You will also need to blacklist the Nouveau drivers before installation:
https://linuxconfig.org/how-to-disable-nouveau-nvidia-driver-on-ubuntu-18-04-bionic-beaver-linux

This will leave you without GL capabilities, though. This means that if you need those at times and iGPU is not enough for you and you want to use the full capabilities of your nVidia card from time to time, you are out of luck with this method.
But if you are running the card just for Seti, unconnected, you will not even notice this problem.
Otherwise, you can still go the standard way, switching off Boinc when needed in one of the many possible ways.
Also, nVidia drivers will not automatically update, I think. But at the moment I cannot still decide if this is a bug or a feature.

- I found no need to edit xorg.conf.
' Been there, done that with no avail and plenty of havocs earlier, anyway. :-(

Done.

My nvidia-smi output:

+-----------------------------------------------------------------------------+
| NVIDIA-SMI 396.54                 Driver Version: 396.54                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 106...  Off  | 00000000:01:00.0 Off |                  N/A |
| 44%   63C    P2    78W / 120W |   1843MiB /  3019MiB |     90%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|    0     18308      C   ...e.berkeley.edu/setiV0.97.linux_x64_10x0  1833MiB |
+-----------------------------------------------------------------------------+

Now the use of my PC is smooth again and I can push my 1060 as much as she can stand.

As always, your mileage may vary, but it is working for me, until next epic crash.

Good night and good luck.

Sleepy

Thanks for the update, Sleepy. Happy to hear you finally got it working the way you wanted. I think that blacklisting the Nouveau drivers beforehand is unnecessary because the Nvidia drivers normally blacklist the Nouveau drivers on first installation anyway. But doing that step beforehand won't hurt anyway. I think the trick you discovered was the initial Ubuntu install just on the embedded iGPU drivers with no Nvidia card installed.

---

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

A proud member of the OFA (Old Farts Association)

yes i think there needs to be more clarity about what version is what and what impacts they have.

also this thread needs some heavy cleaning in general.
all updated info needs to be added to the OP, or create a new sticky thread that can be managed by someone.
the existing sticky for "optimized" app, only lists windows lunatics builds, and stops at v0.43, there has to be a better way
it's a very common problem here to have information either missing to lost members, or scattered throughout a multi-hundred post thread such as this one.
combining all recent info into a single thread would make the life of everyone easier, especially newcomers that "dont know what they dont know"

. . So, are you applying for the job ? :)

. . Personally I would recommend starting a new thread and trying to keep it up to date and relevant. But since no one can delete messages and only moderators can hide messages, good luck trying to keep it lean and tidy.

. . Another approach is if you are scrounging through the older messages and find something that is relevant but needs updating, quote it to bring it to the top of the thread and edit it to make it up to date.

Stephen

:)

i'd absolutely update it if i had access to edit the OP.

i dont want to delete all the thread content. i just want all the up to date content added to the first post of this whole thread.

or a sticky thread that only has a single post, locked topic, as a repository for all the current information and links to the apps (lots of old links out there, some work some dont)

that way when someone clicks this, they dont get outdated info. say someone new to seti reads this thread, they start at the beginning and start downloading all the old links (which may or may not even work anymore), and they start running cuda80 apps. that's a waste of time when they should be skipping all that to begin with.

Kinda hard on BOINC forums. How about making new threads? I mean this thread has CUDA80 in the title which is how many versions old by now? Let old threads with old info die.

Kinda hard on BOINC forums. How about making new threads? I mean this thread has CUDA80 in the title which is how many versions old by now? Let old threads with old info die.

Now how about a spiffy new name?

Like "Setting up a Linux machine to crunch CUDA90 and CUDA90+ for Windows users"?

It has a certain ring to it :)

I have posted my "how to" on the questions and answers forum for Linux/Unix users where a moderator promptly made it a sticky.

Tom

---

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

I'd suggest people just Download the App from Crunchers Anonymous and Read the README.
That's usually the way things work.
As Far as What the App does, well it runs CUDA, on most recent versions of Linux, with the GPUs listed in the README, sorta like the previous version.
If you want to now how fast it is I suggest you download it and Test it.
Of course, since it's stated it produces More Correct Results than the Previous versions, I would hope people would do the project a favor and select the one producing the Best Results. Which is Kinda why I posted it.

Yes, thought of mentioning it earlier to Raistmer but I assumed he being a developer, his knowledge level was way past me. Plus, I only know what a ASUS BIOS looks like. And other manufacturer BIOS' often don't have nearly the same kind of fine controls that ASUS boards do. So the boot target override may not be available to everyone on all the different systems.

. . Using ASUS mobos myself I can only guess what is in the BIOS setup on other brands.

Stephen

:)

Kinda hard on BOINC forums. How about making new threads? I mean this thread has CUDA80 in the title which is how many versions old by now? Let old threads with old info die.

Stephen is the originator of the thread. He alone can make the change to the thread title. I agree, the title could be changed to something more generic, like, "Setting up a Linux machine to crunch the CUDA special app for Windows users"

---

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

A proud member of the OFA (Old Farts Association)

If you mention CUDA Special and Windows in the same sentence, the first post will be ... I just trashed all my work units. Why?

If you mention CUDA Special and Windows in the same sentence, the first post will be ... I just trashed all my work units. Why?

Probably true, sadly. As stated previously, the only way a Windows user should be exposed to the special app is through a native Windows application either as the stock app from Main or through an updated Lunatics installer.

---

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

A proud member of the OFA (Old Farts Association)

If you mention CUDA Special and Windows in the same sentence, the first post will be ... I just trashed all my work units. Why?

Agreed, windows should not appear anywhere in the same sentence. Give wrong impression. More like, those wanting to switch from Windows to Linux.

If you mention CUDA Special and Windows in the same sentence, the first post will be ... I just trashed all my work units. Why?

Agreed, windows should not appear anywhere in the same sentence. Give wrong impression. More like, those wanting to switch from Windows to Linux.

this.

when i first came upon this thread, i thought this thread was somehow explaining how to take jobs from a windows machine and redistribute them to a linux machine for processing. like "hey Windows, i'm Linux, let me do that for you"

when it doesn't mean that at all lol.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours