Is the BitMinter client only suitable for use with the BitMinter pool or can it be used with other pools?
It works only on the BitMinter pool at the moment. Support for backup pools most likely coming in the next version.
Topic: Bitminter client (Windows/Linux/Mac) - page 38. (Read 654653 times)
It works only on the BitMinter pool at the moment. Support for backup pools most likely coming in the next version.
Is the BitMinter client only suitable for use with the BitMinter pool or can it be used with other pools?
BitMinter client version 1.3.0 is out. Thanks to everyone who helped test the beta releases!
Changes from 1.2.0 to 1.3.0:
Try it out:
If you have issues with 1.3.0 then you can still get the previous release (1.2.0) at http://bitminter.com/client/1.2.0/bitminter.jnlp
I'd be interested in hearing from anyone mining on Raspberry Pi, or with OpenBSD or FreeBSD operating systems.
Changes from 1.2.0 to 1.3.0:
- Support Icarus FPGA devices
- Fix "class not found" bug on Raspberry Pi
- Detect CPU model on Raspberry Pi, and hopefully other ARM systems.
- Implemented getwork extension: midstate (calculate midstate on client instead of server, reducing server load)
- Implemented getwork extension: rollntime, with "expire" support (get more than 1 work unit in a single request to the server)
- Dynamic work queue size
- Expire proof of work if undeliverable for 15 minutes
- Expire (non-rollntime) work unit if unprocessed for 5 minutes
- Count X accepted/rejected when the work difficulty was X (X is rounded down)
- Bugfix: don't count as device miscalculation when a proof of work exceeds difficulty 1 but not the (above 1) difficulty given by the server
- Only scan USB ttys on Linux - prevents many error messages about ttySxx.
- Bugfix on Linux: devices detected by a full probe and devices added through probing a specified port were named differently and it was possible to add the same device twice.
- Sort devices (by name) when dynamically adding external devices to device display.
- Default to compact display for anything but the bottom "total" display.
- Do not start CPU when clicking "total" display's start button for the first time after starting the program, unless it is the only device. Would previously start all visible (non-hidden) devices.
- Added X-Mining-Hashrate HTTP header to report hash rate to server.
- Staggered start of devices when multiple devices are started with the button on the status line or the "total" display's start button. Should give a smoother start up of (multiple) BFL minirigs.
- When going to performance mode remember the old window size and restore it when going back to detailed mode.
- Re-enabled comm port interval scanning (FPGA section of config) Can be used to automatically pick up FPGAs when plugged in
- Fixed bug that could cause "probe all ports" to stop working and report "no serial ports found"
- Changed regular poll interval to 20 ms (was 10) for BFL default config. Saves 5-10% CPU usage on testsystem with 2 BFL minirigs, no performance loss
- Changed hammering poll interval to 5 ms (was 1) for BFL default config. Saves 10-15% CPU usage on testsystem with 2 BFL minirigs, < 0.1% perf. loss
- Hopefully works on OpenBSD and FreeBSD as well now. FPGA only, untested.
- Recognize more AMD E-series CPUs
Try it out:
If you have issues with 1.3.0 then you can still get the previous release (1.2.0) at http://bitminter.com/client/1.2.0/bitminter.jnlp
I'd be interested in hearing from anyone mining on Raspberry Pi, or with OpenBSD or FreeBSD operating systems.
Quote
"Connection failed: Invalid argument: getsockname"
What to do? What to do?
Windows 8 has some network behavior that Java doesn't handle well. You can try upgrading Java to the latest version. I believe it was fixed in the latest Java 6 version, hopefully also in Java 7.
Also, even with the bug you can run an old version of bitminter client which has some older (non-async) networking code, as posted earlier in this thread:
Quote
Windows 8 note:
Version 1.2.0 will not run on current Windows 8 beta versions with current Java releases because of a problem with asynchronous I/O running Java on Windows 8. Until this is fixed in either Java or Windows, if you want to run the miner on Windows 8 you will have to use the previous release:
http://bitminter.com/client/1.1.2/bitminter.jnlp
Version 1.2.0 will not run on current Windows 8 beta versions with current Java releases because of a problem with asynchronous I/O running Java on Windows 8. Until this is fixed in either Java or Windows, if you want to run the miner on Windows 8 you will have to use the previous release:
http://bitminter.com/client/1.1.2/bitminter.jnlp
Of course 1.1.2 is lacking a lot of the goodies that are present in later versions. So it's probably worth a shot upgrading Java.
Quote
"Connection failed: Invalid argument: getsockname"
What to do? What to do?
Is it possible to use BitMinter Client ( BFL Single ) and BTCminer ( ZTEX boards) at the same time on one pc?
And both are mining in the BitMinter pool at the same time?
And both are mining in the BitMinter pool at the same time?
Sure, that's not a problem.
Is it possible to use BitMinter Client ( BFL Single ) and BTCminer ( ZTEX boards) at the same time on one pc?
And both are mining in the BitMinter pool at the same time?
And both are mining in the BitMinter pool at the same time?
Sweet
Will you have ASIC support upon release (are you working with BFL at all)
Yes. I am in touch with BFL about that and my goal is to have a miner version out that supports it before you get your ASIC.
Now I want to use additional a few ZTEX USB-FPGA 1.15y Boards.
Will they work with the new BitMinter 1.3 ?
Will they work with the new BitMinter 1.3 ?
Sorry, there's no ZTEX support. I may add that in the future, it depends on time and priorities...
Will you have ASIC support upon release (are you working with BFL at all)
Now I want to use additional a few ZTEX USB-FPGA 1.15y Boards.
Will they work with the new BitMinter 1.3 ?
Will they work with the new BitMinter 1.3 ?
Sorry, there's no ZTEX support. I may add that in the future, it depends on time and priorities...
I have got a BFL Single a few days ago.
It works very good with you BitMinter 1.2.0.
Now I want to use additional a few ZTEX USB-FPGA 1.15y Boards.
Will they work with the new BitMinter 1.3 ?
It works very good with you BitMinter 1.2.0.
Now I want to use additional a few ZTEX USB-FPGA 1.15y Boards.
Will they work with the new BitMinter 1.3 ?
th for the reply. i thought it was something like that. But i wanted to be sure that everything is fine.
It's also possible that it is throttling, check to see whether the front light is blinking when the slowdown occurs. If so, it needs better cooling or lower ambient temperature.Already checked that before posting and it runs fine.
th for the reply. i thought it was something like that. But i wanted to be sure that everything is fine.
It's also possible that it is throttling, check to see whether the front light is blinking when the slowdown occurs. If so, it needs better cooling or lower ambient temperature.
th for the reply. i thought it was something like that. But i wanted to be sure that everything is fine.
Hi i just got my BFL Single and it runs fine at 826Mhps. But from time to time it drops down sometimes below 700 and then crawles back up to 826. Is that normal? Also do you think v1.3 could help.
Because of the way the BFL FPGA devices work some hashes are wasted at every block change. This is why they are useless on p2pool which has block changes every 10 seconds.
Some miners may show a steady hash rate, counting the actual hashes being processed by the unit. I decided to show the effective hash rate instead because it is what really matters and it shows you what is going on. Thrown away hashes are not useful.
In the same vein the BitMinter pool hash rate is the effective hash rate. Many pools count rejected proofs of work for their hash rate, but I don't see the point in this, except that it makes their pools look faster.
I believe I read somewhere that the future ASIC units from BFL will work on p2pool. I assume that means they will have a better protocol for communication between PC and mining device, hopefully resulting in no wasted hashes and perhaps also lower CPU usage (using something smarter than polling).
Hi i just got my BFL Single and it runs fine at 826Mhps. But from time to time it drops down sometimes below 700 and then crawles back up to 826. Is that normal? Also do you think v1.3 could help.
BitMinter client v1.3.0beta3 is ready for testing.
News since beta2:
Please check it out:
I would like to get 1.3.0 out soon, so please help test this beta. I'm particularly interested in performance differences for BFL mining compared to 1.2.0 (the current stable version) and with different poll intervals. Also of course any bugs you find and whether it runs ok on raspberry pi or PC with openbsd or freebsd, if you are able to test on any of those.
News since beta2:
- Improve sorting order of FPGAs ("natural" order, usb2 before usb19)
- Re-enabled comm port interval scanning (FPGA section of config)
Can be used to automatically pick up FPGAs when plugged in - Count X accepted/rejected when the work difficulty was X (X is rounded down)
- Fixed bug that could cause "probe all ports" to stop working and
report "no serial ports found" - Changed regular poll interval to 20 ms (was 10) for BFL default config
Saves 5-10% CPU usage on testsystem with 2 BFL minirigs, no performance loss - Changed hammering poll interval to 5 ms (was 1) for BFL default config
Saves 10-15% CPU usage on testsystem with 2 BFL minirigs, < 0.1% perf. loss - Bugfix: stopping an FPGA could cause another FPGA to timeout and stop too
- Hopefully works on OpenBSD and FreeBSD as well now. FPGA only, untested.
Please check it out:
I would like to get 1.3.0 out soon, so please help test this beta. I'm particularly interested in performance differences for BFL mining compared to 1.2.0 (the current stable version) and with different poll intervals. Also of course any bugs you find and whether it runs ok on raspberry pi or PC with openbsd or freebsd, if you are able to test on any of those.
Definitely would be nice to have a backup pool option for times like now...
Yep, that's among the things on the top of my list after Black Hat and Def Con are over.
Do you plan on integrating the asic chips into this program?
Yes, as soon as BFL has info on their new protocol available (for communicating with the devices) I'll start implementing it. In the mean time I am working on other changes to the server and client to make them work better with such high hash rates as you will see with ASICs.
oh cool....thanks for the info....that might even make it better (if namecoins ever become worth anything). do most other mining pools or software do this? ....used guiminer, but never saw namecoins being generated.
Some pools have merged mining of namecoins and some don't. Currently I believe they add about 0.5% to your income if you sell them for bitcoins. After the reward halving on the bitcoin chain the namecoins might be a 1% profit boost. But that depends of course on how the namecoin/bitcoin exchange rate will go.
Do you plan on integrating the asic chips into this program?
Jump to: