Topic: Bitminter client (Windows/Linux/Mac) - page 13. (Read 654946 times)
Thread now pinned for being an actively maintained and used project.
WOW ... The fastest users table has a serious contender, sitting at no.1 at +27,700 Ghs (fefox) ... this user was always in the top 50, but WTF have they deployed now? Bitminter has jumped nearly 100Ths in under a couple of weeks. No.2 sits at 9,000+, lol
no kidding, what DOES he have? he is killing my score as a ~50GH/s wimpy miner.
PS The new release of the software works great. I can combine my Icarus and Ants again with no issues and it connects to the site with less flaws, as in zero. Thanks Doc!
WOW ... The fastest users table has a serious contender, sitting at no.1 at +27,700 Ghs (fefox) ... this user was always in the top 50, but WTF have they deployed now? Bitminter has jumped nearly 100Ths in under a couple of weeks. No.2 sits at 9,000+, lol
Bitminter client v1.5.0 beta3 is ready for testing.
I have found your software solid and easy to work with. Glad I found your site. Been processing SETI packets for over 15 years, this sounded like fun.
Thank you!
Had to force a browser refresh and then, perfect, all Antminers start properly and at their set 2Ghps speed.
So far it runs quite stable for me.
I'm running Ubuntu Studio 13. something...
So far it runs quite stable for me.
I'm running Ubuntu Studio 13. something...
Bitminter client v1.5.0 beta3 is ready for testing.
New:
Please check it out:
New:
- Bugfix: antminer would sometimes still be detected as icarus
- Bugfix: chili asic would run out of work after recovering from chili firmware problem
- Improved overclocking for antminer, enable entering 4-digit hex code directly
- Default to not setting a clock speed on new antminer devices (keep their current clock)
- Improved workaround for Java 6/7 bug that could cause security- or nullpointer-exception after the program had been running for a while
Please check it out:
I'm having a problem where the Bitminter beta is incorrectly identifying Antminers as Icarus devices.
New beta that fixes this is coming right up.
Cool beans!
I did manage to tinker enough with stopping the device, removing the port, removing and re-inserting the device, setting the port to R/W and probing it again.
It was a bit of work but all 9 are running at 2Ghps (or pretty close).
I'm having a problem where the Bitminter beta is incorrectly identifying Antminers as Icarus devices.
New beta that fixes this is coming right up.
I'm having a problem where the Bitminter beta is incorrectly identifying Antminers as Icarus devices.
It seems random, right now it's 2, 3, and 7, before it was 0 and 6.
I'm on Linux, so I unplugged the powered hub, removed all the ttyUSB devices, plugged it back in, and made sure to set all ttyUSB to R/W.
I was using Icarus devices before but now it's all Antminers.
Anything I can do to fix this?
Thanks,
-Sean
It seems random, right now it's 2, 3, and 7, before it was 0 and 6.
I'm on Linux, so I unplugged the powered hub, removed all the ttyUSB devices, plugged it back in, and made sure to set all ttyUSB to R/W.
I was using Icarus devices before but now it's all Antminers.
Anything I can do to fix this?
Thanks,
-Sean
Yes. You can overclock them. Try this link... http://www.designer2k2.at/mods/elektronik/85-block-erupter-overclocking.html
Unfortunately, after looking at the article, the effort and cost to get from 336 to 440 is not cost effective.
Sell three 336 and get a single Antminer U1 and double your speed.
Is there any way to overclock the ASIC block eruptors? Running at .336 mh/s is going to become useless, even with their low power consumption soon so I'd like to get everything out of them that I can while I can.
Yes. You can overclock them. Try this link... http://www.designer2k2.at/mods/elektronik/85-block-erupter-overclocking.html
BitMinter client v1.5.0beta2 is ready for testing.
New: Overclock support (click tune & tweak button) and identify button (click to flash LED) for Antminer U1
New: Overclock support (click tune & tweak button) and identify button (click to flash LED) for Antminer U1
Can you change the code so that it preserves the current overclock setting for 'new' Antminer U1 devices. When I have to unplug and re-plug the mining hardware the Silicon Labs driver on my MacBook Pro assigns all the Antminers and Block Erupters new device names. Version 1.5.0beta2 changes the 'new' Antminers to 1.6 GH/s.
Is there a way to fetch the current setting from each Antminer U1 and use that? It's a pain to have to re-set all five, especially since only one can run at 2.1 GH/s. Especially since I can't seem to get the "Identify" buttons to work (the red LEDs don't blink and the 'share found' green LEDs blink all the time).
The Tune & Tweak UI is very slow on my MacBook. It often takes several seconds to respond to a mouse click.
Hi,
I seem to be having a high number of miscalculations (6.5%).
Is there anything that can be done to try and reduce or investigate the problem?
I am running 2 x BFL 7 GHs Jalapeno's.
Thanks,
Phil
I seem to be having a high number of miscalculations (6.5%).
Is there anything that can be done to try and reduce or investigate the problem?
I am running 2 x BFL 7 GHs Jalapeno's.
Thanks,
Phil
Wasn't there a pencil mode for the BE's ??
Is there any way to overclock the ASIC block eruptors? Running at .336 mh/s is going to become useless, even with their low power consumption soon so I'd like to get everything out of them that I can while I can.
I don't know of any overclocking mechanism for those, sorry.
The Beta seems to be working wonderfully and I really like the tune and tweak feature. It makes it really easy to overclock and tinker with my AntMiners.
Is there any way to overclock the ASIC block eruptors? Running at .336 mh/s is going to become useless, even with their low power consumption soon so I'd like to get everything out of them that I can while I can.
Is there any way to overclock the ASIC block eruptors? Running at .336 mh/s is going to become useless, even with their low power consumption soon so I'd like to get everything out of them that I can while I can.
Fantastic job! I have 11 U1's @ 2.0GH/s and 1 @ 1.8 (there's always one) that are mining with no errors. The Icarus are mining normally as well and nothing has crashed yet. Thanks, I've been waiting for this.
BitMinter client v1.5.0beta2 is ready for testing.
New:
Please check it out:
Custom overclock support planned for next beta. For now there is a pre-defined list to choose from.
New:
- Overclock support (click tune & tweak button) and identify button (click to flash LED) for Antminer U1
- Rewritten Red/Blue Fury support - should work much better now
- Bugfix: Chili ASIC would fail on first try and you'd need to start the device twice
- Bugfix: Fixed a bug where scanning for devices could stop working until you restarted the client
Please check it out:
Custom overclock support planned for next beta. For now there is a pre-defined list to choose from.
Hey there,
Im totally new here and wanted to know what that proofs of work accepted by server means. And i'd also like to know how i get my bitcoins paid out from my workers... theres just this proofs of work accepted by server but the amount of bitcoins is never increasing!
I would be very happy if some1 could help me!
Thank you!!!
Im totally new here and wanted to know what that proofs of work accepted by server means. And i'd also like to know how i get my bitcoins paid out from my workers... theres just this proofs of work accepted by server but the amount of bitcoins is never increasing!
I would be very happy if some1 could help me!
Thank you!!!
did not see the [antminer] tuning setting.
So how did you do it??
In bfgminer I set the clock to --set-device antminer:clock=x0981So how did you do it??
the Antminer remembers the setting in the BitMinter client
Just installed bfgminer (on Mac OS X 10.9.2 using the Linux instructions) and successfully set the clock to 2.0 GH/s.
Code:
git clone https://github.com/luke-jr/bfgminer
cd bfgminer
./autogen.sh
./configure
make
make install
sudo ./bfgminer --scan antminer:all -o mint.bitminter.com:8332 -u USERNAME -p x --set-device antminer:clock=x0981
After it runs a few seconds you can type 'q' to quit bfgminer and re-start BitMinter with your AntMiner U1 devices set to 2.0 GH/s.
I was getting NO hardware errors at 2.0 GH/s so I tried 2.2 GH/s (clock=x0A81). That got a few hardware errors on four of my AntMiners but LOTS of errors on the fifth. I switched them all back to 2.0 GH/S. In theory you can use bfgminer to set them individually... maybe another time.
Jump to: