Author

Topic: Official FutureBit Moonlander 2 Driver and Support Thread - page 102. (Read 71401 times)

legendary
Activity: 1736
Merit: 1006
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?

At the very least you would need to replace the bfgminer binaries it generates with my supplied RPi binaries (just copy over bfgminer executable).

After I get the next version out that fixes some bugs ill probably be able to merge it into main branch.

just copy the bfgminer to the minera custom folder.. it needs to be renamed to bfgminer-futurebit2
legendary
Activity: 2061
Merit: 1388
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?

At the very least you would need to replace the bfgminer binaries it generates with my supplied RPi binaries (just copy over bfgminer executable).

After I get the next version out that fixes some bugs ill probably be able to merge it into main branch.
newbie
Activity: 5
Merit: 0
Pre-ordered the Moonlander 2 a couple months ago and it arrived today. Thanks for this thread. Have it up and mining, all tuned in thanks to this!
jr. member
Activity: 70
Merit: 1
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?
jr. member
Activity: 70
Merit: 1
Hello,
 I will preface the following statement by saying that I am a 100% newbie to mining and know just about enough about computers to make myself dangerous, but also know that I'm a Hands On type learner and must dive in and try things.  So on to my question:

    I got my 4 Moonlander2s in the mail last week and hadn't had much of a chance to toy with them until today.   I followed the set up instructions, downloaded the drivers and other software and got them up and running in no time flat.  I ran them for about 15 mins and they were all hashing like crazy, it was then I realized that there was one very important step left out of the set up, at least for noobs like me;  Where and how does one edit the file to insert our own personal user name, password, and wallet address for the distribution of the his/her share of the block reward? 

Thanks in advance to anyone willing to point me in the right direction.

Steve

Check out Astrali's instructions on the first page, you want the part where you use nano.
legendary
Activity: 2061
Merit: 1388
These no longer will work on NH

| 19.48/19.40/ 8.94Mh/s | A:1 R:0+0(none)  0 days 00:08:16], one share 8 minutes lol

 [2017-12-02 19:16:59] Stratum from pool 2 detected new block
 [2017-12-02 19:17:05] Stratum from pool 2 detected new block
 [2017-12-02 19:17:32] Network difficulty changed to 984k ( 7.04Th)
 [2017-12-02 19:17:32] Stratum from pool 2 detected new block
 [2017-12-02 19:19:01] Stratum from pool 2 detected new block
 [2017-12-02 19:19:31] Network difficulty changed to 993k ( 7.11Th)
 [2017-12-02 19:19:31] Stratum from pool 2 detected new block
 [2017-12-02 19:19:44] Network difficulty changed to 1.19M ( 8.51Th)
 [2017-12-02 19:19:44] Stratum from pool 2 detected new block
 [2017-12-02 19:20:07] Network difficulty changed to 1.48M (10.62Th)
 [2017-12-02 19:20:07] Stratum from pool 2 detected new block
 [2017-12-02 19:20:57] Stratum from pool 2 detected new block
 [2017-12-02 19:21:52] Network difficulty changed to 1.62M (11.61Th)
 [2017-12-02 19:21:52] Stratum from pool 2 detected new block
 [2017-12-02 19:22:00] Network difficulty changed to 1.84M (13.19Th)
 [2017-12-02 19:22:00] Stratum from pool 2 detected new block
 [2017-12-02 19:22:13] Stratum from pool 2 detected new block
 [2017-12-02 19:23:37] Network difficulty changed to 2.01M (14.42Th)
 [2017-12-02 19:23:37] Stratum from pool 2 detected new block

i havent tested mine on nh, but they dont work on zpool or multipool.us :/

try putting #skipcbcheck on the url after the port number.


Yea that is a known issue having to use /#skipcbcheck using scrypt algo with bfgminer, that will not help with the difficulty, I even tried to set a minimum diff in the password field, did not help

They are running, just the pool diff is very high for these. Like I said most pools are not designed to run anything slower than 200-500 MH these days. Some pools have an option to set the diff in the password field (for example litecoinpool password "d=128" sets the diff to 128. 128 or 256 is a good value for these for shares every few seconds. Past that it will take minutes or longer for you to see a share. If pools don't have this, id contact them and ask for a "low diff port" (under 512) for USB miners.

Technically as long as the red LED is flashing constantly and hash rate displayed is good, it dosent matter that your submitted shares at a lower rate, just payout variance will be higher.
newbie
Activity: 1
Merit: 0
Hello,
 I will preface the following statement by saying that I am a 100% newbie to mining and know just about enough about computers to make myself dangerous, but also know that I'm a Hands On type learner and must dive in and try things.  So on to my question:

    I got my 4 Moonlander2s in the mail last week and hadn't had much of a chance to toy with them until today.   I followed the set up instructions, downloaded the drivers and other software and got them up and running in no time flat.  I ran them for about 15 mins and they were all hashing like crazy, it was then I realized that there was one very important step left out of the set up, at least for noobs like me;  Where and how does one edit the file to insert our own personal user name, password, and wallet address for the distribution of the his/her share of the block reward? 

Thanks in advance to anyone willing to point me in the right direction.

Steve
hero member
Activity: 630
Merit: 506
Need a list of scrypt pools these are not compatible with, you cannot mine on pro hashing either
hero member
Activity: 630
Merit: 506
These no longer will work on NH

| 19.48/19.40/ 8.94Mh/s | A:1 R:0+0(none)  0 days 00:08:16], one share 8 minutes lol

 [2017-12-02 19:16:59] Stratum from pool 2 detected new block
 [2017-12-02 19:17:05] Stratum from pool 2 detected new block
 [2017-12-02 19:17:32] Network difficulty changed to 984k ( 7.04Th)
 [2017-12-02 19:17:32] Stratum from pool 2 detected new block
 [2017-12-02 19:19:01] Stratum from pool 2 detected new block
 [2017-12-02 19:19:31] Network difficulty changed to 993k ( 7.11Th)
 [2017-12-02 19:19:31] Stratum from pool 2 detected new block
 [2017-12-02 19:19:44] Network difficulty changed to 1.19M ( 8.51Th)
 [2017-12-02 19:19:44] Stratum from pool 2 detected new block
 [2017-12-02 19:20:07] Network difficulty changed to 1.48M (10.62Th)
 [2017-12-02 19:20:07] Stratum from pool 2 detected new block
 [2017-12-02 19:20:57] Stratum from pool 2 detected new block
 [2017-12-02 19:21:52] Network difficulty changed to 1.62M (11.61Th)
 [2017-12-02 19:21:52] Stratum from pool 2 detected new block
 [2017-12-02 19:22:00] Network difficulty changed to 1.84M (13.19Th)
 [2017-12-02 19:22:00] Stratum from pool 2 detected new block
 [2017-12-02 19:22:13] Stratum from pool 2 detected new block
 [2017-12-02 19:23:37] Network difficulty changed to 2.01M (14.42Th)
 [2017-12-02 19:23:37] Stratum from pool 2 detected new block

i havent tested mine on nh, but they dont work on zpool or multipool.us :/

try putting #skipcbcheck on the url after the port number.


Yea that is a known issue having to use /#skipcbcheck using scrypt algo with bfgminer, that will not help with the difficulty, I even tried to set a minimum diff in the password field, did not help
legendary
Activity: 1736
Merit: 1006
These no longer will work on NH

| 19.48/19.40/ 8.94Mh/s | A:1 R:0+0(none)  0 days 00:08:16], one share 8 minutes lol

 [2017-12-02 19:16:59] Stratum from pool 2 detected new block
 [2017-12-02 19:17:05] Stratum from pool 2 detected new block
 [2017-12-02 19:17:32] Network difficulty changed to 984k ( 7.04Th)
 [2017-12-02 19:17:32] Stratum from pool 2 detected new block
 [2017-12-02 19:19:01] Stratum from pool 2 detected new block
 [2017-12-02 19:19:31] Network difficulty changed to 993k ( 7.11Th)
 [2017-12-02 19:19:31] Stratum from pool 2 detected new block
 [2017-12-02 19:19:44] Network difficulty changed to 1.19M ( 8.51Th)
 [2017-12-02 19:19:44] Stratum from pool 2 detected new block
 [2017-12-02 19:20:07] Network difficulty changed to 1.48M (10.62Th)
 [2017-12-02 19:20:07] Stratum from pool 2 detected new block
 [2017-12-02 19:20:57] Stratum from pool 2 detected new block
 [2017-12-02 19:21:52] Network difficulty changed to 1.62M (11.61Th)
 [2017-12-02 19:21:52] Stratum from pool 2 detected new block
 [2017-12-02 19:22:00] Network difficulty changed to 1.84M (13.19Th)
 [2017-12-02 19:22:00] Stratum from pool 2 detected new block
 [2017-12-02 19:22:13] Stratum from pool 2 detected new block
 [2017-12-02 19:23:37] Network difficulty changed to 2.01M (14.42Th)
 [2017-12-02 19:23:37] Stratum from pool 2 detected new block

i havent tested mine on nh, but they dont work on zpool or multipool.us sorry i meant prohashing :/

try putting #skipcbcheck on the url after the port number.
hero member
Activity: 630
Merit: 506
These no longer will work on NH

| 19.48/19.40/ 8.94Mh/s | A:1 R:0+0(none)  0 days 00:08:16], one share 8 minutes lol

 [2017-12-02 19:16:59] Stratum from pool 2 detected new block
 [2017-12-02 19:17:05] Stratum from pool 2 detected new block
 [2017-12-02 19:17:32] Network difficulty changed to 984k ( 7.04Th)
 [2017-12-02 19:17:32] Stratum from pool 2 detected new block
 [2017-12-02 19:19:01] Stratum from pool 2 detected new block
 [2017-12-02 19:19:31] Network difficulty changed to 993k ( 7.11Th)
 [2017-12-02 19:19:31] Stratum from pool 2 detected new block
 [2017-12-02 19:19:44] Network difficulty changed to 1.19M ( 8.51Th)
 [2017-12-02 19:19:44] Stratum from pool 2 detected new block
 [2017-12-02 19:20:07] Network difficulty changed to 1.48M (10.62Th)
 [2017-12-02 19:20:07] Stratum from pool 2 detected new block
 [2017-12-02 19:20:57] Stratum from pool 2 detected new block
 [2017-12-02 19:21:52] Network difficulty changed to 1.62M (11.61Th)
 [2017-12-02 19:21:52] Stratum from pool 2 detected new block
 [2017-12-02 19:22:00] Network difficulty changed to 1.84M (13.19Th)
 [2017-12-02 19:22:00] Stratum from pool 2 detected new block
 [2017-12-02 19:22:13] Stratum from pool 2 detected new block
 [2017-12-02 19:23:37] Network difficulty changed to 2.01M (14.42Th)
 [2017-12-02 19:23:37] Stratum from pool 2 detected new block
jr. member
Activity: 70
Merit: 1

[/quote]

your problem is usb speed.. try upping the worker difficulty.. i found if you have it too low, say 64 or 128 and multiple sticks... they get jammed up after awhile.
also minera has a restart option. it works great.


[/quote]

How do you get them to run on Minera? I know how to get Minera on a Pi, but is it just plug and play from there?
newbie
Activity: 2
Merit: 0
Hey there jstefanop, just received my order a couple of days ago, and it seems like one of my miners has an issue where it runs normally for a brief period of time (avg 2-min hashrate of ~4.1 running at 756), and after a few minutes, it ramps down to ~2.7 or so, and that's where it stays. I have two other units that work fine, and do not exhibit this behavior. I've tried adjusting the core voltage a bit (swept the from 0.7 - 0.825), but nothing seemed to have an effect. Didn't alter mem voltage. Another note is that I don't notice this drop when I run at lower frequencies; at 684 for example, all three sticks seems to have a avg 2-min hashrate of 1.75.

Not sure if it helps, but its unit #2815. Any thoughts or suggestions? Got a multimeter in case that's useful. Thanks in advance!

I wouldnt be worried unless your average hashrate, and pool hashrate (the last two numbers) show lower than expected hash. Also try isolating that miner to see if its a hub/power issue.

Thanks for the reply. Definitely have excluded the USB ports: my two other miners seem to operate fine on the same port(s); both are very stable for long runs, one at 832mhz and the other at 796mhz. And sorry I didn't mention it originally, but yes: the average hashrate and the pool hashrate both trend downwards, once this "throttling" kicks in. Currently I'm running it at 700mhz / .75v core / 0.9v mem; for the first ten minutes, it hashed at about 3.8Mh/s, but then it throttled around that time, and the values have now settled at 2.63 / 2.68 / 2.76Mh/s after running for about 25 minutes total. That's what happens pretty much every time I run them: two run great, but this one throttles down to 2.7Mh/s, and I can't seem to get it to hash above that rate unless I restart BFGMiner.

On a side note, it sounds very similar to what soifigured described in this post:

Got some assembled and up and running.  I'm noticing some are slowing down to about 2MH after running for an hour or so.  Is this a self preservation feature?  Are they running too hot?  I hit all the small heatsinks with my pyrometer and temps are all about 60C.

Thanks again for all the help, appreciate you taking the time to help us out.

*Edit: I might have found a sweet spot for the voltages on this miner, I dropped the memory down quite a bit and currently I'm having a nice run with it at 756mhz, using core voltage of 0.73v and memory voltage of 0.79v. The values currently being reported by bfgminer are 4.25 / 4.22 / 4.29Mh/s, and it's been running for ~15 mins or so. I kept mulling over the fact that the miner was just being throttled, but still was basically healthy, for all intents and purposes. So I decided to try reducing the stock voltages a bit and see how things go. Will let you guys know if this works out for me, gonna give let it run overnight.

** Final edit: results of the overnight run are good. All three miners are working great now.
legendary
Activity: 1736
Merit: 1006
legendary
Activity: 1736
Merit: 1006
I will ask here also.

Why are these needing to be built by HolyScott before shipping?

HolyScott-

I was not expecting labor to have to build and put them all together

he is putting them together so he can test them first.. i asked.

i guess he didnt feel comfortable just sending them out untested.
newbie
Activity: 9
Merit: 0
similar to yellowshark,

my landers are ...

Code:
 MLD 0:       |   0.0/  0.0/  0.0 h/s | A:   0 R:0+0(none) HW: 0/none
 MLD 1:       |  3.94/ 3.59/ 3.74Mh/s | A:  53 R:0+0(none) HW: 0/none
 MLD 2:       |   0.0/  0.0/  0.0 h/s | A:   0 R:0+0(none) HW: 0/none
 MLD 3:       |  3.88/ 3.85/ 3.97Mh/s | A:  59 R:0+0(none) HW: 1/.21%
 MLD 4:       |   0.0/  0.0/  0.0 h/s | A:   0 R:0+0(none) HW: 0/none
 MLD 5:       |  3.88/ 3.85/ 3.98Mh/s | A:  66 R:0+0(none) HW: 0/none
 MLD 6:       |  3.87/ 4.00/ 3.92Mh/s | A:  66 R:0+0(none) HW: 1/.21%
 MLD 7:       |   0.0/  0.0/  0.0 h/s | A:   0 R:0+0(none) HW: 0/none
 MLD 8:       |  3.84/ 3.82/ 4.08Mh/s | A:  60 R:0+0(none) HW: 0/none
 MLD 9:       |  3.80/ 3.84/ 3.86Mh/s | A:  64 R:0+0(none) HW: 5/1.1%
 MLD10:       |  3.81/ 3.85/ 4.29Mh/s | A:  78 R:0+0(none) HW: 0/none
 MLD11:       |  3.90/ 3.81/ 3.89Mh/s | A:  73 R:0+0(none) HW: 1/.21%
 MLD12:       |  3.81/ 3.80/ 4.10Mh/s | A:  60 R:0+0(none) HW: 0/none
 MLD13:       |  3.88/ 3.85/ 3.95Mh/s | A:  74 R:0+0(none) HW: 0/none
 MLD14:       |   0.0/  0.0/  0.0 h/s | A:   0 R:0+0(none) HW: 0/none
 MLD15:       |   0.0/  0.0/  0.0 h/s | A:   0 R:0+0(none) HW: 0/none
 MLD16:       | 565.5/544.4/564.6kh/s | A:   9 R:0+0(none) HW: 0/none
 MLD17:       |  58.0/ 45.7/ 33.2kh/s | A:   0 R:0+0(none) HW: 0/none
 MLD18:       |  3.86/ 3.85/ 4.11Mh/s | A:  67 R:0+0(none) HW: 0/none
 MLD19:       |  60.3/ 51.1/ 74.7kh/s | A:   5 R:0+0(none) HW: 0/none
 MLD20:       |  2.52/ 2.87/ 3.02Mh/s | A:  44 R:0+0(none) HW: 1/.27%
 MLD21:       |  3.90/ 3.93/ 4.24Mh/s | A:  74 R:0+0(none) HW: 1/.20%
 MLD22:       |  3.89/ 3.82/ 4.07Mh/s | A:  72 R:0+0(none) HW: 0/none
 MLD23:       |  2.57/ 2.93/ 3.26Mh/s | A:  44 R:0+0(none) HW: 0/none
 MLD24:       |   0.0/  0.0/  0.0 h/s | A:   0 R:0+0(none) HW: 0/none
 MLD25:       |  2.38/ 2.75/ 2.89Mh/s | A:  50 R:0+0(none) HW: 0/none
 MLD26:       |   0.0/  0.0/  0.0 h/s | A:   0 R:0+0(none) HW: 0/none
 MLD27:       |  2.43/ 3.00/ 3.16Mh/s | A:  47 R:0+0(none) HW: 0/none
 MLD28:       |  3.89/ 3.84/ 3.90Mh/s | A:  54 R:0+0(none) HW: 1/.21%
 MLD29:       |  2.56/ 2.93/ 2.87Mh/s | A:  42 R:0+0(none) HW: 0/none
 MLD30:       | 330.2/315.8/240.8kh/s | A:   7 R:0+0(none) HW: 0/none
 MLD31:       |   0.0/  0.0/  0.0 h/s | A:   0 R:0+0(none) HW: 0/none
 MLD32:       |  3.90/ 3.85/ 3.84Mh/s | A:  60 R:0+0(none) HW: 0/none
 MLD33:       |  3.92/ 4.01/ 4.18Mh/s | A:  55 R:0+0(none) HW: 1/.20%
 MLD34:       |  3.87/ 3.84/ 3.85Mh/s | A:  53 R:0+0(none) HW: 0/none
 MLD35:       |   0.0/  0.0/  0.0 h/s | A:   0 R:0+0(none) HW: 0/none
 MLD36:       |  3.85/ 3.84/ 3.89Mh/s | A:  74 R:0+0(none) HW: 0/none
 MLD37:       |  3.83/ 3.86/ 4.12Mh/s | A:  71 R:0+0(none) HW: 0/none
 MLD38:       |  3.90/ 3.85/ 4.40Mh/s | A:  59 R:0+0(none) HW: 4/.75%
 MLD39:       |  3.93/ 3.86/ 4.43Mh/s | A:  68 R:0+0(none) HW: 0/none
 MLD40:       |  3.84/ 3.79/ 3.69Mh/s | A:  59 R:0+0(none) HW: 2/.45%
 MLD41:       |  3.02/ 3.59/ 4.00Mh/s | A:  47 R:0+0(none) HW: 0/none
 MLD42:       |  1.92/ 1.31/ 1.16Mh/s | A:  24 R:0+0(none) HW: 0/none
 MLD43:       |  3.90/ 3.81/ 4.03Mh/s | A:  75 R:0+0(none) HW: 1/.21%
 MLD44:       |   0.0/  0.0/  0.0 h/s | A:   0 R:0+0(none) HW: 0/none
 MLD45:       |   0.0/  0.0/  0.0 h/s | A:   0 R:0+0(none) HW: 0/none
 MLD46:       |  3.86/ 3.80/ 3.74Mh/s | A:  59 R:0+0(none) HW: 0/none
 MLD47:       | 521.5/380.5/307.2kh/s | A:   6 R:0+0(none) HW: 0/none
 MLD48:       |  3.93/ 3.87/ 4.03Mh/s | A:  63 R:0+0(none) HW: 1/.21%
 MLD49:       |  3.84/ 3.79/ 4.12Mh/s | A:  64 R:0+0(none) HW: 4/.80%
 MLD50:       |   0.0/  0.0/  0.0 h/s | A:   0 R:0+0(none) HW: 0/none
 MLD51:       |  1.41/ 1.24/ 1.20Mh/s | A:  15 R:0+0(none) HW: 0/none
 MLD52:       |  2.61/ 2.75/ 2.87Mh/s | A:  46 R:0+0(none) HW: 0/none
 MLD53:       |   0.0/  0.0/  0.0 h/s | A:   0 R:0+0(none) HW: 0/none
 MLD54:       |   0.0/  0.0/  0.0 h/s | A:   0 R:0+0(none) HW: 0/none
 MLD55:       |  3.92/ 3.88/ 4.13Mh/s | A:  81 R:0+0(none) HW: 1/.20%
 MLD56:       |   0.0/  0.0/  0.0 h/s | A:   0 R:0+0(none) HW: 0/none
 MLD57:       |  2.97/ 3.57/ 3.75Mh/s | A:  51 R:0+0(none) HW: 0/none
 MLD58:       | 279.0/253.1/274.0kh/s | A:   8 R:0+0(none) HW: 0/none
 MLD59:       |  3.88/ 3.83/ 3.84Mh/s | A:  57 R:0+0(none) HW: 0/none
 MLD60:       |   0.0/  0.0/  0.0 h/s | A:   0 R:0+0(none) HW: 0/none
 MLD61:       |   0.0/  0.0/  0.0 h/s | A:   0 R:0+0(none) HW: 0/none
 MLD62:       |  2.54/ 2.39/ 2.51Mh/s | A:  39 R:0+0(none) HW: 0/none
 MLD63:       |  3.90/ 3.85/ 4.09Mh/s | A:  56 R:0+0(none) HW: 0/none
 MLD64:       |   0.0/  0.0/  0.0 h/s | A:   0 R:0+0(none) HW: 0/none
 MLD65:       |  3.84/ 3.80/ 4.29Mh/s | A:  62 R:0+0(none) HW: 2/.39%
 MLD66:       |   0.0/  0.0/  0.0 h/s | A:   0 R:0+0(none) HW: 0/none
 MLD67:       |  3.87/ 4.01/ 3.99Mh/s | A:  40 R:0+0(none) HW: 1/.21%
 MLD68:       | 180.0/148.8/149.5kh/s | A:   8 R:0+0(none) HW: 0/none
 MLD69:       | 739.5/656.6/722.3kh/s | A:  16 R:0+0(none) HW: 2/2.2%
 MLD70:       |   0.0/  0.0/  0.0 h/s | A:   0 R:0+0(none) HW: 0/none
 MLD71:       |  3.89/ 3.85/ 3.68Mh/s | A:  57 R:0+0(none) HW: 0/none
 MLD72:       |  3.87/ 3.82/ 3.92Mh/s | A:  66 R:0+0(none) HW: 0/none
 MLD73:       |  3.90/ 3.85/ 3.84Mh/s | A:  56 R:0+0(none) HW: 2/.43%
 MLD74:       |  1.26/ 0.98/ 0.99Mh/s | A:  12 R:0+0(none) HW: 0/none

there are 2 types of problem.

1) not working at all (it may be USB trouble but my power supply is very strong)
2) dropping down to kH/s

idk why... I really want auto restart function.
So I'm running 75 landers now, it outputs only 160MH/s... I'm sad...
hero member
Activity: 630
Merit: 506
I will ask here also.

Why are these needing to be built by HolyScott before shipping?

HolyScott-

I was not expecting labor to have to build and put them all together
legendary
Activity: 2061
Merit: 1388
Hey there jstefanop, just received my order a couple of days ago, and it seems like one of my miners has an issue where it runs normally for a brief period of time (avg 2-min hashrate of ~4.1 running at 756), and after a few minutes, it ramps down to ~2.7 or so, and that's where it stays. I have two other units that work fine, and do not exhibit this behavior. I've tried adjusting the core voltage a bit (swept the from 0.7 - 0.825), but nothing seemed to have an effect. Didn't alter mem voltage. Another note is that I don't notice this drop when I run at lower frequencies; at 684 for example, all three sticks seems to have a avg 2-min hashrate of 1.75.

Not sure if it helps, but its unit #2815. Any thoughts or suggestions? Got a multimeter in case that's useful. Thanks in advance!

I wouldnt be worried unless your average hashrate, and pool hashrate (the last two numbers) show lower than expected hash. Also try isolating that miner to see if its a hub/power issue.
legendary
Activity: 2061
Merit: 1388
I received my Moonlander 2 today and I can not get to work on either of my two linux boxes.  I am running Ubuntu 16.04 on both machines.  When I run lsusb:
Code:
Bus 006 Device 002: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light

when I run dmesg:
Code:
[1746203.975666] usb 6-1: new full-speed USB device number 2 using xhci_hcd
[1746204.162324] usb 6-1: New USB device found, idVendor=10c4, idProduct=ea60
[1746204.162329] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[1746204.162331] usb 6-1: Product: FutureBit Moonlander 2
[1746204.162333] usb 6-1: Manufacturer: FutureBit
[1746204.162335] usb 6-1: SerialNumber: 2ca47d36230be71194d9f95433cb487a
[1746205.198180] usbcore: registered new interface driver usbserial
[1746205.198194] usbcore: registered new interface driver usbserial_generic
[1746205.198205] usbserial: USB Serial support registered for generic
[1746205.201203] usbcore: registered new interface driver cp210x
[1746205.201216] usbserial: USB Serial support registered for cp210x
[1746205.201246] cp210x 6-1:1.0: cp210x converter detected
[1746205.219355] usb 6-1: cp210x converter now attached to ttyUSB0

But when I run ./start_moonlander2.sh
Code:
 bfgminer version 5.4.2-34-gea3ba70 - Started: [2017-12-01 16:30:43] - [  0 days 00:01:10]
 [M]anage devices [P]ool management [S]ettings [D]isplay options             [H]elp [Q]uit
 Pool 0: us.litecoinpool.or  Diff:1m  +Strtm  LU:[16:31:50]  User:jstefanop.1
 Block: ...2abc04de8b3ac40b  Diff:1.5M (10.76T)  Started: [16:30:42]  I: 0.00 BTC/hr
 ST:2  F:0  NB:1  AS:0  BW:[105/  9 B/s]  E:0.00  BS:0
 0            |   0.0/  0.0/  0.0 h/s | A:0 R:0+0(none) HW:0/none
-------------------------------------------------------------------------------------------
NO DEVICES FOUND: Press 'M' and '+' to add
-------------------------------------------------------------------------------------------
 [2017-12-01 16:30:37] Waiting for devices; press 'M+' to add, or 'Q' to quit
 [2017-12-01 16:30:37] Probing for an alive pool
 [2017-12-01 16:30:42] Pool 0 stratum+tcp://us.litecoinpool.org:3333 alive
 [2017-12-01 16:30:42] Pool 0 is hiding block contents from us
 [2017-12-01 16:30:42] Network difficulty changed to 1.5M (10.76T)
 [2017-12-01 16:30:42] Stratum from pool 0 detected new block

I tried to manually enter with "mld:/dev/ttyUSB0", but I get "No new devices found".

I thought to try to build it myself, but there is no "build.sh" or "configure.sh" in the source code.  And I could not get "git clone" to work.

Any ideas what to try next?



Looks like its loading a different UART driver. Is this a fresh ubuntu install?  Do you see a yellow led flash on board when your start it up?
newbie
Activity: 42
Merit: 0
pop the USB HUBs question over on the hub thread and i'll reply (i am looking to do similar):

https://bitcointalksearch.org/topic/futurebit-moonlander-2-usb-hubs-thread-2455609

Jump to: