It is simply impossible for two individuals doing programming to come up with the same acronyms for their user-exposed commands. Given that there's claims being made by claymore that his last non-protected compiled kernel has been ripped by this guy, and given the too-many 1:1 matching flags, specifically the ones related to kernel configurable options, I 100% believe what Claymore is saying and that this guys has ripped the kernel, which therefore has made him have to re-used the same flags, because he only has the decompiled assembler code of the kernel, which cannot be written back to its originating user-space language easily.

So a kind non-disrespectful (not) fuck you pajeet to you Phoenix.

v.10 sets correct clocks and voltage for wattman with the last two non-blockchain (drivers 2017.10.20 and the one from september), but then it throttles down upon full startup to 40% less GPU clock while keeping specified voltage values. Then upon exit, I can see in wattman the system maintains the correct OC values specified upon miner startup that the miner itself did not use.

All test were done by using all four specs for GPU and mem clocks+voltages due to mixed results in OCing without increased voltages being specified as noted in thread.

I have had no success in running stable the blockchain driver with and without any OC. The miner does start, I do see a north of ETH 5Mhs increases, but then it freezes my system. I've had very low li/lidag/ethi/dcri values with that driver and still the system keeps on crashing. Vega64 under windows obviously.

Thanks for all the great work, miner looks sweet!