 Show Posts
|
|
Pages: « 1 2 [3] 4 »
|
- Cheap generic case - just something that works for mounting a motherboard and PSU - $20
I wouldn't cheap out on the case. A case that can evacuate a lot of heat should be considered a requirement. I am reusing a high quality but very old case that was never designed for the heat generated by these types of cards at these loads and am having issues getting the heat out of the case. I would love to move to 3 cards but just cannot at this time until I solve my heat issues. |
|
|
|
|
Indeed, CPU needs are minimal.
I have two 5870's pushing about .825GH/s while running on a 2.6 GHz Celeron in Ubuntu and the CPU is near idle. 15 minute load average is 0.05.
|
|
|
|
|
same here in 1.45. it reports 0% stales but deepbit reports much more.
also, the % stales I had before (~.27%) is now way up to .31% so it is definitely worse...
|
|
|
|
|
@gat3way, I have about an hour or so. If you want to try and debug anything for a bit I am available. I am on #bitcoin.
|
|
|
|
BTW are your 5870s crossfired ?
No. |
|
|
|
Hmpf, that's kinda strange. I definitely see one issue with the thermal monitoring (5970 detected by ADL as a single device named "5800 series" instead of 2 devices, as far as I understood, it depends on the card's BIOS version, so that I need to take that into account).
OK then the crash thing is really weird. Still not sure why does that happen, will build a version that spits out more debug messages to find out what causes them.
Actually, I have two 5870 cards. I also experience the performance issue. I see about 667MH/s with hashkill and about ~800MH/s with phoenix. |
|
|
|
Could you check what SDK version are you really using?
This is simple: just type:
ldd /usr/bin/hashkill | grep OpenCL
and paste.
Looking at the guide posted, they do install the SDK and they do set it inside .bashrc. However they do not immediately set the LD_LIBRARY_PATH variable and you will not be using SDK2.3 until you relogin (or open a new session). Thus, if you have already set LD_LIBRARY_PATH to SDK2.1 or 2.2, it would crash. I am asking that because the symptoms are very much as though you're using older SDK - it crashes right after the BFI_INT replacement, on the first clEnqueueNDRangeKernel operation.
me@miner00:~/hashkill-0.2.4-x86_64$ hashkill-gpu -p bitcoin *****:deepbit.net:8332 -D -a *****
[hashkill] Version 0.2.4
[hashkill] Plugin 'bitcoin' loaded successfully
[hashkill] Using GPU double mode
[hashkill] Found GPU device: Advanced Micro Devices, Inc. - Cypress
[hashkill] Found GPU device: Advanced Micro Devices, Inc. - Cypress
[hashkill] GPU0: ATI Radeon HD 5800 Series [busy:0%] [temp:53C]
[hashkill] Temperature threshold set to 90 degrees C
[hashkill] This plugin supports GPU acceleration.
[hashkill] Initialized hash indexes
[hashkill] Initialized thread mutexes
[hashkill] Spawned worker threads
[hashkill] Successfully connected and authorized at deepbit.net:8332
[hashkill] Compiling OpenCL kernel source (amd_bitcoin.cl)
[hashkill] Binary size: 348696
[hashkill] Doing BFI_INT magic...
[hashkill] Long polling available, starting LP thread.
Segmentation fault
me@miner00:~/hashkill-0.2.4-x86_64$ ldd /usr/bin/hashkill-gpu | grep OpenCL
libOpenCL.so => /opt/ati-stream-sdk-v2.3-lnx64/lib/x86_64/libOpenCL.so (0x00007fb6f7c73000)
me@miner00:~/hashkill-0.2.4-x86_64$ which hashkill-gpu
/usr/bin/hashkill-gpu
me@miner00:~/hashkill-0.2.4-x86_64$
|
|
|
|
This is what the "tryout" build returned http://www.gat3way.eu/poc/hashkill-0.2.4-x86_64-exp.tgzkh@UMiner:~/Downloads/hashkill/hashkill-0.2.4-x86_64$ sudo ./install.sh Installation complete. Please set your LD_LIBRARY_PATH variable if you are ATI user and intend to run hashkill-gpu Run hashkill-cpu for CPU-based attacks or hashkill-gpu for GPU/CPU-based ones [hashkill] Version 0.2.4 [hashkill] Plugin 'bitcoin' loaded successfully [hashkill] Found GPU device: Advanced Micro Devices, Inc. - Redwood [hashkill] GPU0: ATI Radeon HD 5570 [busy:0%] [temp:60C] [hashkill] Temperature threshold set to 90 degrees C [hashkill] This plugin supports GPU acceleration. [hashkill] Initialized hash indexes [hashkill] Initialized thread mutexes [hashkill] Spawned worker threads [hashkill] Successfully connected and authorized at mining.bitcoin.cz:8332 [hashkill] Compiling OpenCL kernel source (amd_bitcoin.cl) [hashkill] Binary size: 348696 [hashkill] Doing BFI_INT magic... Segmentation fault I get the exact same problem. |
|
|
|
|
The whole 'root install' thing really doesn't matter. Look at the install.sh script. It's using root privs to copy files into /usr/bin and /usr/share/hashkill. None of those files are setuid/gid. When you actually execute the files, you are executing them (unless you are being silly and running hashkill as root or with sudo) with an unprivileged user account. At that point, your risks are the same as if you ran a binary from your home directory.
Now, open code is a different story....
|
|
|
|
@bolapara, with -G4 you are too much dependant on CPU and memory. With systems with multicore CPUs and lots of RAM that's OK, but I guess you'd be better off if you provide -G 2 (or no -G at all). -G4 requires about 700 MB of system memory on a single-GPU system and probably about 1GB with dual-GPU ones (sigh) and if you don't have them free, you can get into swap and generally fuck up overall performance quite a lot  Also, with -G4 it takes more time until all threads kick in and initial kernel compilation time is much slower as well. So you are likely to see peak results after ~20-30 seconds or even more with multi-GPU systems. As a general rule, I'd advise you to stay off turning -G option (unless you are nvidia user with newer drivers where -G2 helps a lot). It has a significant meaning with some "fast" hash cracking plugins (e.g mysql-old), but it does not bring much benefits with bitcoin. You are likely just increasing your overall power consumption without any benefit. OK, thanks. For the record, I also tried no -G option and just -D and had the same results. |
|
|
|
@bolapara: did you use the -D option?
Used -G4 -D |
|
|
|
PS @bolapara how did you get 434 on the 5870, i have one clocked at 850, what is yours at? please share.
Dedicated mining rig Ubuntu 10.10 11.4 drivers, 2.1 SDK 1000 core, 300 mem clocks 100% fan speed 76C phoenix 1.4 - VECTORS AGGRESSION=12 WORKSIZE=128 BFI_INT |
|
|
|
|
Tried it out and you are about 90MH/s slower than phoenix 1.4 for me.
ubuntu 10.10 x64 - 5870
hashkill - SDK 2.3 - ~344MH/s
phoenix 1.4 - SDK 2.1 - ~434MH/s
|
|
|
|
I'm lost. How do I read the 3 fields?
The last two fields are timestamps (number of seconds since epoch) but I'm not sure how to interpret the first field. |
|
|
|
So far how many blocks generated?
As of now it looks like 4! Seems we're a bit on the lucky side right now. |
|
|
|
|
Just a note. So far, my payoffs seem pretty good here compared to other pools. That being said, the total hashrate went down quite a bit from it's peak so I hope it continues!
|
|
|
|
Question. The 'shares' field in hashrate.php output, is that the number of accepted shares for this work unit? Or accepted shares in a period of time? Is there a way for me to see how many accepted shares there are for the current work unit? Isn't that what we are paid on? |
|
|
|
I've never seen this from the current pools. Besides, if a pool operator wanted to cheat, they could just silently withhold/lie about blocks found... I agree statistics are nice, but I'm not sure it's a trust-related issue.
As fpgaminer mentioned, various pools show various data about blocks and payouts. Even if you just provided an API which provided the data in a JSON format, that would be killer. I don't care about having a website if I can get all the info that way. |
|
|
|
Where to see the results?
Any website address to see my money & shares... Results will show up immediately in your client when one of us finds a block. No website or anything setup right now, I'd like to minimize my time spent on it to minimize the fees I have to charge. Maybe when this part is good and tested, it might be worth looking into... dunno yet. Hmm, really in my opinion you are going to need some way of showing when you got a block and what the payout to everyone is. Without that, I don't think people will trust the pool. |
|
|
|
|
Working fine with Phoenix 1.3 and I'm pushing about 428MH/s.
|
|
|
|
|
