Comment # 6
on bug 82201
from Kai
(In reply to comment #5) > Are you checking radeon_pm_info while the app is running? E.g., via ssh or > via another X terminal? If you switch to another VT or something like that > there will not be any activity. Can you try is with something simple like > glxgears? E.g., run `vblank_mode=0 glxgears -fullscreen` and then check > radeon_pm_info via ssh while gears is running. I've always checked through SSH from a second machine. Now for your glxgears test: reclocking works (in Portal 2 as well, where I get 58-60 FPS now). The only difference is the radeon.dpm=1 on the kernel command line. Was that expected? I thought DPM was activated automatically with your 3.17 branch (it says so during boot as well, see e.g. attachment 103996 [details]) or at least I interpreted the "[drm] radeon: dpm initialized" line that way. As far as I'm concerned this can be closed, though the radeon man page should probably get a line like "setting radeon.dpm=1 is mandatory for reclocking on the following ASICs". I let you decide whether this is something that should have happend automatically (my preference) or that requires the kernel parameter and close/keep the report accordingly.
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
