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

no

Ok, it worked. Many thanks, ckolivas.

Now, I can run 2 instances of cgminer, one is using the Intel GPU and another is using the Nvidea GPU.
Is there some sort of command for cgminer to use both platforms and see both GPU's in same instance? 

it is worth to mention that NVDA hw is 3 times slower in SHA than AMD/ATI.

Alas all of this is wrong.

All you need to do is add the following to your command: --gpu-platform 1

This is wrong. You can build cgminer for nvidia. The precompiled binaries are for ATI, but if you download the nvidia opencl SDK you should be able to build against it. I have done this on linux a long time ago, no idea about windows. You don't get any fan control or temperature monitoring.

Thanks for your answer. The hub is self powered and it was weeks working alone.

The lancelot i installed today is connected directly to the rasp pi.

The problem is not the power, i think that cgminer only give works to the lancelot and the block erupter usb gets in standby...

If your hub is not powered, you might be straining it.  You should only need 1A or so though since the Lancelot has its own power chord.

Hello, i've a little problem, i'll try to explain.
I'm using rasp pi, and installed cgminer 3.3.1
I have 1 block erupter in a hub usb powered and a lancelot from blackarrow.

I've been using my block erupter a lot of days without problems.

Since I installed my lancelot, I tried with sudo cgminer and it starts working, but it seems the block erupter gets the first work, after that it gets in standby meanwhile the lancelot works fully. A 60 seconds the cgminer says the block erupter gets sick.

What can I do? Do you need something abot logs?

Please help!
Thanks in advantage

CUDA miner is only for Litecoin, not for BTC (I think). But many thanks for your kind answer. I now understand why cgminer doesn't use the Nvidea GPU.

For nvidea use CUDA miner, cgminer is only for openCL devices...

CUDA miner: https://bitcointalksearch.org/topic/ann-cudaminer-ccminer-cuda-based-mining-applications-windowslinuxmacosx-167229

Greetings.

I have a Alienware m14x with OS Windows 8 64 bits and 2 GPU's: Nvidea GeForce as default GPU and a Intel HD Graphics 4000 GPU.

With Diablo-miner, it identifies the 2 GPU's but uses only the Nvidea GeForce GT650m (25 MH/s) (GPU Load 97%).

But with cgminer 3.3.1, it only uses the Intel HD Graphics 4000 GPU, mining @ 11.8 MH/s (the Nvidea GPU load is 0%).

Is it possible for cgminer, to use both GPU's or even only the Nvidea GPU instead of the Intel one?

Many thanks in advance.

UPDATE: cgminer n option:

https://bitcointalk.org/index.php?topic=28402.msg2649331;topicseen#msg2649331

Cgminer sets network difficulty, how?

I'm asking this to better understand the problem I have at the moment. Scrypt mining (ltc) currently due to skyrocketing bitcoin diff, my cgminer is reporting a network diff of 57.9M, rather than the 883.xxxxxx which is the current ltc diff. No HW, and hash rate is good--it's a 7950, hashing at 530 Kh/s.

I had just switched from btc mining to ltc mining. When I was btc mining, cgminer reported correct network diff, but now that I have switched to ltc scrypt mining, it's reporting highly inaccurate diff.

Why is this? Does this have any impact or consequences? Any suggestions please?

Thanks for the input, I was a little apprehensive to hack the Beaglebone since I'm linux rusty.  It is a 2.0 hub.

Got 3.3.1 compiled and running on it last night, we'll see how it works later when I get the hub moved back down there and hooked up.

I have to assume you are using GPUs on scrypt givern your numbers.  Regarding GPUs, as has been posted roughly 2 billion times in this thread (albeit mostly for bitcoin), if you change drivers or SDK and then later upgrade cgminer where there are any kernel changes at all, you changed settings.  This is because you made cgminer compile new kernels on a different driver/sdk combo.  Copying a batch file or other breed of launch script doesn't change what you did to your mining machine between cgminer versions.  If you delete the scrypt kernel files from 3.2.1, you will probably see the same slowdown when you run it again and it generates new ones  You'll need to back them up first to test this.  Once it is confirmed, you will need to either revert to the old kernels on the old version, copy the old kernels to the new version if they have the exact same file names, or try to find the magic driver / SDK combo again to get the new version to compile new kernels with the best speed (deleting kernels from the new version between each attempt, probably pulling out lots of hair, and most likely making things worse before you make them better).

ETA:  In your case, you switched to a new folder, so even if there were no kernel changes, you compiled new kernels on new drivers.  I referred to this point in the fix options (copy the old kernels to the new version implies they are in different places, just like copy the batch file to the new version does), but didn't otherwise make it clear in my original response, so wanted to add it.

I did not change the settings.
impossible change settings moved .bat file to the folder of new cgminer 3.3.1

If your usb hub is a usb2 hub and not a usb3 hub you will be far better off moving to the latest version of cgminer instead. The only reason to stick with the old version of cgminer is if you have multiple usb1.1 devices on a usb3 hub for there remains an instability there that we've been unable to debug so far.

Oops.  My bad.

Cheers for the feedback , I'll delete the post now.

For the lazy: