Bitcoin Forum
February 26, 2024, 07:59:12 AM *
News: Latest Bitcoin Core release: 26.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Bitcoin / Development & Technical Discussion / [Request] Bandwidth limits on: September 22, 2011, 04:09:13 AM

I would like to limit the bandwidth usage of the client. I have a bitcoin daemon running all the time to support mining, but on occasion it uploads large chunks of data to other clients. This causes my latency to spike in online games which is irritating. A pair of programmable bandwidth caps (upload/download) would lessen the impact of distributing the block chain during gaming sessions.
2  Bitcoin / Bitcoin Discussion / What are You buying with bitcoins? on: September 19, 2011, 02:42:39 AM

I'd do a poll, but that limits the options to my imagination.
3  Bitcoin / Mining software (miners) / Automatic temperature/clock speed control on: August 01, 2011, 10:26:09 PM
Since my miners run unattended in unconditioned space I need to insure they don't get too hot and shutdown (or burn out), so I wrote this script (derived in small part from gputempmon.sh by myrond) to automatically lower the clock if the chip gets too hot, or raise the clock if it is below the maximum frequency.

Code:
#!/bin/bash
#version 0.01

TARGETTEMP=88
MAXCLOCK=940
MINCLOCK=500

# Get number of adapters
export DISPLAY=:0
num=`aticonfig --adapter=all --odgt | grep Temperature | wc | awk -- '{ print $1 }'`

# Set all adapters to maximum fan speed
for (( i=0; i<$num; i++ )) do
    export DISPLAY=:0.$i
    aticonfig --od-enable
    aticonfig --adapter=$i --pplib-cmd "set fanspeed 0 99"
done

#
while true; do
    sleep 10
    clear
    date

    for (( i=0; i<$num; i++ )) do
        export DISPLAY=:0.$i

        # Collect current clock speed/temperature
        curtemp=`aticonfig --adapter=$i --odgt | grep "Sensor 0:" | tr -s ' ' | cut -f 6 -d ' ' | cut -f 1 -d '.'`
        curclk=`aticonfig --adapter=$i --odgc | grep "Current Clocks"|tr -s ' '|cut -f 5 -d ' '`

# Status
echo "Adapter $i clock:${curclk}, Temp:${curtemp}C"
        # Lower clock if too hot, raise clock if to slow
        if [ "$curtemp" -gt "$TARGETTEMP" ]; then
            echo "Adapter $i is overheating, slowing it down"
            let "curclk -= 1"
            aticonfig --adapter=$i --odsc=$curclk,0 > /dev/null
        elif [ "$curtemp" -eq "$TARGETTEMP" ]; then
   echo "Adapter $i at target temp"
        elif [ "$curclk" -lt "$MINCLOCK" ]; then
            echo "Adapter $i is idle"
        elif [ "$curclk" -lt "$MAXCLOCK" ]; then
            echo "Adapter $i can run faster, speeding it up"
            let "curclk += 1"
            aticonfig --adapter=$i --odsc=$curclk,0 > /dev/null
        else
   echo "Adapter $i at maximum clock"
        fi
    done
done

A new version that allows different speeds/temps/enables for adapters (only lightly tested):

Code:
#!/bin/bash
#version 0.03

# The parentheses make these variables into arrays
# The arrays will be padded with the last value in each line
ENABLE=(1 0)
TARGETTEMP=(88)
MAXCLOCK=(940 940)

# Get number of adapters
export DISPLAY=:0
num=`aticonfig --adapter=all --odgt | grep Temperature | wc | awk -- '{ print $1 }'`

# Find the last element in each array, then pad to the number of adapters
i=0
for tmp in ${ENABLE[@]} ; do
    let "i += 1"
done
for (( j=i; j<$num; j++ )) do
    ENABLE[j]=$tmp
done
i=0
for tmp in ${TARGETTEMP[@]} ; do
    let "i += 1"
done
for (( j=i; j<$num; j++ )) do
    TARGETTEMP[j]=$tmp
done
i=0
for tmp in ${MAXCLOCK[@]} ; do
    let "i += 1"
done
for (( j=i; j<$num; j++ )) do
    MAXCLOCK[j]=$tmp
done

# Set all adapters to maximum clock speed
for (( i=0; i<$num; i++ )) do
    if [ "${ENABLE[i]}" -eq "1" ]; then
        export DISPLAY=:0.$i
        aticonfig --od-enable
        aticonfig --adapter=$i --pplib-cmd "set fanspeed 0 99"
    fi
done

#
while true; do
    sleep 10
    clear
    date

    for (( i=0; i<$num; i++ )) do
        if [ "${ENABLE[i]}" -eq "1" ]; then
            export DISPLAY=:0.$i

            # Collect current clock speed/temperature
            curtemp=`aticonfig --adapter=$i --odgt | grep "Sensor 0:" | tr -s ' ' | cut -f 6 -d ' ' | cut -f 1 -d '.'`
            curclk=`aticonfig --adapter=$i --odgc | grep "Current Clocks"|tr -s ' '|cut -f 5 -d ' '`

    # Status
    echo "Adapter $i clock:${curclk}, Temp:${curtemp}C"
            # Lower clock if too hot, raise clock if to slow
            if [ "$curtemp" -gt "${TARGETTEMP[i]}" ]; then
                echo "Adapter $i is overheating, slowing it down"
                let "curclk -= 1"
                aticonfig --adapter=$i --odsc=$curclk,0 > /dev/null
            elif [ "$curtemp" -eq "${TARGETTEMP[i]}" ]; then
        echo "Adapter $i at target temp"
            elif [ "$curclk" -lt "500" ]; then
                echo "Adapter $i is idle"
            elif [ "$curclk" -lt "${MAXCLOCK[i]}" ]; then
                echo "Adapter $i can run faster, speeding it up"
                let "curclk += 1"
                aticonfig --adapter=$i --odsc=$curclk,0 > /dev/null
            else
        echo "Adapter $i at maximum clock"
            fi
        fi
    done
done
Edit: Added idle detection to stop adjusting clock when slowed down
4  Bitcoin / Mining support / Redundant Bitcoin clients on: July 20, 2011, 10:47:48 PM

I have two mining machines both pointing at a third machine running the Bitcoin client. This gives a single point of failure.

I am going to run the Bitcoin client on each of the mining machines and have all the mining clients working locally.

My question is should I use the same wallet on both mining machines? Or is the risk of search for the same nonce pretty high since the generate transaction is identical. It seems to me the two machines would get out of sync pretty quickly and the only chance to re-sync would be after a new block was pushed. With this method I can monitor both miners from a single bitcoin client located anywhere (on my smartphone for example)

The other option is to have separate wallets on each miner, but that requires connecting to each machine to see the status.

5  Bitcoin / Mining software (miners) / GUIMiner on remote system, displaying on local host? on: July 09, 2011, 02:01:26 AM
I want to run GUIminer on a remote computer and have the display show up on my local system.

I have two systems: monitor and miner, both running Ubuntu and latest AMD SDK

I ssh to miner and run:

Code:
DISPLAY=:0 python guiminer.py

GUIminer puts the display on miner.

I ssh to miner and run:

Code:
DISPLAY=monitor:0 python guiminer.py

GUIminer shows up on monitor, but the opencl list only shows the processor, not the video cards.

Is there any way to separate them? I'm not adverse to hacking on guiminer, but I don't know where to begin.

Sorry, wrong forum. Diablo move it to the correct one please....
6  Other / Beginners & Help / What's the deal with block 133233? on: June 26, 2011, 01:33:28 AM

Bunch of 48K+ plus transactions with small amounts (~10) being split off. Is that normal? If I have a large sum in my wallet and I give somebody 10 coins does it go into the block as 50K from key X (mine) ---> 49,990 to key Y (mine) and 10 to key Z (somebody else?)

For reference:
http://blockexplorer.com/block/0000000000000464742a8d6147c4ef3a0d41658f643d624555a1cfa9c80aa0f3
7  Other / Beginners & Help / [SOLVED] aticonfig: This program must be run as root when no X server is active on: June 25, 2011, 08:42:18 PM

If you want to run your farm headless, and manage it through SSH, you will soon discover the dreaded: "aticonfig: This program must be run as root when no X server is active" or "ERROR - X needs to be running to perform ATI Overdrive(TM) commands" error messages.

To monitor temperatures (or any other aticonfig command) you need the following:

Code:
user@farm:~$ export DISPLAY=:0
user@farm:~$ xhost +
access control disabled, clients can connect from any host
user@farm:~$ aticonfig --adapter=all --odgt

Adapter 0 - AMD Radeon HD 6900 Series
            Sensor 0: Temperature - 90.00 C

Adapter 1 - AMD Radeon HD 6900 Series
            Sensor 0: Temperature - 103.00 C
user@farm:~$

Note, you can use any of the aticonfig commands to tweak clock settings or whatever.

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!