Pages:
Author

Topic: [ANN] Kryptohash | Brand new PoW algo | 320bit hash | ed25519 | PID algo for dif - page 68. (Read 149459 times)

newbie
Activity: 24
Merit: 0
Interesting, got two 280x on Win7x64 w/14.9 drivers.  Getting about 147k on each card but nothing ever found on card #2, only HW errors?

Swap back over to known good sgminer cfg for DRK and bam, GPU 1 working solid.  Latest gpu support was for cgminer 3.7.2 and this ver is 3.7.5.  Anyone have any ideas?

Im getting the same thing with 290s(non x) all the accepteds show up on card 0, card 1,2 and 3 only get HW errors. Win 7 64 with 14.6 amd drivers.
newbie
Activity: 27
Merit: 0
Is this Windows or Linux? A "sample" kryptohash.conf file should be included with the Windows installer.

I've tried installing the wallet on (debian-based, PiMP) Linux & Mac. On both machines, I get a "bigendian" error when configuring. So I have the miner installed (and not yet working) with no wallet to mine towards.

I posted the exact "bigendian" ./configure error on page 4 or 5
sr. member
Activity: 350
Merit: 250
Interesting, got two 280x on Win7x64 w/14.9 drivers.  Getting about 147k on each card but nothing ever found on card #2, only HW errors?

Swap back over to known good sgminer cfg for DRK and bam, GPU 1 working solid.  Latest gpu support was for cgminer 3.7.2 and this ver is 3.7.5.  Anyone have any ideas?
member
Activity: 87
Merit: 10
MY kryptohash.conf

rpcuser=a3860903.1
rpcpassword=x
rpcallowip=127.0.0.1
rpcport=38912
listen=1
daemon=1
server=1

BAT
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
cgminer.exe --kryptohash -o 127.0.0.1:38912 -u a3860903.1 -p x --shaders 1024 --shaders-mul 8



Pool 0 slow/down or URL or credentials invalid
full member
Activity: 154
Merit: 100
why cgminer still pool 0 slow/down?

That's what i'm getting still...

same here... Huh

Go to the Debug console and type: getwork

What do you get?
+1



{
"data" : "010000000000000045169a200616cc763b3f9de957df29b906201a6ac585d6d0aa8fff11b62f05a 6a831b9f039000000a83b541f198ccc1a07e72c5619b1e8fa7473451ef4a120884f73c327086388 ca916fd37797896a172541480f4a010000000000000000000000000000ffff0026b640000000000 0000000000000000000",
"target" : "0000000000000000000000000000000000000000000000000000000000000000000000ffff00000 0"
}


Ok, now do the same but, with the kryptohash-cli.exe that is included in the daemon folder

From the Command Prompt type:  kryptohash-cli getwork



kryptohash-cli.exe its close it self after i click it

Don't click on it.  Open the Command Prompt, navigate to the folder where kryptohash-cli.exe is located and type:

kryptohash-cli getinfo
kryptohash-cli getwork

D:\Kryptohash Core 64-bit\daemon>kryptohash-cli getinfo
error: You must set rpcpassword= in the configuration file:
C:\Users\Administrator\AppData\Roaming\Kryptohash\kryptohash.conf
If the file does not exist, create it with owner-readable-only file permissions.


D:\Kryptohash Core 64-bit\daemon>kryptohash-cli getwork
error: You must set rpcpassword= in the configuration file:
C:\Users\Administrator\AppData\Roaming\Kryptohash\kryptohash.conf
If the file does not exist, create it with owner-readable-only file permissions.

make a file at C:\Users\Administrator\AppData\Roaming\Kryptohash
name it kryptohash.conf  
put this :
rpcuser=yourusername
rpcpassword=password
server=1
member
Activity: 87
Merit: 10
why cgminer still pool 0 slow/down?

That's what i'm getting still...

same here... Huh

Go to the Debug console and type: getwork

What do you get?
+1



{
"data" : "010000000000000045169a200616cc763b3f9de957df29b906201a6ac585d6d0aa8fff11b62f05a 6a831b9f039000000a83b541f198ccc1a07e72c5619b1e8fa7473451ef4a120884f73c327086388 ca916fd37797896a172541480f4a010000000000000000000000000000ffff0026b640000000000 0000000000000000000",
"target" : "0000000000000000000000000000000000000000000000000000000000000000000000ffff00000 0"
}


Ok, now do the same but, with the kryptohash-cli.exe that is included in the daemon folder

From the Command Prompt type:  kryptohash-cli getwork



kryptohash-cli.exe its close it self after i click it

Don't click on it.  Open the Command Prompt, navigate to the folder where kryptohash-cli.exe is located and type:

kryptohash-cli getinfo
kryptohash-cli getwork

D:\Kryptohash Core 64-bit\daemon>kryptohash-cli getinfo
error: You must set rpcpassword= in the configuration file:
C:\Users\Administrator\AppData\Roaming\Kryptohash\kryptohash.conf
If the file does not exist, create it with owner-readable-only file permissions.


D:\Kryptohash Core 64-bit\daemon>kryptohash-cli getwork
error: You must set rpcpassword= in the configuration file:
C:\Users\Administrator\AppData\Roaming\Kryptohash\kryptohash.conf
If the file does not exist, create it with owner-readable-only file permissions.
full member
Activity: 210
Merit: 100
ActionCrypto.com ★ Bitcoin Binary Options
Sounds cool!

best of luck  Wink
full member
Activity: 196
Merit: 100
why cgminer still pool 0 slow/down?

That's what i'm getting still...

same here... Huh

Go to the Debug console and type: getwork

What do you get?
+1



{
"data" : "010000000000000045169a200616cc763b3f9de957df29b906201a6ac585d6d0aa8fff11b62f05a 6a831b9f039000000a83b541f198ccc1a07e72c5619b1e8fa7473451ef4a120884f73c327086388 ca916fd37797896a172541480f4a010000000000000000000000000000ffff0026b640000000000 0000000000000000000",
"target" : "0000000000000000000000000000000000000000000000000000000000000000000000ffff00000 0"
}


Ok, now do the same but, with the kryptohash-cli.exe that is included in the daemon folder

From the Command Prompt type:  kryptohash-cli getwork



kryptohash-cli.exe its close it self after i click it

Don't click on it.  Open the Command Prompt, navigate to the folder where kryptohash-cli.exe is located and type:

kryptohash-cli getinfo
kryptohash-cli getwork



thank you fixed and running now
Development can solve a machine can only run a graphics card problem?
sr. member
Activity: 329
Merit: 250
Have multiple rigs with 290s and get nothing but HW errors.

Tried all combos of --shaders  2816, 2048, 1792 --shaders-mul 8 or 10 or 6 or 4 or 2

any suggestions?





I would need to see the cgminer debug output.  Are those R9 290 or R9 290x?  The former has 2560 Stream Processors, the latter 2816 Stream Processors.

To obtain cgminer debug output:

cgminer.exe --debug --kryptohash -o 127.0.0.1:38912 -u {YourRPC_username} -p {Your_RPC_password} --shaders 2560 --shaders-mul 8  2>logfile.txt

Then, PM me that logfile.txt file
full member
Activity: 154
Merit: 100
why cgminer still pool 0 slow/down?

That's what i'm getting still...

same here... Huh

Go to the Debug console and type: getwork

What do you get?
+1



{
"data" : "010000000000000045169a200616cc763b3f9de957df29b906201a6ac585d6d0aa8fff11b62f05a 6a831b9f039000000a83b541f198ccc1a07e72c5619b1e8fa7473451ef4a120884f73c327086388 ca916fd37797896a172541480f4a010000000000000000000000000000ffff0026b640000000000 0000000000000000000",
"target" : "0000000000000000000000000000000000000000000000000000000000000000000000ffff00000 0"
}


Ok, now do the same but, with the kryptohash-cli.exe that is included in the daemon folder

From the Command Prompt type:  kryptohash-cli getwork



kryptohash-cli.exe its close it self after i click it

Don't click on it.  Open the Command Prompt, navigate to the folder where kryptohash-cli.exe is located and type:

kryptohash-cli getinfo
kryptohash-cli getwork



thank you fixed and running now
sr. member
Activity: 329
Merit: 250
@ 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


Thanks for bringing this to my attention.  I'll investigate.

Edit: this limit of 1 forum posting every 5 mins is getting old really fast.  Undecided

newbie
Activity: 24
Merit: 0
Have multiple rigs with 290s and get nothing but HW errors.

Tried all combos of --shaders  2816, 2048, 1792 --shaders-mul 8 or 10 or 6 or 4 or 2

any suggestions?



sr. member
Activity: 329
Merit: 250
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 to a conf I made here: /opt/ifmi/cgminer.khc.conf

Quote from: Beginning of cgminer.khc.conf
{
  "pools": [
    {
      "url": "http://127.0.0.1:38912",
      "user": "truckfarmer",
      "pass": "x",
      "profile": "khc"
    }
  ],
  "profiles": [
    {
      "name": "khc",
      "algorithm": "kryptohash",

Is this Windows or Linux?
A "sample" kryptohash.conf file should be included with the Windows installer.  If you can't find one, create your own kryptohash.conf file using a text editor, add the below parameters and save it to the roaming folder  C:\Users\{Your_User}\AppData\Roaming\Kryptohash\  or to the folder you specified when you executed Kryptohash-Qt.exe for the first time.

kryptohash.conf

region=0
addnode=104.131.54.248
addnode=178.62.96.79
server=1
rpcuser={Your_RPC_Username}
rpcpassword={Your_RPC_Secret_Password}
rpcconnect=127.0.0.1         <-- Note that if you are running cgminer-khc on a different computer, you need to specify its IP address here.
keypool=100
paytxfee=0.0



full member
Activity: 196
Merit: 100
Sell some KHC, if you are interested,
Please make an offer, PM me, thank you!
1000 Cong sell?
sr. member
Activity: 490
Merit: 250
Sell some KHC, if you are interested,
Please make an offer, PM me, thank you!
legendary
Activity: 1400
Merit: 1000
@ 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
legendary
Activity: 1610
Merit: 1008
Forget-about-it
im not having luck on my 7950.  Rejects.. Ive dumbed down the shader-mul from 8 to 4 and still getting rejects.  
@ 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.



just solved one on -mul 10  so its anybodys guess. look forward to reading the explanation if you find it


*edit, awarded 6, 4 rejects. 3 awarded didnt show in wallet. 3 blocks solved..
sr. member
Activity: 329
Merit: 250
@ 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.

full member
Activity: 196
Merit: 100
A computer can only use a graphics card mining? I inserted the 6 card is only one card!!
legendary
Activity: 1610
Merit: 1008
Forget-about-it
im not having luck on my 7950.  Rejects.. Ive dumbed down the shader-mul from 8 to 4 and still getting rejects. 
Pages:
Jump to: