Comment # 37
on bug 72785
from Tom Stellard
(In reply to Linux User from comment #36) > Got similar issues when trying scrypt. I have relatively recent bfgminer (~1 > month old git build) and more or less recent graphics stack: 3.17 kernel, > mesa 10.4 pre-release from Oibaf PPA and LLVM 3.5.1 > > I have bunch of HD5000 based cards, mostly HD5750/5770 and somesuch and R9 > 270. Tests have shown bfgminer performs correctly when computing SHA256 and > goes about 80% of catalyst at 57xx and even better than that on R9 270. > > However things are much worse when it comes to scrypt. I got impression open > driver can get issues if something aggressively using GPU VRAM. > > Some observations about open drivers stack so far: > - If you set scrypt intensity too high, there is high risk GPU would lock up > in fatal way and crash (can happen on both 57xx and R9). > Do you have an X server running? One cause of lockups is bfgminer hogging the GPU, and X not being able to do anything. I recommend trying without an X server. For best results when not using an X server, enable render nodes in the kernel by adding drm.rnodes=1 to your kernel command line.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
