You sent me coupons August 27, can i still use them?
I don't think there is an expiration date on them. After one week they go to the next person in line. So you do loose the ability to use them after that time. P.S. if I don't hear from you in a week, your coupons are forfeited and will be made available for group #5 buyers and so on.
|
|
|
|
FWIW, I've not been able to run a version of CGMiner higher than 3.3.1 for longer than 48 hours driving Erupter USB's on Windows 7 64 bit or Windows 8 64 bit. 3.4.0 just died on me across two rigs. Any version that uses the new USB drivers eventually crashes on me with mwsock.dll causing the error under Windows  Have there been other reports of this perchance ? Yeah, same here.. same setup (Win7 64bit).. never really checked the crash/dump though to confirm that dll. I got this, this morning as well. Win7 64 bit. In my case I was running 4 instances and the three Stratum crashed and the one Getwork was still working. Don't know if that means anything? |
|
|
|
remainder of group #11, #10, #9, #8, #7 and #6 are able/eligible to redeem their coupons based on the inventory shipped to me this time.
Did I miss a PM or did you not contact GB#8 yet ? The last update from Canary said Group 9 had been PM'd. |
|
|
|
So with the new block erupter's out by asicminer do you have any more information on them? Do you plan to sell them and if so how much? Freidcat mentioned something about ROI but that would imply a very low price point.
Friedcat clearly doesn't understand the term ROI ... His or ours? |
|
|
|
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.
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 |
|
|
|
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.
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? |
|
|
|
|
With just one Block Erupter USB it really doesn't matter. Just start your mining program, put a fan on the BE, minimize the program and forget about it.
I would probably solo mine with one device and check it once a year just for giggles.
Have Fun,
Sam
|
|
|
|
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 |
|
|
|
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? |
|
|
|
Windbloze 7.
Grow up.  That was just for your enjoyment  |
|
|
|
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 |
|
|
|
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. |
|
|
|
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. |
|
|
|
First I'll apologize if I posted in the wrong area.
I didn't mean to imply, in this case, that you posted in the wrong area. This is Mining Support after all. But CG Miner has a support thread, so it may be more productive to post there. Especially if it's bug related. I just recently found CG Watcher too and it looks neat and nifty. Haven't tried it yet though. Glad your mining OK now. Sam |
|
|
|
Hubs 2-5 each contain six block erupters. Each is plugged into hub #1.
What is the current rating of your hub power supplies? You need more than 3 Amps as each Erupter draws .5 Amp. |
|
|
|
Now people can get off your nuts! Sheesh.. this coupon shit has been a disaster from the beginning
Disaster or not, I'm glad they're doing it. Waiting patiently Sam |
|
|
|
Stuck it in the fridge for about 30 minutes and it doesn't seem to have helped. If anything, it looks like it's gotten worse; down to ~5.4 GH/s now. That doesnt sound like a particularly good idea. Have you tried removing the casing and inverting the fan so its blowing down? I did that a couple days ago and my temp went from 45C to 35C. |
|
|
|
|
I have seen that on my system with CGMiner 3.3.3.
I chalked it up to instability caused by unplugging 15 Block Erupters, a few at a time, to attach heat sinks and then plugging them back in while 4 instances of CGMiner were running. Also did the same thing with my Jalapeno to remove the case and flip the fan.
I haven't seen this while not messing around like that though, yet.
Sam
P.S. post in the CGMiner thread.
|
|
|
|
but I also didn't factor in that I gave out over 8,000 coupons.
This just hit me. You mean to say you have sold over 8,000 Block Erupters?!? |
|
|
|
|
Show Posts
