Author

Topic: Problem with Sgminer + xintensity? Can't set memory clocks. (Read 4398 times)

full member
Activity: 140
Merit: 100
Residencial Castor Apart-Hotel
what kernel is used to mine scrypt coins?
bmL
member
Activity: 95
Merit: 10
I use 410.

"xintensity" : "410,410,410,410",

The issue is not what xintensity to use. The issue is that when I try to use xintensity, sgminer won't change the GPU mem clocks. I'm stuck at 1050/150, and I'm getting 11kh/s.
You propably set wrong intensity and GPU went into some kind of safe mode.
My cards go to 150 memory when I overstress them with wrong settings and then card's won't allow to change clocks until I reboot system. Try using different xintensity until u get one to work (try values between 1-10).
legendary
Activity: 952
Merit: 1000
I ended up switching to BAMT, and I had the same issue, which tells me I didn't build SGMiner wrong, nor was it a problem with my OS/drivers. I ended up upgrading to BAMT 1.5 (with the 14.1 drivers) and building a new version of SGMiner 4.1.0, and the issue went away. I can now use xIntensity just fine.
newbie
Activity: 8
Merit: 0
I had the same prob.  plug a screen or dummy plug and it will work on the 290.
legendary
Activity: 952
Merit: 1000
Don't think it's a problem with building sgminer wrong. Tried Litecoin BAMT 1.3, and it does the same thing. Balls.
full member
Activity: 196
Merit: 100
Couldn't say then.  I used exactly the same OS and package versions as you to build sgminer.
legendary
Activity: 952
Merit: 1000
I use 410.

"xintensity" : "410,410,410,410",

The issue is not what xintensity to use. The issue is that when I try to use xintensity, sgminer won't change the GPU mem clocks. I'm stuck at 1050/150, and I'm getting 11kh/s.
full member
Activity: 196
Merit: 100
I use 410.


"xintensity" : "410,410,410,410",
"worksize" : "384,384,384,384",
"kernel" : "zuikkis,zuikkis,zuikkis,zuikkis",
"lookup-gap" : "0,0,0,0",
"thread-concurrency" : "20481,20481,20481,20481",
"shaders" : "0,0,0,0",
"gpu-engine" : "1050-1050,1050-1050,1050-1050,1050-1050",
"gpu-fan" : "85-85,95-95,85-85,85-85",
"gpu-memclock" : "1450,1450,1450,1450",
"gpu-memdiff" : "0,0,0,0",
"gpu-powertune" : "20,20,20,20",
"gpu-vddc" : "0.000,0.000,0.000,0.000",
"temp-cutoff" : "95,95,95,95",
"temp-overheat" : "85,85,85,85",
"temp-target" : "75,75,75,75",
"api-mcast-port" : "4028",
"api-port" : "4028",
"expiry" : "30",
"failover-only" : true,
"failover-switch-delay" : "60",
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"log" : "5",
"no-pool-disable" : true,
"queue" : "1",
"scan-time" : "15",
"tcp-keepalive" : "30",
"temp-hysteresis" : "3",
"shares" : "0",
"kernel-path" : "/usr/local/bin"
legendary
Activity: 952
Merit: 1000
I'm using Xubuntu 13.10, AMD 13.11b9 drivers, APP SDK 2.9, and ADL SDK 6, SGMiner 4.0.0. For hardware, I'm using Gigabyte 280x and PowerColor 290 cards.

I was able to build sgminer just fine. Compared to sgminer 3.7.2, I can close it without crashing X, and I get about the same hashrate.

I'm trying to use the xintensity option. Whenever I do, I get TERRIBLE hashrates. Like 10-15kh/s. SGMiner shows "I:8" on the side, which doesn't make any sense, and the mem clock is running at 150MHz. I can't manually change the mem clock; it's just stuck at 150MHz. I also can't change the I; it's just stuck at 8, which doesn't make any sense cuz I'm trying all sorts of values from 80 to 1100.

When I go back to using normal intensity rather than xintensity, everything works. I: reads as whatever I set it to, and the mem clocks change just fine.

Anyone know why this would be? Did it build wrong somehow? Thanks!
Jump to: