I find very telling that the only responses I got here were after I said I fixed it and to just talk shit, basically because I'm upset. Very helpful. How about pointing out some of those posts. No you just wait for a troll moment then pounce. THANK YOU
TROLLS
VERY HELPFUL
Says the person who wouldn't post how their problem was fixed. Isn't that telling as well? So you guys aren't willing to help me fix a problem on my one setup which is most likely different than every other setup because everyone's machine is different? Well... Screw you guys... I'm going home. What are you whining about? This conversation had nothing to do with you. Unless your the same person as GrapeApe using more than one account?!?!? |
|
|
|
I had the same problem but on a RaspberryPi. Try cgminer 3.1.1 and see if that helps.
Is that how you solved your problem? Treating each miner as a serial device uses more CPU horsepower. |
|
|
|
I think i should start by figuring out which method i should mine with. DGM, PPLNS, PPS, proportional. Any suggestions?
I will never do PPS again. It has caused serious damage to good pools and has caused some pools to go completely bankrupt. I like DGM on Ozcoin I seem to do really well with it. BTC Guild is a very good pool so I guess I don't mind PPLNS. There are threads on these forums that explain the theory of operation for these payout methods. Sam |
|
|
|
OK will try that. If anybody has some time to explain in simple terms for a nub that would be appreciated.
Also, does the size of the pool effect anything of just the features it offers?
Size of the pool only matters if the pool is very small. Medium sized to large pools will get you about the same payout over periods of time. Sam |
|
|
|
LOL thanks for suggestion. Hopefully i can get a few more opinions and maybe a quick education.
Just search the forums for those terms and you will get allot of information. There are threads dedicated to the payout systems if you want the technical info behind them. Sam |
|
|
|
I was looking at that post. I read the method description but i dont really understand it. I did not see a description for pay orphans, pay TX reward, variable difficulty, stratum, etc. Would like to understand the details at least a little bit.
Why ozcoin?
You asked for help picking so I gave you a pick.  Ozcoin does all of the things you don't yet understand. They are all good things for the miner. Sam |
|
|
|
So I got my first erupters today and spent about 2 hours trying to take the advice in a bunch of threads about settings them up with cgminer. Silly me tried to set them up with the latest version of cgminer 3.3.1. Since the -S command was removed a few versions ago it seems like you are now supposed to get a perfect install of the drivers and then it magically detects the USB devices on start up. But this didn't work for me, and others in some threads had problems with this too. So I followed this guide http://rdmsnippets.com/tag/install-block-erupter-on-windows-7/ to the letter and used the older 3.1.1 and it worked more or less perfectly. Not sure how support for the USB miners will progress with new versions of cgminer. I suppose its best to just leave it alone since it works. Also I used the D-Link DUB-H7 hub and it works flawlessly. Running of my netbook (~13 watts) which runs 24/7 anyway, seems like a good host. Unless you have USB 3.0 hubs, you should have just followed the simple paragraph in the ASIC readme file and installed the WinUSB driver with Zadig and associate your USB Erupter with the WinUSB driver. I did that and had my Erupters running in minutes and has been running flawlessly since with no command line arguments besides --usb ICA:3 since I'm running three instances of CGMiner with 3 Erupters per pool. Much simpler than mapping all of those serial ports and putting each port/miner in the command line. Sam ASIC-README.txt in version 3.1.1 only refers to BFL and Avalon devices. I had a look in it but figured it was not relevant at the time. The ASIC Readme in 3.3.1, you know the version you had trouble with because you didn't read the ASIC Readme nor the regular readme. Why read the ASIC Readme in the version you got working with the old command line arguments that you seem to be already familiar with? |
|
|
|
So I got my first erupters today and spent about 2 hours trying to take the advice in a bunch of threads about settings them up with cgminer. Silly me tried to set them up with the latest version of cgminer 3.3.1. Since the -S command was removed a few versions ago it seems like you are now supposed to get a perfect install of the drivers and then it magically detects the USB devices on start up. But this didn't work for me, and others in some threads had problems with this too. So I followed this guide http://rdmsnippets.com/tag/install-block-erupter-on-windows-7/ to the letter and used the older 3.1.1 and it worked more or less perfectly. Not sure how support for the USB miners will progress with new versions of cgminer. I suppose its best to just leave it alone since it works. Also I used the D-Link DUB-H7 hub and it works flawlessly. Running of my netbook (~13 watts) which runs 24/7 anyway, seems like a good host. Unless you have USB 3.0 hubs, you should have just followed the simple paragraph in the ASIC readme file and installed the WinUSB driver with Zadig and associate your USB Erupter with the WinUSB driver. I did that and had my Erupters running in minutes and has been running flawlessly since with no command line arguments besides --usb ICA:3 since I'm running three instances of CGMiner with 3 Erupters per pool. Much simpler than mapping all of those serial ports and putting each port/miner in the command line. Sam |
|
|
|
|
What is your command line?
What coin are you trying to mine?
What mining device are you trying to use?
What is the actual error message?
|
|
|
|
I look forward to seeing "Hi organofcorti, love and kisses, Tycho" in the coinbase this weekend.
Organofcorti, A little too revealing  You have a problem with coino-erotic love? Coinophobe! FACT: Most coinophobes are repressed coinosexuals themselves. I don't feel repressed. But I may be repressing the thought. |
|
|
|
"--usb bfl:1" is for the old FPGA Singles. For Jalapenos, you want "--usb baj:1".
I run two instances of CGMiner on one computer, where --usb bfl:1 points my FPGA to one pool, and another instnace with --usb bas:1 points my Single at another pool.
Actually, all BFL SC devices (jalanpenos, singles, etc) are "--usb bas:#". It's based on the driver (bas for the new sc driver, bfl for the old fpga driver). I found that this worked, with the device index starting at 1. Also, --usb x:y works, with x and y being the bus and device numbers for the miner as reported by lsusb. Now I can have my mining split between pools...just need for P2Pool to switch over to v13 now. I was using the Bus:Device at first too. But on reboot those assignments can change so switched my methodology to --usb ICA:3 for each instance. That way it doesn't matter which device it actually uses just grabs the first 3 available. Also you would use --usb BAS:1 in case you missed the posts correcting my mistake. Any way you want to do it, it does work great. Also the options are explained in the readme.txt under advanced usb options. Sam |
|
|
|
How difficult would it be to allow several instances of cgminer in the same system?
Easy, I run 3 to 5 instances with 3.3.1 I'm trying to run one instance on each of my Jalapeņos so I can have one mine on BTCGuild and the other on P2Pool. I'm trying to use something like this to launch two instances of cgminer: screen -dmS miner_0 cgminer --api-listen --api-allow W:127.0.0.1 --api-port 4028 --device 0 --remove-disabled --url stratum+tcp://stratum.btcguild.com:3333 --user ____ --pass ____
screen -dmS miner_1 cgminer --api-listen --api-allow W:127.0.0.1 --api-port 4029 --device 1 --remove-disabled --url stratum+tcp://salfter.gotdns.org:9332 --user ____ --pass ____
The first one starts properly and runs on just one Jalapeņo, but the other doesn't. Removing the screen invocation and adding --text-only produces this: [2013-07-09 10:02:34] Started cgminer 3.3.1
[2013-07-09 10:02:34] Loaded configuration file /home/salfter/.cgminer/cgminer.conf
[2013-07-09 10:02:34] SEM: BitForceSC USB failed to get (1409024) '/tmp/cgminer-usb-1-6' - device in use
[2013-07-09 10:02:34] SEM: BitForceSC USB failed to get (1441793) '/tmp/cgminer-usb-1-5' - device in use
[2013-07-09 10:02:34] Command line options set a device that doesn't exist
It says both are in use, even though only one is actually in use. Just use --usb bfl:1 for each instance |
|
|
|
I look forward to seeing "Hi organofcorti, love and kisses, Tycho" in the coinbase this weekend.
Organofcorti, A little too revealing |
|
|
|
How difficult would it be to allow several instances of cgminer in the same system?
Easy, I run 3 to 5 instances with 3.3.1 |
|
|
|
May be a long-term contender since it does useful work rather than just hashing.
So, uh, "just hashing" isn't "useful work"? |
|
|
|
Not so solved, when starting cgminer 5 or 6 are recognized almost immediately, the rest come in a few seconds later but the last few more often than not are not listed  anyone else have this problem ? I've found I have to run the zadig driver installer each time I start mining in Win7, like so: 1 - plug in erupters 2 - run zadig installer 3 - disconnect & reconnect erupters 4 - start cgminer That is just bizarre. I ran Zadig once and have not had to do it since. Per the ASIC readme 1. Unplug all Erupters 2. Run Zadig - Install WinUSB (I may have rebooted, can't remember for sure) - You cannot install WinUSB while Erupters are plugged in. 3. Plug in one Erupter, verify that it is set to WinUSB. 4. Close Zadig, plug in the rest of the Erupters, run CGMiner. Done Win7 32bit. I have not had to rerun Zadig since. And I have added Erupters since my initial install. Running 10 now. Sam |
|
|
|
Thanks!
So in my scenarios, I should be using Pool 1 since it has a much higher "U"? Any idea why it's so much higher?
The two different pools are using variable difficulty and they have different targets for that difficulty. Your WU:, aka Worker Utility, or diff 1 shares, is the same and the pools will convert your shares back to diff 1 to pay on. So both pools will pay on about the same number of shares. Sam |
|
|
|
Thank you for the link and for the considerate kind words.
Your quite welcome. I ask questions to get informed (and to be uplifted by human beings' kindness to each other when they answer questions).
Hmm, Your "question" seems much more of an accusation than an actual question. Also, I have not painted anybody with any brush, but simply asked a question about how transaction fees are hadled by pools.
You only asked how they were handled after you assumed that all pool ops kept them. The list the you linked to is comprehensive. Do you mean the answer lies in the "Pay TX Reward?" column.
Yes If yes, then it seems that the majority of the pools (and p2pool does not count as there is no operator) still keep transaction fees to themselves, so my encouragement for the pool operators to share those accumulated transaction fees still stands.
That's correct. Your "encouragement" sounds fair and reasonable to me. Also read the end of the Mining Pools List where a pool shares the transactions with the block finder. That sounds like a cool idea to me as well. Keep in mind that not all pools keep the information in that list up to date either so there may be more pools who share transaction fees too. And I'm sure as the fees become a higher percentage of income more will follow suit or go by the wayside. Keep up the kinder/gentler encouragement. Sam Edit: And I do apologize for my initial reply being more sarcastic than it needed to be. |
|
|
|
Maybe you should have looked at the Mining Pool List, URL below, and the top post in this forum sub group, before blathering on about something you really don't know what your talking about, not completely anyway. I don't mean to be a jerk here, well a little maybe, but you are painting the pool ops with a really broad brush unfairly and uninformed. Sam https://bitcointalk.org/index.php?topic=104664.msg1146108#msg1146108 |
|
|
|
|
Show Posts
