I dropped in the Windoze binary and the Jalapeno works, but now the Block Erupters don't. You want a new log.txt? |
|
|
|
Here they are, my two SHA-256 miners, I have tried to update to the cgminer-4.9.0, but it was impossible.
With cgminer-4.9.0 I only get that works the AMU unit.
While you can see a very funny screenshot of them running happyly into cgminer-4.8.0
Thank you very much.
I just tried CGMiner with my Jalapeno and found that it doesn't work as well. CGMiner says no devices found but cgminer -n shows the Jalapeno as being there. It has been working fine with 4.7.1 which is what I had been using. I don't have any bfl hardware any more. Can someone who has one start it with the extra options "-D -T 2>log.txt" and after it's failed at startup stop it and post the output of log.txt here (preferably within code tags). The file exceeds the 64,000 character limit of the message so here's a link to it https://dl.dropboxusercontent.com/u/65145036/log.txt |
|
|
|
Here they are, my two SHA-256 miners, I have tried to update to the cgminer-4.9.0, but it was impossible.
With cgminer-4.9.0 I only get that works the AMU unit.
While you can see a very funny screenshot of them running happyly into cgminer-4.8.0
Thank you very much.
I just tried CGMiner with my Jalapeno and found that it doesn't work as well. CGMiner says no devices found but cgminer -n shows the Jalapeno as being there. It has been working fine with 4.7.1 which is what I had been using. |
|
|
|
Having in issue with 4.9.0 on the r-pi. I have 10 Antminer devices (ANU). During initialization, a few of them will initialize as U3 devices (AU3) and repeatedly fail until I disable the USB port and re-enable. After the hot plug logic correctly detects that they are ANU devices and they run perfectly. Is there a way to tell cgminer to use only a single device type (ANU) or identify which device type is plugged into which port and defeat the automatic detection logic?
Try excluding the AU3. I had a similar problem with my BAJ being detected as a BXM until I excluded it in an earlier version of CGMiner. Sorry, but how do I exclude the AU3? Is that a run-time command line parameter or a configuration parameter prior to the build? It's a command line parameter. It's in the ASIC Readme, or should be at least. To disable detection of the false BXM I had to add "--usb BF1:0". I don't know what the driver instance name for your false AU3 is. The documentation would seem to indicate I can only exclude all Icarus driver devices, not specific types. I tried "--usb AU3:0" and it gave me a message to the effect that there was not driver named AU3. You can enable/disable any device CGMiner recognizes. I have no idea which one is an AU3 or an ANU since I don't have those miners. But if both of these devices are icarus AKA ICA then I got nuthin. Here's a list of driver instances from the readme, so it should be one of these. _________________________________ The second version --usb BAS:1,BFL:1,MMQ:0,ICA:0,KLN:0 allows you to specify how many devices to choose based on each device driver cgminer has - the current USB drivers are: AVA, BAS, BFL, BF1, DRB, HFA, ICA, KLN and MMQ. _________________________________ |
|
|
|
Having in issue with 4.9.0 on the r-pi. I have 10 Antminer devices (ANU). During initialization, a few of them will initialize as U3 devices (AU3) and repeatedly fail until I disable the USB port and re-enable. After the hot plug logic correctly detects that they are ANU devices and they run perfectly. Is there a way to tell cgminer to use only a single device type (ANU) or identify which device type is plugged into which port and defeat the automatic detection logic?
Try excluding the AU3. I had a similar problem with my BAJ being detected as a BXM until I excluded it in an earlier version of CGMiner. Sorry, but how do I exclude the AU3? Is that a run-time command line parameter or a configuration parameter prior to the build? It's a command line parameter. It's in the ASIC Readme, or should be at least. To disable detection of the false BXM I had to add "--usb BF1:0". I don't know what the driver instance name for your false AU3 is. |
|
|
|
Having in issue with 4.9.0 on the r-pi. I have 10 Antminer devices (ANU). During initialization, a few of them will initialize as U3 devices (AU3) and repeatedly fail until I disable the USB port and re-enable. After the hot plug logic correctly detects that they are ANU devices and they run perfectly. Is there a way to tell cgminer to use only a single device type (ANU) or identify which device type is plugged into which port and defeat the automatic detection logic?
Try excluding the AU3. I had a similar problem with my BAJ being detected as a BXM until I excluded it in an earlier version of CGMiner. |
|
|
|
Hello. Dear experts, I need help. have scyipt Asik
Mainline CGMiner does not support scrypt. Post in the Alt Coin forum for help with the proper fork, if there is one. |
|
|
|
Just pointing out that the blockchain information doesn't have to reside at the 'default' location or even on the same PC that runs the node. This is a fully supported feature of Bitcoin Core. I'm running this now on an old laptop with a fairly small hard disk drive, that could not accommodate the full blockchain, so I copied it from one of my other PC's that runs a 'normal' client to a NAS (Network Attached Storage), mapped the path to the location on the NAS to a network drive on the PC running the node, and it works. It saved a lot of time of downloading the blockchain off the internet, but still took some time to verify the blocks by the node PC.
Cheers
Cool, I didn't know that. |
|
|
|
I've got bitcoin core running and in the debug window it details if its a incoming or outgoing connection and then a total of them both. Ill leave the machine going and see what it is saying then. Just doing my contribution to the bitcoin network!!  Mine just has the number of connections in the debug window and on the GUI. What does it say on the GUI for "active connections" ? Running the latest QT 0.9.3 with the -disablewallet option on the command line brings a user interface window that shows the incoming and outgoing connections. I fired up my newer client and do see the incoming/outgoing now. I would say it working correctly for your. I don't know about your other question. I do think they are working on supporting multiple wallet.dat files I would think that would be similar to what your thinking, but they aren't there yet. |
|
|
|
I've got bitcoin core running and in the debug window it details if its a incoming or outgoing connection and then a total of them both. Ill leave the machine going and see what it is saying then. Just doing my contribution to the bitcoin network!! Mine just has the number of connections in the debug window and on the GUI. What does it say on the GUI for "active connections" ? |
|
|
|
Hi
It has completed downloading the blockchain and currently has incoming connections. I'm asking the outgoing connections seem to be stuck on 8? Is this correct or will this change as well as it stays live?
thanks
Your client distinguishes between incoming and outgoing connections? I have never seen that. It has always shown me "active connections". Mine is currently at 82. Anyway a socket is both incoming and outgoing. You can use netstat to see how many connections there are but they should be equal to the active connections shown on the client. |
|
|
|
Just a little question,
looking at the stats for bitcoin core, i can see the connections coming in but its always staying on 8 outgoing? Is this just the way it is or will this rise aswell... bare in mind ive had this running for about a hour now.
thanks
It will have 8 connections while downloading the blockchain. Once that has completed it will accept incoming connections provided you have port forwarding set in your router for TCP 8333 to the IP of your machine with the client running. |
|
|
|
Any blocks found yet?
It's very easy to find the block found reports in this thread. All you have to do is look. |
|
|
|
I don't see and equipment detected in you cgminer instance. Cgminer is working, however you are not submitting and shares.
honestly i am new and i want to mining using my CPU using CGminer ,,,,but i do not know what should i need to can mining on my CPU ......i wish to help me please .....what exactly i need to can mining 1) i download CGminer last version . so what i need again to can mining in my cpu  You need a different mining software since CGMiner doesn't use CPU's or GPU's anymore. It only supports ASIC hardware. Also you can't really mine Bitcoin with a CPU so you would need to check into alt coins that can be mined with CPU in the Alt Coin forum. so,,,,what is the other different mining software to can mine bitcoin in my cpu ? help me please Like I said post in the alt coin forum and ask there since you can't mine Bitcoins with CPU. I don't really know what CPU mining software is still available. |
|
|
|
The readme file with 3.1.1 should tell you what command line option you should use to setup the USB miners as serial devices.
Or you could get the latest CGMiner and use the Zadig utility to install WinUSB and set it as the default driver for your miners and use CGMiner, 4.9 now, without any command line options and have it just work.
I would do the latter.
Thanks for the reply! I am currently using an AntMiner U2 ASIC, what mining software would you suggest I use? Sam. I would use the latest version of CGMiner which is 4.9. I doubt that old version will recognize it. |
|
|
|
|
The latest version of CGMiner is 4.9 not 2.4. Don't know where you would have downloaded that old of a version from, but I wouldn't trust it.
Also you should post in the CGMiner forum for support.
|
|
|
|
I don't see and equipment detected in you cgminer instance. Cgminer is working, however you are not submitting and shares.
honestly i am new and i want to mining using my CPU using CGminer ,,,,but i do not know what should i need to can mining on my CPU ......i wish to help me please .....what exactly i need to can mining 1) i download CGminer last version . so what i need again to can mining in my cpu You need a different mining software since CGMiner doesn't use CPU's or GPU's anymore. It only supports ASIC hardware. Also you can't really mine Bitcoin with a CPU so you would need to check into alt coins that can be mined with CPU in the Alt Coin forum. |
|
|
|
Since this is a pool for solo miners, I would assume that you would have better luck here then if you truly solo mined. Is this true? My thought was because the work is split between all the workers instead of all of use doing the same work.
Your luck is the same on a solo pool or on your solo bitcoind. Nobody is doing the same work either way. Solo pools usually have better connections to good super nodes so that your block, if you find one, has a better chance of being broadcasted on the network first. When you solomine it is more likely your block will loose an orphan race. |
|
|
|
|
The readme file with 3.1.1 should tell you what command line option you should use to setup the USB miners as serial devices.
Or you could get the latest CGMiner and use the Zadig utility to install WinUSB and set it as the default driver for your miners and use CGMiner, 4.9 now, without any command line options and have it just work.
I would do the latter.
|
|
|
|
Is the blockerupter prisma/tube not enabled in the windows binary download? When I run cgminer 4.9.0 it never detects the tube I have connected with a
CP2102 Uart. The option "bet-clk 25" results in "unrecognized option". I complied it myself in Mingw. This way detects it but I get LIBUSB errors the a crash.
This same setup works fine under Linux but due to hardware placement windows is the only option now, or the crappy controller using a proxy. Never have been
able to get this thing to hash under Windows 7 x64.
Anyone else encounter this? Did you install the WinUSB driver and set it as the default for your mining devices? Yes, using zadig. Why is the option "--bet-clk 25" returning "unrecognized option" although this is referenced in the readme. What is produced when I attempt to run cgminer: Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Owner\Desktop\cgminer-4.8.0-windows>start.bat C:\Users\Owner\Desktop\cgminer-4.8.0-windows>cgminer.exe -o stratum+tcp://192.168.1.118:73 33 -u Helipotte.0 -p x --api-network --api-listen --bet-clk 25 [2014-12-30 13:40:34] cgminer.exe: --bet-clk: unrecognized option Dunno. I didn't see you mention the WinUSB driver so I thought I'd run that up the flagpole. I'm assuming you tried it without the --bet-clk option at all too? |
|
|
|
|
Show Posts
