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

[taipo]

Will upgrading the S1s to this latest version affect the use of the Slush proxy between the miners and the pool?

[-ck]

Will upgrading the S1s to this latest version affect the use of the Slush proxy between the miners and the pool?

No, but if the slush proxy supports mining redirection then you are still open to the attack of being redirected and are not being protected by cgminer.

[Dunkelheit667]

...That having been said, I didn't say not to try it...

I'm sorry, didn't want to put your findings into question, just shared my experiences in addition. No offense intended.

Huh well Raspbian and ARCH list 3.10 firmware. I wonder why there would be no kernel change between distributions. I don't know myself so I wonder. I can't seem to find anything specific. If you know something I am missing (I don't use Linux as much as I likely should) I would love to know. Maybe everyone builds from the same source. I don't think so but maybe. If so I suppose it was magic that my 30 minute to 2 hour delay between lockups went away with arch rather then up to date Raspbian.

You can build at least from the same source - this is an interesting read. Indeed there may be some (minor) changes, so not 100% sure if both kernels are actually the same. Major differences between distributions are e.g. different libraries. Like the old problems with different libusb versions. Can not remember exactly which kind of issues, but one distribution worked fine the other caused issues just because of different library versions. As libusb comes now with cgminer and cgminer is not using the system library, these (old) issues are gone.

[taipo]

Will upgrading the S1s to this latest version affect the use of the Slush proxy between the miners and the pool?

No, but if the slush proxy supports mining redirection then you are still open to the attack of being redirected and are not being protected by cgminer.

Well I must have done something wrong here then because having patched the S1's, my slush proxy is showing now as a dead pool on all of the Ants.

[-ck]

Will upgrading the S1s to this latest version affect the use of the Slush proxy between the miners and the pool?

No, but if the slush proxy supports mining redirection then you are still open to the attack of being redirected and are not being protected by cgminer.

Well I must have done something wrong here then because having patched the S1's, my slush proxy is showing now as a dead pool on all of the Ants.

I guess you need to check with support from slush then cos I wasn't aware it would use redirect in any way within the proxy code, unless it's because you're using an IP address directly?

[retrogeek]

Having problems getting my Drillbit Avalon Thumb Gen2 to hash.

Using 4.3.3, compiled with --enable-drillbit, cgminer picks up the device but hashing stays at 0

Code:

cgminer version 4.3.3 - Started: [2014-05-06 12:13:42]
--------------------------------------------------------------------------------
 (5s):0.000 (1m):0.000 (5m):0.000 (15m):0.000 (avg):0.000h/s
 A:0  R:0  HW:0  WU:0.0/m
 Connected to stratum.bitcoin.cz diff 1 with stratum as user [user]
 Block: 8a266ea0...  Diff:8G  Started: [12:13:42]  Best share: 0
--------------------------------------------------------------------------------
 [U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
 0: DRB 0       : A 1                     |  0.000 /  0.000h/s WU:0.0/m
--------------------------------------------------------------------------------
 [2014-05-06 12:13:36] Started cgminer 4.3.3
 [2014-05-06 12:13:36] Loaded configuration file ../cgminer.conf
 [2014-05-06 12:13:37] DRB 0: Config: int:500:1:900 Serial: 460c3a00
 [2014-05-06 12:13:37] Probing for an alive pool
 [2014-05-06 12:13:41] Pool 0 difficulty changed to 3
 [2014-05-06 12:13:42] Network diff set to 8G
 [2014-05-06 12:13:47] API running in IP access mode on port 4028 (15)
 [2014-05-06 12:14:13] Pool 0 difficulty changed to 1
 [2014-05-06 12:14:13] Stratum from pool 0 requested work restart

Do I have bad hardware?

[techman05]

Probably not but you should check on http://drillbitsystem.com/forum/index.php  . Ckolivias can only do so much for individual products and you'll get a better response there.

[kano]

Having problems getting my Drillbit Avalon Thumb Gen2 to hash.

Using 4.3.3, compiled with --enable-drillbit, cgminer picks up the device but hashing stays at 0

...

Do I have bad hardware?

I've got a T 1 (and an E 8 ) but not an A 1
Though that's my fault since they had some miners for me but I never went and got them (they don't live far from me)
I'm still running 4.2.2a on the T 1 coz that's on my RPi.
Building 4.3.3a now to see if there's any issues ... I'll update here once it's running (takes a while to build on an RPi)

[retrogeek]

I'll update here once it's running (takes a while to build on an RPi)

Many thanks Kano - appreciate it.

My eclectic little miner collection (a Hex Fury, a couple of Jalapenos, a bunch of U1s and the problematic A1) will thank you!

 - r

[kano]

I'll update here once it's running (takes a while to build on an RPi)

Many thanks Kano - appreciate it.

My eclectic little miner collection (a Hex Fury, a couple of Jalapenos, a bunch of U1s and the problematic A1) will thank you!

 - r

Yeah sorry - got side tracked last night testing new hardware
But there were no problems with the T1 with the latest code.
So it must be A1 specific or a hardware setup problem.

Code:

cgminer version 4.3.3 - Started: [2014-05-07 14:01:51]
--------------------------------------------------------------------------------
 (5s):2.663G (1m):2.950G (5m):3.212G (15m):3.121G (avg):3.054Gh/s
 A:44070  R:49  HW:2069  WU:42.6/m
 Connected to multiple pools with block change notify
 Block: 317dc477...  Diff:8G  Started: [07:14:31]  Best share: 54.4K
--------------------------------------------------------------------------------
 [U]SB management [P]ool management [ S]ettings [D]isplay options [Q]uit
 0: AMU 0       :                         | 394.8M / 334.3Mh/s WU: 4.7/m
 1: DRB 0       : T 1                     | 2.159G / 2.051Gh/s WU:28.7/m
 2: AMU 1       :                         | 336.8M / 334.6Mh/s WU: 4.7/m
 3: AMU 2       :                         | 335.5M / 334.4Mh/s WU: 4.6/m
--------------------------------------------------------------------------------

(run time >15 hrs)

[Polyatomic]

Block change notify. That's cool.

[-ck]

ckolivas,

Can i use cgminer with a cube erupter?

No

[techman05]

There's so much more you can do with your money why would you go that way. You have a seller on Amazon.com selling an antminer for 200 plus shipping and 20 ghash drillbit avalons at $65 a piece with free shipping with more than one if you go through barntech. Both by the way are 100 percent using cgminer behind them.

[Taugeran]

What is the manner for individually setting the oscillator bits for separate nanofuries?

[KyrosKrane]

Just checking if the thread title is correct? It still reads 4.3.2, even though the first post lists 4.3.3 as current.

[techman05]

Just checking if the thread title is correct? It still reads 4.3.2, even though the first post lists 4.3.3 as current.

He's just been personally moderating this post so there's an opening for chaos and invalid details. 4.3.3 is the newest until otherwise specified on github or http://ck.kolivas.org/apps/cgminer/

[Zich]

Just checking if the thread title is correct? It still reads 4.3.2, even though the first post lists 4.3.3 as current.

New release: Version 4.3.3, 4th May 2014


Human readable changelog:

- Fox for a huge long-standing memory leak with the BXF driver which affected bi*fury, hex*fury and OneString miners.
- Formatting fixes for miner.php


Full changelog:

- Fix typo
- Work should be freed when aged, fixing a massive memory leak for bxf devices
- miner.php fix single rig summary/config field formatting
- miner.php fix single rig total formatting

[vayvanne]

cgminer-4.3.3-windows stops to respond to key presses after I restart it by pressing [scy]. hashing continues.

[-ck]

cgminer-4.3.3-windows stops to respond to key presses after I restart it by pressing [scy]. hashing continues.

Restart's always been precarious and much worse so on windows. Just quit and start again instead. Yes I agree it's not ideal but restart should probably have never been put there for windows since it ends up killing shit to shut down the existing instance instead of shutting down neatly.

[Bgkoffler]

All -

I am new to this board so please don't attack

I have been using CGMiner successfully for a few months using one of the pre-built versions from http://ck.kolivas.org/apps/cgminer/.

I now need to build the program so that i can add Hash Fast support, allowing me to monitor the temperature of each die on my cards, but when i built it myself i don't have the information showing up at the top of the screen that i normally get - and it just doesn't seem to work for me!

Any thoughts on how i can successfully build this would be greatly appreciated. The instructions in the README as self explanatory and i followed them each time - the end product is just not what i am looking for.

Thanks,

BK