Could you try deleting java temporary files and trying again? You find that under java control panel, which you can access from windows control panel if you are on windows. You can also reach it by running "javaws -viewer" from command line on any OS. I had this problem when switching from java 6 to java 7 on a Windows machine.


A couple times today there has been 1500+ more connections than usual and 3-4 times the normal CPU usage. Not sure yet what's causing it as I haven't had the luck to watch it as it happens.

Sorry for the instability this morning.

I woke up just as it was passing. Not sure if it was a networking issue - I couldn't see any problems on the server.

BitMinter client v1.3.0beta2 is ready for testing.

News since beta1:

• Improved automatic timer tuning and hash rate detection for Icarus FPGAs.
• Improved FPGA error handling, should fix lockup that could happen with beta1.
• Fix bug introduced in beta1, crash when unplugging FPGA while mining.
• Bugfix: detect CPU model on Raspberry Pi, and hopefully other ARM systems.
• 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 alphabetically 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.

Please check it out:

Yeah, that's becoming annoying. I lose about 30 BTC every time due to the prepay perk. I have now increased connectivity to the bitcoin network to help reduce orphans.

Anyone running bitcoin-qt/bitcoind from bitcoin.org, please upgrade to v0.6.3. It has faster block propagation which helps reduce orphans for all pools.

On a side note, roll-ntime is now enabled on the server for all miners that support it, to increase efficiency. This means your miner program won't need to talk to the server quite as often.

Have a look at the livestats and all will be revealed

https://bitminter.com/livestats/big

That technique may work with version 1.1.2 http://bitminter.com/client/1.1.2/bitminter.jnlp - I haven't tested it behind a proxy though.

Java proxy settings won't work with the later versions. Hopefully I will have proxy support in the next beta though.

Just click the version number in the table for 32-bit, 64-bit or PowerPC depending on your CPU. I don't think you need "VID/PID combination" (whatever that is), so no need to contact them.

Yep, when you scan for devices and it doesn't find any it will give you some hints in the log. Try grabbing Mac drivers from http://www.ftdichip.com/Drivers/VCP.htm

Edit: The stable version runs fine on Mac. But if it's not too much bother I'd love to hear how the beta runs (look a few posts back). Hopefully it still runs fine and with low CPU usage.

Beautiful screenshot, Fefox. I have to wipe a tear from my eye. 


I have contacted BFL about that, and it's what I'm aiming for, yes.

Currently beta testing Icarus support for the BitMinter client:
https://bitcointalk.org/index.php?topic=31163.msg1008906#msg1008906

New beta version of BitMinter client is out. Please give it a try and report any problems:
https://bitcointalk.org/index.php?topic=31163.msg1008906#msg1008906


Yeah, that was very bad luck. Sure would be nice with an equivalent run of good luck now.

New beta version of BitMinter client is out. Please give it a try and report any problems:
https://bitcointalk.org/index.php?topic=31163.msg1008906#msg1008906

BitMinter client v1.3.0beta1 is out! A big thank you to Turbor for access to his system with Icarus and BFL single for testing.

Here are the news:

• Support Icarus FPGA devices
• Fix "class not found" bug on Raspberry Pi
• 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
• 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

TL;DR: Support Icarus, Raspberry Pi and very high hash rates.

I made a lot of changes to the serial port handling (BFL and Icarus). I'm interested in hearing about any old features that may be broken, specifically whether mining on Mac with FPGAs still works without high CPU usage, and new stuff: mining on Icarus, mining with Raspberry Pi (with Icarus or BFL), and mining on Cairnsmore with Icarus bitstream. Or anything else you find good or bad.

Please check it out:

You could set up a Linux USB stick to boot up, log you in and do "javaws http://bitminter.com/client/bitminter.jnlp" to launch the app.

You'd need a writable filesystem (you can get that installing ubuntu on a USB stick) for saving the settings. First time you start it you'll have to set up name, password, set it to automatically mine when started, etc.

You'll need Java installed.

I may look into streamlining this more in the future.

Looks like there is some kind of routing issue. Anyone else having the same problems dobo79 is having?


You mean solo mining with the BitMinter client? Not currently.

Nothing changed here, and others are still mining. You can't reach the website, nor connect miners?

If you run "traceroute bitminter" (linux) or "tracert bitminter" (windows) at the command prompt, how far does it go before timing out? Do you get to any hetzner.de hosts?

Nonces starting with three nullbytes (0x000000??) are never reported. Nonces starting with three FF (0xFFFFFF??) always get 01 for the fourth byte, which is usually an incorrect result. This had me confused for a while. Error in the bitstream?

Adding Icarus support to my miner. But I can't get it to ever return a nonce starting with three null bytes. I feed it data for which there is such a solution, but it's not working.

Is that normal? Does it start scanning from nonce 0x00000100 ?

You're back just in time for the block from hell. Let's hope it ends soon.

Thanks guys