http://wiki.linuxmce.org/api.php?action=feedcontributions&feedformat=atom&user=UniLinuxMCE - User contributions [en]2026-05-11T05:51:07ZUser contributionsMediaWiki 1.44.0http://wiki.linuxmce.org/index.php?title=User:UNi&diff=20133User:UNi2009-07-30T23:54:36Z<p>Uni: /* MOTHERBOARD */</p>
<hr />
<div>[[Category:User Setups]]<br />
<br />
= '''About Me''' =<br />
<br />
I've been working with OpenBSD and Linux for 10 years, but never delved into X-Windows as I use OBSD mainly for LAMP functions. I live in Northern California (NorCAL) and work as a Network Engineer.<br />
<br />
= '''LinuxMCE''' =<br />
<br />
After having major crashing issues with LMCE, I found that it didn't like my video card so much (though others recommended it...); it would crash X-Windows. Also video card was sharing an interrupt with my NIC. I have resolved these issues by going back to my initial build Video Card, and installing a new NIC which doesn't try to mate with my Vid Card's interrupt. My box is very stable now and never crashes and I'm really enjoying LMCE now.<br />
<br />
<br />
== '''Next Steps''' ==<br />
<br />
<br />
<br />
* setup a MD after I'm sure the Core is stable and maybe wait until 810 before investing any more moola<br />
<br />
= '''Configuration''' =<br />
<br />
<br />
== '''Core''' ==<br />
<br />
<br />
<br />
<br />
=== Components: ===<br />
<br />
<br />
==== CPU ====<br />
<br />
Intel Dual-Core<br />
<br />
==== MOTHERBOARD ====<br />
<br />
[[ASUS P5NSLI LGA 775 NVIDIA nForce 570 SLI Intel Edition ATX Intel Motherboard]]<br />
<br />
* This motherboard seems to work but I got a ton of "rtc: lost some interrupts at 1024Hz" in Syslog and no one seems to know why...it resolved itself in 810 Alpha.<br />
<br />
<br />
* µATX<br />
<br />
* 4x DDR2 Slot<br />
<br />
* GF 7600<br />
<br />
* onboard 5.1 Audio<br />
<br />
* 1x Gigabit Marvell LAN<br />
<br />
* 1x PCI-E 16x<br />
<br />
* 2x PCI-E 1x<br />
<br />
* 1x PCI<br />
<br />
==== RAM ====<br />
<br />
2GB Infineon CL5<br />
<br />
==== Video Card ====<br />
<br />
BFG Tech BFGR76256GTOCE GeForce 7600GT 256MB<br />
<br />
==== STORAGE ====<br />
Western Digital Caviar SE16 WD2500KS 250GB 7200 RPM SATA 3.0Gb/s Hard Drive - OEM <br />
<br />
<br />
==== PSU ====<br />
<br />
<br />
<br />
==== CASE ====<br />
<br />
Enermax<br />
<br />
<br />
==== OTHER ====<br />
<br />
CPU-FAN:<br />
<br />
== '''Media Directors''' ==<br />
<br />
none so far<br />
<br />
<br />
<br />
= '''Automation''' =<br />
<br />
* Added a Linksys Wireless-G Internet Video Camera WVC54GCA, and enabled motion module</div>Unihttp://wiki.linuxmce.org/index.php?title=LinuxMCE-0810_alpha2&diff=20132LinuxMCE-0810 alpha22009-07-30T20:26:46Z<p>Uni: /* Installation */</p>
<hr />
<div>[[Category:Versions]]<br />
{| align="right"<br />
| __TOC__<br />
|}<br />
<br />
==Installation==<br />
# Install Kubuntu Intrepid desktop, update it and enable the restricted (video) drivers if needed. (download Kubuntu 8.10 '''desktop''' release from one of these: [http://mirrors.ccs.neu.edu/releases.ubuntu.com/kubuntu/8.10/ Northeastern University Mirror, USA], [http://swtsrv.informatik.uni-mannheim.de/pub/linux/distributions/ubuntu-release/kubuntu/8.10/ Mannheim University Mirror, Germany]) '''Currently, only the 32bit version of LinuxMCE is available. Only download the i386 version of 8.10 Kubuntu, even if your system can support 64bit versions.'''<br />
# Run aptitude update and aptitude dist-upgrade to get the latest Kubuntu updates.<br />
# Grab the latest installer script from [http://deb.linuxmce.org/ubuntu here], unpack them and change into the freshly created ''new-installer'' directory.<br />
# Run the following scripts (as root, in order): pre-install-from-repo.sh, mce-install.sh, post-install.sh.<br />
# Reboot, wait for the activity to stop (see progress on console 8).<br />
<br />
'''EDIT: MAKE SURE YOUR INTERNET CONNECTION IS ON ETH0!''' (For linux Newbies ETH0 is probably the network card on your motherboard...or plug all NICs into a switch that has Internet access)<br />
<br />
In other words, after installing Kubuntu:<br />
sudo su - #This might ask for the password you specified earlier during the install of kubuntu.<br />
aptitude update<br />
aptitude dist-upgrade<br />
wget -c http://deb.linuxmce.org/ubuntu/new-installer-alpha-latest.tar.gz<br />
tar xvf new-installer-alpha-latest.tar.gz<br />
cd new-installer<br />
./pre-install-from-repo.sh<br />
./mce-install.sh<br />
./post-install.sh<br />
reboot<br />
<br />
=== HDMI Audio ===<br />
If you installed 0810 Alpha 2.26 or earlier you will need to do apt-get dist-upgrade on your Core & MD's to get the updated AVwizard that enables HDMI audio to be easily configured... this will get you the new AVwizard and any other fixes changes since you last upgraded. For the time being you will need to upgrade nVidia (180.60 or greater) & alsa (1.0.20 or later) drivers by hand.<br />
<br />
Updated AVwizard notes;<br />
<br />
The new AVwizard now allows you to select primary & secondary HDMI/VGA connectors using the keyboard. Press '1' for HDMI 1 and 'Q' for HDMI 2 and press '2' for VGA 1 and 'S' for VGA 2. Once in the Graphical AVwizard UI you will notice that these new connectors are now available for selection. you will also notice that the AVwizard now has a new screen layout for selecting the Audio output and also includes 'HDMI' as one of the output connector options. Select 'HDMI' from this screen if you want Stereo output then in the following screen respond 'No' to Dolby Digital and DTS. If you want surround audio to be routed out of the HDMI connector (mainly used with surround amplifiers with HDMI inputs) then select 'HDMI' and then answers 'yes' to the Dolby Digital & DTS wizard screens.<br />
<br />
=== nVidia Restricted Driver ===<br />
<strike>Install the nVidia restricted driver (177) from KDE using the Hardware Manager ''before'' installing LinuxMCE 0810 Alpha for the best results</strike> The installer will now automatically choose and install the correct restricted driver during setup.It will be installed after selecting "OpenGL" on your Media Director in web admin page.<br />
<br />
=== MythTV ===<br />
<strike>Remove reference to hardy in /etc/apt/sources.list<br />
<br />
from terminal<br />
<pre><br />
sudo apt-get install pluto-mythtv-player<br />
</pre><br />
<br />
Install updated version of pluto-mythtv-plugin</strike><br />
<br />
=== Setup Diskless MD ===<br />
<strike>Follow the steps from [[LinuxMCE-0810_alpha1#Setup_Diskless_MD|alpha1]].</strike><br />
<br />
=== Upgrading kernel ===<br />
<strike>There are issues with the ''fglrx'' driver that are documented in Ubuntu's bug tracking system. If you're experiencing those issues, upgrade the kernel to ''2.6.27-13'' or better. [[Upgrading the Kernel]] has been updated with instructions on doing this.</strike> The latest official kernel is -14<br />
<br />
== Updates ==<br />
Check if there is no junk like references to hardy in /etc/apt/sources.list then:<br />
sudo apt-get update<br />
sudo apt-get dist-upgrade<br />
Or use a package manager on the KDE desktop for more convenience.<br />
<br />
=== 20090218 (alpha-2.1) ===<br />
*lmce-datalog-db_2.0.0.44.0902180810<br />
*lmce-datalogger-plugin_2.0.0.44.0902180810<br />
*lmce-enocean-tcm120_2.0.0.44.0902180810<br />
*lmce-src-datalogger-plugin_2.0.0.44.0902180810<br />
*lmce-src-enocean-tcm120_2.0.0.44.0902180810<br />
*lmce-src-lmce-datalog_2.0.0.44.0902180810<br />
*pluto-dcerouter_2.0.0.44.0902180810<br />
*pluto-dhcpd-plugin_2.0.0.44.0902180810<br />
*pluto-hald-src_2.0.0.44.0902180810<br />
*pluto-hald_2.0.0.44.0902180810<br />
*pluto-mythtv-plugin_2.0.0.44.0902180810<br />
*pluto-orbitergen_2.0.0.44.0902180810<br />
*pluto-src-dcerouter_2.0.0.44.0902180810<br />
*pluto-src-hal-device-finder_2.0.0.44.0902180810<br />
*pluto-src-mythtv-plugin_2.0.0.44.0902180810<br />
*pluto-src-orbitergen_2.0.0.44.0902180810<br />
*pluto-src-updatemedia_2.0.0.44.0902180810<br />
*pluto-updateentarea_2.0.0.44.0902180810<br />
*pluto-updatemedia_2.0.0.44.0902180810<br />
*pluto-zwave-lighting_2.0.0.44.0902180810<br />
*lmce-game-player_2.0.0.44.0902180810<br />
*lmce-game-plugin_2.0.0.44.0902180810<br />
*lmce-src-game-player_2.0.0.44.0902180810<br />
*lmce-src-game-plugin_2.0.0.44.0902180810<br />
<br />
==== 20090222 (alpha-2.1.1) ====<br />
*pluto-dcerouter_2.0.0.44.0902220810<br />
*pluto-bluetooth-dongle_2.0.0.44.0902220810<br />
<br />
=== 20090301 (alpha-2.2) ===<br />
SVN revision: 21746<br />
<br />
To avoid a known problem when upgrading pluto-storage-devices, forcefully remove it before upgrading and let apt fix it:<br />
dpkg -r --force-all pluto-storage-devices<br />
apt-get update<br />
apt-get install -f<br />
Also please note that installing the upgrade of pluto-system-database will OVERWRITE your existing pluto_main database. It is therefore advisable to make a backup first!<br />
mysqldump --skip-extended-insert pluto_main >pluto_main_$PK_Installation-`date '+%Y%m%d:%H%M%S'`.sql<br />
*pluto-boot-scripts_2.0.0.44.0903010810<br />
*pluto-network-storage_2.0.0.44.0903010810<br />
*pluto-skins-basic_2.0.0.44.0903010810<br />
*pluto-src-network-storage_2.0.0.44.0903010810<br />
*pluto-src-std-plugins_2.0.0.44.0903010810<br />
*pluto-src-updatemedia_2.0.0.44.0903010810<br />
*pluto-std-plugins_2.0.0.44.0903010810<br />
*pluto-storage-devices_2.0.0.44.0903010810<br />
*pluto-system-database_2.0.0.44.0903010810 <br />
*pluto-updatemedia_2.0.0.44.0903010810<br />
*pluto-website-admin_2.0.0.44.0903010810<br />
<br />
=== 20090308 (alpha-2.3) ===<br />
SVN revision: 21765<br />
<br />
Again it is wise to backup your database as there is a new pluto-system-database package, but this one will not overwrite your pluto_main database if it is already installed, it should do an sqlCVS update instead. <br />
Also remove the pluto-storage-devices, hopefully for the last time. <br />
See the previous upgrade [[LinuxMCE-0810_alpha2#20090301_.28alpha-2.2.29|above]] for details on how to do these things. <br />
<br />
*pluto-asterisk_2.0.0.44.0903080810<br />
*pluto-src-asterisk_2.0.0.44.0903080810<br />
*pluto-src-text-to-speech_2.0.0.44.0903080810<br />
*pluto-src-updatemedia_2.0.0.44.0903080810<br />
*pluto-storage-devices_2.0.0.44.0903080810<br />
*pluto-system-database_2.0.0.44.0903080810<br />
*pluto-text-to-speech_2.0.0.44.0903080810<br />
*pluto-updatemedia_2.0.0.44.0903080810<br />
*pluto-website-admin_2.0.0.44.0903080810<br />
<br />
=== 20090315 (alpha-2.4) ===<br />
SVN revision: 21798<br />
<br />
The web admin is being moved from pluto-admin to lmce-admin with this build. A redirect has been placed in pluto-admin to redirect to the new web admin URL to help smooth the transition. While every attempt has been made to make this a smooth transition, please be sure to file a trac ticket if you find bugs related to this move so I can get them taken care of - [[User:jondecker76|jondecker76]]<br />
<br />
<br />
The Asterisk IVR is broken in this release. For those that need to get it working/wish to try out new changes, do the following:<br />
sudo apt-get install libsox-fmt-all <br />
cd /usr/pluto/bin<br />
sudo rm generate_users_voicemenu.pl<br />
sudo wget http://svn.linuxmce.org/trac.cgi/browser/branches/LinuxMCE-0810/src/Asterisk/generate_users_voicemenu.pl?format=raw<br />
sudo chmod 755 generate_users_voicemenu.pl<br />
sudo ./generate_users_voicemenu.pl<br />
Be sure to have the default voice set up in the Text_To_Speech device's device data (its default is the ugly one we're already used to)! I also highly recommend following the instructions located at [http://wiki.linuxmce.org/index.php/Text_To_Speech http://wiki.linuxmce.org/index.php/Text_To_Speech] on how to install some better voices, and set the default voice to voice_nitech_us_slt_arctic_hts after you install the better voices (this is the best free voice available ATM). This should all work on next weeks build for those that can wait.. I'm still working on getting the better voices included by default, but need to check on licensing issues first.<br />
<br />
<br />
<br />
*pluto-asterisk_2.0.0.44.0903150810<br />
*pluto-boot-scripts_2.0.0.44.0903150810<br />
*pluto-makerelease_2.0.0.44.0903150810<br />
*pluto-newmdinteractor_2.0.0.44.0903150810<br />
*pluto-orbitergen_2.0.0.44.0903150810<br />
*pluto-proxy-orbiter_2.0.0.44.0903150810<br />
*pluto-src-asterisk_2.0.0.44.0903150810<br />
*pluto-src-makerelease_2.0.0.44.0903150810<br />
*pluto-src-newmdinteractor_2.0.0.44.0903150810<br />
*pluto-src-orbitergen_2.0.0.44.0903150810<br />
*pluto-src-proxy-orbiter_2.0.0.44.0903150810<br />
*pluto-src-std-plugins_2.0.0.44.0903150810<br />
*pluto-src-text-to-speech_2.0.0.44.0903150810<br />
*pluto-std-plugins_2.0.0.44.0903150810<br />
*pluto-system-database_2.0.0.44.0903150810<br />
*pluto-text-to-speech_2.0.0.44.0903150810<br />
*pluto-updateentarea_2.0.0.44.0903150810<br />
*pluto-website-admin_2.0.0.44.0903150810<br />
<br />
=== 20090322 (alpha-2.5) ===<br />
SVN revision: 21827<br />
<br />
*freepbx_0+2.3.1-2<br />
*pluto-asterisk_2.0.0.44.0903220810<br />
*pluto-dhcpd-plugin_2.0.0.44.0903220810<br />
*pluto-install-scripts_2.0.0.44.0903220810<br />
*pluto-raid-tools_2.0.0.44.0903220810<br />
*pluto-skins-basic_2.0.0.44.0903220810<br />
*pluto-src-asterisk_2.0.0.44.0903220810<br />
*pluto-website-admin_2.0.0.44.0903220810<br />
<br />
=== 20090401 (alpha-2.6) ===<br />
Note: This build will attempt to use Launch Manager to co-ordinate startup and shutdown of devices. While it is not 100% finished, it is working and stable. Please test it out and file any problems against trac ticket #48. Also, please note the following:<br />
I'm not sure on this, but you may have to manually install LM via apt-get<br />
After you upgrade, reboot your core <br />
CLI output of LM can be viewed on tty8 on the core, and tty1 on MD's (alt+ctrl+F8 and alt+ctrl+F1 respectively). You will have to manually switch back to the orbiter on tty7 when finished<br />
CLI output is not yet completely finished, so the top fields will be blank (this is normal for now)<br />
CLI output of the log messages is working however, so please take a peek at them on tty8/tty1 shortly after you hear the 2nd set of beeps on boot up (when the "x" cursor appears on the screen).<br />
You can further test out LM by switching to tty8/tty1 right after doing a router reload and watching the output and comparing it to what you would expect it to be.<br />
LM dos not yet track regen process and report the % done. This should be working in next week's build, however.<br />
If there are problems and/or you wish to restore previous functionality, the original /usr/pluto/bin/startCore.sh file can be restored from the backup /usr/pluto/bin/startCore.sh._backup, and the LM package removed<br />
LM is not yet properly daemonized. I'm saving this step for last after the socket layer is implemented and we get a client coded.<br />
'''Note:''' All orbiters will likely do a FULL REGEN after this update, and it may appear that your system is hanging because of this. Please give it some time to finish the regen (could take up to an hour on large installs)<br />
<br />
* lmcevdr_1.1-10_all.deb<br />
* pluto-website-admin_2.0.0.44.0904010019_i386.deb<br />
* pluto-dynamic-dns_2.0.0.44.0904010019_i386.deb<br />
* lmce-launch-manager_2.0.0.44.0904010019_i386.deb<br />
* pluto-boot-scripts_2.0.0.44.0904010019_i386.deb<br />
* pluto-system-database_2.0.0.44.0904010019_i386.deb<br />
* pluto-orbitergen_2.0.0.44.0904010019_i386.deb<br />
* pluto-updateentarea_2.0.0.44.0904010019_i386.deb<br />
* pluto-orbiter_2.0.0.44.0904010019_i386.deb<br />
<br />
=== 20090405 (alpha 2.7) ===<br />
From now on, the SVN version will part of the deb name.<br />
You may need to uninstall 'lmcevdr' (dpkg -r --force-all lmcevdr) and reinstall it (apt-get install lmcevdr) to get around the install-script bug in last weeks .deb package. It worked for me. <br />
* lmce-game-player_2.0.0.44.090405.21873_i386.deb<br />
* lmce-game-plugin_2.0.0.44.090405.21873_i386.deb<br />
* lmce-launch-manager_2.0.0.44.090405.21873_i386.deb<br />
* lmce-phoenix-solo-usb_2.0.0.44.090405.21873_i386.deb<br />
* lmcevdr_1.1-10_all.deb (This is no main package, and therefore does not contain the regular version designation. It is based upon version 21875)<br />
* pluto-bluetooth-dongle_2.0.0.44.090405.21873_i386.deb<br />
* pluto-simplephone_2.0.0.44.090405.21873_i386.deb<br />
* pluto-system-database_2.0.0.44.090405.21873_i386.deb<br />
* pluto-website-admin_2.0.0.44.09040521873_i386.deb<br />
<br />
=== 20090412 (alpha 2.8) ===<br />
* pluto-text-to-speech_2.0.0.44.09041221886_i386.deb (283,284) - Finally, good voices will actually install (Nitech HTS Arctic). <br />
* pluto-system-database_2.0.0.44.09041221886_i386.deb (211) - New default voice is voice_nitech_us_slt_arctic_hts. - game plugin and player template cleanups<br />
* mce-diskless-tools_2.0.0.44.09041221886_i386.deb (627,628) - Update kernel image for diskless MDs upon regenning.<br />
* pluto-website-admin_2.0.0.44.09041221886_i386.deb (220) - Infrared codes will now properly come from schema.linuxmce.org<br />
* pluto-boot-scripts_2.0.0.44.09041221886_i386.deb (234)- also schema.linuxmce.org IR codes related.<br />
* pluto-motion-wrapper_2.0.0.44.09041221886_i386.deb (455,456) - changed config variable from ffmpeg_filename to movie_filename<br />
* lmce_launch_manager_2.0.0.44.09041221886_i386.deb (298,299) - LM Actions now work from CLI(such as reload, regen, reboot, etc...)<br />
* lmce-game-player_2.0.0.44.09041221886_i386.deb (673,674) - Rebuilt for new device template<br />
* lmce-game-plugin_2.0.0.44.09041221886_i386.deb (671,672) - Rebuilt for new device template<br />
* pluto-updateentarea_2.0.0.44.09041221886_i386.deb (341,342) - may need to be rebuilt for device template changes<br />
<br />
=== 20090413 (alpha 2.9 jondecker special) ===<br />
* pluto-text-to-speech_2.0.0.44.09041321887_i386.deb (283,284) - fixes stupid post-install typo<br />
* pluto-zwave-lighting_2.0.0.44.09041321891_i386.deb (505,506) - thermostate support<br />
<br />
=== 20090419 (alpha 2.10 pbr) ===<br />
* pluto-text-to-speech_2.0.0.44.09041921897_i386.deb<br />
* pluto-website-admin_2.0.0.44.09041921897_i386.deb<br />
* lmce-screen-capture-camera_2.0.0.44.09041921897_i386.deb<br />
* pluto-system-database_2.0.0.44.09041921897_i386.deb<br />
* lmce-game-plugin_2.0.0.44.09041921897_i386.deb<br />
* lmce-game-player_2.0.0.44.09041921897_i386.deb<br />
* pluto-asterisk_2.0.0.44.09041921897_i386.deb<br />
<br />
=== 20090426 (alpha 2.11) ===<br />
With this release, MythTV now takes advantage of storage groups. Do some recordings, and try recording to a few different storage groups. <br />
Please test this out and report any problems such as duplicate attributes appearing in pluto_media, icon image not showing up, recordings failing to record, etc. Also, if you do have problems, try a reboot and see if it fixes the problem, then please let me know if the reboot fixed your problem. - jondecker76<br />
<br />
'''POST-BUILD UPDATE:''' A couple of small bugs have been found that will be fixed in next week's build. 1) Some storage groups are missing the leading "/" in the path, causing problems images in mythweb, downloads in the mythweb, etc. 2) Unmounted storage devices were being skipped. This means that you may not have a storage group for some of your devices at some times. I am changing this so that the storage groups are created, and if for some reason it is not available when a recording is set to use the storage group, then the recording will go to the (always present) Default storage group.<br />
For those wanting to fix #1 right now, just edit /usr/pluto/bin/StorageDevices_PlutoDirStructure.sh and add a preceeding slash before the path beginning with 'home/....' on lines 214 and 226. After this modification, MythTV works great in all of the storage groups! (You should do a reboot after making the change)<br />
<br />
* lmcevdr_1.1-10_all.deb - more setup fixes, this time for the MD<br />
* pluto-boot-scripts_2.0.0.44.09042621919_i386.deb (234) - small fix to get rid of a warning on DCERouter startup re missing dir., New MythTV directory structure stuff<br />
* pluto-asterisk_2.0.0.44.09042621919_i386.deb (270,271) - Added Support for Cisco 7910 phone<br />
* pluto-dhcpd-plugin_2.0.0.44.09042621919_i386.deb (302) - Added support for Cisco 7910 phone<br />
* pluto-system-database_2.0.0.44.09042621919_i386.deb (211) - '''If new devices are added, the pluto-system-database needs to be updates as well'''<br />
* pluto-storage-devices_2.0.0.44.09042621919_i386.deb (533) - Adds new tv_shows_* directories. Generates MythTV storage groups<br />
* pluto-std-plugins_2.0.0.44.09042621919_i386.deb (134,153) - adds some useful debugging snippets that helped trace down the problem of mythtv attributes not adding to pluto_media<br />
* pluto-mythtv-plugin_2.0.0.44.09042621919_i386.deb (134,153) - lots of changes to facilitate the new storage groups<br />
* pluto-network-storage_2.0.0.44.09042621919_i386.deb (503,508) - small changes to work with new tv_shows_* directories<br />
<br />
=== 20090429 (alpha 2.12) ===<br />
* pluto-storage-devices_2.0.0.44.09042921929_i386.deb (533) - Fixes some small bugs in MythTV storage groups<br />
* pluto-boot-scripts_2.0.0.44.09042921929_i386.deb (234) - misc. MythTV storage group enhancements<br />
* pluto-mythtv-plugin_2.0.0.44.09042921929_i386.deb (134,153) - misc. MythTV storage group enhancement<br />
* mce-diskless-tools_2.0.0.44.09042921929_i386.changes (627,628) - lots of fixes for MD boot- Changes effect new installs only<br />
* pluto-system-database_2.0.0.44.09042921929_i386.deb (211) - Fixes hardy issue in sources.list<br />
* pluto-nvidia-video-drivers_2.0.0.44.09042921929_i386.deb (490) - changed the package requirement to nvidia-glx-180 for intrepid<br />
<br />
=== 20090501 (alpha 2.13) ===<br />
There are a few more MythTV storage group changes in this build. Please understand that the storage group name changes may throw mythweb out of whack on some old recordings, but this should be minimal. The old "user_*/<storage_device>" naming scheme is replaced with a "<username>:<storage_device>" naming convention. This will appeal to many more users than the user_* convention. Also, there is now support for custom storage groups. You can make your own storage groups now on top of the auto-generated LMCE ones by prepending with "custom:" (for example, you may make a new storage group named "custom:MyDrive", and it will not be removed or overwritten by the scripts that generate the storage groups). One last change is in the "Default" storage group - it no longer points to the drive with most space. This was changed because eventually it would throw mythweb for a loop once the paths changed. I will look into a better way to defaultly record to the drive with most space, most likely using recording profiles.<br />
<br />
* lmce-launch-manager (298,299) - db wrapper fix to handle empty resultsets<br />
* pluto-bluetooth-dongle (124,143) - fix some connection issues in JavaMO<br />
* pluto-mythtv-plugin (134,153)<br />
* pluto-storage-devices (533)<br />
* pluto-boot-scripts (234) - MD fixes<br />
* mce-diskless-tools (391) - MD fixes<br />
* pluto-install-scripts (627,628) - MD fixes<br />
* pluto-x-scripts (520,523) - AV Wizard fix for MD<br />
* pluto-zwave-lighting (505,506) - Init speedup<br />
<br />
=== 20090503 (alpha2.14) ===<br />
* pluto-zwave-lighting_2.0.0.44.09050321942_i386.deb (505,506) - boolean fixes<br />
<br />
=== 20090505 (alpha2.15) ===<br />
KDE on the MD should work now. The first boot of the system after the update will take a bit longer, as stuff that has not worked, is now being executed for the first time.<br />
<br />
* mce-diskless-tools_2.0.0.44.09050521951_i386.deb (627,628) - Lots of small fixes<br />
* pluto-system-database_2.0.0.44.09050521951_i386.deb (211) - More hardy extinction<br />
* pluto-boot-scripts_2.0.0.44.09050521951_i386.deb (234) - Small bug with regards to MySQL authorization fixed, which results in a running KDE on the MD, again.<br />
<br />
=== 20090505 (alpha2.16 snafu fix) ===<br />
* pluto-boot-scripts_2.0.0.44.09050521958_i386.deb (234) - snafu causing weird things and corruption on updates<br />
<br />
=== 20090506 (alpha2.17) ===<br />
* pluto-asterisk_2.0.0.44.09050621962_i386.deb (270,271) - Additional australian provider in the web admin (VoIPWA) and some janitory work.<br />
* pluto-boot-scripts_2.0.0.44.09050621962_i386.deb (234) - Additional visual feedback during the first boot, after running the AV Wizard<br />
<br />
=== 20090507 (alpha2.18)===<br />
* pluto-dhcpd-plugin_2.0.0.44.09050721973_i386.deb (302) - Pnp script for Cisco 7910, aastra (aastra still needs a device template)<br />
* lmce-launch-manager_2.0.0.44.09050721973_i386.deb (298,299) - Launch manager is now started in its own screen session<br />
* pluto-system-database_2.0.0.44.09050721973_i386.deb (211) - Removal of X Client Data as a dependency<br />
* pluto-mythtv-plugin_2.0.0.44.09050721973_i386.deb (134,153) - small changes to keep backend in sync<br />
* pluto-storage-devices_2.0.0.44.09050721973_i386.deb (533) - Updates the Default and LiveTV storage groups so they use the drive with most space<br />
* pluto-boot-scripts_2.0.0.44.09050721973_i386.deb (234) - Better detection of Intel Mobile Graphics adapter<br />
<br />
=== 20090511 (alpha2.19) ===<br />
* lmcevdr - more VDR configuration settings<br />
* pluto-boot-scripts_2.0.0.44.09051121983_i386.deb (234) - Another KDE Desktop on MD fix<br />
* mce-diskless-tools_2.0.0.44.09051121984_i386.deb (627,628) - Be agnostic about the compression format of tar archives, and more forgiving on download problems<br />
<br />
=== 20090515 (alpha2.20) ===<br />
* lmcevdr_1.1-10_all.deb - more VDR configuration settings<br />
* pluto-system-database_2.0.0.44.09051522002_i386.deb (211) - Additional package definitions (vdr-plugin-streamdev-server and vdr-plugin-streamdev-client)<br />
* pluto-hald_2.0.0.44.09051522002_i386.deb (529,530) - USB detection, better MCE2 support<br />
* pluto-vdr-plugin_2.0.0.44.09051522002_i386.deb (466,467) - Additional dependency for pluto-vdr-plugin to vdr-plugin-streamdev-server<br />
* lmce-launch-manager_2.0.0.44.09051522002_i386.deb (298,299) - Prompt user for reload after new MD creation (Requires manual re-run of Diskless_CreateTBZ.sh)<br />
* pluto-orbiter_2.0.0.44.09051522002_i386.deb (119,138) - Prompt user for reload after new MD creation (Requires manual re-run of Diskless_CreateTBZ.sh)<br />
* pluto-storage-devices_2.0.0.44.09051522003_i386.deb (533) - some small MythTV storage group tweaks<br />
* pluto-slim-server-streamer_2.0.0.44.09051522002_i386.deb (289,290) - changes to the configuraton script to start squeezecenter instead of slimserver<br />
* pluto-website-admin_2.0.0.44.09051522002_i386.deb (220) - Screen Saver section fixed<br />
* pluto-plutoutils_2.0.0.44.09051522002_i386.deb (197,196) - fix FileUtils::ReadURL method<br />
* pluto-std-plugins_2.0.0.44.09051522002_i386.deb (116,135) - support for external media in conjunction with playlists<br />
<br />
=== 20090520 (alpha2.21) ===<br />
* pluto-website-admin_2.0.0.44.09052022008_i386.deb (220) - GSD/IR code update fixes<br />
<br />
=== 20090601 (alpha 2.22) ===<br />
This update contains lots of changes to the storage mechanism. Make sure you can live without a working system for a while, in case things don't work out ...<br />
<br />
* pluto-system-database_2.0.0.44.09060122043_i386.deb (211) - More VDR related changes in the package definitions.<br />
* pluto-boot-scripts_2.0.0.44.09060122043_i386.deb (234) - New installations will use our own new_installation script, starting with number 1000000<br />
* pluto-std-plugins_2.0.0.44.09060122043_i386.deb (116,135) - fixed bug in playlist support<br />
* pluto-network-storage_2.0.0.44.09060122043_i386.deb (503,508) - New /home/public/data/pvr directory structure related<br />
* pluto-storage-devices_2.0.0.44.09060122043_i386.deb (533) - New /home/public/data/pvr directory structure related<br />
* pluto-mythtv-plugin_2.0.0.44.09060122043_i386.deb (134,153) - Storage group enhancements to use the new pvr directory, as well as addition of a new script to handle mythtv storagegroup creation and maintenance. Hopefully this will also fix some stability issues. Mythtv auto expire set from 1GB to 10GB to match the LMCE low disk space nag.<br />
* pluto-website-admin_2.0.0.44.09060122043_i386.deb (220) - more Pluto -> LMCE renames...<br />
* pluto-skins-basic_2.0.0.44.09060122043_i386.deb (204) - new art work for MythTV remote<br />
* pluto-zwave-lighting2.0.0.44.09060122043_i386.deb (505,506) - inclusion enhancements<br />
<br />
=== 20090609 (alpha 2.23) ===<br />
* pluto-boot-scripts_2.0.0.44.09060922056 (234)- backup procedure backs up pluto_media and mediapics<br />
* pluto-skins-basic_2.0.0.44.09060922056 (204) - more art work for MythTV remote on a mobile, remove pluto from more orbiter screens<br />
* pluto-system-database_2.0.0.44.09060922056 (211) - Updates to the MythTV remote and EnOcean package<br />
* pluto-zwave-lighting_2.0.0.44.09060922056 (505,506) - device reset capabilities<br />
* lmce-shoutcast-radio-plugin_2.0.0.44.09060922056 (703,704) - Initial shoutcast support<br />
<br />
=== 20090628 (alpha 2.24) ===<br />
* lmce-mediatomb_2.0.0.44.09062822099_i386.deb (702) - Support for MediaTomb UPnP Server. One day, I will understand why people don't put UPnP into a name, when it handles the configuration of a UPnP Server<br />
* pluto-asterisk_2.0.0.44.09062822099_i386.deb (270,271) - Make sure asterisk is owner of all /etc/asterisk files after updating the dialplan.<br />
* pluto-dhcpd-plugin_2.0.0.44.09062822099_i386.deb (302) - Make sure asterisk is owner of all /etc/asterisk files after adding IP phones<br />
* pluto-orbiter_2.0.0.44.09062822099_i386.deb (119,138) - Support for Gyration 3101<br />
* pluto-skins-basic_2.0.0.44.09062822099_i386.deb (204) - more art work for voice mail<br />
* pluto-slim-server-streamer_2.0.0.44.09062822099_i386.deb (289,290) - support playing of URLs via SqueezeBoxes, turn off SqueezeBoxes after stopping from Orbiter<br />
* pluto-std-plugins_2.0.0.44.09062822099_i386.deb (116,135) - Updates to voice mail datagrid, media streams by default attempt to grab a synopsis from the attribute database, if available, support for Gyration 3101<br />
* pluto-system-database_2.0.0.44.09062822099_i386.deb (211) - Updates to the voice mail screens, cursor no longer visible in video playback (Yeah, TschakEEE go!!!), Support for Gyration 3101<br />
* pluto-zwave-lighting_2.0.0.44.09062822099_i386.deb (505,506) - enhanced logging<br />
<br />
=== 20090721 (alpha 2.25) ===<br />
* lmce-shoutcast-radio-plugin_2.0.0.44.09072122164_i386.deb (703,704) - sanity check on configuration values, prevents excessive load when too low interval<br />
* pluto-bluetooth-dongle_2.0.0.44.09072122164_i386.deb (124,143) - JavaMO -Updated keymappings for SE phones, doesn't turn on backlight - saves phone battery<br />
* pluto-chromoflex_2.0.0.44.09072122164_i386.deb (711,712) - Initial support<br />
* pluto-dhcpd-plugin_2.0.0.44.09072122164_i386.deb (302) - Fixing overambitious deletion in configure_squeezebox.pl<br />
* pluto-irtrans-ethernet_2.0.0.44.09072122164_i386.deb (709,710) - Plug and play support for the IRTrans Ethernet dongles<br />
* pluto-orbiter_2.0.0.44.09072122164_i386.deb (119,138) - Fix of serious keyboard bug introduced in alpha 2.24<br />
* pluto-slim-server-streamer_2.0.0.44.09072122164_i386.deb (289,290) - Modified launch script. [http://svn.linuxmce.org/trac.cgi/ticket/282 Trac #282 Preserve media position when moving media]<br />
* pluto-slimserver-plugin_2.0.0.44.09072122164_i386.deb (425,425) - [http://svn.linuxmce.org/trac.cgi/ticket/282 Trac #282 Preserve media position when moving media]<br />
* pluto-standard-plugins_2.0.0.44.09072122164_i386.deb (116,135) - Changes to Media Plugin to make nicer output of playing media in Playlist datagrid.<br />
* pluto-system-database_2.0.0.44.09072122164_i386.deb (211) - Updates to device template #53.<br />
<br />
=== 20090722 (alpha2.26) ===<br />
* pluto-av-wizard_2.0.0.44.09072222170_i386.deb (556,555) - HDMI sound support<br />
* pluto-boot-scripts_2.0.0.44.09072222170_i386.deb (234) - HDMI sound support<br />
* pluto-website-admin_2.0.0.44.09072222170_i386.deb (220) - HDMI sound support<br />
** HDMI support requires ALSA 1.0.19 or later.<br />
<br />
=== upcoming... ===<br />
* lmce-activate-orbiter-plasmoid (707,708) - Plasmoid to re-activate Orbiter<br />
*<br />
<br />
== Previous alpha releases ==<br />
* Notes about [[LinuxMCE-0810 alpha1]]<br />
* Notes about [[LinuxMCE-0810 alpha0]]</div>Unihttp://wiki.linuxmce.org/index.php?title=LinuxMCE-0810_alpha2&diff=20131LinuxMCE-0810 alpha22009-07-30T20:26:32Z<p>Uni: /* Installation */</p>
<hr />
<div>[[Category:Versions]]<br />
{| align="right"<br />
| __TOC__<br />
|}<br />
<br />
==Installation==<br />
# Install Kubuntu Intrepid desktop, update it and enable the restricted (video) drivers if needed. (download Kubuntu 8.10 '''desktop''' release from one of these: [http://mirrors.ccs.neu.edu/releases.ubuntu.com/kubuntu/8.10/ Northeastern University Mirror, USA], [http://swtsrv.informatik.uni-mannheim.de/pub/linux/distributions/ubuntu-release/kubuntu/8.10/ Mannheim University Mirror, Germany]) '''Currently, only the 32bit version of LinuxMCE is available. Only download the i386 version of 8.10 Kubuntu, even if your system can support 64bit versions.'''<br />
# Run aptitude update and aptitude dist-upgrade to get the latest Kubuntu updates.<br />
# Grab the latest installer script from [http://deb.linuxmce.org/ubuntu here], unpack them and change into the freshly created ''new-installer'' directory.<br />
# Run the following scripts (as root, in order): pre-install-from-repo.sh, mce-install.sh, post-install.sh.<br />
# Reboot, wait for the activity to stop (see progress on console 8).<br />
<br />
EDIT: MAKE SURE YOUR INTERNET CONNECTION IS ON ETH0! (For linux Newbies ETH0 is probably the network card on your motherboard...or plug all NICs into a switch that has Internet access)<br />
<br />
In other words, after installing Kubuntu:<br />
sudo su - #This might ask for the password you specified earlier during the install of kubuntu.<br />
aptitude update<br />
aptitude dist-upgrade<br />
wget -c http://deb.linuxmce.org/ubuntu/new-installer-alpha-latest.tar.gz<br />
tar xvf new-installer-alpha-latest.tar.gz<br />
cd new-installer<br />
./pre-install-from-repo.sh<br />
./mce-install.sh<br />
./post-install.sh<br />
reboot<br />
<br />
=== HDMI Audio ===<br />
If you installed 0810 Alpha 2.26 or earlier you will need to do apt-get dist-upgrade on your Core & MD's to get the updated AVwizard that enables HDMI audio to be easily configured... this will get you the new AVwizard and any other fixes changes since you last upgraded. For the time being you will need to upgrade nVidia (180.60 or greater) & alsa (1.0.20 or later) drivers by hand.<br />
<br />
Updated AVwizard notes;<br />
<br />
The new AVwizard now allows you to select primary & secondary HDMI/VGA connectors using the keyboard. Press '1' for HDMI 1 and 'Q' for HDMI 2 and press '2' for VGA 1 and 'S' for VGA 2. Once in the Graphical AVwizard UI you will notice that these new connectors are now available for selection. you will also notice that the AVwizard now has a new screen layout for selecting the Audio output and also includes 'HDMI' as one of the output connector options. Select 'HDMI' from this screen if you want Stereo output then in the following screen respond 'No' to Dolby Digital and DTS. If you want surround audio to be routed out of the HDMI connector (mainly used with surround amplifiers with HDMI inputs) then select 'HDMI' and then answers 'yes' to the Dolby Digital & DTS wizard screens.<br />
<br />
=== nVidia Restricted Driver ===<br />
<strike>Install the nVidia restricted driver (177) from KDE using the Hardware Manager ''before'' installing LinuxMCE 0810 Alpha for the best results</strike> The installer will now automatically choose and install the correct restricted driver during setup.It will be installed after selecting "OpenGL" on your Media Director in web admin page.<br />
<br />
=== MythTV ===<br />
<strike>Remove reference to hardy in /etc/apt/sources.list<br />
<br />
from terminal<br />
<pre><br />
sudo apt-get install pluto-mythtv-player<br />
</pre><br />
<br />
Install updated version of pluto-mythtv-plugin</strike><br />
<br />
=== Setup Diskless MD ===<br />
<strike>Follow the steps from [[LinuxMCE-0810_alpha1#Setup_Diskless_MD|alpha1]].</strike><br />
<br />
=== Upgrading kernel ===<br />
<strike>There are issues with the ''fglrx'' driver that are documented in Ubuntu's bug tracking system. If you're experiencing those issues, upgrade the kernel to ''2.6.27-13'' or better. [[Upgrading the Kernel]] has been updated with instructions on doing this.</strike> The latest official kernel is -14<br />
<br />
== Updates ==<br />
Check if there is no junk like references to hardy in /etc/apt/sources.list then:<br />
sudo apt-get update<br />
sudo apt-get dist-upgrade<br />
Or use a package manager on the KDE desktop for more convenience.<br />
<br />
=== 20090218 (alpha-2.1) ===<br />
*lmce-datalog-db_2.0.0.44.0902180810<br />
*lmce-datalogger-plugin_2.0.0.44.0902180810<br />
*lmce-enocean-tcm120_2.0.0.44.0902180810<br />
*lmce-src-datalogger-plugin_2.0.0.44.0902180810<br />
*lmce-src-enocean-tcm120_2.0.0.44.0902180810<br />
*lmce-src-lmce-datalog_2.0.0.44.0902180810<br />
*pluto-dcerouter_2.0.0.44.0902180810<br />
*pluto-dhcpd-plugin_2.0.0.44.0902180810<br />
*pluto-hald-src_2.0.0.44.0902180810<br />
*pluto-hald_2.0.0.44.0902180810<br />
*pluto-mythtv-plugin_2.0.0.44.0902180810<br />
*pluto-orbitergen_2.0.0.44.0902180810<br />
*pluto-src-dcerouter_2.0.0.44.0902180810<br />
*pluto-src-hal-device-finder_2.0.0.44.0902180810<br />
*pluto-src-mythtv-plugin_2.0.0.44.0902180810<br />
*pluto-src-orbitergen_2.0.0.44.0902180810<br />
*pluto-src-updatemedia_2.0.0.44.0902180810<br />
*pluto-updateentarea_2.0.0.44.0902180810<br />
*pluto-updatemedia_2.0.0.44.0902180810<br />
*pluto-zwave-lighting_2.0.0.44.0902180810<br />
*lmce-game-player_2.0.0.44.0902180810<br />
*lmce-game-plugin_2.0.0.44.0902180810<br />
*lmce-src-game-player_2.0.0.44.0902180810<br />
*lmce-src-game-plugin_2.0.0.44.0902180810<br />
<br />
==== 20090222 (alpha-2.1.1) ====<br />
*pluto-dcerouter_2.0.0.44.0902220810<br />
*pluto-bluetooth-dongle_2.0.0.44.0902220810<br />
<br />
=== 20090301 (alpha-2.2) ===<br />
SVN revision: 21746<br />
<br />
To avoid a known problem when upgrading pluto-storage-devices, forcefully remove it before upgrading and let apt fix it:<br />
dpkg -r --force-all pluto-storage-devices<br />
apt-get update<br />
apt-get install -f<br />
Also please note that installing the upgrade of pluto-system-database will OVERWRITE your existing pluto_main database. It is therefore advisable to make a backup first!<br />
mysqldump --skip-extended-insert pluto_main >pluto_main_$PK_Installation-`date '+%Y%m%d:%H%M%S'`.sql<br />
*pluto-boot-scripts_2.0.0.44.0903010810<br />
*pluto-network-storage_2.0.0.44.0903010810<br />
*pluto-skins-basic_2.0.0.44.0903010810<br />
*pluto-src-network-storage_2.0.0.44.0903010810<br />
*pluto-src-std-plugins_2.0.0.44.0903010810<br />
*pluto-src-updatemedia_2.0.0.44.0903010810<br />
*pluto-std-plugins_2.0.0.44.0903010810<br />
*pluto-storage-devices_2.0.0.44.0903010810<br />
*pluto-system-database_2.0.0.44.0903010810 <br />
*pluto-updatemedia_2.0.0.44.0903010810<br />
*pluto-website-admin_2.0.0.44.0903010810<br />
<br />
=== 20090308 (alpha-2.3) ===<br />
SVN revision: 21765<br />
<br />
Again it is wise to backup your database as there is a new pluto-system-database package, but this one will not overwrite your pluto_main database if it is already installed, it should do an sqlCVS update instead. <br />
Also remove the pluto-storage-devices, hopefully for the last time. <br />
See the previous upgrade [[LinuxMCE-0810_alpha2#20090301_.28alpha-2.2.29|above]] for details on how to do these things. <br />
<br />
*pluto-asterisk_2.0.0.44.0903080810<br />
*pluto-src-asterisk_2.0.0.44.0903080810<br />
*pluto-src-text-to-speech_2.0.0.44.0903080810<br />
*pluto-src-updatemedia_2.0.0.44.0903080810<br />
*pluto-storage-devices_2.0.0.44.0903080810<br />
*pluto-system-database_2.0.0.44.0903080810<br />
*pluto-text-to-speech_2.0.0.44.0903080810<br />
*pluto-updatemedia_2.0.0.44.0903080810<br />
*pluto-website-admin_2.0.0.44.0903080810<br />
<br />
=== 20090315 (alpha-2.4) ===<br />
SVN revision: 21798<br />
<br />
The web admin is being moved from pluto-admin to lmce-admin with this build. A redirect has been placed in pluto-admin to redirect to the new web admin URL to help smooth the transition. While every attempt has been made to make this a smooth transition, please be sure to file a trac ticket if you find bugs related to this move so I can get them taken care of - [[User:jondecker76|jondecker76]]<br />
<br />
<br />
The Asterisk IVR is broken in this release. For those that need to get it working/wish to try out new changes, do the following:<br />
sudo apt-get install libsox-fmt-all <br />
cd /usr/pluto/bin<br />
sudo rm generate_users_voicemenu.pl<br />
sudo wget http://svn.linuxmce.org/trac.cgi/browser/branches/LinuxMCE-0810/src/Asterisk/generate_users_voicemenu.pl?format=raw<br />
sudo chmod 755 generate_users_voicemenu.pl<br />
sudo ./generate_users_voicemenu.pl<br />
Be sure to have the default voice set up in the Text_To_Speech device's device data (its default is the ugly one we're already used to)! I also highly recommend following the instructions located at [http://wiki.linuxmce.org/index.php/Text_To_Speech http://wiki.linuxmce.org/index.php/Text_To_Speech] on how to install some better voices, and set the default voice to voice_nitech_us_slt_arctic_hts after you install the better voices (this is the best free voice available ATM). This should all work on next weeks build for those that can wait.. I'm still working on getting the better voices included by default, but need to check on licensing issues first.<br />
<br />
<br />
<br />
*pluto-asterisk_2.0.0.44.0903150810<br />
*pluto-boot-scripts_2.0.0.44.0903150810<br />
*pluto-makerelease_2.0.0.44.0903150810<br />
*pluto-newmdinteractor_2.0.0.44.0903150810<br />
*pluto-orbitergen_2.0.0.44.0903150810<br />
*pluto-proxy-orbiter_2.0.0.44.0903150810<br />
*pluto-src-asterisk_2.0.0.44.0903150810<br />
*pluto-src-makerelease_2.0.0.44.0903150810<br />
*pluto-src-newmdinteractor_2.0.0.44.0903150810<br />
*pluto-src-orbitergen_2.0.0.44.0903150810<br />
*pluto-src-proxy-orbiter_2.0.0.44.0903150810<br />
*pluto-src-std-plugins_2.0.0.44.0903150810<br />
*pluto-src-text-to-speech_2.0.0.44.0903150810<br />
*pluto-std-plugins_2.0.0.44.0903150810<br />
*pluto-system-database_2.0.0.44.0903150810<br />
*pluto-text-to-speech_2.0.0.44.0903150810<br />
*pluto-updateentarea_2.0.0.44.0903150810<br />
*pluto-website-admin_2.0.0.44.0903150810<br />
<br />
=== 20090322 (alpha-2.5) ===<br />
SVN revision: 21827<br />
<br />
*freepbx_0+2.3.1-2<br />
*pluto-asterisk_2.0.0.44.0903220810<br />
*pluto-dhcpd-plugin_2.0.0.44.0903220810<br />
*pluto-install-scripts_2.0.0.44.0903220810<br />
*pluto-raid-tools_2.0.0.44.0903220810<br />
*pluto-skins-basic_2.0.0.44.0903220810<br />
*pluto-src-asterisk_2.0.0.44.0903220810<br />
*pluto-website-admin_2.0.0.44.0903220810<br />
<br />
=== 20090401 (alpha-2.6) ===<br />
Note: This build will attempt to use Launch Manager to co-ordinate startup and shutdown of devices. While it is not 100% finished, it is working and stable. Please test it out and file any problems against trac ticket #48. Also, please note the following:<br />
I'm not sure on this, but you may have to manually install LM via apt-get<br />
After you upgrade, reboot your core <br />
CLI output of LM can be viewed on tty8 on the core, and tty1 on MD's (alt+ctrl+F8 and alt+ctrl+F1 respectively). You will have to manually switch back to the orbiter on tty7 when finished<br />
CLI output is not yet completely finished, so the top fields will be blank (this is normal for now)<br />
CLI output of the log messages is working however, so please take a peek at them on tty8/tty1 shortly after you hear the 2nd set of beeps on boot up (when the "x" cursor appears on the screen).<br />
You can further test out LM by switching to tty8/tty1 right after doing a router reload and watching the output and comparing it to what you would expect it to be.<br />
LM dos not yet track regen process and report the % done. This should be working in next week's build, however.<br />
If there are problems and/or you wish to restore previous functionality, the original /usr/pluto/bin/startCore.sh file can be restored from the backup /usr/pluto/bin/startCore.sh._backup, and the LM package removed<br />
LM is not yet properly daemonized. I'm saving this step for last after the socket layer is implemented and we get a client coded.<br />
'''Note:''' All orbiters will likely do a FULL REGEN after this update, and it may appear that your system is hanging because of this. Please give it some time to finish the regen (could take up to an hour on large installs)<br />
<br />
* lmcevdr_1.1-10_all.deb<br />
* pluto-website-admin_2.0.0.44.0904010019_i386.deb<br />
* pluto-dynamic-dns_2.0.0.44.0904010019_i386.deb<br />
* lmce-launch-manager_2.0.0.44.0904010019_i386.deb<br />
* pluto-boot-scripts_2.0.0.44.0904010019_i386.deb<br />
* pluto-system-database_2.0.0.44.0904010019_i386.deb<br />
* pluto-orbitergen_2.0.0.44.0904010019_i386.deb<br />
* pluto-updateentarea_2.0.0.44.0904010019_i386.deb<br />
* pluto-orbiter_2.0.0.44.0904010019_i386.deb<br />
<br />
=== 20090405 (alpha 2.7) ===<br />
From now on, the SVN version will part of the deb name.<br />
You may need to uninstall 'lmcevdr' (dpkg -r --force-all lmcevdr) and reinstall it (apt-get install lmcevdr) to get around the install-script bug in last weeks .deb package. It worked for me. <br />
* lmce-game-player_2.0.0.44.090405.21873_i386.deb<br />
* lmce-game-plugin_2.0.0.44.090405.21873_i386.deb<br />
* lmce-launch-manager_2.0.0.44.090405.21873_i386.deb<br />
* lmce-phoenix-solo-usb_2.0.0.44.090405.21873_i386.deb<br />
* lmcevdr_1.1-10_all.deb (This is no main package, and therefore does not contain the regular version designation. It is based upon version 21875)<br />
* pluto-bluetooth-dongle_2.0.0.44.090405.21873_i386.deb<br />
* pluto-simplephone_2.0.0.44.090405.21873_i386.deb<br />
* pluto-system-database_2.0.0.44.090405.21873_i386.deb<br />
* pluto-website-admin_2.0.0.44.09040521873_i386.deb<br />
<br />
=== 20090412 (alpha 2.8) ===<br />
* pluto-text-to-speech_2.0.0.44.09041221886_i386.deb (283,284) - Finally, good voices will actually install (Nitech HTS Arctic). <br />
* pluto-system-database_2.0.0.44.09041221886_i386.deb (211) - New default voice is voice_nitech_us_slt_arctic_hts. - game plugin and player template cleanups<br />
* mce-diskless-tools_2.0.0.44.09041221886_i386.deb (627,628) - Update kernel image for diskless MDs upon regenning.<br />
* pluto-website-admin_2.0.0.44.09041221886_i386.deb (220) - Infrared codes will now properly come from schema.linuxmce.org<br />
* pluto-boot-scripts_2.0.0.44.09041221886_i386.deb (234)- also schema.linuxmce.org IR codes related.<br />
* pluto-motion-wrapper_2.0.0.44.09041221886_i386.deb (455,456) - changed config variable from ffmpeg_filename to movie_filename<br />
* lmce_launch_manager_2.0.0.44.09041221886_i386.deb (298,299) - LM Actions now work from CLI(such as reload, regen, reboot, etc...)<br />
* lmce-game-player_2.0.0.44.09041221886_i386.deb (673,674) - Rebuilt for new device template<br />
* lmce-game-plugin_2.0.0.44.09041221886_i386.deb (671,672) - Rebuilt for new device template<br />
* pluto-updateentarea_2.0.0.44.09041221886_i386.deb (341,342) - may need to be rebuilt for device template changes<br />
<br />
=== 20090413 (alpha 2.9 jondecker special) ===<br />
* pluto-text-to-speech_2.0.0.44.09041321887_i386.deb (283,284) - fixes stupid post-install typo<br />
* pluto-zwave-lighting_2.0.0.44.09041321891_i386.deb (505,506) - thermostate support<br />
<br />
=== 20090419 (alpha 2.10 pbr) ===<br />
* pluto-text-to-speech_2.0.0.44.09041921897_i386.deb<br />
* pluto-website-admin_2.0.0.44.09041921897_i386.deb<br />
* lmce-screen-capture-camera_2.0.0.44.09041921897_i386.deb<br />
* pluto-system-database_2.0.0.44.09041921897_i386.deb<br />
* lmce-game-plugin_2.0.0.44.09041921897_i386.deb<br />
* lmce-game-player_2.0.0.44.09041921897_i386.deb<br />
* pluto-asterisk_2.0.0.44.09041921897_i386.deb<br />
<br />
=== 20090426 (alpha 2.11) ===<br />
With this release, MythTV now takes advantage of storage groups. Do some recordings, and try recording to a few different storage groups. <br />
Please test this out and report any problems such as duplicate attributes appearing in pluto_media, icon image not showing up, recordings failing to record, etc. Also, if you do have problems, try a reboot and see if it fixes the problem, then please let me know if the reboot fixed your problem. - jondecker76<br />
<br />
'''POST-BUILD UPDATE:''' A couple of small bugs have been found that will be fixed in next week's build. 1) Some storage groups are missing the leading "/" in the path, causing problems images in mythweb, downloads in the mythweb, etc. 2) Unmounted storage devices were being skipped. This means that you may not have a storage group for some of your devices at some times. I am changing this so that the storage groups are created, and if for some reason it is not available when a recording is set to use the storage group, then the recording will go to the (always present) Default storage group.<br />
For those wanting to fix #1 right now, just edit /usr/pluto/bin/StorageDevices_PlutoDirStructure.sh and add a preceeding slash before the path beginning with 'home/....' on lines 214 and 226. After this modification, MythTV works great in all of the storage groups! (You should do a reboot after making the change)<br />
<br />
* lmcevdr_1.1-10_all.deb - more setup fixes, this time for the MD<br />
* pluto-boot-scripts_2.0.0.44.09042621919_i386.deb (234) - small fix to get rid of a warning on DCERouter startup re missing dir., New MythTV directory structure stuff<br />
* pluto-asterisk_2.0.0.44.09042621919_i386.deb (270,271) - Added Support for Cisco 7910 phone<br />
* pluto-dhcpd-plugin_2.0.0.44.09042621919_i386.deb (302) - Added support for Cisco 7910 phone<br />
* pluto-system-database_2.0.0.44.09042621919_i386.deb (211) - '''If new devices are added, the pluto-system-database needs to be updates as well'''<br />
* pluto-storage-devices_2.0.0.44.09042621919_i386.deb (533) - Adds new tv_shows_* directories. Generates MythTV storage groups<br />
* pluto-std-plugins_2.0.0.44.09042621919_i386.deb (134,153) - adds some useful debugging snippets that helped trace down the problem of mythtv attributes not adding to pluto_media<br />
* pluto-mythtv-plugin_2.0.0.44.09042621919_i386.deb (134,153) - lots of changes to facilitate the new storage groups<br />
* pluto-network-storage_2.0.0.44.09042621919_i386.deb (503,508) - small changes to work with new tv_shows_* directories<br />
<br />
=== 20090429 (alpha 2.12) ===<br />
* pluto-storage-devices_2.0.0.44.09042921929_i386.deb (533) - Fixes some small bugs in MythTV storage groups<br />
* pluto-boot-scripts_2.0.0.44.09042921929_i386.deb (234) - misc. MythTV storage group enhancements<br />
* pluto-mythtv-plugin_2.0.0.44.09042921929_i386.deb (134,153) - misc. MythTV storage group enhancement<br />
* mce-diskless-tools_2.0.0.44.09042921929_i386.changes (627,628) - lots of fixes for MD boot- Changes effect new installs only<br />
* pluto-system-database_2.0.0.44.09042921929_i386.deb (211) - Fixes hardy issue in sources.list<br />
* pluto-nvidia-video-drivers_2.0.0.44.09042921929_i386.deb (490) - changed the package requirement to nvidia-glx-180 for intrepid<br />
<br />
=== 20090501 (alpha 2.13) ===<br />
There are a few more MythTV storage group changes in this build. Please understand that the storage group name changes may throw mythweb out of whack on some old recordings, but this should be minimal. The old "user_*/<storage_device>" naming scheme is replaced with a "<username>:<storage_device>" naming convention. This will appeal to many more users than the user_* convention. Also, there is now support for custom storage groups. You can make your own storage groups now on top of the auto-generated LMCE ones by prepending with "custom:" (for example, you may make a new storage group named "custom:MyDrive", and it will not be removed or overwritten by the scripts that generate the storage groups). One last change is in the "Default" storage group - it no longer points to the drive with most space. This was changed because eventually it would throw mythweb for a loop once the paths changed. I will look into a better way to defaultly record to the drive with most space, most likely using recording profiles.<br />
<br />
* lmce-launch-manager (298,299) - db wrapper fix to handle empty resultsets<br />
* pluto-bluetooth-dongle (124,143) - fix some connection issues in JavaMO<br />
* pluto-mythtv-plugin (134,153)<br />
* pluto-storage-devices (533)<br />
* pluto-boot-scripts (234) - MD fixes<br />
* mce-diskless-tools (391) - MD fixes<br />
* pluto-install-scripts (627,628) - MD fixes<br />
* pluto-x-scripts (520,523) - AV Wizard fix for MD<br />
* pluto-zwave-lighting (505,506) - Init speedup<br />
<br />
=== 20090503 (alpha2.14) ===<br />
* pluto-zwave-lighting_2.0.0.44.09050321942_i386.deb (505,506) - boolean fixes<br />
<br />
=== 20090505 (alpha2.15) ===<br />
KDE on the MD should work now. The first boot of the system after the update will take a bit longer, as stuff that has not worked, is now being executed for the first time.<br />
<br />
* mce-diskless-tools_2.0.0.44.09050521951_i386.deb (627,628) - Lots of small fixes<br />
* pluto-system-database_2.0.0.44.09050521951_i386.deb (211) - More hardy extinction<br />
* pluto-boot-scripts_2.0.0.44.09050521951_i386.deb (234) - Small bug with regards to MySQL authorization fixed, which results in a running KDE on the MD, again.<br />
<br />
=== 20090505 (alpha2.16 snafu fix) ===<br />
* pluto-boot-scripts_2.0.0.44.09050521958_i386.deb (234) - snafu causing weird things and corruption on updates<br />
<br />
=== 20090506 (alpha2.17) ===<br />
* pluto-asterisk_2.0.0.44.09050621962_i386.deb (270,271) - Additional australian provider in the web admin (VoIPWA) and some janitory work.<br />
* pluto-boot-scripts_2.0.0.44.09050621962_i386.deb (234) - Additional visual feedback during the first boot, after running the AV Wizard<br />
<br />
=== 20090507 (alpha2.18)===<br />
* pluto-dhcpd-plugin_2.0.0.44.09050721973_i386.deb (302) - Pnp script for Cisco 7910, aastra (aastra still needs a device template)<br />
* lmce-launch-manager_2.0.0.44.09050721973_i386.deb (298,299) - Launch manager is now started in its own screen session<br />
* pluto-system-database_2.0.0.44.09050721973_i386.deb (211) - Removal of X Client Data as a dependency<br />
* pluto-mythtv-plugin_2.0.0.44.09050721973_i386.deb (134,153) - small changes to keep backend in sync<br />
* pluto-storage-devices_2.0.0.44.09050721973_i386.deb (533) - Updates the Default and LiveTV storage groups so they use the drive with most space<br />
* pluto-boot-scripts_2.0.0.44.09050721973_i386.deb (234) - Better detection of Intel Mobile Graphics adapter<br />
<br />
=== 20090511 (alpha2.19) ===<br />
* lmcevdr - more VDR configuration settings<br />
* pluto-boot-scripts_2.0.0.44.09051121983_i386.deb (234) - Another KDE Desktop on MD fix<br />
* mce-diskless-tools_2.0.0.44.09051121984_i386.deb (627,628) - Be agnostic about the compression format of tar archives, and more forgiving on download problems<br />
<br />
=== 20090515 (alpha2.20) ===<br />
* lmcevdr_1.1-10_all.deb - more VDR configuration settings<br />
* pluto-system-database_2.0.0.44.09051522002_i386.deb (211) - Additional package definitions (vdr-plugin-streamdev-server and vdr-plugin-streamdev-client)<br />
* pluto-hald_2.0.0.44.09051522002_i386.deb (529,530) - USB detection, better MCE2 support<br />
* pluto-vdr-plugin_2.0.0.44.09051522002_i386.deb (466,467) - Additional dependency for pluto-vdr-plugin to vdr-plugin-streamdev-server<br />
* lmce-launch-manager_2.0.0.44.09051522002_i386.deb (298,299) - Prompt user for reload after new MD creation (Requires manual re-run of Diskless_CreateTBZ.sh)<br />
* pluto-orbiter_2.0.0.44.09051522002_i386.deb (119,138) - Prompt user for reload after new MD creation (Requires manual re-run of Diskless_CreateTBZ.sh)<br />
* pluto-storage-devices_2.0.0.44.09051522003_i386.deb (533) - some small MythTV storage group tweaks<br />
* pluto-slim-server-streamer_2.0.0.44.09051522002_i386.deb (289,290) - changes to the configuraton script to start squeezecenter instead of slimserver<br />
* pluto-website-admin_2.0.0.44.09051522002_i386.deb (220) - Screen Saver section fixed<br />
* pluto-plutoutils_2.0.0.44.09051522002_i386.deb (197,196) - fix FileUtils::ReadURL method<br />
* pluto-std-plugins_2.0.0.44.09051522002_i386.deb (116,135) - support for external media in conjunction with playlists<br />
<br />
=== 20090520 (alpha2.21) ===<br />
* pluto-website-admin_2.0.0.44.09052022008_i386.deb (220) - GSD/IR code update fixes<br />
<br />
=== 20090601 (alpha 2.22) ===<br />
This update contains lots of changes to the storage mechanism. Make sure you can live without a working system for a while, in case things don't work out ...<br />
<br />
* pluto-system-database_2.0.0.44.09060122043_i386.deb (211) - More VDR related changes in the package definitions.<br />
* pluto-boot-scripts_2.0.0.44.09060122043_i386.deb (234) - New installations will use our own new_installation script, starting with number 1000000<br />
* pluto-std-plugins_2.0.0.44.09060122043_i386.deb (116,135) - fixed bug in playlist support<br />
* pluto-network-storage_2.0.0.44.09060122043_i386.deb (503,508) - New /home/public/data/pvr directory structure related<br />
* pluto-storage-devices_2.0.0.44.09060122043_i386.deb (533) - New /home/public/data/pvr directory structure related<br />
* pluto-mythtv-plugin_2.0.0.44.09060122043_i386.deb (134,153) - Storage group enhancements to use the new pvr directory, as well as addition of a new script to handle mythtv storagegroup creation and maintenance. Hopefully this will also fix some stability issues. Mythtv auto expire set from 1GB to 10GB to match the LMCE low disk space nag.<br />
* pluto-website-admin_2.0.0.44.09060122043_i386.deb (220) - more Pluto -> LMCE renames...<br />
* pluto-skins-basic_2.0.0.44.09060122043_i386.deb (204) - new art work for MythTV remote<br />
* pluto-zwave-lighting2.0.0.44.09060122043_i386.deb (505,506) - inclusion enhancements<br />
<br />
=== 20090609 (alpha 2.23) ===<br />
* pluto-boot-scripts_2.0.0.44.09060922056 (234)- backup procedure backs up pluto_media and mediapics<br />
* pluto-skins-basic_2.0.0.44.09060922056 (204) - more art work for MythTV remote on a mobile, remove pluto from more orbiter screens<br />
* pluto-system-database_2.0.0.44.09060922056 (211) - Updates to the MythTV remote and EnOcean package<br />
* pluto-zwave-lighting_2.0.0.44.09060922056 (505,506) - device reset capabilities<br />
* lmce-shoutcast-radio-plugin_2.0.0.44.09060922056 (703,704) - Initial shoutcast support<br />
<br />
=== 20090628 (alpha 2.24) ===<br />
* lmce-mediatomb_2.0.0.44.09062822099_i386.deb (702) - Support for MediaTomb UPnP Server. One day, I will understand why people don't put UPnP into a name, when it handles the configuration of a UPnP Server<br />
* pluto-asterisk_2.0.0.44.09062822099_i386.deb (270,271) - Make sure asterisk is owner of all /etc/asterisk files after updating the dialplan.<br />
* pluto-dhcpd-plugin_2.0.0.44.09062822099_i386.deb (302) - Make sure asterisk is owner of all /etc/asterisk files after adding IP phones<br />
* pluto-orbiter_2.0.0.44.09062822099_i386.deb (119,138) - Support for Gyration 3101<br />
* pluto-skins-basic_2.0.0.44.09062822099_i386.deb (204) - more art work for voice mail<br />
* pluto-slim-server-streamer_2.0.0.44.09062822099_i386.deb (289,290) - support playing of URLs via SqueezeBoxes, turn off SqueezeBoxes after stopping from Orbiter<br />
* pluto-std-plugins_2.0.0.44.09062822099_i386.deb (116,135) - Updates to voice mail datagrid, media streams by default attempt to grab a synopsis from the attribute database, if available, support for Gyration 3101<br />
* pluto-system-database_2.0.0.44.09062822099_i386.deb (211) - Updates to the voice mail screens, cursor no longer visible in video playback (Yeah, TschakEEE go!!!), Support for Gyration 3101<br />
* pluto-zwave-lighting_2.0.0.44.09062822099_i386.deb (505,506) - enhanced logging<br />
<br />
=== 20090721 (alpha 2.25) ===<br />
* lmce-shoutcast-radio-plugin_2.0.0.44.09072122164_i386.deb (703,704) - sanity check on configuration values, prevents excessive load when too low interval<br />
* pluto-bluetooth-dongle_2.0.0.44.09072122164_i386.deb (124,143) - JavaMO -Updated keymappings for SE phones, doesn't turn on backlight - saves phone battery<br />
* pluto-chromoflex_2.0.0.44.09072122164_i386.deb (711,712) - Initial support<br />
* pluto-dhcpd-plugin_2.0.0.44.09072122164_i386.deb (302) - Fixing overambitious deletion in configure_squeezebox.pl<br />
* pluto-irtrans-ethernet_2.0.0.44.09072122164_i386.deb (709,710) - Plug and play support for the IRTrans Ethernet dongles<br />
* pluto-orbiter_2.0.0.44.09072122164_i386.deb (119,138) - Fix of serious keyboard bug introduced in alpha 2.24<br />
* pluto-slim-server-streamer_2.0.0.44.09072122164_i386.deb (289,290) - Modified launch script. [http://svn.linuxmce.org/trac.cgi/ticket/282 Trac #282 Preserve media position when moving media]<br />
* pluto-slimserver-plugin_2.0.0.44.09072122164_i386.deb (425,425) - [http://svn.linuxmce.org/trac.cgi/ticket/282 Trac #282 Preserve media position when moving media]<br />
* pluto-standard-plugins_2.0.0.44.09072122164_i386.deb (116,135) - Changes to Media Plugin to make nicer output of playing media in Playlist datagrid.<br />
* pluto-system-database_2.0.0.44.09072122164_i386.deb (211) - Updates to device template #53.<br />
<br />
=== 20090722 (alpha2.26) ===<br />
* pluto-av-wizard_2.0.0.44.09072222170_i386.deb (556,555) - HDMI sound support<br />
* pluto-boot-scripts_2.0.0.44.09072222170_i386.deb (234) - HDMI sound support<br />
* pluto-website-admin_2.0.0.44.09072222170_i386.deb (220) - HDMI sound support<br />
** HDMI support requires ALSA 1.0.19 or later.<br />
<br />
=== upcoming... ===<br />
* lmce-activate-orbiter-plasmoid (707,708) - Plasmoid to re-activate Orbiter<br />
*<br />
<br />
== Previous alpha releases ==<br />
* Notes about [[LinuxMCE-0810 alpha1]]<br />
* Notes about [[LinuxMCE-0810 alpha0]]</div>Unihttp://wiki.linuxmce.org/index.php?title=LinuxMCE-0810_alpha2&diff=20130LinuxMCE-0810 alpha22009-07-30T20:25:56Z<p>Uni: /* Installation */</p>
<hr />
<div>[[Category:Versions]]<br />
{| align="right"<br />
| __TOC__<br />
|}<br />
<br />
==Installation==<br />
# Install Kubuntu Intrepid desktop, update it and enable the restricted (video) drivers if needed. (download Kubuntu 8.10 '''desktop''' release from one of these: [http://mirrors.ccs.neu.edu/releases.ubuntu.com/kubuntu/8.10/ Northeastern University Mirror, USA], [http://swtsrv.informatik.uni-mannheim.de/pub/linux/distributions/ubuntu-release/kubuntu/8.10/ Mannheim University Mirror, Germany]) '''Currently, only the 32bit version of LinuxMCE is available. Only download the i386 version of 8.10 Kubuntu, even if your system can support 64bit versions.'''<br />
# Run aptitude update and aptitude dist-upgrade to get the latest Kubuntu updates.<br />
# Grab the latest installer script from [http://deb.linuxmce.org/ubuntu here], unpack them and change into the freshly created ''new-installer'' directory.<br />
# Run the following scripts (as root, in order): pre-install-from-repo.sh, mce-install.sh, post-install.sh.<br />
# Reboot, wait for the activity to stop (see progress on console 8).<br />
<br />
EDIT: MAKE SURE YOUR INTERNET CONNECTION IS ON ETH0! (For linux Newbies ETH0 is probably the network card on your motherboard...or plug all NICs into a switch)<br />
<br />
In other words, after installing Kubuntu:<br />
sudo su - #This might ask for the password you specified earlier during the install of kubuntu.<br />
aptitude update<br />
aptitude dist-upgrade<br />
wget -c http://deb.linuxmce.org/ubuntu/new-installer-alpha-latest.tar.gz<br />
tar xvf new-installer-alpha-latest.tar.gz<br />
cd new-installer<br />
./pre-install-from-repo.sh<br />
./mce-install.sh<br />
./post-install.sh<br />
reboot<br />
<br />
=== HDMI Audio ===<br />
If you installed 0810 Alpha 2.26 or earlier you will need to do apt-get dist-upgrade on your Core & MD's to get the updated AVwizard that enables HDMI audio to be easily configured... this will get you the new AVwizard and any other fixes changes since you last upgraded. For the time being you will need to upgrade nVidia (180.60 or greater) & alsa (1.0.20 or later) drivers by hand.<br />
<br />
Updated AVwizard notes;<br />
<br />
The new AVwizard now allows you to select primary & secondary HDMI/VGA connectors using the keyboard. Press '1' for HDMI 1 and 'Q' for HDMI 2 and press '2' for VGA 1 and 'S' for VGA 2. Once in the Graphical AVwizard UI you will notice that these new connectors are now available for selection. you will also notice that the AVwizard now has a new screen layout for selecting the Audio output and also includes 'HDMI' as one of the output connector options. Select 'HDMI' from this screen if you want Stereo output then in the following screen respond 'No' to Dolby Digital and DTS. If you want surround audio to be routed out of the HDMI connector (mainly used with surround amplifiers with HDMI inputs) then select 'HDMI' and then answers 'yes' to the Dolby Digital & DTS wizard screens.<br />
<br />
=== nVidia Restricted Driver ===<br />
<strike>Install the nVidia restricted driver (177) from KDE using the Hardware Manager ''before'' installing LinuxMCE 0810 Alpha for the best results</strike> The installer will now automatically choose and install the correct restricted driver during setup.It will be installed after selecting "OpenGL" on your Media Director in web admin page.<br />
<br />
=== MythTV ===<br />
<strike>Remove reference to hardy in /etc/apt/sources.list<br />
<br />
from terminal<br />
<pre><br />
sudo apt-get install pluto-mythtv-player<br />
</pre><br />
<br />
Install updated version of pluto-mythtv-plugin</strike><br />
<br />
=== Setup Diskless MD ===<br />
<strike>Follow the steps from [[LinuxMCE-0810_alpha1#Setup_Diskless_MD|alpha1]].</strike><br />
<br />
=== Upgrading kernel ===<br />
<strike>There are issues with the ''fglrx'' driver that are documented in Ubuntu's bug tracking system. If you're experiencing those issues, upgrade the kernel to ''2.6.27-13'' or better. [[Upgrading the Kernel]] has been updated with instructions on doing this.</strike> The latest official kernel is -14<br />
<br />
== Updates ==<br />
Check if there is no junk like references to hardy in /etc/apt/sources.list then:<br />
sudo apt-get update<br />
sudo apt-get dist-upgrade<br />
Or use a package manager on the KDE desktop for more convenience.<br />
<br />
=== 20090218 (alpha-2.1) ===<br />
*lmce-datalog-db_2.0.0.44.0902180810<br />
*lmce-datalogger-plugin_2.0.0.44.0902180810<br />
*lmce-enocean-tcm120_2.0.0.44.0902180810<br />
*lmce-src-datalogger-plugin_2.0.0.44.0902180810<br />
*lmce-src-enocean-tcm120_2.0.0.44.0902180810<br />
*lmce-src-lmce-datalog_2.0.0.44.0902180810<br />
*pluto-dcerouter_2.0.0.44.0902180810<br />
*pluto-dhcpd-plugin_2.0.0.44.0902180810<br />
*pluto-hald-src_2.0.0.44.0902180810<br />
*pluto-hald_2.0.0.44.0902180810<br />
*pluto-mythtv-plugin_2.0.0.44.0902180810<br />
*pluto-orbitergen_2.0.0.44.0902180810<br />
*pluto-src-dcerouter_2.0.0.44.0902180810<br />
*pluto-src-hal-device-finder_2.0.0.44.0902180810<br />
*pluto-src-mythtv-plugin_2.0.0.44.0902180810<br />
*pluto-src-orbitergen_2.0.0.44.0902180810<br />
*pluto-src-updatemedia_2.0.0.44.0902180810<br />
*pluto-updateentarea_2.0.0.44.0902180810<br />
*pluto-updatemedia_2.0.0.44.0902180810<br />
*pluto-zwave-lighting_2.0.0.44.0902180810<br />
*lmce-game-player_2.0.0.44.0902180810<br />
*lmce-game-plugin_2.0.0.44.0902180810<br />
*lmce-src-game-player_2.0.0.44.0902180810<br />
*lmce-src-game-plugin_2.0.0.44.0902180810<br />
<br />
==== 20090222 (alpha-2.1.1) ====<br />
*pluto-dcerouter_2.0.0.44.0902220810<br />
*pluto-bluetooth-dongle_2.0.0.44.0902220810<br />
<br />
=== 20090301 (alpha-2.2) ===<br />
SVN revision: 21746<br />
<br />
To avoid a known problem when upgrading pluto-storage-devices, forcefully remove it before upgrading and let apt fix it:<br />
dpkg -r --force-all pluto-storage-devices<br />
apt-get update<br />
apt-get install -f<br />
Also please note that installing the upgrade of pluto-system-database will OVERWRITE your existing pluto_main database. It is therefore advisable to make a backup first!<br />
mysqldump --skip-extended-insert pluto_main >pluto_main_$PK_Installation-`date '+%Y%m%d:%H%M%S'`.sql<br />
*pluto-boot-scripts_2.0.0.44.0903010810<br />
*pluto-network-storage_2.0.0.44.0903010810<br />
*pluto-skins-basic_2.0.0.44.0903010810<br />
*pluto-src-network-storage_2.0.0.44.0903010810<br />
*pluto-src-std-plugins_2.0.0.44.0903010810<br />
*pluto-src-updatemedia_2.0.0.44.0903010810<br />
*pluto-std-plugins_2.0.0.44.0903010810<br />
*pluto-storage-devices_2.0.0.44.0903010810<br />
*pluto-system-database_2.0.0.44.0903010810 <br />
*pluto-updatemedia_2.0.0.44.0903010810<br />
*pluto-website-admin_2.0.0.44.0903010810<br />
<br />
=== 20090308 (alpha-2.3) ===<br />
SVN revision: 21765<br />
<br />
Again it is wise to backup your database as there is a new pluto-system-database package, but this one will not overwrite your pluto_main database if it is already installed, it should do an sqlCVS update instead. <br />
Also remove the pluto-storage-devices, hopefully for the last time. <br />
See the previous upgrade [[LinuxMCE-0810_alpha2#20090301_.28alpha-2.2.29|above]] for details on how to do these things. <br />
<br />
*pluto-asterisk_2.0.0.44.0903080810<br />
*pluto-src-asterisk_2.0.0.44.0903080810<br />
*pluto-src-text-to-speech_2.0.0.44.0903080810<br />
*pluto-src-updatemedia_2.0.0.44.0903080810<br />
*pluto-storage-devices_2.0.0.44.0903080810<br />
*pluto-system-database_2.0.0.44.0903080810<br />
*pluto-text-to-speech_2.0.0.44.0903080810<br />
*pluto-updatemedia_2.0.0.44.0903080810<br />
*pluto-website-admin_2.0.0.44.0903080810<br />
<br />
=== 20090315 (alpha-2.4) ===<br />
SVN revision: 21798<br />
<br />
The web admin is being moved from pluto-admin to lmce-admin with this build. A redirect has been placed in pluto-admin to redirect to the new web admin URL to help smooth the transition. While every attempt has been made to make this a smooth transition, please be sure to file a trac ticket if you find bugs related to this move so I can get them taken care of - [[User:jondecker76|jondecker76]]<br />
<br />
<br />
The Asterisk IVR is broken in this release. For those that need to get it working/wish to try out new changes, do the following:<br />
sudo apt-get install libsox-fmt-all <br />
cd /usr/pluto/bin<br />
sudo rm generate_users_voicemenu.pl<br />
sudo wget http://svn.linuxmce.org/trac.cgi/browser/branches/LinuxMCE-0810/src/Asterisk/generate_users_voicemenu.pl?format=raw<br />
sudo chmod 755 generate_users_voicemenu.pl<br />
sudo ./generate_users_voicemenu.pl<br />
Be sure to have the default voice set up in the Text_To_Speech device's device data (its default is the ugly one we're already used to)! I also highly recommend following the instructions located at [http://wiki.linuxmce.org/index.php/Text_To_Speech http://wiki.linuxmce.org/index.php/Text_To_Speech] on how to install some better voices, and set the default voice to voice_nitech_us_slt_arctic_hts after you install the better voices (this is the best free voice available ATM). This should all work on next weeks build for those that can wait.. I'm still working on getting the better voices included by default, but need to check on licensing issues first.<br />
<br />
<br />
<br />
*pluto-asterisk_2.0.0.44.0903150810<br />
*pluto-boot-scripts_2.0.0.44.0903150810<br />
*pluto-makerelease_2.0.0.44.0903150810<br />
*pluto-newmdinteractor_2.0.0.44.0903150810<br />
*pluto-orbitergen_2.0.0.44.0903150810<br />
*pluto-proxy-orbiter_2.0.0.44.0903150810<br />
*pluto-src-asterisk_2.0.0.44.0903150810<br />
*pluto-src-makerelease_2.0.0.44.0903150810<br />
*pluto-src-newmdinteractor_2.0.0.44.0903150810<br />
*pluto-src-orbitergen_2.0.0.44.0903150810<br />
*pluto-src-proxy-orbiter_2.0.0.44.0903150810<br />
*pluto-src-std-plugins_2.0.0.44.0903150810<br />
*pluto-src-text-to-speech_2.0.0.44.0903150810<br />
*pluto-std-plugins_2.0.0.44.0903150810<br />
*pluto-system-database_2.0.0.44.0903150810<br />
*pluto-text-to-speech_2.0.0.44.0903150810<br />
*pluto-updateentarea_2.0.0.44.0903150810<br />
*pluto-website-admin_2.0.0.44.0903150810<br />
<br />
=== 20090322 (alpha-2.5) ===<br />
SVN revision: 21827<br />
<br />
*freepbx_0+2.3.1-2<br />
*pluto-asterisk_2.0.0.44.0903220810<br />
*pluto-dhcpd-plugin_2.0.0.44.0903220810<br />
*pluto-install-scripts_2.0.0.44.0903220810<br />
*pluto-raid-tools_2.0.0.44.0903220810<br />
*pluto-skins-basic_2.0.0.44.0903220810<br />
*pluto-src-asterisk_2.0.0.44.0903220810<br />
*pluto-website-admin_2.0.0.44.0903220810<br />
<br />
=== 20090401 (alpha-2.6) ===<br />
Note: This build will attempt to use Launch Manager to co-ordinate startup and shutdown of devices. While it is not 100% finished, it is working and stable. Please test it out and file any problems against trac ticket #48. Also, please note the following:<br />
I'm not sure on this, but you may have to manually install LM via apt-get<br />
After you upgrade, reboot your core <br />
CLI output of LM can be viewed on tty8 on the core, and tty1 on MD's (alt+ctrl+F8 and alt+ctrl+F1 respectively). You will have to manually switch back to the orbiter on tty7 when finished<br />
CLI output is not yet completely finished, so the top fields will be blank (this is normal for now)<br />
CLI output of the log messages is working however, so please take a peek at them on tty8/tty1 shortly after you hear the 2nd set of beeps on boot up (when the "x" cursor appears on the screen).<br />
You can further test out LM by switching to tty8/tty1 right after doing a router reload and watching the output and comparing it to what you would expect it to be.<br />
LM dos not yet track regen process and report the % done. This should be working in next week's build, however.<br />
If there are problems and/or you wish to restore previous functionality, the original /usr/pluto/bin/startCore.sh file can be restored from the backup /usr/pluto/bin/startCore.sh._backup, and the LM package removed<br />
LM is not yet properly daemonized. I'm saving this step for last after the socket layer is implemented and we get a client coded.<br />
'''Note:''' All orbiters will likely do a FULL REGEN after this update, and it may appear that your system is hanging because of this. Please give it some time to finish the regen (could take up to an hour on large installs)<br />
<br />
* lmcevdr_1.1-10_all.deb<br />
* pluto-website-admin_2.0.0.44.0904010019_i386.deb<br />
* pluto-dynamic-dns_2.0.0.44.0904010019_i386.deb<br />
* lmce-launch-manager_2.0.0.44.0904010019_i386.deb<br />
* pluto-boot-scripts_2.0.0.44.0904010019_i386.deb<br />
* pluto-system-database_2.0.0.44.0904010019_i386.deb<br />
* pluto-orbitergen_2.0.0.44.0904010019_i386.deb<br />
* pluto-updateentarea_2.0.0.44.0904010019_i386.deb<br />
* pluto-orbiter_2.0.0.44.0904010019_i386.deb<br />
<br />
=== 20090405 (alpha 2.7) ===<br />
From now on, the SVN version will part of the deb name.<br />
You may need to uninstall 'lmcevdr' (dpkg -r --force-all lmcevdr) and reinstall it (apt-get install lmcevdr) to get around the install-script bug in last weeks .deb package. It worked for me. <br />
* lmce-game-player_2.0.0.44.090405.21873_i386.deb<br />
* lmce-game-plugin_2.0.0.44.090405.21873_i386.deb<br />
* lmce-launch-manager_2.0.0.44.090405.21873_i386.deb<br />
* lmce-phoenix-solo-usb_2.0.0.44.090405.21873_i386.deb<br />
* lmcevdr_1.1-10_all.deb (This is no main package, and therefore does not contain the regular version designation. It is based upon version 21875)<br />
* pluto-bluetooth-dongle_2.0.0.44.090405.21873_i386.deb<br />
* pluto-simplephone_2.0.0.44.090405.21873_i386.deb<br />
* pluto-system-database_2.0.0.44.090405.21873_i386.deb<br />
* pluto-website-admin_2.0.0.44.09040521873_i386.deb<br />
<br />
=== 20090412 (alpha 2.8) ===<br />
* pluto-text-to-speech_2.0.0.44.09041221886_i386.deb (283,284) - Finally, good voices will actually install (Nitech HTS Arctic). <br />
* pluto-system-database_2.0.0.44.09041221886_i386.deb (211) - New default voice is voice_nitech_us_slt_arctic_hts. - game plugin and player template cleanups<br />
* mce-diskless-tools_2.0.0.44.09041221886_i386.deb (627,628) - Update kernel image for diskless MDs upon regenning.<br />
* pluto-website-admin_2.0.0.44.09041221886_i386.deb (220) - Infrared codes will now properly come from schema.linuxmce.org<br />
* pluto-boot-scripts_2.0.0.44.09041221886_i386.deb (234)- also schema.linuxmce.org IR codes related.<br />
* pluto-motion-wrapper_2.0.0.44.09041221886_i386.deb (455,456) - changed config variable from ffmpeg_filename to movie_filename<br />
* lmce_launch_manager_2.0.0.44.09041221886_i386.deb (298,299) - LM Actions now work from CLI(such as reload, regen, reboot, etc...)<br />
* lmce-game-player_2.0.0.44.09041221886_i386.deb (673,674) - Rebuilt for new device template<br />
* lmce-game-plugin_2.0.0.44.09041221886_i386.deb (671,672) - Rebuilt for new device template<br />
* pluto-updateentarea_2.0.0.44.09041221886_i386.deb (341,342) - may need to be rebuilt for device template changes<br />
<br />
=== 20090413 (alpha 2.9 jondecker special) ===<br />
* pluto-text-to-speech_2.0.0.44.09041321887_i386.deb (283,284) - fixes stupid post-install typo<br />
* pluto-zwave-lighting_2.0.0.44.09041321891_i386.deb (505,506) - thermostate support<br />
<br />
=== 20090419 (alpha 2.10 pbr) ===<br />
* pluto-text-to-speech_2.0.0.44.09041921897_i386.deb<br />
* pluto-website-admin_2.0.0.44.09041921897_i386.deb<br />
* lmce-screen-capture-camera_2.0.0.44.09041921897_i386.deb<br />
* pluto-system-database_2.0.0.44.09041921897_i386.deb<br />
* lmce-game-plugin_2.0.0.44.09041921897_i386.deb<br />
* lmce-game-player_2.0.0.44.09041921897_i386.deb<br />
* pluto-asterisk_2.0.0.44.09041921897_i386.deb<br />
<br />
=== 20090426 (alpha 2.11) ===<br />
With this release, MythTV now takes advantage of storage groups. Do some recordings, and try recording to a few different storage groups. <br />
Please test this out and report any problems such as duplicate attributes appearing in pluto_media, icon image not showing up, recordings failing to record, etc. Also, if you do have problems, try a reboot and see if it fixes the problem, then please let me know if the reboot fixed your problem. - jondecker76<br />
<br />
'''POST-BUILD UPDATE:''' A couple of small bugs have been found that will be fixed in next week's build. 1) Some storage groups are missing the leading "/" in the path, causing problems images in mythweb, downloads in the mythweb, etc. 2) Unmounted storage devices were being skipped. This means that you may not have a storage group for some of your devices at some times. I am changing this so that the storage groups are created, and if for some reason it is not available when a recording is set to use the storage group, then the recording will go to the (always present) Default storage group.<br />
For those wanting to fix #1 right now, just edit /usr/pluto/bin/StorageDevices_PlutoDirStructure.sh and add a preceeding slash before the path beginning with 'home/....' on lines 214 and 226. After this modification, MythTV works great in all of the storage groups! (You should do a reboot after making the change)<br />
<br />
* lmcevdr_1.1-10_all.deb - more setup fixes, this time for the MD<br />
* pluto-boot-scripts_2.0.0.44.09042621919_i386.deb (234) - small fix to get rid of a warning on DCERouter startup re missing dir., New MythTV directory structure stuff<br />
* pluto-asterisk_2.0.0.44.09042621919_i386.deb (270,271) - Added Support for Cisco 7910 phone<br />
* pluto-dhcpd-plugin_2.0.0.44.09042621919_i386.deb (302) - Added support for Cisco 7910 phone<br />
* pluto-system-database_2.0.0.44.09042621919_i386.deb (211) - '''If new devices are added, the pluto-system-database needs to be updates as well'''<br />
* pluto-storage-devices_2.0.0.44.09042621919_i386.deb (533) - Adds new tv_shows_* directories. Generates MythTV storage groups<br />
* pluto-std-plugins_2.0.0.44.09042621919_i386.deb (134,153) - adds some useful debugging snippets that helped trace down the problem of mythtv attributes not adding to pluto_media<br />
* pluto-mythtv-plugin_2.0.0.44.09042621919_i386.deb (134,153) - lots of changes to facilitate the new storage groups<br />
* pluto-network-storage_2.0.0.44.09042621919_i386.deb (503,508) - small changes to work with new tv_shows_* directories<br />
<br />
=== 20090429 (alpha 2.12) ===<br />
* pluto-storage-devices_2.0.0.44.09042921929_i386.deb (533) - Fixes some small bugs in MythTV storage groups<br />
* pluto-boot-scripts_2.0.0.44.09042921929_i386.deb (234) - misc. MythTV storage group enhancements<br />
* pluto-mythtv-plugin_2.0.0.44.09042921929_i386.deb (134,153) - misc. MythTV storage group enhancement<br />
* mce-diskless-tools_2.0.0.44.09042921929_i386.changes (627,628) - lots of fixes for MD boot- Changes effect new installs only<br />
* pluto-system-database_2.0.0.44.09042921929_i386.deb (211) - Fixes hardy issue in sources.list<br />
* pluto-nvidia-video-drivers_2.0.0.44.09042921929_i386.deb (490) - changed the package requirement to nvidia-glx-180 for intrepid<br />
<br />
=== 20090501 (alpha 2.13) ===<br />
There are a few more MythTV storage group changes in this build. Please understand that the storage group name changes may throw mythweb out of whack on some old recordings, but this should be minimal. The old "user_*/<storage_device>" naming scheme is replaced with a "<username>:<storage_device>" naming convention. This will appeal to many more users than the user_* convention. Also, there is now support for custom storage groups. You can make your own storage groups now on top of the auto-generated LMCE ones by prepending with "custom:" (for example, you may make a new storage group named "custom:MyDrive", and it will not be removed or overwritten by the scripts that generate the storage groups). One last change is in the "Default" storage group - it no longer points to the drive with most space. This was changed because eventually it would throw mythweb for a loop once the paths changed. I will look into a better way to defaultly record to the drive with most space, most likely using recording profiles.<br />
<br />
* lmce-launch-manager (298,299) - db wrapper fix to handle empty resultsets<br />
* pluto-bluetooth-dongle (124,143) - fix some connection issues in JavaMO<br />
* pluto-mythtv-plugin (134,153)<br />
* pluto-storage-devices (533)<br />
* pluto-boot-scripts (234) - MD fixes<br />
* mce-diskless-tools (391) - MD fixes<br />
* pluto-install-scripts (627,628) - MD fixes<br />
* pluto-x-scripts (520,523) - AV Wizard fix for MD<br />
* pluto-zwave-lighting (505,506) - Init speedup<br />
<br />
=== 20090503 (alpha2.14) ===<br />
* pluto-zwave-lighting_2.0.0.44.09050321942_i386.deb (505,506) - boolean fixes<br />
<br />
=== 20090505 (alpha2.15) ===<br />
KDE on the MD should work now. The first boot of the system after the update will take a bit longer, as stuff that has not worked, is now being executed for the first time.<br />
<br />
* mce-diskless-tools_2.0.0.44.09050521951_i386.deb (627,628) - Lots of small fixes<br />
* pluto-system-database_2.0.0.44.09050521951_i386.deb (211) - More hardy extinction<br />
* pluto-boot-scripts_2.0.0.44.09050521951_i386.deb (234) - Small bug with regards to MySQL authorization fixed, which results in a running KDE on the MD, again.<br />
<br />
=== 20090505 (alpha2.16 snafu fix) ===<br />
* pluto-boot-scripts_2.0.0.44.09050521958_i386.deb (234) - snafu causing weird things and corruption on updates<br />
<br />
=== 20090506 (alpha2.17) ===<br />
* pluto-asterisk_2.0.0.44.09050621962_i386.deb (270,271) - Additional australian provider in the web admin (VoIPWA) and some janitory work.<br />
* pluto-boot-scripts_2.0.0.44.09050621962_i386.deb (234) - Additional visual feedback during the first boot, after running the AV Wizard<br />
<br />
=== 20090507 (alpha2.18)===<br />
* pluto-dhcpd-plugin_2.0.0.44.09050721973_i386.deb (302) - Pnp script for Cisco 7910, aastra (aastra still needs a device template)<br />
* lmce-launch-manager_2.0.0.44.09050721973_i386.deb (298,299) - Launch manager is now started in its own screen session<br />
* pluto-system-database_2.0.0.44.09050721973_i386.deb (211) - Removal of X Client Data as a dependency<br />
* pluto-mythtv-plugin_2.0.0.44.09050721973_i386.deb (134,153) - small changes to keep backend in sync<br />
* pluto-storage-devices_2.0.0.44.09050721973_i386.deb (533) - Updates the Default and LiveTV storage groups so they use the drive with most space<br />
* pluto-boot-scripts_2.0.0.44.09050721973_i386.deb (234) - Better detection of Intel Mobile Graphics adapter<br />
<br />
=== 20090511 (alpha2.19) ===<br />
* lmcevdr - more VDR configuration settings<br />
* pluto-boot-scripts_2.0.0.44.09051121983_i386.deb (234) - Another KDE Desktop on MD fix<br />
* mce-diskless-tools_2.0.0.44.09051121984_i386.deb (627,628) - Be agnostic about the compression format of tar archives, and more forgiving on download problems<br />
<br />
=== 20090515 (alpha2.20) ===<br />
* lmcevdr_1.1-10_all.deb - more VDR configuration settings<br />
* pluto-system-database_2.0.0.44.09051522002_i386.deb (211) - Additional package definitions (vdr-plugin-streamdev-server and vdr-plugin-streamdev-client)<br />
* pluto-hald_2.0.0.44.09051522002_i386.deb (529,530) - USB detection, better MCE2 support<br />
* pluto-vdr-plugin_2.0.0.44.09051522002_i386.deb (466,467) - Additional dependency for pluto-vdr-plugin to vdr-plugin-streamdev-server<br />
* lmce-launch-manager_2.0.0.44.09051522002_i386.deb (298,299) - Prompt user for reload after new MD creation (Requires manual re-run of Diskless_CreateTBZ.sh)<br />
* pluto-orbiter_2.0.0.44.09051522002_i386.deb (119,138) - Prompt user for reload after new MD creation (Requires manual re-run of Diskless_CreateTBZ.sh)<br />
* pluto-storage-devices_2.0.0.44.09051522003_i386.deb (533) - some small MythTV storage group tweaks<br />
* pluto-slim-server-streamer_2.0.0.44.09051522002_i386.deb (289,290) - changes to the configuraton script to start squeezecenter instead of slimserver<br />
* pluto-website-admin_2.0.0.44.09051522002_i386.deb (220) - Screen Saver section fixed<br />
* pluto-plutoutils_2.0.0.44.09051522002_i386.deb (197,196) - fix FileUtils::ReadURL method<br />
* pluto-std-plugins_2.0.0.44.09051522002_i386.deb (116,135) - support for external media in conjunction with playlists<br />
<br />
=== 20090520 (alpha2.21) ===<br />
* pluto-website-admin_2.0.0.44.09052022008_i386.deb (220) - GSD/IR code update fixes<br />
<br />
=== 20090601 (alpha 2.22) ===<br />
This update contains lots of changes to the storage mechanism. Make sure you can live without a working system for a while, in case things don't work out ...<br />
<br />
* pluto-system-database_2.0.0.44.09060122043_i386.deb (211) - More VDR related changes in the package definitions.<br />
* pluto-boot-scripts_2.0.0.44.09060122043_i386.deb (234) - New installations will use our own new_installation script, starting with number 1000000<br />
* pluto-std-plugins_2.0.0.44.09060122043_i386.deb (116,135) - fixed bug in playlist support<br />
* pluto-network-storage_2.0.0.44.09060122043_i386.deb (503,508) - New /home/public/data/pvr directory structure related<br />
* pluto-storage-devices_2.0.0.44.09060122043_i386.deb (533) - New /home/public/data/pvr directory structure related<br />
* pluto-mythtv-plugin_2.0.0.44.09060122043_i386.deb (134,153) - Storage group enhancements to use the new pvr directory, as well as addition of a new script to handle mythtv storagegroup creation and maintenance. Hopefully this will also fix some stability issues. Mythtv auto expire set from 1GB to 10GB to match the LMCE low disk space nag.<br />
* pluto-website-admin_2.0.0.44.09060122043_i386.deb (220) - more Pluto -> LMCE renames...<br />
* pluto-skins-basic_2.0.0.44.09060122043_i386.deb (204) - new art work for MythTV remote<br />
* pluto-zwave-lighting2.0.0.44.09060122043_i386.deb (505,506) - inclusion enhancements<br />
<br />
=== 20090609 (alpha 2.23) ===<br />
* pluto-boot-scripts_2.0.0.44.09060922056 (234)- backup procedure backs up pluto_media and mediapics<br />
* pluto-skins-basic_2.0.0.44.09060922056 (204) - more art work for MythTV remote on a mobile, remove pluto from more orbiter screens<br />
* pluto-system-database_2.0.0.44.09060922056 (211) - Updates to the MythTV remote and EnOcean package<br />
* pluto-zwave-lighting_2.0.0.44.09060922056 (505,506) - device reset capabilities<br />
* lmce-shoutcast-radio-plugin_2.0.0.44.09060922056 (703,704) - Initial shoutcast support<br />
<br />
=== 20090628 (alpha 2.24) ===<br />
* lmce-mediatomb_2.0.0.44.09062822099_i386.deb (702) - Support for MediaTomb UPnP Server. One day, I will understand why people don't put UPnP into a name, when it handles the configuration of a UPnP Server<br />
* pluto-asterisk_2.0.0.44.09062822099_i386.deb (270,271) - Make sure asterisk is owner of all /etc/asterisk files after updating the dialplan.<br />
* pluto-dhcpd-plugin_2.0.0.44.09062822099_i386.deb (302) - Make sure asterisk is owner of all /etc/asterisk files after adding IP phones<br />
* pluto-orbiter_2.0.0.44.09062822099_i386.deb (119,138) - Support for Gyration 3101<br />
* pluto-skins-basic_2.0.0.44.09062822099_i386.deb (204) - more art work for voice mail<br />
* pluto-slim-server-streamer_2.0.0.44.09062822099_i386.deb (289,290) - support playing of URLs via SqueezeBoxes, turn off SqueezeBoxes after stopping from Orbiter<br />
* pluto-std-plugins_2.0.0.44.09062822099_i386.deb (116,135) - Updates to voice mail datagrid, media streams by default attempt to grab a synopsis from the attribute database, if available, support for Gyration 3101<br />
* pluto-system-database_2.0.0.44.09062822099_i386.deb (211) - Updates to the voice mail screens, cursor no longer visible in video playback (Yeah, TschakEEE go!!!), Support for Gyration 3101<br />
* pluto-zwave-lighting_2.0.0.44.09062822099_i386.deb (505,506) - enhanced logging<br />
<br />
=== 20090721 (alpha 2.25) ===<br />
* lmce-shoutcast-radio-plugin_2.0.0.44.09072122164_i386.deb (703,704) - sanity check on configuration values, prevents excessive load when too low interval<br />
* pluto-bluetooth-dongle_2.0.0.44.09072122164_i386.deb (124,143) - JavaMO -Updated keymappings for SE phones, doesn't turn on backlight - saves phone battery<br />
* pluto-chromoflex_2.0.0.44.09072122164_i386.deb (711,712) - Initial support<br />
* pluto-dhcpd-plugin_2.0.0.44.09072122164_i386.deb (302) - Fixing overambitious deletion in configure_squeezebox.pl<br />
* pluto-irtrans-ethernet_2.0.0.44.09072122164_i386.deb (709,710) - Plug and play support for the IRTrans Ethernet dongles<br />
* pluto-orbiter_2.0.0.44.09072122164_i386.deb (119,138) - Fix of serious keyboard bug introduced in alpha 2.24<br />
* pluto-slim-server-streamer_2.0.0.44.09072122164_i386.deb (289,290) - Modified launch script. [http://svn.linuxmce.org/trac.cgi/ticket/282 Trac #282 Preserve media position when moving media]<br />
* pluto-slimserver-plugin_2.0.0.44.09072122164_i386.deb (425,425) - [http://svn.linuxmce.org/trac.cgi/ticket/282 Trac #282 Preserve media position when moving media]<br />
* pluto-standard-plugins_2.0.0.44.09072122164_i386.deb (116,135) - Changes to Media Plugin to make nicer output of playing media in Playlist datagrid.<br />
* pluto-system-database_2.0.0.44.09072122164_i386.deb (211) - Updates to device template #53.<br />
<br />
=== 20090722 (alpha2.26) ===<br />
* pluto-av-wizard_2.0.0.44.09072222170_i386.deb (556,555) - HDMI sound support<br />
* pluto-boot-scripts_2.0.0.44.09072222170_i386.deb (234) - HDMI sound support<br />
* pluto-website-admin_2.0.0.44.09072222170_i386.deb (220) - HDMI sound support<br />
** HDMI support requires ALSA 1.0.19 or later.<br />
<br />
=== upcoming... ===<br />
* lmce-activate-orbiter-plasmoid (707,708) - Plasmoid to re-activate Orbiter<br />
*<br />
<br />
== Previous alpha releases ==<br />
* Notes about [[LinuxMCE-0810 alpha1]]<br />
* Notes about [[LinuxMCE-0810 alpha0]]</div>Unihttp://wiki.linuxmce.org/index.php?title=User:UNi&diff=18784User:UNi2009-05-04T17:54:00Z<p>Uni: /* MOTHERBOARD */</p>
<hr />
<div>[[Category:User Setups]]<br />
<br />
= '''About Me''' =<br />
<br />
I've been working with OpenBSD and Linux for 10 years, but never delved into X-Windows as I use OBSD mainly for LAMP functions. I live in Northern California (NorCAL) and work as a Network Engineer.<br />
<br />
= '''LinuxMCE''' =<br />
<br />
After having major crashing issues with LMCE, I found that it didn't like my video card so much (though others recommended it...); it would crash X-Windows. Also video card was sharing an interrupt with my NIC. I have resolved these issues by going back to my initial build Video Card, and installing a new NIC which doesn't try to mate with my Vid Card's interrupt. My box is very stable now and never crashes and I'm really enjoying LMCE now.<br />
<br />
<br />
== '''Next Steps''' ==<br />
<br />
<br />
<br />
* setup a MD after I'm sure the Core is stable and maybe wait until 810 before investing any more moola<br />
<br />
= '''Configuration''' =<br />
<br />
<br />
== '''Core''' ==<br />
<br />
<br />
<br />
<br />
=== Components: ===<br />
<br />
<br />
==== CPU ====<br />
<br />
Intel Dual-Core<br />
<br />
==== MOTHERBOARD ====<br />
<br />
[[ASUS P5NSLI LGA 775 NVIDIA nForce 570 SLI Intel Edition ATX Intel Motherboard]]<br />
<br />
* This motherboard seems to work but I got a ton of "rtc: lost some interrupts at 1024Hz" in Syslog and no one seems to know why...I'm guessing it will be resolved in 810.<br />
<br />
<br />
* µATX<br />
<br />
* 4x DDR2 Slot<br />
<br />
* GF 7600<br />
<br />
* onboard 5.1 Audio<br />
<br />
* 1x Gigabit Marvell LAN<br />
<br />
* 1x PCI-E 16x<br />
<br />
* 2x PCI-E 1x<br />
<br />
* 1x PCI<br />
<br />
==== RAM ====<br />
<br />
2GB Infineon CL5<br />
<br />
==== Video Card ====<br />
<br />
BFG Tech BFGR76256GTOCE GeForce 7600GT 256MB<br />
<br />
==== STORAGE ====<br />
Western Digital Caviar SE16 WD2500KS 250GB 7200 RPM SATA 3.0Gb/s Hard Drive - OEM <br />
<br />
<br />
==== PSU ====<br />
<br />
<br />
<br />
==== CASE ====<br />
<br />
Enermax<br />
<br />
<br />
==== OTHER ====<br />
<br />
CPU-FAN:<br />
<br />
== '''Media Directors''' ==<br />
<br />
none so far<br />
<br />
<br />
<br />
= '''Automation''' =<br />
<br />
* Added a Linksys Wireless-G Internet Video Camera WVC54GCA, and enabled motion module</div>Unihttp://wiki.linuxmce.org/index.php?title=User:UNi&diff=18783User:UNi2009-05-04T17:53:04Z<p>Uni: /* '''LinuxMCE''' */</p>
<hr />
<div>[[Category:User Setups]]<br />
<br />
= '''About Me''' =<br />
<br />
I've been working with OpenBSD and Linux for 10 years, but never delved into X-Windows as I use OBSD mainly for LAMP functions. I live in Northern California (NorCAL) and work as a Network Engineer.<br />
<br />
= '''LinuxMCE''' =<br />
<br />
After having major crashing issues with LMCE, I found that it didn't like my video card so much (though others recommended it...); it would crash X-Windows. Also video card was sharing an interrupt with my NIC. I have resolved these issues by going back to my initial build Video Card, and installing a new NIC which doesn't try to mate with my Vid Card's interrupt. My box is very stable now and never crashes and I'm really enjoying LMCE now.<br />
<br />
<br />
== '''Next Steps''' ==<br />
<br />
<br />
<br />
* setup a MD after I'm sure the Core is stable and maybe wait until 810 before investing any more moola<br />
<br />
= '''Configuration''' =<br />
<br />
<br />
== '''Core''' ==<br />
<br />
<br />
<br />
<br />
=== Components: ===<br />
<br />
<br />
==== CPU ====<br />
<br />
Intel Dual-Core<br />
<br />
==== MOTHERBOARD ====<br />
<br />
[[ASUS P5NSLI LGA 775 NVIDIA nForce 570 SLI Intel Edition ATX Intel Motherboard]]<br />
<br />
* This motherboard seems to work but I got a ton of "rtc: lost some interrupts at 1024Hz" in Syslog and no one seems to know why...<br />
<br />
<br />
* µATX<br />
<br />
* 4x DDR2 Slot<br />
<br />
* GF 7600<br />
<br />
* onboard 5.1 Audio<br />
<br />
* 1x Gigabit Marvell LAN<br />
<br />
* 1x PCI-E 16x<br />
<br />
* 2x PCI-E 1x<br />
<br />
* 1x PCI<br />
<br />
==== RAM ====<br />
<br />
2GB Infineon CL5<br />
<br />
==== Video Card ====<br />
<br />
BFG Tech BFGR76256GTOCE GeForce 7600GT 256MB<br />
<br />
==== STORAGE ====<br />
Western Digital Caviar SE16 WD2500KS 250GB 7200 RPM SATA 3.0Gb/s Hard Drive - OEM <br />
<br />
<br />
==== PSU ====<br />
<br />
<br />
<br />
==== CASE ====<br />
<br />
Enermax<br />
<br />
<br />
==== OTHER ====<br />
<br />
CPU-FAN:<br />
<br />
== '''Media Directors''' ==<br />
<br />
none so far<br />
<br />
<br />
<br />
= '''Automation''' =<br />
<br />
* Added a Linksys Wireless-G Internet Video Camera WVC54GCA, and enabled motion module</div>Unihttp://wiki.linuxmce.org/index.php?title=User:UNi&diff=18782User:UNi2009-05-04T17:48:15Z<p>Uni: /* Components: */</p>
<hr />
<div>[[Category:User Setups]]<br />
<br />
= '''About Me''' =<br />
<br />
I've been working with OpenBSD and Linux for 10 years, but never delved into X-Windows as I use OBSD mainly for LAMP functions. I live in Northern California (NorCAL) and work as a Network Engineer.<br />
<br />
= '''LinuxMCE''' =<br />
<br />
After having major crashing issues with LMCE, I found that it didn't like my video card so much and same video card was sharing an interrupt with my NIC. I have resolved these issues by going back to my initial Video Card, and installing a new NIC which doesn't try to mate with my Vid Card's interrupt. My box is very stable now and never crashes.<br />
<br />
<br />
== '''Next Steps''' ==<br />
<br />
<br />
<br />
* setup a MD after I'm sure the Core is stable and maybe wait until 810 before investing any more moola<br />
<br />
= '''Configuration''' =<br />
<br />
<br />
== '''Core''' ==<br />
<br />
<br />
<br />
<br />
=== Components: ===<br />
<br />
<br />
==== CPU ====<br />
<br />
Intel Dual-Core<br />
<br />
==== MOTHERBOARD ====<br />
<br />
[[ASUS P5NSLI LGA 775 NVIDIA nForce 570 SLI Intel Edition ATX Intel Motherboard]]<br />
<br />
* This motherboard seems to work but I got a ton of "rtc: lost some interrupts at 1024Hz" in Syslog and no one seems to know why...<br />
<br />
<br />
* µATX<br />
<br />
* 4x DDR2 Slot<br />
<br />
* GF 7600<br />
<br />
* onboard 5.1 Audio<br />
<br />
* 1x Gigabit Marvell LAN<br />
<br />
* 1x PCI-E 16x<br />
<br />
* 2x PCI-E 1x<br />
<br />
* 1x PCI<br />
<br />
==== RAM ====<br />
<br />
2GB Infineon CL5<br />
<br />
==== Video Card ====<br />
<br />
BFG Tech BFGR76256GTOCE GeForce 7600GT 256MB<br />
<br />
==== STORAGE ====<br />
Western Digital Caviar SE16 WD2500KS 250GB 7200 RPM SATA 3.0Gb/s Hard Drive - OEM <br />
<br />
<br />
==== PSU ====<br />
<br />
<br />
<br />
==== CASE ====<br />
<br />
Enermax<br />
<br />
<br />
==== OTHER ====<br />
<br />
CPU-FAN:<br />
<br />
== '''Media Directors''' ==<br />
<br />
none so far<br />
<br />
<br />
<br />
= '''Automation''' =<br />
<br />
* Added a Linksys Wireless-G Internet Video Camera WVC54GCA, and enabled motion module</div>Unihttp://wiki.linuxmce.org/index.php?title=User:UNi&diff=18781User:UNi2009-05-04T17:43:33Z<p>Uni: /* '''LinuxMCE''' */</p>
<hr />
<div>[[Category:User Setups]]<br />
<br />
= '''About Me''' =<br />
<br />
I've been working with OpenBSD and Linux for 10 years, but never delved into X-Windows as I use OBSD mainly for LAMP functions. I live in Northern California (NorCAL) and work as a Network Engineer.<br />
<br />
= '''LinuxMCE''' =<br />
<br />
After having major crashing issues with LMCE, I found that it didn't like my video card so much and same video card was sharing an interrupt with my NIC. I have resolved these issues by going back to my initial Video Card, and installing a new NIC which doesn't try to mate with my Vid Card's interrupt. My box is very stable now and never crashes.<br />
<br />
<br />
== '''Next Steps''' ==<br />
<br />
<br />
<br />
* setup a MD after I'm sure the Core is stable and maybe wait until 810 before investing any more moola<br />
<br />
= '''Configuration''' =<br />
<br />
<br />
== '''Core''' ==<br />
<br />
<br />
<br />
<br />
=== Components: ===<br />
<br />
<br />
==== CPU ====<br />
<br />
Intel Dual-Core<br />
<br />
==== MOTHERBOARD ====<br />
<br />
[[ASUS P5NSLI LGA 775 NVIDIA nForce 570 SLI Intel Edition ATX Intel Motherboard]]<br />
<br />
* This motherboard seems to work but I got a ton of "rtc: lost some interrupts at 1024Hz" in Syslog and no one seems to know why...<br />
<br />
<br />
* µATX<br />
<br />
* 4x DDR2 Slot<br />
<br />
* GF 7600<br />
<br />
* onboard 5.1 Audio<br />
<br />
* 1x Gigabit Marvell LAN<br />
<br />
* 1x PCI-E 16x<br />
<br />
* 2x PCI-E 1x<br />
<br />
* 1x PCI<br />
<br />
==== RAM ====<br />
<br />
2GB Infineon CL5<br />
<br />
==== STORAGE ====<br />
Western Digital Caviar SE16 WD2500KS 250GB 7200 RPM SATA 3.0Gb/s Hard Drive - OEM <br />
<br />
<br />
==== PSU ====<br />
<br />
<br />
<br />
==== CASE ====<br />
<br />
Enermax<br />
<br />
<br />
==== OTHER ====<br />
<br />
CPU-FAN: <br />
<br />
<br />
== '''Media Directors''' ==<br />
<br />
none so far<br />
<br />
<br />
<br />
= '''Automation''' =<br />
<br />
* Added a Linksys Wireless-G Internet Video Camera WVC54GCA, and enabled motion module</div>Unihttp://wiki.linuxmce.org/index.php?title=Display_Drivers&diff=18633Display Drivers2009-04-21T23:28:45Z<p>Uni: /* Installation */</p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
[[Category: Tutorials]]<br />
[[Category: Hardware| ]]<br />
<br />
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.<br />
<br />
'''Note that this should normally not be necessary unless you have specific wishes or trouble getting your display to work properly.''' <br />
<br />
== Installation ==<br />
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. Before you get started on the below, you will want to (from recovery mode) issue this command ''"cat /proc/interrupts"'' and make sure your video card is not sharing an interrupt with another device, such as a NIC (network interface card). If it is, you could run into a lot of issues. Your output should look something like this, with your Video Card not sharing an interrupt, as reflected below in line 21 where the Nvidia stands alone:<br />
<br />
''19: 38492811 0 IO-APIC-fasteoi eth0 <br><br />
''20: 2 0 IO-APIC-fasteoi ehci_hcd:usb2 <br>''<br />
''21: 10938712 0 IO-APIC-fasteoi nvidia <br>''<br />
''<br />
=== ATI Chipsets ===<br />
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].<br />
<br />
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.<br />
<br />
==== Installing The ATI Driver ====<br />
<br />
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.<br />
<br />
'''Step 1'''<br />
<br />
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'.<br />
<br />
'''Step 2'''<br />
<br />
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;<br />
<br />
sudo su - <return><br />
ssh moonNN <return> (**where the NN is the device number for the MD we're configuring**)<br />
<br />
Alternatively do the following from the MD/Core you are configuring;<br />
<br />
Ctrl+Alt+2<br />
<br />
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;<br />
<br />
Firstly make sure our sources.list is up to date:<br />
<br />
apt-get update <return><br />
<br />
Now lets install the ATI driver and packages;<br />
<br />
apt-get install linux-restricted-modules-generic restricted-manager <return><br />
<br />
Answer 'Y' to installing new packages then do the following steps;<br />
<br />
apt-get install xorg-driver-fglrx <return><br />
depmod -a <return><br />
<br />
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;<br />
<br />
I use the console text editor 'joe' below but you can use whichever you prefer ('nano' is installed by default for example);<br />
<br />
joe /etc/X11/xorg.conf <return><br />
<br />
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;<br />
<br />
Driver "vesa"<br />
or<br />
Driver "ati"<br />
<br />
Change the string 'vesa' (or ati) to 'fglrx' which is the name of the ATI driver. The updated driver line should look like below;<br />
<br />
Driver "fglrx"<br />
<br />
Now save the changes you have made to xorg.conf.<br />
<br />
Now reboot the MD from the console with;<br />
<br />
reboot <return><br />
<br />
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.<br />
<br />
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.<br />
<br />
=== NVidia Chipsets ===<br />
<br />
==== Bugs ====<br />
If you are here, trying to update your driver because video is not working, remember that there is a bug with some Nvidia cards that makes graphical output always appear on the DVI plug, not the VGA plug. If you have a display attached to the VGA port on your adapter, buy a DVI to VGA converter plug before putting yourself through a lot of pain!<br />
<br />
==== Legacy Drivers ====<br />
With legacy drivers the AVWizard might crash because it could not load the nvidia-legacy kernel module. It is unclear why kdm will start and not the AVWizard. A quick fix is to set the '''Driver''' option for the video card in the ''/etc/X11/xorg.conf'' file to '''vesa'''. Go through the AVWizard and then change it back. Another option is to edit ''/etc/modprobe.d/aliases'' and add '''alias nvidia nvidia-legacy'''. Don't forget about this line when you switch to a newer card.<br />
<br />
==== Latest Drivers ====<br />
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. <br />
<br />
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. <br />
'''<you>@dcerouter:~$''' sudo -s<br />
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:<br />
'''root@dcerouter:~#''' wget <nowiki>http://us.download.nvidia.com/XFree86/Linux-x86/</nowiki>''<version>''<nowiki>/NVIDIA-Linux-x86-</nowiki>''<version>''<nowiki>-pkg1.run</nowiki><br />
3. Go to runlevel 1 to stop the currently running X-server. <br />
'''root@dcerouter:~#''' telinit 1 <br />
4. Execute the installer and follow instructions. a) Ignore the warning about runlevel 1 and b) don't bother looking for "precompiled kernel interfaces" (drivers).<br />
'''root@dcerouter:~#''' sh NVIDIA-Linux-x86-''<version>''-pkg1.run<br />
5. The installer will attempt to remove old legacy drivers. If it cannot, you may receive X errors (Eg. ''Error: API mismatch''). The solution is to manually remove or disable the legacy drivers. <br />
'''nano /etc/default/linux-restricted-modules-common''' <br />
Disable the NVIDIA linux-restricted kernel modules (nvidia, nvidia_legacy) by changing the DISABLED_MODULES line to read:<br />
'''DISABLED_MODULES="nv nvidia_new"'''<br />
6. 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.<br />
<br />
''** Update - Do a "sudo cat /proc/driver/nvidia/version" and make sure it reads something similar to this, matching the newest drivers you just installed: NVIDIA UNIX x86 Kernel Module 180.29. The "nvclock" utility is useful for monitoring GPU overheating''<br />
<br />
==== Media Directors ====<br />
Instructions for installing the latest nVidia driver on your media directors can be found in the [[Upgrading the Kernel#Video Drivers|upgrading the kernel]] wiki.<br />
<br />
=== Intel Chipsets ===<br />
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.<br />
<br />
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.<br />
<br />
==== For LinuxMCE-0704 ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
From man i810:<br />
Option "LinearAlloc" "integer"<br />
Allows more memory for the offscreen allocator. This usually<br />
helps in situations where HDTV movies are required to play but<br />
not enough offscreen memory is usually available. Set this to<br />
8160 for upto 1920x1080 HDTV support. Default 0KB (off).<br />
<br />
==== potential problem ====<br />
<br />
there can be a problem with some intel drivers, like the gma 3100. see [[bug/gma3100driver]] for further informations<br />
<br />
=== Via Chipsets ===<br />
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]<br />
<br />
The proprietary Via Unichrome driver works best with Linux MCE. Unfortunately this driver has intentionally been stripped of support for most GLX extensions. This driver does not support alpha blending which is a prerequisite of [[UI2]]. Via licenses the full featured driver to system integrators, such as [[Fiire]]. This licensed driver is not publicly available. Additionally there is a known incompatibility issue with the licensed driver and Linux MCE 0710. <br />
<br />
On April 08, 2008 Via announced a new open source initiative to help develop open drivers for certain video chipsets [http://www.phoronix.com/scan.php?page=article&item=via_oss&num=1]. This press release echos sour notes with many developers who have heard this tune many times before. No useful information or code has been released to date, striking yet another all to familiar chord in the open source community [http://www.phoronix.com/scan.php?page=article&item=via_bluff&num=1].<br />
<br />
'''HOW-TO VIA Openchrome driver for xorg:'''<br><br />
For VIA CX700M2 UniChrome PRO II Graphics (1" VIA units) or mainly via graphics:<br><br />
<br />
''shell into your box and do the following:''<br><br />
apt-get -y 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 subversion xserver-xorg-dev libdrm-dev libxvmc-dev<br />
<br />
cd /usr/src<br />
svn checkout http://svn.openchrome.org/svn/trunk openchrome<br />
cd openchrome*<br />
./autogen.sh --prefix=/usr<br />
make<br />
make install<br />
<br />
Now we have to edit /etc/X11/xorg.conf and change the device driver to via openchrome:<br><br />
vi /etc/X11/xorg.conf<br />
Go to<br />
Section "Device"<br />
and change<br />
Driver "vesa" <br />
to<br />
Driver "openchrome"<br />
save and test the compiled new driver with a: <br><br />
X :1<br />
and if your xwindow comes up, you can reboot and have fun<br><br />
<br />
=== Other Chipsets ===<br />
Please help out by adding more if you can.<br />
<br />
== Configuration ==<br />
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.<br />
<br />
=== Getting started ===<br />
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. <br />
<br />
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:<br />
telinit 1<br />
This wil stop the running X-server and drop you into rescue mode as well. <br />
<br />
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.<br />
<br />
=== Generating a template ===<br />
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. <br />
<br />
'''While there is no (other) X-server running''' you can create a template configuration file by running:<br />
X -configure<br />
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:<br />
X -config ~/xorg.conf.new<br />
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). <br />
<br />
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.<br />
<br />
Here is an example of such a generated file:<br />
<br />
Section "ServerLayout"<br />
Identifier "X.org Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Mouse0" "CorePointer"<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/etc/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/X11/misc"<br />
FontPath "/usr/X11R6/lib/X11/fonts/misc"<br />
FontPath "/usr/share/fonts/X11/cyrillic"<br />
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/Type1"<br />
FontPath "/usr/X11R6/lib/X11/fonts/Type1"<br />
FontPath "/usr/share/fonts/X11/100dpi"<br />
FontPath "/usr/share/fonts/X11/75dpi"<br />
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "extmod"<br />
Load "record"<br />
Load "xtrap"<br />
Load "dri"<br />
Load "glx"<br />
Load "dbe"<br />
Load "GLcore"<br />
Load "type1"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Keyboard0"<br />
Driver "kbd"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Mouse0"<br />
Driver "mouse"<br />
Option "Protocol" "auto"<br />
Option "Device" "/dev/input/mice"<br />
Option "ZAxisMapping" "4 5 6 7"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
EndSection<br />
<br />
Section "Device"<br />
### Available Driver options are:-<br />
### Values: &lt;i&gt;: integer, <f>: float, <bool>: "True"/"False",<br />
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"<br />
### [arg]: arg optional<br />
#Option "ShadowFB" # [<bool>]<br />
#Option "DefaultRefresh" # [<bool>]<br />
#Option "ModeSetClearScreen" # [<bool>]<br />
Identifier "Card0"<br />
Driver "vesa"<br />
''VendorName "ATI Technologies Inc"''<br />
''BoardName "ATI Radeon Xpress 1200 Series"''<br />
''BusID '''"PCI:1:5:0"'''''<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 1<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 4<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 8<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 15<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 16<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
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:<br />
X -scanpci<br />
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.<br />
<br />
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.<br />
<br />
=== Refresh rate / ModeLine ===<br />
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:<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
''HorizSync '''27-102''' # kHz''<br />
''VertRefresh '''50-160''' # Hz''<br />
EndSection<br />
<br />
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. <br />
<br />
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. <br />
* http://koala.ilog.fr/cgi-bin/nph-colas-modelines<br />
* http://xtiming.sourceforge.net/cgi-bin/xtiming.pl<br />
* http://www.bohne-lang.de/spec/linux/modeline/<br />
* http://amlc.berlios.de/<br />
* http://www.mythtv.org/wiki/index.php/Working_with_Modelines<br />
If one modeline doesn't work perfectly, try another, perhaps from another generator, because they can vary so much.<br />
<br />
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]-[&larr;Backspace] and readjust your settings. Most modern screens however simply report that the signal is out of range if this happens.<br />
<br />
=== Colordepth and resolution ===<br />
Specify the colordepth and resolution(s) you would like to use, like this:<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
''DefaultDepth '''24'''''<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
''Virtual '''1600 1200'''''<br />
''Modes '''"1600x1200" "1280x1024" "1024x768" "800x600" "640x480" "512x384" "400x300" "320x240"'''''<br />
EndSubSection<br />
EndSection<br />
<br />
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.<br />
<br />
=== DRI device permissions ===<br />
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.<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
<br />
=== Chipset driver ===<br />
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''').<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
''# Driver "'''vesa'''"''<br />
''Driver "'''fglrx'''"''<br />
VendorName "ATI Technologies Inc"<br />
BoardName "ATI Radeon Xpress 1200 Series"<br />
BusID "PCI:1:5:0"<br />
EndSection<br />
<br />
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.<br />
<br />
=== Physical display size ===<br />
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.<br />
<br />
Section "Monitor"<br />
...<br />
DisplaySize '''155 95'''<br />
EndSection<br />
<br />
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.<br />
<br />
=== Disable composite ===<br />
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.<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
EndSection<br />
<br />
=== Additional options ===<br />
To be continued, I don't think this is enough to get UI2 completely (either mode) going yet. Feel free to jump in anytime... <br />
<br />
<br />
Things still to sort out amongst others (i.e. what is it, do we need it and what are the settings if any):<br />
<br />
Section "Module"<br />
Load "i2c"<br />
Load "bitmap"<br />
Load "ddc"<br />
Load "freetype"<br />
Load "int10"<br />
Load "vbe"<br />
Load "speedo"<br />
Load "type1"<br />
Load "dbe"<br />
Load "glx"<br />
Load "v4l"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AIGLX" "off"<br />
EndSection<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
# Option "RENDER" "true"<br />
EndSection<br />
<br />
Option "PseudoColorVisuals" "off"<br />
Option "OpenGLOverlay" "off"<br />
Option "VideoOverlay" "off"<br />
Option "DesktopSetup" "clone"<br />
<br />
TV-out options, 2nd display, etc.<br />
<br />
<br />
== Troubleshooting ==<br />
<br />
=== The AVWizard crashes X-windows ===<br />
<br />
Try setting the [[#Chipset_driver]] option to '''vesa''', run the AVWizard again and then change the driver back to what it was.<br />
<br />
=== Black screen ===<br />
<br />
* 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.<br />
<br />
*One problem on nvidia-cards could be that it does not detect the right monitor.<br />
<br />
::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><br />
::where XXX is CRT, CRT-0, CRT-1, DVI-0, DVI-1, ...<br />
::Save and exit (nano: Ctrl+x) and restart the computer. In my case it was "CRT-1".<br />
<br />
=== X-windows won't start ===<br />
<br />
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]-[&larr;Backspace] simultaneous to quit (alternative: use "startx" and get the full desktop, if any), then reboot when it works and you're done.<br />
<br />
=== Signal out of range ===<br />
<br />
See ''[[#Refresh rate / ModeLine ]]'' above.<br />
<br />
=== Microscopic fonts in KDE ===<br />
<br />
See ''[[#Physical_display_size]]'' above.<br />
<br />
If the above does not work, probably Xorg is calculating the DPI value in the wrong way.<br />
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.<br />
<br />
If those values are too small, fonts will be displayed accordingly (i.e, VERY small)<br />
<br />
A workaround is to force Xorg to startup with a given DPI value.<br />
<br />
To achieve this the following steps are required:<br />
<br />
* edit the file /usr/pluto/bin/Start_X_Wrapper.sh on your MD where you are facing the font problem<br />
* find the line beginning with xinit<br />
* add "-dpi 96" (without quotes) at the end of this line<br />
* save the file and reboot MD<br />
<br />
Obviously it is possible to set DPI to something different than 96, according to specific needs.<br />
<br />
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.<br />
<br />
=== LinuxMCE keeps reconfiguring my display settings ===<br />
<br />
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.<br />
<br />
For LinuxMCE 710 simply comment out the line that says<br />
. /usr/pluto/bin/X-CleanupVideo.sh<br />
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.<br />
<br />
== See also ==<br />
* [http://www.mythtv.org/wiki/index.php/Main_Page MythTV wiki] <br />
* MythTV Experience [http://brentlagesse.net/~brent/mythtv.php]<br />
* [[X_Configuration_Scripts]]</div>Unihttp://wiki.linuxmce.org/index.php?title=Display_Drivers&diff=18632Display Drivers2009-04-21T23:27:55Z<p>Uni: /* Installation */</p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
[[Category: Tutorials]]<br />
[[Category: Hardware| ]]<br />
<br />
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.<br />
<br />
'''Note that this should normally not be necessary unless you have specific wishes or trouble getting your display to work properly.''' <br />
<br />
== Installation ==<br />
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. Before you get started on the below, you will want to (from recovery mode) issue this command ''"cat /proc/interrupts"'' and make sure your video card is not sharing an interrupt with another device, such as a NIC (network interface card). If it is, you could run into a lot of issues. Your output should look something like this, with your Video Card not sharing an interrupt, as reflected below:<br />
<br />
''19: 38492811 0 IO-APIC-fasteoi eth0 <br><br />
''20: 2 0 IO-APIC-fasteoi ehci_hcd:usb2 <br>''<br />
''21: 10938712 0 IO-APIC-fasteoi nvidia <br>''<br />
''<br />
=== ATI Chipsets ===<br />
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].<br />
<br />
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.<br />
<br />
==== Installing The ATI Driver ====<br />
<br />
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.<br />
<br />
'''Step 1'''<br />
<br />
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'.<br />
<br />
'''Step 2'''<br />
<br />
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;<br />
<br />
sudo su - <return><br />
ssh moonNN <return> (**where the NN is the device number for the MD we're configuring**)<br />
<br />
Alternatively do the following from the MD/Core you are configuring;<br />
<br />
Ctrl+Alt+2<br />
<br />
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;<br />
<br />
Firstly make sure our sources.list is up to date:<br />
<br />
apt-get update <return><br />
<br />
Now lets install the ATI driver and packages;<br />
<br />
apt-get install linux-restricted-modules-generic restricted-manager <return><br />
<br />
Answer 'Y' to installing new packages then do the following steps;<br />
<br />
apt-get install xorg-driver-fglrx <return><br />
depmod -a <return><br />
<br />
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;<br />
<br />
I use the console text editor 'joe' below but you can use whichever you prefer ('nano' is installed by default for example);<br />
<br />
joe /etc/X11/xorg.conf <return><br />
<br />
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;<br />
<br />
Driver "vesa"<br />
or<br />
Driver "ati"<br />
<br />
Change the string 'vesa' (or ati) to 'fglrx' which is the name of the ATI driver. The updated driver line should look like below;<br />
<br />
Driver "fglrx"<br />
<br />
Now save the changes you have made to xorg.conf.<br />
<br />
Now reboot the MD from the console with;<br />
<br />
reboot <return><br />
<br />
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.<br />
<br />
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.<br />
<br />
=== NVidia Chipsets ===<br />
<br />
==== Bugs ====<br />
If you are here, trying to update your driver because video is not working, remember that there is a bug with some Nvidia cards that makes graphical output always appear on the DVI plug, not the VGA plug. If you have a display attached to the VGA port on your adapter, buy a DVI to VGA converter plug before putting yourself through a lot of pain!<br />
<br />
==== Legacy Drivers ====<br />
With legacy drivers the AVWizard might crash because it could not load the nvidia-legacy kernel module. It is unclear why kdm will start and not the AVWizard. A quick fix is to set the '''Driver''' option for the video card in the ''/etc/X11/xorg.conf'' file to '''vesa'''. Go through the AVWizard and then change it back. Another option is to edit ''/etc/modprobe.d/aliases'' and add '''alias nvidia nvidia-legacy'''. Don't forget about this line when you switch to a newer card.<br />
<br />
==== Latest Drivers ====<br />
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. <br />
<br />
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. <br />
'''<you>@dcerouter:~$''' sudo -s<br />
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:<br />
'''root@dcerouter:~#''' wget <nowiki>http://us.download.nvidia.com/XFree86/Linux-x86/</nowiki>''<version>''<nowiki>/NVIDIA-Linux-x86-</nowiki>''<version>''<nowiki>-pkg1.run</nowiki><br />
3. Go to runlevel 1 to stop the currently running X-server. <br />
'''root@dcerouter:~#''' telinit 1 <br />
4. Execute the installer and follow instructions. a) Ignore the warning about runlevel 1 and b) don't bother looking for "precompiled kernel interfaces" (drivers).<br />
'''root@dcerouter:~#''' sh NVIDIA-Linux-x86-''<version>''-pkg1.run<br />
5. The installer will attempt to remove old legacy drivers. If it cannot, you may receive X errors (Eg. ''Error: API mismatch''). The solution is to manually remove or disable the legacy drivers. <br />
'''nano /etc/default/linux-restricted-modules-common''' <br />
Disable the NVIDIA linux-restricted kernel modules (nvidia, nvidia_legacy) by changing the DISABLED_MODULES line to read:<br />
'''DISABLED_MODULES="nv nvidia_new"'''<br />
6. 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.<br />
<br />
''** Update - Do a "sudo cat /proc/driver/nvidia/version" and make sure it reads something similar to this, matching the newest drivers you just installed: NVIDIA UNIX x86 Kernel Module 180.29. The "nvclock" utility is useful for monitoring GPU overheating''<br />
<br />
==== Media Directors ====<br />
Instructions for installing the latest nVidia driver on your media directors can be found in the [[Upgrading the Kernel#Video Drivers|upgrading the kernel]] wiki.<br />
<br />
=== Intel Chipsets ===<br />
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.<br />
<br />
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.<br />
<br />
==== For LinuxMCE-0704 ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
From man i810:<br />
Option "LinearAlloc" "integer"<br />
Allows more memory for the offscreen allocator. This usually<br />
helps in situations where HDTV movies are required to play but<br />
not enough offscreen memory is usually available. Set this to<br />
8160 for upto 1920x1080 HDTV support. Default 0KB (off).<br />
<br />
==== potential problem ====<br />
<br />
there can be a problem with some intel drivers, like the gma 3100. see [[bug/gma3100driver]] for further informations<br />
<br />
=== Via Chipsets ===<br />
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]<br />
<br />
The proprietary Via Unichrome driver works best with Linux MCE. Unfortunately this driver has intentionally been stripped of support for most GLX extensions. This driver does not support alpha blending which is a prerequisite of [[UI2]]. Via licenses the full featured driver to system integrators, such as [[Fiire]]. This licensed driver is not publicly available. Additionally there is a known incompatibility issue with the licensed driver and Linux MCE 0710. <br />
<br />
On April 08, 2008 Via announced a new open source initiative to help develop open drivers for certain video chipsets [http://www.phoronix.com/scan.php?page=article&item=via_oss&num=1]. This press release echos sour notes with many developers who have heard this tune many times before. No useful information or code has been released to date, striking yet another all to familiar chord in the open source community [http://www.phoronix.com/scan.php?page=article&item=via_bluff&num=1].<br />
<br />
'''HOW-TO VIA Openchrome driver for xorg:'''<br><br />
For VIA CX700M2 UniChrome PRO II Graphics (1" VIA units) or mainly via graphics:<br><br />
<br />
''shell into your box and do the following:''<br><br />
apt-get -y 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 subversion xserver-xorg-dev libdrm-dev libxvmc-dev<br />
<br />
cd /usr/src<br />
svn checkout http://svn.openchrome.org/svn/trunk openchrome<br />
cd openchrome*<br />
./autogen.sh --prefix=/usr<br />
make<br />
make install<br />
<br />
Now we have to edit /etc/X11/xorg.conf and change the device driver to via openchrome:<br><br />
vi /etc/X11/xorg.conf<br />
Go to<br />
Section "Device"<br />
and change<br />
Driver "vesa" <br />
to<br />
Driver "openchrome"<br />
save and test the compiled new driver with a: <br><br />
X :1<br />
and if your xwindow comes up, you can reboot and have fun<br><br />
<br />
=== Other Chipsets ===<br />
Please help out by adding more if you can.<br />
<br />
== Configuration ==<br />
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.<br />
<br />
=== Getting started ===<br />
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. <br />
<br />
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:<br />
telinit 1<br />
This wil stop the running X-server and drop you into rescue mode as well. <br />
<br />
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.<br />
<br />
=== Generating a template ===<br />
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. <br />
<br />
'''While there is no (other) X-server running''' you can create a template configuration file by running:<br />
X -configure<br />
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:<br />
X -config ~/xorg.conf.new<br />
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). <br />
<br />
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.<br />
<br />
Here is an example of such a generated file:<br />
<br />
Section "ServerLayout"<br />
Identifier "X.org Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Mouse0" "CorePointer"<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/etc/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/X11/misc"<br />
FontPath "/usr/X11R6/lib/X11/fonts/misc"<br />
FontPath "/usr/share/fonts/X11/cyrillic"<br />
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/Type1"<br />
FontPath "/usr/X11R6/lib/X11/fonts/Type1"<br />
FontPath "/usr/share/fonts/X11/100dpi"<br />
FontPath "/usr/share/fonts/X11/75dpi"<br />
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "extmod"<br />
Load "record"<br />
Load "xtrap"<br />
Load "dri"<br />
Load "glx"<br />
Load "dbe"<br />
Load "GLcore"<br />
Load "type1"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Keyboard0"<br />
Driver "kbd"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Mouse0"<br />
Driver "mouse"<br />
Option "Protocol" "auto"<br />
Option "Device" "/dev/input/mice"<br />
Option "ZAxisMapping" "4 5 6 7"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
EndSection<br />
<br />
Section "Device"<br />
### Available Driver options are:-<br />
### Values: &lt;i&gt;: integer, <f>: float, <bool>: "True"/"False",<br />
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"<br />
### [arg]: arg optional<br />
#Option "ShadowFB" # [<bool>]<br />
#Option "DefaultRefresh" # [<bool>]<br />
#Option "ModeSetClearScreen" # [<bool>]<br />
Identifier "Card0"<br />
Driver "vesa"<br />
''VendorName "ATI Technologies Inc"''<br />
''BoardName "ATI Radeon Xpress 1200 Series"''<br />
''BusID '''"PCI:1:5:0"'''''<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 1<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 4<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 8<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 15<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 16<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
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:<br />
X -scanpci<br />
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.<br />
<br />
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.<br />
<br />
=== Refresh rate / ModeLine ===<br />
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:<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
''HorizSync '''27-102''' # kHz''<br />
''VertRefresh '''50-160''' # Hz''<br />
EndSection<br />
<br />
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. <br />
<br />
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. <br />
* http://koala.ilog.fr/cgi-bin/nph-colas-modelines<br />
* http://xtiming.sourceforge.net/cgi-bin/xtiming.pl<br />
* http://www.bohne-lang.de/spec/linux/modeline/<br />
* http://amlc.berlios.de/<br />
* http://www.mythtv.org/wiki/index.php/Working_with_Modelines<br />
If one modeline doesn't work perfectly, try another, perhaps from another generator, because they can vary so much.<br />
<br />
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]-[&larr;Backspace] and readjust your settings. Most modern screens however simply report that the signal is out of range if this happens.<br />
<br />
=== Colordepth and resolution ===<br />
Specify the colordepth and resolution(s) you would like to use, like this:<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
''DefaultDepth '''24'''''<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
''Virtual '''1600 1200'''''<br />
''Modes '''"1600x1200" "1280x1024" "1024x768" "800x600" "640x480" "512x384" "400x300" "320x240"'''''<br />
EndSubSection<br />
EndSection<br />
<br />
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.<br />
<br />
=== DRI device permissions ===<br />
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.<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
<br />
=== Chipset driver ===<br />
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''').<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
''# Driver "'''vesa'''"''<br />
''Driver "'''fglrx'''"''<br />
VendorName "ATI Technologies Inc"<br />
BoardName "ATI Radeon Xpress 1200 Series"<br />
BusID "PCI:1:5:0"<br />
EndSection<br />
<br />
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.<br />
<br />
=== Physical display size ===<br />
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.<br />
<br />
Section "Monitor"<br />
...<br />
DisplaySize '''155 95'''<br />
EndSection<br />
<br />
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.<br />
<br />
=== Disable composite ===<br />
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.<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
EndSection<br />
<br />
=== Additional options ===<br />
To be continued, I don't think this is enough to get UI2 completely (either mode) going yet. Feel free to jump in anytime... <br />
<br />
<br />
Things still to sort out amongst others (i.e. what is it, do we need it and what are the settings if any):<br />
<br />
Section "Module"<br />
Load "i2c"<br />
Load "bitmap"<br />
Load "ddc"<br />
Load "freetype"<br />
Load "int10"<br />
Load "vbe"<br />
Load "speedo"<br />
Load "type1"<br />
Load "dbe"<br />
Load "glx"<br />
Load "v4l"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AIGLX" "off"<br />
EndSection<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
# Option "RENDER" "true"<br />
EndSection<br />
<br />
Option "PseudoColorVisuals" "off"<br />
Option "OpenGLOverlay" "off"<br />
Option "VideoOverlay" "off"<br />
Option "DesktopSetup" "clone"<br />
<br />
TV-out options, 2nd display, etc.<br />
<br />
<br />
== Troubleshooting ==<br />
<br />
=== The AVWizard crashes X-windows ===<br />
<br />
Try setting the [[#Chipset_driver]] option to '''vesa''', run the AVWizard again and then change the driver back to what it was.<br />
<br />
=== Black screen ===<br />
<br />
* 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.<br />
<br />
*One problem on nvidia-cards could be that it does not detect the right monitor.<br />
<br />
::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><br />
::where XXX is CRT, CRT-0, CRT-1, DVI-0, DVI-1, ...<br />
::Save and exit (nano: Ctrl+x) and restart the computer. In my case it was "CRT-1".<br />
<br />
=== X-windows won't start ===<br />
<br />
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]-[&larr;Backspace] simultaneous to quit (alternative: use "startx" and get the full desktop, if any), then reboot when it works and you're done.<br />
<br />
=== Signal out of range ===<br />
<br />
See ''[[#Refresh rate / ModeLine ]]'' above.<br />
<br />
=== Microscopic fonts in KDE ===<br />
<br />
See ''[[#Physical_display_size]]'' above.<br />
<br />
If the above does not work, probably Xorg is calculating the DPI value in the wrong way.<br />
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.<br />
<br />
If those values are too small, fonts will be displayed accordingly (i.e, VERY small)<br />
<br />
A workaround is to force Xorg to startup with a given DPI value.<br />
<br />
To achieve this the following steps are required:<br />
<br />
* edit the file /usr/pluto/bin/Start_X_Wrapper.sh on your MD where you are facing the font problem<br />
* find the line beginning with xinit<br />
* add "-dpi 96" (without quotes) at the end of this line<br />
* save the file and reboot MD<br />
<br />
Obviously it is possible to set DPI to something different than 96, according to specific needs.<br />
<br />
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.<br />
<br />
=== LinuxMCE keeps reconfiguring my display settings ===<br />
<br />
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.<br />
<br />
For LinuxMCE 710 simply comment out the line that says<br />
. /usr/pluto/bin/X-CleanupVideo.sh<br />
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.<br />
<br />
== See also ==<br />
* [http://www.mythtv.org/wiki/index.php/Main_Page MythTV wiki] <br />
* MythTV Experience [http://brentlagesse.net/~brent/mythtv.php]<br />
* [[X_Configuration_Scripts]]</div>Unihttp://wiki.linuxmce.org/index.php?title=Display_Drivers&diff=18631Display Drivers2009-04-21T23:27:27Z<p>Uni: /* Installation */</p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
[[Category: Tutorials]]<br />
[[Category: Hardware| ]]<br />
<br />
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.<br />
<br />
'''Note that this should normally not be necessary unless you have specific wishes or trouble getting your display to work properly.''' <br />
<br />
== Installation ==<br />
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. Before you get started on the below, you will want to (from recovery mode) issue this command ''"sudo cat /proc/interrupts"'' and make sure your video card is not sharing an interrupt with another device, such as a NIC (network interface card). If it is, you could run into a lot of issues. Your output should look something like this, with your Video Card not sharing an interrupt, as reflected below:<br />
<br />
''19: 38492811 0 IO-APIC-fasteoi eth0 <br><br />
''20: 2 0 IO-APIC-fasteoi ehci_hcd:usb2 <br>''<br />
''21: 10938712 0 IO-APIC-fasteoi nvidia <br>''<br />
''<br />
=== ATI Chipsets ===<br />
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].<br />
<br />
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.<br />
<br />
==== Installing The ATI Driver ====<br />
<br />
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.<br />
<br />
'''Step 1'''<br />
<br />
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'.<br />
<br />
'''Step 2'''<br />
<br />
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;<br />
<br />
sudo su - <return><br />
ssh moonNN <return> (**where the NN is the device number for the MD we're configuring**)<br />
<br />
Alternatively do the following from the MD/Core you are configuring;<br />
<br />
Ctrl+Alt+2<br />
<br />
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;<br />
<br />
Firstly make sure our sources.list is up to date:<br />
<br />
apt-get update <return><br />
<br />
Now lets install the ATI driver and packages;<br />
<br />
apt-get install linux-restricted-modules-generic restricted-manager <return><br />
<br />
Answer 'Y' to installing new packages then do the following steps;<br />
<br />
apt-get install xorg-driver-fglrx <return><br />
depmod -a <return><br />
<br />
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;<br />
<br />
I use the console text editor 'joe' below but you can use whichever you prefer ('nano' is installed by default for example);<br />
<br />
joe /etc/X11/xorg.conf <return><br />
<br />
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;<br />
<br />
Driver "vesa"<br />
or<br />
Driver "ati"<br />
<br />
Change the string 'vesa' (or ati) to 'fglrx' which is the name of the ATI driver. The updated driver line should look like below;<br />
<br />
Driver "fglrx"<br />
<br />
Now save the changes you have made to xorg.conf.<br />
<br />
Now reboot the MD from the console with;<br />
<br />
reboot <return><br />
<br />
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.<br />
<br />
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.<br />
<br />
=== NVidia Chipsets ===<br />
<br />
==== Bugs ====<br />
If you are here, trying to update your driver because video is not working, remember that there is a bug with some Nvidia cards that makes graphical output always appear on the DVI plug, not the VGA plug. If you have a display attached to the VGA port on your adapter, buy a DVI to VGA converter plug before putting yourself through a lot of pain!<br />
<br />
==== Legacy Drivers ====<br />
With legacy drivers the AVWizard might crash because it could not load the nvidia-legacy kernel module. It is unclear why kdm will start and not the AVWizard. A quick fix is to set the '''Driver''' option for the video card in the ''/etc/X11/xorg.conf'' file to '''vesa'''. Go through the AVWizard and then change it back. Another option is to edit ''/etc/modprobe.d/aliases'' and add '''alias nvidia nvidia-legacy'''. Don't forget about this line when you switch to a newer card.<br />
<br />
==== Latest Drivers ====<br />
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. <br />
<br />
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. <br />
'''<you>@dcerouter:~$''' sudo -s<br />
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:<br />
'''root@dcerouter:~#''' wget <nowiki>http://us.download.nvidia.com/XFree86/Linux-x86/</nowiki>''<version>''<nowiki>/NVIDIA-Linux-x86-</nowiki>''<version>''<nowiki>-pkg1.run</nowiki><br />
3. Go to runlevel 1 to stop the currently running X-server. <br />
'''root@dcerouter:~#''' telinit 1 <br />
4. Execute the installer and follow instructions. a) Ignore the warning about runlevel 1 and b) don't bother looking for "precompiled kernel interfaces" (drivers).<br />
'''root@dcerouter:~#''' sh NVIDIA-Linux-x86-''<version>''-pkg1.run<br />
5. The installer will attempt to remove old legacy drivers. If it cannot, you may receive X errors (Eg. ''Error: API mismatch''). The solution is to manually remove or disable the legacy drivers. <br />
'''nano /etc/default/linux-restricted-modules-common''' <br />
Disable the NVIDIA linux-restricted kernel modules (nvidia, nvidia_legacy) by changing the DISABLED_MODULES line to read:<br />
'''DISABLED_MODULES="nv nvidia_new"'''<br />
6. 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.<br />
<br />
''** Update - Do a "sudo cat /proc/driver/nvidia/version" and make sure it reads something similar to this, matching the newest drivers you just installed: NVIDIA UNIX x86 Kernel Module 180.29. The "nvclock" utility is useful for monitoring GPU overheating''<br />
<br />
==== Media Directors ====<br />
Instructions for installing the latest nVidia driver on your media directors can be found in the [[Upgrading the Kernel#Video Drivers|upgrading the kernel]] wiki.<br />
<br />
=== Intel Chipsets ===<br />
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.<br />
<br />
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.<br />
<br />
==== For LinuxMCE-0704 ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
From man i810:<br />
Option "LinearAlloc" "integer"<br />
Allows more memory for the offscreen allocator. This usually<br />
helps in situations where HDTV movies are required to play but<br />
not enough offscreen memory is usually available. Set this to<br />
8160 for upto 1920x1080 HDTV support. Default 0KB (off).<br />
<br />
==== potential problem ====<br />
<br />
there can be a problem with some intel drivers, like the gma 3100. see [[bug/gma3100driver]] for further informations<br />
<br />
=== Via Chipsets ===<br />
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]<br />
<br />
The proprietary Via Unichrome driver works best with Linux MCE. Unfortunately this driver has intentionally been stripped of support for most GLX extensions. This driver does not support alpha blending which is a prerequisite of [[UI2]]. Via licenses the full featured driver to system integrators, such as [[Fiire]]. This licensed driver is not publicly available. Additionally there is a known incompatibility issue with the licensed driver and Linux MCE 0710. <br />
<br />
On April 08, 2008 Via announced a new open source initiative to help develop open drivers for certain video chipsets [http://www.phoronix.com/scan.php?page=article&item=via_oss&num=1]. This press release echos sour notes with many developers who have heard this tune many times before. No useful information or code has been released to date, striking yet another all to familiar chord in the open source community [http://www.phoronix.com/scan.php?page=article&item=via_bluff&num=1].<br />
<br />
'''HOW-TO VIA Openchrome driver for xorg:'''<br><br />
For VIA CX700M2 UniChrome PRO II Graphics (1" VIA units) or mainly via graphics:<br><br />
<br />
''shell into your box and do the following:''<br><br />
apt-get -y 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 subversion xserver-xorg-dev libdrm-dev libxvmc-dev<br />
<br />
cd /usr/src<br />
svn checkout http://svn.openchrome.org/svn/trunk openchrome<br />
cd openchrome*<br />
./autogen.sh --prefix=/usr<br />
make<br />
make install<br />
<br />
Now we have to edit /etc/X11/xorg.conf and change the device driver to via openchrome:<br><br />
vi /etc/X11/xorg.conf<br />
Go to<br />
Section "Device"<br />
and change<br />
Driver "vesa" <br />
to<br />
Driver "openchrome"<br />
save and test the compiled new driver with a: <br><br />
X :1<br />
and if your xwindow comes up, you can reboot and have fun<br><br />
<br />
=== Other Chipsets ===<br />
Please help out by adding more if you can.<br />
<br />
== Configuration ==<br />
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.<br />
<br />
=== Getting started ===<br />
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. <br />
<br />
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:<br />
telinit 1<br />
This wil stop the running X-server and drop you into rescue mode as well. <br />
<br />
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.<br />
<br />
=== Generating a template ===<br />
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. <br />
<br />
'''While there is no (other) X-server running''' you can create a template configuration file by running:<br />
X -configure<br />
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:<br />
X -config ~/xorg.conf.new<br />
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). <br />
<br />
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.<br />
<br />
Here is an example of such a generated file:<br />
<br />
Section "ServerLayout"<br />
Identifier "X.org Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Mouse0" "CorePointer"<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/etc/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/X11/misc"<br />
FontPath "/usr/X11R6/lib/X11/fonts/misc"<br />
FontPath "/usr/share/fonts/X11/cyrillic"<br />
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/Type1"<br />
FontPath "/usr/X11R6/lib/X11/fonts/Type1"<br />
FontPath "/usr/share/fonts/X11/100dpi"<br />
FontPath "/usr/share/fonts/X11/75dpi"<br />
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "extmod"<br />
Load "record"<br />
Load "xtrap"<br />
Load "dri"<br />
Load "glx"<br />
Load "dbe"<br />
Load "GLcore"<br />
Load "type1"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Keyboard0"<br />
Driver "kbd"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Mouse0"<br />
Driver "mouse"<br />
Option "Protocol" "auto"<br />
Option "Device" "/dev/input/mice"<br />
Option "ZAxisMapping" "4 5 6 7"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
EndSection<br />
<br />
Section "Device"<br />
### Available Driver options are:-<br />
### Values: &lt;i&gt;: integer, <f>: float, <bool>: "True"/"False",<br />
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"<br />
### [arg]: arg optional<br />
#Option "ShadowFB" # [<bool>]<br />
#Option "DefaultRefresh" # [<bool>]<br />
#Option "ModeSetClearScreen" # [<bool>]<br />
Identifier "Card0"<br />
Driver "vesa"<br />
''VendorName "ATI Technologies Inc"''<br />
''BoardName "ATI Radeon Xpress 1200 Series"''<br />
''BusID '''"PCI:1:5:0"'''''<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 1<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 4<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 8<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 15<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 16<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
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:<br />
X -scanpci<br />
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.<br />
<br />
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.<br />
<br />
=== Refresh rate / ModeLine ===<br />
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:<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
''HorizSync '''27-102''' # kHz''<br />
''VertRefresh '''50-160''' # Hz''<br />
EndSection<br />
<br />
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. <br />
<br />
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. <br />
* http://koala.ilog.fr/cgi-bin/nph-colas-modelines<br />
* http://xtiming.sourceforge.net/cgi-bin/xtiming.pl<br />
* http://www.bohne-lang.de/spec/linux/modeline/<br />
* http://amlc.berlios.de/<br />
* http://www.mythtv.org/wiki/index.php/Working_with_Modelines<br />
If one modeline doesn't work perfectly, try another, perhaps from another generator, because they can vary so much.<br />
<br />
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]-[&larr;Backspace] and readjust your settings. Most modern screens however simply report that the signal is out of range if this happens.<br />
<br />
=== Colordepth and resolution ===<br />
Specify the colordepth and resolution(s) you would like to use, like this:<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
''DefaultDepth '''24'''''<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
''Virtual '''1600 1200'''''<br />
''Modes '''"1600x1200" "1280x1024" "1024x768" "800x600" "640x480" "512x384" "400x300" "320x240"'''''<br />
EndSubSection<br />
EndSection<br />
<br />
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.<br />
<br />
=== DRI device permissions ===<br />
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.<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
<br />
=== Chipset driver ===<br />
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''').<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
''# Driver "'''vesa'''"''<br />
''Driver "'''fglrx'''"''<br />
VendorName "ATI Technologies Inc"<br />
BoardName "ATI Radeon Xpress 1200 Series"<br />
BusID "PCI:1:5:0"<br />
EndSection<br />
<br />
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.<br />
<br />
=== Physical display size ===<br />
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.<br />
<br />
Section "Monitor"<br />
...<br />
DisplaySize '''155 95'''<br />
EndSection<br />
<br />
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.<br />
<br />
=== Disable composite ===<br />
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.<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
EndSection<br />
<br />
=== Additional options ===<br />
To be continued, I don't think this is enough to get UI2 completely (either mode) going yet. Feel free to jump in anytime... <br />
<br />
<br />
Things still to sort out amongst others (i.e. what is it, do we need it and what are the settings if any):<br />
<br />
Section "Module"<br />
Load "i2c"<br />
Load "bitmap"<br />
Load "ddc"<br />
Load "freetype"<br />
Load "int10"<br />
Load "vbe"<br />
Load "speedo"<br />
Load "type1"<br />
Load "dbe"<br />
Load "glx"<br />
Load "v4l"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AIGLX" "off"<br />
EndSection<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
# Option "RENDER" "true"<br />
EndSection<br />
<br />
Option "PseudoColorVisuals" "off"<br />
Option "OpenGLOverlay" "off"<br />
Option "VideoOverlay" "off"<br />
Option "DesktopSetup" "clone"<br />
<br />
TV-out options, 2nd display, etc.<br />
<br />
<br />
== Troubleshooting ==<br />
<br />
=== The AVWizard crashes X-windows ===<br />
<br />
Try setting the [[#Chipset_driver]] option to '''vesa''', run the AVWizard again and then change the driver back to what it was.<br />
<br />
=== Black screen ===<br />
<br />
* 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.<br />
<br />
*One problem on nvidia-cards could be that it does not detect the right monitor.<br />
<br />
::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><br />
::where XXX is CRT, CRT-0, CRT-1, DVI-0, DVI-1, ...<br />
::Save and exit (nano: Ctrl+x) and restart the computer. In my case it was "CRT-1".<br />
<br />
=== X-windows won't start ===<br />
<br />
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]-[&larr;Backspace] simultaneous to quit (alternative: use "startx" and get the full desktop, if any), then reboot when it works and you're done.<br />
<br />
=== Signal out of range ===<br />
<br />
See ''[[#Refresh rate / ModeLine ]]'' above.<br />
<br />
=== Microscopic fonts in KDE ===<br />
<br />
See ''[[#Physical_display_size]]'' above.<br />
<br />
If the above does not work, probably Xorg is calculating the DPI value in the wrong way.<br />
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.<br />
<br />
If those values are too small, fonts will be displayed accordingly (i.e, VERY small)<br />
<br />
A workaround is to force Xorg to startup with a given DPI value.<br />
<br />
To achieve this the following steps are required:<br />
<br />
* edit the file /usr/pluto/bin/Start_X_Wrapper.sh on your MD where you are facing the font problem<br />
* find the line beginning with xinit<br />
* add "-dpi 96" (without quotes) at the end of this line<br />
* save the file and reboot MD<br />
<br />
Obviously it is possible to set DPI to something different than 96, according to specific needs.<br />
<br />
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.<br />
<br />
=== LinuxMCE keeps reconfiguring my display settings ===<br />
<br />
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.<br />
<br />
For LinuxMCE 710 simply comment out the line that says<br />
. /usr/pluto/bin/X-CleanupVideo.sh<br />
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.<br />
<br />
== See also ==<br />
* [http://www.mythtv.org/wiki/index.php/Main_Page MythTV wiki] <br />
* MythTV Experience [http://brentlagesse.net/~brent/mythtv.php]<br />
* [[X_Configuration_Scripts]]</div>Unihttp://wiki.linuxmce.org/index.php?title=BFG_GeForce_7600GT_256MB&diff=18618BFG GeForce 7600GT 256MB2009-04-18T17:26:45Z<p>Uni: </p>
<hr />
<div>[[Category: Graphic Cards]] <br />
<br />
This card works fine with UI2 medium settings (masking) and alpha Blending, but is a little tedious to get going on a HDMI interface. Hold down Shift key after you hear the system beeps to make it work.</div>Unihttp://wiki.linuxmce.org/index.php?title=BFG_GeForce_7600GT_256MB&diff=18617BFG GeForce 7600GT 256MB2009-04-18T17:23:57Z<p>Uni: </p>
<hr />
<div>[[Category: Graphic Cards]] <br />
<br />
This card works fine with UI2, but is a little tedious to get going on a HDMI interface.</div>Unihttp://wiki.linuxmce.org/index.php?title=BFG_GeForce_7300_GS&diff=18611BFG GeForce 7300 GS2009-04-17T20:17:32Z<p>Uni: </p>
<hr />
<div>[[Category: Graphic Cards]] <br />
<br />
<br />
This card works out of the box, supports Alpha Blending, DVI, and does not need updated drivers to work.<br />
<br />
<br />
--[[User:Uni|Uni]] 22:17, 17 April 2009 (CEST) It works fine but X crashes sometimes even with the newest driver.</div>Unihttp://wiki.linuxmce.org/index.php?title=BFG_GeForce_7300_GS&diff=18610BFG GeForce 7300 GS2009-04-17T20:17:13Z<p>Uni: </p>
<hr />
<div>[[Category: Graphic Cards]] <br />
<br />
<br />
This card works out of the box, supports Alpha Blending, DVI, and does not need updated drivers to work.<br />
<br />
<br />
--[[User:Uni|Uni]] 22:17, 17 April 2009 (CEST)It works fine but X crashes sometimes even with the newest driver.</div>Unihttp://wiki.linuxmce.org/index.php?title=Display_Drivers&diff=18438Display Drivers2009-04-13T22:15:25Z<p>Uni: /* Installation */</p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
[[Category: Tutorials]]<br />
[[Category: Hardware| ]]<br />
<br />
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.<br />
<br />
'''Note that this should normally not be necessary unless you have specific wishes or trouble getting your display to work properly.''' <br />
<br />
== Installation ==<br />
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. Before you get started on the below, you will want to (from recovery mode) issue this command ''"sudo cat /proc/interrupts"'' and make sure your video card is not sharing an interrupt with another device, such as a NIC (network interface card). If it is, you could run into a lot of issues. Your output should look something like this:<br />
<br />
''19: 38492811 0 IO-APIC-fasteoi eth0 <br><br />
''20: 2 0 IO-APIC-fasteoi ehci_hcd:usb2 <br>''<br />
''21: 10938712 0 IO-APIC-fasteoi nvidia <br>''<br />
''<br />
=== ATI Chipsets ===<br />
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].<br />
<br />
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.<br />
<br />
==== Installing The ATI Driver ====<br />
<br />
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.<br />
<br />
'''Step 1'''<br />
<br />
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'.<br />
<br />
'''Step 2'''<br />
<br />
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;<br />
<br />
sudo su - <return><br />
ssh moonNN <return> (**where the NN is the device number for the MD we're configuring**)<br />
<br />
Alternatively do the following from the MD/Core you are configuring;<br />
<br />
Ctrl+Alt+2<br />
<br />
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;<br />
<br />
Firstly make sure our sources.list is up to date:<br />
<br />
apt-get update <return><br />
<br />
Now lets install the ATI driver and packages;<br />
<br />
apt-get install linux-restricted-modules-generic restricted-manager <return><br />
<br />
Answer 'Y' to installing new packages then do the following steps;<br />
<br />
apt-get install xorg-driver-fglrx <return><br />
depmod -a <return><br />
<br />
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;<br />
<br />
I use the console text editor 'joe' below but you can use whichever you prefer ('nano' is installed by default for example);<br />
<br />
joe /etc/X11/xorg.conf <return><br />
<br />
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;<br />
<br />
Driver "vesa"<br />
or<br />
Driver "ati"<br />
<br />
Change the string 'vesa' (or ati) to 'fglrx' which is the name of the ATI driver. The updated driver line should look like below;<br />
<br />
Driver "fglrx"<br />
<br />
Now save the changes you have made to xorg.conf.<br />
<br />
Now reboot the MD from the console with;<br />
<br />
reboot <return><br />
<br />
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.<br />
<br />
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.<br />
<br />
=== NVidia Chipsets ===<br />
<br />
==== Bugs ====<br />
If you are here, trying to update your driver because video is not working, remember that there is a bug with some Nvidia cards that makes graphical output always appear on the DVI plug, not the VGA plug. If you have a display attached to the VGA port on your adapter, buy a DVI to VGA converter plug before putting yourself through a lot of pain!<br />
<br />
==== Legacy Drivers ====<br />
With legacy drivers the AVWizard might crash because it could not load the nvidia-legacy kernel module. It is unclear why kdm will start and not the AVWizard. A quick fix is to set the '''Driver''' option for the video card in the ''/etc/X11/xorg.conf'' file to '''vesa'''. Go through the AVWizard and then change it back. Another option is to edit ''/etc/modprobe.d/aliases'' and add '''alias nvidia nvidia-legacy'''. Don't forget about this line when you switch to a newer card.<br />
<br />
==== Latest Drivers ====<br />
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. <br />
<br />
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. <br />
'''<you>@dcerouter:~$''' sudo -s<br />
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:<br />
'''root@dcerouter:~#''' wget <nowiki>http://us.download.nvidia.com/XFree86/Linux-x86/</nowiki>''<version>''<nowiki>/NVIDIA-Linux-x86-</nowiki>''<version>''<nowiki>-pkg1.run</nowiki><br />
3. Go to runlevel 1 to stop the currently running X-server. <br />
'''root@dcerouter:~#''' telinit 1 <br />
4. Execute the installer and follow instructions. a) Ignore the warning about runlevel 1 and b) don't bother looking for "precompiled kernel interfaces" (drivers).<br />
'''root@dcerouter:~#''' sh NVIDIA-Linux-x86-''<version>''-pkg1.run<br />
5. The installer will attempt to remove old legacy drivers. If it cannot, you may receive X errors (Eg. ''Error: API mismatch''). The solution is to manually remove or disable the legacy drivers. <br />
'''nano /etc/default/linux-restricted-modules-common''' <br />
Disable the NVIDIA linux-restricted kernel modules (nvidia, nvidia_legacy) by changing the DISABLED_MODULES line to read:<br />
'''DISABLED_MODULES="nv nvidia_new"'''<br />
6. 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.<br />
<br />
''** Update - Do a "sudo cat /proc/driver/nvidia/version" and make sure it reads something similar to this, matching the newest drivers you just installed: NVIDIA UNIX x86 Kernel Module 180.29. The "nvclock" utility is useful for monitoring GPU overheating''<br />
<br />
==== Media Directors ====<br />
Instructions for installing the latest nVidia driver on your media directors can be found in the [[Upgrading the Kernel#Video Drivers|upgrading the kernel]] wiki.<br />
<br />
=== Intel Chipsets ===<br />
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.<br />
<br />
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.<br />
<br />
==== For LinuxMCE-0704 ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
From man i810:<br />
Option "LinearAlloc" "integer"<br />
Allows more memory for the offscreen allocator. This usually<br />
helps in situations where HDTV movies are required to play but<br />
not enough offscreen memory is usually available. Set this to<br />
8160 for upto 1920x1080 HDTV support. Default 0KB (off).<br />
<br />
==== potential problem ====<br />
<br />
there can be a problem with some intel drivers, like the gma 3100. see [[bug/gma3100driver]] for further informations<br />
<br />
=== Via Chipsets ===<br />
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]<br />
<br />
The proprietary Via Unichrome driver works best with Linux MCE. Unfortunately this driver has intentionally been stripped of support for most GLX extensions. This driver does not support alpha blending which is a prerequisite of [[UI2]]. Via licenses the full featured driver to system integrators, such as [[Fiire]]. This licensed driver is not publicly available. Additionally there is a known incompatibility issue with the licensed driver and Linux MCE 0710. <br />
<br />
On April 08, 2008 Via announced a new open source initiative to help develop open drivers for certain video chipsets [http://www.phoronix.com/scan.php?page=article&item=via_oss&num=1]. This press release echos sour notes with many developers who have heard this tune many times before. No useful information or code has been released to date, striking yet another all to familiar chord in the open source community [http://www.phoronix.com/scan.php?page=article&item=via_bluff&num=1].<br />
<br />
'''HOW-TO VIA Openchrome driver for xorg:'''<br><br />
For VIA CX700M2 UniChrome PRO II Graphics (1" VIA units) or mainly via graphics:<br><br />
<br />
''shell into your box and do the following:''<br><br />
apt-get -y 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 subversion xserver-xorg-dev libdrm-dev libxvmc-dev<br />
<br />
cd /usr/src<br />
svn checkout http://svn.openchrome.org/svn/trunk openchrome<br />
cd openchrome*<br />
./autogen.sh --prefix=/usr<br />
make<br />
make install<br />
<br />
Now we have to edit /etc/X11/xorg.conf and change the device driver to via openchrome:<br><br />
vi /etc/X11/xorg.conf<br />
Go to<br />
Section "Device"<br />
and change<br />
Driver "vesa" <br />
to<br />
Driver "openchrome"<br />
save and test the compiled new driver with a: <br><br />
X :1<br />
and if your xwindow comes up, you can reboot and have fun<br><br />
<br />
=== Other Chipsets ===<br />
Please help out by adding more if you can.<br />
<br />
== Configuration ==<br />
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.<br />
<br />
=== Getting started ===<br />
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. <br />
<br />
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:<br />
telinit 1<br />
This wil stop the running X-server and drop you into rescue mode as well. <br />
<br />
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.<br />
<br />
=== Generating a template ===<br />
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. <br />
<br />
'''While there is no (other) X-server running''' you can create a template configuration file by running:<br />
X -configure<br />
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:<br />
X -config ~/xorg.conf.new<br />
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). <br />
<br />
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.<br />
<br />
Here is an example of such a generated file:<br />
<br />
Section "ServerLayout"<br />
Identifier "X.org Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Mouse0" "CorePointer"<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/etc/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/X11/misc"<br />
FontPath "/usr/X11R6/lib/X11/fonts/misc"<br />
FontPath "/usr/share/fonts/X11/cyrillic"<br />
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/Type1"<br />
FontPath "/usr/X11R6/lib/X11/fonts/Type1"<br />
FontPath "/usr/share/fonts/X11/100dpi"<br />
FontPath "/usr/share/fonts/X11/75dpi"<br />
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "extmod"<br />
Load "record"<br />
Load "xtrap"<br />
Load "dri"<br />
Load "glx"<br />
Load "dbe"<br />
Load "GLcore"<br />
Load "type1"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Keyboard0"<br />
Driver "kbd"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Mouse0"<br />
Driver "mouse"<br />
Option "Protocol" "auto"<br />
Option "Device" "/dev/input/mice"<br />
Option "ZAxisMapping" "4 5 6 7"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
EndSection<br />
<br />
Section "Device"<br />
### Available Driver options are:-<br />
### Values: &lt;i&gt;: integer, <f>: float, <bool>: "True"/"False",<br />
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"<br />
### [arg]: arg optional<br />
#Option "ShadowFB" # [<bool>]<br />
#Option "DefaultRefresh" # [<bool>]<br />
#Option "ModeSetClearScreen" # [<bool>]<br />
Identifier "Card0"<br />
Driver "vesa"<br />
''VendorName "ATI Technologies Inc"''<br />
''BoardName "ATI Radeon Xpress 1200 Series"''<br />
''BusID '''"PCI:1:5:0"'''''<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 1<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 4<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 8<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 15<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 16<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
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:<br />
X -scanpci<br />
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.<br />
<br />
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.<br />
<br />
=== Refresh rate / ModeLine ===<br />
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:<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
''HorizSync '''27-102''' # kHz''<br />
''VertRefresh '''50-160''' # Hz''<br />
EndSection<br />
<br />
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. <br />
<br />
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. <br />
* http://koala.ilog.fr/cgi-bin/nph-colas-modelines<br />
* http://xtiming.sourceforge.net/cgi-bin/xtiming.pl<br />
* http://www.bohne-lang.de/spec/linux/modeline/<br />
* http://amlc.berlios.de/<br />
* http://www.mythtv.org/wiki/index.php/Working_with_Modelines<br />
If one modeline doesn't work perfectly, try another, perhaps from another generator, because they can vary so much.<br />
<br />
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]-[&larr;Backspace] and readjust your settings. Most modern screens however simply report that the signal is out of range if this happens.<br />
<br />
=== Colordepth and resolution ===<br />
Specify the colordepth and resolution(s) you would like to use, like this:<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
''DefaultDepth '''24'''''<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
''Virtual '''1600 1200'''''<br />
''Modes '''"1600x1200" "1280x1024" "1024x768" "800x600" "640x480" "512x384" "400x300" "320x240"'''''<br />
EndSubSection<br />
EndSection<br />
<br />
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.<br />
<br />
=== DRI device permissions ===<br />
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.<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
<br />
=== Chipset driver ===<br />
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''').<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
''# Driver "'''vesa'''"''<br />
''Driver "'''fglrx'''"''<br />
VendorName "ATI Technologies Inc"<br />
BoardName "ATI Radeon Xpress 1200 Series"<br />
BusID "PCI:1:5:0"<br />
EndSection<br />
<br />
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.<br />
<br />
=== Physical display size ===<br />
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.<br />
<br />
Section "Monitor"<br />
...<br />
DisplaySize '''155 95'''<br />
EndSection<br />
<br />
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.<br />
<br />
=== Disable composite ===<br />
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.<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
EndSection<br />
<br />
=== Additional options ===<br />
To be continued, I don't think this is enough to get UI2 completely (either mode) going yet. Feel free to jump in anytime... <br />
<br />
<br />
Things still to sort out amongst others (i.e. what is it, do we need it and what are the settings if any):<br />
<br />
Section "Module"<br />
Load "i2c"<br />
Load "bitmap"<br />
Load "ddc"<br />
Load "freetype"<br />
Load "int10"<br />
Load "vbe"<br />
Load "speedo"<br />
Load "type1"<br />
Load "dbe"<br />
Load "glx"<br />
Load "v4l"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AIGLX" "off"<br />
EndSection<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
# Option "RENDER" "true"<br />
EndSection<br />
<br />
Option "PseudoColorVisuals" "off"<br />
Option "OpenGLOverlay" "off"<br />
Option "VideoOverlay" "off"<br />
Option "DesktopSetup" "clone"<br />
<br />
TV-out options, 2nd display, etc.<br />
<br />
<br />
== Troubleshooting ==<br />
<br />
=== The AVWizard crashes X-windows ===<br />
<br />
Try setting the [[#Chipset_driver]] option to '''vesa''', run the AVWizard again and then change the driver back to what it was.<br />
<br />
=== Black screen ===<br />
<br />
* 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.<br />
<br />
*One problem on nvidia-cards could be that it does not detect the right monitor.<br />
<br />
::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><br />
::where XXX is CRT, CRT-0, CRT-1, DVI-0, DVI-1, ...<br />
::Save and exit (nano: Ctrl+x) and restart the computer. In my case it was "CRT-1".<br />
<br />
=== X-windows won't start ===<br />
<br />
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]-[&larr;Backspace] simultaneous to quit (alternative: use "startx" and get the full desktop, if any), then reboot when it works and you're done.<br />
<br />
=== Signal out of range ===<br />
<br />
See ''[[#Refresh rate / ModeLine ]]'' above.<br />
<br />
=== Microscopic fonts in KDE ===<br />
<br />
See ''[[#Physical_display_size]]'' above.<br />
<br />
If the above does not work, probably Xorg is calculating the DPI value in the wrong way.<br />
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.<br />
<br />
If those values are too small, fonts will be displayed accordingly (i.e, VERY small)<br />
<br />
A workaround is to force Xorg to startup with a given DPI value.<br />
<br />
To achieve this the following steps are required:<br />
<br />
* edit the file /usr/pluto/bin/Start_X_Wrapper.sh on your MD where you are facing the font problem<br />
* find the line beginning with xinit<br />
* add "-dpi 96" (without quotes) at the end of this line<br />
* save the file and reboot MD<br />
<br />
Obviously it is possible to set DPI to something different than 96, according to specific needs.<br />
<br />
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.<br />
<br />
=== LinuxMCE keeps reconfiguring my display settings ===<br />
<br />
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.<br />
<br />
For LinuxMCE 710 simply comment out the line that says<br />
. /usr/pluto/bin/X-CleanupVideo.sh<br />
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.<br />
<br />
== See also ==<br />
* [http://www.mythtv.org/wiki/index.php/Main_Page MythTV wiki] <br />
* MythTV Experience [http://brentlagesse.net/~brent/mythtv.php]<br />
* [[X_Configuration_Scripts]]</div>Unihttp://wiki.linuxmce.org/index.php?title=Display_Drivers&diff=18437Display Drivers2009-04-13T22:15:06Z<p>Uni: /* Installation */</p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
[[Category: Tutorials]]<br />
[[Category: Hardware| ]]<br />
<br />
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.<br />
<br />
'''Note that this should normally not be necessary unless you have specific wishes or trouble getting your display to work properly.''' <br />
<br />
== Installation ==<br />
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. Before you get started on the below, you will want to (from recovery mode) issue this command ''"sudo cat /proc/interrupts"'' and make sure your video card is not sharing an interrupt with another device, such as a NIC (network interface card). If it is, you could run into a lot of issues. Your output should look something like this:<br />
<br />
''19: 38492811 0 IO-APIC-fasteoi eth0 <br><br />
20: 2 0 IO-APIC-fasteoi ehci_hcd:usb2 <br><br />
21: 10938712 0 IO-APIC-fasteoi nvidia <br><br />
''<br />
=== ATI Chipsets ===<br />
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].<br />
<br />
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.<br />
<br />
==== Installing The ATI Driver ====<br />
<br />
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.<br />
<br />
'''Step 1'''<br />
<br />
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'.<br />
<br />
'''Step 2'''<br />
<br />
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;<br />
<br />
sudo su - <return><br />
ssh moonNN <return> (**where the NN is the device number for the MD we're configuring**)<br />
<br />
Alternatively do the following from the MD/Core you are configuring;<br />
<br />
Ctrl+Alt+2<br />
<br />
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;<br />
<br />
Firstly make sure our sources.list is up to date:<br />
<br />
apt-get update <return><br />
<br />
Now lets install the ATI driver and packages;<br />
<br />
apt-get install linux-restricted-modules-generic restricted-manager <return><br />
<br />
Answer 'Y' to installing new packages then do the following steps;<br />
<br />
apt-get install xorg-driver-fglrx <return><br />
depmod -a <return><br />
<br />
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;<br />
<br />
I use the console text editor 'joe' below but you can use whichever you prefer ('nano' is installed by default for example);<br />
<br />
joe /etc/X11/xorg.conf <return><br />
<br />
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;<br />
<br />
Driver "vesa"<br />
or<br />
Driver "ati"<br />
<br />
Change the string 'vesa' (or ati) to 'fglrx' which is the name of the ATI driver. The updated driver line should look like below;<br />
<br />
Driver "fglrx"<br />
<br />
Now save the changes you have made to xorg.conf.<br />
<br />
Now reboot the MD from the console with;<br />
<br />
reboot <return><br />
<br />
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.<br />
<br />
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.<br />
<br />
=== NVidia Chipsets ===<br />
<br />
==== Bugs ====<br />
If you are here, trying to update your driver because video is not working, remember that there is a bug with some Nvidia cards that makes graphical output always appear on the DVI plug, not the VGA plug. If you have a display attached to the VGA port on your adapter, buy a DVI to VGA converter plug before putting yourself through a lot of pain!<br />
<br />
==== Legacy Drivers ====<br />
With legacy drivers the AVWizard might crash because it could not load the nvidia-legacy kernel module. It is unclear why kdm will start and not the AVWizard. A quick fix is to set the '''Driver''' option for the video card in the ''/etc/X11/xorg.conf'' file to '''vesa'''. Go through the AVWizard and then change it back. Another option is to edit ''/etc/modprobe.d/aliases'' and add '''alias nvidia nvidia-legacy'''. Don't forget about this line when you switch to a newer card.<br />
<br />
==== Latest Drivers ====<br />
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. <br />
<br />
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. <br />
'''<you>@dcerouter:~$''' sudo -s<br />
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:<br />
'''root@dcerouter:~#''' wget <nowiki>http://us.download.nvidia.com/XFree86/Linux-x86/</nowiki>''<version>''<nowiki>/NVIDIA-Linux-x86-</nowiki>''<version>''<nowiki>-pkg1.run</nowiki><br />
3. Go to runlevel 1 to stop the currently running X-server. <br />
'''root@dcerouter:~#''' telinit 1 <br />
4. Execute the installer and follow instructions. a) Ignore the warning about runlevel 1 and b) don't bother looking for "precompiled kernel interfaces" (drivers).<br />
'''root@dcerouter:~#''' sh NVIDIA-Linux-x86-''<version>''-pkg1.run<br />
5. The installer will attempt to remove old legacy drivers. If it cannot, you may receive X errors (Eg. ''Error: API mismatch''). The solution is to manually remove or disable the legacy drivers. <br />
'''nano /etc/default/linux-restricted-modules-common''' <br />
Disable the NVIDIA linux-restricted kernel modules (nvidia, nvidia_legacy) by changing the DISABLED_MODULES line to read:<br />
'''DISABLED_MODULES="nv nvidia_new"'''<br />
6. 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.<br />
<br />
''** Update - Do a "sudo cat /proc/driver/nvidia/version" and make sure it reads something similar to this, matching the newest drivers you just installed: NVIDIA UNIX x86 Kernel Module 180.29. The "nvclock" utility is useful for monitoring GPU overheating''<br />
<br />
==== Media Directors ====<br />
Instructions for installing the latest nVidia driver on your media directors can be found in the [[Upgrading the Kernel#Video Drivers|upgrading the kernel]] wiki.<br />
<br />
=== Intel Chipsets ===<br />
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.<br />
<br />
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.<br />
<br />
==== For LinuxMCE-0704 ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
From man i810:<br />
Option "LinearAlloc" "integer"<br />
Allows more memory for the offscreen allocator. This usually<br />
helps in situations where HDTV movies are required to play but<br />
not enough offscreen memory is usually available. Set this to<br />
8160 for upto 1920x1080 HDTV support. Default 0KB (off).<br />
<br />
==== potential problem ====<br />
<br />
there can be a problem with some intel drivers, like the gma 3100. see [[bug/gma3100driver]] for further informations<br />
<br />
=== Via Chipsets ===<br />
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]<br />
<br />
The proprietary Via Unichrome driver works best with Linux MCE. Unfortunately this driver has intentionally been stripped of support for most GLX extensions. This driver does not support alpha blending which is a prerequisite of [[UI2]]. Via licenses the full featured driver to system integrators, such as [[Fiire]]. This licensed driver is not publicly available. Additionally there is a known incompatibility issue with the licensed driver and Linux MCE 0710. <br />
<br />
On April 08, 2008 Via announced a new open source initiative to help develop open drivers for certain video chipsets [http://www.phoronix.com/scan.php?page=article&item=via_oss&num=1]. This press release echos sour notes with many developers who have heard this tune many times before. No useful information or code has been released to date, striking yet another all to familiar chord in the open source community [http://www.phoronix.com/scan.php?page=article&item=via_bluff&num=1].<br />
<br />
'''HOW-TO VIA Openchrome driver for xorg:'''<br><br />
For VIA CX700M2 UniChrome PRO II Graphics (1" VIA units) or mainly via graphics:<br><br />
<br />
''shell into your box and do the following:''<br><br />
apt-get -y 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 subversion xserver-xorg-dev libdrm-dev libxvmc-dev<br />
<br />
cd /usr/src<br />
svn checkout http://svn.openchrome.org/svn/trunk openchrome<br />
cd openchrome*<br />
./autogen.sh --prefix=/usr<br />
make<br />
make install<br />
<br />
Now we have to edit /etc/X11/xorg.conf and change the device driver to via openchrome:<br><br />
vi /etc/X11/xorg.conf<br />
Go to<br />
Section "Device"<br />
and change<br />
Driver "vesa" <br />
to<br />
Driver "openchrome"<br />
save and test the compiled new driver with a: <br><br />
X :1<br />
and if your xwindow comes up, you can reboot and have fun<br><br />
<br />
=== Other Chipsets ===<br />
Please help out by adding more if you can.<br />
<br />
== Configuration ==<br />
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.<br />
<br />
=== Getting started ===<br />
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. <br />
<br />
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:<br />
telinit 1<br />
This wil stop the running X-server and drop you into rescue mode as well. <br />
<br />
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.<br />
<br />
=== Generating a template ===<br />
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. <br />
<br />
'''While there is no (other) X-server running''' you can create a template configuration file by running:<br />
X -configure<br />
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:<br />
X -config ~/xorg.conf.new<br />
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). <br />
<br />
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.<br />
<br />
Here is an example of such a generated file:<br />
<br />
Section "ServerLayout"<br />
Identifier "X.org Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Mouse0" "CorePointer"<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/etc/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/X11/misc"<br />
FontPath "/usr/X11R6/lib/X11/fonts/misc"<br />
FontPath "/usr/share/fonts/X11/cyrillic"<br />
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/Type1"<br />
FontPath "/usr/X11R6/lib/X11/fonts/Type1"<br />
FontPath "/usr/share/fonts/X11/100dpi"<br />
FontPath "/usr/share/fonts/X11/75dpi"<br />
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "extmod"<br />
Load "record"<br />
Load "xtrap"<br />
Load "dri"<br />
Load "glx"<br />
Load "dbe"<br />
Load "GLcore"<br />
Load "type1"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Keyboard0"<br />
Driver "kbd"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Mouse0"<br />
Driver "mouse"<br />
Option "Protocol" "auto"<br />
Option "Device" "/dev/input/mice"<br />
Option "ZAxisMapping" "4 5 6 7"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
EndSection<br />
<br />
Section "Device"<br />
### Available Driver options are:-<br />
### Values: &lt;i&gt;: integer, <f>: float, <bool>: "True"/"False",<br />
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"<br />
### [arg]: arg optional<br />
#Option "ShadowFB" # [<bool>]<br />
#Option "DefaultRefresh" # [<bool>]<br />
#Option "ModeSetClearScreen" # [<bool>]<br />
Identifier "Card0"<br />
Driver "vesa"<br />
''VendorName "ATI Technologies Inc"''<br />
''BoardName "ATI Radeon Xpress 1200 Series"''<br />
''BusID '''"PCI:1:5:0"'''''<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 1<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 4<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 8<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 15<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 16<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
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:<br />
X -scanpci<br />
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.<br />
<br />
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.<br />
<br />
=== Refresh rate / ModeLine ===<br />
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:<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
''HorizSync '''27-102''' # kHz''<br />
''VertRefresh '''50-160''' # Hz''<br />
EndSection<br />
<br />
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. <br />
<br />
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. <br />
* http://koala.ilog.fr/cgi-bin/nph-colas-modelines<br />
* http://xtiming.sourceforge.net/cgi-bin/xtiming.pl<br />
* http://www.bohne-lang.de/spec/linux/modeline/<br />
* http://amlc.berlios.de/<br />
* http://www.mythtv.org/wiki/index.php/Working_with_Modelines<br />
If one modeline doesn't work perfectly, try another, perhaps from another generator, because they can vary so much.<br />
<br />
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]-[&larr;Backspace] and readjust your settings. Most modern screens however simply report that the signal is out of range if this happens.<br />
<br />
=== Colordepth and resolution ===<br />
Specify the colordepth and resolution(s) you would like to use, like this:<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
''DefaultDepth '''24'''''<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
''Virtual '''1600 1200'''''<br />
''Modes '''"1600x1200" "1280x1024" "1024x768" "800x600" "640x480" "512x384" "400x300" "320x240"'''''<br />
EndSubSection<br />
EndSection<br />
<br />
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.<br />
<br />
=== DRI device permissions ===<br />
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.<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
<br />
=== Chipset driver ===<br />
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''').<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
''# Driver "'''vesa'''"''<br />
''Driver "'''fglrx'''"''<br />
VendorName "ATI Technologies Inc"<br />
BoardName "ATI Radeon Xpress 1200 Series"<br />
BusID "PCI:1:5:0"<br />
EndSection<br />
<br />
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.<br />
<br />
=== Physical display size ===<br />
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.<br />
<br />
Section "Monitor"<br />
...<br />
DisplaySize '''155 95'''<br />
EndSection<br />
<br />
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.<br />
<br />
=== Disable composite ===<br />
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.<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
EndSection<br />
<br />
=== Additional options ===<br />
To be continued, I don't think this is enough to get UI2 completely (either mode) going yet. Feel free to jump in anytime... <br />
<br />
<br />
Things still to sort out amongst others (i.e. what is it, do we need it and what are the settings if any):<br />
<br />
Section "Module"<br />
Load "i2c"<br />
Load "bitmap"<br />
Load "ddc"<br />
Load "freetype"<br />
Load "int10"<br />
Load "vbe"<br />
Load "speedo"<br />
Load "type1"<br />
Load "dbe"<br />
Load "glx"<br />
Load "v4l"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AIGLX" "off"<br />
EndSection<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
# Option "RENDER" "true"<br />
EndSection<br />
<br />
Option "PseudoColorVisuals" "off"<br />
Option "OpenGLOverlay" "off"<br />
Option "VideoOverlay" "off"<br />
Option "DesktopSetup" "clone"<br />
<br />
TV-out options, 2nd display, etc.<br />
<br />
<br />
== Troubleshooting ==<br />
<br />
=== The AVWizard crashes X-windows ===<br />
<br />
Try setting the [[#Chipset_driver]] option to '''vesa''', run the AVWizard again and then change the driver back to what it was.<br />
<br />
=== Black screen ===<br />
<br />
* 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.<br />
<br />
*One problem on nvidia-cards could be that it does not detect the right monitor.<br />
<br />
::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><br />
::where XXX is CRT, CRT-0, CRT-1, DVI-0, DVI-1, ...<br />
::Save and exit (nano: Ctrl+x) and restart the computer. In my case it was "CRT-1".<br />
<br />
=== X-windows won't start ===<br />
<br />
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]-[&larr;Backspace] simultaneous to quit (alternative: use "startx" and get the full desktop, if any), then reboot when it works and you're done.<br />
<br />
=== Signal out of range ===<br />
<br />
See ''[[#Refresh rate / ModeLine ]]'' above.<br />
<br />
=== Microscopic fonts in KDE ===<br />
<br />
See ''[[#Physical_display_size]]'' above.<br />
<br />
If the above does not work, probably Xorg is calculating the DPI value in the wrong way.<br />
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.<br />
<br />
If those values are too small, fonts will be displayed accordingly (i.e, VERY small)<br />
<br />
A workaround is to force Xorg to startup with a given DPI value.<br />
<br />
To achieve this the following steps are required:<br />
<br />
* edit the file /usr/pluto/bin/Start_X_Wrapper.sh on your MD where you are facing the font problem<br />
* find the line beginning with xinit<br />
* add "-dpi 96" (without quotes) at the end of this line<br />
* save the file and reboot MD<br />
<br />
Obviously it is possible to set DPI to something different than 96, according to specific needs.<br />
<br />
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.<br />
<br />
=== LinuxMCE keeps reconfiguring my display settings ===<br />
<br />
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.<br />
<br />
For LinuxMCE 710 simply comment out the line that says<br />
. /usr/pluto/bin/X-CleanupVideo.sh<br />
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.<br />
<br />
== See also ==<br />
* [http://www.mythtv.org/wiki/index.php/Main_Page MythTV wiki] <br />
* MythTV Experience [http://brentlagesse.net/~brent/mythtv.php]<br />
* [[X_Configuration_Scripts]]</div>Unihttp://wiki.linuxmce.org/index.php?title=Display_Drivers&diff=18436Display Drivers2009-04-13T22:14:40Z<p>Uni: /* Installation */</p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
[[Category: Tutorials]]<br />
[[Category: Hardware| ]]<br />
<br />
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.<br />
<br />
'''Note that this should normally not be necessary unless you have specific wishes or trouble getting your display to work properly.''' <br />
<br />
== Installation ==<br />
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. Before you get started on the below, you will want to (from recovery mode) issue this command ''"sudo cat /proc/interrupts"'' and make sure your video card is not sharing an interrupt with another device, such as a NIC (network interface card). If it is, you could run into a lot of issues. Your output should look something like this:<br />
<br />
19: 38492811 0 IO-APIC-fasteoi eth0 <br><br />
20: 2 0 IO-APIC-fasteoi ehci_hcd:usb2 <br><br />
21: 10938712 0 IO-APIC-fasteoi nvidia <br><br />
<br />
=== ATI Chipsets ===<br />
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].<br />
<br />
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.<br />
<br />
==== Installing The ATI Driver ====<br />
<br />
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.<br />
<br />
'''Step 1'''<br />
<br />
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'.<br />
<br />
'''Step 2'''<br />
<br />
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;<br />
<br />
sudo su - <return><br />
ssh moonNN <return> (**where the NN is the device number for the MD we're configuring**)<br />
<br />
Alternatively do the following from the MD/Core you are configuring;<br />
<br />
Ctrl+Alt+2<br />
<br />
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;<br />
<br />
Firstly make sure our sources.list is up to date:<br />
<br />
apt-get update <return><br />
<br />
Now lets install the ATI driver and packages;<br />
<br />
apt-get install linux-restricted-modules-generic restricted-manager <return><br />
<br />
Answer 'Y' to installing new packages then do the following steps;<br />
<br />
apt-get install xorg-driver-fglrx <return><br />
depmod -a <return><br />
<br />
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;<br />
<br />
I use the console text editor 'joe' below but you can use whichever you prefer ('nano' is installed by default for example);<br />
<br />
joe /etc/X11/xorg.conf <return><br />
<br />
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;<br />
<br />
Driver "vesa"<br />
or<br />
Driver "ati"<br />
<br />
Change the string 'vesa' (or ati) to 'fglrx' which is the name of the ATI driver. The updated driver line should look like below;<br />
<br />
Driver "fglrx"<br />
<br />
Now save the changes you have made to xorg.conf.<br />
<br />
Now reboot the MD from the console with;<br />
<br />
reboot <return><br />
<br />
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.<br />
<br />
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.<br />
<br />
=== NVidia Chipsets ===<br />
<br />
==== Bugs ====<br />
If you are here, trying to update your driver because video is not working, remember that there is a bug with some Nvidia cards that makes graphical output always appear on the DVI plug, not the VGA plug. If you have a display attached to the VGA port on your adapter, buy a DVI to VGA converter plug before putting yourself through a lot of pain!<br />
<br />
==== Legacy Drivers ====<br />
With legacy drivers the AVWizard might crash because it could not load the nvidia-legacy kernel module. It is unclear why kdm will start and not the AVWizard. A quick fix is to set the '''Driver''' option for the video card in the ''/etc/X11/xorg.conf'' file to '''vesa'''. Go through the AVWizard and then change it back. Another option is to edit ''/etc/modprobe.d/aliases'' and add '''alias nvidia nvidia-legacy'''. Don't forget about this line when you switch to a newer card.<br />
<br />
==== Latest Drivers ====<br />
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. <br />
<br />
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. <br />
'''<you>@dcerouter:~$''' sudo -s<br />
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:<br />
'''root@dcerouter:~#''' wget <nowiki>http://us.download.nvidia.com/XFree86/Linux-x86/</nowiki>''<version>''<nowiki>/NVIDIA-Linux-x86-</nowiki>''<version>''<nowiki>-pkg1.run</nowiki><br />
3. Go to runlevel 1 to stop the currently running X-server. <br />
'''root@dcerouter:~#''' telinit 1 <br />
4. Execute the installer and follow instructions. a) Ignore the warning about runlevel 1 and b) don't bother looking for "precompiled kernel interfaces" (drivers).<br />
'''root@dcerouter:~#''' sh NVIDIA-Linux-x86-''<version>''-pkg1.run<br />
5. The installer will attempt to remove old legacy drivers. If it cannot, you may receive X errors (Eg. ''Error: API mismatch''). The solution is to manually remove or disable the legacy drivers. <br />
'''nano /etc/default/linux-restricted-modules-common''' <br />
Disable the NVIDIA linux-restricted kernel modules (nvidia, nvidia_legacy) by changing the DISABLED_MODULES line to read:<br />
'''DISABLED_MODULES="nv nvidia_new"'''<br />
6. 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.<br />
<br />
''** Update - Do a "sudo cat /proc/driver/nvidia/version" and make sure it reads something similar to this, matching the newest drivers you just installed: NVIDIA UNIX x86 Kernel Module 180.29. The "nvclock" utility is useful for monitoring GPU overheating''<br />
<br />
==== Media Directors ====<br />
Instructions for installing the latest nVidia driver on your media directors can be found in the [[Upgrading the Kernel#Video Drivers|upgrading the kernel]] wiki.<br />
<br />
=== Intel Chipsets ===<br />
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.<br />
<br />
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.<br />
<br />
==== For LinuxMCE-0704 ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
From man i810:<br />
Option "LinearAlloc" "integer"<br />
Allows more memory for the offscreen allocator. This usually<br />
helps in situations where HDTV movies are required to play but<br />
not enough offscreen memory is usually available. Set this to<br />
8160 for upto 1920x1080 HDTV support. Default 0KB (off).<br />
<br />
==== potential problem ====<br />
<br />
there can be a problem with some intel drivers, like the gma 3100. see [[bug/gma3100driver]] for further informations<br />
<br />
=== Via Chipsets ===<br />
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]<br />
<br />
The proprietary Via Unichrome driver works best with Linux MCE. Unfortunately this driver has intentionally been stripped of support for most GLX extensions. This driver does not support alpha blending which is a prerequisite of [[UI2]]. Via licenses the full featured driver to system integrators, such as [[Fiire]]. This licensed driver is not publicly available. Additionally there is a known incompatibility issue with the licensed driver and Linux MCE 0710. <br />
<br />
On April 08, 2008 Via announced a new open source initiative to help develop open drivers for certain video chipsets [http://www.phoronix.com/scan.php?page=article&item=via_oss&num=1]. This press release echos sour notes with many developers who have heard this tune many times before. No useful information or code has been released to date, striking yet another all to familiar chord in the open source community [http://www.phoronix.com/scan.php?page=article&item=via_bluff&num=1].<br />
<br />
'''HOW-TO VIA Openchrome driver for xorg:'''<br><br />
For VIA CX700M2 UniChrome PRO II Graphics (1" VIA units) or mainly via graphics:<br><br />
<br />
''shell into your box and do the following:''<br><br />
apt-get -y 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 subversion xserver-xorg-dev libdrm-dev libxvmc-dev<br />
<br />
cd /usr/src<br />
svn checkout http://svn.openchrome.org/svn/trunk openchrome<br />
cd openchrome*<br />
./autogen.sh --prefix=/usr<br />
make<br />
make install<br />
<br />
Now we have to edit /etc/X11/xorg.conf and change the device driver to via openchrome:<br><br />
vi /etc/X11/xorg.conf<br />
Go to<br />
Section "Device"<br />
and change<br />
Driver "vesa" <br />
to<br />
Driver "openchrome"<br />
save and test the compiled new driver with a: <br><br />
X :1<br />
and if your xwindow comes up, you can reboot and have fun<br><br />
<br />
=== Other Chipsets ===<br />
Please help out by adding more if you can.<br />
<br />
== Configuration ==<br />
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.<br />
<br />
=== Getting started ===<br />
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. <br />
<br />
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:<br />
telinit 1<br />
This wil stop the running X-server and drop you into rescue mode as well. <br />
<br />
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.<br />
<br />
=== Generating a template ===<br />
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. <br />
<br />
'''While there is no (other) X-server running''' you can create a template configuration file by running:<br />
X -configure<br />
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:<br />
X -config ~/xorg.conf.new<br />
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). <br />
<br />
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.<br />
<br />
Here is an example of such a generated file:<br />
<br />
Section "ServerLayout"<br />
Identifier "X.org Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Mouse0" "CorePointer"<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/etc/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/X11/misc"<br />
FontPath "/usr/X11R6/lib/X11/fonts/misc"<br />
FontPath "/usr/share/fonts/X11/cyrillic"<br />
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/Type1"<br />
FontPath "/usr/X11R6/lib/X11/fonts/Type1"<br />
FontPath "/usr/share/fonts/X11/100dpi"<br />
FontPath "/usr/share/fonts/X11/75dpi"<br />
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "extmod"<br />
Load "record"<br />
Load "xtrap"<br />
Load "dri"<br />
Load "glx"<br />
Load "dbe"<br />
Load "GLcore"<br />
Load "type1"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Keyboard0"<br />
Driver "kbd"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Mouse0"<br />
Driver "mouse"<br />
Option "Protocol" "auto"<br />
Option "Device" "/dev/input/mice"<br />
Option "ZAxisMapping" "4 5 6 7"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
EndSection<br />
<br />
Section "Device"<br />
### Available Driver options are:-<br />
### Values: &lt;i&gt;: integer, <f>: float, <bool>: "True"/"False",<br />
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"<br />
### [arg]: arg optional<br />
#Option "ShadowFB" # [<bool>]<br />
#Option "DefaultRefresh" # [<bool>]<br />
#Option "ModeSetClearScreen" # [<bool>]<br />
Identifier "Card0"<br />
Driver "vesa"<br />
''VendorName "ATI Technologies Inc"''<br />
''BoardName "ATI Radeon Xpress 1200 Series"''<br />
''BusID '''"PCI:1:5:0"'''''<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 1<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 4<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 8<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 15<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 16<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
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:<br />
X -scanpci<br />
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.<br />
<br />
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.<br />
<br />
=== Refresh rate / ModeLine ===<br />
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:<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
''HorizSync '''27-102''' # kHz''<br />
''VertRefresh '''50-160''' # Hz''<br />
EndSection<br />
<br />
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. <br />
<br />
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. <br />
* http://koala.ilog.fr/cgi-bin/nph-colas-modelines<br />
* http://xtiming.sourceforge.net/cgi-bin/xtiming.pl<br />
* http://www.bohne-lang.de/spec/linux/modeline/<br />
* http://amlc.berlios.de/<br />
* http://www.mythtv.org/wiki/index.php/Working_with_Modelines<br />
If one modeline doesn't work perfectly, try another, perhaps from another generator, because they can vary so much.<br />
<br />
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]-[&larr;Backspace] and readjust your settings. Most modern screens however simply report that the signal is out of range if this happens.<br />
<br />
=== Colordepth and resolution ===<br />
Specify the colordepth and resolution(s) you would like to use, like this:<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
''DefaultDepth '''24'''''<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
''Virtual '''1600 1200'''''<br />
''Modes '''"1600x1200" "1280x1024" "1024x768" "800x600" "640x480" "512x384" "400x300" "320x240"'''''<br />
EndSubSection<br />
EndSection<br />
<br />
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.<br />
<br />
=== DRI device permissions ===<br />
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.<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
<br />
=== Chipset driver ===<br />
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''').<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
''# Driver "'''vesa'''"''<br />
''Driver "'''fglrx'''"''<br />
VendorName "ATI Technologies Inc"<br />
BoardName "ATI Radeon Xpress 1200 Series"<br />
BusID "PCI:1:5:0"<br />
EndSection<br />
<br />
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.<br />
<br />
=== Physical display size ===<br />
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.<br />
<br />
Section "Monitor"<br />
...<br />
DisplaySize '''155 95'''<br />
EndSection<br />
<br />
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.<br />
<br />
=== Disable composite ===<br />
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.<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
EndSection<br />
<br />
=== Additional options ===<br />
To be continued, I don't think this is enough to get UI2 completely (either mode) going yet. Feel free to jump in anytime... <br />
<br />
<br />
Things still to sort out amongst others (i.e. what is it, do we need it and what are the settings if any):<br />
<br />
Section "Module"<br />
Load "i2c"<br />
Load "bitmap"<br />
Load "ddc"<br />
Load "freetype"<br />
Load "int10"<br />
Load "vbe"<br />
Load "speedo"<br />
Load "type1"<br />
Load "dbe"<br />
Load "glx"<br />
Load "v4l"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AIGLX" "off"<br />
EndSection<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
# Option "RENDER" "true"<br />
EndSection<br />
<br />
Option "PseudoColorVisuals" "off"<br />
Option "OpenGLOverlay" "off"<br />
Option "VideoOverlay" "off"<br />
Option "DesktopSetup" "clone"<br />
<br />
TV-out options, 2nd display, etc.<br />
<br />
<br />
== Troubleshooting ==<br />
<br />
=== The AVWizard crashes X-windows ===<br />
<br />
Try setting the [[#Chipset_driver]] option to '''vesa''', run the AVWizard again and then change the driver back to what it was.<br />
<br />
=== Black screen ===<br />
<br />
* 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.<br />
<br />
*One problem on nvidia-cards could be that it does not detect the right monitor.<br />
<br />
::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><br />
::where XXX is CRT, CRT-0, CRT-1, DVI-0, DVI-1, ...<br />
::Save and exit (nano: Ctrl+x) and restart the computer. In my case it was "CRT-1".<br />
<br />
=== X-windows won't start ===<br />
<br />
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]-[&larr;Backspace] simultaneous to quit (alternative: use "startx" and get the full desktop, if any), then reboot when it works and you're done.<br />
<br />
=== Signal out of range ===<br />
<br />
See ''[[#Refresh rate / ModeLine ]]'' above.<br />
<br />
=== Microscopic fonts in KDE ===<br />
<br />
See ''[[#Physical_display_size]]'' above.<br />
<br />
If the above does not work, probably Xorg is calculating the DPI value in the wrong way.<br />
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.<br />
<br />
If those values are too small, fonts will be displayed accordingly (i.e, VERY small)<br />
<br />
A workaround is to force Xorg to startup with a given DPI value.<br />
<br />
To achieve this the following steps are required:<br />
<br />
* edit the file /usr/pluto/bin/Start_X_Wrapper.sh on your MD where you are facing the font problem<br />
* find the line beginning with xinit<br />
* add "-dpi 96" (without quotes) at the end of this line<br />
* save the file and reboot MD<br />
<br />
Obviously it is possible to set DPI to something different than 96, according to specific needs.<br />
<br />
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.<br />
<br />
=== LinuxMCE keeps reconfiguring my display settings ===<br />
<br />
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.<br />
<br />
For LinuxMCE 710 simply comment out the line that says<br />
. /usr/pluto/bin/X-CleanupVideo.sh<br />
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.<br />
<br />
== See also ==<br />
* [http://www.mythtv.org/wiki/index.php/Main_Page MythTV wiki] <br />
* MythTV Experience [http://brentlagesse.net/~brent/mythtv.php]<br />
* [[X_Configuration_Scripts]]</div>Unihttp://wiki.linuxmce.org/index.php?title=Display_Drivers&diff=18435Display Drivers2009-04-13T22:13:51Z<p>Uni: /* Installation */</p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
[[Category: Tutorials]]<br />
[[Category: Hardware| ]]<br />
<br />
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.<br />
<br />
'''Note that this should normally not be necessary unless you have specific wishes or trouble getting your display to work properly.''' <br />
<br />
== Installation ==<br />
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. Before you get started on the below, you will want to (from recovery mode) issue this command "cat /proc/interrupts" and make sure your video card is not sharing an interrupt with another device, such as a NIC (network interface card). If it is, you could run into a lot of issues. Your output should look something like this:<br />
<br />
19: 38492811 0 IO-APIC-fasteoi eth0 <br><br />
20: 2 0 IO-APIC-fasteoi ehci_hcd:usb2 <br><br />
21: 10938712 0 IO-APIC-fasteoi nvidia <br><br />
<br />
=== ATI Chipsets ===<br />
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].<br />
<br />
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.<br />
<br />
==== Installing The ATI Driver ====<br />
<br />
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.<br />
<br />
'''Step 1'''<br />
<br />
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'.<br />
<br />
'''Step 2'''<br />
<br />
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;<br />
<br />
sudo su - <return><br />
ssh moonNN <return> (**where the NN is the device number for the MD we're configuring**)<br />
<br />
Alternatively do the following from the MD/Core you are configuring;<br />
<br />
Ctrl+Alt+2<br />
<br />
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;<br />
<br />
Firstly make sure our sources.list is up to date:<br />
<br />
apt-get update <return><br />
<br />
Now lets install the ATI driver and packages;<br />
<br />
apt-get install linux-restricted-modules-generic restricted-manager <return><br />
<br />
Answer 'Y' to installing new packages then do the following steps;<br />
<br />
apt-get install xorg-driver-fglrx <return><br />
depmod -a <return><br />
<br />
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;<br />
<br />
I use the console text editor 'joe' below but you can use whichever you prefer ('nano' is installed by default for example);<br />
<br />
joe /etc/X11/xorg.conf <return><br />
<br />
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;<br />
<br />
Driver "vesa"<br />
or<br />
Driver "ati"<br />
<br />
Change the string 'vesa' (or ati) to 'fglrx' which is the name of the ATI driver. The updated driver line should look like below;<br />
<br />
Driver "fglrx"<br />
<br />
Now save the changes you have made to xorg.conf.<br />
<br />
Now reboot the MD from the console with;<br />
<br />
reboot <return><br />
<br />
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.<br />
<br />
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.<br />
<br />
=== NVidia Chipsets ===<br />
<br />
==== Bugs ====<br />
If you are here, trying to update your driver because video is not working, remember that there is a bug with some Nvidia cards that makes graphical output always appear on the DVI plug, not the VGA plug. If you have a display attached to the VGA port on your adapter, buy a DVI to VGA converter plug before putting yourself through a lot of pain!<br />
<br />
==== Legacy Drivers ====<br />
With legacy drivers the AVWizard might crash because it could not load the nvidia-legacy kernel module. It is unclear why kdm will start and not the AVWizard. A quick fix is to set the '''Driver''' option for the video card in the ''/etc/X11/xorg.conf'' file to '''vesa'''. Go through the AVWizard and then change it back. Another option is to edit ''/etc/modprobe.d/aliases'' and add '''alias nvidia nvidia-legacy'''. Don't forget about this line when you switch to a newer card.<br />
<br />
==== Latest Drivers ====<br />
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. <br />
<br />
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. <br />
'''<you>@dcerouter:~$''' sudo -s<br />
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:<br />
'''root@dcerouter:~#''' wget <nowiki>http://us.download.nvidia.com/XFree86/Linux-x86/</nowiki>''<version>''<nowiki>/NVIDIA-Linux-x86-</nowiki>''<version>''<nowiki>-pkg1.run</nowiki><br />
3. Go to runlevel 1 to stop the currently running X-server. <br />
'''root@dcerouter:~#''' telinit 1 <br />
4. Execute the installer and follow instructions. a) Ignore the warning about runlevel 1 and b) don't bother looking for "precompiled kernel interfaces" (drivers).<br />
'''root@dcerouter:~#''' sh NVIDIA-Linux-x86-''<version>''-pkg1.run<br />
5. The installer will attempt to remove old legacy drivers. If it cannot, you may receive X errors (Eg. ''Error: API mismatch''). The solution is to manually remove or disable the legacy drivers. <br />
'''nano /etc/default/linux-restricted-modules-common''' <br />
Disable the NVIDIA linux-restricted kernel modules (nvidia, nvidia_legacy) by changing the DISABLED_MODULES line to read:<br />
'''DISABLED_MODULES="nv nvidia_new"'''<br />
6. 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.<br />
<br />
''** Update - Do a "sudo cat /proc/driver/nvidia/version" and make sure it reads something similar to this, matching the newest drivers you just installed: NVIDIA UNIX x86 Kernel Module 180.29. The "nvclock" utility is useful for monitoring GPU overheating''<br />
<br />
==== Media Directors ====<br />
Instructions for installing the latest nVidia driver on your media directors can be found in the [[Upgrading the Kernel#Video Drivers|upgrading the kernel]] wiki.<br />
<br />
=== Intel Chipsets ===<br />
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.<br />
<br />
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.<br />
<br />
==== For LinuxMCE-0704 ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
From man i810:<br />
Option "LinearAlloc" "integer"<br />
Allows more memory for the offscreen allocator. This usually<br />
helps in situations where HDTV movies are required to play but<br />
not enough offscreen memory is usually available. Set this to<br />
8160 for upto 1920x1080 HDTV support. Default 0KB (off).<br />
<br />
==== potential problem ====<br />
<br />
there can be a problem with some intel drivers, like the gma 3100. see [[bug/gma3100driver]] for further informations<br />
<br />
=== Via Chipsets ===<br />
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]<br />
<br />
The proprietary Via Unichrome driver works best with Linux MCE. Unfortunately this driver has intentionally been stripped of support for most GLX extensions. This driver does not support alpha blending which is a prerequisite of [[UI2]]. Via licenses the full featured driver to system integrators, such as [[Fiire]]. This licensed driver is not publicly available. Additionally there is a known incompatibility issue with the licensed driver and Linux MCE 0710. <br />
<br />
On April 08, 2008 Via announced a new open source initiative to help develop open drivers for certain video chipsets [http://www.phoronix.com/scan.php?page=article&item=via_oss&num=1]. This press release echos sour notes with many developers who have heard this tune many times before. No useful information or code has been released to date, striking yet another all to familiar chord in the open source community [http://www.phoronix.com/scan.php?page=article&item=via_bluff&num=1].<br />
<br />
'''HOW-TO VIA Openchrome driver for xorg:'''<br><br />
For VIA CX700M2 UniChrome PRO II Graphics (1" VIA units) or mainly via graphics:<br><br />
<br />
''shell into your box and do the following:''<br><br />
apt-get -y 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 subversion xserver-xorg-dev libdrm-dev libxvmc-dev<br />
<br />
cd /usr/src<br />
svn checkout http://svn.openchrome.org/svn/trunk openchrome<br />
cd openchrome*<br />
./autogen.sh --prefix=/usr<br />
make<br />
make install<br />
<br />
Now we have to edit /etc/X11/xorg.conf and change the device driver to via openchrome:<br><br />
vi /etc/X11/xorg.conf<br />
Go to<br />
Section "Device"<br />
and change<br />
Driver "vesa" <br />
to<br />
Driver "openchrome"<br />
save and test the compiled new driver with a: <br><br />
X :1<br />
and if your xwindow comes up, you can reboot and have fun<br><br />
<br />
=== Other Chipsets ===<br />
Please help out by adding more if you can.<br />
<br />
== Configuration ==<br />
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.<br />
<br />
=== Getting started ===<br />
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. <br />
<br />
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:<br />
telinit 1<br />
This wil stop the running X-server and drop you into rescue mode as well. <br />
<br />
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.<br />
<br />
=== Generating a template ===<br />
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. <br />
<br />
'''While there is no (other) X-server running''' you can create a template configuration file by running:<br />
X -configure<br />
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:<br />
X -config ~/xorg.conf.new<br />
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). <br />
<br />
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.<br />
<br />
Here is an example of such a generated file:<br />
<br />
Section "ServerLayout"<br />
Identifier "X.org Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Mouse0" "CorePointer"<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/etc/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/X11/misc"<br />
FontPath "/usr/X11R6/lib/X11/fonts/misc"<br />
FontPath "/usr/share/fonts/X11/cyrillic"<br />
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/Type1"<br />
FontPath "/usr/X11R6/lib/X11/fonts/Type1"<br />
FontPath "/usr/share/fonts/X11/100dpi"<br />
FontPath "/usr/share/fonts/X11/75dpi"<br />
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "extmod"<br />
Load "record"<br />
Load "xtrap"<br />
Load "dri"<br />
Load "glx"<br />
Load "dbe"<br />
Load "GLcore"<br />
Load "type1"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Keyboard0"<br />
Driver "kbd"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Mouse0"<br />
Driver "mouse"<br />
Option "Protocol" "auto"<br />
Option "Device" "/dev/input/mice"<br />
Option "ZAxisMapping" "4 5 6 7"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
EndSection<br />
<br />
Section "Device"<br />
### Available Driver options are:-<br />
### Values: &lt;i&gt;: integer, <f>: float, <bool>: "True"/"False",<br />
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"<br />
### [arg]: arg optional<br />
#Option "ShadowFB" # [<bool>]<br />
#Option "DefaultRefresh" # [<bool>]<br />
#Option "ModeSetClearScreen" # [<bool>]<br />
Identifier "Card0"<br />
Driver "vesa"<br />
''VendorName "ATI Technologies Inc"''<br />
''BoardName "ATI Radeon Xpress 1200 Series"''<br />
''BusID '''"PCI:1:5:0"'''''<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 1<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 4<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 8<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 15<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 16<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
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:<br />
X -scanpci<br />
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.<br />
<br />
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.<br />
<br />
=== Refresh rate / ModeLine ===<br />
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:<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
''HorizSync '''27-102''' # kHz''<br />
''VertRefresh '''50-160''' # Hz''<br />
EndSection<br />
<br />
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. <br />
<br />
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. <br />
* http://koala.ilog.fr/cgi-bin/nph-colas-modelines<br />
* http://xtiming.sourceforge.net/cgi-bin/xtiming.pl<br />
* http://www.bohne-lang.de/spec/linux/modeline/<br />
* http://amlc.berlios.de/<br />
* http://www.mythtv.org/wiki/index.php/Working_with_Modelines<br />
If one modeline doesn't work perfectly, try another, perhaps from another generator, because they can vary so much.<br />
<br />
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]-[&larr;Backspace] and readjust your settings. Most modern screens however simply report that the signal is out of range if this happens.<br />
<br />
=== Colordepth and resolution ===<br />
Specify the colordepth and resolution(s) you would like to use, like this:<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
''DefaultDepth '''24'''''<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
''Virtual '''1600 1200'''''<br />
''Modes '''"1600x1200" "1280x1024" "1024x768" "800x600" "640x480" "512x384" "400x300" "320x240"'''''<br />
EndSubSection<br />
EndSection<br />
<br />
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.<br />
<br />
=== DRI device permissions ===<br />
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.<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
<br />
=== Chipset driver ===<br />
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''').<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
''# Driver "'''vesa'''"''<br />
''Driver "'''fglrx'''"''<br />
VendorName "ATI Technologies Inc"<br />
BoardName "ATI Radeon Xpress 1200 Series"<br />
BusID "PCI:1:5:0"<br />
EndSection<br />
<br />
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.<br />
<br />
=== Physical display size ===<br />
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.<br />
<br />
Section "Monitor"<br />
...<br />
DisplaySize '''155 95'''<br />
EndSection<br />
<br />
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.<br />
<br />
=== Disable composite ===<br />
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.<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
EndSection<br />
<br />
=== Additional options ===<br />
To be continued, I don't think this is enough to get UI2 completely (either mode) going yet. Feel free to jump in anytime... <br />
<br />
<br />
Things still to sort out amongst others (i.e. what is it, do we need it and what are the settings if any):<br />
<br />
Section "Module"<br />
Load "i2c"<br />
Load "bitmap"<br />
Load "ddc"<br />
Load "freetype"<br />
Load "int10"<br />
Load "vbe"<br />
Load "speedo"<br />
Load "type1"<br />
Load "dbe"<br />
Load "glx"<br />
Load "v4l"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AIGLX" "off"<br />
EndSection<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
# Option "RENDER" "true"<br />
EndSection<br />
<br />
Option "PseudoColorVisuals" "off"<br />
Option "OpenGLOverlay" "off"<br />
Option "VideoOverlay" "off"<br />
Option "DesktopSetup" "clone"<br />
<br />
TV-out options, 2nd display, etc.<br />
<br />
<br />
== Troubleshooting ==<br />
<br />
=== The AVWizard crashes X-windows ===<br />
<br />
Try setting the [[#Chipset_driver]] option to '''vesa''', run the AVWizard again and then change the driver back to what it was.<br />
<br />
=== Black screen ===<br />
<br />
* 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.<br />
<br />
*One problem on nvidia-cards could be that it does not detect the right monitor.<br />
<br />
::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><br />
::where XXX is CRT, CRT-0, CRT-1, DVI-0, DVI-1, ...<br />
::Save and exit (nano: Ctrl+x) and restart the computer. In my case it was "CRT-1".<br />
<br />
=== X-windows won't start ===<br />
<br />
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]-[&larr;Backspace] simultaneous to quit (alternative: use "startx" and get the full desktop, if any), then reboot when it works and you're done.<br />
<br />
=== Signal out of range ===<br />
<br />
See ''[[#Refresh rate / ModeLine ]]'' above.<br />
<br />
=== Microscopic fonts in KDE ===<br />
<br />
See ''[[#Physical_display_size]]'' above.<br />
<br />
If the above does not work, probably Xorg is calculating the DPI value in the wrong way.<br />
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.<br />
<br />
If those values are too small, fonts will be displayed accordingly (i.e, VERY small)<br />
<br />
A workaround is to force Xorg to startup with a given DPI value.<br />
<br />
To achieve this the following steps are required:<br />
<br />
* edit the file /usr/pluto/bin/Start_X_Wrapper.sh on your MD where you are facing the font problem<br />
* find the line beginning with xinit<br />
* add "-dpi 96" (without quotes) at the end of this line<br />
* save the file and reboot MD<br />
<br />
Obviously it is possible to set DPI to something different than 96, according to specific needs.<br />
<br />
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.<br />
<br />
=== LinuxMCE keeps reconfiguring my display settings ===<br />
<br />
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.<br />
<br />
For LinuxMCE 710 simply comment out the line that says<br />
. /usr/pluto/bin/X-CleanupVideo.sh<br />
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.<br />
<br />
== See also ==<br />
* [http://www.mythtv.org/wiki/index.php/Main_Page MythTV wiki] <br />
* MythTV Experience [http://brentlagesse.net/~brent/mythtv.php]<br />
* [[X_Configuration_Scripts]]</div>Unihttp://wiki.linuxmce.org/index.php?title=Display_Drivers&diff=18434Display Drivers2009-04-13T22:13:13Z<p>Uni: /* Installation */</p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
[[Category: Tutorials]]<br />
[[Category: Hardware| ]]<br />
<br />
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.<br />
<br />
'''Note that this should normally not be necessary unless you have specific wishes or trouble getting your display to work properly.''' <br />
<br />
== Installation ==<br />
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. Before you get started on the below, you will want to (from recovery mode) issue this command "cat /proc/interrupts" and make sure your video card is not sharing an interrupt with another device, such as a NIC. If it is, you could run into a lot of issues. Your output should look something like this:<br />
<br />
19: 38492811 0 IO-APIC-fasteoi eth0 <br><br />
20: 2 0 IO-APIC-fasteoi ehci_hcd:usb2 <br><br />
21: 10938712 0 IO-APIC-fasteoi nvidia <br><br />
<br />
=== ATI Chipsets ===<br />
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].<br />
<br />
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.<br />
<br />
==== Installing The ATI Driver ====<br />
<br />
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.<br />
<br />
'''Step 1'''<br />
<br />
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'.<br />
<br />
'''Step 2'''<br />
<br />
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;<br />
<br />
sudo su - <return><br />
ssh moonNN <return> (**where the NN is the device number for the MD we're configuring**)<br />
<br />
Alternatively do the following from the MD/Core you are configuring;<br />
<br />
Ctrl+Alt+2<br />
<br />
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;<br />
<br />
Firstly make sure our sources.list is up to date:<br />
<br />
apt-get update <return><br />
<br />
Now lets install the ATI driver and packages;<br />
<br />
apt-get install linux-restricted-modules-generic restricted-manager <return><br />
<br />
Answer 'Y' to installing new packages then do the following steps;<br />
<br />
apt-get install xorg-driver-fglrx <return><br />
depmod -a <return><br />
<br />
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;<br />
<br />
I use the console text editor 'joe' below but you can use whichever you prefer ('nano' is installed by default for example);<br />
<br />
joe /etc/X11/xorg.conf <return><br />
<br />
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;<br />
<br />
Driver "vesa"<br />
or<br />
Driver "ati"<br />
<br />
Change the string 'vesa' (or ati) to 'fglrx' which is the name of the ATI driver. The updated driver line should look like below;<br />
<br />
Driver "fglrx"<br />
<br />
Now save the changes you have made to xorg.conf.<br />
<br />
Now reboot the MD from the console with;<br />
<br />
reboot <return><br />
<br />
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.<br />
<br />
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.<br />
<br />
=== NVidia Chipsets ===<br />
<br />
==== Bugs ====<br />
If you are here, trying to update your driver because video is not working, remember that there is a bug with some Nvidia cards that makes graphical output always appear on the DVI plug, not the VGA plug. If you have a display attached to the VGA port on your adapter, buy a DVI to VGA converter plug before putting yourself through a lot of pain!<br />
<br />
==== Legacy Drivers ====<br />
With legacy drivers the AVWizard might crash because it could not load the nvidia-legacy kernel module. It is unclear why kdm will start and not the AVWizard. A quick fix is to set the '''Driver''' option for the video card in the ''/etc/X11/xorg.conf'' file to '''vesa'''. Go through the AVWizard and then change it back. Another option is to edit ''/etc/modprobe.d/aliases'' and add '''alias nvidia nvidia-legacy'''. Don't forget about this line when you switch to a newer card.<br />
<br />
==== Latest Drivers ====<br />
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. <br />
<br />
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. <br />
'''<you>@dcerouter:~$''' sudo -s<br />
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:<br />
'''root@dcerouter:~#''' wget <nowiki>http://us.download.nvidia.com/XFree86/Linux-x86/</nowiki>''<version>''<nowiki>/NVIDIA-Linux-x86-</nowiki>''<version>''<nowiki>-pkg1.run</nowiki><br />
3. Go to runlevel 1 to stop the currently running X-server. <br />
'''root@dcerouter:~#''' telinit 1 <br />
4. Execute the installer and follow instructions. a) Ignore the warning about runlevel 1 and b) don't bother looking for "precompiled kernel interfaces" (drivers).<br />
'''root@dcerouter:~#''' sh NVIDIA-Linux-x86-''<version>''-pkg1.run<br />
5. The installer will attempt to remove old legacy drivers. If it cannot, you may receive X errors (Eg. ''Error: API mismatch''). The solution is to manually remove or disable the legacy drivers. <br />
'''nano /etc/default/linux-restricted-modules-common''' <br />
Disable the NVIDIA linux-restricted kernel modules (nvidia, nvidia_legacy) by changing the DISABLED_MODULES line to read:<br />
'''DISABLED_MODULES="nv nvidia_new"'''<br />
6. 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.<br />
<br />
''** Update - Do a "sudo cat /proc/driver/nvidia/version" and make sure it reads something similar to this, matching the newest drivers you just installed: NVIDIA UNIX x86 Kernel Module 180.29. The "nvclock" utility is useful for monitoring GPU overheating''<br />
<br />
==== Media Directors ====<br />
Instructions for installing the latest nVidia driver on your media directors can be found in the [[Upgrading the Kernel#Video Drivers|upgrading the kernel]] wiki.<br />
<br />
=== Intel Chipsets ===<br />
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.<br />
<br />
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.<br />
<br />
==== For LinuxMCE-0704 ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
From man i810:<br />
Option "LinearAlloc" "integer"<br />
Allows more memory for the offscreen allocator. This usually<br />
helps in situations where HDTV movies are required to play but<br />
not enough offscreen memory is usually available. Set this to<br />
8160 for upto 1920x1080 HDTV support. Default 0KB (off).<br />
<br />
==== potential problem ====<br />
<br />
there can be a problem with some intel drivers, like the gma 3100. see [[bug/gma3100driver]] for further informations<br />
<br />
=== Via Chipsets ===<br />
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]<br />
<br />
The proprietary Via Unichrome driver works best with Linux MCE. Unfortunately this driver has intentionally been stripped of support for most GLX extensions. This driver does not support alpha blending which is a prerequisite of [[UI2]]. Via licenses the full featured driver to system integrators, such as [[Fiire]]. This licensed driver is not publicly available. Additionally there is a known incompatibility issue with the licensed driver and Linux MCE 0710. <br />
<br />
On April 08, 2008 Via announced a new open source initiative to help develop open drivers for certain video chipsets [http://www.phoronix.com/scan.php?page=article&item=via_oss&num=1]. This press release echos sour notes with many developers who have heard this tune many times before. No useful information or code has been released to date, striking yet another all to familiar chord in the open source community [http://www.phoronix.com/scan.php?page=article&item=via_bluff&num=1].<br />
<br />
'''HOW-TO VIA Openchrome driver for xorg:'''<br><br />
For VIA CX700M2 UniChrome PRO II Graphics (1" VIA units) or mainly via graphics:<br><br />
<br />
''shell into your box and do the following:''<br><br />
apt-get -y 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 subversion xserver-xorg-dev libdrm-dev libxvmc-dev<br />
<br />
cd /usr/src<br />
svn checkout http://svn.openchrome.org/svn/trunk openchrome<br />
cd openchrome*<br />
./autogen.sh --prefix=/usr<br />
make<br />
make install<br />
<br />
Now we have to edit /etc/X11/xorg.conf and change the device driver to via openchrome:<br><br />
vi /etc/X11/xorg.conf<br />
Go to<br />
Section "Device"<br />
and change<br />
Driver "vesa" <br />
to<br />
Driver "openchrome"<br />
save and test the compiled new driver with a: <br><br />
X :1<br />
and if your xwindow comes up, you can reboot and have fun<br><br />
<br />
=== Other Chipsets ===<br />
Please help out by adding more if you can.<br />
<br />
== Configuration ==<br />
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.<br />
<br />
=== Getting started ===<br />
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. <br />
<br />
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:<br />
telinit 1<br />
This wil stop the running X-server and drop you into rescue mode as well. <br />
<br />
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.<br />
<br />
=== Generating a template ===<br />
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. <br />
<br />
'''While there is no (other) X-server running''' you can create a template configuration file by running:<br />
X -configure<br />
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:<br />
X -config ~/xorg.conf.new<br />
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). <br />
<br />
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.<br />
<br />
Here is an example of such a generated file:<br />
<br />
Section "ServerLayout"<br />
Identifier "X.org Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Mouse0" "CorePointer"<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/etc/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/X11/misc"<br />
FontPath "/usr/X11R6/lib/X11/fonts/misc"<br />
FontPath "/usr/share/fonts/X11/cyrillic"<br />
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/Type1"<br />
FontPath "/usr/X11R6/lib/X11/fonts/Type1"<br />
FontPath "/usr/share/fonts/X11/100dpi"<br />
FontPath "/usr/share/fonts/X11/75dpi"<br />
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "extmod"<br />
Load "record"<br />
Load "xtrap"<br />
Load "dri"<br />
Load "glx"<br />
Load "dbe"<br />
Load "GLcore"<br />
Load "type1"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Keyboard0"<br />
Driver "kbd"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Mouse0"<br />
Driver "mouse"<br />
Option "Protocol" "auto"<br />
Option "Device" "/dev/input/mice"<br />
Option "ZAxisMapping" "4 5 6 7"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
EndSection<br />
<br />
Section "Device"<br />
### Available Driver options are:-<br />
### Values: &lt;i&gt;: integer, <f>: float, <bool>: "True"/"False",<br />
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"<br />
### [arg]: arg optional<br />
#Option "ShadowFB" # [<bool>]<br />
#Option "DefaultRefresh" # [<bool>]<br />
#Option "ModeSetClearScreen" # [<bool>]<br />
Identifier "Card0"<br />
Driver "vesa"<br />
''VendorName "ATI Technologies Inc"''<br />
''BoardName "ATI Radeon Xpress 1200 Series"''<br />
''BusID '''"PCI:1:5:0"'''''<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 1<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 4<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 8<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 15<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 16<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
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:<br />
X -scanpci<br />
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.<br />
<br />
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.<br />
<br />
=== Refresh rate / ModeLine ===<br />
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:<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
''HorizSync '''27-102''' # kHz''<br />
''VertRefresh '''50-160''' # Hz''<br />
EndSection<br />
<br />
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. <br />
<br />
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. <br />
* http://koala.ilog.fr/cgi-bin/nph-colas-modelines<br />
* http://xtiming.sourceforge.net/cgi-bin/xtiming.pl<br />
* http://www.bohne-lang.de/spec/linux/modeline/<br />
* http://amlc.berlios.de/<br />
* http://www.mythtv.org/wiki/index.php/Working_with_Modelines<br />
If one modeline doesn't work perfectly, try another, perhaps from another generator, because they can vary so much.<br />
<br />
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]-[&larr;Backspace] and readjust your settings. Most modern screens however simply report that the signal is out of range if this happens.<br />
<br />
=== Colordepth and resolution ===<br />
Specify the colordepth and resolution(s) you would like to use, like this:<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
''DefaultDepth '''24'''''<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
''Virtual '''1600 1200'''''<br />
''Modes '''"1600x1200" "1280x1024" "1024x768" "800x600" "640x480" "512x384" "400x300" "320x240"'''''<br />
EndSubSection<br />
EndSection<br />
<br />
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.<br />
<br />
=== DRI device permissions ===<br />
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.<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
<br />
=== Chipset driver ===<br />
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''').<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
''# Driver "'''vesa'''"''<br />
''Driver "'''fglrx'''"''<br />
VendorName "ATI Technologies Inc"<br />
BoardName "ATI Radeon Xpress 1200 Series"<br />
BusID "PCI:1:5:0"<br />
EndSection<br />
<br />
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.<br />
<br />
=== Physical display size ===<br />
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.<br />
<br />
Section "Monitor"<br />
...<br />
DisplaySize '''155 95'''<br />
EndSection<br />
<br />
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.<br />
<br />
=== Disable composite ===<br />
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.<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
EndSection<br />
<br />
=== Additional options ===<br />
To be continued, I don't think this is enough to get UI2 completely (either mode) going yet. Feel free to jump in anytime... <br />
<br />
<br />
Things still to sort out amongst others (i.e. what is it, do we need it and what are the settings if any):<br />
<br />
Section "Module"<br />
Load "i2c"<br />
Load "bitmap"<br />
Load "ddc"<br />
Load "freetype"<br />
Load "int10"<br />
Load "vbe"<br />
Load "speedo"<br />
Load "type1"<br />
Load "dbe"<br />
Load "glx"<br />
Load "v4l"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AIGLX" "off"<br />
EndSection<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
# Option "RENDER" "true"<br />
EndSection<br />
<br />
Option "PseudoColorVisuals" "off"<br />
Option "OpenGLOverlay" "off"<br />
Option "VideoOverlay" "off"<br />
Option "DesktopSetup" "clone"<br />
<br />
TV-out options, 2nd display, etc.<br />
<br />
<br />
== Troubleshooting ==<br />
<br />
=== The AVWizard crashes X-windows ===<br />
<br />
Try setting the [[#Chipset_driver]] option to '''vesa''', run the AVWizard again and then change the driver back to what it was.<br />
<br />
=== Black screen ===<br />
<br />
* 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.<br />
<br />
*One problem on nvidia-cards could be that it does not detect the right monitor.<br />
<br />
::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><br />
::where XXX is CRT, CRT-0, CRT-1, DVI-0, DVI-1, ...<br />
::Save and exit (nano: Ctrl+x) and restart the computer. In my case it was "CRT-1".<br />
<br />
=== X-windows won't start ===<br />
<br />
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]-[&larr;Backspace] simultaneous to quit (alternative: use "startx" and get the full desktop, if any), then reboot when it works and you're done.<br />
<br />
=== Signal out of range ===<br />
<br />
See ''[[#Refresh rate / ModeLine ]]'' above.<br />
<br />
=== Microscopic fonts in KDE ===<br />
<br />
See ''[[#Physical_display_size]]'' above.<br />
<br />
If the above does not work, probably Xorg is calculating the DPI value in the wrong way.<br />
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.<br />
<br />
If those values are too small, fonts will be displayed accordingly (i.e, VERY small)<br />
<br />
A workaround is to force Xorg to startup with a given DPI value.<br />
<br />
To achieve this the following steps are required:<br />
<br />
* edit the file /usr/pluto/bin/Start_X_Wrapper.sh on your MD where you are facing the font problem<br />
* find the line beginning with xinit<br />
* add "-dpi 96" (without quotes) at the end of this line<br />
* save the file and reboot MD<br />
<br />
Obviously it is possible to set DPI to something different than 96, according to specific needs.<br />
<br />
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.<br />
<br />
=== LinuxMCE keeps reconfiguring my display settings ===<br />
<br />
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.<br />
<br />
For LinuxMCE 710 simply comment out the line that says<br />
. /usr/pluto/bin/X-CleanupVideo.sh<br />
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.<br />
<br />
== See also ==<br />
* [http://www.mythtv.org/wiki/index.php/Main_Page MythTV wiki] <br />
* MythTV Experience [http://brentlagesse.net/~brent/mythtv.php]<br />
* [[X_Configuration_Scripts]]</div>Unihttp://wiki.linuxmce.org/index.php?title=Display_Drivers&diff=18433Display Drivers2009-04-13T22:12:25Z<p>Uni: </p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
[[Category: Tutorials]]<br />
[[Category: Hardware| ]]<br />
<br />
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.<br />
<br />
'''Note that this should normally not be necessary unless you have specific wishes or trouble getting your display to work properly.''' <br />
<br />
== Installation ==<br />
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. Before you get started on the below, you will want to (from recovery mode) issue this command "cat /proc/interrupts" and make sure your video card is not sharing an interrupt with another device, such as a NIC. If it is, you could run into a lot of issues. It should look something like this:<br />
<br />
19: 38492811 0 IO-APIC-fasteoi eth0 <br><br />
20: 2 0 IO-APIC-fasteoi ehci_hcd:usb2 <br><br />
21: 10938712 0 IO-APIC-fasteoi nvidia <br><br />
<br />
=== ATI Chipsets ===<br />
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].<br />
<br />
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.<br />
<br />
==== Installing The ATI Driver ====<br />
<br />
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.<br />
<br />
'''Step 1'''<br />
<br />
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'.<br />
<br />
'''Step 2'''<br />
<br />
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;<br />
<br />
sudo su - <return><br />
ssh moonNN <return> (**where the NN is the device number for the MD we're configuring**)<br />
<br />
Alternatively do the following from the MD/Core you are configuring;<br />
<br />
Ctrl+Alt+2<br />
<br />
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;<br />
<br />
Firstly make sure our sources.list is up to date:<br />
<br />
apt-get update <return><br />
<br />
Now lets install the ATI driver and packages;<br />
<br />
apt-get install linux-restricted-modules-generic restricted-manager <return><br />
<br />
Answer 'Y' to installing new packages then do the following steps;<br />
<br />
apt-get install xorg-driver-fglrx <return><br />
depmod -a <return><br />
<br />
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;<br />
<br />
I use the console text editor 'joe' below but you can use whichever you prefer ('nano' is installed by default for example);<br />
<br />
joe /etc/X11/xorg.conf <return><br />
<br />
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;<br />
<br />
Driver "vesa"<br />
or<br />
Driver "ati"<br />
<br />
Change the string 'vesa' (or ati) to 'fglrx' which is the name of the ATI driver. The updated driver line should look like below;<br />
<br />
Driver "fglrx"<br />
<br />
Now save the changes you have made to xorg.conf.<br />
<br />
Now reboot the MD from the console with;<br />
<br />
reboot <return><br />
<br />
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.<br />
<br />
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.<br />
<br />
=== NVidia Chipsets ===<br />
<br />
==== Bugs ====<br />
If you are here, trying to update your driver because video is not working, remember that there is a bug with some Nvidia cards that makes graphical output always appear on the DVI plug, not the VGA plug. If you have a display attached to the VGA port on your adapter, buy a DVI to VGA converter plug before putting yourself through a lot of pain!<br />
<br />
==== Legacy Drivers ====<br />
With legacy drivers the AVWizard might crash because it could not load the nvidia-legacy kernel module. It is unclear why kdm will start and not the AVWizard. A quick fix is to set the '''Driver''' option for the video card in the ''/etc/X11/xorg.conf'' file to '''vesa'''. Go through the AVWizard and then change it back. Another option is to edit ''/etc/modprobe.d/aliases'' and add '''alias nvidia nvidia-legacy'''. Don't forget about this line when you switch to a newer card.<br />
<br />
==== Latest Drivers ====<br />
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. <br />
<br />
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. <br />
'''<you>@dcerouter:~$''' sudo -s<br />
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:<br />
'''root@dcerouter:~#''' wget <nowiki>http://us.download.nvidia.com/XFree86/Linux-x86/</nowiki>''<version>''<nowiki>/NVIDIA-Linux-x86-</nowiki>''<version>''<nowiki>-pkg1.run</nowiki><br />
3. Go to runlevel 1 to stop the currently running X-server. <br />
'''root@dcerouter:~#''' telinit 1 <br />
4. Execute the installer and follow instructions. a) Ignore the warning about runlevel 1 and b) don't bother looking for "precompiled kernel interfaces" (drivers).<br />
'''root@dcerouter:~#''' sh NVIDIA-Linux-x86-''<version>''-pkg1.run<br />
5. The installer will attempt to remove old legacy drivers. If it cannot, you may receive X errors (Eg. ''Error: API mismatch''). The solution is to manually remove or disable the legacy drivers. <br />
'''nano /etc/default/linux-restricted-modules-common''' <br />
Disable the NVIDIA linux-restricted kernel modules (nvidia, nvidia_legacy) by changing the DISABLED_MODULES line to read:<br />
'''DISABLED_MODULES="nv nvidia_new"'''<br />
6. 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.<br />
<br />
''** Update - Do a "sudo cat /proc/driver/nvidia/version" and make sure it reads something similar to this, matching the newest drivers you just installed: NVIDIA UNIX x86 Kernel Module 180.29. The "nvclock" utility is useful for monitoring GPU overheating''<br />
<br />
==== Media Directors ====<br />
Instructions for installing the latest nVidia driver on your media directors can be found in the [[Upgrading the Kernel#Video Drivers|upgrading the kernel]] wiki.<br />
<br />
=== Intel Chipsets ===<br />
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.<br />
<br />
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.<br />
<br />
==== For LinuxMCE-0704 ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
From man i810:<br />
Option "LinearAlloc" "integer"<br />
Allows more memory for the offscreen allocator. This usually<br />
helps in situations where HDTV movies are required to play but<br />
not enough offscreen memory is usually available. Set this to<br />
8160 for upto 1920x1080 HDTV support. Default 0KB (off).<br />
<br />
==== potential problem ====<br />
<br />
there can be a problem with some intel drivers, like the gma 3100. see [[bug/gma3100driver]] for further informations<br />
<br />
=== Via Chipsets ===<br />
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]<br />
<br />
The proprietary Via Unichrome driver works best with Linux MCE. Unfortunately this driver has intentionally been stripped of support for most GLX extensions. This driver does not support alpha blending which is a prerequisite of [[UI2]]. Via licenses the full featured driver to system integrators, such as [[Fiire]]. This licensed driver is not publicly available. Additionally there is a known incompatibility issue with the licensed driver and Linux MCE 0710. <br />
<br />
On April 08, 2008 Via announced a new open source initiative to help develop open drivers for certain video chipsets [http://www.phoronix.com/scan.php?page=article&item=via_oss&num=1]. This press release echos sour notes with many developers who have heard this tune many times before. No useful information or code has been released to date, striking yet another all to familiar chord in the open source community [http://www.phoronix.com/scan.php?page=article&item=via_bluff&num=1].<br />
<br />
'''HOW-TO VIA Openchrome driver for xorg:'''<br><br />
For VIA CX700M2 UniChrome PRO II Graphics (1" VIA units) or mainly via graphics:<br><br />
<br />
''shell into your box and do the following:''<br><br />
apt-get -y 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 subversion xserver-xorg-dev libdrm-dev libxvmc-dev<br />
<br />
cd /usr/src<br />
svn checkout http://svn.openchrome.org/svn/trunk openchrome<br />
cd openchrome*<br />
./autogen.sh --prefix=/usr<br />
make<br />
make install<br />
<br />
Now we have to edit /etc/X11/xorg.conf and change the device driver to via openchrome:<br><br />
vi /etc/X11/xorg.conf<br />
Go to<br />
Section "Device"<br />
and change<br />
Driver "vesa" <br />
to<br />
Driver "openchrome"<br />
save and test the compiled new driver with a: <br><br />
X :1<br />
and if your xwindow comes up, you can reboot and have fun<br><br />
<br />
=== Other Chipsets ===<br />
Please help out by adding more if you can.<br />
<br />
== Configuration ==<br />
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.<br />
<br />
=== Getting started ===<br />
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. <br />
<br />
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:<br />
telinit 1<br />
This wil stop the running X-server and drop you into rescue mode as well. <br />
<br />
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.<br />
<br />
=== Generating a template ===<br />
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. <br />
<br />
'''While there is no (other) X-server running''' you can create a template configuration file by running:<br />
X -configure<br />
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:<br />
X -config ~/xorg.conf.new<br />
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). <br />
<br />
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.<br />
<br />
Here is an example of such a generated file:<br />
<br />
Section "ServerLayout"<br />
Identifier "X.org Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Mouse0" "CorePointer"<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/etc/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/X11/misc"<br />
FontPath "/usr/X11R6/lib/X11/fonts/misc"<br />
FontPath "/usr/share/fonts/X11/cyrillic"<br />
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/Type1"<br />
FontPath "/usr/X11R6/lib/X11/fonts/Type1"<br />
FontPath "/usr/share/fonts/X11/100dpi"<br />
FontPath "/usr/share/fonts/X11/75dpi"<br />
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "extmod"<br />
Load "record"<br />
Load "xtrap"<br />
Load "dri"<br />
Load "glx"<br />
Load "dbe"<br />
Load "GLcore"<br />
Load "type1"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Keyboard0"<br />
Driver "kbd"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Mouse0"<br />
Driver "mouse"<br />
Option "Protocol" "auto"<br />
Option "Device" "/dev/input/mice"<br />
Option "ZAxisMapping" "4 5 6 7"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
EndSection<br />
<br />
Section "Device"<br />
### Available Driver options are:-<br />
### Values: &lt;i&gt;: integer, <f>: float, <bool>: "True"/"False",<br />
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"<br />
### [arg]: arg optional<br />
#Option "ShadowFB" # [<bool>]<br />
#Option "DefaultRefresh" # [<bool>]<br />
#Option "ModeSetClearScreen" # [<bool>]<br />
Identifier "Card0"<br />
Driver "vesa"<br />
''VendorName "ATI Technologies Inc"''<br />
''BoardName "ATI Radeon Xpress 1200 Series"''<br />
''BusID '''"PCI:1:5:0"'''''<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 1<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 4<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 8<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 15<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 16<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
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:<br />
X -scanpci<br />
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.<br />
<br />
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.<br />
<br />
=== Refresh rate / ModeLine ===<br />
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:<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
''HorizSync '''27-102''' # kHz''<br />
''VertRefresh '''50-160''' # Hz''<br />
EndSection<br />
<br />
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. <br />
<br />
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. <br />
* http://koala.ilog.fr/cgi-bin/nph-colas-modelines<br />
* http://xtiming.sourceforge.net/cgi-bin/xtiming.pl<br />
* http://www.bohne-lang.de/spec/linux/modeline/<br />
* http://amlc.berlios.de/<br />
* http://www.mythtv.org/wiki/index.php/Working_with_Modelines<br />
If one modeline doesn't work perfectly, try another, perhaps from another generator, because they can vary so much.<br />
<br />
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]-[&larr;Backspace] and readjust your settings. Most modern screens however simply report that the signal is out of range if this happens.<br />
<br />
=== Colordepth and resolution ===<br />
Specify the colordepth and resolution(s) you would like to use, like this:<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
''DefaultDepth '''24'''''<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
''Virtual '''1600 1200'''''<br />
''Modes '''"1600x1200" "1280x1024" "1024x768" "800x600" "640x480" "512x384" "400x300" "320x240"'''''<br />
EndSubSection<br />
EndSection<br />
<br />
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.<br />
<br />
=== DRI device permissions ===<br />
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.<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
<br />
=== Chipset driver ===<br />
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''').<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
''# Driver "'''vesa'''"''<br />
''Driver "'''fglrx'''"''<br />
VendorName "ATI Technologies Inc"<br />
BoardName "ATI Radeon Xpress 1200 Series"<br />
BusID "PCI:1:5:0"<br />
EndSection<br />
<br />
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.<br />
<br />
=== Physical display size ===<br />
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.<br />
<br />
Section "Monitor"<br />
...<br />
DisplaySize '''155 95'''<br />
EndSection<br />
<br />
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.<br />
<br />
=== Disable composite ===<br />
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.<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
EndSection<br />
<br />
=== Additional options ===<br />
To be continued, I don't think this is enough to get UI2 completely (either mode) going yet. Feel free to jump in anytime... <br />
<br />
<br />
Things still to sort out amongst others (i.e. what is it, do we need it and what are the settings if any):<br />
<br />
Section "Module"<br />
Load "i2c"<br />
Load "bitmap"<br />
Load "ddc"<br />
Load "freetype"<br />
Load "int10"<br />
Load "vbe"<br />
Load "speedo"<br />
Load "type1"<br />
Load "dbe"<br />
Load "glx"<br />
Load "v4l"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AIGLX" "off"<br />
EndSection<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
# Option "RENDER" "true"<br />
EndSection<br />
<br />
Option "PseudoColorVisuals" "off"<br />
Option "OpenGLOverlay" "off"<br />
Option "VideoOverlay" "off"<br />
Option "DesktopSetup" "clone"<br />
<br />
TV-out options, 2nd display, etc.<br />
<br />
<br />
== Troubleshooting ==<br />
<br />
=== The AVWizard crashes X-windows ===<br />
<br />
Try setting the [[#Chipset_driver]] option to '''vesa''', run the AVWizard again and then change the driver back to what it was.<br />
<br />
=== Black screen ===<br />
<br />
* 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.<br />
<br />
*One problem on nvidia-cards could be that it does not detect the right monitor.<br />
<br />
::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><br />
::where XXX is CRT, CRT-0, CRT-1, DVI-0, DVI-1, ...<br />
::Save and exit (nano: Ctrl+x) and restart the computer. In my case it was "CRT-1".<br />
<br />
=== X-windows won't start ===<br />
<br />
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]-[&larr;Backspace] simultaneous to quit (alternative: use "startx" and get the full desktop, if any), then reboot when it works and you're done.<br />
<br />
=== Signal out of range ===<br />
<br />
See ''[[#Refresh rate / ModeLine ]]'' above.<br />
<br />
=== Microscopic fonts in KDE ===<br />
<br />
See ''[[#Physical_display_size]]'' above.<br />
<br />
If the above does not work, probably Xorg is calculating the DPI value in the wrong way.<br />
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.<br />
<br />
If those values are too small, fonts will be displayed accordingly (i.e, VERY small)<br />
<br />
A workaround is to force Xorg to startup with a given DPI value.<br />
<br />
To achieve this the following steps are required:<br />
<br />
* edit the file /usr/pluto/bin/Start_X_Wrapper.sh on your MD where you are facing the font problem<br />
* find the line beginning with xinit<br />
* add "-dpi 96" (without quotes) at the end of this line<br />
* save the file and reboot MD<br />
<br />
Obviously it is possible to set DPI to something different than 96, according to specific needs.<br />
<br />
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.<br />
<br />
=== LinuxMCE keeps reconfiguring my display settings ===<br />
<br />
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.<br />
<br />
For LinuxMCE 710 simply comment out the line that says<br />
. /usr/pluto/bin/X-CleanupVideo.sh<br />
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.<br />
<br />
== See also ==<br />
* [http://www.mythtv.org/wiki/index.php/Main_Page MythTV wiki] <br />
* MythTV Experience [http://brentlagesse.net/~brent/mythtv.php]<br />
* [[X_Configuration_Scripts]]</div>Unihttp://wiki.linuxmce.org/index.php?title=Display_Drivers&diff=18432Display Drivers2009-04-13T22:11:25Z<p>Uni: </p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
[[Category: Tutorials]]<br />
[[Category: Hardware| ]]<br />
<br />
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.<br />
<br />
'''Note that this should normally not be necessary unless you have specific wishes or trouble getting your display to work properly.''' <br />
<br />
== Installation ==<br />
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. Before you get started on the below, you will want to (from recovery mode) issue this command "cat /proc/interrupts" and make sure your video card is not sharing an interrupt with another device, such as a NIC. If it is, you could run into a lot of issues. It should look something like this:<br />
<br />
19: 38492811 0 IO-APIC-fasteoi eth0<br />
20: 2 0 IO-APIC-fasteoi ehci_hcd:usb2<br />
21: 10938712 0 IO-APIC-fasteoi nvidia<br />
<br />
=== ATI Chipsets ===<br />
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].<br />
<br />
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.<br />
<br />
==== Installing The ATI Driver ====<br />
<br />
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.<br />
<br />
'''Step 1'''<br />
<br />
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'.<br />
<br />
'''Step 2'''<br />
<br />
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;<br />
<br />
sudo su - <return><br />
ssh moonNN <return> (**where the NN is the device number for the MD we're configuring**)<br />
<br />
Alternatively do the following from the MD/Core you are configuring;<br />
<br />
Ctrl+Alt+2<br />
<br />
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;<br />
<br />
Firstly make sure our sources.list is up to date:<br />
<br />
apt-get update <return><br />
<br />
Now lets install the ATI driver and packages;<br />
<br />
apt-get install linux-restricted-modules-generic restricted-manager <return><br />
<br />
Answer 'Y' to installing new packages then do the following steps;<br />
<br />
apt-get install xorg-driver-fglrx <return><br />
depmod -a <return><br />
<br />
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;<br />
<br />
I use the console text editor 'joe' below but you can use whichever you prefer ('nano' is installed by default for example);<br />
<br />
joe /etc/X11/xorg.conf <return><br />
<br />
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;<br />
<br />
Driver "vesa"<br />
or<br />
Driver "ati"<br />
<br />
Change the string 'vesa' (or ati) to 'fglrx' which is the name of the ATI driver. The updated driver line should look like below;<br />
<br />
Driver "fglrx"<br />
<br />
Now save the changes you have made to xorg.conf.<br />
<br />
Now reboot the MD from the console with;<br />
<br />
reboot <return><br />
<br />
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.<br />
<br />
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.<br />
<br />
=== NVidia Chipsets ===<br />
<br />
==== Bugs ====<br />
If you are here, trying to update your driver because video is not working, remember that there is a bug with some Nvidia cards that makes graphical output always appear on the DVI plug, not the VGA plug. If you have a display attached to the VGA port on your adapter, buy a DVI to VGA converter plug before putting yourself through a lot of pain!<br />
<br />
==== Legacy Drivers ====<br />
With legacy drivers the AVWizard might crash because it could not load the nvidia-legacy kernel module. It is unclear why kdm will start and not the AVWizard. A quick fix is to set the '''Driver''' option for the video card in the ''/etc/X11/xorg.conf'' file to '''vesa'''. Go through the AVWizard and then change it back. Another option is to edit ''/etc/modprobe.d/aliases'' and add '''alias nvidia nvidia-legacy'''. Don't forget about this line when you switch to a newer card.<br />
<br />
==== Latest Drivers ====<br />
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. <br />
<br />
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. <br />
'''<you>@dcerouter:~$''' sudo -s<br />
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:<br />
'''root@dcerouter:~#''' wget <nowiki>http://us.download.nvidia.com/XFree86/Linux-x86/</nowiki>''<version>''<nowiki>/NVIDIA-Linux-x86-</nowiki>''<version>''<nowiki>-pkg1.run</nowiki><br />
3. Go to runlevel 1 to stop the currently running X-server. <br />
'''root@dcerouter:~#''' telinit 1 <br />
4. Execute the installer and follow instructions. a) Ignore the warning about runlevel 1 and b) don't bother looking for "precompiled kernel interfaces" (drivers).<br />
'''root@dcerouter:~#''' sh NVIDIA-Linux-x86-''<version>''-pkg1.run<br />
5. The installer will attempt to remove old legacy drivers. If it cannot, you may receive X errors (Eg. ''Error: API mismatch''). The solution is to manually remove or disable the legacy drivers. <br />
'''nano /etc/default/linux-restricted-modules-common''' <br />
Disable the NVIDIA linux-restricted kernel modules (nvidia, nvidia_legacy) by changing the DISABLED_MODULES line to read:<br />
'''DISABLED_MODULES="nv nvidia_new"'''<br />
6. 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.<br />
<br />
''** Update - Do a "sudo cat /proc/driver/nvidia/version" and make sure it reads something similar to this, matching the newest drivers you just installed: NVIDIA UNIX x86 Kernel Module 180.29. The "nvclock" utility is useful for monitoring GPU overheating''<br />
<br />
==== Media Directors ====<br />
Instructions for installing the latest nVidia driver on your media directors can be found in the [[Upgrading the Kernel#Video Drivers|upgrading the kernel]] wiki.<br />
<br />
=== Intel Chipsets ===<br />
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.<br />
<br />
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.<br />
<br />
==== For LinuxMCE-0704 ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
From man i810:<br />
Option "LinearAlloc" "integer"<br />
Allows more memory for the offscreen allocator. This usually<br />
helps in situations where HDTV movies are required to play but<br />
not enough offscreen memory is usually available. Set this to<br />
8160 for upto 1920x1080 HDTV support. Default 0KB (off).<br />
<br />
==== potential problem ====<br />
<br />
there can be a problem with some intel drivers, like the gma 3100. see [[bug/gma3100driver]] for further informations<br />
<br />
=== Via Chipsets ===<br />
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]<br />
<br />
The proprietary Via Unichrome driver works best with Linux MCE. Unfortunately this driver has intentionally been stripped of support for most GLX extensions. This driver does not support alpha blending which is a prerequisite of [[UI2]]. Via licenses the full featured driver to system integrators, such as [[Fiire]]. This licensed driver is not publicly available. Additionally there is a known incompatibility issue with the licensed driver and Linux MCE 0710. <br />
<br />
On April 08, 2008 Via announced a new open source initiative to help develop open drivers for certain video chipsets [http://www.phoronix.com/scan.php?page=article&item=via_oss&num=1]. This press release echos sour notes with many developers who have heard this tune many times before. No useful information or code has been released to date, striking yet another all to familiar chord in the open source community [http://www.phoronix.com/scan.php?page=article&item=via_bluff&num=1].<br />
<br />
'''HOW-TO VIA Openchrome driver for xorg:'''<br><br />
For VIA CX700M2 UniChrome PRO II Graphics (1" VIA units) or mainly via graphics:<br><br />
<br />
''shell into your box and do the following:''<br><br />
apt-get -y 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 subversion xserver-xorg-dev libdrm-dev libxvmc-dev<br />
<br />
cd /usr/src<br />
svn checkout http://svn.openchrome.org/svn/trunk openchrome<br />
cd openchrome*<br />
./autogen.sh --prefix=/usr<br />
make<br />
make install<br />
<br />
Now we have to edit /etc/X11/xorg.conf and change the device driver to via openchrome:<br><br />
vi /etc/X11/xorg.conf<br />
Go to<br />
Section "Device"<br />
and change<br />
Driver "vesa" <br />
to<br />
Driver "openchrome"<br />
save and test the compiled new driver with a: <br><br />
X :1<br />
and if your xwindow comes up, you can reboot and have fun<br><br />
<br />
=== Other Chipsets ===<br />
Please help out by adding more if you can.<br />
<br />
== Configuration ==<br />
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.<br />
<br />
=== Getting started ===<br />
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. <br />
<br />
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:<br />
telinit 1<br />
This wil stop the running X-server and drop you into rescue mode as well. <br />
<br />
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.<br />
<br />
=== Generating a template ===<br />
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. <br />
<br />
'''While there is no (other) X-server running''' you can create a template configuration file by running:<br />
X -configure<br />
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:<br />
X -config ~/xorg.conf.new<br />
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). <br />
<br />
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.<br />
<br />
Here is an example of such a generated file:<br />
<br />
Section "ServerLayout"<br />
Identifier "X.org Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Mouse0" "CorePointer"<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/etc/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/X11/misc"<br />
FontPath "/usr/X11R6/lib/X11/fonts/misc"<br />
FontPath "/usr/share/fonts/X11/cyrillic"<br />
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/Type1"<br />
FontPath "/usr/X11R6/lib/X11/fonts/Type1"<br />
FontPath "/usr/share/fonts/X11/100dpi"<br />
FontPath "/usr/share/fonts/X11/75dpi"<br />
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "extmod"<br />
Load "record"<br />
Load "xtrap"<br />
Load "dri"<br />
Load "glx"<br />
Load "dbe"<br />
Load "GLcore"<br />
Load "type1"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Keyboard0"<br />
Driver "kbd"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Mouse0"<br />
Driver "mouse"<br />
Option "Protocol" "auto"<br />
Option "Device" "/dev/input/mice"<br />
Option "ZAxisMapping" "4 5 6 7"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
EndSection<br />
<br />
Section "Device"<br />
### Available Driver options are:-<br />
### Values: &lt;i&gt;: integer, <f>: float, <bool>: "True"/"False",<br />
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"<br />
### [arg]: arg optional<br />
#Option "ShadowFB" # [<bool>]<br />
#Option "DefaultRefresh" # [<bool>]<br />
#Option "ModeSetClearScreen" # [<bool>]<br />
Identifier "Card0"<br />
Driver "vesa"<br />
''VendorName "ATI Technologies Inc"''<br />
''BoardName "ATI Radeon Xpress 1200 Series"''<br />
''BusID '''"PCI:1:5:0"'''''<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 1<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 4<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 8<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 15<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 16<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
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:<br />
X -scanpci<br />
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.<br />
<br />
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.<br />
<br />
=== Refresh rate / ModeLine ===<br />
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:<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
''HorizSync '''27-102''' # kHz''<br />
''VertRefresh '''50-160''' # Hz''<br />
EndSection<br />
<br />
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. <br />
<br />
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. <br />
* http://koala.ilog.fr/cgi-bin/nph-colas-modelines<br />
* http://xtiming.sourceforge.net/cgi-bin/xtiming.pl<br />
* http://www.bohne-lang.de/spec/linux/modeline/<br />
* http://amlc.berlios.de/<br />
* http://www.mythtv.org/wiki/index.php/Working_with_Modelines<br />
If one modeline doesn't work perfectly, try another, perhaps from another generator, because they can vary so much.<br />
<br />
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]-[&larr;Backspace] and readjust your settings. Most modern screens however simply report that the signal is out of range if this happens.<br />
<br />
=== Colordepth and resolution ===<br />
Specify the colordepth and resolution(s) you would like to use, like this:<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
''DefaultDepth '''24'''''<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
''Virtual '''1600 1200'''''<br />
''Modes '''"1600x1200" "1280x1024" "1024x768" "800x600" "640x480" "512x384" "400x300" "320x240"'''''<br />
EndSubSection<br />
EndSection<br />
<br />
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.<br />
<br />
=== DRI device permissions ===<br />
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.<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
<br />
=== Chipset driver ===<br />
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''').<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
''# Driver "'''vesa'''"''<br />
''Driver "'''fglrx'''"''<br />
VendorName "ATI Technologies Inc"<br />
BoardName "ATI Radeon Xpress 1200 Series"<br />
BusID "PCI:1:5:0"<br />
EndSection<br />
<br />
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.<br />
<br />
=== Physical display size ===<br />
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.<br />
<br />
Section "Monitor"<br />
...<br />
DisplaySize '''155 95'''<br />
EndSection<br />
<br />
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.<br />
<br />
=== Disable composite ===<br />
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.<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
EndSection<br />
<br />
=== Additional options ===<br />
To be continued, I don't think this is enough to get UI2 completely (either mode) going yet. Feel free to jump in anytime... <br />
<br />
<br />
Things still to sort out amongst others (i.e. what is it, do we need it and what are the settings if any):<br />
<br />
Section "Module"<br />
Load "i2c"<br />
Load "bitmap"<br />
Load "ddc"<br />
Load "freetype"<br />
Load "int10"<br />
Load "vbe"<br />
Load "speedo"<br />
Load "type1"<br />
Load "dbe"<br />
Load "glx"<br />
Load "v4l"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AIGLX" "off"<br />
EndSection<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
# Option "RENDER" "true"<br />
EndSection<br />
<br />
Option "PseudoColorVisuals" "off"<br />
Option "OpenGLOverlay" "off"<br />
Option "VideoOverlay" "off"<br />
Option "DesktopSetup" "clone"<br />
<br />
TV-out options, 2nd display, etc.<br />
<br />
<br />
== Troubleshooting ==<br />
<br />
=== The AVWizard crashes X-windows ===<br />
<br />
Try setting the [[#Chipset_driver]] option to '''vesa''', run the AVWizard again and then change the driver back to what it was.<br />
<br />
=== Black screen ===<br />
<br />
* 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.<br />
<br />
*One problem on nvidia-cards could be that it does not detect the right monitor.<br />
<br />
::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><br />
::where XXX is CRT, CRT-0, CRT-1, DVI-0, DVI-1, ...<br />
::Save and exit (nano: Ctrl+x) and restart the computer. In my case it was "CRT-1".<br />
<br />
=== X-windows won't start ===<br />
<br />
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]-[&larr;Backspace] simultaneous to quit (alternative: use "startx" and get the full desktop, if any), then reboot when it works and you're done.<br />
<br />
=== Signal out of range ===<br />
<br />
See ''[[#Refresh rate / ModeLine ]]'' above.<br />
<br />
=== Microscopic fonts in KDE ===<br />
<br />
See ''[[#Physical_display_size]]'' above.<br />
<br />
If the above does not work, probably Xorg is calculating the DPI value in the wrong way.<br />
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.<br />
<br />
If those values are too small, fonts will be displayed accordingly (i.e, VERY small)<br />
<br />
A workaround is to force Xorg to startup with a given DPI value.<br />
<br />
To achieve this the following steps are required:<br />
<br />
* edit the file /usr/pluto/bin/Start_X_Wrapper.sh on your MD where you are facing the font problem<br />
* find the line beginning with xinit<br />
* add "-dpi 96" (without quotes) at the end of this line<br />
* save the file and reboot MD<br />
<br />
Obviously it is possible to set DPI to something different than 96, according to specific needs.<br />
<br />
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.<br />
<br />
=== LinuxMCE keeps reconfiguring my display settings ===<br />
<br />
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.<br />
<br />
For LinuxMCE 710 simply comment out the line that says<br />
. /usr/pluto/bin/X-CleanupVideo.sh<br />
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.<br />
<br />
== See also ==<br />
* [http://www.mythtv.org/wiki/index.php/Main_Page MythTV wiki] <br />
* MythTV Experience [http://brentlagesse.net/~brent/mythtv.php]<br />
* [[X_Configuration_Scripts]]</div>Unihttp://wiki.linuxmce.org/index.php?title=User:UNi&diff=18354User:UNi2009-04-08T16:31:42Z<p>Uni: /* MOTHERBOARD */</p>
<hr />
<div>[[Category:User Setups]]<br />
<br />
= '''About Me''' =<br />
<br />
I've been working with OpenBSD and Linux for 10 years, but never delved into X-Windows as I use OBSD mainly for LAMP functions. I live in Northern California (NorCAL) and work as a Network Engineer.<br />
<br />
= '''LinuxMCE''' =<br />
<br />
After experimenting with LMCE, I'm not convinced that Linux is more stable than Windows as I've had multiple crashes and weirdness going on with this product. I've finally got it stabilized somewhat after killing a few Processes that run by default, namely Motion / motion and ScreenSaver.<br />
<br />
<br />
== '''Next Steps''' ==<br />
<br />
<br />
<br />
* setup a MD after I'm sure the Core is stable and maybe wait until 810 before investing any more moola<br />
<br />
= '''Configuration''' =<br />
<br />
<br />
== '''Core''' ==<br />
<br />
<br />
<br />
<br />
=== Components: ===<br />
<br />
<br />
==== CPU ====<br />
<br />
Intel Dual-Core<br />
<br />
==== MOTHERBOARD ====<br />
<br />
[[ASUS P5NSLI LGA 775 NVIDIA nForce 570 SLI Intel Edition ATX Intel Motherboard]]<br />
<br />
* This motherboard seems to work but I got a ton of "rtc: lost some interrupts at 1024Hz" in Syslog and no one seems to know why...<br />
<br />
<br />
* µATX<br />
<br />
* 4x DDR2 Slot<br />
<br />
* GF 7600<br />
<br />
* onboard 5.1 Audio<br />
<br />
* 1x Gigabit Marvell LAN<br />
<br />
* 1x PCI-E 16x<br />
<br />
* 2x PCI-E 1x<br />
<br />
* 1x PCI<br />
<br />
==== RAM ====<br />
<br />
2GB Infineon CL5<br />
<br />
==== STORAGE ====<br />
Western Digital Caviar SE16 WD2500KS 250GB 7200 RPM SATA 3.0Gb/s Hard Drive - OEM <br />
<br />
<br />
==== PSU ====<br />
<br />
<br />
<br />
==== CASE ====<br />
<br />
Enermax<br />
<br />
<br />
==== OTHER ====<br />
<br />
CPU-FAN: <br />
<br />
<br />
== '''Media Directors''' ==<br />
<br />
none so far<br />
<br />
<br />
<br />
= '''Automation''' =<br />
<br />
* Added a Linksys Wireless-G Internet Video Camera WVC54GCA, and enabled motion module</div>Unihttp://wiki.linuxmce.org/index.php?title=User:UNi&diff=18353User:UNi2009-04-08T16:30:34Z<p>Uni: /* '''Automation''' */</p>
<hr />
<div>[[Category:User Setups]]<br />
<br />
= '''About Me''' =<br />
<br />
I've been working with OpenBSD and Linux for 10 years, but never delved into X-Windows as I use OBSD mainly for LAMP functions. I live in Northern California (NorCAL) and work as a Network Engineer.<br />
<br />
= '''LinuxMCE''' =<br />
<br />
After experimenting with LMCE, I'm not convinced that Linux is more stable than Windows as I've had multiple crashes and weirdness going on with this product. I've finally got it stabilized somewhat after killing a few Processes that run by default, namely Motion / motion and ScreenSaver.<br />
<br />
<br />
== '''Next Steps''' ==<br />
<br />
<br />
<br />
* setup a MD after I'm sure the Core is stable and maybe wait until 810 before investing any more moola<br />
<br />
= '''Configuration''' =<br />
<br />
<br />
== '''Core''' ==<br />
<br />
<br />
<br />
<br />
=== Components: ===<br />
<br />
<br />
==== CPU ====<br />
<br />
Intel Dual-Core<br />
<br />
==== MOTHERBOARD ====<br />
<br />
[[ASUS P5NSLI LGA 775 NVIDIA nForce 570 SLI Intel Edition ATX Intel Motherboard]]<br />
<br />
** This motherboard seems to work but I got a ton of "rtc: lost some interrupts at 1024Hz" in Syslog and no one seems to know why...<br />
<br />
<br />
* µATX<br />
<br />
* 4x DDR2 Slot<br />
<br />
* GF 7600<br />
<br />
* onboard 5.1 Audio<br />
<br />
* 1x Gigabit Marvell LAN<br />
<br />
* 1x PCI-E 16x<br />
<br />
* 2x PCI-E 1x<br />
<br />
* 1x PCI<br />
<br />
==== RAM ====<br />
<br />
2GB Infineon CL5<br />
<br />
==== STORAGE ====<br />
Western Digital Caviar SE16 WD2500KS 250GB 7200 RPM SATA 3.0Gb/s Hard Drive - OEM <br />
<br />
<br />
==== PSU ====<br />
<br />
<br />
<br />
==== CASE ====<br />
<br />
Enermax<br />
<br />
<br />
==== OTHER ====<br />
<br />
CPU-FAN: <br />
<br />
<br />
== '''Media Directors''' ==<br />
<br />
none so far<br />
<br />
<br />
<br />
= '''Automation''' =<br />
<br />
* Added a Linksys Wireless-G Internet Video Camera WVC54GCA, and enabled motion module</div>Unihttp://wiki.linuxmce.org/index.php?title=User:UNi&diff=18345User:UNi2009-04-07T23:01:34Z<p>Uni: /* '''Automation''' */</p>
<hr />
<div>[[Category:User Setups]]<br />
<br />
= '''About Me''' =<br />
<br />
I've been working with OpenBSD and Linux for 10 years, but never delved into X-Windows as I use OBSD mainly for LAMP functions. I live in Northern California (NorCAL) and work as a Network Engineer.<br />
<br />
= '''LinuxMCE''' =<br />
<br />
After experimenting with LMCE, I'm not convinced that Linux is more stable than Windows as I've had multiple crashes and weirdness going on with this product. I've finally got it stabilized somewhat after killing a few Processes that run by default, namely Motion / motion and ScreenSaver.<br />
<br />
<br />
== '''Next Steps''' ==<br />
<br />
<br />
<br />
* setup a MD after I'm sure the Core is stable and maybe wait until 810 before investing any more moola<br />
<br />
= '''Configuration''' =<br />
<br />
<br />
== '''Core''' ==<br />
<br />
<br />
<br />
<br />
=== Components: ===<br />
<br />
<br />
==== CPU ====<br />
<br />
Intel Dual-Core<br />
<br />
==== MOTHERBOARD ====<br />
<br />
[[ASUS P5NSLI LGA 775 NVIDIA nForce 570 SLI Intel Edition ATX Intel Motherboard]]<br />
<br />
** This motherboard seems to work but I got a ton of "rtc: lost some interrupts at 1024Hz" in Syslog and no one seems to know why...<br />
<br />
<br />
* µATX<br />
<br />
* 4x DDR2 Slot<br />
<br />
* GF 7600<br />
<br />
* onboard 5.1 Audio<br />
<br />
* 1x Gigabit Marvell LAN<br />
<br />
* 1x PCI-E 16x<br />
<br />
* 2x PCI-E 1x<br />
<br />
* 1x PCI<br />
<br />
==== RAM ====<br />
<br />
2GB Infineon CL5<br />
<br />
==== STORAGE ====<br />
Western Digital Caviar SE16 WD2500KS 250GB 7200 RPM SATA 3.0Gb/s Hard Drive - OEM <br />
<br />
<br />
==== PSU ====<br />
<br />
<br />
<br />
==== CASE ====<br />
<br />
Enermax<br />
<br />
<br />
==== OTHER ====<br />
<br />
CPU-FAN: <br />
<br />
<br />
== '''Media Directors''' ==<br />
<br />
none so far<br />
<br />
<br />
<br />
= '''Automation''' =<br />
<br />
* Added a Linksys Wireless camera and enabled motion module</div>Unihttp://wiki.linuxmce.org/index.php?title=User:UNi&diff=18344User:UNi2009-04-07T23:00:38Z<p>Uni: /* '''About Me''' */</p>
<hr />
<div>[[Category:User Setups]]<br />
<br />
= '''About Me''' =<br />
<br />
I've been working with OpenBSD and Linux for 10 years, but never delved into X-Windows as I use OBSD mainly for LAMP functions. I live in Northern California (NorCAL) and work as a Network Engineer.<br />
<br />
= '''LinuxMCE''' =<br />
<br />
After experimenting with LMCE, I'm not convinced that Linux is more stable than Windows as I've had multiple crashes and weirdness going on with this product. I've finally got it stabilized somewhat after killing a few Processes that run by default, namely Motion / motion and ScreenSaver.<br />
<br />
<br />
== '''Next Steps''' ==<br />
<br />
<br />
<br />
* setup a MD after I'm sure the Core is stable and maybe wait until 810 before investing any more moola<br />
<br />
= '''Configuration''' =<br />
<br />
<br />
== '''Core''' ==<br />
<br />
<br />
<br />
<br />
=== Components: ===<br />
<br />
<br />
==== CPU ====<br />
<br />
Intel Dual-Core<br />
<br />
==== MOTHERBOARD ====<br />
<br />
[[ASUS P5NSLI LGA 775 NVIDIA nForce 570 SLI Intel Edition ATX Intel Motherboard]]<br />
<br />
** This motherboard seems to work but I got a ton of "rtc: lost some interrupts at 1024Hz" in Syslog and no one seems to know why...<br />
<br />
<br />
* µATX<br />
<br />
* 4x DDR2 Slot<br />
<br />
* GF 7600<br />
<br />
* onboard 5.1 Audio<br />
<br />
* 1x Gigabit Marvell LAN<br />
<br />
* 1x PCI-E 16x<br />
<br />
* 2x PCI-E 1x<br />
<br />
* 1x PCI<br />
<br />
==== RAM ====<br />
<br />
2GB Infineon CL5<br />
<br />
==== STORAGE ====<br />
Western Digital Caviar SE16 WD2500KS 250GB 7200 RPM SATA 3.0Gb/s Hard Drive - OEM <br />
<br />
<br />
==== PSU ====<br />
<br />
<br />
<br />
==== CASE ====<br />
<br />
Enermax<br />
<br />
<br />
==== OTHER ====<br />
<br />
CPU-FAN: <br />
<br />
<br />
== '''Media Directors''' ==<br />
<br />
none so far<br />
<br />
<br />
<br />
= '''Automation''' =<br />
<br />
none so far</div>Unihttp://wiki.linuxmce.org/index.php?title=User:UNi&diff=18343User:UNi2009-04-07T22:59:33Z<p>Uni: /* '''LinuxMCE''' */</p>
<hr />
<div>[[Category:User Setups]]<br />
<br />
= '''About Me''' =<br />
<br />
I've been working with OpenBSD for 10 years, but never delved into X-Windows as I use OBSD mainly for LAMP functions. I live in Northern California (NorCAL) and work as a Network Engineer. <br />
<br />
<br />
= '''LinuxMCE''' =<br />
<br />
After experimenting with LMCE, I'm not convinced that Linux is more stable than Windows as I've had multiple crashes and weirdness going on with this product. I've finally got it stabilized somewhat after killing a few Processes that run by default, namely Motion / motion and ScreenSaver.<br />
<br />
<br />
== '''Next Steps''' ==<br />
<br />
<br />
<br />
* setup a MD after I'm sure the Core is stable and maybe wait until 810 before investing any more moola<br />
<br />
= '''Configuration''' =<br />
<br />
<br />
== '''Core''' ==<br />
<br />
<br />
<br />
<br />
=== Components: ===<br />
<br />
<br />
==== CPU ====<br />
<br />
Intel Dual-Core<br />
<br />
==== MOTHERBOARD ====<br />
<br />
[[ASUS P5NSLI LGA 775 NVIDIA nForce 570 SLI Intel Edition ATX Intel Motherboard]]<br />
<br />
** This motherboard seems to work but I got a ton of "rtc: lost some interrupts at 1024Hz" in Syslog and no one seems to know why...<br />
<br />
<br />
* µATX<br />
<br />
* 4x DDR2 Slot<br />
<br />
* GF 7600<br />
<br />
* onboard 5.1 Audio<br />
<br />
* 1x Gigabit Marvell LAN<br />
<br />
* 1x PCI-E 16x<br />
<br />
* 2x PCI-E 1x<br />
<br />
* 1x PCI<br />
<br />
==== RAM ====<br />
<br />
2GB Infineon CL5<br />
<br />
==== STORAGE ====<br />
Western Digital Caviar SE16 WD2500KS 250GB 7200 RPM SATA 3.0Gb/s Hard Drive - OEM <br />
<br />
<br />
==== PSU ====<br />
<br />
<br />
<br />
==== CASE ====<br />
<br />
Enermax<br />
<br />
<br />
==== OTHER ====<br />
<br />
CPU-FAN: <br />
<br />
<br />
== '''Media Directors''' ==<br />
<br />
none so far<br />
<br />
<br />
<br />
= '''Automation''' =<br />
<br />
none so far</div>Unihttp://wiki.linuxmce.org/index.php?title=User:UNi&diff=18342User:UNi2009-04-07T22:59:00Z<p>Uni: </p>
<hr />
<div>[[Category:User Setups]]<br />
<br />
= '''About Me''' =<br />
<br />
I've been working with OpenBSD for 10 years, but never delved into X-Windows as I use OBSD mainly for LAMP functions. I live in Northern California (NorCAL) and work as a Network Engineer. <br />
<br />
<br />
= '''LinuxMCE''' =<br />
<br />
After experimenting with LMCE, I'm not convinced that Linux is more stable than Windows as I've had multiple crashes and weirdness going on with this product. I've finally got it stabilized somewhat after killing a few Processes that run by default, namely Motion / motion + and ScreenSaver.<br />
<br />
<br />
== '''Next Steps''' ==<br />
<br />
<br />
<br />
* setup a MD after I'm sure the Core is stable and maybe wait until 810 before investing any more moola<br />
<br />
<br />
= '''Configuration''' =<br />
<br />
<br />
== '''Core''' ==<br />
<br />
<br />
<br />
<br />
=== Components: ===<br />
<br />
<br />
==== CPU ====<br />
<br />
Intel Dual-Core<br />
<br />
==== MOTHERBOARD ====<br />
<br />
[[ASUS P5NSLI LGA 775 NVIDIA nForce 570 SLI Intel Edition ATX Intel Motherboard]]<br />
<br />
** This motherboard seems to work but I got a ton of "rtc: lost some interrupts at 1024Hz" in Syslog and no one seems to know why...<br />
<br />
<br />
* µATX<br />
<br />
* 4x DDR2 Slot<br />
<br />
* GF 7600<br />
<br />
* onboard 5.1 Audio<br />
<br />
* 1x Gigabit Marvell LAN<br />
<br />
* 1x PCI-E 16x<br />
<br />
* 2x PCI-E 1x<br />
<br />
* 1x PCI<br />
<br />
==== RAM ====<br />
<br />
2GB Infineon CL5<br />
<br />
==== STORAGE ====<br />
Western Digital Caviar SE16 WD2500KS 250GB 7200 RPM SATA 3.0Gb/s Hard Drive - OEM <br />
<br />
<br />
==== PSU ====<br />
<br />
<br />
<br />
==== CASE ====<br />
<br />
Enermax<br />
<br />
<br />
==== OTHER ====<br />
<br />
CPU-FAN: <br />
<br />
<br />
== '''Media Directors''' ==<br />
<br />
none so far<br />
<br />
<br />
<br />
= '''Automation''' =<br />
<br />
none so far</div>Unihttp://wiki.linuxmce.org/index.php?title=User:UNi&diff=18341User:UNi2009-04-07T22:57:23Z<p>Uni: </p>
<hr />
<div>[[Category:User Setups]]<br />
<br />
= '''About Me''' =<br />
<br />
I've been working with OpenBSD for 10 years, but never delved into X-Windows as I use OBSD mainly for LAMP functions. I live in Northern California (NorCAL) and work as a Network Engineer. <br />
<br />
<br />
= '''LinuxMCE''' =<br />
<br />
After experimenting with LMCE, I'm not convinced that Linux is more stable than Windows as I've had multiple crashes and weirdness going on with this product. I've finally got it stabilized somewhat after killing a few Processes that run by default, namely Motion / motion + and ScreenSaver.<br />
<br />
<br />
== '''Next Steps''' ==<br />
<br />
<br />
<br />
* setup a MD after I'm sure the Core is stable and maybe wait until 810 before investing any more moola<br />
<br />
<br />
= '''Configuration''' =<br />
<br />
<br />
== '''Core''' ==<br />
<br />
<br />
<br />
<br />
=== Components: ===<br />
<br />
<br />
==== CPU ====<br />
<br />
Intel Dual-Core<br />
<br />
==== MOTHERBOARD ====<br />
<br />
[[ASUS P5NSLI LGA 775 NVIDIA nForce 570 SLI Intel Edition ATX Intel Motherboard]]<br />
<br />
* µATX<br />
<br />
* 4x DDR2 Slot<br />
<br />
* GF 7600<br />
<br />
* onboard 5.1 Audio<br />
<br />
* 1x Gigabit Marvell LAN<br />
<br />
* 1x PCI-E 16x<br />
<br />
* 2x PCI-E 1x<br />
<br />
* 1x PCI<br />
<br />
==== RAM ====<br />
<br />
2GB Infineon CL5<br />
<br />
==== STORAGE ====<br />
Western Digital Caviar SE16 WD2500KS 250GB 7200 RPM SATA 3.0Gb/s Hard Drive - OEM <br />
<br />
<br />
==== PSU ====<br />
<br />
<br />
<br />
==== CASE ====<br />
<br />
Enermax<br />
<br />
<br />
==== OTHER ====<br />
<br />
CPU-FAN: <br />
<br />
<br />
== '''Media Directors''' ==<br />
<br />
none so far<br />
<br />
<br />
<br />
= '''Automation''' =<br />
<br />
none so far</div>Unihttp://wiki.linuxmce.org/index.php?title=User:UNi&diff=18340User:UNi2009-04-07T22:56:06Z<p>Uni: </p>
<hr />
<div>[[Category:User Setups]]<br />
<br />
= '''About Me''' =<br />
<br />
I've been working with OpenBSD for 10 years, but never delved into X-Windows as I use OBSD mainly for LAMP functions. I live in Northern California (NorCAL) and work as a Network Engineer. <br />
<br />
<br />
= '''LinuxMCE''' =<br />
<br />
After experimenting with LMCE, I'm not convinced that Linux is more stable than Windows as I've had multiple crashes and weirdness going on with this product. I've finally got it stabilized somewhat after killing a few Processes that run by default, namely Motion / motion + and ScreenSaver.<br />
<br />
<br />
== Next Steps ==<br />
<br />
<br />
<br />
* setup a MD after I'm sure the Core is stable and maybe wait until 810 before investing any more moola<br />
<br />
<br />
= '''Configuration''' =<br />
<br />
<br />
== '''Core''' ==<br />
<br />
<br />
<br />
<br />
=== Components: ===<br />
<br />
<br />
==== CPU ====<br />
<br />
Intel Dual-Core<br />
<br />
==== MOTHERBOARD ====<br />
<br />
[[ASUS P5NSLI LGA 775 NVIDIA nForce 570 SLI Intel Edition ATX Intel Motherboard]]<br />
<br />
* µATX<br />
<br />
* 4x DDR2 Slot<br />
<br />
* GF 7600<br />
<br />
* onboard 5.1 Audio<br />
<br />
* 1x Gigabit Marvell LAN<br />
<br />
* 1x PCI-E 16x<br />
<br />
* 2x PCI-E 1x<br />
<br />
* 1x PCI<br />
<br />
==== RAM ====<br />
<br />
2GB Infineon CL5<br />
<br />
==== STORAGE ====<br />
Western Digital Caviar SE16 WD2500KS 250GB 7200 RPM SATA 3.0Gb/s Hard Drive - OEM <br />
<br />
<br />
==== PSU ====<br />
<br />
<br />
<br />
==== CASE ====<br />
<br />
Enermax<br />
<br />
<br />
==== OTHER ====<br />
<br />
CPU-FAN: <br />
<br />
<br />
== '''Media Directors''' ==<br />
<br />
none so far<br />
<br />
<br />
<br />
= '''Automation''' =<br />
<br />
none so far</div>Unihttp://wiki.linuxmce.org/index.php?title=User:UNi&diff=18339User:UNi2009-04-07T22:50:20Z<p>Uni: </p>
<hr />
<div>[[Category:User Setups]]<br />
<br />
<br />
= '''About Me''' =<br />
<br />
I've been working with OpenBSD for 10 years, but never delved into X-Windows as I use OBSD mainly for LAMP functions. I live in Northern California (NorCAL) and work as a Network Engineer.<br />
<br />
<br />
<br />
= '''LinuxMCE:''' =<br />
<br />
After experimenting with LMCE, I'm not convinced that Linux is more stable than Windows as I've had multiple crashes and weirdness going on with this product. I've finally got it stabilized somewhat after killing a few Processes that run by default, namely Motion / motion + and ScreenSaver. <br />
<br />
<br />
= '''Configuration:''' =<br />
<br />
Core<br />
<br />
<br />
= '''Components:''' =<br />
<br />
CPU<br />
<br />
<br />
MOTHERBOARD<br />
<br />
ASUS P5NSLI LGA 775 NVIDIA nForce 570 SLI Intel Edition ATX Intel Motherboard <br />
<br />
* µATX <br />
<br />
* 4x DDR2 Slot <br />
<br />
* onboard 5.1 Audio <br />
<br />
* 1x Gigabit Marvell LAN <br />
<br />
* 1x PCI-E 16x <br />
<br />
* 2x PCI-E 1x <br />
<br />
* 1x PCI <br />
<br />
RAM<br />
<br />
2GB Infineon CL5<br />
<br />
STORAGE<br />
<br />
Western Digital Caviar SE16 WD2500KS 250GB 7200 RPM SATA 3.0Gb/s Hard Drive - OEM<br />
<br />
PSU<br />
<br />
<br />
CASE<br />
<br />
<br />
OTHER<br />
<br />
<br />
<br />
Media Directors<br />
<br />
none so far<br />
<br />
<br />
Automation<br />
<br />
none so far</div>Unihttp://wiki.linuxmce.org/index.php?title=User:UNi&diff=18338User:UNi2009-04-07T22:47:38Z<p>Uni: </p>
<hr />
<div>[[Category:User Setups]]<br />
<br />
Contents<br />
[hide]<br />
<br />
* 1 About Me<br />
* 2 LinuxMCE and me<br />
o 2.1 Next Steps<br />
* 3 Configuration<br />
o 3.1 Core<br />
+ 3.1.1 Components:<br />
# 3.1.1.1 CPU<br />
# 3.1.1.2 MOTHERBOARD<br />
# 3.1.1.3 RAM<br />
# 3.1.1.4 STORAGE<br />
# 3.1.1.5 PSU<br />
# 3.1.1.6 CASE<br />
# 3.1.1.7 OTHER<br />
o 3.2 Media Directors<br />
* 4 Automation<br />
<br />
= '''About Me''' =<br />
<br />
I've been working with OpenBSD for 10 years, but never delved into X-Windows as I use OBSD mainly for LAMP functions. I live in Northern California (NorCAL) and work as a Network Engineer.<br />
<br />
<br />
<br />
LinuxMCE:<br />
<br />
After experimenting with LMCE, I'm not convinced that Linux is more stable than Windows as I've had multiple crashes and weirdness going on with this product. I've finally got it stabilized somewhat after killing a few Processes that run by default, namely Motion / motion + and ScreenSaver. <br />
<br />
<br />
Configuration:<br />
<br />
Core<br />
<br />
<br />
Components:<br />
<br />
CPU<br />
<br />
<br />
MOTHERBOARD<br />
<br />
ASUS P5NSLI LGA 775 NVIDIA nForce 570 SLI Intel Edition ATX Intel Motherboard <br />
<br />
* µATX <br />
<br />
* 4x DDR2 Slot <br />
<br />
* onboard 5.1 Audio <br />
<br />
* 1x Gigabit Marvell LAN <br />
<br />
* 1x PCI-E 16x <br />
<br />
* 2x PCI-E 1x <br />
<br />
* 1x PCI <br />
<br />
RAM<br />
<br />
2GB Infineon CL5<br />
<br />
STORAGE<br />
<br />
Western Digital Caviar SE16 WD2500KS 250GB 7200 RPM SATA 3.0Gb/s Hard Drive - OEM<br />
<br />
PSU<br />
<br />
<br />
CASE<br />
<br />
<br />
OTHER<br />
<br />
<br />
<br />
Media Directors<br />
<br />
none so far<br />
<br />
<br />
Automation<br />
<br />
none so far</div>Unihttp://wiki.linuxmce.org/index.php?title=User:UNi&diff=18337User:UNi2009-04-07T22:46:25Z<p>Uni: </p>
<hr />
<div><br />
[[Category:User Setups]]<br />
<br />
Contents<br />
[hide]<br />
<br />
* 1 About Me<br />
* 2 LinuxMCE and me<br />
o 2.1 Next Steps<br />
* 3 Configuration<br />
o 3.1 Core<br />
+ 3.1.1 Components:<br />
# 3.1.1.1 CPU<br />
# 3.1.1.2 MOTHERBOARD<br />
# 3.1.1.3 RAM<br />
# 3.1.1.4 STORAGE<br />
# 3.1.1.5 PSU<br />
# 3.1.1.6 CASE<br />
# 3.1.1.7 OTHER<br />
o 3.2 Media Directors<br />
* 4 Automation<br />
<br />
About Me<br />
<br />
I've been working with OpenBSD for 10 years, but never delved into X-Windows as I use OBSD mainly for LAMP functions. I live in Northern California (NorCAL) and work as a Network Engineer.<br />
<br />
<br />
<br />
LinuxMCE:<br />
<br />
After experimenting with LMCE, I'm not convinced that Linux is more stable than Windows as I've had multiple crashes and weirdness going on with this product. I've finally got it stabilized somewhat after killing a few Processes that run by default, namely Motion / motion + and ScreenSaver. <br />
<br />
<br />
Configuration:<br />
<br />
Core<br />
<br />
<br />
Components:<br />
<br />
CPU<br />
<br />
<br />
MOTHERBOARD<br />
<br />
ASUS P5NSLI LGA 775 NVIDIA nForce 570 SLI Intel Edition ATX Intel Motherboard <br />
<br />
* µATX <br />
<br />
* 4x DDR2 Slot <br />
<br />
* onboard 5.1 Audio <br />
<br />
* 1x Gigabit Marvell LAN <br />
<br />
* 1x PCI-E 16x <br />
<br />
* 2x PCI-E 1x <br />
<br />
* 1x PCI <br />
<br />
RAM<br />
<br />
2GB Infineon CL5<br />
<br />
STORAGE<br />
<br />
Western Digital Caviar SE16 WD2500KS 250GB 7200 RPM SATA 3.0Gb/s Hard Drive - OEM<br />
<br />
PSU<br />
<br />
<br />
CASE<br />
<br />
<br />
OTHER<br />
<br />
<br />
<br />
Media Directors<br />
<br />
none so far<br />
<br />
<br />
Automation<br />
<br />
none so far</div>Unihttp://wiki.linuxmce.org/index.php?title=User:UNi&diff=18336User:UNi2009-04-07T22:44:06Z<p>Uni: </p>
<hr />
<div>Contents<br />
[hide]<br />
<br />
* 1 About Me<br />
* 2 LinuxMCE and me<br />
o 2.1 Next Steps<br />
* 3 Configuration<br />
o 3.1 Core<br />
+ 3.1.1 Components:<br />
# 3.1.1.1 CPU<br />
# 3.1.1.2 MOTHERBOARD<br />
# 3.1.1.3 RAM<br />
# 3.1.1.4 STORAGE<br />
# 3.1.1.5 PSU<br />
# 3.1.1.6 CASE<br />
# 3.1.1.7 OTHER<br />
o 3.2 Media Directors<br />
* 4 Automation<br />
<br />
About Me<br />
<br />
I've been working with OpenBSD for 10 years, but never delved into X-Windows as I use OBSD mainly for LAMP functions. I live in Northern California (NorCAL) and work as a Network Engineer.<br />
<br />
<br />
<br />
LinuxMCE and me<br />
<br />
After experimenting with LMCE, I'm not convinced that Linux is more stable than Windows as I've had multiple crashes and weirdness going on with this product. I've finally got it stabilized somewhat after killing a few Processes that run by default, namely Motion / motion + and ScreenSaver. <br />
<br />
<br />
Configuration<br />
Core<br />
<br />
<br />
Components:<br />
CPU<br />
<br />
<br />
MOTHERBOARD<br />
<br />
ASUS P5NSLI LGA 775 NVIDIA nForce 570 SLI Intel Edition ATX Intel Motherboard <br />
<br />
* µATX <br />
<br />
* 4x DDR2 Slot <br />
<br />
* onboard 5.1 Audio <br />
<br />
* 1x Gigabit Marvell LAN <br />
<br />
* 1x PCI-E 16x <br />
<br />
* 2x PCI-E 1x <br />
<br />
* 1x PCI <br />
<br />
RAM<br />
<br />
2GB Infineon CL5<br />
<br />
STORAGE<br />
<br />
Western Digital Caviar SE16 WD2500KS 250GB 7200 RPM SATA 3.0Gb/s Hard Drive - OEM<br />
<br />
PSU<br />
<br />
<br />
CASE<br />
<br />
<br />
OTHER<br />
<br />
<br />
<br />
Media Directors<br />
<br />
none so far<br />
<br />
<br />
Automation<br />
<br />
none so far</div>Unihttp://wiki.linuxmce.org/index.php?title=User:UNi&diff=18335User:UNi2009-04-07T22:42:29Z<p>Uni: New page: Contents [hide] * 1 About Me * 2 LinuxMCE and me o 2.1 Next Steps * 3 Configuration o 3.1 Core + 3.1.1 Components: #...</p>
<hr />
<div><br />
Contents<br />
[hide]<br />
<br />
* 1 About Me<br />
* 2 LinuxMCE and me<br />
o 2.1 Next Steps<br />
* 3 Configuration<br />
o 3.1 Core<br />
+ 3.1.1 Components:<br />
# 3.1.1.1 CPU<br />
# 3.1.1.2 MOTHERBOARD<br />
# 3.1.1.3 RAM<br />
# 3.1.1.4 STORAGE<br />
# 3.1.1.5 PSU<br />
# 3.1.1.6 CASE<br />
# 3.1.1.7 OTHER<br />
o 3.2 Media Directors<br />
* 4 Automation<br />
<br />
About Me<br />
<br />
I've been working with OpenBSD for 10 years, but never delved into X-Windows as I use OBSD mainly for LAMP functions. I live in Northern California (NorCAL) and work as a Network Engineer.<br />
<br />
<br />
<br />
LinuxMCE and me<br />
<br />
After experimenting with LMCE, I'm not convinced that Linux is more stable than Windows as I've had multiple crashes and weirdness going on with this product. I've finally got it stabilized somewhat after killing a few Processes that run by default, namely Motion / motion + and ScreenSaver. <br />
<br />
<br />
Configuration<br />
Core<br />
<br />
<br />
Components:<br />
CPU<br />
<br />
<br />
MOTHERBOARD<br />
<br />
ASUS P5NSLI LGA 775 NVIDIA nForce 570 SLI Intel Edition ATX Intel Motherboard <br />
<br />
* µATX <br />
<br />
* 4x DDR2 Slot <br />
<br />
* onboard 5.1 Audio <br />
<br />
* 1x Gigabit Marvell LAN <br />
<br />
* 1x PCI-E 16x <br />
<br />
* 2x PCI-E 1x <br />
<br />
* 1x PCI <br />
<br />
RAM<br />
<br />
2GB Infineon CL5<br />
<br />
STORAGE<br />
<br />
Western Digital Caviar SE16 WD2500KS 250GB 7200 RPM SATA 3.0Gb/s Hard Drive - OEM<br />
<br />
PSU<br />
<br />
<br />
CASE<br />
<br />
<br />
OTHER<br />
<br />
<br />
<br />
Media Directors<br />
<br />
none so far<br />
<br />
<br />
Automation<br />
<br />
none so far</div>Unihttp://wiki.linuxmce.org/index.php?title=Display_Drivers&diff=18275Display Drivers2009-04-02T17:09:11Z<p>Uni: /* Latest Drivers */</p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
[[Category: Tutorials]]<br />
[[Category: Hardware| ]]<br />
<br />
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.<br />
<br />
'''Note that this should normally not be necessary unless you have specific wishes or trouble getting your display to work properly.''' <br />
<br />
== Installation ==<br />
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.<br />
<br />
=== ATI Chipsets ===<br />
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].<br />
<br />
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.<br />
<br />
==== Installing The ATI Driver ====<br />
<br />
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.<br />
<br />
'''Step 1'''<br />
<br />
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'.<br />
<br />
'''Step 2'''<br />
<br />
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;<br />
<br />
sudo su - <return><br />
ssh moonNN <return> (**where the NN is the device number for the MD we're configuring**)<br />
<br />
Alternatively do the following from the MD/Core you are configuring;<br />
<br />
Ctrl+Alt+2<br />
<br />
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;<br />
<br />
Firstly make sure our sources.list is up to date:<br />
<br />
apt-get update <return><br />
<br />
Now lets install the ATI driver and packages;<br />
<br />
apt-get install linux-restricted-modules-generic restricted-manager <return><br />
<br />
Answer 'Y' to installing new packages then do the following steps;<br />
<br />
apt-get install xorg-driver-fglrx <return><br />
depmod -a <return><br />
<br />
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;<br />
<br />
I use the console text editor 'joe' below but you can use whichever you prefer ('nano' is installed by default for example);<br />
<br />
joe /etc/X11/xorg.conf <return><br />
<br />
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;<br />
<br />
Driver "vesa"<br />
or<br />
Driver "ati"<br />
<br />
Change the string 'vesa' (or ati) to 'fglrx' which is the name of the ATI driver. The updated driver line should look like below;<br />
<br />
Driver "fglrx"<br />
<br />
Now save the changes you have made to xorg.conf.<br />
<br />
Now reboot the MD from the console with;<br />
<br />
reboot <return><br />
<br />
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.<br />
<br />
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.<br />
<br />
=== NVidia Chipsets ===<br />
<br />
==== Bugs ====<br />
If you are here, trying to update your driver because video is not working, remember that there is a bug with some Nvidia cards that makes graphical output always appear on the DVI plug, not the VGA plug. If you have a display attached to the VGA port on your adapter, buy a DVI to VGA converter plug before putting yourself through a lot of pain!<br />
<br />
==== Legacy Drivers ====<br />
With legacy drivers the AVWizard might crash because it could not load the nvidia-legacy kernel module. It is unclear why kdm will start and not the AVWizard. A quick fix is to set the '''Driver''' option for the video card in the ''/etc/X11/xorg.conf'' file to '''vesa'''. Go through the AVWizard and then change it back. Another option is to edit ''/etc/modprobe.d/aliases'' and add '''alias nvidia nvidia-legacy'''. Don't forget about this line when you switch to a newer card.<br />
<br />
==== Latest Drivers ====<br />
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. <br />
<br />
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. <br />
'''<you>@dcerouter:~$''' sudo -s<br />
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:<br />
'''root@dcerouter:~#''' wget <nowiki>http://us.download.nvidia.com/XFree86/Linux-x86/</nowiki>''<version>''<nowiki>/NVIDIA-Linux-x86-</nowiki>''<version>''<nowiki>-pkg1.run</nowiki><br />
3. Go to runlevel 1 to stop the currently running X-server. <br />
'''root@dcerouter:~#''' telinit 1 <br />
4. Execute the installer and follow instructions. a) Ignore the warning about runlevel 1 and b) don't bother looking for "precompiled kernel interfaces" (drivers).<br />
'''root@dcerouter:~#''' sh NVIDIA-Linux-x86-''<version>''-pkg1.run<br />
5. The installer will attempt to remove old legacy drivers. If it cannot, you may receive X errors (Eg. ''Error: API mismatch''). The solution is to manually remove or disable the legacy drivers. <br />
'''nano /etc/default/linux-restricted-modules-common''' <br />
Disable the NVIDIA linux-restricted kernel modules (nvidia, nvidia_legacy) by changing the DISABLED_MODULES line to read:<br />
'''DISABLED_MODULES="nv nvidia_new"'''<br />
6. 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.<br />
<br />
''** Update - Do a "sudo cat /proc/driver/nvidia/version" and make sure it reads something similar to this, matching the newest drivers you just installed: NVIDIA UNIX x86 Kernel Module 180.29. The "nvclock" utility is useful for monitoring GPU overheating''<br />
<br />
==== Media Directors ====<br />
Instructions for installing the latest nVidia driver on your media directors can be found in the [[Upgrading the Kernel#Video Drivers|upgrading the kernel]] wiki.<br />
<br />
=== Intel Chipsets ===<br />
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.<br />
<br />
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.<br />
<br />
==== For LinuxMCE-0704 ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
From man i810:<br />
Option "LinearAlloc" "integer"<br />
Allows more memory for the offscreen allocator. This usually<br />
helps in situations where HDTV movies are required to play but<br />
not enough offscreen memory is usually available. Set this to<br />
8160 for upto 1920x1080 HDTV support. Default 0KB (off).<br />
<br />
==== potential problem ====<br />
<br />
there can be a problem with some intel drivers, like the gma 3100. see [[bug/gma3100driver]] for further informations<br />
<br />
=== Via Chipsets ===<br />
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]<br />
<br />
The proprietary Via Unichrome driver works best with Linux MCE. Unfortunately this driver has intentionally been stripped of support for most GLX extensions. This driver does not support alpha blending which is a prerequisite of [[UI2]]. Via licenses the full featured driver to system integrators, such as [[Fiire]]. This licensed driver is not publicly available. Additionally there is a known incompatibility issue with the licensed driver and Linux MCE 0710. <br />
<br />
On April 08, 2008 Via announced a new open source initiative to help develop open drivers for certain video chipsets [http://www.phoronix.com/scan.php?page=article&item=via_oss&num=1]. This press release echos sour notes with many developers who have heard this tune many times before. No useful information or code has been released to date, striking yet another all to familiar chord in the open source community [http://www.phoronix.com/scan.php?page=article&item=via_bluff&num=1].<br />
<br />
'''HOW-TO VIA Openchrome driver for xorg:'''<br><br />
For VIA CX700M2 UniChrome PRO II Graphics (1" VIA units) or mainly via graphics:<br><br />
<br />
''shell into your box and do the following:''<br><br />
apt-get -y 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 subversion xserver-xorg-dev libdrm-dev libxvmc-dev<br />
<br />
cd /usr/src<br />
svn checkout http://svn.openchrome.org/svn/trunk openchrome<br />
cd openchrome*<br />
./autogen.sh --prefix=/usr<br />
make<br />
make install<br />
<br />
Now we have to edit /etc/X11/xorg.conf and change the device driver to via openchrome:<br><br />
vi /etc/X11/xorg.conf<br />
Go to<br />
Section "Device"<br />
and change<br />
Driver "vesa" <br />
to<br />
Driver "openchrome"<br />
save and test the compiled new driver with a: <br><br />
X :1<br />
and if your xwindow comes up, you can reboot and have fun<br><br />
<br />
=== Other Chipsets ===<br />
Please help out by adding more if you can.<br />
<br />
== Configuration ==<br />
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.<br />
<br />
=== Getting started ===<br />
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. <br />
<br />
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:<br />
telinit 1<br />
This wil stop the running X-server and drop you into rescue mode as well. <br />
<br />
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.<br />
<br />
=== Generating a template ===<br />
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. <br />
<br />
'''While there is no (other) X-server running''' you can create a template configuration file by running:<br />
X -configure<br />
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:<br />
X -config ~/xorg.conf.new<br />
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). <br />
<br />
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.<br />
<br />
Here is an example of such a generated file:<br />
<br />
Section "ServerLayout"<br />
Identifier "X.org Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Mouse0" "CorePointer"<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/etc/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/X11/misc"<br />
FontPath "/usr/X11R6/lib/X11/fonts/misc"<br />
FontPath "/usr/share/fonts/X11/cyrillic"<br />
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/Type1"<br />
FontPath "/usr/X11R6/lib/X11/fonts/Type1"<br />
FontPath "/usr/share/fonts/X11/100dpi"<br />
FontPath "/usr/share/fonts/X11/75dpi"<br />
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "extmod"<br />
Load "record"<br />
Load "xtrap"<br />
Load "dri"<br />
Load "glx"<br />
Load "dbe"<br />
Load "GLcore"<br />
Load "type1"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Keyboard0"<br />
Driver "kbd"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Mouse0"<br />
Driver "mouse"<br />
Option "Protocol" "auto"<br />
Option "Device" "/dev/input/mice"<br />
Option "ZAxisMapping" "4 5 6 7"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
EndSection<br />
<br />
Section "Device"<br />
### Available Driver options are:-<br />
### Values: &lt;i&gt;: integer, <f>: float, <bool>: "True"/"False",<br />
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"<br />
### [arg]: arg optional<br />
#Option "ShadowFB" # [<bool>]<br />
#Option "DefaultRefresh" # [<bool>]<br />
#Option "ModeSetClearScreen" # [<bool>]<br />
Identifier "Card0"<br />
Driver "vesa"<br />
''VendorName "ATI Technologies Inc"''<br />
''BoardName "ATI Radeon Xpress 1200 Series"''<br />
''BusID '''"PCI:1:5:0"'''''<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 1<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 4<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 8<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 15<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 16<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
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:<br />
X -scanpci<br />
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.<br />
<br />
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.<br />
<br />
=== Refresh rate / ModeLine ===<br />
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:<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
''HorizSync '''27-102''' # kHz''<br />
''VertRefresh '''50-160''' # Hz''<br />
EndSection<br />
<br />
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. <br />
<br />
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. <br />
* http://koala.ilog.fr/cgi-bin/nph-colas-modelines<br />
* http://xtiming.sourceforge.net/cgi-bin/xtiming.pl<br />
* http://www.bohne-lang.de/spec/linux/modeline/<br />
* http://amlc.berlios.de/<br />
* http://www.mythtv.org/wiki/index.php/Working_with_Modelines<br />
If one modeline doesn't work perfectly, try another, perhaps from another generator, because they can vary so much.<br />
<br />
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]-[&larr;Backspace] and readjust your settings. Most modern screens however simply report that the signal is out of range if this happens.<br />
<br />
=== Colordepth and resolution ===<br />
Specify the colordepth and resolution(s) you would like to use, like this:<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
''DefaultDepth '''24'''''<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
''Virtual '''1600 1200'''''<br />
''Modes '''"1600x1200" "1280x1024" "1024x768" "800x600" "640x480" "512x384" "400x300" "320x240"'''''<br />
EndSubSection<br />
EndSection<br />
<br />
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.<br />
<br />
=== DRI device permissions ===<br />
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.<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
<br />
=== Chipset driver ===<br />
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''').<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
''# Driver "'''vesa'''"''<br />
''Driver "'''fglrx'''"''<br />
VendorName "ATI Technologies Inc"<br />
BoardName "ATI Radeon Xpress 1200 Series"<br />
BusID "PCI:1:5:0"<br />
EndSection<br />
<br />
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.<br />
<br />
=== Physical display size ===<br />
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.<br />
<br />
Section "Monitor"<br />
...<br />
DisplaySize '''155 95'''<br />
EndSection<br />
<br />
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.<br />
<br />
=== Disable composite ===<br />
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.<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
EndSection<br />
<br />
=== Additional options ===<br />
To be continued, I don't think this is enough to get UI2 completely (either mode) going yet. Feel free to jump in anytime... <br />
<br />
<br />
Things still to sort out amongst others (i.e. what is it, do we need it and what are the settings if any):<br />
<br />
Section "Module"<br />
Load "i2c"<br />
Load "bitmap"<br />
Load "ddc"<br />
Load "freetype"<br />
Load "int10"<br />
Load "vbe"<br />
Load "speedo"<br />
Load "type1"<br />
Load "dbe"<br />
Load "glx"<br />
Load "v4l"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AIGLX" "off"<br />
EndSection<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
# Option "RENDER" "true"<br />
EndSection<br />
<br />
Option "PseudoColorVisuals" "off"<br />
Option "OpenGLOverlay" "off"<br />
Option "VideoOverlay" "off"<br />
Option "DesktopSetup" "clone"<br />
<br />
TV-out options, 2nd display, etc.<br />
<br />
<br />
== Troubleshooting ==<br />
<br />
=== The AVWizard crashes X-windows ===<br />
<br />
Try setting the [[#Chipset_driver]] option to '''vesa''', run the AVWizard again and then change the driver back to what it was.<br />
<br />
=== Black screen ===<br />
<br />
* 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.<br />
<br />
*One problem on nvidia-cards could be that it does not detect the right monitor.<br />
<br />
::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><br />
::where XXX is CRT, CRT-0, CRT-1, DVI-0, DVI-1, ...<br />
::Save and exit (nano: Ctrl+x) and restart the computer. In my case it was "CRT-1".<br />
<br />
=== X-windows won't start ===<br />
<br />
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]-[&larr;Backspace] simultaneous to quit (alternative: use "startx" and get the full desktop, if any), then reboot when it works and you're done.<br />
<br />
=== Signal out of range ===<br />
<br />
See ''[[#Refresh rate / ModeLine ]]'' above.<br />
<br />
=== Microscopic fonts in KDE ===<br />
<br />
See ''[[#Physical_display_size]]'' above.<br />
<br />
If the above does not work, probably Xorg is calculating the DPI value in the wrong way.<br />
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.<br />
<br />
If those values are too small, fonts will be displayed accordingly (i.e, VERY small)<br />
<br />
A workaround is to force Xorg to startup with a given DPI value.<br />
<br />
To achieve this the following steps are required:<br />
<br />
* edit the file /usr/pluto/bin/Start_X_Wrapper.sh on your MD where you are facing the font problem<br />
* find the line beginning with xinit<br />
* add "-dpi 96" (without quotes) at the end of this line<br />
* save the file and reboot MD<br />
<br />
Obviously it is possible to set DPI to something different than 96, according to specific needs.<br />
<br />
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.<br />
<br />
=== LinuxMCE keeps reconfiguring my display settings ===<br />
<br />
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.<br />
<br />
For LinuxMCE 710 simply comment out the line that says<br />
. /usr/pluto/bin/X-CleanupVideo.sh<br />
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.<br />
<br />
== See also ==<br />
* [http://www.mythtv.org/wiki/index.php/Main_Page MythTV wiki] <br />
* MythTV Experience [http://brentlagesse.net/~brent/mythtv.php]<br />
* [[X_Configuration_Scripts]]</div>Unihttp://wiki.linuxmce.org/index.php?title=Display_Drivers&diff=18135Display Drivers2009-03-26T19:09:37Z<p>Uni: /* Latest Drivers */</p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
[[Category: Tutorials]]<br />
[[Category: Hardware| ]]<br />
<br />
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.<br />
<br />
'''Note that this should normally not be necessary unless you have specific wishes or trouble getting your display to work properly.''' <br />
<br />
== Installation ==<br />
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.<br />
<br />
=== ATI Chipsets ===<br />
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].<br />
<br />
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.<br />
<br />
==== Installing The ATI Driver ====<br />
<br />
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.<br />
<br />
'''Step 1'''<br />
<br />
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'.<br />
<br />
'''Step 2'''<br />
<br />
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;<br />
<br />
sudo su - <return><br />
ssh moonNN <return> (**where the NN is the device number for the MD we're configuring**)<br />
<br />
Alternatively do the following from the MD/Core you are configuring;<br />
<br />
Ctrl+Alt+2<br />
<br />
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;<br />
<br />
Firstly make sure our sources.list is up to date:<br />
<br />
apt-get update <return><br />
<br />
Now lets install the ATI driver and packages;<br />
<br />
apt-get install linux-restricted-modules-generic restricted-manager <return><br />
<br />
Answer 'Y' to installing new packages then do the following steps;<br />
<br />
apt-get install xorg-driver-fglrx <return><br />
depmod -a <return><br />
<br />
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;<br />
<br />
I use the console text editor 'joe' below but you can use whichever you prefer ('nano' is installed by default for example);<br />
<br />
joe /etc/X11/xorg.conf <return><br />
<br />
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;<br />
<br />
Driver "vesa"<br />
or<br />
Driver "ati"<br />
<br />
Change the string 'vesa' (or ati) to 'fglrx' which is the name of the ATI driver. The updated driver line should look like below;<br />
<br />
Driver "fglrx"<br />
<br />
Now save the changes you have made to xorg.conf.<br />
<br />
Now reboot the MD from the console with;<br />
<br />
reboot <return><br />
<br />
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.<br />
<br />
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.<br />
<br />
=== NVidia Chipsets ===<br />
<br />
==== Bugs ====<br />
If you are here, trying to update your driver because video is not working, remember that there is a bug with some Nvidia cards that makes graphical output always appear on the DVI plug, not the VGA plug. If you have a display attached to the VGA port on your adapter, buy a DVI to VGA converter plug before putting yourself through a lot of pain!<br />
<br />
==== Legacy Drivers ====<br />
With legacy drivers the AVWizard might crash because it could not load the nvidia-legacy kernel module. It is unclear why kdm will start and not the AVWizard. A quick fix is to set the '''Driver''' option for the video card in the ''/etc/X11/xorg.conf'' file to '''vesa'''. Go through the AVWizard and then change it back. Another option is to edit ''/etc/modprobe.d/aliases'' and add '''alias nvidia nvidia-legacy'''. Don't forget about this line when you switch to a newer card.<br />
<br />
==== Latest Drivers ====<br />
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. <br />
<br />
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. <br />
'''<you>@dcerouter:~$''' sudo -s<br />
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:<br />
'''root@dcerouter:~#''' wget <nowiki>http://us.download.nvidia.com/XFree86/Linux-x86/</nowiki>''<version>''<nowiki>/NVIDIA-Linux-x86-</nowiki>''<version>''<nowiki>-pkg1.run</nowiki><br />
3. Go to runlevel 1 to stop the currently running X-server. <br />
'''root@dcerouter:~#''' telinit 1 <br />
4. Execute the installer and follow instructions. a) Ignore the warning about runlevel 1 and b) don't bother looking for "precompiled kernel interfaces" (drivers).<br />
'''root@dcerouter:~#''' sh NVIDIA-Linux-x86-''<version>''-pkg1.run<br />
5. The installer will attempt to remove old legacy drivers. If it cannot, you may receive X errors (Eg. ''Error: API mismatch''). The solution is to manually remove or disable the legacy drivers. <br />
'''nano /etc/default/linux-restricted-modules-common''' <br />
Disable the NVIDIA linux-restricted kernel modules (nvidia, nvidia_legacy) by changing the DISABLED_MODULES line to read:<br />
'''DISABLED_MODULES="nv nvidia_new"'''<br />
6. 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.<br />
<br />
''** Update - You may experience your box hanging completely on the Xorg process (CPU at 100%) if you're using the older NVIDIA drivers. Do a "sudo cat /proc/driver/nvidia/version" and make sure it reads something similar to this, matching the newest drivers you just installed: NVIDIA UNIX x86 Kernel Module 180.29''<br />
<br />
==== Media Directors ====<br />
Instructions for installing the latest nVidia driver on your media directors can be found in the [[Upgrading the Kernel#Video Drivers|upgrading the kernel]] wiki.<br />
<br />
=== Intel Chipsets ===<br />
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.<br />
<br />
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.<br />
<br />
==== For LinuxMCE-0704 ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
From man i810:<br />
Option "LinearAlloc" "integer"<br />
Allows more memory for the offscreen allocator. This usually<br />
helps in situations where HDTV movies are required to play but<br />
not enough offscreen memory is usually available. Set this to<br />
8160 for upto 1920x1080 HDTV support. Default 0KB (off).<br />
<br />
==== potential problem ====<br />
<br />
there can be a problem with some intel drivers, like the gma 3100. see [[bug/gma3100driver]] for further informations<br />
<br />
=== Via Chipsets ===<br />
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]<br />
<br />
The proprietary Via Unichrome driver works best with Linux MCE. Unfortunately this driver has intentionally been stripped of support for most GLX extensions. This driver does not support alpha blending which is a prerequisite of [[UI2]]. Via licenses the full featured driver to system integrators, such as [[Fiire]]. This licensed driver is not publicly available. Additionally there is a known incompatibility issue with the licensed driver and Linux MCE 0710. <br />
<br />
On April 08, 2008 Via announced a new open source initiative to help develop open drivers for certain video chipsets [http://www.phoronix.com/scan.php?page=article&item=via_oss&num=1]. This press release echos sour notes with many developers who have heard this tune many times before. No useful information or code has been released to date, striking yet another all to familiar chord in the open source community [http://www.phoronix.com/scan.php?page=article&item=via_bluff&num=1].<br />
<br />
'''HOW-TO VIA Openchrome driver for xorg:'''<br><br />
For VIA CX700M2 UniChrome PRO II Graphics (1" VIA units) or mainly via graphics:<br><br />
<br />
''shell into your box and do the following:''<br><br />
apt-get -y 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 subversion xserver-xorg-dev libdrm-dev libxvmc-dev<br />
<br />
cd /usr/src<br />
svn checkout http://svn.openchrome.org/svn/trunk openchrome<br />
cd openchrome*<br />
./autogen.sh --prefix=/usr<br />
make<br />
make install<br />
<br />
Now we have to edit /etc/X11/xorg.conf and change the device driver to via openchrome:<br><br />
vi /etc/X11/xorg.conf<br />
Go to<br />
Section "Device"<br />
and change<br />
Driver "vesa" <br />
to<br />
Driver "openchrome"<br />
save and test the compiled new driver with a: <br><br />
X :1<br />
and if your xwindow comes up, you can reboot and have fun<br><br />
<br />
=== Other Chipsets ===<br />
Please help out by adding more if you can.<br />
<br />
== Configuration ==<br />
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.<br />
<br />
=== Getting started ===<br />
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. <br />
<br />
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:<br />
telinit 1<br />
This wil stop the running X-server and drop you into rescue mode as well. <br />
<br />
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.<br />
<br />
=== Generating a template ===<br />
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. <br />
<br />
'''While there is no (other) X-server running''' you can create a template configuration file by running:<br />
X -configure<br />
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:<br />
X -config ~/xorg.conf.new<br />
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). <br />
<br />
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.<br />
<br />
Here is an example of such a generated file:<br />
<br />
Section "ServerLayout"<br />
Identifier "X.org Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Mouse0" "CorePointer"<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/etc/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/X11/misc"<br />
FontPath "/usr/X11R6/lib/X11/fonts/misc"<br />
FontPath "/usr/share/fonts/X11/cyrillic"<br />
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/Type1"<br />
FontPath "/usr/X11R6/lib/X11/fonts/Type1"<br />
FontPath "/usr/share/fonts/X11/100dpi"<br />
FontPath "/usr/share/fonts/X11/75dpi"<br />
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "extmod"<br />
Load "record"<br />
Load "xtrap"<br />
Load "dri"<br />
Load "glx"<br />
Load "dbe"<br />
Load "GLcore"<br />
Load "type1"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Keyboard0"<br />
Driver "kbd"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Mouse0"<br />
Driver "mouse"<br />
Option "Protocol" "auto"<br />
Option "Device" "/dev/input/mice"<br />
Option "ZAxisMapping" "4 5 6 7"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
EndSection<br />
<br />
Section "Device"<br />
### Available Driver options are:-<br />
### Values: &lt;i&gt;: integer, <f>: float, <bool>: "True"/"False",<br />
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"<br />
### [arg]: arg optional<br />
#Option "ShadowFB" # [<bool>]<br />
#Option "DefaultRefresh" # [<bool>]<br />
#Option "ModeSetClearScreen" # [<bool>]<br />
Identifier "Card0"<br />
Driver "vesa"<br />
''VendorName "ATI Technologies Inc"''<br />
''BoardName "ATI Radeon Xpress 1200 Series"''<br />
''BusID '''"PCI:1:5:0"'''''<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 1<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 4<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 8<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 15<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 16<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
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:<br />
X -scanpci<br />
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.<br />
<br />
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.<br />
<br />
=== Refresh rate / ModeLine ===<br />
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:<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
''HorizSync '''27-102''' # kHz''<br />
''VertRefresh '''50-160''' # Hz''<br />
EndSection<br />
<br />
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. <br />
<br />
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. <br />
* http://koala.ilog.fr/cgi-bin/nph-colas-modelines<br />
* http://xtiming.sourceforge.net/cgi-bin/xtiming.pl<br />
* http://www.bohne-lang.de/spec/linux/modeline/<br />
* http://amlc.berlios.de/<br />
* http://www.mythtv.org/wiki/index.php/Working_with_Modelines<br />
If one modeline doesn't work perfectly, try another, perhaps from another generator, because they can vary so much.<br />
<br />
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]-[&larr;Backspace] and readjust your settings. Most modern screens however simply report that the signal is out of range if this happens.<br />
<br />
=== Colordepth and resolution ===<br />
Specify the colordepth and resolution(s) you would like to use, like this:<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
''DefaultDepth '''24'''''<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
''Virtual '''1600 1200'''''<br />
''Modes '''"1600x1200" "1280x1024" "1024x768" "800x600" "640x480" "512x384" "400x300" "320x240"'''''<br />
EndSubSection<br />
EndSection<br />
<br />
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.<br />
<br />
=== DRI device permissions ===<br />
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.<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
<br />
=== Chipset driver ===<br />
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''').<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
''# Driver "'''vesa'''"''<br />
''Driver "'''fglrx'''"''<br />
VendorName "ATI Technologies Inc"<br />
BoardName "ATI Radeon Xpress 1200 Series"<br />
BusID "PCI:1:5:0"<br />
EndSection<br />
<br />
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.<br />
<br />
=== Physical display size ===<br />
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.<br />
<br />
Section "Monitor"<br />
...<br />
DisplaySize '''155 95'''<br />
EndSection<br />
<br />
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.<br />
<br />
=== Disable composite ===<br />
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.<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
EndSection<br />
<br />
=== Additional options ===<br />
To be continued, I don't think this is enough to get UI2 completely (either mode) going yet. Feel free to jump in anytime... <br />
<br />
<br />
Things still to sort out amongst others (i.e. what is it, do we need it and what are the settings if any):<br />
<br />
Section "Module"<br />
Load "i2c"<br />
Load "bitmap"<br />
Load "ddc"<br />
Load "freetype"<br />
Load "int10"<br />
Load "vbe"<br />
Load "speedo"<br />
Load "type1"<br />
Load "dbe"<br />
Load "glx"<br />
Load "v4l"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AIGLX" "off"<br />
EndSection<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
# Option "RENDER" "true"<br />
EndSection<br />
<br />
Option "PseudoColorVisuals" "off"<br />
Option "OpenGLOverlay" "off"<br />
Option "VideoOverlay" "off"<br />
Option "DesktopSetup" "clone"<br />
<br />
TV-out options, 2nd display, etc.<br />
<br />
<br />
== Troubleshooting ==<br />
<br />
=== The AVWizard crashes X-windows ===<br />
<br />
Try setting the [[#Chipset_driver]] option to '''vesa''', run the AVWizard again and then change the driver back to what it was.<br />
<br />
=== Black screen ===<br />
<br />
* 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.<br />
<br />
*One problem on nvidia-cards could be that it does not detect the right monitor.<br />
<br />
::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><br />
::where XXX is CRT, CRT-0, CRT-1, DVI-0, DVI-1, ...<br />
::Save and exit (nano: Ctrl+x) and restart the computer. In my case it was "CRT-1".<br />
<br />
=== X-windows won't start ===<br />
<br />
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]-[&larr;Backspace] simultaneous to quit (alternative: use "startx" and get the full desktop, if any), then reboot when it works and you're done.<br />
<br />
=== Signal out of range ===<br />
<br />
See ''[[#Refresh rate / ModeLine ]]'' above.<br />
<br />
=== Microscopic fonts in KDE ===<br />
<br />
See ''[[#Physical_display_size]]'' above.<br />
<br />
If the above does not work, probably Xorg is calculating the DPI value in the wrong way.<br />
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.<br />
<br />
If those values are too small, fonts will be displayed accordingly (i.e, VERY small)<br />
<br />
A workaround is to force Xorg to startup with a given DPI value.<br />
<br />
To achieve this the following steps are required:<br />
<br />
* edit the file /usr/pluto/bin/Start_X_Wrapper.sh on your MD where you are facing the font problem<br />
* find the line beginning with xinit<br />
* add "-dpi 96" (without quotes) at the end of this line<br />
* save the file and reboot MD<br />
<br />
Obviously it is possible to set DPI to something different than 96, according to specific needs.<br />
<br />
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.<br />
<br />
=== LinuxMCE keeps reconfiguring my display settings ===<br />
<br />
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.<br />
<br />
For LinuxMCE 710 simply comment out the line that says<br />
. /usr/pluto/bin/X-CleanupVideo.sh<br />
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.<br />
<br />
== See also ==<br />
* [http://www.mythtv.org/wiki/index.php/Main_Page MythTV wiki] <br />
* MythTV Experience [http://brentlagesse.net/~brent/mythtv.php]<br />
* [[X_Configuration_Scripts]]</div>Unihttp://wiki.linuxmce.org/index.php?title=Display_Drivers&diff=18134Display Drivers2009-03-26T19:08:25Z<p>Uni: /* Latest Drivers */</p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
[[Category: Tutorials]]<br />
[[Category: Hardware| ]]<br />
<br />
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.<br />
<br />
'''Note that this should normally not be necessary unless you have specific wishes or trouble getting your display to work properly.''' <br />
<br />
== Installation ==<br />
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.<br />
<br />
=== ATI Chipsets ===<br />
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].<br />
<br />
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.<br />
<br />
==== Installing The ATI Driver ====<br />
<br />
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.<br />
<br />
'''Step 1'''<br />
<br />
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'.<br />
<br />
'''Step 2'''<br />
<br />
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;<br />
<br />
sudo su - <return><br />
ssh moonNN <return> (**where the NN is the device number for the MD we're configuring**)<br />
<br />
Alternatively do the following from the MD/Core you are configuring;<br />
<br />
Ctrl+Alt+2<br />
<br />
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;<br />
<br />
Firstly make sure our sources.list is up to date:<br />
<br />
apt-get update <return><br />
<br />
Now lets install the ATI driver and packages;<br />
<br />
apt-get install linux-restricted-modules-generic restricted-manager <return><br />
<br />
Answer 'Y' to installing new packages then do the following steps;<br />
<br />
apt-get install xorg-driver-fglrx <return><br />
depmod -a <return><br />
<br />
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;<br />
<br />
I use the console text editor 'joe' below but you can use whichever you prefer ('nano' is installed by default for example);<br />
<br />
joe /etc/X11/xorg.conf <return><br />
<br />
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;<br />
<br />
Driver "vesa"<br />
or<br />
Driver "ati"<br />
<br />
Change the string 'vesa' (or ati) to 'fglrx' which is the name of the ATI driver. The updated driver line should look like below;<br />
<br />
Driver "fglrx"<br />
<br />
Now save the changes you have made to xorg.conf.<br />
<br />
Now reboot the MD from the console with;<br />
<br />
reboot <return><br />
<br />
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.<br />
<br />
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.<br />
<br />
=== NVidia Chipsets ===<br />
<br />
==== Bugs ====<br />
If you are here, trying to update your driver because video is not working, remember that there is a bug with some Nvidia cards that makes graphical output always appear on the DVI plug, not the VGA plug. If you have a display attached to the VGA port on your adapter, buy a DVI to VGA converter plug before putting yourself through a lot of pain!<br />
<br />
==== Legacy Drivers ====<br />
With legacy drivers the AVWizard might crash because it could not load the nvidia-legacy kernel module. It is unclear why kdm will start and not the AVWizard. A quick fix is to set the '''Driver''' option for the video card in the ''/etc/X11/xorg.conf'' file to '''vesa'''. Go through the AVWizard and then change it back. Another option is to edit ''/etc/modprobe.d/aliases'' and add '''alias nvidia nvidia-legacy'''. Don't forget about this line when you switch to a newer card.<br />
<br />
==== Latest Drivers ====<br />
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. <br />
<br />
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. <br />
'''<you>@dcerouter:~$''' sudo -s<br />
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:<br />
'''root@dcerouter:~#''' wget <nowiki>http://us.download.nvidia.com/XFree86/Linux-x86/</nowiki>''<version>''<nowiki>/NVIDIA-Linux-x86-</nowiki>''<version>''<nowiki>-pkg1.run</nowiki><br />
3. Go to runlevel 1 to stop the currently running X-server. <br />
'''root@dcerouter:~#''' telinit 1 <br />
4. Execute the installer and follow instructions. a) Ignore the warning about runlevel 1 and b) don't bother looking for "precompiled kernel interfaces" (drivers).<br />
'''root@dcerouter:~#''' sh NVIDIA-Linux-x86-''<version>''-pkg1.run<br />
5. The installer will attempt to remove old legacy drivers. If it cannot, you may receive X errors (Eg. ''Error: API mismatch''). The solution is to manually remove or disable the legacy drivers. <br />
'''nano /etc/default/linux-restricted-modules-common''' <br />
Disable the NVIDIA linux-restricted kernel modules (nvidia, nvidia_legacy) by changing the DISABLED_MODULES line to read:<br />
'''DISABLED_MODULES="nv nvidia_new"'''<br />
6. 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.<br />
<br />
''Italic text''** Update - You may experience your box hanging completely on the Xorg process (CPU at 100%) if you're using the older drivers. Do a "sudo cat /proc/driver/nvidia/version" and make sure it reads something similar to this, matching the newest drivers you just installed: NVIDIA UNIX x86 Kernel Module 180.29<br />
<br />
==== Media Directors ====<br />
Instructions for installing the latest nVidia driver on your media directors can be found in the [[Upgrading the Kernel#Video Drivers|upgrading the kernel]] wiki.<br />
<br />
=== Intel Chipsets ===<br />
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.<br />
<br />
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.<br />
<br />
==== For LinuxMCE-0704 ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
From man i810:<br />
Option "LinearAlloc" "integer"<br />
Allows more memory for the offscreen allocator. This usually<br />
helps in situations where HDTV movies are required to play but<br />
not enough offscreen memory is usually available. Set this to<br />
8160 for upto 1920x1080 HDTV support. Default 0KB (off).<br />
<br />
==== potential problem ====<br />
<br />
there can be a problem with some intel drivers, like the gma 3100. see [[bug/gma3100driver]] for further informations<br />
<br />
=== Via Chipsets ===<br />
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]<br />
<br />
The proprietary Via Unichrome driver works best with Linux MCE. Unfortunately this driver has intentionally been stripped of support for most GLX extensions. This driver does not support alpha blending which is a prerequisite of [[UI2]]. Via licenses the full featured driver to system integrators, such as [[Fiire]]. This licensed driver is not publicly available. Additionally there is a known incompatibility issue with the licensed driver and Linux MCE 0710. <br />
<br />
On April 08, 2008 Via announced a new open source initiative to help develop open drivers for certain video chipsets [http://www.phoronix.com/scan.php?page=article&item=via_oss&num=1]. This press release echos sour notes with many developers who have heard this tune many times before. No useful information or code has been released to date, striking yet another all to familiar chord in the open source community [http://www.phoronix.com/scan.php?page=article&item=via_bluff&num=1].<br />
<br />
'''HOW-TO VIA Openchrome driver for xorg:'''<br><br />
For VIA CX700M2 UniChrome PRO II Graphics (1" VIA units) or mainly via graphics:<br><br />
<br />
''shell into your box and do the following:''<br><br />
apt-get -y 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 subversion xserver-xorg-dev libdrm-dev libxvmc-dev<br />
<br />
cd /usr/src<br />
svn checkout http://svn.openchrome.org/svn/trunk openchrome<br />
cd openchrome*<br />
./autogen.sh --prefix=/usr<br />
make<br />
make install<br />
<br />
Now we have to edit /etc/X11/xorg.conf and change the device driver to via openchrome:<br><br />
vi /etc/X11/xorg.conf<br />
Go to<br />
Section "Device"<br />
and change<br />
Driver "vesa" <br />
to<br />
Driver "openchrome"<br />
save and test the compiled new driver with a: <br><br />
X :1<br />
and if your xwindow comes up, you can reboot and have fun<br><br />
<br />
=== Other Chipsets ===<br />
Please help out by adding more if you can.<br />
<br />
== Configuration ==<br />
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.<br />
<br />
=== Getting started ===<br />
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. <br />
<br />
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:<br />
telinit 1<br />
This wil stop the running X-server and drop you into rescue mode as well. <br />
<br />
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.<br />
<br />
=== Generating a template ===<br />
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. <br />
<br />
'''While there is no (other) X-server running''' you can create a template configuration file by running:<br />
X -configure<br />
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:<br />
X -config ~/xorg.conf.new<br />
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). <br />
<br />
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.<br />
<br />
Here is an example of such a generated file:<br />
<br />
Section "ServerLayout"<br />
Identifier "X.org Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Mouse0" "CorePointer"<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/etc/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/X11/misc"<br />
FontPath "/usr/X11R6/lib/X11/fonts/misc"<br />
FontPath "/usr/share/fonts/X11/cyrillic"<br />
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/Type1"<br />
FontPath "/usr/X11R6/lib/X11/fonts/Type1"<br />
FontPath "/usr/share/fonts/X11/100dpi"<br />
FontPath "/usr/share/fonts/X11/75dpi"<br />
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "extmod"<br />
Load "record"<br />
Load "xtrap"<br />
Load "dri"<br />
Load "glx"<br />
Load "dbe"<br />
Load "GLcore"<br />
Load "type1"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Keyboard0"<br />
Driver "kbd"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Mouse0"<br />
Driver "mouse"<br />
Option "Protocol" "auto"<br />
Option "Device" "/dev/input/mice"<br />
Option "ZAxisMapping" "4 5 6 7"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
EndSection<br />
<br />
Section "Device"<br />
### Available Driver options are:-<br />
### Values: &lt;i&gt;: integer, <f>: float, <bool>: "True"/"False",<br />
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"<br />
### [arg]: arg optional<br />
#Option "ShadowFB" # [<bool>]<br />
#Option "DefaultRefresh" # [<bool>]<br />
#Option "ModeSetClearScreen" # [<bool>]<br />
Identifier "Card0"<br />
Driver "vesa"<br />
''VendorName "ATI Technologies Inc"''<br />
''BoardName "ATI Radeon Xpress 1200 Series"''<br />
''BusID '''"PCI:1:5:0"'''''<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 1<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 4<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 8<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 15<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 16<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
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:<br />
X -scanpci<br />
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.<br />
<br />
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.<br />
<br />
=== Refresh rate / ModeLine ===<br />
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:<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
''HorizSync '''27-102''' # kHz''<br />
''VertRefresh '''50-160''' # Hz''<br />
EndSection<br />
<br />
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. <br />
<br />
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. <br />
* http://koala.ilog.fr/cgi-bin/nph-colas-modelines<br />
* http://xtiming.sourceforge.net/cgi-bin/xtiming.pl<br />
* http://www.bohne-lang.de/spec/linux/modeline/<br />
* http://amlc.berlios.de/<br />
* http://www.mythtv.org/wiki/index.php/Working_with_Modelines<br />
If one modeline doesn't work perfectly, try another, perhaps from another generator, because they can vary so much.<br />
<br />
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]-[&larr;Backspace] and readjust your settings. Most modern screens however simply report that the signal is out of range if this happens.<br />
<br />
=== Colordepth and resolution ===<br />
Specify the colordepth and resolution(s) you would like to use, like this:<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
''DefaultDepth '''24'''''<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
''Virtual '''1600 1200'''''<br />
''Modes '''"1600x1200" "1280x1024" "1024x768" "800x600" "640x480" "512x384" "400x300" "320x240"'''''<br />
EndSubSection<br />
EndSection<br />
<br />
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.<br />
<br />
=== DRI device permissions ===<br />
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.<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
<br />
=== Chipset driver ===<br />
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''').<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
''# Driver "'''vesa'''"''<br />
''Driver "'''fglrx'''"''<br />
VendorName "ATI Technologies Inc"<br />
BoardName "ATI Radeon Xpress 1200 Series"<br />
BusID "PCI:1:5:0"<br />
EndSection<br />
<br />
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.<br />
<br />
=== Physical display size ===<br />
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.<br />
<br />
Section "Monitor"<br />
...<br />
DisplaySize '''155 95'''<br />
EndSection<br />
<br />
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.<br />
<br />
=== Disable composite ===<br />
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.<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
EndSection<br />
<br />
=== Additional options ===<br />
To be continued, I don't think this is enough to get UI2 completely (either mode) going yet. Feel free to jump in anytime... <br />
<br />
<br />
Things still to sort out amongst others (i.e. what is it, do we need it and what are the settings if any):<br />
<br />
Section "Module"<br />
Load "i2c"<br />
Load "bitmap"<br />
Load "ddc"<br />
Load "freetype"<br />
Load "int10"<br />
Load "vbe"<br />
Load "speedo"<br />
Load "type1"<br />
Load "dbe"<br />
Load "glx"<br />
Load "v4l"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AIGLX" "off"<br />
EndSection<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
# Option "RENDER" "true"<br />
EndSection<br />
<br />
Option "PseudoColorVisuals" "off"<br />
Option "OpenGLOverlay" "off"<br />
Option "VideoOverlay" "off"<br />
Option "DesktopSetup" "clone"<br />
<br />
TV-out options, 2nd display, etc.<br />
<br />
<br />
== Troubleshooting ==<br />
<br />
=== The AVWizard crashes X-windows ===<br />
<br />
Try setting the [[#Chipset_driver]] option to '''vesa''', run the AVWizard again and then change the driver back to what it was.<br />
<br />
=== Black screen ===<br />
<br />
* 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.<br />
<br />
*One problem on nvidia-cards could be that it does not detect the right monitor.<br />
<br />
::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><br />
::where XXX is CRT, CRT-0, CRT-1, DVI-0, DVI-1, ...<br />
::Save and exit (nano: Ctrl+x) and restart the computer. In my case it was "CRT-1".<br />
<br />
=== X-windows won't start ===<br />
<br />
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]-[&larr;Backspace] simultaneous to quit (alternative: use "startx" and get the full desktop, if any), then reboot when it works and you're done.<br />
<br />
=== Signal out of range ===<br />
<br />
See ''[[#Refresh rate / ModeLine ]]'' above.<br />
<br />
=== Microscopic fonts in KDE ===<br />
<br />
See ''[[#Physical_display_size]]'' above.<br />
<br />
If the above does not work, probably Xorg is calculating the DPI value in the wrong way.<br />
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.<br />
<br />
If those values are too small, fonts will be displayed accordingly (i.e, VERY small)<br />
<br />
A workaround is to force Xorg to startup with a given DPI value.<br />
<br />
To achieve this the following steps are required:<br />
<br />
* edit the file /usr/pluto/bin/Start_X_Wrapper.sh on your MD where you are facing the font problem<br />
* find the line beginning with xinit<br />
* add "-dpi 96" (without quotes) at the end of this line<br />
* save the file and reboot MD<br />
<br />
Obviously it is possible to set DPI to something different than 96, according to specific needs.<br />
<br />
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.<br />
<br />
=== LinuxMCE keeps reconfiguring my display settings ===<br />
<br />
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.<br />
<br />
For LinuxMCE 710 simply comment out the line that says<br />
. /usr/pluto/bin/X-CleanupVideo.sh<br />
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.<br />
<br />
== See also ==<br />
* [http://www.mythtv.org/wiki/index.php/Main_Page MythTV wiki] <br />
* MythTV Experience [http://brentlagesse.net/~brent/mythtv.php]<br />
* [[X_Configuration_Scripts]]</div>Unihttp://wiki.linuxmce.org/index.php?title=Display_Drivers&diff=18133Display Drivers2009-03-26T19:04:59Z<p>Uni: /* Bugs */</p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
[[Category: Tutorials]]<br />
[[Category: Hardware| ]]<br />
<br />
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.<br />
<br />
'''Note that this should normally not be necessary unless you have specific wishes or trouble getting your display to work properly.''' <br />
<br />
== Installation ==<br />
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.<br />
<br />
=== ATI Chipsets ===<br />
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].<br />
<br />
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.<br />
<br />
==== Installing The ATI Driver ====<br />
<br />
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.<br />
<br />
'''Step 1'''<br />
<br />
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'.<br />
<br />
'''Step 2'''<br />
<br />
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;<br />
<br />
sudo su - <return><br />
ssh moonNN <return> (**where the NN is the device number for the MD we're configuring**)<br />
<br />
Alternatively do the following from the MD/Core you are configuring;<br />
<br />
Ctrl+Alt+2<br />
<br />
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;<br />
<br />
Firstly make sure our sources.list is up to date:<br />
<br />
apt-get update <return><br />
<br />
Now lets install the ATI driver and packages;<br />
<br />
apt-get install linux-restricted-modules-generic restricted-manager <return><br />
<br />
Answer 'Y' to installing new packages then do the following steps;<br />
<br />
apt-get install xorg-driver-fglrx <return><br />
depmod -a <return><br />
<br />
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;<br />
<br />
I use the console text editor 'joe' below but you can use whichever you prefer ('nano' is installed by default for example);<br />
<br />
joe /etc/X11/xorg.conf <return><br />
<br />
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;<br />
<br />
Driver "vesa"<br />
or<br />
Driver "ati"<br />
<br />
Change the string 'vesa' (or ati) to 'fglrx' which is the name of the ATI driver. The updated driver line should look like below;<br />
<br />
Driver "fglrx"<br />
<br />
Now save the changes you have made to xorg.conf.<br />
<br />
Now reboot the MD from the console with;<br />
<br />
reboot <return><br />
<br />
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.<br />
<br />
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.<br />
<br />
=== NVidia Chipsets ===<br />
<br />
==== Bugs ====<br />
If you are here, trying to update your driver because video is not working, remember that there is a bug with some Nvidia cards that makes graphical output always appear on the DVI plug, not the VGA plug. If you have a display attached to the VGA port on your adapter, buy a DVI to VGA converter plug before putting yourself through a lot of pain!<br />
<br />
==== Legacy Drivers ====<br />
With legacy drivers the AVWizard might crash because it could not load the nvidia-legacy kernel module. It is unclear why kdm will start and not the AVWizard. A quick fix is to set the '''Driver''' option for the video card in the ''/etc/X11/xorg.conf'' file to '''vesa'''. Go through the AVWizard and then change it back. Another option is to edit ''/etc/modprobe.d/aliases'' and add '''alias nvidia nvidia-legacy'''. Don't forget about this line when you switch to a newer card.<br />
<br />
==== Latest Drivers ====<br />
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. <br />
<br />
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. <br />
'''<you>@dcerouter:~$''' sudo -s<br />
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:<br />
'''root@dcerouter:~#''' wget <nowiki>http://us.download.nvidia.com/XFree86/Linux-x86/</nowiki>''<version>''<nowiki>/NVIDIA-Linux-x86-</nowiki>''<version>''<nowiki>-pkg1.run</nowiki><br />
3. Go to runlevel 1 to stop the currently running X-server. <br />
'''root@dcerouter:~#''' telinit 1 <br />
4. Execute the installer and follow instructions. a) Ignore the warning about runlevel 1 and b) don't bother looking for "precompiled kernel interfaces" (drivers).<br />
'''root@dcerouter:~#''' sh NVIDIA-Linux-x86-''<version>''-pkg1.run<br />
5. The installer will attempt to remove old legacy drivers. If it cannot, you may receive X errors (Eg. ''Error: API mismatch''). The solution is to manually remove or disable the legacy drivers. <br />
'''nano /etc/default/linux-restricted-modules-common''' <br />
Disable the NVIDIA linux-restricted kernel modules (nvidia, nvidia_legacy) by changing the DISABLED_MODULES line to read:<br />
'''DISABLED_MODULES="nv nvidia_new"'''<br />
6. 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.<br />
<br />
==== Media Directors ====<br />
Instructions for installing the latest nVidia driver on your media directors can be found in the [[Upgrading the Kernel#Video Drivers|upgrading the kernel]] wiki.<br />
<br />
=== Intel Chipsets ===<br />
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.<br />
<br />
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.<br />
<br />
==== For LinuxMCE-0704 ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
From man i810:<br />
Option "LinearAlloc" "integer"<br />
Allows more memory for the offscreen allocator. This usually<br />
helps in situations where HDTV movies are required to play but<br />
not enough offscreen memory is usually available. Set this to<br />
8160 for upto 1920x1080 HDTV support. Default 0KB (off).<br />
<br />
==== potential problem ====<br />
<br />
there can be a problem with some intel drivers, like the gma 3100. see [[bug/gma3100driver]] for further informations<br />
<br />
=== Via Chipsets ===<br />
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]<br />
<br />
The proprietary Via Unichrome driver works best with Linux MCE. Unfortunately this driver has intentionally been stripped of support for most GLX extensions. This driver does not support alpha blending which is a prerequisite of [[UI2]]. Via licenses the full featured driver to system integrators, such as [[Fiire]]. This licensed driver is not publicly available. Additionally there is a known incompatibility issue with the licensed driver and Linux MCE 0710. <br />
<br />
On April 08, 2008 Via announced a new open source initiative to help develop open drivers for certain video chipsets [http://www.phoronix.com/scan.php?page=article&item=via_oss&num=1]. This press release echos sour notes with many developers who have heard this tune many times before. No useful information or code has been released to date, striking yet another all to familiar chord in the open source community [http://www.phoronix.com/scan.php?page=article&item=via_bluff&num=1].<br />
<br />
'''HOW-TO VIA Openchrome driver for xorg:'''<br><br />
For VIA CX700M2 UniChrome PRO II Graphics (1" VIA units) or mainly via graphics:<br><br />
<br />
''shell into your box and do the following:''<br><br />
apt-get -y 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 subversion xserver-xorg-dev libdrm-dev libxvmc-dev<br />
<br />
cd /usr/src<br />
svn checkout http://svn.openchrome.org/svn/trunk openchrome<br />
cd openchrome*<br />
./autogen.sh --prefix=/usr<br />
make<br />
make install<br />
<br />
Now we have to edit /etc/X11/xorg.conf and change the device driver to via openchrome:<br><br />
vi /etc/X11/xorg.conf<br />
Go to<br />
Section "Device"<br />
and change<br />
Driver "vesa" <br />
to<br />
Driver "openchrome"<br />
save and test the compiled new driver with a: <br><br />
X :1<br />
and if your xwindow comes up, you can reboot and have fun<br><br />
<br />
=== Other Chipsets ===<br />
Please help out by adding more if you can.<br />
<br />
== Configuration ==<br />
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.<br />
<br />
=== Getting started ===<br />
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. <br />
<br />
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:<br />
telinit 1<br />
This wil stop the running X-server and drop you into rescue mode as well. <br />
<br />
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.<br />
<br />
=== Generating a template ===<br />
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. <br />
<br />
'''While there is no (other) X-server running''' you can create a template configuration file by running:<br />
X -configure<br />
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:<br />
X -config ~/xorg.conf.new<br />
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). <br />
<br />
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.<br />
<br />
Here is an example of such a generated file:<br />
<br />
Section "ServerLayout"<br />
Identifier "X.org Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Mouse0" "CorePointer"<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/etc/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/X11/misc"<br />
FontPath "/usr/X11R6/lib/X11/fonts/misc"<br />
FontPath "/usr/share/fonts/X11/cyrillic"<br />
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/Type1"<br />
FontPath "/usr/X11R6/lib/X11/fonts/Type1"<br />
FontPath "/usr/share/fonts/X11/100dpi"<br />
FontPath "/usr/share/fonts/X11/75dpi"<br />
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "extmod"<br />
Load "record"<br />
Load "xtrap"<br />
Load "dri"<br />
Load "glx"<br />
Load "dbe"<br />
Load "GLcore"<br />
Load "type1"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Keyboard0"<br />
Driver "kbd"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Mouse0"<br />
Driver "mouse"<br />
Option "Protocol" "auto"<br />
Option "Device" "/dev/input/mice"<br />
Option "ZAxisMapping" "4 5 6 7"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
EndSection<br />
<br />
Section "Device"<br />
### Available Driver options are:-<br />
### Values: &lt;i&gt;: integer, <f>: float, <bool>: "True"/"False",<br />
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"<br />
### [arg]: arg optional<br />
#Option "ShadowFB" # [<bool>]<br />
#Option "DefaultRefresh" # [<bool>]<br />
#Option "ModeSetClearScreen" # [<bool>]<br />
Identifier "Card0"<br />
Driver "vesa"<br />
''VendorName "ATI Technologies Inc"''<br />
''BoardName "ATI Radeon Xpress 1200 Series"''<br />
''BusID '''"PCI:1:5:0"'''''<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 1<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 4<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 8<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 15<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 16<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
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:<br />
X -scanpci<br />
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.<br />
<br />
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.<br />
<br />
=== Refresh rate / ModeLine ===<br />
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:<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
''HorizSync '''27-102''' # kHz''<br />
''VertRefresh '''50-160''' # Hz''<br />
EndSection<br />
<br />
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. <br />
<br />
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. <br />
* http://koala.ilog.fr/cgi-bin/nph-colas-modelines<br />
* http://xtiming.sourceforge.net/cgi-bin/xtiming.pl<br />
* http://www.bohne-lang.de/spec/linux/modeline/<br />
* http://amlc.berlios.de/<br />
* http://www.mythtv.org/wiki/index.php/Working_with_Modelines<br />
If one modeline doesn't work perfectly, try another, perhaps from another generator, because they can vary so much.<br />
<br />
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]-[&larr;Backspace] and readjust your settings. Most modern screens however simply report that the signal is out of range if this happens.<br />
<br />
=== Colordepth and resolution ===<br />
Specify the colordepth and resolution(s) you would like to use, like this:<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
''DefaultDepth '''24'''''<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
''Virtual '''1600 1200'''''<br />
''Modes '''"1600x1200" "1280x1024" "1024x768" "800x600" "640x480" "512x384" "400x300" "320x240"'''''<br />
EndSubSection<br />
EndSection<br />
<br />
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.<br />
<br />
=== DRI device permissions ===<br />
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.<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
<br />
=== Chipset driver ===<br />
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''').<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
''# Driver "'''vesa'''"''<br />
''Driver "'''fglrx'''"''<br />
VendorName "ATI Technologies Inc"<br />
BoardName "ATI Radeon Xpress 1200 Series"<br />
BusID "PCI:1:5:0"<br />
EndSection<br />
<br />
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.<br />
<br />
=== Physical display size ===<br />
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.<br />
<br />
Section "Monitor"<br />
...<br />
DisplaySize '''155 95'''<br />
EndSection<br />
<br />
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.<br />
<br />
=== Disable composite ===<br />
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.<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
EndSection<br />
<br />
=== Additional options ===<br />
To be continued, I don't think this is enough to get UI2 completely (either mode) going yet. Feel free to jump in anytime... <br />
<br />
<br />
Things still to sort out amongst others (i.e. what is it, do we need it and what are the settings if any):<br />
<br />
Section "Module"<br />
Load "i2c"<br />
Load "bitmap"<br />
Load "ddc"<br />
Load "freetype"<br />
Load "int10"<br />
Load "vbe"<br />
Load "speedo"<br />
Load "type1"<br />
Load "dbe"<br />
Load "glx"<br />
Load "v4l"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AIGLX" "off"<br />
EndSection<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
# Option "RENDER" "true"<br />
EndSection<br />
<br />
Option "PseudoColorVisuals" "off"<br />
Option "OpenGLOverlay" "off"<br />
Option "VideoOverlay" "off"<br />
Option "DesktopSetup" "clone"<br />
<br />
TV-out options, 2nd display, etc.<br />
<br />
<br />
== Troubleshooting ==<br />
<br />
=== The AVWizard crashes X-windows ===<br />
<br />
Try setting the [[#Chipset_driver]] option to '''vesa''', run the AVWizard again and then change the driver back to what it was.<br />
<br />
=== Black screen ===<br />
<br />
* 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.<br />
<br />
*One problem on nvidia-cards could be that it does not detect the right monitor.<br />
<br />
::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><br />
::where XXX is CRT, CRT-0, CRT-1, DVI-0, DVI-1, ...<br />
::Save and exit (nano: Ctrl+x) and restart the computer. In my case it was "CRT-1".<br />
<br />
=== X-windows won't start ===<br />
<br />
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]-[&larr;Backspace] simultaneous to quit (alternative: use "startx" and get the full desktop, if any), then reboot when it works and you're done.<br />
<br />
=== Signal out of range ===<br />
<br />
See ''[[#Refresh rate / ModeLine ]]'' above.<br />
<br />
=== Microscopic fonts in KDE ===<br />
<br />
See ''[[#Physical_display_size]]'' above.<br />
<br />
If the above does not work, probably Xorg is calculating the DPI value in the wrong way.<br />
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.<br />
<br />
If those values are too small, fonts will be displayed accordingly (i.e, VERY small)<br />
<br />
A workaround is to force Xorg to startup with a given DPI value.<br />
<br />
To achieve this the following steps are required:<br />
<br />
* edit the file /usr/pluto/bin/Start_X_Wrapper.sh on your MD where you are facing the font problem<br />
* find the line beginning with xinit<br />
* add "-dpi 96" (without quotes) at the end of this line<br />
* save the file and reboot MD<br />
<br />
Obviously it is possible to set DPI to something different than 96, according to specific needs.<br />
<br />
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.<br />
<br />
=== LinuxMCE keeps reconfiguring my display settings ===<br />
<br />
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.<br />
<br />
For LinuxMCE 710 simply comment out the line that says<br />
. /usr/pluto/bin/X-CleanupVideo.sh<br />
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.<br />
<br />
== See also ==<br />
* [http://www.mythtv.org/wiki/index.php/Main_Page MythTV wiki] <br />
* MythTV Experience [http://brentlagesse.net/~brent/mythtv.php]<br />
* [[X_Configuration_Scripts]]</div>Unihttp://wiki.linuxmce.org/index.php?title=Display_Drivers&diff=18132Display Drivers2009-03-26T19:03:58Z<p>Uni: /* Bugs */</p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
[[Category: Tutorials]]<br />
[[Category: Hardware| ]]<br />
<br />
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.<br />
<br />
'''Note that this should normally not be necessary unless you have specific wishes or trouble getting your display to work properly.''' <br />
<br />
== Installation ==<br />
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.<br />
<br />
=== ATI Chipsets ===<br />
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].<br />
<br />
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.<br />
<br />
==== Installing The ATI Driver ====<br />
<br />
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.<br />
<br />
'''Step 1'''<br />
<br />
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'.<br />
<br />
'''Step 2'''<br />
<br />
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;<br />
<br />
sudo su - <return><br />
ssh moonNN <return> (**where the NN is the device number for the MD we're configuring**)<br />
<br />
Alternatively do the following from the MD/Core you are configuring;<br />
<br />
Ctrl+Alt+2<br />
<br />
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;<br />
<br />
Firstly make sure our sources.list is up to date:<br />
<br />
apt-get update <return><br />
<br />
Now lets install the ATI driver and packages;<br />
<br />
apt-get install linux-restricted-modules-generic restricted-manager <return><br />
<br />
Answer 'Y' to installing new packages then do the following steps;<br />
<br />
apt-get install xorg-driver-fglrx <return><br />
depmod -a <return><br />
<br />
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;<br />
<br />
I use the console text editor 'joe' below but you can use whichever you prefer ('nano' is installed by default for example);<br />
<br />
joe /etc/X11/xorg.conf <return><br />
<br />
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;<br />
<br />
Driver "vesa"<br />
or<br />
Driver "ati"<br />
<br />
Change the string 'vesa' (or ati) to 'fglrx' which is the name of the ATI driver. The updated driver line should look like below;<br />
<br />
Driver "fglrx"<br />
<br />
Now save the changes you have made to xorg.conf.<br />
<br />
Now reboot the MD from the console with;<br />
<br />
reboot <return><br />
<br />
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.<br />
<br />
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.<br />
<br />
=== NVidia Chipsets ===<br />
<br />
==== Bugs ====<br />
If you are here, trying to update your driver because video is not working, remember that there is a bug with some Nvidia cards that makes graphical output always appear on the DVI plug, not the VGA plug. If you have a display attached to the VGA port on your adapter, buy a DVI to VGA converter plug before putting yourself through a lot of pain!<br />
<br />
***03-26-09 You may experience hangs on the Xorg process (CPU at 100%) if you're using the older drivers. Do a "sudo cat /proc/driver/nvidia/version" and make sure after you've updated your drivers using the process outlined below, that it reads: NVIDIA UNIX x86 Kernel Module 180.29<br />
<br />
==== Legacy Drivers ====<br />
With legacy drivers the AVWizard might crash because it could not load the nvidia-legacy kernel module. It is unclear why kdm will start and not the AVWizard. A quick fix is to set the '''Driver''' option for the video card in the ''/etc/X11/xorg.conf'' file to '''vesa'''. Go through the AVWizard and then change it back. Another option is to edit ''/etc/modprobe.d/aliases'' and add '''alias nvidia nvidia-legacy'''. Don't forget about this line when you switch to a newer card.<br />
<br />
==== Latest Drivers ====<br />
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. <br />
<br />
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. <br />
'''<you>@dcerouter:~$''' sudo -s<br />
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:<br />
'''root@dcerouter:~#''' wget <nowiki>http://us.download.nvidia.com/XFree86/Linux-x86/</nowiki>''<version>''<nowiki>/NVIDIA-Linux-x86-</nowiki>''<version>''<nowiki>-pkg1.run</nowiki><br />
3. Go to runlevel 1 to stop the currently running X-server. <br />
'''root@dcerouter:~#''' telinit 1 <br />
4. Execute the installer and follow instructions. a) Ignore the warning about runlevel 1 and b) don't bother looking for "precompiled kernel interfaces" (drivers).<br />
'''root@dcerouter:~#''' sh NVIDIA-Linux-x86-''<version>''-pkg1.run<br />
5. The installer will attempt to remove old legacy drivers. If it cannot, you may receive X errors (Eg. ''Error: API mismatch''). The solution is to manually remove or disable the legacy drivers. <br />
'''nano /etc/default/linux-restricted-modules-common''' <br />
Disable the NVIDIA linux-restricted kernel modules (nvidia, nvidia_legacy) by changing the DISABLED_MODULES line to read:<br />
'''DISABLED_MODULES="nv nvidia_new"'''<br />
6. 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.<br />
<br />
==== Media Directors ====<br />
Instructions for installing the latest nVidia driver on your media directors can be found in the [[Upgrading the Kernel#Video Drivers|upgrading the kernel]] wiki.<br />
<br />
=== Intel Chipsets ===<br />
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.<br />
<br />
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.<br />
<br />
==== For LinuxMCE-0704 ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
From man i810:<br />
Option "LinearAlloc" "integer"<br />
Allows more memory for the offscreen allocator. This usually<br />
helps in situations where HDTV movies are required to play but<br />
not enough offscreen memory is usually available. Set this to<br />
8160 for upto 1920x1080 HDTV support. Default 0KB (off).<br />
<br />
==== potential problem ====<br />
<br />
there can be a problem with some intel drivers, like the gma 3100. see [[bug/gma3100driver]] for further informations<br />
<br />
=== Via Chipsets ===<br />
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]<br />
<br />
The proprietary Via Unichrome driver works best with Linux MCE. Unfortunately this driver has intentionally been stripped of support for most GLX extensions. This driver does not support alpha blending which is a prerequisite of [[UI2]]. Via licenses the full featured driver to system integrators, such as [[Fiire]]. This licensed driver is not publicly available. Additionally there is a known incompatibility issue with the licensed driver and Linux MCE 0710. <br />
<br />
On April 08, 2008 Via announced a new open source initiative to help develop open drivers for certain video chipsets [http://www.phoronix.com/scan.php?page=article&item=via_oss&num=1]. This press release echos sour notes with many developers who have heard this tune many times before. No useful information or code has been released to date, striking yet another all to familiar chord in the open source community [http://www.phoronix.com/scan.php?page=article&item=via_bluff&num=1].<br />
<br />
'''HOW-TO VIA Openchrome driver for xorg:'''<br><br />
For VIA CX700M2 UniChrome PRO II Graphics (1" VIA units) or mainly via graphics:<br><br />
<br />
''shell into your box and do the following:''<br><br />
apt-get -y 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 subversion xserver-xorg-dev libdrm-dev libxvmc-dev<br />
<br />
cd /usr/src<br />
svn checkout http://svn.openchrome.org/svn/trunk openchrome<br />
cd openchrome*<br />
./autogen.sh --prefix=/usr<br />
make<br />
make install<br />
<br />
Now we have to edit /etc/X11/xorg.conf and change the device driver to via openchrome:<br><br />
vi /etc/X11/xorg.conf<br />
Go to<br />
Section "Device"<br />
and change<br />
Driver "vesa" <br />
to<br />
Driver "openchrome"<br />
save and test the compiled new driver with a: <br><br />
X :1<br />
and if your xwindow comes up, you can reboot and have fun<br><br />
<br />
=== Other Chipsets ===<br />
Please help out by adding more if you can.<br />
<br />
== Configuration ==<br />
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.<br />
<br />
=== Getting started ===<br />
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. <br />
<br />
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:<br />
telinit 1<br />
This wil stop the running X-server and drop you into rescue mode as well. <br />
<br />
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.<br />
<br />
=== Generating a template ===<br />
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. <br />
<br />
'''While there is no (other) X-server running''' you can create a template configuration file by running:<br />
X -configure<br />
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:<br />
X -config ~/xorg.conf.new<br />
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). <br />
<br />
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.<br />
<br />
Here is an example of such a generated file:<br />
<br />
Section "ServerLayout"<br />
Identifier "X.org Configured"<br />
Screen 0 "Screen0" 0 0<br />
InputDevice "Mouse0" "CorePointer"<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
EndSection<br />
<br />
Section "Files"<br />
RgbPath "/etc/X11/rgb"<br />
ModulePath "/usr/lib/xorg/modules"<br />
FontPath "/usr/share/fonts/X11/misc"<br />
FontPath "/usr/X11R6/lib/X11/fonts/misc"<br />
FontPath "/usr/share/fonts/X11/cyrillic"<br />
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"<br />
FontPath "/usr/share/fonts/X11/Type1"<br />
FontPath "/usr/X11R6/lib/X11/fonts/Type1"<br />
FontPath "/usr/share/fonts/X11/100dpi"<br />
FontPath "/usr/share/fonts/X11/75dpi"<br />
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"<br />
EndSection<br />
<br />
Section "Module"<br />
Load "extmod"<br />
Load "record"<br />
Load "xtrap"<br />
Load "dri"<br />
Load "glx"<br />
Load "dbe"<br />
Load "GLcore"<br />
Load "type1"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Keyboard0"<br />
Driver "kbd"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Mouse0"<br />
Driver "mouse"<br />
Option "Protocol" "auto"<br />
Option "Device" "/dev/input/mice"<br />
Option "ZAxisMapping" "4 5 6 7"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
EndSection<br />
<br />
Section "Device"<br />
### Available Driver options are:-<br />
### Values: &lt;i&gt;: integer, <f>: float, <bool>: "True"/"False",<br />
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"<br />
### [arg]: arg optional<br />
#Option "ShadowFB" # [<bool>]<br />
#Option "DefaultRefresh" # [<bool>]<br />
#Option "ModeSetClearScreen" # [<bool>]<br />
Identifier "Card0"<br />
Driver "vesa"<br />
''VendorName "ATI Technologies Inc"''<br />
''BoardName "ATI Radeon Xpress 1200 Series"''<br />
''BusID '''"PCI:1:5:0"'''''<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 1<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 4<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 8<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 15<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 16<br />
EndSubSection<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
EndSubSection<br />
EndSection<br />
<br />
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:<br />
X -scanpci<br />
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.<br />
<br />
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.<br />
<br />
=== Refresh rate / ModeLine ===<br />
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:<br />
<br />
Section "Monitor"<br />
Identifier "Monitor0"<br />
VendorName "Monitor Vendor"<br />
ModelName "Monitor Model"<br />
''HorizSync '''27-102''' # kHz''<br />
''VertRefresh '''50-160''' # Hz''<br />
EndSection<br />
<br />
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. <br />
<br />
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. <br />
* http://koala.ilog.fr/cgi-bin/nph-colas-modelines<br />
* http://xtiming.sourceforge.net/cgi-bin/xtiming.pl<br />
* http://www.bohne-lang.de/spec/linux/modeline/<br />
* http://amlc.berlios.de/<br />
* http://www.mythtv.org/wiki/index.php/Working_with_Modelines<br />
If one modeline doesn't work perfectly, try another, perhaps from another generator, because they can vary so much.<br />
<br />
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]-[&larr;Backspace] and readjust your settings. Most modern screens however simply report that the signal is out of range if this happens.<br />
<br />
=== Colordepth and resolution ===<br />
Specify the colordepth and resolution(s) you would like to use, like this:<br />
<br />
Section "Screen"<br />
Identifier "Screen0"<br />
Device "Card0"<br />
Monitor "Monitor0"<br />
''DefaultDepth '''24'''''<br />
SubSection "Display"<br />
Viewport 0 0<br />
Depth 24<br />
''Virtual '''1600 1200'''''<br />
''Modes '''"1600x1200" "1280x1024" "1024x768" "800x600" "640x480" "512x384" "400x300" "320x240"'''''<br />
EndSubSection<br />
EndSection<br />
<br />
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.<br />
<br />
=== DRI device permissions ===<br />
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.<br />
<br />
Section "DRI"<br />
Mode 0666<br />
EndSection<br />
<br />
=== Chipset driver ===<br />
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''').<br />
<br />
Section "Device"<br />
Identifier "Card0"<br />
''# Driver "'''vesa'''"''<br />
''Driver "'''fglrx'''"''<br />
VendorName "ATI Technologies Inc"<br />
BoardName "ATI Radeon Xpress 1200 Series"<br />
BusID "PCI:1:5:0"<br />
EndSection<br />
<br />
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.<br />
<br />
=== Physical display size ===<br />
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.<br />
<br />
Section "Monitor"<br />
...<br />
DisplaySize '''155 95'''<br />
EndSection<br />
<br />
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.<br />
<br />
=== Disable composite ===<br />
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.<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
EndSection<br />
<br />
=== Additional options ===<br />
To be continued, I don't think this is enough to get UI2 completely (either mode) going yet. Feel free to jump in anytime... <br />
<br />
<br />
Things still to sort out amongst others (i.e. what is it, do we need it and what are the settings if any):<br />
<br />
Section "Module"<br />
Load "i2c"<br />
Load "bitmap"<br />
Load "ddc"<br />
Load "freetype"<br />
Load "int10"<br />
Load "vbe"<br />
Load "speedo"<br />
Load "type1"<br />
Load "dbe"<br />
Load "glx"<br />
Load "v4l"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AIGLX" "off"<br />
EndSection<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
# Option "RENDER" "true"<br />
EndSection<br />
<br />
Option "PseudoColorVisuals" "off"<br />
Option "OpenGLOverlay" "off"<br />
Option "VideoOverlay" "off"<br />
Option "DesktopSetup" "clone"<br />
<br />
TV-out options, 2nd display, etc.<br />
<br />
<br />
== Troubleshooting ==<br />
<br />
=== The AVWizard crashes X-windows ===<br />
<br />
Try setting the [[#Chipset_driver]] option to '''vesa''', run the AVWizard again and then change the driver back to what it was.<br />
<br />
=== Black screen ===<br />
<br />
* 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.<br />
<br />
*One problem on nvidia-cards could be that it does not detect the right monitor.<br />
<br />
::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><br />
::where XXX is CRT, CRT-0, CRT-1, DVI-0, DVI-1, ...<br />
::Save and exit (nano: Ctrl+x) and restart the computer. In my case it was "CRT-1".<br />
<br />
=== X-windows won't start ===<br />
<br />
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]-[&larr;Backspace] simultaneous to quit (alternative: use "startx" and get the full desktop, if any), then reboot when it works and you're done.<br />
<br />
=== Signal out of range ===<br />
<br />
See ''[[#Refresh rate / ModeLine ]]'' above.<br />
<br />
=== Microscopic fonts in KDE ===<br />
<br />
See ''[[#Physical_display_size]]'' above.<br />
<br />
If the above does not work, probably Xorg is calculating the DPI value in the wrong way.<br />
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.<br />
<br />
If those values are too small, fonts will be displayed accordingly (i.e, VERY small)<br />
<br />
A workaround is to force Xorg to startup with a given DPI value.<br />
<br />
To achieve this the following steps are required:<br />
<br />
* edit the file /usr/pluto/bin/Start_X_Wrapper.sh on your MD where you are facing the font problem<br />
* find the line beginning with xinit<br />
* add "-dpi 96" (without quotes) at the end of this line<br />
* save the file and reboot MD<br />
<br />
Obviously it is possible to set DPI to something different than 96, according to specific needs.<br />
<br />
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.<br />
<br />
=== LinuxMCE keeps reconfiguring my display settings ===<br />
<br />
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.<br />
<br />
For LinuxMCE 710 simply comment out the line that says<br />
. /usr/pluto/bin/X-CleanupVideo.sh<br />
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.<br />
<br />
== See also ==<br />
* [http://www.mythtv.org/wiki/index.php/Main_Page MythTV wiki] <br />
* MythTV Experience [http://brentlagesse.net/~brent/mythtv.php]<br />
* [[X_Configuration_Scripts]]</div>Unihttp://wiki.linuxmce.org/index.php?title=BFG_GeForce_7300_GS&diff=18085BFG GeForce 7300 GS2009-03-23T04:47:54Z<p>Uni: </p>
<hr />
<div>[[Category: Graphic Cards]] <br />
<br />
<br />
This card works out of the box, supports Alpha Blending, DVI, and does not need updated drivers to work.</div>Unihttp://wiki.linuxmce.org/index.php?title=BFG_GeForce_7300_GS&diff=18084BFG GeForce 7300 GS2009-03-23T04:46:30Z<p>Uni: New page: This card works out of the box, supports Alpha Blending, DVI, and does not need updated drivers to work.</p>
<hr />
<div><br />
<br />
This card works out of the box, supports Alpha Blending, DVI, and does not need updated drivers to work.</div>Unihttp://wiki.linuxmce.org/index.php?title=BFG_GeForce_7600GT_256MB&diff=17990BFG GeForce 7600GT 256MB2009-03-16T03:12:07Z<p>Uni: </p>
<hr />
<div>[[Category: Graphic Cards]] <br />
<br />
Please note that this PCI-E card does not work out of the box with LMCE, connecting to an HDMI interface. It will work connecting to VGA. Even installing the newest Nvidia drivers afterwards and running the Video and Audio wizard will not drive the HDMI properly. You will need to install Kubuntu first, then CD1 + CD2. It's a bit tedious but it works.</div>Unihttp://wiki.linuxmce.org/index.php?title=BFG_GeForce_7600GT_256MB&diff=17989BFG GeForce 7600GT 256MB2009-03-16T03:10:24Z<p>Uni: </p>
<hr />
<div>[[Category: Graphic Cards]] <br />
<br />
Please note that this PCI-E card does not work out of the box with LMCE, connecting to an HDMI interface. It will work connecting to VGA. Even installing the newest NVidia drivers afterwards and running the Video and Audio wizard will not drive the HDMI properly. You will need to install Kubuntu first, then CD1 + CD2. It's a bit tedious but it works.</div>Unihttp://wiki.linuxmce.org/index.php?title=BFG_GeForce_7600GT_256MB&diff=17988BFG GeForce 7600GT 256MB2009-03-16T03:08:17Z<p>Uni: New page: Category: Graphic Cards Please note that this card does not work out of the box with LMCE, connecting to an HDMI interface. Even installing the newest NVidia drivers afterwards ...</p>
<hr />
<div>[[Category: Graphic Cards]] <br />
<br />
Please note that this card does not work out of the box with LMCE, connecting to an HDMI interface. Even installing the newest NVidia drivers afterwards will not drive the HDMI properly. You will need to install Kubuntu first, then CD1 + CD2.</div>Unihttp://wiki.linuxmce.org/index.php?title=BFGTech_GeForce_7600GS_512MB&diff=17983BFGTech GeForce 7600GS 512MB2009-03-16T02:47:52Z<p>Uni: /* Status */</p>
<hr />
<div>[[Category: Hardware]]<br />
[[Category: Graphic Cards]]<br />
<br />
<br />
<br />
[[Image:7600GS_512_AGP.jpg]]<br />
<br />
<br />
== Detailed Specifications ==<br />
<br />
'''Performance'''<br><br />
GPU NVIDIA GeForce 7600 GS<br><br />
Core Clock 420 MHz (vs. 400MHz standard)<br><br />
Vertices 525 million/sec.<br><br />
<br />
'''Memory'''<br><br />
Video Memory 512MB<br> <br />
Memory Type DDR2<br><br />
<br />
'''Connections'''<br><br />
Bus Type AGP<br><br />
Connector(s) Dual-Link DVI-I, VGA + HDTV<br> <br />
RAMDACs Dual 400MHz<br><br />
Multiple Monitor Support Yes<br><br />
HDCP Capable No<br><br />
<br />
'''Included In Box'''<br><br />
> BFG NVIDIA GeForce 7600 GS OC 512MB graphics card<br><br />
> Quick install guide<br><br />
> DVI-I to VGA dongle<br><br />
> HDTV dongle<br><br />
> Driver CD, which includes: NVIDIA ForceWare unified graphics drivers and Full installation manual .pdf<br><br />
<br />
'''Minimum System Requirements'''<br><br />
> 256MB of system memory<br> <br />
> Microsoft Windows XP<br> <br />
> CD or DVD-ROM drive<br> <br />
> A minimum 350W system power supply (with 12V current rating of 20A or more)<br><br />
> An AGP compliant motherboard. Some motherboards violate the AGP specification and therefore this card may not physically fit in some systems<br><br />
> An available hard disk drive power dongle<br><br />
<br />
== Status ==<br />
<br />
This Nvidia 7600GS AGP Card works right out of the box. The card has a dongle for HDTV compatability (not tested). The card had no issues supporting UI2 alphablending.<br />
<br />
[http://www.bfgtech.com/bfgr76512gsoc.aspx BFG Tech Product Page]<br />
<br />
The Nvidia 7600GT, PCI-E card does not work with the DVD install, connecting the cable to the DVI output on your PC. You must install Kubuntu first, then CD1 + CD2, and then it works.</div>Uni