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

same results with powering from usb port on the machine (non hub)?

I was running the stick for a while without any problem, but recently all of a sudden the bfgminer log started to look like this:

 [2018-01-10 19:41:27] Accepted 005114ba MLD 0  Diff 12m/7m
 [2018-01-10 19:41:33] Accepted 002be7f3 MLD 0  Diff 22m/7m
 [2018-01-10 19:41:48] MLD 0: ASIC has stopped hashing, attempting to restart
 [2018-01-10 19:41:49] Accepted 0038776b MLD 0  Diff 17m/7m
 [2018-01-10 19:41:50] New best share: 73m
 [2018-01-10 19:41:51] Accepted 000d96a3 MLD 0  Diff 73m/7m
 [2018-01-10 19:41:51] New best share: 115m
 [2018-01-10 19:41:52] Accepted 0008abcc MLD 0  Diff 115m/7m
 [2018-01-10 19:41:56] Accepted 002f34f2 MLD 0  Diff 21m/7m
 [2018-01-10 19:41:57] Accepted 006701af MLD 0  Diff 9m/7m
 [2018-01-10 19:42:16] Accepted 0045588e MLD 0  Diff 14m/7m
 [2018-01-10 19:42:17] Accepted 00256d79 ZUS 0aq Diff 26m/7m
 [2018-01-10 19:42:17] MLD 0: Unrecognized response
 [2018-01-10 19:42:19] Accepted 00798f2c ZUS 0bs Diff 8m/7m
 [2018-01-10 19:42:29] MLD 0: ASIC has stopped hashing, attempting to restart
 [2018-01-10 19:42:32] New block: ...a64ee3d1e95b8290 diff 3.66M (26.21T)
 [2018-01-10 19:42:32] Stratum from pool 0 detected new block
 [2018-01-10 19:42:42] Accepted 00592a2d MLD 0  Diff 11m/7m
 [2018-01-10 19:42:43] Accepted 00180ccc ZUS 0bk Diff 41m/7m
 [2018-01-10 19:42:47] Accepted 006127ac MLD 0  Diff 10m/7m
 [2018-01-10 19:42:53] Accepted 005c4df2 MLD 0  Diff 10m/7m
 [2018-01-10 19:42:55] MLD 0: Unrecognized response

etc

So it still hashes, but with frequent errors and at degraded hash rate.

All settings are default, I never overclocked the miner. No configuration changes (which I know about) were made. Powered USB hub.

What could it be?

current setup is 720Mhz. i used to run them on 768 but speed gain wasn't big, so i tuned back to 720. it worked for weeks on 720 with 8.20mhps total until day before yesterday

Well, you are getting around 4Mh/s for MLD0, and 700Mhz gives 700*5.66 (see page1) = 4.0Mh/s, so normally that means 700 or maybe 720Mhz.  At 768Mhz you should get 768*5.66 = 4.35Mh/s and you are not getting that by far (MLD0), so no matter what I think something is wrong and it could be powerdraw.  Why do you think you have zero problems if your hashrate is substantially below target? Or were MLD0 and MLD1 properly hashing at 4.35Mh/s in the past _and_ both have gone down?

the setup hasn't changed for weeks. i used to run them on 768 with zero problems, so this is not the case

Where are  getting that "clock freq" from?

If you are referring to the line that starts with "2" and has the 7.xx 7.xx 7.xx  - that is the combined hash rate of the two ML2's

Maybe I missed something.

Looks like you are using a clockfrequency of 700Mhz, did you maybe up this from the default of 600Mhz for 2 days ago? Might be that they are not getting enough power from the USB ports, are these two PC USB ports?

for last two days one stick started to stop hashing every few minutes. what to do? this is clearly not normal - sticks worked properly before

Wow I just got my first moonlander 2 today cause it was  so hard to find them and I am so impressed.  It took me like 5 minutes to set it up and mine.  Thanks to whoever created this masterpiece.

if you mean loading sittings via config.txt, yes that works fine. My branch is just a clone of bfgminer, with some things not specific to the moonlander disabled to help with debugging, but all the main features of bfgminer work with my build.

please check the order thread for those updates and don't post here for anything other than support questions.

It isn't being said so I will just confirm my suspicion is that since the MLD driver  (for FB MLD v2) is not merged with the main BFGMiner repo, the BFGMiner won't config file won't work with FutureBit Moonlander 2...@jstefanop ? 

I have to make a script to add all my custom goodiness for each miner? Just trying to see which direction I should put my resources into..

 

@jstefanop Is there any news about the pre batch 2 delivery date...

I'm sorry I came off a little harshing sounding. I just meant the issue is not related to Moonlander 2 because you've isolated the point of failure (the USB HUB). I hope your new hub works better for you. Good luck!

That usually points to the chipset that inside the USB HUB. Some chipsets have better support across OS than others.

Thank you for the response, I ordered a different hub to see if that solves the issue. For anyone in the future having similar issues I’ll post the results.

Some hubs under linux/pi have issues...I specifically know that anker hubs for example wont work under linux/pi due to some kernel/driver issue they still have not fixed.

Thats a hub error.

If ML2 is recognized when directly plugged in, how is this an ML2 issue?

Do you have a different computer which you could try attaching USB HUB to? For a USB HUB to be recognized, make sure you have no devices attached to it. Attach USB HUB solo to your computer and see if it is detected. After USB HUB is detected, then you attach other USB devices to it.