Holy crap, I've been wasting my time!
*Quits bitcoin mining*
I just threw mine in the trash. So glad someone told me before I wasted more electricity! * ckolivas stalks outside crazyates' house and intercepts his trash
|
|
|
All useful debugging is much appreciated, thanks.
|
|
|
Hack their arses to make them hash as much as they possibly can while their hashrate is still meaningful.
|
|
|
I keep getting an error that says:
cgminer.exe has stopped working
what can I do to remedy this? and is there an auto-restart button/option somewhere?
|
|
|
Hello I am mining multiple GPUs in Scrypt, and I was wondering if it is possible, to change the temperature reading, instead of use the GPU CORE temperature, use the GPU VRM one in cgminer. The reason is, in scrypt the problem is not the GPU core, but the VRM which is usually 10 to 15 degrees above GPU, sometimes more. Since cgminer regulates temperature based on GPU CORE temp, when it is could outside, the fan PWM goes very low, and the VRM temp goes very very high. ex: now I have 52 core (18C ambient), but VRM is at 83 (C), and the fan PWM is still at 20%, because core temp is low. I could solve it to use minimum PWM 50% in the config, but I prefer not to stress the fans if isn't necessary. The only way I know to read VRM temp is with GPU-Z under windows (I use xubuntu 12.04) can this be done? because aticonfig --odgt only gives GPU CORE temp. thanks Indkt. No
|
|
|
Not at the moment, no. I'm surprised people are putting mining hardware behind proxies now that it's all gone custom hardware to be honest...
|
|
|
All proxy support was disabled for stratum from 3.2.0 onwards to work around bugs from using libcurl which was making the proxy connections.
|
|
|
I am sorry to report that 3.4.1 is still exhibiting the mswsock.dll crashes I reported earlier "That mining software which we dare not speak it's name" has been running solid in my testing on another rig that experienced the same crashes under 3.4.1 Usual story, try a debug build with instructions from http://ck.kolivas.org/apps/cgminer/debug/and check your antivirus software is happy with the DLL (other soft may not use the same dll).
|
|
|
I've been unable to get any cgminer version after 3.3.1 to start on Win7 x64, using the pre-built binaries. I get the message "Error opening terminal: dumb"
3.3.1 works fine with identical configuration, but I'd rather not be stuck on an old version.
Unrelated to cgminer. Google for it, seems to be related to some windows environment variable with various solutions offered. Thanks. Out of curiosity, any idea why it only effects more recent versions? The way we output to the console changed ever so slightly so perhaps it's related and the variable is relevant now?
|
|
|
BFLSC users, I just tracked down a bug which would lead to a crash. I've just committed a fix for it to git, and will release a hotfix release soon.
|
|
|
I've been unable to get any cgminer version after 3.3.1 to start on Win7 x64, using the pre-built binaries. I get the message "Error opening terminal: dumb"
3.3.1 works fine with identical configuration, but I'd rather not be stuck on an old version.
Unrelated to cgminer. Google for it, seems to be related to some windows environment variable with various solutions offered.
|
|
|
Having a problem running 3.4.1 from cgminer-3.4.1-x86_64-built.tar.bz2: cat /etc/issue Ubuntu 12.04.2 LTS \n \l
dpkg -l | grep libudev ii libgudev-1.0-0 1:175-0ubuntu9.4 GObject-based wrapper library for libudev ii libudev-dev 175-0ubuntu9.4 udev library (development files) ii libudev0 175-0ubuntu9.4 udev library
cgminer-nogpu: error while loading shared libraries: libudev.so.1: cannot open shared object file: No such file or directory
Alas it's built for ubuntu 13.04 so you'll have to build it yourself since it looks like your ubuntu has only udev0 and not udev1.
|
|
|
Latest cgminer does not use or support the -S command. That was removed a long time ago. But you DO NEED TO READ ASIC-README on how to set up the driver for the erupter to work.
|
|
|
CGMiner seems to be randomly closing. I'm running cgminer-nogpu on Win 8x64 with a BFL Little Single and 2 AMUs. It runs in a batch file that loops, and the batch file keeps restarting it, so it is closing nicely, and I haven't lost any downtime. I think it's done it about 4-5 times since I updated to 3.4.0, which was about 8 days ago? The newest one was this morning, after I had left for work. It had been running for about 2 days solid before that.
It never did this before. The AMUs are pretty new. Is it the AMUs causing it, or upgrading to 3.4.0, or both?
Hard to know without excluding one thing at a time? Try running the AMUs in their own instance and see if one the other or both crashes? Also there are debug builds which would help me find out where it's crashing and fix it. http://ck.kolivas.org/apps/cgminer/debug/I ran 2 instances of CGMiner-nogpu like you suggested, one with 2 SC Single (1x 30GH + 1x 60GH), and one with 2 AMUs. The instance with the 2 BFL miners was the one that crashed. I didn't see it happened, as it was about 45 minutes ago, but again my batch file seems to have restarted it. I'll try 3.4.1 and see if anything changed. It won't debug anything unless you install the debugger as described in the debug readme in there. Anyway see how you go with 3.4.1, I found a few places that could lead to crashes that I fixed in that version. I will also update the debug binaries to be 3.4.1 3.4.1 did the same thing: it just restarted by itself. I saw it hit 1million shares around 2am, and then it seems it restarted itself at 8:15am. I'll download the debug builds when the site is back up. Darn, well the site is back up and I just uploaded the new debug builds for 3.4.1.
|
|
|
ck.kolivas.org - still down?
7 hours to go.
|
|
|
ck.kolivas.org is down :/ mirror needed Again, to repeat. Opening post, mirror of files.
|
|
|
My miner is having a fairly annoying problem and I have no idea of the reason or solution. Every couple hours, I get [2013-08-31 13:54:18] Attempting to restart cgminer 3.4.0 in the log, then the miner slows down to around 1/5th of it's usual speed, the fans start randomly changing speeds, almost no work is produced, and cgminer becomes nearly unresponsive in some cases. What is going on? I don't see any errors being produced, nothing's overheating. It just randomly 'attempts to restart' and then stops working right. The only thing that could do that is a message to restart, either via the menu or being told via the API.
|
|
|
With the latest cgminer (3.4.1) Windows build, the SOCKS proxy option does not work and is probably broken. I've setup a local proxy via PuTTY (localhost:9999), and have tried --socks-proxy 127.0.0.1:9999, --socks-proxy localhost:9999, and --socks-proxy socks5://127.0.0.1:9999, to no avail. I verified that it did not work via Wireshark, which found packets being received and transmitted directly to the pool's IP. Using (pooler's) cpuminer with the proxy option --proxy socks5://127.0.0.1:9999 works perfectly, with Wireshark not detecting any packets sent to the pool's IP.
Again: Proxies do not work with stratum on cgminer due to me using raw socket code for reliability. You need to use something like proxifier.
|
|
|
Slush's document stipulated that it should refresh at least every 60 seconds. If it's much longer than that, since you're dealing with raw sockets that can quietly die, there is no way for the miner software to know if the socket has disappeared, so cgminer uses 90 seconds between messages to say the pool has died so you cannot increase it to much more. Updating it more frequently includes newer transactions but requires more refreshes on your mining software, and vice versa.
|
|
|
|