Topic: Oct 11 to Nov 11 Sidehack stick pool club. - page 5. (Read 19804 times)
TheRock stick is down ... will fix it tonight.
I PMed to larry12 if i can take his place in this club. He answered: "hi no problem to take my “seat” i’m not in my country right now and i cant manage sidestick."
If it's ok for "the club", i will start on sunday.
If it's ok for "the club", i will start on sunday.
Could phil/cryptoglance set up a donation worker for me.
I'm #17 on the list as .peptostick
Could you add a .peptodonation worker for me please?
As an aside, my two sticks were nearly dead this morning when I woke up, generating 1 Gh on one stick and nothing on the other.
I unplugged and replugged them, rebooted minera, and they came back to life. Very strange though because they had been running without a hiccup for weeks.
I'm #17 on the list as .peptostick
Could you add a .peptodonation worker for me please?
As an aside, my two sticks were nearly dead this morning when I woke up, generating 1 Gh on one stick and nothing on the other.
I unplugged and replugged them, rebooted minera, and they came back to life. Very strange though because they had been running without a hiccup for weeks.
Been messing around with my sticks... so they are off and on. Still have issues running different pools from different sticks, I'm using cgminer-gekko and Pi. The --usb :1 command seems to work as long as there is one instance running but multiple ones read duplicate #'s if labeled --usb :2 and so on.
Has anyone looked into their /etc/rc.local file? I found Minerd in there mining cpu hashes for someones ghash.io acct. (worth checking) or is this just an example?
Has anyone looked into their /etc/rc.local file? I found Minerd in there mining cpu hashes for someones ghash.io acct. (worth checking) or is this just an example?
--usb :# is for the # of sticks you want to run on each instance of cgminer. So usb :2 would do 2 sticks.
Also found it helps to put a sleep in before the next instance starts in the /etc/rc.local
sudo ./cgminer -o pool -u
sleep 10s (just tells it to wait 10 seconds, before starting 2nd cgminer and most times 6 seconds will do, but whats an extra 4 seconds?)
sudo ./cgminer -o pool -u
When I added those lines in the /etc folder it did not auto start for me.
With the Pi being Linux (unless your using some thing else for the Pi) you have to do the sudo cp 01-cgminer.rules /etc/udev/rules.d/ from within the cgminer-gekko dir.
Also need to sudo usermod -G plugdev -a "what ever user name you used" (it's probably already done, but just to make sure and without "").
My /etc/rc.local looks like this.
#!/bin/sh -e
(cut out standard lines)
# By default this script does nothing.
cd /home/pi/cgminer-gekko (pi as example)
sleep 10s (if you want, just to give the Pi time to boot up)
screen -dmS cgminer sudo ./cgminer -o stratum+tcp://solo.ckpool.org:3333 -u xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx --usb :1 --compac-freq 250 --suggest-diff 16 --widescreen --worktime -o stratum+tcp://stratum.kano.is:3333 -u xxxxxx (all on one line)
sleep 10s
screen -dmS cgminer sudo ./cgminer -o stratum+tcp://solo.ckpool.org:3333 -u 1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.Jake36stick --usb :4 --com :4 --compac-freq 250 --suggest-diff 68 --widescreen --worktime -o stratum+tcp://stratum.kano.is:3333 -u xxxxxxx (all on one line)
exit 0
Plus, if you make a mistake on 1 or both of the long lines, 1 or both usually wont start mining.
Are you guys still accepting new members for the club?
My sticks (from the first batch if I'm not mistaken) just got released from customs and I might get them sent from the capital in two weeks.
Sorry if the answer to my question seems obvious, but english is not my first language and the first posts in the thread looked a bit messy so I'm not sure if you're taking in members or not.
My sticks (from the first batch if I'm not mistaken) just got released from customs and I might get them sent from the capital in two weeks.
Sorry if the answer to my question seems obvious, but english is not my first language and the first posts in the thread looked a bit messy so I'm not sure if you're taking in members or not.
I need to review as we max at 30.
Maybe therealsteve dropped out.
give me a little time to check.
the answer is therealsteve has not stick mined for a week in a row so you could take his place when your sticks come into your home.
So you are next in line. post when you get the sticks.
Are you guys still accepting new members for the club?
My sticks (from the first batch if I'm not mistaken) just got released from customs and I might get them sent from the capital in two weeks.
Sorry if the answer to my question seems obvious, but english is not my first language and the first posts in the thread looked a bit messy so I'm not sure if you're taking in members or not.
My sticks (from the first batch if I'm not mistaken) just got released from customs and I might get them sent from the capital in two weeks.
Sorry if the answer to my question seems obvious, but english is not my first language and the first posts in the thread looked a bit messy so I'm not sure if you're taking in members or not.
Been messing around with my sticks... so they are off and on. Still have issues running different pools from different sticks, I'm using cgminer-gekko and Pi. The --usb :1 command seems to work as long as there is one instance running but multiple ones read duplicate #'s if labeled --usb :2 and so on.
Has anyone looked into their /etc/rc.local file? I found Minerd in there mining cpu hashes for someones ghash.io acct. (worth checking) or is this just an example?
Has anyone looked into their /etc/rc.local file? I found Minerd in there mining cpu hashes for someones ghash.io acct. (worth checking) or is this just an example?
--usb :# is for the # of sticks you want to run on each instance of cgminer. So usb :2 would do 2 sticks.
Also found it helps to put a sleep in before the next instance starts in the /etc/rc.local
sudo ./cgminer -o pool -u
sleep 10s (just tells it to wait 10 seconds, before starting 2nd cgminer and most times 6 seconds will do, but whats an extra 4 seconds?)
sudo ./cgminer -o pool -u
When I added those lines in the /etc folder it did not auto start for me.
going to try jakes link. today or tomorrow.
I set up my two s-7's in the garage they run well. Took a while .
I setup the 5 compacs on bfgminer yesterday they are running okay.
I will get on to the new rasp pi late today.
It is going to be 75f today. I am going to top coat my driveway for the winter.
This hot temp will let me do it and all the Rain we had the last two days has prepped the driveway nicely.
The real reason is my house is 81f today with the heat from the 2 s-7's
So when I coat my driveway I will leave the garage door open this will cool things off.
I set up my two s-7's in the garage they run well. Took a while .
I setup the 5 compacs on bfgminer yesterday they are running okay.
I will get on to the new rasp pi late today.
It is going to be 75f today. I am going to top coat my driveway for the winter.
This hot temp will let me do it and all the Rain we had the last two days has prepped the driveway nicely.
The real reason is my house is 81f today with the heat from the 2 s-7's
So when I coat my driveway I will leave the garage door open this will cool things off.
Will that image work on the new model rasp pi?
I could use an image for my model 2 rasp pi.
I could use an image for my model 2 rasp pi.
My current one is a RPI 1 model b. But if it would be useful I have a RPI 2 been sitting waiting for a project. I could get a Raspbian image with compac-cgminer installed on it.
Do you need it to run the pre productions usb's (that black one or reviewer), or just production? I should be able to throw one together.
Will that image work on the new model rasp pi?
I could use an image for my model 2 rasp pi.
I'm running the linked Minera with the gekko cgminer on my Pi 2 mod B - plug and play. You could pull the cgminer out and just copy that to a new card as well. Or compile it - the Pi2's compile stuff so much faster than the earlier boards.I could use an image for my model 2 rasp pi.
Been messing around with my sticks... so they are off and on. Still have issues running different pools from different sticks, I'm using cgminer-gekko and Pi. The --usb :1 command seems to work as long as there is one instance running but multiple ones read duplicate #'s if labeled --usb :2 and so on.
Has anyone looked into their /etc/rc.local file? I found Minerd in there mining cpu hashes for someones ghash.io acct. (worth checking) or is this just an example?
Has anyone looked into their /etc/rc.local file? I found Minerd in there mining cpu hashes for someones ghash.io acct. (worth checking) or is this just an example?
--usb :# is for the # of sticks you want to run on each instance of cgminer. So usb :2 would do 2 sticks.
Also found it helps to put a sleep in before the next instance starts in the /etc/rc.local
sudo ./cgminer -o pool -u
sleep 10s (just tells it to wait 10 seconds, before starting 2nd cgminer and most times 6 seconds will do, but whats an extra 4 seconds?)
sudo ./cgminer -o pool -u
Will that image work on the new model rasp pi?
I could use an image for my model 2 rasp pi.
I could use an image for my model 2 rasp pi.
There is no harm in trying it, it might work, but I don't think it will work, different processor's.
I've got a new Pi 2 model, thats running Ubuntu 14.04.3 LTS and cgminer-gekko. I'll look for the links to loading it and post them
I can also read up and find out how to do an image of it and post it when I get time in a day or 2, if you want.
EDIT: Woke up a little early, so here are the instructions I followed to get Ubuntu 14.04.3 LTS (it's a stripped down version without all the extras like office/video player and stuff) running on the Pi 2.
https://www.raspberrypi.org/documentation/installation/installing-images/README.md (just pick what operating system your going to use to write the image with)
https://wiki.ubuntu.com/ARM/RaspberryPi#Download (to download the image and set it up once it's written to the SD card (just noticed it's got the above link on there to)).
There's also Ubuntu 15.10 Mate out for the Pi 2, but it has a lot of the stuff like office suit, video, and the like installed (https://ubuntu-mate.org/raspberry-pi/) that is not needed for mining. I tried this one (or 15.04) and went with the 14.03 one instead, for some reason I can't remember now.
Been messing around with my sticks... so they are off and on. Still have issues running different pools from different sticks, I'm using cgminer-gekko and Pi. The --usb :1 command seems to work as long as there is one instance running but multiple ones read duplicate #'s if labeled --usb :2 and so on.
Has anyone looked into their /etc/rc.local file? I found Minerd in there mining cpu hashes for someones ghash.io acct. (worth checking) or is this just an example?
Has anyone looked into their /etc/rc.local file? I found Minerd in there mining cpu hashes for someones ghash.io acct. (worth checking) or is this just an example?
Okay when I set bfgminer up on a windows 7 at BuySolar's house it was a bit buggy but we got it to do 5 sticks at 60gh on bitminer.
It was okay.
Nothing compares to linux debian running cgminer I get 25 days of uptime or better close to prefect hw's.
I just need to spend time learning linux as it really seems to be good for these sticks.
I pulled the biggest stick share I have ever done today!
http://solo.ckpool.org/workers/1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.philipma1957sticks
"bestshare": 2,281,962,537.7536292
2 billion plus not bad!
It was okay.
Nothing compares to linux debian running cgminer I get 25 days of uptime or better close to prefect hw's.
I just need to spend time learning linux as it really seems to be good for these sticks.
I pulled the biggest stick share I have ever done today!
http://solo.ckpool.org/workers/1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.philipma1957sticks
"bestshare": 2,281,962,537.7536292
2 billion plus not bad!
Thanks for sharing this... Because of this post, I realized the column size was incorrect and the BestShare was not saving correctly. I have updated the column...... Turns out our best share was 19B!
Will that image work on the new model rasp pi?
I could use an image for my model 2 rasp pi.
I could use an image for my model 2 rasp pi.
What are your thoughts on bfgminer vs cgminer after trying both? I have been using cgminer as novak seemed to do a great one of it.
I was curious if you noticed any pro's or con's. It sounded like bfgminer was getting better after update on able to use freq, but was not sure if worth trying.
I was curious if you noticed any pro's or con's. It sounded like bfgminer was getting better after update on able to use freq, but was not sure if worth trying.
I like that cgminer runs without errors, but I do not like having to use zadig.
I like the cgminer-gekko build, but since I can't compile and that build doesn't see my other usb sticks since it wasn't compiled with any other hardware options it's tough.
I like that bfgminer has the RPC option to mess with frequency while the stick is hashing.
I use them both on different computers. One of mine I cannot use zadig so that one gets bfg.
I plan to do a linux install eventually, I just don't have a lot of free time and that is pretty low on my priority list at the moment.
I get the same comms error, I've reported it in a few threads but never had any response as to what causes it or how to make it go away. I get the same error using my U3 with bfgminer on this same machine, so I think it may be hardware related and not actually have anything to do with bfg.
On this machine I currently have 2 gekko sticks and 2 nanofury usb sticks. I do not get comm errors with only the nanofury sticks, but once I plug in the compacs or the U3 the errors pop up. Since the compac used to be recognized as a U3 I think that's a hint as to where the issue is.
The good news is my devices seem to hash along just fine, despite the error. The only problem is that eventually, after 8-24 hours, the hash drops to almost nothing pool side while bfg still reports full hash speed. At that point I just restart bfgminer and unplug/replug the miners, that's the only work around I've managed to come up with.
Pool side reports a bit lower than bfg, probably a result of the comms error.
On this machine I currently have 2 gekko sticks and 2 nanofury usb sticks. I do not get comm errors with only the nanofury sticks, but once I plug in the compacs or the U3 the errors pop up. Since the compac used to be recognized as a U3 I think that's a hint as to where the issue is.
The good news is my devices seem to hash along just fine, despite the error. The only problem is that eventually, after 8-24 hours, the hash drops to almost nothing pool side while bfg still reports full hash speed. At that point I just restart bfgminer and unplug/replug the miners, that's the only work around I've managed to come up with.
Pool side reports a bit lower than bfg, probably a result of the comms error.
Yeah I went to another home of a forum member as I had promised to set up bfgminer with five sticks. It worked on his setup.
I was doing it on windows 7 but in a vm on a Mac. Thus the error.
I think it is because I recently upgraded the Mac os
What are your thoughts on bfgminer vs cgminer after trying both? I have been using cgminer as novak seemed to do a great one of it.
I was curious if you noticed any pro's or con's. It sounded like bfgminer was getting better after update on able to use freq, but was not sure if worth trying.
Okay when I set bfgminer up on a windows 7 at BuySolar's house it was a bit buggy but we got it to do 5 sticks at 60gh on bitminer.
It was okay.
Nothing compares to linux debian running cgminer I get 25 days of uptime or better close to prefect hw's.
I just need to spend time learning linux as it really seems to be good for these sticks.
I pulled the biggest stick share I have ever done today!
http://solo.ckpool.org/workers/1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.philipma1957sticks
"bestshare": 2,281,962,537.7536292
2 billion plus not bad!
Thanks for sharing comparison I was wondering how it works.
I have been using a RPI version b. It really does just work great. I have thought about uploading image but not sure if anyone would use it. I have it set up for icarus (reviewer and prototype compacs) and compac with cgminer. I run 2 instances of cgminer and it works very well. I love the setup.
I get the same comms error, I've reported it in a few threads but never had any response as to what causes it or how to make it go away. I get the same error using my U3 with bfgminer on this same machine, so I think it may be hardware related and not actually have anything to do with bfg.
On this machine I currently have 2 gekko sticks and 2 nanofury usb sticks. I do not get comm errors with only the nanofury sticks, but once I plug in the compacs or the U3 the errors pop up. Since the compac used to be recognized as a U3 I think that's a hint as to where the issue is.
The good news is my devices seem to hash along just fine, despite the error. The only problem is that eventually, after 8-24 hours, the hash drops to almost nothing pool side while bfg still reports full hash speed. At that point I just restart bfgminer and unplug/replug the miners, that's the only work around I've managed to come up with.
Pool side reports a bit lower than bfg, probably a result of the comms error.
On this machine I currently have 2 gekko sticks and 2 nanofury usb sticks. I do not get comm errors with only the nanofury sticks, but once I plug in the compacs or the U3 the errors pop up. Since the compac used to be recognized as a U3 I think that's a hint as to where the issue is.
The good news is my devices seem to hash along just fine, despite the error. The only problem is that eventually, after 8-24 hours, the hash drops to almost nothing pool side while bfg still reports full hash speed. At that point I just restart bfgminer and unplug/replug the miners, that's the only work around I've managed to come up with.
Pool side reports a bit lower than bfg, probably a result of the comms error.
Yeah I went to another home of a forum member as I had promised to set up bfgminer with five sticks. It worked on his setup.
I was doing it on windows 7 but in a vm on a Mac. Thus the error.
I think it is because I recently upgraded the Mac os
What are your thoughts on bfgminer vs cgminer after trying both? I have been using cgminer as novak seemed to do a great one of it.
I was curious if you noticed any pro's or con's. It sounded like bfgminer was getting better after update on able to use freq, but was not sure if worth trying.
Okay when I set bfgminer up on a windows 7 at BuySolar's house it was a bit buggy but we got it to do 5 sticks at 60gh on bitminer.
It was okay.
Nothing compares to linux debian running cgminer I get 25 days of uptime or better close to prefect hw's.
I just need to spend time learning linux as it really seems to be good for these sticks.
I pulled the biggest stick share I have ever done today!
http://solo.ckpool.org/workers/1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.philipma1957sticks
"bestshare": 2,281,962,537.7536292
2 billion plus not bad!
I get the same comms error, I've reported it in a few threads but never had any response as to what causes it or how to make it go away. I get the same error using my U3 with bfgminer on this same machine, so I think it may be hardware related and not actually have anything to do with bfg.
On this machine I currently have 2 gekko sticks and 2 nanofury usb sticks. I do not get comm errors with only the nanofury sticks, but once I plug in the compacs or the U3 the errors pop up. Since the compac used to be recognized as a U3 I think that's a hint as to where the issue is.
The good news is my devices seem to hash along just fine, despite the error. The only problem is that eventually, after 8-24 hours, the hash drops to almost nothing pool side while bfg still reports full hash speed. At that point I just restart bfgminer and unplug/replug the miners, that's the only work around I've managed to come up with.
Pool side reports a bit lower than bfg, probably a result of the comms error.
On this machine I currently have 2 gekko sticks and 2 nanofury usb sticks. I do not get comm errors with only the nanofury sticks, but once I plug in the compacs or the U3 the errors pop up. Since the compac used to be recognized as a U3 I think that's a hint as to where the issue is.
The good news is my devices seem to hash along just fine, despite the error. The only problem is that eventually, after 8-24 hours, the hash drops to almost nothing pool side while bfg still reports full hash speed. At that point I just restart bfgminer and unplug/replug the miners, that's the only work around I've managed to come up with.
Pool side reports a bit lower than bfg, probably a result of the comms error.
Yeah I went to another home of a forum member as I had promised to set up bfgminer with five sticks. It worked on his setup.
I was doing it on windows 7 but in a vm on a Mac. Thus the error.
I think it is because I recently upgraded the Mac os
What are your thoughts on bfgminer vs cgminer after trying both? I have been using cgminer as novak seemed to do a great one of it.
I was curious if you noticed any pro's or con's. It sounded like bfgminer was getting better after update on able to use freq, but was not sure if worth trying.
I get the same comms error, I've reported it in a few threads but never had any response as to what causes it or how to make it go away. I get the same error using my U3 with bfgminer on this same machine, so I think it may be hardware related and not actually have anything to do with bfg.
On this machine I currently have 2 gekko sticks and 2 nanofury usb sticks. I do not get comm errors with only the nanofury sticks, but once I plug in the compacs or the U3 the errors pop up. Since the compac used to be recognized as a U3 I think that's a hint as to where the issue is.
The good news is my devices seem to hash along just fine, despite the error. The only problem is that eventually, after 8-24 hours, the hash drops to almost nothing pool side while bfg still reports full hash speed. At that point I just restart bfgminer and unplug/replug the miners, that's the only work around I've managed to come up with.
Pool side reports a bit lower than bfg, probably a result of the comms error.
On this machine I currently have 2 gekko sticks and 2 nanofury usb sticks. I do not get comm errors with only the nanofury sticks, but once I plug in the compacs or the U3 the errors pop up. Since the compac used to be recognized as a U3 I think that's a hint as to where the issue is.
The good news is my devices seem to hash along just fine, despite the error. The only problem is that eventually, after 8-24 hours, the hash drops to almost nothing pool side while bfg still reports full hash speed. At that point I just restart bfgminer and unplug/replug the miners, that's the only work around I've managed to come up with.
Pool side reports a bit lower than bfg, probably a result of the comms error.
Yeah I went to another home of a forum member as I had promised to set up bfgminer with five sticks. It worked on his setup.
I was doing it on windows 7 but in a vm on a Mac. Thus the error.
I think it is because I recently upgraded the Mac os
Jump to: