Pages:
Author

Topic: TT-Miner 2022.4.1 KAWPOW, PROGPOW, ETHASH, ETCHASH, EPIC, SHA512256D, GHOSTRIDER - page 17. (Read 132259 times)

member
Activity: 566
Merit: 16
Have strange issue with API with this 4.0.0 version. With 3.x there was no problem.

Miner get crash immediatelly during connection to API, no matter if API client connect during miner start or doing first connection after 5 minutes of mining.
Just crash immediatelly.



./TT-Miner -a PROGPOW -P stratum+tcp://[email protected]:3910 --api-bind 127.0.0.1:3333

TT-Miner - Version: 4.0.0 (Apr 20 2020 11:25:38)
(...)
****************** Start mining
Segmentation fault

My API client use this line to connect to API:
echo '{"id":0,"jsonrpc":"2.0","method":"miner_getstat1"}' | nc -q 0 127.0.0.1 3333

If I disable my API client, then miner works good.



Hi,

yes this bug is reported and I'm working on it. I will remove the linux version until a fix is available.
Sorry-
member
Activity: 707
Merit: 12
Have strange issue with API with this 4.0.0 version. With 3.x there was no problem.

Miner get crash immediatelly during connection to API, no matter if API client connect during miner start or doing first connection after 5 minutes of mining.
Just crash immediatelly.



./TT-Miner -a PROGPOW -P stratum+tcp://[email protected]:3910 --api-bind 127.0.0.1:3333

TT-Miner - Version: 4.0.0 (Apr 20 2020 11:25:38)
(...)
****************** Start mining
Segmentation fault

My API client use this line to connect to API:
echo '{"id":0,"jsonrpc":"2.0","method":"miner_getstat1"}' | nc -q 0 127.0.0.1 3333

If I disable my API client, then miner works good.
member
Activity: 566
Merit: 16
TT-Miner Release 4.0.0

I made some improvements in the algo structure. All algos should at least see some performance improvement on every system. The old ‘BCI’ progpow is removed since the project is dead. All other progpow versions are collected now in the new progpow algo. I have also added auto detection for algos. In most cases it is OK to just add the -coin XXX option to define coin, algo and protocol. For SSL/TCL protocols the addition of ‘stratum+ssl’ or ‘https’ is still required.

New coins added:
-   Raven (KAWPOW) - TESTNET
-   Veil     (ProgPoW) - TESTNET
-   Tecra   (MTP)
-   ERE     EtherCore (https://ethercore.org/)
-   HANA   Hanacoin (https://www.hanacoin.com/)


Windows: https://TradeProject.de/download/Miner/TT-Miner.zip
Linux:      https://TradeProject.de/download/Miner/TT-Miner.tar.xz

Please let me know if you have any issues.
member
Activity: 566
Merit: 16
..the miners for Sero are so buggy...I suspect the project is not really meant to be mined by 'outsiders'....it is being mined by a very limited few on the inside...I tried every miner..I have both AMD rigs, and Nvidia...none of the miners worked...many of them worked for other supported coins, but not Sero. Apart from all being in primitive Chinese stick figure language, there are no English pools. There are no detailed and reliable (easy to follow) miner setup guides. This project will fail, it cannot be mined by people outside their little clique. I call rubbish..plain and simple. STAY AWAY. Your wasting time paying attention to this chinese rubbish.

Do you want to share details of your problems so that ppl can help you?
member
Activity: 103
Merit: 10
..the miners for Sero are so buggy...I suspect the project is not really meant to be mined by 'outsiders'....it is being mined by a very limited few on the inside...I tried every miner..I have both AMD rigs, and Nvidia...none of the miners worked...many of them worked for other supported coins, but not Sero. Apart from all being in primitive Chinese stick figure language, there are no English pools. There are no detailed and reliable (easy to follow) miner setup guides. This project will fail, it cannot be mined by people outside their little clique. I call rubbish..plain and simple. STAY AWAY. Your wasting time paying attention to this chinese rubbish.
legendary
Activity: 2940
Merit: 1091
--- ChainWorks Industries ---
Intensity? ...

#crysx
Idunno, all other parameters were at it's default values.

I have seen this error many times before ...

On other miners admittedly, but usually because intensity is too high under default conditions. This may not be the issue of course, but try to drop the intensity down somehow and see.

A Low value would show you whether it mines or gives you the same error when the intensity is cut right back. If it mines, you know there is a limit that the miner will run at, so then it's just a matter of finding what that limit is.

I am unsure what parameter controls intensity in TTMiner, but that would be the first thing I would look at in this scenario.

#crysx
legendary
Activity: 2030
Merit: 1076
A humble Siberian miner
Intensity? ...

#crysx
Idunno, all other parameters were at it's default values.
legendary
Activity: 2940
Merit: 1091
--- ChainWorks Industries ---
On latest HiveOS I have the following problem with TT-Miner when I'm trying to mine Sero:



The only extra argument I configure on HiveOS side is
Code:
-coin SERO
How can I fix this?

Intensity? ...

#crysx
legendary
Activity: 2030
Merit: 1076
A humble Siberian miner
On latest HiveOS I have the following problem with TT-Miner when I'm trying to mine Sero:



The only extra argument I configure on HiveOS side is
Code:
-coin SERO
How can I fix this?
newbie
Activity: 107
Merit: 0
Hey. I have such a bug on all farms in windows events, it pops up every 10-15 minutes


Bad application name: TT-Miner.exe, version: 3.2.2.61, timestamp: 0x5df1c194
Failed module name: unknown, version: 0.0.0.0, timestamp: 0x00000000
Exception Code: 0xc0000005
Error offset: 0x0000000000000000
Bad Process ID: 0x7b8
Application start time: 0x01d5e0e127209cb9
The path of the failed application: C: \ Users \ Ti \ AppData \ Local \ AwesomeMiner \ tt-miner-3.2.2_1 \ TT-Miner.exe
Failed module path: unknown
Report ID: a85b7103-f0c0-44e4-bec2-957c1ef8b3c9
The full name of the failed package:
Bad Package Application Code:

Bad application name: TT-Miner.exe, version: 3.2.2.61, timestamp: 0x5df1c194
Failed module name: unknown, version: 0.0.0.0, timestamp: 0x00000000
Exception Code: 0xc0000005
Error offset: 0x0000000000000000
Bad Process ID: 0x324
Application start-up time: 0x01d5e184273d0377
The path of the failed application: C: \ Users \ nokau \ AppData \ Local \ AwesomeMiner \ tt-miner-3.2.2_1 \ TT-Miner.exe
Failed module path: unknown
Report ID: 8a82c6b1-fbb3-4c43-a3f7-afbdfcb8f4dc
The full name of the failed package:
Bad Package Application Code:

On one farm, this leads to a reboot.
sr. member
Activity: 954
Merit: 250
Which miner is the best to mine XZC on gtx 1080ti?
member
Activity: 297
Merit: 10
You could still fix that bug though Smiley
member
Activity: 566
Merit: 16
Actually nevermind, I tested with a different pool and your miner is slower than progminer for progpowz on 1070 and 1080ti (and then there's also the fee)

OK-np
member
Activity: 297
Merit: 10
Actually nevermind, I tested with a different pool and your miner is slower than progminer for progpowz on 1070 and 1080ti (and then there's also the fee)
member
Activity: 566
Merit: 16
stratum+tcp does not work (that's already the default). ethproxy+tcp:// seems to work (Sends eth_submitLogin), but now i have a new problem as the username has a dot "." which your miner confuses with workername. I already tried hex encoding it as %2e but then your miner actually sends %2e to the server instead of dot "." ... what's the fix?

tt-miner -a PROGPOWZ -P ethproxy+tcp://foo.123456:[email protected]:3344

Note that the required username is "foo.123456". There is no workername but tt-miner thinks 123456 is a workername and sets the username to "foo". Using "foo%2e123456" doesn't work as it doesn't look you translate hex encoded strings (you're sending them as is to the pool).

Ah- OK. got your point. Let me fix.
member
Activity: 297
Merit: 10
stratum+tcp does not work (that's already the default). ethproxy+tcp:// seems to work (Sends eth_submitLogin), but now i have a new problem as the username has a dot "." which your miner confuses with workername. I already tried hex encoding it as %2e but then your miner actually sends %2e to the server instead of dot "." ... what's the fix?

tt-miner -a PROGPOWZ -P ethproxy+tcp://foo.123456:[email protected]:3344

Note that the required username is "foo.123456". There is no workername but tt-miner thinks 123456 is a workername and sets the username to "foo". Using "foo%2e123456" doesn't work as it doesn't look you translate hex encoded strings (you're sending them as is to the pool).
member
Activity: 566
Merit: 16
Hi,

try stratum+tcp or stratum1+tcp. Would be helpful if you send PM me a commandline so that I have more information.
member
Activity: 297
Merit: 10
How do I specify ethproxy protocol (supporting eth_submitWork etc) for progpowz? Currently this miner doesn't work with MRR, it submits stratum and MRR doesn't respond, then it drops connection

progminer (fork of ethminer) does, and I'm forced to use the ethproxy protocol, which ethminer knows of
jr. member
Activity: 41
Merit: 1
So silent in here, no changes in excavator? Sad
Pages:
Jump to: