Author

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

legendary
Activity: 2955
Merit: 1050
I've always thought ......
thank you ckolivas Smiley
a very good summary for me  Smiley
hero member
Activity: 807
Merit: 500
Maybe we should save the "bitcoin is dead, long live the bitcoin" talk for when bitcoin is dead.  (OK, no one is talking about bitcoin being dead, but I'm seeing an awful lot of doom and gloom posts that may very well primarily come from the fact that the reward just halved even though it should obviously take time for "markets" to adjust).  It seems like I read a long time ago that bitcoin was designed with the expectancy that only large entities would be mining and most others would be using it as a currency.  That may not be correct as far as design is concerned, but if it was expected a year or two ago (when I read whatever I read), the only people this change will shed from the community are those who mine solely to sell and reap rewards (pity it won't shed scammers).  In such a scenario, as they fail to reap rewards and stop buying new hardware, the conversion should stabilize, and the primary purpose of bitcoin should continue to thrive for those who truly support it.
hero member
Activity: 981
Merit: 500
DIV - Your "Virtual Life" Secured and Decentralize
Not saying anyone is wrong. My experience based on 1 BFL single delivered on May 7th actually paid for an upgrade already. Plus about another 240$. The timeline for me has thus far sucked. I am in front of my expected earnings by a great deal but I hoped for better. I expect that it will continue to suck because of the ability to make new generations by shrinking die size. Still as long as I am not marginal before a die shrink I could likely use my older hardware for a while albeit losing more profits to power bills. By older I don't mean the single. It will likely be so underpowered in a week tops that my unit would make little to no money. Even in that week it wouldn't make any real money. What I ment is that though I dislike the potential for many many new generation products I do like that essentially anything with a USB port and an internet connection can be a piece of the BTC infrastructure.

Sure the GPU's could make you money depending on what you had and if you could upgrade them. I use a cheap Acer net top setup with an nVidia Ion card and and Atom CPU. No part of that is good for mining. I could buy hardware and get to where I was hashrate wise but my FPGA did only cost me 600 and change. New PS, MB, RAM, and 2-4 video cards would have likely cost me about as much but used far more power for the same hashrate. I didn't see GPU's in this case as any less dedicated hardware since I would only buy them for bitcoin mining.

My setup is around 110W for my DVR to mine making me money. My next setup will likely be even better power wise for a while. Then again the difficulty will also keep going up making you buy more hardware of accept less money per time unit.
member
Activity: 88
Merit: 10
Gliding...
I've always thought FPGAs were a waste of money. Assuming ASICs come in the next 2 months, indeed hardly anyone would have made a return on investment with FPGAs yet they will find themselves with ...

+1

Panda Mouse
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
I've always thought FPGAs were a waste of money. Assuming ASICs come in the next 2 months, indeed hardly anyone would have made a return on investment with FPGAs yet they will find themselves with devices that have no other realistic useful purpose - AKA doorstops. I have never spent a cent on FPGAs, do not own one, and have only gotten involved with their development when no one else could find solutions to awkward problems with them. On the other hand, GPUs have only just fallen below profitability, yet if you factor in resale value for them, they still don't look so bad compared to FPGAs, but mining long term on them seems a waste now. I never once believed GPU mining would die in the face of FPGAs unless the status quo was somehow magically maintained for years which I never believed would happen.

However, ASICs are a totally different ball game. They basically will redefine what mining means with bitcoin, where there is no point mining with anything else if any profit is to be made. They will make GPUs, and even FPGAs, look totally useless to mine with. 1 year from now, absolutely no one will be mining BTC on anything but ASICs, except for newbies to bitcoin mining, who will ask the obvious questions about GPU mining, and still even CPU mining.

I will sorely miss the "anyone can use their spare hardware to mine with" aspect to bitcoin mining. I honestly believe that is more true to the ideal of bitcoin, where everyone running a node was contributing to its security. However, what spare hardware people had has changed dramatically recently anyway as PCs are dramatically on the decline and people move to more portable devices with less CPU/GPU power in the form of tablets and phones etc. Alas the algorithm lends itself really well to ASIC based mining, meaning everything else will be a complete waste of time. Now while cgminer will continue to work on alternate cryptocurrencies, I honestly think all the alternative cryptocurrencies will go nowhere. The only reason to mine them is to find something that can be profitable by converting it to BTC.

Down the track, cgminer will indeed be used mostly to mine with dedicated ASIC hardware to mine BTC. GPU mining for BTC will be as irrelevant then as CPU mining is today. I don't like the fact that the network will be secured with devices from 4 or 5 manufacturers making hardware that serves only one purpose - btc mining. While BTC mining previously was still only in the hands of intel, amd and nvidia, the fact is it was not on their radar at all. Bitcoin mining was a lucky aside they did, where AMD/ATI GPUs happened to do better than anyone else, and anyone with spare cycles on their hardware could choose to contribute and earn a little on the side.

Long term, cgminer will be the lowest overhead c software to drive ASICs to do bitcoin mining, with lots of code in it that is no longer relevant to BTC mining. What I really worry about, is that new hardware will continue to come out frequently enough that people end up on a cycle of investing in hardware that basically never pays itself off as slightly newer hardware and higher diffs keep coming out. Sure at some stage the limits of technology will be reached, but given the best tech at the moment is going to be 65nm ASICs when CPUs are 28nm devices, I can see the cycle going on for some time, and then even if btc mining ASICs end up in line with CPU manufacturers, they still continue to evolve over time. Dramatic profits from ASICs will likely only last a couple of weeks at most for a lucky few. The rest of you who paid for devices that don't even exist yet will not be making any magical profit no matter how big the hashrate appears. Your proportion of the total bitcoin hashrate will remain pitiful.

Sigh...
hero member
Activity: 981
Merit: 500
DIV - Your "Virtual Life" Secured and Decentralize
I believed about 11 months ago GPU mining would die entirely because of FPGA's. I wasn't right. I was sure by now it would be old news.

CGMiner is what I use for my FPGA setup. Abandoning BTC entirely would be a loss for those that use CGMiners very advanced features to keep work piling up on their boxes like garbage in a round file. I don't think I will bet on GPU dying again. I may wait for it to happen this time.

PS everything seems great here. Working fast (WU dropped back to 11.9 but I had throttles so it was expected).
12133A
9R
0.00074178% Rejects on Stratum on Eclipse. That is amazing to me!
sr. member
Activity: 378
Merit: 250
Why is it so damn hot in here?
i strongly believe that BTC cgminer for GPU will be dead in a matter of weeks.
Thus, all the efforts now for cgminer development should be in the direction of LTC (scrypt) Smiley

be·lieve
[bih-leev], be·lieved, be·liev·ing.
verb (used without object)
1.
to have confidence in the truth, the existence, or the reliability of something, although without absolute proof that one is right in doing so.

I belive you are an asshat.
hero member
Activity: 607
Merit: 500
i strongly believe that BTC cgminer for GPU will be dead in a matter of weeks.
Thus, all the efforts now for cgminer development should be in the direction of LTC (scrypt) Smiley
legendary
Activity: 952
Merit: 1000
crazyates
i used and 12.8 drivers with 2.7 SDK and 11.11 with 2.5 SDK - no result((
will try 12.4 with 2.7 SDK tomorrow.....
with other drivers except 11.6 my comp reboots((
Well IIRC, scrypt requires 2.6 or newer, so 2.5 is out. 12.8 with the included ocl runtime should be your best bet. Idk then.  Tongue
member
Activity: 125
Merit: 10
crazyates
i used and 12.8 drivers with 2.7 SDK and 11.11 with 2.5 SDK - no result((
will try 12.4 with 2.7 SDK tomorrow.....
with other drivers except 11.6 my comp reboots((
legendary
Activity: 952
Merit: 1000
Can anyone help?
Windows XP
scrypt
hd6950
catalyst 11.6
app sdk 2.7
can't compile kernel
Code:
[2012-11-29 13:46:50] Error -11: Building Program (clBuildProgram)
[2012-11-29 13:46:50] C:\DOCUME~1\z\LOCALS~1\Temp\OCL270.tmp.cl(636): warning:
variable "ySIZE" was
          declared but never referenced
        const uint ySIZE = (1024/LOOKUP_GAP+(1024%LOOKUP_GAP>0));
                   ^

LOOP UNROLL: pragma unroll (line 582)
    Unrolled as requested!
LOOP UNROLL: pragma unroll (line 573)
    Unrolled as requested!
LOOP UNROLL: pragma unroll (line 664)
    Unrolled as requested!
LOOP UNROLL: pragma unroll (line 591)
    Unrolled as requested!
LOOP UNROLL: pragma unroll (line [2012-11-29 13:46:50] Failed to init GPU thread
 0, disabling device 0
with other drivers not running at all

From the AMD APP SDK Requirement Page, SDK2.7 requires drivers 12.4 or newer. I've never seen anyone else using 11.6 with 2.7.
member
Activity: 125
Merit: 10
Can anyone help?
Windows XP
scrypt
hd6950
catalyst 11.6
app sdk 2.7
can't compile kernel
Code:
[2012-11-29 13:46:50] Error -11: Building Program (clBuildProgram)
[2012-11-29 13:46:50] C:\DOCUME~1\z\LOCALS~1\Temp\OCL270.tmp.cl(636): warning:
variable "ySIZE" was
          declared but never referenced
        const uint ySIZE = (1024/LOOKUP_GAP+(1024%LOOKUP_GAP>0));
                   ^

LOOP UNROLL: pragma unroll (line 582)
    Unrolled as requested!
LOOP UNROLL: pragma unroll (line 573)
    Unrolled as requested!
LOOP UNROLL: pragma unroll (line 664)
    Unrolled as requested!
LOOP UNROLL: pragma unroll (line 591)
    Unrolled as requested!
LOOP UNROLL: pragma unroll (line [2012-11-29 13:46:50] Failed to init GPU thread
 0, disabling device 0
with other drivers not running at all
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
sr. member
Activity: 383
Merit: 250
Con Kolivas, Just noticed a possible bug on Windows. When I hit 'q' to exit cgminer it restarted cgminer. Possibly crashed which triggered the restart. Race condition? Or is it not checking for user quitting on restart code (when cgminer crashes)?

Edit: Cgminer 2.9.5
hero member
Activity: 807
Merit: 500
Please add --no-restart
That way it will not try to restart if it crashes, which is stopping it from dumping properly. Thanks.
Does this help? I truncated everything after the #2 because they all (737) said "No symbol table info available."
Code:
gdb cgminer core.15150
GNU gdb (GDB) Fedora (7.3-43.fc15)
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
...
Reading symbols from /usr/local/bin/cgminer...done.
[New LWP 15230]
[New LWP 15205]
[New LWP 15158]
[New LWP 15209]
[New LWP 15157]
[New LWP 15150]
[New LWP 15210]
[New LWP 15207]
[New LWP 15202]
[New LWP 15206]
[New LWP 15203]
[New LWP 15212]
[New LWP 15208]
Missing separate debuginfo for
Try: yum --disablerepo='*' --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/3a/8fe6cb0063d56fc9be76ecd085c05f1b8a76e6
[Thread debugging using libthread_db enabled]
Cannot find new threads: generic error
Core was generated by `cgminer -o http://GBTPOOL:GWPORT -O x:y'.
Program terminated with signal 11, Segmentation fault.
#0  0x0000003c6f67e8c1 in strcat () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install cyrus-sasl-lib-2.1.23-18.fc15.x86_64 glibc-2.14.1-5.x86_64 keyutils-libs-1.2-7.fc15.x86_64 krb5-libs-1.9.1-5.fc15.x86_64 libX11-1.4.3-1.fc15.x86_64 libXau-1.0.6-2.fc15.x86_64 libXext-1.2.0-2.fc15.x86_64 libXinerama-1.1.1-2.fc15.x86_64 libcom_err-1.41.14-2.fc15.x86_64 libcurl-7.21.3-11.fc15.x86_64 libgcc-4.6.0-10.fc15.x86_64 libidn-1.19-2.fc15.x86_64 libselinux-2.0.99-4.fc15.x86_64 libssh2-1.2.7-1.fc15.x86_64 libstdc++-4.6.0-10.fc15.x86_64 libxcb-1.7-2.fc15.x86_64 mesa-libGLU-7.11-1.fc15.x86_64 ncurses-libs-5.8-2.20110319.fc15.x86_64 nspr-4.8.8-1.fc15.x86_64 nss-3.12.10-6.fc15.x86_64 nss-mdns-0.10-9.fc15.x86_64 nss-softokn-freebl-3.12.10-2.fc15.x86_64 nss-util-3.12.10-1.fc15.x86_64 openldap-2.4.24-3.fc15.x86_64 openssl-1.0.0g-1.fc15.x86_64 xorg-x11-drv-catalyst-libs-11.6-1.fc15.x86_64 zlib-1.2.5-3.fc15.x86_64
(gdb) bt full
#0  0x0000003c6f67e8c1 in strcat () from /lib64/libc.so.6
No symbol table info available.
#1  0x00000000004093f0 in submit_upstream_work (work=0x7f67e4000c00, curl=0x7f67e400b5f0,
    resubmit=false) at cgminer.c:2331
        gbt_block = "02000000ca538130d3b31ccc24be835ba05bf2b8c41f8dfe8c112584ca03", '0' , "8d4ca763df01df8377efc6a798d0607e3325259b4923e603308d8237d8ece2b97a22b650eae0041a11865698400100000001", '0' , "ffffffff4b034e34030e"...
        varint = 0x3030303030303030

        header = 0x3136646362313465

        data = "76a914dcacb1cb4f31a6a3a239ae0199626bce00a72c3788acacc59502000000001976a91428220c"
        hexstr = 0x3838376332663736

        val = 0x3633343139613637
        res = 0x3931303030303030
        err = 0x3030303030306461
        s = "4188acb896", '0' , "1976a914f52651ec8fe199ea975c63fc36369364c31fe80288ac980b", '0' , "1976a9140f9bfe4cfd6c45c623a77d8087982c41a6fef69588ac50a2", '0' , "1976a914cccdfc3b5e7ae849041e954dc48f47b96b2219f4"...
        rc = 57
        thr_id = 959918646
        cgpu = 0x3239333738353534
        pool = 0x6465343939663962
        rolltime = 1681469798
        hash32 = 0x6639313265646462
        tv_submit = {tv_sec = 7306075964502533688, tv_usec = 4121744960866432049}
        tv_submit_reply = {tv_sec = 4134645543713452080, tv_usec = 3978477492665463857}
        hashshow = "ad", '0' , "1976a9141f24c264b0f47ece27326a3905be9b91fd1da97788ac34"
        worktime = "ac4c320200000000001976a914bd43b675c496b8b13bde490465ea355a94136faf88acc0543a00000000001976a914bcd6b30774cc7bdcc922e4f1817ca035667b18cd88acd46e1800000000001976a9147cb7a1d86ddddcdc8ef192cbd0bc67a370524b"
#2  0x3931303030303030 in ?? ()
No symbol table info available.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
One question about "Best share:" ... is it working correctly when Solo Mining?
Yes
hero member
Activity: 547
Merit: 531
First bits: 12good
One question about "Best share:" ... is it working correctly when Solo Mining?

Thanks
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
In case anyone wants me to try something else...
Debug build would be helpful. If you're running fedora that suggests you're building it yourself. If that's the case, add "-g" to your CFLAGS, rebuild your cgminer 2.9.5 (without stripping the file), enable coredumps with "ulimit -c unlimited" and then run whatever it is that's crashing. Once you get a "core dumped" message at the end of running it, then run:
gdb cgminer core
bt full

And post the information from that please.
I'm getting "No stack."  I assume that makes it obvious I've never done this before...

ETA:
Code:
cat /usr/src/cgminer-2.9.5/Makefile | grep CFLAGS\ =
CFLAGS = -I/usr/src/ati-stream-sdk-v2.1-lnx64/include -g
Also, FYI, this is the exact error I was getting in 2.9.4 on GBT only:
Code:
Crashed with signal 11! Will attempt to restart--- Failed to restart, exiting nowing
latest version, x86_64 linux, build with -02 -Wall
I'm not sure whether the fact that it is also happening on that other miner will make you laugh or cry...
Well that's my code so it's no surprise...

Please add --no-restart
That way it will not try to restart if it crashes, which is stopping it from dumping properly. Thanks.
hero member
Activity: 807
Merit: 500
In case anyone wants me to try something else...
Debug build would be helpful. If you're running fedora that suggests you're building it yourself. If that's the case, add "-g" to your CFLAGS, rebuild your cgminer 2.9.5 (without stripping the file), enable coredumps with "ulimit -c unlimited" and then run whatever it is that's crashing. Once you get a "core dumped" message at the end of running it, then run:
gdb cgminer core
bt full

And post the information from that please.
I'm getting "No stack."  I assume that makes it obvious I've never done this before...

ETA:
Code:
cat /usr/src/cgminer-2.9.5/Makefile | grep CFLAGS\ =
CFLAGS = -I/usr/src/ati-stream-sdk-v2.1-lnx64/include -g
Also, FYI, this is the exact error I was getting in 2.9.4 on GBT only:
Code:
Crashed with signal 11! Will attempt to restart--- Failed to restart, exiting nowing
latest version, x86_64 linux, build with -02 -Wall
I'm not sure whether the fact that it is also happening on that other miner will make you laugh or cry...
hero member
Activity: 981
Merit: 500
DIV - Your "Virtual Life" Secured and Decentralize
I am using eclipses stratum on US1.
3849 accepted so far
2 rejected.
Compared to 2 days of 1.2% I am very happy with the improvement.

CPU Miner was abandoned and Con made Cpu Gpu Miner
Jump to: