make sure it's the "linux" version. otherwise, you're getting a neutered version with a shitty cpu + low ram.
Yeah, he got the right device. There's OpenWRT too, another great distro. |
|
|
|
Don't do it. I have a sli watercooled 6990s and its been nothing but problems. Running water and electronics non stop is not a good combination!
Buy the nonconductive coolant then. Garbage. Distilled water is non-conductive (or more correctly has very low electrical conductivity). Lots of horror stories of all that wonder goop breaking down inside waterblocks and destroying radiators. DAT, I targeted that piece of advice at a guy apparently having issues with his WC installation. Distilled water rocks but if you have even a minor leakage, it will pick up dirt and the conductivity rises fast. In this context, going with chemical coolants might not be that bad an idea, huh? I'm not advocating that stuff over good-old water for general use, neither am I not trying to change your opinion. I'm trying to find an optimal solution to a specific problem so that a newb operator doesn't burn his rig down. You're right though - if the installation finally proves watertight and runs without problems, you can easily replace the chemicals with water. |
|
|
|
Tell me then why I don't have any cpu usage with even 12 intensity with 2.1, but have all up to 100% on one core (with 1 gpu miner) with all other sdk's? It's the same bug.
If you posted your driver version, OS and GPU config someone could try to unravel your issue but this is hardly the appropriate thread. Proof by counter-example: a lot of miners moved to 11.11 or 11.12 driver and reported no CPU-hogging issues. Therefore, the major CPU-hogging flaw has been fixed. Computers and operating systems are inherently very complex subjects and great many things can go wrong. Unexpected combinations of drivers, SDKs and system libraries can still peg the CPU but it's luckily relatively uncommon. Mixing x64 and x86 code can not only be a real pain but also result in undefined behavior. EDIT:: Con, latest git works like a charm  The GPU order has changed on my Debian machines, though. EDIT:: Another donation is due as soon as my wallet recuperates. |
|
|
|
This is the infamous cpu bug.
No it's bloody damned not. THE cpu bug would eat a whole core no matter what intensity/aggression you'd chosen. It was caused by AMD's driver fuck-up and has since been fixed. There have been some OS-specific CPU hogging issues, eg with Ubuntu. Do the research first and don't post misleading and try not to post inaccurate information, k? Intensity higher than 9 is only supposed to be used with 79xx cards. |
|
|
|
I lost 77 BTC that day and it has made me much more cautious.
It would seem your (obviously lacking in error control) backup script made you develop a cavalier attitude toward the wallet file. Ever heard of doing off-site backups? Also, what the hell? Unless you changed it, there should be a pool of 100 unused keys in your wallet. How were you able to run out of key-pool with so many "recent backups"? Something just doesn't add up here. |
|
|
|
when using anything above intensity 9 on my 5970 w/ 11.12 drivers. The cpu usage is pegged... 9 and below cpu usage is 0%
Any reason why its higher on I 10+? thanks
You are only supposed to use 10+ with the new 79xx cards. I'm positive Con mentioned that somewhere around here. |
|
|
|
... I won the auction on Michael Schumachers Benetton F1 oil radiator...
Good for you P4  Don't do it. I have a sli watercooled 6990s and its been nothing but problems. Running water and electronics non stop is not a good combination!
Buy the nonconductive coolant then. |
|
|
|
|
I find the idea of banning CPU miners from pools appealing.
CPU mining is not even supported by default in the newest versions of cgminer... no good reason why pools shouldn't drop CPU-mining support in their own best interest.
The fact that such an approach would hit botnet overlords with a ricochet just adds more value to the idea.
|
|
|
|
... Somehow last good config = BSOD. I had no flash drives to reinstall windows so I said frak it. Thanks AMD+windows. Great ending.
I reckon you did manage to log into windows prior to the BSOD? The "Last good config" registry value gets overwritten on each successfully finished boot, hence is of limited use. Then again, Windows itself is of limited use  |
|
|
|
...Can we get a re-post of those facepalms please?
Ask and you shall receive.  root@haerdalis::/home/jake# /opt/bcm/cgminer-testing/cgminer [2012-01-29 13:48:56] Started cgminer 2.2.0
WARNING: All config files need .conf: /etc/modprobe.d/00local, it will be ignored in a future release.
FATAL: Module nvidia not found.
*** glibc detected *** /opt/bcm/cgminer-testing: realloc(): invalid old size: 0xbfa81ce8 ***
======= Backtrace: =========
/lib/i686/cmov/libc.so.6(+0x6b381)[0xb75b7381]
/lib/i686/cmov/libc.so.6(+0x70aad)[0xb75bcaad]
/lib/i686/cmov/libc.so.6(realloc+0xdd)[0xb75bcd8d]
/opt/bcm/cgminer-testing[0x80590ad]
/usr/lib/libcurl-gnutls.so.4(Curl_client_write+0x198)[0xb770e6e8]
/usr/lib/libcurl-gnutls.so.4(Curl_readwrite+0x12c0)[0xb7721b00]
/usr/lib/libcurl-gnutls.so.4(+0x29f1b)[0xb7721f1b]
/usr/lib/libcurl-gnutls.so.4(curl_easy_perform+0x43)[0xb7722d93]
/opt/bcm/cgminer-testing[0x805a1db]
/opt/bcm/cgminer-testing[0x80509d2]
/opt/bcm/cgminer-testing[0x80566a8]
/lib/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0xb7562ca6]
/opt/bcm/cgminer-testing[0x804ad01]
======= Memory map: ========
...
Latest git tends to die a miserable death, Con. The previous build i reported testing some 12 hours ago works just fine. |
|
|
|
Doc, I'm loving that perk purchase page idea. Are you going to change the layout a bit to resemble Fallout's interface? Those good-old days of 2D games are never coming back :tries to hold back tears, to no great success: |
|
|
|
Hey, Holliday, I removed some sting from my previous post. Apparently, unlockable CPUs and GPUs were hitting AMD's revenue to a greater extent than expected. A bloody shame what AMD have done but they have been haunted by constant financial issues (which are the main reason AMD sold out all their fabs) and need every penny of that revenue badly  BTW, the 6950 chips aren't all perfectly good - any chip with shader defects is down-graded to 6950 status if at least 1408 shaders are in fine working order. |
|
|
|
Use the past tense when necessary Holliday. The operative word is could. The same gpu core chips are being used for both 6950 versions and the 1GB version used to be just as unlockable. Since your article was published, AMD decided to laser-cut the inactive shaders in the 6950 chips instead of disabling them in the bios (the transition was made in 2011Q2 IIRC). On a similar note, all new AMD CPUs that may have had unlockable cores are getting the same "special treatment". Any 6950 may be unlockable if it's using the old core revision from before the change but those chips are extremely scarce now. I'd like to make this fact painfully clear: AMD uses the same chips for 6970 and 6950 cards, only with some shaders disabled in the case of the weaker model. Those shaders could be re-enabled by flashing the bios. Unfortunately for the users, the internal policies at AMD were changed and now the shaders on chips sold as 6950 are being laser-cut. There's no going around that. |
|
|
|
|
Acknowledged and thank you. Testing latest git version right now.
|
|
|
|
Nice workaround but give how crappy 2.5 is I see no reason to keep it...
Dependency hell, DAT. 2.6 is extremely crappy but necessary for running 7xxx cards. 2.5 and 2.4 are less crappy and required for 69xx cards. 2.1 is the best SDK version unless you limnit yourself to VLIW5 architecture cards. What miners should really do is organize their GPUs in groups by required SDK version. Mixing VLIW4 and VLIW5 cards is a waste of hash rate, adding GCN to the bunch - a criminal waste |
|
|
|
No need to remove anything. Just copy the 2.1 SDK libraries into cgminer's directory and you're done! You need the following files: amdocl.dll
amdoclcl.dll
OpenCL.dll
A reboot might be necessary if Windows doesn't want to unload the previously-used 2.5 SDK libraries from memory. |
|
|
|
|
Nifty set-up, Catfish.
The only question I have is, why bother with lxde at all if you're going to manage the rig via ssh?
Run the X server manually and just disable the desktop manager.
If you ever need desktop access (why?) just re-enable lxde and you're done.
Make sure you have enabled all the CPU-related powers saving options in the BIOS and that you have cpufrequtils installed - the CPU should throttle all inactive cores to 800MHz cutting down power usage and heat significantly.
Any bios-flashed ASUS 6950 DCII 1GB-s? Have you been able to drop the voltages or memory speeds?
|
|
|
|
Yes, it will obviously be faster.
Shut up jCole, no trolling!  Your post has been reported. The additional RAM is of no significance at all for mining, damn it! In fact, more memory means higher energy use and temperatures. Your mining speed will ultimately only be affected by how far you feel comfortable overclocking the card. |
|
|
|
Of course it is. Add those to your config file: "intensity" : "9,9,8,9",
"vectors" : "2",
"worksize" : "64", Intensity is the same as Aggression in phoenix nomanclature. With cgminer you are use a per-card value as shown in the example code. Don't use values hight than 9 unless using a 7970 card. You don't need to specify BFI_INT, it's on by default. Also, RTFM - that info is in the readme file and in the very first post of this thread. |
|
|
|
|
No. Let him rot in oblivion.
I don't feel we need more silliness than we already get.
|
|
|
|
|
Show Posts
