<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://wiki.linuxmce.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Viking</id>
	<title>LinuxMCE - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="http://wiki.linuxmce.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Viking"/>
	<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php/Special:Contributions/Viking"/>
	<updated>2026-07-21T18:31:22Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.44.0</generator>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Sony_KDL-46W4500&amp;diff=31701</id>
		<title>Sony KDL-46W4500</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Sony_KDL-46W4500&amp;diff=31701"/>
		<updated>2012-07-20T21:02:05Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Hardware]]&lt;br /&gt;
{{versioninfo|810Status=Working|810UpdatedDate=10th July 2012|810UpdatedBy=Viking}}&lt;br /&gt;
[[Category:Video]]&lt;br /&gt;
[[Category:Displays]]&lt;br /&gt;
&lt;br /&gt;
I am using an &#039;&#039;&#039;European&#039;&#039;&#039; version this TV and will try to describe problems I have here.&lt;br /&gt;
&lt;br /&gt;
Connected to a Nvidia 8400 GS with an DVI to HDMI cable. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;10th July 2012 - Currently I am using the judderfree solution further down with 0810 &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
I was not able to get the AV Wizard to setup the TV to 1080p with 50hz, so I setup 1080p and 60hz. Then afterwards I changed the xorg.conf and changed/added the following lines :&lt;br /&gt;
&lt;br /&gt;
 Option         &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
 Option         &amp;quot;UseEDID&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 Modes           &amp;quot;1920x1080_50_1&amp;quot; &amp;quot;1920x1080_50_0&amp;quot; &amp;quot;1920x1080_50&amp;quot; &amp;quot;1920x1080&amp;quot; &amp;quot;1920x1080_50i&amp;quot;&lt;br /&gt;
 VertRefresh     49-51&lt;br /&gt;
&lt;br /&gt;
and rebooted. After that I had 50hz.&lt;br /&gt;
&lt;br /&gt;
The line &amp;quot;1920x1080_50&amp;quot; uses the EDID information it gets of the TV and sets things up correctly. In the /var/log/Xorg.0.log you can then see that it chooses the right resolution.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot; is important, otherwise you will get very small unreadable characters.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
I did also start KDE and then start nvidia-settings. Then below OpenGL settings activated the checkbox next to &amp;quot;Sync to VBlank&amp;quot; so that it is used.&lt;br /&gt;
&lt;br /&gt;
Then in MythTV (see here http://www.mythtv.org/wiki/VDPAU#Enabling_VDPAU_in_MythFrontend) under &amp;quot;Utilities -&amp;gt; Setup -&amp;gt; TV Settings -&amp;gt; Playback -&amp;gt; Playback Profiles (3/8)&amp;quot; setup &amp;quot;VDPAU Normal&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Update 20.07.2012 for Judderfree is this also needed :&lt;br /&gt;
http://www.mythtv.org/wiki/VDPAU#Tearing.2FStuttering&lt;br /&gt;
Change Option &amp;quot;Composite&amp;quot; &amp;quot;true&amp;quot; in /etc/X11/xorg.conf to &#039;&#039;&#039;&amp;quot;Disable&amp;quot;&#039;&#039;&#039;:&lt;br /&gt;
&lt;br /&gt;
   Section &amp;quot;Extensions&amp;quot;&lt;br /&gt;
       Option &amp;quot;Composite&amp;quot; &amp;quot;Disable&amp;quot;&lt;br /&gt;
   EndSection&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Judder free TV and Video with MythTV and MythTV video plugin ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;10th July 2012 - This is the CURRENT solution I am using with 0810 &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Using the description from here :&lt;br /&gt;
http://www.mythtv.org/wiki/User_Manual:JudderFree&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT is in your xorg.conf to change the Option &amp;quot;DynamicTwinView&amp;quot; to &amp;quot;true&amp;quot; !!!&#039;&#039;&#039; That is the option that lets you choose ALL the refresh rates, also the 23.97 !&lt;br /&gt;
&lt;br /&gt;
I did setup all the needed resolutions and changed MythTV to change the resolution as described in the link above. &#039;&#039;&#039;The xorg.conf from below works with that!!!&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
That way MýthTV&#039;s Video plugin will change the refresh rate to the right typ, no matter what kind of material you are playing. Execpt for PAL DVD&#039;s , they are for some reason set to NTSC 59.96 rate. I have no idea why at the monent.&lt;br /&gt;
&lt;br /&gt;
I have still setup the VDPAU things above in mythtv and &amp;quot;vsync to blanc&amp;quot; nvidia-settings !!&lt;br /&gt;
&lt;br /&gt;
And this is also needed :&lt;br /&gt;
http://www.mythtv.org/wiki/VDPAU#Tearing.2FStuttering&lt;br /&gt;
Change Option &amp;quot;Composite&amp;quot; &amp;quot;true&amp;quot; in /etc/X11/xorg.conf to &#039;&#039;&#039;&amp;quot;Disable&amp;quot;&#039;&#039;&#039;:&lt;br /&gt;
&lt;br /&gt;
   Section &amp;quot;Extensions&amp;quot;&lt;br /&gt;
       Option &amp;quot;Composite&amp;quot; &amp;quot;Disable&amp;quot;&lt;br /&gt;
   EndSection&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Alternate solution (I used first) ==&lt;br /&gt;
&lt;br /&gt;
I was not able to get the TV setup to 1080p with 50hz, so I choosed 1080p and 60hz. Then afterwards I changed the xorg.conf to the right 1080p@50hz Modeline i found in the HDTV list in the MythTV modeline database.&lt;br /&gt;
&lt;br /&gt;
        # 1920x1080 @ 50 Hz (EDID) HSync: 56.25 kHz&lt;br /&gt;
        ModeLine &amp;quot;1920x1080&amp;quot; 148.50 1920 2448 2496 2640 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
&lt;br /&gt;
And changed the VertRefresh to :&lt;br /&gt;
        VertRefresh     49-51&lt;br /&gt;
&lt;br /&gt;
and rebooted. After that I had 50hz.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== My latest xorg.conf ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    Section &amp;quot;ServerLayout&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;XFree86 Configured&amp;quot;&lt;br /&gt;
    	Screen	  0	&amp;quot;Screen0&amp;quot;	0 0&lt;br /&gt;
    	InputDevice	&amp;quot;Mouse0&amp;quot;	&amp;quot;CorePointer&amp;quot;&lt;br /&gt;
    	InputDevice	&amp;quot;Keyboard0&amp;quot;	&amp;quot;CoreKeyboard&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Files&amp;quot;&lt;br /&gt;
    #	RgbPath		&amp;quot;/usr/X11R6/lib/X11/rgb&amp;quot;&lt;br /&gt;
    	ModulePath	&amp;quot;/usr/lib/xorg/modules&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/share/fonts/X11&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/misc/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/Speedo/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/Type1/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/CID/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/75dpi/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/100dpi/&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Module&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;dbe&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;extmod&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;record&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;xtrap&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;speedo&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;type1&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;glx&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;int10&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;v4l&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;InputDevice&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;Keyboard0&amp;quot;&lt;br /&gt;
    	Driver		&amp;quot;keyboard&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;XkbLayout&amp;quot;		&amp;quot;us&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;XkbVariant&amp;quot;	&amp;quot;basic&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;XkbModel&amp;quot;		&amp;quot;pc105&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;InputDevice&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;Mouse0&amp;quot;&lt;br /&gt;
    	Driver		&amp;quot;mouse&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;Protocol&amp;quot;		&amp;quot;auto&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;Device&amp;quot;		&amp;quot;/dev/input/mice&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;ZAxisMapping&amp;quot;	&amp;quot;4 5&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Monitor&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;Monitor0&amp;quot;&lt;br /&gt;
    	VendorName	&amp;quot;Sony&amp;quot;&lt;br /&gt;
    	ModelName	&amp;quot;46&amp;quot;&lt;br /&gt;
    	## HorizSync	20-500&lt;br /&gt;
    	# 1920x1080 @ 50 Hz (EDID) HSync: 28.125 kHz&lt;br /&gt;
    	## VertRefresh	49-51&lt;br /&gt;
    	## ModeLine &amp;quot;1920x1080_my50i&amp;quot; 74.25 1920 2448 2492 2640 1080 1084 1094 1124 +HSync +VSync Interlace&lt;br /&gt;
            # 1920x1080 @ 50 Hz (EDID) HSync: 56.25 kHz&lt;br /&gt;
            ## ModeLine &amp;quot;1920x1080_my50&amp;quot; 148.50 1920 2448 2496 2640 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
    &lt;br /&gt;
    	# 1920x1080p @ 50Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@50&amp;quot; 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 60Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@60&amp;quot; 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 24Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@24&amp;quot; 74.250 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 23.976Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@23.976&amp;quot; 74.175 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080i @ 50Hz (EIA/CEA-861B) &lt;br /&gt;
    	Modeline &amp;quot;1920x1080@50i&amp;quot; 74.250 1920 2448 2492 2640 1080 1085 1095 1125 +hsync +vsync Interlace &lt;br /&gt;
    	# 1920x1080i @ 60Hz (EIA/CEA-861B) &lt;br /&gt;
    	Modeline &amp;quot;1920x1080@60i&amp;quot; 74.250 1920 2008 2052 2200 1080 1085 1095 1125 +hsync +vsync interlace &lt;br /&gt;
    	# 1920x1080p @ 59.94Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@59.94&amp;quot; 148.350 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080i @ 59.94Hz (EIA/CEA-861B) &lt;br /&gt;
    	Modeline &amp;quot;1920x1080@59.94i&amp;quot; 74.175 1920 2008 2052 2200 1080 1085 1095 1125 +hsync +vsync Interlace &lt;br /&gt;
    	# 1920x1080p @ 25Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@25&amp;quot; 74.250 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 29.97Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@29.97&amp;quot; 74.175 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 30Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@30&amp;quot; 74.250 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	HorizSync	20.0 - 150.0 &lt;br /&gt;
    	VertRefresh     23.0 - 90.0 &lt;br /&gt;
    	Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;True&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEDIDFreqs&amp;quot; &amp;quot;FALSE&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;FALSE&amp;quot;&lt;br /&gt;
    	#!# Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoEdidModes&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Device&amp;quot;&lt;br /&gt;
    	### Available Driver options are:-&lt;br /&gt;
    	### Values: &amp;lt;i&amp;gt;: integer, &amp;lt;f&amp;gt;: float, &amp;lt;bool&amp;gt;: &amp;quot;True&amp;quot;/&amp;quot;False&amp;quot;,&lt;br /&gt;
    	### &amp;lt;string&amp;gt;: &amp;quot;String&amp;quot;, &amp;lt;freq&amp;gt;: &amp;quot;&amp;lt;f&amp;gt; Hz/kHz/MHz&amp;quot;&lt;br /&gt;
    	### [arg]: arg optional&lt;br /&gt;
    	#Option		&amp;quot;NoAccel&amp;quot;				# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;SWcursor&amp;quot;				# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;ColorKey&amp;quot;				# &amp;lt;i&amp;gt;&lt;br /&gt;
    	#Option		&amp;quot;CacheLines&amp;quot;			# &amp;lt;i&amp;gt;&lt;br /&gt;
    	#Option		&amp;quot;Dac6Bit&amp;quot;				# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;DRI&amp;quot;					# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;NoDDC&amp;quot;					# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;ShowCache&amp;quot;				# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;XvMCSurfaces&amp;quot;			# &amp;lt;i&amp;gt;&lt;br /&gt;
    	Identifier	&amp;quot;Card0&amp;quot;&lt;br /&gt;
    	Driver		&amp;quot;nvidia&amp;quot;&lt;br /&gt;
    	VendorName	&amp;quot;Unknown Vendor Name&amp;quot;&lt;br /&gt;
    	BoardName	&amp;quot;Unknown Board Name&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;LinearAlloc&amp;quot;		&amp;quot;16384&amp;quot;&lt;br /&gt;
    	#BusID		&amp;quot;PCI:0:2:0&amp;quot;&lt;br /&gt;
    #	Option		&amp;quot;NoDDC&amp;quot;				&amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;XvmcUsesTextures&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;renderAccel&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoDDCValue&amp;quot;&lt;br /&gt;
    	# Option &amp;quot;UseEDID&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEDID&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
            Option &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	## Option         &amp;quot;TripleBuffer&amp;quot; &amp;quot;True&amp;quot;&lt;br /&gt;
    	Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoLogo&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoBandWidthTest&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes,NoEdidModes&amp;quot;&lt;br /&gt;
    	## Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoVertRefreshCheck, NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes&amp;quot;&lt;br /&gt;
    &lt;br /&gt;
    	Option &amp;quot;DynamicTwinView&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEvents&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	## CJA Maybe remove ?&lt;br /&gt;
    	Option &amp;quot;AllowGLXWithComposite&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AddARGBGLXVisuals&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;ConnectedMonitor&amp;quot; &amp;quot;DFP&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Screen&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;Screen0&amp;quot;&lt;br /&gt;
    	Device		&amp;quot;Card0&amp;quot;&lt;br /&gt;
    	Monitor		&amp;quot;Monitor0&amp;quot;&lt;br /&gt;
    	DefaultDepth	24&lt;br /&gt;
    	Option	    &amp;quot;FlatPanelProperties&amp;quot; &amp;quot;Scaling = Native&amp;quot; &lt;br /&gt;
    	Option	    &amp;quot;TwinView&amp;quot; &amp;quot;0&amp;quot; &lt;br /&gt;
    	SubSection &amp;quot;Display&amp;quot;&lt;br /&gt;
    		## Modes		&amp;quot;1920x1080_50i&amp;quot; &amp;quot;1920x1080_50i_0&amp;quot; &amp;quot;1920x1080_my50i&amp;quot;&lt;br /&gt;
    		## Virtual		1920 1080&lt;br /&gt;
    		Depth     24 &lt;br /&gt;
    &lt;br /&gt;
    		Modes &amp;quot;1920x1080@50&amp;quot; &amp;quot;1920x1080@60&amp;quot; &amp;quot;1920x1080@24&amp;quot; &amp;quot;1920x1080@23.976&amp;quot; &amp;quot;1920x1080@50i&amp;quot;&lt;br /&gt;
    		Modes &amp;quot;1920x1080@60i&amp;quot; &amp;quot;1920x1080@59.94&amp;quot; &amp;quot;1920x1080@59.94i&amp;quot;&lt;br /&gt;
    &lt;br /&gt;
    		## Modes &amp;quot;1920x1080@50i&amp;quot; &amp;quot;1920x1080@50&amp;quot; &amp;quot;1920x1080@60&amp;quot; &amp;quot;1920x1080@24&amp;quot; &amp;quot;1920x1080@23.976&amp;quot;&lt;br /&gt;
    		## Modes &amp;quot;1920x1080@60i&amp;quot; &amp;quot;1920x1080@59.94&amp;quot; &amp;quot;1920x1080@59.94i&amp;quot;&lt;br /&gt;
    		# Modes &amp;quot;1920x1080@25&amp;quot; &amp;quot;1920x1080@29.97&amp;quot; &amp;quot;1920x1080@30&amp;quot;&lt;br /&gt;
    	EndSubSection&lt;br /&gt;
    	Option &amp;quot;XvmcUsesTextures&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;renderAccel&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoDDCValue&amp;quot;&lt;br /&gt;
    	# Option &amp;quot;UseEDID&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEDID&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
            Option &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoLogo&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoBandWidthTest&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes,NoEdidModes&amp;quot;&lt;br /&gt;
    	## Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoVertRefreshCheck, NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes&amp;quot;&lt;br /&gt;
    	Option &amp;quot;DynamicTwinView&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEvents&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	## CJA Maybe remove ?&lt;br /&gt;
    	Option &amp;quot;AllowGLXWithComposite&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AddARGBGLXVisuals&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;TVStandard&amp;quot;	&amp;quot;1080p (16:9)&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;AllowMouseOpenFail&amp;quot;	&amp;quot;true&amp;quot;&lt;br /&gt;
    	Option  &amp;quot;AutoAddDevices&amp;quot; 	&amp;quot;false&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;BlankTime&amp;quot;		&amp;quot;0&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;StandbyTime&amp;quot;	&amp;quot;0&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;SuspendTime&amp;quot;	&amp;quot;0&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;OffTime&amp;quot;		&amp;quot;0&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;AIGLX&amp;quot;			&amp;quot;Off&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;Extensions&amp;quot;&lt;br /&gt;
    	Option &amp;quot;Composite&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	Option &amp;quot;RENDER&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Sony_KDL-46W4500&amp;diff=31690</id>
		<title>Sony KDL-46W4500</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Sony_KDL-46W4500&amp;diff=31690"/>
		<updated>2012-07-10T10:04:38Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Hardware]]&lt;br /&gt;
{{versioninfo|810Status=Working|810UpdatedDate=10th July 2012|810UpdatedBy=Viking}}&lt;br /&gt;
[[Category:Video]]&lt;br /&gt;
[[Category:Displays]]&lt;br /&gt;
&lt;br /&gt;
I am using an &#039;&#039;&#039;European&#039;&#039;&#039; version this TV and will try to describe problems I have here.&lt;br /&gt;
&lt;br /&gt;
Connected to a Nvidia 8400 GS with an DVI to HDMI cable. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;10th July 2012 - Currently I am using the judderfree solution further down with 0810 &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
I was not able to get the AV Wizard to setup the TV to 1080p with 50hz, so I setup 1080p and 60hz. Then afterwards I changed the xorg.conf and changed/added the following lines :&lt;br /&gt;
&lt;br /&gt;
 Option         &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
 Option         &amp;quot;UseEDID&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 Modes           &amp;quot;1920x1080_50_1&amp;quot; &amp;quot;1920x1080_50_0&amp;quot; &amp;quot;1920x1080_50&amp;quot; &amp;quot;1920x1080&amp;quot; &amp;quot;1920x1080_50i&amp;quot;&lt;br /&gt;
 VertRefresh     49-51&lt;br /&gt;
&lt;br /&gt;
and rebooted. After that I had 50hz.&lt;br /&gt;
&lt;br /&gt;
The line &amp;quot;1920x1080_50&amp;quot; uses the EDID information it gets of the TV and sets things up correctly. In the /var/log/Xorg.0.log you can then see that it chooses the right resolution.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot; is important, otherwise you will get very small unreadable characters.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
I did also start KDE and then start nvidia-settings. Then below OpenGL settings activated the checkbox next to &amp;quot;Sync to VBlank&amp;quot; so that it is used.&lt;br /&gt;
&lt;br /&gt;
Then in MythTV (see here http://www.mythtv.org/wiki/VDPAU#Enabling_VDPAU_in_MythFrontend) under &amp;quot;Utilities -&amp;gt; Setup -&amp;gt; TV Settings -&amp;gt; Playback -&amp;gt; Playback Profiles (3/8)&amp;quot; setup &amp;quot;VDPAU Normal&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Not sure what fixed my LiveTV juddering in the end.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Judder free TV and Video with MythTV and MythTV video plugin ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;10th July 2012 - This is the CURRENT solution I am using with 0810 &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Using the description from here :&lt;br /&gt;
http://www.mythtv.org/wiki/User_Manual:JudderFree&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT is in your xorg.conf to change the Option &amp;quot;DynamicTwinView&amp;quot; to &amp;quot;true&amp;quot; !!!&#039;&#039;&#039; That is the option that lets you choose ALL the refresh rates, also the 23.97 !&lt;br /&gt;
&lt;br /&gt;
I did setup all the needed resolutions and changed MythTV to change the resolution as described in the link above. &#039;&#039;&#039;The xorg.conf from below works with that!!!&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
That way MýthTV&#039;s Video plugin will change the refresh rate to the right typ, no matter what kind of material you are playing. Execpt for PAL DVD&#039;s , they are for some reason set to NTSC 59.96 rate. I have no idea why at the monent.&lt;br /&gt;
&lt;br /&gt;
I have still setup the VDPAU things above in mythtv and &amp;quot;vsync to blanc&amp;quot; nvidia-settings !!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Alternate solution (I used first) ==&lt;br /&gt;
&lt;br /&gt;
I was not able to get the TV setup to 1080p with 50hz, so I choosed 1080p and 60hz. Then afterwards I changed the xorg.conf to the right 1080p@50hz Modeline i found in the HDTV list in the MythTV modeline database.&lt;br /&gt;
&lt;br /&gt;
        # 1920x1080 @ 50 Hz (EDID) HSync: 56.25 kHz&lt;br /&gt;
        ModeLine &amp;quot;1920x1080&amp;quot; 148.50 1920 2448 2496 2640 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
&lt;br /&gt;
And changed the VertRefresh to :&lt;br /&gt;
        VertRefresh     49-51&lt;br /&gt;
&lt;br /&gt;
and rebooted. After that I had 50hz.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== My latest xorg.conf ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    Section &amp;quot;ServerLayout&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;XFree86 Configured&amp;quot;&lt;br /&gt;
    	Screen	  0	&amp;quot;Screen0&amp;quot;	0 0&lt;br /&gt;
    	InputDevice	&amp;quot;Mouse0&amp;quot;	&amp;quot;CorePointer&amp;quot;&lt;br /&gt;
    	InputDevice	&amp;quot;Keyboard0&amp;quot;	&amp;quot;CoreKeyboard&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Files&amp;quot;&lt;br /&gt;
    #	RgbPath		&amp;quot;/usr/X11R6/lib/X11/rgb&amp;quot;&lt;br /&gt;
    	ModulePath	&amp;quot;/usr/lib/xorg/modules&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/share/fonts/X11&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/misc/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/Speedo/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/Type1/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/CID/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/75dpi/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/100dpi/&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Module&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;dbe&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;extmod&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;record&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;xtrap&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;speedo&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;type1&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;glx&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;int10&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;v4l&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;InputDevice&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;Keyboard0&amp;quot;&lt;br /&gt;
    	Driver		&amp;quot;keyboard&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;XkbLayout&amp;quot;		&amp;quot;us&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;XkbVariant&amp;quot;	&amp;quot;basic&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;XkbModel&amp;quot;		&amp;quot;pc105&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;InputDevice&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;Mouse0&amp;quot;&lt;br /&gt;
    	Driver		&amp;quot;mouse&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;Protocol&amp;quot;		&amp;quot;auto&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;Device&amp;quot;		&amp;quot;/dev/input/mice&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;ZAxisMapping&amp;quot;	&amp;quot;4 5&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Monitor&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;Monitor0&amp;quot;&lt;br /&gt;
    	VendorName	&amp;quot;Sony&amp;quot;&lt;br /&gt;
    	ModelName	&amp;quot;46&amp;quot;&lt;br /&gt;
    	## HorizSync	20-500&lt;br /&gt;
    	# 1920x1080 @ 50 Hz (EDID) HSync: 28.125 kHz&lt;br /&gt;
    	## VertRefresh	49-51&lt;br /&gt;
    	## ModeLine &amp;quot;1920x1080_my50i&amp;quot; 74.25 1920 2448 2492 2640 1080 1084 1094 1124 +HSync +VSync Interlace&lt;br /&gt;
            # 1920x1080 @ 50 Hz (EDID) HSync: 56.25 kHz&lt;br /&gt;
            ## ModeLine &amp;quot;1920x1080_my50&amp;quot; 148.50 1920 2448 2496 2640 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
    &lt;br /&gt;
    	# 1920x1080p @ 50Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@50&amp;quot; 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 60Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@60&amp;quot; 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 24Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@24&amp;quot; 74.250 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 23.976Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@23.976&amp;quot; 74.175 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080i @ 50Hz (EIA/CEA-861B) &lt;br /&gt;
    	Modeline &amp;quot;1920x1080@50i&amp;quot; 74.250 1920 2448 2492 2640 1080 1085 1095 1125 +hsync +vsync Interlace &lt;br /&gt;
    	# 1920x1080i @ 60Hz (EIA/CEA-861B) &lt;br /&gt;
    	Modeline &amp;quot;1920x1080@60i&amp;quot; 74.250 1920 2008 2052 2200 1080 1085 1095 1125 +hsync +vsync interlace &lt;br /&gt;
    	# 1920x1080p @ 59.94Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@59.94&amp;quot; 148.350 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080i @ 59.94Hz (EIA/CEA-861B) &lt;br /&gt;
    	Modeline &amp;quot;1920x1080@59.94i&amp;quot; 74.175 1920 2008 2052 2200 1080 1085 1095 1125 +hsync +vsync Interlace &lt;br /&gt;
    	# 1920x1080p @ 25Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@25&amp;quot; 74.250 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 29.97Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@29.97&amp;quot; 74.175 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 30Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@30&amp;quot; 74.250 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	HorizSync	20.0 - 150.0 &lt;br /&gt;
    	VertRefresh     23.0 - 90.0 &lt;br /&gt;
    	Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;True&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEDIDFreqs&amp;quot; &amp;quot;FALSE&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;FALSE&amp;quot;&lt;br /&gt;
    	#!# Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoEdidModes&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Device&amp;quot;&lt;br /&gt;
    	### Available Driver options are:-&lt;br /&gt;
    	### Values: &amp;lt;i&amp;gt;: integer, &amp;lt;f&amp;gt;: float, &amp;lt;bool&amp;gt;: &amp;quot;True&amp;quot;/&amp;quot;False&amp;quot;,&lt;br /&gt;
    	### &amp;lt;string&amp;gt;: &amp;quot;String&amp;quot;, &amp;lt;freq&amp;gt;: &amp;quot;&amp;lt;f&amp;gt; Hz/kHz/MHz&amp;quot;&lt;br /&gt;
    	### [arg]: arg optional&lt;br /&gt;
    	#Option		&amp;quot;NoAccel&amp;quot;				# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;SWcursor&amp;quot;				# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;ColorKey&amp;quot;				# &amp;lt;i&amp;gt;&lt;br /&gt;
    	#Option		&amp;quot;CacheLines&amp;quot;			# &amp;lt;i&amp;gt;&lt;br /&gt;
    	#Option		&amp;quot;Dac6Bit&amp;quot;				# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;DRI&amp;quot;					# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;NoDDC&amp;quot;					# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;ShowCache&amp;quot;				# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;XvMCSurfaces&amp;quot;			# &amp;lt;i&amp;gt;&lt;br /&gt;
    	Identifier	&amp;quot;Card0&amp;quot;&lt;br /&gt;
    	Driver		&amp;quot;nvidia&amp;quot;&lt;br /&gt;
    	VendorName	&amp;quot;Unknown Vendor Name&amp;quot;&lt;br /&gt;
    	BoardName	&amp;quot;Unknown Board Name&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;LinearAlloc&amp;quot;		&amp;quot;16384&amp;quot;&lt;br /&gt;
    	#BusID		&amp;quot;PCI:0:2:0&amp;quot;&lt;br /&gt;
    #	Option		&amp;quot;NoDDC&amp;quot;				&amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;XvmcUsesTextures&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;renderAccel&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoDDCValue&amp;quot;&lt;br /&gt;
    	# Option &amp;quot;UseEDID&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEDID&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
            Option &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	## Option         &amp;quot;TripleBuffer&amp;quot; &amp;quot;True&amp;quot;&lt;br /&gt;
    	Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoLogo&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoBandWidthTest&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes,NoEdidModes&amp;quot;&lt;br /&gt;
    	## Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoVertRefreshCheck, NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes&amp;quot;&lt;br /&gt;
    &lt;br /&gt;
    	Option &amp;quot;DynamicTwinView&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEvents&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	## CJA Maybe remove ?&lt;br /&gt;
    	Option &amp;quot;AllowGLXWithComposite&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AddARGBGLXVisuals&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;ConnectedMonitor&amp;quot; &amp;quot;DFP&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Screen&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;Screen0&amp;quot;&lt;br /&gt;
    	Device		&amp;quot;Card0&amp;quot;&lt;br /&gt;
    	Monitor		&amp;quot;Monitor0&amp;quot;&lt;br /&gt;
    	DefaultDepth	24&lt;br /&gt;
    	Option	    &amp;quot;FlatPanelProperties&amp;quot; &amp;quot;Scaling = Native&amp;quot; &lt;br /&gt;
    	Option	    &amp;quot;TwinView&amp;quot; &amp;quot;0&amp;quot; &lt;br /&gt;
    	SubSection &amp;quot;Display&amp;quot;&lt;br /&gt;
    		## Modes		&amp;quot;1920x1080_50i&amp;quot; &amp;quot;1920x1080_50i_0&amp;quot; &amp;quot;1920x1080_my50i&amp;quot;&lt;br /&gt;
    		## Virtual		1920 1080&lt;br /&gt;
    		Depth     24 &lt;br /&gt;
    &lt;br /&gt;
    		Modes &amp;quot;1920x1080@50&amp;quot; &amp;quot;1920x1080@60&amp;quot; &amp;quot;1920x1080@24&amp;quot; &amp;quot;1920x1080@23.976&amp;quot; &amp;quot;1920x1080@50i&amp;quot;&lt;br /&gt;
    		Modes &amp;quot;1920x1080@60i&amp;quot; &amp;quot;1920x1080@59.94&amp;quot; &amp;quot;1920x1080@59.94i&amp;quot;&lt;br /&gt;
    &lt;br /&gt;
    		## Modes &amp;quot;1920x1080@50i&amp;quot; &amp;quot;1920x1080@50&amp;quot; &amp;quot;1920x1080@60&amp;quot; &amp;quot;1920x1080@24&amp;quot; &amp;quot;1920x1080@23.976&amp;quot;&lt;br /&gt;
    		## Modes &amp;quot;1920x1080@60i&amp;quot; &amp;quot;1920x1080@59.94&amp;quot; &amp;quot;1920x1080@59.94i&amp;quot;&lt;br /&gt;
    		# Modes &amp;quot;1920x1080@25&amp;quot; &amp;quot;1920x1080@29.97&amp;quot; &amp;quot;1920x1080@30&amp;quot;&lt;br /&gt;
    	EndSubSection&lt;br /&gt;
    	Option &amp;quot;XvmcUsesTextures&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;renderAccel&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoDDCValue&amp;quot;&lt;br /&gt;
    	# Option &amp;quot;UseEDID&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEDID&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
            Option &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoLogo&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoBandWidthTest&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes,NoEdidModes&amp;quot;&lt;br /&gt;
    	## Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoVertRefreshCheck, NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes&amp;quot;&lt;br /&gt;
    	Option &amp;quot;DynamicTwinView&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEvents&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	## CJA Maybe remove ?&lt;br /&gt;
    	Option &amp;quot;AllowGLXWithComposite&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AddARGBGLXVisuals&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;TVStandard&amp;quot;	&amp;quot;1080p (16:9)&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;AllowMouseOpenFail&amp;quot;	&amp;quot;true&amp;quot;&lt;br /&gt;
    	Option  &amp;quot;AutoAddDevices&amp;quot; 	&amp;quot;false&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;BlankTime&amp;quot;		&amp;quot;0&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;StandbyTime&amp;quot;	&amp;quot;0&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;SuspendTime&amp;quot;	&amp;quot;0&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;OffTime&amp;quot;		&amp;quot;0&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;AIGLX&amp;quot;			&amp;quot;Off&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;Extensions&amp;quot;&lt;br /&gt;
    	Option &amp;quot;Composite&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	Option &amp;quot;RENDER&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Sony_KDL-46W4500&amp;diff=31689</id>
		<title>Sony KDL-46W4500</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Sony_KDL-46W4500&amp;diff=31689"/>
		<updated>2012-07-10T08:27:38Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Hardware]]&lt;br /&gt;
{{versioninfo|810Status=Working|810UpdatedDate=10th July 2012|810UpdatedBy=Viking}}&lt;br /&gt;
[[Category:Video]]&lt;br /&gt;
[[Category:Displays]]&lt;br /&gt;
&lt;br /&gt;
I am using an &#039;&#039;&#039;European&#039;&#039;&#039; version this TV and will try to describe problems I have here.&lt;br /&gt;
&lt;br /&gt;
Connected to a Nvidia 8400 GS with an DVI to HDMI cable. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;10th July 2012 - Currently I am using the judderfree solution further down with 0810 &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
I was not able to get the AV Wizard to setup the TV to 1080p with 50hz, so I setup 1080p and 60hz. Then afterwards I changed the xorg.conf and changed/added the following lines :&lt;br /&gt;
&lt;br /&gt;
 Option         &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
 Option         &amp;quot;UseEDID&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 Modes           &amp;quot;1920x1080_50_1&amp;quot; &amp;quot;1920x1080_50_0&amp;quot; &amp;quot;1920x1080_50&amp;quot; &amp;quot;1920x1080&amp;quot; &amp;quot;1920x1080_50i&amp;quot;&lt;br /&gt;
 VertRefresh     49-51&lt;br /&gt;
&lt;br /&gt;
and rebooted. After that I had 50hz.&lt;br /&gt;
&lt;br /&gt;
The line &amp;quot;1920x1080_50&amp;quot; uses the EDID information it gets of the TV and sets things up correctly. In the /var/log/Xorg.0.log you can then see that it chooses the right resolution.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot; is important, otherwise you will get very small unreadable characters.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
I did also start KDE and then start nvidia-settings. Then below OpenGL settings activated the checkbox next to &amp;quot;Sync to VBlank&amp;quot; so that it is used.&lt;br /&gt;
&lt;br /&gt;
Then in MythTV (see here http://www.mythtv.org/wiki/VDPAU#Enabling_VDPAU_in_MythFrontend) under &amp;quot;Utilities -&amp;gt; Setup -&amp;gt; TV Settings -&amp;gt; Playback -&amp;gt; Playback Profiles (3/8)&amp;quot; setup &amp;quot;VDPAU Normal&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Not sure what fixed my LiveTV juddering in the end.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Judder free TV and Video with MythTV and MythTV video plugin ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;10th July 2012 - This is the CURRENT solution I am using with 0810 &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Using the description from here :&lt;br /&gt;
http://www.mythtv.org/wiki/User_Manual:JudderFree&lt;br /&gt;
&lt;br /&gt;
I did setup all the needed resolutions and changed MythTV to change the resolution as described in the link above. &#039;&#039;&#039;The xorg.conf from below works with that!!!&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
That way MýthTV&#039;s Video plugin will change the refresh rate to the right typ, no matter what kind of material you are playing. Execpt for PAL DVD&#039;s , they are for some reason set to NTSC 59.96 rate. I have no idea why at the monent.&lt;br /&gt;
&lt;br /&gt;
I have still setup the VDPAU things above in mythtv and &amp;quot;vsync to blanc&amp;quot; nvidia-settings !!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Alternate solution (I used first) ==&lt;br /&gt;
&lt;br /&gt;
I was not able to get the TV setup to 1080p with 50hz, so I choosed 1080p and 60hz. Then afterwards I changed the xorg.conf to the right 1080p@50hz Modeline i found in the HDTV list in the MythTV modeline database.&lt;br /&gt;
&lt;br /&gt;
        # 1920x1080 @ 50 Hz (EDID) HSync: 56.25 kHz&lt;br /&gt;
        ModeLine &amp;quot;1920x1080&amp;quot; 148.50 1920 2448 2496 2640 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
&lt;br /&gt;
And changed the VertRefresh to :&lt;br /&gt;
        VertRefresh     49-51&lt;br /&gt;
&lt;br /&gt;
and rebooted. After that I had 50hz.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== My latest xorg.conf ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    Section &amp;quot;ServerLayout&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;XFree86 Configured&amp;quot;&lt;br /&gt;
    	Screen	  0	&amp;quot;Screen0&amp;quot;	0 0&lt;br /&gt;
    	InputDevice	&amp;quot;Mouse0&amp;quot;	&amp;quot;CorePointer&amp;quot;&lt;br /&gt;
    	InputDevice	&amp;quot;Keyboard0&amp;quot;	&amp;quot;CoreKeyboard&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Files&amp;quot;&lt;br /&gt;
    #	RgbPath		&amp;quot;/usr/X11R6/lib/X11/rgb&amp;quot;&lt;br /&gt;
    	ModulePath	&amp;quot;/usr/lib/xorg/modules&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/share/fonts/X11&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/misc/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/Speedo/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/Type1/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/CID/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/75dpi/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/100dpi/&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Module&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;dbe&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;extmod&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;record&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;xtrap&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;speedo&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;type1&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;glx&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;int10&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;v4l&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;InputDevice&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;Keyboard0&amp;quot;&lt;br /&gt;
    	Driver		&amp;quot;keyboard&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;XkbLayout&amp;quot;		&amp;quot;us&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;XkbVariant&amp;quot;	&amp;quot;basic&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;XkbModel&amp;quot;		&amp;quot;pc105&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;InputDevice&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;Mouse0&amp;quot;&lt;br /&gt;
    	Driver		&amp;quot;mouse&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;Protocol&amp;quot;		&amp;quot;auto&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;Device&amp;quot;		&amp;quot;/dev/input/mice&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;ZAxisMapping&amp;quot;	&amp;quot;4 5&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Monitor&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;Monitor0&amp;quot;&lt;br /&gt;
    	VendorName	&amp;quot;Sony&amp;quot;&lt;br /&gt;
    	ModelName	&amp;quot;46&amp;quot;&lt;br /&gt;
    	## HorizSync	20-500&lt;br /&gt;
    	# 1920x1080 @ 50 Hz (EDID) HSync: 28.125 kHz&lt;br /&gt;
    	## VertRefresh	49-51&lt;br /&gt;
    	## ModeLine &amp;quot;1920x1080_my50i&amp;quot; 74.25 1920 2448 2492 2640 1080 1084 1094 1124 +HSync +VSync Interlace&lt;br /&gt;
            # 1920x1080 @ 50 Hz (EDID) HSync: 56.25 kHz&lt;br /&gt;
            ## ModeLine &amp;quot;1920x1080_my50&amp;quot; 148.50 1920 2448 2496 2640 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
    &lt;br /&gt;
    	# 1920x1080p @ 50Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@50&amp;quot; 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 60Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@60&amp;quot; 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 24Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@24&amp;quot; 74.250 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 23.976Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@23.976&amp;quot; 74.175 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080i @ 50Hz (EIA/CEA-861B) &lt;br /&gt;
    	Modeline &amp;quot;1920x1080@50i&amp;quot; 74.250 1920 2448 2492 2640 1080 1085 1095 1125 +hsync +vsync Interlace &lt;br /&gt;
    	# 1920x1080i @ 60Hz (EIA/CEA-861B) &lt;br /&gt;
    	Modeline &amp;quot;1920x1080@60i&amp;quot; 74.250 1920 2008 2052 2200 1080 1085 1095 1125 +hsync +vsync interlace &lt;br /&gt;
    	# 1920x1080p @ 59.94Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@59.94&amp;quot; 148.350 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080i @ 59.94Hz (EIA/CEA-861B) &lt;br /&gt;
    	Modeline &amp;quot;1920x1080@59.94i&amp;quot; 74.175 1920 2008 2052 2200 1080 1085 1095 1125 +hsync +vsync Interlace &lt;br /&gt;
    	# 1920x1080p @ 25Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@25&amp;quot; 74.250 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 29.97Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@29.97&amp;quot; 74.175 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 30Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@30&amp;quot; 74.250 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	HorizSync	20.0 - 150.0 &lt;br /&gt;
    	VertRefresh     23.0 - 90.0 &lt;br /&gt;
    	Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;True&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEDIDFreqs&amp;quot; &amp;quot;FALSE&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;FALSE&amp;quot;&lt;br /&gt;
    	#!# Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoEdidModes&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Device&amp;quot;&lt;br /&gt;
    	### Available Driver options are:-&lt;br /&gt;
    	### Values: &amp;lt;i&amp;gt;: integer, &amp;lt;f&amp;gt;: float, &amp;lt;bool&amp;gt;: &amp;quot;True&amp;quot;/&amp;quot;False&amp;quot;,&lt;br /&gt;
    	### &amp;lt;string&amp;gt;: &amp;quot;String&amp;quot;, &amp;lt;freq&amp;gt;: &amp;quot;&amp;lt;f&amp;gt; Hz/kHz/MHz&amp;quot;&lt;br /&gt;
    	### [arg]: arg optional&lt;br /&gt;
    	#Option		&amp;quot;NoAccel&amp;quot;				# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;SWcursor&amp;quot;				# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;ColorKey&amp;quot;				# &amp;lt;i&amp;gt;&lt;br /&gt;
    	#Option		&amp;quot;CacheLines&amp;quot;			# &amp;lt;i&amp;gt;&lt;br /&gt;
    	#Option		&amp;quot;Dac6Bit&amp;quot;				# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;DRI&amp;quot;					# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;NoDDC&amp;quot;					# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;ShowCache&amp;quot;				# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;XvMCSurfaces&amp;quot;			# &amp;lt;i&amp;gt;&lt;br /&gt;
    	Identifier	&amp;quot;Card0&amp;quot;&lt;br /&gt;
    	Driver		&amp;quot;nvidia&amp;quot;&lt;br /&gt;
    	VendorName	&amp;quot;Unknown Vendor Name&amp;quot;&lt;br /&gt;
    	BoardName	&amp;quot;Unknown Board Name&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;LinearAlloc&amp;quot;		&amp;quot;16384&amp;quot;&lt;br /&gt;
    	#BusID		&amp;quot;PCI:0:2:0&amp;quot;&lt;br /&gt;
    #	Option		&amp;quot;NoDDC&amp;quot;				&amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;XvmcUsesTextures&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;renderAccel&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoDDCValue&amp;quot;&lt;br /&gt;
    	# Option &amp;quot;UseEDID&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEDID&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
            Option &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	## Option         &amp;quot;TripleBuffer&amp;quot; &amp;quot;True&amp;quot;&lt;br /&gt;
    	Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoLogo&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoBandWidthTest&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes,NoEdidModes&amp;quot;&lt;br /&gt;
    	## Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoVertRefreshCheck, NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes&amp;quot;&lt;br /&gt;
    &lt;br /&gt;
    	Option &amp;quot;DynamicTwinView&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEvents&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	## CJA Maybe remove ?&lt;br /&gt;
    	Option &amp;quot;AllowGLXWithComposite&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AddARGBGLXVisuals&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;ConnectedMonitor&amp;quot; &amp;quot;DFP&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Screen&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;Screen0&amp;quot;&lt;br /&gt;
    	Device		&amp;quot;Card0&amp;quot;&lt;br /&gt;
    	Monitor		&amp;quot;Monitor0&amp;quot;&lt;br /&gt;
    	DefaultDepth	24&lt;br /&gt;
    	Option	    &amp;quot;FlatPanelProperties&amp;quot; &amp;quot;Scaling = Native&amp;quot; &lt;br /&gt;
    	Option	    &amp;quot;TwinView&amp;quot; &amp;quot;0&amp;quot; &lt;br /&gt;
    	SubSection &amp;quot;Display&amp;quot;&lt;br /&gt;
    		## Modes		&amp;quot;1920x1080_50i&amp;quot; &amp;quot;1920x1080_50i_0&amp;quot; &amp;quot;1920x1080_my50i&amp;quot;&lt;br /&gt;
    		## Virtual		1920 1080&lt;br /&gt;
    		Depth     24 &lt;br /&gt;
    &lt;br /&gt;
    		Modes &amp;quot;1920x1080@50&amp;quot; &amp;quot;1920x1080@60&amp;quot; &amp;quot;1920x1080@24&amp;quot; &amp;quot;1920x1080@23.976&amp;quot; &amp;quot;1920x1080@50i&amp;quot;&lt;br /&gt;
    		Modes &amp;quot;1920x1080@60i&amp;quot; &amp;quot;1920x1080@59.94&amp;quot; &amp;quot;1920x1080@59.94i&amp;quot;&lt;br /&gt;
    &lt;br /&gt;
    		## Modes &amp;quot;1920x1080@50i&amp;quot; &amp;quot;1920x1080@50&amp;quot; &amp;quot;1920x1080@60&amp;quot; &amp;quot;1920x1080@24&amp;quot; &amp;quot;1920x1080@23.976&amp;quot;&lt;br /&gt;
    		## Modes &amp;quot;1920x1080@60i&amp;quot; &amp;quot;1920x1080@59.94&amp;quot; &amp;quot;1920x1080@59.94i&amp;quot;&lt;br /&gt;
    		# Modes &amp;quot;1920x1080@25&amp;quot; &amp;quot;1920x1080@29.97&amp;quot; &amp;quot;1920x1080@30&amp;quot;&lt;br /&gt;
    	EndSubSection&lt;br /&gt;
    	Option &amp;quot;XvmcUsesTextures&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;renderAccel&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoDDCValue&amp;quot;&lt;br /&gt;
    	# Option &amp;quot;UseEDID&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEDID&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
            Option &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoLogo&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoBandWidthTest&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes,NoEdidModes&amp;quot;&lt;br /&gt;
    	## Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoVertRefreshCheck, NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes&amp;quot;&lt;br /&gt;
    	Option &amp;quot;DynamicTwinView&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEvents&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	## CJA Maybe remove ?&lt;br /&gt;
    	Option &amp;quot;AllowGLXWithComposite&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AddARGBGLXVisuals&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;TVStandard&amp;quot;	&amp;quot;1080p (16:9)&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;AllowMouseOpenFail&amp;quot;	&amp;quot;true&amp;quot;&lt;br /&gt;
    	Option  &amp;quot;AutoAddDevices&amp;quot; 	&amp;quot;false&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;BlankTime&amp;quot;		&amp;quot;0&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;StandbyTime&amp;quot;	&amp;quot;0&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;SuspendTime&amp;quot;	&amp;quot;0&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;OffTime&amp;quot;		&amp;quot;0&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;AIGLX&amp;quot;			&amp;quot;Off&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;Extensions&amp;quot;&lt;br /&gt;
    	Option &amp;quot;Composite&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	Option &amp;quot;RENDER&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Sony_KDL-46W4500&amp;diff=31688</id>
		<title>Sony KDL-46W4500</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Sony_KDL-46W4500&amp;diff=31688"/>
		<updated>2012-07-10T08:26:29Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Hardware]]&lt;br /&gt;
{{versioninfo|810Status=Working|810UpdatedDate=10th July 2012|810UpdatedBy=Viking}}&lt;br /&gt;
[[Category:Video]]&lt;br /&gt;
[[Category:Displays]]&lt;br /&gt;
&lt;br /&gt;
I am using an &#039;&#039;&#039;European&#039;&#039;&#039; version this TV and will try to describe problems I have here.&lt;br /&gt;
&lt;br /&gt;
Connected to a Nvidia 8400 GS with an DVI to HDMI cable. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;10th July 2012 - Currently I am using the judderfree solution further down with 0810 &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
I was not able to get the AV Wizard to setup the TV to 1080p with 50hz, so I setup 1080p and 60hz. Then afterwards I changed the xorg.conf and changed/added the following lines :&lt;br /&gt;
&lt;br /&gt;
 Option         &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
 Option         &amp;quot;UseEDID&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 Modes           &amp;quot;1920x1080_50_1&amp;quot; &amp;quot;1920x1080_50_0&amp;quot; &amp;quot;1920x1080_50&amp;quot; &amp;quot;1920x1080&amp;quot; &amp;quot;1920x1080_50i&amp;quot;&lt;br /&gt;
 VertRefresh     49-51&lt;br /&gt;
&lt;br /&gt;
and rebooted. After that I had 50hz.&lt;br /&gt;
&lt;br /&gt;
The line &amp;quot;1920x1080_50&amp;quot; uses the EDID information it gets of the TV and sets things up correctly. In the /var/log/Xorg.0.log you can then see that it chooses the right resolution.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot; is important, otherwise you will get very small unreadable characters.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
I did also start KDE and then start nvidia-settings. Then below OpenGL settings activated the checkbox next to &amp;quot;Sync to VBlank&amp;quot; so that it is used.&lt;br /&gt;
&lt;br /&gt;
Then in MythTV (see here http://www.mythtv.org/wiki/VDPAU#Enabling_VDPAU_in_MythFrontend) under &amp;quot;Utilities -&amp;gt; Setup -&amp;gt; TV Settings -&amp;gt; Playback -&amp;gt; Playback Profiles (3/8)&amp;quot; setup &amp;quot;VDPAU Normal&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Not sure what fixed my LiveTV juddering in the end.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Judder free TV and Video with MythTV and MythTV video plugin ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;10th July 2012 - This is the CURRENT solution I am using with 0810 &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Using the description from here :&lt;br /&gt;
http://www.mythtv.org/wiki/User_Manual:JudderFree&lt;br /&gt;
&lt;br /&gt;
I did setup all the needed resolutions and changed MythTV to change the resolution as described in the link above. &#039;&#039;&#039;The xorg.conf from below works with that!!!&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
That way MýthTV&#039;s Video plugin will change the refresh rate to the right typ, no matter what kind of material you are playing. Execpt for PAL DVD&#039;s , they are for some reason set to NTSC 59.96 rate. I have no idea why at the monent.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Alternate solution (I used first) ==&lt;br /&gt;
&lt;br /&gt;
I was not able to get the TV setup to 1080p with 50hz, so I choosed 1080p and 60hz. Then afterwards I changed the xorg.conf to the right 1080p@50hz Modeline i found in the HDTV list in the MythTV modeline database.&lt;br /&gt;
&lt;br /&gt;
        # 1920x1080 @ 50 Hz (EDID) HSync: 56.25 kHz&lt;br /&gt;
        ModeLine &amp;quot;1920x1080&amp;quot; 148.50 1920 2448 2496 2640 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
&lt;br /&gt;
And changed the VertRefresh to :&lt;br /&gt;
        VertRefresh     49-51&lt;br /&gt;
&lt;br /&gt;
and rebooted. After that I had 50hz.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== My latest xorg.conf ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    Section &amp;quot;ServerLayout&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;XFree86 Configured&amp;quot;&lt;br /&gt;
    	Screen	  0	&amp;quot;Screen0&amp;quot;	0 0&lt;br /&gt;
    	InputDevice	&amp;quot;Mouse0&amp;quot;	&amp;quot;CorePointer&amp;quot;&lt;br /&gt;
    	InputDevice	&amp;quot;Keyboard0&amp;quot;	&amp;quot;CoreKeyboard&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Files&amp;quot;&lt;br /&gt;
    #	RgbPath		&amp;quot;/usr/X11R6/lib/X11/rgb&amp;quot;&lt;br /&gt;
    	ModulePath	&amp;quot;/usr/lib/xorg/modules&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/share/fonts/X11&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/misc/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/Speedo/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/Type1/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/CID/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/75dpi/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/100dpi/&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Module&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;dbe&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;extmod&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;record&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;xtrap&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;speedo&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;type1&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;glx&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;int10&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;v4l&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;InputDevice&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;Keyboard0&amp;quot;&lt;br /&gt;
    	Driver		&amp;quot;keyboard&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;XkbLayout&amp;quot;		&amp;quot;us&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;XkbVariant&amp;quot;	&amp;quot;basic&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;XkbModel&amp;quot;		&amp;quot;pc105&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;InputDevice&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;Mouse0&amp;quot;&lt;br /&gt;
    	Driver		&amp;quot;mouse&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;Protocol&amp;quot;		&amp;quot;auto&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;Device&amp;quot;		&amp;quot;/dev/input/mice&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;ZAxisMapping&amp;quot;	&amp;quot;4 5&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Monitor&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;Monitor0&amp;quot;&lt;br /&gt;
    	VendorName	&amp;quot;Sony&amp;quot;&lt;br /&gt;
    	ModelName	&amp;quot;46&amp;quot;&lt;br /&gt;
    	## HorizSync	20-500&lt;br /&gt;
    	# 1920x1080 @ 50 Hz (EDID) HSync: 28.125 kHz&lt;br /&gt;
    	## VertRefresh	49-51&lt;br /&gt;
    	## ModeLine &amp;quot;1920x1080_my50i&amp;quot; 74.25 1920 2448 2492 2640 1080 1084 1094 1124 +HSync +VSync Interlace&lt;br /&gt;
            # 1920x1080 @ 50 Hz (EDID) HSync: 56.25 kHz&lt;br /&gt;
            ## ModeLine &amp;quot;1920x1080_my50&amp;quot; 148.50 1920 2448 2496 2640 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
    &lt;br /&gt;
    	# 1920x1080p @ 50Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@50&amp;quot; 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 60Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@60&amp;quot; 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 24Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@24&amp;quot; 74.250 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 23.976Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@23.976&amp;quot; 74.175 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080i @ 50Hz (EIA/CEA-861B) &lt;br /&gt;
    	Modeline &amp;quot;1920x1080@50i&amp;quot; 74.250 1920 2448 2492 2640 1080 1085 1095 1125 +hsync +vsync Interlace &lt;br /&gt;
    	# 1920x1080i @ 60Hz (EIA/CEA-861B) &lt;br /&gt;
    	Modeline &amp;quot;1920x1080@60i&amp;quot; 74.250 1920 2008 2052 2200 1080 1085 1095 1125 +hsync +vsync interlace &lt;br /&gt;
    	# 1920x1080p @ 59.94Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@59.94&amp;quot; 148.350 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080i @ 59.94Hz (EIA/CEA-861B) &lt;br /&gt;
    	Modeline &amp;quot;1920x1080@59.94i&amp;quot; 74.175 1920 2008 2052 2200 1080 1085 1095 1125 +hsync +vsync Interlace &lt;br /&gt;
    	# 1920x1080p @ 25Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@25&amp;quot; 74.250 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 29.97Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@29.97&amp;quot; 74.175 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 30Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@30&amp;quot; 74.250 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	HorizSync	20.0 - 150.0 &lt;br /&gt;
    	VertRefresh     23.0 - 90.0 &lt;br /&gt;
    	Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;True&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEDIDFreqs&amp;quot; &amp;quot;FALSE&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;FALSE&amp;quot;&lt;br /&gt;
    	#!# Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoEdidModes&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Device&amp;quot;&lt;br /&gt;
    	### Available Driver options are:-&lt;br /&gt;
    	### Values: &amp;lt;i&amp;gt;: integer, &amp;lt;f&amp;gt;: float, &amp;lt;bool&amp;gt;: &amp;quot;True&amp;quot;/&amp;quot;False&amp;quot;,&lt;br /&gt;
    	### &amp;lt;string&amp;gt;: &amp;quot;String&amp;quot;, &amp;lt;freq&amp;gt;: &amp;quot;&amp;lt;f&amp;gt; Hz/kHz/MHz&amp;quot;&lt;br /&gt;
    	### [arg]: arg optional&lt;br /&gt;
    	#Option		&amp;quot;NoAccel&amp;quot;				# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;SWcursor&amp;quot;				# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;ColorKey&amp;quot;				# &amp;lt;i&amp;gt;&lt;br /&gt;
    	#Option		&amp;quot;CacheLines&amp;quot;			# &amp;lt;i&amp;gt;&lt;br /&gt;
    	#Option		&amp;quot;Dac6Bit&amp;quot;				# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;DRI&amp;quot;					# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;NoDDC&amp;quot;					# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;ShowCache&amp;quot;				# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;XvMCSurfaces&amp;quot;			# &amp;lt;i&amp;gt;&lt;br /&gt;
    	Identifier	&amp;quot;Card0&amp;quot;&lt;br /&gt;
    	Driver		&amp;quot;nvidia&amp;quot;&lt;br /&gt;
    	VendorName	&amp;quot;Unknown Vendor Name&amp;quot;&lt;br /&gt;
    	BoardName	&amp;quot;Unknown Board Name&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;LinearAlloc&amp;quot;		&amp;quot;16384&amp;quot;&lt;br /&gt;
    	#BusID		&amp;quot;PCI:0:2:0&amp;quot;&lt;br /&gt;
    #	Option		&amp;quot;NoDDC&amp;quot;				&amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;XvmcUsesTextures&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;renderAccel&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoDDCValue&amp;quot;&lt;br /&gt;
    	# Option &amp;quot;UseEDID&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEDID&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
            Option &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	## Option         &amp;quot;TripleBuffer&amp;quot; &amp;quot;True&amp;quot;&lt;br /&gt;
    	Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoLogo&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoBandWidthTest&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes,NoEdidModes&amp;quot;&lt;br /&gt;
    	## Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoVertRefreshCheck, NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes&amp;quot;&lt;br /&gt;
    &lt;br /&gt;
    	Option &amp;quot;DynamicTwinView&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEvents&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	## CJA Maybe remove ?&lt;br /&gt;
    	Option &amp;quot;AllowGLXWithComposite&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AddARGBGLXVisuals&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;ConnectedMonitor&amp;quot; &amp;quot;DFP&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Screen&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;Screen0&amp;quot;&lt;br /&gt;
    	Device		&amp;quot;Card0&amp;quot;&lt;br /&gt;
    	Monitor		&amp;quot;Monitor0&amp;quot;&lt;br /&gt;
    	DefaultDepth	24&lt;br /&gt;
    	Option	    &amp;quot;FlatPanelProperties&amp;quot; &amp;quot;Scaling = Native&amp;quot; &lt;br /&gt;
    	Option	    &amp;quot;TwinView&amp;quot; &amp;quot;0&amp;quot; &lt;br /&gt;
    	SubSection &amp;quot;Display&amp;quot;&lt;br /&gt;
    		## Modes		&amp;quot;1920x1080_50i&amp;quot; &amp;quot;1920x1080_50i_0&amp;quot; &amp;quot;1920x1080_my50i&amp;quot;&lt;br /&gt;
    		## Virtual		1920 1080&lt;br /&gt;
    		Depth     24 &lt;br /&gt;
    &lt;br /&gt;
    		Modes &amp;quot;1920x1080@50&amp;quot; &amp;quot;1920x1080@60&amp;quot; &amp;quot;1920x1080@24&amp;quot; &amp;quot;1920x1080@23.976&amp;quot; &amp;quot;1920x1080@50i&amp;quot;&lt;br /&gt;
    		Modes &amp;quot;1920x1080@60i&amp;quot; &amp;quot;1920x1080@59.94&amp;quot; &amp;quot;1920x1080@59.94i&amp;quot;&lt;br /&gt;
    &lt;br /&gt;
    		## Modes &amp;quot;1920x1080@50i&amp;quot; &amp;quot;1920x1080@50&amp;quot; &amp;quot;1920x1080@60&amp;quot; &amp;quot;1920x1080@24&amp;quot; &amp;quot;1920x1080@23.976&amp;quot;&lt;br /&gt;
    		## Modes &amp;quot;1920x1080@60i&amp;quot; &amp;quot;1920x1080@59.94&amp;quot; &amp;quot;1920x1080@59.94i&amp;quot;&lt;br /&gt;
    		# Modes &amp;quot;1920x1080@25&amp;quot; &amp;quot;1920x1080@29.97&amp;quot; &amp;quot;1920x1080@30&amp;quot;&lt;br /&gt;
    	EndSubSection&lt;br /&gt;
    	Option &amp;quot;XvmcUsesTextures&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;renderAccel&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoDDCValue&amp;quot;&lt;br /&gt;
    	# Option &amp;quot;UseEDID&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEDID&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
            Option &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoLogo&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoBandWidthTest&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes,NoEdidModes&amp;quot;&lt;br /&gt;
    	## Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoVertRefreshCheck, NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes&amp;quot;&lt;br /&gt;
    	Option &amp;quot;DynamicTwinView&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEvents&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	## CJA Maybe remove ?&lt;br /&gt;
    	Option &amp;quot;AllowGLXWithComposite&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AddARGBGLXVisuals&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;TVStandard&amp;quot;	&amp;quot;1080p (16:9)&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;AllowMouseOpenFail&amp;quot;	&amp;quot;true&amp;quot;&lt;br /&gt;
    	Option  &amp;quot;AutoAddDevices&amp;quot; 	&amp;quot;false&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;BlankTime&amp;quot;		&amp;quot;0&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;StandbyTime&amp;quot;	&amp;quot;0&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;SuspendTime&amp;quot;	&amp;quot;0&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;OffTime&amp;quot;		&amp;quot;0&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;AIGLX&amp;quot;			&amp;quot;Off&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;Extensions&amp;quot;&lt;br /&gt;
    	Option &amp;quot;Composite&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	Option &amp;quot;RENDER&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Sony_KDL-46W4500&amp;diff=31687</id>
		<title>Sony KDL-46W4500</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Sony_KDL-46W4500&amp;diff=31687"/>
		<updated>2012-07-10T08:15:42Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Hardware]]&lt;br /&gt;
{{versioninfo|810Status=Working|810UpdatedDate=10th July 2012|810UpdatedBy=Viking}}&lt;br /&gt;
[[Category:Video]]&lt;br /&gt;
[[Category:Displays]]&lt;br /&gt;
&lt;br /&gt;
I am using an &#039;&#039;&#039;European&#039;&#039;&#039; version this TV and will try to describe problems I have here.&lt;br /&gt;
&lt;br /&gt;
Connected to a Nvidia 7300GT with an DVI to HDMI cable. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;NOTE that the 50 Hz modelines will probably not work if you try to connect to a non-HDMI port on the Sony TV (i.e. the PC input).  The Sony KDL-46WE5 (which is supposed to be very similar to this model) would not display 1920x1080 50Hz modelines when the PC was connected to the PC input on the TV.  This failure happened was using a VGA DB15 video cable attached to a DVI-DB15 converter - the graphics card in my PC has 2xDVI ports.  Once an DVI-HDMI converter and HDMI cable was used then the 50Hz modelines worked properly. The Sony manual has a single table for the graphics modes supported by the PC and HDMI inputs- this would lead you to believe that PC input and the HDMI inputs all support the same graphics modes but they don&#039;t. (Indulis&#039; experience)&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
I was not able to get the AV Wizard to setup the TV to 1080p with 50hz, so I chose 1080p and 60hz. Then afterwards I changed the xorg.conf and changed/added the following lines :&lt;br /&gt;
&lt;br /&gt;
 Option         &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
 Option         &amp;quot;UseEDID&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 Modes           &amp;quot;1920x1080_50_1&amp;quot; &amp;quot;1920x1080_50_0&amp;quot; &amp;quot;1920x1080_50&amp;quot; &amp;quot;1920x1080&amp;quot; &amp;quot;1920x1080_50i&amp;quot;&lt;br /&gt;
 VertRefresh     49-51&lt;br /&gt;
&lt;br /&gt;
and rebooted. After that I had 50hz.&lt;br /&gt;
&lt;br /&gt;
The line &amp;quot;1920x1080_50&amp;quot; uses the EDID information it gets of the TV and sets things up correctly. In the /var/log/Xorg.0.log you can then see that it chooses the right resolution.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot; is important, otherwise you will get very small unreadable characters.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Judder free TV and Video with MythTV and MythTV video plugin ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;This is the CURRENT solution I am using with 0810 &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Using the description from here :&lt;br /&gt;
http://www.mythtv.org/wiki/User_Manual:JudderFree&lt;br /&gt;
&lt;br /&gt;
I did setup all the needed resolutions and changed MythTV to change the resolution as described in the link above. The xorg.conf from below works with that!!!&lt;br /&gt;
&lt;br /&gt;
That way MýthTV&#039;s Video plugin will change the refresh rate to the right typ, no matter what kind of material you are playing. Execpt for PAL DVD&#039;s , they are for some reason set to NTSC 59.96 rate. I have no idea why at the monent.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Alternate solution (I used first) ==&lt;br /&gt;
&lt;br /&gt;
I was not able to get the TV setup to 1080p with 50hz, so I choosed 1080p and 60hz. Then afterwards I changed the xorg.conf to the right 1080p@50hz Modeline i found in the HDTV list in the MythTV modeline database.&lt;br /&gt;
&lt;br /&gt;
        # 1920x1080 @ 50 Hz (EDID) HSync: 56.25 kHz&lt;br /&gt;
        ModeLine &amp;quot;1920x1080&amp;quot; 148.50 1920 2448 2496 2640 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
&lt;br /&gt;
And changed the VertRefresh to :&lt;br /&gt;
        VertRefresh     49-51&lt;br /&gt;
&lt;br /&gt;
and rebooted. After that I had 50hz.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== My latest xorg.conf ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    Section &amp;quot;ServerLayout&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;XFree86 Configured&amp;quot;&lt;br /&gt;
    	Screen	  0	&amp;quot;Screen0&amp;quot;	0 0&lt;br /&gt;
    	InputDevice	&amp;quot;Mouse0&amp;quot;	&amp;quot;CorePointer&amp;quot;&lt;br /&gt;
    	InputDevice	&amp;quot;Keyboard0&amp;quot;	&amp;quot;CoreKeyboard&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Files&amp;quot;&lt;br /&gt;
    #	RgbPath		&amp;quot;/usr/X11R6/lib/X11/rgb&amp;quot;&lt;br /&gt;
    	ModulePath	&amp;quot;/usr/lib/xorg/modules&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/share/fonts/X11&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/misc/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/Speedo/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/Type1/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/CID/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/75dpi/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/100dpi/&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Module&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;dbe&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;extmod&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;record&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;xtrap&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;speedo&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;type1&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;glx&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;int10&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;v4l&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;InputDevice&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;Keyboard0&amp;quot;&lt;br /&gt;
    	Driver		&amp;quot;keyboard&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;XkbLayout&amp;quot;		&amp;quot;us&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;XkbVariant&amp;quot;	&amp;quot;basic&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;XkbModel&amp;quot;		&amp;quot;pc105&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;InputDevice&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;Mouse0&amp;quot;&lt;br /&gt;
    	Driver		&amp;quot;mouse&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;Protocol&amp;quot;		&amp;quot;auto&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;Device&amp;quot;		&amp;quot;/dev/input/mice&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;ZAxisMapping&amp;quot;	&amp;quot;4 5&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Monitor&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;Monitor0&amp;quot;&lt;br /&gt;
    	VendorName	&amp;quot;Sony&amp;quot;&lt;br /&gt;
    	ModelName	&amp;quot;46&amp;quot;&lt;br /&gt;
    	## HorizSync	20-500&lt;br /&gt;
    	# 1920x1080 @ 50 Hz (EDID) HSync: 28.125 kHz&lt;br /&gt;
    	## VertRefresh	49-51&lt;br /&gt;
    	## ModeLine &amp;quot;1920x1080_my50i&amp;quot; 74.25 1920 2448 2492 2640 1080 1084 1094 1124 +HSync +VSync Interlace&lt;br /&gt;
            # 1920x1080 @ 50 Hz (EDID) HSync: 56.25 kHz&lt;br /&gt;
            ## ModeLine &amp;quot;1920x1080_my50&amp;quot; 148.50 1920 2448 2496 2640 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
    &lt;br /&gt;
    	# 1920x1080p @ 50Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@50&amp;quot; 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 60Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@60&amp;quot; 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 24Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@24&amp;quot; 74.250 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 23.976Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@23.976&amp;quot; 74.175 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080i @ 50Hz (EIA/CEA-861B) &lt;br /&gt;
    	Modeline &amp;quot;1920x1080@50i&amp;quot; 74.250 1920 2448 2492 2640 1080 1085 1095 1125 +hsync +vsync Interlace &lt;br /&gt;
    	# 1920x1080i @ 60Hz (EIA/CEA-861B) &lt;br /&gt;
    	Modeline &amp;quot;1920x1080@60i&amp;quot; 74.250 1920 2008 2052 2200 1080 1085 1095 1125 +hsync +vsync interlace &lt;br /&gt;
    	# 1920x1080p @ 59.94Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@59.94&amp;quot; 148.350 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080i @ 59.94Hz (EIA/CEA-861B) &lt;br /&gt;
    	Modeline &amp;quot;1920x1080@59.94i&amp;quot; 74.175 1920 2008 2052 2200 1080 1085 1095 1125 +hsync +vsync Interlace &lt;br /&gt;
    	# 1920x1080p @ 25Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@25&amp;quot; 74.250 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 29.97Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@29.97&amp;quot; 74.175 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 30Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@30&amp;quot; 74.250 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	HorizSync	20.0 - 150.0 &lt;br /&gt;
    	VertRefresh     23.0 - 90.0 &lt;br /&gt;
    	Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;True&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEDIDFreqs&amp;quot; &amp;quot;FALSE&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;FALSE&amp;quot;&lt;br /&gt;
    	#!# Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoEdidModes&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Device&amp;quot;&lt;br /&gt;
    	### Available Driver options are:-&lt;br /&gt;
    	### Values: &amp;lt;i&amp;gt;: integer, &amp;lt;f&amp;gt;: float, &amp;lt;bool&amp;gt;: &amp;quot;True&amp;quot;/&amp;quot;False&amp;quot;,&lt;br /&gt;
    	### &amp;lt;string&amp;gt;: &amp;quot;String&amp;quot;, &amp;lt;freq&amp;gt;: &amp;quot;&amp;lt;f&amp;gt; Hz/kHz/MHz&amp;quot;&lt;br /&gt;
    	### [arg]: arg optional&lt;br /&gt;
    	#Option		&amp;quot;NoAccel&amp;quot;				# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;SWcursor&amp;quot;				# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;ColorKey&amp;quot;				# &amp;lt;i&amp;gt;&lt;br /&gt;
    	#Option		&amp;quot;CacheLines&amp;quot;			# &amp;lt;i&amp;gt;&lt;br /&gt;
    	#Option		&amp;quot;Dac6Bit&amp;quot;				# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;DRI&amp;quot;					# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;NoDDC&amp;quot;					# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;ShowCache&amp;quot;				# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;XvMCSurfaces&amp;quot;			# &amp;lt;i&amp;gt;&lt;br /&gt;
    	Identifier	&amp;quot;Card0&amp;quot;&lt;br /&gt;
    	Driver		&amp;quot;nvidia&amp;quot;&lt;br /&gt;
    	VendorName	&amp;quot;Unknown Vendor Name&amp;quot;&lt;br /&gt;
    	BoardName	&amp;quot;Unknown Board Name&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;LinearAlloc&amp;quot;		&amp;quot;16384&amp;quot;&lt;br /&gt;
    	#BusID		&amp;quot;PCI:0:2:0&amp;quot;&lt;br /&gt;
    #	Option		&amp;quot;NoDDC&amp;quot;				&amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;XvmcUsesTextures&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;renderAccel&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoDDCValue&amp;quot;&lt;br /&gt;
    	# Option &amp;quot;UseEDID&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEDID&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
            Option &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	## Option         &amp;quot;TripleBuffer&amp;quot; &amp;quot;True&amp;quot;&lt;br /&gt;
    	Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoLogo&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoBandWidthTest&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes,NoEdidModes&amp;quot;&lt;br /&gt;
    	## Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoVertRefreshCheck, NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes&amp;quot;&lt;br /&gt;
    &lt;br /&gt;
    	Option &amp;quot;DynamicTwinView&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEvents&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	## CJA Maybe remove ?&lt;br /&gt;
    	Option &amp;quot;AllowGLXWithComposite&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AddARGBGLXVisuals&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;ConnectedMonitor&amp;quot; &amp;quot;DFP&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Screen&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;Screen0&amp;quot;&lt;br /&gt;
    	Device		&amp;quot;Card0&amp;quot;&lt;br /&gt;
    	Monitor		&amp;quot;Monitor0&amp;quot;&lt;br /&gt;
    	DefaultDepth	24&lt;br /&gt;
    	Option	    &amp;quot;FlatPanelProperties&amp;quot; &amp;quot;Scaling = Native&amp;quot; &lt;br /&gt;
    	Option	    &amp;quot;TwinView&amp;quot; &amp;quot;0&amp;quot; &lt;br /&gt;
    	SubSection &amp;quot;Display&amp;quot;&lt;br /&gt;
    		## Modes		&amp;quot;1920x1080_50i&amp;quot; &amp;quot;1920x1080_50i_0&amp;quot; &amp;quot;1920x1080_my50i&amp;quot;&lt;br /&gt;
    		## Virtual		1920 1080&lt;br /&gt;
    		Depth     24 &lt;br /&gt;
    &lt;br /&gt;
    		Modes &amp;quot;1920x1080@50&amp;quot; &amp;quot;1920x1080@60&amp;quot; &amp;quot;1920x1080@24&amp;quot; &amp;quot;1920x1080@23.976&amp;quot; &amp;quot;1920x1080@50i&amp;quot;&lt;br /&gt;
    		Modes &amp;quot;1920x1080@60i&amp;quot; &amp;quot;1920x1080@59.94&amp;quot; &amp;quot;1920x1080@59.94i&amp;quot;&lt;br /&gt;
    &lt;br /&gt;
    		## Modes &amp;quot;1920x1080@50i&amp;quot; &amp;quot;1920x1080@50&amp;quot; &amp;quot;1920x1080@60&amp;quot; &amp;quot;1920x1080@24&amp;quot; &amp;quot;1920x1080@23.976&amp;quot;&lt;br /&gt;
    		## Modes &amp;quot;1920x1080@60i&amp;quot; &amp;quot;1920x1080@59.94&amp;quot; &amp;quot;1920x1080@59.94i&amp;quot;&lt;br /&gt;
    		# Modes &amp;quot;1920x1080@25&amp;quot; &amp;quot;1920x1080@29.97&amp;quot; &amp;quot;1920x1080@30&amp;quot;&lt;br /&gt;
    	EndSubSection&lt;br /&gt;
    	Option &amp;quot;XvmcUsesTextures&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;renderAccel&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoDDCValue&amp;quot;&lt;br /&gt;
    	# Option &amp;quot;UseEDID&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEDID&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
            Option &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoLogo&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoBandWidthTest&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes,NoEdidModes&amp;quot;&lt;br /&gt;
    	## Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoVertRefreshCheck, NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes&amp;quot;&lt;br /&gt;
    	Option &amp;quot;DynamicTwinView&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEvents&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	## CJA Maybe remove ?&lt;br /&gt;
    	Option &amp;quot;AllowGLXWithComposite&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AddARGBGLXVisuals&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;TVStandard&amp;quot;	&amp;quot;1080p (16:9)&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;AllowMouseOpenFail&amp;quot;	&amp;quot;true&amp;quot;&lt;br /&gt;
    	Option  &amp;quot;AutoAddDevices&amp;quot; 	&amp;quot;false&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;BlankTime&amp;quot;		&amp;quot;0&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;StandbyTime&amp;quot;	&amp;quot;0&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;SuspendTime&amp;quot;	&amp;quot;0&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;OffTime&amp;quot;		&amp;quot;0&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;AIGLX&amp;quot;			&amp;quot;Off&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;Extensions&amp;quot;&lt;br /&gt;
    	Option &amp;quot;Composite&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	Option &amp;quot;RENDER&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Sony_KDL-46W4500&amp;diff=31686</id>
		<title>Sony KDL-46W4500</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Sony_KDL-46W4500&amp;diff=31686"/>
		<updated>2012-07-10T08:13:52Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Hardware]]&lt;br /&gt;
{{Versioninfo}}&lt;br /&gt;
[[Category:Video]]&lt;br /&gt;
[[Category:Displays]]&lt;br /&gt;
&lt;br /&gt;
I am using an &#039;&#039;&#039;European&#039;&#039;&#039; version this TV and will try to describe problems I have here.&lt;br /&gt;
&lt;br /&gt;
Connected to a Nvidia 7300GT with an DVI to HDMI cable. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;NOTE that the 50 Hz modelines will probably not work if you try to connect to a non-HDMI port on the Sony TV (i.e. the PC input).  The Sony KDL-46WE5 (which is supposed to be very similar to this model) would not display 1920x1080 50Hz modelines when the PC was connected to the PC input on the TV.  This failure happened was using a VGA DB15 video cable attached to a DVI-DB15 converter - the graphics card in my PC has 2xDVI ports.  Once an DVI-HDMI converter and HDMI cable was used then the 50Hz modelines worked properly. The Sony manual has a single table for the graphics modes supported by the PC and HDMI inputs- this would lead you to believe that PC input and the HDMI inputs all support the same graphics modes but they don&#039;t. (Indulis&#039; experience)&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
I was not able to get the AV Wizard to setup the TV to 1080p with 50hz, so I chose 1080p and 60hz. Then afterwards I changed the xorg.conf and changed/added the following lines :&lt;br /&gt;
&lt;br /&gt;
 Option         &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
 Option         &amp;quot;UseEDID&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 Modes           &amp;quot;1920x1080_50_1&amp;quot; &amp;quot;1920x1080_50_0&amp;quot; &amp;quot;1920x1080_50&amp;quot; &amp;quot;1920x1080&amp;quot; &amp;quot;1920x1080_50i&amp;quot;&lt;br /&gt;
 VertRefresh     49-51&lt;br /&gt;
&lt;br /&gt;
and rebooted. After that I had 50hz.&lt;br /&gt;
&lt;br /&gt;
The line &amp;quot;1920x1080_50&amp;quot; uses the EDID information it gets of the TV and sets things up correctly. In the /var/log/Xorg.0.log you can then see that it chooses the right resolution.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot; is important, otherwise you will get very small unreadable characters.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Judder free TV and Video with MythTV and MythTV video plugin ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;This is the CURRENT solution I am using with 0810 &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Using the description from here :&lt;br /&gt;
http://www.mythtv.org/wiki/User_Manual:JudderFree&lt;br /&gt;
&lt;br /&gt;
I did setup all the needed resolutions and changed MythTV to change the resolution as described in the link above. The xorg.conf from below works with that!!!&lt;br /&gt;
&lt;br /&gt;
That way MýthTV&#039;s Video plugin will change the refresh rate to the right typ, no matter what kind of material you are playing. Execpt for PAL DVD&#039;s , they are for some reason set to NTSC 59.96 rate. I have no idea why at the monent.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Alternate solution (I used first) ==&lt;br /&gt;
&lt;br /&gt;
I was not able to get the TV setup to 1080p with 50hz, so I choosed 1080p and 60hz. Then afterwards I changed the xorg.conf to the right 1080p@50hz Modeline i found in the HDTV list in the MythTV modeline database.&lt;br /&gt;
&lt;br /&gt;
        # 1920x1080 @ 50 Hz (EDID) HSync: 56.25 kHz&lt;br /&gt;
        ModeLine &amp;quot;1920x1080&amp;quot; 148.50 1920 2448 2496 2640 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
&lt;br /&gt;
And changed the VertRefresh to :&lt;br /&gt;
        VertRefresh     49-51&lt;br /&gt;
&lt;br /&gt;
and rebooted. After that I had 50hz.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== My latest xorg.conf ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    Section &amp;quot;ServerLayout&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;XFree86 Configured&amp;quot;&lt;br /&gt;
    	Screen	  0	&amp;quot;Screen0&amp;quot;	0 0&lt;br /&gt;
    	InputDevice	&amp;quot;Mouse0&amp;quot;	&amp;quot;CorePointer&amp;quot;&lt;br /&gt;
    	InputDevice	&amp;quot;Keyboard0&amp;quot;	&amp;quot;CoreKeyboard&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Files&amp;quot;&lt;br /&gt;
    #	RgbPath		&amp;quot;/usr/X11R6/lib/X11/rgb&amp;quot;&lt;br /&gt;
    	ModulePath	&amp;quot;/usr/lib/xorg/modules&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/share/fonts/X11&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/misc/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/Speedo/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/Type1/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/CID/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/75dpi/&amp;quot;&lt;br /&gt;
    	FontPath	&amp;quot;/usr/X11R6/lib/X11/fonts/100dpi/&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Module&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;dbe&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;extmod&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;record&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;xtrap&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;speedo&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;type1&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;glx&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;int10&amp;quot;&lt;br /&gt;
    	Load	&amp;quot;v4l&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;InputDevice&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;Keyboard0&amp;quot;&lt;br /&gt;
    	Driver		&amp;quot;keyboard&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;XkbLayout&amp;quot;		&amp;quot;us&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;XkbVariant&amp;quot;	&amp;quot;basic&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;XkbModel&amp;quot;		&amp;quot;pc105&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;InputDevice&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;Mouse0&amp;quot;&lt;br /&gt;
    	Driver		&amp;quot;mouse&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;Protocol&amp;quot;		&amp;quot;auto&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;Device&amp;quot;		&amp;quot;/dev/input/mice&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;ZAxisMapping&amp;quot;	&amp;quot;4 5&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Monitor&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;Monitor0&amp;quot;&lt;br /&gt;
    	VendorName	&amp;quot;Sony&amp;quot;&lt;br /&gt;
    	ModelName	&amp;quot;46&amp;quot;&lt;br /&gt;
    	## HorizSync	20-500&lt;br /&gt;
    	# 1920x1080 @ 50 Hz (EDID) HSync: 28.125 kHz&lt;br /&gt;
    	## VertRefresh	49-51&lt;br /&gt;
    	## ModeLine &amp;quot;1920x1080_my50i&amp;quot; 74.25 1920 2448 2492 2640 1080 1084 1094 1124 +HSync +VSync Interlace&lt;br /&gt;
            # 1920x1080 @ 50 Hz (EDID) HSync: 56.25 kHz&lt;br /&gt;
            ## ModeLine &amp;quot;1920x1080_my50&amp;quot; 148.50 1920 2448 2496 2640 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
    &lt;br /&gt;
    	# 1920x1080p @ 50Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@50&amp;quot; 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 60Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@60&amp;quot; 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 24Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@24&amp;quot; 74.250 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 23.976Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@23.976&amp;quot; 74.175 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080i @ 50Hz (EIA/CEA-861B) &lt;br /&gt;
    	Modeline &amp;quot;1920x1080@50i&amp;quot; 74.250 1920 2448 2492 2640 1080 1085 1095 1125 +hsync +vsync Interlace &lt;br /&gt;
    	# 1920x1080i @ 60Hz (EIA/CEA-861B) &lt;br /&gt;
    	Modeline &amp;quot;1920x1080@60i&amp;quot; 74.250 1920 2008 2052 2200 1080 1085 1095 1125 +hsync +vsync interlace &lt;br /&gt;
    	# 1920x1080p @ 59.94Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@59.94&amp;quot; 148.350 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080i @ 59.94Hz (EIA/CEA-861B) &lt;br /&gt;
    	Modeline &amp;quot;1920x1080@59.94i&amp;quot; 74.175 1920 2008 2052 2200 1080 1085 1095 1125 +hsync +vsync Interlace &lt;br /&gt;
    	# 1920x1080p @ 25Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@25&amp;quot; 74.250 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 29.97Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@29.97&amp;quot; 74.175 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	# 1920x1080p @ 30Hz (EIA/CEA-861B) &lt;br /&gt;
    	ModeLine &amp;quot;1920x1080@30&amp;quot; 74.250 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync &lt;br /&gt;
    	HorizSync	20.0 - 150.0 &lt;br /&gt;
    	VertRefresh     23.0 - 90.0 &lt;br /&gt;
    	Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;True&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEDIDFreqs&amp;quot; &amp;quot;FALSE&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;FALSE&amp;quot;&lt;br /&gt;
    	#!# Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoEdidModes&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Device&amp;quot;&lt;br /&gt;
    	### Available Driver options are:-&lt;br /&gt;
    	### Values: &amp;lt;i&amp;gt;: integer, &amp;lt;f&amp;gt;: float, &amp;lt;bool&amp;gt;: &amp;quot;True&amp;quot;/&amp;quot;False&amp;quot;,&lt;br /&gt;
    	### &amp;lt;string&amp;gt;: &amp;quot;String&amp;quot;, &amp;lt;freq&amp;gt;: &amp;quot;&amp;lt;f&amp;gt; Hz/kHz/MHz&amp;quot;&lt;br /&gt;
    	### [arg]: arg optional&lt;br /&gt;
    	#Option		&amp;quot;NoAccel&amp;quot;				# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;SWcursor&amp;quot;				# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;ColorKey&amp;quot;				# &amp;lt;i&amp;gt;&lt;br /&gt;
    	#Option		&amp;quot;CacheLines&amp;quot;			# &amp;lt;i&amp;gt;&lt;br /&gt;
    	#Option		&amp;quot;Dac6Bit&amp;quot;				# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;DRI&amp;quot;					# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;NoDDC&amp;quot;					# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;ShowCache&amp;quot;				# [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    	#Option		&amp;quot;XvMCSurfaces&amp;quot;			# &amp;lt;i&amp;gt;&lt;br /&gt;
    	Identifier	&amp;quot;Card0&amp;quot;&lt;br /&gt;
    	Driver		&amp;quot;nvidia&amp;quot;&lt;br /&gt;
    	VendorName	&amp;quot;Unknown Vendor Name&amp;quot;&lt;br /&gt;
    	BoardName	&amp;quot;Unknown Board Name&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;LinearAlloc&amp;quot;		&amp;quot;16384&amp;quot;&lt;br /&gt;
    	#BusID		&amp;quot;PCI:0:2:0&amp;quot;&lt;br /&gt;
    #	Option		&amp;quot;NoDDC&amp;quot;				&amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;XvmcUsesTextures&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;renderAccel&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoDDCValue&amp;quot;&lt;br /&gt;
    	# Option &amp;quot;UseEDID&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEDID&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
            Option &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	## Option         &amp;quot;TripleBuffer&amp;quot; &amp;quot;True&amp;quot;&lt;br /&gt;
    	Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoLogo&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoBandWidthTest&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes,NoEdidModes&amp;quot;&lt;br /&gt;
    	## Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoVertRefreshCheck, NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes&amp;quot;&lt;br /&gt;
    &lt;br /&gt;
    	Option &amp;quot;DynamicTwinView&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEvents&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	## CJA Maybe remove ?&lt;br /&gt;
    	Option &amp;quot;AllowGLXWithComposite&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AddARGBGLXVisuals&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option		&amp;quot;ConnectedMonitor&amp;quot; &amp;quot;DFP&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Screen&amp;quot;&lt;br /&gt;
    	Identifier	&amp;quot;Screen0&amp;quot;&lt;br /&gt;
    	Device		&amp;quot;Card0&amp;quot;&lt;br /&gt;
    	Monitor		&amp;quot;Monitor0&amp;quot;&lt;br /&gt;
    	DefaultDepth	24&lt;br /&gt;
    	Option	    &amp;quot;FlatPanelProperties&amp;quot; &amp;quot;Scaling = Native&amp;quot; &lt;br /&gt;
    	Option	    &amp;quot;TwinView&amp;quot; &amp;quot;0&amp;quot; &lt;br /&gt;
    	SubSection &amp;quot;Display&amp;quot;&lt;br /&gt;
    		## Modes		&amp;quot;1920x1080_50i&amp;quot; &amp;quot;1920x1080_50i_0&amp;quot; &amp;quot;1920x1080_my50i&amp;quot;&lt;br /&gt;
    		## Virtual		1920 1080&lt;br /&gt;
    		Depth     24 &lt;br /&gt;
    &lt;br /&gt;
    		Modes &amp;quot;1920x1080@50&amp;quot; &amp;quot;1920x1080@60&amp;quot; &amp;quot;1920x1080@24&amp;quot; &amp;quot;1920x1080@23.976&amp;quot; &amp;quot;1920x1080@50i&amp;quot;&lt;br /&gt;
    		Modes &amp;quot;1920x1080@60i&amp;quot; &amp;quot;1920x1080@59.94&amp;quot; &amp;quot;1920x1080@59.94i&amp;quot;&lt;br /&gt;
    &lt;br /&gt;
    		## Modes &amp;quot;1920x1080@50i&amp;quot; &amp;quot;1920x1080@50&amp;quot; &amp;quot;1920x1080@60&amp;quot; &amp;quot;1920x1080@24&amp;quot; &amp;quot;1920x1080@23.976&amp;quot;&lt;br /&gt;
    		## Modes &amp;quot;1920x1080@60i&amp;quot; &amp;quot;1920x1080@59.94&amp;quot; &amp;quot;1920x1080@59.94i&amp;quot;&lt;br /&gt;
    		# Modes &amp;quot;1920x1080@25&amp;quot; &amp;quot;1920x1080@29.97&amp;quot; &amp;quot;1920x1080@30&amp;quot;&lt;br /&gt;
    	EndSubSection&lt;br /&gt;
    	Option &amp;quot;XvmcUsesTextures&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;renderAccel&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoDDCValue&amp;quot;&lt;br /&gt;
    	# Option &amp;quot;UseEDID&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEDID&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
            Option &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoLogo&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;NoBandWidthTest&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes,NoEdidModes&amp;quot;&lt;br /&gt;
    	## Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoVertRefreshCheck, NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes&amp;quot;&lt;br /&gt;
    	Option &amp;quot;DynamicTwinView&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;UseEvents&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	## CJA Maybe remove ?&lt;br /&gt;
    	Option &amp;quot;AllowGLXWithComposite&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AddARGBGLXVisuals&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;TVStandard&amp;quot;	&amp;quot;1080p (16:9)&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;AllowMouseOpenFail&amp;quot;	&amp;quot;true&amp;quot;&lt;br /&gt;
    	Option  &amp;quot;AutoAddDevices&amp;quot; 	&amp;quot;false&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;BlankTime&amp;quot;		&amp;quot;0&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;StandbyTime&amp;quot;	&amp;quot;0&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;SuspendTime&amp;quot;	&amp;quot;0&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;OffTime&amp;quot;		&amp;quot;0&amp;quot;&lt;br /&gt;
    	Option	&amp;quot;AIGLX&amp;quot;			&amp;quot;Off&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;Extensions&amp;quot;&lt;br /&gt;
    	Option &amp;quot;Composite&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    	Option &amp;quot;RENDER&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    	Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Sony_KDL-46W4500&amp;diff=31685</id>
		<title>Sony KDL-46W4500</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Sony_KDL-46W4500&amp;diff=31685"/>
		<updated>2012-07-09T17:26:00Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Hardware]]&lt;br /&gt;
{{Versioninfo}}&lt;br /&gt;
[[Category:Video]]&lt;br /&gt;
[[Category:Displays]]&lt;br /&gt;
&lt;br /&gt;
I am using an &#039;&#039;&#039;European&#039;&#039;&#039; version this TV and will try to describe problems I have here.&lt;br /&gt;
&lt;br /&gt;
Connected to a Nvidia 7300GT with an DVI to HDMI cable. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;NOTE that the 50 Hz modelines will probably not work if you try to connect to a non-HDMI port on the Sony TV (i.e. the PC input).  The Sony KDL-46WE5 (which is supposed to be very similar to this model) would not display 1920x1080 50Hz modelines when the PC was connected to the PC input on the TV.  This failure happened was using a VGA DB15 video cable attached to a DVI-DB15 converter - the graphics card in my PC has 2xDVI ports.  Once an DVI-HDMI converter and HDMI cable was used then the 50Hz modelines worked properly. The Sony manual has a single table for the graphics modes supported by the PC and HDMI inputs- this would lead you to believe that PC input and the HDMI inputs all support the same graphics modes but they don&#039;t. (Indulis&#039; experience)&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
I was not able to get the TV setup to 1080p with 50hz, so I chose 1080p and 60hz. Then afterwards I changed the xorg.conf and changed/added the folowing lines :&lt;br /&gt;
&lt;br /&gt;
 Option         &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
 Option         &amp;quot;UseEDID&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 Modes           &amp;quot;1920x1080_50_1&amp;quot; &amp;quot;1920x1080_50_0&amp;quot; &amp;quot;1920x1080_50&amp;quot; &amp;quot;1920x1080&amp;quot; &amp;quot;1920x1080_50i&amp;quot;&lt;br /&gt;
 VertRefresh     49-51&lt;br /&gt;
&lt;br /&gt;
and rebooted. After that I had 50hz.&lt;br /&gt;
&lt;br /&gt;
The line &amp;quot;1920x1080_50&amp;quot; uses the EDID information it gets of the TV and sets things up correctly. In the /var/log/Xorg.0.log you can then see that it chooses the right resolution.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot; is important, otherwise you will get very small unreadable characters.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Alternate solution (I used first).&lt;br /&gt;
&lt;br /&gt;
I was not able to get the TV setup to 1080p with 50hz, so I choosed 1080p and 60hz. Then afterwards I changed the xorg.conf to the right 1080p@50hz Modeline i found in the HDTV list in the MythTV modeline database.&lt;br /&gt;
&lt;br /&gt;
        # 1920x1080 @ 50 Hz (EDID) HSync: 56.25 kHz&lt;br /&gt;
        ModeLine &amp;quot;1920x1080&amp;quot; 148.50 1920 2448 2496 2640 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
&lt;br /&gt;
And changed the VertRefresh to :&lt;br /&gt;
        VertRefresh     49-51&lt;br /&gt;
&lt;br /&gt;
and rebooted. After that I had 50hz.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
My latest xorg.conf&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    Section &amp;quot;ServerLayout&amp;quot;&lt;br /&gt;
    		Identifier      &amp;quot;XFree86 Configured&amp;quot;&lt;br /&gt;
    		Screen    0     &amp;quot;Screen0&amp;quot;       0 0&lt;br /&gt;
    		InputDevice     &amp;quot;Mouse0&amp;quot;        &amp;quot;CorePointer&amp;quot;&lt;br /&gt;
    		InputDevice     &amp;quot;Keyboard0&amp;quot;     &amp;quot;CoreKeyboard&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Files&amp;quot;&lt;br /&gt;
    #       RgbPath         &amp;quot;/usr/X11R6/lib/X11/rgb&amp;quot;&lt;br /&gt;
    		ModulePath      &amp;quot;/usr/lib/xorg/modules&amp;quot;&lt;br /&gt;
    		FontPath        &amp;quot;/usr/share/fonts/X11&amp;quot;&lt;br /&gt;
    		FontPath        &amp;quot;/usr/X11R6/lib/X11/fonts/misc/&amp;quot;&lt;br /&gt;
    		FontPath        &amp;quot;/usr/X11R6/lib/X11/fonts/Speedo/&amp;quot;&lt;br /&gt;
    		FontPath        &amp;quot;/usr/X11R6/lib/X11/fonts/Type1/&amp;quot;&lt;br /&gt;
    		FontPath        &amp;quot;/usr/X11R6/lib/X11/fonts/CID/&amp;quot;&lt;br /&gt;
    		FontPath        &amp;quot;/usr/X11R6/lib/X11/fonts/75dpi/&amp;quot;&lt;br /&gt;
    		FontPath        &amp;quot;/usr/X11R6/lib/X11/fonts/100dpi/&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Module&amp;quot;&lt;br /&gt;
    		Load    &amp;quot;dbe&amp;quot;&lt;br /&gt;
    		Load    &amp;quot;extmod&amp;quot;&lt;br /&gt;
    		Load    &amp;quot;record&amp;quot;&lt;br /&gt;
    		Load    &amp;quot;xtrap&amp;quot;&lt;br /&gt;
    		Load    &amp;quot;speedo&amp;quot;&lt;br /&gt;
    		Load    &amp;quot;type1&amp;quot;&lt;br /&gt;
    		Load    &amp;quot;glx&amp;quot;&lt;br /&gt;
    		Load    &amp;quot;int10&amp;quot;&lt;br /&gt;
    		Load    &amp;quot;v4l&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;InputDevice&amp;quot;&lt;br /&gt;
    		Identifier      &amp;quot;Keyboard0&amp;quot;&lt;br /&gt;
    		Driver          &amp;quot;keyboard&amp;quot;&lt;br /&gt;
    		Option          &amp;quot;XkbLayout&amp;quot;             &amp;quot;us&amp;quot;&lt;br /&gt;
    		Option          &amp;quot;XkbVariant&amp;quot;    &amp;quot;basic&amp;quot;&lt;br /&gt;
    		Option          &amp;quot;XkbModel&amp;quot;              &amp;quot;pc105&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;InputDevice&amp;quot;&lt;br /&gt;
    		Identifier      &amp;quot;Mouse0&amp;quot;&lt;br /&gt;
    		Driver          &amp;quot;mouse&amp;quot;&lt;br /&gt;
    		Option          &amp;quot;Protocol&amp;quot;              &amp;quot;auto&amp;quot;&lt;br /&gt;
    		Option          &amp;quot;Device&amp;quot;                &amp;quot;/dev/input/mice&amp;quot;&lt;br /&gt;
    		Option          &amp;quot;ZAxisMapping&amp;quot;  &amp;quot;4 5&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Monitor&amp;quot;&lt;br /&gt;
    		Identifier      &amp;quot;Monitor0&amp;quot;&lt;br /&gt;
    		VendorName      &amp;quot;Sony&amp;quot;&lt;br /&gt;
    		ModelName       &amp;quot;46&amp;quot;&lt;br /&gt;
    &lt;br /&gt;
    		# 1920x1080p @ 50Hz (EIA/CEA-861B)&lt;br /&gt;
    		# ModeLine &amp;quot;1920x1080@50&amp;quot; 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync&lt;br /&gt;
    		# 1920x1080p @ 60Hz (EIA/CEA-861B)&lt;br /&gt;
    		ModeLine &amp;quot;1920x1080@60&amp;quot; 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync&lt;br /&gt;
    		# 1920x1080p @ 24Hz (EIA/CEA-861B)&lt;br /&gt;
    		ModeLine &amp;quot;1920x1080@24&amp;quot; 74.250 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync&lt;br /&gt;
    		# 1920x1080p @ 23.976Hz (EIA/CEA-861B)&lt;br /&gt;
    		ModeLine &amp;quot;1920x1080@23.976&amp;quot; 74.175 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync&lt;br /&gt;
    		# 1920x1080i @ 50Hz (EIA/CEA-861B)&lt;br /&gt;
    		Modeline &amp;quot;1920x1080@50i&amp;quot; 74.250 1920 2448 2492 2640 1080 1085 1095 1125 +hsync +vsync Interlace&lt;br /&gt;
    		# 1920x1080i @ 60Hz (EIA/CEA-861B)&lt;br /&gt;
    		Modeline &amp;quot;1920x1080@60i&amp;quot; 74.250 1920 2008 2052 2200 1080 1085 1095 1125 +hsync +vsync interlace&lt;br /&gt;
    		# 1920x1080p @ 59.94Hz (EIA/CEA-861B)&lt;br /&gt;
    		ModeLine &amp;quot;1920x1080@59.94&amp;quot; 148.350 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync&lt;br /&gt;
    		# 1920x1080i @ 59.94Hz (EIA/CEA-861B)&lt;br /&gt;
    		Modeline &amp;quot;1920x1080@59.94i&amp;quot; 74.175 1920 2008 2052 2200 1080 1085 1095 1125 +hsync +vsync Interlace&lt;br /&gt;
    		# 1920x1080p @ 25Hz (EIA/CEA-861B)&lt;br /&gt;
    		ModeLine &amp;quot;1920x1080@25&amp;quot; 74.250 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync&lt;br /&gt;
    		# 1920x1080p @ 29.97Hz (EIA/CEA-861B)&lt;br /&gt;
    		ModeLine &amp;quot;1920x1080@29.97&amp;quot; 74.175 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync&lt;br /&gt;
    		# 1920x1080p @ 30Hz (EIA/CEA-861B)&lt;br /&gt;
    		ModeLine &amp;quot;1920x1080@30&amp;quot; 74.250 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync&lt;br /&gt;
    		HorizSync       20.0 - 150.0&lt;br /&gt;
    		VertRefresh     23.0 - 90.0&lt;br /&gt;
    		Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;True&amp;quot;&lt;br /&gt;
    		Option &amp;quot;UseEDIDFreqs&amp;quot; &amp;quot;FALSE&amp;quot;&lt;br /&gt;
    		Option &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;FALSE&amp;quot;&lt;br /&gt;
    		#!# Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoEdidModes&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Device&amp;quot;&lt;br /&gt;
    		### Available Driver options are:-&lt;br /&gt;
    		### Values: &amp;lt;i&amp;gt;: integer, &amp;lt;f&amp;gt;: float, &amp;lt;bool&amp;gt;: &amp;quot;True&amp;quot;/&amp;quot;False&amp;quot;,&lt;br /&gt;
    		### &amp;lt;string&amp;gt;: &amp;quot;String&amp;quot;, &amp;lt;freq&amp;gt;: &amp;quot;&amp;lt;f&amp;gt; Hz/kHz/MHz&amp;quot;&lt;br /&gt;
    		### [arg]: arg optional&lt;br /&gt;
    		#Option         &amp;quot;NoAccel&amp;quot;                               # [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    		#Option         &amp;quot;SWcursor&amp;quot;                              # [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    		#Option         &amp;quot;ColorKey&amp;quot;                              # &amp;lt;i&amp;gt;&lt;br /&gt;
    		#Option         &amp;quot;CacheLines&amp;quot;                    # &amp;lt;i&amp;gt;&lt;br /&gt;
    		#Option         &amp;quot;Dac6Bit&amp;quot;                               # [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    		#Option         &amp;quot;DRI&amp;quot;                                   # [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    		#Option         &amp;quot;NoDDC&amp;quot;                                 # [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    		#Option         &amp;quot;ShowCache&amp;quot;                             # [&amp;lt;bool&amp;gt;]&lt;br /&gt;
    		#Option         &amp;quot;XvMCSurfaces&amp;quot;                  # &amp;lt;i&amp;gt;&lt;br /&gt;
    		Identifier      &amp;quot;Card0&amp;quot;&lt;br /&gt;
    		Driver          &amp;quot;nvidia&amp;quot;&lt;br /&gt;
    		VendorName      &amp;quot;Unknown Vendor Name&amp;quot;&lt;br /&gt;
    		BoardName       &amp;quot;Unknown Board Name&amp;quot;&lt;br /&gt;
    		Option          &amp;quot;LinearAlloc&amp;quot;           &amp;quot;16384&amp;quot;&lt;br /&gt;
    		#BusID          &amp;quot;PCI:0:2:0&amp;quot;&lt;br /&gt;
    #       Option          &amp;quot;NoDDC&amp;quot;                         &amp;quot;true&amp;quot;&lt;br /&gt;
    		Option &amp;quot;XvmcUsesTextures&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    		Option &amp;quot;renderAccel&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    		Option &amp;quot;NoDDCValue&amp;quot;&lt;br /&gt;
    		# Option &amp;quot;UseEDID&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    		Option &amp;quot;UseEDID&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    		Option &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    		## Option         &amp;quot;TripleBuffer&amp;quot; &amp;quot;True&amp;quot;&lt;br /&gt;
    		Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    		Option &amp;quot;NoLogo&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    		Option &amp;quot;NoBandWidthTest&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    		Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes,NoEdidModes&amp;quot;&lt;br /&gt;
    		## Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoVertRefreshCheck, NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes&amp;quot;&lt;br /&gt;
    &lt;br /&gt;
    		Option &amp;quot;DynamicTwinView&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    		Option &amp;quot;UseEvents&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    		## CJA Maybe remove ?&lt;br /&gt;
    		Option &amp;quot;AllowGLXWithComposite&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    		Option &amp;quot;AddARGBGLXVisuals&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    		Option          &amp;quot;ConnectedMonitor&amp;quot; &amp;quot;DFP&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;Screen&amp;quot;&lt;br /&gt;
    		Identifier      &amp;quot;Screen0&amp;quot;&lt;br /&gt;
    		Device          &amp;quot;Card0&amp;quot;&lt;br /&gt;
    		Monitor         &amp;quot;Monitor0&amp;quot;&lt;br /&gt;
    		DefaultDepth    24&lt;br /&gt;
    		Option      &amp;quot;FlatPanelProperties&amp;quot; &amp;quot;Scaling = Native&amp;quot;&lt;br /&gt;
    		Option      &amp;quot;TwinView&amp;quot; &amp;quot;0&amp;quot;&lt;br /&gt;
    		SubSection &amp;quot;Display&amp;quot;&lt;br /&gt;
    				## Modes                &amp;quot;1920x1080_50i&amp;quot; &amp;quot;1920x1080_50i_0&amp;quot; &amp;quot;1920x1080_my50i&amp;quot;&lt;br /&gt;
    				## Virtual              1920 1080&lt;br /&gt;
    				Depth     24&lt;br /&gt;
    				Modes &amp;quot;1920x1080@50i&amp;quot; &amp;quot;1920x1080@50&amp;quot; &amp;quot;1920x1080@60&amp;quot; &amp;quot;1920x1080@24&amp;quot; &amp;quot;1920x1080@23.976&amp;quot;&lt;br /&gt;
    				Modes &amp;quot;1920x1080@60i&amp;quot; &amp;quot;1920x1080@59.94&amp;quot; &amp;quot;1920x1080@59.94i&amp;quot;&lt;br /&gt;
    				Modes &amp;quot;1920x1080@25&amp;quot; &amp;quot;1920x1080@29.97&amp;quot; &amp;quot;1920x1080@30&amp;quot;&lt;br /&gt;
    		EndSubSection&lt;br /&gt;
    		Option &amp;quot;XvmcUsesTextures&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    		Option &amp;quot;renderAccel&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    		Option &amp;quot;NoDDCValue&amp;quot;&lt;br /&gt;
    		# Option &amp;quot;UseEDID&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    		Option &amp;quot;UseEDID&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    		Option &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    		Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    		Option &amp;quot;NoLogo&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    		Option &amp;quot;NoBandWidthTest&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    		Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes,NoEdidModes&amp;quot;&lt;br /&gt;
    		## Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoVertRefreshCheck, NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes&amp;quot;&lt;br /&gt;
    		Option &amp;quot;DynamicTwinView&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    		Option &amp;quot;UseEvents&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    		## CJA Maybe remove ?&lt;br /&gt;
    		Option &amp;quot;AllowGLXWithComposite&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    		Option &amp;quot;AddARGBGLXVisuals&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    		Option  &amp;quot;TVStandard&amp;quot;    &amp;quot;1080p (16:9)&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    &lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    		Option  &amp;quot;AllowMouseOpenFail&amp;quot;    &amp;quot;true&amp;quot;&lt;br /&gt;
    		Option  &amp;quot;AutoAddDevices&amp;quot;        &amp;quot;false&amp;quot;&lt;br /&gt;
    		Option  &amp;quot;BlankTime&amp;quot;             &amp;quot;0&amp;quot;&lt;br /&gt;
    		Option  &amp;quot;StandbyTime&amp;quot;   &amp;quot;0&amp;quot;&lt;br /&gt;
    		Option  &amp;quot;SuspendTime&amp;quot;   &amp;quot;0&amp;quot;&lt;br /&gt;
    		Option  &amp;quot;OffTime&amp;quot;               &amp;quot;0&amp;quot;&lt;br /&gt;
    		Option  &amp;quot;AIGLX&amp;quot;                 &amp;quot;Off&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    		Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    		Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    		Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    		Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;Extensions&amp;quot;&lt;br /&gt;
    		Option &amp;quot;Composite&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
    		Option &amp;quot;RENDER&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
    EndSection&lt;br /&gt;
    Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
    		Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
    EndSection&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Sony_KDL-46W4500&amp;diff=31684</id>
		<title>Sony KDL-46W4500</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Sony_KDL-46W4500&amp;diff=31684"/>
		<updated>2012-07-09T17:05:59Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Hardware]]&lt;br /&gt;
{{Versioninfo}}&lt;br /&gt;
[[Category:Video]]&lt;br /&gt;
[[Category:Displays]]&lt;br /&gt;
&lt;br /&gt;
I am using an &#039;&#039;&#039;European&#039;&#039;&#039; version this TV and will try to describe problems I have here.&lt;br /&gt;
&lt;br /&gt;
Connected to a Nvidia 7300GT with an DVI to HDMI cable. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;NOTE that the 50 Hz modelines will probably not work if you try to connect to a non-HDMI port on the Sony TV (i.e. the PC input).  The Sony KDL-46WE5 (which is supposed to be very similar to this model) would not display 1920x1080 50Hz modelines when the PC was connected to the PC input on the TV.  This failure happened was using a VGA DB15 video cable attached to a DVI-DB15 converter - the graphics card in my PC has 2xDVI ports.  Once an DVI-HDMI converter and HDMI cable was used then the 50Hz modelines worked properly. The Sony manual has a single table for the graphics modes supported by the PC and HDMI inputs- this would lead you to believe that PC input and the HDMI inputs all support the same graphics modes but they don&#039;t. (Indulis&#039; experience)&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
I was not able to get the TV setup to 1080p with 50hz, so I chose 1080p and 60hz. Then afterwards I changed the xorg.conf and changed/added the folowing lines :&lt;br /&gt;
&lt;br /&gt;
 Option         &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
 Option         &amp;quot;UseEDID&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 Modes           &amp;quot;1920x1080_50_1&amp;quot; &amp;quot;1920x1080_50_0&amp;quot; &amp;quot;1920x1080_50&amp;quot; &amp;quot;1920x1080&amp;quot; &amp;quot;1920x1080_50i&amp;quot;&lt;br /&gt;
 VertRefresh     49-51&lt;br /&gt;
&lt;br /&gt;
and rebooted. After that I had 50hz.&lt;br /&gt;
&lt;br /&gt;
The line &amp;quot;1920x1080_50&amp;quot; uses the EDID information it gets of the TV and sets things up correctly. In the /var/log/Xorg.0.log you can then see that it chooses the right resolution.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot; is important, otherwise you will get very small unreadable characters.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Alternate solution (I used first).&lt;br /&gt;
&lt;br /&gt;
I was not able to get the TV setup to 1080p with 50hz, so I choosed 1080p and 60hz. Then afterwards I changed the xorg.conf to the right 1080p@50hz Modeline i found in the HDTV list in the MythTV modeline database.&lt;br /&gt;
&lt;br /&gt;
        # 1920x1080 @ 50 Hz (EDID) HSync: 56.25 kHz&lt;br /&gt;
        ModeLine &amp;quot;1920x1080&amp;quot; 148.50 1920 2448 2496 2640 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
&lt;br /&gt;
And changed the VertRefresh to :&lt;br /&gt;
        VertRefresh     49-51&lt;br /&gt;
&lt;br /&gt;
and rebooted. After that I had 50hz.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
My latest xorg.conf&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Section &amp;quot;ServerLayout&amp;quot;&lt;br /&gt;
        Identifier      &amp;quot;XFree86 Configured&amp;quot;&lt;br /&gt;
        Screen    0     &amp;quot;Screen0&amp;quot;       0 0&lt;br /&gt;
        InputDevice     &amp;quot;Mouse0&amp;quot;        &amp;quot;CorePointer&amp;quot;&lt;br /&gt;
        InputDevice     &amp;quot;Keyboard0&amp;quot;     &amp;quot;CoreKeyboard&amp;quot;&lt;br /&gt;
EndSection&lt;br /&gt;
&lt;br /&gt;
Section &amp;quot;Files&amp;quot;&lt;br /&gt;
#       RgbPath         &amp;quot;/usr/X11R6/lib/X11/rgb&amp;quot;&lt;br /&gt;
        ModulePath      &amp;quot;/usr/lib/xorg/modules&amp;quot;&lt;br /&gt;
        FontPath        &amp;quot;/usr/share/fonts/X11&amp;quot;&lt;br /&gt;
        FontPath        &amp;quot;/usr/X11R6/lib/X11/fonts/misc/&amp;quot;&lt;br /&gt;
        FontPath        &amp;quot;/usr/X11R6/lib/X11/fonts/Speedo/&amp;quot;&lt;br /&gt;
        FontPath        &amp;quot;/usr/X11R6/lib/X11/fonts/Type1/&amp;quot;&lt;br /&gt;
        FontPath        &amp;quot;/usr/X11R6/lib/X11/fonts/CID/&amp;quot;&lt;br /&gt;
        FontPath        &amp;quot;/usr/X11R6/lib/X11/fonts/75dpi/&amp;quot;&lt;br /&gt;
        FontPath        &amp;quot;/usr/X11R6/lib/X11/fonts/100dpi/&amp;quot;&lt;br /&gt;
EndSection&lt;br /&gt;
&lt;br /&gt;
Section &amp;quot;Module&amp;quot;&lt;br /&gt;
        Load    &amp;quot;dbe&amp;quot;&lt;br /&gt;
        Load    &amp;quot;extmod&amp;quot;&lt;br /&gt;
        Load    &amp;quot;record&amp;quot;&lt;br /&gt;
        Load    &amp;quot;xtrap&amp;quot;&lt;br /&gt;
        Load    &amp;quot;speedo&amp;quot;&lt;br /&gt;
        Load    &amp;quot;type1&amp;quot;&lt;br /&gt;
        Load    &amp;quot;glx&amp;quot;&lt;br /&gt;
        Load    &amp;quot;int10&amp;quot;&lt;br /&gt;
        Load    &amp;quot;v4l&amp;quot;&lt;br /&gt;
EndSection&lt;br /&gt;
&lt;br /&gt;
Section &amp;quot;InputDevice&amp;quot;&lt;br /&gt;
        Identifier      &amp;quot;Keyboard0&amp;quot;&lt;br /&gt;
        Driver          &amp;quot;keyboard&amp;quot;&lt;br /&gt;
        Option          &amp;quot;XkbLayout&amp;quot;             &amp;quot;us&amp;quot;&lt;br /&gt;
        Option          &amp;quot;XkbVariant&amp;quot;    &amp;quot;basic&amp;quot;&lt;br /&gt;
        Option          &amp;quot;XkbModel&amp;quot;              &amp;quot;pc105&amp;quot;&lt;br /&gt;
EndSection&lt;br /&gt;
&lt;br /&gt;
Section &amp;quot;InputDevice&amp;quot;&lt;br /&gt;
        Identifier      &amp;quot;Mouse0&amp;quot;&lt;br /&gt;
        Driver          &amp;quot;mouse&amp;quot;&lt;br /&gt;
        Option          &amp;quot;Protocol&amp;quot;              &amp;quot;auto&amp;quot;&lt;br /&gt;
        Option          &amp;quot;Device&amp;quot;                &amp;quot;/dev/input/mice&amp;quot;&lt;br /&gt;
        Option          &amp;quot;ZAxisMapping&amp;quot;  &amp;quot;4 5&amp;quot;&lt;br /&gt;
EndSection&lt;br /&gt;
&lt;br /&gt;
Section &amp;quot;Monitor&amp;quot;&lt;br /&gt;
        Identifier      &amp;quot;Monitor0&amp;quot;&lt;br /&gt;
        VendorName      &amp;quot;Sony&amp;quot;&lt;br /&gt;
        ModelName       &amp;quot;46&amp;quot;&lt;br /&gt;
&lt;br /&gt;
        # 1920x1080p @ 50Hz (EIA/CEA-861B)&lt;br /&gt;
        # ModeLine &amp;quot;1920x1080@50&amp;quot; 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync&lt;br /&gt;
        # 1920x1080p @ 60Hz (EIA/CEA-861B)&lt;br /&gt;
        ModeLine &amp;quot;1920x1080@60&amp;quot; 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync&lt;br /&gt;
        # 1920x1080p @ 24Hz (EIA/CEA-861B)&lt;br /&gt;
        ModeLine &amp;quot;1920x1080@24&amp;quot; 74.250 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync&lt;br /&gt;
        # 1920x1080p @ 23.976Hz (EIA/CEA-861B)&lt;br /&gt;
        ModeLine &amp;quot;1920x1080@23.976&amp;quot; 74.175 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync&lt;br /&gt;
        # 1920x1080i @ 50Hz (EIA/CEA-861B)&lt;br /&gt;
        Modeline &amp;quot;1920x1080@50i&amp;quot; 74.250 1920 2448 2492 2640 1080 1085 1095 1125 +hsync +vsync Interlace&lt;br /&gt;
        # 1920x1080i @ 60Hz (EIA/CEA-861B)&lt;br /&gt;
        Modeline &amp;quot;1920x1080@60i&amp;quot; 74.250 1920 2008 2052 2200 1080 1085 1095 1125 +hsync +vsync interlace&lt;br /&gt;
        # 1920x1080p @ 59.94Hz (EIA/CEA-861B)&lt;br /&gt;
        ModeLine &amp;quot;1920x1080@59.94&amp;quot; 148.350 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync&lt;br /&gt;
        # 1920x1080i @ 59.94Hz (EIA/CEA-861B)&lt;br /&gt;
        Modeline &amp;quot;1920x1080@59.94i&amp;quot; 74.175 1920 2008 2052 2200 1080 1085 1095 1125 +hsync +vsync Interlace&lt;br /&gt;
        # 1920x1080p @ 25Hz (EIA/CEA-861B)&lt;br /&gt;
        ModeLine &amp;quot;1920x1080@25&amp;quot; 74.250 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync&lt;br /&gt;
        # 1920x1080p @ 29.97Hz (EIA/CEA-861B)&lt;br /&gt;
        ModeLine &amp;quot;1920x1080@29.97&amp;quot; 74.175 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync&lt;br /&gt;
        # 1920x1080p @ 30Hz (EIA/CEA-861B)&lt;br /&gt;
        ModeLine &amp;quot;1920x1080@30&amp;quot; 74.250 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync&lt;br /&gt;
        HorizSync       20.0 - 150.0&lt;br /&gt;
        VertRefresh     23.0 - 90.0&lt;br /&gt;
        Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;True&amp;quot;&lt;br /&gt;
        Option &amp;quot;UseEDIDFreqs&amp;quot; &amp;quot;FALSE&amp;quot;&lt;br /&gt;
        Option &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;FALSE&amp;quot;&lt;br /&gt;
        #!# Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoEdidModes&amp;quot;&lt;br /&gt;
EndSection&lt;br /&gt;
&lt;br /&gt;
Section &amp;quot;Device&amp;quot;&lt;br /&gt;
        ### Available Driver options are:-&lt;br /&gt;
        ### Values: &amp;lt;i&amp;gt;: integer, &amp;lt;f&amp;gt;: float, &amp;lt;bool&amp;gt;: &amp;quot;True&amp;quot;/&amp;quot;False&amp;quot;,&lt;br /&gt;
        ### &amp;lt;string&amp;gt;: &amp;quot;String&amp;quot;, &amp;lt;freq&amp;gt;: &amp;quot;&amp;lt;f&amp;gt; Hz/kHz/MHz&amp;quot;&lt;br /&gt;
        ### [arg]: arg optional&lt;br /&gt;
        #Option         &amp;quot;NoAccel&amp;quot;                               # [&amp;lt;bool&amp;gt;]&lt;br /&gt;
        #Option         &amp;quot;SWcursor&amp;quot;                              # [&amp;lt;bool&amp;gt;]&lt;br /&gt;
        #Option         &amp;quot;ColorKey&amp;quot;                              # &amp;lt;i&amp;gt;&lt;br /&gt;
        #Option         &amp;quot;CacheLines&amp;quot;                    # &amp;lt;i&amp;gt;&lt;br /&gt;
        #Option         &amp;quot;Dac6Bit&amp;quot;                               # [&amp;lt;bool&amp;gt;]&lt;br /&gt;
        #Option         &amp;quot;DRI&amp;quot;                                   # [&amp;lt;bool&amp;gt;]&lt;br /&gt;
        #Option         &amp;quot;NoDDC&amp;quot;                                 # [&amp;lt;bool&amp;gt;]&lt;br /&gt;
        #Option         &amp;quot;ShowCache&amp;quot;                             # [&amp;lt;bool&amp;gt;]&lt;br /&gt;
        #Option         &amp;quot;XvMCSurfaces&amp;quot;                  # &amp;lt;i&amp;gt;&lt;br /&gt;
        Identifier      &amp;quot;Card0&amp;quot;&lt;br /&gt;
        Driver          &amp;quot;nvidia&amp;quot;&lt;br /&gt;
        VendorName      &amp;quot;Unknown Vendor Name&amp;quot;&lt;br /&gt;
        BoardName       &amp;quot;Unknown Board Name&amp;quot;&lt;br /&gt;
        Option          &amp;quot;LinearAlloc&amp;quot;           &amp;quot;16384&amp;quot;&lt;br /&gt;
        #BusID          &amp;quot;PCI:0:2:0&amp;quot;&lt;br /&gt;
#       Option          &amp;quot;NoDDC&amp;quot;                         &amp;quot;true&amp;quot;&lt;br /&gt;
        Option &amp;quot;XvmcUsesTextures&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        Option &amp;quot;renderAccel&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        Option &amp;quot;NoDDCValue&amp;quot;&lt;br /&gt;
        # Option &amp;quot;UseEDID&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
        Option &amp;quot;UseEDID&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        Option &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
        ## Option         &amp;quot;TripleBuffer&amp;quot; &amp;quot;True&amp;quot;&lt;br /&gt;
        Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        Option &amp;quot;NoLogo&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        Option &amp;quot;NoBandWidthTest&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes,NoEdidModes&amp;quot;&lt;br /&gt;
        ## Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoVertRefreshCheck, NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes&amp;quot;&lt;br /&gt;
&lt;br /&gt;
        Option &amp;quot;DynamicTwinView&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
        Option &amp;quot;UseEvents&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        ## CJA Maybe remove ?&lt;br /&gt;
        Option &amp;quot;AllowGLXWithComposite&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        Option &amp;quot;AddARGBGLXVisuals&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        Option          &amp;quot;ConnectedMonitor&amp;quot; &amp;quot;DFP&amp;quot;&lt;br /&gt;
EndSection&lt;br /&gt;
&lt;br /&gt;
Section &amp;quot;Screen&amp;quot;&lt;br /&gt;
        Identifier      &amp;quot;Screen0&amp;quot;&lt;br /&gt;
        Device          &amp;quot;Card0&amp;quot;&lt;br /&gt;
        Monitor         &amp;quot;Monitor0&amp;quot;&lt;br /&gt;
        DefaultDepth    24&lt;br /&gt;
        Option      &amp;quot;FlatPanelProperties&amp;quot; &amp;quot;Scaling = Native&amp;quot;&lt;br /&gt;
        Option      &amp;quot;TwinView&amp;quot; &amp;quot;0&amp;quot;&lt;br /&gt;
        SubSection &amp;quot;Display&amp;quot;&lt;br /&gt;
                ## Modes                &amp;quot;1920x1080_50i&amp;quot; &amp;quot;1920x1080_50i_0&amp;quot; &amp;quot;1920x1080_my50i&amp;quot;&lt;br /&gt;
                ## Virtual              1920 1080&lt;br /&gt;
                Depth     24&lt;br /&gt;
                Modes &amp;quot;1920x1080@50i&amp;quot; &amp;quot;1920x1080@50&amp;quot; &amp;quot;1920x1080@60&amp;quot; &amp;quot;1920x1080@24&amp;quot; &amp;quot;1920x1080@23.976&amp;quot;&lt;br /&gt;
                Modes &amp;quot;1920x1080@60i&amp;quot; &amp;quot;1920x1080@59.94&amp;quot; &amp;quot;1920x1080@59.94i&amp;quot;&lt;br /&gt;
                Modes &amp;quot;1920x1080@25&amp;quot; &amp;quot;1920x1080@29.97&amp;quot; &amp;quot;1920x1080@30&amp;quot;&lt;br /&gt;
        EndSubSection&lt;br /&gt;
        Option &amp;quot;XvmcUsesTextures&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        Option &amp;quot;renderAccel&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        Option &amp;quot;NoDDCValue&amp;quot;&lt;br /&gt;
        # Option &amp;quot;UseEDID&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
        Option &amp;quot;UseEDID&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        Option &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
        Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        Option &amp;quot;NoLogo&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        Option &amp;quot;NoBandWidthTest&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes,NoEdidModes&amp;quot;&lt;br /&gt;
        ## Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoVertRefreshCheck, NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes&amp;quot;&lt;br /&gt;
        Option &amp;quot;DynamicTwinView&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
        Option &amp;quot;UseEvents&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        ## CJA Maybe remove ?&lt;br /&gt;
        Option &amp;quot;AllowGLXWithComposite&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        Option &amp;quot;AddARGBGLXVisuals&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        Option  &amp;quot;TVStandard&amp;quot;    &amp;quot;1080p (16:9)&amp;quot;&lt;br /&gt;
EndSection&lt;br /&gt;
&lt;br /&gt;
Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
        Option  &amp;quot;AllowMouseOpenFail&amp;quot;    &amp;quot;true&amp;quot;&lt;br /&gt;
        Option  &amp;quot;AutoAddDevices&amp;quot;        &amp;quot;false&amp;quot;&lt;br /&gt;
        Option  &amp;quot;BlankTime&amp;quot;             &amp;quot;0&amp;quot;&lt;br /&gt;
        Option  &amp;quot;StandbyTime&amp;quot;   &amp;quot;0&amp;quot;&lt;br /&gt;
        Option  &amp;quot;SuspendTime&amp;quot;   &amp;quot;0&amp;quot;&lt;br /&gt;
        Option  &amp;quot;OffTime&amp;quot;               &amp;quot;0&amp;quot;&lt;br /&gt;
        Option  &amp;quot;AIGLX&amp;quot;                 &amp;quot;Off&amp;quot;&lt;br /&gt;
EndSection&lt;br /&gt;
Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
        Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
EndSection&lt;br /&gt;
Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
        Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
EndSection&lt;br /&gt;
Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
        Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
EndSection&lt;br /&gt;
Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
        Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
EndSection&lt;br /&gt;
Section &amp;quot;Extensions&amp;quot;&lt;br /&gt;
        Option &amp;quot;Composite&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
        Option &amp;quot;RENDER&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
EndSection&lt;br /&gt;
Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
        Option &amp;quot;AutoAddDevices&amp;quot; &amp;quot;False&amp;quot;&lt;br /&gt;
EndSection&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Web_Orbiter_2.0&amp;diff=24960</id>
		<title>Web Orbiter 2.0</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Web_Orbiter_2.0&amp;diff=24960"/>
		<updated>2010-08-31T06:43:33Z</updated>

		<summary type="html">&lt;p&gt;Viking: /* HTC Desire (Android 2.1) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{versioninfo|810Status=Relevant|810UpdatedDate=23rd July 2010|810UpdatedBy=Purps}}&lt;br /&gt;
{| align=&amp;quot;right&amp;quot;&lt;br /&gt;
  | __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
[[Category: Orbiters]]&lt;br /&gt;
[[Category: Tutorials]]&lt;br /&gt;
&lt;br /&gt;
A Web Orbiter is any device (such as a iPhone, iPod Touch, iPad, laptop, PC, etc.) that accesses the Orbiter user interface (UI) through a Web browser.&lt;br /&gt;
&lt;br /&gt;
The new Web Orbiter 2.0 has been re-written from the ground up to make sure it has a much smoother performance overall but especially on slower lower powered devices and devices that are connected over slow LAN connections or even slower external connections...such as a Mobile 3G network or slow WiFi connection.&lt;br /&gt;
&lt;br /&gt;
So what has changed? Well visually your Orbiter UI will look like it does on your existing standard Orbiters but you will notice that unlike the original Web Orbiter the new 2.0 version does not refresh every 5 secs. The new Web Orbiter now only updates if something changes in the system and that requires the UI screen you are currently viewing to be updated or if you click on a UI button or other UI element and that causes a screen update. &lt;br /&gt;
&lt;br /&gt;
To achieve this the proxy_orbiter has been updated so that it sets a flag called &#039;ANYNEWS&#039; to &#039;true&#039; if some element of the current displayed screen has been updated. The Web Orbiter makes a light weight call to query the state of this flag once every second and only gets an updated UI screen if the flag is set to &#039;true&#039; otherwise no screen update is requested. So in use the new Web Orbiter 2.0 behaves in a very similar fashion to the Orbiter on one of your MD&#039;s - and now it even performs with a similar performance level too.&lt;br /&gt;
&lt;br /&gt;
Whats a proxy_orbiter? Proxy_orbiter runs on the Core and its job is to render the UI for the Web Orbiter that is running remotely on some other device. Each Web Orbiter has an associated proxy_orbiter and the two work in partnership. Proxy_orbiters do all the &#039;heavy lifting&#039; rendering the UI and this allows the remote device that is running the Web Orbiter to be much less powerful and very simple devices indeed if needed.&lt;br /&gt;
&lt;br /&gt;
Another change in the new 2.0 Web Orbiter is that screen refreshes are double buffered so that the new Web Orbiter receives the new screen update from your Core in the background and only redraws the screen when it has the complete image stored in memory - this makes the update process smoother and faster.&lt;br /&gt;
&lt;br /&gt;
The overall effect of all these changes is to vastly improve the performance and usability while at the same time reducing the processing overhead of the Web Orbiter massively.&lt;br /&gt;
&lt;br /&gt;
== Setup ==&lt;br /&gt;
The procedure to setup a Web Orbiter is simple but the order of steps is important.&lt;br /&gt;
#First of all, add a new Generic Web Device as a Child Device for your Core:&lt;br /&gt;
##Goto the LinuxMCE Admin website--&amp;gt;Show devices tree--&amp;gt;CORE. The CORE&#039;s detail page should appear.&lt;br /&gt;
##Click &#039;Create Child Device&#039;.&lt;br /&gt;
##In the Description, enter the name of the specific web orbiter.&lt;br /&gt;
##In the Add child device window, click the button &#039;Pick device template&#039;. The new pop-up window containing device templates will be opened.&lt;br /&gt;
##In the &#039;Device Category&#039; dropdown list, choose &#039;Peripherals&#039;.&lt;br /&gt;
##In the &#039;Device Template&#039; dropdown list, find and select &amp;quot;Generic Web Device&amp;quot; (or just type the template id: 1748 and press go).&lt;br /&gt;
##Click the button &#039;Pick Device Template&#039;. 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.&lt;br /&gt;
##A new Generic Proxy Orbiter will also be created automatically. Watch the Orbiter generation process on the Orbiters page: Wizard--&amp;gt;Devices--&amp;gt;Orbiters.&lt;br /&gt;
#Wait till the Orbiter generation procedure finishes. A message on an active Orbiter or on the Orbiter page will indicate when it has completed.&lt;br /&gt;
#Set the appropriate screen resolution to suit the device your Web Orbiter is intended for from the &#039;Size&#039; drop down&lt;br /&gt;
#Set the &#039;Skin&#039; drop down to the skin you want to use (normally this would mean the UI1 Standard Variation or a derivative)&lt;br /&gt;
#Click on your new Generic Proxy Orbiter in the device tree, give it a unique name and then scroll to the bottom of the page on the right and look for the field called &#039;Listen Port&#039;. This field will be set to &#039;3461&#039; by default (if this Web Orbiter is not your first then you should increment this value by one ie to &#039;3462&#039; - each Web Orbiter must have a unique &#039;Listen Port&#039; number)&lt;br /&gt;
#Now click the &#039;Save&#039; button at the bottom of the screen to save the changes you have made.&lt;br /&gt;
#Now do a &#039;Full Regen&#039; from the &#039;Wizard - Orbiters&#039; page (use the &#039;Full Regen&#039; for the specific Web Orbiter you have created and not the overall &#039;Full Regen&#039; button at the top of the page). Next when the Regen has completed do a &amp;quot;[[Quick reload router]]&amp;quot;. Otherwise, the Web Orbiter won&#039;t work properly.&lt;br /&gt;
&lt;br /&gt;
==Device Screen Resolutions==&lt;br /&gt;
If the &#039;Device&#039; your planning to use your Web Orbiter on is a Desktop or Laptop then use the biggest resolution that will comfortably fit onto your screen. If your device is a touch screen device like an iPad, iPhone or iPod Touch then choose a resoltion that matches the overall resolution of the devices display;&lt;br /&gt;
&lt;br /&gt;
===iPad===&lt;br /&gt;
The iPad has a screen resolution of 1024x768 so if your creating an Orbiter for the iPad this is the resolution you should select for this Web Orbiter.&lt;br /&gt;
&lt;br /&gt;
===iPhone (pre iPhone 4) or iPad Touch===&lt;br /&gt;
The iPhone/iPod Touch have a screen resolution of 480x320 so if your creating an Orbiter for either of these this is the resolution you should select for this Web Orbiter.&lt;br /&gt;
&lt;br /&gt;
===iPhone 4===&lt;br /&gt;
The iPhone 4 has a screen resolution of 960x640 so if your creating an Orbiter for the iPhone 4 this is the resolution you should select for this Web Orbiter.&lt;br /&gt;
&lt;br /&gt;
===Google Nexus One or HTC Desire (Android)===&lt;br /&gt;
If you have a Nexus One you will need to select a resolution of 480x800 (select N770 in the web admin, it is 480x800) so if your creating an Orbiter for the Nexus One this is the resolution you should select for this Web Orbiter.&lt;br /&gt;
&lt;br /&gt;
On the HTC Desire you might also have to go into the web browser settings and change the default zoom to &amp;quot;far away&amp;quot; (mine is danish, so don&#039;t know the exact english decription). After that it should be full screen.&lt;br /&gt;
&lt;br /&gt;
===Nokia 5800 XpressMusic===&lt;br /&gt;
For a fullscreen orbiter, iPhone resolution 480x320 works quite well. For a screen that&#039;s full width (but requires some vertical scrolling), 640x480 (Standard TV) works well. This resolution allows for easier reading of some orbiter buttons, without the need for zooming in.&lt;br /&gt;
&lt;br /&gt;
===Nintendo DSi===&lt;br /&gt;
Best screen resolution, 480x320 so far. Lower resolutions may work well also with &amp;quot;Mobile Phone Basic&amp;quot; skin applied.&lt;br /&gt;
&lt;br /&gt;
==Good skins for small screens==&lt;br /&gt;
&lt;br /&gt;
here we should list the skins that can be used on the smaller screens of Phones and alike.&lt;br /&gt;
&lt;br /&gt;
The skin &amp;quot;Mobile Phone Basic&amp;quot; is OK readable on the HTC Desire at 480x800.&lt;br /&gt;
&lt;br /&gt;
iPhone/iPod Touch - The &amp;quot;Basic&amp;quot; skin works well. The Titanium skins should also work ok although might be a little bit harder to make out text in file lists etc. &amp;quot;Mobile Phone Basic&amp;quot; isn&#039;t a good choice as it is missing a few buttons (eg. Random in the remote) as it was designed for devices with hardware buttons. Once you load up the web-orbiter on your iPhone the Safari &#039;menu&#039; bars get in the way a bit. This can be overcome by hitting the &#039;+&#039; symbol on the bottom bar and adding an icon to your home screen. This will then open up with only the &#039;status&#039; bar at the top.&lt;br /&gt;
&lt;br /&gt;
==Access to the Web Orbiter==&lt;br /&gt;
&lt;br /&gt;
===From within your home===&lt;br /&gt;
You can access the Web Orbiter 2.0 from any of the following Web browsers (Google Chrome, Mozilla Firefox, Safari). Others may also work but have not been tested (your experiences with other web browsers would be welcome here) :&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;For the 810 releases the correct URL is:&#039;&#039;&#039;&lt;br /&gt;
&#039;&#039;&amp;lt;nowiki&amp;gt;http://&amp;amp;lt;core_ip&amp;amp;gt;/lmce-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:* From within the &amp;quot;internal&amp;quot; LinuxMCE LAN, for example: &lt;br /&gt;
::::&#039;&#039;http://192.168.80.1/lmce-admin/weborbiter.php&#039;&#039; (0810)&lt;br /&gt;
:::::(This assumes the IP address range set by default at installation.)&lt;br /&gt;
:*You can also use the network name of the Core in place of the IP address. For example, if the Core was named &amp;quot;dcerouter&amp;quot; during the default installation, you could use:&lt;br /&gt;
::::&#039;&#039;&amp;lt;nowiki&amp;gt;http://dcerouter/pluto-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
:*From the &amp;quot;external&amp;quot; WAN side of the Core, the core_ip would be the WAN IP address of the core (ie the one offered to the WAN side NIC on the Core by your broadband Router). If, for example, the core has a WAN side address of 192.168.0.50 offered up by your Broadband Router, use:&lt;br /&gt;
:::: &#039;&#039;&amp;lt;nowiki&amp;gt;http://192.168.0.50/lmce-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:::::(Note: To use this method, [[Outside Access]] must be enabled.)&lt;br /&gt;
&lt;br /&gt;
===From the Internet===&lt;br /&gt;
You could use the IP address:port for your home LAN, with port forwarding to the Core&#039;s LAN IP address (enabled by your home LAN router). &lt;br /&gt;
*&#039;&#039;This is an advanced topic and may not be secure in the current version.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
By default, LinuxMCE is not accessible outside your home. This makes the system secure, but it prevents you from accessing the web site via the Internet while away from home.  You can [[Outside_Access|turn on Internet access]], allowing access to the admin website anywhere. For your own security, however, we recommend you first read about [[Security &amp;amp; Privacy Issues]].&lt;br /&gt;
&lt;br /&gt;
===Login page===&lt;br /&gt;
*A simple login page should be displayed. Input an existing user name and password, then click &amp;quot;Login&amp;quot;.&lt;br /&gt;
*From the dropdown list of devices, choose the Web Orbiter you would like to use and click or touch &#039;Open&#039;. If you have got several web orbiters in your system then they will be displayed in the dropdown and you can choose which one to use. (only one user can use any Web Orbiter at a given time)&lt;br /&gt;
*A page that looks similar to this should appear: [[Image:Web Orbiter.jpg|center]]&lt;br /&gt;
*Here is another UI1 variation loaded into Web Orbiter 2.0: [[Image:web_orbiter_20_in_chrome1.jpg|center]]&lt;br /&gt;
*This image is of Web Orbiter 2.0 running on an iPod Touch: [[Image:Web orbiter on iPod Touch4.JPG|center]]&lt;br /&gt;
&lt;br /&gt;
==Where is the Web Orbiter code on my system?==&lt;br /&gt;
&lt;br /&gt;
===Look in the following directories on your Core===&lt;br /&gt;
&lt;br /&gt;
Look in;&lt;br /&gt;
 /var/www/lmce-admin/&lt;br /&gt;
&lt;br /&gt;
You will see the following Web Orbiter related files (there are many other unrelated files in this directory too);&lt;br /&gt;
&lt;br /&gt;
 weborbiter_command.php&lt;br /&gt;
 weborbiter_image.php&lt;br /&gt;
 weborbiter.php&lt;br /&gt;
&lt;br /&gt;
Look in;&lt;br /&gt;
 /var/www/lmce-admin/weborbiter&lt;br /&gt;
&lt;br /&gt;
You should see the following files;&lt;br /&gt;
&lt;br /&gt;
 IT.php         &lt;br /&gt;
 jquery.min.js  &lt;br /&gt;
 jquery.timers.js&lt;br /&gt;
 login.html&lt;br /&gt;
 waiting.gif&lt;br /&gt;
 weborbiter.css&lt;br /&gt;
 weborbiter.html&lt;br /&gt;
 weborbiter.js&lt;br /&gt;
 weborbiter_select.html&lt;br /&gt;
&lt;br /&gt;
==Devices that have been tested with Web orbiter 2.0==&lt;br /&gt;
This is a simple list of devices that have been tested with Web Orbiter 2.0. If you have got a new device to add to this list then please add it below...or if you have some experiences with a device already listed then please add some simple notes here too.&lt;br /&gt;
&lt;br /&gt;
===Ipad===&lt;br /&gt;
&lt;br /&gt;
===iPod===&lt;br /&gt;
&lt;br /&gt;
===iPhone 3GS===&lt;br /&gt;
&lt;br /&gt;
===iPhone 4===&lt;br /&gt;
&lt;br /&gt;
===HTC Hero (Android 1.6)===&lt;br /&gt;
&lt;br /&gt;
===HTC Desire (Android 2.1)===&lt;br /&gt;
Screen size is a little bit small I think, it is difficult to hit the up/down keys.&lt;br /&gt;
&lt;br /&gt;
For &#039;&#039;&#039;full screen&#039;&#039;&#039; orbiter - take a look above at &amp;quot;Device Screen Resolutions&amp;quot; for the right settings&lt;br /&gt;
&lt;br /&gt;
===Nokia N800===&lt;br /&gt;
&lt;br /&gt;
===Nokia N900===&lt;br /&gt;
&lt;br /&gt;
===Nokia 5800 XpressMusic===&lt;br /&gt;
Both &amp;quot;S60 Browser&amp;quot; (default) and &amp;quot;Opera Mobile&amp;quot; work well.&lt;br /&gt;
&lt;br /&gt;
===Nintendo DSi===&lt;br /&gt;
&lt;br /&gt;
===Eken M002===&lt;br /&gt;
&lt;br /&gt;
See M002 info here [[Eken_m002]]. See video of the M002 running Web Orbiter 2.0 here; [http://www.youtube.com/watch?v=eA0SaYYQb7E Eken m002]&lt;br /&gt;
&lt;br /&gt;
==Web Orbiter 2.0 has been tested on the following browsers==&lt;br /&gt;
&lt;br /&gt;
===Firefox 3.6===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
===Chrome 6.0.453.1 dev===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
Also works fine as a chrome application shortcut.&lt;br /&gt;
Just create the shortcut when you are logged into the orbiter and have the right device chosen.&lt;br /&gt;
&lt;br /&gt;
===OperaMini===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
===OperaMobile 10===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
===Midori 0.2.2===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
===Internet Explorer===&lt;br /&gt;
Not working due to javascript issues.&lt;br /&gt;
&lt;br /&gt;
===S60 Browser===&lt;br /&gt;
Default Symbian browser - works fine (tested on Nokia 5800 XpressMusic)&lt;br /&gt;
&lt;br /&gt;
===Nintendo DSi Browser===&lt;br /&gt;
(based on Opera)&lt;br /&gt;
&lt;br /&gt;
==Troubleshooting==&lt;br /&gt;
===Connect failed===&lt;br /&gt;
If you try to connect to the Web Orbiter and see this message:&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;quot;Connect to proxy orbiter failed, please try again&amp;quot;&amp;lt;/code&amp;gt;, &lt;br /&gt;
this means that Orbiter generation hasn&#039;t finished yet, or that you forgot to do a [[Quick_reload_router|quick restart of the router]].&lt;br /&gt;
&lt;br /&gt;
Keywords: WebOrbiter&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Web_Orbiter_2.0&amp;diff=24587</id>
		<title>Web Orbiter 2.0</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Web_Orbiter_2.0&amp;diff=24587"/>
		<updated>2010-07-22T08:44:44Z</updated>

		<summary type="html">&lt;p&gt;Viking: /* Good skins for small screens */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{versioninfo}}&lt;br /&gt;
{| align=&amp;quot;right&amp;quot;&lt;br /&gt;
  | __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
[[Category: Orbiters]]&lt;br /&gt;
[[Category: Tutorials]]&lt;br /&gt;
&lt;br /&gt;
A Web Orbiter is any device (such as a iPhone, iPod Touch, iPad, laptop, PC, etc.) that accesses the Orbiter user interface (UI) through a Web browser.&lt;br /&gt;
&lt;br /&gt;
The new Web Orbiter 2.0 has been re-written from the ground up to make sure it has a much smoother performance overall but especially on slower lower powered devices and devices that are connected over slow LAN connections or even slower external connections...such as a Mobile 3G network or slow WiFi connection.&lt;br /&gt;
&lt;br /&gt;
So what has changed? Well visually your Orbiter UI will look like it does on your existing standard Orbiters but you will notice that unlike the original Web Orbiter the new 2.0 version does not refresh every 5 secs. The new Web Orbiter now only updates if something changes in the system and that requires the UI screen you are currently viewing to be updated or if you click on a UI button or other UI element and that causes a screen update. &lt;br /&gt;
&lt;br /&gt;
To achieve this the proxy_orbiter has been updated so that it sets a flag called &#039;ANYNEWS&#039; to &#039;true&#039; if some element of the current displayed screen has been updated. The Web Orbiter makes a light weight call to query the state of this flag once every second and only gets an updated UI screen if the flag is set to &#039;true&#039; otherwise no screen update is requested. So in use the new Web Orbiter 2.0 behaves in a very similar fashion to the Orbiter on one of your MD&#039;s - and now it even performs with a similar performance level too.&lt;br /&gt;
&lt;br /&gt;
Whats a proxy_orbiter? Proxy_orbiter runs on the Core and its job is to render the UI for the Web Orbiter that is running remotely on some other device. Each Web Orbiter has an associated proxy_orbiter and the two work in partnership. Proxy_orbiters do all the &#039;heavy lifting&#039; rendering the UI and this allows the remote device that is running the Web Orbiter to be much less powerful and very simple devices indeed if needed.&lt;br /&gt;
&lt;br /&gt;
Another change in the new 2.0 Web Orbiter is that screen refreshes are double buffered so that the new Web Orbiter receives the new screen update from your Core in the background and only redraws the screen when it has the complete image stored in memory - this makes the update process smoother and faster.&lt;br /&gt;
&lt;br /&gt;
The overall effect of all these changes is to vastly improve the performance and usability while at the same time reducing the processing overhead of the Web Orbiter massively.&lt;br /&gt;
&lt;br /&gt;
== Setup ==&lt;br /&gt;
The procedure to setup a Web Orbiter is simple but the order of steps is important.&lt;br /&gt;
#First of all, add a new Generic Web Device as a Child Device for your Core:&lt;br /&gt;
##Goto the LinuxMCE Admin website--&amp;gt;Show devices tree--&amp;gt;CORE. The CORE&#039;s detail page should appear.&lt;br /&gt;
##Click &#039;Create Child Device&#039;.&lt;br /&gt;
##In the Description, enter the name of the specific web orbiter.&lt;br /&gt;
##In the Add child device window, click the button &#039;Pick device template&#039;. The new pop-up window containing device templates will be opened.&lt;br /&gt;
##In the &#039;Device Category&#039; dropdown list, choose &#039;Peripherals&#039;.&lt;br /&gt;
##In the &#039;Device Template&#039; dropdown list, find and select &amp;quot;Generic Web Device&amp;quot; (or just type the template id: 1748 and press go).&lt;br /&gt;
##Click the button &#039;Pick Device Template&#039;. 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.&lt;br /&gt;
##A new Generic Proxy Orbiter will also be created automatically. Watch the Orbiter generation process on the Orbiters page: Wizard--&amp;gt;Devices--&amp;gt;Orbiters.&lt;br /&gt;
#Wait till the Orbiter generation procedure finishes. A message on an active Orbiter or on the Orbiter page will indicate when it has completed.&lt;br /&gt;
#Set the appropriate screen resolution to suit the device your Web Orbiter is intended for from the &#039;Size&#039; drop down&lt;br /&gt;
#Set the &#039;Skin&#039; drop down to the skin you want to use (normally this would mean the UI1 Standard Variation or a derivative)&lt;br /&gt;
#Click on your new Generic Proxy Orbiter in the device tree, give it a unique name and then scroll to the bottom of the page on the right and look for the field called &#039;Listen Port&#039;. This field will be set to &#039;3461&#039; by default (if this Web Orbiter is not your first then you should increment this value by one ie to &#039;3462&#039; - each Web Orbiter must have a unique &#039;Listen Port&#039; number)&lt;br /&gt;
#Now click the &#039;Save&#039; button at the bottom of the screen to save the changes you have made.&lt;br /&gt;
#Now do a &#039;Full Regen&#039; from the &#039;Wizard - Orbiters&#039; page (use the &#039;Full Regen&#039; for the specific Web Orbiter you have created and not the overall &#039;Full Regen&#039; button at the top of the page). Next when the Regen has completed do a &amp;quot;[[Quick reload router]]&amp;quot;. Otherwise, the Web Orbiter won&#039;t work properly.&lt;br /&gt;
&lt;br /&gt;
==Device Screen Resolutions==&lt;br /&gt;
If the &#039;Device&#039; your planning to use your Web Orbiter on is a Desktop or Laptop then use the biggest resolution that will comfortably fit onto your screen. If your device is a touch screen device like an iPad, iPhone or iPod Touch then choose a resoltion that matches the overall resolution of the devices display;&lt;br /&gt;
&lt;br /&gt;
===iPad===&lt;br /&gt;
The iPad has a screen resolution of 1024x768 so if your creating an Orbiter for the iPad this is the resolution you should select for this Web Orbiter.&lt;br /&gt;
&lt;br /&gt;
===iPhone (pre iPhone 4) or iPad Touch===&lt;br /&gt;
The iPhone/iPod Touch hav a screen resolution of 480x320 so if your creating an Orbiter for either of these this is the resolution you should select for this Web Orbiter.&lt;br /&gt;
&lt;br /&gt;
===iPhone 4===&lt;br /&gt;
The iPhone 4 has a screen resolution of 960x640 so if your creating an Orbiter for the iPhone 4 this is the resolution you should select for this Web Orbiter.&lt;br /&gt;
&lt;br /&gt;
===Google Nexus One or HTC Desire (Android)===&lt;br /&gt;
If you have a Nexus One you will need to select a resolution of 480x800 (select N770 in the web admin, it is 480x800) so if your creating an Orbiter for the Nexus One this is the resolution you should select for this Web Orbiter.&lt;br /&gt;
&lt;br /&gt;
On the HTC Desire you might also have to go into the web browser settings and change the default zoom to &amp;quot;far away&amp;quot; (mine is danish, so don&#039;t know the exact english decription). After that it should be full screen.&lt;br /&gt;
&lt;br /&gt;
==Good skins for small screens==&lt;br /&gt;
&lt;br /&gt;
here we should list the skins that can be used on the smaller screens of Phones and alike.&lt;br /&gt;
&lt;br /&gt;
The skin &amp;quot;Mobile Phone Basic&amp;quot; is OK readable on the HTC Desire at 480x800.&lt;br /&gt;
&lt;br /&gt;
==Access to the Web Orbiter==&lt;br /&gt;
&lt;br /&gt;
===From within your home===&lt;br /&gt;
You can access the Web Orbiter 2.0 from any of the following Web browsers (Google Chrome, Mozilla Firefox, Safari). Others may also work but have not been tested (your experiences with other web browsers would be welcome here) :&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;For the 810 releases the correct URL is:&#039;&#039;&#039;&lt;br /&gt;
&#039;&#039;&amp;lt;nowiki&amp;gt;http://&amp;amp;lt;core_ip&amp;amp;gt;/lmce-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:* From within the &amp;quot;internal&amp;quot; LinuxMCE LAN, for example: &lt;br /&gt;
::::&#039;&#039;http://192.168.80.1/lmce-admin/weborbiter.php&#039;&#039; (0810)&lt;br /&gt;
:::::(This assumes the IP address range set by default at installation.)&lt;br /&gt;
:*You can also use the network name of the Core in place of the IP address. For example, if the Core was named &amp;quot;dcerouter&amp;quot; during the default installation, you could use:&lt;br /&gt;
::::&#039;&#039;&amp;lt;nowiki&amp;gt;http://dcerouter/pluto-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
:*From the &amp;quot;external&amp;quot; WAN side of the Core, the core_ip would be the WAN IP address of the core (ie the one offered to the WAN side NIC on the Core by your broadband Router). If, for example, the core has a WAN side address of 192.168.0.50 offered up by your Broadband Router, use:&lt;br /&gt;
:::: &#039;&#039;&amp;lt;nowiki&amp;gt;http://192.168.0.50/lmce-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:::::(Note: To use this method, [[Outside Access]] must be enabled.)&lt;br /&gt;
&lt;br /&gt;
===From the Internet===&lt;br /&gt;
You could use the IP address:port for your home LAN, with port forwarding to the Core&#039;s LAN IP address (enabled by your home LAN router). &lt;br /&gt;
*&#039;&#039;This is an advanced topic and may not be secure in the current version.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
By default, LinuxMCE is not accessible outside your home. This makes the system secure, but it prevents you from accessing the web site via the Internet while away from home.  You can [[Outside_Access|turn on Internet access]], allowing access to the admin website anywhere. For your own security, however, we recommend you first read about [[Security &amp;amp; Privacy Issues]].&lt;br /&gt;
&lt;br /&gt;
===Login page===&lt;br /&gt;
*A simple login page should be displayed. Input an existing user name and password, then click &amp;quot;Login&amp;quot;.&lt;br /&gt;
*From the dropdown list of devices, choose the Web Orbiter you would like to use and click or touch &#039;Open&#039;. If you have got several web orbiters in your system then they will be displayed in the dropdown and you can choose which one to use. (only one user can use any Web Orbiter at a given time)&lt;br /&gt;
*A page that looks similar to this should appear: [[Image:Web Orbiter.jpg|center]]&lt;br /&gt;
*Here is another UI1 variation loaded into Web Orbiter 2.0: [[Image:web_orbiter_20_in_chrome1.jpg|center]]&lt;br /&gt;
*This image is of Web Orbiter 2.0 running on an iPod Touch: [[Image:Web orbiter on iPod Touch4.JPG|center]]&lt;br /&gt;
&lt;br /&gt;
==Where is the Web Orbiter code on my system?==&lt;br /&gt;
&lt;br /&gt;
===Look in the following directories on your Core===&lt;br /&gt;
&lt;br /&gt;
Look in;&lt;br /&gt;
 /var/www/lmce-admin/&lt;br /&gt;
&lt;br /&gt;
You will see the following Web Orbiter related files (there are many other unrelated files in this directory too);&lt;br /&gt;
&lt;br /&gt;
 weborbiter_command.php&lt;br /&gt;
 weborbiter_image.php&lt;br /&gt;
 weborbiter.php&lt;br /&gt;
&lt;br /&gt;
Look in;&lt;br /&gt;
 /var/www/lmce-admin/weborbiter&lt;br /&gt;
&lt;br /&gt;
You should see the following files;&lt;br /&gt;
&lt;br /&gt;
 IT.php         &lt;br /&gt;
 jquery.min.js  &lt;br /&gt;
 jquery.timers.js&lt;br /&gt;
 login.html&lt;br /&gt;
 waiting.gif&lt;br /&gt;
 weborbiter.css&lt;br /&gt;
 weborbiter.html&lt;br /&gt;
 weborbiter.js&lt;br /&gt;
 weborbiter_select.html&lt;br /&gt;
&lt;br /&gt;
==Devices that have been tested with Web orbiter 2.0==&lt;br /&gt;
This is a simple list of devices that have been tested with Web Orbiter 2.0. If you have got a new device to add to this list then please add it below...or if you have some experiences with a device already listed then please add some simple notes here too.&lt;br /&gt;
&lt;br /&gt;
===Ipad===&lt;br /&gt;
&lt;br /&gt;
===iPod===&lt;br /&gt;
&lt;br /&gt;
===iPhone 3GS===&lt;br /&gt;
&lt;br /&gt;
===iPhone 4===&lt;br /&gt;
&lt;br /&gt;
===HTC Hero (Android 1.6)===&lt;br /&gt;
&lt;br /&gt;
===HTC Desire (Android 2.1)===&lt;br /&gt;
Screen size is a little bit small I think, it is difficult to hit the up/down keys. &lt;br /&gt;
&lt;br /&gt;
===Nokia N800===&lt;br /&gt;
&lt;br /&gt;
===Nokia N900===&lt;br /&gt;
&lt;br /&gt;
==Web Orbiter 2.0 has been tested on the following browsers==&lt;br /&gt;
&lt;br /&gt;
===Firefox 3.6===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
===Chrome 6.0.453.1 dev===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
Also works fine as a chrome application shortcut.&lt;br /&gt;
Just create the shortcut when you are logged into the orbiter and have the right device chosen.&lt;br /&gt;
&lt;br /&gt;
===OperaMini===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
===OperaMobile 10===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
===Midori 0.2.2===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
===Internet Explorer===&lt;br /&gt;
Not working due to javascript issues.&lt;br /&gt;
&lt;br /&gt;
==Troubleshooting==&lt;br /&gt;
===Connect failed===&lt;br /&gt;
If you try to connect to the Web Orbiter and see this message:&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;quot;Connect to proxy orbiter failed, please try again&amp;quot;&amp;lt;/code&amp;gt;, &lt;br /&gt;
this means that Orbiter generation hasn&#039;t finished yet, or that you forgot to do a [[Quick_reload_router|quick restart of the router]].&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Web_Orbiter_2.0&amp;diff=24583</id>
		<title>Web Orbiter 2.0</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Web_Orbiter_2.0&amp;diff=24583"/>
		<updated>2010-07-21T14:09:41Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{versioninfo}}&lt;br /&gt;
{| align=&amp;quot;right&amp;quot;&lt;br /&gt;
  | __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
[[Category: Orbiters]]&lt;br /&gt;
[[Category: Tutorials]]&lt;br /&gt;
&lt;br /&gt;
A Web Orbiter is any device (such as a iPhone, iPod Touch, iPad, laptop, PC, etc.) that accesses the Orbiter user interface (UI) through a Web browser.&lt;br /&gt;
&lt;br /&gt;
The new Web Orbiter 2.0 has been re-written from the ground up to make sure it has a much smoother performance overall but especially on slower lower powered devices and devices that are connected over slow LAN connections or even slower external connections...such as a Mobile 3G network or slow WiFi connection.&lt;br /&gt;
&lt;br /&gt;
So what has changed? Well visually your Orbiter UI will look like it does on your existing standard Orbiters but you will notice that unlike the original Web Orbiter the new 2.0 version does not refresh every 5 secs. The new Web Orbiter now only updates if something changes in the system and that requires the UI screen you are currently viewing to be updated or if you click on a UI button or other UI element and that causes a screen update. &lt;br /&gt;
&lt;br /&gt;
To achieve this the proxy_orbiter has been updated so that it sets a flag called &#039;ANYNEWS&#039; to &#039;true&#039; if some element of the current displayed screen has been updated. The Web Orbiter makes a light weight call to query the state of this flag once every second and only gets an updated UI screen if the flag is set to &#039;true&#039; otherwise no screen update is requested. So in use the new Web Orbiter 2.0 behaves in a very similar fashion to the Orbiter on one of your MD&#039;s - and now it even performs with a similar performance level too.&lt;br /&gt;
&lt;br /&gt;
Whats a proxy_orbiter? Proxy_orbiter runs on the Core and its job is to render the UI for the Web Orbiter that is running remotely on some other device. Each Web Orbiter has an associated proxy_orbiter and the two work in partnership. Proxy_orbiters do all the &#039;heavy lifting&#039; rendering the UI and this allows the remote device that is running the Web Orbiter to be much less powerful and very simple devices indeed if needed.&lt;br /&gt;
&lt;br /&gt;
Another change in the new 2.0 Web Orbiter is that screen refreshes are double buffered so that the new Web Orbiter receives the new screen update from your Core in the background and only redraws the screen when it has the complete image stored in memory - this makes the update process smoother and faster.&lt;br /&gt;
&lt;br /&gt;
The overall effect of all these changes is to vastly improve the performance and usability while at the same time reducing the processing overhead of the Web Orbiter massively.&lt;br /&gt;
&lt;br /&gt;
== Setup ==&lt;br /&gt;
The procedure to setup a Web Orbiter is simple but the order of steps is important.&lt;br /&gt;
#First of all, add a new Generic Web Device as a Child Device for your Core:&lt;br /&gt;
##Goto the LinuxMCE Admin website--&amp;gt;Show devices tree--&amp;gt;CORE. The CORE&#039;s detail page should appear.&lt;br /&gt;
##Click &#039;Create Child Device&#039;.&lt;br /&gt;
##In the Description, enter the name of the specific web orbiter.&lt;br /&gt;
##In the Add child device window, click the button &#039;Pick device template&#039;. The new pop-up window containing device templates will be opened.&lt;br /&gt;
##In the &#039;Device Category&#039; dropdown list, choose &#039;Peripherals&#039;.&lt;br /&gt;
##In the &#039;Device Template&#039; dropdown list, find and select &amp;quot;Generic Web Device&amp;quot; (or just type the template id: 1748 and press go).&lt;br /&gt;
##Click the button &#039;Pick Device Template&#039;. 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.&lt;br /&gt;
##A new Generic Proxy Orbiter will also be created automatically. Watch the Orbiter generation process on the Orbiters page: Wizard--&amp;gt;Devices--&amp;gt;Orbiters.&lt;br /&gt;
#Wait till the Orbiter generation procedure finishes. A message on an active Orbiter or on the Orbiter page will indicate when it has completed.&lt;br /&gt;
#Set the appropriate screen resolution to suit the device your Web Orbiter is intended for from the &#039;Size&#039; drop down&lt;br /&gt;
#Set the &#039;Skin&#039; drop down to the skin you want to use (normally this would mean the UI1 Standard Variation or a derivative)&lt;br /&gt;
#Click on your new Generic Proxy Orbiter in the device tree, give it a unique name and then scroll to the bottom of the page on the right and look for the field called &#039;Listen Port&#039;. This field will be set to &#039;3461&#039; by default (if this Web Orbiter is not your first then you should increment this value by one ie to &#039;3462&#039; - each Web Orbiter must have a unique &#039;Listen Port&#039; number)&lt;br /&gt;
#Now click the &#039;Save&#039; button at the bottom of the screen to save the changes you have made.&lt;br /&gt;
#Now do a &#039;Full Regen&#039; from the &#039;Wizard - Orbiters&#039; page (use the &#039;Full Regen&#039; for the specific Web Orbiter you have created and not the overall &#039;Full Regen&#039; button at the top of the page). Next when the Regen has completed do a &amp;quot;[[Quick reload router]]&amp;quot;. Otherwise, the Web Orbiter won&#039;t work properly.&lt;br /&gt;
&lt;br /&gt;
==Device Screen Resolutions==&lt;br /&gt;
If the &#039;Device&#039; your planning to use your Web Orbiter on is a Desktop or Laptop then use the biggest resolution that will comfortably fit onto your screen. If your device is a touch screen device like an iPad, iPhone or iPod Touch then choose a resoltion that matches the overall resolution of the devices display;&lt;br /&gt;
&lt;br /&gt;
===iPad===&lt;br /&gt;
The iPad has a screen resolution of 1024x768 so if your creating an Orbiter for the iPad this is the resolution you should select for this Web Orbiter.&lt;br /&gt;
&lt;br /&gt;
===iPhone (pre iPhone 4) or iPad Touch===&lt;br /&gt;
The iPhone/iPod Touch hav a screen resolution of 480x320 so if your creating an Orbiter for either of these this is the resolution you should select for this Web Orbiter.&lt;br /&gt;
&lt;br /&gt;
===iPhone 4===&lt;br /&gt;
The iPhone 4 has a screen resolution of 960x640 so if your creating an Orbiter for the iPhone 4 this is the resolution you should select for this Web Orbiter.&lt;br /&gt;
&lt;br /&gt;
===Google Nexus One or HTC Desire (Android)===&lt;br /&gt;
If you have a Nexus One you will need to select a resolution of 480x800 (select N770 in the web admin, it is 480x800) so if your creating an Orbiter for the Nexus One this is the resolution you should select for this Web Orbiter.&lt;br /&gt;
&lt;br /&gt;
On the HTC Desire you might also have to go into the web browser settings and change the default zoom to &amp;quot;far away&amp;quot; (mine is danish, so don&#039;t know the exact english decription). After that it should be full screen.&lt;br /&gt;
&lt;br /&gt;
==Good skins for small screens==&lt;br /&gt;
&lt;br /&gt;
here we should list the skins that can be used on the smaller screens of Phones and alike.&lt;br /&gt;
&lt;br /&gt;
==Access to the Web Orbiter==&lt;br /&gt;
&lt;br /&gt;
===From within your home===&lt;br /&gt;
You can access the Web Orbiter 2.0 from any of the following Web browsers (Google Chrome, Mozilla Firefox, Safari). Others may also work but have not been tested (your experiences with other web browsers would be welcome here) :&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;For the 810 releases the correct URL is:&#039;&#039;&#039;&lt;br /&gt;
&#039;&#039;&amp;lt;nowiki&amp;gt;http://&amp;amp;lt;core_ip&amp;amp;gt;/lmce-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:* From within the &amp;quot;internal&amp;quot; LinuxMCE LAN, for example: &lt;br /&gt;
::::&#039;&#039;http://192.168.80.1/lmce-admin/weborbiter.php&#039;&#039; (0810)&lt;br /&gt;
:::::(This assumes the IP address range set by default at installation.)&lt;br /&gt;
:*You can also use the network name of the Core in place of the IP address. For example, if the Core was named &amp;quot;dcerouter&amp;quot; during the default installation, you could use:&lt;br /&gt;
::::&#039;&#039;&amp;lt;nowiki&amp;gt;http://dcerouter/pluto-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
:*From the &amp;quot;external&amp;quot; WAN side of the Core, the core_ip would be the WAN IP address of the core (ie the one offered to the WAN side NIC on the Core by your broadband Router). If, for example, the core has a WAN side address of 192.168.0.50 offered up by your Broadband Router, use:&lt;br /&gt;
:::: &#039;&#039;&amp;lt;nowiki&amp;gt;http://192.168.0.50/lmce-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:::::(Note: To use this method, [[Outside Access]] must be enabled.)&lt;br /&gt;
&lt;br /&gt;
===From the Internet===&lt;br /&gt;
You could use the IP address:port for your home LAN, with port forwarding to the Core&#039;s LAN IP address (enabled by your home LAN router). &lt;br /&gt;
*&#039;&#039;This is an advanced topic and may not be secure in the current version.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
By default, LinuxMCE is not accessible outside your home. This makes the system secure, but it prevents you from accessing the web site via the Internet while away from home.  You can [[Outside_Access|turn on Internet access]], allowing access to the admin website anywhere. For your own security, however, we recommend you first read about [[Security &amp;amp; Privacy Issues]].&lt;br /&gt;
&lt;br /&gt;
===Login page===&lt;br /&gt;
*A simple login page should be displayed. Input an existing user name and password, then click &amp;quot;Login&amp;quot;.&lt;br /&gt;
*From the dropdown list of devices, choose the Web Orbiter you would like to use and click or touch &#039;Open&#039;. If you have got several web orbiters in your system then they will be displayed in the dropdown and you can choose which one to use. (only one user can use any Web Orbiter at a given time)&lt;br /&gt;
*A page that looks similar to this should appear: [[Image:Web Orbiter.jpg|center]]&lt;br /&gt;
*Here is another UI1 variation loaded into Web Orbiter 2.0: [[Image:web_orbiter_20_in_chrome1.jpg|center]]&lt;br /&gt;
*This image is of Web Orbiter 2.0 running on an iPod Touch: [[Image:Web orbiter on iPod Touch4.JPG|center]]&lt;br /&gt;
&lt;br /&gt;
==Where is the Web Orbiter code on my system?==&lt;br /&gt;
&lt;br /&gt;
===Look in the following directories on your Core===&lt;br /&gt;
&lt;br /&gt;
Look in;&lt;br /&gt;
 /var/www/lmce-admin/&lt;br /&gt;
&lt;br /&gt;
You will see the following Web Orbiter related files (there are many other unrelated files in this directory too);&lt;br /&gt;
&lt;br /&gt;
 weborbiter_command.php&lt;br /&gt;
 weborbiter_image.php&lt;br /&gt;
 weborbiter.php&lt;br /&gt;
&lt;br /&gt;
Look in;&lt;br /&gt;
 /var/www/lmce-admin/weborbiter&lt;br /&gt;
&lt;br /&gt;
You should see the following files;&lt;br /&gt;
&lt;br /&gt;
 IT.php         &lt;br /&gt;
 jquery.min.js  &lt;br /&gt;
 jquery.timers.js&lt;br /&gt;
 login.html&lt;br /&gt;
 waiting.gif&lt;br /&gt;
 weborbiter.css&lt;br /&gt;
 weborbiter.html&lt;br /&gt;
 weborbiter.js&lt;br /&gt;
 weborbiter_select.html&lt;br /&gt;
&lt;br /&gt;
==Devices that have been tested with Web orbiter 2.0==&lt;br /&gt;
This is a simple list of devices that have been tested with Web Orbiter 2.0. If you have got a new device to add to this list then please add it below...or if you have some experiences with a device already listed then please add some simple notes here too.&lt;br /&gt;
&lt;br /&gt;
===Ipad===&lt;br /&gt;
&lt;br /&gt;
===iPod===&lt;br /&gt;
&lt;br /&gt;
===iPhone 3GS===&lt;br /&gt;
&lt;br /&gt;
===iPhone 4===&lt;br /&gt;
&lt;br /&gt;
===HTC Hero (Android 1.6)===&lt;br /&gt;
&lt;br /&gt;
===HTC Desire (Android 2.1)===&lt;br /&gt;
Screen size is a little bit small I think, it is difficult to hit the up/down keys. &lt;br /&gt;
&lt;br /&gt;
===Nokia N800===&lt;br /&gt;
&lt;br /&gt;
===Nokia N900===&lt;br /&gt;
&lt;br /&gt;
==Web Orbiter 2.0 has been tested on the following browsers==&lt;br /&gt;
&lt;br /&gt;
===Firefox 3.6===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
===Chrome 6.0.453.1 dev===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
Also works fine as a chrome application shortcut.&lt;br /&gt;
Just create the shortcut when you are logged into the orbiter and have the right device chosen.&lt;br /&gt;
&lt;br /&gt;
===OperaMini===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
===OperaMobile 10===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
===Midori 0.2.2===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
===Internet Explorer===&lt;br /&gt;
Not working due to javascript issues.&lt;br /&gt;
&lt;br /&gt;
==Troubleshooting==&lt;br /&gt;
===Connect failed===&lt;br /&gt;
If you try to connect to the Web Orbiter and see this message:&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;quot;Connect to proxy orbiter failed, please try again&amp;quot;&amp;lt;/code&amp;gt;, &lt;br /&gt;
this means that Orbiter generation hasn&#039;t finished yet, or that you forgot to do a [[Quick_reload_router|quick restart of the router]].&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Web_Orbiter_2.0&amp;diff=24582</id>
		<title>Web Orbiter 2.0</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Web_Orbiter_2.0&amp;diff=24582"/>
		<updated>2010-07-21T14:07:23Z</updated>

		<summary type="html">&lt;p&gt;Viking: /* Devices that have been tested with Web orbiter 2.0 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{versioninfo}}&lt;br /&gt;
{| align=&amp;quot;right&amp;quot;&lt;br /&gt;
  | __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
[[Category: Orbiters]]&lt;br /&gt;
[[Category: Tutorials]]&lt;br /&gt;
&lt;br /&gt;
A Web Orbiter is any device (such as a iPhone, iPod Touch, iPad, laptop, PC, etc.) that accesses the Orbiter user interface (UI) through a Web browser.&lt;br /&gt;
&lt;br /&gt;
The new Web Orbiter 2.0 has been re-written from the ground up to make sure it has a much smoother performance overall but especially on slower lower powered devices and devices that are connected over slow LAN connections or even slower external connections...such as a Mobile 3G network or slow WiFi connection.&lt;br /&gt;
&lt;br /&gt;
So what has changed? Well visually your Orbiter UI will look like it does on your existing standard Orbiters but you will notice that unlike the original Web Orbiter the new 2.0 version does not refresh every 5 secs. The new Web Orbiter now only updates if something changes in the system and that requires the UI screen you are currently viewing to be updated or if you click on a UI button or other UI element and that causes a screen update. &lt;br /&gt;
&lt;br /&gt;
To achieve this the proxy_orbiter has been updated so that it sets a flag called &#039;ANYNEWS&#039; to &#039;true&#039; if some element of the current displayed screen has been updated. The Web Orbiter makes a light weight call to query the state of this flag once every second and only gets an updated UI screen if the flag is set to &#039;true&#039; otherwise no screen update is requested. So in use the new Web Orbiter 2.0 behaves in a very similar fashion to the Orbiter on one of your MD&#039;s - and now it even performs with a similar performance level too.&lt;br /&gt;
&lt;br /&gt;
Whats a proxy_orbiter? Proxy_orbiter runs on the Core and its job is to render the UI for the Web Orbiter that is running remotely on some other device. Each Web Orbiter has an associated proxy_orbiter and the two work in partnership. Proxy_orbiters do all the &#039;heavy lifting&#039; rendering the UI and this allows the remote device that is running the Web Orbiter to be much less powerful and very simple devices indeed if needed.&lt;br /&gt;
&lt;br /&gt;
Another change in the new 2.0 Web Orbiter is that screen refreshes are double buffered so that the new Web Orbiter receives the new screen update from your Core in the background and only redraws the screen when it has the complete image stored in memory - this makes the update process smoother and faster.&lt;br /&gt;
&lt;br /&gt;
The overall effect of all these changes is to vastly improve the performance and usability while at the same time reducing the processing overhead of the Web Orbiter massively.&lt;br /&gt;
&lt;br /&gt;
== Setup ==&lt;br /&gt;
The procedure to setup a Web Orbiter is simple but the order of steps is important.&lt;br /&gt;
#First of all, add a new Generic Web Device as a Child Device for your Core:&lt;br /&gt;
##Goto the LinuxMCE Admin website--&amp;gt;Show devices tree--&amp;gt;CORE. The CORE&#039;s detail page should appear.&lt;br /&gt;
##Click &#039;Create Child Device&#039;.&lt;br /&gt;
##In the Description, enter the name of the specific web orbiter.&lt;br /&gt;
##In the Add child device window, click the button &#039;Pick device template&#039;. The new pop-up window containing device templates will be opened.&lt;br /&gt;
##In the &#039;Device Category&#039; dropdown list, choose &#039;Peripherals&#039;.&lt;br /&gt;
##In the &#039;Device Template&#039; dropdown list, find and select &amp;quot;Generic Web Device&amp;quot; (or just type the template id: 1748 and press go).&lt;br /&gt;
##Click the button &#039;Pick Device Template&#039;. 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.&lt;br /&gt;
##A new Generic Proxy Orbiter will also be created automatically. Watch the Orbiter generation process on the Orbiters page: Wizard--&amp;gt;Devices--&amp;gt;Orbiters.&lt;br /&gt;
#Wait till the Orbiter generation procedure finishes. A message on an active Orbiter or on the Orbiter page will indicate when it has completed.&lt;br /&gt;
#Set the appropriate screen resolution to suit the device your Web Orbiter is intended for from the &#039;Size&#039; drop down&lt;br /&gt;
#Set the &#039;Skin&#039; drop down to the skin you want to use (normally this would mean the UI1 Standard Variation or a derivative)&lt;br /&gt;
#Click on your new Generic Proxy Orbiter in the device tree, give it a unique name and then scroll to the bottom of the page on the right and look for the field called &#039;Listen Port&#039;. This field will be set to &#039;3461&#039; by default (if this Web Orbiter is not your first then you should increment this value by one ie to &#039;3462&#039; - each Web Orbiter must have a unique &#039;Listen Port&#039; number)&lt;br /&gt;
#Now click the &#039;Save&#039; button at the bottom of the screen to save the changes you have made.&lt;br /&gt;
#Now do a &#039;Full Regen&#039; from the &#039;Wizard - Orbiters&#039; page (use the &#039;Full Regen&#039; for the specific Web Orbiter you have created and not the overall &#039;Full Regen&#039; button at the top of the page). Next when the Regen has completed do a &amp;quot;[[Quick reload router]]&amp;quot;. Otherwise, the Web Orbiter won&#039;t work properly.&lt;br /&gt;
&lt;br /&gt;
==Device Screen Resolutions==&lt;br /&gt;
If the &#039;Device&#039; your planning to use your Web Orbiter on is a Desktop or Laptop then use the biggest resolution that will comfortably fit onto your screen. If your device is a touch screen device like an iPad, iPhone or iPod Touch then choose a resoltion that matches the overall resolution of the devices display;&lt;br /&gt;
&lt;br /&gt;
===iPad===&lt;br /&gt;
The iPad has a screen resolution of 1024x768 so if your creating an Orbiter for the iPad this is the resolution you should select for this Web Orbiter.&lt;br /&gt;
&lt;br /&gt;
===iPhone (pre iPhone 4) or iPad Touch===&lt;br /&gt;
The iPhone/iPod Touch hav a screen resolution of 480x320 so if your creating an Orbiter for either of these this is the resolution you should select for this Web Orbiter.&lt;br /&gt;
&lt;br /&gt;
===iPhone 4===&lt;br /&gt;
The iPhone 4 has a screen resolution of 960x640 so if your creating an Orbiter for the iPhone 4 this is the resolution you should select for this Web Orbiter.&lt;br /&gt;
&lt;br /&gt;
===Google Nexus One or HTC Desire (Android)===&lt;br /&gt;
If you have a Nexus One you will need to select a resolution of 480x800 (select N770 in the web admin, it is 480x800) so if your creating an Orbiter for the Nexus One this is the resolution you should select for this Web Orbiter.&lt;br /&gt;
&lt;br /&gt;
On the HTC Desire you might also have to go into the web browser settings and change the default zoom to &amp;quot;far away&amp;quot; (mine is danish, so don&#039;t know the exact english decription). After that it should be full screen.&lt;br /&gt;
&lt;br /&gt;
==Access to the Web Orbiter==&lt;br /&gt;
&lt;br /&gt;
===From within your home===&lt;br /&gt;
You can access the Web Orbiter 2.0 from any of the following Web browsers (Google Chrome, Mozilla Firefox, Safari). Others may also work but have not been tested (your experiences with other web browsers would be welcome here) :&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;For the 810 releases the correct URL is:&#039;&#039;&#039;&lt;br /&gt;
&#039;&#039;&amp;lt;nowiki&amp;gt;http://&amp;amp;lt;core_ip&amp;amp;gt;/lmce-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:* From within the &amp;quot;internal&amp;quot; LinuxMCE LAN, for example: &lt;br /&gt;
::::&#039;&#039;http://192.168.80.1/lmce-admin/weborbiter.php&#039;&#039; (0810)&lt;br /&gt;
:::::(This assumes the IP address range set by default at installation.)&lt;br /&gt;
:*You can also use the network name of the Core in place of the IP address. For example, if the Core was named &amp;quot;dcerouter&amp;quot; during the default installation, you could use:&lt;br /&gt;
::::&#039;&#039;&amp;lt;nowiki&amp;gt;http://dcerouter/pluto-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
:*From the &amp;quot;external&amp;quot; WAN side of the Core, the core_ip would be the WAN IP address of the core (ie the one offered to the WAN side NIC on the Core by your broadband Router). If, for example, the core has a WAN side address of 192.168.0.50 offered up by your Broadband Router, use:&lt;br /&gt;
:::: &#039;&#039;&amp;lt;nowiki&amp;gt;http://192.168.0.50/lmce-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:::::(Note: To use this method, [[Outside Access]] must be enabled.)&lt;br /&gt;
&lt;br /&gt;
===From the Internet===&lt;br /&gt;
You could use the IP address:port for your home LAN, with port forwarding to the Core&#039;s LAN IP address (enabled by your home LAN router). &lt;br /&gt;
*&#039;&#039;This is an advanced topic and may not be secure in the current version.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
By default, LinuxMCE is not accessible outside your home. This makes the system secure, but it prevents you from accessing the web site via the Internet while away from home.  You can [[Outside_Access|turn on Internet access]], allowing access to the admin website anywhere. For your own security, however, we recommend you first read about [[Security &amp;amp; Privacy Issues]].&lt;br /&gt;
&lt;br /&gt;
===Login page===&lt;br /&gt;
*A simple login page should be displayed. Input an existing user name and password, then click &amp;quot;Login&amp;quot;.&lt;br /&gt;
*From the dropdown list of devices, choose the Web Orbiter you would like to use and click or touch &#039;Open&#039;. If you have got several web orbiters in your system then they will be displayed in the dropdown and you can choose which one to use. (only one user can use any Web Orbiter at a given time)&lt;br /&gt;
*A page that looks similar to this should appear: [[Image:Web Orbiter.jpg|center]]&lt;br /&gt;
*Here is another UI1 variation loaded into Web Orbiter 2.0: [[Image:web_orbiter_20_in_chrome1.jpg|center]]&lt;br /&gt;
*This image is of Web Orbiter 2.0 running on an iPod Touch: [[Image:Web orbiter on iPod Touch4.JPG|center]]&lt;br /&gt;
&lt;br /&gt;
==Where is the Web Orbiter code on my system?==&lt;br /&gt;
&lt;br /&gt;
===Look in the following directories on your Core===&lt;br /&gt;
&lt;br /&gt;
Look in;&lt;br /&gt;
 /var/www/lmce-admin/&lt;br /&gt;
&lt;br /&gt;
You will see the following Web Orbiter related files (there are many other unrelated files in this directory too);&lt;br /&gt;
&lt;br /&gt;
 weborbiter_command.php&lt;br /&gt;
 weborbiter_image.php&lt;br /&gt;
 weborbiter.php&lt;br /&gt;
&lt;br /&gt;
Look in;&lt;br /&gt;
 /var/www/lmce-admin/weborbiter&lt;br /&gt;
&lt;br /&gt;
You should see the following files;&lt;br /&gt;
&lt;br /&gt;
 IT.php         &lt;br /&gt;
 jquery.min.js  &lt;br /&gt;
 jquery.timers.js&lt;br /&gt;
 login.html&lt;br /&gt;
 waiting.gif&lt;br /&gt;
 weborbiter.css&lt;br /&gt;
 weborbiter.html&lt;br /&gt;
 weborbiter.js&lt;br /&gt;
 weborbiter_select.html&lt;br /&gt;
&lt;br /&gt;
==Devices that have been tested with Web orbiter 2.0==&lt;br /&gt;
This is a simple list of devices that have been tested with Web Orbiter 2.0. If you have got a new device to add to this list then please add it below...or if you have some experiences with a device already listed then please add some simple notes here too.&lt;br /&gt;
&lt;br /&gt;
===Ipad===&lt;br /&gt;
&lt;br /&gt;
===iPod===&lt;br /&gt;
&lt;br /&gt;
===iPhone 3GS===&lt;br /&gt;
&lt;br /&gt;
===iPhone 4===&lt;br /&gt;
&lt;br /&gt;
===HTC Hero (Android 1.6)===&lt;br /&gt;
&lt;br /&gt;
===HTC Desire (Android 2.1)===&lt;br /&gt;
Screen size is a little bit small I think, it is difficult to hit the up/down keys. &lt;br /&gt;
&lt;br /&gt;
===Nokia N800===&lt;br /&gt;
&lt;br /&gt;
===Nokia N900===&lt;br /&gt;
&lt;br /&gt;
==Web Orbiter 2.0 has been tested on the following browsers==&lt;br /&gt;
&lt;br /&gt;
===Firefox 3.6===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
===Chrome 6.0.453.1 dev===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
Also works fine as a chrome application shortcut.&lt;br /&gt;
Just create the shortcut when you are logged into the orbiter and have the right device chosen.&lt;br /&gt;
&lt;br /&gt;
===OperaMini===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
===OperaMobile 10===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
===Midori 0.2.2===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
===Internet Explorer===&lt;br /&gt;
Not working due to javascript issues.&lt;br /&gt;
&lt;br /&gt;
==Troubleshooting==&lt;br /&gt;
===Connect failed===&lt;br /&gt;
If you try to connect to the Web Orbiter and see this message:&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;quot;Connect to proxy orbiter failed, please try again&amp;quot;&amp;lt;/code&amp;gt;, &lt;br /&gt;
this means that Orbiter generation hasn&#039;t finished yet, or that you forgot to do a [[Quick_reload_router|quick restart of the router]].&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Web_Orbiter_2.0&amp;diff=24581</id>
		<title>Web Orbiter 2.0</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Web_Orbiter_2.0&amp;diff=24581"/>
		<updated>2010-07-21T14:05:21Z</updated>

		<summary type="html">&lt;p&gt;Viking: /* Google Nexus One or HTC Desire (Android) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{versioninfo}}&lt;br /&gt;
{| align=&amp;quot;right&amp;quot;&lt;br /&gt;
  | __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
[[Category: Orbiters]]&lt;br /&gt;
[[Category: Tutorials]]&lt;br /&gt;
&lt;br /&gt;
A Web Orbiter is any device (such as a iPhone, iPod Touch, iPad, laptop, PC, etc.) that accesses the Orbiter user interface (UI) through a Web browser.&lt;br /&gt;
&lt;br /&gt;
The new Web Orbiter 2.0 has been re-written from the ground up to make sure it has a much smoother performance overall but especially on slower lower powered devices and devices that are connected over slow LAN connections or even slower external connections...such as a Mobile 3G network or slow WiFi connection.&lt;br /&gt;
&lt;br /&gt;
So what has changed? Well visually your Orbiter UI will look like it does on your existing standard Orbiters but you will notice that unlike the original Web Orbiter the new 2.0 version does not refresh every 5 secs. The new Web Orbiter now only updates if something changes in the system and that requires the UI screen you are currently viewing to be updated or if you click on a UI button or other UI element and that causes a screen update. &lt;br /&gt;
&lt;br /&gt;
To achieve this the proxy_orbiter has been updated so that it sets a flag called &#039;ANYNEWS&#039; to &#039;true&#039; if some element of the current displayed screen has been updated. The Web Orbiter makes a light weight call to query the state of this flag once every second and only gets an updated UI screen if the flag is set to &#039;true&#039; otherwise no screen update is requested. So in use the new Web Orbiter 2.0 behaves in a very similar fashion to the Orbiter on one of your MD&#039;s - and now it even performs with a similar performance level too.&lt;br /&gt;
&lt;br /&gt;
Whats a proxy_orbiter? Proxy_orbiter runs on the Core and its job is to render the UI for the Web Orbiter that is running remotely on some other device. Each Web Orbiter has an associated proxy_orbiter and the two work in partnership. Proxy_orbiters do all the &#039;heavy lifting&#039; rendering the UI and this allows the remote device that is running the Web Orbiter to be much less powerful and very simple devices indeed if needed.&lt;br /&gt;
&lt;br /&gt;
Another change in the new 2.0 Web Orbiter is that screen refreshes are double buffered so that the new Web Orbiter receives the new screen update from your Core in the background and only redraws the screen when it has the complete image stored in memory - this makes the update process smoother and faster.&lt;br /&gt;
&lt;br /&gt;
The overall effect of all these changes is to vastly improve the performance and usability while at the same time reducing the processing overhead of the Web Orbiter massively.&lt;br /&gt;
&lt;br /&gt;
== Setup ==&lt;br /&gt;
The procedure to setup a Web Orbiter is simple but the order of steps is important.&lt;br /&gt;
#First of all, add a new Generic Web Device as a Child Device for your Core:&lt;br /&gt;
##Goto the LinuxMCE Admin website--&amp;gt;Show devices tree--&amp;gt;CORE. The CORE&#039;s detail page should appear.&lt;br /&gt;
##Click &#039;Create Child Device&#039;.&lt;br /&gt;
##In the Description, enter the name of the specific web orbiter.&lt;br /&gt;
##In the Add child device window, click the button &#039;Pick device template&#039;. The new pop-up window containing device templates will be opened.&lt;br /&gt;
##In the &#039;Device Category&#039; dropdown list, choose &#039;Peripherals&#039;.&lt;br /&gt;
##In the &#039;Device Template&#039; dropdown list, find and select &amp;quot;Generic Web Device&amp;quot; (or just type the template id: 1748 and press go).&lt;br /&gt;
##Click the button &#039;Pick Device Template&#039;. 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.&lt;br /&gt;
##A new Generic Proxy Orbiter will also be created automatically. Watch the Orbiter generation process on the Orbiters page: Wizard--&amp;gt;Devices--&amp;gt;Orbiters.&lt;br /&gt;
#Wait till the Orbiter generation procedure finishes. A message on an active Orbiter or on the Orbiter page will indicate when it has completed.&lt;br /&gt;
#Set the appropriate screen resolution to suit the device your Web Orbiter is intended for from the &#039;Size&#039; drop down&lt;br /&gt;
#Set the &#039;Skin&#039; drop down to the skin you want to use (normally this would mean the UI1 Standard Variation or a derivative)&lt;br /&gt;
#Click on your new Generic Proxy Orbiter in the device tree, give it a unique name and then scroll to the bottom of the page on the right and look for the field called &#039;Listen Port&#039;. This field will be set to &#039;3461&#039; by default (if this Web Orbiter is not your first then you should increment this value by one ie to &#039;3462&#039; - each Web Orbiter must have a unique &#039;Listen Port&#039; number)&lt;br /&gt;
#Now click the &#039;Save&#039; button at the bottom of the screen to save the changes you have made.&lt;br /&gt;
#Now do a &#039;Full Regen&#039; from the &#039;Wizard - Orbiters&#039; page (use the &#039;Full Regen&#039; for the specific Web Orbiter you have created and not the overall &#039;Full Regen&#039; button at the top of the page). Next when the Regen has completed do a &amp;quot;[[Quick reload router]]&amp;quot;. Otherwise, the Web Orbiter won&#039;t work properly.&lt;br /&gt;
&lt;br /&gt;
==Device Screen Resolutions==&lt;br /&gt;
If the &#039;Device&#039; your planning to use your Web Orbiter on is a Desktop or Laptop then use the biggest resolution that will comfortably fit onto your screen. If your device is a touch screen device like an iPad, iPhone or iPod Touch then choose a resoltion that matches the overall resolution of the devices display;&lt;br /&gt;
&lt;br /&gt;
===iPad===&lt;br /&gt;
The iPad has a screen resolution of 1024x768 so if your creating an Orbiter for the iPad this is the resolution you should select for this Web Orbiter.&lt;br /&gt;
&lt;br /&gt;
===iPhone (pre iPhone 4) or iPad Touch===&lt;br /&gt;
The iPhone/iPod Touch hav a screen resolution of 480x320 so if your creating an Orbiter for either of these this is the resolution you should select for this Web Orbiter.&lt;br /&gt;
&lt;br /&gt;
===iPhone 4===&lt;br /&gt;
The iPhone 4 has a screen resolution of 960x640 so if your creating an Orbiter for the iPhone 4 this is the resolution you should select for this Web Orbiter.&lt;br /&gt;
&lt;br /&gt;
===Google Nexus One or HTC Desire (Android)===&lt;br /&gt;
If you have a Nexus One you will need to select a resolution of 480x800 (select N770 in the web admin, it is 480x800) so if your creating an Orbiter for the Nexus One this is the resolution you should select for this Web Orbiter.&lt;br /&gt;
&lt;br /&gt;
On the HTC Desire you might also have to go into the web browser settings and change the default zoom to &amp;quot;far away&amp;quot; (mine is danish, so don&#039;t know the exact english decription). After that it should be full screen.&lt;br /&gt;
&lt;br /&gt;
==Access to the Web Orbiter==&lt;br /&gt;
&lt;br /&gt;
===From within your home===&lt;br /&gt;
You can access the Web Orbiter 2.0 from any of the following Web browsers (Google Chrome, Mozilla Firefox, Safari). Others may also work but have not been tested (your experiences with other web browsers would be welcome here) :&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;For the 810 releases the correct URL is:&#039;&#039;&#039;&lt;br /&gt;
&#039;&#039;&amp;lt;nowiki&amp;gt;http://&amp;amp;lt;core_ip&amp;amp;gt;/lmce-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:* From within the &amp;quot;internal&amp;quot; LinuxMCE LAN, for example: &lt;br /&gt;
::::&#039;&#039;http://192.168.80.1/lmce-admin/weborbiter.php&#039;&#039; (0810)&lt;br /&gt;
:::::(This assumes the IP address range set by default at installation.)&lt;br /&gt;
:*You can also use the network name of the Core in place of the IP address. For example, if the Core was named &amp;quot;dcerouter&amp;quot; during the default installation, you could use:&lt;br /&gt;
::::&#039;&#039;&amp;lt;nowiki&amp;gt;http://dcerouter/pluto-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
:*From the &amp;quot;external&amp;quot; WAN side of the Core, the core_ip would be the WAN IP address of the core (ie the one offered to the WAN side NIC on the Core by your broadband Router). If, for example, the core has a WAN side address of 192.168.0.50 offered up by your Broadband Router, use:&lt;br /&gt;
:::: &#039;&#039;&amp;lt;nowiki&amp;gt;http://192.168.0.50/lmce-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:::::(Note: To use this method, [[Outside Access]] must be enabled.)&lt;br /&gt;
&lt;br /&gt;
===From the Internet===&lt;br /&gt;
You could use the IP address:port for your home LAN, with port forwarding to the Core&#039;s LAN IP address (enabled by your home LAN router). &lt;br /&gt;
*&#039;&#039;This is an advanced topic and may not be secure in the current version.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
By default, LinuxMCE is not accessible outside your home. This makes the system secure, but it prevents you from accessing the web site via the Internet while away from home.  You can [[Outside_Access|turn on Internet access]], allowing access to the admin website anywhere. For your own security, however, we recommend you first read about [[Security &amp;amp; Privacy Issues]].&lt;br /&gt;
&lt;br /&gt;
===Login page===&lt;br /&gt;
*A simple login page should be displayed. Input an existing user name and password, then click &amp;quot;Login&amp;quot;.&lt;br /&gt;
*From the dropdown list of devices, choose the Web Orbiter you would like to use and click or touch &#039;Open&#039;. If you have got several web orbiters in your system then they will be displayed in the dropdown and you can choose which one to use. (only one user can use any Web Orbiter at a given time)&lt;br /&gt;
*A page that looks similar to this should appear: [[Image:Web Orbiter.jpg|center]]&lt;br /&gt;
*Here is another UI1 variation loaded into Web Orbiter 2.0: [[Image:web_orbiter_20_in_chrome1.jpg|center]]&lt;br /&gt;
*This image is of Web Orbiter 2.0 running on an iPod Touch: [[Image:Web orbiter on iPod Touch4.JPG|center]]&lt;br /&gt;
&lt;br /&gt;
==Where is the Web Orbiter code on my system?==&lt;br /&gt;
&lt;br /&gt;
===Look in the following directories on your Core===&lt;br /&gt;
&lt;br /&gt;
Look in;&lt;br /&gt;
 /var/www/lmce-admin/&lt;br /&gt;
&lt;br /&gt;
You will see the following Web Orbiter related files (there are many other unrelated files in this directory too);&lt;br /&gt;
&lt;br /&gt;
 weborbiter_command.php&lt;br /&gt;
 weborbiter_image.php&lt;br /&gt;
 weborbiter.php&lt;br /&gt;
&lt;br /&gt;
Look in;&lt;br /&gt;
 /var/www/lmce-admin/weborbiter&lt;br /&gt;
&lt;br /&gt;
You should see the following files;&lt;br /&gt;
&lt;br /&gt;
 IT.php         &lt;br /&gt;
 jquery.min.js  &lt;br /&gt;
 jquery.timers.js&lt;br /&gt;
 login.html&lt;br /&gt;
 waiting.gif&lt;br /&gt;
 weborbiter.css&lt;br /&gt;
 weborbiter.html&lt;br /&gt;
 weborbiter.js&lt;br /&gt;
 weborbiter_select.html&lt;br /&gt;
&lt;br /&gt;
==Devices that have been tested with Web orbiter 2.0==&lt;br /&gt;
This is a simple list of devices that have been tested with Web Orbiter 2.0. If you have got a new device to add to this list then please add it below...or if you have some experiences with a device already listed then please add some simple notes here too.&lt;br /&gt;
&lt;br /&gt;
===Ipad===&lt;br /&gt;
&lt;br /&gt;
===iPod===&lt;br /&gt;
&lt;br /&gt;
===iPhone 3GS===&lt;br /&gt;
&lt;br /&gt;
===iPhone 4===&lt;br /&gt;
&lt;br /&gt;
===HTC Hero (Android 1.6)===&lt;br /&gt;
&lt;br /&gt;
===Nokia N800===&lt;br /&gt;
&lt;br /&gt;
===Nokia N900===&lt;br /&gt;
&lt;br /&gt;
==Web Orbiter 2.0 has been tested on the following browsers==&lt;br /&gt;
&lt;br /&gt;
===Firefox 3.6===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
===Chrome 6.0.453.1 dev===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
Also works fine as a chrome application shortcut.&lt;br /&gt;
Just create the shortcut when you are logged into the orbiter and have the right device chosen.&lt;br /&gt;
&lt;br /&gt;
===OperaMini===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
===OperaMobile 10===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
===Midori 0.2.2===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
===Internet Explorer===&lt;br /&gt;
Not working due to javascript issues.&lt;br /&gt;
&lt;br /&gt;
==Troubleshooting==&lt;br /&gt;
===Connect failed===&lt;br /&gt;
If you try to connect to the Web Orbiter and see this message:&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;quot;Connect to proxy orbiter failed, please try again&amp;quot;&amp;lt;/code&amp;gt;, &lt;br /&gt;
this means that Orbiter generation hasn&#039;t finished yet, or that you forgot to do a [[Quick_reload_router|quick restart of the router]].&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Web_Orbiter_2.0&amp;diff=24580</id>
		<title>Web Orbiter 2.0</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Web_Orbiter_2.0&amp;diff=24580"/>
		<updated>2010-07-21T14:03:11Z</updated>

		<summary type="html">&lt;p&gt;Viking: /* Device Screen Resolutions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{versioninfo}}&lt;br /&gt;
{| align=&amp;quot;right&amp;quot;&lt;br /&gt;
  | __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
[[Category: Orbiters]]&lt;br /&gt;
[[Category: Tutorials]]&lt;br /&gt;
&lt;br /&gt;
A Web Orbiter is any device (such as a iPhone, iPod Touch, iPad, laptop, PC, etc.) that accesses the Orbiter user interface (UI) through a Web browser.&lt;br /&gt;
&lt;br /&gt;
The new Web Orbiter 2.0 has been re-written from the ground up to make sure it has a much smoother performance overall but especially on slower lower powered devices and devices that are connected over slow LAN connections or even slower external connections...such as a Mobile 3G network or slow WiFi connection.&lt;br /&gt;
&lt;br /&gt;
So what has changed? Well visually your Orbiter UI will look like it does on your existing standard Orbiters but you will notice that unlike the original Web Orbiter the new 2.0 version does not refresh every 5 secs. The new Web Orbiter now only updates if something changes in the system and that requires the UI screen you are currently viewing to be updated or if you click on a UI button or other UI element and that causes a screen update. &lt;br /&gt;
&lt;br /&gt;
To achieve this the proxy_orbiter has been updated so that it sets a flag called &#039;ANYNEWS&#039; to &#039;true&#039; if some element of the current displayed screen has been updated. The Web Orbiter makes a light weight call to query the state of this flag once every second and only gets an updated UI screen if the flag is set to &#039;true&#039; otherwise no screen update is requested. So in use the new Web Orbiter 2.0 behaves in a very similar fashion to the Orbiter on one of your MD&#039;s - and now it even performs with a similar performance level too.&lt;br /&gt;
&lt;br /&gt;
Whats a proxy_orbiter? Proxy_orbiter runs on the Core and its job is to render the UI for the Web Orbiter that is running remotely on some other device. Each Web Orbiter has an associated proxy_orbiter and the two work in partnership. Proxy_orbiters do all the &#039;heavy lifting&#039; rendering the UI and this allows the remote device that is running the Web Orbiter to be much less powerful and very simple devices indeed if needed.&lt;br /&gt;
&lt;br /&gt;
Another change in the new 2.0 Web Orbiter is that screen refreshes are double buffered so that the new Web Orbiter receives the new screen update from your Core in the background and only redraws the screen when it has the complete image stored in memory - this makes the update process smoother and faster.&lt;br /&gt;
&lt;br /&gt;
The overall effect of all these changes is to vastly improve the performance and usability while at the same time reducing the processing overhead of the Web Orbiter massively.&lt;br /&gt;
&lt;br /&gt;
== Setup ==&lt;br /&gt;
The procedure to setup a Web Orbiter is simple but the order of steps is important.&lt;br /&gt;
#First of all, add a new Generic Web Device as a Child Device for your Core:&lt;br /&gt;
##Goto the LinuxMCE Admin website--&amp;gt;Show devices tree--&amp;gt;CORE. The CORE&#039;s detail page should appear.&lt;br /&gt;
##Click &#039;Create Child Device&#039;.&lt;br /&gt;
##In the Description, enter the name of the specific web orbiter.&lt;br /&gt;
##In the Add child device window, click the button &#039;Pick device template&#039;. The new pop-up window containing device templates will be opened.&lt;br /&gt;
##In the &#039;Device Category&#039; dropdown list, choose &#039;Peripherals&#039;.&lt;br /&gt;
##In the &#039;Device Template&#039; dropdown list, find and select &amp;quot;Generic Web Device&amp;quot; (or just type the template id: 1748 and press go).&lt;br /&gt;
##Click the button &#039;Pick Device Template&#039;. 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.&lt;br /&gt;
##A new Generic Proxy Orbiter will also be created automatically. Watch the Orbiter generation process on the Orbiters page: Wizard--&amp;gt;Devices--&amp;gt;Orbiters.&lt;br /&gt;
#Wait till the Orbiter generation procedure finishes. A message on an active Orbiter or on the Orbiter page will indicate when it has completed.&lt;br /&gt;
#Set the appropriate screen resolution to suit the device your Web Orbiter is intended for from the &#039;Size&#039; drop down&lt;br /&gt;
#Set the &#039;Skin&#039; drop down to the skin you want to use (normally this would mean the UI1 Standard Variation or a derivative)&lt;br /&gt;
#Click on your new Generic Proxy Orbiter in the device tree, give it a unique name and then scroll to the bottom of the page on the right and look for the field called &#039;Listen Port&#039;. This field will be set to &#039;3461&#039; by default (if this Web Orbiter is not your first then you should increment this value by one ie to &#039;3462&#039; - each Web Orbiter must have a unique &#039;Listen Port&#039; number)&lt;br /&gt;
#Now click the &#039;Save&#039; button at the bottom of the screen to save the changes you have made.&lt;br /&gt;
#Now do a &#039;Full Regen&#039; from the &#039;Wizard - Orbiters&#039; page (use the &#039;Full Regen&#039; for the specific Web Orbiter you have created and not the overall &#039;Full Regen&#039; button at the top of the page). Next when the Regen has completed do a &amp;quot;[[Quick reload router]]&amp;quot;. Otherwise, the Web Orbiter won&#039;t work properly.&lt;br /&gt;
&lt;br /&gt;
==Device Screen Resolutions==&lt;br /&gt;
If the &#039;Device&#039; your planning to use your Web Orbiter on is a Desktop or Laptop then use the biggest resolution that will comfortably fit onto your screen. If your device is a touch screen device like an iPad, iPhone or iPod Touch then choose a resoltion that matches the overall resolution of the devices display;&lt;br /&gt;
&lt;br /&gt;
===iPad===&lt;br /&gt;
The iPad has a screen resolution of 1024x768 so if your creating an Orbiter for the iPad this is the resolution you should select for this Web Orbiter.&lt;br /&gt;
&lt;br /&gt;
===iPhone (pre iPhone 4) or iPad Touch===&lt;br /&gt;
The iPhone/iPod Touch hav a screen resolution of 480x320 so if your creating an Orbiter for either of these this is the resolution you should select for this Web Orbiter.&lt;br /&gt;
&lt;br /&gt;
===iPhone 4===&lt;br /&gt;
The iPhone 4 has a screen resolution of 960x640 so if your creating an Orbiter for the iPhone 4 this is the resolution you should select for this Web Orbiter.&lt;br /&gt;
&lt;br /&gt;
===Google Nexus One or HTC Desire (Android)===&lt;br /&gt;
If you have a Nexus One you will need to select a resolution of 480x800 (select N770 in the web admin, it is 480x800) so if your creating an Orbiter for the Nexus One this is the resolution you should select for this Web Orbiter.&lt;br /&gt;
&lt;br /&gt;
==Access to the Web Orbiter==&lt;br /&gt;
&lt;br /&gt;
===From within your home===&lt;br /&gt;
You can access the Web Orbiter 2.0 from any of the following Web browsers (Google Chrome, Mozilla Firefox, Safari). Others may also work but have not been tested (your experiences with other web browsers would be welcome here) :&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;For the 810 releases the correct URL is:&#039;&#039;&#039;&lt;br /&gt;
&#039;&#039;&amp;lt;nowiki&amp;gt;http://&amp;amp;lt;core_ip&amp;amp;gt;/lmce-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:* From within the &amp;quot;internal&amp;quot; LinuxMCE LAN, for example: &lt;br /&gt;
::::&#039;&#039;http://192.168.80.1/lmce-admin/weborbiter.php&#039;&#039; (0810)&lt;br /&gt;
:::::(This assumes the IP address range set by default at installation.)&lt;br /&gt;
:*You can also use the network name of the Core in place of the IP address. For example, if the Core was named &amp;quot;dcerouter&amp;quot; during the default installation, you could use:&lt;br /&gt;
::::&#039;&#039;&amp;lt;nowiki&amp;gt;http://dcerouter/pluto-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
:*From the &amp;quot;external&amp;quot; WAN side of the Core, the core_ip would be the WAN IP address of the core (ie the one offered to the WAN side NIC on the Core by your broadband Router). If, for example, the core has a WAN side address of 192.168.0.50 offered up by your Broadband Router, use:&lt;br /&gt;
:::: &#039;&#039;&amp;lt;nowiki&amp;gt;http://192.168.0.50/lmce-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:::::(Note: To use this method, [[Outside Access]] must be enabled.)&lt;br /&gt;
&lt;br /&gt;
===From the Internet===&lt;br /&gt;
You could use the IP address:port for your home LAN, with port forwarding to the Core&#039;s LAN IP address (enabled by your home LAN router). &lt;br /&gt;
*&#039;&#039;This is an advanced topic and may not be secure in the current version.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
By default, LinuxMCE is not accessible outside your home. This makes the system secure, but it prevents you from accessing the web site via the Internet while away from home.  You can [[Outside_Access|turn on Internet access]], allowing access to the admin website anywhere. For your own security, however, we recommend you first read about [[Security &amp;amp; Privacy Issues]].&lt;br /&gt;
&lt;br /&gt;
===Login page===&lt;br /&gt;
*A simple login page should be displayed. Input an existing user name and password, then click &amp;quot;Login&amp;quot;.&lt;br /&gt;
*From the dropdown list of devices, choose the Web Orbiter you would like to use and click or touch &#039;Open&#039;. If you have got several web orbiters in your system then they will be displayed in the dropdown and you can choose which one to use. (only one user can use any Web Orbiter at a given time)&lt;br /&gt;
*A page that looks similar to this should appear: [[Image:Web Orbiter.jpg|center]]&lt;br /&gt;
*Here is another UI1 variation loaded into Web Orbiter 2.0: [[Image:web_orbiter_20_in_chrome1.jpg|center]]&lt;br /&gt;
*This image is of Web Orbiter 2.0 running on an iPod Touch: [[Image:Web orbiter on iPod Touch4.JPG|center]]&lt;br /&gt;
&lt;br /&gt;
==Where is the Web Orbiter code on my system?==&lt;br /&gt;
&lt;br /&gt;
===Look in the following directories on your Core===&lt;br /&gt;
&lt;br /&gt;
Look in;&lt;br /&gt;
 /var/www/lmce-admin/&lt;br /&gt;
&lt;br /&gt;
You will see the following Web Orbiter related files (there are many other unrelated files in this directory too);&lt;br /&gt;
&lt;br /&gt;
 weborbiter_command.php&lt;br /&gt;
 weborbiter_image.php&lt;br /&gt;
 weborbiter.php&lt;br /&gt;
&lt;br /&gt;
Look in;&lt;br /&gt;
 /var/www/lmce-admin/weborbiter&lt;br /&gt;
&lt;br /&gt;
You should see the following files;&lt;br /&gt;
&lt;br /&gt;
 IT.php         &lt;br /&gt;
 jquery.min.js  &lt;br /&gt;
 jquery.timers.js&lt;br /&gt;
 login.html&lt;br /&gt;
 waiting.gif&lt;br /&gt;
 weborbiter.css&lt;br /&gt;
 weborbiter.html&lt;br /&gt;
 weborbiter.js&lt;br /&gt;
 weborbiter_select.html&lt;br /&gt;
&lt;br /&gt;
==Devices that have been tested with Web orbiter 2.0==&lt;br /&gt;
This is a simple list of devices that have been tested with Web Orbiter 2.0. If you have got a new device to add to this list then please add it below...or if you have some experiences with a device already listed then please add some simple notes here too.&lt;br /&gt;
&lt;br /&gt;
===Ipad===&lt;br /&gt;
&lt;br /&gt;
===iPod===&lt;br /&gt;
&lt;br /&gt;
===iPhone 3GS===&lt;br /&gt;
&lt;br /&gt;
===iPhone 4===&lt;br /&gt;
&lt;br /&gt;
===HTC Hero (Android 1.6)===&lt;br /&gt;
&lt;br /&gt;
===Nokia N800===&lt;br /&gt;
&lt;br /&gt;
===Nokia N900===&lt;br /&gt;
&lt;br /&gt;
==Web Orbiter 2.0 has been tested on the following browsers==&lt;br /&gt;
&lt;br /&gt;
===Firefox 3.6===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
===Chrome 6.0.453.1 dev===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
Also works fine as a chrome application shortcut.&lt;br /&gt;
Just create the shortcut when you are logged into the orbiter and have the right device chosen.&lt;br /&gt;
&lt;br /&gt;
===OperaMini===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
===OperaMobile 10===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
===Midori 0.2.2===&lt;br /&gt;
Works fine.&lt;br /&gt;
&lt;br /&gt;
===Internet Explorer===&lt;br /&gt;
Not working due to javascript issues.&lt;br /&gt;
&lt;br /&gt;
==Troubleshooting==&lt;br /&gt;
===Connect failed===&lt;br /&gt;
If you try to connect to the Web Orbiter and see this message:&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;quot;Connect to proxy orbiter failed, please try again&amp;quot;&amp;lt;/code&amp;gt;, &lt;br /&gt;
this means that Orbiter generation hasn&#039;t finished yet, or that you forgot to do a [[Quick_reload_router|quick restart of the router]].&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Web_Orbiter_2.0&amp;diff=24300</id>
		<title>Web Orbiter 2.0</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Web_Orbiter_2.0&amp;diff=24300"/>
		<updated>2010-07-07T15:36:21Z</updated>

		<summary type="html">&lt;p&gt;Viking: /* Login page */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{versioninfo}}&lt;br /&gt;
{| align=&amp;quot;right&amp;quot;&lt;br /&gt;
  | __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
[[Category: Orbiters]]&lt;br /&gt;
[[Category: Tutorials]]&lt;br /&gt;
&lt;br /&gt;
A Web Orbiter is any device (such as a iPhone, iPod Touch, iPad, laptop, PC, etc.) that accesses the Orbiter user interface (UI) through a Web browser.&lt;br /&gt;
&lt;br /&gt;
The new Web Orbiter 2.0 has been re-written from the ground up to make sure it has a much smoother performance overall but especially on slower lower powered devices and devices that are connected over slow LAN connections or even slower external connections...such as a Mobile 3G network or slow WiFi connection.&lt;br /&gt;
&lt;br /&gt;
So what has changed? Well visually your Orbiter UI will look like it does on your existing standard Orbiters but you will notice that unlike the original Web Orbiter the new 2.0 version does not refresh every 5 secs. The new Web Orbiter now only updates if something changes in the system and that requires the UI screen you are currently viewing to be updated or if you click on a UI button or other UI element and that causes a screen update. &lt;br /&gt;
&lt;br /&gt;
Proxy_orbiter runs on the Core and its job is to render the UI for the Web Orbiter that is running remotely on some other device. Each Web Orbiter has an associated proxy_orbiter and the two work in partnership. Proxy_orbiters do all the &#039;heavy lifting&#039; rendering the UI and this allows the remote device that is running the Web Orbiter to be much less powerful and very simple devices indeed if needed.&lt;br /&gt;
&lt;br /&gt;
To achieve this the proxy_orbiter has been updated so that it sets a flag called &#039;ANYNEWS&#039; to &#039;true&#039; if some element of the current displayed screen has been updated. The Web Orbiter makes a light weight call to query the state of this flag once every second and only gets an updated UI screen if the flag is set to &#039;true&#039; otherwise no screen update is requested. So in use the new Web Orbiter 2.0 behaves in a very similar fashion to the Orbiter on one of your MD&#039;s - and now it even performs with a similar performance level too.&lt;br /&gt;
&lt;br /&gt;
Another change in the new 2.0 Web Orbiter is that screen refreshes are double buffered so that the new Web Orbiter receives the new screen update from your Core in the background and only redraws the screen when it has the complete image stored in memory - this makes the update process smoother and faster.&lt;br /&gt;
&lt;br /&gt;
The overall effect of all these changes is to vastly improve the performance and usability while at the same time reducing the processing overhead of the Web Orbiter massively.&lt;br /&gt;
&lt;br /&gt;
== Setup ==&lt;br /&gt;
The procedure to setup a Web Orbiter is simple but the order of steps is important.&lt;br /&gt;
#First of all, add a new Generic Web Device as a Child Device for your Core:&lt;br /&gt;
##Goto the LinuxMCE Admin website--&amp;gt;Show devices tree--&amp;gt;CORE. The CORE&#039;s detail page should appear.&lt;br /&gt;
##Click &#039;Create Child Device&#039;.&lt;br /&gt;
##In the Description, enter the name of the specific web orbiter.&lt;br /&gt;
##In the Add child device window, click the button &#039;Pick device template&#039;. The new pop-up window containing device templates will be opened.&lt;br /&gt;
##In the &#039;Device Category&#039; dropdown list, choose &#039;Peripherals&#039;.&lt;br /&gt;
##In the &#039;Device Template&#039; dropdown list, find and select &amp;quot;Generic Web Device&amp;quot; (or just type the template id: 1748 and press go).&lt;br /&gt;
##Click the button &#039;Pick Device Template&#039;. 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.&lt;br /&gt;
##A new Generic Proxy Orbiter will also be created automatically. Watch the Orbiter generation process on the Orbiters page: Wizard--&amp;gt;Devices--&amp;gt;Orbiters.&lt;br /&gt;
#Wait till the Orbiter generation procedure finishes. A message on an active Orbiter or on the Orbiter page will indicate when it has completed.&lt;br /&gt;
#Click on your new Generic Proxy Orbiter in the device tree and then scroll to the bottom of the page on the right and look for the field called &#039;Listen Port&#039;. This field will be set to &#039;3461&#039; by default (if this Web Orbiter is not your first then you should increment this value by one ie to &#039;3462&#039; - each Web Orbiter must have a unique &#039;Listen Port&#039;)&lt;br /&gt;
#Now click the &#039;Save&#039; button at the bottom of the screen to save the changes you have made.&lt;br /&gt;
#Now do a &#039;Full Regen&#039; from the &#039;Wizard - Orbiters&#039; page (use the &#039;Full Regen&#039; for the specific Web Orbiter you have created and not the overall &#039;Full Regen&#039; button at the top of the page. Next when the Regen has completed do a &amp;quot;[[Quick reload router]]&amp;quot;. Otherwise, the Orbiter won&#039;t work properly.&lt;br /&gt;
&lt;br /&gt;
==Access to the Web Orbiter==&lt;br /&gt;
&lt;br /&gt;
===From within your home===&lt;br /&gt;
You can access the Web Orbiter 2.0 from any of the following Web browsers (Google Chrome, Mozilla Firefox, Safari). Others may also work but have not been tested (your experiences with other web browsers would be welcome here) :&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;For the 810 releases the correct URL is:&#039;&#039;&#039;&lt;br /&gt;
&#039;&#039;&amp;lt;nowiki&amp;gt;http://&amp;amp;lt;core_ip&amp;amp;gt;/lmce-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:* From within the &amp;quot;internal&amp;quot; LinuxMCE LAN, for example: &lt;br /&gt;
::::&#039;&#039;http://192.168.80.1/lmce-admin/weborbiter.php&#039;&#039; (0810)&lt;br /&gt;
:::::(This assumes the IP address range set by default at installation.)&lt;br /&gt;
:*You can also use the network name of the Core in place of the IP address. For example, if the Core was named &amp;quot;dcerouter&amp;quot; during the default installation, you could use:&lt;br /&gt;
::::&#039;&#039;&amp;lt;nowiki&amp;gt;http://dcerouter/pluto-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
:*From the &amp;quot;external&amp;quot; WAN side of the Core, the core_ip would be the WAN IP address of the core (ie the one offered to the WAN side NIC on the Core by your broadband Router). If, for example, the core has a WAN side address of 192.168.0.50 offered up by your Broadband Router, use:&lt;br /&gt;
:::: &#039;&#039;&amp;lt;nowiki&amp;gt;http://192.168.0.50/lmce-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:::::(Note: To use this method, [[Outside Access]] must be enabled.)&lt;br /&gt;
&lt;br /&gt;
===From the Internet===&lt;br /&gt;
You could use the IP address:port for your home LAN, with port forwarding to the Core&#039;s LAN IP address (enabled by your home LAN router). &lt;br /&gt;
*&#039;&#039;This is an advanced topic and may not be secure in the current version.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
By default, LinuxMCE is not accessible outside your home. This makes the system secure, but it prevents you from accessing the web site via the Internet while away from home.  You can [[Outside_Access|turn on Internet access]], allowing access to the admin website anywhere. For your own security, however, we recommend you first read about [[Security &amp;amp; Privacy Issues]].&lt;br /&gt;
&lt;br /&gt;
===Login page===&lt;br /&gt;
*A simple login page should be displayed. Input an existing user name and password, then click &amp;quot;Login&amp;quot;.&lt;br /&gt;
*From the dropdown list of devices, choose Generic Web Device. If you have got several web orbiters defined, this is the place you can choose between them.&lt;br /&gt;
*A page that looks similar to this should appear: [[Image:Web Orbiter.jpg|center]]&lt;br /&gt;
&lt;br /&gt;
==Troubleshooting==&lt;br /&gt;
===Connect failed===&lt;br /&gt;
If you try to connect to the Web Orbiter and see this message:&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;quot;Connect to proxy orbiter failed, please try again&amp;quot;&amp;lt;/code&amp;gt;, &lt;br /&gt;
this means that Orbiter generation hasn&#039;t finished yet, or that you forgot to do a [[Quick_reload_router|quick restart of the router]].&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Web_Orbiter_2.0&amp;diff=24299</id>
		<title>Web Orbiter 2.0</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Web_Orbiter_2.0&amp;diff=24299"/>
		<updated>2010-07-07T15:35:31Z</updated>

		<summary type="html">&lt;p&gt;Viking: /* From within your home */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{versioninfo}}&lt;br /&gt;
{| align=&amp;quot;right&amp;quot;&lt;br /&gt;
  | __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
[[Category: Orbiters]]&lt;br /&gt;
[[Category: Tutorials]]&lt;br /&gt;
&lt;br /&gt;
A Web Orbiter is any device (such as a iPhone, iPod Touch, iPad, laptop, PC, etc.) that accesses the Orbiter user interface (UI) through a Web browser.&lt;br /&gt;
&lt;br /&gt;
The new Web Orbiter 2.0 has been re-written from the ground up to make sure it has a much smoother performance overall but especially on slower lower powered devices and devices that are connected over slow LAN connections or even slower external connections...such as a Mobile 3G network or slow WiFi connection.&lt;br /&gt;
&lt;br /&gt;
So what has changed? Well visually your Orbiter UI will look like it does on your existing standard Orbiters but you will notice that unlike the original Web Orbiter the new 2.0 version does not refresh every 5 secs. The new Web Orbiter now only updates if something changes in the system and that requires the UI screen you are currently viewing to be updated or if you click on a UI button or other UI element and that causes a screen update. &lt;br /&gt;
&lt;br /&gt;
Proxy_orbiter runs on the Core and its job is to render the UI for the Web Orbiter that is running remotely on some other device. Each Web Orbiter has an associated proxy_orbiter and the two work in partnership. Proxy_orbiters do all the &#039;heavy lifting&#039; rendering the UI and this allows the remote device that is running the Web Orbiter to be much less powerful and very simple devices indeed if needed.&lt;br /&gt;
&lt;br /&gt;
To achieve this the proxy_orbiter has been updated so that it sets a flag called &#039;ANYNEWS&#039; to &#039;true&#039; if some element of the current displayed screen has been updated. The Web Orbiter makes a light weight call to query the state of this flag once every second and only gets an updated UI screen if the flag is set to &#039;true&#039; otherwise no screen update is requested. So in use the new Web Orbiter 2.0 behaves in a very similar fashion to the Orbiter on one of your MD&#039;s - and now it even performs with a similar performance level too.&lt;br /&gt;
&lt;br /&gt;
Another change in the new 2.0 Web Orbiter is that screen refreshes are double buffered so that the new Web Orbiter receives the new screen update from your Core in the background and only redraws the screen when it has the complete image stored in memory - this makes the update process smoother and faster.&lt;br /&gt;
&lt;br /&gt;
The overall effect of all these changes is to vastly improve the performance and usability while at the same time reducing the processing overhead of the Web Orbiter massively.&lt;br /&gt;
&lt;br /&gt;
== Setup ==&lt;br /&gt;
The procedure to setup a Web Orbiter is simple but the order of steps is important.&lt;br /&gt;
#First of all, add a new Generic Web Device as a Child Device for your Core:&lt;br /&gt;
##Goto the LinuxMCE Admin website--&amp;gt;Show devices tree--&amp;gt;CORE. The CORE&#039;s detail page should appear.&lt;br /&gt;
##Click &#039;Create Child Device&#039;.&lt;br /&gt;
##In the Description, enter the name of the specific web orbiter.&lt;br /&gt;
##In the Add child device window, click the button &#039;Pick device template&#039;. The new pop-up window containing device templates will be opened.&lt;br /&gt;
##In the &#039;Device Category&#039; dropdown list, choose &#039;Peripherals&#039;.&lt;br /&gt;
##In the &#039;Device Template&#039; dropdown list, find and select &amp;quot;Generic Web Device&amp;quot; (or just type the template id: 1748 and press go).&lt;br /&gt;
##Click the button &#039;Pick Device Template&#039;. 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.&lt;br /&gt;
##A new Generic Proxy Orbiter will also be created automatically. Watch the Orbiter generation process on the Orbiters page: Wizard--&amp;gt;Devices--&amp;gt;Orbiters.&lt;br /&gt;
#Wait till the Orbiter generation procedure finishes. A message on an active Orbiter or on the Orbiter page will indicate when it has completed.&lt;br /&gt;
#Click on your new Generic Proxy Orbiter in the device tree and then scroll to the bottom of the page on the right and look for the field called &#039;Listen Port&#039;. This field will be set to &#039;3461&#039; by default (if this Web Orbiter is not your first then you should increment this value by one ie to &#039;3462&#039; - each Web Orbiter must have a unique &#039;Listen Port&#039;)&lt;br /&gt;
#Now click the &#039;Save&#039; button at the bottom of the screen to save the changes you have made.&lt;br /&gt;
#Now do a &#039;Full Regen&#039; from the &#039;Wizard - Orbiters&#039; page (use the &#039;Full Regen&#039; for the specific Web Orbiter you have created and not the overall &#039;Full Regen&#039; button at the top of the page. Next when the Regen has completed do a &amp;quot;[[Quick reload router]]&amp;quot;. Otherwise, the Orbiter won&#039;t work properly.&lt;br /&gt;
&lt;br /&gt;
==Access to the Web Orbiter==&lt;br /&gt;
&lt;br /&gt;
===From within your home===&lt;br /&gt;
You can access the Web Orbiter 2.0 from any of the following Web browsers (Google Chrome, Mozilla Firefox, Safari). Others may also work but have not been tested (your experiences with other web browsers would be welcome here) :&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;For the 810 releases the correct URL is:&#039;&#039;&#039;&lt;br /&gt;
&#039;&#039;&amp;lt;nowiki&amp;gt;http://&amp;amp;lt;core_ip&amp;amp;gt;/lmce-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:* From within the &amp;quot;internal&amp;quot; LinuxMCE LAN, for example: &lt;br /&gt;
::::&#039;&#039;http://192.168.80.1/lmce-admin/weborbiter.php&#039;&#039; (0810)&lt;br /&gt;
:::::(This assumes the IP address range set by default at installation.)&lt;br /&gt;
:*You can also use the network name of the Core in place of the IP address. For example, if the Core was named &amp;quot;dcerouter&amp;quot; during the default installation, you could use:&lt;br /&gt;
::::&#039;&#039;&amp;lt;nowiki&amp;gt;http://dcerouter/pluto-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
:*From the &amp;quot;external&amp;quot; WAN side of the Core, the core_ip would be the WAN IP address of the core (ie the one offered to the WAN side NIC on the Core by your broadband Router). If, for example, the core has a WAN side address of 192.168.0.50 offered up by your Broadband Router, use:&lt;br /&gt;
:::: &#039;&#039;&amp;lt;nowiki&amp;gt;http://192.168.0.50/lmce-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:::::(Note: To use this method, [[Outside Access]] must be enabled.)&lt;br /&gt;
&lt;br /&gt;
===From the Internet===&lt;br /&gt;
You could use the IP address:port for your home LAN, with port forwarding to the Core&#039;s LAN IP address (enabled by your home LAN router). &lt;br /&gt;
*&#039;&#039;This is an advanced topic and may not be secure in the current version.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
By default, LinuxMCE is not accessible outside your home. This makes the system secure, but it prevents you from accessing the web site via the Internet while away from home.  You can [[Outside_Access|turn on Internet access]], allowing access to the admin website anywhere. For your own security, however, we recommend you first read about [[Security &amp;amp; Privacy Issues]].&lt;br /&gt;
&lt;br /&gt;
===Login page===&lt;br /&gt;
*A simple login page should be displayed. Input an existing user name and password, then click &amp;quot;Login&amp;quot;.&lt;br /&gt;
*From the dropdown list of devices, choose Generic Web Device.&lt;br /&gt;
*A page that looks similar to this should appear: [[Image:Web Orbiter.jpg|center]]&lt;br /&gt;
&lt;br /&gt;
==Troubleshooting==&lt;br /&gt;
===Connect failed===&lt;br /&gt;
If you try to connect to the Web Orbiter and see this message:&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;quot;Connect to proxy orbiter failed, please try again&amp;quot;&amp;lt;/code&amp;gt;, &lt;br /&gt;
this means that Orbiter generation hasn&#039;t finished yet, or that you forgot to do a [[Quick_reload_router|quick restart of the router]].&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Web_Orbiter_2.0&amp;diff=24298</id>
		<title>Web Orbiter 2.0</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Web_Orbiter_2.0&amp;diff=24298"/>
		<updated>2010-07-07T15:34:52Z</updated>

		<summary type="html">&lt;p&gt;Viking: /* From within your home */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{versioninfo}}&lt;br /&gt;
{| align=&amp;quot;right&amp;quot;&lt;br /&gt;
  | __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
[[Category: Orbiters]]&lt;br /&gt;
[[Category: Tutorials]]&lt;br /&gt;
&lt;br /&gt;
A Web Orbiter is any device (such as a iPhone, iPod Touch, iPad, laptop, PC, etc.) that accesses the Orbiter user interface (UI) through a Web browser.&lt;br /&gt;
&lt;br /&gt;
The new Web Orbiter 2.0 has been re-written from the ground up to make sure it has a much smoother performance overall but especially on slower lower powered devices and devices that are connected over slow LAN connections or even slower external connections...such as a Mobile 3G network or slow WiFi connection.&lt;br /&gt;
&lt;br /&gt;
So what has changed? Well visually your Orbiter UI will look like it does on your existing standard Orbiters but you will notice that unlike the original Web Orbiter the new 2.0 version does not refresh every 5 secs. The new Web Orbiter now only updates if something changes in the system and that requires the UI screen you are currently viewing to be updated or if you click on a UI button or other UI element and that causes a screen update. &lt;br /&gt;
&lt;br /&gt;
Proxy_orbiter runs on the Core and its job is to render the UI for the Web Orbiter that is running remotely on some other device. Each Web Orbiter has an associated proxy_orbiter and the two work in partnership. Proxy_orbiters do all the &#039;heavy lifting&#039; rendering the UI and this allows the remote device that is running the Web Orbiter to be much less powerful and very simple devices indeed if needed.&lt;br /&gt;
&lt;br /&gt;
To achieve this the proxy_orbiter has been updated so that it sets a flag called &#039;ANYNEWS&#039; to &#039;true&#039; if some element of the current displayed screen has been updated. The Web Orbiter makes a light weight call to query the state of this flag once every second and only gets an updated UI screen if the flag is set to &#039;true&#039; otherwise no screen update is requested. So in use the new Web Orbiter 2.0 behaves in a very similar fashion to the Orbiter on one of your MD&#039;s - and now it even performs with a similar performance level too.&lt;br /&gt;
&lt;br /&gt;
Another change in the new 2.0 Web Orbiter is that screen refreshes are double buffered so that the new Web Orbiter receives the new screen update from your Core in the background and only redraws the screen when it has the complete image stored in memory - this makes the update process smoother and faster.&lt;br /&gt;
&lt;br /&gt;
The overall effect of all these changes is to vastly improve the performance and usability while at the same time reducing the processing overhead of the Web Orbiter massively.&lt;br /&gt;
&lt;br /&gt;
== Setup ==&lt;br /&gt;
The procedure to setup a Web Orbiter is simple but the order of steps is important.&lt;br /&gt;
#First of all, add a new Generic Web Device as a Child Device for your Core:&lt;br /&gt;
##Goto the LinuxMCE Admin website--&amp;gt;Show devices tree--&amp;gt;CORE. The CORE&#039;s detail page should appear.&lt;br /&gt;
##Click &#039;Create Child Device&#039;.&lt;br /&gt;
##In the Description, enter the name of the specific web orbiter.&lt;br /&gt;
##In the Add child device window, click the button &#039;Pick device template&#039;. The new pop-up window containing device templates will be opened.&lt;br /&gt;
##In the &#039;Device Category&#039; dropdown list, choose &#039;Peripherals&#039;.&lt;br /&gt;
##In the &#039;Device Template&#039; dropdown list, find and select &amp;quot;Generic Web Device&amp;quot; (or just type the template id: 1748 and press go).&lt;br /&gt;
##Click the button &#039;Pick Device Template&#039;. 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.&lt;br /&gt;
##A new Generic Proxy Orbiter will also be created automatically. Watch the Orbiter generation process on the Orbiters page: Wizard--&amp;gt;Devices--&amp;gt;Orbiters.&lt;br /&gt;
#Wait till the Orbiter generation procedure finishes. A message on an active Orbiter or on the Orbiter page will indicate when it has completed.&lt;br /&gt;
#Click on your new Generic Proxy Orbiter in the device tree and then scroll to the bottom of the page on the right and look for the field called &#039;Listen Port&#039;. This field will be set to &#039;3461&#039; by default (if this Web Orbiter is not your first then you should increment this value by one ie to &#039;3462&#039; - each Web Orbiter must have a unique &#039;Listen Port&#039;)&lt;br /&gt;
#Now click the &#039;Save&#039; button at the bottom of the screen to save the changes you have made.&lt;br /&gt;
#Now do a &#039;Full Regen&#039; from the &#039;Wizard - Orbiters&#039; page (use the &#039;Full Regen&#039; for the specific Web Orbiter you have created and not the overall &#039;Full Regen&#039; button at the top of the page. Next when the Regen has completed do a &amp;quot;[[Quick reload router]]&amp;quot;. Otherwise, the Orbiter won&#039;t work properly.&lt;br /&gt;
&lt;br /&gt;
==Access to the Web Orbiter==&lt;br /&gt;
&lt;br /&gt;
===From within your home===&lt;br /&gt;
You can access the Web Orbiter 2.0 from any of the following Web browsers (Google Chrome, Mozilla Firefox, Safari). Others may also work but have not been tested (your experiences with other web browsers would be welcome here) :&lt;br /&gt;
&lt;br /&gt;
If you have got several web orbiters defined, you will be asked which one you would like to use.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;For the 810 releases the correct URL is:&#039;&#039;&#039;&lt;br /&gt;
&#039;&#039;&amp;lt;nowiki&amp;gt;http://&amp;amp;lt;core_ip&amp;amp;gt;/lmce-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:* From within the &amp;quot;internal&amp;quot; LinuxMCE LAN, for example: &lt;br /&gt;
::::&#039;&#039;http://192.168.80.1/lmce-admin/weborbiter.php&#039;&#039; (0810)&lt;br /&gt;
:::::(This assumes the IP address range set by default at installation.)&lt;br /&gt;
:*You can also use the network name of the Core in place of the IP address. For example, if the Core was named &amp;quot;dcerouter&amp;quot; during the default installation, you could use:&lt;br /&gt;
::::&#039;&#039;&amp;lt;nowiki&amp;gt;http://dcerouter/pluto-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
:*From the &amp;quot;external&amp;quot; WAN side of the Core, the core_ip would be the WAN IP address of the core (ie the one offered to the WAN side NIC on the Core by your broadband Router). If, for example, the core has a WAN side address of 192.168.0.50 offered up by your Broadband Router, use:&lt;br /&gt;
:::: &#039;&#039;&amp;lt;nowiki&amp;gt;http://192.168.0.50/lmce-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:::::(Note: To use this method, [[Outside Access]] must be enabled.)&lt;br /&gt;
&lt;br /&gt;
===From the Internet===&lt;br /&gt;
You could use the IP address:port for your home LAN, with port forwarding to the Core&#039;s LAN IP address (enabled by your home LAN router). &lt;br /&gt;
*&#039;&#039;This is an advanced topic and may not be secure in the current version.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
By default, LinuxMCE is not accessible outside your home. This makes the system secure, but it prevents you from accessing the web site via the Internet while away from home.  You can [[Outside_Access|turn on Internet access]], allowing access to the admin website anywhere. For your own security, however, we recommend you first read about [[Security &amp;amp; Privacy Issues]].&lt;br /&gt;
&lt;br /&gt;
===Login page===&lt;br /&gt;
*A simple login page should be displayed. Input an existing user name and password, then click &amp;quot;Login&amp;quot;.&lt;br /&gt;
*From the dropdown list of devices, choose Generic Web Device.&lt;br /&gt;
*A page that looks similar to this should appear: [[Image:Web Orbiter.jpg|center]]&lt;br /&gt;
&lt;br /&gt;
==Troubleshooting==&lt;br /&gt;
===Connect failed===&lt;br /&gt;
If you try to connect to the Web Orbiter and see this message:&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;quot;Connect to proxy orbiter failed, please try again&amp;quot;&amp;lt;/code&amp;gt;, &lt;br /&gt;
this means that Orbiter generation hasn&#039;t finished yet, or that you forgot to do a [[Quick_reload_router|quick restart of the router]].&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Web_Orbiter&amp;diff=21588</id>
		<title>Web Orbiter</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Web_Orbiter&amp;diff=21588"/>
		<updated>2009-11-08T16:44:23Z</updated>

		<summary type="html">&lt;p&gt;Viking: /* From within your home */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| align=&amp;quot;right&amp;quot;&lt;br /&gt;
  | __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
[[Category: Orbiters]]&lt;br /&gt;
[[Category: Tutorials]]&lt;br /&gt;
&lt;br /&gt;
A Web Orbiter is any device (such as a laptop, PC, etc.) that accesses the Orbiter user interface (UI) through a Web browser.  &lt;br /&gt;
&lt;br /&gt;
== Setup ==&lt;br /&gt;
The procedure to setup a Web Orbiter is simple but the order of steps is important.&lt;br /&gt;
#First of all, add a new Generic Web Device as a Child Device for your Core:&lt;br /&gt;
##Goto the LinuxMCE Admin website--&amp;gt;Show devices tree--&amp;gt;CORE. The CORE&#039;s detail page should appear.&lt;br /&gt;
##Click &#039;Create Child Device&#039;.&lt;br /&gt;
##In the Add child device window, click the button &#039;Pick device template&#039;. The new pop-up window contained device templates will be opened.&lt;br /&gt;
##In the &#039;Device Category&#039; dropdown list, choose &#039;Peripherals&#039;.&lt;br /&gt;
##In the &#039;Device Template&#039; dropdown list, find and select &amp;quot;Generic Web Device&amp;quot; (or just type the template id: 1748 and press go).&lt;br /&gt;
##Click the button &#039;Pick Device Template&#039;. 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.&lt;br /&gt;
##A new Generic Proxy Orbiter will also be created automatically. Watch the Orbiter generation process on the Orbiters page: Wizard--&amp;gt;Devices--&amp;gt;Orbiters.&lt;br /&gt;
#Wait till the Orbiter generation procedure finishes. A message on an active Orbiter or on the Orbiter page will indicate when it has completed.&lt;br /&gt;
#Do a &amp;quot;[[Quick reload router]]&amp;quot;. Otherwise, the Orbiter won&#039;t work properly.&lt;br /&gt;
&lt;br /&gt;
==Access to the Web Orbiter==&lt;br /&gt;
&lt;br /&gt;
===From within your home===&lt;br /&gt;
You can access the Web Orbiter from any web browser (Mozilla Firefox, IE, Safari):&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If you are currently using the 810 alpha releases the correct URL is:&#039;&#039;&#039;&lt;br /&gt;
&#039;&#039;&amp;lt;nowiki&amp;gt;http://&amp;amp;lt;core_ip&amp;amp;gt;/lmce-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The current release 710 uses the information below.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*In the browser address bar, type the URL &#039;&#039;&amp;lt;nowiki&amp;gt;http://&amp;amp;lt;core_ip&amp;amp;gt;/pluto-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;.&lt;br /&gt;
:* From within the &amp;quot;internal&amp;quot; LinuxMCE LAN, for example: &lt;br /&gt;
::::&#039;&#039;http://192.168.80.1/pluto-admin/weborbiter.php&#039;&#039; (0710)&lt;br /&gt;
::::&#039;&#039;http://192.168.80.1/lmce-admin/weborbiter.php&#039;&#039; (0810)&lt;br /&gt;
:::::(This assumes the IP address range set by default at installation.)&lt;br /&gt;
:*You can also use the network name of the Core in place of the IP address. For example, if the Core was named &amp;quot;dcerouter&amp;quot; during the default installation, you could use:&lt;br /&gt;
::::&#039;&#039;&amp;lt;nowiki&amp;gt;http://dcerouter/pluto-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
:*From the &amp;quot;external&amp;quot; home LAN, the core_ip would be the LAN IP address of the core. If, for example, the core is at 192.168.0.50 on the home LAN, use:&lt;br /&gt;
:::: &#039;&#039;&amp;lt;nowiki&amp;gt;http://192.168.0.50/pluto-admin/weborbiter.php&amp;lt;/nowiki&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:::::(Note: To use this method, [[Outside Access]] must be enabled.)&lt;br /&gt;
&lt;br /&gt;
===From the Internet===&lt;br /&gt;
You could use the IP address:port for your home LAN, with port forwarding to the Core&#039;s LAN IP address (enabled by your home LAN router). &lt;br /&gt;
*&#039;&#039;This is an advanced topic and may not be secure in the current version.&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
By default, LinuxMCE is not accessible outside your home. This makes the system secure, but it prevents you from accessing the web site via the Internet while away from home.  You can [[Outside_Access|turn on Internet access]], allowing access to the admin website anywhere. For your own security, however, we recommend you first read about [[Security &amp;amp; Privacy Issues]].&lt;br /&gt;
&lt;br /&gt;
===Login page===&lt;br /&gt;
*A simple login page should be displayed. Input an existing user name and password, then click &amp;quot;Login&amp;quot;.&lt;br /&gt;
*From the dropdown list of devices, choose Generic Web Device.&lt;br /&gt;
*A page that looks similar to this should appear: [[Image:Web Orbiter.jpg|center]]&lt;br /&gt;
&lt;br /&gt;
==Troubleshooting==&lt;br /&gt;
===Connect failed===&lt;br /&gt;
If you try to connect to the Web Orbiter and see this message:&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;quot;Connect to proxy orbiter failed, please try again&amp;quot;&amp;lt;/code&amp;gt;, &lt;br /&gt;
this means that Orbiter generation hasn&#039;t finished yet,  or that you forgot to do a [[Quick_reload_router|quick restart of the router]].&lt;br /&gt;
&lt;br /&gt;
=== Size ===&lt;br /&gt;
I was able to change the size of the rendered image in the Wizard--&amp;gt;Orbiters page. Find the Web Orbiter device in the list and resize it. After another orbiter regen, it was the right size for me. (&#039;&#039;Source http://forum.linuxmce.org/index.php?topic=3833.0&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
=== Problems with rapid refresh rate ===&lt;br /&gt;
&lt;br /&gt;
Problem:&lt;br /&gt;
When using the Web Orbiter over the Internet (instead of from within my home LAN), it refreshed every 5 seconds, making it difficult to use. The images were repeatedly downloaded each time.&lt;br /&gt;
&lt;br /&gt;
Solution:&lt;br /&gt;
*Go to [[LinuxMCE Admin Website]]--&amp;gt;Device tree--&amp;gt;CORE--&amp;gt;Generic Web Device--&amp;gt;Device Data &lt;br /&gt;
*Set the Refresh Interval to a higher value (I used 60 seconds for mine).&lt;br /&gt;
&lt;br /&gt;
=== Changing default room ===&lt;br /&gt;
Changing the default room in the Wizard--&amp;gt;Devices--&amp;gt;Orbiters page has no effect.&lt;br /&gt;
&lt;br /&gt;
Solution:&lt;br /&gt;
*Go to [[LinuxMCE Admin Website]]--&amp;gt;Device tree--&amp;gt;CORE--&amp;gt;Generic Web Device&lt;br /&gt;
*Check the box for the room to control&lt;br /&gt;
&lt;br /&gt;
===Screen Deadlock===&lt;br /&gt;
If the screen of your orbiter becomes &amp;quot;frozen&amp;quot; or stuck and orbiter regens and router reloads do not resolve the issue, run this from the core:&lt;br /&gt;
 sudo killall -9 Proxy_Orbiter&lt;br /&gt;
(Source: http://forum.linuxmce.org/index.php?topic=6844.0)&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=LinuxMCE-0810_beta&amp;diff=21561</id>
		<title>LinuxMCE-0810 beta</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=LinuxMCE-0810_beta&amp;diff=21561"/>
		<updated>2009-11-01T15:55:02Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Software]]&lt;br /&gt;
This page outlines some information about the Beta, as well as outline any changes and bugfixes we are applying, just like we did with the alpha2 page.&lt;br /&gt;
&lt;br /&gt;
The installation instructions found on the alpha2 page still apply:&lt;br /&gt;
&lt;br /&gt;
==Internet Installation==&lt;br /&gt;
# Install Kubuntu Intrepid desktop and update it. (download Kubuntu 8.10 &#039;&#039;&#039;desktop&#039;&#039;&#039; release from one of these: [http://mirrors.ccs.neu.edu/releases.ubuntu.com/kubuntu/8.10/ Northeastern University Mirror, USA], [http://swtsrv.informatik.uni-mannheim.de/pub/linux/distributions/ubuntu-release/kubuntu/8.10/ Mannheim University Mirror, Germany]) &#039;&#039;&#039;Currently, only the 32bit version of LinuxMCE is available. Only download the i386 version of 8.10 Kubuntu, even if your system can support 64bit versions.&#039;&#039;&#039;&lt;br /&gt;
# Run aptitude update and aptitude dist-upgrade to get the latest Kubuntu updates.&lt;br /&gt;
# Grab the latest installer script from [http://deb.linuxmce.org/ubuntu here], unpack them and change into the freshly created &#039;&#039;new-installer&#039;&#039; directory.&lt;br /&gt;
# Run the following scripts (as root, in order): pre-install-from-repo.sh, mce-install.sh, post-install.sh.&lt;br /&gt;
# Reboot, wait for the activity to stop (see progress on console 8).&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;EDIT:  MAKE SURE YOUR INTERNET CONNECTION IS ON ETH0!&#039;&#039;&#039; (For linux Newbies ETH0 is probably the network card on your motherboard...or plug all NICs into a switch that has Internet access)&lt;br /&gt;
&lt;br /&gt;
In other words, after installing Kubuntu:&lt;br /&gt;
 sudo su - #This might ask for the password you specified earlier during the install of kubuntu.&lt;br /&gt;
 aptitude update&lt;br /&gt;
 aptitude dist-upgrade&lt;br /&gt;
 wget -c http://deb.linuxmce.org/ubuntu/new-installer-alpha-latest.tar.gz&lt;br /&gt;
 tar xvf new-installer-alpha-latest.tar.gz&lt;br /&gt;
 cd new-installer&lt;br /&gt;
 ./pre-install-from-repo.sh&lt;br /&gt;
 ./mce-install.sh&lt;br /&gt;
 ./post-install.sh&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
==DVD Installation==&lt;br /&gt;
&lt;br /&gt;
However, if you want to install the DVD, grab it via the torrent [http://www.linuxmce.org/index.php/download here].&lt;br /&gt;
&lt;br /&gt;
Upon DVD boot, select LinuxMCE install. This will install a regular Kubuntu 810 system, with an additional button on the desktop to install LinuxMCE upon restart. Let Kubuntu&#039;s install run through, and after restart, login, and double click on the LinuxMCE icon. This will run the fullinstall.sh in /root/new-installer&lt;br /&gt;
&lt;br /&gt;
The DVD installer per default does not create the initial MD image, as that creation takes a very long time, and most people probably prefer to give 810 a test, without the MDs. If you want to setup MDs, you have to manually run &lt;br /&gt;
 /usr/pluto/bin/Diskless_CreateTBZ.sh&lt;br /&gt;
&lt;br /&gt;
If you have problems running Diskless_CreateTBZ.sh, check [[Error Running Diskless CreateTBZ.sh|this article]].&lt;br /&gt;
&lt;br /&gt;
After running your diskless MD for the first time (whether it works or not), remember to convert the image it creates on the core to i386 if your MD hardware is amd64. This can be done through the [[LinuxMCE Admin Website|LinuxMCE Admin site]] by clicking on &amp;quot;Media Directors&amp;quot;, changing the architecture to &amp;quot;i386&amp;quot; (from &amp;quot;amd64&amp;quot;) for the MD in question, clicking &amp;quot;Update&amp;quot; and then &amp;quot;Rebuild image&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
If you then have problems netbooting your diskless media directors because you are receiving the error message &amp;quot;Diskless Setup Failed&amp;quot;, check [[Diskless setup failed error in 0810 beta|this article]].&lt;br /&gt;
&lt;br /&gt;
=== Upcoming beta2 changes... ===&lt;br /&gt;
The upcoming beta2 will have a complete set of new packages. This is due to changes in the mysql handling to finally fix unicode issues.&lt;br /&gt;
&lt;br /&gt;
=== After beta2... ===&lt;br /&gt;
* Build_Replacement_Package - freepbx (ubuntu/asterisk/freepbx) - Ticket #345 - Fixes the issue of installing new modules in FreePBX.&lt;br /&gt;
* Phone Lines fixing - asterisk (src/asterisk) - Ticket #374 - Fixes the issue during the creation procedure of a new phone lines via web LinuxMCE Admin.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Bugfixes ==&lt;br /&gt;
=== Diskless setup failed ===&lt;br /&gt;
Should you receive the error &amp;quot;Diskless setup failed&amp;quot; when trying to netboot your MDs, see here&lt;br /&gt;
[[Diskless_setup_failed_error_in_0810_beta]]&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Viking&amp;diff=20150</id>
		<title>User:Viking</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Viking&amp;diff=20150"/>
		<updated>2009-08-04T10:23:58Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[category:User Setups]]&lt;br /&gt;
&lt;br /&gt;
This is my system.&lt;br /&gt;
&lt;br /&gt;
1st MD TV :&lt;br /&gt;
* [[Sony_KDL-46W4500]] - 1080p resolution UI2 overlay interface&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Core :&lt;br /&gt;
* ASUS M3A-H/HDMI&lt;br /&gt;
* AMD Athlon 64 X2 5050e Sockel-AM2 Box&lt;br /&gt;
* be quiet Straight Power 350W ATX 2.2 &lt;br /&gt;
* Arctic Cooling Freezer 64 Pro PMW&lt;br /&gt;
* 2x DDR2-800 2048MB &lt;br /&gt;
* 2x Arctic Cooling 120x120x25 AF12025 PWM &lt;br /&gt;
* Pioneer DVR-216DBK black&lt;br /&gt;
* Sharkoon Revenge Economy Edition Case - black &lt;br /&gt;
* 3 x 1TB Samsung Spinpoint F1 HD103UI EcoGreen (in RAID5)&lt;br /&gt;
* Longshine LCS-8337TXR (PCI Express)&lt;br /&gt;
* PSU 350W be quiet  E6-350W Straight Power&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
1st MD :&lt;br /&gt;
* ASUS 8400GS 512MB silent graphicscard&lt;br /&gt;
* 1xGigabyte GA-MA78GM-S2H   - DON&#039;T buy it for 0710 !!&lt;br /&gt;
* AMD Athlon 64 X2 5050e Sockel-AM2 Box&lt;br /&gt;
* be quiet Straight Power 350W ATX 2.2 &lt;br /&gt;
* Arctic Cooling Freezer 64 Pro PMW&lt;br /&gt;
* 2x DDR2-800 2048MB &lt;br /&gt;
* Pioneer DVR-216DBK black&lt;br /&gt;
* 3 x 1TB Samsung Spinpoint F1 HD103UI EcoGreen (in RAID5)&lt;br /&gt;
* Longshine LCS-8337TXR (PCI Express)&lt;br /&gt;
* PSU 350W be quiet  E6-350W Straight Power&lt;br /&gt;
* Silverstone LC17 case&lt;br /&gt;
&lt;br /&gt;
* USB-UIRT (søg i wiki/forum) infrarød sender/modtager&lt;br /&gt;
* Phillips SRM 5100 (Windows MCE remote control) - apparently not 100% compatible&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Network&lt;br /&gt;
* Digitus N-Way Switch 5 Gigabit ports 5x10/100/1000TX (cheap but OK)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
TV cards &lt;br /&gt;
* TechnoTrend: S2-3200 (not in use yet, so not 100% sure if it works)&lt;br /&gt;
* 2 old TechnoTrend DVB-s cards. 1x 1.6-4MB, 1x 1.3-DVB-s&lt;br /&gt;
* 1 WinTV Nova-s&lt;br /&gt;
* 1 Satelco DVB-C (KNC ONE compatible)&lt;br /&gt;
* 1x Hauppauge WinTV Nova-TD  (DVB-T usb stick) - is probably not going to be used, using DVB-C instead.&lt;br /&gt;
&lt;br /&gt;
Lightcontrol &lt;br /&gt;
* Tricklestar 200ZW-EU-W&lt;br /&gt;
* Seluxit Viasens controlle&lt;br /&gt;
* (the Tricklestar 300ZW-EU-W was replaced by the Viasens as it is better)&lt;br /&gt;
&lt;br /&gt;
And a couple of  Z-wave devices to play with ;)&lt;br /&gt;
* http://www.zwave4u.com/products/en/Lighting-and-Power/PlugIn-Adapters/ACT-Homepro-ZRP-200-Schuko-Plugin-Switch.html&lt;br /&gt;
* http://www.zwave4u.com/products/en/Lighting-and-Power/PlugIn-Adapters/ACT-Homepro-ZDP-200-Schuko-Plugin-Dimmer.html&lt;br /&gt;
* Two Merten 507001&lt;br /&gt;
* One Merten button 508044&lt;br /&gt;
* Two Merten 506004&lt;br /&gt;
* Everspring SM103&lt;br /&gt;
* Everspring SP103&lt;br /&gt;
&lt;br /&gt;
Most of them not implemented yet.&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=MythTV&amp;diff=20018</id>
		<title>MythTV</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=MythTV&amp;diff=20018"/>
		<updated>2009-07-24T11:40:38Z</updated>

		<summary type="html">&lt;p&gt;Viking: /* EXPERIMENTAL: Update MythTV to VDPAU version on 0810 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| align=&amp;quot;right&amp;quot;&lt;br /&gt;
  | __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
[[Category: Programmer&#039;s Guide]]&lt;br /&gt;
[[Category:Software components]]&lt;br /&gt;
[[Category: Video]]&lt;br /&gt;
[[Category:Tutorials]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;MythTV&#039;&#039;&#039; is a Linux application which turns a PC (with the necessary hardware) into a [[personal video recorder]], a digital multimedia home entertainment system, and a Home Theater Personal Computer. It is used by LinuxMCE to handle viewing and recording of television.&lt;br /&gt;
&lt;br /&gt;
*[http://www.mythtv.org MythTV Main Website]&lt;br /&gt;
*[[Mythweb]] wiki entry&lt;br /&gt;
*[[Mythtv:Skipping_Commercials]] wiki entry&lt;br /&gt;
&lt;br /&gt;
==Setting up MythTV in LinuxMCE==&lt;br /&gt;
(&amp;lt;small&amp;gt;&#039;&#039;If you purchased a Media Director with LinuxMCE pre-installed, you can skip steps 2, 3 and 6 below -- they will have been preconfigured.&amp;lt;/small&amp;gt;)&lt;br /&gt;
&lt;br /&gt;
*Plug in and boot your Media director.&lt;br /&gt;
&lt;br /&gt;
*If you have a PVR capture card, such as the PVR250/350 supported by IVTV, or the newer Blackbird cards (cx88), install any updated firmware available from the manufacturer. (Sometimes an Internet search for &#039;linuxmce&#039; and &#039;firmware&#039; will also locate firmware for your card.)&lt;br /&gt;
&lt;br /&gt;
*Make sure the capture card type is specified in [[LinuxMCE Admin Website]]--&amp;gt;Wizard--&amp;gt;Devices--&amp;gt;Media Directors.&lt;br /&gt;
&lt;br /&gt;
*For each Media Director, select the &#039;Computing&#039; button on either the Orbiter that appears on the media director&#039;s screen (the on-screen orbiter), or using any other Orbiter which is controlling the same room as the Media Director.  Choose &amp;quot;MythTV Setup&amp;quot;.  Myth&#039;s setup utility will appear on the Media Director.  If you launched this from an Orbiter other than the Media Director&#039;s own on-screen Orbiter, that Orbiter will display a keyboard &amp;amp; mouse that you can use (in addition to the media director&#039;s own). In this way you can use a webpad or PDA Orbiter as a wireless keyboard/mouse.&lt;br /&gt;
&lt;br /&gt;
*If you do not use NTSC, go to the &amp;quot;General&amp;quot;--&amp;gt;&amp;quot;Next&amp;quot;--&amp;gt;&amp;quot;Global Backend Setup&amp;quot; page.  Choose your video standard (NTSC, PAL, etc.).  The other default general settings should be fine. Press ESC to return to the Main Myth Setup Menu.&lt;br /&gt;
&lt;br /&gt;
*Choose &amp;quot;Capture Cards&amp;quot;--&amp;gt;&amp;quot;New Capture Card&amp;quot;. &lt;br /&gt;
:* If you have an ivtv or blackbird/cx88 card, choose &amp;quot;MPEG-2 Encoder card (PVR-250/350)&amp;quot;.&lt;br /&gt;
:* If you&#039;re using the cx88/blackbird driver, change the &#039;video0&#039; to &#039;video1&#039;.&lt;br /&gt;
:* If you have got a DVB-s card, as card type use: &#039;&#039;DVB DTV TV-Card (v3.x)&#039;&#039; and select the right frontend (autodetected) below. ATTENTION, Don&#039;t forget to set &#039;&#039;DiSEqC&#039;&#039;, i set to &#039;&#039;Universal (Europe)&#039;&#039;. Otherwise you will not be able to tune (at least that was my experience).&lt;br /&gt;
&lt;br /&gt;
*If your card was properly identified, the video device field should be filled in for you.  If not, try rebooting the Media Director and repeating.  Press ESC to return to the Main Myth Setup Menu.&lt;br /&gt;
&lt;br /&gt;
*Choose &amp;quot;Video Sources&amp;quot; and select your video source.  Refer to the Myth user&#039;s Manual for details. For DVB-s &#039;&#039;Transmitted guide only (EIT)&#039;&#039; is a good start choice. Press ESC to return to the Main Myth Setup Menu.&lt;br /&gt;
&lt;br /&gt;
*Choose &amp;quot;Input connections&amp;quot; to indicate which video source is connected to which input on the capture card.&lt;br /&gt;
&lt;br /&gt;
*Press ESC to exit Myth Setup and return to the LinuxMCE Orbiter screen.&lt;br /&gt;
&lt;br /&gt;
*At this point you will be prompted to run mythfilldatabse.  Select &amp;quot;Yes&amp;quot;.&lt;br /&gt;
:Sadly, as of 0710b3, this command silently fails to run.  To fix this problem:&lt;br /&gt;
:*Open /etc/mythtv/mysql.txt&lt;br /&gt;
:*Copy the value for DBpasswd from that file.&lt;br /&gt;
:*Open /home/linuxmce/.mythtv/mysql.txt (this file was created when you tried to run mythfilldatabse earlier and where linuxmce is the user you created when installing ubuntu - assuming CD installation)&lt;br /&gt;
&lt;br /&gt;
:*Paste the value you copied earlier into the DBpasswd field&lt;br /&gt;
:*Save the file and run mythfilldatabase again.&lt;br /&gt;
:*Go get a coffee&lt;br /&gt;
&lt;br /&gt;
*You will need to do a full reboot of the whole LinuxMCE system (the Core and all Media Directors) before you can watch TV with Myth TV.  You may want to setup all the Media Directors at once, therefore, and then do a complete reboot.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;NOTE:&#039;&#039;&#039; Do not reboot until the Media Directors have had a chance to retrieve the channel data.  You can confirm this by choosing the &#039;TV&#039; button on the Orbiter main menu.  This launches MythTV.  Then choose &amp;quot;Manage Recordings&amp;quot;, &amp;quot;Schedule Recordings&amp;quot;, &amp;quot;Program Guide&amp;quot;.  You should see some program guide data.  If you do not, wait a bit so Myth has a chance to download the guide data.&lt;br /&gt;
&lt;br /&gt;
===Troubleshooting===&lt;br /&gt;
&lt;br /&gt;
*[http://www.mythtv.org MythTV Main Website official Myth website]&lt;br /&gt;
*[http://forum.linuxmce.com LinuxMCE forums]&lt;br /&gt;
&lt;br /&gt;
====MythTV&#039;s Backend doesn&#039;t show any tuners====&lt;br /&gt;
I had an issue where, after adding my information using the setup wizard, the mythbackend process did not show any tuners as being available.  This may have occured because I had deleted my PVR-150 devices and re-added them.  The issue was simply that LinuxMCE did not fill in the device path for the tuner.  The solution was to go in to the &amp;quot;computing&amp;quot; menu and to run MythTV Setup.  Once in the MythTV Setup screen, select Tuners and you&#039;ll probably see your tuners listed without a device path (for example, &amp;quot;MPG:  &amp;quot; instead of &amp;quot;MPG: /dev/video0&amp;quot;.  Simply go into each tuner and select the proper video device and then exit.  You should not have to do anything with the input sources as these would have already been configured by LinuxMCE&lt;br /&gt;
&lt;br /&gt;
====Fixing Errors in MythTV Tables====&lt;br /&gt;
Upon sudden power loss or in some other situations, you may experience odd behavior from MythTV on restart. This includes&lt;br /&gt;
*Scheduled recordings not showing in &#039;Upcoming Recording&#039; in Mythweb&lt;br /&gt;
*Inability to record programs from any interface, be it the on-screen orbiter or Mythweb.&lt;br /&gt;
*Inconsistencies in the &#039;&#039;&#039;mythconverg&#039;&#039;&#039; table (Advanced Users)&lt;br /&gt;
&lt;br /&gt;
To correct this issue, please take the following steps:&lt;br /&gt;
Try either of these options:&lt;br /&gt;
&lt;br /&gt;
*1st we check to see if infact there are problem tables by running this in a shell on the core:&lt;br /&gt;
  /etc/init.d/mythtv-backend stop&lt;br /&gt;
  mysqlcheck -c -uroot -p mythconverg &lt;br /&gt;
&lt;br /&gt;
**if there are errors the run&lt;br /&gt;
&lt;br /&gt;
  mysqlcheck -r -uroot -p mythconverg&lt;br /&gt;
&lt;br /&gt;
occasional this does not fix the problem, then try this&lt;br /&gt;
&lt;br /&gt;
  cd /var/lib/mysql/mythconverg&lt;br /&gt;
  /etc/init.d/mythtv-backend stop&lt;br /&gt;
  /etc/init.d/mysql stop&lt;br /&gt;
  myisamchk *.MYI -r&lt;br /&gt;
&lt;br /&gt;
This should correct the issue. In my own testing (golgoj4) after a reboot everything was functioning correctly.&lt;br /&gt;
&lt;br /&gt;
This fix was provided by user Rwilson131 (thanks)&lt;br /&gt;
&lt;br /&gt;
==Electronic Program Guide with xmltv==&lt;br /&gt;
&lt;br /&gt;
*Read the [[MythTV%2C_xmltv_and_channels|xmltv channels guide]].&lt;br /&gt;
&lt;br /&gt;
==  MythTV frontend access to LinuxMCE &amp;amp; MD password ==&lt;br /&gt;
 &lt;br /&gt;
LMCE&#039;s version of MythTV runs a mythbackend server. As long as your versions are close or exact, you should simply have to put the MythTV frontend PC on the same subnet as the core media subnet (default is 192.168.80.1) when running mythfrontend it will ask you for the masterserver backend ip address or hostname (again the default is 192.168.80.1 or dcerouter), after providing this information, you will most likely be able to connect to your content (I do this all the time from my laptop booted to kubuntu 710, and the mythv-frontend package installed) and I can view my recordings and watch TV live from the tuners.&lt;br /&gt;
&lt;br /&gt;
the latest version of MythTV in LMCE is 0.20.2 fixes, so as long as the version you install is of this variant or package level, you should be able to connect up. If you for whatever reason do not wish to attach the myth frontend pc/laptop to the media subnet provided by the core, you will have to make ammendments to your LMCE firewall from the web admin to allow mythtv to talk to it, or simply disable the LMCE firewall so that the mythfrontend can connect to its address.&lt;br /&gt;
&lt;br /&gt;
PASSWORD&lt;br /&gt;
&lt;br /&gt;
You will also have to go into mythtv setup on the lmce core, and get the username and password for the mythtv mysql user. Otherwise you will not be able to connect to the LMCE master backend. &lt;br /&gt;
&lt;br /&gt;
discussion at&lt;br /&gt;
http://forum.linuxmce.org/index.php?topic=5180.0&lt;br /&gt;
&lt;br /&gt;
==EXPERIMENTAL: Update MythTV to VDPAU version on 0810==&lt;br /&gt;
&lt;br /&gt;
I first installed the LinuxMCE standard version of MythTV and got it working and &#039;&#039;&#039;after that&#039;&#039;&#039; I installed the VDPAU version.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you don&#039;t have a Nvidia cvard on the core then you should probably not update the core  !!!&lt;br /&gt;
&lt;br /&gt;
Otherwise first update the Core and the the MD doing this&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*add avenard repository to /etc/apt/sources.list&lt;br /&gt;
From http://www.avenard.org/media/Ubuntu_Repository/Ubuntu_Repository.html&lt;br /&gt;
&lt;br /&gt;
*Add the signing GPG key&lt;br /&gt;
&lt;br /&gt;
    wget http://www.avenard.org/files/ubuntu-repos/ubuntu-repos.key &amp;amp;&amp;amp; sudo apt-key add ubuntu-repos.key &amp;amp;&amp;amp; rm ubuntu-repos.key&lt;br /&gt;
&lt;br /&gt;
*Add repository 08.10 &lt;br /&gt;
    echo &amp;quot;deb http://www.avenard.org/files/ubuntu-repos intrepid release&amp;quot; | sudo tee /etc/apt/sources.list.d/avenard.list&lt;br /&gt;
&lt;br /&gt;
 apt-get update&lt;br /&gt;
 apt-get install libmyth-0.21-0 libmyth-perl mythtv-backend mythtv-common mythtv-frontend mythtv-transcode-utils pluto-mythtv-player&lt;br /&gt;
&lt;br /&gt;
*update nvidia using the 180.60 packages from avenard&lt;br /&gt;
 apt-get install nvidia-common nvidia-glx-180 nvidia-180-modaliases&lt;br /&gt;
*maybe update alsa to 1.0.20 - I did not do that, but might be that you will have to.&lt;br /&gt;
*reboot&lt;br /&gt;
*run myth setup and add a profile like describved below &amp;quot;quick FAQ&amp;quot; here&lt;br /&gt;
 http://www.avenard.org/media/MythTV_%26_VDPAU/MythTV_%26_VDPAU.html&lt;br /&gt;
&lt;br /&gt;
Quick F.A.Q:&lt;br /&gt;
&lt;br /&gt;
Q: My CPU usage is still very high / my computer still can’t play HD videos&lt;br /&gt;
A: Using VDPAU isn’t automatic, you must create a new TV Playback profile. In mythfrontend, go into Setup -&amp;gt; TV Settings -&amp;gt; Playback -&amp;gt;  Playback Profiles. Create a new playback profile VDPAU.&lt;br /&gt;
&lt;br /&gt;
If you have a nVidia &amp;lt; 8600GT or &amp;lt; 9500GT, use the following profile:&lt;br /&gt;
&amp;lt;      W: 1920 H: 720, decoder: VDPAU, renderer: VDPAU, Deinterlacer: Advanced 2X&lt;br /&gt;
&amp;gt;=    W: 0 H: 720, decoder: VDPAU, renderer: VDPAU, Deinterlacer: Temporal 2X&lt;br /&gt;
&lt;br /&gt;
If you have a nVidia &amp;gt;= 8600GT or &amp;gt;= 9500GT, use the following profile:&lt;br /&gt;
&amp;gt;      W: 0 H: 0, decoder: VDPAU, renderer: VDPAU, Deinterlacer: Advanced 2X&lt;br /&gt;
&lt;br /&gt;
With this profile, your CPU usage during playback should be around 5-10%.&lt;br /&gt;
&lt;br /&gt;
*If mythTV hangs offen, please uncheck &amp;quot;Enable Realtime Priority threads&amp;quot; in TV -&amp;gt; General Playback.&lt;br /&gt;
*Setup your xorg.conf to 1080i&lt;br /&gt;
&lt;br /&gt;
*Add this to xorg.conf after &#039;Driver          &amp;quot;nvidia&amp;quot;&#039; (maybe not needed !!)&lt;br /&gt;
 Option         &amp;quot;TripleBuffer&amp;quot; &amp;quot;True&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==Programmer&#039;s Guide==&lt;br /&gt;
We have created a DCE Device that wraps the MythTV libraries and can receive commands from other DCE devices and use them to control the TV functionality of the mythtv. Supported functionality at this moment comprises the following: Start TV, Stop TV, Tune to channel, Channel Up, Channel Down. The player uses the same mechanisms that the current (as of 0.16 version) MythTv frontend program uses. So for every mythtv installation that currently works the player should work the same way as the current frontend.&lt;br /&gt;
&lt;br /&gt;
In order to be able to do this we had to change the signature of some methods in a class used by the mythfrontend application. The classes in question is the TV class defined in the  &amp;lt;b&amp;gt;libs/libmythtv/tv_play.{h,cpp}&amp;lt;/b&amp;gt; files from the mythtv repository. The changes consist in some method and field access changes (made some previously private methods to be public). This was done in order to be able to control the player programatically and avoid putting synthetic events into the playback windows event queue. The changes only affect the headers and are used to compile the player. The binary should run on any machine with a working 0.16 MythTV installation. &lt;br /&gt;
&lt;br /&gt;
Since we needed to have a resizable playback window we had to make some changes in the way the mythtv playback window is created and displayed. The change is a derived class from the MainMythWindow class which knows about resize events and uses them to resize all child objects inside it. The class is available in the plutohome.com svn repository also (in the &amp;lt;b&amp;gt;MythTV Player&amp;lt;/b&amp;gt; module). &lt;br /&gt;
&lt;br /&gt;
This module does not work currently with a mythfrontend application running. The module will present itself to the server as another mythfrontend client and it will use one tuner on playback (the same way as a mythtfronted will do).&lt;br /&gt;
== For German Speaking Users - and DVB-C ==&lt;br /&gt;
There is a very nice entry in the [http://mythwiki.de/index.php?title=Schnelleinstieg_DVB-C MythWiki]&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=MythTV&amp;diff=20017</id>
		<title>MythTV</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=MythTV&amp;diff=20017"/>
		<updated>2009-07-24T11:36:40Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| align=&amp;quot;right&amp;quot;&lt;br /&gt;
  | __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
[[Category: Programmer&#039;s Guide]]&lt;br /&gt;
[[Category:Software components]]&lt;br /&gt;
[[Category: Video]]&lt;br /&gt;
[[Category:Tutorials]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;MythTV&#039;&#039;&#039; is a Linux application which turns a PC (with the necessary hardware) into a [[personal video recorder]], a digital multimedia home entertainment system, and a Home Theater Personal Computer. It is used by LinuxMCE to handle viewing and recording of television.&lt;br /&gt;
&lt;br /&gt;
*[http://www.mythtv.org MythTV Main Website]&lt;br /&gt;
*[[Mythweb]] wiki entry&lt;br /&gt;
*[[Mythtv:Skipping_Commercials]] wiki entry&lt;br /&gt;
&lt;br /&gt;
==Setting up MythTV in LinuxMCE==&lt;br /&gt;
(&amp;lt;small&amp;gt;&#039;&#039;If you purchased a Media Director with LinuxMCE pre-installed, you can skip steps 2, 3 and 6 below -- they will have been preconfigured.&amp;lt;/small&amp;gt;)&lt;br /&gt;
&lt;br /&gt;
*Plug in and boot your Media director.&lt;br /&gt;
&lt;br /&gt;
*If you have a PVR capture card, such as the PVR250/350 supported by IVTV, or the newer Blackbird cards (cx88), install any updated firmware available from the manufacturer. (Sometimes an Internet search for &#039;linuxmce&#039; and &#039;firmware&#039; will also locate firmware for your card.)&lt;br /&gt;
&lt;br /&gt;
*Make sure the capture card type is specified in [[LinuxMCE Admin Website]]--&amp;gt;Wizard--&amp;gt;Devices--&amp;gt;Media Directors.&lt;br /&gt;
&lt;br /&gt;
*For each Media Director, select the &#039;Computing&#039; button on either the Orbiter that appears on the media director&#039;s screen (the on-screen orbiter), or using any other Orbiter which is controlling the same room as the Media Director.  Choose &amp;quot;MythTV Setup&amp;quot;.  Myth&#039;s setup utility will appear on the Media Director.  If you launched this from an Orbiter other than the Media Director&#039;s own on-screen Orbiter, that Orbiter will display a keyboard &amp;amp; mouse that you can use (in addition to the media director&#039;s own). In this way you can use a webpad or PDA Orbiter as a wireless keyboard/mouse.&lt;br /&gt;
&lt;br /&gt;
*If you do not use NTSC, go to the &amp;quot;General&amp;quot;--&amp;gt;&amp;quot;Next&amp;quot;--&amp;gt;&amp;quot;Global Backend Setup&amp;quot; page.  Choose your video standard (NTSC, PAL, etc.).  The other default general settings should be fine. Press ESC to return to the Main Myth Setup Menu.&lt;br /&gt;
&lt;br /&gt;
*Choose &amp;quot;Capture Cards&amp;quot;--&amp;gt;&amp;quot;New Capture Card&amp;quot;. &lt;br /&gt;
:* If you have an ivtv or blackbird/cx88 card, choose &amp;quot;MPEG-2 Encoder card (PVR-250/350)&amp;quot;.&lt;br /&gt;
:* If you&#039;re using the cx88/blackbird driver, change the &#039;video0&#039; to &#039;video1&#039;.&lt;br /&gt;
:* If you have got a DVB-s card, as card type use: &#039;&#039;DVB DTV TV-Card (v3.x)&#039;&#039; and select the right frontend (autodetected) below. ATTENTION, Don&#039;t forget to set &#039;&#039;DiSEqC&#039;&#039;, i set to &#039;&#039;Universal (Europe)&#039;&#039;. Otherwise you will not be able to tune (at least that was my experience).&lt;br /&gt;
&lt;br /&gt;
*If your card was properly identified, the video device field should be filled in for you.  If not, try rebooting the Media Director and repeating.  Press ESC to return to the Main Myth Setup Menu.&lt;br /&gt;
&lt;br /&gt;
*Choose &amp;quot;Video Sources&amp;quot; and select your video source.  Refer to the Myth user&#039;s Manual for details. For DVB-s &#039;&#039;Transmitted guide only (EIT)&#039;&#039; is a good start choice. Press ESC to return to the Main Myth Setup Menu.&lt;br /&gt;
&lt;br /&gt;
*Choose &amp;quot;Input connections&amp;quot; to indicate which video source is connected to which input on the capture card.&lt;br /&gt;
&lt;br /&gt;
*Press ESC to exit Myth Setup and return to the LinuxMCE Orbiter screen.&lt;br /&gt;
&lt;br /&gt;
*At this point you will be prompted to run mythfilldatabse.  Select &amp;quot;Yes&amp;quot;.&lt;br /&gt;
:Sadly, as of 0710b3, this command silently fails to run.  To fix this problem:&lt;br /&gt;
:*Open /etc/mythtv/mysql.txt&lt;br /&gt;
:*Copy the value for DBpasswd from that file.&lt;br /&gt;
:*Open /home/linuxmce/.mythtv/mysql.txt (this file was created when you tried to run mythfilldatabse earlier and where linuxmce is the user you created when installing ubuntu - assuming CD installation)&lt;br /&gt;
&lt;br /&gt;
:*Paste the value you copied earlier into the DBpasswd field&lt;br /&gt;
:*Save the file and run mythfilldatabase again.&lt;br /&gt;
:*Go get a coffee&lt;br /&gt;
&lt;br /&gt;
*You will need to do a full reboot of the whole LinuxMCE system (the Core and all Media Directors) before you can watch TV with Myth TV.  You may want to setup all the Media Directors at once, therefore, and then do a complete reboot.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;NOTE:&#039;&#039;&#039; Do not reboot until the Media Directors have had a chance to retrieve the channel data.  You can confirm this by choosing the &#039;TV&#039; button on the Orbiter main menu.  This launches MythTV.  Then choose &amp;quot;Manage Recordings&amp;quot;, &amp;quot;Schedule Recordings&amp;quot;, &amp;quot;Program Guide&amp;quot;.  You should see some program guide data.  If you do not, wait a bit so Myth has a chance to download the guide data.&lt;br /&gt;
&lt;br /&gt;
===Troubleshooting===&lt;br /&gt;
&lt;br /&gt;
*[http://www.mythtv.org MythTV Main Website official Myth website]&lt;br /&gt;
*[http://forum.linuxmce.com LinuxMCE forums]&lt;br /&gt;
&lt;br /&gt;
====MythTV&#039;s Backend doesn&#039;t show any tuners====&lt;br /&gt;
I had an issue where, after adding my information using the setup wizard, the mythbackend process did not show any tuners as being available.  This may have occured because I had deleted my PVR-150 devices and re-added them.  The issue was simply that LinuxMCE did not fill in the device path for the tuner.  The solution was to go in to the &amp;quot;computing&amp;quot; menu and to run MythTV Setup.  Once in the MythTV Setup screen, select Tuners and you&#039;ll probably see your tuners listed without a device path (for example, &amp;quot;MPG:  &amp;quot; instead of &amp;quot;MPG: /dev/video0&amp;quot;.  Simply go into each tuner and select the proper video device and then exit.  You should not have to do anything with the input sources as these would have already been configured by LinuxMCE&lt;br /&gt;
&lt;br /&gt;
====Fixing Errors in MythTV Tables====&lt;br /&gt;
Upon sudden power loss or in some other situations, you may experience odd behavior from MythTV on restart. This includes&lt;br /&gt;
*Scheduled recordings not showing in &#039;Upcoming Recording&#039; in Mythweb&lt;br /&gt;
*Inability to record programs from any interface, be it the on-screen orbiter or Mythweb.&lt;br /&gt;
*Inconsistencies in the &#039;&#039;&#039;mythconverg&#039;&#039;&#039; table (Advanced Users)&lt;br /&gt;
&lt;br /&gt;
To correct this issue, please take the following steps:&lt;br /&gt;
Try either of these options:&lt;br /&gt;
&lt;br /&gt;
*1st we check to see if infact there are problem tables by running this in a shell on the core:&lt;br /&gt;
  /etc/init.d/mythtv-backend stop&lt;br /&gt;
  mysqlcheck -c -uroot -p mythconverg &lt;br /&gt;
&lt;br /&gt;
**if there are errors the run&lt;br /&gt;
&lt;br /&gt;
  mysqlcheck -r -uroot -p mythconverg&lt;br /&gt;
&lt;br /&gt;
occasional this does not fix the problem, then try this&lt;br /&gt;
&lt;br /&gt;
  cd /var/lib/mysql/mythconverg&lt;br /&gt;
  /etc/init.d/mythtv-backend stop&lt;br /&gt;
  /etc/init.d/mysql stop&lt;br /&gt;
  myisamchk *.MYI -r&lt;br /&gt;
&lt;br /&gt;
This should correct the issue. In my own testing (golgoj4) after a reboot everything was functioning correctly.&lt;br /&gt;
&lt;br /&gt;
This fix was provided by user Rwilson131 (thanks)&lt;br /&gt;
&lt;br /&gt;
==Electronic Program Guide with xmltv==&lt;br /&gt;
&lt;br /&gt;
*Read the [[MythTV%2C_xmltv_and_channels|xmltv channels guide]].&lt;br /&gt;
&lt;br /&gt;
==  MythTV frontend access to LinuxMCE &amp;amp; MD password ==&lt;br /&gt;
 &lt;br /&gt;
LMCE&#039;s version of MythTV runs a mythbackend server. As long as your versions are close or exact, you should simply have to put the MythTV frontend PC on the same subnet as the core media subnet (default is 192.168.80.1) when running mythfrontend it will ask you for the masterserver backend ip address or hostname (again the default is 192.168.80.1 or dcerouter), after providing this information, you will most likely be able to connect to your content (I do this all the time from my laptop booted to kubuntu 710, and the mythv-frontend package installed) and I can view my recordings and watch TV live from the tuners.&lt;br /&gt;
&lt;br /&gt;
the latest version of MythTV in LMCE is 0.20.2 fixes, so as long as the version you install is of this variant or package level, you should be able to connect up. If you for whatever reason do not wish to attach the myth frontend pc/laptop to the media subnet provided by the core, you will have to make ammendments to your LMCE firewall from the web admin to allow mythtv to talk to it, or simply disable the LMCE firewall so that the mythfrontend can connect to its address.&lt;br /&gt;
&lt;br /&gt;
PASSWORD&lt;br /&gt;
&lt;br /&gt;
You will also have to go into mythtv setup on the lmce core, and get the username and password for the mythtv mysql user. Otherwise you will not be able to connect to the LMCE master backend. &lt;br /&gt;
&lt;br /&gt;
discussion at&lt;br /&gt;
http://forum.linuxmce.org/index.php?topic=5180.0&lt;br /&gt;
&lt;br /&gt;
==EXPERIMENTAL: Update MythTV to VDPAU version on 0810==&lt;br /&gt;
&lt;br /&gt;
If you don&#039;t have a Nvidia cvard on the core then you should probably not update the core  !!!&lt;br /&gt;
&lt;br /&gt;
Otherwise first update the Core and the the MD doing this&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*add avenard repository to /etc/apt/sources.list&lt;br /&gt;
From http://www.avenard.org/media/Ubuntu_Repository/Ubuntu_Repository.html&lt;br /&gt;
&lt;br /&gt;
*Add the signing GPG key&lt;br /&gt;
&lt;br /&gt;
    wget http://www.avenard.org/files/ubuntu-repos/ubuntu-repos.key &amp;amp;&amp;amp; sudo apt-key add ubuntu-repos.key &amp;amp;&amp;amp; rm ubuntu-repos.key&lt;br /&gt;
&lt;br /&gt;
*Add repository 08.10 &lt;br /&gt;
    echo &amp;quot;deb http://www.avenard.org/files/ubuntu-repos intrepid release&amp;quot; | sudo tee /etc/apt/sources.list.d/avenard.list&lt;br /&gt;
&lt;br /&gt;
 apt-get update&lt;br /&gt;
 apt-get install libmyth-0.21-0 libmyth-perl mythtv-backend mythtv-common mythtv-frontend mythtv-transcode-utils pluto-mythtv-player&lt;br /&gt;
&lt;br /&gt;
*update nvidia using the 180.60 packages from avenard&lt;br /&gt;
 apt-get install nvidia-common nvidia-glx-180 nvidia-180-modaliases&lt;br /&gt;
*maybe update alsa to 1.0.20 - I did not do that, but might be that you will have to.&lt;br /&gt;
*reboot&lt;br /&gt;
*run myth setup and add a profile like describved below &amp;quot;quick FAQ&amp;quot; here&lt;br /&gt;
 http://www.avenard.org/media/MythTV_%26_VDPAU/MythTV_%26_VDPAU.html&lt;br /&gt;
&lt;br /&gt;
Quick F.A.Q:&lt;br /&gt;
&lt;br /&gt;
Q: My CPU usage is still very high / my computer still can’t play HD videos&lt;br /&gt;
A: Using VDPAU isn’t automatic, you must create a new TV Playback profile. In mythfrontend, go into Setup -&amp;gt; TV Settings -&amp;gt; Playback -&amp;gt;  Playback Profiles. Create a new playback profile VDPAU.&lt;br /&gt;
&lt;br /&gt;
If you have a nVidia &amp;lt; 8600GT or &amp;lt; 9500GT, use the following profile:&lt;br /&gt;
&amp;lt;      W: 1920 H: 720, decoder: VDPAU, renderer: VDPAU, Deinterlacer: Advanced 2X&lt;br /&gt;
&amp;gt;=    W: 0 H: 720, decoder: VDPAU, renderer: VDPAU, Deinterlacer: Temporal 2X&lt;br /&gt;
&lt;br /&gt;
If you have a nVidia &amp;gt;= 8600GT or &amp;gt;= 9500GT, use the following profile:&lt;br /&gt;
&amp;gt;      W: 0 H: 0, decoder: VDPAU, renderer: VDPAU, Deinterlacer: Advanced 2X&lt;br /&gt;
&lt;br /&gt;
With this profile, your CPU usage during playback should be around 5-10%.&lt;br /&gt;
&lt;br /&gt;
*If mythTV hangs offen, please uncheck &amp;quot;Enable Realtime Priority threads&amp;quot; in TV -&amp;gt; General Playback.&lt;br /&gt;
*Setup your xorg.conf to 1080i&lt;br /&gt;
&lt;br /&gt;
*Add this to xorg.conf after &#039;Driver          &amp;quot;nvidia&amp;quot;&#039; (maybe not needed !!)&lt;br /&gt;
 Option         &amp;quot;TripleBuffer&amp;quot; &amp;quot;True&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==Programmer&#039;s Guide==&lt;br /&gt;
We have created a DCE Device that wraps the MythTV libraries and can receive commands from other DCE devices and use them to control the TV functionality of the mythtv. Supported functionality at this moment comprises the following: Start TV, Stop TV, Tune to channel, Channel Up, Channel Down. The player uses the same mechanisms that the current (as of 0.16 version) MythTv frontend program uses. So for every mythtv installation that currently works the player should work the same way as the current frontend.&lt;br /&gt;
&lt;br /&gt;
In order to be able to do this we had to change the signature of some methods in a class used by the mythfrontend application. The classes in question is the TV class defined in the  &amp;lt;b&amp;gt;libs/libmythtv/tv_play.{h,cpp}&amp;lt;/b&amp;gt; files from the mythtv repository. The changes consist in some method and field access changes (made some previously private methods to be public). This was done in order to be able to control the player programatically and avoid putting synthetic events into the playback windows event queue. The changes only affect the headers and are used to compile the player. The binary should run on any machine with a working 0.16 MythTV installation. &lt;br /&gt;
&lt;br /&gt;
Since we needed to have a resizable playback window we had to make some changes in the way the mythtv playback window is created and displayed. The change is a derived class from the MainMythWindow class which knows about resize events and uses them to resize all child objects inside it. The class is available in the plutohome.com svn repository also (in the &amp;lt;b&amp;gt;MythTV Player&amp;lt;/b&amp;gt; module). &lt;br /&gt;
&lt;br /&gt;
This module does not work currently with a mythfrontend application running. The module will present itself to the server as another mythfrontend client and it will use one tuner on playback (the same way as a mythtfronted will do).&lt;br /&gt;
== For German Speaking Users - and DVB-C ==&lt;br /&gt;
There is a very nice entry in the [http://mythwiki.de/index.php?title=Schnelleinstieg_DVB-C MythWiki]&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=MythTV&amp;diff=19760</id>
		<title>MythTV</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=MythTV&amp;diff=19760"/>
		<updated>2009-07-13T21:29:34Z</updated>

		<summary type="html">&lt;p&gt;Viking: /* Setting up MythTV in LinuxMCE */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| align=&amp;quot;right&amp;quot;&lt;br /&gt;
  | __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
[[Category: Programmer&#039;s Guide]]&lt;br /&gt;
[[Category:Software components]]&lt;br /&gt;
[[Category: Video]]&lt;br /&gt;
[[Category:Tutorials]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;MythTV&#039;&#039;&#039; is a Linux application which turns a PC (with the necessary hardware) into a [[personal video recorder]], a digital multimedia home entertainment system, and a Home Theater Personal Computer. It is used by LinuxMCE to handle viewing and recording of television.&lt;br /&gt;
&lt;br /&gt;
*[http://www.mythtv.org MythTV Main Website]&lt;br /&gt;
*[[Mythweb]] wiki entry&lt;br /&gt;
*[[Mythtv:Skipping_Commercials]] wiki entry&lt;br /&gt;
&lt;br /&gt;
==Setting up MythTV in LinuxMCE==&lt;br /&gt;
(&amp;lt;small&amp;gt;&#039;&#039;If you purchased a Media Director with LinuxMCE pre-installed, you can skip steps 2, 3 and 6 below -- they will have been preconfigured.&amp;lt;/small&amp;gt;)&lt;br /&gt;
&lt;br /&gt;
*Plug in and boot your Media director.&lt;br /&gt;
&lt;br /&gt;
*If you have a PVR capture card, such as the PVR250/350 supported by IVTV, or the newer Blackbird cards (cx88), install any updated firmware available from the manufacturer. (Sometimes an Internet search for &#039;linuxmce&#039; and &#039;firmware&#039; will also locate firmware for your card.)&lt;br /&gt;
&lt;br /&gt;
*Make sure the capture card type is specified in [[LinuxMCE Admin Website]]--&amp;gt;Wizard--&amp;gt;Devices--&amp;gt;Media Directors.&lt;br /&gt;
&lt;br /&gt;
*For each Media Director, select the &#039;Computing&#039; button on either the Orbiter that appears on the media director&#039;s screen (the on-screen orbiter), or using any other Orbiter which is controlling the same room as the Media Director.  Choose &amp;quot;MythTV Setup&amp;quot;.  Myth&#039;s setup utility will appear on the Media Director.  If you launched this from an Orbiter other than the Media Director&#039;s own on-screen Orbiter, that Orbiter will display a keyboard &amp;amp; mouse that you can use (in addition to the media director&#039;s own). In this way you can use a webpad or PDA Orbiter as a wireless keyboard/mouse.&lt;br /&gt;
&lt;br /&gt;
*If you do not use NTSC, go to the &amp;quot;General&amp;quot;--&amp;gt;&amp;quot;Next&amp;quot;--&amp;gt;&amp;quot;Global Backend Setup&amp;quot; page.  Choose your video standard (NTSC, PAL, etc.).  The other default general settings should be fine. Press ESC to return to the Main Myth Setup Menu.&lt;br /&gt;
&lt;br /&gt;
*Choose &amp;quot;Capture Cards&amp;quot;--&amp;gt;&amp;quot;New Capture Card&amp;quot;. &lt;br /&gt;
:* If you have an ivtv or blackbird/cx88 card, choose &amp;quot;MPEG-2 Encoder card (PVR-250/350)&amp;quot;.&lt;br /&gt;
:* If you&#039;re using the cx88/blackbird driver, change the &#039;video0&#039; to &#039;video1&#039;.&lt;br /&gt;
:* If you have got a DVB-s card, as card type use: &#039;&#039;DVB DTV TV-Card (v3.x)&#039;&#039; and select the right frontend (autodetected) below. ATTENTION, Don&#039;t forget to set &#039;&#039;DiSEqC&#039;&#039;, i set to &#039;&#039;Universal (Europe)&#039;&#039;. Otherwise you will not be able to tune (at least that was my experience).&lt;br /&gt;
&lt;br /&gt;
*If your card was properly identified, the video device field should be filled in for you.  If not, try rebooting the Media Director and repeating.  Press ESC to return to the Main Myth Setup Menu.&lt;br /&gt;
&lt;br /&gt;
*Choose &amp;quot;Video Sources&amp;quot; and select your video source.  Refer to the Myth user&#039;s Manual for details. For DVB-s &#039;&#039;Transmitted guide only (EIT)&#039;&#039; is a good start choice. Press ESC to return to the Main Myth Setup Menu.&lt;br /&gt;
&lt;br /&gt;
*Choose &amp;quot;Input connections&amp;quot; to indicate which video source is connected to which input on the capture card.&lt;br /&gt;
&lt;br /&gt;
*Press ESC to exit Myth Setup and return to the LinuxMCE Orbiter screen.&lt;br /&gt;
&lt;br /&gt;
*At this point you will be prompted to run mythfilldatabse.  Select &amp;quot;Yes&amp;quot;.&lt;br /&gt;
:Sadly, as of 0710b3, this command silently fails to run.  To fix this problem:&lt;br /&gt;
:*Open /etc/mythtv/mysql.txt&lt;br /&gt;
:*Copy the value for DBpasswd from that file.&lt;br /&gt;
:*Open /home/linuxmce/.mythtv/mysql.txt (this file was created when you tried to run mythfilldatabse earlier and where linuxmce is the user you created when installing ubuntu - assuming CD installation)&lt;br /&gt;
&lt;br /&gt;
:*Paste the value you copied earlier into the DBpasswd field&lt;br /&gt;
:*Save the file and run mythfilldatabase again.&lt;br /&gt;
:*Go get a coffee&lt;br /&gt;
&lt;br /&gt;
*You will need to do a full reboot of the whole LinuxMCE system (the Core and all Media Directors) before you can watch TV with Myth TV.  You may want to setup all the Media Directors at once, therefore, and then do a complete reboot.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;NOTE:&#039;&#039;&#039; Do not reboot until the Media Directors have had a chance to retrieve the channel data.  You can confirm this by choosing the &#039;TV&#039; button on the Orbiter main menu.  This launches MythTV.  Then choose &amp;quot;Manage Recordings&amp;quot;, &amp;quot;Schedule Recordings&amp;quot;, &amp;quot;Program Guide&amp;quot;.  You should see some program guide data.  If you do not, wait a bit so Myth has a chance to download the guide data.&lt;br /&gt;
&lt;br /&gt;
===Troubleshooting===&lt;br /&gt;
&lt;br /&gt;
*[http://www.mythtv.org MythTV Main Website official Myth website]&lt;br /&gt;
*[http://forum.linuxmce.com LinuxMCE forums]&lt;br /&gt;
&lt;br /&gt;
====MythTV&#039;s Backend doesn&#039;t show any tuners====&lt;br /&gt;
I had an issue where, after adding my information using the setup wizard, the mythbackend process did not show any tuners as being available.  This may have occured because I had deleted my PVR-150 devices and re-added them.  The issue was simply that LinuxMCE did not fill in the device path for the tuner.  The solution was to go in to the &amp;quot;computing&amp;quot; menu and to run MythTV Setup.  Once in the MythTV Setup screen, select Tuners and you&#039;ll probably see your tuners listed without a device path (for example, &amp;quot;MPG:  &amp;quot; instead of &amp;quot;MPG: /dev/video0&amp;quot;.  Simply go into each tuner and select the proper video device and then exit.  You should not have to do anything with the input sources as these would have already been configured by LinuxMCE&lt;br /&gt;
&lt;br /&gt;
====Fixing Errors in MythTV Tables====&lt;br /&gt;
Upon sudden power loss or in some other situations, you may experience odd behavior from MythTV on restart. This includes&lt;br /&gt;
*Scheduled recordings not showing in &#039;Upcoming Recording&#039; in Mythweb&lt;br /&gt;
*Inability to record programs from any interface, be it the on-screen orbiter or Mythweb.&lt;br /&gt;
*Inconsistencies in the &#039;&#039;&#039;mythconverg&#039;&#039;&#039; table (Advanced Users)&lt;br /&gt;
&lt;br /&gt;
To correct this issue, please take the following steps:&lt;br /&gt;
Try either of these options:&lt;br /&gt;
&lt;br /&gt;
*1st we check to see if infact there are problem tables by running this in a shell on the core:&lt;br /&gt;
  /etc/init.d/mythtv-backend stop&lt;br /&gt;
  mysqlcheck -c -uroot -p mythconverg &lt;br /&gt;
&lt;br /&gt;
**if there are errors the run&lt;br /&gt;
&lt;br /&gt;
  mysqlcheck -r -uroot -p mythconverg&lt;br /&gt;
&lt;br /&gt;
occasional this does not fix the problem, then try this&lt;br /&gt;
&lt;br /&gt;
  cd /var/lib/mysql/mythconverg&lt;br /&gt;
  /etc/init.d/mythtv-backend stop&lt;br /&gt;
  /etc/init.d/mysql stop&lt;br /&gt;
  myisamchk *.MYI -r&lt;br /&gt;
&lt;br /&gt;
This should correct the issue. In my own testing (golgoj4) after a reboot everything was functioning correctly.&lt;br /&gt;
&lt;br /&gt;
This fix was provided by user Rwilson131 (thanks)&lt;br /&gt;
&lt;br /&gt;
==Electronic Program Guide with xmltv==&lt;br /&gt;
&lt;br /&gt;
*Read the [[MythTV%2C_xmltv_and_channels|xmltv channels guide]].&lt;br /&gt;
&lt;br /&gt;
==  MythTV frontend access to LinuxMCE &amp;amp; MD password ==&lt;br /&gt;
 &lt;br /&gt;
LMCE&#039;s version of MythTV runs a mythbackend server. As long as your versions are close or exact, you should simply have to put the MythTV frontend PC on the same subnet as the core media subnet (default is 192.168.80.1) when running mythfrontend it will ask you for the masterserver backend ip address or hostname (again the default is 192.168.80.1 or dcerouter), after providing this information, you will most likely be able to connect to your content (I do this all the time from my laptop booted to kubuntu 710, and the mythv-frontend package installed) and I can view my recordings and watch TV live from the tuners.&lt;br /&gt;
&lt;br /&gt;
the latest version of MythTV in LMCE is 0.20.2 fixes, so as long as the version you install is of this variant or package level, you should be able to connect up. If you for whatever reason do not wish to attach the myth frontend pc/laptop to the media subnet provided by the core, you will have to make ammendments to your LMCE firewall from the web admin to allow mythtv to talk to it, or simply disable the LMCE firewall so that the mythfrontend can connect to its address.&lt;br /&gt;
&lt;br /&gt;
PASSWORD&lt;br /&gt;
&lt;br /&gt;
You will also have to go into mythtv setup on the lmce core, and get the username and password for the mythtv mysql user. Otherwise you will not be able to connect to the LMCE master backend. &lt;br /&gt;
&lt;br /&gt;
discussion at&lt;br /&gt;
http://forum.linuxmce.org/index.php?topic=5180.0&lt;br /&gt;
&lt;br /&gt;
==Programmer&#039;s Guide==&lt;br /&gt;
We have created a DCE Device that wraps the MythTV libraries and can receive commands from other DCE devices and use them to control the TV functionality of the mythtv. Supported functionality at this moment comprises the following: Start TV, Stop TV, Tune to channel, Channel Up, Channel Down. The player uses the same mechanisms that the current (as of 0.16 version) MythTv frontend program uses. So for every mythtv installation that currently works the player should work the same way as the current frontend.&lt;br /&gt;
&lt;br /&gt;
In order to be able to do this we had to change the signature of some methods in a class used by the mythfrontend application. The classes in question is the TV class defined in the  &amp;lt;b&amp;gt;libs/libmythtv/tv_play.{h,cpp}&amp;lt;/b&amp;gt; files from the mythtv repository. The changes consist in some method and field access changes (made some previously private methods to be public). This was done in order to be able to control the player programatically and avoid putting synthetic events into the playback windows event queue. The changes only affect the headers and are used to compile the player. The binary should run on any machine with a working 0.16 MythTV installation. &lt;br /&gt;
&lt;br /&gt;
Since we needed to have a resizable playback window we had to make some changes in the way the mythtv playback window is created and displayed. The change is a derived class from the MainMythWindow class which knows about resize events and uses them to resize all child objects inside it. The class is available in the plutohome.com svn repository also (in the &amp;lt;b&amp;gt;MythTV Player&amp;lt;/b&amp;gt; module). &lt;br /&gt;
&lt;br /&gt;
This module does not work currently with a mythfrontend application running. The module will present itself to the server as another mythfrontend client and it will use one tuner on playback (the same way as a mythtfronted will do).&lt;br /&gt;
== For German Speaking Users - and DVB-C ==&lt;br /&gt;
There is a very nice entry in the [http://mythwiki.de/index.php?title=Schnelleinstieg_DVB-C MythWiki]&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=MythTV&amp;diff=19759</id>
		<title>MythTV</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=MythTV&amp;diff=19759"/>
		<updated>2009-07-13T21:27:50Z</updated>

		<summary type="html">&lt;p&gt;Viking: /* Setting up MythTV in LinuxMCE */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| align=&amp;quot;right&amp;quot;&lt;br /&gt;
  | __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
[[Category: Programmer&#039;s Guide]]&lt;br /&gt;
[[Category:Software components]]&lt;br /&gt;
[[Category: Video]]&lt;br /&gt;
[[Category:Tutorials]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;MythTV&#039;&#039;&#039; is a Linux application which turns a PC (with the necessary hardware) into a [[personal video recorder]], a digital multimedia home entertainment system, and a Home Theater Personal Computer. It is used by LinuxMCE to handle viewing and recording of television.&lt;br /&gt;
&lt;br /&gt;
*[http://www.mythtv.org MythTV Main Website]&lt;br /&gt;
*[[Mythweb]] wiki entry&lt;br /&gt;
*[[Mythtv:Skipping_Commercials]] wiki entry&lt;br /&gt;
&lt;br /&gt;
==Setting up MythTV in LinuxMCE==&lt;br /&gt;
(&amp;lt;small&amp;gt;&#039;&#039;If you purchased a Media Director with LinuxMCE pre-installed, you can skip steps 2, 3 and 6 below -- they will have been preconfigured.&amp;lt;/small&amp;gt;)&lt;br /&gt;
&lt;br /&gt;
*Plug in and boot your Media director.&lt;br /&gt;
&lt;br /&gt;
*If you have a PVR capture card, such as the PVR250/350 supported by IVTV, or the newer Blackbird cards (cx88), install any updated firmware available from the manufacturer. (Sometimes an Internet search for &#039;linuxmce&#039; and &#039;firmware&#039; will also locate firmware for your card.)&lt;br /&gt;
&lt;br /&gt;
*Make sure the capture card type is specified in [[LinuxMCE Admin Website]]--&amp;gt;Wizard--&amp;gt;Devices--&amp;gt;Media Directors.&lt;br /&gt;
&lt;br /&gt;
*For each Media Director, select the &#039;Computing&#039; button on either the Orbiter that appears on the media director&#039;s screen (the on-screen orbiter), or using any other Orbiter which is controlling the same room as the Media Director.  Choose &amp;quot;MythTV Setup&amp;quot;.  Myth&#039;s setup utility will appear on the Media Director.  If you launched this from an Orbiter other than the Media Director&#039;s own on-screen Orbiter, that Orbiter will display a keyboard &amp;amp; mouse that you can use (in addition to the media director&#039;s own). In this way you can use a webpad or PDA Orbiter as a wireless keyboard/mouse.&lt;br /&gt;
&lt;br /&gt;
*If you do not use NTSC, go to the &amp;quot;General&amp;quot;--&amp;gt;&amp;quot;Next&amp;quot;--&amp;gt;&amp;quot;Global Backend Setup&amp;quot; page.  Choose your video standard (NTSC, PAL, etc.).  The other default general settings should be fine. Press ESC to return to the Main Myth Setup Menu.&lt;br /&gt;
&lt;br /&gt;
*Choose &amp;quot;Capture Cards&amp;quot;--&amp;gt;&amp;quot;New Capture Card&amp;quot;. &lt;br /&gt;
:* If you have an ivtv or blackbird/cx88 card, choose &amp;quot;MPEG-2 Encoder card (PVR-250/350)&amp;quot;.&lt;br /&gt;
:* If you&#039;re using the cx88/blackbird driver, change the &#039;video0&#039; to &#039;video1&#039;.&lt;br /&gt;
:* If you have got a DVB-s card, as card type use: &#039;&#039;DVB DTV TV-Card (v3.x)&#039;&#039; and select the right frontend (autodetected) below. ATTENTION, Don&#039;t forget to set &#039;&#039;DiSEqC&#039;&#039;, i set to &#039;&#039;Universal (Europe)&#039;&#039;. Otherwise you will not be able to tune (at least that was my experience).&lt;br /&gt;
&lt;br /&gt;
*If your card was properly identified, the video device field should be filled in for you.  If not, try rebooting the Media Director and repeating.  Press ESC to return to the Main Myth Setup Menu.&lt;br /&gt;
&lt;br /&gt;
*Choose &amp;quot;Video Sources&amp;quot; and select your video source.  Refer to the Myth user&#039;s Manual for details.  Press ESC to return to the Main Myth Setup Menu.&lt;br /&gt;
&lt;br /&gt;
*Choose &amp;quot;Input connections&amp;quot; to indicate which video source is connected to which input on the capture card.&lt;br /&gt;
&lt;br /&gt;
*Press ESC to exit Myth Setup and return to the LinuxMCE Orbiter screen.&lt;br /&gt;
&lt;br /&gt;
*At this point you will be prompted to run mythfilldatabse.  Select &amp;quot;Yes&amp;quot;.&lt;br /&gt;
:Sadly, as of 0710b3, this command silently fails to run.  To fix this problem:&lt;br /&gt;
:*Open /etc/mythtv/mysql.txt&lt;br /&gt;
:*Copy the value for DBpasswd from that file.&lt;br /&gt;
:*Open /home/linuxmce/.mythtv/mysql.txt (this file was created when you tried to run mythfilldatabse earlier and where linuxmce is the user you created when installing ubuntu - assuming CD installation)&lt;br /&gt;
&lt;br /&gt;
:*Paste the value you copied earlier into the DBpasswd field&lt;br /&gt;
:*Save the file and run mythfilldatabase again.&lt;br /&gt;
:*Go get a coffee&lt;br /&gt;
&lt;br /&gt;
*You will need to do a full reboot of the whole LinuxMCE system (the Core and all Media Directors) before you can watch TV with Myth TV.  You may want to setup all the Media Directors at once, therefore, and then do a complete reboot.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;NOTE:&#039;&#039;&#039; Do not reboot until the Media Directors have had a chance to retrieve the channel data.  You can confirm this by choosing the &#039;TV&#039; button on the Orbiter main menu.  This launches MythTV.  Then choose &amp;quot;Manage Recordings&amp;quot;, &amp;quot;Schedule Recordings&amp;quot;, &amp;quot;Program Guide&amp;quot;.  You should see some program guide data.  If you do not, wait a bit so Myth has a chance to download the guide data.&lt;br /&gt;
&lt;br /&gt;
===Troubleshooting===&lt;br /&gt;
&lt;br /&gt;
*[http://www.mythtv.org MythTV Main Website official Myth website]&lt;br /&gt;
*[http://forum.linuxmce.com LinuxMCE forums]&lt;br /&gt;
&lt;br /&gt;
====MythTV&#039;s Backend doesn&#039;t show any tuners====&lt;br /&gt;
I had an issue where, after adding my information using the setup wizard, the mythbackend process did not show any tuners as being available.  This may have occured because I had deleted my PVR-150 devices and re-added them.  The issue was simply that LinuxMCE did not fill in the device path for the tuner.  The solution was to go in to the &amp;quot;computing&amp;quot; menu and to run MythTV Setup.  Once in the MythTV Setup screen, select Tuners and you&#039;ll probably see your tuners listed without a device path (for example, &amp;quot;MPG:  &amp;quot; instead of &amp;quot;MPG: /dev/video0&amp;quot;.  Simply go into each tuner and select the proper video device and then exit.  You should not have to do anything with the input sources as these would have already been configured by LinuxMCE&lt;br /&gt;
&lt;br /&gt;
====Fixing Errors in MythTV Tables====&lt;br /&gt;
Upon sudden power loss or in some other situations, you may experience odd behavior from MythTV on restart. This includes&lt;br /&gt;
*Scheduled recordings not showing in &#039;Upcoming Recording&#039; in Mythweb&lt;br /&gt;
*Inability to record programs from any interface, be it the on-screen orbiter or Mythweb.&lt;br /&gt;
*Inconsistencies in the &#039;&#039;&#039;mythconverg&#039;&#039;&#039; table (Advanced Users)&lt;br /&gt;
&lt;br /&gt;
To correct this issue, please take the following steps:&lt;br /&gt;
Try either of these options:&lt;br /&gt;
&lt;br /&gt;
*1st we check to see if infact there are problem tables by running this in a shell on the core:&lt;br /&gt;
  /etc/init.d/mythtv-backend stop&lt;br /&gt;
  mysqlcheck -c -uroot -p mythconverg &lt;br /&gt;
&lt;br /&gt;
**if there are errors the run&lt;br /&gt;
&lt;br /&gt;
  mysqlcheck -r -uroot -p mythconverg&lt;br /&gt;
&lt;br /&gt;
occasional this does not fix the problem, then try this&lt;br /&gt;
&lt;br /&gt;
  cd /var/lib/mysql/mythconverg&lt;br /&gt;
  /etc/init.d/mythtv-backend stop&lt;br /&gt;
  /etc/init.d/mysql stop&lt;br /&gt;
  myisamchk *.MYI -r&lt;br /&gt;
&lt;br /&gt;
This should correct the issue. In my own testing (golgoj4) after a reboot everything was functioning correctly.&lt;br /&gt;
&lt;br /&gt;
This fix was provided by user Rwilson131 (thanks)&lt;br /&gt;
&lt;br /&gt;
==Electronic Program Guide with xmltv==&lt;br /&gt;
&lt;br /&gt;
*Read the [[MythTV%2C_xmltv_and_channels|xmltv channels guide]].&lt;br /&gt;
&lt;br /&gt;
==  MythTV frontend access to LinuxMCE &amp;amp; MD password ==&lt;br /&gt;
 &lt;br /&gt;
LMCE&#039;s version of MythTV runs a mythbackend server. As long as your versions are close or exact, you should simply have to put the MythTV frontend PC on the same subnet as the core media subnet (default is 192.168.80.1) when running mythfrontend it will ask you for the masterserver backend ip address or hostname (again the default is 192.168.80.1 or dcerouter), after providing this information, you will most likely be able to connect to your content (I do this all the time from my laptop booted to kubuntu 710, and the mythv-frontend package installed) and I can view my recordings and watch TV live from the tuners.&lt;br /&gt;
&lt;br /&gt;
the latest version of MythTV in LMCE is 0.20.2 fixes, so as long as the version you install is of this variant or package level, you should be able to connect up. If you for whatever reason do not wish to attach the myth frontend pc/laptop to the media subnet provided by the core, you will have to make ammendments to your LMCE firewall from the web admin to allow mythtv to talk to it, or simply disable the LMCE firewall so that the mythfrontend can connect to its address.&lt;br /&gt;
&lt;br /&gt;
PASSWORD&lt;br /&gt;
&lt;br /&gt;
You will also have to go into mythtv setup on the lmce core, and get the username and password for the mythtv mysql user. Otherwise you will not be able to connect to the LMCE master backend. &lt;br /&gt;
&lt;br /&gt;
discussion at&lt;br /&gt;
http://forum.linuxmce.org/index.php?topic=5180.0&lt;br /&gt;
&lt;br /&gt;
==Programmer&#039;s Guide==&lt;br /&gt;
We have created a DCE Device that wraps the MythTV libraries and can receive commands from other DCE devices and use them to control the TV functionality of the mythtv. Supported functionality at this moment comprises the following: Start TV, Stop TV, Tune to channel, Channel Up, Channel Down. The player uses the same mechanisms that the current (as of 0.16 version) MythTv frontend program uses. So for every mythtv installation that currently works the player should work the same way as the current frontend.&lt;br /&gt;
&lt;br /&gt;
In order to be able to do this we had to change the signature of some methods in a class used by the mythfrontend application. The classes in question is the TV class defined in the  &amp;lt;b&amp;gt;libs/libmythtv/tv_play.{h,cpp}&amp;lt;/b&amp;gt; files from the mythtv repository. The changes consist in some method and field access changes (made some previously private methods to be public). This was done in order to be able to control the player programatically and avoid putting synthetic events into the playback windows event queue. The changes only affect the headers and are used to compile the player. The binary should run on any machine with a working 0.16 MythTV installation. &lt;br /&gt;
&lt;br /&gt;
Since we needed to have a resizable playback window we had to make some changes in the way the mythtv playback window is created and displayed. The change is a derived class from the MainMythWindow class which knows about resize events and uses them to resize all child objects inside it. The class is available in the plutohome.com svn repository also (in the &amp;lt;b&amp;gt;MythTV Player&amp;lt;/b&amp;gt; module). &lt;br /&gt;
&lt;br /&gt;
This module does not work currently with a mythfrontend application running. The module will present itself to the server as another mythfrontend client and it will use one tuner on playback (the same way as a mythtfronted will do).&lt;br /&gt;
== For German Speaking Users - and DVB-C ==&lt;br /&gt;
There is a very nice entry in the [http://mythwiki.de/index.php?title=Schnelleinstieg_DVB-C MythWiki]&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Viking&amp;diff=19758</id>
		<title>User:Viking</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Viking&amp;diff=19758"/>
		<updated>2009-07-13T20:11:58Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[category:User Setups]]&lt;br /&gt;
&lt;br /&gt;
This is my system.&lt;br /&gt;
&lt;br /&gt;
1st MD TV :&lt;br /&gt;
* [[Sony_KDL-46W4500]] - 1080p resolution UI2 overlay interface&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Core :&lt;br /&gt;
* ASUS M3A-H/HDMI&lt;br /&gt;
* AMD Athlon 64 X2 5050e Sockel-AM2 Box&lt;br /&gt;
* be quiet Straight Power 350W ATX 2.2 &lt;br /&gt;
* Arctic Cooling Freezer 64 Pro PMW&lt;br /&gt;
* 2x DDR2-800 2048MB &lt;br /&gt;
* 2x Arctic Cooling 120x120x25 AF12025 PWM &lt;br /&gt;
* Pioneer DVR-216DBK black&lt;br /&gt;
* Sharkoon Revenge Economy Edition Case - black &lt;br /&gt;
* 3 x 1TB Samsung Spinpoint F1 HD103UI EcoGreen (in RAID5)&lt;br /&gt;
* Longshine LCS-8337TXR (PCI Express)&lt;br /&gt;
* PSU 350W be quiet  E6-350W Straight Power&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
1st MD :&lt;br /&gt;
* NVIDIA 7300GT grafikkort&lt;br /&gt;
* 1xGigabyte GA-MA78GM-S2H   - DON&#039;T buy it for 0710 !!&lt;br /&gt;
* AMD Athlon 64 X2 5050e Sockel-AM2 Box&lt;br /&gt;
* be quiet Straight Power 350W ATX 2.2 &lt;br /&gt;
* Arctic Cooling Freezer 64 Pro PMW&lt;br /&gt;
* 2x DDR2-800 2048MB &lt;br /&gt;
* Pioneer DVR-216DBK black&lt;br /&gt;
* 3 x 1TB Samsung Spinpoint F1 HD103UI EcoGreen (in RAID5)&lt;br /&gt;
* Longshine LCS-8337TXR (PCI Express)&lt;br /&gt;
* PSU 350W be quiet  E6-350W Straight Power&lt;br /&gt;
* Silverstone LC17 case&lt;br /&gt;
&lt;br /&gt;
* USB-UIRT (søg i wiki/forum) infrarød sender/modtager&lt;br /&gt;
* Phillips SRM 5100 (Windows MCE remote control) - apparently not 100% compatible&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Network&lt;br /&gt;
* Digitus N-Way Switch 5 Gigabit ports 5x10/100/1000TX (cheap but OK)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
TV cards &lt;br /&gt;
* TechnoTrend: S2-3200 (not in use yet, so not 100% sure if it works)&lt;br /&gt;
* 2 old TechnoTrend DVB-s cards. 1x 1.6-4MB, 1x 1.3-DVB-s&lt;br /&gt;
* 1 WinTV Nova-s&lt;br /&gt;
* 1 Satelco DVB-C (KNC ONE compatible)&lt;br /&gt;
* 1x Hauppauge WinTV Nova-TD  (DVB-T usb stick) - is probably not going to be used, using DVB-C instead.&lt;br /&gt;
&lt;br /&gt;
Lightcontrol &lt;br /&gt;
* Tricklestar 200ZW-EU-W&lt;br /&gt;
* Seluxit Viasens controlle&lt;br /&gt;
* (the Tricklestar 300ZW-EU-W was replaced by the Viasens as it is better)&lt;br /&gt;
&lt;br /&gt;
And a couple of  Z-wave devices to play with ;)&lt;br /&gt;
* http://www.zwave4u.com/products/en/Lighting-and-Power/PlugIn-Adapters/ACT-Homepro-ZRP-200-Schuko-Plugin-Switch.html&lt;br /&gt;
* http://www.zwave4u.com/products/en/Lighting-and-Power/PlugIn-Adapters/ACT-Homepro-ZDP-200-Schuko-Plugin-Dimmer.html&lt;br /&gt;
* Two Merten 507001&lt;br /&gt;
* One Merten button 508044&lt;br /&gt;
* Two Merten 506004&lt;br /&gt;
* Everspring SM103&lt;br /&gt;
* Everspring SP103&lt;br /&gt;
&lt;br /&gt;
Most of them not implemented yet.&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Viking&amp;diff=19757</id>
		<title>User:Viking</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Viking&amp;diff=19757"/>
		<updated>2009-07-13T20:11:21Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[category:User Setups]]&lt;br /&gt;
&lt;br /&gt;
This is my system.&lt;br /&gt;
&lt;br /&gt;
1st MD TV :&lt;br /&gt;
* [[Sony_KDL-46W4500]] - 1080p resolution UI2 overlay interface&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Core :&lt;br /&gt;
* ASUS M3A-H/HDMI&lt;br /&gt;
* AMD Athlon 64 X2 5050e Sockel-AM2 Box&lt;br /&gt;
* be quiet Straight Power 350W ATX 2.2 &lt;br /&gt;
* Arctic Cooling Freezer 64 Pro PMW&lt;br /&gt;
* 2x DDR2-800 2048MB &lt;br /&gt;
* 2x Arctic Cooling 120x120x25 AF12025 PWM &lt;br /&gt;
* Pioneer DVR-216DBK black&lt;br /&gt;
* Sharkoon Revenge Economy Edition Case - black &lt;br /&gt;
* 3 x 1TB Samsung Spinpoint F1 HD103UI EcoGreen (in RAID5)&lt;br /&gt;
* Longshine LCS-8337TXR (PCI Express)&lt;br /&gt;
* PSU 350W be quiet  E6-350W Straight Power&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
1st MD :&lt;br /&gt;
* NVIDIA 7300GT grafikkort&lt;br /&gt;
* 1xGigabyte GA-MA78GM-S2H&lt;br /&gt;
* AMD Athlon 64 X2 5050e Sockel-AM2 Box&lt;br /&gt;
* be quiet Straight Power 350W ATX 2.2 &lt;br /&gt;
* Arctic Cooling Freezer 64 Pro PMW&lt;br /&gt;
* 2x DDR2-800 2048MB &lt;br /&gt;
* Pioneer DVR-216DBK black&lt;br /&gt;
* 3 x 1TB Samsung Spinpoint F1 HD103UI EcoGreen (in RAID5)&lt;br /&gt;
* Longshine LCS-8337TXR (PCI Express)&lt;br /&gt;
* PSU 350W be quiet  E6-350W Straight Power&lt;br /&gt;
* Silverstone LC17 case&lt;br /&gt;
&lt;br /&gt;
* USB-UIRT (søg i wiki/forum) infrarød sender/modtager&lt;br /&gt;
* Phillips SRM 5100 (Windows MCE remote control) - apparently not 100% compatible&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Network&lt;br /&gt;
* Digitus N-Way Switch 5 Gigabit ports 5x10/100/1000TX (cheap but OK)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
TV cards &lt;br /&gt;
* TechnoTrend: S2-3200 (not in use yet, so not 100% sure if it works)&lt;br /&gt;
* 2 old TechnoTrend DVB-s cards. 1x 1.6-4MB, 1x 1.3-DVB-s&lt;br /&gt;
* 1 WinTV Nova-s&lt;br /&gt;
* 1 Satelco DVB-C (KNC ONE compatible)&lt;br /&gt;
* 1x Hauppauge WinTV Nova-TD  (DVB-T usb stick) - is probably not going to be used, using DVB-C instead.&lt;br /&gt;
&lt;br /&gt;
Lightcontrol &lt;br /&gt;
* Tricklestar 200ZW-EU-W&lt;br /&gt;
* Seluxit Viasens controlle&lt;br /&gt;
* (the Tricklestar 300ZW-EU-W was replaced by the Viasens as it is better)&lt;br /&gt;
&lt;br /&gt;
And a couple of  Z-wave devices to play with ;)&lt;br /&gt;
* http://www.zwave4u.com/products/en/Lighting-and-Power/PlugIn-Adapters/ACT-Homepro-ZRP-200-Schuko-Plugin-Switch.html&lt;br /&gt;
* http://www.zwave4u.com/products/en/Lighting-and-Power/PlugIn-Adapters/ACT-Homepro-ZDP-200-Schuko-Plugin-Dimmer.html&lt;br /&gt;
* Two Merten 507001&lt;br /&gt;
* One Merten button 508044&lt;br /&gt;
* Two Merten 506004&lt;br /&gt;
* Everspring SM103&lt;br /&gt;
* Everspring SP103&lt;br /&gt;
&lt;br /&gt;
Most of them not implemented yet.&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Windows_MCE_Remote&amp;diff=19205</id>
		<title>Windows MCE Remote</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Windows_MCE_Remote&amp;diff=19205"/>
		<updated>2009-05-28T08:01:50Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Input]]&lt;br /&gt;
[[Category:Infrared]]&lt;br /&gt;
&lt;br /&gt;
USB Remote intended for Media Center PCs&lt;br /&gt;
*Vendors Website: http://www.microsoft.com/hardware/mouseandkeyboard/productdetails.aspx?pid=065&lt;br /&gt;
*Supported by LinuxMCE when used with one of the supported [[:Category:Infrared |Infrared Receivers]].&lt;br /&gt;
== Media Center Remotes ==&lt;br /&gt;
&lt;br /&gt;
{| border=1 cellspacing=0 cellpadding=2&lt;br /&gt;
|&lt;br /&gt;
| [[Image:MCEremote.jpg]]&lt;br /&gt;
| [[Image:MCE-Remote-2.jpg | Media Centre Remote 2]]&lt;br /&gt;
| [[Image:MCE-Remote-2-alt.jpg | Media Centre Remote 2 ALT]]&lt;br /&gt;
| [[Image:Mce-hauppauge.jpg | MCE Remote Hauppauge version]]&lt;br /&gt;
| [[Image:MCE-Remote-2-v1069.jpg | MCE Remote Hauppauge Windows Vista version]]&lt;br /&gt;
|-&lt;br /&gt;
| Version&lt;br /&gt;
| &amp;lt;center&amp;gt;1&amp;lt;/center&amp;gt;&lt;br /&gt;
| &amp;lt;center&amp;gt;2&amp;lt;/center&amp;gt;&lt;br /&gt;
| &amp;lt;center&amp;gt;2&amp;lt;/center&amp;gt;&lt;br /&gt;
| &amp;lt;center&amp;gt;2&amp;lt;/center&amp;gt;&lt;br /&gt;
| &amp;lt;center&amp;gt;2&amp;lt;/center&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Model&lt;br /&gt;
| &amp;lt;center&amp;gt;&amp;lt;/center&amp;gt;&lt;br /&gt;
| &amp;lt;center&amp;gt;1039&amp;lt;/center&amp;gt;&lt;br /&gt;
| &amp;lt;center&amp;gt;1039&amp;lt;/center&amp;gt;&lt;br /&gt;
| &amp;lt;center&amp;gt;Hauppauge PVR- kit&amp;lt;/center&amp;gt;&lt;br /&gt;
| &amp;lt;center&amp;gt;1069&amp;lt;/center&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Features&lt;br /&gt;
| &amp;lt;center&amp;gt;Backlight&amp;lt;/center&amp;gt;&lt;br /&gt;
| &amp;lt;center&amp;gt;Backlight&amp;lt;/center&amp;gt;&lt;br /&gt;
| &amp;lt;center&amp;gt;Backlight&amp;lt;/center&amp;gt;&lt;br /&gt;
| &amp;lt;center&amp;gt;&amp;quot;My&amp;quot; Buttons&amp;lt;/center&amp;gt;&lt;br /&gt;
| &amp;lt;center&amp;gt;Uses mceusb2 lircd.conf&amp;lt;/center&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Description===&lt;br /&gt;
There are two main versions of the MCE remote, typically referred to as the &#039;older&#039; (Version 1) and &#039;newer&#039; (Version 2) models. Both of these are now supported in the latest lirc, currently 0.8.1.&lt;br /&gt;
&lt;br /&gt;
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&#039;s own, shipped with MCE 2005 and contained in Hauppauge TV card MCE-Kits. &lt;br /&gt;
&lt;br /&gt;
===Support===&lt;br /&gt;
&lt;br /&gt;
====Version 2 ====&lt;br /&gt;
* [[Windows MCE Receiver|IR Receiver]] is supported&lt;br /&gt;
**The easiest method of installation is via the [[LinuxMCE Admin Website]] &lt;br /&gt;
***Click on [[Media Directors]]&lt;br /&gt;
***Scroll to the bottom of the list of configurable items for Infrared remote controls you will use and select &amp;quot;Windows XP MC Remote&amp;quot; from the drop down list which matches the [[:Category:Infrared |Infrared Receivers]] you have installed, this will automatically update the lircd.conf file.&lt;br /&gt;
***Reload the Router and you should be good to go.&lt;br /&gt;
* IR Transmitter is supported with driver module lirc_mceusb2 version &amp;gt;= 0.24 (lirc-0.8.2). &lt;br /&gt;
**Although not currently Officially supported in LinuxMCE, you can follow the instructions in the following post to get it working:&lt;br /&gt;
***http://wiki.linuxmce.org/index.php/Windows_MCE_Receiver&lt;br /&gt;
* Version 1069 (black remote) comes with a new SMK IR receiver which requires new lirc_mceusb2 (Version 1.30) &lt;br /&gt;
** The new SMK IR receiver requires a newer version of LIRC than currently ships with LinuxMCE 704.&lt;br /&gt;
** Refer to the following forum posts for more information and possible fix: &lt;br /&gt;
*** http://forum.linuxmce.org/index.php?topic=2678.0&lt;br /&gt;
*** http://forum.linuxmce.org/index.php?topic=2517.0&lt;br /&gt;
&lt;br /&gt;
==== Version 1 ====&lt;br /&gt;
* IR Receiver is supported &lt;br /&gt;
* IR Transmitter is not supported&lt;br /&gt;
&lt;br /&gt;
====Hauppauge PVR-150 Remote====&lt;br /&gt;
The [[Hauppauge WinTV-PVR-150 MCE]] comes with an MCE compatible remote, as of LinuxMCE version 0710, it does not work out-of-the-box.  See [[Alx9r&#039;s PVR-150 Remote Setup]] for an example of how to set this remote up.&lt;br /&gt;
&lt;br /&gt;
====Philips SRM 5100 MCE Remote====&lt;br /&gt;
[[Philips_SRM_5100_MCE_Remote]]&lt;br /&gt;
&lt;br /&gt;
==Troubleshooting==&lt;br /&gt;
# 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.&lt;br /&gt;
# 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 &lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
* [[Windows MCE Receiver]]&lt;br /&gt;
* http://www.mythtv.org/wiki/index.php/MCE_Remote&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Philips_SRM_5100_MCE_Remote&amp;diff=19204</id>
		<title>Philips SRM 5100 MCE Remote</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Philips_SRM_5100_MCE_Remote&amp;diff=19204"/>
		<updated>2009-05-28T08:00:07Z</updated>

		<summary type="html">&lt;p&gt;Viking: New page: Category:Hardware Category:Input Category:Infrared  *Vendors Website: http://www.consumer.philips.com/consumer/en/gb/consumer/cc/_productid_SRM5100_10_GB_CONSUMER/Multimedia-Re...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Hardware]]&lt;br /&gt;
[[Category:Input]]&lt;br /&gt;
[[Category:Infrared]]&lt;br /&gt;
&lt;br /&gt;
*Vendors Website: http://www.consumer.philips.com/consumer/en/gb/consumer/cc/_productid_SRM5100_10_GB_CONSUMER/Multimedia-Remote-Control+SRM5100-10&lt;br /&gt;
*&#039;&#039;&#039;NOT RECCOMENDED&#039;&#039;&#039; for LinuxMCE 0710 (not tested with 0810)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You have to install a newer version of LIRC or at least a newer driver.&lt;br /&gt;
The remote is not working fully - the colour buttons are not usable in VDR&lt;br /&gt;
&lt;br /&gt;
But WORST of all the reciever also reacts on light from my Sony LCD TV :( so it is almost unusable&lt;br /&gt;
&lt;br /&gt;
There are some workarounds getting it working with 0710 - but I never got happy with it.&lt;br /&gt;
Viking&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Tricklestar_300ZW-EU-W&amp;diff=19137</id>
		<title>Tricklestar 300ZW-EU-W</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Tricklestar_300ZW-EU-W&amp;diff=19137"/>
		<updated>2009-05-22T07:52:29Z</updated>

		<summary type="html">&lt;p&gt;Viking: /* Status */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Hardware]]&lt;br /&gt;
[[Category: RF Control]]&lt;br /&gt;
[[Category: ZWave]]&lt;br /&gt;
&lt;br /&gt;
[[Image:300ZW-XX-W-(HI-RES).jpg|thumb|200px|Tricklestar 300ZW-EU-W]]&lt;br /&gt;
&lt;br /&gt;
= Status =&lt;br /&gt;
&#039;&#039;&#039;May 2009 - This dongle is not recommended at the moment as it does not provide stable ZWave enviroment. See also the ZWave driver thread in the forum for more&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
In Europe use this instead : [[Seluxit viaSENS Homecontroller]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Received sample from manufacturer. Will be full Plug and play with the next release (0810). Works on 0710 with some easy tweaks (either manually create the device or add the usb id&#039;s (067b2303) to the #1754 device template: [[ZWave_DeviceTemplate_PlugAndPlay]]).&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;This dongle is available in US and EU frequencies and has the latest Zensys library version&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
To get your zwave devices included into the 300ZW-EU-W or 300ZW-US-W for Linuxmce 710 to control, you will also need a remote like TrickleStar 200ZW-US-W - 2-Button Z-Wave Remote/Inclusion Controller. The alternative and free way would be to download the MAC Widget for a MAC, this has the abiltiy to include your divices into the 300ZW and then the wizard in Linuxmce 710  will see them and auto configure them for you.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;MAC Widget&#039;&#039;&#039;&lt;br /&gt;
http://www.tricklestar.com/html/s02_article/article_view.asp?art_id=210&amp;amp;nav_cat_id=150&amp;amp;nav_top_id=57&lt;br /&gt;
&lt;br /&gt;
= About = &lt;br /&gt;
The Tricklestar 300ZW-EU-W is a USB Z-Wave Controller based on a Zensys chip. It uses a frequency of 868MHz. There is also a US version.&lt;br /&gt;
It uses the latest Z-Wave software, 4.27 from October 2008, with support for all the new command classes, and supports both high speed (4x 40kbps) and standard speed Z-Wave devices.&lt;br /&gt;
&lt;br /&gt;
= USB =&lt;br /&gt;
uses the pl2303 chipset and the same manuf./prod. ids.&lt;br /&gt;
&lt;br /&gt;
= Links =&lt;br /&gt;
http://www.tricklestar.com&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=ZWave&amp;diff=19136</id>
		<title>ZWave</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=ZWave&amp;diff=19136"/>
		<updated>2009-05-22T07:48:58Z</updated>

		<summary type="html">&lt;p&gt;Viking: /* Manual Setup using SIS Mode with the Tricklestar Remote */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| align=&amp;quot;right&amp;quot;&lt;br /&gt;
  | __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
[[Category: Hardware| ]]&lt;br /&gt;
[[Category: RF Control]]&lt;br /&gt;
[[Category: ZWave]]&lt;br /&gt;
[[Category: Programmer&#039;s Guide]]&lt;br /&gt;
&lt;br /&gt;
Z-Wave™ is a wireless RF-based communications technology designed for residential and light commercial control and status reading applications such as meter reading, lighting and appliance control, HVAC, access control, intruder and fire detection.&lt;br /&gt;
&lt;br /&gt;
== Overview ==&lt;br /&gt;
The support from LinuxMCE system is represented by an executable &#039;&#039;&#039;ZWave&#039;&#039;&#039; (it&#039;s placed in /usr/pluto/bin) which is the device implementation and a &#039;&#039;&#039;DeviceTemplate (1754)&#039;&#039;&#039; which is used to create LinuxMCE Devices for ZWave.&lt;br /&gt;
&lt;br /&gt;
Look at the Z-Wave Wiki Category to see pages for different &#039;&#039;&#039;[http://wiki.linuxmce.org/index.php/Category:ZWave Z-Wave devices]&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The source code is available in LinuxMCE&#039;s SVN repository: http://svn.linuxmce.org/svn/branches/LinuxMCE-0810/src/ZWave.&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
=== Open version ===&lt;br /&gt;
The new open Z-Wave driver will be included in the upcoming 0810 release.&lt;br /&gt;
&lt;br /&gt;
A 32bit binary of the new Z-Wave driver for 0710 can be found here: http://vt100.at/files/ZWave-0.0.2-0710-32bit.bz2&lt;br /&gt;
Just swap with the existing /usr/pluto/bin/ZWave and quick reload the router.&lt;br /&gt;
&lt;br /&gt;
=== New Fiire driver ===&lt;br /&gt;
Fiire also provides a new Z-Wave driver, it is binary only: [[Fiire ZWave Patch]]&lt;br /&gt;
&lt;br /&gt;
=== Old version ===&lt;br /&gt;
This is the version shipped with 0710. The source code for the old version is not available as it depends on proprietary files from Zensys.&lt;br /&gt;
&lt;br /&gt;
== Interfaces ==&lt;br /&gt;
=== Supported ===&lt;br /&gt;
* [[ACT Homepro ZCS000]]&lt;br /&gt;
* [[ACT Homepro ZCS010]]&lt;br /&gt;
* [[ACT Homepro ZCS101]]&lt;br /&gt;
* [[ACT Homepro ZCS201]]&lt;br /&gt;
* [[ACT Homepro ZCU000]]&lt;br /&gt;
* [[ACT Homepro ZCU010]]&lt;br /&gt;
* [[Intermatic HA22]]&lt;br /&gt;
* [[Intermatic HA23C]]&lt;br /&gt;
* [[Intermatic HA20C]]&lt;br /&gt;
* [[MCV_Z-Wave_Dongle|Mi Casa Verde USB + Inclusion Controller in one]]&lt;br /&gt;
* [[Seluxit viaSENS Homecontroller]]&lt;br /&gt;
* [[Tricklestar 300ZW-US-W]]&lt;br /&gt;
* [[Tricklestar 300ZW-EU-W]]&lt;br /&gt;
&lt;br /&gt;
=== UNSUPPORTED ===&lt;br /&gt;
&#039;&#039;&#039;those don&#039;t work&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* [[ACT Homepro ZCU101]]&lt;br /&gt;
* [[ACT Homepro ZCU201]]&lt;br /&gt;
&lt;br /&gt;
== How to install and use ZWave ==&lt;br /&gt;
=== Automatic installation - Lighting Wizard ===&lt;br /&gt;
The [[Lighting Wizard]] allows you to easily integrate LinuxMCE into your Z-Wave network. It is started after you plug in the Z-Wave dongle. Just follow the onscreen instructions.&lt;br /&gt;
&lt;br /&gt;
=== Manual Setup using SIS Mode with the Tricklestar Remote ===&lt;br /&gt;
SIS mode currently needs either the Seluxit ViaSens ZWave USB controller installed or the new Tricklestar USB Controller (see here for info on installing this controller [[ZWave_DeviceTemplate_PlugAndPlay | ZWave Device Template Plug&#039;n&#039;Play]]). Please note that you cannot currently use the Lighting Wizard when configuring SIS mode. You will also need to update to a current version of the new Open ZWave binary.&lt;br /&gt;
&lt;br /&gt;
# Firstly reset your ZWave USB controller so that you can start to add devices in SIS mode. Use Web Admin -&amp;gt;Wizard-&amp;gt;Devices-&amp;gt;Interfaces and find the device called &#039;ZWave&#039; and click its &#039;Advanced&#039; button. In the next screen click on &#039;Send command to device&#039; and then select &#039;Reset&#039; from the drop-down list, Tick &#039;Delivery Confirmation&#039; and then click &#039;Send Message&#039;. Now if you see &#039;Message received OK&#039; your ZWave USB controller has been successfully reset.&lt;br /&gt;
# Next we need to include your Tricklestar remote into your ZWave network. Firstly we need to set the remote into Configuration Mode (see also the manual) this is done with the little switch on the bottom side next to the USB connector. Then do the following button presses on the Tricklestar remote which should be in close proximity to the ZWave USB interface - Press and hold the Remotes top most button down until you see a Green LED light up then release the button and press it briefly again. The Green LED should now be blinking slowly (if it isn&#039;t then repeat this step again). Now back in Web Admin use the &#039;Send Command to Device&#039; screen again and select &#039;Download Configuration&#039; from the drop-down. Now click &#039;Send Message&#039; and watch the slowly flashing Green LED on the remote. If the LED stops flashing and glows continuously green for a few seconds then you have succeeded in including the Remote. However if you see a Red LED displayed continuously for a few secs something went wrong - in this case please repeat this whole step again. Assuming you got a Green LED at the end of this step you should (after waiting a couple of minutes for the inclusion prcess to finish) do a reload router before continuing. NOTE: If it does not work that way, try sending the &#039;Download Configuration&#039; command first and then press and hold the Remotes top most button down until it goes green and the press the same button again shortly, that way around it worked better for me (was a tip from Hari).&lt;br /&gt;
# Next we can Include each of your ZWave devices into the ZWave network (before starting to include devices it is important that they are located and fixed in their final locations). Using the Tricklestar remote go to each ZWave device (again you should be in close proximity to each device as you Include them) and do the following;&lt;br /&gt;
## Press and hold the Remotes top most button down until you see a Green LED light up then release the button and press it briefly again. The Green LED should now be blinking slowly (if it isn&#039;t then repeat this step again).&lt;br /&gt;
## Now briefly press the Inclusion button on the device you are including. You should see the remotes Green LED stop flashing and glow continuously Green for a few seconds. If you did then you have succeeded in including the device. However if you see a Red LED displayed continuously for a few secs something went wrong - in this case please repeat this whole step again.&lt;br /&gt;
## Repeat the step above for each ZWave device would like to include in your ZWave network.&lt;br /&gt;
# After including your last ZWave device, go back to Web Admin, do a reload router (or maybe two if LinuxMCE tells you to) and select Wizards-&amp;gt;Devices-&amp;gt;Lights. You should now see all the devices you included have been auto-magically added to the &#039;Wizard: Lights&#039; screen! This is power of SIS mode! Now you can change your device names in the &#039;Description&#039; field, select which &#039;Room&#039; they are actually in and use &#039;PK_FloorplanObjectType&#039; drop-down to select the floor plan icon they will display when placed on the floor plan etc. When you have updated this info for each ZWave device click &#039;Update&#039; at the bottom of the screen.&lt;br /&gt;
# If devices are not added automatically - meaning there is no popup on the Orbiters showing &amp;quot;added new device X&amp;quot; - then you can try this. If you have added logging you wil see in /var/log/pluto/*_ZWave.log&amp;quot; that lightswitches are detected by the USB controller because it shows up like this &amp;quot;Got basic report from node X, value: X&amp;quot;. After addind the first device go to the USB Controller and do a &#039;Download Configuration&#039; like above again - but this time &#039;&#039;&#039;without&#039;&#039;&#039; doing a &#039;reset&#039; first. Then do a quick reload router once or twice and try adding the next device. Now it should work.&lt;br /&gt;
&lt;br /&gt;
Of course at anytime when you want to add some new ZWave devices to your installation just do the inclusion steps above with the remote &amp;amp; the device your adding - you dont need to add all your devices in one go. Each time you include a new device just do a reload router and auto-magically it will be in your ZWave devices tree.&lt;br /&gt;
&lt;br /&gt;
Note, you should never do the download config again after you have initially added the USB controller to the Tricklestar remote. To add a new node just put the Tricklestar into config mode with the switch and then add the new nodes with the &amp;quot;up till flash- up&amp;quot; procedure. Same for device removal. The Tricklestar will notify the USB controller about the change. This is automatically detected by LinuxMCE and you will see a popup on all orbiters with the new zwave node id.&lt;br /&gt;
&lt;br /&gt;
=== Manual Excluding devices using SIS Mode with the Tricklestar Remote ===&lt;br /&gt;
&lt;br /&gt;
Why do I have to do this ? (Quote from hari)&lt;br /&gt;
Z-Wave is a mesh. The routing table is updated at inclusion/exclusion. When you move stuff around without following the procedure (except portable devices like remote controllers) you can get network problems.&lt;br /&gt;
&lt;br /&gt;
# Put the Configuration Switch of the Trickestar Remote in “Configuration Mode” like this. Press-and-hold “Up” Operation button for 2 seconds to enter Configuration Mode. LED Indicator will illuminate Green. Short-press the “Down” Operation Button one time to put the device into Exclusion Mode. The Green LED should now be blinking slowly (if it isn&#039;t then repeat this step again).&lt;br /&gt;
# Press the Exclusion Initiator of the Device to be Excluded (normally the same button as the Inclusion Initiator).&lt;br /&gt;
# LED Indicator on the Remote will illuminate Green when device is successfully excluded and illuminate Red if the operation is unsuccessful. Orbiters will show a message that the device is removed.&lt;br /&gt;
# Repeat steps 2-4 for each Device to be Excluded from the Network.&lt;br /&gt;
# After Excluding all the devices that you would like to remove, go back to Web Admin, do a reload router and select Wizards-&amp;gt;Devices-&amp;gt;Lights. The Excluded devices should now be gone.&lt;br /&gt;
&lt;br /&gt;
=== Manual setup / Download configuration ===&lt;br /&gt;
Once you have successfully installed the ZWave USB controller and it is seen on LinuxMCE ([[media:zwave_homepro_interface.png]]), you can proceed by populating the ZWave network information to LinuxMCE.&lt;br /&gt;
&lt;br /&gt;
# Add your ZWave devices to your master ZWave master remote controller (like ZTH200)&lt;br /&gt;
#* Once the devices are added to remote and verified they are working (you can control them with your remote controller), you need to copy the ZWave network information to LinuxMCE.&lt;br /&gt;
# Go to LinuxMCE admin page (&amp;lt;nowiki&amp;gt;&amp;quot;http://192.168.80.1/pluto-admin/&amp;quot;&amp;lt;/nowiki&amp;gt;), then choose &amp;quot;Wizard -&amp;gt; Devices -&amp;gt; Interfaces -&amp;gt; [your ZWave controller] -&amp;gt; Advanced&amp;quot;.&lt;br /&gt;
## On the device page select &amp;quot;Send command to device&amp;quot;.&lt;br /&gt;
## Select command &amp;quot;Download Configuration&amp;quot; and choose &amp;quot;Send Message&amp;quot;.&lt;br /&gt;
##* Leave the data and file fields as blank&lt;br /&gt;
# Now LinuxMCE is waiting for the ZWave information and you should send a copy of the ZWave network with your master remote controller to LinuxMCE.&lt;br /&gt;
#* If you are using HomePro remote controller this is done by selecting: &amp;quot;Setup -&amp;gt; Copy Remote Ctrl. -&amp;gt; Send Information -&amp;gt; Identical Copy&amp;quot;. Once you have done that, the remote will show &amp;quot;Sending information...&amp;quot; and after successful sending it will return to clock screen (this shouldn&#039;t take more than couple of minutes).&lt;br /&gt;
#* You can monitor the process by watching the Zwave log file on LinuxMCE (usually &amp;quot;/var/log/pluto/*ZWave.log&amp;quot;). Unfortunately the admin page doesn&#039;t give much information of what is being done and is everything going smoothly. If the process is successfully, you should see the LinuxMCE communicating with the USB controller&lt;br /&gt;
#* Make sure the sending remote controller is near enough the USB receiver, otherwise nothing will happen.&lt;br /&gt;
# Go to device tree (Show devices tree) and you should see ([[Media:zwave_devices_tree.png]]) the newly added ZWave modules/devices on the tree under &amp;quot;CORE -&amp;gt; ZWave&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
You should do quick reload (Wizard -&amp;gt; Restart -&amp;gt; Quick Reload Router) in order to use the newly added devices with LinuxMCE. Once you have done that you should be able to control (like switching on/off) the devices under the  Light ([[Media:zwave_lights.png]]).&lt;br /&gt;
&lt;br /&gt;
== PIR (Binary Sensor) support ==&lt;br /&gt;
&lt;br /&gt;
[[ACT Homepro Motion Detector]]&lt;br /&gt;
&lt;br /&gt;
== Z-Wave API documentation ==&lt;br /&gt;
&lt;br /&gt;
[[ZWave API]]&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Viking&amp;diff=19000</id>
		<title>User:Viking</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Viking&amp;diff=19000"/>
		<updated>2009-05-14T11:24:19Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[category:User Setups]]&lt;br /&gt;
&lt;br /&gt;
This is my system.&lt;br /&gt;
&lt;br /&gt;
1st MD TV :&lt;br /&gt;
* [[Sony_KDL-46W4500]] - 1080p resolution UI2 overlay interface&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Core :&lt;br /&gt;
* ASUS M3A-H/HDMI&lt;br /&gt;
* AMD Athlon 64 X2 5050e Sockel-AM2 Box&lt;br /&gt;
* be quiet Straight Power 350W ATX 2.2 &lt;br /&gt;
* Arctic Cooling Freezer 64 Pro PMW&lt;br /&gt;
* 2x DDR2-800 2048MB &lt;br /&gt;
* 2x Arctic Cooling 120x120x25 AF12025 PWM &lt;br /&gt;
* Pioneer DVR-216DBK black&lt;br /&gt;
* Sharkoon Revenge Economy Edition Case - black &lt;br /&gt;
* 3 x 1TB Samsung Spinpoint F1 HD103UI EcoGreen (in RAID5)&lt;br /&gt;
* Longshine LCS-8337TXR (PCI Express)&lt;br /&gt;
* PSU 350W be quiet  E6-350W Straight Power&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
1st MD :&lt;br /&gt;
* NVIDIA 7300GT grafikkort&lt;br /&gt;
* 1xGigabyte GA-MA78GM-S2H&lt;br /&gt;
* AMD Athlon 64 X2 5050e Sockel-AM2 Box&lt;br /&gt;
* be quiet Straight Power 350W ATX 2.2 &lt;br /&gt;
* Arctic Cooling Freezer 64 Pro PMW&lt;br /&gt;
* 2x DDR2-800 2048MB &lt;br /&gt;
* Pioneer DVR-216DBK black&lt;br /&gt;
* 3 x 1TB Samsung Spinpoint F1 HD103UI EcoGreen (in RAID5)&lt;br /&gt;
* Longshine LCS-8337TXR (PCI Express)&lt;br /&gt;
* PSU 350W be quiet  E6-350W Straight Power&lt;br /&gt;
* Silverstone LC17 case&lt;br /&gt;
&lt;br /&gt;
* USB-UIRT (søg i wiki/forum) infrarød sender/modtager&lt;br /&gt;
* Phillips SRM 5100 (Windows MCE remote control) - apparently not 100% compatible&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Network&lt;br /&gt;
* Digitus N-Way Switch 5 Gigabit ports 5x10/100/1000TX (cheap but OK)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
TV cards &lt;br /&gt;
* TechnoTrend: S2-3200 (not in use yet, so not 100% sure if it works)&lt;br /&gt;
* 2 old TechnoTrend DVB-s cards. 1x 1.6-4MB, 1x 1.3-DVB-s&lt;br /&gt;
* 1 WinTV Nova-s&lt;br /&gt;
* 1 Satelco DVB-C (KNC ONE compatible)&lt;br /&gt;
* 1x Hauppauge WinTV Nova-TD  (DVB-T usb stick) - is probably not going to be used, using DVB-C instead.&lt;br /&gt;
&lt;br /&gt;
Lightcontrol &lt;br /&gt;
* Tricklestar 200ZW-EU-W&lt;br /&gt;
* Tricklestar 300ZW-EU-W&lt;br /&gt;
&lt;br /&gt;
And a couple of  Z-wave devices to play with ;)&lt;br /&gt;
* http://www.zwave4u.com/products/en/Lighting-and-Power/PlugIn-Adapters/ACT-Homepro-ZRP-200-Schuko-Plugin-Switch.html&lt;br /&gt;
* http://www.zwave4u.com/products/en/Lighting-and-Power/PlugIn-Adapters/ACT-Homepro-ZDP-200-Schuko-Plugin-Dimmer.html&lt;br /&gt;
* Two Merten 507001&lt;br /&gt;
* One Merten button 508044&lt;br /&gt;
* Two Merten 506004&lt;br /&gt;
* Everspring SM103&lt;br /&gt;
* Everspring SP103&lt;br /&gt;
&lt;br /&gt;
Most of them not implemented yet.&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=ZWave&amp;diff=18657</id>
		<title>ZWave</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=ZWave&amp;diff=18657"/>
		<updated>2009-04-25T16:12:14Z</updated>

		<summary type="html">&lt;p&gt;Viking: /* Manual Excluding devices using SIS Mode with the Tricklestar Remote */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| align=&amp;quot;right&amp;quot;&lt;br /&gt;
  | __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
[[Category: Hardware| ]]&lt;br /&gt;
[[Category: RF Control]]&lt;br /&gt;
[[Category: ZWave]]&lt;br /&gt;
[[Category: Programmer&#039;s Guide]]&lt;br /&gt;
&lt;br /&gt;
Z-Wave™ is a wireless RF-based communications technology designed for residential and light commercial control and status reading applications such as meter reading, lighting and appliance control, HVAC, access control, intruder and fire detection.&lt;br /&gt;
&lt;br /&gt;
== Overview ==&lt;br /&gt;
The support from LinuxMCE system is represented by an executable &#039;&#039;&#039;ZWave&#039;&#039;&#039; (it&#039;s placed in /usr/pluto/bin) which is the device implementation and a &#039;&#039;&#039;DeviceTemplate (1754)&#039;&#039;&#039; which is used to create LinuxMCE Devices for ZWave.&lt;br /&gt;
&lt;br /&gt;
Look at the Z-Wave Wiki Category to see pages for different &#039;&#039;&#039;[http://wiki.linuxmce.org/index.php/Category:ZWave Z-Wave devices]&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The source code is available in LinuxMCE&#039;s SVN repository: http://svn.linuxmce.org/svn/branches/LinuxMCE-0810/src/ZWave.&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
=== Open version ===&lt;br /&gt;
The new open Z-Wave driver will be included in the upcoming 0810 release.&lt;br /&gt;
&lt;br /&gt;
A 32bit binary of the new Z-Wave driver for 0710 can be found here: http://vt100.at/files/ZWave-0.0.2-0710-32bit.bz2&lt;br /&gt;
Just swap with the existing /usr/pluto/bin/ZWave and quick reload the router.&lt;br /&gt;
&lt;br /&gt;
=== New Fiire driver ===&lt;br /&gt;
Fiire also provides a new Z-Wave driver, it is binary only: [[Fiire_ZWave_Patch]]&lt;br /&gt;
=== Old version ===&lt;br /&gt;
This is the version shipped with 0710. The source code for the old version is not available as it depends on proprietary files from Zensys.&lt;br /&gt;
&lt;br /&gt;
== Interfaces ==&lt;br /&gt;
=== Supported ===&lt;br /&gt;
* [[ACT Homepro ZCS000]]&lt;br /&gt;
* [[ACT Homepro ZCS010]]&lt;br /&gt;
* [[ACT Homepro ZCS101]]&lt;br /&gt;
* [[ACT Homepro ZCS201]]&lt;br /&gt;
* [[ACT Homepro ZCU000]]&lt;br /&gt;
* [[ACT Homepro ZCU010]]&lt;br /&gt;
* [[Intermatic HA22]]&lt;br /&gt;
* [[Intermatic HA23C]]&lt;br /&gt;
* [[MCV_Z-Wave_Dongle|Mi Casa Verde USB + Inclusion Controller in one]]&lt;br /&gt;
* [[Seluxit viaSENS Homecontroller]]&lt;br /&gt;
* [[Tricklestar 300ZW-US-W]]&lt;br /&gt;
* [[Tricklestar 300ZW-EU-W]]&lt;br /&gt;
=== UNSUPPORTED ===&lt;br /&gt;
&#039;&#039;&#039;those don&#039;t work&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* [[ACT Homepro ZCU101]]&lt;br /&gt;
* [[ACT Homepro ZCU201]]&lt;br /&gt;
&lt;br /&gt;
== How to install and use ZWave ==&lt;br /&gt;
=== Automatic installation - Lighting Wizard ===&lt;br /&gt;
The [[Lighting Wizard]] allows you to easily integrate LinuxMCE into your Z-Wave network. It is started after you plug in the Z-Wave dongle. Just follow the onscreen instructions.&lt;br /&gt;
&lt;br /&gt;
=== Manual Setup using SIS Mode with the Tricklestar Remote ===&lt;br /&gt;
SIS mode currently needs either the Seluxit ViaSens ZWave USB controller installed or the new Tricklestar USB Controller (see here for info on installing this controller [[ZWave_DeviceTemplate_PlugAndPlay]]). You will also need to update to a current version of the new Open ZWave binary.&lt;br /&gt;
&lt;br /&gt;
# Firstly reset your ZWave USB controller so that you can start to add devices in SIS mode. Use Web Admin -&amp;gt;Wizard-&amp;gt;Devices-&amp;gt;Interfaces and find the device called &#039;ZWave&#039; and click its &#039;Advanced&#039; button. In the next screen click on &#039;Send command to device&#039; and then select &#039;Reset&#039; from the drop-down list, Tick &#039;Delivery Confirmation&#039; and then click &#039;Send Message&#039;. Now if you see &#039;Message received OK&#039; your ZWave USB controller has been successfully reset.&lt;br /&gt;
# Next we need to include your Tricklestar remote into your ZWave network. Firstly we need to set the remote into Configuration Mode (see also the manual) this is done with the little switch on the bottom side next to the USB connector. Then do the following button presses on the Tricklestar remote which should be in close proximity to the ZWave USB interface - Press and hold the Remotes top most button down until you see a Green LED light up then release the button and press it briefly again. The Green LED should now be blinking slowly (if it isn&#039;t then repeat this step again). Now back in Web Admin use the &#039;Send Command to Device&#039; screen again and select &#039;Download Configuration&#039; from the drop-down. Now click &#039;Send Message&#039; and watch the slowly flashing Green LED on the remote. If the LED stops flashing and glows continuously green for a few seconds then you have succeeded in including the Remote. However if you see a Red LED displayed continuously for a few secs something went wrong - in this case please repeat this whole step again. Assuming you got a Green LED at the end of this step you should (after waiting a couple of minutes for the inclusion prcess to finish) do a reload router before continuing. NOTE: If it does not work that way, try sending the &#039;Download Configuration&#039; command first and then press and hold the Remotes top most button down until it goes green and the press the same button again shortly, that way around it worked better for me (was a tip from Hari).&lt;br /&gt;
# Next we can Include each of your ZWave devices into the ZWave network (before starting to include devices it is important that they are located and fixed in their final locations). Using the Tricklestar remote go to each ZWave device (again you should be in close proximity to each device as you Include them) and do the following;&lt;br /&gt;
## Press and hold the Remotes top most button down until you see a Green LED light up then release the button and press it briefly again. The Green LED should now be blinking slowly (if it isn&#039;t then repeat this step again).&lt;br /&gt;
## Now briefly press the Inclusion button on the device you are including. You should see the remotes Green LED stop flashing and glow continuously Green for a few seconds. If you did then you have succeeded in including the device. However if you see a Red LED displayed continuously for a few secs something went wrong - in this case please repeat this whole step again.&lt;br /&gt;
## Repeat the step above for each ZWave device would like to include in your ZWave network.&lt;br /&gt;
# After including your last ZWave device, go back to Web Admin, do a reload router (or maybe two if LinuxMCE tells you to) and select Wizards-&amp;gt;Devices-&amp;gt;Lights. You should now see all the devices you included have been auto-magically added to the &#039;Wizard: Lights&#039; screen! This is power of SIS mode! Now you can change your device names in the &#039;Description&#039; field, select which &#039;Room&#039; they are actually in and use &#039;PK_FloorplanObjectType&#039; drop-down to select the floor plan icon they will display when placed on the floor plan etc. When you have updated this info for each ZWave device click &#039;Update&#039; at the bottom of the screen.&lt;br /&gt;
&lt;br /&gt;
Of course at anytime when you want to add some new ZWave devices to your installation just do the inclusion steps above with the remote &amp;amp; the device your adding - you dont need to add all your devices in one go. Each time you include a new device just do a reload router and auto-magically it will be in your ZWave devices tree.&lt;br /&gt;
&lt;br /&gt;
Note, you should never do the download config again after you have initially added the USB controller to the Tricklestar remote. To add a new node just put the Tricklestar into config mode with the switch and then add the new nodes with the &amp;quot;up till flash- up&amp;quot; procedure. Same for device removal. The Tricklestar will notify the USB controller about the change. This is automatically detected by LinuxMCE and you will see a popup on all orbiters with the new zwave node id.&lt;br /&gt;
&lt;br /&gt;
=== Manual Excluding devices using SIS Mode with the Tricklestar Remote ===&lt;br /&gt;
&lt;br /&gt;
Why do I have to do this ? (Quote from hari)&lt;br /&gt;
Z-Wave is a mesh. The routing table is updated at inclusion/exclusion. When you move stuff around without following the procedure (except portable devices like remote controllers) you can get network problems.&lt;br /&gt;
&lt;br /&gt;
# Put the Configuration Switch of the Trickestar Remote in “Configuration Mode” like this. Press-and-hold “Up” Operation button for 2 seconds to enter Configuration Mode. LED Indicator will illuminate Green. Short-press the “Down” Operation Button one time to put the device into Exclusion Mode. The Green LED should now be blinking slowly (if it isn&#039;t then repeat this step again).&lt;br /&gt;
# Press the Exclusion Initiator of the Device to be Excluded (normally the same button as the Inclusion Initiator).&lt;br /&gt;
# LED Indicator on the Remote will illuminate Green when device is successfully excluded and illuminate Red if the operation is unsuccessful. Orbiters will show a message that the device is removed.&lt;br /&gt;
# Repeat steps 2-4 for each Device to be Excluded from the Network.&lt;br /&gt;
# After Excluding all the devices that you would like to remove, go back to Web Admin, do a reload router and select Wizards-&amp;gt;Devices-&amp;gt;Lights. The Excluded devices should now be gone.&lt;br /&gt;
&lt;br /&gt;
=== Manual setup / Download configuration ===&lt;br /&gt;
Once you have successfully installed the ZWave USB controller and it is seen on LinuxMCE ([[media:zwave_homepro_interface.png]]), you can proceed by populating the ZWave network information to LinuxMCE.&lt;br /&gt;
&lt;br /&gt;
# Add your ZWave devices to your master ZWave master remote controller (like ZTH200)&lt;br /&gt;
#* Once the devices are added to remote and verified they are working (you can control them with your remote controller), you need to copy the ZWave network information to LinuxMCE.&lt;br /&gt;
# Go to LinuxMCE admin page (&amp;lt;nowiki&amp;gt;&amp;quot;http://192.168.80.1/pluto-admin/&amp;quot;&amp;lt;/nowiki&amp;gt;), then choose &amp;quot;Wizard -&amp;gt; Devices -&amp;gt; Interfaces -&amp;gt; [your ZWave controller] -&amp;gt; Advanced&amp;quot;.&lt;br /&gt;
## On the device page select &amp;quot;Send command to device&amp;quot;.&lt;br /&gt;
## Select command &amp;quot;Download Configuration&amp;quot; and choose &amp;quot;Send Message&amp;quot;.&lt;br /&gt;
##* Leave the data and file fields as blank&lt;br /&gt;
# Now LinuxMCE is waiting for the ZWave information and you should send a copy of the ZWave network with your master remote controller to LinuxMCE.&lt;br /&gt;
#* If you are using HomePro remote controller this is done by selecting: &amp;quot;Setup -&amp;gt; Copy Remote Ctrl. -&amp;gt; Send Information -&amp;gt; Identical Copy&amp;quot;. Once you have done that, the remote will show &amp;quot;Sending information...&amp;quot; and after successful sending it will return to clock screen (this shouldn&#039;t take more than couple of minutes).&lt;br /&gt;
#* You can monitor the process by watching the Zwave log file on LinuxMCE (usually &amp;quot;/var/log/pluto/*ZWave.log&amp;quot;). Unfortunately the admin page doesn&#039;t give much information of what is being done and is everything going smoothly. If the process is successfully, you should see the LinuxMCE communicating with the USB controller&lt;br /&gt;
#* Make sure the sending remote controller is near enough the USB receiver, otherwise nothing will happen.&lt;br /&gt;
# Go to device tree (Show devices tree) and you should see ([[Media:zwave_devices_tree.png]]) the newly added ZWave modules/devices on the tree under &amp;quot;CORE -&amp;gt; ZWave&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
You should do quick reload (Wizard -&amp;gt; Restart -&amp;gt; Quick Reload Router) in order to use the newly added devices with LinuxMCE. Once you have done that you should be able to control (like switching on/off) the devices under the  Light ([[Media:zwave_lights.png]]).&lt;br /&gt;
&lt;br /&gt;
== PIR (Binary Sensor) support ==&lt;br /&gt;
&lt;br /&gt;
[[ACT_Homepro_Motion_Detector]]&lt;br /&gt;
&lt;br /&gt;
== Z-Wave API documentation ==&lt;br /&gt;
&lt;br /&gt;
[[ZWave_API]]&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Sony_KDL-46W4500&amp;diff=18644</id>
		<title>Sony KDL-46W4500</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Sony_KDL-46W4500&amp;diff=18644"/>
		<updated>2009-04-24T07:23:54Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Hardware]]&lt;br /&gt;
[[Category:Video]]&lt;br /&gt;
[[Category:Displays]]&lt;br /&gt;
&lt;br /&gt;
I am using an &#039;&#039;&#039;European&#039;&#039;&#039; version this TV and will try to describe problems I have here.&lt;br /&gt;
&lt;br /&gt;
Connected to a Nvidia 7300GT with an DVI to HDMI cable.&lt;br /&gt;
&lt;br /&gt;
I was not able to get the TV setup to 1080p with 50hz, so I choosed 1080p and 60hz. Then afterwards I changed the xorg.conf and changed/added the folowing lines :&lt;br /&gt;
&lt;br /&gt;
 Option         &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
 Option         &amp;quot;UseEDID&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 Modes           &amp;quot;1920x1080_50_1&amp;quot; &amp;quot;1920x1080_50_0&amp;quot; &amp;quot;1920x1080_50&amp;quot; &amp;quot;1920x1080&amp;quot; &amp;quot;1920x1080_50i&amp;quot;&lt;br /&gt;
 VertRefresh     49-51&lt;br /&gt;
&lt;br /&gt;
and rebooted. After that I had 50hz.&lt;br /&gt;
&lt;br /&gt;
The line &amp;quot;1920x1080_50&amp;quot; uses the EDID information it gets of the TV and sets things up correctly. In the /var/log/Xorg.0.log you can then see that it chooses the right resolution.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot; is important, otherwise you will get very small unreadable characters.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Alternate solution (I used first).&lt;br /&gt;
&lt;br /&gt;
I was not able to get the TV setup to 1080p with 50hz, so I choosed 1080p and 60hz. Then afterwards I changed the xorg.conf to the right 1080p@50hz Modeline i found in the HDTV list in the MythTV modeline database.&lt;br /&gt;
&lt;br /&gt;
        # 1920x1080 @ 50 Hz (EDID) HSync: 56.25 kHz&lt;br /&gt;
        ModeLine &amp;quot;1920x1080&amp;quot; 148.50 1920 2448 2496 2640 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
&lt;br /&gt;
And changed the VertRefresh to :&lt;br /&gt;
        VertRefresh     49-51&lt;br /&gt;
&lt;br /&gt;
and rebooted. After that I had 50hz.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
My latest xorg.conf&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
  Section &amp;quot;ServerLayout&amp;quot;&lt;br /&gt;
          Identifier      &amp;quot;XFree86 Configured&amp;quot;&lt;br /&gt;
          Screen    0     &amp;quot;Screen0&amp;quot;       0 0&lt;br /&gt;
          InputDevice     &amp;quot;Mouse0&amp;quot;        &amp;quot;CorePointer&amp;quot;&lt;br /&gt;
          InputDevice     &amp;quot;Keyboard0&amp;quot;     &amp;quot;CoreKeyboard&amp;quot;&lt;br /&gt;
  EndSection&lt;br /&gt;
  &lt;br /&gt;
  Section &amp;quot;Files&amp;quot;&lt;br /&gt;
          RgbPath         &amp;quot;/usr/X11R6/lib/X11/rgb&amp;quot;&lt;br /&gt;
          ModulePath      &amp;quot;/usr/lib/xorg/modules&amp;quot;&lt;br /&gt;
          FontPath        &amp;quot;/usr/share/fonts/X11&amp;quot;&lt;br /&gt;
          FontPath        &amp;quot;/usr/X11R6/lib/X11/fonts/misc/&amp;quot;&lt;br /&gt;
          FontPath        &amp;quot;/usr/X11R6/lib/X11/fonts/Speedo/&amp;quot;&lt;br /&gt;
          FontPath        &amp;quot;/usr/X11R6/lib/X11/fonts/Type1/&amp;quot;&lt;br /&gt;
          FontPath        &amp;quot;/usr/X11R6/lib/X11/fonts/CID/&amp;quot;&lt;br /&gt;
          FontPath        &amp;quot;/usr/X11R6/lib/X11/fonts/75dpi/&amp;quot;&lt;br /&gt;
          FontPath        &amp;quot;/usr/X11R6/lib/X11/fonts/100dpi/&amp;quot;&lt;br /&gt;
  EndSection&lt;br /&gt;
  &lt;br /&gt;
  Section &amp;quot;Module&amp;quot;&lt;br /&gt;
          Load    &amp;quot;dbe&amp;quot;&lt;br /&gt;
          Load    &amp;quot;extmod&amp;quot;&lt;br /&gt;
          Load    &amp;quot;record&amp;quot;&lt;br /&gt;
          Load    &amp;quot;xtrap&amp;quot;&lt;br /&gt;
          Load    &amp;quot;speedo&amp;quot;&lt;br /&gt;
          Load    &amp;quot;type1&amp;quot;&lt;br /&gt;
          Load    &amp;quot;glx&amp;quot;&lt;br /&gt;
          Load    &amp;quot;int10&amp;quot;&lt;br /&gt;
          Load    &amp;quot;v4l&amp;quot;&lt;br /&gt;
  EndSection&lt;br /&gt;
  &lt;br /&gt;
  Section &amp;quot;InputDevice&amp;quot;&lt;br /&gt;
          Identifier      &amp;quot;Keyboard0&amp;quot;&lt;br /&gt;
          Driver          &amp;quot;keyboard&amp;quot;&lt;br /&gt;
          Option          &amp;quot;XkbLayout&amp;quot;     &amp;quot;dk&amp;quot;&lt;br /&gt;
          Option          &amp;quot;XkbVariant&amp;quot;    &amp;quot;basic&amp;quot;&lt;br /&gt;
          Option          &amp;quot;XkbModel&amp;quot;              &amp;quot;pc105&amp;quot;&lt;br /&gt;
  EndSection&lt;br /&gt;
  &lt;br /&gt;
  Section &amp;quot;InputDevice&amp;quot;&lt;br /&gt;
          Identifier      &amp;quot;Mouse0&amp;quot;&lt;br /&gt;
          Driver          &amp;quot;mouse&amp;quot;&lt;br /&gt;
          Option          &amp;quot;Protocol&amp;quot;              &amp;quot;auto&amp;quot;&lt;br /&gt;
          Option          &amp;quot;Device&amp;quot;                &amp;quot;/dev/input/mice&amp;quot;&lt;br /&gt;
          Option          &amp;quot;ZAxisMapping&amp;quot;  &amp;quot;4 5&amp;quot;&lt;br /&gt;
  EndSection&lt;br /&gt;
  &lt;br /&gt;
  Section &amp;quot;Monitor&amp;quot;&lt;br /&gt;
          Identifier      &amp;quot;Monitor0&amp;quot;&lt;br /&gt;
          VendorName      &amp;quot;Unknown Monitor Vendor&amp;quot;&lt;br /&gt;
          ModelName       &amp;quot;Unknown Monitor Model&amp;quot;&lt;br /&gt;
  &lt;br /&gt;
          # gtf 1920 1080 50&lt;br /&gt;
          #&lt;br /&gt;
          # 1920x1080 @ 25 Hz (EDID) HSync: 28.125 kHz&lt;br /&gt;
          # 1920x1080 @ 50 Hz (EDID) HSync: 56.25 kHz&lt;br /&gt;
          # ORG Modeline  &amp;quot;1920x1080&amp;quot; 148.5 1920 1960 2016 2200 1080 1082 1088 1125&lt;br /&gt;
          # ORG VertRefresh       59-61&lt;br /&gt;
          # 1920x1080 @ 25 Hz (EDID) HSync: 28.125 kHz&lt;br /&gt;
          # ModeLine &amp;quot;1920x1080&amp;quot; 74.25 1920 2448 2492 2640 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
          # 1920x1080 @ 50 Hz (EDID) HSync: 56.25 kHz&lt;br /&gt;
          # ModeLine &amp;quot;1920x1080&amp;quot; 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
          #&lt;br /&gt;
          # 1920x1080 @ 50 Hz (EDID) HSync: 28.125 kHz&lt;br /&gt;
          ModeLine &amp;quot;1920x1080_my50i&amp;quot; 74.25 1920 2448 2492 2640 1080 1084 1094 1124 +HSync +VSync Interlace&lt;br /&gt;
          #&lt;br /&gt;
          # From Powerstrip 1920x1080 @ 24hz&lt;br /&gt;
          # ModeLine &amp;quot;1920x1080&amp;quot; 74.250 1920 2560 2608 2752 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
          # From Powerstrip 1920x1080 @ 25hz&lt;br /&gt;
          # Xorg.log said 24,9hz / try adding some more&lt;br /&gt;
          # ModeLine &amp;quot;1920x1080&amp;quot; 77.142 1920 2560 2608 2752 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
          ModeLine &amp;quot;1920x1080_my25&amp;quot; 77.500 1920 2560 2608 2752 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
          # VertRefresh   24-26&lt;br /&gt;
          #&lt;br /&gt;
          # From Powerstrip 1920x1080 @ 50hz&lt;br /&gt;
          ModeLine &amp;quot;1920x1080_my50&amp;quot; 148.500 1920 2448 2496 2640 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
          # ModeLine &amp;quot;1920x1080_my50a&amp;quot; 148.750 1920 2448 2496 2640 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
          VertRefresh     24-51&lt;br /&gt;
          HorizSync       20-500&lt;br /&gt;
          # VertRefresh   49-51&lt;br /&gt;
  EndSection&lt;br /&gt;
  &lt;br /&gt;
  Section &amp;quot;Device&amp;quot;&lt;br /&gt;
          ### Available Driver options are:-&lt;br /&gt;
          ### Values: &amp;lt;i&amp;gt;: integer, &amp;lt;f&amp;gt;: float, &amp;lt;bool&amp;gt;: &amp;quot;True&amp;quot;/&amp;quot;False&amp;quot;,&lt;br /&gt;
          ### &amp;lt;string&amp;gt;: &amp;quot;String&amp;quot;, &amp;lt;freq&amp;gt;: &amp;quot;&amp;lt;f&amp;gt; Hz/kHz/MHz&amp;quot;&lt;br /&gt;
          ### [arg]: arg optional&lt;br /&gt;
          #Option         &amp;quot;NoAccel&amp;quot;                               # [&amp;lt;bool&amp;gt;]&lt;br /&gt;
          #Option         &amp;quot;SWcursor&amp;quot;                              # [&amp;lt;bool&amp;gt;]&lt;br /&gt;
          #Option         &amp;quot;ColorKey&amp;quot;                              # &amp;lt;i&amp;gt;&lt;br /&gt;
          #Option         &amp;quot;CacheLines&amp;quot;                    # &amp;lt;i&amp;gt;&lt;br /&gt;
          #Option         &amp;quot;Dac6Bit&amp;quot;                               # [&amp;lt;bool&amp;gt;]&lt;br /&gt;
          #Option         &amp;quot;DRI&amp;quot;                                   # [&amp;lt;bool&amp;gt;]&lt;br /&gt;
          #Option         &amp;quot;NoDDC&amp;quot;                                 # [&amp;lt;bool&amp;gt;]&lt;br /&gt;
          #Option         &amp;quot;ShowCache&amp;quot;                             # [&amp;lt;bool&amp;gt;]&lt;br /&gt;
          #Option         &amp;quot;XvMCSurfaces&amp;quot;                  # &amp;lt;i&amp;gt;&lt;br /&gt;
          Identifier      &amp;quot;Card0&amp;quot;&lt;br /&gt;
          Driver          &amp;quot;nvidia&amp;quot;&lt;br /&gt;
          VendorName      &amp;quot;Unknown Vendor Name&amp;quot;&lt;br /&gt;
          BoardName       &amp;quot;Unknown Board Name&amp;quot;&lt;br /&gt;
          Option          &amp;quot;LinearAlloc&amp;quot;           &amp;quot;16384&amp;quot;&lt;br /&gt;
          #BusID          &amp;quot;PCI:0:2:0&amp;quot;&lt;br /&gt;
  #       Option          &amp;quot;NoDDC&amp;quot;                         &amp;quot;true&amp;quot;&lt;br /&gt;
     Option         &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
     ## Option         &amp;quot;UseEDIDFreqs&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
          Option &amp;quot;XvmcUsesTextures&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          Option &amp;quot;renderAccel&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          Option &amp;quot;NoDDCValue&amp;quot;&lt;br /&gt;
          ## Option &amp;quot;UseEDID&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
          Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          Option &amp;quot;NoLogo&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          Option &amp;quot;NoBandWidthTest&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          # Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes&amp;quot;&lt;br /&gt;
          Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoVertRefreshCheck, NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes&amp;quot;&lt;br /&gt;
          Option &amp;quot;DynamicTwinView&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
          Option &amp;quot;UseEvents&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          Option &amp;quot;AllowGLXWithComposite&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          Option &amp;quot;AddARGBGLXVisuals&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          Option          &amp;quot;ConnectedMonitor&amp;quot; &amp;quot;DFP&amp;quot;&lt;br /&gt;
  EndSection&lt;br /&gt;
  &lt;br /&gt;
  Section &amp;quot;Screen&amp;quot;&lt;br /&gt;
          Identifier      &amp;quot;Screen0&amp;quot;&lt;br /&gt;
          Device          &amp;quot;Card0&amp;quot;&lt;br /&gt;
          Monitor         &amp;quot;Monitor0&amp;quot;&lt;br /&gt;
          DefaultDepth    24&lt;br /&gt;
          SubSection &amp;quot;Display&amp;quot;&lt;br /&gt;
                  # Modes         &amp;quot;1920x1080&amp;quot;&lt;br /&gt;
                  Modes           &amp;quot;1920x1080_50_1&amp;quot; &amp;quot;1920x1080_50_0&amp;quot; &amp;quot;1920x1080_50&amp;quot; &amp;quot;1920x1080_my50&amp;quot;&lt;br /&gt;
                  # Modes         &amp;quot;1920x1080_my50a&amp;quot; &amp;quot;1920x1080_50&amp;quot; &amp;quot;1920x1080_50_0&amp;quot; &amp;quot;1920x1080&amp;quot;&lt;br /&gt;
                  #TESTED Modes           &amp;quot;1920x1080_50_0&amp;quot; &amp;quot;1920x1080_50i_0&amp;quot; &amp;quot;1920x1080_50i&amp;quot; &amp;quot;1920x1080_my50i&amp;quot; &amp;quot;1920x1080_my25&amp;quot; &amp;quot;1920x1080&amp;quot;&lt;br /&gt;
                  Virtual         1920 1080&lt;br /&gt;
          EndSubSection&lt;br /&gt;
     Option         &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
     ## Option         &amp;quot;UseEDIDFreqs&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
          Option &amp;quot;XvmcUsesTextures&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          Option &amp;quot;renderAccel&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          Option &amp;quot;NoDDCValue&amp;quot;&lt;br /&gt;
          ## Option &amp;quot;UseEDID&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
          Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          Option &amp;quot;NoLogo&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          Option &amp;quot;NoBandWidthTest&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          # Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes&amp;quot;&lt;br /&gt;
          Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoVertRefreshCheck, NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes&amp;quot;&lt;br /&gt;
          Option &amp;quot;DynamicTwinView&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
          Option &amp;quot;UseEvents&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          Option &amp;quot;AllowGLXWithComposite&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          Option &amp;quot;AddARGBGLXVisuals&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          Option  &amp;quot;TVStandard&amp;quot;    &amp;quot;1080p&amp;quot;&lt;br /&gt;
  EndSection&lt;br /&gt;
  &lt;br /&gt;
  Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
          Option  &amp;quot;AllowMouseOpenFail&amp;quot;    &amp;quot;true&amp;quot;&lt;br /&gt;
          Option  &amp;quot;BlankTime&amp;quot;             &amp;quot;0&amp;quot;&lt;br /&gt;
          Option  &amp;quot;StandbyTime&amp;quot;   &amp;quot;0&amp;quot;&lt;br /&gt;
          Option  &amp;quot;SuspendTime&amp;quot;   &amp;quot;0&amp;quot;&lt;br /&gt;
          Option  &amp;quot;OffTime&amp;quot;               &amp;quot;0&amp;quot;&lt;br /&gt;
          Option  &amp;quot;AIGLX&amp;quot;                 &amp;quot;Off&amp;quot;&lt;br /&gt;
  EndSection&lt;br /&gt;
  Section &amp;quot;Extensions&amp;quot;&lt;br /&gt;
          Option &amp;quot;Composite&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
          Option &amp;quot;RENDER&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
  EndSection&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Viking&amp;diff=18643</id>
		<title>User:Viking</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Viking&amp;diff=18643"/>
		<updated>2009-04-24T07:21:31Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[category:User Setups]]&lt;br /&gt;
&lt;br /&gt;
This is my system.&lt;br /&gt;
&lt;br /&gt;
1st MD TV :&lt;br /&gt;
* [[Sony_KDL-46W4500]] - 1080p resolution UI2 overlay interface&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Core :&lt;br /&gt;
* ASUS M3A-H/HDMI&lt;br /&gt;
* AMD Athlon 64 X2 5050e Sockel-AM2 Box&lt;br /&gt;
* be quiet Straight Power 350W ATX 2.2 &lt;br /&gt;
* Arctic Cooling Freezer 64 Pro PMW&lt;br /&gt;
* 2x DDR2-800 2048MB &lt;br /&gt;
* 2x Arctic Cooling 120x120x25 AF12025 PWM &lt;br /&gt;
* Pioneer DVR-216DBK black&lt;br /&gt;
* Sharkoon Revenge Economy Edition Case - black &lt;br /&gt;
* 3 x 1TB Samsung Spinpoint F1 HD103UI EcoGreen (in RAID5)&lt;br /&gt;
* Longshine LCS-8337TXR (PCI Express)&lt;br /&gt;
* PSU 350W be quiet  E6-350W Straight Power&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
1st MD :&lt;br /&gt;
* NVIDIA 7300GT grafikkort&lt;br /&gt;
* 1xGigabyte GA-MA78GM-S2H&lt;br /&gt;
* AMD Athlon 64 X2 5050e Sockel-AM2 Box&lt;br /&gt;
* be quiet Straight Power 350W ATX 2.2 &lt;br /&gt;
* Arctic Cooling Freezer 64 Pro PMW&lt;br /&gt;
* 2x DDR2-800 2048MB &lt;br /&gt;
* Pioneer DVR-216DBK black&lt;br /&gt;
* 3 x 1TB Samsung Spinpoint F1 HD103UI EcoGreen (in RAID5)&lt;br /&gt;
* Longshine LCS-8337TXR (PCI Express)&lt;br /&gt;
* PSU 350W be quiet  E6-350W Straight Power&lt;br /&gt;
* Silverstone LC17 case&lt;br /&gt;
&lt;br /&gt;
* USB-UIRT (søg i wiki/forum) infrarød sender/modtager&lt;br /&gt;
* Phillips SRM 5100 (Windows MCE remote control) - apparently not 100% compatible&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Network&lt;br /&gt;
* Digitus N-Way Switch 5 Gigabit ports 5x10/100/1000TX (cheap but OK)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
TV cards &lt;br /&gt;
* TechnoTrend: S2-3200 (not in use yet, so not 100% sure if it works)&lt;br /&gt;
* 2 old TechnoTrend DVB-s cards. 1x 1.6-4MB, 1x 1.3-DVB-s&lt;br /&gt;
* 1 WinTV Nova-s&lt;br /&gt;
* 1 Satelco DVB-C (KNC ONE compatible)&lt;br /&gt;
* 1x Hauppauge WinTV Nova-TD  (DVB-T usb stick) - is probably not going to be used, using DVB-C instead.&lt;br /&gt;
&lt;br /&gt;
Lightcontrol &lt;br /&gt;
* Tricklestar 200ZW-EU-W&lt;br /&gt;
* Tricklestar 300ZW-EU-W&lt;br /&gt;
&lt;br /&gt;
And a couple of  Z-wave devices to play with ;)&lt;br /&gt;
* Everspring SM103&lt;br /&gt;
* Everspring SP103&lt;br /&gt;
* http://www.zwave4u.com/products/en/Lighting-and-Power/PlugIn-Adapters/ACT-Homepro-ZRP-200-Schuko-Plugin-Switch.html&lt;br /&gt;
* http://www.zwave4u.com/products/en/Lighting-and-Power/PlugIn-Adapters/ACT-Homepro-ZDP-200-Schuko-Plugin-Dimmer.html&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Upgrading_the_Kernel&amp;diff=18385</id>
		<title>Upgrading the Kernel</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Upgrading_the_Kernel&amp;diff=18385"/>
		<updated>2009-04-10T22:28:56Z</updated>

		<summary type="html">&lt;p&gt;Viking: /* Asterisk telephony */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:LinuxMCEMaintenance]]&lt;br /&gt;
[[category: tutorials]]&lt;br /&gt;
[[category: programmer&#039;s Guide]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
The ability to change kernel versions at will can be extremely useful for fighting driver bugs and regressions. This article provides procedures for upgrading the kernel.&lt;br /&gt;
&lt;br /&gt;
==LinuxMCE 0810==&lt;br /&gt;
Upgrading kernels is significantly easier in 0810, now that LinxMCE uses the standard Ubuntu kernel.  If you&#039;re interested in using a non-standard kernel, you can adapt the 0710 instructions to your needs.&lt;br /&gt;
&lt;br /&gt;
===Apt Repositories===&lt;br /&gt;
If the kernel version you&#039;re looking for is not available in the standard repositories, you might have to enable the proposed repositories by adding a line that looks something like:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
deb http://ubuntu.media.mit.edu/ubuntu/ intrepid-proposed restricted main universe multiverse&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
to &#039;&#039;/etc/apt/sources.list&#039;&#039;.  Of course, you&#039;ll want to use the package mirror that is closest to you, probably not MIT.  After adding this line, run &#039;&#039;apt-get update&#039;&#039; to refresh the package lists.&lt;br /&gt;
&lt;br /&gt;
===Installing===&lt;br /&gt;
On the core, simply install the new kernel like any other package.  Don&#039;t forget the restricted modules and headers if you need them.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
linuxmce@dcerouter:~$ sudo apt-get install linux-image-2.6.27-13-generic linux-restricted-modules-2.6.27-11-generic linux-headers-2.6.27-11-generic&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
If you always want the most up-to-date kernel, consider installing the package &#039;&#039;[http://packages.ubuntu.com/intrepid/linux linux]&#039;&#039;.  (This is outside of the scope of this article.)&lt;br /&gt;
&lt;br /&gt;
On MDs, there is one extra step. You will need to update some links in &#039;&#039;/boot/&#039;&#039;.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
root@moon44:~# cd /boot/&lt;br /&gt;
root@moon44:/boot# mv initrd.img initrd.img.bk&lt;br /&gt;
root@moon44:/boot# mv vmlinuz vmlinuz.bk&lt;br /&gt;
root@moon44:/boot# ln initrd.img-2.6.27-13-generic initrd.img&lt;br /&gt;
root@moon44:/boot# ln vmlinuz-2.6.27-13-generic vmlinuz&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==LinuxMCE 0710==&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;WARNING:&#039;&#039;&#039;&#039;&#039; This procedure will break certain things and may even make your system unusable, therefore use at your own risk.  Of course, if your system is not working or is unstable anyway, then trying this could improve things!  &lt;br /&gt;
 &lt;br /&gt;
The kernel version that ships with LinuxMCE 0710 is 2.6.22-14. At the time of writing the most recent stable kernel version is 2.6.28.8. The .22 kernel is almost a full year old and as such does not support a lot of the newer hardware.&lt;br /&gt;
&lt;br /&gt;
Note- kernel version 2.6.27 has changes in it (a redefined set of arguments for smp_call_function) which breaks earlier versions of the Nvidia driver.  Nvidia drivers 178.80 and above should work.&lt;br /&gt;
&lt;br /&gt;
====Caveats====&lt;br /&gt;
Some modules that are part of the vanilla Linux MCE installation are not part of the standard Linux kernel. These modules have been added as part of the Ubuntu distribution or by LMCE. It is not always straight forward, or even possible to compile these modules against different kernel sources. I suggest you read this entire Wiki first, to determine if you will be affected by the missing modules.&lt;br /&gt;
&lt;br /&gt;
====Alternatives====&lt;br /&gt;
Usually kernels are upgraded for better driver support. In these cases it is often easier to compile new versions of modules against the 2.6.22-14 kernel than it is to upgrade the whole kernel (for reasons mentioned in the [[Upgrading the Kernel#Caveats|caveats]] section. Unfortunately, a lot of modules depend on other modules or patches in the kernel. So this option is not always possible.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 cd ~&lt;br /&gt;
 wget http://www.somesite.com/some_kernel_driver.c&lt;br /&gt;
 echo obj-m = some_kernel_driver.o &amp;gt; Makefile&lt;br /&gt;
 cd /lib/modules/2.6.22-14-generic/build&lt;br /&gt;
 make M=~ modules&lt;br /&gt;
 ls -l ~/some_kernel_driver.ko&lt;br /&gt;
&lt;br /&gt;
You may then copy the module to the appropriate directory in the modules tree.&lt;br /&gt;
&lt;br /&gt;
===Upgrade process===&lt;br /&gt;
&lt;br /&gt;
This wiki will provide step-by-step instructions on how to upgrade your kernel. These examples will assume you are upgrading to 2.6.26 from 2.6.22. You may however apply these steps to any 2.6 kernel.&lt;br /&gt;
&lt;br /&gt;
An alternative approach is described here [http://www.debian.org/releases/stable/i386/ch08s06.html.en Rebuilding the kernel the debian way].  Anyone using this potentially easier method could update this document.&lt;br /&gt;
&lt;br /&gt;
====Potential problems====&lt;br /&gt;
All the normal issues of upgrading your kernel apply. Always keep your old, working kernel on hand. &lt;br /&gt;
&lt;br /&gt;
====Steps====&lt;br /&gt;
&lt;br /&gt;
=====Recompiling the kernel=====&lt;br /&gt;
The first step is to grab the kernel source and extract it to the /usr/src folder.&lt;br /&gt;
&lt;br /&gt;
 cd /usr/src&lt;br /&gt;
 wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.28.7.tar.bz2&lt;br /&gt;
 tar -jxvf linux-2.6.28.7.tar.bz&lt;br /&gt;
 rm linux&lt;br /&gt;
 ln -s linux-2.6.28.5 linux&lt;br /&gt;
&lt;br /&gt;
Now lets copy the .config file from our generic 2.6.22 kernel.&lt;br /&gt;
 cd linux&lt;br /&gt;
 cp /boot/config-2.6.22-14-generic .config&lt;br /&gt;
&lt;br /&gt;
On our first load of menuconfig there will be many warnings displayed about non-existant config options. This is simply due to the removal or renaming of old options. Most of these warnings are insignificant, and enabled by default in the vanilla kernel. I would quickly go over the list of warnings and verify that any drivers you need haven&#039;t been renamed. One option that has been renamed is DVB_CORE_ATTACH. It is now DVB_MEDIA_ATTACH, and you may need it if you use the DVB stack. Also some netfilter matches have been renamed. Simply reselect these from the config menus. You may also need to install the ncurses library and development files if you haven&#039;t already.&lt;br /&gt;
&lt;br /&gt;
 sudo apt-get install libncurses5 libncurses5-dev qt3-dev-tools libqt3-mt-dev&lt;br /&gt;
&lt;br /&gt;
Then you can either choose to use the character based interface to set your kernel options&lt;br /&gt;
 make menuconfig 2&amp;gt; module_errors&lt;br /&gt;
&lt;br /&gt;
Or you can use the GUI interface&lt;br /&gt;
 DISPLAY=:0.0 make xconfig&lt;br /&gt;
&lt;br /&gt;
It&#039;s also a good idea to go over the kernel and make any optimizations for your particular system. The performance gain from these options is fairly minor, but definitely worth selecting. &lt;br /&gt;
&lt;br /&gt;
I opted to change these things:&lt;br /&gt;
* Selected exact processor family to enable processor optimization extensions&lt;br /&gt;
* Selected preemptive kernel (low latency)&lt;br /&gt;
* Build SATA driver into kernel&lt;br /&gt;
* Build MD,RAID1,RAID5 modules into kernel&lt;br /&gt;
* Build NIC module into kernel&lt;br /&gt;
* Disabled kernel debugging (&#039;&#039;&#039;Note: This is very important if you plan to use this kernel on Media Directors.&#039;&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
At this point you can start the kernel build process. You may use the standard kernel method or the Debian build method. For simplicity this Wiki will use the standard method.&lt;br /&gt;
 make&lt;br /&gt;
 sudo make modules_install&lt;br /&gt;
&lt;br /&gt;
Copy your kernel image to your /boot folder. Create a new initramfs image. Update your menu.lst file.&lt;br /&gt;
&lt;br /&gt;
 cp arch/yyxx/boot/bzImage /boot/vmlinuz-2.6.28.7&lt;br /&gt;
 mkinitramfs -o /boot/initrd.img-2.6.26.5 2.6.28.7&lt;br /&gt;
 nano /boot/grub/menu.lst&lt;br /&gt;
&lt;br /&gt;
Save a list of all currently used modules for future reference. You will use this later to make sure you have all the required modules.&lt;br /&gt;
&lt;br /&gt;
   lsmod &amp;gt; ~/module_list-2.6.22.14&lt;br /&gt;
&lt;br /&gt;
Go ahead and reboot. Your new kernel should now load. If your boot fails, simply edit the parameters from the grub menu and specify your old kernel and initramfs image. Please note: udev attempts to assign persistent names to most devices. If the way the kernel identifies your device changes from your old kernel version to the new one, udev may assume it&#039;s a new device and assign it an unexpected name. For example, the nForce ethernet drivers corrected a bug in the way the MAC address was read from the device. On my first boot what was usually my eth0 device was now my eth1 device. To fix this simply flush the offending rule from the /etc/udev/rules.d folder.&lt;br /&gt;
&lt;br /&gt;
   reboot&lt;br /&gt;
&lt;br /&gt;
=====Additional items which need to be rebuilt=====&lt;br /&gt;
You should now build any custom modules you need. Linux MCE (and Ubuntu) come with some non-standard drivers. The key modules to worry about are AppArmor, Asterisk (ztdummy &amp;amp; zaptel), ALSA, nVidia video, ATI video. You are better off downloading the latest nVidia and ATI drivers and installing them using the instructions found in the [[Display Drivers|display drivers]] wiki. The Gutsy kernel also contains other important video drivers, like ivtv. However most of these drivers are now in the mainstream kernel and more up-to-date than the Gutsy versions.&lt;br /&gt;
&lt;br /&gt;
=====Mythtv=====&lt;br /&gt;
You do not have to rebuild Mythtv, but if you chose to use the new High Precision Event Timer (HPET) instead of the older kernel Real Time Clock (RTC), then Mythtv will not start up because /proc/sys/dev/rtc/max-user-freq does not exist.  This is because the LinuxMCE 7.10 /etc/init.d/mythtv-backend script does not check if it exists before trying to write to it.  You will have to change your /etc/init.d/mythtv-backend script as follows:&lt;br /&gt;
&lt;br /&gt;
 case &amp;quot;$1&amp;quot; in&lt;br /&gt;
    start)&lt;br /&gt;
        if test -e $RUNDIR/$NAME.pid ; then&lt;br /&gt;
            echo &amp;quot;mythbackend already running, use restart instead.&amp;quot;&lt;br /&gt;
        else&lt;br /&gt;
            # set the timeslice to 1/1024 of a sec for smoother mythtv and xine and mplayer playback &lt;br /&gt;
            if [ -w /proc/sys/dev/rtc/max-user-freq ] # check if RTC (older kernels) exists and I can write to it&lt;br /&gt;
                # failure is not an option!&lt;br /&gt;
            then echo 1024 &amp;gt; /proc/sys/dev/rtc/max-user-freq&lt;br /&gt;
        elif [ -w /proc/sys/dev/hpet/max-user-freq ] # or newer kernels with the High Precision Timer (HPET)&lt;br /&gt;
            # may or may not emulate the older RTC fully&lt;br /&gt;
        then echo 1024 &amp;gt; /proc/sys/dev/hpet/max-user-freq&lt;br /&gt;
    fi # start starting the startup of mythtv &lt;br /&gt;
 echo -n &amp;quot;Starting $DESC: $NAME &amp;quot; start-stop-daemon --start --pidfile $RUNDIR/$NAME.pid \ &lt;br /&gt;
&lt;br /&gt;
=====Apparmor=====&lt;br /&gt;
I have decided to forgo the AppArmor module. Compiling and running this module would require a complete upgrade of the whole package in addition to manually patching many areas of the kernel. This is entirely too much work for something that is largely useless in a Linux MCE installation. &lt;br /&gt;
&lt;br /&gt;
=====ALSA=====&lt;br /&gt;
For the ALSA drivers I opted to upgrade the whole package. The compilation and installation is so straight forward that there&#039;s no reason to play around with mixmatched versions. Just rebuild both the kernel drivers and the userspace utilities. Here are the steps for that (Note: You should select your card specifically for the alsa-driver package, using the --with-cards option):&lt;br /&gt;
 mkdir alsa&lt;br /&gt;
 cd alsa&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.19.tar.bz2&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/firmware/alsa-firmware-1.0.19.tar.bz2&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/lib/alsa-lib-1.0.19.tar.bz2&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/plugins/alsa-plugins-1.0.19.tar.bz2&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/utils/alsa-utils-1.0.19.tar.bz2&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/oss-lib/alsa-oss-1.0.17.tar.bz2&lt;br /&gt;
 for fi in *; do&lt;br /&gt;
 tar -jxvf $fi&lt;br /&gt;
 done&lt;br /&gt;
 cd alsa-driver-1.0.19 &lt;br /&gt;
 ./configure --with-cards=hda-intel&lt;br /&gt;
 make&lt;br /&gt;
 sudo make install&lt;br /&gt;
 cd ..&lt;br /&gt;
 for fi in alsa-lib-1.0.19 alsa-plugins-1.0.19 alsa-utils-1.0.19 alsa-oss-1.0.19 alsa-firmware-1.0.19; do&lt;br /&gt;
 cd $fi&lt;br /&gt;
 ./configure&lt;br /&gt;
 make&lt;br /&gt;
 sudo make install&lt;br /&gt;
 cd ..&lt;br /&gt;
 done&lt;br /&gt;
&lt;br /&gt;
=====Asterisk telephony=====&lt;br /&gt;
For Asterisk, simply download the latest Zaptel sources. Configure, Make, Install. &lt;br /&gt;
 wget http://downloads.digium.com/pub/zaptel/zaptel-1.4.12.1.tar.gz&lt;br /&gt;
 tar -zxvf zaptel-1.4.12.1.tar.gz&lt;br /&gt;
 cd zaptel-1.4.12.1&lt;br /&gt;
 ./configure --prefix=/usr&lt;br /&gt;
 make&lt;br /&gt;
 sudo make install&lt;br /&gt;
&lt;br /&gt;
For kernel &amp;gt;= 2.6.28 a fix is needed&lt;br /&gt;
Save the following as zaptel-kernel.patch :&lt;br /&gt;
&lt;br /&gt;
 --- zaptel-1.4.12.1/kernel/ztdummy.c.ORG        2009-04-11 00:26:02.000000000 +0200&lt;br /&gt;
 +++ zaptel-1.4.12.1/kernel/ztdummy.c    2009-04-11 00:26:53.000000000 +0200&lt;br /&gt;
 @@ -199,7 +199,12 @@&lt;br /&gt;
          * expired.&lt;br /&gt;
          * We should worry if overrun is 2 or more; then we really missed&lt;br /&gt;
          * a tick */&lt;br /&gt;
 -       overrun = hrtimer_forward(&amp;amp;zaptimer, htmr-&amp;gt;expires,&lt;br /&gt;
 +       overrun = hrtimer_forward(&amp;amp;zaptimer,&lt;br /&gt;
 +#if LINUX_VERSION_CODE &amp;gt; KERNEL_VERSION(2,6,27)&lt;br /&gt;
 +                      hrtimer_get_expires(htmr),&lt;br /&gt;
 +#else&lt;br /&gt;
 +                      htmr-&amp;gt;expires,&lt;br /&gt;
 +#endif&lt;br /&gt;
                         ktime_set(0, ZAPTEL_TIME_NS));&lt;br /&gt;
         if(overrun &amp;gt; 1) {&lt;br /&gt;
                 if(printk_ratelimit())&lt;br /&gt;
&lt;br /&gt;
and apply after untaring like this :&lt;br /&gt;
 tar -zxvf zaptel-1.4.12.1.tar.gz&lt;br /&gt;
 patch -p0 &amp;lt;zaptel-kernel.patch&lt;br /&gt;
&lt;br /&gt;
=====LIRC IR control=====&lt;br /&gt;
You will also need to recompile LIRC. Note: Some LIRC drivers are not SMP safe and will not compile on SMP kernels. In this case I suggest you pick only the drivers you need.&lt;br /&gt;
&lt;br /&gt;
For kernel version 2.6.27 the following LIRC setup steps worked. The only issue you will have is with some modules not compiling, as noted above. Just compile the module you need for your remote- for me it was &#039;&#039;mceusb2&#039;&#039;.&lt;br /&gt;
  cd /opt/lirc&lt;br /&gt;
  wget http://prdownloads.sourceforge.net/lirc/lirc-0.8.4a.tar.bz2&lt;br /&gt;
  tar -xjvf lirc-0.8.4a.tar.bz2&lt;br /&gt;
  ./configure --prefix=/usr --with-driver=usbmce2&lt;br /&gt;
  make&lt;br /&gt;
  checkinstall&lt;br /&gt;
&lt;br /&gt;
At this point if you get errors about not being about to overwrite&lt;br /&gt;
/usr/lib/liblirc_client.la you may need to&lt;br /&gt;
  cp /usr/lib/liblirc_client.la /opt/lirc/liblirc_client.la.orig&lt;br /&gt;
  dpkg --force-overwrite -i lirc_0.8.4a-1_i386.deb&lt;br /&gt;
&lt;br /&gt;
Proceed with&lt;br /&gt;
  modprobe lirc_mceusb2&lt;br /&gt;
  lircd&lt;br /&gt;
  mode2&lt;br /&gt;
Press some buttons on your remote, you should see information appear about the IR being received.&lt;br /&gt;
&lt;br /&gt;
For 2.6.26.5 I had to patch some files in the kernel to get LIRC to compile. The patch is located on the LIRC site. Also only the CVS version will compile. I ran into even more drama with LIRC, because many drivers failed to even attempt a build. I was able to manually enter each driver directory and perform a make/make install. After applying the patch to the kernel, it failed to compile as well. At this point I would assume that LIRC is not working with 2.6.26.5. &lt;br /&gt;
 cd /usr/src/linux&lt;br /&gt;
 wget http://lirc.sourceforge.net/software/snapshots/lirc-bttv-linux-2.6.24.patch&lt;br /&gt;
 patch -p1 &amp;lt; lirc-bttv-linux-2.6.24.patch&lt;br /&gt;
 cd ..&lt;br /&gt;
 cvs -z8 -d:pserver:anonymous@lirc.cvs.sourceforge.net:/cvsroot/lirc co lirc&lt;br /&gt;
 cd lirc-0.8.3&lt;br /&gt;
 ./configure --prefix=/usr --with-driver=all&lt;br /&gt;
 make&lt;br /&gt;
 make install &lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
=====Video driver=====&lt;br /&gt;
You will most likely need to reinstall your video driver at this point, if you used a proprietary binary version. Instructions for getting the latest driver and installing it can be found in the [[Display Drivers|display drivers]] wiki.&lt;br /&gt;
&lt;br /&gt;
For nVidia do this:&lt;br /&gt;
 wget http://us.download.nvidia.com/XFree86/Linux-x86/177.80/NVIDIA-Linux-x86-177.80-pkg1.run&lt;br /&gt;
 sh NVIDIA-Linux-x86-177.80-pkg1.run&lt;br /&gt;
&lt;br /&gt;
If you have already had a newer version of the driver installed, then just install the kernel module like this :&lt;br /&gt;
 sh NVIDIA-Linux-x86-XXX.XX-pkg1.run -K&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Now it is a good idea to compare your lsmod output from your old kernel to the output of your new kernel. Just to be certain you didn&#039;t miss anything. I found the order to be different, so I copied the output to an Excel spreadsheet and sorted the two different lists. The only discrepancies I found were related to name changes in the kernel and AppArmor.&lt;br /&gt;
&lt;br /&gt;
=====Tuner and other drivers=====&lt;br /&gt;
Don&#039;t forget to recompile and install other drivers which you may have had to install to get your system working.  These include the V4L DVB drivers.&lt;br /&gt;
&lt;br /&gt;
====Media Directors====&lt;br /&gt;
In a traditional installation the Core and Media Directors all run the Gutsy 2.6.22-14 kernel. You may still use this kernel if you like, or you may opt to use your newly built kernel. &lt;br /&gt;
===Use old kernel===&lt;br /&gt;
If you want the media directors to continue to use this old kernel then you must create a symlink to the old kernel in the boot directory of each MD. You must also update the MD archives with this symlink, so future MDs will be setup correctly.&lt;br /&gt;
&lt;br /&gt;
 mkdir /tmp/moonfs_64 /tmp/moonfs_32&lt;br /&gt;
 tar -jxvf /usr/pluto/install/PlutMD-adm64.tar.bz2 /tmp/moonfs_64/&lt;br /&gt;
 tar -jxvf /usr/pluto/install/PlutMD-i386.tar.bz2 /tmp/moonfs_32/&lt;br /&gt;
 for md in /usr/pluto/diskless/* /tmp/moonfs_64 /tmp/moonfs_32; do&lt;br /&gt;
 md_device=`echo &amp;quot;$md&amp;quot; | sed -e &#039;s/.*[/]\([^/]\)/\1/g&#039;`&lt;br /&gt;
 cd $md/boot&lt;br /&gt;
 ln -s vmlinuz-2.6.22-14-generic vmlinuz-2.6.26.5&lt;br /&gt;
 ln -s initrd.img-2.6.22-14-generic initrd.img-2.6.26.5&lt;br /&gt;
 done&lt;br /&gt;
 tar -C /tmp/moonfs_64 -jcvpf /usr/pluto/install/PlutoMD-adm64.tar.bz2 .&lt;br /&gt;
 tar -C /tmp/moonfs_32 -jcvpf /usr/pluto/install/PlutoMD-i386.tar.bz2 .&lt;br /&gt;
 rm -rf /tmp/moonfs_*&lt;br /&gt;
&lt;br /&gt;
=====Use new kernel=====&lt;br /&gt;
A better route, although more complex one is to use your new kernel on the media directors as well. You can do this by copying your kernel and modules to each MD root filesystem. Additionally, you will need to add the kernel image plus modules to the MD root archive (/usr/pluto/install/PlutoMD-xxxyyy.tar.bz2) where xxxyyy is your architecture. This does present an issue if your core and media directors are not the same architecture. In this case you will need to build a kernel for the other architecture using cross-compile methods or using a machine of the that architecture. &lt;br /&gt;
&lt;br /&gt;
These scripts serve as a guideline, and may need to be customized to your unique configuration. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;A few notes:&#039;&#039;&#039;&lt;br /&gt;
* Your initrd-img file should be about 10MB. If it is around the 40MB mark you compiled your kernel with debugging support. The tftp server will refuse to transfer files this large. As a result, all MDs will fail to boot. If you absolutely must use a debugging kernel then there are options you can pass to tftp to make it ignore this limit.&lt;br /&gt;
* These scripts assume all media directors and cores are 64-bit machines. It is left as an exercise for the reader to distribute the proper kernel image for the target MD&#039;s architecture.&lt;br /&gt;
* You should build your video driver files first, so you can include them in your MD archive.&lt;br /&gt;
&lt;br /&gt;
 for md in /usr/pluto/diskless/*; do&lt;br /&gt;
 md_device=`echo &amp;quot;$md&amp;quot; | sed -e &#039;s/.*[/]\([^/]\)/\1/g&#039;`&lt;br /&gt;
 cp /boot/vmlinuz-2.6.26.5 $md/boot/&lt;br /&gt;
 cp /boot/initrd.img-2.6.26.5 $md/boot/&lt;br /&gt;
 cp -r /lib/modules/2.6.26.5/ $md/lib/modules/&lt;br /&gt;
 /usr/pluto/bin/Diskless_InstallKernel.sh $md_device&lt;br /&gt;
 done&lt;br /&gt;
 /usr/pluto/bin/Diskless_BuildDefaultImage.sh&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Now rebuild the archives, so future Media Directors will get the correct kernel image. &lt;br /&gt;
 cd /tmp&lt;br /&gt;
 mkdir moonfs_x64&lt;br /&gt;
 cd moonfs_x64&lt;br /&gt;
 tar -jxvf /usr/pluto/install/PlutMD-adm64.tar.bz2&lt;br /&gt;
 cp /boot/vmlinuz-2.6.26.5 boot&lt;br /&gt;
 cp /boot/initrd.img-2.6.26.5 boot&lt;br /&gt;
 cp -r /lib/modules/2.6.26.5/ lib/modules/&lt;br /&gt;
 tar -jcvpf /usr/pluto/install/PlutoMD-adm64.tar.bz2 *&lt;br /&gt;
 cd ..&lt;br /&gt;
 rm -rf moonfs_x64&lt;br /&gt;
&lt;br /&gt;
====Video Drivers====&lt;br /&gt;
Video drivers for Media Directors get their own section because they often require updated libraries in addition to updated kernel modules. These libraries will have to be distributed to the media directors and updated in the archive. nVidia&#039;s driver installation script provides many useful options for this. I have not looked into a way to do with the ATI drivers, but I assume it&#039;s similar. &lt;br /&gt;
&lt;br /&gt;
You will need this small script I made. NVIDIA packages the precompiled kernel interface with a proprietary header. Removing the header allows you to link the interface and kernel module manually.&lt;br /&gt;
&lt;br /&gt;
stripheader.sh&lt;br /&gt;
 readsint ()&lt;br /&gt;
 {&lt;br /&gt;
   byte=`head -c$2 $1 | tail -c1`&lt;br /&gt;
   sint=`printf &#039;%u&#039; &amp;quot;&#039;$byte&amp;quot;`&lt;br /&gt;
   let &amp;quot;sint=$sint &amp;amp; 0xFF&amp;quot;&lt;br /&gt;
   eval &amp;quot;$3=\&amp;quot;$sint\&amp;quot;&amp;quot;&lt;br /&gt;
 }&lt;br /&gt;
 readuint32 ()&lt;br /&gt;
 {&lt;br /&gt;
   readsint $1 $(($2+1)) b1&lt;br /&gt;
   readsint $1 $(($2+2)) b2&lt;br /&gt;
   readsint $1 $(($2+3)) b3&lt;br /&gt;
   readsint $1 $(($2+4)) b4 &lt;br /&gt;
 &lt;br /&gt;
   uint=$(( ($b4 &amp;lt;&amp;lt; 24) + ($b3 &amp;lt;&amp;lt; 16) + ($b2 &amp;lt;&amp;lt; 8) + $b1 ))&lt;br /&gt;
   eval &amp;quot;$3=\&amp;quot;$uint\&amp;quot;&amp;quot;&lt;br /&gt;
 } &lt;br /&gt;
 &lt;br /&gt;
 let &amp;quot;header=12&amp;quot;&lt;br /&gt;
 readuint32 $1 $header int&lt;br /&gt;
 let &amp;quot;header=$header+$int+4&amp;quot;&lt;br /&gt;
 readuint32 $1 $header int&lt;br /&gt;
 let &amp;quot;header=$header+$int+4&amp;quot;&lt;br /&gt;
 readuint32 $1 $header int&lt;br /&gt;
 let &amp;quot;header=$header+$int+4&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
 precomp=$(stat -c%s &amp;quot;$1&amp;quot;)&lt;br /&gt;
 let &amp;quot;precomp-=$header&amp;quot;&lt;br /&gt;
 tail -c$precomp $1 &amp;gt; $2&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
These commands will update each Media Director. You should also copy these files into the MD archives. This is left as an exercise for the reader.&lt;br /&gt;
&lt;br /&gt;
 wget http://us.download.nvidia.com/XFree86/Linux-x86_64/173.14.12/NVIDIA-Linux-x86_64-173.14.12-pkg2.run&lt;br /&gt;
 sh NVIDIA-Linux-x86_64-173.14.12-pkg2.run --keep --add-this-kernel&lt;br /&gt;
 ./stripheader.sh NVIDIA-Linux-x86_64-173.14.12-pkg2/usr/src/nv/precompiled/precompiled-nv-linux.o* NVIDIA-Linux-x86_64-173.14.12-pkg2/usr/src/nv/nv-linux.o&lt;br /&gt;
 ld -d -r -o nvidia.ko NVIDIA-Linux-x86_64-173.14.12-pkg2/usr/src/nv/nv-linux.o NVIDIA-Linux-x86_64-173.14.12-pkg2/usr/src/nv/nv-kernel.o&lt;br /&gt;
 for md in /usr/pluto/diskless/*; do&lt;br /&gt;
 cp -r NVIDIA-Linux-x86_64-173.14.12-pkg2/usr/* $md/usr/&lt;br /&gt;
 cp nvidia.ko $md/lib/modules/2.6.26.5/kernel/drivers/video/&lt;br /&gt;
 done&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Upgrading_the_Kernel&amp;diff=18384</id>
		<title>Upgrading the Kernel</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Upgrading_the_Kernel&amp;diff=18384"/>
		<updated>2009-04-10T22:20:45Z</updated>

		<summary type="html">&lt;p&gt;Viking: /* Asterisk telephony */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:LinuxMCEMaintenance]]&lt;br /&gt;
[[category: tutorials]]&lt;br /&gt;
[[category: programmer&#039;s Guide]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
The ability to change kernel versions at will can be extremely useful for fighting driver bugs and regressions. This article provides procedures for upgrading the kernel.&lt;br /&gt;
&lt;br /&gt;
==LinuxMCE 0810==&lt;br /&gt;
Upgrading kernels is significantly easier in 0810, now that LinxMCE uses the standard Ubuntu kernel.  If you&#039;re interested in using a non-standard kernel, you can adapt the 0710 instructions to your needs.&lt;br /&gt;
&lt;br /&gt;
===Apt Repositories===&lt;br /&gt;
If the kernel version you&#039;re looking for is not available in the standard repositories, you might have to enable the proposed repositories by adding a line that looks something like:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
deb http://ubuntu.media.mit.edu/ubuntu/ intrepid-proposed restricted main universe multiverse&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
to &#039;&#039;/etc/apt/sources.list&#039;&#039;.  Of course, you&#039;ll want to use the package mirror that is closest to you, probably not MIT.  After adding this line, run &#039;&#039;apt-get update&#039;&#039; to refresh the package lists.&lt;br /&gt;
&lt;br /&gt;
===Installing===&lt;br /&gt;
On the core, simply install the new kernel like any other package.  Don&#039;t forget the restricted modules and headers if you need them.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
linuxmce@dcerouter:~$ sudo apt-get install linux-image-2.6.27-13-generic linux-restricted-modules-2.6.27-11-generic linux-headers-2.6.27-11-generic&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
If you always want the most up-to-date kernel, consider installing the package &#039;&#039;[http://packages.ubuntu.com/intrepid/linux linux]&#039;&#039;.  (This is outside of the scope of this article.)&lt;br /&gt;
&lt;br /&gt;
On MDs, there is one extra step. You will need to update some links in &#039;&#039;/boot/&#039;&#039;.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
root@moon44:~# cd /boot/&lt;br /&gt;
root@moon44:/boot# mv initrd.img initrd.img.bk&lt;br /&gt;
root@moon44:/boot# mv vmlinuz vmlinuz.bk&lt;br /&gt;
root@moon44:/boot# ln initrd.img-2.6.27-13-generic initrd.img&lt;br /&gt;
root@moon44:/boot# ln vmlinuz-2.6.27-13-generic vmlinuz&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==LinuxMCE 0710==&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;WARNING:&#039;&#039;&#039;&#039;&#039; This procedure will break certain things and may even make your system unusable, therefore use at your own risk.  Of course, if your system is not working or is unstable anyway, then trying this could improve things!  &lt;br /&gt;
 &lt;br /&gt;
The kernel version that ships with LinuxMCE 0710 is 2.6.22-14. At the time of writing the most recent stable kernel version is 2.6.28.8. The .22 kernel is almost a full year old and as such does not support a lot of the newer hardware.&lt;br /&gt;
&lt;br /&gt;
Note- kernel version 2.6.27 has changes in it (a redefined set of arguments for smp_call_function) which breaks earlier versions of the Nvidia driver.  Nvidia drivers 178.80 and above should work.&lt;br /&gt;
&lt;br /&gt;
====Caveats====&lt;br /&gt;
Some modules that are part of the vanilla Linux MCE installation are not part of the standard Linux kernel. These modules have been added as part of the Ubuntu distribution or by LMCE. It is not always straight forward, or even possible to compile these modules against different kernel sources. I suggest you read this entire Wiki first, to determine if you will be affected by the missing modules.&lt;br /&gt;
&lt;br /&gt;
====Alternatives====&lt;br /&gt;
Usually kernels are upgraded for better driver support. In these cases it is often easier to compile new versions of modules against the 2.6.22-14 kernel than it is to upgrade the whole kernel (for reasons mentioned in the [[Upgrading the Kernel#Caveats|caveats]] section. Unfortunately, a lot of modules depend on other modules or patches in the kernel. So this option is not always possible.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 cd ~&lt;br /&gt;
 wget http://www.somesite.com/some_kernel_driver.c&lt;br /&gt;
 echo obj-m = some_kernel_driver.o &amp;gt; Makefile&lt;br /&gt;
 cd /lib/modules/2.6.22-14-generic/build&lt;br /&gt;
 make M=~ modules&lt;br /&gt;
 ls -l ~/some_kernel_driver.ko&lt;br /&gt;
&lt;br /&gt;
You may then copy the module to the appropriate directory in the modules tree.&lt;br /&gt;
&lt;br /&gt;
===Upgrade process===&lt;br /&gt;
&lt;br /&gt;
This wiki will provide step-by-step instructions on how to upgrade your kernel. These examples will assume you are upgrading to 2.6.26 from 2.6.22. You may however apply these steps to any 2.6 kernel.&lt;br /&gt;
&lt;br /&gt;
An alternative approach is described here [http://www.debian.org/releases/stable/i386/ch08s06.html.en Rebuilding the kernel the debian way].  Anyone using this potentially easier method could update this document.&lt;br /&gt;
&lt;br /&gt;
====Potential problems====&lt;br /&gt;
All the normal issues of upgrading your kernel apply. Always keep your old, working kernel on hand. &lt;br /&gt;
&lt;br /&gt;
====Steps====&lt;br /&gt;
&lt;br /&gt;
=====Recompiling the kernel=====&lt;br /&gt;
The first step is to grab the kernel source and extract it to the /usr/src folder.&lt;br /&gt;
&lt;br /&gt;
 cd /usr/src&lt;br /&gt;
 wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.28.7.tar.bz2&lt;br /&gt;
 tar -jxvf linux-2.6.28.7.tar.bz&lt;br /&gt;
 rm linux&lt;br /&gt;
 ln -s linux-2.6.28.5 linux&lt;br /&gt;
&lt;br /&gt;
Now lets copy the .config file from our generic 2.6.22 kernel.&lt;br /&gt;
 cd linux&lt;br /&gt;
 cp /boot/config-2.6.22-14-generic .config&lt;br /&gt;
&lt;br /&gt;
On our first load of menuconfig there will be many warnings displayed about non-existant config options. This is simply due to the removal or renaming of old options. Most of these warnings are insignificant, and enabled by default in the vanilla kernel. I would quickly go over the list of warnings and verify that any drivers you need haven&#039;t been renamed. One option that has been renamed is DVB_CORE_ATTACH. It is now DVB_MEDIA_ATTACH, and you may need it if you use the DVB stack. Also some netfilter matches have been renamed. Simply reselect these from the config menus. You may also need to install the ncurses library and development files if you haven&#039;t already.&lt;br /&gt;
&lt;br /&gt;
 sudo apt-get install libncurses5 libncurses5-dev qt3-dev-tools libqt3-mt-dev&lt;br /&gt;
&lt;br /&gt;
Then you can either choose to use the character based interface to set your kernel options&lt;br /&gt;
 make menuconfig 2&amp;gt; module_errors&lt;br /&gt;
&lt;br /&gt;
Or you can use the GUI interface&lt;br /&gt;
 DISPLAY=:0.0 make xconfig&lt;br /&gt;
&lt;br /&gt;
It&#039;s also a good idea to go over the kernel and make any optimizations for your particular system. The performance gain from these options is fairly minor, but definitely worth selecting. &lt;br /&gt;
&lt;br /&gt;
I opted to change these things:&lt;br /&gt;
* Selected exact processor family to enable processor optimization extensions&lt;br /&gt;
* Selected preemptive kernel (low latency)&lt;br /&gt;
* Build SATA driver into kernel&lt;br /&gt;
* Build MD,RAID1,RAID5 modules into kernel&lt;br /&gt;
* Build NIC module into kernel&lt;br /&gt;
* Disabled kernel debugging (&#039;&#039;&#039;Note: This is very important if you plan to use this kernel on Media Directors.&#039;&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
At this point you can start the kernel build process. You may use the standard kernel method or the Debian build method. For simplicity this Wiki will use the standard method.&lt;br /&gt;
 make&lt;br /&gt;
 sudo make modules_install&lt;br /&gt;
&lt;br /&gt;
Copy your kernel image to your /boot folder. Create a new initramfs image. Update your menu.lst file.&lt;br /&gt;
&lt;br /&gt;
 cp arch/yyxx/boot/bzImage /boot/vmlinuz-2.6.28.7&lt;br /&gt;
 mkinitramfs -o /boot/initrd.img-2.6.26.5 2.6.28.7&lt;br /&gt;
 nano /boot/grub/menu.lst&lt;br /&gt;
&lt;br /&gt;
Save a list of all currently used modules for future reference. You will use this later to make sure you have all the required modules.&lt;br /&gt;
&lt;br /&gt;
   lsmod &amp;gt; ~/module_list-2.6.22.14&lt;br /&gt;
&lt;br /&gt;
Go ahead and reboot. Your new kernel should now load. If your boot fails, simply edit the parameters from the grub menu and specify your old kernel and initramfs image. Please note: udev attempts to assign persistent names to most devices. If the way the kernel identifies your device changes from your old kernel version to the new one, udev may assume it&#039;s a new device and assign it an unexpected name. For example, the nForce ethernet drivers corrected a bug in the way the MAC address was read from the device. On my first boot what was usually my eth0 device was now my eth1 device. To fix this simply flush the offending rule from the /etc/udev/rules.d folder.&lt;br /&gt;
&lt;br /&gt;
   reboot&lt;br /&gt;
&lt;br /&gt;
=====Additional items which need to be rebuilt=====&lt;br /&gt;
You should now build any custom modules you need. Linux MCE (and Ubuntu) come with some non-standard drivers. The key modules to worry about are AppArmor, Asterisk (ztdummy &amp;amp; zaptel), ALSA, nVidia video, ATI video. You are better off downloading the latest nVidia and ATI drivers and installing them using the instructions found in the [[Display Drivers|display drivers]] wiki. The Gutsy kernel also contains other important video drivers, like ivtv. However most of these drivers are now in the mainstream kernel and more up-to-date than the Gutsy versions.&lt;br /&gt;
&lt;br /&gt;
=====Mythtv=====&lt;br /&gt;
You do not have to rebuild Mythtv, but if you chose to use the new High Precision Event Timer (HPET) instead of the older kernel Real Time Clock (RTC), then Mythtv will not start up because /proc/sys/dev/rtc/max-user-freq does not exist.  This is because the LinuxMCE 7.10 /etc/init.d/mythtv-backend script does not check if it exists before trying to write to it.  You will have to change your /etc/init.d/mythtv-backend script as follows:&lt;br /&gt;
&lt;br /&gt;
 case &amp;quot;$1&amp;quot; in&lt;br /&gt;
    start)&lt;br /&gt;
        if test -e $RUNDIR/$NAME.pid ; then&lt;br /&gt;
            echo &amp;quot;mythbackend already running, use restart instead.&amp;quot;&lt;br /&gt;
        else&lt;br /&gt;
            # set the timeslice to 1/1024 of a sec for smoother mythtv and xine and mplayer playback &lt;br /&gt;
            if [ -w /proc/sys/dev/rtc/max-user-freq ] # check if RTC (older kernels) exists and I can write to it&lt;br /&gt;
                # failure is not an option!&lt;br /&gt;
            then echo 1024 &amp;gt; /proc/sys/dev/rtc/max-user-freq&lt;br /&gt;
        elif [ -w /proc/sys/dev/hpet/max-user-freq ] # or newer kernels with the High Precision Timer (HPET)&lt;br /&gt;
            # may or may not emulate the older RTC fully&lt;br /&gt;
        then echo 1024 &amp;gt; /proc/sys/dev/hpet/max-user-freq&lt;br /&gt;
    fi # start starting the startup of mythtv &lt;br /&gt;
 echo -n &amp;quot;Starting $DESC: $NAME &amp;quot; start-stop-daemon --start --pidfile $RUNDIR/$NAME.pid \ &lt;br /&gt;
&lt;br /&gt;
=====Apparmor=====&lt;br /&gt;
I have decided to forgo the AppArmor module. Compiling and running this module would require a complete upgrade of the whole package in addition to manually patching many areas of the kernel. This is entirely too much work for something that is largely useless in a Linux MCE installation. &lt;br /&gt;
&lt;br /&gt;
=====ALSA=====&lt;br /&gt;
For the ALSA drivers I opted to upgrade the whole package. The compilation and installation is so straight forward that there&#039;s no reason to play around with mixmatched versions. Just rebuild both the kernel drivers and the userspace utilities. Here are the steps for that (Note: You should select your card specifically for the alsa-driver package, using the --with-cards option):&lt;br /&gt;
 mkdir alsa&lt;br /&gt;
 cd alsa&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.19.tar.bz2&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/firmware/alsa-firmware-1.0.19.tar.bz2&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/lib/alsa-lib-1.0.19.tar.bz2&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/plugins/alsa-plugins-1.0.19.tar.bz2&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/utils/alsa-utils-1.0.19.tar.bz2&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/oss-lib/alsa-oss-1.0.17.tar.bz2&lt;br /&gt;
 for fi in *; do&lt;br /&gt;
 tar -jxvf $fi&lt;br /&gt;
 done&lt;br /&gt;
 cd alsa-driver-1.0.19 &lt;br /&gt;
 ./configure --with-cards=hda-intel&lt;br /&gt;
 make&lt;br /&gt;
 sudo make install&lt;br /&gt;
 cd ..&lt;br /&gt;
 for fi in alsa-lib-1.0.19 alsa-plugins-1.0.19 alsa-utils-1.0.19 alsa-oss-1.0.19 alsa-firmware-1.0.19; do&lt;br /&gt;
 cd $fi&lt;br /&gt;
 ./configure&lt;br /&gt;
 make&lt;br /&gt;
 sudo make install&lt;br /&gt;
 cd ..&lt;br /&gt;
 done&lt;br /&gt;
&lt;br /&gt;
=====Asterisk telephony=====&lt;br /&gt;
For Asterisk, simply download the latest Zaptel sources. Configure, Make, Install. &lt;br /&gt;
 wget http://downloads.digium.com/pub/zaptel/zaptel-1.4.12.1.tar.gz&lt;br /&gt;
 tar -zxvf zaptel-1.4.12.1.tar.gz&lt;br /&gt;
 cd zaptel-1.4.12.1&lt;br /&gt;
 ./configure --prefix=/usr&lt;br /&gt;
 make&lt;br /&gt;
 sudo make install&lt;br /&gt;
&lt;br /&gt;
For kernel &amp;gt;= 2.6.28 a fix is needed&lt;br /&gt;
Save the following as zaptel-kernel.patch :&lt;br /&gt;
&lt;br /&gt;
 --- ztdummy.c.ORG       2009-04-11 00:16:56.000000000 +0200&lt;br /&gt;
 +++ ztdummy.c   2009-04-11 00:16:59.000000000 +0200&lt;br /&gt;
 @@ -199,7 +199,12 @@&lt;br /&gt;
          * expired.&lt;br /&gt;
          * We should worry if overrun is 2 or more; then we really missed&lt;br /&gt;
          * a tick */&lt;br /&gt;
 -       overrun = hrtimer_forward(&amp;amp;zaptimer, htmr-&amp;gt;expires,&lt;br /&gt;
 +      overrun = hrtimer_forward(&amp;amp;zaptimer,&lt;br /&gt;
 +#if LINUX_VERSION_CODE &amp;gt; KERNEL_VERSION(2,6,27)&lt;br /&gt;
 +                      hrtimer_get_expires(htmr),&lt;br /&gt;
 +#else&lt;br /&gt;
 +                      htmr-&amp;gt;expires,&lt;br /&gt;
 +#endif&lt;br /&gt;
                         ktime_set(0, ZAPTEL_TIME_NS));&lt;br /&gt;
         if(overrun &amp;gt; 1) {&lt;br /&gt;
                 if(printk_ratelimit())&lt;br /&gt;
&lt;br /&gt;
and apply after untaring like this :&lt;br /&gt;
 tar -zxvf zaptel-1.4.12.1.tar.gz&lt;br /&gt;
 patch -p0 &amp;lt;zaptel-kernel.patch&lt;br /&gt;
&lt;br /&gt;
=====LIRC IR control=====&lt;br /&gt;
You will also need to recompile LIRC. Note: Some LIRC drivers are not SMP safe and will not compile on SMP kernels. In this case I suggest you pick only the drivers you need.&lt;br /&gt;
&lt;br /&gt;
For kernel version 2.6.27 the following LIRC setup steps worked. The only issue you will have is with some modules not compiling, as noted above. Just compile the module you need for your remote- for me it was &#039;&#039;mceusb2&#039;&#039;.&lt;br /&gt;
  cd /opt/lirc&lt;br /&gt;
  wget http://prdownloads.sourceforge.net/lirc/lirc-0.8.4a.tar.bz2&lt;br /&gt;
  tar -xjvf lirc-0.8.4a.tar.bz2&lt;br /&gt;
  ./configure --prefix=/usr --with-driver=usbmce2&lt;br /&gt;
  make&lt;br /&gt;
  checkinstall&lt;br /&gt;
&lt;br /&gt;
At this point if you get errors about not being about to overwrite&lt;br /&gt;
/usr/lib/liblirc_client.la you may need to&lt;br /&gt;
  cp /usr/lib/liblirc_client.la /opt/lirc/liblirc_client.la.orig&lt;br /&gt;
  dpkg --force-overwrite -i lirc_0.8.4a-1_i386.deb&lt;br /&gt;
&lt;br /&gt;
Proceed with&lt;br /&gt;
  modprobe lirc_mceusb2&lt;br /&gt;
  lircd&lt;br /&gt;
  mode2&lt;br /&gt;
Press some buttons on your remote, you should see information appear about the IR being received.&lt;br /&gt;
&lt;br /&gt;
For 2.6.26.5 I had to patch some files in the kernel to get LIRC to compile. The patch is located on the LIRC site. Also only the CVS version will compile. I ran into even more drama with LIRC, because many drivers failed to even attempt a build. I was able to manually enter each driver directory and perform a make/make install. After applying the patch to the kernel, it failed to compile as well. At this point I would assume that LIRC is not working with 2.6.26.5. &lt;br /&gt;
 cd /usr/src/linux&lt;br /&gt;
 wget http://lirc.sourceforge.net/software/snapshots/lirc-bttv-linux-2.6.24.patch&lt;br /&gt;
 patch -p1 &amp;lt; lirc-bttv-linux-2.6.24.patch&lt;br /&gt;
 cd ..&lt;br /&gt;
 cvs -z8 -d:pserver:anonymous@lirc.cvs.sourceforge.net:/cvsroot/lirc co lirc&lt;br /&gt;
 cd lirc-0.8.3&lt;br /&gt;
 ./configure --prefix=/usr --with-driver=all&lt;br /&gt;
 make&lt;br /&gt;
 make install &lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
=====Video driver=====&lt;br /&gt;
You will most likely need to reinstall your video driver at this point, if you used a proprietary binary version. Instructions for getting the latest driver and installing it can be found in the [[Display Drivers|display drivers]] wiki.&lt;br /&gt;
&lt;br /&gt;
For nVidia do this:&lt;br /&gt;
 wget http://us.download.nvidia.com/XFree86/Linux-x86/177.80/NVIDIA-Linux-x86-177.80-pkg1.run&lt;br /&gt;
 sh NVIDIA-Linux-x86-177.80-pkg1.run&lt;br /&gt;
&lt;br /&gt;
If you have already had a newer version of the driver installed, then just install the kernel module like this :&lt;br /&gt;
 sh NVIDIA-Linux-x86-XXX.XX-pkg1.run -K&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Now it is a good idea to compare your lsmod output from your old kernel to the output of your new kernel. Just to be certain you didn&#039;t miss anything. I found the order to be different, so I copied the output to an Excel spreadsheet and sorted the two different lists. The only discrepancies I found were related to name changes in the kernel and AppArmor.&lt;br /&gt;
&lt;br /&gt;
=====Tuner and other drivers=====&lt;br /&gt;
Don&#039;t forget to recompile and install other drivers which you may have had to install to get your system working.  These include the V4L DVB drivers.&lt;br /&gt;
&lt;br /&gt;
====Media Directors====&lt;br /&gt;
In a traditional installation the Core and Media Directors all run the Gutsy 2.6.22-14 kernel. You may still use this kernel if you like, or you may opt to use your newly built kernel. &lt;br /&gt;
===Use old kernel===&lt;br /&gt;
If you want the media directors to continue to use this old kernel then you must create a symlink to the old kernel in the boot directory of each MD. You must also update the MD archives with this symlink, so future MDs will be setup correctly.&lt;br /&gt;
&lt;br /&gt;
 mkdir /tmp/moonfs_64 /tmp/moonfs_32&lt;br /&gt;
 tar -jxvf /usr/pluto/install/PlutMD-adm64.tar.bz2 /tmp/moonfs_64/&lt;br /&gt;
 tar -jxvf /usr/pluto/install/PlutMD-i386.tar.bz2 /tmp/moonfs_32/&lt;br /&gt;
 for md in /usr/pluto/diskless/* /tmp/moonfs_64 /tmp/moonfs_32; do&lt;br /&gt;
 md_device=`echo &amp;quot;$md&amp;quot; | sed -e &#039;s/.*[/]\([^/]\)/\1/g&#039;`&lt;br /&gt;
 cd $md/boot&lt;br /&gt;
 ln -s vmlinuz-2.6.22-14-generic vmlinuz-2.6.26.5&lt;br /&gt;
 ln -s initrd.img-2.6.22-14-generic initrd.img-2.6.26.5&lt;br /&gt;
 done&lt;br /&gt;
 tar -C /tmp/moonfs_64 -jcvpf /usr/pluto/install/PlutoMD-adm64.tar.bz2 .&lt;br /&gt;
 tar -C /tmp/moonfs_32 -jcvpf /usr/pluto/install/PlutoMD-i386.tar.bz2 .&lt;br /&gt;
 rm -rf /tmp/moonfs_*&lt;br /&gt;
&lt;br /&gt;
=====Use new kernel=====&lt;br /&gt;
A better route, although more complex one is to use your new kernel on the media directors as well. You can do this by copying your kernel and modules to each MD root filesystem. Additionally, you will need to add the kernel image plus modules to the MD root archive (/usr/pluto/install/PlutoMD-xxxyyy.tar.bz2) where xxxyyy is your architecture. This does present an issue if your core and media directors are not the same architecture. In this case you will need to build a kernel for the other architecture using cross-compile methods or using a machine of the that architecture. &lt;br /&gt;
&lt;br /&gt;
These scripts serve as a guideline, and may need to be customized to your unique configuration. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;A few notes:&#039;&#039;&#039;&lt;br /&gt;
* Your initrd-img file should be about 10MB. If it is around the 40MB mark you compiled your kernel with debugging support. The tftp server will refuse to transfer files this large. As a result, all MDs will fail to boot. If you absolutely must use a debugging kernel then there are options you can pass to tftp to make it ignore this limit.&lt;br /&gt;
* These scripts assume all media directors and cores are 64-bit machines. It is left as an exercise for the reader to distribute the proper kernel image for the target MD&#039;s architecture.&lt;br /&gt;
* You should build your video driver files first, so you can include them in your MD archive.&lt;br /&gt;
&lt;br /&gt;
 for md in /usr/pluto/diskless/*; do&lt;br /&gt;
 md_device=`echo &amp;quot;$md&amp;quot; | sed -e &#039;s/.*[/]\([^/]\)/\1/g&#039;`&lt;br /&gt;
 cp /boot/vmlinuz-2.6.26.5 $md/boot/&lt;br /&gt;
 cp /boot/initrd.img-2.6.26.5 $md/boot/&lt;br /&gt;
 cp -r /lib/modules/2.6.26.5/ $md/lib/modules/&lt;br /&gt;
 /usr/pluto/bin/Diskless_InstallKernel.sh $md_device&lt;br /&gt;
 done&lt;br /&gt;
 /usr/pluto/bin/Diskless_BuildDefaultImage.sh&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Now rebuild the archives, so future Media Directors will get the correct kernel image. &lt;br /&gt;
 cd /tmp&lt;br /&gt;
 mkdir moonfs_x64&lt;br /&gt;
 cd moonfs_x64&lt;br /&gt;
 tar -jxvf /usr/pluto/install/PlutMD-adm64.tar.bz2&lt;br /&gt;
 cp /boot/vmlinuz-2.6.26.5 boot&lt;br /&gt;
 cp /boot/initrd.img-2.6.26.5 boot&lt;br /&gt;
 cp -r /lib/modules/2.6.26.5/ lib/modules/&lt;br /&gt;
 tar -jcvpf /usr/pluto/install/PlutoMD-adm64.tar.bz2 *&lt;br /&gt;
 cd ..&lt;br /&gt;
 rm -rf moonfs_x64&lt;br /&gt;
&lt;br /&gt;
====Video Drivers====&lt;br /&gt;
Video drivers for Media Directors get their own section because they often require updated libraries in addition to updated kernel modules. These libraries will have to be distributed to the media directors and updated in the archive. nVidia&#039;s driver installation script provides many useful options for this. I have not looked into a way to do with the ATI drivers, but I assume it&#039;s similar. &lt;br /&gt;
&lt;br /&gt;
You will need this small script I made. NVIDIA packages the precompiled kernel interface with a proprietary header. Removing the header allows you to link the interface and kernel module manually.&lt;br /&gt;
&lt;br /&gt;
stripheader.sh&lt;br /&gt;
 readsint ()&lt;br /&gt;
 {&lt;br /&gt;
   byte=`head -c$2 $1 | tail -c1`&lt;br /&gt;
   sint=`printf &#039;%u&#039; &amp;quot;&#039;$byte&amp;quot;`&lt;br /&gt;
   let &amp;quot;sint=$sint &amp;amp; 0xFF&amp;quot;&lt;br /&gt;
   eval &amp;quot;$3=\&amp;quot;$sint\&amp;quot;&amp;quot;&lt;br /&gt;
 }&lt;br /&gt;
 readuint32 ()&lt;br /&gt;
 {&lt;br /&gt;
   readsint $1 $(($2+1)) b1&lt;br /&gt;
   readsint $1 $(($2+2)) b2&lt;br /&gt;
   readsint $1 $(($2+3)) b3&lt;br /&gt;
   readsint $1 $(($2+4)) b4 &lt;br /&gt;
 &lt;br /&gt;
   uint=$(( ($b4 &amp;lt;&amp;lt; 24) + ($b3 &amp;lt;&amp;lt; 16) + ($b2 &amp;lt;&amp;lt; 8) + $b1 ))&lt;br /&gt;
   eval &amp;quot;$3=\&amp;quot;$uint\&amp;quot;&amp;quot;&lt;br /&gt;
 } &lt;br /&gt;
 &lt;br /&gt;
 let &amp;quot;header=12&amp;quot;&lt;br /&gt;
 readuint32 $1 $header int&lt;br /&gt;
 let &amp;quot;header=$header+$int+4&amp;quot;&lt;br /&gt;
 readuint32 $1 $header int&lt;br /&gt;
 let &amp;quot;header=$header+$int+4&amp;quot;&lt;br /&gt;
 readuint32 $1 $header int&lt;br /&gt;
 let &amp;quot;header=$header+$int+4&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
 precomp=$(stat -c%s &amp;quot;$1&amp;quot;)&lt;br /&gt;
 let &amp;quot;precomp-=$header&amp;quot;&lt;br /&gt;
 tail -c$precomp $1 &amp;gt; $2&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
These commands will update each Media Director. You should also copy these files into the MD archives. This is left as an exercise for the reader.&lt;br /&gt;
&lt;br /&gt;
 wget http://us.download.nvidia.com/XFree86/Linux-x86_64/173.14.12/NVIDIA-Linux-x86_64-173.14.12-pkg2.run&lt;br /&gt;
 sh NVIDIA-Linux-x86_64-173.14.12-pkg2.run --keep --add-this-kernel&lt;br /&gt;
 ./stripheader.sh NVIDIA-Linux-x86_64-173.14.12-pkg2/usr/src/nv/precompiled/precompiled-nv-linux.o* NVIDIA-Linux-x86_64-173.14.12-pkg2/usr/src/nv/nv-linux.o&lt;br /&gt;
 ld -d -r -o nvidia.ko NVIDIA-Linux-x86_64-173.14.12-pkg2/usr/src/nv/nv-linux.o NVIDIA-Linux-x86_64-173.14.12-pkg2/usr/src/nv/nv-kernel.o&lt;br /&gt;
 for md in /usr/pluto/diskless/*; do&lt;br /&gt;
 cp -r NVIDIA-Linux-x86_64-173.14.12-pkg2/usr/* $md/usr/&lt;br /&gt;
 cp nvidia.ko $md/lib/modules/2.6.26.5/kernel/drivers/video/&lt;br /&gt;
 done&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Upgrading_the_Kernel&amp;diff=18366</id>
		<title>Upgrading the Kernel</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Upgrading_the_Kernel&amp;diff=18366"/>
		<updated>2009-04-09T21:35:50Z</updated>

		<summary type="html">&lt;p&gt;Viking: /* Video driver */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:LinuxMCEMaintenance]]&lt;br /&gt;
[[category: tutorials]]&lt;br /&gt;
[[category: programmer&#039;s Guide]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
The ability to change kernel versions at will can be extremely useful for fighting driver bugs and regressions. This article provides procedures for upgrading the kernel.&lt;br /&gt;
&lt;br /&gt;
==LinuxMCE 0810==&lt;br /&gt;
Upgrading kernels is significantly easier in 0810, now that LinxMCE uses the standard Ubuntu kernel.  If you&#039;re interested in using a non-standard kernel, you can adapt the 0710 instructions to your needs.&lt;br /&gt;
&lt;br /&gt;
===Apt Repositories===&lt;br /&gt;
If the kernel version you&#039;re looking for is not available in the standard repositories, you might have to enable the proposed repositories by adding a line that looks something like:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
deb http://ubuntu.media.mit.edu/ubuntu/ intrepid-proposed restricted main universe multiverse&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
to &#039;&#039;/etc/apt/sources.list&#039;&#039;.  Of course, you&#039;ll want to use the package mirror that is closest to you, probably not MIT.  After adding this line, run &#039;&#039;apt-get update&#039;&#039; to refresh the package lists.&lt;br /&gt;
&lt;br /&gt;
===Installing===&lt;br /&gt;
On the core, simply install the new kernel like any other package.  Don&#039;t forget the restricted modules and headers if you need them.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
linuxmce@dcerouter:~$ sudo apt-get install linux-image-2.6.27-13-generic linux-restricted-modules-2.6.27-11-generic linux-headers-2.6.27-11-generic&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
If you always want the most up-to-date kernel, consider installing the package &#039;&#039;[http://packages.ubuntu.com/intrepid/linux linux]&#039;&#039;.  (This is outside of the scope of this article.)&lt;br /&gt;
&lt;br /&gt;
On MDs, there is one extra step. You will need to update some links in &#039;&#039;/boot/&#039;&#039;.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
root@moon44:~# cd /boot/&lt;br /&gt;
root@moon44:/boot# mv initrd.img initrd.img.bk&lt;br /&gt;
root@moon44:/boot# mv vmlinuz vmlinuz.bk&lt;br /&gt;
root@moon44:/boot# ln initrd.img-2.6.27-13-generic initrd.img&lt;br /&gt;
root@moon44:/boot# ln vmlinuz-2.6.27-13-generic vmlinuz&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==LinuxMCE 0710==&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;WARNING:&#039;&#039;&#039;&#039;&#039; This procedure will break certain things and may even make your system unusable, therefore use at your own risk.  Of course, if your system is not working or is unstable anyway, then trying this could improve things!  &lt;br /&gt;
 &lt;br /&gt;
The kernel version that ships with LinuxMCE 0710 is 2.6.22-14. At the time of writing the most recent stable kernel version is 2.6.28.8. The .22 kernel is almost a full year old and as such does not support a lot of the newer hardware.&lt;br /&gt;
&lt;br /&gt;
Note- kernel version 2.6.27 has changes in it (a redefined set of arguments for smp_call_function) which breaks earlier versions of the Nvidia driver.  Nvidia drivers 178.80 and above should work.&lt;br /&gt;
&lt;br /&gt;
====Caveats====&lt;br /&gt;
Some modules that are part of the vanilla Linux MCE installation are not part of the standard Linux kernel. These modules have been added as part of the Ubuntu distribution or by LMCE. It is not always straight forward, or even possible to compile these modules against different kernel sources. I suggest you read this entire Wiki first, to determine if you will be affected by the missing modules.&lt;br /&gt;
&lt;br /&gt;
====Alternatives====&lt;br /&gt;
Usually kernels are upgraded for better driver support. In these cases it is often easier to compile new versions of modules against the 2.6.22-14 kernel than it is to upgrade the whole kernel (for reasons mentioned in the [[Upgrading the Kernel#Caveats|caveats]] section. Unfortunately, a lot of modules depend on other modules or patches in the kernel. So this option is not always possible.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 cd ~&lt;br /&gt;
 wget http://www.somesite.com/some_kernel_driver.c&lt;br /&gt;
 echo obj-m = some_kernel_driver.o &amp;gt; Makefile&lt;br /&gt;
 cd /lib/modules/2.6.22-14-generic/build&lt;br /&gt;
 make M=~ modules&lt;br /&gt;
 ls -l ~/some_kernel_driver.ko&lt;br /&gt;
&lt;br /&gt;
You may then copy the module to the appropriate directory in the modules tree.&lt;br /&gt;
&lt;br /&gt;
===Upgrade process===&lt;br /&gt;
&lt;br /&gt;
This wiki will provide step-by-step instructions on how to upgrade your kernel. These examples will assume you are upgrading to 2.6.26 from 2.6.22. You may however apply these steps to any 2.6 kernel.&lt;br /&gt;
&lt;br /&gt;
An alternative approach is described here [http://www.debian.org/releases/stable/i386/ch08s06.html.en Rebuilding the kernel the debian way].  Anyone using this potentially easier method could update this document.&lt;br /&gt;
&lt;br /&gt;
====Potential problems====&lt;br /&gt;
All the normal issues of upgrading your kernel apply. Always keep your old, working kernel on hand. &lt;br /&gt;
&lt;br /&gt;
====Steps====&lt;br /&gt;
&lt;br /&gt;
=====Recompiling the kernel=====&lt;br /&gt;
The first step is to grab the kernel source and extract it to the /usr/src folder.&lt;br /&gt;
&lt;br /&gt;
 cd /usr/src&lt;br /&gt;
 wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.28.7.tar.bz2&lt;br /&gt;
 tar -jxvf linux-2.6.28.7.tar.bz&lt;br /&gt;
 rm linux&lt;br /&gt;
 ln -s linux-2.6.28.5 linux&lt;br /&gt;
&lt;br /&gt;
Now lets copy the .config file from our generic 2.6.22 kernel.&lt;br /&gt;
 cd linux&lt;br /&gt;
 cp /boot/config-2.6.22-14-generic .config&lt;br /&gt;
&lt;br /&gt;
On our first load of menuconfig there will be many warnings displayed about non-existant config options. This is simply due to the removal or renaming of old options. Most of these warnings are insignificant, and enabled by default in the vanilla kernel. I would quickly go over the list of warnings and verify that any drivers you need haven&#039;t been renamed. One option that has been renamed is DVB_CORE_ATTACH. It is now DVB_MEDIA_ATTACH, and you may need it if you use the DVB stack. Also some netfilter matches have been renamed. Simply reselect these from the config menus. You may also need to install the ncurses library and development files if you haven&#039;t already.&lt;br /&gt;
&lt;br /&gt;
 sudo apt-get install libncurses5 libncurses5-dev qt3-dev-tools libqt3-mt-dev&lt;br /&gt;
&lt;br /&gt;
Then you can either choose to use the character based interface to set your kernel options&lt;br /&gt;
 make menuconfig 2&amp;gt; module_errors&lt;br /&gt;
&lt;br /&gt;
Or you can use the GUI interface&lt;br /&gt;
 DISPLAY=:0.0 make xconfig&lt;br /&gt;
&lt;br /&gt;
It&#039;s also a good idea to go over the kernel and make any optimizations for your particular system. The performance gain from these options is fairly minor, but definitely worth selecting. &lt;br /&gt;
&lt;br /&gt;
I opted to change these things:&lt;br /&gt;
* Selected exact processor family to enable processor optimization extensions&lt;br /&gt;
* Selected preemptive kernel (low latency)&lt;br /&gt;
* Build SATA driver into kernel&lt;br /&gt;
* Build MD,RAID1,RAID5 modules into kernel&lt;br /&gt;
* Build NIC module into kernel&lt;br /&gt;
* Disabled kernel debugging (&#039;&#039;&#039;Note: This is very important if you plan to use this kernel on Media Directors.&#039;&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
At this point you can start the kernel build process. You may use the standard kernel method or the Debian build method. For simplicity this Wiki will use the standard method.&lt;br /&gt;
 make&lt;br /&gt;
 sudo make modules_install&lt;br /&gt;
&lt;br /&gt;
Copy your kernel image to your /boot folder. Create a new initramfs image. Update your menu.lst file.&lt;br /&gt;
&lt;br /&gt;
 cp arch/yyxx/boot/bzImage /boot/vmlinuz-2.6.28.7&lt;br /&gt;
 mkinitramfs -o /boot/initrd.img-2.6.26.5 2.6.28.7&lt;br /&gt;
 nano /boot/grub/menu.lst&lt;br /&gt;
&lt;br /&gt;
Save a list of all currently used modules for future reference. You will use this later to make sure you have all the required modules.&lt;br /&gt;
&lt;br /&gt;
   lsmod &amp;gt; ~/module_list-2.6.22.14&lt;br /&gt;
&lt;br /&gt;
Go ahead and reboot. Your new kernel should now load. If your boot fails, simply edit the parameters from the grub menu and specify your old kernel and initramfs image. Please note: udev attempts to assign persistent names to most devices. If the way the kernel identifies your device changes from your old kernel version to the new one, udev may assume it&#039;s a new device and assign it an unexpected name. For example, the nForce ethernet drivers corrected a bug in the way the MAC address was read from the device. On my first boot what was usually my eth0 device was now my eth1 device. To fix this simply flush the offending rule from the /etc/udev/rules.d folder.&lt;br /&gt;
&lt;br /&gt;
   reboot&lt;br /&gt;
&lt;br /&gt;
=====Additional items which need to be rebuilt=====&lt;br /&gt;
You should now build any custom modules you need. Linux MCE (and Ubuntu) come with some non-standard drivers. The key modules to worry about are AppArmor, Asterisk (ztdummy &amp;amp; zaptel), ALSA, nVidia video, ATI video. You are better off downloading the latest nVidia and ATI drivers and installing them using the instructions found in the [[Display Drivers|display drivers]] wiki. The Gutsy kernel also contains other important video drivers, like ivtv. However most of these drivers are now in the mainstream kernel and more up-to-date than the Gutsy versions.&lt;br /&gt;
&lt;br /&gt;
=====Mythtv=====&lt;br /&gt;
You do not have to rebuild Mythtv, but if you chose to use the new High Precision Event Timer (HPET) instead of the older kernel Real Time Clock (RTC), then Mythtv will not start up because /proc/sys/dev/rtc/max-user-freq does not exist.  This is because the LinuxMCE 7.10 /etc/init.d/mythtv-backend script does not check if it exists before trying to write to it.  You will have to change your /etc/init.d/mythtv-backend script as follows:&lt;br /&gt;
&lt;br /&gt;
 case &amp;quot;$1&amp;quot; in&lt;br /&gt;
    start)&lt;br /&gt;
        if test -e $RUNDIR/$NAME.pid ; then&lt;br /&gt;
            echo &amp;quot;mythbackend already running, use restart instead.&amp;quot;&lt;br /&gt;
        else&lt;br /&gt;
            # set the timeslice to 1/1024 of a sec for smoother mythtv and xine and mplayer playback &lt;br /&gt;
            if [ -w /proc/sys/dev/rtc/max-user-freq ] # check if RTC (older kernels) exists and I can write to it&lt;br /&gt;
                # failure is not an option!&lt;br /&gt;
            then echo 1024 &amp;gt; /proc/sys/dev/rtc/max-user-freq&lt;br /&gt;
        elif [ -w /proc/sys/dev/hpet/max-user-freq ] # or newer kernels with the High Precision Timer (HPET)&lt;br /&gt;
            # may or may not emulate the older RTC fully&lt;br /&gt;
        then echo 1024 &amp;gt; /proc/sys/dev/hpet/max-user-freq&lt;br /&gt;
    fi # start starting the startup of mythtv &lt;br /&gt;
 echo -n &amp;quot;Starting $DESC: $NAME &amp;quot; start-stop-daemon --start --pidfile $RUNDIR/$NAME.pid \ &lt;br /&gt;
&lt;br /&gt;
=====Apparmor=====&lt;br /&gt;
I have decided to forgo the AppArmor module. Compiling and running this module would require a complete upgrade of the whole package in addition to manually patching many areas of the kernel. This is entirely too much work for something that is largely useless in a Linux MCE installation. &lt;br /&gt;
&lt;br /&gt;
=====ALSA=====&lt;br /&gt;
For the ALSA drivers I opted to upgrade the whole package. The compilation and installation is so straight forward that there&#039;s no reason to play around with mixmatched versions. Just rebuild both the kernel drivers and the userspace utilities. Here are the steps for that (Note: You should select your card specifically for the alsa-driver package, using the --with-cards option):&lt;br /&gt;
 mkdir alsa&lt;br /&gt;
 cd alsa&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.19.tar.bz2&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/firmware/alsa-firmware-1.0.19.tar.bz2&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/lib/alsa-lib-1.0.19.tar.bz2&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/plugins/alsa-plugins-1.0.19.tar.bz2&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/utils/alsa-utils-1.0.19.tar.bz2&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/oss-lib/alsa-oss-1.0.17.tar.bz2&lt;br /&gt;
 for fi in *; do&lt;br /&gt;
 tar -jxvf $fi&lt;br /&gt;
 done&lt;br /&gt;
 cd alsa-driver-1.0.19 &lt;br /&gt;
 ./configure --with-cards=hda-intel&lt;br /&gt;
 make&lt;br /&gt;
 sudo make install&lt;br /&gt;
 cd ..&lt;br /&gt;
 for fi in alsa-lib-1.0.19 alsa-plugins-1.0.19 alsa-utils-1.0.19 alsa-oss-1.0.19 alsa-firmware-1.0.19; do&lt;br /&gt;
 cd $fi&lt;br /&gt;
 ./configure&lt;br /&gt;
 make&lt;br /&gt;
 sudo make install&lt;br /&gt;
 cd ..&lt;br /&gt;
 done&lt;br /&gt;
&lt;br /&gt;
=====Asterisk telephony=====&lt;br /&gt;
For Asterisk, simply download the latest Zaptel sources. Configure, Make, Install. &lt;br /&gt;
 wget http://downloads.digium.com/pub/zaptel/zaptel-1.4.12.1.tar.gz&lt;br /&gt;
 tar -zxvf zaptel-1.4.12.1.tar.gz&lt;br /&gt;
 cd zaptel-1.4.12.1&lt;br /&gt;
 ./configure --prefix=/usr&lt;br /&gt;
 make&lt;br /&gt;
 sudo make install&lt;br /&gt;
&lt;br /&gt;
=====LIRC IR control=====&lt;br /&gt;
You will also need to recompile LIRC. Note: Some LIRC drivers are not SMP safe and will not compile on SMP kernels. In this case I suggest you pick only the drivers you need.&lt;br /&gt;
&lt;br /&gt;
For kernel version 2.6.27 the following LIRC setup steps worked. The only issue you will have is with some modules not compiling, as noted above. Just compile the module you need for your remote- for me it was &#039;&#039;mceusb2&#039;&#039;.&lt;br /&gt;
  cd /opt/lirc&lt;br /&gt;
  wget http://prdownloads.sourceforge.net/lirc/lirc-0.8.4a.tar.bz2&lt;br /&gt;
  tar -xjvf lirc-0.8.4a.tar.bz2&lt;br /&gt;
  ./configure --prefix=/usr --with-driver=usbmce2&lt;br /&gt;
  make&lt;br /&gt;
  checkinstall&lt;br /&gt;
&lt;br /&gt;
At this point if you get errors about not being about to overwrite&lt;br /&gt;
/usr/lib/liblirc_client.la you may need to&lt;br /&gt;
  cp /usr/lib/liblirc_client.la /opt/lirc/liblirc_client.la.orig&lt;br /&gt;
  dpkg --force-overwrite -i lirc_0.8.4a-1_i386.deb&lt;br /&gt;
&lt;br /&gt;
Proceed with&lt;br /&gt;
  modprobe lirc_mceusb2&lt;br /&gt;
  lircd&lt;br /&gt;
  mode2&lt;br /&gt;
Press some buttons on your remote, you should see information appear about the IR being received.&lt;br /&gt;
&lt;br /&gt;
For 2.6.26.5 I had to patch some files in the kernel to get LIRC to compile. The patch is located on the LIRC site. Also only the CVS version will compile. I ran into even more drama with LIRC, because many drivers failed to even attempt a build. I was able to manually enter each driver directory and perform a make/make install. After applying the patch to the kernel, it failed to compile as well. At this point I would assume that LIRC is not working with 2.6.26.5. &lt;br /&gt;
 cd /usr/src/linux&lt;br /&gt;
 wget http://lirc.sourceforge.net/software/snapshots/lirc-bttv-linux-2.6.24.patch&lt;br /&gt;
 patch -p1 &amp;lt; lirc-bttv-linux-2.6.24.patch&lt;br /&gt;
 cd ..&lt;br /&gt;
 cvs -z8 -d:pserver:anonymous@lirc.cvs.sourceforge.net:/cvsroot/lirc co lirc&lt;br /&gt;
 cd lirc-0.8.3&lt;br /&gt;
 ./configure --prefix=/usr --with-driver=all&lt;br /&gt;
 make&lt;br /&gt;
 make install &lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
=====Video driver=====&lt;br /&gt;
You will most likely need to reinstall your video driver at this point, if you used a proprietary binary version. Instructions for getting the latest driver and installing it can be found in the [[Display Drivers|display drivers]] wiki.&lt;br /&gt;
&lt;br /&gt;
For nVidia do this:&lt;br /&gt;
 wget http://us.download.nvidia.com/XFree86/Linux-x86/177.80/NVIDIA-Linux-x86-177.80-pkg1.run&lt;br /&gt;
 sh NVIDIA-Linux-x86-177.80-pkg1.run&lt;br /&gt;
&lt;br /&gt;
If you have already had a newer version of the driver installed, then just install the kernel module like this :&lt;br /&gt;
 sh NVIDIA-Linux-x86-XXX.XX-pkg1.run -K&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Now it is a good idea to compare your lsmod output from your old kernel to the output of your new kernel. Just to be certain you didn&#039;t miss anything. I found the order to be different, so I copied the output to an Excel spreadsheet and sorted the two different lists. The only discrepancies I found were related to name changes in the kernel and AppArmor.&lt;br /&gt;
&lt;br /&gt;
=====Tuner and other drivers=====&lt;br /&gt;
Don&#039;t forget to recompile and install other drivers which you may have had to install to get your system working.  These include the V4L DVB drivers.&lt;br /&gt;
&lt;br /&gt;
====Media Directors====&lt;br /&gt;
In a traditional installation the Core and Media Directors all run the Gutsy 2.6.22-14 kernel. You may still use this kernel if you like, or you may opt to use your newly built kernel. &lt;br /&gt;
===Use old kernel===&lt;br /&gt;
If you want the media directors to continue to use this old kernel then you must create a symlink to the old kernel in the boot directory of each MD. You must also update the MD archives with this symlink, so future MDs will be setup correctly.&lt;br /&gt;
&lt;br /&gt;
 mkdir /tmp/moonfs_64 /tmp/moonfs_32&lt;br /&gt;
 tar -jxvf /usr/pluto/install/PlutMD-adm64.tar.bz2 /tmp/moonfs_64/&lt;br /&gt;
 tar -jxvf /usr/pluto/install/PlutMD-i386.tar.bz2 /tmp/moonfs_32/&lt;br /&gt;
 for md in /usr/pluto/diskless/* /tmp/moonfs_64 /tmp/moonfs_32; do&lt;br /&gt;
 md_device=`echo &amp;quot;$md&amp;quot; | sed -e &#039;s/.*[/]\([^/]\)/\1/g&#039;`&lt;br /&gt;
 cd $md/boot&lt;br /&gt;
 ln -s vmlinuz-2.6.22-14-generic vmlinuz-2.6.26.5&lt;br /&gt;
 ln -s initrd.img-2.6.22-14-generic initrd.img-2.6.26.5&lt;br /&gt;
 done&lt;br /&gt;
 tar -C /tmp/moonfs_64 -jcvpf /usr/pluto/install/PlutoMD-adm64.tar.bz2 .&lt;br /&gt;
 tar -C /tmp/moonfs_32 -jcvpf /usr/pluto/install/PlutoMD-i386.tar.bz2 .&lt;br /&gt;
 rm -rf /tmp/moonfs_*&lt;br /&gt;
&lt;br /&gt;
=====Use new kernel=====&lt;br /&gt;
A better route, although more complex one is to use your new kernel on the media directors as well. You can do this by copying your kernel and modules to each MD root filesystem. Additionally, you will need to add the kernel image plus modules to the MD root archive (/usr/pluto/install/PlutoMD-xxxyyy.tar.bz2) where xxxyyy is your architecture. This does present an issue if your core and media directors are not the same architecture. In this case you will need to build a kernel for the other architecture using cross-compile methods or using a machine of the that architecture. &lt;br /&gt;
&lt;br /&gt;
These scripts serve as a guideline, and may need to be customized to your unique configuration. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;A few notes:&#039;&#039;&#039;&lt;br /&gt;
* Your initrd-img file should be about 10MB. If it is around the 40MB mark you compiled your kernel with debugging support. The tftp server will refuse to transfer files this large. As a result, all MDs will fail to boot. If you absolutely must use a debugging kernel then there are options you can pass to tftp to make it ignore this limit.&lt;br /&gt;
* These scripts assume all media directors and cores are 64-bit machines. It is left as an exercise for the reader to distribute the proper kernel image for the target MD&#039;s architecture.&lt;br /&gt;
* You should build your video driver files first, so you can include them in your MD archive.&lt;br /&gt;
&lt;br /&gt;
 for md in /usr/pluto/diskless/*; do&lt;br /&gt;
 md_device=`echo &amp;quot;$md&amp;quot; | sed -e &#039;s/.*[/]\([^/]\)/\1/g&#039;`&lt;br /&gt;
 cp /boot/vmlinuz-2.6.26.5 $md/boot/&lt;br /&gt;
 cp /boot/initrd.img-2.6.26.5 $md/boot/&lt;br /&gt;
 cp -r /lib/modules/2.6.26.5/ $md/lib/modules/&lt;br /&gt;
 /usr/pluto/bin/Diskless_InstallKernel.sh $md_device&lt;br /&gt;
 done&lt;br /&gt;
 /usr/pluto/bin/Diskless_BuildDefaultImage.sh&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Now rebuild the archives, so future Media Directors will get the correct kernel image. &lt;br /&gt;
 cd /tmp&lt;br /&gt;
 mkdir moonfs_x64&lt;br /&gt;
 cd moonfs_x64&lt;br /&gt;
 tar -jxvf /usr/pluto/install/PlutMD-adm64.tar.bz2&lt;br /&gt;
 cp /boot/vmlinuz-2.6.26.5 boot&lt;br /&gt;
 cp /boot/initrd.img-2.6.26.5 boot&lt;br /&gt;
 cp -r /lib/modules/2.6.26.5/ lib/modules/&lt;br /&gt;
 tar -jcvpf /usr/pluto/install/PlutoMD-adm64.tar.bz2 *&lt;br /&gt;
 cd ..&lt;br /&gt;
 rm -rf moonfs_x64&lt;br /&gt;
&lt;br /&gt;
====Video Drivers====&lt;br /&gt;
Video drivers for Media Directors get their own section because they often require updated libraries in addition to updated kernel modules. These libraries will have to be distributed to the media directors and updated in the archive. nVidia&#039;s driver installation script provides many useful options for this. I have not looked into a way to do with the ATI drivers, but I assume it&#039;s similar. &lt;br /&gt;
&lt;br /&gt;
You will need this small script I made. NVIDIA packages the precompiled kernel interface with a proprietary header. Removing the header allows you to link the interface and kernel module manually.&lt;br /&gt;
&lt;br /&gt;
stripheader.sh&lt;br /&gt;
 readsint ()&lt;br /&gt;
 {&lt;br /&gt;
   byte=`head -c$2 $1 | tail -c1`&lt;br /&gt;
   sint=`printf &#039;%u&#039; &amp;quot;&#039;$byte&amp;quot;`&lt;br /&gt;
   let &amp;quot;sint=$sint &amp;amp; 0xFF&amp;quot;&lt;br /&gt;
   eval &amp;quot;$3=\&amp;quot;$sint\&amp;quot;&amp;quot;&lt;br /&gt;
 }&lt;br /&gt;
 readuint32 ()&lt;br /&gt;
 {&lt;br /&gt;
   readsint $1 $(($2+1)) b1&lt;br /&gt;
   readsint $1 $(($2+2)) b2&lt;br /&gt;
   readsint $1 $(($2+3)) b3&lt;br /&gt;
   readsint $1 $(($2+4)) b4 &lt;br /&gt;
 &lt;br /&gt;
   uint=$(( ($b4 &amp;lt;&amp;lt; 24) + ($b3 &amp;lt;&amp;lt; 16) + ($b2 &amp;lt;&amp;lt; 8) + $b1 ))&lt;br /&gt;
   eval &amp;quot;$3=\&amp;quot;$uint\&amp;quot;&amp;quot;&lt;br /&gt;
 } &lt;br /&gt;
 &lt;br /&gt;
 let &amp;quot;header=12&amp;quot;&lt;br /&gt;
 readuint32 $1 $header int&lt;br /&gt;
 let &amp;quot;header=$header+$int+4&amp;quot;&lt;br /&gt;
 readuint32 $1 $header int&lt;br /&gt;
 let &amp;quot;header=$header+$int+4&amp;quot;&lt;br /&gt;
 readuint32 $1 $header int&lt;br /&gt;
 let &amp;quot;header=$header+$int+4&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
 precomp=$(stat -c%s &amp;quot;$1&amp;quot;)&lt;br /&gt;
 let &amp;quot;precomp-=$header&amp;quot;&lt;br /&gt;
 tail -c$precomp $1 &amp;gt; $2&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
These commands will update each Media Director. You should also copy these files into the MD archives. This is left as an exercise for the reader.&lt;br /&gt;
&lt;br /&gt;
 wget http://us.download.nvidia.com/XFree86/Linux-x86_64/173.14.12/NVIDIA-Linux-x86_64-173.14.12-pkg2.run&lt;br /&gt;
 sh NVIDIA-Linux-x86_64-173.14.12-pkg2.run --keep --add-this-kernel&lt;br /&gt;
 ./stripheader.sh NVIDIA-Linux-x86_64-173.14.12-pkg2/usr/src/nv/precompiled/precompiled-nv-linux.o* NVIDIA-Linux-x86_64-173.14.12-pkg2/usr/src/nv/nv-linux.o&lt;br /&gt;
 ld -d -r -o nvidia.ko NVIDIA-Linux-x86_64-173.14.12-pkg2/usr/src/nv/nv-linux.o NVIDIA-Linux-x86_64-173.14.12-pkg2/usr/src/nv/nv-kernel.o&lt;br /&gt;
 for md in /usr/pluto/diskless/*; do&lt;br /&gt;
 cp -r NVIDIA-Linux-x86_64-173.14.12-pkg2/usr/* $md/usr/&lt;br /&gt;
 cp nvidia.ko $md/lib/modules/2.6.26.5/kernel/drivers/video/&lt;br /&gt;
 done&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Sony_KDL-46W4500&amp;diff=18284</id>
		<title>Sony KDL-46W4500</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Sony_KDL-46W4500&amp;diff=18284"/>
		<updated>2009-04-03T10:42:19Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Hardware]]&lt;br /&gt;
[[Category:Video]]&lt;br /&gt;
[[Category:Displays]]&lt;br /&gt;
&lt;br /&gt;
I am using an &#039;&#039;&#039;European&#039;&#039;&#039; version this TV and will try to describe problems I have here.&lt;br /&gt;
&lt;br /&gt;
Connected to a Nvidia 7300GT with an DVI to HDMI cable.&lt;br /&gt;
&lt;br /&gt;
I was not able to get the TV setup to 1080p with 50hz, so I choosed 1080p and 60hz. Then afterwards I changed the xorg.conf and changed/added the folowing lines :&lt;br /&gt;
&lt;br /&gt;
 Option         &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
 Option         &amp;quot;UseEDID&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 Modes       &amp;quot;1920x1080_50&amp;quot;&lt;br /&gt;
 VertRefresh     49-51&lt;br /&gt;
&lt;br /&gt;
and rebooted. After that I had 50hz.&lt;br /&gt;
&lt;br /&gt;
The line &amp;quot;1920x1080_50&amp;quot; uses the EDID information it gets of the TV and sets things up correctly. In the /var/log/Xorg.0.log you can then see that it chooses the right resolution.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot; is important, otherwise you will get very small unreadable characters.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Alternate solution (I used first).&lt;br /&gt;
&lt;br /&gt;
I was not able to get the TV setup to 1080p with 50hz, so I choosed 1080p and 60hz. Then afterwards I changed the xorg.conf to the right 1080p@50hz Modeline i found in the HDTV list in the MythTV modeline database.&lt;br /&gt;
&lt;br /&gt;
        # 1920x1080 @ 50 Hz (EDID) HSync: 56.25 kHz&lt;br /&gt;
        ModeLine &amp;quot;1920x1080&amp;quot; 148.50 1920 2448 2496 2640 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
&lt;br /&gt;
And changed the VertRefresh to :&lt;br /&gt;
        VertRefresh     49-51&lt;br /&gt;
&lt;br /&gt;
and rebooted. After that I had 50hz.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
My latest xorg.conf&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
  Section &amp;quot;ServerLayout&amp;quot;&lt;br /&gt;
          Identifier      &amp;quot;XFree86 Configured&amp;quot;&lt;br /&gt;
          Screen    0     &amp;quot;Screen0&amp;quot;       0 0&lt;br /&gt;
          InputDevice     &amp;quot;Mouse0&amp;quot;        &amp;quot;CorePointer&amp;quot;&lt;br /&gt;
          InputDevice     &amp;quot;Keyboard0&amp;quot;     &amp;quot;CoreKeyboard&amp;quot;&lt;br /&gt;
  EndSection&lt;br /&gt;
  &lt;br /&gt;
  Section &amp;quot;Files&amp;quot;&lt;br /&gt;
          RgbPath         &amp;quot;/usr/X11R6/lib/X11/rgb&amp;quot;&lt;br /&gt;
          ModulePath      &amp;quot;/usr/lib/xorg/modules&amp;quot;&lt;br /&gt;
          FontPath        &amp;quot;/usr/share/fonts/X11&amp;quot;&lt;br /&gt;
          FontPath        &amp;quot;/usr/X11R6/lib/X11/fonts/misc/&amp;quot;&lt;br /&gt;
          FontPath        &amp;quot;/usr/X11R6/lib/X11/fonts/Speedo/&amp;quot;&lt;br /&gt;
          FontPath        &amp;quot;/usr/X11R6/lib/X11/fonts/Type1/&amp;quot;&lt;br /&gt;
          FontPath        &amp;quot;/usr/X11R6/lib/X11/fonts/CID/&amp;quot;&lt;br /&gt;
          FontPath        &amp;quot;/usr/X11R6/lib/X11/fonts/75dpi/&amp;quot;&lt;br /&gt;
          FontPath        &amp;quot;/usr/X11R6/lib/X11/fonts/100dpi/&amp;quot;&lt;br /&gt;
  EndSection&lt;br /&gt;
  &lt;br /&gt;
  Section &amp;quot;Module&amp;quot;&lt;br /&gt;
          Load    &amp;quot;dbe&amp;quot;&lt;br /&gt;
          Load    &amp;quot;extmod&amp;quot;&lt;br /&gt;
          Load    &amp;quot;record&amp;quot;&lt;br /&gt;
          Load    &amp;quot;xtrap&amp;quot;&lt;br /&gt;
          Load    &amp;quot;speedo&amp;quot;&lt;br /&gt;
          Load    &amp;quot;type1&amp;quot;&lt;br /&gt;
          Load    &amp;quot;glx&amp;quot;&lt;br /&gt;
          Load    &amp;quot;int10&amp;quot;&lt;br /&gt;
          Load    &amp;quot;v4l&amp;quot;&lt;br /&gt;
  EndSection&lt;br /&gt;
  &lt;br /&gt;
  Section &amp;quot;InputDevice&amp;quot;&lt;br /&gt;
          Identifier      &amp;quot;Keyboard0&amp;quot;&lt;br /&gt;
          Driver          &amp;quot;keyboard&amp;quot;&lt;br /&gt;
          Option          &amp;quot;XkbLayout&amp;quot;     &amp;quot;dk&amp;quot;&lt;br /&gt;
          Option          &amp;quot;XkbVariant&amp;quot;    &amp;quot;basic&amp;quot;&lt;br /&gt;
          Option          &amp;quot;XkbModel&amp;quot;              &amp;quot;pc105&amp;quot;&lt;br /&gt;
  EndSection&lt;br /&gt;
  &lt;br /&gt;
  Section &amp;quot;InputDevice&amp;quot;&lt;br /&gt;
          Identifier      &amp;quot;Mouse0&amp;quot;&lt;br /&gt;
          Driver          &amp;quot;mouse&amp;quot;&lt;br /&gt;
          Option          &amp;quot;Protocol&amp;quot;              &amp;quot;auto&amp;quot;&lt;br /&gt;
          Option          &amp;quot;Device&amp;quot;                &amp;quot;/dev/input/mice&amp;quot;&lt;br /&gt;
          Option          &amp;quot;ZAxisMapping&amp;quot;  &amp;quot;4 5&amp;quot;&lt;br /&gt;
  EndSection&lt;br /&gt;
  &lt;br /&gt;
  Section &amp;quot;Monitor&amp;quot;&lt;br /&gt;
          Identifier      &amp;quot;Monitor0&amp;quot;&lt;br /&gt;
          VendorName      &amp;quot;Unknown Monitor Vendor&amp;quot;&lt;br /&gt;
          ModelName       &amp;quot;Unknown Monitor Model&amp;quot;&lt;br /&gt;
  &lt;br /&gt;
          # gtf 1920 1080 50&lt;br /&gt;
          #&lt;br /&gt;
          # 1920x1080 @ 25 Hz (EDID) HSync: 28.125 kHz&lt;br /&gt;
          # 1920x1080 @ 50 Hz (EDID) HSync: 56.25 kHz&lt;br /&gt;
          # ORG Modeline  &amp;quot;1920x1080&amp;quot; 148.5 1920 1960 2016 2200 1080 1082 1088 1125&lt;br /&gt;
          # ORG VertRefresh       59-61&lt;br /&gt;
          # 1920x1080 @ 25 Hz (EDID) HSync: 28.125 kHz&lt;br /&gt;
          # ModeLine &amp;quot;1920x1080&amp;quot; 74.25 1920 2448 2492 2640 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
          # 1920x1080 @ 50 Hz (EDID) HSync: 56.25 kHz&lt;br /&gt;
          # ModeLine &amp;quot;1920x1080&amp;quot; 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
          #&lt;br /&gt;
          # 1920x1080 @ 50 Hz (EDID) HSync: 28.125 kHz&lt;br /&gt;
          ModeLine &amp;quot;1920x1080_my50i&amp;quot; 74.25 1920 2448 2492 2640 1080 1084 1094 1124 +HSync +VSync Interlace&lt;br /&gt;
          #&lt;br /&gt;
          # From Powerstrip 1920x1080 @ 24hz&lt;br /&gt;
          # ModeLine &amp;quot;1920x1080&amp;quot; 74.250 1920 2560 2608 2752 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
          # From Powerstrip 1920x1080 @ 25hz&lt;br /&gt;
          # Xorg.log said 24,9hz / try adding some more&lt;br /&gt;
          # ModeLine &amp;quot;1920x1080&amp;quot; 77.142 1920 2560 2608 2752 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
          ModeLine &amp;quot;1920x1080_my25&amp;quot; 77.500 1920 2560 2608 2752 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
          # VertRefresh   24-26&lt;br /&gt;
          #&lt;br /&gt;
          # From Powerstrip 1920x1080 @ 50hz&lt;br /&gt;
          ModeLine &amp;quot;1920x1080_my50&amp;quot; 148.500 1920 2448 2496 2640 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
          # ModeLine &amp;quot;1920x1080_my50a&amp;quot; 148.750 1920 2448 2496 2640 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
          VertRefresh     24-51&lt;br /&gt;
          HorizSync       20-500&lt;br /&gt;
          # VertRefresh   49-51&lt;br /&gt;
  EndSection&lt;br /&gt;
  &lt;br /&gt;
  Section &amp;quot;Device&amp;quot;&lt;br /&gt;
          ### Available Driver options are:-&lt;br /&gt;
          ### Values: &amp;lt;i&amp;gt;: integer, &amp;lt;f&amp;gt;: float, &amp;lt;bool&amp;gt;: &amp;quot;True&amp;quot;/&amp;quot;False&amp;quot;,&lt;br /&gt;
          ### &amp;lt;string&amp;gt;: &amp;quot;String&amp;quot;, &amp;lt;freq&amp;gt;: &amp;quot;&amp;lt;f&amp;gt; Hz/kHz/MHz&amp;quot;&lt;br /&gt;
          ### [arg]: arg optional&lt;br /&gt;
          #Option         &amp;quot;NoAccel&amp;quot;                               # [&amp;lt;bool&amp;gt;]&lt;br /&gt;
          #Option         &amp;quot;SWcursor&amp;quot;                              # [&amp;lt;bool&amp;gt;]&lt;br /&gt;
          #Option         &amp;quot;ColorKey&amp;quot;                              # &amp;lt;i&amp;gt;&lt;br /&gt;
          #Option         &amp;quot;CacheLines&amp;quot;                    # &amp;lt;i&amp;gt;&lt;br /&gt;
          #Option         &amp;quot;Dac6Bit&amp;quot;                               # [&amp;lt;bool&amp;gt;]&lt;br /&gt;
          #Option         &amp;quot;DRI&amp;quot;                                   # [&amp;lt;bool&amp;gt;]&lt;br /&gt;
          #Option         &amp;quot;NoDDC&amp;quot;                                 # [&amp;lt;bool&amp;gt;]&lt;br /&gt;
          #Option         &amp;quot;ShowCache&amp;quot;                             # [&amp;lt;bool&amp;gt;]&lt;br /&gt;
          #Option         &amp;quot;XvMCSurfaces&amp;quot;                  # &amp;lt;i&amp;gt;&lt;br /&gt;
          Identifier      &amp;quot;Card0&amp;quot;&lt;br /&gt;
          Driver          &amp;quot;nvidia&amp;quot;&lt;br /&gt;
          VendorName      &amp;quot;Unknown Vendor Name&amp;quot;&lt;br /&gt;
          BoardName       &amp;quot;Unknown Board Name&amp;quot;&lt;br /&gt;
          Option          &amp;quot;LinearAlloc&amp;quot;           &amp;quot;16384&amp;quot;&lt;br /&gt;
          #BusID          &amp;quot;PCI:0:2:0&amp;quot;&lt;br /&gt;
  #       Option          &amp;quot;NoDDC&amp;quot;                         &amp;quot;true&amp;quot;&lt;br /&gt;
     Option         &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
     ## Option         &amp;quot;UseEDIDFreqs&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
          Option &amp;quot;XvmcUsesTextures&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          Option &amp;quot;renderAccel&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          Option &amp;quot;NoDDCValue&amp;quot;&lt;br /&gt;
          ## Option &amp;quot;UseEDID&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
          Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          Option &amp;quot;NoLogo&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          Option &amp;quot;NoBandWidthTest&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          # Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes&amp;quot;&lt;br /&gt;
          Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoVertRefreshCheck, NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes&amp;quot;&lt;br /&gt;
          Option &amp;quot;DynamicTwinView&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
          Option &amp;quot;UseEvents&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          Option &amp;quot;AllowGLXWithComposite&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          Option &amp;quot;AddARGBGLXVisuals&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          Option          &amp;quot;ConnectedMonitor&amp;quot; &amp;quot;DFP&amp;quot;&lt;br /&gt;
  EndSection&lt;br /&gt;
  &lt;br /&gt;
  Section &amp;quot;Screen&amp;quot;&lt;br /&gt;
          Identifier      &amp;quot;Screen0&amp;quot;&lt;br /&gt;
          Device          &amp;quot;Card0&amp;quot;&lt;br /&gt;
          Monitor         &amp;quot;Monitor0&amp;quot;&lt;br /&gt;
          DefaultDepth    24&lt;br /&gt;
          SubSection &amp;quot;Display&amp;quot;&lt;br /&gt;
                  # Modes         &amp;quot;1920x1080&amp;quot;&lt;br /&gt;
                  Modes           &amp;quot;1920x1080_50_1&amp;quot; &amp;quot;1920x1080_50_0&amp;quot; &amp;quot;1920x1080_50&amp;quot; &amp;quot;1920x1080_my50&amp;quot;&lt;br /&gt;
                  # Modes         &amp;quot;1920x1080_my50a&amp;quot; &amp;quot;1920x1080_50&amp;quot; &amp;quot;1920x1080_50_0&amp;quot; &amp;quot;1920x1080&amp;quot;&lt;br /&gt;
                  #TESTED Modes           &amp;quot;1920x1080_50_0&amp;quot; &amp;quot;1920x1080_50i_0&amp;quot; &amp;quot;1920x1080_50i&amp;quot; &amp;quot;1920x1080_my50i&amp;quot; &amp;quot;1920x1080_my25&amp;quot; &amp;quot;1920x1080&amp;quot;&lt;br /&gt;
                  Virtual         1920 1080&lt;br /&gt;
          EndSubSection&lt;br /&gt;
     Option         &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
     ## Option         &amp;quot;UseEDIDFreqs&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
          Option &amp;quot;XvmcUsesTextures&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          Option &amp;quot;renderAccel&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          Option &amp;quot;NoDDCValue&amp;quot;&lt;br /&gt;
          ## Option &amp;quot;UseEDID&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
          Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          Option &amp;quot;NoLogo&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          Option &amp;quot;NoBandWidthTest&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          # Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes&amp;quot;&lt;br /&gt;
          Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoVertRefreshCheck, NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes&amp;quot;&lt;br /&gt;
          Option &amp;quot;DynamicTwinView&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
          Option &amp;quot;UseEvents&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          Option &amp;quot;AllowGLXWithComposite&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          Option &amp;quot;AddARGBGLXVisuals&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
          Option  &amp;quot;TVStandard&amp;quot;    &amp;quot;1080p&amp;quot;&lt;br /&gt;
  EndSection&lt;br /&gt;
  &lt;br /&gt;
  Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
          Option  &amp;quot;AllowMouseOpenFail&amp;quot;    &amp;quot;true&amp;quot;&lt;br /&gt;
          Option  &amp;quot;BlankTime&amp;quot;             &amp;quot;0&amp;quot;&lt;br /&gt;
          Option  &amp;quot;StandbyTime&amp;quot;   &amp;quot;0&amp;quot;&lt;br /&gt;
          Option  &amp;quot;SuspendTime&amp;quot;   &amp;quot;0&amp;quot;&lt;br /&gt;
          Option  &amp;quot;OffTime&amp;quot;               &amp;quot;0&amp;quot;&lt;br /&gt;
          Option  &amp;quot;AIGLX&amp;quot;                 &amp;quot;Off&amp;quot;&lt;br /&gt;
  EndSection&lt;br /&gt;
  Section &amp;quot;Extensions&amp;quot;&lt;br /&gt;
          Option &amp;quot;Composite&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
          Option &amp;quot;RENDER&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
  EndSection&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Sony_KDL-46W4500&amp;diff=18283</id>
		<title>Sony KDL-46W4500</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Sony_KDL-46W4500&amp;diff=18283"/>
		<updated>2009-04-03T08:39:39Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Hardware]]&lt;br /&gt;
[[Category:Video]]&lt;br /&gt;
[[Category:Displays]]&lt;br /&gt;
&lt;br /&gt;
I am using an &#039;&#039;&#039;European&#039;&#039;&#039; version this TV and will try to describe problems I have here.&lt;br /&gt;
&lt;br /&gt;
Connected to a Nvidia 7300GT with an DVI to HDMI cable.&lt;br /&gt;
&lt;br /&gt;
I was not able to get the TV setup to 1080p with 50hz, so I choosed 1080p and 60hz. Then afterwards I changed the xorg.conf and changed/added the folowing lines :&lt;br /&gt;
&lt;br /&gt;
 Option         &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
 Option         &amp;quot;UseEDID&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 Modes       &amp;quot;1920x1080_50&amp;quot;&lt;br /&gt;
 VertRefresh     49-51&lt;br /&gt;
&lt;br /&gt;
and rebooted. After that I had 50hz.&lt;br /&gt;
&lt;br /&gt;
The line &amp;quot;1920x1080_50&amp;quot; uses the EDID information it gets of the TV and sets things up correctly. In the /var/log/Xorg.0.log you can then see that it chooses the right resolution.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot; is important, otherwise you will get very small unreadable characters.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Alternate solution (I used first).&lt;br /&gt;
&lt;br /&gt;
I was not able to get the TV setup to 1080p with 50hz, so I choosed 1080p and 60hz. Then afterwards I changed the xorg.conf to the right 1080p@50hz Modeline i found in the HDTV list in the MythTV modeline database.&lt;br /&gt;
&lt;br /&gt;
        # 1920x1080 @ 50 Hz (EDID) HSync: 56.25 kHz&lt;br /&gt;
        ModeLine &amp;quot;1920x1080&amp;quot; 148.50 1920 2448 2496 2640 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
&lt;br /&gt;
And changed the VertRefresh to :&lt;br /&gt;
        VertRefresh     49-51&lt;br /&gt;
&lt;br /&gt;
and rebooted. After that I had 50hz.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
My latest xorg.conf&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 # xorg.conf (xorg X Window System server configuration file)&lt;br /&gt;
 #&lt;br /&gt;
 # This file was generated by dexconf, the Debian X Configuration tool, using&lt;br /&gt;
 # values from the debconf database.&lt;br /&gt;
 #&lt;br /&gt;
 # Edit this file with caution, and see the xorg.conf manual page.&lt;br /&gt;
 # (Type &amp;quot;man xorg.conf&amp;quot; at the shell prompt.)&lt;br /&gt;
 #&lt;br /&gt;
 # This file is automatically updated on xserver-xorg package upgrades *only*&lt;br /&gt;
 # if it has not been modified since the last upgrade of the xserver-xorg&lt;br /&gt;
 # package.&lt;br /&gt;
 #&lt;br /&gt;
 # If you have edited this file but would like it to be automatically updated&lt;br /&gt;
 # again, run the following command:&lt;br /&gt;
 #   sudo dpkg-reconfigure -phigh xserver-xorg &lt;br /&gt;
&lt;br /&gt;
 Section &amp;quot;Files&amp;quot;&lt;br /&gt;
 EndSection&lt;br /&gt;
&lt;br /&gt;
 Section &amp;quot;InputDevice&amp;quot;&lt;br /&gt;
        Identifier      &amp;quot;Generic Keyboard&amp;quot;&lt;br /&gt;
        Driver          &amp;quot;kbd&amp;quot;&lt;br /&gt;
        Option          &amp;quot;CoreKeyboard&amp;quot;&lt;br /&gt;
        Option          &amp;quot;XkbRules&amp;quot;      &amp;quot;xorg&amp;quot;&lt;br /&gt;
        Option          &amp;quot;XkbModel&amp;quot;      &amp;quot;pc105&amp;quot;&lt;br /&gt;
        Option          &amp;quot;XkbLayout&amp;quot;     &amp;quot;dk&amp;quot;&lt;br /&gt;
        Option          &amp;quot;XkbVariant&amp;quot;    &amp;quot;basic&amp;quot;&lt;br /&gt;
 EndSection&lt;br /&gt;
&lt;br /&gt;
 Section &amp;quot;InputDevice&amp;quot;&lt;br /&gt;
        Identifier      &amp;quot;Configured Mouse&amp;quot;&lt;br /&gt;
        Driver          &amp;quot;mouse&amp;quot;&lt;br /&gt;
        Option          &amp;quot;CorePointer&amp;quot;&lt;br /&gt;
        Option          &amp;quot;Device&amp;quot;                &amp;quot;/dev/input/mice&amp;quot;&lt;br /&gt;
        Option          &amp;quot;Protocol&amp;quot;              &amp;quot;ImPS/2&amp;quot;&lt;br /&gt;
        Option          &amp;quot;ZAxisMapping&amp;quot;          &amp;quot;4 5&amp;quot;&lt;br /&gt;
        Option          &amp;quot;Emulate3Buttons&amp;quot;       &amp;quot;true&amp;quot;&lt;br /&gt;
 EndSection&lt;br /&gt;
&lt;br /&gt;
 Section &amp;quot;InputDevice&amp;quot;&lt;br /&gt;
        Driver          &amp;quot;wacom&amp;quot;&lt;br /&gt;
        Identifier      &amp;quot;stylus&amp;quot;&lt;br /&gt;
        Option          &amp;quot;Device&amp;quot;        &amp;quot;/dev/input/wacom&amp;quot;&lt;br /&gt;
        Option          &amp;quot;Type&amp;quot;          &amp;quot;stylus&amp;quot;&lt;br /&gt;
        Option          &amp;quot;ForceDevice&amp;quot;   &amp;quot;ISDV4&amp;quot;         # Tablet PC ONLY&lt;br /&gt;
 EndSection&lt;br /&gt;
&lt;br /&gt;
 Section &amp;quot;InputDevice&amp;quot;&lt;br /&gt;
        Driver          &amp;quot;wacom&amp;quot;&lt;br /&gt;
        Identifier      &amp;quot;eraser&amp;quot;&lt;br /&gt;
        Option          &amp;quot;Device&amp;quot;        &amp;quot;/dev/input/wacom&amp;quot;&lt;br /&gt;
        Option          &amp;quot;Type&amp;quot;          &amp;quot;eraser&amp;quot;&lt;br /&gt;
        Option          &amp;quot;ForceDevice&amp;quot;   &amp;quot;ISDV4&amp;quot;         # Tablet PC ONLY&lt;br /&gt;
 EndSection&lt;br /&gt;
&lt;br /&gt;
 Section &amp;quot;InputDevice&amp;quot;&lt;br /&gt;
        Driver          &amp;quot;wacom&amp;quot;&lt;br /&gt;
        Identifier      &amp;quot;cursor&amp;quot;&lt;br /&gt;
        Option          &amp;quot;Device&amp;quot;        &amp;quot;/dev/input/wacom&amp;quot;&lt;br /&gt;
        Option          &amp;quot;Type&amp;quot;          &amp;quot;cursor&amp;quot;&lt;br /&gt;
        Option          &amp;quot;ForceDevice&amp;quot;   &amp;quot;ISDV4&amp;quot;         # Tablet PC ONLY&lt;br /&gt;
 EndSection&lt;br /&gt;
&lt;br /&gt;
 Section &amp;quot;Device&amp;quot;&lt;br /&gt;
        Identifier      &amp;quot;ATI Technologies Inc ATI&amp;quot;&lt;br /&gt;
        Driver      &amp;quot;fglrx&amp;quot;&lt;br /&gt;
&lt;br /&gt;
        # Driver                &amp;quot;vesa&amp;quot;&lt;br /&gt;
        # BusID         &amp;quot;PCI:1:5:0&amp;quot;&lt;br /&gt;
        Option &amp;quot;XvmcUsesTextures&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        Option &amp;quot;renderAccel&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        Option &amp;quot;NoDDCValue&amp;quot;&lt;br /&gt;
        Option &amp;quot;UseEDID&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
        Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        Option &amp;quot;NoLogo&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        Option &amp;quot;NoBandWidthTest&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes&amp;quot;&lt;br /&gt;
        Option &amp;quot;DynamicTwinView&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
        Option &amp;quot;UseEvents&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        Option          &amp;quot;ConnectedMonitor&amp;quot; &amp;quot;DFP&amp;quot;&lt;br /&gt;
 EndSection&lt;br /&gt;
&lt;br /&gt;
 Section &amp;quot;Monitor&amp;quot;&lt;br /&gt;
        Identifier      &amp;quot;SyncMaster&amp;quot;&lt;br /&gt;
        Option          &amp;quot;DPMS&amp;quot;&lt;br /&gt;
&lt;br /&gt;
        # 1680x1050 @ 60.00 Hz (GTF) hsync: 65.22 kHz; pclk: 147.14 MHz&lt;br /&gt;
&lt;br /&gt;
        # 1920x1080 @ 25 Hz (EDID) HSync: 28.125 kHz&lt;br /&gt;
        #                 # 1920x1080 @ 50 Hz (EDID) HSync: 56.25 kHz&lt;br /&gt;
        #&lt;br /&gt;
 # FROM xorglog  Default mode &amp;quot;1920x1080&amp;quot;: 148.5 MHz (scaled from 0.0 MHz), 56.2 kHz, 50.0 Hz&lt;br /&gt;
        Modeline        &amp;quot;1920x1080&amp;quot; 148.5 1920 1960 2016 2200 1080 1082 1088 1125&lt;br /&gt;
        HorizSync       20-500&lt;br /&gt;
        VertRefresh     59-61&lt;br /&gt;
 EndSection&lt;br /&gt;
&lt;br /&gt;
 Section &amp;quot;Screen&amp;quot;&lt;br /&gt;
        Identifier      &amp;quot;Default Screen&amp;quot;&lt;br /&gt;
        Device          &amp;quot;ATI Technologies Inc ATI&amp;quot;&lt;br /&gt;
        Monitor         &amp;quot;SyncMaster&amp;quot;&lt;br /&gt;
        DefaultDepth    24&lt;br /&gt;
        SubSection &amp;quot;Display&amp;quot;&lt;br /&gt;
                Modes           &amp;quot;1920x1080&amp;quot;&lt;br /&gt;
                Virtual         1920 1080&lt;br /&gt;
        EndSubSection&lt;br /&gt;
        Option &amp;quot;XvmcUsesTextures&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        Option &amp;quot;renderAccel&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        Option &amp;quot;NoDDCValue&amp;quot;&lt;br /&gt;
        Option &amp;quot;UseEDID&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
        Option &amp;quot;ExactModeTimingsDVI&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        Option &amp;quot;NoLogo&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        Option &amp;quot;NoBandWidthTest&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        Option &amp;quot;ModeValidation&amp;quot; &amp;quot;NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes&amp;quot;&lt;br /&gt;
        Option &amp;quot;DynamicTwinView&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
        Option &amp;quot;UseEvents&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
        Option  &amp;quot;TVStandard&amp;quot;    &amp;quot;1080p&amp;quot;&lt;br /&gt;
 EndSection&lt;br /&gt;
&lt;br /&gt;
 Section &amp;quot;ServerLayout&amp;quot;&lt;br /&gt;
        Identifier      &amp;quot;Default Layout&amp;quot;&lt;br /&gt;
        Screen          &amp;quot;Default Screen&amp;quot;&lt;br /&gt;
        InputDevice     &amp;quot;Generic Keyboard&amp;quot;&lt;br /&gt;
        InputDevice     &amp;quot;Configured Mouse&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 # Uncomment if you have a wacom tablet&lt;br /&gt;
 #       InputDevice     &amp;quot;stylus&amp;quot;        &amp;quot;SendCoreEvents&amp;quot;&lt;br /&gt;
 #       InputDevice     &amp;quot;cursor&amp;quot;        &amp;quot;SendCoreEvents&amp;quot;&lt;br /&gt;
 #       InputDevice     &amp;quot;eraser&amp;quot;        &amp;quot;SendCoreEvents&amp;quot;&lt;br /&gt;
 EndSection&lt;br /&gt;
 Section &amp;quot;Extensions&amp;quot;&lt;br /&gt;
        Option &amp;quot;Composite&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
        Option &amp;quot;RENDER&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
 EndSection&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Viking&amp;diff=18129</id>
		<title>User:Viking</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Viking&amp;diff=18129"/>
		<updated>2009-03-25T13:46:30Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[category:User Setups]]&lt;br /&gt;
&lt;br /&gt;
This is my system.&lt;br /&gt;
&lt;br /&gt;
1st MD TV :&lt;br /&gt;
* [[Sony_KDL-46W4500]] - 1080p resolution UI2 overlay interface&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Core :&lt;br /&gt;
* ASUS M3A-H/HDMI&lt;br /&gt;
* AMD Athlon 64 X2 5050e Sockel-AM2 Box&lt;br /&gt;
* be quiet Straight Power 350W ATX 2.2 &lt;br /&gt;
* Arctic Cooling Freezer 64 Pro PMW&lt;br /&gt;
* 2x DDR2-800 2048MB &lt;br /&gt;
* 2x Arctic Cooling 120x120x25 AF12025 PWM &lt;br /&gt;
* Pioneer DVR-216DBK black&lt;br /&gt;
* Sharkoon Revenge Economy Edition Case - black &lt;br /&gt;
* 3 x 1TB Samsung Spinpoint F1 HD103UI EcoGreen (in RAID5)&lt;br /&gt;
* Longshine LCS-8337TXR (PCI Express)&lt;br /&gt;
* PSU 350W be quiet  E6-350W Straight Power&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
1st MD :&lt;br /&gt;
* NVIDIA 7300GT grafikkort&lt;br /&gt;
* 1xGigabyte GA-MA78GM-S2H&lt;br /&gt;
* AMD Athlon 64 X2 5050e Sockel-AM2 Box&lt;br /&gt;
* be quiet Straight Power 350W ATX 2.2 &lt;br /&gt;
* Arctic Cooling Freezer 64 Pro PMW&lt;br /&gt;
* 2x DDR2-800 2048MB &lt;br /&gt;
* Pioneer DVR-216DBK black&lt;br /&gt;
* 3 x 1TB Samsung Spinpoint F1 HD103UI EcoGreen (in RAID5)&lt;br /&gt;
* Longshine LCS-8337TXR (PCI Express)&lt;br /&gt;
* PSU 350W be quiet  E6-350W Straight Power&lt;br /&gt;
* Silverstone LC17 case&lt;br /&gt;
&lt;br /&gt;
* USB-UIRT (søg i wiki/forum) infrarød sender/modtager&lt;br /&gt;
* Phillips SRM 5100 (Windows MCE remote control) - apparently not 100% compatible&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Network&lt;br /&gt;
* Digitus N-Way Switch 5 Gigabit ports 5x10/100/1000TX &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
TV cards &lt;br /&gt;
* TechnoTrend: S2-3200 (not in use yet, so not 100% sure if it works)&lt;br /&gt;
* 2 old  TechnoTrend DVB-s &lt;br /&gt;
* 1x Hauppauge WinTV Nova-TD  (DVB-T usb stick)&lt;br /&gt;
&lt;br /&gt;
Lightcontrol &lt;br /&gt;
* Tricklestar 200ZW-EU-W&lt;br /&gt;
* Tricklestar 300ZW-EU-W&lt;br /&gt;
&lt;br /&gt;
And a couple of  Z-wave devices to play with ;)&lt;br /&gt;
* Everspring SM103&lt;br /&gt;
* Everspring SP103&lt;br /&gt;
* http://www.zwave4u.com/products/en/Lighting-and-Power/PlugIn-Adapters/ACT-Homepro-ZRP-200-Schuko-Plugin-Switch.html&lt;br /&gt;
* http://www.zwave4u.com/products/en/Lighting-and-Power/PlugIn-Adapters/ACT-Homepro-ZDP-200-Schuko-Plugin-Dimmer.html&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Viking&amp;diff=18128</id>
		<title>User:Viking</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Viking&amp;diff=18128"/>
		<updated>2009-03-25T13:46:12Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[category:User Setups]]&lt;br /&gt;
&lt;br /&gt;
This is my system.&lt;br /&gt;
&lt;br /&gt;
1st MD TV :&lt;br /&gt;
* Sony [[Sony_KDL-46W4500]] - 1080p resolution UI2 overlay interface&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Core :&lt;br /&gt;
* ASUS M3A-H/HDMI&lt;br /&gt;
* AMD Athlon 64 X2 5050e Sockel-AM2 Box&lt;br /&gt;
* be quiet Straight Power 350W ATX 2.2 &lt;br /&gt;
* Arctic Cooling Freezer 64 Pro PMW&lt;br /&gt;
* 2x DDR2-800 2048MB &lt;br /&gt;
* 2x Arctic Cooling 120x120x25 AF12025 PWM &lt;br /&gt;
* Pioneer DVR-216DBK black&lt;br /&gt;
* Sharkoon Revenge Economy Edition Case - black &lt;br /&gt;
* 3 x 1TB Samsung Spinpoint F1 HD103UI EcoGreen (in RAID5)&lt;br /&gt;
* Longshine LCS-8337TXR (PCI Express)&lt;br /&gt;
* PSU 350W be quiet  E6-350W Straight Power&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
1st MD :&lt;br /&gt;
* NVIDIA 7300GT grafikkort&lt;br /&gt;
* 1xGigabyte GA-MA78GM-S2H&lt;br /&gt;
* AMD Athlon 64 X2 5050e Sockel-AM2 Box&lt;br /&gt;
* be quiet Straight Power 350W ATX 2.2 &lt;br /&gt;
* Arctic Cooling Freezer 64 Pro PMW&lt;br /&gt;
* 2x DDR2-800 2048MB &lt;br /&gt;
* Pioneer DVR-216DBK black&lt;br /&gt;
* 3 x 1TB Samsung Spinpoint F1 HD103UI EcoGreen (in RAID5)&lt;br /&gt;
* Longshine LCS-8337TXR (PCI Express)&lt;br /&gt;
* PSU 350W be quiet  E6-350W Straight Power&lt;br /&gt;
* Silverstone LC17 case&lt;br /&gt;
&lt;br /&gt;
* USB-UIRT (søg i wiki/forum) infrarød sender/modtager&lt;br /&gt;
* Phillips SRM 5100 (Windows MCE remote control) - apparently not 100% compatible&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Network&lt;br /&gt;
* Digitus N-Way Switch 5 Gigabit ports 5x10/100/1000TX &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
TV cards &lt;br /&gt;
* TechnoTrend: S2-3200 (not in use yet, so not 100% sure if it works)&lt;br /&gt;
* 2 old  TechnoTrend DVB-s &lt;br /&gt;
* 1x Hauppauge WinTV Nova-TD  (DVB-T usb stick)&lt;br /&gt;
&lt;br /&gt;
Lightcontrol &lt;br /&gt;
* Tricklestar 200ZW-EU-W&lt;br /&gt;
* Tricklestar 300ZW-EU-W&lt;br /&gt;
&lt;br /&gt;
And a couple of  Z-wave devices to play with ;)&lt;br /&gt;
* Everspring SM103&lt;br /&gt;
* Everspring SP103&lt;br /&gt;
* http://www.zwave4u.com/products/en/Lighting-and-Power/PlugIn-Adapters/ACT-Homepro-ZRP-200-Schuko-Plugin-Switch.html&lt;br /&gt;
* http://www.zwave4u.com/products/en/Lighting-and-Power/PlugIn-Adapters/ACT-Homepro-ZDP-200-Schuko-Plugin-Dimmer.html&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Sony_KDL-46W4500&amp;diff=18127</id>
		<title>Sony KDL-46W4500</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Sony_KDL-46W4500&amp;diff=18127"/>
		<updated>2009-03-25T13:45:07Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Hardware]]&lt;br /&gt;
[[Category:Video]]&lt;br /&gt;
[[Category:Displays]]&lt;br /&gt;
&lt;br /&gt;
I am using an &#039;&#039;&#039;European&#039;&#039;&#039; version this TV and will try to describe problems I have here.&lt;br /&gt;
&lt;br /&gt;
Connected to a Nvidia 7300GT with an DVI to HDMI cable.&lt;br /&gt;
&lt;br /&gt;
I was not able to get the TV setup to 1080p with 50hz, so I choosed 1080p and 60hz. Then afterwards I changed the xorg.conf and changed/added the folowing lines :&lt;br /&gt;
&lt;br /&gt;
 Option         &amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot;&lt;br /&gt;
 Option         &amp;quot;UseEDID&amp;quot; &amp;quot;true&amp;quot;&lt;br /&gt;
&lt;br /&gt;
 Modes       &amp;quot;1920x1080_50&amp;quot;&lt;br /&gt;
 VertRefresh     49-51&lt;br /&gt;
&lt;br /&gt;
and rebooted. After that I had 50hz.&lt;br /&gt;
&lt;br /&gt;
The line &amp;quot;1920x1080_50&amp;quot; uses the EDID information it gets of the TV and sets things up correctly. In the /var/log/Xorg.0.log you can then see that it chooses the right resolution.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;UseEDIDDpi&amp;quot; &amp;quot;false&amp;quot; is important, otherwise you will get very small unreadable characters.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Alternate solution (I used first).&lt;br /&gt;
&lt;br /&gt;
I was not able to get the TV setup to 1080p with 50hz, so I choosed 1080p and 60hz. Then afterwards I changed the xorg.conf to the right 1080p@50hz Modeline i found in the HDTV list in the MythTV modeline database.&lt;br /&gt;
&lt;br /&gt;
        # 1920x1080 @ 50 Hz (EDID) HSync: 56.25 kHz&lt;br /&gt;
        ModeLine &amp;quot;1920x1080&amp;quot; 148.50 1920 2448 2496 2640 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
&lt;br /&gt;
And changed the VertRefresh to :&lt;br /&gt;
        VertRefresh     49-51&lt;br /&gt;
&lt;br /&gt;
and rebooted. After that I had 50hz.&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Viking&amp;diff=18022</id>
		<title>User:Viking</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Viking&amp;diff=18022"/>
		<updated>2009-03-18T14:22:06Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[category:User Setups]]&lt;br /&gt;
&lt;br /&gt;
This is my system.&lt;br /&gt;
&lt;br /&gt;
1st MD TV :&lt;br /&gt;
* Sony KDL-46W4500 - 1080p resolution UI2 overlay interface&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Core :&lt;br /&gt;
* ASUS M3A-H/HDMI&lt;br /&gt;
* AMD Athlon 64 X2 5050e Sockel-AM2 Box&lt;br /&gt;
* be quiet Straight Power 350W ATX 2.2 &lt;br /&gt;
* Arctic Cooling Freezer 64 Pro PMW&lt;br /&gt;
* 2x DDR2-800 2048MB &lt;br /&gt;
* 2x Arctic Cooling 120x120x25 AF12025 PWM &lt;br /&gt;
* Pioneer DVR-216DBK black&lt;br /&gt;
* Sharkoon Revenge Economy Edition Case - black &lt;br /&gt;
* 3 x 1TB Samsung Spinpoint F1 HD103UI EcoGreen (in RAID5)&lt;br /&gt;
* Longshine LCS-8337TXR (PCI Express)&lt;br /&gt;
* PSU 350W be quiet  E6-350W Straight Power&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
1st MD :&lt;br /&gt;
* NVIDIA 7300GT grafikkort&lt;br /&gt;
* 1xGigabyte GA-MA78GM-S2H&lt;br /&gt;
* AMD Athlon 64 X2 5050e Sockel-AM2 Box&lt;br /&gt;
* be quiet Straight Power 350W ATX 2.2 &lt;br /&gt;
* Arctic Cooling Freezer 64 Pro PMW&lt;br /&gt;
* 2x DDR2-800 2048MB &lt;br /&gt;
* Pioneer DVR-216DBK black&lt;br /&gt;
* 3 x 1TB Samsung Spinpoint F1 HD103UI EcoGreen (in RAID5)&lt;br /&gt;
* Longshine LCS-8337TXR (PCI Express)&lt;br /&gt;
* PSU 350W be quiet  E6-350W Straight Power&lt;br /&gt;
* Silverstone LC17 case&lt;br /&gt;
&lt;br /&gt;
* USB-UIRT (søg i wiki/forum) infrarød sender/modtager&lt;br /&gt;
* Phillips SRM 5100 (Windows MCE remote control) - apparently not 100% compatible&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Network&lt;br /&gt;
* Digitus N-Way Switch 5 Gigabit ports 5x10/100/1000TX &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
TV cards &lt;br /&gt;
* TechnoTrend: S2-3200 (not in use yet, so not 100% sure if it works)&lt;br /&gt;
* 2 old  TechnoTrend DVB-s &lt;br /&gt;
* 1x Hauppauge WinTV Nova-TD  (DVB-T usb stick)&lt;br /&gt;
&lt;br /&gt;
Lightcontrol &lt;br /&gt;
* Tricklestar 200ZW-EU-W&lt;br /&gt;
* Tricklestar 300ZW-EU-W&lt;br /&gt;
&lt;br /&gt;
And a couple of  Z-wave devices to play with ;)&lt;br /&gt;
* Everspring SM103&lt;br /&gt;
* Everspring SP103&lt;br /&gt;
* http://www.zwave4u.com/products/en/Lighting-and-Power/PlugIn-Adapters/ACT-Homepro-ZRP-200-Schuko-Plugin-Switch.html&lt;br /&gt;
* http://www.zwave4u.com/products/en/Lighting-and-Power/PlugIn-Adapters/ACT-Homepro-ZDP-200-Schuko-Plugin-Dimmer.html&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Sony_KDL-46W4500&amp;diff=18006</id>
		<title>Sony KDL-46W4500</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Sony_KDL-46W4500&amp;diff=18006"/>
		<updated>2009-03-16T23:30:13Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Hardware]]&lt;br /&gt;
[[Category:Video]]&lt;br /&gt;
[[Category:Displays]]&lt;br /&gt;
&lt;br /&gt;
I am using an &#039;&#039;&#039;European&#039;&#039;&#039; version this TV and will try to describe problems I have here.&lt;br /&gt;
&lt;br /&gt;
Connected to a Nvidia 7300GT with an DVI to HDMI cable.&lt;br /&gt;
&lt;br /&gt;
I was not able to get the TV setup to 1080p with 50hz, so I choosed 1080p and 60hz. Then afterwards I changed the xorg.conf to the right 1080p@50hz Modeline i found in the HDTV list in the MythTV modeline database.&lt;br /&gt;
&lt;br /&gt;
        # 1920x1080 @ 50 Hz (EDID) HSync: 56.25 kHz&lt;br /&gt;
        ModeLine &amp;quot;1920x1080&amp;quot; 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +HSync +VSync&lt;br /&gt;
&lt;br /&gt;
And changed the VertRefresh to :&lt;br /&gt;
        VertRefresh     49-51&lt;br /&gt;
&lt;br /&gt;
and rebooted. After that I had 50hz.&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Viking&amp;diff=17999</id>
		<title>User:Viking</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Viking&amp;diff=17999"/>
		<updated>2009-03-16T13:08:42Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[category:User Setups]]&lt;br /&gt;
&lt;br /&gt;
This is my system.&lt;br /&gt;
&lt;br /&gt;
1st MD TV :&lt;br /&gt;
* Sony KDL-46W4500 - 1080p resolution UI2 interface&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Core :&lt;br /&gt;
* ASUS M3A-H/HDMI&lt;br /&gt;
* AMD Athlon 64 X2 5050e Sockel-AM2 Box&lt;br /&gt;
* be quiet Straight Power 350W ATX 2.2 &lt;br /&gt;
* Arctic Cooling Freezer 64 Pro PMW&lt;br /&gt;
* 2x DDR2-800 2048MB &lt;br /&gt;
* 2x Arctic Cooling 120x120x25 AF12025 PWM &lt;br /&gt;
* Pioneer DVR-216DBK black&lt;br /&gt;
* Sharkoon Revenge Economy Edition Case - black &lt;br /&gt;
* 3 x 1TB Samsung Spinpoint F1 HD103UI EcoGreen (in RAID5)&lt;br /&gt;
* Longshine LCS-8337TXR (PCI Express)&lt;br /&gt;
* PSU 350W be quiet  E6-350W Straight Power&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
1st MD :&lt;br /&gt;
* NVIDIA 7300GT grafikkort&lt;br /&gt;
* 1xGigabyte GA-MA78GM-S2H&lt;br /&gt;
* AMD Athlon 64 X2 5050e Sockel-AM2 Box&lt;br /&gt;
* be quiet Straight Power 350W ATX 2.2 &lt;br /&gt;
* Arctic Cooling Freezer 64 Pro PMW&lt;br /&gt;
* 2x DDR2-800 2048MB &lt;br /&gt;
* Pioneer DVR-216DBK black&lt;br /&gt;
* 3 x 1TB Samsung Spinpoint F1 HD103UI EcoGreen (in RAID5)&lt;br /&gt;
* Longshine LCS-8337TXR (PCI Express)&lt;br /&gt;
* PSU 350W be quiet  E6-350W Straight Power&lt;br /&gt;
* Silverstone LC17 case&lt;br /&gt;
&lt;br /&gt;
* USB-UIRT (søg i wiki/forum) infrarød sender/modtager&lt;br /&gt;
* Phillips SRM 5100 (Windows MCE remote control) - apparently not 100% compatible&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Network&lt;br /&gt;
* Digitus N-Way Switch 5 Gigabit ports 5x10/100/1000TX &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
TV cards &lt;br /&gt;
* TechnoTrend: S2-3200 (not in use yet, so not 100% sure if it works)&lt;br /&gt;
* 2 old  TechnoTrend DVB-s &lt;br /&gt;
* 1x Hauppauge WinTV Nova-TD  (DVB-T usb stick)&lt;br /&gt;
&lt;br /&gt;
Lightcontrol &lt;br /&gt;
* Tricklestar 200ZW-EU-W&lt;br /&gt;
* Tricklestar 300ZW-EU-W&lt;br /&gt;
&lt;br /&gt;
And a couple of  Z-wave devices to play with ;)&lt;br /&gt;
* Everspring SM103&lt;br /&gt;
* Everspring SP103&lt;br /&gt;
* http://www.zwave4u.com/products/en/Lighting-and-Power/PlugIn-Adapters/ACT-Homepro-ZRP-200-Schuko-Plugin-Switch.html&lt;br /&gt;
* http://www.zwave4u.com/products/en/Lighting-and-Power/PlugIn-Adapters/ACT-Homepro-ZDP-200-Schuko-Plugin-Dimmer.html&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Viking&amp;diff=17998</id>
		<title>User:Viking</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Viking&amp;diff=17998"/>
		<updated>2009-03-16T13:05:41Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[category:User Setups]]&lt;br /&gt;
&lt;br /&gt;
This is my system.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Core :&lt;br /&gt;
* ASUS M3A-H/HDMI&lt;br /&gt;
* AMD Athlon 64 X2 5050e Sockel-AM2 Box&lt;br /&gt;
* be quiet Straight Power 350W ATX 2.2 &lt;br /&gt;
* Arctic Cooling Freezer 64 Pro PMW&lt;br /&gt;
* 2x DDR2-800 2048MB &lt;br /&gt;
* 2x Arctic Cooling 120x120x25 AF12025 PWM &lt;br /&gt;
* Pioneer DVR-216DBK black&lt;br /&gt;
* Sharkoon Revenge Economy Edition Case - black &lt;br /&gt;
* 3 x 1TB Samsung Spinpoint F1 HD103UI EcoGreen (in RAID5)&lt;br /&gt;
* Longshine LCS-8337TXR (PCI Express)&lt;br /&gt;
* PSU 350W be quiet  E6-350W Straight Power&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
MediaDirector&lt;br /&gt;
* NVIDIA 7300GT grafikkort&lt;br /&gt;
* 1xGigabyte GA-MA78GM-S2H&lt;br /&gt;
* AMD Athlon 64 X2 5050e Sockel-AM2 Box&lt;br /&gt;
* be quiet Straight Power 350W ATX 2.2 &lt;br /&gt;
* Arctic Cooling Freezer 64 Pro PMW&lt;br /&gt;
* 2x DDR2-800 2048MB &lt;br /&gt;
* Pioneer DVR-216DBK black&lt;br /&gt;
* 3 x 1TB Samsung Spinpoint F1 HD103UI EcoGreen (in RAID5)&lt;br /&gt;
* Longshine LCS-8337TXR (PCI Express)&lt;br /&gt;
* PSU 350W be quiet  E6-350W Straight Power&lt;br /&gt;
* Silverstone LC17 case&lt;br /&gt;
&lt;br /&gt;
* USB-UIRT (søg i wiki/forum) infrarød sender/modtager&lt;br /&gt;
* Phillips SRM 5100 (Windows MCE remote control) - apparently not 100% compatible&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Network&lt;br /&gt;
* Digitus N-Way Switch 5 Gigabit ports 5x10/100/1000TX &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
TV cards &lt;br /&gt;
* TechnoTrend: S2-3200 (not in use yet, so not 100% sure if it works)&lt;br /&gt;
* 2 old  TechnoTrend DVB-s &lt;br /&gt;
* 1x Hauppauge WinTV Nova-TD  (DVB-T usb stick)&lt;br /&gt;
&lt;br /&gt;
Lightcontrol &lt;br /&gt;
* Tricklestar 200ZW-EU-W&lt;br /&gt;
* Tricklestar 300ZW-EU-W&lt;br /&gt;
&lt;br /&gt;
And a couple of  Z-wave devices to play with ;)&lt;br /&gt;
* Everspring SM103&lt;br /&gt;
* Everspring SP103&lt;br /&gt;
* http://www.zwave4u.com/products/en/Lighting-and-Power/PlugIn-Adapters/ACT-Homepro-ZRP-200-Schuko-Plugin-Switch.html&lt;br /&gt;
* http://www.zwave4u.com/products/en/Lighting-and-Power/PlugIn-Adapters/ACT-Homepro-ZDP-200-Schuko-Plugin-Dimmer.html&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Viking&amp;diff=17997</id>
		<title>User:Viking</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Viking&amp;diff=17997"/>
		<updated>2009-03-16T13:04:53Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[category:User Setups]]&lt;br /&gt;
&lt;br /&gt;
This is my system.&lt;br /&gt;
&lt;br /&gt;
Core :&lt;br /&gt;
* ASUS M3A-H/HDMI&lt;br /&gt;
* AMD Athlon 64 X2 5050e Sockel-AM2 Box&lt;br /&gt;
* be quiet Straight Power 350W ATX 2.2 &lt;br /&gt;
* Arctic Cooling Freezer 64 Pro PMW&lt;br /&gt;
* 2x DDR2-800 2048MB &lt;br /&gt;
* 2x Arctic Cooling 120x120x25 AF12025 PWM &lt;br /&gt;
* Pioneer DVR-216DBK black&lt;br /&gt;
* Sharkoon Revenge Economy Edition Case - black &lt;br /&gt;
* 3 x 1TB Samsung Spinpoint F1 HD103UI EcoGreen (in RAID5)&lt;br /&gt;
* Longshine LCS-8337TXR (PCI Express)&lt;br /&gt;
* PSU 350W be quiet  E6-350W Straight Power&lt;br /&gt;
&lt;br /&gt;
MediaDirector&lt;br /&gt;
* NVIDIA 7300GT grafikkort&lt;br /&gt;
* 1xGigabyte GA-MA78GM-S2H&lt;br /&gt;
* AMD Athlon 64 X2 5050e Sockel-AM2 Box&lt;br /&gt;
* be quiet Straight Power 350W ATX 2.2 &lt;br /&gt;
* Arctic Cooling Freezer 64 Pro PMW&lt;br /&gt;
* 2x DDR2-800 2048MB &lt;br /&gt;
* Pioneer DVR-216DBK black&lt;br /&gt;
* 3 x 1TB Samsung Spinpoint F1 HD103UI EcoGreen (in RAID5)&lt;br /&gt;
* Longshine LCS-8337TXR (PCI Express)&lt;br /&gt;
* PSU 350W be quiet  E6-350W Straight Power&lt;br /&gt;
* Silverstone LC17 case&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* USB-UIRT (søg i wiki/forum) infrarød sender/modtager&lt;br /&gt;
* Phillips SRM 5100 (Windows MCE remote control) - apparently not 100% compatible&lt;br /&gt;
&lt;br /&gt;
* Digitus N-Way Switch 5 Gigabit ports 5x10/100/1000TX &lt;br /&gt;
&lt;br /&gt;
TV cards &lt;br /&gt;
* TechnoTrend: S2-3200 (not in use yet, so not 100% sure if it works)&lt;br /&gt;
* 2 old  TechnoTrend DVB-s &lt;br /&gt;
* 1x Hauppauge WinTV Nova-TD  (DVB-T usb stick)&lt;br /&gt;
&lt;br /&gt;
Lightcontrol &lt;br /&gt;
* Tricklestar 200ZW-EU-W&lt;br /&gt;
* Tricklestar 300ZW-EU-W&lt;br /&gt;
&lt;br /&gt;
And a couple of  Z-wave devices to play with ;)&lt;br /&gt;
* Everspring SM103&lt;br /&gt;
* Everspring SP103&lt;br /&gt;
* http://www.zwave4u.com/products/en/Lighting-and-Power/PlugIn-Adapters/ACT-Homepro-ZRP-200-Schuko-Plugin-Switch.html&lt;br /&gt;
* http://www.zwave4u.com/products/en/Lighting-and-Power/PlugIn-Adapters/ACT-Homepro-ZDP-200-Schuko-Plugin-Dimmer.html&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Viking&amp;diff=17996</id>
		<title>User:Viking</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Viking&amp;diff=17996"/>
		<updated>2009-03-16T13:02:30Z</updated>

		<summary type="html">&lt;p&gt;Viking: New page: This is my system.  Core : ASUS M3A-H/HDMI AMD Athlon 64 X2 5050e Sockel-AM2 Box be quiet Straight Power 350W ATX 2.2  Arctic Cooling Freezer 64 Pro PMW 2x DDR2-800 2048MB  2x Arctic Cooli...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This is my system.&lt;br /&gt;
&lt;br /&gt;
Core :&lt;br /&gt;
ASUS M3A-H/HDMI&lt;br /&gt;
AMD Athlon 64 X2 5050e Sockel-AM2 Box&lt;br /&gt;
be quiet Straight Power 350W ATX 2.2 &lt;br /&gt;
Arctic Cooling Freezer 64 Pro PMW&lt;br /&gt;
2x DDR2-800 2048MB &lt;br /&gt;
2x Arctic Cooling 120x120x25 AF12025 PWM &lt;br /&gt;
Pioneer DVR-216DBK black&lt;br /&gt;
Sharkoon Revenge Economy Edition Case - black &lt;br /&gt;
3 x 1TB Samsung Spinpoint F1 HD103UI EcoGreen (in RAID5)&lt;br /&gt;
Longshine LCS-8337TXR (PCI Express)&lt;br /&gt;
PSU 350W be quiet  E6-350W Straight Power&lt;br /&gt;
&lt;br /&gt;
MediaDirector&lt;br /&gt;
NVIDIA 7300GT grafikkort&lt;br /&gt;
1xGigabyte GA-MA78GM-S2H&lt;br /&gt;
AMD Athlon 64 X2 5050e Sockel-AM2 Box&lt;br /&gt;
be quiet Straight Power 350W ATX 2.2 &lt;br /&gt;
Arctic Cooling Freezer 64 Pro PMW&lt;br /&gt;
2x DDR2-800 2048MB &lt;br /&gt;
2x Arctic Cooling 120x120x25 AF12025 PWM &lt;br /&gt;
Pioneer DVR-216DBK black&lt;br /&gt;
3 x 1TB Samsung Spinpoint F1 HD103UI EcoGreen (in RAID5)&lt;br /&gt;
Longshine LCS-8337TXR (PCI Express)&lt;br /&gt;
PSU 350W be quiet  E6-350W Straight Power&lt;br /&gt;
Silverstone LC17 case&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
USB-UIRT (søg i wiki/forum) infrarød sender/modtager&lt;br /&gt;
Phillips SRM 5100 (Windows MCE remote control) - apparently not 100% compatible&lt;br /&gt;
&lt;br /&gt;
Digitus N-Way Switch 5 Gigabit ports 5x10/100/1000TX &lt;br /&gt;
&lt;br /&gt;
TV cards &lt;br /&gt;
TechnoTrend: S2-3200 (not in use yet, so not 100% sure if it works)&lt;br /&gt;
2 old  TechnoTrend DVB-s &lt;br /&gt;
1x Hauppauge WinTV Nova-TD  (DVB-T usb stick)&lt;br /&gt;
&lt;br /&gt;
Lightcontrol &lt;br /&gt;
Tricklestar 200ZW-EU-W&lt;br /&gt;
Tricklestar 300ZW-EU-W&lt;br /&gt;
&lt;br /&gt;
And a couple of  Z-wave devices to play with ;)&lt;br /&gt;
Everspring SM103&lt;br /&gt;
Everspring SP103&lt;br /&gt;
http://www.zwave4u.com/products/en/Lighting-and-Power/PlugIn-Adapters/ACT-Homepro-ZRP-200-Schuko-Plugin-Switch.html&lt;br /&gt;
http://www.zwave4u.com/products/en/Lighting-and-Power/PlugIn-Adapters/ACT-Homepro-ZDP-200-Schuko-Plugin-Dimmer.html&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Sony_KDL-46W4500&amp;diff=17995</id>
		<title>Sony KDL-46W4500</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Sony_KDL-46W4500&amp;diff=17995"/>
		<updated>2009-03-16T12:44:34Z</updated>

		<summary type="html">&lt;p&gt;Viking: New page: Category:Hardware Category:Video Category:Displays  I am using an &amp;#039;&amp;#039;&amp;#039;European&amp;#039;&amp;#039;&amp;#039; version this TV and will try to describe problems I have here.  Connected to a Nvidia 7300GT wi...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Hardware]]&lt;br /&gt;
[[Category:Video]]&lt;br /&gt;
[[Category:Displays]]&lt;br /&gt;
&lt;br /&gt;
I am using an &#039;&#039;&#039;European&#039;&#039;&#039; version this TV and will try to describe problems I have here.&lt;br /&gt;
&lt;br /&gt;
Connected to a Nvidia 7300GT with an DVI to HDMI cable.&lt;br /&gt;
&lt;br /&gt;
I was not able to get the TV setup to 1080p with 50hz, so I choosed 1080p and 60hz. Then afterwards I changed the xorg.conf to the right 1080p@50hz Modeline i found in the HDTV list in the MythTV modeline database.&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=VDR&amp;diff=17965</id>
		<title>VDR</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=VDR&amp;diff=17965"/>
		<updated>2009-03-13T23:03:41Z</updated>

		<summary type="html">&lt;p&gt;Viking: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| align=&amp;quot;right&amp;quot;&lt;br /&gt;
  | __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
[[Category:Software components]]&lt;br /&gt;
[[Category:Video]]&lt;br /&gt;
[[Category:Tutorials]]&lt;br /&gt;
= The Video Disk Recorder =&lt;br /&gt;
VDR is a [[personal video recorder]] system aimed at the DVB market. It supports DVB-S, DVB-C and DVB-T tuner cards. More details can be found at the [http://www.cadsoftusa.com/vdr/ VDR homepage].&lt;br /&gt;
&lt;br /&gt;
It is the second PVR system integrated into LinuxMCE. The main aim is for a seamless integration into LinuxMCE. The UI should not change between VDR and the other LinuxMCE pieces. The first version of this integration wass scheduled for January 2008, and is mainly sponsored by [http://www.dianemo.co.uk Convergent Home Technologies Ltd].&lt;br /&gt;
&lt;br /&gt;
== Configuration ==&lt;br /&gt;
&lt;br /&gt;
Recently I managed to setup VDR under LinuxMCE successfully. This brief howto is a result of my personal experience. Don&#039;t hesitate to improve it. &lt;br /&gt;
&lt;br /&gt;
===Installation===&lt;br /&gt;
&lt;br /&gt;
VDR can be chosen by two ways. The first one is initial configuration after installation. During setup the media center property you should choose VDR and not MythTV. The second way is to tick VDR and tick off MythTV on the &amp;lt;strong&amp;gt;Software modules&amp;lt;/strong&amp;gt; page - &amp;lt;em&amp;gt;Wizard --&amp;amp;gt; Media Directors&amp;lt;/em&amp;gt;. In both cases VDR will be installed automatically and will start after installation.&lt;br /&gt;
&lt;br /&gt;
[[Image:LMCE-software-modules.jpg|thumb|550px|left|LinuxMCE Software Modules]]&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both;&amp;quot;/&amp;gt; &lt;br /&gt;
To make VDR configuration and manage easier its web interface - VDRAdmin can be used. It should be installed manually:&lt;br /&gt;
&lt;br /&gt;
    sudo apt-get install vdradmin-am&lt;br /&gt;
&lt;br /&gt;
and then enabled to be able run by replacing ENABLED=&amp;quot;0&amp;quot; by ENABLED=&amp;quot;1&amp;quot; in the &amp;lt;em&amp;gt;/etc/default/vdradmin-am&amp;lt;/em&amp;gt;. Also don&#039;t forget to add a new firewall rule for the port 8001 - &amp;lt;em&amp;gt;Advanced --&amp;gt;&amp;amp;gt; Network --&amp;amp;gt; Firewall Rules&amp;lt;/em&amp;gt;. &lt;br /&gt;
&lt;br /&gt;
=== Scanning for Channels ===&lt;br /&gt;
&lt;br /&gt;
To enable scanning for channels the DVB utilities package should also installed manually:&lt;br /&gt;
&lt;br /&gt;
    sudo apt-get update&lt;br /&gt;
&lt;br /&gt;
then do&lt;br /&gt;
&lt;br /&gt;
    sudo apt-get install dvb-utils&lt;br /&gt;
&lt;br /&gt;
==== Scanning for DVB-T Channels ====&lt;br /&gt;
&lt;br /&gt;
Firstly we need to stop VDR before we scan for channels;&lt;br /&gt;
&lt;br /&gt;
    sudo /etc/init.d/vdr stop&lt;br /&gt;
&lt;br /&gt;
Above we installed the dvb-utils package and this will have installed the scan utility and tuning files for many DVB transmitters in various regions. Look for a transmitter in your region by looking in the following directory;&lt;br /&gt;
&lt;br /&gt;
  ls /usr/share/doc/dvb-utils/examples/scan/dvb-t&lt;br /&gt;
&lt;br /&gt;
You should now see something like this on your console;&lt;br /&gt;
&lt;br /&gt;
 au-Adelaide            fi-Ahtari          fi-Taivalkoski       se-Borlange                  se-Uddevalla&lt;br /&gt;
 au-Brisbane            fi-Ala-Vuokki      fi-Tammela           se-Emmaboda                  se-Uppsala&lt;br /&gt;
 au-canberra            fi-Ammansaari      fi-Tampere           se-Falun                     se-Vannas&lt;br /&gt;
 au-Darwin              fi-Anjalankoski    fi-Tervola           se-Gallivare                 se-Varberg&lt;br /&gt;
 au-GoldCoast           fi-Espoo           fi-Turku             se-Gavle                     se-Vasteras&lt;br /&gt;
 au-Hobart              fi-Eurajoki        fi-Utsjoki           se-Goteborg_Brudaremossen    se-Vastervik&lt;br /&gt;
 au-Mackay              fi-Fiskars         fi-Vaasa             se-Goteborg_Slattadamm       se-Visby&lt;br /&gt;
 au-Melbourne           fi-Haapavesi       fi-Vuokatti          se-Halmstad                  se-Vislanda&lt;br /&gt;
 au-Melbourne-Upwey     fi-Hetta           fi-Vuotso            se-Harnosand                 se-Ystad&lt;br /&gt;
 au-Perth               fi-Iisalmi         fi-Yllas             se-Helsingborg               tw-Taipei&lt;br /&gt;
 au-Sydney_Kings_Cross  fi-Inari           fr-Bordeaux          se-Horby                     uk-Angus&lt;br /&gt;
 au-sydney_north_shore  fi-Joutseno        fr-Brest             se-Hudiksvall                uk-Bilsdale&lt;br /&gt;
 au-Townsville          fi-Juntusranta     fr-LeMans            se-Jonkoping                 uk-BlackHill&lt;br /&gt;
 au-unknown             fi-Jyvaskyla       fr-Lyon-Fourviere    se-Kalix                     uk-BluebellHill&lt;br /&gt;
 cz-Praha               fi-Kaihuanvaara    fr-Lyon-Pilat        se-Karlshamn                 uk-Caradon&lt;br /&gt;
 de-Berlin              fi-Karigasniemi    fr-Marseille         se-Karlskrona                uk-CaradonHill&lt;br /&gt;
 de-Braunschweig        fi-Kaunispaa       fr-Nantes            se-Karlstad                  uk-Craigkelly&lt;br /&gt;
 de-Bremen              fi-Kerimaki        fr-Niort             se-Kiruna                    uk-CrystalPalace&lt;br /&gt;
 de-Erfurt-Weimar       fi-Kiihtelysvaara  fr-Orleans           se-Kisa                      uk-Dover&lt;br /&gt;
 de-Frankfurt           fi-Kilpisjarvi     fr-Paris             se-Kramfors                  uk-DoverB&lt;br /&gt;
 de-Hamburg             fi-Koli            fr-Rennes            se-Linkoping_Vattentorn      uk-Durris&lt;br /&gt;
 de-Hannover            fi-Kruunupyy       fr-Rouen             se-Malmo                     uk-EmleyMoor&lt;br /&gt;
 de-Kiel                fi-Kuopio          fr-Toulouse          se-Malmo_Kronprinsen         uk-Hannington&lt;br /&gt;
 de-Koeln-Bonn          fi-Kuttanen        fr-Vannes            se-Molndal_Vasterberget      uk-Heathfield&lt;br /&gt;
 de-Leipzig             fi-Lahti           hr-Zagreb            se-Mora                      uk-Llanddona&lt;br /&gt;
 de-Luebeck             fi-Lapua           is-Reykjavik         se-Motala                    uk-Mendip&lt;br /&gt;
 de-Muenchen            fi-Mikkeli         it-Bologna           se-Nassjo                    uk-Oxford&lt;br /&gt;
 de-Nuernberg           fi-Oulu            it-Bolzano           se-Norrkoping                uk-PontopPike&lt;br /&gt;
 de-Rostock             fi-Pello           it-Catania           se-Norrtalje_Sodra_Bergen    uk-Redruth&lt;br /&gt;
 de-Ruhrgebiet          fi-Pernaja         it-Conero            se-Orebro                    uk-Reigate&lt;br /&gt;
 de-Schwerin            fi-Pihtipudas      it-Genova            se-Ornskoldsvik              uk-Rowridge&lt;br /&gt;
 dk-Copenhagen          fi-Posio           it-Milano            se-Ostersund                 uk-SandyHeath&lt;br /&gt;
 es-Alfabia             fi-Pudasjarvi      it-Torino            se-Osthammar                 uk-Storeton&lt;br /&gt;
 es-Alpicat             fi-Puolanka        it-Varese            se-Skelleftea                uk-SudburyB&lt;br /&gt;
 es-Collserola          fi-Pyhatunturi     nl-AlphenaandenRijn  se-Skovde                    uk-SuttonColdfield&lt;br /&gt;
 es-Lugo                fi-Pyhavuori       nl-Randstad          se-Sodertalje_Ragnhildsborg  uk-TheWrekin&lt;br /&gt;
 es-Madrid              fi-Ranua           se-Alvsbyn           se-Stockholm_Marieberg       uk-TheWrekinB&lt;br /&gt;
 es-Mussara             fi-Rovaniemi       se-Angelholm         se-Stockholm_Nacka           uk-Waltham&lt;br /&gt;
 es-Rocacorba           fi-Ruka            se-Bollnas           se-Sundsvall                 uk-WhitehawkHill&lt;br /&gt;
 es-Sevilla             fi-Salla           se-Boras             se-Trollhattan               uk-WinterHill&lt;br /&gt;
&lt;br /&gt;
Once you have found the DVB-T transmitter for your region then use the line below to generate the VDR compatible channels.conf for that specific transmitter using the line below substituting &#039;uk-CrystalPalace&#039; with the name of your closest transmitter;&lt;br /&gt;
&lt;br /&gt;
 cd /home&lt;br /&gt;
 sudo scan -o vdr -p -u /usr/share/doc/dvb-utils/examples/scan/dvb-t/uk-CrystalPalace &amp;gt; channels.conf&lt;br /&gt;
&lt;br /&gt;
This will write the channels.conf file and also output data on all the found and tuned channels to the console. The scan process usually takes less than a minute but can take longer if you have a low quality signal in your area. Below is an example of the output for &#039;uk-CrystalPalace&#039; my local transmitter here in the UK showing the channels broadcast on all 6 MUX&#039;s;&lt;br /&gt;
&lt;br /&gt;
 scanning /usr/share/doc/dvb-utils/examples/scan/dvb-t/uk-CrystalPalace&lt;br /&gt;
 using &#039;/dev/dvb/adapter0/frontend0&#039; and &#039;/dev/dvb/adapter0/demux0&#039;&lt;br /&gt;
 initial transponder 505833333 0 3 9 1 0 0 0&lt;br /&gt;
 &amp;gt;&amp;gt;&amp;gt; tune to: 505833:I999B8C34D999M16T2G32Y0:T:27500:&lt;br /&gt;
 0x0000 0x1044: pmt_pid 0x1044 BBC -- BBC ONE (running)&lt;br /&gt;
 0x0000 0x1084: pmt_pid 0x1084 BBC -- BBC TWO (running)&lt;br /&gt;
 0x0000 0x10ff: pmt_pid 0x10ff BBC -- BBC THREE (running)&lt;br /&gt;
 0x0000 0x113f: pmt_pid 0x113f BBC -- BBC NEWS 24 (running)&lt;br /&gt;
 0x0000 0x117f: pmt_pid 0x117f BBC -- BBCi (running)&lt;br /&gt;
 0x0000 0x123f: pmt_pid 0x123f BBC -- CBBC Channel (running)&lt;br /&gt;
 Network Name &#039;Crystal Palace&#039;&lt;br /&gt;
 &amp;gt;&amp;gt;&amp;gt; tune to: 481833:I999B8C23D12M64T2G32Y0:T:27500:&lt;br /&gt;
 Network Name &#039;Crystal Palace&#039;&lt;br /&gt;
 0x2005 0x2045: pmt_pid 0x0100 ITV -- ITV1 (running)&lt;br /&gt;
 0x2005 0x2066: pmt_pid 0x0104 ITV -- ITV3 (running)&lt;br /&gt;
 0x2005 0x2085: pmt_pid 0x0102 ITV -- ITV2 (running)&lt;br /&gt;
 0x2005 0x20a1: pmt_pid 0x0116 ITV -- ITV4 (running)&lt;br /&gt;
 0x2005 0x20c0: pmt_pid 0x0108 Channel 4 TV -- Channel 4 (running)&lt;br /&gt;
 0x2005 0x20fa: pmt_pid 0x010e Channel 4 TV -- More 4 (running)&lt;br /&gt;
 0x2005 0x2100: pmt_pid 0x010b Channel 4 TV -- E4 (running)&lt;br /&gt;
 0x2005 0x2104: pmt_pid 0x010c Channel 4 TV -- Channel 4+1 (running)&lt;br /&gt;
 0x2005 0x2145: pmt_pid 0x0110 Teletext Limited -- Teletext (running)&lt;br /&gt;
 0x2005 0x21c3: pmt_pid 0x0112 Teletext Limited -- Teletext Cars (running)&lt;br /&gt;
 0x2005 0x2240: pmt_pid 0x0114 Channel 4 TV -- Teletext on 4 (running)&lt;br /&gt;
 0x2005 0x2244: pmt_pid 0x011c Global Radio -- Heart (running)&lt;br /&gt;
 &amp;gt;&amp;gt;&amp;gt; tune to: 561833:I999B8C23D12M64T2G32Y0:T:27500:&lt;br /&gt;
 0x3002 0x3242: pmt_pid 0x0101 five -- Five (running)&lt;br /&gt;
 0x3002 0x3280: pmt_pid 0x0113 five -- Five Life (running)&lt;br /&gt;
 0x3002 0x32c0: pmt_pid 0x0117 five -- Five US (running)&lt;br /&gt;
 0x3002 0x3340: pmt_pid 0x0103 QVC -- QVC (running)&lt;br /&gt;
 0x3002 0x37c0: pmt_pid 0x0105 Sit-Up Ltd -- bid tv (running)&lt;br /&gt;
 0x3002 0x3900: pmt_pid 0x010a EMAP -- Smash Hits! (running)&lt;br /&gt;
 0x3002 0x3940: pmt_pid 0x010b EMAP -- MOJO (running)&lt;br /&gt;
 0x3002 0x39c0: pmt_pid 0x010c Teletext Limited -- Ttext Holidays (running)&lt;br /&gt;
 0x3002 0x3a80: pmt_pid 0x010e five -- UKTV Style (running, scrambled)&lt;br /&gt;
 0x3002 0x3b80: pmt_pid 0x0112 five -- TVX / RED HOT (running)&lt;br /&gt;
 0x3002 0x3cc0: pmt_pid 0x0114 five -- UKTV Gold (running, scrambled)&lt;br /&gt;
 0x3002 0x3d00: pmt_pid 0x0115 Sit-Up Ltd -- price-drop tv (running)&lt;br /&gt;
 0x3002 0x3dc0: pmt_pid 0x0118 five -- Teachers TV (running)&lt;br /&gt;
 0x3002 0x3e20: pmt_pid 0x0124 Turner Broadcasting System Europe Limited -- Nuts TV (running)&lt;br /&gt;
 0x3002 0x3e80: pmt_pid 0x011d five -- Eurosport UK (running, scrambled)&lt;br /&gt;
 0x3002 0x3ea0: pmt_pid 0x0104 ITV -- CITV (running)&lt;br /&gt;
 0x3002 0x3ee0: pmt_pid 0x011c ITV -- SETANTA SPORTS (running)&lt;br /&gt;
 0x3002 0x3f00: pmt_pid 0x011b Teletext Limited -- Teletext Games (running)&lt;br /&gt;
 0x3002 0x3f20: pmt_pid 0x0125 The Jewellery Channel -- Jewellery Chan (running)&lt;br /&gt;
 0x3002 0x3f60: pmt_pid 0x0120 TopUp TV Ltd -- TopUp Anytime1 (running, scrambled)&lt;br /&gt;
 0x3002 0x3f80: pmt_pid 0x0121 TopUp TV Ltd -- TopUp Anytime2 (running, scrambled)&lt;br /&gt;
 0x3002 0x3fa0: pmt_pid 0x0122 TopUp TV Ltd -- TopUp Anytime3 (running, scrambled)&lt;br /&gt;
 WARNING: filter timeout pid 0x0010&lt;br /&gt;
 &amp;gt;&amp;gt;&amp;gt; tune to: 529833:I999B8C34D34M16T2G32Y0:T:27500:&lt;br /&gt;
 0x4000 0x4280: pmt_pid 0x02ca BBC -- BBC Parliament (running)&lt;br /&gt;
 0x4000 0x41c0: pmt_pid 0x02be BBC -- BBC FOUR (running)&lt;br /&gt;
 0x4000 0x4240: pmt_pid 0x02bf BBC -- CBeebies (running)&lt;br /&gt;
 0x4000 0x4600: pmt_pid 0x02c0 BBC -- BBC R5 Live (running)&lt;br /&gt;
 0x4000 0x4640: pmt_pid 0x02c1 BBC -- BBC 5L SportsX (running)&lt;br /&gt;
 0x4000 0x4680: pmt_pid 0x02c2 BBC -- BBC 6 Music (running)&lt;br /&gt;
 0x4000 0x46c0: pmt_pid 0x02c3 BBC -- BBC 7 (running)&lt;br /&gt;
 0x4000 0x4700: pmt_pid 0x02c4 BBC -- 1Xtra BBC (running)&lt;br /&gt;
 0x4000 0x4740: pmt_pid 0x02c5 BBC -- BBC Asian Net. (running)&lt;br /&gt;
 0x4000 0x4c00: pmt_pid 0x02c6 BBC -- 301 (running)&lt;br /&gt;
 0x4000 0x4c40: pmt_pid 0x02c7 BBC -- 302 (running)&lt;br /&gt;
 0x4000 0x4c80: pmt_pid 0x02c8 BBC -- 303 (running)&lt;br /&gt;
 0x4000 0x4180: pmt_pid 0x02bd BBC -- 305 (running)&lt;br /&gt;
 0x4000 0x4e00: pmt_pid 0x02c9 BBC -- Community (running)&lt;br /&gt;
 0x4000 0x4840: pmt_pid 0x02cb BBC -- BBC Radio 1 (running)&lt;br /&gt;
 0x4000 0x4880: pmt_pid 0x02cc BBC -- BBC Radio 2 (running)&lt;br /&gt;
 0x4000 0x48c0: pmt_pid 0x02cd BBC -- BBC Radio 3 (running)&lt;br /&gt;
 0x4000 0x4900: pmt_pid 0x02ce BBC -- BBC Radio 4 (running)&lt;br /&gt;
 Network Name &#039;Crystal Palace&#039;&lt;br /&gt;
 &amp;gt;&amp;gt;&amp;gt; tune to: 578166:I999B8C34D34M16T2G32Y0:T:27500:&lt;br /&gt;
 0x5000 0x5740: pmt_pid 0x02c1 Channel 4 TV -- E4+1 (running)&lt;br /&gt;
 0x5000 0x5640: pmt_pid 0x02bd Sky -- Sky News (running)&lt;br /&gt;
 0x5000 0x5680: pmt_pid 0x02be Sky -- Sky Spts News (running)&lt;br /&gt;
 0x5000 0x56c0: pmt_pid 0x02bf Sky -- SKY THREE (running)&lt;br /&gt;
 0x5000 0x5840: pmt_pid 0x02c2 talkSPORT -- talkSPORT (running)&lt;br /&gt;
 0x5000 0x5c80: pmt_pid 0x02cd Sky -- Sky Text (running)&lt;br /&gt;
 0x5000 0x5a40: pmt_pid 0x02ca Virgin Radio -- Virgin Radio (running)&lt;br /&gt;
 0x5000 0x5cc0: pmt_pid 0x02cf yoomedia -- tvtv DIGITAL (running)&lt;br /&gt;
 0x5000 0x5700: pmt_pid 0x02c0 UKTV -- Dave (running)&lt;br /&gt;
 0x5000 0x5780: pmt_pid 0x02cc Square1 Management Ltd -- smileTV (running)&lt;br /&gt;
 0x5000 0x59c0: pmt_pid 0x02c8 London Christian Radio Ltd -- Premier Radio (running)&lt;br /&gt;
 0x5000 0x5a00: pmt_pid 0x02c9 Score Digital -- Clyde 1 (running)&lt;br /&gt;
 Network Name &#039;Crystal Palace&#039;&lt;br /&gt;
 &amp;gt;&amp;gt;&amp;gt; tune to: 537833:I999B8C34D34M16T2G32Y0:T:27500:&lt;br /&gt;
 0x6000 0x6440: pmt_pid 0x03e9 EMAP -- The HITS (running)&lt;br /&gt;
 0x6000 0x6480: pmt_pid 0x03ea MTV Europe -- TMF (running)&lt;br /&gt;
 0x6000 0x64c0: pmt_pid 0x03eb UKTV -- UKTV History (running)&lt;br /&gt;
 0x6000 0x6500: pmt_pid 0x03ec Flextech -- Virgin1 (running)&lt;br /&gt;
 0x6000 0x6540: pmt_pid 0x03ed CCI -- Ideal World (running)&lt;br /&gt;
 0x6000 0x6640: pmt_pid 0x03fd EMAP -- Kiss (running)&lt;br /&gt;
 0x6000 0x66c0: pmt_pid 0x03ff EMAP -- Kerrang! (running)&lt;br /&gt;
 0x6000 0x6700: pmt_pid 0x0400 GMG -- SMOOTH RADIO (running)&lt;br /&gt;
 0x6000 0x67c0: pmt_pid 0x0403 EMAP -- The Hits Radio (running)&lt;br /&gt;
 0x6000 0x6800: pmt_pid 0x0404 EMAP -- Magic (running)&lt;br /&gt;
 0x6000 0x6840: pmt_pid 0x0405 EMAP -- Q (running)&lt;br /&gt;
 0x6000 0x6980: pmt_pid 0x0407 4TV Ltd -- 4TVinteractive (running)&lt;br /&gt;
 0x6000 0x69c0: pmt_pid 0x03ee ITV -- ITV2 +1 (running)&lt;br /&gt;
 0x6000 0x6a00: pmt_pid 0x03f0 Channel 4 TV -- Film4 (running)&lt;br /&gt;
 0x6000 0x6780: pmt_pid 0x0402 BBC -- BBC World Sv. (running)&lt;br /&gt;
 0x6000 0x6680: pmt_pid 0x03fe EMAP -- heat (running)&lt;br /&gt;
 0x6000 0x6a40: pmt_pid 0x03f1 Channel 4 -- Gems TV (running)&lt;br /&gt;
 0x6000 0x6a80: pmt_pid 0x03f2 Camelot Group plc -- Lottery Xtra (running)&lt;br /&gt;
 Network Name &#039;Crystal Palace&#039;&lt;br /&gt;
 dumping lists (90 services)&lt;br /&gt;
 Done.&lt;br /&gt;
&lt;br /&gt;
Below is an example of the first few lines of the &#039;channels.conf&#039; that was produced by the example above. Notice that the channels are grouped by MUX and not by their UK LCN (Logical Channel Number) which are the numbers with the &#039;@&#039; in front on alternate lines. &lt;br /&gt;
&lt;br /&gt;
 :@1&lt;br /&gt;
 BBC - BBC ONE:505833:I999B8C34D34M16T2G32Y0:T:27500:600:601,602:0:0:4164:0:0:0&lt;br /&gt;
 :@2&lt;br /&gt;
 BBC - BBC TWO:505833:I999B8C34D34M16T2G32Y0:T:27500:610:611,612:0:0:4228:0:0:0&lt;br /&gt;
 :@80&lt;br /&gt;
 BBC - BBC NEWS 24:505833:I999B8C34D34M16T2G32Y0:T:27500:640:641:0:0:4415:0:0:0&lt;br /&gt;
 :@70&lt;br /&gt;
 BBC - CBBC Channel:505833:I999B8C34D34M16T2G32Y0:T:27500:620:621,622:0:0:4671:0:0:0&lt;br /&gt;
 :@3&lt;br /&gt;
 ITV - ITV1:481833:I999B8C23D12M64T2G32Y0:T:27500:520:521,522:0:0:8261:0:0:0&lt;br /&gt;
 :@6&lt;br /&gt;
 ITV - ITV2:481833:I999B8C23D12M64T2G32Y0:T:27500:530:531,532:0:0:8325:0:0:0&lt;br /&gt;
 :@10&lt;br /&gt;
 ITV - ITV3:481833:I999B8C23D12M64T2G32Y0:T:27500:540:541,542:0:0:8294:0:0:0&lt;br /&gt;
 :@102&lt;br /&gt;
 Teletext Limited - Teletext Cars:481833:I999B8C23D12M64T2G32Y0:T:27500:0:789:0:0:8643:0:0:0&lt;br /&gt;
 :@4&lt;br /&gt;
 Channel 4 TV - Channel 4:481833:I999B8C23D12M64T2G32Y0:T:27500:560+8190:561,562:0:0:8384:0:0:0&lt;br /&gt;
 :@13&lt;br /&gt;
 Channel 4 TV - Channel 4+1:481833:I999B8C23D12M64T2G32Y0:T:27500:580+8190:581,582:0:0:8452:0:0:0&lt;br /&gt;
 :@29&lt;br /&gt;
 Channel 4 TV - E4:481833:I999B8C23D12M64T2G32Y0:T:27500:570+8190:571,572:0:0:8448:0:0:0&lt;br /&gt;
 :@14&lt;br /&gt;
 Channel 4 TV - More 4:481833:I999B8C23D12M64T2G32Y0:T:27500:590+8190:591,592:0:0:8442:0:0:0&lt;br /&gt;
 :@28&lt;br /&gt;
 ITV - ITV4:481833:I999B8C23D12M64T2G32Y0:T:27500:600:601:0:0:8353:0:0:0&lt;br /&gt;
 (null) - [2243]:481833:I999B8C23D12M64T2G32Y0:T:27500:0:621:0:0:8771:0:0:0&lt;br /&gt;
 :@728&lt;br /&gt;
 Global Radio - Heart:481833:I999B8C23D12M64T2G32Y0:T:27500:0:631:0:0:8772:0:0:0&lt;br /&gt;
&lt;br /&gt;
VDR will load the channels into the EPG in the order that they are listed in the &#039;channels.conf&#039;. So for example in the UK you might want to &#039;sort&#039; the lines in the &#039;channels.conf&#039; based on their LCN before loading them into VDR... although the &#039;channels.conf&#039; will work fine without this.  Here is a command which will create a new &#039;channels-sorted.conf&#039; file from the original, sorted by LCN:&lt;br /&gt;
&lt;br /&gt;
  perl -0777ne &#039;print for sort{($a=~/^:@(\d+)/)[0]&amp;lt;=&amp;gt;($b=~/^:@(\d+)/)[0]}split/(?=^:@)/m&#039; channels.conf &amp;gt; channels-sorted.conf&lt;br /&gt;
  mv channels-sorted.conf channels.conf&lt;br /&gt;
&lt;br /&gt;
Now that you have a good &#039;channels.conf&#039; for your local DVB-T transmitter you need to load it into VDR. So just upload the new &#039;channels.conf&#039; file using LinuxMCE&#039;s Web Admin site - go to Advanced –&amp;gt; Configuration –&amp;gt; VDR and use the &#039;Browse&#039; button next to &#039;Upload custom file&#039; to find where you created your &#039;channels.conf&#039; file and click &#039;Upload&#039;. Now restart vdr from the console;&lt;br /&gt;
 sudo /etc/init.d/vdr restart&lt;br /&gt;
Now use the following command to check that vdr is running;&lt;br /&gt;
 /etc/init.d/vdr status&lt;br /&gt;
You should see the line below;&lt;br /&gt;
 Getting status of Linux Video Disk Recorder   -= LMCE VERSION 0710-10 =- : vdr - is running.&lt;br /&gt;
Now the acid test...go to your LinuxMCE Orbiter and select &#039;TV&#039; from the &#039;Media&#039; menu to see a live picture and your all done.&lt;br /&gt;
==== Scanning for DVB-S Channels ====&lt;br /&gt;
&amp;lt;strong&amp;gt;Configuration&amp;lt;/strong&amp;gt;&lt;br /&gt;
To configure VDR we should get the list of all available channels for desire satellite. You can find it somewhere or create using DVB utility &amp;lt;strong&amp;gt;scan&amp;lt;/strong&amp;gt;. To do that we need the list of transponders stored as INI file. Get it from the [http://joshyfun.peque.org/transponders/index.html JoshyFun&#039;s site]. Store it somewhere on your LinuxMCE core. In my case I use the INI file for [http://joshyfun.peque.org/transponders/0130.ini Hotbird]. &lt;br /&gt;
&lt;br /&gt;
Before scanning stop VDR:&lt;br /&gt;
    sudo /etc/init.d/vdr stop&lt;br /&gt;
and start scanning procedure:&lt;br /&gt;
    scan -o vdr -p -x 0 0130.ini &amp;gt; channels.conf&lt;br /&gt;
It might take about 10-20 minutes depends on the number of available channels on your satellite. When scanning is finished just upload the created channels.conf file via Admin site - &amp;lt;em&amp;gt;Advanced --&amp;amp;gt; Configuration --&amp;amp;gt; VDR&amp;lt;/em&amp;gt;. And then pickup your satellite from the list (see picture above).&lt;br /&gt;
[[Image:LMCE-VDR-config.jpg|thumb|550px|left|LinuxMCE VDR Configuration Screen]]&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both;&amp;quot;/&amp;gt; &lt;br /&gt;
Quick reload router (most probably is not needed) and press button &amp;lt;strong&amp;gt;TV&amp;lt;/strong&amp;gt; on the on-screen Orbiter. You should be able to watch live TV. To navigate on that screen use F6, F7 and F8 buttons on your keyboard, Gyration mouse or Fiire remote. Additionally you can switch channels, see EPG and schedule recording from VDRAdmin web interface. &lt;br /&gt;
===Enable Dolby Digital Audio in xinelibout===&lt;br /&gt;
&lt;br /&gt;
 sudo -s&lt;br /&gt;
 ssh moonXX (where XX is the number of your MD)&lt;br /&gt;
Then start alsamixer on the commandline and press the right arrow on the keyboard until you get till &amp;quot;IEC958&amp;quot;. If this is muted (says MM) then press the &amp;quot;m&amp;quot; button on the keyboard and the ESC key to save.&lt;br /&gt;
&lt;br /&gt;
Then stop vdr :&lt;br /&gt;
 /etc/init.d/vdr stop&lt;br /&gt;
&lt;br /&gt;
and edit /etc/vdr/setup.conf and change the following lines to look like this :&lt;br /&gt;
 xineliboutput.Audio.Port = iec958&lt;br /&gt;
 xineliboutput.Audio.Speakers = Pass Through&lt;br /&gt;
 CurrentDolby = 1&lt;br /&gt;
 UseDolbyDigital = 1&lt;br /&gt;
&lt;br /&gt;
And if you also want to record Dolby Digital  then also change :&lt;br /&gt;
 RecordDolbyDigital = 1&lt;br /&gt;
&lt;br /&gt;
After saving the changes, restart vdr :&lt;br /&gt;
 /etc/init.d/vdr start&lt;br /&gt;
&lt;br /&gt;
Now you can replay recordings with Dolby Digital Audio&lt;br /&gt;
&lt;br /&gt;
/Viking&lt;br /&gt;
&lt;br /&gt;
===Troubleshooting===&lt;br /&gt;
If VDR works not as you expect you can do following:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ol&amp;gt;&lt;br /&gt;
	&amp;lt;li&amp;gt;Check VDR log - /var/log/pluto/&amp;amp;lt;ID_VDR_IN_YOUR_SYSTEM&amp;amp;gt;_VDR.log&amp;lt;/li&amp;gt;&lt;br /&gt;
	&amp;lt;li&amp;gt;Check if everything ok with your DVB card:&lt;br /&gt;
       &amp;lt;ul&amp;gt;&lt;br /&gt;
	&amp;lt;li&amp;gt;&amp;lt;strong&amp;gt;lspci&amp;lt;/strong&amp;gt; - you should see your card in the list of PCI devices&amp;lt;/li&amp;gt;&lt;br /&gt;
	&amp;lt;li&amp;gt;&amp;lt;strong&amp;gt;dmesg|grep -i dvb&amp;lt;/strong&amp;gt; - if driver if your DVB card is loaded correctly you will see it here. Note that in some cases you should place a firmware for your card into &amp;lt;em&amp;gt;/lib/firmware&amp;lt;/em&amp;gt;!&amp;lt;/li&amp;gt; &lt;br /&gt;
       &amp;lt;/ul&amp;gt;&lt;br /&gt;
        &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
=== MCE Remote Functions ===&lt;br /&gt;
The MCE Remote button functions listed below are for lmcevdr-v10.&lt;br /&gt;
==== What do the buttons do? ====&lt;br /&gt;
[[Image:MCE-Remote-2.jpg|frame|50px|left|MCE IR Remote]]&lt;br /&gt;
==== TV Off ====&lt;br /&gt;
Not implemented currently&lt;br /&gt;
==== PC Off ====&lt;br /&gt;
When the menu bar is displayed or the screen saver is displaying images this button will power off the Core or any Media Directors that have IR remote control features. In VDR this button stops the Live TV picture (any scheduled recordings will be unaffected).&lt;br /&gt;
==== Record ====&lt;br /&gt;
Pressing this button when watching Live TV will start an &#039;Instant Recording&#039;.&lt;br /&gt;
==== Stop ====&lt;br /&gt;
Pressing this button will stop the playback of a recording and return you to the Live TV picture on the channel you were watching previously.&lt;br /&gt;
==== Pause ====&lt;br /&gt;
When you have a Live TV picture on the screen pressing this button will &#039;Pause Live TV&#039; and start recording - pressing this button again will un-pause the picture and start playing the recording while continuing to record the live transmission. If you are watching a recording and you press this button the playback of the recording will stop and the picture will &#039;freeze&#039; on the screen. Pressing this button again will continue the playback of the recording again.&lt;br /&gt;
==== Rew ====&lt;br /&gt;
Rewinds a recording. There are 3 Rew speeds - pressing this button once gives you speed 1, press it again for speed 2 and a third time for speed 3. This button does nothing when watching Live TV.&lt;br /&gt;
==== Play ====&lt;br /&gt;
Pressing this button in &#039;Pause&#039; mode plays the paused recording and pressing it again will &#039;Pause&#039; the playback again.&lt;br /&gt;
==== Fwd ====&lt;br /&gt;
Fast Forwards a recording. There are 3 Fwd speeds - pressing this button once gives you speed 1, press it again for speed 2 and a third time for speed 3. This button does nothing when watching Live TV.&lt;br /&gt;
==== Replay ====&lt;br /&gt;
Press to jump back 1 min in a recording. Press repeatedly to jump back quickly through a recording.&lt;br /&gt;
==== Skip ====&lt;br /&gt;
Press to Skip forward 1 min in a recording. Press repeatedly to jump forward quickly through a recording.&lt;br /&gt;
==== Back ====&lt;br /&gt;
Takes you back to the last VDR on-screen menu if watching Live TV or a Recording and back to previous on-screen menu if an a VDR on-screen menu is already displayed.&lt;br /&gt;
==== More Info ====&lt;br /&gt;
Press once to display &#039;Info screen&#039; for a Live Channel or a Recording. Press again to cancel &#039;Info screen&#039;.&lt;br /&gt;
==== Up Arrow ====&lt;br /&gt;
While watching Live TV does a Channel Up. In on-screen menu moves to the menu option above.&lt;br /&gt;
==== Left Arrow ====&lt;br /&gt;
When watching a recording is equivalent to pressing &#039;Rewind&#039;. In on-screen Schedule menu moves backwards in time.&lt;br /&gt;
==== OK ====&lt;br /&gt;
Pressing this button when Live TV displays the mini on-screen guide for 5 secs at the bottom of the screen. When playing a recording pressing this button displays the playback progress panel at the bottom of the screen. Press again to hide the playback progress panel.&lt;br /&gt;
==== Right Arrow ====&lt;br /&gt;
When watching a recording is equivalent to pressing &#039;Fwd&#039;. In on-screen Schedule menu pressing this button moves forwards in time.&lt;br /&gt;
==== Down Arrow ====&lt;br /&gt;
While watching Live TV pressing this button does a Channel Down. In VDR on-screen menu moves pressing this button moves you to the menu option below. When watching a recording is equivalent to pressing &#039;Pause&#039;.&lt;br /&gt;
==== Vol - (+) (-) ====&lt;br /&gt;
Increase or Decrease volume.&lt;br /&gt;
==== Green Start Button ====&lt;br /&gt;
Displays LinuxMCE Menu Bar.&lt;br /&gt;
==== Channel - (+) (-) ====&lt;br /&gt;
Increases or Decreases the Channel number and then changes to that Live TV channel&lt;br /&gt;
==== Mute ====&lt;br /&gt;
Pressing this button repeatedly toggles between Muted sound, on-screen subtitles and un-muted sound.&lt;br /&gt;
==== Recorded TV ====&lt;br /&gt;
Displays the VDR TV Recordings screen. Use Back repeatedly to back out of on-screen menus and get back to Live TV.&lt;br /&gt;
==== Guide ====&lt;br /&gt;
Displays the on-screen EPG Guide for the currently tuned channel. Use Colour buttons to Record, View Progs, Now &amp;amp; Next, Schedule &amp;amp; Next.&lt;br /&gt;
==== Live TV ====&lt;br /&gt;
Turns on Live TV or if already watching Live TV displays the on-screen EPG.&lt;br /&gt;
==== DVD Menu ====&lt;br /&gt;
When watching Live TV displays Channel List.&lt;br /&gt;
==== 1,2,3,4,5,6,7,8,9,*,0,# ====&lt;br /&gt;
Use to choose channel number directly in Live TV or to jump to on-screen menu items directly when an on-screen menu is displayed.&lt;br /&gt;
==== Clear ====&lt;br /&gt;
Currently unused&lt;br /&gt;
==== Enter ====&lt;br /&gt;
Equivalent to pressing &#039;OK&#039;&lt;br /&gt;
==== Text ====&lt;br /&gt;
Currently unused&lt;br /&gt;
==== Red ====&lt;br /&gt;
In Live TV displays Recordings menu. In VDR menus does the &#039;Red&#039; labeled function.&lt;br /&gt;
==== Green ====&lt;br /&gt;
In Live TV displays Channels on-screen menu. In on-screen menus does the &#039;Green&#039; labeled function.&lt;br /&gt;
==== Yellow ====&lt;br /&gt;
In Live TV displays Info on-screen menu. In on-screen menus does the &#039;Yellow&#039; labeled function.&lt;br /&gt;
==== Blue ====&lt;br /&gt;
In Live TV displays Timers on-screen menu. In on-screen menus does the &#039;Yellow&#039; labeled function.&lt;br /&gt;
== Adding your own plugins to vdr ==&lt;br /&gt;
===Installing vdr-dev===&lt;br /&gt;
If you want to build and add plugins to vdr you need to install the vdr-dev package. Open a console session at your core or ssh in from another machine and do;&lt;br /&gt;
 apt-get install vdr-dev&lt;br /&gt;
Now follow the instructions for building the plugin you are interested in.&lt;br /&gt;
== Manual Installation ==&lt;br /&gt;
For details on manually installing VDR please look in [[VDR Manual Install]].&lt;br /&gt;
== See also ==&lt;br /&gt;
* [http://www.linuxtv.org/vdrwiki/index.php/Main_Page VDR Wiki (English)]&lt;br /&gt;
* [http://www.free-x.de/wiki/index.php VDR Wiki (Russian)]&lt;br /&gt;
* [http://allrussian.info/board.php?boardid=61 VDR Forum (Russian)]&lt;br /&gt;
* [http://www.vdr-portal.de VDR Portal (German)]&lt;/div&gt;</summary>
		<author><name>Viking</name></author>
	</entry>
</feed>