Topic: MultiMiner: Any Miner, Any Where, on Any Device (Free, Open Source, Cross Platform) - page 140. (Read 827340 times)
November 22, 2013, 09:51:54 PM
Does coinchoose still work? I have been getting the "Error Parsing Coin Choose JASON " error all day long on all of my miners.
November 21, 2013, 11:00:57 PM
I would like to know why blues only mining at like half speed in cgminer on this. my blues wont go past 900MH/s on some and others wont go above 1.2GH yet bfgminer am over 2.5GH on most
November 21, 2013, 10:25:45 PM
Okay folks. Here's the last major feature for the v1.3/v1.4 series of MultiMiner: support for the CoinWarz API. I would still encourage anyone having trouble with the free CoinChoose API to let sal002 know so he has a chance to address those issues. Note that the CoinWarz API does require an API key and will allow a maximum of 1,000 calls before you will have to pay.
MultiMiner v1.3.50 (pre-release)
Once things look stable and any outstanding bugs have been addressed I'll release this as a public v1.4 release.
MultiMiner v1.3.50 (pre-release)
Once things look stable and any outstanding bugs have been addressed I'll release this as a public v1.4 release.
November 21, 2013, 03:56:50 AM
You are using cgminer 3.6.6 and it looks like this version does not return the ID argument with the 'devs' RPC API.
Version 1.3.49 is now available as a pre-release and addresses this issue:
- Address error using previous generation miners (cgminer 3.6 or bfgminer 3.4)
November 21, 2013, 02:26:26 AM
Will do
November 21, 2013, 02:20:21 AM
Just sent them
You are using cgminer 3.6.6 and it looks like this version does not return the ID argument with the 'devs' RPC API. Any chance you can try cgminer 3.7.2? In the meantime I'll try cgminer 3.6.6 myself and see if this is easy to fix.
November 21, 2013, 02:11:23 AM
Just sent them
November 21, 2013, 02:03:09 AM
Just updated and now I am getting this .net error on all my miners:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.Collections.ArrayList.get_Item(Int32 index)
at System.Windows.Forms.DataGridViewRowCollection.get_Item(Int32 index)
at MultiMiner.Win.MainForm.PopulateDeviceInfoFromProcesses() in d:\Data\Visual Studio Projects\Personal\MultiMiner\MultiMiner.Win\MainForm.cs:line 1285
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.6407 (Win8RTMGDR.050727-6400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
MultiMiner.Win
Assembly Version: 1.3.48.0
Win32 Version: 1.3.48
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.Collections.ArrayList.get_Item(Int32 index)
at System.Windows.Forms.DataGridViewRowCollection.get_Item(Int32 index)
at MultiMiner.Win.MainForm.PopulateDeviceInfoFromProcesses() in d:\Data\Visual Studio Projects\Personal\MultiMiner\MultiMiner.Win\MainForm.cs:line 1285
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.6407 (Win8RTMGDR.050727-6400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
MultiMiner.Win
Assembly Version: 1.3.48.0
Win32 Version: 1.3.48
Nice - thanks for the quick response!
Can you email me (nwoolls at gmail dot com):
- Screenshots of what MultiMiner looks like when this error happens
- The ApiLog JSON files found in %appdata%\MultiMiner
Edit: And screenshots of the About dialog from MultiMiner please.
November 21, 2013, 01:53:47 AM
Just updated and now I am getting this .net error on all my miners:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.Collections.ArrayList.get_Item(Int32 index)
at System.Windows.Forms.DataGridViewRowCollection.get_Item(Int32 index)
at MultiMiner.Win.MainForm.PopulateDeviceInfoFromProcesses() in d:\Data\Visual Studio Projects\Personal\MultiMiner\MultiMiner.Win\MainForm.cs:line 1285
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.6407 (Win8RTMGDR.050727-6400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
MultiMiner.Win
Assembly Version: 1.3.48.0
Win32 Version: 1.3.48
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.Collections.ArrayList.get_Item(Int32 index)
at System.Windows.Forms.DataGridViewRowCollection.get_Item(Int32 index)
at MultiMiner.Win.MainForm.PopulateDeviceInfoFromProcesses() in d:\Data\Visual Studio Projects\Personal\MultiMiner\MultiMiner.Win\MainForm.cs:line 1285
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.6407 (Win8RTMGDR.050727-6400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
MultiMiner.Win
Assembly Version: 1.3.48.0
Win32 Version: 1.3.48
November 21, 2013, 01:05:30 AM
Version 1.3.48 is now available as a prerelease. This update consists of fixes for cgminer 3.8 and support for BF1 devices : Blue and Red Fury.
A big thank you to another wonderful user who sent me a Red Fury stick. This has made support for BF1 devices possible in this release.
Notes on BF1 / Blue & Red Fury support
The device support story in 1.3.48 isn't super clear. Let me try to clear it up:
As stated above, bfgminer 3.7 will allow automatic detection of both BF1 and Erupter devices, but it also has larger changes that mean it will not be supported by MultiMiner 1.3 or 1.4.
- Official support for BF1 devices (Blue / Red Fury)
- Official support for BFL devices using cgminer (previously only bfgminer officially supported)
- Will not prompt to upgrade to bfgminer 3.7 (3.7 will be a breaking change)
- Fixed deviceIndex errors when mining begins on startup and a previous device is no longer present
- Don't attempt to pass --intensity arguments to cgminer 3.8+
- The option to Disable GPU mining was not working in bfgminer 3.3+
- Specify the --no-adl argument when enumerating devices
A big thank you to another wonderful user who sent me a Red Fury stick. This has made support for BF1 devices possible in this release.
Notes on BF1 / Blue & Red Fury support
The device support story in 1.3.48 isn't super clear. Let me try to clear it up:
- If you need support for both BF1 sticks and Erupter sticks, you must use cgminer (bfgminer 3.6 cannot automatically recognize both BF1 and Erupter sticks - this is resolved for 3.7)
- If you need support for both BF1 sticks and GPUs, you must use bfgminer (cgminer 3.8 no longer supports GPU mining)
- If you need support for BF1 sticks, Erupter sticks, and GPUs cgminer 3.7 may work but is untested
As stated above, bfgminer 3.7 will allow automatic detection of both BF1 and Erupter devices, but it also has larger changes that mean it will not be supported by MultiMiner 1.3 or 1.4.
November 20, 2013, 02:54:56 PM
continued...
To illustrate a bit more fully why things are going the direction they are for v2.0...
I think the future of virtual currency mining looks something like this:
This should be obvious to anyone who has used MultiMiner. The entire point is to let you use your mining hardware - all of it - to mine whatever coins you want.
If you ask the cgminer folks, they are only interested in Bitcoin, only interested in ASICs, and only interested in supporting Linux, constantly discussing dropping support for other OSs.
I (and a lot of other folks) think that the future of mining is very unlikely to be something that only involves folks who run Linux and ASICs. There is far too much interest. However Con and Kano have made it clear that there will be no discussion of scrypt, alt coins, etc.
What can I say...I just don't discriminate.
So this is basically an impasse in where I see the need for an app like MultiMiner and where cgminer has no intention of supporting this set of features.
To illustrate a bit more fully why things are going the direction they are for v2.0...
I think the future of virtual currency mining looks something like this:
- Not just Bitcoin
- Not just ASICs
- Not just Linux
This should be obvious to anyone who has used MultiMiner. The entire point is to let you use your mining hardware - all of it - to mine whatever coins you want.
If you ask the cgminer folks, they are only interested in Bitcoin, only interested in ASICs, and only interested in supporting Linux, constantly discussing dropping support for other OSs.
I (and a lot of other folks) think that the future of mining is very unlikely to be something that only involves folks who run Linux and ASICs. There is far too much interest. However Con and Kano have made it clear that there will be no discussion of scrypt, alt coins, etc.
What can I say...I just don't discriminate.
So this is basically an impasse in where I see the need for an app like MultiMiner and where cgminer has no intention of supporting this set of features.
Thumbs up!
November 20, 2013, 12:15:34 PM
Edit: Try your rescanning without changing the "Disable GPU mining" setting. Maybe the devices are detected at some times and not others? According to Luke the --disable-gpu flag isn't even present in the bfgminer source code anymore. It is literally doing nothing.
Received a Red Fury stick today and have confirmed the above suspicion. If I use bfgminer to scan for devices, sometimes it returns the BF1 device, sometimes it doesn't.
Code:
bfgminer -d? -S opencl:auto -S erupter:all -S bigpic:auto
I'll keep looking into it. In my previous discussions with Luke he indicated that trying to probe for both Erupters and BF1 sticks causes issues, which is what I am seeing too.
November 19, 2013, 09:51:23 PM
continued...
To illustrate a bit more fully why things are going the direction they are for v2.0...
I think the future of virtual currency mining looks something like this:
This should be obvious to anyone who has used MultiMiner. The entire point is to let you use your mining hardware - all of it - to mine whatever coins you want.
If you ask the cgminer folks, they are only interested in Bitcoin, only interested in ASICs, and only interested in supporting Linux, constantly discussing dropping support for other OSs.
I (and a lot of other folks) think that the future of mining is very unlikely to be something that only involves folks who run Linux and ASICs. There is far too much interest. However Con and Kano have made it clear that there will be no discussion of scrypt, alt coins, etc.
What can I say...I just don't discriminate.
So this is basically an impasse in where I see the need for an app like MultiMiner and where cgminer has no intention of supporting this set of features.
To illustrate a bit more fully why things are going the direction they are for v2.0...
I think the future of virtual currency mining looks something like this:
- Not just Bitcoin
- Not just ASICs
- Not just Linux
This should be obvious to anyone who has used MultiMiner. The entire point is to let you use your mining hardware - all of it - to mine whatever coins you want.
If you ask the cgminer folks, they are only interested in Bitcoin, only interested in ASICs, and only interested in supporting Linux, constantly discussing dropping support for other OSs.
I (and a lot of other folks) think that the future of mining is very unlikely to be something that only involves folks who run Linux and ASICs. There is far too much interest. However Con and Kano have made it clear that there will be no discussion of scrypt, alt coins, etc.
What can I say...I just don't discriminate.
So this is basically an impasse in where I see the need for an app like MultiMiner and where cgminer has no intention of supporting this set of features.
November 19, 2013, 09:43:09 PM
Some notes on the direction of this project to those who may be interested:
Work towards 1.4 is progressing nicely. I have completed more fixes for cgminer 3.8, addressed issues reported by users, and should have both CoinWarz and Blue/Red Fury support as well.
That said...
Version 1.4 of MultiMiner will be the last version that supports cgminer. I have discussed this before and unfortunately the time has come. Version 1.4 will support cgminer and should be a solid release. I'll fix anything serious that crops up for the 1.4 release and, as MultiMiner is Open Source and MIT licensed, anyone can pick up there.
I will be branching the code and working on version 2.0. Previously I had tried to keep the code that I depend on in cgminer and bfgminer simple and compatible. However that is getting to be far too difficult with both projects progressing rapidly in their own directions. The reasons I have chosen bfgminer are pretty straight-forward:
So Luke and I will continue to work together, more closely now, to create a more solid mining solution. Because I do not have to try to maintain compatibility, MultiMiner 2.0 should be more stable and with more features.
Let me know if there are any questions. I welcome everyone's feedback. I'd also welcome someone to maintain the cgminer compatibility but, as it is, I just do not have the time to keep up.
Work towards 1.4 is progressing nicely. I have completed more fixes for cgminer 3.8, addressed issues reported by users, and should have both CoinWarz and Blue/Red Fury support as well.
That said...
Version 1.4 of MultiMiner will be the last version that supports cgminer. I have discussed this before and unfortunately the time has come. Version 1.4 will support cgminer and should be a solid release. I'll fix anything serious that crops up for the 1.4 release and, as MultiMiner is Open Source and MIT licensed, anyone can pick up there.
I will be branching the code and working on version 2.0. Previously I had tried to keep the code that I depend on in cgminer and bfgminer simple and compatible. However that is getting to be far too difficult with both projects progressing rapidly in their own directions. The reasons I have chosen bfgminer are pretty straight-forward:
- I am a miner, and I have far better luck mining with bfgminer, especially with USB devices (if I keep refreshing devices with -d? with cgminer under Windows, I consistently get a different number of USB devices)
- bfgminer supports GPU mining, cgminer does not
- Luke has been very open and receptive in working with me from the beginning
- I hate to say it but there honestly seems to be a lot of attitude and ego to be found in the cgminer threads
So Luke and I will continue to work together, more closely now, to create a more solid mining solution. Because I do not have to try to maintain compatibility, MultiMiner 2.0 should be more stable and with more features.
Let me know if there are any questions. I welcome everyone's feedback. I'd also welcome someone to maintain the cgminer compatibility but, as it is, I just do not have the time to keep up.
November 19, 2013, 06:16:46 PM
When I disable GPU
Are you talking about the "Disable GPU mining" button in MultiMiner? If so I'd direct you to the bfgminer thread. These all sound like bugs to me. This is what those above combinations are running:
"Disable GPU mining" checked in MultiMiner:
Code:
bfgminer -d? -S all -S opencl:auto --disable-gpu
"Disable GPU mining" unchecked in MultiMiner:
Code:
bfgminer -d? -S all -S opencl:auto
I cannot see how these should affect Blue Fury detection.
Edit: Try your rescanning without changing the "Disable GPU mining" setting. Maybe the devices are detected at some times and not others? According to Luke the --disable-gpu flag isn't even present in the bfgminer source code anymore. It is literally doing nothing.
No idea all I know is multiminer hates it all wish could get working and be happy but grrrrrr.
November 19, 2013, 04:05:07 PM
When I disable GPU
Are you talking about the "Disable GPU mining" button in MultiMiner? If so I'd direct you to the bfgminer thread. These all sound like bugs to me. This is what those above combinations are running:
"Disable GPU mining" checked in MultiMiner:
Code:
bfgminer -d? -S all -S opencl:auto --disable-gpu
"Disable GPU mining" unchecked in MultiMiner:
Code:
bfgminer -d? -S all -S opencl:auto
I cannot see how these should affect Blue Fury detection.
Edit: Try your rescanning without changing the "Disable GPU mining" setting. Maybe the devices are detected at some times and not others? According to Luke the --disable-gpu flag isn't even present in the bfgminer source code anymore. It is literally doing nothing.
November 19, 2013, 03:54:30 PM
I can get the blues and eruptors working fine on bfgminer bit with lots of fucking around. multi miner tho in order for it to detect my blue furys I need gpu enabled a you will see in the pic ones called BMP are the Blue fury usb sticks. They light up and detect. However when going to mine give ms a middle finger lol
The Process Log screen in MultiMiner shows the exact arguments being used to run bfgminer. What is the difference between the non-working arguments that MultiMiner is using and the working arguments that you are using with bfgminer? The "Disable GPU mining" checkbox in MultiMiner is only passing --disable-gpu to bfgminer. If this is affecting Blue Fury detection that sounds like a bug in bfgminer.
When I disable GPU and rescan the untis BMP being the Blue fury disappear. And then the eruptrs show and the gpus. However I cant mine. I have to disable gpus and then i can use the eruptors only. When I stop start a few times I can then use eruptors and gpu even with GPU disabled and when I click to enable GPU my eruptors vanish and then the BMP come back for the blue furys.
November 19, 2013, 03:53:50 PM
I can get the blues and eruptors working fine on bfgminer bit with lots of fucking around. multi miner tho in order for it to detect my blue furys I need gpu enabled a you will see in the pic ones called BMP are the Blue fury usb sticks. They light up and detect. However when going to mine give ms a middle finger lol
The Process Log screen in MultiMiner shows the exact arguments being used to run bfgminer. What is the difference between the non-working arguments that MultiMiner is using and the working arguments that you are using with bfgminer? The "Disable GPU mining" checkbox in MultiMiner is only passing --disable-gpu to bfgminer. If this is affecting Blue Fury detection that sounds like a bug in bfgminer.
November 19, 2013, 03:49:36 PM
I can get the blues and eruptors working fine on bfgminer bit with lots of fucking around. multi miner tho in order for it to detect my blue furys I need gpu enabled a you will see in the pic ones called BMP are the Blue fury usb sticks. They light up and detect. However when going to mine give ms a middle finger lol
November 19, 2013, 03:45:50 PM
Just got error
Basically, MultiMiner is running this:
Code:
bfgminer -S all -S opencl:auto -d?
to list your available mining devices. Then it is launching bfgminer with the -d argument to specify those devices. In your screenshot, MultiMiner is specifying -d 0 -d 1 -d 2, but bfgminer is saying one of those devices doesn't exist.
If you are the above command and it shows 3 devices, but then you are unable to mine with them using -d 0 -d 1 -d 2 then that sounds like a bug in bfgminer.
Jump to: