Posts made by cisahasa

Can he post a picture? Never saw 1100 GPU farm yet.

there is 2-4 of them… seen it

It seems to me that KNC is up to publishing firmware for their Titan miners. Someone is testing FTC on coinotron again.

tell me more what is happening?

noticed that sgminer will not support p2pools

but there is a easy way around that problem

point your miner to miningrigrental, set your price so high no one rents, then set up pool where your rig mines when its not rented(now any p2pool will work)

i tried raw + I 13+ w 64-256

have no time to play more now

first look for 280x only hw, hash down by 70%

will try later with better time

drivers: 14.200.1004.0

is there any use of this update for me, i have 280x?

i have my “tweak”, so im doing solo when needed with sg

also same issue when connecting p2pools with sg

becauce of rawintensity i would like to solo with sg 15% faster than cg

litebar moved on neoscrypt and they dont even care to release wallets…

private mining for now or compile your own.

stay out of those guys

i was trying to solo mine, found out wallet is out of date…

first wasted lot of time why miner will not work, it will not.

and just now im not interested compiling my own wallet

private mining goes on…

and sg miner 5.1 has some issues when solo! why need to use proxy? solo prevented?

as wolf said, i hate when my miner is not doing what its told to do, why?

now under testing:

280x(hynix) 325khs, clock speed does not matter so much this at 1100mhz, memory 1500mhz

sgminer.exe -k neoscrypt --thread-concurrency 8192 --rawintensity 6144 --worksize 256 -g 4 --lookup-gap 2

ati catalyst 14.11 beta dlls ( no big changes from 14.6rc2 if there is any…)

sgminer 5.1.0dev posted somewhere here, wolfs miner will not work

using now dlls from 14.11

file size is not same…

bins now created ok, no hw erros with 14.9-14.11 catalyst

I believe they are going off the actual DLL versions of the files, and not using the Catalyst version like most of us do. So when they say 14.2 it is probably Catalyst 14.6 RC2 or Catalyst 14.7 RC3.

yep, not talking about catalyst version, but actual driver version

AMD Catalyst 14.9 (14.201.1009)

now trying 14.9rc2, first look seems its fastest(like 0.5%)

solved!! used miner NOT compiled by wolf!

i made some notepad work, we should get 50% of original scrypt hashrate when kernel is optimal

Make sure you are removing regular intensity setting from your config when you run xintensity.

yep, im not so stupid. still no idea what this is…

we been fooled…

PPL like I said there is nothing special in my settings, it works every time on anything I just need to setup --xintensity 3. I m using 14.6 RC2 drivers and all other settings are the same like for any other miner. Here is complete line.

sgminer.exe -k neoscrypt --lookup-gap 2 --xintensity 3 --worksize 256 -g 2 -o xxxx:xxxx -u x -p x --gpu-engine “1000,1000,1000” --thread-concurrency “8192,8192,8192” --gpu-memclock “1500,1500,1500”

One more thing, I published this 5 days ago on my local forum and there is about 20 miners who use this settings for last 5 days or so.

equal to mine, why it wont work for me???

Well, weird… I rebooted my rig, and the 3% gained from the 112 worksize turned into about a 5% loss in hashrate over the 96 settings, but running the 96 settings was right where it’s been at…

So, I decided to do the old driver swaparoo with all the OCL stuff posted here (and wipe the bin file during swaps)

With 13/96/2 and 1100/1450 the results are 290/290x hashrate:

The 13.9 gets 161k145k

The 14.2 gets 298/294k

The 14.4 gets 255/242k

The 14.6 (rc2) gets 298/294k

The 14.7 (rc1) gets 298/294k

Tried running the worksize 112 again after all that, and it shows the 3% gain again, and lower hashrate on the 290x.

try my dllls from previous post and update your results??

edit: my best test

getting best results so far using dlls from 14.201.1009( very little effect):

http://www.filedropper.com/142011009

Both xintensity and rawintensity work properly under sgminer5-dev and with neoscrypt. I’ve used xintensity on my 290x with neoscrypt and it works fine, albeit with tiny less hash rate with the settings I used. It’s probably the thread concurrency you need to adjust here, and what magical TC is majsta using? I have no idea :(

miner compiled by wolf? 4.2.2 so called 5.xx??

im on win 7 64 bit . xi no use… i have no idea why

xIntensity works by being a shader multiplier for the thread intensity. It gives you finer control over thread intensity than just using regular Intensity settings of I1-20 which use a standard 2^x = thread intensity (where x is the intensity setting). You need to specify the number of shaders your card has in your config file to get this, or raw intensity to work properly because, again, xIntensity is a shader multiplier. I’ve used both xIntensity and rawintensity settings before, and let me just say that they are great features, but don’t expect a miraculous 100% increase in hash rate. Using these settings may or may not give you better hash rate, and to be honest, you will be spending a lot more time tweaking your config if you use xIntensity or rawintensity. rawintensity isn’t a multiplier. It’s a method of directly controlling the thread intensity. So going off of the traditional intensity 2^x = thread intensity (where x is intensity setting), you are simply entering the total number of thread intensity rather than using an equation or a shader multiplier. xIntensity and rawintensity settings also require extensive tweaking of the thread-concurrency as well, so traditional values of TC that worked while using standard intensity I1-20 will most likely require different TC settings for every single adjustment you make to xIntensity or rawintensity. So, HW errors are being caused because majsta hasn’t posted the number of shaders, nor have they posted the TC setting, which again is very important for using xIntensity and rawintensity. Here’s a good place to start for learning about xIntensity in particular:

https://github.com/sgminer-dev/sgminer/commit/7aeae40af22e6108aab8b68a229eea25a639d650

xIntensity Example: r9 280x has 2048 shaders

I15 = 2^15 = 32768 thread intensity

I16 = 2^16 = 65536 thread intensity

xIntensity setting 16 = 16 * 2048 = 32768 thread intensity

xIntensity setting 17 = 17 * 2048 = 34816 thread intensity

So using regular I1-20, there’s a huge, exponential jump in the number of thread intensity even at increment +1 (from I15-I16 it’s about a 2x increase in thread intensity). Using xIntensity, there’s a very small increase in thread intensity from xintensity16 to xintensity17, which again, may or may not give you better, or worse, hash rates.

no new info for me…

still something i am missing, hw only what ever i do when using xi

xi nor working in any way for neo?? why?