 Show Posts
|
|
Pages: [1]
|
Some E3's can be difficult to flash, use a 2gb micro sd card formatted to FAT32 and extract the firmware onto the root of the micro sd card, move jumper over as-per bitmain instructions. Honestly? there is a file located located in root called "core" which I am told is just a core dump file and taking up a ton of space which is preventing the firmware update from installing, I just ssh to the miner, locate the file in "/" and remove it with "rm core" then exit and run the firmware upgrade from the web gui without issue, it was really easy. |
|
|
|
Trying to run miner for ckb on 1070ti's and cannot get miner to launch, any ideas as to what I may be doing wrong? C:\NBMiner_26.2_Win\NBMiner_Win>nbminer -a eaglesong -o stratum+tcp://ckb.f2pool.com:4300 -u xxxx.xx:x
[12:22:02] INFO - ----------------------------------------------
[12:22:02] INFO - | NBMiner |
[12:22:02] INFO - | Crypto GPU Miner |
[12:22:02] INFO - | 26.2 |
[12:22:02] INFO - ----------------------------------------------
[12:22:02] INFO - ALGO: eaglesong
[12:22:02] INFO - URL: stratum+tcp://ckb.f2pool.com:4300
[12:22:02] INFO - USER: xxxx.xx:x
[12:22:02] INFO - TEMP-LIMIT: 90C
[12:22:02] ERROR - !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[12:22:02] ERROR - Mining program unexpected exit.
[12:22:02] ERROR - Reason: Process crashed
[12:22:02] ERROR - Restart miner after 10 secs ...
[12:22:02] ERROR - !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
|
|
|
|
Server = IP of the Diskcoind server ?????
Port = 63336 #rpcport of Diskcoind server
UpdaterAddr = IP of the Diskcoind server ???????
UpdaterPort = 63336 #rpcport of Diskcoind server
InfoAddr = IP of the Diskcoind server ??????
InfoPort = 63336 #rpcport for Diskcoind server |
|
|
|
My original post was a result of changing the "Port" information in the miner.conf from 63336 to 63335, looking at the listener on the diskcoind server, tcp ipv4 is listening on 63335 and ipv6 is on 63336 which is the default and I changed it because I am not routing ipv6. Since, I nage changed it back to 63336 and the logs now read differently error however the miner still performs the same. It opens but does not do anything. "Mode" : "pool",
"Server" : "192.168.1.109",
"Port": 63336,
"UpdaterAddr" : "192.168.1.109",
"UpdaterPort": 63336,
"InfoAddr" : "192.168.1.109",
"InfoPort": 63336,
"EnableProxy": false,
"ProxyPort": 8126,
"Paths": [
"D:\\"
], 15:57:34 === Config loaded ===
15:57:34 Miner path: C:\Users\dc-test\Downloads\dcminer.0714\dcminer.0714\
15:57:34 Searching servers...
15:57:34 Address: 192.168.1.109 defined as: 192.168.1.109
15:57:34 Address: 192.168.1.109 defined as: 192.168.1.109
15:57:34 Address: 192.168.1.109 defined as: 192.168.1.109
15:57:34 Updater thread started
15:57:34 Update mining info
15:57:34 * GMI: Received: HTTP/1.0 403 Forbidden\r\nContent-Type: text/html; charset=ISO-8859-1\r\nConnection: close\r\n\r\n
15:57:34 *! GMI: error parsing JSON message from pool
15:57:35 * GMI: Received: HTTP/1.0 403 Forbidden\r\nContent-Type: text/html; charset=ISO-8859-1\r\nConnection: close\r\n\r\n
15:57:35 *! GMI: error parsing JSON message from pool
15:57:36 * GMI: Received: HTTP/1.0 403 Forbidden\r\nContent-Type: text/html; charset=ISO-8859-1\r\nConnection: close\r\n\r\n
15:57:36 *! GMI: error parsing JSON message from pool
15:57:37 * GMI: Received: HTTP/1.0 403 Forbidden\r\nContent-Type: text/html; charset=ISO-8859-1\r\nConnection: close\r\n\r\n
15:57:37 *! GMI: error parsing JSON message from pool
15:57:38 * GMI: Received: HTTP/1.0 403 Forbidden\r\nContent-Type: text/html; charset=ISO-8859-1\r\nConnection: close\r\n\r\n
15:57:38 *! GMI: error parsing JSON message from pool
15:57:39 * GMI: Received: HTTP/1.0 403 Forbidden\r\nContent-Type: text/html; charset=ISO-8859-1\r\nConnection: close\r\n\r\n
15:57:39 *! GMI: error parsing JSON message from pool |
|
|
|
I am still struggling to get the miner to run, can someone tell me what this means in the miner logs? 11:58:31 === Config loaded ===
11:58:31 Miner path: C:\Users\dc-test\Downloads\dcminer.0714\dcminer.0714\
11:58:31 Searching servers...
11:58:31 Address: 192.168.1.109 defined as: 192.168.1.109
11:58:31 Address: 192.168.1.109 defined as: 192.168.1.109
11:58:31 Address: 192.168.1.109 defined as: 192.168.1.109
11:58:31 Updater thread started
11:58:31 Update mining info
11:58:31 *! GMI: get mining info failed:: 10054
11:58:32 *! GMI: get mining info failed:: 10054
11:58:33 *! GMI: get mining info failed:: 10054
11:58:34 *! GMI: get mining info failed:: 10054
11:58:35 *! GMI: get mining info failed:: 10054
11:58:36 *! GMI: get mining info failed:: 10054
11:58:37 *! GMI: get mining info failed:: 10054
11:58:38 * GMI: Received:
11:58:38 *! GMI: error message from pool
11:58:39 *! GMI: get mining info failed:: 10054
11:58:40 *! GMI: get mining info failed:: 10054 The miner opens and doesn't do anything. I unplugged the test drives and then it at least appears runs through the config then displays error that no plts were found which makes since and now has me wondering about my plot process? I use that PID gen page to create a PID and used that number in turboplotter to plot the disk? I wonder if I did this correct? detail instruction are non existent for this project. I have been trying for a few weeks not to even get it to run. Could someone provide so clarity for these messages? |
|
|
|
Burst/bhd/boom use uint64 PID, the PID that Diskcoin uses is less than uint56, we all use the same POC2 file.
At present, the global POC hashrate is around 2000p, and the hashrate less than uint56 occupies 1/256, less than 10P, which means that everyone needs to replot files. Replot will take time, the advantage of this is that there will be no huge hashrate in DISC mining immediately, which can avoid huge hashrate attacks for Diskcoin, such as 51% attacks or miner-activated softfork (MASF), thus ensuring the safety and stability on the chain. And it will be fairer for everyone.
Must admit, I was excited to get in on a new project from the beginning however, the chance of me "replotting" is zero. I will continue following the project to see if someone can get it to support our existing poc2 plots. |
|
|
|
are you open to dallas? if so, how much power are you needing?
Yes, open to Dallas as long as terms are reasonable. 4 D3s (1200 W each) and 2 L3s (~800W) and 1 Pandaminer GPU (~1250W). Roughly 7.6 KW Please share your details or PM me. I'm open to Dallas as well PM info please? |
|
|
|
|
