Topic: [TUTORIAL] Solo Mining Litecoins Guide--Windows! - page 9. (Read 306141 times)

Just found two blocks in the span of an hour, right on C:

Use a real pool on failover-only, then quit your daemon (litecoin-qt.exe -server) and let your miner switch to the pool. Then let it grab a few shares, and verify that your pool is counting your shares, and that after 15 minutes, that your hashes match (or are close to matching).

Then you will know that your miner is running fine at least.  Then start your daemon, and see if your miner automatically switches to solo.

Also, I am either having a bit of bad luck, or the difficulty went up today.  Good luck.

24 hours and no blocks. :{  Is there any way to check if this is working okay?  I'm pulling 750w/hr at the wall so I don't want to waste power

Ya, I had found one this morning, but nothing all day.  Not bad though, another 2 blocks in 12 hours.  Just got to wait it out...probably back to my back luck phase, but who knows!

Ok, GL2U!

Hopefully, I left it mining overnight and I didn't find one yet, but I'm hopeful today I'll find one.  I remember soloing before with my CPU that sometimes you'd wait 24 hours for a block and then you'd find a streak of them in a few hour span.

Awesome.  My latest block was at 23 hours from previous block. I was pushing them pretty hard at 420kh/s earlier as we hardly use the computers on Sundays.  Yet about half an hour ago, one of my miners failed-over to pool 1 for about 20 minutes, yet my other miner was fine, and the daemon was fine.  I had to [q]uit cgminer and restart to get it to go back to solo. Weird.  But thank God I had a failer over, otherwise it would have been mining for nothing.


Cool. You should get one every 6 to 7 hours based on litecoinpool's calculator

just started soloing with 1650kh/s (3x 7950s), hopefully i'll get some blocks soon. thanks for the guide!

Finally found another one a little bit ago.  My speed currently is 480 khash/s on this 6950, but at night when it is cooler I can push it to 530 khash/s.

Yeah, you were super duper lucky on that one.  What's your speed (again)?

Ya, mine looks mostly like yours.  It mostly says New block detected on network, but the occasional Rejected block.  I guess that is normal.  I didn't know about using a second pool for LP, so I will set that up and hopefully that will help.  Guess I am just having bad luck, guess that's what I get for solving 2 in the first 12 hours - made me think I should be seeing more.

ditch, are you solo mining? You should see "New block detected..." every 2 minutes or so, as well as any rejects.

Every now and then I get a reject.  I don't know exactly what that means, but it keeps going tho.  At my speed of 400kh/s, I am solving a block every 27 hours.  The highest intensity I put when computers are idle is 16. This makes the mouse dramatically slow, and I can't watch any videos. (I can on i12)

One thing that is helping me out is setting up a --failover-only with a second pool, a real pool that has long polling. That way cgminer gets the LP notification, and your litecoin daemon will benefit and switch to the new block faster than if you didn't have a second pool.

Can you post a screenshot of your cgminer?  Here's mine:



as you can see, i am "connected to http://192.168.1.27:9332" which is my other computer that is running the daemon.  If i were mining solo, I wouldn't have LP, but it's taking the LP data from my secondary pool (notroll.in) and using that. Notice I also have a rejected "share" there. That is NOT from the pool, as you can see it's "pool 0" which is Solo.

My batch file:

If you have a second pool with LP, instead of seeing "New Block Detected..." you see "LONGPOLL from pool 1 detected a new block" like you see in my screenshot.

BTW, those "accepted" shares you see there are because my solo computer rebooted automatically for windows updates. Luckily I am awake at 3 in the morning.  Strangely, I didn't get any rejects when it was mining for the pool, those 5 have been in the past 24 hours.

Still getting several "Rejected....." and still no accepted.  Can someone suggest what I can do to fix it?  Is there a way to reset something?  I don't know why it has stopped working.

So is 12.6 supposed to be the best for litecoin?  I am on 12.8 right now and it is working well, but looking for a way to add a few hashes.

I don't know how this guy is getting 522 kh/s out of his 6950 at those clocks.  I have the same settings, and unlocked shaders as well, but I have to run at 990 core at 1375 mem to get that speed.

https://github.com/litecoin-project/litecoin/wiki/Mining-hardware-comparison#wiki-ATI_AMD_GPUs

EDIT:

Seems like 12.6 did boost my khash/s a little.  I was around 522 at the above clocks after 10 minutes, and it has been 15 minutes on 12.6 with the above clocks and I am around 530 khash/s  

I solved 2 blocks in the first 12 hours of solomining LTC a couple days ago, but haven't got any thing else yet   , though yesterday I was out of town and I set I=20 before I left, so it crashed and didn't mine all day, but still!

And sometimes I see it says "Rejected  ............."  What does that mean?  Does it mean it solved a block, but someone else already submitted it or what?

Yes, my 6790 on intensity 12 is 137kH on average.  On I 16 it only adds 12kH. (my card has 800 shaders)

Perhaps I'll post mine soon, working on cutting it down to just a port-scanner for a competition (Not anything special, just checks what ports are open, but is customized for ease-of-use on my end)

Yeah, upgrading drivers helps solve a lot of problems, but also seems to decrease hash rate a few percent.

Did it ever go up to what you expected after an hour or so?

You wrote one? cool.  I found a suitable one, but I'd love to try yours out.

Anyhoo, I have solved the "missing" header problem.  I upgraded Catalyst 12.6 (from 11.12).

Now the hashes seem low, but I've heard that I need to give it time to show true kH rates.

I wrote my own port-scanning application.

Anywho, if it is listening, have you tried connecting another 3rd computer up? Does that run fine?

Yes, computers are on the same internal network.


I don't know how to do that. I just googled it, and downloaded 1 utility, but it doesn't seem to let me scan ports that I wanna scan (9332). I will continue to try other utilities, and update this post.  

But before then, how do YOU scan for open ports on an internal network?

EDIT: I found PortQry from Microsoft.  I was able to determine than TCP port 9332 on 192.168.1.27 is LISTENING.

Hmm... try downloading the latest ATI driver (12., and let me know if that works.