I don't get the same result. When I mine solo against the standard client (RPC only, no long polling) memory fills up.
Hmm, thats weird, look at my memory graph, most of it is slush and at the end is arsbitcoin   Maybe there is some other difference between those pools that triggers this, oh well...  |
|
|
|
If someone could load it up in pdb and figure out what datastructure is doing it, I could probably fix it.
I would start with the RPC code, including the modified Twisted.web library. I run my miners through MMP, and I usually run them for weeks at a time with >100,000 accepted shares between restarts. I don't see any performance problems or memory leaks running with MMP. Hi, I think it could be related to longpolling. For example when I mine on slush (rpc only) it works fine for days, as soon as I mine on a pool that uses longpolling it starts to fill the memory. It happens on arsbitcoin and btcguild in my case. |
|
|
|
Hi there  Uhmm I noticed that your pool has been added to this bithopper programm... It says in the config file that this pool uses a broken scoring algorithm :/ Should we worry about that? One main reason I am mining here is, that I was thinking the score based system would protect somewhat from the pool hoppers. On the other hand the pool is pretty big, so the effect they have on the rest of the pool is probably very small. Still worries me a bit. |
|
|
|
Yes, there are multiple ways to do it. I use collectd with an exec plugin that grabs gpu load and so on and display it with a php frontend (its called collectd graph panel 0.3) Others use munin http://forum.bitcoin.org/index.php?topic=10233.0Then there is rug-monitor: http://forum.bitcoin.org/index.php?topic=10214There are probably even more that I never heard of If you are running windows, then I don't know. All these things above depend on the command "aticonfig" to get the needed data. |
|
|
|
You could try to add a & at the end of the commands, that makes it start in the background, seems to do the trick on my ubuntu netbook So gnome-terminal --title gpu.overclock --command "sh /home/corelinux1/gpu.overclock.sh"
becomes gnome-terminal --title gpu.overclock --command "sh /home/corelinux1/gpu.overclock.sh" &
and so on. |
|
|
|
|
I am just guessing, but the "No protocol specified" sounds like it comes from the Xserver?
I am collecting some infos with collectd and I had to export Xauthority too, like
export XAUTHORITY=/home/USER_LOGGED_INTO_X_AND_IS_MINING/.Xauthority
But my script runs as the same user which is running the miners.
If you run this as a different user you could try "xauth merge /home/USER_LOGGED_INTO_X_AND_IS_MINING/.Xauthority"
and then the export stuff after that. Or you can play around with xhost and allow localhost for everything or something like that.
Greetings
nnn
|
|
|
|
Hey, am I the only one having some problems on this pool? Get some miner is idle once in a while. Is longpolling broken or something? Have a lot of rejects after LP Push, see: [11/07/2011 07:31:57] LP: New work pushed
[11/07/2011 07:32:09] Warning: work queue empty, miner is idle
[11/07/2011 07:32:12] Result: 98e9f4be rejected
[11/07/2011 07:32:12] Result: 1f885fed rejected
[11/07/2011 07:32:12] Result: ee558687 rejected
[11/07/2011 07:32:13] Result: 13e77eec rejected
[11/07/2011 08:10:46] LP: New work pushed
[11/07/2011 08:10:55] Result: 78353884 rejected
[11/07/2011 08:10:58] Result: 9510d9f5 rejected
[11/07/2011 08:11:01] Result: 4dc4d6fe rejected
[11/07/2011 08:11:04] Result: f039908e rejected
[11/07/2011 08:11:04] Result: 7d7d58ec rejected
[11/07/2011 08:11:04] Result: 8d6ba15d rejected
[11/07/2011 08:11:08] Result: acd6240e accepted
|
|
|
|
Yes, Ive flashed it with an Asus bios (Its XFX) and a stock XFX bios. Both complete successfully, but the card refuses to allow windows to boot. I think as soon as it begins to initialize something in the card makes everything lock up.
Lol this may sound retarded, but... have you tried to put it in the oven? LOL a lot of people seem to have success putting defective gpus in the oven for a short time. That sometimes fixes it and the card works again. Its worth a try if its defective anyway. Google gpu oven if you don't believe me  Works also with motherboards, recently fixed a motherboard with a defective pcie slot, put it in the oven at 190 Celsius for 7 minutes, works again (I shielded the plastic parts with aluminium foil) |
|
|
|
Hi there, I never cloned a install like that, but recently installed a Slackware straight to usbdrive, which took some afterwork to play nice. Basicly, if you have say one big ext4 partition on the usb drive and all your files are in there with the right permissions, you "only" need to make it bootable imo I would try something like this, give the partition on the usbstick a LABEL (sometimes devices can be sda or sdb on usbboot, so its good to use a LABEL or UUID so everthing runs smooth) tune2fs -L USBROOT /dev/sdb1 (asuming sdb1 is the partition on your usbstick) #verify your label with blkid mkdir /mnt/usbroot mount /dev/sdb1 /mnt/usbroot mount -o bind /dev /mnt/usbroot/dev mount -o bind /proc /mnt/usbroot/proc mount -o bind /sys /mnt/usbroot/sys #chroot into the usbstick chroot /mnt/usbroot modify /etc/fstab so that the rootpartition points to your LABEL, looks like that for me: LABEL=USBROOT / ext4 defaults,noatime 1 1 One important thing, for usbbooting you need to set a delay, so the kernel has some time to find the usb devices while booting, add rootdelay=7 to the default boot options in /etc/default/grub (sometimes you need longer delay, try 10 if 7 is not working) # install grub grub-install /dev/sdb (make sure this is your usbstick) update-grub cross fingers and try to boot No guarantee, just wrote this down from my head, but maybe it works . |
|
|
|
Hello I understand setting: to but where do I get the hashrate data from? It's not explained in the readme. I know I would set it in: by replacing Off with the source of the file, but I need more info on which file has the hashrates or how to get the hashrates to log to a file. I assume the same thing would be needed to get shares? There is a patch included for phoenix miner, which enables logging to a file. Or get the patch here https://raw.github.com/disq/bitcoin-rug-monitor/master/logtotext-1.48.diffIt says 1.48 but works on 1.50 too. After you patched phoenix with that you can add something like this to the commandline which starts phoenix miner "-t /tmp/miner.log". That is the file you give as status_file in the config. |
|
|
|
Someone said with 11.6 you can overclock past the bios limits on Linux? Is this true?
Yes its true, was running 975/300 yesterday but desktop freezes if I watch tv with kaffeine now running on 925/300. SDK 2.1 helps alot
I run 900/300
with 2.4 i get 335-340 with 2.1 i get 350+
SDK 2.4 with phoenix and option -k phatk works also good, my other machine is doing 359 Mhash with that. |
|
|
|
If you are at the black window, try ALT+F7 that should switch you back to the X Server (If it is still alive that is) If not I would login on the ALT+F1 terminal and check if the X server is still running, maybe do a ps axu and look for a program called X or do a pgrep X or so, you could also check some logs dmesg cat /var/log/syslog cat /var/log/messages etc etc... maybe there is info what is happening. !!! carefull on my sapphire 5850 that turns the fan completly off !!! not sure wtf that is...
but "theoretical" it should work like this to set it back into auto mode
DISPLAY=:0.0 aticonfig --pplib-cmd "set fanspeed 0 auto"After thinking about it, better don't try to set it back to auto this way, you can do it with a tool called AMDOverDriveCtrl, go to the Tab Fanspeed and then click default. |
|
|
|
I am not running suse, but I would check if the needed enviroment variables for the SDK are set. If they are not set you need to add something like this to your .bashrc or whatever shell you use: (This is for 64bit, you have to adjust this for a 32bit system) export AMDAPPSDKROOT=/path/to/your/AMD-APP-SDK-v2.4-lnx64
export AMDAPPSDKSAMPLEROOT=/path/to/your/AMD-APP-SDK-v2.4-lnx64
export LD_LIBRARY_PATH=$AMDAPPSDKROOT/lib/x86_64:
Not sure what the AMDAPPSDKROOT is for, the most important thing is that LD_LIBRARY_PATH contains the sdk path. |
|
|
|
weird, I see this too. But they point to different blockexplorer addresses, and one shows no such block.  Something else: Is there still ddos attacks going on? because sometimes my miners stop for a moment with workque empty. I am not sure if this is maybe my internet connection. |
|
|
|
Oh noes, I think your bitcoind just died or something  MSG: Call to bitcoind failed: [Errno socket error] [Errno 111] Connection refused MSG: Backend is not connected! |
|
|
|
Nice timeline. I hadn't read about that big BTC transaction minutes before the MtGox shutdown yet.
I agree! I was also unaware of the 432077.76654321 BTC transaction. Kinda strange that if you read the digits backwards you get a '12345667' sequence. Could that just be a fluke? On this show which just ended from onlyonetv, the MT Gox guy said they did this transaction to move the bitcoins to a secure wallet, and that only maybe something like 200 coins got lost. Lets hope this is true... |
|
|
|
Hi, I have never done it, but maybe you need to shortcut some pins look here http://blog.zorinaq.com/?e=42, then scroll down until it says: Shorting Pins for "Presence Detection" If it works you can send the BTC here: 1E3kex71ozqWdWuzKfemMJPDJhpdSKHmSw  |
|
|
|
Hard to say what the problem could be. I would double check that the files in /etc/OpenCL exists (they get extracted there when you accept the sdk license) ls -l /etc/OpenCL/vendors/
total 8
-r--r--r-- 1 user user 15 Jan 27 04:13 amdocl32.icd
-r--r--r-- 1 user user 15 Jan 27 04:13 amdocl64.icd
if in doubt, just do another cd /; tar xzf /opt/AMD-APP-SDK-v2.4-lnx64/icd-registration.tgz
Also on linuxcoin I had problems with the miners in /opt/miners, so I copied my directory with the miners from my desktop to /home/user And if you start your miners in a SCREEN session, you have to add something to .screenrc setenv LD_LIBRARY_PATH "/opt/AMD-APP-SDK-v2.4-lnx64/lib/x86_64/:/opt/ati-stream-sdk-v2.1-lnx64/lib/x86_64/"
setenv DISPLAY ":0"
Maybe one of that helps |
|
|
|
|
Show Posts
