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

I'll try to enable a log but all I know is I had it restarted by someone and came home and found all devices marked as sick and it trying to restart though it obviously wasn't having success. btcguild brought down the alternate pool so I guessing this may be an alternate problem.  Whatever it is happened fast as I had it turned on at 5 and was fudged by 5:15 .

I had the impression with antminers you could change the overclock and under clock  them like a for example drillbit devices.

Here's the link to the how to guide I was originally reading up on when I bought my antminers. https://github.com/AntMiner/AntGen1/tree/master/manual

These things seem to have a little more brains to mess with and I want to be able to treat them as such....please

This request has nothing to do with my previous pm just in case you thought that.


edit...

  I made it past 30 minutes since restart. Maybe the devices weren't ready yet for a restart when I loaded last.
 edit 2
 went to 53 minute then kept getting block with no work and then everything went sick when I tried to change pools. One eroupter lost connection to the pc and I'm reinstalling the driver for it.  I'm going to take a pic and see what goes sick first at least.

oh and just noticed at least they have different names though I haven't tried commands yet

edit 3
Something tells me cgminer hates coinex's switchpool. I took a pic and first I saw btcguild found a block then coinex kept looking for a block till I got a no error and then no device error for my drillbit thumb. I hope that doesn't mean bad things for my drillbit thumb.

Not quite, is there anything to gain from the other driver apart from it being "different" ?

I'm still unable to reproduce your btcguild bug so I'd need debug output from someone who gets it to try and figure out why it's still happening.

In jimjags build I thought it was a separate driver for antminer (bmsc or something) So I thought the end result would be the same here to differentiate the devices and use the commands that should be available for antminers (and probably s1's though like you said they have their own interface)

Still my joy has led to bah that btc guild still probably kills cgminer and I didn't set the right pool to avoid this (I got in mid block and cgminer stopped 2 hours after starting)

Does that clarify what I mean?

Are you asking if antminer U1s work with other icarus devices? Of course they do. Are you asking about the S1 miner? That doesn't use regular USB so can only be run on the included tplink router hardware as far as I understand it.

So I'm not sure what your question is?

Hey
I am running a Avalon 200 clone (openwrt with CGminer - firmware for the unit is dated 2013 Nov. 10).
I am seeing a 20-25% discrepancy in hash rate between what the unit is reporting and the 2 pools I tried (BTCguild, BTCdig).
The actual numbers:

Openwrt repors (under CGminer status):
230 GH/s (I'm oc'ed to 1500 - the same pattern was observed when non-o/c I tried..)

BTCdig sees ~ 150-160 GH/s
BTCguild sees ~ 175-190 GH/s

the number of rejected/stale are normal - nothing obvious there. I could post a screenshot of the Cgminer status page if that helps.

I could also get a new firmware but no clue where I could get it from (for this specific unit that is)

Any help is appreciated
thanks
-S.

Mac build will be delayed until this evening (forgot my development HDD at home).

Also, the title of this thread still is at 3.11.0.  I almost missed that a new version was out.

Is the driver for the Technobit HEX16A2 20GH Avalon board gone in to cgminer mainstream, or would I have to rely on a patched version of cgminer?

Bonus question, if it is mainstream, can I also run a Bitburner Fury alongside (which is a Bitfury based board pretending to be an Avalon)?

Just to be a pain in the butt, but are you still working on making the antminer on its own driver so its own settings can be used. Still awesome step getting it to work. Jimjags version had it in a separate driver. I cant confirm or deny if its better since he only compiles in mac but hopefully its possible.

this new version works fine and very stable in my system and my antminer usb goes aroun 1.5, 1.6Gh/s,

Not from cgminer itself, no.

Good day,

thanks for the really fast FIX for the Antminer, but is with the ICARUS driver also overclocking possible?

regards

New version: 3.12.0, 29th January 2014

- Another even number, so it's gotta be stable!

Human readable changelog:

- Antminer U1 support
- Numerous fixes for behaviour surrounding USB errors - pipe and IO errors, and no more attempting to reset the device since it's rarely helpful and occasionally harmful.
- Libusb and libusbx have finally reconciled their differences and merged all their fixes together into a new official libusb release, so the main change in this version is updating the core code to include this latest libusb. Hopefully this might increase compatibility with some USB3 hubs on windows and make it more reliable (based on the changelogs I can see in libusb). This is the reason for the minor version number update to 12 as it's quite a substantial code change, hopefully only for the better!
- Increased the hashfast overheat limit default to 90 after extensive discussions with the engineers who designed the devices.
- Fixed a crash in the nanofury USB stick code.
- Fixed the displayed diff shown being wrong when solo mining.
- bab driver fixes courtesy of Kano.


Full changelog:

- Add support for AntminerU1 devices with the icarus driver.
- Add antminer U1 to comment in udev rules.
- Do away with usb resets entirely since we retry on both pipe and io errors now
and they're of dubious value.
- Retry on usb IO errors instead of faking success.
- Check that we've cleared the pipe error after a clear request, not the err
value which is unchanged.
- Update to libusb-1.0.18
- Change hfa overheat limit to 90 degrees.
- Relax timeout in hf get header to 500ms to match the usb timeout.
- Minion - check/clear interrupts for all chips
- Set info work to null after it is freed in nf1 after a restart to prevent
double free later.
- The second_run bool in libbitfury should be per device. Microoptimise its and
job_switched usage, removing the unused results array for NF1 devices.
- Fix displayed diff when solo mining at >2^32 diff.
- bab - stop stale work accumulating
- bab - set the default SPI speed back to 96000

this version is stable i run it for days without any problem. The version of cgminer there is 3.09

Hello, is the inofficial Cgminer 24/7 stable?


If so, what version it is under the link?

https://github.com/fractalbc/cgminer

greets

Thanks.

Your missing the 6 post just before you posted this message.

Just searched the README.txt, NEWS.txt and ASIC-README.txt. Found nothing about Antminer support.  What am I missing?
Thanks.

https://github.com/bitmaintech/cgminer

That is a fork of cgminer back in Sep of '13.  I have started on a patch from cgminer-3.10.0 (just did the diff -r), but now that you are interested, I'll go back to my real job...

https://github.com/fractalbc/cgminer

thats what i use. it works nice with 21 antminers and 37 block erupters!

Someone want to point me to the best current cgminer code for them please?