SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching

[doktor83]

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.

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%.

If I relaunch miner every hour, fees are 24 periods, right ?

you can relaunch it every 5 minutes, or 1 hour or 25 days, that is not my business how you use it I can't know for how long are you going to use the miner, so i can't predict what will the 0.85% be.
That is why there is a 24 hour period. And period.

[nordmann666]

tried new Algo CN Red today...works one hour but miner closed and now i get "EXCEPTION 90012. FAULTY HDMI DEVICE INT3H."

whats wrong?

[WhyMe]

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.

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%.

If I relaunch miner every hour, fees are 24 periods, right ?

you can relaunch it every 5 minutes, or 1 hour or 25 days, that is not my business how you use it I can't know for how long are you going to use the miner, so i can't predict what will the 0.85% be.
That is why there is a 24 hour period. And period.

Well, I'm dev too, but not at your level for sure.
But ( for exemple ) write in a file when miner starts/stops and fees periods, and check that at miner launch is not so complicated.

EDIT1 : I know you listen the community, may be this can be a feature in a future version !?
EDIT2 : We don't have information in log when switching on devfee ?

[doktor83]

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.

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%.

If I relaunch miner every hour, fees are 24 periods, right ?

you can relaunch it every 5 minutes, or 1 hour or 25 days, that is not my business how you use it I can't know for how long are you going to use the miner, so i can't predict what will the 0.85% be.
That is why there is a 24 hour period. And period.

Well, I'm dev too, but not at your level for sure.
But ( for exemple ) write in a file when miner starts/stops and fees periods, and check that at miner launch is not so complicated.

EDIT : I know you listen the community, may be this can be a feature in a future version !?

let me ask you something, and im done with the devfee chat.

When the first devfee out of 12 was after two hours, and you stopped/started the miner for example every hour, hour and a half. Sometimes maybe every 3 hours. It could happen that it never mined the devfee for 24h, or maybe 1-2-3 times for 24h. And that was ok for you. You got what you wanted, but i got maybe a 10th of the 0.85% devfee. That was fair and OK with you.
Now that i just reorganised the fee mining (so its still 0.85%), and this way im sure i get minimum the 1/13th of the 0.85% (wow, so much), suddenly that is a problem to you.

Don't you guys see how unfair you are?

I am not going to change the way the devfee is mined. If you can't settle with this, you are welcome to use the older versions where you can just skip the devfee mining part easily.

[WhyMe]

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.

2 of my rigs have started SRBMiner 55 and 59 times in last 24h ...

I'm not telling I don't wan't to pay your fees, I'm telling I want to pay 0.85% a day, not 0.85%/13 each time I launch miner.

Your job is great, your miner is the best on my cards, it makes me money, it's normal you have your fees. But not more than it's annonced.

[doktor83]

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.

[WhyMe]

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.

[doktor83]

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.

[heavyarms1912]

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.

[doktor83]

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.

[SpceGhst]

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.

[WhyMe]

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 ...

[Coinseeker18]

Hi, I have mining with adrenaline 18.5.1 driver version, is this ok? Because nanopool doesn't show the hashrate very acurate.

[abg00]

1.6.5 dont work on mox after devfee
need to restart miner

[RuMiner]

- Added driver version data to API

please add miner version to API output also

[doktor83]

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:

[hammuh]

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 . . .

[doktor83]

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

[hammuh]

Use kernel 2 set up gpus in gpu_conf, there is an example on the first page

Thanks. It works now.

[doktor83]

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.