 Show Posts
|
|
Pages: [1]
|
Auroracoin the craziest thing I've ever seen in cryptos and it's premined. I'm thinking some whales will be dumping soon.
It's really something to watch. $400M has flowed into AUR, it seems mainly at the expense of alts. It looks like Wolong has been exiting UNO. UNO seems to be in better shape than before the pump, though I feel for anyone who bought in high. UNO is now on many more exchanges, price is still higher than before the pump, many long timers in the community made out and should be able to buy back in for more UNO soon, the community grew, awareness increased, and we enjoyed a lot of attention. The scrutiny of the coin held up, even if the scrutiny of Wolong didn't. Anyone who is anyone in alts has now heard of UNO. I would love to hear a word from our Dev's, just to make sure they are still engaged on aboard with UNO. Well said, and echo the request from the Dev team to ensure we're still running steady. |
|
|
|
|
I think people are awaiting the "relaunch", until then, there's not a whole lot going on with the EAC community. It probably also needs more initiatives (like DOGE has done) to really promote it's value as the "green coin".
Lastly, there was a pump attempt a few weeks back. I'm sure there are a lot of people exiting from that.
I anticipate the coin stabilizing through March, and then looking towards the 200 satoshi range by May. Just my guess, but there are a ton of factors at play.
|
|
|
|
|
Can the removal of BTC from multipool.us be considered?
The switching speed of the pool doesn't coalesce well with the overall concept because of the overall low hashrate (compared to other pools), and the overall low amount of time that hashrate contributes to directly mining BTC.
The outcome of this is invariably 48h+ mining that achieves no return whatsoever, and a switch is made to an altcoin.
The only way a small(er) pool will be successful in mining BTC is with a dedicated and ongoing hashrate. This quite simply is not a realistic expectation from a profit-switching mining pool.
|
|
|
|
ah, the setting for bfgminer is actually
--set-device antminer:freq=0881
the default frequency is 0781 and you can try 0981
make sure you cool the device properly!
I can confirm this is now working, from the terminal. Still can't get it running from the GUI, though. Thanks either way! |
|
|
|
|
Great update! My antminer U1's are finally recognized as Ants in OSX under bfgminer for the first time and are running at full speed.
Is there a way to enable overclocking for the U1 devices? To do this I assume I need to run bfgminer from the Terminal, which I tried, however the "bmsc-freq XXXX" command is unrecognized.
Thanks again!
|
|
|
|
|
I was able to build a version of cgminer to get them working using Icarus drivers, but they do not run faster than 500MH/s. I'm waiting until they're officially supported, I suppose. I can't get anything else working.
|
|
|
|
Hi all; I've been following this thread for a few days, initially pointing my efforts to getting my U1's working under OSX.
Firstly, I'll state that I'm running a VM of Win7 on OSX because I can't get the AntGen1/AnMiner repo to make on OSX. Therefore, I'm having some trouble with 2x U1 sticks under Win7.
What I'm experiencing on Win7, now that I have all drivers installed, is a rollercoaster ride of hashing.
Inserting the first U1, it hashes up to the desired speed (1.6GH/s+), and then stabilizes. Inserting the second U1, it too hashes up to the desired speed, and then stabilizes. It's stable for approximately 20 seconds. Then, the hashrate plummets slowly (down to >100MH/s) for each device. Wait another 20 seconds, and both will bounce back to the desired speed. Additionally, my HW error rate is around 7-10%, with the vast majority of the errors appears in the "plummet" phase.
I can't figure out what the heck is going on; if anyone has any advice I'd love to hear it.
Hi I'm running on OSX but my setup will be quite different as I've a couple of aftermarket USB 3.0 cards in it: an old one I can't remember the name of and a CalDigit. I've tried running various miners off it. Got a similar sounding USB polling weirdness messing with me. To stamp on that I played with "USB Prober" in Developer/Applications/Utilities. (You need the developer tools installed) I went to USB logger and hit start. My USB polling problems went away. I've not bothered digging further than that as the last few bitcoin-qt's were discouraging so've given up on the OSX version for now and went the VM route for that part. USB logger also gives a nice log of what's plugging in and out. I too am running my miners of an externally powered USB hub, but what I'm most curious about is how you built the AntGen1/AntMiner cgminer repo on OSX. I've been hit with a dozen errors that I simply can't troubleshoot because a dozen more open up after each one I squash. Could you please provide some additional information on your cgminer make, setup, and run procedures for OSX? I would be very grateful. I just followed instructions from Nate Woolls and both cgminer and bfgminer built fine for me: http://blog.nwoolls.com/2013/04/24/bitcoin-mining-on-mac-os-x-cgminer-bfgminer/Interesting, I'll try that right now. Did you use ANY of the configuration options from the AntMiner/AntGen guide? I was under the impression was had to use their custom cgminer build to get it working. EDIT: I built per the instructions in the link, but now --bmsc-options are not recognized. Were you able to add this somehow? |
|
|
|
Hi all; I've been following this thread for a few days, initially pointing my efforts to getting my U1's working under OSX.
Firstly, I'll state that I'm running a VM of Win7 on OSX because I can't get the AntGen1/AnMiner repo to make on OSX. Therefore, I'm having some trouble with 2x U1 sticks under Win7.
What I'm experiencing on Win7, now that I have all drivers installed, is a rollercoaster ride of hashing.
Inserting the first U1, it hashes up to the desired speed (1.6GH/s+), and then stabilizes. Inserting the second U1, it too hashes up to the desired speed, and then stabilizes. It's stable for approximately 20 seconds. Then, the hashrate plummets slowly (down to >100MH/s) for each device. Wait another 20 seconds, and both will bounce back to the desired speed. Additionally, my HW error rate is around 7-10%, with the vast majority of the errors appears in the "plummet" phase.
I can't figure out what the heck is going on; if anyone has any advice I'd love to hear it.
Hi I'm running on OSX but my setup will be quite different as I've a couple of aftermarket USB 3.0 cards in it: an old one I can't remember the name of and a CalDigit. I've tried running various miners off it. Got a similar sounding USB polling weirdness messing with me. To stamp on that I played with "USB Prober" in Developer/Applications/Utilities. (You need the developer tools installed) I went to USB logger and hit start. My USB polling problems went away. I've not bothered digging further than that as the last few bitcoin-qt's were discouraging so've given up on the OSX version for now and went the VM route for that part. USB logger also gives a nice log of what's plugging in and out. I too am running my miners of an externally powered USB hub, but what I'm most curious about is how you built the AntGen1/AntMiner cgminer repo on OSX. I've been hit with a dozen errors that I simply can't troubleshoot because a dozen more open up after each one I squash. Could you please provide some additional information on your cgminer make, setup, and run procedures for OSX? I would be very grateful. |
|
|
|
|
Hi all; I've been following this thread for a few days, initially pointing my efforts to getting my U1's working under OSX.
Firstly, I'll state that I'm running a VM of Win7 on OSX because I can't get the AntGen1/AnMiner repo to make on OSX. Therefore, I'm having some trouble with 2x U1 sticks under Win7.
What I'm experiencing on Win7, now that I have all drivers installed, is a rollercoaster ride of hashing.
Inserting the first U1, it hashes up to the desired speed (1.6GH/s+), and then stabilizes. Inserting the second U1, it too hashes up to the desired speed, and then stabilizes. It's stable for approximately 20 seconds. Then, the hashrate plummets slowly (down to >100MH/s) for each device. Wait another 20 seconds, and both will bounce back to the desired speed. Additionally, my HW error rate is around 7-10%, with the vast majority of the errors appears in the "plummet" phase.
I can't figure out what the heck is going on; if anyone has any advice I'd love to hear it.
|
|
|
|
|
Thanks for the reply. I'll spin up a VM with VirtualBox and give Ubuntu a try in the short term.
Were there any specific missing libraries that I should prepare for?
|
|
|
|
|
I've got them too but can't get them running.
What Operating System are you on? I'd love any details.
|
|
|
|
|
Correct, it does not work.
Only the custom cgminer provided by the AntGen team works with the device (so I'm lead to believe).
|
|
|
|
|
Hi everyone!
1BtGbk5Ex5HSimAQrDXGHj3Vm4cDhTRrQc
|
|
|
|
Hi all - I need help building the custom cgminer to run the new Antminer U1 USB ASIC. I have attempted to pull from GitHub and build according to Unix instructions, but I'm getting a plethora of errors. Most notably, I can't even get ./autogen.sh finishing successfully. The most common error I receive is: checking dependency style of gcc... gcc3
./configure: line 4010: AC_PROG_LIBTOOL: command not found
./configure: line 4011: syntax error near unexpected token `Windows'
./configure: line 4011: `LT_LANG(Windows Resource)'
configure: error: ./configure failed for compat/libusb-1.0 Any help is appreciated. This is the link to the custom cgminer I'm trying to make -- https://github.com/AntMiner/AntGen1/tree/master/cgminer |
|
|
|
|
