Search content
Sort by

Showing 20 of 24 results by TAKCuCT
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC Community Release free-easy-to-use Linux Nvidia Mining
by
TAKCuCT
on 09/04/2019, 19:05:35 UTC
A bit less 2 years i am on nvOC. This is the best miners OS now. I had tried a most famous OS's like a ethos, hiveos, simple os and some exotic zhaos, chineese miner os. My rigs still on nvOC.
Post
Topic
Board Mining (Altcoins)
Re: [Hspminer]aeternity: fastest aeterntiy miner 2.0.7 for Linux and Windows
by
TAKCuCT
on 04/01/2019, 08:04:24 UTC
Ubuntu 16.04, 415.25 - drivers, all other miners works. But hspminer:

Code:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
WARNING:

You should always run with libnvidia-ml.so that is installed with your
NVIDIA Display Driver. By default it's installed in /usr/lib and /usr/lib64.
libnvidia-ml.so in GDK package is a stub library that is attached only for
build purposes (e.g. machine that you build your application doesn't have
to have Display Driver installed).
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
nv platform init failed.
Post
Topic
Board Mining (Altcoins)
Re: [ANN] Bminer: a fast Equihash/Ethash/Tensority miner for CUDA GPUs (10.5.0)
by
TAKCuCT
on 13/11/2018, 09:58:57 UTC
We’re pleased to release Bminer 10.6.0.

The release provides:

  • Substantially increase BTM mining speed, e.g. 4650 H/s on 1080Ti now.
  • This version requires CUDA 9.2 or above.

Please see https://www.bminer.me for more details.

Happy mining!
Ubuntu 16.04, Drivers 415,13, 4*1080TI+2*1070. All other miners works fine, but new bminer:
Code:
[INFO] [2018-11-13T14:51:48+05:00] Watchdog has started.                        
[INFO] [2018-11-13T14:51:48+05:00] Starting miner on 6 devices                  
[INFO] [2018-11-13T14:51:48+05:00] Starting the management API at 0.0.0.0:42000
[INFO] [2018-11-13T14:51:48+05:00] Starting miner on device 0...                
[INFO] [2018-11-13T14:51:48+05:00] Connected to btm.matpool.io:8118            
[INFO] [2018-11-13T14:51:48+05:00] Started miner on device 0                    
[INFO] [2018-11-13T14:51:49+05:00] Starting miner on device 1...                
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0x7332ff]

Tryed no overclock, no PL, still the same.

Update: 410.73 drivers - same error.

Update: BMiner does not working with  matpool.io
Post
Topic
Board Mining (Altcoins)
Re: GMiner CUDA Equihash 144,5/192,7 Miner v1.07 (BTG, BTCZ, ZERO)
by
TAKCuCT
on 02/11/2018, 20:23:07 UTC
Can you make a scripts for HiveOS? Like this http://download.hiveos.farm/custom/
Post
Topic
Board Mining (Altcoins)
Re: GMiner CUDA Equihash 144_5/192_7 Miner v1.01 (BTG, BTCZ, ZERO)
by
TAKCuCT
on 28/09/2018, 16:10:46 UTC
1.01
144,5
Same sols/s on 1070 vs ewbf, but more (+10/15%) better on 1080ti.

192.7
+15/25% vs ewbf.

I think we will see answer from ewbf soon.
Post
Topic
Board Mining (Altcoins)
Re: [ANN] Bminer: a fast Equihash/Ethash/Tensority miner for CUDA GPUs (10.2.0)
by
TAKCuCT
on 10/09/2018, 05:53:40 UTC
Please add support for ProgPOW.
Post
Topic
Board Mining (Altcoins)
Re: [ANN] Bminer: a fast Equihash/Ethash/Tensority miner for CUDA GPUs (9.0.0)
by
TAKCuCT
on 30/07/2018, 10:39:50 UTC
Please add support for mining equihash 96_5
Post
Topic
Board Mining (Altcoins)
Re: EWBF's Cuda Equihash Miner
by
TAKCuCT
on 05/07/2018, 09:59:26 UTC
split them up. Or, launch 2 ewbf miners (or more)
HiveOS does not allow 2 same miners.
Post
Topic
Board Mining (Altcoins)
Re: EWBF's Cuda Equihash Miner
by
TAKCuCT
on 05/07/2018, 08:24:18 UTC
Still no fixes for rigs more than 12 cards.
Post
Topic
Board Mining (Altcoins)
Re: EWBF's Cuda Equihash Miner
by
TAKCuCT
on 27/06/2018, 16:08:53 UTC
Gents, who else has 12 card rigs on SMOS? I have 1070 and 1070ti rigs with 12x GPUs

last 10th, 11th and 12th card keep crushing (or rather, they do not even start mining), i have even removed overclock and tested with stock, still the same.

The rigs work fine with other miners, like EWBF 0.3.4b or Claymore for eth.

Since effectively out of 36 GPUs 7 - 8 are not working, i have switched back to ETH until this is sorted out.

Answer:
https://bitcointalk.org/index.php?topic=4466962.msg40306835#msg40306835

I'm waitnig for new version too.
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC easy-to-use Linux Nvidia Mining vBASIC || Community Edition 2.0
by
TAKCuCT
on 15/05/2018, 03:03:58 UTC
I don't know if they are related errors:


I have been messing with it for 2 days, installed the OS again... nothing



Did you try to change drivers? Try from 384.
Post
Topic
Board Mining (Altcoins)
Re: nvOC v0019-2.0 Community Release
by
TAKCuCT
on 05/01/2018, 09:49:11 UTC
Any one tried Bminer fast Equihash miner for CUDA GPUs ?

https://bitcointalk.org/index.php?topic=2519271.0


Good to add it to default equihash miners too?

More than dstm sol/s on miner, lower than dstm sol/s on pool.
Post
Topic
Board Mining (Altcoins)
Re: hsrminer - Nvidia mining software for various algos by palgin&alexkap
by
TAKCuCT
on 03/01/2018, 16:54:58 UTC
linux version please!
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC Nvidia Mining OS FORK v PXA-1.9.1
by
TAKCuCT
on 25/12/2017, 06:37:51 UTC
ok all issues resolved with that user anyone else with issues?
Just a small fix - 8coin at MPH-EQUIHASH address -> MPH_ADDRESS same at MPH-ETHASH

And can you add limits at OC?
Post
Topic
Board Mining (Altcoins)
Re: [ANN] Bminer: a fast Equihash miner for CUDA GPUs
by
TAKCuCT
on 04/12/2017, 17:34:55 UTC
Linux version?
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.4
by
TAKCuCT
on 07/11/2017, 17:34:27 UTC
As i said above: all rigs in different places and different networks.
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.4
by
TAKCuCT
on 07/11/2017, 17:21:36 UTC


Ok, nothing there other than @fullzero's USB reference (comment out last 2 lines of /etc/fstab to fix those mount timeout errors). Anyway, let's try another tact. Can you find anything related to the time when it last happened using:

Code:
journalctl -u NetworkManager

that should give you detailed networking information.

Networkmanager - disabled.
Syslog from another rig
Code:
WARNING **: log file empty (logrotate?) /var/log/apt/term.log
Nov  6 06:40:18 m1-desktop AptDaemon: INFO: Quitting due to inactivity
Nov  6 06:40:18 m1-desktop org.debian.apt[554]: 06:40:18 AptDaemon [INFO]: Quitting due to inactivity
Nov  6 06:40:18 m1-desktop org.debian.apt[554]: 06:40:18 AptDaemon [INFO]: Quitting was requested
Nov  6 06:40:18 m1-desktop AptDaemon: INFO: Quitting was requested
Nov  6 07:17:01 m1-desktop CRON[10281]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Nov  6 07:30:01 m1-desktop CRON[12570]: (root) CMD (test -x /etc/init.d/anacron && /usr/sbin/invoke-rc.d anacron start >/dev/null)
Nov  6 07:30:01 m1-desktop anacron[12592]: Anacron 2.3 started on 2017-11-06
Nov  6 07:30:01 m1-desktop anacron[12592]: Will run job `cron.daily' in 5 min.
Nov  6 07:30:01 m1-desktop anacron[12592]: Jobs will be executed sequentially
Nov  6 07:30:01 m1-desktop systemd[1]: Started Run anacron jobs.
Nov  6 07:31:31 m1-desktop systemd[1]: dev-disk-by\x2duuid-55184403759586FB.device: Job dev-disk-by\x2duuid-55184403759586FB.device/start timed out.
Nov  6 07:31:31 m1-desktop systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-55184403759586FB.device.
Nov  6 07:31:31 m1-desktop systemd[1]: Dependency failed for /mnt/55184403759586FB.
Nov  6 07:31:31 m1-desktop systemd[1]: mnt-55184403759586FB.mount: Job mnt-55184403759586FB.mount/start failed with result 'dependency'.
Nov  6 07:31:31 m1-desktop systemd[1]: dev-disk-by\x2duuid-55184403759586FB.device: Job dev-disk-by\x2duuid-55184403759586FB.device/start failed with result 'timeout'.
Nov  6 07:31:31 m1-desktop systemd[1]: dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device: Job dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device/start timed out.
Nov  6 07:31:31 m1-desktop systemd[1]: Timed out waiting for device dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device.
Nov  6 07:31:31 m1-desktop systemd[1]: Dependency failed for /mnt/usb-SanDisk_Cruzer_Blade_4C530001260812105231-0:0-part1.
Nov  6 07:31:31 m1-desktop systemd[1]: mnt-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.mount: Job mnt-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.mount/start failed with result 'dependency'.
Nov  6 07:31:31 m1-desktop systemd[1]: dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device: Job dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device/start failed with result 'timeout'.
Nov  6 07:35:01 m1-desktop anacron[12592]: Job `cron.daily' started
Nov  6 07:35:01 m1-desktop anacron[13336]: Updated timestamp for job `cron.daily' to 2017-11-06
Nov  6 07:35:01 m1-desktop cracklib: no dictionary update necessary.
Nov  6 07:35:01 m1-desktop rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="553" x-info="http://www.rsyslog.com"] rsyslogd was HUPed

It looks like problems start after
Code:
Nov  6 07:35:01 m1-desktop anacron[12592]: Job `cron.daily' started
Nov  6 07:35:01 m1-desktop anacron[13336]: Updated timestamp for job `cron.daily'
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.4
by
TAKCuCT
on 07/11/2017, 16:35:26 UTC
Last part of fresh syslog:
Code:
Nov  7 02:19:51 m1-desktop gnome-session-binary[1711]: Entering running state
Nov  7 02:19:51 m1-desktop gnome-session[1711]: (process:1969): indicator-application-service-WARNING **: Unable to get watcher name 'org.kde.StatusNotifierWatcher'
Nov  7 02:19:51 m1-desktop gnome-session[1711]: (process:1969): indicator-application-service-WARNING **: Name Lost
Nov  7 02:19:51 m1-desktop gnome-session[1711]: (nautilus:1964): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
Nov  7 02:19:51 m1-desktop gnome-session[1711]: (nautilus:1964): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
Nov  7 02:19:51 m1-desktop gnome-session[1711]: (nautilus:1964): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Nov  7 02:19:51 m1-desktop gnome-session[1711]: (nautilus:1964): GLib-GObject-WARNING **: invalid (NULL) pointer instance
Nov  7 02:19:51 m1-desktop gnome-session[1711]: (nautilus:1964): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Nov  7 02:19:51 m1-desktop gnome-session[1711]: (nm-applet:1962): nm-applet-WARNING **: NetworkManager is not running
Nov  7 02:19:51 m1-desktop dbus[640]: [system] Activating service name='org.freedesktop.fwupd' (using servicehelper)
Nov  7 02:19:51 m1-desktop systemd[1]: Starting Stop ureadahead data collection...
Nov  7 02:19:51 m1-desktop systemd[1]: Stopped Read required files in advance.
Nov  7 02:19:51 m1-desktop systemd[1]: Started Stop ureadahead data collection.
Nov  7 02:19:51 m1-desktop gnome-session[1711]: (guake:1965): libglade-WARNING **: unknown attribute `swapped' for .
Nov  7 02:19:51 m1-desktop gnome-session[1711]: message repeated 21 times: [ (guake:1965): libglade-WARNING **: unknown attribute `swapped' for .]
Nov  7 02:19:51 m1-desktop gnome-session[1711]: INFO:guake.guake_app:Logging configuration complete
Nov  7 02:19:51 m1-desktop gnome-session[1711]: /usr/lib/python2.7/dist-packages/guake/guake_app.py:1785: GtkWarning: gtk_box_pack: assertion 'child->parent == NULL' failed
Nov  7 02:19:51 m1-desktop gnome-session[1711]:   self.mainframe.pack_start(self.notebook, expand=True, fill=True, padding=0)
Nov  7 02:19:52 m1-desktop org.freedesktop.fwupd[640]: (fwupd:2010): Fu-WARNING **: Failed to coldplug: UEFI firmware updating not supported
Nov  7 02:19:52 m1-desktop dbus[640]: [system] Successfully activated service 'org.freedesktop.fwupd'
Nov  7 02:20:23 m1-desktop systemd[1]: dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device: Job dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device/start timed out.
Nov  7 02:20:23 m1-desktop systemd[1]: Timed out waiting for device dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device.
Nov  7 02:20:23 m1-desktop systemd[1]: Dependency failed for /mnt/usb-SanDisk_Cruzer_Blade_4C530001260812105231-0:0-part1.
Nov  7 02:20:23 m1-desktop systemd[1]: mnt-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.mount: Job mnt-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.mount/start failed with result 'dependency'.
Nov  7 02:20:23 m1-desktop systemd[1]: dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device: Job dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device/start failed with result 'timeout'.
Nov  7 02:20:23 m1-desktop systemd[1]: dev-disk-by\x2duuid-55184403759586FB.device: Job dev-disk-by\x2duuid-55184403759586FB.device/start timed out.
Nov  7 02:20:23 m1-desktop systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-55184403759586FB.device.
Nov  7 02:20:23 m1-desktop systemd[1]: Dependency failed for /mnt/55184403759586FB.
Nov  7 02:20:23 m1-desktop systemd[1]: mnt-55184403759586FB.mount: Job mnt-55184403759586FB.mount/start failed with result 'dependency'.
Nov  7 02:20:23 m1-desktop systemd[1]: Startup finished in 6.349s (kernel) + 1min 30.189s (userspace) = 1min 36.539s.
Nov  7 02:20:23 m1-desktop systemd[1]: dev-disk-by\x2duuid-55184403759586FB.device: Job dev-disk-by\x2duuid-55184403759586FB.device/start failed with result 'timeout'.
Nov  7 02:20:53 m1-desktop gnome-session[1711]: ** (update-notifier:2695): WARNING **: log file empty (logrotate?) /var/log/dpkg.log
Nov  7 02:20:53 m1-desktop gnome-session[1711]: ** (update-notifier:2695): WARNING **: log file empty (logrotate?) /var/log/apt/term.log
Nov  7 02:23:54 m1-desktop anacron[607]: Job `cron.daily' started
Nov  7 02:23:54 m1-desktop anacron[3608]: Updated timestamp for job `cron.daily' to 2017-11-07
Nov  7 02:23:54 m1-desktop cracklib: no dictionary update necessary.
Nov  7 02:23:54 m1-desktop systemd[1]: Reloading LSB: Apache2 web server.
Nov  7 02:23:54 m1-desktop apache2[3667]:  * Reloading Apache httpd web server apache2
Nov  7 02:23:54 m1-desktop apache2[3667]:  *
Nov  7 02:23:54 m1-desktop systemd[1]: Reloaded LSB: Apache2 web server.
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.4
by
TAKCuCT
on 07/11/2017, 12:08:32 UTC
I have 3 rigs on Asrock h110 BTC+ nvidia based (1070 + 1060) on different PSU's and connected to different routers. All of them has very unpleasant problem: once or twice or thrice per day the system hangs and hangs the entire network. This happens only on nvOC, on smos or on ubuntu 16.04 - ok about 2 days. Tried: disable (and remove) dhcp, another router, disable network manager, usb-lan but problem still here. Any thoughts?

You say "the system hangs and hangs the entire network" yet you also say you have 3 rigs. Do you have any idea which system is responsible for a particular "hang"? Also, how do you fix the hang? You also mention disabling usb-lan so how are the rigs connected to the network - wired, wireless, or?

You may want to look for errors/issues in in each rigs /var/log/syslog.
Rigs are in different places but with the same symptoms. Connected by wire. Hangs only can be fixed by reset button or power switch.
Post
Topic
Board Mining (Altcoins)
Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.4
by
TAKCuCT
on 07/11/2017, 11:03:33 UTC
I have 3 rigs on Asrock h110 BTC+ nvidia based (1070 + 1060) on different PSU's and connected to different routers. All of them has very unpleasant problem: once or twice or thrice per day the system hangs and hangs the entire network. This happens only on nvOC, on smos or on ubuntu 16.04 - ok about 2 days. Tried: disable (and remove) dhcp, another router, disable network manager, usb-lan but problem still here. Any thoughts?