Topic: Claymore XPM GPU Miner discussion (Read 142111 times)

HI ,i have 280x card.But i cannot mining,
Invalid share
Reason:Share failed

cmon Claymore you are due for another release please i'm sure we pay you enough

For anyone interested:
Primecoin [XPM] is being purchased here.

v12.0 is available:
https://bitcointalksearch.org/topic/claymores-xpm-primecoin-gpu-miner-v132-693680

Please use new thread to ask questions, I cannot maintain this thread because I'm not owner of original post.

Use Catalyst 13.12 for this miner.

Claymore there is strange thing - i use 14.4 drivers and mine on R9 290X and R9 270X. Instance of miner, running on 290x is ok, but instance on 270x print next:

and does not work on new version

I could get one of the cards (mentioned in quote) for cheap and i wanna know which is the best for mining.

Can someone explain me why a 0.5% increase in difficulty means almost a 30% decrease in coins mined?

...which is aprox 0. 

0 hash? Why? My CPU (G540) get 16 hash.

about 0 hash and a little more than 0 cpd if you were going to mine xpm

Is there anybody who knows how much hash can i get with an 5450 or an 6450 or an R7 240?

Not that I can offer any better but rots answer is technically a little confusing.  At some point, everyone that uses an ISP has a public IP address which they pay for usually on a leased time period basis.  The only exception could be if you had an ISP that used RFC 1918 IP addresses as their leased and managed IP addresses... which I can barely fathom... although I suppose it's possible.  But all you'd have to do to see your public/leased IP address which you get from your ISP is to open a command prompt and enter ipconfig /all to see all your IP info.  Looking at the "gateway" IP address will show you your public IP address which is what your home router (probably a WIFI capable router) will connect to.  The default IP address for your router is probably 192.168.1.1 and your host computer (and any other device on your home network) would be something like 192.168.1.X which is a standard Class C RFC 1918 private IP address.  This is commonly called NAT: Network Address Translation but should really be called PAT: Port Address Translation.  NAT is 1:1 translation of an internal RFC 1918 address to an external public IP address while PAT is many private addresses to 1 public IP address and it does this by tagging ports.

So now that you can see "port" address translation, the rest might make a little more sense as to why it works.

2ldr

So anyways, if you want to have more connections you can make sure some settings on your router are on... Such as port forwarding for just one rig or port triggering to make it effective in the entire network: it's TCP port 9911.  This way, all inbound traffic for port 9911 (XPM's port) will be accepted.  You can also make sure your firewall has a special rule to accept all the incoming traffic on TCP port 9911.

I did all of the above and never got over 8 connections but then again I didn't really watch that long.  The other thing I did since I have 2 rigs is setup a solo pool with one pool mining to rpc 127.0.0.1 and the other rig going to the 192.168.1.X address of the main rig.  After I did that, I finally saw more connections: as many as 12 to 14 connections which I thought was pretty cool.  And then I smiled.

But.. solo mining is random and scary.  I have no idea if it's better or worse than pool yet.  Only time will tell.  And I think it helps to have a lot of hash power too... so I'm trying to boost that up however I may.... Added a few more GPUs.  we'll see.  

glta

you need do nothing, if you have pubilc IP, incoming connections is automatic enable, if you has no public IP,
there's no way to allow incoming connections.

Readme file instructions .

 1) What is this ?
 2) How i put more connections ?
 3) guide me please . thx . 

I added mirror for files:
https://drive.google.com/folderview?id=0B69wv2iqszefRjNHVjdvMkF2VDA&usp=sharing

Unfortunately I cannot update OP.

Yes, of course

+ a little performance bump, right...

Claymore i'm having the same issue. after some ttime one of the gpus stops making shares. didnt happen in v10

Ok, I will implement it in next update, I'm already working on it. But if you have problems with GPUs probably you overclocked them too much.