Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 249. (Read 5805531 times)
August 18, 2013, 01:58:50 AM
Nope, seems I was entirely wrong. It was a issue with Android not supporting USB Host mode out of the Box and I think I have the wrong OTG cable. I need to get a Y cable. So pretty much my Tablet was trying to run the BE's without taking in the extra power.
August 17, 2013, 10:44:26 PM
I think I figured out what the problem I had with my Tablet setup, I think using the OTG cable adds an extra "hub" to introduce lag into the data pipeline causing errors. That's why it worked when I hooked the BE directly but not with the hub. So even if I DID get Serial-USB working(Android doesn't seem to have that in the stock kernel) I think I'd have the same problems happening. At least I've eliminated the fact it wasn't a LibUSB problem. Now the million dollar question is HOW can I fix this? I'll post specs for the "Linux Root Hub" (The OTG cable) Later. I think messing with that might fix the problem I'm having.
August 17, 2013, 08:21:25 PM
You do know that the up and down arrows work to scroll the top section of the screen when there is more than fits, right?
no i didn't, the top just keeps pushin' the bottom down.
August 17, 2013, 07:39:51 PM
You do know that the up and down arrows work to scroll the top section of the screen when there is more than fits, right?
August 17, 2013, 06:50:19 PM
There probably a simple answer to this, what do you do when the number of erupters you are running pushes the display off the bottom of the screen. So far I've been getting by with a smaller font, but that will only work so long.
resize the window. click on the box in top left, click properties. go to layout and increase the window height. you may need to restart it for it to take effect. (I assume you're talking windows)
M
use --usb and the block erupter code : a number that fits, then make a terminal session alt+F1 to alt+F6 for additional units. Limits the number of erupters per window, keeps all stats and allows them all to work. It can be especially helpful for adding less variance. I don't bother running the hashing units with x running. less resources and all....
August 17, 2013, 03:34:22 PM
Yeah, I use CGWatcher http://manotechnology.blogspot.co.uk/p/cgwatcher.html on windows, there are a few web based ones for Linux too. the are very handy, and restart CGMiner when it gets a bit confused, or graphics/usb driver restarts, etc...
August 17, 2013, 02:21:07 PM
There probably a simple answer to this, what do you do when the number of erupters you are running pushes the display off the bottom of the screen. So far I've been getting by with a smaller font, but that will only work so long.
resize the window. click on the box in top left, click properties. go to layout and increase the window height. you may need to restart it for it to take effect. (I assume you're talking windows)
M
Use --compact mode and stop get per device statistics from the API (some kind of dashboard, etc) instead of by looking at the screen.
August 17, 2013, 01:51:11 PM
I cant put this program work on my Win 8 64bits... its strange!
it shutdown after I put the data of pool, user and pass...
it shutdown after I put the data of pool, user and pass...
August 17, 2013, 01:30:39 PM
There probably a simple answer to this, what do you do when the number of erupters you are running pushes the display off the bottom of the screen. So far I've been getting by with a smaller font, but that will only work so long.
resize the window. click on the box in top left, click properties. go to layout and increase the window height. you may need to restart it for it to take effect. (I assume you're talking windows)
M
August 17, 2013, 01:16:09 PM
There probably a simple answer to this, what do you do when the number of erupters you are running pushes the display off the bottom of the screen. So far I've been getting by with a smaller font, but that will only work so long.
resize the window. click on the box in top left, click properties. go to layout and increase the window height. you may need to restart it for it to take effect. (I assume you're talking windows)
M
August 17, 2013, 01:00:41 PM
There probably a simple answer to this, what do you do when the number of erupters you are running pushes the display off the bottom of the screen. So far I've been getting by with a smaller font, but that will only work so long.
August 16, 2013, 06:48:02 PM
Unofficial Mac binaries updated to 3.3.4 at http://spaceman.ca/cgminer.
This directly relates to the whole libusb monologue I've been having in here over the last month
That specifically means your libusb on your mac is bugged - the timeout option when doing I/O isn't working
The README says how to build with a working libusb and it works on Linux and Windows - no idea about a Mac ...
Tell whoever Karin is to read the README ...
That specifically means your libusb on your mac is bugged - the timeout option when doing I/O isn't working
The README says how to build with a working libusb and it works on Linux and Windows - no idea about a Mac ...
Tell whoever Karin is to read the README ...
Karin, read the README
I keep a very close eye on the readme's (even following their changes on github), and I've tried using rc10 but if I recall it had no effect on this bug on Macs, so I instead include the latest libusb in my builds.
Kano makes it sounds like the error confidently lies within libusb, so I'll do a full spectrum of tests with various libusb versions. If I can find a version that works I will update cgminer for Mac OS X and Asteroid (my Mac GUI to cgminer) accordingly.
Otherwise, we'll have to dig deeper into libusb, and any errors generated from cgminer (and what the community can help with) would be our best bet in figuring out the issue with libusb + Macs. I'll try and do these test builds tonight and will post back with what I find.
As I have already stated, I can run two different libusb versions on the same architecture and one works while the other doesn't.
The test problem that I've mentioned in here a few times is standalone code (bits and pieces of the code I've written in cgminer - but modified) and that shows if timeouts are working ... and if they are matching the expected values also.
https://bitcointalk.org/index.php?topic=28402.msg2817682;topicseen#msg2817682
https://bitcointalk.org/index.php?topic=28402.msg2846296;topicseen#msg2846296
https://bitcointalk.org/index.php?topic=28402.msg2938585;topicseen#msg2938585
That specific version - libusb-1.0.16-rc10 - works on Linux and Windows
I've seen other 1.0.16 versions that don't work ... thus using the 'latest' libusb is not guaranteed to solve it.
Also, libusb has 2 sources: libusb and libusbx, and some OSs provide libusbx instead of libusb
The README also states how to use the libusb mentioned
August 16, 2013, 04:33:42 PM
I'm Karin!
I keep a very close eye on the readme's (even following their changes on github), and I've tried using rc10 but if I recall it had no effect on this bug on Macs, so I instead include the latest libusb in my builds.
Kano makes it sounds like the error confidently lies within libusb, so I'll do a full spectrum of tests with various libusb versions. If I can find a version that works I will update cgminer for Mac OS X and Asteroid (my Mac GUI to cgminer) accordingly.
Otherwise, we'll have to dig deeper into libusb, and any errors generated from cgminer (and what the community can help with) would be our best bet in figuring out the issue with libusb + Macs. I'll try and do these test builds tonight and will post back with what I find.
I appreciate it! Let me know if you figure anything out. I'd be happy to help in any way I can and/or send you a small tip for your time as I'm basically sitting dead in the water until I can get this sorted. I keep a very close eye on the readme's (even following their changes on github), and I've tried using rc10 but if I recall it had no effect on this bug on Macs, so I instead include the latest libusb in my builds.
Kano makes it sounds like the error confidently lies within libusb, so I'll do a full spectrum of tests with various libusb versions. If I can find a version that works I will update cgminer for Mac OS X and Asteroid (my Mac GUI to cgminer) accordingly.
Otherwise, we'll have to dig deeper into libusb, and any errors generated from cgminer (and what the community can help with) would be our best bet in figuring out the issue with libusb + Macs. I'll try and do these test builds tonight and will post back with what I find.
August 16, 2013, 03:03:17 PM
I have an issue with the latest CGMINER...
Instead of showing the number of "Accepted" and "Rejected" A: 2 R:1 HW: 0... it shows the "last diff" of the last accepted block for accepted and rejected, eg, for my scrypt-coins it shows...
A: 70687 R :68799 (Wow, great, 70687 accepted blocks and only 68799 rejects! From submitting two blocks!) lol
Those are the DIFFs of the coins I am mining, 70.7K and 68.8K were the two found.
Why did this change, and how do I get it back to show the NUMBER of accepted so I can see when ACCEPTED vs REJECTED, to gauge the effectiveness of the coins I am mining. Without knowing the number of accepted coins, that stat is useless. Why would we care what the DIFF was, in the stats?
This is not what it should be showing us... something is wrong... as per the readme and sample screen-shots...
I also notice it is throwing-off other stats... hope this throw-off isn't going to change the way the program makes judgement about connections...
Note: This is the windows compiled version 3.3.4, mining bottlecaps at the moment version 1.4.1.
Instead of showing the number of "Accepted" and "Rejected" A: 2 R:1 HW: 0... it shows the "last diff" of the last accepted block for accepted and rejected, eg, for my scrypt-coins it shows...
A: 70687 R :68799 (Wow, great, 70687 accepted blocks and only 68799 rejects! From submitting two blocks!) lol
Those are the DIFFs of the coins I am mining, 70.7K and 68.8K were the two found.
Why did this change, and how do I get it back to show the NUMBER of accepted so I can see when ACCEPTED vs REJECTED, to gauge the effectiveness of the coins I am mining. Without knowing the number of accepted coins, that stat is useless. Why would we care what the DIFF was, in the stats?
This is not what it should be showing us... something is wrong... as per the readme and sample screen-shots...
Quote
Each column is as follows:
5s: A 5 second exponentially decaying average hash rate
avg: An all time average hash rate
Q: The number of requested (Queued) work items from the pools
A: The number of Accepted shares
R: The number of Rejected shares
HW: The number of HardWare errors
E: The Efficiency defined as number of shares returned / work item
U: The Utility defined as the number of shares / minute
5s: A 5 second exponentially decaying average hash rate
avg: An all time average hash rate
Q: The number of requested (Queued) work items from the pools
A: The number of Accepted shares
R: The number of Rejected shares
HW: The number of HardWare errors
E: The Efficiency defined as number of shares returned / work item
U: The Utility defined as the number of shares / minute
I also notice it is throwing-off other stats... hope this throw-off isn't going to change the way the program makes judgement about connections...
Note: This is the windows compiled version 3.3.4, mining bottlecaps at the moment version 1.4.1.
August 16, 2013, 02:06:02 PM
Unofficial Mac binaries updated to 3.3.4 at http://spaceman.ca/cgminer.
This directly relates to the whole libusb monologue I've been having in here over the last month
That specifically means your libusb on your mac is bugged - the timeout option when doing I/O isn't working
The README says how to build with a working libusb and it works on Linux and Windows - no idea about a Mac ...
Tell whoever Karin is to read the README ...
That specifically means your libusb on your mac is bugged - the timeout option when doing I/O isn't working
The README says how to build with a working libusb and it works on Linux and Windows - no idea about a Mac ...
Tell whoever Karin is to read the README ...
Karin, read the README
I keep a very close eye on the readme's (even following their changes on github), and I've tried using rc10 but if I recall it had no effect on this bug on Macs, so I instead include the latest libusb in my builds.
Kano makes it sounds like the error confidently lies within libusb, so I'll do a full spectrum of tests with various libusb versions. If I can find a version that works I will update cgminer for Mac OS X and Asteroid (my Mac GUI to cgminer) accordingly.
Otherwise, we'll have to dig deeper into libusb, and any errors generated from cgminer (and what the community can help with) would be our best bet in figuring out the issue with libusb + Macs. I'll try and do these test builds tonight and will post back with what I find.
August 16, 2013, 12:44:07 PM
I've been away for a while and decided to give 3.3 another shot since kano et al are singing its praises everywhere.
3.3.4 using libusb-1.0.16-rc10 compiled from sourceforge still shuts down half of my 4x AM USB eruptors when running on Debian amd64 with USB disconnects. If there's some sort of logs you would like let me to post, let me know what you would like to see, but compiling a newer libusb absolutely *does not* solve the problem.
Back to 3.1.1 where everything works fine.
3.3.4 using libusb-1.0.16-rc10 compiled from sourceforge still shuts down half of my 4x AM USB eruptors when running on Debian amd64 with USB disconnects. If there's some sort of logs you would like let me to post, let me know what you would like to see, but compiling a newer libusb absolutely *does not* solve the problem.
Back to 3.1.1 where everything works fine.
I seem to be having a similar problem on Win7x64 with WinUSB (via Zadig). I have 10 BEs, and every couple of hours, at least one will stop working with an error like this:
Code:
AMU0: Comms error (werr=-7 amt=0)
I tried using different hubs and tried using no more than 4 BEs in each 7-port HUB, in case it was a power issue, but nothing helps.
I have not tried using 3.1.1 yet, but I guess that is my next step. This is very frustrating.
[Edit: I should add that if CGMiner is restarted, it will not pick up the BE that apparently failed. It will seem to be OK, in that Windows says it is OK, and working, but the LED will stay on steady, and I have to manually unplug and replug it to get it to be seen by CGMINER.]
August 16, 2013, 11:50:32 AM
I've been away for a while and decided to give 3.3 another shot since kano et al are singing its praises everywhere.
3.3.4 using libusb-1.0.16-rc10 compiled from sourceforge still shuts down half of my 4x AM USB eruptors when running on Debian amd64 with USB disconnects. If there's some sort of logs you would like let me to post, let me know what you would like to see, but compiling a newer libusb absolutely *does not* solve the problem.
Back to 3.1.1 where everything works fine.
3.3.4 using libusb-1.0.16-rc10 compiled from sourceforge still shuts down half of my 4x AM USB eruptors when running on Debian amd64 with USB disconnects. If there's some sort of logs you would like let me to post, let me know what you would like to see, but compiling a newer libusb absolutely *does not* solve the problem.
Back to 3.1.1 where everything works fine.
August 16, 2013, 10:39:36 AM
In this case I would assume that I've also have an average hashrate of 100GH at the pool, right?
It sounds like your implying that the pools estimate of your hash rate is correct?? If so it is not!
The pool has no idea what your hash rate is. It's just an estimate.
With most pools you can change the time period which the hash rate is estimated for which will influence how fast and how accurate your estimate will be.
No, I don't imply this. I know about the pool hashrate estimation based on shares during a specified time period.
My questions are regarding the impact of the hw-error counter.
August 16, 2013, 10:33:33 AM
In this case I would assume that I've also have an average hashrate of 100GH at the pool, right?
It sounds like your implying that the pools estimate of your hash rate is correct?? If so it is not!
The pool has no idea what your hash rate is. It's just an estimate.
With most pools you can change the time period which the hash rate is estimated for which will influence how fast and how accurate your estimate will be.
August 16, 2013, 10:23:23 AM
I've a basic question about the impact of hw-errors inside cgminer and on the over-all mining result at a pool.
I'm just doing different firmware optimizations inside the current BFL firmware for my ASIC singles and want to make sure that my understanding of the hw-error counter inside cgminer is really correct.
Let's say I'm getting an average hashrate of 100GH with 0% hw-errors showing up inside cgminer and nothing else is going wrong (retries, network problems etc.). In this case I would assume that I've also have an average hashrate of 100GH at the pool, right?
Now let's say cgminer is showing me 1% hw-errors. My basic understanding of software like cgminer is, that it's checking the mining result of the mining device and if the result is wrong, this result will not be forwarded to the pool and the hw-error counter is going up. Is my assumption correct, that in this case the average hashrate at the pool will be 99GH? Or is there anything else (relevant overhead, etc.) caused by hw-errors which has to be kept in mind when thinking about the over-all mining result at a pool?
I'm just doing different firmware optimizations inside the current BFL firmware for my ASIC singles and want to make sure that my understanding of the hw-error counter inside cgminer is really correct.
Let's say I'm getting an average hashrate of 100GH with 0% hw-errors showing up inside cgminer and nothing else is going wrong (retries, network problems etc.). In this case I would assume that I've also have an average hashrate of 100GH at the pool, right?
Now let's say cgminer is showing me 1% hw-errors. My basic understanding of software like cgminer is, that it's checking the mining result of the mining device and if the result is wrong, this result will not be forwarded to the pool and the hw-error counter is going up. Is my assumption correct, that in this case the average hashrate at the pool will be 99GH? Or is there anything else (relevant overhead, etc.) caused by hw-errors which has to be kept in mind when thinking about the over-all mining result at a pool?
Jump to: