http://wiki.linuxmce.org/api.php?action=feedcontributions&feedformat=atom&user=Marrandy 2026-05-11T05:39:13Z User contributions MediaWiki 1.44.0 http://wiki.linuxmce.org/index.php?title=User:Marrandy&diff=28777 2011-10-06T12:49:05Z

<p>Marrandy: </p> <hr /> <div> My current configuration: (work in progress at the moment) <br /> I have a lot of parts ie.zoneminder (now using Blue Iris) for cameras, asterisk/freeswitch for telephone/VOIP, <br /> Caddx NX security system. I'm no longer trying to bring them together. Waiting for the next release before I start testing again.<br /> <br /> <br /> LinuxMCE version - 0810-Release<br /> <br /> Computer: Hybrid, ASUS M3N78-VM.<br /> <br /> Remote Storage: Thecus N7700 RAID array.<br /> <br /> Orbiters/Remote Controls: DT-366, Fiire remote.<br /> <br /> TV: HDhomerun, Sharp Aquos.<br /> <br /> Control: USB-UIRT, GC-100-12.<br /> <br /> Satellite Setup: None at the moment, but I'm looking.<br /> <br /> Home Automation: Insteon various. X10 various.<br /> <br /> Camera Setup: 4 x analog cameras: Currently connected to ZoneMinder (now Blue Iris) Server. Several Axis IP cameras.<br /> <br /> Cable TV: For my sins, I finally got Brighthouse/Tampabay cable.</div>

Marrandy http://wiki.linuxmce.org/index.php?title=WebDT_366&diff=27747 2011-04-22T13:59:39Z

<p>Marrandy: /* Usage */</p> <hr /> <div>[[Category: Hardware]]<br /> {{versioninfo}}<br /> [[Category: WebPads]]<br /> [[Category: Orbiters]]<br /> <br /> [[Image:WebDT366.jpg]]<br /> <br /> [http://www.dtresearch.com/ Official site]<br /> <br /> [http://dtresearch.com/support/manuals/WebDT366%20Basic%20Operation%20Guide.pdf PDF]<br /> <br /> [http://webdt.org/ Forum dedicated to all the WebDTs out there]<br /> <br /> - Windows® Embedded and Windows XP with Windows Media Player and Internet Explorer; ICA &amp; RDP Terminal clients; Terminal Emulation software &lt;br&gt;<br /> - Compatible with Windows CE or Windows XP applications &lt;br&gt;<br /> - Brilliant 8.4&quot; TFT Active Matrix LCD at 800 x 600 SVGA resolution &lt;br&gt;<br /> - Integrated touch screen display with &quot;on screen&quot; soft keyboard support &lt;br&gt;<br /> - CompactFlash™ slot; PC Card slot; USB port &lt;br&gt;<br /> - Built-in HDD, 802.11 b/g WLAN adapter and Bluetooth available &lt;br&gt;<br /> - Full 16-bit audio with stereo; headset jack; built-in stereo speakers and microphone&lt;br&gt;<br /> <br /> ----<br /> <br /> Price: $350 - see [http://forum.linuxmce.org/index.php?topic=7051.0 this] forum post for more information on ordering.<br /> <br /> ----<br /> <br /> ==Demonstration==<br /> <br /> Google Videos:<br /> <br /> [http://video.google.com/videoplay?docid=1080865851585336899&amp;ei=XxpvSqKlGYSwrAOP_-mWBQ&amp;q=webdt&amp;hl=en Part 1 of 2]<br /> <br /> [http://video.google.com/videoplay?docid=2013509531300772806&amp;ei=XxpvSqKlGYSwrAOP_-mWBQ&amp;hl=en Part 2 of 2]<br /> <br /> ==Tech Specs==<br /> <br /> [[Image:Pins.jpg]]<br /> <br /> '''WebDT Pins (Numbered looking at front of cradle)'''<br /> <br /> <br /> [[Image:Power Connection.jpg]] <br /> <br /> '''Power Connection is on the right-hand side of the cradle.'''<br /> <br /> [[Image:USB Connections.jpg]]<br /> <br /> '''USB B connection is on left-hand side of the cradle, the two USB A connections are on the front.'''<br /> <br /> <br /> Reading the table: The number to the left of the &quot;:&quot; is the pin number, the number to the right is the number on the usb connection number (as I numbered them).<br /> <br /> 1: (Unknown)<br /> 2: U13<br /> 3: U9<br /> 4: U2, U6, U11<br /> 5: U12<br /> 6: (Unknown)<br /> <br /> 7: U5, U10, U15<br /> 8: U8<br /> 9: P1<br /> 10: U7<br /> 11: U14<br /> 12: (Unknown)<br /> <br /> 13: (Unknown)<br /> 14: (Unknown)<br /> 15: (Unknown)<br /> 16: P2<br /> 17: (Unknown)<br /> 18: U1<br /> <br /> Pins U3 and U4 connections' are unknown presently.<br /> <br /> ==Installing the Orbiter==<br /> - Make sure your system is setup according to the network specifications detailed [http://wiki.linuxmce.org/index.php/Network_Settings here] &lt;br&gt;<br /> - Format a USB stick. I like Gparted. Use a stick that is at least 1GB.&lt;br&gt;<br /> - Download the [http://www.linuxmce.org/webpad/webpad-gamma1.dd.bz2 file]. &lt;br&gt;<br /> - Uncompress it &lt;br&gt;<br /> sudo bunzip2 webpad-gamma1.dd.bz2<br /> - Copy the file to the stick using dd.<br /> sudo dd if=webpad-gamma1.dd of=/dev/sda &lt;br&gt;<br /> where /dev/sda is the location of your USB stick. You can use Gparted to determine the location of your stick.<br /> - Plug the stick into the WebDT 366 and power it on. &lt;br&gt;<br /> - A LinuxMCE splace screen should appear and the installation process will begin automatically. &lt;br&gt;<br /> - After the installation completes, power down the device, remove the USB stick, and power it back on.&lt;br&gt;<br /> - The device will boot and show a LinuxMCE splash screen along with a progress bar. After this is loaded, you will be presented with a screen to input your wireless settings. &lt;br&gt;<br /> - The splash screen will reappear and then a series of screens will ask for input so that an Orbiter can be generated.<br /> <br /> <br /> Troubleshooting:&lt;br&gt;<br /> - If you receive the following error:<br /> USB Boot Device : MASS Storage Class [00F9h/FFh/3Fh]<br /> Missing operating system.<br /> No boot device present. Halting.<br /> you have most likely used dd incorrectly:<br /> sudo dd if=webpad-gamma1.dd of=/dev/sda1<br /> Note the addition of the &quot;1&quot; at the end of &quot;/dev/sda&quot;. Be sure and use dd without this, or any other number.&lt;br&gt;<br /> - If your flash drive has multiple partitions, you can make a bootable USB disk with a program like [http://www.ultimatebootcd.com/download.html UBCD] and then remove the multiple partitions, create one, and then proceed with the installation instructions shown above. &lt;br&gt;<br /> - If your USB stick won't fit into the USB port of the WebDT, use a USB cable extender.&lt;br&gt;&lt;br&gt;<br /> <br /> == Usage ==<br /> - To access the terminal, press the third soft key when the splash screen is displayed upon booting. If this does not work, attach a keyboard to the USB port and when the splash screen appears, press:<br /> CTRL-C<br /> t<br /> - From the terminal, you can run the configuration utility by entering:<br /> /usr/local/bin/TabletCFG<br /> - You can ssh into the tablet using the username of root and the password of root<br /> - Pressing the power key once will suspend the device. Pressing it again will bring it out of suspend. &lt;br&gt;<br /> - Holding the power key will power down the device. &lt;br&gt;<br /> - Pressing the second soft key will hide the UI and pressing the first soft key will bring it back. This is useful if you don't want the UI displayed but still want quick access to using the device. &lt;br&gt;<br /> - Pressing the third soft key will bring up the wireless settings configuration screen. &lt;br&gt;<br /> - Pressing the fourth soft key will reload the orbiter. &lt;br&gt;<br /> - Pressing the third soft key plus UP/DOWN on the 4way button on the right, adjusts the brightness of the screen<br /> <br /> <br /> [http://forum.linuxmce.org/index.php?topic=6577.0 This] forum post proved most useful in creating these instructions.<br /> <br /> <br /> The DT366 will timeout (screen blanks). To make sure you first screen touch doesn't launch anything, do the following:-<br /> <br /> TSCHAKeee: pointed out not to touch the button on the right, that I could go to Computing - Web Admin - go to Orbiters by either looking on the left side for devices - orbiters or wizard - devices- orbiters. Find the correct orbiter, select advanced and 3 rows or so from the bottom, check Ignore First event, then save and reload<br /> <br /> ==WPA2 Wireless security for WebDT366==<br /> [http://wiki.linuxmce.org/index.php/WebDT_366_WPA2 Wiki page for WPA2 security]</div>

Marrandy http://wiki.linuxmce.org/index.php?title=WebDT_366&diff=27746 2011-04-22T13:59:00Z

<p>Marrandy: /* Usage */ - settings to prevent launching an item whern the screen is blanked.</p> <hr /> <div>[[Category: Hardware]]<br /> {{versioninfo}}<br /> [[Category: WebPads]]<br /> [[Category: Orbiters]]<br /> <br /> [[Image:WebDT366.jpg]]<br /> <br /> [http://www.dtresearch.com/ Official site]<br /> <br /> [http://dtresearch.com/support/manuals/WebDT366%20Basic%20Operation%20Guide.pdf PDF]<br /> <br /> [http://webdt.org/ Forum dedicated to all the WebDTs out there]<br /> <br /> - Windows® Embedded and Windows XP with Windows Media Player and Internet Explorer; ICA &amp; RDP Terminal clients; Terminal Emulation software &lt;br&gt;<br /> - Compatible with Windows CE or Windows XP applications &lt;br&gt;<br /> - Brilliant 8.4&quot; TFT Active Matrix LCD at 800 x 600 SVGA resolution &lt;br&gt;<br /> - Integrated touch screen display with &quot;on screen&quot; soft keyboard support &lt;br&gt;<br /> - CompactFlash™ slot; PC Card slot; USB port &lt;br&gt;<br /> - Built-in HDD, 802.11 b/g WLAN adapter and Bluetooth available &lt;br&gt;<br /> - Full 16-bit audio with stereo; headset jack; built-in stereo speakers and microphone&lt;br&gt;<br /> <br /> ----<br /> <br /> Price: $350 - see [http://forum.linuxmce.org/index.php?topic=7051.0 this] forum post for more information on ordering.<br /> <br /> ----<br /> <br /> ==Demonstration==<br /> <br /> Google Videos:<br /> <br /> [http://video.google.com/videoplay?docid=1080865851585336899&amp;ei=XxpvSqKlGYSwrAOP_-mWBQ&amp;q=webdt&amp;hl=en Part 1 of 2]<br /> <br /> [http://video.google.com/videoplay?docid=2013509531300772806&amp;ei=XxpvSqKlGYSwrAOP_-mWBQ&amp;hl=en Part 2 of 2]<br /> <br /> ==Tech Specs==<br /> <br /> [[Image:Pins.jpg]]<br /> <br /> '''WebDT Pins (Numbered looking at front of cradle)'''<br /> <br /> <br /> [[Image:Power Connection.jpg]] <br /> <br /> '''Power Connection is on the right-hand side of the cradle.'''<br /> <br /> [[Image:USB Connections.jpg]]<br /> <br /> '''USB B connection is on left-hand side of the cradle, the two USB A connections are on the front.'''<br /> <br /> <br /> Reading the table: The number to the left of the &quot;:&quot; is the pin number, the number to the right is the number on the usb connection number (as I numbered them).<br /> <br /> 1: (Unknown)<br /> 2: U13<br /> 3: U9<br /> 4: U2, U6, U11<br /> 5: U12<br /> 6: (Unknown)<br /> <br /> 7: U5, U10, U15<br /> 8: U8<br /> 9: P1<br /> 10: U7<br /> 11: U14<br /> 12: (Unknown)<br /> <br /> 13: (Unknown)<br /> 14: (Unknown)<br /> 15: (Unknown)<br /> 16: P2<br /> 17: (Unknown)<br /> 18: U1<br /> <br /> Pins U3 and U4 connections' are unknown presently.<br /> <br /> ==Installing the Orbiter==<br /> - Make sure your system is setup according to the network specifications detailed [http://wiki.linuxmce.org/index.php/Network_Settings here] &lt;br&gt;<br /> - Format a USB stick. I like Gparted. Use a stick that is at least 1GB.&lt;br&gt;<br /> - Download the [http://www.linuxmce.org/webpad/webpad-gamma1.dd.bz2 file]. &lt;br&gt;<br /> - Uncompress it &lt;br&gt;<br /> sudo bunzip2 webpad-gamma1.dd.bz2<br /> - Copy the file to the stick using dd.<br /> sudo dd if=webpad-gamma1.dd of=/dev/sda &lt;br&gt;<br /> where /dev/sda is the location of your USB stick. You can use Gparted to determine the location of your stick.<br /> - Plug the stick into the WebDT 366 and power it on. &lt;br&gt;<br /> - A LinuxMCE splace screen should appear and the installation process will begin automatically. &lt;br&gt;<br /> - After the installation completes, power down the device, remove the USB stick, and power it back on.&lt;br&gt;<br /> - The device will boot and show a LinuxMCE splash screen along with a progress bar. After this is loaded, you will be presented with a screen to input your wireless settings. &lt;br&gt;<br /> - The splash screen will reappear and then a series of screens will ask for input so that an Orbiter can be generated.<br /> <br /> <br /> Troubleshooting:&lt;br&gt;<br /> - If you receive the following error:<br /> USB Boot Device : MASS Storage Class [00F9h/FFh/3Fh]<br /> Missing operating system.<br /> No boot device present. Halting.<br /> you have most likely used dd incorrectly:<br /> sudo dd if=webpad-gamma1.dd of=/dev/sda1<br /> Note the addition of the &quot;1&quot; at the end of &quot;/dev/sda&quot;. Be sure and use dd without this, or any other number.&lt;br&gt;<br /> - If your flash drive has multiple partitions, you can make a bootable USB disk with a program like [http://www.ultimatebootcd.com/download.html UBCD] and then remove the multiple partitions, create one, and then proceed with the installation instructions shown above. &lt;br&gt;<br /> - If your USB stick won't fit into the USB port of the WebDT, use a USB cable extender.&lt;br&gt;&lt;br&gt;<br /> <br /> == Usage ==<br /> - To access the terminal, press the third soft key when the splash screen is displayed upon booting. If this does not work, attach a keyboard to the USB port and when the splash screen appears, press:<br /> CTRL-C<br /> t<br /> - From the terminal, you can run the configuration utility by entering:<br /> /usr/local/bin/TabletCFG<br /> - You can ssh into the tablet using the username of root and the password of root<br /> - Pressing the power key once will suspend the device. Pressing it again will bring it out of suspend. &lt;br&gt;<br /> - Holding the power key will power down the device. &lt;br&gt;<br /> - Pressing the second soft key will hide the UI and pressing the first soft key will bring it back. This is useful if you don't want the UI displayed but still want quick access to using the device. &lt;br&gt;<br /> - Pressing the third soft key will bring up the wireless settings configuration screen. &lt;br&gt;<br /> - Pressing the fourth soft key will reload the orbiter. &lt;br&gt;<br /> - Pressing the third soft key plus UP/DOWN on the 4way button on the right, adjusts the brightness of the screen<br /> <br /> <br /> [http://forum.linuxmce.org/index.php?topic=6577.0 This] forum post proved most useful in creating these instructions.<br /> <br /> <br /> The DT366 will timeout (screen blanks). To make sure you first screen touch doesn't lanunch anything, do the following:-<br /> <br /> TSCHAKeee: pointed out not to touch the button on the right, that I could go to Computing - Web Admin - go to Orbiters by either looking on the left side for devices - orbiters or wizard - devices- orbiters. Find the correct orbiter, select advanced and 3 rows or so from the bottom, check Ignore First event, then save and reload<br /> <br /> ==WPA2 Wireless security for WebDT366==<br /> [http://wiki.linuxmce.org/index.php/WebDT_366_WPA2 Wiki page for WPA2 security]</div>

Marrandy http://wiki.linuxmce.org/index.php?title=User:Marrandy&diff=27273 2011-03-21T00:17:54Z

<p>Marrandy: </p> <hr /> <div> My current configuration: (work in progress at the moment) <br /> I have a lot of parts ie.zoneminder (now using Blue Iris) for cameras, asterisk/freeswitch for telephone/VOIP, <br /> Caddx NX security system. I'm no longer trying to bring them together. Waiting for the next release before I start testing again.<br /> <br /> <br /> <br /> Computer: Hybrid, ASUS M3N78-VM.<br /> <br /> Remote Storage: Thecus N7700 RAID array.<br /> <br /> Orbiters/Remote Controls: DT-366, Fiire remote.<br /> <br /> TV: HDhomerun, Sharp Aquos.<br /> <br /> Control: USB-UIRT, GC-100-12.<br /> <br /> Satellite Setup: None at the moment, but I'm looking.<br /> <br /> Home Automation: Insteon various. X10 various.<br /> <br /> Camera Setup: 4 x analog cameras: Currently connected to ZoneMinder (now Blue Iris) Server. Several Axis IP cameras.<br /> <br /> Cable TV: For my sins, I finally got Brighthouse/Tampabay cable.</div>

Marrandy http://wiki.linuxmce.org/index.php?title=User:Marrandy&diff=26093 2010-11-05T15:20:57Z

<p>Marrandy: </p> <hr /> <div> My current configuration: (work in progress at the moment) <br /> I have a lot of parts ie. zoneminder for cameras, asterisk for telephone/VOIP, <br /> Caddx NX security system. I'm trying to bring them together.<br /> <br /> <br /> <br /> Computer: Hybrid, ASUS M3N78-VM<br /> <br /> Remote Storage: Thecus N7700 RAID array<br /> <br /> Orbiters/Remote Controls: DT-366<br /> <br /> TV: HDhomerun, Sharp Aquos<br /> <br /> Control: USB-UIRT, GC-100-12<br /> Satellite Setup: None at the moment, but I'm looking.<br /> Home Automation: Insteon various. X10 various.<br /> <br /> Camera Setup: 4 x analog cameras: Currently connected to ZoneMinder Server. Several Axis IP cameras.<br /> <br /> Cable TV: For my sins, I finally got Brighthouse/tampabay cable.</div>

Marrandy http://wiki.linuxmce.org/index.php?title=User:Marrandy&diff=26092 2010-11-05T15:20:32Z

<p>Marrandy: </p> <hr /> <div> My current configuration: (work in progress at the moment) I have a lot of parts ie. zoneminder for cameras, asterisk for telephone/VOIP, Caddx NX security system. I'm trying to bring them together.<br /> <br /> <br /> <br /> Computer: Hybrid, ASUS M3N78-VM<br /> <br /> Remote Storage: Thecus N7700 RAID array<br /> <br /> Orbiters/Remote Controls: DT-366<br /> <br /> TV: HDhomerun, Sharp Aquos<br /> <br /> Control: USB-UIRT, GC-100-12<br /> Satellite Setup: None at the moment, but I'm looking.<br /> Home Automation: Insteon various. X10 various.<br /> <br /> Camera Setup: 4 x analog cameras: Currently connected to ZoneMinder Server. Several Axis IP cameras.<br /> <br /> Cable TV: For my sins, I finally got Brighthouse/tampabay cable.</div>

Marrandy http://wiki.linuxmce.org/index.php?title=User:Marrandy&diff=26091 2010-11-05T15:19:13Z

<p>Marrandy: </p> <hr /> <div> My current configuration: (work in progress at the moment): I have a lot of parts ie. zoneminder for cameras, asterisk for telephone/VOIP, Caddx NX security system. I'm trying to bring them together.<br /> <br /> <br /> <br /> Computer: Hybrid, ASUS M3N78-VM<br /> <br /> Remote Storage: Thecus N7700 RAID array<br /> <br /> Orbiters/Remote Controls: DT-366<br /> <br /> TV: HDhomerun, Sharp Aquos<br /> <br /> Control: USB-UIRT, GC-100-12<br /> Satellite Setup: None at the moment, but I'm looking.<br /> Home Automation: Insteon various. X10 various.<br /> <br /> Camera Setup: 4 x analog cameras: Currently connected to ZoneMinder Server. Several Axis IP cameras.<br /> <br /> Cable TV: For my sins, I finally got Brighthouse/tampabay cable.</div>

Marrandy http://wiki.linuxmce.org/index.php?title=User:Marrandy&diff=25087 2010-09-20T04:26:37Z

<p>Marrandy: </p> <hr /> <div> my current configuration: (work in progress at the moment): I have a lot of parts ie. zoneminder for cameras, asterisk for telephone/VOIP, <br /> security system. I'm trying to bring them together.<br /> <br /> <br /> <br /> <br /> <br /> Orbiters/Remote Controls: DT-366<br /> <br /> HDhomerun<br /> <br /> USB-UIRT, GC-100-12<br /> <br /> Home Automation: Insteon various. X10 various.<br /> <br /> Camera Setup: 4 x analog cameras: Currently connected to ZoneMinder Server. Several Axis IP cameras.<br /> <br /> Satellite Setup: None at the moment, but I'm looking.</div>

Marrandy http://wiki.linuxmce.org/index.php?title=Upgrading_the_Kernel&diff=18064 2009-03-22T02:16:32Z

<p>Marrandy: /* LinuxMCE 0710 */</p> <hr /> <div>[[Category:LinuxMCEMaintenance]]<br /> [[category: tutorials]]<br /> [[category: programmer's Guide]]<br /> <br /> <br /> ==Introduction==<br /> 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.<br /> <br /> ==LinuxMCE 0810==<br /> 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.<br /> <br /> ===Apt Repositories===<br /> 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:<br /> &lt;pre&gt;<br /> deb http://ubuntu.media.mit.edu/ubuntu/ intrepid-proposed restricted main universe multiverse<br /> &lt;/pre&gt;<br /> 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.<br /> <br /> ===Installing===<br /> On the core, simply install the new kernel like any other package. Don't forget the restricted modules and headers if you need them.<br /> &lt;pre&gt;<br /> linuxmce@dcerouter:~$ sudo apt-get install linux-image-2.6.27-13-generic linux-restricted-modules-2.6.27-11-generic linux-headers-2.6.27-11-generic<br /> &lt;/pre&gt;<br /> 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.)<br /> <br /> On MDs, there is one extra step. You will need to update some links in ''/boot/''.<br /> &lt;pre&gt;<br /> root@moon44:~# cd /boot/<br /> root@moon44:/boot# mv initrd.img initrd.img.bk<br /> root@moon44:/boot# mv vmlinuz vmlinuz.bk<br /> root@moon44:/boot# ln initrd.img-2.6.27-13-generic initrd.img<br /> root@moon44:/boot# ln vmlinuz-2.6.27-13-generic vmlinuz<br /> &lt;/pre&gt;<br /> <br /> ==LinuxMCE 0710==<br /> '''''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! <br /> <br /> 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.<br /> <br /> 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.<br /> <br /> ====Caveats====<br /> 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.<br /> <br /> ====Alternatives====<br /> 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.<br /> <br /> Example:<br /> cd ~<br /> wget http://www.somesite.com/some_kernel_driver.c<br /> echo obj-m = some_kernel_driver.o &gt; Makefile<br /> cd /lib/modules/2.6.22-14-generic/build<br /> make M=~ modules<br /> ls -l ~/some_kernel_driver.ko<br /> <br /> You may then copy the module to the appropriate directory in the modules tree.<br /> <br /> ===Upgrade process===<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> ====Potential problems====<br /> All the normal issues of upgrading your kernel apply. Always keep your old, working kernel on hand. <br /> <br /> ====Steps====<br /> <br /> =====Recompiling the kernel=====<br /> The first step is to grab the kernel source and extract it to the /usr/src folder.<br /> <br /> cd /usr/src<br /> wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.28.7.tar.bz2<br /> tar -jxvf linux-2.6.28.7.tar.bz<br /> rm linux<br /> ln -s linux-2.6.28.5 linux<br /> <br /> Now lets copy the .config file from our generic 2.6.22 kernel.<br /> cd linux<br /> cp /boot/config-2.6.22-14-generic .config<br /> <br /> 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.<br /> <br /> sudo apt-get install libncurses5 libncurses5-dev qt3-dev-tools libqt3-mt-dev<br /> <br /> Then you can either choose to use the character based interface to set your kernel options<br /> make menuconfig 2&gt; module_errors<br /> <br /> Or you can use the GUI interface<br /> DISPLAY=:0.0 make xconfig<br /> <br /> 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. <br /> <br /> I opted to change these things:<br /> * Selected exact processor family to enable processor optimization extensions<br /> * Selected preemptive kernel (low latency)<br /> * Build SATA driver into kernel<br /> * Build MD,RAID1,RAID5 modules into kernel<br /> * Build NIC module into kernel<br /> * Disabled kernel debugging ('''Note: This is very important if you plan to use this kernel on Media Directors.''')<br /> <br /> 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.<br /> make<br /> sudo make modules_install<br /> <br /> Copy your kernel image to your /boot folder. Create a new initramfs image. Update your menu.lst file.<br /> <br /> cp arch/yyxx/boot/bzImage /boot/vmlinuz-2.6.28.7<br /> mkinitramfs -o /boot/initrd.img-2.6.26.5 2.6.28.7<br /> nano /boot/grub/menu.lst<br /> <br /> 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.<br /> <br /> lsmod &gt; ~/module_list-2.6.22.14<br /> <br /> 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.<br /> <br /> reboot<br /> <br /> =====Additional items which need to be rebuilt=====<br /> 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; 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.<br /> <br /> =====Mythtv=====<br /> 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:<br /> <br /> case &quot;$1&quot; in<br /> start)<br /> if test -e $RUNDIR/$NAME.pid ; then<br /> echo &quot;mythbackend already running, use restart instead.&quot;<br /> else<br /> # set the timeslice to 1/1024 of a sec for smoother mythtv and xine and mplayer playback <br /> if [ -w /proc/sys/dev/rtc/max-user-freq ] # check if RTC (older kernels) exists and I can write to it<br /> # failure is not an option!<br /> then echo 1024 &gt; /proc/sys/dev/rtc/max-user-freq<br /> elif [ -w /proc/sys/dev/hpet/max-user-freq ] # or newer kernels with the High Precision Timer (HPET)<br /> # may or may not emulate the older RTC fully<br /> then echo 1024 &gt; /proc/sys/dev/hpet/max-user-freq<br /> fi # start starting the startup of mythtv <br /> echo -n &quot;Starting $DESC: $NAME &quot; start-stop-daemon --start --pidfile $RUNDIR/$NAME.pid \ <br /> <br /> =====Apparmor=====<br /> 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. <br /> <br /> =====ALSA=====<br /> 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):<br /> mkdir alsa<br /> cd alsa<br /> wget ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.19.tar.bz2<br /> wget ftp://ftp.alsa-project.org/pub/firmware/alsa-firmware-1.0.19.tar.bz2<br /> wget ftp://ftp.alsa-project.org/pub/lib/alsa-lib-1.0.19.tar.bz2<br /> wget ftp://ftp.alsa-project.org/pub/plugins/alsa-plugins-1.0.19.tar.bz2<br /> wget ftp://ftp.alsa-project.org/pub/utils/alsa-utils-1.0.19.tar.bz2<br /> wget ftp://ftp.alsa-project.org/pub/oss-lib/alsa-oss-1.0.17.tar.bz2<br /> for fi in *; do<br /> tar -jxvf $fi<br /> done<br /> cd alsa-driver-1.0.19 <br /> ./configure --with-cards=hda-intel<br /> make<br /> sudo make install<br /> cd ..<br /> 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<br /> cd $fi<br /> ./configure<br /> make<br /> sudo make install<br /> cd ..<br /> done<br /> <br /> =====Asterisk telephony=====<br /> For Asterisk, simply download the latest Zaptel sources. Configure, Make, Install. <br /> wget http://downloads.digium.com/pub/zaptel/zaptel-1.4.12.1.tar.gz<br /> tar -zxvf zaptel-1.4.12.1.tar.gz<br /> cd zaptel-1.4.12.1<br /> ./configure --prefix=/usr<br /> make<br /> sudo make install<br /> <br /> =====LIRC IR control=====<br /> 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.<br /> <br /> 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''.<br /> cd /opt/lirc<br /> wget http://prdownloads.sourceforge.net/lirc/lirc-0.8.4a.tar.bz2<br /> tar -xjvf lirc-0.8.4a.tar.bz2<br /> ./configure --prefix=/usr --with-driver=usbmce2<br /> make<br /> checkinstall<br /> <br /> At this point if you get errors about not being about to overwrite<br /> /usr/lib/liblirc_client.la you may need to<br /> cp /usr/lib/liblirc_client.la /opt/lirc/liblirc_client.la.orig<br /> dpkg --force-overwrite -i lirc_0.8.4a-1_i386.deb<br /> <br /> Proceed with<br /> modprobe lirc_mceusb2<br /> lircd<br /> mode2<br /> Press some buttons on your remote, you should see information appear about the IR being received.<br /> <br /> 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. <br /> cd /usr/src/linux<br /> wget http://lirc.sourceforge.net/software/snapshots/lirc-bttv-linux-2.6.24.patch<br /> patch -p1 &lt; lirc-bttv-linux-2.6.24.patch<br /> cd ..<br /> cvs -z8 -d:pserver:anonymous@lirc.cvs.sourceforge.net:/cvsroot/lirc co lirc<br /> cd lirc-0.8.3<br /> ./configure --prefix=/usr --with-driver=all<br /> make<br /> make install <br /> reboot<br /> <br /> =====Video driver=====<br /> 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.<br /> <br /> For nVidia do this:<br /> wget http://us.download.nvidia.com/XFree86/Linux-x86/177.80/NVIDIA-Linux-x86-177.80-pkg1.run<br /> sh NVIDIA-Linux-x86-177.80-pkg1.run<br /> <br /> 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.<br /> <br /> =====Tuner and other drivers=====<br /> 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.<br /> <br /> ====Media Directors====<br /> 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. <br /> ===Use old kernel===<br /> 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.<br /> <br /> mkdir /tmp/moonfs_64 /tmp/moonfs_32<br /> tar -jxvf /usr/pluto/install/PlutMD-adm64.tar.bz2 /tmp/moonfs_64/<br /> tar -jxvf /usr/pluto/install/PlutMD-i386.tar.bz2 /tmp/moonfs_32/<br /> for md in /usr/pluto/diskless/* /tmp/moonfs_64 /tmp/moonfs_32; do<br /> md_device=`echo &quot;$md&quot; | sed -e 's/.*[/]\([^/]\)/\1/g'`<br /> cd $md/boot<br /> ln -s vmlinuz-2.6.22-14-generic vmlinuz-2.6.26.5<br /> ln -s initrd.img-2.6.22-14-generic initrd.img-2.6.26.5<br /> done<br /> tar -C /tmp/moonfs_64 -jcvpf /usr/pluto/install/PlutoMD-adm64.tar.bz2 .<br /> tar -C /tmp/moonfs_32 -jcvpf /usr/pluto/install/PlutoMD-i386.tar.bz2 .<br /> rm -rf /tmp/moonfs_*<br /> <br /> =====Use new kernel=====<br /> 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. <br /> <br /> These scripts serve as a guideline, and may need to be customized to your unique configuration. <br /> <br /> '''A few notes:'''<br /> * 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.<br /> * 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.<br /> * You should build your video driver files first, so you can include them in your MD archive.<br /> <br /> for md in /usr/pluto/diskless/*; do<br /> md_device=`echo &quot;$md&quot; | sed -e 's/.*[/]\([^/]\)/\1/g'`<br /> cp /boot/vmlinuz-2.6.26.5 $md/boot/<br /> cp /boot/initrd.img-2.6.26.5 $md/boot/<br /> cp -r /lib/modules/2.6.26.5/ $md/lib/modules/<br /> /usr/pluto/bin/Diskless_InstallKernel.sh $md_device<br /> done<br /> /usr/pluto/bin/Diskless_BuildDefaultImage.sh<br /> <br /> <br /> Now rebuild the archives, so future Media Directors will get the correct kernel image. <br /> cd /tmp<br /> mkdir moonfs_x64<br /> cd moonfs_x64<br /> tar -jxvf /usr/pluto/install/PlutMD-adm64.tar.bz2<br /> cp /boot/vmlinuz-2.6.26.5 boot<br /> cp /boot/initrd.img-2.6.26.5 boot<br /> cp -r /lib/modules/2.6.26.5/ lib/modules/<br /> tar -jcvpf /usr/pluto/install/PlutoMD-adm64.tar.bz2 *<br /> cd ..<br /> rm -rf moonfs_x64<br /> <br /> ====Video Drivers====<br /> 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. <br /> <br /> 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.<br /> <br /> stripheader.sh<br /> readsint ()<br /> {<br /> byte=`head -c$2 $1 | tail -c1`<br /> sint=`printf '%u' &quot;'$byte&quot;`<br /> let &quot;sint=$sint &amp; 0xFF&quot;<br /> eval &quot;$3=\&quot;$sint\&quot;&quot;<br /> }<br /> readuint32 ()<br /> {<br /> readsint $1 $(($2+1)) b1<br /> readsint $1 $(($2+2)) b2<br /> readsint $1 $(($2+3)) b3<br /> readsint $1 $(($2+4)) b4 <br /> <br /> uint=$(( ($b4 &lt;&lt; 24) + ($b3 &lt;&lt; 16) + ($b2 &lt;&lt; 8) + $b1 ))<br /> eval &quot;$3=\&quot;$uint\&quot;&quot;<br /> } <br /> <br /> let &quot;header=12&quot;<br /> readuint32 $1 $header int<br /> let &quot;header=$header+$int+4&quot;<br /> readuint32 $1 $header int<br /> let &quot;header=$header+$int+4&quot;<br /> readuint32 $1 $header int<br /> let &quot;header=$header+$int+4&quot;<br /> <br /> precomp=$(stat -c%s &quot;$1&quot;)<br /> let &quot;precomp-=$header&quot;<br /> tail -c$precomp $1 &gt; $2<br /> <br /> <br /> 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.<br /> <br /> wget http://us.download.nvidia.com/XFree86/Linux-x86_64/173.14.12/NVIDIA-Linux-x86_64-173.14.12-pkg2.run<br /> sh NVIDIA-Linux-x86_64-173.14.12-pkg2.run --keep --add-this-kernel<br /> ./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<br /> 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<br /> for md in /usr/pluto/diskless/*; do<br /> cp -r NVIDIA-Linux-x86_64-173.14.12-pkg2/usr/* $md/usr/<br /> cp nvidia.ko $md/lib/modules/2.6.26.5/kernel/drivers/video/<br /> done</div>

Marrandy http://wiki.linuxmce.org/index.php?title=User:Marrandy&diff=9361 2008-03-02T04:06:15Z

<p>Marrandy: </p> <hr /> <div> my current configuration: (work in progress at the moment): I have a lot of parts ie. zoneminder for cameras, asterisk for telephone/VOIP, <br /> security system. I'm trying to bring them together.<br /> <br /> Fiire engine: <br /> <br /> Fiire station (set-top box)<br /> <br /> Orbiters/Remote Controls: 1 x Fiire Chief Remote (I intend to get at least one more with several USB keys), Nokia 6260<br /> <br /> PVR-150, 350, pcHDTV HD-3000, HDhomerun<br /> <br /> USB-UIRT, GC-100-12<br /> <br /> Home Automation: Insteon various. X10 various.<br /> <br /> Camera Setup: 4 x analog cameras: Currently connected to ZoneMinder Server<br /> <br /> Satellite Setup: None at the moment, but I'm looking.</div>

Marrandy http://wiki.linuxmce.org/index.php?title=User:Marrandy&diff=9360 2008-03-02T04:02:57Z

<p>Marrandy: </p> <hr /> <div> my current configuration: (work in progress at the moment): I have a lot of parts ie. zoneminder for cameras, asterisk for telephone/VOIP, <br /> security system. I'm trying to bring them together.<br /> <br /> Fiire engine: <br /> <br /> Fiire station (set-top box)<br /> <br /> Orbiters/Remote Controls: 1 x Fiire Chief Remote (I intend to get at least one more with several USB keys)<br /> <br /> Home Automation: Insteon various. X10 various.<br /> <br /> Camera Setup: 4 x analog cameras: Currently connected to ZoneMinder Server<br /> <br /> Satellite Setup: None at the moment, but I'm looking.</div>

Marrandy http://wiki.linuxmce.org/index.php?title=User:Marrandy&diff=9359 2008-03-02T04:02:14Z

<p>Marrandy: </p> <hr /> <div> my current configuration: (work in progress at the moment): I have a lot of parts ie. zoneminder for cameras, asterisk for telephone/VOIP, <br /> security system. I'm trying to bring them together.<br /> <br /> Fiire engine: <br /> <br /> Fiire station (set-top box)<br /> <br /> Orbiters/Remote Controls: 1 x Fiire Chief Remote (I intend to get at least one more with several USB keys)<br /> <br /> Camera Setup: 4 x analog cameras: Currently connected to ZoneMinder Server<br /> <br /> Satellite Setup: None at the moment, but I'm looking.<br /> <br /> Home Automation:<br /> Insteon various.<br /> X10 various.</div>

Marrandy http://wiki.linuxmce.org/index.php?title=User:Marrandy&diff=9358 2008-03-02T04:01:40Z

<p>Marrandy: </p> <hr /> <div> my current configuration: (work in progress at the moment): I have a lot of parts ie. zoneminder for cameras, asterisk for telephone/VOIP, <br /> security system. I'm trying to bring them together.<br /> <br /> Fiire engine: <br /> <br /> Fiire station (set-top box)<br /> <br /> Orbiters/Remote Controls: 1 x Fiire Chief Remote (I intend to get at least one more with several USB keys)<br /> <br /> Camera Setup: 4 x analog cameras: Currently connected to ZoneMinder Server<br /> <br /> Satellite Setup: None at the moment<br /> <br /> Home Automation:<br /> Insteon various.<br /> X10 various.</div>

Marrandy http://wiki.linuxmce.org/index.php?title=User:Marrandy&diff=9357 2008-03-02T03:58:11Z

<p>Marrandy: </p> <hr /> <div> my current configuration: (work in progress at the moment): I have a lot of parts ie. zoneminder for cameras, asterisk for telephone/VOIP, <br /> security system. I'm trying to bring them together.<br /> <br /> Satellite Setup: None at the moment<br /> <br /> Camera Setup: 4 x analog cameras: Currently connected to ZoneMinder Server<br /> <br /> System Name: DCERouter (Fiire Engine)<br /> OS: Kubuntu Feisty 7.04<br /> Primary App: LinuxMCE Core/Hybrid<br /> <br /> System Name: Fiire Station (set-top box)<br /> <br /> Orbiters/Remote Controls: 1 x Fiire Chief Remote<br /> <br /> Home Automation:<br /> Insteon various.<br /> X10 various.</div>

Marrandy http://wiki.linuxmce.org/index.php?title=User:Marrandy&diff=9356 2008-03-02T03:54:30Z

<p>Marrandy: </p> <hr /> <div> my current configuration: (work in progress at the moment): I have a lot of parts ie. zoneminder for cameras, asterisk for telephone/VOIP, <br /> security system. I'm trying to bring them together.<br /> <br /> Satellite Setup: None at the moment<br /> <br /> Camera Setup: 4 x analog cameras: Currently connected to ZoneMinder Server<br /> <br /> System Name: DCERouter (Fiire Engine)<br /> OS: Kubuntu Feisty 7.04<br /> Primary App: LinuxMCE Core/Hybrid<br /> <br /> System Name: Fiire Station (set-top box)<br /> <br /> Orbiters/Remote Controls:<br /> 1 x Fiire Chief Remotes<br /> <br /> Home Automation:<br /> Insteon various.<br /> X10 various.<br /> X10 wireless Motion Sensors (Hawkeyes)</div>

Marrandy http://wiki.linuxmce.org/index.php?title=User:Marrandy&diff=9355 2008-03-02T03:54:05Z

<p>Marrandy: </p> <hr /> <div> my current configuration: (work in progress at the moment): I have a lot of parts ie. zoneminder for cameras, asterisk for telephone/VOIP, security system. I'm trying to bring them together.<br /> <br /> Satellite Setup: None at the moment<br /> <br /> Camera Setup: 4 x analog cameras: Currently connected to ZoneMinder Server<br /> <br /> System Name: DCERouter (Fiire Engine)<br /> OS: Kubuntu Feisty 7.04<br /> Primary App: LinuxMCE Core/Hybrid<br /> <br /> System Name: Fiire Station (set-top box)<br /> <br /> Orbiters/Remote Controls:<br /> 1 x Fiire Chief Remotes<br /> <br /> Home Automation:<br /> Insteon various.<br /> X10 various.<br /> X10 wireless Motion Sensors (Hawkeyes)</div>

Marrandy http://wiki.linuxmce.org/index.php?title=User:Marrandy&diff=9354 2008-03-02T03:52:22Z

<p>Marrandy: </p> <hr /> <div> my current configuration: (work in progress at the moment)<br /> <br /> Satellite Setup: None at the moment<br /> <br /> Camera Setup: 4 x analog cameras: Currently connected to ZoneMinder Server<br /> <br /> System Name: DCERouter (Fiire Engine)<br /> OS: Kubuntu Feisty 7.04<br /> Primary App: LinuxMCE Core/Hybrid<br /> <br /> System Name: Fiire Station (set-top box)<br /> <br /> Orbiters/Remote Controls:<br /> 1 x Fiire Chief Remotes<br /> <br /> Home Automation:<br /> Insteon various.<br /> X10 various.<br /> X10 wireless Motion Sensors (Hawkeyes)</div>

Marrandy http://wiki.linuxmce.org/index.php?title=User:Marrandy&diff=9353 2008-03-02T03:51:52Z

<p>Marrandy: </p> <hr /> <div> my current configuration: (work in progress at the moment)<br /> <br /> Satellite Setup: None at the moment<br /> <br /> Camera Setup: IP Cameras: 4 x analog cameras Currently connected to ZoneMinder Server<br /> <br /> System Name: DCERouter (Fiire Engine)<br /> OS: Kubuntu Feisty 7.04<br /> Primary App: LinuxMCE Core/Hybrid<br /> <br /> System Name: Fiire Station (set-top box)<br /> <br /> Orbiters/Remote Controls:<br /> 1 x Fiire Chief Remotes<br /> <br /> Home Automation:<br /> Insteon various.<br /> X10 various.<br /> X10 wireless Motion Sensors (Hawkeyes)</div>

Marrandy http://wiki.linuxmce.org/index.php?title=User:Marrandy&diff=9352 2008-03-02T03:49:45Z

<p>Marrandy: </p> <hr /> <div>my current configuration: (work in progress at the moment)<br /> <br /> System Specifications:<br /> <br /> Satellite Setup: <br /> <br /> None at the moment<br /> <br /> Camera Setup:<br /> IP Cameras: 4 x analog cameras<br /> Curently connected to ZoneMinder Server<br /> <br /> System Name: DCERouter (Fiire Engine)<br /> OS: Kubuntu Feisty 7.04<br /> Primary App: LinuxMCE Core/Hybrid<br /> <br /> System Name: Fiire Station (set-top box)<br /> <br /> Orbiters/Remote Controls:<br /> 1 x Fiire Chief Remotes<br /> <br /> Home Automation:<br /> INSTEON various.<br /> X10 various.<br /> X10 wireless Motion Sensors (Hawkeyes)</div>

Marrandy http://wiki.linuxmce.org/index.php?title=User:Marrandy&diff=9351 2008-03-02T03:48:36Z

<p>Marrandy: </p> <hr /> <div>my current configuration: (work in progress at the moment)<br /> <br /> System Specifications:<br /> <br /> Satellite Setup: <br /> <br /> None at the moment<br /> <br /> Camera Setup:<br /> IP Cameras: 3 x analog cameras<br /> Curently connected to ZoneMinder Server<br /> <br /> System Name: DCERouter (Fiire Engine)<br /> Tuner: 1 x PVR-350 MCE<br /> OS: Kubuntu Feisty 7.04<br /> Primary App: LinuxMCE Core/Hybrid<br /> <br /> System Name: Fiire Station (set-top box)<br /> <br /> Orbiters/Remote Controls:<br /> 1 x Fiire Chief Remotes<br /> <br /> Home Automation:<br /> INSTEON various.<br /> X10 various.<br /> X10 wireless Motion Sensors (Hawkeyes)</div>

Marrandy http://wiki.linuxmce.org/index.php?title=User:Marrandy&diff=9350 2008-03-02T03:48:13Z

<p>Marrandy: </p> <hr /> <div>my current configuration: (work in progress at the moment)<br /> <br /> System Specifications:<br /> <br /> Satellite Setup: <br /> <br /> None at the moment<br /> <br /> Camera Setup:<br /> IP Cameras: 3 x analog cameras<br /> <br /> Curently connected to ZoneMinder Server<br /> <br /> System Name: DCERouter (Fiire Engine)<br /> Tuner: 1 x PVR-350 MCE<br /> OS: Kubuntu Feisty 7.04<br /> Primary App: LinuxMCE Core/Hybrid<br /> <br /> System Name: Fiire Station (set-top box)<br /> <br /> Orbiters/Remote Controls:<br /> 1 x Fiire Chief Remotes<br /> <br /> Home Automation:<br /> INSTEON various.<br /> X10 various.<br /> X10 wireless Motion Sensors (Hawkeyes)</div>

Marrandy http://wiki.linuxmce.org/index.php?title=User:Marrandy&diff=9349 2008-03-02T03:48:00Z

<p>Marrandy: </p> <hr /> <div>my current configuration: (work in progress at the moment)<br /> <br /> System Specifications:<br /> <br /> Satellite Setup: <br /> <br /> None at the moment<br /> <br /> Camera Setup:<br /> IP Cameras: 3 x analog cameras<br /> <br /> Curently connected to ZoneMinder Server<br /> <br /> System Name: DCERouter (Fiire Engine)<br /> Tuner: 1 x PVR-350 MCE<br /> OS: Kubuntu Feisty 7.04<br /> Primary App: LinuxMCE Core/Hybrid<br /> <br /> System Name: Fiire Station (set-top box)<br /> <br /> Orbiters/Remote Controls:<br /> 1 x Fiire Chief Remotes<br /> <br /> Home Automation:<br /> INSTEON various.<br /> X10 various.<br /> X10 wireless Motion Sensors (Hawkeyes)</div>

Marrandy http://wiki.linuxmce.org/index.php?title=User:Marrandy&diff=9348 2008-03-02T03:46:55Z

<p>Marrandy: </p> <hr /> <div>my current configuration: (work in progress at the moment)<br /> <br /> System Specifications:<br /> <br /> Satellite Setup: <br /> <br /> None at the moment<br /> <br /> Camera Setup:<br /> IP Cameras: 3 x analog cameras<br /> <br /> Curently connected to ZoneMinder Server<br /> <br /> System Name: DCERouter (Fiire Engine)<br /> Tuner: 1 x PVR-350 MCE<br /> OS: Kubuntu Feisty 7.04<br /> Primary App: LinuxMCE Core/Hybrid<br /> <br /> System Name: Fiire Station (set-top box)<br /> <br /> Orbiters/Remote Controls:<br /> 1 x Fiire Chief Remotes<br /> <br /> Home Automation:<br /> INSTEON various.<br /> X10 various.<br /> X10 wireless Motion Sensors (Hawkeyes)</div>

Marrandy http://wiki.linuxmce.org/index.php?title=User:Marrandy&diff=9347 2008-03-02T03:45:33Z

<p>Marrandy: </p> <hr /> <div>my current configuration: (work in progress at the moment)<br /> <br /> System Specifications:<br /> <br /> Satellite Setup: <br /> <br /> None at the moment<br /> <br /> Camera Setup:<br /> IP Cameras: 3 x analog cameras<br /> <br /> Curently connected to ZoneMinder Server<br /> <br /> System Name: DCERouter (Fiire Engine)<br /> Tuner: 1 x PVR-150 MCE<br /> OS: Kubuntu Feisty 7.04<br /> Primary App: LinuxMCE Core/Hybrid<br /> <br /> System Name: Fiire Station (set-top box)<br /> <br /> Orbiters/Remote Controls:<br /> 1 x Fiire Chief Remotes<br /> <br /> Home Automation:<br /> INSTEON everywhere.<br /> Plethra of older X10 equipment, some still being used<br /> X10 wireless Motion Sensors (Hawkeyes)</div>

Marrandy http://wiki.linuxmce.org/index.php?title=User:Marrandy&diff=9346 2008-03-02T03:41:06Z

<p>Marrandy: </p> <hr /> <div>my current configuration: (work in progress at the moment)&lt;P&gt;<br /> <br /> System Specifications:<br /> &lt;P&gt; <br /> No cable or satelite - pending<br /> &lt;P&gt;<br /> Zoneminder server&lt;BR&gt;<br /> Camera Setup: 4 x color PIR analogs&lt;P&gt;<br /> 3 x X-10 wireless sensors&lt;P&gt;<br /> &lt;P&gt;<br /> Hybrid server: Fiire Engine&lt;P&gt;<br /> Motherboard: 1 x M2N-VM DVI&lt;P&gt;<br /> Case: 1 x TD112 MicroATX Tower-Deesktop Case&lt;P&gt;<br /> CPU: 1 x AMDAthlon X2 Processor BE-2350 AM2&lt;P&gt;<br /> RAM: 2 x DDR2 667Mhz 512MB PC5300 memory&lt;P&gt;<br /> Optical: 1 x Lite-On 20X DVD+/-RW Dual layer&lt;P&gt;<br /> HD: 1 x Hitachi 160GB EIDE 7,200RPM 3.5&quot; H/D&lt;P&gt;<br /> GPU: 1 x Built-in Nvidia GeForce 7050PV&lt;P&gt;<br /> OS: Ubuntu Feisty 7.04&lt;P&gt;<br /> <br /> Primary App: LinuxMCE-0704<br /> API version: <br /> Source code: <br /> SVN branch: <br /> <br /> System Name: Fiire Station (1&quot;) <br /> Display: 15&quot; LCD Touch Screen<br /> <br /> System Name: Fiire Station (2.2&quot;) <br /> Display: 15&quot; LCD Touch Screen<br /> <br /> <br /> <br /> System Name: Laptop (Dan) <br /> Motherboard: Dell Inspiron 9600<br /> CPU: Intel Centrino 1.9Ghz<br /> RAM: 512MB<br /> HD: 100GB<br /> OS: Win XP Home<br /> DVD Burner: built-in<br /> NIC: 10/100TX/802.11g/Bluetooth<br /> <br /> System Name: Laptop (wife) <br /> Motherboard: Macbook (Intel)<br /> CPU: Intel Core Duo<br /> HD: ? <br /> OS: OS X Tiger<br /> RAM: 512MB<br /> Optical: DVD / CDRW combo<br /> Primary App: Wife's Workstation<br /> Mythfrontend (mac)<br /> <br /> System Name: PS3<br /> OS: YDL 5.01<br /> OS: game-os (standard)<br /> Primary App: Upnp Client / child's nexopia.. ;)<br /> System Name: Xbox360 Elite<br /> Primary App: sitting there collecting dust <br /> <br /> System Name: Compaq <br /> Primary App: linuxMCE Media Director<br /> <br /> System Name: Development (Dan) <br /> Motherboard: MS-6380E<br /> CPU: AMD XP2200<br /> RAM: 2G<br /> HD: 2 x ST3200822A 200Gb<br /> Primary App: Development<br /> <br /> System Name: IBM <br /> Motherboard: NetVista<br /> RAM: 1Gb<br /> OS: Ubuntu 6.10<br /> Primary App: ZoneMinder 1.22.2 Server<br /> Primary App: workstation<br /> <br /> System Name: DigiMatrix <br /> OS: PXE ubuntu 7.04<br /> Primary App: Frontend (media Director)<br /> <br /> System Name: Digipos <br /> OS: Ubuntu 7.04 <br /> Primary App: Frontend (media Director)<br /> <br /> Orbiters/Remote Controls: <br /> HP Ipaq 4150<br /> 2 x Fiire Chief Remotes<br /> <br /> Home Automation: <br /> INSTEON everywhere.<br /> Simplehomenet EZBridge<br /> Simplehomenet EZRain1 Sprinkler Controller<br /> Simplehomenet EZIO8SA I/O board<br /> Simplehomener EZX10RF (for legacy X10 controllers, motion sensors, etc)<br /> Smarthome Insteon Software Developer's Kit<br /> Plethra of older X10 equipment, some still being used<br /> X10 wireless Motion Sensors (Hawkeyes)</div>

Marrandy http://wiki.linuxmce.org/index.php?title=User:Marrandy&diff=9345 2008-03-02T03:39:33Z

<p>Marrandy: </p> <hr /> <div>my current configuration: (work in progress at the moment)&lt;P&gt;<br /> <br /> System Specifications:<br /> &lt;P&gt; <br /> No cable or satelite - pending<br /> &lt;P&gt;<br /> Zoneminder server&lt;BR&gt;<br /> Camera Setup: 4 x color PIR analogs&lt;P&gt;<br /> 3 x X-10 wireless sensors&lt;P&gt;<br /> &lt;P&gt;<br /> Hybrid server: Fiire Engine&lt;P&gt;<br /> Motherboard: 1 x M2N-VM DVI&lt;P&gt;<br /> Case: 1 x TD112 MicroATX Tower-Deesktop Case&lt;P&gt;<br /> CPU: 1 x AMDAthlon X2 Processor BE-2350 AM2&lt;P&gt;<br /> RAM: 2 x DDR2 667Mhz 512MB PC5300 memory&lt;P&gt;<br /> Optical: 1 x Lite-On 20X DVD+/-RW Dual layer&lt;P&gt;<br /> HD: 1 x Hitachi 160GB EIDE 7,200RPM 3.5&quot; H/D&lt;P&gt;<br /> GPU: 1 x Built-in Nvidia GeForce 7050PV&lt;P&gt;<br /> OS: Ubuntu Feisty 7.04&lt;P&gt;<br /> <br /> Primary App: LinuxMCE-0704<br /> API version: <br /> Source code: <br /> SVN branch: <br /> <br /> <br /> System Name: Fiire Station (2.2&quot;) <br /> Display: 15&quot; LCD Touch Screen<br /> <br /> <br /> <br /> System Name: Laptop (Dan) <br /> Motherboard: Dell Inspiron 9600<br /> CPU: Intel Centrino 1.9Ghz<br /> RAM: 512MB<br /> HD: 100GB<br /> OS: Win XP Home<br /> DVD Burner: built-in<br /> NIC: 10/100TX/802.11g/Bluetooth<br /> <br /> Orbiters/Remote Controls: <br /> <br /> 1 x Fiire Chief Remotes<br /> <br /> Home Automation: <br /> INSTEON everywhere.<br /> <br /> Plethra of older X10 equipment, some still being used<br /> X10 wireless Motion Sensors (Hawkeyes)</div>

Marrandy http://wiki.linuxmce.org/index.php?title=User:Marrandy&diff=9344 2008-03-02T03:36:16Z

<p>Marrandy: </p> <hr /> <div>my current configuration: (work in progress at the moment)&lt;P&gt;<br /> <br /> System Specifications: <br /> <br /> No cable or satelite - pending<br /> <br /> Zoneminder server<br /> Camera Setup: <br /> 4 x color PIR analogs<br /> 3 x X-10 wireless<br /> <br /> <br /> Hyprid server: Fiire Engine<br /> System Name: <br /> Motherboard: 1 x M2N-VM DVI<br /> Case: 1 x TD112 MicroATX Tower-Deesktop Case<br /> CPU: 1 x AMDAthlon X2 Processor BE-2350 AM2<br /> RAM: 2 x DDR2 667Mhz 512MB PC5300 memory<br /> Optical: 1 x Lite-On 20X DVD+/-RW Dual layer<br /> HD: 1 x Hitachi 160GB EIDE 7,200RPM 3.5&quot; H/D<br /> GPU: 1 x Built-in Nvidia GeForce 7050PV<br /> OS: Ubuntu Feisty 7.04<br /> Primary App: LinuxMCE-0704<br /> API version: <br /> Source code: <br /> SVN branch: <br /> <br /> <br /> System Name: Fiire Station (2.2&quot;) <br /> Display: 15&quot; LCD Touch Screen<br /> <br /> <br /> <br /> System Name: Laptop (Dan) <br /> Motherboard: Dell Inspiron 9600<br /> CPU: Intel Centrino 1.9Ghz<br /> RAM: 512MB<br /> HD: 100GB<br /> OS: Win XP Home<br /> DVD Burner: built-in<br /> NIC: 10/100TX/802.11g/Bluetooth<br /> <br /> Orbiters/Remote Controls: <br /> <br /> 1 x Fiire Chief Remotes<br /> <br /> Home Automation: <br /> INSTEON everywhere.<br /> <br /> Plethra of older X10 equipment, some still being used<br /> X10 wireless Motion Sensors (Hawkeyes)</div>

Marrandy http://wiki.linuxmce.org/index.php?title=Hardware&diff=8517 2008-01-22T03:53:23Z

<p>Marrandy: /* Video Capture Card */</p> <hr /> <div>[[Image:Diagram1.jpg|thumb|right|300px|Connectivity possible with LinuxMCE]]<br /> A basic LinuxMCE system can be set up with relatively modest PC and networking hardware. More advanced (though not necessarily expensive) systems can work with virtually any device that allows some form of input/output control capability. This might be through ethernet, infrared, [http://en.wikipedia.org/wiki/RS-232 RS232] or a home [[:Category:Automation|Automation]] control protocol such as [[X10]].<br /> <br /> * Check out the [[:Category:Hardware|hardware category]] for an organized list of hardware<br /> * Check out the [[:Category:Newbie_Packs|newbie pack category]] for an organized list of newbie packs<br /> * Check out [[LinuxMCE_Products|LinuxMCE Products]] for a list of products made for LinuxMCE<br /> <br /> =LinuxMCE hardware terms=<br /> Here is a list of LinuxMCE-specific hardware terms.<br /> <br /> *[[Core]] - a PC which is the center of your system<br /> *[[Media Director]] - PC devices which are connected to your core and provide<br /> *[[Hybrid]] - a Core and Media Director combined.<br /> *[[Orbiter]] - a user interface to control the system, running on a Media Director or elsewhere, for instance on a lightweight portable device such as a web pad.<br /> <br /> =Minimum Requirements=<br /> ==CPU==<br /> A LinuxMCE core-only machine can be run on a slower CPU such as a P3 if media encoding/decoding is not done on the core but, running the database, web server, and other system services can put reasonable load on your CPU.<br /> <br /> ==Motherboard==<br /> Any Linux-compatible motherboard (95% chance your's will work) will run smoothly, give or take a few features (SPDIF, etc.). See the [[:Category:Mainboards|mainboards category]] for more infornmation and experience with these.<br /> ==RAM==<br /> For a bare minimum core, 256MB+ of RAM is needed. For machines encoding/decoding media and/or running desktop applications 512MB+ is needed for smooth function.<br /> ==Hard Drive==<br /> Your machines' hard drive(s) should be at least 4GB (to install the OS) plus as much as you want for media storage, network-boot images, etc. And you can add as much storage as you want via NAS, other machines, and other storage devices.<br /> ==DVD/CD-ROM==<br /> A DVD drive is required for installing with the Quick Install DVD. Without a DVD-ROM drive, the user is left to the CD install method, which requires a fresh install of Kubuntu 7.04, then a 2CD installation of LinuxMCE.<br /> LinuxMCE also supports the Sony VGP-XL1B(N) (N=1,2,3...) CD/DVD jukebox (drive + changer), as well as the compatible PowerFile models. Those jukeboxes in turn require a FireWire connector on the PC. <br /> =Recommended Specifications=<br /> ==CPU==<br /> Late model single-core or any dual or quad core processor is enough power to run a Core or Media Director.<br /> ==RAM==<br /> 1GB+ RAM should handle most setups. 4GB+ would require 64-bit OS which will be available in 0710.<br /> ==DVD/CD-ROM==<br /> DVD-ROM drive is required for installing using the Quick Install DVD and a DVD+/-RW drive is recommend for backing up media, burning CDs, etc.<br /> Of the available supported CD/DVD jukeboxes, the Sony XL1BN (N=1,2,3...) seem to be the most popular in the community, but they are discontinued by Sony.<br /> <br /> =User Feedback=<br /> Please see the article on [[adding your own hardware]] to the [[:Category:Hardware|Hardware Category]] and help out by contributing your experience with the hardware you have tried. Some more general considerations can be found below, feel free to expand on these with your personal experience as well (don't forget to sign your additions with four '~' characters).<br /> <br /> ==CPU==<br /> * A PIII/733MHz system can encode one video stream using the MPEG-4 codec using 480x480 capture resolution. This does not allow for live TV watching, but does allow for encoding video and then watching it later.<br /> * A developer states that his AMD1800+ system can almost encode two MPEG-4 video streams and watch one program simultaneously.<br /> * A PIII/800MHz system with 512MB RAM can encode one video stream using the RTjpeg codec with 480x480 capture resolution and play it back simultaneously, thereby allowing live TV watching.<br /> * A dual Celeron/450MHz is able to view a 480x480 MPEG-4/3300kbps file created on a different system with 30% CPU usage.<br /> * A P4 2.4GHz machine can encode two 3300Kbps 480x480 MPEG-4 files and simultaneously serve content to a remote frontend.<br /> ==RAM==<br /> <br /> ==FireWire==<br /> You may use the [[Firewire]] output of the [[Motorola DCT6200]] or the [[Motorola SA3250|SA3250]].<br /> ==Video Capture Card==<br /> See the [[:Category:TV Cards|TV Cards Category]] for more information on, and experience with, these devices.<br /> <br /> pcHDTV manufactures and supplies cards just for Linux that provide HDTV and analog, now on their third generation of card, the HD-5500 available from http://www.pchdtv.com/<br /> <br /> The Plextor ConvertX PVR devices are supported through Linux drivers available from http://www.plextor.com/english/support/LinuxSDK.htm. MythTV uses the Plextor to capture hardware encoded MPEG-4, so the host CPU requirements are low.<br /> <br /> [[Hauppauge WinTV-PVR-USB2]] (driver available at http://www.isely.net/pvrusb2/) emulates a PVR-x50 card.<br /> IP Recorder (RTSP, RTS, UDP)<br /> <br /> MPEG-2, MPEG-4 and H.264 internet TS stream recording is supported using the IPTV recorder in MythTV. This recorder expects the channels to be supplied as a m3u playlist. If your DSL/Fiber provider supplies television service, but does not provide a m3u playlist for the channels, you can construct one for your own use. You do not need to download it from the same server as the streams themselves, and can also read it from a file if this is more convenient.<br /> <br /> If your provider uses 5C encryption on a particular channel, you won't be able to get any content.<br /> DBoxII or other devices running Neutrino<br /> <br /> You may use the Ethernet port of an DBoxII or a similar device to capture MPEG2. Your set top box has to be running the Neutrino GUI.<br /> USB Capture Devices.<br /> <br /> ==Sound Card==<br /> The system needs a sound card or an on-board equivalent on the motherboard to play back and in most cases, to record sound. Any sound card that can be operated by the [[ALSA]] (Advanced Linux Sound Architecture) kernel modules will work with MythTV. However, some cards and drivers will provide better quality or compatibility than others. In particular, many audio devices included on motherboards can be problematic.<br /> <br /> The usual practice for capturing the audio associated with the video is to run a cable from an audio output on the video capture card to the Line input on a sound card. However, some video capture cards provide on-board audio capabilities that work with the kernel btaudio module instead, thereby eliminating the need for a cable. This is useful if you will be using multiple capture cards in a single chassis, since each capture card will not need its own sound card. Note that a separate sound card is still required for playback when using btaudio, and that often the audio recorded in this way will be mono only. See the btaudio section for more information.<br /> = See Also =<br /> The [[:Category:Hardware|hardware category]] and it's sub categories.<br /> =External references=<br /> * [[Useful Accessories]]<br /> * [https://wiki.ubuntu.com/HardwareSupport Ubuntu hardware wiki]<br /> * [http://www.mythtv.org/wiki/index.php/Category:Hardware MythTV hardware wiki]<br /> * [http://www.voip-info.org/wiki/view/Asterisk+hardware Asterisk hardware]<br /> * [http://forum.linuxmce.com/index.php?topic=1711.0 Building a New Rig]<br /> * [http://forum.linuxmce.com/index.php?topic=1353.msg8341#msg8341 For those wanting to roll your own box ...]</div>

Marrandy http://wiki.linuxmce.org/index.php?title=User:Marrandy&diff=8090 2007-12-30T21:24:03Z

<p>Marrandy: </p> <hr /> <div>my current configuration: (work in progress at the moment) <br /> System Specifications: <br /> <br /> No cable or sateelite - pending<br /> <br /> Camera Setup: <br /> 4 x color PIR analogs<br /> 3 x X-10 wireless<br /> <br /> Currently connected to ZoneMinder Server.<br /> <br /> Hyprid server: Fiire Engine<br /> System Name: <br /> Motherboard: 1 x M2N-VM DVI<br /> Case: 1 x TD112 MicroATX Tower-Deesktop Case<br /> CPU: 1 x AMDAthlon X2 Processor BE-2350 AM2<br /> RAM: 2 x DDR2 667Mhz 512MB PC5300 memory<br /> Optical: 1 x Lite-On 20X DVD+/-RW Dual layer<br /> HD: 1 x Hitachi 160GB EIDE 7,200RPM 3.5&quot; H/D<br /> GPU: 1 x Built-in Nvidia GeForce 7050PV<br /> OS: Ubuntu Feisty 7.04<br /> Primary App: LinuxMCE-0704<br /> API version: <br /> Source code: <br /> SVN branch: <br /> <br /> <br /> System Name: Fiire Station (2.2&quot;) <br /> Display: 15&quot; LCD Touch Screen<br /> <br /> <br /> <br /> System Name: Laptop (Dan) <br /> Motherboard: Dell Inspiron 9600<br /> CPU: Intel Centrino 1.9Ghz<br /> RAM: 512MB<br /> HD: 100GB<br /> OS: Win XP Home<br /> DVD Burner: built-in<br /> NIC: 10/100TX/802.11g/Bluetooth<br /> <br /> Orbiters/Remote Controls: <br /> <br /> 1 x Fiire Chief Remotes<br /> <br /> Home Automation: <br /> INSTEON everywhere.<br /> <br /> Plethra of older X10 equipment, some still being used<br /> X10 wireless Motion Sensors (Hawkeyes)</div>

Marrandy http://wiki.linuxmce.org/index.php?title=User:Marrandy&diff=8089 2007-12-30T21:11:14Z

<p>Marrandy: </p> <hr /> <div>my current configuration: (work in progress at the moment) <br /> System Specifications: <br /> Satellite Setup: <br /> Antennae: 2 x 60cm eliptical<br /> 2 x 60cm Starchoice<br /> LNB: 4 x Standard LNB<br /> 2 x quad LNB (starchoice)<br /> Switch: 1 x Emp Centauri 9x8 Multiswitch<br /> receivers: 1 x Starchoice PVR-530<br /> 2 x Starchoice DVR-505<br /> 3 x Starchoice DVR-300<br /> <br /> Camera Setup: <br /> IP Cameras: 3 x GS1600H Outdoor Day/night <br /> 1 x GS9403 Pan/Tilt<br /> Curently connected to ZoneMinder Server<br /> <br /> System Name: mythbackend <br /> Motherboard: 1 x nVidia 680iSLI<br /> Case: 1 x 4U Rackmount<br /> CPU: 1 x Intel Core 2 Duo 6600<br /> RAM: 2 x Kingston KVR667D2N5/1G (2G)<br /> Optical: 1 x Samsung SH-S183 sata (DVD RW)<br /> HD: 1 x Seagate ST3320620AS 320GB sata<br /> GPU: 1 x nVidia 7600GT 256MB<br /> DVB-S: 1 x Twinhan VP1022A<br /> DVB-S: 1 x Twinhan VP1020A<br /> OS: Ubuntu Feisty 7.04<br /> Primary App: MythTV Backend<br /> API version: 0.20.20070717-1<br /> Source code: 14158M<br /> SVN branch: mythtv-multirec<br /> <br /> System Name: LinuxMCEdevel (in development) <br /> Motherboard: 1 x nVidea 680iSLI<br /> Case: 1 x 4U Rackmount<br /> CPU: 1 x Intel Core 2 Duo 6400<br /> RAM: 2 x Kingston KVR667D2N5/1G (2G)<br /> Optical: 1 x sata DVD<br /> HD: 2 x Seagate ST3320620AS sata<br /> GPU: 1 x nVidia 7600GT 256MB<br /> DVB-S: 1 x Twinhan VP-1020A<br /> Tuner: 1 x PVR-150 MCE<br /> OS: Kubuntu Feisty 7.04<br /> Primary App: LinuxMCE Backend<br /> Interface:CM11A X10 Computer Interface on ttyS0<br /> <br /> System Name: DCERouter (Fiire Engine) <br /> Tuner: 1 x PVR-150 MCE<br /> OS: Kubuntu Feisty 7.04<br /> Primary App: LinuxMCE Core/Hybrid<br /> Interface:PLM Insteon Powerline Modem on ttyS0<br /> <br /> System Name: Fiire Station (1&quot;) <br /> Display: 15&quot; LCD Touch Screen<br /> <br /> System Name: Fiire Station (2.2&quot;) <br /> Display: 15&quot; LCD Touch Screen<br /> <br /> <br /> <br /> System Name: Laptop (Dan) <br /> Motherboard: Dell Inspiron 9600<br /> CPU: Intel Centrino 1.9Ghz<br /> RAM: 512MB<br /> HD: 100GB<br /> OS: Win XP Home<br /> DVD Burner: built-in<br /> NIC: 10/100TX/802.11g/Bluetooth<br /> <br /> System Name: Laptop (wife) <br /> Motherboard: Macbook (Intel)<br /> CPU: Intel Core Duo<br /> HD: ? <br /> OS: OS X Tiger<br /> RAM: 512MB<br /> Optical: DVD / CDRW combo<br /> Primary App: Wife's Workstation<br /> Mythfrontend (mac)<br /> <br /> System Name: PS3<br /> OS: YDL 5.01<br /> OS: game-os (standard)<br /> Primary App: Upnp Client / child's nexopia.. ;)<br /> System Name: Xbox360 Elite<br /> Primary App: sitting there collecting dust <br /> <br /> System Name: Compaq <br /> Primary App: linuxMCE Media Director<br /> <br /> System Name: Development (Dan) <br /> Motherboard: MS-6380E<br /> CPU: AMD XP2200<br /> RAM: 2G<br /> HD: 2 x ST3200822A 200Gb<br /> Primary App: Development<br /> <br /> System Name: IBM <br /> Motherboard: NetVista<br /> RAM: 1Gb<br /> OS: Ubuntu 6.10<br /> Primary App: ZoneMinder 1.22.2 Server<br /> Primary App: workstation<br /> <br /> System Name: DigiMatrix <br /> OS: PXE ubuntu 7.04<br /> Primary App: Frontend (media Director)<br /> <br /> System Name: Digipos <br /> OS: Ubuntu 7.04 <br /> Primary App: Frontend (media Director)<br /> <br /> Orbiters/Remote Controls: <br /> HP Ipaq 4150<br /> 2 x Fiire Chief Remotes<br /> <br /> Home Automation: <br /> INSTEON everywhere.<br /> Simplehomenet EZBridge<br /> Simplehomenet EZRain1 Sprinkler Controller<br /> Simplehomenet EZIO8SA I/O board<br /> Simplehomener EZX10RF (for legacy X10 controllers, motion sensors, etc)<br /> Smarthome Insteon Software Developer's Kit<br /> Plethra of older X10 equipment, some still being used<br /> X10 wireless Motion Sensors (Hawkeyes)</div>

Marrandy http://wiki.linuxmce.org/index.php?title=Hardware&diff=7685 2007-12-08T05:44:37Z

<p>Marrandy: /* Video Capture Card */</p> <hr /> <div>[[Image:Diagram1.jpg|thumb|right|300px|Connectivity possible with LinuxMCE]]<br /> A basic LinuxMCE system can be set up with relatively modest PC and networking hardware. More advanced (though not necessarily expensive) systems can work with virtually any device that allows some form of input/output control capability. This might be through ethernet, infrared, [http://en.wikipedia.org/wiki/RS-232 RS232] or a home control protocol such as [[X10]].<br /> <br /> * Check out the [[:Category:Hardware|hardware category]] for an organized list of hardware<br /> * Check out [[LinuxMCE_Products|LinuxMCE Products]] for a list of products made for LinuxMCE<br /> <br /> ==LinuxMCE hardware terms==<br /> Here is a list of LinuxMCE-specific hardware terms.<br /> <br /> *[[Core]] - a PC which is the center of your system<br /> *[[Media director]] - PC devices which are connected to your core and provide<br /> *[[Orbiter]] - one or more lightweight portable devices used to control the system<br /> <br /> ==Minimum Requirements==<br /> ===CPU===<br /> A LinuxMCE core-only machine can be run on a slower CPU such as a P3 if media encoding/decoding is not done on the core but, running the database, web server, and other system services can put resonable load on your CPU.<br /> ===Motherboard===<br /> Any Linux-compatible motherboard (95% chance your's will work) will run smoothly, give or take a few features (SPDIF, etc.)<br /> ===RAM===<br /> For a bare minimum core, 256MB+ of RAM is needed. For machines encoding/decoding media and/or running desktop applications 512MB+ is needed for smooth function.<br /> ===Hard Drive===<br /> Your machines' hard drive(s) should be at least 4GB (to install the OS) plus as much as you want for media storage, network-boot images, etc.<br /> ===DVD/CD-ROM===<br /> A DVD drive is required for installing with the Quick Install DVD. Without a DVD-ROM drive, the user is left to the CD install method, which requires a fresh install of Kubuntu 7.04, then a 2CD installation of LinuxMCE.<br /> ==Recommended Specifications==<br /> ===CPU===<br /> Late model single-core or any dual or quad core processor is enough power to run a Core or Media Director.<br /> ===Motherboard===<br /> Any Linux-compatible motherboard. Can have built-in digital audio, Gb networking, HDMI, GPU, etc.<br /> ===RAM===<br /> 1GB+ RAM should handle most setups. 4GB+ would require 64-bit OS which will be available in 0710.<br /> ===Hard Drive===<br /> Most drives today offer more than enough storage space to run LinuxMCE, but you can add as much storage as you want via NAS, other machines, and other storage devices.<br /> ===DVD/CD-ROM===<br /> DVD-ROM drive is required for installing using the Quick Install DVD and a DVD+-RW drive is recommend for backing up media, burning CDs, etc.<br /> <br /> ==User Feedback==<br /> ===CPU===<br /> * A PIII/733MHz system can encode one video stream using the MPEG-4 codec using 480x480 capture resolution. This does not allow for live TV watching, but does allow for encoding video and then watching it later.<br /> * A developer states that his AMD1800+ system can almost encode two MPEG-4 video streams and watch one program simultaneously.<br /> * A PIII/800MHz system with 512MB RAM can encode one video stream using the RTjpeg codec with 480x480 capture resolution and play it back simultaneously, thereby allowing live TV watching.<br /> * A dual Celeron/450MHz is able to view a 480x480 MPEG-4/3300kbps file created on a different system with 30% CPU usage.<br /> * A P4 2.4GHz machine can encode two 3300Kbps 480x480 MPEG-4 files and simultaneously serve content to a remote frontend.<br /> ===FireWire===<br /> You may use the [[Firewire]] output of the [[Motorola DCT6200]] or the [[Motorola SA3250|SA3250]].<br /> ===Video Capture Card===<br /> pcHDTV manufactures and supplies cards just for Linux and is now on its third generation of card, the HD-5500 available from http://www.pchdtv.com/<br /> <br /> The Plextor ConvertX PVR devices are supported through Linux drivers available from http://www.plextor.com/english/support/LinuxSDK.htm. MythTV uses the Plextor to capture hardware encoded MPEG-4, so the host CPU requirements are low.<br /> <br /> [[Hauppauge WinTV-PVR-USB2]] (driver available at http://www.isely.net/pvrusb2/) emulates a PVR-x50 card.<br /> IP Recorder (RTSP, RTS, UDP)<br /> <br /> MPEG-2, MPEG-4 and H.264 internet TS stream recording is supported using the IPTV recorder in MythTV. This recorder expects the channels to be supplied as a m3u playlist. If your DSL/Fiber provider supplies television service, but does not provide a m3u playlist for the channels, you can construct one for your own use. You do not need to download it from the same server as the streams themselves, and can also read it from a file if this is more convenient.<br /> <br /> If your provider uses 5C encryption on a particular channel, you won't be able to get any content.<br /> DBoxII or other devices running Neutrino<br /> <br /> You may use the Ethernet port of an DBoxII or a similar device to capture MPEG2. Your set top box has to be running the Neutrino GUI.<br /> USB Capture Devices.<br /> <br /> ===Sound Card===<br /> The system needs a sound card or an on-board equivalent on the motherboard to play back and in most cases, to record sound. Any sound card that can be operated by the [[ALSA]] (Advanced Linux Sound Architecture) kernel modules will work with MythTV. However, some cards and drivers will provide better quality or compatibility than others. In particular, many audio devices included on motherboards can be problematic.<br /> <br /> The usual practice for capturing the audio associated with the video is to run a cable from an audio output on the video capture card to the Line input on a sound card. However, some video capture cards provide on-board audio capabilities that work with the kernel btaudio module instead, thereby eliminating the need for a cable. This is useful if you will be using multiple capture cards in a single chassis, since each capture card will not need its own sound card. Note that a separate sound card is still required for playback when using btaudio, and that often the audio recorded in this way will be mono only. See the btaudio section for more information.<br /> ==== See Also ====<br /> The [[:Category:Hardware|hardware category]] and it's sub categories.<br /> ==External references==<br /> * [[Useful Accessories]]<br /> * [https://wiki.ubuntu.com/HardwareSupport Ubuntu hardware wiki]<br /> * [http://www.mythtv.org/wiki/index.php/Category:Hardware MythTV hardware wiki]<br /> * [http://www.voip-info.org/wiki/view/Asterisk+hardware Asterisk hardware]<br /> * [http://forum.linuxmce.com/index.php?topic=1711.0 Building a New Rig]<br /> * [http://forum.linuxmce.com/index.php?topic=1353.msg8341#msg8341 For those wanting to roll your own box ...]</div>

Marrandy http://wiki.linuxmce.org/index.php?title=What_hardware_I_will_need&diff=7563 2007-12-05T16:08:15Z

<p>Marrandy: /* A video capture card supported by Linux */</p> <hr /> <div>{| align=&quot;right&quot;<br /> | __TOC__<br /> |}<br /> [[Category: Hardware Lists]]<br /> '''''This page is obsolete/outdated, please use a single page for each piece of hardware and add it to the relevant categories as described here: [[Adding your own hardware]]'''''<br /> {{merge|Hardware}}<br /> <br /> = Hardware requirements =<br /> == Minimum == Standard Definition (SD) DVD and audio (MP3, OGG, etc) player.<br /> * The simple answer is a machine that can install and boot [http://www.kubuntu.com Kubuntu] (presently Feisty Fawn 7.04).<br /> <br /> == Standard == Standard Definition DVR + Audio/Video player<br /> From the [http://www.mythtv.org/docs/mythtv-HOWTO-3.html MythTV Hardware Requirements] page.<br /> === CPU ===<br /> * A PIII/733MHz system can encode one video stream using the MPEG-4 codec using 480x480 capture resolution. This does not allow for live TV watching, but does allow for encoding video and then watching it later.<br /> * A developer states that his AMD1800+ system can almost encode two MPEG-4 video streams and watch one program simultaneously.<br /> * A PIII/800MHz system with 512MB RAM can encode one video stream using the RTjpeg codec with 480x480 capture resolution and play it back simultaneously, thereby allowing live TV watching.<br /> * A dual Celeron/450MHz is able to view a 480x480 MPEG-4/3300kbps file created on a different system with 30% CPU usage.<br /> * A P4 2.4GHz machine can encode two 3300Kbps 480x480 MPEG-4 files and simultaneously serve content to a remote frontend.<br /> <br /> === Firewire (optional) ===<br /> <br /> You may use the [[Firewire]] output of the [[Motorola DCT6200]] or the [[Motorola SA3250|SA3250]]. <br /> <br /> === A video capture card supported by Linux ===<br /> <br /> pcHDTV makes and manufactures cards just for Linux and is now on its third generation of card, the HD-5500 available from http://www.pchdtv.com/<br /> <br /> The Plextor ConvertX PVR devices are supported through Linux drivers available from http://www.plextor.com/english/support/LinuxSDK.htm. MythTV uses the Plextor to capture hardware encoded MPEG-4, so the host CPU requirements are low.<br /> <br /> [[Hauppauge WinTV-PVR-USB2]] (driver available at http://www.isely.net/pvrusb2/) emulates a PVR-x50 card.<br /> IP Recorder (RTSP, RTS, UDP)<br /> <br /> MPEG-2, MPEG-4 and H.264 internet TS stream recording is supported using the IPTV recorder in MythTV. This recorder expects the channels to be supplied as a m3u playlist. If your DSL/Fiber provider supplies television service, but does not provide a m3u playlist for the channels, you can construct one for your own use. You do not need to download it from the same server as the streams themselves, and can also read it from a file if this is more convenient.<br /> <br /> If your provider uses 5C encryption on a particular channel, you won't be able to get any content.<br /> DBoxII or other devices running Neutrino<br /> <br /> You may use the Ethernet port of an DBoxII or a similar device to capture MPEG2. Your set top box has to be running the Neutrino GUI.<br /> USB Capture Devices.<br /> <br /> === Sound card ===<br /> <br /> The system needs a sound card or an on-board equivalent on the motherboard to play back and in most cases, to record sound. Any sound card that can be operated by the [[ALSA]] (Advanced Linux Sound Architecture) kernel modules will work with MythTV. However, some cards and drivers will provide better quality or compatibility than others. In particular, many audio devices included on motherboards can be problematic.<br /> <br /> The usual practice for capturing the audio associated with the video is to run a cable from an audio output on the video capture card to the Line input on a sound card. However, some video capture cards provide on-board audio capabilities that work with the kernel btaudio module instead, thereby eliminating the need for a cable. This is useful if you will be using multiple capture cards in a single chassis, since each capture card will not need its own sound card. Note that a separate sound card is still required for playback when using btaudio, and that often the audio recorded in this way will be mono only. See the btaudio section for more information.<br /> <br /> ==== See Also ====<br /> The [[:Category:Hardware|hardware category]] and it's sub categories.<br /> <br /> == Forum Discussions ==<br /> * [http://forum.linuxmce.com/index.php?topic=1711.0 Building a New Rig]<br /> * [http://forum.linuxmce.com/index.php?topic=1353.msg8341#msg8341 For those wanting to roll your own box ...]</div>

Marrandy http://wiki.linuxmce.org/index.php?title=What_hardware_I_will_need&diff=7562 2007-12-05T16:07:55Z

<p>Marrandy: /* A video capture card supported by Linux */</p> <hr /> <div>{| align=&quot;right&quot;<br /> | __TOC__<br /> |}<br /> [[Category: Hardware Lists]]<br /> '''''This page is obsolete/outdated, please use a single page for each piece of hardware and add it to the relevant categories as described here: [[Adding your own hardware]]'''''<br /> {{merge|Hardware}}<br /> <br /> = Hardware requirements =<br /> == Minimum == Standard Definition (SD) DVD and audio (MP3, OGG, etc) player.<br /> * The simple answer is a machine that can install and boot [http://www.kubuntu.com Kubuntu] (presently Feisty Fawn 7.04).<br /> <br /> == Standard == Standard Definition DVR + Audio/Video player<br /> From the [http://www.mythtv.org/docs/mythtv-HOWTO-3.html MythTV Hardware Requirements] page.<br /> === CPU ===<br /> * A PIII/733MHz system can encode one video stream using the MPEG-4 codec using 480x480 capture resolution. This does not allow for live TV watching, but does allow for encoding video and then watching it later.<br /> * A developer states that his AMD1800+ system can almost encode two MPEG-4 video streams and watch one program simultaneously.<br /> * A PIII/800MHz system with 512MB RAM can encode one video stream using the RTjpeg codec with 480x480 capture resolution and play it back simultaneously, thereby allowing live TV watching.<br /> * A dual Celeron/450MHz is able to view a 480x480 MPEG-4/3300kbps file created on a different system with 30% CPU usage.<br /> * A P4 2.4GHz machine can encode two 3300Kbps 480x480 MPEG-4 files and simultaneously serve content to a remote frontend.<br /> <br /> === Firewire (optional) ===<br /> <br /> You may use the [[Firewire]] output of the [[Motorola DCT6200]] or the [[Motorola SA3250|SA3250]]. <br /> <br /> === A video capture card supported by Linux ===<br /> <br /> pcHDTV makes and manufactures cards just for Linux and is now on its third generation of card, the HD-5500 available from http://www.pchdtv.com/<br /> The Plextor ConvertX PVR devices are supported through Linux drivers available from http://www.plextor.com/english/support/LinuxSDK.htm. MythTV uses the Plextor to capture hardware encoded MPEG-4, so the host CPU requirements are low.<br /> <br /> [[Hauppauge WinTV-PVR-USB2]] (driver available at http://www.isely.net/pvrusb2/) emulates a PVR-x50 card.<br /> IP Recorder (RTSP, RTS, UDP)<br /> <br /> MPEG-2, MPEG-4 and H.264 internet TS stream recording is supported using the IPTV recorder in MythTV. This recorder expects the channels to be supplied as a m3u playlist. If your DSL/Fiber provider supplies television service, but does not provide a m3u playlist for the channels, you can construct one for your own use. You do not need to download it from the same server as the streams themselves, and can also read it from a file if this is more convenient.<br /> <br /> If your provider uses 5C encryption on a particular channel, you won't be able to get any content.<br /> DBoxII or other devices running Neutrino<br /> <br /> You may use the Ethernet port of an DBoxII or a similar device to capture MPEG2. Your set top box has to be running the Neutrino GUI.<br /> USB Capture Devices.<br /> <br /> === Sound card ===<br /> <br /> The system needs a sound card or an on-board equivalent on the motherboard to play back and in most cases, to record sound. Any sound card that can be operated by the [[ALSA]] (Advanced Linux Sound Architecture) kernel modules will work with MythTV. However, some cards and drivers will provide better quality or compatibility than others. In particular, many audio devices included on motherboards can be problematic.<br /> <br /> The usual practice for capturing the audio associated with the video is to run a cable from an audio output on the video capture card to the Line input on a sound card. However, some video capture cards provide on-board audio capabilities that work with the kernel btaudio module instead, thereby eliminating the need for a cable. This is useful if you will be using multiple capture cards in a single chassis, since each capture card will not need its own sound card. Note that a separate sound card is still required for playback when using btaudio, and that often the audio recorded in this way will be mono only. See the btaudio section for more information.<br /> <br /> ==== See Also ====<br /> The [[:Category:Hardware|hardware category]] and it's sub categories.<br /> <br /> == Forum Discussions ==<br /> * [http://forum.linuxmce.com/index.php?topic=1711.0 Building a New Rig]<br /> * [http://forum.linuxmce.com/index.php?topic=1353.msg8341#msg8341 For those wanting to roll your own box ...]</div>

Marrandy http://wiki.linuxmce.org/index.php?title=Main_Page&diff=7135 2007-11-10T19:58:52Z

<p>Marrandy: </p> <hr /> <div>__NOTOC__ __NOEDITSECTION__<br /> &lt;div align=&quot;center&quot;&gt;<br /> &lt;div style=&quot;font-size:175%; font-weight:bold&quot;&gt;The '''[http://linuxmce.org LinuxMCE]''' wiki&lt;/div&gt;<br /> '''Your guide to a smarter home!'''<br /> &lt;/div&gt;<br /> <br /> <br /> {| style=&quot;clear: both; border: 1px solid #aaa; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.5em; float: right; text-align:center&quot;<br /> |'''Screenshots'''<br /> [[Image:MainMenu2.jpg|200px]]&lt;br/&gt;&lt;small&gt;The main menu with media in the background&lt;/small&gt;&lt;br/&gt;&lt;br/&gt;<br /> |-<br /> |[[Image:FileBrowserUI1.jpg|200px]]&lt;br/&gt;&lt;small&gt;Browsing media files&lt;/small&gt;&lt;br/&gt;&lt;br/&gt;<br /> |-<br /> |[[Image:DialNumberUI1.jpg|200px]]&lt;br/&gt;&lt;small&gt;Telephone dial pad&lt;/small&gt;&lt;br/&gt;&lt;br/&gt;[[Screenshots|More screenshots and videos]]<br /> |}<br /> '''LinuxMCE is the only all-in-one open source solution that seamlessly combines:'''<br /> * ''Media &amp; entertainment'' with a server for music and video plus a [[PVR]] like TiVo or Sky+<br /> * ''Home automation'' to control everything from lights to heating with a touch-screen tablet or your mobile phone<br /> * ''Phone system'' with video conferencing<br /> * ''Security system'' that feeds live video to your mobile during a security breach<br /> <br /> [[LinuxMCE|Read more]] to see all the possibilities that LinuxMCE offers.<br /> <br /> LinuxMCE Video hardware link is here http://wiki.linuxmce.org/index.php/Video<br /> <br /> ==Download==<br /> Please take a moment to read about '''[[Known_Issues|known issues]]''' before downloading our ''Quick Install DVD'' or the ''Two-CD Installer''.<br /> <br /> {| cellspacing=5 cellpadding=5 border=0 width=100%<br /> |width=48|{{Click || image=Globe.gif | link=Download_Instructions | width=48px | height=48px }}<br /> |'''[[Download_Instructions|Download LinuxMCE]]'''&lt;br&gt;&lt;small&gt;After checking known issues please download from an appropriate mirror&lt;/small&gt;<br /> |}<br /> <br /> ==Project News==<br /> *[http://www.osweekly.com/index.php?option=com_content&amp;task=view&amp;id=2664 Linux Media Center PCs Review Roundup] ''(4 October)''<br /> *[http://www.news.com/DRM-troubles-drive-ex-Microsoft-employee-to-Linux/2100-1016_3-6210131.html DRM troubles drive ex-Microsoft employee to Linux] ''(26 September)''<br /> *[http://linuxmce.org/news.php?id=10| New SchedulesDirect service for MythTV] ''(31 August)''<br /> *[[Download_Instructions|LinuxMCE 0704 is out!]] ''(7 August)''<br /> <br /> {| cellspacing=5 cellpadding=5 border=0 width=100%<br /> |width=48|{{Click || image=Newspaper.gif | link=LinuxMCE_media_coverage | width=48px | height=48px }}<br /> |'''[[LinuxMCE media coverage|More LinuxMCE media coverage]]'''&lt;br&gt;&lt;small&gt;Third party media and blog coverage&lt;/small&gt;<br /> |}<br /> <br /> ==Support==<br /> {| cellspacing=5 cellpadding=5 border=0 <br /> |width=48|{{Click || image=Manual.gif | link=User Manual | width=48px | height=48px }}<br /> |'''[[User Manual]]'''&lt;br&gt;&lt;small&gt;LinuxMCE User Manual<br /> |width=48|{{Click || image=Guides.gif | link=:Category:Tutorials | width=48px | height=48px }}<br /> |'''[[:Category:Tutorials|Guides]]'''&lt;br&gt;&lt;small&gt;HOWTO guides describing common scenarios<br /> |-<br /> |width=48|{{Click || image=FAQ.gif | link=Frequently Asked Questions | width=48px | height=48px }}<br /> |'''[[Frequently Asked Questions]]'''&lt;br&gt;&lt;small&gt;Responses to the most common questions<br /> |width=48|{{Click || image=Hardware.gif | link=Hardware | width=48px | height=48px }}<br /> |'''[[Hardware]]'''&lt;br&gt;&lt;small&gt;Hardware documentation<br /> |-<br /> |width=48|{{Click || image=Troubleshooting.gif | link=Troubleshooting | width=48px | height=48px }}<br /> |'''[[Troubleshooting]]'''&lt;br&gt;&lt;small&gt;Help with common problems<br /> |width=48|{{UrlClick || image=Mail.gif | link=:Category:Hardware | width=48px | height=48px }}<br /> |'''[http://sourceforge.net/mail/?group_id=166973 Mailing List]'''&lt;br&gt;&lt;small&gt;Stay up to date with regular emails<br /> |-<br /> |width=48|{{UrlClick || image=Forum.gif | link=kjh | width=48px | height=48px }}<br /> |'''[http://forum.linuxmce.com Forum]'''&lt;br&gt;&lt;small&gt;Support forum<br /> |<br /> |<br /> |}<br /> <br /> <br /> ==Development==<br /> {| cellspacing=5 cellpadding=5 border=0<br /> |width=48|{{Click || image=Contacts.gif | link=Contacts | width=48px | height=48px }}<br /> |'''[[Contacts|Contact Information]]'''&lt;br&gt;&lt;small&gt;Contact people involved with the project<br /> |width=48|{{Click || image=Manual.gif | link=Programmer's Guide | width=48px | height=48px }}<br /> |'''[[Programmer's Guide]]'''&lt;br&gt;&lt;small&gt;A guide for software developers<br /> |-<br /> |width=48|{{Click || image=Software.gif | link=Software components | width=48px | height=48px }}<br /> |'''[[Software components|Software Components]]'''&lt;br&gt;&lt;small&gt;Open source software used by LinuxMCE<br /> |width=48|{{Click || image=Bug.gif | link=Bug Reports | width=48px | height=48px }}<br /> |'''[[Bug Reports]]'''&lt;br&gt;&lt;small&gt;Help improve the software by reporting bugs<br /> |-<br /> |width=48|{{Click || image=Binary.gif | link=Source Code | width=48px | height=48px }}<br /> |'''[[Source Code]]'''&lt;br&gt;&lt;small&gt;Access the LinuxMCE source code<br /> |width=48|{{UrlClick || image=CDR.gif | link=Versions | width=48px | height=48px }}<br /> |'''[[Versions]]'''&lt;br&gt;&lt;small&gt;View version histories and changes<br /> |}</div>

Marrandy http://wiki.linuxmce.org/index.php?title=Main_Page&diff=4655 2007-08-15T20:21:36Z

<p>Marrandy: /* FAQ */</p> <hr /> <div>==What is LinuxMCE?==<br /> [http://LinuxMCE.org LinuxMCE] is the only solution seamlessly combining:<br /> # media &amp; entertainment with a server for music, movies and tv shows, plus a PVR and DVD Player,<br /> # a home automation system to control everything in the home with touch-screen tablet and Bluetooth mobile phone controllers,<br /> # a phone system with video conferencing,<br /> # a security system that feeds you live video on your mobile phone when something happens, and lets you speak to visitors through your stereos, and<br /> # a home PC solution.<br /> <br /> A typical LinuxMCE system consists of a '''Core''': one PC acting as a dedicated server and interface with all the sub-components. The Core includes our own plug-and-play back-end so it listens for and auto configures all sorts of devices like network audio players (such as Squeeze Box), IP phones and cameras. The Core automatically exposes a network boot for any other PC's or thin clients you want to use as '''Media Directors''', which you hook up to your TV/Stereo's to use as set top boxes, complete with a media player, PVR, video conferencing, intercom, and a GUI to control everything in the home. All Media Directors work together seamlessly as a total whole-house solution. <br /> <br /> In addition to the usual infrared remote controls, LinuxMCE includes remote control software that runs on Symbian Bluetooth mobile phones as well as Linux, Windows and Windows CE devices like webpads and pda's. They all feature cover art, interactive maps and floor plans, and let you control any device in the house. The UI is skinnable and multi-language. The mobile phone has a &quot;follow-me&quot; feature so your media and other settings follow you from room to room. It switches from Bluetooth to cellular gprs/wap when you leave the house you're always in control.<br /> <br /> __TOC__<br /> <br /> ==News==<br /> ==Features==<br /> <br /> LinuxMCE is an all-in-one solution for your home that seamlessly combines media &amp; entertainment, home automation, security, telecommunications and computing. Browse the [[Features|features page]], along with [[What can I do with LinuxMCE?]] to see the possibilities available from LinuxMCE.<br /> <br /> ==Screenshots==<br /> [[Image:MainMenu2.jpg|left|thumb|UI2 Main Menu]]<br /> [[Image:FileBrowserUI1.jpg|left|thumb|UI1 Media Files Browser]]<br /> [[Image:DialNumberUI1.jpg|none|thumb|UI1 Phone Dial Pad]]<br /> &lt;br&gt;<br /> '''[[screenshots|More screenshots and videos]]'''<br /> <br /> ==Download==<br /> <br /> To get Linux MCE, please download and install Linux MCE installer from the main page of website. After this, please start the &quot;Linux MCE Installer&quot; application - it will download and install required packages.<br /> <br /> ==Getting Started==<br /> <br /> This section has moved to [[Getting Started]].<br /> <br /> ==Support==<br /> <br /> ===User's Manual===<br /> <br /> This section has moved to [[User's Manual]].<br /> <br /> ===Mailing List===<br /> <br /> Support beyond that contained in this wiki can be found via the official LinuxMCE [http://forum.linuxmce.com/index.php forums] and through the available [http://LinuxMCE.com/support/index.php?section=mail mailing lists].<br /> <br /> ===Configuring LinuxMCE===<br /> <br /> [[LinuxMCE Admin Website|Configuring LinuxMCE]]<br /> <br /> [[Users_Page | Users' Documentation]]<br /> <br /> ===FAQ===<br /> *[[What hardware I will need]]<br /> *[[Tested good hardware]]<br /> *[[Tested bad hardware]]<br /> *[[Development status for all modules]]<br /> *[[What does an appliance solution like LinuxMCE cost?]]<br /> *[[Is LinuxMCE an appliance or software solution?]]<br /> *[[Do I need LinuxMCE? Can I use the projects by themselves?]]<br /> *[[How do I login to a Linux console?]]<br /> *[[How are media files organized?]]<br /> *[[I can't access my media files over the network]]<br /> *[[Reset the password for the LinuxMCE Admin site]]<br /> *[[What if you don't have a driver for my home automation device]]<br /> *[[What scenarios are created automatically?]]<br /> *[[I'm a Linux user already. Should I use LinuxMCE's distribution]]<br /> *[[Encrypted DVD's|Why doesn't LinuxMCE support encrypted DVD's?]]<br /> <br /> ===Troubleshooting===<br /> * [[svn default properties]]<br /> * [[Adding new computing apps]]<br /> * [[Installing on a new platform]]<br /> * [[Windows|Installer for Windows]]<br /> * [[Installer Problems]]<br /> <br /> ==Development==<br /> <br /> ===Author's Information===<br /> <br /> Information regarding author information can be found on the LinuxMCE [http://wiki.linuxmce.org/index.php/Contacts contacts] page.<br /> <br /> ===Programmer's Guide===<br /> <br /> There is a great deal of documentation on the LinuxMCE platform available in the [[Programmer's Guide]]. This guide provides an overview of the LinuxMCE architecture, <br /> <br /> ===Software Used by LinuxMCE===<br /> <br /> LinuxMCE is often called a platform for developing smart home modules constructed by a variety of open source projects. The integration of these open source projects, such as [http://xinehq.de Xine], [http://www.mythtv.org Mythtv], and [http://www.asterisk.org Asterisk], can be found in the LinuxMCE Software Documentation.<br /> <br /> [[Documentation by Device Templates]]<br /> <br /> [http://wiki.linuxmce.com/index.php/Doxygen doxygen diagrams]<br /> <br /> LinuxMCE is an open source project and uses open source software. More information regarding LinuxMCE's relationship to open source can be found on the [[Open Source Info|open source information]] page, the [[License| license information]] page, what to do if you're an [http://LinuxMCE.com/index.php?section=developer open source developer], and LinuxMCE's [http://LinuxMCE.com/index.php?section=letter open source strategy].<br /> <br /> ===Report Bugs===<br /> <br /> Bugs may be [http://www.linuxmce.com/mantis/ reported] via the bug tracking system, [http://www.mantisbugtracker.com/ Mantis].<br /> <br /> ===Source===<br /> <br /> LinuxMCE is a pretty big project. Not counting [[GSD]] devices, LinuxMCE's own code is already well over a million lines in hundreds of modules, with over 1,000 pages of online documentation, and in addition LinuxMCE also incorporates lots of other big open source projects like Asterisk, Xine, MythTV, Firefox, VideoLan, SlimServer, etc., all of which have special LinuxMCE 'wrappers' to allow them to work together seamlessly as a total home solution. For the brave of heart, you can also download [http://LinuxMCE.com/support/index.php?section=mainDownload&amp;package=0 modules by hand], and see all the dependencies and compatibility for each module.<br /> <br /> You can browse the [http://linuxmce.svn.sourceforge.net/viewvc/linuxmce/trunk/ web based repository viewer]. Or you can you do an anonymous svn checkout as follows:<br /> <br /> svn co &lt;nowiki&gt;http://&lt;/nowiki&gt;linuxmce.svn.sourceforge.net/svnroot/linuxmce/trunk/''modulename''<br /> <br /> You can checkout all the software with if you use http://linuxmce.svn.sourceforge.net/viewvc/linuxmce/trunk/ as the repository location for the module name, or go to the [http://linuxmce.svn.sourceforge.net/viewvc/linuxmce/trunk/ repository viewer] to find the name of the SVN directory for the module you are interested in.<br /> <br /> Here are short instructions if you want compile your module with svn sources : [[Building_From_Source]].<br /> <br /> === Versions ===<br /> <br /> The current version of Linux MCE is '''0704''', as of August 07, 2007.<br /> <br /> == Short Howto on Wiki ==<br /> <br /> This section has been moved to [[Short Howto on Wiki]].</div>

Marrandy