Show Posts
|
Pages: « 1 2 3 [4]
|
Thanks for the explanation. It would be nice if stats are delayed by a day or so in this pool, or a hopper unfriendly payment scheme could be implemented. Stats delaying is not effective anymore, there are other ways to detect pool's new blocks. So, when the block is generated by the pool, it is being broadcast over the network, i.e. to the poolhopper directly connected to the pool daemon. The poolhopper can determine that the block has been generated by the pool (and not relayed by the pool), if it haven't got the block from the other sources first.
|
|
|
I hesitate to use 2.1 SDK, because I want to use the computer during mining. I've noticed that the CPU usage increases gradually with miner agression: 0% of single core usage at Aggression 8; 268 MHash/s 0% at Aggression 9, but screen updates became laggy 12% at Aggression 10; 50% at Aggression 11 80% at Aggression 12 90% at Aggression 13; 273 MHash/s
|
|
|
Uninstall all ATI drivers and use Driver Sweeper in safe mode to clean the remains of your previous tests, which may prevent correct installation from MSI file (i.e. newer versions of OpenCL drivers). You can also search for these files manually in Windows directory. Then install 11.12 without SDK, and then SDK 11.2. For me it works fine on two PCs. And what miner do you use? I use Phoenix Miner with phatk kernel with .bat script like this (copy this command in script n times, where n is number of cards): start /AFFINITY [1,2,4,8...] /ABOVENORMAL phoenix -u http://USER:PASS@URL:PORT -k phatk BFI_INT FASTLOOP=false VECTORS AGGRESSION=8 WORKSIZE=256 DEVICE=[0,1,2,3...] PLATFORM=0
|
|
|
3 x 5830, C2D E6600
|
|
|
I've inspected c:\ATI\Support\11-2_vista_win7_64_ocl\ATIStreamSDK_dev.msi file with MSI Viewer and it looks like SDK v. 2.3
|
|
|
I have just observed that although current round stats are delayed for a few hours, information who solved the latest block is not delayed. It is all the poolhoppers need!
|
|
|
For purpose of this thread: to test if I can mine BTC and SC at the same time. And to get rich
|
|
|
I have assigned BTC miners to different CPU cores at increased priority to allow mining solidcoins on four CPU cores at the same time.
|
|
|
Thanks, but I am sure. This is a dedicated rig and usage is near 0% when it's not mining. It's been a while since I tried phoenix though, I'll give it another shot, but in the past phoenix made things worse as far as resources go.
My phoenix batch script goes like this: start /AFFINITY 4 /ABOVENORMAL phoenix -u http://USER1:PASS1@bitcoins.lc:8080/ -k phatk BFI_INT BITALIGN FASTLOOP=false VECTORS AGGRESSION=8 DEVICE=0 PLATFORM=0 WORKSIZE=256 start /AFFINITY 8 /ABOVENORMAL phoenix -u http://USER2:PASS2@bitcoins.lc:8080/ -k phatk BFI_INT BITALIGN FASTLOOP=false VECTORS AGGRESSION=8 DEVICE=1 PLATFORM=0 WORKSIZE=256
|
|
|
that will wear out one of your cores pretty quick, unless your script rotates the cores.
I don't overclock CPU and its cooling is sufficient (Scythe Mugen), so wearing the CPU out is not feasible. Besides, my point is to NOT load the cores in 100%, to save energy or increase profits by mining solidcoins !
|
|
|
To start your miners with Above Normal priority, use script with following commands to assign each miner to the different core:
start /AFFINITY x /ABOVENORMAL miner_command where x = 2core no. (i.e. 1,2,4,8 ...)
This way you can get rid of the fluctuations and even mine Solidcoins or Litecoins on all CPU cores and Bitcoins on GPUs.
@up Are you sure that the miners are responsible and not some other processes? I use Windows 7 x64 and phoenix miners and they have 1% CPU usage in the Task Manager. I have Intel C2Q 9450 + Asus Commando (p965) MoBo, Radeons 5850 and 5830.
|
|
|
Der Client will sich nur nicht compilieren lassen, da ihm eine lib fehlt, die unter debian nicht in den repros ist. /usr/include/db_cxx.h:59:22: fatal error: iostream.h: Datei oder Verzeichnis nicht gefunden Hat das jemand schon hinbekommen? --berndl In file makefile.unix add command: -DHAVE_CXX_STDHEADERS at the end of the line 13: DEFS=...
|
|
|
I have created a script for running bitcoind as a system service. http://forum.bitcoin.org/index.php?topic=16823.msg260914#msg260914Now I have my wallet.dat file stored on a secure root account in a Linux server. I'm normally working on an unprivileged account, and bitcoind starts with Linux and works unattended. It beats storing bitcoins on an unsecure Windows box for sure!
|
|
|
I wrote a script for starting bitcoind as a Linux system service (daemon) at computer start. You should put this script in /etc/rc.d/ directory (with permission to execute this script) and bitcoind in /usr/sbin/ Bitcoind will use root account, so create in ~root/.bitcoin/ directory file bitcoin.conf For example: rpcuser=USER rpcpassword=PASSWORD rpcport=8332 rpcallowip=*
Now you can start bitcoind using System Services application or by executing this script in /etc/rc.d/ Note that bitcoind becomes responsive about 15 seconds after start. Script bitcoins #!/bin/sh # # If you like this script, please donate 0.1 BTC to 19PpvogGn9AeavU7uvPrxfnxGJL3ZMBDni # # /etc/init.d/bitcoins # ### BEGIN INIT INFO # Provides: bitcoind # Required-Start: $local_fs $network # Required-Stop: $local_fs $network # Should-Start $named $time # Should-Stop $named $time # Default-Start: 3 5 # Default-Stop: 0 1 2 6 # Short-Description: Bitcoin daemon # Description: Bitcoin daemon ### END INIT INFO
BITCOIND="/usr/sbin/bitcoind" RUNLEVEL=`runlevel|cut -f2 -d' '`
function wait_for_daemon { # "Waiting for the server start." if [ $RUNLEVEL -eq 6 ] || [ $RUNLEVEL -lt 3 ]; then return 0 fi $BITCOIND getbalance >/dev/null while [ $? -gt 0 ]; do sleep 1 checkproc $BITCOIND if [ $? -gt 0 ]; then echo "Critical error: bitcoin daemon failure." return $? fi $BITCOIND getbalance >/dev/null done return 0 }
function wait_for_death { # waiting for daemon's death if [ $RUNLEVEL -eq 6 ] || [ $RUNLEVEL -lt 3 ]; then return 0 fi checkproc $BITCOIND while [ $? -eq 0 ]; do echo -n "." sleep 1 checkproc $BITCOIND done return 0 } . /etc/rc.status rc_reset
case "$1" in start*) checkproc $BITCOIND if [ $? -eq 0 ]; then echo "The bitcoin daemon has been already started - restart is unnecessary." $0 status else echo "Starting the bitcoin daemon." if [ ! -L /.bitcoin ]; then ln -s ~root/.bitcoin /.bitcoin fi startproc -s -u root -g root $BITCOIND rc_status -v fi ;; stop) checkproc $BITCOIND if [ $? -eq 0 ]; then echo "Stopping the bitcoin daemon:" if [ $RUNLEVEL -eq 6 ] || [ $RUNLEVEL -lt 3 ]; then $BITCOIND stop else wait_for_daemon $BITCOIND stop wait_for_death fi rc_status -v rm ~root/.bitcoin/.lock sync else echo "The bitcoin daemon has already been stopped or has not been started." $0 status fi ;; restart|reload) ## Stop the service and regardless of whether it was ## running or not, start it again. $0 stop $0 start
# Remember status and be quiet rc_status ;; status) echo -n "Status of the bitcoin daemon " checkproc -k $BITCOIND if [ $? -eq 0 ]; then rc_status -v else rc_status -u fi ;; info) echo "Info on the bitcoin daemon:" checkproc $BITCOIND if [ $? -eq 0 ]; then wait_for_daemon $BITCOIND getinfo rc_status -v else echo "The bitcoin daemon has not been started." $0 status fi ;; *) echo "Usage: $0 {start|restart|reload|stop|status|info}" exit 1 ;; esac rc_exit
|
|
|
My investigations shows that problem may be in driver version. When I was using Ubuntu 10.10 and NVidia 260.19.36, there are no problems - poclbm was using only 0-5 % Today I upgraded to Ubuntu 11.04 and fresh NVidia driver 270.41.19, and now poclbm (and phoenix too) are using up to 100% When I install old NVidia driver 260.19.36 on Ubuntu 11.04, poclbm is digging and "top" shows low cpu usage (0-5%), but unfortunately X server cannot starting complaining about "ABI version mismatch". Now I am on Ubuntu 11.04 with fresh driver, and also seeking for better solution... Maybe I'll have to go back to Ubuntu 10.10. EDIT: videocard is - nVidia Corporation GT215 [GeForce GT 240] (rev a2) ~20.000 khash/s IMHO this problem is caused by the OpenCL implementation in the driver, I am testing the RPC miner (CUDA) under Windows 7 and it works fine, with very small CPU usage (< 1%) and 80% of the poclbm efficiency (43 vs 55 mhash/s). I have tested also the OpenCL version of the RPC miner, and the tests were inconclusive, it used 100% of one of the cores for a few minutes and repeatedly generated 0 khash/s, then crashed because of the memory allocation error. I have GTX 275 and C2Q 9450 @ 2,66 GHz.
|
|
|
|