Oh hey two things;
1, anytime i try to save a .conf file, It saves, Looks all good to go, But always goes "failed to load json configuration file<--or something simmilar
2, I've heard that you can put the .dll's from older SDK's somewhere in/near the CGminer folder, And then CGminer will use them, AKA 12.1 SDK 2.6 With 12.1 SDK 2.4 performance
Where do i put the dlls? (i know wich ones)
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 705. (Read 5805728 times)
January 13, 2012, 09:57:06 PM
January 13, 2012, 09:46:24 PM
HW is hardware errors. Your card is producing nothing but garbage and not a single share so you're pushing them too hard.
XD yeah, I was failing when i posted that... Ima delete that old one.. Just for the record. (and lol shame on me for this)i accedentally set the core and mem in viseversa, While at the same time, I wanted to see how much "lag" i got when running a game with CGminer at i3.
So.. 450core 1000mem. LOL=Epic lag on everything, And i thought it was just the miner, the crashing? Yeah, Lol t'was also due to my failure of the clocks+bench+mine
January 13, 2012, 09:44:52 PM
couple of comments..
1. take them off crossfire if you can
2. back the clocks off a little bit. (I run 6870's at 940, only that high because that is stock)
3. I dont see any accepted shares, only HW (isn't that hardware failures?
4. 83 seems like a high temp
5. 100% fan? how long do you plan on that fan working?
I don't run anything over 930 engine core, you can get a higher hash rate, fut for how long? and how stable?
1. gaming
2. they are stable at 1015core
3. LOL yeah.. Thats screwy i didnt notice that, Heres a better example, Thanks for pointing that out.
4. Yeaaahhhh it is...
5. Well. It's usually not at 100%, CGminer's been the first miner to raise my temps, The card has two fans, And a fan Atop of it pulling the heat out, Overnight, It drops to 80%
Heres a new line of what im getting (lol) since i blatently failed last time
Code:
cgminer version 2.1.2 - Started: [2012-01-13 18:37:07]
--------------------------------------------------------------------------------
(5s):634.2 (avg):632.2 Mh/s | Q:113 A:106 R:0 HW:0 E:94% U:8.52/m
TQ: 1 ST: 1 SS: 0 DW: 0 NB: 1 LW: 0 GF: 0 RF: 0
Connected to http://pit.deepbit.net:8332 with LP as user *************
Block: 000004bffbab40b456b696ab01b35521... Started: [18:37:07]
--------------------------------------------------------------------------------
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: 83.0C 100% | 317.2/315.9Mh/s | A:56 R:0 HW:0 U: 4.50/m I: 3
GPU 1: 80.0C 98% | 317.5/316.9Mh/s | A:50 R:0 HW:0 U: 4.02/m I: 3
--------------------------------------------------------------------------------
[2012-01-13 18:48:21] Accepted 00000000.fe653916.f311515d GPU 1 thread 3
[2012-01-13 18:48:44] Accepted 00000000.0bb0dcde.011fc6b5 GPU 1 thread 1
[2012-01-13 18:48:53] Accepted 00000000.e9ee5129.fc2e4fa1 GPU 0 thread 2
[2012-01-13 18:48:54] Accepted 00000000.24c13e33.6b273e3e GPU 0 thread 0
[2012-01-13 18:49:04] Accepted 00000000.8b072a29.c9074be6 GPU 0 thread 0
[2012-01-13 18:49:05] Accepted 00000000.0ef976ef.4aa64a0b GPU 1 thread 3
[2012-01-13 18:49:12] Accepted 00000000.62474031.80218b4f GPU 0 thread 0
[2012-01-13 18:49:16] Accepted 00000000.e7bb8d12.ad5f7181 GPU 1 thread 3
[2012-01-13 18:49:22] Accepted 00000000.d00eef91.5ea25a64 GPU 1 thread 1
[2012-01-13 18:49:24] Accepted 00000000.d970a4e3.19742876 GPU 0 thread 2
[2012-01-13 18:49:35] Accepted 00000000.f838815a.95ffee8c GPU 1 thread 1
[2012-01-13 18:49:35] Accepted 00000000.4dad1c63.87a47724 GPU 1 thread 3
January 13, 2012, 09:41:39 PM
HW is hardware errors. Your card is producing nothing but garbage and not a single share so you're pushing them too hard.
January 13, 2012, 08:50:41 PM
3. I dont see any accepted shares, only HW (isn't that hardware failures?
4. 83 seems like a high temp
5. 100% fan? how long do you plan on that fan working?
4. 83 seems like a high temp
5. 100% fan? how long do you plan on that fan working?
Yeah he is killing that card.
Quote
U:0.00/m
You produced absolutely no value for the entire time you were mining. 83C, 100% fan, 100% hardware failure rate. A HW of anything other than 0 should be a massive WARNING WARNING WARNING GPU DESTRUCTION IN PROGRESS!Drop the clocks back to stock, set fan @ 75%. Temps should be in the 50C to 60C. Start from there. Find best intensity (try each for at least 30 min to get a good average). Drop memclock down and then start overclocking slow.
January 13, 2012, 08:34:39 PM
couple of comments..
1. take them off crossfire if you can
2. back the clocks off a little bit. (I run 6870's at 940, only that high because that is stock)
3. I dont see any accepted shares, only HW (isn't that hardware failures?
4. 83 seems like a high temp
5. 100% fan? how long do you plan on that fan working?
I don't run anything over 930 engine core, you can get a higher hash rate, fut for how long? and how stable?
January 13, 2012, 06:29:20 PM
Back to the RPC stuff:
being able to switch a pool, or change a gpu engine clock are really the only commands I need. I would gladly pay 5 btc if these two features made it to the trunk.
Jim
https://bitcointalksearch.org/topic/m.689228
But yeah - state exactly what you want with those 2 commands and once the CPU changes happen I'll put those 2 on first priority (for 5 BTC
January 13, 2012, 11:17:14 AM
Back to the RPC stuff:
being able to switch a pool, or change a gpu engine clock are really the only commands I need. I would gladly pay 5 btc if these two features made it to the trunk.
Jim
January 13, 2012, 10:40:38 AM
You're assuming that people with questionable morals/ethics are obvious based on their behavior on message boards.
An aside: this reminds me of the business with the Reiser file system in Linux, written by the convicted murderer Hans Reiser
Good stuff but not universally adopted partly due to the "ick factor" with the man himself.
The axe murderer comment was not coincidence, given the history of Hans and linux An aside: this reminds me of the business with the Reiser file system in Linux, written by the convicted murderer Hans Reiser
Good stuff but not universally adopted partly due to the "ick factor" with the man himself.
In fact his code never got incorporated because it had too many problems. It had nothing to do with him being a murderer. Once he was convicted, though, all the people working on his project slowly all walked away one by one, thus leaving the code to rot.
January 13, 2012, 10:38:40 AM
You're assuming that people with questionable morals/ethics are obvious based on their behavior on message boards.
An aside: this reminds me of the business with the Reiser file system in Linux, written by the convicted murderer Hans Reiser
Good stuff but not universally adopted partly due to the "ick factor" with the man himself.
An aside: this reminds me of the business with the Reiser file system in Linux, written by the convicted murderer Hans Reiser
Good stuff but not universally adopted partly due to the "ick factor" with the man himself.
January 13, 2012, 10:38:02 AM
I judge all code by the code's merit. If it's GPL compliant and good code, then even if it's from an axe murderer, I'll take it. I have thought about this long and hard in the past. Read Rusty's take on it:
http://rusty.ozlabs.org/?p=196
http://rusty.ozlabs.org/?p=196
Thanks for the link.
“If you didn’t run code written by assholes, your machine wouldn’t boot”
LOLZ!
January 13, 2012, 10:37:13 AM
people should be wary then, and other developers should double check his work in bitcoin if they already havent.
You cant have people with very suspect morals, writing code that deals with money. Anywhere else dealing with anything like bitcoin, he would have had to go through a background check and send his fingerprints to the fed. Most likely he would have failed said background check during the psychological profile.
dude whatYou cant have people with very suspect morals, writing code that deals with money. Anywhere else dealing with anything like bitcoin, he would have had to go through a background check and send his fingerprints to the fed. Most likely he would have failed said background check during the psychological profile.
If the code is verified and read through by other competent devleopers, it doesn't matter who wrote it initially. For all we know Satoshi himself could be some evil guy, but because the code is open source, it was verified many times over by other developers to be safe and working.
January 13, 2012, 10:34:17 AM
people should be wary then, and other developers should double check his work in bitcoin if they already havent.
You cant have people with very suspect morals, writing code that deals with money. Anywhere else dealing with anything like bitcoin, he would have had to go through a background check and send his fingerprints to the fed. Most likely he would have failed said background check during the psychological profile.
You cant have people with very suspect morals, writing code that deals with money. Anywhere else dealing with anything like bitcoin, he would have had to go through a background check and send his fingerprints to the fed. Most likely he would have failed said background check during the psychological profile.
January 13, 2012, 10:33:27 AM
I judge all code by the code's merit. If it's GPL compliant and good code, then even if it's from an axe murderer, I'll take it. I have thought about this long and hard in the past. Read Rusty's take on it:
http://rusty.ozlabs.org/?p=196
http://rusty.ozlabs.org/?p=196
January 13, 2012, 09:50:42 AM
Well actually it's up to ckolivas
Though I will say that Luke didn't bother to do the api.c changes in his FPGA pull ... that's slack.
Though I will say that Luke didn't bother to do the api.c changes in his FPGA pull ... that's slack.
January 13, 2012, 09:23:13 AM
Although most of us do not agree with many of Luke's positions and actions, it is obvious from inspecting his code that he is a capable coder. If you wish to boycott anything that he has touched, then you can stop using Bitcoin - he has committed several fixes/improvements etc to it.
January 13, 2012, 09:04:33 AM
YES, let him fork his own project and call it DOOSH-JR-MINER, but PLEASE do not allow any of his contributions to make into the master repository.
Why. I haven't tested them yet but the code looks useful. The 0.4% improvement code is a rather mundane bug fix. Should we intentionally keep a bug in cgminer because we don't like the author? Does that make the community better somehow?
January 13, 2012, 08:53:51 AM
He has indicated that reverse engineering is lawful and an acceptable method of moving forward, so please take this into consideration when reviewing his patches and do everything you possibly can to MAKE THEM YOUR OWN so that his reputation doesn't leave any marks on this great project.
Reverse engineering is lawful. Granted that right has been severly (and IMHO wrongly) degraded by provisions in DMCA but there is nothing wrong with reverse engineering.
Often when products or protocols are abandoned the ONLY way forward to new sustainable code is via reverse engineering. Linux simply wouldn't exist without reverse engineering. Before companies began to support it most drivers were created from reverse engineering.
I left the person of your attack out of the quote and response because it is off-topic but I felt I couldn't leave this perception unchallenged.
Also in a GPL project there is no such thing as MAKE THEM YOUR OWN. If you want your own fork that makes fart sounds everytime a block is found you can pull it right now. The license gives you the right and that right can never be taken away.
I should have clarified a bit.....so thank you for reminding me to post again.
YES, let him fork his own project and call it DOOSH-JR-MINER, but PLEASE do not allow any of his contributions to make into the master repository.
January 13, 2012, 08:49:02 AM
He has indicated that reverse engineering is lawful and an acceptable method of moving forward, so please take this into consideration when reviewing his patches and do everything you possibly can to MAKE THEM YOUR OWN so that his reputation doesn't leave any marks on this great project.
Reverse engineering is lawful. Granted that right has been severly (and IMHO wrongly) degraded by provisions in DMCA but there is nothing wrong with reverse engineering.
Often when products or protocols are abandoned the ONLY way forward to new sustainable code is via reverse engineering. Linux simply wouldn't exist without reverse engineering. Before companies began to support it most drivers were created from reverse engineering.
I left the person of your attack out of the quote and response because it is off-topic but I felt I couldn't leave this perception unchallenged.
Also in a GPL project there is no such thing as MAKE THEM YOUR OWN. If you want your own fork that makes fart sounds everytime a block is found you can pull it right now. The license gives you the right and that right can never be taken away.
January 13, 2012, 08:48:16 AM
Thanks for doing this work. It will take me some time to review these patches as they're fairly large and I'm relatively low on cycles for anything more than a cursory glance at the moment.
Please do not allow Luke-Jr to become associated with CGMiner in any way. Frankly, he is nothing more than a stain on the community as a whole and if his past actions are any indication, you would be opening the door for him to create more havoc in the project than it is worth.
He has indicated that reverse engineering is lawful and an acceptable method of moving forward, so please take this into consideration when reviewing his patches and do everything you possibly can to MAKE THEM YOUR OWN so that his reputation doesn't leave any marks on this great project.
Your avatar SUX, but hey I guess freedom of speech, right
?Dia
Jump to: