Raspberry Pi miner?
-
@piezo
I don't know much about raspberry pi and such, but I got that same deadline problem when I changed the default setting from Jminer properties to a much higher value (when mining on a laptop):connectionTimeout=6000
The problem disappeared when I changed it to a lower one.
-
@Propagandalf
Ok thanks, i will give it a try.
The Burst-miner has the following default-options in the mining.conf{ "poolUrl" : "pool.burstcoin.eu:80", "submissionMaxDelay" : 30, "submissionMaxRetry" : 3, "submissionMaxDeadline" : 3888000, "socketTimeout" : 60, "maxBufferSizeMB" : 1024, "plots" : [ "/plot/folder/disk1/", "/plot/folder/disk2/", "/plot/folder/disk3/" ] }So i play around a little bit with the values of socketTimeout and submissionMaxDelay.
-
Changing socketTimeout and submissionMaxDelay didn't help but I found another advice for this Problem under "Issues" on github. Other users of the Burst-miner (https://github.com/uraymeiviar/burst-miner/releases) had the same problem.
- https://github.com/uraymeiviar/burst-miner/issues/1
- https://github.com/uraymeiviar/burst-miner/issues/2
uraymeiviar named this as possible reason for the different pool's deadline and miner's deadline:
- could be because of difference in plot data format
- wrong plot filename
- others also report this if their plot is "optimized" with a tool, i never tested this miner with "optimized" plot since i never optimize my plot
So my plots are not optimized and have the correct filename (I think the name is correct because with all other miners the plots could be mined perfectly). So the remaining possible reason is:
"could be because of difference in plot data format" , whatever that means. :)
-
Any updates
-
@Burstde wanted to throw in the creepminer. There is an open issue for the ARM version, but unfortunately I don't own a raspberry pi and I had no time for setting up an emulator.
Any help appreciated :)
-
@Creepsky Coincidentally I complied and am now running creepminer on an Odroid XU4 (arm7). I just followed the linux compile instructions and it just worked without any problems or modifications. It's been running for about 5 days now with no problems other than the webserver part does not update correctly and shows some strange info.
CPU and memory usage is very low and I am getting 45 MB/s read avg on a USB3 connected WD Green drive with a 1TB plot file.
-
@SuperDan Hi, how did you created plot files on your Odroid? I'm trying to use mdcct (on raspi2), but I stuck at gcc error "unrecognized command line option'-m64'.
-
Any update?
-
Also following, as this could be a game changer if people could easily mine on a rpi 3. Burst claims to be able to mine on phones, (which is sort of misleading). so a pi shouldn't be impossible at all In theory.
-
There are miner that successfully compiled the creepminer on their raspberry pi 3.
https://github.com/Creepsky/creepMiner/issues/78.. scroll at the very bottom and follow the instructions. In the end, the raspberry pi is nothing more than linux.
-
I wrote a miner that should work on the pi: https://github.com/Polyomino/burst-rminer
I use it with xudroids mining 32TB each over usb3
-
@polyomino What is the read time?
-
It takes me 8 min to read everything.
-
sorry if i missed it, but on pi2+ i can run windows or xubuntu right? If windows is xplotter and jminer working. thx


