I have xxx GPU's and have tried Every single miner that is publicly available.
CGMINER is BY FAR the best mining software in my opinion.
CGMINER is BY FAR the best mining software in my opinion.
^^^
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 776. (Read 5805728 times)
September 12, 2011, 10:29:46 AM
^^^
September 12, 2011, 07:43:40 AM
Internet won't die on me (a 4 to 5 nines improbable
event given where my miners are connected).
This is what I'm spending my next chunk of mined
BTC on:
http://www.avocent.com/Products/Category/Power_Distribution_Units/Direct_PDU.aspx
I might consider one of those if I ever get serious about this. Here's a really good deal on one, open box: http://underbid.com/merchant/tfloutlet/product/762-18218/DPDU201-001/Avocent_DirectPDU_DPDU201001_8Port_Zero_U_Vertical_Rackmount_PDU_230_V_8_x_IEC_60320_C13_C13R_Out_-_Open_Box_-_Like_New.html?ref=base
September 12, 2011, 07:18:11 AM
Quote from: mmortal03 link=topic=28402.msg518224#msg518224
Oddly enough, after some restarts and system updates, it seems to now be overclocking it over the ViDock. I can't say why, but I'm happy.
Is this with the new v2.0.2? Some changes I made to it should help set things even though it thinks it has failed now.No, it still can't do what msi afterburner does, nor can it outdo the 125 difference limit on 6970s.
Nope, it was with 2.0.0. It's the craziest thing, because now it's working just fine. I've since updated to 2.0.2, and it's still running great. The only changes that I had made that I'm aware of before it started working for me were to some power settings, along with running some Windows Updates, and then a restart. I'll let you know if I ever run into it again.
So, I have to say, this is really awesome, running a 5870 off of a netbook, being able to overclock the GPU and underclock its memory fully. With this setup I'm only needing around 230-240 watts to run the rig in its entirety, and my hashing rate peaks at around 440 MHashes! This keeps me profitable for at least a few more months, versus when I was running it off of a desktop.
Mind you, this type of setup loses its advantage if you want to scale up to multiple cards, but at least it's the most optimal for running a single card.Anyway, a donation is coming your way as soon as I get my next payouts!
September 12, 2011, 06:31:18 AM
As amazing as cgminer is, the "no monitoring required" comment
isn't entirely accurate (yet). You still need monitoring external to
the mining rig to catch system freezes: as much as Con did to try
and restart GPU's, there are situations where nothing short of a cold
reboot will get things back on track, and to catch those, you need
an external prober.
Also, cgminer doesn't yet have a way to shoot you an email or an
SMS like a full-on monitoring system would
You could always auto restart your system every certain number of hours to try to keep any system crash symptoms from building up, but even with that, sometimes you'll get blue screens, and the OS can't restart itself at the scheduled time. I guess you could have something like a DRAC installed on your rig to hard restart it from another computer if it stops responding. Besides that, there's always the problem of your Internet connection going down and you having no failover, but that's kind of a worst case scenario.
September 12, 2011, 04:37:27 AM
Suggestion:
--on-dead ~/dead.sh
When cgminer detects a card is dead, executes specified parameter.
useful eg.
or
--on-dead ~/dead.sh
When cgminer detects a card is dead, executes specified parameter.
useful eg.
Code:
#!/bin/bash
echo "Failed card" | mail [email protected]
shutdown -r now
or
Code:
kill cgminer
cgminer -c config.json
September 11, 2011, 11:52:41 PM
You do realize its easy to get banned, right? Take my advice, shut the fuck up.
You do realize its easy to not act like a responsible moderator on these forums, right? Take my advice, resign as moderator.
September 11, 2011, 09:23:47 PM
That may or may not be correct. I don't follow the windows stuff that closely.
September 11, 2011, 09:20:46 PM
None of the initialisation code for the GPUs actually changed between 2.0 and 2.0.2. You are getting stung by random windows fuckage (this bug seems confined to windows) where you may have to restart it multiple times to get it working because it fails to build the kernels. You just happened to be lucky on the 2.0 release. However you are also in luck as there is a way around if it you already had it working in an earlier version. Copy any files from your 2.0.0 directory that have names ending in .bin into your 2.0.2 directory and try again.
Yep, that worked. How far into the future will that carry me you think?I'll keep that in mind.
I'm currently using Catalyst 11.6, I saw your comment that 11.8 is actually better for Windoze, why is that?
Thanks again,
Sam
September 11, 2011, 07:53:58 PM
None of the initialisation code for the GPUs actually changed between 2.0 and 2.0.2. You are getting stung by random windows fuckage (this bug seems confined to windows) where you may have to restart it multiple times to get it working because it fails to build the kernels. You just happened to be lucky on the 2.0 release. However you are also in luck as there is a way around if it you already had it working in an earlier version. Copy any files from your 2.0.0 directory that have names ending in .bin into your 2.0.2 directory and try again.
Yep, that worked. How far into the future will that carry me you think? September 11, 2011, 07:51:51 PM
I just tried 2.0.2 and got the same error that I had with 2.0.1 which is as follows
---------------------------------------------
[2011-09-11 10:14:20] Failed to init GPU thread 0, disabling device 0
[2011-09-11 10:14:20] The most common reason for this failure is cgminer being u
nable to read the kernel .cl files
[2011-09-11 10:14:20] Alternatively if it has failed on different GPUs, restarti
ng might help.
Press enter to continue:
---------------------------------------------
When I try to restart either GPU it crash's. When I press Q to quit the program it also crash's.
I'm back to using 2.0.0 again.
Sam
None of the initialisation code for the GPUs actually changed between 2.0 and 2.0.2. You are getting stung by random windows fuckage (this bug seems confined to windows) where you may have to restart it multiple times to get it working because it fails to build the kernels. You just happened to be lucky on the 2.0 release. However you are also in luck as there is a way around if it you already had it working in an earlier version. Copy any files from your 2.0.0 directory that have names ending in .bin into your 2.0.2 directory and try again.---------------------------------------------
[2011-09-11 10:14:20] Failed to init GPU thread 0, disabling device 0
[2011-09-11 10:14:20] The most common reason for this failure is cgminer being u
nable to read the kernel .cl files
[2011-09-11 10:14:20] Alternatively if it has failed on different GPUs, restarti
ng might help.
Press enter to continue:
---------------------------------------------
When I try to restart either GPU it crash's. When I press Q to quit the program it also crash's.
I'm back to using 2.0.0 again.
Sam
Yep, that worked. How far into the future will that carry me you think?
Still crash's on exit.
Thanks for the workaround,
Sam
September 11, 2011, 06:31:29 PM
Avast antivirus this morning suddenly decided cgminer was malware and deleted it.
Just a heads up you might want to turn it off if you use it.
You do need to read the forum when your a noob ...Just a heads up you might want to turn it off if you use it.
This has been discussed already and happened a few weeks back.
The problem is that the Avast AV people are morons (same for a few other AV companies) and detect the valid code of cgminer.exe rather than the actual viral code of the trojan that uses it.
Thus Avast will allow that trojan to install anything but will only intercept it if it installs cgminer.exe ... see the problem there?
September 11, 2011, 05:11:51 PM
I just tried 2.0.2 and got the same error that I had with 2.0.1 which is as follows
---------------------------------------------
[2011-09-11 10:14:20] Failed to init GPU thread 0, disabling device 0
[2011-09-11 10:14:20] The most common reason for this failure is cgminer being u
nable to read the kernel .cl files
[2011-09-11 10:14:20] Alternatively if it has failed on different GPUs, restarti
ng might help.
Press enter to continue:
---------------------------------------------
When I try to restart either GPU it crash's. When I press Q to quit the program it also crash's.
I'm back to using 2.0.0 again.
Sam
None of the initialisation code for the GPUs actually changed between 2.0 and 2.0.2. You are getting stung by random windows fuckage (this bug seems confined to windows) where you may have to restart it multiple times to get it working because it fails to build the kernels. You just happened to be lucky on the 2.0 release. However you are also in luck as there is a way around if it you already had it working in an earlier version. Copy any files from your 2.0.0 directory that have names ending in .bin into your 2.0.2 directory and try again. ---------------------------------------------
[2011-09-11 10:14:20] Failed to init GPU thread 0, disabling device 0
[2011-09-11 10:14:20] The most common reason for this failure is cgminer being u
nable to read the kernel .cl files
[2011-09-11 10:14:20] Alternatively if it has failed on different GPUs, restarti
ng might help.
Press enter to continue:
---------------------------------------------
When I try to restart either GPU it crash's. When I press Q to quit the program it also crash's.
I'm back to using 2.0.0 again.
Sam
September 11, 2011, 02:03:33 PM
damn, this software sucks balls... guiminer FTW !!!!!
are you serious dude?
Guiminer is crap compared to cgminer
I have been mining since BTC was worth 0.85 USD
I have 10 GPU's and have tried Every single miner that is publicly available.
CGMINER is BY FAR the best mining software in my opinion.
September 11, 2011, 01:51:24 PM
damn, this software sucks balls... guiminer FTW !!!!!
guiminer is nothing compared to this....well, aside from noob-friendly.
September 11, 2011, 01:24:55 PM
damn, this software sucks balls... guiminer FTW !!!!!
September 11, 2011, 01:17:19 PM
(except I use none of the crappy tools you describe, especially not SNMP (ugh) )
)Well-well-well...
September 11, 2011, 12:44:22 PM
Avast antivirus this morning suddenly decided cgminer was malware and deleted it.
Just a heads up you might want to turn it off if you use it.
Just a heads up you might want to turn it off if you use it.
September 11, 2011, 10:31:29 AM
I just tried 2.0.2 and got the same error that I had with 2.0.1 which is as follows
---------------------------------------------
[2011-09-11 10:14:20] Failed to init GPU thread 0, disabling device 0
[2011-09-11 10:14:20] The most common reason for this failure is cgminer being u
nable to read the kernel .cl files
[2011-09-11 10:14:20] Alternatively if it has failed on different GPUs, restarti
ng might help.
Press enter to continue:
---------------------------------------------
When I try to restart either GPU it crash's. When I press Q to quit the program it also crash's.
I'm back to using 2.0.0 again.
Sam
---------------------------------------------
[2011-09-11 10:14:20] Failed to init GPU thread 0, disabling device 0
[2011-09-11 10:14:20] The most common reason for this failure is cgminer being u
nable to read the kernel .cl files
[2011-09-11 10:14:20] Alternatively if it has failed on different GPUs, restarti
ng might help.
Press enter to continue:
---------------------------------------------
When I try to restart either GPU it crash's. When I press Q to quit the program it also crash's.
I'm back to using 2.0.0 again.
Sam
September 11, 2011, 10:15:13 AM
RE: possible incorrect mem clock reading on ASUS directCU6870
Thanks for the feedback. I'd be very cautious of believing any other number than that one reported back by cgminer. There are different ways of querying the card that report back different values and cgminer is simply reporting back what the card says is its current running speed. On my 6970s it says the speed was set fine when I set it low, but then reports back at full memory speed. Looking at the temperature+fanspeeds confirms it is definitely running at the hotter 1375 (default).
interesting. GPU-Z reports mem temps (well I think its mem temp) so Ill play with the clocks and see if the temps move around enough to see what the clocks actually are.
Ill let ya know what I find - if I can figure it out that is, heh
EDIT hmm I doubt its mem temps its monitoring. crud.
September 11, 2011, 10:12:18 AM
Oh yeah, and also it needs an SNMP backend so that stats from the rigs can be aggregated into something like Zabbix or cacti + icinga. I see it: mining in the enterprise.
Jump to: