I see people running these sticks with Rpi s with powered hubs so I wonder... Is this software going to run on armv7 device running kernel 2.6.x. Any maemo freaks here...? That woud be fun...
RPi executable is compiled for armv6 which runs on both amrv6 and armv7 devices. Not sure about really old kernels...that might not even have the UART driver in the kernel, so you would at the very least need to compile the UART driver and load the kernel extension.
|
|
|
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.
|
|
|
Well got an email from Bitmart today regarding my moonlander-2 order. after 2 months waiting, they tell me to send an extra $60 for shipping. wtf. are those guy's a scam or what ? didn't you checked your resellers, or what ? Sounds like you don't live in South Africa? He's my south african distributor and has been vetted. Don't expect shipping to be cheap if you don't live there.
|
|
|
Hi OP!
How can i pre order here in the Philippines? I really want to buy some. I hope that i can get some amazing Future USB's. I need some badly. THANKS
check out links above, order from eyeboot for your region.
|
|
|
Im working on a fix to keep the alive automatically. The current dead/restart logic is bugged in bfgminer, so I'm going to implement it directly in the driver. Should have a new release out in the next few days.
Awesome! I'm having this same problem and I'm looking forward to the update! Again, you're an incredibly awesome person! Agreed, thanks for making these sticks! Really looking forward to the update as well, it'd be great if they could restart on their own. Assuming ample power (I'm only running two of them off the Plugable hub), what are the optimal settings for the frequency and core voltage? On the stock settings I'm getting between 3-3.5 MH/s each stick. 756 is what I have found to be the optimal balance between hashrate and power on these chips. 756 runs fine at about .7v, so you can turn core voltage down a bit, and turn down memory voltage as low as your ASIC can handle (~.75-. for best power draw. Check out my tuning guide in OP on how to fine tune these using --benchmark flag. Sounds like just changing the frequency to 756 in the code should be probably work without messing with the hardware screws? I'd rather just start with that. Yes just change the "600" to 756 in the start_moonlander file.
|
|
|
Looking forward to buying in for a few on the next batch!
OP has been updated for batch 2 sales starting tomorrow: Batch 2 Pre-order will start December 6th at 12 PM EST. This batch is larger and more distributors have been added so anyone that didn't have a chance to pick up a pre-order last batch should be fine this time around. bittawm has also been added as an Australian and New Zealand Distributor, and will be participating in the Batch 2 Pre-order. He has excellent seller reputation in that region, and has setup his site for the pre-order below (ill post his link before sales go live tomorrow, don't mind his "basic" site he threw this together quick to be able to process the pre-orders quickly). https://bittawmart.com
|
|
|
Long time lurker, but felt like I finally needed an account.
jstefanop, you're absolutely awesome! I pre-ordered a single kit back way back when from AsicPuppy.
I got it on Saturday (I didn't get a shipment notification, but when I emailed AsicPuppy, they sent me a tracking code. But it was already delivered! Fine by me!) and have it hashing away right now using a Raspbery Pi 2 connected to the Pluggable 2.0 USB hub that was recommended in the Hub thread.
I'm pointing it at multipool.us because I want to collect all the different coins they mine (I may look into even smaller scrypt coins just for fun!). I know I will probably never make back the money, but I've spent far more money on hobbies I ended up not liking.
jstefanop, your dedication and support to this product is amazing. I hope you don't get discouraged from a small minority of people complaining. They probably never designed, built, tested and shipped a complete electronic device before. So what do they know?
I'm looking forward to the next batch! Maybe I'll buy 2 more to fill up the USB hub!
Thanks for this post, means alot!
|
|
|
Im working on a fix to keep the alive automatically. The current dead/restart logic is bugged in bfgminer, so I'm going to implement it directly in the driver. Should have a new release out in the next few days.
Awesome! I'm having this same problem and I'm looking forward to the update! Again, you're an incredibly awesome person! Agreed, thanks for making these sticks! Really looking forward to the update as well, it'd be great if they could restart on their own. Assuming ample power (I'm only running two of them off the Plugable hub), what are the optimal settings for the frequency and core voltage? On the stock settings I'm getting between 3-3.5 MH/s each stick. 756 is what I have found to be the optimal balance between hashrate and power on these chips. 756 runs fine at about .7v, so you can turn core voltage down a bit, and turn down memory voltage as low as your ASIC can handle (~.75-. for best power draw. Check out my tuning guide in OP on how to fine tune these using --benchmark flag.
|
|
|
I've received my four and they seem to be working ok, but they are dying occasionally. Like this morning two of three I have plugged into one comp were just not hashing, but had been working for the whole day while I was awake yesterday. When I restart bfgminer they're working fine though. Is this related to using higher frequency? Higher frequency without tuning voltage? Computer not splitting enough current? Something else?
Did you change from stock setting? You get zombie state if USB port can't provide enough amperage. On multiple devices, if one device acts up, that can't affect the other ones. Single stock is most stable but multi stock you should expect them to zombie hopefully later than sooner. I did increase clock frequency to 700-something. Two are plugged directly into mobo and one in USB on front side of comp. I'll try to go back to stick and see if they can work uninterrupted for couple days at least. This is on Windows 7 computer. Im working on a fix to keep the alive automatically. The current dead/restart logic is bugged in bfgminer, so I'm going to implement it directly in the driver. Should have a new release out in the next few days.
|
|
|
Is this because I installed legacy VCP Driver?
sunk818@SMBP.local:~/Downloads/bfg-futurebit2$ ./start-moonlander-2 dyld: lazy symbol binding failed: Symbol not found: _clock_gettime Referenced from: /Users/sunk818/Downloads/bfg-futurebit2/bin/./bfgminer Expected in: /usr/lib/libSystem.B.dylib
dyld: Symbol not found: _clock_gettime Referenced from: /Users/sunk818/Downloads/bfg-futurebit2/bin/./bfgminer Expected in: /usr/lib/libSystem.B.dylib
./start-moonlander-2: line 4: 31854 Trace/BPT trap: 5 ./bfgminer --scrypt -o stratum+tcp://us.litecoinpool.org:3333 -u jstefanop.1 -p 1 -S MLD:all --set MLD:clock=600 sunk818@SMBP.local:~/Downloads/bfg-futurebit2$
Your on Mac OS 10.11 or lower. Mac OS 10.12 works out of the box, and 10.13 works with the workaround posted in the OP. Apple has been changing shit in their system libraries like crazy lately and can't support anything other than the latest OSes. If you compile natively on that system it will work, but compiling bfgminer for Mac is a bitch. Way easier to just upgrade to 10.12. If you know your way around brew, you can use my brew tap here to help with Mac OS compiling: https://github.com/jstefanop/homebrew-xgminer
|
|
|
The hub has enough power - the issue with USB extenders is that they're not powered, so its possible they can't pull the power needed. (It's like using an unpowered PCIe riser on a GPU rig.) Most USB extenders are powered. I just use all the extra USB 3 cables I have from my USB GPU risers and they work great.
|
|
|
When will pre order batch 2 start? Or can I somewhere buy that Miner all are out of stock.
I will make an announcement for batch 2 before they go on sale. Probably sometime next week. also for bitshopper? should have bought 3 more instead of just 2 but hey.. can an European customer buy from asicpuppy and receive the assembled moonlander 2? Yes all of them...they will all have plenty of batch 2 stock, and most regions of the world are covered (NA, Europe, Asia, and Aus/NZ). You should be only be ordering from the region closest to you.
|
|
|
Why are these needing to be built by HolyScott before shipping?
HolyScott-
I was not expecting labor to have to build and put them all together
All distributors knew ahead of time they would be getting parts, and it was up to them if they wanted to ship them out in "kit" form or fully assembled. They were under no obligated to assembled them, since pre-order price was cheap and end customers should be fine with the 5 minutes it would take to assemble these. If i was going to assemble every order you guys would be waiting for your sticks for another month (or would have cost at least and extra $10 per stick to have a team of assemblers). Scott's and awesome guy and he assembled them all for you. As a sidenote im a little discouraged by all the negative comments directed at my US distributors for "late" shipments. I never promised anything other than up to Mid Nov for shipments to my distributors, which is when shipments did start. All shipments were done within a 2 week time frame in the middle of our thanksgiving holiday here, and all of you guys have your pre-orders in hand or in carrier hands right now. (not to mention that I personally know most the you guys complaining are reselling these at 2x markup).
|
|
|
Folks buying hash from Nicehash - I've had occasional peaks above 10,000 back when it was profitable to do that.
Folks with mid-sized farms (as mentioned, that's only 24 or so L3+).
They may be using LiteCoinPool as a backup "rollover" pool from NiceHash - given how often *my* miners end up giving me short "spikes" on litecoinpool, I'd bet on that being the real explanation.
Yea looks like someone is trying to mine alot of LTC using nicehash.
|
|
|
Wait, I think we're rolling. https://imgur.com/a/cPjjbMight take a minute for my pool to update I guess? Any feedback is greatly appreciated. Looks good, what did you change from before? Your hardware errors were way to high on the last screenshoot.
|
|
|
Nicehash works fine, you need to use the following URL for it to work.
stratum+tcp://scrypt.usa.nicehash.com:3333/#skipcbcheck#xnsub
i.e. add "#skipcbcheck#xnsub" at the end of the URL.
Keep in mind Nicehash's default diff seems to be 256k...this will take hours before you submit a share, and unfortunately most pools are setup to adjust vardiff AFTER the first share. Ill try and contact them to see what can be done.
|
|
|
You know I designed this with a fan built in so you don't have to come up with clumsy external fan solutions like that The built in fan can handle up to 800-900mhz no issues, your running at stock 600
|
|
|
|