Bitcoin Forum
November 27, 2021, 06:28:52 PM *
News: Latest Bitcoin Core release: 22.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 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 ... 108 »
  Print  
Author Topic: Official FutureBit Moonlander 2 Driver and Support Thread  (Read 69152 times)
thestockfadi
Newbie
*
Offline Offline

Activity: 48
Merit: 0


View Profile
December 23, 2017, 03:26:19 PM
 #641

New Error

https://image.ibb.co/mXqcH6/now_what.png
1638037732
Hero Member
*
Offline Offline

Posts: 1638037732

View Profile Personal Message (Offline)

Ignore
1638037732
Reply with quote  #2

1638037732
Report to moderator
1638037732
Hero Member
*
Offline Offline

Posts: 1638037732

View Profile Personal Message (Offline)

Ignore
1638037732
Reply with quote  #2

1638037732
Report to moderator
1638037732
Hero Member
*
Offline Offline

Posts: 1638037732

View Profile Personal Message (Offline)

Ignore
1638037732
Reply with quote  #2

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

Posts: 1638037732

View Profile Personal Message (Offline)

Ignore
1638037732
Reply with quote  #2

1638037732
Report to moderator
1638037732
Hero Member
*
Offline Offline

Posts: 1638037732

View Profile Personal Message (Offline)

Ignore
1638037732
Reply with quote  #2

1638037732
Report to moderator
1638037732
Hero Member
*
Offline Offline

Posts: 1638037732

View Profile Personal Message (Offline)

Ignore
1638037732
Reply with quote  #2

1638037732
Report to moderator
thestockfadi
Newbie
*
Offline Offline

Activity: 48
Merit: 0


View Profile
December 23, 2017, 03:52:51 PM
 #642

no device error. .

https://image.ibb.co/mxNcjm/no_device.png


Now back to the regular error which is telling me that MLD1 ASIC has stopped hashing, attempting to restart
MLD1 : unrecognized response. .




I have turned down the frequency to 384 as instructed . . At this frequency it's only hashing at 1.97 but I am still getting the MLD1 Errors. .
jstefanop
Legendary
*
Offline Offline

Activity: 1929
Merit: 1310


View Profile
December 23, 2017, 04:20:48 PM
 #643

Code:
pi@raspberrypi:~ $ dmesg
[1277666.945413] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[1277666.945533] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[1277667.037557] usb 1-1.4.3: USB disconnect, device number 57
[1277667.037986] cp210x ttyUSB0: failed set request 0x7 status: -19
[1277667.038007] cp210x ttyUSB0: failed set request 0x12 status: -19
[1277667.038020] cp210x ttyUSB0: failed set request 0x0 status: -19
[1277667.038519] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[1277667.038582] cp210x 1-1.4.3:1.0: device disconnected

this is what i get in dmesg when i attach my 4th moonlander from eyeboot.
ideas whats causing this?

lsusb won't find the device neither it will be seen by bfgminer

Green light on, fan is running!


Greetings - Astrali

That’s the error you usually get when you are using too long/bad extenender. Have you tried plugging that one into another port/PC?

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
Astrali
Full Member
***
Offline Offline

Activity: 281
Merit: 122

Crypto Addicted


View Profile WWW
December 23, 2017, 04:52:44 PM
 #644

Code:
pi@raspberrypi:~ $ dmesg
[1277666.945413] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[1277666.945533] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[1277667.037557] usb 1-1.4.3: USB disconnect, device number 57
[1277667.037986] cp210x ttyUSB0: failed set request 0x7 status: -19
[1277667.038007] cp210x ttyUSB0: failed set request 0x12 status: -19
[1277667.038020] cp210x ttyUSB0: failed set request 0x0 status: -19
[1277667.038519] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[1277667.038582] cp210x 1-1.4.3:1.0: device disconnected

this is what i get in dmesg when i attach my 4th moonlander from eyeboot.
ideas whats causing this?

lsusb won't find the device neither it will be seen by bfgminer

Green light on, fan is running!


Greetings - Astrali

That’s the error you usually get when you are using too long/bad extenender. Have you tried plugging that one into another port/PC?

i had device in a 20 cm long cheap extender - but now i get same error when i plug it directly in my hub where all the others went fine. (remove 1 of 3 - plug this one in - only 2 work - remove this one and put back other one - all 3 work).
(3x Bitshopper moonlander 1x Eyeboot Moonlander).
The eyeboot one worked before on low mhz (600) on my windows pc on a long extender directly at an usb 3.0 port.
windows doesnt recognize it as well anymore Sad

did i lost 1 baby?

Join the mining! pool.cryptopowered.club    Smiley   || Need a miner? Rent one! MiningRigRentals
jstefanop
Legendary
*
Offline Offline

Activity: 1929
Merit: 1310


View Profile
December 23, 2017, 05:05:13 PM
 #645

Code:
pi@raspberrypi:~ $ dmesg
[1277666.945413] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[1277666.945533] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[1277667.037557] usb 1-1.4.3: USB disconnect, device number 57
[1277667.037986] cp210x ttyUSB0: failed set request 0x7 status: -19
[1277667.038007] cp210x ttyUSB0: failed set request 0x12 status: -19
[1277667.038020] cp210x ttyUSB0: failed set request 0x0 status: -19
[1277667.038519] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[1277667.038582] cp210x 1-1.4.3:1.0: device disconnected

this is what i get in dmesg when i attach my 4th moonlander from eyeboot.
ideas whats causing this?

lsusb won't find the device neither it will be seen by bfgminer

Green light on, fan is running!


Greetings - Astrali

That’s the error you usually get when you are using too long/bad extenender. Have you tried plugging that one into another port/PC?

i had device in a 20 cm long cheap extender - but now i get same error when i plug it directly in my hub where all the others went fine. (remove 1 of 3 - plug this one in - only 2 work - remove this one and put back other one - all 3 work).
(3x Bitshopper moonlander 1x Eyeboot Moonlander).
The eyeboot one worked before on low mhz (600) on my windows pc on a long extender directly at an usb 3.0 port.
windows doesnt recognize it as well anymore Sad

did i lost 1 baby?

Doubt an extender could fry it unless it was internally shorted. If you plug it directly into USB port do you get the same error message?

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
Astrali
Full Member
***
Offline Offline

Activity: 281
Merit: 122

Crypto Addicted


View Profile WWW
December 23, 2017, 05:48:28 PM
 #646

Code:
pi@raspberrypi:~ $ dmesg
[1277666.945413] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[1277666.945533] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[1277667.037557] usb 1-1.4.3: USB disconnect, device number 57
[1277667.037986] cp210x ttyUSB0: failed set request 0x7 status: -19
[1277667.038007] cp210x ttyUSB0: failed set request 0x12 status: -19
[1277667.038020] cp210x ttyUSB0: failed set request 0x0 status: -19
[1277667.038519] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[1277667.038582] cp210x 1-1.4.3:1.0: device disconnected

this is what i get in dmesg when i attach my 4th moonlander from eyeboot.
ideas whats causing this?

lsusb won't find the device neither it will be seen by bfgminer

Green light on, fan is running!


Greetings - Astrali

That’s the error you usually get when you are using too long/bad extenender. Have you tried plugging that one into another port/PC?

i had device in a 20 cm long cheap extender - but now i get same error when i plug it directly in my hub where all the others went fine. (remove 1 of 3 - plug this one in - only 2 work - remove this one and put back other one - all 3 work).
(3x Bitshopper moonlander 1x Eyeboot Moonlander).
The eyeboot one worked before on low mhz (600) on my windows pc on a long extender directly at an usb 3.0 port.
windows doesnt recognize it as well anymore Sad

did i lost 1 baby?

Doubt an extender could fry it unless it was internally shorted. If you plug it directly into USB port do you get the same error message?

on my RPI i cant directly connect it (PSU to weak) and on windows i dont get this detailed message ..

lets guess i fried something .. which part would break? would this be visible?
can it be replaced?

thanks for your help by the way Smiley

Join the mining! pool.cryptopowered.club    Smiley   || Need a miner? Rent one! MiningRigRentals
HagssFIN
Legendary
*
Offline Offline

Activity: 2142
Merit: 1596


Electrical engineer (B.E.). Mining since 2014.


View Profile WWW
December 23, 2017, 10:40:30 PM
 #647

I bought one of these from ASICPuppy.

What a great stick miner, thank you jstefanop.  Smiley

I run this with my Windows PC in a USB 3 port.
The pre-compiled bfgminer was really easy peacy lemon squeezy.

I personally found a sweet spot for settings by tuning the Core Voltage to 0.655V and running it at 576 MHz frequency.
600 MHz was really unstable with lots of rejects and some hw error.

The hash rate is about 3.2 Mh/s.
And the power consumption is not too much for the USB 3 port.

I'm trying to get lucky, I have pointed it to a LTC solo pool.  Cheesy

philipma1957
Legendary
*
Offline Offline

Activity: 3220
Merit: 3862



View Profile
December 24, 2017, 12:11:33 AM
 #648

I bought one of these from ASICPuppy.

What a great stick miner, thank you jstefanop.  Smiley

I run this with my Windows PC in a USB 3 port.
The pre-compiled bfgminer was really easy peacy lemon squeezy.

I personally found a sweet spot for settings by tuning the Core Voltage to 0.655V and running it at 576 MHz frequency.
600 MHz was really unstable with lots of rejects and some hw error.

The hash rate is about 3.2 Mh/s.
And the power consumption is not too much for the USB 3 port.

I'm trying to get lucky, I have pointed it to a LTC solo pool.  Cheesy

me too.

I like these sticks  I am pointed at this pool

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

I ordered 2 more sticks  from asicpuppy



did a video of them,

https://www.youtube.com/watch?v=H-4QqZKMKWA

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

Activity: 74
Merit: 10

crestonium.io - 0% fees cryptobank


View Profile WWW
December 24, 2017, 01:14:55 AM
 #649

Further update.
Changing core pot to 0.83v leaving memory at stock results in some units now hashing consistently at 6 and 5 with <1% errors!


NathanEHarvey
Newbie
*
Offline Offline

Activity: 40
Merit: 0


View Profile WWW
December 24, 2017, 04:50:31 AM
 #650

Quote
Please download the new driver release which has numerous bug fixes and enhancements

https://github.com/jstefanop/bfgminer/releases/tag/bfgminer-5.4.2-futurebit2-beta2

My computer keeps flagging the bfgminer-5.4.2-futurebit2-win64.zip as a trojan virus... anyone else?  Undecided
NathanEHarvey
Newbie
*
Offline Offline

Activity: 40
Merit: 0


View Profile WWW
December 24, 2017, 04:54:21 AM
 #651

Quote
Trojan:Win32/Fuery.A!cl


Alert level: Severe Detected with Windows Defender Antivirus
slanislaw
Member
**
Offline Offline

Activity: 107
Merit: 11


View Profile
December 24, 2017, 06:07:39 AM
 #652

Quote
Please download the new driver release which has numerous bug fixes and enhancements

https://github.com/jstefanop/bfgminer/releases/tag/bfgminer-5.4.2-futurebit2-beta2

My computer keeps flagging the bfgminer-5.4.2-futurebit2-win64.zip as a trojan virus... anyone else?  Undecided

Mine too. Its a false positive. Disable the antivirus, download, then add an exclusion and turn your av back on.
Fenboy
Newbie
*
Offline Offline

Activity: 83
Merit: 0


View Profile
December 24, 2017, 11:22:45 AM
 #653

I bought one of these from ASICPuppy.

What a great stick miner, thank you jstefanop.  Smiley

I run this with my Windows PC in a USB 3 port.
The pre-compiled bfgminer was really easy peacy lemon squeezy.

I personally found a sweet spot for settings by tuning the Core Voltage to 0.655V and running it at 576 MHz frequency.
600 MHz was really unstable with lots of rejects and some hw error.

The hash rate is about 3.2 Mh/s.
And the power consumption is not too much for the USB 3 port.

I'm trying to get lucky, I have pointed it to a LTC solo pool.  Cheesy

I was running 1x Moonlander from USB 3 at 796 MHz to get 4.5 MH/s, dont know if your aiming for max hash?
HagssFIN
Legendary
*
Offline Offline

Activity: 2142
Merit: 1596


Electrical engineer (B.E.). Mining since 2014.


View Profile WWW
December 24, 2017, 11:24:40 AM
 #654

I bought one of these from ASICPuppy.

What a great stick miner, thank you jstefanop.  Smiley

I run this with my Windows PC in a USB 3 port.
The pre-compiled bfgminer was really easy peacy lemon squeezy.

I personally found a sweet spot for settings by tuning the Core Voltage to 0.655V and running it at 576 MHz frequency.
600 MHz was really unstable with lots of rejects and some hw error.

The hash rate is about 3.2 Mh/s.
And the power consumption is not too much for the USB 3 port.

I'm trying to get lucky, I have pointed it to a LTC solo pool.  Cheesy

I was running 1x Moonlander from USB 3 at 796 MHz to get 4.5 MH/s, dont know if your aiming for max hash?

That's too much for a USB 3 port.

Unless you are actually running it with a powered USB hub.

Fenboy
Newbie
*
Offline Offline

Activity: 83
Merit: 0


View Profile
December 24, 2017, 11:33:01 AM
 #655

USB port on front of PC. Usb meter showed 1.93A at 4.55v, ran fine 4.52MH/s
8-bit
Sr. Member
****
Offline Offline

Activity: 417
Merit: 250



View Profile
December 24, 2017, 06:53:47 PM
 #656

Hey Guys, happy holidays!!

I'm setting up a 4 of these guys for a friend. The latest drivers seem to install successfully. I left the Start_Moonlander2 batch info as is, just to test that everything was working correctly, before I edit the pool info..

It doesn't seem to start mining, the command window comes up and when i press 'any key' it closes without really getting into the bfg miner window. Any ideas?


CannaCoin.tech - The Future of the Cannabis Industry | CannaCoin Community Manager
“The greatness of a man is not in how much wealth he acquires, but in his integrity and his ability to affect those around him positively” ― Bob Marley
jstefanop
Legendary
*
Offline Offline

Activity: 1929
Merit: 1310


View Profile
December 24, 2017, 07:04:40 PM
 #657

Hey Guys, happy holidays!!

I'm setting up a 4 of these guys for a friend. The latest drivers seem to install successfully. I left the Start_Moonlander2 batch info as is, just to test that everything was working correctly, before I edit the pool info..

It doesn't seem to start mining, the command window comes up and when i press 'any key' it closes without really getting into the bfg miner window. Any ideas?



Guys you really need to start reading the first 3 posts (that included the FAQ section which has the answer to this question) in this thread before posting. The thread is already over 30 pages long and does not need to be cluttered with posts like this. Your wasting your own time by not reading the basics first, and making it hard for people with real issues to find an answer.

Quote
Q: Im using windows and nothing happens when i click the start_moonlander.bat file
Your anti-virus software most likely deleted bfgminer.exe when you extracted it. Make sure you setup a rule so it does not do this.

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
philipma1957
Legendary
*
Offline Offline

Activity: 3220
Merit: 3862



View Profile
December 24, 2017, 08:26:06 PM
 #658

Hey Guys, happy holidays!!

I'm setting up a 4 of these guys for a friend. The latest drivers seem to install successfully. I left the Start_Moonlander2 batch info as is, just to test that everything was working correctly, before I edit the pool info..

It doesn't seem to start mining, the command window comes up and when i press 'any key' it closes without really getting into the bfg miner window. Any ideas?



Guys you really need to start reading the first 3 posts (that included the FAQ section which has the answer to this question) in this thread before posting. The thread is already over 30 pages long and does not need to be cluttered with posts like this. Your wasting your own time by not reading the basics first, and making it hard for people with real issues to find an answer.

Quote
Q: Im using windows and nothing happens when i click the start_moonlander.bat file
Your anti-virus software most likely deleted bfgminer.exe when you extracted it. Make sure you setup a rule so it does not do this.


make a folder on you desktop
mining software
make a folder inside it call it
call it virus  allowed zone


go to your antivirus

exclude both folders from the virus protector/


download software  and  put it directly into  virus allowed zone


so you have a nest

desktop-mining software -virus allowed zone-bgminer


open bgminer and it will run and not  be deleted 

I see BTC as the super highway and alt coins as taxis and trucks needed to move transactions.
lennyNO
Newbie
*
Offline Offline

Activity: 76
Merit: 0


View Profile
December 25, 2017, 10:28:57 PM
 #659

I have this weird problem that started after I received my 2nd batch of 5 MLD2s last friday. I think the same problem has been reported earlier by others but I never found a good resolution.

First I had 6 MLD2s, no problems, I was running them all the way up to 954Mhz but now I have scaled back again to 876Mhz.

Last friday I received a 2nd batch of 5 (total 11), and since then 1 or 2 of the MLDs hash at about 1/2 the normal rate (normal is around 5Mh/s with my clock setting, these sit around 2-3Mh/s). Several people have reported a problem like this before.

What happens is that at least for one of the MLDs I first get the error "MLD : unrecognized response", then usually a "MLD: ASIC has stopped hashing, attempting to restart" and from there it goes downhill. And the MLD usually settles around 2-3Mh/s.

The red lights keep flashing and I really cannot tell which one is hashing at halve speed, I can't tell a difference. Which miner gets assigned to which MLD seems also random and bfgminer gives a ASIC serial number of sorts, but one has plug in one MLD after the other, restart bfgminer to see which ASIC serial number corresponds with which MLD serial number to see which physical unit is playing up. So it is close to impossible for me to tell which 1 or 2 MLDs or USB ports they are connected to cause problems.


What I understand is that too low mem voltage may result in more frequent restarts, but that seems not the problem
What I understand is that too low core voltage may result in more HW errors, but that is neither the problem

I am still not clear about the symptoms in a situation when the MLD draws too much current, but as I am using the eyeboot industrual 19 port 40A hub with only 11 units, power should not be the issue. I have also observed the same going back to 5 units, so it seems something with 1-2 units. But I have no clue what!!!

I have turned of the USB hub, disconnected everything, reconnected, restarted, still same problem, not sure if same MLD?

Other details
Using win10, latest bfgminer + drivers, clock at 900MHz, problem also seen at lower clock (but I have not tried every clock setting).

It drives me nuts. I could live with one unit that's having issues, but 2 is too much.

I tried to google the unrecognized response, but did not get any further, so I might now check the source code and see what kind of conditions may trigger this.

Any input much appreciated.
aarons6
Legendary
*
Offline Offline

Activity: 1736
Merit: 1006


View Profile
December 25, 2017, 10:41:31 PM
 #660

I have this weird problem that started after I received my 2nd batch of 5 MLD2s last friday. I think the same problem has been reported earlier by others but I never found a good resolution.

First I had 6 MLD2s, no problems, I was running them all the way up to 954Mhz but now I have scaled back again to 876Mhz.

Last friday I received a 2nd batch of 5 (total 11), and since then 1 or 2 of the MLDs hash at about 1/2 the normal rate (normal is around 5Mh/s with my clock setting, these sit around 2-3Mh/s). Several people have reported a problem like this before.

What happens is that at least for one of the MLDs I first get the error "MLD : unrecognized response", then usually a "MLD: ASIC has stopped hashing, attempting to restart" and from there it goes downhill. And the MLD usually settles around 2-3Mh/s.

The red lights keep flashing and I really cannot tell which one is hashing at halve speed, I can't tell a difference. Which miner gets assigned to which MLD seems also random and bfgminer gives a ASIC serial number of sorts, but one has plug in one MLD after the other, restart bfgminer to see which ASIC serial number corresponds with which MLD serial number to see which physical unit is playing up. So it is close to impossible for me to tell which 1 or 2 MLDs or USB ports they are connected to cause problems.


What I understand is that too low mem voltage may result in more frequent restarts, but that seems not the problem
What I understand is that too low core voltage may result in more HW errors, but that is neither the problem

I am still not clear about the symptoms in a situation when the MLD draws too much current, but as I am using the eyeboot industrual 19 port 40A hub with only 11 units, power should not be the issue. I have also observed the same going back to 5 units, so it seems something with 1-2 units. But I have no clue what!!!

I have turned of the USB hub, disconnected everything, reconnected, restarted, still same problem, not sure if same MLD?

Other details
Using win10, latest bfgminer + drivers, clock at 900MHz, problem also seen at lower clock (but I have not tried every clock setting).

It drives me nuts. I could live with one unit that's having issues, but 2 is too much.

I tried to google the unrecognized response, but did not get any further, so I might now check the source code and see what kind of conditions may trigger this.

Any input much appreciated.

try to double the worker difficulty pool side..

what i found is if its too low, the usb gets saturated somehow and it cant keep up..
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 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 ... 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!