 Show Posts
|
|
Pages: [1]
|
Why not put you a loop in the script that cycles between pools? that way if the cgminer crashes or loses connection then it will auto resume.
...
All (reputable) standalone miners have a crontab entry checking the API every few minutes that restarts cgminer when it isn't mining. Edit: also there are apps that will alert you if your hash rate drops. So, to make sure I understand. I need to add a crontab entry to check the API? Any chance of getting some sample code or a link to an explainer so I can get that done on my Raspberry Pi? Also, any suggestions of apps to monitor the hash rate? Thanks for helping an old guy learn new tricks. Much 'predicated. |
|
|
|
Why not put you a loop in the script that cycles between pools? that way if the cgminer crashes or loses connection then it will auto resume.
Then put that script in the rc.local so it runs at start up? that way as long as power is on, with cables connected, and internet access you are just about plug and forget.
@acoleman Makes a lot of sense. I've been wondering about connecting to more than one pool. Was trying to be loyal since Kano helped me get up and running in the first place. What other pools have the same kind of solid reputation? Also would you mind providing a sample of what that script looks like? |
|
|
|
Does anyone have/use a script to monitor cgminer and send out alert emails if it seems to be down or not functioning correctly? As OCD as I am checking Kano's site and ssh-ing into my Pi each day to make sure all is well seems like the long way around this wall. I found this one but it seems very old and I'm concerned it might not work or worse yet hose up my now very stable mining rig. https://github.com/romdr/cgminer-monitor Thanks in advance for any help of direction you can provide.  |
|
|
|
Are you running your own .sh file or just opening cgminer?
I suppose I'm just opening cgminer. Here is exactly every step I took up to this point: sudo apt-get update
sudo apt-get upgrade -y
sudo apt-get install -y build-essential autoconf automake libtool pkg-config libcurl4-openssl-dev libudev-dev libusb-1.0-0-dev libncurses5-dev zlib1g-dev git
cd
git clone https://github.com/kanoi/cgminer.git
cd cgminer
CFLAGS="-O2 -march=native -fcommon" ./autogen.sh --enable-gekko --enable-icarus
sudo make install
cd cgminer
sudo cgminer -o stratum+tcp://nl.kano.is:3333 -u *******.worker -p x --gekko-compacf-freq 450 --gekko-start-freq 300 --gekko-mine2 --gekko-tune2 60
Then when it starts running the T value and frequency are both 200. In the dir 'cgminer', when I type 'ls', no cgminer.conf file is listed but when I type '/root/.cgminer/cminer.conf' it returns "access denied." Really hope you guys can help because I don't want to give up. Please excuse my ignorance!  I might be wrong but I think it's one of two things. Maybe both. 1. In your last line change it to ./cgminer sudo ./cgminer -o stratum+tcp://nl.kano.is:3333 -u *******.worker -p x --gekko-compacf-freq 450 --gekko-start-freq 300 --gekko-mine2 --gekko-tune2 60 2. Did you run the commands for USB port access? I'm pretty sure I found that in this forum somewhere. It's just two lines of commands you need to run, but I'd try #1 above first. |
|
|
|
Three ideas 1) --suggest-diff 442 Using lower will be ignored on my pool Or just set it on the Workers->Management page to 442 2) try: --gekko-compacf-freq 450 --gekko-start-freq 300 --gekko-mine2 --gekko-tune2 60 Of course, as obvious, make sure it has enough cooling 3) grab a screen shot so we can see what it says Wish me luck - after running over a week at 400 with no issues going to push it to 450 and see if the smoke stays inside the sticks Update: Looks like with the BitCoinMech USB hub the max might be 425 with three sticks. I did tweak the pot screw a bit to get this working but at 450 just didn't seem to settle down in a stable state. Might buy more sticks and try a different hub as an experiment. |
|
|
|
Thats probably why it hasnt been mentioned. Its not as linear as the previous sticks. Cheers Kano.
EDIT:-
Just throwing this out there. But would there be a market for a dual to single usb pcb to join two ports together on the gekko hub? So you can run a compac-f at full speed? Er? Why? to feed the F 6A? You can already do that with his hub -- if you do not mind vastly overloading the USB socket, just leave the other port open, plug in the F and crank her up. A dual to single adapter still faces that max 3A limit for the single socket. I just installed meters between my sticks and the hub. I'm getting just under 5V at just under 2A per port. Is that sufficient to run at 400? |
|
|
|
@kano All I can say is thank you. All the struggling to learn about mining over the last months just paid off in your one message. You really did simplify the complex, at least enough for me to understand it! cgminer must determine if a share (nonce) should be sent to the pool. It would be really bad if it couldn't do that When you tell cgminer you want all the extra information it can throw at you, by telling it '--verbose', one of the output lines is to tell you what it does with each nonce the chip returns to cgminer. At 260GH/s you generate around 60.5 nonces of 1 difficulty, per second. My pool doesn't want you sending that much crap to it Nor do you want to increase your network flow by 202 times My pool will set a work difficulty so that you are sending shares at around 18 per minute. Thus cgminer must work out what difficulty each nonce is and if it should send it. In verbose more it tells you for, on average, 201 of those 202 that their difficulty is too low. https://kano.is/index.php?k=workdiff [2021-10-29 09:28:27.862] Accepted 4b97ce57 Diff 867/788 GSF 0
This means the pool is asking me for shares of 788 diff or higher (one GSF + one GSI) Another way to look at this is that it means, on average, one in 788 nonces returned at 1 difficulty will be 788 difficulty. However the driver I wrote will have already set the chip ticket mask (difficulty) to 16 at this stage, so only 16th of the nonces are returned by the chip over USB to cgminer. Thus you'd see 16th of the messages in verbose mode. |
|
|
|
@VanLife4Me, please edit your posts to use the code tag. Found on the tool bar it looks like #. Using it changes text logs to a much easier to look at scrollable box like this cgminer version 4.12.0 - Started: [2021-10-28 17:59:42.804]
--------------------------------------------------------------------------------
(5s):870.0G (1m):841.4G (5m):813.9G (15m):805.1G (avg):799.4Gh/s
A:1061242 R:0 HW:544 WU:11166.9/m
Connected to stratum.kano.is diff 442 with stratum as user xxxxxxxx.worker
Block: bf5e4b2d... Diff:20.1T Started: [19:29:35.353] Best share: 892K
--------------------------------------------------------------------------------
SB management [P]ool management ettings [D]isplay options [Q]uit
0: GSF 10050209: BM1397:01+ 400.00MHz T:400 P:400 (31:16) | 100% WU:100% | 196
1: GSF 10050081: BM1397:01+ 400.00MHz T:400 P:400 (31:16) | 100% WU:100% | 293
2: GSF 10050191: BM1397:01+ 400.00MHz T:400 P:400 (32:16) | 100% WU:100% | 347
.1G / 268.0Gh/s WU:3744.1/m-----------------------------------------------------
[2021-10-28 19:33:17.202] Accepted 375b762b Diff 1.18K/442 GSF 2
[2021-10-28 19:33:18.604] Accepted 1a901997 Diff 2.47K/442 GSF 0
[2021-10-28 19:33:19.002] Accepted 481c8428 Diff 909/442 GSF 2
[2021-10-28 19:33:20.763] Accepted 0d5c652a Diff 4.91K/442 GSF 0
[2021-10-28 19:33:21.861] Accepted 52c80865 Diff 792/442 GSF 1
[2021-10-28 19:33:22.101] Accepted 834b1bce Diff 499/442 GSF 1
[2021-10-28 19:33:24.344] Accepted 5cfdf732 Diff 705/442 GSF 2
[2021-10-28 19:33:25.284] Accepted 091f85f6 Diff 7.18K/442 GSF 2
[2021-10-28 19:33:29.083] Accepted 45308790 Diff 947/442 GSF 2
[2021-10-28 19:33:29.423] Accepted 25566981 Diff 1.75K/442 GSF 2
[2021-10-28 19:33:30.581] Accepted 0400f618 Diff 16.4K/442 GSF 1
Done, and thank you for the tip. |
|
|
|
"Share above target" is probably something with the pool expecting a faster miner (more shares coming in) and it could take a few minutes to retarget.
NiceHash and proper cgminer don't work well together, because NiceHash requires some added protocol stuff that's demonstrably insecure and kano refuses to support it.
I'm still getting the Share above target on Kano where I have been running all morning. Does this help? cgminer version 4.12.0 - Started: [2021-10-28 17:59:42.804] -------------------------------------------------------------------------------- (5s):720.6G (1m):776.9G (5m):756.4G (15m):524.5G (avg):796.0Gh/s A:186082 R:0 HW:128 WU:11117.7/m Connected to stratum.kano.is diff 442 with stratum as user xxxxxxx.worker Block: 281d978b... Diff:20.1T Started: [18:13:35.427] Best share: 459K -------------------------------------------------------------------------------- SB management [P]ool management ettings [D]isplay options [Q]uit
0: GSF 10050209: BM1397:01+ 400.00MHz T:400 P:400 (32:16) | 100% WU:100% | 276
1: GSF 10050081: BM1397:01+ 400.00MHz T:400 P:399 (32:16) | 100% WU:100% | 254
2: GSF 10050191: BM1397:01+ 400.00MHz T:400 P:400 (32:16) | 100% WU:100% | 223
.7G / 265.7Gh/s WU:3711.1/m-----------------------------------------------------
[2021-10-28 18:15:59.600] GSF 1: Share above target
[2021-10-28 18:15:59.600] 1: GSF 1 - AsicBoost nonce found : midstate 2
[2021-10-28 18:15:59.680] 1: GSF 1 - Device reported nonce: 8d5bfa0f @ 19 (0)
[2021-10-28 18:15:59.680] GSF 1: Share above target
[2021-10-28 18:15:59.680] 1: GSF 1 - AsicBoost nonce found : midstate 1
[2021-10-28 18:15:59.700] 1: GSF 1 - Device reported nonce: bc62f812 @ 19 (0)
[2021-10-28 18:15:59.700] GSF 1: Share above target
[2021-10-28 18:15:59.700] 1: GSF 1 - AsicBoost nonce found : midstate 1
[2021-10-28 18:15:59.842] 2: GSF 2 - Device reported nonce: 4f401734 @ 79 (0)
[2021-10-28 18:15:59.842] GSF 2: Share above target
[2021-10-28
Looks like you have the "--verbose" command in your config/bat file. Take that out and see what you get listed on the cgminer screen. Thank you, I turned that on when it seemed to not be working with Nicehash. So, this is what it should look like then? cgminer version 4.12.0 - Started: [2021-10-28 17:59:42.804]
--------------------------------------------------------------------------------
(5s):870.0G (1m):841.4G (5m):813.9G (15m):805.1G (avg):799.4Gh/s
A:1061242 R:0 HW:544 WU:11166.9/m
Connected to stratum.kano.is diff 442 with stratum as user xxxxxxxx.worker
Block: bf5e4b2d... Diff:20.1T Started: [19:29:35.353] Best share: 892K
--------------------------------------------------------------------------------
[U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
0: GSF 10050209: BM1397:01+ 400.00MHz T:400 P:400 (31:16) | 100% WU:100% | 196
1: GSF 10050081: BM1397:01+ 400.00MHz T:400 P:400 (31:16) | 100% WU:100% | 293
2: GSF 10050191: BM1397:01+ 400.00MHz T:400 P:400 (32:16) | 100% WU:100% | 347
.1G / 268.0Gh/s WU:3744.1/m-----------------------------------------------------
[2021-10-28 19:33:17.202] Accepted 375b762b Diff 1.18K/442 GSF 2
[2021-10-28 19:33:18.604] Accepted 1a901997 Diff 2.47K/442 GSF 0
[2021-10-28 19:33:19.002] Accepted 481c8428 Diff 909/442 GSF 2
[2021-10-28 19:33:20.763] Accepted 0d5c652a Diff 4.91K/442 GSF 0
[2021-10-28 19:33:21.861] Accepted 52c80865 Diff 792/442 GSF 1
[2021-10-28 19:33:22.101] Accepted 834b1bce Diff 499/442 GSF 1
[2021-10-28 19:33:24.344] Accepted 5cfdf732 Diff 705/442 GSF 2
[2021-10-28 19:33:25.284] Accepted 091f85f6 Diff 7.18K/442 GSF 2
[2021-10-28 19:33:29.083] Accepted 45308790 Diff 947/442 GSF 2
[2021-10-28 19:33:29.423] Accepted 25566981 Diff 1.75K/442 GSF 2
[2021-10-28 19:33:30.581] Accepted 0400f618 Diff 16.4K/442 GSF 1 I suspect yes as it looks like this on Kano.is: Worker Name: Work Diff :Last Share Shares :Diff :Share Rate ĢElapsed :Invalid :Hash Rate Info :Best :Best Ever
xxxxxxxx.worker 442 6s 7,165 3,166,930 656.67GHs 2m 39s 0.000% 806.25GHs LA/Bv 74.1786M 74.1786M
Total: 1 (1 active worker) 7,165 3,166,930 656.67GHs 0.000% 806.25GHs |
|
|
|
"Share above target" is probably something with the pool expecting a faster miner (more shares coming in) and it could take a few minutes to retarget.
NiceHash and proper cgminer don't work well together, because NiceHash requires some added protocol stuff that's demonstrably insecure and kano refuses to support it.
I'm still getting the Share above target on Kano where I have been running all morning. Does this help? cgminer version 4.12.0 - Started: [2021-10-28 17:59:42.804]
--------------------------------------------------------------------------------
(5s):720.6G (1m):776.9G (5m):756.4G (15m):524.5G (avg):796.0Gh/s
A:186082 R:0 HW:128 WU:11117.7/m
Connected to stratum.kano.is diff 442 with stratum as user xxxxxxx.worker
Block: 281d978b... Diff:20.1T Started: [18:13:35.427] Best share: 459K
--------------------------------------------------------------------------------
[U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
0: GSF 10050209: BM1397:01+ 400.00MHz T:400 P:400 (32:16) | 100% WU:100% | 276
1: GSF 10050081: BM1397:01+ 400.00MHz T:400 P:399 (32:16) | 100% WU:100% | 254
2: GSF 10050191: BM1397:01+ 400.00MHz T:400 P:400 (32:16) | 100% WU:100% | 223
.7G / 265.7Gh/s WU:3711.1/m-----------------------------------------------------
[2021-10-28 18:15:59.600] GSF 1: Share above target
[2021-10-28 18:15:59.600] 1: GSF 1 - AsicBoost nonce found : midstate 2
[2021-10-28 18:15:59.680] 1: GSF 1 - Device reported nonce: 8d5bfa0f @ 19 (0)
[2021-10-28 18:15:59.680] GSF 1: Share above target
[2021-10-28 18:15:59.680] 1: GSF 1 - AsicBoost nonce found : midstate 1
[2021-10-28 18:15:59.700] 1: GSF 1 - Device reported nonce: bc62f812 @ 19 (0)
[2021-10-28 18:15:59.700] GSF 1: Share above target
[2021-10-28 18:15:59.700] 1: GSF 1 - AsicBoost nonce found : midstate 1
[2021-10-28 18:15:59.842] 2: GSF 2 - Device reported nonce: 4f401734 @ 79 (0)
[2021-10-28 18:15:59.842] GSF 2: Share above target
[2021-10-28 |
|
|
|
So, I've read enough here to know some of you are successfully mining, is it just that I shouldn't be mining with NiceHash? If so, any recommendations?
Known good pools are kano.is and solo.ckpool.org Use those to get everything configured correctly. First question - to avoid top posting (which I guess I did) should I have quoted a previous message? So, I'm connected to Kano now and getting the same issue "Share above target" and suggestions on how to attack that? Is it going to be a matter of getting the voltages right? At the moment I'm running one stick and one fan at a time. I'm using all equipment from bitcoinmerch. Thanks for being patient with a new guy. I've spent several days making sure I'd tried everything I could figure out from internet searches. |
|
|
|
|
Hello all, newbie here, but I have read this whole thread a few times.
I've got my three CompacF miners running with CGMiner at 400 (I have meters coming Friday to further tune voltage), but when I mine with NiceHash I end up with most of my shares being discarded. Their help says this has something to do with my mining software and overclocking.
So, I've read enough here to know some of you are successfully mining, is it just that I shouldn't be mining with NiceHash? If so, any recommendations? I'd like to generate revenue regularly as this is part of my DCA stacking strategy.
Thanks in advance for any help you all can provide, finding this thread has made my life so much easier!
|
|
|
|
|
