Comment # 7
on bug 74250
from Alex Deucher
(In reply to comment #6) > (In reply to comment #4) > > Please try the attached patches. > > Yay, those help ! Thanks a lot, Alex ! :-) > With all three patches (attachements #93015, #103772, #103773) I get working > DPM and none of the error messages above. > I used the drm-next-3.17-wip kernel from yesterday with the patches applied > manually (noticed you committed them just after I started the build). I > think you didn't commit #93015 ? It's irrelevant with the other patches applied. > DPM also seems to work quite correcty, the card goes up to over 1GHz > (1040MHz should be max for my card) on sclk, mclk always stays the same (but > is different than without dpm): > # cat /sys/kernel/debug/dri/0/radeon_pm_info > power level avg sclk: 100120 mclk: 130000 > > Without the patches, I always got: > power level avg sclk: 30000 mclk: 15000 > > Half-Life 2 now runs more or less constantly at 60fps with hig details and > 8x MSAA :-) Metro Last Light is only at 20-30fps, but that's still great. > What I don't really understand is that Metro didn't feel much slower when > dpm didn't work (HL2 certainly did). > > > I guess sclk stands for "shader clock" and mclk is for "memory clock" ? On > Windows I believe I also have different memory clocks between the desktop > and in games - is memory clocking not dynamic yet ? sclk (system clock) is the engine clock and mclk is the memory clock. It should be dynamic. With no GPU tasks running you should see power level avg sclk: 30000 mclk: 15000 and both should be higher when there is GPU load. Can you attach your dmesg and xorg log with the patches applied? Also are you using multiple monitors? If so can you try again with a single monitor?
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