DiabloMiner GPU Miner

[DiabloD3]

Hi guys, need a little help here.

I just got my second mining rig up and (kinda) running, but I'm having some troubles.

When I try to run Diablo, I get the following messages:
 "Using AMD parallel processing OpenCL 1.1 AMD-App (851.4)
error: OpenCL platform AMD parallel processing OpenCL contains no devices
error: No OpenCL devices found
Diablominer: An error occurred while starting the application.

I'm running 12.3 catalyst on XP Pro SP3, and everything looks fine on the desktop side.
It seems like there's no SDK installed, but I tried installing it manually and there's no difference.
Thoughts?

Which Radeon?

Oops!
5830, sorry forgot to put that in.

12.1 and up install the runtime, you should never install the SDK on top of Catalyst anymore.

What arguments did you give DM?

[1714019243]

1714019243

[Elmojo]

12.1 and up install the runtime, you should never install the SDK on top of Catalyst anymore.

What arguments did you give DM?

Funny you should say that, because I just finished doing a complete uninstall and reinstall of 12.2 and it seems to be working now.
However, now I'm having a problem with the machine locking up while mining.
I suspect my power supply is sketchy, and could be the issue.
Thanks for the quick replies!

[DiabloD3]

12.1 and up install the runtime, you should never install the SDK on top of Catalyst anymore.

What arguments did you give DM?

Funny you should say that, because I just finished doing a complete uninstall and reinstall of 12.2 and it seems to be working now.
However, now I'm having a problem with the machine locking up while mining.
I suspect my power supply is sketchy, and could be the issue.
Thanks for the quick replies!

Either PSU sucks, wall power sucks, you're overclocking and/or undervolting too far, or GPU temp is over 85c (or less if the card is a shitty brand).

[Elmojo]

12.1 and up install the runtime, you should never install the SDK on top of Catalyst anymore.

What arguments did you give DM?

Funny you should say that, because I just finished doing a complete uninstall and reinstall of 12.2 and it seems to be working now.
However, now I'm having a problem with the machine locking up while mining.
I suspect my power supply is sketchy, and could be the issue.
Thanks for the quick replies!

Either PSU sucks, wall power sucks, you're overclocking and/or undervolting too far, or GPU temp is over 85c (or less if the card is a shitty brand).

I'm leaning towards the PSU being the culprit.
Wall power is clean, only overclocking to 950core/333mem, no voltage adjustments, GPU temp hasn't gone over 70c that I've seen so far.

[DiabloD3]

12.1 and up install the runtime, you should never install the SDK on top of Catalyst anymore.

What arguments did you give DM?

Funny you should say that, because I just finished doing a complete uninstall and reinstall of 12.2 and it seems to be working now.
However, now I'm having a problem with the machine locking up while mining.
I suspect my power supply is sketchy, and could be the issue.
Thanks for the quick replies!

Either PSU sucks, wall power sucks, you're overclocking and/or undervolting too far, or GPU temp is over 85c (or less if the card is a shitty brand).

I'm leaning towards the PSU being the culprit.
Wall power is clean, only overclocking to 950core/333mem, no voltage adjustments, GPU temp hasn't gone over 70c that I've seen so far.

Try no overclocks and see if it still locks up. If it doesn't, then you overclocked too far.

[Joshwaa]

Just my experience.. I have 5 HD5830's and all run happy at 900/300 except for one.. will not run with out crashing unless mem is above 610mhz. Just my 2 BTC.

[penguinlust]

Hi, folks. I'm experimenting with using my 6770 for mining using DiabloMiner. I love how easy this software is to set up, but there's one commandline switch I don't understand...

What does the -g switch do?

I'm getting a respectable 185-190 MH with my current configuration, but I'd like to improve my efficiency and keep the other miners in the pool happy. Will setting -g higher (or lower?) help me achieve that? (FYI, I have a good Internet connection and no issues connecting to the server for the pool.)

[DiabloD3]

Hi, folks. I'm experimenting with using my 6770 for mining using DiabloMiner. I love how easy this software is to set up, but there's one commandline switch I don't understand...

What does the -g switch do?

I'm getting a respectable 185-190 MH with my current configuration, but I'd like to improve my efficiency and keep the other miners in the pool happy. Will setting -g higher (or lower?) help me achieve that? (FYI, I have a good Internet connection and no issues connecting to the server for the pool.)

-g sets how often it pulls new work; however, it is completely ignored on any pool that does long poll and/or sets an expiry time. The default value of -g is whats recommended for solo miners.

[penguinlust]

Ah-ha! So that explains why the setting doesn't seem to make a difference for me! Thanks for the explanation.

[alpet]

Hi! How set secondary pool in failover configuration? Can miner works with several pools simultaneously?

[DiabloD3]

Hi! How set secondary pool in failover configuration? Can miner works with several pools simultaneously?

That is detailed in the op post: just use commas in the arguments.

[alpet]

That is detailed in the op post: just use commas in the arguments.

Tested with sample:

Code:

-o pool.metabank.ru,pit.deepbit.net -r 80,8332

With different ports, secondary not worked if primary fails. Error is "Read timeout"

[DiabloD3]

That is detailed in the op post: just use commas in the arguments.

Tested with sample:

Code:

-o pool.metabank.ru,pit.deepbit.net -r 80,8332

With different ports, secondary not worked if primary fails. Error is "Read timeout"

You can't use port 80 with DiabloMiner. Also, it will still emit the error, but it still switches to the next.

[alpet]

You can't use port 80 with DiabloMiner. Also, it will still emit the error, but it still switches to the next.

Why can't use? My rigs normally works with pool.metabank.ru and sends block to port 80 without errors. Problem only with switch to port 8332 of secondary pool.

[DiabloD3]

You can't use port 80 with DiabloMiner. Also, it will still emit the error, but it still switches to the next.

Why can't use? My rigs normally works with pool.metabank.ru and sends block to port 80 without errors. Problem only with switch to port 8332 of secondary pool.

DiabloMiner automatically rewrites 80 to the default port to prevent user error.

[alpet]

DiabloMiner automatically rewrites 80 to the default port to prevent user error.

I'm confused. Default port is 8332 ? With option -r 8332,8332 miner never connected to pool.metabank.ru, and switching to pit.deepbit.net automatically. Possible my miner is older verion.
In network monitor connections on port 80 is established:

[DiabloD3]

DiabloMiner automatically rewrites 80 to the default port to prevent user error.

I'm confused. Default port is 8332 ? With option -r 8332,8332 miner never connected to pool.metabank.ru, and switching to pit.deepbit.net automatically. Possible my miner is older verion.
In network monitor connections on port 80 is established:

Yeah, I think its 8332. Also, forget what I said, I forgot I removed the code that ignores port 80, it should in fact work.

[alpet]

Yeah, I think its 8332. Also, forget what I said, I forgot I removed the code that ignores port 80, it should in fact work.

Ok. Can you improve selecting different port in multipool configuration?

[DiabloD3]

Yeah, I think its 8332. Also, forget what I said, I forgot I removed the code that ignores port 80, it should in fact work.

Ok. Can you improve selecting different port in multipool configuration?

Why? It already allows nearly unlimited pools. I think you made a different mistake, such as not providing comma separated -u and -p as well.

[alpet]

Why? It already allows nearly unlimited pools. I think you made a different mistake, such as not providing comma separated -u and -p as well.

Yep, something in config has been wrong. I rewrited its, and failover now working. Thanks!