DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author

Quote from: valve on June 11, 2011, 09:51:13 PM

Rebooted, uninstalled and reinstalled the drivers. I was mining this morning but shut them down because of deepbit going down throughout the day and updated the miner then waited for deepbit to come back online. I honestly cannot remember if they started up the first time or not I have been having a strange problem with one of my cards although that was not affecting it earlier maybe that is what it is now. If I would connect to my top card and leave crossfire off the miner would start but would get a driver stopped responding but has recovered error. If I would enable crossfire the miner would start and the computer would just freeze.

Don't enable Crossfire when mining. Try using a newer version of Catalyst (like 11.5), you might be looking at some obscure driver bug.

valve

newbie

Activity: 10

Merit: 0

EDIT
For some reason I cannot post a reply but anyway I updated my drivers and now it is working again. I started up my first miner then connected to the other card and gave starting that one a shot it didn't work the first time and gave me some errors (if you want to know what they are I will edit again and post them) but I pulled back up my info and to my supprise it started mining.

DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author

Quote from: valve on June 11, 2011, 09:34:30 PM

10.10, I am running two 5830 cards so that was the recommended on the first page. I have been mining with these for 4 days now and have not had this happen till today.

Hrm, try rebooting yet? The drivers might have gone nuts.

valve

newbie

Activity: 10

Merit: 0

10.10, I am running two 5830 cards so that was the recommended on the first page. I have been mining with these for 4 days now and have not had this happen till today.

DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author

Quote from: valve on June 11, 2011, 09:04:31 PM

tried starting my miner about 1 hour ago and got this

[6/11/11 7:59:01 pm] started
[6/11/11 7:59:01 pm] connecting to : http://deepbit.net:8332/
[6/11/11 7:59:01 pm] using ATI stream opencl 1.0 ATI-stream-v2.1 <145>
internal error: compilation failed.

[6/11/11 7:59:01 pm] error: failed to build program on cypress <#1>

What version of Catalyst? It might be too old.

valve

newbie

Activity: 10

Merit: 0

tried starting my miner about 1 hour ago and got this

[6/11/11 7:59:01 pm] started
[6/11/11 7:59:01 pm] connecting to : http://deepbit.net:8332/
[6/11/11 7:59:01 pm] using ATI stream opencl 1.0 ATI-stream-v2.1 <145>
internal error: compilation failed.

[6/11/11 7:59:01 pm] error: failed to build program on cypress <#1>

DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author

DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author

Quote from: horrorshow on June 11, 2011, 03:40:48 PM

Ok, so I installed catalyst 10.11 and I thought I had installed SDK 2.1 properly, however...

[6/11/11 3:31:08 PM] Using AMD Accelerated Parallel Processing OpenCL 1.1 AMD-AP
P-SDK-v2.4 (595.10)
[6/11/11 3:31:09 PM] BFI_INT patching enabled, disabling hardware checking
[6/11/11 3:31:09 PM] Added Cypress (#2) (14 CU, local work size of 128)
[6/11/11 3:31:12 PM] Using ATI Stream OpenCL 1.0 ATI-Stream-v2.1 (145)

Does anyone know why it says stream v2.1 and SDK 2.4? How can I fix this on win7 x64?

You have both installed. Don't do that.

mike503

newbie

Activity: 1

Merit: 0

I have a couple headless Solaris 11 machines (or OpenSolaris maybe on one) I'd love to run miners on them if possible. CPU mode right now, since I don't have graphics cards for it right now. It has 2 PCIe slots and 2 open PCI-X slots (yes, PCI-X) if anyone had any ideas of decent-bang-for-buck mining cards t to throw in that are supported under Solaris...

They are headless, so I don't have X11 working.

Any ideas? Tried setting DISPLAY to 0:0 ... still no go. it actually didn't immediately fail, but also didn't work.

Code:


# DISPLAY="0:0" bash ./DiabloMiner-Solaris.sh 
[6/11/11 4:23:17 PM] Started

Exception in thread "main" java.lang.InternalError: Can't connect to X11 window server using '0:0' as the value of the DISPLAY variable.
        at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
        at sun.awt.X11GraphicsEnvironment.access$100(X11GraphicsEnvironment.java:52)
        at sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:155)
        at java.security.AccessController.doPrivileged(Native Method)
        at sun.awt.X11GraphicsEnvironment.(X11GraphicsEnvironment.java:131)
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:169)
        at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:68)
        at sun.awt.X11.XToolkit.(XToolkit.java:89)
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:169)
        at java.awt.Toolkit$2.run(Toolkit.java:834)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:826)
        at org.lwjgl.LinuxSysImplementation.(LinuxSysImplementation.java:45)
        at org.lwjgl.Sys.createImplementation(Sys.java:113)
        at org.lwjgl.Sys.(Sys.java:98)
        at org.lwjgl.opencl.CL.(CL.java:51)
        at com.diablominer.DiabloMiner.DiabloMiner.execute(DiabloMiner.java:391)
        at com.diablominer.DiabloMiner.DiabloMiner.main(DiabloMiner.java:127)

horrorshow

newbie

Activity: 56

Merit: 0

Ok, so I installed catalyst 10.11 and I thought I had installed SDK 2.1 properly, however...

[6/11/11 3:31:08 PM] Using AMD Accelerated Parallel Processing OpenCL 1.1 AMD-AP
P-SDK-v2.4 (595.10)
[6/11/11 3:31:09 PM] BFI_INT patching enabled, disabling hardware checking
[6/11/11 3:31:09 PM] Added Cypress (#2) (14 CU, local work size of 128)
[6/11/11 3:31:12 PM] Using ATI Stream OpenCL 1.0 ATI-Stream-v2.1 (145)

Does anyone know why it says stream v2.1 and SDK 2.4? How can I fix this on win7 x64?

krazzer

newbie

Activity: 1

Merit: 0

I have an early 2009 imac with a Radeon 4850, latest updates running DiabloMiner with -v 2 -w64, i'm getting :
Block 166 found on Radeon HD 4850 (#1)
33241/39200 khash/sec

Is this the best i can get?

claw

newbie

Activity: 13

Merit: 0

After installing 0.3.21 I wasn't sure if I could get it running with the -server flag...it runs, but I'm still not connecting with DiabloMiner so I tried running bitcoind but I had to copy the libeay32.dll into the \daemon directory. Now that's chugging away in the background and when I run DiabloMiner I get several copies of

Quote

[6/11/11 5:50:33 AM] ERROR: Can't connect to Bitcoin: Bitcoin returned error mes
sage: "http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">

Error

401 Unauthorized.

during which time it spiked up to 16Khash/sec and then it stopped returning those errors, threw

Quote

Exception in thread "DiabloMiner Executor (GeForce 9600 GSO (#1)/0)" Exception in thread "DiabloMiner Executor (GeForce 9600 GSO (#1)/1)" java.lang.NullPointerException
at com.diablominer.DiabloMiner.DiabloMiner$DeviceState$ExecutionState.run(DiabloMiner.java:832)
at java.lang.Thread.run(Unknown Source)
Exception in thread "DiabloMiner Executor (GeForce 9600 GSO (#1)/2)" java.lang.NullPointerException
at com.diablominer.DiabloMiner.DiabloMiner$DeviceState$ExecutionState.run(DiabloMiner.java:832)
at java.lang.Thread.run(Unknown Source)
java.lang.NullPointerException
at com.diablominer.DiabloMiner.DiabloMiner$DeviceState$ExecutionState.run(DiabloMiner.java:832)
at java.lang.Thread.run(Unknown Source)

but didn't quit. It settled into displaying "0/yyyy khash/seccsecc" at the bottom of the terminal where yyyy started up in the 12000 range and quickly dropped into the low hundreds before I stopped it.

krom

newbie

Activity: 12

Merit: 0

Quote from: Bartbarian on June 11, 2011, 05:07:14 AM

I'm a bit late to the party but i like magic, and it would be awesome if the landlord would actually pay me to live here (fixed rent baby Wink

I have a Vista 64 work/game rig with a Intel Core 2 e8500 and a HD4870 X2, which lists in GPU Caps OpenCL as two RV770's and a Core2 (thats 3 devices, mining will be fun; it's know for being a hot bitch). I updated my ancient drivers today with newest Catalyst 11.5 and OpenCL 2.4. After all the basic mistakes i now seemed to have DiabloMiner running:

C:\BitCoin\DiabloMiner>DiabloMiner-Windows.exe -u login -p secret -w 64
[11-6-11 11:53:59] Started
[11-6-11 11:53:59] Connecting to: http://127.0.0.1:8332/
[11-6-11 11:53:59] Using AMD Accelerated Parallel Processing OpenCL 1.1 AMD-APP-SDK-v2.4 (595.10)
[11-6-11 11:54:00] Added ATI RV770 (#1) (10 CU, local work size of 64)

but then.. nothing.. the wiki says: A few lines of output will scroll by, followed by "waiting..." or error messages, but this just sits there.

I look into GPU Caps and it says GPU load 2%, Catalyst panel tells me temp stays cool.

I tried fiddling with options but i dont' really understand what's going on. Anyone got suggestions or some angle of attack? (Besides installing linux that is.)

There's a problem with the most recent version of Bitcoin (0.3.22-beta), which results in the problem you describe. Use bitcoin 0.3.21-beta (link) and it should work.

@DiabloD3:
Maybe you should put that info on the first post as long as the problem persists. Although it's not a problem with your miner, ppl might think that.

edit: maybe i should add that i do use Win7 64bit and a HD 4870, accompanied by a AMD X2 @3Ghz. No clue if this problem exists in other OS versions / constellations.

Bartbarian

newbie

Activity: 1

Merit: 0

I'm a bit late to the party but i like magic, and it would be awesome if the landlord would actually pay me to live here (fixed rent baby Wink

I have a Vista 64 work/game rig with a Intel Core 2 e8500 and a HD4870 X2, which lists in GPU Caps OpenCL as two RV770's and a Core2 (thats 3 devices, mining will be fun; it's know for being a hot bitch). I updated my ancient drivers today with newest Catalyst 11.5 and OpenCL 2.4. After all the basic mistakes i now seemed to have DiabloMiner running:

C:\BitCoin\DiabloMiner>DiabloMiner-Windows.exe -u login -p secret -w 64
[11-6-11 11:53:59] Started
[11-6-11 11:53:59] Connecting to: http://127.0.0.1:8332/
[11-6-11 11:53:59] Using AMD Accelerated Parallel Processing OpenCL 1.1 AMD-APP-SDK-v2.4 (595.10)
[11-6-11 11:54:00] Added ATI RV770 (#1) (10 CU, local work size of 64)

but then.. nothing.. the wiki says: A few lines of output will scroll by, followed by "waiting..." or error messages, but this just sits there.

I look into GPU Caps and it says GPU load 2%, Catalyst panel tells me temp stays cool.

I tried fiddling with options but i dont' really understand what's going on. Anyone got suggestions or some angle of attack? (Besides installing linux that is.)

DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author

Quote from: qed on June 10, 2011, 10:41:26 PM

Quote from: DiabloD3 on November 09, 2010, 02:27:42 PM

Radeon users: Catalyst 10.9 through 10.11 + SDK 2.1 seems to be the golden combination for 4xxx and 5xxx miners. Catalyst 11.5a + SDK 2.4 seems to be golden combination for 6xxx. 2.4 does not suffer from the CPU use bug 2.2/2.3 have. Do not use 2.2/2.3.

100% CPU usage still present with Catalyst 11.5a + SDK 2.4.

Its a different bug this time. They moved the CPU usage bug into the driver itself. It only effects SOME Windows users, but not all, and no Linux users.

qed

full member

Activity: 196

Merit: 100

Quote from: DiabloD3 on November 09, 2010, 02:27:42 PM

Radeon users: Catalyst 10.9 through 10.11 + SDK 2.1 seems to be the golden combination for 4xxx and 5xxx miners. Catalyst 11.5a + SDK 2.4 seems to be golden combination for 6xxx. 2.4 does not suffer from the CPU use bug 2.2/2.3 have. Do not use 2.2/2.3.

100% CPU usage still present with Catalyst 11.5a + SDK 2.4.

DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author

Quote from: frisco on June 10, 2011, 05:47:19 PM

I was mining with deepbit for the entire time, maybe laggy sometimes but I have 66ms ping right now.

And about the OC, I tried diferent config that caused visual corruption or even instant freeze this time the app crashed but everything remained working and I think I was able to start the miner again, anyway I will try improve that.

And maybe we don't need nonce stealing but ask ahead when they are running low, that will have no impact on slow miners and should help to avoid short stops, the bigger problem comes when every thread stops at the same time, usually during the first minutes after a connection or block change, not a big deal but it can be an improvement.

What you described sounded like you OC'ed too far.

Asking ahead is hard to do right and it also causes increased stale work. It fetches new work more than once a minute for most users. Also, this uses 3 different sets of work in parallel, its unlikely all 3 will block at the same time.

It really isn't the issue that people claim it is, other miners suffer from it much more.

claw

newbie

Activity: 13

Merit: 0

Quote from: DiabloD3 on June 10, 2011, 01:42:20 PM

Quote from: krom on June 10, 2011, 01:39:48 PM

I had the same problem when setting up the miner. There seems to be a problem with the most recent version of bitcoin (0.3.22-beta). Try version 0.3.21-beta and it should work - given that the rest of your setup is okay.

What, seriously? Thats bad.

Well, it might not be good, but it is progress.

Now -- using the previous version of the Bitcoin client, after reporting that it's added the GPU, it has started throwing "Can't connect to Bitcoin: Connection refused: connect" errors. It throws a bunch (~12) of them with "waiting..." between the first several and then khash/sec figures between them for a while (in the 11-13000 range) and then reports the fatal error and drops out of running.

I'm launching the app with the -u and -p flags each followed by the values in the bitcoin.conf file. Am I supposed to be doing something different because I'm using 0.3.21 now?

frisco

full member

Activity: 176

Merit: 100

I was mining with deepbit for the entire time, maybe laggy sometimes but I have 66ms ping right now.

And about the OC, I tried diferent config that caused visual corruption or even instant freeze this time the app crashed but everything remained working and I think I was able to start the miner again, anyway I will try improve that.

And maybe we don't need nonce stealing but ask ahead when they are running low, that will have no impact on slow miners and should help to avoid short stops, the bigger problem comes when every thread stops at the same time, usually during the first minutes after a connection or block change, not a big deal but it can be an improvement.

DiabloD3

legendary

Activity: 1162

Merit: 1000

DiabloMiner author

Quote from: Lasse on June 10, 2011, 09:00:07 AM

Diablo,

In a previous post you did slash the average hash/s function on deepbit. I am a bit puzzled though: I manage close to 800Mh/s according to dm's output. However, whenever I look at deepbit, I see roughly dm/2. This is fully reflected in the share I receive. Using poclbm, I only managed about 90% of dm's rate, however, the values on deepbit and my share nearly doubled...

Make sure you're using the absolutely most up to date version of the miner. mtrlt's patch screwed up dropping about 1/3rd of shares for some people. I've fixed it since then.

Topic: DiabloMiner GPU Miner - page 54. (Read 866596 times)

401 Unauthorized.