LinuxMCE - User contributions [en]

Web Orbiter

2008-01-17T01:40:51Z

Mog:

The Web Orbiter is an instance of the Orbiter that is accessible from a Web browser across a network from the Core.

== Setup ==
Procedure to setup the Web Orbiter is simple but the order of steps is important.
#First of all we should add a new Generic Web Device as a Child Device for your Core:
##On the Adminsite homepage, at the bottom of the left column's expansion of all the menu items, click "Show devices tree" and then "CORE". The CORE's detail page should appear.
##On this page click the link 'Create Child Device'.
##In the Add child device window, click the button 'Pick device template'. The new pop-up window contained device templates will be opened.
##In the 'Device Category' dropdown list, choose 'Peripherals'.
##In the 'Device Template' dropdown list, find and select "Generic Web Device".
##Click the button 'Pick Device Template'. The Add Child Device Window will close, and the Generic Web Device will be added to the Core, as the updated Device Tree will show.
##Also new Generic Proxy Orbiter will be created automatically on this stage. We can watch the Orbiter generation process on the Orbiters page: Wizard --> Devices --> Orbiters.
#Wait till generation procedure finishes. A message on some active Orbiter or on the Orbiter page will so indicate.
#Don't forget Quick reload router. It's important because otherwise the Orbiter won't work properly.
#We can access to the Web Orbiter:
##Type URL ''<nowiki>http://<core_ip>/pluto-admin/weborbiter.php</nowiki>'' in the browser address bar. You will get a very plain login page.
##Input existing user name and password, then click the "Login" button. You will get a page with a list of devices.
##From the dropdown list, choose Generic Web Device. You will get a page that looks similar to: [[Image:Web Orbiter.jpg|center]]

If you try to connect to the Web Orbiter and see this message:
<code>"Connect to proxy orbiter failed, please try again"</code>
this means that the procedure of Orbiter generation doesn't finish yet or you forgot to quick restart of router.

== Size ==
I was able to change the size of the rendered image in the Wizard->Orbiters page, I just found my Web Orbiter device in the list, and resized it.. after a regen, it was at the right size.
:''Source http://forum.linuxmce.org/index.php?topic=3833.0''

[[Category: Orbiters]]
[[Category: Tutorials]]

Known Issues

2008-01-17T01:35:52Z

Mog: /* Known issues with LinuxMCE 0704 */

== Known issues with LinuxMCE 0704 ==

Be sure to read [[Video#network]] because if you don't enable your network connection you won't have gallery art or be able to add extra software.

The QuickInstall DVD is not correctly handling an installation with a single network interface card. If you have only 1 network interface card, then as explained in [[Video#network]] when you go to test your network, go into the Admin site. Choose Advanced, Configuration, Devices. Click the 'Core' in the left device tree. Scroll down to 'Network Settings', and carefully edit that line changing the text that says "eth1" to instead say "eth0:0". Then save the changes on that page. Now go to Advanced, Network, Network Settings. If you're using a static IP specify it now. Whether or not you made any changes, click the update button which will cause it to reset your network. Confirm you now have an internet connection. The network settings should show that eth0 is your normal network (dhcp or static), and eth1 is 192.168.80.1. If you don't want LinuxMCE to be your DHCP server, you can disable that option here.

LMCE 0704 will not use windows shares with spaces in them, e.g. "DISK 1".

== Known issues with LinuxMCE 1.1 Beta ==

* if you get the following error:

pluto-dcerouter: Depends: pluto-confirm-dependencies (>= 2.0.0.44) but it is not going to be installed
Depends: pluto-confirm-dependencies (< 2.0.0.45) but it is not going to be installed
Depends: pluto-createdevice (>= 2.0.0.44) but it is not going to be installed
Depends: pluto-createdevice (< 2.0.0.45) but it is not going to be installed
Depends: pluto-install-scripts (>= 2.0.0.44) but it is not going to be installed
Depends: pluto-install-scripts (< 2.0.0.45) but it is not going to be installed
Depends: pluto-local-database (>= 2.0.0.44) but it is not going to be installed
Depends: pluto-local-database (< 2.0.0.45) but it is not going to be installed
Depends: pluto-std-plugins (>= 2.0.0.44) but it is not going to be installed
Depends: pluto-std-plugins (< 2.0.0.45) but it is not going to be installed
Depends: pluto-system-database (>= 2.0.0.44) but it is not going to be installed
Depends: pluto-system-database (< 2.0.0.45) but it is not going to be installed
Depends: pluto-website-admin (>= 2.0.0.44) but it is not going to be installed
Depends: pluto-website-admin (< 2.0.0.45) but it is not going to be installed
Depends: pluto-boot-scripts (>= 2.0.0.44) but it is not going to be installed
Depends: pluto-boot-scripts (< 2.0.0.45) but it is not going to be installed
PreDepends: samba but it is not going to be installed
E: Broken packages

Solution: the quickest solution is to skip the use of the cache cd or to have latest samba package installed before starting the installation.

* sometimes it's better to kill the network manager and add the network settings manually. I found that the network settings are overwritten when the installation of Linux MCE is finished. and you don't have internet connection anymore. This may lead to problems like the one above, with the samba package.

* if you are rebooting the system after installing LinuxMCE 1.1 and the system hangs up at "'''Running local boot scripts (/etc/rc.local) [ OK]'''"

Solution: rename kdm.saved from /etc/init.d to kdm and then reboot.

== Known issues with LinuxMCE 1.0 ==

It is best to install version 1.0 on a separate box, rather than your main Ubuntu system because of the following issues:

* The installer is messing up Ubuntu's xorg.conf file by removing the nvidia driver and replacing it with vesa. This was actually a necessary hack that got forgotten about. There is a bug in the nVidia drivers (it has been reported) that causes them to crash when two X sessions are running and try to open the same card. Using the 'nv' driver on one and the 'nvidia' on the other still doesn't work, but using vesa on one and nvidia on the other does. So the hack changes Ubuntu's xorg.conf from nVidia to Vesa. If you install a dedicated LinuxMCE box this isn't an issue, but it can be a problem when you are a Ubuntu user and want better performance on your Ubuntu desktop than the vesa driver allows.

* The installer will revert the Ubuntu sources.list back to the default, removing any non-standard repositories, when it does the upgrade before installing itself.

* As mentioned in other places, the scripts carried from Pluto were written to be run on a dedicated system and 'take over' completely. It was a huge task just getting LinuxMCE 1.0 out the door, and the Ubuntu integration is still a work in progress and the scripts are still too invasive. If this is a dedicated system, or if you're not a Linux user, this is perhaps still a good thing because you'll never need to touch your configuration files: LinuxMCE will setup the dhcp server, samba network shares, network settings, and so on. But, if you are a Ubuntu user, be warned that it will override some of your settings until we get the Ubuntu integration improved.

Additional issues:

* Most of the problems reported so far are caused by using UI2, which requires OpenGL, on video cards without good Linux OpenGL support. The solution is to use UI1 instead. nVidia 6xxx and higher are preferred and will run UI2 with the 3d effects and alpha blending.

* A bug in the media browser was identified that is causing it to run very slow and consume a lot of memory. A 1.01 patch will be out soon.

* In the haste to release the updated LinuxMCE 1.0 that didn't use the website for downloading the software after the Digg story brought the server down, there was a sloppy error building the package for the Windows binaries. Most of them are empty. This means the Windows orbiter that runs on web pads, pda's and ms smart phones, as well as some other windows applets which are also on the download page in your Core's admin web site, are missing.

* Some of the users reported having broken packages during the installation of LinuxMCE, usually 'pluto-orbiter' package. This could happen from a number of reasons. We have identified a few of them, such as:
- the vim package cannot be installed because of a conflict at 'vim-common'. For details on how to fix that, please follow: [http://wiki.linuxmce.com/index.php/Installer_Problems]
- The Ubuntu repositories are sometimes unavailable. You should try reinstalling, or installing the packages by hand

MirrorsOld

2008-01-17T01:31:52Z

Mog: /* LinuxMCE 0704 */

== LinuxMCE 0704 ==

'''Before installing, check out the [[Known_Issues]].'''

There are 2 installers: the CD installer and the Quick install DVD installer ([[Download_Instructions|more]]). The new demo video that is on [http://video.google.com/videoplay?docid=2176025602905109829&hl=en Google Video] can be downloaded here in high-def 720p Ogg-Theora (.ogm) and Windows Media Video (.wmv). WMV is most compatible for viewing under windows, and OGM for Linux. Source is also available.

The md5sum for the LinuxMCE 0704 files are :

'''81206cd80caa6fc93965c94b2ac8f434 LinuxMCE_0704_CD1.iso'''

'''b00d7a04eccfdd0e85be4e6432b59919 LinuxMCE_0704_CD2.iso'''

'''c219674756bcd5ec202a68712baac2de LinuxMCE_0704_Quick_Install_DVD.iso'''

'''996b84f7d9e409b64078d4f06804c830 LinuxMCE_0704_Demo_Video_2mbit.ogm'''

'''7205c0ead596cff3e4e50d1a1b9004a5 LinuxMCE_0704_Demo_Video_2mbit.wmv'''

'''071f91777035bf49b4766367d65e09f3 LinuxMCE_0704_Source.tar.bz2'''

This wiki page is editable so users can add additional mirrors. To prevent the addition of malware to the .iso, the md5sum is also shown on the [http://linuxmce.org/index.phphome page in the news section], which is not editable by the public.

People who will be providing mirrors can email to '''Paul Webber''' -- contact: webpaul1 -at- gmail (.com) for a URL to the LinuxMCE ftp server to get the files faster, and remove the (1.0 only) comment from this wiki when your mirror has the 0704 files.

LinuxMCE 0704 was released on August 6, 2007. At this time the torrents contain the release, and the mirrors should be updated soon. Mirrors which have (1.0 only) have not been updated.

{| border="1" cellspacing="0" cellpadding="5" style="border-collapse:collapse; border-color:#8eabd0; background:#e7edf5"
|- style="background: lightsteelblue"
|-
!Official Torrents:
|
* http://torrents.thepiratebay.org/3764634/LinuxMCE_0704_CDs.3764634.TPB.torrent
* http://torrents.thepiratebay.org/3764648/LinuxMCE_0704_Quick_Install_DVD.iso.3764648.TPB.torrent
* http://torrents.thepiratebay.org/3764646/LinuxMCE_0704_Demo_Video_2mbit.wmv.3764646.TPB.torrent
* http://torrents.thepiratebay.org/3764636/LinuxMCE_0704_Demo_Video_2mbit.ogm.3764636.TPB.torrent
* http://torrents.thepiratebay.org/3764683/LinuxMCE_0704_Source.tar.bz2.3764683.TPB.torrent
Please help us seed! Leave your torrent open for as long as possible after you've finished downloading.
|-
![http://www.pando.com/ Pando] (a P2P app):
|
* [http://services.pando.com/soapservices/Package/package.pando?id=6618ABF20D15D2A34C1A0DB9C6C59413DF4FFA04&key=CBC7D75A7E1B42A569D5279CBA615E7F104B477C31C2976C049401E3661EF598&tt=S2W&embedId=B9E747AD30731766989193E1340946C8 LinuxMCE 0704 CDs]
* [http://services.pando.com/soapservices/Package/package.pando?id=7FE3D9D2B8E59EFB97318683522877CD28330A87&key=DED2EE743E1F705AF31B443A1330AB70E86F1878A869D6BC297D95C1F819823A&tt=S2W&embedId=193D3148503A5EEFA08C0C24627F5948 LinuxMCE 0704 Quick Install DVD]
* [http://services.pando.com/soapservices/Package/package.pando?id=AE927E039492FF3D1B5927F103AC8ACC9E467420&key=19802D095AC8B79757D0076C56F219D09C10D61980CC3C0E79D3CB3A0C664643&tt=S2W&embedId=342B2207F34F5129BEBA959FF74084F8 LinuxMCE 0704 Source]
* [http://services.pando.com/soapservices/Package/package.pando?id=E8B2C60114EFAFBC98ACB4922EA33AF8B203CE61&key=0150B234C0F4E626658DF9C9593BD60C6C6BFD22EA0141C82568856D310BBFB4&tt=S2W&embedId=CBCB18EE0C7DDE5C929EC5D6675686ED LinuxMCE 0704 Demo Video 2mbit(wmv)]
* [http://services.pando.com/soapservices/Package/package.pando?id=DDBD54C81F68144DFBF5D04A8B4BEB52EA32C0B5&key=66C9F572658F55E7A4F489BB9C3F87AC23D0BF756F57998BB73630F9AFC3ED26&tt=S2W&embedId=AE7DD83014C380EAF30F5B4DB3CE82CC LinuxMCE 0704 Demo Video 2mbit(ogm)]
* [http://cache.pando.com/soapservices/Package/package.pando?id=93C79E269A55BE14C7F68A859B0EF336B2CF4849&key=AAE42C36492B011477091337338945CB724B32ADC6F975597A261448318B620B&tt=S2W LinuxMCE 1.0]
|-
!U.S.:
|
* (0704) http://www.neversfw.com/linux/ (2 CD's)
* (0704 / 0710beta2) http://proyectos.pixelamigo.com/software/Ubuntu/linuxMCE/ Must pay donation to download( Linux MCE 2CDs and Quick Install DVD + Ubuntu Ultimate Edition 1.6 + Ubuntu Gamers Edition 1.4 + Linux MCE 0710 DVD beta 2)
* (1.0 only) http://evilwalrus.net/mirror/ - ( [http://evilwalrus.net/mirror/mce-installer_1.0.0-1_i386.deb .deb installer] & [http://evilwalrus.net/mirror/linuxmce-1.0-packages.iso iso])
|-
!Europe/Middle East:
|
* (0704) http://kubuntu.org/~jriddell/linuxmce/
* (0704 + 1.0) http://www.netzwelt.de/software/4459-linuxmce.html
* (0704 + 1.0) http://mirror.mirimar.net/linuxmce/
* (0704) http://mirrors.flumpy.org/LinuxMCE/ (2 CD's / DVD (wrong Checksum) / Videos & Source)
* (1.0 only) http://mirror.hgkz.ch/ftp/iso/linuxmce/linuxmce-1.0-packages.iso
|-
!FileFront Mirror:
|
* (1.0 only) http://hosted.filefront.com/linuxmce/1925781 To help take some load of paid websites...
|-
!MediaFire Direct Links
|
* Files are direct downloads, use [http://www.freebyte.com/hjsplit/ HJ-Split] to combine.
* (1.0 only) [http://www.mediafire.com/?014wq4mgmki Part 1]
* (1.0 only) [http://www.mediafire.com/?9ozzyltiimt Part 2]
* (1.0 only) [http://www.mediafire.com/?a5q5yfdyzqy Part 3]
* (1.0 only) [http://www.mediafire.com/?1uwzzzzu0xm Part 4]
* (1.0 only) [http://www.mediafire.com/?czzmq5jzygu Part 5]
* (1.0 only) [http://www.mediafire.com/?64dw2mzz3km Part 6] -> WORKING (I spoke with MediaFire, and as of 4/3/2007 9:30am the link DOES work, sorry about the downtime)
* (1.0 only) [http://www.mediafire.com/?5ygynmnnqfr Part 7]
|-
!Rapidshare Links
|
* Like the MediaFire Links, use [http://www.freebyte.com/hjsplit/ HJ-Split] to combine.
* This folder contains all 39 parts to rejoin.
* As time permits I will add the other releases
* [http://rapidshare.com/users/UUJRMI?byfilename=1 LinuxMCE 0704 Quick Install DVD iso] (Bad file) <- not bad, just merge the binaries and rename to *.iso
* [http://rapidshare.com/users/Q3VYT7?byfilename=1 LinuxMCE CD isos 1 & 2]
|-
!Asia/Pacfic Links
|
* AusGamers (Australia)
* [http://www.ausgamers.com/files/details/html/30171 LinuxMCE 0704 ISO Disc 1]
* [http://www.ausgamers.com/files/details/html/30172 LinuxMCE 0704 ISO Disc 2]
* [http://www.ausgamers.com/files/details/html/30573 LinuxMCE Quick Install DVD ISO]
|}

test

Easy-share mirror:

(1.0 only) [http://w13.easy-share.com/2311321.html Part 1]

(1.0 only) [http://w13.easy-share.com/2314241.html Part 2]

(1.0 only) [http://w13.easy-share.com/2320901.html Part 3]

(1.0 only) [http://w13.easy-share.com/2320961.html Part 4]

(1.0 only) [http://w13.easy-share.com/2321011.html Part 5]

(1.0 only) [http://w13.easy-share.com/2321051.html Part 6]

(1.0 only) [http://w13.easy-share.com/2321071.html Part 7]

Talk:Controlling LinuxMCE

2008-01-16T10:48:22Z

Mog:

This is the main article for Controlling LinuxMCE.

Todo:
Rename Category:Infrared to Category:Remote Controls which is a better name and also is what's used in MythTV's wiki.

http://www.mythtv.org/wiki/index.php/Category:Remote_Controls

USB UIRT

2008-01-16T10:46:24Z

Mog:

[[Category: Hardware]]
[[Category: Automation]]
[[Category: Infrared]]

{| align="right"
| __TOC__
|}

[[Image:USB_UIRT.jpg|right]]

* Manufacturer home page: http://www.usbuirt.com/
* Seems to work: http://wiki.linuxmce.com/index.php/Video#Equipment_used_in_the_demo
==Use in LinuxMCE==
===Connection===
* This device is [[Plug&play]], which means not significant amount of modifications to get it to work.

===Adding Remotes===
{{sectstub}}
* Windows XP MC Remote is added automatically.
* Adding different remotes (needs more work)

===Controlling AV Devices===
* [[AV Devices]] is the main page used for making and adjusting control over A/V Equipment.
* Also take a look at [[Infrared Codes]] if you are having problems with the prepopulated Codesets.

== Sales Pitch ==
The USB-UIRT, along with Automation Software such as [[LinuxMCE]], allows your PC to both Receive and Transmit infrared signals -- exactly like those used by the collection of remote controls you've acquired for your TV, VCR, Audio System, etc. The USB-UIRT can:
* Receive signals from the remote controls you already have (allowing your PC to perform actions when the 'Play' button is pressed on your VCR remote, for example)

* 'Learn' from remotes you already have and Transmit a duplicate of these signals from your PC (for example, your PC could automatically turn ON your VCR and tune it to channel 3)

* Use codes available from the Web for other remotes (such as the Philips Pronto) to control all of your equipment with Remote (IR) receivers (including special 'discrete' remote codes your brand-name remote doesn't include!). For example, the USB-UIRT could transmit the discrete 'Input 3' code to your TV to directly switch it to input 3, rather than cycling through all of the inputs.
==Technical Details==
===IR Reception===
* 34-40KHz Frequency Range
* 56KHz IR Receiver Add-On Option*
* UIR-compatible Receiver Mode
* >8 Meter Sensitivity
* IR Wavelength Filtered
* USB Wake-from-Standby Capability
* Built-in wideband IR detector for accurate Learning, including carrier frequency.
* USB Wake-from-Standby Capability

===IR Transmission===

* 20-60KHz Frequency Range
* Two (2) built-in High-Power Emitters
* 1/8" Mini-Jack for External Emitters
* UIRT-compatible Struct and Raw modes
* Extended-length code support in hardware (up to 96burst-pairs)
* Max-length burst code support in driver (up to 2048 burst-pairs)

===Dimensions===

* 2.4"W x 1.5"D x 0.7"H

==See also==
* http://www.mythtv.org/wiki/index.php/USB-UIRT

Automatic diskless boot of media directors

2008-01-15T09:30:04Z

Mog: /* PXE-Boot hangs up, looping...... */

[[Category: Tutorials]]
[[Category: Networking]]
[[Category: Programmer's Guide]]
{| align="right"
| __TOC__
|}
LinuxMCE allows [[media director]]s to be booted over the network. This means that you can boot up thin clients without hard drives, or systems with other operating systems without affecting what is already on the disk.

==How to set it up==
===Enable PXE boot===
This is also known as network boot and can be accessed in your computer's [http://en.wikipedia.org/wiki/BIOS BIOS]. The exact procedure varies depending on your PC. Normally you press F2 or DEL right after turning the PC on to enter the BIOS settings. There is then usually an advanced option to enable this.

===Set the correct boot order===
You are also going to want to set the boot order in the BIOS so the network boot comes first, and your hard drive second. However most BIOS's will make you first enable network boot, save your changes, restart the computer, and then enter the BIOS settings a second time to set the boot order.

===Determine your network card's MAC address===
When network boot is working you should see at bootup the PC's mac address, and a messages about trying to contact a DHCP server, or trying to find a network boot image. This will be a new message you didn't see before and it means network boot is active on the PC. It will usually try for about 10 seconds to do a network boot image, and then give up and boot off the hard drive. This is what you want. When you see the message that it is trying to do the network boot, write down the mac address.

You can also get the mac address in Windows by running IPCONFIG command prompt, or in Linux by typing ifconfig as root from a console or a terminal.

===Setup the media director in LinuxMCE===
In LinuxMCE Admin go to '''Wizard > Devices > Media Directors'''. Add the media director if this is a new one, and set the mac address. The mac address should be a series of six 2 character sequences separated by colons, like this: 1A:00:F2:21:23:9F

Click 'update' to save your changes, and then click 'Setup Diskless Media Directors'. Wait for the popup window to finish. If this is a new media director you just added, go to Wizard, Restart and click 'Quick Reload Router' so the Router is aware of this new device.

===Boot up from the network===
Now turn on the PC. You should see that it gets an IP address and boots into the media director software. The first time you boot it, it can take up to 30 minutes to boot because it will be installing a lot of the software on the diskless image on the core, and it will also need to generate a user interface.

Once it's up, use the '''Wizard > Devices > Media Directors''' page to set the display resolution and also choose extra software you want to run on that Media Director with the 'Edit Computing Applications' button.

==How to use it==
[[Using LinuxMCE]]. If this media director has a hard drive in it that contains another operating system (like Windows or Linux), then from the media director's on-screen orbiter, or from any other orbiter that is currently controlling that media director, hit the 'power' button and choose 'restart as windows/linux' to boot up the computer off the hard drive and use it like a normal PC. Then choose 'restart as LinuxMCE' from the orbiter to boot it back again into LinuxMCE.

==Troubleshooting==
===PXE-Boot hangs up, looping......===

I got an Asus A7N8X-deluxe board, with two NICs onboard, when I connect one of them the md tries to boot via PXE, everything seems to go its way, until, the line: filename tftpboot/pxelinux.0 comes up, for about 20 seconds and after this.
After this, the last block written:

IP-Config eth0 complete (from 192.168.1.23)
adr: 192.168.80.255 broadcast: 192.168.80.255 netmask: 255.255.255.0
gateway: 192.168.80.1 dns0: 192.168.80.1 dns1: 0.0.0.0
rootserver: 192.168.80.1 rootpath: filename tftpboot/pxelinux.0

is repeated about hours in a really fast way.....

====Answer====
It is switching nics on you during the pxe boot. Disabling one of the on-board nics.

:''Source: http://forum.linuxmce.org/index.php?topic=3521.0''

==GRUB PXE network boot==
In some situations, it may be more appropriate to use GNU GRUB bootloader:

#The machine does not support PXE booting directly (no boot-ROM).
#You can use a GRUB bootmenu to decide wheter you want to boot LMCE or the native OS.
#Booting is a lot faster when you boot the native OS by skipping the network step.
#GRUB allows for easy adjustments of the boot parameters at boottime.

This is described in detail at [[GRUB PXE network boot]].

==Programmer's guide==
The network boot images are contained in /usr/pluto/diskless/[deviceID]. If a network image is corrupted, just delete that directory, and re-run 'Setup Diskless Media Directors'.

When the user hits the power button to change which device is booted, the command is sent to "General Info Plugin", which updates /tftpboot/pxelinux.cfg/01-[mac address]. That file contains a line KERNEL or LOCALBOOT 0, depending on what the user wants to boot. If it's LOCALBOOT 0, then when the media director tries to do a network boot the Core will tell it to boot off the hard drive instead. General Info Plugin then sends the App Server running on that machine a command to reboot.

Since there is both a Linux and Windows version of App Server, if App Server is installed and running on the Windows PC, then LinuxMCE can still reboot it remotely back into the network boot even if it's running Windows. Also the Windows App Server utility gives you a tray icon to switch back to network boot.

==Other Network Cards==
If you get to the remote machine starting the boot process, but then fails with it unable to find eth0, the reason may be because the stock diskless image did not have your network card statically compiled. The linux image building process does allow for additional network modules to be loaded during the boot process. The installer that linuxmce uses builds this image from a base copy of the operating system (ubuntu) that is untar'd during the diskless setup process. It puts this into it's own directory that serves as a virtual harddrive for your diskless machine. In the /usr/pluto/diskless directory you should have a list of device numbers that correspond to your diskless machines. For example: '45' was the number for my diskless machine. Edit the file /usr/pluto/diskless/###/etc/initramfs-tools/modules and add on your nic's module. In my case I edit /usr/pluto/diskless/45/etc/initramfs-tools/modules and added sky2. Then run the /usr/pluto/bin/Diskless_InstallKernel.sh script with the device number (directory name) of your diskless machine. In my case "/usr/pluto/bin/Diskless_InstallKernel.sh 45". This script builds the initrd image and puts it in the proper place (symlinks it actually).

The driver used in my machine was the 'sky2' driver for Marvell Gigabit ethernet cards. Other drivers will be located in the /usr/pluto/diskless/xx/lib/modules/2.xxx/kernel/drivers/net/ directory.

Automatic diskless boot of media directors

2008-01-15T08:27:34Z

Mog: Add troubleshooting

[[Category: Tutorials]]
[[Category: Networking]]
[[Category: Programmer's Guide]]
{| align="right"
| __TOC__
|}
LinuxMCE allows [[media director]]s to be booted over the network. This means that you can boot up thin clients without hard drives, or systems with other operating systems without affecting what is already on the disk.

==How to set it up==
===Enable PXE boot===
This is also known as network boot and can be accessed in your computer's [http://en.wikipedia.org/wiki/BIOS BIOS]. The exact procedure varies depending on your PC. Normally you press F2 or DEL right after turning the PC on to enter the BIOS settings. There is then usually an advanced option to enable this.

===Set the correct boot order===
You are also going to want to set the boot order in the BIOS so the network boot comes first, and your hard drive second. However most BIOS's will make you first enable network boot, save your changes, restart the computer, and then enter the BIOS settings a second time to set the boot order.

===Determine your network card's MAC address===
When network boot is working you should see at bootup the PC's mac address, and a messages about trying to contact a DHCP server, or trying to find a network boot image. This will be a new message you didn't see before and it means network boot is active on the PC. It will usually try for about 10 seconds to do a network boot image, and then give up and boot off the hard drive. This is what you want. When you see the message that it is trying to do the network boot, write down the mac address.

You can also get the mac address in Windows by running IPCONFIG command prompt, or in Linux by typing ifconfig as root from a console or a terminal.

===Setup the media director in LinuxMCE===
In LinuxMCE Admin go to '''Wizard > Devices > Media Directors'''. Add the media director if this is a new one, and set the mac address. The mac address should be a series of six 2 character sequences separated by colons, like this: 1A:00:F2:21:23:9F

Click 'update' to save your changes, and then click 'Setup Diskless Media Directors'. Wait for the popup window to finish. If this is a new media director you just added, go to Wizard, Restart and click 'Quick Reload Router' so the Router is aware of this new device.

===Boot up from the network===
Now turn on the PC. You should see that it gets an IP address and boots into the media director software. The first time you boot it, it can take up to 30 minutes to boot because it will be installing a lot of the software on the diskless image on the core, and it will also need to generate a user interface.

Once it's up, use the '''Wizard > Devices > Media Directors''' page to set the display resolution and also choose extra software you want to run on that Media Director with the 'Edit Computing Applications' button.

==How to use it==
[[Using LinuxMCE]]. If this media director has a hard drive in it that contains another operating system (like Windows or Linux), then from the media director's on-screen orbiter, or from any other orbiter that is currently controlling that media director, hit the 'power' button and choose 'restart as windows/linux' to boot up the computer off the hard drive and use it like a normal PC. Then choose 'restart as LinuxMCE' from the orbiter to boot it back again into LinuxMCE.

==Troubleshooting==
===PXE-Boot hangs up, looping......===

I got an Asus A7N8X-deluxe board, with two NICs onboard, when I connect one of them the md tries to boot via PXE, everything seems to go its way, until, the line: filename tftpboot/pxelinux.0 comes up, for about 20 seconds and after this.
After this, the last block written:

IP-Config eth0 complete (from 192.168.1.23)
adr: 192.168.80.255 broadcast: 192.168.80.255 netmask: 255.255.255.0
gateway: 192.168.80.1 dns0: 192.168.80.1 dns1: 0.0.0.0
rootserver: 192.168.80.1 rootpath: filename tftpboot/pxelinux.0

is repeated about hours in a really fast way.....

Source: http://forum.linuxmce.org/index.php?topic=3521.0

====Answer====
It is switching nics on you during the pxe boot. Disabling one of the on-board nics.

==GRUB PXE network boot==
In some situations, it may be more appropriate to use GNU GRUB bootloader:

#The machine does not support PXE booting directly (no boot-ROM).
#You can use a GRUB bootmenu to decide wheter you want to boot LMCE or the native OS.
#Booting is a lot faster when you boot the native OS by skipping the network step.
#GRUB allows for easy adjustments of the boot parameters at boottime.

This is described in detail at [[GRUB PXE network boot]].

==Programmer's guide==
The network boot images are contained in /usr/pluto/diskless/[deviceID]. If a network image is corrupted, just delete that directory, and re-run 'Setup Diskless Media Directors'.

When the user hits the power button to change which device is booted, the command is sent to "General Info Plugin", which updates /tftpboot/pxelinux.cfg/01-[mac address]. That file contains a line KERNEL or LOCALBOOT 0, depending on what the user wants to boot. If it's LOCALBOOT 0, then when the media director tries to do a network boot the Core will tell it to boot off the hard drive instead. General Info Plugin then sends the App Server running on that machine a command to reboot.

Since there is both a Linux and Windows version of App Server, if App Server is installed and running on the Windows PC, then LinuxMCE can still reboot it remotely back into the network boot even if it's running Windows. Also the Windows App Server utility gives you a tray icon to switch back to network boot.

==Other Network Cards==
If you get to the remote machine starting the boot process, but then fails with it unable to find eth0, the reason may be because the stock diskless image did not have your network card statically compiled. The linux image building process does allow for additional network modules to be loaded during the boot process. The installer that linuxmce uses builds this image from a base copy of the operating system (ubuntu) that is untar'd during the diskless setup process. It puts this into it's own directory that serves as a virtual harddrive for your diskless machine. In the /usr/pluto/diskless directory you should have a list of device numbers that correspond to your diskless machines. For example: '45' was the number for my diskless machine. Edit the file /usr/pluto/diskless/###/etc/initramfs-tools/modules and add on your nic's module. In my case I edit /usr/pluto/diskless/45/etc/initramfs-tools/modules and added sky2. Then run the /usr/pluto/bin/Diskless_InstallKernel.sh script with the device number (directory name) of your diskless machine. In my case "/usr/pluto/bin/Diskless_InstallKernel.sh 45". This script builds the initrd image and puts it in the proper place (symlinks it actually).

The driver used in my machine was the 'sky2' driver for Marvell Gigabit ethernet cards. Other drivers will be located in the /usr/pluto/diskless/xx/lib/modules/2.xxx/kernel/drivers/net/ directory.

UpdateMedia

2008-01-15T05:50:01Z

Mog:

UpdateMedia is a daemon that constantly scans for media files in the /home/public and each /home/user_xxx folder which is created for each family member, and any media is added to the pluto_media database, File table, and attributes and cover art go into the Attribute and Picture tables. Under /home/public and /home/users_xxx is a data subfolder which contains the actual video, audio, pictures folders. The /home/user_xxx directories themselves will contain system files for each user, like email boxes, and the main login for that user. That's why there's a 'data' subfolder.

* Learn more about [[How are media files organized? | media files are organized]].

You can start/stop the UpdateMedia daemon from a console with this command:
/usr/pluto/bin/UpdateMediaDaemonControl.sh -enable|-disable

[[Category: LinuxMCE Devices]]

Source Code

2008-01-15T05:36:18Z

Mog: /* Obsolete Source */

'''LinuxMCE''' is a pretty big project. Not counting [[GSD]] devices, LinuxMCE's own code is already well over a million lines in hundreds of modules, with over 1,000 pages of online documentation, and in addition LinuxMCE also incorporates lots of other big open source projects like [[Asterisk]], [[Xine]], [[MythTV]], [[Firefox]], [http://www.videolan.org/ VideoLan], [http://www.slimdevices.com/pi_features.html SlimServer], [http://www.kubuntu.org/ Kubuntu Linux] itself, etc., all of which have special LinuxMCE 'wrappers' to allow them to work together seamlessly as a total home solution. For the brave of heart, you can also download modules by hand, and see all the dependencies and compatibility for each module.

=Current Source=
You can browse the [http://svn.charonmedia.com/trac.cgi/browser LinuxMCE source] at the [http://svn.charonmedia.com/ Charon Media Trac website]. Or you can download it from SVN:
<pre>
# Download snapshot (391MiB)
wget http://www.charonmedia.org/lmce-1465.tbz

# Test checksum to ensure it was downloaded intact.
md5sum lmce-1465.tbz # should be b3d4b3f6b33ff5e6c4641390f2314095

# Update snapshot (uncompressed: 1823MiB either snapshot or updated).
tar xfj lmce-1465.tbz
cd lmce
svn update

# Build from source (optional) to 3692MiB, total source+build = 5515MiB.
./configure
make
</pre>

The old version of the source code description (of the old SVN) could be a good starting point for identifying what each of the code in the current SVN does, but it's no guarantee. An updated version of that description would be very useful.

=Obsolete Source=
This section refers to the obsolete sourcecode stored at SourceForge. The current (recent 0704 and all 0710) source is stored at Charon Media, as mentioned in [[#Current_Source]]. The descriptions of the obsolete code might also be wrong descriptions of the current structure and content of the source code, but it could be a clue where none others exist, because that's where the current source code evolved from. (- [[User:Matthew|Matthew]] 08:51, 10 January 2008 (MST))

You can browse the [http://linuxmce.svn.sourceforge.net/viewvc/linuxmce/trunk/ web based repository viewer]. Or you can do an anonymous svn checkout as follows:

svn co <nowiki>http://</nowiki>linuxmce.svn.sourceforge.net/svnroot/linuxmce/trunk/''modulename''

You can checkout all the software with if you use http://linuxmce.svn.sourceforge.net/viewvc/linuxmce/trunk/ as the repository location for the module name, or go to the [http://linuxmce.svn.sourceforge.net/viewvc/linuxmce/trunk/ repository viewer] to find the name of the SVN directory for the module you are interested in.

Here are short instructions if you want compile your module with svn sources : [[Building_From_Source|Building from source]].

----

I've made a start at some pointers to finding your way around the code. [Note, I'm a noob here, so I may have got this wrong, so feel free to add/change. Also, it's by no means complete yet!]

'''''trunk/config-pkgs/''''' contains ...
* ''intel8x0/'' -
'''''trunk/installers/''''' contains ...
* ''CD_Installer/'' -
* ''Installers/'' -
* ''PhoneInstall/'' -
* ''WindowsInstaller/'' -
'''''trunk/libs/''''' contains ...
* ''CrossPlatform/'' -
* ''Libraries/'' -
'''''trunk/src/''''' contains ...
* ''ANSI-to-HTML/ '' -
* ''AVWizard/ '' -
* ''Add_Software/ '' -
* ''App_Server/ '' -
* ''AptUtils/ '' -
* ''Asterisk/ '' -
* ''BD/ '' -
* ''Basic_XML_Data_Source_Plugin/ '' -
* ''Bluetooth_Dongle/ '' -
* ''BootScripts/ '' -
* ''CDDB_Identifier/ '' -
* ''CM11A/ '' -
* ''CheckDependencyScript/ '' -
* ''CliUtils/ '' -
* ''Climate_Plugin/ '' -
* ''ColorSplitter/ '' -
* ''ConfirmDependencies/ '' -
* ''ConfirmDependencies_Script/ '' -
* ''ConfirmDependencies_Script_Offline/ '' -
* ''CreateDevice/ '' -
* ''Crystal_Fontz_USBRS232/ '' -
* ''DCE/ '' -
* ''DCEGen/ '' -
* ''DCERouter/ '' -
* ''Datagrid_Plugin/ '' -
* ''Dhcpd-Plugin/ '' -
* ''DiskMonitor/ '' -
* ''Disk_Drive/ '' -
* ''Disk_Drive_Functions/ '' -
* ''Diskless-Add-Ons/ '' -
* ''DynamicDNS/ '' -
* ''EIB/ '' -
* ''Event_Plugin/ '' -
* ''FakeEPG/ '' -
* ''File_Grids_Plugin/ '' -
* ''Firewire2Video4Linux/ '' -
* ''FirewireVideo/ '' -
* ''GalleryViewer/ '' -
* ''Gen_Devices/ '' -
* ''General_Info_Plugin/ '' -
* ''Generic_Serial_Device/ '' -
* ''GyrationMouse/ '' -
* ''HAL/ '' -
* ''HAL_DeviceFinder/ '' -
* ''HDHomeRun/ '' -
* ''Hooks_rcS/ '' -
* ''IR/ '' -
* ''IRBase/ '' -
* ''IRTrans/ '' -
* ''Infrared_Plugin/ '' -
* ''JobHandler/ '' -
* ''LIRC_DCE/ '' -
* ''Lighting_Plugin/ '' -
* ''Linphone/ '' -
* ''MaemoOrbiterLauncher/ '' -
* ''MakeRelease/ '' -
* ''MakeRelease_PrepFiles/ '' -
* ''Media_Live_LCDButtons/ '' -
* ''Media_Plugin/ '' -
* ''MessageSend/ '' -
* ''MessageTranslation/ '' -
* ''Motion_Wrapper/ '' -
* ''MythTV_Backend_Proxy/ '' -
* ''MythTV_Player/ '' -
* ''MythTV_PlugIn/ '' -
* ''Network_Storage/ '' -
* ''NewMD_interactor/ '' -
* ''Orbiter/ '' -
* ''OrbiterGen/ '' -
* ''Orbiter_Plugin/ '' -
* ''OutlookSync/ '' -
* ''Photo_Screen_Saver/ '' -
* ''Plug_And_Play_Plugin/ '' -
* ''PlutoDHCP/ '' -
* ''PlutoMO/ '' -
* ''PlutoRaidTools/ '' -
* ''PlutoStorageDevices/ '' -
* ''PlutoUpdateSystem/ '' -
* ''PlutoUpgradeHelper/ '' -
* ''PlutoUtils/ '' -
* ''PlutoVIP/ '' -
* ''Powerfile_C200/ '' -
* ''Proxy_Orbiter/ '' -
* ''Qos/ '' -
* ''RA/ '' -
* ''RemoteAssistance/ '' -
* ''SDL_Helpers/ '' -
* ''SMPTE_Fountain/ '' -
* ''STEngine/ '' -
* ''SVNLog/ '' -
* ''SambaScan/ '' -
* ''ScreenGen/ '' -
* ''Security_Plugin/ '' -
* ''Serial/ '' -
* ''SerializeClass/ '' -
* ''Setup_CaptureCards/ '' -
* ''Setup_SoundCards/ '' -
* ''SimplePhone/ '' -
* ''SlimServer_PlugIn/ '' -
* ''Slim_Server_Streamer/ '' -
* ''SoundScripts/ '' -
* ''Speech/ '' -
* ''Splitter/ '' -
* ''Telecom_Plugin/ '' -
* ''TestSerialPort/ '' -
* ''Test_Treo/ '' -
* ''Text_To_Speech/ '' -
* ''Tira/ '' -
* ''Tribune/ '' -
* ''Tribunexml/ '' -
* ''UPnP/ '' -
* ''USB_PNP/ '' -
* ''USB_UIRT_0038/ '' -
* ''UbuntuDiskless/ '' -
* ''Ubuntu_Helpers/ '' -
* ''UpdateEntArea/ '' -
* ''UpdateMedia/ '' -
* ''VDR/ '' -
* ''VDRPlugin/ '' -
* ''VFD_LCD/ '' -
* ''VIPDesign/ '' -
* ''VIPEstablishment/ '' -
* ''VIPServer/ '' -
* ''VIPShared/ '' -
* ''VideoLan_Client/ '' -
* ''VideoLan_PlugIn/ '' -
* ''VideoLan_Server/ '' -
* ''VoiceMailMonitor/ '' -
* ''WinBluetooth/ '' -
* ''Windows_Share_Scanner/ '' -
* ''X-KbLayout/ '' -
* ''X-Resolution/ '' -
* ''XML_Data_Handler_Plugin/ '' -
* ''XinePlayerTest/ '' -
* ''Xine_Player/ '' -
* ''Xine_Plugin/ '' -
* ''bin/ '' -
* ''convert_color/ '' -
* ''convert_mac/ '' -
* ''convert_time/ '' -
* ''database/ '' -
* ''database_audi/ '' -
* ''database_marbella/ '' -
* ''designer/ '' -
* ''docs/ '' -
* ''drivers/ '' -
* ''fakepkgs/ '' -
* ''gc100/ '' -
* ''inotify/ '' -
* ''kernel-upgrade/ '' -
* ''lib/ '' -
* ''mce-installer/ '' -
* ''mce-launcher/ '' -
* ''pluto-ati-drivers/ '' -
* ''pluto-nvidia-drivers/ '' -
* ''pluto_gcs-2.6_module/ '' -
* ''pluto_main/ '' -
* ''pluto_media/ '' -
* ''pluto_media_updater/ '' -
* ''pluto_security/ '' -
* ''pluto_speech/ '' -
* ''pluto_telecom/ '' -
* ''pnp_detection_scripts/ '' -
* ''shift_state/ '' -
* ''skins/ '' -
* ''so_postinst/ '' -
* ''sql2cpp/ '' -
* ''sqlCVS/ '' -
* ''ussp-push/ '' -
* ''utilities/ '' -
* ''BuildWinBinaries.bat '' -
* ''Construct '' -
* ''MakeRelease_All.bat '' -
* ''MakeRelease_Symbian_S60.bat '' -
* ''MakeRelease_Windows.bat '' -
* ''MakeRelease_WindowsCE.bat '' -
* ''Makefile '' -
* ''Makefile_all '' -
* ''SwitchToLinuxMCE.bat '' -
* ''SwitchToPluto.bat '' -
* ''build.xml '' -
* ''pluto.sln '' -
'''''trunk/ubuntu''''' contains ...
* ''asterisk/'' -
* ''libsdl1.2-1.2.10/'' -
* ''libsdl1.2-1.2.7+1.2.8cvs20041007/'' -
* ''lirc-pluto-0.1/'' -
* ''lshwd-2.0-rc4/'' -
* ''mtx-1.3.10/'' -
* ''tee-pluto/'' -
* ''xine-lib-1.1.3/'' -
'''''trunk/web''''' contains the two web-based configuration programs:
* ''Amp'' - The Asterisk (IP Phone exchange) management program
* ''pluto-admin'' - LinuxMCE Web Admin

[[Category:Development]]

Display Drivers

2008-01-15T03:06:30Z

Mog: /* Microscopic fonts in KDE */

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

An incomplete HowTo on updating LinuxMCE to the latest display drivers and configuring them manually. It could use your help, so if something is different in your situation, please add it.

'''Note that this should normally not be necessary unless you have specific wishes or trouble getting your display to work properly.'''

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

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

For more information see also the [http://wiki.cchtml.com/index.php/Main_Page Unofficial ATI Linux Driver Wiki] and you might want to have a look at [http://www.mythtv.org/wiki/index.php/AtiProprietaryDriver AtiProprietaryDriver] in the MythTV wiki as well since LinuxMCE depends on it for viewing TV. MythTV in turn relies heavily on the support of certain features by the graphics drivers. The ATI drivers turn out to be a bit "challenged" in this area to say the least.

=== NVidia Chipsets ===
There are several ways to install NVidia drivers, the way described here is meant as a guide to install the very latest drivers from the NVidia website. Note that this way will bypass the LinuxMCE (Kubuntu) packaging system, possibly removing and/or overwriting some of it's files.

1. Go to a console (text) terminal by holding [CTRL]-[ALT] and pressing the [F1] key simultaneously, log in with the user account you have created during the Kubuntu install and become root, if you haven't done so already.
'''<you>@dcerouter:~$''' sudo -s
2. Download the latest [http://www.nvidia.com/object/unix.html linux drivers from NVidia] (depending [http://www.nvidia.com/object/IO_32667.html on your hardware], one of versions: 100.14.23, 1.0-9639 or 1.0-7185 currently), if you haven't done so already. When you have found the URL for downloading the package on the nvidia site you could download it like this:
'''root@dcerouter:~#''' wget <nowiki>http://us.download.nvidia.com/XFree86/Linux-x86/</nowiki>''<version>''<nowiki>/NVIDIA-Linux-x86-</nowiki>''<version>''<nowiki>-pkg1.run</nowiki>
3. Go to runlevel 1 to stop the currently running X-server.

NB: There was no need for me to run this command as I was already in Level 1 - It just locked up the keyboard. --[[User:Mortar|Mortar]] 18:12, 6 January 2008 (MST)
'''root@dcerouter:~#''' telinit 1
4. Execute the installer and follow instructions. Ignore the warning about runlevel 1 and don't bother looking for precompiled drivers.
'''root@dcerouter:~#''' sh NVIDIA-Linux-x86-''<version>''-pkg1.run
5. Now it needs to be configured. The recommended and most convenient way is to use the [[AVWizard]]. For more advanced setup, or if the AVWizard for some reason is unable to set your up your screens to your liking, you can configure the ''X-server'' manually by editing the ''xorg.conf'' file directly.

=== Intel Chipsets ===
There is a renewed interest in the Intel graphics chipsets since Intel released the drivers under the GPL. However, they're still not at the same level as nVidia's and can't do alpha blending.

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

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

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

=== Via Chipsets ===
Use the Openchrome or Via Unichrome drivers. The Via Unichrome drivers can be downloaded from http://www.viaarena.com/default.aspx?PageID=2&OSID=45&CatID=3220

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

== Configuration ==
The recommended and most convenient way is to use the [[AVWizard]]. For more advanced setup, or if the X-server (and thus also the AVWizard) is unable to start, you can configure the ''X-server'' manually by editing the ''xorg.conf'' file directly.

=== Getting started ===
Start by making a backup copy of the ''/etc/X11/xorg.conf'' file (even if it doesn't work it might contain settings you could need). In this example we will start from scratch and edit the configuration file step by step to get the main display setup.

Some of these steps require that there will be no X-server active on the system, the easiest way to achieve this is to boot in ''rescue-mode'', just hit [Esc] when [[Grub]] tells you to during the startup of your machine and select the right line from the menu. Another way is to go to a text-mode console (aka. terminal) with [CTRL]-[ALT]-[F1], [[Logging In|log in]], become root and issue the command:
telinit 1
This wil stop the running X-server and drop you into rescue mode as well.

One of the advantages is that now you can start and stop the X-server by hand with an alternative configuration file and without having to reboot or even start an entire desktop environment.

=== Generating a template ===
These instructions were originally written for ATI chipsets, so they might need to be adjusted and updated a bit. Not all of the specific options may be relevant for your chipset.

'''While there is no (other) X-server running''' you can create a template configuration file by running:
X -configure
This will create a file called xorg.conf.new in your ''home'' directory, test it with the following command and hit [CTRL]-[ALT]-[Backspace] when done:
X -config ~/xorg.conf.new
Within a few seconds a gray bitpattern should show up with an 'X' shaped mouse cursor. If the screen is distorted or reports the refresh rate to be out of range then you will either have to specify the proper refreshrate limitations for your screen or insert "modelines" for the resolution(s) you want to use (see below).

When you're satisfied you can overwrite ''/etc/X11/xorg.conf'' with this file to make it the default (you did make a backup didn't you?), once you have done that you can use "startx" to test and have the use of your desktop as well. This should at least be enough to allow the use of a graphic configuration tool (like the [[AVWizard]] for instance) to set up your display further. More advanced manual configuration options can be found below.

Here is an example of such a generated file:

Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
RgbPath "/etc/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/X11R6/lib/X11/fonts/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/X11R6/lib/X11/fonts/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
Load "extmod"
Load "record"
Load "xtrap"
Load "dri"
Load "glx"
Load "dbe"
Load "GLcore"
Load "type1"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection

Section "Device"
### Available Driver options are:-
### Values: : integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "ShadowFB" # [<bool>]
#Option "DefaultRefresh" # [<bool>]
#Option "ModeSetClearScreen" # [<bool>]
Identifier "Card0"
Driver "vesa"
''VendorName "ATI Technologies Inc"''
''BoardName "ATI Radeon Xpress 1200 Series"''
''BusID '''"PCI:1:5:0"'''''
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

Note that the only thing really specific to my setup in this config file is ''BusID'', if you only have one graphics adapter in your system this value can be omitted, otherwise the value(s) can be found with:
X -scanpci
Where each card will need it's own Device Section in the config file. The "VendorName" and "BoardName" settings are just labels and serve no real purpose other then being able to identify this particular device, which is usefull if you have more then one.

We'll be using this sample configuration as a starting point in the other examples below, the comments (lines starting with ''#'' can be safely removed as well as the ''"Display"'' subsections for the colordepths we don't plan on using.

=== Refresh rate / ModeLine ===
The easiest way to sort this problem is to let the X-server figure this out by not specifying the limits of your screen. However this often fails, leaving you with an unusable display. Simply look up '''your screen''''s refresh rates in the documentation and add them like this:

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
''HorizSync '''27-102''' # kHz''
''VertRefresh '''50-160''' # Hz''
EndSection

Alternatively you could specify a "ModeLine" for each resolution you want to use. By using ModeLines you have much finer controll over the timings of the output signal generated by your videocard. The drawback is that the timing values can be hard to get right.

Search the web for a "modeline generator", and many of these will include instructions on how to add the modeline, but briefly, you just add it to the "Monitor" section. Read the [http://en.wikipedia.org/wiki/Modeline wikipedia entry] to learn how to use modelines.
* http://koala.ilog.fr/cgi-bin/nph-colas-modelines
* http://xtiming.sourceforge.net/cgi-bin/xtiming.pl
* http://www.bohne-lang.de/spec/linux/modeline/
* http://amlc.berlios.de/
If one modeline doesn't work perfectly, try another, perhaps from another generator, because they can vary so much.

Using the wrong timings could in some (nowadays rare) occasions damage the hardware of your screen, so if it looks garbeled don't leave it like that for hours on end but hit [Ctrl]-[Alt]-[←Backspace] and readjust your settings. Most modern screens however simply report that the signal is out of range if this happens.

=== Colordepth and resolution ===
Specify the colordepth and resolution(s) you would like to use, like this:

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
''DefaultDepth '''24'''''
SubSection "Display"
Viewport 0 0
Depth 24
''Virtual '''1600 1200'''''
''Modes '''"1600x1200" "1280x1024" "1024x768" "800x600" "640x480" "512x384" "400x300" "320x240"'''''
EndSubSection
EndSection

As most people will only be using 24 bits anyway, I have removed the other redundant subsections. "Virtual" is the size of your desktop and "Modes" are physical resolutions, you can flip through these by holding [CTRL]-[ALT] and pressing the plus or minus on the numeric keypad. These are just examples, most people will only want to specify the resolution they actually use.

=== DRI device permissions ===
This section is needed to have the X-server set the proper permissions on the DRI device during startup. Simply add it to the end of the /etx/X11.xorg file if it isn't there already.

Section "DRI"
Mode 0666
EndSection

=== Chipset driver ===
Change "'''vesa'''" to "'''fglrx'''" (or "'''ati'''", depending on which drivers you installed earlier), as shown below, the old line is left as a comment in this example for clarity, but it's better to remove it as some scripts seem to find it confusing. For Nvidia chipsets use '''nvidia''' or '''nv''' as the driver names (instead of '''fglrx''').

Section "Device"
Identifier "Card0"
''# Driver "'''vesa'''"''
''Driver "'''fglrx'''"''
VendorName "ATI Technologies Inc"
BoardName "ATI Radeon Xpress 1200 Series"
BusID "PCI:1:5:0"
EndSection

If your X-server was running you will have to restart it completely for the changes to take effect, the easiest and most thorough way to do this is to reboot.

=== Physical display size ===
Like specifying the refresh rate his is optional but sometimes necessary, most of the time it is either detected or some sane defaults are used but sometimes it isn't, which can result in unreadable font sizes.

Section "Monitor"
...
DisplaySize '''155 95'''
EndSection

Where you have to replace the numbers with the physical '''width''' and '''height''' of your screen in millimeters (1" = 25mm), feel free to try mine, however these are for a small touchscreen.

=== Disable composite ===
Aparently the ATI '''fglrx''' driver does not ''yet'' support composite with DRI. So if you are using the fglrx driver, disable it by adding this to the end of the /etx/X11.xorg file if it isn't there already.

Section "Extensions"
Option "Composite" "Disable"
EndSection

=== Additional options ===
To be continued, I don't think this is enough to get UI2 completely (either mode) going yet. Feel free to jump in anytime...

Things still to sort out amongst others (i.e. what is it, do we need it and what are the settings if any):

Section "Module"
Load "i2c"
Load "bitmap"
Load "ddc"
Load "freetype"
Load "int10"
Load "vbe"
Load "speedo"
Load "type1"
Load "dbe"
Load "glx"
Load "v4l"
EndSection

Section "ServerFlags"
Option "AIGLX" "off"
EndSection

Section "Extensions"
Option "Composite" "Disable"
# Option "RENDER" "true"
EndSection

Option "PseudoColorVisuals" "off"
Option "OpenGLOverlay" "off"
Option "VideoOverlay" "off"
Option "DesktopSetup" "clone"

TV-out options, 2nd display, etc.

== Troubleshooting ==

=== X-windows won't start for AVWizard ===

*One problem on nvidia-cards could be that it does not detect the right monitor.

::Go to Console 1 ([Ctrl]+[Alt]+1) and edit /etc/X11/xorg.conf (nano -w /etc/X11/xorg.conf). Find the section ::Device with the driver nvidia add the line <pre>Option "ConnectedMonitor" "XXX"
::where XXX is CRT, CRT-0, CRT-1, DVI-0, DVI-1, ...</pre>
::Save and exit (nano: Ctrl+x) and restart the computer. In my case it was "CRT-1".
* Screen is black, after install seemed to go okay. You may have even seen the Kubuntu splash screen.
**[[AVWizard]]

=== X-windows won't start ===

Reboot into rescue-mode if needed (hit [Esc] when [[Grub]] tells you to), and restore a working copy of your /etc/X11/xorg.conf, or edit it by hand to fix the problem. Test it with the command "X" and press [Ctrl]-[Alt]-[←Backspace] simultaneous to quit (alternative: use "startx" and get the full desktop, if any), then reboot when it works and you're done.

=== Signal out of range ===

See ''[[#Refresh rate / ModeLine ]]'' above.

=== Microscopic fonts in KDE ===

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

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

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

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

To achieve this the following steps are required:

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

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

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

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

Add a line containing '''exit''' to the top of the ''/usr/pluto/bin/Xconfigure.sh'' file.

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

Display Drivers

2008-01-15T02:52:00Z

Mog: /* Microscopic fonts in KDE */

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

An incomplete HowTo on updating LinuxMCE to the latest display drivers and configuring them manually. It could use your help, so if something is different in your situation, please add it.

'''Note that this should normally not be necessary unless you have specific wishes or trouble getting your display to work properly.'''

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

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

For more information see also the [http://wiki.cchtml.com/index.php/Main_Page Unofficial ATI Linux Driver Wiki] and you might want to have a look at [http://www.mythtv.org/wiki/index.php/AtiProprietaryDriver AtiProprietaryDriver] in the MythTV wiki as well since LinuxMCE depends on it for viewing TV. MythTV in turn relies heavily on the support of certain features by the graphics drivers. The ATI drivers turn out to be a bit "challenged" in this area to say the least.

=== NVidia Chipsets ===
There are several ways to install NVidia drivers, the way described here is meant as a guide to install the very latest drivers from the NVidia website. Note that this way will bypass the LinuxMCE (Kubuntu) packaging system, possibly removing and/or overwriting some of it's files.

1. Go to a console (text) terminal by holding [CTRL]-[ALT] and pressing the [F1] key simultaneously, log in with the user account you have created during the Kubuntu install and become root, if you haven't done so already.
'''<you>@dcerouter:~$''' sudo -s
2. Download the latest [http://www.nvidia.com/object/unix.html linux drivers from NVidia] (depending [http://www.nvidia.com/object/IO_32667.html on your hardware], one of versions: 100.14.23, 1.0-9639 or 1.0-7185 currently), if you haven't done so already. When you have found the URL for downloading the package on the nvidia site you could download it like this:
'''root@dcerouter:~#''' wget <nowiki>http://us.download.nvidia.com/XFree86/Linux-x86/</nowiki>''<version>''<nowiki>/NVIDIA-Linux-x86-</nowiki>''<version>''<nowiki>-pkg1.run</nowiki>
3. Go to runlevel 1 to stop the currently running X-server.

NB: There was no need for me to run this command as I was already in Level 1 - It just locked up the keyboard. --[[User:Mortar|Mortar]] 18:12, 6 January 2008 (MST)
'''root@dcerouter:~#''' telinit 1
4. Execute the installer and follow instructions. Ignore the warning about runlevel 1 and don't bother looking for precompiled drivers.
'''root@dcerouter:~#''' sh NVIDIA-Linux-x86-''<version>''-pkg1.run
5. Now it needs to be configured. The recommended and most convenient way is to use the [[AVWizard]]. For more advanced setup, or if the AVWizard for some reason is unable to set your up your screens to your liking, you can configure the ''X-server'' manually by editing the ''xorg.conf'' file directly.

=== Intel Chipsets ===
There is a renewed interest in the Intel graphics chipsets since Intel released the drivers under the GPL. However, they're still not at the same level as nVidia's and can't do alpha blending.

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

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

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

=== Via Chipsets ===
Use the Openchrome or Via Unichrome drivers. The Via Unichrome drivers can be downloaded from http://www.viaarena.com/default.aspx?PageID=2&OSID=45&CatID=3220

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

== Configuration ==
The recommended and most convenient way is to use the [[AVWizard]]. For more advanced setup, or if the X-server (and thus also the AVWizard) is unable to start, you can configure the ''X-server'' manually by editing the ''xorg.conf'' file directly.

=== Getting started ===
Start by making a backup copy of the ''/etc/X11/xorg.conf'' file (even if it doesn't work it might contain settings you could need). In this example we will start from scratch and edit the configuration file step by step to get the main display setup.

Some of these steps require that there will be no X-server active on the system, the easiest way to achieve this is to boot in ''rescue-mode'', just hit [Esc] when [[Grub]] tells you to during the startup of your machine and select the right line from the menu. Another way is to go to a text-mode console (aka. terminal) with [CTRL]-[ALT]-[F1], [[Logging In|log in]], become root and issue the command:
telinit 1
This wil stop the running X-server and drop you into rescue mode as well.

One of the advantages is that now you can start and stop the X-server by hand with an alternative configuration file and without having to reboot or even start an entire desktop environment.

=== Generating a template ===
These instructions were originally written for ATI chipsets, so they might need to be adjusted and updated a bit. Not all of the specific options may be relevant for your chipset.

'''While there is no (other) X-server running''' you can create a template configuration file by running:
X -configure
This will create a file called xorg.conf.new in your ''home'' directory, test it with the following command and hit [CTRL]-[ALT]-[Backspace] when done:
X -config ~/xorg.conf.new
Within a few seconds a gray bitpattern should show up with an 'X' shaped mouse cursor. If the screen is distorted or reports the refresh rate to be out of range then you will either have to specify the proper refreshrate limitations for your screen or insert "modelines" for the resolution(s) you want to use (see below).

When you're satisfied you can overwrite ''/etc/X11/xorg.conf'' with this file to make it the default (you did make a backup didn't you?), once you have done that you can use "startx" to test and have the use of your desktop as well. This should at least be enough to allow the use of a graphic configuration tool (like the [[AVWizard]] for instance) to set up your display further. More advanced manual configuration options can be found below.

Here is an example of such a generated file:

Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
RgbPath "/etc/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/X11R6/lib/X11/fonts/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/X11R6/lib/X11/fonts/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
Load "extmod"
Load "record"
Load "xtrap"
Load "dri"
Load "glx"
Load "dbe"
Load "GLcore"
Load "type1"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection

Section "Device"
### Available Driver options are:-
### Values: : integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "ShadowFB" # [<bool>]
#Option "DefaultRefresh" # [<bool>]
#Option "ModeSetClearScreen" # [<bool>]
Identifier "Card0"
Driver "vesa"
''VendorName "ATI Technologies Inc"''
''BoardName "ATI Radeon Xpress 1200 Series"''
''BusID '''"PCI:1:5:0"'''''
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

Note that the only thing really specific to my setup in this config file is ''BusID'', if you only have one graphics adapter in your system this value can be omitted, otherwise the value(s) can be found with:
X -scanpci
Where each card will need it's own Device Section in the config file. The "VendorName" and "BoardName" settings are just labels and serve no real purpose other then being able to identify this particular device, which is usefull if you have more then one.

We'll be using this sample configuration as a starting point in the other examples below, the comments (lines starting with ''#'' can be safely removed as well as the ''"Display"'' subsections for the colordepths we don't plan on using.

=== Refresh rate / ModeLine ===
The easiest way to sort this problem is to let the X-server figure this out by not specifying the limits of your screen. However this often fails, leaving you with an unusable display. Simply look up '''your screen''''s refresh rates in the documentation and add them like this:

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
''HorizSync '''27-102''' # kHz''
''VertRefresh '''50-160''' # Hz''
EndSection

Alternatively you could specify a "ModeLine" for each resolution you want to use. By using ModeLines you have much finer controll over the timings of the output signal generated by your videocard. The drawback is that the timing values can be hard to get right.

Search the web for a "modeline generator", and many of these will include instructions on how to add the modeline, but briefly, you just add it to the "Monitor" section. Read the [http://en.wikipedia.org/wiki/Modeline wikipedia entry] to learn how to use modelines.
* http://koala.ilog.fr/cgi-bin/nph-colas-modelines
* http://xtiming.sourceforge.net/cgi-bin/xtiming.pl
* http://www.bohne-lang.de/spec/linux/modeline/
* http://amlc.berlios.de/
If one modeline doesn't work perfectly, try another, perhaps from another generator, because they can vary so much.

Using the wrong timings could in some (nowadays rare) occasions damage the hardware of your screen, so if it looks garbeled don't leave it like that for hours on end but hit [Ctrl]-[Alt]-[←Backspace] and readjust your settings. Most modern screens however simply report that the signal is out of range if this happens.

=== Colordepth and resolution ===
Specify the colordepth and resolution(s) you would like to use, like this:

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
''DefaultDepth '''24'''''
SubSection "Display"
Viewport 0 0
Depth 24
''Virtual '''1600 1200'''''
''Modes '''"1600x1200" "1280x1024" "1024x768" "800x600" "640x480" "512x384" "400x300" "320x240"'''''
EndSubSection
EndSection

As most people will only be using 24 bits anyway, I have removed the other redundant subsections. "Virtual" is the size of your desktop and "Modes" are physical resolutions, you can flip through these by holding [CTRL]-[ALT] and pressing the plus or minus on the numeric keypad. These are just examples, most people will only want to specify the resolution they actually use.

=== DRI device permissions ===
This section is needed to have the X-server set the proper permissions on the DRI device during startup. Simply add it to the end of the /etx/X11.xorg file if it isn't there already.

Section "DRI"
Mode 0666
EndSection

=== Chipset driver ===
Change "'''vesa'''" to "'''fglrx'''" (or "'''ati'''", depending on which drivers you installed earlier), as shown below, the old line is left as a comment in this example for clarity, but it's better to remove it as some scripts seem to find it confusing. For Nvidia chipsets use '''nvidia''' or '''nv''' as the driver names (instead of '''fglrx''').

Section "Device"
Identifier "Card0"
''# Driver "'''vesa'''"''
''Driver "'''fglrx'''"''
VendorName "ATI Technologies Inc"
BoardName "ATI Radeon Xpress 1200 Series"
BusID "PCI:1:5:0"
EndSection

If your X-server was running you will have to restart it completely for the changes to take effect, the easiest and most thorough way to do this is to reboot.

=== Physical display size ===
Like specifying the refresh rate his is optional but sometimes necessary, most of the time it is either detected or some sane defaults are used but sometimes it isn't, which can result in unreadable font sizes.

Section "Monitor"
...
DisplaySize '''155 95'''
EndSection

Where you have to replace the numbers with the physical '''width''' and '''height''' of your screen in millimeters (1" = 25mm), feel free to try mine, however these are for a small touchscreen.

=== Disable composite ===
Aparently the ATI '''fglrx''' driver does not ''yet'' support composite with DRI. So if you are using the fglrx driver, disable it by adding this to the end of the /etx/X11.xorg file if it isn't there already.

Section "Extensions"
Option "Composite" "Disable"
EndSection

=== Additional options ===
To be continued, I don't think this is enough to get UI2 completely (either mode) going yet. Feel free to jump in anytime...

Things still to sort out amongst others (i.e. what is it, do we need it and what are the settings if any):

Section "Module"
Load "i2c"
Load "bitmap"
Load "ddc"
Load "freetype"
Load "int10"
Load "vbe"
Load "speedo"
Load "type1"
Load "dbe"
Load "glx"
Load "v4l"
EndSection

Section "ServerFlags"
Option "AIGLX" "off"
EndSection

Section "Extensions"
Option "Composite" "Disable"
# Option "RENDER" "true"
EndSection

Option "PseudoColorVisuals" "off"
Option "OpenGLOverlay" "off"
Option "VideoOverlay" "off"
Option "DesktopSetup" "clone"

TV-out options, 2nd display, etc.

== Troubleshooting ==

=== X-windows won't start for AVWizard ===

*One problem on nvidia-cards could be that it does not detect the right monitor.

::Go to Console 1 ([Ctrl]+[Alt]+1) and edit /etc/X11/xorg.conf (nano -w /etc/X11/xorg.conf). Find the section ::Device with the driver nvidia add the line <pre>Option "ConnectedMonitor" "XXX"
::where XXX is CRT, CRT-0, CRT-1, DVI-0, DVI-1, ...</pre>
::Save and exit (nano: Ctrl+x) and restart the computer. In my case it was "CRT-1".
* Screen is black, after install seemed to go okay. You may have even seen the Kubuntu splash screen.
**[[AVWizard]]

=== X-windows won't start ===

Reboot into rescue-mode if needed (hit [Esc] when [[Grub]] tells you to), and restore a working copy of your /etc/X11/xorg.conf, or edit it by hand to fix the problem. Test it with the command "X" and press [Ctrl]-[Alt]-[←Backspace] simultaneous to quit (alternative: use "startx" and get the full desktop, if any), then reboot when it works and you're done.

=== Signal out of range ===

See ''[[#Refresh rate / ModeLine ]]'' above.

=== Microscopic fonts in KDE ===

See ''[[#Physical_display_size|Physical display size]]'' above.

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

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

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

To achieve this the following steps are required:

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

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

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

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

Add a line containing '''exit''' to the top of the ''/usr/pluto/bin/Xconfigure.sh'' file.

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

Controlling LinuxMCE

2008-01-13T02:54:45Z

Mog:

{{Stub}}
==Infrared remotes==
This is used to mean a method of communication over an invisible to our eye light beam. Most remotes use this technology to communicate. The downside is that you need direct line-of-site to get the message to the device.

* [[Control LinuxMCE using an Infrared remote]]
* [[:Category:Infrared]]

With the correct infrared receiver you can use any remote with LinuxMCE. If your remote isn't in the database you will need to [[Add support for new remote controls|configure it]]. The config will then be [[Share IR Codes|shared with other LinuxMCE users]].

If you want to control your A/V equiment, for example having LinuxMCE turn on your TV & amplifier and set the correct inputs you must have an Ir Blaster such as the [[USB UIRT]] or other compatible hardware.
:''Full article [[Control regular A/V equipment]]''

There are many infrared remotes that come with Ir Receiver that works well with LinuxMCE. For example [[Windows MCE Remote]] and [[Windows MCE Receiver]]

* [[Gc100]]
* http://www.mythtv.org/wiki/index.php/Using_an_IR_Blaster_with_MythTV
* http://en.wikipedia.org/wiki/Remote_control

==Specialized remotes==
* [[Nintendo WiiMote]]

==Orbiters==
[[Orbiters]] have displays. Basically orbiters aren't attached to a specific media director and can go from room to room.
* [[User Manual#Orbiters]]
===Handheld computers/PDAs===
* [[:Category:Orbiters]]

===Computers===
* [[Web Orbiter]] and [[Add Web Orbiter]]
* [[Windows]] orbiter. Runs on linux using wine.
* Keyboard & Mouse (media director)

Infrared Codes

2008-01-13T02:21:32Z

Mog: Add categories

LinuxMCE is building a very organized database of infrared codes. Please follow our structure since it means that all the existing menus and remotes will work with your equipment and will prevent everyone from needing to create their own screens and learn the same codes repeatedly. A/V devices and infrared codes you add are automatically merged into a master database unless you check the box on the A/V page 'Don't share my infrared codes with other users'.

First, add the commands that your device will support. Add the most common sets of commands for this type of device by checking the appropriate "Command Groups". Then choose "Add/Remove Commands" to add the less common commands. Please do not add new commands unless you are sure the command does not already exist. Our stock remote controls layouts send the standard commands. For example, when you hit the volume "UP" button on a phone or an Orbiter your device will receive the "Vol Up" command (or infrared code). If instead of using the stock "Vol Up" command you add your own command, like "Louder" or "Volume +", then your device will not work with any of the "stock" remotes and you will need to designer your own remote controls. Plus other users won't be able to use the codes you learn.

If a commands intended use is not clear, there with be a [?] tip that will explain it. For example, the single command "Skip Fwd - Channel/Track Greater" is used for changing channels on a TV/VCR/Cable Box, and tracks on a CD, chapters on a DVD, and station skip on a radio. This way a simple, generic remote with nothing but skip fwd/back and play/pause will still work logically with virtually any type of a/v device.

Also if you know the infrared group, which is based on the device codes used in all One-For-All, Radio Shack and other UEI remotes as explained at http://www.hifi-remote.com/ofa/codes.shtml, please choose it from the list. Although manufacturers build hundreds of different models, they generally all use the same codes. If you select this group, then only 1 user needs to learn the codes for a Sony TV, for example, and all other users with Sony TV's will be able to use the same codes without re-learning them. If you don't know the group, it's ok, but that means the codes will be filed/stored with your specific model--rather than the group--and then only other users with that exact same model will be able to use the codes.

For each command, the "Master Code" in LinuxMCE's database is highlighted blue. If there is a "Master Code" this is your best bet. If not, or if it doesn't work, try testing the codes other users have provided--they are in white. If they don't work, click "New Code" to learn or type in your own code, which will be in yellow. Please delete your code if it doesn't work so other users don't see it. Select the code that works best for your device. Once many users are successfully using a code it is automatically moved into the "Master Code" in blue.

[[Learning/typing my own code]]

Refer to the LinuxMCE [[AV Properties]] and [[IR/GSD codes syncronization]].

[[Category:Infrared]]
[[Category:Input]]

Controlling LinuxMCE

2008-01-12T09:36:55Z

Mog: /* Orbiters */

{{Stub}}
==Infrared remotes==
This is used to mean a method of communication over an invisible to our eye light beam. Most remotes use this technology to communicate. The downside is that you need direct line-of-site to get the message to the device.

* [[Control LinuxMCE using an Infrared remote]]
* [[:Category:Infrared]]

With the correct infrared receiver you can use any remote with LinuxMCE. If your remote isn't in the database you will need to [[Add support for new remote controls|configure it]]. The config will then be [[Share IR Codes|shared with other LinuxMCE users]].

If you want to control your A/V equiment, for example having LinuxMCE turn on your TV & amplifier and set the correct inputs you must have an Ir Blaster such as the [[USB UIRT]] or other compatible hardware.
:''Full article [[Control regular A/V equipment]]''

There are many infrared remotes that come with Ir Receiver that works well with LinuxMCE. For example [[Windows MCE Remote]] and [[Windows MCE Receiver]]

* [[Gc100]]
* http://www.mythtv.org/wiki/index.php/Using_an_IR_Blaster_with_MythTV
* http://en.wikipedia.org/wiki/Remote_control

==Specialized remotes==
* [[Nintendo WiiMote]]

==Orbiters==
[[Orbiters]] have displays. Basically orbiters aren't attached to a specific media director and can go from room to room.
===Handheld computers/PDAs===
* [[:Category:Orbiters]]

===Computers===
* [[Web Orbiter]] and [[Add Web Orbiter]]
* [[Windows]] orbiter. Runs on linux using wine.
* Keyboard & Mouse (media director)

Control LinuxMCE using an Infrared remote

2008-01-12T09:33:41Z

Mog: needs cleanup

{{cleanup}}

<h1>How to set it up</h1>
In LinuxMCE Admin choose Wizard, Devices, Media Directors. Choose the type of Infrared Receiver you have from the pull-down. The list of choices are LIRC drivers, so you can also refer to http://lirc.org/ for details. Most use the "default" driver. Then add all the "Infrared remote controls you will use". You can have as many as you want and they will all work. LinuxMCE Admin will then add 1 Infrared Receiver device, and 1 device for each remote control you added. After adding any new devices chose Wizard, Restart and click Quick Reload Router so LinuxMCE starts using that device.

<h1>How to use it</h1>
When the media director starts you will see a graphical user interface with a menu of buttons. This is the "Orbiter". It's the same user interface as on the web-pads and PDA's. The Orbiter that the media director displays on your TV we call the On-screen Orbiter, to distinguish from the other roving Orbiters like the PDA's and mobile phones. What the buttons on the infrared remote control do depends largely on what you see on the On-Screen Orbiter. LinuxMCE is intelligent enough to know that sometimes you push buttons to control the media director's Orbiter, and sometimes you push buttons to control whatever media device you're using. LinuxMCE will handle all the translation for you. In other words you can use one universal remote control to LinuxMCE and other A/V Equipment.

Here's an example. Let's say you have a media director, which is also controlling your satellite TV box as well as a regular DVD player. The media director is controlling both of them via Infrared. You have a universal remote control which you added to LinuxMCE as described above. The On-screen Orbiter is visible on the TV. As you hit the up/down/left/right/enter buttons on the remote you will see that you can select the menu options on the Orbiter. You select the button to watch "Satellite TV", and the TV appears. Now when you hit up/down/left/right/enter LinuxMCE knows you obviously want to control the satellite tv box. So, when you press those buttons LinuxMCE translates the infrared codes into ones that your satellite tv box understands, and you will see the same arrows on the same remote control are now controlling the satellite TV. You hit 'Power Off', and the satellite box shuts off, and the Orbiter's menu is again visible. Now the arrows are again controlling the Orbiter. You choose the button to watch a DVD in your DVD Player. Now the same arrows are controlling the DVD player. And when you hit 'pause' the DVD player will pause, even though you're holding the LinuxMCE remote--not the DVD remote. LinuxMCE is translating everything for you so you don't have to juggle remote controls. Again you hit 'power' and the DVD turns off. Hit 'power' again and the orbiter shuts the TV off. Hit 'power' a third time and the media director itself turns off. This is even better than a universal remote control since you don't need to tell it what device you want to control--LinuxMCE figures it out on its own.

Although you can use all sorts of remote controls, and all have different buttons, they will all control LinuxMCE in a consistent manner. The media-specific buttons, like rewind/fastforward, play/pause, etc., will always control whatever media device you are currently listening to no matter what screen is visible on the on-screen Orbiter. Navigation buttons, like up/down/left/right/enter and the 10-key number pad, will control the currently active media device if the On-screen Orbiter is showing the remote control for that device. Otherwise it controls the On-screen Orbiter. When the main menu is visible on the Orbiter you can select scenarios with the up/down/left/right/enter buttons, or the 10-key pad. To use the 10-key pad, hit the type of scenario you want: the categories are always numbered as follows: 1=Lighting, 2=Media, 3=Climate, 4=Telecom, 5=Security, 6=Misc Then when the list of those scenarios appears, hit the scenario you want, such as 2 for the 2nd scenario. Thus 22 on the remote will start TV (2=Media, TV is always the 2nd option).

You can use different remote controls that have completely different layouts, but they will still control LinuxMCE in a consistent manner. For example you can use a Bang & Olufsen remote which only has a single set of up/down/left/right buttons, and LinuxMCE knows that when there is a menu on screen those buttons should move the highlighter around on the screen, and when there is not a menu on screen, those buttons are used for rewind fast-forward and skip up/down. The logic is all handled automatically so for the user it is a very intuitive experience, allowing all sorts of different devices to be controlled with all sorts of different remote controls without having to do any setup.

== Programmer's Guide ==

Be sure to read the How To Use It section above first.

As you can see, LinuxMCE provides a highly intelligent interpretation of infrared remote buttons, that automatically change their function based on what the user is doing, what type of remote control layout exists, and where the infrared codes are going. If you have ever worked with infrared remote controls, such as LIRC, you know that there is no standard, and all the remote controls have different buttons with different names. Therefore we had to create a database structure that allows for interpreting the different button names into commands which can change depending upon the context and the layout of the remote.

The DCE Devices (i.e. the LinuxMCE binary that is run to handle i/r reception) are all of the category Peripherals, Infrared Receivers.

In LinuxMCE Admin choose Advanced > Device Templates, and you can see the categories and devices in them. There is a separate folder for the LIRC drivers. In addition to a device for the i/r receiver, there is also a device for the i/r remote. The remote controls are of the type Peripherals > Remote Controls. Since the definition of the infrared codes for a remote control is stored within the remote control device, and that definition varies depending upon the type of receiver, you will see there is a separate subcategory for each type of receiver.

For example there is a folder "LIRC Remote Controls" that has all of the remote controls and definition files for the LIRC project. We also created our own DCE devices for other infrared receivers, such as IRTrans and Tira. Although these are supported within the lirc project, we found that we had better control and greater accuracy when we used the native SDKs for these receivers. So, for example, if you have an IRTrans receiver, and an XPMC remote, you have two possibilities. First you could add the LIRC receiver device, and the XPMC remote device that is within the LIRC remote category. In this case the remote control will be using an LIRC config file. Secondly you could add LinuxMCE's native IRTrans receiver device, and then pick the XMPC remote device that is within the IRTrans remotes category, which stores the button codes in a different format, that is in IRTrans' native format. When you are adding your infrared receiver and remote control using the LinuxMCE Admin Wizard/Devices/Media Directors page, the wizard automatically ensures that when you add a remote control it is the correct category.

For each remote control there is a device data "#59 Configuration" which has the remote controls configuration file, which defined all the infrared codes at each button will send and gives each code, or button, a name. So the XPMC remote within the LIRC category has a device data #59 that is the LIRC config file. The XPMC remote within the IRTrans category has a device data #59 that is the same buttons/codes, but in IRTrans format.

When the framework starts an IR receiver device, iIn general this device will first scan for all sister devices within the category remote control, and write out a configuration file. So, for example, when LIRC_DCE runs it finds all LIRC remote controls on that machine, grabs the device data "#59 Configuration" for every one of them and writes that out to a lirc.conf file, and then starts LIRC.

All the logic is in a base class called IRReceiverBase. All of LinuxMCE's infrared receiver devices use this same base class. So the actual code that is specific to each type of receiver is very small, usually around 20 lines. It only needs to write out the configuration file at start up, and then call the member function ReceivedCode within IRReceiverBase when a button is pushed. This function takes the name of the button as a parameter, and converts this into a message.

Since all of the receivers use a common base class to handle the logic, that also means that all of the translation between buttons and actions is also in a shared database. It does not matter whether you are using LIRC or some other infrared receiver, the translation is the same. There is no unified standard for what the buttons are called. The button "SkipFwd" may be called "Fwd", "Skip+", "Jump->", etc. The table RemoteMapping in the main mysql database, pluto_main, has a field Mapping which lists all the button aliases, followed by the command to be executed when any of those buttons is pushed. For example: chup;skipfwd;ChanUp;SkipNext;|0 -106 1 65 5 +1

Whenever any infrared receiver reports any of those button presses, the message "0 -106 1 65 5 +1" gets fired. The format of the message is the same as if you typed it with the MessageSend utility: ie from device, to device message type, message id, followed by parameters.

So if the user presses a button called ChanUp, a message will be sent to device -106 (media plugin) of type 1 (command) id 65 (Jump Position In Playlist) with parameter 5 (Value To Assign) set to "+1". This table is shared amongst all LinuxMCE users, and is updated every time your system upgrades versions. If you make your own manual changes to this table then the next time your core upgrades it will not upgrade the rows in that table that you modified, because SQL CVS does not, by default, overwrite your local changes with global ones. Therefore, if you have a new remote control with some new buttons that we have not yet mapped, it is recommended that you e-mail us or post us a message in the forum, with the button name and the message and then we can add it to our master database and then your system can remain in sync with other users enhancements. If you want to do some mapping that is just for you, you can change the table and know your changes will not be overwritten.

You'll note that the RemoteMapping table has 2 optional fields: ScreenType and RemoteLayout. When the IRReceiverBase base class is deciding what message to send in response to button press, it first looks for a more specific entry where the screen type matches the type of screen currently visible on the orbiter, and the remote layout matches the layout. The on-screen orbiters regularly send messages to the infrared receiver telling them what type of screen is currently visible, using the following codes: M=Main Menu, m=other menu, R=LinuxMCE Remote, r=Non-LinuxMCE remote, F=File Listing. This allows for buttons to behave differently depending upon what type of screen is visible. For example when the main menu is visible, the arrows on a remote control should send a message to the on-screen orbiter to move the highlight pointer around on the screen. However when the user is controlling an external piece of AV equipment, like a DVD player, the arrows should pass through to the DVD player so the user can control its own on-screen menu. Also the type of functionality can vary depending upon the layout of the remote. For example, Bang & Olufsen remotes are quite simple, there is only a single up/down/left/right buttons which are used both to navigate on-screen menus as well as to handle rewind fast-forward and skip. Other remotes have dedicated arrows and media navigation buttons. So one remote layout can be created for Bang & Olufsen-style remote, where the arrows control the menu when there is a menu on screen, and adjust the media when there is not. The remote layout is a device data "#110 Remote Layout" stored with the remote control

When IRReceiverBase looks for a mapping it first looks for records that match the current screen type and remote layout, and then revert to standard records (ie ScreenType and RemoteLayout are null) only if there are no matching results.

See also [[Add support for new remote controls]]

[[Category:Infrared]]
[[Category: Programmer's Guide]]
[[Category: Tutorials]]

Controlling LinuxMCE

2008-01-12T09:30:47Z

Mog: /* Infrared remotes */

{{Stub}}
==Infrared remotes==
This is used to mean a method of communication over an invisible to our eye light beam. Most remotes use this technology to communicate. The downside is that you need direct line-of-site to get the message to the device.

* [[Control LinuxMCE using an Infrared remote]]
* [[:Category:Infrared]]

With the correct infrared receiver you can use any remote with LinuxMCE. If your remote isn't in the database you will need to [[Add support for new remote controls|configure it]]. The config will then be [[Share IR Codes|shared with other LinuxMCE users]].

If you want to control your A/V equiment, for example having LinuxMCE turn on your TV & amplifier and set the correct inputs you must have an Ir Blaster such as the [[USB UIRT]] or other compatible hardware.
:''Full article [[Control regular A/V equipment]]''

There are many infrared remotes that come with Ir Receiver that works well with LinuxMCE. For example [[Windows MCE Remote]] and [[Windows MCE Receiver]]

* [[Gc100]]
* http://www.mythtv.org/wiki/index.php/Using_an_IR_Blaster_with_MythTV
* http://en.wikipedia.org/wiki/Remote_control

==Specialized remotes==
* [[Nintendo WiiMote]]

==Orbiters==
Orbiters have displays. Basically orbiters aren't attached to a specific media director and can go from room to room.
===Handheld computers/PDAs===
* [[:Category:Orbiters]]

===Computers===
* [[Web Orbiter]] and [[Add Web Orbiter]]
* [[Windows]] orbiter. Runs on linux using wine.
* Keyboard & Mouse (media director)

Controlling LinuxMCE

2008-01-12T09:24:33Z

Mog:

{{Stub}}
==Infrared remotes==
This is used to mean a method of communication over an invisible to our eye light beam. Most remotes use this technology to communicate. The downside is that you need direct line-of-site to get the message to the device.

With the correct infrared receiver you can use any remote with LinuxMCE, provided you configure it.
* [[Control LinuxMCE using an Infrared remote]]
* [[Add support for new remote controls]]
* [[:Category:Infrared]]

If you want to control your A/V equiment, for example having LinuxMCE turn on your TV & amplifier and set the correct inputs you must have an Ir Blaster such as the [[USB UIRT]] or other compatible hardware.
:''Full article [[Control regular A/V equipment]]''

There are many infrared remotes that come with Ir Receiver that works well with LinuxMCE. For example [[Windows MCE Remote]] and [[Windows MCE Receiver]]

* [[Gc100]]
* http://www.mythtv.org/wiki/index.php/Using_an_IR_Blaster_with_MythTV
* http://en.wikipedia.org/wiki/Remote_control
* [[Share IR Codes]]

==Specialized remotes==
* [[Nintendo WiiMote]]

==Orbiters==
Orbiters have displays. Basically orbiters aren't attached to a specific media director and can go from room to room.
===Handheld computers/PDAs===
* [[:Category:Orbiters]]

===Computers===
* [[Web Orbiter]] and [[Add Web Orbiter]]
* [[Windows]] orbiter. Runs on linux using wine.
* Keyboard & Mouse (media director)

Windows MCE Remote

2008-01-12T09:20:55Z

Mog: /* Version 2 */

[[Category:Input]]
[[Category:Infrared]]

USB Remote intended for Media Center PCs
*Vendors Website: http://www.microsoft.com/hardware/mouseandkeyboard/productdetails.aspx?pid=065
*Supported by LinuxMCE when used with one of the supported [[:Category:Infrared |Infrared Receivers]].
== Media Center Remotes ==

{| border=1 cellspacing=0 cellpadding=2
|
| [[Image:MCEremote.jpg]]
| [[Image:MCE-Remote-2.jpg | Media Centre Remote 2]]
| [[Image:MCE-Remote-2-alt.jpg | Media Centre Remote 2 ALT]]
| [[Image:Mce-hauppauge.jpg | MCE Remote Hauppauge version]]
| [[Image:MCE-Remote-2-v1069.jpg | MCE Remote Hauppauge Windows Vista version]]
|-
| Version
| <center>1</center>
| <center>2</center>
| <center>2</center>
| <center>2</center>
| <center>2</center>
|-
| Model
| <center></center>
| <center>1039</center>
| <center>1039</center>
| <center>Hauppauge PVR- kit</center>
| <center>1069</center>
|-
| Features
| <center>Backlight</center>
| <center>Backlight</center>
| <center>Backlight</center>
| <center>"My" Buttons</center>
| <center>Uses mceusb2 lircd.conf</center>
|}

===Description===
There are two main versions of the MCE remote, typically referred to as the 'older' (Version 1) and 'newer' (Version 2) models. Both of these are now supported in the latest lirc, currently 0.8.1.

The newer remote comes in various alternatives, including different shapes and features. The new model is manufactured by Philips and half a dozen other manufacturers and is available by (among many other ways) purchase on it's own, shipped with MCE 2005 and contained in Hauppauge TV card MCE-Kits.

===Support===
====Version 2 ====
* [[Windows MCE Receiver|IR Receiver]] is supported
**The easiest method of installation is via the [[LinuxMCE Admin Website]]
***Click on [[Media Directors]]
***Scroll to the bottom of the list of configurable items for Infrared remote controls you will use and select "Windows XP MC Remote" from the drop down list which matches the [[:Category:Infrared |Infrared Receivers]] you have installed, this will automatically update the lircd.conf file.
***Reload the Router and you should be good to go.
* IR Transmitter is supported with driver module lirc_mceusb2 version >= 0.24 (lirc-0.8.2).
**However, the transmitter is not currently supported in LinuxMCE
* Version 1069 (black remote) comes with a new SMK IR receiver which requires new lirc_mceusb2 (Version 1.30)
** The new SMK IR receiver requires a newer version of LIRC than currently ships with LinuxMCE 704.
** Refer to the following forum posts for more information and possible fix:
*** http://forum.linuxmce.org/index.php?topic=2678.0
*** http://forum.linuxmce.org/index.php?topic=2517.0

==== Version 1 ====
* IR Receiver is supported
* IR Transmitter is not supported

==Troubleshooting==
# Currently the lircd.conf file is located in the /etc/lirc/ directory which is not where the scripts are trying to update the lircd.conf file. You need to go to the /etc/lirc directory and vi hardware.conf and add /ect/lircd.conf as the location of the lircd.conf file. Then cd into /etc directory and vi lircd.conf and save a blank file, now the scripts will be able to update the lircd.conf file with the appropriate remote control data.
# I have newer version of Windows MCE Remote, and I can not get it to work. Please refer to the following posts for possible solutions: http://forum.linuxmce.org/index.php?topic=2678.0 and http://forum.linuxmce.org/index.php?topic=2517.0

==See Also==
* [[Windows MCE Receiver]]
* http://www.mythtv.org/wiki/index.php/MCE_Remote

Windows MCE Remote

2008-01-12T09:19:22Z

Mog: /* See Also */

[[Category:Input]]
[[Category:Infrared]]

USB Remote intended for Media Center PCs
*Vendors Website: http://www.microsoft.com/hardware/mouseandkeyboard/productdetails.aspx?pid=065
*Supported by LinuxMCE when used with one of the supported [[:Category:Infrared |Infrared Receivers]].
== Media Center Remotes ==

{| border=1 cellspacing=0 cellpadding=2
|
| [[Image:MCEremote.jpg]]
| [[Image:MCE-Remote-2.jpg | Media Centre Remote 2]]
| [[Image:MCE-Remote-2-alt.jpg | Media Centre Remote 2 ALT]]
| [[Image:Mce-hauppauge.jpg | MCE Remote Hauppauge version]]
| [[Image:MCE-Remote-2-v1069.jpg | MCE Remote Hauppauge Windows Vista version]]
|-
| Version
| <center>1</center>
| <center>2</center>
| <center>2</center>
| <center>2</center>
| <center>2</center>
|-
| Model
| <center></center>
| <center>1039</center>
| <center>1039</center>
| <center>Hauppauge PVR- kit</center>
| <center>1069</center>
|-
| Features
| <center>Backlight</center>
| <center>Backlight</center>
| <center>Backlight</center>
| <center>"My" Buttons</center>
| <center>Uses mceusb2 lircd.conf</center>
|}

===Description===
There are two main versions of the MCE remote, typically referred to as the 'older' (Version 1) and 'newer' (Version 2) models. Both of these are now supported in the latest lirc, currently 0.8.1.

The newer remote comes in various alternatives, including different shapes and features. The new model is manufactured by Philips and half a dozen other manufacturers and is available by (among many other ways) purchase on it's own, shipped with MCE 2005 and contained in Hauppauge TV card MCE-Kits.

===Support===
====Version 2 ====
* IR Receiver is supported
**The easiest method of installation is via the [[LinuxMCE Admin Website]]
***Click on [[Media Directors]]
***Scroll to the bottom of the list of configurable items for Infrared remote controls you will use and select "Windows XP MC Remote" from the drop down list which matches the [[:Category:Infrared |Infrared Receivers]] you have installed, this will automatically update the lircd.conf file.
***Reload the Router and you should be good to go.
* IR Transmitter is supported with driver module lirc_mceusb2 version >= 0.24 (lirc-0.8.2).
**However, the transmitter is not currently supported in LinuxMCE
* Version 1069 (black remote) comes with a new SMK IR receiver which requires new lirc_mceusb2 (Version 1.30)
** The new SMK IR receiver requires a newer version of LIRC than currently ships with LinuxMCE 704.
** Refer to the following forum posts for more information and possible fix:
*** http://forum.linuxmce.org/index.php?topic=2678.0
*** http://forum.linuxmce.org/index.php?topic=2517.0

==== Version 1 ====
* IR Receiver is supported
* IR Transmitter is not supported

==Troubleshooting==
# Currently the lircd.conf file is located in the /etc/lirc/ directory which is not where the scripts are trying to update the lircd.conf file. You need to go to the /etc/lirc directory and vi hardware.conf and add /ect/lircd.conf as the location of the lircd.conf file. Then cd into /etc directory and vi lircd.conf and save a blank file, now the scripts will be able to update the lircd.conf file with the appropriate remote control data.
# I have newer version of Windows MCE Remote, and I can not get it to work. Please refer to the following posts for possible solutions: http://forum.linuxmce.org/index.php?topic=2678.0 and http://forum.linuxmce.org/index.php?topic=2517.0

==See Also==
* [[Windows MCE Receiver]]
* http://www.mythtv.org/wiki/index.php/MCE_Remote

Controlling LinuxMCE

2008-01-12T09:18:11Z

Mog: /* Infrared remotes */

{{Stub}}
==Infrared remotes==
This is used to mean a method of communication over an invisible to our eye light beam. Most remotes use this technology to communicate. The downside is that you need direct line-of-site to get the message to the device.

With the correct infrared receiver you can use any remote with LinuxMCE, provided you configure it.
* [[Infrared]]
* [[Control LinuxMCE using an Infrared remote]]
* [[Add support for new remote controls]]
* [[:Category:Infrared]]

If you want to control your A/V equiment, for example having LinuxMCE turn on your TV & amplifier and set the correct inputs you must have an Ir Blaster such as the [[USB UIRT]] or other compatible hardware.
:''Full article [[Control regular A/V equipment]]''

There are many infrared remotes that come with Ir Receiver that works well with LinuxMCE. For example [[Windows MCE Remote]] and [[Windows MCE Receiver]]

* [[Gc100]]
* http://www.mythtv.org/wiki/index.php/Using_an_IR_Blaster_with_MythTV
* http://en.wikipedia.org/wiki/Remote_control
* [[Share IR Codes]]

==Handheld computers/PDAs==
* [[:Category:Orbiters]]
==Computers==
* [[Web Orbiter]] and [[Add Web Orbiter]]
* [[Windows]] orbiter
* Keyboard & Mouse (media director)

==Specialized remotes==
* [[Nintendo WiiMote]]

Controlling LinuxMCE

2008-01-12T09:14:32Z

Mog:

{{Stub}}
==Infrared remotes==
This is used to mean a method of communication over an invisible to our eye light beam. Most remotes use this technology to communicate. The downside is that you need direct line-of-site to get the message to the device.

With the correct infrared receiver you can use any remote with LinuxMCE, provided you configure it.
[[Infrared]] [[Control LinuxMCE using an Infrared remote]] [[Add support for new remote controls]] [[:Category:Infrared]]

:Full article [[Control regular A/V equipment]]
If you want to control your A/V equiment, for example having LinuxMCE turn on your TV & amplifier and set the correct inputs you must have an Ir Blaster such as the [[USB UIRT]] or other compatible hardware.

* [[Windows MCE Remote]] and [[Windows MCE Receiver]]
* [[Gc100]]
* http://www.mythtv.org/wiki/index.php/Using_an_IR_Blaster_with_MythTV
* http://en.wikipedia.org/wiki/Remote_control

==Handheld computers/PDAs==
* [[:Category:Orbiters]]
==Computers==
* [[Web Orbiter]] and [[Add Web Orbiter]]
* [[Windows]] orbiter
* Keyboard & Mouse (media director)

==Specialized remotes==
* [[Nintendo WiiMote]]

Control A/V equipment with RS232/USB/Ethernet

2008-01-12T09:08:22Z

Mog:

[[Category: Serial]]
[[Category: Video]]
[[Category: Audio]]
[[Category: Automation]]
[[Category:Infrared]]
[[Category:Input]]

<h1>How to set it up</h1>
Normally LinuxMCE can control RS32 and Ethernet devices much better than infrared because the communication is more accurate. Also most devices controlled by those means are bi-directional, meaning that the device can tell LinuxMCE when the user does something manually. This allows LinuxMCE to monitor the devices and see if the user manually turn it on or off and try to anticipate what the user wants to do and automatically follow through. So whenever possible we encourage users to get A/V equipment with RS232 or Ethernet interfaces.

We have a device called "Generic Serial Device" to make it easy to add support for these devices. Add the device to the system just like normal, as explained [[Control a TV or cable/satellite box]]. Click the "Advanced" button on the A/VB equipment page to view the device settings, and click the view button next to the device template. Checked the box "Implements DCE", and put this in the command line: Generic_Serial_Device
Now on the A/V equipment page click the "IR/GSD codes" button. Add the commands you want to support just like you would for infrared equipment as explained [[Control regular A/V equipment]]. The only difference is that instead you'll be entering the data to send the device to execute the command, or Ruby snippets. Ruby as a simple programming language, yet pretty powerful and flexible. Some simple devices do not have a structured command protocol, you simply send them the string of data to execute a command. For example, click Advanced, Device Templates, Manufacturer: Denon, Category: A/V - Amps/receivers, Model: AVC-A1SRA (RS232), and click "Edit". Under "Infrared Groups", click the "Edit Commands" next to "Denon AVR/AVC protocol #1300". This is a simple protocol--no programming was required. To turn the device off you send it PWSTANDBY follwed by a carriage return. You'll see the syntax is: <$"PWSTANDBY\r"$> where <$"XXX"$> sends XXX to the device, and \r sends a carriage return. You'll see a little snippet of Ruby code for the "On" command. Since we wanted to always unmute the receiver when we turn it on, so it starts in a known state, we need to send PWON followed by MUOFF, but with a 2 second delay in between. While some technical skills are required to setup a serial device, you'll see this is much easier than requiring device drives to be written in C++ or other some other programming language.

Some devices are not so simple and they require a more complicated command protocol including checksums and so on.. For this you'll need to use Ruby. Refer to other similar GSD devices to see how it is done, or contact LinuxMCE to get assistance from one of our programmers.

<h1>How to use it</h1>
Just add a media scenario for the device, as explained [[Control a TV or cable/satellite box]]

<h1>Programmer's guide</h1>
The Ruby snippets used by GSD are stored in the InfraredGroup_Command table in the pluto_main, just like Infrared Codes. Also, if you leave "Share my codes" box checked, the GSD codes will be shared too. The logic for determining what GSD codes each device uses is in Infrared_Plugin. The command is Get Infrared Codes--exactly the same like retrieving infrared codes. The GSD (see src/Generic_Serial_Device) is a C++ DCE device that includes an embedded Ruby engine. Whenever it receives a command it forwards it to the Ruby processor. The intent is to have a very light way that non-programmers can add support for the thousands of generic serial devices out there.

Template:Cleanup

2008-01-12T09:06:31Z

Mog:

'''This article needs a cleanup'''

Control regular A/V equipment

2008-01-12T09:03:39Z

Mog: Add to Infrared category, mark for cleanup

{{Cleanup}}

<h1>How to set it up</h1>
First add the infrared transmitter on the Wizard, Devices, Interfaces page in LinuxMCE Admin. Then add your a/v devices on the Wizard, Devices, A/V Equipment page. [[Control a TV or cable/satellite box]] for an example of adding a TV, and creating a new Device Template if your model isn't already in the system.
On the A/V Equipment page issue specify for each device what infrared transmitter will be controlling it in the Controlled Via pulled down. If this device uses infrared codes, when you click the "A/V properties" button next to that device you should the "Uses I/R" box is checked. Confirm the inputs and other I/R settings, such as toggle vs. discrete are correct. If they are not, then whoever added the device template for this model originally may have done it wrong, or perhaps he had a different model. In either case you can create a new Device Template for your model as explained [[Control a TV or cable/satellite box]]. Then click the "IR/GSD codes" button to select or learn new infrared codes.

LinuxMCE includes a stock library of infrared codes supplied by other users. These codes are grouped, sometimes referred to as code sets or Infrared Groups. For example, Sony may make a thousand and models of TV sets, but nearly all of them use the same infrared codes; the remotes are interchangeable. Therefore it makes no sense to learn or input the infrared codes for every single model, rather it's much easier to put all the codes into a group called "Sony TV codes", and then only 1 user needs to add the codes, and then every other user with the Sony TV can use that set of codes. On the IR/GSD codes page you can select what Infrared Group, or codeset, you want to use for this device. All the codes are stored in Pronto format. If there are multiple Infrared Groups for that Manufacturer and Device Category, you can choose the one you want from the pull down, and then click the test code button next to one of the codes to see if the device responds. Worst case you need to create your own I/R codes. If an existing Infrared Group is correct, but there are just more new codes you need to add, choose the Infrared Group and then choose Add/remove commands. If none of the existing Infrared Groups are correct, you can create a new infrared group, or leave the Infrared Group pull-down empty and the codes you provide will be used only for this model, without belonging to an Infrared Group.

Check off one of the Command Groups check boxes to add groups of codes, such as Standard navigation, or volume control. Or click the add remove command buttons to add them individually. Try to use the existing command whenever possible; they are already quite complete. It is important to use the correct existing commands, even if your device gives them another name. For example, when you hit the channel up button on any remote-control, it will send to the "Skip Fwd - Channel/Track Greater" command to the device. Different remote controls call this function different things. Maybe yours calls it "Seek Up". If you create a new command called "Seek Up", then the existing remote-control which is designed to send our stock command will not work with your device, and you'll need to create a whole new remote control for your device. You don't want to do that. LinuxMCE Orbiter runs on web pads, pda's, phones, etc. We already have stock remote controls for all those types of devices that send our stock commands. Therefore it is much easier to use the existing commands even if the names are different than what you're device uses.

If your infrared device supports learning, then when you click the "new code" button on the I/R code page you'll be able to learn the code automatically. For example, if you're using the gc100, there is a learning dongle for it. Plug it into the gc100's port or into another serial port on the computer that is controlled in the gc100. On the gc100's device page, specify what serial port you're using in the "comm port parameter". If your device does not support learning, or is unable to learn the code correctly, then you'll need to get the code in pronto format on your own. One of the best sources is the http://www.remotecentral.com website. You can copy and paste the infrared codes from that website into the LinuxMCE Admin page. On the A/V equipment page if you leave the check box "Share my I/R codes with others" checked the infrared codes will automatically be shared with other users.

To test codes you can either do it by clicking the test code button from the infrared code page in LinuxMCE Admin, or by clicking the Advanced button on the orbiter, which is normally the LinuxMCE logo. On the Orbiter's advanced page is an option to test infrared codes. Note that to test i/r codes with that button on the orbiter only I/R codes that were already in the system before the last Router reload will work. This isn't the case with the [[LinuxMCE Admin Website[[, so, when setting up devices for the first time, the website is the preferred tool.

<h1>How to use it</h1>
Just add a media scenario for the device, as explained [[Control a TV or cable/satellite box]]

<h1>Programmer's guide</h1>
The logic for determining what infrared codes each device uses is in Infrared_Plugin. The command is Get Infrared Codes. Each infrared interface device, like the [[gc100]], should inherit from the MessageTranslation class which handles translating for toggle codes, proper formatting of numbers, etc.

[[Category:Tutorials]]
[[Category:Input]]
[[Category:Infrared]]

Controlling LinuxMCE

2008-01-12T09:00:37Z

Mog: /* Infrared remotes */

{{Stub}}
==Infrared remotes==
This is used to mean a method of communication over an invisible to our eye light beam. Most remotes use this technology to communicate. The downside is that you need direct line-of-site to get the message to the device.

With the correct infrared receiver you can use any remote.

* [[Infrared]]
* [[Control LinuxMCE using an Infrared remote]]
* [[Add support for new remote controls]]
* [[Windows MCE Remote]] and [[Windows MCE Receiver]]
* [[:Category:Infrared]]
* [[Gc100]]
* [[USB UIRT]] [[Control regular A/V equipment]]
* http://www.mythtv.org/wiki/index.php/Using_an_IR_Blaster_with_MythTV

==Handheld computers/PDAs==
* [[:Category:Orbiters]]
==Computers==
* [[Web Orbiter]] and [[Add Web Orbiter]]
* [[Windows]] orbiter
* Keyboard & Mouse (media director)

==Specialized remotes==
* [[Nintendo WiiMote]]

Controlling LinuxMCE

2008-01-12T08:53:56Z

Mog: /* Infrared remotes */

{{Stub}}
==Infrared remotes==
* [[Infrared]]
* [[USB UIRT]]
* [[Windows MCE Remote]]
* [[:Category:Infrared]]

==Handheld computers/PDAs==
* [[:Category:Orbiters]]
==Computers==
* [[Web Orbiter]] and [[Add Web Orbiter]]
* [[Windows]] orbiter
* Keyboard & Mouse (media director)

==Specialized remotes==
* [[Nintendo WiiMote]]

Controlling LinuxMCE

2008-01-12T08:53:34Z

Mog: /* Computers */

{{Stub}}
==Infrared remotes==
* [[Infrared]]
* [[USB UIRT]]
* [[Windows MCE Remote]]
* [[:Category:InfraRed]]
==Handheld computers/PDAs==
* [[:Category:Orbiters]]
==Computers==
* [[Web Orbiter]] and [[Add Web Orbiter]]
* [[Windows]] orbiter
* Keyboard & Mouse (media director)

==Specialized remotes==
* [[Nintendo WiiMote]]

Controlling LinuxMCE

2008-01-12T08:52:35Z

Mog: InfraRed -> Infrared

{{Stub}}
==Infrared remotes==
* [[Infrared]]
* [[USB UIRT]]
* [[Windows MCE Remote]]
* [[:Category:Infrared]]
==Handheld computers/PDAs==
* [[:Category:Orbiters]]
==Computers==
* [[Web Orbiter]] and [[Add Web Orbiter]]
* [[Windows]] orbiter
==Specialized remotes==
* [[Nintendo WiiMote]]

LinuxMCE:Community Portal:Category Proposal

2008-01-12T08:51:34Z

Mog:

[[Category: Categories]]

I've created this page to make a proposal of how to setup the categories for the wiki. Feel free to add/edit/comment.

*Computer Hardware
**Motherboards
**Graphic Cards
**Sound Cards
**TV-cards
**Keyboards
**Mice
**Remotes
**Bluetooth Devices
**Laptops

*PDAs and other Portable Devices except cell phones
**Webpads

*Software
**Third party software

*Audio Sources
**Receivers

*Video Sources
**Set-top boxes
***Satellite boxes
***Cable boxes
***Digital terrestrial boxes
***PVR boxes
**VCR
**DVD
**Blu-ray
**HD-Dvd
**Cameras
**TV-cards (also in computer hardware)

*Video Displays
**LCD
**Plasma
**Projectors

*Multimedia

*Networking

*Home Automation
**Lighting
**Climate
**Security (Maybe this should be it's own main category?)

*Telecom
**Cellullar phones (Mobile phones?)
**IP-phones
**Phone-Providers (or less obvious "Phone-Lines" as in the pluto-admin)

*Development

==Suggestion==
One thing I think is important is that articles must not appear once in a category and then again in a more general category. For example, Sony Amplifier should not appear once in 'audio hardware' and then again in 'hardware'. This is consistent with the [http://meta.wikimedia.org/wiki/MediaWiki_User%27s_Guide:_Using_Categories#Category_considerations guidelines for Wikimedia projects], which are very well thought through. [[User:Lozzo|Lozzo]] 13:33, 26 September 2007 (MST)

:I think it's important for articles to be in as many relevant categories as possible, this helps to navigate and find similar pages much quicker. Guidlines of other wikis don't apply here, just because some other unrelated wiki uses that organisation doesn't mean we have to. So please don't remove Categories from pages, they are there for a reason. --[[User:Zaerc|Zaerc]] 04:51, 3 October 2007 (MST)

::With respect, I completely disagree. Categories are there to facilitate an elegant taxonomy - not for things to be appearing twice. Having strict categories (i.e. without repetition and in the style used on wikipedia as the reslt of much community debate) makes things easier to maintain ''and'' to find. [[User:Lozzo|Lozzo]] 00:56, 7 October 2007 (MST)

:::The problem is that this is not the wikipedia (or wikimedia). And the resulting policy of much community debate there does not automaticly apply here. Things are not either hardware or a phone or an orbitter, they can be all three at once. Hence they should appear in all these relevant categories. Likewise a NAS should go under storage and networking as well as hardware. I think this makes them much easier to find and I really don't see how it could hinder maintenance --[[User:Zaerc|Zaerc]] 05:34, 7 October 2007 (MST)

==Expanding the existing structure==
It seems better to me, for the Hardware section at least, to take into account the existing structure, and expand on that. Implementing the proposal above will scatter the existing pages and leave many categories empty. As soon as certain categories become overcrowded they can be split into subcategories. Therefore with a few adjustments we can mostly leave things the way they are and expand it where needed. This should ease the pain of a transition as well.

Below is an expanded and slightly modified version of the existing stucture, this should be a lot less intrusive, and yes some categories appear as sub-categories again, I see no problem with that. Categories for future expansion are in brackets, to be created when there are enough pages to justify (fill) them. --[[User:Zaerc|Zaerc]] 04:51, 3 October 2007 (MST)

*[[:Category:Hardware|Hardware]]
**[[:Category:Audio|Audio]]
***(Receivers)
***(Sound Cards)
**[[:Category:Automation|Automation]]
***Cameras
***Climate
***InfraRed
***Security
***Serial
**[[:Category:Cameras|Cameras]]
**[[:Category:Climate|Climate]]
**[[:Category:Cores|Cores]]
**[[:Category:Displays|Displays]]
**[[:Category:Infrared|Infrared]]
**[[:Category:Input|Input]]
***Cameras
***InfraRed
***(Keyboards)
***(Mice)
***(Remotes)
***(TV Cards)
**[[:Category:Laptops|Laptops]]
**[[:Category:Mainboards|Mainboards]]
**[[:Category:Media Directors|Media Directors]]
**[[:Category:Networking|Networking]]
***(Network Adapters)
***(Network Attached Storage)
***(Wireless)
**[[:Category:Orbiters|Orbiters]]
***Phones <are '''all''' phones orbiters?>
***WebPads
***(PDAs)
**[[:Category:Phones|Phones]]
***(IP Phones)
***(USB Phones)
***(WiFi Phones)
**([[:Category:Phone Lines|Phone Lines]])
**[[:Category:Security|Security]]
**[[:Category:Serial|Serial]]
**[[:Category:Supported|Supported]]
**([[:Category:Storage|Storage]])
***(External Drives)
***(Network Attached Storage)
**[[:Category:Telecom|Telecom]]
***Phones
***(Phone Lines)
**[[:Category:TV Cards|TV Cards]]
**([[:Category:USB|USB]])
**[[:Category:Video|Video]]
***Cameras
***Displays
****(LCD)
****(Plasma)
****(Projectors)
***(Graphic Cards)
***TV Cards
**[[:Category:WebPads|WebPads]]

Windows MCE Receiver

2008-01-12T08:50:59Z

Mog: InfraRed -> Infrared

[[Category:Hardware]]
[[Category:Input]]
[[Category:Infrared]]

*Vendors Website: http://www.microsoft.com/hardware/mouseandkeyboard/productdetails.aspx?pid=065
*Supported by LinuxMCE

===Description===
There are two common version of the USB IR Receiver/Transmitter
#Phillips eHome Infrared Transceiver
#SMK eHome Infrared Transceiver
Both are supported in the latest version of LIRC
===Support===
* IR Receiver is supported
**The easiest method of installation is via the [[LinuxMCE Admin Website]]
***Click on [[Media Directors]]
***Scroll to the bottom of the list of configurable items for [[:Category:Infrared |Infrared Receivers]] and select mce_usb2 from the drop down list, this will automatically install the lirc modules and update the lircd.conf file.
***Reload the Router and you should be good to go.
* IR Transmitter is supported with driver module lirc_mceusb2 version >= 0.24 (lirc-0.8.2).
**However, the transmitter is not currently supported in LinuxMCE
===Troubleshooting===
1. Currently you need to run the following command in order to get the LIRC modules available for use
depmod -ae
modprobe lirc_mceusb2

Alternatively do the following at the Core to fix non-functioning IR on an MD;

Use Web Admin -> Wizard -> Devices -> Media Directors to get the id number of each MD (the number preceded by a #). The open a console session at the KDE desktop and type the following;

ssh moon<id number of MD> **this opens a console session on the MD**
depmod
reboot

This should allow the modules to be available and you should be able to use the remote control with the USB dongle included with the remote.

Windows MCE Remote

2008-01-12T08:50:33Z

Mog: InfraRed -> Infrared

[[Category:Input]]
[[Category:Infrared]]

USB Remote intended for Media Center PCs
*Vendors Website: http://www.microsoft.com/hardware/mouseandkeyboard/productdetails.aspx?pid=065
*Supported by LinuxMCE when used with one of the supported [[:Category:Infrared |Infrared Receivers]].
== Media Center Remotes ==

{| border=1 cellspacing=0 cellpadding=2
|
| [[Image:MCEremote.jpg]]
| [[Image:MCE-Remote-2.jpg | Media Centre Remote 2]]
| [[Image:MCE-Remote-2-alt.jpg | Media Centre Remote 2 ALT]]
| [[Image:Mce-hauppauge.jpg | MCE Remote Hauppauge version]]
| [[Image:MCE-Remote-2-v1069.jpg | MCE Remote Hauppauge Windows Vista version]]
|-
| Version
| <center>1</center>
| <center>2</center>
| <center>2</center>
| <center>2</center>
| <center>2</center>
|-
| Model
| <center></center>
| <center>1039</center>
| <center>1039</center>
| <center>Hauppauge PVR- kit</center>
| <center>1069</center>
|-
| Features
| <center>Backlight</center>
| <center>Backlight</center>
| <center>Backlight</center>
| <center>"My" Buttons</center>
| <center>Uses mceusb2 lircd.conf</center>
|}

===Description===
There are two main versions of the MCE remote, typically referred to as the 'older' (Version 1) and 'newer' (Version 2) models. Both of these are now supported in the latest lirc, currently 0.8.1.

The newer remote comes in various alternatives, including different shapes and features. The new model is manufactured by Philips and half a dozen other manufacturers and is available by (among many other ways) purchase on it's own, shipped with MCE 2005 and contained in Hauppauge TV card MCE-Kits.

===Support===
====Version 2 ====
* IR Receiver is supported
**The easiest method of installation is via the [[LinuxMCE Admin Website]]
***Click on [[Media Directors]]
***Scroll to the bottom of the list of configurable items for Infrared remote controls you will use and select "Windows XP MC Remote" from the drop down list which matches the [[:Category:Infrared |Infrared Receivers]] you have installed, this will automatically update the lircd.conf file.
***Reload the Router and you should be good to go.
* IR Transmitter is supported with driver module lirc_mceusb2 version >= 0.24 (lirc-0.8.2).
**However, the transmitter is not currently supported in LinuxMCE
* Version 1069 (black remote) comes with a new SMK IR receiver which requires new lirc_mceusb2 (Version 1.30)
** The new SMK IR receiver requires a newer version of LIRC than currently ships with LinuxMCE 704.
** Refer to the following forum posts for more information and possible fix:
*** http://forum.linuxmce.org/index.php?topic=2678.0
*** http://forum.linuxmce.org/index.php?topic=2517.0

==== Version 1 ====
* IR Receiver is supported
* IR Transmitter is not supported

==Troubleshooting==
# Currently the lircd.conf file is located in the /etc/lirc/ directory which is not where the scripts are trying to update the lircd.conf file. You need to go to the /etc/lirc directory and vi hardware.conf and add /ect/lircd.conf as the location of the lircd.conf file. Then cd into /etc directory and vi lircd.conf and save a blank file, now the scripts will be able to update the lircd.conf file with the appropriate remote control data.
# I have newer version of Windows MCE Remote, and I can not get it to work. Please refer to the following posts for possible solutions: http://forum.linuxmce.org/index.php?topic=2678.0 and http://forum.linuxmce.org/index.php?topic=2517.0

==See Also==
* http://www.mythtv.org/wiki/index.php/MCE_Remote

Category:InfraRed

2008-01-12T08:49:08Z

Mog:

Renamed to [[:Category:Infrared]]

Category:Infrared

2008-01-12T08:45:30Z

Mog:

[[Category: Hardware]]
[[Category: Input]]

Infrared devices and other related stuff should be here

Windows MCE Remote

2008-01-12T08:44:23Z

Mog: Category:InfraRed -> Infrared

[[Category:Input]]
[[Category:Infrared]]

USB Remote intended for Media Center PCs
*Vendors Website: http://www.microsoft.com/hardware/mouseandkeyboard/productdetails.aspx?pid=065
*Supported by LinuxMCE when used with one of the supported [[:Category:InfraRed |Infrared Receivers]].
== Media Center Remotes ==

{| border=1 cellspacing=0 cellpadding=2
|
| [[Image:MCEremote.jpg]]
| [[Image:MCE-Remote-2.jpg | Media Centre Remote 2]]
| [[Image:MCE-Remote-2-alt.jpg | Media Centre Remote 2 ALT]]
| [[Image:Mce-hauppauge.jpg | MCE Remote Hauppauge version]]
| [[Image:MCE-Remote-2-v1069.jpg | MCE Remote Hauppauge Windows Vista version]]
|-
| Version
| <center>1</center>
| <center>2</center>
| <center>2</center>
| <center>2</center>
| <center>2</center>
|-
| Model
| <center></center>
| <center>1039</center>
| <center>1039</center>
| <center>Hauppauge PVR- kit</center>
| <center>1069</center>
|-
| Features
| <center>Backlight</center>
| <center>Backlight</center>
| <center>Backlight</center>
| <center>"My" Buttons</center>
| <center>Uses mceusb2 lircd.conf</center>
|}

===Description===
There are two main versions of the MCE remote, typically referred to as the 'older' (Version 1) and 'newer' (Version 2) models. Both of these are now supported in the latest lirc, currently 0.8.1.

The newer remote comes in various alternatives, including different shapes and features. The new model is manufactured by Philips and half a dozen other manufacturers and is available by (among many other ways) purchase on it's own, shipped with MCE 2005 and contained in Hauppauge TV card MCE-Kits.

===Support===
====Version 2 ====
* IR Receiver is supported
**The easiest method of installation is via the [[LinuxMCE Admin Website]]
***Click on [[Media Directors]]
***Scroll to the bottom of the list of configurable items for Infrared remote controls you will use and select "Windows XP MC Remote" from the drop down list which matches the [[:Category:InfraRed |Infrared Receivers]] you have installed, this will automatically update the lircd.conf file.
***Reload the Router and you should be good to go.
* IR Transmitter is supported with driver module lirc_mceusb2 version >= 0.24 (lirc-0.8.2).
**However, the transmitter is not currently supported in LinuxMCE
* Version 1069 (black remote) comes with a new SMK IR receiver which requires new lirc_mceusb2 (Version 1.30)
** The new SMK IR receiver requires a newer version of LIRC than currently ships with LinuxMCE 704.
** Refer to the following forum posts for more information and possible fix:
*** http://forum.linuxmce.org/index.php?topic=2678.0
*** http://forum.linuxmce.org/index.php?topic=2517.0

==== Version 1 ====
* IR Receiver is supported
* IR Transmitter is not supported

==Troubleshooting==
# Currently the lircd.conf file is located in the /etc/lirc/ directory which is not where the scripts are trying to update the lircd.conf file. You need to go to the /etc/lirc directory and vi hardware.conf and add /ect/lircd.conf as the location of the lircd.conf file. Then cd into /etc directory and vi lircd.conf and save a blank file, now the scripts will be able to update the lircd.conf file with the appropriate remote control data.
# I have newer version of Windows MCE Remote, and I can not get it to work. Please refer to the following posts for possible solutions: http://forum.linuxmce.org/index.php?topic=2678.0 and http://forum.linuxmce.org/index.php?topic=2517.0

==See Also==
* http://www.mythtv.org/wiki/index.php/MCE_Remote

Windows MCE Receiver

2008-01-12T08:44:11Z

Mog:

[[Category:Hardware]]
[[Category:Input]]
[[Category:Infrared]]

*Vendors Website: http://www.microsoft.com/hardware/mouseandkeyboard/productdetails.aspx?pid=065
*Supported by LinuxMCE

===Description===
There are two common version of the USB IR Receiver/Transmitter
#Phillips eHome Infrared Transceiver
#SMK eHome Infrared Transceiver
Both are supported in the latest version of LIRC
===Support===
* IR Receiver is supported
**The easiest method of installation is via the [[LinuxMCE Admin Website]]
***Click on [[Media Directors]]
***Scroll to the bottom of the list of configurable items for [[:Category:InfraRed |Infrared Receivers]] and select mce_usb2 from the drop down list, this will automatically install the lirc modules and update the lircd.conf file.
***Reload the Router and you should be good to go.
* IR Transmitter is supported with driver module lirc_mceusb2 version >= 0.24 (lirc-0.8.2).
**However, the transmitter is not currently supported in LinuxMCE
===Troubleshooting===
1. Currently you need to run the following command in order to get the LIRC modules available for use
depmod -ae
modprobe lirc_mceusb2

Alternatively do the following at the Core to fix non-functioning IR on an MD;

Use Web Admin -> Wizard -> Devices -> Media Directors to get the id number of each MD (the number preceded by a #). The open a console session at the KDE desktop and type the following;

ssh moon<id number of MD> **this opens a console session on the MD**
depmod
reboot

This should allow the modules to be available and you should be able to use the remote control with the USB dongle included with the remote.

USB UIRT

2008-01-12T08:43:56Z

Mog: Category:InfraRed -> Infrared

Tira

2008-01-12T08:43:49Z

Mog: Category:InfraRed -> Infrared

[[Category: Hardware]]
[[Category: Automation]]
[[Category: Infrared]]
{{stub}}

Tira is an infrared transmitter for a PC.

==Sales pitch==
In many situations, it is necessary to be able to transmit IR signals from a PC. For example, if you use a PC as a TIVO or ReplayTV device, it would be great if a PC could automatically switch channels on a cable box. Also, in many home automation applications a PC needs to control various equipments around the house. Most of the equipment can be controlled by IR signals. That's why we decided to develop Tira, the Transmitting InfraRed Adapter.
It works with a popular program Girder and allows to capture IR codes right from the original remote and reproduce them later. Of course, it allows you to control applications running on a PC, as Ira-2 does.[http://www.home-electro.com/tira2.php]

Phillips eHome RC6ir

2008-01-12T08:43:44Z

Mog: Category:InfraRed -> Infrared

[[Category:Input]]
[[Category:Infrared]]

USB Remote intended for Windows Vista Media Center PCs

Packaged with the [[NMEDIAPC 600 BA]]. Does not plug and play in with LIRC, LinuxMCE, or MythTV.

IRTrans

2008-01-12T08:43:39Z

Mog: Category:InfraRed -> Infrared

[[Category: Hardware]]
[[Category: Automation]]
[[Category: Infrared]]

IRTrans is a German manufacturer of home control hardware, particularly relating to infrared.[http://www.irtrans.de/en/main.php]

==Sales pitch==
IR Trans transforms your PC into a programmable remote control: It learns the codes of your remote control, stores them in a database and sends them controlled by your applications. Furthermore you can control your PC with almost any remote control.

You are looking for a solution to integrate your existing Audio/Video equipment into your home automation system? - IRTrans is the most modern and flexible system for IR control with up to 256 zones. With IRTrans Bus Modules the system can be extended in a flexibel way at any time.

==Technical Information==
• To each USB or RS232 device up to 15 additional devices can be connected using the serial 2/3 wire bus.
• With up 16 RS232/USB Devices a total of max. 256 devices per PC is possible
• Each device has got an unique address that can be used to receive and send
• In addition the IRTrans system can relay IR codes from one room to another - even without a PC
• The serial 2/3 wire bus (3 wire including supply power) can be up to 50-80m long
• Simple telephone wire is suitable for the bus. Of course CAT5/6 can also be used
• Arbitrary topologies for the serial bus are possible: Star, bus or a combination
• The baudrate of the serial bus of up to 38,400 Baud guarantees a fast communication
• Using the serial bus LCD Displays can be connected in every room
• The system can be extended using IRTrans Bus Modules
• Attractive packets with all accessories allow for an easy entry
• The IRTrans software is based on a flexible TCP/IP client server architecture
• The devices can therefore be accessed via any LAN/WAN connection
• Several clients can connect to the server at the same time
• There are different ways available to integrate the system with EIB installations:

[http://www.irtrans.de/en/]

IMON PAD

2008-01-12T08:43:32Z

Mog: Category:InfraRed -> Infrared

[[Category: Hardware]]
[[Category: Input]]
[[Category: Infrared]]

== Adding Support Of iMON PAD remote control ==

[[Image:iMON_PAD_remote.jpg]]

iMON IR receiver is a part of many popular and nice looking HTPC cases such Silverstone LC16M and LC20M. But LinuxMCE doesn't support in from the box. That brief how to will help you add iMON PAD to your installation. Sure that approach can be applied to any LIRC remote.

== Adding new device template ==

<ol>
<li>Go to Advanced :: Configuration :: Device Templates, add new manufacture - SoundGraph, add a new template for that manufacture (choose LIRC Remote Control as Device Category)</li>
<li>In the new template add a property - '''Configuration''' and put there LIRC configuration file for iMON PAD, for example, you can use [http://smart-home-blog.com/wp-content/plugins/wp-downloadMonitor/download.php?id=7 that one] (modified according to LinuxMCE buttons mapping).
<li>Go to media director(s) page, press "Add Remote" and chose iMON PAD from the list.</li>
<li>Set "Infrared Receivers" as "default".</li>
<li>Quick reload router.</li>
</ol>

After router is up you should see that lirc package in your system:
<code>dpkg -l|grep lirc</code>
Also, a new log for the LIRC device will be available - <some_ID>_LIRC.log

'''Note:''' iMON remote control is supported by LIRC 0.8.1. But to use iMON PAD buttons we have to re-compile LIRC with applied [http://smart-home-blog.com/wp-content/plugins/wp-downloadMonitor/download.php?id=5 patch]:

<code>
tar xvjf lirc-0.8.1.tar.bz2 
CD lirc-0.8.0 
patch -p1 < ../lirc-imon-pad2keys.patch 
./configure 
make 
make install 
</code>

== Using iMON PAD remote control ==

Using PAD buttons: Up, Down, Left and Right it's possible to move from one menu item to another. Button 'Enter' is needed to choose desired item. Green button returns you to the main screen. Also, there are available numeric buttons from 0 to 9. Using them you can also choose menu item but PAD buttons are much efficient. For more information, have a look at [[Control LinuxMCE using an Infrared remote]]

== See also ==

<ul>
<li>[http://venky.ws/projects/imon Linux Drivers for Soundgraph iMON USB IR/VFD devices]</li>
<li>[http://brakemeier.de/electronics/vdr/lirc-imon.html LIRC iMON Patches]</li>
<li>[http://www.mythtv.org/wiki/index.php/Imon Configure iMON on MythTV]</li>
<li>[http://smart-home-blog.com/writes/configure-imon-padvfd-in-plutohome Configure iMon PAD/VFD in Plutohome]</li>
</ul>

GlobalCache GC-100

2008-01-12T08:43:22Z

Mog: Category:InfraRed -> Infrared

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

[[Image:GC100.jpg|right]]

GC100 is a device which allows you to have remote connection almost anywhere. It's a network device which will forward all your data to :
* couple of serial ports
* [[IR]] senders and/or sensors
* several relays
For more details about the product check [http://www.globalcache.com/products/gc-index.html manufacturer web site].

== Send IR codes ==
LinuxMCE implementation of GC100 assumes that in device tree we'll have children and the messages are actually addressed to them instead of GC100 itself.

So when you are sending "ON" to TV controlled by GC100, the message is routed to the GC100, it finds [[infrared]] code for "ON" for that specific TV, sends a command to gc100 to send a specific [[infrared]] sequence, which will blink IR sender connected to specific port, and the TV will turn on.

The only two commands that GC100 implements itself are : '''CMD_Send_Code''' used to test which IR is suitable for your equipment and '''CMD_Learn_IR''' used to learn new IR codes.

== Learn IR codes ==
The learning device is actually unrelated to GC100. It may be plugged into one of GC100's serial ports (don't forget to set them to 9600 bps), or in regular serial port, just be sure you specified right port in GC100 device data.

There are several other devices that support learning of infrared codes : [[IRTrans]], [[Tira]], [[USB_UIRT]].

Learning is done from [[LinuxMCE-admin|web page]]. When clicking "Learn" gc100 will start a thread that will try to get data from the port. If nothing is received in 30 seconds the thread will die. The page will continue to refresh trying to see if anything was added, but after 30 seconds it's useless.

== How to ==
=== Install ===
The device is not quite [[plug&play]]. You have to perform a factory reset and to add it from orbiter ("Add GC100" button).

A script will do some tricks with IP, will submit some pages on GC100's interface and so on. It will install needed software and after that it should say that device is ready to use (don't forget to [[quickreload]])

=== Before the first use ===
* Insert proper wires in relays, devices in serial ports, [[IR]] LEDs and/or sensors.
* Go to device's webpage and set proper inputs/outputs, baud rates and so on.
* Add child devices in [[LinuxMCE-admin]] webpage and set proper device data to match the wiring.

This should do it.

=== Known Problems ===

==== MAC detection ====

Currently the support for the gc100 in LinuxMCE is broken, at least for some models or firmware versions. The ''/usr/pluto/bin/gc100-conf.pl'' script is for some reason unable to determine the gc100's MAC Adress after it has been reset to factory defaults. As a result it is only half configured and not added to the system properly.

The only known workaround [http://smart-home-blog.com/archives/688] [http://forum.linuxmce.org/index.php?topic=1990.msg9161#msg9161] at this time is to manually edit the perl script, and hardcode the MAC address of your gc100. In short, find this line in the script:
sub get_gc100mac {
Then insert this line immediately following it (replace ''00:00:00:00:00:00'' with the adress of your gc100):
'''return "''00:00:00:00:00:00''";'''
As a result it should look something like this now:
exit(4);
}
}

sub get_gc100mac {

'''return "''00:00:00:00:00:00''"''';

`curl <nowiki>http://192.168.1.70/Commands.cgi</nowiki> -o gc100mac1 --silent`;
`curl <nowiki>http://192.168.1.101/Commands.cgi</nowiki> -o gc100mac2 --silent`;
open(FILE,"gc100mac1");
@data1 = <FILE>;
close(FILE);

Reset the gc100 to factory defaults if necessary and you should be able to add it from an orbiter as described above.

Another possible workaround ''might'' be described on the [http://plutohome.com/wiki/index.php/Gc100 Plutohome wiki for the gc100], under '''Complete Manual Install'''.

Firmware versions known to be affected:
* 2.4-06 (GC100-06)

==== Serial Port ====

The GC100's serial port does not work under LinuxMCE without a small modification, see: [http://forum.linuxmce.org/index.php?topic=2161.msg10140#msg10140 Re: GC100 + CM11 setup]

The following commands should correct this issue (and make a backup copy just in case):
mv /usr/pluto/bin/gc100-serial-bridge.sh /usr/pluto/bin/gc100-serial-bridge.sh.backup
sed -e 's/false/0/g' /usr/pluto/bin/gc100-serial-bridge.sh.backup >/usr/pluto/bin/gc100-serial-bridge.sh

It basicly replaces '''false''' with '''0''' in the ''/usr/pluto/bin/gc100-serial-bridge.sh'' file. Afterwards a reboot may be in order.

== Implementation details ==
In ''gc100.cpp'' there is a lot of code for format conversion and other stuff. Practically it's not a big deal it receives a command, find a proper IR sequence and sends it to gc100.

Fiire Chief

2008-01-12T08:43:14Z

Mog: Category:InfraRed -> Infrared

[[Category: Hardware]]
[[Category: Input]]
[[Category: Infrared]]
[[Category: Supported]]

[[Image:FiireChief.jpg|thumb|200px|Fiire Chief Remote Control]]

== Status ==
Supported by [http://www.fiire.com Fiire] (LMCE support) / [http://www.polywell.com Polywell Computers] (hardware).

== Features ==
* Wireless R/F gyro remote control specially designed for use with LinuxMCE.
* Universal I/R support for up to 3 legacy devices.
* Follow me function (requires additional USB dongles).

== Sales Pitch ==
The [[Fiire Chief]] controls both the [[Fiire Engine]] and the [[Fiire Station]]. It uses RF wireless, and has a range of approx. 50’. It is omni-directional and does not require line of site like an infrared remote. The FiireChief has all the traditional, legacy remote control buttons, as well as 3 specialized ‘gyro’ buttons in the middle that let you control every function using only those 3 buttons and gestural movements. It also has a built-in ‘follow-me’ feature. You can start media in one room, and when you want to move to another room, just take the remote with you and press ‘Follow-me’. Fiire is able to track each remote individually, so whatever media you started with that remote will follow that remote around the house. Your movies, TV and music effortlessly follow you as you move from room to room. And whenever you enter a room, the FiireChief instantly and automatically switches to control the devices in that room. So when you’re in the living room, the volume button controls the volume on the tv in the living room. Take the remote into the bedroom, and the volume button controls whatever tv is in the bedroom, whether or not it is the same brand as the one in the living room. The FiireChief is the only remote control you will need for every room in the home, and you don’t need to worry about which remote goes with which room since any remote can work in any room.

Additionally, the FiireChief has a universal i/r remote built-in with both pre-stored codes and learning. You can program up to 3 i/r devices to control with the ‘tv’, ‘aux’, and ‘cab/sat’ buttons at the top. In those modes, it acts like a normal, universal i/r remote.

The FiireChief includes one USB dongle which you connect to a Fiire Engine, Fiire Station, or other LinuxMCE PC running UI2.

== Where to buy ==

http://www.fiire.com/fiire-chief.php

Control LinuxMCE using an Infrared remote

2008-01-12T08:43:03Z

Mog: Category:InfraRed -> Infrared

<h1>How to set it up</h1>
In LinuxMCE Admin choose Wizard, Devices, Media Directors. Choose the type of Infrared Receiver you have from the pull-down. The list of choices are LIRC drivers, so you can also refer to http://lirc.org/ for details. Most use the "default" driver. Then add all the "Infrared remote controls you will use". You can have as many as you want and they will all work. LinuxMCE Admin will then add 1 Infrared Receiver device, and 1 device for each remote control you added. After adding any new devices chose Wizard, Restart and click Quick Reload Router so LinuxMCE starts using that device.

<h1>How to use it</h1>
When the media director starts you will see a graphical user interface with a menu of buttons. This is the "Orbiter". It's the same user interface as on the web-pads and PDA's. The Orbiter that the media director displays on your TV we call the On-screen Orbiter, to distinguish from the other roving Orbiters like the PDA's and mobile phones. What the buttons on the infrared remote control do depends largely on what you see on the On-Screen Orbiter. LinuxMCE is intelligent enough to know that sometimes you push buttons to control the media director's Orbiter, and sometimes you push buttons to control whatever media device you're using. LinuxMCE will handle all the translation for you. In other words you can use one universal remote control to LinuxMCE and other A/V Equipment.

Here's an example. Let's say you have a media director, which is also controlling your satellite TV box as well as a regular DVD player. The media director is controlling both of them via Infrared. You have a universal remote control which you added to LinuxMCE as described above. The On-screen Orbiter is visible on the TV. As you hit the up/down/left/right/enter buttons on the remote you will see that you can select the menu options on the Orbiter. You select the button to watch "Satellite TV", and the TV appears. Now when you hit up/down/left/right/enter LinuxMCE knows you obviously want to control the satellite tv box. So, when you press those buttons LinuxMCE translates the infrared codes into ones that your satellite tv box understands, and you will see the same arrows on the same remote control are now controlling the satellite TV. You hit 'Power Off', and the satellite box shuts off, and the Orbiter's menu is again visible. Now the arrows are again controlling the Orbiter. You choose the button to watch a DVD in your DVD Player. Now the same arrows are controlling the DVD player. And when you hit 'pause' the DVD player will pause, even though you're holding the LinuxMCE remote--not the DVD remote. LinuxMCE is translating everything for you so you don't have to juggle remote controls. Again you hit 'power' and the DVD turns off. Hit 'power' again and the orbiter shuts the TV off. Hit 'power' a third time and the media director itself turns off. This is even better than a universal remote control since you don't need to tell it what device you want to control--LinuxMCE figures it out on its own.

Although you can use all sorts of remote controls, and all have different buttons, they will all control LinuxMCE in a consistent manner. The media-specific buttons, like rewind/fastforward, play/pause, etc., will always control whatever media device you are currently listening to no matter what screen is visible on the on-screen Orbiter. Navigation buttons, like up/down/left/right/enter and the 10-key number pad, will control the currently active media device if the On-screen Orbiter is showing the remote control for that device. Otherwise it controls the On-screen Orbiter. When the main menu is visible on the Orbiter you can select scenarios with the up/down/left/right/enter buttons, or the 10-key pad. To use the 10-key pad, hit the type of scenario you want: the categories are always numbered as follows: 1=Lighting, 2=Media, 3=Climate, 4=Telecom, 5=Security, 6=Misc Then when the list of those scenarios appears, hit the scenario you want, such as 2 for the 2nd scenario. Thus 22 on the remote will start TV (2=Media, TV is always the 2nd option).

You can use different remote controls that have completely different layouts, but they will still control LinuxMCE in a consistent manner. For example you can use a Bang & Olufsen remote which only has a single set of up/down/left/right buttons, and LinuxMCE knows that when there is a menu on screen those buttons should move the highlighter around on the screen, and when there is not a menu on screen, those buttons are used for rewind fast-forward and skip up/down. The logic is all handled automatically so for the user it is a very intuitive experience, allowing all sorts of different devices to be controlled with all sorts of different remote controls without having to do any setup.

== Programmer's Guide ==

Be sure to read the How To Use It section above first.

As you can see, LinuxMCE provides a highly intelligent interpretation of infrared remote buttons, that automatically change their function based on what the user is doing, what type of remote control layout exists, and where the infrared codes are going. If you have ever worked with infrared remote controls, such as LIRC, you know that there is no standard, and all the remote controls have different buttons with different names. Therefore we had to create a database structure that allows for interpreting the different button names into commands which can change depending upon the context and the layout of the remote.

The DCE Devices (i.e. the LinuxMCE binary that is run to handle i/r reception) are all of the category Peripherals, Infrared Receivers.

In LinuxMCE Admin choose Advanced > Device Templates, and you can see the categories and devices in them. There is a separate folder for the LIRC drivers. In addition to a device for the i/r receiver, there is also a device for the i/r remote. The remote controls are of the type Peripherals > Remote Controls. Since the definition of the infrared codes for a remote control is stored within the remote control device, and that definition varies depending upon the type of receiver, you will see there is a separate subcategory for each type of receiver.

For example there is a folder "LIRC Remote Controls" that has all of the remote controls and definition files for the LIRC project. We also created our own DCE devices for other infrared receivers, such as IRTrans and Tira. Although these are supported within the lirc project, we found that we had better control and greater accuracy when we used the native SDKs for these receivers. So, for example, if you have an IRTrans receiver, and an XPMC remote, you have two possibilities. First you could add the LIRC receiver device, and the XPMC remote device that is within the LIRC remote category. In this case the remote control will be using an LIRC config file. Secondly you could add LinuxMCE's native IRTrans receiver device, and then pick the XMPC remote device that is within the IRTrans remotes category, which stores the button codes in a different format, that is in IRTrans' native format. When you are adding your infrared receiver and remote control using the LinuxMCE Admin Wizard/Devices/Media Directors page, the wizard automatically ensures that when you add a remote control it is the correct category.

For each remote control there is a device data "#59 Configuration" which has the remote controls configuration file, which defined all the infrared codes at each button will send and gives each code, or button, a name. So the XPMC remote within the LIRC category has a device data #59 that is the LIRC config file. The XPMC remote within the IRTrans category has a device data #59 that is the same buttons/codes, but in IRTrans format.

When the framework starts an IR receiver device, iIn general this device will first scan for all sister devices within the category remote control, and write out a configuration file. So, for example, when LIRC_DCE runs it finds all LIRC remote controls on that machine, grabs the device data "#59 Configuration" for every one of them and writes that out to a lirc.conf file, and then starts LIRC.

All the logic is in a base class called IRReceiverBase. All of LinuxMCE's infrared receiver devices use this same base class. So the actual code that is specific to each type of receiver is very small, usually around 20 lines. It only needs to write out the configuration file at start up, and then call the member function ReceivedCode within IRReceiverBase when a button is pushed. This function takes the name of the button as a parameter, and converts this into a message.

Since all of the receivers use a common base class to handle the logic, that also means that all of the translation between buttons and actions is also in a shared database. It does not matter whether you are using LIRC or some other infrared receiver, the translation is the same. There is no unified standard for what the buttons are called. The button "SkipFwd" may be called "Fwd", "Skip+", "Jump->", etc. The table RemoteMapping in the main mysql database, pluto_main, has a field Mapping which lists all the button aliases, followed by the command to be executed when any of those buttons is pushed. For example: chup;skipfwd;ChanUp;SkipNext;|0 -106 1 65 5 +1

Whenever any infrared receiver reports any of those button presses, the message "0 -106 1 65 5 +1" gets fired. The format of the message is the same as if you typed it with the MessageSend utility: ie from device, to device message type, message id, followed by parameters.

So if the user presses a button called ChanUp, a message will be sent to device -106 (media plugin) of type 1 (command) id 65 (Jump Position In Playlist) with parameter 5 (Value To Assign) set to "+1". This table is shared amongst all LinuxMCE users, and is updated every time your system upgrades versions. If you make your own manual changes to this table then the next time your core upgrades it will not upgrade the rows in that table that you modified, because SQL CVS does not, by default, overwrite your local changes with global ones. Therefore, if you have a new remote control with some new buttons that we have not yet mapped, it is recommended that you e-mail us or post us a message in the forum, with the button name and the message and then we can add it to our master database and then your system can remain in sync with other users enhancements. If you want to do some mapping that is just for you, you can change the table and know your changes will not be overwritten.

You'll note that the RemoteMapping table has 2 optional fields: ScreenType and RemoteLayout. When the IRReceiverBase base class is deciding what message to send in response to button press, it first looks for a more specific entry where the screen type matches the type of screen currently visible on the orbiter, and the remote layout matches the layout. The on-screen orbiters regularly send messages to the infrared receiver telling them what type of screen is currently visible, using the following codes: M=Main Menu, m=other menu, R=LinuxMCE Remote, r=Non-LinuxMCE remote, F=File Listing. This allows for buttons to behave differently depending upon what type of screen is visible. For example when the main menu is visible, the arrows on a remote control should send a message to the on-screen orbiter to move the highlight pointer around on the screen. However when the user is controlling an external piece of AV equipment, like a DVD player, the arrows should pass through to the DVD player so the user can control its own on-screen menu. Also the type of functionality can vary depending upon the layout of the remote. For example, Bang & Olufsen remotes are quite simple, there is only a single up/down/left/right buttons which are used both to navigate on-screen menus as well as to handle rewind fast-forward and skip. Other remotes have dedicated arrows and media navigation buttons. So one remote layout can be created for Bang & Olufsen-style remote, where the arrows control the menu when there is a menu on screen, and adjust the media when there is not. The remote layout is a device data "#110 Remote Layout" stored with the remote control

When IRReceiverBase looks for a mapping it first looks for records that match the current screen type and remote layout, and then revert to standard records (ie ScreenType and RemoteLayout are null) only if there are no matching results.

See also [[Add support for new remote controls]]

[[Category:Infrared]]
[[Category: Programmer's Guide]]
[[Category: Tutorials]]

Add support for new remote controls

2008-01-12T08:41:48Z

Mog: Category:InfraRed -> Infrared

<h1>How to set it up</h1>
LinuxMCE's infrared remote control module is based on LIRC. See http://lirc.org/ for details. LIRC includes an 'IR Record' utility to build a configuration file for a new remote control. Once you do that, then in LinuxMCE Admin choose 'Advanced', 'Device Templates'. Choose the manufacturer, for the Category choose Peripherals, Remote Controls, LIRC Remote controls. Type in the model of the remote and click 'add'. Then edit the device, add a device data "Configuration" and copy the LIRC configuration file into it.

The Programming Guide in [[Control LinuxMCE using an Infrared remote]] explains how it all works, and also how to use it.


[[Adding iMON PAD]] explains how to add it to the LinnuxMCE.


<h1>How to use it</h1>
[[Control LinuxMCE using an Infrared remote]]

<h1>Programmer's guide</h1>
[[Control LinuxMCE using an Infrared remote]]

[[Category:Input]]
[[Category:Infrared]]
[[Category:Tutorials]]

Controlling LinuxMCE

2008-01-12T08:39:30Z

Mog:

Windows

2008-01-12T08:39:10Z

Mog:

{{NeedsToBeFixed}}
If you want to run the Windows version of the Orbiter, we have an installer. This will allow you to use a Windows PC or tablet as an Orbiter. [http://plutohome.com/download/installers/windows/Orbiter%20-%202.0.0.0.exe Download]
The rest of the software, such as DCE Router, the devices and Plug-ins also run on Windows with the exception of Xine and MythTV. Since there is not yet a Windows-compatible media player, Windows has been a lower priority. An install program is not yet available to setup a Windows computer as a core or media director. We just created an archive file with all the required dll's and exe's http://files-upload.com/files/454340/winbin.zip. Uncompress the archive to any directory, and run DCERouter.exe. Any DCE Device can connect to any router. Windows devices will connect to a Linux DCERouter, and vice-versa. The archive also includes [[Designer]] which is used to build the user interface for the Orbiters. This is a C# program and requires the .NET framework.
You can also download the source code and build using the included Microsoft Visual Studio .NET 2003 project files. You will need to install MySQL, SDL and the Pthread libraries manually until we have a Windows installer to do it for you. If you want to run the LinuxMCE Admin web site, you will also need php and a compatible web server, like Apache or IIS.

[[Category:Orbiter]][[Category:Input]]

Controlling LinuxMCE

2008-01-12T08:36:08Z

Mog:

Controlling LinuxMCE

2008-01-12T08:33:37Z

Mog:

{{Stub}}
==Infrared remotes==
* [[Infrared]]
* [[USB UIRT]]
* [[Windows MCE Remote]]
* [[:Category:Infrared]]
==Handheld computers/PDAs==
* [[:Category:Orbiters]]
==Computers==
* [[Web Orbiter]] and [[Add Web Orbiter]]
==Specialized remotes==
* [[Nintendo WiiMote]]

Hauppauge Nova-T

2008-01-11T07:07:42Z

Mog:

[[Category: Hardware]]
[[Category: Video]]
[[Category: TV Cards]]
{{stub}}
Hauppauge Nova-T is in fact a [http://en.wikipedia.org/wiki/Hauppauge_Computer_Works#Table_of_products series of cards], which card(s) is this article referring to?

A blog entry describing howto install and configure this card is here: http://tperl.blogspot.com/2007/10/hauppauge-wintv-nova-t-stick-under.html

According to the author, this card works great in Debian. Haven't tried with LinuxMCE...

//Motin

Other comment:
The card seems to work ok but then it crashes and the screen freezes up.

Hopefully its just a small problem. It will still record if a recording has been started but the screen locks up on the core.

Will update if I find out more.

Display Drivers

2008-01-11T06:42:46Z

Mog: /* Signal out of range */

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

An incomplete HowTo on updating LinuxMCE to the latest display drivers and configuring them manually. It could use your help, so if something is different in your situation, please add it.

'''Note that this should normally not be necessary unless you have specific wishes or trouble getting your display to work properly.'''

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

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

For more information see also the [http://wiki.cchtml.com/index.php/Main_Page Unofficial ATI Linux Driver Wiki] and you might want to have a look at [http://www.mythtv.org/wiki/index.php/AtiProprietaryDriver AtiProprietaryDriver] in the MythTV wiki as well since LinuxMCE depends on it for viewing TV. MythTV in turn relies heavily on the support of certain features by the graphics drivers. The ATI drivers turn out to be a bit "challenged" in this area to say the least.

=== NVidia Chipsets ===
There are several ways to install NVidia drivers, the way described here is meant as a guide to install the very latest drivers from the NVidia website. Note that this way will bypass the LinuxMCE (Kubuntu) packaging system, possibly removing and/or overwriting some of it's files.

1. Go to a console (text) terminal by holding [CTRL]-[ALT] and pressing the [F1] key simultaneously, log in with the user account you have created during the Kubuntu install and become root, if you haven't done so already.
'''<you>@dcerouter:~$''' sudo -s
2. Download the latest [http://www.nvidia.com/object/unix.html linux drivers from NVidia] (depending [http://www.nvidia.com/object/IO_32667.html on your hardware], one of versions: 100.14.23, 1.0-9639 or 1.0-7185 currently), if you haven't done so already. When you have found the URL for downloading the package on the nvidia site you could download it like this:
'''root@dcerouter:~#''' wget <nowiki>http://us.download.nvidia.com/XFree86/Linux-x86/</nowiki>''<version>''<nowiki>/NVIDIA-Linux-x86-</nowiki>''<version>''<nowiki>-pkg1.run</nowiki>
3. Go to runlevel 1 to stop the currently running X-server.

NB: There was no need for me to run this command as I was already in Level 1 - It just locked up the keyboard. --[[User:Mortar|Mortar]] 18:12, 6 January 2008 (MST)
'''root@dcerouter:~#''' telinit 1
4. Execute the installer and follow instructions. Ignore the warning about runlevel 1 and don't bother looking for precompiled drivers.
'''root@dcerouter:~#''' sh NVIDIA-Linux-x86-''<version>''-pkg1.run
5. Now it needs to be configured. The recommended and most convenient way is to use the [[AVWizard]]. For more advanced setup, or if the AVWizard for some reason is unable to set your up your screens to your liking, you can configure the ''X-server'' manually by editing the ''xorg.conf'' file directly.

=== Intel Chipsets ===
There is a renewed interest in the Intel graphics chipsets since Intel released the drivers under the GPL. However, they're still not at the same level as nVidia's and can't do alpha blending.

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

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

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

=== Via Chipsets ===
Use the Openchrome or Via Unichrome drivers. The Via Unichrome drivers can be downloaded from http://www.viaarena.com/default.aspx?PageID=2&OSID=45&CatID=3220

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

== Configuration ==
The recommended and most convenient way is to use the [[AVWizard]]. For more advanced setup, or if the X-server (and thus also the AVWizard) is unable to start, you can configure the ''X-server'' manually by editing the ''xorg.conf'' file directly.

=== Getting started ===
Start by making a backup copy of the ''/etc/X11/xorg.conf'' file (even if it doesn't work it might contain settings you could need). In this example we will start from scratch and edit the configuration file step by step to get the main display setup.

Some of these steps require that there will be no X-server active on the system, the easiest way to achieve this is to boot in ''rescue-mode'', just hit [Esc] when [[Grub]] tells you to during the startup of your machine and select the right line from the menu. Another way is to go to a text-mode console (aka. terminal) with [CTRL]-[ALT]-[F1], [[Logging In|log in]], become root and issue the command:
telinit 1
This wil stop the running X-server and drop you into rescue mode as well.

One of the advantages is that now you can start and stop the X-server by hand with an alternative configuration file and without having to reboot or even start an entire desktop environment.

=== Generating a template ===
These instructions were originally written for ATI chipsets, so they might need to be adjusted and updated a bit. Not all of the specific options may be relevant for your chipset.

'''While there is no (other) X-server running''' you can create a template configuration file by running:
X -configure
This will create a file called xorg.conf.new in your ''home'' directory, test it with the following command and hit [CTRL]-[ALT]-[Backspace] when done:
X -config ~/xorg.conf.new
Within a few seconds a gray bitpattern should show up with an 'X' shaped mouse cursor. If the screen is distorted or reports the refresh rate to be out of range then you will either have to specify the proper refreshrate limitations for your screen or insert "modelines" for the resolution(s) you want to use (see below).

When you're satisfied you can overwrite ''/etc/X11/xorg.conf'' with this file to make it the default (you did make a backup didn't you?), once you have done that you can use "startx" to test and have the use of your desktop as well. This should at least be enough to allow the use of a graphic configuration tool (like the [[AVWizard]] for instance) to set up your display further. More advanced manual configuration options can be found below.

Here is an example of such a generated file:

Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
RgbPath "/etc/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/X11R6/lib/X11/fonts/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/X11R6/lib/X11/fonts/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
Load "extmod"
Load "record"
Load "xtrap"
Load "dri"
Load "glx"
Load "dbe"
Load "GLcore"
Load "type1"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection

Section "Device"
### Available Driver options are:-
### Values: : integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "ShadowFB" # [<bool>]
#Option "DefaultRefresh" # [<bool>]
#Option "ModeSetClearScreen" # [<bool>]
Identifier "Card0"
Driver "vesa"
''VendorName "ATI Technologies Inc"''
''BoardName "ATI Radeon Xpress 1200 Series"''
''BusID '''"PCI:1:5:0"'''''
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

Note that the only thing really specific to my setup in this config file is ''BusID'', if you only have one graphics adapter in your system this value can be omitted, otherwise the value(s) can be found with:
X -scanpci
Where each card will need it's own Device Section in the config file. The "VendorName" and "BoardName" settings are just labels and serve no real purpose other then being able to identify this particular device, which is usefull if you have more then one.

We'll be using this sample configuration as a starting point in the other examples below, the comments (lines starting with ''#'' can be safely removed as well as the ''"Display"'' subsections for the colordepths we don't plan on using.

=== Refresh rate / ModeLine ===
The easiest way to sort this problem is to let the X-server figure this out by not specifying the limits of your screen. However this often fails, leaving you with an unusable display. Simply look up '''your screen''''s refresh rates in the documentation and add them like this:

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
''HorizSync '''27-102''' # kHz''
''VertRefresh '''50-160''' # Hz''
EndSection

Alternatively you could specify a "ModeLine" for each resolution you want to use. By using ModeLines you have much finer controll over the timings of the output signal generated by your videocard. The drawback is that the timing values can be hard to get right.

Search the web for a "modeline generator", and many of these will include instructions on how to add the modeline, but briefly, you just add it to the "Monitor" section. Read the [http://en.wikipedia.org/wiki/Modeline wikipedia entry] to learn how to use modelines.
* http://koala.ilog.fr/cgi-bin/nph-colas-modelines
* http://xtiming.sourceforge.net/cgi-bin/xtiming.pl
* http://www.bohne-lang.de/spec/linux/modeline/
* http://amlc.berlios.de/
If one modeline doesn't work perfectly, try another, perhaps from another generator, because they can vary so much.

Using the wrong timings could in some (nowadays rare) occasions damage the hardware of your screen, so if it looks garbeled don't leave it like that for hours on end but hit [Ctrl]-[Alt]-[←Backspace] and readjust your settings. Most modern screens however simply report that the signal is out of range if this happens.

=== Colordepth and resolution ===
Specify the colordepth and resolution(s) you would like to use, like this:

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
''DefaultDepth '''24'''''
SubSection "Display"
Viewport 0 0
Depth 24
''Virtual '''1600 1200'''''
''Modes '''"1600x1200" "1280x1024" "1024x768" "800x600" "640x480" "512x384" "400x300" "320x240"'''''
EndSubSection
EndSection

As most people will only be using 24 bits anyway, I have removed the other redundant subsections. "Virtual" is the size of your desktop and "Modes" are physical resolutions, you can flip through these by holding [CTRL]-[ALT] and pressing the plus or minus on the numeric keypad. These are just examples, most people will only want to specify the resolution they actually use.

=== DRI device permissions ===
This section is needed to have the X-server set the proper permissions on the DRI device during startup. Simply add it to the end of the /etx/X11.xorg file if it isn't there already.

Section "DRI"
Mode 0666
EndSection

=== Chipset driver ===
Change "'''vesa'''" to "'''fglrx'''" (or "'''ati'''", depending on which drivers you installed earlier), as shown below, the old line is left as a comment in this example for clarity, but it's better to remove it as some scripts seem to find it confusing. For Nvidia chipsets use '''nvidia''' or '''nv''' as the driver names (instead of '''fglrx''').

Section "Device"
Identifier "Card0"
''# Driver "'''vesa'''"''
''Driver "'''fglrx'''"''
VendorName "ATI Technologies Inc"
BoardName "ATI Radeon Xpress 1200 Series"
BusID "PCI:1:5:0"
EndSection

If your X-server was running you will have to restart it completely for the changes to take effect, the easiest and most thorough way to do this is to reboot.

=== Physical display size ===
Like specifying the refresh rate his is optional but sometimes necessary, most of the time it is either detected or some sane defaults are used but sometimes it isn't, which can result in unreadable font sizes.

Section "Monitor"
...
DisplaySize '''155 95'''
EndSection

Where you have to replace the numbers with the physical '''width''' and '''height''' of your screen in millimeters (1" = 25mm), feel free to try mine, however these are for a small touchscreen.

=== Disable composite ===
Aparently the ATI '''fglrx''' driver does not ''yet'' support composite with DRI. So if you are using the fglrx driver, disable it by adding this to the end of the /etx/X11.xorg file if it isn't there already.

Section "Extensions"
Option "Composite" "Disable"
EndSection

=== Additional options ===
To be continued, I don't think this is enough to get UI2 completely (either mode) going yet. Feel free to jump in anytime...

Things still to sort out amongst others (i.e. what is it, do we need it and what are the settings if any):

Section "Module"
Load "i2c"
Load "bitmap"
Load "ddc"
Load "freetype"
Load "int10"
Load "vbe"
Load "speedo"
Load "type1"
Load "dbe"
Load "glx"
Load "v4l"
EndSection

Section "ServerFlags"
Option "AIGLX" "off"
EndSection

Section "Extensions"
Option "Composite" "Disable"
# Option "RENDER" "true"
EndSection

Option "PseudoColorVisuals" "off"
Option "OpenGLOverlay" "off"
Option "VideoOverlay" "off"
Option "DesktopSetup" "clone"

TV-out options, 2nd display, etc.

== Troubleshooting ==

=== X-windows won't start for AVWizard ===

*One problem on nvidia-cards could be that it does not detect the right monitor.

::Go to Console 1 ([Ctrl]+[Alt]+1) and edit /etc/X11/xorg.conf (nano -w /etc/X11/xorg.conf). Find the section ::Device with the driver nvidia add the line <pre>Option "ConnectedMonitor" "XXX"
::where XXX is CRT, CRT-0, CRT-1, DVI-0, DVI-1, ...</pre>
::Save and exit (nano: Ctrl+x) and restart the computer. In my case it was "CRT-1".
* Screen is black, after install seemed to go okay. You may have even seen the Kubuntu splash screen.
**[[AVWizard]]

=== X-windows won't start ===

Reboot into rescue-mode if needed (hit [Esc] when [[Grub]] tells you to), and restore a working copy of your /etc/X11/xorg.conf, or edit it by hand to fix the problem. Test it with the command "X" and press [Ctrl]-[Alt]-[←Backspace] simultaneous to quit (alternative: use "startx" and get the full desktop, if any), then reboot when it works and you're done.

=== Signal out of range ===

See ''[[#Refresh rate / ModeLine ]]'' above.

=== Microscopic fonts in KDE ===

See ''[http://wiki.linuxmce.com/index.php/Display_Drivers#Physical_display_size Physical display size]'' above.

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

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

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

To achieve this the following steps are required:

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

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

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

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

Add a line containing '''exit''' to the top of the ''/usr/pluto/bin/Xconfigure.sh'' file.

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