Ninjastic
Search content
Sort by
Showing 13 of 13 results by salvo2002
Post
Topic
Board Mining (Altcoins)
Re: Z9 Full Modded Efudd NO-DEV FEE 100% Free Individual Clocking
by
salvo2002
on 14/02/2019, 20:22:24 UTC
Quote from: gsrcrxsi314 on February 13, 2019, 02:43:34 AM
efudd, you're arguing with someone that thinks he can lower his electric bill by running his miners off an inverter powered by a wind turbine generator, thats being driven from an electric motor plugged back into the house electric.

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

comprehension isnt his strong suit.

he comes up with half baked schemes because he just wants to be in the "club" of contributors so he can try to get free handouts to his crypto addresses.

omg, thanks for this... good toilet entertainment!
Post
Topic
Board Mining (Altcoins)
Re: Z9 Full Modded Efudd NO-DEV FEE 100% Free Individual Clocking
by
salvo2002
on 12/02/2019, 23:28:51 UTC
well that was entertaining.

Quote from: chipless on February 12, 2019, 06:01:16 PM
I may not explain it all correctly...
Unethical yes...
Post
Topic
Board Mining (Altcoins)
Re: Efudd's Z9/Mini Fuddware v2.1c / PS4 Contest through 12/24!
by
salvo2002
on 09/12/2018, 21:41:38 UTC
Love your fuddwareTM. FYI... I installed 2.1c and it's telling me there's an update available.

https://ibb.co/8gDzY4B
Post
Topic
Board Mining (Altcoins)
Re: Efudd's Z9/Mini Fuddware v2.1c / PS4 and ZEC Contests have started!
by
salvo2002
on 05/12/2018, 18:25:24 UTC
Can I use your firmware with HiveOS integration? https://github.com/minershive/hiveos-asic
Post
Topic
Board Mining (Altcoins)
Re: Efudd's Z9 Firmware: V. 2.0d now available - Latest update in post# 346
by
salvo2002
on 22/11/2018, 04:42:01 UTC
Quote from: efudd on November 20, 2018, 11:42:04 PM
I need a couple of testers for v2.1 for the Z9 Mini, and v2.1 for the Z9 large.
Send me a PM if you are interested -- I want to get some additional verification before "opening the floodgates".

Anyone beta testing with HiveOS?
Post
Topic
Board Mining (Altcoins)
Re: Efudd's Z9 Firmware: V. 2.0d now available (Non-Paid!) - Updates in post# 299
by
salvo2002
on 19/11/2018, 17:31:26 UTC
Quote from: efudd on November 19, 2018, 05:16:14 AM
It is very likely that the mini variant will be released at the same time. I've got an image for the mini under test now as well.
Awesome, can’t wait!  Grin you rock Jason!
Post
Topic
Board Mining (Altcoins)
Re: PhoenixMiner 3.0c: fastest Ethereum/Ethash miner with lowest devfee (Windows)
by
salvo2002
on 17/09/2018, 23:12:12 UTC
Shoutout for the Linux version!

I ran a comparison test for ~29hrs between PhoenixMiner and Claymore. Results here: https://forum.hiveos.farm/t/custom-miner-phoenixminer/7391/2

Keep up the great work PhoenixMiner Devs!
Post
Topic
Board Mining (Altcoins)
Re: PhoenixMiner 3.0c: fastest Ethereum/Ethash miner with lowest devfee (Windows)
by
salvo2002
on 15/09/2018, 20:22:35 UTC
Quote from: PhoenixMiner on September 15, 2018, 05:39:34 AM
   The config seems OK apart from the two -mport options but the second one just overrides the value of the first one, so this isn't really a problem. As for the missing temperature and fan data - this is quite strange, we haven't seen this - perhaps this depends on how hiveOS extracts these: from the miner, or independently. It seems that hiveOS 0.5-74 is based on Ubuntu 18.04, which may be cause or at least part of the problem - we are testing now with Ubuntu 18.04 LTS, so we hope that we will find and fix any problems.

   As for the -tt not working - this is normal, as we do not support hardware control under Linux yet. It will be added in the next version.

I think it's because there is a -tt 0 in there...

The top part of the config is a carry over from a global_config.txt used with claymore. I've edited my global_config.txt to only have:
Code:
#DONT EDIT THIS FILE, IT WILL BE OVERWTITTEN AFTER UPDATE

#Management port, readonly
-mport 3335

#Log to the same file
-logfile /var/log/miner/phoenixminer/lastrun_noappend.log

I had the same problem with the webgui not showing fans and temps. At first I had -tt 0 in the user config because I thought I needed it using HiveOS autofan. Using -tt 0 obivuosly won't output any temp/fan stats.

Using -tt 1 in phoenix or not specifying any -tt (guessing default is -tt 1) just like claymore  Wink, it displays temps and fans fine.

Discussion over at HiveOS: https://forum.hiveos.farm/t/custom-miner-integration/4521/257
Post
Topic
Board Mining (Altcoins)
Re: PhoenixMiner 3.0c: fastest Ethereum/Ethash miner with lowest devfee (Windows)
by
salvo2002
on 13/09/2018, 03:09:05 UTC
Quote from: PhoenixMiner on September 12, 2018, 03:07:28 PM
Code:
  File: PhoenixMiner_3.5c_Linux.tar.gz
    ====================================
 SHA-1: 507c0a69d734519e74e11c89a457d69ce2445106
 SHA-256: 72b4b78fc09770c43a6869923d6bb729571e20aa81da1ccaf8f21392e2d5a7db
 SHA-512: 60505a339be0828f436354906b38bb42ab8c958f2070ef42058015409e5774eb4c4f914b722e055f0c443fd18138e370ddaf277b69ac6a0e07e74569fa7656aa

Version 3.5c fixes the problems that were discovered during the beta-testing of 3.5a and 3.5b, including the following:
  * Fixed freezing problems immediately after GPU are recognized
  * Fixed hardware monitoring problem under Linux with more than 6 GPUs
  * Fixed problems under Linux with unrecognized drivers and stale share increases

testing it now...

Code:
2018.09.12:20:04:41.378: main Phoenix Miner 3.5c Linux/gcc - Release build
2018.09.12:20:04:41.378: main Cmd line:
2018.09.12:20:04:41.378: main config.txt: -mport -3333 -r 1 -logfile /var/log/miner/phoenixminer/lastrun_noappend.log -tt 0
2018.09.12:20:04:41.380: main Unable to enum CUDA GPUs: unknown error
2018.09.12:20:04:41.427: main OpenCL driver version: 17.50-511655
2018.09.12:20:04:41.427: main Available GPUs for mining:
2018.09.12:20:04:41.427: main GPU1: Radeon RX 570 Series (pcie 1), OpenCL 1.2, 8 GB VRAM, 32 CUs
2018.09.12:20:04:41.427: main GPU2: Radeon RX 580 Series (pcie 2), OpenCL 1.2, 8 GB VRAM, 36 CUs
2018.09.12:20:04:41.427: main GPU3: Radeon RX 570 Series (pcie 3), OpenCL 1.2, 8 GB VRAM, 32 CUs
2018.09.12:20:04:41.427: main GPU4: Radeon RX 580 Series (pcie 4), OpenCL 1.2, 8 GB VRAM, 36 CUs
2018.09.12:20:04:41.427: main GPU5: Radeon RX 570 Series (pcie 5), OpenCL 1.2, 8 GB VRAM, 32 CUs
2018.09.12:20:04:41.427: main GPU6: Radeon RX 570 Series (pcie 7), OpenCL 1.2, 8 GB VRAM, 32 CUs
2018.09.12:20:04:41.427: main GPU7: Radeon RX 580 Series (pcie 8), OpenCL 1.2, 8 GB VRAM, 36 CUs
2018.09.12:20:04:41.427: main GPU8: Radeon RX 580 Series (pcie 9), OpenCL 1.2, 8 GB VRAM, 36 CUs
2018.09.12:20:04:41.428: main AMD sysfs monitor initialized
2018.09.12:20:04:41.428: main Eth: the pool list contains 4 pools
2018.09.12:20:04:41.428: main Eth: primary pool: naw-eth.hiveon.net:4444
2018.09.12:20:04:41.428: main Starting GPU mining
Post
Topic
Board Mining (Altcoins)
Re: PhoenixMiner 3.0c: fastest Ethereum/Ethash miner with lowest devfee (Windows)
by
salvo2002
on 12/09/2018, 02:17:19 UTC
Quote from: PhoenixMiner on September 11, 2018, 07:31:33 AM
   Thank you, this is very helpful. Most probably the miner can't recognize the OpenCL driver and some of the most aggressive driver-specific optimizations aren't used. Can you please check if you have a line like this:
Code:
2018.09.10:06:24:11.757: main OpenCL driver version: 17.40
in the start of PhoenixMiner log (it should be among the first five to ten lines in the log file)? Also, could you please tell us the version of your AMD drivers?

AMD driver version: 17.50-511655
Code:
dpkg -l amdgpu-pro
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                                                  Version                         Architecture                    Description
+++-=====================================================-===============================-===============================-===============================================================================================================
ii  amdgpu-pro                                            17.50-511655                    amd64                           Meta package to install amdgpu Pro components.


I don't see a
Code:
"Main OpenCL driver version: ..."

Here are the first 100 lines of the log file... closest thing to any "OpenCL" statements are
Code:
Using new optimized OpenCL kernels (device name 'Ellesmere')
GPU1: Radeon RX 570 Series (pcie 1), OpenCL 1.2, 8 GB VRAM, 32 CUs
I shortened the "jsonrpc":"2.0","result" strings...
Code:
2018.09.11:18:59:32.140: main Phoenix Miner 3.5a Linux/gcc - Release build
2018.09.11:18:59:32.140: main Cmd line:
2018.09.11:18:59:32.140: main config.txt: -mport -3333 -r 1 -logfile lastrun_noappend.log -logdir /var/log/miner/custom/ -tt 0
2018.09.11:18:59:32.145: main Unable to enum CUDA GPUs: unknown error
2018.09.11:18:59:32.182: main Available GPUs for mining:
2018.09.11:18:59:32.182: main GPU1: Radeon RX 570 Series (pcie 1), OpenCL 1.2, 8 GB VRAM, 32 CUs
2018.09.11:18:59:32.182: main GPU2: Radeon RX 580 Series (pcie 2), OpenCL 1.2, 8 GB VRAM, 36 CUs
2018.09.11:18:59:32.182: main GPU3: Radeon RX 570 Series (pcie 3), OpenCL 1.2, 8 GB VRAM, 32 CUs
2018.09.11:18:59:32.182: main GPU4: Radeon RX 580 Series (pcie 4), OpenCL 1.2, 8 GB VRAM, 36 CUs
2018.09.11:18:59:32.182: main GPU5: Radeon RX 570 Series (pcie 5), OpenCL 1.2, 8 GB VRAM, 32 CUs
2018.09.11:18:59:32.182: main GPU6: Radeon RX 570 Series (pcie 6), OpenCL 1.2, 8 GB VRAM, 32 CUs
2018.09.11:18:59:32.182: main GPU7: Radeon RX 570 Series (pcie 8), OpenCL 1.2, 8 GB VRAM, 32 CUs
2018.09.11:18:59:32.182: main GPU8: Radeon RX 580 Series (pcie 9), OpenCL 1.2, 8 GB VRAM, 36 CUs
2018.09.11:18:59:32.182: main GPU9: Radeon RX 580 Series (pcie 10), OpenCL 1.2, 8 GB VRAM, 36 CUs
2018.09.11:18:59:32.183: main AMD sysfs monitor initialized
2018.09.11:18:59:32.184: main Eth: the pool list contains 4 pools
2018.09.11:18:59:32.184: main Eth: primary pool: naw-eth.hiveon.net:4444
2018.09.11:18:59:32.184: main Starting GPU mining
2018.09.11:18:59:32.184: wdog Starting watchdog thread
2018.09.11:18:59:32.184: main Eth: Connecting to ethash pool naw-eth.hiveon.net:4444 (proto: EthProxy)
2018.09.11:18:59:32.236: eths Eth: Connected to ethash pool naw-eth.hiveon.net:4444 (54.183.35.85)
2018.09.11:18:59:32.236: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["xxxxxxx","x"]}
2018.09.11:18:59:32.264: eths Eth: Received: {"jsonrpc":"2.0","result":true,"id":1}
2018.09.11:18:59:32.265: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
2018.09.11:18:59:32.292: eths Eth: Received: {"jsonrpc":"2.0","result":["x","x","x"],"id":5}
2018.09.11:18:59:32.292: eths Eth: New job #694418d0 from naw-eth.hiveon.net:4444; diff: 4000MH
2018.09.11:18:59:32.292: GPU1 GPU1: Starting up... (0)
2018.09.11:18:59:32.292: GPU1 Eth: Generating light cache for epoch #210
2018.09.11:18:59:32.304: GPU2 GPU2: Starting up... (0)
2018.09.11:18:59:32.304: GPU3 GPU3: Starting up... (0)
2018.09.11:18:59:32.304: GPU4 GPU4: Starting up... (0)
2018.09.11:18:59:32.304: GPU5 GPU5: Starting up... (0)
2018.09.11:18:59:32.304: GPU6 GPU6: Starting up... (0)
2018.09.11:18:59:32.304: GPU7 GPU7: Starting up... (0)
2018.09.11:18:59:32.304: GPU8 GPU8: Starting up... (0)
2018.09.11:18:59:32.304: GPU9 GPU9: Starting up... (0)
2018.09.11:18:59:32.399: main Listening for CDM remote manager at port 3333 in read-only mode
2018.09.11:18:59:34.116: eths Eth: Received: { "jsonrpc":"2.0", "result": ["x","x","x"] }
2018.09.11:18:59:34.116: eths Eth: New job #eb3d7c98 from naw-eth.hiveon.net:4444; diff: 4000MH
2018.09.11:18:59:34.296: GPU1 GPU1: Using new optimized OpenCL kernels (device name 'Ellesmere')
2018.09.11:18:59:34.296: GPU1 GPU1: Allocating DAG (2.66) GB; good for epoch up to #212
2018.09.11:18:59:34.296: GPU1 GPU1: Allocating light cache buffer (42.5) MB; good for epoch up to #212
2018.09.11:18:59:34.391: GPU2 GPU2: Using new optimized OpenCL kernels (device name 'Ellesmere')
2018.09.11:18:59:34.391: GPU2 GPU2: Allocating DAG (2.66) GB; good for epoch up to #212
2018.09.11:18:59:34.391: GPU2 GPU2: Allocating light cache buffer (42.5) MB; good for epoch up to #212
2018.09.11:18:59:34.403: GPU1 GPU1: Generating DAG for epoch #210
2018.09.11:18:59:34.487: GPU3 GPU3: Using new optimized OpenCL kernels (device name 'Ellesmere')
2018.09.11:18:59:34.487: GPU3 GPU3: Allocating DAG (2.66) GB; good for epoch up to #212
2018.09.11:18:59:34.487: GPU3 GPU3: Allocating light cache buffer (42.5) MB; good for epoch up to #212
2018.09.11:18:59:34.498: GPU2 GPU2: Generating DAG for epoch #210
2018.09.11:18:59:34.582: GPU4 GPU4: Using new optimized OpenCL kernels (device name 'Ellesmere')
2018.09.11:18:59:34.582: GPU4 GPU4: Allocating DAG (2.66) GB; good for epoch up to #212
2018.09.11:18:59:34.582: GPU4 GPU4: Allocating light cache buffer (42.5) MB; good for epoch up to #212
2018.09.11:18:59:34.595: GPU3 GPU3: Generating DAG for epoch #210
2018.09.11:18:59:34.677: GPU5 GPU5: Using new optimized OpenCL kernels (device name 'Ellesmere')
2018.09.11:18:59:34.678: GPU5 GPU5: Allocating DAG (2.66) GB; good for epoch up to #212
2018.09.11:18:59:34.678: GPU5 GPU5: Allocating light cache buffer (42.5) MB; good for epoch up to #212
2018.09.11:18:59:34.690: GPU4 GPU4: Generating DAG for epoch #210
2018.09.11:18:59:34.773: GPU6 GPU6: Using new optimized OpenCL kernels (device name 'Ellesmere')
2018.09.11:18:59:34.773: GPU6 GPU6: Allocating DAG (2.66) GB; good for epoch up to #212
2018.09.11:18:59:34.773: GPU6 GPU6: Allocating light cache buffer (42.5) MB; good for epoch up to #212
2018.09.11:18:59:34.785: GPU5 GPU5: Generating DAG for epoch #210
2018.09.11:18:59:34.868: GPU7 GPU7: Using new optimized OpenCL kernels (device name 'Ellesmere')
2018.09.11:18:59:34.868: GPU7 GPU7: Allocating DAG (2.66) GB; good for epoch up to #212
2018.09.11:18:59:34.868: GPU7 GPU7: Allocating light cache buffer (42.5) MB; good for epoch up to #212
2018.09.11:18:59:34.881: GPU6 GPU6: Generating DAG for epoch #210
2018.09.11:18:59:34.964: GPU8 GPU8: Using new optimized OpenCL kernels (device name 'Ellesmere')
2018.09.11:18:59:34.964: GPU8 GPU8: Allocating DAG (2.66) GB; good for epoch up to #212
2018.09.11:18:59:34.964: GPU8 GPU8: Allocating light cache buffer (42.5) MB; good for epoch up to #212
2018.09.11:18:59:34.977: GPU7 GPU7: Generating DAG for epoch #210
2018.09.11:18:59:35.060: GPU9 GPU9: Using new optimized OpenCL kernels (device name 'Ellesmere')
2018.09.11:18:59:35.060: GPU9 GPU9: Allocating DAG (2.66) GB; good for epoch up to #212
2018.09.11:18:59:35.060: GPU9 GPU9: Allocating light cache buffer (42.5) MB; good for epoch up to #212
2018.09.11:18:59:35.072: GPU8 GPU8: Generating DAG for epoch #210
2018.09.11:18:59:35.167: GPU9 GPU9: Generating DAG for epoch #210
2018.09.11:18:59:36.162: GPU1 GPU1: DAG  31%
2018.09.11:18:59:36.181: GPU2 GPU2: DAG  38%
2018.09.11:18:59:36.410: GPU3 GPU3: DAG  31%
2018.09.11:18:59:36.502: GPU4 GPU4: DAG  31%
2018.09.11:18:59:36.600: GPU5 GPU5: DAG  31%
2018.09.11:18:59:36.696: GPU6 GPU6: DAG  31%
2018.09.11:18:59:36.755: GPU8 GPU8: DAG  38%
2018.09.11:18:59:36.791: GPU7 GPU7: DAG  31%
2018.09.11:18:59:36.851: GPU9 GPU9: DAG  38%
2018.09.11:18:59:36.860: eths Eth: Received: { "jsonrpc":"2.0", "result": ["x","x","x"] }
2018.09.11:18:59:36.860: eths Eth: New job #d5e03598 from naw-eth.hiveon.net:4444; diff: 4000MH
2018.09.11:18:59:37.205: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2018.09.11:18:59:37.205: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0) 7: 0.000 MH/s (0) 8: 0.000 MH/s (0) 9: 0.000 MH/s (0)
2018.09.11:18:59:37.796: GPU2 GPU2: DAG  75%
2018.09.11:18:59:37.912: GPU1 GPU1: DAG  63%
2018.09.11:18:59:38.158: GPU3 GPU3: DAG  63%
2018.09.11:18:59:38.248: GPU4 GPU4: DAG  63%
2018.09.11:18:59:38.348: GPU5 GPU5: DAG  63%
2018.09.11:18:59:38.369: GPU8 GPU8: DAG  75%
2018.09.11:18:59:38.444: GPU6 GPU6: DAG  63%
2018.09.11:18:59:38.464: GPU9 GPU9: DAG  75%
Post
Topic
Board Mining (Altcoins)
Re: PhoenixMiner 3.0c: fastest Ethereum/Ethash miner with lowest devfee (Windows)
by
salvo2002
on 11/09/2018, 01:23:11 UTC
Hi all, just reporting my results... on:

PhoenixMiner 3.5a -- First release with support for Linux

Code:
4.10.17-hiveos #1 SMP Sun Dec 10 08:48:43 EET 2017 x86_64 x86_64 x86_64 GNU/Linux
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.5 LTS"

Based on this post over at HiveOS community: https://forum.hiveos.farm/t/custom-miner-integration/4521/212

2-3 MH/s increase (reported hashrate) over Claymore 11.9, BUT a significant increase in stale shares! [using https://www.hiveon.net/ ETH pool]

screenshot:
https://ibb.co/fBu5h9
Post
Topic
Board Mining (Altcoins)
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.7 (Windows/Linux)
by
salvo2002
on 24/04/2018, 04:57:02 UTC
Quote from: Claymore on April 23, 2018, 08:18:22 PM
Quote from: salvo2002 on April 23, 2018, 05:27:15 PM
Thanks for the updated version @Claymore!

Quick question...on Linux [HiveOS] when I run two claymore dual instances [v11.6] eth only mode (split up a 10 card rig // -di 01234 in one mining eth and -di 56789 in the other mining etc) claymore reports the temps and fan settings for all 10 cards in both instances and I get OpenCL hangs. If I run one instance of claymore with all 10 cards its stable -- no OpenCL hangs.

I assume I get the OpenCL hangs when running two instances due to both instances trying to query temps & fan speeds at the same time. Is there a setting I am missing that only queries/controls the cards enabled in the instance  Huh
Use "-tt 0" to disable monitoring.

Ahhhh, thanks! Seems to be working fine after -tt 0 is used for the second instance and the first instance manages all of the cards, although -ttli and -ttdcr won't work in the second instance.
Post
Topic
Board Mining (Altcoins)
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.7 (Windows/Linux)
by
salvo2002
on 23/04/2018, 17:27:15 UTC
Thanks for the updated version @Claymore!

Quick question...on Linux [HiveOS] when I run two claymore dual instances [v11.6] eth only mode (split up a 10 card rig // -di 01234 in one mining eth and -di 56789 in the other mining etc) claymore reports the temps and fan settings for all 10 cards in both instances and I get OpenCL hangs. If I run one instance of claymore with all 10 cards its stable -- no OpenCL hangs.

I assume I get the OpenCL hangs when running two instances due to both instances trying to query temps & fan speeds at the same time. Is there a setting I am missing that only queries/controls the cards enabled in the instance  Huh