BitMaker-hub
NerdMiner crashes
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
I have erased the flash completely and re-written firmware. Does not help here...
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?
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).
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.
Using zsolo pool with very low difficulty port 6056 do the same crash in an hour aprox. CKpool seams to be stable.
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.
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?
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!
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.
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!!!)
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?
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?
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.
@StarGateMiner
btc.zsolo.bid:6057
I'm using port 6056. How can we see any difference using 6057 or 6056?
@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?
@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?
I ran now 45minutes on btc.zsolo.bid:6057 and miner froze, no changes happening on screen, needed to restart it
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
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...
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?
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
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?
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..
THis will be solved with a propietary pool with low low low difficulty share
Are you creating a nerdpool, isn't it?
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.
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 :-(
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?
@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 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.