Hi all.
Using Raspberry, OS Raspbian, Cgminer 4.8.0 (from https://github.com/bitmaintech/cgminer) and Antminer U3.
At working, Cgminer show 10-15Gh, but in Bitmain specifications U3 hash rate 63Gh±5%.
Maybe worked 1 of 4 chip in AU3? Any way solve this problem?
Thanks.
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 47. (Read 5805649 times)
May 15, 2015, 01:51:38 AM
May 13, 2015, 08:44:19 PM
I cloned and built cgminer from https://github.com/ckolivas/cgminer yesterday and it wouldn't work with my ASICMiner Tubes connected via USB.
I decided to try the version here: https://github.com/blockerupter/cgminer and it worked, but it's six months old.
Is this a known issue? Or should I start digging to see what broke it?
I decided to try the version here: https://github.com/blockerupter/cgminer and it worked, but it's six months old.
Is this a known issue? Or should I start digging to see what broke it?
If the version you last compiled is working, what features would you need from the new version?
Why not stick to that one?
Regressions are usually worth looking into.
Thanks for the reply. I was under the impression that it worked at some point. I'll just use the working version from the blockerupter repo.
May 13, 2015, 06:14:19 PM
I cloned and built cgminer from https://github.com/ckolivas/cgminer yesterday and it wouldn't work with my ASICMiner Tubes connected via USB.
I decided to try the version here: https://github.com/blockerupter/cgminer and it worked, but it's six months old.
Is this a known issue? Or should I start digging to see what broke it?
I decided to try the version here: https://github.com/blockerupter/cgminer and it worked, but it's six months old.
Is this a known issue? Or should I start digging to see what broke it?
If the version you last compiled is working, what features would you need from the new version?
Why not stick to that one?
Regressions are usually worth looking into.
May 13, 2015, 12:10:38 PM
I cloned and built cgminer from https://github.com/ckolivas/cgminer yesterday and it wouldn't work with my ASICMiner Tubes connected via USB.
I decided to try the version here: https://github.com/blockerupter/cgminer and it worked, but it's six months old.
Is this a known issue? Or should I start digging to see what broke it?
I decided to try the version here: https://github.com/blockerupter/cgminer and it worked, but it's six months old.
Is this a known issue? Or should I start digging to see what broke it?
If the version you last compiled is working, what features would you need from the new version?
Why not stick to that one?
Regressions are usually worth looking into.
May 13, 2015, 11:32:23 AM
I cloned and built cgminer from https://github.com/ckolivas/cgminer yesterday and it wouldn't work with my ASICMiner Tubes connected via USB.
I decided to try the version here: https://github.com/blockerupter/cgminer and it worked, but it's six months old.
Is this a known issue? Or should I start digging to see what broke it?
I decided to try the version here: https://github.com/blockerupter/cgminer and it worked, but it's six months old.
Is this a known issue? Or should I start digging to see what broke it?
If the version you last compiled is working, what features would you need from the new version?
Why not stick to that one?
May 13, 2015, 08:08:26 AM
I cloned and built cgminer from https://github.com/ckolivas/cgminer yesterday and it wouldn't work with my ASICMiner Tubes connected via USB.
I decided to try the version here: https://github.com/blockerupter/cgminer and it worked, but it's six months old.
Is this a known issue? Or should I start digging to see what broke it?
I decided to try the version here: https://github.com/blockerupter/cgminer and it worked, but it's six months old.
Is this a known issue? Or should I start digging to see what broke it?
May 05, 2015, 01:11:26 PM
I had an issue raised on git regarding the S1 API.
Seems it may have been a user typing error?
Anyone else seen any problem like this that they can reproduce?
https://github.com/kanoi/cgminer-binaries/issues/9
The API IPv6 changes by someone else were initially problematic but later fixed.
So, I wasn't 100% certain if there were still any more IPv4 problems from the changes for the IPv6 code.
Seems it may have been a user typing error?
Anyone else seen any problem like this that they can reproduce?
https://github.com/kanoi/cgminer-binaries/issues/9
The API IPv6 changes by someone else were initially problematic but later fixed.
So, I wasn't 100% certain if there were still any more IPv4 problems from the changes for the IPv6 code.
I have no IPv4 problems with my S1 API running 4.9.1a.
Here's cryptoGlance reporting my S1 via API:
May 05, 2015, 04:37:36 AM
I had an issue raised on git regarding the S1 API.
Seems it may have been a user typing error?
Anyone else seen any problem like this that they can reproduce?
https://github.com/kanoi/cgminer-binaries/issues/9
The API IPv6 changes by someone else were initially problematic but later fixed.
So, I wasn't 100% certain if there were still any more IPv4 problems from the changes for the IPv6 code.
Seems it may have been a user typing error?
Anyone else seen any problem like this that they can reproduce?
https://github.com/kanoi/cgminer-binaries/issues/9
The API IPv6 changes by someone else were initially problematic but later fixed.
So, I wasn't 100% certain if there were still any more IPv4 problems from the changes for the IPv6 code.
May 04, 2015, 11:06:33 AM
No, the web interface shows the package version, which of course doesn't change when you replace the cgminer binary.
Quote
Looking very much forward to updated cgminer for my S3+, keep up the solid work, ck & Kano!
S2 is in the works now, the S3 is after that and will be more effort than the S1 and S2 combined 
That's what I figured, but wanted to double check. Thanks for including the API version check instructions, makes me feel better to verify that I did it correctly.
Good luck with S2 and S3, sorry to hear S3 is going to be so much work, hopefully it's worth it!
May 04, 2015, 04:58:04 AM
I really appreciate the easy to follow instructions. They are perfect for someone like me who barely knows what each line is doing, thank you.
Installed the new binary on one of my underclocked ants and now the discard rate is much higher. Averages around 6% now. With the previous binary (4.3.2)
it was around .2%. Is this normal?
Exact setting I am using: [196.88 69 5f06] with latest firmware.
Thanks!
it was around .2%. Is this normal?
Exact setting I am using: [196.88 69 5f06] with latest firmware.
Thanks!
On my now updated to 4.9.1a overclocked (393 freq) S1 I see 0 rejects (used to be around 0.3%), error rate is about the same ~1%. Hash rate is up a little, too, but we'll see how that levels out. I had to do the fix for LST time, but no big deal. I updated the monitor script, too.
Question, I verified the cgminer version via API, but is there a way to see the version from the web GUI, too? Just curious.
Quote
Looking very much forward to updated cgminer for my S3+, keep up the solid work, ck & Kano!
S2 is in the works now, the S3 is after that and will be more effort than the S1 and S2 combined May 03, 2015, 06:36:27 PM
Installed the new binary on one of my underclocked ants and now the discard rate is much higher. Averages around 6% now. With the previous binary (4.3.2)
it was around .2%. Is this normal?
Exact setting I am using: [196.88 69 5f06] with latest firmware.
Thanks!
Discards do not matter.it was around .2%. Is this normal?
Exact setting I am using: [196.88 69 5f06] with latest firmware.
Thanks!
Did you mean Rejects?
If so post the full set of relevant numbers:
Elasped, DiffA, DiffR
Rejects are actually very low. Just curious about the discards.
May 03, 2015, 06:26:43 PM
Installed the new binary on one of my underclocked ants and now the discard rate is much higher. Averages around 6% now. With the previous binary (4.3.2)
it was around .2%. Is this normal?
Exact setting I am using: [196.88 69 5f06] with latest firmware.
Thanks!
Discards do not matter.it was around .2%. Is this normal?
Exact setting I am using: [196.88 69 5f06] with latest firmware.
Thanks!
Did you mean Rejects?
If so post the full set of relevant numbers:
Elasped, DiffA, DiffR
Rejects are actually very low. Just curious about the discards.
May 03, 2015, 05:49:02 PM
Installed the new binary on one of my underclocked ants and now the discard rate is much higher. Averages around 6% now. With the previous binary (4.3.2)
it was around .2%. Is this normal?
Exact setting I am using: [196.88 69 5f06] with latest firmware.
Thanks!
Discards do not matter.it was around .2%. Is this normal?
Exact setting I am using: [196.88 69 5f06] with latest firmware.
Thanks!
Did you mean Rejects?
If so post the full set of relevant numbers:
Elasped, DiffA, DiffR
May 03, 2015, 04:27:08 PM
I really appreciate the easy to follow instructions. They are perfect for someone like me who barely knows what each line is doing, thank you.
Installed the new binary on one of my underclocked ants and now the discard rate is much higher. Averages around 6% now. With the previous binary (4.3.2)
it was around .2%. Is this normal?
Exact setting I am using: [196.88 69 5f06] with latest firmware.
Thanks!
it was around .2%. Is this normal?
Exact setting I am using: [196.88 69 5f06] with latest firmware.
Thanks!
On my now updated to 4.9.1a overclocked (393 freq) S1 I see 0 rejects (used to be around 0.3%), error rate is about the same ~1%. Hash rate is up a little, too, but we'll see how that levels out. I had to do the fix for LST time, but no big deal. I updated the monitor script, too.
Question, I verified the cgminer version via API, but is there a way to see the version from the web GUI, too? Just curious.
Looking very much forward to updated cgminer for my S3+, keep up the solid work, ck & Kano!
May 03, 2015, 12:35:00 PM
Installed the new binary on one of my underclocked ants and now the discard rate is much higher. Averages around 6% now. With the previous binary (4.3.2)
it was around .2%. Is this normal?
Exact setting I am using: [196.88 69 5f06] with latest firmware.
Thanks!
it was around .2%. Is this normal?
Exact setting I am using: [196.88 69 5f06] with latest firmware.
Thanks!
May 03, 2015, 12:49:27 AM
I've put up a new AntS1 binary in my binaries git hub of latest 4.9.1a cgminer - of course with the cgminer git version with the fixes in it.
I've tested it on my pool https://kano.is/ and also on p2pool (fired up my home one for a while for testing)
For details and installing: https://github.com/kanoi/cgminer-binaries/tree/master/AntS1
I've tested it on my pool https://kano.is/ and also on p2pool (fired up my home one for a while for testing)
For details and installing: https://github.com/kanoi/cgminer-binaries/tree/master/AntS1
Great, will update my S1 straight away. Thank you!
May 02, 2015, 04:50:22 PM
I've put up a new AntS1 binary in my binaries git hub of latest 4.9.1a cgminer - of course with the cgminer git version with the fixes in it.
I've tested it on my pool https://kano.is/ and also on p2pool (fired up my home one for a while for testing)
For details and installing: https://github.com/kanoi/cgminer-binaries/tree/master/AntS1
I've tested it on my pool https://kano.is/ and also on p2pool (fired up my home one for a while for testing)
For details and installing: https://github.com/kanoi/cgminer-binaries/tree/master/AntS1
May 02, 2015, 04:47:21 PM
Hi, I see these errors once and a while with 800 Monarchs BMA0: Ran out of queued IDs after 6 of 7.
What does it mean? Also sometimes I see hex2bin str truncated.
And BMA0: incorrect result count 10 (INPROCESS:00x00) will try 10 (COUNT: 100x00)
I'm using 4.9.1 built from github on ubuntu x64
Thanks
USB hardware errors.What does it mean? Also sometimes I see hex2bin str truncated.
And BMA0: incorrect result count 10 (INPROCESS:00x00) will try 10 (COUNT: 100x00)
I'm using 4.9.1 built from github on ubuntu x64
Thanks
Try replacing the cables or your hub and make sure you are using USB2.0 port.
May 01, 2015, 06:23:28 AM
Hi, I see these errors once and a while with 800 Monarchs BMA0: Ran out of queued IDs after 6 of 7.
What does it mean? Also sometimes I see hex2bin str truncated.
And BMA0: incorrect result count 10 (INPROCESS:00x00) will try 10 (COUNT: 100x00)
I'm using 4.9.1 built from github on ubuntu x64
Thanks
What does it mean? Also sometimes I see hex2bin str truncated.
And BMA0: incorrect result count 10 (INPROCESS:00x00) will try 10 (COUNT: 100x00)
I'm using 4.9.1 built from github on ubuntu x64
Thanks
May 01, 2015, 02:03:38 AM
Hi. Thank you for your effort developing cgminer. Im interested in working with cgminer to develop some programs (like a GUI) and I want to ask you to questions:
I just ordered today a Usb miner but I want to start right now to develop but I cant run Cgminer, there is part in code which I can rewrite or some other way to run 4.9.1 on testnet without a USB miner?
My next question is if I start to develop with an older version (which suports GPU mining) via API, my program would be compatible with 4.9.1 when I get my USB miner?
Thank you for your time.
All changes I have done to the API since I first wrote it have been backward compatible except when removing functionality no longer needed.I just ordered today a Usb miner but I want to start right now to develop but I cant run Cgminer, there is part in code which I can rewrite or some other way to run 4.9.1 on testnet without a USB miner?
My next question is if I start to develop with an older version (which suports GPU mining) via API, my program would be compatible with 4.9.1 when I get my USB miner?
Thank you for your time.
That was one of the big design issues I decided upon when I first completed writing the API.
Other have screwed with that compatibility so you may or may not get what you expect.
Jump to: