janonathon
Newbie
 Offline
Activity: 55
Merit: 0
|
 |
June 29, 2014, 02:03:00 AM |
|
Hi guys, I've just started using multiminer so that i can run an R-Box and have it monitored and reset when it gets sick or dead rather than having to do it manually through bfgminer like i have been. Well I use bitminter and entered all its credentials perfectly into the client but whenever i start mining, Multiminer just signs it into eligius which is something I've never even used and certainly DONT WANT TO. Why won't it just listen to me and mine where I want? Does anyone out there have a fix? I feel like it should be noob stuff (really it SHOULDNT be an issue since I've never entered information for eligius in the 1st place). Thanks for anyone with help.
-John-
Do you have Perks enabled in MultiMiner? Yes What you are seeing is the 1% donation for enabling perks. If you disable perks, it will remove the donation. I don't know all the details how it works but I don't use perks as I mine very few coins and I don't switch for profit etc. Bitminter wasn't recieving any hashpower even though i'd set them up in the initial setup wizard. Do i have to wait for 1% of a day to pass before it switches over? Or is it taken out gradually? I recently had to reconfigure one of my pools as MultiMiner was not connecting properly and would move to the next pool in that coins list. The problem was I removed the "stratum+tcp://" from the pool address (many MM versions ago) and since updating MM, it would no longer connect to the pool without the stratum+tcp:// in the address. I know this for a fact as my S1 was hashing fine on the same pool that MM would/could not connect and mine until I added stratum+tcp:// in the coins url config. The donation is gradual, so there must be something wrong with your pool connection/setup as your equipment is mining and donating 1% to the MM dev. I suggest checking with BTCGuild or Slush pool (if mining SHA-256). Hope that helps some. Check with BTCGuild or slush pool? What about exactly? I've only been to MM and here to deal with miner issues. Not sure why I'm being sent off to different pools... And you type stratum+tcp:// into the field right next to where it says it's adding it in front anyway? |
|
|
|
|
|
|
|
|
|
|
|
No Gods or Kings. Only Bitcoin
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
mstrongbow
Sr. Member
Offline
Activity: 322
Merit: 250
3D Printed!
|
|
June 29, 2014, 02:10:41 AM |
|
Hi guys, I've just started using multiminer so that i can run an R-Box and have it monitored and reset when it gets sick or dead rather than having to do it manually through bfgminer like i have been. Well I use bitminter and entered all its credentials perfectly into the client but whenever i start mining, Multiminer just signs it into eligius which is something I've never even used and certainly DONT WANT TO. Why won't it just listen to me and mine where I want? Does anyone out there have a fix? I feel like it should be noob stuff (really it SHOULDNT be an issue since I've never entered information for eligius in the 1st place). Thanks for anyone with help.
-John-
Do you have Perks enabled in MultiMiner? Yes What you are seeing is the 1% donation for enabling perks. If you disable perks, it will remove the donation. I don't know all the details how it works but I don't use perks as I mine very few coins and I don't switch for profit etc. Bitminter wasn't recieving any hashpower even though i'd set them up in the initial setup wizard. Do i have to wait for 1% of a day to pass before it switches over? Or is it taken out gradually? I recently had to reconfigure one of my pools as MultiMiner was not connecting properly and would move to the next pool in that coins list. The problem was I removed the "stratum+tcp://" from the pool address (many MM versions ago) and since updating MM, it would no longer connect to the pool without the stratum+tcp:// in the address. I know this for a fact as my S1 was hashing fine on the same pool that MM would/could not connect and mine until I added stratum+tcp:// in the coins url config. The donation is gradual, so there must be something wrong with your pool connection/setup as your equipment is mining and donating 1% to the MM dev. I suggest checking with BTCGuild or Slush pool (if mining SHA-256). Hope that helps some. Check with BTCGuild or slush pool? What about exactly? I've only been to MM and here to deal with miner issues. Not sure why I'm being sent off to different pools... And you type stratum+tcp:// into the field right next to where it says it's adding it in front anyway? Only 1 instance of "stratum+tcp://" be entered. I suggested to check your miner that it is it setup properly by pointing it at either BTCGuild or Slush pool to determine if the pool you were originally trying to connect/mine with is up or not. Post up some screenshots of your configs etc. It is difficult to know exactly what your problem is and me just throwing somewhat random suggestions is not getting you anywhere fast. Also, please state what mining gear you are attempting to mine with and what OS etc. |
|
|
|
ManeBjorn
Legendary
Offline
Activity: 1288
Merit: 1004
|
|
June 29, 2014, 02:30:31 AM |
|
If I remember correctly there was a bunch of info on running your blades with MM. They were back in the page 120 to 139 range in this thread. I do not have one setup in MM currently but with the current version of MM comes with the current version of BFGMiner and it is fully compatible. I will re-setup a Blade tomorrow afternoon and post my arguments for you to check out. But in the meantime check back in the above page range there were some arguments and they were what I used for a base. Hi, is there any guide(working) available on how to setup your G-Blade with MM? I've been reading and searching around, somewhere someone reports something and somewhere the other thing - with one single, same device that most of the people are using. Hence not able to gather it up altogether. I'll be getting my very first ASIC on coming Wednesday, so don't have any pre-experience on setting it up. Any help/suggestion on how to set the G-Blade with MM is very much appreciated.
Thanks
P.S. G-Blade doesn't works with SGMiner? Works stable with latest BFGMiner?
Help Please(!) - My G-Blade has already arrived - Before I put it to work, I NEED to know the best or at least properly working configuration for this device, so that I don't damage it - Earlier my question got ignored(even messaged Nate, but he's on vacation, I heard) - So please-please help. Many many thanks in advance.  P.S. I'm mainly want to know the list of "arguments" used to operate this device. What is necessary and what's not to be included in the configuration file. Thanks |
|
|
|
Phoenix48
Newbie
Offline
Activity: 43
Merit: 0
|
|
June 29, 2014, 07:01:24 AM |
|
I get this error not often but once in a while. I always fix it by simply deleting the ApiLog file and restart Multiminer but it seems there is a problem somewhere. Consultez la fin de ce message pour plus de détails sur l'appel du débogage
juste-à-temps (JIT) à la place de cette boîte de dialogue.
************** Texte de l'exception **************
System.UnauthorizedAccessException: L'accès au chemin d'accès 'C:\Users\Daniel\AppData\Roaming\MultiMiner\ApiLog.2' est refusé.
à System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
à System.IO.File.Delete(String path)
à MultiMiner.Utility.Serialization.ObjectLogger.BackupLogFileToSets(String logFilePath) dans d:\Data\Visual Studio Projects\Personal\MultiMiner\MultiMiner\MultiMiner.Utility\Serialization\ObjectLogger.cs:ligne 67
à MultiMiner.Utility.Serialization.ObjectLogger.RollOverLogFile(String logFilePath) dans d:\Data\Visual Studio Projects\Personal\MultiMiner\MultiMiner\MultiMiner.Utility\Serialization\ObjectLogger.cs:ligne 50
à MultiMiner.Utility.Serialization.ObjectLogger.LogObjectToFile(Object objectToLog, String logFilePath) dans d:\Data\Visual Studio Projects\Personal\MultiMiner\MultiMiner\MultiMiner.Utility\Serialization\ObjectLogger.cs:ligne 36
à MultiMiner.Win.Forms.MinerForm.LogObjectToFile(Object objectToLog, String logFileName) dans d:\Data\Visual Studio Projects\Personal\MultiMiner\MultiMiner\MultiMiner.Win\Forms\MinerForm.cs:ligne 5469
à MultiMiner.Win.Forms.MinerForm.LogApiEvent(Object sender, LogEventArgs eventArgs) dans d:\Data\Visual Studio Projects\Personal\MultiMiner\MultiMiner\MultiMiner.Win\Forms\MinerForm.cs:ligne 5621
à MultiMiner.Xgminer.Api.ApiContext.GetResponse(String apiVerb, Int32 timeoutMs) dans d:\Data\Visual Studio Projects\Personal\MultiMiner\MultiMiner\MultiMiner.Xgminer.Api\ApiContext.cs:ligne 131
à MultiMiner.Xgminer.Api.ApiContext.GetSummaryInformation() dans d:\Data\Visual Studio Projects\Personal\MultiMiner\MultiMiner\MultiMiner.Xgminer.Api\ApiContext.cs:ligne 46
à MultiMiner.Win.Forms.MinerForm.GetSummaryInfoFromProcess(MinerProcess minerProcess) dans d:\Data\Visual Studio Projects\Personal\MultiMiner\MultiMiner\MultiMiner.Win\Forms\MinerForm.cs:ligne 5429
à MultiMiner.Win.Forms.MinerForm.PopulateSummaryInfoFromProcesses() dans d:\Data\Visual Studio Projects\Personal\MultiMiner\MultiMiner\MultiMiner.Win\Forms\MinerForm.cs:ligne 5278
à System.Windows.Forms.Timer.OnTick(EventArgs e)
à System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
à System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Assemblys chargés **************
mscorlib
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.8000 (FX35W81RTMGDR.050727-8000)
CodeBase : file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
MultiMiner.Win
Version de l'assembly : 3.2.3.237
Version Win32 : 3.2.3.237
CodeBase : file:///C:/Users/Daniel/AppData/Local/MultiMiner/MultiMiner.Win.exe
----------------------------------------
System.Drawing
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
MultiMiner.Engine
Version de l'assembly : 3.2.3.237
Version Win32 : 3.2.3.237
CodeBase : file:///C:/Users/Daniel/AppData/Local/MultiMiner/MultiMiner.Engine.DLL
----------------------------------------
MultiMiner.Utility
Version de l'assembly : 3.2.3.237
Version Win32 : 3.2.3.237
CodeBase : file:///C:/Users/Daniel/AppData/Local/MultiMiner/MultiMiner.Utility.DLL
----------------------------------------
MultiMiner.Xgminer.Api
Version de l'assembly : 3.2.3.237
Version Win32 : 3.2.3.237
CodeBase : file:///C:/Users/Daniel/AppData/Local/MultiMiner/MultiMiner.Xgminer.Api.DLL
----------------------------------------
MultiMiner.Xgminer
Version de l'assembly : 3.2.3.237
Version Win32 : 3.2.3.237
CodeBase : file:///C:/Users/Daniel/AppData/Local/MultiMiner/MultiMiner.Xgminer.DLL
----------------------------------------
MultiMiner.MobileMiner
Version de l'assembly : 3.2.3.237
Version Win32 : 3.2.3.237
CodeBase : file:///C:/Users/Daniel/AppData/Local/MultiMiner/MultiMiner.MobileMiner.DLL
----------------------------------------
System.Xml
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Core
Version de l'assembly : 3.5.0.0
Version Win32 : 3.5.30729.7903 built by: Win9Rel
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms.resources
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms.resources/2.0.0.0_fr_b77a5c561934e089/System.Windows.Forms.resources.dll
----------------------------------------
Accessibility
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
System.Configuration
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
7b96zp7u
Version de l'assembly : 3.2.3.237
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
tpifzpjw
Version de l'assembly : 3.2.3.237
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
MultiMiner.Discovery
Version de l'assembly : 3.2.3.237
Version Win32 : 3.2.3.237
CodeBase : file:///C:/Users/Daniel/AppData/Local/MultiMiner/MultiMiner.Discovery.DLL
----------------------------------------
MultiMiner.Remoting
Version de l'assembly : 3.2.3.237
Version Win32 : 3.2.3.237
CodeBase : file:///C:/Users/Daniel/AppData/Local/MultiMiner/MultiMiner.Remoting.DLL
----------------------------------------
System.Web.Extensions
Version de l'assembly : 3.5.0.0
Version Win32 : 3.5.30729.7903
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System.Web.Extensions/3.5.0.0__31bf3856ad364e35/System.Web.Extensions.dll
----------------------------------------
3z4h3q54
Version de l'assembly : 3.2.3.237
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
qa1dyynr
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
MultiMiner.CoinWarz
Version de l'assembly : 3.2.3.237
Version Win32 : 3.2.3.237
CodeBase : file:///C:/Users/Daniel/AppData/Local/MultiMiner/MultiMiner.CoinWarz.DLL
----------------------------------------
MultiMiner.CoinApi
Version de l'assembly : 3.2.3.237
Version Win32 : 3.2.3.237
CodeBase : file:///C:/Users/Daniel/AppData/Local/MultiMiner/MultiMiner.CoinApi.DLL
----------------------------------------
MultiMiner.CoinChoose
Version de l'assembly : 3.2.3.237
Version Win32 : 3.2.3.237
CodeBase : file:///C:/Users/Daniel/AppData/Local/MultiMiner/MultiMiner.CoinChoose.DLL
----------------------------------------
fkkqbvqx
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
Newtonsoft.Json
Version de l'assembly : 4.5.0.0
Version Win32 : 5.0.8.16617
CodeBase : file:///C:/Users/Daniel/AppData/Local/MultiMiner/Newtonsoft.Json.DLL
----------------------------------------
System.resources
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System.resources/2.0.0.0_fr_b77a5c561934e089/System.resources.dll
----------------------------------------
mscorlib.resources
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.8000 (FX35W81RTMGDR.050727-8000)
CodeBase : file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
MultiMiner.Coinbase
Version de l'assembly : 3.2.3.237
Version Win32 : 3.2.3.237
CodeBase : file:///C:/Users/Daniel/AppData/Local/MultiMiner/MultiMiner.Coinbase.DLL
----------------------------------------
System.ComponentModel.DataAnnotations
Version de l'assembly : 3.5.0.0
Version Win32 : 3.5.30729.7903
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System.ComponentModel.DataAnnotations/3.5.0.0__31bf3856ad364e35/System.ComponentModel.DataAnnotations.dll
----------------------------------------
System.Runtime.Serialization
Version de l'assembly : 3.0.0.0
Version Win32 : 3.0.4506.7903 (Win9Rel.030729-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Serialization/3.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll
----------------------------------------
System.Xml.Linq
Version de l'assembly : 3.5.0.0
Version Win32 : 3.5.30729.7903 built by: Win9Rel
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml.Linq/3.5.0.0__b77a5c561934e089/System.Xml.Linq.dll
----------------------------------------
System.Data
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_64/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
nbygvzbu
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
ifsm40bu
Version de l'assembly : 3.2.3.237
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
mgl0diit
Version de l'assembly : 3.2.3.237
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
nf0cacch
Version de l'assembly : 3.2.3.237
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
Interop.IWshRuntimeLibrary
Version de l'assembly : 1.0.0.0
Version Win32 : 1.0.0.0
CodeBase : file:///C:/Users/Daniel/AppData/Local/MultiMiner/Interop.IWshRuntimeLibrary.DLL
----------------------------------------
System.Management
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
System.ServiceModel
Version de l'assembly : 3.0.0.0
Version Win32 : 3.0.4506.7903 (Win9Rel.030729-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System.ServiceModel/3.0.0.0__b77a5c561934e089/System.ServiceModel.dll
----------------------------------------
SMDiagnostics
Version de l'assembly : 3.0.0.0
Version Win32 : 3.0.4506.7903 (Win9Rel.030729-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/SMDiagnostics/3.0.0.0__b77a5c561934e089/SMDiagnostics.dll
----------------------------------------
System.Transactions
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_64/System.Transactions/2.0.0.0__b77a5c561934e089/System.Transactions.dll
----------------------------------------
System.Web
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.8001 (FX35W81RTMGDR.050727-8000)
CodeBase : file:///C:/WINDOWS/assembly/GAC_64/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.dll
----------------------------------------
System.IdentityModel
Version de l'assembly : 3.0.0.0
Version Win32 : 3.0.4506.7903 (Win9Rel.030729-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System.IdentityModel/3.0.0.0__b77a5c561934e089/System.IdentityModel.dll
----------------------------------------
jwale8xj
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
MultiMiner.Stats
Version de l'assembly : 3.2.3.237
Version Win32 : 3.2.3.237
CodeBase : file:///C:/Users/Daniel/AppData/Local/MultiMiner/MultiMiner.Stats.DLL
----------------------------------------
wmhqzug2
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
tq0a1l7y
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
yvr3vzlv
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
snb5_jjo
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
4goa2pml
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
wow8vx1m
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
54t0ok51
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
05fqtuyq
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
hjqu-jnn
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
MultiMiner.Services
Version de l'assembly : 3.2.3.237
Version Win32 : 3.2.3.237
CodeBase : file:///C:/Users/Daniel/AppData/Local/MultiMiner/MultiMiner.Services.DLL
----------------------------------------
ifgrppfn
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
vr1cgncr
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
vzisl4v6
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
x8ac5-tj
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
mduht4zk
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
tdamisgs
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
liydcnn9
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
ew_oyzvc
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
p9kr30og
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
brqpgk77
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
-5umrk8m
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
xhovweo2
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
plrkddnv
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
xqwtpo0b
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
mtd8s7bk
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
muhxmu0c
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
vkjl3_qj
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
qj2cggpi
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
_h73ukxb
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
vt9qwp8p
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
lc-znkxv
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
340nndtt
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
d4mhf1vj
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
jf3pkmcr
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
npxlzry9
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
dnv0xntb
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
7q9_8aw8
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
gox3ye7w
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
fenik5lk
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
l8hsa58z
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
qp3iszfk
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
q63iwpvw
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
thy6nyin
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
avhq6off
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
3jx9_1ey
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
iven5j-d
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
kgkzdgpd
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
v9il42gj
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
kuos4bly
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
g7r1b_gj
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
cec7n5q_
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
1zsxxgrx
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
rahjpwgq
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
scigqebh
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
kvfzsjzt
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
1hk33kw-
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
v7agimo8
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
wnjzbzrl
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
6kear6fh
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
bf8rtplq
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
mnvdpbko
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
9-o5enfu
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
1hfiohp2
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
xizy485i
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
lcyymaj4
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
qlsp0qcm
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
ys0esxga
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
iyqcvpob
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
r7xx9ijg
Version de l'assembly : 2.0.0.0
Version Win32 : 2.0.50727.7905 (win9rel.050727-7900)
CodeBase : file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
************** Débogage JIT **************
Pour activer le débogage juste-à-temps (JIT), le fichier de configuration pour cette
application ou cet ordinateur (machine.config) doit avoir la valeur
jitDebugging définie dans la section system.windows.forms.
L'application doit également être compilée avec le débogage
activé.
Par exemple :
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
Lorsque le débogage juste-à-temps est activé, les exceptions non gérées
seront envoyées au débogueur JIT inscrit sur l'ordinateur
plutôt que d'être gérées par cette boîte de dialogue.
|
|
|
|
|
|
conteaza
|
|
June 29, 2014, 05:18:55 PM
Last edit: June 29, 2014, 06:03:25 PM by conteaza |
|
Looks great I'll try this miner right now!BTC
|
|
|
|
|
imall4btc
Member
Offline
Activity: 77
Merit: 10
|
|
June 29, 2014, 06:22:29 PM |
|
If I remember correctly there was a bunch of info on running your blades with MM. They were back in the page 120 to 139 range in this thread. I do not have one setup in MM currently but with the current version of MM comes with the current version of BFGMiner and it is fully compatible. I will re-setup a Blade tomorrow afternoon and post my arguments for you to check out. But in the meantime check back in the above page range there were some arguments and they were what I used for a base. Hi, is there any guide(working) available on how to setup your G-Blade with MM? I've been reading and searching around, somewhere someone reports something and somewhere the other thing - with one single, same device that most of the people are using. Hence not able to gather it up altogether. I'll be getting my very first ASIC on coming Wednesday, so don't have any pre-experience on setting it up. Any help/suggestion on how to set the G-Blade with MM is very much appreciated.
Thanks
P.S. G-Blade doesn't works with SGMiner? Works stable with latest BFGMiner?
Help Please(!) - My G-Blade has already arrived - Before I put it to work, I NEED to know the best or at least properly working configuration for this device, so that I don't damage it - Earlier my question got ignored(even messaged Nate, but he's on vacation, I heard) - So please-please help. Many many thanks in advance. P.S. I'm mainly want to know the list of "arguments" used to operate this device. What is necessary and what's not to be included in the configuration file. Thanks Thanks a lot, ManeBjorn! Glad someone is ready to help me out.  I'm going through those pages you mentioned, but so far didn't found something related to my issue(will continue till the last page though). Started one of blades,with "arguments" as: --set-device gridseed:clock=838(then 850, 870 and max. 900 - with all three values miner is reported DEAD!  ), but have only reached 2.1MH/s hardly!! , really worried now. Closed the miner and started to search again, as I'm scared that with wrong or vague arguments I might damage the device. Will be also waiting for your tested configuration. Thanks P.S. Btw I observed one strange thing in this short period - I had BFGMiner 3.10.0 installed and I never updated it as I didn't use it - with this version I achieved like 2.87MH/s also, thinking that after upgrade I'll get much more hashrate - so I updated to 4.2.0, but to my surprise I only got like 1.8MH/s-2.1MH/s - I'm really worried now.  |
Wallet addresses being updated...
|
|
|
janonathon
Newbie
Offline
Activity: 55
Merit: 0
|
|
June 29, 2014, 07:16:39 PM
Last edit: June 29, 2014, 07:39:19 PM by janonathon |
|
Hi guys, I've just started using multiminer so that i can run an R-Box and have it monitored and reset when it gets sick or dead rather than having to do it manually through bfgminer like i have been. Well I use bitminter and entered all its credentials perfectly into the client but whenever i start mining, Multiminer just signs it into eligius which is something I've never even used and certainly DONT WANT TO. Why won't it just listen to me and mine where I want? Does anyone out there have a fix? I feel like it should be noob stuff (really it SHOULDNT be an issue since I've never entered information for eligius in the 1st place). Thanks for anyone with help.
-John-
Do you have Perks enabled in MultiMiner? Yes What you are seeing is the 1% donation for enabling perks. If you disable perks, it will remove the donation. I don't know all the details how it works but I don't use perks as I mine very few coins and I don't switch for profit etc. Bitminter wasn't recieving any hashpower even though i'd set them up in the initial setup wizard. Do i have to wait for 1% of a day to pass before it switches over? Or is it taken out gradually? I recently had to reconfigure one of my pools as MultiMiner was not connecting properly and would move to the next pool in that coins list. The problem was I removed the "stratum+tcp://" from the pool address (many MM versions ago) and since updating MM, it would no longer connect to the pool without the stratum+tcp:// in the address. I know this for a fact as my S1 was hashing fine on the same pool that MM would/could not connect and mine until I added stratum+tcp:// in the coins url config. The donation is gradual, so there must be something wrong with your pool connection/setup as your equipment is mining and donating 1% to the MM dev. I suggest checking with BTCGuild or Slush pool (if mining SHA-256). Hope that helps some. Check with BTCGuild or slush pool? What about exactly? I've only been to MM and here to deal with miner issues. Not sure why I'm being sent off to different pools... And you type stratum+tcp:// into the field right next to where it says it's adding it in front anyway? Only 1 instance of "stratum+tcp://" be entered. I suggested to check your miner that it is it setup properly by pointing it at either BTCGuild or Slush pool to determine if the pool you were originally trying to connect/mine with is up or not. Post up some screenshots of your configs etc. It is difficult to know exactly what your problem is and me just throwing somewhat random suggestions is not getting you anywhere fast. Also, please state what mining gear you are attempting to mine with and what OS etc. Fixed it. I was making a stupid mistake. I was only putting in my worker name since that's all it was asking for. This last time I reinstalled it I noticed they never ask for a username so i put it in the worker name as the usual "user_worker" and it's going for now. Hopefully the option of "restarting suspect miners" lives up to its name and I can finally stop worrying about its operation. An R-Box as I mentioned before, which has as tendency to get "sick" or "dead" when running on bfgminer. |
|
|
|
|
mstrongbow
Sr. Member
Offline
Activity: 322
Merit: 250
3D Printed!
|
|
June 29, 2014, 07:42:26 PM |
|
Hi guys, I've just started using multiminer so that i can run an R-Box and have it monitored and reset when it gets sick or dead rather than having to do it manually through bfgminer like i have been. Well I use bitminter and entered all its credentials perfectly into the client but whenever i start mining, Multiminer just signs it into eligius which is something I've never even used and certainly DONT WANT TO. Why won't it just listen to me and mine where I want? Does anyone out there have a fix? I feel like it should be noob stuff (really it SHOULDNT be an issue since I've never entered information for eligius in the 1st place). Thanks for anyone with help.
-John-
Do you have Perks enabled in MultiMiner? Yes What you are seeing is the 1% donation for enabling perks. If you disable perks, it will remove the donation. I don't know all the details how it works but I don't use perks as I mine very few coins and I don't switch for profit etc. Bitminter wasn't recieving any hashpower even though i'd set them up in the initial setup wizard. Do i have to wait for 1% of a day to pass before it switches over? Or is it taken out gradually? I recently had to reconfigure one of my pools as MultiMiner was not connecting properly and would move to the next pool in that coins list. The problem was I removed the "stratum+tcp://" from the pool address (many MM versions ago) and since updating MM, it would no longer connect to the pool without the stratum+tcp:// in the address. I know this for a fact as my S1 was hashing fine on the same pool that MM would/could not connect and mine until I added stratum+tcp:// in the coins url config. The donation is gradual, so there must be something wrong with your pool connection/setup as your equipment is mining and donating 1% to the MM dev. I suggest checking with BTCGuild or Slush pool (if mining SHA-256). Hope that helps some. Check with BTCGuild or slush pool? What about exactly? I've only been to MM and here to deal with miner issues. Not sure why I'm being sent off to different pools... And you type stratum+tcp:// into the field right next to where it says it's adding it in front anyway? Only 1 instance of "stratum+tcp://" be entered. I suggested to check your miner that it is it setup properly by pointing it at either BTCGuild or Slush pool to determine if the pool you were originally trying to connect/mine with is up or not. Post up some screenshots of your configs etc. It is difficult to know exactly what your problem is and me just throwing somewhat random suggestions is not getting you anywhere fast. Also, please state what mining gear you are attempting to mine with and what OS etc. Fixed it. I was making a stupid mistake. I was only putting in my worker name since that's all it was asking for. This last time I reinstalled it I noticed they never ask for a username so i put it in the worker name as the usual "user_worker" and it's going for now. Hopefully the option of "restarting suspect miners" lives up to its name and I can finally stop worrying about its operation. An R-Box as I mentioned before, which has as tendency to get "sick" or "dead" when running on bfgminer. MM is awesome for the RBox miners! Only issue I have had with MM and RBox miners is IF your RBox miner loses power, MM will need to RESCAN before the RBox miners will start mining again. Glad you got it working and I figured it was something simple . Cheers! |
|
|
|
ManeBjorn
Legendary
Offline
Activity: 1288
Merit: 1004
|
|
June 29, 2014, 09:11:27 PM |
|
Hi sorry for the delay in getting back to you. --set-device gridseed:clock=838 That is the sweet spot and I normally get 2.6 mh/s to 2.8 mh/s. One thing that it may be is the Diff setting at the pool. Which pool are you using you may be on a VarDiff pool and can adjust it. I found with the newer version of BFGMiner that 512 Diff seems to work the best. You can always go back to the older version of BFG if you need to that worked best for you. Just remove the BFG folder in the Miners folder in the MultiMiner folder. Then copy in the version you want. Just remember to not upgrade when prompted after that point unless you want to try a newer version. If I remember correctly there was a bunch of info on running your blades with MM. They were back in the page 120 to 139 range in this thread. I do not have one setup in MM currently but with the current version of MM comes with the current version of BFGMiner and it is fully compatible. I will re-setup a Blade tomorrow afternoon and post my arguments for you to check out. But in the meantime check back in the above page range there were some arguments and they were what I used for a base. Hi, is there any guide(working) available on how to setup your G-Blade with MM? I've been reading and searching around, somewhere someone reports something and somewhere the other thing - with one single, same device that most of the people are using. Hence not able to gather it up altogether. I'll be getting my very first ASIC on coming Wednesday, so don't have any pre-experience on setting it up. Any help/suggestion on how to set the G-Blade with MM is very much appreciated.
Thanks
P.S. G-Blade doesn't works with SGMiner? Works stable with latest BFGMiner?
Help Please(!) - My G-Blade has already arrived - Before I put it to work, I NEED to know the best or at least properly working configuration for this device, so that I don't damage it - Earlier my question got ignored(even messaged Nate, but he's on vacation, I heard) - So please-please help. Many many thanks in advance. P.S. I'm mainly want to know the list of "arguments" used to operate this device. What is necessary and what's not to be included in the configuration file. Thanks Thanks a lot, ManeBjorn! Glad someone is ready to help me out. I'm going through those pages you mentioned, but so far didn't found something related to my issue(will continue till the last page though). Started one of blades,with "arguments" as: --set-device gridseed:clock=838(then 850, 870 and max. 900 - with all three values miner is reported DEAD! ), but have only reached 2.1MH/s hardly!! , really worried now. Closed the miner and started to search again, as I'm scared that with wrong or vague arguments I might damage the device. Will be also waiting for your tested configuration. Thanks P.S. Btw I observed one strange thing in this short period - I had BFGMiner 3.10.0 installed and I never updated it as I didn't use it - with this version I achieved like 2.87MH/s also, thinking that after upgrade I'll get much more hashrate - so I updated to 4.2.0, but to my surprise I only got like 1.8MH/s-2.1MH/s - I'm really worried now. |
|
|
|
imall4btc
Member
Offline
Activity: 77
Merit: 10
|
|
June 29, 2014, 09:30:56 PM |
|
Thanks for your input, ManeBjorn. Yes, I tried this, but got like 35+ HW, with hashrate around 2.8MH/s. Thought I was damaging the device, so switched it to 800 and now it get 0 HW's @ 2.6MH/s. Having so many HW's surely damages the device, isn't it? You ain't getting any? As well as what command line is used to set the difficulty in MM?? Thanks Hi sorry for the delay in getting back to you. --set-device gridseed:clock=838 That is the sweet spot and I normally get 2.6 mh/s to 2.8 mh/s. One thing that it may be is the Diff setting at the pool. Which pool are you using you may be on a VarDiff pool and can adjust it. I found with the newer version of BFGMiner that 512 Diff seems to work the best. You can always go back to the older version of BFG if you need to that worked best for you. Just remove the BFG folder in the Miners folder in the MultiMiner folder. Then copy in the version you want. Just remember to not upgrade when prompted after that point unless you want to try a newer version. If I remember correctly there was a bunch of info on running your blades with MM. They were back in the page 120 to 139 range in this thread. I do not have one setup in MM currently but with the current version of MM comes with the current version of BFGMiner and it is fully compatible. I will re-setup a Blade tomorrow afternoon and post my arguments for you to check out. But in the meantime check back in the above page range there were some arguments and they were what I used for a base. Hi, is there any guide(working) available on how to setup your G-Blade with MM? I've been reading and searching around, somewhere someone reports something and somewhere the other thing - with one single, same device that most of the people are using. Hence not able to gather it up altogether. I'll be getting my very first ASIC on coming Wednesday, so don't have any pre-experience on setting it up. Any help/suggestion on how to set the G-Blade with MM is very much appreciated.
Thanks
P.S. G-Blade doesn't works with SGMiner? Works stable with latest BFGMiner?
Help Please(!) - My G-Blade has already arrived - Before I put it to work, I NEED to know the best or at least properly working configuration for this device, so that I don't damage it - Earlier my question got ignored(even messaged Nate, but he's on vacation, I heard) - So please-please help. Many many thanks in advance. P.S. I'm mainly want to know the list of "arguments" used to operate this device. What is necessary and what's not to be included in the configuration file. Thanks Thanks a lot, ManeBjorn! Glad someone is ready to help me out. I'm going through those pages you mentioned, but so far didn't found something related to my issue(will continue till the last page though). Started one of blades,with "arguments" as: --set-device gridseed:clock=838(then 850, 870 and max. 900 - with all three values miner is reported DEAD! ), but have only reached 2.1MH/s hardly!! , really worried now. Closed the miner and started to search again, as I'm scared that with wrong or vague arguments I might damage the device. Will be also waiting for your tested configuration. Thanks P.S. Btw I observed one strange thing in this short period - I had BFGMiner 3.10.0 installed and I never updated it as I didn't use it - with this version I achieved like 2.87MH/s also, thinking that after upgrade I'll get much more hashrate - so I updated to 4.2.0, but to my surprise I only got like 1.8MH/s-2.1MH/s - I'm really worried now. |
Wallet addresses being updated...
|
|
|
ManeBjorn
Legendary
Offline
Activity: 1288
Merit: 1004
|
|
June 29, 2014, 09:55:59 PM |
|
I don't think it damages the device it just causes you to get fewer shares accepted. If you are doing great at 800 keep it there. That is great. Thanks for your input, ManeBjorn. Yes, I tried this, but got like 35+ HW, with hashrate around 2.8MH/s. Thought I was damaging the device, so switched it to 800 and now it get 0 HW's @ 2.6MH/s. Having so many HW's surely damages the device, isn't it? You ain't getting any? As well as what command line is used to set the difficulty in MM?? Thanks Hi sorry for the delay in getting back to you. --set-device gridseed:clock=838 That is the sweet spot and I normally get 2.6 mh/s to 2.8 mh/s. One thing that it may be is the Diff setting at the pool. Which pool are you using you may be on a VarDiff pool and can adjust it. I found with the newer version of BFGMiner that 512 Diff seems to work the best. You can always go back to the older version of BFG if you need to that worked best for you. Just remove the BFG folder in the Miners folder in the MultiMiner folder. Then copy in the version you want. Just remember to not upgrade when prompted after that point unless you want to try a newer version. If I remember correctly there was a bunch of info on running your blades with MM. They were back in the page 120 to 139 range in this thread. I do not have one setup in MM currently but with the current version of MM comes with the current version of BFGMiner and it is fully compatible. I will re-setup a Blade tomorrow afternoon and post my arguments for you to check out. But in the meantime check back in the above page range there were some arguments and they were what I used for a base. Hi, is there any guide(working) available on how to setup your G-Blade with MM? I've been reading and searching around, somewhere someone reports something and somewhere the other thing - with one single, same device that most of the people are using. Hence not able to gather it up altogether. I'll be getting my very first ASIC on coming Wednesday, so don't have any pre-experience on setting it up. Any help/suggestion on how to set the G-Blade with MM is very much appreciated.
Thanks
P.S. G-Blade doesn't works with SGMiner? Works stable with latest BFGMiner?
Help Please(!) - My G-Blade has already arrived - Before I put it to work, I NEED to know the best or at least properly working configuration for this device, so that I don't damage it - Earlier my question got ignored(even messaged Nate, but he's on vacation, I heard) - So please-please help. Many many thanks in advance. P.S. I'm mainly want to know the list of "arguments" used to operate this device. What is necessary and what's not to be included in the configuration file. Thanks Thanks a lot, ManeBjorn! Glad someone is ready to help me out. I'm going through those pages you mentioned, but so far didn't found something related to my issue(will continue till the last page though). Started one of blades,with "arguments" as: --set-device gridseed:clock=838(then 850, 870 and max. 900 - with all three values miner is reported DEAD! ), but have only reached 2.1MH/s hardly!! , really worried now. Closed the miner and started to search again, as I'm scared that with wrong or vague arguments I might damage the device. Will be also waiting for your tested configuration. Thanks P.S. Btw I observed one strange thing in this short period - I had BFGMiner 3.10.0 installed and I never updated it as I didn't use it - with this version I achieved like 2.87MH/s also, thinking that after upgrade I'll get much more hashrate - so I updated to 4.2.0, but to my surprise I only got like 1.8MH/s-2.1MH/s - I'm really worried now. |
|
|
|
imall4btc
Member
Offline
Activity: 77
Merit: 10
|
|
June 29, 2014, 10:01:33 PM |
|
Someone at this forum said it damages, so I was worried. If it doesn't, then I'll surely try to OC a bit.  Can you tell me how to set the diff in MM, dunno that.  Thanks P.S. MY ultimate goal is to reach 6MH/s with my G-Blade, not much. I don't think it damages the device it just causes you to get fewer shares accepted. If you are doing great at 800 keep it there. That is great. Thanks for your input, ManeBjorn. Yes, I tried this, but got like 35+ HW, with hashrate around 2.8MH/s. Thought I was damaging the device, so switched it to 800 and now it get 0 HW's @ 2.6MH/s. Having so many HW's surely damages the device, isn't it? You ain't getting any? As well as what command line is used to set the difficulty in MM?? Thanks Hi sorry for the delay in getting back to you. --set-device gridseed:clock=838 That is the sweet spot and I normally get 2.6 mh/s to 2.8 mh/s. One thing that it may be is the Diff setting at the pool. Which pool are you using you may be on a VarDiff pool and can adjust it. I found with the newer version of BFGMiner that 512 Diff seems to work the best. You can always go back to the older version of BFG if you need to that worked best for you. Just remove the BFG folder in the Miners folder in the MultiMiner folder. Then copy in the version you want. Just remember to not upgrade when prompted after that point unless you want to try a newer version. If I remember correctly there was a bunch of info on running your blades with MM. They were back in the page 120 to 139 range in this thread. I do not have one setup in MM currently but with the current version of MM comes with the current version of BFGMiner and it is fully compatible. I will re-setup a Blade tomorrow afternoon and post my arguments for you to check out. But in the meantime check back in the above page range there were some arguments and they were what I used for a base. Hi, is there any guide(working) available on how to setup your G-Blade with MM? I've been reading and searching around, somewhere someone reports something and somewhere the other thing - with one single, same device that most of the people are using. Hence not able to gather it up altogether. I'll be getting my very first ASIC on coming Wednesday, so don't have any pre-experience on setting it up. Any help/suggestion on how to set the G-Blade with MM is very much appreciated.
Thanks
P.S. G-Blade doesn't works with SGMiner? Works stable with latest BFGMiner?
Help Please(!) - My G-Blade has already arrived - Before I put it to work, I NEED to know the best or at least properly working configuration for this device, so that I don't damage it - Earlier my question got ignored(even messaged Nate, but he's on vacation, I heard) - So please-please help. Many many thanks in advance. P.S. I'm mainly want to know the list of "arguments" used to operate this device. What is necessary and what's not to be included in the configuration file. Thanks Thanks a lot, ManeBjorn! Glad someone is ready to help me out. I'm going through those pages you mentioned, but so far didn't found something related to my issue(will continue till the last page though). Started one of blades,with "arguments" as: --set-device gridseed:clock=838(then 850, 870 and max. 900 - with all three values miner is reported DEAD! ), but have only reached 2.1MH/s hardly!! , really worried now. Closed the miner and started to search again, as I'm scared that with wrong or vague arguments I might damage the device. Will be also waiting for your tested configuration. Thanks P.S. Btw I observed one strange thing in this short period - I had BFGMiner 3.10.0 installed and I never updated it as I didn't use it - with this version I achieved like 2.87MH/s also, thinking that after upgrade I'll get much more hashrate - so I updated to 4.2.0, but to my surprise I only got like 1.8MH/s-2.1MH/s - I'm really worried now. |
Wallet addresses being updated...
|
|
|
ManeBjorn
Legendary
Offline
Activity: 1288
Merit: 1004
|
|
June 29, 2014, 11:10:09 PM |
|
Remember to keep them cool if you are overclocking. What pool are you mining on? Some support it through an addition to your login others have a worker panel that you set it with. Here is a list of VarDiff pools that link out to them with instructions for each site. Test your miner with different settings that they have and see how it goes. https://bitcointalk.org/index.php?topic=645532.0Someone at this forum said it damages, so I was worried. If it doesn't, then I'll surely try to OC a bit. Can you tell me how to set the diff in MM, dunno that. Thanks P.S. MY ultimate goal is to reach 6MH/s with my G-Blade, not much. I don't think it damages the device it just causes you to get fewer shares accepted. If you are doing great at 800 keep it there. That is great. Thanks for your input, ManeBjorn. Yes, I tried this, but got like 35+ HW, with hashrate around 2.8MH/s. Thought I was damaging the device, so switched it to 800 and now it get 0 HW's @ 2.6MH/s. Having so many HW's surely damages the device, isn't it? You ain't getting any? As well as what command line is used to set the difficulty in MM?? Thanks Hi sorry for the delay in getting back to you. --set-device gridseed:clock=838 That is the sweet spot and I normally get 2.6 mh/s to 2.8 mh/s. One thing that it may be is the Diff setting at the pool. Which pool are you using you may be on a VarDiff pool and can adjust it. I found with the newer version of BFGMiner that 512 Diff seems to work the best. You can always go back to the older version of BFG if you need to that worked best for you. Just remove the BFG folder in the Miners folder in the MultiMiner folder. Then copy in the version you want. Just remember to not upgrade when prompted after that point unless you want to try a newer version. If I remember correctly there was a bunch of info on running your blades with MM. They were back in the page 120 to 139 range in this thread. I do not have one setup in MM currently but with the current version of MM comes with the current version of BFGMiner and it is fully compatible. I will re-setup a Blade tomorrow afternoon and post my arguments for you to check out. But in the meantime check back in the above page range there were some arguments and they were what I used for a base. Hi, is there any guide(working) available on how to setup your G-Blade with MM? I've been reading and searching around, somewhere someone reports something and somewhere the other thing - with one single, same device that most of the people are using. Hence not able to gather it up altogether. I'll be getting my very first ASIC on coming Wednesday, so don't have any pre-experience on setting it up. Any help/suggestion on how to set the G-Blade with MM is very much appreciated.
Thanks
P.S. G-Blade doesn't works with SGMiner? Works stable with latest BFGMiner?
Help Please(!) - My G-Blade has already arrived - Before I put it to work, I NEED to know the best or at least properly working configuration for this device, so that I don't damage it - Earlier my question got ignored(even messaged Nate, but he's on vacation, I heard) - So please-please help. Many many thanks in advance. P.S. I'm mainly want to know the list of "arguments" used to operate this device. What is necessary and what's not to be included in the configuration file. Thanks Thanks a lot, ManeBjorn! Glad someone is ready to help me out. I'm going through those pages you mentioned, but so far didn't found something related to my issue(will continue till the last page though). Started one of blades,with "arguments" as: --set-device gridseed:clock=838(then 850, 870 and max. 900 - with all three values miner is reported DEAD! ), but have only reached 2.1MH/s hardly!! , really worried now. Closed the miner and started to search again, as I'm scared that with wrong or vague arguments I might damage the device. Will be also waiting for your tested configuration. Thanks P.S. Btw I observed one strange thing in this short period - I had BFGMiner 3.10.0 installed and I never updated it as I didn't use it - with this version I achieved like 2.87MH/s also, thinking that after upgrade I'll get much more hashrate - so I updated to 4.2.0, but to my surprise I only got like 1.8MH/s-2.1MH/s - I'm really worried now. |
|
|
|
imall4btc
Member
Offline
Activity: 77
Merit: 10
|
|
June 29, 2014, 11:51:44 PM |
|
I'm mining coins based on their "straight profitability" through MM. There are quite a lot of pools, actually. After mining with Waffle & Clever, I switched to MM to increase my ROI(in which I've been successful btw! ) I wanted to know how to set diff in MM though. Anyway, thanks for your help, honestly, appreciate it very much!!  Thanks Remember to keep them cool if you are overclocking. What pool are you mining on? Some support it through an addition to your login others have a worker panel that you set it with. Here is a list of VarDiff pools that link out to them with instructions for each site. Test your miner with different settings that they have and see how it goes. https://bitcointalk.org/index.php?topic=645532.0Someone at this forum said it damages, so I was worried. If it doesn't, then I'll surely try to OC a bit. Can you tell me how to set the diff in MM, dunno that. Thanks P.S. MY ultimate goal is to reach 6MH/s with my G-Blade, not much. I don't think it damages the device it just causes you to get fewer shares accepted. If you are doing great at 800 keep it there. That is great. Thanks for your input, ManeBjorn. Yes, I tried this, but got like 35+ HW, with hashrate around 2.8MH/s. Thought I was damaging the device, so switched it to 800 and now it get 0 HW's @ 2.6MH/s. Having so many HW's surely damages the device, isn't it? You ain't getting any? As well as what command line is used to set the difficulty in MM?? Thanks Hi sorry for the delay in getting back to you. --set-device gridseed:clock=838 That is the sweet spot and I normally get 2.6 mh/s to 2.8 mh/s. One thing that it may be is the Diff setting at the pool. Which pool are you using you may be on a VarDiff pool and can adjust it. I found with the newer version of BFGMiner that 512 Diff seems to work the best. You can always go back to the older version of BFG if you need to that worked best for you. Just remove the BFG folder in the Miners folder in the MultiMiner folder. Then copy in the version you want. Just remember to not upgrade when prompted after that point unless you want to try a newer version. If I remember correctly there was a bunch of info on running your blades with MM. They were back in the page 120 to 139 range in this thread. I do not have one setup in MM currently but with the current version of MM comes with the current version of BFGMiner and it is fully compatible. I will re-setup a Blade tomorrow afternoon and post my arguments for you to check out. But in the meantime check back in the above page range there were some arguments and they were what I used for a base. Hi, is there any guide(working) available on how to setup your G-Blade with MM? I've been reading and searching around, somewhere someone reports something and somewhere the other thing - with one single, same device that most of the people are using. Hence not able to gather it up altogether. I'll be getting my very first ASIC on coming Wednesday, so don't have any pre-experience on setting it up. Any help/suggestion on how to set the G-Blade with MM is very much appreciated.
Thanks
P.S. G-Blade doesn't works with SGMiner? Works stable with latest BFGMiner?
Help Please(!) - My G-Blade has already arrived - Before I put it to work, I NEED to know the best or at least properly working configuration for this device, so that I don't damage it - Earlier my question got ignored(even messaged Nate, but he's on vacation, I heard) - So please-please help. Many many thanks in advance. P.S. I'm mainly want to know the list of "arguments" used to operate this device. What is necessary and what's not to be included in the configuration file. Thanks Thanks a lot, ManeBjorn! Glad someone is ready to help me out. I'm going through those pages you mentioned, but so far didn't found something related to my issue(will continue till the last page though). Started one of blades,with "arguments" as: --set-device gridseed:clock=838(then 850, 870 and max. 900 - with all three values miner is reported DEAD! ), but have only reached 2.1MH/s hardly!! , really worried now. Closed the miner and started to search again, as I'm scared that with wrong or vague arguments I might damage the device. Will be also waiting for your tested configuration. Thanks P.S. Btw I observed one strange thing in this short period - I had BFGMiner 3.10.0 installed and I never updated it as I didn't use it - with this version I achieved like 2.87MH/s also, thinking that after upgrade I'll get much more hashrate - so I updated to 4.2.0, but to my surprise I only got like 1.8MH/s-2.1MH/s - I'm really worried now. |
Wallet addresses being updated...
|
|
|
|
bensam123
|
|
June 30, 2014, 04:16:31 AM |
|
Anyone else getting errors with mobileminer API 429 and 500? One of my machines no longer connects for some reason.
MM needs to be updated for x15 as well.
|
|
|
|
|
Oldminer
Legendary
Offline
Activity: 1022
Merit: 1001
|
|
June 30, 2014, 02:06:05 PM |
|
Still waiting for the option to be able to stop/start dead miners individually....
|
|
|
|
mstrongbow
Sr. Member
Offline
Activity: 322
Merit: 250
3D Printed!
|
|
June 30, 2014, 11:43:53 PM
Last edit: July 01, 2014, 06:08:57 AM by mstrongbow |
|
Anyone running MultiMiner with Gridseed Orbs AND Rockminer RBox units on the same Windows machine?
If so, any tips?
edit: modded gridseed orbs
|
|
|
|
crazyearner
Legendary
Offline
Activity: 1820
Merit: 1001
|
|
July 04, 2014, 11:45:54 PM |
|
Loving the kick ass updates and now using gpus for other algo and also A MASSIVE THANK YOU FOR SUPPORTING OTHER MINER SOFTWARE SUCH AS SGMINER
Question I see another rsg version in their how on earth do you get it to work cos I keep on getting miner arguments lol
|
|
|
|
|
ThomasMuller
|
|
July 05, 2014, 05:19:27 PM |
|
I don't know if there is a better documentation for Ubuntu somewhere but debugging by trial and error is slow and time consuming. Is there a way to turn on Debug traces in MM? or verbose mode!
So far my attempts to make MM use bfgminer other than the one downloaded via ppa ended in failure I have been trying to make MM on Ubuntu 12.04 64bit for 3 days.
What Linux documentation there is can be found in the Readme. Unfortunately there's a bug in the current MultiMiner keeping it from detecting BFGMiner on Linux. This will be fixed in the next update. would you like to share the bug with me and build procedure on Linux and I can help you with MM on Ubuntu. it is my best interest to make it work based on how much time you already invested in MM. Any estimate for Linux fix? I'm eager to help! |
|
|
|
|
mstrongbow
Sr. Member
Offline
Activity: 322
Merit: 250
3D Printed!
|
|
July 05, 2014, 08:15:44 PM |
|
I have been unable to get MultiMiner to change my Rockminer RBox frequency even though I use the --set rockminer:clock=290.
They are rock solid but a the extra Gh/s would be nice considering I have 10+ RBox miners (2 Gh/s increase per unit would be OVER 20 Gh/s) so it adds up.
Also, I would like to request a feature for one of the next revisions of MM. How about having MM display the EFFECTIVE hash rates when available instead of the current/average (not sure which it displays now).
Thanks
|
|
|
|
|
