<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [HAWAII] Get acceleration working" href="https://bugs.freedesktop.org/show_bug.cgi?id=78453#c130">Comment # 130</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [HAWAII] Get acceleration working" href="https://bugs.freedesktop.org/show_bug.cgi?id=78453">bug 78453</a> from <a class="email" href="mailto:luziphermcleod@yahoo.ie" title="Luzipher <luziphermcleod@yahoo.ie>"> Luzipher</a> <pre>(In reply to <a href="show_bug.cgi?id=78453#c126">comment #126</a>) > (In reply to <a href="show_bug.cgi?id=78453#c124">comment #124</a>) > > > > And for the DPM stuff: dpm doesn't seem to work, the numbers never changed > > (tested on console without X and Metro Last Light; I dropped my previous > > "radeon.dpm=0" from the kernel parameters): > > # cat /sys/kernel/debug/dri/64/radeon_pm_info > > power level avg sclk: 30000 mclk: 15000 > > You need to print that out while you have a 3D app running. Those numbers > are real-time. E.g., in the console, there is no 3D acceleration happening > so they stay at their low levels. I did just that :-) Sorry if I wasn't clear enough on this. Actually what I did was starting Metro Last Light and catting over ssh multiple times from my laptop (Metro doesn't allow alt-tab). The values never changed at all. I chose Metro, because it's the most graphically challenging piece of software I have - and should therefore certainly cause a change of values. glxgears didn't cause a change as well, but I thought that might be because it's too simple. Today, to verify, I also tried it with Half Life 2. Same result. (But MSAA works now with the libdrm patch, thanks Marek !) All of the above still with the "ASIC_ProfilingInfo v3.1" as I got a NULL pointer dereference with yesterday's drm-next-3.17-rebased-on-fixes kernel. I guess the new kernel to use is "standard" 3.17-wip, as it now contains all the Hawaii stuff ? I'm also ok with tracking the remaining issues in separate bugs - do I need to close this bug ? (I'd wait till the xf86-video-ati patch is applied). Any requests on which issues should get their own bugs now ? Turning off HDMI-0 and Glyphs come to mind ? Oh and I had a typo in my last comment - of course I updated <a class="bz_bug_link bz_status_NEW " title="NEW --- - [HAWAII][DPM] New Version 3.1 for ASIC_ProfilingInfo / ci_upload_dpm_level_enable_mask failed" href="show_bug.cgi?id=74250">bug #74250</a>. Is that maybe related to my never changing power states ?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>