Are there any downsides to running 1 thread per GPU on a normal pool? Every time I try enabling that second thread, my hashrate drops severely and my system becomes really slow.
It usually adds only a small amount to the hashrate in the order of 1-3% depending on device. Alright. Do you maybe know why it's doing that? I know I used to use 2 threads back when I was on Windows and it ran just fine. Also it seems to be just the display GPU that suffers, but being on dynamic intensity, it's supposed to set itself to 1 thread anyway, right? No idea  Only time someone reported something along these lines they discovered the display GPU wasn't actually the one they thought it was in cgminer. The GPU numbers don't always make sense and are just whatever OpenCL tells cgminer. |
|
|
|
|
I'm really sorry but I'm going to have to backtrack on this as I've realised I don't have the time to dedicate to getting this working. I'd still like to see the x6500 support in cgminer, so you should put it back as a generic bounty as you originally planned and open it up for tenders again.
|
|
|
|
|
Default cgminer settings are designed to be the best for 7970 automatically because I spent a heck of a lot of time optimising it for GCN. They end up being -v 1 -w 64 -k poclbm and if you don't specify anything, that's what you'll get.
|
|
|
|
Are there any downsides to running 1 thread per GPU on a normal pool? Every time I try enabling that second thread, my hashrate drops severely and my system becomes really slow.
It usually adds only a small amount to the hashrate in the order of 1-3% depending on device. |
|
|
|
I tested using cgminer's auto from 75 degrees (where it sits around 73 most of the time) to doubling the fan speed manually which brought it down to 65 degrees. It used 2 watts more. So whatever die effects are there between 65-75 degrees are offset by the fan power. * ckolivas puts it back on default autofan settings |
|
|
|
Be aware that you might need to factor in delivery to Australia in the bounty, since that's where I am. That was quite expensive for a GPU, but shouldn't be so bad for this board. Thanks  |
|
|
|
Both 2.3.2 and 2.3.3 windows versions stop working on user switching.
2.3.1 works well.
Win7 x64, SDK 2.6.
User switching?... What on earth has the cgminer version got to do with that? I don't know O_o. But when I return back to the user running cgminer I see that no more shares were submitted since I switched out. It just staying still. Well you'll have to look elsewhere to see what permissions you extracted the zip file with or something like that, because cgminer has no clue about users or permissions like that. |
|
|
|
Using this example/option from another thread.... cgminer version 2.3.1m - Started: [2012-03-25 20:43:39]
--------------------------------------------------------------------------------
(5s):1878.8 (avg):1856.0 Mh/s | Q:41418 A:107620 R:770 HW:0 E:260% U:26.23/m
TQ: 6 ST: 7 SS: 389 DW: 3386 NB: 546 LW: 247388 GF: 7 RF: 14
Connected to http://au.ozco.in:8331 with LP as user miku.1
Block: 00000a240880dae42eea41dd1b91940a... Started: [11:29:40]
--------------------------------------------------------------------------------
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
Radeon 5850: 76.0C 3277RPM | 358.7/358.5Mh/s | A:26060 R:114 HW:0 U: 4.99/m I: 9
Radeon 5870: 69.0C 2898RPM | 367.1/365.7Mh/s | A:26372 R:112 HW:0 U: 5.05/m I: 9
Icarus: | 370.7/366.1Mh/s | A:27565 R:273 HW:0 U: 5.28/m
BF Single: 64.1C | 504.1/765.6Mh/s | A:27625 R:271 HW:0 U: 5.29/m
--------------------------------------------------------------------------------
[2012-03-29 11:39:22] Accepted 00000000.df0f50fd.43d06b28 Icarus thread 4 pool 0
[2012-03-29 11:39:24] Accepted 00000000.a7607fe8.9e9ac7de BF Single thread 5 pool 0
[2012-03-29 11:39:27] Accepted 00000000.0e7a8c29.192f6ff1 BF Single thread 5 pool 0
Is there currently a supported API call in 2.3.3 that will return CARD MODEL or CARD FAMILY ? I'm sorry but this is virtually impossible to do reliably (the GPU part). OpenCL doesn't tell us what the devices are. cgminer tries to guess with ADL and it's not entirely reliable. |
|
|
|
|
Welcome to discovering human nature. All you need to do is look at your own (in)action to understand why everyone else is doing it.
|
|
|
|
|
Re: The display.
Screw it, I don't really want to change the layout, or what's displayed, so I've spent the afternoon fighting with curses to try and get it working with any number of devices, provided your window is long enough. If it's not, you'll lose the log window output.
|
|
|
|
Both 2.3.2 and 2.3.3 windows versions stop working on user switching.
2.3.1 works well.
Win7 x64, SDK 2.6.
User switching?... What on earth has the cgminer version got to do with that? |
|
|
|
|
What are they worth? If you can get enough BTC from others to buy one and send it to me, I'd do it myself.
|
|
|
|
Let's talk interface. What's needed, what's considered redundant, and what's missing?
For me, miner.php actually does most of what's needed quite well, aside from saving the configuration and some of the more advanced features in other projects (like email notifications). I don't even use the command line interface once it's started, unless troubleshooting - even then, dumping to a log is easier. So is the text interface even necessary anymore? I use the text interface myself. So you have zero chance of me getting rid of it. |
|
|
|
You're right, I won't get very far. I'll refrain from posting suggestions in the future... I mean really, who wants suggestions on how to improve a program or solve a problem?
Kano doesn't speak for this project. I'm open to suggestions. To be honest I was hoping by now one of the API front ends that people had coded could have replaced this ageing text based interface, but they're all not quite as comprehensive, and tend to need other software to work and so on, so I'm not going to include any of them (yet). Let's talk interface. What's needed, what's considered redundant, and what's missing? cgminer version 2.3.3 - Started: [2012-04-17 22:02:28]
--------------------------------------------------------------------------------
(5s):1534.0 (avg):1592.1 Mh/s | Q:47325 A:110020 R:304 HW:0 E:232% U:22.20/m
TQ: 6 ST: 6 SS: 127 DW: 4379 NB: 501 LW: 135131 GF: 78 RF: 44
Connected to http://au.ozco.in:8332 with LP as user ckolivas.0
Block: 000007382fac2ce444d7d5b79a1553bd... Started: [08:31:39]
--------------------------------------------------------------------------------
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: 72.0C 3265RPM | 718.6/716.7Mh/s | A:49665 R:132 HW:0 U: 10.02/m I:11
GPU 1: 72.5C 4346RPM | 430.5/428.7Mh/s | A:29367 R: 79 HW:0 U: 5.92/m I: 9
GPU 2: 72.5C 3641RPM | 449.5/446.7Mh/s | A:30990 R: 93 HW:0 U: 6.25/m I: 9
--------------------------------------------------------------------------------
[2012-04-21 08:35:21] Accepted 00000000.ec068da4.1ba7d1ab GPU 0 thread 0 pool 1
[2012-04-21 08:35:22] Accepted 00000000.ad98a857.5cd189b9 GPU 0 thread 0 pool 1
[2012-04-21 08:35:26] Accepted 00000000.cca935f3.4f36a99c GPU 0 thread 0 pool 1
[2012-04-21 08:35:29] Accepted 00000000.6e86a341.0f4d32b6 GPU 0 thread 1 pool 1
A lot of these were added initially simply because no one had ever offered so much information or features before, and as I added things to cgminer, I added the information to the display. Largely, the way people mine and the issues have changed. However, I don't want cgminer to only be suitable to miners with heaps of hardware. I still want it accessible to the miner with only one GPU that is mining. |
|
|
|
Try cgminer?
Does CGMiner support 7970s now? Yes. I worked my arse off to make it perform well on 7970s. You don't even need to specify anything apart from an intensity level to get the best 7970 performance. I get 720 Mhash from my 7970 running at 1200/1050+5% clocks at intensity 11. Being on windows, you'll probably have to compromise with intensity 9 and slightly lower hashrate to avoid heavy CPU usage. |
|
|
|
|
Unfortunately, cgminer can't do shit to the voltage of a 7970.
|
|
|
|
For my 5xxx cards, I found out that 2.2.6 works best. Although 2.3.3 also works fine, the cursor jumps everywhere on the screen randomly
I did see performance drop when I switch to diablo kernel, don't know why
The diablo kernel is only for 2.6 SDK based installations. That said, the custom modified poclbm kernel I include is probably equally good, if not better, for 2.6 SDK based installations. However, 2.1/2.4/2.5 SDK installations will usually work best with the phatk kernel (which is chosen automatically anyway). As for why your cursor jumps all over the screen randomly, NFI. |
|
|
|
|
Reluctant to add another line for something so flaky, variable, unreliable, and just plain broken. Doesn't make sense. Alas curses just isn't flexible enough to cope with this sort of usage where it has some idea of being used on fixed terminals where resizing is a big deal. curses...
|
|
|
|
|
Show Posts
