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

Hi.  Can anyone help. 

On my Mac with 10.13.06 I'm trying to edit the start-moonlander-2 file in order to insert my own info but the bfgminer-5.4.2-FutureBit2-mac64 folder that I have downloaded has 'read only' permissions even though the 'file info' states that there is a read and write privilege for myself.

Amy ideas.  Unlocking the folder does nothing and it is not possible to change any of the permissions locked or unlocked.

Thanks in advance.

I had issues when I ran these on usb3 ports.   Run's smoothly for me however on usb2.0 and clocked at 720Mhz.  I have two of them on a gekkoscience USB powered hub.  I wouldn't suggest running these directly from a PC usb port as they will not get the proper power that's needed.

Hello,

Ive noticed that over time (after a few hours) my hash rate drops down to about 2.5 MH/s., Anybody else having this issue? Ive tried different clock speeds thinking it might be overheating, but it even does it at 600 MHz.

My settings:

Clock Speed: 796
Vcore: 0.740
VMem: 0.848

Its running on my PCs USB3 port if that matters.,

how bad is it to run one of these without the fan? it seems the fan on mine has fallen off :/ how it happened im not to sure of

This is covered extensively in this thread...and its one of the FAQ questions covered on the first page of this thread.

https://bitcointalksearch.org/topic/m.24766878

hi, I ve got 3pcs moonlanders and one PC. Is it possible configure that first mld will be working for first pool, second mld for second pool and third for any other pool.
I was thinking that this MLD:ALL and change on MLD:1 or 2 or 3 ll be the key but it didn t work
Someone know how to do this??

Sorry! Your are right, I was using this config to mine at ltc.tbdice.org (solo), I got confused.

bfgminer is not setup to mine solo directly to wallet. This won't work.

Your must add your wallet address.
In ccminer you have --coinbase-addr=JogdpsHjmxfpoTWtNY7VdPvPgGiKktr

For bfgminer:
--generate-to JogdpsHjmxfpoTWtNY7VdPvPgGiKktr

hi, I need Your help.
I m trying to mining one coin, it is solo mining.
When I m using scrypt via GPU ccminer everything is working, (but gpu have only 0,5Mh) so I bought this usb miner. But it don t want mining, message is: "Started bfgminer 5.4.2-38-g106390a99
[2019-04-27 20:13:18] Probing for an alive pool
[2019-04-27 20:13:18] blktmpl error: Unrecognized block version, and not allowed to reduce or force it
[2019-04-27 20:13:18] Pool 0 slow/down or URL or credentials invalid
[2019-04-27 20:13:19] No servers were found that could be used to get work from.
[2019-04-27 20:13:19] Please check the details from the list below of the servers you have input
[2019-04-27 20:13:19] Most likely you have input the wrong URL, forgotten to add a port, or have not set up workers
[2019-04-27 20:13:19] Pool: 0 URL: http://127.0.0.1:2255 User: u1 Password: p1
[2019-04-27 20:13:19] Press any key to exit, or BFGMiner will try again in 15s.
[2019-04-27 20:13:36] No servers were found that could be used to get work from.
[2019-04-27 20:13:36] Please check the details from the list below of the servers you have input
[2019-04-27 20:13:36] Most likely you have input the wrong URL, forgotten to add a port, or have not set up workers
[2019-04-27 20:13:36] Pool: 0 URL: http://127.0.0.1:2255 User: u1 Password: p1
[2019-04-27 20:13:36] Press any key to exit, or BFGMiner will try again in 15s."

My ccminer good and working config is": :mine
ccminer.exe -a scrypt -o http://127.0.0.1:2255 -u u1 -p p1 -i 25 --no-longpoll --no-getwork --no-stratum --coinbase-addr=JogdpsHjmxfpoTWtNY7VdPvPgGiKktr
ping -n 30 127.0.0.1
goto :mine

My bfg not working config is: bfgminer.exe --scrypt -o 127.0.0.1:2255 -u u1 -p p1 -S MLD:all --set MLD:clock=600
pause

Maybe You ll be know What is wrong with this bfg bat??

thank you all so much for the help you tried to give me but as i had expected it was my windows based pc that was giving me the issues after getting a powered usb hub and setting the moonlander up on my Raspbery Pi 3B+ its been running stable for almost a full 24 hours now with out any random forced stop like my other pc. looks like ill be running this from my pi from now on. thanks again.

Hello i was wondering what chip does the futurebit moonlander uses? I never saw that before?

Hi guys, cheers for all the info in these pages... I've got my moonlander running fantastic on litecoinpool.org  at about 5 mh's at 744 clock from my PC's standard USB (no powered hub) with in a minute I get accepted shares one after the other... no problems at all.

but when I try to mine a alt coin on other pools like Zergpool I get a sh!t ton of errors such as mismatched info, stratum interruptions ect ect and a ton of HW errors.

I''m playing around with d= and scan-time, But not seeming to help much. any Pro tips for me ?? best I've had is 7 accepted to 110 HW in 15 minutes or so

Ok steps I had to make, and again, many thanks for helping me get this straightened out.   I'm posting up the below in case it helps any of the others using both Gekko Newpac's and Moonlanders on the same ubuntu  system.

First run the following command:  dmesg | grep ttyUSB

I have currently only 1 gekkoscience newpac and 1 moonlander on this system tinkering with.  They are on the same USB hub (a 10 port powered hub) and are shown attached to the following USB ports:

dmesg | grep ttyUSB
[   18.635808] usb 1-5.5: FTDI USB Serial Device converter now attached to ttyUSB0
[   19.749267] usb 1-5.7.4: cp210x converter now attached to ttyUSB1


So based on above, the cp210x (moonlander using) is on USB1.  The Newpac is on USB0.

Now, inside the folder where I installed the moonlander mining software I created a miner_verge.sh file to run the following command:


./bfgminer --scrypt -o stratum+tcp://xvg.mastermining.net:3181#skipcbcheck -u username.workername -p x -S /dev/ttyUSB1 --set MLD:clock=700

Listed above I have bfgminer pointed to pool mastermining mining Verge coin.   You would insert your username.worker to whatever pool you are connected to  add -S /dev/ttyUSB1 in this example as the Moonlander Miner is on USB1.   After saved and made the .sh executable just type sudo ./miner.verge.sh and now it is mining.


Next is to configure the gekko newpac miner.  Right now I have a script in it's directory called miner_prohashing.sh that I was using as a testing pool.  Below is the code in the script:

./cgminer -o stratum+tcp://prohashing.com:3335 -u username -p x --usb 1:3 --gekko-newpac-freq 200 --gekko-newpac-boost


For the gekko miners, you will need to add   --usb  bus address : device address.    So to get this information I run lsusb:


lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 003: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 001 Device 002: ID 1a40:0201 Terminus Technology Inc. FE 2.1 7-port Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 011 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 010 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 010 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Here I am looking for the ltd bridge(I2C/SPI/UART/FIFO) as this one is the Gekko Miner.  It is on Bus 001 and Device 003.  So in my miner statement above, I keyed --usb 1:3 so that it will know which of the usb sticks to use for cgminer.



If you are running multiple sticks say 4 moonlanders and 4 gekko's you may have to tweak a little more with this.  I believe with the Gekko's you would extend the --usb command so if I had 2 more in usb 4 and 5 and they were all on Bus 1 then I would have --usb 1:3,1:4,1:5 if I am understanding the readme file correctly.

 jstefanop  you are awesome!!   I now have both the gekko newpac and the moonlander 2 mining, on the same hub together without conflicts.   I have a few tweaks I need to make and then I'll post up the changes I had to make so that it'll help anyone else running into the same issue that I did on Ubuntu.

You need to figure out which tty each is attached too, and make sure you specify in bfgminer/cgminer to not auto-scan (ie use the -S /dev/ttyUSB0) flag.

My driver is pretty good at filtering out the right ASIC before injecting commands to the chip, but im pretty sure gekkosciences driver starts sending commands as soon as it finds a UART chip, which is why it screws up the moonlanders. Make sure auto-scan is not enabled will keep each driver from trying to send commands to the wrong usb miner.

Thanks.  I may have to do as you said and break them down on two different systems.   I recently picked up a Raspberry Pi 3 b+ and may put one of these hubs on it if it'll work.



*edit* and you are right on windows.  I must not have been paying attention as it appeared to have been running.  The Moonlander was however the Gekko Newpac wasn't.  Eventhough it was still showing hashing power and Mhz, I didn't see before the errors showing at the bottom about missing driver.   When I reboot, and run only the gekko newpac the driver is then picked up and attached to the newpac.

Bummer.     Thanks again for the help.

If you were able to get a 2Pac and Moonlander2 (ML2) to work on the same computer, you've gotten a lot further than most of us. You should write a blog post about it. I could never get the drivers to work together in Windows 10. Linux I always run one or other, but not both.

Ok new issue.   But this seems to be related to the cp210x.  In ubuntu 18.04 LTS linux distro, I have successfully got the moonlander mining Verge coin.  The problem I am having is when I connect a Gekkoscience newpac miner to the system.  I am not Linux tech savy enough to correct the issue.   What happens is that when moonlander is running it'll start erroring out with input/output errors.  I can't have both of them running at the same time.  Even with Moonlander connected to a USB2.0 port and running the newpac on a USB 3.0 port.

When I run the following command: dmesg | grep ttyUSB it appears the cp210x will disconnect from ttyusb0 (moonlander is on) and connect to ttyusb1 (gekko newpac is on) and alternate between the two causing bfgminer to fail on the moonlander.

Any ideas on how to keep it from alternating like this and have both running together?  I tested on my windows machine and both are able to work together without issue.  Ubuntu on the other hand no so.  When I ran the below command 'before' launching the mining software, it showed correctly moonlander device on usb0 and the gekko on usb1.  'After' running the miner, the below is what happens and I believe is the reason for the issue.  Soon I will be attaching an Arduino Uno for some electronic projects I am working on and believe this will possibly create issues with it as well.  Help is appreciated.  Just don't know how to correct.   Thanks

dmesg | grep ttyUSB
[ 3555.477422] usb 1-5.7.4: cp210x converter now attached to ttyUSB0
[51108.420407] usb 10-1.1: FTDI USB Serial Device converter now attached to ttyUSB1
[51298.159975] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[51298.170611] usb 1-5.7.4: cp210x converter now attached to ttyUSB2
[51298.170999] cp210x ttyUSB2: cp210x converter now disconnected from ttyUSB2
[51298.180661] usb 1-5.7.4: cp210x converter now attached to ttyUSB2
[51298.180938] cp210x ttyUSB2: cp210x converter now disconnected from ttyUSB2
[51298.191097] usb 1-5.7.4: cp210x converter now attached to ttyUSB2
[51298.191410] cp210x ttyUSB2: cp210x converter now disconnected from ttyUSB2
[51298.201626] usb 1-5.7.4: cp210x converter now attached to ttyUSB2
[51298.201953] cp210x ttyUSB2: cp210x converter now disconnected from ttyUSB2
[51298.213337] usb 1-5.7.4: cp210x converter now attached to ttyUSB2
[51298.213502] cp210x ttyUSB2: cp210x converter now disconnected from ttyUSB2
[51298.222722] usb 1-5.7.4: cp210x converter now attached to ttyUSB2
[51298.274997] ftdi_sio ttyUSB1: FTDI USB Serial Device converter now disconnected from ttyUSB1
[51303.705760] cp210x ttyUSB2: cp210x converter now disconnected from ttyUSB2
[51303.715506] usb 1-5.7.4: cp210x converter now attached to ttyUSB1
[51303.715684] cp210x ttyUSB1: cp210x converter now disconnected from ttyUSB1
[51303.724919] usb 1-5.7.4: cp210x converter now attached to ttyUSB1
[51303.725115] cp210x ttyUSB1: cp210x converter now disconnected from ttyUSB1
[51303.735049] usb 1-5.7.4: cp210x converter now attached to ttyUSB1
[51303.735440] cp210x ttyUSB1: cp210x converter now disconnected from ttyUSB1
[51303.745002] usb 1-5.7.4: cp210x converter now attached to ttyUSB1
[51303.745194] cp210x ttyUSB1: cp210x converter now disconnected from ttyUSB1
[51303.757735] usb 1-5.7.4: cp210x converter now attached to ttyUSB1
[51303.758826] cp210x ttyUSB1: cp210x converter now disconnected from ttyUSB1
[51303.768730] usb 1-5.7.4: cp210x converter now attached to ttyUSB1
[51308.993333] cp210x ttyUSB1: cp210x converter now disconnected from ttyUSB1
[51309.003325] usb 1-5.7.4: cp210x converter now attached to ttyUSB0
[51309.003669] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[51309.014305] usb 1-5.7.4: cp210x converter now attached to ttyUSB0
[51309.014731] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[51309.025782] usb 1-5.7.4: cp210x converter now attached to ttyUSB0
[51309.026985] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[51309.037099] usb 1-5.7.4: cp210x converter now attached to ttyUSB0
[51309.037310] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[51309.049339] usb 1-5.7.4: cp210x converter now attached to ttyUSB0
[51309.049577] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[51309.060475] usb 1-5.7.4: cp210x converter now attached to ttyUSB0

Disregard messages.  Figured it out.  Like I said....error between keyboard and chair .   I forgot when I was logged in setting this up I was on as root.  Then when trying to run this today I'm using my normal account, even though it has root/admin access it just isn't it.   I reinstalled into a different folder.  ran the command (had to use Sudo due to locked devices) and it is now working.   All is well.   Thanks