Bitcoin Forum
November 30, 2021, 09:43:56 AM *
News: Latest Bitcoin Core release: 22.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 [72] 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 »
  Print  
Author Topic: Official FutureBit Moonlander 2 Driver and Support Thread  (Read 69170 times)
scoobysportD
Jr. Member
*
Offline Offline

Activity: 105
Merit: 1


View Profile
March 29, 2018, 06:09:02 PM
 #1421

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.
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.
1638265436
Hero Member
*
Offline Offline

Posts: 1638265436

View Profile Personal Message (Offline)

Ignore
1638265436
Reply with quote  #2

1638265436
Report to moderator
1638265436
Hero Member
*
Offline Offline

Posts: 1638265436

View Profile Personal Message (Offline)

Ignore
1638265436
Reply with quote  #2

1638265436
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1638265436
Hero Member
*
Offline Offline

Posts: 1638265436

View Profile Personal Message (Offline)

Ignore
1638265436
Reply with quote  #2

1638265436
Report to moderator
1638265436
Hero Member
*
Offline Offline

Posts: 1638265436

View Profile Personal Message (Offline)

Ignore
1638265436
Reply with quote  #2

1638265436
Report to moderator
jstefanop
Legendary
*
Offline Offline

Activity: 1929
Merit: 1310


View Profile
March 29, 2018, 06:19:20 PM
 #1422


Thats not formatted correctly, you have another pool listed in the password input (-p), you should have your password in there, then "-o" for the second pool URL.

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?



I've been having issues matching the serial numbers to the stickers on the devices I thought that too about the last few digits however some of my serial numbers share the last few digits and none match the stickers at all  Huh:
Code:
/dev/ttyUSB0 - FutureBit_FutureBit_Moonlander_2_3e8f26157a48e71189f626920d6e317d
/dev/ttyUSB1 - FutureBit_FutureBit_Moonlander_2_c6c19e18505fe711ada0600a3f3d1008
/dev/ttyUSB3 - FutureBit_FutureBit_Moonlander_2_22c4d13f4c5fe711977d5f0a3f3d1008
/dev/ttyUSB4 - FutureBit_FutureBit_Moonlander_2_ce1d16ae8c48e71195a826920d6e317d
/dev/ttyUSB2 - FutureBit_FutureBit_Moonlander_2_f20ededd7f48e7119f5b1b920d6e317d


yea I can do that, probably not till tomorrow though. I'm really hoping the new hub turns up sooner rather than later
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.

The numbers BFGminer is spitting out seem like hexadecimal. Maybe if you convert that to decimal like the s/n tags use they may match up?
Tried figuring it out that way, can't come up with anything that matches unfortunately.

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.


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. 

Project Apollo: A Pod Miner Designed for the Home https://bitcointalk.org/index.php?topic=4974036
FutureBit Moonlander 2 USB Scrypt Stick Miner: https://bitcointalk.org/index.php?topic=2125643.0
LTC:LX5vpxrQE4eLRLPobKwZhw2comkKFCh3p4 - BTC:14w9Lea6kdVzspJk8TQRe7qSYu9LhzJJsh
scoobysportD
Jr. Member
*
Offline Offline

Activity: 105
Merit: 1


View Profile
March 31, 2018, 07:32:36 AM
 #1423


I've been having issues matching the serial numbers to the stickers on the devices I thought that too about the last few digits however some of my serial numbers share the last few digits and none match the stickers at all  Huh:
Code:
/dev/ttyUSB0 - FutureBit_FutureBit_Moonlander_2_3e8f26157a48e71189f626920d6e317d
/dev/ttyUSB1 - FutureBit_FutureBit_Moonlander_2_c6c19e18505fe711ada0600a3f3d1008
/dev/ttyUSB3 - FutureBit_FutureBit_Moonlander_2_22c4d13f4c5fe711977d5f0a3f3d1008
/dev/ttyUSB4 - FutureBit_FutureBit_Moonlander_2_ce1d16ae8c48e71195a826920d6e317d
/dev/ttyUSB2 - FutureBit_FutureBit_Moonlander_2_f20ededd7f48e7119f5b1b920d6e317d


yea I can do that, probably not till tomorrow though. I'm really hoping the new hub turns up sooner rather than later

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 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?
Bitfort
Sr. Member
****
Offline Offline

Activity: 840
Merit: 327

invest trade and gamble wisely


View Profile
March 31, 2018, 07:48:56 AM
 #1424


I've been having issues matching the serial numbers to the stickers on the devices I thought that too about the last few digits however some of my serial numbers share the last few digits and none match the stickers at all  Huh:
Code:
/dev/ttyUSB0 - FutureBit_FutureBit_Moonlander_2_3e8f26157a48e71189f626920d6e317d
/dev/ttyUSB1 - FutureBit_FutureBit_Moonlander_2_c6c19e18505fe711ada0600a3f3d1008
/dev/ttyUSB3 - FutureBit_FutureBit_Moonlander_2_22c4d13f4c5fe711977d5f0a3f3d1008
/dev/ttyUSB4 - FutureBit_FutureBit_Moonlander_2_ce1d16ae8c48e71195a826920d6e317d
/dev/ttyUSB2 - FutureBit_FutureBit_Moonlander_2_f20ededd7f48e7119f5b1b920d6e317d


yea I can do that, probably not till tomorrow though. I'm really hoping the new hub turns up sooner rather than later

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 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?

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.


MY HINTs
◄M► MINING
◄G► GAMBLING
◄E► EXCHANGE

◄E► (KCS) Kucoin-Staking, Auto-Lending, Trading-Bot
◄E► (BNB) Binance-Staking, Savings, 10% RefBack
◄E► (TRX) Poloniex-Staking, Lending, Fee Discount
◄E► (LEO) Bitfinex-Staking, Auto-Lending

◄G► Betfury-Faucet, Dividend Earnings (BFG holders, mine BFG by playing)
◄G► Bitvest -  Faucet, Bankroll Invest
◄G► CryptoGames-Faucet, Lotto
◄G► PrimeDice-Faucet

◄M► Prohashing (Multipool)-Payout in any coin, get 0.50% bonus for 30 days
◄M► MiningRigRentals (Marketplace)-buy hashrate or rent your miners
◄M► Viabtc  (Pool)-payout to Coinex (exchnage) without fees


scoobysportD
Jr. Member
*
Offline Offline

Activity: 105
Merit: 1


View Profile
March 31, 2018, 12:28:04 PM
 #1425


I've been having issues matching the serial numbers to the stickers on the devices I thought that too about the last few digits however some of my serial numbers share the last few digits and none match the stickers at all  Huh:
Code:
/dev/ttyUSB0 - FutureBit_FutureBit_Moonlander_2_3e8f26157a48e71189f626920d6e317d
/dev/ttyUSB1 - FutureBit_FutureBit_Moonlander_2_c6c19e18505fe711ada0600a3f3d1008
/dev/ttyUSB3 - FutureBit_FutureBit_Moonlander_2_22c4d13f4c5fe711977d5f0a3f3d1008
/dev/ttyUSB4 - FutureBit_FutureBit_Moonlander_2_ce1d16ae8c48e71195a826920d6e317d
/dev/ttyUSB2 - FutureBit_FutureBit_Moonlander_2_f20ededd7f48e7119f5b1b920d6e317d


yea I can do that, probably not till tomorrow though. I'm really hoping the new hub turns up sooner rather than later

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 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?

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.


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  Huh

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.
pyroandy
Newbie
*
Offline Offline

Activity: 88
Merit: 0


View Profile
March 31, 2018, 01:02:32 PM
 #1426


I've been having issues matching the serial numbers to the stickers on the devices I thought that too about the last few digits however some of my serial numbers share the last few digits and none match the stickers at all  Huh:
Code:
/dev/ttyUSB0 - FutureBit_FutureBit_Moonlander_2_3e8f26157a48e71189f626920d6e317d
/dev/ttyUSB1 - FutureBit_FutureBit_Moonlander_2_c6c19e18505fe711ada0600a3f3d1008
/dev/ttyUSB3 - FutureBit_FutureBit_Moonlander_2_22c4d13f4c5fe711977d5f0a3f3d1008
/dev/ttyUSB4 - FutureBit_FutureBit_Moonlander_2_ce1d16ae8c48e71195a826920d6e317d
/dev/ttyUSB2 - FutureBit_FutureBit_Moonlander_2_f20ededd7f48e7119f5b1b920d6e317d


yea I can do that, probably not till tomorrow though. I'm really hoping the new hub turns up sooner rather than later

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 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:
https://ip.bitcointalk.org/?u=http%3A%2F%2Fi65.tinypic.com%2F20st3tg.jpg&t=587&c=AevpAj9atJZJHg
And how is it matched?

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.


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  Huh

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.

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

Activity: 105
Merit: 1


View Profile
March 31, 2018, 02:05:56 PM
Last edit: March 31, 2018, 03:12:55 PM by scoobysportD
 #1427

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  Huh

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.

My guess would be its a USB update thing. By restarting BFGminer you are forcing the USB ports to update?
Don't think so; bfgminer has been restarted multiple times before...
philipma1957
Legendary
*
Offline Offline

Activity: 3220
Merit: 3878



View Profile
March 31, 2018, 02:13:51 PM
 #1428


...

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  Huh

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 Grin

I see BTC as the super highway and alt coins as taxis and trucks needed to move transactions.
scoobysportD
Jr. Member
*
Offline Offline

Activity: 105
Merit: 1


View Profile
March 31, 2018, 03:14:00 PM
 #1429


...

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  Huh

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.

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 Grin
[/quote]
But were you able to see all the UUID's from first boot in BFGminer? Mining was no problem on my setup either.
philipma1957
Legendary
*
Offline Offline

Activity: 3220
Merit: 3878



View Profile
March 31, 2018, 03:51:45 PM
 #1430


...

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  Huh

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.

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 Grin
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

I see BTC as the super highway and alt coins as taxis and trucks needed to move transactions.
scoobysportD
Jr. Member
*
Offline Offline

Activity: 105
Merit: 1


View Profile
March 31, 2018, 10:48:58 PM
 #1431


...

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  Huh

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.

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 Grin
But were you able to see all the UUID's from first boot in BFGminer? Mining was no problem on my setup either.

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
??
joyfulocean
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
April 01, 2018, 04:23:10 PM
 #1432

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)
Code:
sudo apt install libjansson-dev libcurl4-openssl-dev

pyroandy
Newbie
*
Offline Offline

Activity: 88
Merit: 0


View Profile
April 01, 2018, 04:53:11 PM
 #1433

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)
Code:
sudo apt install libjansson-dev libcurl4-openssl-dev



Quote
Jr. Member
*


Activity: 49
Merit: 0


View Profile
   
Re: Official FutureBit Moonlander 2 Driver and Support Thread
November 22, 2017, 11:55:42 PM
 #33
I can confirm that Astrali's instructions work perfectly - I don't have the Moonlander2s yet so I haven't run the test yet, but everything compiled without any errors. You might want to add to sudo apt-get update and sudo apt-get dist-upgrade first though, even on a fresh install I got errors trying to install the necessary library files until I had run them. Thanks again Astrali, that was a huge help!

One more question - if I'm going to be running two miners should I just have just one worker information entered?

Have you upgraded your Operating System?
jstefanop
Legendary
*
Offline Offline

Activity: 1929
Merit: 1310


View Profile
April 01, 2018, 07:42:44 PM
 #1434

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  Grin

Project Apollo: A Pod Miner Designed for the Home https://bitcointalk.org/index.php?topic=4974036
FutureBit Moonlander 2 USB Scrypt Stick Miner: https://bitcointalk.org/index.php?topic=2125643.0
LTC:LX5vpxrQE4eLRLPobKwZhw2comkKFCh3p4 - BTC:14w9Lea6kdVzspJk8TQRe7qSYu9LhzJJsh
pyroandy
Newbie
*
Offline Offline

Activity: 88
Merit: 0


View Profile
April 01, 2018, 08:19:38 PM
 #1435

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  Grin

Would it be a Moonlander 4 then?
scoobysportD
Jr. Member
*
Offline Offline

Activity: 105
Merit: 1


View Profile
April 01, 2018, 11:55:15 PM
 #1436

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  Grin
Sounds more like self destruct mode  Wink
pyroandy
Newbie
*
Offline Offline

Activity: 88
Merit: 0


View Profile
April 02, 2018, 12:48:17 PM
 #1437

I thought somewhere in the long lengthy thread that someone posted the optimum settings for the highest efficiency for these Moonlanders.
Does anyone recall that?
I when thru the thread again and could not seem to find it.
Bitfort
Sr. Member
****
Offline Offline

Activity: 840
Merit: 327

invest trade and gamble wisely


View Profile
April 02, 2018, 01:04:34 PM
 #1438

I thought somewhere in the long lengthy thread that someone posted the optimum settings for the highest efficiency for these Moonlanders.
Does anyone recall that?
I when thru the thread again and could not seem to find it.

Only one I'm aware is in OP (search for: sweet spot).
But IMO it's not universal (each of my sticks has a bit different setting to keep the same level of HW errors .. had to tinker them individualy).

@jstefanop  good one with the asicboost. I bet you fooled few users.

MY HINTs
◄M► MINING
◄G► GAMBLING
◄E► EXCHANGE

◄E► (KCS) Kucoin-Staking, Auto-Lending, Trading-Bot
◄E► (BNB) Binance-Staking, Savings, 10% RefBack
◄E► (TRX) Poloniex-Staking, Lending, Fee Discount
◄E► (LEO) Bitfinex-Staking, Auto-Lending

◄G► Betfury-Faucet, Dividend Earnings (BFG holders, mine BFG by playing)
◄G► Bitvest -  Faucet, Bankroll Invest
◄G► CryptoGames-Faucet, Lotto
◄G► PrimeDice-Faucet

◄M► Prohashing (Multipool)-Payout in any coin, get 0.50% bonus for 30 days
◄M► MiningRigRentals (Marketplace)-buy hashrate or rent your miners
◄M► Viabtc  (Pool)-payout to Coinex (exchnage) without fees


pyroandy
Newbie
*
Offline Offline

Activity: 88
Merit: 0


View Profile
April 02, 2018, 03:44:41 PM
 #1439

I thought somewhere in the long lengthy thread that someone posted the optimum settings for the highest efficiency for these Moonlanders.
Does anyone recall that?
I when thru the thread again and could not seem to find it.

Only one I'm aware is in OP (search for: sweet spot).
But IMO it's not universal (each of my sticks has a bit different setting to keep the same level of HW errors .. had to tinker them individualy).

@jstefanop  good one with the asicboost. I bet you fooled few users.

Thanks found it in the very first post. Under the Tuning section. Core voltage .725V with a frequency of 756MHz.
ahumado84
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
April 02, 2018, 04:36:28 PM
 #1440

Hi! one of my mld began to stop for 10 secs every now and then and it stops continuously. Had everyone the same issue? I didn't change the config and worked for weeks until now. Alternatives? Thanks
Pages: « 1 ... 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 [72] 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!