MultiMiner: Any Miner, Any Where, on Any Device (Free, Open Source, Cross Platform)

[danboid]

I have been able to work round that crash by leaving the zero in the port entry box, entering the port then deleting the zero so there is always text in the box.

I've added the details of my Bitcoin pool to coin config and I can see my Icarus devices listed in the main window but the start button is greyed out. Why might that be?

Thanks for your help!

[1714199105]

1714199105

[1714199105]

1714199105

[1714199105]

1714199105

[1714199105]

1714199105

[1714199105]

1714199105

[Foss]

Very strange bug: if usb bluetooth adapter conected MM or bfg does not see GPU's. Old MM 1.3.47 with cgminer work fine.  MM - 2.3.5, bfg - 3.10 win 64, win7x64, i7-4770k, 8 Gb RAM, HD 7870 with dummy plug & HD 7950 with dummy plug , main video - integrated HD 4600.

[nwoolls]

I've added the details of my Bitcoin pool to coin config and I can see my Icarus devices listed in the main window but the start button is greyed out. Why might that be?

Sounds like you need to select a coin configuration for the devices displayed. Right-click on the individual device name (e.g. the name of an ASIC or GPU) and you'll see a menu of configured coins. Select one and click Save, and then the Start button should be enabled.

Alternatively you can use the Quick Switch to switch all devices to a coin at once.

[nwoolls]

Very strange bug: if usb bluetooth adapter conected MM or bfg does not see GPU's. Old MM 1.3.47 with cgminer work fine.  MM - 2.3.5, bfg - 3.10 win 64, win7x64, i7-4770k, 8 Gb RAM, HD 7870 with dummy plug & HD 7950 with dummy plug , main video - integrated HD 4600.

At a guess bfgminer is crashing trying to probe for USB ASICs. MultiMiner launches bfgminer with the -S all argument to ensure it picks up all devices, but this also means bfgminer pokes and prods all sorts of hardware.

Please post the output of the following command:

Code:

bfgminer -d? -S all -D

[Foss]

Sorry I hurried, this full version

[nwoolls]

It hasn't finished, keep waiting. Once it finishes you'll probably need to post this over on the bfgminer thread.

What I'll probably do is introduce a setting in the next update so that the -S auto argument is used instead of -S all. It won't detect some devices (Erupters, AntMiners) but it also doesn't probe and poke every USB device on the system.

[nwoolls]

No idea if this will help, but here is a sample of a reject from the log:

If you get bored pop by #eligius on Freenode IRC. I'm gonna be spending time this weekend working with Luke on sniping Scrypt bugs.

[nwoolls]

What I'll probably do is introduce a setting in the next update so that the -S auto argument is used instead of -S all. It won't detect some devices (Erupters, AntMiners) but it also doesn't probe and poke every USB device on the system.

@Foss: I've added an option to disable the USB probing. You can try out an unofficial build here:

https://www.dropbox.com/s/ll1805ms0haydv8/MultiMiner-2.4.0.zip

Check the option to disable USB probing under Settings > Advanced miner settings.

[The Observer]

So.... 10 pages of reading and i feel i am still where i started. i have been using Multiminer since there were only 2 pages on this thread, AND I LOVE IT. i recently just bought a bunch of antminer U1 usb's to add to my list of hardware, and for the life of me cannot get them to be recognized or work on multi-miner.

I have already FULLY uninstalled multiminer and BFG, wiping everything from the appdata folders and everything. Re-installed the latest release. re-installed all the sillicone labs drivers. tried every tweak i could think of. I see a lot of people who can get them recognized just not get them working, and i cannot even get mine to show up on the list of devices.

Is there any more official fix for this at the moment? if not, does anyone have any suggestions on how to run the Antminer U1's outside of multiminer on a different client without messing up all the hardware i already have running on multiminer?

Thanks,

[nwoolls]

Is there any more official fix for this at the moment? if not, does anyone have any suggestions on how to run the Antminer U1's outside of multiminer on a different client without messing up all the hardware i already have running on multiminer?

Either use one of the unofficial builds of 2.4 from earlier in this thread or use the latest official release with the following entered under Settings > Advanced miner settings for Hardware Scan arguments:

Code:

-S antminer:all

[good_shepherd]

i found a bug to fix... this ones easy.

ok to fix BSOD with long running BFGminers (1 day or soo), i went to the features in advanced settings "restart miner every hour".

it works!!!

my miners no longer goto zero hashrate or cause BSOD.

im very happy with this feature.


however, just an anomoly.


when i manually stop the miners, the timer doesnt stop, cause the next restart will be an hour away from the original start, and not my manual start.

thanks!! love the software


ie:

1st start

7:35
8:35 (restart)
9:35 (restart)

(manual stop at 10:10)

(manuallu click start at 10:20)

10:35 (restart by the feature) insteaf of at 11:20


thanks :-)

[Foss]

What I'll probably do is introduce a setting in the next update so that the -S auto argument is used instead of -S all. It won't detect some devices (Erupters, AntMiners) but it also doesn't probe and poke every USB device on the system.

@Foss: I've added an option to disable the USB probing. You can try out an unofficial build here:

https://www.dropbox.com/s/ll1805ms0haydv8/MultiMiner-2.4.0.zip

Check the option to disable USB probing under Settings > Advanced miner settings.

Yessss that is!!!!!!!!
Thank you

[nwoolls]

Yessss that is!!!!!!!!
Thank you

Always a pleasure  Happy mining!

[danboid]

Hi nwoolls!

Thanks for explaining that! I now have MM mining happily under Debian Jessie / KDE! 

Did you look into the port editing crash with mono? I presume it'll be a bug in mono rather than MM if it doesn't happen with Windows .NET.

[nwoolls]

Did you look into the port editing crash with mono? I presume it'll be a bug in mono rather than MM if it doesn't happen with Windows .NET.

It is indeed a bug in Mono rather than specifically in MultiMiner. I have it noted to see if I can handle it myself, but do plan on doing a native Qt-based UI for MultiMiner on Linux and OS X in the future.

[nwoolls]

when i manually stop the miners, the timer doesnt stop, cause the next restart will be an hour away from the original start, and not my manual start.

My thanks for reporting this - it's fixed in 2.3.6 

[nwoolls]

Gonna kick these both out the door and see what sticks  

Version 2.3.6 of MultiMiner is now available. This is a miner update to 2.3.5 and includes a couple of small bug fixes:

• Fixed additional KeyNotFoundException errors parsing pool information
• Reset the Auto-Restart Miners timer when the user starts mining

Additionally version 2.4.0 of MultiMiner is also available. This includes the above bug fixes as well as the following new features:

• Added official support for AntMiner U1 and LittleFury USB ASICs
• Added a per-pool miner arguments setting (e.g. for providing --pool-proxy)
• Improved support for detecting and displaying device names
• Clicking the Utility column will now toggle the app to display Work Utility
• Both the Current and Effective (based on Work Utility) hash-rate are now shown for each device (in addition to the previous Average hash-rate)
• Coin configurations are no longer permanently disabled when all pools are down and Auto-Mining is enabled under Strategies
• Added the option to disable USB probing
• Hardware is now re-scanned before mining (optionally) automatically starts on startup

Version 2.4 addresses a lot of requests and feedback from users.

From here I will be working on 2.5 which will include the #1 most requested feature. Hold on to your butts!

[ManeBjorn]

You have been crazy busy.
Thanks for all the work.
I can't wait to see what your going to do next. 

Gonna kick these both out the door and see what sticks  

Version 2.3.6 of MultiMiner is now available. This is a miner update to 2.3.5 and includes a couple of small bug fixes:

• Fixed additional KeyNotFoundException errors parsing pool information
• Reset the Auto-Restart Miners timer when the user starts mining

Additionally version 2.4.0 of MultiMiner is also available. This includes the above bug fixes as well as the following new features:

• Added official support for AntMiner U1 and LittleFury USB ASICs
• Added a per-pool miner arguments setting (e.g. for providing --pool-proxy)
• Improved support for detecting and displaying device names
• Clicking the Utility column will now toggle the app to display Work Utility
• Both the Current and Effective (based on Work Utility) hash-rate are now shown for each device (in addition to the previous Average hash-rate)
• Coin configurations are no longer permanently disabled when all pools are down and Auto-Mining is enabled under Strategies
• Added the option to disable USB probing
• Hardware is now re-scanned before mining (optionally) automatically starts on startup

Version 2.4 addresses a lot of requests and feedback from users.

From here I will be working on 2.5 which will include the #1 most requested feature. Hold on to your butts!

[Raptor2213]

Version 2.3.6 of MultiMiner is now available. This is a miner update to 2.3.5

Was that supposed to be a pun?

From here I will be working on 2.5 which will include the #1 most requested feature. Hold on to your butts!

What is the #1 most requested feature?

[nwoolls]

Was that supposed to be a pun?

I'm going to lie and say yes that was entirely intentional and not at all an oversight due to far too much programming 

What is the #1 most requested feature?

That is the question! Can you feel the suspense?