 |
May 17, 2013, 12:26:01 AM |
|
Right now I have three mining rigs, and for a while all three were working fine. However I had to reboot my server that is also functioning as a mining rig, and little was I aware that since I had last rebooted it, Ubuntu (which was set to security only updates) since went through multiple kernel revisions and dkms driver revisions (and strangely enough, these "security" updates to these kernels often seem to break support for my ZFS modules.) When it came back up, that mining node (running cgminer) never came up with it.
cgminer was indicating for every single share that there is a hardware and the nonce was invalid. I know for a fact that this isn't a hardware problem, because I installed steam and ran a game to make sure that everything was working as it should. No glitches or anything, game renders perfectly. I went through the song and dance of repeatedly clearing and reinstalling drivers, trying different ones, etc, and the result was always the same. I also tried using bfgminer instead - same problem. I tried using catalyst 11.11 as is often suggested elsewhere, and that particular driver won't even install (I think maybe it is incompatible with kernel 3.7?)
I've tried updating the APP SDK to 2.8 by the way, problem still exists.
Now, I've been looking all over the place for methods of resolving the hardware nonce issue, and both here and elsewhere most of these issues are old, and I can't tell if there is some kind of game changer about the 3.7 kernel, or the newer catalyst drivers. On one of my mining rigs, I did have problems with cgminer crashing when used with a newer catalyst driver, I had to downgrade to I think an 11 series driver before it would run at all. Apparently the cause of this is due to 5xxx and 6xxx cards not working correctly with cgminer if using the newer drivers, and going to an old one fixes it.
If this also applies to linux, then how would I get this to work? It will be a major pain in the butt to roll back every single driver and other whatnot that upgraded along with that kernel just to use an older version of the catalyst driver, so I'm hoping to avoid that if I can. Anybody have any other ideas? Again, with everything in its current state, games actually run correctly. So other than for bitcoin mining, the graphics driver is behaving exactly as its supposed to. And again, this problem happens in both cgminer and bfgminer with APP SDK 2.8 installed. (By the way, is there any way to determine whether these miners are actually using that one or are using their own compiled in one?)
|
