Quote from: massnerder on August 31, 2013, 02:06:48 AM

Quote from: Asphyxiated on August 31, 2013, 01:48:40 AM

Quote from: massnerder on August 30, 2013, 07:46:20 PM

what exactly does the -g flag do? I can't seem to find it in the --help

again with your settings my display driver crashes, but if i set it to g1 then it goes just fine but only at about 550khash

with my settings g1/g2 didn't seem to make any difference (edit) before it didn't that is ... now with the 13.8 driver g1 crashes my setings, but g2 works

so for now with 13.8- your settings g1 works g2 crashes, my settings g1 crashes g2 works

The -g setting is how many gpu threads to start, if you have only 1 gpu then -g1 with a TC of 64 * bit-width (or slightly less for me) or -g 2 with TC of (64 * bit-wdith) / 2 should be used, if you have a 7990 then -g 2 would be best, there is probably better settings but if i got a 7990 i would first try -g 2 and --thread-concurrency 16384 (i think the bit-width of 7990 is 256, i could be wrong though).

so if i run it with g2 in the command line but i have gpu-threads 1 in my conf file, which one take priority?

i should probably go change that...

honestly I don't know but i would think that the command line args should supercede the config file args, at least thats how i would write it, so incase you forget you have something in config files you forgot about it would be overridden with whatever you have in command line as you must want that argument you set in the command line to be active since you typed it there while config files can be old...

but again just a guess.