Originally posted by Hans
View Post
Announcement
Collapse
No announcement yet.
stumped - xorg edgers + 2.6.35-rc1 DRI fail
Collapse
X
-
Originally posted by hmmm View Postsudo echo dynpm > /sys/class/drm/card0/device/power_method
Leave a comment:
-
With this command, you just sudo-ed 'echo'. The redirect ('> /sys/...') is still done by shell (bash), which is not sudo-ed. I found once really interesting alternative, using tee:
echo dynpm | sudo tee /sys/class/drm/card0/device/power_method
The only side-effect is that "dynpm" string will be emitted to stdout too.
Leave a comment:
-
cheers, it worked - although i'm getting some intermittent flickering now.
Any idea why i had do go into sudo -i as opposed to having to running the command with just:
sudo echo dynpm > /sys/class/drm/card0/device/power_method
Leave a comment:
-
I keep getting Permission denied whenever I try to enable dynpm:
echo dynpm > /sys/class/drm/card0/device/power_method
Same thing happens when trying to:
echo low > /sys/class/drm/card0/device/power_profile
Leave a comment:
-
The option was removed in 2.6.35 as the dynpm can now be dynamically set via sysfs. It's a general property of kernel modules to fail if an invalid option is provided; not something specific to radeon.
Leave a comment:
-
I have the same issue with drm-next and 2.6.35-rc1. If radeon.dynpm=1 is set the drm fails to load, bacause of "unknown option dynpm".
I guess even if dynpm is on by default it still should not happen.
2.6.34 works fine.
Leave a comment:
-
That's interesting. Maybe the radeon module should be made to rather ignore unknown options?
Leave a comment:
Leave a comment: