 Show Posts
|
|
Pages: [1]
|
|
Does anyone have problems where a USB attached mouse just fails to work after awhile? Sometimes I'll come back to the Apollo after it's been running a few days, and while I can move the mouse, I can't actually click on anything. I have to unplug the USB mouse, plug it back in, and then I can interact with items on screen again.
|
|
|
|
DoofyWops, I’m running mine on nicehash on the normal sha256 server. Not the asisboost one.
Also i get the updates window for the OS. Dont update it otherwise you will have to reflash the SD card.
Thanks a bunch!!! Can I ask what rate you're getting? I'm getting 0.88 TH/s |
|
|
|
I have a few questions: Occasionally I get a popup asking me to update things on the Apollo. I usually dismiss it because I'm unsure if this is the system update or the OTA updates. Can someone please clarify this for me? Do the OTA updates automatically happen, or do I get prompted? Another thing was my Apollo basically locked up when this popup came up after leaving it up for a few days (I was gone over a weekend). I could move the mouse around, but was unable to dismiss the modal or get FireFox to resume focus. The miner was still going though. I had to power it down manually and bring it back up again so I could interact with it. Another question, has anyone hooked this up to Nice Hash successfully? I'm wondering what algorithm I should be using when referencing this page: https://www.nicehash.com/asic-miningAnd I just want to say thanks again to jstefanop! I have 3 LTC moonlanders that I was tinkering with years ago and I'm stoked to finally have this upgrade! I really appreciate all the work you've done over the years and I want to congratulate you on building a successful business around it. Good job! |
|
|
|
|
I flashed my microSD card with the latest update, so I'm running Apollo v0.3.1. I've decided to try the lottery and use ckpool. When I check the pool stats for ckpool, I can see my hash rate reporting at like 1.78T, but my problem is that the dashboard on the Apollo says otherwise. All indicators to the pool say 'inactive', and says I'm hashing at rate of 0.0. I've tried, stopping, starting, restarting a few times, but all mining dashboard representations look like nothing is happening even though the pool is reporting otherwise. Any suggestions? The node dashboard looks OK and looks to be displaying accurate information.
|
|
|
|
|
Interested!
Laptop:
Model Name: MacBook Pro
Processor Name: Intel Core i7
Processor Speed: 2.7 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 8 MB
Memory: 16 GB
OS: 10.13.2 (High Sierra)
VIDEO
Chipset Model: Intel HD Graphics 530
Type: GPU
Bus: Built-In
VRAM (Dynamic, Max): 1536 MB
Vendor: Intel
Device ID: 0x191b
Revision ID: 0x0006
Automatic Graphics Switching: Supported
gMux Version: 4.0.29 [3.2.8]
Metal: Supported, feature set macOS GPUFamily1 v3
VIDEO
Chipset Model: AMD Radeon Pro 455
Type: GPU
Bus: PCIe
PCIe Lane Width: x8
VRAM (Total): 2 GB
Vendor: AMD (0x1002)
Device ID: 0x67ef
Revision ID: 0x00c7
ROM Revision: 113-C980AF-908
VBIOS Version: 113-C9801AP-028
EFI Driver Version: 01.00.908
Automatic Graphics Switching: Supported
gMux Version: 4.0.29 [3.2.8]
Metal: Supported, feature set macOS GPUFamily1 v3
Phone:
Google Pixel 2
CPU: Qualcomm® Snapdragon™ 835 2.35Ghz + 1.9Ghz, 64Bit Octa-Core
MEM: 4GB LPDDR4x RAM
OS: Android 8.1.0
|
|
|
|
Ok, I'm not sure what the issue is here. I'm running 2 MLD's on my RPi2. It's been running fine for the last 3 days with no issues. Today I got a voltage meter that I plugged my USB hub into to measure the overall energy consumption of the MLDs over time.
I stopped currently running BFGMiner, then shut down the pi. Plugged the hub into the meter, and turned the pi back on with the hub and MLDs connected to it, but I can't get BFGMiner to find the MLD's anymore.
...
The lights on both MLD's are solid green.
Any thoughts on how to troubleshoot, or if I'm missing something? I've restarted the pi numerous times with the MLDs plugged in and out trying to get them to showup in bfgminer to no avail.
Some Googling turned up this: https://askubuntu.com/questions/234691/cannot-mount-see-access-usb-device-ttyusb0Basically it looks like everything is setup, but cannot communicate on the ttyUSB0 and ttyUSB1 'ports'. I did the following with both MLDs connected and then logged out and back in: sudo usermod -G dialout -a username If anyone can explain what would cause this to suddenly stop working, I'd love to hear it. For the moment, I'm back up and running again! =) Anxiously awaiting my 3rd in Jan.... |
|
|
|
Ok, I'm not sure what the issue is here. I'm running 2 MLD's on my RPi2. It's been running fine for the last 3 days with no issues. Today I got a voltage meter that I plugged my USB hub into to measure the overall energy consumption of the MLDs over time. I stopped currently running BFGMiner, then shut down the pi. Plugged the hub into the meter, and turned the pi back on with the hub and MLDs connected to it, but I can't get BFGMiner to find the MLD's anymore. The result of is below /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/5p, 480M
|__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=smsc95xx, 480M
|__ Port 2: Dev 7, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 1: Dev 8, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 2: Dev 11, If 0, Class=Vendor Specific Class, Driver=cp210x, 12M
|__ Port 4: Dev 9, If 0, Class=Vendor Specific Class, Driver=cp210x, 12M
|__ Port 4: Dev 5, If 0, Class=Vendor Specific Class, Driver=rt2800usb, 480M
also lists the following: T: Bus=01 Lev=04 Prnt=08 Port=01 Cnt=01 Dev#= 11 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=10c4 ProdID=ea60 Rev=01.00
S: Manufacturer=FutureBit
S: Product=FutureBit Moonlander 2
S: SerialNumber=xXx
C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=cp210x
T: Bus=01 Lev=04 Prnt=08 Port=03 Cnt=02 Dev#= 9 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=10c4 ProdID=ea60 Rev=01.00
S: Manufacturer=FutureBit
S: Product=FutureBit Moonlander 2
S: SerialNumber=xXx
C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=cp210x
So it looks like it's there and running. My current start_moonlander2.sh script looks like: ./bfgminer --scrypt -o stratum+tcp://us.litecoinpool.org:3333 -u MyName.3 -p myPass -S MLD:all --set MLD:clock=600 The lights on both MLD's are solid green. Any thoughts on how to troubleshoot, or if I'm missing something? I've restarted the pi numerous times with the MLDs plugged in and out trying to get them to showup in bfgminer to no avail. |
|
|
|
I'm having an issue getting my Moonlander 2 to be recognized in bfgminer on my Macbook Pro OSX High Sierra 10.13.1. The Moonlander 2 is recognized in the System Information, but I can't get it to come up in bfgminer using 'auto' or 'all' as a target for the device to add. I'm not really sure what a valid serial port would be. Any suggestions would be great! Edit: My USB Hub is connected to a monitor, which is then connected via USB-C to my Macbook Pro. So there is some level of indirection to get to the actual USB devices. But my mouse & keyboard work fine so there's that =P Here's the output from 'ioreg -p IOUSB -w0 -l' | +-o FutureBit Moonlander 2@14521200 <class AppleUSBDevice, id 0x1000246fc, registered, matched, active, busy 0 (23 ms), retain 17>
| | {
| | "sessionID" = 15263740325007
| | "iManufacturer" = 1
| | "bNumConfigurations" = 1
| | "idProduct" = 60000
| | "bcdDevice" = 256
| | "Bus Power Available" = 250
| | "USB Address" = 14
| | "bMaxPacketSize0" = 64
| | "iProduct" = 2
| | "iSerialNumber" = 3
| | "bDeviceClass" = 0
| | "Built-In" = No
| | "locationID" = 340922880
| | "bDeviceSubClass" = 0
| | "bcdUSB" = 512
| | "USB Product Name" = "FutureBit Moonlander 2"
| | "PortNum" = 2
| | "non-removable" = "no"
| | "IOCFPlugInTypes" = {"9dc7b780-9ec0-11d4-a54f-000a27052861"="IOUSBFamily.kext/Contents/PlugIns/IOUSBLib.bundle"}
| | "bDeviceProtocol" = 0
| | "IOUserClientClass" = "IOUSBDeviceUserClientV2"
| | "IOPowerManagement" = {"DevicePowerState"=0,"CurrentPowerState"=3,"CapabilityFlags"=65536,"MaxPowerState"=4,"DriverPowerState"=3}
| | "kUSBCurrentConfiguration" = 1
| | "Device Speed" = 1
| | "USB Vendor Name" = "FutureBit"
| | "idVendor" = 4292
| | "IOGeneralInterest" = "IOCommand is not serializable"
| | "USB Serial Number" = "<removed>"
| | "IOClassNameOverride" = "IOUSBDevice"
| | }
Sigh...did you read any part of my post or FAQ before posting this? Q: My Moonlander 2 is not working with Mac OS 10.13
New security features in Mac OS 10.13 prevent the sililabs UART driver from loading. Until they provide a fix, please use the following workaround:
The workaround is to disable the SIP, installed the driver then enable the SIP.
-Shut down the Mac, start with Cmd-R depressed to boot to the Recovery Partition that will display the System Utilities.
-Open the Terminal and issue the command csrutil status and you will see SIP is enabled. To disable the SIP issue the command csrutil disable and then restart the Mac.
-You can then download and install the latest driver from Silicon Labs, you have the new USB to UART driver installed, and should work with the moonlander now
-Shut down and boot to the System Utilities and issue the command csrutil enable and restart.
-The csrutil disable and csrtil enable can only be issued from the Terminal while booted to Recovery Partition. Yes, this is a PITA but it works. No need to sigh. I 100% did all of those steps. In fact, I did this twice. I did the 2nd installation after running the uninstall.sh script for the driver library (which produces no output when run BTW). |
|
|
|
I'm having an issue getting my Moonlander 2 to be recognized in bfgminer on my Macbook Pro OSX High Sierra 10.13.1. The Moonlander 2 is recognized in the System Information, but I can't get it to come up in bfgminer using 'auto' or 'all' as a target for the device to add. I'm not really sure what a valid serial port would be. Any suggestions would be great! Edit: My USB Hub is connected to a monitor, which is then connected via USB-C to my Macbook Pro. So there is some level of indirection to get to the actual USB devices. But my mouse & keyboard work fine so there's that =P Here's the output from 'ioreg -p IOUSB -w0 -l' | +-o FutureBit Moonlander 2@14521200 <class AppleUSBDevice, id 0x1000246fc, registered, matched, active, busy 0 (23 ms), retain 17>
| | {
| | "sessionID" = 15263740325007
| | "iManufacturer" = 1
| | "bNumConfigurations" = 1
| | "idProduct" = 60000
| | "bcdDevice" = 256
| | "Bus Power Available" = 250
| | "USB Address" = 14
| | "bMaxPacketSize0" = 64
| | "iProduct" = 2
| | "iSerialNumber" = 3
| | "bDeviceClass" = 0
| | "Built-In" = No
| | "locationID" = 340922880
| | "bDeviceSubClass" = 0
| | "bcdUSB" = 512
| | "USB Product Name" = "FutureBit Moonlander 2"
| | "PortNum" = 2
| | "non-removable" = "no"
| | "IOCFPlugInTypes" = {"9dc7b780-9ec0-11d4-a54f-000a27052861"="IOUSBFamily.kext/Contents/PlugIns/IOUSBLib.bundle"}
| | "bDeviceProtocol" = 0
| | "IOUserClientClass" = "IOUSBDeviceUserClientV2"
| | "IOPowerManagement" = {"DevicePowerState"=0,"CurrentPowerState"=3,"CapabilityFlags"=65536,"MaxPowerState"=4,"DriverPowerState"=3}
| | "kUSBCurrentConfiguration" = 1
| | "Device Speed" = 1
| | "USB Vendor Name" = "FutureBit"
| | "idVendor" = 4292
| | "IOGeneralInterest" = "IOCommand is not serializable"
| | "USB Serial Number" = "<removed>"
| | "IOClassNameOverride" = "IOUSBDevice"
| | }
|
|
|
|
|
