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

Would it be a Moonlander 4 then?

Today I have a special announcement. Thank you for everyone that bought a Moonlander 2, I am finally enabling ASICBOOST for everyone! Simply add "--enable_boost 1" at the end of the Moonlander config file, and your hashrate will double!

Sorry for not sharing this sooner, but we had to secretly mine double the speed to recoup all our dev costs 

Have you upgraded your Operating System?

Dear Astrali

I am a novice in Linux but bought Raspberry Pi3 to run the moonlander 2.
however I got stock in running "sudo apt install libjansson-dev libcurl4-openssl-dev"
in the terminal mode, i typed (copy and pasted as well) but it say "libjansson-dev" package can not be found. nor Libcurl4-dev has no condidate to install.
  (I may not describe it exactly cause i have to translate into English. )
What do i miss in here?

Thanks in advance.

install neccesary library files (thanks to jstefanop for providing this info)

yes  all 8 show but I have the hi end usb 3 hub from  eyeboot  and a pc with an i7 cpu and 16 gb ram plus a 500 gb ssd
[/quote]
The pc i first used also is i7, 64gigs of ram and 1tb ssd.. that doesn't mean anything for these miners though :p

Just to double check:
In BFGminer main display, when you enter "M" to see device display, you can see the unique ID of that device? Not just that it is hashing etc but the actual ID (20 digits or something like this:
3e8f26157a48e71189f626920d6e317d
??

But were you able to see all the UUID's from first boot in BFGminer? Mining was no problem on my setup either.
[/quote]

yes  all 8 show but I have the hi end usb 3 hub from  eyeboot  and a pc with an i7 cpu and 16 gb ram plus a 500 gb ssd

nope I run 8 sticks on a stud hub for weeks on end zero issues. set at  836 or 846 I can't rembember

here I am below

http://ltc.tbdice.org/users.htm


MWxsXgQXomddd4kjpGynNUhaTeDpy4QZLi     Self     44.4M / 0.000%   39.5M / 0.000%   37M / 0.087%   221M / 0.144%   265M / 0.145%   501.10945


ever the optimist  I solo mine
[/quote]
But were you able to see all the UUID's from first boot in BFGminer? Mining was no problem on my setup either.

Ah like that, yeah that'd be a possibility.

On a different, ODD note....
My MLD's kept quitting after a while, or at least, 4 of them did. I'm guessing it was just a bit too much per port on the hub to run 'em at 900mhz.
I've been fiddling with the settings and voltages, dropped mem voltage a bit. I currently have them all set at 876mhz, which for the past 20 minutes seems to work fine. But what i found odd was that while i was testing, i was running 1 stick at a time. When doing so, tapping the M to get the device menu in BFG allowed me to see the UUID. When i connected multiple, i still only saw that one UUID.

Then i disconnected all again. Plugged in one. Went to manage screen and yep, UUID. Plugged in the next. Went to manage screen and yep, UUID. Plugged in the next. Went to manage screen and nope, no UUID  

Restarted BFG, went to manage screen and then i had the 3rd UUID visible.. I'm kind of lost as to why/how. But then just went on with the 4th/5th/6th/7th MLD i have at the moment. Had to restart BFG a couple of times, but now all my MLD's are seen in the manage screen with their UUID.

My guess is that the BFGminer needs some more work in order to operate correctly with multiple sticks.
[/quote]

nope I run 8 sticks on a stud hub for weeks on end zero issues. set at  836 or 846 I can't rembember

here I am below

http://ltc.tbdice.org/users.htm


MWxsXgQXomddd4kjpGynNUhaTeDpy4QZLi     Self     44.4M / 0.000%   39.5M / 0.000%   37M / 0.087%   221M / 0.144%   265M / 0.145%   501.10945


ever the optimist  I solo mine

Don't think so; bfgminer has been restarted multiple times before...

My guess would be its a USB update thing. By restarting BFGminer you are forcing the USB ports to update?

Ah like that, yeah that'd be a possibility.

On a different, ODD note....
My MLD's kept quitting after a while, or at least, 4 of them did. I'm guessing it was just a bit too much per port on the hub to run 'em at 900mhz.
I've been fiddling with the settings and voltages, dropped mem voltage a bit. I currently have them all set at 876mhz, which for the past 20 minutes seems to work fine. But what i found odd was that while i was testing, i was running 1 stick at a time. When doing so, tapping the M to get the device menu in BFG allowed me to see the UUID. When i connected multiple, i still only saw that one UUID.

Then i disconnected all again. Plugged in one. Went to manage screen and yep, UUID. Plugged in the next. Went to manage screen and yep, UUID. Plugged in the next. Went to manage screen and nope, no UUID 

Restarted BFG, went to manage screen and then i had the 3rd UUID visible.. I'm kind of lost as to why/how. But then just went on with the 4th/5th/6th/7th MLD i have at the moment. Had to restart BFG a couple of times, but now all my MLD's are seen in the manage screen with their UUID.

My guess is that the BFGminer needs some more work in order to operate correctly with multiple sticks.

I understand there is no relation between UUID and the number on the sticker.

What you can do is plug single one. Check the UUID with bfgminer and mark that stick using your own system ( e.g. using marker rewrite the sticker to UUID, or add new sticker  ...).
Do the same with all of them one by one.

I must be missing or mis interpreting something here, because i still cannot figure out which code belongs to which MLD :S

Do we have to convert it to decimal? if so, which part? When looking at the above UUID, which relates to which miner in the picture:

And how is it matched?

The numbers are not related unfortunately. The sticker on the back is the actual serial number, and what bfgminer shows is the UUID coded in the hardware. For some reason how the UUID is generated the last digits are sometimes the same, but the first 10 digits or so are always unique to each stick. You can match these first few digits to each serial number on the back. 

I'm running at 0.8-0.82 core with 900mhz so you've got some room left.

You bet your ass it could be worse!! Only 4 quid?? I had to pay just shy of 40 euro's in taxes and "administrative" charges.

managed to test the core voltage as between 0.71 & 0.72 my meter was fluctuating between the two, memory voltage is around 0.78.
I'll start tweaking when this new hub turns up. £3.98 import tax to pay before they'll deliver it, my governments so petty still it could be worse.

my rule of thumb for scrypt

256*mh

so I set difficulty on these to either 768 or 512 depending on the pool. I set the lower difficulty on multipools that switch a lot

I am going to assume then that the two serial numbers are not related to each other. The number that BFGminer is reading is probably hard coded into the chip.
Maybe check them one at a time in BFGminer and put your own label on them.

I read that the difficulty preset has to be in the range of the pools accepted difficulty. Do your pools have two different difficulties?

On the subject of difficulty, what is the most profitable difficulty to run these miners at? I have one MLD2 mining in the LiteCoin pool.

Those pools both run without passwords, so not to sure what to enter then? I tried 'x' but then it came back with this error:
Unexpected extra commandline arguments

After that, i removed the difficulty setting, then it did run.
It now runs with this code:
bfgminer.exe --scrypt -o stratum+tcp://pool.tittiecoin.com:3335 -u TEmAH67jzTRxFQP1cqZ64F4Bh5T1JsBpwo -p x -o stratum+tcp://tittiecoin.p2p.0x0a.nl:28008 -u TEmAH67jzTRxFQP1cqZ64F4Bh5T1JsBpwo -p x -S MLD:all --set MLD:clock=900
 pause

But, when i try to enter d=1024 for one of the pools, it fails again. When using -d=1024 it disables the MLD's.

Is it impossible to set a difficulty when having a failover pool?


Great, thanks! Hope you'll like the hub as much as i do. With 5 MLD's you shouldn't have any trouble at all running with that hub at 900mhz.

Tried figuring it out that way, can't come up with anything that matches unfortunately.

I learned how to set up and run SSH with Putty last night. Now to figure out "screen" Thanks guys