Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 241. (Read 5806004 times)
August 25, 2013, 04:42:59 PM
Kano, quick question. Does cgminer control when avalon fan speed argument kicks in? On my bitburners, 100% fan setting doesn't kick in for about 3-5 min so temp is rising very quickly to 55-60c then fans go to 100% and its cooling down to about 48C and stays like that. Do you think its something in the firmware that can be improved or cgminer? Shouldn't fan speed go to 100% if set by arg straight from the start of cgminer?
August 25, 2013, 04:38:47 PM
...
I installed the Windows binary distribution of CGMiner - 3.3.1, I believe, was the current release at that time. I read the README, and downloaded the Zadig binary linked on page 1, and installed the WinUSB driver for my block erupters, and for my BFL devices. I then (just to be careful) rebooted the PC. All devices appeared to be using the correct WinUSB drivers, so I then started CGMiner. The devices were all recognized, and seemed to function as expected. Over the next few days, however, I found that at least one Block Erupter would stop working after, on average, ~2-3 hours. CGMiner would be constantly printing a communications error with the failed device, and the device itself would have an LED that was fully on constantly. Manually unplugging and re-plugging the device would fix the problem, and CGMiner would autodetect the newly-reinserted device.
So what did I do wrong? I did not try CGMiner under Linux, but whether or not that works would not change the fact that there was a problem with the Win 7 configuration, and that is the problem I reported.
I installed the Windows binary distribution of CGMiner - 3.3.1, I believe, was the current release at that time. I read the README, and downloaded the Zadig binary linked on page 1, and installed the WinUSB driver for my block erupters, and for my BFL devices. I then (just to be careful) rebooted the PC. All devices appeared to be using the correct WinUSB drivers, so I then started CGMiner. The devices were all recognized, and seemed to function as expected. Over the next few days, however, I found that at least one Block Erupter would stop working after, on average, ~2-3 hours. CGMiner would be constantly printing a communications error with the failed device, and the device itself would have an LED that was fully on constantly. Manually unplugging and re-plugging the device would fix the problem, and CGMiner would autodetect the newly-reinserted device.
So what did I do wrong? I did not try CGMiner under Linux, but whether or not that works would not change the fact that there was a problem with the Win 7 configuration, and that is the problem I reported.
Can someone just go delete every post related to this moron in this thread ...
I answered it with my very first post.
https://bitcointalksearch.org/topic/m.2960179
Quote from: xyzzy099 on August 18, 2013, 10:23:09 PM
...
So which is it?Wrong version? Wrong libusb.dll? You built it yourself and didn't follow the libusb instructions?
... and cgminer will be rock solid on linux also if you do it as per instructions.
You were running an old version of cgminer for fucked if I know what reason.
So indeed you are a complete fucking waste of time here
3.3.2 came out on the 9th of August that used a replacement fixed libusb ...
Actually I was mistaken when I said 3.3.1 was current at that time. I just checked and verified that I had 3.3.2 installed on the Windows machine, if you really even care about this issue. Actually, it looks like the last version I installed - which would be the one I was using when I initially posted - was 3.3.4.
August 25, 2013, 04:25:09 PM
...
I installed the Windows binary distribution of CGMiner - 3.3.1, I believe, was the current release at that time. I read the README, and downloaded the Zadig binary linked on page 1, and installed the WinUSB driver for my block erupters, and for my BFL devices. I then (just to be careful) rebooted the PC. All devices appeared to be using the correct WinUSB drivers, so I then started CGMiner. The devices were all recognized, and seemed to function as expected. Over the next few days, however, I found that at least one Block Erupter would stop working after, on average, ~2-3 hours. CGMiner would be constantly printing a communications error with the failed device, and the device itself would have an LED that was fully on constantly. Manually unplugging and re-plugging the device would fix the problem, and CGMiner would autodetect the newly-reinserted device.
So what did I do wrong? I did not try CGMiner under Linux, but whether or not that works would not change the fact that there was a problem with the Win 7 configuration, and that is the problem I reported.
I installed the Windows binary distribution of CGMiner - 3.3.1, I believe, was the current release at that time. I read the README, and downloaded the Zadig binary linked on page 1, and installed the WinUSB driver for my block erupters, and for my BFL devices. I then (just to be careful) rebooted the PC. All devices appeared to be using the correct WinUSB drivers, so I then started CGMiner. The devices were all recognized, and seemed to function as expected. Over the next few days, however, I found that at least one Block Erupter would stop working after, on average, ~2-3 hours. CGMiner would be constantly printing a communications error with the failed device, and the device itself would have an LED that was fully on constantly. Manually unplugging and re-plugging the device would fix the problem, and CGMiner would autodetect the newly-reinserted device.
So what did I do wrong? I did not try CGMiner under Linux, but whether or not that works would not change the fact that there was a problem with the Win 7 configuration, and that is the problem I reported.
Can someone just go delete every post related to this moron in this thread ...
I answered it with my very first post.
https://bitcointalksearch.org/topic/m.2960179
Quote from: xyzzy099 on August 18, 2013, 10:23:09 PM
...
So which is it?Wrong version? Wrong libusb.dll? You built it yourself and didn't follow the libusb instructions?
... and cgminer will be rock solid on linux also if you do it as per instructions.
You were running an old version of cgminer for fucked if I know what reason.
So indeed you are a complete fucking waste of time here
3.3.2 came out on the 9th of August that used a replacement fixed libusb ...
August 25, 2013, 03:46:06 PM
The only other the "I" could suggest is to try the latest CGMiner.
But I understand that you have a working rig now. So you may not want to fix what is no longer broken for you.
I have not seen this behavior with 3.3.1, .2, .3, .4 and I just updated to 3.4.0 yesterday and have not seen this behavior.
My setup is very similar to what you described, Win7 32 bit, 64 bit since yesterday, 15 BE's on 5/7 Port Rosewill hubs and one Jalapeno.
When changing versions I would recommend rebooting the machine to make sure the new .dll is loaded vs. the old one. But I doubt the usb .dll's would effect this since your on USB 2.0 hubs.
Sam
You're right, I don't want to interrupt a working set-up. I could troubleshoot the issue all the way to the hardware level, if I needed to - I have a nice LeCroy O-Scope with a USB analyzer module at work. Maybe I would have been willing to go that route just to help out the CGMiner project, if I had not been greeted with such animosity by Kano.
Well, we didn't manage to figure out what the problem was, but at least we managed to have a civilized conversation about the issue. Thanks for your help.
August 25, 2013, 03:31:14 PM
The hubs are DLink DUB-H7 7-port hubs, with 5 sticks in each hub with 3A power supplies. It's my understanding that each BE should use 0.5A, so this should provide sufficient overhead for 5 sticks. These hubs are well-known to work well with BEs in groups of 5.
Most importantly though, they work flawlessly when attached to a Linux box running different S/W, so I think blaming the hardware is probably a dead-end.
Most importantly though, they work flawlessly when attached to a Linux box running different S/W, so I think blaming the hardware is probably a dead-end.
Yep, I agree.
Is it always the same Erupter/USB port.
I'm not trying to "blame" your hardware just trying to cover all the bases, in the unlikely event you haven't.
How many instances of CGMiner were you running? Were you trying to use any command line options?
No it was not always the same erupter or port or hub. It seemed to be completely random. Even the erupters plugged into the 1.2A fast-charge ports had the issue randomly, with the same frequency as the sticks in the normal ports.
I was only using one instance of CGMiner, and the only options on the command line were '-G' to avoid using the GPU, and -c to load the correct config file.
The only other the "I" could suggest is to try the latest CGMiner.
But I understand that you have a working rig now. So you may not want to fix what is no longer broken for you.
I have not seen this behavior with 3.3.1, .2, .3, .4 and I just updated to 3.4.0 yesterday and have not seen this behavior.
My setup is very similar to what you described, Win7 32 bit, 64 bit since yesterday, 15 BE's on 5/7 Port Rosewill hubs and one Jalapeno.
When changing versions I would recommend rebooting the machine to make sure the new .dll is loaded vs. the old one. But I doubt the usb .dll's would effect this since your on USB 2.0 hubs.
Sam
August 25, 2013, 02:12:43 PM
The hubs are DLink DUB-H7 7-port hubs, with 5 sticks in each hub with 3A power supplies. It's my understanding that each BE should use 0.5A, so this should provide sufficient overhead for 5 sticks. These hubs are well-known to work well with BEs in groups of 5.
Most importantly though, they work flawlessly when attached to a Linux box running different S/W, so I think blaming the hardware is probably a dead-end.
Most importantly though, they work flawlessly when attached to a Linux box running different S/W, so I think blaming the hardware is probably a dead-end.
Yep, I agree.
Is it always the same Erupter/USB port.
I'm not trying to "blame" your hardware just trying to cover all the bases, in the unlikely event you haven't.
How many instances of CGMiner were you running? Were you trying to use any command line options?
No it was not always the same erupter or port or hub. It seemed to be completely random. Even the erupters plugged into the 1.2A fast-charge ports had the issue randomly, with the same frequency as the sticks in the normal ports.
I was only using one instance of CGMiner, and the only options on the command line were '-G' to avoid using the GPU, and -c to load the correct config file.
August 25, 2013, 02:08:05 PM
The hubs are DLink DUB-H7 7-port hubs, with 5 sticks in each hub with 3A power supplies. It's my understanding that each BE should use 0.5A, so this should provide sufficient overhead for 5 sticks. These hubs are well-known to work well with BEs in groups of 5.
Most importantly though, they work flawlessly when attached to a Linux box running different S/W, so I think blaming the hardware is probably a dead-end.
Most importantly though, they work flawlessly when attached to a Linux box running different S/W, so I think blaming the hardware is probably a dead-end.
Yep, I agree.
Is it always the same Erupter/USB port.
I'm not trying to "blame" your hardware just trying to cover all the bases, in the unlikely event you haven't.
How many instances of CGMiner were you running? Were you trying to use any command line options?
August 25, 2013, 01:39:02 PM
I have a bit of a problem.
I have 2 gpu's and 4 usb asci's
I run -o stratum.d7.lt:3333 -u xxxx -p xxxx -d 0 -d 1 -d 2 -d 3 -d 4 -d 5 --api-listen --api-port 4028 --api-allow W:127.0.0.1 -T and cgminer probes for an alive pool than crashes.
I have also tried -o stratum.d7.lt:3333 -u xxxx -p xxxx -w 256 -g 1 --thread-concurrency 6144,24000 -I 14,20 -d 0 -d 1 -d 2 -d 3 --api-listen --api-port 4029 --api-allow W:127.0.0.1 -T
to try and set up the gpu's but the same thing happens
Any ideas?
I have 2 gpu's and 4 usb asci's
I run -o stratum.d7.lt:3333 -u xxxx -p xxxx -d 0 -d 1 -d 2 -d 3 -d 4 -d 5 --api-listen --api-port 4028 --api-allow W:127.0.0.1 -T and cgminer probes for an alive pool than crashes.
I have also tried -o stratum.d7.lt:3333 -u xxxx -p xxxx -w 256 -g 1 --thread-concurrency 6144,24000 -I 14,20 -d 0 -d 1 -d 2 -d 3 --api-listen --api-port 4029 --api-allow W:127.0.0.1 -T
to try and set up the gpu's but the same thing happens
Any ideas?
August 25, 2013, 12:39:40 PM
I installed the Windows binary distribution of CGMiner - 3.3.1, I believe, was the current release at that time. I read the README, and downloaded the Zadig binary linked on page 1, and installed the WinUSB driver for my block erupters, and for my BFL devices. I then (just to be careful) rebooted the PC. All devices appeared to be using the correct WinUSB drivers, so I then started CGMiner. The devices were all recognized, and seemed to function as expected. Over the next few days, however, I found that at least one Block Erupter would stop working after, on average, ~2-3 hours. CGMiner would be constantly printing a communications error with the failed device, and the device itself would have an LED that was fully on constantly. Manually unplugging and re-plugging the device would fix the problem, and CGMiner would autodetect the newly-reinserted device.
That sounds like a hub not supplying enough power. What hub(s) are you using and what is the current and voltage rating of the Power Supplies.
Sam
The hubs are DLink DUB-H7 7-port hubs, with 5 sticks in each hub with 3A power supplies. It's my understanding that each BE should use 0.5A, so this should provide sufficient overhead for 5 sticks. These hubs are well-known to work well with BEs in groups of 5.
Most importantly though, they work flawlessly when attached to a Linux box running different S/W, so I think blaming the hardware is probably a dead-end.
August 25, 2013, 12:21:43 PM
I installed the Windows binary distribution of CGMiner - 3.3.1, I believe, was the current release at that time. I read the README, and downloaded the Zadig binary linked on page 1, and installed the WinUSB driver for my block erupters, and for my BFL devices. I then (just to be careful) rebooted the PC. All devices appeared to be using the correct WinUSB drivers, so I then started CGMiner. The devices were all recognized, and seemed to function as expected. Over the next few days, however, I found that at least one Block Erupter would stop working after, on average, ~2-3 hours. CGMiner would be constantly printing a communications error with the failed device, and the device itself would have an LED that was fully on constantly. Manually unplugging and re-plugging the device would fix the problem, and CGMiner would autodetect the newly-reinserted device.
That sounds like a hub not supplying enough power. What hub(s) are you using and what is the current and voltage rating of the Power Supplies.
Sam
August 25, 2013, 12:15:48 PM
When you have a notable antagonist like Kano involved with this project, it's hard to avoid shit talking 
It's actually very easy to avoid.I agree in theory. Unfortunately, I have an obsessive compulsion to call people on their bullshit
We all have our quirks.
August 25, 2013, 11:31:02 AM
Wrong. I am not a CGMiner developer. I have no responsibility or interest in personally debugging CGMiner.
Both developers and users are part of the Open Source Software community, users have responsibility to report problems and help ascertain what the cause is, when possible.
but he chose to just blindly attack me instead.
He didn't "blindly" attack you, You, gave first offense, now your refusing to take responsibility for it. You want Kano to take responsibility for his offensive post, but why should he when YOU refuse?
You failed to quote my whole post - as I said, I was willing to help debug the problem, but was not afforded that opportunity.
Exactly HOW did I "give first offense"
I did NOTHING but point out a problem I had. I said NOTHING to offend anyone. I did not know that Kano had some kind of bizarre hatred of [THE MINER THAT DARE NOT SAY ITS NAME IN THIS THREAD]. Clearly Kano read offense into a post that contained NONE.Since you seem to possess the OSS community spirit, maybe you and I could talk about the problem in more detail, so we can identify the part where I did something stupid that resulted in my problem?
I installed the Windows binary distribution of CGMiner - 3.3.1, I believe, was the current release at that time. I read the README, and downloaded the Zadig binary linked on page 1, and installed the WinUSB driver for my block erupters, and for my BFL devices. I then (just to be careful) rebooted the PC. All devices appeared to be using the correct WinUSB drivers, so I then started CGMiner. The devices were all recognized, and seemed to function as expected. Over the next few days, however, I found that at least one Block Erupter would stop working after, on average, ~2-3 hours. CGMiner would be constantly printing a communications error with the failed device, and the device itself would have an LED that was fully on constantly. Manually unplugging and re-plugging the device would fix the problem, and CGMiner would autodetect the newly-reinserted device.
So what did I do wrong? I did not try CGMiner under Linux, but whether or not that works would not change the fact that there was a problem with the Win 7 configuration, and that is the problem I reported.
August 25, 2013, 11:21:31 AM
Outside of the documentation, are there any concise examples of the overclocking commands in action, that I could study before my rigs get here?
Going through this entire thread is not possible!
(I am running MinePeon with CG Miner on a Raspberry Pi. I'll be overclocking a Burnin Mining rig and then a Bitfury chip custom rig).
Thanks,
IAS
No bitfury drivers yet.Going through this entire thread is not possible!
(I am running MinePeon with CG Miner on a Raspberry Pi. I'll be overclocking a Burnin Mining rig and then a Bitfury chip custom rig).
Thanks,
IAS
Burnin's BitBurner is simply a case of adjusting the freq and the volts - the higher the volts the bigger the risk of hardware failure.
The higher the frequency, the larger the volts required to reduce HW errors.
Update of what I posted in the Burnin thread
BTB 0: 56C 400 1346mV | 7.192G/7.991Gh/s | A:243645 R:2216 HW:12 WU:111.6/m
[Device Hardware%] => 0.0049 (yes that's a %)
It's documented in the README, ASIC-README and API-README ...
To set the start voltage:
--bitburner-voltage nnnn
nnnn - from 1200 to 1400
Warning it can kill your power supply or even your board ... be careful adjusting it too high
To set the start frequency (for one board with 20 chips)
--avalon-options 115200:2:10:d:nnn
nnn from 282 up to 450
When it's running you can change them also via the API, but it doesn't really help to work out the performance coz you need to run it for a few hours to get marginally reliable statistics - the Avalon driver doesn't count hashes, it estimates them.
Thanks a lot Kano. I know how some newb questions can be a pain.
I'll watch the voltage closely and wasn't aware of it being able to do so much harm. Had no idea it could hurt a PS.
Hopefully Burnin Mining and SebastianJu find some good settings to settle on and post them.
Barntech will help, I think, with the drivers. At least he is talking about overclocking the rigs he is producing with Bitfury's. Said he got it from 2Ghash/s to 2.7Ghash/s. That is a lot. Burnin Minding talked about getting them to 5Ghash/s and I asked him how as it made no sense, but he never replied. Hmmmmm....
Have you heard of anyone using the --avalon-auto option? I see quite a few other interesting options there.
Thanks,
IAS
August 25, 2013, 11:08:44 AM
Wrong. I am not a CGMiner developer. I have no responsibility or interest in personally debugging CGMiner.
Both developers and users are part of the Open Source Software community, users have responsibility to report problems and help ascertain what the cause is, when possible.
but he chose to just blindly attack me instead.
He didn't "blindly" attack you, You, gave first offense, now your refusing to take responsibility for it. You want Kano to take responsibility for his offensive post, but why should he when YOU refuse?
August 25, 2013, 11:01:36 AM
That was just for your enjoyment
August 25, 2013, 11:00:03 AM
August 25, 2013, 10:59:35 AM
Heh, well at least you pretended that you knew what you were talking about
1) A different serial-USB driver for EACH USB chip ... we only use one
2) Oops - you can't send a control transfer with serial-USB damn shame about that hey
(I'm sure that one will be well above your understanding)
3) Though I guess you didn't notice the drivers in your God's miner that do use direct USB ... damn!
1) A different serial-USB driver for EACH USB chip ... we only use one
2) Oops - you can't send a control transfer with serial-USB damn shame about that hey
(I'm sure that one will be well above your understanding)
3) Though I guess you didn't notice the drivers in your God's miner that do use direct USB ... damn!
What about the crashing on first run with GPU mining on Windows? You've still not acknowledged this.
On several machines, several installs (Win7x64 Pro/Enterprise or Win8x64), I can only get cgminer to work with the ancient 12.8 drivers - and even then it's only 75% success rate. Yet 'the other miner' works with 13.4 and newer no problems. It doesn't make sense.
Edit: Spelling typo
August 25, 2013, 10:58:45 AM
Yeah, well one mining program uses stupid USB drivers which need so many hoops to be jumped through to get working, if they do at all, for no apparent benefit.
I for one really like the "stupid USB drivers".
CGMiner 3.2.1 was the easiest install of new hardware I ever had. I switched from GPU's to BE's and Jalapeno with NO ISSUES on Windbloze 7.
Then when 3.3.1 was released I was able to run multiple instances of CGMiner with equal numbers of BE's to multiple pools with ease and reliability. You just cannot do that with serial USB drivers, when you reboot the system the ports can and probably will come up with a different port mapping and then I would need to redo my .bat files again to do what I want until the next round of Windoze updates.
Implementing new and improved ways of doing things always causes problem, but when they are resolved then you have a better application.
I guess we should all get ticked off at Al Gore for inventing the internet too, right? Nobody should need more than a 1200bps modem and a BBS right?
Sam
August 25, 2013, 10:51:40 AM
In all fairness, I think even you would have to agree that this trainwreck was created by Kano.
No! You need to take responsibility for your own actions.
You started this "trainwreck" with no intentions of finding out what the problem was you were having with the program.
This is a community where we all work together to identify and resolve problems. You had no intention of doing that. You just lobbed a hand grenade and got offended by a remark in response you YOUR offensive remark.
Grow Up!
Wrong. I am not a CGMiner developer. I have no responsibility or interest in personally debugging CGMiner. Especially now, since I no longer even use it.
That being said, I thought the developers might want to be aware of the issue, that's why I posted it. I would have been perfectly happy to provide more details to help Kano debug the issue, if he had requested that - but he chose to just blindly attack me instead.
August 25, 2013, 10:45:00 AM
When you have a notable antagonist like Kano involved with this project, it's hard to avoid shit talking
It's actually very easy to avoid.
Jump to: