LinuxMCE - User contributions [en]

Wizard Pages

2007-09-17T22:35:07Z

Macca: remove spam

The Wizard is designed to be a quick and simple way to setup your whole LinuxMCE system. To use it, just go to the LinuxMCE Admin web site, and click "Wizard". Then go through each of the pages and fill out the information on each page. Be sure to click "Save" or "Update" to save the changes you make to each page before going to the next. Every page in the Wizard section is designed to be simple for the non-techie. There may be some other, more advanced pages that are more technical.
What pages you see in your Wizard will depend on what devices you have in your home--you will only see pages that apply to your home. If you add more devices later on, more pages may appear in the wizard for those devices.
Setting up your LinuxMCE system consists of 4 things:
1) Providing some general information, such as what kind of network you have.
2) Creating the devices (lights, tv's, cameras, etc.).
3) Creating your scenarios. A "scenario" is a group of commands, or tasks, you want executed when you touch a button. Each scenario you create will appear on the Orbiters as a button. Scenarios are generally organized into 5 categories: lighting, media, climate, security and telephone. You can create, for example, a lighting scenario called "Entertaining" which turns on all the lights in the house and in the front yard. A button labeled "Entertaining" will then appear on the Orbiters in the lighting section--touch it to activate the scenario. Any scenario can do anything. For example, just because the "Entertaining" scenario is a lighting scenario doesn't mean the scenario only affects lights. You can make the scenario also play some music, and maybe open the front gate. You can use the "Advanced, My Scenarios" menu option for low-level control over a scenario, to make it do whatever you want. However the Wizard includes pages that make it very easy to create scenarios. For example, when you add a lighting scenario with the Wizard, it lists all the lights in the house and lets you pick the ones you want to change with the scenario.
4) Creating event handlers. This is how you tell LinuxMCE you want it to do something in response to some event. For example, you want LinuxMCE to turn on the Front Porch light when a motion detector is tripped. Or you want it to play a loud message on the TV's when there is a security breach. Or stop watering the lawn after it rains.

Orbiters

2007-09-17T22:33:05Z

Macca: remove spam

An "Orbiter" is a remote control--anything you use to control your LinuxMCE system.
Here you add all the orbiters you want to use in your house, no matter what type. This includes the mobile orbiters (ie mobile phones), the regular orbiters (like wireless webpads and tablet pc's), any orbiters you want to run on a normal PC, as well as the on-screen displays. Every Media Director displays an Orbiter on screen as well. All these orbiters, and every one will appear on this page.
Room: is where the room where the orbiter is normally kept. For mobile orbiters this selection isn't important since you carry them everywhere. For regular orbiters, whatever room you choose is the room that the orbiter will use until the user selects something else.
Leave Monitor on for OSD: OSD (On-screen display) refers to the orbiters that run on the media directors. These are a little different since the media director is normally connected to a tv. If you want to use the Orbiter on a media director using a keyboard/mouse or infrared remote control, check this box. It means that when media stops LinuxMCE won't turn the tv off right away so you can continue using the Orbiter using the Media Director's keyboard or mouse, or the infrared remote. The TV will turn off only when the screen saver starts, or if you touch the 'power' button and 'turn off display'. If you always control the Media Director using another orbiter, like a web pad or mobile phone, you can leave it unchecked. Then the TV will come on only when you're going to play media or watch TV, and it will turn off immediately when you stop watching media.
This device uses a Wi-Fi connection Is useful for webpads and pda's with a wi-fi signal. Since wi-fi is rather unreliable, the core and Orbiter will constantly 'ping' each other so they both know the connection is still strong enough, and the Orbiter software will automatically exit when the Orbiter goes out of range.
No Effects: Many screens have special effects, like animated buttons, fades, and so on. If the orbiter has a slow processor, this can make it take longer to respond. Choose this to disable any special effects on the orbiter so it runs as fast as possible.
Language: All the text on the screen will appear in this language, if possible.
NOTE: You can create your own menus and translate screens into other languages using [[Designer]].
Size: Choose the screen size you want. If this is an on-screen orbiter (an orbiter that appears on a media director), this will also set the media director's screen resolution.
Skin: There may be several skins, or motif's, to choose from, like 'Wood', 'Marble', etc.
User: Is the person who normally uses this orbiter.
Quick Regen: To make the orbiters respond quickly, all the images you see on their screens are pre-rendered. The User interface is "built" by the program [[Orbiter Generator]]. This will cause Orbiter Generator to re-generate the user interface for this orbiter, but it will only regenerate the screens that appear to have changed.
Full Regen: This will cause Orbiter Generator to re-generate every screen on the Orbiter.
Reduce image size by %: This will cause Orbiter Generator to add some padding to the screens. This is useful if the screen margins are being displayed outside of the TV screen. Developer info: although it may sound intuitive that the corresponding DeviceData is also called "Reduce image size by %", it is in fact called "Spacing". The PK_DeviceData for it is 150. The text "Reduce image size by %" comes from the DeviceTemplate_DeviceData table and it's the meaning of the device data in that specific device context
Offset: This will cause Orbiter...

[[Category: Orbiters]]

Adding new web links

2007-09-12T10:30:19Z

Macca: Complete new page

It is possible to add new web links to the computing page.

*First, click pluto-admin, under the computing menu. Firefox should open.
*Click Bookmarks->Manage Bookmarks and add your new bookmarks.
*Quit firefox by File->Quit. '''IMPORTANT:''' If you quit firefox by using the linux mce buttons at the bottom of the screen your bookmarks will not be saved!
Your new bookmarks should now appear on the computing page.

[[Category : Tutorials]]

Talk:Suggested hardware

2007-09-11T12:42:37Z

Macca: /* A single page */

May I suggest using seperate hierarchical categories under Hardware instead of sections? I know it's a bit of a hassle since we're the first, but I'm hoping everybody will add their own hardware over time. Anyway, thanks for helping out, much appreciated. --[[User:Zaerc|Zaerc]] 08:49, 8 July 2007 (MST)

I suggest this page should be redirected to [[tested good hardware]] and [[tested bad hardware]].--[[User:Macca|Macca]] 02:56, 3 September 2007 (MST)
* Uh, you can't redirect to 2 different places. Maybe you could provide some argument for maintaining 2 separate pages. Otherwise your comment is not useful.

Macca, I think that the opposite should happen. [[tested good hardware]] and [[tested bad hardware]] should be redirected here. There's nothing worse than having to look on 2 pages and still not knowing the answer. There are 3 states of hardware good, bad and unknown. So you should at least promote a page called "untested hardware". Now if I have a piece of hardware I'd have to check [[tested good hardware]], [[tested bad hardware]] and "untested hardware" in order to know the status of my device. IMHO that sucks. Why can't I just go to 1 page and see what the status of my device is ? I suggest a table with a status column. --[[User:Trout|Trout]] 16:49, 4 September 2007 (MST)

I don't want to get into a turf war or pissing contest here. That helps no-one. A few notes;
*Any list of this kind needs to be clear and concise. Currently the suggested_hardware page is neither.
*For ease of use, the list should be alphabetised. Is there a way to do this automatically?
*The device naming convention should be standardised. ManufacturerName_ModelName works well and seems to be widely in use on this wiki.
*Similarily there should be a standard layout for the device articles. At the very top should be a status section stating if it works, what version of linuxmce it works with (future-proofing. Like all things, easy doing it from the start, hard to add on later) etc. This should be short and to the point, any extra information about why it doesn't work etc should go in the problems and pitfalls section. This layout should also include a personal experience section (at the end) which users should tag. This allows follow up questions on the forum or the discussion page. Maybe we should create some templates called template_motherboard or motherboard_layout for each device type?
*If the status of a device is not known, it doesn't go on the list. Otherwise you end up with a list of every motherboard etc known to man. There are [[http://motherboards.org other sites]] that do this, and far better than we could here.
*Is it possible to set up a table that can be filtered or sorted?
*Maybe a traffic light system? Green works, Red doesn't and Yellow works but maybe isn't worth the trouble( or maybe experimental).
*Page naming. Maybe hardware_status? The name suggested_hardware sounds like it should perform the same function as what_hardware_will_i_need or maybe a list for a complete, top-of-the-line do-everything system. Tested_hardware doesn't sound quite right either.
*It should be linked prominently on the main page of the wiki, maybe also a sticky subject in the forums.
There's probably lots more, but its late here, and i'm tired :) --[[User:Macca|Macca]] 07:08, 7 September 2007 (MST)

==Our options for a hardware status list==
===A table===
No good. Sure, we could make a kick-ass table that users could sort on manufacturer name, device type, device status etc. But it would be impossible for users to add new hardware to. Even a simple 2 column table is difficult to add new data to. For a new user, they will take one look at the edit page and run screaming. Not the effect we are after. Unless we have a sole person maintaining the table (which defeats the point of a wiki) it wont work.
* In a wiki, you must assume that editors have the know-how to edit rather than just type. You are trying to say the opposite here. Your argument of only one maintainer is absurd.
**I don't think you know what goes into creating a table. I thought a table would be the perfect solution, but i went and did some research before i wrote the 'options' piece. Even a table with only two columns is difficult to add new data to. Add in another column or some different sections or start colouring cells and even experienced wiki users will find it incredibly difficult adding new devices. Tables in wikis render differently in each browser, so a user (even if they know what they are doing) could add something in IE, for example, that will look fine to him, but break the page for firefox users. Having a page that breaks if a user puts a space or a single quote in the wrong spot is not a good idea. It would be an incredibly frustrating experience for the user and not only would they not add their device to the list, they may not add information to any other wiki pages. The harder a page is to edit and the more knowledge required to do so reduces the likelyhood that users will add their own information. What we should be aiming for is lowest-common-denominator. If a page is easy to add information to then more users are likely to add theirs, especially if all they have to do is copy what was done before them, no special knowledge needed. The point of a wiki is that ANYBODY can edit it, creating complex pages just adds barriers to entry. --[[User:Macca|Macca]] 18:16, 9 September 2007 (MST)
*** ANYBODY can edit. At the end of the day, they'll always find a way to communicate that they have hardware they'd like to add. And it may need to be formatted in the table correctly. I disagree with '''The point of a wiki is that ANYBODY can edit it''' because the point of a wiki is that EVERYONE can edit it. The point is important because it means 1. we don't rely on a single user to maintain. 2. One person can add it incorrectly and another can format it more correctly. Also I don't know why you are trying to please the editors rather than the readers. Typically a page is read significantly more than it's written. So why not make it good for the readers and *slightly* harder for the writers? [[User:Trout|Trout]] 02:41, 10 September 2007 (MST)
****If the wiki is easy to edit then more people will edit it. this makes our community stronger and the wiki better. Why would we want to make it hard for people? What we should be aiming for is for every reader to be an editor. If users have to send an email to someone or post in the forums to get their hardware added to the list then we may as well scrap the wiki and just have a standard web page. If a user adds something to a table incorrectly, it may break the table completely or worse. There is a very insidious flaw with tables. the data isnt added in one place, its all over the edit page. if the user doesn't get every bit of data in exactly the right place then almost every device on that table is going to show the wrong data. The table will look normal, but the data will be wrong. It could go unnoticed for months, and every device added in that time will have be removed and readded once the flaw is found and fixed. There is not much that can go wrong with a simple list, and if anything does go wrong ANY user can go in and fix it, even one with no wiki knowledge at all.--[[User:Macca|Macca]] 16:05, 10 September 2007 (MST)
**Also, it could be an HTML table. This is a bit easier for editors and still gives a good look. We'd have to for go the column sorting possibility, but maybe it's a good compromise. [[User:Trout|Trout]] 02:46, 11 September 2007 (MST)

===A single page===
2 options here, separate working and nonworking sections, or everything together relying on comments to tell the difference between them.
*2 sections. Easy to read, easy to navigate, easy to edit. Alphabetising sub-sections means both sections will keep same heirachy. Page size is larger. Chance for users to put devices in the wrong section.
*Comments. Messy, hard to tell status at a glance. Problems with users adding long-winded comments or not adding comments at all (especially when there is no page for the device). Page size grows at least 2x faster than number of devices. Is there an upper limit for wiki page size?
** Actually there are more options than 2.
* Create a traffic light system Red = not working, yellow = partially not working, green = fully working (non-existance in the table means unknown) Then you can tell at a glance, what the full story about a device is.[[User:Trout|Trout]] 09:09, 9 September 2007 (MST)
**Thats really just the same as the comments option. You are relying on aditional information to know the status of the device. What if a user doesnt put the colour in? what if the page for a device doesn't exist? The text will be red. Does that mean that the device doesn't work? Introducing a partial option is not a good idea. How many shades of gray should we cater for? If a device works (that is performs its primary intended function) then it goes on the working list. If i have to do some mucking around first, recompile the kernel, add text to a config file, sacrifice a goat on the full moon, but my video card outputs video or my sound card outputs sound then it goes on the working list (even if secondary features dont work yet). If i do all of the above and my sound card works as a DAC for an oscilloscope but doesnt output sound, then it goes on the nonworking list.--[[User:Macca|Macca]] 18:16, 9 September 2007 (MST)
*** It must be nice to see the world in such black and white. Okay, so what about a video card that works but does not support transparency ? Which pile ? [[User:Trout|Trout]] 02:33, 10 September 2007 (MST)
**** You mean any video card that doesnt use an nvidia chipset? Quite obviously the working pile. Transparency is not necessary for running linuxmce and the lack of it doesnt prevent any of the core features from working. i can still watch vidoes, surf the web and control any device in my house. There are going to be few devices that work 100%. Say i have 2 tv tuners, one supports fm radio reception and one doesnt. both cards allow me to watch tv and record flawlessly. Most users arent going to care about fm radio. AFAIK it isnt even supported by linuxmce. So why should one card be labelled partially working when it performs equally as well as a card that is labelled as working? The point i am trying to make is that information about each device, what functions it performs (or doesnt perform), what voodoo it requires to get recognised, how many rs232 ports it has etc belongs on the page for that device. Requiring that information on multiple pages means thing will get out of date much easier. It is not that onerous to add just a link to a device page on the working or non working list, but if users have to retype what they just typed on another page, many are not going to bother. If we have a page that is just a list of links, no extra information, we can tell users that if a page for their device doesn't exist, they can create one simply by adding their device to the list. Hey presto, instantly users are adding their devices. (Sure they could create their device, edit that page and then add it to the list, but we just cut out a step and got the users to do our job for us. If only there was a way to automatically create a page based on a template. we wouldn't have to do any work at all!)--[[User:Macca|Macca]] 15:44, 10 September 2007 (MST)
***** '''You mean any video card that doesnt use an nvidia chipset?''' No, I mean cards that don't support transparency. Yes, today's answer is ones that don't have NVidia chipset. But what about when someone else produces one that also works? So a user 1. sees the cool video and 2. sees that all the video cards are working perfectly. Then you tell them: "oh, I didn't know you wanted trasparency, you have to look at each hardware page for that information." Sorry, but that is not an acceptable situation. It's important to know that the features demanded by LinuxMCE are all working with a particular device. It will probably drive purchase of devices that have it. Also it's not always clear which cards use the NVidia chipset. and this rule can change in the future. That said, we '''need''' a partially working or a partially not working indication. [[User:Trout|Trout]] 02:53, 11 September 2007 (MST)
******I never claimed any devices on the working list worked perfectly, i said their primary intended function works (We can make this clear to the users by stating it at the top of the list), and where exactly does linux mce '''demand''' that my video card support transparency?. Even if you do have a partial working status, the user still has to look on the page for that device to find out exactly what works and what doesn't. It adds no value when (as i have pointed out before) virtually all devices will be 'partially working' (Hardly anything has plug and play support, devices that perform no useful function (read: don't work) are recognised by the system(putting them above the level of 'completely not working' and therefore into the category of partially working)). What about different levels of partially working? do you provide a percentage? how do you decide what percentage each feature that works is worth? Even if you come up with a fair and even system, users still have to go to the page for each device to get the full story, and if they have to go there any way, why bother with the extra information in the first place?(It all comes back to simplicity. The simpler the page is, the more likely users will add data to it and keep it up to date, the more likely it is to be a useful resource). It is not sensible to have every feature for every device listed on a single page, why even have individual device pages at all? Why have any extra pages? The entire wiki should be on a single page, that way users can find all the information they need without having to click on any pesky links at all.--[[User:Macca|Macca]] 05:42, 11 September 2007 (MST)

* Take a look at this page and see if it is one that can be adopted. [[HCL]] It appears to be a hold over from the Pluto guys, but it looks like it may have potential.--[[User:Rwilson131|Rwilson131]] 11:29, 9 September 2007 (MST)
**Thanks for your input. That page is too complex, Imagine having 50 devices on there. all that information belongs on the page for each individual device.--[[User:Macca|Macca]] 18:16, 9 September 2007 (MST)

===multiple pages===
No confusion over whether device works or not. Hardware support on linux is pretty good, the list of working devices is going to be far longer than the list of those that dont work. Keeping the lists separate makes both of them easier to read and edit. If the sections are alphabetised then both pages will keep the same heirachy automatically.
* Big time confusion. Ok if I look at the "good" page and I see my device, then there's no confusion. But if it's not listed, I am absolutely confused. Hmmm is it not working? Is it unknown? Maybe it's partially working and not listed on this "good hardware" page.
* ''the list of working devices is going to be far longer than the list of those that dont work. Keeping the lists separate makes both of them easier to read and edit.'' - Uh no, it does not.
* ''If the sections are alphabetised then both pages will keep the same heirachy automatically.'' - again, no. especially when more and more cross devices come about. for example the iPhone. should it be listed under PDA or phone? Hmm I wonder if it'll match the separately maintained good/bad hardware page. I assume that when you say automatically you mean naturally.[[User:Trout|Trout]] 09:16, 9 September 2007 (MST)
**Naturally is a better word, thanks. Motherboards may have video chips or sound chips on board. Does this mean it should be listed under video cards or sound cards? I think not. Most devices will have more than one funtion, each device should be listed under the section that matches its primary intended function. The iphone is primarily a phone, and so goes in the phone section.--[[User:Macca|Macca]] 18:16, 9 September 2007 (MST)
===working and nonworking categories===
No need to maintain a separate status page, just go to category:working and there it is, automatically alphabetised for you. How do you separate the motherboards from the mobile phones from the tv tuners though?

* Traffic light system.[[User:Trout|Trout]] 09:17, 9 September 2007 (MST)
**I am not sure what you mean here. There is no way to add additional information for each device to the categories page.--[[User:Macca|Macca]] 18:16, 9 September 2007 (MST)
*** Oops, you're right. [[User:Trout|Trout]] 02:28, 10 September 2007 (MST)

===no status list at all===
Rely on individual device pages. Not really a good solution, provides no overview so users wanting to get a list of known working components to build their system have to trawl through each device page individually.
* Agreed :) [[User:Trout|Trout]] 09:18, 9 September 2007 (MST)

===''conclusion''===
The categories option seems elegant at first, making use of inbuilt wiki tools to do our job for us, but it only does half the job. It can't categorise the working devices by device-type on the one page. Most devices don't have helpful names, so users wont know if sony_xyz123 is a television or an a/v reciever or a dvd jukebox. This makes it almost useless.

Both single page options will become unwieldy as the list grows. It is too easy for users to add devices to the wrong section or not put comments in etc.
Separating categories reduces confusion. Have a look at the [[suggested hardware]] page. Tell me which of those tv tuner cards work and which don't. You can't. None of them have any information, one doesn't even have its own page. Now look at the tv tuners on the [[tested good hardware]] page. No confusion there, all of them work. The need for a list of known working hardware is far greater than the need for a list of hardware that doesnt work. Why clutter up the former with the latter? It just doesn't make sense. If a user has a specific peice of hardware and wants to know if it works or not, they can type the name in the search box and get the answer instantly. If a user wants to know what hardware definately works with linux mce so he can write a shoppping list, he doesn't want to be confronted with a list that contains both working and nonworking devices, especially if he is not sure which is which. If a developer is looking to increase linux mce's hardware compatability, he doesn't care what already works, he only wants to know of those devices that don't work. There is no need for both categories to be on the same page or in the same list, it just adds clutter and confusion. The only way the separate page option could be confusing is if the same device ends up on both lists, but this can just as easily happen with any of the other solutions. There is no additional cost in having a second page (seeing as how there are over 1800 of them), it costs the user nothing to add their hardware to working_hardware rather than hardware_status#working. If the nonworking page doesnt get visited much, then there has been the benefit of not cluttering up information people do want with information they don't. If, on the other hand, the non working page gets visited lots, those users will have benefited by not having to trawl through a list containing hundreds of working devices to find the information on the few they are after. It's a win-win situation.
--[[User:Macca|Macca]] 05:16, 9 September 2007 (MST)

Both single page options will become unwieldy as the list grows.

that's contradicts what you said about the good hardware list being much bigger than the bad list.
I get that you just want two lists, but for users who are not so inclined to do a bunch of digging and comparing and searching between lists, we need a single page to do this job. It would be very helpful to have a table with an '''at-a-glance''' graphic that told the overall story about the device. r/y/g
I think that you also overlook how difficult it is to know when something has an unknown status. It'd give me a much better feeling if I went to a single hardware page and saw all the other Hauppauge devices, with r/y/g statues and not the one I have or consider buying.. It would tell me instantly that the status is not known. How can I get this with your multiple pages ?
[[User:Trout|Trout]] 09:23, 9 September 2007 (MST)
*Why would users have to do 'a bunch of digging and comparing and searching between lists'? If a user wants to know if tv tuner brand_x model_y works in linuxmce, they type brand_x model_y into the search box. Instant result whatever the status. If a user is looking to get some new hardware and wants to know what works with linuxmce, they go to the working list, pick a tv tuner card and do some research on price, availabliity, features etc. If they dont like it, they go back to the list and pick another one.--[[User:Macca|Macca]] 18:16, 9 September 2007 (MST)

== Categories are just fine ==

Users can either find their hardware by name, or use the subcategories to find specific hardware by type. As far as I'm concerned all the other lists can go since they are a nuisance to maintain and add very little extra value.

-- [[User:Zaerc|Zaerc]] 10:51, 9 September 2007 (MST)

* so you are for [[Talk:Suggested hardware#no status list at all|no status list at all]]. For me that's insane because you then need to goto each hardware page to find the status. On this issue, I agree with [[User:Macca|Macca]] [[User:Trout|Trout]] 13:30, 9 September 2007 (MST)

== other concerns ==

In my opinion the focus should be on getting more information in here, and making 1, 2 or 3 more pages on which extra information has to be kept up to date is not really helping. This is not supposed to be a shopping list, but a growing source of information to which people should add themselves with as little hassle as possible. But if you guys want to maintain such lists then you have my blessing. I just think that every piece of hardware deserves it's own page.

--[[User:Zaerc|Zaerc]] 14:07, 9 September 2007 (MST)
*Zaerc, i know that you are an active user here and i appreciate your comments. No doubt you have seen posts in the forum along the lines of 'what hardware will work with linux mce'. There are a fair few of them at the moment and it is only going to get worse over time. This is the problem that i am trying to address. If we have a sticky subject in the forum pointing these individuals to a page in the wiki it frees up users from answering the same questions over and over, and the important or interesting posts wont get lost in the noise. We definately need a seperate page for each device, no arguments there. See my notes about templates above, i would value some input.--[[User:Macca|Macca]] 18:16, 9 September 2007 (MST)

* I agree that each piece of hardware deserves it's own page. But also an overview page with links to all these individual hardware pages is needed IMHO. [[User:Trout|Trout]] 14:42, 9 September 2007 (MST)

== Yet another opinion ==

First of all, lets keep things simple:

We make categories, motherboards, tv-cards, gfx-card, soundcards etc.

Then, list all hardware that's been tested, on that page and the result, if i want more info about a particular motherboard, tv-card etc - I click it and get additional info. Easy to maintain, easy to add entries etc.

As it is now, it's like a huge pile of info, not much structure too it, I'd love to help out and see this grow into something really useful and easy.

[[User:Samme|Samme]] 04:52, 10 September 2007 (MST)

Talk:Suggested hardware

2007-09-10T23:05:35Z

Macca: /* A table */

May I suggest using seperate hierarchical categories under Hardware instead of sections? I know it's a bit of a hassle since we're the first, but I'm hoping everybody will add their own hardware over time. Anyway, thanks for helping out, much appreciated. --[[User:Zaerc|Zaerc]] 08:49, 8 July 2007 (MST)

I suggest this page should be redirected to [[tested good hardware]] and [[tested bad hardware]].--[[User:Macca|Macca]] 02:56, 3 September 2007 (MST)
* Uh, you can't redirect to 2 different places. Maybe you could provide some argument for maintaining 2 separate pages. Otherwise your comment is not useful.

Macca, I think that the opposite should happen. [[tested good hardware]] and [[tested bad hardware]] should be redirected here. There's nothing worse than having to look on 2 pages and still not knowing the answer. There are 3 states of hardware good, bad and unknown. So you should at least promote a page called "untested hardware". Now if I have a piece of hardware I'd have to check [[tested good hardware]], [[tested bad hardware]] and "untested hardware" in order to know the status of my device. IMHO that sucks. Why can't I just go to 1 page and see what the status of my device is ? I suggest a table with a status column. --[[User:Trout|Trout]] 16:49, 4 September 2007 (MST)

I don't want to get into a turf war or pissing contest here. That helps no-one. A few notes;
*Any list of this kind needs to be clear and concise. Currently the suggested_hardware page is neither.
*For ease of use, the list should be alphabetised. Is there a way to do this automatically?
*The device naming convention should be standardised. ManufacturerName_ModelName works well and seems to be widely in use on this wiki.
*Similarily there should be a standard layout for the device articles. At the very top should be a status section stating if it works, what version of linuxmce it works with (future-proofing. Like all things, easy doing it from the start, hard to add on later) etc. This should be short and to the point, any extra information about why it doesn't work etc should go in the problems and pitfalls section. This layout should also include a personal experience section (at the end) which users should tag. This allows follow up questions on the forum or the discussion page. Maybe we should create some templates called template_motherboard or motherboard_layout for each device type?
*If the status of a device is not known, it doesn't go on the list. Otherwise you end up with a list of every motherboard etc known to man. There are [[http://motherboards.org other sites]] that do this, and far better than we could here.
*Is it possible to set up a table that can be filtered or sorted?
*Maybe a traffic light system? Green works, Red doesn't and Yellow works but maybe isn't worth the trouble( or maybe experimental).
*Page naming. Maybe hardware_status? The name suggested_hardware sounds like it should perform the same function as what_hardware_will_i_need or maybe a list for a complete, top-of-the-line do-everything system. Tested_hardware doesn't sound quite right either.
*It should be linked prominently on the main page of the wiki, maybe also a sticky subject in the forums.
There's probably lots more, but its late here, and i'm tired :) --[[User:Macca|Macca]] 07:08, 7 September 2007 (MST)

==Our options for a hardware status list==
===A table===
No good. Sure, we could make a kick-ass table that users could sort on manufacturer name, device type, device status etc. But it would be impossible for users to add new hardware to. Even a simple 2 column table is difficult to add new data to. For a new user, they will take one look at the edit page and run screaming. Not the effect we are after. Unless we have a sole person maintaining the table (which defeats the point of a wiki) it wont work.
* In a wiki, you must assume that editors have the know-how to edit rather than just type. You are trying to say the opposite here. Your argument of only one maintainer is absurd.
**I don't think you know what goes into creating a table. I thought a table would be the perfect solution, but i went and did some research before i wrote the 'options' piece. Even a table with only two columns is difficult to add new data to. Add in another column or some different sections or start colouring cells and even experienced wiki users will find it incredibly difficult adding new devices. Tables in wikis render differently in each browser, so a user (even if they know what they are doing) could add something in IE, for example, that will look fine to him, but break the page for firefox users. Having a page that breaks if a user puts a space or a single quote in the wrong spot is not a good idea. It would be an incredibly frustrating experience for the user and not only would they not add their device to the list, they may not add information to any other wiki pages. The harder a page is to edit and the more knowledge required to do so reduces the likelyhood that users will add their own information. What we should be aiming for is lowest-common-denominator. If a page is easy to add information to then more users are likely to add theirs, especially if all they have to do is copy what was done before them, no special knowledge needed. The point of a wiki is that ANYBODY can edit it, creating complex pages just adds barriers to entry. --[[User:Macca|Macca]] 18:16, 9 September 2007 (MST)
*** ANYBODY can edit. At the end of the day, they'll always find a way to communicate that they have hardware they'd like to add. And it may need to be formatted in the table correctly. I disagree with '''The point of a wiki is that ANYBODY can edit it''' because the point of a wiki is that EVERYONE can edit it. The point is important because it means 1. we don't rely on a single user to maintain. 2. One person can add it incorrectly and another can format it more correctly. Also I don't know why you are trying to please the editors rather than the readers. Typically a page is read significantly more than it's written. So why not make it good for the readers and *slightly* harder for the writers? [[User:Trout|Trout]] 02:41, 10 September 2007 (MST)
****If the wiki is easy to edit then more people will edit it. this makes our community stronger and the wiki better. Why would we want to make it hard for people? What we should be aiming for is for every reader to be an editor. If users have to send an email to someone or post in the forums to get their hardware added to the list then we may as well scrap the wiki and just have a standard web page. If a user adds something to a table incorrectly, it may break the table completely or worse. There is a very insidious flaw with tables. the data isnt added in one place, its all over the edit page. if the user doesn't get every bit of data in exactly the right place then almost every device on that table is going to show the wrong data. The table will look normal, but the data will be wrong. It could go unnoticed for months, and every device added in that time will have be removed and readded once the flaw is found and fixed. There is not much that can go wrong with a simple list, and if anything does go wrong ANY user can go in and fix it, even one with no wiki knowledge at all.--[[User:Macca|Macca]] 16:05, 10 September 2007 (MST)

===A single page===
2 options here, separate working and nonworking sections, or everything together relying on comments to tell the difference between them.
*2 sections. Easy to read, easy to navigate, easy to edit. Alphabetising sub-sections means both sections will keep same heirachy. Page size is larger. Chance for users to put devices in the wrong section.
*Comments. Messy, hard to tell status at a glance. Problems with users adding long-winded comments or not adding comments at all (especially when there is no page for the device). Page size grows at least 2x faster than number of devices. Is there an upper limit for wiki page size?
** Actually there are more options than 2.
* Create a traffic light system Red = not working, yellow = partially not working, green = fully working (non-existance in the table means unknown) Then you can tell at a glance, what the full story about a device is.[[User:Trout|Trout]] 09:09, 9 September 2007 (MST)
**Thats really just the same as the comments option. You are relying on aditional information to know the status of the device. What if a user doesnt put the colour in? what if the page for a device doesn't exist? The text will be red. Does that mean that the device doesn't work? Introducing a partial option is not a good idea. How many shades of gray should we cater for? If a device works (that is performs its primary intended function) then it goes on the working list. If i have to do some mucking around first, recompile the kernel, add text to a config file, sacrifice a goat on the full moon, but my video card outputs video or my sound card outputs sound then it goes on the working list (even if secondary features dont work yet). If i do all of the above and my sound card works as a DAC for an oscilloscope but doesnt output sound, then it goes on the nonworking list.--[[User:Macca|Macca]] 18:16, 9 September 2007 (MST)
*** It must be nice to see the world in such black and white. Okay, so what about a video card that works but does not support transparency ? Which pile ? [[User:Trout|Trout]] 02:33, 10 September 2007 (MST)
**** You mean any video card that doesnt use an nvidia chipset? Quite obviously the working pile. Transparency is not necessary for running linuxmce and the lack of it doesnt prevent any of the core features from working. i can still watch vidoes, surf the web and control any device in my house. There are going to be few devices that work 100%. Say i have 2 tv tuners, one supports fm radio reception and one doesnt. both cards allow me to watch tv and record flawlessly. Most users arent going to care about fm radio. AFAIK it isnt even supported by linuxmce. So why should one card be labelled partially working when it performs equally as well as a card that is labelled as working? The point i am trying to make is that information about each device, what functions it performs (or doesnt perform), what voodoo it requires to get recognised, how many rs232 ports it has etc belongs on the page for that device. Requiring that information on multiple pages means thing will get out of date much easier. It is not that onerous to add just a link to a device page on the working or non working list, but if users have to retype what they just typed on another page, many are not going to bother. If we have a page that is just a list of links, no extra information, we can tell users that if a page for their device doesn't exist, they can create one simply by adding their device to the list. Hey presto, instantly users are adding their devices. (Sure they could create their device, edit that page and then add it to the list, but we just cut out a step and got the users to do our job for us. If only there was a way to automatically create a page based on a template. we wouldn't have to do any work at all!)--[[User:Macca|Macca]] 15:44, 10 September 2007 (MST)

* Take a look at this page and see if it is one that can be adopted. [[HCL]] It appears to be a hold over from the Pluto guys, but it looks like it may have potential.--[[User:Rwilson131|Rwilson131]] 11:29, 9 September 2007 (MST)
**Thanks for your input. That page is too complex, Imagine having 50 devices on there. all that information belongs on the page for each individual device.--[[User:Macca|Macca]] 18:16, 9 September 2007 (MST)

===multiple pages===
No confusion over whether device works or not. Hardware support on linux is pretty good, the list of working devices is going to be far longer than the list of those that dont work. Keeping the lists separate makes both of them easier to read and edit. If the sections are alphabetised then both pages will keep the same heirachy automatically.
* Big time confusion. Ok if I look at the "good" page and I see my device, then there's no confusion. But if it's not listed, I am absolutely confused. Hmmm is it not working? Is it unknown? Maybe it's partially working and not listed on this "good hardware" page.
* ''the list of working devices is going to be far longer than the list of those that dont work. Keeping the lists separate makes both of them easier to read and edit.'' - Uh no, it does not.
* ''If the sections are alphabetised then both pages will keep the same heirachy automatically.'' - again, no. especially when more and more cross devices come about. for example the iPhone. should it be listed under PDA or phone? Hmm I wonder if it'll match the separately maintained good/bad hardware page. I assume that when you say automatically you mean naturally.[[User:Trout|Trout]] 09:16, 9 September 2007 (MST)
**Naturally is a better word, thanks. Motherboards may have video chips or sound chips on board. Does this mean it should be listed under video cards or sound cards? I think not. Most devices will have more than one funtion, each device should be listed under the section that matches its primary intended function. The iphone is primarily a phone, and so goes in the phone section.--[[User:Macca|Macca]] 18:16, 9 September 2007 (MST)
===working and nonworking categories===
No need to maintain a separate status page, just go to category:working and there it is, automatically alphabetised for you. How do you separate the motherboards from the mobile phones from the tv tuners though?

* Traffic light system.[[User:Trout|Trout]] 09:17, 9 September 2007 (MST)
**I am not sure what you mean here. There is no way to add additional information for each device to the categories page.--[[User:Macca|Macca]] 18:16, 9 September 2007 (MST)
*** Oops, you're right. [[User:Trout|Trout]] 02:28, 10 September 2007 (MST)

===no status list at all===
Rely on individual device pages. Not really a good solution, provides no overview so users wanting to get a list of known working components to build their system have to trawl through each device page individually.
* Agreed :) [[User:Trout|Trout]] 09:18, 9 September 2007 (MST)

===''conclusion''===
The categories option seems elegant at first, making use of inbuilt wiki tools to do our job for us, but it only does half the job. It can't categorise the working devices by device-type on the one page. Most devices don't have helpful names, so users wont know if sony_xyz123 is a television or an a/v reciever or a dvd jukebox. This makes it almost useless.

Both single page options will become unwieldy as the list grows. It is too easy for users to add devices to the wrong section or not put comments in etc.
Separating categories reduces confusion. Have a look at the [[suggested hardware]] page. Tell me which of those tv tuner cards work and which don't. You can't. None of them have any information, one doesn't even have its own page. Now look at the tv tuners on the [[tested good hardware]] page. No confusion there, all of them work. The need for a list of known working hardware is far greater than the need for a list of hardware that doesnt work. Why clutter up the former with the latter? It just doesn't make sense. If a user has a specific peice of hardware and wants to know if it works or not, they can type the name in the search box and get the answer instantly. If a user wants to know what hardware definately works with linux mce so he can write a shoppping list, he doesn't want to be confronted with a list that contains both working and nonworking devices, especially if he is not sure which is which. If a developer is looking to increase linux mce's hardware compatability, he doesn't care what already works, he only wants to know of those devices that don't work. There is no need for both categories to be on the same page or in the same list, it just adds clutter and confusion. The only way the separate page option could be confusing is if the same device ends up on both lists, but this can just as easily happen with any of the other solutions. There is no additional cost in having a second page (seeing as how there are over 1800 of them), it costs the user nothing to add their hardware to working_hardware rather than hardware_status#working. If the nonworking page doesnt get visited much, then there has been the benefit of not cluttering up information people do want with information they don't. If, on the other hand, the non working page gets visited lots, those users will have benefited by not having to trawl through a list containing hundreds of working devices to find the information on the few they are after. It's a win-win situation.
--[[User:Macca|Macca]] 05:16, 9 September 2007 (MST)

Both single page options will become unwieldy as the list grows.

that's contradicts what you said about the good hardware list being much bigger than the bad list.
I get that you just want two lists, but for users who are not so inclined to do a bunch of digging and comparing and searching between lists, we need a single page to do this job. It would be very helpful to have a table with an '''at-a-glance''' graphic that told the overall story about the device. r/y/g
I think that you also overlook how difficult it is to know when something has an unknown status. It'd give me a much better feeling if I went to a single hardware page and saw all the other Hauppauge devices, with r/y/g statues and not the one I have or consider buying.. It would tell me instantly that the status is not known. How can I get this with your multiple pages ?
[[User:Trout|Trout]] 09:23, 9 September 2007 (MST)
*Why would users have to do 'a bunch of digging and comparing and searching between lists'? If a user wants to know if tv tuner brand_x model_y works in linuxmce, they type brand_x model_y into the search box. Instant result whatever the status. If a user is looking to get some new hardware and wants to know what works with linuxmce, they go to the working list, pick a tv tuner card and do some research on price, availabliity, features etc. If they dont like it, they go back to the list and pick another one.--[[User:Macca|Macca]] 18:16, 9 September 2007 (MST)

== Categories are just fine ==

Users can either find their hardware by name, or use the subcategories to find specific hardware by type. As far as I'm concerned all the other lists can go since they are a nuisance to maintain and add very little extra value.

-- [[User:Zaerc|Zaerc]] 10:51, 9 September 2007 (MST)

* so you are for [[Talk:Suggested hardware#no status list at all|no status list at all]]. For me that's insane because you then need to goto each hardware page to find the status. On this issue, I agree with [[User:Macca|Macca]] [[User:Trout|Trout]] 13:30, 9 September 2007 (MST)

== other concerns ==

In my opinion the focus should be on getting more information in here, and making 1, 2 or 3 more pages on which extra information has to be kept up to date is not really helping. This is not supposed to be a shopping list, but a growing source of information to which people should add themselves with as little hassle as possible. But if you guys want to maintain such lists then you have my blessing. I just think that every piece of hardware deserves it's own page.

--[[User:Zaerc|Zaerc]] 14:07, 9 September 2007 (MST)
*Zaerc, i know that you are an active user here and i appreciate your comments. No doubt you have seen posts in the forum along the lines of 'what hardware will work with linux mce'. There are a fair few of them at the moment and it is only going to get worse over time. This is the problem that i am trying to address. If we have a sticky subject in the forum pointing these individuals to a page in the wiki it frees up users from answering the same questions over and over, and the important or interesting posts wont get lost in the noise. We definately need a seperate page for each device, no arguments there. See my notes about templates above, i would value some input.--[[User:Macca|Macca]] 18:16, 9 September 2007 (MST)

* I agree that each piece of hardware deserves it's own page. But also an overview page with links to all these individual hardware pages is needed IMHO. [[User:Trout|Trout]] 14:42, 9 September 2007 (MST)

== Yet another opinion ==

First of all, lets keep things simple:

We make categories, motherboards, tv-cards, gfx-card, soundcards etc.

Then, list all hardware that's been tested, on that page and the result, if i want more info about a particular motherboard, tv-card etc - I click it and get additional info. Easy to maintain, easy to add entries etc.

As it is now, it's like a huge pile of info, not much structure too it, I'd love to help out and see this grow into something really useful and easy.

[[User:Samme|Samme]] 04:52, 10 September 2007 (MST)

Talk:Suggested hardware

2007-09-10T22:44:39Z

Macca: /* A single page */

May I suggest using seperate hierarchical categories under Hardware instead of sections? I know it's a bit of a hassle since we're the first, but I'm hoping everybody will add their own hardware over time. Anyway, thanks for helping out, much appreciated. --[[User:Zaerc|Zaerc]] 08:49, 8 July 2007 (MST)

I suggest this page should be redirected to [[tested good hardware]] and [[tested bad hardware]].--[[User:Macca|Macca]] 02:56, 3 September 2007 (MST)
* Uh, you can't redirect to 2 different places. Maybe you could provide some argument for maintaining 2 separate pages. Otherwise your comment is not useful.

Macca, I think that the opposite should happen. [[tested good hardware]] and [[tested bad hardware]] should be redirected here. There's nothing worse than having to look on 2 pages and still not knowing the answer. There are 3 states of hardware good, bad and unknown. So you should at least promote a page called "untested hardware". Now if I have a piece of hardware I'd have to check [[tested good hardware]], [[tested bad hardware]] and "untested hardware" in order to know the status of my device. IMHO that sucks. Why can't I just go to 1 page and see what the status of my device is ? I suggest a table with a status column. --[[User:Trout|Trout]] 16:49, 4 September 2007 (MST)

I don't want to get into a turf war or pissing contest here. That helps no-one. A few notes;
*Any list of this kind needs to be clear and concise. Currently the suggested_hardware page is neither.
*For ease of use, the list should be alphabetised. Is there a way to do this automatically?
*The device naming convention should be standardised. ManufacturerName_ModelName works well and seems to be widely in use on this wiki.
*Similarily there should be a standard layout for the device articles. At the very top should be a status section stating if it works, what version of linuxmce it works with (future-proofing. Like all things, easy doing it from the start, hard to add on later) etc. This should be short and to the point, any extra information about why it doesn't work etc should go in the problems and pitfalls section. This layout should also include a personal experience section (at the end) which users should tag. This allows follow up questions on the forum or the discussion page. Maybe we should create some templates called template_motherboard or motherboard_layout for each device type?
*If the status of a device is not known, it doesn't go on the list. Otherwise you end up with a list of every motherboard etc known to man. There are [[http://motherboards.org other sites]] that do this, and far better than we could here.
*Is it possible to set up a table that can be filtered or sorted?
*Maybe a traffic light system? Green works, Red doesn't and Yellow works but maybe isn't worth the trouble( or maybe experimental).
*Page naming. Maybe hardware_status? The name suggested_hardware sounds like it should perform the same function as what_hardware_will_i_need or maybe a list for a complete, top-of-the-line do-everything system. Tested_hardware doesn't sound quite right either.
*It should be linked prominently on the main page of the wiki, maybe also a sticky subject in the forums.
There's probably lots more, but its late here, and i'm tired :) --[[User:Macca|Macca]] 07:08, 7 September 2007 (MST)

==Our options for a hardware status list==
===A table===
No good. Sure, we could make a kick-ass table that users could sort on manufacturer name, device type, device status etc. But it would be impossible for users to add new hardware to. Even a simple 2 column table is difficult to add new data to. For a new user, they will take one look at the edit page and run screaming. Not the effect we are after. Unless we have a sole person maintaining the table (which defeats the point of a wiki) it wont work.
* In a wiki, you must assume that editors have the know-how to edit rather than just type. You are trying to say the opposite here. Your argument of only one maintainer is absurd.
**I don't think you know what goes into creating a table. I thought a table would be the perfect solution, but i went and did some research before i wrote the 'options' piece. Even a table with only two columns is difficult to add new data to. Add in another column or some different sections or start colouring cells and even experienced wiki users will find it incredibly difficult adding new devices. Tables in wikis render differently in each browser, so a user (even if they know what they are doing) could add something in IE, for example, that will look fine to him, but break the page for firefox users. Having a page that breaks if a user puts a space or a single quote in the wrong spot is not a good idea. It would be an incredibly frustrating experience for the user and not only would they not add their device to the list, they may not add information to any other wiki pages. The harder a page is to edit and the more knowledge required to do so reduces the likelyhood that users will add their own information. What we should be aiming for is lowest-common-denominator. If a page is easy to add information to then more users are likely to add theirs, especially if all they have to do is copy what was done before them, no special knowledge needed. The point of a wiki is that ANYBODY can edit it, creating complex pages just adds barriers to entry. --[[User:Macca|Macca]] 18:16, 9 September 2007 (MST)
*** ANYBODY can edit. At the end of the day, they'll always find a way to communicate that they have hardware they'd like to add. And it may need to be formatted in the table correctly. I disagree with '''The point of a wiki is that ANYBODY can edit it''' because the point of a wiki is that EVERYONE can edit it. The point is important because it means 1. we don't rely on a single user to maintain. 2. One person can add it incorrectly and another can format it more correctly. Also I don't know why you are trying to please the editors rather than the readers. Typically a page is read significantly more than it's written. So why not make it good for the readers and *slightly* harder for the writers? [[User:Trout|Trout]] 02:41, 10 September 2007 (MST)

===A single page===
2 options here, separate working and nonworking sections, or everything together relying on comments to tell the difference between them.
*2 sections. Easy to read, easy to navigate, easy to edit. Alphabetising sub-sections means both sections will keep same heirachy. Page size is larger. Chance for users to put devices in the wrong section.
*Comments. Messy, hard to tell status at a glance. Problems with users adding long-winded comments or not adding comments at all (especially when there is no page for the device). Page size grows at least 2x faster than number of devices. Is there an upper limit for wiki page size?
** Actually there are more options than 2.
* Create a traffic light system Red = not working, yellow = partially not working, green = fully working (non-existance in the table means unknown) Then you can tell at a glance, what the full story about a device is.[[User:Trout|Trout]] 09:09, 9 September 2007 (MST)
**Thats really just the same as the comments option. You are relying on aditional information to know the status of the device. What if a user doesnt put the colour in? what if the page for a device doesn't exist? The text will be red. Does that mean that the device doesn't work? Introducing a partial option is not a good idea. How many shades of gray should we cater for? If a device works (that is performs its primary intended function) then it goes on the working list. If i have to do some mucking around first, recompile the kernel, add text to a config file, sacrifice a goat on the full moon, but my video card outputs video or my sound card outputs sound then it goes on the working list (even if secondary features dont work yet). If i do all of the above and my sound card works as a DAC for an oscilloscope but doesnt output sound, then it goes on the nonworking list.--[[User:Macca|Macca]] 18:16, 9 September 2007 (MST)
*** It must be nice to see the world in such black and white. Okay, so what about a video card that works but does not support transparency ? Which pile ? [[User:Trout|Trout]] 02:33, 10 September 2007 (MST)
**** You mean any video card that doesnt use an nvidia chipset? Quite obviously the working pile. Transparency is not necessary for running linuxmce and the lack of it doesnt prevent any of the core features from working. i can still watch vidoes, surf the web and control any device in my house. There are going to be few devices that work 100%. Say i have 2 tv tuners, one supports fm radio reception and one doesnt. both cards allow me to watch tv and record flawlessly. Most users arent going to care about fm radio. AFAIK it isnt even supported by linuxmce. So why should one card be labelled partially working when it performs equally as well as a card that is labelled as working? The point i am trying to make is that information about each device, what functions it performs (or doesnt perform), what voodoo it requires to get recognised, how many rs232 ports it has etc belongs on the page for that device. Requiring that information on multiple pages means thing will get out of date much easier. It is not that onerous to add just a link to a device page on the working or non working list, but if users have to retype what they just typed on another page, many are not going to bother. If we have a page that is just a list of links, no extra information, we can tell users that if a page for their device doesn't exist, they can create one simply by adding their device to the list. Hey presto, instantly users are adding their devices. (Sure they could create their device, edit that page and then add it to the list, but we just cut out a step and got the users to do our job for us. If only there was a way to automatically create a page based on a template. we wouldn't have to do any work at all!)--[[User:Macca|Macca]] 15:44, 10 September 2007 (MST)

* Take a look at this page and see if it is one that can be adopted. [[HCL]] It appears to be a hold over from the Pluto guys, but it looks like it may have potential.--[[User:Rwilson131|Rwilson131]] 11:29, 9 September 2007 (MST)
**Thanks for your input. That page is too complex, Imagine having 50 devices on there. all that information belongs on the page for each individual device.--[[User:Macca|Macca]] 18:16, 9 September 2007 (MST)

===multiple pages===
No confusion over whether device works or not. Hardware support on linux is pretty good, the list of working devices is going to be far longer than the list of those that dont work. Keeping the lists separate makes both of them easier to read and edit. If the sections are alphabetised then both pages will keep the same heirachy automatically.
* Big time confusion. Ok if I look at the "good" page and I see my device, then there's no confusion. But if it's not listed, I am absolutely confused. Hmmm is it not working? Is it unknown? Maybe it's partially working and not listed on this "good hardware" page.
* ''the list of working devices is going to be far longer than the list of those that dont work. Keeping the lists separate makes both of them easier to read and edit.'' - Uh no, it does not.
* ''If the sections are alphabetised then both pages will keep the same heirachy automatically.'' - again, no. especially when more and more cross devices come about. for example the iPhone. should it be listed under PDA or phone? Hmm I wonder if it'll match the separately maintained good/bad hardware page. I assume that when you say automatically you mean naturally.[[User:Trout|Trout]] 09:16, 9 September 2007 (MST)
**Naturally is a better word, thanks. Motherboards may have video chips or sound chips on board. Does this mean it should be listed under video cards or sound cards? I think not. Most devices will have more than one funtion, each device should be listed under the section that matches its primary intended function. The iphone is primarily a phone, and so goes in the phone section.--[[User:Macca|Macca]] 18:16, 9 September 2007 (MST)
===working and nonworking categories===
No need to maintain a separate status page, just go to category:working and there it is, automatically alphabetised for you. How do you separate the motherboards from the mobile phones from the tv tuners though?

* Traffic light system.[[User:Trout|Trout]] 09:17, 9 September 2007 (MST)
**I am not sure what you mean here. There is no way to add additional information for each device to the categories page.--[[User:Macca|Macca]] 18:16, 9 September 2007 (MST)
*** Oops, you're right. [[User:Trout|Trout]] 02:28, 10 September 2007 (MST)

===no status list at all===
Rely on individual device pages. Not really a good solution, provides no overview so users wanting to get a list of known working components to build their system have to trawl through each device page individually.
* Agreed :) [[User:Trout|Trout]] 09:18, 9 September 2007 (MST)

===''conclusion''===
The categories option seems elegant at first, making use of inbuilt wiki tools to do our job for us, but it only does half the job. It can't categorise the working devices by device-type on the one page. Most devices don't have helpful names, so users wont know if sony_xyz123 is a television or an a/v reciever or a dvd jukebox. This makes it almost useless.

Both single page options will become unwieldy as the list grows. It is too easy for users to add devices to the wrong section or not put comments in etc.
Separating categories reduces confusion. Have a look at the [[suggested hardware]] page. Tell me which of those tv tuner cards work and which don't. You can't. None of them have any information, one doesn't even have its own page. Now look at the tv tuners on the [[tested good hardware]] page. No confusion there, all of them work. The need for a list of known working hardware is far greater than the need for a list of hardware that doesnt work. Why clutter up the former with the latter? It just doesn't make sense. If a user has a specific peice of hardware and wants to know if it works or not, they can type the name in the search box and get the answer instantly. If a user wants to know what hardware definately works with linux mce so he can write a shoppping list, he doesn't want to be confronted with a list that contains both working and nonworking devices, especially if he is not sure which is which. If a developer is looking to increase linux mce's hardware compatability, he doesn't care what already works, he only wants to know of those devices that don't work. There is no need for both categories to be on the same page or in the same list, it just adds clutter and confusion. The only way the separate page option could be confusing is if the same device ends up on both lists, but this can just as easily happen with any of the other solutions. There is no additional cost in having a second page (seeing as how there are over 1800 of them), it costs the user nothing to add their hardware to working_hardware rather than hardware_status#working. If the nonworking page doesnt get visited much, then there has been the benefit of not cluttering up information people do want with information they don't. If, on the other hand, the non working page gets visited lots, those users will have benefited by not having to trawl through a list containing hundreds of working devices to find the information on the few they are after. It's a win-win situation.
--[[User:Macca|Macca]] 05:16, 9 September 2007 (MST)

Both single page options will become unwieldy as the list grows.

that's contradicts what you said about the good hardware list being much bigger than the bad list.
I get that you just want two lists, but for users who are not so inclined to do a bunch of digging and comparing and searching between lists, we need a single page to do this job. It would be very helpful to have a table with an '''at-a-glance''' graphic that told the overall story about the device. r/y/g
I think that you also overlook how difficult it is to know when something has an unknown status. It'd give me a much better feeling if I went to a single hardware page and saw all the other Hauppauge devices, with r/y/g statues and not the one I have or consider buying.. It would tell me instantly that the status is not known. How can I get this with your multiple pages ?
[[User:Trout|Trout]] 09:23, 9 September 2007 (MST)
*Why would users have to do 'a bunch of digging and comparing and searching between lists'? If a user wants to know if tv tuner brand_x model_y works in linuxmce, they type brand_x model_y into the search box. Instant result whatever the status. If a user is looking to get some new hardware and wants to know what works with linuxmce, they go to the working list, pick a tv tuner card and do some research on price, availabliity, features etc. If they dont like it, they go back to the list and pick another one.--[[User:Macca|Macca]] 18:16, 9 September 2007 (MST)

== Categories are just fine ==

Users can either find their hardware by name, or use the subcategories to find specific hardware by type. As far as I'm concerned all the other lists can go since they are a nuisance to maintain and add very little extra value.

-- [[User:Zaerc|Zaerc]] 10:51, 9 September 2007 (MST)

* so you are for [[Talk:Suggested hardware#no status list at all|no status list at all]]. For me that's insane because you then need to goto each hardware page to find the status. On this issue, I agree with [[User:Macca|Macca]] [[User:Trout|Trout]] 13:30, 9 September 2007 (MST)

== other concerns ==

In my opinion the focus should be on getting more information in here, and making 1, 2 or 3 more pages on which extra information has to be kept up to date is not really helping. This is not supposed to be a shopping list, but a growing source of information to which people should add themselves with as little hassle as possible. But if you guys want to maintain such lists then you have my blessing. I just think that every piece of hardware deserves it's own page.

--[[User:Zaerc|Zaerc]] 14:07, 9 September 2007 (MST)
*Zaerc, i know that you are an active user here and i appreciate your comments. No doubt you have seen posts in the forum along the lines of 'what hardware will work with linux mce'. There are a fair few of them at the moment and it is only going to get worse over time. This is the problem that i am trying to address. If we have a sticky subject in the forum pointing these individuals to a page in the wiki it frees up users from answering the same questions over and over, and the important or interesting posts wont get lost in the noise. We definately need a seperate page for each device, no arguments there. See my notes about templates above, i would value some input.--[[User:Macca|Macca]] 18:16, 9 September 2007 (MST)

* I agree that each piece of hardware deserves it's own page. But also an overview page with links to all these individual hardware pages is needed IMHO. [[User:Trout|Trout]] 14:42, 9 September 2007 (MST)

== Yet another opinion ==

First of all, lets keep things simple:

We make categories, motherboards, tv-cards, gfx-card, soundcards etc.

Then, list all hardware that's been tested, on that page and the result, if i want more info about a particular motherboard, tv-card etc - I click it and get additional info. Easy to maintain, easy to add entries etc.

As it is now, it's like a huge pile of info, not much structure too it, I'd love to help out and see this grow into something really useful and easy.

[[User:Samme|Samme]] 04:52, 10 September 2007 (MST)

Talk:Suggested hardware

2007-09-10T01:16:14Z

Macca:

Talk:Suggested hardware

2007-09-09T12:16:39Z

Macca:

Talk:Suggested hardware

2007-09-07T14:08:09Z

Macca:

I suggest this page should be redirected to [[tested good hardware]] and [[tested bad hardware]].--[[User:Macca|Macca]] 02:56, 3 September 2007 (MST)

May I suggest using seperate hierarchical categories under Hardware instead of sections? I know it's a bit of a hassle since we're the first, but I'm hoping everybody will add their own hardware over time. Anyway, thanks for helping out, much appreciated. --[[User:Zaerc|Zaerc]] 08:49, 8 July 2007 (MST)

Macca, I think that the opposite should happen. [[tested good hardware]] and [[tested bad hardware]] should be redirected here. There's nothing worse than having to look on 2 pages and still not knowing the answer. There are 3 states of hardware good, bad and unknown. So you should at least promote a page called "untested hardware". Now if I have a piece of hardware I'd have to check [[tested good hardware]], [[tested bad hardware]] and "untested hardware" in order to know the status of my device. IMHO that sucks. Why can't I just go to 1 page and see what the status of my device is ? I suggest a table with a status column.

I don't want to get into a turf war or pissing contest here. That helps no-one. A few notes;
*A single page is best.
*Any list of this kind needs to be clear and concise. Currently the suggested_hardware page is neither.
*For ease of use, the list should be alphabetised. Is there a way to do this automatically?
*The device naming convention should be standardised. ManufacturerName_ModelName works well and seems to be widely in use on this wiki.
*Similarily there should be a standard layout for the device articles. At the very top should be a status section stating if it works, what version of linuxmce it works with (future-proofing. Like all things, easy doing it from the start, hard to add on later) etc. This should be short and to the point, any extra information about why it doesn't work etc should go in the problems and pitfalls section. This layout should also include a personal experience section (at the end) which users should tag. This allows follow up questions on the forum or the discussion page. Maybe we should create some templates called template_motherboard or motherboard_layout for each device type?
*If the status of a device is not known, it doesn't go on the list. Otherwise you end up with a list of every motherboard etc known to man. There are [[http://motherboards.org other sites]] that do this, and far better than we could here.
*Is it possible to set up a table that can be filtered or sorted?
*Maybe a traffic light system? Green works, Red doesn't and Yellow works but maybe isn't worth the trouble( or maybe experimental).
*Page naming. Maybe hardware_status? The name suggested_hardware sounds like it should perform the same function as what_hardware_will_i_need or maybe a list for a complete, top-of-the-line do-everything system. Tested_hardware doesn't sound quite right either.
*It should be linked prominently on the main page of the wiki, maybe also a sticky subject in the forums.
There's probably lots more, but its late here, and i'm tired :) --[[User:Macca|Macca]] 07:08, 7 September 2007 (MST)

Information for Australian users

2007-09-04T01:16:48Z

Macca: added sudo to commands

== MythTV ==
MythTV works fine with Australian Free-To-Air digital television. There are 2 main sources for Electronic Program Guide information, [http://www.icetv.com.au iceTV] and [http://www.tuhs.org/twiki/bin/view/TVGuide/WebHome The Australian Community TV Guide](ozTiVo). iceTV is a comercial offering, and costs about AU$3 per week. ozTiVo is free, however both sites require registration.

=== Setup ===
*Visit one (or both) of the above sites to register and set up your profile (be sure to select xmltv for the data format).
*Get [http://www.cse.unsw.edu.au/~willu/xmltv/tv_grab_au_reg this script] and install it in /usr/local/bin
**Make sure it is executable: ''sudo chmod +x tv_grab_au_reg''
**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''.
*Run MythTV-setup and add a new video source to use 'tv_grab_au' (call it something like FTA).
**Set 'TimeOffset' to 'Auto'
**Configure a capture card to use the video source (FTA)
**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.
**Exit Setup, don't run mythfilldatabase.
*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).
*Run mythfilldatabase( start MythTV-setup and then exit, hit yes when prompted.
*Enjoy your new EPG

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

Information for Australian users

2007-09-04T01:14:48Z

Macca: added link to foxtel info

== MythTV ==
MythTV works fine with Australian Free-To-Air digital television. There are 2 main sources for Electronic Program Guide information, [http://www.icetv.com.au iceTV] and [http://www.tuhs.org/twiki/bin/view/TVGuide/WebHome The Australian Community TV Guide](ozTiVo). iceTV is a comercial offering, and costs about AU$3 per week. ozTiVo is free, however both sites require registration.

=== Setup ===
*Visit one (or both) of the above sites to register and set up your profile (be sure to select xmltv for the data format).
*Get [http://www.cse.unsw.edu.au/~willu/xmltv/tv_grab_au_reg this script] and install it in /usr/local/bin
**Make sure it is executable: ''chmod +x tv_grab_au_reg''
**Symlink /usr/local/bin/tv_grab_au to tv_grab_au_reg with ''ln -s /usr/local/bin/tv_grab_au_reg /usr/local/bin/tv_grab_au''.
*Run MythTV-setup and add a new video source to use 'tv_grab_au' (call it something like FTA).
**Set 'TimeOffset' to 'Auto'
**Configure a capture card to use the video source (FTA)
**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.
**Exit Setup, don't run mythfilldatabase.
*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).
*Run mythfilldatabase( start MythTV-setup and then exit, hit yes when prompted.
*Enjoy your new EPG

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

Australia

2007-09-04T01:09:00Z

Macca:

#REDIRECT [[Information for australian users]]

Information for Australian users

2007-09-03T10:52:10Z

Macca: work in progress

== MythTV ==
MythTV works fine with Australian Free-To-Air digital television. There are 2 main sources for Electronic Program Guide information, [http://www.icetv.com.au iceTV] and [http://www.tuhs.org/twiki/bin/view/TVGuide/WebHome The Australian Community TV Guide](ozTiVo). iceTV is a comercial offering, and costs about AU$3 per week. ozTiVo is free, however both sites require registration.

=== Setup ===
*Visit one (or both) of the above sites to register and set up your profile (be sure to select xmltv for the data format).
*Get [http://www.cse.unsw.edu.au/~willu/xmltv/tv_grab_au_reg this script] and install it in /usr/local/bin
**Make sure it is executable: ''chmod +x tv_grab_au_reg''
**Symlink /usr/local/bin/tv_grab_au to tv_grab_au_reg with ''ln -s /usr/local/bin/tv_grab_au_reg /usr/local/bin/tv_grab_au''.
*Run MythTV-setup and add a new video source to use 'tv_grab_au' (call it something like FTA).
**Set 'TimeOffset' to 'Auto'
**Configure a capture card to use the video source (FTA)
**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.
**Exit Setup, don't run mythfilldatabase.
*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).
*Run mythfilldatabase( start MythTV-setup and then exit, hit yes when prompted.
*Enjoy your new EPG

You can use the same process to import foxtel channels, call it foxtel instead of FTA.

What hardware I will need

2007-09-03T10:13:54Z

Macca: removed reference to edgy eft

= Hardware requirements =
== Minimum == Standard Definition (SD) DVD and audio (MP3, OGG, etc) player.
* The simple answer is a machine that can install and boot [http://www.ubuntu.com Ubuntu] (presently Feisty Fawn 7.04).

== Standard == Standard Definition DVR + Audio/Video player
From the [http://www.mythtv.org/docs/mythtv-HOWTO-3.html MythTV Hardware Requirements] page.
=== CPU ===
* A PIII/733MHz system can encode one video stream using the MPEG-4 codec using 480x480 capture resolution. This does not allow for live TV watching, but does allow for encoding video and then watching it later.
* A developer states that his AMD1800+ system can almost encode two MPEG-4 video streams and watch one program simultaneously.
* A PIII/800MHz system with 512MB RAM can encode one video stream using the RTjpeg codec with 480x480 capture resolution and play it back simultaneously, thereby allowing live TV watching.
* A dual Celeron/450MHz is able to view a 480x480 MPEG-4/3300kbps file created on a different system with 30% CPU usage.
* A P4 2.4GHz machine can encode two 3300Kbps 480x480 MPEG-4 files and simultaneously serve content to a remote frontend.
* A video capture card supported by Linux.

=== Firewire (Optional) ===

You may use the [[Firewire]] output of the [[Motorola DCT6200]] or the [[Motorola SA3250|SA3250]]. If your provider uses 5C encryption on a particular channel, you won't be able to get any content.
DBoxII or other devices running Neutrino

You may use the Ethernet port of an DBoxII or a similar device to capture MPEG2. Your set top box has to be running the Neutrino GUI.
USB Capture Devices.

The Plextor ConvertX PVR devices are supported through Linux drivers available from http://www.plextor.com/english/support/LinuxSDK.htm. MythTV uses the Plextor to capture hardware encoded MPEG-4, so the host CPU requirements are low.

[[Hauppauge]] [[WinTV-PVR-USB2]] (driver available at http://www.isely.net/pvrusb2/) emulates a PVR-x50 card.
IP Recorder (RTSP, RTS, UDP)

MPEG-2, MPEG-4 and H.264 internet TS stream recording is supported using the IPTV recorder in MythTV. This recorder expects the channels to be supplied as a m3u playlist. If your DSL/Fiber provider supplies television service, but does not provide a m3u playlist for the channels, you can construct one for your own use. You do not need to download it from the same server as the streams themselves, and can also read it from a file if this is more convenient.

=== Sound card ===

The system needs a sound card or an on-board equivalent on the motherboard to play back and in most cases, to record sound. Any sound card that can be operated by the [[ALSA]] (Advanced Linux Sound Architecture) kernel modules will work with MythTV. However, some cards and drivers will provide better quality or compatibility than others. In particular, many audio devices included on motherboards can be problematic.

The usual practice for capturing the audio associated with the video is to run a cable from an audio output on the video capture card to the Line input on a sound card. However, some video capture cards provide on-board audio capabilities that work with the kernel btaudio module instead, thereby eliminating the need for a cable. This is useful if you will be using multiple capture cards in a single chassis, since each capture card will not need its own sound card. Note that a separate sound card is still required for playback when using btaudio, and that often the audio recorded in this way will be mono only. See the btaudio section for more information.

==== See Also ====
[[Tested good hardware]], [[Tested bad hardware]], [[Suggested hardware]]

== Forum Discussions ==
* [http://forum.linuxmce.com/index.php?topic=1711.0 Building a New Rig]
* [http://forum.linuxmce.com/index.php?topic=1353.msg8341#msg8341 For those wanting to roll your own box ...]

[[ Category : Hardware ]]

What hardware I will need

2007-09-03T09:58:52Z

Macca: added links to tested good (and bad) hardware

= Hardware requirements =
== Minimum == Standard Definition (SD) DVD and audio (MP3, OGG, etc) player.
* The simple answer is a machine that can install and boot [http://www.ubuntu.com Ubuntu] (presently Edgy Eft 6.10).

== Standard == Standard Definition DVR + Audio/Video player
From the [http://www.mythtv.org/docs/mythtv-HOWTO-3.html MythTV Hardware Requirements] page.
=== CPU ===
* A PIII/733MHz system can encode one video stream using the MPEG-4 codec using 480x480 capture resolution. This does not allow for live TV watching, but does allow for encoding video and then watching it later.
* A developer states that his AMD1800+ system can almost encode two MPEG-4 video streams and watch one program simultaneously.
* A PIII/800MHz system with 512MB RAM can encode one video stream using the RTjpeg codec with 480x480 capture resolution and play it back simultaneously, thereby allowing live TV watching.
* A dual Celeron/450MHz is able to view a 480x480 MPEG-4/3300kbps file created on a different system with 30% CPU usage.
* A P4 2.4GHz machine can encode two 3300Kbps 480x480 MPEG-4 files and simultaneously serve content to a remote frontend.
* A video capture card supported by Linux.

=== Firewire (Optional) ===

You may use the [[Firewire]] output of the [[Motorola DCT6200]] or the [[Motorola SA3250|SA3250]]. If your provider uses 5C encryption on a particular channel, you won't be able to get any content.
DBoxII or other devices running Neutrino

You may use the Ethernet port of an DBoxII or a similar device to capture MPEG2. Your set top box has to be running the Neutrino GUI.
USB Capture Devices.

The Plextor ConvertX PVR devices are supported through Linux drivers available from http://www.plextor.com/english/support/LinuxSDK.htm. MythTV uses the Plextor to capture hardware encoded MPEG-4, so the host CPU requirements are low.

[[Hauppauge]] [[WinTV-PVR-USB2]] (driver available at http://www.isely.net/pvrusb2/) emulates a PVR-x50 card.
IP Recorder (RTSP, RTS, UDP)

MPEG-2, MPEG-4 and H.264 internet TS stream recording is supported using the IPTV recorder in MythTV. This recorder expects the channels to be supplied as a m3u playlist. If your DSL/Fiber provider supplies television service, but does not provide a m3u playlist for the channels, you can construct one for your own use. You do not need to download it from the same server as the streams themselves, and can also read it from a file if this is more convenient.

=== Sound card ===

The system needs a sound card or an on-board equivalent on the motherboard to play back and in most cases, to record sound. Any sound card that can be operated by the [[ALSA]] (Advanced Linux Sound Architecture) kernel modules will work with MythTV. However, some cards and drivers will provide better quality or compatibility than others. In particular, many audio devices included on motherboards can be problematic.

The usual practice for capturing the audio associated with the video is to run a cable from an audio output on the video capture card to the Line input on a sound card. However, some video capture cards provide on-board audio capabilities that work with the kernel btaudio module instead, thereby eliminating the need for a cable. This is useful if you will be using multiple capture cards in a single chassis, since each capture card will not need its own sound card. Note that a separate sound card is still required for playback when using btaudio, and that often the audio recorded in this way will be mono only. See the btaudio section for more information.

==== See Also ====
[[Tested good hardware]], [[Tested bad hardware]], [[Suggested hardware]]

== Forum Discussions ==
* [http://forum.linuxmce.com/index.php?topic=1711.0 Building a New Rig]
* [http://forum.linuxmce.com/index.php?topic=1353.msg8341#msg8341 For those wanting to roll your own box ...]

[[ Category : Hardware ]]

Talk:Suggested hardware

2007-09-03T09:56:29Z

Macca:

Leadtek DTV1000T

2007-09-03T09:53:47Z

Macca: New page

This card works out of the box. In Mythtv-setup, under capture cards, select 'DVB DTV capture card (v3.x)' for the card type. Set 'DVB Card Number' to 0 ( for the first card, 1 for 2nd card etc)

The remote control that comes with this card is not yet supported.

Building From Source

2007-08-30T05:37:38Z

Macca: added link to mirrors page

'''Source code for LinuxMCE 0704 is on the [[Mirrors]]. This page hasn't been updated for 0704 yet'''

== Before You Begin==
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.

Also since this script was written with a single goal in mind, to get everything done, i might left by mistake some lines of code that may not run on your computers (hardcoded paths and stuff like this) but i relay on you to at lease try to fix them before asking for help but if the problem is not so obvious i would gladly give you advices.

== The Build Scripts ==
The build scripts are in sourceforge svn so to get them you will need subversion installed.
sudo apt-get install subversion
svn co https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/trunk/src/Ubuntu_Helpers

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.

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:

*''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.
*''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.
*''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.
*''Checkout_Svn'': Will do a svn checkout on sourceforge to get all the needed sources
*''Build_Replacements'': LinuxMCE needs some 3rd party some packages that are not part of ubuntu distribution. This function will build / get them for you.
*''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.
*''Import_Build_Database'': Imports a fresh copy of the pluto databases needed at build time.
*''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.
*''Build_Pluto_Stuff'': Uses MakeRelase to compile the sources and build packages out of them
*''Create_Local_Repository'': Optional you can create a local repository so that you can easily test your debs.

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.

== Source Code Location ==

Our source code is located on sourceforge and you can get it by svn from : https://linuxmce.svn.sourceforge.net/svnroot/linuxmce/

The png used for the skins are located here : http://www.linuxmce.com/linuxmce-skins-1.0.tar.bz2

The sql dumps of the databases needed for the build : http://www.linuxmce.com/linuxmce-databases-1.0.tar.gz

[[Category: Tutorials]]

Installation Guide

2007-08-30T05:30:29Z

Macca: added link to install fault log (http://linuxmce.org/troubles.php)

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

''' If you want to install LinuxMCE using the DVD check these steps [[DVD_Installation]]'''

Steps for installing Linux MCE on an Kubuntu 7.04 (Feisty Fawn) system :

'''1.''' Take an Kubuntu install already configured with Internet connection (Configure your network card and DNS). If you don't have an Kubuntu system already installed please follow these generic steps:

*Take an [http://www.kubuntu.org/download.php Kubuntu 7.04 Live CD] and boot from it.
*Choose 'Start or install Kubuntu'
*When Kubuntu's desktop appears, double-click on 'Install'
*A short wizard will start and guide you; Select the language and press 'forward'
*Choose your timezone and press 'forward'
*Select the keyboard layout
*Choose desktop name, a user name and a password
*Select the partitioning options for your disk: erase the entire disk or just manually edit the options.
*Ready to install.
*Reboot the system and remove the Live CD
 

'''2.''' From within the Kubuntu 7.04 desktop, open Firefox (the orange and blue icon at the top), and go to [http://www.linuxmce.com www.linuxmce.com] and select 'Download Instructions' to download the Linux MCE CD`s or the DVD on your machine. Or just use this direct link [http://wiki.linuxmce.org/index.php/Mirrors click here]

[[Image:Good1.jpg|400px]]

'''3.''' Once you have downloaded the packages, proceed with the installation. First, you have to install mce-installer, which is the software that will guide you through the installation. Right-click on it, go to Kubuntu Package Menu -> Install Package.

[[Image:Inst1.jpg|400px]]

Alternatively, you can install the mce-installer from a command prompt without the need to burn the ISOs as follows:
cd ''/directory/where/the/downloaded/iso/files/are/''
mkdir -pv mnt
sudo mount LinuxMCE_0704_CD1.iso mnt/ -o loop
sudo dpkg -i mnt/mce-installer_2.0.1-1_i386.deb
sudo umount mnt
rmdir -v mnt

'''4.''' The installer will have put an "Install Linux MCE" icon on your desktop. Double-click it to start the installation process. A window will appear saying that you will be notified when updates are available.

[[Image:Snapshot1.JPG|400px]]

After this you have to choose if you want a dedicated core or a hybrid ([http://linuxmce.com/wiki/index.php/Getting_Started#A_Dedicated_Core click here]to find out the difference between a core and a hybrid), and then click on "Forward" button.

[[Image:Snapshot2.JPG|400px]]

'''5.''' *Only for Nvidia cards - LinuxMCE will detect that you are using a nVidia Card, but you are not using the proprietary video driver. Only that driver works well with LinuxMCE and nvidia cards and it will ask you it you want to switch to it now.

[[Image:Snapshot3.JPG|400px]]

'''6.''' The next screen will ask you want to keep your current network configuration or if you want to set your network options manually; then press "Forward".

[[Image:Snapshot4.JPG|400px]]

And then you must set your network using static IP or DHCP

[[Image:Snapshot5.JPG|400px]]

'''7.''' You have to choose a mirror

[[Image:Snapshot6.JPG|400px]]

'''8.''' In the next step you have 2 options :
*First it asks you if you want to Run a DHCP Server or not. LinuxMCE must be the DHCP server for your home 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 home you want to use as media stations.
*The other option asks if you want to keep the default Internal Network address or if you want to change it. If you have already a DHCP-Server running, choose also this option. You can then switch from 'manually' to 'DHCP'.

After that you must press 'Forward'.

[[Image:Snapshot7.JPG|400px]]

'''9.''' In the next window you need to choose what interface you want to use and you have to pick one of three possibilities.

[[Image:Snapshot8.JPG|400px]]

'''10.''' On the next step you have to choose if you want to install lame and libdvdcss and if it is legal in your country to use them.

[[Image:Snapshot9.JPG|400px]]

'''11.''' You have to select how do you plan to use your computer: Primarily used as a PC- you can start LMCE manually when you need it or A dedicated LinuxMCE and you can start Kubuntu when you need it.

[[Image:Snapshot10.JPG|400px]]

'''12.''' This step is very important you have to insert

LinuxMCE DISC 1

[[Image:Snapshot11.JPG|400px]]

LinuxMCE DISC 2

[[Image:Snapshot12.JPG|400px]]

Kubuntu 7.04 Live CD

[[Image:Snapshot13.JPG|400px]]

You can see the message about the Linux MCE system installation.

[[Image:Snapshot14.JPG|400px]]

Don't worry if the system seems to stop at points or report what seems like error messages.
This is normal since at places it will be testing drivers out, and is only there for the advanced Linux user.
You will get a dialog box if something really does go wrong. And, understand this may take a very long time
since it will in parallel be updating your Kubuntu system to the latest version. Just leave it for an hour
or two and come back later.

After the installation is done you’ll receive a message from the installer that will tell you to restart the system

[[Image:Snapshot15.jpg|400px]]

Next follow the [http://linuxmce.com/wiki/index.php?title=QuickStart_Guide Quick Start Guide] to tell LinuxMCE about how you want to use it.

Note that if you said you want LinuxMCE to startup by default, after rebooting you'll have LinuxMCE, not Kubuntu. If you will only use this as a media pc, that's fine; you won't ever need to access the Kubuntu desktop to set anything up and can do it all from either the LMCE UI and a remote control, or with the LMCE web admin panel using the web browser of any pc in your home. But, if you want to use this as a normal Kubuntu PC too, and you want to start Kubuntu after LinuxMCE is going, there's not yet an icon to switch to Kubuntu from within LinuxMCE, so press Ctrl+Alt+F2, login, and type StartX. If you said you want Kubuntu by default, it will boot to the Kubuntu desktop and you can choose Applications, Sound & Video, Start Media Center to start LinuxMCE manually. When both LinuxMCE and Kubuntu are running, you can toggle between them by pressing ctrl+alt+f7 for Kubuntu and ctrl+alt+F11 for LinuxMCE. Unfortunately, at this moment, once you start LinuxMCE there is no way to stop it. The Kubuntu integration is still a work in progress.

Getting Started

2007-08-28T04:30:08Z

Macca: removed reference to ubuntu 6.10

==Equipment: Picking The Right Components==

''See also: [[Tested good hardware]] and [[Tested bad hardware]]''

===The Core===

Most important, is the "core". This is the main LinuxMCE server that runs all the applications. The commercial version uses a high-end server with RAID-5 storage. You'll probably be able to get by with a good Pentium 4, at least 80 GB of storage and two network cards (Gigabit ideally).

It would be best to use a dedicated core, which means you'll end up putting this computer somewhere out of the way and not connecting a monitor to it. If you are using only one computer for your system, then you've chosen the "hybrid" system, which means that your core will also be your media player. You'll definitely need a monitor or TV for this system!

===Media Directors===

Note that each media director will need a Bluetooth dongle if you want to use a Bluetooth mobile phone as the remote in that area. To control your a/v equipment using infrared, you will need an interface module (global cache gc100). This interface module also gives you extra serial ports. So, in this example, the TV is controlled by infrared, and the receiver by RS232.

''See also: [[Sound Cards]] and [[Network_Boot_for_Media_Directors]]''

===Orbiters===

===Network Attached Storage===

An alternative to having a lot of storage space in the core is to have a small hard drive for the core and store all your files on a [[Network Attached Storage|network attached storage]] (or NAS) server. The [http://www.buffalotech.com/products/network-storage/terastation/ Buffalo TeraStation] is 1.0 TeraByte RAID-5 and under $1K(US). Having a NAS will allow you to not lose your precious media files. You'll likely want the larger storage for your collection of music and videos. Keep in mind that your LinuxMCE system can also record TV shows (using MythTV) and video from your security cameras (using Motion).

===Additional Devices===

''See also [[Recommended Accessories]]''

Optionally, you may want the aforementioned home automation devices for controlling your lights. Also, optionally, you may want security cameras, plasma screen TV, a streaming media music player such as the [http://www.slimdevices.com Squeezebox], an alarm system with a serial interface, etc. Some of these devices need ''another'' device called a [http://www.globalcache.com/products/gc-index.html gc100]. This allows devices that communicate using a serial port (good alarm panels) or infrared (like your TV) to connect to the network and talk with your LinuxMCE core.

===Location Considerations===

This section has been moved to [[Choosing Locations]].

===Wiring Considerations===

''Main article: [[Wiring Considerations]]''

Once LinuxMCE is installed, just treat it like an appliance--plug it in, turn it on, and leave it alone. The great news is that don't need to install any software on the media PCs that will be used as media directors. You can leave whatever operating system is on there, such as Windows, untouched-they will do a [[Network Boot for Media Directors]] when you want to use them as a Media Director.

The only special requirement is that the LinuxMCE Core needs to be your DHCP server so that it can offer the plug-and-play and network boot services. You cannot have 2 DHCP servers on the same network (not easily at least). In our Core, we provide [[Why dual network cards?|dual network cards]] one for the "external" network, where your internet is connected, and one for the "internal" network within the house, and into which all your devices are connected. This makes LinuxMCE act as a firewall, and allows it to co-exist with another DHCP server. If you have a DSL or cable modem that needs to be the DHCP server it won't be a problem--just plug it into the "external" port. LinuxMCE's DHCP server only operates on the "internal" one. However, if you have only 1 network card in the Core, you will need to be able to give it a static IP and disable the DHCP server in your DSL/Cable modem. Otherwise you will have to disable LinuxMCE's DHCP server and lose a lot of functionality.

==Setting Up The Hardware==

There are many ways to install LinuxMCE, and lots of options for equipment. However, the key components in a LinuxMCE system are the Core (the PC acting as the master server), Media Directors (media PC's connected to your TV's), and Orbiters (remote controls-web pads, pda's, mobile phones, etc.).

===A Dealer Core===

If you buy from a Pro dealer, they will come to your home, analyze your situation, and make the decision with you. They will offer a complete, custom-installed solution.
If you buy from regular dealer, the first thing you will need to get is 1 Core. This is the brains behind the whole system, and it must run 24/7 since it will be providing all the services in your home, like the security system, media server, phones, etc. Also, all the media in the home (movies, music, etc.) will be stored on the Core. Most dealers sell Cores that are commercial servers with massive storage and full redundancy so they will run non-stop without incident. Since these Cores are often bulky, they are normally tucked away in a wiring closet or equipment rack. However, you can also hook the Core up to your TV and use it as your first media director--we call this a hybrid. Prices for Cores vary from under $1,000 for a basic Pentium PC, up to $7,000+ for a dual Xeon model with 4TB of storage. See our ***Core comparison*** guide for help deciding.
Then for each TV area where you want media you will need a media director. It's easy to add or remove media directors at any time. See our ***media director comparison guide***.
For Orbiters you can either buy touch-screen tablets from a LinuxMCE dealer ***comparison guide***. Be sure to get a Bluetooth-enabled Symbian http://www.series60.com phone from your local mobile phone carrier--they make great remote controls.

Also view our http://www.linuxmce.org/wiki/index.php/LinuxMCE:Compability to see what 3rd party devices will work with LinuxMCE, like lighting control systems, cameras, alarm panels, etc.

=== I will use my own PC's ===

First a warning LinuxMCE is Linux-based, but don't worry. Sometimes drivers are not available for Linux as soon as they are for Windows. Particularly, if you bought some new, exotic hardware there may not be drivers. If you're looking to get some new hardware to run LinuxMCE you may want to check sites like http://www.linuxcompatible.org to be sure it's supported under Linux before you buy. Or maybe post a "will this work?" message in our forum. If you already have the hardware it can't hurt to try.

You will need one PC to run the Core software. Although you could install the Core on top of your existing Windows/Linux o/s, or build from source, it will be tricky and you will miss out on a lot of features. You really needs to use our own distribution because, in addition to our own software, LinuxMCE also includes lots of other open source projects, like Asterisk, Firefox, Xine, VideoLan, etc. We built "wrappers" for all of them which is how we get them all to work together seamlessly. For example, if you start watching a movie in 1 room, LinuxMCE will use Xine on that local media director. Use the orbiter to move that movie to 2 rooms, and LinuxMCE seamlessly detects the network capabilities (multi-cast switch, etc.), moves the video source to the Core using VideoLan, broadcasts to both rooms, uses VLC to do the rendering and changes the UI on the remote controls. If you use the vanilla packages from, say Fedora, none of that will work. Plus, a lot of LinuxMCE's more advanced, kernel-level modules, like plug-and-play, bandwidth shaping to ensure your phone calls are clear, network boot, and so on may not work on other Linux distributions and definitely cannot be done under Windows.

Note this PC should always be left on since it becomes the 'brains' for the whole house and all the other pieces won't function unless they can find the Core. In our commercial product, the Core is a fail-safe, redundant server.

There is only one special requirement. The Core needs to be your DHCP server so that it can offer the plug-and-play and network boot services. You cannot have 2 DHCP servers on the same network (not easily at least). If you have another DHCP server (like a cable/dsl modem), we recommend your Core have dual network cards: one for the "external" network, where your internet is connected, and one for the "internal" network within the house, and into which all your devices are connected. This makes LinuxMCE act as a firewall, and allows it to co-exist with another DHCP server. If you have a DSL or cable modem that needs to be the DHCP server it won't be a problem--just plug it into the "external" port. LinuxMCE's DHCP server only operates on the "internal" one. However, if you have only 1 network card in the Core, you will need to be able to give it a static IP and disable the DHCP server in your DSL/Cable modem. Otherwise you will have to disable LinuxMCE's DHCP server and lose a lot of functionality.

You can also put other cards in the Core, such as analog phone line interfaces from www.digium.com for the phone system or analog video capture cards for surveillance cameras. You can put the PVR/satellite capture cards in the individual media PC's, or you can put several in the Core, which will share the video throughout the house.

Wherever you have a TV/Stereo you can use a PC or thin-client as the Media Director--it doesn't need to be on all the time and there's no software to install since they will network boot off the Core. Just be sure it has a good Linux-compatible sound card, a Linux-compatible video card, supports PXE network boot (nearly all recent motherboards do), and--optionally--a PVR card. To use the Bluetooth mobile phones as remote controls, add a USB Bluetooth Dongle for each media director (around $25). All the media directors will report the signal strengths of all the mobile phones--this is how the Core figures out what room you're in. Since all resources in the whole house are shared, you will be able to control any device in any room from anywhere--as long as you're within Bluetooth range of any media director (about 10m or 30feet), you will have control over everything in the house. You can also use low-cost network audio players, like the Squeeze Box, wherever you want to add music.

To control the system, you can use the PC's mouse and keyboard, or an infrared remote, or run the Orbiter software on your mobile phones, webpads and PDA's.

Also view our http://www.linuxmce.org/wiki/index.php/LinuxMCE:Compability to see what 3rd party devices will work with LinuxMCE, like lighting control systems, cameras, alarm panels, etc.

===A Dedicated Core===

The Core is the central point of the Linux MCE system and runs applications and daemons needed for the other devices to exchange messages. A dedicated core will run only the backed applications and will not provide any fronted except the web interface, this means you won't act as a media center. You'll need to use Media Directors to be able to play movies, listen to music and watch TV. This kind of setup is recommended when you have lot of extra devices, this way the back end applications will have full access to Core's resources. 

[[Image:Diagram1.jpg|200px]]

===A Dedicated Hybrid===

A "hybrid" just means the computer that is running is the "Core" software is also running the "Media Director" software-you use the Core as a Media Director. The only reason we don't recommend this in our high-end installations is because a computer suitable for a Core is usually a pretty massive box with major hard drive capacity and rather noisy, so it's shoved away in the wiring closet, rather than sitting next to a TV like a Media Director would. However, you can use a regular PC as the Core + Media Director (Hybrid) also. Just remember that it will need to always be on since the Core software is what controls everything in the house.

[[Image:Diagram2.jpg|200px]]

Be sure you complete the installation of your Core/Hybrid before trying to boot the media directors.

==Installation==

===Pre-installation Setup===

'''Note:''' During the installation, you may have some difficulties that can be avoided by following the advice below:

# Make sure you have an Internet connection prior to starting! After LinuxMCE installs, it will need to access the Internet and download the latest patches. (More often than not, you want this!)
# Confused about which internet adapter should be your "main" when that option is given to you during the install? Just click on one. You have a 50/50 chance of getting it right. You can easily change it later in the LinuxMCE-admin pages by selecting "Advanced -> Network -> Network Settings" from the drop-down and clicking "Swap Interfaces".
# Use the core's DHCP server to give machines on your network a dynamic IP address. Turn off the DHCP server on any other devices you may have on your network! This is very important! You probably already have your home router giving out addresses. Check the configuration and turn that feature off. LinuxMCE uses the DHCP requests from machines that come online to figure out what they are and what to do with them.
# A map of your home. This is actually a very important step because LinuxMCE seems to need the map to properly finish the installation of some devices. It is easy to create a map using any drawing software or just draw one by hand and scan it. You don't need anything fancy, just some squares representing your different rooms. If the file is too big, LinuxMCE will scale it to fit. You can always upload a new map later on when you feel like being more creative. You can also make multiple maps, say, one for each floor or section of your house. This will all make more sense later when you get into configuring the devices.

===Download===
Download the Ubuntu installer and optional packages ISO from [http://linuxmce.org/wiki/index.php/Download_Instructions here].

===Software Installation===

You can find Steps for installing Linux MCE on a Kubuntu 7.04 system [http://wiki.linuxmce.org/index.php/Installation_Guide here].

===Finalize The Install===

After you have set everything up, you should do a full reboot of the "LinuxMCE universe", meaning rebooting the Core/Hybrid plus any media directors.
You can do this by choosing "Restart" from the LinuxMCE Admin site wizard (the last option), or from any orbiter or media director by clicking the LinuxMCE logo on the main menu and choosing "Reboot Core".
If your media directors support both software power off and wake on lan, the core will turn them off before it reboots itself, and will turn them back on when it has finished booting up. If not, you may need to reboot the media directors manually by cycling power on them. Note that you should not turn the media directors on until the Core/Hybrid has finished booting up.

==Configuration==

===Tell LinuxMCE About Your Home===

[[Tell LinuxMCE about your home]] shows you how to use our LinuxMCE Admin wizard. In about 2 hours you can have everything setup--the whole-house media server, full control all your lights, climate, and tv/hi-fi gear, the phone system, follow-me, everything. It's quick, painless, and non-technical.

===Adding Other Devices===

If you chose a "Core", not being used as a Media Director, then it will boot up and you will see a simple menu like this: 
[[Image:Console.jpg|200px]]
LinuxMCE Core; After boot-up menu 
You don't need to do anything. Your Core is up and running. Just make note of the IP address - you will need it to configure the system. 
If you chose a "Hybrid", that is you are using your Core as a Media Director, it will boot up to the same welcome menu as any media director. Note that the welcome menu will appear on the first boot. After that, it will boot to the normal main menu, however, you can click the LinuxMCE logo in the lower left corner of the main menu to see the advanced options, including all the buttons on the welcome menu. 
[[Image:Welcome.jpg|200px]]

You need a web browser to configure your LinuxMCE system using the built-in [[LinuxMCE Admin Website]]
Since the Hybrid + Media Directors have one built in, you can just click the "LinuxMCE Admin" website to bring it up directly on the Hybrid. Or, from any web browser in your home, go to the URL: http://myip/linuxmce_admin where myip is the IP address of the
Core/Hybrid.
Login then click [[Wizard Pages|Wizard]]. You will see the following screen.
[[Image:Wizard.jpg|200px]]

Follow each of the links in the left panel to choose your basic settings, add the devices, scenarios, and event handlers.
Here's an example for setting up an ultra low-cost smart home setup based on X10. The equipment we mention will cost under $1,000, although the procedure is exactly the same with a $100,000 high-end based on Lutron, Vantage, EIB, etc. So, please read the example regardless of your system type, so you understand the techniques.
EXAMPLE: Adding other devicesExample:
You have 2 gc100's which give you Infrared control of you're a/v equipment, extra serial ports to plug other stuff into, ttl inputs and relays. You have some tv's and stereo's to control, and also a CM11A module to control X10 devices, plus some X10 lights and thermostats.
You will plug the CM11A into one of the rs232 serial ports on the gc100. You also have an alarm panel with a serial interface, some squeeze box audio players, and some network cameras.

After specifying [[Basic Info]] on the first couple wizard pages, like family members and rooms, you get to [[Interfaces]].
Here you add all the devices that are used to interface with, or control other devices. So, the gc100 is an interface device, but the tv's and stereo's it controls are on the a/v page. The CM11A, Vantage, Lutron, etc. are also interfaces, the lights, blinds, drapes, etc. they control are on the [[Lights|lighting page]]. The alarm panel is an interface, the motion, glass break, smoke alarms, etc., are on the [[Security]].
Some home automation devices do not require an interface, some do. An IP-based camera does not require an interface device-add it directly to [[Surveillance Cameras]].
Analog cameras do need some sort of interface device, like a camera capture board, which you must first add to the interfaces page. Add the interface devices first on the interface page, and then the devices they control on the respective page. If you want to add EIB lights (on the lights page), you won't be allowed to do that until you first add the EIB interface on the interfaces page, because an EIB light cannot be used with an interface. If you add interfaces for both an EIB Lighting system, and an X10 lighting system, then on the lighting page you will be able to add both types of lights, and the 'Controlled Via' field will show you what interface is being used.
Back to our example: Plug one of your gc100's into the network, and click the 'add gc100' button on the interface page. gc100's are treated special because they are IP-based, but their network configuration is a bit different and does not allow them to be plug-and-play. Once you got the message that it was found and configured, click on the Interfaces page again--now you'll see it there. Maybe give it a descriptive name so you can remember which is which. Now plug in the 2nd gc100, and repeat.
Next choose 'Add Devices' and add the CM11A. Like all RS232 devices, it is not plug and play, you must add it manually. Repeat for the alarm panel. In both cases, the Controlled Via devices is the Core, since that's where the software drivers will be run. But, when you go to choose the port, it only shows the Core's internal serial ports, and you want to plug it into one of the ports on the gc100. So, click 'Wizard', 'Restart' and 'quick reload router'. That causes the DCE Router to reload the list of devices in the house so it sees the new gc100's you added, and adds the ports. Refresh the Interfaces page, and now you can choose the gc100 ports for the CM11A and alarm panel.Next, add your tv's and stereo's on the [[AV Devices]] and indicate how they are connected (which AV inputs). If your model is not in the database you will need to add it. If the I/R codes for your device aren't listed or don't work, you will click the A/V properties button and either [[Learning/typing my own code|learn them]] using the gc100's learner (plug it into serial port 1 and click 'learn'), or [[Learning/typing my own code|copy+paste the I/R codes in pronto format]] from a source like www.remotecentral.com. Your devices and I/R codes will automatically be sent to LinuxMCE and added to the master database for other users unless you uncheck the box. In the 'controlled via' chose whichever one of the gc100's has the infrared emitter attached for that device. Turn your Squeeze Boxes on, set the network to DHCP, and plug them in. LinuxMCE will automatically recognize them and configure them. You will see a confirmation message and be asked to pick the room they're in. Refresh the A/V page to see the Squeeze Boxes and indicate how you connect them to your stereo system.

On the [[Media Directors]] and [[Orbiters]] page, be sure your settings are correct. Then on the [[Lights]] and [[Climate]] pages, add all your X10 lights/thermostats. The 'Controlled Via' is the cm11A device. On the security page, add all your motion detectors, smoke alarms, etc. The 'Controlled Via' is the alarm panel.
On the [[Floorplans]], drag and drop your devices on the maps you upload. You'll need to do a 'regen orbiter' followed by a 'quick reload router' before you can use the floorplans.

Now let's test the devices. Do another 'quick reload router' so DCERouter sees these new devices. Go back to a device, like a light, click 'ADV' to go to the advanced page, or go there manually by choosing [[Devices]] from the menu. Click 'Send command to device', and choose a command. If it doesn't respond, go to 'Advanced', 'Logs' and check the logs for the interface, the CM11A in this case.

===Scenarios, Events & Security===

In the [[Scenarios]] page, add the scenarios, or buttons, you want for each room. Like a Lighting scenario in the Bedroom called 'Go to sleep' which dims the lights, or a security scenario in the living to view a camera. When you do a 'quick reload router', DCERouter will automatically add Media Scenarios for each room for whatever media devices are in there. But your new scenarios are not visible on the Orbiter until you regenerate--see the note below in 'Using LinuxMCE with an Orbiter'. Next add [[Events]], in other words, when something happens (a motion detector is tripped, the sun sets, etc.) you want LinuxMCE to do this (turn on a light). Also set security options, like how you want to be notified when something happens in the house. Each page has context sensitive help to explain everything. They will take effect next time you reboot or 'quick reload router'.

===Configuring Myth TV===

This section has been moved to [[Setting up MythTV]].

===Upload Your Media===

There will also be Microsoft Windows compatible network shares on the Core or Hybrid (uses Samba) . There is a "public" share for putting all files that the whole family can share--movies, music, etc. And there is a private share for each family member. To access these network shares in Windows, choose Start, Run, and type \\ plus the IP address of the Core or hybrid.

For example: \\192.168.80.1 Note that if you add new family members, their network share will not be available until after you reboot the Core/Hybrid. Once you copy your media into the appropriate folder, you can go into the LinuxMCE Admin site, choose "Files & Media" and "Media Files Sync" to be sure your media is in the database, add attributes (artist, actor, etc.), and choose cover art.

==Using LinuxMCE==

This section has been moved to [[Using LinuxMCE]]. In 10 minutes you'll be up to speed and using all of LinuxMCE's features.

Using LinuxMCE with an Orbiter
Orbiter is just our way of saying remote control. All the Media Directors run an on-screen Orbiter, like the one below. Choose options on the on-screen orbiter with a keyboard/mouse attached to the media director, or with an infrared remote control. The Orbiter software runs on Linux, Windows and Windows CE, and can also be run on webpads and PDA's.
Either way, it works exactly the same.Below is the main menu. In the lower right are the [[Who Am I, Where Am I|'who' and 'where']] buttons. This indicates what room you are in, or want to control, and which family member is using the Orbiter.

Touch either button if this isn't correct. Even if you are using an on-screen orbiter on the media director in the Living Room, for example, you can still change the location to the Bedroom. That means you would be using the Media Director in the Living Room as a remote control for the devices in the bedroom. Normally you don't change the location for an on-screen orbiter, since that device stays in a fixed place, but you do when you have a wireless web pad or pda you carry around.

The icons on the left all lead to a [[maps]], or floorplan, of your house showing your lighting, media, climate, telecom and security devices. Next to each of the floorplan icons are the scenarios for that category and the given room. In the scenarios section of the LinuxMCE Admin web site you create the scenarios for each room. You can have a lighting scenario called 'entertaining guests' that sets some lights, plays some background music, unlocks the door, and so on.
 
[[Image:Main-menu.jpg|200px]]

[[Image:Litscen.jpg|200px]] 

NOTE:
Many orbiters have relatively slow processors (like PDA's and phones) and may be running on slow wi-fi connections. So, the orbiters do not retrieve the large, full-size graphics, scaling them, drawing the text, and rendering everything on the fly.

Rather all the graphics on your Orbiter are pre-scaled and pre-rendered by OrbiterGen. This means that if you add new scenarios or devices, or change floorplans or skins, you won't see them immediately on the Orbiter. You must go to the 'Advanced
Options' page by clicking the LinuxMCE logo on the main menu, and choose 'Regenerate this Orbiter'. You'll be asked to wait about 60 seconds or so while the renderer creates new graphics, and then the Orbiter will reload.

Using your system with a Mobile Orbiter
Unless you turned off the "Auto Detect new Bluetooth Phones" option for the Media Director, compatible Bluetooth Mobile phones will automatically be detected when they are within range of any Media Director if they have Bluetooth turned on. A message will appear on all the Orbiters asking if it's a phone, and if so, to whom it belongs. Be sure you add your family members to the LinuxMCE Admin web site before doing this. Also, you may need to turn on the TV to see the message on the on-screen orbiter.

If you choose to install the software, the phone will beep. Just hit 'yes' to accept the software, and accept the default prompts.The mobile orbiter works pretty much like a regular orbiter. The difference is that you don't usually need to worry about the "who" and "where" button. The "who" is determined when you chose to install the software. That family member is assumed to always be the user. And the "where" is automatic-whenever you come within range of a media director it will automatically switch to the correct location. You can press the button under the location if you want to control a location other than the one you are in.

Since the display is smaller, rather than showing all the scenarios on the main menu, you must first choose the category, like lighting, and then choose the scenario from the sub menu that appears. You can also hold the category to toggle 'follow-me' mode, indicated with a red F. So, if you hold down the 2 button, a red F appears for media. Now as you move around the house your media will follow you. All 5 categories have follow-me. <a
href="http://linuxmce.org/index.php?section=how_LinuxMCE_works">Screen shots of the Mobile Orbiter</a> / [[User's manual]]

==Troubleshooting==

[[Testing_and_troubleshooting_devices]]

[[Development status for all modules|What works and what doesn't?]]

If you don't know Linux at all, you can go into the LinuxMCE Admin website and choose [[Outside Access]], and check the box to get outside assistance from LinuxMCE. You will pick a password you will give one of our tech support staff. When you do, your system will make a secure, encrypted connection back to our support staff giving us temporary access to your system. The connection is closed as soon as you uncheck the box. Without checking that box, nobody at LinuxMCE will have any access to your system.

This troubleshooting guide assumes some basic knowledge of Linux. In LinuxMCE, everything is a device. In the LinuxMCE Admin web site, you can choose [[Devices]], to see a list of all the devices in your installation. We recommend you don't make changes here - you can break things! The top level device is usually a computer, either the core or a hybrid or an orbiter. All the logs for the devices on that computer are stored in /var/log/pluto. You can ssh in to the core using the root password you chose, and from there, you can ssh to all the media directors-shared keys were automatically setup.
All current activity is logged in the file that ends in ".newlog". After a device crashes, its logs are moved into
the ".log" directory. At bootup, all logs are archived into /var/log/pluto/archives.

All DCE devices are running in separate screen sessions. Type "screen -ls" to see all active screen sessions,
and "screen -r PID" where PID is the id you saw in the -ls list to attach to the screen session. There is not much for you to do or see though since all the output on stderr and stdout is going into the logs. DCERouter is running the same way on your core or hybrid.

At bootup, all the scripts listed in the LinuxMCE Admin website under [[Boot Sequence]] are run. If any programs crash, a core dump file is put in /usr/pluto/coredump. At each reboot, any core dumps are archived with the log files in /var/log/pluto/archives. A database dump/configuration snapshot are also put in each archive. Archives are deleted after 5 days.

If you're a programmer, you can also check out our [[Programmer's Guide]]. If you want to learn about writing DCE Devices, see the [[DCE]].


''Note:''
We had to leave some basic features out of the free version due to licensing issues. See [http://www.geocities.com/medencid/index.html here] for a list. If you purchase a pre-built LinuxMCE system, some or all of these technologies may be licensed and the license fee built into the purchase price. Before contacting LinuxMCE support to ask why something doesn't work, please refer to that site so you know what features were left out intentionally. Note that LinuxMCE does not encourage, endorse or support users adding 3rd party modules, nor did LinuxMCE develop those modules. If you choose to add 3rd party modules we suggest you first confirm they are legal in your area.

Getting Started

2007-08-23T22:58:33Z

Macca: added links to tested hardware pages

==Equipment: Picking The Right Components==

''See also: [[Tested good hardware]] and [[Tested bad hardware]]''

===The Core===

Most important, is the "core". This is the main LinuxMCE server that runs all the applications. The commercial version uses a high-end server with RAID-5 storage. You'll probably be able to get by with a good Pentium 4, at least 80 GB of storage and two network cards (Gigabit ideally).

It would be best to use a dedicated core, which means you'll end up putting this computer somewhere out of the way and not connecting a monitor to it. If you are using only one computer for your system, then you've chosen the "hybrid" system, which means that your core will also be your media player. You'll definitely need a monitor or TV for this system!

===Media Directors===

Note that each media director will need a Bluetooth dongle if you want to use a Bluetooth mobile phone as the remote in that area. To control your a/v equipment using infrared, you will need an interface module (global cache gc100). This interface module also gives you extra serial ports. So, in this example, the TV is controlled by infrared, and the receiver by RS232.

''See also: [[Sound Cards]] and [[Network_Boot_for_Media_Directors]]''

===Orbiters===

===Network Attached Storage===

An alternative to having a lot of storage space in the core is to have a small hard drive for the core and store all your files on a [[Network Attached Storage|network attached storage]] (or NAS) server. The [http://www.buffalotech.com/products/network-storage/terastation/ Buffalo TeraStation] is 1.0 TeraByte RAID-5 and under $1K(US). Having a NAS will allow you to not lose your precious media files. You'll likely want the larger storage for your collection of music and videos. Keep in mind that your LinuxMCE system can also record TV shows (using MythTV) and video from your security cameras (using Motion).

===Additional Devices===

''See also [[Recommended Accessories]]''

Optionally, you may want the aforementioned home automation devices for controlling your lights. Also, optionally, you may want security cameras, plasma screen TV, a streaming media music player such as the [http://www.slimdevices.com Squeezebox], an alarm system with a serial interface, etc. Some of these devices need ''another'' device called a [http://www.globalcache.com/products/gc-index.html gc100]. This allows devices that communicate using a serial port (good alarm panels) or infrared (like your TV) to connect to the network and talk with your LinuxMCE core.

===Location Considerations===

This section has been moved to [[Choosing Locations]].

===Wiring Considerations===

''Main article: [[Wiring Considerations]]''

Once LinuxMCE is installed, just treat it like an appliance--plug it in, turn it on, and leave it alone. The great news is that don't need to install any software on the media PCs that will be used as media directors. You can leave whatever operating system is on there, such as Windows, untouched-they will do a [[Network Boot for Media Directors]] when you want to use them as a Media Director.

The only special requirement is that the LinuxMCE Core needs to be your DHCP server so that it can offer the plug-and-play and network boot services. You cannot have 2 DHCP servers on the same network (not easily at least). In our Core, we provide [[Why dual network cards?|dual network cards]] one for the "external" network, where your internet is connected, and one for the "internal" network within the house, and into which all your devices are connected. This makes LinuxMCE act as a firewall, and allows it to co-exist with another DHCP server. If you have a DSL or cable modem that needs to be the DHCP server it won't be a problem--just plug it into the "external" port. LinuxMCE's DHCP server only operates on the "internal" one. However, if you have only 1 network card in the Core, you will need to be able to give it a static IP and disable the DHCP server in your DSL/Cable modem. Otherwise you will have to disable LinuxMCE's DHCP server and lose a lot of functionality.

==Setting Up The Hardware==

There are many ways to install LinuxMCE, and lots of options for equipment. However, the key components in a LinuxMCE system are the Core (the PC acting as the master server), Media Directors (media PC's connected to your TV's), and Orbiters (remote controls-web pads, pda's, mobile phones, etc.).

===A Dealer Core===

If you buy from a Pro dealer, they will come to your home, analyze your situation, and make the decision with you. They will offer a complete, custom-installed solution.
If you buy from regular dealer, the first thing you will need to get is 1 Core. This is the brains behind the whole system, and it must run 24/7 since it will be providing all the services in your home, like the security system, media server, phones, etc. Also, all the media in the home (movies, music, etc.) will be stored on the Core. Most dealers sell Cores that are commercial servers with massive storage and full redundancy so they will run non-stop without incident. Since these Cores are often bulky, they are normally tucked away in a wiring closet or equipment rack. However, you can also hook the Core up to your TV and use it as your first media director--we call this a hybrid. Prices for Cores vary from under $1,000 for a basic Pentium PC, up to $7,000+ for a dual Xeon model with 4TB of storage. See our ***Core comparison*** guide for help deciding.
Then for each TV area where you want media you will need a media director. It's easy to add or remove media directors at any time. See our ***media director comparison guide***.
For Orbiters you can either buy touch-screen tablets from a LinuxMCE dealer ***comparison guide***. Be sure to get a Bluetooth-enabled Symbian http://www.series60.com phone from your local mobile phone carrier--they make great remote controls.

Also view our http://www.linuxmce.org/wiki/index.php/LinuxMCE:Compability to see what 3rd party devices will work with LinuxMCE, like lighting control systems, cameras, alarm panels, etc.

=== I will use my own PC's ===

First a warning LinuxMCE is Linux-based, but don't worry. Sometimes drivers are not available for Linux as soon as they are for Windows. Particularly, if you bought some new, exotic hardware there may not be drivers. If you're looking to get some new hardware to run LinuxMCE you may want to check sites like http://www.linuxcompatible.org to be sure it's supported under Linux before you buy. Or maybe post a "will this work?" message in our forum. If you already have the hardware it can't hurt to try.

You will need one PC to run the Core software. Although you could install the Core on top of your existing Windows/Linux o/s, or build from source, it will be tricky and you will miss out on a lot of features. You really needs to use our own distribution because, in addition to our own software, LinuxMCE also includes lots of other open source projects, like Asterisk, Firefox, Xine, VideoLan, etc. We built "wrappers" for all of them which is how we get them all to work together seamlessly. For example, if you start watching a movie in 1 room, LinuxMCE will use Xine on that local media director. Use the orbiter to move that movie to 2 rooms, and LinuxMCE seamlessly detects the network capabilities (multi-cast switch, etc.), moves the video source to the Core using VideoLan, broadcasts to both rooms, uses VLC to do the rendering and changes the UI on the remote controls. If you use the vanilla packages from, say Fedora, none of that will work. Plus, a lot of LinuxMCE's more advanced, kernel-level modules, like plug-and-play, bandwidth shaping to ensure your phone calls are clear, network boot, and so on may not work on other Linux distributions and definitely cannot be done under Windows.

Note this PC should always be left on since it becomes the 'brains' for the whole house and all the other pieces won't function unless they can find the Core. In our commercial product, the Core is a fail-safe, redundant server.

There is only one special requirement. The Core needs to be your DHCP server so that it can offer the plug-and-play and network boot services. You cannot have 2 DHCP servers on the same network (not easily at least). If you have another DHCP server (like a cable/dsl modem), we recommend your Core have dual network cards: one for the "external" network, where your internet is connected, and one for the "internal" network within the house, and into which all your devices are connected. This makes LinuxMCE act as a firewall, and allows it to co-exist with another DHCP server. If you have a DSL or cable modem that needs to be the DHCP server it won't be a problem--just plug it into the "external" port. LinuxMCE's DHCP server only operates on the "internal" one. However, if you have only 1 network card in the Core, you will need to be able to give it a static IP and disable the DHCP server in your DSL/Cable modem. Otherwise you will have to disable LinuxMCE's DHCP server and lose a lot of functionality.

You can also put other cards in the Core, such as analog phone line interfaces from www.digium.com for the phone system or analog video capture cards for surveillance cameras. You can put the PVR/satellite capture cards in the individual media PC's, or you can put several in the Core, which will share the video throughout the house.

Wherever you have a TV/Stereo you can use a PC or thin-client as the Media Director--it doesn't need to be on all the time and there's no software to install since they will network boot off the Core. Just be sure it has a good Linux-compatible sound card, a Linux-compatible video card, supports PXE network boot (nearly all recent motherboards do), and--optionally--a PVR card. To use the Bluetooth mobile phones as remote controls, add a USB Bluetooth Dongle for each media director (around $25). All the media directors will report the signal strengths of all the mobile phones--this is how the Core figures out what room you're in. Since all resources in the whole house are shared, you will be able to control any device in any room from anywhere--as long as you're within Bluetooth range of any media director (about 10m or 30feet), you will have control over everything in the house. You can also use low-cost network audio players, like the Squeeze Box, wherever you want to add music.

To control the system, you can use the PC's mouse and keyboard, or an infrared remote, or run the Orbiter software on your mobile phones, webpads and PDA's.

Also view our http://www.linuxmce.org/wiki/index.php/LinuxMCE:Compability to see what 3rd party devices will work with LinuxMCE, like lighting control systems, cameras, alarm panels, etc.

===A Dedicated Core===

The Core is the central point of the Linux MCE system and runs applications and daemons needed for the other devices to exchange messages. A dedicated core will run only the backed applications and will not provide any fronted except the web interface, this means you won't act as a media center. You'll need to use Media Directors to be able to play movies, listen to music and watch TV. This kind of setup is recommended when you have lot of extra devices, this way the back end applications will have full access to Core's resources. 

[[Image:Diagram1.jpg|200px]]

===A Dedicated Hybrid===

A "hybrid" just means the computer that is running is the "Core" software is also running the "Media Director" software-you use the Core as a Media Director. The only reason we don't recommend this in our high-end installations is because a computer suitable for a Core is usually a pretty massive box with major hard drive capacity and rather noisy, so it's shoved away in the wiring closet, rather than sitting next to a TV like a Media Director would. However, you can use a regular PC as the Core + Media Director (Hybrid) also. Just remember that it will need to always be on since the Core software is what controls everything in the house.

[[Image:Diagram2.jpg|200px]]

Be sure you complete the installation of your Core/Hybrid before trying to boot the media directors.

==Installation==

===Pre-installation Setup===

'''Note:''' During the installation, you may have some difficulties that can be avoided by following the advice below:

# Make sure you have an Internet connection prior to starting! After LinuxMCE installs, it will need to access the Internet and download the latest patches. (More often than not, you want this!)
# Confused about which internet adapter should be your "main" when that option is given to you during the install? Just click on one. You have a 50/50 chance of getting it right. You can easily change it later in the LinuxMCE-admin pages by selecting "Advanced -> Network -> Network Settings" from the drop-down and clicking "Swap Interfaces".
# Use the core's DHCP server to give machines on your network a dynamic IP address. Turn off the DHCP server on any other devices you may have on your network! This is very important! You probably already have your home router giving out addresses. Check the configuration and turn that feature off. LinuxMCE uses the DHCP requests from machines that come online to figure out what they are and what to do with them.
# A map of your home. This is actually a very important step because LinuxMCE seems to need the map to properly finish the installation of some devices. It is easy to create a map using any drawing software or just draw one by hand and scan it. You don't need anything fancy, just some squares representing your different rooms. If the file is too big, LinuxMCE will scale it to fit. You can always upload a new map later on when you feel like being more creative. You can also make multiple maps, say, one for each floor or section of your house. This will all make more sense later when you get into configuring the devices.

===Download===
Download the Ubuntu installer and optional packages ISO from [http://linuxmce.org/wiki/index.php/Download_Instructions here].

===Software Installation===

You can find Steps for installing Linux MCE on an Ubuntu 6.10 system [http://wiki.linuxmce.org/index.php/Installation_Guide here].

===Finalize The Install===

After you have set everything up, you should do a full reboot of the "LinuxMCE universe", meaning rebooting the Core/Hybrid plus any media directors.
You can do this by choosing "Restart" from the LinuxMCE Admin site wizard (the last option), or from any orbiter or media director by clicking the LinuxMCE logo on the main menu and choosing "Reboot Core".
If your media directors support both software power off and wake on lan, the core will turn them off before it reboots itself, and will turn them back on when it has finished booting up. If not, you may need to reboot the media directors manually by cycling power on them. Note that you should not turn the media directors on until the Core/Hybrid has finished booting up.

==Configuration==

===Tell LinuxMCE About Your Home===

[[Tell LinuxMCE about your home]] shows you how to use our LinuxMCE Admin wizard. In about 2 hours you can have everything setup--the whole-house media server, full control all your lights, climate, and tv/hi-fi gear, the phone system, follow-me, everything. It's quick, painless, and non-technical.

===Adding Other Devices===

If you chose a "Core", not being used as a Media Director, then it will boot up and you will see a simple menu like this: 
[[Image:Console.jpg|200px]]
LinuxMCE Core; After boot-up menu 
You don't need to do anything. Your Core is up and running. Just make note of the IP address - you will need it to configure the system. 
If you chose a "Hybrid", that is you are using your Core as a Media Director, it will boot up to the same welcome menu as any media director. Note that the welcome menu will appear on the first boot. After that, it will boot to the normal main menu, however, you can click the LinuxMCE logo in the lower left corner of the main menu to see the advanced options, including all the buttons on the welcome menu. 
[[Image:Welcome.jpg|200px]]

You need a web browser to configure your LinuxMCE system using the built-in [[LinuxMCE Admin Website]]
Since the Hybrid + Media Directors have one built in, you can just click the "LinuxMCE Admin" website to bring it up directly on the Hybrid. Or, from any web browser in your home, go to the URL: http://myip/linuxmce_admin where myip is the IP address of the
Core/Hybrid.
Login then click [[Wizard Pages|Wizard]]. You will see the following screen.
[[Image:Wizard.jpg|200px]]

Follow each of the links in the left panel to choose your basic settings, add the devices, scenarios, and event handlers.
Here's an example for setting up an ultra low-cost smart home setup based on X10. The equipment we mention will cost under $1,000, although the procedure is exactly the same with a $100,000 high-end based on Lutron, Vantage, EIB, etc. So, please read the example regardless of your system type, so you understand the techniques.
EXAMPLE: Adding other devicesExample:
You have 2 gc100's which give you Infrared control of you're a/v equipment, extra serial ports to plug other stuff into, ttl inputs and relays. You have some tv's and stereo's to control, and also a CM11A module to control X10 devices, plus some X10 lights and thermostats.
You will plug the CM11A into one of the rs232 serial ports on the gc100. You also have an alarm panel with a serial interface, some squeeze box audio players, and some network cameras.

After specifying [[Basic Info]] on the first couple wizard pages, like family members and rooms, you get to [[Interfaces]].
Here you add all the devices that are used to interface with, or control other devices. So, the gc100 is an interface device, but the tv's and stereo's it controls are on the a/v page. The CM11A, Vantage, Lutron, etc. are also interfaces, the lights, blinds, drapes, etc. they control are on the [[Lights|lighting page]]. The alarm panel is an interface, the motion, glass break, smoke alarms, etc., are on the [[Security]].
Some home automation devices do not require an interface, some do. An IP-based camera does not require an interface device-add it directly to [[Surveillance Cameras]].
Analog cameras do need some sort of interface device, like a camera capture board, which you must first add to the interfaces page. Add the interface devices first on the interface page, and then the devices they control on the respective page. If you want to add EIB lights (on the lights page), you won't be allowed to do that until you first add the EIB interface on the interfaces page, because an EIB light cannot be used with an interface. If you add interfaces for both an EIB Lighting system, and an X10 lighting system, then on the lighting page you will be able to add both types of lights, and the 'Controlled Via' field will show you what interface is being used.
Back to our example: Plug one of your gc100's into the network, and click the 'add gc100' button on the interface page. gc100's are treated special because they are IP-based, but their network configuration is a bit different and does not allow them to be plug-and-play. Once you got the message that it was found and configured, click on the Interfaces page again--now you'll see it there. Maybe give it a descriptive name so you can remember which is which. Now plug in the 2nd gc100, and repeat.
Next choose 'Add Devices' and add the CM11A. Like all RS232 devices, it is not plug and play, you must add it manually. Repeat for the alarm panel. In both cases, the Controlled Via devices is the Core, since that's where the software drivers will be run. But, when you go to choose the port, it only shows the Core's internal serial ports, and you want to plug it into one of the ports on the gc100. So, click 'Wizard', 'Restart' and 'quick reload router'. That causes the DCE Router to reload the list of devices in the house so it sees the new gc100's you added, and adds the ports. Refresh the Interfaces page, and now you can choose the gc100 ports for the CM11A and alarm panel.Next, add your tv's and stereo's on the [[AV Devices]] and indicate how they are connected (which AV inputs). If your model is not in the database you will need to add it. If the I/R codes for your device aren't listed or don't work, you will click the A/V properties button and either [[Learning/typing my own code|learn them]] using the gc100's learner (plug it into serial port 1 and click 'learn'), or [[Learning/typing my own code|copy+paste the I/R codes in pronto format]] from a source like www.remotecentral.com. Your devices and I/R codes will automatically be sent to LinuxMCE and added to the master database for other users unless you uncheck the box. In the 'controlled via' chose whichever one of the gc100's has the infrared emitter attached for that device. Turn your Squeeze Boxes on, set the network to DHCP, and plug them in. LinuxMCE will automatically recognize them and configure them. You will see a confirmation message and be asked to pick the room they're in. Refresh the A/V page to see the Squeeze Boxes and indicate how you connect them to your stereo system.

On the [[Media Directors]] and [[Orbiters]] page, be sure your settings are correct. Then on the [[Lights]] and [[Climate]] pages, add all your X10 lights/thermostats. The 'Controlled Via' is the cm11A device. On the security page, add all your motion detectors, smoke alarms, etc. The 'Controlled Via' is the alarm panel.
On the [[Floorplans]], drag and drop your devices on the maps you upload. You'll need to do a 'regen orbiter' followed by a 'quick reload router' before you can use the floorplans.

Now let's test the devices. Do another 'quick reload router' so DCERouter sees these new devices. Go back to a device, like a light, click 'ADV' to go to the advanced page, or go there manually by choosing [[Devices]] from the menu. Click 'Send command to device', and choose a command. If it doesn't respond, go to 'Advanced', 'Logs' and check the logs for the interface, the CM11A in this case.

===Scenarios, Events & Security===

In the [[Scenarios]] page, add the scenarios, or buttons, you want for each room. Like a Lighting scenario in the Bedroom called 'Go to sleep' which dims the lights, or a security scenario in the living to view a camera. When you do a 'quick reload router', DCERouter will automatically add Media Scenarios for each room for whatever media devices are in there. But your new scenarios are not visible on the Orbiter until you regenerate--see the note below in 'Using LinuxMCE with an Orbiter'. Next add [[Events]], in other words, when something happens (a motion detector is tripped, the sun sets, etc.) you want LinuxMCE to do this (turn on a light). Also set security options, like how you want to be notified when something happens in the house. Each page has context sensitive help to explain everything. They will take effect next time you reboot or 'quick reload router'.

===Configuring Myth TV===

This section has been moved to [[Setting up MythTV]].

===Upload Your Media===

There will also be Microsoft Windows compatible network shares on the Core or Hybrid (uses Samba) . There is a "public" share for putting all files that the whole family can share--movies, music, etc. And there is a private share for each family member. To access these network shares in Windows, choose Start, Run, and type \\ plus the IP address of the Core or hybrid.

For example: \\192.168.80.1 Note that if you add new family members, their network share will not be available until after you reboot the Core/Hybrid. Once you copy your media into the appropriate folder, you can go into the LinuxMCE Admin site, choose "Files & Media" and "Media Files Sync" to be sure your media is in the database, add attributes (artist, actor, etc.), and choose cover art.

==Using LinuxMCE==

This section has been moved to [[Using LinuxMCE]]. In 10 minutes you'll be up to speed and using all of LinuxMCE's features.

Using LinuxMCE with an Orbiter
Orbiter is just our way of saying remote control. All the Media Directors run an on-screen Orbiter, like the one below. Choose options on the on-screen orbiter with a keyboard/mouse attached to the media director, or with an infrared remote control. The Orbiter software runs on Linux, Windows and Windows CE, and can also be run on webpads and PDA's.
Either way, it works exactly the same.Below is the main menu. In the lower right are the [[Who Am I, Where Am I|'who' and 'where']] buttons. This indicates what room you are in, or want to control, and which family member is using the Orbiter.

Touch either button if this isn't correct. Even if you are using an on-screen orbiter on the media director in the Living Room, for example, you can still change the location to the Bedroom. That means you would be using the Media Director in the Living Room as a remote control for the devices in the bedroom. Normally you don't change the location for an on-screen orbiter, since that device stays in a fixed place, but you do when you have a wireless web pad or pda you carry around.

The icons on the left all lead to a [[maps]], or floorplan, of your house showing your lighting, media, climate, telecom and security devices. Next to each of the floorplan icons are the scenarios for that category and the given room. In the scenarios section of the LinuxMCE Admin web site you create the scenarios for each room. You can have a lighting scenario called 'entertaining guests' that sets some lights, plays some background music, unlocks the door, and so on.
 
[[Image:Main-menu.jpg|200px]]

[[Image:Litscen.jpg|200px]] 

NOTE:
Many orbiters have relatively slow processors (like PDA's and phones) and may be running on slow wi-fi connections. So, the orbiters do not retrieve the large, full-size graphics, scaling them, drawing the text, and rendering everything on the fly.

Rather all the graphics on your Orbiter are pre-scaled and pre-rendered by OrbiterGen. This means that if you add new scenarios or devices, or change floorplans or skins, you won't see them immediately on the Orbiter. You must go to the 'Advanced
Options' page by clicking the LinuxMCE logo on the main menu, and choose 'Regenerate this Orbiter'. You'll be asked to wait about 60 seconds or so while the renderer creates new graphics, and then the Orbiter will reload.

Using your system with a Mobile Orbiter
Unless you turned off the "Auto Detect new Bluetooth Phones" option for the Media Director, compatible Bluetooth Mobile phones will automatically be detected when they are within range of any Media Director if they have Bluetooth turned on. A message will appear on all the Orbiters asking if it's a phone, and if so, to whom it belongs. Be sure you add your family members to the LinuxMCE Admin web site before doing this. Also, you may need to turn on the TV to see the message on the on-screen orbiter.

If you choose to install the software, the phone will beep. Just hit 'yes' to accept the software, and accept the default prompts.The mobile orbiter works pretty much like a regular orbiter. The difference is that you don't usually need to worry about the "who" and "where" button. The "who" is determined when you chose to install the software. That family member is assumed to always be the user. And the "where" is automatic-whenever you come within range of a media director it will automatically switch to the correct location. You can press the button under the location if you want to control a location other than the one you are in.

Since the display is smaller, rather than showing all the scenarios on the main menu, you must first choose the category, like lighting, and then choose the scenario from the sub menu that appears. You can also hold the category to toggle 'follow-me' mode, indicated with a red F. So, if you hold down the 2 button, a red F appears for media. Now as you move around the house your media will follow you. All 5 categories have follow-me. <a
href="http://linuxmce.org/index.php?section=how_LinuxMCE_works">Screen shots of the Mobile Orbiter</a> / [[User's manual]]

==Troubleshooting==

[[Testing_and_troubleshooting_devices]]

[[Development status for all modules|What works and what doesn't?]]

If you don't know Linux at all, you can go into the LinuxMCE Admin website and choose [[Outside Access]], and check the box to get outside assistance from LinuxMCE. You will pick a password you will give one of our tech support staff. When you do, your system will make a secure, encrypted connection back to our support staff giving us temporary access to your system. The connection is closed as soon as you uncheck the box. Without checking that box, nobody at LinuxMCE will have any access to your system.

This troubleshooting guide assumes some basic knowledge of Linux. In LinuxMCE, everything is a device. In the LinuxMCE Admin web site, you can choose [[Devices]], to see a list of all the devices in your installation. We recommend you don't make changes here - you can break things! The top level device is usually a computer, either the core or a hybrid or an orbiter. All the logs for the devices on that computer are stored in /var/log/pluto. You can ssh in to the core using the root password you chose, and from there, you can ssh to all the media directors-shared keys were automatically setup.
All current activity is logged in the file that ends in ".newlog". After a device crashes, its logs are moved into
the ".log" directory. At bootup, all logs are archived into /var/log/pluto/archives.

All DCE devices are running in separate screen sessions. Type "screen -ls" to see all active screen sessions,
and "screen -r PID" where PID is the id you saw in the -ls list to attach to the screen session. There is not much for you to do or see though since all the output on stderr and stdout is going into the logs. DCERouter is running the same way on your core or hybrid.

At bootup, all the scripts listed in the LinuxMCE Admin website under [[Boot Sequence]] are run. If any programs crash, a core dump file is put in /usr/pluto/coredump. At each reboot, any core dumps are archived with the log files in /var/log/pluto/archives. A database dump/configuration snapshot are also put in each archive. Archives are deleted after 5 days.

If you're a programmer, you can also check out our [[Programmer's Guide]]. If you want to learn about writing DCE Devices, see the [[DCE]].


''Note:''
We had to leave some basic features out of the free version due to licensing issues. See [http://www.geocities.com/medencid/index.html here] for a list. If you purchase a pre-built LinuxMCE system, some or all of these technologies may be licensed and the license fee built into the purchase price. Before contacting LinuxMCE support to ask why something doesn't work, please refer to that site so you know what features were left out intentionally. Note that LinuxMCE does not encourage, endorse or support users adding 3rd party modules, nor did LinuxMCE develop those modules. If you choose to add 3rd party modules we suggest you first confirm they are legal in your area.