Message boards :
Number crunching :
Linux CUDA 'Special' App finally available, featuring Low CPU use
Message board moderation
Previous · 1 . . . 41 · 42 · 43 · 44 · 45 · 46 · 47 . . . 83 · Next
Author | Message |
---|---|
tazzduke Send message Joined: 15 Sep 07 Posts: 190 Credit: 28,269,068 RAC: 5 |
Greetings Stephen ???? What did you just acquire that you seem to think is a dud ???? Regards |
Stephen "Heretic" Send message Joined: 20 Sep 12 Posts: 5557 Credit: 192,787,363 RAC: 628 |
Greetings Stephen . . A new rig with an ASUS Prime X370 Pro mobo and a Ryzen7-1700 with Corair Vengeance 2666MHz ram. . . Either I have bricked it (which I doubt because I have been super careful) or it is a dud. It will not run through the POST, gives no display and accepts no input. The lights come on and the fans and ODD spin up OK but then nothing ... :( Stephen :( |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
I've been attempting to build a new version of BOINC that works in the Ubuntu 16.04.x Home folder. It's been mostly a Success with a couple Snafus. Has anyone running one of the newer versions of BOINC, around 7.6, noticed the view in the Tasks window has a tendency to jump to the bottom of the page during an Update? Sometimes it happens every few Updates, sometimes it takes over an hour or two before I'm looking at the bottom of the page. Other than that, and the time zone tags in the Event Log disappearing/reappearing, it seems to be working OK. Just wondering how many others have found the Tasks page has mysteriously moved to the bottom of the page. To give it a try, open it to the Tasks Tab and Sort it by Progress, with the Active Tasks at the Top of the Page. I did compile a new build of zi3v in 16.04.2, but it doesn't seem to be much different than the current version. The OS display is a little different with BOINC 7.7.x, it names the version of Linux...for me anyway. Operating System - Linux Ubuntu Ubuntu 16.04.2 LTS [4.8.0-58-generic] BOINC version - 7.7.0 |
tazzduke Send message Joined: 15 Sep 07 Posts: 190 Credit: 28,269,068 RAC: 5 |
Hi Stephen Sorry to hear, hope it works out for you. Regards |
jason_gee Send message Joined: 24 Nov 06 Posts: 7489 Credit: 91,093,184 RAC: 0 |
Just a quick drop by to give a heads up, mostly directed at Petri, while sorting other stuff. Upcoming Cuda changes for [redacted] will likely require checking/modifications to all Warp Synchronous code. Both Baseline and Special. "Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions. |
Gene Send message Joined: 26 Apr 99 Posts: 150 Credit: 48,393,279 RAC: 118 |
@TBar re: tasks tab Yes, I see the same effect in 7.6.33 (and it was the same in 7.6.22; and maybe before that...) My "workaround" is to sort tasks in REVERSE order, click second time on "progress" column, and then live with the running tasks filtering down and out of the bottom of the screen. There is also a similar effect in the "Transfers" tab, i.e. active transfers displayed at the top but the window selects the bottom portion of the list when the list size exceeds the window size. Gene; |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
Thanks for the reply. I remember the same problem, along with other problems, back in version 7.4.22. You have to go back to a 7.2.xx version to escape the bouncing page. The versions prior to 7.4 used wxWidgets 2.8, the newer versions use wxWidgets 3.0. Ubuntu versions above around 15.04 require wxWidgets 3. It's thought the problem is with wxWidgets. Compared to the current Linux Development version 7.4.22, both 7.6.33 and 7.7.x are much better as they appear to only suffer from the bouncing page and Event log time tags. Version 7.4.22 also has those problems along more 'serious' snafus. Hopefully we'll see something better than 7.4.22 posted as the Development version soon. |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
I'm going to declare Mission Accomplished. I Now have a version of BOINC 7.2.47 that; 1) Works in the Home Folder of 16.04.x where it Doesn't require Special Permissions 2) Built with Static wxWidgets 2.8.12 Libraries, meaning No LibWx Dependencies 3) Works with Ubuntu 12.04, 14.04, and yes, 16.04.x and above 4) Doesn't suffer from the Jumping Tasks Tab Page or the Disappearing Event Log Time tags which Every Higher Version I've tested Does Suffer from. 5) Very easy to install, if you Don't already have a BOINC Folder, Expand to your Home Folder and double click on boincmgr 6) If you have an existing BOINC Folder in your Home Folder, simply copy the five expanded files and paste them into your existing BOINC Folder My three Linux machines are running it. First time there's been a worthy replacement for 7.2.33 in Ages. Now running Linux is even Easier... |
Stephen "Heretic" Send message Joined: 20 Sep 12 Posts: 5557 Credit: 192,787,363 RAC: 628 |
I'm going to declare Mission Accomplished. . . OK, when I get the new rig working I will try 16.04 LTS and this ... Stephen 8^} |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
I've been trying to decide what to do with 'it'. After reading the ReadMe here, https://github.com/BOINC/boinc/blob/master/README.md, I decided to just go ahead and post it at C.A. None of the code has been changed and according to the link you can pretty much give it to anyone. This version is much better than the current 7.4.22 Development version Berkeley has posted and works in the Newer Linux versions where the current Recommended version doesn't. Over the past week I've built and tested numerous versions and none of them had any problems other than the Jumping Tasks page and disappearing time tags. It's a mystery why the current 7.4.22 version preforms so badly. This version, 7.2.47, doesn't have those problems and should be tested on other machines. It's basically what you would get after downloading and running the .sh file from Berkeley. If you plan on using the run_manager and run_client files you need to first open them and change the word user to the name of your Home folder. I can see possibilities, you could just insert the CUDA Special package into the BOINC package and make it extremely easy to be up and running in a couple minutes. But really, how hard is it to just do that manually? ;-) |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
Oh, the files are here, http://www.arkayn.us/forum/index.php?topic=197.msg4515#msg4515 I had to split them into two parts to upload them...you need both parts. |
tazzduke Send message Joined: 15 Sep 07 Posts: 190 Credit: 28,269,068 RAC: 5 |
Greetings TBAR On my two MINT 18.2 machines am running the repo version 7.6.33 and the Special Cuda App, my GTX 950 running it will soon overtake my GTX 960 running SOG on WIN 7 lol. Yeah I have no hiccups with this version of BOINC, and with a couple of mouseclicks and one cmdline entry and away we go. The bug about sorting tasks no the way its meant to be doesnt bother me, I just click the tab bar to sort and its happy. Regards |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
After the test I ran, the chances of the AsyncRPC Bug just being on My machines is just about Zero. Everyone has to have this Bug since it's in the BOINC Source code. It will affect different Platforms in different ways. Some may not have Jumping Pages, they might have things such as, failure to download tasks during RPC Events. I'm surprised Almost No One has mentioned this problem with BOINC suddenly moving the page to the bottom during RPC Events. It's such an obvious Bug. Imagine My surprise when Every version of BOINC I compiled above 7.2.47 had this Bug in Linux. It seems using BOINC 7.2.33 for so long was a very good thing. Now I have 7.2.47 that works in 16.04...I'm set for a few years ;-) |
-= Vyper =- Send message Joined: 5 Sep 99 Posts: 1652 Credit: 1,065,191,981 RAC: 2,537 |
Hi TBar.. Just wanted you to know that i've switched my Quad 750Ti to your application now. If you perhaps want a machine to monitor missbehaviour within the executable but i presume that wont be much of an issue. https://setiathome.berkeley.edu/show_host_detail.php?hostid=8053171 Thanks for keeping it up! _________________________________________________________________________ Addicted to SETI crunching! Founder of GPU Users Group |
petri33 Send message Joined: 6 Jun 02 Posts: 1668 Credit: 623,086,772 RAC: 156 |
Just a quick drop by to give a heads up, mostly directed at Petri, while sorting other stuff. Upcoming Cuda changes for [redacted] will likely require checking/modifications to all Warp Synchronous code. Both Baseline and Special. Thanks. Will keep an eye on that. 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 |
Stephen "Heretic" Send message Joined: 20 Sep 12 Posts: 5557 Credit: 192,787,363 RAC: 628 |
. . Hi TBar . . I am most distressed ... I have an invalid task that is not a noise bomb ... http://setiathome.berkeley.edu/workunit.php?wuid=2616796976 . . It looks OK to me though it completed slightly quicker than the usual Guppi task. 4.1 mins compared to 5.4, whether or not that is any pointer to why it might have been marked as invalid. Stephen ?? |
Grant (SSSF) Send message Joined: 19 Aug 99 Posts: 13720 Credit: 208,696,464 RAC: 304 |
. . I am most distressed ... I have an invalid task that is not a noise bomb ... Their results Spike count: 1 Autocorr count: 2 Pulse count: 6 Triplet count: 0 Gaussian count: 0 Your result Spike count: 9 Autocorr count: 2 Pulse count: 4 Triplet count: 15 Gaussian count: 0 EdIt- that's a bit odd, it started on Device 1, then stopped & restated on Device 2. In cudaAcc_initializeDevice(): Boinc passed DevPref 1 setiathome_CUDA: CUDA Device 1 specified, checking... Device 1: GeForce GTX 970 is okay SETI@home using CUDA accelerated device GeForce GTX 970 Unroll autotune 13. Overriding Pulse find periods per launch. Parameter -pfp set to 13 setiathome v8 enhanced x41p_zi3v, Cuda 8.00 special CUDA 8.0 Special version by petri33. setiathome_CUDA: CUDA Device 2 specified, checking... Device 2: GeForce GTX 970 is okay SETI@home using CUDA accelerated device GeForce GTX 970 Unroll autotune 13. Overriding Pulse find periods per launch. Parameter -pfp set to 13 Restarted at 72.01 percent, with setiathome enhanced x41p_zi3v, Cuda 8.00 special **** Detected setiathome_enhanced_v7 task ****. Autocorrelations enabled, size 128k elements. Grant Darwin NT |
Brent Norman Send message Joined: 1 Dec 99 Posts: 2786 Credit: 685,657,289 RAC: 835 |
EdIt- that's a bit odd, it stared on Device 1, then stopped & restated on Device 2.That would be it. The app really doesn't like to be restarted from checkpoint, and can throw errors - even on the same card. |
Grant (SSSF) Send message Joined: 19 Aug 99 Posts: 13720 Credit: 208,696,464 RAC: 304 |
EdIt- that's a bit odd, it stared on Device 1, then stopped & restated on Device 2.That would be it. The app really doesn't like to be restarted from checkpoint, and can throw errors - even on the same card. Hmm, bit of house keeping required? Clear out everything before re-loading, initialising & re-starting the WU? Odd that on the restart it thought it was doing a v7 WU. Grant Darwin NT |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
Restarted at 72.01 percentThat has already been discussed. You will have to talk to Petri about that one. My suggestion would be to set the checkpoints to longer than your GPU takes to finish a task. Or, you can do as I do and remove the active GPU tasks from the client_state.xml before restarting Boinc. In any case, nothing I can do about it, I just compile the code. In other events, I've discovered a way to have Boinc Manager Stop boinc when exiting Boinc Manager 7.2.47 in 16.04.2. Before Exiting Boinc Manager 7.2.47, select Advanced/Shut down connected client... That Will stop the active tasks and boinc in the newer versions, then select to Exit Boinc Manager. This works very nicely in Ubuntu 16.04.2, but there is a problem trying to restart Boinc Manager in Mint 18.2. So, I've basically given up on MInt and suggest following the line on the Berkeley Download page; Linux x64 Tested on the current Ubuntu distribution; may work on others.That is why I started using Ubuntu to begin with, I looked at the Berkeley page, and decided Ubuntu must be the one. Seems to have worked out nicely as Petri was also using it. Since all I do is compile existing code, the same line goes for any BOINC Linux Apps I compile. So, now I have BOINC 7.2.47 that works in the Newer Ubuntu versions without the annoying Tasks page bouncing, and the Newest BOINC 7.8 for those that don't mind the bouncing. They both work well on My machines running Ubuntu and are here, New BOINC Build to run on Ubuntu 16.04 |
©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.