Difference between revisions of "Display Drivers"
|Line 276:||Line 276:|
== Troubleshooting ==
== Troubleshooting ==
=== X-windows won't start ===
=== X-windows won't start ===
Revision as of 14:57, 27 September 2007
An incomplete HowTo on updating LinuxMCE to the latest display drivers and configuring them manually. It could use your help, so if something is different in your situation, please add it.
Note that this should normally not be necessary unless you have specific wishes or trouble getting your display to work properly.
- 1 Installation
- 2 Configuration
- 3 Troubleshooting
- 4 See also
The two main ways to install the ATI drivers are described in the Ubuntu Feisty Installation Guide.
For more information see also the Unofficial ATI Linux Driver Wiki and you might want to have a look at AtiProprietaryDriver in the MythTV wiki as well since LinuxMCE depends on it for viewing TV. MythTV in turn relies heavily on the support of certain features by the graphics drivers. The ATI drivers turn out to be a bit "challenged" in this area to say the least.
There are several ways to install NVidia drivers, the way described here is meant as a guide to install the very latest drivers from the NVidia website. Note that this way will bypass the LinuxMCE (Kubuntu) packaging system, possibly removing and/or overwriting some of it's files.
1. Go to a console (text) terminal by holding [CTRL]-[ALT] and pressing the [F1] key simultaneously, log in with the user account you have created during the Kubuntu install and become root, if you haven't done so already.
<you>@dcerouter:~$ sudo -s
root@dcerouter:~# wget http://us.download.nvidia.com/XFree86/Linux-x86/100.14.11/NVIDIA-Linux-x86-<version>-pkg1.run
3. Go to runlevel 1 to stop the currently running X-server.
root@dcerouter:~# telinit 1
4. Execute the installer and follow instructions. Ignore the warning about runlevel 1 and don't bother looking for precompiled drivers.
root@dcerouter:~# sh NVIDIA-Linux-x86-<version>-pkg1.run
5. Now it needs to be configured. The recommended and most convenient way is to use the AVWizard. For more advanced setup, or if the AVWizard for some reason is unable to set your up your screens to your liking, you can configure the X-server manually by editing the xorg.conf file directly.
There is a renewed interest in the Intel graphics chipsets since Intel released the drivers under the GPL. However, they're still not at the same level as nVidia's and can't do alpha blending.
Use the Openchrome or Via Unichrome drivers. The Via Unichrome drivers can be downloaded from http://www.viaarena.com/default.aspx?PageID=2&OSID=45&CatID=3220
Please help out by adding more if you can.
The recommended and most convenient way is to use the AVWizard. For more advanced setup, or if the X-server (and thus also the AVWizard) is unable to start, you can configure the X-server manually by editing the xorg.conf file directly.
Start by making a backup copy of the /etc/X11/xorg.conf file (even if it doesn't work it might contain settings you could need). In this example we will start from scratch and edit the configuration file step by step to get the main display setup.
Some of these steps require that there will be no X-server active on the system, the easiest way to achieve this is to boot in rescue-mode, just hit [Esc] when Grub tells you to during the startup of your machine and select the right line from the menu. Another way is to go to a text-mode console (aka. terminal) with [CTRL]-[ALT]-[F1], log in, become root and issue the command:
This wil stop the running X-server and drop you into rescue mode as well.
One of the advantages is that now you can start and stop the X-server by hand with an alternative configuration file and without having to reboot or even start an entire desktop environment.
Generating a template
These instructions were originally written for ATI chipsets, so they might need to be adjusted and updated a bit. Not all of the specific options may be relevant for your chipset.
While there is no (other) X-server running you can create a template configuration file by running:
This will create a file called xorg.conf.new in your home directory, test it with the following command and hit [CTRL]-[ALT]-[Backspace] when done:
X -config ~/xorg.conf.new
Within a few seconds a gray bitpattern should show up with an 'X' shaped mouse cursor. If the screen is distorted or reports the refresh rate to be out of range then you will either have to specify the proper refreshrate limitations for your screen or insert "modelines" for the resolution(s) you want to use (see below).
When you're satisfied you can overwrite /etc/X11/xorg.conf with this file to make it the default (you did make a backup didn't you?), once you have done that you can use "startx" to test and have the use of your desktop as well. This should at least be enough to allow the use of a graphic configuration tool (like the AVWizard for instance) to set up your display further. More advanced manual configuration options can be found below.
Here is an example of such a generated file:
Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "Files" RgbPath "/etc/X11/rgb" ModulePath "/usr/lib/xorg/modules" FontPath "/usr/share/fonts/X11/misc" FontPath "/usr/X11R6/lib/X11/fonts/misc" FontPath "/usr/share/fonts/X11/cyrillic" FontPath "/usr/share/fonts/X11/100dpi/:unscaled" FontPath "/usr/share/fonts/X11/75dpi/:unscaled" FontPath "/usr/share/fonts/X11/Type1" FontPath "/usr/X11R6/lib/X11/fonts/Type1" FontPath "/usr/share/fonts/X11/100dpi" FontPath "/usr/share/fonts/X11/75dpi" FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" EndSection Section "Module" Load "extmod" Load "record" Load "xtrap" Load "dri" Load "glx" Load "dbe" Load "GLcore" Load "type1" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5 6 7" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName "Monitor Model" EndSection Section "Device" ### Available Driver options are:- ### Values: <i>: integer, <f>: float, <bool>: "True"/"False", ### <string>: "String", <freq>: "<f> Hz/kHz/MHz" ### [arg]: arg optional #Option "ShadowFB" # [<bool>] #Option "DefaultRefresh" # [<bool>] #Option "ModeSetClearScreen" # [<bool>] Identifier "Card0" Driver "vesa" VendorName "ATI Technologies Inc" BoardName "ATI Radeon Xpress 1200 Series" BusID "PCI:1:5:0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" SubSection "Display" Viewport 0 0 Depth 1 EndSubSection SubSection "Display" Viewport 0 0 Depth 4 EndSubSection SubSection "Display" Viewport 0 0 Depth 8 EndSubSection SubSection "Display" Viewport 0 0 Depth 15 EndSubSection SubSection "Display" Viewport 0 0 Depth 16 EndSubSection SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection
Note that the only thing really specific to my setup in this config file is BusID, if you only have one graphics adapter in your system this value can be omitted, otherwise the value(s) can be found with:
Where each card will need it's own Device Section in the config file. The "VendorName" and "BoardName" settings are just labels and serve no real purpose other then being able to identify this particular device, which is usefull if you have more then one.
We'll be using this sample configuration as a starting point in the other examples below, the comments (lines starting with # can be safely removed as well as the "Display" subsections for the colordepths we don't plan on using.
Refresh rate / ModeLine
The easiest way to sort this problem is to let the X-server figure this out by not specifying the limits of your screen. However this often fails, leaving you with an unusable display. Simply look up your screen's refresh rates in the documentation and add them like this:
Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName "Monitor Model" HorizSync 27-102 # kHz VertRefresh 50-160 # Hz EndSection
Alternatively you could specify a "ModeLine" for each resolution you want to use. By using ModeLines you have much finer controll over the timings of the output signal generated by your videocard. The drawback is that the timing values can be hard to get right.
Search the web for a "modeline generator", and many of these will include instructions on how to add the modeline, but briefly, you just add it to the "Monitor" section. Read the wikipedia entry to learn how to use modelines.
If one modeline doesn't work perfectly, try another, perhaps from another generator, because they can vary so much.
Using the wrong timings could in some (nowadays rare) occasions damage the hardware of your screen, so if it looks garbeled don't leave it like that for hours on end but hit [Ctrl]-[Alt]-[←Backspace] and readjust your settings. Most modern screens however simply report that the signal is out of range if this happens.
Colordepth and resolution
Specify the colordepth and resolution(s) you would like to use, like this:
Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Virtual 1600 1200 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" "512x384" "400x300" "320x240" EndSubSection EndSection
As most people will only be using 24 bits anyway, I have removed the other redundant subsections. "Virtual" is the size of your desktop and "Modes" are physical resolutions, you can flip through these by holding [CTRL]-[ALT] and pressing the plus or minus on the numeric keypad. These are just examples, most people will only want to specify the resolution they actually use.
DRI device permissions
This section is needed to have the X-server set the proper permissions on the DRI device during startup. Simply add it to the end of the /etx/X11.xorg file if it isn't there already.
Section "DRI" Mode 0666 EndSection
Change "vesa" to "fglrx" (or "ati", depending on which drivers you installed earlier), as shown below, the old line is left as a comment in this example for clarity, but it's better to remove it as some scripts seem to find it confusing. For Nvidia chipsets use nvidia or nv as the driver names (instead of fglrx).
Section "Device" Identifier "Card0" # Driver "vesa" Driver "fglrx" VendorName "ATI Technologies Inc" BoardName "ATI Radeon Xpress 1200 Series" BusID "PCI:1:5:0" EndSection
If your X-server was running you will have to restart it completely for the changes to take effect, the easiest and most thorough way to do this is to reboot.
Physical display size
Like specifying the refresh rate his is optional but sometimes necessary, most of the time it is either detected or some sane defaults are used but sometimes it isn't, which can result in unreadable font sizes.
Section "Monitor" ... DisplaySize 155 95 EndSection
Where you have to replace the numbers with the physical width and height of your screen in millimeters (1" = 25mm), feel free to try mine, however these are for a small touchscreen.
Aparently the ATI fglrx driver does not yet support composite with DRI. So if you are using the fglrx driver, disable it by adding this to the end of the /etx/X11.xorg file if it isn't there already.
Section "Extensions" Option "Composite" "Disable" EndSection
To be continued, I don't think this is enough to get UI2 completely (either mode) going yet. Feel free to jump in anytime...
Things still to sort out amongst others (i.e. what is it, do we need it and what are the settings if any):
Section "Module" Load "i2c" Load "bitmap" Load "ddc" Load "freetype" Load "int10" Load "vbe" Load "speedo" Load "type1" Load "dbe" Load "glx" Load "v4l" EndSection
Section "ServerFlags" Option "AIXGL" "off" EndSection
Section "Extensions" Option "Composite" "Disable" # Option "RENDER" "true" EndSection
Option "PseudoColorVisuals" "off" Option "OpenGLOverlay" "off" Option "VideoOverlay" "off" Option "DesktopSetup" "clone"
TV-out options, 2nd display, etc.
X-windows won't start for AVWizard
One problem on nvidia-cards could be that it does not detect the right monitor.Go to Console 1 ([Ctrl]+[Alt]+1) and edit /etc/X11/xorg.conf (nano -w /etc/X11/xorg.conf). Find the section Device with the driver nvidia add the line
Option "ConnectedMonitor" "XXX" where XXX is CRT, CRT-0, CRT-1, DVI-0, DVI-1, ...
Save and exit (nano: Ctrl+x) and restart the computer. In my case it was "CRT-1".
X-windows won't start
Reboot into rescue-mode if needed (hit [Esc] when Grub tells you to), and restore a working copy of your /etc/X11/xorg.conf, or edit it by hand to fix the problem. Test it with the command "X" and press [Ctrl]-[Alt]-[←Backspace] simultaneous to quit (alternative: use "startx" and get the full desktop, if any), then reboot when it works and you're done.
Signal out of range
See Refresh rate above.
Microscopic fonts in KDE
See Physical display size above.