LinuxMCE - User contributions [en]

LinuxMCE-0810 alpha2

2009-05-22T03:21:38Z

Cylon7: /* nVidia Restricted Driver */

{| align="right"
| __TOC__
|}

==Installation==
# Install Kubuntu Intrepid, update it and enable the restricted (video) drivers if needed. (download Kubuntu 8.10 release from one of these: [http://mirrors.ccs.neu.edu/releases.ubuntu.com/kubuntu/8.10/ Northeastern University Mirror, USA], [http://swtsrv.informatik.uni-mannheim.de/pub/linux/distributions/ubuntu-release/kubuntu/8.10/ Mannheim University Mirror, Germany]) '''Currently, only the 32bit version of LinuxMCE is available. Only download the i386 version of 8.10 Kubuntu, even if your system can support 64bit versions.'''
# Run aptitude update and aptitude dist-upgrade to get the latest Kubuntu updates.
# Grab the latest installer script from [http://deb.linuxmce.org/ubuntu here], unpack them and change into the freshly created ''new-installer'' directory.
# Run the following scripts (as root, in order): pre-install-from-repo.sh, mce-install.sh, post-install.sh.
# Reboot, wait for the activity to stop (see progress on console 8).

In other words, after installing Kubuntu and upgrading it etcetera:
sudo su - #This might ask for the password you specified earlier during the install of kubuntu.
wget -c http://deb.linuxmce.org/ubuntu/new-installer-alpha-latest.tar.gz
tar xvf new-installer-alpha-latest.tar.gz
cd new-installer
./pre-install-from-repo.sh
./mce-install.sh
./post-install.sh
reboot
=== nVidia Restricted Driver ===
<strike>Install the nVidia restricted driver (177) from KDE using the Hardware Manager ''before'' installing LinuxMCE 0810 Alpha for the best results</strike> The installer will now automatically choose and install the correct restricted driver during setup.

=== MythTV ===
<strike>Remove reference to hardy in /etc/apt/sources.list

from terminal
<pre>
sudo apt-get install pluto-mythtv-player
</pre>

Install updated version of pluto-mythtv-plugin</strike>

=== Setup Diskless MD ===
<strike>Follow the steps from [[LinuxMCE-0810_alpha1#Setup_Diskless_MD|alpha1]].</strike>

=== Upgrading kernel ===
<strike>There are issues with the ''fglrx'' driver that are documented in Ubuntu's bug tracking system. If you're experiencing those issues, upgrade the kernel to ''2.6.27-13'' or better. [[Upgrading the Kernel]] has been updated with instructions on doing this.</strike> The latest official kernel is -14

== Updates ==
Check if there is no junk like references to hardy in /etc/apt/sources.list then:
sudo apt-get update
sudo apt-get dist-upgrade
Or use a package manager on the KDE desktop for more convenience.

=== 20090218 (alpha-2.1) ===
*lmce-datalog-db_2.0.0.44.0902180810
*lmce-datalogger-plugin_2.0.0.44.0902180810
*lmce-enocean-tcm120_2.0.0.44.0902180810
*lmce-src-datalogger-plugin_2.0.0.44.0902180810
*lmce-src-enocean-tcm120_2.0.0.44.0902180810
*lmce-src-lmce-datalog_2.0.0.44.0902180810
*pluto-dcerouter_2.0.0.44.0902180810
*pluto-dhcpd-plugin_2.0.0.44.0902180810
*pluto-hald-src_2.0.0.44.0902180810
*pluto-hald_2.0.0.44.0902180810
*pluto-mythtv-plugin_2.0.0.44.0902180810
*pluto-orbitergen_2.0.0.44.0902180810
*pluto-src-dcerouter_2.0.0.44.0902180810
*pluto-src-hal-device-finder_2.0.0.44.0902180810
*pluto-src-mythtv-plugin_2.0.0.44.0902180810
*pluto-src-orbitergen_2.0.0.44.0902180810
*pluto-src-updatemedia_2.0.0.44.0902180810
*pluto-updateentarea_2.0.0.44.0902180810
*pluto-updatemedia_2.0.0.44.0902180810
*pluto-zwave-lighting_2.0.0.44.0902180810
*lmce-game-player_2.0.0.44.0902180810
*lmce-game-plugin_2.0.0.44.0902180810
*lmce-src-game-player_2.0.0.44.0902180810
*lmce-src-game-plugin_2.0.0.44.0902180810

==== 20090222 (alpha-2.1.1) ====
*pluto-dcerouter_2.0.0.44.0902220810
*pluto-bluetooth-dongle_2.0.0.44.0902220810

=== 20090301 (alpha-2.2) ===
SVN revision: 21746

To avoid a known problem when upgrading pluto-storage-devices, forcefully remove it before upgrading and let apt fix it:
dpkg -r --force-all pluto-storage-devices
apt-get update
apt-get install -f
Also please note that installing the upgrade of pluto-system-database will OVERWRITE your existing pluto_main database. It is therefore advisable to make a backup first!
mysqldump --skip-extended-insert pluto_main >pluto_main_$PK_Installation-`date '+%Y%m%d:%H%M%S'`.sql
*pluto-boot-scripts_2.0.0.44.0903010810
*pluto-network-storage_2.0.0.44.0903010810
*pluto-skins-basic_2.0.0.44.0903010810
*pluto-src-network-storage_2.0.0.44.0903010810
*pluto-src-std-plugins_2.0.0.44.0903010810
*pluto-src-updatemedia_2.0.0.44.0903010810
*pluto-std-plugins_2.0.0.44.0903010810
*pluto-storage-devices_2.0.0.44.0903010810
*pluto-system-database_2.0.0.44.0903010810
*pluto-updatemedia_2.0.0.44.0903010810
*pluto-website-admin_2.0.0.44.0903010810

=== 20090308 (alpha-2.3) ===
SVN revision: 21765

Again it is wise to backup your database as there is a new pluto-system-database package, but this one will not overwrite your pluto_main database if it is already installed, it should do an sqlCVS update instead.
Also remove the pluto-storage-devices, hopefully for the last time.
See the previous upgrade [[LinuxMCE-0810_alpha2#20090301_.28alpha-2.2.29|above]] for details on how to do these things.

*pluto-asterisk_2.0.0.44.0903080810
*pluto-src-asterisk_2.0.0.44.0903080810
*pluto-src-text-to-speech_2.0.0.44.0903080810
*pluto-src-updatemedia_2.0.0.44.0903080810
*pluto-storage-devices_2.0.0.44.0903080810
*pluto-system-database_2.0.0.44.0903080810
*pluto-text-to-speech_2.0.0.44.0903080810
*pluto-updatemedia_2.0.0.44.0903080810
*pluto-website-admin_2.0.0.44.0903080810

=== 20090315 (alpha-2.4) ===
SVN revision: 21798

The web admin is being moved from pluto-admin to lmce-admin with this build. A redirect has been placed in pluto-admin to redirect to the new web admin URL to help smooth the transition. While every attempt has been made to make this a smooth transition, please be sure to file a trac ticket if you find bugs related to this move so I can get them taken care of - [[User:jondecker76|jondecker76]]

The Asterisk IVR is broken in this release. For those that need to get it working/wish to try out new changes, do the following:
sudo apt-get install libsox-fmt-all
cd /usr/pluto/bin
sudo rm generate_users_voicemenu.pl
sudo wget http://svn.linuxmce.org/trac.cgi/browser/branches/LinuxMCE-0810/src/Asterisk/generate_users_voicemenu.pl?format=raw
sudo chmod 755 generate_users_voicemenu.pl
sudo ./generate_users_voicemenu.pl
Be sure to have the default voice set up in the Text_To_Speech device's device data (its default is the ugly one we're already used to)! I also highly recommend following the instructions located at [http://wiki.linuxmce.org/index.php/Text_To_Speech http://wiki.linuxmce.org/index.php/Text_To_Speech] on how to install some better voices, and set the default voice to voice_nitech_us_slt_arctic_hts after you install the better voices (this is the best free voice available ATM). This should all work on next weeks build for those that can wait.. I'm still working on getting the better voices included by default, but need to check on licensing issues first.

*pluto-asterisk_2.0.0.44.0903150810
*pluto-boot-scripts_2.0.0.44.0903150810
*pluto-makerelease_2.0.0.44.0903150810
*pluto-newmdinteractor_2.0.0.44.0903150810
*pluto-orbitergen_2.0.0.44.0903150810
*pluto-proxy-orbiter_2.0.0.44.0903150810
*pluto-src-asterisk_2.0.0.44.0903150810
*pluto-src-makerelease_2.0.0.44.0903150810
*pluto-src-newmdinteractor_2.0.0.44.0903150810
*pluto-src-orbitergen_2.0.0.44.0903150810
*pluto-src-proxy-orbiter_2.0.0.44.0903150810
*pluto-src-std-plugins_2.0.0.44.0903150810
*pluto-src-text-to-speech_2.0.0.44.0903150810
*pluto-std-plugins_2.0.0.44.0903150810
*pluto-system-database_2.0.0.44.0903150810
*pluto-text-to-speech_2.0.0.44.0903150810
*pluto-updateentarea_2.0.0.44.0903150810
*pluto-website-admin_2.0.0.44.0903150810

=== 20090322 (alpha-2.5) ===
SVN revision: 21827

*freepbx_0+2.3.1-2
*pluto-asterisk_2.0.0.44.0903220810
*pluto-dhcpd-plugin_2.0.0.44.0903220810
*pluto-install-scripts_2.0.0.44.0903220810
*pluto-raid-tools_2.0.0.44.0903220810
*pluto-skins-basic_2.0.0.44.0903220810
*pluto-src-asterisk_2.0.0.44.0903220810
*pluto-website-admin_2.0.0.44.0903220810

=== 20090401 (alpha-2.6) ===
Note: This build will attempt to use Launch Manager to co-ordinate startup and shutdown of devices. While it is not 100% finished, it is working and stable. Please test it out and file any problems against trac ticket #48. Also, please note the following:
I'm not sure on this, but you may have to manually install LM via apt-get
After you upgrade, reboot your core
CLI output of LM can be viewed on tty8 on the core, and tty1 on MD's (alt+ctrl+F8 and alt+ctrl+F1 respectively). You will have to manually switch back to the orbiter on tty7 when finished
CLI output is not yet completely finished, so the top fields will be blank (this is normal for now)
CLI output of the log messages is working however, so please take a peek at them on tty8/tty1 shortly after you hear the 2nd set of beeps on boot up (when the "x" cursor appears on the screen).
You can further test out LM by switching to tty8/tty1 right after doing a router reload and watching the output and comparing it to what you would expect it to be.
LM dos not yet track regen process and report the % done. This should be working in next week's build, however.
If there are problems and/or you wish to restore previous functionality, the original /usr/pluto/bin/startCore.sh file can be restored from the backup /usr/pluto/bin/startCore.sh._backup, and the LM package removed
LM is not yet properly daemonized. I'm saving this step for last after the socket layer is implemented and we get a client coded.
'''Note:''' All orbiters will likely do a FULL REGEN after this update, and it may appear that your system is hanging because of this. Please give it some time to finish the regen (could take up to an hour on large installs)

* lmcevdr_1.1-10_all.deb
* pluto-website-admin_2.0.0.44.0904010019_i386.deb
* pluto-dynamic-dns_2.0.0.44.0904010019_i386.deb
* lmce-launch-manager_2.0.0.44.0904010019_i386.deb
* pluto-boot-scripts_2.0.0.44.0904010019_i386.deb
* pluto-system-database_2.0.0.44.0904010019_i386.deb
* pluto-orbitergen_2.0.0.44.0904010019_i386.deb
* pluto-updateentarea_2.0.0.44.0904010019_i386.deb
* pluto-orbiter_2.0.0.44.0904010019_i386.deb

=== 20090405 (alpha 2.7) ===
From now on, the SVN version will part of the deb name.
You may need to uninstall 'lmcevdr' (dpkg -r --force-all lmcevdr) and reinstall it (apt-get install lmcevdr) to get around the install-script bug in last weeks .deb package. It worked for me.
* lmce-game-player_2.0.0.44.090405.21873_i386.deb
* lmce-game-plugin_2.0.0.44.090405.21873_i386.deb
* lmce-launch-manager_2.0.0.44.090405.21873_i386.deb
* lmce-phoenix-solo-usb_2.0.0.44.090405.21873_i386.deb
* lmcevdr_1.1-10_all.deb (This is no main package, and therefore does not contain the regular version designation. It is based upon version 21875)
* pluto-bluetooth-dongle_2.0.0.44.090405.21873_i386.deb
* pluto-simplephone_2.0.0.44.090405.21873_i386.deb
* pluto-system-database_2.0.0.44.090405.21873_i386.deb
* pluto-website-admin_2.0.0.44.09040521873_i386.deb

=== 20090412 (alpha 2.8) ===
* pluto-text-to-speech_2.0.0.44.09041221886_i386.deb (283,284) - Finally, good voices will actually install (Nitech HTS Arctic).
* pluto-system-database_2.0.0.44.09041221886_i386.deb (211) - New default voice is voice_nitech_us_slt_arctic_hts. - game plugin and player template cleanups
* mce-diskless-tools_2.0.0.44.09041221886_i386.deb (627,628) - Update kernel image for diskless MDs upon regenning.
* pluto-website-admin_2.0.0.44.09041221886_i386.deb (220) - Infrared codes will now properly come from schema.linuxmce.org
* pluto-boot-scripts_2.0.0.44.09041221886_i386.deb (234)- also schema.linuxmce.org IR codes related.
* pluto-motion-wrapper_2.0.0.44.09041221886_i386.deb (455,456) - changed config variable from ffmpeg_filename to movie_filename
* lmce_launch_manager_2.0.0.44.09041221886_i386.deb (298,299) - LM Actions now work from CLI(such as reload, regen, reboot, etc...)
* lmce-game-player_2.0.0.44.09041221886_i386.deb (673,674) - Rebuilt for new device template
* lmce-game-plugin_2.0.0.44.09041221886_i386.deb (671,672) - Rebuilt for new device template
* pluto-updateentarea_2.0.0.44.09041221886_i386.deb (341,342) - may need to be rebuilt for device template changes

=== 20090413 (alpha 2.9 jondecker special) ===
* pluto-text-to-speech_2.0.0.44.09041321887_i386.deb (283,284) - fixes stupid post-install typo
* pluto-zwave-lighting_2.0.0.44.09041321891_i386.deb (505,506) - thermostate support

=== 20090419 (alpha 2.10 pbr) ===
* pluto-text-to-speech_2.0.0.44.09041921897_i386.deb
* pluto-website-admin_2.0.0.44.09041921897_i386.deb
* lmce-screen-capture-camera_2.0.0.44.09041921897_i386.deb
* pluto-system-database_2.0.0.44.09041921897_i386.deb
* lmce-game-plugin_2.0.0.44.09041921897_i386.deb
* lmce-game-player_2.0.0.44.09041921897_i386.deb
* pluto-asterisk_2.0.0.44.09041921897_i386.deb

=== 20090426 (alpha 2.11) ===
With this release, MythTV now takes advantage of storage groups. Do some recordings, and try recording to a few different storage groups.
Please test this out and report any problems such as duplicate attributes appearing in pluto_media, icon image not showing up, recordings failing to record, etc. Also, if you do have problems, try a reboot and see if it fixes the problem, then please let me know if the reboot fixed your problem. - jondecker76

'''POST-BUILD UPDATE:''' A couple of small bugs have been found that will be fixed in next week's build. 1) Some storage groups are missing the leading "/" in the path, causing problems images in mythweb, downloads in the mythweb, etc. 2) Unmounted storage devices were being skipped. This means that you may not have a storage group for some of your devices at some times. I am changing this so that the storage groups are created, and if for some reason it is not available when a recording is set to use the storage group, then the recording will go to the (always present) Default storage group.
For those wanting to fix #1 right now, just edit /usr/pluto/bin/StorageDevices_PlutoDirStructure.sh and add a preceeding slash before the path beginning with 'home/....' on lines 214 and 226. After this modification, MythTV works great in all of the storage groups! (You should do a reboot after making the change)

* lmcevdr_1.1-10_all.deb - more setup fixes, this time for the MD
* pluto-boot-scripts_2.0.0.44.09042621919_i386.deb (234) - small fix to get rid of a warning on DCERouter startup re missing dir., New MythTV directory structure stuff
* pluto-asterisk_2.0.0.44.09042621919_i386.deb (270,271) - Added Support for Cisco 7910 phone
* pluto-dhcpd-plugin_2.0.0.44.09042621919_i386.deb (302) - Added support for Cisco 7910 phone
* pluto-system-database_2.0.0.44.09042621919_i386.deb (211) - '''If new devices are added, the pluto-system-database needs to be updates as well'''
* pluto-storage-devices_2.0.0.44.09042621919_i386.deb (533) - Adds new tv_shows_* directories. Generates MythTV storage groups
* pluto-std-plugins_2.0.0.44.09042621919_i386.deb (134,153) - adds some useful debugging snippets that helped trace down the problem of mythtv attributes not adding to pluto_media
* pluto-mythtv-plugin_2.0.0.44.09042621919_i386.deb (134,153) - lots of changes to facilitate the new storage groups
* pluto-network-storage_2.0.0.44.09042621919_i386.deb (503,508) - small changes to work with new tv_shows_* directories

=== 20090429 (alpha 2.12) ===
* pluto-storage-devices_2.0.0.44.09042921929_i386.deb (533) - Fixes some small bugs in MythTV storage groups
* pluto-boot-scripts_2.0.0.44.09042921929_i386.deb (234) - misc. MythTV storage group enhancements
* pluto-mythtv-plugin_2.0.0.44.09042921929_i386.deb (134,153) - misc. MythTV storage group enhancement
* mce-diskless-tools_2.0.0.44.09042921929_i386.changes (627,628) - lots of fixes for MD boot- Changes effect new installs only
* pluto-system-database_2.0.0.44.09042921929_i386.deb (211) - Fixes hardy issue in sources.list
* pluto-nvidia-video-drivers_2.0.0.44.09042921929_i386.deb (490) - changed the package requirement to nvidia-glx-180 for intrepid

=== 20090501 (alpha 2.13) ===
There are a few more MythTV storage group changes in this build. Please understand that the storage group name changes may throw mythweb out of whack on some old recordings, but this should be minimal. The old "user_*/<storage_device>" naming scheme is replaced with a "<username>:<storage_device>" naming convention. This will appeal to many more users than the user_* convention. Also, there is now support for custom storage groups. You can make your own storage groups now on top of the auto-generated LMCE ones by prepending with "custom:" (for example, you may make a new storage group named "custom:MyDrive", and it will not be removed or overwritten by the scripts that generate the storage groups). One last change is in the "Default" storage group - it no longer points to the drive with most space. This was changed because eventually it would throw mythweb for a loop once the paths changed. I will look into a better way to defaultly record to the drive with most space, most likely using recording profiles.

* lmce-launch-manager (298,299) - db wrapper fix to handle empty resultsets
* pluto-bluetooth-dongle (124,143) - fix some connection issues in JavaMO
* pluto-mythtv-plugin (134,153)
* pluto-storage-devices (533)
* pluto-boot-scripts (234) - MD fixes
* mce-diskless-tools (391) - MD fixes
* pluto-install-scripts (627,628) - MD fixes
* pluto-x-scripts (520,523) - AV Wizard fix for MD
* pluto-zwave-lighting (505,506) - Init speedup

=== 20090503 (alpha2.14) ===
* pluto-zwave-lighting_2.0.0.44.09050321942_i386.deb (505,506) - boolean fixes

=== 20090505 (alpha2.15) ===
KDE on the MD should work now. The first boot of the system after the update will take a bit longer, as stuff that has not worked, is now being executed for the first time.

* mce-diskless-tools_2.0.0.44.09050521951_i386.deb (627,628) - Lots of small fixes
* pluto-system-database_2.0.0.44.09050521951_i386.deb (211) - More hardy extinction
* pluto-boot-scripts_2.0.0.44.09050521951_i386.deb (234) - Small bug with regards to MySQL authorization fixed, which results in a running KDE on the MD, again.

=== 20090505 (alpha2.16 snafu fix) ===
* pluto-boot-scripts_2.0.0.44.09050521958_i386.deb (234) - snafu causing weird things and corruption on updates

=== 20090506 (alpha2.17) ===
* pluto-asterisk_2.0.0.44.09050621962_i386.deb (270,271) - Additional australian provider in the web admin (VoIPWA) and some janitory work.
* pluto-boot-scripts_2.0.0.44.09050621962_i386.deb (234) - Additional visual feedback during the first boot, after running the AV Wizard

=== 20090507 (alpha2.18)===
* pluto-dhcpd-plugin_2.0.0.44.09050721973_i386.deb (302) - Pnp script for Cisco 7910, aastra (aastra still needs a device template)
* lmce-launch-manager_2.0.0.44.09050721973_i386.deb (298,299) - Launch manager is now started in its own screen session
* pluto-system-database_2.0.0.44.09050721973_i386.deb (211) - Removal of X Client Data as a dependency
* pluto-mythtv-plugin_2.0.0.44.09050721973_i386.deb (134,153) - small changes to keep backend in sync
* pluto-storage-devices_2.0.0.44.09050721973_i386.deb (533) - Updates the Default and LiveTV storage groups so they use the drive with most space
* pluto-boot-scripts_2.0.0.44.09050721973_i386.deb (234) - Better detection of Intel Mobile Graphics adapter

=== 20090511 (alpha2.19) ===
* lmcevdr - more VDR configuration settings
* pluto-boot-scripts_2.0.0.44.09051121983_i386.deb (234) - Another KDE Desktop on MD fix
* mce-diskless-tools_2.0.0.44.09051121984_i386.deb (627,628) - Be agnostic about the compression format of tar archives, and more forgiving on download problems

=== 20090515 (alpha2.20) ===
* lmcevdr_1.1-10_all.deb - more VDR configuration settings
* pluto-system-database_2.0.0.44.09051522002_i386.deb (211) - Additional package definitions (vdr-plugin-streamdev-server and vdr-plugin-streamdev-client)
* pluto-hald_2.0.0.44.09051522002_i386.deb (529,530) - USB detection, better MCE2 support
* pluto-vdr-plugin_2.0.0.44.09051522002_i386.deb (466,467) - Additional dependency for pluto-vdr-plugin to vdr-plugin-streamdev-server
* lmce-launch-manager_2.0.0.44.09051522002_i386.deb (298,299) - Prompt user for reload after new MD creation (Requires manual re-run of Diskless_CreateTBZ.sh)
* pluto-orbiter_2.0.0.44.09051522002_i386.deb (119,138) - Prompt user for reload after new MD creation (Requires manual re-run of Diskless_CreateTBZ.sh)
* pluto-storage-devices_2.0.0.44.09051522003_i386.deb (533) - some small MythTV storage group tweaks
* pluto-slim-server-streamer_2.0.0.44.09051522002_i386.deb (289,290) - changes to the configuraton script to start squeezecenter instead of slimserver
* pluto-website-admin_2.0.0.44.09051522002_i386.deb (220) - Screen Saver section fixed
* pluto-plutoutils_2.0.0.44.09051522002_i386.deb (197,196) - fix FileUtils::ReadURL method
* pluto-std-plugins_2.0.0.44.09051522002_i386.deb (116,135) - support for external media in conjunction with playlists

=== 20090520 (alpha2.21) ===
* pluto-website-admin_2.0.0.44.09052022008_i386.deb (220) - GSD/IR code update fixes

=== 20090524 (upcoming ...) ===
* pluto-system-database (211) - More VDR related changes in the package definitions.

== Previous alpha releases ==
* Notes about [[LinuxMCE-0810 alpha1]]
* Notes about [[LinuxMCE-0810 alpha0]]

LinuxMCE-0810 alpha2

2009-04-24T11:39:58Z

Cylon7: /* Upgrading kernel */ typo

{| align="right"
| __TOC__
|}

==Installation==
# Install Kubuntu Intrepid, update it and enable the restricted (video) drivers if needed. ([http://www.kubuntu.org/getkubuntu/download download Kubuntu 8.10 release])
# Run aptitude update and aptitude dist-upgrade to get the latest Kubuntu updates.
# Grab the latest installer script from [http://deb.linuxmce.org/ubuntu here], unpack them and change into the freshly created ''new-installer'' directory.
# Run the following scripts (as root, in order): pre-install-from-repo.sh, mce-install.sh, post-install.sh.
# Reboot, wait for the activity to stop (see progress on console 8).

In other words, after installing Kubuntu and upgrading it etcetera:
sudo su - #This might ask for the password you specified earlier during the install of kubuntu.
wget -c http://deb.linuxmce.org/ubuntu/new-installer-alpha-latest.tar.gz
tar xvf new-installer-alpha-latest.tar.gz
cd new-installer
./pre-install-from-repo.sh
./mce-install.sh
./post-install.sh
reboot
=== nVidia Restricted Driver ===
Install the nVidia restricted driver (177) from KDE using the Hardware Manager ''before'' installing LinuxMCE 0810 Alpha for the best results

=== MythTV ===
Remove reference to hardy in /etc/apt/sources.list

from terminal
<pre>
sudo apt-get install pluto-mythtv-player
</pre>

Install updated version of pluto-mythtv-plugin

=== Setup Diskless MD ===
Follow the steps from [[LinuxMCE-0810_alpha1#Setup_Diskless_MD|alpha1]].

=== Upgrading kernel ===
There are issues with the ''fglrx'' driver that are documented in Ubuntu's bug tracking system. If you're experiencing those issues, upgrade the kernel to ''2.6.27-13'' or better. [[Upgrading the Kernel]] has been updated with instructions on doing this.

== Updates ==
Check if there is no junk like references to hardy in /etc/apt/sources.list then:
sudo apt-get update
sudo apt-get dist-upgrade
Or use a package manager on the KDE desktop for more convenience.

=== 20090218 (alpha-2.1) ===
*lmce-datalog-db_2.0.0.44.0902180810
*lmce-datalogger-plugin_2.0.0.44.0902180810
*lmce-enocean-tcm120_2.0.0.44.0902180810
*lmce-src-datalogger-plugin_2.0.0.44.0902180810
*lmce-src-enocean-tcm120_2.0.0.44.0902180810
*lmce-src-lmce-datalog_2.0.0.44.0902180810
*pluto-dcerouter_2.0.0.44.0902180810
*pluto-dhcpd-plugin_2.0.0.44.0902180810
*pluto-hald-src_2.0.0.44.0902180810
*pluto-hald_2.0.0.44.0902180810
*pluto-mythtv-plugin_2.0.0.44.0902180810
*pluto-orbitergen_2.0.0.44.0902180810
*pluto-src-dcerouter_2.0.0.44.0902180810
*pluto-src-hal-device-finder_2.0.0.44.0902180810
*pluto-src-mythtv-plugin_2.0.0.44.0902180810
*pluto-src-orbitergen_2.0.0.44.0902180810
*pluto-src-updatemedia_2.0.0.44.0902180810
*pluto-updateentarea_2.0.0.44.0902180810
*pluto-updatemedia_2.0.0.44.0902180810
*pluto-zwave-lighting_2.0.0.44.0902180810
*lmce-game-player_2.0.0.44.0902180810
*lmce-game-plugin_2.0.0.44.0902180810
*lmce-src-game-player_2.0.0.44.0902180810
*lmce-src-game-plugin_2.0.0.44.0902180810

==== 20090222 (alpha-2.1.1) ====
*pluto-dcerouter_2.0.0.44.0902220810
*pluto-bluetooth-dongle_2.0.0.44.0902220810

=== 20090301 (alpha-2.2) ===
SVN revision: 21746

To avoid a known problem when upgrading pluto-storage-devices, forcefully remove it before upgrading and let apt fix it:
dpkg -r --force-all pluto-storage-devices
apt-get update
apt-get install -f
Also please note that installing the upgrade of pluto-system-database will OVERWRITE your existing pluto_main database. It is therefore advisable to make a backup first!
mysqldump --skip-extended-insert pluto_main >pluto_main_$PK_Installation-`date '+%Y%m%d:%H%M%S'`.sql
*pluto-boot-scripts_2.0.0.44.0903010810
*pluto-network-storage_2.0.0.44.0903010810
*pluto-skins-basic_2.0.0.44.0903010810
*pluto-src-network-storage_2.0.0.44.0903010810
*pluto-src-std-plugins_2.0.0.44.0903010810
*pluto-src-updatemedia_2.0.0.44.0903010810
*pluto-std-plugins_2.0.0.44.0903010810
*pluto-storage-devices_2.0.0.44.0903010810
*pluto-system-database_2.0.0.44.0903010810
*pluto-updatemedia_2.0.0.44.0903010810
*pluto-website-admin_2.0.0.44.0903010810

=== 20090308 (alpha-2.3) ===
SVN revision: 21765

Again it is wise to backup your database as there is a new pluto-system-database package, but this one will not overwrite your pluto_main database if it is already installed, it should do an sqlCVS update instead.
Also remove the pluto-storage-devices, hopefully for the last time.
See the previous upgrade [[LinuxMCE-0810_alpha2#20090301_.28alpha-2.2.29|above]] for details on how to do these things.

*pluto-asterisk_2.0.0.44.0903080810
*pluto-src-asterisk_2.0.0.44.0903080810
*pluto-src-text-to-speech_2.0.0.44.0903080810
*pluto-src-updatemedia_2.0.0.44.0903080810
*pluto-storage-devices_2.0.0.44.0903080810
*pluto-system-database_2.0.0.44.0903080810
*pluto-text-to-speech_2.0.0.44.0903080810
*pluto-updatemedia_2.0.0.44.0903080810
*pluto-website-admin_2.0.0.44.0903080810

=== 20090315 (alpha-2.4) ===
SVN revision: 21798

The web admin is being moved from pluto-admin to lmce-admin with this build. A redirect has been placed in pluto-admin to redirect to the new web admin URL to help smooth the transition. While every attempt has been made to make this a smooth transition, please be sure to file a trac ticket if you find bugs related to this move so I can get them taken care of - [[User:jondecker76|jondecker76]]

The Asterisk IVR is broken in this release. For those that need to get it working/wish to try out new changes, do the following:
sudo apt-get install libsox-fmt-all
cd /usr/pluto/bin
sudo rm generate_users_voicemenu.pl
sudo wget http://svn.linuxmce.org/trac.cgi/browser/branches/LinuxMCE-0810/src/Asterisk/generate_users_voicemenu.pl?format=raw
sudo chmod 755 generate_users_voicemenu.pl
sudo ./generate_users_voicemenu.pl
Be sure to have the default voice set up in the Text_To_Speech device's device data (its default is the ugly one we're already used to)! I also highly recommend following the instructions located at [http://wiki.linuxmce.org/index.php/Text_To_Speech http://wiki.linuxmce.org/index.php/Text_To_Speech] on how to install some better voices, and set the default voice to voice_nitech_us_slt_arctic_hts after you install the better voices (this is the best free voice available ATM). This should all work on next weeks build for those that can wait.. I'm still working on getting the better voices included by default, but need to check on licensing issues first.

*pluto-asterisk_2.0.0.44.0903150810
*pluto-boot-scripts_2.0.0.44.0903150810
*pluto-makerelease_2.0.0.44.0903150810
*pluto-newmdinteractor_2.0.0.44.0903150810
*pluto-orbitergen_2.0.0.44.0903150810
*pluto-proxy-orbiter_2.0.0.44.0903150810
*pluto-src-asterisk_2.0.0.44.0903150810
*pluto-src-makerelease_2.0.0.44.0903150810
*pluto-src-newmdinteractor_2.0.0.44.0903150810
*pluto-src-orbitergen_2.0.0.44.0903150810
*pluto-src-proxy-orbiter_2.0.0.44.0903150810
*pluto-src-std-plugins_2.0.0.44.0903150810
*pluto-src-text-to-speech_2.0.0.44.0903150810
*pluto-std-plugins_2.0.0.44.0903150810
*pluto-system-database_2.0.0.44.0903150810
*pluto-text-to-speech_2.0.0.44.0903150810
*pluto-updateentarea_2.0.0.44.0903150810
*pluto-website-admin_2.0.0.44.0903150810

=== 20090322 (alpha-2.5) ===
SVN revision: 21827

*freepbx_0+2.3.1-2
*pluto-asterisk_2.0.0.44.0903220810
*pluto-dhcpd-plugin_2.0.0.44.0903220810
*pluto-install-scripts_2.0.0.44.0903220810
*pluto-raid-tools_2.0.0.44.0903220810
*pluto-skins-basic_2.0.0.44.0903220810
*pluto-src-asterisk_2.0.0.44.0903220810
*pluto-website-admin_2.0.0.44.0903220810

=== 20090401 (alpha-2.6) ===
Note: This build will attempt to use Launch Manager to co-ordinate startup and shutdown of devices. While it is not 100% finished, it is working and stable. Please test it out and file any problems against trac ticket #48. Also, please note the following:
I'm not sure on this, but you may have to manually install LM via apt-get
After you upgrade, reboot your core
CLI output of LM can be viewed on tty8 on the core, and tty1 on MD's (alt+ctrl+F8 and alt+ctrl+F1 respectively). You will have to manually switch back to the orbiter on tty7 when finished
CLI output is not yet completely finished, so the top fields will be blank (this is normal for now)
CLI output of the log messages is working however, so please take a peek at them on tty8/tty1 shortly after you hear the 2nd set of beeps on boot up (when the "x" cursor appears on the screen).
You can further test out LM by switching to tty8/tty1 right after doing a router reload and watching the output and comparing it to what you would expect it to be.
LM dos not yet track regen process and report the % done. This should be working in next week's build, however.
If there are problems and/or you wish to restore previous functionality, the original /usr/pluto/bin/startCore.sh file can be restored from the backup /usr/pluto/bin/startCore.sh._backup, and the LM package removed
LM is not yet properly daemonized. I'm saving this step for last after the socket layer is implemented and we get a client coded.
'''Note:''' All orbiters will likely do a FULL REGEN after this update, and it may appear that your system is hanging because of this. Please give it some time to finish the regen (could take up to an hour on large installs)

* lmcevdr_1.1-10_all.deb
* pluto-website-admin_2.0.0.44.0904010019_i386.deb
* pluto-dynamic-dns_2.0.0.44.0904010019_i386.deb
* lmce-launch-manager_2.0.0.44.0904010019_i386.deb
* pluto-boot-scripts_2.0.0.44.0904010019_i386.deb
* pluto-system-database_2.0.0.44.0904010019_i386.deb
* pluto-orbitergen_2.0.0.44.0904010019_i386.deb
* pluto-updateentarea_2.0.0.44.0904010019_i386.deb
* pluto-orbiter_2.0.0.44.0904010019_i386.deb

=== 20090405 (alpha 2.7) ===
From now on, the SVN version will part of the deb name.
You may need to uninstall 'lmcevdr' (dpkg -r --force-all lmcevdr) and reinstall it (apt-get install lmcevdr) to get around the install-script bug in last weeks .deb package. It worked for me.
* lmce-game-player_2.0.0.44.090405.21873_i386.deb
* lmce-game-plugin_2.0.0.44.090405.21873_i386.deb
* lmce-launch-manager_2.0.0.44.090405.21873_i386.deb
* lmce-phoenix-solo-usb_2.0.0.44.090405.21873_i386.deb
* lmcevdr_1.1-10_all.deb (This is no main package, and therefore does not contain the regular version designation. It is based upon version 21875)
* pluto-bluetooth-dongle_2.0.0.44.090405.21873_i386.deb
* pluto-simplephone_2.0.0.44.090405.21873_i386.deb
* pluto-system-database_2.0.0.44.090405.21873_i386.deb
* pluto-website-admin_2.0.0.44.09040521873_i386.deb

=== 20090412 (alpha 2.8) ===
* pluto-text-to-speech_2.0.0.44.09041221886_i386.deb (283,284) - Finally, good voices will actually install (Nitech HTS Arctic).
* pluto-system-database_2.0.0.44.09041221886_i386.deb (211) - New default voice is voice_nitech_us_slt_arctic_hts. - game plugin and player template cleanups
* mce-diskless-tools_2.0.0.44.09041221886_i386.deb (627,628) - Update kernel image for diskless MDs upon regenning.
* pluto-website-admin_2.0.0.44.09041221886_i386.deb (220) - Infrared codes will now properly come from schema.linuxmce.org
* pluto-boot-scripts_2.0.0.44.09041221886_i386.deb (234)- also schema.linuxmce.org IR codes related.
* pluto-motion-wrapper_2.0.0.44.09041221886_i386.deb (455,456) - changed config variable from ffmpeg_filename to movie_filename
* lmce_launch_manager_2.0.0.44.09041221886_i386.deb (298,299) - LM Actions now work from CLI(such as reload, regen, reboot, etc...)
* lmce-game-player_2.0.0.44.09041221886_i386.deb (673,674) - Rebuilt for new device template
* lmce-game-plugin_2.0.0.44.09041221886_i386.deb (671,672) - Rebuilt for new device template
* pluto-updateentarea_2.0.0.44.09041221886_i386.deb (341,342) - may need to be rebuilt for device template changes

=== 20090413 (alpha 2.9 jondecker special) ===
* pluto-text-to-speech_2.0.0.44.09041321887_i386.deb (283,284) - fixes stupid post-install typo
* pluto-zwave-lighting_2.0.0.44.09041321891_i386.deb (505,506) - thermostate support

=== 20090419 (alpha 2.10 pbr) ===
* pluto-text-to-speech_2.0.0.44.09041921897_i386.deb
* pluto-website-admin_2.0.0.44.09041921897_i386.deb
* lmce-screen-capture-camera_2.0.0.44.09041921897_i386.deb
* pluto-system-database_2.0.0.44.09041921897_i386.deb
* lmce-game-plugin_2.0.0.44.09041921897_i386.deb
* lmce-game-player_2.0.0.44.09041921897_i386.deb
* pluto-asterisk_2.0.0.44.09041921897_i386.deb

=== 20090426 (upcoming...) ===
* lmcevdr_1.1-10_all.deb - more setup fixes, this time for the MD
* pluto-boot-scripts (234) - small fix to get rid of a warning on DCERouter startup re missing dir.
* pluto-asterisk - Added Support for Cisco 7910 phone
* pluto-dhcpd-plugin - Added support for Cisco 7910 phone

== Previous alpha releases ==
* Notes about [[LinuxMCE-0810 alpha1]]
* Notes about [[LinuxMCE-0810 alpha0]]

Upgrading the Kernel

2009-04-24T11:15:12Z

Cylon7: /* Installing */ typo in package numbers for linux-restricted and linux-headers

[[Category:LinuxMCEMaintenance]]
[[category: tutorials]]
[[category: programmer's Guide]]

==Introduction==
The ability to change kernel versions at will can be extremely useful for fighting driver bugs and regressions. This article provides procedures for upgrading the kernel.

==LinuxMCE 0810==
Upgrading kernels is significantly easier in 0810, now that LinxMCE uses the standard Ubuntu kernel. If you're interested in using a non-standard kernel, you can adapt the 0710 instructions to your needs.

===Apt Repositories===
If the kernel version you're looking for is not available in the standard repositories, you might have to enable the proposed repositories by adding a line that looks something like:
<pre>
deb http://ubuntu.media.mit.edu/ubuntu/ intrepid-proposed restricted main universe multiverse
</pre>
to ''/etc/apt/sources.list''. Of course, you'll want to use the package mirror that is closest to you, probably not MIT. After adding this line, run ''apt-get update'' to refresh the package lists.

===Installing===
On the core, simply install the new kernel like any other package. Don't forget the restricted modules and headers if you need them.
<pre>
linuxmce@dcerouter:~$ sudo apt-get install linux-image-2.6.27-13-generic linux-restricted-modules-2.6.27-13-generic linux-headers-2.6.27-13-generic
</pre>
If you always want the most up-to-date kernel, consider installing the package ''[http://packages.ubuntu.com/intrepid/linux linux]''. (This is outside of the scope of this article.)

On MDs, there is one extra step. You will need to update some links in ''/boot/''.
<pre>
root@moon44:~# cd /boot/
root@moon44:/boot# mv initrd.img initrd.img.bk
root@moon44:/boot# mv vmlinuz vmlinuz.bk
root@moon44:/boot# ln initrd.img-2.6.27-13-generic initrd.img
root@moon44:/boot# ln vmlinuz-2.6.27-13-generic vmlinuz
</pre>

==LinuxMCE 0710==
'''''WARNING:''''' This procedure will break certain things and may even make your system unusable, therefore use at your own risk. Of course, if your system is not working or is unstable anyway, then trying this could improve things!

The kernel version that ships with LinuxMCE 0710 is 2.6.22-14. At the time of writing the most recent stable kernel version is 2.6.28.8. The .22 kernel is almost a full year old and as such does not support a lot of the newer hardware.

Note- kernel version 2.6.27 has changes in it (a redefined set of arguments for smp_call_function) which breaks earlier versions of the Nvidia driver. Nvidia drivers 178.80 and above should work.

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

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

Example:
cd ~
wget http://www.somesite.com/some_kernel_driver.c
echo obj-m = some_kernel_driver.o > Makefile
cd /lib/modules/2.6.22-14-generic/build
make M=~ modules
ls -l ~/some_kernel_driver.ko

You may then copy the module to the appropriate directory in the modules tree.

===Upgrade process===

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.

An alternative approach is described here [http://www.debian.org/releases/stable/i386/ch08s06.html.en Rebuilding the kernel the debian way]. Anyone using this potentially easier method could update this document.

====Potential problems====
All the normal issues of upgrading your kernel apply. Always keep your old, working kernel on hand.

====Steps====

=====Recompiling the kernel=====
The first step is to grab the kernel source and extract it to the /usr/src folder.

cd /usr/src
wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.28.7.tar.bz2
tar -jxvf linux-2.6.28.7.tar.bz
rm linux
ln -s linux-2.6.28.5 linux

Now lets copy the .config file from our generic 2.6.22 kernel.
cd linux
cp /boot/config-2.6.22-14-generic .config

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

sudo apt-get install libncurses5 libncurses5-dev qt3-dev-tools libqt3-mt-dev

Then you can either choose to use the character based interface to set your kernel options
make menuconfig 2> module_errors

Or you can use the GUI interface
DISPLAY=:0.0 make xconfig

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

I opted to change these things:
* Selected exact processor family to enable processor optimization extensions
* Selected preemptive kernel (low latency)
* Build SATA driver into kernel
* Build MD,RAID1,RAID5 modules into kernel
* Build NIC module into kernel
* Disabled kernel debugging ('''Note: This is very important if you plan to use this kernel on Media Directors.''')

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.
make
sudo make modules_install

Copy your kernel image to your /boot folder. Create a new initramfs image. Update your menu.lst file.

cp arch/yyxx/boot/bzImage /boot/vmlinuz-2.6.28.7
mkinitramfs -o /boot/initrd.img-2.6.26.5 2.6.28.7
nano /boot/grub/menu.lst

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.

lsmod > ~/module_list-2.6.22.14

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

reboot

=====Additional items which need to be rebuilt=====
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 & 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.

=====Mythtv=====
You do not have to rebuild Mythtv, but if you chose to use the new High Precision Event Timer (HPET) instead of the older kernel Real Time Clock (RTC), then Mythtv will not start up because /proc/sys/dev/rtc/max-user-freq does not exist. This is because the LinuxMCE 7.10 /etc/init.d/mythtv-backend script does not check if it exists before trying to write to it. You will have to change your /etc/init.d/mythtv-backend script as follows:

case "$1" in
start)
if test -e $RUNDIR/$NAME.pid ; then
echo "mythbackend already running, use restart instead."
else
# set the timeslice to 1/1024 of a sec for smoother mythtv and xine and mplayer playback
if [ -w /proc/sys/dev/rtc/max-user-freq ] # check if RTC (older kernels) exists and I can write to it
# failure is not an option!
then echo 1024 > /proc/sys/dev/rtc/max-user-freq
elif [ -w /proc/sys/dev/hpet/max-user-freq ] # or newer kernels with the High Precision Timer (HPET)
# may or may not emulate the older RTC fully
then echo 1024 > /proc/sys/dev/hpet/max-user-freq
fi # start starting the startup of mythtv
echo -n "Starting $DESC: $NAME " start-stop-daemon --start --pidfile $RUNDIR/$NAME.pid \

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

=====ALSA=====
For the ALSA drivers I opted to upgrade the whole package. The compilation and installation is so straight forward that there'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):
mkdir alsa
cd alsa
wget ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.19.tar.bz2
wget ftp://ftp.alsa-project.org/pub/firmware/alsa-firmware-1.0.19.tar.bz2
wget ftp://ftp.alsa-project.org/pub/lib/alsa-lib-1.0.19.tar.bz2
wget ftp://ftp.alsa-project.org/pub/plugins/alsa-plugins-1.0.19.tar.bz2
wget ftp://ftp.alsa-project.org/pub/utils/alsa-utils-1.0.19.tar.bz2
wget ftp://ftp.alsa-project.org/pub/oss-lib/alsa-oss-1.0.17.tar.bz2
for fi in *; do
tar -jxvf $fi
done
cd alsa-driver-1.0.19
./configure --with-cards=hda-intel
make
sudo make install
cd ..
for fi in alsa-lib-1.0.19 alsa-plugins-1.0.19 alsa-utils-1.0.19 alsa-oss-1.0.19 alsa-firmware-1.0.19; do
cd $fi
./configure
make
sudo make install
cd ..
done

=====Asterisk telephony=====
For Asterisk, simply download the latest Zaptel sources. Configure, Make, Install.
wget http://downloads.digium.com/pub/zaptel/zaptel-1.4.12.1.tar.gz
tar -zxvf zaptel-1.4.12.1.tar.gz
cd zaptel-1.4.12.1
./configure --prefix=/usr
make
sudo make install

For kernel >= 2.6.28 a fix is needed
Save the following as zaptel-kernel.patch :

--- zaptel-1.4.12.1/kernel/ztdummy.c.ORG 2009-04-11 00:26:02.000000000 +0200
+++ zaptel-1.4.12.1/kernel/ztdummy.c 2009-04-11 00:26:53.000000000 +0200
@@ -199,7 +199,12 @@
* expired.
* We should worry if overrun is 2 or more; then we really missed
* a tick */
- overrun = hrtimer_forward(&zaptimer, htmr->expires,
+ overrun = hrtimer_forward(&zaptimer,
+#if LINUX_VERSION_CODE > KERNEL_VERSION(2,6,27)
+ hrtimer_get_expires(htmr),
+#else
+ htmr->expires,
+#endif
ktime_set(0, ZAPTEL_TIME_NS));
if(overrun > 1) {
if(printk_ratelimit())

and apply after untaring like this :
tar -zxvf zaptel-1.4.12.1.tar.gz
patch -p0 <zaptel-kernel.patch

=====LIRC IR control=====
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 kernel version 2.6.27 the following LIRC setup steps worked. The only issue you will have is with some modules not compiling, as noted above. Just compile the module you need for your remote- for me it was ''mceusb2''.
cd /opt/lirc
wget http://prdownloads.sourceforge.net/lirc/lirc-0.8.4a.tar.bz2
tar -xjvf lirc-0.8.4a.tar.bz2
./configure --prefix=/usr --with-driver=usbmce2
make
checkinstall

At this point if you get errors about not being about to overwrite
/usr/lib/liblirc_client.la you may need to
cp /usr/lib/liblirc_client.la /opt/lirc/liblirc_client.la.orig
dpkg --force-overwrite -i lirc_0.8.4a-1_i386.deb

Proceed with
modprobe lirc_mceusb2
lircd
mode2
Press some buttons on your remote, you should see information appear about the IR being received.

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.
cd /usr/src/linux
wget http://lirc.sourceforge.net/software/snapshots/lirc-bttv-linux-2.6.24.patch
patch -p1 < lirc-bttv-linux-2.6.24.patch
cd ..
cvs -z8 -d:pserver:anonymous@lirc.cvs.sourceforge.net:/cvsroot/lirc co lirc
cd lirc-0.8.3
./configure --prefix=/usr --with-driver=all
make
make install
reboot

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

For nVidia do this:
wget http://us.download.nvidia.com/XFree86/Linux-x86/177.80/NVIDIA-Linux-x86-177.80-pkg1.run
sh NVIDIA-Linux-x86-177.80-pkg1.run

If you have already had a newer version of the driver installed, then just install the kernel module like this :
sh NVIDIA-Linux-x86-XXX.XX-pkg1.run -K

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

=====Tuner and other drivers=====
Don't forget to recompile and install other drivers which you may have had to install to get your system working. These include the V4L DVB drivers.

====Media Directors====
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.
===Use old kernel===
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.

mkdir /tmp/moonfs_64 /tmp/moonfs_32
tar -jxvf /usr/pluto/install/PlutMD-adm64.tar.bz2 /tmp/moonfs_64/
tar -jxvf /usr/pluto/install/PlutMD-i386.tar.bz2 /tmp/moonfs_32/
for md in /usr/pluto/diskless/* /tmp/moonfs_64 /tmp/moonfs_32; do
md_device=`echo "$md" | sed -e 's/.*[/]$[^/]$/\1/g'`
cd $md/boot
ln -s vmlinuz-2.6.22-14-generic vmlinuz-2.6.26.5
ln -s initrd.img-2.6.22-14-generic initrd.img-2.6.26.5
done
tar -C /tmp/moonfs_64 -jcvpf /usr/pluto/install/PlutoMD-adm64.tar.bz2 .
tar -C /tmp/moonfs_32 -jcvpf /usr/pluto/install/PlutoMD-i386.tar.bz2 .
rm -rf /tmp/moonfs_*

=====Use new kernel=====
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.

These scripts serve as a guideline, and may need to be customized to your unique configuration.

'''A few notes:'''
* 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.
* 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's architecture.
* You should build your video driver files first, so you can include them in your MD archive.

for md in /usr/pluto/diskless/*; do
md_device=`echo "$md" | sed -e 's/.*[/]$[^/]$/\1/g'`
cp /boot/vmlinuz-2.6.26.5 $md/boot/
cp /boot/initrd.img-2.6.26.5 $md/boot/
cp -r /lib/modules/2.6.26.5/ $md/lib/modules/
/usr/pluto/bin/Diskless_InstallKernel.sh $md_device
done
/usr/pluto/bin/Diskless_BuildDefaultImage.sh

Now rebuild the archives, so future Media Directors will get the correct kernel image.
cd /tmp
mkdir moonfs_x64
cd moonfs_x64
tar -jxvf /usr/pluto/install/PlutMD-adm64.tar.bz2
cp /boot/vmlinuz-2.6.26.5 boot
cp /boot/initrd.img-2.6.26.5 boot
cp -r /lib/modules/2.6.26.5/ lib/modules/
tar -jcvpf /usr/pluto/install/PlutoMD-adm64.tar.bz2 *
cd ..
rm -rf moonfs_x64

====Video Drivers====
Video drivers for Media Directors get their own section because they often require updated libraries in addition to updated kernel modules. These libraries will have to be distributed to the media directors and updated in the archive. nVidia'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's similar.

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.

stripheader.sh
readsint ()
{
byte=`head -c$2 $1 | tail -c1`
sint=`printf '%u' "'$byte"`
let "sint=$sint & 0xFF"
eval "$3=\"$sint\""
}
readuint32 ()
{
readsint $1 $(($2+1)) b1
readsint $1 $(($2+2)) b2
readsint $1 $(($2+3)) b3
readsint $1 $(($2+4)) b4

uint=$(( ($b4 << 24) + ($b3 << 16) + ($b2 << 8) + $b1 ))
eval "$3=\"$uint\""
}

let "header=12"
readuint32 $1 $header int
let "header=$header+$int+4"
readuint32 $1 $header int
let "header=$header+$int+4"
readuint32 $1 $header int
let "header=$header+$int+4"

precomp=$(stat -c%s "$1")
let "precomp-=$header"
tail -c$precomp $1 > $2

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.

wget http://us.download.nvidia.com/XFree86/Linux-x86_64/173.14.12/NVIDIA-Linux-x86_64-173.14.12-pkg2.run
sh NVIDIA-Linux-x86_64-173.14.12-pkg2.run --keep --add-this-kernel
./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
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
for md in /usr/pluto/diskless/*; do
cp -r NVIDIA-Linux-x86_64-173.14.12-pkg2/usr/* $md/usr/
cp nvidia.ko $md/lib/modules/2.6.26.5/kernel/drivers/video/
done