[ANN] ccminer 2.3 - opensource - GPL (tpruvot) - page 157.

nzsquirrell

member

Activity: 113

Merit: 10

Compilation of 1.6.5 produces an error under linux:

g++ -DHAVE_CONFIG_H -I. -DHAVE_PCIDEV -fopenmp -pthread -fno-strict-aliasing -I./compat/jansson -I/usr/local/cuda/include -g -O2 -MT ccminer-cuda.o -MD -MP -MF .deps/ccminer-cuda.Tpo -c -o ccminer-cuda.o `test -f 'cuda.cpp' || echo './'`cuda.cpp
cuda.cpp: In function 'void cuda_devicenames()':
cuda.cpp:79:44: error: 'gpu_vendor' was not declared in this scope
if (gpu_vendor(props.pciBusID, vendorname) > 0 && strlen(vendorname)) {

Weirdly gpu_vendor is declared in nvml.h, and nvml.h is included in cuda.cpp ..... any ideas?

Otherwise keep up the great work!

Epsylon3

legendary

Activity: 1484

Merit: 1082

ccminer/cpuminer developer

type ldconfig but your error is really "simple" to understand :p maybe you should use Windows

Infern0

member

Activity: 126

Merit: 10

Getting this error when I try to run on ubuntu 14.04... any ideas guys???

/home/infern0/Downloads/ccminer/ccminer-linux/ccminer: error while loading shared libraries: libcudart.so.7.0: cannot open shared object file: No such file or directory

Epsylon3

legendary

Activity: 1484

Merit: 1082

ccminer/cpuminer developer

v1.6.5 released today... topic updated

Note: The nvidia-smi tool was updated in the latest nvidia drivers on both linux (352.21) and windows (353.30)

All Clocks, Power in Watts and many other infos are now available, and may be programmable too via the nvml interface... stay tuned.. :p

nvidia-smi -q

Code:

GPU 0000:02:00.0
    Product Name                    : GeForce GTX 960
    Product Brand                   : GeForce
    Display Mode                    : Disabled
    Display Active                  : Disabled
    Persistence Mode                : Enabled
    Accounting Mode                 : Disabled
    Accounting Mode Buffer Size     : 128

    PCI
        Bus                         : 0x02
        Device                      : 0x00
        Domain                      : 0x0000
        Device Id                   : 0x140110DE
        Bus Id                      : 0000:02:00.0
        Sub System Id               : 0x85201043
        GPU Link Info
            PCIe Generation
                Max                 : 2
                Current             : 2
            Link Width
                Max                 : 16x
                Current             : 4x
        Bridge Chip
            Type                    : N/A
            Firmware                : N/A
        Replays since reset         : 0
        Tx Throughput               : 0 KB/s
        Rx Throughput               : 0 KB/s
    Fan Speed                       : 78 %
    Performance State               : P0
...
    FB Memory Usage
        Total                       : 2047 MiB
        Used                        : 451 MiB
        Free                        : 1596 MiB
    BAR1 Memory Usage
        Total                       : 256 MiB
        Used                        : 4 MiB
        Free                        : 252 MiB
    Compute Mode                    : Default
    Utilization
        Gpu                         : 99 %
        Memory                      : 38 %
        Encoder                     : 0 %
        Decoder                     : 0 %
...
    Temperature
        GPU Current Temp            : 73 C
        GPU Shutdown Temp           : 101 C
        GPU Slowdown Temp           : 96 C
    Power Readings
        Power Management            : Supported
        Power Draw                  : 113.08 W
        Power Limit                 : 130.00 W
        Default Power Limit         : 130.00 W
        Enforced Power Limit        : 130.00 W
        Min Power Limit             : 60.00 W
        Max Power Limit             : 150.00 W
    Clocks
        Graphics                    : 1379 MHz
        SM                          : 1379 MHz
        Memory                      : 3600 MHz
    Applications Clocks
        Graphics                    : 1430 MHz
        Memory                      : 3600 MHz
    Default Applications Clocks
        Graphics                    : 1227 MHz
        Memory                      : 3600 MHz
    Max Clocks
        Graphics                    : 1493 MHz
        SM                          : 1493 MHz
        Memory                      : 3600 MHz

The tool is in C:\Program Files\NVIDIA Corporation\NVSMI in windows with the documentation

greedytacothief

newbie

Activity: 1

Merit: 0

I have been having this error with my gtx 660se

Code:

cuda error in func'qubit_luffa512_cpu_init' input at line 446, invalid device symbol

ccminer does work with my gtx 770 very well, but i have just not been able to get this to work

this is the batch file for my 660

Code:

ccminer-30-35-50-52.exe -t 2 -d 1 --algo=qubit -o stratum+tcp://stratum.dgb.theblocksfactory.com:9000 -u greedytacothief.1 -p x -f 10

tuaris

hero member

Activity: 780

Merit: 501

This is not working

IMweasel

newbie

Activity: 29

Merit: 0

Quote from: Epsylon3 on June 03, 2015, 04:39:45 PM

was just a debug line for my recent pool settings... scrypt-jane is so slow that the scan time is almost ignored... Its an extreme test...

Please i dont want to talk about this algo, i imported it to have it and do some compatibility tests/bench... will not touch it for the moment

Ok...too bad. The UTC founders even recommend -s 1, which works fine for cudaminer...it's still catching blocks just fine, so no need to study them for so long.
Scrypt-Jane seems profitable for somewhat older cards though, and CCminer is more capable to keep performance high. I wish it would work for UTC Cry

By the way, the same problem exists for your compilations of the CPU miner,it just cannot do UTC Cry

I'll give it a rest now...just hoping you can fix it someday... thanks for the swift support!

Edit:original CPUminer is also unable to mine UCT. Trying out yacminer for it,and this one does it flawless!
I figured it might have something to do with this timestamp thing?

Edit2:Pooler stated that is miner does not support UTC. So i guess that any fork without adding specific support,won't work.

Leinaded

newbie

Activity: 63

Merit: 0

Quote from: Epsylon3 on June 03, 2015, 05:25:59 PM

No.. With these last details... I know why... Avx is required (checked in my build options) if i remember right..

But, just use the x86... Perf are a bit better.. x64 one has no advantages yet... Until nvapi is deprecated (not until nvml is fully implemented by nvidia)

Thanks a lot for the help Epsy, it works like a charm now. 15-20 Kh/s improvement compared with the x64 original ccminer, not bad

Epsylon3

legendary

Activity: 1484

Merit: 1082

ccminer/cpuminer developer

No.. With these last details... I know why... Avx is required (checked in my build options) if i remember right..

But, just use the x86... Perf are a bit better.. x64 one has no advantages yet... Until nvapi is deprecated (not until nvml is fully implemented by nvidia)

Leinaded

newbie

Activity: 63

Merit: 0

Quote from: Epsylon3 on June 03, 2015, 04:41:31 PM

Quote from: Leinaded on June 03, 2015, 07:31:01 AM

Hi I'm having some problem with this miner. It doesn't run on my Windows 10 Technical Preview. Always gives the message "ccminer has stopped working" even running the miner with no arguments. Original ccminer by cbuchner1 v1.2 beta works fine in this same OS. I'm using the same config with this modded version and my graphic card is a Gigabyte GT 730 2GB DDR5 using the latest 352.84 drivers for Windows 10.

Run params: ccminer-x64-35-50-52.exe -a dmd-gr -o stratum+tcp://dmdpool.digsys.bg:3333 -u username.workername -p workerpassword

Beware both x64 and x86 cant run in the same folder... There are 2 dll with the same name but one is x86 and not the other one... Does that help you ?
Tested without problems here... Next time please put real credentials, i hate to register on pools for debug purpose, and this one require a wallet address

Sorry maybe I'm missing something obvious but I see only one msvcr120.dll in my install directory. I've downloaded release ccminer-rel1.6.4-vc2013-x64.7z. Also the problem is not related with the pool because the program doesn't even run in my pc, not even with --help param. The exe just crashes not even showing the dos prompt.

Perhaps is related to my videocard not being supported? Is Compute 3.5 Kepler - GK208

Thanks for all the help Epsylon3

P. S. my CPU is an Intel Core 2 Quad Q6700

Epsylon3

legendary

Activity: 1484

Merit: 1082

ccminer/cpuminer developer

Quote from: Leinaded on June 03, 2015, 07:31:01 AM

Hi I'm having some problem with this miner. It doesn't run on my Windows 10 Technical Preview. Always gives the message "ccminer has stopped working" even running the miner with no arguments. Original ccminer by cbuchner1 v1.2 beta works fine in this same OS. I'm using the same config with this modded version and my graphic card is a Gigabyte GT 730 2GB DDR5 using the latest 352.84 drivers for Windows 10.

Run params: ccminer-x64-35-50-52.exe -a dmd-gr -o stratum+tcp://dmdpool.digsys.bg:3333 -u username.workername -p workerpassword

Tested without problems here... Next time please put real credentials, i hate to register on pools for debug purpose, and this one require a wallet address

Epsylon3

legendary

Activity: 1484

Merit: 1082

ccminer/cpuminer developer

was just a debug line for my recent pool settings... scrypt-jane is so slow that the scan time is almost ignored... Its an extreme test...

Please i dont want to talk about this algo, i imported it to have it and do some compatibility tests/bench... will not touch it for the moment

IMweasel

newbie

Activity: 29

Merit: 0

When i tried -D i noticed something today... is the -s 10 supposed to be directly after my login name?
POOL 0: 127.0.0.1:44101 USER x -s 10
I would guess it is a scantime flag,but no matter what i set it to,the s 10 persists to be there.
And also,if i use the -s flag,the actual scantime does not change at all.

Epsylon3

legendary

Activity: 1484

Merit: 1082

ccminer/cpuminer developer

Beware both x64 and x86 cant run in the same folder... There are 2 dll with the same name but one is x86 and not the other one... Does that help you ?

Leinaded

newbie

Activity: 63

Merit: 0

Quote from: sp_ on June 03, 2015, 07:36:44 AM

try with a lower intensity. like -i 10. and increase upwards if it goes well.

Thanks sp_ but it seems the problem is not intensity related. Tried that and still same crash. It doesnt even show the cmd screen. :S

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

try with a lower intensity. like -i 10. and increase upwards if it goes well.

Leinaded

newbie

Activity: 63

Merit: 0

Hi I'm having some problem with this miner. It doesn't run on my Windows 10 Technical Preview. Always gives the message "ccminer has stopped working" even running the miner with no arguments. Original ccminer by cbuchner1 v1.2 beta works fine in this same OS. I'm using the same config with this modded version and my graphic card is a Gigabyte GT 730 2GB DDR5 using the latest 352.84 drivers for Windows 10.

Run params: ccminer-x64-35-50-52.exe -a dmd-gr -o stratum+tcp://dmdpool.digsys.bg:3333 -u username.workername -p workerpassword

IMweasel

newbie

Activity: 29

Merit: 0

Quote from: Epsylon3 on May 29, 2015, 03:23:06 PM

You will get a lot of boo like that without the gbt check... That means somebody else found it before you. You can sometimes have more details in the wallet debug.log

I'm not sure what to look for in the debug.log...
These are my CC and Cudaminer stats. CC was up yesterday all afternoon, Cuda was up last night.
Comparing the the yay and boo rates; i think something is going wrong somewhere!
I don't have a clue what to do/try to get this working properly.

CC

[2015-06-01 19:59:16] GPU #0: n=88220
[2015-06-01 20:00:37] found => 0008dd26 26dd0800
[2015-06-01 20:00:37] GPU #0: GeForce GTX 660, 303.77 H/s
[2015-06-01 20:00:37] accepted: 0/7 (0.00%), 607.15 H/s booooo
[2015-06-01 20:00:37] job 556c9dc2 target change: 91743000000 (11.0)
[2015-06-01 20:00:37] GPU #0: start=00000000 end=000fffff range=000fffff

Cuda
[2015-06-02 08:41:02] accepted: 11/11 (100.00%), 0.38 khash/s (yay!!!)

edit:
past 6 hour tryout using CC
[2015-06-02 14:44:22] found => 0000a4f6 f6a40000
[2015-06-02 14:44:22] GPU #0: GeForce GTX 660, 269.62 H/s
[2015-06-02 14:44:23] accepted: 0/13 (0.00%), 541.01 H/s booooo
[2015-06-02 14:44:23] GPU #0: start=00000000 end=000fffff range=000fffff

and another 6 hour tryout using Cuda coming up.

IMweasel

newbie

Activity: 29

Merit: 0

Quote from: Epsylon3 on June 01, 2015, 08:00:55 AM

no, read my readme

v1.6.3
Import and adapt Neoscrypt from djm34 work (SM 5+ only)

Alright... clear.
But, :-)
I've tried ccminer-1.0-edition-djm neoscrypt, and it works just fine... as far as the (noob) eye can tell.
Using the supplied neoscrypt.bat, i already reach about 70 Mh/s per device...which is not bad,right?
I wonder why you would recompile djm's work into your builds,but choose to disable support for sm3.0 devices?

Epsylon3

legendary

Activity: 1484

Merit: 1082

ccminer/cpuminer developer

sorry, i cant help for that... ask in the noisy threads Wink

Topic: [ANN] ccminer 2.3 - opensource - GPL (tpruvot) - page 157. (Read 500193 times)