nomadwheels.blogg.se - How to adjust overscan intel graphics and media

How to adjust overscan intel graphics and media driver#
How to adjust overscan intel graphics and media software#

usr/bin/gconftool-2 -type string -set /system/gstreamer/0.10/default/videosink ximagesink # We do the later, but only if the current display size > 2048įor output in $(/usr/bin/xrandr -d :0.0 -verbose| \ # So there are 2 ways to work around the bug, either use Compositing or disable XV. # unless you use Metacity compositing, which is rather slow.

# Basically you cannot have video acceleration if desktop size >2048 pixels in either way # This script is to work around an annoying issue on Intel 945 video chips It could be launched from a dock hotplug event script (although that would not take care of all the use cases, such as booting with external display already attached) Here is a script I wrote that automatically sets the correct video output option based on configured displays. Gconftool-2 -type string -set /system/gstreamer/0.10/default/videosink autovideosink Gconftool-2 -type string -set /system/gstreamer/0.10/default/videosink ximagesink For Gstreamer enabled apps this can be set globally, for other apps you will have to dig into their settings. This will cause much higher CPU usage, but only during video playback. Gconftool-2 -type bool -set /apps/metacity/general/compositing_manager false

How to adjust overscan intel graphics and media driver#

Xvideo does not work (black or empty video window) įor the Xvideo issue a workaround in the driver is technically possible but not yet implemented.įor now you can work around the Xvideo driver issue by either enabling Metacity compositing or disabling XV overlay.Įnable Metacity Compositing gconftool-2 -type bool -set /apps/metacity/general/compositing_manager true.

How to adjust overscan intel graphics and media software#

3D acceleration is limited (compiz will crash, or with some older software stacks may even freeze the system).

Here are the limitations you may run into when running dual-display Extended desktop. The chip has hardware limitations when the display area exceeds 2048 pixels (horizontally or vertically), which is why earlier versions of the driver did not even try to support it.

But in reality you should really be running at least the 2.6.30.5 kernel and version 2.8 of the Intel driver.

Right now KMS is still in heavy development, and officially requires at least kernel 2.6.29 with version 2.7 of the Intel driver. Note that KMS does not eliminate the need for the Intel Xorg driver, it just frees that driver from the hardware setup functions. larger virtual display size (4096x4096) allowing extended desktop configs (2048x2048 without KMS).should in the future allow for the X server to run without root privileges.early graphical boot display with seamless login.in theory should not allow the X video driver to hang the system.ability to show kernel dump screens even when the X server was running.increased stability, because it removes the current contention between the X server and the kernel.This should have the following benefits over legacy mode setting KMS (Kernel Mode Setting) as the name suggests moves some video setup functions to the kernel. Intel releases a new driver once per quarter. The Intel opensource videodriver is maintained by Intel at. Uses up to 224MB of main memory for video usage.Integrated into the following chipsets:.2.3 ThinkPads this chip may be found in.