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

[kano]

I was poking around the README file when I noticed what seems to be a missing line:

Code:

  --with-system-libusb    Compile against dynamic system libusb (default use

Basic *nix build instructions:

It seems there should be another line continuing the parenthetical comment on the --with-system-libusb line, but there's nothing there.

That aside, I was wondering what the list of compile-time options is that you use for creating the official binaries? That might be handy to include in the README as well. My goal is to compile a binary that's almost identical to the official binary, but with one driver tweaked a little to my satisfaction.

Many thanks.

Firstly, unless you want to do extensive testing, don't use that option.
libusb is broken on many linux distros.

Secondly, all the USB devices are enabled in ckolivas' binaries.
My binary git, the README says.

[KyrosKrane]

Firstly, unless you want to do extensive testing, don't use that option.
libusb is broken on many linux distros.

Heh, believe me, I have no intention of using it! In fact, I switched to Linux just because of the insane headaches of dealing with USB miners on Windows. I was just pointing out that the readme seemed incomplete.

Thanks for the info on the binaries; much appreciated!

[RusellPower]

I am mining using a Raspberry Pi with cgminer and it hangs after a little while or few hours.

I did read on some pages over the internet that this is due to a "memory paging issue". I don't know what this is and if or it's the correct reason.

Can someone help me with this issue?

PS: I am running Arch Linux on my RPi

[GrapeApe]

Does CGMiner support SSL/TLS?

If not are there any plans to include it it in the future, if so does anyone think the pool operators will/should be supporting it given the recent round of attacks?

[Dunkelheit667]

I am mining using a Raspberry Pi with cgminer and it hangs after a little while or few hours.

I did read on some pages over the internet that this is due to a "memory paging issue". I don't know what this is and if or it's the correct reason.

Can someone help me with this issue?

PS: I am running Arch Linux on my RPi

Here you go: http://projectklondike.org/how-to-run#rpi-freeze

Make sure you're adding this option as described to the existing line, it should look like this:



Good luck!

[-ck]

New release - version 4.3.2, 2nd May 2014


Human readable changelog:

- There's a workaround in this version to minimise the risk of the man-in-the-middle attack of redirecting you to a different pool you don't want to be hashing on. Stratum reconnect will only honour the request if the reconnect is to a server with the same domain name.
- Fix for some overflow errors on stats with massive hashrates/shares.
- Fix a major memory leak which mostly affected hashfast users.
- Fix for a failed connection after a redirection that would then never return.
- Devices with unique serial numbers of 4 or more characters will now be displayed by their serial number in the status bar.
- Support for new firmware for OneStringMiners that will identify themselves as OSM devices.
- Support for OSM debugging and LED modes.
- A1 driver updates.


Full changelog:

- Make reconnection messages more explanatory
- Fix accounting bug with nrolltime drivers
- upgrade some int to int64_t to avoid overflows in reporting
- Stratum client.reconnect require matching URL
- Fix memory leak in submit_noffset_nonce
- Clean up any work that may not have been used in the work scheduler
- Avoid unnecessary deref now that it's done within discard_work
- Clean work pointers after one way usage functions
- Avoid unnecessary total_work_inc in generating local work
- Cosmetic fixes
- Fix idle bug, when redirected client can't auth
- Rename spond temp rate to asics total rate
- Build fixes
- Set the unique id only for usb devices with serial strings longer than 4 chars
long
- Use usb serial strings as unique id if devices have them
- Discretely identify the onestring miners as OSM
- Add bxf debugging option and osm led modes
- A1: modularize board selector / add initial CCR support
- A1: cleanup tca9535 logging
- A1: fix and extend PLL parameters
- A1: clean up compile warnings
- A1: use real level in hexdump
- Add identification for onestring miner variants
- Avalon2: Parser the power good signal
- driver-avalon2: this functions used on detect, which don't have thr setup yet

[Taugeran]

Does CGMiner support SSL/TLS?

If not are there any plans to include it it in the future, if so does anyone think the pool operators will/should be supporting it given the recent round of attacks?

btcguild & bfgminer are working on support for ssl/tls

[RusellPower]

I am mining using a Raspberry Pi with cgminer and it hangs after a little while or few hours.

I did read on some pages over the internet that this is due to a "memory paging issue". I don't know what this is and if or it's the correct reason.

Can someone help me with this issue?

PS: I am running Arch Linux on my RPi

Here you go: http://projectklondike.org/how-to-run#rpi-freeze

Make sure you're adding this option as described to the existing line, it should look like this:

https://i.imgur.com/a4opFyb.png

Good luck!

Thank you! I will try it out...

[ManeBjorn]

Thanks for the OSM update.  I am going to dl and get using it now.
 

New release - version 4.3.2, 2nd May 2014


Human readable changelog:

- There's a workaround in this version to minimise the risk of the man-in-the-middle attack of redirecting you to a different pool you don't want to be hashing on. Stratum reconnect will only honour the request if the reconnect is to a server with the same domain name.
- Fix for some overflow errors on stats with massive hashrates/shares.
- Fix a major memory leak which mostly affected hashfast users.
- Fix for a failed connection after a redirection that would then never return.
- Devices with unique serial numbers of 4 or more characters will now be displayed by their serial number in the status bar.
- Support for new firmware for OneStringMiners that will identify themselves as OSM devices.
- Support for OSM debugging and LED modes.
- A1 driver updates.


Full changelog:

- Make reconnection messages more explanatory
- Fix accounting bug with nrolltime drivers
- upgrade some int to int64_t to avoid overflows in reporting
- Stratum client.reconnect require matching URL
- Fix memory leak in submit_noffset_nonce
- Clean up any work that may not have been used in the work scheduler
- Avoid unnecessary deref now that it's done within discard_work
- Clean work pointers after one way usage functions
- Avoid unnecessary total_work_inc in generating local work
- Cosmetic fixes
- Fix idle bug, when redirected client can't auth
- Rename spond temp rate to asics total rate
- Build fixes
- Set the unique id only for usb devices with serial strings longer than 4 chars
long
- Use usb serial strings as unique id if devices have them
- Discretely identify the onestring miners as OSM
- Add bxf debugging option and osm led modes
- A1: modularize board selector / add initial CCR support
- A1: cleanup tca9535 logging
- A1: fix and extend PLL parameters
- A1: clean up compile warnings
- A1: use real level in hexdump
- Add identification for onestring miner variants
- Avalon2: Parser the power good signal
- driver-avalon2: this functions used on detect, which don't have thr setup yet

[-ck]

Thanks for the OSM update.  I am going to dl and get using it now.
 

Be aware the OSM update is for firmware which is only for testing for now, so if you're using the stable firmware release by OneString it will still come up as MXF but work the same in every other way; it's just the cosmetic change of missing the name OSM.

[Askit2]

I am mining using a Raspberry Pi with cgminer and it hangs after a little while or few hours.

I did read on some pages over the internet that this is due to a "memory paging issue". I don't know what this is and if or it's the correct reason.

Can someone help me with this issue?

PS: I am running Arch Linux on my RPi

Here you go: http://projectklondike.org/how-to-run#rpi-freeze

Make sure you're adding this option as described to the existing line, it should look like this:



Good luck!

I am not absolutely sure that is a fix for ARCH Linux. The fix you posted is to fix a long standing Raspbian problem. Now I can't say it won't fix it. I can say that mine doesn't exhibit this behavior with ARCH.

Best of luck to the person with the problem and I hope they find a solution.

EDIT: If you are running out of memory try the newest version maybe a memory leak is causing you grief with the limited RAM.

[ManeBjorn]

Yes I have not updated the new firmware yet.  I have been keeping up with Ben about it.
I am going to try it in a few days though and give him some feedback.
Your update saved me having to compile it in.  I appreciate it greatly.  I am not good at that stuff anymore.

Thanks for the OSM update.  I am going to dl and get using it now.
 

Be aware the OSM update is for firmware which is only for testing for now, so if you're using the stable firmware release by OneString it will still come up as MXF but work the same in every other way; it's just the cosmetic change of missing the name OSM.

[matagatoz]

Hi, After updating to 4.3.2 , if you go Settings, then save, cgminer will just close ( no error )

im on Ubuntu 13.10 64x , runing cgminer with

Code:

su ./cgminer

[Dunkelheit667]

I am mining using a Raspberry Pi with cgminer and it hangs after a little while or few hours.

I did read on some pages over the internet that this is due to a "memory paging issue". I don't know what this is and if or it's the correct reason.

Can someone help me with this issue?

PS: I am running Arch Linux on my RPi

Here you go: http://projectklondike.org/how-to-run#rpi-freeze

Make sure you're adding this option as described to the existing line, it should look like this:



Good luck!

I am not absolutely sure that is a fix for ARCH Linux. The fix you posted is to fix a long standing Raspbian problem. Now I can't say it won't fix it. I can say that mine doesn't exhibit this behavior with ARCH.

Best of luck to the person with the problem and I hope they find a solution.

EDIT: If you are running out of memory try the newest version maybe a memory leak is causing you grief with the limited RAM.

Not 100% sure but Raspbian and Arch using the same Raspberry Firmware/Kernel as far as I understood. I've seen the same behavior on Arch (at least with 3.6.11 up to 3.10.?) and the hint above solved all issues with my 'freezing' Raspberry (in fact it's alive, but USB including the network port is gone). Most likely you'll never see the behavior as long as the number of connected USB devices is fairly low. With let's say 10 or 15+ you will notice issues sooner or later. At least from my experience.

Anyway, it's worth a try and of course the latest cgminer is always the best.

[RusellPower]

Moved to Raspbian, applied the patch, waiting to see if it works... 

[yelloyello]

Nice this thread but......

I have 3 KNC Jupiters (april 2014) and I want to update cgminer.
I am familiar with putty.

But, how to upgrade the cgminer?  apt-get install does not work.

anyone ??

[Buchi-88]

New release - version 4.3.2, 2nd May 2014


Human readable changelog:

- There's a workaround in this version to minimise the risk of the man-in-the-middle attack of redirecting you to a different pool you don't want to be hashing on. Stratum reconnect will only honour the request if the reconnect is to a server with the same domain name.
- Fix for some overflow errors on stats with massive hashrates/shares.
- Fix a major memory leak which mostly affected hashfast users.
- Fix for a failed connection after a redirection that would then never return.
- Devices with unique serial numbers of 4 or more characters will now be displayed by their serial number in the status bar.
- Support for new firmware for OneStringMiners that will identify themselves as OSM devices.
- Support for OSM debugging and LED modes.
- A1 driver updates.


Full changelog:

- Make reconnection messages more explanatory
- Fix accounting bug with nrolltime drivers
- upgrade some int to int64_t to avoid overflows in reporting
- Stratum client.reconnect require matching URL
- Fix memory leak in submit_noffset_nonce
- Clean up any work that may not have been used in the work scheduler
- Avoid unnecessary deref now that it's done within discard_work
- Clean work pointers after one way usage functions
- Avoid unnecessary total_work_inc in generating local work
- Cosmetic fixes
- Fix idle bug, when redirected client can't auth
- Rename spond temp rate to asics total rate
- Build fixes
- Set the unique id only for usb devices with serial strings longer than 4 chars
long
- Use usb serial strings as unique id if devices have them
- Discretely identify the onestring miners as OSM
- Add bxf debugging option and osm led modes
- A1: modularize board selector / add initial CCR support
- A1: cleanup tca9535 logging
- A1: fix and extend PLL parameters
- A1: clean up compile warnings
- A1: use real level in hexdump
- Add identification for onestring miner variants
- Avalon2: Parser the power good signal
- driver-avalon2: this functions used on detect, which don't have thr setup yet

Hello, after the update i have follow problem:

USB management [P]ool management Settings [D]isplay options [Q]uit
 0: ANU 0       :                         | 23.36M / 1.488Gh/s WU:20.9/m
 1: ANU 1       :                         | 402.6M / 1.521Gh/s WU:20.2/m
--------------------------------------------------------------------------------
 [2014-05-03 20:21:46] ANU0: Comms error (werr=0 amt=0)
 [2014-05-03 20:22:05] ANU1: Comms error (werr=0 amt=0)
 [2014-05-03 20:22:21] ANU0: Comms error (werr=0 amt=0)
 [2014-05-03 20:22:33] Shutdown signal received.

Is this a Bug or I have a problem with my HUB?

greets

[kano]

...
Hello, after the update i have follow problem:

USB management [P]ool management Settings [D]isplay options [Q]uit
 0: ANU 0       :                         | 23.36M / 1.488Gh/s WU:20.9/m
 1: ANU 1       :                         | 402.6M / 1.521Gh/s WU:20.2/m
--------------------------------------------------------------------------------
 [2014-05-03 20:21:46] ANU0: Comms error (werr=0 amt=0)
 [2014-05-03 20:22:05] ANU1: Comms error (werr=0 amt=0)
 [2014-05-03 20:22:21] ANU0: Comms error (werr=0 amt=0)
 [2014-05-03 20:22:33] Shutdown signal received.

Is this a Bug or I have a problem with my HUB?

greets

... smaller quotes thanks ...

Anyway, there are no changes to the Icarus driver.

Probable causes are:
1) Overheating - although it's getting colder here, it's getting hotter in the northern hemisphere - these things have no temperature sensors - they are stupid
2) Power, as usual, if your hub isn't providing enough or it's plug pack is now over heating. 2000mA seems to be needed for 2xANU
3) General hardware problems as you suggested

[kano]

Updated AntS1 cgminer binary to 4.3.2a
The binary and README are in my cgminer-binaries git here:
https://github.com/kanoi/cgminer-binaries/tree/master/AntS1  <-- Follow this link to get the new binary

Read the README on the screen there for how to replace the /usr/bin/cgminer binary in your AntS1 with the new one.

Thus it includes a client.reconnect patch:
"minimise the risk of the man-in-the-middle attack of redirecting you to a different pool"

This, as usual, includes the cgminer patch for the luci web display.

There's info in the README to update the luci code if LSTime is showing incorrectly after the update
(most newer AntS1's)

I've also documented steps to update the cgminer-monitor to restart cgminer if Elapsed Time is greater than 4 weeks.
This usually means the clock has messed up on the AntS1.
If you do mine for 4 weeks non-stop, it's simply a cgminer restart so no problem.

My source for this version is here:
https://github.com/kanoi/cgminer/tree/ants1-4.3.2a-85fcf0c

This binary includes all cgminer changes up to 4.3.2 and forward after that up to:
https://github.com/ckolivas/cgminer/commit/686d648f15d6c70f252c411242ecd7edc7294f90

[Raptor2213]

Updated AntS1 cgminer binary to 4.3.2a
The binary and README are in my cgminer-binaries git here:
https://github.com/kanoi/cgminer-binaries/tree/master/AntS1  <-- Follow this link to get the new binary

Read the README on the screen there for how to replace the /usr/bin/cgminer binary in your AntS1 with the new one.

Thus it includes a client.reconnect patch:
"minimise the risk of the man-in-the-middle attack of redirecting you to a different pool"

This, as usual, includes the cgminer patch for the luci web display.

There's info in the README to update the luci code if LSTime is showing incorrectly after the update
(most newer AntS1's)

I've also documented steps to update the cgminer-monitor to restart cgminer if Elapsed Time is greater than 4 weeks.
This usually means the clock has messed up on the AntS1.
If you do mine for 4 weeks non-stop, it's simply a cgminer restart so no problem.

My source for this version is here:
https://github.com/kanoi/cgminer/tree/ants1-4.3.2a-85fcf0c

This binary includes all cgminer changes up to 4.3.2 and forward after that up to:
https://github.com/ckolivas/cgminer/commit/686d648f15d6c70f252c411242ecd7edc7294f90

Good to know, now I need to downgrade to 4.2.2a.  I use a service that uses the client.redirect 'feature' to redirect to other pools.  I don't suppose there's a command-line option to disable this?