Topic: Linux mining distro for the Raspberry PI - MinePeon - page 37. (Read 685140 times)
Looks very nice! Hope the icy's and nanos will stop bother you, mine will arrive the next days...
Thanks guys.
I wish you all a good (and hopefully profitable) new year!
I am having one of those rare days when I have nothing else to do but work on MinePeon, have a look at this;-
New Graphs, Pool Order Updating, more drivers.... and more.
Now if I could only get those darn nanofury's to work..
Neil
I wish you all a good (and hopefully profitable) new year!
I am having one of those rare days when I have nothing else to do but work on MinePeon, have a look at this;-
New Graphs, Pool Order Updating, more drivers.... and more.
Now if I could only get those darn nanofury's to work..
Neil
+1 for the MineForeman
Happy New Year to Neil, tk1337 and to all participants of this thread.
Seems i cant get nanofury working on it.
Any ideas?
Any ideas?
Working on it now, I finally have a few to make it easier.
Beastlymac sent me a few of the new upcoming IceFury's (very nice bits of gear) and a MinePeon user was nice enough to sen me an actual nanofury.
They both arrived yesterday but I am still having problems, I get them detected OK now and seem to have most of the hidapi problems sorted but I am now getting errors like;-
Code:
[2013-12-31 08:32:48] NFY 0 failure, disabling!
[2013-12-31 08:32:48] mcp2210_spi_transfer: Failed to continue SPI transfer (60 bytes remaining)
[2013-12-31 08:32:48] NFY 0 failure, disabling!
[2013-12-31 08:32:48] mcp2210_set_cfg_gpio: Failed to set current GPIO config
[2013-12-31 08:32:48] mcp2210_spi_transfer: Failed to continue SPI transfer (60 bytes remaining)
[2013-12-31 08:32:48] NFY 0 failure, disabling!
[2013-12-31 08:32:48] mcp2210_spi_transfer: Failed to continue SPI transfer (60 bytes remaining)
[2013-12-31 08:32:48] NFY 0 failure, disabling!
[2013-12-31 08:32:48] mcp2210_spi_transfer: Failed to continue SPI transfer (60 bytes remaining)
[2013-12-31 08:32:48] NFY 0 failure, disabling!
[2013-12-31 08:32:48] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
[2013-12-31 08:32:49] mcp2210_spi_transfer: Failed to continue SPI transfer (60 bytes remaining)
[2013-12-31 08:32:49] mcp2210_set_cfg_gpio: Failed to set current GPIO config
[2013-12-31 08:32:49] NFY 0 failure, disabling!
[2013-12-31 08:32:49] mcp2210_spi_transfer: Failed to continue SPI transfer (60 bytes remaining)
[2013-12-31 08:32:49] NFY 0 failure, disabling!
[2013-12-31 08:32:49] mcp2210_spi_transfer: Failed to continue SPI transfer (60 bytes remaining)
While trying to initialise the devices. I am about to downgrade bfgminer to 3.8.0 to make sure it is not a problem that come in with 3.9.0 (it happens).
If that doesn't work I have compile a pole of debugging info and I am going to ask Luke-Jr for a hand (he is moving house at the moment so he is a bit busy).
Neil
Seems i cant get nanofury working on it.
Any ideas?
Any ideas?
Could somebody tell me what does mean and what to do, if I see this message in CGMINER, please?
BlackArrowBitFuryGPIO failed open /dev/mem (13)
I am using Butterflylabs Little Single SC.
BlackArrowBitFuryGPIO failed open /dev/mem (13)
I am using Butterflylabs Little Single SC.
Hi,
any body know how to git pull to the news master version?
Ther is a two day old master version in git. If i use git pull it will not load the master.
Thanks
Deagel
any body know how to git pull to the news master version?
Ther is a two day old master version in git. If i use git pull it will not load the master.
Thanks
Deagel
Someone tested it on BeagleBone (Black)?
One question.
I am using wireless conection by wifi dongle.
Many times connection is interrupted.
Why minepeon do not restart miner(raspberry pi) if he do not see devices ?
any command ?
I am using wireless conection by wifi dongle.
Many times connection is interrupted.
Why minepeon do not restart miner(raspberry pi) if he do not see devices ?
any command ?
Thank you for helping.
Should
sysvinit-tools be replaced with core/procps-ng?
Will not break something?
Should
sysvinit-tools be replaced with core/procps-ng?
Will not break something?
Quote
[minepeon@minepeon ~]$ sudo pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
alarm is up to date
aur is up to date
:: Starting full system upgrade...
:: Replace sysvinit-tools with core/procps-ng? [Y/n]
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
alarm is up to date
aur is up to date
:: Starting full system upgrade...
:: Replace sysvinit-tools with core/procps-ng? [Y/n]
It didn't affect my MinePeon when I did "sudo pacman -Syu" and said yes to everything.
But yeah, you should do everything that Neil says.
Minepeon is based on what distro?
I don't actually get along, I am so used to Debian. Basics of which distribution I have to learn/read to work better with Minepoen?
Still great product, btw.
I don't actually get along, I am so used to Debian. Basics of which distribution I have to learn/read to work better with Minepoen?
Still great product, btw.
Arch Linux (ARM).
I have nothing against Debian but Arch allows very specific builds customised to Architectures (Hence the Arch in it's name). It allowed me to build exactly what I wanted and nothing more, but it will still allow you to customise it however you like.
It also works on a rolling release system that make maintenance a lot easier (compared to versions with Debian OS's).
Last of all, when I started MinePeon Debian's (or rather rasperians) USB implementation was so bauked it crashed any USB miner within hours. I believe it still is and the miner guys do various work around's to make it work (i.e. they compile in their own libusb etc..).
Neil
Minepeon is based on what distro?
I don't actually get along, I am so used to Debian. Basics of which distribution I have to learn/read to work better with Minepoen?
Still great product, btw.
I don't actually get along, I am so used to Debian. Basics of which distribution I have to learn/read to work better with Minepoen?
Still great product, btw.
I'm a bit tired, and a bit dazed with all this mining stuff at the moment. 
What is the story with the IceFury USB miners? They seem to be a NanoFury clone.
Is the hidapi stuff included with MinePeon? Or did I try and install hidapi when trying to get the BlueFurys working? Jeesh, I can't remember.
Also, someone mentioned adding the -q option to bfgminer to improve performance - well I've tried it on my OpenWRT router, and performance is much, much improved, so much that my Blades and Cube run on the OpenWRT device when they used to switch to the Windows machine in preference.
What is the story with the IceFury USB miners? They seem to be a NanoFury clone.
Is the hidapi stuff included with MinePeon? Or did I try and install hidapi when trying to get the BlueFurys working? Jeesh, I can't remember.
Also, someone mentioned adding the -q option to bfgminer to improve performance - well I've tried it on my OpenWRT router, and performance is much, much improved, so much that my Blades and Cube run on the OpenWRT device when they used to switch to the Windows machine in preference.
last I heard IceFury was the continuation of the BlueFury/RedFury design.
It is a fun and novel way to kill SD cards though with of all of the writes.
bitcoind gets to about Feb 2013 (eventually), from then on it gets starts to seriously lag behind (taking ~24 hours to validate ~18hrs worth of blocks) until eventually it kills the SD cards - have been tempted to see if that can be used as a way of stress-testing SSD drives 
Would be interesting to see if microSDs using an SD adaptor can last longer or not under the same conditions.
Don't see why they would, microSD is just the same shitty chip on a smaller package.
It is a fun and novel way to kill SD cards though with of all of the writes.
bitcoind gets to about Feb 2013 (eventually), from then on it gets starts to seriously lag behind (taking ~24 hours to validate ~18hrs worth of blocks) until eventually it kills the SD cards - have been tempted to see if that can be used as a way of stress-testing SSD drives Would be interesting to see if microSDs using an SD adaptor can last longer or not under the same conditions.
I'm a bit tired, and a bit dazed with all this mining stuff at the moment.
What is the story with the IceFury USB miners? They seem to be a NanoFury clone.
Is the hidapi stuff included with MinePeon? Or did I try and install hidapi when trying to get the BlueFurys working? Jeesh, I can't remember.
Also, someone mentioned adding the -q option to bfgminer to improve performance - well I've tried it on my OpenWRT router, and performance is much, much improved, so much that my Blades and Cube run on the OpenWRT device when they used to switch to the Windows machine in preference.
What is the story with the IceFury USB miners? They seem to be a NanoFury clone.
Is the hidapi stuff included with MinePeon? Or did I try and install hidapi when trying to get the BlueFurys working? Jeesh, I can't remember.
Also, someone mentioned adding the -q option to bfgminer to improve performance - well I've tried it on my OpenWRT router, and performance is much, much improved, so much that my Blades and Cube run on the OpenWRT device when they used to switch to the Windows machine in preference.
last I heard IceFury was the continuation of the BlueFury/RedFury design.
Correct, I've got one coming to replace a BlueFury that went fizzt.
It is a fun and novel way to kill SD cards though with of all of the writes.
bitcoind gets to about Feb 2013 (eventually), from then on it gets starts to seriously lag behind (taking ~24 hours to validate ~18hrs worth of blocks) until eventually it kills the SD cards - have been tempted to see if that can be used as a way of stress-testing SSD drives 
If you have a desire to play/test the new cgminer 3.9.0, Kano has provided compiled versions for RPi here:
https://bitcointalksearch.org/topic/m.4101165
It was trivial to install:
From the stats page on the Web GUI, click Restart Miner. Confirm Miner Version says cgminer3.9.0a
Done.
https://bitcointalksearch.org/topic/m.4101165
It was trivial to install:
Code:
cd /opt/minepeon/bin
wget https://github.com/kanoi/cgminer-binaries/raw/master/RPi_Arch/cgminer-3.9.0a
sudo mv cgminer cgminer.old
sudo mv cgminer-3.9.0a cgminer
sudo chmod +x cgminer
Done.
I'm a bit tired, and a bit dazed with all this mining stuff at the moment.
What is the story with the IceFury USB miners? They seem to be a NanoFury clone.
Is the hidapi stuff included with MinePeon? Or did I try and install hidapi when trying to get the BlueFurys working? Jeesh, I can't remember.
Also, someone mentioned adding the -q option to bfgminer to improve performance - well I've tried it on my OpenWRT router, and performance is much, much improved, so much that my Blades and Cube run on the OpenWRT device when they used to switch to the Windows machine in preference.
What is the story with the IceFury USB miners? They seem to be a NanoFury clone.
Is the hidapi stuff included with MinePeon? Or did I try and install hidapi when trying to get the BlueFurys working? Jeesh, I can't remember.
Also, someone mentioned adding the -q option to bfgminer to improve performance - well I've tried it on my OpenWRT router, and performance is much, much improved, so much that my Blades and Cube run on the OpenWRT device when they used to switch to the Windows machine in preference.
last I heard IceFury was the continuation of the BlueFury/RedFury design.
Jump to: