|
helipotte
|
 |
November 12, 2015, 09:42:13 PM |
|
Thanks for the offer guys, but being in Australia means it would cost more to ship than the hardware itself is worth. Perhaps if you could find a document somewhere with firmware change details I could guess what modifications might be needed in the driver from it and work on one remotely.
According to BFL "Monarchs shipped April 2015 and after can use the official BFGMiner 5.1.0 or later." and it would appear there were changes there that broke all older versions since BFL says to use a custom version built on Jun 23rd 2014 for "Monarchs shipped before April 2015". I would guess that the change can be found somewhere here on a date after Jun 23rd 2014. I wonder how you would determine which units shipped prior to April 2014? I got all of mine second hand. Maybe that is the month F/W 1.4.5 started going on production units. As a sidenote, I have been using BFGminer 5.4.0 but the cpu usage is very high when I have many units controlled by one instance (15+).
|
|
|
|
|
GameGen
Newbie

Activity: 23
Merit: 0
|
 |
November 13, 2015, 07:39:06 PM |
|
I have an little problem or bug by cgminer 4.9.2. Who can help me?
|
|
|
|
|
os2sam
Legendary

Activity: 3586
Merit: 1099
Think for yourself
|
 |
November 14, 2015, 12:13:26 AM |
|
I have an little problem or bug by cgminer 4.9.2. Who can help me?
Well this is the support thread for CGMiner. So post your problem/bug. Preferably with screen captures, your command line and .conf file if you use that.
|
A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
|
|
|
GameGen
Newbie

Activity: 23
Merit: 0
|
 |
November 14, 2015, 12:23:49 AM Last edit: November 14, 2015, 10:23:04 AM by GameGen |
|
ok fine, my first question can i run my antminer u2 and u3 together. My second question after some time freeze cgminer and when i try to restart it with s, c, y Screenshot: https://onedrive.live.com/redir?resid=57341EF1A3DDC267!6055&authkey=!AImC6a4fWmgEDtk&v=3&ithint=photo%2cpng I wait 5 hours and i can´t close the window. Start batch: cgminer.exe -o stratum+tcp://coinotron.com:3338 -O ..... --au3-freq 237.5 --au3-volt 800 --api-listen by me was ist late sorry for the little mistranslation
|
|
|
|
|
kano
Legendary

Activity: 4844
Merit: 1933
Linux since 1997 RedHat 4
|
 |
November 14, 2015, 01:51:24 AM |
|
Thanks for the offer guys, but being in Australia means it would cost more to ship than the hardware itself is worth. Perhaps if you could find a document somewhere with firmware change details I could guess what modifications might be needed in the driver from it and work on one remotely. ...
I wonder how you would determine which units shipped prior to April 2014? I got all of mine second hand. Maybe that is the month F/W 1.4.5 started going on ... Well the API 'stats' "GetInfo" I show all the information the BFL devices state for their configuration which shows "FIRMWARE: 1.0.0" for my one before it died That's your best bet ... assuming the correct things were done by BFL ...
|
|
|
|
|
zOU
|
 |
November 15, 2015, 07:12:32 PM |
|
I doubt it looks acceptable yet, it's pretty much the half of icarus that I wanted plus some initialization. I intend to clean it up more when I add multi-chip support.
But I do plan to push it into cgminer so it's available.
-- novak
Hello, Do you want to wait for multichip support or you want to push it before ? Thank you novak
|
|
|
|
|
nubbins7
|
 |
November 21, 2015, 10:49:58 PM |
|
I am having a problem getting cgminer too detected my antminer u3 i have downloaded the driver needed and did what i had too do with zadig but still getting "NO DEVICES DETECTED" please help someone thanks. 
|
|
|
|
|
kano
Legendary

Activity: 4844
Merit: 1933
Linux since 1997 RedHat 4
|
 |
November 22, 2015, 04:23:22 AM |
|
I am having a problem getting cgminer too detected my antminer u3 i have downloaded the driver needed and did what i had too do with zadig but still getting "NO DEVICES DETECTED" please help someone thanks.  One of: bad hardware, bad cables, bad hub, unrecognised usb3 port, or you need to master: https://github.com/ckolivas/cgminer/blob/master/README#L399
|
|
|
|
|
zOU
|
 |
November 22, 2015, 08:33:24 AM |
|
I am having a problem getting cgminer too detected my antminer u3 i have downloaded the driver needed and did what i had too do with zadig but still getting "NO DEVICES DETECTED" please help someone thanks.  you should probably ask in the Antminer U3 support thread 
|
|
|
|
|
nubbins7
|
 |
November 22, 2015, 08:19:07 PM |
|
Ok thanks for the info. The hardware is working it works here and there when i use the bitminter client.
|
|
|
|
|
kano
Legendary

Activity: 4844
Merit: 1933
Linux since 1997 RedHat 4
|
 |
November 22, 2015, 09:38:21 PM |
|
Ok thanks for the info. The hardware is working it works here and there when i use the bitminter client.
If the bitminter client is working, then cgminer wont work. cgminer is the only miner to do direct USB, we sidestep all the various random low quality serial drivers and talk directly to USB miners. Thus you need zadig setup correctly, then cgminer mines to all devices using the one WinUSB driver. Bitminter wont work with zadig setup correctly. (This of course is only a windows issue)
|
|
|
|
|
nubbins7
|
 |
November 22, 2015, 11:40:38 PM Last edit: November 23, 2015, 01:03:58 AM by nubbins7 |
|
Thanks for your time but still cant get it too work followed all the steps needed but nothing. Edit: Finally got it to work using the command line
|
|
|
|
|
o_solo_miner
Legendary

Activity: 2574
Merit: 1540
-> morgen, ist heute, schon gestern <-
|
 |
November 27, 2015, 07:43:40 PM Last edit: November 27, 2015, 08:00:49 PM by o_solo_miner |
|
Well, I've got a problem with cgminer 4.9.2 (with BFL Jalapeno) on a Raspi2. As long as I try to connect to cksolo all went ok. If I try my bitcoind, it reports: "No Stratum, GBT or Solo support in pool 0 http://192.168.2.112:8332 unable to use" Info: --- On cgminer 4.7.1 (Win Version with an Antminer U2) conection to my bitcoind works verry well. Bitcoind is the v0.11.2 (64Bit) running on Linux. --- I am now a bit confused where to search first for my error. can you please point me in a direction where to search for error? Edit: The rpcallowip entry is setup correctly in bitcoin.conf for both, the pc and the raspi2
|
|
|
|
|
zOU
|
 |
November 27, 2015, 07:51:44 PM |
|
Have you tried 192.168.2.112:8332
No http:// in cgminer configuration ?
|
|
|
|
o_solo_miner
Legendary

Activity: 2574
Merit: 1540
-> morgen, ist heute, schon gestern <-
|
 |
November 27, 2015, 07:55:02 PM |
|
Yes, but then as expected cgminer uses stratum protocol wich is not possible with bitcoind. So it will not help. Pool Information is then also dead quota.
|
|
|
|
os2sam
Legendary

Activity: 3586
Merit: 1099
Think for yourself
|
 |
November 27, 2015, 08:32:45 PM |
|
"No Stratum, GBT or Solo support in pool 0 http://192.168.2.112:8332 unable to use" Info: --- Bitcoind is the v0.11.2 (64Bit) running on Linux. --- When I get this error message with 11.2 I just have to shutdown Bitcoin-qt and restart it then start CGMiner again. I have to do this every 1 to 4 days. The Bitcoin client isn't as stable/reliable as it used to be, it seems.
|
A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
|
|
|
o_solo_miner
Legendary

Activity: 2574
Merit: 1540
-> morgen, ist heute, schon gestern <-
|
 |
November 27, 2015, 08:47:18 PM |
|
"No Stratum, GBT or Solo support in pool 0 http://192.168.2.112:8332 unable to use" Info: --- Bitcoind is the v0.11.2 (64Bit) running on Linux. --- When I get this error message with 11.2 I just have to shutdown Bitcoin-qt and restart it then start CGMiner again. I have to do this every 1 to 4 days. The Bitcoin client isn't as stable/reliable as it used to be, it seems. In the morning I switch on my work pc (Debian8 64Bit), that is running bitcoin-qt with the -server. On the Win PC I let the win version run with the u2 and this works fine, no issues. Then I start it on the raspi2 and it comes up with this error, and switch to the Failover solockpool and works ok then. I try'ed Raspi2 only, no change. I reconfigured bitcoin.conf to Raspi2 only, no change. Maybe it is a fault of mine in compiling this? I got absolute no idea. EDIT: When cgminer is started it probes and directly report the error, so I was thinking that it try and not waiting for a response or so...
|
|
|
|
-ck (OP)
Legendary

Activity: 4844
Merit: 1744
Ruu \o/
|
 |
November 27, 2015, 08:54:02 PM |
|
In the morning I switch on my work pc (Debian8 64Bit), that is running bitcoin-qt with the -server. On the Win PC I let the win version run with the u2 and this works fine, no issues. Then I start it on the raspi2 and it comes up with this error, and switch to the Failover solockpool and works ok then.
I try'ed Raspi2 only, no change. I reconfigured bitcoin.conf to Raspi2 only, no change.
Maybe it is a fault of mine in compiling this? I got absolute no idea.
Are you connecting more than one miner to the bitcoin-qt at a time? Since cgminer maintains a persistent connection when solo mining, bitcoind doesn't like more than one connection to it.
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
o_solo_miner
Legendary

Activity: 2574
Merit: 1540
-> morgen, ist heute, schon gestern <-
|
 |
November 27, 2015, 09:01:29 PM |
|
puhh thank you for answering, I get crazy here.
It does not work if I try do do it with the raspi only.
But i will double check now, i return in a minute.
|
|
|
|
o_solo_miner
Legendary

Activity: 2574
Merit: 1540
-> morgen, ist heute, schon gestern <-
|
 |
November 27, 2015, 09:06:03 PM |
|
sorry for double post,
No it does not work with the bitcoin-qt in solo mode.
The rpcallow is now on the raspi ip, the win version was not started and the message appear direct after starting cgminer. It probe for alive pool and display the error, after that it switch over and work fine.
Maybe it is an issue on the raspi Network?
|
|
|
|
|