I guess that makes sense. I thought I had set NNT on my computers after the WOW event, apparently this one got shut down before it could upload. Of course before I updated to Mint, I used 7.z to store my BOINC folder and unzipped it to the desktop once I had mint installed. Then I unzipped the all-in-one to the desktop. When I started BOINC, it uploaded all those old files. I guess that is were all the errors came from.

---

I switched another computer to Linux Mint 19.3. But I made a mistake before starting BOINC, I didn't put the AMD CPU app in the folder and point the app/info toward the app. I messed up a bunch of CPU wu, now I have to wait for my daily quota to come back up.

---

Well, that's just great...
Seems every time We get all the Apps working well, SETI changes something that breaks them. Well, seems they broke everything this time :-(
I thought about what might be needed Next, and decided the Latest and Greatest version of the Berkeley version of BOINC might be nice. You will need a nicely working version of BOINC , that works in your Home folder, for all those Other Projects. I was hoping to test it with an Overflow Storm to make sure it works with 14 GPUs reporting 100+ tasks every 5 minutes, but, I don't suppose that will happen now. Otherwise, it's been working Great over the past few days of testing.

This version, as with the other All-In-Ones, is completely Stock with a few settings changed for better performance on High-End Systems.
1) The Minimum Retry time was changed from 120 sec to 15 secs to keep from having the Uploads/Downloads pile up during Shorty/Overflow Storms.
2) The Minimum Backoff time was changed to 305 sec to also help with Uploads/Downloads backing up.
3) The job_limit was increased to 5000.
These changes solve most problems with stuck Uploads/Downloads. Retry times are in seconds, Backoff times are in minutes. It seems to work very well.

I also included the New AVX CPU App, and the CUDA 10.2 version that works with Maxwell. The Maxwell version only has precompiled code for Maxwell and Pascal, so, use the larger version of 10.2 for Pascal and Above GPUs. This of course made the file somewhat larger...

So, enjoy the Newest version of BOINC, it's working well on My machines. It's in the Same location, http://www.arkayn.us/lunatics/BOINC.7z

Well, that's just great...
Seems every time We get all the Apps working well, SETI changes something that breaks them. Well, seems they broke everything this time :-(
I thought about what might be needed Next, and decided the Latest and Greatest version of the Berkeley version of BOINC might be nice. You will need a nicely working version of BOINC , that works in your Home folder, for all those Other Projects. I was hoping to test it with an Overflow Storm to make sure it works with 14 GPUs reporting 100+ tasks every 5 minutes, but, I don't suppose that will happen now. Otherwise, it's been working Great over the past few days of testing.
This version, as with the other All-In-Ones, is completely Stock with a few settings changed for better performance on High-End Systems.
1) The Minimum Retry time was changed from 120 sec to 15 secs to keep from having the Uploads/Downloads pile up during Shorty/Overflow Storms.
2) The Minimum Backoff time was changed to 305 sec to also help with Uploads/Downloads backing up.
3) The job_limit was increased to 5000.
These changes solve most problems with stuck Uploads/Downloads. Retry times are in seconds, Backoff times are in minutes. It seems to work very well.
I also included the New AVX CPU App, and the CUDA 10.2 version that works with Maxwell. The Maxwell version only has precompiled code for Maxwell and Pascal, so, use the larger version of 10.2 for Pascal and Above GPUs. This of course made the file somewhat larger...
So, enjoy the Newest version of BOINC, it's working well on My machines. It's in the Same location, http://www.arkayn.us/lunatics/BOINC.7z

. . Thanks for the effort TBar. Somehow the latest news has taken the wind right out of my sails, I imagine it is much the same for most others.

. . It's been fun and interesting.

Stephen

:(

TBar, thank you for all the work that you've done in supporting the community. And thanks to all the other developers, software/hardware wizards and to the other kind, generous and helpful souls who over the years have helped people like myself maintain our senses of humor and sanity when we ran into those odd "Why is *that* happening?" situations.

---

Well, that's just great...
Seems every time We get all the Apps working well, SETI changes something that breaks them. Well, seems they broke everything this time :-(
I thought about what might be needed Next, and decided the Latest and Greatest version of the Berkeley version of BOINC might be nice. You will need a nicely working version of BOINC , that works in your Home folder, for all those Other Projects. I was hoping to test it with an Overflow Storm to make sure it works with 14 GPUs reporting 100+ tasks every 5 minutes, but, I don't suppose that will happen now. Otherwise, it's been working Great over the past few days of testing.

This version, as with the other All-In-Ones, is completely Stock with a few settings changed for better performance on High-End Systems.
1) The Minimum Retry time was changed from 120 sec to 15 secs to keep from having the Uploads/Downloads pile up during Shorty/Overflow Storms.
2) The Minimum Backoff time was changed to 305 sec to also help with Uploads/Downloads backing up.
3) The job_limit was increased to 5000.
These changes solve most problems with stuck Uploads/Downloads. Retry times are in seconds, Backoff times are in minutes. It seems to work very well.

I also included the New AVX CPU App, and the CUDA 10.2 version that works with Maxwell. The Maxwell version only has precompiled code for Maxwell and Pascal, so, use the larger version of 10.2 for Pascal and Above GPUs. This of course made the file somewhat larger...

So, enjoy the Newest version of BOINC, it's working well on My machines. It's in the Same location, http://www.arkayn.us/lunatics/BOINC.7z

Thank you. I really "LIKE" the All-in-One approach. After reading all the apparent headaches of trying to run repository BOINC I would prefer to stick with your version.

Tom

---

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

I thought about what might be needed Next, and decided the Latest and Greatest version of the Berkeley version of BOINC might be nice. You will need a nicely working version of BOINC , that works in your Home folder, for all those Other Projects.
...
So, enjoy the Newest version of BOINC,

Thanks for this, and all your efforts. Loaded on two hosts right now, the others at the end of the month.
Much appreciated!

---

I've been cobbling together some older hand-me-downs, I ended up with a Dell Vostro-400. It has a Core2Quad Q6600 in it. I don't think it supports SSE4.1. Any idea which CPU app I should use? I found a copy of "MBv8_8.05r3345_avx_linux64_CPU" in my downloads folder on my windows computer.

---

I don't think a Q6600 will support AVX (from the app name), since it doesn't support the earlier SSE 4.1

I used to run Q6600s - I think they had SSSE3.

Been looking around on another computer, I found MBv8_8.04r3306_sse2_linux64_CPU.7z

---

Extensions and Technologies
MMX instructions
SSE / Streaming SIMD Extensions
SSE2 / Streaming SIMD Extensions 2
SSE3 / Streaming SIMD Extensions 3
SSSE3 / Supplemental Streaming SIMD Extensions 3
EM64T / Extended Memory 64 technology / Intel 64 ?
VT-x / Virtualization technology ?

The r3306 SSE2 app would be a good choice.

---

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

A proud member of the OFA (Old Farts Association)

If you are part of the group that plans to continue "running" the S@H project after the last tasks are processed on your Linux box
just remember if S@H starts distributing "new" apps with different names (because they have other astronomy research starting) your system will not download them unless you have renamed your "app_info.xml" file so that "anything" will be downloaded and processed.

Otherwise you would be dependent on catching a website announcement etc.

Tom

---

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

If you are going "around and around" with Ubuntu 18.4.x for anything from the logon loop to not being able to get the Nvidia drivers to install via "Launchpad" then you might want to try Zorin (core).

It has a long history of a "Windows-ish" ver 7 Gui.

It has a "modern Nvidia" drivers install as part of the main install menu.

I installed it and it was "turn key" to get BOINC up and running again.

Sorta.

I would suggest you run BOINC dry if possible. And you might have to "reset" your non-Seti projects as well as re-extract your BOINC.zip file.

Tom M

---

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

If you are going "around and around" with Ubuntu 18.4.x for anything from the logon loop to not being able to get the Nvidia drivers to install via "Launchpad" then you might want to try Zorin (core).

Now that I've refreshed my ux head a bit, I can't say I've found much grief with 18.04.
There are a few things I do, however, that make life easier.
1) Load Samba, so I can use my Win10 box across the network for basic file edits and admin, especially LAMP admin.
2) Enable local SSH and load PuTTY on the Win box, for places where Win across the network can't handle the job (e.g. ownership, permissions, symlinks, etc.)
3) Forget Gnome/Nautilus exist. Not needed with 1,2 above in place.
4) Do use dos2unix across SSH where needed after edits.
5) Do updates and installs across SSH from a terminal window. Easier than GUI anyway.
These days, about the only time I go downstairs is when I actually need to touch the box itself.

---

If you are going "around and around" with Ubuntu 18.4.x for anything from the logon loop to not being able to get the Nvidia drivers to install via "Launchpad" then you might want to try Zorin (core).

Now that I've refreshed my ux head a bit, I can't say I've found much grief with 18.04.
There are a few things I do, however, that make life easier.
1) Load Samba, so I can use my Win10 box across the network for basic file edits and admin, especially LAMP admin.
2) Enable local SSH and load PuTTY on the Win box, for places where Win across the network can't handle the job (e.g. ownership, permissions, symlinks, etc.)
3) Forget Gnome/Nautilus exist. Not needed with 1,2 above in place.
4) Do use dos2unix across SSH where needed after edits.
5) Do updates and installs across SSH from a terminal window. Easier than GUI anyway.
These days, about the only time I go downstairs is when I actually need to touch the box itself.

Do you ever use the LInux box to remote into windows? I am having a heck of a time......

---

Do you ever use the LInux box to remote into windows? I am having a heck of a time......

Can't say I've had a need to do that, though I can see a couple ways it could be done. There's a remote Desktop app for Linux out there called Remmina Remote Desktop Client. Haven't tried it, but it looks promising .
I tried to set up XRDP for GUI access via RDP to Ubuntu, but had no luck with it due primarily, I believe, to interactions with the NVidia drivers or my poor understanding of XOrg. That's what led me to what I detailed above.

---

If you are going "around and around" with Ubuntu 18.4.x for anything from the logon loop to not being able to get the Nvidia drivers to install via "Launchpad" then you might want to try Zorin (core).

Now that I've refreshed my ux head a bit, I can't say I've found much grief with 18.04.
There are a few things I do, however, that make life easier.
1) Load Samba, so I can use my Win10 box across the network for basic file edits and admin, especially LAMP admin.
2) Enable local SSH and load PuTTY on the Win box, for places where Win across the network can't handle the job (e.g. ownership, permissions, symlinks, etc.)
3) Forget Gnome/Nautilus exist. Not needed with 1,2 above in place.
4) Do use dos2unix across SSH where needed after edits.
5) Do updates and installs across SSH from a terminal window. Easier than GUI anyway.
These days, about the only time I go downstairs is when I actually need to touch the box itself.

Do you ever use the LInux box to remote into windows? I am having a heck of a time......

Hi Buckeye,

As Jim stated Remmina is a good choice. I use it to access my Win7 laptop from my Linux Mint main. I use the RDP protocol to access all my hosts even the Linux hosts.

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

If you are part of the group that plans to continue "running" the S@H project after the last tasks are processed on your Linux box
just remember if S@H starts distributing "new" apps with different names (because they have other astronomy research starting) your system will not download them unless you have renamed your "app_info.xml" file so that "anything" will be downloaded and processed.
Otherwise you would be dependent on catching a website announcement etc.
Tom

. . That's a good point Tom. But for the meantime I am still trying to catch some resends to help clear up the backlog.

Stephen

. .

Tom,

I don't think anyone else has had as much problems getting the nvidia drivers to work on Ubuntu 18 as you. There's gotta be something you're doing wrong or different than everyone else to cause so many problems. Ubuntu is very easy. Maybe the problem is you're trying to use the GUI too much. I only do installs via the CLI and it's never failed me. Always have the monitor plugged into the GPU that displays the BIOS screen, this is usually the x16 slot closest to the CPU socket (but some boards might break convention, my Supermicro boards do)

after a fresh Ubuntu 18.04 install, do:

sudo apt update
sudo apt upgrade
reboot
sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt update
sudo apt install nvidia-driver-440
reboot

and you're done.

to enable overclocking and thermal/fan control:

sudo nvidia-xconfig --thermal-configuration-check --cool-bits=28 --enable-all-gpus

the ONLY problem I ever had was after running the coolbits command and writing an xorg.conf file, sometimes the bus ID gets changed of the GPU driving the monitor. and this only happens on certain motherboards, my Supermicro boards never had this happen, and my ASUS z270 board doesn't do it either, but ASUS HEDT boards (x79/x99) seem to be affected by this problem, it happens on my ASUS P9X79E-WS, and I know it happens on Keith and Zalster's ASUS x99 boards that are similar. this will result in booting to a black screen and you might see a mouse pointer if you move the mouse around. just manually edit the xorg.conf file to return device/screen 0 to being the bus ID back to the GPU that shows the BIOS at boot.

sudo nano /etc/X11/xorg.conf
--make changes to file in nano--
[Ctrl]+X to save changes
reboot

---

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

the ONLY problem I ever had was after running the coolbits command and writing an xorg.conf file, sometimes the bus ID gets changed of the GPU driving the monitor. ... just manually edit the xorg.conf file to return device/screen 0 to being the bus ID back to the GPU that shows the BIOS at boot.

sudo nano /etc/X11/xorg.conf
--make changes to file in nano--
[Ctrl]+X to save changes
reboot

That's been the issue that's plagued me on my HP boxes since day 1. Can't ever count on where the desktop is actually going to show up. The times I tried to change the xorg.conf file I ended up unbootable, and had to go back to the backup.
Must be about time for me to tackle that issue again, now that SETI is wound down and most crunchers are turned off, and figure out how I'm doing wrong something that should be so simple.

---