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

>> Can you mine using bfgminer with the Moonlander2 (ML2) plugged directly into your computer's USB?
Yes, that works fine (at reduced clockfrquency, obviously). So the usb to uart driver is working fine.

>> Do you have a Windows 7 or Windows 10 workstation you can try to mine with?
Ok, it is the hub-driver that seems the problem, not the mining. I connected the hub to a win 7 machine, and then the ML2 is recognised properly (after installing the usb to uart drivers first, of course). I can't use that machine for mining though as it is my job machine.

I looked under device manager on my win7 machine what usb driver it installed and it appears the (VIA?) USB MTT driver. Going to VIAs webpages I get the impression these exist for win7 and up only?? Suck!!! So I am sort of convinced now that it has to do with the default driver my vista machine installs for the hub which is not good enough. If anyone has any suggestion on alternative drivers that may make this thing work under vista, it will be hugely appreciated!!

I see people running these sticks with Rpi s with powered hubs so I wonder... Is this software going to run on armv7 device running kernel 2.6.x. Any maemo freaks here...? That woud be fun...

Can you mine using bfgminer with the Moonlander2 (ML2) plugged directly into your computer's USB? You may need to turn down the MHZ from 600 to 300 (in the Start_Moonlander2.bat file) just to underpower it and see if you can hash with it.


Yes, very frustrating. Do you have a Windows 7 or Windows 10 workstation you can try to mine with? Try ML2 directly and with Eyeboot in between.

You might try contacting Eyeboot for advice. I suggest asking who the chipset manufacturer for Eyeboot USB HUB is and whether there are newer drivers available. For example, the chipset manufacturer could be VIA and you could possibly upgrade the driver for the USB controller.

i'll try the dist upgrade as well
maybe this can fix it.

Thanks!

Happy my instructions that i blindly wrote helped

Warm greetings - Astrali

It was in fact the USB 3.0 hub.  I replaced with a Plugable USB 2.0 powered 60w hub and it works great.  Thanks for the help figuring that out, Philip and Mark.

Happy mining to all!

-Jim

If it helps troubleshoot, I used your instructions on my Pi 3 and my two sticks are hashing perfectly. The only changes I made were to start with:

sudo apt-get update
sudo apt-get dist-upgrade

before I cut and pasted your instructions and to change:

./start_moonlander.sh
to
./start_moonlander2.sh

in the last step.

Good luck, and thanks again for all the help!

my "special" hub can handle 2 (with 3A) on windows and works fine. problem seems to be my raspberry

>> I can get 3 different eyeboot hubs working which one do you have?

This one https://www.eyeboot.com/19-port-40a-usb3-hub.html  It is really nice, except that my pc doesn't recognize the device (moonlander) when I plug it in, comes up as 'unknown device'. I have not figure out yet how to force a driver...

>> Can you state what OS you are running (e.g. Windows 10 64-bit? Linux? Mac?)
Vista 32 bit, I installed the 32 bit driver and it works just fine on the USB ports on the computer. USB 2.0 ports. The HUB is USB 3

>> Did you install the driver prior to plugging in the USB devices?
Yes.

>> Did you check Device Manager to see if there are any USB devices with a (unknown device), You might try removing that and restarting computer.
Yes, that is the problem, they are coming up as unknown device. I did a full reboot, but it is the same problem.

>> Did you try using a different USB port on the Eyeboot?
Yes, it is on all of them it seems.

>> Can you attach a flash drive to the offending USB port and see if it recognized?
Yes I did that and that worked fine.

It seems that through the hub windows does not recognize what device the moonlander is. And I can neither install the driver manually. When I connect a moonlander directly to a usb port on my PC and go in device manager under com port and see for the driver, I see there are actually three driver files: two sys files and one dll. And those are picked up just fine. But not when I connect to the Eyeboot hub.

Frustrating!!

I can get 3 different eyeboot hubs working

which one do you have?

Can you state what OS you are running (e.g. Windows 10 64-bit? Linux? Mac?)
Did you install the driver prior to plugging in the USB devices?
Did you check Device Manager to see if there are any USB devices with a (unknown device), You might try removing that and restarting computer.


As you can see from my screenshot, MLD 0 is your first device. MLD 1 & 2 are your 2nd and 3rd device. I suggest you try a full reboot. Something is not being cleared.


Did you try using a different USB port on the Eyeboot?

Can you attach a flash drive to the offending USB port and see if it recognized? Again, might be a bad device recognition on that particular port that needs to be removed in Device Manager.

Upgraded from macOS 10.10.5 to 10.12.6. I don't know if I needed to install the UART driver, but your dmg worked out of the box. (I may have installed the newest UART prior.)

I wanted to run 700Mhz, but too unstable. Getting better hash rates collectively at stock 600 Mhz.

Look, got 8 running right now.

Any help much appreciated. Today I got my 6 moonlander 2's. I installed the sw. When I plug 1 or 2 into my USB 2 ports on my computer, everything works fine. For some reason bgfminer shows a MLD 0 miner that doesn't exist, no idea where it comes from. My two moonlanders are MLD 1 and 2. Sofar so good.

What the setup intro does not mention is that when you actually plug in a device it should say "installing USB to UART driver". Under device manager you can see the virtual com ports.

The problem is with my eyeboot USB hub. A real nice thing, looks professional. When I plug a USB HD into this hub, my computer recognises it. But when I plug in a moonlander, the power comes on (green led) but it is not recognized, i.e. I don't get the "installing driver" message. Obviously then bgfminer neither can communicate with the units. Now this is very decent hi-power hub by Eyeboot, so it really ought to work. I know the warnings on cheap hubs but this thing _should_ work.

I really want to get my 6 moonlanders a full speed, so... anyone any suggestions on how to troubleshoot my connections. I will keep trying and see what happens. If I should post this in another forum let me know. Any help much appreciated!!

As a side note, when plugged into my PC and hashing away, the two moonlanders are very quiet!, I barely can hear the fans. But on the HUB they were making a lot of noise!! Maybe the attachment is just not as firm

just pluged moonlander to my hub ..

result is this:

device is detected by dmesg - but i cant find it in lsusb - bfgminer wont find it as well.
This line seems to be the moonlander - after i pluged 2 - i got this line twice.

Bus 001 Device 012: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light

Still - BFGminer wont find it.

missing something, or maybe my high quality hub?

Greetings - Astrali

Pool 0 is hiding block contents from us.

And it doesn't mine anymore. Started doing that on Sunday I think it was.

Yes just change the "600" to 756 in the start_moonlander file.

I have get today my 2 Moonlanders from Bitshopper  and i try it first on win 7 and it all works fine with stock settings  !   After this i have them now running on my pi 3 and have done some testing with the mhz in the start file and for my 2 on the pi 3 stable working is 768 mhz


Regards  Lafu

Sounds like just changing the frequency to 756 in the code should be probably work without messing with the hardware screws? I'd rather just start with that.

756 is what I have found to be the optimal balance between hashrate and power on these chips. 756 runs fine at about .7v, so you can turn core voltage down a bit, and turn down memory voltage as low as your ASIC can handle (~.75-. for best power draw.

Check out my tuning guide in OP on how to fine tune these using --benchmark flag.

I'm questioning whether plugable usb hub can handle the power draw. I was able to get 4 Mh/s on port 1, 4, 7 initially. At a later point one of the ML2 goes to 1 Mh/s on the port. That's what it stabilizes at. Either they are running too hot just with the given fan or the power draw is too great at stock running at 744 Mhz. I'm thinking I need something that can draw more power reliably. Maybe cheapo home made HUB will be better than Unpluggable. Right now, I can only plug in 3 USB ASIC. Any more and there are stability issues or unoptimal performance.

Look at device 1 and 3.