|
FYI Got back into doing some GPU tinkering, picked up the Saphire Vega 56 pulse...this is a neat little card. I have it at 47 MH stable on eth right now.
|
|
|
|
@jstefanop good one with the asicboost. I bet you fooled few users.
 |
|
|
|
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  |
|
|
|
For those that dont understand, this is an april fools joke.
Why do you have to ruin the fun so early...I was hoping I could be entertained for a little longer. |
|
|
|
|
haha looks like bitmain is finally starting to squirm a little after extracting billions from everyone. They are issuing coupons and dropping prices like crazy. Just got a bunch of $350 coupons this morning.
Hopefully they will be stuck with a shit ton of excess stock, and get screwed with 100's of millions in 7-10nm chips for bitcoin and 16nm for Litecoin that they wont be able to sell at the crazy prices they were hoping for this summer.
|
|
|
|
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  : /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. |
|
|
|
Thanks for sharing....pretty useful info....is it also availableon Amazon or only eBay?
What are you referring to? the Moonlanders or some hubs or what exactly? And if someone has experience in this: As the pool i usually mine to has been down due to an error whilst updating (this will take them a while  ) I'm trying to add a 2nd pool to my bat file. From what i gather from different topics here on bitcointalk, it should be as simple as adding the url, username and password for the 2nd pool and it should switch when necessary. But when i try to run it with that bat file nothing happens... Any suggestions? You can try to put "pause" at the end of bat file (this prevents closing the window and you should see some message what's wrong) Great tip! It says: "Unexpected extra commandline arguments" This is the text in my bat file: bfgminer.exe --scrypt -o stratum+tcp://pool.tittiecoin.com:3335 -u TEmAH67jzTRxFQP1cqZ64F4Bh5T1JsBpwo -p stratum+tcp://tittiecoin.p2p.0x0a.nl:28008 -u TEmAH67jzTRxFQP1cqZ64F4Bh5T1JsBpwo -p d=1024 -S MLD:all --set MLD:clock=900 pause Got it running with that now, but got a new error: No URI supplied for pool 1 From what i can find i need to set up a proxy to get past this?? 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. |
|
|
|
Is there any way Bitmain can 'change the firmware' to get around a fork of some of the coins like moreno threating such?
curious if they have any options with ASIC's as an X3 miner...
just watching from the sidelines but curious...
Forget it. No way. This wont happen. 100% At least not for "public"? Thats not how ASICs work...the "firmware" is etched into the silicon. Once the ASIC is made for a particular algorithm thats ALL it can do and there is no way to change it. The only exception to this is if bitmain started building their own FPGAs, which would be way slower than ASICs, but much more energy efficient than GPUs, and almost as flexible as GPUs in changing the algorithm. Of course like others have stated, there is no reason for them to offer a flexible FPGA style miner, when they can just pump out new ASICs for every new algorithm. They have become so good at it they can bring a new algorithm to silicon in a few months it seems. |
|
|
|
jstefanop,
I know this may not be the appropriate thread (not sure) but I am doing this in public so that if anyone else has questions as to the "authenticity" of these devices, they can reference this thread.
After 30 days of use, a buyer on eBay is attempting to get a return by claiming:
"Doesn't seem authentic"
"this is not the second batch of version 2"
I am asking if you can weigh in on the high res photos of the devices and explain a little for my own reference in case why these are indeed the latest ML2's that you put out.
I would appreciate you weighing in, please.
Yes those are Batch 2 units. Batch 1 had no silkscreen on the back, while batch 2 have the silkscreen with the FutureBit logo on it. |
|
|
|
Thanks! That board is your problem, it only provides 500ma per usb port. As you can see in my post above, the MLD's easily go over 2 amps! That is not the exact USB hub he is using. It is actually the newer blue Block Erupter 49 port with a 50 amp fuse. Here is a picture of that exact same board delivering 2.55 amps to an ML2 that was stock settings to determine amperage draw.  [.....] That there is the main issue with most of these hubs. They have HORRIBLE 5v regulation. As soon as you turn one Moonlander on you see voltage drop to 4.5 or lower. Most of the generic hubs you can't do much about, but at least these style high power hubs come with a 5v PSU that can be adjusted for the non faint of heart. You can open up the eyeboot style hubs and inside you'll find the PSU, that has some sort of pot/adjustment screw for output voltage. The moonlanders themselves can handle up to 5.25v on the input, so lets say the hub is dropping from 5v to 4.5v when you start it up, you could set it to 5.25-5.5 on startup, so it drops to around 5v. A .5v increase will reduce current draw by 10% (so you can run existing sticks 10% faster, or add 10% more sticks per hub). If you do this make sure you don't keep the stick idle for too long, as anything above 5.25v could damage the UART chip. |
|
|
|
I just noticed that the L1 memory probe point is half-cranked at my Moonlanders.
First i thought it might be specific to the bitshopper.de -batch, but i do not see any pictures online with Memory-probepoints looking like my one.
Does anyone else have the same on his moonlanders ? Should this be an issue ? The MLDs worked fine so far so i never suspected anything.
Haven't cranked up the clockspeed, yet.
Thats fine, unfortunately the inductors used in Batch 1 were more prone to have the inductor casing crack from thermal stress during reflow. This is purely cosmetic though and has no effect on performance (as you can see inside it an inductor is just a wound up copper coil, as long as that coil is not damaged its fine). |
|
|
|
Speaking of non support related activity, I wanted to post this for a while and this reminded me. So theoretically speaking with all the moonlander 2 hashing out there now, there should have been several blocks found by Moonlander 2s...and I'm sure one or two of those blocks are from solo people. Definitely post up and let us know if you hit the jackpot and got 25 LTC out of a single moonlander 2. That would be a cool story! |
|
|
|
BTW; @jstefanop:
What i'd love to see in BFGminer / the MLD's if possible; a way to identify them. BFG sets them up as MLD 0, MLD 1, MLD 2.... etc. But there's no way of telling (as far as i am aware of) to figure out which stick is MLD 0 or MLD 1 etc. Troubleshooting can be made so much simpler with unique ID's. After a reboot, the ID's get swapped now so MLD 0 could then be MLD 2 etc. I know that my gridseed dual miners had unique ID's, so if you plugged them in 1 at a time, you could make a note of which ID that miner had and if there ever was a problem you knew exactly which miner to fix.
Moonlanders have UIDs as well. Just press "M" while its running, then select the device number you want, and it will show its ID under serial number. You can then match the last couple digits to the actual serial number sticker on each device. Next update will also have enable/disable functions implemented, so that will be another way to quickly check which is which since toggling enable/disable will cause the LEDs to flash. |
|
|
|
|
I wish I could understand bitmain logic...
"Hey lets make a siacoin miner that will make $50 day profit after everyone plugs them in and charge 2,500 for them"
...2 months later
"Hey lets make a Monero miner that will possibly make $50 a day after everyone plugs them in IF they don't fork and charge 12,000 for them"
|
|
|
|
Checking in, I just leave them alone and let them do their thing. Still rock solid on the 4 Anker hubs.   Great stability. How high you got in freq and Vcore? And temps? He's running max frequency at that hashrate. Good to know that my design can handle max frequency for so long without blowing up |
|
|
|
|
Looking to pick up a A4+ miner. I can take full miner, boards, dead boards, bad performing miner etc. I just need it for dissecting/parts.
|
|
|
|
Is there any limit to how many can be run off a Pi3b with a powered hub?
Not really, just whatever system limit for USB devices is, which is probably around 255. Im sure the pi would start choking way before then. |
|
|
|
After receiving a better powered hub today i've started tuning the 3 moonlanders which i currently have. They are all running stable at 832 clock speed. I've copied the setting for core voltage and memory so all 3 are set in the same way. HW error rates are at 0.38, 0.06 and 0.94% so thats nice and they are hashing along at ~4.70mh/s each. Quite happy with that figure. One 'issue' though, 2 of the MLD's reach a temperature of about 51-54 degrees celsius. The third goes up to 72-75 degrees celsius. I've already ordered some external fans so that should bring it down a couple of degrees but other than that, any suggestion as to why 1 of them is running so hot? Thanks for any ideas Check the back heatsink, it could have not been applied correctly. Just put some pressure on it and make sure its stuck on there well. |
|
|
|
|
Show Posts
