Author

Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 385. (Read 5806015 times)

hero member
Activity: 924
Merit: 1000
Watch out for the "Neg-Rep-Dogie-Police".....
strange issue with cgminer.
Two cards one 5870 and one 5850
I have connected one monitor to the 5870
I am getting a message when starting cgminer which says that "ADL found less devices than opencl! There is possibly more than one display attached to a GPU. Use the gpu map feature to reliably map OpenCL to ADL"
Then if I take the cable and connect it to the 5850 and then to the 5870 everything works fine and I don't get the previous message.
In case I don't, I get the message above and cannot control the GPU settings.
I experimented with --gpu-map with no luck.
Any ideas?

Even though your not supposed to have to use them, I still use a dummy plug on my GPU that doesn't drive a monitor and expand my desktop to that GPU w/dummy plug.  That just makes things work much better for me.

So that may be worth a try.
Sam

Oh yeah, the good old dummy plug.......takes me back a bit...... Grin
legendary
Activity: 3586
Merit: 1099
Think for yourself
strange issue with cgminer.
Two cards one 5870 and one 5850
I have connected one monitor to the 5870
I am getting a message when starting cgminer which says that "ADL found less devices than opencl! There is possibly more than one display attached to a GPU. Use the gpu map feature to reliably map OpenCL to ADL"
Then if I take the cable and connect it to the 5850 and then to the 5870 everything works fine and I don't get the previous message.
In case I don't, I get the message above and cannot control the GPU settings.
I experimented with --gpu-map with no luck.
Any ideas?

Even though your not supposed to have to use them, I still use a dummy plug on my GPU that doesn't drive a monitor and expand my desktop to that GPU w/dummy plug.  That just makes things work much better for me.

So that may be worth a try.
Sam
member
Activity: 80
Merit: 10
damn thanks anyway
I am not really accustomed to the linux environment so I haven't tried it yet
hero member
Activity: 924
Merit: 1000
Watch out for the "Neg-Rep-Dogie-Police".....
Win-doze

There's yer problem.

I used to use windoze for mining - too many problems like you're having. I seem to remember having to completely uninstall & reinstall driver + sdk to get rid of that, but I can't really remember TBH - I kind of erased it from my memory deliberately sort of thing.... Wink
member
Activity: 80
Merit: 10
hero member
Activity: 924
Merit: 1000
Watch out for the "Neg-Rep-Dogie-Police".....
strange issue with cgminer.
Two cards one 5870 and one 5850
I have connected one monitor to the 5870
I am getting a message when starting cgminer which says that "ADL found less devices than opencl! There is possibly more than one display attached to a GPU. Use the gpu map feature to reliably map OpenCL to ADL"
Then if I take the cable and connect it to the 5850 and then to the 5870 everything works fine and I don't get the previous message.
In case I don't, I get the message above and cannot control the GPU settings.
I experimented with --gpu-map with no luck.
Any ideas?

Linux or windoze?

If Linux, try: sudo aticonfig --adapter=all -f --initial

Reboot.
member
Activity: 80
Merit: 10
strange issue with cgminer.
Two cards one 5870 and one 5850
I have connected one monitor to the 5870
I am getting a message when starting cgminer which says that "ADL found less devices than opencl! There is possibly more than one display attached to a GPU. Use the gpu map feature to reliably map OpenCL to ADL"
Then if I take the cable and connect it to the 5850 and then to the 5870 everything works fine and I don't get the previous message.
In case I don't, I get the message above and cannot control the GPU settings.
I experimented with --gpu-map with no luck.
Any ideas?
legendary
Activity: 2576
Merit: 1186
Alright enough. STFU. If any other miner software was posting in the CGMiner thread about how the author thought their software was better, they would get a shitstorm up the ass. If Diablo, ufasoft, M0mchil, or Jedi95 was in here saying their miner was better than CGMiner, they would get their posts removed. Yet somehow because your program was forked from CGMiner, you get these special privileges.

From now on, I will reporting any post by LJR in the CGMiner thread to the mods. I suggest everyone else to do the same.
Cool story bro.
legendary
Activity: 952
Merit: 1000
Alright enough. STFU. If any other miner software was posting in the CGMiner thread about how the author thought their software was better, they would get a shitstorm up the ass. If Diablo, ufasoft, M0mchil, or Jedi95 was in here saying their miner was better than CGMiner, they would get their posts removed. Yet somehow because your program was forked from CGMiner, you get these special privileges.

From now on, I will reporting any post by LJR in the CGMiner thread to the mods. I suggest everyone else to do the same.
legendary
Activity: 2702
Merit: 1468
Hi Kano,

I was trying to upgrade from 2.7.6 to 2.11.3

I followed your procedure to update BFL device driver to WinUSB.  Downloaded zadig (for Windows 7), run it as administrator.
I got an error installing WinUSB driver.  Here is the Zadig debug log:

http://www.petermoss.com/akbash/zadig_install_log

Can you add FTDI driver support as an option?  As it is now, I can only use 2.10.5 version.

legendary
Activity: 2576
Merit: 1186
Since 2.11.3 something with (5s) MH/s counting is really weird:

http://s16.postimg.org/kpvvw1v6d/Bildschirmfoto_2013_03_30_um_01_24_34.png
Correct, devices that hash ~5s or slower per nonce range indeed do not show a very reliable value for a 5s average ... since that really is what to expect if you think about the mathematics of it Smiley

Your reasoning sounds valid, but this is a bug that didn't exist in a previous version. How is that not a regression? I am always using the latest git version, and at least for now, reverting commit 072ffbba424770afcbd2e1a10aead8a5035f80de returns the old (correct) 5s hashrate average for slow devices.
I intentionally did not merge this regression into BFGMiner.
sr. member
Activity: 658
Merit: 250
Since 2.11.3 something with (5s) MH/s counting is really weird:

http://s16.postimg.org/kpvvw1v6d/Bildschirmfoto_2013_03_30_um_01_24_34.png
Correct, devices that hash ~5s or slower per nonce range indeed do not show a very reliable value for a 5s average ... since that really is what to expect if you think about the mathematics of it Smiley

Your reasoning sounds valid, but this is a bug that didn't exist in a previous version. How is that not a regression? I am always using the latest git version, and at least for now, reverting commit 072ffbba424770afcbd2e1a10aead8a5035f80de returns the old (correct) 5s hashrate average for slow devices.
legendary
Activity: 1973
Merit: 1007
I decided to upgrade from 2.10.x today and it looks like you've killed my startup scripts. Why was scan-serial removed for BFL devices? I was running multiple instances of CGminer with each instance pointing to only one of my singles. This allowed me to tie one pool to one device(with all other pools set to failover only).

 Is there any other way I can replicate this functionality in 2.11.x or should I go back to 2.10.x or BFGminer? Do I need to build with icarus support, and if I do, will the switch still work with a BFL device? If you guys were to add the ability to tie a pool to a specific device in one instance, that would work too:)
To repeat what is written in the README, FPGA-README, in the NEWS file, in the posts here on the forum ...
BFL devices are USB direct and always autodetected unless you tell cgminer not to.
--scan-serial is ONLY used for Icarus now
The command related to restricting detection of BFL/MMQ is --usb as explained in detail (47 lines) in the README ...
e.g. --usb BFL:1 would only detect a single BFL and stop looking

Ah great, I'll give the USB switch a shot. I quickly scanned through the docs but was more interested in why -S was removed. Now that I've read serial-USB was removed that makes sense. Thanks
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Since 2.11.3 something with (5s) MH/s counting is really weird:

http://s16.postimg.org/kpvvw1v6d/Bildschirmfoto_2013_03_30_um_01_24_34.png
Correct, devices that hash ~5s or slower per nonce range indeed do not show a very reliable value for a 5s average ... since that really is what to expect if you think about the mathematics of it Smiley
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
I decided to upgrade from 2.10.x today and it looks like you've killed my startup scripts. Why was scan-serial removed for BFL devices? I was running multiple instances of CGminer with each instance pointing to only one of my singles. This allowed me to tie one pool to one device(with all other pools set to failover only).

 Is there any other way I can replicate this functionality in 2.11.x or should I go back to 2.10.x or BFGminer? Do I need to build with icarus support, and if I do, will the switch still work with a BFL device? If you guys were to add the ability to tie a pool to a specific device in one instance, that would work too:)
To repeat what is written in the README, FPGA-README, in the NEWS file, in the posts here on the forum ...
BFL devices are USB direct and always autodetected unless you tell cgminer not to.
--scan-serial is ONLY used for Icarus now
The command related to restricting detection of BFL/MMQ is --usb as explained in detail (47 lines) in the README ...
e.g. --usb BFL:1 would only detect a single BFL and stop looking
legendary
Activity: 952
Merit: 1000
That's no reason to continue using deprecated technology. CGMiner could also be a 16-bit binary.
You missed the point. CGMiner is also deprecated software for deprecated technology (GPUs).
It's posts like this that piss me off.

A) Doesn't BFG mine on GPUs? If it's so deprecated, I dare you to cut out the GPU portion of BFG, and see how many people care.
B) Don't a lot of people still mine on GPUs? I know I do.
C) If a software is still being maintained and actively developed, how can it be called deprecated?

The only obvious answer: You don't like CGMiner, and you will do everything in your power to defame it, and promote your fork.
full member
Activity: 196
Merit: 100
You mean the current, supported, standard interface, instead of bypassing it to use a low-level interface that has no benefit whatsoever.

The "current, supported, standard interface" is an ancient unix terminal interface which conveniently doesn't exist on all platforms. A mining device is not a terminal where unpredictable buffering somewhere in the chain is not a big deal.

It's like writing your own TCP/IP stack instead of using the one included in the OS.

Awful analogy.

A TCP/IP stack is a complicated and generic stack used by many different parts of the system (and by remote systems). Replacing it would almost certainly compromise performance, reliability, security, etc.

A mining-device interface is much simpler and only used by a single application for a single purpose.

you've lost support, driver updates

For a usb serial driver? You've got to be fucking kidding me.

ease of use

For the end user? It "just works" on linux. Your point is partially valid on Windows, except that Windows is Windows, so it is not.

forward compatibility with new hardware

You're almost guaranteed to need to update the mining software for new hardware.

and regular-user-mode access.

You can replug the device on linux to get the normal driver back if you really want it. Again, there isn't much to say about Windows here.
legendary
Activity: 2576
Merit: 1186
By the way, and this is totally unrelated, is it possible to use Eloipool to run a TRC pool?
I don't know what TRC is. Try it and see?

Honestly, I don't really know how to set up a pool. I'm a programmer, but I haven't found much information out there. If you could point me to a resource, that'd be awesome.
https://bitcointalksearch.org/topic/avalon-users-bitcoind-eloipool-configuration-158105
legendary
Activity: 1973
Merit: 1007
I decided to upgrade from 2.10.x today and it looks like you've killed my startup scripts. Why was scan-serial removed for BFL devices? I was running multiple instances of CGminer with each instance pointing to only one of my singles. This allowed me to tie one pool to one device(with all other pools set to failover only).

 Is there any other way I can replicate this functionality in 2.11.x or should I go back to 2.10.x or BFGminer? Do I need to build with icarus support, and if I do, will the switch still work with a BFL device? If you guys were to add the ability to tie a pool to a specific device in one instance, that would work too:)
legendary
Activity: 2702
Merit: 1240
Since 2.11.3 something with (5s) MH/s counting is really weird:

Jump to: