Bitcoin Forum
December 05, 2020, 06:04:30 AM *
News: Bitcointalk Community Awards
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Economy / Digital goods / WTB Google Play Store Gift Card on: May 12, 2017, 11:35:11 AM
I am looking to buy around 10-200$ google play store e-code.


Willing to use escrow if you are not trusted. or you will go first.

If you have please pm'me the code with your btc address. i'll pay you immediately.

%80
2  Bitcoin / Hardware / Weekend Project: USB Block Eruptor Coffee Warmer on: July 24, 2013, 07:33:16 AM
We recently had a surplus of hard drive heat sinks at work from old drives that were being sent out for destruction/recycling and I snagged a few of them on the way out the door. This weekend I wanted to have some fun and decided to turn one of them into a coffee warmer with some spare parts and two spare Block Eruptors I had laying around.

The original unmodified heat sink




I drilled a hole between the two USB connectors and expanded the original outer holes to give sufficient clearance for the zip ties



Added standoffs to each of the corners


Prepping for final assembly


The two Block Eruptors attached to the heat sink with thermal tape


Added zip ties for strain relief



Hashing away


Results:
The heatsink works a little too well and only gets uncomfortably warm on the top of the heatsink, but there is plenty of room to add another one later.
3  Other / CPU/GPU Bitcoin mining hardware / Project: custom 19in rack passive cooling system on: September 02, 2012, 02:38:15 AM
Hi folks,

I figured that I would share my project with you all in the hope that you get a little enjoyment out of it the way I have.

My primary mining system had to be relocated to a common area at home at the end of last year due to a visitor (read MIL) that has been staying with us since that time following the birth of a child. Normally the fan noise from the GPUs when running full-throttle wouldn't be a concern, but the silly things scream like a banshee which had become detrimental to the WAF for my bitcoin mining, so something had to be done. In the mean time I have had to reduce the fan speed (and correspondingly the hash rate) of my system during daylight hours, and can only run at full throttle in the middle of the night.

To that end, my project has the following design goals:
  • Ability to dissipate >900W of heat load
  • Near silent when running
  • Appealing visual design (remembering the WAF)
  • Modular and serviceable
  • Minimum external components
  • Reasonable cost (funded by mining)
  • Flexible design that will allow cooling of next generation mining hardware in addition to the current GPUs

All this in mind, I started looking into water cooling as some folks have had a measure of success increasing efficiency when mining after doing so. Most of the systems I had seen all used active cooling that use one or more fans to pass air through a radiator and remove heat from the cooling liquid. This would work fine if noise isn't a concern, but in my case I had to find another way. As my research progressed, I ran discovered passive cooling. It has the same heat dissipation benefit of active cooling, but needs a larger surface area to allow convection and ambient airflow to dissipate the same heat load. Fortunately my mining rigs are located in a 19in rack with adequate airflow and space to accommodate a larger surface area radiator array.

I discovered the Alphacool Cape Cora series passive radiator modules which met my design goals and began a design based on them. The initial design required keeping at least two rows of the radiators relatively close to the side of the rack, and the original solid aluminum sides of the rack had to be changed out with something that required some air to pass through to allow effective cooling. Also, the radiator modules would be rather heavy once assembled and filled with cooling liquid, so mounts were needed that could accommodate the weight and maintain rigidity. I went through a few designs over the intervening months, but ultimately settled on Design G (the staggered array design below):

High resolution version here.

Since the plan is to use copper heat exchangers and brass fittings in the cooling loop, the aluminum Cape Cora modules posed a problem wrt galvanic corrosion. To that end, I will be electrically insulating the radiator modules and using a corrosion inhibitor in the cooling fluid.

Since there a multiple pumps and sensors, I settled on the Aquaero 5 XT from Aquacomputer to manage everything. At present only Windows drivers are being released by Aquacomputer, so I might need to spend some time updating the Aquaero 4 Linux port someone did a few years ago.

Free time has been hard to come by, so actual construction has been slow. I have uploaded pictures of the progress so far, and will add more as things progress.

Have fun!
4  Other / CPU/GPU Bitcoin mining hardware / GUIDE - Underclocking Memory to 150MHz on a 6990 running Linux on: April 18, 2012, 01:16:57 AM
Hi folks,

This question seems to keep getting asked and there doesn't appear to be a definitive reference available, so this is post is intended to capture all the relevant details necessary to underclock your 6990 memory to 150MHz, and drop your core voltage to 1.050V on Linux.

At the present time there are no software tools available to reliably do this, and it requires reflashing the BIOS. The following procedure documents how to do so.


First a disclaimer: This procedure may damage/brick your card. You have been warned.

With that out of the way, I applied these settings on my two XFX 6990s in mid October 2011 and have been running without issues since that time.


Lets get started:

Download the latest version of the following tools: RBE, ATIFlash

For the overclock BIOS I did the following:

1) With power off, set BIOS switch to overclock position on each 6990.
2) Boot to DOS on your mining rig with CD/USB/floppy (like Ultimate Boot CD) and attach media with ATIFlash.exe if not on the boot media.
3) Enumerate all cards detected with ATIFlash -i
4) Document the BIOS checksum for each of your cards with ATIFlash -cb x where x is your adapter ID provided in step 3.
5) Dump BIOS on each adapter to USB/floppy with ATIFlash -s x BIOSx.ROM where x is the adapter ID.
6) Remove USB/floppy and attach to a Windows PC with RBE.
7) Load each BIOSx.ROM into RBE where x is the adapter ID.
8) In the Clock settings tab, locate Clock info 00 (this should have GPU (MHz) = 880).
9) Modify the settings for Clock info 00 to have GPU (MHz) = 880, RAM (MHz) = 150, Voltage (V) = ?. (Note: Only change the RAM MHz value)
10) Modify the settings for Clock info 03 to have GPU (MHz) = 800, RAM (MHz) = 150, Voltage (V) = ?. (Note: Only change the RAM MHz value)

11) In the GPU registers edit VID4 (mV) from 1175 to 1050. Note: The voltage may or may not update in the Clock info section of RBE. This doesn't matter.

12) Save each BIOS image to the USB/floppy named as BIOSxNEW.ROM where x is the adapter ID.
13) Move the USB/Floppy back to your mining rig.
14) Confirm the checksum on each ROM image with ATIFlash -cf BIOSx.ROM and compare with your previously documented values for each adapter. You can also see these in the Info section of RBE:


If and only if the checksums match proceed to the next steps

15) Flash each new BIOS onto the respective adapter with ATIFlash -p x BIOSxNEW.ROM where x is the adapter ID.
16) Once all adapter BIOS images have been flashed, reboot. It is important not to reboot until both master/slave BIOS on a card have been flashed before rebooting.
17) Boot back into Linux, and confirm the clock settings have been updated with DISPLAY=:0 aticonfig --adapter=all --odgc
18) Mine away (cgminer no longer requires setting --gpu-memdiff)

References: 1, 2

Have fun!
5  Bitcoin / Mining software (miners) / Cacti template for CGMINER monitoring on: April 13, 2012, 04:22:51 AM
Hi folks,

I have had this on my todo list for months, but finally got a few cycles to get started. These templates provide graphs for the stats available from cgminer >=2.1.0 (>=2.3.2 for PGA support) JSON API to compliment my earlier work on pool and AMD GPU Cacti templates.


Sample graphs from my 6990-based GPU miner:

Summary Totals

Total Average Hash Rate (from MHS av)


Total Hash Rate (computed from Total MH)


Total Utility


Total Work


Total Efficiency (computed from Accepted and Getworks)


Total Errors


Devs

5s Average Hash Rate


Average Hash Rate


Fan Percent


Fan Speed


GPU Activity


GPU Clock


GPU Voltage


Hash Rate


Memory Clock


Temperature


Utility


Work


Pools

Work (primary pool)


Work (secondary pool)


Errors (primary pool)


Errors (secondary pool)


Efficiency (primary pool)


Efficiency (secondary pool) Looks like I may have more work to do here




Release History
  • v0.01 4/15/2012
    First working version. Supports cgminer >=2.1.0 API JSON format (>=2.3.2 for PGA support). Supports stats from summary, pools and devs responses. Only tested with GPU support as no PGA or CPU miners were available at the time of release (caveat emptor).

Prerequisites

  • Installed and operational instance of Cacti (Spine and cmd.php pollers both work fine)
  • Perl 5.8.5 or later
  • HTTP::Request Perl module
  • LWP Perl module
  • JSON Perl module
  • JSON::XS Perl module

Install procedure
  • Grab latest script/templates package from here.
  • Unzip the archive
  • Move cgminer_devs_stats.xml and cgminer_pools_stats.xml into your script_queries directory (i.e. cacti/resource/script_queries/)
  • Move query_cgminer_stats.pl into your scripts directory (i.e. cacti/scripts/)
  • Ensure query_cgminer_stats.pl runs (perl query_cgminer_stats.pl generates the help text). If this doesn't work (you see an error about something missing) see the troubleshooting section for resolving Perl issues.
  • Ensure query_cgminer_stats.pl can connect to your CGMINER host, and has read access to the API (perl query_cgminer_stats.pl HOSTNAME summary). If this doesn't work, check your CGMINER options for API access to ensure the requesting host has the appropriate (read-only or read-write) rights.
  • Import the cacti_host_template_cgminer_host.xml host template from the Cacti web GUI.
  • Create a new host in Cacti, selecting the CGMINER Host host template. Set the hostname to your CGMINER hostname or IP. Be sure to disable Downed Host Detection and SNMP unless you have SNMP operational on your host.

Trouble Shooting

Perl issues
  • The most common Perl issue is missing modules. Have a look at this link for assistance in setting up CPAN and testing for missing modules.
  • If you have a Redhat-based distro (RHEL, CentOS, etc), and would prefer to use the RPMs instead of mucking about with CPAN, the perl-libwww-perl RPM (from upstream provider) contains HTTP::Request and other LWP modules. perl-JSON, perl-JSON-XS and perl-Cache-Memcached RPMs are available on RPM Forge and/or EPEL
  • These modules are also available in PPM form for ActiveState's ActivePerl on Windows, but as I don't run Windows I can't verify the details.
6  Bitcoin / Mining / Cacti template for AMD GPU monitoring on: October 18, 2011, 06:13:39 AM
By leveraging my earlier work exposing GPU stats via SNMP, I created a Cacti template for monitoring my mining rigs and would like to share my work with all of you.

Here are some teaser graphs from one of my (largely untuned) 6990 GPUs:

Adding graphs to Cacti


Core clock for GPU 0


Memory clock for GPU 0 (underclocked to 150MHz)


Core voltage for GPU 0


Fan speed for GPU 0


Temperature for GPU 0


Load for GPU 0



Prerequisites

Installation instructions
  • Grab the latest template package from here.
  • Unzip the package and copy snmp_queries/amd.gpu.xml to your snmp_queries directory i.e. /var/www/html/cacti/resource/snmp_queries
  • Import cacti_data_query_amd_gpu.xml from the Cacti web interface.
  • Add the 'AMD GPU' Data Query to your miner host or host template.
  • 'Create Graphs for this Host' as you would normally.

Troubleshooting
  • Ensure that the host's SNMP Timeout value is set adequately long (e.g. >5 seconds) as the polling cycle for a host can be quite long.

A Verbose Query should look like the following:
Code:
+ Running data query [16].
+ Found type = '3' [snmp query].
+ Found data query XML file at '/var/www/html/cacti/resource/snmp_queries/amd_gpu.xml'
+ XML file parsed ok.
+ Executing SNMP walk for list of indexes @ '.1.3.6.1.4.1.8072.1.3.2.4.1.2.5.103.112.117.105.100'
+ Index found at OID: '.1.3.6.1.4.1.8072.1.3.2.4.1.2.5.103.112.117.105.100.1' value: '0'
+ Index found at OID: '.1.3.6.1.4.1.8072.1.3.2.4.1.2.5.103.112.117.105.100.2' value: '1'
+ Index found at OID: '.1.3.6.1.4.1.8072.1.3.2.4.1.2.5.103.112.117.105.100.3' value: '2'
+ Index found at OID: '.1.3.6.1.4.1.8072.1.3.2.4.1.2.5.103.112.117.105.100.4' value: '3'
+ Located input field 'gpuId' [walk]
+ Executing SNMP walk for data @ '.1.3.6.1.4.1.8072.1.3.2.4.1.2.5.103.112.117.105.100'
+ Found item [gpuId='0'] index: 1 [from value]
+ Found item [gpuId='1'] index: 2 [from value]
+ Found item [gpuId='2'] index: 3 [from value]
+ Found item [gpuId='3'] index: 4 [from value]
+ Located input field 'gpuAddress' [walk]
+ Executing SNMP walk for data @ '.1.3.6.1.4.1.8072.1.3.2.4.1.2.10.103.112.117.97.100.100.114.101.115.115'
+ Found item [gpuAddress='03:00.0'] index: 1 [from value]
+ Found item [gpuAddress='04:00.0'] index: 2 [from value]
+ Found item [gpuAddress='07:00.0'] index: 3 [from value]
+ Found item [gpuAddress='08:00.0'] index: 4 [from value]
+ Located input field 'gpuDescription' [walk]
+ Executing SNMP walk for data @ '.1.3.6.1.4.1.8072.1.3.2.4.1.2.14.103.112.117.100.101.115.99.114.105.112.116.105.111.110'
+ Found item [gpuDescription='AMD Radeon HD 6900 Series'] index: 1 [from value]
+ Found item [gpuDescription='AMD Radeon HD 6900 Series'] index: 2 [from value]
+ Found item [gpuDescription='AMD Radeon HD 6900 Series'] index: 3 [from value]
+ Found item [gpuDescription='AMD Radeon HD 6900 Series'] index: 4 [from value]
+ Found data query XML file at '/var/www/html/cacti/resource/snmp_queries/amd_gpu.xml'
+ Found data query XML file at '/var/www/html/cacti/resource/snmp_queries/amd_gpu.xml'
+ Found data query XML file at '/var/www/html/cacti/resource/snmp_queries/amd_gpu.xml'
...

Have fun!
7  Bitcoin / Mining / Monitoring AMD GPUs with SNMP in Linux on: October 18, 2011, 12:22:51 AM
Hi folks,

I'm a big fan of monitoring system performance with SNMP and when it came to mining I didn't find much out there that satisfied my requirements, so I decided to put something together and share with you all. The following describes how to monitor a Linux-based host with any number of ATI GPUs:

Prerequesites
  • Linux host (makes use of aticonfig and POSIX signalling)
  • Perl
  • AMD drivers
  • All installed GPUs detected and operational
  • All GPUs must have support for PPLIB.
  • Net-snmp installed and operational


Installation instructions
  • Grab the latest script from here.
  • Install this script somewhere net-snmp can execute it (e.g. /usr/local/bin).
  • Edit the following lines in the script as appropriate for your environment:
Code:
########################################################
## Tweak the following variables for your environment
#
my $sudo = "sudo -u jintu";           # The sudo command to execute
my $aticonfig = "/usr/bin/aticonfig"; # The full path to aticonfig
my $display = "DISPLAY=:0";           # The display your X session and ATI GPUs are running under
#
  • Edit snmpd.conf (mine is in /etc/snmp) to include the following lines (edit the path as appropriate):
Code:
# These are multi-line output visible from NET-SNMP-EXTEND-MIB::nsExtendOutLine
extend  gputemp         /usr/local/bin/gpu_snmp.pl temp
extend  gpuload         /usr/local/bin/gpu_snmp.pl load
extend  gpuclock        /usr/local/bin/gpu_snmp.pl clock
extend  gpumemory       /usr/local/bin/gpu_snmp.pl memory
extend  gpuvcore        /usr/local/bin/gpu_snmp.pl vcore
extend  gpufan          /usr/local/bin/gpu_snmp.pl fan
extend  gpuid           /usr/local/bin/gpu_snmp.pl id
extend  gpuaddress      /usr/local/bin/gpu_snmp.pl address
extend  gpudescription  /usr/local/bin/gpu_snmp.pl description
#
  • Test with snmpwalk e.g. 'snmpwalk -v2c -cpublic localhost NET-SNMP-EXTEND-MIB::nsExtendOutLine' which should output something like the following from my dual 6990 rig:
Code:
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpuid".1 = STRING: 0
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpuid".2 = STRING: 1
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpuid".3 = STRING: 2
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpuid".4 = STRING: 3
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpufan".1 = STRING: 85
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpufan".2 = STRING: 85
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpufan".3 = STRING: 85
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpufan".4 = STRING: 85
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpuload".1 = STRING: 78
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpuload".2 = STRING: 91
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpuload".3 = STRING: 94
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpuload".4 = STRING: 98
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gputemp".1 = STRING: 7350
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gputemp".2 = STRING: 7400
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gputemp".3 = STRING: 7450
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gputemp".4 = STRING: 7550
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpuclock".1 = STRING: 500
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpuclock".2 = STRING: 500
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpuclock".3 = STRING: 515
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpuclock".4 = STRING: 505
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpuvcore".1 = STRING: 1000
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpuvcore".2 = STRING: 1000
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpuvcore".3 = STRING: 1050
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpuvcore".4 = STRING: 1050
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpumemory".1 = STRING: 150
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpumemory".2 = STRING: 150
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpumemory".3 = STRING: 150
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpumemory".4 = STRING: 150
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpuaddress".1 = STRING: 03:00.0
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpuaddress".2 = STRING: 04:00.0
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpuaddress".3 = STRING: 07:00.0
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpuaddress".4 = STRING: 08:00.0
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpudescription".1 = STRING: AMD Radeon HD 6900 Series
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpudescription".2 = STRING: AMD Radeon HD 6900 Series
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpudescription".3 = STRING: AMD Radeon HD 6900 Series
NET-SNMP-EXTEND-MIB::nsExtendOutLine."gpudescription".4 = STRING: AMD Radeon HD 6900 Series



Troubleshooting
  • If you see "sudo: sorry, you must have a tty to run sudo" when executing the script via snmpd, comment out the following line in your sudoers file:
Code:
"Default requiretty"


    Wire up to your NMS as you see fit. For reference, I have posted my Cacti template utilizing these stats here.

    Have fun!
    8  Bitcoin / Pools / Cacti monitoring/stats graphing template for mining pools on: June 27, 2011, 09:44:45 PM
    Hi folks,

    I wanted to share my work on a Cacti template for monitoring mining pools (BTC Guild and Slush are currently supported). The templates (and included scripts) leverage the mining pool's JSON feeds to generate reasonably pretty graphs for the health of your account, worker (miner) performance and overall pool performance (if the pool supports this). With Cacti's PIA and the THold plugin you could take this further and define alert thresholds to notify you of a change if anything falls out of tolerance.

    Unlike some of the pool monitoring services out there, this is entirely free. However, if you feel so inclined, donations are much appreciated and help encourage the development of additional features and support for more pools.  With a little effort, you too can set up your own monitor to keep an eye on all your miners and the pools they use using these templates.

    Here are a few teaser graphs from my miners:



    Slush's Pool

    User Rewards


    Worker Hash Rate (OpenCL)


    Worker Hash Rate (Total all workers)


    Worker Last Share (OpenCL)


    Worker Last Share (Total all workers)


    Worker Score (OpenCL)


    Worker Score (Total all workers)


    Worker Shares (OpenCL)


    Worker Shares (Total all workers)






    BTC Guild

    Difficulty


    Difficulty (NMC)


    Pool PPS Rate


    Pool PPS Rate (NMC)


    Pool Speed


    24 Hour Rewards


    24 Hour Rewards (NMC)


    Paid Rewards


    Paid Rewards (NMC)


    Total Rewards


    Total Rewards (NMC)


    Unpaid Rewards


    Unpaid Rewards (NMC)


    Worker Hash Rate


    Worker Last Share


    Worker Shares


    Worker Shares (NMC)


    Worker Shares Since Reset


    Worker Shares Since Reset



    Revision History
    • v0.07 5/8/2012
      Major rework for comprehensive support of the new BTC Guild PPS API and simplification of the script. Required nearly all related Cacti templates to be reworked as well. Added NMC stats. Removed Pool stats as there is no API support by BTCGuild for pool stats anymore.  At the time of writing, BTC Guild only allows one API connection per 60 seconds, so memcached is essentially required now.
    • v0.06 10/24/2011
      Initial support of BTC Guild following their move to PPS. Worker Cumulative Total, Worker Last Share, Worker Reset Shares and Worker Total are not currently working properly and more work is needed to correct this.
    • 7/18/2011
      Removed pool and worker round stats for BTC Guild as these are no longer supported in the API.
    • v0.05 7/14/2011
      Added 24 hour totals now that this has been added to the BTC Guild JSON. Minor bugfix to not blow up when we "never" in last_share responses. Added Worker Last Share.
    • v0.04 7/6/2011
      Added support for Slush's pool. Minor bugfixes for worker indexing in BTC Guild script after the addition of worker totals. Added more specific memcached namespace to allow multiple accounts to be monitored from the same Cacti instance sharing memcached. Added simple check for when the API JSON gives us null.
    • v0.03 7/4/2011
      Added total all workers (sum of all workers) to script as this is lacking in the API JSON. Added the following graph templates: Worker Reset, Worker Cumulative Total, Blocks Found and Payouts.
    • v0.02 6/29/2011
      Added simple JSON caching via memcached resulting in big performance boost:
        Before -> SYSTEM STATS: Time:114.1648 Method:spine Processes:2 Threads:4 Hosts:12 HostsPerProcess:6 DataSources:159 RRDsProcessed:105
        After  -> SYSTEM STATS: Time:19.5116 Method:spine Processes:2 Threads:4 Hosts:12 HostsPerProcess:6 DataSources:159 RRDsProcessed:105
    • v0.01 6/28/2011
      First working version.  No JSON query caching support (Slow!).
    Pages: [1]
    Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!