OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.1

[-ck]

if (cgpu && cgpu->deven == DEV_ENABLED) cgpu->drv->flush_work(cgpu);

flush work is not initialized  in this case 

Updated git. The mining thread shouldn't appear with read lock held so see if that code suffices.

[1679525543]

1679525543

[1679525543]

1679525543

[1679525543]

1679525543

[1679525543]

1679525543

[1679525543]

1679525543

[loshia]

if (cgpu && cgpu->deven == DEV_ENABLED) cgpu->drv->flush_work(cgpu);

flush work is not initialized  in this case 

Updated git. The mining thread shouldn't appear with read lock held so see if that code suffices.

10X
But on my tplinks it sill segfaults from time to times because of it - drv->flush-queue . It is a temporally fix probably. But unfortunately no gdb on my tplink. I hope you will see it on your Avalon unit...

Thank you
Best

[whiteEAGLE]

Hello forum!

Can anybody help me with setting up cgminer on a RPi?
I'm nwe to the RPi and don't really know what i'm doing....
At this time i'm using minepeon and it works so far.
But i want to set up cgminer on Raspbian. Is there a "How to" guide somewhere in the last 666 sides tread

Hope someone has the time to take care of a newbie

Thanks!

[Beastlymac]

Hello forum!

Can anybody help me with setting up cgminer on a RPi?
I'm nwe to the RPi and don't really know what i'm doing....
At this time i'm using minepeon and it works so far.
But i want to set up cgminer on Raspbian. Is there a "How to" guide somewhere in the last 666 sides tread

Hope someone has the time to take care of a newbie

Thanks!

Follow this guide. But change 3.3.4 to 3.7.0
http://www.huement.com/blog/?p=941

[Askit2]

Hello forum!

Can anybody help me with setting up cgminer on a RPi?
I'm nwe to the RPi and don't really know what i'm doing....
At this time i'm using minepeon and it works so far.
But i want to set up cgminer on Raspbian. Is there a "How to" guide somewhere in the last 666 sides tread

Hope someone has the time to take care of a newbie

Thanks!

Don't use Raspbian. Please. All my runtime issues disappeared when working under arch. Please use arch.

If you must use raspbian here is what I did to get everything setup....
First install the requirements to build cgminer. (I would as it makes hotfixes on git useable).
Some of these aren't strictly required. Like you don't need vim or screen. Screen is just awesome though.

Code:

apt-get install vim screen
apt-get install git
apt-get install automake
apt-get install autoconf
apt-get install libcurl4-openssl-dev
apt-get install libusb-1.0.0-dev
apt-get install libncurses5-dev
apt-get install libudev-dev
apt-get install pkg-config
apt-get install libtool

Next build instructions.
Each line is its own command.

Code:

git clone https://github.com/ckolivas/cgminer --branch master

cd cgminer

CFLAGS="-g -W -Wall" ./autogen.sh --enable-bflsc --enable-icarus --enable-bitforce --enable-modminer --enable-ztex --enable-avalon --enable-klondike

make clean

make

Again I would likely use Pacman to get the packages you need to build your own. Pacman is on Arch (What mine peon runs) and works just fine. Hopefully the USB/Memory errors on Raspbian get worked out soon but I got tired of waiting.

EDIT: My instructions are likely dated but the package list is from things Kano and CK posted. The rest are just things I wrote down so I wouldn't forget.

EDIT2: There is one file that needs copied. Look in the readme and follow the code. Really it isn't hard to set it up.

[RaTTuS]

http://www.raspberrypi.org/phpBB3/viewtopic.php?t=54176&p=417366#p417366
works for me raspbian no issues,

for 3.6.1
I don't bother with the libusb just plain cgminer

[-ck]

New version: 3.7.2, 5th November 2013

In the interests of not leaving a relatively unstable release out there, here's a pure bugfix release.


Human readable changelog:

- Fix for crashes on startup and hotplug.
- Fix for hangs doing no further work after a block change.
- Fix yet again scrypt showing a block solve with every highish diff share.
- Try to find a compromise between the various ends of the windows+AMU timeout issue spectrum.
- Write errors will cause a device failure, allowing cgminer to attempt to hotplug them again.
- Icarus based devices will hopefully align on the display with others.
- Fix for short periods of no/idled work on avalon devices due to async restarts with block changes.
- Fix for diff shown on big endian machines
- Fix for building with curses disabled.
- Other low level clean ups.


Full changelog:

- Clean up completely on avalon shutdown.
- Use cgsem timed waits in avalon driver to not miss any queued wake ups to
account for async messages coming during a flush work.
- Statline before is too long on icarus that doesn't have monitoring.
- Different windows+usb combinations respond with varying levels of reliability
wrt timeouts so use a nominal extra 40ms before cancelling transfers that fail
to time out on their own.
- Do all hotplug_process under the write mining_thr_lock
- Fix for opt_worktime on big endian machines.
- Correct set_blockdiff for big endian machines.
- Make sure cgpu exists in the restart threads loop in cases of hotplug etc.
- Treat usb write timeout errors as unrecoverable.
- Transfer errors are filtered out in usbutils now so no need to look for them
in NODEV checks.
- Remove now unused entries from struct cg_usb_device
- Do not double up with checking for end of timeout measurements in usb
read/write.
- Do get_work in fill_queue without holding other locks.
- Initialise usb after all the locks and conditionals are initialised.
- Use only a trylock in flush queue to prevent deadlocks.
- Add a wr_trylock wrapper for pthread rw lock write trylock.
- Scale diff for scrypt when testing for block solves.
- Fix for non curses build.

[jmc1517]

No, there are too many changes post 3.5.1 that everything else depends on. In the same way new versions come out for other reasons and need bugfixes, the solution is to fix the current  behaviour, not go to the old behaviour.

EDIT: What's interesting is that the pattern is the same every time in your logs. One device disappears and then another has timeouts forever more. However it also seems to keep hashing fine based on the fact that your summary shows the hashrate is the same for AMU0 as the rest.

EDIT2: Here're the next tests (note this is specifically for your issue now since last report aigeezer's was working)
http://ck.kolivas.org/apps/cgminer/temp/cgminer-lt.exe
http://ck.kolivas.org/apps/cgminer/temp/cgminer-nt.exe
http://ck.kolivas.org/apps/cgminer/temp/cgminer-et.exe

Appreciate your dedication to this, I'll stick with it for as long as you want to keep testing, but quite willing to stick with the older version if you want to spend your time more productively!

So, latest test results. Nothing to very hopeful, at least to my untrained eye:
Started cgminer-lt @10:21, zombie at 11:01. Test ended
Started cgminer-nt @11:06, zombie at 12:07. Test ended

Started cgminer-et at 12:11. First zombie AMU29 appeared at 12:18 just as I started uploading to Flickr aagin (coincidence?). The offending AMU was replugged at 12:22 and started working again as AMU 34.

Two AMU LEDs came on full and 2 zombies appeared in the display at 12:25, AMU 14&16, but AMU 16 started working again. Tis behaviour is new, perhaps?  It was removed from the table and reappeared as AMU 35. AMU 14 was still reported as zombie, but there was no corresponding "NO_DEVICE" in the logfile for either of these two. Strange?

I tried re-plugging AMU 14 @12:30 but it did not get recognised again (LED came back full on and the zombie remained in the display table). Test ended...

Edit to add logfile links:
 https://dl.dropboxusercontent.com/u/44240170/logfile-lt.txt
 https://dl.dropboxusercontent.com/u/44240170/logfile-nt.txt
 https://dl.dropboxusercontent.com/u/44240170/logfile-et.txt

Edit: Just noticed the 3.7.1 release.  I'll give it a try. You never know!
 

[-ck]

So, latest test results. Nothing to very hopeful, at least to my untrained eye:
Started cgminer-lt @10:21, zombie at 11:01. Test ended
Started cgminer-nt @11:06, zombie at 12:07. Test ended

Started cgminer-et at 12:11. First zombie AMU29 appeared at 12:18 just as I started uploading to Flickr aagin (coincidence?). The offending AMU was replugged at 12:22 and started working again as AMU 34.

Two AMU LEDs came on full and 2 zombies appeared in the display at 12:25, AMU 14&16, but AMU 16 started working again. Tis behaviour is new, perhaps?  It was removed from the table and reappeared as AMU 35. AMU 14 was still reported as zombie, but there was no corresponding "NO_DEVICE" in the logfile for either of these two. Strange?

I tried re-plugging AMU 14 @12:30 but it did not get recognised again (LED came back full on and the zombie remained in the display table). Test ended...

Edit to add logfile links:
 https://dl.dropboxusercontent.com/u/44240170/logfile-lt.txt
 https://dl.dropboxusercontent.com/u/44240170/logfile-nt.txt
 https://dl.dropboxusercontent.com/u/44240170/logfile-et.txt

Edit: Just noticed the 3.7.1 release.  I'll give it a try. You never know!
 

Thanks for that. 3.7.1 is closest to -et in behaviour.

[whiteEAGLE]

Does sgminer run with Nanofury NF1 USB-sticks?

If yes - how can i get it to work?

[-ck]

Does sgminer run with Nanofury NF1 USB-sticks?

If yes - how can i get it to work?

No

[whiteEAGLE]

is this planed to add?

[aigeezer]

So, latest test results. Nothing to very hopeful, at least to my untrained eye:
Started cgminer-lt @10:21, zombie at 11:01. Test ended
Started cgminer-nt @11:06, zombie at 12:07. Test ended

Started cgminer-et at 12:11. First zombie AMU29 appeared at 12:18 just as I started uploading to Flickr aagin (coincidence?). The offending AMU was replugged at 12:22 and started working again as AMU 34.

Two AMU LEDs came on full and 2 zombies appeared in the display at 12:25, AMU 14&16, but AMU 16 started working again. Tis behaviour is new, perhaps?  It was removed from the table and reappeared as AMU 35. AMU 14 was still reported as zombie, but there was no corresponding "NO_DEVICE" in the logfile for either of these two. Strange?

I tried re-plugging AMU 14 @12:30 but it did not get recognised again (LED came back full on and the zombie remained in the display table). Test ended...

Edit to add logfile links:
 https://dl.dropboxusercontent.com/u/44240170/logfile-lt.txt
 https://dl.dropboxusercontent.com/u/44240170/logfile-nt.txt
 https://dl.dropboxusercontent.com/u/44240170/logfile-et.txt

Edit: Just noticed the 3.7.1 release.  I'll give it a try. You never know!
 

Thanks for that. 3.7.1 is closest to -et in behaviour.

3.7.1 froze on startup for me and did not respond to the Q command. I tried it twice, then reverted to 3.7.0 which seems to be running fine. Prior to that, 3.7.0 had run without error for 24 hours before I tried the update to 3.7.1.

[jmc1517]

So, latest test results.
Edit: Just noticed the 3.7.1 release.  I'll give it a try. You never know!
 

Thanks for that. 3.7.1 is closest to -et in behaviour.

3.7.1 doesn't start up for me - it just hangs and doesn't turn off any of the AMU LEDs.  No screen display.  I've tried both zip and 7z archives, running cgminer with my usual conf file, and also cgminer-nogpu.  No dice.  Tried a few times, then back to 3.5.1 which started up ok.  I guess it's not just me, seeing the previous post from aigeezer.
 

[-ck]

Shit shit shit, last minute breakage 

pretend you didn't see 3.7.1

[-ck]

3.7.2 uploading as we speak/type. Besides, even numbers always sound more stable.

EDIT: And it's up.

[aigeezer]

3.7.2 uploading as we speak/type. Besides, even numbers always sound more stable.

EDIT: And it's up.

It's off to a good start for me (Windows zip version).

[P_Shep]

Getting this compile error:

cgminer-driver-knc-spi-fpga.o: In function `knc_process_response.constprop.6':
driver-knc-spi-fpga.c:(.text+0xf54): undefined reference to `WEXITSTATUS'
cgminer-driver-knc-spi-fpga.o: In function `knc_scanwork':
driver-knc-spi-fpga.c:(.text+0x1700): undefined reference to `WEXITSTATUS'

[-ck]

Getting this compile error:

cgminer-driver-knc-spi-fpga.o: In function `knc_process_response.constprop.6':
driver-knc-spi-fpga.c:(.text+0xf54): undefined reference to `WEXITSTATUS'
cgminer-driver-knc-spi-fpga.o: In function `knc_scanwork':
driver-knc-spi-fpga.c:(.text+0x1700): undefined reference to `WEXITSTATUS'

The KfC sauce is meant to only cook on this architecture: arm-angstrom-linux-gnueabi
There is no point trying to compile it for anything else since the hardware only exists on a beaglebone. What are you trying to compile it for?

[P_Shep]

Getting this compile error:

cgminer-driver-knc-spi-fpga.o: In function `knc_process_response.constprop.6':
driver-knc-spi-fpga.c:(.text+0xf54): undefined reference to `WEXITSTATUS'
cgminer-driver-knc-spi-fpga.o: In function `knc_scanwork':
driver-knc-spi-fpga.c:(.text+0x1700): undefined reference to `WEXITSTATUS'

The KfC sauce is meant to only cook on this architecture: arm-angstrom-linux-gnueabi
There is no point trying to compile it for anything else since the hardware only exists on a beaglebone. What are you trying to compile it for?

Ah, ok, I just enabled everything. Complies fine without.
And thanks for adding the '--with-system-libusb'