I agree, best to avoid the toolkit unless you need it to develop apps. They recently changed the way the toolkit handles the video drivers. You can get yourself in trouble with the toolkit installing its version of the graphics drivers alongside your runtime version of CUDA with the usual graphics drivers installation.

I have been reading this document which I just discovered.

https://docs.nvidia.com/deploy/cuda-compatibility/

Lots of good info about driver versions and CUDA version support among the various generations of cards.

To summarize: acemd3 cuda80 and cuda100 are very satisfactory for linux. Very few failures, fast, blazing on rtx 2080. The win app will need work though.

There is definitely NO NEED TO install the CUDA toolkit for GPUGRID. It's not required, so don't complicate your set-up unnecessarily.

You just will want to have not-too-old drivers, however.

When can we expect the linux version of acemd3 released to the masses?

My guess not until Toni can figure out how to get the acemd3 Windows app working.

I hope the CUDA 9.2 drivers are good enough. When I tried to update to the latest CUDA 10.x drivers for my GTX 1070 from the Nvidia repository (Ubuntu 16.04.6), it blanked out the desktop. BOINC still worked, but I had to reload the OS to get the desktop back. I suppose something in the X.Org server (if that is what they use) does not like the latest drivers, though the Linux experts will need to fix it.

I hope the CUDA 9.2 drivers are good enough. When I tried to update to the latest CUDA 10.x drivers for my GTX 1070 from the Nvidia repository (Ubuntu 16.04.6), it blanked out the desktop. BOINC still worked, but I had to reload the OS to get the desktop back. I suppose something in the X.Org server (if that is what they use) does not like the latest drivers, though the Linux experts will need to fix it.

I have nVidia proprietary drivers ver 430.14 with cuda ver 10.2 installed for three GTX-1060's working fine on my two FX-8350 Fedora 30 systems. Don't know where Ubuntu 16.x falls in the latest distro release line but F30 is the latest release (last month release date) and all is well.

I still think using the graphics-drivers ppa is the easiest solution for obtaining and installing the drivers. As long as you have a debian distro newer than 14, you are good to go with the drivers right up to the current 430 series.

Just add the ppa to your sources and make your choice of which driver you want. Either install from the command line or install from the Software Updater.

https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa

I have a task that appears to be misbehaving.



Application
Long runs (8-12 hours on fastest card) 9.22 (cuda80)
Name
e82s77_e68s28p1f217-PABLO_v3Q9UM73_MOR_14_IDP-0-2-RND6181
State
Running
Received
6/9/2019 3:14:13 AM
Report deadline
6/14/2019 3:14:14 AM
Resources
0.991 CPUs + 1 NVIDIA GPU
Estimated computation size
5,000,000 GFLOPs
CPU time
00:54:04
CPU time since checkpoint
00:00:01
Elapsed time
20:13:55
Estimated time remaining
---
Fraction done
73.853%
Virtual memory size
1.11 GB
Working set size
359.47 MB
Directory
slots/0
Process ID
3684
Progress rate
3.600% per hour
Executable
acemd-922-80.exe

The progess percentage has been frozen, or at least nearly frozen, for at least the last 10 hours.

The estimated remaining time has been --- for at least the last 10 hours.

How long should I let it run before aborting it? Is there anything else I should do to make it run properly?

http://www.gpugrid.net/workunit.php?wuid=16519044

Try to suspend and restart it. Or kill it.

Try to suspend and restart it. Or kill it.

Suspending and restarting it set it back many hours, but only let it have many more hours to show the same problem.

Aborting it worked, though.

Any plans of sending out more beta tasks for Linux? I'm eager to try it on my 2070 and 1660 Ti.

This thread has been very quiet since the last posting by Toni. I should hope that means he is quietly working hard on polishing off the new apps for both Linux and Windows. And soon that new work with new apps will become available.

Yes. The problem is now the windows app and its dependencies. We also need to setup some hardware to test it.

By the way, any experience with W10 bootable USBs for testing purposes?

T

to make a bootable win10 disk i use wintousb software, with win10 iso image.
then unplug internal disk, setup the bios in a proper way to boot from usb disk and you go.

or you can use ultraiso, write image disk and then usb hdd+ option to install iso-image on disk or usb

Thanks for the tips!

Erik was referring to Win 10 installation from USB. Supposedly Win 10 can also boot from a stick - however, this requires certified sticks. I don't have any further experience with that.

MrS

---

Scanning for our furry friends since Jan 2002

Below is a link to a step by step guide with screenshots and links to the appropriate software to make the USB.
You will need an educational or enterprise license of Win10 to run it.

https://au.pcmag.com/windows-10-1/46896/how-to-run-windows-10-from-a-usb-drive

I would consider purchasing a 250 GB SSD drive and setting up a Win/linux dual boot option using grub on one of your linux workstations. You'd still have a buy a license for Win10 pro. Building a "cheap" dedicated Win10 system would be even better. I would think Win10 on a USB stick would a be painful experience (slow).

Erik was referring to Win 10 installation from USB. Supposedly Win 10 can also boot from a stick - however, this requires certified sticks. I don't have any further experience with that.

MrS

nope, i was referring about how to make bootable win10 usb or portable disk. i was not talking about bootable usb to install win10, like you are thinking.

my suggestion was: already installed win10 on bootable usb or ssd (or whatever) using wintousb or ultraiso

I would think Win10 on a USB stick would a be painful experience (slow).

Agreed.

consider purchasing a 250 GB SSD drive and setting up a Win/linux dual boot option

+1
Due to the Win10 licensing model, the USB stick would not be portable between host PCs. It would go to setup mode every time it is plugged into a different host PC, and another Win 10 license would be needed.

I would think Win10 on a USB stick would a be painful experience (slow).

Agreed.

consider purchasing a 250 GB SSD drive and setting up a Win/linux dual boot option

+1
Due to the Win10 licensing model, the USB stick would not be portable between host PCs. It would go to setup mode every time it is plugged into a different host PC, and another Win 10 license would be needed.

it is portabke between all host machines. my experience with enterprise and education version wwin10 is portable between intel and amd platforms. only....when you switch between platforms, you need to activate win10. but be honest....who cares about activating when you are running it for test purposes and temporarly