I did have the chance to test it using a Telsa K20x and I got around 75 Khs.
Thanks. I tried on a GTX 970 and 750TI only running each by themselves. They ran but only HW errors. Also the scan time and expiry worked perfect, my rejects dropped significantly. |
|
|
|
|
Just curious if anyone has been able to get a Nvidia card working with the miner?
I kinda like how it is set up to be only able to mine with 1 card also.
|
|
|
|
|
With the new wallet 0.3.3 I get a lot of gpu throttling down due to the "Waiting for work from pool 0".
I did not notice that before.
And same as everyone else who has replied still get HW errors on any other cards that I try and mine. Even tried putting the wallet on another computer and solo into that with a different port and no go.
|
|
|
|
I am getting about 3 blocks rejected for everyone that I find on my 280x. Anyone else having this issue?
I also can only get my 280X to mine. My 270X will not mine just HW errors and my other pc with Nvidia cards also nothing but HW.
What settings you use for your 280x? I have my shades set to 2048 and shader mul set to 8. Right now I show 32 accepted and 96 rejected. I believe that cgminer info is incorrect right now so it is actually 16 found and 48 rejected. If you notice that cgminer accepted /rejected is always an even number. |
|
|
|
|
I am getting about 3 blocks rejected for everyone that I find on my 280x. Anyone else having this issue?
I also can only get my 280X to mine. My 270X will not mine just HW errors and my other pc with Nvidia cards also nothing but HW.
|
|
|
|
@ wr104
Can you tell me how I can find out to determine my threads per core? I tried to google but can't find the correct answer.
I might have got lucky on my 280x. It is up and running at 135 kh/s and finding blocks decently but I can't get my 270x going. I keep getting HW errors. From what I can determine I have 1280 shaders on the 270x.
The two most important parameters for the cgminer-khc are the 'shaders' and the 'shaders_mul'. The former is straightforward. If you GPU has 2048 Stream Processors then, you need to use '--shaders 2048'. The latter is a bit more complicated to as it depends on the GPU architecture and how much memory you have in your video card. Unfortunately, the best value for 'shaders_mul' must be found through trial and error. That said, with all the video cards that I tested, I found that the best value for 'shaders_mul' was always 8. But, your mileage may vary, if you know what I'm saying. When I developed the kshake320 opencl kernel and I was testing it using CodeXL, I did find somewhere a good explanation on how to best determine the number of threads per Stream Processor. I'll try to find it. Thanks for the reply. I am also guessing that cgminer shows 2 blocks for every 1 block found because of the block reward plus the random coins in there? Cgminer shows 30 blocks and the wallet 15 blocks. If I am correct you might want to add something in the OP so you don't get tons of questions about that. I seen someone has already questioned it. EDIT: I like this coin. thanks |
|
|
|
Edit the kryptohash.conf file and ensure the following parameters are uncommented: - server=1
- rpcuser={RPC_username}
- rpcpassword={RPC_password}
- rpcport=38912
- rpcconnect=127.0.0.1
Ah! I'm so confused! I DO NOT HAVE A KRYPTOHASH.CONF ANYWHERE AFTER **FIRST** INSTALL. This conf is for the cgminer-khc, correct? Or is it for the wallet? Do I need to make one? Where do I put it? Where should it be if I already have it? Right now I have a PiMP/cgminer-khc pointed here: /opt/ifmi/cgminer.khc.conf { "pools": [ { "url": " http://127.0.0.1:38912", "user": "truckfarmer", "pass": "x", "profile": "khc" } ], "profiles": [ { "name": "khc", "algorithm": "kryptohash", Yes you have to make your config file and place it in the KryptoHash appdata folder. |
|
|
|
|
@ wr104
Can you tell me how I can find out to determine my threads per core? I tried to google but can't find the correct answer.
I might have got lucky on my 280x. It is up and running at 135 kh/s and finding blocks decently but I can't get my 270x going. I keep getting HW errors. From what I can determine I have 1280 shaders on the 270x.
|
|
|
|
Compiling the wallet on OS X & Linux, at ./configure I get an error: checking whether byte ordering is bigendian... yes
configure: error: "Big Endian not supported" antonio, can you post your kryptohash.conf for the 280x please?! thank you!!! *Disclaimer* My config file is not the safest way to solo mine. I solo mine from 3 computers into the same wallet. Use this setup at your own risk. I would recommend to use the config in the OP. rpcuser=YOURUSERNAMEHERE rpcpassword=YOURPASSWORDHERE rpcallowip=* rpcport=38912 listen=1 daemon=1 server=1 |
|
|
|
|
Are stream processors the same as shaders on AMD cards?
Up and running finally on 280x and finding blocks.
Now just gotta get 750ti and 970 going (also 270x, having issues now).
|
|
|
|
Asking serious question so if taken wrong please don't respond.
Has this coin been abandoned by the dev?
Just curious because for me the 1.5 version of wallet is still buggy as hell. Can't do nothing without it going into "(Not Responding)" anytime I click on anything. Takes forever to load and about 20 minutes just to get it to start staking because of it freezing up so much.
Does the 1.4.1 version still work or is that one on the wrong blockchain if I try and use it?
Thanks.
Read the changelog.. if there was a fork between versions you have to use the newer version.. see what i mean ? And the feedback about CPU wallet usage is interesting guys (assuming you are all staking ? if your posting your usage percentage) I may be wrong but I only seen that 1.4.1 was a required upgrade but not the 1.5. That is why I wanted to make sure before trying out that version again. I didn't read that 1.5 was mandatory but maybe someone might still be using that version and weighed in. Just being cautious. |
|
|
|
the latest wallet uses 1 core for 100% almost all the time, so it depends how many cores you have.
for 8 core CPU it is like 13%.
do not know what the wallet is counting all the time.
I have a six core AMD 1100t. It usually uses about 6-13% on each core at any given time. you need to set the CPU affinity for JPC wallet to only one core, then you see the real workload. Is that through one of the tabs to do that or do have to use the console.? |
|
|
|
the latest wallet uses 1 core for 100% almost all the time, so it depends how many cores you have.
for 8 core CPU it is like 13%.
do not know what the wallet is counting all the time.
I have a six core AMD 1100t. It usually uses about 6-13% on each core at any given time. |
|
|
|
Asking serious question so if taken wrong please don't respond.
Has this coin been abandoned by the dev?
Just curious because for me the 1.5 version of wallet is still buggy as hell. Can't do nothing without it going into "(Not Responding)" anytime I click on anything. Takes forever to load and about 20 minutes just to get it to start staking because of it freezing up so much.
Does the 1.4.1 version still work or is that one on the wrong blockchain if I try and use it?
Thanks.
If I'm not mistaken, the dev(s) is(are) Korean. The community is definitely less active here. Might be more so on other languages forums. For some speculation, I notice the rich lists are still very fat at the top so one could assume there is a future in it. Usually there is an "abandon ship" mentality when a coin is dying. Me personally, I'm holding my modest couple million and staking regularly. I've got a hunch we'll see something later. Of course there's always a chance that as BTC becomes more widely known and used it actually makes alt coins less relevant rather than more. P.S. what kind of bugs are you experiencing? Thanks for the reply. Main problem is the wallet becoming unresponsive everything I click on something. For instance if I want to check the transaction tab it goes into "Not Resposive" up in the top left corner and takes minutes, sometimes up to 10 minutes to get going. It does this every time I click on a tab. I am not cpu mining anything else and I know the wallet uses some of the cpu to stake. I don't have this issue with any other wallets that I run and have staking. I knew the DEV said something about 1.6 would solve some issues but that seems like ages ago. |
|
|
|
|
Asking serious question so if taken wrong please don't respond.
Has this coin been abandoned by the dev?
Just curious because for me the 1.5 version of wallet is still buggy as hell. Can't do nothing without it going into "(Not Responding)" anytime I click on anything. Takes forever to load and about 20 minutes just to get it to start staking because of it freezing up so much.
Does the 1.4.1 version still work or is that one on the wrong blockchain if I try and use it?
Thanks.
|
|
|
|
|
@ iGotSpots
This has probably been answered a million times but I just actually seen this in my wallet.
When my set number of coins stake they "disappear" instead of going into the stake column as other wallets do. Here is the example that happened. I am a small timer compared to everyone else but I had 7,788 coins right before a stake. I notice that I had a stake for 345 coins waiting to mature but the Balance was 6,575 and the Stake was at 0. The Stake should have shown the 1,213 coins that was Staking to get the 345.
In the end everything is fine but not sure if this "glitch" can be fixed in the next wallet update to ease some of the confusion. I wasn't too worried at all since I knew the coins was actually staking and my correct balance would show up after that.
|
|
|
|
Is there a qt wallet for windows? i don't like exe wallets. Not sure how to make a exe into a qt either.
Hi, the exe wallet is an auto installer for easy use for new crypto users, it will install for you the qt in c:/programfiles/pimpcash. If you would like the qt just in zip file to unzip wherever you want you can download the zip package PIMP Windows Download + pimpcash.conf (zip) Windows Wallet InstallerThanks |
|
|
|
|
Is there a qt wallet for windows? i don't like exe wallets. Not sure how to make a exe into a qt either.
|
|
|
|
If you are on Windows. Go to the computer with wallet and open the command window and type ipconfig then look for your IPv4 Address. Make sure you use that ip address in your bat on the non wallet computer. Example. If wallet computer ipv4 address is 192.192.1.921 your bat should look something like this: spreadminer -o http://192.192.1.921:41667 -u USERNAME -p PASSWORD I also use rpcport=41667 in my config file. If you change anything in your confige file you must restart the wallet. NOTE: I am a rookie compared to tsiv but this is how I solo mine from multiple computers to the main with the wallet. I have other steps that I must do but they are not the most secure way that I have read about how I do it but it works fine for me. Been mining at time a total of 3 computers into the one with the wallet. Running JSON RPC over internet is insecure. It allows any intermediate node to intercept your communications (including your RPC password). This is especially dangerous if you are mining on unlocked wallet because it would allow to steal your coins. This article describes how to use secure RPC connections: https://en.bitcoin.it/wiki/Enabling_SSL_on_original_client_daemonOf course you can instead assume that your internet provider is not interested in stealing your information as well as anyone else who has access to your traffic (NSA maybe). Thanks for the link. I'll try and make sence of that. I know I am running very insecure that is why i put that Note in there for him to read. But curious question if you can answer, kinda off topic, Wouldn't my router block all incoming traffic? I have all my wallets running on wireless rigs. I am not concerned about my IP provider or even the NSA,if the NSA wnats something from me I am pretty sure they can get it with my limited knowledge in computer programming and all. Thanks |
|
|
|
thank you  And how would i send my hash to the same wallet from my 2nd computer through the internet ? Here is how: Also you can mine to a specific address (this is useful if you are mining on several computers). To do so: 1. Use existing or better generate a new address. 2. Open debug console (Tools -> Debug Console) and enter: dumpprivkey SYourSpreadCoinAddress 3. You will get your private key. Then open spreadcoin.conf or create it if it doesn't exist (D:\Users\<username>\AppData\Roaming\SpreadCoin\spreadcoin.conf on Windows) and add the following line: miningprivkey=YourPrivateKey 4. Restart your wallet if it was running. In the Mining tab you will now see notification that all mined coins will go to this address. Of course you need to generate address and get privkey on one computer and edit spreadcoin.conf on the other. What is the difference between mining in one wallet with privatekey with several computers and mining with a more wallets especially? the wallet uses electricity = $ This part confuses me - I need to open my wallet on the second computer in order to solo mine. If I don't open the wallet I get json errors. Does the wallet have to be open on both rigs in order to solo mine? And at this point aren't I still burning electricity? You only need one wallet running. On the computer running the wallet you point your miner to 127.0.0.1 and on the other computer you point it to the computer that's running the wallet. Computer 1, with wallet: miner.exe -o 127.0.0.1:41677 Computer 2: miner.exe -o ip.of.wallet.computer:41677 Don't put gen=1 into the conf, that makes the wallet run the internal CPU miner and that's a waste of electricity at these network hash rates. Something like this would do the trick, add the miningprivkey parameter if you want, personally I don't use it. server=1
rpcallowip=127.0.0.1
rpcallowip=192.168.1.*
rpcuser=yourrpcusername
rpcpassword=yourrpcpassword
The first rpcallowip allows RPC connections from the same computer that is running the wallet. The second rpcallowip is needed to allow connections from the other computer, change the IP to whatever your local network is. Or you can run the wallet on both computer, as long as you don't use gen=1 it doesn't really hurt but you'll have to deal with having two separate wallets and moving coins from them separately. Ok - so just to confirm - I do not need my wallet running on the second machine to get it to mine? I will try this setup and see if it works - thank you. Edit - ok I tried it without the wallet on the second machine running and it gets the json error when I open the miner. I must be missing something? If you are on Windows. Go to the computer with wallet and open the command window and type ipconfig then look for your IPv4 Address. Make sure you use that ip address in your bat on the non wallet computer. Example. If wallet computer ipv4 address is 192.192.1.921 your bat should look something like this: spreadminer -o http://192.192.1.921:41667 -u USERNAME -p PASSWORD I also use rpcport=41667 in my config file. If you change anything in your confige file you must restart the wallet. NOTE: I am a rookie compared to tsiv but this is how I solo mine from multiple computers to the main with the wallet. I have other steps that I must do but they are not the most secure way that I have read about how I do it but it works fine for me. Been mining at time a total of 3 computers into the one with the wallet. |
|
|
|
|
Show Posts
