<?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=Ihas</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=Ihas"/>
	<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php/Special:Contributions/Ihas"/>
	<updated>2026-05-11T05:40:23Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.44.0</generator>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=LinuxMCE-0810_alpha1&amp;diff=18319</id>
		<title>LinuxMCE-0810 alpha1</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=LinuxMCE-0810_alpha1&amp;diff=18319"/>
		<updated>2009-04-06T02:00:09Z</updated>

		<summary type="html">&lt;p&gt;Ihas: /* Setup Diskless MD */&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;
&lt;br /&gt;
LinuxMCE-0810-alpha1 is a test release build from the sources available in the LinuxMCE-0810 branch of SVN.  It is missing several components of which the sources are not publicly available.&lt;br /&gt;
&lt;br /&gt;
This page is superseeded by [[LinuxMCE-0810 alpha2]]&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
# Install Kubuntu Intrepid, update it and enable the restricted (video) drivers if needed. ([http://www.kubuntu.org/getkubuntu/download download Kubuntu 8.10 release])&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;
In other words, after installing Kubuntu and upgrading it etcetera:&lt;br /&gt;
 sudo su - #This might ask for the password you specified earlier during the install of kubuntu.&lt;br /&gt;
 wget -c http://deb.linuxmce.org/ubuntu/new-installer-alpha1.tar.bz2&lt;br /&gt;
 tar xvf new-installer-alpha1.tar.bz2&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;
== Setup Diskless MD ==&lt;br /&gt;
# On core from a terminal run sudo /usr/pluto/bin/Diskless_BuildDefaultImage.sh&lt;br /&gt;
# Boot MD&lt;br /&gt;
# Rundiskless setup fails, but the device gets created&lt;br /&gt;
# Change md to i386 in webadmin -&amp;gt; rebuild image&lt;br /&gt;
# On the core&lt;br /&gt;
## Set a password for root on MD&lt;br /&gt;
###chroot /usr/pluto/diskless/&amp;lt;##&amp;gt;&lt;br /&gt;
### run passwd.... enter password for root&lt;br /&gt;
#On MD Switch to a terminal session&lt;br /&gt;
## Login to MD as root&lt;br /&gt;
## apt-get install nvidia-glx-177&lt;br /&gt;
#From core copy valid xorg.conf from etc/X11 to /usr/pluto/diskless/##/etc/X11&lt;br /&gt;
# Reboot MD. Now, the AV Wizard should come up&lt;br /&gt;
# After the AV Wizard it takes a longer time to launch devices. No not need to reboot.&lt;br /&gt;
&lt;br /&gt;
=== Note ===&lt;br /&gt;
If you don&#039;t happen to have a running xorg.conf, copy over the existing /etc/X11/xorg.conf.pluto-avwizard to /etc/X11/xorg.conf. &lt;br /&gt;
&lt;br /&gt;
You have to remove a single line RgbPath from the xorg.conf file, and change the line&lt;br /&gt;
 driver nv&lt;br /&gt;
&lt;br /&gt;
to&lt;br /&gt;
 driver nvidia&lt;br /&gt;
&lt;br /&gt;
== Known Problems ==&lt;br /&gt;
=== Upgrading pluto-storage-devices ===&lt;br /&gt;
If apt-get upgrade does cause problems with pluto-boot-scripts, do the following&lt;br /&gt;
 dpkg -r --force-all pluto-storage-devices&lt;br /&gt;
 apt-get install pluto-storage-devices&lt;br /&gt;
 apt-get upgrade&lt;br /&gt;
&lt;br /&gt;
=== VDR Installation ===&lt;br /&gt;
VDR does not yet install a working setup. Follow [[VDR Manual Install]] regarding configuration files.&lt;br /&gt;
&lt;br /&gt;
=== VDR and sqlCVS Update ===&lt;br /&gt;
A sqlCVS update will reset the selection from VDR back to MythTV. Re-running the Setup wizard and re-selecting VDR rectifies this glitch.&lt;br /&gt;
&lt;br /&gt;
For other older known problems please look at [[LinuxMCE-0810_alpha0]]&lt;br /&gt;
&lt;br /&gt;
==Updates==&lt;br /&gt;
&lt;br /&gt;
===20081206 (alpha-1.1)===&lt;br /&gt;
* pluto-vdr_2.0.0.44.0812060810&lt;br /&gt;
* pluto-src-vdr_2.0.0.44.0812060810&lt;br /&gt;
* pluto-website-admin_2.0.0.44.0812060810&lt;br /&gt;
&lt;br /&gt;
===20081214 (alpha-1.2)===&lt;br /&gt;
* pluto-boot-scripts_2.0.0.44.0812140810&lt;br /&gt;
* pluto-website-admin_2.0.0.44.0812140810&lt;br /&gt;
* pluto-vdr_2.0.0.44.0812140810&lt;br /&gt;
* pluto-src-vdr_2.0.0.44.0812140810&lt;br /&gt;
&lt;br /&gt;
===20081221 (alpha-1.3)===&lt;br /&gt;
* lirc-pluto_0.1.1&lt;br /&gt;
* pluto-skins-basic_2.0.0.44.0812210810&lt;br /&gt;
* pluto-website-admin_2.0.0.44.0812210810&lt;br /&gt;
* pluto-boot-scripts_2.0.0.44.0812210810&lt;br /&gt;
&lt;br /&gt;
===20081228 (alpha-1.4)===&lt;br /&gt;
* asterisk-pluto_1.4.10-4&lt;br /&gt;
* pluto-std-plugins_2.0.0.44.0812280810&lt;br /&gt;
* pluto-storage-devices_2.0.0.44.0812280810&lt;br /&gt;
* pluto-website-admin_2.0.0.44.0812280810&lt;br /&gt;
* pluto-raid-tools_2.0.0.44.0812280810&lt;br /&gt;
* pluto-asterisk_2.0.0.44.0812280810&lt;br /&gt;
* pluto-avwizard-src_2.0.0.44.0812280810&lt;br /&gt;
* pluto-avwizard_2.0.0.44.0812280810&lt;br /&gt;
* pluto-boot-scripts_2.0.0.44.0812280810&lt;br /&gt;
* pluto-capture-card-scripts_2.0.0.44.0812280810&lt;br /&gt;
* pluto-dhcpd-plugin_2.0.0.44.0812280810&lt;br /&gt;
* mce-diskless-tools-src_2.0.0.44.0812280810&lt;br /&gt;
* mce-diskless-tools_2.0.0.44.0812280810&lt;br /&gt;
&lt;br /&gt;
===20090104 (alpha-1.5)===&lt;br /&gt;
* libxine1-xvdr_1.0.1-5+lmce1&lt;br /&gt;
* libxineliboutput-fbfe_1.0.1-5+lmce1&lt;br /&gt;
* libxineliboutput-sxfe_1.0.1-5+lmce1&lt;br /&gt;
* vdr-plugin-xineliboutput_1.0.1-5+lmce1&lt;br /&gt;
* xineliboutput-fbfe_1.0.1-5+lmce1&lt;br /&gt;
* xineliboutput-sxfe_1.0.1-5+lmce1&lt;br /&gt;
* pluto-website-admin_2.0.0.44.0901040810&lt;br /&gt;
&lt;br /&gt;
===20090111 (alpha-1.6)===&lt;br /&gt;
* pluto-website-admin_2.0.0.44.0901110810&lt;br /&gt;
* pluto-updatemedia_2.0.0.44.0901110810 [http://trac.linuxmce.org/trac.cgi/ticket/72 #72] --[[User:Posde|posde]]&lt;br /&gt;
* pluto-slim-server-streamer_2.0.0.44.0901110810 [http://trac.linuxmce.org/trac.cgi/ticket/77 #77] --[[User:Posde|posde]]&lt;br /&gt;
* pluto-boot-scripts_2.0.0.44.0901110810 [http://trac.linuxmce.org/trac.cgi/ticket/80 #80] --[[User:Posde|posde]]&lt;br /&gt;
&lt;br /&gt;
===20090118 (upcoming)===&lt;br /&gt;
* sql2cpp run integration [[User:Posde|posde]] [http://svn.linuxmce.org/trac.cgi/ticket/82]&lt;br /&gt;
...&lt;/div&gt;</summary>
		<author><name>Ihas</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Silicondust_HDHomeRun_DVB-T&amp;diff=17893</id>
		<title>Silicondust HDHomeRun DVB-T</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Silicondust_HDHomeRun_DVB-T&amp;diff=17893"/>
		<updated>2009-03-06T02:50:43Z</updated>

		<summary type="html">&lt;p&gt;Ihas: /* Where to Buy? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Hardware]]&lt;br /&gt;
[[Category: TV_Cards]]&lt;br /&gt;
[[Category: Video]]&lt;br /&gt;
&lt;br /&gt;
[[Image:Hdhomerun.jpg|400px|right|thumb|HDHomeRun]]&lt;br /&gt;
== More Information ==&lt;br /&gt;
&lt;br /&gt;
* Silicondust [http://www.silicondust.com HDHomeRun]&lt;br /&gt;
* [http://www.HDHomeRun.com.au HDHomeRun Australia]&lt;br /&gt;
&lt;br /&gt;
== Where to Buy? ==&lt;br /&gt;
&lt;br /&gt;
Australia&lt;br /&gt;
* [http://www.HDHomeRun.com.au HDHomeRun Australian Website] AUD$299 + AUD$15 Postage&lt;br /&gt;
* Harvey Norman&lt;br /&gt;
* [http://www.ihas.com.au IHAS]&lt;br /&gt;
&lt;br /&gt;
== Overview ==&lt;br /&gt;
&lt;br /&gt;
Watch over-the-air HD digital DVB-T TV from all computers in your home network&lt;br /&gt;
&lt;br /&gt;
Dual tuners - record/watch multiple channels at once&lt;br /&gt;
&lt;br /&gt;
Compatible With:&lt;br /&gt;
    * Windows Media Center:&lt;br /&gt;
          o MCE 2005&lt;br /&gt;
          o Vista MCE 32-bit&lt;br /&gt;
          o Vista MCE 64-bit &lt;br /&gt;
    * SnapStream BeyondTV&lt;br /&gt;
    * SageTV - DVR for Windows &amp;amp; Mac&lt;br /&gt;
    * MediaPortal - DVR for Windows&lt;br /&gt;
    * GB-PVR - DVR for Windows&lt;br /&gt;
    * MythTV - DVR for Linux&lt;br /&gt;
    * Pluto - Home automation &amp;amp; media system&lt;br /&gt;
    * VLC - Multi-platform media viewer&lt;br /&gt;
    * TSReader - MPEG-2 transport stream analysis &lt;br /&gt;
    * Elgato Eye TV for MAC&lt;br /&gt;
&lt;br /&gt;
Detailed Specifications:&lt;br /&gt;
&lt;br /&gt;
    *  QPSK/QAM16/QAM64 (DVB-T over-the-air digital TV)&lt;br /&gt;
    *  8/7/6 MHz channel bandwidth (multi-country operation)&lt;br /&gt;
    *  Dual HDTV Tuners&lt;br /&gt;
    *  IR Receiver (38kHz)&lt;br /&gt;
    *  100baseTX high speed network&lt;br /&gt;
&lt;br /&gt;
Package Includes:&lt;br /&gt;
&lt;br /&gt;
    *  Networked Digital HDTV Tuner&lt;br /&gt;
    *  Power supply&lt;br /&gt;
    *  2 x RG-6 Coax Cables&lt;br /&gt;
    *  1.8M RJ45 Patch Cable&lt;br /&gt;
&lt;br /&gt;
== Configuring ==&lt;br /&gt;
&lt;br /&gt;
TBD&lt;/div&gt;</summary>
		<author><name>Ihas</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Hardy-iglu&amp;diff=15703</id>
		<title>Hardy-iglu</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Hardy-iglu&amp;diff=15703"/>
		<updated>2008-09-24T08:41:59Z</updated>

		<summary type="html">&lt;p&gt;Ihas: /* General issues */&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;
&lt;br /&gt;
hardy-iglu is a test release build from the sources available in the LinuxMCE-0804 branch of SVN.  It is missing several components of which the sources are not publicly available.&lt;br /&gt;
&lt;br /&gt;
==Versions available==&lt;br /&gt;
&lt;br /&gt;
The currently available version is alpha0, which is broken in numerous ways.  This release was only intended to see if the installer works, and perhaps to provide a base for further development.  &lt;br /&gt;
&lt;br /&gt;
===alpha0===&lt;br /&gt;
&lt;br /&gt;
The alpha0 release is broken pretty badly and definately not suited for actual use.  This release is only available as a CD installer for the i386 platform, note that one of the ISO images is currently to big to fit on a CD.  &lt;br /&gt;
&lt;br /&gt;
The Iglu ISO images can currently be downloaded from one of [[User:Zaerc|Zaerc]]&#039;s personal servers (please note that this server is not intended for massive downloading, and will likely be replaced with a torrent if this uses up to much resources).&lt;br /&gt;
* [http://penemue.zaerc.com/linuxmce/isos/Iglu-0804_alpha0.i386.CD1.iso Iglu-0804_alpha0.i386.CD1.iso]&lt;br /&gt;
* [http://penemue.zaerc.com/linuxmce/isos/Iglu-0804_alpha0.i386.CD2.iso Iglu-0804_alpha0.i386.CD2.iso]&lt;br /&gt;
* [http://old-releases.ubuntu.com/releases/kubuntu/hardy/kubuntu-8.04-desktop-i386.iso kubuntu-8.04-desktop-i386.iso]&lt;br /&gt;
====Installation====&lt;br /&gt;
&lt;br /&gt;
It needs to be installed on a clean (not upgraded!) [http://old-releases.ubuntu.com/releases/kubuntu/hardy/ Kubuntu-8.04] desktop install (not 8.04.1!), and there are 2 packages (do not install or upgrade any others) that need to be installed before the lmce installer can be run sucessfully, like this:&lt;br /&gt;
 apt-get update&lt;br /&gt;
 apt-get install dpkg-dev msttcorefonts&lt;br /&gt;
Other then that, the instructions of the regular [[Installation Guide]] apply, except for the versions used.&lt;br /&gt;
&lt;br /&gt;
In a nutshell: &lt;br /&gt;
#Install Kubutu-8.04 desktop from the live-CD.&lt;br /&gt;
#Install the dpkg-dev and msttcorefonts packages in advance as shown above.&lt;br /&gt;
#Copy the 3 ISOs (Iglu-0804_alpha0.i386.CD1.iso, Iglu-0804_alpha0.i386.CD2.iso and kubuntu-8.04-desktop-i386.iso) over to the fresh Kubuntu-8.04 desktop install.&lt;br /&gt;
#Mount Iglu-0804_alpha0.i386.CD1.iso, install the mce-installer_2.0.1-1_i386.deb package and unmount the ISO again.&lt;br /&gt;
#Run the installer by clicking the icon on the desktop, when it asks for the CDs simply point it at the corresponding ISO instead.&lt;br /&gt;
#Walk away and check back in an hour or so.&lt;br /&gt;
&lt;br /&gt;
====Post-install====&lt;br /&gt;
&lt;br /&gt;
After the install has finished edit the &#039;&#039;sources.list&#039;&#039; file to look something like this:&lt;br /&gt;
 deb file:/usr/pluto/deb-cache/ ./&lt;br /&gt;
 &lt;br /&gt;
 deb &amp;lt;nowiki&amp;gt;http://nl.archive.ubuntu.com/ubuntu/&amp;lt;/nowiki&amp;gt; hardy  main restricted multiverse universe&lt;br /&gt;
 deb &amp;lt;nowiki&amp;gt;http://nl.archive.ubuntu.com/ubuntu/&amp;lt;/nowiki&amp;gt; hardy-security  main restricted multiverse universe&lt;br /&gt;
 deb &amp;lt;nowiki&amp;gt;http://nl.archive.ubuntu.com/ubuntu/&amp;lt;/nowiki&amp;gt; hardy-updates  main restricted multiverse universe&lt;br /&gt;
 &lt;br /&gt;
 deb &amp;lt;nowiki&amp;gt;http://packages.medibuntu.org/&amp;lt;/nowiki&amp;gt; hardy free non-free&lt;br /&gt;
 deb &amp;lt;nowiki&amp;gt;http://debian.slimdevices.com/&amp;lt;/nowiki&amp;gt; stable main&lt;br /&gt;
&lt;br /&gt;
Note that you may have a different ubuntu mirror then &#039;&#039;nl.archive.ubuntu.com&#039;&#039; that is probably more suitable, depending on what you chose during the installation of Kubuntu-8.04 of course.&lt;br /&gt;
After modifying the &#039;&#039;sources.list&#039;&#039; file run the following commands:&lt;br /&gt;
 wget -q &amp;lt;nowiki&amp;gt;http://packages.medibuntu.org/medibuntu-key.gpg&amp;lt;/nowiki&amp;gt; -O- | apt-key add -&lt;br /&gt;
 apt-get update&lt;br /&gt;
&lt;br /&gt;
The installer also breaks the &#039;&#039;/etc/init.d/mysql&#039;&#039; script, it now fails to stop the database without generating an error.  This can be corrected by commenting out the line containing &amp;quot;linuxmce&amp;quot;, here&#039;s an easy way to do just that:&lt;br /&gt;
 sed &#039;/linuxmce/s/^.*$/#&amp;amp;/&#039; -i /etc/init.d/mysql&lt;br /&gt;
&lt;br /&gt;
====Known problems====&lt;br /&gt;
Please add all the issues you can find below, and/or add your name to the list of people confirming (simply sign it with &amp;lt;nowiki&amp;gt;~~~&amp;lt;/nowiki&amp;gt;).&lt;br /&gt;
&lt;br /&gt;
=====General issues=====&lt;br /&gt;
*Several buttons appear to be missing in the setup wizard, probaly just one or more missing graphics.&lt;br /&gt;
Confirmed by: [[User:Zaerc|Zaerc]]&lt;br /&gt;
*The &amp;quot;Add Software&amp;quot; list is empty, this probably needs to be filled somewhere, see also &amp;quot;workarounds&amp;quot; below.&lt;br /&gt;
Confirmed by: [[User:Zaerc|Zaerc]]&lt;br /&gt;
*There are entries for old repositories in the sources.list, they probably need to be removed&lt;br /&gt;
Confirmed by: [[User:Zaerc|Zaerc]]&lt;br /&gt;
*Asterisk apparently fails to run (without even giving a proper error).&lt;br /&gt;
Confirmed by: [[User:Zaerc|Zaerc]]&lt;br /&gt;
*Sending the MobileOrbiter software to the phone fails as the binaries weren&#039;t build, however it does work if the orbiter was already installed on the phone by a previous version of lmce.&lt;br /&gt;
Confirmed by: [[User:Zaerc|Zaerc]]&lt;br /&gt;
*Lirc is not working &lt;br /&gt;
Confirmed by: [[User:hgait|hgait]]&lt;br /&gt;
&lt;br /&gt;
=====UI1 related=====&lt;br /&gt;
*Several graphics for buttons (&amp;quot;Remote&amp;quot;, &amp;quot;Options&amp;quot; and &amp;quot;Play All&amp;quot;) are missing from the video file list screen.&lt;br /&gt;
Confirmed by: [[User:Zaerc|Zaerc]]&lt;br /&gt;
&lt;br /&gt;
=====UI2 related=====&lt;br /&gt;
*Playback issue where the video is only visible when the UI is on-screen&lt;br /&gt;
Confirmed by: [[User:Zaerc|Zaerc]]&lt;br /&gt;
&lt;br /&gt;
====Workarounds and fixes====&lt;br /&gt;
*Installing libdvdcss and/or w32codecs.&lt;br /&gt;
 apt-get update&lt;br /&gt;
 apt-get install libdvdcss2 #if you want libdvdcss&lt;br /&gt;
 apt-get install w32codecs #if you want the w32codecs&lt;br /&gt;
&lt;br /&gt;
Confirmed by: &lt;br /&gt;
&lt;br /&gt;
*The External Media Identifier fails to start, this is because it wasn&#039;t build as the sources are not available.&lt;br /&gt;
Turn it off by disabeling it in the web-admin&#039;s &amp;quot;devices tree&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Confirmed by: [[User:Zaerc|Zaerc]]&lt;br /&gt;
&lt;br /&gt;
The External Media Identifier can be installed successfully using the 0710 &amp;quot;id-my-disc_1.8.ub0710_i386.deb&amp;quot; package.&lt;br /&gt;
After doing the [[Hardy-iglu#Updates|Updates]] listed below, it can be installed with &#039;&#039;&#039;apt-get install id-my-disc&#039;&#039;&#039; (or even with the adept package manager on the KDE Desktop).&lt;br /&gt;
&lt;br /&gt;
Confirmed by: [[User:tkmedia|tkmedia]], [[User:Zaerc|Zaerc]]&lt;br /&gt;
&lt;br /&gt;
====Confirmed Working====&lt;br /&gt;
*The mce-installer.&lt;br /&gt;
Confirmed by: [[User:Zaerc|Zaerc]]&lt;br /&gt;
*The flickr photo screen saver.&lt;br /&gt;
Confirmed by: [[User:Zaerc|Zaerc]]&lt;br /&gt;
*Diskless media director.&lt;br /&gt;
Confirmed by: [[User:tkmedia|tkmedia]] (using initial manual setup)&lt;br /&gt;
*The Symbian-60(v2) Mobile-Orbiter, &#039;&#039;provided that the software was already installed on the device by a previous version of lmce.&#039;&#039;&lt;br /&gt;
Confirmed by: [[User:Zaerc|Zaerc]]&lt;br /&gt;
*[[gc100]].&lt;br /&gt;
Confirmed by: [[User:Zaerc|Zaerc]]  (older firmware that requires manual setup)&lt;br /&gt;
*[[CM11]].&lt;br /&gt;
Confirmed by: [[User:Zaerc|Zaerc]]&lt;br /&gt;
*KDE Desktop.&lt;br /&gt;
Confirmed by: [[User:Zaerc|Zaerc]]&lt;br /&gt;
*Mythtv works in a fashion still testing more &lt;br /&gt;
Confirmed By [[User:hgait|hgait]]&lt;br /&gt;
&lt;br /&gt;
====Updates====&lt;br /&gt;
&lt;br /&gt;
There are updated packages available, add these lines to your &#039;&#039;/etc/apt/sources.list&#039;&#039; file:&lt;br /&gt;
 deb &amp;lt;nowiki&amp;gt;http://penemue.zaerc.com/linuxmce/&amp;lt;/nowiki&amp;gt; hardy-iglu  universe multiverse&lt;br /&gt;
 deb &amp;lt;nowiki&amp;gt;http://penemue.zaerc.com/linuxmce/&amp;lt;/nowiki&amp;gt; hardy-iglu-updates  universe&lt;br /&gt;
&lt;br /&gt;
By default the mce-installer pins the system to a certain version in order to block upgrades, this needs to be undone with the following command:&lt;br /&gt;
 mv /etc/apt/preferences /etc/apt/preferences.save&lt;br /&gt;
&lt;br /&gt;
Then you can update your system to the latest version of hardy using the following commands:&lt;br /&gt;
 apt-get update&lt;br /&gt;
 apt-get -y upgrade&lt;br /&gt;
 apt-get install -y zaptel-modules-2.6.24-19-generic&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
Alternatively it should be possible to use a graphical package manager like KDE&#039;s adept, which can be installed as followed:&lt;br /&gt;
 apt-get install -y adept&lt;br /&gt;
&lt;br /&gt;
=====Issues fixed=====&lt;br /&gt;
* Modules for newer kernel version (2.6.24-19-generic).&lt;br /&gt;
* Subtitles crashing Xine_Player [issue [http://mantis.linuxmce.org/view.php?id=4200 #4200]].&lt;/div&gt;</summary>
		<author><name>Ihas</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Hardy-iglu&amp;diff=15702</id>
		<title>Hardy-iglu</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Hardy-iglu&amp;diff=15702"/>
		<updated>2008-09-24T08:34:05Z</updated>

		<summary type="html">&lt;p&gt;Ihas: /* Confirmed Working */&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;
&lt;br /&gt;
hardy-iglu is a test release build from the sources available in the LinuxMCE-0804 branch of SVN.  It is missing several components of which the sources are not publicly available.&lt;br /&gt;
&lt;br /&gt;
==Versions available==&lt;br /&gt;
&lt;br /&gt;
The currently available version is alpha0, which is broken in numerous ways.  This release was only intended to see if the installer works, and perhaps to provide a base for further development.  &lt;br /&gt;
&lt;br /&gt;
===alpha0===&lt;br /&gt;
&lt;br /&gt;
The alpha0 release is broken pretty badly and definately not suited for actual use.  This release is only available as a CD installer for the i386 platform, note that one of the ISO images is currently to big to fit on a CD.  &lt;br /&gt;
&lt;br /&gt;
The Iglu ISO images can currently be downloaded from one of [[User:Zaerc|Zaerc]]&#039;s personal servers (please note that this server is not intended for massive downloading, and will likely be replaced with a torrent if this uses up to much resources).&lt;br /&gt;
* [http://penemue.zaerc.com/linuxmce/isos/Iglu-0804_alpha0.i386.CD1.iso Iglu-0804_alpha0.i386.CD1.iso]&lt;br /&gt;
* [http://penemue.zaerc.com/linuxmce/isos/Iglu-0804_alpha0.i386.CD2.iso Iglu-0804_alpha0.i386.CD2.iso]&lt;br /&gt;
* [http://old-releases.ubuntu.com/releases/kubuntu/hardy/kubuntu-8.04-desktop-i386.iso kubuntu-8.04-desktop-i386.iso]&lt;br /&gt;
====Installation====&lt;br /&gt;
&lt;br /&gt;
It needs to be installed on a clean (not upgraded!) [http://old-releases.ubuntu.com/releases/kubuntu/hardy/ Kubuntu-8.04] desktop install (not 8.04.1!), and there are 2 packages (do not install or upgrade any others) that need to be installed before the lmce installer can be run sucessfully, like this:&lt;br /&gt;
 apt-get update&lt;br /&gt;
 apt-get install dpkg-dev msttcorefonts&lt;br /&gt;
Other then that, the instructions of the regular [[Installation Guide]] apply, except for the versions used.&lt;br /&gt;
&lt;br /&gt;
In a nutshell: &lt;br /&gt;
#Install Kubutu-8.04 desktop from the live-CD.&lt;br /&gt;
#Install the dpkg-dev and msttcorefonts packages in advance as shown above.&lt;br /&gt;
#Copy the 3 ISOs (Iglu-0804_alpha0.i386.CD1.iso, Iglu-0804_alpha0.i386.CD2.iso and kubuntu-8.04-desktop-i386.iso) over to the fresh Kubuntu-8.04 desktop install.&lt;br /&gt;
#Mount Iglu-0804_alpha0.i386.CD1.iso, install the mce-installer_2.0.1-1_i386.deb package and unmount the ISO again.&lt;br /&gt;
#Run the installer by clicking the icon on the desktop, when it asks for the CDs simply point it at the corresponding ISO instead.&lt;br /&gt;
#Walk away and check back in an hour or so.&lt;br /&gt;
&lt;br /&gt;
====Post-install====&lt;br /&gt;
&lt;br /&gt;
After the install has finished edit the &#039;&#039;sources.list&#039;&#039; file to look something like this:&lt;br /&gt;
 deb file:/usr/pluto/deb-cache/ ./&lt;br /&gt;
 &lt;br /&gt;
 deb &amp;lt;nowiki&amp;gt;http://nl.archive.ubuntu.com/ubuntu/&amp;lt;/nowiki&amp;gt; hardy  main restricted multiverse universe&lt;br /&gt;
 deb &amp;lt;nowiki&amp;gt;http://nl.archive.ubuntu.com/ubuntu/&amp;lt;/nowiki&amp;gt; hardy-security  main restricted multiverse universe&lt;br /&gt;
 deb &amp;lt;nowiki&amp;gt;http://nl.archive.ubuntu.com/ubuntu/&amp;lt;/nowiki&amp;gt; hardy-updates  main restricted multiverse universe&lt;br /&gt;
 &lt;br /&gt;
 deb &amp;lt;nowiki&amp;gt;http://packages.medibuntu.org/&amp;lt;/nowiki&amp;gt; hardy free non-free&lt;br /&gt;
 deb &amp;lt;nowiki&amp;gt;http://debian.slimdevices.com/&amp;lt;/nowiki&amp;gt; stable main&lt;br /&gt;
&lt;br /&gt;
Note that you may have a different ubuntu mirror then &#039;&#039;nl.archive.ubuntu.com&#039;&#039; that is probably more suitable, depending on what you chose during the installation of Kubuntu-8.04 of course.&lt;br /&gt;
After modifying the &#039;&#039;sources.list&#039;&#039; file run the following commands:&lt;br /&gt;
 wget -q &amp;lt;nowiki&amp;gt;http://packages.medibuntu.org/medibuntu-key.gpg&amp;lt;/nowiki&amp;gt; -O- | apt-key add -&lt;br /&gt;
 apt-get update&lt;br /&gt;
&lt;br /&gt;
The installer also breaks the &#039;&#039;/etc/init.d/mysql&#039;&#039; script, it now fails to stop the database without generating an error.  This can be corrected by commenting out the line containing &amp;quot;linuxmce&amp;quot;, here&#039;s an easy way to do just that:&lt;br /&gt;
 sed &#039;/linuxmce/s/^.*$/#&amp;amp;/&#039; -i /etc/init.d/mysql&lt;br /&gt;
&lt;br /&gt;
====Known problems====&lt;br /&gt;
Please add all the issues you can find below, and/or add your name to the list of people confirming (simply sign it with &amp;lt;nowiki&amp;gt;~~~&amp;lt;/nowiki&amp;gt;).&lt;br /&gt;
&lt;br /&gt;
=====General issues=====&lt;br /&gt;
*Several buttons appear to be missing in the setup wizard, probaly just one or more missing graphics.&lt;br /&gt;
Confirmed by: [[User:Zaerc|Zaerc]]&lt;br /&gt;
*The &amp;quot;Add Software&amp;quot; list is empty, this probably needs to be filled somewhere, see also &amp;quot;workarounds&amp;quot; below.&lt;br /&gt;
Confirmed by: [[User:Zaerc|Zaerc]]&lt;br /&gt;
*There are entries for old repositories in the sources.list, they probably need to be removed&lt;br /&gt;
Confirmed by: [[User:Zaerc|Zaerc]]&lt;br /&gt;
*Asterisk apparently fails to run (without even giving a proper error).&lt;br /&gt;
Confirmed by: [[User:Zaerc|Zaerc]]&lt;br /&gt;
*Sending the MobileOrbiter software to the phone fails as the binaries weren&#039;t build, however it does work if the orbiter was already installed on the phone by a previous version of lmce.&lt;br /&gt;
Confirmed by: [[User:Zaerc|Zaerc]]&lt;br /&gt;
&lt;br /&gt;
=====UI1 related=====&lt;br /&gt;
*Several graphics for buttons (&amp;quot;Remote&amp;quot;, &amp;quot;Options&amp;quot; and &amp;quot;Play All&amp;quot;) are missing from the video file list screen.&lt;br /&gt;
Confirmed by: [[User:Zaerc|Zaerc]]&lt;br /&gt;
&lt;br /&gt;
=====UI2 related=====&lt;br /&gt;
*Playback issue where the video is only visible when the UI is on-screen&lt;br /&gt;
Confirmed by: [[User:Zaerc|Zaerc]]&lt;br /&gt;
&lt;br /&gt;
====Workarounds and fixes====&lt;br /&gt;
*Installing libdvdcss and/or w32codecs.&lt;br /&gt;
 apt-get update&lt;br /&gt;
 apt-get install libdvdcss2 #if you want libdvdcss&lt;br /&gt;
 apt-get install w32codecs #if you want the w32codecs&lt;br /&gt;
&lt;br /&gt;
Confirmed by: &lt;br /&gt;
&lt;br /&gt;
*The External Media Identifier fails to start, this is because it wasn&#039;t build as the sources are not available.&lt;br /&gt;
Turn it off by disabeling it in the web-admin&#039;s &amp;quot;devices tree&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Confirmed by: [[User:Zaerc|Zaerc]]&lt;br /&gt;
&lt;br /&gt;
The External Media Identifier can be installed successfully using the 0710 &amp;quot;id-my-disc_1.8.ub0710_i386.deb&amp;quot; package.&lt;br /&gt;
After doing the [[Hardy-iglu#Updates|Updates]] listed below, it can be installed with &#039;&#039;&#039;apt-get install id-my-disc&#039;&#039;&#039; (or even with the adept package manager on the KDE Desktop).&lt;br /&gt;
&lt;br /&gt;
Confirmed by: [[User:tkmedia|tkmedia]], [[User:Zaerc|Zaerc]]&lt;br /&gt;
&lt;br /&gt;
====Confirmed Working====&lt;br /&gt;
*The mce-installer.&lt;br /&gt;
Confirmed by: [[User:Zaerc|Zaerc]]&lt;br /&gt;
*The flickr photo screen saver.&lt;br /&gt;
Confirmed by: [[User:Zaerc|Zaerc]]&lt;br /&gt;
*Diskless media director.&lt;br /&gt;
Confirmed by: [[User:tkmedia|tkmedia]] (using initial manual setup)&lt;br /&gt;
*The Symbian-60(v2) Mobile-Orbiter, &#039;&#039;provided that the software was already installed on the device by a previous version of lmce.&#039;&#039;&lt;br /&gt;
Confirmed by: [[User:Zaerc|Zaerc]]&lt;br /&gt;
*[[gc100]].&lt;br /&gt;
Confirmed by: [[User:Zaerc|Zaerc]]  (older firmware that requires manual setup)&lt;br /&gt;
*[[CM11]].&lt;br /&gt;
Confirmed by: [[User:Zaerc|Zaerc]]&lt;br /&gt;
*KDE Desktop.&lt;br /&gt;
Confirmed by: [[User:Zaerc|Zaerc]]&lt;br /&gt;
*Mythtv works in a fashion still testing more &lt;br /&gt;
Confirmed By [[User:hgait|hgait]]&lt;br /&gt;
&lt;br /&gt;
====Updates====&lt;br /&gt;
&lt;br /&gt;
There are updated packages available, add these lines to your &#039;&#039;/etc/apt/sources.list&#039;&#039; file:&lt;br /&gt;
 deb &amp;lt;nowiki&amp;gt;http://penemue.zaerc.com/linuxmce/&amp;lt;/nowiki&amp;gt; hardy-iglu  universe multiverse&lt;br /&gt;
 deb &amp;lt;nowiki&amp;gt;http://penemue.zaerc.com/linuxmce/&amp;lt;/nowiki&amp;gt; hardy-iglu-updates  universe&lt;br /&gt;
&lt;br /&gt;
By default the mce-installer pins the system to a certain version in order to block upgrades, this needs to be undone with the following command:&lt;br /&gt;
 mv /etc/apt/preferences /etc/apt/preferences.save&lt;br /&gt;
&lt;br /&gt;
Then you can update your system to the latest version of hardy using the following commands:&lt;br /&gt;
 apt-get update&lt;br /&gt;
 apt-get -y upgrade&lt;br /&gt;
 apt-get install -y zaptel-modules-2.6.24-19-generic&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
Alternatively it should be possible to use a graphical package manager like KDE&#039;s adept, which can be installed as followed:&lt;br /&gt;
 apt-get install -y adept&lt;br /&gt;
&lt;br /&gt;
=====Issues fixed=====&lt;br /&gt;
* Modules for newer kernel version (2.6.24-19-generic).&lt;br /&gt;
* Subtitles crashing Xine_Player [issue [http://mantis.linuxmce.org/view.php?id=4200 #4200]].&lt;/div&gt;</summary>
		<author><name>Ihas</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Upgrading_the_Kernel&amp;diff=15701</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=15701"/>
		<updated>2008-09-23T00:53:57Z</updated>

		<summary type="html">&lt;p&gt;Ihas: /* Steps */&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;
{| align=&amp;quot;right&amp;quot;&lt;br /&gt;
  | __TOC__&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. The kernel version that ships with LinuxMCE 0710 is 2.6.22-14. At the time of writing the most recent kernel version is 2.6.26.5. 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;
==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;
==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;
The first step is to grab the kernel source and extract it to the /usr/src folder.&lt;br /&gt;
&lt;br /&gt;
 wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.26.5.tar.bz2&lt;br /&gt;
 tar -jxvf linux-2.6.26.5.tar.bz&lt;br /&gt;
 rm linux&lt;br /&gt;
 ln -s linux-2.6.26.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;
 apt-get install libncurses5 libncurses5-dev&lt;br /&gt;
 make menuconfig 2&amp;gt; module_errors&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;
&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;
 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.26.5&lt;br /&gt;
 mkinitramfs -o /boot/initrd.img-2.6.26.5 2.6.26.5&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;
&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;
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;
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.17.tar.bz2&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/firmware/alsa-firmware-1.0.17.tar.bz2&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/lib/alsa-lib-1.0.17a.tar.bz2&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/plugins/alsa-plugins-1.0.17.tar.bz2&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/utils/alsa-utils-1.0.17.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.17 &lt;br /&gt;
 ./configure --with-cards=hda-intel&lt;br /&gt;
 make&lt;br /&gt;
 make install&lt;br /&gt;
 cd ..&lt;br /&gt;
 for fi in alsa-lib-1.0.17a alsa-plugins-1.0.17 alsa-utils-1.0.17 alsa-oss-1.0.17 alsa-firmware-1.0.17; do&lt;br /&gt;
 cd $fi&lt;br /&gt;
 ./configure&lt;br /&gt;
 make&lt;br /&gt;
 make install&lt;br /&gt;
 cd ..&lt;br /&gt;
 done&lt;br /&gt;
 &lt;br /&gt;
&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;
 make install&lt;br /&gt;
&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. 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;
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_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&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;
==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 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>Ihas</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Upgrading_the_Kernel&amp;diff=15697</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=15697"/>
		<updated>2008-09-23T00:40:56Z</updated>

		<summary type="html">&lt;p&gt;Ihas: /* Steps */&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;
{| align=&amp;quot;right&amp;quot;&lt;br /&gt;
  | __TOC__&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. The kernel version that ships with LinuxMCE 0710 is 2.6.22-14. At the time of writing the most recent kernel version is 2.6.26.5. 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;
==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;
==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;
The first step is to grab the kernel source and extract it to the /usr/src folder.&lt;br /&gt;
&lt;br /&gt;
 wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.26.5.tar.bz2&lt;br /&gt;
 tar -jxvf linux-2.6.26.5.tar.bz&lt;br /&gt;
 rm linux&lt;br /&gt;
 ln -s linux-2.6.26.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;
 apt-get install libncurses5 libncurses5-dev&lt;br /&gt;
 make menuconfig 2&amp;gt; module_errors&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;
&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;
 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.26.5&lt;br /&gt;
mkinitramfs -o /boot/initrd.img-2.6.26.5 2.6.26.5&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;
&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;
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;
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.17.tar.bz2&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/firmware/alsa-firmware-1.0.17.tar.bz2&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/lib/alsa-lib-1.0.17a.tar.bz2&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/plugins/alsa-plugins-1.0.17.tar.bz2&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/utils/alsa-utils-1.0.17.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.17 &lt;br /&gt;
 ./configure --with-cards=hda-intel&lt;br /&gt;
 make&lt;br /&gt;
 make install&lt;br /&gt;
 cd ..&lt;br /&gt;
 for fi in alsa-lib-1.0.17a alsa-plugins-1.0.17 alsa-utils-1.0.17 alsa-oss-1.0.17 alsa-firmware-1.0.17; do&lt;br /&gt;
 cd $fi&lt;br /&gt;
 ./configure&lt;br /&gt;
 make&lt;br /&gt;
 make install&lt;br /&gt;
 cd ..&lt;br /&gt;
 done&lt;br /&gt;
 &lt;br /&gt;
&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;
 make install&lt;br /&gt;
&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. 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;
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_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&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;
==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 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>Ihas</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Upgrading_the_Kernel&amp;diff=15696</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=15696"/>
		<updated>2008-09-23T00:34:46Z</updated>

		<summary type="html">&lt;p&gt;Ihas: /* Steps */&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;
{| align=&amp;quot;right&amp;quot;&lt;br /&gt;
  | __TOC__&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. The kernel version that ships with LinuxMCE 0710 is 2.6.22-14. At the time of writing the most recent kernel version is 2.6.26.5. 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;
==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;
==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;
The first step is to grab the kernel source and extract it to the /usr/src folder.&lt;br /&gt;
&lt;br /&gt;
 wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.26.5.tar.bz2&lt;br /&gt;
 tar -jxvf linux-2.6.26.5.tar.bz&lt;br /&gt;
 rm linux&lt;br /&gt;
 ln -s linux-2.6.26.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;
 apt-get install libncurses5 libncurses5-dev&lt;br /&gt;
 make menuconfig 2&amp;gt; module_errors&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;
&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;
 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.26.5&lt;br /&gt;
mkinitramfs -o /boot/initrd.img-2.6.26.5 2.6.26.5&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;
&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;
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;
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.17.tar.bz2&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/firmware/alsa-firmware-1.0.17.tar.bz2&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/lib/alsa-lib-1.0.17a.tar.bz2&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/plugins/alsa-plugins-1.0.17.tar.bz2&lt;br /&gt;
 wget ftp://ftp.alsa-project.org/pub/utils/alsa-utils-1.0.17.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.17 &lt;br /&gt;
 ./configure --with-cards=hda-intel&lt;br /&gt;
 make&lt;br /&gt;
 make install&lt;br /&gt;
 cd ..&lt;br /&gt;
 for fi in alsa-lib-1.0.17a alsa-plugins-1.0.17 alsa-utils-1.0.17 alsa-oss-1.0.17 alsa-firmware-1.0.17; do&lt;br /&gt;
 cd $fi&lt;br /&gt;
 ./configure&lt;br /&gt;
 make&lt;br /&gt;
 make install&lt;br /&gt;
 cd ..&lt;br /&gt;
 done&lt;br /&gt;
 &lt;br /&gt;
&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;
 make install&lt;br /&gt;
&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. 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;
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_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&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;
==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 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>Ihas</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=VOIP_Service_Providers&amp;diff=15214</id>
		<title>VOIP Service Providers</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=VOIP_Service_Providers&amp;diff=15214"/>
		<updated>2008-08-12T03:21:55Z</updated>

		<summary type="html">&lt;p&gt;Ihas: /* Require Manual Setup */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Phone Lines]]&lt;br /&gt;
[[Category:Telecom]]&lt;br /&gt;
&lt;br /&gt;
If you do not see your VOIP Provider listed here also check [[:Category:Phone Lines| Phone Lines]]&lt;br /&gt;
&lt;br /&gt;
==Automatically Setup==&lt;br /&gt;
* [[Broadvoice]]&lt;br /&gt;
* [[E-Fon_(Switzerland)]]&lt;br /&gt;
* [[Inphonex]]&lt;br /&gt;
* [[NuFone]]&lt;br /&gt;
* [[Sipgate]]&lt;br /&gt;
* [[Teliax]]&lt;br /&gt;
* [[VoiceEclipse]]&lt;br /&gt;
&lt;br /&gt;
==Require Manual Setup==&lt;br /&gt;
&lt;br /&gt;
Here is a description on [[Manual Phones Configuration | How to Configure Phone Lines Manually]]&lt;br /&gt;
&lt;br /&gt;
* gotalk - VoIP providers - Australia - [http://www.gotalk.com]&lt;br /&gt;
* Voipwa - VoIP providers - Australia - [http://www.voipwa.com.au]&lt;br /&gt;
* [[Free world dialup]]&lt;br /&gt;
* [[VOIP with XS4All]]&lt;/div&gt;</summary>
		<author><name>Ihas</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Ihas&amp;diff=15199</id>
		<title>User:Ihas</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Ihas&amp;diff=15199"/>
		<updated>2008-08-08T02:12:40Z</updated>

		<summary type="html">&lt;p&gt;Ihas: /* MDs */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[category:User Setups]] &lt;br /&gt;
==About Us==&lt;br /&gt;
&lt;br /&gt;
ihas (Innovative Home Automation Systems) is a company in Perth, Western Australia specialising in Home Automation solutions for the Australian market.&lt;br /&gt;
&lt;br /&gt;
We have been active in the IT industry for several years, and also operate a VoIP provider with PSTN interconnect capabilities.  We started investigating LinuxMCE for our own use in 2007 and when we realised that working setups were something we could sell, we formed ihas and began building and selling LinuxMCE solutions.&lt;br /&gt;
&lt;br /&gt;
Together our staff have over 30 years&#039; experience in the IT industry, most of that with Linux.&lt;br /&gt;
&lt;br /&gt;
==Our Hardware==&lt;br /&gt;
&lt;br /&gt;
We have a number of clients &#039;out there&#039; using LinuxMCE in their homes and businesses.&lt;br /&gt;
&lt;br /&gt;
All our systems are built using quality hardware which we have tested in operation in our own workshop.  If we can&#039;t make it work, it doesn&#039;t get used.&lt;br /&gt;
&lt;br /&gt;
Let&#039;s have a look at a couple of the systems we&#039;ve installed.  These are both home customers, &lt;br /&gt;
&lt;br /&gt;
===Setup 1===&lt;br /&gt;
&lt;br /&gt;
This first system is a home customer.&lt;br /&gt;
&lt;br /&gt;
====Core====&lt;br /&gt;
&lt;br /&gt;
Hybrid/Core&lt;br /&gt;
&lt;br /&gt;
* Intel Core 2 Quad CPU 2.4 GHz&lt;br /&gt;
* MSI Mainboard&lt;br /&gt;
* 2 G RAM&lt;br /&gt;
* Maxtor STM 325082 250G SATA-II Hard Drive (for boot)&lt;br /&gt;
* Seagate ST3500630AS 500G SATA-II Hard Drive (for storage)&lt;br /&gt;
* LG GH20NS10 DVD-RAM&lt;br /&gt;
* Nova-T-500 Dual DVB-T Tuner card&lt;br /&gt;
&lt;br /&gt;
====MDs====&lt;br /&gt;
&lt;br /&gt;
* 3 x MSI MediaLive! Barebones with Athlon 64 X2 Dual Core 4200+ CPU and 4G RAM.&lt;br /&gt;
&lt;br /&gt;
* AOpen 945 Mini PC, which uses an Intel Mobile CPU with 2G RAM.&lt;br /&gt;
&lt;br /&gt;
====Phones====&lt;br /&gt;
&lt;br /&gt;
* Cisco 7970G IP Phone&lt;br /&gt;
&lt;br /&gt;
===Setup 2===&lt;br /&gt;
&lt;br /&gt;
====Core====&lt;/div&gt;</summary>
		<author><name>Ihas</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Ihas&amp;diff=15198</id>
		<title>User:Ihas</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Ihas&amp;diff=15198"/>
		<updated>2008-08-08T02:11:29Z</updated>

		<summary type="html">&lt;p&gt;Ihas: /* MDs */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[category:User Setups]] &lt;br /&gt;
==About Us==&lt;br /&gt;
&lt;br /&gt;
ihas (Innovative Home Automation Systems) is a company in Perth, Western Australia specialising in Home Automation solutions for the Australian market.&lt;br /&gt;
&lt;br /&gt;
We have been active in the IT industry for several years, and also operate a VoIP provider with PSTN interconnect capabilities.  We started investigating LinuxMCE for our own use in 2007 and when we realised that working setups were something we could sell, we formed ihas and began building and selling LinuxMCE solutions.&lt;br /&gt;
&lt;br /&gt;
Together our staff have over 30 years&#039; experience in the IT industry, most of that with Linux.&lt;br /&gt;
&lt;br /&gt;
==Our Hardware==&lt;br /&gt;
&lt;br /&gt;
We have a number of clients &#039;out there&#039; using LinuxMCE in their homes and businesses.&lt;br /&gt;
&lt;br /&gt;
All our systems are built using quality hardware which we have tested in operation in our own workshop.  If we can&#039;t make it work, it doesn&#039;t get used.&lt;br /&gt;
&lt;br /&gt;
Let&#039;s have a look at a couple of the systems we&#039;ve installed.  These are both home customers, &lt;br /&gt;
&lt;br /&gt;
===Setup 1===&lt;br /&gt;
&lt;br /&gt;
This first system is a home customer.&lt;br /&gt;
&lt;br /&gt;
====Core====&lt;br /&gt;
&lt;br /&gt;
Hybrid/Core&lt;br /&gt;
&lt;br /&gt;
* Intel Core 2 Quad CPU 2.4 GHz&lt;br /&gt;
* MSI Mainboard&lt;br /&gt;
* 2 G RAM&lt;br /&gt;
* Maxtor STM 325082 250G SATA-II Hard Drive (for boot)&lt;br /&gt;
* Seagate ST3500630AS 500G SATA-II Hard Drive (for storage)&lt;br /&gt;
* LG GH20NS10 DVD-RAM&lt;br /&gt;
* Nova-T-500 Dual DVB-T Tuner card&lt;br /&gt;
&lt;br /&gt;
====MDs====&lt;br /&gt;
&lt;br /&gt;
There are three MDs, built around the MSI MediaLive! Barebones with Athlon 64 X2 Dual Core 4200+ CPU and 4G RAM.&lt;br /&gt;
&lt;br /&gt;
There is also an AOpen 945 Mini PC, which uses an Intel Mobile CPU.  It has 2G RAM in it.&lt;br /&gt;
&lt;br /&gt;
====Phones====&lt;br /&gt;
&lt;br /&gt;
* Cisco 7970G IP Phone&lt;br /&gt;
&lt;br /&gt;
===Setup 2===&lt;br /&gt;
&lt;br /&gt;
====Core====&lt;/div&gt;</summary>
		<author><name>Ihas</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Ihas&amp;diff=15197</id>
		<title>User:Ihas</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Ihas&amp;diff=15197"/>
		<updated>2008-08-08T02:07:16Z</updated>

		<summary type="html">&lt;p&gt;Ihas: /* Our Hardware */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[category:User Setups]] &lt;br /&gt;
==About Us==&lt;br /&gt;
&lt;br /&gt;
ihas (Innovative Home Automation Systems) is a company in Perth, Western Australia specialising in Home Automation solutions for the Australian market.&lt;br /&gt;
&lt;br /&gt;
We have been active in the IT industry for several years, and also operate a VoIP provider with PSTN interconnect capabilities.  We started investigating LinuxMCE for our own use in 2007 and when we realised that working setups were something we could sell, we formed ihas and began building and selling LinuxMCE solutions.&lt;br /&gt;
&lt;br /&gt;
Together our staff have over 30 years&#039; experience in the IT industry, most of that with Linux.&lt;br /&gt;
&lt;br /&gt;
==Our Hardware==&lt;br /&gt;
&lt;br /&gt;
We have a number of clients &#039;out there&#039; using LinuxMCE in their homes and businesses.&lt;br /&gt;
&lt;br /&gt;
All our systems are built using quality hardware which we have tested in operation in our own workshop.  If we can&#039;t make it work, it doesn&#039;t get used.&lt;br /&gt;
&lt;br /&gt;
Let&#039;s have a look at a couple of the systems we&#039;ve installed.  These are both home customers, &lt;br /&gt;
&lt;br /&gt;
===Setup 1===&lt;br /&gt;
&lt;br /&gt;
This first system is a home customer.&lt;br /&gt;
&lt;br /&gt;
====Core====&lt;br /&gt;
&lt;br /&gt;
Hybrid/Core&lt;br /&gt;
&lt;br /&gt;
* Intel Core 2 Quad CPU 2.4 GHz&lt;br /&gt;
* MSI Mainboard&lt;br /&gt;
* 2 G RAM&lt;br /&gt;
* Maxtor STM 325082 250G SATA-II Hard Drive (for boot)&lt;br /&gt;
* Seagate ST3500630AS 500G SATA-II Hard Drive (for storage)&lt;br /&gt;
* LG GH20NS10 DVD-RAM&lt;br /&gt;
* Nova-T-500 Dual DVB-T Tuner card&lt;br /&gt;
&lt;br /&gt;
====MDs====&lt;br /&gt;
&lt;br /&gt;
There are two MDs, both built around the MSI MediaLive! Barebones with Athlon 64 X2 Dual Core 4200+ CPU and 4G RAM.&lt;br /&gt;
&lt;br /&gt;
====Phones====&lt;br /&gt;
&lt;br /&gt;
* Cisco 7970G IP Phone&lt;br /&gt;
&lt;br /&gt;
===Setup 2===&lt;br /&gt;
&lt;br /&gt;
====Core====&lt;/div&gt;</summary>
		<author><name>Ihas</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Ihas&amp;diff=15196</id>
		<title>User:Ihas</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Ihas&amp;diff=15196"/>
		<updated>2008-08-08T01:57:27Z</updated>

		<summary type="html">&lt;p&gt;Ihas: /* Our Hardware */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[category:User Setups]] &lt;br /&gt;
==About Us==&lt;br /&gt;
&lt;br /&gt;
ihas (Innovative Home Automation Systems) is a company in Perth, Western Australia specialising in Home Automation solutions for the Australian market.&lt;br /&gt;
&lt;br /&gt;
We have been active in the IT industry for several years, and also operate a VoIP provider with PSTN interconnect capabilities.  We started investigating LinuxMCE for our own use in 2007 and when we realised that working setups were something we could sell, we formed ihas and began building and selling LinuxMCE solutions.&lt;br /&gt;
&lt;br /&gt;
Together our staff have over 30 years&#039; experience in the IT industry, most of that with Linux.&lt;br /&gt;
&lt;br /&gt;
==Our Hardware==&lt;br /&gt;
&lt;br /&gt;
We have a number of clients &#039;out there&#039; using LinuxMCE in their homes and businesses.&lt;br /&gt;
&lt;br /&gt;
All our systems are built using quality hardware which we have tested in operation in our own workshop.  If we can&#039;t make it work, it doesn&#039;t get used.&lt;br /&gt;
&lt;br /&gt;
===Setup 1===&lt;br /&gt;
&lt;br /&gt;
This first system is a home customer.&lt;br /&gt;
&lt;br /&gt;
====Core====&lt;br /&gt;
&lt;br /&gt;
Hybrid/Core&lt;br /&gt;
&lt;br /&gt;
* Intel Core 2 Quad CPU 2.4 GHz&lt;br /&gt;
* MSI Mainboard&lt;br /&gt;
* 2 G RAM&lt;br /&gt;
* Maxtor STM 325082 250G SATA-II Hard Drive (for boot)&lt;br /&gt;
* Seagate ST3500630AS 500G SATA-II Hard Drive (for storage)&lt;br /&gt;
* LG GH20NS10 DVD-RAM&lt;br /&gt;
* Nova-T-500 Dual DVB-T Tuner card&lt;br /&gt;
&lt;br /&gt;
====MDs====&lt;br /&gt;
&lt;br /&gt;
* 2 x MSI MediaLive! Barebones&lt;br /&gt;
&lt;br /&gt;
====Phones====&lt;br /&gt;
&lt;br /&gt;
* Cisco 7970G IP Phone&lt;br /&gt;
&lt;br /&gt;
===Setup 2===&lt;br /&gt;
&lt;br /&gt;
====Core====&lt;/div&gt;</summary>
		<author><name>Ihas</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Ihas&amp;diff=15195</id>
		<title>User:Ihas</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Ihas&amp;diff=15195"/>
		<updated>2008-08-08T01:55:56Z</updated>

		<summary type="html">&lt;p&gt;Ihas: /* Our Hardware */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[category:User Setups]] &lt;br /&gt;
==About Us==&lt;br /&gt;
&lt;br /&gt;
ihas (Innovative Home Automation Systems) is a company in Perth, Western Australia specialising in Home Automation solutions for the Australian market.&lt;br /&gt;
&lt;br /&gt;
We have been active in the IT industry for several years, and also operate a VoIP provider with PSTN interconnect capabilities.  We started investigating LinuxMCE for our own use in 2007 and when we realised that working setups were something we could sell, we formed ihas and began building and selling LinuxMCE solutions.&lt;br /&gt;
&lt;br /&gt;
Together our staff have over 30 years&#039; experience in the IT industry, most of that with Linux.&lt;br /&gt;
&lt;br /&gt;
==Our Hardware==&lt;br /&gt;
&lt;br /&gt;
We have a number of clients &#039;out there&#039; using LinuxMCE in their homes and businesses.&lt;br /&gt;
&lt;br /&gt;
===Setup 1===&lt;br /&gt;
&lt;br /&gt;
This first system is a home customer.&lt;br /&gt;
&lt;br /&gt;
====Core====&lt;br /&gt;
&lt;br /&gt;
Hybrid/Core&lt;br /&gt;
&lt;br /&gt;
* Intel Core 2 Quad CPU 2.4 GHz&lt;br /&gt;
* MSI Mainboard&lt;br /&gt;
* 2 G RAM&lt;br /&gt;
* Maxtor STM 325082 250G SATA-II Hard Drive (for boot)&lt;br /&gt;
* Seagate ST3500630AS 500G SATA-II Hard Drive (for storage)&lt;br /&gt;
* LG GH20NS10 DVD-RAM&lt;br /&gt;
* Nova-T-500 Dual DVB-T Tuner card&lt;br /&gt;
&lt;br /&gt;
====MDs====&lt;br /&gt;
&lt;br /&gt;
* 2 x MSI MediaLive! Barebones&lt;br /&gt;
&lt;br /&gt;
====Phones====&lt;br /&gt;
&lt;br /&gt;
* Cisco 7970G IP Phone&lt;br /&gt;
&lt;br /&gt;
===Setup 2===&lt;br /&gt;
&lt;br /&gt;
====Core====&lt;/div&gt;</summary>
		<author><name>Ihas</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Ihas&amp;diff=15194</id>
		<title>User:Ihas</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Ihas&amp;diff=15194"/>
		<updated>2008-08-08T01:54:00Z</updated>

		<summary type="html">&lt;p&gt;Ihas: /* Core */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[category:User Setups]] &lt;br /&gt;
==About Us==&lt;br /&gt;
&lt;br /&gt;
ihas (Innovative Home Automation Systems) is a company in Perth, Western Australia specialising in Home Automation solutions for the Australian market.&lt;br /&gt;
&lt;br /&gt;
We have been active in the IT industry for several years, and also operate a VoIP provider with PSTN interconnect capabilities.  We started investigating LinuxMCE for our own use in 2007 and when we realised that working setups were something we could sell, we formed ihas and began building and selling LinuxMCE solutions.&lt;br /&gt;
&lt;br /&gt;
Together our staff have over 30 years&#039; experience in the IT industry, most of that with Linux.&lt;br /&gt;
&lt;br /&gt;
==Our Hardware==&lt;br /&gt;
&lt;br /&gt;
We have a number of clients &#039;out there&#039; using LinuxMCE in their homes and businesses.&lt;br /&gt;
&lt;br /&gt;
===Setup 1===&lt;br /&gt;
&lt;br /&gt;
This first system is a home customer.&lt;br /&gt;
&lt;br /&gt;
====Core====&lt;br /&gt;
&lt;br /&gt;
Hybrid/Core&lt;br /&gt;
&lt;br /&gt;
* Intel Core 2 Quad CPU 2.4 GHz&lt;br /&gt;
* MSI Mainboard&lt;br /&gt;
* 2 G RAM&lt;br /&gt;
* Maxtor STM 325082 250G SATA-II Hard Drive (for boot)&lt;br /&gt;
* Seagate ST3500630AS 500G SATA-II Hard Drive (for storage)&lt;br /&gt;
* LG GH20NS10 DVD-RAM&lt;br /&gt;
* Nova-T-500 Dual DVB-T Tuner card&lt;br /&gt;
&lt;br /&gt;
====MDs====&lt;br /&gt;
&lt;br /&gt;
* 2 x MSI MediaLive! Barebones&lt;br /&gt;
&lt;br /&gt;
====Phones====&lt;br /&gt;
&lt;br /&gt;
* Cisco 7970G IP Phone&lt;/div&gt;</summary>
		<author><name>Ihas</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Ihas&amp;diff=15193</id>
		<title>User:Ihas</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Ihas&amp;diff=15193"/>
		<updated>2008-08-08T01:52:35Z</updated>

		<summary type="html">&lt;p&gt;Ihas: /* Our Hardware */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[category:User Setups]] &lt;br /&gt;
==About Us==&lt;br /&gt;
&lt;br /&gt;
ihas (Innovative Home Automation Systems) is a company in Perth, Western Australia specialising in Home Automation solutions for the Australian market.&lt;br /&gt;
&lt;br /&gt;
We have been active in the IT industry for several years, and also operate a VoIP provider with PSTN interconnect capabilities.  We started investigating LinuxMCE for our own use in 2007 and when we realised that working setups were something we could sell, we formed ihas and began building and selling LinuxMCE solutions.&lt;br /&gt;
&lt;br /&gt;
Together our staff have over 30 years&#039; experience in the IT industry, most of that with Linux.&lt;br /&gt;
&lt;br /&gt;
==Our Hardware==&lt;br /&gt;
&lt;br /&gt;
We have a number of clients &#039;out there&#039; using LinuxMCE in their homes and businesses.&lt;br /&gt;
&lt;br /&gt;
===Core===&lt;br /&gt;
&lt;br /&gt;
Hybrid/Core&lt;br /&gt;
&lt;br /&gt;
* Intel Core 2 Quad CPU 2.4 GHz&lt;br /&gt;
* MSI Mainboard&lt;br /&gt;
* 2 G RAM&lt;br /&gt;
* Maxtor STM 325082 250G SATA-II Hard Drive (for boot)&lt;br /&gt;
* Seagate ST3500630AS 500G SATA-II Hard Drive (for storage)&lt;br /&gt;
* LG GH20NS10 DVD-RAM&lt;br /&gt;
* Nova-T-500 Dual DVB-T Tuner card&lt;br /&gt;
&lt;br /&gt;
MDs&lt;br /&gt;
&lt;br /&gt;
* 2 x MSI MediaLive! Barebones&lt;br /&gt;
&lt;br /&gt;
Phone&lt;br /&gt;
&lt;br /&gt;
* Cisco 7970G IP Phone&lt;/div&gt;</summary>
		<author><name>Ihas</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Ihas&amp;diff=15192</id>
		<title>User:Ihas</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Ihas&amp;diff=15192"/>
		<updated>2008-08-08T01:20:40Z</updated>

		<summary type="html">&lt;p&gt;Ihas: /* About Us */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[category:User Setups]] &lt;br /&gt;
==About Us==&lt;br /&gt;
&lt;br /&gt;
ihas (Innovative Home Automation Systems) is a company in Perth, Western Australia specialising in Home Automation solutions for the Australian market.&lt;br /&gt;
&lt;br /&gt;
We have been active in the IT industry for several years, and also operate a VoIP provider with PSTN interconnect capabilities.  We started investigating LinuxMCE for our own use in 2007 and when we realised that working setups were something we could sell, we formed ihas and began building and selling LinuxMCE solutions.&lt;br /&gt;
&lt;br /&gt;
Together our staff have over 30 years&#039; experience in the IT industry, most of that with Linux.&lt;br /&gt;
&lt;br /&gt;
==Our Hardware==&lt;br /&gt;
&lt;br /&gt;
We have a number of clients &#039;out there&#039; using LinuxMCE in their homes and businesses.&lt;/div&gt;</summary>
		<author><name>Ihas</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Ihas&amp;diff=15191</id>
		<title>User:Ihas</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Ihas&amp;diff=15191"/>
		<updated>2008-08-08T00:57:07Z</updated>

		<summary type="html">&lt;p&gt;Ihas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[category:User Setups]] &lt;br /&gt;
==About Us==&lt;br /&gt;
&lt;br /&gt;
ihas is a company in Perth, Western Australia specialising in Home Automation solutions for the Australian market.&lt;br /&gt;
&lt;br /&gt;
We have been active in the IT industry for several years, and also operate a VoIP provider with PSTN interconnect capabilities.&lt;br /&gt;
&lt;br /&gt;
Together our staff have over 30 years&#039; experience in the IT industry, most of that with Linux.&lt;/div&gt;</summary>
		<author><name>Ihas</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=MSI_Media_Live_Barebone&amp;diff=15111</id>
		<title>MSI Media Live Barebone</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=MSI_Media_Live_Barebone&amp;diff=15111"/>
		<updated>2008-07-29T02:57:00Z</updated>

		<summary type="html">&lt;p&gt;Ihas: /* VFD Front Panel Display */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Hardware]]&lt;br /&gt;
[[Category: Barebones]]&lt;br /&gt;
&lt;br /&gt;
[[Image: MSI_MediaLive-front.jpg|thumb|200px|MSI Media Live Barebone]]&lt;br /&gt;
=MSI Media Live Barebone=&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== About ===&lt;br /&gt;
Barebone from MSI with the MSI Media Live Motherboard (7329)&lt;br /&gt;
&lt;br /&gt;
=VFD Front Panel Display=&lt;br /&gt;
To get this working, you will need to do the following&lt;br /&gt;
*log into the webadmin at http://dcerouter/pluto-admin/&lt;br /&gt;
*In the left hand menu frame scroll to the bottom and select &amp;quot;Show Device Tree&amp;quot;. Now click the &#039;+&#039; next to the name of your MSI Media Live MD to expand the list to display its devices. You should now see an item called &amp;quot;Media Live LCD/Buttons&amp;quot;. Click on this item.&lt;br /&gt;
*You will now see the Device Template for the &amp;quot;Media Live LCD/Buttons&amp;quot; displayed in the right hand frame.&lt;br /&gt;
*In the line in the device template labeled &amp;quot;Device Template&amp;quot; you will see a green button named &amp;quot;View&amp;quot;... Click this to view/edit the device template #1860 for the &amp;quot;Media Live LCD/Buttons&amp;quot;.&lt;br /&gt;
*A new window will open to display the device template #1860.&lt;br /&gt;
** On the 2nd line of the device template you will see &#039;Implements DCE&#039; - tick this.&lt;br /&gt;
** Now in the &#039;Command Line&#039; field enter &amp;quot;Media_Live_LCDButtons&amp;quot; &#039;&#039;&#039;**make sure there are no typos in this string**&#039;&#039;&#039;&lt;br /&gt;
** Scroll to the bottom of the window and click &#039;Save&#039; and then close the window.&lt;br /&gt;
** Now restart your media director to have the template changes take effect.&lt;br /&gt;
*Once the MD has booted and you are back in the Orbiter your MSI Media Live VFD should be illuminated and displaying the date/time.&lt;br /&gt;
*Try playing some audio/video and watch the VFD display as you navigate an play content - all of which will be reflected in the display.&lt;br /&gt;
*If your a VDR user you will see channel name and EPG data displayed for the live picture.&lt;br /&gt;
*also has been test in mythtv and it works the same as VDR &lt;br /&gt;
&lt;br /&gt;
Thanks to Thom and Gbutters&lt;br /&gt;
Reference: http://forum.linuxmce.org/index.php?topic=5849.0&lt;br /&gt;
== Links ==&lt;br /&gt;
[http://www.msicomputer.com/product/p_spec.asp?model=Media_Live&amp;amp;class=npc]&lt;/div&gt;</summary>
		<author><name>Ihas</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Ihas&amp;diff=14983</id>
		<title>User:Ihas</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Ihas&amp;diff=14983"/>
		<updated>2008-07-17T08:13:59Z</updated>

		<summary type="html">&lt;p&gt;Ihas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[category:User Setups]] &lt;br /&gt;
&lt;br /&gt;
Comming Soon &lt;br /&gt;
www.ihas.com.au&lt;/div&gt;</summary>
		<author><name>Ihas</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Ihas&amp;diff=14982</id>
		<title>User:Ihas</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Ihas&amp;diff=14982"/>
		<updated>2008-07-17T08:08:54Z</updated>

		<summary type="html">&lt;p&gt;Ihas: New page: Comming Soon  www.ihas.com.au&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Comming Soon &lt;br /&gt;
www.ihas.com.au&lt;/div&gt;</summary>
		<author><name>Ihas</name></author>
	</entry>
</feed>