Search content
Sort by
Showing 20 of 32 results by soifigured
Re: [OS] nvOC easy-to-use Linux Nvidia Mining vBASIC || Community Edition 2.0
Are there any plans to add in the Funokoshi equihash miner?
I just tried it quickly by grabbing the v2.3 of funakoshiMiner (executable) from here:
https://github.com/funakoshi2718/funakoshi-miner/releases
After I chmod'ed the file to make it executable, I was able to give it a quick test on my 3 GPU Test rig by starting it up with this command line:
./funakoshiMiner -cd 0 1 2 -l zec.suprnova.cc:2242 -u .Miner1
So, if you want to mine with it, there is no compatibility with nvOC 19-2.0 Community Edition. There is no compiling necessary (nore possible for that matter since he doesn't provide source).
Thanks for the response! I was wondering if there were any plans to add it into the script files so that it would auto launch on boot like EWBF and DSTM do.
Very very tempted to order this hub, anyone comment if it's any good ??
http://www.sipolar.com/page172.html?product_id=18
https://www.amazon.co.uk/Sipolar-Port-Charge-Phone-Tablet-Black/dp/B01K4MZQJ8
http://www.sipolar.com/page172.html?product_id=18
https://www.amazon.co.uk/Sipolar-Port-Charge-Phone-Tablet-Black/dp/B01K4MZQJ8
I can't speak for the 10 port but I have two of the sipolar a223 20 port hubs and they are working well for me and the way the ports are laid out on the a223 you can actually fit 12 moonlanders.
Re: Official FutureBit Moonlander 2 Driver and Support Thread
Has anyone figured out a good way to single out a problematic miner in an array of miners? I rather not have to run them all individually to find the problem child.
how is one a problem? you can usually tell if one jammed up by looking at the red light..
I have an array of 30 of these things and there are 1 or 2 that will drop off to 2MH or so after a few hours, staring at blinking lights looking for the one that is blinking slightly slower doesn't seem like the most efficient use of time. I was hoping someone had a clever trick or something they knew of.
If you see the tty devices then try running it with sudo.
Could be just a permissions thing
Could be just a permissions thing
Holy crap! I was not launching my miner with sudo! That is probably it, cuz I could see the devices with lsusb. Welp the devil is in the details. I'll try that and report back.
Thanks again!
Welp turned out to be a permissions thing, I'm up and running. Thanks!
If you see the tty devices then try running it with sudo.
Could be just a permissions thing
Could be just a permissions thing
Holy crap! I was not launching my miner with sudo! That is probably it, cuz I could see the devices with lsusb. Welp the devil is in the details. I'll try that and report back.
Thanks again!
I would check /var/log/messages for any messages and also look for /dev/tty* devices ?
I'll give that a shot tonight, thanks!
Yep latest image from about 2 months ago.
EDIT: what hub are you using ?
EDIT: what hub are you using ?
Sipolar A-223. What confuses me is that they work under Mich's provided minera image, but they don't work under raspian-stretch or ubuntu-mate. I'll fire up bfgminer and it will return "no devices detected, waiting for devices." I'm a little stumped. I'm pretty sure I added the relevant dependencies, hopefully someone can provide a little insight.
My first moonlander 2 just turned up ! 
all working. This is a picture of my setup:
https://imgur.com/a/U68EH
Consists of:
1) Raspberry PI 3 with official Rapsberry PI 3 power supply
2) Cheap USB 2.0 7 port hub - Pluscom Model u7PH-3A (not using the power supply as the Pi seems to be enough for this) cascaded into:
3) Plugable USB 3.0 7 port Hub (inc 12V 5A 60w psu) - Model: USB3-HUB7BC
3 more are in the post in the way so will be testing more plugged into the same when i can (going to try and do 7x all at the time time via extension cables)
Been running now for about an hour now litecoinpool reporting hashing at 3,498kH/s (so far so good!)
Boom!
all working. This is a picture of my setup:https://imgur.com/a/U68EH
Consists of:
1) Raspberry PI 3 with official Rapsberry PI 3 power supply
2) Cheap USB 2.0 7 port hub - Pluscom Model u7PH-3A (not using the power supply as the Pi seems to be enough for this) cascaded into:
3) Plugable USB 3.0 7 port Hub (inc 12V 5A 60w psu) - Model: USB3-HUB7BC
3 more are in the post in the way so will be testing more plugged into the same when i can (going to try and do 7x all at the time time via extension cables)
Been running now for about an hour now litecoinpool reporting hashing at 3,498kH/s (so far so good!)
Boom!
UPDATE:. This is still running plus I've now expanded it to use 4x moonlanders at 756 speed. One is using a USB extension cable but seems to be ok. All getting around 4,492 kH/s from litecoinpool
Are you using raspian stretch? My moonlander are not being detected under stretch.
Re: Official FutureBit Moonlander 2 Driver and Support Thread
Tried running a few miners on another raspberry pi running raspian stretch, but I ran into an issue. lsusb shows the driver loaded is cygnal and not silabs. Is there a quick kernel patch that can be applied or do we have to compile the drivers from silabs and insert them?
Re: Official FutureBit Moonlander 2 Driver and Support Thread
Rasberry Pi Raspbian OS
So this relates to the Moonlanders, but is more of a Raspbian question
When I reboot my pi, it reassigns all USBs ttyUSB0 becomes 2, 4 becomes 8.....etc....
I am using 4 v1.2 Mooonlanders and 8 v2.0 Moonlanders, so I need to specify the USB in order to get them to work with the correct bfgminer.
Any idea on how I can lock them down to their # even after reboot?
This problem may or may not continue once jstefanop enables the new bfgminer to run both, but I'm guessing I'll still need to identify by ttyUSB#
So this relates to the Moonlanders, but is more of a Raspbian question
When I reboot my pi, it reassigns all USBs ttyUSB0 becomes 2, 4 becomes 8.....etc....
I am using 4 v1.2 Mooonlanders and 8 v2.0 Moonlanders, so I need to specify the USB in order to get them to work with the correct bfgminer.
Any idea on how I can lock them down to their # even after reboot?
This problem may or may not continue once jstefanop enables the new bfgminer to run both, but I'm guessing I'll still need to identify by ttyUSB#
I haven't tried this with the moonlanders yet, but I know when using bfg with older gridseeds you could call them out by serial number. When you go to manage devices in bfg you can find the serial number of the device (It is different than what is found on the sticker). Give that a shot, I'm very curious to see if it works out. I don't have any syntax examples with me. It's been a good long while since I've used a gridseed but I'll try to post one up after I get home from work tonight.
You can also call out the devices by usb bus instead of port. Not sure if the rpi has more than one usb bus though.
Re: Official FutureBit Moonlander 2 Driver and Support Thread
Just a bit of a dumb question ...
Do these devices need to be plugged in directly into the USB port/hub, or could you use an USB extension from the hub to the device?
Something like this: https://www.sweetwater.com/store/detail/LokSaverCable
TIA.
Do these devices need to be plugged in directly into the USB port/hub, or could you use an USB extension from the hub to the device?
Something like this: https://www.sweetwater.com/store/detail/LokSaverCable
TIA.
You can use them with USB extensions. I'm using usb extensions to put a little space between mine, they still hash well. I'm using ones from monoprice.com. They can be had for pretty cheap through them.
Here's 11 of them running on a Sipolar hub
Would help to know what speed you are able to run them at on that hub.
I'm running them at 756 getting an average of 4.4mh/s per stick.
Wow I'm lucky to get 4.0-4.25 at that speed on the same hub and clockspeed.
Re: Official FutureBit Moonlander 2 Driver and Support Thread
Has anyone figured out a good way to single out a problematic miner in an array of miners? I rather not have to run them all individually to find the problem child.
how is one a problem? you can usually tell if one jammed up by looking at the red light..
I got a couple miners that will slow down to 2 MH, so the red light will still blink.
I think this is not the stick issue (rather pool issue). Which pool you are using?
I face the same problem when tried to rent them on miningrentals. When were not rented (and mined on my specific pool - litecoinpool.org) everything was fine ... but once someone rent them the hashrate started slowly dropping to less than 1MHs ... I had to restart them few times.
I'm mining on litecoinpool.org. The sticks will mine just fine for a few hours then they'll slow down to 2MH or so.
Well, then I was wrong
I'm now 18 hours without stop on litecoinpool.org (would be more but there was electricity outage).
Doh! Sometimes I'll have a good run and they'll go for like 2 days or so before slowing down, but more often than not it's just a couple hours.
Re: Official FutureBit Moonlander 2 Driver and Support Thread
Has anyone figured out a good way to single out a problematic miner in an array of miners? I rather not have to run them all individually to find the problem child.
how is one a problem? you can usually tell if one jammed up by looking at the red light..
I got a couple miners that will slow down to 2 MH, so the red light will still blink.
I think this is not the stick issue (rather pool issue). Which pool you are using?
I face the same problem when tried to rent them on miningrentals. When were not rented (and mined on my specific pool - litecoinpool.org) everything was fine ... but once someone rent them the hashrate started slowly dropping to less than 1MHs ... I had to restart them few times.
I'm mining on litecoinpool.org. The sticks will mine just fine for a few hours then they'll slow down to 2MH or so.
I use litecoinpool.org and it seems ok with me - Been running for nearly a week with no issues (getting a constant 4.44Mh/s) and this is my setup:
https://bitcointalk.org/index.php?topic=2455609.msg25653813#msg25653813
What setup do you have? hub / os / etc ?
I'm currently running 24 of them on two sipolar A-223's on a windows 10 machine. I chose that particular hub because it had an integrated 200w power supply, seems to be pretty good. Eventually I want to move these over to a rpi and use Minera, but I'll cross that bridge when I get there.
Re: Official FutureBit Moonlander 2 Driver and Support Thread
Has anyone figured out a good way to single out a problematic miner in an array of miners? I rather not have to run them all individually to find the problem child.
how is one a problem? you can usually tell if one jammed up by looking at the red light..
I got a couple miners that will slow down to 2 MH, so the red light will still blink.
I think this is not the stick issue (rather pool issue). Which pool you are using?
I face the same problem when tried to rent them on miningrentals. When were not rented (and mined on my specific pool - litecoinpool.org) everything was fine ... but once someone rent them the hashrate started slowly dropping to less than 1MHs ... I had to restart them few times.
I'm mining on litecoinpool.org. The sticks will mine just fine for a few hours then they'll slow down to 2MH or so.
Re: Official FutureBit Moonlander 2 Driver and Support Thread
Has anyone figured out a good way to single out a problematic miner in an array of miners? I rather not have to run them all individually to find the problem child.
how is one a problem? you can usually tell if one jammed up by looking at the red light..
I got a couple miners that will slow down to 2 MH, so the red light will still blink.
Re: [Minera v0.8.1] Your next mining dashboard - Networked/CPUminer/CGminer/BFGminer
Can anyone help with using Minera with a Moonlander2 USB stick and a Pi 3b? I know how to get Minera on the Pi and access it via it's IP on my computer, but is it just plug and play or are there additional steps after that?
Do the SIlabs drivers need to be compiled and installed or can we skip that step and just pop in jstephanp's fork of bfgminer into the custom miners directory?
just make sure you rename it.
Gotcha. I wasn't having too much luck installing Minera over raspian. When I would launch the miner the log file would tell me that the directory the binary was in was just a directory. I'll give the premade image a shot.
Re: Official FutureBit Moonlander 2 Driver and Support Thread
Has anyone figured out a good way to single out a problematic miner in an array of miners? I rather not have to run them all individually to find the problem child.