Someone have any idea why cgminer 3.4.2 closes when I enter pool login information? I think my eurupter is detected since its not giving me the your using the wrong driver error with the winUSB drivers but It just closes. I'm not sure if theres an error log to look at since it hasn't started doing anything yet.
PM me if you can give me a heads up.
I'm currently trying it on windows 7 since windows vista wouldn't let me set the shortcut commands.
Thanks
Run it from a command prompt and the window can't close. You'll get far more useful information that way. |
|
|
|
Yeah, I was never a big fan of the blades just because they're so...user-unfriendly. I can understand requiring a bit of work to get something like a BitFury 400 GH/s kit running. But not a 10-13 GH/s unit.
No offence eleuthria but to me it seems like a garage sale of their leftover stuff and you're an unwitting participant to get rid of it for them. |
|
|
|
Interesting, it's not showing up an AMU at all... nothing matches AMU 10c4:ea60
I checked the BE device properties in Device Manager, and I did see those bytes (10c4:ea60) in the various device setting strings. So Windows itself is identifying the device correctly and loading the right driver. If it helps you debug this further, the motherboard I'm using is a Gigabyte GA-Z87X-UD4H. Is there anything further I can do to help resolve this, or do we just have to wait for whoever is in charge of libusb development to add support for this motherboard/chipset/whatever the root cause is? Hmm there are some usb3 ports that are apparently not working with libusb, perhaps you have some. Try different ports or a hub or something to see if that's it? |
|
|
|
all i keep getting is no devices detected. iv tried everything and iv got no where, this is actually starting to drive me insane! any advice would not go a miss right now.
iv tried different forms of .bat files from \\.\COM3 to \COM3 also tried both -s and -S and nothing seems to work, iv only been using bit minter and they work fine there but i would like to start trying other pools now,
my device manager show me all COM Ports that im using the block erupters with, im running windows 7 64bit too if that helps?
cgminer does NOT USE COM PORTS. Please read the included ASIC-README file. |
|
|
|
|
By the way, are you using a socks4 or 5 proxy?
|
|
|
|
I also ran cgminer with this command line, in case it provides any further useful info. Here's the first few lines of the output. cgminer-nogpu --debug --verbose 2>cgminer.debug.output.txt [2013-09-06 17:30:48] Started cgminer 3.4.2
[2013-09-06 17:30:48] Loaded configuration file cgminer.conf
[2013-09-06 17:30:48] USB scan devices: checking for ICA devices
[2013-09-06 17:30:48] RES: thread starting
[2013-09-06 17:30:48] ICA looking for ICA 067b:2303 but found 8086:8c26 instead
[2013-09-06 17:30:48] ICA looking for AMU 10c4:ea60 but found 8086:8c26 instead
[2013-09-06 17:30:48] ICA looking for BLT 0403:6001 but found 8086:8c26 instead
[2013-09-06 17:30:48] ICA looking for LLT 0403:6001 but found 8086:8c26 instead
[2013-09-06 17:30:48] ICA looking for CMR 0403:8350 but found 8086:8c26 instead
[2013-09-06 17:30:48] ICA looking for CMR 0403:6014 but found 8086:8c26 instead
[2013-09-06 17:30:48] ICA looking for ICA 067b:2303 but found 8086:8c2d instead
[2013-09-06 17:30:48] ICA looking for AMU 10c4:ea60 but found 8086:8c2d instead
[2013-09-06 17:30:48] ICA looking for BLT 0403:6001 but found 8086:8c2d instead
[2013-09-06 17:30:48] ICA looking for LLT 0403:6001 but found 8086:8c2d instead
[2013-09-06 17:30:48] ICA looking for CMR 0403:8350 but found 8086:8c2d instead
[2013-09-06 17:30:48] ICA looking for CMR 0403:6014 but found 8086:8c2d instead
[2013-09-06 17:30:48] ICA looking for ICA 067b:2303 but found 8087:8000 instead
[2013-09-06 17:30:48] ICA looking for AMU 10c4:ea60 but found 8087:8000 instead
[2013-09-06 17:30:48] ICA looking for BLT 0403:6001 but found 8087:8000 instead
[2013-09-06 17:30:48] ICA looking for LLT 0403:6001 but found 8087:8000 instead
[2013-09-06 17:30:48] ICA looking for CMR 0403:8350 but found 8087:8000 instead
[2013-09-06 17:30:48] ICA looking for CMR 0403:6014 but found 8087:8000 instead
[2013-09-06 17:30:48] ICA looking for ICA 067b:2303 but found 8087:8008 instead
[2013-09-06 17:30:48] ICA looking for AMU 10c4:ea60 but found 8087:8008 instead
[2013-09-06 17:30:48] ICA looking for BLT 0403:6001 but found 8087:8008 instead
[2013-09-06 17:30:48] ICA looking for LLT 0403:6001 but found 8087:8008 instead
[2013-09-06 17:30:48] ICA looking for CMR 0403:8350 but found 8087:8008 instead
[2013-09-06 17:30:48] ICA looking for CMR 0403:6014 but found 8087:8008 instead
Interesting, it's not showing up an AMU at all... nothing matches AMU 10c4:ea60 |
|
|
|
|
History will repeat itself once more. Sure a lot of people will not invest with them again, but a hell of a lot will prepay for fear of missing out.
|
|
|
|
|
I've just created native stratum proxy support for http1.0/1.1 and socks5 proxies for cgminer and it is now in the git master branch so it will be in the next cgminer release.
|
|
|
|
Interesting.. Kano they even thanked your for the help you did not know you gave them....
LMFAO....
LOL Ooh they thanked me too! I feel all warm and fuzzy.
@ckolivas, @kano may I say that thery're thanking for the creation of CGminer ? quoting the relevant part: Secondly with regards to CGminer, and it’s opensource protocol we’ve been able to configure our device unassisted and made a greater than 30% performance increase using the underlying code, for which we would like to thank both kano and ckolivas with their outstanding contribution to the community.
sure I would had wanted a more "close" collaboration between KnC and @kano, @ckolivas. Another possible scenario is that they didn't changed the CGminer's code but only apply tweaks to PCB/IC/whatever... but I'm not an expert so I don't know if it'd be possible. When last we spoke, they were talking about writing their own driver for cgminer, so I assume it's just that and not a separate mining application. That is not necessarily good news by the way... |
|
|
|
Got a crash report under Windows while running the 3.4.2 debug build.
---
cgminer.exe caused a Stack Overflow at location 74946ae6 in module mswsock.dll.
Registers:
eax=00add5b8 ebx=03ff3098 ecx=ff676980 edx=ffffffff esi=03ff30a8 edi=00000000
eip=74946ae6 esp=03ff3000 ebp=03ff30f8 iopl=0 nv up ei pl zr na po nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246
Call stack:
74946AE6 mswsock.dll:74946AE6
75ED6A28 WS2_32.dll:75ED6A28 select
00424FDF cgminer.exe:00424FDF
004251A8 cgminer.exe:004251A8
00413ED1 cgminer.exe:00413ED1
004B1BAB cgminer.exe:004B1BAB
76BD1287 msvcrt.dll:76BD1287 _itow_s
76BD1328 msvcrt.dll:76BD1328 _endthreadex
750833AA kernel32.dll:750833AA BaseThreadInitThunk
77259F72 ntdll.dll:77259F72 RtlInitializeExceptionChain
77259F45 ntdll.dll:77259F45 RtlInitializeExceptionChain
Thanks very much for doing that. Unfortunately you're not going to like the answer. The crash is in the microsoft DLL provided and not in any of the cgminer code or any DLLs I distribute. It should not be possible for my software to make an operating system provided library crash unless there's a bug in the library. Googling around I can see a few exploits in the past for that particular DLL (so I assume some security update fixed it) and some trojans that have replaced or attached themselves to that DLL. Ironically a stack overflow is precisely the exploit described so the best I can guess is that there is an updated DLL in some software update somewhere. |
|
|
|
Any plans to add ASICminer blade support? Brickminer did but only linux at the moment...
i'd love to have that feature for my blade. i wont need the stratum proxy running then. cgminer is running on my pi with 5 usb block errupters and a ztex quad and ztex single anyway. and i dont have to touch brickminer. I had no idea there was demand for such a feature. I don't code features because other software has it but for my own interest in the code/feature, overwhelming user demand and sponsorship. Given I have no hardware that would use it, and the getwork protocol is not used by anything else and will not be in use by any new hardware, I don't really see a compelling reason to code up what is not a trivial feature to add, I'm afraid. |
|
|
|
Another question answered already. By KnC themselves. Posted on this thread too. Can you read? Or do you just pop by every now and then to stir up some pointless crap? Oh - did they? Got a link to the post? I missed it. I'm curious as to what their reply was - they never replied by email. Interesting.. Kano they even thanked your for the help you did not know you gave them.... LMFAO.... LOL Ooh they thanked me too! I feel all warm and fuzzy. |
|
|
|
Well, I *can* make more firmware, but I will be making it blind, and since the new usb library needs udev, I will have modified the avalon build to include udev in it. I have no idea if that even works just like that or needs some other modifications to work. So while I can build the firmware, I can't test if it works, and likely, given the change to the underlying OS, it will brick the avalon. If someone is capable of unbricking their avalon and is willing to try it, I'll post said firmware (the former requirement is more important than the latter desire). However... there is nothing particularly new in the latest cgminer for Avalon except for the inclusion of a new libusb built statically into the binary which may make it less likely to have USB failures, but since the last firmware I posted was so solid, I don't see the need for upgrading. It's just a WR703N with a few mods. I'll try and get one of mine modded to send him if he'll take it. I'll need a shipping address if someone wants to PM me one.
I most definitely appreciate his contributions. I received some more avalons yesterday that came with 0723. After I put 0821 on them they're all mining substantially faster.
I really hope to see a firmware some day that can clock each 10-chip board individually. I don't know what it would take to accomplish that...I guess reprogramming the FPGA controller.
For now I plan to play games swapping modules around to try and make some strong machines (clocked higher) and some weaker ones.
Thanks for the offer Bogart, but I'm not expecting to pull any more rabbits out of my hat for Avalon hardware. I still wouldn't mind a fixed device (broke the damn thing trying to hold down reset button) so I can at least keep the avalon firmware in line with latest cgminer. |
|
|
|
who is talking about bitcoin mining???
first two words in OP: ''Scrypt-coiners!''
Yeah so he's posting it in the wrong place, which is what I was saying. |
|
|
|
|
I think you're in the wrong place. GPUs have no place in bitcoin mining any more. Try posting this in the altcoin forum section.
|
|
|
|
I'm having trouble getting 3.4.2 working with my ASICMiner USB Block Erupter. I'm still using 3.1.1. 8( I've looked at the usbfail post https://bitcointalk.org/index.php?topic=28402.msg2817682#msg2817682I've built a local version of libusb-1.0.16-rc10 But, when I try to run cgminer's configure to use it it looks like it is still using the cgminer*/compat/libusb* version. FYI - I only use this machine for mining so I would be happy to change libusb to whatever version works for cgminer if that's easier than pointing the cgminer make to my local libusb... Thanks. I wanted to make it easier for everyone so I modified the entire build tree to use the optimal libusb automatically, that's why it's now included in the cgminer release tarballs/git tree (it is 1.0.16-rc10) and is built into the cgminer binary statically. No need to do anything with libusb from the user side. |
|
|
|
For now I can't see there being cgminer support.
I even tried to buy one and was told no.
Over irc I've seen the cgminer development gradually progressing over the past few days, I suppose punin (and others?) are "going at it" allready. A fork, not cgminer. Kano, it is not like you have a trademark on cgminer name. Call it a fork, a variant or whatever. It is still a cgminer. You can incorporate it into cgminer that Con is maintaining or not. It is ultimately Con's call. There's no argument here. What he means is that there was a fork made from a slightly earlier version of cgminer from which the driver was developed. There is nothing wrong with that. However the code only works on an RPi, and I have since been asked to merge the code into mainline cgminer. The code itself is unusable generically in cgminer which is designed to work on other architectures and operating systems so I cannot include the code as it currently is - especially since it works in a way that is a profound security issue. It also happens that the hardware design of devices made with bitfury chips to date depend on that unique relationship with RPi devices so I've been unable to rewrite the driver to make the usb sticks and other bitfury based hardware work anywhere else. I've not found a decent solution to this issue, but I'm still investigating and watching. |
|
|
|
Hi guys,
Bit of an issue, not serious. Cgminer is showing 30% cpu usage since upgrading to latest - seems very high eh? I done the usual compile with make clean, had no errors at all that I could see, it just seems to be a bit too heavy on resources - any suggestions? Xubuntu 12.04 64bit.
That does sound wrong. Did you set CFLAGS to enable optimisations? I see 1% CPU usage on a modern CPU with 217GH across 4 devices on a similar linux. |
|
|
|
I dont understand how this pool has such a big piece of the network with a 3% fee??
It must be worth it somehow?
Deepbit predates many other modern pools. Historically during a major boom in bitcoin price when a lot of other pools struggled with the sudden demand for more miners combined with loads of DDoS attacks on the pools, this pool was just about the only pool able to withstand the greater demand and showed a level of stability that was unparalleled so it attracted a great proportion of miners despite the higher fees. However, that's history now and the bitcoin mining landscape is completely utterly unrecognisable from those days... but this pool remains virtually unchanged from what it was in those days in fees and features. |
|
|
|
|
Show Posts
