I have confirmed this works on 5970s. Next would be the 6990s...
Yeah yeah, working on that ;-)
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 692. (Read 5805728 times)
January 24, 2012, 11:30:40 AM
I have confirmed this works on 5970s. Next would be the 6990s...
Yeah yeah, working on that ;-)
January 24, 2012, 09:49:15 AM
Well, after much poking and prodding and asking on forums and scouring APIs and lots of ridiculous documents, I can see there is no official way to tell that two GPUs on a dual GPU card belong to the same device. There is nothing shared between the two. However, having access to an actual device I was able to come u p with the following. This has been committed to the git tree:
Detect dual GPU cards via the indirect information of - 1st card has a fan controller. 2nd card does not have a fan controller, cards share the same device name, and are one bus ID apart. Use this information to create paired devices, displaying the fan speed on both devices and using the hottest temperature from either GPU to control the overall fanspeed.
I have confirmed this works on 5970s. Next would be the 6990s...
Now I better get some sleep
Detect dual GPU cards via the indirect information of - 1st card has a fan controller. 2nd card does not have a fan controller, cards share the same device name, and are one bus ID apart. Use this information to create paired devices, displaying the fan speed on both devices and using the hottest temperature from either GPU to control the overall fanspeed.
I have confirmed this works on 5970s. Next would be the 6990s...
Now I better get some sleep
ck, this could be problematic on windoz machines.... sometimes windows mixes up the order of the gpus. I know windoz is everyone's favorite whipping boy, but it is a necessary evil.
Code:
cgminer version 2.1.2 - Started: [1327278549] Rig: miner14
(5s):? (avg): 1723.83 Mh/s | Q:32805 A:52875 R:584 HW:0 E:?% U:23.21/m
TQ:? ST:137 SS:? DW:2095 NB:228 LW:94056 GF:29 RF:447
Connected to http://us.eclipsemc.com:8337 with LP as user ?
GPU 0: 74.5C | 361.1/360.0Mh/s | 800Mhz 1.05V A:11121 R:121 HW:0 U:4.88/m I: 7
GPU 1: 73.5C | 361.3/360.1Mh/s | 800Mhz 1.05V A:10746 R:125 HW:0 U:4.72/m I: 7
GPU 2: 73.5C 3498RPM 55% | 360.4/360.1Mh/s | 800Mhz 1.05V A:11168 R:127 HW:0 U:4.90/m I: 7
GPU 3: 74.0C 3695RPM 61% | 361.5/360.1Mh/s | 800Mhz 1.05V A:11098 R:134 HW:0 U:4.87/m I: 7
GPU 4: 66.5C 2666RPM 50% | 280.4/283.4Mh/s | 900Mhz 1.15V A:8742 R:77 HW:0 U:3.84/m I: 7
edit: to make matters worse. GPU 4: is actual in the 0 slot and has this monitor plugged into it... just the way windows sometimes loads the drivers..
January 24, 2012, 09:28:59 AM
Well, after much poking and prodding and asking on forums and scouring APIs and lots of ridiculous documents, I can see there is no official way to tell that two GPUs on a dual GPU card belong to the same device. There is nothing shared between the two. However, having access to an actual device I was able to come u p with the following. This has been committed to the git tree:
Detect dual GPU cards via the indirect information of - 1st card has a fan controller. 2nd card does not have a fan controller, cards share the same device name, and are one bus ID apart. Use this information to create paired devices, displaying the fan speed on both devices and using the hottest temperature from either GPU to control the overall fanspeed.
I have confirmed this works on 5970s. Next would be the 6990s...
Now I better get some sleep
Detect dual GPU cards via the indirect information of - 1st card has a fan controller. 2nd card does not have a fan controller, cards share the same device name, and are one bus ID apart. Use this information to create paired devices, displaying the fan speed on both devices and using the hottest temperature from either GPU to control the overall fanspeed.
I have confirmed this works on 5970s. Next would be the 6990s...
Now I better get some sleep
January 24, 2012, 08:37:17 AM
I'm running cgminer like this:
and here is the content of Desktop/p2pool.json:
as you can see I have set the donation amount to 0.5%, yet cgminer still says:
how come? Is the configuration file above not correct? I'm running cgminer 2.1.2.
Code:
cgminer -c Desktop/p2pool.json
and here is the content of Desktop/p2pool.json:
Code:
{
"pools" : [
{
"url" : "http://127.0.0.1:9332",
"user" : "nouser",
"pass" : "nopass1"
},
{
"url" : "http://arsbitcoin.com:8344",
"user" : "",
"pass" : "default"
}
],
"kernel" : "phatk",
"kernel-path" : "/usr/local/bin",
"worksize" : "256",
"vectors" : "2",
"intensity" : "6",
"donation" : "0.5"
}
as you can see I have set the donation amount to 0.5%, yet cgminer still says:
Code:
[2012-01-24 14:28:44] --donation is disabled, please consider just 0.5% :-(
how come? Is the configuration file above not correct? I'm running cgminer 2.1.2.
January 24, 2012, 06:15:48 AM
No problem, I'll see what I can see set up. Do you have a preference in Linux distro? ;-)
Thanks, ubuntu or debian are the likely culprits. January 24, 2012, 05:30:34 AM
Interested in remote access to a 6990 rig?
A quick prod would not hurt, but I expect I'll find the same thing. Of course I can only work with linux :sNo problem, I'll see what I can see set up. Do you have a preference in Linux distro? ;-)
January 24, 2012, 05:28:40 AM
Interested in remote access to a 6990 rig?
A quick prod would not hurt, but I expect I'll find the same thing. Of course I can only work with linux :s January 24, 2012, 05:26:57 AM
Just an update to tell you where the next version is up to. It's currently awaiting proper BFL support on windows, which Luke-jr is fighting with at the moment. While I'm waiting, I've been given access to a 5970 remotely and trying to find some way to massage the fan to work for both GPUs. So far it's been a miserable failure since everything simply shows the devices as discrete devices. Those willing to try a git tarball or build from git, the current tree is quite stable. 79xx GCN support is non-existent as of yet. Here is the changelog so far:
Interested in remote access to a 6990 rig?
January 24, 2012, 05:23:35 AM
This joke is getting old but what the hell...
lolwindows: reboot || reinstallation || defenestration
The REAL joke is that the above is actually quite a powerful troubleshooting guide for Redmond-based OS-s.
lolwindows: reboot || reinstallation || defenestration
The REAL joke is that the above is actually quite a powerful troubleshooting guide for Redmond-based OS-s.
Did posting that make your dingy bigger than the rest of the male population?
The real joke is people like you that keep putting up the same old diatribe.
The Windows 7 rig I am typing this response on right now, has been up for 27 days. The power went out or it would have been up longer. This installation has never had to be reinstalled since I first installed it 1 week prior to the official release date. This Windows 7 computer has never been infested with any malware or virus.
+1. Windows 7 rig has been up for multiple weeks.
January 24, 2012, 04:43:53 AM
I've just committed the first patch to the git tree that should enable 79xx cards to work properly under cgminer (delete any dodgy .bins created before this attempt). I have no idea if it performs even remotely well, but in theory at least, it won't behave stupidly as the current version does. If someone does run it, could you please dump the output of -D -T the first time you run it? Also it may be worth starting it with -v 1, and/or experiment with various combinations of -v and -w (default being -v 2 -w 128 if you set nothing).
January 23, 2012, 11:29:18 PM
7970 definitely needs >= 11.12 and sdk 2.6
Oh yes and the card is still as yet unsupported so xorg needs to be manually configured to allow an unsupported device. January 23, 2012, 10:14:06 PM
ckolivas , You have been busy. will be sending btc's your way also:
as for the 5970 fan issue, what I have done is set a minimum for fans ie: 50-85 that way if the first gpu is too cool, the fan will at least go 50 to keep the other cool.
as for the 79xx. do you want me to give you remote access ? only problem is that most of my rigs are linuxcoin, or windows 7
Yes there are definitely ways to keep the 5970 safe but it relies on user input.
Remote access would be great, provided it's some linux distribution that I can still install stuff into so that I may build software on it...
The only linux I have right now is linuxcoin. linuxcoin-v0.2-final
edit: i just thought of something.... the drivers on linuxcoin may not work with 7970 at all correct? so when you get to it, on my rig or your own, will I have to migrate to full ubuntu with updated drivers?
January 23, 2012, 09:54:38 PM
ckolivas , You have been busy. will be sending btc's your way also:
as for the 5970 fan issue, what I have done is set a minimum for fans ie: 50-85 that way if the first gpu is too cool, the fan will at least go 50 to keep the other cool.
as for the 79xx. do you want me to give you remote access ? only problem is that most of my rigs are linuxcoin, or windows 7
Yes there are definitely ways to keep the 5970 safe but it relies on user input.
Remote access would be great, provided it's some linux distribution that I can still install stuff into so that I may build software on it...
January 23, 2012, 09:27:56 PM
ckolivas , You have been busy. will be sending btc's your way also:
as for the 5970 fan issue, what I have done is set a minimum for fans ie: 50-85 that way if the first gpu is too cool, the fan will at least go 50 to keep the other cool.
as for the 79xx. do you want me to give you remote access ? only problem is that most of my rigs are linuxcoin, or windows 7
January 23, 2012, 09:07:58 PM
Just an update to tell you where the next version is up to. It's currently awaiting proper BFL support on windows, which Luke-jr is fighting with at the moment. While I'm waiting, I've been given access to a 5970 remotely and trying to find some way to massage the fan to work for both GPUs. So far it's been a miserable failure since everything simply shows the devices as discrete devices. Those willing to try a git tarball or build from git, the current tree is quite stable. 79xx GCN support is non-existent as of yet. Here is the changelog so far:
- Add API commands: config, switchpool, gpu settings, save
- Implement socks4 proxy support.
- Fix send() for JSON strings
- Introduce a --net-delay option which guarantees at least 250ms between any
networking requests to not overload slow routers.
- Generalise locking init code.
- Allow invalid values to be in the configuration file, just skipping over them
provided the rest of the file is valid JSON. This will allow older configurat
- Allow CPU mining explicitly enable only if other mining support is built in.
- BitForce FPGA support
- Configure out building and support of all CPU mining code unless
--enable-cpumining is enabled.
- Allow parsed values to be zero which will allow 0 values in the config file to
work.
- Advertise that we can make our own midstate, so the pool can skip generating
it for us
- Refactor the CPU scanhash_* functions to use a common API. Fixes bugs.
- Don't consider a pool lagging if a request has only just been filed. This
should decrease the false positives for "pool not providing work fast enough".
- Invalidating work after longpoll made hash_pop return no work giving a false
positive for dead pool. Rework hash_pop to retry while finds no staged work u
- Remove TCP_NODELAY from curl options as many small packets may be contributing
to network overload, when --net-delay is enabled.
- Refactor miner_thread to be common code for any kind of device
- Simplify submit_nonce loop and avoid potentially missing FOUND - 1 entry.
Reported by Luke-Jr.
- Micro-optimisation in sha256_sse2 code courtesy of Guido Ascioti
- Refactor to abstract device-specific code
Meanwhile, I still don't have my own rig back awaiting the mobo replacement... sigh.
- Add API commands: config, switchpool, gpu settings, save
- Implement socks4 proxy support.
- Fix send() for JSON strings
- Introduce a --net-delay option which guarantees at least 250ms between any
networking requests to not overload slow routers.
- Generalise locking init code.
- Allow invalid values to be in the configuration file, just skipping over them
provided the rest of the file is valid JSON. This will allow older configurat
- Allow CPU mining explicitly enable only if other mining support is built in.
- BitForce FPGA support
- Configure out building and support of all CPU mining code unless
--enable-cpumining is enabled.
- Allow parsed values to be zero which will allow 0 values in the config file to
work.
- Advertise that we can make our own midstate, so the pool can skip generating
it for us
- Refactor the CPU scanhash_* functions to use a common API. Fixes bugs.
- Don't consider a pool lagging if a request has only just been filed. This
should decrease the false positives for "pool not providing work fast enough".
- Invalidating work after longpoll made hash_pop return no work giving a false
positive for dead pool. Rework hash_pop to retry while finds no staged work u
- Remove TCP_NODELAY from curl options as many small packets may be contributing
to network overload, when --net-delay is enabled.
- Refactor miner_thread to be common code for any kind of device
- Simplify submit_nonce loop and avoid potentially missing FOUND - 1 entry.
Reported by Luke-Jr.
- Micro-optimisation in sha256_sse2 code courtesy of Guido Ascioti
- Refactor to abstract device-specific code
Meanwhile, I still don't have my own rig back awaiting the mobo replacement... sigh.
January 23, 2012, 08:40:41 PM
Code:
cgminer version 2.1.2 - Started: [2012-01-16 18:14:21]
--------------------------------------------------------------------------------
(5s):1664.2 (avg):1656.5 Mh/s | Q:198847 A:200504 R:5649 HW:0 E:101% U:22.
TQ: 4 ST: 5 SS: 10 DW: 9250 NB: 938 LW: 75021 GF: 531 RF: 16
Connected towith LP as user
Block: 00000b6e89bb00a92d1f75b327f1573f... Started: [00:20:12]
--------------------------------------------------------------------------------
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: | 373.3/372.4Mh/s | A:44859 R:1137 HW:0 U: 4.98/m I: 8
GPU 1: | 373.9/372.3Mh/s | A:45492 R:1214 HW:0 U: 5.05/m I: 8
GPU 2: | 303.0/302.6Mh/s | A:36805 R:1074 HW:0 U: 4.08/m I: 8
GPU 3: | 304.6/304.2Mh/s | A:36709 R:1051 HW:0 U: 4.07/m I: 8
GPU 4: | 305.6/304.9Mh/s | A:36640 R:1173 HW:0 U: 4.06/m I: 8
--------------------------------------------------------------------------------
Hmmm...where did my temps and fan speeds go ?
This happened to two of my rigs a couple days ago. I quit Cgminer and started it back up and temps and fan speeds showed up again.
It was the same for me. It had been running for days before that info stopped displaying. Those two rigs I mentioned are running on Windows 7 using the compiled version provided by ckolivas.
Correct.
I've been running the win32 binaries that were provided in the OP on Windows 7 64bit. Had been running fine for a few days, then all of a sudden the temps and fan speeds go away. Restarted cgminer and it's appeared ago.
This is on my main PC, may have happened after remoting in via Logmein, not sure.
My rigs are all on a KVM, so a remote session would not have been the cause for me. I'm not really worried about it because as I said, once Cgminer was restarted the problem went away. I was just putting it out there that you were not alone. I never had this happen prior to 2.1.2.
Restarting is the easy fix...but pulling the cgminer via JSON RPC interface for ANUBIS gives me -1's for all the GPU info...this is annoying. Never happened prior to 2.1.2 either.
January 23, 2012, 08:35:04 PM
Code:
cgminer version 2.1.2 - Started: [2012-01-16 18:14:21]
--------------------------------------------------------------------------------
(5s):1664.2 (avg):1656.5 Mh/s | Q:198847 A:200504 R:5649 HW:0 E:101% U:22.
TQ: 4 ST: 5 SS: 10 DW: 9250 NB: 938 LW: 75021 GF: 531 RF: 16
Connected towith LP as user
Block: 00000b6e89bb00a92d1f75b327f1573f... Started: [00:20:12]
--------------------------------------------------------------------------------
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: | 373.3/372.4Mh/s | A:44859 R:1137 HW:0 U: 4.98/m I: 8
GPU 1: | 373.9/372.3Mh/s | A:45492 R:1214 HW:0 U: 5.05/m I: 8
GPU 2: | 303.0/302.6Mh/s | A:36805 R:1074 HW:0 U: 4.08/m I: 8
GPU 3: | 304.6/304.2Mh/s | A:36709 R:1051 HW:0 U: 4.07/m I: 8
GPU 4: | 305.6/304.9Mh/s | A:36640 R:1173 HW:0 U: 4.06/m I: 8
--------------------------------------------------------------------------------
Hmmm...where did my temps and fan speeds go ?
This happened to two of my rigs a couple days ago. I quit Cgminer and started it back up and temps and fan speeds showed up again.
It was the same for me. It had been running for days before that info stopped displaying. Those two rigs I mentioned are running on Windows 7 using the compiled version provided by ckolivas.
Correct.
I've been running the win32 binaries that were provided in the OP on Windows 7 64bit. Had been running fine for a few days, then all of a sudden the temps and fan speeds go away. Restarted cgminer and it's appeared ago.
This is on my main PC, may have happened after remoting in via Logmein, not sure.
My rigs are all on a KVM, so a remote session would not have been the cause for me. I'm not really worried about it because as I said, once Cgminer was restarted the problem went away. I was just putting it out there that you were not alone. I never had this happen prior to 2.1.2.
January 23, 2012, 07:07:56 PM
Donating is tough to do.
cgminer 2.1.2 compiled from github version as of about 3.5 hours before this post.
Heh well thanks for enabling donate. This run was extraordinarily unlucky because you hit the donate threshhold just as the longpoll hit and block changed. I had to make the donate affect your mining as little as possible which means I also had to tolerate more rejects by not dirtying the "block database" in cgminer with those from the donation pool. It won't affect your own mining reject rate, but I guess doesn't look as nice in your local summary.Code:
[2012-01-23 14:41:11] LONGPOLL detected new block on network, waiting on fresh work
[2012-01-23 14:41:12] Rejected 00000000.6f296009.749ead13 GPU 3 thread 6 pool 0
[2012-01-23 14:41:14] Rejected 00000000.be045aa1.b8a81aee GPU 4 thread 8 donate
cgminer 2.1.2 compiled from github version as of about 3.5 hours before this post.
In summary, I'm willing to wear the missed good shares if you're happy to ignore the rejects
January 23, 2012, 06:06:57 PM
Donating is tough to do.
cgminer 2.1.2 compiled from github version as of about 3.5 hours before this post.
Code:
[2012-01-23 14:40:57] Accepted 00000000.ce179714.1d6592cc GPU 0 thread 1 pool 0
[2012-01-23 14:41:03] Rejected 00000000.fb8c2501.87936a36 GPU 1 thread 2 pool 0
[2012-01-23 14:41:03] Rejected 00000000.0b4a42f0.b109b162 GPU 5 thread 11 pool 0
[2012-01-23 14:41:03] LONGPOLL detected new block on network, waiting on fresh work
[2012-01-23 14:41:03] Rejected 00000000.701eea75.8ac410a3 GPU 1 thread 2 pool 0
[2012-01-23 14:41:07] LONGPOLL detected new block on network, waiting on fresh work
[2012-01-23 14:41:08] Stale share detected, discarding
[2012-01-23 14:41:11] Rejected 00000000.f43a2d22.c69c9f25 GPU 4 thread 8 pool 0
[2012-01-23 14:41:11] Rejected 00000000.9cbe6d72.df3f2710 GPU 5 thread 10 pool 0
[2012-01-23 14:41:11] LONGPOLL detected new block on network, waiting on fresh work
[2012-01-23 14:41:12] Rejected 00000000.6f296009.749ead13 GPU 3 thread 6 pool 0
[2012-01-23 14:41:14] Rejected 00000000.be045aa1.b8a81aee GPU 4 thread 8 donate
[2012-01-23 14:41:17] Rejected 00000000.f391cbde.54d9781b GPU 3 thread 7 donate
[2012-01-23 14:41:18] Rejected 00000000.7e0e895c.c3dda8b9 GPU 1 thread 3 donate
[2012-01-23 14:41:19] Rejected 00000000.e31e0679.f2a5e5fe GPU 0 thread 0 donate
[2012-01-23 14:41:19] Rejected 00000000.3c06a3d7.d10535a6 GPU 4 thread 8 donate
[2012-01-23 14:41:20] Rejected 00000000.6409355b.a8f98755 GPU 5 thread 11 donate
[2012-01-23 14:41:20] Rejected 00000000.81242f6b.5730057b GPU 4 thread 8 donate
[2012-01-23 14:41:21] Rejected 00000000.a4e64c35.186aa858 GPU 5 thread 11 donate
[2012-01-23 14:41:25] Rejected 00000000.870bd58c.aa2a54be GPU 5 thread 10 donate
[2012-01-23 14:41:27] Rejected 00000000.3da0420d.14af8534 GPU 0 thread 1 donate
[2012-01-23 14:41:30] Rejected 00000000.ff338698.e454d136 GPU 2 thread 4 donate
[2012-01-23 14:41:31] Rejected 00000000.be85c73e.ee194fdb GPU 2 thread 5 donate
[2012-01-23 14:41:33] Rejected 00000000.83b92bb9.74c697be GPU 2 thread 5 donate
[2012-01-23 14:41:34] Rejected 00000000.86d864de.d73edda3 GPU 5 thread 11 donate
[2012-01-23 14:41:37] Accepted 00000000.3ad53a14.71c71264 GPU 2 thread 4 pool 0
cgminer 2.1.2 compiled from github version as of about 3.5 hours before this post.
January 23, 2012, 06:00:31 PM
Code:
cgminer version 2.1.2 - Started: [2012-01-16 18:14:21]
--------------------------------------------------------------------------------
(5s):1664.2 (avg):1656.5 Mh/s | Q:198847 A:200504 R:5649 HW:0 E:101% U:22.
TQ: 4 ST: 5 SS: 10 DW: 9250 NB: 938 LW: 75021 GF: 531 RF: 16
Connected towith LP as user
Block: 00000b6e89bb00a92d1f75b327f1573f... Started: [00:20:12]
--------------------------------------------------------------------------------
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: | 373.3/372.4Mh/s | A:44859 R:1137 HW:0 U: 4.98/m I: 8
GPU 1: | 373.9/372.3Mh/s | A:45492 R:1214 HW:0 U: 5.05/m I: 8
GPU 2: | 303.0/302.6Mh/s | A:36805 R:1074 HW:0 U: 4.08/m I: 8
GPU 3: | 304.6/304.2Mh/s | A:36709 R:1051 HW:0 U: 4.07/m I: 8
GPU 4: | 305.6/304.9Mh/s | A:36640 R:1173 HW:0 U: 4.06/m I: 8
--------------------------------------------------------------------------------
Hmmm...where did my temps and fan speeds go ?
This happened to two of my rigs a couple days ago. I quit Cgminer and started it back up and temps and fan speeds showed up again.
It was the same for me. It had been running for days before that info stopped displaying. Those two rigs I mentioned are running on Windows 7 using the compiled version provided by ckolivas.
Correct.
I've been running the win32 binaries that were provided in the OP on Windows 7 64bit. Had been running fine for a few days, then all of a sudden the temps and fan speeds go away. Restarted cgminer and it's appeared ago.
This is on my main PC, may have happened after remoting in via Logmein, not sure.
Jump to: