Search content
Sort by
Showing 6 of 6 results by panosarp
Re: [ANN] TRITON [TRIT][ASIC-RESISTANT] Updated June 5, 2018
Hello all.
So, i downloaded the latest gui wallet got my TRIT address, i mined myself some triton and i decided to send those coins to the exchange.
There was 1800 coins in the wallet, i am putting the exchange address and payment id, set the amount to send to 1700 hit send and get an error about transaction size bytes to large.
After that i notice that my wallet has 1200 coins and nothing send to the exchanged, in addition there was no outgoing transactions in the wallet history.
I reset the wallet, no joy, coins still missing.
I gave this thread some read and noticed others having problems with the gui wallet so decide to import the wallet keys to the cli wallet, except there is no import option
in the trit simplewallet.
A few days i am feeling brave and i decide give the gui wallet another try, i fill in the details and i send 600 coins to tradeogre.
This time the transaction is completed, 600 coins send with... 600 coins fee !!! For a total of 1200 spend.
So, i downloaded the latest gui wallet got my TRIT address, i mined myself some triton and i decided to send those coins to the exchange.
There was 1800 coins in the wallet, i am putting the exchange address and payment id, set the amount to send to 1700 hit send and get an error about transaction size bytes to large.
After that i notice that my wallet has 1200 coins and nothing send to the exchanged, in addition there was no outgoing transactions in the wallet history.
I reset the wallet, no joy, coins still missing.
I gave this thread some read and noticed others having problems with the gui wallet so decide to import the wallet keys to the cli wallet, except there is no import option
in the trit simplewallet.
A few days i am feeling brave and i decide give the gui wallet another try, i fill in the details and i send 600 coins to tradeogre.
This time the transaction is completed, 600 coins send with... 600 coins fee !!! For a total of 1200 spend.
Re: [ANN] [SUM] [PoW] Ṩ Bitsum - Telegram-oriented cryptocurrency
Greetings all,
is it possible to send to an address with payment id from telegram (stocks.exchange for example).
Or the cli wallet is needed for such transaction ?
is it possible to send to an address with payment id from telegram (stocks.exchange for example).
Or the cli wallet is needed for such transaction ?
Re: Genesis Mining Presents: SGMiner-GM - now with Zawawa's GG! [Updated 17/01/2017]
Quote
[18:21:13] Error -4 while attempting to enqueue kernel 0.
[18:21:13] GPU 3 failure, disabling!
[18:21:13] Error -4 while attempting to enqueue kernel 0.
[18:21:13] GPU 0 failure, disabling!
[18:21:13] Error -4 while attempting to enqueue kernel 0.
[18:21:13] GPU 2 failure, disabling!
[18:21:13] Error -4 while attempting to enqueue kernel 0.
[18:21:13] GPU 1 failure, disabling!
Any idea whats wrong?[18:21:13] GPU 3 failure, disabling!
[18:21:13] Error -4 while attempting to enqueue kernel 0.
[18:21:13] GPU 0 failure, disabling!
[18:21:13] Error -4 while attempting to enqueue kernel 0.
[18:21:13] GPU 2 failure, disabling!
[18:21:13] Error -4 while attempting to enqueue kernel 0.
[18:21:13] GPU 1 failure, disabling!
4*470 under Win7 and blockchain driver from 27/07, sgminer 5.5.5-gm
profile
Quote
"profiles":
[
{
"name": "xmr",
"algorithm": "cryptonight",
"rawintensity": "832",
"worksize": "8",
"gpu-threads": "1"
}
],
"default-profile": "xmr",
"no-extranonce": true,
"gpu-platform": "0"
[
{
"name": "xmr",
"algorithm": "cryptonight",
"rawintensity": "832",
"worksize": "8",
"gpu-threads": "1"
}
],
"default-profile": "xmr",
"no-extranonce": true,
"gpu-platform": "0"
I had the same problem when i was using windows 7 on my rigs.
Try version 5.5.4 it should work.
Also try "gpu-threads": "2"
Re: Gateless Gate: zawawa's open-source ZEC/ETH/XMR/PASC miner (256 S/s on RX 480)
Hello everyone.
I am having a problem with GG and cryptonight mining.
On every pool that has variable difficulty, eventually your miner will be assigned a high diff and if GG will not find a share for 90 seconds
it will disconnect, upon reconnect diff will be at whatever starting diff port you have chosen and the whole cycle repeats.
Overall hashing speed takes a hit from all the disconnects.
I think the following code is responsible for the disconnect (gatelessgate.c):
And the static initialization of the timeout a few lines above:
This disconnect does not occur on xmr_stak miners.
A workaround is setting a low enough fixed diff to ensure max share time < 90 sec, unfortunately most pools do not support fixed diff.
I am having a problem with GG and cryptonight mining.
On every pool that has variable difficulty, eventually your miner will be assigned a high diff and if GG will not find a share for 90 seconds
it will disconnect, upon reconnect diff will be at whatever starting diff port you have chosen and the whole cycle repeats.
Overall hashing speed takes a hit from all the disconnects.
I think the following code is responsible for the disconnect (gatelessgate.c):
Code:
/* The protocol specifies that notify messages should be sent
* every minute so if we fail to receive any for 90 seconds we
* assume the connection has been dropped and treat this pool
* as dead */
if (!sock_full(pool) && (sel_ret = select(pool->sock + 1, &rd, NULL, NULL, &timeout)) < 1) {
applog(LOG_DEBUG, "Stratum select failed on %s with value %d", get_pool_name(pool), sel_ret);
s = NULL;
} else
s = recv_line(pool);
if (!s) {
applog(LOG_NOTICE, "Stratum connection to %s interrupted", get_pool_name(pool));
pool->getfail_occasions++;
total_go++;
* every minute so if we fail to receive any for 90 seconds we
* assume the connection has been dropped and treat this pool
* as dead */
if (!sock_full(pool) && (sel_ret = select(pool->sock + 1, &rd, NULL, NULL, &timeout)) < 1) {
applog(LOG_DEBUG, "Stratum select failed on %s with value %d", get_pool_name(pool), sel_ret);
s = NULL;
} else
s = recv_line(pool);
if (!s) {
applog(LOG_NOTICE, "Stratum connection to %s interrupted", get_pool_name(pool));
pool->getfail_occasions++;
total_go++;
And the static initialization of the timeout a few lines above:
Code:
timeout.tv_sec = 90;
timeout.tv_usec = 0;
timeout.tv_usec = 0;
This disconnect does not occur on xmr_stak miners.
A workaround is setting a low enough fixed diff to ensure max share time < 90 sec, unfortunately most pools do not support fixed diff.
The official AMD blockchain driver for windows 7 x64 does not work (miners crash).
The leaked driver from robinh00d works but nothing can undervolt my RX570's, only OverdriveNTool works for a few seconds before reverting.
The solution that worked best is to use the leaked driver and the wattman from the official driver:
1. Install the official amd driver with amd settings
2. Without reboot install the leaked driver via device manager by going the "i have a disk" route (for all cards - one by one)
3. If you have a modified bios, run atikmdag-patcher and reboot
4. Use wattman to apply your mem clock and volt settings
5. Open miner, everything will be ok except undervolt, now with miner running make a small change to wattman and reapply (for each card one by one)
The voltages appear to be sticking for as long as the miner is running , except for the main card that reverts occasionally.
The leaked driver from robinh00d works but nothing can undervolt my RX570's, only OverdriveNTool works for a few seconds before reverting.
The solution that worked best is to use the leaked driver and the wattman from the official driver:
1. Install the official amd driver with amd settings
2. Without reboot install the leaked driver via device manager by going the "i have a disk" route (for all cards - one by one)
3. If you have a modified bios, run atikmdag-patcher and reboot
4. Use wattman to apply your mem clock and volt settings
5. Open miner, everything will be ok except undervolt, now with miner running make a small change to wattman and reapply (for each card one by one)
The voltages appear to be sticking for as long as the miner is running , except for the main card that reverts occasionally.
everything is works now. except the power with eth+SC almost sucks 140W.
Using OverdriveNTool from here: https://forums.guru3d.com/threads/overdriventool-tool-for-amd-polaris-gpus.416116
you can disable all power states except P7 for gpu and P2 for memory, that way the undervolt will be retained since gpu will always be at the highest performance state
and never throttle down.
The cards will consume more power when idle that way but for a mining ring that is irrelevant.
The official AMD blockchain driver for windows 7 x64 does not work (miners crash).
The leaked driver from robinh00d works but nothing can undervolt my RX570's, only OverdriveNTool works for a few seconds before reverting.
The solution that worked best is to use the leaked driver and the wattman from the official driver:
1. Install the official amd driver with amd settings
2. Without reboot install the leaked driver via device manager by going the "i have a disk" route (for all cards - one by one)
3. If you have a modified bios, run atikmdag-patcher and reboot
4. Use wattman to apply your mem clock and volt settings
5. Open miner, everything will be ok except undervolt, now with miner running make a small change to wattman and reapply (for each card one by one)
The voltages appear to be sticking for as long as the miner is running , except for the main card that reverts occasionally.
The leaked driver from robinh00d works but nothing can undervolt my RX570's, only OverdriveNTool works for a few seconds before reverting.
The solution that worked best is to use the leaked driver and the wattman from the official driver:
1. Install the official amd driver with amd settings
2. Without reboot install the leaked driver via device manager by going the "i have a disk" route (for all cards - one by one)
3. If you have a modified bios, run atikmdag-patcher and reboot
4. Use wattman to apply your mem clock and volt settings
5. Open miner, everything will be ok except undervolt, now with miner running make a small change to wattman and reapply (for each card one by one)
The voltages appear to be sticking for as long as the miner is running , except for the main card that reverts occasionally.