LinuxMCE - User contributions [en]

Internet Radio

2010-07-18T05:49:48Z

Usaf-lt-g: /* Notes and troubleshooting */

{{versioninfo|810Status=Working|810UpdatedDate=23rd June 2010|810UpdatedBy=Metoer}}
[[Category: Tutorials]]
Currently there is no direct support for the Internet Radio station list in LinuxMCE. However, you can create the scenario shortcut to quick-start your favorite station.

Here is a link to a page with a few stations that you can choose from, I tried a couple and they all seemed to work with this wiki.
http://slhungary.hu/print.php?plugin:content.40

* Go to [[LinuxMCE Admin Website]] --> Advanced --> Configuration --> Scenarios --> Media Scenarios" and press "Add My Scenario" button.

* Under "Add My Scenario" type a description, like "DI - Lounge". Check in which room you want this scenario to appear. Press "Save".

* Click on the description of the scenario that you've just added.

* In "Scenario commands" select "Media Plug-in" from the "Device:" drop-down and "MH Play Media" from the "Command:" drop-down. Press the "Add" button.

# In the "#13 Filename (string)" field type the URL of your online radio station ( e.g.: http://scfire-chi0l-1.stream.aol.com/stream/1009 ).
# In the "#29 PK_MediaType (int)" type 4.
# In the "#45 PK_EntertainArea (string)" put the number of the Entertaining Area (it usually starts from 1, see the note below). Press the "Save" button and the "Test Command" to see if it works.

* Do a [[quick reload router|Quick Reload]] & [[Orbiter Generator|Regen]] and you'll be able to see you radio on the media menu of your Orbiter. Click on the button and it should start playing.

==Where to Find Compatible Internet Radio Stations==

If you're in the U.S. like me, you'll probably have a hard time finding "direct URLs" that you can create scenarios with that are compatible with LMCE. Like many of you, I wanted to use ShoutCast stations, however, ShoutCast has changed their webpage in such a way that it will open up it's own propreitary plug-in that doesn't provide you with the actual station's direct URL. Useless, if you want to create a new station scenario in LMCE.

I recommend doing the following:

1. Download WinAmp onto a Windows Box

2. Open up WinAmp and browse to your favorite Station (I use shoutcast stations)

3. Right click on the Winamp window where it lists what you're currently listening to

4. Click "View File Info"

5. This will provide the direct URL link you'll need to include in the steps below when you're creating your stations.

* I hope this helps... I had a hard time finding useful information on where to go to actually get "legitimate" direct URLs for Internet Radio Stations.

==Notes and troubleshooting==

* The media type "4" corresponds to a workaround, MEDIATYPE_pluto_StoredAudio_CONST. When all stuff eventually works, it will be changed to the "6" (MEDIATYPE_pluto_LiveRadio_CONST)

* If radio station playback doesn't start - try playing it a couple times more. There is an issue in xine-lib which sometimes causes it to fail the first time.

* Be sure not to put the URL of the playlist in "#13 Filename" parameter - it should be the URL of the station itself. Playlist URLs usually end with ".m3u" and ".pls". Download the playlist and get the URL of station from it (there can be many entries, each representing a mirror).

* If you have issues identifying your Entertainment Area ID, you can query the DB directly:
:* At the terminal, start the mysql commandline:
mysql -u root -p pluto_main <enter>
:then issue the following query
mysql> SELECT PK_EntertainArea, Description FROM EntertainArea;
:*Select the ID of the desired area from the list:
+------------------+------------------+
| PK_EntertainArea | Description |
+------------------+------------------+
| 1 | Bedroom (Master) |
+------------------+------------------+
1 row in set (0.00 sec)
:type 'quit' to exit:
mysql> quit <enter>

Display Drivers

2008-08-06T21:02:24Z

Usaf-lt-g: /* You will most likely need to generate a new xorg.conf file as well. See the additional steps section on how to do this and how to set it up for your particular setup */

{| align="right"
| __TOC__
|}
[[Category: Tutorials]]
[[Category: Hardware| ]]

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.'''

== Installation ==
If the graphical environment cannot start you are likely to see a text screen blinking, this makes it very hard to login, if this is the case you can reboot into "recovery mode" by pressing [Esc] when GRUB tells you to during the boot process and then select it from the menu you will be presented with.

=== ATI Chipsets ===
The two main ways to install the ATI drivers are described in the [http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide Ubuntu Feisty Installation Guide].

For more information see also the [http://wiki.cchtml.com/index.php/Main_Page Unofficial ATI Linux Driver Wiki] and you might want to have a look at [http://www.mythtv.org/wiki/index.php/AtiProprietaryDriver 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.

==== Installing The ATI Driver ====

Here's the procedure I use for setting up an ATI X1250 MD. Currently the the AVwizard in 0710 does not configure ATI cards properly so you need to to do some manual steps to get things working.

'''Step 1'''

Add the MD in the normal way (ie plug it into the network and let it add itself). Let it reboot and then it should run the AVwizard. Choose the options you want - output connector, resolution, refresh.... UI2 with Overlay etc etc and complete the wizard. Now the screen will return to a console screen and will after 5-10 mins will try to run the setup Wizard... but the setup Wizard will run very slowly and the video of 'Sarah' will not play smoothly. This is because the ATI drivers are not installed yet and the X driver is set to 'vesa'.

'''Step 2'''

From another machine ssh into the partially installed MD using Konsole from the KDE Desktop or a terminal app like Putty under Windows XP. Do the following from the console;

sudo su - <return>
ssh moonNN <return> (**where the NN is the device number for the MD we're configuring**)

Alternatively do the following from the MD/Core you are configuring;

Ctrl+Alt+2

Now login using the login you created when you installed your system ie When you ran the DVD installer or CD installer. Now we're logged into the MD we are configuring as 'root' and we can install the ATI drivers and configure Xorg.conf;

Firstly make sure our sources.list is up to date:

apt-get update <return>

Now lets install the ATI driver and packages;

apt-get install linux-restricted-modules-generic restricted-manager <return>

Answer 'Y' to installing new packages then do the following steps;

apt-get install xorg-driver-fglrx <return>
depmod -a <return>

So far so good... now we have the ATI drivers installed! (the current driver in the repos is not the latest ATI release an updated driver will be packaged soon though). Now we have to configure Xorg to use it! Do the steps below;

I use the console text editor 'joe' below but you can use whichever you prefer ('nano' is installed by default for example);

joe /etc/X11/xorg.conf <return>

Now you are editing the xorg.conf of your MD and the only change you need to make is to the 'Device' section. In the 'Device' section you will see a line thats says;

Driver "vesa"
or
Driver "ati"

Change the string 'vesa' (or ati) to 'fglrx' which is the name of the ATI driver. The updated driver line should look like below;

Driver "fglrx"

Now save the changes you have made to xorg.conf.

Now reboot the MD from the console with;

reboot <return>

The MD will now reboot normally and the setup wizard will run again.... but this time the video and the Ui will run smoothly as the ATI driver is installed and confgured.

Currently the ATI driver will not support UI2 with transparency but it will support UI2 with overlay very nicely indeed. There are two small caveats to running UI2 with Overlay currently with the ATI driver in that the 'Compass Rose' on screen menu for selecting DVD chapters, Lighting levels etc etc and the 'Zoom & Aspect ratio' screen when playing Video do not draw correctly - the bit maps for the menus do not display but the menus do work.

=== NVidia Chipsets ===
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
2. Download the latest [http://www.nvidia.com/object/unix.html linux drivers from NVidia] (depending [http://www.nvidia.com/object/IO_32667.html on your hardware], one of versions: 1XX.XX.XX, 1.0-96xx or 1.0-71XX), if you haven't done so already. When you have found the URL for downloading the package on the nvidia site you could download it like this:
'''root@dcerouter:~#''' wget <nowiki>http://us.download.nvidia.com/XFree86/Linux-x86/</nowiki>''<version>''<nowiki>/NVIDIA-Linux-x86-</nowiki>''<version>''<nowiki>-pkg1.run</nowiki>
3. Go to runlevel 1 to stop the currently running X-server.

NB: There was no need for me to run this command as I was already in Level 1 - It just locked up the keyboard. --[[User:Mortar|Mortar]] 18:12, 6 January 2008 (MST)
'''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.

If the AVWizard crashes (as it did for me when installing the legacy drivers) try setting the '''driver''' option in the ''xorg.conf'' file to '''vesa''', go through the AVWizard and then change it back. --[[User:Zaerc|Zaerc]] 15:14, 5 June 2008 (PDT)

=== Intel Chipsets ===
There is a renewed interest in the Intel graphics chipsets since Intel released the drivers under the GPL. Currently the Intel driver still cannot support UI2 with Alphablending but they will support UI2 with Overlay very nicely and video performance is excellent. LinuxMCE versions after Beta4 have full support for configuring the Intel driver in the AVwizard.

From LinuxMCE-0710 Beta4 onwards LinuxMCE will install the newer intel driver by default - so the instructions below are only useful if your still running LinuxMCE-0704.

==== For LinuxMCE-0704 ====

You will want to make sure you are using the newer intel drivers from http://packages.ubuntu.com/gutsy/i386/xserver-xorg-video-intel/download for i386. These replace the older i810, etc. drivers and should cover all the modern intel chipsets. The name for this driver is 'intel' and would replace the older 'i810' drivers.

If you're using i810 driver make sure you add Option "LinearAlloc" "8160" to xorg.conf or video players will crash with X11 error: BadAlloc.

From man i810:
Option "LinearAlloc" "integer"
Allows more memory for the offscreen allocator. This usually
helps in situations where HDTV movies are required to play but
not enough offscreen memory is usually available. Set this to
8160 for upto 1920x1080 HDTV support. Default 0KB (off).

==== potential problem ====

there can be a problem with some intel drivers, like the gma 3100. see [[bug/gma3100driver]] for further informations

=== Via Chipsets ===
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]

At the time of this writing (10/04/08), the binary Via Unichrome driver (released december 2007) works best (stable, good 2d and 3d) on my Via Mini ITX with CLE266 integerated graphics system. It is able to run UI2 medium with very good performance.
There is a crash at bootup (with any via driver) if the complete runlevel 2 starts.
This issue can be worked around by booting recovery mode and manually starting only /etc/init.d/kdm as root.
Issue under investigation - will update here when good workaround is done.
Contact zeratul at fastmail.fm for latest status/tips

'''HOW-TO VIA Openchrome driver for xorg:''' 
For VIA CX700M2 UniChrome PRO II Graphics (1" VIA units) or mainly via graphics: 
==== NOTE:--[[User:Usaf-lt-g|Usaf-lt-g]] 13:17, 2 August 2008 (PDT) ====

==== --[[User:Usaf-lt-g|Usaf-lt-g]] 14:01, 6 August 2008 (PDT)The steps mentioned BELOW were ONLY successful for UI1 not UI2. I have yet to get UI2 working, however these steps will work for 710 UI1.
 
After following the below directions, you MAY experience your MD locking the next time it boots, if this the case... ssh to your core first and make sure you have root access by issuing the '''sudo -s''' command. 
 
cd /tftpboot/pxelinux.cfg 
 
locate the mac address of the MD and then 
vi <your MAC address here> 
place the '''acpi=off''' command at the end of the APPEND line. 
 
save the file and reboot MD.
 
 

==== NOTE: --[[User:Usaf-lt-g|Usaf-lt-g]] 14:02, 6 August 2008 (PDT) You will most likely need to generate a new xorg.conf file as well. See the additional steps section on how to do this and how to set it up for your particular setup

==== NOTE:[[User:usaf-lt-g|usaf-lt-g]] Sunday July 28th, 2008 ====

----

Burgiman's instructions worked... with some minor modifications. Take note, I had a VERY difficult time first being able to SSH in to my MD. However, note, that I'm using an "earlier" version of LMCE (Beta 3). My MD is also diskless, and NETBIOS handled. If you can't gain root access to your MD through SSH I suggest the following method:

----

--[[User:Usaf-lt-g|Usaf-lt-g]] 22:55, 27 July 2008 (PDT)

''shell into your core as linuxmce / linuxmce and do the following:'' 

----
sudo -s
cd /usr/pluto/diskless
chroot <your MD # found on the linuxmce admin devices page>
(chroot will allow you to access the MD's file system as a root user)
----
''from here I suggest you make a new group and user and then add them to the list of sudoers so that you can easily have SSH access to your MD anytime without this hassle. I did the following:''

----
groupadd parents
useradd -g parents chris
passwd chris
<set your password>
visudo
here you need to add a line below the:
root ALL=(ALL) ALL 
line. Mine was:
chris ALL=(ALL) ALL 
----

''Now you'll be able to login using this user with password you supplied and issue the sudo -s command, which will grant you root access to the MD.''
 
--[[User:Usaf-lt-g|Usaf-lt-g]] 22:55, 27 July 2008 (PDT)
''now from here you're going to need some additional packages installed before you can do anything with the OpenChrome drivers.'' 

----
apt-get install subversion (which will give you the svn command)
apt-get install xserver-xorg-dev 
apt-get install libdrm-dev 
apt-get install libxvmc-dev 
----

''After that, you SHOULD be able to follow the rest of the install below. It worked for me. Hope this helps.''
 
Feel free to edit if necessary.
Chris

====NOTE:[[User:ddamron|ddamron]] Monday June 30, 2008====
Burgiman's instructions did NOT work for me.
Take that for what it's worth.
I had better success installing the VIA Unichrome Driver, and UI1. Use CLE266 mode.
If you have more success, please update this page
Dan

'''UPDATED FOR 0710!'''
--[[User:Burgiman|burgi]] 11:47, 2 June 2008 (PDT)

''shell into your box and do the following:'' 
apt-get install build-essential automake1.9 libtool x11proto-* libgl1-mesa-dev makedepend libxxf86vm-dev libexpat1-dev libexpat1 libxmu-dev xtrans-dev libpng12-dev libxcomposite-dev libxfixes-dev libxdamage-dev libxrandr-dev libxrender-dev libstartup-notification0-dev libgconf2-dev

cd /usr/src
svn checkout http://svn.openchrome.org/svn/trunk openchrome
cd openchrome*
./autogen.sh --prefix=/usr
make
make install

Now we have to edit /etc/X11/xorg.conf and change the device driver to via openchrome: 
vi /etc/X11/xorg.conf
Go to
Section "Device"
and change
Driver "vesa"
to
Driver "openchrome"
save and test the compiled new driver with a: 
X :1
and if your xwindow comes up, you can reboot and have fun 
--[[User:Burgiman|burgi]] 13:37, 3 March 2008 (PST)

=== Other Chipsets ===
Please help out by adding more if you can.

== Configuration ==
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.

=== Getting started ===
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], [[Logging In|log in]], become root and issue the command:
telinit 1
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:
X -configure
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: : 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:
X -scanpci
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 [http://en.wikipedia.org/wiki/Modeline wikipedia entry] to learn how to use modelines.
* http://koala.ilog.fr/cgi-bin/nph-colas-modelines
* http://xtiming.sourceforge.net/cgi-bin/xtiming.pl
* http://www.bohne-lang.de/spec/linux/modeline/
* http://amlc.berlios.de/
* http://www.mythtv.org/wiki/index.php/Working_with_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

=== Chipset driver ===
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.

=== Disable composite ===
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

=== Additional options ===
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 "AIGLX" "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.

== Troubleshooting ==

=== The AVWizard crashes X-windows ===

Try setting the [[#Chipset_driver]] option to '''vesa''', run the AVWizard again and then change the driver back to what it was.

=== Black screen ===

* Screen is black, after install seemed to go okay. You may have even seen the Kubuntu splash screen. See [[AVWizard]] on how to select the proper output.

*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 <pre>Option "ConnectedMonitor" "XXX"</pre>
::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 / ModeLine ]]'' above.

=== Microscopic fonts in KDE ===

See ''[[#Physical_display_size]]'' above.

If the above does not work, probably Xorg is calculating the DPI value in the wrong way.
This can be verified by having a look at the file /var/log/Xorg.0.log related to the MD with this issue searching for the line containing "DPI set to (x , y)",where x and y are values that apply to the specific display.

If those values are too small, fonts will be displayed accordingly (i.e, VERY small)

A workaround is to force Xorg to startup with a given DPI value.

To achieve this the following steps are required:

* edit the file /usr/pluto/bin/Start_X_Wrapper.sh on your MD where you are facing the font problem
* find the line beginning with xinit
* add "-dpi 96" (without quotes) at the end of this line
* save the file and reboot MD

Obviously it is possible to set DPI to something different than 96, according to specific needs.

Please note that after an LMCE update the startup script may be replaced by new ones, so the above workaround may have to be re-applied in order to keep fonts at the desired dimension.

=== LinuxMCE keeps reconfiguring my display settings ===

Add a line containing '''exit''' to the top of the ''/usr/pluto/bin/Xconfigure.sh'' file. After you do this you may experience difficulties running the AVWizard again, if so remove this line and add it back again after the wizard is finished.

For LinuxMCE 710 simply comment out the line that says
. /usr/pluto/bin/X-CleanupVideo.sh
This is the command that gets run that modifies the xorg.conf file on startup. This is different than above because if you put exit at the top your display will not get initialized. And as above if you want to run the AVWizard you will need to uncomment this line.

== See also ==
* [http://www.mythtv.org/wiki/index.php/Main_Page MythTV wiki]
* MythTV Experience [http://brentlagesse.net/~brent/mythtv.php]
* [[X_Configuration_Scripts]]

Display Drivers

2008-08-06T21:01:12Z

Usaf-lt-g: /* The steps mentioned BELOW were ONLY successful for UI1 not UI2. I have yet to get UI2 working, however these steps will work for 710 UI1. */

{| align="right"
| __TOC__
|}
[[Category: Tutorials]]
[[Category: Hardware| ]]

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.'''

== Installation ==
If the graphical environment cannot start you are likely to see a text screen blinking, this makes it very hard to login, if this is the case you can reboot into "recovery mode" by pressing [Esc] when GRUB tells you to during the boot process and then select it from the menu you will be presented with.

=== ATI Chipsets ===
The two main ways to install the ATI drivers are described in the [http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide Ubuntu Feisty Installation Guide].

For more information see also the [http://wiki.cchtml.com/index.php/Main_Page Unofficial ATI Linux Driver Wiki] and you might want to have a look at [http://www.mythtv.org/wiki/index.php/AtiProprietaryDriver 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.

==== Installing The ATI Driver ====

Here's the procedure I use for setting up an ATI X1250 MD. Currently the the AVwizard in 0710 does not configure ATI cards properly so you need to to do some manual steps to get things working.

'''Step 1'''

Add the MD in the normal way (ie plug it into the network and let it add itself). Let it reboot and then it should run the AVwizard. Choose the options you want - output connector, resolution, refresh.... UI2 with Overlay etc etc and complete the wizard. Now the screen will return to a console screen and will after 5-10 mins will try to run the setup Wizard... but the setup Wizard will run very slowly and the video of 'Sarah' will not play smoothly. This is because the ATI drivers are not installed yet and the X driver is set to 'vesa'.

'''Step 2'''

From another machine ssh into the partially installed MD using Konsole from the KDE Desktop or a terminal app like Putty under Windows XP. Do the following from the console;

sudo su - <return>
ssh moonNN <return> (**where the NN is the device number for the MD we're configuring**)

Alternatively do the following from the MD/Core you are configuring;

Ctrl+Alt+2

Now login using the login you created when you installed your system ie When you ran the DVD installer or CD installer. Now we're logged into the MD we are configuring as 'root' and we can install the ATI drivers and configure Xorg.conf;

Firstly make sure our sources.list is up to date:

apt-get update <return>

Now lets install the ATI driver and packages;

apt-get install linux-restricted-modules-generic restricted-manager <return>

Answer 'Y' to installing new packages then do the following steps;

apt-get install xorg-driver-fglrx <return>
depmod -a <return>

So far so good... now we have the ATI drivers installed! (the current driver in the repos is not the latest ATI release an updated driver will be packaged soon though). Now we have to configure Xorg to use it! Do the steps below;

I use the console text editor 'joe' below but you can use whichever you prefer ('nano' is installed by default for example);

joe /etc/X11/xorg.conf <return>

Now you are editing the xorg.conf of your MD and the only change you need to make is to the 'Device' section. In the 'Device' section you will see a line thats says;

Driver "vesa"
or
Driver "ati"

Change the string 'vesa' (or ati) to 'fglrx' which is the name of the ATI driver. The updated driver line should look like below;

Driver "fglrx"

Now save the changes you have made to xorg.conf.

Now reboot the MD from the console with;

reboot <return>

The MD will now reboot normally and the setup wizard will run again.... but this time the video and the Ui will run smoothly as the ATI driver is installed and confgured.

Currently the ATI driver will not support UI2 with transparency but it will support UI2 with overlay very nicely indeed. There are two small caveats to running UI2 with Overlay currently with the ATI driver in that the 'Compass Rose' on screen menu for selecting DVD chapters, Lighting levels etc etc and the 'Zoom & Aspect ratio' screen when playing Video do not draw correctly - the bit maps for the menus do not display but the menus do work.

=== NVidia Chipsets ===
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
2. Download the latest [http://www.nvidia.com/object/unix.html linux drivers from NVidia] (depending [http://www.nvidia.com/object/IO_32667.html on your hardware], one of versions: 1XX.XX.XX, 1.0-96xx or 1.0-71XX), if you haven't done so already. When you have found the URL for downloading the package on the nvidia site you could download it like this:
'''root@dcerouter:~#''' wget <nowiki>http://us.download.nvidia.com/XFree86/Linux-x86/</nowiki>''<version>''<nowiki>/NVIDIA-Linux-x86-</nowiki>''<version>''<nowiki>-pkg1.run</nowiki>
3. Go to runlevel 1 to stop the currently running X-server.

NB: There was no need for me to run this command as I was already in Level 1 - It just locked up the keyboard. --[[User:Mortar|Mortar]] 18:12, 6 January 2008 (MST)
'''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.

If the AVWizard crashes (as it did for me when installing the legacy drivers) try setting the '''driver''' option in the ''xorg.conf'' file to '''vesa''', go through the AVWizard and then change it back. --[[User:Zaerc|Zaerc]] 15:14, 5 June 2008 (PDT)

=== Intel Chipsets ===
There is a renewed interest in the Intel graphics chipsets since Intel released the drivers under the GPL. Currently the Intel driver still cannot support UI2 with Alphablending but they will support UI2 with Overlay very nicely and video performance is excellent. LinuxMCE versions after Beta4 have full support for configuring the Intel driver in the AVwizard.

From LinuxMCE-0710 Beta4 onwards LinuxMCE will install the newer intel driver by default - so the instructions below are only useful if your still running LinuxMCE-0704.

==== For LinuxMCE-0704 ====

You will want to make sure you are using the newer intel drivers from http://packages.ubuntu.com/gutsy/i386/xserver-xorg-video-intel/download for i386. These replace the older i810, etc. drivers and should cover all the modern intel chipsets. The name for this driver is 'intel' and would replace the older 'i810' drivers.

If you're using i810 driver make sure you add Option "LinearAlloc" "8160" to xorg.conf or video players will crash with X11 error: BadAlloc.

From man i810:
Option "LinearAlloc" "integer"
Allows more memory for the offscreen allocator. This usually
helps in situations where HDTV movies are required to play but
not enough offscreen memory is usually available. Set this to
8160 for upto 1920x1080 HDTV support. Default 0KB (off).

==== potential problem ====

there can be a problem with some intel drivers, like the gma 3100. see [[bug/gma3100driver]] for further informations

=== Via Chipsets ===
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]

At the time of this writing (10/04/08), the binary Via Unichrome driver (released december 2007) works best (stable, good 2d and 3d) on my Via Mini ITX with CLE266 integerated graphics system. It is able to run UI2 medium with very good performance.
There is a crash at bootup (with any via driver) if the complete runlevel 2 starts.
This issue can be worked around by booting recovery mode and manually starting only /etc/init.d/kdm as root.
Issue under investigation - will update here when good workaround is done.
Contact zeratul at fastmail.fm for latest status/tips

'''HOW-TO VIA Openchrome driver for xorg:''' 
For VIA CX700M2 UniChrome PRO II Graphics (1" VIA units) or mainly via graphics: 
==== NOTE:--[[User:Usaf-lt-g|Usaf-lt-g]] 13:17, 2 August 2008 (PDT) ====

==== --[[User:Usaf-lt-g|Usaf-lt-g]] 14:01, 6 August 2008 (PDT)The steps mentioned BELOW were ONLY successful for UI1 not UI2. I have yet to get UI2 working, however these steps will work for 710 UI1.
 
After following the below directions, you MAY experience your MD locking the next time it boots, if this the case... ssh to your core first and make sure you have root access by issuing the '''sudo -s''' command. 
 
cd /tftpboot/pxelinux.cfg 
 
locate the mac address of the MD and then 
vi <your MAC address here> 
place the '''acpi=off''' command at the end of the APPEND line. 
 
save the file and reboot MD.
 
 

== You will most likely need to generate a new xorg.conf file as well. See the additional steps section on how to do this and how to set it up for your particular setup ==

==== NOTE:[[User:usaf-lt-g|usaf-lt-g]] Sunday July 28th, 2008 ====

----

Burgiman's instructions worked... with some minor modifications. Take note, I had a VERY difficult time first being able to SSH in to my MD. However, note, that I'm using an "earlier" version of LMCE (Beta 3). My MD is also diskless, and NETBIOS handled. If you can't gain root access to your MD through SSH I suggest the following method:

----

--[[User:Usaf-lt-g|Usaf-lt-g]] 22:55, 27 July 2008 (PDT)

''shell into your core as linuxmce / linuxmce and do the following:'' 

----
sudo -s
cd /usr/pluto/diskless
chroot <your MD # found on the linuxmce admin devices page>
(chroot will allow you to access the MD's file system as a root user)
----
''from here I suggest you make a new group and user and then add them to the list of sudoers so that you can easily have SSH access to your MD anytime without this hassle. I did the following:''

----
groupadd parents
useradd -g parents chris
passwd chris
<set your password>
visudo
here you need to add a line below the:
root ALL=(ALL) ALL 
line. Mine was:
chris ALL=(ALL) ALL 
----

''Now you'll be able to login using this user with password you supplied and issue the sudo -s command, which will grant you root access to the MD.''
 
--[[User:Usaf-lt-g|Usaf-lt-g]] 22:55, 27 July 2008 (PDT)
''now from here you're going to need some additional packages installed before you can do anything with the OpenChrome drivers.'' 

----
apt-get install subversion (which will give you the svn command)
apt-get install xserver-xorg-dev 
apt-get install libdrm-dev 
apt-get install libxvmc-dev 
----

''After that, you SHOULD be able to follow the rest of the install below. It worked for me. Hope this helps.''
 
Feel free to edit if necessary.
Chris

====NOTE:[[User:ddamron|ddamron]] Monday June 30, 2008====
Burgiman's instructions did NOT work for me.
Take that for what it's worth.
I had better success installing the VIA Unichrome Driver, and UI1. Use CLE266 mode.
If you have more success, please update this page
Dan

'''UPDATED FOR 0710!'''
--[[User:Burgiman|burgi]] 11:47, 2 June 2008 (PDT)

''shell into your box and do the following:'' 
apt-get install build-essential automake1.9 libtool x11proto-* libgl1-mesa-dev makedepend libxxf86vm-dev libexpat1-dev libexpat1 libxmu-dev xtrans-dev libpng12-dev libxcomposite-dev libxfixes-dev libxdamage-dev libxrandr-dev libxrender-dev libstartup-notification0-dev libgconf2-dev

cd /usr/src
svn checkout http://svn.openchrome.org/svn/trunk openchrome
cd openchrome*
./autogen.sh --prefix=/usr
make
make install

Now we have to edit /etc/X11/xorg.conf and change the device driver to via openchrome: 
vi /etc/X11/xorg.conf
Go to
Section "Device"
and change
Driver "vesa"
to
Driver "openchrome"
save and test the compiled new driver with a: 
X :1
and if your xwindow comes up, you can reboot and have fun 
--[[User:Burgiman|burgi]] 13:37, 3 March 2008 (PST)

=== Other Chipsets ===
Please help out by adding more if you can.

== Configuration ==
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.

=== Getting started ===
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], [[Logging In|log in]], become root and issue the command:
telinit 1
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:
X -configure
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: : 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:
X -scanpci
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 [http://en.wikipedia.org/wiki/Modeline wikipedia entry] to learn how to use modelines.
* http://koala.ilog.fr/cgi-bin/nph-colas-modelines
* http://xtiming.sourceforge.net/cgi-bin/xtiming.pl
* http://www.bohne-lang.de/spec/linux/modeline/
* http://amlc.berlios.de/
* http://www.mythtv.org/wiki/index.php/Working_with_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

=== Chipset driver ===
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.

=== Disable composite ===
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

=== Additional options ===
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 "AIGLX" "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.

== Troubleshooting ==

=== The AVWizard crashes X-windows ===

Try setting the [[#Chipset_driver]] option to '''vesa''', run the AVWizard again and then change the driver back to what it was.

=== Black screen ===

* Screen is black, after install seemed to go okay. You may have even seen the Kubuntu splash screen. See [[AVWizard]] on how to select the proper output.

*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 <pre>Option "ConnectedMonitor" "XXX"</pre>
::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 / ModeLine ]]'' above.

=== Microscopic fonts in KDE ===

See ''[[#Physical_display_size]]'' above.

If the above does not work, probably Xorg is calculating the DPI value in the wrong way.
This can be verified by having a look at the file /var/log/Xorg.0.log related to the MD with this issue searching for the line containing "DPI set to (x , y)",where x and y are values that apply to the specific display.

If those values are too small, fonts will be displayed accordingly (i.e, VERY small)

A workaround is to force Xorg to startup with a given DPI value.

To achieve this the following steps are required:

* edit the file /usr/pluto/bin/Start_X_Wrapper.sh on your MD where you are facing the font problem
* find the line beginning with xinit
* add "-dpi 96" (without quotes) at the end of this line
* save the file and reboot MD

Obviously it is possible to set DPI to something different than 96, according to specific needs.

Please note that after an LMCE update the startup script may be replaced by new ones, so the above workaround may have to be re-applied in order to keep fonts at the desired dimension.

=== LinuxMCE keeps reconfiguring my display settings ===

Add a line containing '''exit''' to the top of the ''/usr/pluto/bin/Xconfigure.sh'' file. After you do this you may experience difficulties running the AVWizard again, if so remove this line and add it back again after the wizard is finished.

For LinuxMCE 710 simply comment out the line that says
. /usr/pluto/bin/X-CleanupVideo.sh
This is the command that gets run that modifies the xorg.conf file on startup. This is different than above because if you put exit at the top your display will not get initialized. And as above if you want to run the AVWizard you will need to uncomment this line.

== See also ==
* [http://www.mythtv.org/wiki/index.php/Main_Page MythTV wiki]
* MythTV Experience [http://brentlagesse.net/~brent/mythtv.php]
* [[X_Configuration_Scripts]]

Display Drivers

2008-08-06T20:59:56Z

Usaf-lt-g: /* NOTE:--Usaf-lt-g 13:17, 2 August 2008 (PDT) */

{| align="right"
| __TOC__
|}
[[Category: Tutorials]]
[[Category: Hardware| ]]

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.'''

== Installation ==
If the graphical environment cannot start you are likely to see a text screen blinking, this makes it very hard to login, if this is the case you can reboot into "recovery mode" by pressing [Esc] when GRUB tells you to during the boot process and then select it from the menu you will be presented with.

=== ATI Chipsets ===
The two main ways to install the ATI drivers are described in the [http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide Ubuntu Feisty Installation Guide].

For more information see also the [http://wiki.cchtml.com/index.php/Main_Page Unofficial ATI Linux Driver Wiki] and you might want to have a look at [http://www.mythtv.org/wiki/index.php/AtiProprietaryDriver 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.

==== Installing The ATI Driver ====

Here's the procedure I use for setting up an ATI X1250 MD. Currently the the AVwizard in 0710 does not configure ATI cards properly so you need to to do some manual steps to get things working.

'''Step 1'''

Add the MD in the normal way (ie plug it into the network and let it add itself). Let it reboot and then it should run the AVwizard. Choose the options you want - output connector, resolution, refresh.... UI2 with Overlay etc etc and complete the wizard. Now the screen will return to a console screen and will after 5-10 mins will try to run the setup Wizard... but the setup Wizard will run very slowly and the video of 'Sarah' will not play smoothly. This is because the ATI drivers are not installed yet and the X driver is set to 'vesa'.

'''Step 2'''

From another machine ssh into the partially installed MD using Konsole from the KDE Desktop or a terminal app like Putty under Windows XP. Do the following from the console;

sudo su - <return>
ssh moonNN <return> (**where the NN is the device number for the MD we're configuring**)

Alternatively do the following from the MD/Core you are configuring;

Ctrl+Alt+2

Now login using the login you created when you installed your system ie When you ran the DVD installer or CD installer. Now we're logged into the MD we are configuring as 'root' and we can install the ATI drivers and configure Xorg.conf;

Firstly make sure our sources.list is up to date:

apt-get update <return>

Now lets install the ATI driver and packages;

apt-get install linux-restricted-modules-generic restricted-manager <return>

Answer 'Y' to installing new packages then do the following steps;

apt-get install xorg-driver-fglrx <return>
depmod -a <return>

So far so good... now we have the ATI drivers installed! (the current driver in the repos is not the latest ATI release an updated driver will be packaged soon though). Now we have to configure Xorg to use it! Do the steps below;

I use the console text editor 'joe' below but you can use whichever you prefer ('nano' is installed by default for example);

joe /etc/X11/xorg.conf <return>

Now you are editing the xorg.conf of your MD and the only change you need to make is to the 'Device' section. In the 'Device' section you will see a line thats says;

Driver "vesa"
or
Driver "ati"

Change the string 'vesa' (or ati) to 'fglrx' which is the name of the ATI driver. The updated driver line should look like below;

Driver "fglrx"

Now save the changes you have made to xorg.conf.

Now reboot the MD from the console with;

reboot <return>

The MD will now reboot normally and the setup wizard will run again.... but this time the video and the Ui will run smoothly as the ATI driver is installed and confgured.

Currently the ATI driver will not support UI2 with transparency but it will support UI2 with overlay very nicely indeed. There are two small caveats to running UI2 with Overlay currently with the ATI driver in that the 'Compass Rose' on screen menu for selecting DVD chapters, Lighting levels etc etc and the 'Zoom & Aspect ratio' screen when playing Video do not draw correctly - the bit maps for the menus do not display but the menus do work.

=== NVidia Chipsets ===
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
2. Download the latest [http://www.nvidia.com/object/unix.html linux drivers from NVidia] (depending [http://www.nvidia.com/object/IO_32667.html on your hardware], one of versions: 1XX.XX.XX, 1.0-96xx or 1.0-71XX), if you haven't done so already. When you have found the URL for downloading the package on the nvidia site you could download it like this:
'''root@dcerouter:~#''' wget <nowiki>http://us.download.nvidia.com/XFree86/Linux-x86/</nowiki>''<version>''<nowiki>/NVIDIA-Linux-x86-</nowiki>''<version>''<nowiki>-pkg1.run</nowiki>
3. Go to runlevel 1 to stop the currently running X-server.

NB: There was no need for me to run this command as I was already in Level 1 - It just locked up the keyboard. --[[User:Mortar|Mortar]] 18:12, 6 January 2008 (MST)
'''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.

If the AVWizard crashes (as it did for me when installing the legacy drivers) try setting the '''driver''' option in the ''xorg.conf'' file to '''vesa''', go through the AVWizard and then change it back. --[[User:Zaerc|Zaerc]] 15:14, 5 June 2008 (PDT)

=== Intel Chipsets ===
There is a renewed interest in the Intel graphics chipsets since Intel released the drivers under the GPL. Currently the Intel driver still cannot support UI2 with Alphablending but they will support UI2 with Overlay very nicely and video performance is excellent. LinuxMCE versions after Beta4 have full support for configuring the Intel driver in the AVwizard.

From LinuxMCE-0710 Beta4 onwards LinuxMCE will install the newer intel driver by default - so the instructions below are only useful if your still running LinuxMCE-0704.

==== For LinuxMCE-0704 ====

You will want to make sure you are using the newer intel drivers from http://packages.ubuntu.com/gutsy/i386/xserver-xorg-video-intel/download for i386. These replace the older i810, etc. drivers and should cover all the modern intel chipsets. The name for this driver is 'intel' and would replace the older 'i810' drivers.

If you're using i810 driver make sure you add Option "LinearAlloc" "8160" to xorg.conf or video players will crash with X11 error: BadAlloc.

From man i810:
Option "LinearAlloc" "integer"
Allows more memory for the offscreen allocator. This usually
helps in situations where HDTV movies are required to play but
not enough offscreen memory is usually available. Set this to
8160 for upto 1920x1080 HDTV support. Default 0KB (off).

==== potential problem ====

there can be a problem with some intel drivers, like the gma 3100. see [[bug/gma3100driver]] for further informations

=== Via Chipsets ===
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]

At the time of this writing (10/04/08), the binary Via Unichrome driver (released december 2007) works best (stable, good 2d and 3d) on my Via Mini ITX with CLE266 integerated graphics system. It is able to run UI2 medium with very good performance.
There is a crash at bootup (with any via driver) if the complete runlevel 2 starts.
This issue can be worked around by booting recovery mode and manually starting only /etc/init.d/kdm as root.
Issue under investigation - will update here when good workaround is done.
Contact zeratul at fastmail.fm for latest status/tips

'''HOW-TO VIA Openchrome driver for xorg:''' 
For VIA CX700M2 UniChrome PRO II Graphics (1" VIA units) or mainly via graphics: 
==== NOTE:--[[User:Usaf-lt-g|Usaf-lt-g]] 13:17, 2 August 2008 (PDT) ====

== The steps mentioned BELOW were ONLY successful for UI1 not UI2. I have yet to get UI2 working, however these steps will work for 710 UI1. ==
 
After following the below directions, you MAY experience your MD locking the next time it boots, if this the case... ssh to your core first and make sure you have root access by issuing the '''sudo -s''' command. 
 
cd /tftpboot/pxelinux.cfg 
 
locate the mac address of the MD and then 
vi <your MAC address here> 
place the '''acpi=off''' command at the end of the APPEND line. 
 
save the file and reboot MD.
 
 

== You will most likely need to generate a new xorg.conf file as well. See the additional steps section on how to do this and how to set it up for your particular setup ==

==== NOTE:[[User:usaf-lt-g|usaf-lt-g]] Sunday July 28th, 2008 ====

----

Burgiman's instructions worked... with some minor modifications. Take note, I had a VERY difficult time first being able to SSH in to my MD. However, note, that I'm using an "earlier" version of LMCE (Beta 3). My MD is also diskless, and NETBIOS handled. If you can't gain root access to your MD through SSH I suggest the following method:

----

--[[User:Usaf-lt-g|Usaf-lt-g]] 22:55, 27 July 2008 (PDT)

''shell into your core as linuxmce / linuxmce and do the following:'' 

----
sudo -s
cd /usr/pluto/diskless
chroot <your MD # found on the linuxmce admin devices page>
(chroot will allow you to access the MD's file system as a root user)
----
''from here I suggest you make a new group and user and then add them to the list of sudoers so that you can easily have SSH access to your MD anytime without this hassle. I did the following:''

----
groupadd parents
useradd -g parents chris
passwd chris
<set your password>
visudo
here you need to add a line below the:
root ALL=(ALL) ALL 
line. Mine was:
chris ALL=(ALL) ALL 
----

''Now you'll be able to login using this user with password you supplied and issue the sudo -s command, which will grant you root access to the MD.''
 
--[[User:Usaf-lt-g|Usaf-lt-g]] 22:55, 27 July 2008 (PDT)
''now from here you're going to need some additional packages installed before you can do anything with the OpenChrome drivers.'' 

----
apt-get install subversion (which will give you the svn command)
apt-get install xserver-xorg-dev 
apt-get install libdrm-dev 
apt-get install libxvmc-dev 
----

''After that, you SHOULD be able to follow the rest of the install below. It worked for me. Hope this helps.''
 
Feel free to edit if necessary.
Chris

====NOTE:[[User:ddamron|ddamron]] Monday June 30, 2008====
Burgiman's instructions did NOT work for me.
Take that for what it's worth.
I had better success installing the VIA Unichrome Driver, and UI1. Use CLE266 mode.
If you have more success, please update this page
Dan

'''UPDATED FOR 0710!'''
--[[User:Burgiman|burgi]] 11:47, 2 June 2008 (PDT)

''shell into your box and do the following:'' 
apt-get install build-essential automake1.9 libtool x11proto-* libgl1-mesa-dev makedepend libxxf86vm-dev libexpat1-dev libexpat1 libxmu-dev xtrans-dev libpng12-dev libxcomposite-dev libxfixes-dev libxdamage-dev libxrandr-dev libxrender-dev libstartup-notification0-dev libgconf2-dev

cd /usr/src
svn checkout http://svn.openchrome.org/svn/trunk openchrome
cd openchrome*
./autogen.sh --prefix=/usr
make
make install

Now we have to edit /etc/X11/xorg.conf and change the device driver to via openchrome: 
vi /etc/X11/xorg.conf
Go to
Section "Device"
and change
Driver "vesa"
to
Driver "openchrome"
save and test the compiled new driver with a: 
X :1
and if your xwindow comes up, you can reboot and have fun 
--[[User:Burgiman|burgi]] 13:37, 3 March 2008 (PST)

=== Other Chipsets ===
Please help out by adding more if you can.

== Configuration ==
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.

=== Getting started ===
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], [[Logging In|log in]], become root and issue the command:
telinit 1
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:
X -configure
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: : 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:
X -scanpci
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 [http://en.wikipedia.org/wiki/Modeline wikipedia entry] to learn how to use modelines.
* http://koala.ilog.fr/cgi-bin/nph-colas-modelines
* http://xtiming.sourceforge.net/cgi-bin/xtiming.pl
* http://www.bohne-lang.de/spec/linux/modeline/
* http://amlc.berlios.de/
* http://www.mythtv.org/wiki/index.php/Working_with_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

=== Chipset driver ===
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.

=== Disable composite ===
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

=== Additional options ===
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 "AIGLX" "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.

== Troubleshooting ==

=== The AVWizard crashes X-windows ===

Try setting the [[#Chipset_driver]] option to '''vesa''', run the AVWizard again and then change the driver back to what it was.

=== Black screen ===

* Screen is black, after install seemed to go okay. You may have even seen the Kubuntu splash screen. See [[AVWizard]] on how to select the proper output.

*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 <pre>Option "ConnectedMonitor" "XXX"</pre>
::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 / ModeLine ]]'' above.

=== Microscopic fonts in KDE ===

See ''[[#Physical_display_size]]'' above.

If the above does not work, probably Xorg is calculating the DPI value in the wrong way.
This can be verified by having a look at the file /var/log/Xorg.0.log related to the MD with this issue searching for the line containing "DPI set to (x , y)",where x and y are values that apply to the specific display.

If those values are too small, fonts will be displayed accordingly (i.e, VERY small)

A workaround is to force Xorg to startup with a given DPI value.

To achieve this the following steps are required:

* edit the file /usr/pluto/bin/Start_X_Wrapper.sh on your MD where you are facing the font problem
* find the line beginning with xinit
* add "-dpi 96" (without quotes) at the end of this line
* save the file and reboot MD

Obviously it is possible to set DPI to something different than 96, according to specific needs.

Please note that after an LMCE update the startup script may be replaced by new ones, so the above workaround may have to be re-applied in order to keep fonts at the desired dimension.

=== LinuxMCE keeps reconfiguring my display settings ===

Add a line containing '''exit''' to the top of the ''/usr/pluto/bin/Xconfigure.sh'' file. After you do this you may experience difficulties running the AVWizard again, if so remove this line and add it back again after the wizard is finished.

For LinuxMCE 710 simply comment out the line that says
. /usr/pluto/bin/X-CleanupVideo.sh
This is the command that gets run that modifies the xorg.conf file on startup. This is different than above because if you put exit at the top your display will not get initialized. And as above if you want to run the AVWizard you will need to uncomment this line.

== See also ==
* [http://www.mythtv.org/wiki/index.php/Main_Page MythTV wiki]
* MythTV Experience [http://brentlagesse.net/~brent/mythtv.php]
* [[X_Configuration_Scripts]]

Display Drivers

2008-08-02T20:17:37Z

Usaf-lt-g: /* NOTE:usaf-lt-g Sunday July 28th, 2008 */

{| align="right"
| __TOC__
|}
[[Category: Tutorials]]
[[Category: Hardware| ]]

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.'''

== Installation ==
If the graphical environment cannot start you are likely to see a text screen blinking, this makes it very hard to login, if this is the case you can reboot into "recovery mode" by pressing [Esc] when GRUB tells you to during the boot process and then select it from the menu you will be presented with.

=== ATI Chipsets ===
The two main ways to install the ATI drivers are described in the [http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide Ubuntu Feisty Installation Guide].

For more information see also the [http://wiki.cchtml.com/index.php/Main_Page Unofficial ATI Linux Driver Wiki] and you might want to have a look at [http://www.mythtv.org/wiki/index.php/AtiProprietaryDriver 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.

==== Installing The ATI Driver ====

Here's the procedure I use for setting up an ATI X1250 MD. Currently the the AVwizard in 0710 does not configure ATI cards properly so you need to to do some manual steps to get things working.

'''Step 1'''

Add the MD in the normal way (ie plug it into the network and let it add itself). Let it reboot and then it should run the AVwizard. Choose the options you want - output connector, resolution, refresh.... UI2 with Overlay etc etc and complete the wizard. Now the screen will return to a console screen and will after 5-10 mins will try to run the setup Wizard... but the setup Wizard will run very slowly and the video of 'Sarah' will not play smoothly. This is because the ATI drivers are not installed yet and the X driver is set to 'vesa'.

'''Step 2'''

From another machine ssh into the partially installed MD using Konsole from the KDE Desktop or a terminal app like Putty under Windows XP. Do the following from the console;

sudo su - <return>
ssh moonNN <return> (**where the NN is the device number for the MD we're configuring**)

Alternatively do the following from the MD/Core you are configuring;

Ctrl+Alt+2

Now login using the login you created when you installed your system ie When you ran the DVD installer or CD installer. Now we're logged into the MD we are configuring as 'root' and we can install the ATI drivers and configure Xorg.conf;

Firstly make sure our sources.list is up to date:

apt-get update <return>

Now lets install the ATI driver and packages;

apt-get install linux-restricted-modules-generic restricted-manager <return>

Answer 'Y' to installing new packages then do the following steps;

apt-get install xorg-driver-fglrx <return>
depmod -a <return>

So far so good... now we have the ATI drivers installed! (the current driver in the repos is not the latest ATI release an updated driver will be packaged soon though). Now we have to configure Xorg to use it! Do the steps below;

I use the console text editor 'joe' below but you can use whichever you prefer ('nano' is installed by default for example);

joe /etc/X11/xorg.conf <return>

Now you are editing the xorg.conf of your MD and the only change you need to make is to the 'Device' section. In the 'Device' section you will see a line thats says;

Driver "vesa"
or
Driver "ati"

Change the string 'vesa' (or ati) to 'fglrx' which is the name of the ATI driver. The updated driver line should look like below;

Driver "fglrx"

Now save the changes you have made to xorg.conf.

Now reboot the MD from the console with;

reboot <return>

The MD will now reboot normally and the setup wizard will run again.... but this time the video and the Ui will run smoothly as the ATI driver is installed and confgured.

Currently the ATI driver will not support UI2 with transparency but it will support UI2 with overlay very nicely indeed. There are two small caveats to running UI2 with Overlay currently with the ATI driver in that the 'Compass Rose' on screen menu for selecting DVD chapters, Lighting levels etc etc and the 'Zoom & Aspect ratio' screen when playing Video do not draw correctly - the bit maps for the menus do not display but the menus do work.

=== NVidia Chipsets ===
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
2. Download the latest [http://www.nvidia.com/object/unix.html linux drivers from NVidia] (depending [http://www.nvidia.com/object/IO_32667.html on your hardware], one of versions: 1XX.XX.XX, 1.0-96xx or 1.0-71XX), if you haven't done so already. When you have found the URL for downloading the package on the nvidia site you could download it like this:
'''root@dcerouter:~#''' wget <nowiki>http://us.download.nvidia.com/XFree86/Linux-x86/</nowiki>''<version>''<nowiki>/NVIDIA-Linux-x86-</nowiki>''<version>''<nowiki>-pkg1.run</nowiki>
3. Go to runlevel 1 to stop the currently running X-server.

NB: There was no need for me to run this command as I was already in Level 1 - It just locked up the keyboard. --[[User:Mortar|Mortar]] 18:12, 6 January 2008 (MST)
'''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.

If the AVWizard crashes (as it did for me when installing the legacy drivers) try setting the '''driver''' option in the ''xorg.conf'' file to '''vesa''', go through the AVWizard and then change it back. --[[User:Zaerc|Zaerc]] 15:14, 5 June 2008 (PDT)

=== Intel Chipsets ===
There is a renewed interest in the Intel graphics chipsets since Intel released the drivers under the GPL. Currently the Intel driver still cannot support UI2 with Alphablending but they will support UI2 with Overlay very nicely and video performance is excellent. LinuxMCE versions after Beta4 have full support for configuring the Intel driver in the AVwizard.

From LinuxMCE-0710 Beta4 onwards LinuxMCE will install the newer intel driver by default - so the instructions below are only useful if your still running LinuxMCE-0704.

==== For LinuxMCE-0704 ====

You will want to make sure you are using the newer intel drivers from http://packages.ubuntu.com/gutsy/i386/xserver-xorg-video-intel/download for i386. These replace the older i810, etc. drivers and should cover all the modern intel chipsets. The name for this driver is 'intel' and would replace the older 'i810' drivers.

If you're using i810 driver make sure you add Option "LinearAlloc" "8160" to xorg.conf or video players will crash with X11 error: BadAlloc.

From man i810:
Option "LinearAlloc" "integer"
Allows more memory for the offscreen allocator. This usually
helps in situations where HDTV movies are required to play but
not enough offscreen memory is usually available. Set this to
8160 for upto 1920x1080 HDTV support. Default 0KB (off).

==== potential problem ====

there can be a problem with some intel drivers, like the gma 3100. see [[bug/gma3100driver]] for further informations

=== Via Chipsets ===
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]

At the time of this writing (10/04/08), the binary Via Unichrome driver (released december 2007) works best (stable, good 2d and 3d) on my Via Mini ITX with CLE266 integerated graphics system. It is able to run UI2 medium with very good performance.
There is a crash at bootup (with any via driver) if the complete runlevel 2 starts.
This issue can be worked around by booting recovery mode and manually starting only /etc/init.d/kdm as root.
Issue under investigation - will update here when good workaround is done.
Contact zeratul at fastmail.fm for latest status/tips

'''HOW-TO VIA Openchrome driver for xorg:''' 
For VIA CX700M2 UniChrome PRO II Graphics (1" VIA units) or mainly via graphics: 
===NOTE:--[[User:Usaf-lt-g|Usaf-lt-g]] 13:17, 2 August 2008 (PDT)===

After following the below directions, you MAY experience your MD locking the next time it boots, if this the case... ssh to your core first and make sure you have root access by issuing the '''sudo -s''' command. 
 
cd /tftpboot/pxelinux.cfg 
 
locate the mac address of the MD and then 
vi <your MAC address here> 
place the '''acpi=off''' command at the end of the APPEND line. 
 
save the file and reboot MD.

===NOTE:[[User:usaf-lt-g|usaf-lt-g]] Sunday July 28th, 2008===

----

Burgiman's instructions worked... with some minor modifications. Take note, I had a VERY difficult time first being able to SSH in to my MD. However, note, that I'm using an "earlier" version of LMCE (Beta 3). My MD is also diskless, and NETBIOS handled. If you can't gain root access to your MD through SSH I suggest the following method:

----

--[[User:Usaf-lt-g|Usaf-lt-g]] 22:55, 27 July 2008 (PDT)

''shell into your core as linuxmce / linuxmce and do the following:'' 

----
sudo -s 
cd /usr/pluto/diskless 
chroot <your MD # found on the linuxmce admin devices page> 
(chroot will allow you to access the MD's file system as a root user) 
----
''from here I suggest you make a new group and user and then add them to the list of sudoers so that you can easily have SSH access to your MD anytime without this hassle. I did the following:''

----
groupadd parents 
useradd -g parents chris 
passwd chris 
<set your password> 
 
visudo 
 
here you need to add a line below the: root ALL=(ALL) ALL line. Mine was: 
 
chris ALL=(ALL) ALL 
----

''Now you'll be able to login using this user with password you supplied and issue the sudo -s command, which will grant you root access to the MD.''
 
--[[User:Usaf-lt-g|Usaf-lt-g]] 22:55, 27 July 2008 (PDT)
''now from here you're going to need some additional packages installed before you can do anything with the OpenChrome drivers.'' 

----
apt-get install subversion (which will give you the svn command) 
 
apt-get install xserver-xorg-dev 
apt-get install libdrm-dev 
apt-get install libxvmc-dev 
----

''After that, you SHOULD be able to follow the rest of the install below. It worked for me. Hope this helps.''
 
Feel free to edit if necessary.
Chris

===NOTE:[[User:ddamron|ddamron]] Monday June 30, 2008===
Burgiman's instructions did NOT work for me.
Take that for what it's worth.
I had better success installing the VIA Unichrome Driver, and UI1. Use CLE266 mode.
If you have more success, please update this page
Dan

'''UPDATED FOR 0710!'''
--[[User:Burgiman|burgi]] 11:47, 2 June 2008 (PDT)

''shell into your box and do the following:'' 
apt-get install build-essential automake1.9 libtool x11proto-* libgl1-mesa-dev makedepend libxxf86vm-dev libexpat1-dev libexpat1 libxmu-dev xtrans-dev libpng12-dev libxcomposite-dev libxfixes-dev libxdamage-dev libxrandr-dev libxrender-dev libstartup-notification0-dev libgconf2-dev

cd /usr/src
svn checkout http://svn.openchrome.org/svn/trunk openchrome
cd openchrome*
./autogen.sh --prefix=/usr
make
make install

Now we have to edit /etc/X11/xorg.conf and change the device driver to via openchrome: 
vi /etc/X11/xorg.conf
Go to
Section "Device"
and change
Driver "vesa"
to
Driver "openchrome"
save and test the compiled new driver with a: 
X :1
and if your xwindow comes up, you can reboot and have fun 
--[[User:Burgiman|burgi]] 13:37, 3 March 2008 (PST)

=== Other Chipsets ===
Please help out by adding more if you can.

== Configuration ==
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.

=== Getting started ===
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], [[Logging In|log in]], become root and issue the command:
telinit 1
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:
X -configure
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: : 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:
X -scanpci
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 [http://en.wikipedia.org/wiki/Modeline wikipedia entry] to learn how to use modelines.
* http://koala.ilog.fr/cgi-bin/nph-colas-modelines
* http://xtiming.sourceforge.net/cgi-bin/xtiming.pl
* http://www.bohne-lang.de/spec/linux/modeline/
* http://amlc.berlios.de/
* http://www.mythtv.org/wiki/index.php/Working_with_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

=== Chipset driver ===
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.

=== Disable composite ===
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

=== Additional options ===
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 "AIGLX" "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.

== Troubleshooting ==

=== The AVWizard crashes X-windows ===

Try setting the [[#Chipset_driver]] option to '''vesa''', run the AVWizard again and then change the driver back to what it was.

=== Black screen ===

* Screen is black, after install seemed to go okay. You may have even seen the Kubuntu splash screen. See [[AVWizard]] on how to select the proper output.

*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 <pre>Option "ConnectedMonitor" "XXX"</pre>
::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 / ModeLine ]]'' above.

=== Microscopic fonts in KDE ===

See ''[[#Physical_display_size]]'' above.

If the above does not work, probably Xorg is calculating the DPI value in the wrong way.
This can be verified by having a look at the file /var/log/Xorg.0.log related to the MD with this issue searching for the line containing "DPI set to (x , y)",where x and y are values that apply to the specific display.

If those values are too small, fonts will be displayed accordingly (i.e, VERY small)

A workaround is to force Xorg to startup with a given DPI value.

To achieve this the following steps are required:

* edit the file /usr/pluto/bin/Start_X_Wrapper.sh on your MD where you are facing the font problem
* find the line beginning with xinit
* add "-dpi 96" (without quotes) at the end of this line
* save the file and reboot MD

Obviously it is possible to set DPI to something different than 96, according to specific needs.

Please note that after an LMCE update the startup script may be replaced by new ones, so the above workaround may have to be re-applied in order to keep fonts at the desired dimension.

=== LinuxMCE keeps reconfiguring my display settings ===

Add a line containing '''exit''' to the top of the ''/usr/pluto/bin/Xconfigure.sh'' file. After you do this you may experience difficulties running the AVWizard again, if so remove this line and add it back again after the wizard is finished.

For LinuxMCE 710 simply comment out the line that says
. /usr/pluto/bin/X-CleanupVideo.sh
This is the command that gets run that modifies the xorg.conf file on startup. This is different than above because if you put exit at the top your display will not get initialized. And as above if you want to run the AVWizard you will need to uncomment this line.

== See also ==
* [http://www.mythtv.org/wiki/index.php/Main_Page MythTV wiki]
* MythTV Experience [http://brentlagesse.net/~brent/mythtv.php]
* [[X_Configuration_Scripts]]

Display Drivers

2008-07-28T05:55:24Z

Usaf-lt-g: /* NOTE:ddamron Monday June 30, 2008 */

{| align="right"
| __TOC__
|}
[[Category: Tutorials]]
[[Category: Hardware| ]]

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.'''

== Installation ==
If the graphical environment cannot start you are likely to see a text screen blinking, this makes it very hard to login, if this is the case you can reboot into "recovery mode" by pressing [Esc] when GRUB tells you to during the boot process and then select it from the menu you will be presented with.

=== ATI Chipsets ===
The two main ways to install the ATI drivers are described in the [http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide Ubuntu Feisty Installation Guide].

For more information see also the [http://wiki.cchtml.com/index.php/Main_Page Unofficial ATI Linux Driver Wiki] and you might want to have a look at [http://www.mythtv.org/wiki/index.php/AtiProprietaryDriver 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.

==== Installing The ATI Driver ====

Here's the procedure I use for setting up an ATI X1250 MD. Currently the the AVwizard in 0710 does not configure ATI cards properly so you need to to do some manual steps to get things working.

'''Step 1'''

Add the MD in the normal way (ie plug it into the network and let it add itself). Let it reboot and then it should run the AVwizard. Choose the options you want - output connector, resolution, refresh.... UI2 with Overlay etc etc and complete the wizard. Now the screen will return to a console screen and will after 5-10 mins will try to run the setup Wizard... but the setup Wizard will run very slowly and the video of 'Sarah' will not play smoothly. This is because the ATI drivers are not installed yet and the X driver is set to 'vesa'.

'''Step 2'''

From another machine ssh into the partially installed MD using Konsole from the KDE Desktop or a terminal app like Putty under Windows XP. Do the following from the console;

sudo su - <return>
ssh moonNN <return> (**where the NN is the device number for the MD we're configuring**)

Alternatively do the following from the MD/Core you are configuring;

Ctrl+Alt+2

Now login using the login you created when you installed your system ie When you ran the DVD installer or CD installer. Now we're logged into the MD we are configuring as 'root' and we can install the ATI drivers and configure Xorg.conf;

Firstly make sure our sources.list is up to date:

apt-get update <return>

Now lets install the ATI driver and packages;

apt-get install linux-restricted-modules-generic restricted-manager <return>

Answer 'Y' to installing new packages then do the following steps;

apt-get install xorg-driver-fglrx <return>
depmod -a <return>

So far so good... now we have the ATI drivers installed! (the current driver in the repos is not the latest ATI release an updated driver will be packaged soon though). Now we have to configure Xorg to use it! Do the steps below;

I use the console text editor 'joe' below but you can use whichever you prefer ('nano' is installed by default for example);

joe /etc/X11/xorg.conf <return>

Now you are editing the xorg.conf of your MD and the only change you need to make is to the 'Device' section. In the 'Device' section you will see a line thats says;

Driver "vesa"
or
Driver "ati"

Change the string 'vesa' (or ati) to 'fglrx' which is the name of the ATI driver. The updated driver line should look like below;

Driver "fglrx"

Now save the changes you have made to xorg.conf.

Now reboot the MD from the console with;

reboot <return>

The MD will now reboot normally and the setup wizard will run again.... but this time the video and the Ui will run smoothly as the ATI driver is installed and confgured.

Currently the ATI driver will not support UI2 with transparency but it will support UI2 with overlay very nicely indeed. There are two small caveats to running UI2 with Overlay currently with the ATI driver in that the 'Compass Rose' on screen menu for selecting DVD chapters, Lighting levels etc etc and the 'Zoom & Aspect ratio' screen when playing Video do not draw correctly - the bit maps for the menus do not display but the menus do work.

=== NVidia Chipsets ===
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
2. Download the latest [http://www.nvidia.com/object/unix.html linux drivers from NVidia] (depending [http://www.nvidia.com/object/IO_32667.html on your hardware], one of versions: 1XX.XX.XX, 1.0-96xx or 1.0-71XX), if you haven't done so already. When you have found the URL for downloading the package on the nvidia site you could download it like this:
'''root@dcerouter:~#''' wget <nowiki>http://us.download.nvidia.com/XFree86/Linux-x86/</nowiki>''<version>''<nowiki>/NVIDIA-Linux-x86-</nowiki>''<version>''<nowiki>-pkg1.run</nowiki>
3. Go to runlevel 1 to stop the currently running X-server.

NB: There was no need for me to run this command as I was already in Level 1 - It just locked up the keyboard. --[[User:Mortar|Mortar]] 18:12, 6 January 2008 (MST)
'''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.

If the AVWizard crashes (as it did for me when installing the legacy drivers) try setting the '''driver''' option in the ''xorg.conf'' file to '''vesa''', go through the AVWizard and then change it back. --[[User:Zaerc|Zaerc]] 15:14, 5 June 2008 (PDT)

=== Intel Chipsets ===
There is a renewed interest in the Intel graphics chipsets since Intel released the drivers under the GPL. Currently the Intel driver still cannot support UI2 with Alphablending but they will support UI2 with Overlay very nicely and video performance is excellent. LinuxMCE versions after Beta4 have full support for configuring the Intel driver in the AVwizard.

From LinuxMCE-0710 Beta4 onwards LinuxMCE will install the newer intel driver by default - so the instructions below are only useful if your still running LinuxMCE-0704.

==== For LinuxMCE-0704 ====

You will want to make sure you are using the newer intel drivers from http://packages.ubuntu.com/gutsy/i386/xserver-xorg-video-intel/download for i386. These replace the older i810, etc. drivers and should cover all the modern intel chipsets. The name for this driver is 'intel' and would replace the older 'i810' drivers.

If you're using i810 driver make sure you add Option "LinearAlloc" "8160" to xorg.conf or video players will crash with X11 error: BadAlloc.

From man i810:
Option "LinearAlloc" "integer"
Allows more memory for the offscreen allocator. This usually
helps in situations where HDTV movies are required to play but
not enough offscreen memory is usually available. Set this to
8160 for upto 1920x1080 HDTV support. Default 0KB (off).

==== potential problem ====

there can be a problem with some intel drivers, like the gma 3100. see [[bug/gma3100driver]] for further informations

=== Via Chipsets ===
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]

At the time of this writing (10/04/08), the binary Via Unichrome driver (released december 2007) works best (stable, good 2d and 3d) on my Via Mini ITX with CLE266 integerated graphics system. It is able to run UI2 medium with very good performance.
There is a crash at bootup (with any via driver) if the complete runlevel 2 starts.
This issue can be worked around by booting recovery mode and manually starting only /etc/init.d/kdm as root.
Issue under investigation - will update here when good workaround is done.
Contact zeratul at fastmail.fm for latest status/tips

'''HOW-TO VIA Openchrome driver for xorg:''' 
For VIA CX700M2 UniChrome PRO II Graphics (1" VIA units) or mainly via graphics: 
===NOTE:[[User:usaf-lt-g|usaf-lt-g]] Sunday July 28th, 2008===

----

Burgiman's instructions worked... with some minor modifications. Take note, I had a VERY difficult time first being able to SSH in to my MD. However, note, that I'm using an "earlier" version of LMCE (Beta 3). My MD is also diskless, and NETBIOS handled. If you can't gain root access to your MD through SSH I suggest the following method:

----

--[[User:Usaf-lt-g|Usaf-lt-g]] 22:55, 27 July 2008 (PDT)

''shell into your core as linuxmce / linuxmce and do the following:'' 

----
sudo -s 
cd /usr/pluto/diskless 
chroot <your MD # found on the linuxmce admin devices page> 
(chroot will allow you to access the MD's file system as a root user) 
----
''from here I suggest you make a new group and user and then add them to the list of sudoers so that you can easily have SSH access to your MD anytime without this hassle. I did the following:''

----
groupadd parents 
useradd -g parents chris 
passwd chris 
<set your password> 
 
visudo 
 
here you need to add a line below the: root ALL=(ALL) ALL line. Mine was: 
 
chris ALL=(ALL) ALL 
----

''Now you'll be able to login using this user with password you supplied and issue the sudo -s command, which will grant you root access to the MD.''
 
--[[User:Usaf-lt-g|Usaf-lt-g]] 22:55, 27 July 2008 (PDT)
''now from here you're going to need some additional packages installed before you can do anything with the OpenChrome drivers.'' 

----
apt-get install subversion (which will give you the svn command) 
 
apt-get install xserver-xorg-dev 
apt-get install libdrm-dev 
apt-get install libxvmc-dev 
----

''After that, you SHOULD be able to follow the rest of the install below. It worked for me. Hope this helps.''
 
Feel free to edit if necessary.
Chris

===NOTE:[[User:ddamron|ddamron]] Monday June 30, 2008===
Burgiman's instructions did NOT work for me.
Take that for what it's worth.
I had better success installing the VIA Unichrome Driver, and UI1. Use CLE266 mode.
If you have more success, please update this page
Dan

'''UPDATED FOR 0710!'''
--[[User:Burgiman|burgi]] 11:47, 2 June 2008 (PDT)

''shell into your box and do the following:'' 
apt-get install build-essential automake1.9 libtool x11proto-* libgl1-mesa-dev makedepend libxxf86vm-dev libexpat1-dev libexpat1 libxmu-dev xtrans-dev libpng12-dev libxcomposite-dev libxfixes-dev libxdamage-dev libxrandr-dev libxrender-dev libstartup-notification0-dev libgconf2-dev

cd /usr/src
svn checkout http://svn.openchrome.org/svn/trunk openchrome
cd openchrome*
./autogen.sh --prefix=/usr
make
make install

Now we have to edit /etc/X11/xorg.conf and change the device driver to via openchrome: 
vi /etc/X11/xorg.conf
Go to
Section "Device"
and change
Driver "vesa"
to
Driver "openchrome"
save and test the compiled new driver with a: 
X :1
and if your xwindow comes up, you can reboot and have fun 
--[[User:Burgiman|burgi]] 13:37, 3 March 2008 (PST)

=== Other Chipsets ===
Please help out by adding more if you can.

== Configuration ==
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.

=== Getting started ===
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], [[Logging In|log in]], become root and issue the command:
telinit 1
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:
X -configure
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: : 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:
X -scanpci
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 [http://en.wikipedia.org/wiki/Modeline wikipedia entry] to learn how to use modelines.
* http://koala.ilog.fr/cgi-bin/nph-colas-modelines
* http://xtiming.sourceforge.net/cgi-bin/xtiming.pl
* http://www.bohne-lang.de/spec/linux/modeline/
* http://amlc.berlios.de/
* http://www.mythtv.org/wiki/index.php/Working_with_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

=== Chipset driver ===
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.

=== Disable composite ===
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

=== Additional options ===
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 "AIGLX" "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.

== Troubleshooting ==

=== The AVWizard crashes X-windows ===

Try setting the [[#Chipset_driver]] option to '''vesa''', run the AVWizard again and then change the driver back to what it was.

=== Black screen ===

* Screen is black, after install seemed to go okay. You may have even seen the Kubuntu splash screen. See [[AVWizard]] on how to select the proper output.

*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 <pre>Option "ConnectedMonitor" "XXX"</pre>
::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 / ModeLine ]]'' above.

=== Microscopic fonts in KDE ===

See ''[[#Physical_display_size]]'' above.

If the above does not work, probably Xorg is calculating the DPI value in the wrong way.
This can be verified by having a look at the file /var/log/Xorg.0.log related to the MD with this issue searching for the line containing "DPI set to (x , y)",where x and y are values that apply to the specific display.

If those values are too small, fonts will be displayed accordingly (i.e, VERY small)

A workaround is to force Xorg to startup with a given DPI value.

To achieve this the following steps are required:

* edit the file /usr/pluto/bin/Start_X_Wrapper.sh on your MD where you are facing the font problem
* find the line beginning with xinit
* add "-dpi 96" (without quotes) at the end of this line
* save the file and reboot MD

Obviously it is possible to set DPI to something different than 96, according to specific needs.

Please note that after an LMCE update the startup script may be replaced by new ones, so the above workaround may have to be re-applied in order to keep fonts at the desired dimension.

=== LinuxMCE keeps reconfiguring my display settings ===

Add a line containing '''exit''' to the top of the ''/usr/pluto/bin/Xconfigure.sh'' file. After you do this you may experience difficulties running the AVWizard again, if so remove this line and add it back again after the wizard is finished.

For LinuxMCE 710 simply comment out the line that says
. /usr/pluto/bin/X-CleanupVideo.sh
This is the command that gets run that modifies the xorg.conf file on startup. This is different than above because if you put exit at the top your display will not get initialized. And as above if you want to run the AVWizard you will need to uncomment this line.

== See also ==
* [http://www.mythtv.org/wiki/index.php/Main_Page MythTV wiki]
* MythTV Experience [http://brentlagesse.net/~brent/mythtv.php]
* [[X_Configuration_Scripts]]