BungaMan
October 19th, 2007, 04:58 PM
This stuff is not for beginners. If you don't know much about this then don't try it. If you do then it's up to your own responsibility if your system gets broken so you are warned in advance !
This is entirely written for my situation which is: Try to use dual screen with AIGLX, open source radeon driver and compiz. My setup is a laptop with radeon mobility 9600 and an external connected CRT screen.
1. If you upgraded from Feisty to Gutsy, chances are you also have the Xgl package (xserver-xgl) installed. You better remove this for better performance. It degraded the graphical UI and you don't need it anyway because we will use aixgl.
2. Auto setup of dual screen doesn't work to good for me and the "Screens and graphics" ain't much worth for me either so diving back into xorg.conf. The updated radeon driver doesn't support mergedfb or xinerama anymore so we'll prep xorg.conf for xrandr.
Start with a simple Device section, leave the tweaking for later on
Section "Device"
Identifier "MobRad9600"
Boardname "ATI Radeon"
Busid "PCI:1:0:0"
Driver "radeon"
Vendorname "ATI"
EndSection
Now add a Monitor section for each monitor you have attached
Section "Monitor"
Identifier "Laptop"
Vendorname "Generic LCD Display"
Modelname "LCD Panel 1280x800"
Option "DPMS"
HorizSync 28-51
VertRefresh 43-60
EndSection
Section "Monitor"
Identifier "CRTThuis"
Vendorname "LG"
Modelname "CRT 1280x1024"
Option "DPMS"
HorizSync 30-96
VertRefresh 50-160
Modeline "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
EndSection
If you don't know the horizonsync and vertrefresh then you can start without them and hope for decent detection. The modeline in the second monitor isn't necessary either but I'll explain that later. If you absolutely want to add the modeline then run the following command in a terminal.
more /var/log/Xorg.0.log | grep "Modeline \"1280x1024\" "
Replace the resolution with the one you are looking for. Note that a monitor can have multiple modelines, each will give you a different refresh rate. More so, with 2 monitors supporting the same resolution you will have the modelines of each so be careful here. To be sure, open up Xorg.0.log in gedit and look for the lines. See for which monitor they are generated. You will need the right modeline afterwards for xrandr.
Now setup the Screen section
Section "Screen"
Identifier "Default Screen"
Device "MobRad9600"
Defaultdepth 24
Monitor "Laptop"
SubSection "Display"
Depth 24
Viewport 1280 0
Virtual 2560 1024
Modes "1280x1024" "1280x800"
EndSubSection
EndSection
Only one screen section and we set it up with the default monitor. In my case thats the LVDS of my laptop. Virtual is important, it defines the total horizontal and vertical size of what you are going to look at. I have a CRT at 1280x1024 and a laptop lcd at 1280x800. The crt left of the laptop so that makes 1280+1280=2560 for the horizontal size and 1024 vertically. Not 1824 vertically because the screens are next to each other, not below each other. Viewport will define the position of my default screen in this virtual size. My crt will take up the first 1280 horizontally so the horizontal starting point of my lcd is 1280. 0 for the vertical position because I let both screens align at the top. Modes contains all the resolutions that I will use. Probably isn't needed with xrandr, but this is untested.
Now we still need a serverlayout
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
Option "AIGLX" "true"
EndSection
Section "DRI"
Mode 0666
EndSection
Section "Extensions"
Option "Composite" "Enable"
EndSection
Make sure that the AIGLX is there and set to true. I don't kow if the DRI section is necessary but it works when it is there, same for Composite :)
My xorg.conf is attached for reference.
3. That should do it for xorg.conf but it doesn't make dual screen work yet. So let's see how we can get xrandr to do its job properly.
Let's query for some info in a console
xrandr -q
It will show you the detected resolutions for each connector (VGA-0 and LVDS in my case). For my CRT, the 1280x1024 resolution was not detected but my monitor sure can handle it so I instruct xrandr to add this "mode". This is where the detected Modelines are needed from Xorg.0.log. The example will make it clear.
xrandr --output VGA-0 --newmode "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
As you can see, I'm telling xrandr to add a new mode to connector VGA-0. I'm giving the mode the name "1280x1024" but you can call it "monkeyres" for example :) The rest of the parameters are taken from the Modeline as you know by now.
This is not enough, newmode is for adding a supported resolution. Now we have to tell to actually use that resolution.
xrandr --addmode VGA-0 "1280x1024"
The example is pretty much self explainatory now.
Now we are ready to activate dual screen properly compared to the clone mode you may have right now.
xrandr --output VGA-0 --left-of LVDS --mode 1280x1024
This is also easy to understand. Tell xrandr that I want to have VGA-0 positioned left of LVDS (my laptop lcd) and use mode name 1280x1024 for VGA-0.
Because xrandr is all about dynamic setup, your setup ain't going to last after a reboot so I made a little script that detects if my desired mode is added and executes the above commands if necessary. Then added the script to my session and each time I log on I have a dual screen started.
This is the content of the script
#!/bin/sh
if ! xrandr -q | grep -q "VGA-0 connected 1280x1024" ; then
xrandr --output VGA-0 --newmode "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
fi
xrandr --addmode VGA-0 "1280x1024"
xrandr --output VGA-0 --left-of LVDS --mode 1280x1024
Now lets get compiz started. Try running the following command in a terminal.
compiz --replace &
It is possible that due to the dual screen setup, you now have a screen that is too large for the maximum texture size.
4. To solve the maximum texture size problem, first of all add support for large textures in DRI. Install driconf and then check in your home dir for the file ".drirc". If it doesn't exist then you may need to run driconf once. In the file add a node for allow_large_textures.
<driconf>
<device screen="0" driver="r300">
<application name="Default">
...other options...
<option name="allow_large_textures" value="2" />
</application>
</device>
</driconf>
Good, now this won't run compiz. Compiz checks for the opengl parameters. In my case the maximum supported texture size is 2048x2048. As you know my virtual area is 2560x1024 so that's a bit out of range. For some background info... compiz makes textures of everything, programs, task bars at the top, your wallpaper, etc.
5. Let's make compiz not check for the texture size. DO THIS ON YOUR OWN RISK. The effect for me is that texturizing my background fails so I have a white are for the supported texture size and for the desktop area that is out of range, I get a funky disfunctional area that I can live with :) If you stretch a program across your dual screen, you'll notice that at one point it will be blank until you resize it back within your maximum texture size.
So... edit /usr/bin/compiz and comment out "return 1;" in the following function. Should be at line 231.
# Check if the max texture size is large enough compared to the resolution
check_texture_size()
{
TEXTURE_LIMIT=$(glxinfo -l | grep GL_MAX_TEXTURE_SIZE | sed 's/.*=[^0-9]//g')
RESOLUTION=$(xdpyinfo | grep -i dimensions: | sed 's/[^0-9]*pixels.*(.*).*//' | sed 's/[^0-9x]*//')
VRES=$(echo $RESOLUTION | sed 's/.*x//')
HRES=$(echo $RESOLUTION | sed 's/x.*//')
verbose "Comparing resolution ($RESOLUTION) to maximum 3D texture size ($TEXTURE_LIMIT): ";
if [ $VRES -gt $TEXTURE_LIMIT ] || [ $HRES -gt $TEXTURE_LIMIT ]; then
verbose "Failed.\n"
# return 1;
fi
verbose "Passed.\n"
return 0
}
Commenting it out will keep everything OK except that it will not return a failure but just continue. This is a bit dirty but for now the easiest.
Save the file and try again to run "compiz --replace &" in a terminal.
I hope that works for you or at least give you a clue on where to look.
[edit]updated some info
This is entirely written for my situation which is: Try to use dual screen with AIGLX, open source radeon driver and compiz. My setup is a laptop with radeon mobility 9600 and an external connected CRT screen.
1. If you upgraded from Feisty to Gutsy, chances are you also have the Xgl package (xserver-xgl) installed. You better remove this for better performance. It degraded the graphical UI and you don't need it anyway because we will use aixgl.
2. Auto setup of dual screen doesn't work to good for me and the "Screens and graphics" ain't much worth for me either so diving back into xorg.conf. The updated radeon driver doesn't support mergedfb or xinerama anymore so we'll prep xorg.conf for xrandr.
Start with a simple Device section, leave the tweaking for later on
Section "Device"
Identifier "MobRad9600"
Boardname "ATI Radeon"
Busid "PCI:1:0:0"
Driver "radeon"
Vendorname "ATI"
EndSection
Now add a Monitor section for each monitor you have attached
Section "Monitor"
Identifier "Laptop"
Vendorname "Generic LCD Display"
Modelname "LCD Panel 1280x800"
Option "DPMS"
HorizSync 28-51
VertRefresh 43-60
EndSection
Section "Monitor"
Identifier "CRTThuis"
Vendorname "LG"
Modelname "CRT 1280x1024"
Option "DPMS"
HorizSync 30-96
VertRefresh 50-160
Modeline "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
EndSection
If you don't know the horizonsync and vertrefresh then you can start without them and hope for decent detection. The modeline in the second monitor isn't necessary either but I'll explain that later. If you absolutely want to add the modeline then run the following command in a terminal.
more /var/log/Xorg.0.log | grep "Modeline \"1280x1024\" "
Replace the resolution with the one you are looking for. Note that a monitor can have multiple modelines, each will give you a different refresh rate. More so, with 2 monitors supporting the same resolution you will have the modelines of each so be careful here. To be sure, open up Xorg.0.log in gedit and look for the lines. See for which monitor they are generated. You will need the right modeline afterwards for xrandr.
Now setup the Screen section
Section "Screen"
Identifier "Default Screen"
Device "MobRad9600"
Defaultdepth 24
Monitor "Laptop"
SubSection "Display"
Depth 24
Viewport 1280 0
Virtual 2560 1024
Modes "1280x1024" "1280x800"
EndSubSection
EndSection
Only one screen section and we set it up with the default monitor. In my case thats the LVDS of my laptop. Virtual is important, it defines the total horizontal and vertical size of what you are going to look at. I have a CRT at 1280x1024 and a laptop lcd at 1280x800. The crt left of the laptop so that makes 1280+1280=2560 for the horizontal size and 1024 vertically. Not 1824 vertically because the screens are next to each other, not below each other. Viewport will define the position of my default screen in this virtual size. My crt will take up the first 1280 horizontally so the horizontal starting point of my lcd is 1280. 0 for the vertical position because I let both screens align at the top. Modes contains all the resolutions that I will use. Probably isn't needed with xrandr, but this is untested.
Now we still need a serverlayout
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
Option "AIGLX" "true"
EndSection
Section "DRI"
Mode 0666
EndSection
Section "Extensions"
Option "Composite" "Enable"
EndSection
Make sure that the AIGLX is there and set to true. I don't kow if the DRI section is necessary but it works when it is there, same for Composite :)
My xorg.conf is attached for reference.
3. That should do it for xorg.conf but it doesn't make dual screen work yet. So let's see how we can get xrandr to do its job properly.
Let's query for some info in a console
xrandr -q
It will show you the detected resolutions for each connector (VGA-0 and LVDS in my case). For my CRT, the 1280x1024 resolution was not detected but my monitor sure can handle it so I instruct xrandr to add this "mode". This is where the detected Modelines are needed from Xorg.0.log. The example will make it clear.
xrandr --output VGA-0 --newmode "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
As you can see, I'm telling xrandr to add a new mode to connector VGA-0. I'm giving the mode the name "1280x1024" but you can call it "monkeyres" for example :) The rest of the parameters are taken from the Modeline as you know by now.
This is not enough, newmode is for adding a supported resolution. Now we have to tell to actually use that resolution.
xrandr --addmode VGA-0 "1280x1024"
The example is pretty much self explainatory now.
Now we are ready to activate dual screen properly compared to the clone mode you may have right now.
xrandr --output VGA-0 --left-of LVDS --mode 1280x1024
This is also easy to understand. Tell xrandr that I want to have VGA-0 positioned left of LVDS (my laptop lcd) and use mode name 1280x1024 for VGA-0.
Because xrandr is all about dynamic setup, your setup ain't going to last after a reboot so I made a little script that detects if my desired mode is added and executes the above commands if necessary. Then added the script to my session and each time I log on I have a dual screen started.
This is the content of the script
#!/bin/sh
if ! xrandr -q | grep -q "VGA-0 connected 1280x1024" ; then
xrandr --output VGA-0 --newmode "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
fi
xrandr --addmode VGA-0 "1280x1024"
xrandr --output VGA-0 --left-of LVDS --mode 1280x1024
Now lets get compiz started. Try running the following command in a terminal.
compiz --replace &
It is possible that due to the dual screen setup, you now have a screen that is too large for the maximum texture size.
4. To solve the maximum texture size problem, first of all add support for large textures in DRI. Install driconf and then check in your home dir for the file ".drirc". If it doesn't exist then you may need to run driconf once. In the file add a node for allow_large_textures.
<driconf>
<device screen="0" driver="r300">
<application name="Default">
...other options...
<option name="allow_large_textures" value="2" />
</application>
</device>
</driconf>
Good, now this won't run compiz. Compiz checks for the opengl parameters. In my case the maximum supported texture size is 2048x2048. As you know my virtual area is 2560x1024 so that's a bit out of range. For some background info... compiz makes textures of everything, programs, task bars at the top, your wallpaper, etc.
5. Let's make compiz not check for the texture size. DO THIS ON YOUR OWN RISK. The effect for me is that texturizing my background fails so I have a white are for the supported texture size and for the desktop area that is out of range, I get a funky disfunctional area that I can live with :) If you stretch a program across your dual screen, you'll notice that at one point it will be blank until you resize it back within your maximum texture size.
So... edit /usr/bin/compiz and comment out "return 1;" in the following function. Should be at line 231.
# Check if the max texture size is large enough compared to the resolution
check_texture_size()
{
TEXTURE_LIMIT=$(glxinfo -l | grep GL_MAX_TEXTURE_SIZE | sed 's/.*=[^0-9]//g')
RESOLUTION=$(xdpyinfo | grep -i dimensions: | sed 's/[^0-9]*pixels.*(.*).*//' | sed 's/[^0-9x]*//')
VRES=$(echo $RESOLUTION | sed 's/.*x//')
HRES=$(echo $RESOLUTION | sed 's/x.*//')
verbose "Comparing resolution ($RESOLUTION) to maximum 3D texture size ($TEXTURE_LIMIT): ";
if [ $VRES -gt $TEXTURE_LIMIT ] || [ $HRES -gt $TEXTURE_LIMIT ]; then
verbose "Failed.\n"
# return 1;
fi
verbose "Passed.\n"
return 0
}
Commenting it out will keep everything OK except that it will not return a failure but just continue. This is a bit dirty but for now the easiest.
Save the file and try again to run "compiz --replace &" in a terminal.
I hope that works for you or at least give you a clue on where to look.
[edit]updated some info