Bitcoin Forum
October 15, 2018, 08:45:51 PM *
News: Make sure you are not using versions of Bitcoin Core other than 0.17.0 [Torrent], 0.16.3, 0.15.2, or 0.14.3. More info.
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 [437] 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 ... 845 »
  Print  
Author Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.1  (Read 5765767 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
MashRinx
Sr. Member
****
Offline Offline

Activity: 390
Merit: 250



View Profile
January 30, 2013, 03:26:00 AM
 #8721

When I initially started mining, I had issues with false-positives from several different Antivirus products and even adding the file/folder exclusions didn't help.  If I remember correctly, Avast was one that I never was able to resolve so I moved on to something else. 

That's been over a year ago though, so they may have improved how their exclusions worked from when I tried.
1539636351
Hero Member
*
Offline Offline

Posts: 1539636351

View Profile Personal Message (Offline)

Ignore
1539636351
Reply with quote  #2

1539636351
Report to moderator
1539636351
Hero Member
*
Offline Offline

Posts: 1539636351

View Profile Personal Message (Offline)

Ignore
1539636351
Reply with quote  #2

1539636351
Report to moderator
1539636351
Hero Member
*
Offline Offline

Posts: 1539636351

View Profile Personal Message (Offline)

Ignore
1539636351
Reply with quote  #2

1539636351
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1539636351
Hero Member
*
Offline Offline

Posts: 1539636351

View Profile Personal Message (Offline)

Ignore
1539636351
Reply with quote  #2

1539636351
Report to moderator
1539636351
Hero Member
*
Offline Offline

Posts: 1539636351

View Profile Personal Message (Offline)

Ignore
1539636351
Reply with quote  #2

1539636351
Report to moderator
1539636351
Hero Member
*
Offline Offline

Posts: 1539636351

View Profile Personal Message (Offline)

Ignore
1539636351
Reply with quote  #2

1539636351
Report to moderator
crazyates
Legendary
*
Offline Offline

Activity: 952
Merit: 1000



View Profile
January 30, 2013, 04:11:01 AM
 #8722

2.10.4j
Question: Will these updates be merged into conman's 2.10.5? When will that happen?

Tips? 1crazy8pMqgwJ7tX7ZPZmyPwFbc6xZKM9
Previous Trade History - Sale Thread
kano
Legendary
*
Offline Offline

Activity: 2604
Merit: 1054


Linux since 1997 RedHat 4


View Profile
January 30, 2013, 07:23:40 AM
 #8723

2.10.4j
Question: Will these updates be merged into conman's 2.10.5? When will that happen?
Yes they are very likely to be part of 2.10.5 - but all the major changes in there are USB/FPGA/ASIC related so until an actual ASIC turns up, I'm not sure if ckolivas wants the terror of looking through my changes and committing (or rejecting) them yet Smiley

This pull request to ckolivas has them all up to 'm':
https://github.com/ckolivas/cgminer/pull/380

It's currently at + 1,859 additions - 924 deletions
So there's quite a bit to it.

Actually I probably should delete 2.10.4j ... and make a 2.10.4m ... 'm' will be the last safe one for a short while.
... also, 'j' causes an incorrect message if your MMQ fails - and I'm not sure if there are other side effects to that message.

Well I'm working on USB hotplug at the moment.
Though I'll work in the usb2 branch - not the master for the real hotplug code.
The last lot of changes (m) were the lead up to getting it ready for USB hotplug, now I gotta actually do it Smiley

Actually - that made me decide - OK I've made an 'm' now in my downloads and also - that's where my master branch in my git will stop while I work on hotplug
I've also deleted the 2.10.4j version since it had that minor bug that is fixed in 2.4.10m
https://github.com/kanoi/cgminer-binaries

And of course my git master branch:
https://github.com/kanoi/cgminer

Edit: 'j' post on the previous page now updated to 'm'
https://bitcointalk.org/index.php?topic=28402.msg1480806#msg1480806

Pool: https://kano.is Here on Bitcointalk: Forum BTC: 1KanoPb8cKYqNrswjaA8cRDk4FAS9eDMLU
FreeNode IRC: irc.freenode.net channel #kano.is Majority developer of the ckpool code
Help keep Bitcoin secure by mining on pools with full block verification on all blocks - and NO empty blocks!
PatMan
Hero Member
*****
Offline Offline

Activity: 924
Merit: 1000


Watch out for the "Neg-Rep-Dogie-Police".....


View Profile WWW
January 30, 2013, 11:35:32 PM
 #8724

2.10.4j
Question: Will these updates be merged into conman's 2.10.5? When will that happen?
Yes they are very likely to be part of 2.10.5 - but all the major changes in there are USB/FPGA/ASIC related so until an actual ASIC turns up, I'm not sure if ckolivas wants the terror of looking through my changes and committing (or rejecting) them yet Smiley

This pull request to ckolivas has them all up to 'm':
https://github.com/ckolivas/cgminer/pull/380

It's currently at + 1,859 additions - 924 deletions
So there's quite a bit to it.

Actually I probably should delete 2.10.4j ... and make a 2.10.4m ... 'm' will be the last safe one for a short while.
... also, 'j' causes an incorrect message if your MMQ fails - and I'm not sure if there are other side effects to that message.

Well I'm working on USB hotplug at the moment.
Though I'll work in the usb2 branch - not the master for the real hotplug code.
The last lot of changes (m) were the lead up to getting it ready for USB hotplug, now I gotta actually do it Smiley

Actually - that made me decide - OK I've made an 'm' now in my downloads and also - that's where my master branch in my git will stop while I work on hotplug
I've also deleted the 2.10.4j version since it had that minor bug that is fixed in 2.4.10m
https://github.com/kanoi/cgminer-binaries

And of course my git master branch:
https://github.com/kanoi/cgminer

Edit: 'j' post on the previous page now updated to 'm'
https://bitcointalk.org/index.php?topic=28402.msg1480806#msg1480806

Thanks again Kano. Loaded & running, all good.

"When one person is deluded it is called insanity - when many people are deluded it is called religion" - Robert M. Pirsig.  I don't want your coins, I want change.
Amazon UK BTC payment service - https://bitcointalk.org/index.php?topic=301229.0 - with FREE delivery!
http://www.ae911truth.org/ - http://rethink911.org/ - http://rememberbuilding7.org/
YipYip
Hero Member
*****
Offline Offline

Activity: 574
Merit: 500



View Profile
January 31, 2013, 08:22:42 PM
 #8725

Trying to get a Saphire 5970 to run up

I have 3 XFX Blk Edition untis that are working well

The Saphire just by itself will run for about 30 seconds and then White/blue screen  ...from reading it is being driven too hard Huh

Here are the settings

cgminer --scrypt -o http://yourpool.com -u username -p password --thread-concurrency 5000-8000 -I 18 -g 1 -w 256

ATI drivers 12.8

What cgminer settings can you suggest to give it an easier time and also what clock & memory settings should i have as well ?

(This may not be relevant....if i run it as part of a 3 cards 1 of the GPU's goes SICK and then eveything crashes after 1-2 mins)

OBJECT NOT FOUND
SAC
Sr. Member
****
Offline Offline

Activity: 322
Merit: 250


View Profile
January 31, 2013, 09:33:19 PM
 #8726

Trying to get a Saphire 5970 to run up

I have 3 XFX Blk Edition untis that are working well

The Saphire just by itself will run for about 30 seconds and then White/blue screen  ...from reading it is being driven too hard Huh

Here are the settings

cgminer --scrypt -o http://yourpool.com -u username -p password --thread-concurrency 8000,8000 -I 18,18 -g 1 -w 256,256

ATI drivers 12.8

What cgminer settings can you suggest to give it an easier time and also what clock & memory settings should i have as well ?

(This may not be relevant....if i run it as part of a 3 cards 1 of the GPU's goes SICK and then eveything crashes after 1-2 mins)



Try like I have it edited in your post and I use 780 for the engine memory at 1160 or 1185 depending on the card I have in use.


Edit: Also --auto-fan --auto-gpu added on the end could be of use to you. An example of the .conf file you can use to have most of these setting automatically applied on startup.

Code:
cat .cgminer/cgminer.conf-ltc
{
"pools" : [
{
        "url" : "http://yourpool.com:9332",
        "user" : "User.1",
          "pass" : "1"
},
{
                "url" : "stratum+tcp://yourpool.com:3333",
                "user" : "User.0",
                "pass" : "12345"
    },
    {
        "url" : "http://192.168.0.187:9332",
        "user" : "miners",
        "pass" : "litecoin"
    }
],

"auto-fan" : true,
"auto-gpu" : true,
"temp-target" : "79",
"gpu-fan" : "0-100",
"intensity" : "18,18,18",
"vectors" : "4,4,4",
"worksize" : "256,256,256",
"thread-concurrency" : "6720,8000,8000",
"log" : "5",
"queue" : "1",
"retry-pause" : "5",
"scan-time" : "60",
"donation" : "0",
"shares" : "0",
"kernel-path" : "/usr/local/bin"
}

The script I use to start you want to be using the export commands regardless of using script to start..

Code:
cat ltc.sh
export GPU_USE_SYNC_OBJECTS=1
export GPU_MAX_ALLOC_PERCENT=100
export DISPLAY=:0
cd ~
cp .cgminer/cgminer.conf-ltc .cgminer/cgminer.conf

~/cgminer-2.10.4 --no-submit-stale --scrypt --api-listen --api-allow W:127.0.0.1,R:192.168.0.0/24 -g 1

The script to set the video speeds.

Code:
cat vset.sh
DISPLAY=:0 aticonfig --od-enable --adapter=all
DISPLAY=:0 aticonfig --od-setclocks=780,1160 --adapter=2
DISPLAY=:0 aticonfig --od-setclocks=780,1160 --adapter=1
DISPLAY=:0 aticonfig --od-setclocks=835,1185 --adapter=0
DISPLAY=:0 aticonfig --odgc --adapter=all
YipYip
Hero Member
*****
Offline Offline

Activity: 574
Merit: 500



View Profile
February 01, 2013, 12:16:39 AM
 #8727

Trying to get a Saphire 5970 to run up

I have 3 XFX Blk Edition untis that are working well

The Saphire just by itself will run for about 30 seconds and then White/blue screen  ...from reading it is being driven too hard Huh

Here are the settings

cgminer --scrypt -o http://yourpool.com -u username -p password --thread-concurrency 8000,8000 -I 18,18 -g 1 -w 256,256

ATI drivers 12.8

What cgminer settings can you suggest to give it an easier time and also what clock & memory settings should i have as well ?

(This may not be relevant....if i run it as part of a 3 cards 1 of the GPU's goes SICK and then eveything crashes after 1-2 mins)



Try like I have it edited in your post and I use 780 for the engine memory at 1160 or 1185 depending on the card I have in use.


Edit: Also --auto-fan --auto-gpu added on the end could be of use to you. An example of the .conf file you can use to have most of these setting automatically applied on startup.

Code:
cat .cgminer/cgminer.conf-ltc
{
"pools" : [
{
        "url" : "http://yourpool.com:9332",
        "user" : "User.1",
          "pass" : "1"
},
{
                "url" : "stratum+tcp://yourpool.com:3333",
                "user" : "User.0",
                "pass" : "12345"
    },
    {
        "url" : "http://192.168.0.187:9332",
        "user" : "miners",
        "pass" : "litecoin"
    }
],

"auto-fan" : true,
"auto-gpu" : true,
"temp-target" : "79",
"gpu-fan" : "0-100",
"intensity" : "18,18,18",
"vectors" : "4,4,4",
"worksize" : "256,256,256",
"thread-concurrency" : "6720,8000,8000",
"log" : "5",
"queue" : "1",
"retry-pause" : "5",
"scan-time" : "60",
"donation" : "0",
"shares" : "0",
"kernel-path" : "/usr/local/bin"
}

The script I use to start you want to be using the export commands regardless of using script to start..

Code:
cat ltc.sh
export GPU_USE_SYNC_OBJECTS=1
export GPU_MAX_ALLOC_PERCENT=100
export DISPLAY=:0
cd ~
cp .cgminer/cgminer.conf-ltc .cgminer/cgminer.conf

~/cgminer-2.10.4 --no-submit-stale --scrypt --api-listen --api-allow W:127.0.0.1,R:192.168.0.0/24 -g 1

The script to set the video speeds.

Code:
cat vset.sh
DISPLAY=:0 aticonfig --od-enable --adapter=all
DISPLAY=:0 aticonfig --od-setclocks=780,1160 --adapter=2
DISPLAY=:0 aticonfig --od-setclocks=780,1160 --adapter=1
DISPLAY=:0 aticonfig --od-setclocks=835,1185 --adapter=0
DISPLAY=:0 aticonfig --odgc --adapter=all

Thanks Dude..will give it a try tonight Cheesy

OBJECT NOT FOUND
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2674
Merit: 1143


Ruu \o/


View Profile WWW
February 01, 2013, 01:18:24 AM
 #8728

Why would you use aticonfig when you can change the clocks directly with cgminer?

Developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org, 1% Fee Solo mining at solo.ckpool.org
-ck
SAC
Sr. Member
****
Offline Offline

Activity: 322
Merit: 250


View Profile
February 01, 2013, 04:00:35 AM
 #8729

Why would you use aticonfig when you can change the clocks directly with cgminer?

Never works with ltc on my machines btc sets them to exactly what I to use in the .conf and as I have said with ltc good luck with that..

Edit: Should add it appears to go with the default of the card involved in ltc mining as I have two 6970s that their default speeds are the sweet spot for kh/s rate those two I never have to set the speeds as they are already where they need to be once it starts up. Any other cards I check the speeds on after it starts are at their default values then they need to be set to where the speeds need to be for ltc mining.
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2674
Merit: 1143


Ruu \o/


View Profile WWW
February 01, 2013, 05:02:04 AM
 #8730

Why would you use aticonfig when you can change the clocks directly with cgminer?

Never works with ltc on my machines btc sets them to exactly what I to use in the .conf and as I have said with ltc good luck with that..

Edit: Should add it appears to go with the default of the card involved in ltc mining as I have two 6970s that their default speeds are the sweet spot for kh/s rate those two I never have to set the speeds as they are already where they need to be once it starts up. Any other cards I check the speeds on after it starts are at their default values then they need to be set to where the speeds need to be for ltc mining.
That doesn't make much sense unless you use settings that wouldn't work with the display library - and usually that involves setting the memory clock much lower than the engine clock which you don't do on LTC. I've mined LTC numerous times and set clocks just fine with cgminer itself.

Developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org, 1% Fee Solo mining at solo.ckpool.org
-ck
SAC
Sr. Member
****
Offline Offline

Activity: 322
Merit: 250


View Profile
February 01, 2013, 07:36:36 AM
 #8731

Why would you use aticonfig when you can change the clocks directly with cgminer?

Never works with ltc on my machines btc sets them to exactly what I to use in the .conf and as I have said with ltc good luck with that..

Edit: Should add it appears to go with the default of the card involved in ltc mining as I have two 6970s that their default speeds are the sweet spot for kh/s rate those two I never have to set the speeds as they are already where they need to be once it starts up. Any other cards I check the speeds on after it starts are at their default values then they need to be set to where the speeds need to be for ltc mining.
That doesn't make much sense unless you use settings that wouldn't work with the display library - and usually that involves setting the memory clock much lower than the engine clock which you don't do on LTC. I've mined LTC numerous times and set clocks just fine with cgminer itself.

Sense or not it does it here is a machine I just put the proper values I need into the .conf and it appears to set the memory but not the engine to what I need and have specified.

Code:
miner4@miner4:~$ odg

Adapter 0 - ATI Radeon HD 5800 Series 
                            Core (MHz)    Memory (MHz)
           Current Clocks :    925           1185
             Current Peak :    925           1185
  Configurable Peak Range : [600-875]     [300-1200]
                 GPU load :    99%

Adapter 1 - ATI Radeon HD 5900 Series
                            Core (MHz)    Memory (MHz)
           Current Clocks :    800           1160
             Current Peak :    800           1160
  Configurable Peak Range : [550-1000]     [300-1500]
                 GPU load :    99%

Adapter 2 - ATI Radeon HD 5900 Series
                            Core (MHz)    Memory (MHz)
           Current Clocks :    800           1160
             Current Peak :    800           1160
  Configurable Peak Range : [550-1000]     [300-1500]
                 GPU load :    99%

Code:
miner4@miner4:~$ cat .cgminer/cgminer.conf
{
"pools" : [
....
],

"auto-fan" : true,
"auto-gpu" : true,
"temp-target" : "79",
"gpu-fan" : "0-100",
"intensity" : "18,18,18",
"gpu-engine" : "0-835,0-780,0-780",
"gpu-memclock" : "1185,1160,1160",
"vectors" : "4,4,4",
"worksize" : "256,256,256",
"thread-concurrency" : "6720,8000,8000",
"log" : "5",
"queue" : "1",
"retry-pause" : "5",
"scan-time" : "60",
"donation" : "0",
"shares" : "0",
"kernel-path" : "/usr/local/bin"
}
YipYip
Hero Member
*****
Offline Offline

Activity: 574
Merit: 500



View Profile
February 01, 2013, 10:35:26 AM
 #8732

Why would you use aticonfig when you can change the clocks directly with cgminer?

Never works with ltc on my machines btc sets them to exactly what I to use in the .conf and as I have said with ltc good luck with that..

Edit: Should add it appears to go with the default of the card involved in ltc mining as I have two 6970s that their default speeds are the sweet spot for kh/s rate those two I never have to set the speeds as they are already where they need to be once it starts up. Any other cards I check the speeds on after it starts are at their default values then they need to be set to where the speeds need to be for ltc mining.
That doesn't make much sense unless you use settings that wouldn't work with the display library - and usually that involves setting the memory clock much lower than the engine clock which you don't do on LTC. I've mined LTC numerous times and set clocks just fine with cgminer itself.

I have played around with the settings you guys have perscribed clock speed ,memory settings etc etc

I have tried 2 x MSI 890 FX mobo ATI 12.8 drivers...even took teh intensity down to 9 (it gave me 79k/hash for both GPU's ..lol )

The card no matter what after ~ 1 min white/blue/grey...gone

I have had 3 x XFX 5970's working fine in these boards etc... Can i safely say the card is dead Huh

OBJECT NOT FOUND
SAC
Sr. Member
****
Offline Offline

Activity: 322
Merit: 250


View Profile
February 01, 2013, 06:37:45 PM
 #8733


I have tried 2 x MSI 890 FX mobo ATI 12.8 drivers...even took teh intensity down to 9 (it gave me 79k/hash for both GPU's ..lol )

The card no matter what after ~ 1 min white/blue/grey...gone

I have had 3 x XFX 5970's working fine in these boards etc... Can i safely say the card is dead Huh

Good chance of it although usually when dead they won't hash at all. Either that or one core will die on you, have had that happen as well.
loshia
Legendary
*
Offline Offline

Activity: 1610
Merit: 1000


View Profile
February 01, 2013, 09:00:11 PM
 #8734

Guy's

I am running my lancelot cluster on tp-link openwrt platform with 64M of ram. I am noticing the restart of my system because cgminer 2.10.4 slowly and steadily eats all of the available free RAM about 45M.

And when cgminer eats all memory (45M) it takes about 2-3 days following happens

Feb  1 14:36:53 cgminer kern.warn kernel: [281314.280000] miner 11 invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=0
Kernel kills cgminer because system is running out of ram

Is there a way to reduce mem usage when cgminer is compiled for openwrt?

10X
PS: Otherwise it runs perfect same as when my pc i386 was used. No hashing speed decrease. The only difference was that my PC had 4G of RAM Sad

Please help the Led Boy aka Bicknellski to make us a nice Christmas led tree and pay WASP membership fee here:
https://bitcointalk.org/index.php?topic=643999.msg7191563#msg7191563
And remember Bicknellski is not collecting money from community;D
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2674
Merit: 1143


Ruu \o/


View Profile WWW
February 01, 2013, 09:15:03 PM
 #8735

Guy's

I am running my lancelot cluster on tp-link openwrt platform with 64M of ram. I am noticing the restart of my system because cgminer 2.10.4 slowly and steadily eats all of the available free RAM about 45M.

And when cgminer eats all memory (45M) it takes about 2-3 days following happens

Feb  1 14:36:53 cgminer kern.warn kernel: [281314.280000] miner 11 invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=0
Kernel kills cgminer because system is running out of ram

Is there a way to reduce mem usage when cgminer is compiled for openwrt?

10X
PS: Otherwise it runs perfect same as when my pc i386 was used. No hashing speed decrease. The only difference was that my PC had 4G of RAM Sad

Yes there is a very slow memory leak in it which only becomes a problem at high hashrates on machines with little ram. A fix will be coming soon.

Developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org, 1% Fee Solo mining at solo.ckpool.org
-ck
loshia
Legendary
*
Offline Offline

Activity: 1610
Merit: 1000


View Profile
February 01, 2013, 09:37:37 PM
 #8736


Yes there is a very slow memory leak in it which only becomes a problem at high hashrates on machines with little ram. A fix will be coming soon.
Super!
My hash rate is about 9200 Mh/s on that host. Probably that is the reason why jgarzik has frequent restarts with his Avalon...

Thanks once again ..I am watching git closely and will compile/upgrade new version immediately and let you know how it goes
10X

Please help the Led Boy aka Bicknellski to make us a nice Christmas led tree and pay WASP membership fee here:
https://bitcointalk.org/index.php?topic=643999.msg7191563#msg7191563
And remember Bicknellski is not collecting money from community;D
PatronDragon
Sr. Member
****
Offline Offline

Activity: 291
Merit: 250


View Profile
February 01, 2013, 10:05:19 PM
 #8737

I use 2 videocards 7970 and 5870 but CGminer writes me that the incorrect file of a configuration! Write to me as the configuration file has to look correctly!
CrazyGuy
Legendary
*
Offline Offline

Activity: 1966
Merit: 1000



View Profile
February 02, 2013, 12:57:38 AM
 #8738

I am having some issues compiling 2.10.4. I've been following the same steps to compile for months and can compile 2.9.7 and prior versions without issue, it's just 2.10.x versions. I think it might be a dependency, but I'm not that linux savy. I have run "apt-get update && apt-get upgrade" to make sure things are current. This is running on a Atom based Mini-ITX MB running Debian 6 with 7 BFLs. (Other than this new compile issue, it's been running great for 6 months)

I did read back around 15 pages to the point where 2.10.0 was released and did not see anyone having any issues with compiling. I also checked the README.txt and it looks like I have all the dependencies. If anyone can point me in the right direction, I'd appreciate it. Thank you.

Code:
CFLAGS="-g -O2 -W -Wall" ./autogen.sh --enable-bitforce --with-libudev
Returns the following:
Code:
  curses.TUI...........: FOUND: -lncurses
Looks OK, but then I get these errors when running "make": (I have tried make clean first as well)
Code:
util.c:207: error: âCURLOPT_TCP_KEEPALIVEâ undeclared (first use in this function)

That looks like your curl installation is a version that somehow should support CURLOPT_TCP_KEEPALIVE (version 7.25.0+) but then actually doesn't.

That should not happen since it is supposed to detect what version of curl you have installed and choose appropriate support. Perhaps you have only a partly installed or mixed installation of libcurl development libraries.


I did an apt-get remove libcurl4-gnutls-dev && apt-get install libcurl4-gnutls-dev

Code:
Unpacking libcurl4-gnutls-dev (from .../libcurl4-gnutls-dev_7.21.0-2.1+squeeze2_i386.deb) ...
Processing triggers for man-db ...
Setting up libcurl4-gnutls-dev (7.21.0-2.1+squeeze2) ...
So is that the wrong version? (Still no love on the make clean / make) Any clue on how to get the 7.25.0+ version you speak of?
Thank you for your time.

It's still supposed to work with older curls. Somewhere it is thinking you have a later version installed which you don't. Anyway I usually install libcurl4-openssl-dev

I was getting the exact same compilation errors today upgrading from 2.9.6. Ubuntu 12.04 apt-get would not install higher than 7.22.0-3ubuntu4. Instead of messing around with it further, I just went ahead and updated to 12.10 and low and behold, i've now got version 7.27.0 of libcurl4-openssl-dev. CGminer compiles fine now.

ASICPuppy.net ASIC Mining Hardware and Accessories - 2Pacs in stock!
kano
Legendary
*
Offline Offline

Activity: 2604
Merit: 1054


Linux since 1997 RedHat 4


View Profile
February 02, 2013, 01:33:29 AM
 #8739

Just for anyone interested while I work on it.

https://github.com/kanoi/cgminer/commits/usb2
Hotplug (currently v0.1) for usbutils.c (that uses libusb) devices.

So far, the usbutils devices are BFL and MMQ
I've been doing all my testing with the BFL (no MMQ testing done yet)
Works fine as it is with BFL already ... and 'should' work with MMQ Smiley

All new devices that are built with usbutils.c will automatically be hotplug also.
(so that will include any ASIC drivers written by us)

I'll get around to converting the Icarus driver to usbutils one day ... to make ICA, CM1 & LOT hotplug also
(though that CM1 name will need a change Tongue ... maybe CMR)
But it's low on the priority at the moment, my todo list has quite a few things in it that I want to do
(including enhancements to this basic hotplug)

Edit:
1) When a usbutils device disappears it says on the screen "ZOMBIE" (not dead)
That's also automatic (like hotplug is)
API says No Device=true
2) Hotplug devices say a message on the screen like:
"Hotplug: BitForce added BFL 2"
3) The Hotplug devices don't show in the device list section of the curses screen
I haven't decided how to handle that yet

Pool: https://kano.is Here on Bitcointalk: Forum BTC: 1KanoPb8cKYqNrswjaA8cRDk4FAS9eDMLU
FreeNode IRC: irc.freenode.net channel #kano.is Majority developer of the ckpool code
Help keep Bitcoin secure by mining on pools with full block verification on all blocks - and NO empty blocks!
loshia
Legendary
*
Offline Offline

Activity: 1610
Merit: 1000


View Profile
February 02, 2013, 10:21:26 AM
 #8740

Kon,

I saw your memleak commit an i am testing it already.
However i am not sure though, there might be some other memleaks when calling pool_active which is happening quite often. I am attaching valgrind output just in case

The other stuff seemed not to be freed on cgminer exit which is not an issue:) Or i think so..
10X

==8359== HEAP SUMMARY:
==8359==     in use at exit: 908,508 bytes in 4,143 blocks
==8359==   total heap usage: 31,624 allocs, 27,481 frees, 41,232,886 bytes allocated
==8359==
==8359== 10 bytes in 2 blocks are definitely lost in loss record 24 of 212
==8359==    at 0x4C2B6CD: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==8359==    by 0x5C83D71: strdup (strdup.c:43)
==8359==    by 0x41F7F0: extract_sockaddr (util.c:871)
==8359==    by 0x404DB3: detect_stratum (cgminer.c:558)
==8359==    by 0x404EA0: set_url (cgminer.c:582)
==8359==    by 0x433E98: parse_one (parse.c:110)
==8359==    by 0x4336B9: opt_parse (opt.c:213)
==8359==    by 0x41BB19: main (cgminer.c:6454)
==8359==
==8359== 32 bytes in 1 blocks are definitely lost in loss record 73 of 212
==8359==    at 0x4C29DB4: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==8359==    by 0x403F4A: string_elist_add (miner.h:528)
==8359==    by 0x404C7F: add_serial (cgminer.c:507)
==8359==    by 0x433E98: parse_one (parse.c:110)
==8359==    by 0x4336B9: opt_parse (opt.c:213)
==8359==    by 0x41BB19: main (cgminer.c:6454)
==8359==
==8359== 35 bytes in 2 blocks are definitely lost in loss record 75 of 212
==8359==    at 0x4C2B6CD: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==8359==    by 0x5C83D71: strdup (strdup.c:43)
==8359==    by 0x41F810: extract_sockaddr (util.c:872)
==8359==    by 0x404DB3: detect_stratum (cgminer.c:558)
==8359==    by 0x404EA0: set_url (cgminer.c:582)
==8359==    by 0x433E98: parse_one (parse.c:110)
==8359==    by 0x4336B9: opt_parse (opt.c:213)
==8359==    by 0x41BB19: main (cgminer.c:6454)
==8359==
==8359== 44 bytes in 1 blocks are definitely lost in loss record 82 of 212
==8359==    at 0x4C29DB4: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==8359==    by 0x41D624: resp_hdr_cb (util.c:129)
==8359==    by 0x4E497F2: Curl_client_write (in /usr/lib/x86_64-linux-gnu/libcurl.so.4.2.0)
==8359==    by 0x4E4832D: Curl_http_readwrite_headers (in /usr/lib/x86_64-linux-gnu/libcurl.so.4.2.0)
==8359==    by 0x4E5FC39: Curl_readwrite (in /usr/lib/x86_64-linux-gnu/libcurl.so.4.2.0)
==8359==    by 0x4E61527: Huh (in /usr/lib/x86_64-linux-gnu/libcurl.so.4.2.0)
==8359==    by 0x41E3A9: json_rpc_call (util.c:377)
==8359==    by 0x414AC1: pool_active (cgminer.c:4807)
==8359==    by 0x417D70: watchpool_thread (cgminer.c:5757)
==8359==    by 0x52A1E99: start_thread (pthread_create.c:308)
==8359==    by 0x5CEECBC: clone (clone.S:112)
==8359==
==8359== 49 bytes in 1 blocks are definitely lost in loss record 89 of 212
==8359==    at 0x4C29DB4: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==8359==    by 0x41D624: resp_hdr_cb (util.c:129)
==8359==    by 0x4E497F2: Curl_client_write (in /usr/lib/x86_64-linux-gnu/libcurl.so.4.2.0)
==8359==    by 0x4E4832D: Curl_http_readwrite_headers (in /usr/lib/x86_64-linux-gnu/libcurl.so.4.2.0)
==8359==    by 0x4E5FC39: Curl_readwrite (in /usr/lib/x86_64-linux-gnu/libcurl.so.4.2.0)
==8359==    by 0x4E61527: Huh (in /usr/lib/x86_64-linux-gnu/libcurl.so.4.2.0)
==8359==    by 0x41E3A9: json_rpc_call (util.c:377)
==8359==    by 0x414AC1: pool_active (cgminer.c:4807)
==8359==    by 0x41C4D3: main (cgminer.c:6708)
==8359==
==8359== 288 bytes in 1 blocks are possibly lost in loss record 160 of 212
==8359==    at 0x4C29DB4: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==8359==    by 0x4012074: _dl_allocate_tls (dl-tls.c:297)
==8359==    by 0x52A2ABC: pthread_create@@GLIBC_2.2.5 (allocatestack.c:571)
==8359==    by 0x414829: init_stratum_thread (cgminer.c:4748)
==8359==    by 0x4149F6: pool_active (cgminer.c:4794)
==8359==    by 0x41C4D3: main (cgminer.c:6708)
==8359==
==8359== 288 bytes in 1 blocks are possibly lost in loss record 161 of 212
==8359==    at 0x4C29DB4: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==8359==    by 0x4012074: _dl_allocate_tls (dl-tls.c:297)
==8359==    by 0x52A2ABC: pthread_create@@GLIBC_2.2.5 (allocatestack.c:571)
==8359==    by 0x41F338: thr_info_create (util.c:767)
==8359==    by 0x41C965: main (cgminer.c:6790)
==8359==
==8359== 288 bytes in 1 blocks are possibly lost in loss record 162 of 212
==8359==    at 0x4C29DB4: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==8359==    by 0x4012074: _dl_allocate_tls (dl-tls.c:297)
==8359==    by 0x52A2ABC: pthread_create@@GLIBC_2.2.5 (allocatestack.c:571)
==8359==    by 0x41F338: thr_info_create (util.c:767)
==8359==    by 0x41CBDD: main (cgminer.c:6850)
==8359==
==8359== 288 bytes in 1 blocks are possibly lost in loss record 163 of 212
==8359==    at 0x4C29DB4: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==8359==    by 0x4012074: _dl_allocate_tls (dl-tls.c:297)
==8359==    by 0x52A2ABC: pthread_create@@GLIBC_2.2.5 (allocatestack.c:571)
==8359==    by 0x414829: init_stratum_thread (cgminer.c:4748)
==8359==    by 0x4149F6: pool_active (cgminer.c:4794)
==8359==    by 0x417D70: watchpool_thread (cgminer.c:5757)
==8359==    by 0x52A1E99: start_thread (pthread_create.c:308)
==8359==    by 0x5CEECBC: clone (clone.S:112)
==8359==
==8359== 531 (504 direct, 27 indirect) bytes in 1 blocks are definitely lost in loss record 176 of 212
==8359==    at 0x4C29DB4: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==8359==    by 0x405E0D: make_work (cgminer.c:1361)
==8359==    by 0x41CCEC: main (cgminer.c:6886)
==8359==
==8359== 727 (104 direct, 623 indirect) bytes in 1 blocks are definitely lost in loss record 180 of 212
==8359==    at 0x4C2B6CD: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==8359==    by 0x50952B1: json_object (in /usr/lib/libjansson.so.4.2.1)
==8359==    by 0x5092C74: Huh (in /usr/lib/libjansson.so.4.2.1)
==8359==    by 0x50930A2: Huh (in /usr/lib/libjansson.so.4.2.1)
==8359==    by 0x5093202: json_loads (in /usr/lib/libjansson.so.4.2.1)
==8359==    by 0x41E6F1: json_rpc_call (util.c:425)
==8359==    by 0x414AC1: pool_active (cgminer.c:4807)
==8359==    by 0x417D70: watchpool_thread (cgminer.c:5757)
==8359==    by 0x52A1E99: start_thread (pthread_create.c:308)
==8359==    by 0x5CEECBC: clone (clone.S:112)
==8359==
==8359== 1,383 (104 direct, 1,279 indirect) bytes in 1 blocks are definitely lost in loss record 187 of 212
==8359==    at 0x4C2B6CD: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==8359==    by 0x50952B1: json_object (in /usr/lib/libjansson.so.4.2.1)
==8359==    by 0x5092C74: Huh (in /usr/lib/libjansson.so.4.2.1)
==8359==    by 0x50930A2: Huh (in /usr/lib/libjansson.so.4.2.1)
==8359==    by 0x5093202: json_loads (in /usr/lib/libjansson.so.4.2.1)
==8359==    by 0x41E6F1: json_rpc_call (util.c:425)
==8359==    by 0x414CA2: pool_active (cgminer.c:4852)
==8359==    by 0x417D70: watchpool_thread (cgminer.c:5757)
==8359==    by 0x52A1E99: start_thread (pthread_create.c:308)
==8359==    by 0x5CEECBC: clone (clone.S:112)
==8359==
==8359== 65,432 bytes in 1 blocks are definitely lost in loss record 210 of 212
==8359==    at 0x4C2B6CD: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==8359==    by 0x425CF6: _io_new (api.c:652)
==8359==    by 0x42DC0D: api (api.c:3684)
==8359==    by 0x412662: api_thread (cgminer.c:4348)
==8359==    by 0x52A1E99: start_thread (pthread_create.c:308)
==8359==    by 0x5CEECBC: clone (clone.S:112)
==8359==
==8359== 672,368 (104 direct, 672,264 indirect) bytes in 1 blocks are definitely lost in loss record 212 of 212
==8359==    at 0x4C2B6CD: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==8359==    by 0x50952B1: json_object (in /usr/lib/libjansson.so.4.2.1)
==8359==    by 0x5092C74: Huh (in /usr/lib/libjansson.so.4.2.1)
==8359==    by 0x50930A2: Huh (in /usr/lib/libjansson.so.4.2.1)
==8359==    by 0x5093202: json_loads (in /usr/lib/libjansson.so.4.2.1)
==8359==    by 0x41E6F1: json_rpc_call (util.c:425)
==8359==    by 0x414CA2: pool_active (cgminer.c:4852)
==8359==    by 0x41C4D3: main (cgminer.c:6708)
==8359==
==8359== LEAK SUMMARY:
==8359==    definitely lost: 66,418 bytes in 12 blocks
==8359==    indirectly lost: 674,193 bytes in 3,866 blocks
==8359==      possibly lost: 1,152 bytes in 4 blocks
==8359==    still reachable: 166,745 bytes in 261 blocks
==8359==         suppressed: 0 bytes in 0 blocks
==8359== Reachable blocks (those to which a pointer was found) are not shown.
==8359== To see them, rerun with: --leak-check=full --show-reachable=yes
==8359==
==8359== For counts of detected and suppressed errors, rerun with: -v
==8359== ERROR SUMMARY: 14 errors from 14 contexts (suppressed: 2 from 2)
 valgrind --lea
ak-check=full ./cgminer --api-port 9999 --per-device-stats --api-
-network --api-listen  -S/dev/ICA0 --icarus-timing=1:38
==8748== Memcheck, a memory error detector
==8748== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==8748== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==8748== Command: ./cgminer xxxxxxxxxx --api-port 9999 --per-device-stats --api-network --api-listen -S/dev/ICA0 --icarus-timing=1:38
==8748==
 [2013-02-02 12:00:23] Started cgminer 2.10.4

Please help the Led Boy aka Bicknellski to make us a nice Christmas led tree and pay WASP membership fee here:
https://bitcointalk.org/index.php?topic=643999.msg7191563#msg7191563
And remember Bicknellski is not collecting money from community;D
Pages: « 1 ... 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 [437] 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 ... 845 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!