Bitcoin Forum
May 27, 2024, 06:30:34 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Bitcoin / Hardware / Re: Official FutureBit Apollo BTC Software/Image and Support thread on: November 20, 2021, 04:47:56 PM
Bought 3 units in Batch 1.

Only one of which had a working front LED. I was informed that the contacts to the other two must have been damaged in shipping.

I'd like to be able to spot check them with a glance.

If it is a simple soldering job, could you provide instructions on how to DIY repair this issue??

2  Alternate cryptocurrencies / Mining (Altcoins) / Re: Official FutureBit Moonlander 2 Driver and Support Thread on: June 06, 2021, 01:34:24 AM
I am running (2) two Moonlander 2's with a R PI 3 and powered by an Anker 10 Port 60W, 12V / 5A.

They both run good for about 2 days, until one drops off, leaving a single unit correctly hashing.

I know this isn't the most industrial grade USB hub in the world - but I assumed it would be enough juice...

Wondering if it might be something with my software.

This is a copy of what I get when I "q" out. Am I doing something wrong? Running bfgminer5.4.2-34

-

./bfgminer --scrypt -o stratum+tcp://litecoinpool.org:3333 -u USERNAME -p 1 -S MLD:all --set MLD:clock=540

 [2021-06-05 21:27:14]
Summary of runtime statistics:

 [2021-06-05 21:27:14] Started at [2021-06-05 01:15:42]
 [2021-06-05 21:27:14] Pool: stratum+tcp://litecoinpool.org:3333
 [2021-06-05 21:27:14] Runtime: 20 hrs : 11 mins : 31 secs
 [2021-06-05 21:27:14] Average hashrate: 5.9 Megahash/s
 [2021-06-05 21:27:14] Solved blocks: 0
 [2021-06-05 21:27:14] Best share difficulty: 41
 [2021-06-05 21:27:14] Share submissions: 7737
 [2021-06-05 21:27:14] Accepted shares: 7711
 [2021-06-05 21:27:14] Rejected shares: 26 + 0 stale (0.00%)
 [2021-06-05 21:27:14] Accepted difficulty shares: 102
 [2021-06-05 21:27:14] Rejected difficulty shares: 0
 [2021-06-05 21:27:14] Hardware errors: 537
 [2021-06-05 21:27:14] Network transfer:  2.43 /  1.01 MB  ( 33.4 /  13.9  B/s)
 [2021-06-05 21:27:14] Efficiency (accepted shares * difficulty / 2 KB): 0.06
 [2021-06-05 21:27:14] Utility (accepted shares / min): 6.36/min

 [2021-06-05 21:27:14] Unable to get work from server occasions: 0
 [2021-06-05 21:27:14] Work items generated locally: 16175
 [2021-06-05 21:27:14] Submitting work remotely delay occasions: 0
 [2021-06-05 21:27:14] New blocks detected on network: 463

 [2021-06-05 21:27:14] Summary of per device statistics:

 [2021-06-05 21:27:14] MLD0        | 20s: 0.00 avg: 2.89 u: 2.93 Mh/s | A:3717 R:13+0(.36%) HW:53/.05%
 [2021-06-05 21:27:14] MLD1        | 20s: 3.04 avg: 3.03 u: 3.06 Mh/s | A:3994 R:13+0(.36%) HW:484/.45%
 [2021-06-05 21:27:14]  
Shutdown signal received.



(Thank you)
3  Alternate cryptocurrencies / Mining (Altcoins) / Re: Official FutureBit Moonlander 2 Driver and Support Thread on: March 11, 2021, 12:51:21 AM
Moriaville,

Install the following:

sudo apt install libncurses5 libncurses5-dev

 Wink

Yes! That did it! Thanks so much.
4  Alternate cryptocurrencies / Mining (Altcoins) / Re: Official FutureBit Moonlander 2 Driver and Support Thread on: March 09, 2021, 03:39:01 AM
Trying to get the ML2 up and running on a Raspberry Pi 3.

From a fresh OS install, I followed @Astrali instructions from the first page of this thread to the letter.

I get this error.

pi@raspberrypi:~/miner $ cd bfgminer_5.4.2-futurebit2_linux_armv6
pi@raspberrypi:~/miner/bfgminer_5.4.2-futurebit2_linux_armv6 $ sudo ./start_moonlander2.sh
./bfgminer: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
pi@raspberrypi:~/miner/bfgminer_5.4.2-futurebit2_linux_armv6 $

What am I doing wrong here?

Thanks in advance.
5  Bitcoin / Hardware / Re: GekkoScience NewPac / Terminus R606 (BM1387) Official Support Thread on: February 25, 2021, 05:13:49 PM
Yep, it's a driver thing. NewPacs require the winUSB driver and sometimes it's not possible to distinguish between the two devices in the OS.

So as long as VCPdriver is on the computer, even if the ML2 is no longer auto-scanning, there is no way to run both together on MacOS?
6  Bitcoin / Hardware / Re: GekkoScience NewPac / Terminus R606 (BM1387) Official Support Thread on: February 25, 2021, 02:36:58 AM
@sidehack

I'm on MacOS 10.15 and I know that Moonlanders and NewPacs don't play well together.

I did find an instance on the other support thread of a user that managed to get both working together on Ubuntu by pointing each to their specific USB bus : port.

I now have the ML2's set to their corresponding UART addresses. No longer are they set to 'ALL'.

Still, CGminer doesn't show the NewPacs after booting and entering the command to [L]ist all devices.

Does the VCP driver make this conceptually impossible? Even if I could direct the NewPacs to their correct --usb bus address : port address? And if I could, do you know the Terminal command that would show me that information?

I'm new to this world. Thanks for making such a cool product. And thanks in advance for your help.
7  Alternate cryptocurrencies / Mining (Altcoins) / Re: Official FutureBit Moonlander 2 Driver and Support Thread on: February 24, 2021, 03:18:13 AM
Ok new issue.   But this seems to be related to the cp210x.  In ubuntu 18.04 LTS linux distro, I have successfully got the moonlander mining Verge coin.  The problem I am having is when I connect a Gekkoscience newpac miner to the system.  I am not Linux tech savy enough to correct the issue.   What happens is that when moonlander is running it'll start erroring out with input/output errors.  I can't have both of them running at the same time.  Even with Moonlander connected to a USB2.0 port and running the newpac on a USB 3.0 port.

When I run the following command: dmesg | grep ttyUSB it appears the cp210x will disconnect from ttyusb0 (moonlander is on) and connect to ttyusb1 (gekko newpac is on) and alternate between the two causing bfgminer to fail on the moonlander.

Any ideas on how to keep it from alternating like this and have both running together?  I tested on my windows machine and both are able to work together without issue.  Ubuntu on the other hand no so.  When I ran the below command 'before' launching the mining software, it showed correctly moonlander device on usb0 and the gekko on usb1.  'After' running the miner, the below is what happens and I believe is the reason for the issue.  Soon I will be attaching an Arduino Uno for some electronic projects I am working on and believe this will possibly create issues with it as well.  Help is appreciated.  Just don't know how to correct.   Thanks



You need to figure out which tty each is attached too, and make sure you specify in bfgminer/cgminer to not auto-scan (ie use the -S /dev/ttyUSB0) flag.

My driver is pretty good at filtering out the right ASIC before injecting commands to the chip, but im pretty sure gekkosciences driver starts sending commands as soon as it finds a UART chip, which is why it screws up the moonlanders. Make sure auto-scan is not enabled will keep each driver from trying to send commands to the wrong usb miner.

Check out the first page, answers are in the FAQ section.
Is this possible to do on Terminal? What is the command to turn off auto-scan? I how do I discover the USB bus address?

I know you don't manufacture the device, but it seems that the VCP driver used with the MacOS ML2 install causes cgminer to not be able to detect the NewPacs. Do you think rerouting both devices to their specific corresponding USB address would avoid this error?

I'm new to this and have really been enjoying learning through this trouble shooting process. My next step is to crib from the Linux process described in the original response to your above post #1894.

ALSO, I ordered the BTC full node and 2 standard units to pair with it. I dig your ethos, man. Thanks.

Check out the FAQ section on the first page of this thread...answers are in there.

Kicking myself for not reading that all the way through...

I followed those instructions but I am struggling finding the bus and port number.

  | | +-o FutureBit Moonlander 2@14320000  <class AppleUSBDevice, id 0x100003821, registered, matched, active, busy 0 (2 ms), retain 13>
  | | |   {
  | | |     "sessionID" = 89647696327114
  | | |     "idProduct" = 60000
  | | |     "iManufacturer" = 1
  | | |     "bDeviceClass" = 0
  | | |     "bMaxPacketSize0" = 64
  | | |     "bcdDevice" = 256
  | | |     "iProduct" = 2
  | | |     "iSerialNumber" = 3
  | | |     "bNumConfigurations" = 1
  | | |     "Bus Power Available" = 250
  | | |     "USB Address" = 34
  | | |     "Built-In" = No
  | | |     "locationID" = 338821120
  | | |     "bDeviceSubClass" = 0
  | | |     "bcdUSB" = 512
  | | |     "USB Product Name" = "FutureBit Moonlander 2"
  | | |     "PortNum" = 2
  | | |     "non-removable" = "no"
  | | |     "kUSBSerialNumberString" = "7ca1b51a5bcee611bad3a7bc30f55f2b"
  | | |     "bDeviceProtocol" = 0
  | | |     "AppleUSBAlternateServiceRegistryID" = 4294981663
  | | |     "IOCFPlugInTypes" = {"9dc7b780-9ec0-11d4-a54f-000a27052861"="IOUSBHostFamily.kext/Contents/PlugIns/IOUSBLib.bundle"}
  | | |     "IOPowerManagement" = {"DevicePowerState"=0,"CurrentPowerState"=3,"CapabilityFlags"=65536,"MaxPowerState"=4,"DriverPowerState"=3}
  | | |     "Device Speed" = 1
  | | |     "USB Vendor Name" = "FutureBit"
  | | |     "idVendor" = 4292
  | | |     "kUSBCurrentConfiguration" = 1
  | | |     "IOGeneralInterest" = "IOCommand is not serializable"
  | | |     "kUSBProductString" = "FutureBit Moonlander 2"
  | | |     "USB Serial Number" = "7ca1b51a5bcee611bad3a7bc30f55f2b"
  | | |     "kUSBVendorString" = "FutureBit"
  | | |     "IOClassNameOverride" = "IOUSBDevice"
  | | |   }
  | | |   

I'm reading as 34:2 but when I add that value for X -

#!/bin/sh
cd -- "$(dirname "$0")"
cd bin
./bfgminer --scrypt -o stratum+tcp://us.litecoinpool.org:3333 -u moriaville.moonl0 -p 1 -S MLD:cu.SLAB_USBtoUART34:2 --set MLD:clock=700

The software says "NO DEVICES FOUND".

Thanks for your help.
8  Alternate cryptocurrencies / Mining (Altcoins) / Re: Official FutureBit Moonlander 2 Driver and Support Thread on: February 23, 2021, 01:59:04 AM
Ok new issue.   But this seems to be related to the cp210x.  In ubuntu 18.04 LTS linux distro, I have successfully got the moonlander mining Verge coin.  The problem I am having is when I connect a Gekkoscience newpac miner to the system.  I am not Linux tech savy enough to correct the issue.   What happens is that when moonlander is running it'll start erroring out with input/output errors.  I can't have both of them running at the same time.  Even with Moonlander connected to a USB2.0 port and running the newpac on a USB 3.0 port.

When I run the following command: dmesg | grep ttyUSB it appears the cp210x will disconnect from ttyusb0 (moonlander is on) and connect to ttyusb1 (gekko newpac is on) and alternate between the two causing bfgminer to fail on the moonlander.

Any ideas on how to keep it from alternating like this and have both running together?  I tested on my windows machine and both are able to work together without issue.  Ubuntu on the other hand no so.  When I ran the below command 'before' launching the mining software, it showed correctly moonlander device on usb0 and the gekko on usb1.  'After' running the miner, the below is what happens and I believe is the reason for the issue.  Soon I will be attaching an Arduino Uno for some electronic projects I am working on and believe this will possibly create issues with it as well.  Help is appreciated.  Just don't know how to correct.   Thanks



You need to figure out which tty each is attached too, and make sure you specify in bfgminer/cgminer to not auto-scan (ie use the -S /dev/ttyUSB0) flag.

My driver is pretty good at filtering out the right ASIC before injecting commands to the chip, but im pretty sure gekkosciences driver starts sending commands as soon as it finds a UART chip, which is why it screws up the moonlanders. Make sure auto-scan is not enabled will keep each driver from trying to send commands to the wrong usb miner.

Is this possible to do on Terminal? What is the command to turn off auto-scan? I how do I discover the USB bus address?

I know you don't manufacture the device, but it seems that the VCP driver used with the MacOS ML2 install causes cgminer to not be able to detect the NewPacs. Do you think rerouting both devices to their specific corresponding USB address would avoid this error?

I'm new to this and have really been enjoying learning through this trouble shooting process. My next step is to crib from the Linux process described in the original response to your above post #1894.

ALSO, I ordered the BTC full node and 2 standard units to pair with it. I dig your ethos, man. Thanks.
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!