Quote from: Astrali on November 05, 2018, 10:53:29 AM

Quote from: crypto_curious on November 05, 2018, 10:47:33 AM

lolMiner.... I think you could not figure out the worse name.

i like the name

As if anybody here give a shit about names xD So many strange names in crypto, but what is important is what is behind. Hands down - who did not raise an eyebrow hearing about the eth enlargement pill the first time Grin

Quote from: squeekie on November 05, 2018, 10:56:51 AM

My guess:

1080 --> 200
580 --> 120

Grin

Ok, noted

Quote from: catfish78 on November 05, 2018, 06:21:26 AM

My guess:

1080 ---> 202
580 ---> 123

Cheesy

Did you two talked about that before?

Quote from: baraday on November 04, 2018, 05:32:33 PM

I guess
1080 232 sol/s
580 143 sol/s.
Grin

At least one of us is optimistic Wink

Quote from: MaxMidnite on November 05, 2018, 09:34:39 AM

Hey man how do I enable logging on Alpha so I can paste you my results?

The only thing you need is an empty folder in your miner directory with name "logs". Then you can add the command line option --logs 1 to enable writing a log file. Or use "LOGS" : 1, in config file.

Quote from: Astrali on November 05, 2018, 12:00:09 AM

just cause the crash contained a line with "boost"

The boost lib is not the problem here. Thats just because if all cards fail the compatibility check there are a few values not written to an internal configuration table ... and this missing value is causing the bug. That will be fixed in alpha 3

So, from clinfo its indeed that your machine does not find the amdgpu-pro driver and uses the Clover platform only ... and this one does not like my kernel code (yet). I will have to set up a test machine on my own to see why this happens (or you manage to set up the pro-drivers ... lets see who succeeds earlier ^^)

Quote from: ivomm on November 05, 2018, 09:53:11 AM

My 390's rig crashes immediately (BTG 144/5). What is the reason? Is it because of the drivers? I am with crimson 17.7.1 (the last that are supported in windows 8.1).

Good question. I am also running that crimson drivers on my Windows test machine and its running fine there on my 580. Also on an earlier page we had reports about a 390 running well. So, atm no idea why, does this happen at older versions as well?
There are two things that may happen:
1) you run with too extreme OC / UV settings. I have once tried to run lolMiner with the ideal settings for mining eth... that try did not last long... equihash has more compute intense components that require a bit more clock and voltage.
2) One user this morning (in telegram) had the problem that his defender refused to unpack some parts of the .zip. As a result he was mixing and old .exe with new Kernel code. That results in a 0 sol/s immediately.

Hope one of the two answers help you - else this is going to be an interesting debug...