Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 27. (Read 5805649 times)
December 03, 2015, 01:52:12 PM
Is it possible to modify cgminer is S3 to look for more than two hashboards? I have a test-board with 4-connectors (Tx and Rx lines + pwm). And I can also test with more devices connected to usb-hub. At least kernel log shows that software installs drivers for cp2102 usb/uart adapter (even with pic in circuit).
December 02, 2015, 02:54:31 AM
Hi -ck,
thank you for your job!
I have 3 Ant S5, if i install this version http://ck.kolivas.org/apps/cgminer/antminer/s5/4.9.0-150105/ the fan go to constantly 100%.
I'm doing something wrong?
thank you for your job!
I have 3 Ant S5, if i install this version http://ck.kolivas.org/apps/cgminer/antminer/s5/4.9.0-150105/ the fan go to constantly 100%.
I'm doing something wrong?
November 27, 2015, 04:40:31 PM
Yes, it was my Fault!
I got a copy of bitcoin.conf for not screwing it up, and guess what I did?
EDIT:
To clear that for all with a similar problem:
The bitcoin.conf got not the correct rpcallowip entry for the client.
I wish I could delete the last entrys in that thread to not beeing identifyed as a "Honk".
Thank you for your help!
I did not see it until I checked the vlan on the cisco and I've got a copy of the conf in the same folder.
The date of the files showed me what I edited.
EDIT: I wonder about the number of connection to bitcoin-qt, both cgminer run "visible" good.
What kind of problem should I expect then on cgminer or bitcoin-qt?
I got a copy of bitcoin.conf for not screwing it up, and guess what I did?
EDIT:
To clear that for all with a similar problem:
The bitcoin.conf got not the correct rpcallowip entry for the client.
I wish I could delete the last entrys in that thread to not beeing identifyed as a "Honk".
Thank you for your help!
I did not see it until I checked the vlan on the cisco and I've got a copy of the conf in the same folder.
The date of the files showed me what I edited.
EDIT: I wonder about the number of connection to bitcoin-qt, both cgminer run "visible" good.
What kind of problem should I expect then on cgminer or bitcoin-qt?
November 27, 2015, 04:36:46 PM
Please be aware that solo mining to your own bitcoind/bitcoin-qt does NOT support M of N addresses (i.e. bitcoin addresses starting with 3). At some stage in the future I will fix this in cgminer but in the interim please only use 1x addresses when mining to your own bitcoin node.
November 27, 2015, 04:33:57 PM
Sorry for wasting your time, found the problem, just checking... November 27, 2015, 04:31:07 PM
Recompile finished, same result, sorry.
Libcurl4-dev was not switched off.
Anything else I might have ruined?
Not in cgminer. What does your rpcallowip have in it on your bitcoin.conf ? Libcurl4-dev was not switched off.
Anything else I might have ruined?
November 27, 2015, 04:22:40 PM
Recompile finished, same result, sorry.
Libcurl4-dev was not switched off.
Anything else I might have ruined?
Libcurl4-dev was not switched off.
Anything else I might have ruined?
November 27, 2015, 04:09:26 PM
it is quite a bit ago, I will check and recompile.
Is there a way how to check that quick?
EDIT: Libcurl was installed so I normaly build with it, but to be shure I am recompiling now.
The raspi2 is fast compared to the old version....
Is there a way how to check that quick?
EDIT: Libcurl was installed so I normaly build with it, but to be shure I am recompiling now.
The raspi2 is fast compared to the old version....
November 27, 2015, 04:07:19 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?
Did you build the raspi version with libcurl ? If you don't then it can't do solo mining. 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?
November 27, 2015, 04: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?
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?
November 27, 2015, 04: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.
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.
November 27, 2015, 03: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. 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.
November 27, 2015, 03: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...
November 27, 2015, 03: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.
November 27, 2015, 02: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.
So it will not help.
Pool Information is then also dead quota.
November 27, 2015, 02:51:44 PM
Have you tried 192.168.2.112:8332
No http:// in cgminer configuration ?
No http:// in cgminer configuration ?
November 27, 2015, 02:43:40 PM
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
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
November 22, 2015, 06:40:38 PM
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
Edit: Finally got it to work using the command line
November 22, 2015, 04: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)
November 22, 2015, 03:19:07 PM
Ok thanks for the info. The hardware is working it works here and there when i use the bitminter client.
Jump to: