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

We don't have any specific code for that hardware so I'm guessing only an unofficial cgminer fork supports them so you'll have to seek help from whoever maintains that fork.

anything special I need to do to compile cgminer to work with btcgarden asics?

anyone have any idea with w_allow low level detected  errors specifically with btcgarden am-v1

0.0000 is not valid JSON at all, for anything. It should just read 0.0.

My workaround is here, so you can see: https://github.com/hashware/node-cgminer-api/blob/master/lib/client.js#L105. I have to manually replace "nan" with 0, otherwise JSON.parse() fails.

Crazy unicode character showing up in cgminer "stats()" response: https://github.com/hashware/node-cgminer-api/issues/10#issuecomment-59324280

Maybe its a Antminer thing, but cgminer shouldn't let invalid JSON be returned.

All cgminer USB on windows uses zadig - same driver config for everything.

Do we use the zadig drivers for the Avalon Nanos or is there a different driver?
These things are buggy that is for sure.

Hello,

Support the Cgminer in the stock version also the Technobit:

240 GHs HEX8A1 Coincraft A1 miner?

sudo ./autogen.sh --enable-hexminera --enable-hexminerc --enable-hexminerb --enable-hexmineru --enable-hexminer8

or only with the HEX patch?

THX

New release: Version 4.7.0, 14th October 2014


Human readable changelog:

- ipv6 support for the API
- Block erupter tube and prisma support
- Support for the avalon nano usb stick
- Support for the --suggest-diff stratum option, currently only supported by ckpools
- Add pool number to addpool response from API
- Make responses to restart and quit from the API valid json
- Change spondoolies sp30 hashrate to valid share based meter
- Add support for a minimum difficulty for slow controllers to not spiral out of control, this will initially make the devices look slow at the pool until vardiff bumps them up properly past the mindiff.
- Change the default queue back to 1 since increasingly devices are on slow controllers and will inevitably increase their queue size to max
- Avalon2 tweaks, show max temperature on command line


Full changelog:

- Implement generic inet_pton for windows
- Fix warnings
- Fix bulk of remaining style in blockerupter.c
- Tidy style in blockerupter.h
- Tidy bulk of style in blockerupter.c
- Fix missing minimum diff setting for blockerupter
- Fix unused variable warnings
- remove unnecessary sleep; fix potenital div by 0 errs; use min_diff in driver
definition
- Fix coding style
- Make the sp30 hashrate meter based on valid share generation
- Change default max queue back to 1 in line with speed of most current asic
controllers
- Change diff limits to values suitable for sp30
- Add pool number to response from addpool to the API
- Make the restart and quit API commands valid json responses
- Fix number of nos
- Add option to set clock ('--bet-clk X' actual clock is (X+1)*10 )
- compatible with X24 board
- Fix error when using v6 without mask in api-allow
- Support ipv6 multicast
- Set min_diff to 1
- Allow arbitrary clamping of lower device diffs for slow controllers by driver
- Don't set default fan to max on hashratio
- The 2nd read never gets anything on ava2 so remove it entirely and just return
an error if we are out of sync
- Implement support for mining.suggest_difficulty
- Fix client ip address output
- Free addrinfo garbage
- Remove the brackets when using v6 pool address
- Add ipv6 support for api listen
- Avalon Nano: Add support Avalon Nano usb miner
- fix bug in setdiff
- limit minimum diff to 64
- Add BlockErupter Driver
- Avalon2: display currect max temperature on statline
- Remove unused variable

I don't get that when I try:

Perhaps you're trying to read them as integers? (They're doubles).

Yeah, 1 should use the values programmed into the device itself.

BUG: the "devs" command returns invalid JSON if no shares have been accepted yet:


It'd be *really* nice to be able to file these in Github so they can be related to the code, and we can track when they are fixed.

Not sure in the case of the habanero since I only ever worked on actual hashfast gear. Probably, give it no clock command at all.

Will look into your bug reports with Kano, the API maintainer, thanks.

API Documentation Bug:


The reply for the "check" command is actually "CHECK", not "COMMAND".

Yes, you need ASIC mining hardware.  CPU and GPU mining is no longer supported with CGMiner and is really a waste of money to mine Bitcoin like that now.

There is an alt coin forum where you can learn about other coin chains that can still be mined with CPU and/or GPU.

Edit:  If you want to research Bitcoin ASIC's you can start here

https://en.bitcoin.it/wiki/Mining_hardware_comparison

I am just running it off of my computer, do you need a certain hardware for this? I am a noob at this so sorry

Dunno.  What's your mining hardware?

So is started it up with a .bat file

cgminer -o stratum.bitcoin.cz:3333 -u Fatal_Leg4cy.worker1 -p x

and it loaded and satarted but all that keeps coming up is "Stratum from pool 0 detected new block" nothing else.
So is it working?

There's a bug with the "restart" JSON API command. It returns this data on success:


Of course, this is not valid JSON, so it has to be parsed differently and handled as a special case in my API: https://github.com/hashware/node-cgminer-api.