Mikestang
Legendary
Offline
Activity: 1274
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
May 03, 2015, 05:49:27 AM |
|
Great, will update my S1 straight away. Thank you!
|
|
|
|
helipotte
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
May 03, 2015, 05: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!
|
|
|
|
Mikestang
Legendary
Offline
Activity: 1274
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
May 03, 2015, 09: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!
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!
|
|
|
|
kano
Legendary
Offline
Activity: 4578
Merit: 1851
Linux since 1997 RedHat 4
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
May 03, 2015, 10: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. Did you mean Rejects? If so post the full set of relevant numbers: Elasped, DiffA, DiffR
|
|
|
|
helipotte
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
May 03, 2015, 11: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. 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.
|
|
|
|
kano
Legendary
Offline
Activity: 4578
Merit: 1851
Linux since 1997 RedHat 4
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
May 03, 2015, 11: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. 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. Discards are unused work - so they mean nothing in terms of shares or hash rate.
|
|
|
|
kano
Legendary
Offline
Activity: 4578
Merit: 1851
Linux since 1997 RedHat 4
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
May 04, 2015, 09: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!
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. No, the web interface shows the package version, which of course doesn't change when you replace the cgminer binary. 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 ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
|
Mikestang
Legendary
Offline
Activity: 1274
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
May 04, 2015, 04:06:33 PM |
|
No, the web interface shows the package version, which of course doesn't change when you replace the cgminer binary. 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 ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) 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!
|
|
|
|
kano
Legendary
Offline
Activity: 4578
Merit: 1851
Linux since 1997 RedHat 4
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
May 05, 2015, 09: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/9The 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.
|
|
|
|
Mikestang
Legendary
Offline
Activity: 1274
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
May 05, 2015, 06:11:26 PM Last edit: May 05, 2015, 06:21:33 PM by Mikestang |
|
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/9The 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: ![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fi59.tinypic.com%2Fvzygdx.jpg&t=665&c=Qg_hXNX8Z84XFA)
|
|
|
|
|
Jay_Pal
Legendary
Offline
Activity: 1493
Merit: 1003
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
May 13, 2015, 04:32:23 PM |
|
If the version you last compiled is working, what features would you need from the new version? Why not stick to that one?
|
|
|
|
WBF1
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
May 13, 2015, 05:10:38 PM |
|
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.
|
|
|
|
-ck (OP)
Legendary
Offline
Activity: 4214
Merit: 1644
Ruu \o/
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
May 13, 2015, 11:14:19 PM |
|
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. You're comparing it to a different codebase. As far as I'm aware, the blockerupter code that was contributed by them to mainline cgminer NEVER worked. None of the main devs ever got any hardware from them to get it working and they never contributed fixes to make sure it was working. I don't go chasing code from other people's branches to get mainline cgminer working with hardware from manufacturers that never really engaged the software community they depend on but I'm very happy to receive fixes from outside sources if they're willing to maintain it. The avalon nano and the blockerupter drivers both fall into the "submitted but broken code" category I'm afraid.
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
WBF1
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
May 14, 2015, 01:44:19 AM |
|
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. You're comparing it to a different codebase. As far as I'm aware, the blockerupter code that was contributed by them to mainline cgminer NEVER worked. None of the main devs ever got any hardware from them to get it working and they never contributed fixes to make sure it was working. I don't go chasing code from other people's branches to get mainline cgminer working with hardware from manufacturers that never really engaged the software community they depend on but I'm very happy to receive fixes from outside sources if they're willing to maintain it. The avalon nano and the blockerupter drivers both fall into the "submitted but broken code" category I'm afraid. 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.
|
|
|
|
Alien77
Newbie
Offline
Activity: 4
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
May 15, 2015, 06:51:38 AM |
|
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.
|
|
|
|
-ck (OP)
Legendary
Offline
Activity: 4214
Merit: 1644
Ruu \o/
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
May 15, 2015, 07:20:41 AM |
|
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. You're using the cgminer from bitmain instead of the official cgminer which this forum thread is about. Try cgminer 4.9.0 (best for U3) from the official sources (links in top post).
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
Alien77
Newbie
Offline
Activity: 4
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
May 15, 2015, 09:11:56 AM |
|
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. You're using the cgminer from bitmain instead of the official cgminer which this forum thread is about. Try cgminer 4.9.0 (best for U3) from the official sources (links in top post). Install cgminer-4.9.0 no effect. Still low hash rate(
|
|
|
|
NathanB
Newbie
Offline
Activity: 12
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
May 15, 2015, 10:05:32 AM |
|
--au3-freq 250 --au3-volt 800
try options
|
|
|
|
Alien77
Newbie
Offline
Activity: 4
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
May 15, 2015, 11:35:06 AM |
|
--au3-freq 250 --au3-volt 800
try options
Tried, nothing has changed. I may be incorrectly configured cgminer? ./configure --enable-icarus
|
|
|
|
|