For me it's the other way around: It's always at full speed.
The only change I noticed is when running UVD, but this results in a hard (or soft? changing VT doesn't work but SysRq+REISUB reboots the machine) lock after a few seconds.
This is with 7982128c3d447df27db963af67bc6b8dc7efb1de from the drm-next-3.11 branch but the commits after that doesn't seem to change any behavior for evergreen cards.
Last edited by droste; 07-05-2013 at 12:59 PM.
Yes everything is set up correctly. Actually I'm the one who explained it to you, how to set this up, so if it is working for you, it should be working for me :-D
DPM and UVD are initialized without errors (dmesg).
UVD is working but stopping UVD playbacks and switching back to a non-UVD power state is locking up the PC sometimes.
DPM does nothing until UVD is used. There it correctly switches power states and power level until the playback ends. After that the power level goes back to power level 2 and stays there.
glad i'm not the only one with e350 problems with DPM and UVD enabled.
fritsch one of the XBMC coders posted a patch to get uvd and dpm working together.
Code:diff --git a/drivers/gpu/drm/radeon/sumo_dpm.c b/drivers/gpu/drm/radeon/sumo_dpm.c index dbad293..a71cbb6 100644 --- a/drivers/gpu/drm/radeon/sumo_dpm.c +++ b/drivers/gpu/drm/radeon/sumo_dpm.c @@ -1727,7 +1727,8 @@ int sumo_dpm_init(struct radeon_device *rdev) pi->enable_sclk_ds = true; pi->enable_dynamic_m3_arbiter = false; pi->enable_dynamic_patch_ps = true; - pi->enable_gfx_power_gating = true; + /* workaround to make UVD + DPM work together */ + pi->enable_gfx_power_gating = false; pi->enable_gfx_clock_gating = true; pi->enable_mg_clock_gating = true; pi->enable_auto_thermal_throttling = true;
Last edited by deadite66; 07-06-2013 at 04:45 AM.
I have tons of this error messages in dmesg, but everything seems fine
HD7640G + HD7670M(closed through vgaswitcheroo), mesa and xf86-video-ati 20130706, llvm 3.4. kernel agd5f's drm-next-3.11 branch 20130705.
And when use mplayer and vdpauinfo, i got this message, but also seems harmlessCode:[ 3561.423301] radeon 0000:00:01.0: GPU fault detected: 147 0x012d1502 [ 3561.423307] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 [ 3561.423312] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 [ 3561.423318] radeon 0000:00:01.0: GPU fault detected: 147 0x012d2502 [ 3561.423324] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 [ 3561.423330] radeon 0000:00:01.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
Code:Inconsistency detected by ld.so: dl-close.c: 765: _dl_close: Assertion `map->l_init_called' failed!
Last edited by jarryson; 07-06-2013 at 08:26 AM.
while an early try with drm-next-3.11-wip worked (but was slow-ish),
latest drm-next-3.11 @f4dec318 gives a flash of garbled output
then black screen, as soon as drm loads. Kernel crash.
Nothing about the crash is logged on disk after reboot.
PC is imac12,2, efi-booted.