Bitcoin Forum
May 23, 2024, 03:35:47 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 [112] 113 114 115 116 117 118 »
2221  Other / CPU/GPU Bitcoin mining hardware / Re: Official DiabloMiner Thread on: February 28, 2011, 12:19:18 AM
On 69xx you can still use 10.11, but you need SDK 2.3 which does still seem to be stable, but it runs around 15% slower over 2.1 for mining.

11.1 and 11.2 seems to suck for everybody. Its strange.
2222  Other / CPU/GPU Bitcoin mining hardware / Re: Official DiabloMiner Thread on: February 27, 2011, 08:56:21 PM
10.9 through 10.11 + sdk 2.1 remains the most reliable option for most
2223  Other / CPU/GPU Bitcoin mining hardware / Re: Official DiabloMiner Thread on: February 27, 2011, 05:40:41 PM
Read the op post again. 11.1 does not run some or all OpenCL apps correctly.
2224  Other / CPU/GPU Bitcoin mining hardware / Re: Official DiabloMiner Thread on: February 27, 2011, 08:49:56 AM
If it starts with 0/0, restart it until it doesn't do that. Something in the driver hoarked, and I can't fix that.

As for attempts... thats not a bug. Those are supposed to happen. This is why they only show up during debug, that is normal operation. It means it found a block that the first 32 bits are 0 (aka a difficulty of 1)

However, yours are all on GPU #2. This means you didn't turn off Crossfire. Since you're on Windows, owning more than one GPU for mining isn't really worth it since disabling Crossfire also disables all GPUs after the first one. I suggest you mine on Linux instead.
2225  Bitcoin / Mining / Re: Stream SDK 2.1 , 2.2 , 2.3 problems on: February 24, 2011, 09:06:13 AM
As I've said in the DiabloMiner thread repeatedly, with 5xxx, use 10.10 or 10.11 with 2.1. All other combinations are inferior.
2226  Other / CPU/GPU Bitcoin mining hardware / Re: Official DiabloMiner Thread on: February 24, 2011, 09:05:12 AM
As far as I can tell, 11.2 retains whatever 11.1 caused.

11.1 on Linux included a change in the Linux kernel module API (which hasn't been done for awhile), so I suspect they really updated shit.
2227  Other / CPU/GPU Bitcoin mining hardware / Re: Official DiabloMiner Thread on: February 24, 2011, 05:06:32 AM
3xxx Radeons can't run OpenCL. You need 4xxx and up.
2228  Other / CPU/GPU Bitcoin mining hardware / Re: Official DiabloMiner Thread on: February 23, 2011, 09:32:17 AM

According to Diablo, my single 5970 at stock settings, without OC is cruising at ~0.85 Ghash/s. According to BitcoinCharts, it's 1/412th of the current network hashing power, right?

Now, i know that there are more than 3-4 hundred 5970's doing Bitcoin, because most vendors are sold out, so many people have several of them in one machine, and some have entire racks of them, not to mention the communes...

So, which hashing rate number is bogus? Or am i totally missing something obvious?

Thanks in advance.
 

Some of your numbers are bogus. A stock 5970 (which is less than two stock 5870 because of factory underclocking) will around 550 mhash/sec; at full 5870 clocks its closer to around 630.

The current network computational power is around 261 ghash/sec.

261 / 0.550 = 475 stock 5970s or 414 fully clocked ones.

There is probably about 50-100 actual 5970s mining, the bulk of the rest is other Radeons, very few Nvidia users, and a bunch of CPU miner (which, although probably thousands of CPUs mining, basically add very little to the overall effort).
2229  Other / CPU/GPU Bitcoin mining hardware / Re: Official DiabloMiner Thread on: February 22, 2011, 08:48:01 AM
What good is the $COMPUTE? I have a problem with stripping the digit from the $DISPLAY variable, as I'm using it to turn off single cards in my setup, would be nice if there where an easy way to enable/disable single cards by specifying lists of cards on the command line. Actually come to think of it I'll add it myself and file a push request ^^

$COMPUTE is the env variable, like $DISPLAY, that says which cards should be used for computing. SDK 2.3 officially recognizes it, but still uses $DISPLAY when its not set. I assume, eventually, all OpenCL impls on Linux will use $COMPUTE only (or use a much better system that isn't a pile of shit).

I'll look at your branch in a bit.
2230  Other / CPU/GPU Bitcoin mining hardware / Re: Official DiabloMiner Thread on: February 21, 2011, 06:56:44 AM
Update: Automatically strip .[0-9] from $DISPLAY and set $COMPUTE, also make work group size of 64 the default instead of the hardware default
2231  Other / CPU/GPU Bitcoin mining hardware / Re: Official DiabloMiner Thread on: February 19, 2011, 01:58:13 AM
Its the /btc/btc-jrproxy.cgi part of the URL thats wrong. Why use a proxy script when you can just forward the port to what you're trying to proxy? I'll eventually add a --url argument, but I'm not adding it for abuses like that.
2232  Other / CPU/GPU Bitcoin mining hardware / Re: Official DiabloMiner Thread on: February 18, 2011, 12:01:23 PM
Diablo, may you change cli parameters so that they correctly handle the standard URL pattern?
Like this:
Code:
foo://username:password@example.com:8042/over/there/index.dtb?type=animal;name=narwhal#nose
As described http://en.wikipedia.org/wiki/Uniform_Resource_Locator (links to RFC in bottom of page).

I want use your miner with smth like
Code:
....DiabloMiner --host home.agalakov.spb.ru:80/btc/btc-jrproxy.cgi --user a --pass a -w 64 -f 6
, but this don't work. :^(

UPD:
Better example:
Code:
....DiabloMiner --host http://a:a@home.agalakov.spb.ru:80/btc/btc-jrproxy.cgi -w 64 -f 6

Except that URL of yours is bad form with using RPC impls like json rpc and xml rpc. Why not just forward the port instead? There is a --port argument after all.
2233  Other / CPU/GPU Bitcoin mining hardware / Re: Official DiabloMiner Thread on: February 18, 2011, 11:57:53 AM
Investigating a little further: it's only the second core on the 5970 which gives me problems (Invalid block found on Cypress (#2), possible driver or hardware issue) it does however produce correct blocks too, so I'm getting nowhere with that one. The 5850 isn't detected by Diablo, although it does show up in aticonfig.

Any ideas?

Because you didn't turn Crossfire off. Removing the cable doesn't turn it off (and you don't need it for Crossfire anyways, it works fine without it) You have to run aticonfig --initial --adapter=all to write a working xorg.conf. Humble gave you bad advice. Also, for the record, 5970s contain an internal Crossfire bridge.

Also, if your DISPLAY is not set to :0, set it to that otherwise my miner won't see all your GPUs.
2234  Other / CPU/GPU Bitcoin mining hardware / Re: Official DiabloMiner Thread on: February 18, 2011, 11:55:24 AM


Any instructions that require using AMD's packaged version of the drivers are wrong and should never be followed. Please only use distro packaged drivers for fglrx.

Why is that? Working fine for me.
[/quote]

Because AMD is retarded and keeps shipping these things. Use your distro packaging, they know what they are doing.
2235  Other / CPU/GPU Bitcoin mining hardware / Re: Official DiabloMiner Thread on: February 18, 2011, 11:53:39 AM
I am trying to start DiabloMiner. What's the issue?

Exception in thread "main" java.lang.NoClassDefFoundError: com/diablominer/DiabloMiner/DiabloMiner
Caused by: java.lang.ClassNotFoundException: com.diablominer.DiabloMiner.DiabloMiner
   at java.net.URLClassLoader$1.run(URLClassLoader.java:217)
   at java.security.AccessController.doPrivileged(Native Method)
   at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:321)
   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:266)
Could not find the main class: com.diablominer.DiabloMiner.DiabloMiner. Program will exit.


You downloaded it from git and forgot to build it. Run mvn package.
2236  Other / CPU/GPU Bitcoin mining hardware / Re: Official DiabloMiner Thread on: February 16, 2011, 04:39:01 AM
Update: Merged proxy patch
2237  Bitcoin / Pools / Re: Cooperative mining (>20Ghash/s, join us!) on: February 15, 2011, 06:30:40 PM
Exactly. No reason to remove everything else if you're only accepting shares for the current block. Not round. Block.

I'm kindly asking you, geebus and FairUser, to stop trolling here again, as you did in m0mchil thread few days ago.

Dude, our modifications to momchill's miner would seriously reduced the load on your server......yet we're trolling?  WTF Ever.
Diablo's miner does this already, but momchills doesn't. That's the point we were making on m0mchill's thread.


Wait, since I implemented this in my miner, wouldn't this make me the troll?
2238  Other / CPU/GPU Bitcoin mining hardware / Re: Official DiabloMiner Thread on: February 15, 2011, 06:22:18 PM
Just read thru this thread and am still a little confuse on versions required.

1. What version of stream is required? 2.1 only?  
2. Does stream need to be V2.1 for linux too?
3. 10.11 catalyst driver needed for windows?
4. What ati drivers are needed for linux?

Im finding it hard to find a clear walkthru or setup options for this miner... can anyone help?

Thanks! Smiley



2.1 runs fastest and doesnt have the CPU use bug. You only need 2.3 on 6xxx hardware. Yes, you need it on Linux too. 10.11 runs best on Linux and Windows.


Any instructions that require using AMD's packaged version of the drivers are wrong and should never be followed. Please only use distro packaged drivers for fglrx.
2239  Other / CPU/GPU Bitcoin mining hardware / Re: Official DiabloMiner Thread on: February 15, 2011, 06:19:50 PM
Update: I updated to LWJGL 2.7.1 yesterday, but some people were experiencing problems, so I rolled it back to 2.6
2240  Other / CPU/GPU Bitcoin mining hardware / Re: Official DiabloMiner Thread on: February 14, 2011, 12:33:46 AM
If you figure out what, tell me.  Wink

Nope, no flaw. But my miner drives hardware and drivers harder than m0's, so its probably tripping a bug in the driver somewhere. You're not the first person to see that happen, but it should be rare. Going the whole way back to 10.11 has solved it for the people who saw this.
Pages: « 1 ... 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 [112] 113 114 115 116 117 118 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!