I'm using the cgminer with gridseed support, I have one main issue which is really annoying can you tell me if it's fixed and which version it's fixed on. The problem is that I have to unplug the USB for my gridseed before cgminer starts, once cgminer has started only then I can plug the USB in otherwise the cgminer just freezes or crashes. If I'm accessing the rig remotely and I need to restart the windows computer then I'm stuck as some one physically needs to be at the rig.
Thank you guys
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 115. (Read 5805527 times)
March 13, 2014, 03:23:41 AM
March 12, 2014, 05:29:02 PM
Yeah, but I've not got that sorted out yet.
(My first attempt was a guess and it didn't solve luci not displaying the first two sections)
I'll get it soon ...
Thank you Kano... Looking forward to it! Token of appreciation sent to you and CK for all the work you guys put in. (My first attempt was a guess and it didn't solve luci not displaying the first two sections)
I'll get it soon ...
March 12, 2014, 05:23:11 PM
hi,
how can i update the cgminer version from a antminer s1? Normally the software is deployed with a new firmware.
thanks
Yeah I can build binaries and ipk files now.how can i update the cgminer version from a antminer s1? Normally the software is deployed with a new firmware.
thanks
I'm not 100% sure of building a complete firmware file, that will come a little later.
The luci web code that displays the stats doesn't work with the correct API code, so I'll see if I can sort that out today and hack a binary that works with both the luci code and of course includes the correct API output for anyone who accesses it.
hi,
thats sounds good
(My first attempt was a guess and it didn't solve luci not displaying the first two sections)
I'll get it soon ...
Good man kano.
A bit off topic, but have you or con played with the new 14.04 LTS (beta) release yet? I've had it on one of my laptops for a week or so & it seems to run sweet. Was wondering if you guys have looked at it yet & if cgminer will work with it "as is".
Thanks & Peace.
March 12, 2014, 05:00:02 PM
hi,
how can i update the cgminer version from a antminer s1? Normally the software is deployed with a new firmware.
thanks
Yeah I can build binaries and ipk files now.how can i update the cgminer version from a antminer s1? Normally the software is deployed with a new firmware.
thanks
I'm not 100% sure of building a complete firmware file, that will come a little later.
The luci web code that displays the stats doesn't work with the correct API code, so I'll see if I can sort that out today and hack a binary that works with both the luci code and of course includes the correct API output for anyone who accesses it.
hi,
thats sounds good
(My first attempt was a guess and it didn't solve luci not displaying the first two sections)
I'll get it soon ...
March 12, 2014, 03:46:28 PM
hi,
how can i update the cgminer version from a antminer s1? Normally the software is deployed with a new firmware.
thanks
Yeah I can build binaries and ipk files now.how can i update the cgminer version from a antminer s1? Normally the software is deployed with a new firmware.
thanks
I'm not 100% sure of building a complete firmware file, that will come a little later.
The luci web code that displays the stats doesn't work with the correct API code, so I'll see if I can sort that out today and hack a binary that works with both the luci code and of course includes the correct API output for anyone who accesses it.
hi,
thats sounds good
March 12, 2014, 01:00:55 AM
hi,
how can i update the cgminer version from a antminer s1? Normally the software is deployed with a new firmware.
thanks
how can i update the cgminer version from a antminer s1? Normally the software is deployed with a new firmware.
thanks
hi,
any feedback?
March 11, 2014, 09:32:39 AM
Thats good you got 1.2 boards but I do I search on ebay and people still have pictures of the u1 advertising as U2's so potentially room for scams.
Have you tried to push it past 2GH? I'd like to think if the U2s start at 2GH maybe you can get 2.5 or a lil bit more since they're supposed to have the updated resistors.
Pics for the lookers
https://bitcointalksearch.org/topic/m.5526949
Have you tried to push it past 2GH? I'd like to think if the U2s start at 2GH maybe you can get 2.5 or a lil bit more since they're supposed to have the updated resistors.
Pics for the lookers
https://bitcointalksearch.org/topic/m.5526949
March 10, 2014, 12:11:59 PM
The new CGMiner also support the new Antminer U2?
I mean yes, only the Heatsink is new?
regards
Try it and let us know I mean yes, only the Heatsink is new?
regards
We don't have any U2's but I think they are the same with just a better heat sink?
Hello,
today i obtained my new Antminer U1 batch, so i see they are HW Revision ANT USB V1.2 so the same Boardas the U2 but with the small Heatsink.
And they run 1A at Cgminer 4.1.0 with 2 GH/s so thanks
regards
March 10, 2014, 10:21:36 AM
I only have 5 eroupters and they seem to go forever. I haven't had a constant green light in a while and I've done each update with precomplied versions. I think the only time mine go visibly green is probably when a new block is found.
On another note I'll miss that green light when I finaly upgrade them out. Its the only way to know when things crap out without checking the cgminer program. Also not if someone does put a green light of death on their next device "Put a dimmer control"
On another note I'll miss that green light when I finaly upgrade them out. Its the only way to know when things crap out without checking the cgminer program. Also not if someone does put a green light of death on their next device "Put a dimmer control"
March 10, 2014, 09:46:56 AM
EDIT: Fixed in git, along with an opportunity for a further optimisation.
Any optimizations to help Block Erupters? Still not quite stable for me, 4.x that is.
4.0.x had regressions but there should be no reason 4.1 is any less stable with erupters than any of the best 3.x versions.
Well, I think I may have used an inaccurate phrase in "not quite stable".
It seems to run and doesn't crash. But it does turn off several erupters on both machines I use, erupters that run just fine on 3.8.4 and 3.11.0.
March 10, 2014, 09:42:35 AM
EDIT: Fixed in git, along with an opportunity for a further optimisation.
Any optimizations to help Block Erupters? Still not quite stable for me, 4.x that is.
4.0.x had regressions but there should be no reason 4.1 is any less stable with erupters than any of the best 3.x versions.
Thank you VERY MUCH!!!
March 10, 2014, 09:40:49 AM
EDIT: Fixed in git, along with an opportunity for a further optimisation.
Any optimizations to help Block Erupters? Still not quite stable for me, 4.x that is.
4.0.x had regressions but there should be no reason 4.1 is any less stable with erupters than any of the best 3.x versions.
March 10, 2014, 09:39:02 AM
EDIT: Fixed in git, along with an opportunity for a further optimisation.
Any optimizations to help Block Erupters? Still not quite stable for me, 4.x that is.
March 10, 2014, 09:35:35 AM
Hello Con,
I might be wrong but i found a possible memleak in
void roll_work(struct work *work)...
More info
if (work->ntime)
work->ntime = offset_ntime(work->ntime, 1);
should be something like
if (work->ntime) {
char *memleak = work->ntime;
work->ntime = offset_ntime(work->ntime, 1);
free(memleak);
}
as long as offset_ntime returns new pointer and old work->ntime pointer is lost and never freed on free_work call
PS: consider it as confirmed and fixed My tplinks are a lot mare happy with the above fix. Everything is working fine and most important memory is not leaking
Good catch, looks valid, thanks!I might be wrong but i found a possible memleak in
void roll_work(struct work *work)...
More info
if (work->ntime)
work->ntime = offset_ntime(work->ntime, 1);
should be something like
if (work->ntime) {
char *memleak = work->ntime;
work->ntime = offset_ntime(work->ntime, 1);
free(memleak);
}
as long as offset_ntime returns new pointer and old work->ntime pointer is lost and never freed on free_work call
PS: consider it as confirmed and fixed
My tplinks are a lot mare happy with the above fix. Everything is working fine and most important memory is not leakingEDIT: Fixed in git, along with an opportunity for a further optimisation.
March 10, 2014, 09:17:53 AM
Hello Con,
I might be wrong but i found a possible memleak in
void roll_work(struct work *work)...
More info
if (work->ntime)
work->ntime = offset_ntime(work->ntime, 1);
should be something like
if (work->ntime) {
char *memleak = work->ntime;
work->ntime = offset_ntime(work->ntime, 1);
free(memleak);
}
as long as offset_ntime returns new pointer and old work->ntime pointer is lost and never freed on free_work call
PS: consider it as confirmed and fixed My tplinks are a lot mare happy with the above fix. Everything is working fine and most important memory is not leaking
Good catch, looks valid, thanks!I might be wrong but i found a possible memleak in
void roll_work(struct work *work)...
More info
if (work->ntime)
work->ntime = offset_ntime(work->ntime, 1);
should be something like
if (work->ntime) {
char *memleak = work->ntime;
work->ntime = offset_ntime(work->ntime, 1);
free(memleak);
}
as long as offset_ntime returns new pointer and old work->ntime pointer is lost and never freed on free_work call
PS: consider it as confirmed and fixed
My tplinks are a lot mare happy with the above fix. Everything is working fine and most important memory is not leakingEDIT: Fixed in git, along with an opportunity for a further optimisation.
March 10, 2014, 08:26:30 AM
Hello Con,
I might be wrong but i found a possible memleak in
void roll_work(struct work *work)...
More info
if (work->ntime)
work->ntime = offset_ntime(work->ntime, 1);
should be something like
if (work->ntime) {
char *memleak = work->ntime;
work->ntime = offset_ntime(work->ntime, 1);
free(memleak);
}
as long as offset_ntime returns new pointer and old work->ntime pointer is lost and never freed on free_work call
PS: consider it as confirmed and fixed My tplinks are a lot mare happy with the above fix. Everything is working fine and most important memory is not leaking
I might be wrong but i found a possible memleak in
void roll_work(struct work *work)...
More info
if (work->ntime)
work->ntime = offset_ntime(work->ntime, 1);
should be something like
if (work->ntime) {
char *memleak = work->ntime;
work->ntime = offset_ntime(work->ntime, 1);
free(memleak);
}
as long as offset_ntime returns new pointer and old work->ntime pointer is lost and never freed on free_work call
PS: consider it as confirmed and fixed
My tplinks are a lot mare happy with the above fix. Everything is working fine and most important memory is not leaking March 09, 2014, 05:50:52 PM
The new CGMiner also support the new Antminer U2?
I mean yes, only the Heatsink is new?
Try it and let us know I mean yes, only the Heatsink is new?
We don't have any U2's but I think they are the same with just a better heat sink?
Ive got a few boxes of these on hand.... pretty nice.
Of the U2s? hows the software support? do they use the same software as the prior versions?Theoretically they're supposed to run identical software to the U1s which cgminer has full support for.
Does anyone know how to overclock them? It seems it works different than the U1, at least I am not able to OC them yet.
If they run the same as the U1 then it would take the same cgminer parameter to overclock it, i.e. adding '--anu-freq 250' would make them run at 2GH
March 09, 2014, 05:48:49 PM
The new CGMiner also support the new Antminer U2?
I mean yes, only the Heatsink is new?
regards
Try it and let us know I mean yes, only the Heatsink is new?
regards
We don't have any U2's but I think they are the same with just a better heat sink?
March 09, 2014, 05:46:13 PM
hi,
how can i update the cgminer version from a antminer s1? Normally the software is deployed with a new firmware.
thanks
Yeah I can build binaries and ipk files now.how can i update the cgminer version from a antminer s1? Normally the software is deployed with a new firmware.
thanks
I'm not 100% sure of building a complete firmware file, that will come a little later.
The luci web code that displays the stats doesn't work with the correct API code, so I'll see if I can sort that out today and hack a binary that works with both the luci code and of course includes the correct API output for anyone who accesses it.
March 09, 2014, 04:38:06 PM
The new CGMiner also support the new Antminer U2?
I mean yes, only the Heatsink is new?
regards
I mean yes, only the Heatsink is new?
regards
Jump to: