Setting up Linux to crunch CUDA90 and above for Windows users

Message boards : Number crunching : Setting up Linux to crunch CUDA90 and above for Windows users
Message board moderation

To post messages, you must log in.

Previous · 1 . . . 75 · 76 · 77 · 78 · 79 · 80 · 81 . . . 162 · Next

AuthorMessage
RickToTheMax

Send message
Joined: 22 May 99
Posts: 105
Credit: 7,958,297
RAC: 0
Canada
Message 1956555 - Posted: 20 Sep 2018, 22:45:46 UTC - in response to Message 1956550.  


On another note, damn i like Kubuntu 18.04 alot! KDE plasma is now quite polished and is pretty light in resources usage (at least compared to old KDE/Gnome)!
If anyone would like to try that out instead of Ubuntu/Lubuntu, as it is closer to the Windows UI in general. The instruction in here work just fine.
My 2nd system is using KDE Neon (now upgraded to 18.04 as well).


. . Thanks for that tip. I might have a look at that ....

. . A question though, which system is running the KDE Plasma front end? The system with the 1060 says it is running Neon so I guess that is your "2nd system". And is it hard to select either of those desktop options?

Stephen

:)


Both are, KDE Neon is a distro made by the KDE team, that keeps the KDE version on the latest version, it is very similar to kubuntu, and is based on ubuntu too, so very similar..

Other one is running Kubuntu, which i would recommend for people not used to linux too much, as it has more default ubuntu features installed, and the installer is even easier
ID: 1956555 · Report as offensive     Reply Quote
RickToTheMax

Send message
Joined: 22 May 99
Posts: 105
Credit: 7,958,297
RAC: 0
Canada
Message 1956556 - Posted: 20 Sep 2018, 22:46:46 UTC
Last modified: 20 Sep 2018, 22:51:58 UTC

The ryzen system is running a Asrock x370 Killer SLI motherboard..

Not sure it would help if you had problems with Lubuntu or Ubuntu, unless your problem was desktop environment related. If the problem is more hardware related, might want to look into installing the latest kernel maybe..
ID: 1956556 · Report as offensive     Reply Quote
Stephen "Heretic" Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 20 Sep 12
Posts: 5557
Credit: 192,787,363
RAC: 628
Australia
Message 1956564 - Posted: 20 Sep 2018, 23:55:47 UTC - in response to Message 1956555.  


. . A question though, which system is running the KDE Plasma front end? The system with the 1060 says it is running Neon so I guess that is your "2nd system". And is it hard to select either of those desktop options?
Stephen

Both are, KDE Neon is a distro made by the KDE team, that keeps the KDE version on the latest version, it is very similar to kubuntu, and is based on ubuntu too, so very similar..

Other one is running Kubuntu, which i would recommend for people not used to linux too much, as it has more default ubuntu features installed, and the installer is even easier


. . Sold! I will have a look and download it.

Stephen

:)
ID: 1956564 · Report as offensive     Reply Quote
Stephen "Heretic" Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 20 Sep 12
Posts: 5557
Credit: 192,787,363
RAC: 628
Australia
Message 1956565 - Posted: 20 Sep 2018, 23:58:14 UTC - in response to Message 1956556.  

The ryzen system is running a Asrock x370 Killer SLI motherboard..

Not sure it would help if you had problems with Lubuntu or Ubuntu, unless your problem was desktop environment related. If the problem is more hardware related, might want to look into installing the latest kernel maybe..


. . The problems are with the latest kernel, but I am running an ASUS X370 mobo so I am wondering if there is an issue there. AFAIK Keith is running all x470 mobos.

Stephen

? ?
ID: 1956565 · Report as offensive     Reply Quote
RickToTheMax

Send message
Joined: 22 May 99
Posts: 105
Credit: 7,958,297
RAC: 0
Canada
Message 1956625 - Posted: 21 Sep 2018, 10:34:08 UTC - in response to Message 1956565.  

Out of curiosity what issues do you have?
I had to RMA my first R7 1700 because of the segfault problems the early batches had when doing hard computing using multiple thread workloads.
Another problem i think alot of people had is the system crashing when idling, i think this was either a kernel fix or bios fix, can't remember, never had that problem tho.
ID: 1956625 · Report as offensive     Reply Quote
Stephen "Heretic" Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 20 Sep 12
Posts: 5557
Credit: 192,787,363
RAC: 628
Australia
Message 1956698 - Posted: 21 Sep 2018, 23:06:53 UTC - in response to Message 1956625.  

Out of curiosity what issues do you have?
I had to RMA my first R7 1700 because of the segfault problems the early batches had when doing hard computing using multiple thread workloads.
Another problem i think alot of people had is the system crashing when idling, i think this was either a kernel fix or bios fix, can't remember, never had that problem tho.


. . Fortunately (or maybe not) it is neither of those. But I am unable to update the video drivers using the 'recovery mode' method used by TBar. Whenever I try to activate the network in recovery mode the system hangs, goes off into limbo when it gets to the message 'found target: sound card'. That message is in green as OK but it goes no further. If I <ctrl>-c it, whatever has hung ends and it boots into the OS. Also when in the OS double clicking on an icon will not run the app, despite the properties being set to executable and permissions being set to 'anyone'. If I sudo the app in a terminal window it will run, but when I run BOINC it does not start/communicate with boinc-client.

. . Just very frustrating. Others are blaming the problem on Lubuntu itself and recommended using 'full' Ubuntu, but since they are both using the same 18.04 kernel I am not convinced that will be any better; and in keeping with the thread topic I am trying to achieve a setup that will be most comfortable for new Linux users coming from a Windows background. Which is why I am now considering trying Kubuntu but maybe using the 16.04 kernel.

. . This is after having a hell of a time getting the installer to create a bootable Linux installation at all because of the 18.04 UEFI bug in which GRUB fails to create the OS loader if the "live disk" is booted in UEFI mode. It took a couple weeks to find out the solution to that one was just to use the BIOS setup to select the non-UEFI listing to boot the 'live disk' itself.

. . So many traps, so few life times ...

Stephen

:(
ID: 1956698 · Report as offensive     Reply Quote
RickToTheMax

Send message
Joined: 22 May 99
Posts: 105
Credit: 7,958,297
RAC: 0
Canada
Message 1956707 - Posted: 22 Sep 2018, 0:05:49 UTC - in response to Message 1956698.  

Hmm this is wierd indeed..
When i installed kubuntu i'm pretty sure i used UEFI boot mode and it worked just fine (i used rufus to create the bootable iso)
And for the nvidia driver, i used the "driver manager" tool to switch to nvidia driver 390,
then:
- ran the command to add the PPA..
- sudo apt update / sudo apt upgrade
- sudo ubuntu-drivers autoinstall
- sudo apt update / upgrade again, since i had dependencies problems
- sudo ubuntu-drivers autoinstall (another time)
- sudo apt install ocl-icd-libopencl1 libcurl3 p7zip libwebkitgtk-1.0.0

Is the recovery method you talk about is for users running 2 nvidia card? (i only use one so..)
ID: 1956707 · Report as offensive     Reply Quote
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 13161
Credit: 1,160,866,277
RAC: 1,873
United States
Message 1956720 - Posted: 22 Sep 2018, 2:34:02 UTC - in response to Message 1956539.  

Is there any thread i should look into to set up keepP2?
I would guess i need some script of some sort,like i will have to boot at stock clock, and maybe have a script run P2 then apply overclock after right?

No, no special script unless you want to write your own to keep from having to type in the command every time or do the copy/paste thing.. The document file in the zip archive explains the syntax. If running just a single gpu, then it is a simple bash command of ./keepP2 in a Terminal window, then just minimize the window and let it run in the background. If running more than a single gpu just add in each next device in the command.

I normally run 4 bash scripts when I start up the computer for crunching. First is the keepP2 command, then I start with a root Terminal window and run my unrestricted command which sets up the cards for overclocking and fan control. Then I run my overclock script which sets up each card for the desired overclock for each card, sets the fans to 100% and turns down the LED lighting, Finally I run my script which sets the priorities and affinities for each of the cpu and gpu applications I run. Then minimize that window and start up BOINC.

You can search on my posts in this thread for my scripts which I have posted several times or I can PM you the scripts if you are interested.
Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)
ID: 1956720 · Report as offensive     Reply Quote
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 13161
Credit: 1,160,866,277
RAC: 1,873
United States
Message 1956722 - Posted: 22 Sep 2018, 2:37:28 UTC - in response to Message 1956565.  



. . The problems are with the latest kernel, but I am running an ASUS X370 mobo so I am wondering if there is an issue there. AFAIK Keith is running all x470 mobos.

Stephen

? ?

Nope still running my second X370 system too. Though every day I look at it falling further behind the X470 systems, I threaten to pull the plug on it and upgrade it to X470.
Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)
ID: 1956722 · Report as offensive     Reply Quote
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 13161
Credit: 1,160,866,277
RAC: 1,873
United States
Message 1956723 - Posted: 22 Sep 2018, 2:40:19 UTC - in response to Message 1956625.  

Out of curiosity what issues do you have?
I had to RMA my first R7 1700 because of the segfault problems the early batches had when doing hard computing using multiple thread workloads.
Another problem i think alot of people had is the system crashing when idling, i think this was either a kernel fix or bios fix, can't remember, never had that problem tho.

I too RMA'd my first Ryzen 1700X week 1705 chip. The replacement week 1738 chip was a dud though compared to the original with regard to memory and core overclocks. Definitely the original chip was better except for the repeated segfault errors.
Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)
ID: 1956723 · Report as offensive     Reply Quote
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 13161
Credit: 1,160,866,277
RAC: 1,873
United States
Message 1956724 - Posted: 22 Sep 2018, 2:42:58 UTC - in response to Message 1956698.  

. . Just very frustrating. Others are blaming the problem on Lubuntu itself and recommended using 'full' Ubuntu, but since they are both using the same 18.04 kernel I am not convinced that will be any better; and in keeping with the thread topic I am trying to achieve a setup that will be most comfortable for new Linux users coming from a Windows background. Which is why I am now considering trying Kubuntu but maybe using the 16.04 kernel.

There's more going on than just a kernel running. You also have to have a desktop manager running the system. I think your desktop manager has more to do with your issues than any kernel.
Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)
ID: 1956724 · Report as offensive     Reply Quote
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 13161
Credit: 1,160,866,277
RAC: 1,873
United States
Message 1956725 - Posted: 22 Sep 2018, 2:45:56 UTC - in response to Message 1956707.  
Last modified: 22 Sep 2018, 2:46:08 UTC

Is the recovery method you talk about is for users running 2 nvidia card? (i only use one so..)

No, the recovery method is for installing the official Nvidia .run file downloaded directly from Nvidia. Not for installing the drivers from the ppa.
Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)
ID: 1956725 · Report as offensive     Reply Quote
RickToTheMax

Send message
Joined: 22 May 99
Posts: 105
Credit: 7,958,297
RAC: 0
Canada
Message 1956727 - Posted: 22 Sep 2018, 2:57:50 UTC - in response to Message 1956720.  

Thanks i'll search this thread!
ID: 1956727 · Report as offensive     Reply Quote
RickToTheMax

Send message
Joined: 22 May 99
Posts: 105
Credit: 7,958,297
RAC: 0
Canada
Message 1956732 - Posted: 22 Sep 2018, 4:01:29 UTC - in response to Message 1956723.  


I too RMA'd my first Ryzen 1700X week 1705 chip. The replacement week 1738 chip was a dud though compared to the original with regard to memory and core overclocks. Definitely the original chip was better except for the repeated segfault errors.


For me it was quite the opposite, max memory was 2666 and wouldn't overclock past 3.7ghz, new one i could run 3000 and 4ghz. I need to update my bios again, see if i can run higher memory.
But getting the overclock was kinda tricky with the bios and i would have to do it all over again.. I was always having the problem where the clock would go back down to like 1.5ghz when vcore was set to high or something like that..
ID: 1956732 · Report as offensive     Reply Quote
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 13161
Credit: 1,160,866,277
RAC: 1,873
United States
Message 1956735 - Posted: 22 Sep 2018, 4:44:19 UTC - in response to Message 1956732.  

That's a flaw in a really old BIOS. Long since solved in the current BIOS'
Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)
ID: 1956735 · Report as offensive     Reply Quote
Stephen "Heretic" Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 20 Sep 12
Posts: 5557
Credit: 192,787,363
RAC: 628
Australia
Message 1956751 - Posted: 22 Sep 2018, 6:29:29 UTC - in response to Message 1956707.  

Hmm this is wierd indeed..
When i installed kubuntu i'm pretty sure i used UEFI boot mode and it worked just fine (i used rufus to create the bootable iso)

. . That makes Kubuntu sound all the more like the way to go. I also used Rufus to create the 'live disk' but both Ubuntu and Lubuntu with the 18.04 kernel did the same thing.

And for the nvidia driver, i used the "driver manager" tool to switch to nvidia driver 390,

. . I have been able to install the proprietary 390 drivers from the repository using the preference manage but I am concerned that a fundamental function isn't working. With TBar recommending the 'recovery mode' method for installing the necessary video drivers I need to know that the installation I recommend will work with whatever the new user tries to do following the suggestions they will probably see and read. A 'sort of' working arrangement that may or may not be ready to fall on its aaaa...what a lovely day is not something I could steer people towards.

Is the recovery method you talk about is for users running 2 nvidia card? (i only use one so..)


. . No its for installing proprietary drivers direct from Nvidia to keep up with the latest support/apps.

Stephen

<shrug>
ID: 1956751 · Report as offensive     Reply Quote
Stephen "Heretic" Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 20 Sep 12
Posts: 5557
Credit: 192,787,363
RAC: 628
Australia
Message 1956753 - Posted: 22 Sep 2018, 6:34:43 UTC - in response to Message 1956722.  


. . The problems are with the latest kernel, but I am running an ASUS X370 mobo so I am wondering if there is an issue there. AFAIK Keith is running all x470 mobos.
Stephen

Nope still running my second X370 system too. Though every day I look at it falling further behind the X470 systems, I threaten to pull the plug on it and upgrade it to X470.


. . I wish I had your budget :) But even if I had the readies to buy the hardware I would struggle to pay the power bills to run them all. The bills are already causing severe pain in the hip pocket every three months ...

Stephen

:)
ID: 1956753 · Report as offensive     Reply Quote
Stephen "Heretic" Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 20 Sep 12
Posts: 5557
Credit: 192,787,363
RAC: 628
Australia
Message 1956755 - Posted: 22 Sep 2018, 6:40:52 UTC - in response to Message 1956723.  

Out of curiosity what issues do you have?
I had to RMA my first R7 1700 because of the segfault problems the early batches had when doing hard computing using multiple thread workloads.
Another problem i think alot of people had is the system crashing when idling, i think this was either a kernel fix or bios fix, can't remember, never had that problem tho.

I too RMA'd my first Ryzen 1700X week 1705 chip. The replacement week 1738 chip was a dud though compared to the original with regard to memory and core overclocks. Definitely the original chip was better except for the repeated segfault errors.


. . There seems to be a bit of a pattern with the R7-1700 series ...

. . I had to RMA my first X370 because it was a boat anchor from the word go. It wouldn't boot at all, no POST, no beeps, no flashing lights just nothing (except the fans would run). The new one seemed fine until I tried to install Lubuntu. But it is working AOK with Win10 (touch wood).

Stephen

:)
ID: 1956755 · Report as offensive     Reply Quote
J. Mileski
Volunteer tester
Avatar

Send message
Joined: 9 Jun 02
Posts: 632
Credit: 172,116,532
RAC: 572
United States
Message 1957023 - Posted: 23 Sep 2018, 23:53:23 UTC

I'm about ready to convert my most powerful computer I own to linux and the special app. As a windows machine it is 8070937.

My question is about the aspeed graphics on board. In windows I have my monitor attached to the onboard vga to free up the 960's for seti. How well will this work in linux?
ID: 1957023 · Report as offensive     Reply Quote
Stephen "Heretic" Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 20 Sep 12
Posts: 5557
Credit: 192,787,363
RAC: 628
Australia
Message 1957032 - Posted: 24 Sep 2018, 0:39:34 UTC - in response to Message 1957023.  

I'm about ready to convert my most powerful computer I own to linux and the special app. As a windows machine it is 8070937.

My question is about the aspeed graphics on board. In windows I have my monitor attached to the onboard vga to free up the 960's for seti. How well will this work in linux?


. . Not very well it seems. There have been several messages about another user's attempts to do that, The problem is that if/when you succeed the xorg interface will only link to the onboard video and you cannot tweak, or control the fans on, the crunching GPUs.

. . I a running 970s and I am using one as the display GPU and there is no major issue with that. But if you intend to the use the PC as something other than a pure cruncher you will experience the usual screen lag issues.

Stephen

. .
ID: 1957032 · Report as offensive     Reply Quote
Previous · 1 . . . 75 · 76 · 77 · 78 · 79 · 80 · 81 . . . 162 · Next

Message boards : Number crunching : Setting up Linux to crunch CUDA90 and above for Windows users


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.