How to install Nvidia drivers on a server

I'm trying to install nvidia drivers instead of again on a remote server running Ubuntu 18.04, which I access via a remote desktop (running Plasma KDE). I followed the instructions of other posts trying to install the proprietary drivers, then purging and reinstalling it several times. I am not sure that the driver is installed correctly.

What I did (after this post Install Nvidia drivers on Ubuntu Server 18.04):

sudo apt-get purge nvidia*

sudo apt-get autoremove

sudo add-apt-repository ppa:graphics-drivers

sudo apt-get install nvidia-driver-430

sudo reboot

It seems to be fine.

I check then nvidia-smi:

| NVIDIA-SMI 430.40       Driver Version: 430.40       CUDA Version: 10.1     |
| 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 1080    Off  | 00000000:01:00.0 Off |                  N/A |
| 33%   37C    P8     7W / 200W |     54MiB /  8119MiB |      0%      Default |

| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|    0      1273      G   /usr/lib/xorg/Xorg                             9MiB |
|    0      1339      G   /usr/bin/sddm-greeter                         42MiB |

This makes me think that the driver has been installed correctly, however, sudo nvidia-settings can not run

ERROR: Unable to load info from any available system                                                                                                                               

(nvidia-settings:2278): GLib-GObject-CRITICAL **: 13:28:34.205: g_object_unref: assertion 'G_IS_OBJECT (object)' failed                                                            
** Message: 13:28:34.206: PRIME: No offloading required. Abort
** Message: 13:28:34.206: PRIME: is it supported? no

Also, glxinfo | grep nvidia do not return anything.

The last two facts make me think that the driver was not installed correctly.

Where I think the problem could be:

In some messages such as:

install nvidia ubuntu 18.04 drivers with secure boot

Can not install Nvidia drivers on Ubuntu 18.04.1

I have found suggestions that when you install, you are prompted for a keyword that you must then enter again when restarting. I did not have this step. In fact, I do not know how to take into account the suggestions for action before starting the computer (such as entering BIOS or disabling Secure Boot as, as I said , it's a remote server that I access via ssh or the remote desktop.

Additional Information:

Operation glxinfo | grep OpenGL

OpenGL renderer string: llvmpipe (LLVM 8.0, 256 bits)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.0.2
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.1 Mesa 19.0.2
OpenGL shading language version string: 1.40
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.0.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:

Operation sudo nvidia-settings

Error code listed above, but a small, empty window appears

(Nvidia configuration window)

Exit the terminal at runtime sudo apt-get install nvidia-driver-430

Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  libxnvctrl0 nvidia-compute-utils-430 nvidia-dkms-430 nvidia-kernel-common-430 nvidia-kernel-source-430
  nvidia-prime nvidia-settings nvidia-utils-430 screen-resolution-extra
The following NEW packages will be installed:
  libxnvctrl0 nvidia-compute-utils-430 nvidia-dkms-430 nvidia-driver-430 nvidia-kernel-common-430
  nvidia-kernel-source-430 nvidia-prime nvidia-settings nvidia-utils-430 screen-resolution-extra
0 upgraded, 10 newly installed, 0 to remove and 162 not upgraded.
Need to get 0 B/13.8 MB of archives.
After this operation, 39.0 MB of additional disk space will be used.
Do you want to continue? (Y/n) y
Selecting previously unselected package libxnvctrl0:amd64.
(Reading database ... 250513 files and directories currently installed.)
Preparing to unpack .../0-libxnvctrl0_418.56-0ubuntu0~gpu18.04.1_amd64.deb ...
Unpacking libxnvctrl0:amd64 (418.56-0ubuntu0~gpu18.04.1) ...
Selecting previously unselected package nvidia-compute-utils-430.
Preparing to unpack .../1-nvidia-compute-utils-430_430.40-0ubuntu0~gpu18.04.1_amd64.deb ...
Unpacking nvidia-compute-utils-430 (430.40-0ubuntu0~gpu18.04.1) ...
Selecting previously unselected package nvidia-kernel-source-430.
Preparing to unpack .../2-nvidia-kernel-source-430_430.40-0ubuntu0~gpu18.04.1_amd64.deb ...
Unpacking nvidia-kernel-source-430 (430.40-0ubuntu0~gpu18.04.1) ...
Selecting previously unselected package nvidia-kernel-common-430.
Preparing to unpack .../3-nvidia-kernel-common-430_430.40-0ubuntu0~gpu18.04.1_amd64.deb ...
Unpacking nvidia-kernel-common-430 (430.40-0ubuntu0~gpu18.04.1) ...
Selecting previously unselected package nvidia-dkms-430.
Preparing to unpack .../4-nvidia-dkms-430_430.40-0ubuntu0~gpu18.04.1_amd64.deb ...
Unpacking nvidia-dkms-430 (430.40-0ubuntu0~gpu18.04.1) ...
Selecting previously unselected package nvidia-utils-430.
Preparing to unpack .../5-nvidia-utils-430_430.40-0ubuntu0~gpu18.04.1_amd64.deb ...
Unpacking nvidia-utils-430 (430.40-0ubuntu0~gpu18.04.1) ...
Selecting previously unselected package nvidia-driver-430.
Preparing to unpack .../6-nvidia-driver-430_430.40-0ubuntu0~gpu18.04.1_amd64.deb ...
Unpacking nvidia-driver-430 (430.40-0ubuntu0~gpu18.04.1) ...
Selecting previously unselected package nvidia-prime.
Preparing to unpack .../7-nvidia-prime_0.8.8.2_all.deb ...
Unpacking nvidia-prime ( ...
Selecting previously unselected package screen-resolution-extra.
Preparing to unpack .../8-screen-resolution-extra_0.17.3_all.deb ...
Unpacking screen-resolution-extra (0.17.3) ...
Selecting previously unselected package nvidia-settings.
Preparing to unpack .../9-nvidia-settings_418.56-0ubuntu0~gpu18.04.1_amd64.deb ...
Unpacking nvidia-settings (418.56-0ubuntu0~gpu18.04.1) ...
Setting up nvidia-prime ( ...
Processing triggers for mime-support (3.60ubuntu1) ...
Setting up nvidia-utils-430 (430.40-0ubuntu0~gpu18.04.1) ...
Setting up nvidia-kernel-common-430 (430.40-0ubuntu0~gpu18.04.1) ...
update-initramfs: deferring update (trigger activated)
Setting up nvidia-compute-utils-430 (430.40-0ubuntu0~gpu18.04.1) ...
Warning: The home dir /nonexistent you specified can't be accessed: No such file or directory
Adding system user `nvidia-persistenced' (UID 127) ...
Adding new group `nvidia-persistenced' (GID 135) ...
Adding new user `nvidia-persistenced' (UID 127) with group `nvidia-persistenced' ...
Not creating home directory `/nonexistent'.
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Setting up nvidia-kernel-source-430 (430.40-0ubuntu0~gpu18.04.1) ...
Setting up screen-resolution-extra (0.17.3) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Processing triggers for dbus (1.12.2-1ubuntu1.1) ...
Setting up libxnvctrl0:amd64 (418.56-0ubuntu0~gpu18.04.1) ...
Setting up nvidia-dkms-430 (430.40-0ubuntu0~gpu18.04.1) ...
update-initramfs: deferring update (trigger activated)
INFO:Enable nvidia
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
Loading new nvidia-430.40 DKMS files...
Building for 4.15.0-58-generic
Building for architecture x86_64
Building initial module for 4.15.0-58-generic

Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.15.0-58-generic/updates/dkms/

Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.15.0-58-generic/updates/dkms/

Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.15.0-58-generic/updates/dkms/

Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.15.0-58-generic/updates/dkms/


DKMS: install completed.
Setting up nvidia-driver-430 (430.40-0ubuntu0~gpu18.04.1) ...
Setting up nvidia-settings (418.56-0ubuntu0~gpu18.04.1) ...
Processing triggers for initramfs-tools (0.130ubuntu3.8) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-58-generic
I: The initramfs will attempt to resume from /dev/dm-1
I: (/dev/mapper/vg0-swap)
I: Set the RESUME variable to override this.
Processing triggers for libc-bin (2.27-3ubuntu1) ...```

No DispalyPort Option in the Audio Output Device Menu, Nvidia Drivers

I can not display my monitor connected to DisplayPort (AW2518HF, connected external speakers) in this drop-down menu:
Settings> Sound> Output> Output Device.

I have opened the Nvidia X server settings and I can assure you that DP Audio is enabled. In addition, I started Windows 7 and was able to select it and play a perfect sound.

I'm using a GTX 750 (EVGA; they've added a DP port in their version) with the 418 driver installed from Software & Updates on Ubuntu 19.04.

here is aplay -l

**** List of PLAYBACK Hardware Devices ****
card 0: PCH (HDA Intel PCH), device 0: ALC887-VD Analog (ALC887-VD Analog)
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia (HDA NVidia), device 3: HDMI 0 (HDMI 0)
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia (HDA NVidia), device 7: HDMI 1 (HDMI 1)
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia (HDA NVidia), device 8: HDMI 2 (HDMI 2)
  Subdevices: 1/1
  Subdevice #0: subdevice #0

iMac 2008 (24 ") running Windows x64 BootCamp – The NVIDIA driver crashes everything

I have a 24 "iMac Apple with a NVIDIA GeForce 8800 GS graphics card under Windows 64x.Everything works perfectly, save for a problem … if I install graphics drivers – not at all – there is no problem. computer hangs like crazy.

I've been looking for countless websites to find a solution, downloaded different versions of drivers (including the beta ones), started in safe mode and tried to perform a clean boot – but none of that that I tried does not solve the problem.

The graphics card may just be fried and I do not know (and I'm too loose to remove it), but the Windows side works better than the Mac side, because booting under OS X causes the iMac hangs in the 10 seconds, no matter what I do; at least on the Windows side, the computer will survive even if no driver is installed. Too bad that using built-in graphics in Windows is not an option.

Can any one suggest other options for me to solve this problem?

apt – Update halted Update halted by nvidia

Try to update my Ubuntu system. Get this error on some Nvidia drivers. He broke the update and prompting only to apt --fix-broken install now. And this command also fails.

I have not found any way to fix this broken update. Any suggestion to solve this problem?

root @ rajhome: ~ # apt --fix-broken install
Reading package lists ... Done
Build a dependency tree
Reading status information ... Done
Fix dependencies ... Done
The following package has been installed automatically and is no longer required:
Use 'apt autoremove & # 39; to delete it.
The following additional packages will be installed:
The following packages will be updated:
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
91 not completely installed or removed.
Need to get 0 B / 142 KB of archives.
After this operation, 23.6 KB of additional disk space will be used.
Do you want to continue? [Y/n] there
(Reading the database ... 244787 files and directories currently installed.)
Preparation of the decompression ... / libglx-mesa0_19.0.2-1ubuntu1.1 ~ 18.04.1_amd64.deb ...
Unpacking libglx-mesa0: amd64 (19.0.2-1ubuntu1.1 ~ 18.04.1) on (18.2.8-0ubuntu0 ~ 18.04.2) ...
dpkg: archive when processing the error /var/cache/apt/archives/libglx-mesa0_19.0.2-1ubuntu1.1~18.04.1_amd64.deb (--unpack):
trying to replace & # 39; /usr/lib/x86_64-linux-gnu/ ;, which is also in the package nvidia-418 418.67-0ubuntu1
Errors were encountered during treatment:
E: The / usr / bin / dpkg subprocess returned an error code (1)

nvidia optimus – bumblebee can not work, impossible to get a display device for DPI calculation

I've already installed the bumblebee, primus, nvidia driver of apt, but there is a problem.

  1. I restart the drone
$ sudo service bumblebeed restart

the result:

bumblebeed.service - Bumblebee Demon C
Loaded: loaded (/lib/systemd/system/bumblebeed.service; enabled; vendor preset: enabled)
Active: active since Saturday 2019-07-06 14:43:36 CST; 3s ago
Main ID: 21489 (bumblebeed)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/bumblebeed.service
1421489 / usr / sbin / bumblebeed

06 July 14:43:36 DobMaMi systemd[1]: Started the Bumblebee C demon.
06 July 14:43:36 DobMaMi bumblebeed[21489]: [15416.944880] [INFO]/ usr / sbin / bumblebeed 3.2.1 Started

It's good.
But after using optirun, the output of the bumblebeed:

bumblebeed.service - Bumblebee Demon C
Loaded: loaded (/lib/systemd/system/bumblebeed.service; enabled; vendor preset: enabled)
Active: active since Saturday 2019-07-06 14:43:36 CST; 2 minutes ago
Main ID: 21489 (bumblebeed)
Tasks: 3 (limit: 4915)
CGroup: /system.slice/bumblebeed.service
1421489 / usr / sbin / bumblebeed
1621682 / usr / lib / xorg / xorg: 8 -config /etc/bumblebee/xorg.conf.nvidia -configdir /etc/bumblebee/xorg.conf.d -sharevts -nolisten tcp -n

06 July 14:43:36 DobMaMi systemd[1]: Started the Bumblebee C demon.
06 July 14:43:36 DobMaMi bumblebeed[21489]: [15416.944880] [INFO]/ usr / sbin / bumblebeed 3.2.1 Started
06 July 14:45:50 DobMaMi bumblebeed[21489]: [15550.959989] [WARN][XORG]    (WW) Hotplugging is enabled, devices using the drivers 'kbd', 'mouse' or & # 39; vmmouse & # 39;
06 July 14:45:50 DobMaMi bumblebeed[21489]: [15550.960037] [WARN][XORG]    (WW) Disabling the keyboard0
06 July 14:45:50 DobMaMi bumblebeed[21489]: [15550.960047] [WARN][XORG]    (WW) Disable mouse0
06 July 14:45:50 DobMaMi bumblebeed[21489]: [15550.960087] [WARN][XORG]    (WW) NVIDIA (0): Can not get the display device for DPI calculation.
  1. optirun is not good
$ optirun nvidia-settings

This is not work, but

$ optirun nvidia-settings -c: 8

It's good.
and the following is also good

$ optirun nvidia-smi
  1. when I run
$ optirun -b primus -vv glxgears
$ optirun -vv glxgears

the output is:

[14936.573585] [DEBUG]Reading the file: /etc/bumblebee/bumblebee.conf
[14936.574402] [DEBUG]optirun version 3.2.1 from ...
[14936.574432] [DEBUG]Active configuration:
[14936.574442] [DEBUG]    Bumblebeed configuration file: /etc/bumblebee/bumblebee.conf
[14936.574452] [DEBUG]    X Display :: 8
[14936.574461] [DEBUG]    LD_LIBRARY_PATH: / usr / lib / x86_64-linux-gnu: / usr / lib / i386-linux-gnu
[14936.574470] [DEBUG]    Socket path: /var/run/bumblebee.socket
[14936.574485] [DEBUG]    Accel / display bridge: primus
[14936.574504] [DEBUG]    VGL compression: proxy
[14936.574527] [DEBUG]    Additional VGLrun options: 
[14936.574548] [DEBUG]    LD Primus path: / usr / lib / x86_64-linux-gnu / primus: / usr / lib / i386-linux-gnu / primus
[14937.983726] [INFO]Answer: yes X is active.

[14937.983803] [INFO]Running an application with the help of primus.
[14937.984132] [DEBUG]The glxgears process has started, PID 21027.
X Failed Request Error: BadMatch (invalid parameter attributes)
Major opcode of failed request: 155 (GLX)
Minor opcode of failed request: 11 (X_GLXSwapBuffers)
Serial number of failed request: 40
Current serial number in the output stream: 41
primus: warning: removal of a frame to avoid a stalemate
primus: warning: waiting time waiting for the operator to display
end up called without active exception
[14940.448978] [DEBUG]SIGCHILD received, but wait failed with no child process
[14940.449086] [DEBUG]Closed socket.
[14940.449174] [DEBUG]Kill all the remaining processes.
  1. I thought maybe a little wrong on the display
$ echo $ DISPLAY
: 0
$ DISPLAY =: 8

then, I run:

$ optirun nvidia-setting


$ optirun glxgears

They all work, but I can not see the user interface of them (the user interface is not displayed on my monitor).

Can any one give me any advice, thanks!

grub2 – Number U19.04 Nvidia 430. bpfilter

I have a laptop with an igpu and nvidia gpu.

Yesterday, I updated my nvidia driver to use the new CUDA, and after the reboot, the laptop looked almost dead. I could not log in too long, I was getting a black screen, sometimes with "bpfilter started". Or nothing. Or it would be frozen depending on the larva.

I spent all day troubleshooting. Blacklist. Edit Grub. Yes, I commented on # WaylandEnable = false & # 39; I've tried lightdm, as well as others. I've installed, upgraded, downgraded and purged various Nvidia drivers. Depending on the type of server, I can access tty, but not always.

The only way I can connect is to use nomodeset in grub, which means not only that I do not have access to my gpu, but that I can not use my external monitor, which also makes the job easier.

All suggestions are very much appreciated!

nvidia – Ubuntu 18.04 crashes. I have no idea what causes it

I updated my desktop computer on June 21, according to the following specifications:

Proc: Ryzen 5 2600 (Cooler stock)
MB: MSI B450 Bazooka More
RAM: Kingston Hyper X Fury 2x8GB 2666
GPU: GTX 1050
PSU: Seasonic S12? 80+ Bronze 520 Watts

And since then, will Ubuntu crash or crash? No display, no keyboard / mouse input (no power) and the EZ DEBUG LED on the MB CPU turns on.

I've tried to contact MSI, but they give me solutions for cases where the unit does not start totally with the processor LED on and for WINDOWS (argh!)

You will find below the last part of syslog before the crash:

Zealot / Enemy (enemy z): NVIDIA GPU minor (version 2.0) – Cryptocurrency Corner

Zealot / Enemy (z-enemy) Minor NVIDIA GPU.
x16r, x16s, Bitcore, Phi1612, Xevan, Tribes, x17, c11, AeriumX, XDNA (hex), phi, phi2, skunk, etc.
=============================================== === ====

Z-ENEMY 2.00 From: Dk & Enemy (z-enemy) NEW

This release includes a new way to manage and monitor the minor.


New features:
– Added the new JSON HTTP API (see json_api_help.txt for more details), available by default on port 4067.
– Added web control panel with monitoring and real-time graphics.
The user interface is responsive and should look good on most mobile phones and tablets.

Other changes:
– The miner informs about the startup of the API servers (Telnet and HTTP)
– You can now disable both servers with –api-bind = 0 and –api-bind-http = 0 respectively
– Minor bug fixes and stability improvements

– For HTTP server – The command line option –api-allow has no effect (for now?)

The Windows:
Cuda: 10.0; 9.2; 9.1 –!zZUHWShC!Z7WVzMeFhKIm2CNakx1_8w

Cuda 10.0:!UCQlSaJI!j_b7REMSVkp5SRDQP2PjaaEpcA7tYuwxJZGj0GJFoqs
Cuda 9.2:!5bAxlSAI!3y5fu0uLjYz51gNNPeiz2959IrHgiyQlVJTobVk4aXA
_______________________________________________________________________________ _________
Z-ENEMY 1.28 From: Dk & Enemy (z-enemy)

For maximum performance, make sure you have the latest drivers (version 415+).

Performance improvements of 1.28 compared to the previous version (1.27):
– Bitcoin Diamond + 7-8%, Hex 4-5% and + 3-5% for x16r / s, x17, bitcore, c11, sonoa, etc.

Other changes:
– Added –no-nvml switch to disable NVML monitoring (useful for reducing the load on low-end processors)
– After several tests, we recommend using the intensity 22 on 1080i cards on x16r algo (and maybe others).

Z-ENEMY 1.27 From: Dk & Enemy (z-enemy)

Performance improvement:
Up to + 3-4% for x16r / s and hex, + 6-8% Bitcoin Diamond, 1-3% on others (x17, bitcore, c11, sonoa, etc.) on GTX 10×0 cards

Z-ENEMY 1.26 ver.1 From: Dk & Enemy (enemy-z)

For maximum performance, make sure you have the latest drivers (version 415+).

Performance improvement:
– Up to + 5-7% x16r / s, + 7% bitcore, a few percent over the others (x17, c11, aergo …) on GTX 10×0 cards.
– Hex algo + 10% for GTX 10×0 cards and + 2% for RTX 20×0 cards.

Other changes:
– Renesis algo deleted
– improved stability

Z-ENEMY 1.25 ver.1 From: Dk & Enemy (enemy-z)

For maximum performance, make sure you have the latest drivers (version 415+).

Performance improvements in x16, x17, c11, bitcore, BCD, aergo, sonoa and hex:
+ 10% or more for RTX 2080 / 2080ti / 2070 cards
+ 3-7% for GTX 1080Ti / 1080 / 1070ti and lower cards

– Reduced use of the processor.

_______________________________________________________________________________ __________

Z-ENEMY 1.24 ver.3 From: Dk & Enemy (enemy-z)

For maximum performance, make sure you have the latest drivers (version 415+).

– Major optimizations for skunk, polytimos and phi
– Minor optimizations for hex and x16r / s, tribes.
– Massive increase in performance for RTX 2080 / 2080ti / 2070 in many algorithms.

– Highlighted hardware statistics reports, colored GPU temperatures (green / yellow / red)
– Added support for Volta architecture
– Important update (1.24 ver.2): correction of a multi-gpu crash bug (skunk and polytimos)
– Important update (1.24 ver.3): reduced pool hashrate (XDNA: hex algo) fixed

Z-ENEMY VER 1.23 From: Dk & Enemy (enemy-z)

For maximum performance, make sure you have the latest drivers (version 415+).

– First wave of performance optimization for the RTX 2080 and 2080Ti series up to 10-20% in various seaweeds :(x16, x17, c11, hex, bitcore, xevan …)
– Minor performance optimizations for old maps (10×0)
– Fixed a memory bug out of the tribes (it is now possible to run it with higher intensities)
– Remove options –tlimit and –plimit
– Added options –max-temp – tempos

– Experimental support CUDA 10: Higher speeds and stability, support for new RTX2080 and 2080 Ti cards
– Performance improvement: 2-5% for most algae (Hex, X16, X17, Bitcore, C11, etc.)

Cuda 10 version 32 and 64 runs faster in most Algos … Update your Nvidia drivers – minimum (ver 415+)
Important. This is the first basic build for Cuda 10, please leave comments on our channel # z-enemies-122test

From: Dk & Enemy (z enemy)

For maximum performance, make sure you have the latest drivers (version 398+).

– Improved performance and stability, some bugs fixed.
– Addition of availability reports.

As in the previous version, the 32-bit version works faster in some algos …

Z-ENEMY VER 1.20 (PUBLIC) From: Dk & Enemy (z-enemy)

For maximum performance, make sure you have the latest drivers (version 398+).

– Major performance improvements: 5-10% in various algae
– Bitcoin Diamond: Supports the new top famous algorithm at high speed, 20-30% higher than the current ones.

As in the previous version, the 32-bit version works faster with some algos (x16 / x17, etc.) …

Enjoy [IMG]

Z-ENEMY VER 1.19 (PUBLIC) From: Dk & Enemy (enemy-z)

For maximum performance, make sure you have the latest drivers (version 398+).

Major performance improvements: 5-7% in various algos (x16, x17, bitcore, c11, hex, etc.)
Improved stability

The 32-bit version seems to be even faster among some players, do not hesitate to test it!

Z-ENEMY VER 1.18 (PUBLIC) From: Dk & Enemy (z-enemy)

For maximum performance, make sure you have the latest drivers (version 398+).

Greetings! We publish an updated version of our operating system with bug fixes and other changes:

Major performance improvements: 10-15% for Xevan (+ fix a reduced hashrate problem from 1.17)
– Minor performance improvements for other algae
– Improved stability for xDNA

Z-ENEMY VER 1.17 (PUBLIC) From: Dk & Enemy (z-enemy)

For maximum performance, make sure you have the latest drivers (version 398+).

Greetings, minor comrades! We publish an updated version of our operating system with a certain speed:

– Major performance improvements: 5 to 10% for X16R and X16S, XDNA (hex), x17, Bitcore (BTX), c11, Sonoa, Renesis, Aergo
– Bottom end cards like 1050/1060 will see some extra% (yes, a bonus)
– The minor no longer depends on memory, it allows to use the memory at +0 or -500 MHz without loss of performance.

Looking good!



For maximum performance, make sure you have the latest drivers (version 398+).

zealot / enemy-1.16 (enemy z) from: Dk & Enemy

– Performance improvement:+ 7-10% hex (X-DNA), + 5% -7% x16r & s, some% for other algae (x17, c11, sonoa, renesis, aergo)
– Experimental characteristic: increased intensity limit (most Algos now allow intensity up to 25, test at your own risk)


For maximum performance, make sure you have the latest drivers (version 398+).

For Windows Cuda 9.2:
zealot / enemy-1.12a (enemy z) from: Dk & Enemy

– Improved phi2 performance: + 4-5% (up to 5 Mh / s for 1070ti, up to 7.5 Mh / s for 1080ti)

– Minor performance improvements for other algos


For maximum performance, make sure you have the latest drivers (version 398+).

zealot / enemy-1.12 (enemy z) of: Dk & Enemy

– Minor performance improvements: x17, x16r, x16s, c11, bitcore, aeriumx and more …
– New algae: SONOA (-a sonoa) and PHI2 (-a phi2)


For Windows (Cuda 9.1)
zealot / enemy-1.11 (enemy z) from: Dk & Enemy

Performance improvement: x17 (+ 4-8%), x16r & s (+ 1-3%), very fast Phi1612 and others …
Quick start on multiple gpu platforms
GPU limit increased to 24
AeriumX (AEX) – the miner supports the new Aerium exchange (-a aeriumx) from 4 June.
added: C11(-a c11) x64 basic and fast (ver.4), skunk(-a skunk) basic, improved TimeTravel8(-a one hour) and Polytimos (-a poly)


For Windows (Cuda 9.1)
zealot / enemy-1.10 (z-enemy) From: Dk & Enemy

Fixed compatibility issues that caused performance degradation with some pools other than yiimp. Now you will see the expected hashrate on them (suprnova).

Improvement of the speed of the cores : (1.09a vs 1.10) + 1-2% total (all algae) and (1.09b vs 1.10) + 1-2% for x16r & x16s.

Support and impose a new algo : Tribes (-a tribes), recommended intensity for Tribes 20-21. + 5% speed compared to 1.09b (service version)

First time or x16 troubleshooting:
– New users – ver. 1.12 works on Cuda 9.1 & 9.2 and it is recommended to make sure you have updated your NVIDIA drivers. You can find the drivers here ver., 398 +++
– The next important thing is the intensity. We recommend first the intensity -19. However, if your PC has 8 GB or more, a fast SSD, and a large swap file, you can use -20/21.
– X16r algo is very wild and erratic. * Very important * Make sure you have enough power on the PSU. Make sure you have at least 20% margin on your power unit or set your PL on 70% to 80% usage.
– It is useful to use + core and + mem, but do not start with OC before checking the stability.

Performance and focus x16:
– This version z-1.12 enemies would be more stable if it used a higher overclocking (90-110%) and + heart and + memory, do not hesitate to experiment it.
– Updating drivers can generate more gains
– The recommended intensity is 20, set 21 only if you know what you are doing. (16 GB of RAM and / or good SWAP file on SSD) Be careful
– Recommended memory 0 or +
– Heart recommended + 50 + 150 (1800-1900 MHz 1080 Ti)
– Overclock slowly and allow enough time to check for stability (12-24 hours) before making other adjustments. x16r is a very chaotic algorithm, so it's not because it works for 1 hour that you can not crash any longer. Sometimes, the hash order can lead to 2000 + mhz and system crash. Keep in mind – overclocking is always at your own risk!
– Yiimp pools recommend manual differences (-pd = 16) – for small farms or (-pd = 48) – for good farms like 5-6 1080 Ti. If you need to name your facilities as well as set diff, try -p rigname, d = 16

Diff x16 can be calculated by multiplying the following:
Number of 1060 multiplied by 3-4
Number 70 or 80 multiplied by 4-8
Number of 80ti times 6-12

example: if you have 3 1060, then diff would be 9-12
if you have 8 70ti then your diff would be 48-96

Dev fees:
– low dev fee 1%
– The development costs will start randomly at the first start of the minor. After 1% of the time mined, then automatically returns to the user group.

Information about x16:

Each block contains 16 random algae.

All the algae have Quick, Way and Slow So, depending on the order and the speed at which they match, your hashrate will be determined at any time.

Quick: Blake (Blk), Bmw512 (Bmw), Keccak (Kck), Skein (Ske), Shabal (Shb), Sha512 (Sha)
Way: Jh512 (Jh5), Luffa (Luf), Cube (Cub), Shavite (Shv), Fugue (Fug), Whirlpool (Wrl)
Slow: Groestl (Gro), Simd (Smd), Echo (Ech), Hamsi (Ham)

Block 181085, difficulty 20228.532
Hashorder: EchFugBmwShaJh5FugShvEchSmdBmwHamWrlJh5KckSkeHam

Means first algo is Slow Echo (Ech)> next Way Fugue (Fug)> …> last Hamsi (Ham). most quick algos in a block is what drives the miner's speed at the Moon! (more than MH)


Yiimp Pools:

z-enemy -a phi layer -o + tcp: // bsod pool pw: 6667 -u LQCifDiNVXjM_your_wallet_CUqZJBa75p11 -p x

z-enemy -a x16r -o stratum + tcp: // yiimp eu: 3636 -u RWgpF9GefjD_your_wallet_1gQmQjpYtYt.GTX950 -p d = 3 -i 19

z-enemy – a bitcore – a stratum + tcp: // yiimp eu: 3556 – u 1D2dKSprpK_your_wallet_1wa8b2LnJ826uf -p x -i 20

Suprnova Pool:

z-enemy -a x16r -o stratum + tcp // rvn suprnova cc: 6667 -u your_login.your_new_employer -p x -i 20


I can not start minor, he says that he misses me msvcr120.dll?
Download and reinstall the drivers from

My miner crashed – error cuda in funk `cuda_check_cpu_setTarget` why?
This error is due to overclocking, lowering the GPU and VRAM clocks.

Latest recommended drivers?
Yes, however, a new driver can sometimes be a problem and using a previous version can be more effective. You will have to check. We recommend at least the NVIDIA drivers of 390 +++ or 398.xx

What is restart-fix.reg in the Windows download folder?
This file will correct the popup and allow the miner to restart after a crash. Run once.

How many GPUs can I run?
We confirmed reports on 19 maps

Is there a simple way to restart Miner automatically in case of a crash?
Yes, check out our sample * .cmd files in Windows Build. As:
: start
z-enemy -a layer phi -o + tcp: // pool bsod pw: 6667 -u LQCifDiNV_YOUR_WALLET_F3CUqZJBa75123 -p x
to start

Does z-1.12 enemies do not support api?
Yes, try –api-remote and / or –api-allow = (simple 0/0)

z-enemies does not support loading the default ccminer.conf from the .conf file?
support of the enemy z config.json

Claymore Dual Ethereum AMD + NVIDIA GPU Miner v14.7 (Windows / Linux) – Cryptocurrency Corner

Dual Ethereum + Claymore's Decred & Siacoin / Lbry / Pascal / Blake2s / Keccak AMD + NVIDIA GPU.

The latest version is v14.7 – Supercharged Edition:

– From now on, the miner driver no longer needs to switch from Windows to test mode. If you want to disable the test mode, use the "-driver uninstall" option (with administrator rights) and reboot.
Then start Miner with administrator rights to automatically install the new driver if needed (or use the "-driver install" option directly).
If you have problems with the signed driver, you can use the "-driver install_test" option. It uses the old approach: activates the test mode (reboot is required) and installs the unsigned driver.
– Adding the "-showpower" option for the GPU's power consumption statistics, press "s" to see it. AMD and Nvidia cards are supported, except for Linux gpu-pro drivers and Radeon7 cards.
– Update Remote Manager to display the total power consumption.
– fixed a problem with the "-logsmaxsize" option when the "-logfile" option is used to specify the log file directory.
– some minor bugfixes and improvements.

DOWNLOAD LINK: MEGA Download Claymore's Miner v14.7

the version is v14.6 – Supercharged Edition:

– The "-rxboost" option now supports older AMD cards (Hawaii, Tonga, Tahiti, Pitcairn). Use the "-rxboost 1" option to improve the hashrate up to 5% by applying additional memory timings.
– now the option "-rxboost" supports all AMD drivers.
– now "-strap" for AMD cards also supports AMD blockchain drivers.
– a few modifications to reduce even a little outdated actions.
– added option "-minspeedtime".
– Added statistics for actions accepting time (min / max / average), press "s" to see it.
– Update Remote Manager to display shares that accept the time.
– some minor bugfixes and improvements.


– Supports optimized synchronization of memory (tapes) on the fly in Windows, without blinking the VBIOS (currently, Polaris, Vega, Nvidia 10xx only), up to 20% faster. The best straps for Ethereum are included.
– Support for the new "double extraction" mode: simultaneous extraction of Ethereum and Decred / Siacoin / Lbry / Pascal / Blake2s / Keccak, without impact on Ethereum extraction rate. Ethereum extraction mode only is also supported.
– The actual Ethereum extraction rate is 3 to 5% higher due to a totally different miners code: far fewer invalid and outdated partitions, higher GPU load, optimized OpenCL code, optimized assembler kernels.
– Supports AMD and nVidia cards, even when mixed.
– No DAG files.
– Supports all versions of Stratum for Ethereum: can be used directly without a proxy with all pools supporting eth-proxy, qtminer or miner-proxy.
– Supports individual Ethereum and Siacoin extraction.
– Supports HTTP and Stratum for Decred.
– Supports HTTP and Stratum for Siacoin.
– Stratum support for Lbry, Pascal, Blake2s, Keccak.
– Supports failover.
– Displays detailed information about the extraction and a hashrate for each card.
– Supports remote monitoring and management.
– Supports GPU selection, built-in GPU overclocking functions and temperature management.
– Supports Ethereum forks (Expanse, etc.).
– Windows and Linux versions.

This version is POOL / SOLO for Ethereum, POOL for Decred, POOL / SOLO for Siacoin, POOL for Lbry, POOL for Pascal, POOL for Blake2s, POOL for Keccak.

For older AMD cards, Catalyst (Crimson) 15.12 is required to optimize performance and compatibility.
For AMD 4xx / 5xx (Polaris) cards, you can use any recent driver.
For AMD cards, set the following environment variables, especially if you have 2 … 4 GB cards:


This minor is free, however, the current developer's fees are 1%. Every hour, it is extracted for 36 seconds.
For all cards of 2 GB and 3 GB, 0% devfee, so you can exploit all ETH forks without devfee, this minor is completely free in this case.
If some cards have a capacity of 2 … 3 GB and others> 3 GB, 2 … 3 GB still belong to you during development, only cards with more than 3 GB of memory will be used for mining. Miner displays the appropriate messages at startup.
The second piece (Decred / Siacoin / Lbry / Pascal / Blake2s / Keccak) is extracted without developer fees.
So the developer fee is 0 … 1%, if you do not agree with the development fee, do not use this minor, or the option " -nofee ".
Attempts to cheat and suppress development costs will result in a slower extraction rate (similar to "-nofee 1"), although the miner displays the same hashrate.
Miner can not simply stop if a fraud is detected because its creators would know that it is not working and would find new tricks. If minor shows no error or slowdown, he is happy.

This version is for recent AMD video cards only: 7xxx, 2xx and 3xx, 2 GB or more. Recent nVidia video cards are also supported.


You can use the "config.txt" file instead of specifying command-line options.
If there is no command line option, Miner will check the "config.txt" file for options.
If there is only one option in the command line, it must be the name of the configuration file.
If there are two or more options in the command line, Miner will take all options from the command line, not the configuration file.
Place one option per line, if the first character of a line is ";" or "#", this line will be ignored.
You can also use environment variables in the "epools.txt" and "config.txt" files. For example, set the environment variable "WORKER" and use it as "% WORKER%" in config.txt or in epools.txt.

If for Ethereum extraction only:

EthDcrMiner64.exe -pool -wal 0xD69af2A796A737A103F12d2f0BCC563a13900E6F -epsw x

EthDcrMiner64.exe -pool -wal 0xD69af2A796A737A103F12d2f0BCC563a13900E6F -epsw x

EthDcrMiner64.exe -pool -wal 0xd69af2a796a737a103f12d2f0bcc563a13900e6f -epsw x -employed rig1

EthDcrMiner64.exe -epool -ewal 0xd69af2a796a737a103f12d2f0bcc563a13900e6f -epsw x -worker rig1

EthDcrMiner64.exe – group layer + tcp: // 3353 -wal 1LmMNkiEvjapn5PRY8A9wypcWJveRrRGWr -epsw x -esm 3 -allpools 1 -estale 0

Ethereum Mine:

EthDcrMiner64.exe -pool -wal 0xd69af2a796a737a103f12d2f0bcc563a13900e6f -epsw x -allcoins -1

Ethereum SOLO mining (suppose geth is


Use the "epools.txt" and "dpools.txt" files to specify additional pools (you can use the "-epoolsfile" and "-dpoolsfile" options to use different filenames).
These files have the text format, one pool per line. Each pool has 3 connection attempts.
Miner disconnects automatically if the pool does not send new jobs for a long time or if the pool rejects too many shares.
If the first character of a line is ";" or "#", this line will be ignored.
Do not change the spacing, spaces between parameters and values ​​are required for analysis.
If you must specify "," character in the parameter value, use two commas – ,, will be treated as a single comma.
You can reload the files "epools.txt" and "dpools.txt" at the time of execution by pressing the "r" key.
The pool specified on the command line is the "primary" pool. Miner will try to come back every 30 minutes if he has to use a different pool from the list.
If no pool has been specified in the command line, the first pool in the failover pool list is the primary pool.
You can change the 30-minute period to a different value with the "-ftime" option or use "-ftime 0" to disable failover to the primary pool.
You can also use environment variables in the "epools.txt", "dpools.txt", and "config.txt" files. For example, set the environment variable "WORKER" and use it as "% WORKER%" in config.txt or in epools.txt.
You can also select the current pool at runtime by pressing the "e" or "d" key.


Miner supports remote monitoring / management via JSON over raw TCP / IP sockets. You can also get the latest lines of text from the console via HTTP.
Start "EthMan.exe" from the "Remote Management" subfolder (Windows version only).
See the built-in help for more information. The "API.txt" file contains more details about the protocol.


– AMD cards: On some cards, you may notice a non-constant extraction speed in dual mode, the speed sometimes becomes a little slower. This problem has been mostly solved in recent versions, but not completely.
– AMD cards: under Linux with gpu-pro drivers, the list of GPUs may differ from that of temperatures. You can use -di to change the order of the GPUs so that they match both lists.
– nVidia cards: Dual mode is not as effective as AMD cards.
– Windows 10 Defender recognizes Miner as a virus, some antivirus do the same. Miner is not a virus, add it to the Defender exceptions.
I've been writing minors since 2014. Most of them are recognized as viruses by some paranoid antiviruses, maybe because I compress my miners to protect them from disassembly, maybe because some people include them in their botnets, or maybe these antiviruses are not good. I do not know. During these years, many people used my minors and no one confirmed that it had stolen or done anything wrong.
Note that I can guarantee clean binaries only for official links in my posts on this forum (bitcointalk). If you have downloaded minor from another link, it can be a virus.
However, my minors are closed sources and so I can not prove that they are not viruses. If you think I write viruses instead of good kids, do not use this minor, or at least not use it on systems that do not contain any useful data.


1. Install Catalyst v15.12 for older AMD cards; for Fury, the Polaris and Vega cards use the latest Blockchain drivers.
2. Disable overclocking.
3. Set the environment variables as described above.
4. Set 16 GB or more of virtual memory.
5. Restart the computer.
6. Check the hardware, the risers.
7. Set an expiration time in the .bat file before starting the minor at system startup (30 seconds or even a minute) and try "-ethi 4" to check if it is more stable. This can help if the miner is not stable on some systems.


– Miner runs too slowly when I operate ETH / ETC but works properly when I operate an ETH fork.
Check if you have enabled "Calculation Mode" in the AMD drivers. You can also press the "y" key to enable "Calculation Mode" in the AMD drivers for all cards (Windows only).

– I can not use ETH / ETC with the Nvidia 3GB card under Windows 10.
Windows 10 internally allocates about 20 percent of the GPU memory so that applications can only use 80 percent of the GPU's memory. Use Windows 7 or Linux.

18.04 – Tearing the screen with NVIDIA GTX 970

There seems to be some screen tearing issues in Ubuntu 18.04, which has been confirmed by the execution of this test:

I've searched Google for a while, but found only recommendations for editing the file. /etc/modprobe.d/nvidia-drm-nomodeset.conf and add

options nvidia-drm modeset = 1

But that did not do anything.

These are the drivers that I use:

enter the description of the image here

What can I do to solve this problem?