Author

Topic: SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching - page 180. (Read 237247 times)

newbie
Activity: 1
Merit: 0
Is it ok not to switch in the latest version? I use 1.6.4, rx 580 8 gb. my cclock is 1200 and my mclock is 1900. intensity 58 worksize 8 threads 2. is my config ok guys for this version?
full member
Activity: 232
Merit: 100
Quote
GPU0: AMD Radeon R9 200 Series [Hawaii] [4096 MB][Intensity 236.0][W: 8][T: 1][K
: 1][BUS: 3]
GPU1: AMD Radeon (TM) R9 380 Series [Tonga] [4096 MB][Intensity 236.0][W: 8][T:
1][K: 1][BUS: 4]

---------------------------------------------------------
SRBMiner Cryptonight AMD GPU miner 1.6.5
DevFee only 0.85%
Press 's' to get some stats
Press 'h' to get some hashrate
Press 'r' to reload pools
Press 0-9 to disable/enable GPU while mining
Give it a few minutes to reach maximum hashrate
---------------------------------------------------------
Total pools: 1

Please wait...

Cryptonight LiteV7 mode enabled

[2018-08-04 02:01:34] Heating up system, please wait...
[2018-08-04 02:01:34] Compiling kernel for DEVICE BUS ID 3 ...
[2018-08-04 02:01:35] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram
 for DeviceID 0 (Thread 0)

Stopping miner...Uno momento
What is wrong kernel 2 is set?
... solved with newer driver but rig hangs badly on start, other miners working very bad (no 3d) so I am backing to my old driver.
newbie
Activity: 57
Merit: 0
I am bad at math and my mom told me not to listen to strangers, sorry.   Cry
Second is true, third is not, first says you know I am right (as I am quiet sure you are not bad at math).
hero member
Activity: 2548
Merit: 626
I am bad at math and my mom told me not to listen to strangers, sorry.   Cry
newbie
Activity: 57
Merit: 0
Interesting this words on devfee and restarting miner ...
I'm using also this method : switching my rigs on the best coin many times per hour/day. Not for not to pay fees but for mining coin with best profit at the moment.
So if fees are launched every time miner starts, fees are more than 0.85% ...
I will try to monitor that ...

I did not reinvent the wheel, every closed source miner that has a fee works this way. I don't understand what's all this wondering now, like you did not know how it works. Smiley

The rules are simple :

0.85% is the fee for 24hr mining.
That means 85660 sec mining for user and 740 sec for the devfee.
There are 13 devfee minings in 24 hours , so every mining period takes ~55-56 sec.

The first devfee of 13 total is in the first 15 minutes. If you kill the miner process and start it again, it will again mine the first fee of 13 total in the first 15 minutes.
So when you mined the first devfee its not 0.85% . 0.85% is 13xdevfee's.

So no, fee's aren't more than 0.85%.
To start, you are entitled to a fair fee. Also, you decide what is fair and if we don't like it we can stop using your miner. Which some of us will do, if they feel they are not treated fairly.
So, to check fairness I have made some calculations in Excel.
- when you mine exactly 24 hours, or 86400 seconds, you get 728 devfee seconds, which is 0,8426%, so a bit less than what Dok is saying in the post I quoted. Seems absolutely fair.
- when you stop just before the last devfee, you cheat it down to 0,7783%.
- however, when you stop just after a mining fee was done, let's say just after the 5th, it is 0,8854%
- and this is higher just after the 4th, 3rd, ... rising to a whopping 6,22% just after the 1st devfee which started this debate
So, what I did was average it all out. I assumed the 1st mining fee to be collected in the 15th minute, the second in the 120th minute and then every 120th minute.
When you assume that over all miners stopping in the first 24 hours, their is an even distribution (which I think it is not, I think it is weighted in the first half), the average fee collected then turns out to be 0,9365%. And that's more than 0,85% as promised.
When you look at miners that mine 12 hours or less, the average is even 1,07%.
To get the 24 hour average to 0,85%, mining fee should be 51 seconds and not 56, the average over 12 hours is then 0,93%. The only way to get that more equal is to do more frequent devfee mining, which would hurt us all.
All other options I can think of are difficult to implement
- centrally register start and end time of miners (put it on a blockchain  Grin)
- mine to a central wallet owned by Dok and get paid out the exact 99,15% of what is mined
So then Dok, would you consider it fair to lower the 56 seconds some more to get the average over 24 hours to the promised 0,85%?
hero member
Activity: 2548
Merit: 626

recheck again. work fine

other trouble. bad share on r9 290(x) card. kernel 2 too
Pool rejected result 0x0002013C (rejected share: invalid result)

algo mox ?
every share invalid?
pool?
jr. member
Activity: 288
Merit: 1
1.6.5 dont work on mox after devfee
need to restart miner

Give more info like logs and screenshots if you want help.

It's working here:



recheck again. work fine

other trouble. bad share on r9 290(x) card. kernel 2 too
Pool rejected result 0x0002013C (rejected share: invalid result)
hero member
Activity: 2548
Merit: 626
Quote
Use kernel 2 set up gpus in gpu_conf, there is an example on the first page

Thanks. It works now.


Next version willl auto select kernel2 for these cards, so you dont have to set it by hand. Smiley
jr. member
Activity: 41
Merit: 1
Quote
Use kernel 2 set up gpus in gpu_conf, there is an example on the first page

Thanks. It works now.
hero member
Activity: 2548
Merit: 626
I can't get the newest miner 1.6.5 to work. You can see the error below. Previous versions including 1.6.4 work fine.
I am using some older cards, Tahiti, and AMD driver 18.3.4.

GPU0: AMD Radeon R9 200 Series [Tahiti] [3072 MB][Intensity 27.0][W: 8][T: 2][K: 1][BUS: 1]
GPU1: AMD Radeon HD 7900 Series [Tahiti] [3072 MB][Intensity 38.0][W: 8][T: 2][K: 1][BUS: 2]

---------------------------------------------------------
SRBMiner Cryptonight AMD GPU miner 1.6.5
DevFee only 0.85%
Press 's' to get some stats
Press 'h' to get some hashrate
Press 'r' to reload pools
Press 0-9 to disable/enable GPU while mining
Give it a few minutes to reach maximum hashrate
---------------------------------------------------------
Total pools: 2

Please wait...

CryptonightV7 mode enabled

[2018-08-03 14:18:42] Heating up system, please wait...
[2018-08-03 14:18:42] Compiling kernel for DEVICE BUS ID 1 ...
[2018-08-03 14:18:42] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram for DeviceID 0 (Thread 0)

Stopping miner...Uno momento

Press any key to continue . . .

Use kernel 2 set up gpus in gpu_conf, there is an example on the first page
jr. member
Activity: 41
Merit: 1
I can't get the newest miner 1.6.5 to work. You can see the error below. Previous versions including 1.6.4 work fine.
I am using some older cards, Tahiti, and AMD driver 18.3.4.

GPU0: AMD Radeon R9 200 Series [Tahiti] [3072 MB][Intensity 27.0][W: 8][T: 2][K: 1][BUS: 1]
GPU1: AMD Radeon HD 7900 Series [Tahiti] [3072 MB][Intensity 38.0][W: 8][T: 2][K: 1][BUS: 2]

---------------------------------------------------------
SRBMiner Cryptonight AMD GPU miner 1.6.5
DevFee only 0.85%
Press 's' to get some stats
Press 'h' to get some hashrate
Press 'r' to reload pools
Press 0-9 to disable/enable GPU while mining
Give it a few minutes to reach maximum hashrate
---------------------------------------------------------
Total pools: 2

Please wait...

CryptonightV7 mode enabled

[2018-08-03 14:18:42] Heating up system, please wait...
[2018-08-03 14:18:42] Compiling kernel for DEVICE BUS ID 1 ...
[2018-08-03 14:18:42] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram for DeviceID 0 (Thread 0)

Stopping miner...Uno momento

Press any key to continue . . .
hero member
Activity: 2548
Merit: 626
1.6.5 dont work on mox after devfee
need to restart miner

Give more info like logs and screenshots if you want help.

It's working here:

member
Activity: 168
Merit: 15
- Added driver version data to API
please add miner version to API output also
jr. member
Activity: 288
Merit: 1
1.6.5 dont work on mox after devfee
need to restart miner
newbie
Activity: 22
Merit: 0
Hi, I have mining with adrenaline 18.5.1 driver version, is this ok? Because nanopool doesn't show the hashrate very acurate.
sr. member
Activity: 661
Merit: 250

You can't restart miner 24 times.  There is an overhead in getting the kernels loaded to GPU, connecting to pool, getting work and submitting result.

Dok changed the first mining fee session.  Unless people are using autoswitch algos/apis this shouldn't be problem (assuming you're not cheating the dev fee).

How about a random dev fee in first session? Is that difficult to implement as well. There are couple of miners that do that.

It's EXACTLY what my tools are doing since more than 2 years ...
jr. member
Activity: 269
Merit: 4
Come on guys... you’re arguing over pennies here.  SRB already has one of the lowest Dev fees around, and is the best CN mining program out there to me.  So, either live with the way the program works, or use a different program.
hero member
Activity: 2548
Merit: 626
For me, since begining, it was logic that fees was calculated for day period, not for "session" period. But it wasn't case.
I mean, if i launch miner 1 time for 24h or 24 times for 1h, fees have to be the same.

You as a developer should know there is no miner that works the way you described.
Name me just one that works this way.

I can believe a newbie thinks it works this way, but you are probably not fresh in the mining scene, so this is not the first miner you used.

You can't restart miner 24 times.  There is an overhead in getting the kernels loaded to GPU, connecting to pool, getting work and submitting result.

Dok changed the first mining fee session.  Unless people are using autoswitch algos/apis this shouldn't be problem (assuming you're not cheating the dev fee).

How about a random dev fee in first session? Is that difficult to implement as well. There are couple of miners that do that.

I could make that random but i know that still won't satisfy these guys, and it also increases the chance of loosing a devfee mining session.
full member
Activity: 729
Merit: 114
For me, since begining, it was logic that fees was calculated for day period, not for "session" period. But it wasn't case.
I mean, if i launch miner 1 time for 24h or 24 times for 1h, fees have to be the same.

You as a developer should know there is no miner that works the way you described.
Name me just one that works this way.

I can believe a newbie thinks it works this way, but you are probably not fresh in the mining scene, so this is not the first miner you used.

You can't restart miner 24 times.  There is an overhead in getting the kernels loaded to GPU, connecting to pool, getting work and submitting result.

Dok changed the first mining fee session.  Unless people are using autoswitch algos/apis this shouldn't be problem (assuming you're not cheating the dev fee).

How about a random dev fee in first session? Is that difficult to implement as well. There are couple of miners that do that.
hero member
Activity: 2548
Merit: 626
We don't have access to miner code, we finally don't know how fee works on each of them. And now I ask me.



you dont have to have access to code because you got info on the screen when the devfee is mined. You know exactly when and how long does it mine. Some miners dont show you even this.
Jump to: