OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 232.

twmz

hero member

Activity: 737

Merit: 500

Quote from: kano on September 05, 2013, 09:51:59 AM

Quote from: ajw107 on September 05, 2013, 07:53:18 AM

I know I'm a bit late in menting this, but a few posts back there was a bit of confusion with where 'make clean' should go. I think people may have been getting confused with 'make distclean'. 'make clean' should just remove old object files, etc (things generated AFTER make is executed) leaving the configure file, etc intact. 'make distclean' will do the same as 'make clean' AND it will remove the configuration file, etc too. So 'make clean' should be safe to run after a autogen or configure command, 'make distclean' won't be safe. If you get an error when you type make clean that there is nothing to be done, that usually means that it's already clean.

I would imagine a good thing to do when building a new version is definitely to run 'make distclean' first to clean out old configs as well, especially if the build process has changed. Even better would be to just 'sudo rm -r ' and do another git clone of the repo, then you know you are safe and don't have anything lying around if you are having problems with the build process.

I realise this was not the original posters problem in the end, but just though it should be mentioned for when people compile other things.
Alex

The problem is that with cgminer 3.4.1/2 there is a completely new configuration, so yeah anyone upgrading really needs to ensure they aren't skipping the autogen and configure ... so it's easier to say: rename the old directory (so you can get any config files or scripts from the old directory, if needed after you rebuild) and start again with an empty cgminer folder or fresh git clone ... even I made some mistakes with this back about 2 or 3 months ago when I was doing libusb version testing (and failed to switch the versions properly a few times)

I have a build.sh file in my cgminer git working directory that I run every time I want to build cgminer. It looks like this:

Code:

#!/bin/sh

make distclean
CFLAGS="-O2 -Wall -march=native" ./autogen.sh --enable-bflsc --enable-icarus --disable-opencl
make
mv -f cgminer cgminer-nogpu

The 'make distclean' may not be necessary every time, but it doesn't take long.

Rant2112

newbie

Activity: 70

Merit: 0

Quote from: -ck on September 04, 2013, 09:40:25 PM

Quote from: Rant2112 on September 04, 2013, 09:25:33 PM

I'm having trouble getting 3.4.2 working with my ASICMiner USB Block Erupter. I'm still using 3.1.1. 8(

I've looked at the usbfail post
https://bitcointalksearch.org/topic/m.2817682

I've built a local version of libusb-1.0.16-rc10

But, when I try to run cgminer's configure to use it it looks like it is still using the cgminer*/compat/libusb* version.

FYI - I only use this machine for mining so I would be happy to change libusb to whatever version works for cgminer if that's easier than pointing the cgminer make to my local libusb...

Thanks.

I wanted to make it easier for everyone so I modified the entire build tree to use the optimal libusb automatically, that's why it's now included in the cgminer release tarballs/git tree (it is 1.0.16-rc10) and is built into the cgminer binary statically. No need to do anything with libusb from the user side.

I am getting the timeout messages with my ASICMiner USB Block Erupter when I use 3.4.2.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: ajw107 on September 05, 2013, 07:53:18 AM

I know I'm a bit late in menting this, but a few posts back there was a bit of confusion with where 'make clean' should go. I think people may have been getting confused with 'make distclean'. 'make clean' should just remove old object files, etc (things generated AFTER make is executed) leaving the configure file, etc intact. 'make distclean' will do the same as 'make clean' AND it will remove the configuration file, etc too. So 'make clean' should be safe to run after a autogen or configure command, 'make distclean' won't be safe. If you get an error when you type make clean that there is nothing to be done, that usually means that it's already clean.

I would imagine a good thing to do when building a new version is definitely to run 'make distclean' first to clean out old configs as well, especially if the build process has changed. Even better would be to just 'sudo rm -r ' and do another git clone of the repo, then you know you are safe and don't have anything lying around if you are having problems with the build process.

I realise this was not the original posters problem in the end, but just though it should be mentioned for when people compile other things.
Alex

The problem is that with cgminer 3.4.1/2 there is a completely new configuration, so yeah anyone upgrading really needs to ensure they aren't skipping the autogen and configure ... so it's easier to say: rename the old directory (so you can get any config files or scripts from the old directory, if needed after you rebuild) and start again with an empty cgminer folder or fresh git clone ... even I made some mistakes with this back about 2 or 3 months ago when I was doing libusb version testing (and failed to switch the versions properly a few times)

ProfMac

legendary

Activity: 1246

Merit: 1002

Quote from: kano on September 05, 2013, 02:56:47 AM

FYI - and I'd not be surprised at all if he didn't want me to say this - but when has that stopped me before ...

ckolivas isn't making any more firmware releases for now.
His OpenWRT thingy (whatever it is) died - he's mining over the USB connection.

So I'd suggest if someone wants more firmware releases, they should band together and send him the hardware needed to replace whatever it is that has a reset switch on it that broke.

Now the reason being the obvious one, that Team Avalon fucked you all over when it comes to support, ckolivas has been supporting you all very well, even though in my Kano vs GitSyncom thread, Team Avalon said I was wrongs suggesting that hardware was required to support them ... yet they pretty much didn't at all ... yeah clearly yet another thing to add the the list of crap from GitSyncom ...

So, yeah, get him a replacement OpenWRT board (I think that's what needed) if you want more firmware releases

I have a backup TP-Link 703n. I can also drop a public SSH key into dropbear on my Avalon.

Xian01

legendary

Activity: 1652

Merit: 1067

Christian Antkow

Got a crash report under Windows while running the 3.4.2 debug build.

---

cgminer.exe caused a Stack Overflow at location 74946ae6 in module mswsock.dll. Registers: eax=00add5b8 ebx=03ff3098 ecx=ff676980 edx=ffffffff esi=03ff30a8 edi=00000000 eip=74946ae6 esp=03ff3000 ebp=03ff30f8 iopl=0 nv up ei pl zr na po nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246 Call stack: 74946AE6 mswsock.dll:74946AE6 75ED6A28 WS2_32.dll:75ED6A28 select 00424FDF cgminer.exe:00424FDF 004251A8 cgminer.exe:004251A8 00413ED1 cgminer.exe:00413ED1 004B1BAB cgminer.exe:004B1BAB 76BD1287 msvcrt.dll:76BD1287 _itow_s 76BD1328 msvcrt.dll:76BD1328 _endthreadex 750833AA kernel32.dll:750833AA BaseThreadInitThunk 77259F72 ntdll.dll:77259F72 RtlInitializeExceptionChain 77259F45 ntdll.dll:77259F45 RtlInitializeExceptionChain

PatMan

hero member

Activity: 924

Merit: 1000

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

Yeah, thanks indeed. I actually deleted the cgminer folder a few times in an effort to ensure a completely "fresh" install, but still had the 30% cpu problem. I'm sure it's a usb issue, my usb controllers are nvidia (ugh!) so I'm currently searching for the latest linux driver for them in the hope that they're newer/better than the ones incorporated in Xubuntu 12.04 64bit (for kano) which I'm using. Failing that, I think it might be worth upgrading to Xubuntu 13.04 - maybe the usb controller drivers are better in that distro? I dunno, I'm grabbing at straws a little here.

Zanatos666

sr. member

Activity: 280

Merit: 250

Sometimes man, just sometimes.....

Quote from: ajw107 on September 05, 2013, 07:53:18 AM

I know I'm a bit late in menting this, but a few posts back there was a bit of confusion with where 'make clean' should go. I think people may have been getting confused with 'make distclean'. 'make clean' should just remove old object files, etc (things generated AFTER make is executed) leaving the configure file, etc intact. 'make distclean' will do the same as 'make clean' AND it will remove the configuration file, etc too. So 'make clean' should be safe to run after a autogen or configure command, 'make distclean' won't be safe. If you get an error when you type make clean that there is nothing to be done, that usually means that it's already clean.

I would imagine a good thing to do when building a new version is definitely to run 'make distclean' first to clean out old configs as well, especially if the build process has changed. Even better would be to just 'sudo rm -r ' and do another git clone of the repo, then you know you are safe and don't have anything lying around if you are having problems with the build process.

I realise this was not the original posters problem in the end, but just though it should be mentioned for when people compile other things.
Alex

Thanks for the clear up on this, I appreciate it.

ajw107

newbie

Activity: 40

Merit: 0

I know I'm a bit late in menting this, but a few posts back there was a bit of confusion with where 'make clean' should go. I think people may have been getting confused with 'make distclean'. 'make clean' should just remove old object files, etc (things generated AFTER make is executed) leaving the configure file, etc intact. 'make distclean' will do the same as 'make clean' AND it will remove the configuration file, etc too. So 'make clean' should be safe to run after a autogen or configure command, 'make distclean' won't be safe. If you get an error when you type make clean that there is nothing to be done, that usually means that it's already clean.

I would imagine a good thing to do when building a new version is definitely to run 'make distclean' first to clean out old configs as well, especially if the build process has changed. Even better would be to just 'sudo rm -r ' and do another git clone of the repo, then you know you are safe and don't have anything lying around if you are having problems with the build process.

I realise this was not the original posters problem in the end, but just though it should be mentioned for when people compile other things.
Alex

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

echo -n summary | nc -4 localhost 4028 | tr "|," "\n"

If you don't have nc ... I've no idea what package it is in coz I have no idea what linux you are using

As for building cgminer, if your cgminer is in /home/me/cgminer/ then:

cd /home/me
mv cgminer cgminer-old
git clone git://github.com/ckolivas/cgminer.git
cd cgminer

... and start autogen/configure all over again then make
Since I have no idea what is in your old cgminer folder (e.g. libusb from before or what)
this will ensure you are using a fresh 3.4.2 and the correct libusb which is part of 3.4.2 and you can't 'make' until you have successfully run autogen and configure and thus have updated all the makefiles

-Redacted-

hero member

Activity: 574

Merit: 501

"java api summary" IS the command line.

PatMan

hero member

Activity: 924

Merit: 1000

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

Quote from: kano on September 04, 2013, 08:17:02 PM

Quote from: PatMan on September 04, 2013, 12:49:21 PM

...
Right, now that I've done embarrassing myself, I'm still stuck with this 30% cpu usage problem - any ideas on that one?

Be gentle with me.......

Do that at the same time as the output of java API summary

I run 2 AMU erupters on a tiny RPi Raspbian and it uses only 1.8% CPU

Code:

23464 root 20 0 202m 59m 2868 S 1.6 16.0 47:03.55 cgminer-3.4.2a

[Elapsed] => 159427

(47*60+3.55)/159427 = 1.77...%

I note that you are also running bitcoind and possibly even p2pool (python) on that at the same time ...

Hey Kano,

Yes, this box is used solely as a p2pool node, all my other mining is done separately on other PC's. When compiling, does the make clean command empty the libusb directory? if not, can you give me a pointer as to where it is so I can empty it manually? I'm not familiar with the java api summary I'm afraid, is there a command line string?

I have a feeling that the usb is the cause of the problem, it's just how to fix it I'm a little lost with. I've ran this box for months previously with very little cpu usage up until the latest update.

Thanks bro.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: Rant2112 on September 04, 2013, 09:25:33 PM

I'm having trouble getting 3.4.2 working with my ASICMiner USB Block Erupter. I'm still using 3.1.1. 8(

I've looked at the usbfail post
https://bitcointalksearch.org/topic/m.2817682

I've built a local version of libusb-1.0.16-rc10

But, when I try to run cgminer's configure to use it it looks like it is still using the cgminer*/compat/libusb* version.

FYI - I only use this machine for mining so I would be happy to change libusb to whatever version works for cgminer if that's easier than pointing the cgminer make to my local libusb...

Thanks.

I wanted to make it easier for everyone so I modified the entire build tree to use the optimal libusb automatically, that's why it's now included in the cgminer release tarballs/git tree (it is 1.0.16-rc10) and is built into the cgminer binary statically. No need to do anything with libusb from the user side.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

3.4.2 uses libusb-1.0.16-rc10
If you build it yourself, start with an empty directory.

Rant2112

newbie

Activity: 70

Merit: 0

I'm having trouble getting 3.4.2 working with my ASICMiner USB Block Erupter. I'm still using 3.1.1. 8(

I've looked at the usbfail post
https://bitcointalksearch.org/topic/m.2817682

I've built a local version of libusb-1.0.16-rc10

But, when I try to run cgminer's configure to use it it looks like it is still using the cgminer*/compat/libusb* version.

FYI - I only use this machine for mining so I would be happy to change libusb to whatever version works for cgminer if that's easier than pointing the cgminer make to my local libusb...

Thanks.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: PatMan on September 04, 2013, 12:49:21 PM

...
Right, now that I've done embarrassing myself, I'm still stuck with this 30% cpu usage problem - any ideas on that one?

Be gentle with me.......

Do that at the same time as the output of java API summary

I run 2 AMU erupters on a tiny RPi Raspbian and it uses only 1.8% CPU

Code:

23464 root 20 0 202m 59m 2868 S 1.6 16.0 47:03.55 cgminer-3.4.2a

[Elapsed] => 159427

(47*60+3.55)/159427 = 1.77...%

I note that you are also running bitcoind and possibly even p2pool (python) on that at the same time ...

centove

full member

Activity: 194

Merit: 100

Quote from: The00Dustin on September 04, 2013, 03:14:05 PM

Quote from: centove on September 04, 2013, 03:01:41 PM

Quote from: The00Dustin on September 04, 2013, 11:45:11 AM

I don't remember why, and I can't find a post saying why, but I'm still running 3.1.1. I decided to try out 3.4.2 and I get this:

Code:

ADL..................: SDK NOT found, GPU monitoring support DISABLED

from the exact same configure command I can still run in the 3.1.1 source and get this:

Code:

ADL..................: SDK found, GPU monitoring support enabled

. Any chance a change needs made in the source to fix that again? I know this happened once before and it was a pretty quick fix, after which I redownloaded.

Copy the ADL_SDK include files from 3.1.1 (or the sdk_app thingy) to the ADL_SDK directory and re-configure.

Duh! Been way too long. Thanks.
ETA: Sent a bitcent your way.

I fumbled around with that for a couple of hours till it hit me.. Wink

zomnut

newbie

Activity: 16

Merit: 0

Using 3.4.2, logging to syslog.

If my cgminer log interval is not set to 5, I don't receive the log entries like

Code:

(5s):xxG (avg):xxGh/s | A:xx R:xx HW:xx WU:xx/m

to syslog at all. I still get other syslog entries from cgminer, just not this entry. When log interval is equal to 5, I get that entry every 5 seconds.

The00Dustin

hero member

Activity: 807

Merit: 500

Quote from: centove on September 04, 2013, 03:01:41 PM

Quote from: The00Dustin on September 04, 2013, 11:45:11 AM

I don't remember why, and I can't find a post saying why, but I'm still running 3.1.1. I decided to try out 3.4.2 and I get this:

Code:

ADL..................: SDK NOT found, GPU monitoring support DISABLED

from the exact same configure command I can still run in the 3.1.1 source and get this:

Code:

ADL..................: SDK found, GPU monitoring support enabled

. Any chance a change needs made in the source to fix that again? I know this happened once before and it was a pretty quick fix, after which I redownloaded.

Copy the ADL_SDK include files from 3.1.1 (or the sdk_app thingy) to the ADL_SDK directory and re-configure.

Duh! Been way too long. Thanks.
ETA: Sent a bitcent your way.

centove

full member

Activity: 194

Merit: 100

Quote from: The00Dustin on September 04, 2013, 11:45:11 AM

I don't remember why, and I can't find a post saying why, but I'm still running 3.1.1. I decided to try out 3.4.2 and I get this:

Code:

ADL..................: SDK NOT found, GPU monitoring support DISABLED

from the exact same configure command I can still run in the 3.1.1 source and get this:

Code:

ADL..................: SDK found, GPU monitoring support enabled

. Any chance a change needs made in the source to fix that again? I know this happened once before and it was a pretty quick fix, after which I redownloaded.

Copy the ADL_SDK include files from 3.1.1 (or the sdk_app thingy) to the ADL_SDK directory and re-configure.

-Redacted-

hero member

Activity: 574

Merit: 501

You really shouldn't mix and match different blockchains in the same config, or in the same session. It's really better to have two config files, quit out of cgminer, switch the files and restart. You are just asking for trouble trying to switch between them on the fly. There are reasons why the instuctions specifically say not to do this...

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