[UNOFFICIAL] [VNL] Vanillacoin 0.4.1 | Instant ▱ Incentivized ▱ Innovative - page 262.

yudhistira

full member

Activity: 347

Merit: 100

2 R280x

Quote

setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1

sgminer.exe -k whirlpoolx -o stratum+tcp://vnl.suprnova.cc:1111 -u vanilla.1 -p x -w 64 -g 2 -X 4096 --no-submit-stale --gpu-powertune 20 --gpu-engine 1150 --gpu-memclock 1500 --lookup-gap 2 --expiry 1 --scan-time 1 --queue 0

first run stabil at 264 Mhs
hw: 0 R: 0 temp max: 80 c 3000 rpm

after a day

speed unstable 261-263
hw:0 R: to much max: 90 c 2500 rpm

something wrong with my gpu or this a bad network

jimlite

legendary

Activity: 1848

Merit: 1018

Also remove gpu platform.

Wolf0

member

Activity: 81

Merit: 1002

It was only the wind.

Pushed a compatibility fix to the miner - it now checks for the function clCreateCommandQueueWithProperties() if OpenCL is found, and if the function's there, it defines a macro I use to include or exclude the runtime check for OpenCL 2.0. This means executables linked against older SDKs that don't support OpenCL 2.0 won't have the runtime check either - lacking the support even if moved to a machine with the proper drivers and GPUs - but that should have been obvious anyway.

If you do link against an SDK with OpenCL 2.0 support, don't worry - on machines with older drivers lacking the support, the runtime check should fail, and the non-existant function will never be called.

Now somebody go test it with an older SDK. Works for the APP SDK 3.0 Beta - correctly detects that it is supported.

elpis

member

Activity: 64

Merit: 10

Quote from: groggin on March 26, 2015, 03:40:08 PM

Quote from: elpis on March 26, 2015, 03:37:52 PM

Does not work Auto-Switching Multi-Algorithm of sgminer (https://ottrbutt.com/sgminer/whirlpoolx/win64/wolf-sgminer-whirlpoolx-03222015-win64.zip). WhirlpoolX-perfectly. Others do not work? Undecided

nope - it's just for VNL Cool

Thank.

groggin

legendary

Activity: 1894

Merit: 1001

Quote from: elpis on March 26, 2015, 03:37:52 PM

Does not work Auto-Switching Multi-Algorithm of sgminer (https://ottrbutt.com/sgminer/whirlpoolx/win64/wolf-sgminer-whirlpoolx-03222015-win64.zip). WhirlpoolX-perfectly. Others do not work? Undecided

nope - it's just for VNL Cool

Wolf0

member

Activity: 81

Merit: 1002

It was only the wind.

Quote from: yudhistira on March 24, 2015, 11:35:00 PM

Quote from: Wolf0 on March 24, 2015, 07:45:25 PM

Quote from: Zuikkis on March 24, 2015, 05:16:08 PM

Quote from: pallas on March 24, 2015, 02:26:44 PM

Quote from: smolen on March 23, 2015, 07:40:27 AM

Quote from: pallas on March 23, 2015, 06:44:08 AM

there are at least a couple very low hanging fruits for us developers to enjoy, thanks wolf0 for helping preserve the specie ;-)

Tsss! Don't tell anyone about prepatched kernels! Wink

I'm in the 600 Mh/s club: 621 on r9 290x@1100.
Now wolf0 will reply "I'm at 700+"... ;-)

My current results.

R9 290 @ 1000MHz: 547MH/s
R9 280x @ 1150MHz: 504MH/s
R9 270 @ 1123MHz: 309MH/s
7990 @ 1000MHz: 438MH/s (per GPU)

Just to brag a bit more, I actually had these already before Wolf's latest release.

I think the Hawaii would easily be 600+ with decent clocks..

You did. Because I gave you a hint, need I remind you? Wink

Hi guys would you like to share for me Wink

You have a bigger hint than the one I gave him - it's the code I released. I'm not in the habit of giving away answers; to learn, you have to find it yourself.

elpis

member

Activity: 64

Merit: 10

Wolf0 Does not work Auto-Switching Multi-Algorithm of sgminer (https://ottrbutt.com/sgminer/whirlpoolx/win64/wolf-sgminer-whirlpoolx-03222015-win64.zip). WhirlpoolX-perfectly. Others do not work? Undecided

traumschiff

legendary

Activity: 1498

Merit: 1001

180 BPM

Quote from: z0n0 on March 26, 2015, 03:21:57 PM

Quote from: traumschiff on March 26, 2015, 03:21:01 PM

Quote from: z0n0 on March 26, 2015, 03:03:55 PM

Now ~260 MH/s...Still way off from yours ~500 mh/s Roll Eyes

You won't get 500 mh/s with the public miner if you don't optimize it by yourself. That's his own private miner and you would know this if you would read back a few pages.

Oh I see

Thanks for info

Np, you can still play with -w and --xintensity to gain the maximum out of the current public miner. Currently I'm hashing with 123 MH/s with my 270x.

z0n0

legendary

Activity: 1274

Merit: 1006

Quote from: traumschiff on March 26, 2015, 03:21:01 PM

Quote from: z0n0 on March 26, 2015, 03:03:55 PM

Now ~260 MH/s...Still way off from yours ~500 mh/s Roll Eyes

You won't get 500 mh/s with the public miner if you don't optimize it by yourself. That's his own private miner and you would know this if you would read back a few pages.

Oh I see

Thanks for info

Wolf0

member

Activity: 81

Merit: 1002

It was only the wind.

Quote from: shojayxt on March 24, 2015, 10:21:28 PM

Quote from: jimlite on March 24, 2015, 09:57:43 PM

Quote from: shojayxt on March 24, 2015, 09:43:42 PM

I'm trying to figure out what the purpose of this coin is besides a miner optimization competition but that's all there is for the last twenty pages.

What's the point?

Have you not read about the instant transfers, most secure/anon coin ever invented, lightweight full node staking on mobile phones?
This is just the beginning, what more would you like?

This whitepaper http://vanillacoin.net/papers/vanillacoin.pdf ? Yes I read it there isn't much there.

IMO, I'm just happy it was actually coded from scratch. 99.99% of the coins around here not only have zero purpose whatsoever, they're created and maintained by people who are not only not coders, they're computer-stupid.

Whether or not he has a plan for this coin, at least the dude has a skill.

traumschiff

legendary

Activity: 1498

Merit: 1001

180 BPM

Quote from: z0n0 on March 26, 2015, 03:03:55 PM

Now ~260 MH/s...Still way off from yours ~500 mh/s Roll Eyes

You won't get 500 mh/s with the public miner if you don't optimize it by yourself. That's his own private miner and you would know this if you would read back a few pages.

z0n0

legendary

Activity: 1274

Merit: 1006

Quote from: Wolf0 on March 26, 2015, 02:36:28 PM

Quote from: z0n0 on March 26, 2015, 02:18:53 PM

Quote from: Wolf0 on March 26, 2015, 02:05:05 PM

Quote from: z0n0 on March 26, 2015, 02:02:54 PM

Quote from: Wolf0 on March 26, 2015, 01:55:02 PM

Quote from: z0n0 on March 26, 2015, 01:48:07 PM

Da fuck am I doin wrong?

@echo off
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
sgminer.exe --algorithm whirlpoolx -o stratum+tcp://mine1.vnl.nonce-pool.com:4333 -u zono.zono -p abc -I 19 -g 2 -w 64 --gpu-platform 1 --no-submit-stale --failover-only

wolf0 is there some of your .bins out already?

~500+ MH/s > ~115 MH/s such a damn huge difference

HELP PLS!

Well, let's see. Not reading the README, using --no-submit-stale, not telling us your card type... am I close?

Close enough

I'm using 280X, "not reading README": guilty...

So I should remove "--no-submit-stale" ?

Of course. If I've said it once, I've said it a thousand times: SGMiner doesn't know if a share is stale. It GUESSES. You have nothing to lose by submitting it, and by not doing so, you won't get paid for it even if it is valid.

I wrote the README for a reason. Tongue

I'm really bad with understanding all these words, I'm mining for fun/hobby, if I'm honest I don't even know what "submitting stale" means

Just found out this:
Okay, it's not perfect, but it'll never be. Sources that I've written or modified have been heavily commented to help out devs who are learning. The OpenCL was entirely written by me, and SGMiner itself was modified by me not just to run the modified kernel, but to clean it, remove algorithms besides WhirlpoolX for simplicity, and add comments. The horrid lib SPH is no longer used at all, instead, a SHA-256 implementation that was actually already there and never even compiled is used for several parts of SGMiner that used to call into lib SPH, and the CPU Whirlpool-512 implementation is a rather clean one I found here. That is also where I found seemingly the only copy of Whirlpool-512 done without tables, on which I based my bitsliced implementation. Another modification I made was to check the OpenCL version at runtime and use clCreateCommandQueueWithProperties() if the version is 2.0 or greater; it replaces clCreateCommandQueue(), and the latter is now deprecated and should not be used, but even the current official SGMiner isn't updated. Anyways, go look at the source for yourself. It will be here momentarily.

Screenshot of final hashrates, although you may find better configs (NSFW): https://ottrbutt.com/miner/whirlpoolxwolfpub-03222015.png

Win64 binaries have been made for release, of course. As you can verify on Bitcoin-OTC's database, my key ID is 0x88CBE71ADD5FB10F - check your GPG sigs. Statically compiled, linked against the beta version 3.0 of the AMD APP SDK, stripped, and signed. The cURL version used is a bit old, but it doesn't matter. ADL headers were whatever version I happened installed on my Linux machine - the headers themselves are portable, and the binary was cross-compiled. Archive contains the binary, the CL file, and a README.

https://ottrbutt.com/sgminer/whirlpoolx/win64/wolf-sgminer-whirlpoolx-03222015-win64.zip
https://ottrbutt.com/sgminer/whirlpoolx/win64/wolf-sgminer-whirlpoolx-03222015-win64.zip.sig

...which gives much better hashrate. I was using some "old" version

EDIT: Is this OK?
"sgminer.exe --kernel whirlpoolx -o stratum+tcp://mine1.vnl.nonce-pool.com:4333 -u zono.zono -p abc -I 19 -g 2 -w 64 --gpu-platform 1 --failover-only"
Should I add something more?

And you still haven't read it, because if you did, you would have known that -I 19 is way too low. Try --xintensity 2048.

Now ~260 MH/s...Still way off from yours ~500 mh/s Roll Eyes

Should I change -w 64 to -w 256?

With HD7850 I get 83 MH/s.

tccd

newbie

Activity: 51

Merit: 0

I think I got one low-hanging fruit but it was too obvious even for a person not involved in any kind of software development. I was doing 300MH/s with 290X@1000/1250 (15.3 beta) and now my hashrate is 316MH/s:

http://store.picbg.net/thumb/B9/34/368dc2228c7eb934.png

z0n0

legendary

Activity: 1274

Merit: 1006

Quote from: Wolf0 on March 26, 2015, 02:05:05 PM

Quote from: z0n0 on March 26, 2015, 02:02:54 PM

Quote from: Wolf0 on March 26, 2015, 01:55:02 PM

Quote from: z0n0 on March 26, 2015, 01:48:07 PM

Da fuck am I doin wrong?

@echo off
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
sgminer.exe --algorithm whirlpoolx -o stratum+tcp://mine1.vnl.nonce-pool.com:4333 -u zono.zono -p abc -I 19 -g 2 -w 64 --gpu-platform 1 --no-submit-stale --failover-only

wolf0 is there some of your .bins out already?

~500+ MH/s > ~115 MH/s such a damn huge difference

HELP PLS!

Well, let's see. Not reading the README, using --no-submit-stale, not telling us your card type... am I close?

Close enough

I'm using 280X, "not reading README": guilty...

So I should remove "--no-submit-stale" ?

Of course. If I've said it once, I've said it a thousand times: SGMiner doesn't know if a share is stale. It GUESSES. You have nothing to lose by submitting it, and by not doing so, you won't get paid for it even if it is valid.

I wrote the README for a reason. Tongue

I'm really bad with understanding all these words, I'm mining for fun/hobby, if I'm honest I don't even know what "submitting stale" means

Just found out this:
Okay, it's not perfect, but it'll never be. Sources that I've written or modified have been heavily commented to help out devs who are learning. The OpenCL was entirely written by me, and SGMiner itself was modified by me not just to run the modified kernel, but to clean it, remove algorithms besides WhirlpoolX for simplicity, and add comments. The horrid lib SPH is no longer used at all, instead, a SHA-256 implementation that was actually already there and never even compiled is used for several parts of SGMiner that used to call into lib SPH, and the CPU Whirlpool-512 implementation is a rather clean one I found here. That is also where I found seemingly the only copy of Whirlpool-512 done without tables, on which I based my bitsliced implementation. Another modification I made was to check the OpenCL version at runtime and use clCreateCommandQueueWithProperties() if the version is 2.0 or greater; it replaces clCreateCommandQueue(), and the latter is now deprecated and should not be used, but even the current official SGMiner isn't updated. Anyways, go look at the source for yourself. It will be here momentarily.

Screenshot of final hashrates, although you may find better configs (NSFW): https://ottrbutt.com/miner/whirlpoolxwolfpub-03222015.png

Win64 binaries have been made for release, of course. As you can verify on Bitcoin-OTC's database, my key ID is 0x88CBE71ADD5FB10F - check your GPG sigs. Statically compiled, linked against the beta version 3.0 of the AMD APP SDK, stripped, and signed. The cURL version used is a bit old, but it doesn't matter. ADL headers were whatever version I happened installed on my Linux machine - the headers themselves are portable, and the binary was cross-compiled. Archive contains the binary, the CL file, and a README.

https://ottrbutt.com/sgminer/whirlpoolx/win64/wolf-sgminer-whirlpoolx-03222015-win64.zip
https://ottrbutt.com/sgminer/whirlpoolx/win64/wolf-sgminer-whirlpoolx-03222015-win64.zip.sig

...which gives much better hashrate. I was using some "old" version

EDIT: Is this OK?
"sgminer.exe --kernel whirlpoolx -o stratum+tcp://mine1.vnl.nonce-pool.com:4333 -u zono.zono -p abc -I 19 -g 2 -w 64 --gpu-platform 1 --failover-only"
Should I add something more?

z0n0

legendary

Activity: 1274

Merit: 1006

Quote from: Wolf0 on March 26, 2015, 01:55:02 PM

Quote from: z0n0 on March 26, 2015, 01:48:07 PM

Da fuck am I doin wrong?

@echo off
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
sgminer.exe --algorithm whirlpoolx -o stratum+tcp://mine1.vnl.nonce-pool.com:4333 -u zono.zono -p abc -I 19 -g 2 -w 64 --gpu-platform 1 --no-submit-stale --failover-only

wolf0 is there some of your .bins out already?

~500+ MH/s > ~115 MH/s such a damn huge difference

HELP PLS!

Well, let's see. Not reading the README, using --no-submit-stale, not telling us your card type... am I close?

Close enough

I'm using 280X, "not reading README": guilty...

So I should remove "--no-submit-stale" ?

z0n0

legendary

Activity: 1274

Merit: 1006

Da fuck am I doin wrong?

@echo off
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
sgminer.exe --algorithm whirlpoolx -o stratum+tcp://mine1.vnl.nonce-pool.com:4333 -u zono.zono -p abc -I 19 -g 2 -w 64 --gpu-platform 1 --no-submit-stale --failover-only

wolf0 is there some of your .bins out already?

~500+ MH/s > ~115 MH/s such a damn huge difference

HELP PLS!

Wolf0

member

Activity: 81

Merit: 1002

It was only the wind.

Quote from: Zuikkis on March 24, 2015, 05:16:08 PM

Quote from: pallas on March 24, 2015, 02:26:44 PM

Quote from: smolen on March 23, 2015, 07:40:27 AM

Quote from: pallas on March 23, 2015, 06:44:08 AM

there are at least a couple very low hanging fruits for us developers to enjoy, thanks wolf0 for helping preserve the specie ;-)

Tsss! Don't tell anyone about prepatched kernels! Wink

I'm in the 600 Mh/s club: 621 on r9 290x@1100.
Now wolf0 will reply "I'm at 700+"... ;-)

My current results.

R9 290 @ 1000MHz: 547MH/s
R9 280x @ 1150MHz: 504MH/s
R9 270 @ 1123MHz: 309MH/s
7990 @ 1000MHz: 438MH/s (per GPU)

Just to brag a bit more, I actually had these already before Wolf's latest release.

I think the Hawaii would easily be 600+ with decent clocks..

You did. Because I gave you a hint, need I remind you? Wink

JuanHungLo

hero member

Activity: 935

Merit: 1001