http://wiki.linuxmce.org/api.php?action=feedcontributions&user=Colinjones&feedformat=atomLinuxMCE - User contributions [en]2024-03-28T10:48:30ZUser contributionsMediaWiki 1.24.1http://wiki.linuxmce.org/index.php?title=Unrecognized_NIC&diff=20105Unrecognized NIC2009-07-28T07:48:19Z<p>Colinjones: /* Caveat */</p>
<hr />
<div>[[Category: Hardware]]<br />
[[Category: Networking]]<br />
[[Category: Troubleshooting]]<br />
[[Category: Tutorials]]<br />
<br />
'''Note''' If you have a r8168 NIC, see the [[r8168]] page first.<br />
<br />
Every now and then, people come along with NICs that are not directly supported by LinuxMCE. Typically when this happens you will see a 'Kernel Panic' during the initial PXE boot process. The following information should help to get even those NICs to work. As an example, the ASUS P5K is used, which is using the Attansic L1 NIC. You may have another chipset used in your NIC which will mean that you need to find out what the chipset is and importantly what kernel module is used to add support for it. Googling the chipset name and the words 'kernel module' will normally throw up some links to help you get the module name. Once you have that information you are ready to follow the simple steps outlined below;<br />
== Modify modules on core ==<br />
To get a NIC to work, you have to modify a file;<br />
sudo <editor-of-choice> /etc/initramfs-tools-interactor/modules<br />
and add a single line for your NICs kernel module. In the above case the name of the module is<br />
atl1<br />
Or for the Marvell Yukon 88E8055 chip for example add;<br />
sky2<br />
After adding the above line (and saving the change of course ;-) ), you have to recreate the initial ramdisk. For 0704 do;<br />
/usr/pluto/bin/Diskless_BuildDefaultImage.sh<br />
or maybe<br />
mkinitramfs -d /etc/initramfs-tools-interactor/ -o /tftpboot/default/initrd<br />
is enough.<br />
<br />
This will create a new initial ramdisk for the first boot of new MDs containing the atl1 module (or in your case for whichever module you have added). Now, the first boot of the diskless MD will succeed and a new diskless media director will be created.<br />
<br />
== Modify the media director initial ramdisk ==<br />
<br />
Note: If your MD is 64 bit capable, but your core is running 32 bit mode LMCE, when the initial MD diskless image is built, it will automatically build a 64 bit image. A 64 bit MD image and 32 bit core is incompatible with running the "chroot" command below. If this your situation, you will need to go to the Wizard->Devices->Media Directors in web admin, before continuing, and edit the Architecture field in the applicable Media Director to say i386 instead of AMD64, hit Update and then Rebuild Image. This will delete the 64 bit image and rebuild the MD's image as 32 bit. This takes a good few minutes to complete<br />
<br />
Note: If you had to follow the R8168 NIC driver article before this article (or had to build/make any other NIC driver before coming here to assign it to your MD), note that the diskless images are created from a compressed archive, not from your core's files. Thus any changes you made, like adding a new <nicdriver>.ko to your /lib/modules/2.6.22-14-generic/kernel/drivers/net will not be present in your new MD image. So you will need to copy these files/changes from your live core image to your new MD image in the same locations, eg...<br />
<br />
sudo cp /lib/modules/2.6.22-14-generic/kernel/drivers/net/r8168.ko /usr/pluto/diskless/''<MD#>''/lib/modules/2.6.22-14-generic/kernel/drivers/net/r8168.ko and<br />
<br />
sudo cp /lib/modules/2.6.22-14-generic/kernel/drivers/net/r8169.ko /usr/pluto/diskless/''<MD#>''/lib/modules/2.6.22-14-generic/kernel/drivers/net/r8169.ko<br />
<br />
To boot this diskless MD later on, the configuration for this new device has to be modified to include the above line as well. Look in the directory structure under /usr/pluto/diskless. Each media director has a directory named with the ID of the director in here. Go into the /usr/pluto/diskless/<mediadirector-id>/etc and edit the file modules to also contain<br />
atl1<br />
<br />
Also, go into '''/usr/pluto/diskless/<mediadirector-id>/etc/initramfs-tools''' and put the line into a file called modules. After this, chroot into the directory of the media directory, and re-create the initial ramdisk.<br />
<br />
To create a new initial ram disk the command is<br />
cd /usr/pluto/diskless/<br />
chroot <mediadirector-id><br />
depmod<br />
cd /boot<br />
mkinitramfs -o initrd.img-`uname -r` `uname -r`<br />
exit<br />
<br />
Now reboot your media director. Everything should come up, the way it is meant to.<br />
<br />
== Caveat ==<br />
Whenever you click Regenerate this media director, you have to redo the step for the initial ramdisk of the media director.<br />
The above steps do not work, if the media director and the core utilize two different CPU architectures,ie. one is using AMD64 the other i386 (chroot won't work). Note - AMD64 does not necessarily imply an AMD CPU, it just means the CPU is in 64 bit mode. An Intel CPU can just as easily be AMD64, and vice versa for i386, it can be an AMD CPU, just in 32 bit mode. i386=32bit mode; AMD64=64bit mode, it says nothing about the CPU manufacturer.</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Unrecognized_NIC&diff=20104Unrecognized NIC2009-07-28T07:46:22Z<p>Colinjones: /* Modify the media director initial ramdisk */</p>
<hr />
<div>[[Category: Hardware]]<br />
[[Category: Networking]]<br />
[[Category: Troubleshooting]]<br />
[[Category: Tutorials]]<br />
<br />
'''Note''' If you have a r8168 NIC, see the [[r8168]] page first.<br />
<br />
Every now and then, people come along with NICs that are not directly supported by LinuxMCE. Typically when this happens you will see a 'Kernel Panic' during the initial PXE boot process. The following information should help to get even those NICs to work. As an example, the ASUS P5K is used, which is using the Attansic L1 NIC. You may have another chipset used in your NIC which will mean that you need to find out what the chipset is and importantly what kernel module is used to add support for it. Googling the chipset name and the words 'kernel module' will normally throw up some links to help you get the module name. Once you have that information you are ready to follow the simple steps outlined below;<br />
== Modify modules on core ==<br />
To get a NIC to work, you have to modify a file;<br />
sudo <editor-of-choice> /etc/initramfs-tools-interactor/modules<br />
and add a single line for your NICs kernel module. In the above case the name of the module is<br />
atl1<br />
Or for the Marvell Yukon 88E8055 chip for example add;<br />
sky2<br />
After adding the above line (and saving the change of course ;-) ), you have to recreate the initial ramdisk. For 0704 do;<br />
/usr/pluto/bin/Diskless_BuildDefaultImage.sh<br />
or maybe<br />
mkinitramfs -d /etc/initramfs-tools-interactor/ -o /tftpboot/default/initrd<br />
is enough.<br />
<br />
This will create a new initial ramdisk for the first boot of new MDs containing the atl1 module (or in your case for whichever module you have added). Now, the first boot of the diskless MD will succeed and a new diskless media director will be created.<br />
<br />
== Modify the media director initial ramdisk ==<br />
<br />
Note: If your MD is 64 bit capable, but your core is running 32 bit mode LMCE, when the initial MD diskless image is built, it will automatically build a 64 bit image. A 64 bit MD image and 32 bit core is incompatible with running the "chroot" command below. If this your situation, you will need to go to the Wizard->Devices->Media Directors in web admin, before continuing, and edit the Architecture field in the applicable Media Director to say i386 instead of AMD64, hit Update and then Rebuild Image. This will delete the 64 bit image and rebuild the MD's image as 32 bit. This takes a good few minutes to complete<br />
<br />
Note: If you had to follow the R8168 NIC driver article before this article (or had to build/make any other NIC driver before coming here to assign it to your MD), note that the diskless images are created from a compressed archive, not from your core's files. Thus any changes you made, like adding a new <nicdriver>.ko to your /lib/modules/2.6.22-14-generic/kernel/drivers/net will not be present in your new MD image. So you will need to copy these files/changes from your live core image to your new MD image in the same locations, eg...<br />
<br />
sudo cp /lib/modules/2.6.22-14-generic/kernel/drivers/net/r8168.ko /usr/pluto/diskless/''<MD#>''/lib/modules/2.6.22-14-generic/kernel/drivers/net/r8168.ko and<br />
<br />
sudo cp /lib/modules/2.6.22-14-generic/kernel/drivers/net/r8169.ko /usr/pluto/diskless/''<MD#>''/lib/modules/2.6.22-14-generic/kernel/drivers/net/r8169.ko<br />
<br />
To boot this diskless MD later on, the configuration for this new device has to be modified to include the above line as well. Look in the directory structure under /usr/pluto/diskless. Each media director has a directory named with the ID of the director in here. Go into the /usr/pluto/diskless/<mediadirector-id>/etc and edit the file modules to also contain<br />
atl1<br />
<br />
Also, go into '''/usr/pluto/diskless/<mediadirector-id>/etc/initramfs-tools''' and put the line into a file called modules. After this, chroot into the directory of the media directory, and re-create the initial ramdisk.<br />
<br />
To create a new initial ram disk the command is<br />
cd /usr/pluto/diskless/<br />
chroot <mediadirector-id><br />
depmod<br />
cd /boot<br />
mkinitramfs -o initrd.img-`uname -r` `uname -r`<br />
exit<br />
<br />
Now reboot your media director. Everything should come up, the way it is meant to.<br />
<br />
== Caveat ==<br />
Whenever you click Regenerate this media director, you have to redo the step for the initial ramdisk of the media director.<br />
The above steps do not work, if the media director and the core utilize two different CPU architectures,ie. one is using AMD64 the other i386 (chroot won't work).</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Unrecognized_NIC&diff=20103Unrecognized NIC2009-07-28T07:44:41Z<p>Colinjones: /* Modify the media director initial ramdisk */ added caveats about if you have 64/32 bit CPUs in MD and core, and to copy over any modified modules from core to MD if you added/created/modified any</p>
<hr />
<div>[[Category: Hardware]]<br />
[[Category: Networking]]<br />
[[Category: Troubleshooting]]<br />
[[Category: Tutorials]]<br />
<br />
'''Note''' If you have a r8168 NIC, see the [[r8168]] page first.<br />
<br />
Every now and then, people come along with NICs that are not directly supported by LinuxMCE. Typically when this happens you will see a 'Kernel Panic' during the initial PXE boot process. The following information should help to get even those NICs to work. As an example, the ASUS P5K is used, which is using the Attansic L1 NIC. You may have another chipset used in your NIC which will mean that you need to find out what the chipset is and importantly what kernel module is used to add support for it. Googling the chipset name and the words 'kernel module' will normally throw up some links to help you get the module name. Once you have that information you are ready to follow the simple steps outlined below;<br />
== Modify modules on core ==<br />
To get a NIC to work, you have to modify a file;<br />
sudo <editor-of-choice> /etc/initramfs-tools-interactor/modules<br />
and add a single line for your NICs kernel module. In the above case the name of the module is<br />
atl1<br />
Or for the Marvell Yukon 88E8055 chip for example add;<br />
sky2<br />
After adding the above line (and saving the change of course ;-) ), you have to recreate the initial ramdisk. For 0704 do;<br />
/usr/pluto/bin/Diskless_BuildDefaultImage.sh<br />
or maybe<br />
mkinitramfs -d /etc/initramfs-tools-interactor/ -o /tftpboot/default/initrd<br />
is enough.<br />
<br />
This will create a new initial ramdisk for the first boot of new MDs containing the atl1 module (or in your case for whichever module you have added). Now, the first boot of the diskless MD will succeed and a new diskless media director will be created.<br />
<br />
== Modify the media director initial ramdisk ==<br />
<br />
Note: If your MD is 64 bit capable, but your core is running 32 bit mode LMCE, when the initial MD diskless image is built, it will automatically build a 64 bit image. A 64 bit MD image and 32 bit core is incompatible with running the "chroot" command below. If this your situation, you will need to go to the Wizard->Devices->Media Directors in web admin, before continuing, and edit the Architecture field in the applicable Media Director to say i386 instead of AMD64, hit Update and then Rebuild Image. This will delete the 64 bit image and rebuild the MD's image as 32 bit. This takes a good few minutes to complete<br />
<br />
Note: If you had to follow the R8168 NIC driver article before this article (or had to build/make any other NIC driver before coming here to assign it to your MD), note that the diskless images are created from a compressed archive, not from your core's files. Thus any changes you made, like adding a new <nicdriver>.ko to your /lib/modules/2.6.22-14-generic/kernel/drivers/net will not be present in your new MD image. So you will need to copy these files/change from your live core image to your new MD image in the same locations, eg...<br />
<br />
sudo cp /lib/modules/2.6.22-14-generic/kernel/drivers/net/r8168.ko /usr/pluto/diskless/''<MD#>''/lib/modules/2.6.22-14-generic/kernel/drivers/net/r8168.ko and<br />
sudo cp /lib/modules/2.6.22-14-generic/kernel/drivers/net/r8169.ko /usr/pluto/diskless/''<MD#>''/lib/modules/2.6.22-14-generic/kernel/drivers/net/r8169.ko<br />
<br />
To boot this diskless MD later on, the configuration for this new device has to be modified to include the above line as well. Look in the directory structure under /usr/pluto/diskless. Each media director has a directory named with the ID of the director in here. Go into the /usr/pluto/diskless/<mediadirector-id>/etc and edit the file modules to also contain<br />
atl1<br />
<br />
Also, go into '''/usr/pluto/diskless/<mediadirector-id>/etc/initramfs-tools''' and put the line into a file called modules. After this, chroot into the directory of the media directory, and re-create the initial ramdisk.<br />
<br />
To create a new initial ram disk the command is<br />
cd /usr/pluto/diskless/<br />
chroot <mediadirector-id><br />
depmod<br />
cd /boot<br />
mkinitramfs -o initrd.img-`uname -r` `uname -r`<br />
exit<br />
<br />
Now reboot your media director. Everything should come up, the way it is meant to.<br />
<br />
== Caveat ==<br />
Whenever you click Regenerate this media director, you have to redo the step for the initial ramdisk of the media director.<br />
The above steps do not work, if the media director and the core utilize two different CPU architectures,ie. one is using AMD64 the other i386 (chroot won't work).</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Where_to_Buy&diff=19957Where to Buy2009-07-17T14:11:27Z<p>Colinjones: /* Australia */ update sites</p>
<hr />
<div>[[Category: Hardware| ]]<br />
{| align="right"<br />
| __TOC__<br />
|}<br />
This is '''not''' meant as an endorsement, but the question of where to buy certain things pops up regularly. Some of this equipment can be hard to find locally, so help out and add your own suppliers to the list if they aren't already there and either way feel free to add a line with your experience. <br />
<br />
''Please add countries alphabetically, and append new stores to the bottom of the lists in order to keep things organized, thank you and good luck with that shopping list!''<br />
<br />
== Africa ==<br />
<br />
== America ==<br />
<br />
=== United States ===<br />
;'''Fiire''' ([http://www.fiire.com/ english]) :''The'' remote, and also core/media director hardware.<br /><br />
;'''Mi Casa Verde''' ([http://shop.micasaverde.com/ english]) :Z-Wave home Automation devices including a new Z-Wave USB interface + inclusion controller in one, and surveillance cameras. Also, a low-cost LinuxMCE-compatible core combined with a Wi-Fi access point.<br /><br />
;'''Smarthome''' ([http://wwww.smarthome.com english]) :Home Automation supplies including Insteon, X10, and Zwave and more custom components as well.<br /><br />
;'''Provantage''' ([http://www.provantage.com/ english]) :Computing parts and accessory superstore.<br /><br />
;'''NewEgg''' ([http://www.newegg.com/ english]) :Computing parts and accessories.<br /><br />
;'''Mini-ITX''' ([http://www.mini-itx.com/store/?c=27 english]) :Thin Clients utilizing their small motherboard technology.<br /><br />
<br />
== Asia ==<br />
<br />
== Australia ==<br />
;'''Static Ice''' ([http://www.staticice.com.au]) :By far the best "Best Price" site for several hundred different computer/electronics equipment retailers in Australia.<br />
<br />
== Europe ==<br />
<br />
=== Belgium ===<br />
;'''IntelliHome''' Domotica Shop ([http://www.intellihome.be/ multi]/[http://www.intellihome.be/english/home.asp english]/[http://www.intellihome.be/nederlands/home.asp dutch]/[http://www.intellihome.be/francais/home.asp french]/[http://www.intellihome.be/deutsch/home.asp german]) :Marmitek X10 Home Automation/Security Products, European shipping<br />
;'''Voipsolutions''' ([http://www.voipsolutions.be/ english]/[http://www.voipsolutions.be/language/fr french]/[http://www.voipsolutions.be/language/nl dutch]) :All kinds of VoIP related hardware solutions.<br />
<br />
=== Denmark ===<br />
;'''Seluxit'''<br />
:([http://www.seluxit.com english]) Z-wave products incl. <br />
:[http://shop.seluxit.com/catalog/product_info.php?currency=EUR&products_id=30 multi-sensor] [http://shop.seluxit.com/catalog/product_info.php?currency=EUR&products_id=29 usb homecontroller]<br />
:Not yet tested.<br />
;'''Innovus''' ([http://www.innovus.dk/ danish]/[http://www.innovus.eu english]) <br />
:Z-wave products<br />
:Not yet tested.<br />
;'''ElectronicHouseKeeper''' ([http://www.electronichousekeeper.com danish])<br />
:Their own line of Z-wave products<br />
:Not yet tested.<br />
;'''Homee''' ([http://www.homee.dk/index.php/en English])<br />
: A Shop with lots of products, new coming every week (almost)<br />
<br />
=== Germany ===<br />
;'''Schalterversand''' ([http://www.schalterversand.de german]) :Z-Wave switches and much more, cheap and fast.<br />
;'''DVBShop''' ([http://www.dvbshop.net english]) :Everything you need for DVB (Cable, Sattelite or Terrestrial) digital television, worldwide shipping.<br />
;'''Zwave4u''' ([http://www.zwave4u.de german]) <br />
:Z-wave products. Accepts Paypal.<br />
:Not yet tested.<br />
;'''Merten''' ([http://www.merten.de german]) :Own line of Z-wave products.<br />
;'''Firma ENS Elektronetshop''' ([http://www.elektronetshop.de german]) <br />
:Merten stuff <br />
:Best price found on Sep 9, 2008<br />
;'''Voltus Elektro Shop''' ([http://www.voltus.de german]) <br />
:Merten stuff <br />
:Also cheaper than official Merten prices, but I found service to be severely lacking (very, very unresponsive!). Summer 2008.<br />
;'''Duewi''' ([http://www.duewi.de german]) <br />
:They have their own line of Z-wave products.<br />
:No online shop.<br />
;'''FINE-BUY''' ([http://www.fine-buy.de/ german]) <br />
:They have some touchscreens.<br />
:the 12.1" (http://www.fine-buy.de/shop/product_info.php?cPath=3_30_64&products_id=159) works fine: [[Egalax-Touchscreen]]<br />
;'''EDI Shop''' ([http://www.edi-shop.de german]) <br />
:EnOcean home automation<br />
<br />
=== Italy ===<br />
;'''Z-wave Europe''' ([http://www.z-wave-europe.org/ italian]) :Z-wave product list for Europe and website links.<br />
<br />
=== Netherlands ===<br />
;'''ElekHomica''' ([http://www.elekhomica.nl/ dutch]/[http://www.elekhomica.nl/infopage2.php?language=nn english])<br />
:X10 and Zwave, even remote controlled curtainrail! EU shipping (curtainrail NL/BE only).<br />
:Quick and painless delivery.<br />
;'''ALTERNATE''' Computerversand ([http://www.alternate.nl/ dutch]) <br />
:[http://www.alternate.nl/html/productDetails.html?artno=NMZV62 airmouse] and lots of regular PC hardware, <br />
:Usually slow on delivery.<br />
;'''iHabitat''' Home automation ([http://www.ihabitat.nl/ dutch])<br />
:[http://www.ihabitat.nl/html/global_cache.html gc100] <br />
:A bit slow to respond to the inquiry, but fast no-nonsense delivery.<br />
;'''MyPowerShop''' ([http://www.mypowershop.eu dutch]) <br />
:X10 and Z-wave products. Accepts Paypal<br />
:Not yet tested<br />
<br />
=== Norway ===<br />
;'''Tronika aka Smarthus''' ([http://www.smarthus.info/ norwegian]) <br />
:Z-wave products incl. [http://www.smarthus.info/product_info.php?cPath=1_46_115&products_id=2248 usb homecontroller]<br />
:Not yet tested<br />
<br />
=== Sweden ===<br />
;'''Eliving''' ([http://www.eliving.se swedish]) <br />
:Z-wave products incl. [http://www.eliving.se/product_info.php?cPath=21_29&products_id=72 usb homecontroller]<br />
:Not yet tested<br />
<br />
=== United Kingdom ===<br />
;'''Convergent Home Technologies - The Digital Home Specialists''' ([http://www.chtukltd.co.uk English])<br />
:Core/Hybrids built & tested to order (AM2/nVidia, Intel)<br />
:MD's built & tested (AM2/nVidia, AM2/ATI, Intel)<br />
:Z-wave - full range of European units<br />
:lmce-0710 software pre-installed & configured on all Core/Hybrids<br />
:Full after sales support provided<br />
:Will Ship Worldwide (but not currently to the US)<br />
;'''Let's automate''' ([http://www.letsautomate.com/index.cfm english]) <br />
:ZWave home automation<br />
;'''Let's automate''' ([http://www.enoceanshop.co.uk] english) <br />
:EnOcean home automation<br />
;'''High Tech Pad''' ([http://www.hightechpad.com] english) <br />
:Z-Wave, USB UIRTs, Bluetooth - Europe-wide Shipping.<br />
;'''UK Automation''' ([http://www.uk-automation.co.uk english])<br />
:X10 stuff from Marmitek<br />
<br />
=== Czech Republic ===<br />
<br />
;'''POWERHOUSE''' ([http://www.powerhouse.eu/ english])<br />
<br />
:Wide range of X10 devices for home automation, security, video surveillance and multimedia. Sipping is available for EU countries.</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Community&diff=19497Community2009-06-27T01:51:48Z<p>Colinjones: </p>
<hr />
<div>Right, having looked at the detail in this post [http://forum.linuxmce.org/index.php?topic=8411.0] i felt its time to see what we are made of as a community, please add your details.<br />
<br />
<br />
GUIDE: copy'n'paste the following lines then append them into the table below (prior to the final line that contains '|}'). This formatting should make it easier for the 'big 5' to work out who can contribute what...<br />
<pre><br />
| Your username<br />
| Your relevant expertise/experience <br />
| Your other experience/expertise<br />
| Your approx time available for the project<br />
| Your time zone or location<br />
| Your particular interest area (if any)<br />
|-<br />
</pre><br />
<br />
<br />
<br />
{| border="1"<br />
!Username<br />
!Relevant expertise/experience<br />
!Other Experience/Expertise<br />
!Time available for the project<br />
!Time zone or location<br />
!Particular Interest Area (If any)<br />
|-<br />
| Geekyhawkes<br />
| advanced newbie<br />
| use to some C+/linux/ubuntu/ html / xml / flash<br />
| few evenings a week<br />
| UK GMT<br />
| User documentation, newbie guides, website design , wiki topics and guides. Line by line intros to get 810 up and running regardless of user experiance.<br />
|-<br />
| tmoore<br />
| advanced newbie<br />
| 14 yrs software product management, IT management consulting, marketing, network & systems management, UNIX admin<br />
| about 3 hrs a week on average<br />
| GMT-7<br />
| Product strategy, team management,(non-technical) marketing & communications<br />
|-<br />
| qball4<br />
| regular user<br />
| HADesigner, graphic design, hardware a/v distribution systems<br />
| average 20-40 hrs/wk available<br />
| US CST<br />
| User Interface, new orbiter platforms<br />
|-<br />
| Fastie81<br />
| advanced newbie<br />
| work with linux/Red Hat/ubuntu day to day / Project Manager / Systems Administrator / Quick Learner<br />
| My work load goes up and down so would have few days one week and none another<br />
| GMT +12 (NZ)<br />
| User Documentation, guides, wiki guides. I would like to learn some coding. Adding Hardware support ,Devices Templates.<br />
|-<br />
| Techstyle<br />
| Advanced Newbie<br />
| System builder, Linux newbie, some Wiki writing experience / PMP (Project Management Professional), MBA, Mechanical Engineer, Entrepreneur<br />
| 1hr per day<br />
| US central (Milwaukee, WI)<br />
| Anything structured<br />
|-<br />
| nite_man<br />
| regular user<br />
| Integrator, consultant, GSD, Ruby, Maemo Orbiter / More then 10 years of software development - Perl, PHP, Linux sysadmin<br />
| 2-4 hours per day<br />
| UTC+2:00 Nicosia, Cyprus<br />
| Admin site, Maemo Orbiter, posting news, blogging, Russian translation<br />
|-<br />
| Daballiemo<br />
| regular user<br />
| Worked my way through Linux/Ubuntu/Fedora mainly on virtualization / Working within MOD and about 15 years of exp. with "paper" documentation<br />
| About 3-6 hours a week<br />
| GMT +1, Amsterdam<br />
| Virtualization and interfacing (webui, remote, keyboard, touch aso)<br />
|-<br />
| SteveC<br />
| LMCE Newbie but keen to get cracking.<br />
| Electronics/Software Engr, C/C++ for 15years.<br />
| Approx 5 hours/week<br />
| UTC+10:00 Brisbane, Australia<br />
| Main interests relate to external hardware interfaces eg. Clipsal CBUS lighting, Caddx/Networx Alarm system.<br />
|-<br />
| Lemming86_au<br />
| Advanced Newbie<br />
| IT Consultant, Network Engineer, Asterisk Admin (No programming experience, yet)<br />
| 3-5 hours/Week<br />
| UTC+9:30 Adelaide, Australia<br />
| Asterisk<br />
|-<br />
| castlec<br />
| LMCE Noob. Linux regular user/noob<br />
| Java Dev, C++ trained (University).<br />
| 3-5 hours/Week<br />
| UTC-5 Ohio, USA<br />
| <br />
|-<br />
| ZuG<br />
| Regular User<br />
| Linux, PHP and a bit of C. Very familiar with Asterisk and OpenVPN<br />
| 3-5 hours/Week<br />
| GMT Cardiff, United Kingdom<br />
| OpenVPN development<br />
|-<br />
| ccoudsi<br />
| Regular user <br />
| 15+ years embedded hardware design, 8+ years engineering manager, Assembly, C, Perl, Ruby (newbie)<br />
| 5-8 hours a week<br />
| UTC-08 PT<br />
| Security Panels<br />
|-<br />
| colinjones<br />
| Regular User<br />
| Bit of bash, some simple coding, learning C++, familiar with the DCE system<br />
| ~15-20 hours/Week<br />
| UTC+10, Sydney, Australia<br />
| LMCE!<br />
|-<br />
|}</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Building_From_Source&diff=19363Building From Source2009-06-10T05:59:05Z<p>Colinjones: /* Building for 0810 */</p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
[[Category: Tutorials]]<br />
[[Category:Development]]<br />
[[Category:Programmer's Guide]]<br />
= Building for 0810 =<br />
Please see [[Building_LinuxMCE_0810|Building LinuxMCE 0810]]<br />
<br />
= Building for 0804 =<br />
Please see [[Building_LinuxMCE]]<br />
<br />
= Building on 0710 =<br />
See also: [[Setting Up A Development Environment]]<br />
== Preparations ==<br />
Set up a directory for the development tree. For example type the following in a shell as "linuxmce" user:<br />
cd /usr/src<br />
sudo mkdir lmce<br />
sudo chown linuxmce lmce<br />
cd lmce<br />
<br />
Install Subversion<br />
sudo apt-get install subversion<br />
<br />
Fetch the source:<br />
svn co http://svn.linuxmce.org/svn/branches/LinuxMCE-0710/<br />
<br />
Copy the libraries needed for to bootstrap:<br />
cp /usr/pluto/lib/* trunk/src/lib<br />
<br />
Run configure:<br />
cd trunk<br />
./configure<br />
<br />
For the svn.linuxmce.org source there is no configure script yet. Run these to prepare bootstrapping:<br />
find . -iname Makefile -exec sed -e 's/<-mkr_t_compile_defines->/-DKDE_LMCE -DDEBUG -DTHREAD_LOG -DLOG_ALL_QUERIES -I\/opt\/libxine1-pluto\/include -I\/opt\/libsdl1.2-1.2.7+1.2.8cvs20041007\/include -I\/opt\/libsdl1.2-1.2.7+1.2.8cvs20041007\/include\/SD/' -i '{}' \;<br />
find . -iname Makefile -exec sed -e 's/<-mkr_t_compile_libs->/-L\/opt\/libxine1-pluto\/lib -L\/opt\/libsdl1.2-1.2.7+1.2.8cvs20041007\/lib/' -i '{}' \;<br />
<br />
== Building ==<br />
Run make:<br />
make<br />
<br />
== Building UpdateMedia ==<br />
Since 7.10 does not use configure, it can be tough getting the entire tree to build. If all you need to build is UpdateMedia (for example), save yourself some trouble and just build that component. For the specific case of UpdateMedia, here are the steps to build based on a 7.10 DVD install and after following the above instructions:<br />
<br />
Install mysqlclient-dev:<br />
sudo apt-get install libmysqlclient15-dev<br />
<br />
Install attr-dev:<br />
sudo apt-get install attr-dev<br />
<br />
Install taglib. Download version 1.5 from http://developer.kde.org/~wheeler/taglib.html, and extract to /usr/src. Then install it with the following commands:<br />
cd /usr/src<br />
sudo chown linuxmce taglib-1.5<br />
cd taglib-1.5<br />
./configure<br />
make<br />
sudo make install<br />
sudo ln -s /usr/local/include/taglib /usr/include/taglib<br />
<br />
Install id3lib. Download version 3.8.3 from http://id3lib.sourceforge.net/, and extract to /usr/src. Then install it with the following commands:<br />
cd /usr/src<br />
sudo chown linuxmce id3lib-3.8.3<br />
cd id3lib-3.8.3<br />
./configure<br />
make<br />
sudo make install<br />
<br />
Build UpdateMedia:<br />
cd /usr/src/lmce/LinuxMCE-0710/src/UpdateMedia<br />
make<br />
<br />
If all goes well, your new binary for UpdateMedia should be in the current folder.<br />
<br />
= Building on 0604 =<br />
'''Source code for LinuxMCE 0704 is on the [[Mirrors]]. This page hasn't been updated for 0704 yet'''<br />
== Before You Begin==<br />
The build script is tested and designed to run on Ubuntu 6.10 x86 but it can be changed to work on various platforms or at least to give others a starting point on how to do it. It'll be harder to port it to non deb based distributions since the software depends on many debian specific stuff but this i hope to be change over time.<br />
<br />
Also since this script was written with a single goal in mind -- to get everything done -- I might have left, by mistake, some lines of code that may not run on your computers (hardcoded paths and stuff like this). But I rely on you to at least try to fix them before asking for help but if the problem is not so obvious I would gladly give you advice.<br />
<br />
== The Build Scripts ==<br />
The build scripts are in sourceforge svn so to get them you will need subversion installed.<br />
sudo apt-get install subversion<br />
svn co https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/trunk/src/Ubuntu_Helpers<br />
<br />
Before running the build script, i insist that you take a look over it so that you know what is doing and not run it blindly. <br />
<br />
The main script that you need to run would be BuildUbuntu.sh. This script should checkout the svn for you, compile the source, build the packages, build an iso and everything else so you can end up with a usable linuxmce build. In this script you can find some functions that are called one by one to perform several operations, here's a short description:<br />
<br />
*''Install_Build_Needed_Packages'': This will install all the deb packages that you</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Building_From_Source&diff=19362Building From Source2009-06-10T05:57:12Z<p>Colinjones: /* Building for 0810 */</p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
[[Category: Tutorials]]<br />
[[Category:Development]]<br />
[[Category:Programmer's Guide]]<br />
= Building for 0810 =<br />
Please see [[Building LinuxMCE 0810|Building_LinuxMCE_0810]]<br />
<br />
= Building for 0804 =<br />
Please see [[Building_LinuxMCE]]<br />
<br />
= Building on 0710 =<br />
See also: [[Setting Up A Development Environment]]<br />
== Preparations ==<br />
Set up a directory for the development tree. For example type the following in a shell as "linuxmce" user:<br />
cd /usr/src<br />
sudo mkdir lmce<br />
sudo chown linuxmce lmce<br />
cd lmce<br />
<br />
Install Subversion<br />
sudo apt-get install subversion<br />
<br />
Fetch the source:<br />
svn co http://svn.linuxmce.org/svn/branches/LinuxMCE-0710/<br />
<br />
Copy the libraries needed for to bootstrap:<br />
cp /usr/pluto/lib/* trunk/src/lib<br />
<br />
Run configure:<br />
cd trunk<br />
./configure<br />
<br />
For the svn.linuxmce.org source there is no configure script yet. Run these to prepare bootstrapping:<br />
find . -iname Makefile -exec sed -e 's/<-mkr_t_compile_defines->/-DKDE_LMCE -DDEBUG -DTHREAD_LOG -DLOG_ALL_QUERIES -I\/opt\/libxine1-pluto\/include -I\/opt\/libsdl1.2-1.2.7+1.2.8cvs20041007\/include -I\/opt\/libsdl1.2-1.2.7+1.2.8cvs20041007\/include\/SD/' -i '{}' \;<br />
find . -iname Makefile -exec sed -e 's/<-mkr_t_compile_libs->/-L\/opt\/libxine1-pluto\/lib -L\/opt\/libsdl1.2-1.2.7+1.2.8cvs20041007\/lib/' -i '{}' \;<br />
<br />
== Building ==<br />
Run make:<br />
make<br />
<br />
== Building UpdateMedia ==<br />
Since 7.10 does not use configure, it can be tough getting the entire tree to build. If all you need to build is UpdateMedia (for example), save yourself some trouble and just build that component. For the specific case of UpdateMedia, here are the steps to build based on a 7.10 DVD install and after following the above instructions:<br />
<br />
Install mysqlclient-dev:<br />
sudo apt-get install libmysqlclient15-dev<br />
<br />
Install attr-dev:<br />
sudo apt-get install attr-dev<br />
<br />
Install taglib. Download version 1.5 from http://developer.kde.org/~wheeler/taglib.html, and extract to /usr/src. Then install it with the following commands:<br />
cd /usr/src<br />
sudo chown linuxmce taglib-1.5<br />
cd taglib-1.5<br />
./configure<br />
make<br />
sudo make install<br />
sudo ln -s /usr/local/include/taglib /usr/include/taglib<br />
<br />
Install id3lib. Download version 3.8.3 from http://id3lib.sourceforge.net/, and extract to /usr/src. Then install it with the following commands:<br />
cd /usr/src<br />
sudo chown linuxmce id3lib-3.8.3<br />
cd id3lib-3.8.3<br />
./configure<br />
make<br />
sudo make install<br />
<br />
Build UpdateMedia:<br />
cd /usr/src/lmce/LinuxMCE-0710/src/UpdateMedia<br />
make<br />
<br />
If all goes well, your new binary for UpdateMedia should be in the current folder.<br />
<br />
= Building on 0604 =<br />
'''Source code for LinuxMCE 0704 is on the [[Mirrors]]. This page hasn't been updated for 0704 yet'''<br />
== Before You Begin==<br />
The build script is tested and designed to run on Ubuntu 6.10 x86 but it can be changed to work on various platforms or at least to give others a starting point on how to do it. It'll be harder to port it to non deb based distributions since the software depends on many debian specific stuff but this i hope to be change over time.<br />
<br />
Also since this script was written with a single goal in mind -- to get everything done -- I might have left, by mistake, some lines of code that may not run on your computers (hardcoded paths and stuff like this). But I rely on you to at least try to fix them before asking for help but if the problem is not so obvious I would gladly give you advice.<br />
<br />
== The Build Scripts ==<br />
The build scripts are in sourceforge svn so to get them you will need subversion installed.<br />
sudo apt-get install subversion<br />
svn co https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/trunk/src/Ubuntu_Helpers<br />
<br />
Before running the build script, i insist that you take a look over it so that you know what is doing and not run it blindly. <br />
<br />
The main script that you need to run would be BuildUbuntu.sh. This script should checkout the svn for you, compile the source, build the packages, build an iso and everything else so you can end up with a usable linuxmce build. In this script you can find some functions that are called one by one to perform several operations, here's a short description:<br />
<br />
*''Install_Build_Needed_Packages'': This will install all the deb packages that you</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Building_From_Source&diff=19361Building From Source2009-06-10T05:56:47Z<p>Colinjones: Added the correct link for building 0810</p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
[[Category: Tutorials]]<br />
[[Category:Development]]<br />
[[Category:Programmer's Guide]]<br />
= Building for 0810 =<br />
Please see [[Building_LinuxMCE_0810]]<br />
<br />
= Building for 0804 =<br />
Please see [[Building_LinuxMCE]]<br />
<br />
= Building on 0710 =<br />
See also: [[Setting Up A Development Environment]]<br />
== Preparations ==<br />
Set up a directory for the development tree. For example type the following in a shell as "linuxmce" user:<br />
cd /usr/src<br />
sudo mkdir lmce<br />
sudo chown linuxmce lmce<br />
cd lmce<br />
<br />
Install Subversion<br />
sudo apt-get install subversion<br />
<br />
Fetch the source:<br />
svn co http://svn.linuxmce.org/svn/branches/LinuxMCE-0710/<br />
<br />
Copy the libraries needed for to bootstrap:<br />
cp /usr/pluto/lib/* trunk/src/lib<br />
<br />
Run configure:<br />
cd trunk<br />
./configure<br />
<br />
For the svn.linuxmce.org source there is no configure script yet. Run these to prepare bootstrapping:<br />
find . -iname Makefile -exec sed -e 's/<-mkr_t_compile_defines->/-DKDE_LMCE -DDEBUG -DTHREAD_LOG -DLOG_ALL_QUERIES -I\/opt\/libxine1-pluto\/include -I\/opt\/libsdl1.2-1.2.7+1.2.8cvs20041007\/include -I\/opt\/libsdl1.2-1.2.7+1.2.8cvs20041007\/include\/SD/' -i '{}' \;<br />
find . -iname Makefile -exec sed -e 's/<-mkr_t_compile_libs->/-L\/opt\/libxine1-pluto\/lib -L\/opt\/libsdl1.2-1.2.7+1.2.8cvs20041007\/lib/' -i '{}' \;<br />
<br />
== Building ==<br />
Run make:<br />
make<br />
<br />
== Building UpdateMedia ==<br />
Since 7.10 does not use configure, it can be tough getting the entire tree to build. If all you need to build is UpdateMedia (for example), save yourself some trouble and just build that component. For the specific case of UpdateMedia, here are the steps to build based on a 7.10 DVD install and after following the above instructions:<br />
<br />
Install mysqlclient-dev:<br />
sudo apt-get install libmysqlclient15-dev<br />
<br />
Install attr-dev:<br />
sudo apt-get install attr-dev<br />
<br />
Install taglib. Download version 1.5 from http://developer.kde.org/~wheeler/taglib.html, and extract to /usr/src. Then install it with the following commands:<br />
cd /usr/src<br />
sudo chown linuxmce taglib-1.5<br />
cd taglib-1.5<br />
./configure<br />
make<br />
sudo make install<br />
sudo ln -s /usr/local/include/taglib /usr/include/taglib<br />
<br />
Install id3lib. Download version 3.8.3 from http://id3lib.sourceforge.net/, and extract to /usr/src. Then install it with the following commands:<br />
cd /usr/src<br />
sudo chown linuxmce id3lib-3.8.3<br />
cd id3lib-3.8.3<br />
./configure<br />
make<br />
sudo make install<br />
<br />
Build UpdateMedia:<br />
cd /usr/src/lmce/LinuxMCE-0710/src/UpdateMedia<br />
make<br />
<br />
If all goes well, your new binary for UpdateMedia should be in the current folder.<br />
<br />
= Building on 0604 =<br />
'''Source code for LinuxMCE 0704 is on the [[Mirrors]]. This page hasn't been updated for 0704 yet'''<br />
== Before You Begin==<br />
The build script is tested and designed to run on Ubuntu 6.10 x86 but it can be changed to work on various platforms or at least to give others a starting point on how to do it. It'll be harder to port it to non deb based distributions since the software depends on many debian specific stuff but this i hope to be change over time.<br />
<br />
Also since this script was written with a single goal in mind -- to get everything done -- I might have left, by mistake, some lines of code that may not run on your computers (hardcoded paths and stuff like this). But I rely on you to at least try to fix them before asking for help but if the problem is not so obvious I would gladly give you advice.<br />
<br />
== The Build Scripts ==<br />
The build scripts are in sourceforge svn so to get them you will need subversion installed.<br />
sudo apt-get install subversion<br />
svn co https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/trunk/src/Ubuntu_Helpers<br />
<br />
Before running the build script, i insist that you take a look over it so that you know what is doing and not run it blindly. <br />
<br />
The main script that you need to run would be BuildUbuntu.sh. This script should checkout the svn for you, compile the source, build the packages, build an iso and everything else so you can end up with a usable linuxmce build. In this script you can find some functions that are called one by one to perform several operations, here's a short description:<br />
<br />
*''Install_Build_Needed_Packages'': This will install all the deb packages that you</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Building_From_Source&diff=19360Building From Source2009-06-10T05:55:25Z<p>Colinjones: /* Building for 0810 */ changed from 0810 to 0804</p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
[[Category: Tutorials]]<br />
[[Category:Development]]<br />
[[Category:Programmer's Guide]]<br />
= Building for 0804 =<br />
Please see [[Building_LinuxMCE]]<br />
<br />
= Building on 0710 =<br />
See also: [[Setting Up A Development Environment]]<br />
== Preparations ==<br />
Set up a directory for the development tree. For example type the following in a shell as "linuxmce" user:<br />
cd /usr/src<br />
sudo mkdir lmce<br />
sudo chown linuxmce lmce<br />
cd lmce<br />
<br />
Install Subversion<br />
sudo apt-get install subversion<br />
<br />
Fetch the source:<br />
svn co http://svn.linuxmce.org/svn/branches/LinuxMCE-0710/<br />
<br />
Copy the libraries needed for to bootstrap:<br />
cp /usr/pluto/lib/* trunk/src/lib<br />
<br />
Run configure:<br />
cd trunk<br />
./configure<br />
<br />
For the svn.linuxmce.org source there is no configure script yet. Run these to prepare bootstrapping:<br />
find . -iname Makefile -exec sed -e 's/<-mkr_t_compile_defines->/-DKDE_LMCE -DDEBUG -DTHREAD_LOG -DLOG_ALL_QUERIES -I\/opt\/libxine1-pluto\/include -I\/opt\/libsdl1.2-1.2.7+1.2.8cvs20041007\/include -I\/opt\/libsdl1.2-1.2.7+1.2.8cvs20041007\/include\/SD/' -i '{}' \;<br />
find . -iname Makefile -exec sed -e 's/<-mkr_t_compile_libs->/-L\/opt\/libxine1-pluto\/lib -L\/opt\/libsdl1.2-1.2.7+1.2.8cvs20041007\/lib/' -i '{}' \;<br />
<br />
== Building ==<br />
Run make:<br />
make<br />
<br />
== Building UpdateMedia ==<br />
Since 7.10 does not use configure, it can be tough getting the entire tree to build. If all you need to build is UpdateMedia (for example), save yourself some trouble and just build that component. For the specific case of UpdateMedia, here are the steps to build based on a 7.10 DVD install and after following the above instructions:<br />
<br />
Install mysqlclient-dev:<br />
sudo apt-get install libmysqlclient15-dev<br />
<br />
Install attr-dev:<br />
sudo apt-get install attr-dev<br />
<br />
Install taglib. Download version 1.5 from http://developer.kde.org/~wheeler/taglib.html, and extract to /usr/src. Then install it with the following commands:<br />
cd /usr/src<br />
sudo chown linuxmce taglib-1.5<br />
cd taglib-1.5<br />
./configure<br />
make<br />
sudo make install<br />
sudo ln -s /usr/local/include/taglib /usr/include/taglib<br />
<br />
Install id3lib. Download version 3.8.3 from http://id3lib.sourceforge.net/, and extract to /usr/src. Then install it with the following commands:<br />
cd /usr/src<br />
sudo chown linuxmce id3lib-3.8.3<br />
cd id3lib-3.8.3<br />
./configure<br />
make<br />
sudo make install<br />
<br />
Build UpdateMedia:<br />
cd /usr/src/lmce/LinuxMCE-0710/src/UpdateMedia<br />
make<br />
<br />
If all goes well, your new binary for UpdateMedia should be in the current folder.<br />
<br />
= Building on 0604 =<br />
'''Source code for LinuxMCE 0704 is on the [[Mirrors]]. This page hasn't been updated for 0704 yet'''<br />
== Before You Begin==<br />
The build script is tested and designed to run on Ubuntu 6.10 x86 but it can be changed to work on various platforms or at least to give others a starting point on how to do it. It'll be harder to port it to non deb based distributions since the software depends on many debian specific stuff but this i hope to be change over time.<br />
<br />
Also since this script was written with a single goal in mind -- to get everything done -- I might have left, by mistake, some lines of code that may not run on your computers (hardcoded paths and stuff like this). But I rely on you to at least try to fix them before asking for help but if the problem is not so obvious I would gladly give you advice.<br />
<br />
== The Build Scripts ==<br />
The build scripts are in sourceforge svn so to get them you will need subversion installed.<br />
sudo apt-get install subversion<br />
svn co https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/trunk/src/Ubuntu_Helpers<br />
<br />
Before running the build script, i insist that you take a look over it so that you know what is doing and not run it blindly. <br />
<br />
The main script that you need to run would be BuildUbuntu.sh. This script should checkout the svn for you, compile the source, build the packages, build an iso and everything else so you can end up with a usable linuxmce build. In this script you can find some functions that are called one by one to perform several operations, here's a short description:<br />
<br />
*''Install_Build_Needed_Packages'': This will install all the deb packages that you will need to build the sourcecode. Probably you will only need to run it once and comment it after the first run on BuildPackages.sh.<br />
*''Create Diskless Archive'': Runs a debootstrap to create a base filesystem for Diskless Media Directors. It's needed later when it'll be packed in a deb packages. You also don't need to run this every time but is safer to leave it uncommented so that the diskless archive will have the latest ubuntu updates.<br />
*''Import_Skins'': Since linuxmce uses a lot of pngs for the all sort of skins, you won't find them in the svn. This function will download a tar.bz2 archive with all the skins and unpack it so that the package builder will now where to take it from.<br />
*''Checkout_Svn'': Will do a svn checkout on sourceforge to get all the needed sources<br />
*''Build_Replacements'': LinuxMCE needs some 3rd party some packages that are not part of ubuntu distribution. This function will build / get them for you.<br />
*''Build_MakeRelease_Binary'': This function compiles the building tools that will do the compilation / package creation of all the other packages by using information stored in the pluto_main_build database.<br />
*''Import_Build_Database'': Imports a fresh copy of the pluto databases needed at build time.<br />
*''Create_Fake_Windows_Binaries'': Orbiter and other aplications don't only run on Linux. Usually the pluto guys compile their applications on windows and put the binaries on the linux build machine so that package creating application will know where to get them. Since we can't compile windows binaries on linux i made this function that creates some fake binary files with a touch so that the package builder won't fail to run.<br />
*''Build_Pluto_Stuff'': Uses MakeRelase to compile the sources and build packages out of them<br />
*''Create_Local_Repository'': Optional you can create a local repository so that you can easily test your debs.<br />
<br />
There is also the get-packages.sh script that is called by BuildUbuntu.sh and has the goal to create and iso with all the needed packages for a linuxmce installation.<br />
<br />
== Source Code Location ==<br />
<br />
Our source code is located on sourceforge and you can get it by svn from : http://svn.linuxmce.org/svn/<br />
<br />
The png used for the skins are located here : http://www.linuxmce.org/build/linuxmce-skins-1.0.tar.bz2<br />
<br />
The sql dumps of the databases needed for the build : http://www.linuxmce.org/build/linuxmce-databases-1.0.tar.gz</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=MSI_Wind_PC&diff=19255MSI Wind PC2009-06-01T01:31:05Z<p>Colinjones: caveat on HD</p>
<hr />
<div>[[Category: Hardware]] <br />
[[Category: Media Directors]]<br />
[[Category: Barebones]]<br />
[[Category: Nettops]]<br />
<br />
The MSI Wind PC is a very small, ultra low power consumption Intel Atom based PC that can be used as an MD. This is a low end, very low cost barebones PC that already includes a CPU. So for MD useage, you just need to add a stick of RAM and you're done!<br />
<br />
The cheapest I have seen it is at NewEgg (they do not ship internationally) for US$139.99, [http://www.newegg.com/Product/Product.aspx?Item=N82E16856167032&Tpk=msi%20wind%20pc here].<br />
<br />
[[Image:MSI_Wind_PC.jpg|thumb|right|300px|MSI Wind PC]]<br />
<br />
<br />
== Advantages ==<br />
<br />
* Small foot print - 300x260x65mm<br />
* Support UI2 with overlay and 1080p (HD) video playback - VGA out only (note it supports 1080p resolutions, but will struggle with UI2 or HD media at this resolution, 720p is best, and avoid high bitrate/advanced codecs like H264)<br />
* 7.1 Surround sound - analogue minijacks<br />
* Almost noiseless<br />
* Low energy consumption - less than 40w at full speed, this is probably including a HDD which isn't needed for LMCE<br />
* Low price<br />
<br />
== Disadvantages ==<br />
<br />
* Video is analogue - no DVI or HDMI<br />
* Audio is analogue - no SPDIF out<br />
<br />
== Known Issues ==<br />
<br />
* Photo Screen Saver sometimes causes issues with the Intel graphics chipset - this causes the unit to lock up. Resolution: disable PSS. It is possible in the next version (0810) of LMCE the driver updates will fix this.<br />
* There is an issue with the NIC drivers that means the unit can't PXE boot properly. Resolution: follow [http://wiki.linuxmce.org/index.php/R8168 this] article to correct the drivers. Probable that the next version of LMCE (0810) will correct this.</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Contacts&diff=19235Contacts2009-05-30T22:52:25Z<p>Colinjones: </p>
<hr />
<div>LinuxMCE is a media centered [[Linux]] distribution. It's built on the solid foundation laid down by debian and Ubuntu. But with all kinds of goodies for the home of the future, from digital video recorder capabilities and home automation to functioning as a telephone switching hub for your home in lieu of a boring intercom system; all tied together by an advanced messaging infrastructure. While the next release 0810 is almost done and focuses on stability, we're already planning for the next release and '''you''' could contribute to it's direction. We're always looking for developers and maintainers to '''[[Contribute|join the team]]'''. New LinuxMCE team members, please add your name, contact info, and a brief bio or description of what you're working on. Thanks!<br />
<br />
----<br />
'''Daniel Kristjansson''' -- contact: danielk -at- cuymedia (.net)<br><br />
Responsibilities: Community liaison, organizing open source volunteers and roadmap<br><br />
----<br />
'''Thomas Cherryhomes''' -- contact: thom.cherryhomes -at- gmail (.com)<br><br />
Responsibilities: Hacking, Coding, Media Plugins/Players, Orbiter Development, HA Designer specialist.<br><br />
----<br />
'''[[User:hari|Harald Klein]]''' -- contact: hari -at- vt100 (.at)<br><br />
Responsibilities: [[sqlCVS]] maintenance, [[JavaMO]], open [[ZWave]] driver, testing<br><br />
----<br />
'''[[User:Nite_man|Michael Stepanov]]''' aka nite_man -- Contact: stepanov.michael -at- gmail (.com)<br><br />
Offering: Build and test SDL Orbiter for Linux-based PC and Nokia770/N800/N810, Russian translation, testing and feedback.<br />
----<br />
'''Pete Kalogiannis''' -- Contact: pkalogiannis -at- gmail (dot) com<br><br />
Offering: [[Insteon]] Integration<br />
----<br />
'''[[User:Jondecker76|Jon Decker]]''' (aka jondecker76) -- Contact: jondecker76 -at- windstream (.net)<br><br />
Offering: CM11A Driver support and integration, Lighting_Plugin maintenance and upgrades, Climate_Plugin and maintenance and upgrades, Web Admin maintenance and upgrades<br />
----<br />
'''[[User:Ddamron|Dan Damron]]''' -- Contact: dan.damron -at- techengine (dot) ca<br><br />
Offering: [[Insteon]] Integration via PLM (In OPEN beta test now!) / EZBridge/EZServ, [[PLCBUS]] Integration<br />
----<br />
'''Robert Wilson''' aka rwilson131 -- Contact: rwilson131 at gmail dot com<br><br />
Offering: Wiki Documentation and Creation of [[User Manual]]<br />
----<br />
'''Derrick Lewis''' aka dlewis -- Contact info: dlewis (at) linuxmce (dot) org <br /><br />
Responsibilities: [http://forum.linuxmce.org Forum] Moderator and Evangelist<br />
----<br />
'''Colin Jones''' aka colinjones -- Contact info: colin_a_jones (at) hotmail (dot) com <br /><br />
Responsibilities: [http://forum.linuxmce.org Forum] Moderator and Evangelist<br />
----<br />
'''Seven Walter''' aka CylonSeven -- Contact: Seven -at- Apollo Smart Homes (dot) com <br><br />
Offering: QA & Testing, Docs, Wiki, Promotions (Central Texas USA). Plenty of hardware for testing: Hybrid w/ RAID, fast MD/HTPC w/ HiDef & Digital Audio out, Firewire & IP cameras, ZWave, etc.<br><br />
----<br />
'''Brandon Kruger''' aka bmk789 -- Contact via [[User:bmk789|User page]]<br/><br />
Offering: wiki moderation & documentation<br />
----<br />
'''[[User:JimmyGosling|Roguen]]''' aka JimmyGosling(Forums), JimmyGos (IIRC) or TheGos (IIRC) -- Contact: Roguen (at) garage68 (dot) com <br /><br />
Offering: code development, wiki documentation<br />
----<br />
'''Andy Brauer'''-- Contact andy (dot) brauer (at) bcx (dot) co (dot) za <br /><br />
Offering: code development, testing marketing and business development<br />
----<br />
'''Evan King'''-- Contact info: evan (at) evanking (dot) net <br /><br />
Offering: Asterisk support and new features, Automation development, iPhone web integration in the future.<br />
----<br />
'''Ken Tarwood'''-- Contact info: fastplymouth (at) gmail (dot) com, B5Duster(IRC) <br /><br />
Offering: Code and web admin app development (c++/c#, python, php), orbiter theming, testing, documentation and marketing activities.<br />
----<br />
'''Uwe Stark''' aka orgel -- Contact info: orgel0 (at) freenet (dot) de <br /><br />
Responsibilities: German translation, translation into the [http://www.linux-mce.de German Wiki], moderator of the [http://forum.linux-mce.de German forum]<br />
----<br />
== Alumni ==<br />
<br />
'''Paul Webber''' -- contact: webpaul1 -at- gmail (.com)<br><br />
Paul launched LinuxMCE on March 15, 2007, but is moving on to other projects. He visits us occasionally but after release 0710 will no longer be solely responsible for any aspect of the LinuxMCE release cycle. See [[History|'''History of LinuxMCE''']], for an explanation of why Paul started the project.<br />
<br />
[[Category:Development]]<br />
[[Category:Wiki administration]]</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Realtek_8168&diff=19106Realtek 81682009-05-19T00:15:22Z<p>Colinjones: /* Compiling Realtek's r8168 module */</p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
[[Category: Hardware]]<br />
[[Category: Networking]]<br />
[[Category: Network Adapters]]<br />
[[Category: Tutorials]]<br />
<br />
=The Realtek RTL8168 network card on LinuxMCE=<br />
<br />
This card is supposed to work with the r8169 module, but this seems to fail for newer cards. Realtek provides the source code for a r8168 module on [http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false#2 their site].<br />
<br />
===What you need to do===<br />
* Download the driver from Realtek (at the time of this article, the version is 8.008.00, released 2008/7/24) to compile the r8168 module<br />
* Install the linux-source package, to hack into the r8169 module.<br />
<br />
The default r8169 module and Realtek's r8168 overlap on a PCI ID, and that's why you need the kernel source. You'll compile the r8169 without the PCI ID that r8168 will associate with.<br />
<br />
>>TODO: Insert section of required packages for the build to work<br />
<br />
===Compiling Realtek's r8168 module===<br />
<br />
* [http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false#2 Download] the Realtek driver: you'll get a file called r8168-8.008.00.tar.bz2<br />
* unpack the file:<br />
tar -jxf r8168-8.008.00.tar.bz2<br />
* switch into the directory that is created:<br />
cd r8168-8.008.00<br />
* build the module:<br />
make<br />
* copy the module to the running kernel:<br />
cp src/r8168.ko /lib/modules/2.6.22-14-generic/kernel/drivers/net/<br />
<br />
(I believe the last cp step is no longer required as it version 8.012.00 of the driver sources, as it does this as part of the make - colinjones)<br />
<br />
===Hacking the r8169 module===<br />
<br />
* Install the kernel source:<br />
apt-get install linux-source<br />
* Un pack the kernel source:<br />
cd /usr/src; tar -jxf linux-source-2.6.22.tar.bz2<br />
* Switch to the kernel directory:<br />
cd linux-source-2.6.22<br />
* Copy the running kernel's configuration:<br />
cp /boot/config-2.6.22-14-generic .config<br />
* Prepare the kernel so you can build modules:<br />
make scripts prepare<br />
* Apply this patch:<br />
patch < r8168.diff<br />
<pre><br />
--- drivers/net/r8169.c.orig 2008-09-05 17:07:29.000000000 +0300<br />
+++ drivers/net/r8169.c 2008-09-04 23:49:51.000000000 +0300<br />
@@ -162,7 +162,7 @@<br />
{ PCI_DEVICE(PCI_VENDOR_ID_REALTEK, 0x8129), 0, 0, RTL_CFG_0 },<br />
{ PCI_DEVICE(PCI_VENDOR_ID_REALTEK, 0x8136), 0, 0, RTL_CFG_2 },<br />
{ PCI_DEVICE(PCI_VENDOR_ID_REALTEK, 0x8167), 0, 0, RTL_CFG_0 },<br />
- { PCI_DEVICE(PCI_VENDOR_ID_REALTEK, 0x8168), 0, 0, RTL_CFG_1 },<br />
+ //{ PCI_DEVICE(PCI_VENDOR_ID_REALTEK, 0x8168), 0, 0, RTL_CFG_1 },<br />
{ PCI_DEVICE(PCI_VENDOR_ID_REALTEK, 0x8169), 0, 0, RTL_CFG_0 },<br />
{ PCI_DEVICE(PCI_VENDOR_ID_DLINK, 0x4300), 0, 0, RTL_CFG_0 },<br />
{ PCI_DEVICE(0x1259, 0xc107), 0, 0, RTL_CFG_0 },<br />
</pre><br />
* Build the network modules:<br />
make M=`pwd`/drivers/net modules<br />
* Confirm that the new r8169 module doesn't have the "pci:v000010ECd00008168sv" alias:<br />
modinfo drivers/net/r8169.ko<br />
* Copy the new r8169.ko to the running kernel:<br />
cp drivers/net/r8169.ko /lib/modules/2.6.22-14-generic/kernel/drivers/net/<br />
* Run depmod<br />
depmod<br />
* Load the module:<br />
modprobe r8168<br />
<br />
=== MDs ===<br />
After you created the modules as described above:<br />
<br />
* Copy the modules to all the affected MD filesystems, in the corresponding location<br />
* Follow the instructions on the [[Unrecognized NIC]] page<br />
<br />
== Asus M3A78-EM ==<br />
Here are the steps required to get this motherboard's Realtek 8168 Gigabit Ethernet Working for an MD.<br />
<br />
To save some steps, I will make my driver available here : [http://dataless.jeromenet.org/r8168.ko r8168 driver]<br />
This can be used on the Realtek 8111B/8111C chipsets as well, that is what my motherboard says, just before PXE boot.<br />
<br />
--[[User:Sethj|Sethj]] 12:50, 12 December 2008 (CET)<br />
<br />
[[Generic_PC#Manual_Setup_of_a_Media_Director | First I manually created the Media Director]] from the [[LinuxMCE Admin Website]]. Did not want it to build an AMD64 image, wanted to stay with i386, and I knew the MAC address of the new MD onboard NIC. Ran "Setup Diskless MD" when that completed I clicked the "Rebuild Image" for the new MD. While that was running I completed the next few things. Wait for this to complete, and then continue.<br />
<br />
* Download the driver package for Linux from Asus' web site here : [http://support.asus.com/download/download.aspx?SLanguage=en-us&model=M3A78-EM LinuxDrivers.zip] - It is under "Others"<br />
* unzip the package to /usr/src<br />
sudo su<br />
cd /usr/src<br />
unzip -qq /path/to/LinuxDrivers.zip<br />
cd /usr/src/LinuxDrivers/LAN/r8168-8.003.00/r8168-8.003.00<br />
make<br />
cp src/r8168.ko /lib/modules/2.6.22-14-generic/kernel/drivers/net/<br />
mv /lib/modules/2.6.22-14-generic/kernel/drivers/net/r8169.ko /lib/modules/2.6.22-14-generic/kernel/drivers/net/r8169.ko.not<br />
depmod -a<br />
/usr/pluto/bin/Diskless_BuildDefaultImage.sh<br />
cp /lib/modules/2.6.22-14-generic/kernel/drivers/net/r8168.ko /usr/pluto/diskless/<moon #>/lib/modules/2.6.22-14-generic/kernel/drivers/net<br />
vi /usr/pluto/diskless/<moon #>/etc/initramfs-tools/modules<br />
added r8168 and saved<br />
cd /usr/pluto/diskless<br />
chroot <moon #><br />
mv /lib/modules/2.6.22-14-generic/kernel/drivers/net/r8169.ko /lib/modules/2.6.22-14-generic/kernel/drivers/net/r8169.ko.not<br />
depmod -a /lib/modules/2.6.22-14-generic/kernel/drivers/net/r8168.ko<br />
cd /boot<br />
update-initramfs -uv<br />
(scrolled up to verify the new module was added it was at the top of the output)<br />
for S and G's ran depmod -a again<br />
exit out of the chroot<br />
<br />
Now boot or reboot the MD.<br />
<br />
For a Core:<br />
<br />
* Get some means to download and store [url]http://dataless.jeromenet.org/r8168.ko[/url], as you may not have internet (no 2nd nic)<br />
I used a pen drive.<br />
* Once you have this file, boot the system in Safe Mode, using option 2 in grub (press ESC when system starts to get to grub)<br />
after the system comes up, you will have your dcerouter# prompt. Insert pen drive, mount it some where: I did:<br />
<br />
mkdir /mnt/temp<br />
mount /dev/sdx1 /mnt/temp (insert your letter for "x" in this, you can find it with dmesg<br />
cp /mnt/temp/r8168.ko /lib/modules/2.6.22-14-generic/kernel/drivers/net/<br />
mv /lib/modules/2.6.22-14-generic/kernel/drivers/net/r8169.ko /lib/modules/2.6.22-14-generic/kernel/drivers/net/r8169.ko.not<br />
depmod -a /lib/modules/2.6.22-14-generic/kernel/drivers/net/r8168.ko<br />
vi /etc/initramfs-tools/modules<br />
add r8168<br />
cd /boot <br />
update-initramfs -uv<br />
(scroll up to verify the new module was added)<br />
<br />
* Now reboot, and that should sort it out.</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=20090415Minutes&diff=1865120090415Minutes2009-04-24T23:17:54Z<p>Colinjones: /* Attendance */ was not in attendance</p>
<hr />
<div>Meeting chair: jimbodude<br />
<br />
Minutes prepared by: jimbodude<br />
<br />
==Attendance==<br />
*dlewis<br />
*hari<br />
*jimbodude<br />
*tkmedia<br />
*totallymaxed<br />
*TSCHAK<br />
*Zaerc<br />
<br />
==Topics and Discussion==<br />
*Several bug reports were covered<br />
**Nothing conclusive came out of the discussion<br />
**About 3 bug tickets in, focus was shifted to the next agenda items to keep interest<br />
<br />
*Standardized testing procedures (presented by '''hari''')<br />
**Goal: locate all bugs in a systematic way<br />
**Method:<br />
**#Develop standardized tests for each component (DCERouter, Web Admin, Orbiter, etc...)<br />
**#Assign 2+ people to each component<br />
**#Run tests over 2-3 days<br />
**#Combine results, create new tickets<br />
**If other test procedures are already available, use those to augment<br />
**'''No one has taken direct responsibility for these tasks.'''<br />
<br />
*Release Scheduling<br />
**Goal: focus development efforts in key areas on a flexible, but documented, schedule such that important issues are not overlooked for long periods of time.<br />
**Method:<br />
**#Find things that don't work<br />
**#Assign them to a milestone<br />
**#Pick a date for each milestone's completion<br />
**Things that are broken or need attention: (in no particular order)<br />
***MD booting<br />
***KDE Desktop on MD<br />
***Getting back to Orbiter from KDE<br />
***the desktop is incorrectly sized on TV's at HD resolutions<br />
***login problem on MD<br />
***Auto detect of USBUIRT<br />
***ir codes in sqlcvs<br />
***serial detection<br />
***cisco 7070 wrong room problem<br />
***making more devices PnP<br />
***work on upgrading telecom<br />
***issue with the sony changer<br />
**'''No one has taken responsibility for these tasks'''<br />
<br />
*Update scheduling discussion is deferred until there is a release schedule<br />
*Installation number generation design discussion is deferred in the interest of time and higher priority issues<br />
<br />
*Defect Tracking<br />
**Goal: Improve defect tracking in order to:<br />
***Communicate issues to a team that is distributed<br />
***Bring attention to issues that may otherwise be ignored<br />
***Focus developer efforts on key tasks<br />
***Assist in release scheduling<br />
**Method: Encourage testers to submit bug reports. Draft a defect reporting policy specific to LinuxMCE<br />
**A LinuxMCE policy will be presented at the next meeting for discussion<br />
**'''jimbodude had taken responsibility for these tasks'''<br />
<br />
*Future Meetings<br />
**This meeting was helpful - future meetings are expected to be just as useful, and should be scheduled<br />
**Since the topics at this meeting require significant follow-up work the next meeting will be in one week<br />
**Meetings thereafter may be weekly or bi-weekly - this decision is deferred to the next meeting<br />
**'''jimbodude has taken responsibility for creating an agenda for the next meeting'''<br />
**'''No one has taken responsibility for scheduling the next meeting'''</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Mirrors_710&diff=18317Mirrors 7102009-04-05T23:02:51Z<p>Colinjones: /* Download locations */</p>
<hr />
<div>= LinuxMCE 0710 =<br />
'''Before installing, check out the [[Known Issues|Known issues]], and please read the [[Installation Guide]] and/or the [[DVD Installation]] guide.''' Installing from DVD is the fastest. Installing from CD .iso images on your hard disk is second fastest (you will need to install Kubuntu 7.10 first), and installing from burned CDs is slowest.<br />
<br />
'''NOTE:''' Please download from the torrent links rather than the mirrors if possible. You are far less likely to get a corruption that will kill your install.<br />
<br />
'''NOTE:''' It is a good idea to use md5sum and the checksums to verify your download is not corrupted.<br />
<br />
'''NOTE:''' It is ''essential'' that you burn your CDs and DVDs using the slowest possible speed your burner supports - faster speeds regularly cause corruptions on the burn which will be fatal to your install.<br />
<br />
<br />
== What you have to download ==<br />
To install LinuxMCE you need to download the DVD (which includes everything needed for the installation) or you can download both LinuxMCE CD's plus a Kubuntu 7.10 CD. You can also choose to download the Dual Layer DVD which includes extra demo media.<br />
<br />
'''''Warning: The DVD installation will wipe the entire disk of the machine -- all previous data will be permanently lost!''''' <br />
(Note: There is a new "keep settings" option which will preserve data in the home directory for most, '''''but not all''''', installations. Also, there are instructions on how to use the [[DVD Install And Custom Partitions|DVD Install with custom partitions]])<br />
<br />
LinuxMCE 0710 was released on May 7th, 2008. This is also known as LinuxMCE 0710 RC2.<br />
<br />
====NOTES:====<br />
<br />
- To upgrade from a 0710 beta to 0710, you can use "LinuxMCE Install CDs for i386" or "LinuxMCE Install DVD for i386" with "keep settings" option. <br />
<br />
- To upgrade from 0704, you can use :<br />
a) "LinuxMCE Install CDs for i386 - 0710 RC2" or "LinuxMCE Install DVD for i386 - 0710 RC2" with "keep settings" option or<br />
b) the upgrade helper application from [http://www.linuxmce.com/upgrade/gutsy-upgrade-scripts_0.1.0-2_i386.deb gutsy-upgrade-scripts_0.1.0-2_i386.deb] and choose to install from web or from DVD (you must have the double layer DVD).<br />
<br />
==Download locations==<br />
<br />
'''NOTE''': Please use the Bit Torrent downloads wherever possible, to ensure a clean, uncorrupted download, and then leave it seeding as long as possible. Important: Always burn these DVDs at the slowest possible speed your drive supports ... this is critical!<br />
<br />
To get the latest sources, use [[http://svn.linuxmce.com/trac.cgi/wiki svn]].<br />
<br />
This wiki page is editable so users can add additional mirrors. If you would like to mirror LinuxMCE, please contact danielk@cuymedia.net. He will give you rsync access to the linuxmce.org servers so you can automatically download the releases ahead of time.<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" style="border-collapse:collapse; border-color:#8eabd0; background:#e7edf5"<br />
|- style="background: lightsteelblue"<br />
|-<br />
!Official Torrents:<br />
|<br />
*[http://torrents.thepiratebay.org/4175308/LinuxMCE_Install_DVD_for_i386_-_0710_RC2.4175308.TPB.torrent LinuxMCE-DVD-i386-rc2.iso]<br />
*[http://torrents.thepiratebay.org/4175304/LinuxMCE_Install_Upgrade_DVD_for_i386_-_0710_RC2.4175304.TPB.torrent LinuxMCE-DVD-DL-i386-rc2.iso]<br />
*[http://torrents.thepiratebay.org/4175297/LinuxMCE_Install_CDs_for_i386_-_0710_RC2.4175297.TPB.torrent LinuxMCE-CD1-i386-rc2.iso LinuxMCE-CD2-i386-rc2.iso]<br />
*[http://torrents.thepiratebay.org/4175299/LinuxMCE_Install_DVD_for_AMD64_-_0710_RC2.4175299.TPB.torrent LinuxMCE-DVD-amd64-rc2]<br />
*[http://torrents.thepiratebay.org/4175295/LinuxMCE_Install_CDs_for_AMD64_-_0710_RC2.4175295.TPB.torrent LinuxMCE-CD1-amd64-rc2.iso LinuxMCE-CD2-amd64-rc2.iso]<br />
<br />
<br />
<br />
Please help us seed! Leave your torrent open for as long as possible after your download finishes.<br />
|-<br />
|-<br />
!Worldwide (CoBlitz):<br />
|<br />
*http://coblitz.codeen.org/linuxmce.iptp.org/710/LinuxMCE-DVD-i386-rc2.iso 3.9G<br />
*http://coblitz.codeen.org/linuxmce.iptp.org/710/LinuxMCE-DVD-DL-i386-rc2.iso 7.0G<br />
*http://coblitz.codeen.org/linuxmce.iptp.org/710/LinuxMCE-CD1-i386-rc2.iso 681M<br />
*http://coblitz.codeen.org/linuxmce.iptp.org/710/LinuxMCE-CD2-i386-rc2.iso 678M<br />
*http://coblitz.codeen.org/linuxmce.iptp.org/710/LinuxMCE-DVD-amd64-rc2.iso 3.9G<br />
*http://coblitz.codeen.org/linuxmce.iptp.org/710/LinuxMCE-DVD-DL-amd64-rc2.iso 7.1G<br />
*http://coblitz.codeen.org/linuxmce.iptp.org/710/LinuxMCE-CD1-amd64-rc2.iso 692M<br />
*http://coblitz.codeen.org/linuxmce.iptp.org/710/LinuxMCE-CD2-amd64-rc2.iso 695M<br />
|-<br />
|-<br />
|-<br />
|-<br />
!Europe (full):<br />
|<br />
*http://linuxmce.iptp.org/<br />
*ftp://ftp.possy.de<br />
|-<br />
|-<br />
!Middle East (full):<br />
|<br />
<!-- *http://mirror.mirimar.net/linuxmce/ (CDs only so far for 710RC2) Ran out of space --><br />
|-<br />
|-<br />
!Australia (full):<br />
|<br />
*http://linuxmce.ihas.com.au/ (for NZ and AU only, others are heavily throttled)<br />
*http://mirror.waia.asn.au/pub/linuxmce/<br />
*http://mirror.internode.on.net/pub/linuxmce/<br />
|-<br />
|-<br />
<br />
|-<br />
|-<br />
!Europe (partial):<br />
|<br />
<!-- *http://www.tsl.csd.uoc.gr/users/koutras/download/linuxmce/ (0704 release & beta only) --><br />
<br />
|-<br />
|-<br />
|-<br />
|-<br />
!USA (full):<br />
|<br />
*http://mirror.mrvining.com/linuxmce.php (latest release only for now)<br />
|-<br />
|-<br />
!USA (partial):<br />
|<br />
*http://www.linuxmcecookbook.com/iso/i386 (latest i386 release CD's only)<br />
*http://mirrorlinux.net/distros/mce710rc2/ (latest release only)<br />
|-<br />
|}<br />
<br />
<br />
Please see the [http://www.linuxmce.org/news.php?id=25 release announcement] on the front page for the md5sums of the files. Since this wiki page is editable we can not keep the md5sums here without the risk of tampering.</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Installation_Guide&diff=18093Installation Guide2009-03-23T23:52:38Z<p>Colinjones: /* Choosing type of Core */ removed detail on disked MD for now...</p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
''After installation please visit [http://linuxmce.org/troubles.php this page] and fill in any information you have about the installation process. This will aid the developers in fixing any faults.''<br />
<br />
''' If you want to install LinuxMCE using the DVD, follow [[DVD Installation|these steps.]]'''<br />
<br />
== Hardware notes ==<br />
<br />
See [[Hardware|this section for general hardware]] recommendations, and [[Video#PC_Preparation|this advice for PC preparation]].<br />
<br />
LinuxMCE differs from other Home Theater PC systems in that some functions are performed by a [[Core]] PC and some functions are performed by a [[Media Director]] PC. A [[hybrid]] Core/Media Director PC does both.<br />
<br />
For the central LinuxMCE Core server that will function on a home automation network, most recommended installations suggest 2 network interface cards (NICs). If you don't have a second NIC card already installed, it is easiest to do so <i>before</i> installing Kubuntu/LinuxMCE, since the second card will then be recognised and configured correctly during the initial installation. You won't have to fiddle with setting it up later. See [[Internal_LAN_setup|this section]] for tips on setting up a nested LinuxMCE LAN within an existing home LAN.<br />
<br />
(If you will have only a single PC acting as a hybrid Core/Media Director, 2 cards aren't strictly necessary, but putting them in at this stage will allow you to expand your network down the line.)<br />
<br />
For a PC acting as a Media Director (either as a standalone or as a hybrid), an nVidia graphics card is strongly recommended so that you can display the [[Selecting the Right UI|User Interface]] in the highest resolution (UI2). If you don't have one installed, it is easiest to do so before starting software installation. It is probably best to stick with an nVidia card on the Core PC as well. Make sure the card is installed prior to software installation.<br />
<br />
[[Video|Check out this video and example installation]] of a complete installation that took this guy a few days and will likely take you a few weeks.<br />
<br />
==Kubuntu 7.10 (Gutsy)==<br />
<br />
Note:<br />
LinuxMCE 0704 (beta) was used only with Kubuntu Desktop version 7.04 (Feisty). The [[current version]] is [[Mirrors_0710|LinuxMCE 0710]] and is meant to be used only with Kubuntu Desktop version 7.10 (Gutsy). A version compatible with Kubuntu version 8.10 is planned for the future.<br />
<br />
Steps for installing Linux MCE on an Kubuntu 7.10 (Gutsy Gibbon) system :<br />
<br />
===Existing Kubuntu 7.10 installation===<br />
<br />
You can install LinuxMCE 0710 on a pre-existing installation of Kubuntu 7.10 using the 2 CD install method (but not the DVD method). To complete the installation you will need a Kubuntu Desktop 7.10 Live CD available, or at least a copy of the .iso file somewhere on your hard drive. (If you need to obtain one, see the next section for the download link. There are instructions if you want to burn a Live CD.)<br />
<br />
The install process will partially overwrite your previous Kubuntu installation using configuration files from the Live CD which are known to be uniquely compatible with LinuxMCE. If you have previously modified your Kubuntu system (subsequent to its original installation), you may lose some of your configuration files because LinuxMCE modifies them to suit its own needs. Therefore, do not install LinuxMCE on a mission-critical PC if you don't want to risk this. (You should dedicate one PC to be a LinuxMCE core server, anyway.)<br />
<br />
===New installation===<br />
If you ''don't'' already have an Kubuntu system installed, follow these generic steps to install Kubuntu Desktop 7.10 from the Live CD:<br />
# Download the CD .iso image for Kubuntu desktop- either the [http://releases.ubuntu.com/kubuntu/7.10/kubuntu-7.10-desktop-i386.iso 32-bit version] or the [http://releases.ubuntu.com/kubuntu/7.10/kubuntu-7.10-desktop-amd64.iso 64-bit version], depending on your processor. Use the 32-bit version if in doubt. Note that LinuxMCE comes in both a 32-bit and a 64-bit version as well, so you must match. (If the above links are down, try this alternate site for the appropriate [http://de.releases.ubuntu.com/kubuntu/ Kubuntu Desktop Live CD].)<br />
# If you don't know how to burn the .iso file to a bootable CD, then see [https://help.ubuntu.com/community/BurningIsoHowto these instructions].<br />
# Boot the Kubuntu Desktop 7.10 LiveCD.<br />
# Choose 'Start or install Kubuntu'.<br />
# When Kubuntu's desktop appears, click on 'Install'.<br />
# A short wizard will guide you. Select the language and press 'forward'.<br />
# Choose your timezone and press 'forward'.<br />
# Select the keyboard layout.<br />
# Choose desktop name, a user name and a password. LinuxMCE uses linuxmce for the user and password, so it is often convenient to use linuxmce as the initial user and password at this step, as well.<br />
# Select the partitioning options for your disk. If this is going to be a dedicated server, you can use the entire disk.<br />
# Ready to install.<br />
# Reboot the system and remove the Live CD.<br />
<br />
==LinuxMCE==<br />
===Download LinuxMCE=== <br />
[[Image:Good1.jpg|400px|right]]<br />
From within the Kubuntu 7.10 desktop, open Konqueror or Firefox (the orange and blue icon at the top), and go to [http://www.linuxmce.org www.linuxmce.org]. Select 'Download Instructions' to download the LinuxMCE CD images (.iso files) or the DVD .iso image onto your machine. You can also find the [[current version|current version here]].<br />
<br />
There is a 32-bit version and a 64-bit version of LinuxMCE. If you are using a 64-bit Kubuntu 7.10 installation, download the corresponding LinuxMCE version.<br />
<br />
You will be downloading two .iso files, each one corresponding to a CD image. The installer is able to use the .iso files directly from the hard drive, or you can burn them to a CD and then use them from the CD.<br />
<br />
(Obviously, if you are downloading the .iso files on another computer, you will have to burn them onto CD to use them.)<br />
<br />
To install using the .iso files on your hard drive directly, skip the next step.<br />
<br />
===Burn download to CDs and install from CDs=== <br />
<br />
''(If you plan to install directly from .iso files, skip this step and proceed to the next step.)''<br />
<br />
If you don't know how to burn an .iso file to a CD then see [https://help.ubuntu.com/community/BurningIsoHowto these instructions].<br />
<br />
Burn the two CDs (assuming you are using this method).<br />
<br />
You can then simply place CD 1 in the CD-ROM and the installer will autostart. You will then be prompted to put CD 2 in the drive, followed by the Kubuntu Desktop Live CD (see later sections).<br />
<br />
The rest will take a lot of time but will essentially install automatically. Skip the next two steps and continue with the installation prompts.<br />
<br />
===Installing mce-installer from command prompt===<br />
<br />
''(Skip the next two steps if you are installing from actual CDs.)''<br />
<br />
You can install the mce-installer from a command prompt without the need to burn the ISOs as follows:<br />
cd ''/directory/where/the/downloaded/iso/files/are/''<br />
mkdir -pv mnt<br />
sudo mount LinuxMCE_0704_CD1.iso mnt/ -o loop<br />
sudo dpkg -i mnt/mce-installer_2.0.1-1_i386.deb<br />
sudo umount mnt<br />
rmdir -v mnt<br />
<br />
If you are using the 64-bit version, use mce-installer_2.0.1-1_amd64.deb instead of mce-installer_2.0.1-1_i386.deb.<br />
<br />
===Installing mce-installer from the KDE Menu===<br />
[[Image:Inst1.jpg|400px|right]]<br />
Once you have downloaded the packages and installed the mce-installer onto your disk, run the mce-installer:<br />
<br />
*From Konqueror (or the Dolphin file manager), find and ''right-click'' on the mce-installer icon. Choose Kubuntu Package Menu --> Install Package.<br />
<br />
<br />
(''This step is done automatically if you are installing from a CD.'')<br />
{{clr}}<br />
<br />
===Install LinuxMCE===<br />
[[Image:Snapshot1.JPG|400px|right]]<br />
The mce-installer places an "Install LinuxMCE" icon on your desktop. Click it to start the installation process. A window will appear saying that you will be notified when updates are available. <br />
{{clr}}<br />
<br />
====Choosing type of Core====<br />
[[Image:Snapshot2.JPG|400px|right]]<br />
Choose if you want a dedicated core or a hybrid. (In brief, a hybrid runs as both the Core and as a Media Director. As such, it needs more computing power. [[Do_I_want_a_dedicated_Core%3F|Click here]] to find out more differences between a core and a hybrid). Then click on the "Forward" button. <br />
<br />
If you aren't going to set up an "internal" home automation LAN at this time, but only will use a single PC for all LinuxMCE functions, then make that single PC installation a hybrid.<br />
<br />
However, if you will create an entire home automation network, it is better to use one PC as the dedicated core server (not a hybrid). It will run faster. You can leave it "headless" (no monitor, keyboard, mouse), and leave it always on. In such a situation, "dedicated Core" would be suitable. Nevertheless, it is possible after installation to choose whether to autostart the Core services by themselves, the Media Director services by themselves, or both together. Thus a "hybrid" installation can later used as a "dedicated Core," as a Media Director, or as both (a hybrid). There is little disadavantage, therefore, in choosing "hybrid" at this step. That is what many first time users choose.<br />
<br />
<br />
{{clr}}<br />
<br />
====Choosing Video Card====<br />
[[Image:Snapshot3.JPG|400px|right]]<br />
This step is displayed only when an nNvidia graphics card is detected by LinuxMCE. You will be asked if you want to use the proprietary nVidia driver (the only one that works well with LinuxMCE and nVidia cards), instead of the generic driver (which doesn't work as well). Generally you should use the proprietary driver. This step is here for legal reasons. <br />
{{clr}}<br />
<br />
====Network Configuration====<br />
[[Image:Snapshot4.JPG|400px|right]]<br />
The next screen will ask you whether you want to keep your current network configuration or whether you want to set your network options manually. The "current network configuration" is usually what the Kubuntu Live CD originally detected and setup automatically. Most commonly this configuration instructs the PC to ask for a dynamic IP from your home LAN router's DHCP service. This option is asking whether your LinuxMCE should continue to ask for a dynamic IP from your external LAN's router (using DHCP), or whether you wish to set a static IP address for your LinuxMCE PC. This setting applies only to the (first) NIC card that is connected to the "external" home LAN. Usually keeping the "current network configuration" is sufficient. Then press "Forward".<br />
{{clr}}<br />
<br />
[[Image:Snapshot5.JPG|400px|right]]<br />
If you chose manual installation, you must now choose whether your PC will use a static IP within the external home LAN, or whether it will accept a dynamic IP assigned by the LAN router's DHCP. If you do not have a home LAN and router, but connect directly through a cable modem, you most likely use a (static) IP (that your cable company assigns you). Generally you have to know your IP address, the cable company's gateway IP, and the cable company's DNS server information (which your cable provider must provide to you). In contrast, most DSL providers use DHCP-assigned dynamic IPs, so if you connect directly through a DSL modem, you most likely use DHCP. You don't have to worry about the gateway and DNS server; DHCP usually discovers those for you automatically. (Obviously, if you bought a static IP service from a DSL or T1 provider, you would have to choose static and fill in the information, just as for a cable modem.) <br />
<br />
If you don't know what the heck you have, use DHCP.<br />
{{clr}}<br />
<br />
=====Choosing Mirror for Packages=====<br />
[[Image:Snapshot6.JPG|400px|right]]<br />
You have to choose a mirror. Pick one geographically close to you. Downloads will be faster. <br />
{{clr}}<br />
<br />
=====Choosing DHCP Server=====<br />
[[Image:Snapshot7.JPG|400px|right]]<br />
You will be asked whether you want (the LinuxMCE core server) to Run a DHCP Server or not. The LinuxMCE core server will be the DHCP server for your "internal" home automation network in order to provide plug-and-play detection of network devices like IP Cameras and VOIP phones, and to provide network boot images to any other PC's in the internal home automation network that you might want to use as Media Directors.<br />
<br />
Hopefully you took some advice and already installed a second NIC card. That second NIC card is used so that LinuxMCE can provide an "internal" DHCP network to the PCs (Media Directors), Orbiters, and devices <i>within</I> your automated home network. All ethernet connections from these devices (within the home automation network) must be connected to a switch (or a router with DHCP turned off) which is then in turn connected to this second NIC card. The LinuxMCE core server then performs the DHCP functions for the "internal" home automation network. <br />
<br />
In essence, the "internal" home automation network is nested within your "external" home LAN. Some PCs can remain outside of the internal home automation network by being directly connected to the router, and therefore not connected to the LinuxMCE server. The first NIC card of the LinuxMCE server therefore communicates to the router of your external home LAN. The second NIC is connected to the internal home automation LAN. The LinuxMCE core server only acts as the DHCP server for the devices in the internal home automation LAN. Savvy?<br />
<br />
Generally, you should answer yes to this question. The only time you would answer no is when you will have only one PC that will be a hybrid core server/media director and you do not plan to use any plug-n-play devices other than those connected directly to that single PC.<br />
<br />
You will be then asked if you want to keep the default Internal Network address for the internal home automation LAN or if you want to change it. You might as well accept the default, unless you have some specific reason for specifying a unique IP range.<br />
<br />
Then press 'Forward'.<br />
{{clr}}<br />
<br />
====Choosing Orbiter Interface====<br />
[[Image:Snapshot8.JPG|400px|right]]<br />
In the next window you need to choose what interface you want to use and you have to pick one of three possibilities. There are currently three options: UI1, UI2 with masking, and UI2 with alpha-blending. UI2 requires specific video cards (nVidia). It is best to choose UI1 for the initial installation if you don't have the appropriate nVidia card or if in doubt, as the interface can be changed later. This will reduce the possibility of video card related errors during installation. After installation, you can check to see if your video card can do masking and alpha-blending by following the instructions at [[Graphics Test]].<br />
{{clr}}<br />
<br />
====Installing Additional Packages====<br />
[[Image:Snapshot9.JPG|400px|right]]<br />
On the next step you have to choose if you want to install [http://en.wikipedia.org/wiki/LAME lame] and [http://en.wikipedia.org/wiki/Libdvdcss libdvdcss] and if it is legal in your country to use them. In general you will want to install them both.<br />
{{clr}}<br />
<br />
====Choosing How to Primarily Use the Computer====<br />
[[Image:Snapshot10.JPG|400px|right]]<br />
You have to select how you plan to use your computer, either: <br />
<br />
*Primarily used as a PC -- you can start LinuxMCE manually when you need it, or<br />
<br />
*A dedicated LinuxMCE -- you can start Kubuntu when you need it.<br />
<br />
For the dedicated core server, choose the second option. If you have a power outage, you can then set the computer to auto-reboot and restore your system without intervention. (If you are serious about home automation, it is best to have a dedicated core server, anyway.) It is possible to access the Kubuntu desktop from within LinuxMCE (see [[#Additional Notes|below]]).<br />
<br />
If you choose the first option and have a power outage, then you will require a boot-up script, cron scheduling, or manual intervention in order to restart the LinuxMCE system.<br />
<br />
If you are just experimenting with LinuxMCE and/or primarily use the PC as a Kubuntu desktop, the first option is suitable. Also, if you wish to directly install LinuxMCE directly on a PC that will be used as a Media Director, but intend to trade its function back and forth between that of a Kubuntu desktop and a Media Director, also choose the first option. <br />
<br />
(Many PCs that will be used as Media Directors can simply be [[netboot|netbooted]] from the Core, however, so you do not really need to install LinuxMCE on them at all if you intend to netboot (which is generally easier).) <br />
{{clr}}<br />
<br />
====Installing LinuxMCE Discs====<br />
This step is very important. You have to insert the CD (or point to the location on the hard drive of the .iso file for the CD): <br />
<br />
[[Image:Snapshot11.JPG|400px|right]]<br />
LinuxMCE CD 1<br />
{{clr}}<br />
<br />
<br />
[[Image:Snapshot12.JPG|400px|right]]<br />
LinuxMCE CD 2<br />
{{clr}}<br />
<br />
<br />
[[Image:Snapshot13.JPG|400px|right]]<br />
Kubuntu 7.10 Live CD<br />
{{clr}}<br />
<br />
<br />
[[Image:Snapshot14.JPG|400px|right]] <br />
You can see the message about the Linux MCE system installation.<br />
{{clr}}<br />
<br />
===Installation can take a long time===<br />
Don't worry if the system seems to stop at points or report what seems like error messages. <br />
This is normal since at places it will be testing drivers out, and is only there for the advanced Linux user. <br />
You will get a dialog box if something really does go wrong. And, understand this may take a very long time<br />
since it will in parallel be updating your Kubuntu system to the latest version. Just leave it for an hour <br />
or two and come back later.<br />
<br />
===Installation Complete===<br />
[[Image:Snapshot15.jpg|400px|right]]<br />
After the installation is done you’ll receive a message from the installer that will tell you to restart the system<br />
{{clr}}<br />
<br />
Next follow the [[QuickStart Guide]] to tell LinuxMCE about how you want to use it.<br />
===Additional Notes===<br />
If you specified that LinuxMCE should startup by default, then after rebooting you will see LinuxMCE (not the Kubuntu desktop). If you will use this computer as a Media PC only, you don't need to access the Kubuntu desktop for any further set up -- all setup is done from the from the [[LinuxMCE Admin Website]] or through the LinuxMCE [[Orbiter]] User Interface.<br />
<br />
If you would like to use this PC as a Kubuntu PC from ''within'' LinuxMCE, however, a menu option on the on-screen Orbiter User Interface of a Media Director is provided to bring up the KDE (Kubuntu) desktop. (This may not work well if the Media Director has been [[netboot|netbooted]].)<br />
<br />
You can also press Ctrl+Alt+F2 from within LinuxMCE to bring up the KDE desktop (then login and type StartX). <br />
<br />
If you specified that the Kubuntu desktop should be run by default, you can then start LinuxMCE manually from within the Kubuntu menu: Applications-->Sound & Video-->Start Media Center. (You can also click on the LinuxMCE icon on the Kubuntu desktop that was placed there during installation.<br />
<br />
When LinuxMCE is running, you can toggle back and forth between them by pressing '''Ctrl+Alt+F7''' for Kubuntu or '''Ctrl+Alt+F11''' for LinuxMCE.<br />
<br />
[[Category: Tutorials]]</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Mirrors_710&diff=18027Mirrors 7102009-03-18T23:51:31Z<p>Colinjones: /* LinuxMCE 0710 */</p>
<hr />
<div>= LinuxMCE 0710 =<br />
'''Before installing, check out the [[Known Issues|Known issues]], and please read the [[Installation Guide]] and/or the [[DVD Installation]] guide.''' Installing from DVD is the fastest. Installing from CD .iso images on your hard disk is second fastest (you will need to install Kubuntu 7.10 first), and installing from burned CDs is slowest.<br />
<br />
'''NOTE:''' Please download from the torrent links rather than the mirrors if possible. You are far less likely to get a corruption that will kill your install.<br />
<br />
'''NOTE:''' It is a good idea to use md5sum and the checksums to verify your download is not corrupted.<br />
<br />
'''NOTE:''' It is ''essential'' that you burn your CDs and DVDs using the slowest possible speed your burner supports - faster speeds regularly cause corruptions on the burn which will be fatal to your install.<br />
<br />
<br />
== What you have to download ==<br />
To install LinuxMCE you need to download the DVD (which includes everything needed for the installation) or you can download both LinuxMCE CD's plus a Kubuntu 7.10 CD. You can also choose to download the Dual Layer DVD which includes extra demo media.<br />
<br />
'''''Warning: The DVD installation will wipe the entire disk of the machine -- all previous data will be permanently lost!''''' <br />
(Note: There is a new "keep settings" option which will preserve data in the home directory for most, '''''but not all''''', installations. Also, there are instructions on how to use the [[DVD Install And Custom Partitions|DVD Install with custom partitions]])<br />
<br />
LinuxMCE 0710 was released on May 7th, 2008. This is also known as LinuxMCE 0710 RC2.<br />
<br />
====NOTES:====<br />
<br />
- To upgrade from a 0710 beta to 0710, you can use "LinuxMCE Install CDs for i386" or "LinuxMCE Install DVD for i386" with "keep settings" option. <br />
<br />
- To upgrade from 0704, you can use :<br />
a) "LinuxMCE Install CDs for i386 - 0710 RC2" or "LinuxMCE Install DVD for i386 - 0710 RC2" with "keep settings" option or<br />
b) the upgrade helper application from [http://www.linuxmce.com/upgrade/gutsy-upgrade-scripts_0.1.0-2_i386.deb gutsy-upgrade-scripts_0.1.0-2_i386.deb] and choose to install from web or from DVD (you must have the double layer DVD).<br />
<br />
==Download locations==<br />
<br />
To get the latest sources, use [[http://svn.linuxmce.com/trac.cgi/wiki svn]].<br />
<br />
This wiki page is editable so users can add additional mirrors. If you would like to mirror LinuxMCE, please contact danielk@cuymedia.net. He will give you rsync access to the linuxmce.org servers so you can automatically download the releases ahead of time.<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" style="border-collapse:collapse; border-color:#8eabd0; background:#e7edf5"<br />
|- style="background: lightsteelblue"<br />
|-<br />
!Official Torrents:<br />
|<br />
*[http://torrents.thepiratebay.org/4175308/LinuxMCE_Install_DVD_for_i386_-_0710_RC2.4175308.TPB.torrent LinuxMCE-DVD-i386-rc2.iso]<br />
*[http://torrents.thepiratebay.org/4175304/LinuxMCE_Install_Upgrade_DVD_for_i386_-_0710_RC2.4175304.TPB.torrent LinuxMCE-DVD-DL-i386-rc2.iso]<br />
*[http://torrents.thepiratebay.org/4175297/LinuxMCE_Install_CDs_for_i386_-_0710_RC2.4175297.TPB.torrent LinuxMCE-CD1-i386-rc2.iso LinuxMCE-CD2-i386-rc2.iso]<br />
*[http://torrents.thepiratebay.org/4175299/LinuxMCE_Install_DVD_for_AMD64_-_0710_RC2.4175299.TPB.torrent LinuxMCE-DVD-amd64-rc2]<br />
*[http://torrents.thepiratebay.org/4175295/LinuxMCE_Install_CDs_for_AMD64_-_0710_RC2.4175295.TPB.torrent LinuxMCE-CD1-amd64-rc2.iso LinuxMCE-CD2-amd64-rc2.iso]<br />
<br />
<br />
<br />
Please help us seed! Leave your torrent open for as long as possible after your download finishes.<br />
|-<br />
|-<br />
!Worldwide (CoBlitz):<br />
|<br />
*http://coblitz.codeen.org/linuxmce.iptp.org/710/LinuxMCE-DVD-i386-rc2.iso 3.9G<br />
*http://coblitz.codeen.org/linuxmce.iptp.org/710/LinuxMCE-DVD-DL-i386-rc2.iso 7.0G<br />
*http://coblitz.codeen.org/linuxmce.iptp.org/710/LinuxMCE-CD1-i386-rc2.iso 681M<br />
*http://coblitz.codeen.org/linuxmce.iptp.org/710/LinuxMCE-CD2-i386-rc2.iso 678M<br />
*http://coblitz.codeen.org/linuxmce.iptp.org/710/LinuxMCE-DVD-amd64-rc2.iso 3.9G<br />
*http://coblitz.codeen.org/linuxmce.iptp.org/710/LinuxMCE-DVD-DL-amd64-rc2.iso 7.1G<br />
*http://coblitz.codeen.org/linuxmce.iptp.org/710/LinuxMCE-CD1-amd64-rc2.iso 692M<br />
*http://coblitz.codeen.org/linuxmce.iptp.org/710/LinuxMCE-CD2-amd64-rc2.iso 695M<br />
|-<br />
|-<br />
|-<br />
|-<br />
!Europe (full):<br />
|<br />
*http://linuxmce.iptp.org/<br />
*ftp://ftp.possy.de<br />
|-<br />
|-<br />
!Middle East (full):<br />
|<br />
<!-- *http://mirror.mirimar.net/linuxmce/ (CDs only so far for 710RC2) Ran out of space --><br />
|-<br />
|-<br />
!Australia (full):<br />
|<br />
*http://linuxmce.ihas.com.au/ (for NZ and AU only, others are heavily throttled)<br />
*http://mirror.waia.asn.au/pub/linuxmce/<br />
*http://mirror.internode.on.net/pub/linuxmce/<br />
|-<br />
|-<br />
<br />
|-<br />
|-<br />
!Europe (partial):<br />
|<br />
<!-- *http://www.tsl.csd.uoc.gr/users/koutras/download/linuxmce/ (0704 release & beta only) --><br />
<br />
|-<br />
|-<br />
|-<br />
|-<br />
!USA (full):<br />
|<br />
|-<br />
|-<br />
!USA (partial):<br />
|<br />
*http://www.linuxmcecookbook.com/iso/i386 (latest i386 release CD's only)<br />
*http://mirrorlinux.net/distros/mce710rc2/ (latest release only)<br />
|-<br />
|}<br />
<br />
<br />
Please see the [http://www.linuxmce.org/news.php?id=25 release announcement] on the front page for the md5sums of the files. Since this wiki page is editable we can not keep the md5sums here without the risk of tampering.</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Mirrors_710&diff=18026Mirrors 7102009-03-18T23:51:01Z<p>Colinjones: /* LinuxMCE 0710 */ some notes on best practice for installing</p>
<hr />
<div>= LinuxMCE 0710 =<br />
'''Before installing, check out the [[Known Issues|Known issues]], and please read the [[Installation Guide]] and/or the [[DVD Installation]] guide.''' Installing from DVD is the fastest. Installing from CD .iso images on your hard disk is second fastest (you will need to install Kubuntu 7.10 first), and installing from burned CDs is slowest.<br />
<br />
'''NOTE:''' Please download from the torrent links rather than the mirrors if possible. You are far less likely to get a corruption that will kill your install.<br />
'''NOTE:''' It is a good idea to use md5sum and the checksums to verify your download is not corrupted.<br />
'''NOTE:''' It is ''essential'' that you burn your CDs and DVDs using the slowest possible speed your burner supports - faster speeds regularly cause corruptions on the burn which will be fatal to your install.<br />
<br />
<br />
== What you have to download ==<br />
To install LinuxMCE you need to download the DVD (which includes everything needed for the installation) or you can download both LinuxMCE CD's plus a Kubuntu 7.10 CD. You can also choose to download the Dual Layer DVD which includes extra demo media.<br />
<br />
'''''Warning: The DVD installation will wipe the entire disk of the machine -- all previous data will be permanently lost!''''' <br />
(Note: There is a new "keep settings" option which will preserve data in the home directory for most, '''''but not all''''', installations. Also, there are instructions on how to use the [[DVD Install And Custom Partitions|DVD Install with custom partitions]])<br />
<br />
LinuxMCE 0710 was released on May 7th, 2008. This is also known as LinuxMCE 0710 RC2.<br />
<br />
====NOTES:====<br />
<br />
- To upgrade from a 0710 beta to 0710, you can use "LinuxMCE Install CDs for i386" or "LinuxMCE Install DVD for i386" with "keep settings" option. <br />
<br />
- To upgrade from 0704, you can use :<br />
a) "LinuxMCE Install CDs for i386 - 0710 RC2" or "LinuxMCE Install DVD for i386 - 0710 RC2" with "keep settings" option or<br />
b) the upgrade helper application from [http://www.linuxmce.com/upgrade/gutsy-upgrade-scripts_0.1.0-2_i386.deb gutsy-upgrade-scripts_0.1.0-2_i386.deb] and choose to install from web or from DVD (you must have the double layer DVD).<br />
<br />
==Download locations==<br />
<br />
To get the latest sources, use [[http://svn.linuxmce.com/trac.cgi/wiki svn]].<br />
<br />
This wiki page is editable so users can add additional mirrors. If you would like to mirror LinuxMCE, please contact danielk@cuymedia.net. He will give you rsync access to the linuxmce.org servers so you can automatically download the releases ahead of time.<br />
<br />
{| border="1" cellspacing="0" cellpadding="5" style="border-collapse:collapse; border-color:#8eabd0; background:#e7edf5"<br />
|- style="background: lightsteelblue"<br />
|-<br />
!Official Torrents:<br />
|<br />
*[http://torrents.thepiratebay.org/4175308/LinuxMCE_Install_DVD_for_i386_-_0710_RC2.4175308.TPB.torrent LinuxMCE-DVD-i386-rc2.iso]<br />
*[http://torrents.thepiratebay.org/4175304/LinuxMCE_Install_Upgrade_DVD_for_i386_-_0710_RC2.4175304.TPB.torrent LinuxMCE-DVD-DL-i386-rc2.iso]<br />
*[http://torrents.thepiratebay.org/4175297/LinuxMCE_Install_CDs_for_i386_-_0710_RC2.4175297.TPB.torrent LinuxMCE-CD1-i386-rc2.iso LinuxMCE-CD2-i386-rc2.iso]<br />
*[http://torrents.thepiratebay.org/4175299/LinuxMCE_Install_DVD_for_AMD64_-_0710_RC2.4175299.TPB.torrent LinuxMCE-DVD-amd64-rc2]<br />
*[http://torrents.thepiratebay.org/4175295/LinuxMCE_Install_CDs_for_AMD64_-_0710_RC2.4175295.TPB.torrent LinuxMCE-CD1-amd64-rc2.iso LinuxMCE-CD2-amd64-rc2.iso]<br />
<br />
<br />
<br />
Please help us seed! Leave your torrent open for as long as possible after your download finishes.<br />
|-<br />
|-<br />
!Worldwide (CoBlitz):<br />
|<br />
*http://coblitz.codeen.org/linuxmce.iptp.org/710/LinuxMCE-DVD-i386-rc2.iso 3.9G<br />
*http://coblitz.codeen.org/linuxmce.iptp.org/710/LinuxMCE-DVD-DL-i386-rc2.iso 7.0G<br />
*http://coblitz.codeen.org/linuxmce.iptp.org/710/LinuxMCE-CD1-i386-rc2.iso 681M<br />
*http://coblitz.codeen.org/linuxmce.iptp.org/710/LinuxMCE-CD2-i386-rc2.iso 678M<br />
*http://coblitz.codeen.org/linuxmce.iptp.org/710/LinuxMCE-DVD-amd64-rc2.iso 3.9G<br />
*http://coblitz.codeen.org/linuxmce.iptp.org/710/LinuxMCE-DVD-DL-amd64-rc2.iso 7.1G<br />
*http://coblitz.codeen.org/linuxmce.iptp.org/710/LinuxMCE-CD1-amd64-rc2.iso 692M<br />
*http://coblitz.codeen.org/linuxmce.iptp.org/710/LinuxMCE-CD2-amd64-rc2.iso 695M<br />
|-<br />
|-<br />
|-<br />
|-<br />
!Europe (full):<br />
|<br />
*http://linuxmce.iptp.org/<br />
*ftp://ftp.possy.de<br />
|-<br />
|-<br />
!Middle East (full):<br />
|<br />
<!-- *http://mirror.mirimar.net/linuxmce/ (CDs only so far for 710RC2) Ran out of space --><br />
|-<br />
|-<br />
!Australia (full):<br />
|<br />
*http://linuxmce.ihas.com.au/ (for NZ and AU only, others are heavily throttled)<br />
*http://mirror.waia.asn.au/pub/linuxmce/<br />
*http://mirror.internode.on.net/pub/linuxmce/<br />
|-<br />
|-<br />
<br />
|-<br />
|-<br />
!Europe (partial):<br />
|<br />
<!-- *http://www.tsl.csd.uoc.gr/users/koutras/download/linuxmce/ (0704 release & beta only) --><br />
<br />
|-<br />
|-<br />
|-<br />
|-<br />
!USA (full):<br />
|<br />
|-<br />
|-<br />
!USA (partial):<br />
|<br />
*http://www.linuxmcecookbook.com/iso/i386 (latest i386 release CD's only)<br />
*http://mirrorlinux.net/distros/mce710rc2/ (latest release only)<br />
|-<br />
|}<br />
<br />
<br />
Please see the [http://www.linuxmce.org/news.php?id=25 release announcement] on the front page for the md5sums of the files. Since this wiki page is editable we can not keep the md5sums here without the risk of tampering.</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Suspend&diff=17964Suspend2009-03-13T18:08:52Z<p>Colinjones: removed unnecessary stuff to stop devices, script now does this</p>
<hr />
<div>[[Category: Tutorials]]<br />
<br />
{| align="right"<br />
| __TOC__<br />
|}<br />
This article describes how to suspend your MD to RAM (standby) or to disk (hibernation).<br />
<br />
Please note that this functionality is not yet integrated into LinuxMCE, and will thus need some editing of Linux configuration files. Integration of the suspend functions has not been reported in the new issue-tracking system. The old Mantis-ID is 3822.<br />
<br />
Ubuntu 710 removed the s2ram utility used to suspend-to-ram. But suspend to disk may still work, depending on your hardware and drivers. It might also be possible to use the s2both command, which is supposed to suspend to RAM and at the same time write the image to disk, to have a backup in case of power-out.<br />
<br />
Ubuntu 810 uses pm-utils as the standard suspend/resume framework. Using this is recommended. It will also work with 710. <br />
Description of how to use pm-utils are below.<br />
<br />
== Motivation ==<br />
* Saving power<br />
* Quick boot (usefull if your MD is noisy and you turn it off when not in use)<br />
<br />
== Setup using PM-Utils ==<br />
PM-utils are the new package in Ubuntu 810 that are responsible for suspending and resuming your computer. It uses the HAL database to find information about what special tricks it need to pull off to get your particular hardware to successfully resume.<br />
<br />
The setup for pm-utils was tested after completing the hibernate setup below, so you may have to include some parts of that to get this to work. In particular the NVidia part may be required.<br />
<br />
Install pm-utils<br />
apt-get install pm-utils<br />
<br />
Create a file /etc/pm/sleep.d/01lmce<br />
#!/bin/bash<br />
<br />
. /usr/lib/pm-utils/functions<br />
<br />
RETVAL=0<br />
case "$1" in<br />
hibernate|suspend)<br />
/usr/pluto/bin/suspend.sh<br />
RETVAL=$?<br />
;;<br />
thaw|resume)<br />
/usr/pluto/bin/resume.sh<br />
;;<br />
*)<br />
;;<br />
esac<br />
<br />
exit $RETVAL<br />
<br />
Create a file /usr/pluto/bin/resume.sh<br />
#!/bin/bash<br />
<br />
/usr/bin/screen -d -m -S "LMCE Launch Manager" /usr/pluto/bin/lmce_launch_manager.sh<br />
<br />
Create a file /usr/pluto/bin/suspend.sh<br />
#!/bin/bash<br />
<br />
. /usr/pluto/bin/Config_Ops.sh<br />
. /usr/pluto/bin/SQL_Ops.sh<br />
. /usr/pluto/bin/pluto.func<br />
<br />
echo "LMCE Suspend Process Started"<br />
<br />
## Turn on WOL<br />
<br />
/usr/pluto/bin/enable_wol.sh<br />
<br />
## Find local IP address<br />
<br />
LocalIP=$(ip addr show dev eth0|grep "inet "|cut -f6 -d" "|cut -f1 -d/)<br />
<br />
## Use local IP address to find MD device number<br />
<br />
FindMDDeviceQ="SELECT PK_Device FROM Device<br />
WHERE IPAddress='$LocalIP';<br />
"<br />
<br />
DeviceID=$(RunSQL "$FindMDDeviceQ")<br />
<br />
## Identify immediate children DCE devices that are currently Registered<br />
<br />
FindChildrenQ="SELECT Device.PK_Device<br />
FROM Device<br />
JOIN DeviceTemplate ON Device.FK_DeviceTemplate=DeviceTemplate.PK_DeviceTemplate<br />
LEFT JOIN Device AS Device_Parent on Device.FK_Device_ControlledVia=Device_Parent.PK_Device<br />
LEFT JOIN DeviceTemplate AS DeviceTemplate_Parent<br />
ON Device_Parent.FK_DeviceTemplate=DeviceTemplate_Parent.PK_DeviceTemplate<br />
WHERE (Device.FK_Device_ControlledVia=$DeviceID<br />
OR (Device_Parent.FK_Device_ControlledVia=$DeviceID AND DeviceTemplate_Parent.FK_DeviceCategory IN (6,7,8) ) )<br />
AND DeviceTemplate.FK_DeviceCategory <> 1<br />
AND DeviceTemplate.ImplementsDCE=1<br />
AND Device.Registered=1;<br />
"<br />
<br />
DeviceList=$(RunSQL "$FindChildrenQ")<br />
<br />
## Send SYSCOMMAND_0 (device shutdown) message to all immediate children. These devices will relay the message to all decendents<br />
<br />
for Device in $DeviceList; do<br />
<br />
/usr/pluto/bin/MessageSend "$DCERouter" 0 "$Device" 7 0 163 "start_local_devices"<br />
<br />
done<br />
<br />
## Send SYSCOMMAND_0 message to MD device itself<br />
/usr/pluto/bin/MessageSend dcerouter 0 $DeviceID 7 0 163 "start_local_devices"<br />
<br />
<br />
## Wait for DCE devices to complete their shutdown<br />
<br />
MaxLoopCount=50<br />
for ((i = 0; i < MaxLoopCount; i++)); do<br />
Devices=$(cat /usr/pluto/locks/pluto_spawned_local_devices.txt | grep -v '^$' | tr '\n' ',')<br />
Devices="${Devices%,}"<br />
<nowiki>if [[ -z "$Devices" ]]; then</nowiki><br />
break<br />
fi<br />
RegCount=0<br />
Q="SELECT COUNT(*) FROM Device WHERE PK_Device IN ($Devices) AND Registered=1"<br />
RegCount=$(RunSQL "$Q")<br />
<nowiki> if [[ "$RegCount" -eq 0 ]]; then </nowiki><br />
break<br />
fi<br />
echo "Waiting for $RegCount devices to shutdown ($Devices)"<br />
sleep 1<br />
done<br />
<br />
echo "Done waiting"<br />
<br />
## Kill the LM processes<br />
<br />
killall -q -s SIGKILL -r lmce_launch_manager\*<br />
<br />
Make sure all three scripts are executable<br />
chmod +x <script><br />
<br />
<br />
That's it. The setup is complete. You can try to suspend by typing pm-suspend. The suspend can take some time as LMCE is stopping the devices on your MD. If your hardware is supported, it will resume and restart lmce.<br />
<br />
== Setup using hibernate ==<br />
It is now recommended to use the pm-utils way of suspending. This way may still work though.<br />
<br />
On the MD in question, make sure you have the uswsusp and hibernate packages installed.<br />
<br />
apt-get install uswsusp hibernate<br />
<br />
Check your BIOS setting to make sure that suspend to ram is enabled.<br />
<br />
== Using NVidia graphics card ==<br />
<br />
Edit your xorg.conf file and add this line to the "Device" section:<br />
<br />
Option "NvAGP" "1"<br />
<br />
Also make sure no other ''vendor'' AGP modules are loaded, like intel_agp, sis_agp etc. The ''agpgart'' module is fine, though.<br />
Use<br />
lspci | grep agp<br />
to list all loaded agp modules.<br />
<br />
If you see any agp modules besides agpgart, add a line to /etc/modprobe.d/blacklist to blacklist the module.<br />
<br />
Edit the /etc/hibernate/ram.conf file, and comment the two lines <br />
#EnableVbeTool yes<br />
#VbetoolPost yes<br />
<br />
Edit the /etc/hibernate/blacklisted-modules, and comment the line:<br />
#nvidia<br />
<br />
<br />
== Lirc module unloading and reloading ==<br />
<br />
'''Not needed for 710'''<br />
<br />
Some lirc modules (at least lirc_serial) needs reloading after suspend. Like for enabling wol, we add a file in the /etc/hibernate/scriptlets.d/ folder, with a descriptive name ''lirc''.<br />
# Stops and unloads the current lirc module before suspending, and<br />
# restarts lirc when resuming<br />
<br />
AddSuspendHook 30 UnloadLirc<br />
AddResumeHook 30 StartLirc<br />
<br />
UnloadLirc() {<br />
/etc/init.d/lirc stop<br />
if [ -f /etc/lirc/hardware.conf ];then<br />
. /etc/lirc/hardware.conf<br />
rmmod $MODULES<br />
fi<br />
}<br />
<br />
StartLirc() {<br />
/etc/init.d/lirc start<br />
}<br />
<br />
== Suspend to RAM ==<br />
<br />
Run <br />
hibernate-ram<br />
to suspends the MD to ram. The script first checks if it recognizes your hardware, to take the correct actions before suspending.<br />
If you get a message that your machine is unknown, edit the /etc/hibernate/ususpend-ram.conf file, and un-comment the <br />
USuspendRamForce yes<br />
line, to force it to suspend anyway.<br />
<br />
== Suspend to disk / Hibernation ==<br />
<br />
Before trying to set up suspend to disk, I recommend that you first get suspend to ram working. All setup needed for suspend to RAM is also required for suspend to disk.<br />
<br />
To enable suspend to disk, you will need to set up a swap partition on the MD in question. This is because the suspend implementation in the current kernel can only save the memory to the swap area. To achieve this on a diskless MD, you might use a CF card and a CF/IDE adapter. A CF card with 1 or 2 GB should be sufficient. However, with a CF card, you should make sure your MD has enough physical ram to avoid using swap, because CF cards may have lower performance than a normal IDE disk.<br />
<br />
<br />
Edit the /etc/fstab file for the MD and add an entry for the swap partition<br />
/dev/sda1 none swap sw 0 0<br />
Adjust the partition to match your swap partition. Make sure you select the right one, or you WILL destroy your data. In the case of a diskless MD, you will probably only have one partition (a CF card for instance). You might need to do partitioning on the disk if it is a empty disk. This is outside the scope of this article.<br />
<br />
<br />
Copy two files from /usr/share/initramfs-tools/scripts/local-premount/ (resume, uswsusp) into /etc/initramfs-tools/scripts/nfs-premount/<br />
Not sure if both files are required, but it doesn't hurt.<br />
<br />
These scripts will run before any file systems have been mounted, and after any disk drivers has been loaded. Both are important: mounting any file systems before resuming can corrupt your data, according to the documentation. And we need to have the drivers loaded to access the suspended image.<br />
<br />
<br />
After copying the two files, run<br />
update-initramfs -u<br />
to update the initramfs image, which includes the scripts in the boot up process.<br />
<br />
<br />
Now reboot your MD. When it has started up again, you can type<br />
hibernate-disk<br />
to initiate suspend to disk.<br />
<br />
== References ==<br />
The hibernate script uses uswsusp by default when trying to suspend to ram. For more information about the s2ram utility used, read the [http://en.opensuse.org/S2ram S2ram howto]<br />
<br />
The [http://en.opensuse.org/NVidia_Suspend_HOWTO NVidia suspend howto]</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Network_Setup&diff=17892Network Setup2009-03-05T21:29:55Z<p>Colinjones: /* Network After LinuxMCE is Installed */ static IP info</p>
<hr />
<div>[[Category:Hardware]]<br />
[[Category:Networking]]<br />
[[Category:Tutorials]]<br />
[[Category:Networking Setups]]<br />
=Overview=<br />
<br />
There is regularly some confusion over how much of your existing home network LinuxMCE requires you to change. Many people incorrectly believe that significant changes are required. In the most common case of home networks, almost no change at all is required. The Core server requires 2 NICs (Network Interface Cards). One is known as the "External" NIC and the other as the "Internal" NIC.<br />
<br />
=Existing Home Network=<br />
<br />
[[Image:Before.PNG]]<br />
<br />
Above we see a very simple home network setup. All devices are connected to a switch, which in turn is connected to the LAN port of a broadband router. In this topology, most people have their broadband router provide dynamic IP addresses to all other devices via DHCP.<br />
<br />
<br />
<br />
=Network After LinuxMCE is Installed=<br />
<br />
[[Image:After.PNG]]<br />
<br />
Above we see the same network, now LinuxMCE enabled. NOTE: The ''only'' change is the Core LinuxMCE server has been inserted between the switch and the broadband router. In practice, this means disconnecting the Cat5e/6 patch cable, shown in the first diagram, from the broadband router and connecting it into the "Internal" NIC of the of the Core server (shown here on the right of the red box). Next, get a new Cat5e/6 patch cable and connect one end to the "External" NIC of the Core server (shown here on the left of the red box), and the other end back into the LAN port of the broadband router. Your setup is now complete!<br />
<br />
In this network, your broadband router can continue providing dynamic IP addresses to the "External" NIC of the core - however, there is nothing stopping you fixing this IP address if you prefer. In which case your broadband router's DHCP server is no longer needed. For the Internal or LinuxMCE network, the Core now provides DHCP services to all devices. IMPORTANT: LinuxMCE needs to be the (only) DHCP server for the Internal network because it provides much more than just IP addresses to these devices. So it is important that you allow it to do this, and leave all your internal devices set to acquire their IP address via DHCP so that LinuxMCE works correctly. This is the only supported configuration - however, as you can see, the impact is either negligible or non-existent.<br />
<br />
It is also well worth noting that your PCs will be detected as "file servers" by LMCE, and when the DHCP server assigns an IP address this is effectively permanent/static. You do not need to worry about the IP address changing all the time, it doesn't! This information will be of particular interest to those who want to NAT or port forward services from the Internet to specific PCs, such as Remote Desktop sessions and Bit Torrent clients.<br />
<br />
In this page, a reference to the "Core server" can either be a dedicated Core or a Hybrid - a core, plus Media Director functionality - either way, it doesn't effect the network topology or any other details described here. The important point is that a "Core server" at the least contains the LinuxMCE core services, and this is the functionality that needs to be the gateway between the Internal network and the External network.<br />
<br />
=Fully Configured Smart Home Solution=<br />
<br />
[[Image:Complete.PNG]]<br />
<br />
In the above diagram you can see the same LinuxMCE enabled network after it has matured - the owner has gone nuts, adding stuff! You may only wish to use LinuxMCE for media playback, in which case you will be more interested in the "MD"s in the diagram. However, you can continue expanding it at will into its designed functionality by added telephones, security systems, home automation networks (lights, environmental controls, irrigation systems, etc)<br />
<br />
It should be understood that this article is attempting to show that in the simplest implementation, LinuxMCE does not require large, wholesale changes to your existing home network - in fact, in many cases it requires no change at all, just an extra Cat5e/6 patch cable. This does not mean that this is the only, recommended or best network design. It is a minimal implementation that satisfies all of the requirements, and is here to show how simple LMCE can actually be. There are many other designs that are extensions of this one, or completely different that also work and may be chosen based on more sophisticated requirements you may have, but this is a starting point.</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=AVWizard_Step_by_Step&diff=17853AVWizard Step by Step2009-03-02T20:49:20Z<p>Colinjones: /* Resolution Settings */</p>
<hr />
<div>[[category: AV Wizard]]<br />
[[Category:Tutorials]]<br />
{| align="right"<br />
| __TOC__<br />
|}<br />
AV Wizard can be accessed by pressing the Shift key when the Kubuntu with LMCE boots up. In the process of booting, at a time, you'll hear a series of beeps. You must be prepared before these beeps to press the Shift key. When you'll hear them, press Shift key and keep it pressed. Then you'll enter in AV Wizard. If instead of AV Wizard you see black screen or "no signal" message on display, try to switch the connector type as it is described in section '''II'''.<br />
<br />
==Section I==<br />
<br />
===Resolution Settings===<br />
Here, you can choose the desired output from your video card to TV or monitor. If you’ll choose '''VGA''', there are many available resolutions and refresh rates. If the optimum resolution for your display is not listed, please see [[Custom Display Resolutions]].<br />
====VGA====<br />
[[Image:Avw1.jpg|thumb|500px|left|Resolution Settings]]<br />
<br style="clear:both;"/><br />
====DVI/HDMI====<br />
[[Image:Avw2.jpg|thumb|500px|left|DVI/HDMI Resolutions]]<br />
[[Image:300px-DVI Connector.jpg|thumb|200px|left|'''DVI/HDMI''' means that you can use a special cable from the <br />
DVI/HDMI output of your video card to DVI/HDMI input of LCD TV/monitor. ]]<br />
<br style="clear:both;"/><br />
You have the same range of resolutions like at VGA. Choose one that is suitable for your display device.<br />
====Component====<br />
[[Image:Avw3.jpg|thumb|500px|left|Component Resolution Options]]<br />
[[Image:180px-Component video RCA.jpg|thumb|200px|left|'''''Component''''' uses another special cable which is consisting at every extremity of three jacks (red, blue and green). The display and the video card must have these three jacks. ]]<br />
<br style="clear:both;"/><br />
<br />
The resolutions for component are made for using with wide screen monitors and TV’s. Choose the one that is best suited to your display device. <br />
====Composite====<br />
[[Image:Avw4.jpg|thumb|500px|left|Composite Resolution Options]]<br />
[[Image:300px-Composite.jpg|thumb|200px|left|'''''Composite''''' is something like a TV out from your video card to the monitor/LCD TV. It uses another special cable with a yellow jack. Like at component, the video card and the display must have this kind of input connector.]] <br />
<br />
<br style="clear:both;"/><br />
If you are choosing Composite, you can also choose one TV standard from the list, supported by your display.<br />
<br />
====S-Video====<br />
[[Image:Avw5.jpg|thumb|500px|left|S-Video Resolution Options]]<br />
[[Image:300px-SVideoConnector.jpg|thumb|200px|left|'''''S-Video''''' is another way to send the signal from the video card to monitor/TV. The jack for the cable looks like in the image below.]]<br />
<br />
<br />
<br style="clear:both;"/><br />
As you can see in the picture above, you will choose one of the TV standards in the list.<br />
<br />
===Confirmation of Resolution===<br />
After choosing a resolution, a counter will appear on your screen which will stay 15 seconds. In this time, you can decide if the resolution is good for your monitor or not. If you like it, press Continue. If not, press Back.<br />
<br />
[[Image:Avw6.jpg|thumb|500px|left|Confirmation of Resolution]]<br />
<br style="clear:both;"/><br />
===Select Graphical User Interface===<br />
The next step of the A/V wizard refers to the graphical aspect of user experience. Here, you have three options:<br />
::Please look a [[Selecting the Right UI]] for more information regarding the best option to choose.<br />
• Static images, no overlay (lightweight) – It uses only static images and works on nearly all graphics platforms.<br />
<br />
• OpenGL with overlay (medium)<br />
<br />
• OpenGL with alpha blending (high-end) - '''Requires very specific Graphics Cards'''<br />
::In this case your media is always first and foremost, and the media is always full-screen. If you're not watching any media, Pluto downloads the 'most interesting' photos from flickr.com and presents smooth sliding, cross-fading gallery art as your media. <br />
<br />
[[Image:Avw8.jpg|thumb|500px|left|Selection of Graphical User Interface]]<br />
<br style="clear:both;"/><br />
===Adjust Image Size===<br />
The wizard will guide you to the adjustment of the image size. If your TV doesn't overscan, meaning crop off the edges, you will see all 4 yellow arrows completely on this step. If your TV does overscan, be sure to hit the - key to reduce the image until all 4 arrows are fully visible. Use the arrow keys to shift the image. The goal is that all 4 arrows are centered and as close to the edges of your screen as possible, but without being cropped off. Once you made the correct setup press OK and go the next screen.<br />
<br />
This is where LinuxMCE will display the user interface. Your movies and media themselves are always full-screen and are not effected by this.<br />
<br />
[[Image:Avw9.jpg|thumb|500px|left|Adjust Image Size]]<br />
<br style="clear:both;"/><br />
<br />
===Audio Output Connector===<br />
Next set up the audio system. Again, you have to look at the sound card to see where is connected the cable which goes to the sound system. If you connected the cable to the correct output you have only to click the choice on the screen. If you will hear a melody, then everything is ok, you made the correct setup.<br />
<br />
[[Image:Avw10.jpg|thumb|500px|left|Audio Output Connector]]<br />
<br />
<br />
[[Image:Avw11.jpg|thumb|500px|left|Volume Adjustment]]<br />
<br style="clear:both;"/><br />
===Dolby Audio Test===<br />
If your audio has Dolby, then you will have an additional screen, if not then you will bypass these two screen.<br />
[[Image:AVWizardStep7.jpg|thumb|500px|left|Dolby Audio Test]]<br />
<br style="clear:both;"/><br />
===DTS Audio Test===<br />
If your audio has Digital Theater Sound(DTS) then you will have an additional screen, if not then you will bypass this screen.<br />
[[Image:AVWizardStep8.jpg|thumb|500px|left|Dolby Audio Test]]<br />
<br style="clear:both;"/><br />
<br />
===Final Confirmation===<br />
The final screen of the AV Wizard will show you the settings that you’ve chosen for the LinuxMCE system. If you agree with these setting press ''I agree'', if not, press ''I do not agree'' and you’ll be able to make the settings again.<br />
<br />
<br />
[[Image:Avw12.jpg|thumb|500px|left|Final Confirmation]]<br />
<br style="clear:both;"/><br />
<br />
==Section II==<br />
<br />
To choose the resolutions and the connector during the wizard there are keyboard key shortcuts - these are only to get a display during the wizard so that you can see what you are doing. You still need to choose the correct ultimate resolution and output using the wizard for when you are actually using LMCE. By default, the AV Wizard has the resolution 640x480 on VGA. To choose the connector you have to press the keys from 1 to 5 (1=DVI, 2=VGA, 3=Component, 4=Composite, 5=S-Video). To choose a resolution you have to press the keys from 6 to 0 (6=640x480, 7=1024x768, 8=720p, 9=1080i, 0=1080p). For choosing the resolution and connector you have to be in the initial screen of AV Wizard.<br />
<br />
<br />
[[Image:Avw13.jpg|thumb|500px|left|Welcome]]<br />
<br style="clear:both;"/><br />
<br />
When you are in this screen press the key the desired connector. The screen will flicker and will return to this initial screen. Then, press the key for the desired resolution. Again, the screen will flicker and will return to the initial screen, using the resolution that you chose. After you made the setup, you can continue with the next settings. Note - the "flickering" whilst LMCE changes output or resolution can take upto 15 seconds to complete, so if you have no display, make sure you wait at least this long to settle down before continuing to the next keyboard shortcut.<br />
<br />
==Troubleshooting==<br />
===Driver Issues=== <br />
*''1080i and 1080p are not fully supported because of some factory issues of NVidia drivers''.<br />
===The AVWizard does not start===<br />
*I hear the beeps but I only have a black screen.<br />
::Please refer to Section II above as it will tell you how to start the AVWizard with a connection other than VGA.<br />
::Also confirm whether you have more than one graphics chipset - this will be the case, for instance, if you have added a graphics card to a motherboard that has integrated graphics included with it. In this case you may need to edit your /etc/X11/xorg.conf file manually. You can do this by hitting ESC during the GRUB boot menu. Choose the Recovery Console. Then from the command line type "lspci" and note the PCI Bus ID of the card you wish to use. Now use a text editor like (sudo) nano or (sudo) joe to edit the xorg.conf file - find the Bus ID option in the Device section and correct this to be the Bus ID you noted above. Save and reboot.</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=AVWizard_Step_by_Step&diff=17852AVWizard Step by Step2009-03-02T20:48:40Z<p>Colinjones: /* Section II */</p>
<hr />
<div>[[category: AV Wizard]]<br />
[[Category:Tutorials]]<br />
{| align="right"<br />
| __TOC__<br />
|}<br />
AV Wizard can be accessed by pressing the Shift key when the Kubuntu with LMCE boots up. In the process of booting, at a time, you'll hear a series of beeps. You must be prepared before these beeps to press the Shift key. When you'll hear them, press Shift key and keep it pressed. Then you'll enter in AV Wizard. If instead of AV Wizard you see black screen or "no signal" message on display, try to switch the connector type as it is described in section '''II'''.<br />
<br />
==Section I==<br />
<br />
===Resolution Settings===<br />
Here, you can choose the desired output from your video card to TV or monitor. If you’ll choose '''VGA''', there are many available resolutions and refresh rates. If you have a LCD TV or LCD monitor there is no need to choose a refresh rate. This is helpful only if you have a CRT monitor. If the optimum resolution for your display is not listed, please see [[Custom Display Resolutions]].<br />
====VGA====<br />
[[Image:Avw1.jpg|thumb|500px|left|Resolution Settings]]<br />
<br style="clear:both;"/><br />
====DVI/HDMI====<br />
[[Image:Avw2.jpg|thumb|500px|left|DVI/HDMI Resolutions]]<br />
[[Image:300px-DVI Connector.jpg|thumb|200px|left|'''DVI/HDMI''' means that you can use a special cable from the <br />
DVI/HDMI output of your video card to DVI/HDMI input of LCD TV/monitor. ]]<br />
<br style="clear:both;"/><br />
You have the same range of resolutions like at VGA. Choose one that is suitable for your display device.<br />
====Component====<br />
[[Image:Avw3.jpg|thumb|500px|left|Component Resolution Options]]<br />
[[Image:180px-Component video RCA.jpg|thumb|200px|left|'''''Component''''' uses another special cable which is consisting at every extremity of three jacks (red, blue and green). The display and the video card must have these three jacks. ]]<br />
<br style="clear:both;"/><br />
<br />
The resolutions for component are made for using with wide screen monitors and TV’s. Choose the one that is best suited to your display device. <br />
====Composite====<br />
[[Image:Avw4.jpg|thumb|500px|left|Composite Resolution Options]]<br />
[[Image:300px-Composite.jpg|thumb|200px|left|'''''Composite''''' is something like a TV out from your video card to the monitor/LCD TV. It uses another special cable with a yellow jack. Like at component, the video card and the display must have this kind of input connector.]] <br />
<br />
<br style="clear:both;"/><br />
If you are choosing Composite, you can also choose one TV standard from the list, supported by your display.<br />
<br />
====S-Video====<br />
[[Image:Avw5.jpg|thumb|500px|left|S-Video Resolution Options]]<br />
[[Image:300px-SVideoConnector.jpg|thumb|200px|left|'''''S-Video''''' is another way to send the signal from the video card to monitor/TV. The jack for the cable looks like in the image below.]]<br />
<br />
<br />
<br style="clear:both;"/><br />
As you can see in the picture above, you will choose one of the TV standards in the list.<br />
<br />
===Confirmation of Resolution===<br />
After choosing a resolution, a counter will appear on your screen which will stay 15 seconds. In this time, you can decide if the resolution is good for your monitor or not. If you like it, press Continue. If not, press Back.<br />
<br />
[[Image:Avw6.jpg|thumb|500px|left|Confirmation of Resolution]]<br />
<br style="clear:both;"/><br />
===Select Graphical User Interface===<br />
The next step of the A/V wizard refers to the graphical aspect of user experience. Here, you have three options:<br />
::Please look a [[Selecting the Right UI]] for more information regarding the best option to choose.<br />
• Static images, no overlay (lightweight) – It uses only static images and works on nearly all graphics platforms.<br />
<br />
• OpenGL with overlay (medium)<br />
<br />
• OpenGL with alpha blending (high-end) - '''Requires very specific Graphics Cards'''<br />
::In this case your media is always first and foremost, and the media is always full-screen. If you're not watching any media, Pluto downloads the 'most interesting' photos from flickr.com and presents smooth sliding, cross-fading gallery art as your media. <br />
<br />
[[Image:Avw8.jpg|thumb|500px|left|Selection of Graphical User Interface]]<br />
<br style="clear:both;"/><br />
===Adjust Image Size===<br />
The wizard will guide you to the adjustment of the image size. If your TV doesn't overscan, meaning crop off the edges, you will see all 4 yellow arrows completely on this step. If your TV does overscan, be sure to hit the - key to reduce the image until all 4 arrows are fully visible. Use the arrow keys to shift the image. The goal is that all 4 arrows are centered and as close to the edges of your screen as possible, but without being cropped off. Once you made the correct setup press OK and go the next screen.<br />
<br />
This is where LinuxMCE will display the user interface. Your movies and media themselves are always full-screen and are not effected by this.<br />
<br />
[[Image:Avw9.jpg|thumb|500px|left|Adjust Image Size]]<br />
<br style="clear:both;"/><br />
<br />
===Audio Output Connector===<br />
Next set up the audio system. Again, you have to look at the sound card to see where is connected the cable which goes to the sound system. If you connected the cable to the correct output you have only to click the choice on the screen. If you will hear a melody, then everything is ok, you made the correct setup.<br />
<br />
[[Image:Avw10.jpg|thumb|500px|left|Audio Output Connector]]<br />
<br />
<br />
[[Image:Avw11.jpg|thumb|500px|left|Volume Adjustment]]<br />
<br style="clear:both;"/><br />
===Dolby Audio Test===<br />
If your audio has Dolby, then you will have an additional screen, if not then you will bypass these two screen.<br />
[[Image:AVWizardStep7.jpg|thumb|500px|left|Dolby Audio Test]]<br />
<br style="clear:both;"/><br />
===DTS Audio Test===<br />
If your audio has Digital Theater Sound(DTS) then you will have an additional screen, if not then you will bypass this screen.<br />
[[Image:AVWizardStep8.jpg|thumb|500px|left|Dolby Audio Test]]<br />
<br style="clear:both;"/><br />
<br />
===Final Confirmation===<br />
The final screen of the AV Wizard will show you the settings that you’ve chosen for the LinuxMCE system. If you agree with these setting press ''I agree'', if not, press ''I do not agree'' and you’ll be able to make the settings again.<br />
<br />
<br />
[[Image:Avw12.jpg|thumb|500px|left|Final Confirmation]]<br />
<br style="clear:both;"/><br />
<br />
==Section II==<br />
<br />
To choose the resolutions and the connector during the wizard there are keyboard key shortcuts - these are only to get a display during the wizard so that you can see what you are doing. You still need to choose the correct ultimate resolution and output using the wizard for when you are actually using LMCE. By default, the AV Wizard has the resolution 640x480 on VGA. To choose the connector you have to press the keys from 1 to 5 (1=DVI, 2=VGA, 3=Component, 4=Composite, 5=S-Video). To choose a resolution you have to press the keys from 6 to 0 (6=640x480, 7=1024x768, 8=720p, 9=1080i, 0=1080p). For choosing the resolution and connector you have to be in the initial screen of AV Wizard.<br />
<br />
<br />
[[Image:Avw13.jpg|thumb|500px|left|Welcome]]<br />
<br style="clear:both;"/><br />
<br />
When you are in this screen press the key the desired connector. The screen will flicker and will return to this initial screen. Then, press the key for the desired resolution. Again, the screen will flicker and will return to the initial screen, using the resolution that you chose. After you made the setup, you can continue with the next settings. Note - the "flickering" whilst LMCE changes output or resolution can take upto 15 seconds to complete, so if you have no display, make sure you wait at least this long to settle down before continuing to the next keyboard shortcut.<br />
<br />
==Troubleshooting==<br />
===Driver Issues=== <br />
*''1080i and 1080p are not fully supported because of some factory issues of NVidia drivers''.<br />
===The AVWizard does not start===<br />
*I hear the beeps but I only have a black screen.<br />
::Please refer to Section II above as it will tell you how to start the AVWizard with a connection other than VGA.<br />
::Also confirm whether you have more than one graphics chipset - this will be the case, for instance, if you have added a graphics card to a motherboard that has integrated graphics included with it. In this case you may need to edit your /etc/X11/xorg.conf file manually. You can do this by hitting ESC during the GRUB boot menu. Choose the Recovery Console. Then from the command line type "lspci" and note the PCI Bus ID of the card you wish to use. Now use a text editor like (sudo) nano or (sudo) joe to edit the xorg.conf file - find the Bus ID option in the Device section and correct this to be the Bus ID you noted above. Save and reboot.</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=AVWizard_Step_by_Step&diff=17851AVWizard Step by Step2009-03-02T20:44:42Z<p>Colinjones: /* The AVWizard does not start */ added details for "black screen" with multiple GPUs</p>
<hr />
<div>[[category: AV Wizard]]<br />
[[Category:Tutorials]]<br />
{| align="right"<br />
| __TOC__<br />
|}<br />
AV Wizard can be accessed by pressing the Shift key when the Kubuntu with LMCE boots up. In the process of booting, at a time, you'll hear a series of beeps. You must be prepared before these beeps to press the Shift key. When you'll hear them, press Shift key and keep it pressed. Then you'll enter in AV Wizard. If instead of AV Wizard you see black screen or "no signal" message on display, try to switch the connector type as it is described in section '''II'''.<br />
<br />
==Section I==<br />
<br />
===Resolution Settings===<br />
Here, you can choose the desired output from your video card to TV or monitor. If you’ll choose '''VGA''', there are many available resolutions and refresh rates. If you have a LCD TV or LCD monitor there is no need to choose a refresh rate. This is helpful only if you have a CRT monitor. If the optimum resolution for your display is not listed, please see [[Custom Display Resolutions]].<br />
====VGA====<br />
[[Image:Avw1.jpg|thumb|500px|left|Resolution Settings]]<br />
<br style="clear:both;"/><br />
====DVI/HDMI====<br />
[[Image:Avw2.jpg|thumb|500px|left|DVI/HDMI Resolutions]]<br />
[[Image:300px-DVI Connector.jpg|thumb|200px|left|'''DVI/HDMI''' means that you can use a special cable from the <br />
DVI/HDMI output of your video card to DVI/HDMI input of LCD TV/monitor. ]]<br />
<br style="clear:both;"/><br />
You have the same range of resolutions like at VGA. Choose one that is suitable for your display device.<br />
====Component====<br />
[[Image:Avw3.jpg|thumb|500px|left|Component Resolution Options]]<br />
[[Image:180px-Component video RCA.jpg|thumb|200px|left|'''''Component''''' uses another special cable which is consisting at every extremity of three jacks (red, blue and green). The display and the video card must have these three jacks. ]]<br />
<br style="clear:both;"/><br />
<br />
The resolutions for component are made for using with wide screen monitors and TV’s. Choose the one that is best suited to your display device. <br />
====Composite====<br />
[[Image:Avw4.jpg|thumb|500px|left|Composite Resolution Options]]<br />
[[Image:300px-Composite.jpg|thumb|200px|left|'''''Composite''''' is something like a TV out from your video card to the monitor/LCD TV. It uses another special cable with a yellow jack. Like at component, the video card and the display must have this kind of input connector.]] <br />
<br />
<br style="clear:both;"/><br />
If you are choosing Composite, you can also choose one TV standard from the list, supported by your display.<br />
<br />
====S-Video====<br />
[[Image:Avw5.jpg|thumb|500px|left|S-Video Resolution Options]]<br />
[[Image:300px-SVideoConnector.jpg|thumb|200px|left|'''''S-Video''''' is another way to send the signal from the video card to monitor/TV. The jack for the cable looks like in the image below.]]<br />
<br />
<br />
<br style="clear:both;"/><br />
As you can see in the picture above, you will choose one of the TV standards in the list.<br />
<br />
===Confirmation of Resolution===<br />
After choosing a resolution, a counter will appear on your screen which will stay 15 seconds. In this time, you can decide if the resolution is good for your monitor or not. If you like it, press Continue. If not, press Back.<br />
<br />
[[Image:Avw6.jpg|thumb|500px|left|Confirmation of Resolution]]<br />
<br style="clear:both;"/><br />
===Select Graphical User Interface===<br />
The next step of the A/V wizard refers to the graphical aspect of user experience. Here, you have three options:<br />
::Please look a [[Selecting the Right UI]] for more information regarding the best option to choose.<br />
• Static images, no overlay (lightweight) – It uses only static images and works on nearly all graphics platforms.<br />
<br />
• OpenGL with overlay (medium)<br />
<br />
• OpenGL with alpha blending (high-end) - '''Requires very specific Graphics Cards'''<br />
::In this case your media is always first and foremost, and the media is always full-screen. If you're not watching any media, Pluto downloads the 'most interesting' photos from flickr.com and presents smooth sliding, cross-fading gallery art as your media. <br />
<br />
[[Image:Avw8.jpg|thumb|500px|left|Selection of Graphical User Interface]]<br />
<br style="clear:both;"/><br />
===Adjust Image Size===<br />
The wizard will guide you to the adjustment of the image size. If your TV doesn't overscan, meaning crop off the edges, you will see all 4 yellow arrows completely on this step. If your TV does overscan, be sure to hit the - key to reduce the image until all 4 arrows are fully visible. Use the arrow keys to shift the image. The goal is that all 4 arrows are centered and as close to the edges of your screen as possible, but without being cropped off. Once you made the correct setup press OK and go the next screen.<br />
<br />
This is where LinuxMCE will display the user interface. Your movies and media themselves are always full-screen and are not effected by this.<br />
<br />
[[Image:Avw9.jpg|thumb|500px|left|Adjust Image Size]]<br />
<br style="clear:both;"/><br />
<br />
===Audio Output Connector===<br />
Next set up the audio system. Again, you have to look at the sound card to see where is connected the cable which goes to the sound system. If you connected the cable to the correct output you have only to click the choice on the screen. If you will hear a melody, then everything is ok, you made the correct setup.<br />
<br />
[[Image:Avw10.jpg|thumb|500px|left|Audio Output Connector]]<br />
<br />
<br />
[[Image:Avw11.jpg|thumb|500px|left|Volume Adjustment]]<br />
<br style="clear:both;"/><br />
===Dolby Audio Test===<br />
If your audio has Dolby, then you will have an additional screen, if not then you will bypass these two screen.<br />
[[Image:AVWizardStep7.jpg|thumb|500px|left|Dolby Audio Test]]<br />
<br style="clear:both;"/><br />
===DTS Audio Test===<br />
If your audio has Digital Theater Sound(DTS) then you will have an additional screen, if not then you will bypass this screen.<br />
[[Image:AVWizardStep8.jpg|thumb|500px|left|Dolby Audio Test]]<br />
<br style="clear:both;"/><br />
<br />
===Final Confirmation===<br />
The final screen of the AV Wizard will show you the settings that you’ve chosen for the LinuxMCE system. If you agree with these setting press ''I agree'', if not, press ''I do not agree'' and you’ll be able to make the settings again.<br />
<br />
<br />
[[Image:Avw12.jpg|thumb|500px|left|Final Confirmation]]<br />
<br style="clear:both;"/><br />
<br />
==Section II==<br />
<br />
Another method to choose the resolutions and the connector is by pressing some keyboard keys. By default, the AV Wizard has the resolution 640x480 on VGA. To choose the connector you have to press the keys from 1 to 5 (1=DVI, 2=VGA, 3=Component, 4=Composite, 5=S-Video). To choose a resolution you have to press the keys from 6 to 0 (6=640x480, 7=1024x768, 8=720p, 9=1080i, 0=1080p). For choosing the resolution and connector you have to be in the initial screen of AV Wizard.<br />
<br />
<br />
[[Image:Avw13.jpg|thumb|500px|left|Welcome]]<br />
<br style="clear:both;"/><br />
<br />
When you are in this screen press the key the desired connector. The screen will flicker and will return to this initial screen. Then, press the key for the desired resolution. Again, the screen will flicker and will return to the initial screen, using the resolution that you chose. After you made the setup, you can continue with the next settings. <br />
<br />
==Troubleshooting==<br />
===Driver Issues=== <br />
*''1080i and 1080p are not fully supported because of some factory issues of NVidia drivers''.<br />
===The AVWizard does not start===<br />
*I hear the beeps but I only have a black screen.<br />
::Please refer to Section II above as it will tell you how to start the AVWizard with a connection other than VGA.<br />
::Also confirm whether you have more than one graphics chipset - this will be the case, for instance, if you have added a graphics card to a motherboard that has integrated graphics included with it. In this case you may need to edit your /etc/X11/xorg.conf file manually. You can do this by hitting ESC during the GRUB boot menu. Choose the Recovery Console. Then from the command line type "lspci" and note the PCI Bus ID of the card you wish to use. Now use a text editor like (sudo) nano or (sudo) joe to edit the xorg.conf file - find the Bus ID option in the Device section and correct this to be the Bus ID you noted above. Save and reboot.</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Talk:AVWizard_Step_by_Step&diff=17850Talk:AVWizard Step by Step2009-03-02T20:35:50Z<p>Colinjones: New page: Actually, refresh rate is very relevant to LCD screens (all screens in fact) so this part of the article is misleading....</p>
<hr />
<div>Actually, refresh rate is very relevant to LCD screens (all screens in fact) so this part of the article is misleading....</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Network_Setup&diff=17779Network Setup2009-02-25T22:03:02Z<p>Colinjones: /* Fully Configured Smart Home Solution */</p>
<hr />
<div>[[Category:Hardware]]<br />
[[Category:Networking]]<br />
[[Category:Tutorials]]<br />
<br />
=Overview=<br />
<br />
There is regularly some confusion over how much of your existing home network LinuxMCE requires you to change. Many people incorrectly believe that significant changes are required. In the most common case of home networks, almost no change at all is required. The Core server requires 2 NICs (Network Interface Cards). One is known as the "External" NIC and the other as the "Internal" NIC.<br />
<br />
=Existing Home Network=<br />
<br />
[[Image:Before.PNG]]<br />
<br />
Above we see a very simple home network setup. All devices are connected to a switch, which in turn is connected to the LAN port of a broadband router. In this topology, most people have their broadband router provide dynamic IP addresses to all other devices via DHCP.<br />
<br />
<br />
<br />
=Network After LinuxMCE is Installed=<br />
<br />
[[Image:After.PNG]]<br />
<br />
Above we see the same network, now LinuxMCE enabled. NOTE: The ''only'' change is the Core LinuxMCE server has been inserted between the switch and the broadband router. In practice, this means disconnecting the Cat5e/6 patch cable, shown in the first diagram, from the broadband router and connecting it into the "Internal" NIC of the of the Core server (shown here on the right of the red box). Next, get a new Cat5e/6 patch cable and connect one end to the "External" NIC of the Core server (shown here on the left of the red box), and the other end back into the LAN port of the broadband router. Your setup is now complete!<br />
<br />
In this network, your broadband router can continue providing dynamic IP addresses to the "External" NIC of the core - however, there is nothing stopping you fixing this IP address if you prefer. In which case your broadband router's DHCP server is no longer needed. For the Internal or LinuxMCE network, the Core now provides DHCP services to all devices. IMPORTANT: LinuxMCE needs to be the (only) DHCP server for the Internal network because it provides much more than just IP addresses to these devices. So it is important that you allow it to do this, and leave all your internal devices set to acquire their IP address via DHCP so that LinuxMCE works correctly. This is the only supported configuration - however, as you can see, the impact is either negligible or non-existent.<br />
<br />
In this page, a reference to the "Core server" can either be a dedicated Core or a Hybrid - a core, plus Media Director functionality - either way, it doesn't effect the network topology or any other details described here. The important point is that a "Core server" at the least contains the LinuxMCE core services, and this is the functionality that needs to be the gateway between the Internal network and the External network.<br />
<br />
=Fully Configured Smart Home Solution=<br />
<br />
[[Image:Complete.PNG]]<br />
<br />
In the above diagram you can see the same LinuxMCE enabled network after it has matured - the owner has gone nuts, adding stuff! You may only wish to use LinuxMCE for media playback, in which case you will be more interested in the "MD"s in the diagram. However, you can continue expanding it at will into its designed functionality by added telephones, security systems, home automation networks (lights, environmental controls, irrigation systems, etc)<br />
<br />
It should be understood that this article is attempting to show that in the simplest implementation, LinuxMCE does not require large, wholesale changes to your existing home network - in fact, in many cases it requires no change at all, just an extra Cat5e/6 patch cable. This does not mean that this is the only, recommended or best network design. It is a minimal implementation that satisfies all of the requirements, and is here to show how simple LMCE can actually be. There are many other designs that are extensions of this one, or completely different that also work and may be chosen based on more sophisticated requirements you may have, but this is a starting point.</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Network_Setup&diff=17775Network Setup2009-02-25T06:56:20Z<p>Colinjones: /* Network After LinuxMCE is Installed */</p>
<hr />
<div>[[Category:Hardware]]<br />
[[Category:Networking]]<br />
[[Category:Tutorials]]<br />
<br />
=Overview=<br />
<br />
There is regularly some confusion over how much of your existing home network LinuxMCE requires you to change. Many people incorrectly believe that significant changes are required. In the most common case of home networks, almost no change at all is required. The Core server requires 2 NICs (Network Interface Cards). One is known as the "External" NIC and the other as the "Internal" NIC.<br />
<br />
=Existing Home Network=<br />
<br />
[[Image:Before.PNG]]<br />
<br />
Above we see a very simple home network setup. All devices are connected to a switch, which in turn is connected to the LAN port of a broadband router. In this topology, most people have their broadband router provide dynamic IP addresses to all other devices via DHCP.<br />
<br />
<br />
<br />
=Network After LinuxMCE is Installed=<br />
<br />
[[Image:After.PNG]]<br />
<br />
Above we see the same network, now LinuxMCE enabled. NOTE: The ''only'' change is the Core LinuxMCE server has been inserted between the switch and the broadband router. In practice, this means disconnecting the Cat5e/6 patch cable, shown in the first diagram, from the broadband router and connecting it into the "Internal" NIC of the of the Core server (shown here on the right of the red box). Next, get a new Cat5e/6 patch cable and connect one end to the "External" NIC of the Core server (shown here on the left of the red box), and the other end back into the LAN port of the broadband router. Your setup is now complete!<br />
<br />
In this network, your broadband router can continue providing dynamic IP addresses to the "External" NIC of the core - however, there is nothing stopping you fixing this IP address if you prefer. In which case your broadband router's DHCP server is no longer needed. For the Internal or LinuxMCE network, the Core now provides DHCP services to all devices. IMPORTANT: LinuxMCE needs to be the (only) DHCP server for the Internal network because it provides much more than just IP addresses to these devices. So it is important that you allow it to do this, and leave all your internal devices set to acquire their IP address via DHCP so that LinuxMCE works correctly. This is the only supported configuration - however, as you can see, the impact is either negligible or non-existent.<br />
<br />
In this page, a reference to the "Core server" can either be a dedicated Core or a Hybrid - a core, plus Media Director functionality - either way, it doesn't effect the network topology or any other details described here. The important point is that a "Core server" at the least contains the LinuxMCE core services, and this is the functionality that needs to be the gateway between the Internal network and the External network.<br />
<br />
=Fully Configured Smart Home Solution=<br />
<br />
[[Image:Complete.PNG]]<br />
<br />
In the above diagram you can see the same LinuxMCE enabled network after it has matured - the owner has gone nuts, adding stuff! You may only wish to use LinuxMCE for media playback, in which case you will be more interested in the "MD"s in the diagram. However, you can continue expanding it at will into its designed functionality by added telephones, security systems, home automation networks (lights, environmental controls, irrigation systems, etc)</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Network_Setup&diff=17774Network Setup2009-02-25T04:43:32Z<p>Colinjones: </p>
<hr />
<div>[[Category:Hardware]]<br />
[[Category:Networking]]<br />
[[Category:Tutorials]]<br />
<br />
=Overview=<br />
<br />
There is regularly some confusion over how much of your existing home network LinuxMCE requires you to change. Many people incorrectly believe that significant changes are required. In the most common case of home networks, almost no change at all is required. The Core server requires 2 NICs (Network Interface Cards). One is known as the "External" NIC and the other as the "Internal" NIC.<br />
<br />
=Existing Home Network=<br />
<br />
[[Image:Before.PNG]]<br />
<br />
Above we see a very simple home network setup. All devices are connected to a switch, which in turn is connected to the LAN port of a broadband router. In this topology, most people have their broadband router provide dynamic IP addresses to all other devices via DHCP.<br />
<br />
<br />
<br />
=Network After LinuxMCE is Installed=<br />
<br />
[[Image:After.PNG]]<br />
<br />
Above we see the same network, now LinuxMCE enabled. NOTE: The ''only'' change is the Core LinuxMCE server has been inserted between the switch and the broadband router. In practice, this means disconnecting the Cat5e/6 patch cable, shown in the first diagram, from the broadband router and connecting it into the "Internal" NIC of the of the Core server (shown here on the right of the red box). Next, get a new Cat5e/6 patch cable and connect one end to the "External" NIC of the Core server (shown here on the left of the red box), and the other end back into the LAN port of the broadband router. Your setup is now complete!<br />
<br />
In this network, your broadband router can continue providing dynamic IP addresses to the "External" NIC of the core - however, there is nothing stopping you fixing this IP address if you prefer. In which case your broadband router's DHCP server is no longer needed. For the Internal or LinuxMCE network, the Core now provides DHCP services to all devices. IMPORTANT: LinuxMCE needs to be the (only) DHCP server for the Internal network because it provides much more than just IP addresses to these devices. So it is important that you allow it to do this, and leave all your internal devices set to acquire their IP address via DHCP so that LinuxMCE works correctly. This is the only supported configuration - however, as you can see, the impact is either negligible or non-existent.<br />
<br />
<br />
=Fully Configured Smart Home Solution=<br />
<br />
[[Image:Complete.PNG]]<br />
<br />
In the above diagram you can see the same LinuxMCE enabled network after it has matured - the owner has gone nuts, adding stuff! You may only wish to use LinuxMCE for media playback, in which case you will be more interested in the "MD"s in the diagram. However, you can continue expanding it at will into its designed functionality by added telephones, security systems, home automation networks (lights, environmental controls, irrigation systems, etc)</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Network_Setup&diff=17773Network Setup2009-02-25T04:42:38Z<p>Colinjones: </p>
<hr />
<div>[[Category:Hardware]]<br />
[[Category:Networking]]<br />
<br />
=Overview=<br />
<br />
There is regularly some confusion over how much of your existing home network LinuxMCE requires you to change. Many people incorrectly believe that significant changes are required. In the most common case of home networks, almost no change at all is required. The Core server requires 2 NICs (Network Interface Cards). One is known as the "External" NIC and the other as the "Internal" NIC.<br />
<br />
=Existing Home Network=<br />
<br />
[[Image:Before.PNG]]<br />
<br />
Above we see a very simple home network setup. All devices are connected to a switch, which in turn is connected to the LAN port of a broadband router. In this topology, most people have their broadband router provide dynamic IP addresses to all other devices via DHCP.<br />
<br />
<br />
<br />
=Network After LinuxMCE is Installed=<br />
<br />
[[Image:After.PNG]]<br />
<br />
Above we see the same network, now LinuxMCE enabled. NOTE: The ''only'' change is the Core LinuxMCE server has been inserted between the switch and the broadband router. In practice, this means disconnecting the Cat5e/6 patch cable, shown in the first diagram, from the broadband router and connecting it into the "Internal" NIC of the of the Core server (shown here on the right of the red box). Next, get a new Cat5e/6 patch cable and connect one end to the "External" NIC of the Core server (shown here on the left of the red box), and the other end back into the LAN port of the broadband router. Your setup is now complete!<br />
<br />
In this network, your broadband router can continue providing dynamic IP addresses to the "External" NIC of the core - however, there is nothing stopping you fixing this IP address if you prefer. In which case your broadband router's DHCP server is no longer needed. For the Internal or LinuxMCE network, the Core now provides DHCP services to all devices. IMPORTANT: LinuxMCE needs to be the (only) DHCP server for the Internal network because it provides much more than just IP addresses to these devices. So it is important that you allow it to do this, and leave all your internal devices set to acquire their IP address via DHCP so that LinuxMCE works correctly. This is the only supported configuration - however, as you can see, the impact is either negligible or non-existent.<br />
<br />
<br />
=Fully Configured Smart Home Solution=<br />
<br />
[[Image:Complete.PNG]]<br />
<br />
In the above diagram you can see the same LinuxMCE enabled network after it has matured - the owner has gone nuts, adding stuff! You may only wish to use LinuxMCE for media playback, in which case you will be more interested in the "MD"s in the diagram. However, you can continue expanding it at will into its designed functionality by added telephones, security systems, home automation networks (lights, environmental controls, irrigation systems, etc)</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Frequently_Asked_Questions&diff=17772Frequently Asked Questions2009-02-25T04:39:47Z<p>Colinjones: /* Why do I need two network cards in my Core? */</p>
<hr />
<div>[[Category:Documentation]]<br />
This '''frequently asked questions''' (FAQ) section outlines solutions to the most common queries for initial/potential users. See also [[troubleshooting]] for solutions to problems experienced with the system.<br />
==Before Installing LinuxMCE==<br />
===What Does LinuxMCE Do For Me?===<br />
'''LinuxMCE is a whole home automation suite. It includes full featured solutions for:'''<br />
*Media<br />
**Organize media with [[Catalog_media_with_attributes|special metadata tags]]<br />
**View/Listen to media in any room<br />
**Media automatically [[Have_my_media_follow_me|follows you]] through your home<br />
**New media is automatically detected - even if it's on other devices like another computer on your network or Network Attached Storage (NAS)<br />
**Control all your A/V gear through LinuxMCE (using [[Control_regular_A/V_equipment|IR]], [[Control_A/V_equipment_with_RS232/USB/Ethernet|USB, Ethernet, or RS-232]]) including automatically powering everything on and setting the proper inputs on each device<br />
*[[Security]]<br />
**Monitor sensors and [[Have_LinuxMCE_notify_me_of_security_alerts|trigger events]]<br />
**[[Monitor_surveillance_cameras|Monitor security cameras]]<br />
*[[LinuxMCE_telecom_features|Telecomunication]]<br />
**Use VoIP phones anywhere in your home with minimal setup<br />
**Voicemail, call forwarding, advanced caller ID<br />
*Network Management<br />
**Take the place of a standard home router<br />
**Advanced [[Firewall_Rules|firewall]]<br />
**Advanced Quality of Service (QoS) to make sure your bandwidth is used effectively (especially important for VoIP)<br />
**Manage networked storage (such as [[Network_Attached_Storage|NAS devices]]<br />
*[[Automation|Home Control and Automation]]<br />
**Control climate and lighting throughout your entire home<br />
<br />
'''LinuxMCE provides all this functionality by controlling [[:Category:Hardware|all kinds of devices]] throughout the home including:'''<br />
*LinuxMCE [[Core]] Computer<br />
*LinuxMCE [[Media_Directors|Media Director]] Computers<br />
*LinuxMCE [[Orbiters|Orbiters]] (Fancy remotes)<br />
**Nokia [[Nokia 770|770]]/[[Nokia N800|N800/N810]]<br />
**Various PDAs (such as IPAQ 5550 and IPAQ hx2410)<br />
**Various Bluetooth capable mobile phones (including Nokia [[Nokia E65|E65]], [[Nokia N70|N70]], [[Nokia N73|N73]], [[Nokia 6620|6620]], [[Nokia 7650|7650]]) <br />
**The [[Web Orbiter]]<br />
**Various [[:Category:Orbiters|other devices]]<br />
*Networked storage (including [[:Category:Network_Attached_Storage|Network Attached Storage]] (NAS) Devices)<br />
*A/V Equipment (TVs, Receivers, Cable Boxes, etc)<br />
**Using [[:Category:Infrared|Infrared]] (IR)<br />
**Using [[Control_A/V_equipment_with_RS232/USB/Ethernet|RS-232]] (Serial)<br />
**Using [[Control_A/V_equipment_with_RS232/USB/Ethernet|Ethernet]] (Network)<br />
**Using [[Control_A/V_equipment_with_RS232/USB/Ethernet|USB]]<br />
*TV [[:Category:TV_Cards|Capture Devices]]<br />
*Lighting [[:Category:Automation|Automation]]<br />
**Using [[X10_LinuxMCE_Configuration|X10]]<br />
**Using [[:Category:ZWave|Z-Wave]]<br />
**Using [[:Category:Insteon|Insteon]]<br />
**Using [[:Category:Automation|various other protocols]]<br />
**See also: [[Automation]]<br />
*HVAC (Climate Control)[[:Category:Automation|Automation]]<br />
*Security [[:Category:Security|Systems or Individual Sensors]]<br />
*Surveillance [[:Category:Cameras|Cameras]] (IP, Firewire, [[:Category:Video_Capture_Boards|video capture board]], etc)<br />
*VoIP [[:Category:Phones|Phones]] and [[VOIP Service Providers|Service Providers]]<br />
<br />
For more, see [[What can I do with LinuxMCE?]]<br />
<br />
===Is LinuxMCE an appliance or software solution?===<br />
Until now there have been two options for a smarthome+media system:<br />
# Low cost '''software''' based PC solutions, including home automation software like [http://www.homeseer.com HomeSeer], [http://www.premisesystems.com Premise] and [http://www.misterhouse.com Mr. House], also media software like [http://www.microsoft.com/windowsxp/mediacenter/default.mspx Microsoft Windows XP Media Center].<br />
# '''Appliance''' solutions, like [http://www.crestron.com Crestron], [http://www.amx.com AMX], [http://www.kaleidescape.com Kaleidescape] and [http://www.escient.com Escient].<br />
<br />
High-end systems are always appliance based, preferred for their simplicity, reliability and lack of hassle; no worry about missing the football game because your PC-based PVR got a virus. But appliance systems cost a lot &mdash; for one that includes automation, media, telephony, etc., like LinuxMCE. Even though those "appliances" are normally PC's inside special cases, often running Linux plus some proprietary software, you can never get the software separately to build your own &mdash; until now.<br />
<br />
LinuxMCE is an appliance solution. The Core becomes a self-configuring, self-maintaining black box appliance. Since the Core automatically offers a network boot image to any PC's you want to use as media directors, they too become appliances. You can still use them as a PC, of course, but you can crash the hard drive, install a virus, delete system files, and it doesn't matter. When you hit 'LinuxMCE' on the remote control, the Core sends it a network boot, the hard drive turns off, it doesn't use your operating system, and you'll never see a PC prompt. And when you hit the PC button, it goes back to being a PC like normal. LinuxMCE is a 'family friendly' solution--you can use the PC for kernel-level coding, knowing the kids can always hit 1 button and still use it to watch cartoons.<br />
<br />
LinuxMCE offers the best of both worlds: an appliance solution at the price of a software solution, and the the power and versatility of a software solution with the ease of use of an appliance. We offer the software for free as open source because our business is licensing LinuxMCE to hardgoods manufacturers who embed it in their products.<br />
<br />
===What do commercial appliance solutions similar to LinuxMCE cost?===<br />
Appliance solutions are normally quite expensive. The most popular combinations are:<br />
# [http://www.crestron.com Crestron] system to do all the home automation. The cost varies depending on what you want to do with it, but a whole-house solution including touch-screen panels will set you back at least $25,000 for an entry-level system, and can easily hit 6 figures.<br />
# [http://www.kaleidescape.com Kaleidescape] for the DVD movie server, costing $27,000 for the main server, and $4,000 for each TV where you want to watch movies.<br />
# [http://www.escient.com Escient] Fireball for the music server, costing $5,000 for the central music server.<br />
# A PBX phone system with voicemail, like [http://www.panasonic.com Panasonic] will cost another 5 grand or so.<br />
<br />
All of those products require professional installation and setup, particularly the home automation devices. LinuxMCE was designed with simple web-based wizard so even non-techies can get a whole solution up within a few hours. But our competitors' products are different. Smart home dealers will require a trained programmer to set them up. For example, it can take weeks of programming to set up a Crestron system in a good-sized house. Programming fees can be over $10,000, plus re-programing fees every time you make a change. '''Bottom line: around $100,000''' for an appliance solution that does what LinuxMCE does.<br />
<br />
Appliance solutions are typically PCs, running an Linux OS with custom, proprietary software, placed inside custom cases. The software is not available separately, so there's no way to economize or build your own.<br />
<br />
LinuxMCE has taken a different approach. LinuxMCE is also an appliance solution, but we have made the software available separately. In fact, it is free, so techies and software programmers can build their own high-end appliance systems. Competing PC hardware manufacturers can license the LinuxMCE platform to use in standard, low-cost PCs. LinuxMCE brings down the cost by offering all the functionality of several systems in 1 system: whole house media & entertainment, home automation, telecom, security, and personal computer.<br />
<br />
===I've heard LinuxMCE is just a bunch of projects merged together. Is that true? What is special about LinuxMCE?===<br />
<p>LinuxMCE includes a lot of other open source projects, like Xine, Asterisk, MythTV, VideoLan, etc. So we are often asked, "Why do I need LinuxMCE, can't I just use those other projects by themselves?"</p><br />
<p>LinuxMCE has a lot of its own software; it's not just a collection of other projects. In fact, LinuxMCE's own software is bigger than most of the key outside projects combined. LinuxMCE includes its own messaging platform. Most of the logic and functionality, such as how to handle home security, media, etc., is in LinuxMCE's plug-in's--not the other projects. Plus LinuxMCE includes a GUI that runs on Linux, Windows, Windows CE and Symbian. There are already thousands of DCE Devices for various smart home components. And LinuxMCE includes lots of development tools, like the GUI Designer, code generators like DCEGen and sql2cpp. There are also some fairly substantial stand-alone projects with LinuxMCE, like sqlCVS. sqlCVS has essentially all the same features as CVS or SVN, but it works with databases--not source code. It is what ensures that when one user translates a screen on the GUI, or learns an infrared code, or creates a new GSD device, that this is committed to a central repository, reviewed by our staff, then propagated to all other users.</p><br />
<p>Additionally LinuxMCE has its own "wrappers" for all the outside open source projects we integrate. This is what allows them to work together seamlessly.</p><br />
<p><b>Example #1: LinuxMCE's wrappers allow open source projects to be interchangeable modules.</b> For example, on one media director un-check the box for the 'Xine' media player, but leave 'VideoLan' checked. Do the opposite for another media director. And for the rest, leave both checked (the default). Now start watching a movie in 1 room. As you move from room to room the movie will seamlessly move from Xine to VideoLan and back. If you leave both checked, Xine will be used when the movie is playing in 1 room only, and VideoLan when it is playing in multiple rooms. This interoperability is not possible outside of LinuxMCE.</p><br />
<p><b>Example #2: LinuxMCE allows a bunch of disparate projects to work together as a seamless whole</b> For example, if there's a security breach in your house, the lights and TV's in the house come on automatically using our home automation DCE device interfaces, and the security pin pad appears on all the Windows webpads and PDA's. After 30 seconds a menacing video plays for the burglar using Xine, while the surveillance cameras monitored by Motion feed a live video to your mobile phone over GPRS. Hit 'Talk' on the phone and Xine suspends, passing control to Linphone which makes a call using Asterisk to your mobile phone with the audio piped through the stereo so you can shout at the intruder and let him know you're watching him from a remote location and calling. To the end-user, it works seamlessly, like 1 cohesive whole, but in reality, what LinuxMCE did is enable a bunch of existing applications to work together.</p><br />
<br />
===Which hardware is known to work?===<br />
See the [[:Category:Hardware|Hardware category]].<br />
===Is LinuxMCE a distribution or a package?===<br />
Strictly speaking LinuxMCE is a package. A very big package. The distribution it runs on is standard Kubuntu Linux.<br />
<br />
Only the PC running as the Core is required to run Kubuntu and use the LinuxMCE package.<br />
<br />
Any PC used as a Media Director can [[netboot]] from the Core, without the requirement for an OS at all. Of course, you can always boot whatever OS is already stored on the hard drive of each Media Director PC and use that PC separately from the LinuxMCE system. Play the games (or whatever) that are stored on the hard drive (using whichever OS is already installed there) there, and when you're ready to use that PC as a Media Director again, you just go back to netbooting from the Core.<br />
<br />
For the Core, you should use Kubuntu and our packages.<br />
<br />
LinuxMCE is based on the standard Kubuntu Linux distribution. While you could try to run LinuxMCE on another distribution, it's not recommended. LinuxMCE has lots of scripts and utilities to facilitate various tasks. Plus, LinuxMCE embeds many other open source projects, like Xine, Asterisk, etc., with our own "wrappers" that allows them to work together seamlessly. These wrappers are only tested against the versions we maintain in our Ubuntu mirror.<br />
<br />
Before we upgrade anything on our mirror, we thoroughly test the new packages in our system to be sure it still works.<br />
<br />
We didn't take any modules away from the Kubuntu distribution, we only added some. You can still use your Core as a normal Kubuntu Linux PC. In fact, our additions can be bypassed if they get in your way, as is explained below. But in general, DCERouter and other devices, like the home automation modules, all run in the background and won't interfere in screen sessions.<br />
<br />
''Here's what we changed:''<br />
<br />
===Can LMCE record digital television?=== <br />
Yes, as long as it is unencrypted. Please [[Understanding_digital_cable|see this article]]<br />
<br />
====Configuration scripts====<br />
LinuxMCE includes a lot of scripts that automate all aspects of maintaining a Linux system. For example, when you add a new user from the LinuxMCE Admin site, it automatically creates a new media directory, exports a samba share, creates an email and voicemail accounts, and so on. There's also scripts to do lots of low-level things like setup ip network prioritizing, so your VOIP calls are always clear. By default, LinuxMCE overwrites and re-creates many Linux config files at each boot. In this regard LinuxMCE acts like a black box appliance. However, once you install LinuxMCE you can go to the [[LinuxMCE Admin Website]]-->Advanced-->Boot Scripts and disable any or all of these scripts. Then you can still maintain your LinuxMCE Core like any other Linux PC and it won't overwrite your config files.<br />
<br />
====Our Ubuntu mirror====<br />
We maintain our own mirror based on Ubuntu. The reason is that we have "wrappers" for many open source projects like Xine, Asterisk, etc., allowing them to work together seamlessly. Whenever updates are posted to Ubuntu's repository, we test the new versions to be sure the changes did not break anything in our wrappers and that the auto-configuration scripts still work. In very rare cases, we need to make our own version of a package that replaces the one in Ubuntu. We avoid that whenever possible, and instead re-work our wrappers so that we can stay current with the "stock" version. Such changes are generally trivial, and you should see no difference between LinuxMCE's Ubuntu mirror and the official one.<br />
<br />
====Window manager====<br />
The Media Directors use our own modified version of the Ratpoison window manager. All applications appear as full-screen, with no borders. Our Orbiter GUI becomes the XWindows desktop. This is the desired behavior in an appliance-like set-top box; we completely isolate the user from anything computer-like. However, you will likely not want this as your main desktop. It is possible to run 2 versions of X on separate terminals: one with LinuxMCE's window manager, and the other with your own preferred choice of desktop.<br />
<br />
====Software Module Overview====<br />
<br />
[[Overview of the software modules]]<br />
<br />
===Ok, I'm sold - what do I need to run LinuxMCE?===<br />
LinuxMCE components include:<br />
*'''''The Core''''' - The computer that acts as the "server" for LinuxMCE. It is responsible for coordinating all the other components and managing your network. This system '''REQUIRES TWO NETWORK CARDS'''. Read the next question for an explanation.<br />
*'''''Media Directors''''' - The computers that are connected to your TV's and allow you to view your media. The Core can also act as a Media Director; this configuration is called a '''''Hybrid'''''. Any system that is to be used as a Media Director should have '''an nVidia graphics card, 6200 or better'''. Read the question after the next for an explanation.<br />
*'''''Orbiters''''' - Small devices used as advanced remote controls. Some possible devices include:<br />
**Bluetooth mobile phones (with OBEX capabilities)<br />
**Nokia Internet tablets (N770/800/810)<br />
**Windows PCs<br />
**Any device with a web browser<br />
<br />
You must have exactly one Core. You may have as many Media Directors and Orbiters as you please. For a more detailed explanation, including hardware recommendations, see [[User_Manual#Hardware|this section]] of the User Manual.<br />
<br />
You will also need additional hardware for certain functionality. Here are some examples:<br />
*Recording/Watching TV - PCI or Ethernet based TV tuner<br />
*Security - Sensors, device to connect sensors to the system, IP-cameras<br />
*Home control and automation - Home automation computer adapter, control system compatible devices (switches, thermostats, etc)<br />
*A/V equipment control - IR Transceiver, RS-232 cabling<br />
*Telecommunication - VoIP provider, VoIP phones (or at least some microphones attached to Media Directors)<br />
<br />
You don't have to buy everything at once - you can expand your system as you please.<br />
<br />
===Why do I need two network cards in my Core?===<br />
LinuxMCE is built to automate as many tasks as possible. In order to do this, it monitors new connections to your network. This allows LinuxMCE to immediately react and automatically configure new networked hardware. This includes setting up VoIP phones and adding media from other systems or Network Attached Storage (NAS) devices. <br />
<br />
The LMCE or "internal" network hosts all of your LMCE devices and media sources, and is connected to the "internal" or second NIC on your core server. The first or "external" NIC can simply connect to your existing network. You can keep any existing routers and DHCP servers you wish on your "external" existing home network. The LMCE core server will connect to that network via the external NIC, and if configured that way, will receive a DHCP lease IP address like any other device. Thus your LMCE core server effectively sits between your "external" and "internal" networks using NICs 1 and 2 respectively.<br />
<br />
I basic diagrammatic guide is [[Network_Setup|here.]]<br />
<br />
But note - anything on your existing network that you want to interact with LMCE, such as NAS devices, wireless APs, PCs that may contain media, VoIP phones, ethernet based security or home automation equipment, should be moved onto the LMCE internal network. From that point it will provide DHCP services and Internet routeing to those devices.<br />
<br />
For that reason, it is important not to put any DHCP servers on your internal network. LMCE must provide that. Any existing DHCP servers on your external network are perfectly fine and can remain, as these do not effect the internal network.<br />
<br />
Ideally, you will eventually (or immediately) move all your devices onto the LMCE internal network, for simplicity. This is highly recommended. This would leave your external network as nothing but a simple link from the core's external NIC to your Internet connection device. <br />
<br />
Some (most?) people have an ADSL modem that also provides routeing functionality - thus your LMCE core will route all Internet bound traffic to this modem, and it will route the traffic on to your ISP. <br />
<br />
Others use broadband modems as a "bridge", typically with a PPPoE dialer, and bridge their public IP address directly to the LMCE core server, thus the core is effectively directly on the Internet and performs all the routing to your ISP itself. This approach is equally valid as the core has a full firewall making it secure. This configuration can be a little trickier to set up, but has the advantage of making VoIP setup much easier.<br />
<br />
Still others have both an ADSL/cable modem and a separate router device on the external network. The LMCE core server routes to the router device, and it routes either to or through the broadband device to your ISP. Again, this is valid, but often unnecessarily complicated.<br />
<br />
===Why does LinuxMCE Require nVidia graphics cards? Why can't I use my ATI card?===<br />
Any system that is going to be used as a Media Director (including a hybrid Core) should have an nVidia graphics card, 6200 or better. This is technically not a requirement, but it is a very strong suggestion. Here's why:<br />
<br />
*ATI's Linux drivers do not properly support all the features LinuxMCE needs to run the graphical overlay<br />
*Because the drivers don't support LinuxMCE's feature set, we haven't done enough refinement of the ATI device templates to make it work without lots of manual intervention<br />
*Even with proper setup - which takes an extreme amount of effort - the results are not all that good.<br />
<br />
The bottom line, nVidia has better support in Linux than ATI, allowing LinuxMCE to do a lot more stuff. Using an nVidia card will save a lot of manual configuration and give a better user experience. For these reasons, LinuxMCE only recommends nVidia cards.<br />
<br />
''LinuxMCE developers will NOT help you configure graphics cards that do not meet this requirement. You are more than welcome to use other hardware, but do so at your own risk.''<br />
<br />
For more information see [[Display Drivers]].<br />
<br />
===How do I install LinuxMCE?===<br />
There are two ways to install LinuxMCE. Both are detailed in the [[Installation Guide]], here's a short summary of each. '''Be sure to read the [[Installation Guide]] in its entirety''' before installing LinuxMCE - it contains '''very important''' information.<br />
<br />
No matter which you choose, it's important to realize that LinuxMCE is not a Linux distribution - it's actually built upon Kubuntu. The most recent version of LinuxMCE is 7.10, which installs on top of Kubuntu 7.10. Do not attempt to install LinuxMCE 7.10 on Kubuntu 8.04 - it will not work.<br />
====DVD Method====<br />
This method will use the entire hard drive and will setup LinuxMCE with default settings. If you want more control over the installation, use the CD method. Booting from the DVD will start the install process.<br />
<br />
Default settings include:<br />
*Automatically install Kubuntu 7.10<br />
*Use the whole hard drive - wiping anything on it<br />
*Start a DHCP server on boot<br />
<br />
====CD Method====<br />
This is a two step process. First, you must install Kubuntu 7.10. '''Do not apply any Kubuntu updates.''' Doing so may cause issues with the LinuxMCE install. Then, start the CD installation from within Kubuntu (not as a boot disc). Details about this process are in the [[Installation Guide]].<br />
<br />
Additional configuration options include:<br />
*Custom partition setup<br />
*Run installation from ISO images (instead of actual discs)<br />
<br />
==First Boot==<br />
===Nothing came up on my TV! What's wrong?===<br />
Probably nothing serious. See [[AVWizard#What_to_do_if_A.2FV_Wizard_does_not_start|this page]].<br />
===My Network Card Doesn't Work! Now What?===<br />
There are some devices that don't work out of the box. [[Unrecognized_NIC|This page]] has more information on getting NICs to work.<br />
===How do I login to a LinuxMCE system?===<br />
In order to do certain things - like system configuration, or general computing - you will need to provide login information. See [[Logging_In]] for details.<br />
===How do I configure LinuxMCE?===<br />
Much of the initial configuration is handled in the installation. The remaining system setup is handled by the [[AVWizard|A/V Wizard]], which automatically launches on the first boot.<br />
<br />
For additional configuration options, see the [[LinuxMCE Admin Website]] (http://dcerouter/ or http://192.168.80.1/) or re-run the A/V Wizard.<br />
<br />
==General Information==<br />
===How are media files organized?===<br />
====General use====<br />
<p>For windows users, you can access the files on the core in Windows explorer's network neighborhood, or by choosing 'Start' 'Run' and typing \\ plus the ip of your core. You will need to login with your user-name and password; it's the same one you use with LinuxMCE Admin. You will see 2 folders: 'public' and 'john', assuming your name is 'John'. Any files that you want everyone in the House to have access to go into the public folder. The folder with your name, John in this case, is your private folder where you can put files that only that only you will have access to. Often times when you choose to save media using the orbiter it will ask you if you want the media to be public or private. If you choose public the media will be saved under the public folder, and if you choose private it will be saved under the private folder with your name. Within those folders you will find some folders called: 'music' (where all ripped cd's go), 'movies' (where all ripped DVD's go), 'videos' (where videos recorded from tv or camcorders go), pictures (where your pictures go), and 'documents' (where your documents go). When you go to play some media in the orbiter by choosing the buttons music, movies, videos, pictures or documents, you will see combined together all the media from the family's public folder as well as the media from your own personal private folder.</p><br />
<br />
<p>So, for example, if you rip a CD 'Madonna' and make it public, and rip a CD 'Rolling Stones' and make it private, and your spouse rips a CD 'Fleetwood Mac' and makes it private, then when you touch music on the orbiter you will see 'Madonna' and 'Rolling Stones', and when your spouse touches music your spouse will see 'Fleetwood Mac' and 'Madonna'. Assuming your name is john and your spouse is susan, then if you browse the network share, you will find 'Madonna' in the folder public\music and you will find 'Rolling Stones' in the folder john\music. If, in LinuxMCE admin your user has 'can modify configuration' checked, then that means you are also able to browse everybody else's private folders too. So in addition to 'public' and 'john', you will also see a folder 'susan', which contains 'music' which contains 'Fleetwood Mac'. If that option is not checked for Susan, then she will only see the folder 'public' and 'susan' and will not see your private folder 'john'.</p><br />
<br />
<p>Note that even if you check that option giving yourself access to everyone's private folders, when you go to browse media on the orbiter you will still only see public files plus your own private files, just so you're not bothered with everyone else's.</p><br />
<br />
<p>To maintain the media files, including copying deleting and renaming, you can either use another PC and a network share, such as a Windows PC with Windows Explorer, or in the LinuxMCE admin web site you can choose Media & Files, Browse.</p><br />
<br />
<p>Note that LinuxMCE maintains an internal database of all your media, including various attributes such as the actors in a movie or the composer of a song. This makes searching very comfortable. For example if you touch the music button, then start typing, you will see all attributes. For example after you touch 'G', you may see 'Geffen Studios (studio)', 'Get You Back (song)', 'GNR Live (album)', and 'Guns N Roses (performer)'. You can continue typing to narrow your entries down further, and touch any entry then 'view' to see all the music that matches. The resulting screen even does cross matching and shows pictures for each attribute.</p><br />
<br />
<p>When you rip media within LinuxMCE the attributes are created automatically. You can view attributes or change them in the LinuxMCE admin site. LinuxMCE also monitors any media that you may add or change outside of LinuxMCE, such as using Windows Explorer. For example if you copy files over in Windows Explorer, LinuxMCE will automatically scan the files and add the attributes to its internal database so you can still search. Also if you rename or delete files, LinuxMCE will automatically update your database accordingly.</p><br />
<br />
<p>If you add a plug-and-play network attached storage device, within each media folder you will see a subfolder for that device and you will be able to move files to and from it.</p><br />
<br />
====Technical explanation====<br />
<p>The public directory maps to /home/public/data, and each user's private directory maps to /home/user_xxxx/data, where xxxx is the internal user ID. The name 'john' is a symlinc to user_xxxx for convenience. The program /usr/pluto/bin/UpdateMedia uses INotify to monitor all /home/public/data and /home/user_xxxx/data folders, so it can rescan whenever the directory is changed. All attributes are stored in the MySql database pluto_media. Each file is a record in the 'File' table. UpdateMedia creates an extended attribute called 'ID' for each file with the primary key of each file. That way if you move or rename a file UpdateMedia will see the extended attribute and your attributes will not be lost--it just updates the database. If you want to add more storage you can map drives under those directories. For example, if you have another 2TB drive array that you want to use for both public music and your private movies, create 2 directories on that array, let's say: public_music and john_movies. Using a network mount, or a symlinc to a network mount, create a folder such as /home/public/data/music/my_2TB_nas that maps to public_music and /home/user_xxxx/data/movies/my_2TB_nas that maps to john_movies. Then when you browse music or movies in the orbiter you will see a folder 'my_2TB_nas' to access the files on that new drive. When you add a plug-and-play network attached storage, LinuxMCE automatically adds a folder within every single directory, such as /home/public/data/music/new_nas, /home/public/data/movies/new_nas, /home/user_xxxx/data/videos/new_nas, and these are automatically mapped to corresponding folders on the NAS. This makes it very easy for a novice to just plug in a NAS and immediately use it without any technical knowledge. However if you want to change this behavior, just remove the symlincs our plug and play script created.</p><br />
<br />
===What are scenarios?===<br />
[[Scenarios]] (aka activities) are the buttons that appear on the main menu of every controller, such as Web pads, PDAs, mobile phones, and Media Director PCs. They trigger any number of actions which can include anything from changing lighting to starting media playback to changing climate settings. Scenarios are specific to rooms. A scenario can affect any device anywhere in the house, but certain scenarios will only be displayed in certain rooms. This is so that when you are in a particular room, you will only see the scenarios that you are likely to use from that room.<br />
See [[What_scenarios_are_created_automatically?|this page]] to learn about what scenarios are created automatically.<br />
===Does LinuxMCE support encrypted DVD's?===<br />
The short answer: yes - if it is legal in your area. You will have to add optional software to enable the features. See [[Encrypted_DVD's| this page]] for more information.<br />
===How can I use additional mouse buttons for LinuxMCE?===<br />
See [[Use_Additional_Mouse_Buttons|this page]]<br />
===How should I format additional hard drives?===<br />
From "blog gelusi: Linux Tuning Guide" (http://gelusi.blogspot.com/2008/02/linux-tuning-guide.html)<br />
<br />
1. Filesystem<br />
Block sizes<br />
<br />
For filesystems dedicated to serving fairly large files, adopting a larger than default 1024 byte block size may yield significant<br />
performance gains.<br />
<br />
Recent transactions on the linux kernel list suggest that setting the block sizein an ext2 file system to 4096 instead of the <br />
default 1024 will result in less file fragmentation, faster fsck's, faster deletes and faster raw read speed, due to the reduced <br />
number of seeks.<br />
<br />
Unfortunately this cannot be changed on the fly. Only a reformat will make this so. The command to format a file system with 4096 <br />
byte blocks is:<br />
<br />
mke2fs -b 4096 /dev/whatever<br />
<br />
Additionally, on any filesystems except those used for logfiles, the default of 5% reserved for root use is excessive for large <br />
file systems, so the command to make the filesystem can be augmented to<br />
<br />
mke2fs -b 4096 -m 1 /dev/whatever<br />
<br />
to set the reserved fraction to 1 percent.<br />
<br />
Then if you want a journaling (ext3) filesystem:<br />
<br />
mke2fs -b 4096 -m 1 -j /dev/whatever<br />
<br />
Note, no further configuration should be necessary as new drives will be auto-discovered.<br />
<br />
==Fixing Problems==<br />
===What if I forget my web admin password?===<br />
[[Reset_the_password_for_the_LinuxMCE_Admin_site|See this article]]<br />
===What if I forget my linuxmce/upgrade account password?===<br />
[[Resetting_Account_Passwords|See this article]]<br />
===I can't access my media files over the network!===<br />
[[I can't access my media files over the network|See this article]].<br />
===What if you don't have a driver for my home automation device?===<br />
[[What if you don't have a driver for my home automation device|See this article]].<br />
===What if my problem isn't listed here?===<br />
It may be listed on the [[Troubleshooting]] page.<br />
<br />
If not, it's time to do some research on your own. [[Main_Page|The LinuxMCE wiki]] is full of information - try using the search feature or browsing categories. See if anyone else has had the same issue by searching on [http://forum.linuxmce.org/ the forum].<br />
<br />
When all else fails, maybe someone else has the answer for you. Try posting on [http://forum.linuxmce.org/ the forum] or our IRC channel (irc.freenode.net #linuxmce).<br />
<br />
Remember, LinuxMCE doesn't have any paid employees, so don't get annoyed if no one gets back to you right away. We're all very busy people who have lives outside of LinuxMCE.</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Network_Setup&diff=17771Network Setup2009-02-25T04:26:06Z<p>Colinjones: A page that we can use to point people to when they don't understand how to set up the network.</p>
<hr />
<div>=Overview=<br />
<br />
There is regularly some confusion over how much of your existing home network LinuxMCE requires you to change. Many people incorrectly believe that significant changes are required. In the most common case of home networks, almost no change at all is required. The Core server requires 2 NICs (Network Interface Cards). One is known as the "External" NIC and the other as the "Internal" NIC.<br />
<br />
=Existing Home Network=<br />
<br />
[[Image:Before.PNG]]<br />
<br />
Above we see a very simple home network setup. All devices are connected to a switch, which in turn is connected to the LAN port of a broadband router. In this topology, most people have their broadband router provide dynamic IP addresses to all other devices via DHCP.<br />
<br />
<br />
<br />
=Network After LinuxMCE is Installed=<br />
<br />
[[Image:After.PNG]]<br />
<br />
Above we see the same network, now LinuxMCE enabled. NOTE: The ''only'' change is the Core LinuxMCE server has been inserted between the switch and the broadband router. In practice, this means disconnecting the Cat5e/6 patch cable, shown in the first diagram, from the broadband router and connecting it into the "Internal" NIC of the of the Core server (shown here on the right of the red box). Next, get a new Cat5e/6 patch cable and connect one end to the "External" NIC of the Core server (shown here on the left of the red box), and the other end back into the LAN port of the broadband router. Your setup is now complete!<br />
<br />
In this network, your broadband router can continue providing dynamic IP addresses to the "External" NIC of the core - however, there is nothing stopping you fixing this IP address if you prefer. In which case your broadband router's DHCP server is no longer needed. For the Internal or LinuxMCE network, the Core now provides DHCP services to all devices. IMPORTANT: LinuxMCE needs to be the (only) DHCP server for the Internal network because it provides much more than just IP addresses to these devices. So it is important that you allow it to do this, and leave all your internal devices set to acquire their IP address via DHCP so that LinuxMCE works correctly. This is the only supported configuration - however, as you can see, the impact is either negligible or non-existent.<br />
<br />
<br />
=Fully Configured Smart Home Solution=<br />
<br />
[[Image:Complete.PNG]]<br />
<br />
In the above diagram you can see the same LinuxMCE enabled network after it has matured - the owner has gone nuts, adding stuff! You may only wish to use LinuxMCE for media playback, in which case you will be more interested in the "MD"s in the diagram. However, you can continue expanding it at will into its designed functionality by added telephones, security systems, home automation networks (lights, environmental controls, irrigation systems, etc)</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=File:Complete.PNG&diff=17770File:Complete.PNG2009-02-25T04:03:35Z<p>Colinjones: This is a fully configured Smart Home solution, depicted using the correct network topology.</p>
<hr />
<div>This is a fully configured Smart Home solution, depicted using the correct network topology.</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=File:After.PNG&diff=17769File:After.PNG2009-02-25T04:02:15Z<p>Colinjones: Typical network setup after installing LinuxMCE - this is the correct topology. The Core LinuxMCE device, that runs the entire house LinuxMCE network, must have 2 NICs and act as a gateway in the depicted here. This Core can either be dedicated to the tas</p>
<hr />
<div>Typical network setup after installing LinuxMCE - this is the correct topology. The Core LinuxMCE device, that runs the entire house LinuxMCE network, must have 2 NICs and act as a gateway in the depicted here. This Core can either be dedicated to the task, or it can be a "hybrid" device, meaning it is both the core of your LinuxMCE network and a Media Director</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=File:Before.PNG&diff=17768File:Before.PNG2009-02-25T03:58:45Z<p>Colinjones: Typical network layout before starting a LinuxMCE project</p>
<hr />
<div>Typical network layout before starting a LinuxMCE project</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Adding_Recognised_Media_Types&diff=17653Adding Recognised Media Types2009-02-10T21:25:31Z<p>Colinjones: New page: == The Issue == In some cases, LMCE's media playing code is perfectly capable of playing a lesser used media type, but LMCE doesn't recognise these media type extensions and so does not e...</p>
<hr />
<div>== The Issue ==<br />
<br />
In some cases, LMCE's media playing code is perfectly capable of playing a lesser used media type, but LMCE doesn't recognise these media type extensions and so does not enter the associated media files into the database.<br />
<br />
An example of this was in the 0710 betas, .mkv Matroska video files although the Xine libraries can play these files. In the current 0710RC2, .m4a (MPEG4 audio layer, commonly used in the Apple world) files are played perfectly, however LMCE does not recognise them so they do not appear in the media browsers to be selected. <br />
<br />
It is very easy to add any video or audio file type so that LMCE adds these to the database. There are two easy ways of doing this:<br />
<br />
== Method 1 (Command Line) ==<br />
<br />
An example for video is given by Totallymaxed here [http://forum.linuxmce.org/index.php?topic=3734.msg22309#msg22309] and for audio by colinjones here [http://forum.linuxmce.org/index.php?topic=6811.msg47202#msg47202]<br />
<br />
You can use a SQL command at a terminal on your core to issue a command that finds the correct MediaType table entry, then replaces the Extensions attribute with a new one.<br />
<br />
mysql -u root -D pluto_main -N -e "UPDATE MediaType SET Extensions = 'mov,avi,mpeg,mpg,wmv,ts,tp,dvd,vdr,ogm,mkv' WHERE Extensions = 'mov,avi,mpeg,mpg,wmv,ts,tp,dvd,vdr,ogm'"<br />
<br />
This very specifically replaces "mov,avi,mpeg,mpg,wmv,ts,tp,dvd,vdr,ogm" with "mov,avi,mpeg,mpg,wmv,ts,tp,dvd,vdr,ogm''',mkv'''", and so will not work once LMCE's list of accepted media types expand in the future. Thus this command will need to be updated with the new lists. If so, it is likely that it will be easier for you to use Method 2 anyway.<br />
<br />
== Method 2 (GUI) ==<br />
<br />
Download and install the MySQL GUI Tools from the [http://dev.mysql.com/downloads/gui-tools/5.0.html MySQL web site]. Now start up MySQL Query Browser and point it at your core (192.168.80.1 only from the internal LAN) and use a username of "root" and the password is blank. The port number for this connection is 3306.<br />
<br />
In the right pane, expand the Pluto_Main database and find the MediaType table. Double click on it, then hit the big Execute button up the top. This will list all the rows in that table. Now you will see two rows called "pluto_StoredAudio" and "pluto_StoredVideo". In the relevant one, edit the Extensions field to include the new file types. NOTE: you will need to enable editing first by hitting the Edit button on the bottom status bar.<br />
<br />
Finally, you will need to hit the Apply Changes button, next to the Edit button, and transfer the updates the the database. Now you can close the Query Browser.<br />
<br />
== Conclusion ==<br />
<br />
Once the changes have been made - using either method - UpdateMedia will need to scan the files again before they are added to the database. Not sure if you can just let this happen on the next 2 mins cycle, or whether you need to force a full manual scan to ensure that it picks up the new files. Feel free to edit this with the answer!<br />
<br />
<br />
[[Category: Tutorials]]</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Understanding_digital_cable&diff=17202Understanding digital cable2009-01-21T03:50:14Z<p>Colinjones: Additional info and minor edits</p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
<br />
=Intro=<br />
In the United States, a transition to digital cable is being made on February 17th, 2009. Many people have been giving confusing information about who will need converters and this also affects LMCE's tv recording. Here are the answers that LMCE users will need to know about the switch. Other countries will have different schedules for converting terrestrial, cable and satellite services.<br />
<br />
==Definitions==<br />
'''OTA''': This is shorthand for "Over the Air". This refers to any tv channels which are broadcast for free. They are over the air in the sense that all you need is an antenna plugged into your tv to access them. There is no need for a subscription to a cable company in order to receive these stations. However, some cable companies provide these channels in their tv line up.<br />
<br />
'''Broadcast Television''': This is the another way to say OTA. As are Digital Terrestrial Television, or DTT.<br />
<br />
'''A Coax cable''': This is the standard tv cable. When going from a wall jack to the tv, you use a coax cable. It's basically an insulated piece of copper wiring with an attachment on the ends to hold it in the plug. <br />
<br />
'''Analog cable''': This refers to the type of signal that comes through the coax cable. It is very similar to a radio signal in that multiple channels (or stations) can be carried through the wire on different frequencies. You don't need a wire for each tv station. This is why we use the term "tv tuner". A tuner is able to lock onto different frequencies carried through the coax cable. This is simplified definition. If you have any more details, please add them.<br />
<br />
'''Digital cable''': This also refers to the type of signal that comes through a coax cable. But with digital tv, 1s and 0s are sent through the coax cable. Thus, a different type of tuner is required to understand this stream of data. <br />
<br />
'''[http://en.wikipedia.org/wiki/Ntsc NTSC]''': National Television System Committee. The analogue television standard used for North America and some other countries. It is actually a system for encoding the colour signal. Although it doesn't necessarily mean 60Hz refresh rate, this is usually implied because of the local power frequencies in most countries that use it. It is used for transmitting analogue television both terrestrially (broadcast to your antenna) and over cable networks and satellite. Compare: PAL<br />
<br />
'''[http://en.wikipedia.org/wiki/PAL PAL]''': Phase Alternate Line. The analogue television standard used for much of the world outside North America. It is actually a system for encoding the colour signal. Although it doesn't necessarily mean 50Hz refresh rate, this is usually implied because of the local power frequencies in most countries that use it. It is used for transmitting analogue television both terrestrially (broadcast to your antenna) and over cable networks and satellite. Compare: NTSC<br />
<br />
'''[http://en.wikipedia.org/wiki/ATSC_Standards ATSC]''': Advanced Television Systems Committee. The digital replacement for NTSC - used in much the same territories. Although some digital satellite services in the North American territory, at least, have opted to use DVB-S/DVB-S2 instead - this is the digital replacement for PAL in satellite services. eg. Dish.<br />
<br />
'''[http://en.wikipedia.org/wiki/Dvb DVB]''': Digital Video Broadcasting. The digital replacement for PAL - used in much the same territories. DVB-S, DVB-T, DVB-C, DVB-H refer to the specific standards for Satellite, Terrestrial, Cable and Handheld, respectively. There are additional formats already in place or to be released soon that include version 2's of these existing formats.<br />
<br />
'''[http://en.wikipedia.org/wiki/QAM QAM]''': Quadrature Amplitude Modulation is a format that can be used for digital information. Just like there are multiple types of file formats for an audio file, (mp3, wma, ogg, flac, etc) there are formats for digital television. QAM seems to be becoming the standard format in the US. More information is needed here, so please help out. <br />
<br />
'''Encrypted signal''': If a piece of data is encrypted, that means that the information is sent in code which only a few people are allowed to know. Cable companies often encrypt their cable signal in order to prevent stealing. If the signal cannot be decrypted, the tv signal is not viewable.<br />
<br />
'''Clear QAM''': Clear QAM is basically a television signal in QAM format that is not encrypted. Virtually all of the OTA stations in the U.S.A use this format.<br />
<br />
<br />
<br />
<br />
==The switch to digital==<br />
<br />
Analogue Switch Off (ASO) So what exactly will be happening on February 17th? All OTA stations will be required by federal law to cease broadcasting analog and begin broadcasting digital. That means that the free stations which are tuned using rabbit ears will no longer carry an analog signal. They will carry digital. Thus, a digital tuner will be needed to understand this new stream of data.<br />
<br />
<br />
However, cable companies are NOT required to change to digital. Hence, comcast customers will not be required to change anything once the February 17th change happens. Comcast will still continue to send analog cable to it's subscribers if they so choose. Here are some common situations and what the outcome will be after February 17th.<br />
<br />
<br />
<br />
Cable subscription: NO, I use an antenna<br />
<br />
Does your tv have a digital tuner?: NO<br />
<br />
Result: In order to continue watching any television at all, you will need a digital converter. Your antenna will be plugged into the converter box, which will then feed into your tv set.<br />
<br />
<br />
<br />
Cable subscription: Yes, from Comcast (or any other)<br />
<br />
Analog or digital subscription?: Analog<br />
<br />
Does your tv have a digital tuner?: NO or YES. Doesn't matter either way<br />
<br />
Result: Nothing will need to change. Your cable provider will continue providing you with analog tv and your television will be able to understand it. Comcast has specifically said it will continue broadcasting analog.<br />
<br />
<br />
Cable subscription: Yes, from Comast (or any other)<br />
<br />
Analog or digital subscription?: Digital and/or High Def<br />
<br />
Does your tv have a digital tuner?: Yes, of course<br />
<br />
Result: Nothing will change for you either. You already are using digital, so the change doesn't affect you.<br />
<br />
<br />
Cable subscription: Yes, from a satellite provider<br />
<br />
Analog or digital subscription?: either<br />
<br />
Result: Satellite TV will not be affected in anyway by the change to digital.<br />
<br />
==What does it mean for LMCE users?==<br />
<br />
First and foremost, it is essential that your tuner first be compatible with LMCE. Before asking the question "Will I be able to record my television?", you must first ask "Will my tuner work at all with LMCE?" For that, please check the wiki section on tuner cards.<br />
<br />
<br />
<br />
Now, onto business. The ability of your computer's tv tuner will be limited by the type of signal. If you have an analog cable subscription, LMCE will be able to tune every single channel which you enjoy on your normal television. You will need an NTSC capable tuner for your computer.<br />
<br />
The problems arise when trying to record digital television. In general, most, if not all cable companies encrypt their digital tv signals. Since they undoubtedly keep their encryption techniques a secret, LMCE will be unable to decrypt those signals. The net result is that digital cable from a provider is unable to be tuned/recorded by LMCE, even when using a digital (ATSC) tuner. The only exception are the free, OTA channels. These channels are not encrypted, thus your ATSC computer tuner will be able to watch these streams. There are work arounds to recording digital subscriptions, but that will be added later as it is very cumbersome and unreliable.</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=MSI_Wind_PC&diff=17132MSI Wind PC2009-01-16T22:07:36Z<p>Colinjones: </p>
<hr />
<div>[[Category: Hardware]] <br />
[[Category: Media Directors]]<br />
[[Category: Barebones]]<br />
<br />
The MSI Wind PC is a very small, ultra low power consumption Intel Atom based PC that can be used as an MD. This is a low end, very low cost barebones PC that already includes a CPU. So for MD useage, you just need to add a stick of RAM and you're done!<br />
<br />
The cheapest I have seen it is at NewEgg (they do not ship internationally) for US$139.99, [http://www.newegg.com/Product/Product.aspx?Item=N82E16856167032&Tpk=msi%20wind%20pc here].<br />
<br />
[[Image:MSI_Wind_PC.jpg|thumb|right|300px|MSI Wind PC]]<br />
<br />
<br />
== Advantages ==<br />
<br />
* Small foot print - 300x260x65mm<br />
* Support UI2 with overlay and 1080p (HD) video playback - VGA out only<br />
* 7.1 Surround sound - analogue minijacks<br />
* Almost noiseless<br />
* Low energy consumption - less than 40w at full speed, this is probably including a HDD which isn't needed for LMCE<br />
* Low price<br />
<br />
== Disadvantages ==<br />
<br />
* Video is analogue - no DVI or HDMI<br />
* Audio is analogue - no SPDIF out<br />
<br />
== Known Issues ==<br />
<br />
* Photo Screen Saver sometimes causes issues with the Intel graphics chipset - this causes the unit to lock up. Resolution: disable PSS. It is possible in the next version (0810) of LMCE the driver updates will fix this.<br />
* There is an issue with the NIC drivers that means the unit can't PXE boot properly. Resolution: follow [http://wiki.linuxmce.org/index.php/R8168 this] article to correct the drivers. Probable that the next version of LMCE (0810) will correct this.</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=MSI_Wind_PC&diff=17131MSI Wind PC2009-01-16T22:05:30Z<p>Colinjones: MSI Wind PC</p>
<hr />
<div>[[Category: Hardware]] <br />
[[Category: Media Directors]]<br />
[[Category: Barebones]]<br />
<br />
The MSI Wind PC is a very small, ultra low power consumption Intel Atom based PC that can be used as an MD. This is a low end, very low cost barebones PC that already includes a CPU. So for MD useage, you just need to add a stick of RAM and you're done!<br />
<br />
The cheapest I have seen it is at NewEgg (they do not ship internationally) for US$139.99, [http://www.newegg.com/Product/Product.aspx?Item=N82E16856167032&Tpk=msi%20wind%20pc here].<br />
<br />
[[Image:MSI_Wind_PC.jpg|thumb|right|300px|MSI Wind PC]]<br />
<br />
<br />
== Advantages ==<br />
<br />
* Small foot print - 300x260x65mm<br />
* Support UI2 with overlay and 1080p (HD) video playback - VGA out only<br />
* 7.1 Surround sound - analogue minijacks<br />
* Almost noiseless<br />
* Low energy consumption - less than 40w at full speed, this is probably including a HDD which isn't needed for LMCE<br />
* Low price<br />
<br />
== Disadvantages ==<br />
<br />
* Video is analogue - no DVI or HDMI<br />
* Audio is analogue - no SPDIF out<br />
<br />
== Known Issues ==<br />
<br />
* Photo Screen Saver sometimes causes issues with the Intel graphics chipset - this causes the unit to lock up. Resolution: disable PSS. It is possible in the next version of LMCE the driver updates will fix this.<br />
* There is an issue with the NIC drivers that means the unit can't PXE boot properly. Resolution: follow [http://wiki.linuxmce.org/index.php/R8168 this] article to correct the drivers</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=File:MSI_Wind_PC.jpg&diff=17130File:MSI Wind PC.jpg2009-01-16T21:47:08Z<p>Colinjones: </p>
<hr />
<div></div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Information_for_Australian_users&diff=15876Information for Australian users2008-10-18T22:45:07Z<p>Colinjones: Information for australian users moved to Information for Australian users: Capitalisation</p>
<hr />
<div>[[Category: Australian Setups]]<br />
<br />
== VDR ==<br />
<br />
VDR is perfect for Australian setups as it is specifically targeted at the DVB digital TV standard. Also, it is far "lighter" than MythTV so integration of its UI with LMCE's UI is much more complete than MythTV. This integration is getting better all the time as it is an active project for [[Convergenthome|CHT]].<br />
<br />
Also, VDR automatically receives Electronic Program Guide information from the TV stations over-the-air. This requires no setup whatsoever and is, of course, free!<br />
<br />
MythTV has more features and capabilities, but for simplicity and consistency of interface VDR is the better option.<br />
<br />
== MythTV ==<br />
MythTV works fine with Australian Free-To-Air digital television. There are 3 main sources for Electronic Program Guide information, [http://www.icetv.com.au iceTV], [http://www.tuhs.org/twiki/bin/view/TVGuide/WebHome The Australian Community TV Guide](ozTiVo), and [http://svn.whuffy.com/wiki Shepherd] which grabs info from multiple sources and collates it.<br />
<br />
iceTV is a comercial offering, and costs about AU$3 per week. ozTiVo is free, however both sites require registration.<br />
<br />
Shepherd can use your OzTivo registration. It is currently the recommended grabber for Australian users, as it is comprehensive and reliable, easy to set up, and keeps itself up to date.<br />
<br />
=== Setup for OzTivo===<br />
*Visit one (or both) of the above sites to register and set up your profile (be sure to select xmltv for the data format).<br />
*Get [http://www.cse.unsw.edu.au/~willu/xmltv/tv_grab_au_reg this script] and install it in /usr/local/bin<br />
**Make sure it is executable: ''sudo chmod +x tv_grab_au_reg''<br />
**Symlink /usr/local/bin/tv_grab_au to tv_grab_au_reg with ''sudo ln -s /usr/local/bin/tv_grab_au_reg /usr/local/bin/tv_grab_au''.<br />
*Run MythTV-setup and add a new video source to use 'tv_grab_au' (call it something like FTA).<br />
**Set 'TimeOffset' to 'Auto'<br />
**Configure a capture card to use the video source (FTA)<br />
**Scan the channels, delete the ones you don't want, then add xmltv info (from your iceTV or ozTiVo profile) to the ones that are left.<br />
**Exit Setup, don't run mythfilldatabase.<br />
*Edit /root/.mythtv/<input source name>.xmltv (FTA in above example) to include your username and password. Remove the information for any sites you are not using. (It may be wise to set this file as read-only, every time you enter the input sources page in mythTV-setup it reconfigures the tv_grab_au script, which overwrites the configuration file with defaults).<br />
*Run mythfilldatabase( start MythTV-setup and then exit, hit yes when prompted.<br />
*Enjoy your new EPG<br />
<br />
You can use the same process to import foxtel channels, call it foxtel instead of FTA. (see [http://www.ozmyth.com/wiki/Preparing+the+Foxtel+STU+for+MythTV this page] for info on setting up foxtel to work with mythTV).<br />
<br />
=== Setup for Shepherd ===<br />
There are some issues with the normal mythfilldatabase job triggered from inside Mythtv and Shepherd (and Oz tv listing grabber). This is due to permissions etc. This can be resolved by running the myhtfilldatabase job automatically from cron and is the recommended way of running shepherd. Shepherd will set this up for you automatically as it installs.<br />
<br />
* sudo passwd mythtv<br />
* sudo su - mythtv<br />
* mkdir .shepherd && cd .shepherd<br />
* wget http://www.whuffy.com/shepherd/shepherd<br />
* sh /home/mythtv/.shepherd/shepherd<br />
* Run through the setup process, and allow shepherd to set up mythtv and a cron entry to run mythtfilldatabase (as mythtv user). Note that one step fails: where it tries to to create a symbolic link from /usr/bin/tv_grab_au to /home/mythtv/.shepherd/shepherd<br />
* create symbolic link manually:<br />
** sudo mv /usr/bin/tv_grab_au /usr/bin/tv_grab_au.old<br />
** sudo ln -s /home/mythtv/.shepherd/shepherd /usr/bin/tv_grab_au<br />
** Use mythtv-setup from a terminal window to disable the mythfilldatabase job ('cos cron will do it instead)<br />
<br />
Note that log files for mythfilldatabase will now go to /home/mythtv/.shepherd/log dir.<br />
<br />
=== Miscellaneous ===<br />
<br />
* Check that your frequency tuning tables are OK for Mythtv. If you have problems with some channels breaking up or horrible screeching audio bursts, it may be that the automatic tuning has not worked properly for a tuner. My SBS transport was tuning to 536500000 instead of 536625000. A transport is what we used to know as a channel in the analogue world, but as the station's allocated frequency band carries multiple channels they renamed the station frequency to a transport.<br />
** From a terminal window '''mythtv-setup --geometry 800x600'''<br />
** Go to Transport Editor and edit any that are wrong.<br />
** Check the frequencies are OK using the [http://www.acma.gov.au/postcode/postcode_acma.shtml pretty useless Australian Communications and Media Authority website]. <br />
*** You need to enter your postcode, click on the callsign (e.g. SBS) and then it will show you the channel (purple is digital- scroll down).<br />
*** Then look up the channel frequency [http://www.zcg.com.au/tvchannels.htm in this table] not on the govt website(why would a govt website have the info in one easy to find place?)<br />
*** '''THE FREQUENCY CALCS NEED CHECKING'''<br />
*** [http://www20.sbs.com.au/transmissions/ SBS] Note that SBS is ''not'' broadcasting on the "traditional" centre of the channel 536500000, but 125 KHz higher at 536625000.<br />
*** [http://www.abc.net.au/reception/freq/ ABC]</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Information_for_Australian_users&diff=15875Information for Australian users2008-10-18T22:43:00Z<p>Colinjones: CHT link</p>
<hr />
<div>[[Category: Australian Setups]]<br />
<br />
== VDR ==<br />
<br />
VDR is perfect for Australian setups as it is specifically targeted at the DVB digital TV standard. Also, it is far "lighter" than MythTV so integration of its UI with LMCE's UI is much more complete than MythTV. This integration is getting better all the time as it is an active project for [[Convergenthome|CHT]].<br />
<br />
Also, VDR automatically receives Electronic Program Guide information from the TV stations over-the-air. This requires no setup whatsoever and is, of course, free!<br />
<br />
MythTV has more features and capabilities, but for simplicity and consistency of interface VDR is the better option.<br />
<br />
== MythTV ==<br />
MythTV works fine with Australian Free-To-Air digital television. There are 3 main sources for Electronic Program Guide information, [http://www.icetv.com.au iceTV], [http://www.tuhs.org/twiki/bin/view/TVGuide/WebHome The Australian Community TV Guide](ozTiVo), and [http://svn.whuffy.com/wiki Shepherd] which grabs info from multiple sources and collates it.<br />
<br />
iceTV is a comercial offering, and costs about AU$3 per week. ozTiVo is free, however both sites require registration.<br />
<br />
Shepherd can use your OzTivo registration. It is currently the recommended grabber for Australian users, as it is comprehensive and reliable, easy to set up, and keeps itself up to date.<br />
<br />
=== Setup for OzTivo===<br />
*Visit one (or both) of the above sites to register and set up your profile (be sure to select xmltv for the data format).<br />
*Get [http://www.cse.unsw.edu.au/~willu/xmltv/tv_grab_au_reg this script] and install it in /usr/local/bin<br />
**Make sure it is executable: ''sudo chmod +x tv_grab_au_reg''<br />
**Symlink /usr/local/bin/tv_grab_au to tv_grab_au_reg with ''sudo ln -s /usr/local/bin/tv_grab_au_reg /usr/local/bin/tv_grab_au''.<br />
*Run MythTV-setup and add a new video source to use 'tv_grab_au' (call it something like FTA).<br />
**Set 'TimeOffset' to 'Auto'<br />
**Configure a capture card to use the video source (FTA)<br />
**Scan the channels, delete the ones you don't want, then add xmltv info (from your iceTV or ozTiVo profile) to the ones that are left.<br />
**Exit Setup, don't run mythfilldatabase.<br />
*Edit /root/.mythtv/<input source name>.xmltv (FTA in above example) to include your username and password. Remove the information for any sites you are not using. (It may be wise to set this file as read-only, every time you enter the input sources page in mythTV-setup it reconfigures the tv_grab_au script, which overwrites the configuration file with defaults).<br />
*Run mythfilldatabase( start MythTV-setup and then exit, hit yes when prompted.<br />
*Enjoy your new EPG<br />
<br />
You can use the same process to import foxtel channels, call it foxtel instead of FTA. (see [http://www.ozmyth.com/wiki/Preparing+the+Foxtel+STU+for+MythTV this page] for info on setting up foxtel to work with mythTV).<br />
<br />
=== Setup for Shepherd ===<br />
There are some issues with the normal mythfilldatabase job triggered from inside Mythtv and Shepherd (and Oz tv listing grabber). This is due to permissions etc. This can be resolved by running the myhtfilldatabase job automatically from cron and is the recommended way of running shepherd. Shepherd will set this up for you automatically as it installs.<br />
<br />
* sudo passwd mythtv<br />
* sudo su - mythtv<br />
* mkdir .shepherd && cd .shepherd<br />
* wget http://www.whuffy.com/shepherd/shepherd<br />
* sh /home/mythtv/.shepherd/shepherd<br />
* Run through the setup process, and allow shepherd to set up mythtv and a cron entry to run mythtfilldatabase (as mythtv user). Note that one step fails: where it tries to to create a symbolic link from /usr/bin/tv_grab_au to /home/mythtv/.shepherd/shepherd<br />
* create symbolic link manually:<br />
** sudo mv /usr/bin/tv_grab_au /usr/bin/tv_grab_au.old<br />
** sudo ln -s /home/mythtv/.shepherd/shepherd /usr/bin/tv_grab_au<br />
** Use mythtv-setup from a terminal window to disable the mythfilldatabase job ('cos cron will do it instead)<br />
<br />
Note that log files for mythfilldatabase will now go to /home/mythtv/.shepherd/log dir.<br />
<br />
=== Miscellaneous ===<br />
<br />
* Check that your frequency tuning tables are OK for Mythtv. If you have problems with some channels breaking up or horrible screeching audio bursts, it may be that the automatic tuning has not worked properly for a tuner. My SBS transport was tuning to 536500000 instead of 536625000. A transport is what we used to know as a channel in the analogue world, but as the station's allocated frequency band carries multiple channels they renamed the station frequency to a transport.<br />
** From a terminal window '''mythtv-setup --geometry 800x600'''<br />
** Go to Transport Editor and edit any that are wrong.<br />
** Check the frequencies are OK using the [http://www.acma.gov.au/postcode/postcode_acma.shtml pretty useless Australian Communications and Media Authority website]. <br />
*** You need to enter your postcode, click on the callsign (e.g. SBS) and then it will show you the channel (purple is digital- scroll down).<br />
*** Then look up the channel frequency [http://www.zcg.com.au/tvchannels.htm in this table] not on the govt website(why would a govt website have the info in one easy to find place?)<br />
*** '''THE FREQUENCY CALCS NEED CHECKING'''<br />
*** [http://www20.sbs.com.au/transmissions/ SBS] Note that SBS is ''not'' broadcasting on the "traditional" centre of the channel 536500000, but 125 KHz higher at 536625000.<br />
*** [http://www.abc.net.au/reception/freq/ ABC]</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Information_for_Australian_users&diff=15874Information for Australian users2008-10-18T22:38:01Z<p>Colinjones: Page was biased towards Myth, when VDR is usually a better choice for Australia</p>
<hr />
<div>[[Category: Australian Setups]]<br />
<br />
== VDR ==<br />
<br />
VDR is perfect for Australian setups as it is specifically targeted at the DVB digital TV standard. Also, it is far "lighter" than MythTV so integration of its UI with LMCE's UI is much more complete than MythTV. This integration is getting better all the time as it is an active project for CHT.<br />
<br />
Also, VDR automatically receives Electronic Program Guide information from the TV stations over-the-air. This requires no setup whatsoever and is, of course, free!<br />
<br />
MythTV has more features and capabilities, but for simplicity and consistency of interface VDR is the better option.<br />
<br />
== MythTV ==<br />
MythTV works fine with Australian Free-To-Air digital television. There are 3 main sources for Electronic Program Guide information, [http://www.icetv.com.au iceTV], [http://www.tuhs.org/twiki/bin/view/TVGuide/WebHome The Australian Community TV Guide](ozTiVo), and [http://svn.whuffy.com/wiki Shepherd] which grabs info from multiple sources and collates it.<br />
<br />
iceTV is a comercial offering, and costs about AU$3 per week. ozTiVo is free, however both sites require registration.<br />
<br />
Shepherd can use your OzTivo registration. It is currently the recommended grabber for Australian users, as it is comprehensive and reliable, easy to set up, and keeps itself up to date.<br />
<br />
=== Setup for OzTivo===<br />
*Visit one (or both) of the above sites to register and set up your profile (be sure to select xmltv for the data format).<br />
*Get [http://www.cse.unsw.edu.au/~willu/xmltv/tv_grab_au_reg this script] and install it in /usr/local/bin<br />
**Make sure it is executable: ''sudo chmod +x tv_grab_au_reg''<br />
**Symlink /usr/local/bin/tv_grab_au to tv_grab_au_reg with ''sudo ln -s /usr/local/bin/tv_grab_au_reg /usr/local/bin/tv_grab_au''.<br />
*Run MythTV-setup and add a new video source to use 'tv_grab_au' (call it something like FTA).<br />
**Set 'TimeOffset' to 'Auto'<br />
**Configure a capture card to use the video source (FTA)<br />
**Scan the channels, delete the ones you don't want, then add xmltv info (from your iceTV or ozTiVo profile) to the ones that are left.<br />
**Exit Setup, don't run mythfilldatabase.<br />
*Edit /root/.mythtv/<input source name>.xmltv (FTA in above example) to include your username and password. Remove the information for any sites you are not using. (It may be wise to set this file as read-only, every time you enter the input sources page in mythTV-setup it reconfigures the tv_grab_au script, which overwrites the configuration file with defaults).<br />
*Run mythfilldatabase( start MythTV-setup and then exit, hit yes when prompted.<br />
*Enjoy your new EPG<br />
<br />
You can use the same process to import foxtel channels, call it foxtel instead of FTA. (see [http://www.ozmyth.com/wiki/Preparing+the+Foxtel+STU+for+MythTV this page] for info on setting up foxtel to work with mythTV).<br />
<br />
=== Setup for Shepherd ===<br />
There are some issues with the normal mythfilldatabase job triggered from inside Mythtv and Shepherd (and Oz tv listing grabber). This is due to permissions etc. This can be resolved by running the myhtfilldatabase job automatically from cron and is the recommended way of running shepherd. Shepherd will set this up for you automatically as it installs.<br />
<br />
* sudo passwd mythtv<br />
* sudo su - mythtv<br />
* mkdir .shepherd && cd .shepherd<br />
* wget http://www.whuffy.com/shepherd/shepherd<br />
* sh /home/mythtv/.shepherd/shepherd<br />
* Run through the setup process, and allow shepherd to set up mythtv and a cron entry to run mythtfilldatabase (as mythtv user). Note that one step fails: where it tries to to create a symbolic link from /usr/bin/tv_grab_au to /home/mythtv/.shepherd/shepherd<br />
* create symbolic link manually:<br />
** sudo mv /usr/bin/tv_grab_au /usr/bin/tv_grab_au.old<br />
** sudo ln -s /home/mythtv/.shepherd/shepherd /usr/bin/tv_grab_au<br />
** Use mythtv-setup from a terminal window to disable the mythfilldatabase job ('cos cron will do it instead)<br />
<br />
Note that log files for mythfilldatabase will now go to /home/mythtv/.shepherd/log dir.<br />
<br />
=== Miscellaneous ===<br />
<br />
* Check that your frequency tuning tables are OK for Mythtv. If you have problems with some channels breaking up or horrible screeching audio bursts, it may be that the automatic tuning has not worked properly for a tuner. My SBS transport was tuning to 536500000 instead of 536625000. A transport is what we used to know as a channel in the analogue world, but as the station's allocated frequency band carries multiple channels they renamed the station frequency to a transport.<br />
** From a terminal window '''mythtv-setup --geometry 800x600'''<br />
** Go to Transport Editor and edit any that are wrong.<br />
** Check the frequencies are OK using the [http://www.acma.gov.au/postcode/postcode_acma.shtml pretty useless Australian Communications and Media Authority website]. <br />
*** You need to enter your postcode, click on the callsign (e.g. SBS) and then it will show you the channel (purple is digital- scroll down).<br />
*** Then look up the channel frequency [http://www.zcg.com.au/tvchannels.htm in this table] not on the govt website(why would a govt website have the info in one easy to find place?)<br />
*** '''THE FREQUENCY CALCS NEED CHECKING'''<br />
*** [http://www20.sbs.com.au/transmissions/ SBS] Note that SBS is ''not'' broadcasting on the "traditional" centre of the channel 536500000, but 125 KHz higher at 536625000.<br />
*** [http://www.abc.net.au/reception/freq/ ABC]</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=1%261&diff=157791&12008-10-03T21:50:12Z<p>Colinjones: /* Additional needs if LinuxMCE is NOT your internet router */</p>
<hr />
<div>1&1 is a german ISP who also provides VoIP services.<br />
== Setup of 1und1 ==<br />
Select 1&1 from the Phone Lines link in the web admin and fill out the blanks.<br />
== Additional needs if LinuxMCE is NOT your internet router ==<br />
If you don't have LinuxMCE as your router, you have to add three additional settings manually to the sip.conf in /etc/asterisk/sip.conf<br />
In the [general]-section add<br />
localnet=192.168.80.0/255.255.255.0<br />
externhost=<name of your the DNS name of your external IP address><br />
externrefresh=10<br />
Make sure you also to port forward the following ports and protocols to the IP address of the external address of LinuxMCE.<br />
# Port 5060, Protocol udp<br />
# Port 10000-20000, Protocol udp<br />
<br />
[[Category: Telecom]]<br />
[[Category: Phone Lines]]</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Frequently_Asked_Questions&diff=15716Frequently Asked Questions2008-09-24T23:17:49Z<p>Colinjones: /* Why do I need 2 network cards in my Core? */</p>
<hr />
<div>[[Category:Documentation]]<br />
This '''frequently asked questions''' (FAQ) section outlines solutions to the most common queries for initial/potential users. See also [[troubleshooting]] for solutions to problems experienced with the system.<br />
==Before Installing LinuxMCE==<br />
===What Does LinuxMCE Do For Me?===<br />
'''LinuxMCE is a whole home automation suite. It includes full featured solutions for:'''<br />
*Media<br />
**Organize media with [[Catalog_media_with_attributes|special metadata tags]]<br />
**View/Listen to media in any room<br />
**Media automatically [[Have_my_media_follow_me|follows you]] through your home<br />
**New media is automatically detected - even if it's on other devices like another computer on your network or Network Attached Storage (NAS)<br />
**Control all your A/V gear through LinuxMCE (using [[Control_regular_A/V_equipment|IR]], [[Control_A/V_equipment_with_RS232/USB/Ethernet|USB, Ethernet, or RS-232]]) including automatically powering everything on and setting the proper inputs on each device<br />
*[[Security]]<br />
**Monitor sensors and [[Have_LinuxMCE_notify_me_of_security_alerts|trigger events]]<br />
**[[Monitor_surveillance_cameras|Monitor security cameras]]<br />
*[[LinuxMCE_telecom_features|Telecomunication]]<br />
**Use VoIP phones anywhere in your home with minimal setup<br />
**Voicemail, call forwarding, advanced caller ID<br />
*Network Management<br />
**Take the place of a standard home router<br />
**Advanced [[Firewall_Rules|firewall]]<br />
**Advanced Quality of Service (QoS) to make sure your bandwidth is used effectively (especially important for VoIP)<br />
**Manage networked storage (such as [[Network_Attached_Storage|NAS devices]]<br />
*[[Automation|Home Control and Automation]]<br />
**Control climate and lighting throughout your entire home<br />
<br />
'''LinuxMCE provides all this functionality by controlling [[:Category:Hardware|all kinds of devices]] throughout the home including:'''<br />
*LinuxMCE [[Core]] Computer<br />
*LinuxMCE [[Media_Directors|Media Director]] Computers<br />
*LinuxMCE [[Orbiters|Orbiters]] (Fancy remotes)<br />
**Nokia [[Nokia 770|770]]/[[Nokia N800|N800/N810]]<br />
**Various PDAs (such as IPAQ 5550 and IPAQ hx2410)<br />
**Various Bluetooth capable mobile phones (including Nokia [[Nokia E65|E65]], [[Nokia N70|N70]], [[Nokia N73|N73]], [[Nokia 6620|6620]], [[Nokia 7650|7650]]) <br />
**The [[Web Orbiter]]<br />
**Various [[:Category:Orbiters|other devices]]<br />
*Networked storage (including [[:Category:Network_Attached_Storage|Network Attached Storage]] (NAS) Devices)<br />
*A/V Equipment (TVs, Receivers, Cable Boxes, etc)<br />
**Using [[:Category:Infrared|Infrared]] (IR)<br />
**Using [[Control_A/V_equipment_with_RS232/USB/Ethernet|RS-232]] (Serial)<br />
**Using [[Control_A/V_equipment_with_RS232/USB/Ethernet|Ethernet]] (Network)<br />
**Using [[Control_A/V_equipment_with_RS232/USB/Ethernet|USB]]<br />
*TV [[:Category:TV_Cards|Capture Devices]]<br />
*Lighting [[:Category:Automation|Automation]]<br />
**Using [[X10_LinuxMCE_Configuration|X10]]<br />
**Using [[:Category:ZWave|Z-Wave]]<br />
**Using [[:Category:Insteon|Insteon]]<br />
**Using [[:Category:Automation|various other protocols]]<br />
**See also: [[Automation]]<br />
*HVAC (Climate Control)[[:Category:Automation|Automation]]<br />
*Security [[:Category:Security|Systems or Individual Sensors]]<br />
*Surveillance [[:Category:Cameras|Cameras]] (IP, Firewire, [[:Category:Video_Capture_Boards|video capture board]], etc)<br />
*VoIP [[:Category:Phones|Phones]] and [[VOIP Service Providers|Service Providers]]<br />
<br />
For more, see [[What can I do with LinuxMCE?]]<br />
<br />
===Is LinuxMCE an appliance or software solution?===<br />
Until now there have been two options for a smarthome+media system:<br />
# Low cost '''software''' based PC solutions, including home automation software like [http://www.homeseer.com HomeSeer], [http://www.premisesystems.com Premise] and [http://www.misterhouse.com Mr. House], also media software like [http://www.microsoft.com/windowsxp/mediacenter/default.mspx Microsoft Windows XP Media Center].<br />
# '''Appliance''' solutions, like [http://www.crestron.com Crestron], [http://www.amx.com AMX], [http://www.kaleidescape.com Kaleidescape] and [http://www.escient.com Escient].<br />
<br />
High-end systems are always appliance based, preferred for their simplicity, reliability and lack of hassle; no worry about missing the football game because your PC-based PVR got a virus. But appliance systems cost a lot &mdash; for one that includes automation, media, telephony, etc., like LinuxMCE. Even though those "appliances" are normally PC's inside special cases, often running Linux plus some proprietary software, you can never get the software separately to build your own &mdash; until now.<br />
<br />
LinuxMCE is an appliance solution. The Core becomes a self-configuring, self-maintaining black box appliance. Since the Core automatically offers a network boot image to any PC's you want to use as media directors, they too become appliances. You can still use them as a PC, of course, but you can crash the hard drive, install a virus, delete system files, and it doesn't matter. When you hit 'LinuxMCE' on the remote control, the Core sends it a network boot, the hard drive turns off, it doesn't use your operating system, and you'll never see a PC prompt. And when you hit the PC button, it goes back to being a PC like normal. LinuxMCE is a 'family friendly' solution--you can use the PC for kernel-level coding, knowing the kids can always hit 1 button and still use it to watch cartoons.<br />
<br />
LinuxMCE offers the best of both worlds: an appliance solution at the price of a software solution, and the the power and versatility of a software solution with the ease of use of an appliance. We offer the software for free as open source because our business is licensing LinuxMCE to hardgoods manufacturers who embed it in their products.<br />
<br />
===What do commercial appliance solutions similar to LinuxMCE cost?===<br />
Appliance solutions are normally quite expensive. The most popular combinations are:<br />
# [http://www.crestron.com Crestron] system to do all the home automation. The cost varies depending on what you want to do with it, but a whole-house solution including touch-screen panels will set you back at least $25,000 for an entry-level system, and can easily hit 6 figures.<br />
# [http://www.kaleidescape.com Kaleidescape] for the DVD movie server, costing $27,000 for the main server, and $4,000 for each TV where you want to watch movies.<br />
# [http://www.escient.com Escient] Fireball for the music server, costing $5,000 for the central music server.<br />
# A PBX phone system with voicemail, like [http://www.panasonic.com Panasonic] will cost another 5 grand or so.<br />
<br />
All of those products require professional installation and setup, particularly the home automation devices. LinuxMCE was designed with simple web-based wizard so even non-techies can get a whole solution up within a few hours. But our competitors' products are different. Smart home dealers will require a trained programmer to set them up. For example, it can take weeks of programming to set up a Crestron system in a good-sized house. Programming fees can be over $10,000, plus re-programing fees every time you make a change. '''Bottom line: around $100,000''' for an appliance solution that does what LinuxMCE does.<br />
<br />
Appliance solutions are typically PCs, running an Linux OS with custom, proprietary software, placed inside custom cases. The software is not available separately, so there's no way to economize or build your own.<br />
<br />
LinuxMCE has taken a different approach. LinuxMCE is also an appliance solution, but we have made the software available separately. In fact, it is free, so techies and software programmers can build their own high-end appliance systems. Competing PC hardware manufacturers can license the LinuxMCE platform to use in standard, low-cost PCs. LinuxMCE brings down the cost by offering all the functionality of several systems in 1 system: whole house media & entertainment, home automation, telecom, security, and personal computer.<br />
<br />
===I've heard LinuxMCE is just a bunch of projects merged together. Is that true? What is special about LinuxMCE?===<br />
<p>LinuxMCE includes a lot of other open source projects, like Xine, Asterisk, MythTV, VideoLan, etc. So we are often asked, "Why do I need LinuxMCE, can't I just use those other projects by themselves?"</p><br />
<p>LinuxMCE has a lot of it's own software--it's not just a collection of other projects. In fact, LinuxMCE's own software is bigger than most of the key outside projects combined. LinuxMCE includes it's own messaging platform. Most of the logic and functionality, such as how to handle home security, media, etc., is in LinuxMCE's plug-in's--not the other projects. Plus LinuxMCE includes a GUI that runs on Linux, Windows, Windows CE and Symbian. There are already thousands of DCE Devices for various smart home components. And LinuxMCE includes lots of development tools, like the GUI Designer, code generators like DCEGen and sql2cpp. There are also some fairly substantial stand-alone projects with LinuxMCE, like sqlCVS. sqlCVS has essentially all the same features as CVS or SVN, but it works with databases--not source code. It is what ensures that when one user translates a screen on the GUI, or learns an infrared code, or creates a new GSD device, that this is committed to a central repository, reviewed by our staff, then propagated to all other users.</p><br />
<p>Additionally LinuxMCE has it's own "wrappers" for all the outside open source projects we integrate. This is what allows them to work together seamlessly.</p><br />
<p><b>Example #1: LinuxMCE's wrappers allow open source projects to be interchangeable modules.</b> For example, on one media director un-check the box for the 'Xine' media player, but leave 'VideoLan' checked. Do the opposite for another media director. And for the rest, leave both checked (the default). Now start watching a movie in 1 room. As you move from room to room the movie will seamlessly move from Xine to VideoLan and back. If you leave both checked, Xine will be used when the movie is playing in 1 room only, and VideoLan when it is playing in multiple rooms. This interoperability is not possible outside of LinuxMCE.</p><br />
<p><b>Example #2: LinuxMCE allows a bunch of disparate projects to work together as a seamless whole</b> For example, if there's a security breach in your house, the lights and TV's in the house come on automatically using our home automation DCE device interfaces, and the security pin pad appears on all the Windows webpads and PDA's. After 30 seconds a menacing video plays for the burglar using Xine, while the surveillance cameras monitored by Motion feed a live video to your mobile phone over GPRS. Hit 'Talk' on the phone and Xine suspends, passing control to Linphone which makes a call using Asterisk to your mobile phone with the audio piped through the stereo so you can shout at the intruder and let him know you're watching him from a remote location and calling. To the end-user, it works seamlessly, like 1 cohesive whole, but in reality, what LinuxMCE did is enable a bunch of existing applications to work together.</p><br />
===Which hardware is known to work?===<br />
See the [[:Category:Hardware|Hardware category]].<br />
===Is LinuxMCE a distribution or a package?===<br />
Strictly speaking LinuxMCE is a package. A very big package. The distribution it runs on is standard Kubuntu Linux.<br />
<br />
Only the PC running as the Core is required to run Kubuntu and use the LinuxMCE package.<br />
<br />
Any PC used as a Media Director can [[netboot]] from the Core, without the requirement for an OS at all. Of course, you can always boot whatever OS is already stored on the hard drive of each Media Director PC and use that PC separately from the LinuxMCE system. Play the games (or whatever) that are stored on the hard drive (using whichever OS is already installed there) there, and when you're ready to use that PC as a Media Director again, you just go back to netbooting from the Core.<br />
<br />
For the Core, you should use Kubuntu and our packages.<br />
<br />
LinuxMCE is based on the standard Kubuntu Linux distribution. While you could try to run LinuxMCE on another distribution, it's not recommended. LinuxMCE has lots of scripts and utilities to facilitate various tasks. Plus, LinuxMCE embeds many other open source projects, like Xine, Asterisk, etc., with our own "wrappers" that allows them to work together seamlessly. These wrappers are only tested against the versions we maintain in our Ubuntu mirror.<br />
<br />
Before we upgrade anything on our mirror, we thoroughly test the new packages in our system to be sure it still works.<br />
<br />
We didn't take any modules away from the Kubuntu distribution, we only added some. You can still use your Core as a normal Kubuntu Linux PC. In fact, our additions can be bypassed if they get in your way, as is explained below. But in general, DCERouter and other devices, like the home automation modules, all run in the background and won't interfere in screen sessions.<br />
<br />
''Here's what we changed:''<br />
<br />
====Configuration scripts====<br />
LinuxMCE includes a lot of scripts that automate all aspects of maintaining a Linux system. For example, when you add a new user from the LinuxMCE Admin site, it automatically creates a new media directory, exports a samba share, creates an email and voicemail accounts, and so on. There's also scripts to do lots of low-level things like setup ip network prioritizing, so your VOIP calls are always clear. By default, LinuxMCE overwrites and re-creates many Linux config files at each boot. In this regard LinuxMCE acts like a black box appliance. However, once you install LinuxMCE you can go to the [[LinuxMCE Admin Website]]-->Advanced-->Boot Scripts and disable any or all of these scripts. Then you can still maintain your LinuxMCE Core like any other Linux PC and it won't overwrite your config files.<br />
<br />
====Our Ubuntu mirror====<br />
We maintain our own mirror based on Ubuntu. The reason is that we have "wrappers" for many open source projects like Xine, Asterisk, etc., allowing them to work together seamlessly. Whenever updates are posted to Ubuntu's repository, we test the new versions to be sure the changes did not break anything in our wrappers and that the auto-configuration scripts still work. In very rare cases, we need to make our own version of a package that replaces the one in Ubuntu. We avoid that whenever possible, and instead re-work our wrappers so that we can stay current with the "stock" version. Such changes are generally trivial, and you should see no difference between LinuxMCE's Ubuntu mirror and the official one.<br />
<br />
====Window manager====<br />
The Media Directors use our own modified version of the Ratpoison window manager. All applications appear as full-screen, with no borders. Our Orbiter GUI becomes the XWindows desktop. This is the desired behavior in an appliance-like set-top box; we completely isolate the user from anything computer-like. However, you will likely not want this as your main desktop. It is possible to run 2 versions of X on separate terminals: one with LinuxMCE's window manager, and the other with your own preferred choice of desktop.<br />
<br />
====Software Module Overview====<br />
<br />
[[Overview of the software modules]]<br />
<br />
===Ok, I'm sold - what do I need to run LinuxMCE?===<br />
LinuxMCE components include:<br />
*'''''The Core''''' - The computer that acts as the "server" for LinuxMCE. It is responsible for coordinating all the other components and managing your network. This system '''REQUIRES TWO NETWORK CARDS'''. Read the next question for an explanation.<br />
*'''''Media Directors''''' - The computers that are connected to your TV's and allow you to view your media. The Core can also act as a Media Director; thid configuration is called a '''''Hybrid'''''. Any system that is to be used as a Media Director should have '''an nVidia graphics card, 6200 or better'''. Read the question after the next for an explanation.<br />
*'''''Orbiters''''' - Small devices used as advanced remote controls. Some possible devices include:<br />
**Bluetooth mobile phones (with OBEX capabilities)<br />
**Nokia Internet tablets (N770/800/810)<br />
**Windows PCs<br />
**Any device with a web browser<br />
<br />
You must have exactly one Core. You may have as many Media Directors and Orbiters as you please. For a more detailed explanation, including hardware recommendations, see [[User_Manual#Hardware|this section]] of the User Manual.<br />
<br />
You will also need additional hardware for certain functionality. Here are some examples:<br />
*Recording/Watching TV - PCI or Ethernet based TV tuner<br />
*Security - Sensors, device to connect sensors to the system, IP-cameras<br />
*Home control and automation - Home automation computer adapter, control system compatible devices (switches, thermostats, etc)<br />
*A/V equipment control - IR Transceiver, RS-232 cabling<br />
*Telecommunication - VoIP provider, VoIP phones (or at least some microphones attached to Media Directors)<br />
<br />
You don't have to buy everything at once - you can expand your system as you please.<br />
<br />
===Why do I need 2 network cards in my Core?===<br />
LinuxMCE is built to automate as many tasks as possible. In order to do this, it monitors new connections to your network. This allows LinuxMCE to immediately react and automatically configure new networked hardware. This includes setting up VoIP phones and adding media from other systems or Network Attached Storage (NAS) devices. <br />
<br />
The LMCE or "internal" network hosts all of your LMCE devices and media sources, and is connected to the "internal" or second NIC on your core server. The first or "external" NIC can simply connect to your existing network. You can keep any existing routers and DHCP servers you wish on your "external" existing home network. The LMCE core server will connect to that network via the external NIC, and if configured that way, will receive a DHCP lease IP address like any other device. Thus your LMCE core server effectively sits between your "external" and "internal" networks using NICs 1 and 2 respectively.<br />
<br />
But note - anything on your existing network that you want to interact with LMCE, such as NAS devices, wireless APs, PCs that may contain media, VoIP phones, ethernet based security or home automation equipment, should be moved onto the LMCE internal network. From that point it will provide DHCP services and Internet routeing to those devices.<br />
<br />
For that reason, it is important not to put any DHCP servers on your internal network. LMCE must provide that. Any existing DHCP servers on your external network are perfectly fine and can remain, as these do not effect the internal network.<br />
<br />
Ideally, you will eventually (or immediately) move all your devices onto the LMCE internal network, for simplicity. This is highly recommended. This would leave your external network as nothing but a simple link from the core's external NIC to your Internet connection device. <br />
<br />
Some (most?) people have an ADSL modem that also provides routeing functionality - thus your LMCE core will route all Internet bound traffic to this modem, and it will route the traffic on to your ISP. <br />
<br />
Others use broadband modems as a "bridge", typically with a PPPoE dialer, and bridge their public IP address directly to the LMCE core server - thus the core is effectively directly on the Internet and performs all the routing to your ISP itself. This approach is equally valid as the core has a full firewall making it secure. This configuration can be a little trickier to set up, but has the advantage of making VoIP setup much easier.<br />
<br />
Still others have both an ADSL/cable modem and a separate router device on the external network. The LMCE core server routes to the router device, and it routes either to or through the broadband device to your ISP. Again, this is valid, but often unnecessarily complicated.<br />
<br />
===Why does LinuxMCE Require nVidia graphics cards? Why can't I use my ATI card?===<br />
Any system that is going to be used as a Media Director (including a hybrid Core) should have an nVidia graphics card, 6200 or better. This is technically not a requirement, but it is a very strong suggestion. Here's why:<br />
<br />
*ATI's Linux drivers do not properly support all the features LinuxMCE needs to run the graphical overlay<br />
*Because the drivers don't support LinuxMCE's feature set, we haven't done enough refinement of the ATI device templates to make it work without lots of manual intervention<br />
*Even with proper setup - which takes an extreme amount of effort - the results are not all that good.<br />
<br />
The bottom line, nVidia has better support in Linux than ATI, allowing LinuxMCE to do a lot more stuff. Using an nVidia card will save a lot of manual configuration and give a better user experience. For these reasons, LinuxMCE only recommends nVidia cards.<br />
<br />
''LinuxMCE developers will NOT help you configure graphics cards that do not meet this requirement. You are more than welcome to use other hardware, but do so at your own risk.''<br />
<br />
For more information see [[Display Drivers]].<br />
<br />
===How do I install LinuxMCE?===<br />
There are two ways to install LinuxMCE. Both are detailed in the [[Installation Guide]], here's a short summary of each. '''Be sure to read the [[Installation Guide]] in its entirety''' before installing LinuxMCE - it contains '''very important''' information.<br />
<br />
No matter which you choose, it's important to realize that LinuxMCE is not a Linux distribution - it's actually built upon Kubuntu. The most recent version of LinuxMCE is 7.10, which installs on top of Kubuntu 7.10. Do not attempt to install LinuxMCE 7.10 on Kubuntu 8.04 - it will not work.<br />
====DVD Method====<br />
This method will use the entire hard drive and will setup LinuxMCE with default settings. If you want more control over the installation, use the CD method. Booting from the DVD will start the install process.<br />
<br />
Default settings include:<br />
*Automatically install Kubuntu 7.10<br />
*Use the whole hard drive - wiping anything on it<br />
*Start a DHCP server on boot<br />
<br />
====CD Method====<br />
This is a two step process. First, you must install Kubuntu 7.10. '''Do not apply any Kubuntu updates.''' Doing so may cause issues with the LinuxMCE install. Then, start the CD installation from within Kubuntu (not as a boot disc). Details about this process are in the [[Installation Guide]].<br />
<br />
Additional configuration options include:<br />
*Custom partition setup<br />
*Run installation from ISO images (instead of actual discs)<br />
<br />
==First Boot==<br />
===Nothing came up on my TV! What's wrong?===<br />
Probably nothing serious. See [[AVWizard#What_to_do_if_A.2FV_Wizard_does_not_start|this page]].<br />
===My Network Card Doesn't Work! Now What?===<br />
There are some devices that don't work out of the box. [[Unrecognized_NIC|This page]] has more information on getting NICs to work.<br />
===How do I login to a LinuxMCE system?===<br />
In order to do certain things - like system configuration, or general computing - you will need to provide login information. See [[Logging_In]] for details.<br />
===How do I configure LinuxMCE?===<br />
Much of the initial configuration is handled in the installation. The remaining system setup is handled by the [[AVWizard|A/V Wizard]], which automatically launches on the first boot.<br />
<br />
For additional configuration options, see the [[LinuxMCE Admin Website]] (http://dcerouter/ or http://192.168.80.1/) or re-run the A/V Wizard.<br />
<br />
==General Information==<br />
===How are media files organized?===<br />
====General use====<br />
<p>For windows users, you can access the files on the core in Windows explorer's network neighborhood, or by choosing 'Start' 'Run' and typing \\ plus the ip of your core. You will need to login with your user-name and password; it's the same one you use with LinuxMCE Admin. You will see 2 folders: 'public' and 'john', assuming your name is 'John'. Any files that you want everyone in the House to have access to go into the public folder. The folder with your name, John in this case, is your private folder where you can put files that only that only you will have access to. Often times when you choose to save media using the orbiter it will ask you if you want the media to be public or private. If you choose public the media will be saved under the public folder, and if you choose private it will be saved under the private folder with your name. Within those folders you will find some folders called: 'music' (where all ripped cd's go), 'movies' (where all ripped DVD's go), 'videos' (where videos recorded from tv or camcorders go), pictures (where your pictures go), and 'documents' (where your documents go). When you go to play some media in the orbiter by choosing the buttons music, movies, videos, pictures or documents, you will see combined together all the media from the family's public folder as well as the media from your own personal private folder.</p><br />
<br />
<p>So, for example, if you rip a CD 'Madonna' and make it public, and rip a CD 'Rolling Stones' and make it private, and your spouse rips a CD 'Fleetwood Mac' and makes it private, then when you touch music on the orbiter you will see 'Madonna' and 'Rolling Stones', and when your spouse touches music your spouse will see 'Fleetwood Mac' and 'Madonna'. Assuming your name is john and your spouse is susan, then if you browse the network share, you will find 'Madonna' in the folder public\music and you will find 'Rolling Stones' in the folder john\music. If, in LinuxMCE admin your user has 'can modify configuration' checked, then that means you are also able to browse everybody else's private folders too. So in addition to 'public' and 'john', you will also see a folder 'susan', which contains 'music' which contains 'Fleetwood Mac'. If that option is not checked for Susan, then she will only see the folder 'public' and 'susan' and will not see your private folder 'john'.</p><br />
<br />
<p>Note that even if you check that option giving yourself access to everyone's private folders, when you go to browse media on the orbiter you will still only see public files plus your own private files, just so you're not bothered with everyone else's.</p><br />
<br />
<p>To maintain the media files, including copying deleting and renaming, you can either use another PC and a network share, such as a Windows PC with Windows Explorer, or in the LinuxMCE admin web site you can choose Media & Files, Browse.</p><br />
<br />
<p>Note that LinuxMCE maintains an internal database of all your media, including various attributes such as the actors in a movie or the composer of a song. This makes searching very comfortable. For example if you touch the music button, then start typing, you will see all attributes. For example after you touch 'G', you may see 'Geffen Studios (studio)', 'Get You Back (song)', 'GNR Live (album)', and 'Guns N Roses (performer)'. You can continue typing to narrow your entries down further, and touch any entry then 'view' to see all the music that matches. The resulting screen even does cross matching and shows pictures for each attribute.</p><br />
<br />
<p>When you rip media within LinuxMCE the attributes are created automatically. You can view attributes or change them in the LinuxMCE admin site. LinuxMCE also monitors any media that you may add or change outside of LinuxMCE, such as using Windows Explorer. For example if you copy files over in Windows Explorer, LinuxMCE will automatically scan the files and add the attributes to its internal database so you can still search. Also if you rename or delete files, LinuxMCE will automatically update your database accordingly.</p><br />
<br />
<p>If you add a plug-and-play network attached storage device, within each media folder you will see a subfolder for that device and you will be able to move files to and from it.</p><br />
<br />
====Technical explanation====<br />
<p>The public directory maps to /home/public/data, and each user's private directory maps to /home/user_xxxx/data, where xxxx is the internal user ID. The name 'john' is a symlinc to user_xxxx for convenience. The program /usr/pluto/bin/UpdateMedia uses INotify to monitor all /home/public/data and /home/user_xxxx/data folders, so it can rescan whenever the directory is changed. All attributes are stored in the MySql database pluto_media. Each file is a record in the 'File' table. UpdateMedia creates an extended attribute called 'ID' for each file with the primary key of each file. That way if you move or rename a file UpdateMedia will see the extended attribute and your attributes will not be lost--it just updates the database. If you want to add more storage you can map drives under those directories. For example, if you have another 2TB drive array that you want to use for both public music and your private movies, create 2 directories on that array, let's say: public_music and john_movies. Using a network mount, or a symlinc to a network mount, create a folder such as /home/public/data/music/my_2TB_nas that maps to public_music and /home/user_xxxx/data/movies/my_2TB_nas that maps to john_movies. Then when you browse music or movies in the orbiter you will see a folder 'my_2TB_nas' to access the files on that new drive. When you add a plug-and-play network attached storage, LinuxMCE automatically adds a folder within every single directory, such as /home/public/data/music/new_nas, /home/public/data/movies/new_nas, /home/user_xxxx/data/videos/new_nas, and these are automatically mapped to corresponding folders on the NAS. This makes it very easy for a novice to just plug in a NAS and immediately use it without any technical knowledge. However if you want to change this behavior, just remove the symlincs our plug and play script created.</p><br />
<br />
===What are scenarios?===<br />
[[Scenarios]] (aka activities) are the buttons that appear on the main menu of every controller, such as Web pads, PDAs, mobile phones, and Media Director PCs. They trigger any number of actions which can include anything from changing lighting to starting media playback to changing climate settings. Scenarios are specific to rooms. A scenario can affect any device anywhere in the house, but certain scenarios will only be displayed in certain rooms. This is so that when you are in a particular room, you will only see the scenarios that you are likely to use from that room.<br />
See [[What_scenarios_are_created_automatically?|this page]] to learn about what scenarios are created automatically.<br />
===Does LinuxMCE support encrypted DVD's?===<br />
The short answer: yes - if it is legal in your area. You will have to add optional software to enable the features. See [[Encrypted_DVD's| this page]] for more information.<br />
===How can I use additional mouse buttons for LinuxMCE?===<br />
See [[Use_Additional_Mouse_Buttons|this page]]<br />
===How should I format additional hard drives?===<br />
From "blog gelusi: Linux Tuning Guide" (http://gelusi.blogspot.com/2008/02/linux-tuning-guide.html)<br />
<br />
1. Filesystem<br />
Block sizes<br />
<br />
For filesystems dedicated to serving fairly large files, adopting a larger than default 1024 byte block size may yield significant<br />
performance gains.<br />
<br />
Recent transactions on the linux kernel list suggest that setting the block sizein an ext2 file system to 4096 instead of the <br />
default 1024 will result in less file fragmentation, faster fsck's, faster deletes and faster raw read speed, due to the reduced <br />
number of seeks.<br />
<br />
Unfortunately this cannot be changed on the fly. Only a reformat will make this so. The command to format a file system with 4096 <br />
byte blocks is:<br />
<br />
mke2fs -b 4096 /dev/whatever<br />
<br />
Additionally, on any filesystems except those used for logfiles, the default of 5% reserved for root use is excessive for large <br />
file systems, so the command to make the filesystem can be augmented to<br />
<br />
mke2fs -b 4096 -m 1 /dev/whatever<br />
<br />
to set the reserved fraction to 1 percent.<br />
<br />
Then if you want a journaling (ext3) filesystem:<br />
<br />
mke2fs -b 4096 -m 1 -j /dev/whatever<br />
<br />
Note, no further configuration should be necessary as new drives will be auto-discovered.<br />
<br />
==Fixing Problems==<br />
===What if I forget my web admin password?===<br />
[[Reset_the_password_for_the_LinuxMCE_Admin_site|See this article]]<br />
===What if I forget my linuxmce/upgrade account password?===<br />
[[Resetting_Account_Passwords|See this article]]<br />
===I can't access my media files over the network!===<br />
[[I can't access my media files over the network|See this article]].<br />
===What if you don't have a driver for my home automation device?===<br />
[[What if you don't have a driver for my home automation device|See this article]].<br />
===What if my problem isn't listed here?===<br />
It may be listed on the [[Troubleshooting]] page.<br />
<br />
If not, it's time to do some research on your own. [[Main_Page|The LinuxMCE wiki]] is full of information - try using the search feature or browsing categories. See if anyone else has had the same issue by searching on [http://forum.linuxmce.org/ the forum].<br />
<br />
When all else fails, maybe someone else has the answer for you. Try posting on [http://forum.linuxmce.org/ the forum] or our IRC channel (irc.freenode.net #linuxmce).<br />
<br />
Remember, LinuxMCE doesn't have any paid employees, so don't get annoyed if no one gets back to you right away. We're all very busy people who have lives outside of LinuxMCE.</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Frequently_Asked_Questions&diff=15715Frequently Asked Questions2008-09-24T23:15:33Z<p>Colinjones: Corrected the section on 2 NICs and requiring to replace your router - this was nonsense! And gives a bad impression of the system. There are some requirements, but these were not them!</p>
<hr />
<div>[[Category:Documentation]]<br />
This '''frequently asked questions''' (FAQ) section outlines solutions to the most common queries for initial/potential users. See also [[troubleshooting]] for solutions to problems experienced with the system.<br />
==Before Installing LinuxMCE==<br />
===What Does LinuxMCE Do For Me?===<br />
'''LinuxMCE is a whole home automation suite. It includes full featured solutions for:'''<br />
*Media<br />
**Organize media with [[Catalog_media_with_attributes|special metadata tags]]<br />
**View/Listen to media in any room<br />
**Media automatically [[Have_my_media_follow_me|follows you]] through your home<br />
**New media is automatically detected - even if it's on other devices like another computer on your network or Network Attached Storage (NAS)<br />
**Control all your A/V gear through LinuxMCE (using [[Control_regular_A/V_equipment|IR]], [[Control_A/V_equipment_with_RS232/USB/Ethernet|USB, Ethernet, or RS-232]]) including automatically powering everything on and setting the proper inputs on each device<br />
*[[Security]]<br />
**Monitor sensors and [[Have_LinuxMCE_notify_me_of_security_alerts|trigger events]]<br />
**[[Monitor_surveillance_cameras|Monitor security cameras]]<br />
*[[LinuxMCE_telecom_features|Telecomunication]]<br />
**Use VoIP phones anywhere in your home with minimal setup<br />
**Voicemail, call forwarding, advanced caller ID<br />
*Network Management<br />
**Take the place of a standard home router<br />
**Advanced [[Firewall_Rules|firewall]]<br />
**Advanced Quality of Service (QoS) to make sure your bandwidth is used effectively (especially important for VoIP)<br />
**Manage networked storage (such as [[Network_Attached_Storage|NAS devices]]<br />
*[[Automation|Home Control and Automation]]<br />
**Control climate and lighting throughout your entire home<br />
<br />
'''LinuxMCE provides all this functionality by controlling [[:Category:Hardware|all kinds of devices]] throughout the home including:'''<br />
*LinuxMCE [[Core]] Computer<br />
*LinuxMCE [[Media_Directors|Media Director]] Computers<br />
*LinuxMCE [[Orbiters|Orbiters]] (Fancy remotes)<br />
**Nokia [[Nokia 770|770]]/[[Nokia N800|N800/N810]]<br />
**Various PDAs (such as IPAQ 5550 and IPAQ hx2410)<br />
**Various Bluetooth capable mobile phones (including Nokia [[Nokia E65|E65]], [[Nokia N70|N70]], [[Nokia N73|N73]], [[Nokia 6620|6620]], [[Nokia 7650|7650]]) <br />
**The [[Web Orbiter]]<br />
**Various [[:Category:Orbiters|other devices]]<br />
*Networked storage (including [[:Category:Network_Attached_Storage|Network Attached Storage]] (NAS) Devices)<br />
*A/V Equipment (TVs, Receivers, Cable Boxes, etc)<br />
**Using [[:Category:Infrared|Infrared]] (IR)<br />
**Using [[Control_A/V_equipment_with_RS232/USB/Ethernet|RS-232]] (Serial)<br />
**Using [[Control_A/V_equipment_with_RS232/USB/Ethernet|Ethernet]] (Network)<br />
**Using [[Control_A/V_equipment_with_RS232/USB/Ethernet|USB]]<br />
*TV [[:Category:TV_Cards|Capture Devices]]<br />
*Lighting [[:Category:Automation|Automation]]<br />
**Using [[X10_LinuxMCE_Configuration|X10]]<br />
**Using [[:Category:ZWave|Z-Wave]]<br />
**Using [[:Category:Insteon|Insteon]]<br />
**Using [[:Category:Automation|various other protocols]]<br />
**See also: [[Automation]]<br />
*HVAC (Climate Control)[[:Category:Automation|Automation]]<br />
*Security [[:Category:Security|Systems or Individual Sensors]]<br />
*Surveillance [[:Category:Cameras|Cameras]] (IP, Firewire, [[:Category:Video_Capture_Boards|video capture board]], etc)<br />
*VoIP [[:Category:Phones|Phones]] and [[VOIP Service Providers|Service Providers]]<br />
<br />
For more, see [[What can I do with LinuxMCE?]]<br />
<br />
===Is LinuxMCE an appliance or software solution?===<br />
Until now there have been two options for a smarthome+media system:<br />
# Low cost '''software''' based PC solutions, including home automation software like [http://www.homeseer.com HomeSeer], [http://www.premisesystems.com Premise] and [http://www.misterhouse.com Mr. House], also media software like [http://www.microsoft.com/windowsxp/mediacenter/default.mspx Microsoft Windows XP Media Center].<br />
# '''Appliance''' solutions, like [http://www.crestron.com Crestron], [http://www.amx.com AMX], [http://www.kaleidescape.com Kaleidescape] and [http://www.escient.com Escient].<br />
<br />
High-end systems are always appliance based, preferred for their simplicity, reliability and lack of hassle; no worry about missing the football game because your PC-based PVR got a virus. But appliance systems cost a lot &mdash; for one that includes automation, media, telephony, etc., like LinuxMCE. Even though those "appliances" are normally PC's inside special cases, often running Linux plus some proprietary software, you can never get the software separately to build your own &mdash; until now.<br />
<br />
LinuxMCE is an appliance solution. The Core becomes a self-configuring, self-maintaining black box appliance. Since the Core automatically offers a network boot image to any PC's you want to use as media directors, they too become appliances. You can still use them as a PC, of course, but you can crash the hard drive, install a virus, delete system files, and it doesn't matter. When you hit 'LinuxMCE' on the remote control, the Core sends it a network boot, the hard drive turns off, it doesn't use your operating system, and you'll never see a PC prompt. And when you hit the PC button, it goes back to being a PC like normal. LinuxMCE is a 'family friendly' solution--you can use the PC for kernel-level coding, knowing the kids can always hit 1 button and still use it to watch cartoons.<br />
<br />
LinuxMCE offers the best of both worlds: an appliance solution at the price of a software solution, and the the power and versatility of a software solution with the ease of use of an appliance. We offer the software for free as open source because our business is licensing LinuxMCE to hardgoods manufacturers who embed it in their products.<br />
<br />
===What do commercial appliance solutions similar to LinuxMCE cost?===<br />
Appliance solutions are normally quite expensive. The most popular combinations are:<br />
# [http://www.crestron.com Crestron] system to do all the home automation. The cost varies depending on what you want to do with it, but a whole-house solution including touch-screen panels will set you back at least $25,000 for an entry-level system, and can easily hit 6 figures.<br />
# [http://www.kaleidescape.com Kaleidescape] for the DVD movie server, costing $27,000 for the main server, and $4,000 for each TV where you want to watch movies.<br />
# [http://www.escient.com Escient] Fireball for the music server, costing $5,000 for the central music server.<br />
# A PBX phone system with voicemail, like [http://www.panasonic.com Panasonic] will cost another 5 grand or so.<br />
<br />
All of those products require professional installation and setup, particularly the home automation devices. LinuxMCE was designed with simple web-based wizard so even non-techies can get a whole solution up within a few hours. But our competitors' products are different. Smart home dealers will require a trained programmer to set them up. For example, it can take weeks of programming to set up a Crestron system in a good-sized house. Programming fees can be over $10,000, plus re-programing fees every time you make a change. '''Bottom line: around $100,000''' for an appliance solution that does what LinuxMCE does.<br />
<br />
Appliance solutions are typically PCs, running an Linux OS with custom, proprietary software, placed inside custom cases. The software is not available separately, so there's no way to economize or build your own.<br />
<br />
LinuxMCE has taken a different approach. LinuxMCE is also an appliance solution, but we have made the software available separately. In fact, it is free, so techies and software programmers can build their own high-end appliance systems. Competing PC hardware manufacturers can license the LinuxMCE platform to use in standard, low-cost PCs. LinuxMCE brings down the cost by offering all the functionality of several systems in 1 system: whole house media & entertainment, home automation, telecom, security, and personal computer.<br />
<br />
===I've heard LinuxMCE is just a bunch of projects merged together. Is that true? What is special about LinuxMCE?===<br />
<p>LinuxMCE includes a lot of other open source projects, like Xine, Asterisk, MythTV, VideoLan, etc. So we are often asked, "Why do I need LinuxMCE, can't I just use those other projects by themselves?"</p><br />
<p>LinuxMCE has a lot of it's own software--it's not just a collection of other projects. In fact, LinuxMCE's own software is bigger than most of the key outside projects combined. LinuxMCE includes it's own messaging platform. Most of the logic and functionality, such as how to handle home security, media, etc., is in LinuxMCE's plug-in's--not the other projects. Plus LinuxMCE includes a GUI that runs on Linux, Windows, Windows CE and Symbian. There are already thousands of DCE Devices for various smart home components. And LinuxMCE includes lots of development tools, like the GUI Designer, code generators like DCEGen and sql2cpp. There are also some fairly substantial stand-alone projects with LinuxMCE, like sqlCVS. sqlCVS has essentially all the same features as CVS or SVN, but it works with databases--not source code. It is what ensures that when one user translates a screen on the GUI, or learns an infrared code, or creates a new GSD device, that this is committed to a central repository, reviewed by our staff, then propagated to all other users.</p><br />
<p>Additionally LinuxMCE has it's own "wrappers" for all the outside open source projects we integrate. This is what allows them to work together seamlessly.</p><br />
<p><b>Example #1: LinuxMCE's wrappers allow open source projects to be interchangeable modules.</b> For example, on one media director un-check the box for the 'Xine' media player, but leave 'VideoLan' checked. Do the opposite for another media director. And for the rest, leave both checked (the default). Now start watching a movie in 1 room. As you move from room to room the movie will seamlessly move from Xine to VideoLan and back. If you leave both checked, Xine will be used when the movie is playing in 1 room only, and VideoLan when it is playing in multiple rooms. This interoperability is not possible outside of LinuxMCE.</p><br />
<p><b>Example #2: LinuxMCE allows a bunch of disparate projects to work together as a seamless whole</b> For example, if there's a security breach in your house, the lights and TV's in the house come on automatically using our home automation DCE device interfaces, and the security pin pad appears on all the Windows webpads and PDA's. After 30 seconds a menacing video plays for the burglar using Xine, while the surveillance cameras monitored by Motion feed a live video to your mobile phone over GPRS. Hit 'Talk' on the phone and Xine suspends, passing control to Linphone which makes a call using Asterisk to your mobile phone with the audio piped through the stereo so you can shout at the intruder and let him know you're watching him from a remote location and calling. To the end-user, it works seamlessly, like 1 cohesive whole, but in reality, what LinuxMCE did is enable a bunch of existing applications to work together.</p><br />
===Which hardware is known to work?===<br />
See the [[:Category:Hardware|Hardware category]].<br />
===Is LinuxMCE a distribution or a package?===<br />
Strictly speaking LinuxMCE is a package. A very big package. The distribution it runs on is standard Kubuntu Linux.<br />
<br />
Only the PC running as the Core is required to run Kubuntu and use the LinuxMCE package.<br />
<br />
Any PC used as a Media Director can [[netboot]] from the Core, without the requirement for an OS at all. Of course, you can always boot whatever OS is already stored on the hard drive of each Media Director PC and use that PC separately from the LinuxMCE system. Play the games (or whatever) that are stored on the hard drive (using whichever OS is already installed there) there, and when you're ready to use that PC as a Media Director again, you just go back to netbooting from the Core.<br />
<br />
For the Core, you should use Kubuntu and our packages.<br />
<br />
LinuxMCE is based on the standard Kubuntu Linux distribution. While you could try to run LinuxMCE on another distribution, it's not recommended. LinuxMCE has lots of scripts and utilities to facilitate various tasks. Plus, LinuxMCE embeds many other open source projects, like Xine, Asterisk, etc., with our own "wrappers" that allows them to work together seamlessly. These wrappers are only tested against the versions we maintain in our Ubuntu mirror.<br />
<br />
Before we upgrade anything on our mirror, we thoroughly test the new packages in our system to be sure it still works.<br />
<br />
We didn't take any modules away from the Kubuntu distribution, we only added some. You can still use your Core as a normal Kubuntu Linux PC. In fact, our additions can be bypassed if they get in your way, as is explained below. But in general, DCERouter and other devices, like the home automation modules, all run in the background and won't interfere in screen sessions.<br />
<br />
''Here's what we changed:''<br />
<br />
====Configuration scripts====<br />
LinuxMCE includes a lot of scripts that automate all aspects of maintaining a Linux system. For example, when you add a new user from the LinuxMCE Admin site, it automatically creates a new media directory, exports a samba share, creates an email and voicemail accounts, and so on. There's also scripts to do lots of low-level things like setup ip network prioritizing, so your VOIP calls are always clear. By default, LinuxMCE overwrites and re-creates many Linux config files at each boot. In this regard LinuxMCE acts like a black box appliance. However, once you install LinuxMCE you can go to the [[LinuxMCE Admin Website]]-->Advanced-->Boot Scripts and disable any or all of these scripts. Then you can still maintain your LinuxMCE Core like any other Linux PC and it won't overwrite your config files.<br />
<br />
====Our Ubuntu mirror====<br />
We maintain our own mirror based on Ubuntu. The reason is that we have "wrappers" for many open source projects like Xine, Asterisk, etc., allowing them to work together seamlessly. Whenever updates are posted to Ubuntu's repository, we test the new versions to be sure the changes did not break anything in our wrappers and that the auto-configuration scripts still work. In very rare cases, we need to make our own version of a package that replaces the one in Ubuntu. We avoid that whenever possible, and instead re-work our wrappers so that we can stay current with the "stock" version. Such changes are generally trivial, and you should see no difference between LinuxMCE's Ubuntu mirror and the official one.<br />
<br />
====Window manager====<br />
The Media Directors use our own modified version of the Ratpoison window manager. All applications appear as full-screen, with no borders. Our Orbiter GUI becomes the XWindows desktop. This is the desired behavior in an appliance-like set-top box; we completely isolate the user from anything computer-like. However, you will likely not want this as your main desktop. It is possible to run 2 versions of X on separate terminals: one with LinuxMCE's window manager, and the other with your own preferred choice of desktop.<br />
<br />
====Software Module Overview====<br />
<br />
[[Overview of the software modules]]<br />
<br />
===Ok, I'm sold - what do I need to run LinuxMCE?===<br />
LinuxMCE components include:<br />
*'''''The Core''''' - The computer that acts as the "server" for LinuxMCE. It is responsible for coordinating all the other components and managing your network. This system '''REQUIRES TWO NETWORK CARDS'''. Read the next question for an explanation.<br />
*'''''Media Directors''''' - The computers that are connected to your TV's and allow you to view your media. The Core can also act as a Media Director; thid configuration is called a '''''Hybrid'''''. Any system that is to be used as a Media Director should have '''an nVidia graphics card, 6200 or better'''. Read the question after the next for an explanation.<br />
*'''''Orbiters''''' - Small devices used as advanced remote controls. Some possible devices include:<br />
**Bluetooth mobile phones (with OBEX capabilities)<br />
**Nokia Internet tablets (N770/800/810)<br />
**Windows PCs<br />
**Any device with a web browser<br />
<br />
You must have exactly one Core. You may have as many Media Directors and Orbiters as you please. For a more detailed explanation, including hardware recommendations, see [[User_Manual#Hardware|this section]] of the User Manual.<br />
<br />
You will also need additional hardware for certain functionality. Here are some examples:<br />
*Recording/Watching TV - PCI or Ethernet based TV tuner<br />
*Security - Sensors, device to connect sensors to the system, IP-cameras<br />
*Home control and automation - Home automation computer adapter, control system compatible devices (switches, thermostats, etc)<br />
*A/V equipment control - IR Transceiver, RS-232 cabling<br />
*Telecommunication - VoIP provider, VoIP phones (or at least some microphones attached to Media Directors)<br />
<br />
You don't have to buy everything at once - you can expand your system as you please.<br />
<br />
===Why do I need 2 network cards in my Core?===<br />
LinuxMCE is built to automate as many tasks as possible. In order to do this, it monitors new connections to your network. This allows LinuxMCE to immediately react and automatically configure new networked hardware. This includes setting up VoIP phones and adding media from other systems or Network Attached Storage (NAS) devices. <br />
<br />
The LMCE or "internal" network hosts all of your LMCE devices and media sources, and is connected to the "internal" or second NIC on your core server. The first or "external" NIC can simply connect to your existing network. You can keep any existing routers and DHCP servers you wish on your "external" existing home network. The LMCE core server will connect to that network via the external NIC, and if configured that way, will receive a DHCP lease IP address like any other device.<br />
<br />
But note - anything on your existing network that you want to interact with LMCE, such as NAS devices, wireless APs, PCs that may contain media, VoIP phones, ethernet based security or home automation equipment, should be moved onto the LMCE internal network. From that point it will provide DHCP services and Internet routeing to those devices.<br />
<br />
For that reason, it is important not to put any DHCP servers on your internal network. LMCE must provide that. Any existing DHCP servers on your external network are perfectly fine and can remain, as these do not effect the internal network.<br />
<br />
Ideally, you will eventually (or immediately) move all your devices onto the LMCE internal network, for simplicity. This is highly recommended. This would leave your external network as nothing but a simple link from the core's external NIC to your Internet connection device. <br />
<br />
Some (most?) people have an ADSL modem that also provides routeing functionality - thus your LMCE core will route all Internet bound traffic to this modem, and it will route the traffic on to your ISP. <br />
<br />
Others use broadband modems as a "bridge", typically with a PPPoE dialer, and bridge their public IP address directly to the LMCE core server - thus the core is effectively directly on the Internet and performs all the routing to your ISP itself. This approach is equally valid as the core has a full firewall making it secure. This configuration can be a little trickier to set up, but has the advantage of making VoIP setup much easier.<br />
<br />
Still others have both an ADSL/cable modem and a separate router device on the external network. The LMCE core server routes to the router device, and it routes either to or through the broadband device to your ISP. Again, this is valid, but often unnecessarily complicated.<br />
<br />
===Why does LinuxMCE Require nVidia graphics cards? Why can't I use my ATI card?===<br />
Any system that is going to be used as a Media Director (including a hybrid Core) should have an nVidia graphics card, 6200 or better. This is technically not a requirement, but it is a very strong suggestion. Here's why:<br />
<br />
*ATI's Linux drivers do not properly support all the features LinuxMCE needs to run the graphical overlay<br />
*Because the drivers don't support LinuxMCE's feature set, we haven't done enough refinement of the ATI device templates to make it work without lots of manual intervention<br />
*Even with proper setup - which takes an extreme amount of effort - the results are not all that good.<br />
<br />
The bottom line, nVidia has better support in Linux than ATI, allowing LinuxMCE to do a lot more stuff. Using an nVidia card will save a lot of manual configuration and give a better user experience. For these reasons, LinuxMCE only recommends nVidia cards.<br />
<br />
''LinuxMCE developers will NOT help you configure graphics cards that do not meet this requirement. You are more than welcome to use other hardware, but do so at your own risk.''<br />
<br />
For more information see [[Display Drivers]].<br />
<br />
===How do I install LinuxMCE?===<br />
There are two ways to install LinuxMCE. Both are detailed in the [[Installation Guide]], here's a short summary of each. '''Be sure to read the [[Installation Guide]] in its entirety''' before installing LinuxMCE - it contains '''very important''' information.<br />
<br />
No matter which you choose, it's important to realize that LinuxMCE is not a Linux distribution - it's actually built upon Kubuntu. The most recent version of LinuxMCE is 7.10, which installs on top of Kubuntu 7.10. Do not attempt to install LinuxMCE 7.10 on Kubuntu 8.04 - it will not work.<br />
====DVD Method====<br />
This method will use the entire hard drive and will setup LinuxMCE with default settings. If you want more control over the installation, use the CD method. Booting from the DVD will start the install process.<br />
<br />
Default settings include:<br />
*Automatically install Kubuntu 7.10<br />
*Use the whole hard drive - wiping anything on it<br />
*Start a DHCP server on boot<br />
<br />
====CD Method====<br />
This is a two step process. First, you must install Kubuntu 7.10. '''Do not apply any Kubuntu updates.''' Doing so may cause issues with the LinuxMCE install. Then, start the CD installation from within Kubuntu (not as a boot disc). Details about this process are in the [[Installation Guide]].<br />
<br />
Additional configuration options include:<br />
*Custom partition setup<br />
*Run installation from ISO images (instead of actual discs)<br />
<br />
==First Boot==<br />
===Nothing came up on my TV! What's wrong?===<br />
Probably nothing serious. See [[AVWizard#What_to_do_if_A.2FV_Wizard_does_not_start|this page]].<br />
===My Network Card Doesn't Work! Now What?===<br />
There are some devices that don't work out of the box. [[Unrecognized_NIC|This page]] has more information on getting NICs to work.<br />
===How do I login to a LinuxMCE system?===<br />
In order to do certain things - like system configuration, or general computing - you will need to provide login information. See [[Logging_In]] for details.<br />
===How do I configure LinuxMCE?===<br />
Much of the initial configuration is handled in the installation. The remaining system setup is handled by the [[AVWizard|A/V Wizard]], which automatically launches on the first boot.<br />
<br />
For additional configuration options, see the [[LinuxMCE Admin Website]] (http://dcerouter/ or http://192.168.80.1/) or re-run the A/V Wizard.<br />
<br />
==General Information==<br />
===How are media files organized?===<br />
====General use====<br />
<p>For windows users, you can access the files on the core in Windows explorer's network neighborhood, or by choosing 'Start' 'Run' and typing \\ plus the ip of your core. You will need to login with your user-name and password; it's the same one you use with LinuxMCE Admin. You will see 2 folders: 'public' and 'john', assuming your name is 'John'. Any files that you want everyone in the House to have access to go into the public folder. The folder with your name, John in this case, is your private folder where you can put files that only that only you will have access to. Often times when you choose to save media using the orbiter it will ask you if you want the media to be public or private. If you choose public the media will be saved under the public folder, and if you choose private it will be saved under the private folder with your name. Within those folders you will find some folders called: 'music' (where all ripped cd's go), 'movies' (where all ripped DVD's go), 'videos' (where videos recorded from tv or camcorders go), pictures (where your pictures go), and 'documents' (where your documents go). When you go to play some media in the orbiter by choosing the buttons music, movies, videos, pictures or documents, you will see combined together all the media from the family's public folder as well as the media from your own personal private folder.</p><br />
<br />
<p>So, for example, if you rip a CD 'Madonna' and make it public, and rip a CD 'Rolling Stones' and make it private, and your spouse rips a CD 'Fleetwood Mac' and makes it private, then when you touch music on the orbiter you will see 'Madonna' and 'Rolling Stones', and when your spouse touches music your spouse will see 'Fleetwood Mac' and 'Madonna'. Assuming your name is john and your spouse is susan, then if you browse the network share, you will find 'Madonna' in the folder public\music and you will find 'Rolling Stones' in the folder john\music. If, in LinuxMCE admin your user has 'can modify configuration' checked, then that means you are also able to browse everybody else's private folders too. So in addition to 'public' and 'john', you will also see a folder 'susan', which contains 'music' which contains 'Fleetwood Mac'. If that option is not checked for Susan, then she will only see the folder 'public' and 'susan' and will not see your private folder 'john'.</p><br />
<br />
<p>Note that even if you check that option giving yourself access to everyone's private folders, when you go to browse media on the orbiter you will still only see public files plus your own private files, just so you're not bothered with everyone else's.</p><br />
<br />
<p>To maintain the media files, including copying deleting and renaming, you can either use another PC and a network share, such as a Windows PC with Windows Explorer, or in the LinuxMCE admin web site you can choose Media & Files, Browse.</p><br />
<br />
<p>Note that LinuxMCE maintains an internal database of all your media, including various attributes such as the actors in a movie or the composer of a song. This makes searching very comfortable. For example if you touch the music button, then start typing, you will see all attributes. For example after you touch 'G', you may see 'Geffen Studios (studio)', 'Get You Back (song)', 'GNR Live (album)', and 'Guns N Roses (performer)'. You can continue typing to narrow your entries down further, and touch any entry then 'view' to see all the music that matches. The resulting screen even does cross matching and shows pictures for each attribute.</p><br />
<br />
<p>When you rip media within LinuxMCE the attributes are created automatically. You can view attributes or change them in the LinuxMCE admin site. LinuxMCE also monitors any media that you may add or change outside of LinuxMCE, such as using Windows Explorer. For example if you copy files over in Windows Explorer, LinuxMCE will automatically scan the files and add the attributes to its internal database so you can still search. Also if you rename or delete files, LinuxMCE will automatically update your database accordingly.</p><br />
<br />
<p>If you add a plug-and-play network attached storage device, within each media folder you will see a subfolder for that device and you will be able to move files to and from it.</p><br />
<br />
====Technical explanation====<br />
<p>The public directory maps to /home/public/data, and each user's private directory maps to /home/user_xxxx/data, where xxxx is the internal user ID. The name 'john' is a symlinc to user_xxxx for convenience. The program /usr/pluto/bin/UpdateMedia uses INotify to monitor all /home/public/data and /home/user_xxxx/data folders, so it can rescan whenever the directory is changed. All attributes are stored in the MySql database pluto_media. Each file is a record in the 'File' table. UpdateMedia creates an extended attribute called 'ID' for each file with the primary key of each file. That way if you move or rename a file UpdateMedia will see the extended attribute and your attributes will not be lost--it just updates the database. If you want to add more storage you can map drives under those directories. For example, if you have another 2TB drive array that you want to use for both public music and your private movies, create 2 directories on that array, let's say: public_music and john_movies. Using a network mount, or a symlinc to a network mount, create a folder such as /home/public/data/music/my_2TB_nas that maps to public_music and /home/user_xxxx/data/movies/my_2TB_nas that maps to john_movies. Then when you browse music or movies in the orbiter you will see a folder 'my_2TB_nas' to access the files on that new drive. When you add a plug-and-play network attached storage, LinuxMCE automatically adds a folder within every single directory, such as /home/public/data/music/new_nas, /home/public/data/movies/new_nas, /home/user_xxxx/data/videos/new_nas, and these are automatically mapped to corresponding folders on the NAS. This makes it very easy for a novice to just plug in a NAS and immediately use it without any technical knowledge. However if you want to change this behavior, just remove the symlincs our plug and play script created.</p><br />
<br />
===What are scenarios?===<br />
[[Scenarios]] (aka activities) are the buttons that appear on the main menu of every controller, such as Web pads, PDAs, mobile phones, and Media Director PCs. They trigger any number of actions which can include anything from changing lighting to starting media playback to changing climate settings. Scenarios are specific to rooms. A scenario can affect any device anywhere in the house, but certain scenarios will only be displayed in certain rooms. This is so that when you are in a particular room, you will only see the scenarios that you are likely to use from that room.<br />
See [[What_scenarios_are_created_automatically?|this page]] to learn about what scenarios are created automatically.<br />
===Does LinuxMCE support encrypted DVD's?===<br />
The short answer: yes - if it is legal in your area. You will have to add optional software to enable the features. See [[Encrypted_DVD's| this page]] for more information.<br />
===How can I use additional mouse buttons for LinuxMCE?===<br />
See [[Use_Additional_Mouse_Buttons|this page]]<br />
===How should I format additional hard drives?===<br />
From "blog gelusi: Linux Tuning Guide" (http://gelusi.blogspot.com/2008/02/linux-tuning-guide.html)<br />
<br />
1. Filesystem<br />
Block sizes<br />
<br />
For filesystems dedicated to serving fairly large files, adopting a larger than default 1024 byte block size may yield significant<br />
performance gains.<br />
<br />
Recent transactions on the linux kernel list suggest that setting the block sizein an ext2 file system to 4096 instead of the <br />
default 1024 will result in less file fragmentation, faster fsck's, faster deletes and faster raw read speed, due to the reduced <br />
number of seeks.<br />
<br />
Unfortunately this cannot be changed on the fly. Only a reformat will make this so. The command to format a file system with 4096 <br />
byte blocks is:<br />
<br />
mke2fs -b 4096 /dev/whatever<br />
<br />
Additionally, on any filesystems except those used for logfiles, the default of 5% reserved for root use is excessive for large <br />
file systems, so the command to make the filesystem can be augmented to<br />
<br />
mke2fs -b 4096 -m 1 /dev/whatever<br />
<br />
to set the reserved fraction to 1 percent.<br />
<br />
Then if you want a journaling (ext3) filesystem:<br />
<br />
mke2fs -b 4096 -m 1 -j /dev/whatever<br />
<br />
Note, no further configuration should be necessary as new drives will be auto-discovered.<br />
<br />
==Fixing Problems==<br />
===What if I forget my web admin password?===<br />
[[Reset_the_password_for_the_LinuxMCE_Admin_site|See this article]]<br />
===What if I forget my linuxmce/upgrade account password?===<br />
[[Resetting_Account_Passwords|See this article]]<br />
===I can't access my media files over the network!===<br />
[[I can't access my media files over the network|See this article]].<br />
===What if you don't have a driver for my home automation device?===<br />
[[What if you don't have a driver for my home automation device|See this article]].<br />
===What if my problem isn't listed here?===<br />
It may be listed on the [[Troubleshooting]] page.<br />
<br />
If not, it's time to do some research on your own. [[Main_Page|The LinuxMCE wiki]] is full of information - try using the search feature or browsing categories. See if anyone else has had the same issue by searching on [http://forum.linuxmce.org/ the forum].<br />
<br />
When all else fails, maybe someone else has the answer for you. Try posting on [http://forum.linuxmce.org/ the forum] or our IRC channel (irc.freenode.net #linuxmce).<br />
<br />
Remember, LinuxMCE doesn't have any paid employees, so don't get annoyed if no one gets back to you right away. We're all very busy people who have lives outside of LinuxMCE.</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=AVWizard&diff=15286AVWizard2008-08-16T03:47:59Z<p>Colinjones: /* What to do if A/V Wizard does not start */</p>
<hr />
<div>This page covers the aspects of the AVWizard that the end user will be interested in. If you want to customise the AVWizard for your needs, like writing a separate backend, see [[AVWizard for developers]].<br />
<br />
==Background==<br />
<br />
LinuxMCE is intended to act like a normal consumer A/V device, even though it is PC based. As a result, the process for configuring displays is substantially different from configuring X11 on a normal Linux machine, and the A/V Wizard has been designed to make this process as easy as possible. Please see the [[EDID]] page for more details on the reasons behind the way it has been designed.<br />
<br />
==Starting A/V Wizard==<br />
===Initially===<br />
This wizard is started automatically the very first time the system boots; it does not automatically start after that.<br />
<br />
===Starting A/V Wizard from the LinuxMCE menu===<br />
The A/V wizard can be restarted at any time from the LinuxMCE menu by choosing Advanced--> Advanced--> A/V Wizard.<br />
<br />
===Restarting the AVWizard during bootup===<br />
Alternatively, the AV Wizard can be started during bootup. Either hold down the Shift key on the keyboard, or press the "A/V Menu" button on the remote to make the A/V wizard start. During bootup you should hear a series of escalating beeps to tell you when LinuxMCE is monitoring the Shift (and "A/V Menu") keys. <br />
<br />
When you hear the descending beeps it means that you're too late; the bootup has already gone past the AV Wizard check and LinuxMCE has already started.<br />
<br />
==How A/V Wizard Starts==<br />
When A/V Wizard starts it always outputs 640x480 on the VGA connector. If you are ''not'' using a VGA connector, you will likely see a black screen when the A/V Wizard starts (even if you previously saw the Kubuntu boot splash). You will know that the A/V Wizard is running, however, because you will hear a series of beeps. If you then have video after hearing the beeps, proceed to [[AVWizard_Step_by_Step| complete the A/V Wizard]]. If not, see the next section.<br />
<br />
==What to do if A/V Wizard does not start==<br />
Press the number 1 through 5 on the keyboard (or the remote control) to switch to the active connector. Wait 15 seconds, and you will hear that same sequence of beeps telling you that A/V Wizard has now restarted. If you don't hear the beeps after 15 seconds, press the number for your connector again.<br />
<br />
<pre> Keys for choosing a connector:<br />
<br />
1: DVI<br />
2: VGA<br />
3: Component<br />
4: Composite<br />
5: S-Video</pre><br />
<br />
If you hear the beeps but still don't see a picture, it's possible that the display you're using cannot handle 640x480. Press the number 6-9, or 0, as shown below, to select your resolution. Again, 15 seconds later, you should hear the beeps when the A/V Wizard is restarted. If you again need to choose a connector (other than the default VGA), press the 1-5 key (as above) and wait until you hear the beeps again. Repeat as often as needed.<br />
<br />
<pre><br />
Keys for choosing a resolution:<br />
<br />
6: 640x480<br />
7: 1024x768<br />
8: 720p<br />
9: 1080i<br />
0: 1080p</pre><br />
<br />
(''Note: Due to a bug in the 0704 release, the numeric keys 0-9 on the Windows XP I/R remote may not be able to set your output connector & resolution. Use the 0-9 keys on the keyboard instead, or use another remote.'')<br />
<br />
Once you have a picture you can proceed to complete the A/V Wizard. You can then resize your user interface to fit your screen, choose your audio outputs, and so on. Follow the [[AVWizard Step by Step]] instructions.<br />
<br />
If you have more than one video card, or a video card and an onboard video chipset LMCE might not be using the correct one, and so you will still get a black screen. To use a card rather than your onboard chipset, go into your BIOS and disable the onboard chipset - note some BIOSs cannot disable, they can only set your card as the primary or initial video chipset, if so then do that.<br />
<br />
If you were able to disable the onboard chipset in your BIOS, then you should be ready to run the AV Wizard - the Linux kernel will not even see the onboard chipset, so will select the card for output.<br />
<br />
If you could only set the card as primary (and not disable the onboard chipset) the you will probably notice that you now see the Kubuntu splash screen and progress bar during start up that you didn't see before. However, once you reach the AV Wizard, the screen goes black again - here it is defaulting to your onboard chipset.<br />
<br />
To correct this, reboot and hit Escape during the GRUB boot menu (just after the BIOS self test), and choose the recovery option. Once you get a command line, you can execute the lspci command - this will list all your PCI interfaced devices, including the onboard and card video chipsets. Make a note of the PCI BusID of the card, eg 2:0:0<br />
<br />
Now use a text editor and edit /etc/X11/xorg.conf. In the Device section you will see the PCI BusID specified - this is probably set to your onboard chipset's ID. Change this to the ID you noted above, save the file and reboot.<br />
<br />
==AVWizard steps==<br />
:''See [[AVWizard Step by Step]] for detailed screen-by-screen instructions.''<br />
<br />
AVWizard is an easy 10 step configuration wizard:<br />
<br />
*AV Welcome screen<br />
*AV Resolution and Refresh screen<br />
*AV Video Resolution counter<br />
*AV UI Switcher<br />
*AV Video Output<br />
*AV Audio Connector<br />
*AV Audio Volume<br />
*AV Dolby Test<br />
*AV DTS Test<br />
*AV Final Selections<br />
<br />
<br />
After that an [[Orbiter Generator]] will be launched, to create an [[Orbiter]] (remote control) for that tool.<br />
<br />
==Running A/V Wizard from the Commandline==<br />
If you are having difficulty running the AVWizard normally (by selecting the option in the Orbiter) it can be run manually by typing in the command line. <pre>/usr/pluto/bin/AVWizard_Run.sh</pre> <br />
Note that you should kill X and any process trying to reload it before running the wizard. You should only do this if your attempt to run it normally fails for whatever reason.<br />
Note: I had to use <pre>sudo -s /usr/pluto/bin/AVWizard_Run.sh</pre> to get my AVWizard to restart.<br />
[[Category: Tutorials]]</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=AVWizard&diff=15285AVWizard2008-08-16T03:46:32Z<p>Colinjones: /* What to do if A/V Wizard does not start */ added section about how to change the PCI BusID when you have 2 graphics chipsets and cannot disable one of them</p>
<hr />
<div>This page covers the aspects of the AVWizard that the end user will be interested in. If you want to customise the AVWizard for your needs, like writing a separate backend, see [[AVWizard for developers]].<br />
<br />
==Background==<br />
<br />
LinuxMCE is intended to act like a normal consumer A/V device, even though it is PC based. As a result, the process for configuring displays is substantially different from configuring X11 on a normal Linux machine, and the A/V Wizard has been designed to make this process as easy as possible. Please see the [[EDID]] page for more details on the reasons behind the way it has been designed.<br />
<br />
==Starting A/V Wizard==<br />
===Initially===<br />
This wizard is started automatically the very first time the system boots; it does not automatically start after that.<br />
<br />
===Starting A/V Wizard from the LinuxMCE menu===<br />
The A/V wizard can be restarted at any time from the LinuxMCE menu by choosing Advanced--> Advanced--> A/V Wizard.<br />
<br />
===Restarting the AVWizard during bootup===<br />
Alternatively, the AV Wizard can be started during bootup. Either hold down the Shift key on the keyboard, or press the "A/V Menu" button on the remote to make the A/V wizard start. During bootup you should hear a series of escalating beeps to tell you when LinuxMCE is monitoring the Shift (and "A/V Menu") keys. <br />
<br />
When you hear the descending beeps it means that you're too late; the bootup has already gone past the AV Wizard check and LinuxMCE has already started.<br />
<br />
==How A/V Wizard Starts==<br />
When A/V Wizard starts it always outputs 640x480 on the VGA connector. If you are ''not'' using a VGA connector, you will likely see a black screen when the A/V Wizard starts (even if you previously saw the Kubuntu boot splash). You will know that the A/V Wizard is running, however, because you will hear a series of beeps. If you then have video after hearing the beeps, proceed to [[AVWizard_Step_by_Step| complete the A/V Wizard]]. If not, see the next section.<br />
<br />
==What to do if A/V Wizard does not start==<br />
Press the number 1 through 5 on the keyboard (or the remote control) to switch to the active connector. Wait 15 seconds, and you will hear that same sequence of beeps telling you that A/V Wizard has now restarted. If you don't hear the beeps after 15 seconds, press the number for your connector again.<br />
<br />
<pre> Keys for choosing a connector:<br />
<br />
1: DVI<br />
2: VGA<br />
3: Component<br />
4: Composite<br />
5: S-Video</pre><br />
<br />
If you hear the beeps but still don't see a picture, it's possible that the display you're using cannot handle 640x480. Press the number 6-9, or 0, as shown below, to select your resolution. Again, 15 seconds later, you should hear the beeps when the A/V Wizard is restarted. If you again need to choose a connector (other than the default VGA), press the 1-5 key (as above) and wait until you hear the beeps again. Repeat as often as needed.<br />
<br />
<pre><br />
Keys for choosing a resolution:<br />
<br />
6: 640x480<br />
7: 1024x768<br />
8: 720p<br />
9: 1080i<br />
0: 1080p</pre><br />
<br />
(''Note: Due to a bug in the 0704 release, the numeric keys 0-9 on the Windows XP I/R remote may not be able to set your output connector & resolution. Use the 0-9 keys on the keyboard instead, or use another remote.'')<br />
<br />
Once you have a picture you can proceed to complete the A/V Wizard. You can then resize your user interface to fit your screen, choose your audio outputs, and so on. Follow the [[AVWizard Step by Step]] instructions.<br />
<br />
If you have more than one video card, or a video card and an onboard video chipset LMCE might not be using the correct one, and so you will still get a black screen. To use a card rather than your onboard chipset, go into your BIOS and disable the onboard chipset - note some BIOSs cannot disable, they can only set your card as the primary or initial video chipset, if so then do that.<br />
<br />
If you were able to disable the onboard chipset in your BIOS, then you should be ready to install - the Linux kernel will not even see the onboard chipset, so will select the card for output.<br />
<br />
If you could only set the card as primary (and not disable the onboard chipset) the you will probably notice that you now see the Kubuntu splash screen and progress bar during start up that you didn't see before. However, once you reach the AV Wizard, the screen goes black again - here it is defaulting to your onboard chipset.<br />
<br />
To correct this, reboot and hit Escape during the GRUB boot menu (just after the BIOS self test), and choose the recovery option. Once you get a command line, you can execute the lspci command - this will list all your PCI interfaced devices, including the onboard and card video chipsets. Make a note of the PCI BusID of the card, eg 2:0:0<br />
<br />
Now use a text editor and edit /etc/X11/xorg.conf. In the Device section you will see the PCI BusID specified - this is probably set to your onboard chipset's ID. Change this to the ID you noted above, save the file and reboot.<br />
<br />
==AVWizard steps==<br />
:''See [[AVWizard Step by Step]] for detailed screen-by-screen instructions.''<br />
<br />
AVWizard is an easy 10 step configuration wizard:<br />
<br />
*AV Welcome screen<br />
*AV Resolution and Refresh screen<br />
*AV Video Resolution counter<br />
*AV UI Switcher<br />
*AV Video Output<br />
*AV Audio Connector<br />
*AV Audio Volume<br />
*AV Dolby Test<br />
*AV DTS Test<br />
*AV Final Selections<br />
<br />
<br />
After that an [[Orbiter Generator]] will be launched, to create an [[Orbiter]] (remote control) for that tool.<br />
<br />
==Running A/V Wizard from the Commandline==<br />
If you are having difficulty running the AVWizard normally (by selecting the option in the Orbiter) it can be run manually by typing in the command line. <pre>/usr/pluto/bin/AVWizard_Run.sh</pre> <br />
Note that you should kill X and any process trying to reload it before running the wizard. You should only do this if your attempt to run it normally fails for whatever reason.<br />
Note: I had to use <pre>sudo -s /usr/pluto/bin/AVWizard_Run.sh</pre> to get my AVWizard to restart.<br />
[[Category: Tutorials]]</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Internal_and_External_networks_swapped/not_working&diff=15275Internal and External networks swapped/not working2008-08-16T03:30:55Z<p>Colinjones: /* What to do */ formatting</p>
<hr />
<div>[[Category:Troubleshooting]][[Category:Networking]]<br />
In some circumstances, and usually with particular motherboards/NICs, Linux may not initialise your network cards in a way that makes LMCE easy to get working.<br />
<br />
=How to check if this has happened=<br />
<br />
Use ethtool to determine your NIC names. For LMCE to work smoothly, the External network (typically connected to your existing home network and/or directly to your broadband router) should be called eth0. The Internal network (this is the new, dedicated LMCE network that all your telephony, media, security, Media Directors, Home Automation, etc devices are on) should be called eth1. There are different ways of configuring LMCE, but this is the default and easiest.<br />
<br />
If ethtool shows you have eth0 and eth2, or eth1 and eth2 or even eth0 and eth1 the wrong way around in some circumstances, then you have this problem.<br />
<br />
=What if it is wrong?=<br />
<br />
LMCE will assume that your external network is out of eth0 and internal out of eth1, so it will send traffic in the wrong directions, not plug and play properly, not be able to access your media, disrupt your external network DHCP, etc.<br />
<br />
=What to do=<br />
<br />
If the interface names are simply swapped, you can try swapping the cables around, or using the "swap" option in the web admin. Most of the time, this is all that is wrong.<br />
<br />
If you have a DHCP server enabled on the external network (you should never have one enabled on the internal network, LMCE provides that functionality), you should see in the web admin that the external interface has got an IP address from that server, and the subnet mask, gateway, etc are all configured correctly. On the internal interface LMCE should automatically assign the static IP address of 192.168.80.1. Devices on the internal network should be able freely to get IP addresses from the DHCP server on that interface. If both of these are true, then your core is correctly networked.<br />
<br />
If the names are wrong and the IP addresses are not set up as above then you need to name the interfaces correctly. You can use the ethtool command to flash the LEDs on each card in turn - do this and note precisely the MAC address (also from ethtool) of the interface that is connected to your external network. Do the same for the internal network.<br />
<br />
You can now create a udev rule to force the names.<br />
<br />
I use the text file editor, Joe. Use whichever editor you prefer - to install Joe from a terminal:<br />
<br />
sudo apt-get install joe<br />
<br />
Create a text file called /etc/udev/rules.d/70-persistent-net.rules (or edit it if it already exists):<br />
<br />
sudo joe /etc/udev/rules.d/70-persistent-net.rules<br />
<br />
Now add these 2 lines:<br />
<br />
KERNEL=="eth*", SYSFS{address}=="aa:bb:cc:dd:ee:ff", NAME="eth0"<br />
<br />
KERNEL=="eth*", SYSFS{address}=="aa:bb:cc:dd:ee:ff", NAME="eth1"<br />
<br />
Substitute aa:bb:cc:dd:ee:ff for the appropriate MAC address - the first one is the MAC address you noted for your external network, the second one for your internal network. NOTE: these are case sensitive, and all letters must be lower case.<br />
<br />
If there were already entries in this file, you will need to use your commonsense to determine whether they conflict. If they do, replace those conflicting entries with the ones above.<br />
<br />
Save and exit the file. Now reboot - the udev rules listen to kernel messages, filter them based on whether they are ethernet interface naming events, and then override the names assigned with the correct ones.<br />
<br />
You should now see in the web admin that all the IP addresses are correctly assigned and you can route both internally and externally.</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Internal_and_External_networks_swapped/not_working&diff=15274Internal and External networks swapped/not working2008-08-16T03:28:34Z<p>Colinjones: /* What to do */ grammar</p>
<hr />
<div>[[Category:Troubleshooting]][[Category:Networking]]<br />
In some circumstances, and usually with particular motherboards/NICs, Linux may not initialise your network cards in a way that makes LMCE easy to get working.<br />
<br />
=How to check if this has happened=<br />
<br />
Use ethtool to determine your NIC names. For LMCE to work smoothly, the External network (typically connected to your existing home network and/or directly to your broadband router) should be called eth0. The Internal network (this is the new, dedicated LMCE network that all your telephony, media, security, Media Directors, Home Automation, etc devices are on) should be called eth1. There are different ways of configuring LMCE, but this is the default and easiest.<br />
<br />
If ethtool shows you have eth0 and eth2, or eth1 and eth2 or even eth0 and eth1 the wrong way around in some circumstances, then you have this problem.<br />
<br />
=What if it is wrong?=<br />
<br />
LMCE will assume that your external network is out of eth0 and internal out of eth1, so it will send traffic in the wrong directions, not plug and play properly, not be able to access your media, disrupt your external network DHCP, etc.<br />
<br />
=What to do=<br />
<br />
If the interface names are simply swapped, you can try swapping the cables around, or using the "swap" option in the web admin. Most of the time, this is all that is wrong.<br />
<br />
If you have a DHCP server enabled on the external network (you should never have one enabled on the internal network, LMCE provides that functionality), you should see in the web admin that the external interface has got an IP address from that server, and the subnet mask, gateway, etc are all configured correctly. On the internal interface LMCE should automatically assign the static IP address of 192.168.80.1. Devices on the internal network should be able freely to get IP addresses from the DHCP server on that interface. If both of these are true, then your core is correctly networked.<br />
<br />
If the names are wrong and the IP addresses are not set up as above then you need to name the interfaces correctly. You can use the ethtool command to flash the LEDs on each card in turn - do this and note precisely the MAC address (also from ethtool) of the interface that is connected to your external network. Do the same for the internal network.<br />
<br />
You can now create a udev rule to force the names.<br />
<br />
I use the text file editor, Joe. Use whichever editor you prefer - to install Joe from a terminal:<br />
<br />
sudo apt-get install joe<br />
<br />
Create a text file called /etc/udev/rules.d/70-persistent-net.rules (or edit it if it already exists):<br />
<br />
sudo joe /etc/udev/rules.d/70-persistent-net.rules<br />
<br />
Now add these 2 lines:<br />
<br />
KERNEL=="eth*", SYSFS{address}=="aa:bb:cc:dd:ee:ff", NAME="eth0"<br />
KERNEL=="eth*", SYSFS{address}=="aa:bb:cc:dd:ee:ff", NAME="eth1"<br />
<br />
Substitute aa:bb:cc:dd:ee:ff for the appropriate MAC address - the first one is the MAC address you noted for your external network, the second one for your internal network. NOTE: these are case sensitive, and all letters must be lower case.<br />
<br />
If there were already entries in this file, you will need to use your commonsense to determine whether they conflict. If they do, replace those conflicting entries with the ones above.<br />
<br />
Save and exit the file. Now reboot - the udev rules listen to kernel messages, filter them based on whether they are ethernet interface naming events, and then override the names assigned with the correct ones.<br />
<br />
You should now see in the web admin that all the IP addresses are correctly assigned and you can route both internally and externally.</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Internal_and_External_networks_swapped/not_working&diff=15269Internal and External networks swapped/not working2008-08-16T03:24:30Z<p>Colinjones: spelling</p>
<hr />
<div>[[Category:Troubleshooting]][[Category:Networking]]<br />
In some circumstances, and usually with particular motherboards/NICs, Linux may not initialise your network cards in a way that makes LMCE easy to get working.<br />
<br />
=How to check if this has happened=<br />
<br />
Use ethtool to determine your NIC names. For LMCE to work smoothly, the External network (typically connected to your existing home network and/or directly to your broadband router) should be called eth0. The Internal network (this is the new, dedicated LMCE network that all your telephony, media, security, Media Directors, Home Automation, etc devices are on) should be called eth1. There are different ways of configuring LMCE, but this is the default and easiest.<br />
<br />
If ethtool shows you have eth0 and eth2, or eth1 and eth2 or even eth0 and eth1 the wrong way around in some circumstances, then you have this problem.<br />
<br />
=What if it is wrong?=<br />
<br />
LMCE will assume that your external network is out of eth0 and internal out of eth1, so it will send traffic in the wrong directions, not plug and play properly, not be able to access your media, disrupt your external network DHCP, etc.<br />
<br />
=What to do=<br />
<br />
If the interface names are simply swapped, you can try swapping the cables around, or using the "swap" option in the web admin. Most of the time, this is all that is wrong.<br />
<br />
If you have a DHCP server enabled on the external network (you should never have one enabled on the internal network, LMCE provides that functionality), you should see in the web admin that the external interface has got an IP address from that server, and the subnet mask, gateway, etc are all configured correctly. On the internal interface LMCE should automatically assign the static IP address of 192.168.80.1. Devices on the internal network should be able freely to get IP addresses from the DHCP server on that interface. If both of these are true, then your core is correctly networked.<br />
<br />
If the names are wrong and the IP addresses are not set up as above then you need to correctly name the interfaces. You can use the ethtool command to flash the LEDs on each card in turn - do this and note precisely the MAC address (also from ethtool) of the interface that is connected to your external network. Do the same for the internal network.<br />
<br />
You can now create a udev rule to force the names.<br />
<br />
I use the text file editor, Joe. Use whichever editor you prefer - to install Joe from a terminal:<br />
<br />
sudo apt-get install joe<br />
<br />
Create a text file called /etc/udev/rules.d/70-persistent-net.rules (or edit it if it already exists):<br />
<br />
sudo joe /etc/udev/rules.d/70-persistent-net.rules<br />
<br />
Now add these 2 lines:<br />
<br />
KERNEL=="eth*", SYSFS{address}=="aa:bb:cc:dd:ee:ff", NAME="eth0"<br />
KERNEL=="eth*", SYSFS{address}=="aa:bb:cc:dd:ee:ff", NAME="eth1"<br />
<br />
Substitute aa:bb:cc:dd:ee:ff for the appropriate MAC address - the first one is the MAC address you noted for your external network, the second one for your internal network. NOTE: these are case sensitive, and all letters must be lower case.<br />
<br />
If there were already entries in this file, you will need to use your commonsense to determine whether they conflict. If they do, replace those conflicting entries with the ones above.<br />
<br />
Save and exit the file. Now reboot - the udev rules listen to kernel messages, filter them based on whether they are ethernet interface naming events, and then override the names assigned with the correct ones.<br />
<br />
You should now see in the web admin that all the IP addresses are correctly assigned and you can route both internally and externally.</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Internal_and_External_networks_swapped/not_working&diff=15268Internal and External networks swapped/not working2008-08-16T03:23:39Z<p>Colinjones: spelling</p>
<hr />
<div>[[Category:Troubleshooting]][[Category:Networking]]<br />
In some circumstances, and usually with particular motherboards/NICs, Linux may not initialise your network cards in a way that make LMCE easy to get working.<br />
<br />
=How to check if this has happened=<br />
<br />
Use ethtool to determine your NIC names. For LMCE to work smoothly, the External network (typically connected to your existing home network and/or directly to your broadband router) should be called eth0. The Internal network (this is the new, dedicated LMCE network that all your telephony, media, security, Media Directors, Home Automation, etc devices are on) should be called eth1. There are different ways of configuring LMCE, but this is the default and easiest.<br />
<br />
If ethtool shows you have eth0 and eth2, or eth1 and eth2 or even eth0 and eth1 the wrong way around in some circumstances, then you have this problem.<br />
<br />
=What if it is wrong?=<br />
<br />
LMCE will assume that your external network is out of eth0 and internal out of eth1, so it will send traffic in the wrong directions, not plug and play properly, not be able to access your media, disrupt your external network DHCP, etc.<br />
<br />
=What to do=<br />
<br />
If the interface names are simply swapped, you can try swapping the cables around, or using the "swap" option in the web admin. Most of the time, this is all that is wrong.<br />
<br />
If you have a DHCP server enabled on the external network (you should never have one enabled on the internal network, LMCE provides that functionality), you should see in the web admin that the external interface has got an IP address from that server, and the subnet mask, gateway, etc are all configured correctly. On the internal interface LMCE should automatically assign the static IP address of 192.168.80.1. Devices on the internal network should be able freely to get IP addresses from the DHCP server on that interface. If both of these are true, then your core is correctly networked.<br />
<br />
If the names are wrong and the IP addresses are not set up as above then you need to correctly name the interfaces. You can use the ethtool command to flash the LEDs on each card in turn - do this and note precisely the MAC address (also from ethtool) of the interface that is connected to your external network. Do the same for the internal network.<br />
<br />
You can now create a udev rule to force the names.<br />
<br />
I use the text file editor, Joe. Use whichever editor you prefer - to install Joe from a terminal:<br />
<br />
sudo apt-get install joe<br />
<br />
Create a text file called /etc/udev/rules.d/70-persistent-net.rules (or edit it if it already exists):<br />
<br />
sudo joe /etc/udev/rules.d/70-persistent-net.rules<br />
<br />
Now add these 2 lines:<br />
<br />
KERNEL=="eth*", SYSFS{address}=="aa:bb:cc:dd:ee:ff", NAME="eth0"<br />
KERNEL=="eth*", SYSFS{address}=="aa:bb:cc:dd:ee:ff", NAME="eth1"<br />
<br />
Substitute aa:bb:cc:dd:ee:ff for the appropriate MAC address - the first one is the MAC address you noted for your external network, the second one for your internal network. NOTE: these are case sensitive, and all letters must be lower case.<br />
<br />
If there were already entries in this file, you will need to use your commonsense to determine whether they conflict. If they do, replace those conflicting entries with the ones above.<br />
<br />
Save and exit the file. Now reboot - the udev rules listen to kernel messages, filter them based on whether they are ethernet interface naming events, and then override the names assigned with the correct ones.<br />
<br />
You should now see in the web admin that all the IP addresses are correctly assigned and you can route both internally and externally.</div>Colinjoneshttp://wiki.linuxmce.org/index.php?title=Internal_and_External_networks_swapped/not_working&diff=15267Internal and External networks swapped/not working2008-08-16T03:22:34Z<p>Colinjones: New page: Category:TroubleshootingCategory:Networking In some circumstance, and usually with particular motherboards/NICs, Linux may not initialise your network cards in a way that make LMCE...</p>
<hr />
<div>[[Category:Troubleshooting]][[Category:Networking]]<br />
In some circumstance, and usually with particular motherboards/NICs, Linux may not initialise your network cards in a way that make LMCE easy to get working.<br />
<br />
=How to check if this has happened=<br />
<br />
Use ethtool to determine your NIC names. For LMCE to work smoothly, the External network (typically connected to your existing home network and/or directly to your broadband router) should be called eth0. The Internal network (this is the new, dedicated LMCE network that all your telephony, media, security, Media Directors, Home Automation, etc devices are on) should be called eth1. There are different ways of configuring LMCE, but this is the default and easiest.<br />
<br />
If ethtool shows you have eth0 and eth2, or eth1 and eth2 or even eth0 and eth1 the wrong way around in some circumstances, then you have this problem.<br />
<br />
=What if it is wrong?=<br />
<br />
LMCE will assume that your external network is out of eth0 and internal out of eth1, so it will send traffic in the wrong directions, not plug and play properly, not be able to access your media, disrupt your external network DHCP, etc.<br />
<br />
=What to do=<br />
<br />
If the interface names are simply swapped, you can try swapping the cables around, or using the "swap" option in the web admin. Most of the time, this is all that is wrong.<br />
<br />
If you have a DHCP server enabled on the external network (you should never have one enabled on the internal network, LMCE provides that functionality), you should see in the web admin that the external interface has got an IP address from that server, and the subnet mask, gateway, etc are all configured correctly. On the internal interface LMCE should automatically assign the static IP address of 192.168.80.1. Devices on the internal network should be able freely to get IP addresses from the DHCP server on that interface. If both of these are true, then your core is correctly networked.<br />
<br />
If the names are wrong and the IP addresses are not set up as above then you need to correctly name the interfaces. You can use the ethtool command to flash the LEDs on each card in turn - do this and note precisely the MAC address (also from ethtool) of the interface that is connected to your external network. Do the same for the internal network.<br />
<br />
You can now create a udev rule to force the names.<br />
<br />
I use the text file editor, Joe. Use whichever editor you prefer - to install Joe from a terminal:<br />
<br />
sudo apt-get install joe<br />
<br />
Create a text file called /etc/udev/rules.d/70-persistent-net.rules (or edit it if it already exists):<br />
<br />
sudo joe /etc/udev/rules.d/70-persistent-net.rules<br />
<br />
Now add these 2 lines:<br />
<br />
KERNEL=="eth*", SYSFS{address}=="aa:bb:cc:dd:ee:ff", NAME="eth0"<br />
KERNEL=="eth*", SYSFS{address}=="aa:bb:cc:dd:ee:ff", NAME="eth1"<br />
<br />
Substitute aa:bb:cc:dd:ee:ff for the appropriate MAC address - the first one is the MAC address you noted for your external network, the second one for your internal network. NOTE: these are case sensitive, and all letters must be lower case.<br />
<br />
If there were already entries in this file, you will need to use your commonsense to determine whether they conflict. If they do, replace those conflicting entries with the ones above.<br />
<br />
Save and exit the file. Now reboot - the udev rules listen to kernel messages, filter them based on whether they are ethernet interface naming events, and then override the names assigned with the correct ones.<br />
<br />
You should now see in the web admin that all the IP addresses are correctly assigned and you can route both internally and externally.</div>Colinjones