DiabloMiner GPU Miner

[kwukduck]

I just reinstalled win7 (64) today and downloaded the latest diablo miner, unfortunately this error pops up:

Code:

[31-7-11 3:05:52] Started
Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 0
        at com.diablominer.DiabloMiner.DiabloMiner.execute(DiabloMiner.java:427)

        at com.diablominer.DiabloMiner.DiabloMiner.main(DiabloMiner.java:133)

[1714117961]

1714117961

[1714117961]

1714117961

[1714117961]

1714117961

[1714117961]

1714117961

[DiabloD3]

I just reinstalled win7 (64) today and downloaded the latest diablo miner, unfortunately this error pops up:

Code:

[31-7-11 3:05:52] Started
Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 0
        at com.diablominer.DiabloMiner.DiabloMiner.execute(DiabloMiner.java:427)

        at com.diablominer.DiabloMiner.DiabloMiner.main(DiabloMiner.java:133)

Yay, I didn't catch the error condition where the user doesn't type any pools to access.

[DiabloD3]

Update: Improved error handling, improved roll ntime disabling support, changed LP hard timeout to 5 minutes

[DiabloD3]

Update: Make roll ntime disabling even more paranoid, change LP timeout back to 10 minutes, re-add force getwork on rejected shares to the new async sendwork code

[DiabloD3]

Update: Remove rollNTimeExpire variable and use refresh/1000, make LP flush all only flushes works for that pool, support X-Reject-Reason in debug output, unify json/rollNTime/fetch time cross-thread signaling in one object

[spiccioli]

Hi DiabloD3,

I'm testing latest version, zip file downloaded yesterday (on a linux coin pc), with a three pools config: mineco.in, slush and btcguild.

I've found that sometimes one or even two pools get 'discarded' and from there on it only mines on the remaining one(s).

Is this by design or something to correct?

TIA

spiccioli.

[DiabloD3]

Hi DiabloD3,

I'm testing latest version, zip file downloaded yesterday (on a linux coin pc), with a three pools config: mineco.in, slush and btcguild.

I've found that sometimes one or even two pools get 'discarded' and from there on it only mines on the remaining one(s).

Is this by design or something to correct?

TIA

spiccioli.

Its by design. Anytime a pool fails to connect during a getwork, that execution thread rotates to the next pool. Which pools execution threads are set to on startup is randomly selected.

The client will generally gravitate towards the most stable pool.

[spiccioli]

Hi DiabloD3,

I'm testing latest version, zip file downloaded yesterday (on a linux coin pc), with a three pools config: mineco.in, slush and btcguild.

I've found that sometimes one or even two pools get 'discarded' and from there on it only mines on the remaining one(s).

Is this by design or something to correct?

TIA

spiccioli.

Its by design. Anytime a pool fails to connect during a getwork, that execution thread rotates to the next pool. Which pools execution threads are set to on startup is randomly selected.

The client will generally gravitate towards the most stable pool.

Ok, I see the logic, but

is there a way to force it to try again (after some time) a pool which gives an error (apart from restarting the program)?

spiccioli

[DiabloD3]

Hi DiabloD3,

I'm testing latest version, zip file downloaded yesterday (on a linux coin pc), with a three pools config: mineco.in, slush and btcguild.

I've found that sometimes one or even two pools get 'discarded' and from there on it only mines on the remaining one(s).

Is this by design or something to correct?

TIA

spiccioli.

Its by design. Anytime a pool fails to connect during a getwork, that execution thread rotates to the next pool. Which pools execution threads are set to on startup is randomly selected.

The client will generally gravitate towards the most stable pool.

Ok, I see the logic, but

is there a way to force it to try again (after some time) a pool which gives an error (apart from restarting the program)?

spiccioli

No.

Although I've been considering having it change pools after a semi-random timeout, but you risk being sent back to the unstable pool.

It really doesn't matter what pool you mine on as long as you're mining, honestly. You'll eventually get the payouts, it just takes a little longer.

[spiccioli]

Hi DiabloD3,

I'm testing latest version, zip file downloaded yesterday (on a linux coin pc), with a three pools config: mineco.in, slush and btcguild.

I've found that sometimes one or even two pools get 'discarded' and from there on it only mines on the remaining one(s).

Is this by design or something to correct?

TIA

spiccioli.

Its by design. Anytime a pool fails to connect during a getwork, that execution thread rotates to the next pool. Which pools execution threads are set to on startup is randomly selected.

The client will generally gravitate towards the most stable pool.

Ok, I see the logic, but

is there a way to force it to try again (after some time) a pool which gives an error (apart from restarting the program)?

spiccioli

No.

Although I've been considering having it change pools after a semi-random timeout, but you risk being sent back to the unstable pool.

It really doesn't matter what pool you mine on as long as you're mining, honestly. You'll eventually get the payouts, it just takes a little longer.

DiabloD3,

Ok, but if this stable pool becomes unreacheable (for example) does your miner move back to one of the previous less-stable pools or stops there waiting for it to become alive again?

Sorry to bother, just to understand its logic.

TIA

spiccioli

[DiabloD3]

DiabloD3,

Ok, but if this stable pool becomes unreacheable (for example) does your miner move back to one of the previous less-stable pools or stops there waiting for it to become alive again?

Sorry to bother, just to understand its logic.

TIA

spiccioli

Yeah, it doesn't keep track of things like that. It'll normally do a 15 second timeout, fail, and rotate to the next.

It is just by virtue of it not rotating off a good pool that it will gravitate towards the more functional pools.

[DiabloD3]

Update: Improved error handling more, remove usage of System.exit() and blanket Exception catching, DiabloMiner now passes FindBugs

[tomek74]

I am having errors compiling DiabloMiner on Lion (Mac Mini 2011 i5 CPU) AMD 6630M.

I am getting the following errer when running maven:
mvn clean install in the DiabloMiner directory. (It works on my MacBook Pro 10.6.8 )

Full debug-log:
http://codepaste.net/ziimsi

[INFO] launch4j: Launch of "windres" failed: the PowerPC architecture is no longer supported.
[ERROR]
net.sf.launch4j.BuilderException: net.sf.launch4j.ExecException: Exec failed(2): [Ljava.lang.String;@3a7f1228
        at net.sf.launch4j.Builder.build(Builder.java:145)
        at com.akathist.maven.plugins.launch4j.Launch4jMojo.execute(Launch4jMojo.java:326)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: net.sf.launch4j.ExecException: Exec failed(2): [Ljava.lang.String;@3a7f1228
        at net.sf.launch4j.Util.exec(Util.java:142)
        at net.sf.launch4j.Cmd.exec(Builder.java:206)
        at net.sf.launch4j.Builder.build(Builder.java:98)
        ... 22 more

[DiabloD3]

I am having errors compiling DiabloMiner on Lion (Mac Mini 2011 i5 CPU) AMD 6630M.

I am getting the following errer when running maven:
mvn clean install in the DiabloMiner directory. (It works on my MacBook Pro 10.6.8 )

Full debug-log:
http://codepaste.net/ziimsi

[INFO] launch4j: Launch of "windres" failed: the PowerPC architecture is no longer supported.
[ERROR]
net.sf.launch4j.BuilderException: net.sf.launch4j.ExecException: Exec failed(2): [Ljava.lang.String;@3a7f1228
        at net.sf.launch4j.Builder.build(Builder.java:145)
        at com.akathist.maven.plugins.launch4j.Launch4jMojo.execute(Launch4jMojo.java:326)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: net.sf.launch4j.ExecException: Exec failed(2): [Ljava.lang.String;@3a7f1228
        at net.sf.launch4j.Util.exec(Util.java:142)
        at net.sf.launch4j.Cmd.exec(Builder.java:206)
        at net.sf.launch4j.Builder.build(Builder.java:98)
        ... 22 more

Seems to be a launch4j bug. Tell them to rebuild the binaries for universal. This will happen on any OSX that doesn't have the PPC emulator anymore (such as any 10.7 and I think some 10.6s)

[tomek74]

Seems to be a launch4j bug. Tell them to rebuild the binaries for universal. This will happen on any OSX that doesn't have the PPC emulator anymore (such as any 10.7 and I think some 10.6s)

Hi DiabloD3,
I will let them know about the bug. Let's see how they react.

I tried something else: I used the compilation from my MacBookPro and copied it to the Mac mini and let it run with following result: (name and password replaced)

localhost:DiabloMinerComp thomas$ ./DiabloMiner-OSX.sh -u placeholder.placeholder -p placeholder -o mining.bitcoin.cz -r 8332
[8/12/11 8:07:43 AM] Started                                                 
[8/12/11 8:07:43 AM] Connecting to: http://mining.bitcoin.cz:8332/           
[8/12/11 8:07:43 AM] Using Apple OpenCL 1.1 (Jun 25 2011 01:23:15)           
[8/12/11 8:07:44 AM] Added ATI Radeon HD 6630M (#1) (5 CU, local work size of 256)
[8/12/11 8:07:44 AM] ERROR: [CL_INVALID_WORK_GROUP_SIZE] : OpenCL Error : clEnqueueNDRangeKernel failed: local_size[0] (256) != required local_size[0] (1024)
[8/12/11 8:07:44 AM] ERROR: Failed to queue kernel, error -54 

[tomek74]

Seems to be a launch4j bug. Tell them to rebuild the binaries for universal. This will happen on any OSX that doesn't have the PPC emulator anymore (such as any 10.7 and I think some 10.6s)

The bug has been submitted already:
https://sourceforge.net/tracker/?func=detail&aid=3385595&group_id=95944&atid=613100#

I have +1 myself.

[DiabloD3]

Seems to be a launch4j bug. Tell them to rebuild the binaries for universal. This will happen on any OSX that doesn't have the PPC emulator anymore (such as any 10.7 and I think some 10.6s)

Hi DiabloD3,
I will let them know about the bug. Let's see how they react.

I tried something else: I used the compilation from my MacBookPro and copied it to the Mac mini and let it run with following result: (name and password replaced)

localhost:DiabloMinerComp thomas$ ./DiabloMiner-OSX.sh -u placeholder.placeholder -p placeholder -o mining.bitcoin.cz -r 8332
[8/12/11 8:07:43 AM] Started                                                 
[8/12/11 8:07:43 AM] Connecting to: http://mining.bitcoin.cz:8332/           
[8/12/11 8:07:43 AM] Using Apple OpenCL 1.1 (Jun 25 2011 01:23:15)           
[8/12/11 8:07:44 AM] Added ATI Radeon HD 6630M (#1) (5 CU, local work size of 256)
[8/12/11 8:07:44 AM] ERROR: [CL_INVALID_WORK_GROUP_SIZE] : OpenCL Error : clEnqueueNDRangeKernel failed: local_size[0] (256) != required local_size[0] (1024)
[8/12/11 8:07:44 AM] ERROR: Failed to queue kernel, error -54 

Known 10.7 bug. Until they fix it, use -w 64.

[tomek74]

I'm running DiabloMiner on a MacMini 10.7 with a ATI Radeon 6630M with the following start parameter:
./DiabloMiner-OSX.sh -u name.macmini -p password -o mining.bitcoin.cz -r 8332 -w 64 -dd

After about 15 minutes the system crashes.

Are the mhash and ghash values realistic?
Last line, before the system crashes:

Code:

mhash: 235.4/591.2 | a/r/hwe: 46/1/0 | ghash: 2456.8 | fps: 272.2

How can I help to debug the issue? (DiabloMiner works perfectly fine an my old MacMini 10.6.8 that I still have.)

Here is the complete output of the DiaboMiner debug log: (Please notice the increasing numbers for mhash and ghash)
http://codepaste.net/qhr2es

[DiabloD3]

I'm running DiabloMiner on a MacMini 10.7 with a ATI Radeon 6630M with the following start parameter:
./DiabloMiner-OSX.sh -u name.macmini -p password -o mining.bitcoin.cz -r 8332 -w 64 -dd

After about 15 minutes the system crashes.

Are the mhash and ghash values realistic?
Last line, before the system crashes:

Code:

mhash: 235.4/591.2 | a/r/hwe: 46/1/0 | ghash: 2456.8 | fps: 272.2

How can I help to debug the issue? (DiabloMiner works perfectly fine an my old MacMini 10.6.8 that I still have.)

Here is the complete output of the DiaboMiner debug log: (Please notice the increasing numbers for mhash and ghash)
http://codepaste.net/qhr2es

The ghash meter just measures raw ghash produced. If it stops moving, then yes, you have a problem. FPS doesn't sound right unless you're a large -f value in the same ballpark, and the second mhash number doesn't make sense unless you own 2 or more video cards.

I assume its just more OSX insanity. I am not surprised.

[tomek74]

The ghash meter just measures raw ghash produced. If it stops moving, then yes, you have a problem. FPS doesn't sound right unless you're a large -f value in the same ballpark, and the second mhash number doesn't make sense unless you own 2 or more video cards.

I assume its just more OSX insanity. I am not surprised.

It is the original Mac Mini without any hardware changes. (1 video card)

How can I help to get rid of the OSX insanity? Or should I get rid of OSX?