NerdMiner crashes #50

tbi88 · 2023-06-02T15:48:27Z

Hi

My NerdMiner crashes quite often. The longest runtime I have seen so far was a bit more than an hour. But it could also happen after a few minutes. This is what I see on the serial console.

Receiving: {"jsonrpc":"2.0","method":"mining.set_difficulty","params":[8000.0],"id":null}
  Receiving: {"jsonrpc":"2.0","method":"mining.notify","params":["00001cba","0f3ec3e037547d1b020e7d9bc424f67c05be412f030478220000000000000000","01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff140303230c04120b7a6400","01380000000001462c4825000000001976a91479d1987f15f5dbd6a3a0c53e4b1303fcee5fe4ef88ac00000000",["3022ea0180125737b2669149658ac05f8388948e2e4c935892fda6e2280f5204","3db41e03f608274c8088b7c63791c7ac20b9b29d84f9a2869387fb8cb46e3289","ce6c8f871c41b959e70bbd0d4188c9133bdcb78a414473c1335e6fa47b71d53b","2d89862b2b7ce5265ab6b32652dfdf33cf2075b2907e0eac538a35f68b4e074a","f022727e3313d13681a38a382553b17d17f42c4611e84597f2b8eb89fdb1f8db","85f658a477ca4708459dad82bd4de86d91e48720eecbecf049642417a4339eaf","e1d8acad8289e94c155d24e78bd70c36fe92edd1c7a02960949d4ba1ef0563c6"],"20000000","18055051","647a0b12",false],"id":null}
  Receiving: {"jsonrpc":"2.0","method":"mining.notify","params":["00001cbb","0f3ec3e037547d1b020e7d9bc424f67c05be412f030478220000000000000000","01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff140303230c041c0b7a6400","01380000000001462c4825000000001976a91479d1987f15f5dbd6a3a0c53e4b1303fcee5fe4ef88ac00000000",["3022ea0180125737b2669149658ac05f8388948e2e4c935892fda6e2280f5204","3db41e03f608274c8088b7c63791c7ac20b9b29d84f9a2869387fb8cb46e3289","ce6c8f871c41b959e70bbd0d4188c9133bdcb78a414473c1335e6fa47b71d53b","2d89862b2b7ce5265ab6b32652dfdf33cf2075b2907e0eac538a35f68b4e074a","f022727e3313d13681a38a382553b17d17f42c4611e84597f2b8eb89fdb1f8db","85f658a477ca4708459dad82bd4de86d91e48720eecbecf049642417a4339eaf","e1d8acad8289e94c155d24e78bd70c36fe92edd1c7a02960949d4ba1ef0563c6"],"20000000","18055051","647a0b1c",false],"id":null}
Guru Meditation Error: Core  1 panic'ed (Unhandled debug exception).
Debug exception reason: BREAK instr
Core  1 register dump:
PC      : 0x403743c0  PS      : 0x00060436  A0      : 0x00000000  A1      : 0x3fcebef0
A2      : 0x3fc9cb7c  A3      : 0x00000000  A4      : 0x00000000  A5      : 0x00000000
A6      : 0x00000000  A7      : 0x00000000  A8      : 0x82028748  A9      : 0x00000003
A10     : 0x3fca6a08  A11     : 0x00060023  A12     : 0x00000003  A13     : 0x82028748
A14     : 0x3fcebea0  A15     : 0x57f3eb07  SAR     : 0x13a2f05e  EXCCAUSE: 0x00000001
EXCVADDR: 0xffffffe0  LBEG    : 0x00000000  LEND    : 0x00000000  LCOUNT  : 0x00000000

Backtrace: 0x403743bd:0x3fcebef0

ELF file SHA256: 6d4e665f53b1e0e3

Rebooting...```

Any idea what is causing that?

Regards

The text was updated successfully, but these errors were encountered:

tbi88 · 2023-06-02T15:52:35Z

I have erased the flash completely and re-written firmware. Does not help here...

santitf · 2023-06-02T16:49:50Z

Hi, I received today my ESP32 s3 from the lilygo store.
Same problem with crashes, same time about an hour max before crash.
I’m trying differents cables or power adaptors.
how can I see the console?

santitf · 2023-06-02T21:24:00Z

News: I'm using zsolo pool under port 6057, but switching ckpool no crashes for 4 hours.
I see that zsolo has a "very low difficulty" using port 6056 (I will test it).

BitMaker-hub · 2023-06-03T11:53:20Z

Hi, I'm going to release an update recently that will solve most of this problems. There were related to Json deserealitzation. So this will no occur more.

santitf · 2023-06-03T17:24:45Z

Using zsolo pool with very low difficulty port 6056 do the same crash in an hour aprox.
CKpool seams to be stable.

Jir8taiwan · 2023-06-08T07:18:37Z

In my crash case, if I use solo mining such as zsolo and ckpool, it will keep going without problem.
however, when it is doing pool mining such as nicehash, binance or viabtc, it keeps crash loop and disconnect immediately.
I do not able to trace and figure out problem yet, but I try to leave this trouble for reference.
If someone has similar issue or helps, please do some advise.
Thanks a lot.

BitMaker-hub · 2023-06-08T10:34:36Z

HI all, It could be interesting to do some follow up with new beta version. Where stratum and Json parsing where improved.
Can you check and give feedback?

santitf · 2023-06-08T10:42:01Z

HI all, It could be interesting to do some follow up with new beta version. Where stratum and Json parsing where improved.
Can you check and give feedback?

Of course!

tbi88 · 2023-06-09T04:47:58Z

I updated to 1.5 beta yesterday evening. Since then it is running a bit less than 12 hours without an issue. Looks definitely better to me!

Thanks.

santitf · 2023-06-09T07:13:13Z

With 1.5 beta 18 hours pointing to zsolo using 6056 port (very low difficulty) withous problems
Shuting down screen, the temps goes down 5-9 degrees using the lilygo case and 26 celsius on room (awsome!!!)

StarGateMiner · 2023-06-09T07:31:59Z

Hi @BitMaker-hub Sadly for myself this beta "causes" crashed when I did not have crash before
Using:
solo.ckpool.org | 3333 | https://solo.ckpool.org/

Should I change pools? or perhaps a hard reformat may work?

StarGateMiner · 2023-06-09T07:33:24Z

I updated to 1.5 beta yesterday evening. Since then it is running a bit less than 12 hours without an issue. Looks definitely better to me!

Thanks.

Which pool?

santitf · 2023-06-09T08:14:04Z

Hi @BitMaker-hub Sadly for myself this beta "causes" crashed when I did not have crash before Using: solo.ckpool.org | 3333 | https://solo.ckpool.org/

Should I change pools? or perhaps a hard reformat may work?

Hi, I see a weird behavor with hash (go to zero, and up for a few seconds and return to zero) when the miner is connected to the PC after use console with esp tool. With 1.4 this problem no occurs. Needs power off/on to work correctly.

tbi88 · 2023-06-09T08:15:15Z

@StarGateMiner

btc.zsolo.bid:6057

santitf · 2023-06-09T08:20:02Z

@StarGateMiner

btc.zsolo.bid:6057

I'm using port 6056. How can we see any difference using 6057 or 6056?

StarGateMiner · 2023-06-09T08:43:38Z

@StarGateMiner
btc.zsolo.bid:6057

I'm using port 6056. How can we see any difference using 6057 or 6056?

I switched to Zsolo Pool and monitoring to see how things go, but weird thing I see no info in zsolo website of my hashrate stats, wondering if it will not display anything, anyone able to see stats on the site?

santitf · 2023-06-09T08:47:33Z

@StarGateMiner
btc.zsolo.bid:6057

I'm using port 6056. How can we see any difference using 6057 or 6056?

I switched to Zsolo Pool and monitoring to see how things go, but weird thing I see no info in zsolo website of my hashrate stats, wondering if it will not display anything, anyone able to see stats on the site?

I can't see info too, in zsolo website.
Is there a pool that sent info about hashrate doing solo mining?

StarGateMiner · 2023-06-09T08:59:02Z

I ran now 45minutes on btc.zsolo.bid:6057 and miner froze, no changes happening on screen, needed to restart it

santitf · 2023-06-09T09:16:05Z

I ran now 45minutes on btc.zsolo.bid:6057 and miner froze, no changes happening on screen, needed to restart it

Try port 6056, mine is mining for 16h

santitf · 2023-06-09T11:13:41Z

I try ViaBTC solo mining: can see my worker at web pool but after a few minutes change from online to offlne (ViaBTC dashboard), but the nerd shows hashrate...

StarGateMiner · 2023-06-09T11:43:22Z

I try ViaBTC solo mining: can see my worker at web pool but after a few minutes change from online to offlne (ViaBTC dashboard), but the nerd shows hashrate...

This is the reason I asked, because I want to prove in a way my miner is actually working when it comes to connection with the pool, do not wish to have false hope :-( is there a way to prove the miner is on a solo pool and working fully?

BitMaker-hub · 2023-06-09T11:53:16Z

Hi guys, I'll test with this pools but the problem is allways the same.
Miner is getting stratum notify from pool and mines.
It actualizes everytime a new job is send by pool, but what happen>
Pool expects an answer every 15 seconds more or less due to its difficulty.

If they see no answers or no shares sent they cut connection.

There is also a "keepAlive" method I implemented to try holding connection more.

But even pool disconnects socket, after NM detecting it reconnects.

THis will be solved with a propietary pool with low low low difficulty share

BitMaker-hub · 2023-06-09T12:01:03Z

ran now 45minutes on btc.zsolo.bid:6057 and miner froze, no changes happening on screen, needed to restart it

Hi, when did you loaded new firmware? are you using 1.5.1 or 1.5?

StarGateMiner · 2023-06-09T12:11:34Z

ran now 45minutes on btc.zsolo.bid:6057 and miner froze, no changes happening on screen, needed to restart it

Hi, when did you loaded new firmware? are you using 1.5.1 or 1.5?

My bad, I was using 1.5, upgraded now to 1.5.1 - will retry and monitor firstly on solo pool as this worked well for me originally..

santitf · 2023-06-09T12:25:52Z

THis will be solved with a propietary pool with low low low difficulty share

Are you creating a nerdpool, isn't it?

VitaminBTC · 2023-06-09T13:06:04Z

I suffered from crashing also - before upgrading to the firmware released yesterday, the hashrate would just show 0.00. After upgrading, the screen just froze (all sections).

I resolved it by simply swapping the USB-C cable i was using. I haven't had the freezing / crashing issue since. The cable i was using before was just a charging cable, but i swapped it for a data cable and it seems to be working so far.

StarGateMiner · 2023-06-09T17:59:09Z

Just checking in again, ok so with firmware 1.5.1 Im getting miner freezing, same setup was fine with 1.0 and went for days on the 3333 | https://solo.ckpool.org/ - so not sure whats happened :-(

tbi88 · 2023-06-09T18:09:40Z

Crazy! Mine is running since > 24 hours with btc.zsolo.bid:6057 with v1.5.1. Before with v1.4.0 I never had anything more than two hours.

Are we using the same hardware revisions?

ghost · 2023-06-09T18:23:45Z

@santitf Are you typing the "clean" url from zsolo (btc.zsolo.bid) or the full stratum link (stratum+tcp://btc.zsolo.bid:6056)?

Can't get mine to work, always stuck at 0.00 hash rate.

santitf · 2023-06-09T18:39:07Z

@santitf Are you typing the "clean" url from zsolo (btc.zsolo.bid) or the full stratum link (stratum+tcp://btc.zsolo.bid:6056)?

Can't get mine to work, always stuck at 0.00 hash rate.

I type the clean url and the port in the line below.

ghost · 2023-06-09T18:41:30Z

I got two boards and trying out different combinations of configs.

So far I tried:

1.5.1 with both zsolo 6056 and 6057
Same with 1.5.0
1.5.1 with cksolo

In all cases, the result is 0s across the board, even though ports are open.

StarGateMiner · 2023-06-10T06:47:26Z

Hi guys, I'll test with this pools but the problem is allways the same. Miner is getting stratum notify from pool and mines. It actualizes everytime a new job is send by pool, but what happen> Pool expects an answer every 15 seconds more or less due to its difficulty.

If they see no answers or no shares sent they cut connection.

There is also a "keepAlive" method I implemented to try holding connection more.

But even pool disconnects socket, after NM detecting it reconnects.

THis will be solved with a propietary pool with low low low difficulty share

I tried version 1.5.1 with different cable also, but issue is same for me on different pools, I get freezing problems where screen freeze and need to restart myself. How do I do a "Hard Reset" of the the device and try and reflash latest code, if issue still exists then something is up with the beta and I will go back to 1.4?

StarGateMiner · 2023-06-10T06:49:06Z

I got two boards and trying out different combinations of configs.

So far I tried:
* 1.5.1 with both zsolo 6056 and 6057

* Same with 1.5.0

* 1.5.1 with cksolo
In all cases, the result is 0s across the board, even though ports are open.

Thats a good point, Im also using Asus router, you saying we need to open ports on router, I did a port check and can see port 3333 on my device is closed?

santitf · 2023-06-10T08:51:36Z

I got two boards and trying out different combinations of configs.

So far I tried:

1.5.1 with both zsolo 6056 and 6057

Same with 1.5.0

1.5.1 with cksolo

In all cases, the result is 0s across the board, even though ports are open.

Hi! I never open ports for mining.
I have an asus router too. Please, check if AiProtection - Two-Way IPS is disable.

ghost · 2023-06-10T13:02:07Z

I have an asus router too. Please, check if AiProtection - Two-Way IPS is disable.

This seems to have fixed the issue! Thank you!

Also noticed the DNS Server set up on the router might be blocking certain domains associated with crypto mining. I myself use NextDNS, but switching to something mainstream like Google DNS allowed the miner to work for a couple of hours. I whitelisted zsolo.bid and ckpool.org, and now I can use NextDNS again.

PMK · 2023-06-10T18:25:28Z

Hi, I'm going to release an update recently that will solve most of this problems. There were related to Json deserealitzation. So this will no occur more.

I'm testing the beta version and got many times:

>>> Completed 0 share(s), 36475 Khashes, avg. hashrate 22.98 KH/s
Received message from pool
Receiving: {"result":true,"error":null,"id":6}
Parsed JSON: unknown
>>> Completed 0 share(s), 36491 Khashes, avg. hashrate 21.12 KH/s

It will continue on.

StarGateMiner · 2023-06-11T08:01:34Z

Hi, I'm going to release an update recently that will solve most of this problems. There were related to Json deserealitzation. So this will no occur more.

I'm testing the beta version and got many times:
>>> Completed 0 share(s), 36475 Khashes, avg. hashrate 22.98 KH/s
Received message from pool
Receiving: {"result":true,"error":null,"id":6}
Parsed JSON: unknown
>>> Completed 0 share(s), 36491 Khashes, avg. hashrate 21.12 KH/s
It will continue on.

Which pool you connecting to? can you try another pool?

StarGateMiner · 2023-06-11T09:30:53Z

I followed this guide: #59 (comment)
Seems to have helped with the freeze issue, I think I will flash this way going forward in the future.
Been on btc.zsolo.bid with port 6056 due to "Very Low Difficulty") now and no crash or freeze for over 45min where before it happened.

PMK · 2023-06-11T09:48:03Z

Hi, I'm going to release an update recently that will solve most of this problems. There were related to Json deserealitzation. So this will no occur more.

I'm testing the beta version and got many times:
>>> Completed 0 share(s), 36475 Khashes, avg. hashrate 22.98 KH/s
Received message from pool
Receiving: {"result":true,"error":null,"id":6}
Parsed JSON: unknown
>>> Completed 0 share(s), 36491 Khashes, avg. hashrate 21.12 KH/s
It will continue on.
Which pool you connecting to? can you try another pool?

btc.zsolo.bid:6056
It's not crashing as mentioned in this issue, but in the logs I see while I monitor it parsed the json and it doesn't know what the message from the pool was.

santitf · 2023-06-11T09:56:27Z

Hi, I'm going to release an update recently that will solve most of this problems. There were related to Json deserealitzation. So this will no occur more.

I'm testing the beta version and got many times:
Completed 0 share(s), 36475 Khashes, avg. hashrate 22.98 KH/s

Received message from pool

Receiving: {"result":true,"error":null,"id":6}

Parsed JSON: unknown

Completed 0 share(s), 36491 Khashes, avg. hashrate 21.12 KH/s
It will continue on.

Which pool you connecting to? can you try another pool?

btc.zsolo.bid:6056

It's not crashing as mentioned in this issue, but in the logs I see while I monitor it parsed the json and it doesn't know what the message from the pool was.

I see the same logs like you, using zsolo.

StarGateMiner · 2023-06-11T09:58:32Z

Hi, I'm going to release an update recently that will solve most of this problems. There were related to Json deserealitzation. So this will no occur more.

I'm testing the beta version and got many times:
>>> Completed 0 share(s), 36475 Khashes, avg. hashrate 22.98 KH/s
Received message from pool
Receiving: {"result":true,"error":null,"id":6}
Parsed JSON: unknown
>>> Completed 0 share(s), 36491 Khashes, avg. hashrate 21.12 KH/s
It will continue on.
Which pool you connecting to? can you try another pool?
btc.zsolo.bid:6056 It's not crashing as mentioned in this issue, but in the logs I see while I monitor it parsed the json and it doesn't know what the message from the pool was.

Noob question, how do I capture/see the logs?

StarGateMiner · 2023-06-13T15:11:58Z

Hi

My NerdMiner crashes quite often. The longest runtime I have seen so far was a bit more than an hour. But it could also happen after a few minutes. This is what I see on the serial console.

Receiving: {"jsonrpc":"2.0","method":"mining.set_difficulty","params":[8000.0],"id":null}
  Receiving: {"jsonrpc":"2.0","method":"mining.notify","params":["00001cba","0f3ec3e037547d1b020e7d9bc424f67c05be412f030478220000000000000000","01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff140303230c04120b7a6400","01380000000001462c4825000000001976a91479d1987f15f5dbd6a3a0c53e4b1303fcee5fe4ef88ac00000000",["3022ea0180125737b2669149658ac05f8388948e2e4c935892fda6e2280f5204","3db41e03f608274c8088b7c63791c7ac20b9b29d84f9a2869387fb8cb46e3289","ce6c8f871c41b959e70bbd0d4188c9133bdcb78a414473c1335e6fa47b71d53b","2d89862b2b7ce5265ab6b32652dfdf33cf2075b2907e0eac538a35f68b4e074a","f022727e3313d13681a38a382553b17d17f42c4611e84597f2b8eb89fdb1f8db","85f658a477ca4708459dad82bd4de86d91e48720eecbecf049642417a4339eaf","e1d8acad8289e94c155d24e78bd70c36fe92edd1c7a02960949d4ba1ef0563c6"],"20000000","18055051","647a0b12",false],"id":null}
  Receiving: {"jsonrpc":"2.0","method":"mining.notify","params":["00001cbb","0f3ec3e037547d1b020e7d9bc424f67c05be412f030478220000000000000000","01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff140303230c041c0b7a6400","01380000000001462c4825000000001976a91479d1987f15f5dbd6a3a0c53e4b1303fcee5fe4ef88ac00000000",["3022ea0180125737b2669149658ac05f8388948e2e4c935892fda6e2280f5204","3db41e03f608274c8088b7c63791c7ac20b9b29d84f9a2869387fb8cb46e3289","ce6c8f871c41b959e70bbd0d4188c9133bdcb78a414473c1335e6fa47b71d53b","2d89862b2b7ce5265ab6b32652dfdf33cf2075b2907e0eac538a35f68b4e074a","f022727e3313d13681a38a382553b17d17f42c4611e84597f2b8eb89fdb1f8db","85f658a477ca4708459dad82bd4de86d91e48720eecbecf049642417a4339eaf","e1d8acad8289e94c155d24e78bd70c36fe92edd1c7a02960949d4ba1ef0563c6"],"20000000","18055051","647a0b1c",false],"id":null}
Guru Meditation Error: Core  1 panic'ed (Unhandled debug exception).
Debug exception reason: BREAK instr
Core  1 register dump:
PC      : 0x403743c0  PS      : 0x00060436  A0      : 0x00000000  A1      : 0x3fcebef0
A2      : 0x3fc9cb7c  A3      : 0x00000000  A4      : 0x00000000  A5      : 0x00000000
A6      : 0x00000000  A7      : 0x00000000  A8      : 0x82028748  A9      : 0x00000003
A10     : 0x3fca6a08  A11     : 0x00060023  A12     : 0x00000003  A13     : 0x82028748
A14     : 0x3fcebea0  A15     : 0x57f3eb07  SAR     : 0x13a2f05e  EXCCAUSE: 0x00000001
EXCVADDR: 0xffffffe0  LBEG    : 0x00000000  LEND    : 0x00000000  LCOUNT  : 0x00000000

Backtrace: 0x403743bd:0x3fcebef0

ELF file SHA256: 6d4e665f53b1e0e3

Rebooting...```

Any idea what is causing that?

Regards

Noob question, how do I capture/see the logs?

PMK · 2023-06-13T19:51:38Z

Noob question, how do I capture/see the logs?

By monitoring the hardware. Connect via usb and run screen /dev/{console port} 115200, whereby the console port is the usb and 115200 is the baud rate.

munsterlander · 2023-11-20T01:14:29Z

Just got a brand new unit from the store with everything pre-installed. It will not stay up for longer than 8 minutes, then it crashes and reboots. The ESP Tool produces this console output:

Miner v2 starting......
Mounting File System...
mounted file system
reading config file
Opened configuration file
{
  "poolString": "public-pool.io",
  "portNumber": 21496,
  "btcString": "XXXXXXXXXXXXXXXXXXXXXXX",
  "gmtZon>>> Completed 0 share(s), 0 Khashes, avg. hashrate 0.00 KH/s
                                                                     >>> [i] Miner: newJob>false / inRun>false) - Client: connected>true / subscribed>false / wificonnected>true
                                                        >>> Completed 0 share(s), 0 Khashes, avg. hashrate 0.00 KH/s
                                                                                                                    >>> [i] Miner: newJob>false / inRun>false) - Client: connected>true / subscribed>false / wificonnected>true
                                                                                                       >>> Completed 0 share(s), 0 Khashes, avg. hashrate 0.00 KH/s
                                           >>> [i] Miner: newJob>false / inRun>false) - Client: connected>true / subscribed>false / wificonnected>true
                              >>> Completed 0 share(s), 0 Khashes, avg. hashrate 0.00 KH/s
                                                                                          >>> [i] Miner: newJob>false / inRun>false) - Client: connected>true / subscribed>false / wificonnected>true
                                                                             >>> Completed 0 share(s), 0 Khashes, avg. hashrate 0.00 KH/s
                 >>> [i] Miner: newJob>false / inRun>false) - Client: connected>true / subscribed>false / wificonnected>true
    >>> Completed 0 share(s), 0 Khashes, avg. hashrate 0.00 KH/s
                                                                >>> [i] Miner: newJob>false / inRun>false) - Client: connected>true / subscribed>false / wificonnected>true
                                                   >>> Completed 0 share(s), 0 Khashes, avg. hashrate 0.00 KH/s
                                                                                                               >>> [i] Miner: newJob>false / inRun>false) - Client: connected>true / subscribed>false / wificonnected>true
                                                                                                  >>> Completed 0 share(s), 0 Khashes, avg. hashrate 0.00 KH/s
                                      >>> [i] Miner: newJob>false / inRun>false) - Client: connected>true / subscribed>false / wificonnected>true
                         [WORKER] ==> Mining subscribe
                                                        Sending  : {"id": 1, "method": "mining.subscribe", "params": ["NerdMinerV2"]}

>>> Completed 0 share(s), 0 Khashes, avg. hashrate 0.00 KH/s
                                                            >>> [i] Miner: newJob>false / inRun>false) - Client: connected>true / subscribed>false / wificonnected>true
                                               Client not connected, trying to connect...
>>> Completed 0 share(s), 0 Khashes, avg. hashrate 0.00 KH/s
                                                            >>> [i] Miner: newJob>false / inRun>false) - Client: connected>true / subscribed>false / wificonnected>true
                                               >>> Completed 0 share(s), 0 Khashes, avg. hashrate 0.00 KH/s
                                                                                                           >>> [i] Miner: newJob>false / inRun>false) - Client: connected>true / subscribed>false / wificonnected>true
                                                                                              >>> Completed 0 share(s), 0 Khashes, avg. hashrate 0.00 KH/s
                                  >>> [i] Miner: newJob>false / inRun>false) - Client: connected>true / subscribed>false / wificonnected>true
                     >>> Completed 0 share(s), 0 Khashes, avg. hashrate 0.00 KH/s
                                                                                 >>> [i] Miner: newJob>false / inRun>false) - Client: connected>true / subscribed>false / wificonnected>true
                                                                    [WORKER] ==> Mining subscribe
                                                                                                   Sending  : {"id": 1, "method": "mining.subscribe", "params": ["NerdMinerV2"]}

Its just an endless stream of sneding, cannot connect, connected, subscribed false, sending....etc.

Any ideas on why it can't subscribe?

deyw-bit · 2023-11-20T16:59:06Z

Facing the same issue as described by munsterlander, with similar console output.
Testing new preinstalled device. The device connects to WiFi, switching screen works fine, it displays correctly the current block, current time, correct global hashrate, etc.
BUT it doesn't mine.
I have tried to change the configuration to various mining pool, but no success.
On the mining screen it shows: Block Templates 0, Best difficulty 0.0000 ... 0.00 KH/s.
I flashed it successfully with https://flasher.bitronics.store/ -- Successfully flashed NerdMinerv2 1.6.2 original board T-Display S3.
But the issue persists. The device keeps restarting after approx 12 to 15 minutes.

Console output:

`>>> [i] Miner: newJob>false / inRun>false) - Client: connected>true / subscribed>false / wificonnected>true
>>> Completed 0 share(s), 0 Khashes, avg. hashrate 0.00 KH/s
>>> [i] Miner: newJob>false / inRun>false) - Client: connected>true / subscribed>false / wificonnected>true
>>> Completed 0 share(s), 0 Khashes, avg. hashrate 0.00 KH/s
>>> [i] Miner: newJob>false / inRun>false) - Client: connected>true / subscribed>false / wificonnected>true
>>> Completed 0 share(s), 0 Khashes, avg. hashrate 0.00 KH/s
>>> [i] Miner: newJob>false / inRun>false) - Client: connected>true / subscribed>false / wificonnected>true
[WORKER] ==> Mining subscribe
Sending : {"id": 1, "method": "mining.subscribe", "params": ["NerdMinerV2"]}

Completed 0 share(s), 0 Khashes, avg. hashrate 0.00 KH/s
>>> [i] Miner: newJob>false / inRun>false) - Client: connected>true / subscribed>false / wificonnected>true
Client not connected, trying to connect...
Completed 0 share(s), 0 Khashes, avg. hashrate 0.00 KH/s
>>> [i] Miner: newJob>false / inRun>false) - Client: connected>true / subscribed>false / wificonnected>true
>>> Completed 0 share(s), 0 Khashes, avg. hashrate 0.00 KH/s
>>> [i] Miner: newJob>false / inRun>false) - Client: connected>true / subscribed>false / wificonnected>true
>>> Completed 0 share(s), 0 Khashes, avg. hashrate 0.00 KH/s
>>> [i] Miner: newJob>false / inRun>false) - Client: connected>true / subscribed>false / wificonnected>true
>>> Completed 0 share(s), 0 Khashes, avg. hashrate 0.00 KH/s
>>> [i] Miner: newJob>false / inRun>false) - Client: connected>true / subscribed>false / wificonnected>true
>>> Completed 0 share(s), 0 Khashes, avg. hashrate 0.00 KH/s
>>> [i] Miner: newJob>false / inRun>false) - Client: connected>true / subscribed>false / wificonnected>true`

munsterlander · 2023-11-21T05:06:24Z

Yup, basically seems like these are crapware now. I cannot get it to mine at all. Tried different pools, flashed, everything.

deyw-bit · 2023-11-21T10:59:14Z

Created a new issue for the problem related to not getting any block templates (device not able to connect to mining pool).

PMK mentioned this issue Jun 16, 2023

What is "normal" in time or amount of 16bit shares to get a 32bit share? #62

Closed

BitMaker-hub closed this as completed Jun 30, 2024

NerdMiner crashes #50

NerdMiner crashes #50

Comments

tbi88 commented Jun 2, 2023

tbi88 commented Jun 2, 2023

santitf commented Jun 2, 2023 • edited Loading

santitf commented Jun 2, 2023 • edited Loading

BitMaker-hub commented Jun 3, 2023

santitf commented Jun 3, 2023

Jir8taiwan commented Jun 8, 2023

BitMaker-hub commented Jun 8, 2023

santitf commented Jun 8, 2023

tbi88 commented Jun 9, 2023

santitf commented Jun 9, 2023 • edited Loading

StarGateMiner commented Jun 9, 2023

StarGateMiner commented Jun 9, 2023

santitf commented Jun 9, 2023

tbi88 commented Jun 9, 2023 • edited Loading

santitf commented Jun 9, 2023 • edited Loading

StarGateMiner commented Jun 9, 2023

santitf commented Jun 9, 2023

StarGateMiner commented Jun 9, 2023

santitf commented Jun 9, 2023

santitf commented Jun 9, 2023 • edited Loading

StarGateMiner commented Jun 9, 2023

BitMaker-hub commented Jun 9, 2023

BitMaker-hub commented Jun 9, 2023

StarGateMiner commented Jun 9, 2023

santitf commented Jun 9, 2023

VitaminBTC commented Jun 9, 2023 • edited Loading

StarGateMiner commented Jun 9, 2023 • edited Loading

tbi88 commented Jun 9, 2023

ghost commented Jun 9, 2023

santitf commented Jun 9, 2023

ghost commented Jun 9, 2023 • edited by ghost Loading

StarGateMiner commented Jun 10, 2023

StarGateMiner commented Jun 10, 2023

santitf commented Jun 10, 2023

ghost commented Jun 10, 2023

PMK commented Jun 10, 2023 • edited Loading

StarGateMiner commented Jun 11, 2023

StarGateMiner commented Jun 11, 2023

PMK commented Jun 11, 2023

santitf commented Jun 11, 2023

StarGateMiner commented Jun 11, 2023

StarGateMiner commented Jun 13, 2023

PMK commented Jun 13, 2023

munsterlander commented Nov 20, 2023 • edited Loading

deyw-bit commented Nov 20, 2023 • edited Loading

munsterlander commented Nov 21, 2023

deyw-bit commented Nov 21, 2023

santitf commented Jun 2, 2023 •

edited

Loading

santitf commented Jun 2, 2023 •

edited

Loading

santitf commented Jun 9, 2023 •

edited

Loading

tbi88 commented Jun 9, 2023 •

edited

Loading

santitf commented Jun 9, 2023 •

edited

Loading

santitf commented Jun 9, 2023 •

edited

Loading

VitaminBTC commented Jun 9, 2023 •

edited

Loading

StarGateMiner commented Jun 9, 2023 •

edited

Loading

ghost commented Jun 9, 2023 •

edited by ghost

Loading

PMK commented Jun 10, 2023 •

edited

Loading

munsterlander commented Nov 20, 2023 •

edited

Loading

deyw-bit commented Nov 20, 2023 •

edited

Loading