<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://wiki.linuxmce.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Coley</id>
	<title>LinuxMCE - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="http://wiki.linuxmce.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Coley"/>
	<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php/Special:Contributions/Coley"/>
	<updated>2026-05-11T05:41:48Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.44.0</generator>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Coley&amp;diff=36915</id>
		<title>User:Coley</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Coley&amp;diff=36915"/>
		<updated>2017-01-10T11:56:45Z</updated>

		<summary type="html">&lt;p&gt;Coley: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:User Setups]]&lt;br /&gt;
&lt;br /&gt;
I may as well put some details on my set-up here. At the moment it is at the experimental stage, time invested now will be just that, beginning to get time to play with this in freshly renovated house.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Dedicated Core&#039;&#039;&#039;&lt;br /&gt;
  Recently installed 14.04.&lt;br /&gt;
  Now on a [[HP ML115 G5]] micro tower server.&lt;br /&gt;
  This beastie has plenty of space - four Hard Drive bays. Added a PCI-E intel Gbit NIC. Added 1TB WD caviar SATA 7200rpm&lt;br /&gt;
  DVB-T freecom USB stick.&lt;br /&gt;
  (&#039;&#039;Tried this with previously working driver and it causes bad things to happen, lsusb freezes.&lt;br /&gt;
  Found newer version here [http://ubuntuforums.org/showpost.php?p=6098621&amp;amp;postcount=5 Intrepid pkg] yet to test...&#039;&#039;)&lt;br /&gt;
  2x[[DVBworld_HD-2104-USB-S2|DVBWorld]] DVB-S2 USB receivers.&lt;br /&gt;
  2x[[TP30|Topping TP30]] USB DACs fed by squeezeslaves for two audio zones.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Zwave&#039;&#039;&#039;&lt;br /&gt;
  Z-wave zcu201 controller - for now.&lt;br /&gt;
  3x Qees Reto plus inline dimmer&lt;br /&gt;
  1x Fibaro dimmer FGD211.&lt;br /&gt;
  1x Fibaro dual Relay FGS221.&lt;br /&gt;
  1x Aeon Minimote&lt;br /&gt;
  1x Z-wave.me Key chain controller.&lt;br /&gt;
  1x Everspring SP814 Motion detector&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;NAS&#039;&#039;&#039;&lt;br /&gt;
  Netgear Readynas NV+&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;MD&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
  Restarted on the [[ASUS M2N-VM]] HDMI mothorboard based Media director.&lt;br /&gt;
  Pxe booting and UI2 overlay in operation!&lt;br /&gt;
  No extras required so far - will update this with additions whenever needed.&lt;br /&gt;
  AMD 64 X2 4200+ processor, 1GB RAM, slot load slimline DVD.&lt;br /&gt;
&lt;br /&gt;
  Pegatron Cape7&lt;br /&gt;
  Pxe booting and UI2 overlay in operation!&lt;br /&gt;
  Phoenix Duet - similar to the [[Phoenix_Solo_USB|Phoenix solo]] but with built-in spkr, need to revert alsa drivers [http://forum.linuxmce.org/index.php?topic=10428.msg72593#msg72593 see this forum post] to get this going.&lt;br /&gt;
&lt;br /&gt;
  3 x Squeezebox receivers for audio zones.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;TV&#039;&#039;&#039;&lt;br /&gt;
  Dell 19&amp;quot; LCD [[Dell_W1900|Dell W1900]]&lt;br /&gt;
  &#039;&#039;see note re audio in&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
  Pioneer PDPLX5090&lt;br /&gt;
  Controlled by Pegatron Cape7 MD, USBtoSerial converter.&lt;br /&gt;
  Works PnP in 10.04/12.04, AFAIK also in 8.10 but there were some issues with /dev/ttyUSB0 vs /dev/&amp;lt;dev id&amp;gt;&lt;br /&gt;
  &lt;br /&gt;
&#039;&#039;&#039;AV Receiver&#039;&#039;&#039;&lt;br /&gt;
  Denon AVR-2312&lt;br /&gt;
  &#039;&#039;Not controlled by MD yet. Serial template exists - what about LAN?&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Orbiters&#039;&#039;&#039;&lt;br /&gt;
  WebDT&lt;br /&gt;
  N900&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Coley&amp;diff=36741</id>
		<title>User:Coley</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Coley&amp;diff=36741"/>
		<updated>2016-05-12T17:58:45Z</updated>

		<summary type="html">&lt;p&gt;Coley: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:User Setups]]&lt;br /&gt;
&lt;br /&gt;
I may as well put some details on my set-up here. At the moment it is at the experimental stage, time invested now will be just that, beginning to get time to play with this in freshly renovated house.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Dedicated Core&#039;&#039;&#039;&lt;br /&gt;
  Recently installed 14.04.&lt;br /&gt;
  Now on a [[HP ML115 G5]] micro tower server.&lt;br /&gt;
  This beastie has plenty of space - four Hard Drive bays. Added a PCI-E intel Gbit NIC. Added 1TB WD caviar SATA 7200rpm&lt;br /&gt;
  DVB-T freecom USB stick.&lt;br /&gt;
  (&#039;&#039;Tried this with previously working driver and it causes bad things to happen, lsusb freezes.&lt;br /&gt;
  Found newer version here [http://ubuntuforums.org/showpost.php?p=6098621&amp;amp;postcount=5 Intrepid pkg] yet to test...&#039;&#039;)&lt;br /&gt;
  2x[[DVBworld_HD-2104-USB-S2|DVBWorld]] DVB-S2 USB receivers.&lt;br /&gt;
  2x[[TP30|Topping TP30]] USB DACs fed by squeezeslaves for two audio zones.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Zwave&#039;&#039;&#039;&lt;br /&gt;
  Z-wave zcu201 controller - for now.&lt;br /&gt;
  3x Qees Reto plus inline dimmer&lt;br /&gt;
  1x Fibaro dimmer FGD211.&lt;br /&gt;
  1x Fibaro dual Relay FGS221.&lt;br /&gt;
  1x Aeon Minimote&lt;br /&gt;
  1x Z-wave.me Key chain controller.&lt;br /&gt;
  1x Everspring SP814 Motion detector&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;NAS&#039;&#039;&#039;&lt;br /&gt;
  Netgear Readynas NV+&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;MD&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
  Restarted on the [[ASUS M2N-VM]] HDMI mothorboard based Media director.&lt;br /&gt;
  Pxe booting and UI2 overlay in operation!&lt;br /&gt;
  No extras required so far - will update this with additions whenever needed.&lt;br /&gt;
  AMD 64 X2 4200+ processor, 1GB RAM, slot load slimline DVD.&lt;br /&gt;
&lt;br /&gt;
  Pegatron Cape7&lt;br /&gt;
  Pxe booting and UI2 overlay in operation!&lt;br /&gt;
  Phoenix Duet - similar to the [[Phoenix_Solo_USB|Phoenix solo]] but with built-in spkr, need to revert alsa drivers [http://forum.linuxmce.org/index.php?topic=10428.msg72593#msg72593 see this forum post] to get this going.&lt;br /&gt;
&lt;br /&gt;
  HP Laptop - n/w boot&lt;br /&gt;
&lt;br /&gt;
  3 x Squeezebox receivers for audio zones.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;TV&#039;&#039;&#039;&lt;br /&gt;
  Dell 19&amp;quot; LCD [[Dell_W1900|Dell W1900]]&lt;br /&gt;
  &#039;&#039;see note re audio in&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
  Pioneer PDPLX5090&lt;br /&gt;
  Controlled by Pegatron Cape7 MD, USBtoSerial converter.&lt;br /&gt;
  Works PnP in 10.04/12.04, AFAIK also in 8.10 but there were some issues with /dev/ttyUSB0 vs /dev/&amp;lt;dev id&amp;gt;&lt;br /&gt;
  &lt;br /&gt;
&#039;&#039;&#039;AV Receiver&#039;&#039;&#039;&lt;br /&gt;
  Denon AVR-2312&lt;br /&gt;
  &#039;&#039;Not controlled by MD yet. Serial template exists - what about LAN?&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Orbiters&#039;&#039;&#039;&lt;br /&gt;
  WebDT&lt;br /&gt;
  N95&lt;br /&gt;
  iPAQ&lt;br /&gt;
  N900&lt;br /&gt;
  iPhone&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Quicken_1-8.8.8-5.1.3-5.9.7.8_Quicken_t.e.ch._s.u.p.p.o.r.t_n.u.m.b.e.r,Quicken&amp;diff=36727</id>
		<title>Quicken 1-8.8.8-5.1.3-5.9.7.8 Quicken t.e.ch. s.u.p.p.o.r.t n.u.m.b.e.r,Quicken</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Quicken_1-8.8.8-5.1.3-5.9.7.8_Quicken_t.e.ch._s.u.p.p.o.r.t_n.u.m.b.e.r,Quicken&amp;diff=36727"/>
		<updated>2016-04-13T17:36:26Z</updated>

		<summary type="html">&lt;p&gt;Coley: deleted spam - admin please delete page&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=File_talk:Forum.gif&amp;diff=35127</id>
		<title>File talk:Forum.gif</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=File_talk:Forum.gif&amp;diff=35127"/>
		<updated>2014-08-06T11:29:45Z</updated>

		<summary type="html">&lt;p&gt;Coley: Undo revision 35126 by YTeectextine (talk) spam&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Installation_Guide&amp;diff=35034</id>
		<title>Installation Guide</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Installation_Guide&amp;diff=35034"/>
		<updated>2014-04-30T16:15:30Z</updated>

		<summary type="html">&lt;p&gt;Coley: Undo revision 35024 by Domtheo (talk) spam&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Installation Tutorials| Installation Tutorials]]&lt;br /&gt;
{| align=&amp;quot;right&amp;quot;&lt;br /&gt;
  | __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
&lt;br /&gt;
For the most up-to-date Final Release see the [[Installing 1004|&#039;&#039;&#039;LinuxMCE 1004&#039;&#039;&#039;]] install&lt;br /&gt;
&lt;br /&gt;
==About Installation (Version 0810 Final)==&lt;br /&gt;
&lt;br /&gt;
This page covers what we&#039;ll call mainstream installation. It shows how to get a LinuxMCE hybrid running with minimum bells and whistles. Once the basic installation is complete, users can look at the other sections of the wiki to learn how to add more advanced features. The basic hardware consists of the computer, display, and speakers. Look at the &amp;quot;Core &amp;amp; Hybrid&amp;quot; section of the wiki for hardware selection articles. Here is some pre-flight advice before installation.&lt;br /&gt;
&lt;br /&gt;
*The computer must be connected to the internet for a successful installation. &lt;br /&gt;
*Recommend using a monitor for the initial install. Monitors are better than TVs for adapting to a wacky resolution setting (it could happen). You probably don&#039;t want to mess about with xorg.conf on your first install. Also recommend using a VGA cable because that is the default setting when the LMCE wizard pops up. I&#039;d specifically advise against using an HDMI cable and expecting it to pass video and sound to your TV. It might work, but more likely it will require extensive tinkering. Its easy to swap to a different display or connection after things are up and running. &lt;br /&gt;
*For sound, you can use computer speakers, or use an spdif connection to an external AV receiver. This is also easy to change later.&lt;br /&gt;
*If you have a TV capture card, it will be configured during the installation. The wizard will ask where to get program guide information. In the US this is usually &amp;quot;schedulesdirect.org&amp;quot;. Set up your account and know your username and password before starting the install.&lt;br /&gt;
&lt;br /&gt;
==Caveats==&lt;br /&gt;
&lt;br /&gt;
*LinuxMCE is an extremely powerful, fantastic piece of software; have no doubt about that. But, please bear in mind that it is a project, not a product. &lt;br /&gt;
&lt;br /&gt;
*LinuxMCE 0810 is based on Ubuntu 8.10, which means that brand new hardware might not work out of the box. For this reason, if you are buying hardware specifically for your home automation system, you might want to use hardware that is a little older and save yourself some money at the same time. That said, in nearly all cases you will be able to get through any issues with a little patience and some help from the community. Unrecognised NICs is the most common issue.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#FF0000&amp;quot;&amp;gt;Please please please be patient. Some parts of the installation can sometimes take hours. If in doubt, leave it overnight.&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Basic Installation Steps==&lt;br /&gt;
&lt;br /&gt;
I might help to think of installation as a 3-step process.&lt;br /&gt;
*Run the DVD. This formats your drive, installs Kubuntu, and preps for LMCE installation. This step finishes by prompting reboot and DVD removal.&lt;br /&gt;
*Install LinuxMCE. The reboot will take you to the Kubuntu screen. You&#039;ll recheck your internet connection, then click the LMCE install icon. More software will load and it will prompt another reboot.&lt;br /&gt;
*Complete the 3 wizards (AV, House Setup, Media). This is where you tell LMCE about your system.&lt;br /&gt;
&lt;br /&gt;
===Run the DVD===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#FF0000&amp;quot;&amp;gt;Caution: Installing LinuxMCE 0810 Final will wipe your entire drive! It is not designed to be dual-booted!&amp;lt;/span&amp;gt;&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If you just want to quickly try LinuxMCE, then consider setting it up temporarily as a virtual machine on your Linux, Mac, or Windows box. [http://www.virtualbox.org/ VirtualBox] will allow you to do this&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
# Download the LinuxMCE 0810 Final ISO from [http://linuxmce.iptp.org/release/LinuxMCE-8.10-final.iso here]. &#039;&#039;Note: Always burn at your DVD drive&#039;s lowest speed to reduce the chance of errors.&#039;&#039;&lt;br /&gt;
# Boot from the DVD.&lt;br /&gt;
# Select your language&lt;br /&gt;
# Select the top option &amp;quot;LinuxMCE&amp;quot;&lt;br /&gt;
# Wait until the installer loads, and then...&lt;br /&gt;
## &#039;&#039;&#039;Welcome&#039;&#039;&#039; - Select your language.&lt;br /&gt;
## &#039;&#039;&#039;Where are you?&#039;&#039;&#039; - Select your location and time zone.&lt;br /&gt;
## &#039;&#039;&#039;Keyboard layout&#039;&#039;&#039; - Select your keyboard layout.&lt;br /&gt;
## &#039;&#039;&#039;Prepare disk space&#039;&#039;&#039; - Set up your partitions as you wish, but the second option &amp;quot;Guided - use entire disk&amp;quot; is perfectly OK.&lt;br /&gt;
## &#039;&#039;&#039;Who are you?&#039;&#039;&#039; - Set up your username, password and the system name (call it whatever you want). This username/password is specifically for the underlying system i.e. Kubuntu, it is NOT for LinuxMCE; this is handled separately.&lt;br /&gt;
## &#039;&#039;&#039;Ready to install&#039;&#039;&#039; - Check everything is as it should be, and press &amp;quot;Install&amp;quot;.&lt;br /&gt;
# Let installation run through, and then remove disk and press enter when instructed to do so.&lt;br /&gt;
&lt;br /&gt;
===Install LinuxMCE===&lt;br /&gt;
&lt;br /&gt;
# Once the new Kubuntu installation has finished booting back up, check that your internet connections are working. If you have a NIC that is not plug-and-play (like the Intel gigabit card) then now is the time to install the driver and confirm operation. Then click the &amp;quot;LinuxMCE&amp;quot; icon on the desktop. This will start the LinuxMCE installation. You may need to enter your Kubuntu password. &lt;br /&gt;
# Wait until the LinuxMCE installation has finished running through. You will see the following message when the installation is complete:&lt;br /&gt;
&lt;br /&gt;
 The first phase of the install process is completed&lt;br /&gt;
 Reboot the system to start the final process.&lt;br /&gt;
&lt;br /&gt;
===Complete the Wizards===&lt;br /&gt;
&lt;br /&gt;
Upon reboot, you will not see Kubuntu. More software will load, then the AV Wizard will start. If you connected the display with something other than a VGA cable, the screen will go black. You will have to press a number on your keyboard (just the number, don&#039;t hit &amp;quot;enter&amp;quot;) to tell the wizard what connection to use. The default value is 2: VGA.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt; Keys for choosing a connector:&lt;br /&gt;
&lt;br /&gt;
1: DVI&lt;br /&gt;
2: VGA&lt;br /&gt;
3: Component&lt;br /&gt;
4: Composite&lt;br /&gt;
5: S-Video&lt;br /&gt;
Q: DVI-2&lt;br /&gt;
W: VGA-2&lt;br /&gt;
L: LVDS&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then follow the wizards as described in the following links.&lt;br /&gt;
&lt;br /&gt;
*[[AVWizard_Step_by_Step|AV Wizard]] &lt;br /&gt;
*[[House_Setup_Wizard|House Setup Wizard]] &lt;br /&gt;
*[[Media_Player_Wizard|Media Setup Wizard]].&lt;br /&gt;
&lt;br /&gt;
Tip: After LMCE is up and running, the LinuxMCE installation icon on the Kubuntu desktop becomes a hazard. Clicking it will begin a reinstall and ruin your day. Best to right click and delete the icon!&lt;br /&gt;
==Links==&lt;br /&gt;
&lt;br /&gt;
*[[:Category:AV_Wizard|AV Wizard]]&lt;br /&gt;
*[[:Category:Installation_Tutorials|General Installation Tutorials]]&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Media_Director&amp;diff=35033</id>
		<title>Media Director</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Media_Director&amp;diff=35033"/>
		<updated>2014-04-30T16:14:39Z</updated>

		<summary type="html">&lt;p&gt;Coley: Undo revision 35025 by Domtheo (talk) spam&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt; {| align=&amp;quot;right&amp;quot;&lt;br /&gt;
  | __TOC__&lt;br /&gt;
  |}&lt;br /&gt;
&lt;br /&gt;
This page defines what a Media Director (MD) is, what it does, how it fits in the LinuxMCE system, and how to select the components necessary for an enjoyable media experience.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== What is a Media Director? ==&lt;br /&gt;
A &#039;&#039;&#039;Media Director&#039;&#039;&#039; (also known as a &#039;&#039;&#039;Media Station&#039;&#039;&#039;) is a PC which channels the audio and video content managed by the LinuxMCE system to the audiovisual devices which are connected to it. &lt;br /&gt;
[[Media Directors]] (MDs for short) are Home Theater PCs (HTPC) with outputs to connect to a television and to speakers. A MD can play all your streaming music and videos, whether from the Core, from network attached storage (NAS), or from other MDs in your system.&lt;br /&gt;
&lt;br /&gt;
{{p}}&lt;br /&gt;
&lt;br /&gt;
== Media Directors and the LinuxMCE system ==&lt;br /&gt;
A LinuxMCE system is made of a single [[Core]] and multiple Media Directors. While it is possible to run the Core as a Media Director also, making it a [[hybrid]] Core/Media Director, you still need a dedicated Media Director for each room or entertainment area where you would like to receive the media. With multiple rooms, this results in multiple Media Directors present in the LinuxMCE system.&lt;br /&gt;
&lt;br /&gt;
Each Media Director is connected to the LinuxMCE [[Core]] server through the home automation/multimedia LAN by its LAN port (NIC). It is also fitted with connections for the TV, stereo or other AV devices through which content is output to the AV devices connected to it. A Media Director PC needs LAN and A/V ports (such as VGA, HDMI, S-video or RCA jacks), and is generally located close to the viewing/listening area.&lt;br /&gt;
&lt;br /&gt;
{{p}}&lt;br /&gt;
&lt;br /&gt;
== Media Director PC components ==&lt;br /&gt;
A Media Director is selected based on the quality of the images and sound it can produce, and the connections necessary for the A/V application. Choosing or building a PC that will be used as a Media Director must be done carefully with respect to the input and output capabilities of that PC. &lt;br /&gt;
These demands are more easily met with a Media Director than with a Home Theater PC, since many of the functions of a standalone HTPC have been moved to the Core in a LinuxMCE system, reducing the hardware requirements of each Media Director, making the Media Director much less expensive than a Home Theater PC.&lt;br /&gt;
&lt;br /&gt;
This section explains the role of each component, and gives you the understanding you need to select Media Directors.&lt;br /&gt;
{{p}}&lt;br /&gt;
&lt;br /&gt;
==== Audio and video ====&lt;br /&gt;
Because media is served through the graphics and sound cards of the Media Director PC, it needs to have a good (nVidia) graphics card and a good sound card (e.g. with 5.1 or 7.1 outputs). Outputs to TV and stereo are directly from a Media Director, so quality output cards are needed.&lt;br /&gt;
&lt;br /&gt;
The Core generally has the TV tuner card for the entire system. A Media Director does not typically need one. {{p}}&lt;br /&gt;
&lt;br /&gt;
==== Remote controls ==== &lt;br /&gt;
A Media Director also provides the interface for input devices. Remote controls (USB-UIRTs, bluetooth devices, etc), in general, are connected to a Media Director. {{p}}&lt;br /&gt;
&lt;br /&gt;
==== Environmental considerations ====&lt;br /&gt;
While a dedicated core can be hidden in a closet or somewhere else, each Media Director is generally attached to a TV or entertainment center. As such, it has requirements similar to a [http://en.wikipedia.org/wiki/Home_theater_PC Home Theater PC]: it should be whisper-quiet (either with very quiet fans or a fan-less heat sink), have low heat emission (which usually implies low power consumption) and be small and unobtrusive (in a stylish case). {{p}}&lt;br /&gt;
&lt;br /&gt;
==== Storage ==== &lt;br /&gt;
Unlike a Home Theater PC, the Media Director does not require a large storage capacity. Storage functions are provided by the Core (or hybrid), not the Media Director. You can, however, add storage to a Media Director, but it is not necessary since the Core carries the PVR and all network media storage functions for the entire system. Only the Core needs a large hard drive storage capacity. {{p}}&lt;br /&gt;
&lt;br /&gt;
==== Processor ==== &lt;br /&gt;
It is important to note that video decoding takes place locally on the Media Director. It would be prudent to ensure that the processing power of the Media Director is sufficient for your media, be it standard definition or high definition content. &lt;br /&gt;
&lt;br /&gt;
{{p}}&lt;br /&gt;
&lt;br /&gt;
== Media Director OS ==&lt;br /&gt;
&lt;br /&gt;
A Media Directors does not require an OS. It can act as a thin client, [[netboot]] from the Core, and be fully operational within minutes. &lt;br /&gt;
&lt;br /&gt;
{{p}}&lt;br /&gt;
&lt;br /&gt;
== Hybrids ==&lt;br /&gt;
When a [[Core]] is also used as a Media Director, it is called a [[Hybrid]]. Since a Hybrid Computer performs all the Core functions and the Media Director functions also, it needs to be capable and all the recommendations for Media Directors apply.&lt;br /&gt;
&lt;br /&gt;
{{p}}&lt;br /&gt;
&lt;br /&gt;
==Links==&lt;br /&gt;
&lt;br /&gt;
*[[:Category:Media_Directors|Possible Media Director platforms]]&lt;br /&gt;
*[[:Category:Laptops|Laptop Media Directors]]&lt;br /&gt;
*[[:Category:Nettops|Nettop Media Directors]]&lt;br /&gt;
&lt;br /&gt;
[[Category: Media Directors]]&lt;br /&gt;
*[[:Category:MediaDirectorTutorials|General Media Director Tutorials]]&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Telecom&amp;diff=35032</id>
		<title>Telecom</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Telecom&amp;diff=35032"/>
		<updated>2014-04-30T16:13:50Z</updated>

		<summary type="html">&lt;p&gt;Coley: Undo revision 35026 by Domtheo (talk) spam&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Links==&lt;br /&gt;
&lt;br /&gt;
*[[:Category:Phone_Lines|Phone Lines]]&lt;br /&gt;
*[[:Category:ATA|Analog Telephone Adapters]]&lt;br /&gt;
*[[:Category:IP_Phones|IP Phones]]&lt;br /&gt;
*[[:Category:Telecom_Tutorials|General Telecom Tutorials]]&lt;br /&gt;
*[[Voice Applications]]&lt;br /&gt;
&lt;br /&gt;
==About==&lt;br /&gt;
&lt;br /&gt;
LinuxMCE has very powerful and flexible telecom capability. Examples include:&lt;br /&gt;
* VOIP phone line provider with an IP Phone (the Cisco 7970 even doubles as an orbiter).&lt;br /&gt;
* VOIP phone line provider with Analog Telephone Adapter (ATA) to use a standard phone.&lt;br /&gt;
* Regular telephone line with ATA&lt;br /&gt;
 &lt;br /&gt;
Telecom in LinuxMCE is enabled by the integration of an open source PBX system for Linux called [http://en.wikipedia.org/wiki/Asterisk_%28PBX%29 Asterisk].&lt;br /&gt;
&lt;br /&gt;
The basic Asterisk software includes many features available in proprietary PBX systems: voice mail, conference calling, interactive voice response (phone menus) and automatic call distribution.&lt;br /&gt;
&lt;br /&gt;
To attach ordinary telephones to a Linux server running Asterisk or to connect to PSTN trunk lines, the server must be fitted with special hardware. Digium and a number of other firms sell PCI cards to attach telephones, telephone lines, T1 and E1 lines, plus other analog and digital phone services to a server.&lt;br /&gt;
&lt;br /&gt;
Perhaps of more interest to many deployers today, Asterisk also supports a wide range of Voice over IP protocols, including SIP, MGCP and H.323. Asterisk can interoperate with most SIP telephones, acting both as registrar and as a gateway between IP phones and the PSTN. Asterisk developers have also designed a new protocol, Inter-Asterisk eXchange (IAX2), for efficient trunking of calls among Asterisk PBXs and to VoIP service providers who support it. Some telephones support the IAX2 protocol directly for communicating with an Asterisk server (see Comparison of VoIP software for examples).&lt;br /&gt;
&lt;br /&gt;
VoIP telephone companies have begun to support Asterisk; many now offer IAX2 or SIP trunking direct to an Asterisk box as an alternative to providing the customer with an ATA.&lt;br /&gt;
&lt;br /&gt;
Telecom functionality involves 5 basic steps. Wiki contributors should cover all 5. &lt;br /&gt;
&lt;br /&gt;
1. Install hardware.&lt;br /&gt;
&lt;br /&gt;
2. Configure LMCE phone device. This tells LMCE how to communicate with the new hardware&lt;br /&gt;
&lt;br /&gt;
3. Configure LMCE phone line device. This tells LMCE how to communicate with the VOIP provider or telephone company.&lt;br /&gt;
&lt;br /&gt;
4. Configure Asterisk using FreePBX. This is LMCE&#039;s telecom brain&lt;br /&gt;
&lt;br /&gt;
5. Configure the new telecom hardware. This tells the VOIP phone or ATA how to communicate with LMCE&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Bmac2&amp;diff=34909</id>
		<title>User:Bmac2</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Bmac2&amp;diff=34909"/>
		<updated>2014-04-02T16:42:55Z</updated>

		<summary type="html">&lt;p&gt;Coley: Undo revision 34908 by VostokUrbanda (talk) spam&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:User Setups]]&lt;br /&gt;
[[Category:VOIP Setups]]&lt;br /&gt;
[[Category: Telecom_Setups]]&lt;br /&gt;
[[Category:Standard Definition Setups]]&lt;br /&gt;
[[Image:Bmac2.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 Barry McCormick&lt;br /&gt;
 Douglas Street&lt;br /&gt;
 Salt Lake City, Utah 84102&lt;br /&gt;
 USA&lt;br /&gt;
 VOIP Phone: 801-438-3590&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
My username is bmac2, I am not a JR, or anything like that, on an old bbs in the late 80s early 90s one bbs required there to be at least one number on your username, and i was using bmac  (short for Barry McCormick) and I added a 2 to it.  Been using that name almost exclusively online since.&lt;br /&gt;
&lt;br /&gt;
I was born in Alabama and have both my BS and MS in Chemical Engineering from the University of Alabama.  I lived in Texas for about 10 years total, 4 years in the army at Ft. Hood, over a year in Austin, then a good 3 in Houston.  I then lived New Orleans from 1997 until 2001 when I moved to Salt Lake City, Utah for family reasons.&lt;br /&gt;
&lt;br /&gt;
My LMCE setup is currently as detailed below.  It is far from being complete, but I am being hounded by our resident wiki nazi ( g you KNOW who you are!!!) so here goes.&lt;br /&gt;
&lt;br /&gt;
=Core/Hybrid=&lt;br /&gt;
&lt;br /&gt;
I use a hybrid core in my setup.  I have my office/workspace/media room in the basement of my house.  Since my core is down here it makes more sense for me to use it as a hybrid and not have another computer running.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Motherboard&#039;&#039;&#039;&lt;br /&gt;
* ABIT AN-M2 ver 2.0  Socket AM2 940 Processor with 2000MT/s system bus&lt;br /&gt;
*Micro-ATX form factor (244mm x 244mm)&lt;br /&gt;
*1x PCI-E X16 slot &lt;br /&gt;
*1x PCI-E X1 slot &lt;br /&gt;
*2 PCI slots&lt;br /&gt;
*built in gigabit network card&lt;br /&gt;
*2 IDE channels&lt;br /&gt;
*4 sata ports&lt;br /&gt;
*built in sound card with digital out&lt;br /&gt;
                  &lt;br /&gt;
&#039;&#039;&#039;Processor&#039;&#039;&#039;&lt;br /&gt;
*AMD 4600+ Retail box processor with AMD branded CPU Fan&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Memory&#039;&#039;&#039;&lt;br /&gt;
*4 GIG DDR 800 ram&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Video Card&#039;&#039;&#039;&lt;br /&gt;
*GeFORCE Nvidia 8600GT PCI-E 16x with 512 Meg of Memory&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hard Drives&#039;&#039;&#039; &lt;br /&gt;
*IDE - Maxtor 300 GB hard drive&lt;br /&gt;
*SATA - Western Digital 1TB green power hard drive&lt;br /&gt;
**&#039;&#039;Software Raid managed by LMCE&#039;&#039;&lt;br /&gt;
*SATA - Seagate 300 GB drive&lt;br /&gt;
*SATA - Western Digital 160 GB drive&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;DVD drive&#039;&#039;&#039;&lt;br /&gt;
*Dual layer Memorex DVD/CD/CDR reader/writer&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Media card reader&#039;&#039;&#039;&lt;br /&gt;
*no name media reader that reads 6 types of media cards.  Fits in a 5 1/4 drive bay&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Case&#039;&#039;&#039;&lt;br /&gt;
*An old case I have had for a while, nothing special except I put a brand new &amp;quot;quiet&amp;quot; power supply in it for the new motherboard. The power supply is a CG Super Power brand that I got at a local store.  480 Watt Supply with a &amp;quot;silent fan&amp;quot;.  The size was based on my running the 4600+ processor and 6 hard drives, plus dvd, etc.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Mouse and keyboard&#039;&#039;&#039;&lt;br /&gt;
*Logitech wireless ergonomic mouse and a generic HP keyboard.  My core sits next to my desk, so I don&#039;t uses any fancy remotes for it, just a mouse and a keyboard.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Serial Port card&#039;&#039;&#039;&lt;br /&gt;
The new motherboards do NOT have serial ports, so I bought a PCI-E X1 slot serial port card.  I need two serial ports, one for my projector control via serial interface, the second to try to get a vfd display working on the system.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Bluetooth&#039;&#039;&#039;&lt;br /&gt;
*A cheap targus generic bluetooth dongle (avoid these, at least get a trendnet or better!!!!)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Projector&#039;&#039;&#039;&lt;br /&gt;
*Optoma DLP projector Model EP-721&lt;br /&gt;
*Native resolution 1024x768, but capable of1080i.&lt;br /&gt;
*Projector actually made by a division of Epson.  Nice projector for under $500.&lt;br /&gt;
&lt;br /&gt;
=Den Media Director=&lt;br /&gt;
*Generic PC built to be the MD&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Motherboard&#039;&#039;&#039;&lt;br /&gt;
*ABIT AN-M2 ver 2.0  Socket AM2 940 Processor with 2000MT/s system bus&lt;br /&gt;
*Micro-ATX form factor (244mm x 244mm)&lt;br /&gt;
*1x PCI-E X16 slot &lt;br /&gt;
*1x PCI-E X1 slot &lt;br /&gt;
*2 PCI slots&lt;br /&gt;
*built in gigabit network card&lt;br /&gt;
*2 IDE channels&lt;br /&gt;
*4 sata ports&lt;br /&gt;
*built in sound card with digital out&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Processor&#039;&#039;&#039;&lt;br /&gt;
*AMD 5600+ retail with AMD fan&lt;br /&gt;
 &lt;br /&gt;
&#039;&#039;&#039;Memory&#039;&#039;&#039;&lt;br /&gt;
*4 GIG DDR 800 ram&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Video Card&#039;&#039;&#039;&lt;br /&gt;
*Nvidia 7200 PCI card&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hard drives&#039;&#039;&#039;&lt;br /&gt;
*NONE - this system network boots using PXE, so no drives needed, which makes it quieter, use less power, and generate less heat&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;DVD Drive&#039;&#039;&#039;&lt;br /&gt;
*DVD reader/writer&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Bluetooth&#039;&#039;&#039;&lt;br /&gt;
*Trendnet Bluetooth dongle&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Remote&#039;&#039;&#039;&lt;br /&gt;
*WII controller set up as a remote&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;TV Capture Card&#039;&#039;&#039;&lt;br /&gt;
*[[Hauppauge_WinTV-PVR-150_MCE]] (non mce and non remote version)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Satellite Box&#039;&#039;&#039;&lt;br /&gt;
*DirecTV Dual tuner pvr Satellite box, model R-15&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IR Control&#039;&#039;&#039;&lt;br /&gt;
*[[USB_UIRT]] with a set of IR extender dongles&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;TV&#039;&#039;&#039;&lt;br /&gt;
*CRAPPY Zenith 36 inch TUBE tv.  Hope to make it go away soon.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Stereo Reciever&#039;&#039;&#039;&lt;br /&gt;
*15 year old low end Onkyo receiver.&lt;br /&gt;
&lt;br /&gt;
=Master Bedroom Media Director=&lt;br /&gt;
&lt;br /&gt;
*Motherboard -  ???/&lt;br /&gt;
*Processor -  ?????&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Kitchen Media Director=&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Motherboard -  ???/&lt;br /&gt;
*Processor -  ?????&lt;br /&gt;
&lt;br /&gt;
=Mobile Orbiters=&lt;br /&gt;
&lt;br /&gt;
*Nokia N800 tablet pc&lt;br /&gt;
*Compaq Ipaq hx2755 color&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Phone System=&lt;br /&gt;
&lt;br /&gt;
One of the MAJOR subsystems, and in my opinion, one of the most powerful and useful subsystems in LMCE is the Asterisk/FreePBX hone system.  It allows you to do cool things like assign extensions to family members, give everyone in your family their own mailbox, etc.  Connected to a VOIP provider, your phone system can now do things that it never could before.  Forget the phone company and run your own phones the way you want them to run.&lt;br /&gt;
&lt;br /&gt;
==VOIP Provider==  &lt;br /&gt;
Broadvoice with a second number and the international package so I can place obscene calls to lmce users in other countries.&lt;br /&gt;
&lt;br /&gt;
==Cisco 7970 Phone==&lt;br /&gt;
The cadillac of phones.  These have the color touch screen, can act as an orbiter (remote control) and handle multiple extension, custom wallpapers, custom rings, etc.  Very much plug and play when you follow the wiki page on this phone set up by TSCHAK.  Mine is running the Cisco SCCP ( or skinny as it is nicknamed ) protocol.  If you can catch one of these on ebay at a reasonable price, get it.  They are a very nice phone with built in speakerphone, headset jacks, hold, transfer, etc.&lt;br /&gt;
&lt;br /&gt;
==Cisco 7960 Phone==&lt;br /&gt;
Just one step down from the 7970, but can be bought at a much cheaper prices used on places such as ebay. This model has 6 phone line/extension capability, but no color and no touchscreen.  It is a very nice solid phone, like most Cisco products.  Mine is running SCCP and was set up using the directions for the 7970, which defaults to the sccp protocol.&lt;br /&gt;
&lt;br /&gt;
==Cisco 7912 Phone==&lt;br /&gt;
A single line phone with no fancy features like speakerphone, multiple extension, but a good solid phone with a very clean looking silver top and a nice quality small monochrome display on it.  I picked mine up for around $20 + shipping on ebay.  Like all my phones, it is running SCCP protocol.&lt;br /&gt;
&lt;br /&gt;
==Analog Telephone Adapter (ATA)== &lt;br /&gt;
I bought an unlocked linksys PAP2T-NA adapter.  Make sure if you are buying an adapter off the Internet that the model has the -NA on it.  Any model without the -NA is locked to a provider like Vonage, etc.  While they CAN be unlocked, it is a very painful process, and does not always work, depending on a ton of factors when you start hacking them.  My advice, if you have one, search the internet and play, but buy yourself one that is unlocked by design and use it.  Even if you unlock one of the vonage ones, they can still possibly give you trouble.  I think mine cost me like $48 or so online.  This adapter is wired to the phone wires (cat 3 type original phone lines) that are running through the house.  So we can plug in any standard phone device, and can plug the satellite dish STBs to the phone line for programming updates.  The second port of the ATA is set up as a fax line to receive faxes, or send them if needed.  I changed the default fax line in LMCE to aim at this extension. &lt;br /&gt;
&lt;br /&gt;
==Analog Cordless Phones==&lt;br /&gt;
My wife has a set of the uniden cordless phones that has the base one that plugs into an analog phone line and the other 2 handsets attach to it wirelessly.  The entire reason I put the ATA in was so she could keep those phones and use them. These along with all the analog phones are set up on a seperate extension.  While you can&#039;t call a specific one of them, you can call the analog extension and ring them seperately. &lt;br /&gt;
&lt;br /&gt;
==Fax Machine==&lt;br /&gt;
YES I know it is old school, but I have it, and an analog port, so what the hell.  It is a 8 or 9 year old SHARP UX-510 Plain paper fax.  My plans are to set up a more sophisticated fax system with lmce, but, this was fun to do just to say I did.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Network Layout=&lt;br /&gt;
&lt;br /&gt;
As a person who works a lot as a network person, my network often changes to suite the latest thing on my plate.  But below is the base portion of my network, and what runs my systems.  My network is only 10/100 at the moment, but I intend to upgrade to gigabit at first oportunity.  The switch you choose makes ALL the difference in the sound quality of your calls.  I had to remove a fairly nice managed 3Com switch from my network and replace it with an an ancient Cisco 300FastHub.  That cleared all the echo of my phones.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:Network flow.png]]&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=File_talk:Forum.gif&amp;diff=34891</id>
		<title>File talk:Forum.gif</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=File_talk:Forum.gif&amp;diff=34891"/>
		<updated>2014-03-28T15:18:12Z</updated>

		<summary type="html">&lt;p&gt;Coley: Undo revision 34890 by Haignishino (talk) spam&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Coley&amp;diff=34889</id>
		<title>User:Coley</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Coley&amp;diff=34889"/>
		<updated>2014-03-25T12:56:23Z</updated>

		<summary type="html">&lt;p&gt;Coley: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:User Setups]]&lt;br /&gt;
&lt;br /&gt;
I may as well put some details on my set-up here. At the moment it is at the experimental stage, time invested now will be just that, beginning to get time to play with this in freshly renovated house.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Dedicated Core&#039;&#039;&#039;&lt;br /&gt;
  Recently &amp;quot;upgraded&amp;quot; to 12.04 alpha.&lt;br /&gt;
  Now on a [[HP ML115 G5]] micro tower server.&lt;br /&gt;
  This beastie has plenty of space - four Hard Drive bays. Added a PCI-E intel Gbit NIC. Added 1TB WD caviar SATA 7200rpm&lt;br /&gt;
  DVB-T freecom USB stick.&lt;br /&gt;
  (&#039;&#039;Tried this with previously working driver and it causes bad things to happen, lsusb freezes.&lt;br /&gt;
  Found newer version here [http://ubuntuforums.org/showpost.php?p=6098621&amp;amp;postcount=5 Intrepid pkg] yet to test...&#039;&#039;)&lt;br /&gt;
  2x[[DVBworld_HD-2104-USB-S2|DVBWorld]] DVB-S2 USB receivers.&lt;br /&gt;
  2x[[TP30|Topping TP30]] USB DACs fed by squeezeslaves for two audio zones.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Zwave&#039;&#039;&#039;&lt;br /&gt;
  Z-wave zcu201 controller - for now.&lt;br /&gt;
  3x Qees Reto plus inline dimmer&lt;br /&gt;
  1x Fibaro dimmer FGD211.&lt;br /&gt;
  1x Fibaro dual Relay FGS221.&lt;br /&gt;
  1x Aeon Minimote&lt;br /&gt;
  1x Z-wave.me Key chain controller.&lt;br /&gt;
  1x Everspring SP814 Motion detector&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;NAS&#039;&#039;&#039;&lt;br /&gt;
  Netgear Readynas NV+&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;MD&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
  Restarted on the [[ASUS M2N-VM]] HDMI mothorboard based Media director.&lt;br /&gt;
  Pxe booting and UI2 overlay in operation!&lt;br /&gt;
  No extras required so far - will update this with additions whenever needed.&lt;br /&gt;
  AMD 64 X2 4200+ processor, 1GB RAM, slot load slimline DVD.&lt;br /&gt;
&lt;br /&gt;
  Pegatron Cape7&lt;br /&gt;
  Pxe booting and UI2 overlay in operation!&lt;br /&gt;
  Phoenix Duet - similar to the [[Phoenix_Solo_USB|Phoenix solo]] but with built-in spkr, need to revert alsa drivers [http://forum.linuxmce.org/index.php?topic=10428.msg72593#msg72593 see this forum post] to get this going.&lt;br /&gt;
&lt;br /&gt;
  HP Laptop - n/w boot&lt;br /&gt;
&lt;br /&gt;
  3 x Squeezebox receivers for audio zones.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;TV&#039;&#039;&#039;&lt;br /&gt;
  Dell 19&amp;quot; LCD [[Dell_W1900|Dell W1900]]&lt;br /&gt;
  &#039;&#039;see note re audio in&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
  Pioneer PDPLX5090&lt;br /&gt;
  Controlled by Pegatron Cape7 MD, USBtoSerial converter.&lt;br /&gt;
  Works PnP in 10.04/12.04, AFAIK also in 8.10 but there were some issues with /dev/ttyUSB0 vs /dev/&amp;lt;dev id&amp;gt;&lt;br /&gt;
  &lt;br /&gt;
&#039;&#039;&#039;AV Receiver&#039;&#039;&#039;&lt;br /&gt;
  Denon AVR-2312&lt;br /&gt;
  &#039;&#039;Not controlled by MD yet. Serial template exists - what about LAN?&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Orbiters&#039;&#039;&#039;&lt;br /&gt;
  WebDT&lt;br /&gt;
  N95&lt;br /&gt;
  iPAQ&lt;br /&gt;
  N900&lt;br /&gt;
  iPhone&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=File_talk:Forum.gif&amp;diff=34880</id>
		<title>File talk:Forum.gif</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=File_talk:Forum.gif&amp;diff=34880"/>
		<updated>2014-03-21T12:25:54Z</updated>

		<summary type="html">&lt;p&gt;Coley: Undo revision 34878 by Haignishino (talk) spam...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Snapshot_overview&amp;diff=34874</id>
		<title>Snapshot overview</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Snapshot_overview&amp;diff=34874"/>
		<updated>2014-03-19T16:05:36Z</updated>

		<summary type="html">&lt;p&gt;Coley: /* HW Install Remarks */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Software]][[Category: testing]][[Category: 1204]][[Category:LinuxMCE Releases]]&lt;br /&gt;
&lt;br /&gt;
This page will help users to pick a snapshot for testing or use. You can download from this page http://linuxmce.iptp.org/snapshots/. Not all snapshots work, so please choose ones below that are reported working.&lt;br /&gt;
You can find an overview of fixes and listed bugs here http://svn.linuxmce.org/trac.cgi/report/1?sort=type&amp;amp;asc=1&amp;amp;page=1. If you find unreported bugs please report them in the svn. This page is a work in progress but the information is valid.&lt;br /&gt;
&lt;br /&gt;
===Recommended Download===&lt;br /&gt;
[http://linuxmce.iptp.org/snapshots/LMCE-1204-20140311212428804.iso LMCE-1204-20140311212428804.iso]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039; MD5SUM: ff2870eacca552c492f9077d2e462d8d &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table  border=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; width=600&amp;gt; &amp;lt;!----If something has an issue, include a link to the svn ticket or forum post ----------&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#CCCC66&amp;quot;&amp;gt;[http://linuxmce.iptp.org/snapshots/LMCE-1204-20140311212428804.iso LMCE-1204-20140311212428804.iso] 12-Mar-2014 00:37&amp;lt;/td&amp;gt;    &amp;lt;!----Enter ISO Name with link!----------&amp;gt;&lt;br /&gt;
     &amp;lt;td&amp;gt;VM&amp;lt;/td&amp;gt;&lt;br /&gt;
     &amp;lt;td&amp;gt;Hardware&amp;lt;/td&amp;gt;&lt;br /&gt;
      &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td width=&amp;quot;145&amp;quot; bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Audio&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td width=&amp;quot;16&amp;quot; bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt; &amp;lt;!----Enter VM Status NOTE: bg color either red or green or grey----------&amp;gt;&lt;br /&gt;
    &amp;lt;td width=&amp;quot;17&amp;quot; bgcolor=&amp;quot;green&amp;quot;&amp;gt;&#039;&#039;&#039;PASS&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Video - Stored media / DVD Playback&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;green&amp;quot;&amp;gt;&#039;&#039;&#039;PASS&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Diskless MD creation&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;green&amp;quot;&amp;gt;&#039;&#039;&#039;PASS&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;MythTV&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;green&amp;quot;&amp;gt;&#039;&#039;&#039;PASS&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;VDR&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Online Services&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;green&amp;quot;&amp;gt;&#039;&#039;&#039;PASS&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Automation - Insteon&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Automation - X10&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Automation - Zwave&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Networking&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;greY&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;green&amp;quot;&amp;gt;&#039;&#039;&#039;PASS&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Security&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Telecom&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===HW Install Remarks===&lt;br /&gt;
-&lt;br /&gt;
&lt;br /&gt;
vesa graphics does not show bootsplash, instead displaying backgrounding errors. These errors occur on every Ubuntu/Kubuntu disk, you typically do not see them because their bootsplash is different than ours, so please disregard them. L3mce&lt;br /&gt;
&lt;br /&gt;
No need to run DisklessCreateTBZ.sh.&lt;br /&gt;
&lt;br /&gt;
Had slight issues on reboot to AVWIz with AMD HD GPU. Took a very long time to get there +- 45min but thereafter graphics working at least as well as 10.04.&lt;br /&gt;
&lt;br /&gt;
Also had a few issues on Zbox MD where there are quite a few requests to reload router. In addition, I saw messages appearing to install Denon AV receiver (which I don&#039;t have) and some other device which I don&#039;t have. They are not in the device tree, though.&lt;br /&gt;
&lt;br /&gt;
So far so good. 1 Core/Hybrid and 1 Zbox MD.&lt;br /&gt;
Hardware profile: [[User:Jamo|Jamo]]&lt;br /&gt;
&lt;br /&gt;
MythTV installs ok, IP addr of backend is set incorrectly to 127.0.0.1, This has been updated afaik for newer snaps.&lt;br /&gt;
&lt;br /&gt;
===Failed Installations===&lt;br /&gt;
LMCE-1204-20140226223128766.iso 26-Feb-2014 23:21 | &#039;&#039;&#039;FAIL&#039;&#039;&#039; Networking issues [http://forum.linuxmce.org/index.php?topic=13585.0]&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Previous succesfull installs===&lt;br /&gt;
[http://linuxmce.iptp.org/snapshots/LMCE-1204-20140302030428788.iso LMCE-1204-20140302030428788.iso]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Snapshot_overview&amp;diff=34873</id>
		<title>Snapshot overview</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Snapshot_overview&amp;diff=34873"/>
		<updated>2014-03-19T16:03:52Z</updated>

		<summary type="html">&lt;p&gt;Coley: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Software]][[Category: testing]][[Category: 1204]][[Category:LinuxMCE Releases]]&lt;br /&gt;
&lt;br /&gt;
This page will help users to pick a snapshot for testing or use. You can download from this page http://linuxmce.iptp.org/snapshots/. Not all snapshots work, so please choose ones below that are reported working.&lt;br /&gt;
You can find an overview of fixes and listed bugs here http://svn.linuxmce.org/trac.cgi/report/1?sort=type&amp;amp;asc=1&amp;amp;page=1. If you find unreported bugs please report them in the svn. This page is a work in progress but the information is valid.&lt;br /&gt;
&lt;br /&gt;
===Recommended Download===&lt;br /&gt;
[http://linuxmce.iptp.org/snapshots/LMCE-1204-20140311212428804.iso LMCE-1204-20140311212428804.iso]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039; MD5SUM: ff2870eacca552c492f9077d2e462d8d &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table  border=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; width=600&amp;gt; &amp;lt;!----If something has an issue, include a link to the svn ticket or forum post ----------&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#CCCC66&amp;quot;&amp;gt;[http://linuxmce.iptp.org/snapshots/LMCE-1204-20140311212428804.iso LMCE-1204-20140311212428804.iso] 12-Mar-2014 00:37&amp;lt;/td&amp;gt;    &amp;lt;!----Enter ISO Name with link!----------&amp;gt;&lt;br /&gt;
     &amp;lt;td&amp;gt;VM&amp;lt;/td&amp;gt;&lt;br /&gt;
     &amp;lt;td&amp;gt;Hardware&amp;lt;/td&amp;gt;&lt;br /&gt;
      &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td width=&amp;quot;145&amp;quot; bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Audio&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td width=&amp;quot;16&amp;quot; bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt; &amp;lt;!----Enter VM Status NOTE: bg color either red or green or grey----------&amp;gt;&lt;br /&gt;
    &amp;lt;td width=&amp;quot;17&amp;quot; bgcolor=&amp;quot;green&amp;quot;&amp;gt;&#039;&#039;&#039;PASS&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Video - Stored media / DVD Playback&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;green&amp;quot;&amp;gt;&#039;&#039;&#039;PASS&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Diskless MD creation&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;green&amp;quot;&amp;gt;&#039;&#039;&#039;PASS&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;MythTV&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;green&amp;quot;&amp;gt;&#039;&#039;&#039;PASS&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;VDR&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Online Services&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;green&amp;quot;&amp;gt;&#039;&#039;&#039;PASS&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Automation - Insteon&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Automation - X10&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Automation - Zwave&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Networking&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;greY&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;green&amp;quot;&amp;gt;&#039;&#039;&#039;PASS&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Security&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Telecom&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===HW Install Remarks===&lt;br /&gt;
-&lt;br /&gt;
&lt;br /&gt;
vesa graphics does not show bootsplash, instead displaying backgrounding errors. These errors occur on every Ubuntu/Kubuntu disk, you typically do not see them because their bootsplash is different than ours, so please disregard them. L3mce&lt;br /&gt;
&lt;br /&gt;
No need to run DisklessCreateTBZ.sh.&lt;br /&gt;
&lt;br /&gt;
Had slight issues on reboot to AVWIz with AMD HD GPU. Took a very long time to get there +- 45min but thereafter graphics working at least as well as 10.04.&lt;br /&gt;
&lt;br /&gt;
Also had a few issues on Zbox MD where there are quite a few requests to reload router. In addition, I saw messages appearing to install Denon AV receiver (which I don&#039;t have) and some other device which I don&#039;t have. They are not in the device tree, though.&lt;br /&gt;
&lt;br /&gt;
So far so good. 1 Core/Hybrid and 1 Zbox MD.&lt;br /&gt;
Hardware profile: [[User:Jamo|Jamo]]&lt;br /&gt;
&lt;br /&gt;
===Failed Installations===&lt;br /&gt;
LMCE-1204-20140226223128766.iso 26-Feb-2014 23:21 | &#039;&#039;&#039;FAIL&#039;&#039;&#039; Networking issues [http://forum.linuxmce.org/index.php?topic=13585.0]&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Previous succesfull installs===&lt;br /&gt;
[http://linuxmce.iptp.org/snapshots/LMCE-1204-20140302030428788.iso LMCE-1204-20140302030428788.iso]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Snapshot_overview&amp;diff=34872</id>
		<title>Snapshot overview</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Snapshot_overview&amp;diff=34872"/>
		<updated>2014-03-19T16:03:28Z</updated>

		<summary type="html">&lt;p&gt;Coley: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Software]][[Category: testing]][[Category: 1204]][[Category:LinuxMCE Releases]]&lt;br /&gt;
&lt;br /&gt;
This page will help users to pick a snapshot for testing or use. You can download from this page http://linuxmce.iptp.org/snapshots/. Not all snapshots work, so please choose ones below that are reported working.&lt;br /&gt;
You can find an overview of fixes and listed bugs here http://svn.linuxmce.org/trac.cgi/report/1?sort=type&amp;amp;asc=1&amp;amp;page=1. If you find unreported bugs please report them in the svn. This page is a work in progress but the information is valid.&lt;br /&gt;
&lt;br /&gt;
===Recommended Download===&lt;br /&gt;
[http://linuxmce.iptp.org/snapshots/LMCE-1204-20140311212428804.iso LMCE-1204-20140311212428804.iso]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039; MD5SUM: ff2870eacca552c492f9077d2e462d8d &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table  border=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; width=600&amp;gt; &amp;lt;!----If something has an issue, include a link to the svn ticket or forum post ----------&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#CCCC66&amp;quot;&amp;gt;[http://linuxmce.iptp.org/snapshots/LMCE-1204-20140311212428804.iso LMCE-1204-20140311212428804.iso] 12-Mar-2014 00:37&amp;lt;/td&amp;gt;    &amp;lt;!----Enter ISO Name with link!----------&amp;gt;&lt;br /&gt;
     &amp;lt;td&amp;gt;VM&amp;lt;/td&amp;gt;&lt;br /&gt;
     &amp;lt;td&amp;gt;Hardware&amp;lt;/td&amp;gt;&lt;br /&gt;
      &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td width=&amp;quot;145&amp;quot; bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Audio&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td width=&amp;quot;16&amp;quot; bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt; &amp;lt;!----Enter VM Status NOTE: bg color either red or green or grey----------&amp;gt;&lt;br /&gt;
    &amp;lt;td width=&amp;quot;17&amp;quot; bgcolor=&amp;quot;green&amp;quot;&amp;gt;&#039;&#039;&#039;PASS&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Video - Stored media / DVD Playback&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;green&amp;quot;&amp;gt;&#039;&#039;&#039;PASS&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Diskless MD creation&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;green&amp;quot;&amp;gt;&#039;&#039;&#039;PASS&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;MythTV&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;PASS&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;VDR&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Online Services&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;green&amp;quot;&amp;gt;&#039;&#039;&#039;PASS&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Automation - Insteon&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Automation - X10&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Automation - Zwave&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Networking&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;greY&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;green&amp;quot;&amp;gt;&#039;&#039;&#039;PASS&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Security&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Telecom&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===HW Install Remarks===&lt;br /&gt;
-&lt;br /&gt;
&lt;br /&gt;
vesa graphics does not show bootsplash, instead displaying backgrounding errors. These errors occur on every Ubuntu/Kubuntu disk, you typically do not see them because their bootsplash is different than ours, so please disregard them. L3mce&lt;br /&gt;
&lt;br /&gt;
No need to run DisklessCreateTBZ.sh.&lt;br /&gt;
&lt;br /&gt;
Had slight issues on reboot to AVWIz with AMD HD GPU. Took a very long time to get there +- 45min but thereafter graphics working at least as well as 10.04.&lt;br /&gt;
&lt;br /&gt;
Also had a few issues on Zbox MD where there are quite a few requests to reload router. In addition, I saw messages appearing to install Denon AV receiver (which I don&#039;t have) and some other device which I don&#039;t have. They are not in the device tree, though.&lt;br /&gt;
&lt;br /&gt;
So far so good. 1 Core/Hybrid and 1 Zbox MD.&lt;br /&gt;
Hardware profile: [[User:Jamo|Jamo]]&lt;br /&gt;
&lt;br /&gt;
===Failed Installations===&lt;br /&gt;
LMCE-1204-20140226223128766.iso 26-Feb-2014 23:21 | &#039;&#039;&#039;FAIL&#039;&#039;&#039; Networking issues [http://forum.linuxmce.org/index.php?topic=13585.0]&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Previous succesfull installs===&lt;br /&gt;
[http://linuxmce.iptp.org/snapshots/LMCE-1204-20140302030428788.iso LMCE-1204-20140302030428788.iso]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Coley&amp;diff=34868</id>
		<title>User:Coley</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Coley&amp;diff=34868"/>
		<updated>2014-03-18T17:35:17Z</updated>

		<summary type="html">&lt;p&gt;Coley: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:User Setups]]&lt;br /&gt;
&lt;br /&gt;
I may as well put some details on my set-up here. At the moment it is at the experimental stage, time invested now will be just that, beginning to get time to play with this in freshly renovated house.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Dedicated Core&#039;&#039;&#039;&lt;br /&gt;
  Recently upgraded to 10.04 alpha.&lt;br /&gt;
  Now on a [[HP ML115 G5]] micro tower server.&lt;br /&gt;
  This beastie has plenty of space - four Hard Drive bays. Added a PCI-E intel Gbit NIC. Added 1TB WD caviar SATA 7200rpm&lt;br /&gt;
  DVB-T freecom USB stick.&lt;br /&gt;
  (&#039;&#039;Tried this with previously working driver and it causes bad things to happen, lsusb freezes.&lt;br /&gt;
  Found newer version here [http://ubuntuforums.org/showpost.php?p=6098621&amp;amp;postcount=5 Intrepid pkg] yet to test...&#039;&#039;)&lt;br /&gt;
  2x[[DVBworld_HD-2104-USB-S2|DVBWorld]] DVB-S2 USB receivers.&lt;br /&gt;
  2x[[TP30|Topping TP30]] USB DACs fed by squeezeslaves for two audio zones.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Zwave&#039;&#039;&#039;&lt;br /&gt;
  Z-wave zcu201 controller - for now.&lt;br /&gt;
  3x Qees Reto plus inline dimmer&lt;br /&gt;
  1x Fibaro dimmer FGD211.&lt;br /&gt;
  1x Fibaro dual Relay FGS221.&lt;br /&gt;
  1x Aeon Minimote&lt;br /&gt;
  1x Z-wave.me Key chain controller.&lt;br /&gt;
  1x Everspring SP814 Motion detector&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;NAS&#039;&#039;&#039;&lt;br /&gt;
  Netgear Readynas NV+&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;MD&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
  Restarted on the [[ASUS M2N-VM]] HDMI mothorboard based Media director.&lt;br /&gt;
  Pxe booting and UI2 overlay in operation!&lt;br /&gt;
  No extras required so far - will update this with additions whenever needed.&lt;br /&gt;
  AMD 64 X2 4200+ processor, 1GB RAM, slot load slimline DVD.&lt;br /&gt;
&lt;br /&gt;
  Pegatron Cape7&lt;br /&gt;
  Pxe booting and UI2 overlay in operation!&lt;br /&gt;
  Phoenix Duet - similar to the [[Phoenix_Solo_USB|Phoenix solo]] but with built-in spkr, need to revert alsa drivers [http://forum.linuxmce.org/index.php?topic=10428.msg72593#msg72593 see this forum post] to get this going.&lt;br /&gt;
&lt;br /&gt;
  HP Laptop - n/w boot&lt;br /&gt;
&lt;br /&gt;
  3 x Squeezebox receivers for audio zones.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;TV&#039;&#039;&#039;&lt;br /&gt;
  Dell 19&amp;quot; LCD [[Dell_W1900|Dell W1900]]&lt;br /&gt;
  &#039;&#039;see note re audio in&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
  Pioneer PDPLX5090&lt;br /&gt;
  Controlled by Pegatron Cape7 MD, USBtoSerial converter.&lt;br /&gt;
  Works PnP in 10.04, AFAIK also in 8.10 but there were some issues with /dev/ttyUSB0 vs /dev/&amp;lt;dev id&amp;gt;&lt;br /&gt;
  &lt;br /&gt;
&#039;&#039;&#039;AV Receiver&#039;&#039;&#039;&lt;br /&gt;
  Denon AVR-2312&lt;br /&gt;
  &#039;&#039;Not controlled by MD yet. Serial template exists - what about LAN?&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Orbiters&#039;&#039;&#039;&lt;br /&gt;
  WebDT&lt;br /&gt;
  N95&lt;br /&gt;
  iPAQ&lt;br /&gt;
  N900&lt;br /&gt;
  iPhone&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Snapshot_overview&amp;diff=34833</id>
		<title>Snapshot overview</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Snapshot_overview&amp;diff=34833"/>
		<updated>2014-03-05T11:52:51Z</updated>

		<summary type="html">&lt;p&gt;Coley: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Software]][[Category: testing]][[Category: 1204]][[Category:LinuxMCE Releases]]&lt;br /&gt;
&lt;br /&gt;
This page will help users to pick a snapshot for testing or use. You can download from this page http://linuxmce.iptp.org/snapshots/. Not all snapshots work, so please choose ones below that are reported working.&lt;br /&gt;
You can find an overview of fixes and listed bugs here http://svn.linuxmce.org/trac.cgi/report/1?sort=type&amp;amp;asc=1&amp;amp;page=1. If you find unreported bugs please report them in the svn. This page is a work in progress but the information is valid.&lt;br /&gt;
&lt;br /&gt;
===Recommended Download===&lt;br /&gt;
&lt;br /&gt;
[http://linuxmce.iptp.org/snapshots/LMCE-1204-20140302030428788.iso LMCE-1204-20140302030428788.iso]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039; MD5SUM: 6d05fbecf2f414617512f758a0e5a995 &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table  border=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; width=600&amp;gt; &amp;lt;!----If something has an issue, include a link to the svn ticket or forum post ----------&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#CCCC66&amp;quot;&amp;gt;[http://linuxmce.iptp.org/snapshots/LMCE-1204-20140302030428788.iso LMCE-1204-20140302030428788.iso] 02-Mar-2014 04:40&amp;lt;/td&amp;gt;    &amp;lt;!----Enter ISO Name with link!----------&amp;gt;&lt;br /&gt;
     &amp;lt;td&amp;gt;VM&amp;lt;/td&amp;gt;&lt;br /&gt;
     &amp;lt;td&amp;gt;Hardware&amp;lt;/td&amp;gt;&lt;br /&gt;
      &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td width=&amp;quot;145&amp;quot; bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Audio&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td width=&amp;quot;16&amp;quot; bgcolor=&amp;quot;green&amp;quot;&amp;gt;&#039;&#039;&#039;PASS&#039;&#039;&#039;&amp;lt;/td&amp;gt; &amp;lt;!----Enter VM Status NOTE: bg color either red or green or grey----------&amp;gt;&lt;br /&gt;
    &amp;lt;td width=&amp;quot;17&amp;quot; bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;???&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Video - Stored media / DVD Playback&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;???&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Diskless MD creation&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;green&amp;quot;&amp;gt;&#039;&#039;&#039;PASS&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;???&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;MythTV&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;green&amp;quot;&amp;gt;&#039;&#039;&#039;PASS&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;VDR&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Online Services&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;green&amp;quot;&amp;gt;&#039;&#039;&#039;PASS&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;???&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Automation - Insteon&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Automation - X10&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Automation - Zwave&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Networking&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;green&amp;quot;&amp;gt;&#039;&#039;&#039;PASS&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;???&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Security&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Telecom&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===VM Install Remarks===&lt;br /&gt;
-&lt;br /&gt;
&lt;br /&gt;
vesa graphics will not show bootsplash, instead displaying backgrounding errors. These erros occur on every Ubuntu/Kubuntu disk, you typically do not see them because their bootsplash is different than ours, so please disregard them. L3mce&lt;br /&gt;
&lt;br /&gt;
After core install initial MD didn&#039;t create correctly - it could have been me being impatient either...&lt;br /&gt;
Re-ran DisklessCreateTBZ.sh on core and once completed newly added MD gets created successfully.&lt;br /&gt;
&lt;br /&gt;
MythTV loads - trying to check capture card atm.&lt;br /&gt;
===Failed Installations===&lt;br /&gt;
LMCE-1204-20140226223128766.iso 26-Feb-2014 23:21 | &#039;&#039;&#039;FAIL&#039;&#039;&#039; Networking issues [http://forum.linuxmce.org/index.php?topic=13585.0]&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Previous succesfull installs===&lt;br /&gt;
-&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Snapshot_overview&amp;diff=34832</id>
		<title>Snapshot overview</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Snapshot_overview&amp;diff=34832"/>
		<updated>2014-03-04T12:42:12Z</updated>

		<summary type="html">&lt;p&gt;Coley: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Software]][[Category: testing]][[Category: 1204]][[Category:LinuxMCE Releases]]&lt;br /&gt;
&lt;br /&gt;
This page will help users to pick a snapshot for testing or use. You can download from this page http://linuxmce.iptp.org/snapshots/. Not all snapshots work, so please choose ones below that are reported working.&lt;br /&gt;
You can find an overview of fixes and listed bugs here http://svn.linuxmce.org/trac.cgi/report/1?sort=type&amp;amp;asc=1&amp;amp;page=1. If you find unreported bugs please report them in the svn. This page is a work in progress but the information is valid.&lt;br /&gt;
&lt;br /&gt;
===Recommended Download===&lt;br /&gt;
&lt;br /&gt;
[http://linuxmce.iptp.org/snapshots/LMCE-1204-20140302030428788.iso LMCE-1204-20140302030428788.iso]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039; MD5SUM: 6d05fbecf2f414617512f758a0e5a995 &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table  border=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; width=600&amp;gt; &amp;lt;!----If something has an issue, include a link to the svn ticket or forum post ----------&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#CCCC66&amp;quot;&amp;gt;[http://linuxmce.iptp.org/snapshots/LMCE-1204-20140302030428788.iso LMCE-1204-20140302030428788.iso] 02-Mar-2014 04:40&amp;lt;/td&amp;gt;    &amp;lt;!----Enter ISO Name with link!----------&amp;gt;&lt;br /&gt;
     &amp;lt;td&amp;gt;VM&amp;lt;/td&amp;gt;&lt;br /&gt;
     &amp;lt;td&amp;gt;Hardware&amp;lt;/td&amp;gt;&lt;br /&gt;
      &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td width=&amp;quot;145&amp;quot; bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Audio&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td width=&amp;quot;16&amp;quot; bgcolor=&amp;quot;green&amp;quot;&amp;gt;&#039;&#039;&#039;PASS&#039;&#039;&#039;&amp;lt;/td&amp;gt; &amp;lt;!----Enter VM Status NOTE: bg color either red or green or grey----------&amp;gt;&lt;br /&gt;
    &amp;lt;td width=&amp;quot;17&amp;quot; bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;???&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Video - Stored media / DVD Playback&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;???&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Diskless MD creation&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;green&amp;quot;&amp;gt;&#039;&#039;&#039;PASS&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;???&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;MythTV&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;VDR&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Online Services&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;???&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Automation - Insteon&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Automation - X10&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Automation - Zwave&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Networking&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;green&amp;quot;&amp;gt;&#039;&#039;&#039;PASS&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;???&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Security&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Telecom&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===VM Install Remarks===&lt;br /&gt;
-&lt;br /&gt;
&lt;br /&gt;
vesa graphics will not show bootsplash, instead displaying backgrounding errors. These erros occur on every Ubuntu/Kubuntu disk, you typically do not see them because their bootsplash is different than ours, so please disregard them. L3mce&lt;br /&gt;
&lt;br /&gt;
After core install initial MD didn&#039;t create correctly - it could have been me being impatient either...&lt;br /&gt;
Re-ran DisklessCreateTBZ.sh on core and once completed newly added MD gets created successfully.&lt;br /&gt;
===Failed Installations===&lt;br /&gt;
LMCE-1204-20140226223128766.iso 26-Feb-2014 23:21 | &#039;&#039;&#039;FAIL&#039;&#039;&#039; Networking issues [http://forum.linuxmce.org/index.php?topic=13585.0]&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Previous succesfull installs===&lt;br /&gt;
-&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Snapshot_overview&amp;diff=34829</id>
		<title>Snapshot overview</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Snapshot_overview&amp;diff=34829"/>
		<updated>2014-03-03T14:47:48Z</updated>

		<summary type="html">&lt;p&gt;Coley: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Software]][[Category: testing]][[Category: 1204]][[Category:LinuxMCE Releases]]&lt;br /&gt;
&lt;br /&gt;
This page will help users to pick a snapshot for testing or use. You can download from this page http://linuxmce.iptp.org/snapshots/. Not all snapshots work, so please choose ones below that are reported working.&lt;br /&gt;
You can find an overview of fixes and listed bugs here http://svn.linuxmce.org/trac.cgi/report/1?sort=type&amp;amp;asc=1&amp;amp;page=1. If you find unreported bugs please report them in the svn. This page is a work in progress but the information is valid.&lt;br /&gt;
&lt;br /&gt;
===Recommended Download===&lt;br /&gt;
&lt;br /&gt;
[http://linuxmce.iptp.org/snapshots/LMCE-1204-20140302030428788.iso LMCE-1204-20140302030428788.iso]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039; MD5SUM: 6d05fbecf2f414617512f758a0e5a995 &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table  border=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; width=600&amp;gt; &amp;lt;!----If something has an issue, include a link to the svn ticket or forum post ----------&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#CCCC66&amp;quot;&amp;gt;[http://linuxmce.iptp.org/snapshots/LMCE-1204-20140302030428788.iso LMCE-1204-20140302030428788.iso] 02-Mar-2014 04:40&amp;lt;/td&amp;gt;    &amp;lt;!----Enter ISO Name with link!----------&amp;gt;&lt;br /&gt;
     &amp;lt;td&amp;gt;VM&amp;lt;/td&amp;gt;&lt;br /&gt;
     &amp;lt;td&amp;gt;Hardware&amp;lt;/td&amp;gt;&lt;br /&gt;
      &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td width=&amp;quot;145&amp;quot; bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Audio&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td width=&amp;quot;16&amp;quot; bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt; &amp;lt;!----Enter VM Status NOTE: bg color either red or green or grey----------&amp;gt;&lt;br /&gt;
    &amp;lt;td width=&amp;quot;17&amp;quot; bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;???&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Video - Stored media / DVD Playback&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;???&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Diskless MD creation&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;???&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;MythTV&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;VDR&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Online Services&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;???&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Automation - Insteon&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Automation - X10&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Automation - Zwave&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Networking&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;green&amp;quot;&amp;gt;&#039;&#039;&#039;PASS&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;???&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Security&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Telecom&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===VM Install Remarks===&lt;br /&gt;
-&lt;br /&gt;
&lt;br /&gt;
vesa graphics will not show bootsplash, instead displaying backgrounding errors. These erros occur on every Ubuntu/Kubuntu disk, you typically do not see them because their bootsplash is different than ours, so please disregard them. L3mce&lt;br /&gt;
&lt;br /&gt;
===Failed Installations===&lt;br /&gt;
LMCE-1204-20140226223128766.iso 26-Feb-2014 23:21 | &#039;&#039;&#039;FAIL&#039;&#039;&#039; Networking issues [http://forum.linuxmce.org/index.php?topic=13585.0]&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Previous succesfull installs===&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Snapshot_overview&amp;diff=34828</id>
		<title>Snapshot overview</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Snapshot_overview&amp;diff=34828"/>
		<updated>2014-03-03T14:41:51Z</updated>

		<summary type="html">&lt;p&gt;Coley: Updated to track 1204 snapshots&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Software]][[Category: testing]][[Category: 1004]]&lt;br /&gt;
&lt;br /&gt;
This page will help users to pick a snapshot for testing or use. You can download from this page http://linuxmce.iptp.org/snapshots/. Not all snapshots work, so please choose ones below that are reported working.&lt;br /&gt;
You can find an overview of fixes and listed bugs here http://svn.linuxmce.org/trac.cgi/report/1?sort=type&amp;amp;asc=1&amp;amp;page=1. If you find unreported bugs please report them in the svn. This page is a work in progress but the information is valid.&lt;br /&gt;
&lt;br /&gt;
===Recommended Download===&lt;br /&gt;
&lt;br /&gt;
[http://linuxmce.iptp.org/snapshots/LMCE-1204-20140302030428788.iso LMCE-1204-20140302030428788.iso]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039; MD5SUM: 6d05fbecf2f414617512f758a0e5a995 &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table  border=&amp;quot;1&amp;quot; align=&amp;quot;center&amp;quot; width=600&amp;gt; &amp;lt;!----If something has an issue, include a link to the svn ticket or forum post ----------&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#CCCC66&amp;quot;&amp;gt;[http://linuxmce.iptp.org/snapshots/LMCE-1204-20140302030428788.iso LMCE-1204-20140302030428788.iso] 02-Mar-2014 04:40&amp;lt;/td&amp;gt;    &amp;lt;!----Enter ISO Name with link!----------&amp;gt;&lt;br /&gt;
     &amp;lt;td&amp;gt;VM&amp;lt;/td&amp;gt;&lt;br /&gt;
     &amp;lt;td&amp;gt;Hardware&amp;lt;/td&amp;gt;&lt;br /&gt;
      &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td width=&amp;quot;145&amp;quot; bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Audio&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td width=&amp;quot;16&amp;quot; bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt; &amp;lt;!----Enter VM Status NOTE: bg color either red or green or grey----------&amp;gt;&lt;br /&gt;
    &amp;lt;td width=&amp;quot;17&amp;quot; bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;???&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Video - Stored media / DVD Playback&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;???&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Diskless MD creation&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;???&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;MythTV&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;VDR&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Online Services&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;???&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Automation - Insteon&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Automation - X10&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Automation - Zwave&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Networking&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;green&amp;quot;&amp;gt;&#039;&#039;&#039;PASS&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;???&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Security&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;#3399CC&amp;quot;&amp;gt;&#039;&#039;&#039;Telecom&#039;&#039;&#039;&amp;lt;/td&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter VM Status ----------&amp;gt;&lt;br /&gt;
    &amp;lt;td bgcolor=&amp;quot;grey&amp;quot;&amp;gt;&#039;&#039;&#039;????&#039;&#039;&#039;&amp;lt;/td&amp;gt;&amp;lt;!----Enter Hardware Status ----------&amp;gt;&lt;br /&gt;
  &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===VM Install Remarks===&lt;br /&gt;
-&lt;br /&gt;
&lt;br /&gt;
vesa graphics will not show bootsplash, instead displaying backgrounding errors. These erros occur on every Ubuntu/Kubuntu disk, you typically do not see them because their bootsplash is different than ours, so please disregard them. L3mce&lt;br /&gt;
&lt;br /&gt;
===Failed Installations===&lt;br /&gt;
LMCE-1204-20140226223128766.iso 26-Feb-2014 23:21 | &#039;&#039;&#039;FAIL&#039;&#039;&#039; Networking issues [http://forum.linuxmce.org/index.php?topic=13585.0]&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Previous succesfull installs===&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Joggler_as_Orbiter_with_Phone&amp;diff=34405</id>
		<title>Joggler as Orbiter with Phone</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Joggler_as_Orbiter_with_Phone&amp;diff=34405"/>
		<updated>2013-08-30T11:41:38Z</updated>

		<summary type="html">&lt;p&gt;Coley: Grant access before running script for updating available soundcards&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Joggler can also, with the addition of a USB sound card, be used as a SimplePhone extension, which allows you to:&lt;br /&gt;
&lt;br /&gt;
(This page is temporary, as a more automated mechanism for handling this will be created.)&lt;br /&gt;
&lt;br /&gt;
== Uses ==&lt;br /&gt;
&lt;br /&gt;
* Use the Joggler as a Phone&lt;br /&gt;
* Use it as an Intercom&lt;br /&gt;
* Utilize Speak in the House&lt;br /&gt;
* Utilize Follow Me for Telecom&lt;br /&gt;
&lt;br /&gt;
== You will need ==&lt;br /&gt;
&lt;br /&gt;
* An O2 Joggler or OpenPeak OpenFrame, set up as per the [[Joggler]] page.&lt;br /&gt;
* A USB microphone, preferrably one specialized for Phone usage, such as the [[Phoenix Audio Solo]], or [[Phoenix Audio Duet]]. I use the latter due to its built in speaker.&lt;br /&gt;
* To Make sure your DCE and Designer repositories are up to date, as per the [[How to use sqlCVS from web admin]] page.&lt;br /&gt;
&lt;br /&gt;
== Procedure ==&lt;br /&gt;
&lt;br /&gt;
This is a currently a manual procedure, which, will be refined and automated soon enough, but for those who want to do it:&lt;br /&gt;
&lt;br /&gt;
=== Set up a Joggler as Audio/Phone Device ===&lt;br /&gt;
&lt;br /&gt;
* Go to Advanced &amp;gt; Configuration &amp;gt; Devices&lt;br /&gt;
* Create Top Level Device. Give it a name like &amp;quot;Bedroom Joggler&amp;quot;&lt;br /&gt;
* Enter template #2266 - it should show Joggler as Audio/Phone, Press Pick Device Template.&lt;br /&gt;
&lt;br /&gt;
==== If you&#039;ve already created an orbiter for your Joggler ====&lt;br /&gt;
&lt;br /&gt;
* Select the Orbiter&lt;br /&gt;
* Scroll to the Controlled By field, it should be -Please Select- currently.&lt;br /&gt;
* Change this value to the device you created above. This will make the Orbiter a child of the Joggler template.&lt;br /&gt;
* Verify this has happened by looking at the device tree, and seeing your orbiter as a child.&lt;br /&gt;
&lt;br /&gt;
=== Set up the SimplePhone child to Orbiter ===&lt;br /&gt;
&lt;br /&gt;
* With the orbiter still selected, press Create Child Device&lt;br /&gt;
* Enter template #1759 - it should show Orbiter Embedded Phone, press Pick Device Template.&lt;br /&gt;
&lt;br /&gt;
Reload the router.&lt;br /&gt;
&lt;br /&gt;
=== Copy files to the device ===&lt;br /&gt;
&lt;br /&gt;
Open a shell on either your hybrid, or a media director, and use this basic command to copy each of the listed files below to the Joggler.&lt;br /&gt;
&lt;br /&gt;
 scp /usr/pluto/bin/[filename] joggler@www.xxx.yyy.zzz&lt;br /&gt;
&lt;br /&gt;
* Config_Ops.sh&lt;br /&gt;
* ListSerialPorts.sh&lt;br /&gt;
* ListSoundCards.sh&lt;br /&gt;
* LockUtils.sh&lt;br /&gt;
* pluto.func&lt;br /&gt;
* SimplePhone&lt;br /&gt;
* Spawn_Device.sh&lt;br /&gt;
* Spawn_Wrapper.sh&lt;br /&gt;
* SQL_Ops.sh&lt;br /&gt;
* Start_LocalDevices.sh&lt;br /&gt;
* TranslateRemoteSoundCard.sh&lt;br /&gt;
* TranslateSoundCard.sh&lt;br /&gt;
* UpdateAvailableSerialPorts.sh&lt;br /&gt;
* UpdateAvailableSoundCards.sh&lt;br /&gt;
* Utils.sh&lt;br /&gt;
&lt;br /&gt;
=== Install additional packages ===&lt;br /&gt;
&lt;br /&gt;
Use apt-get to install additional packages (FIXME: maybe there are more)&lt;br /&gt;
&lt;br /&gt;
 apt-get install screen mysql-client &lt;br /&gt;
&lt;br /&gt;
=== Update Startup Scripts ===&lt;br /&gt;
&lt;br /&gt;
==== /home/joggler/.xinitrc ====&lt;br /&gt;
&lt;br /&gt;
 export DISPLAY=:0.0&lt;br /&gt;
 xset +dpms&lt;br /&gt;
 xset dpms 300 300 300&lt;br /&gt;
 &lt;br /&gt;
 cat /dev/null &amp;gt;/usr/pluto/locks/pluto_spawned_local_devices.txt&lt;br /&gt;
 &lt;br /&gt;
 if [ -f /home/joggler/startSqueezeSlave.sh ]; then&lt;br /&gt;
 	/home/joggler/startSqueezeSlave.sh&amp;amp;&lt;br /&gt;
 fi&lt;br /&gt;
 &lt;br /&gt;
 if [ -f /home/joggler/startOrbiter.sh ]; then&lt;br /&gt;
 	/home/joggler/startOrbiter.sh&lt;br /&gt;
 else&lt;br /&gt;
 	xterm&lt;br /&gt;
 fi&lt;br /&gt;
&lt;br /&gt;
==== /home/joggler/startOrbiter.sh ====&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 &lt;br /&gt;
 . /usr/pluto/bin/Config_Ops.sh 2&amp;gt;/dev/null&lt;br /&gt;
 &lt;br /&gt;
 /usr/pluto/bin/UpdateAvailableSoundCards.sh&lt;br /&gt;
 &lt;br /&gt;
 xhost +&lt;br /&gt;
 &lt;br /&gt;
 /usr/pluto/bin/Start_LocalDevices.sh&lt;br /&gt;
 &lt;br /&gt;
 while [ &amp;quot;1&amp;quot; == &amp;quot;1&amp;quot; ] ; do &lt;br /&gt;
 	cd /usr/pluto/bin&lt;br /&gt;
 #	/usr/pluto/bin/Orbiter -r $DCERouter  -d $MyOrbiterID&lt;br /&gt;
 	sleep 15&lt;br /&gt;
 done&lt;br /&gt;
&lt;br /&gt;
==== /etc/pluto.conf ====&lt;br /&gt;
&lt;br /&gt;
 MySqlHost = 192.168.80.1&lt;br /&gt;
 MySqlUser = root&lt;br /&gt;
 MySqlPassword =&lt;br /&gt;
 MySqlDBName = pluto_main&lt;br /&gt;
 DCERouter = 192.168.80.1&lt;br /&gt;
 MySqlPort = 3306&lt;br /&gt;
 DCERouterPort = 3450&lt;br /&gt;
 PK_Device = 252 (replace with your #2266 device #)&lt;br /&gt;
 LogLevels=1,5,7,8&lt;br /&gt;
 Display = 0&lt;br /&gt;
&lt;br /&gt;
=== Allow Joggler to access pluto_main Database ===&lt;br /&gt;
&lt;br /&gt;
Launch mysql on your core, and do the following:&lt;br /&gt;
&lt;br /&gt;
 GRANT ALL PRIVILEGES ON pluto_main.* TO root@joggler.ip.address.here&lt;br /&gt;
&lt;br /&gt;
=== Run UpdateAvailableSoundCards.sh ===&lt;br /&gt;
&lt;br /&gt;
If you haven&#039;t attached your microphone, do so now. And run /usr/pluto/UpdateAvailableSoundCards.sh ... This will populate the device data for the sound cards, so that it can be selected in the Web Admin, on the Phones page.&lt;br /&gt;
&lt;br /&gt;
 /usr/pluto/bin/UpdateAvailableSoundCards.sh &lt;br /&gt;
&lt;br /&gt;
=== Select your Soundcard on the Phones Page ===&lt;br /&gt;
&lt;br /&gt;
Go to the Web admin, Wizard &amp;gt; Phones on the left pane, and find your new SimplePhone, it will be called Orbiter Embedded Phone. Set the room, and set the Sound Card to your microphone. Update. Reload Router.&lt;br /&gt;
&lt;br /&gt;
=== Reboot your Joggler ===&lt;br /&gt;
&lt;br /&gt;
Either by unplugging and plugging, or:&lt;br /&gt;
&lt;br /&gt;
 # sync&lt;br /&gt;
 # reboot&lt;br /&gt;
&lt;br /&gt;
Wait for Orbiter to re-appear.&lt;br /&gt;
&lt;br /&gt;
=== Verify SimplePhone is running ===&lt;br /&gt;
&lt;br /&gt;
SSH back into your joggler, and do a:&lt;br /&gt;
&lt;br /&gt;
 screen -ls&lt;br /&gt;
&lt;br /&gt;
You should see, two screen processes, one for Orbiter, and one for SimplePhone.&lt;br /&gt;
&lt;br /&gt;
 joggler@bedroom-joggler:~$ screen -ls&lt;br /&gt;
 There are screens on:&lt;br /&gt;
 	1071.SimplePhone_255	(27/08/13 18:45:03)	(Detached)&lt;br /&gt;
 	985.Orbiter-254	(27/08/13 18:44:56)	(Detached)&lt;br /&gt;
 2 Sockets in /var/run/screen/S-joggler.&lt;br /&gt;
 &lt;br /&gt;
 joggler@bedroom-joggler:~$ &lt;br /&gt;
&lt;br /&gt;
That&#039;s it, your new phone extension should be running! :)&lt;br /&gt;
&lt;br /&gt;
If you have any problems or questions, feel free to hit me up on forums or IRC. --[[User:Tschak909|Tschak909]] 20:09, 29 August 2013 (CEST)&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Floorplans&amp;diff=34294</id>
		<title>Floorplans</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Floorplans&amp;diff=34294"/>
		<updated>2013-07-25T16:37:08Z</updated>

		<summary type="html">&lt;p&gt;Coley: Removed outdated info.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:Floorplan.jpg|thumb|250px|Floorplan Wizard Page Admin Website]]&amp;lt;p&amp;gt;On the main menu on your Orbiters are floorplans for Lighting, Media, Climate, Security and Telecom.  These show the devices in your entire house at a glance and let you control them all individually, or as a group.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;You can also have many different floorplans.  For example, if you have a large house, it might be easier to break the floorplan into a &amp;quot;North&amp;quot; and &amp;quot;South&amp;quot;.  Or another floorplan for the grounds.  The floorplans are simply bitmap graphics that you create.  &amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Choose the &#039;Add another floorplan&#039; link to add a floorplan. You will need to give the floorplan a name, like &amp;quot;First Floor&amp;quot;, &amp;quot;Second Floor&amp;quot;, &amp;quot;Gardens&amp;quot;, etc.  Then you will specify where the bitmap file is on your local pc, or choose browse to find it.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Then use the left pull-down to pick a floorplan, and the right pull-down to pick the type of device.  If you choose &amp;quot;2nd Floor&amp;quot; and &amp;quot;Lighting&amp;quot;, for example, the wizard will show the floorplan called &amp;quot;2nd Floor&amp;quot; and a list of all the lighting devices in your home.  Then you can drag the device from the list on the left and drop it on the floorplan.  Move devices using drag and drop.  If you want to remove a device from the floorplan just drag it and drop it off the floorplan.  Position whatever devices you want to appear on that floorplan, and do not worry about the rest.  For example, you may want to put your outside lights on the &amp;quot;Gardens&amp;quot; floorplan, and your first floor lights on the &amp;quot;First floor&amp;quot; floorplan.  However, LinuxMCE lets you position any device anywhere without restriction.  If you do not put a device on a particular floorplan, then you will not be able to control that device from that floorplan&#039;s interactive map.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;When you touch the &amp;quot;floorplan&amp;quot; button on the Orbiter (the buttons in the left column) you will see your floorplan with little icons for all the devices.  Which icons appear are based on your selection on the device page.  For example on the &amp;quot;Wizard/Devices/Lighting&amp;quot; page you can specify for each light if it&#039;s a chandelier, ceiling light, accent light, etc., and that will determine which icon is drawn on the floorplan.  Refer to the [[Orbiter User&#039;s manual]] for instructions on using the floorplans.&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Floorplan Assistance==&lt;br /&gt;
You can request assistance from the community, or from the two companies listed below.&lt;br /&gt;
&amp;lt;br&amp;gt;For the UK contact Convergent Home Technologies&lt;br /&gt;
&amp;lt;br&amp;gt;For Germany contact DE Centersonic&lt;br /&gt;
&lt;br /&gt;
==Recommended Floorplan Size==&lt;br /&gt;
*Make them roughly square around 1200 x 1200 px--it can be smaller but then OrbiterGen will have to stretch them for high-res displays and they may not look as good. &lt;br /&gt;
*Save as PNG.&lt;br /&gt;
*See [[Control_lights_or_climate_with_a_floorplan]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: Admin Website]]&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Floorplan_texts&amp;diff=34293</id>
		<title>Floorplan texts</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Floorplan_texts&amp;diff=34293"/>
		<updated>2013-07-25T16:34:08Z</updated>

		<summary type="html">&lt;p&gt;Coley: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Development]]&lt;br /&gt;
[[Category: Programmer&#039;s Guide]]&lt;br /&gt;
== Floorplan Texts ==&lt;br /&gt;
Currently, there is a bug in the display of floorplan texts for mapIcons (the small icons you can drag and drop on your floorplan to control devices)&lt;br /&gt;
&lt;br /&gt;
Here is some documentation on the bug:&lt;br /&gt;
* The text location set up in HADesigner is not respected when the text is rendered. Text is always rendered at the Upper Left-Hand Corner (ULX) of the parent icon.&lt;br /&gt;
* The text bounding box set up in HADesigner is not respected either when test is rendered. Text always starts at the ULX of the parent icon, and wraps with the Icon&#039;s image width.&lt;br /&gt;
&lt;br /&gt;
Floorplans icon texts can be unreadable currently, because the text is black - and sometimes the icon is black - making the text unreadable. This bug prevents us from moving the text either to the side, or above or below the icon where it would be readable (and have a cleaner layout). This bug was found because I was trying to move the icon texts BELOW the icons for a cleaner, more readable floorplan display.&lt;br /&gt;
&lt;br /&gt;
In my examples, I am using the java-base QuickDesigner - but this is irrelevant, as I have verified the same behavior in HADesigner. I will be showing modifications to the Thermostat floorplan icon to illustrate the bugs.&lt;br /&gt;
&lt;br /&gt;
First, this screenshot shows the actual floorplan thermostat icon. You can see that the actual image includes a blank area to the right for the text to fit (NOTE: Need to find out if a text&#039;s bounding box can be OUTSIDE of the icon image)&lt;br /&gt;
&lt;br /&gt;
[[Image:preview_original_nothinghighlighted.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here is a screenshot of the stock location of the text&#039;s bounding box (highlighted in pink). Text should ONLY be displayed in this bounding box (note that the bounding box is TO THE RIGHT of the thermostat icon. This is where the text should appear!)&lt;br /&gt;
&lt;br /&gt;
[[Image:preview_original.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here is a screenshot of the page in Designer used to set the size of the bounding box. You can see that originally, it has an offset of 100 (to the right) and a width of 254.&lt;br /&gt;
&lt;br /&gt;
[[Image:texts_original.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here is a screenshot of how it appears on the orbiter. Notice that the text is not limited to the bounding box, and starts at the ULX of the icon. Both the location and the bounding box that was set up in Designer is being ignored!&lt;br /&gt;
&lt;br /&gt;
[[Image:result_original.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;First Modification - Making the bounding box wider&#039;&#039;&#039;&lt;br /&gt;
I used Designer to make the bounding box of the text about twice as wide (so that the text would not wrap, and to see if text can extend beyond the dimensions of the parent image).&lt;br /&gt;
&lt;br /&gt;
As you can see, I modified the width of the bounding box to be 512 - about twice as wide as it originally was!&lt;br /&gt;
&lt;br /&gt;
[[Image:texts_modified.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As would be expected, the preview shows us that we do indeed have a much wider bounding box:&lt;br /&gt;
&lt;br /&gt;
[[Image:preview_modified.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Now, you would expect that with such a wide bounding box there would be plenty of room for the text, and it would not have to wrap to a second line. But as you can see, how it appears in the orbiter:&lt;br /&gt;
&lt;br /&gt;
[[Image:result_modified.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Conclusions from this first round of modifications:&lt;br /&gt;
* The bounding box&#039;s offset from the parent icon is not preserved and indeed text rendering is always at the ULX of the parent icon.&lt;br /&gt;
* I still can&#039;t tell if it should be possible to have a text&#039;s bounding box outside of the parent image. If the text didn&#039;t wrap like expected, it would have proved that text could exist outside of the parent icon&#039;s dimensions.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Another modification - making the bounding box much narrower&#039;&#039;&#039;&lt;br /&gt;
In this test, i used designer to make the bounding box much narrower that it was originally. The reason for this test is to see if the bounding box is considered at all for wrapping, or if text wrapping is based on consideration of the parent icon&#039;s width.  &lt;br /&gt;
&lt;br /&gt;
For this test, I made the bounding box width=125 (about half of the original value)&lt;br /&gt;
&lt;br /&gt;
[[Image:texts_small.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You can see from the preview below, that the new bounding box area is much narrower. &lt;br /&gt;
&lt;br /&gt;
[[Image:small_preview.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
I would have expected the text to wrap to at least 3 lines because the bounding box is so narrow. However, as you can see from the image below, the result has not changed at all, and the text still starts at the ULX of the parent icon, and wraps to the parent icon&#039;s with.&lt;br /&gt;
&lt;br /&gt;
[[Image:small_result.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Conclusions from this round of modifications:&lt;br /&gt;
* It is now apparent that the bounding box set up in Designer is not respected at all, and instead, the text is always started at the parent icon&#039;s ULX, and wraps to the width of the image&lt;br /&gt;
* I would imagine, that if we were to fix this bug, then text should be able to exist OUTSIDE of the parent icon&#039;s dimensions. To do this, the starting position of the text should be equal to the parent icon&#039;s ULX + the X and Y of the text (these are offsets). Also, for wrapping purposes, the texts width and height properties shoudl be added to the texts starting position.  It would appear that this was never even implemented in the orbiter code.&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Coley&amp;diff=33948</id>
		<title>User:Coley</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Coley&amp;diff=33948"/>
		<updated>2013-03-14T11:49:52Z</updated>

		<summary type="html">&lt;p&gt;Coley: more zwave devices&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:User Setups]]&lt;br /&gt;
&lt;br /&gt;
I may as well put some details on my set-up here. At the moment it is at the experimental stage, time invested now will be just that, beginning to get time to play with this in freshly renovated house.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Dedicated Core&#039;&#039;&#039;&lt;br /&gt;
  Recently upgraded to 10.04 alpha.&lt;br /&gt;
  Now on a [[HP ML115 G5]] micro tower server.&lt;br /&gt;
  This beastie has plenty of space - four Hard Drive bays. Added a PCI-E intel Gbit NIC. Added 1TB WD caviar SATA 7200rpm&lt;br /&gt;
  DVB-T freecom USB stick.&lt;br /&gt;
  (&#039;&#039;Tried this with previously working driver and it causes bad things to happen, lsusb freezes.&lt;br /&gt;
  Found newer version here [http://ubuntuforums.org/showpost.php?p=6098621&amp;amp;postcount=5 Intrepid pkg] yet to test...&#039;&#039;)&lt;br /&gt;
  2x[[DVBworld_HD-2104-USB-S2|DVBWorld]] DVB-S2 USB receivers.&lt;br /&gt;
  2x[[TP30|Topping TP30]] USB DACs fed by squeezeslaves for two audio zones.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Zwave&#039;&#039;&#039;&lt;br /&gt;
  Z-wave zcu201 controller - for now.&lt;br /&gt;
  2x Qees Reto plus inline dimmer&lt;br /&gt;
  1x Fibaro dimmer FGD211.&lt;br /&gt;
  1x Fibaro dual Relay FGS221.&lt;br /&gt;
  1x Aeon Minimote&lt;br /&gt;
  1x Z-wave.me Key chain controller.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;NAS&#039;&#039;&#039;&lt;br /&gt;
  Netgear Readynas NV+&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;MD&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
  Restarted on the [[ASUS M2N-VM]] HDMI mothorboard based Media director.&lt;br /&gt;
  Pxe booting and UI2 overlay in operation!&lt;br /&gt;
  No extras required so far - will update this with additions whenever needed.&lt;br /&gt;
  AMD 64 X2 4200+ processor, 1GB RAM, slot load slimline DVD.&lt;br /&gt;
&lt;br /&gt;
  Pegatron Cape7&lt;br /&gt;
  Pxe booting and UI2 overlay in operation!&lt;br /&gt;
  Phoenix Duet - similar to the [[Phoenix_Solo_USB|Phoenix solo]] but with built-in spkr, need to revert alsa drivers [http://forum.linuxmce.org/index.php?topic=10428.msg72593#msg72593 see this forum post] to get this going.&lt;br /&gt;
&lt;br /&gt;
  HP Laptop - n/w boot&lt;br /&gt;
&lt;br /&gt;
  3 x Squeezebox receivers for audio zones.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;TV&#039;&#039;&#039;&lt;br /&gt;
  Dell 19&amp;quot; LCD [[Dell_W1900|Dell W1900]]&lt;br /&gt;
  &#039;&#039;see note re audio in&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
  Pioneer PDPLX5090&lt;br /&gt;
  Controlled by Pegatron Cape7 MD, USBtoSerial converter.&lt;br /&gt;
  Works PnP in 10.04, AFAIK also in 8.10 but there were some issues with /dev/ttyUSB0 vs /dev/&amp;lt;dev id&amp;gt;&lt;br /&gt;
  &lt;br /&gt;
&#039;&#039;&#039;AV Receiver&#039;&#039;&#039;&lt;br /&gt;
  Denon AVR-2312&lt;br /&gt;
  &#039;&#039;Not controlled by MD yet. Serial template exists - what about LAN?&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Orbiters&#039;&#039;&#039;&lt;br /&gt;
  WebDT&lt;br /&gt;
  N95&lt;br /&gt;
  iPAQ&lt;br /&gt;
  N900&lt;br /&gt;
  iPhone&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=User:Coley&amp;diff=33936</id>
		<title>User:Coley</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=User:Coley&amp;diff=33936"/>
		<updated>2013-03-12T12:04:24Z</updated>

		<summary type="html">&lt;p&gt;Coley: Added sep section for ZWave&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:User Setups]]&lt;br /&gt;
&lt;br /&gt;
I may as well put some details on my set-up here. At the moment it is at the experimental stage, time invested now will be just that, beginning to get time to play with this in freshly renovated house.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Dedicated Core&#039;&#039;&#039;&lt;br /&gt;
  Recently upgraded to 10.04 alpha.&lt;br /&gt;
  Now on a [[HP ML115 G5]] micro tower server.&lt;br /&gt;
  This beastie has plenty of space - four Hard Drive bays. Added a PCI-E intel Gbit NIC. Added 1TB WD caviar SATA 7200rpm&lt;br /&gt;
  DVB-T freecom USB stick.&lt;br /&gt;
  (&#039;&#039;Tried this with previously working driver and it causes bad things to happen, lsusb freezes.&lt;br /&gt;
  Found newer version here [http://ubuntuforums.org/showpost.php?p=6098621&amp;amp;postcount=5 Intrepid pkg] yet to test...&#039;&#039;)&lt;br /&gt;
  2x[[DVBworld_HD-2104-USB-S2|DVBWorld]] DVB-S2 USB receivers.&lt;br /&gt;
  2x[[TP30|Topping TP30]] USB DACs fed by squeezeslaves for two audio zones.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Zwave&#039;&#039;&#039;&lt;br /&gt;
  Z-wave zcu201 controller - for now.&lt;br /&gt;
  2x Qees Reto plus inline dimmer&lt;br /&gt;
  1x Fibaro dimmer.&lt;br /&gt;
  1x Fibaro dual Relay.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;NAS&#039;&#039;&#039;&lt;br /&gt;
  Netgear Readynas NV+&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;MD&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
  Restarted on the [[ASUS M2N-VM]] HDMI mothorboard based Media director.&lt;br /&gt;
  Pxe booting and UI2 overlay in operation!&lt;br /&gt;
  No extras required so far - will update this with additions whenever needed.&lt;br /&gt;
  AMD 64 X2 4200+ processor, 1GB RAM, slot load slimline DVD.&lt;br /&gt;
&lt;br /&gt;
  Pegatron Cape7&lt;br /&gt;
  Pxe booting and UI2 overlay in operation!&lt;br /&gt;
  Phoenix Duet - similar to the [[Phoenix_Solo_USB|Phoenix solo]] but with built-in spkr, need to revert alsa drivers [http://forum.linuxmce.org/index.php?topic=10428.msg72593#msg72593 see this forum post] to get this going.&lt;br /&gt;
&lt;br /&gt;
  HP Laptop - n/w boot&lt;br /&gt;
&lt;br /&gt;
  3 x Squeezebox receivers for audio zones.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;TV&#039;&#039;&#039;&lt;br /&gt;
  Dell 19&amp;quot; LCD [[Dell_W1900|Dell W1900]]&lt;br /&gt;
  &#039;&#039;see note re audio in&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
  Pioneer PDPLX5090&lt;br /&gt;
  Controlled by Pegatron Cape7 MD, USBtoSerial converter.&lt;br /&gt;
  Works PnP in 10.04, AFAIK also in 8.10 but there were some issues with /dev/ttyUSB0 vs /dev/&amp;lt;dev id&amp;gt;&lt;br /&gt;
  &lt;br /&gt;
&#039;&#039;&#039;AV Receiver&#039;&#039;&#039;&lt;br /&gt;
  Denon AVR-2312&lt;br /&gt;
  &#039;&#039;Not controlled by MD yet. Serial template exists - what about LAN?&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Orbiters&#039;&#039;&#039;&lt;br /&gt;
  WebDT&lt;br /&gt;
  N95&lt;br /&gt;
  iPAQ&lt;br /&gt;
  N900&lt;br /&gt;
  iPhone&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=32601</id>
		<title>RaspberryPi qOrbiter</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=32601"/>
		<updated>2012-10-05T10:20:03Z</updated>

		<summary type="html">&lt;p&gt;Coley: minor status update&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Development]]&lt;br /&gt;
==Device Specification==&lt;br /&gt;
-The Raspberry Pi is an ARM based computer the size of a credit card.  700Mhz, 256MB RAM, Ethernet, 2xUSB, GPIO&lt;br /&gt;
&lt;br /&gt;
-256MB of RAM is insufficient to build lmce.  MakeRelease and MakeRelease_PrepFiles both fail with out of memory errors due to the limited memory available on the RPi.&lt;br /&gt;
-Cross-compiling will be required.  More notes to follow.&lt;br /&gt;
==Debian Chroot Environment==&lt;br /&gt;
One approach is to set up a debian chroot environment, and use qemu with pass though emulation.&lt;br /&gt;
See http://wiki.debian.org/EmDebian/CrossDebootstrap#QEMU.2BAC8-debootstrap_approach&lt;br /&gt;
===Specifically for the Pi with raspbian image===&lt;br /&gt;
&#039;&#039;sudo needed for all of these commands&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Install some necessaries&lt;br /&gt;
 # apt-get install binfmt-support qemu qemu-user-static debootstrap&lt;br /&gt;
&lt;br /&gt;
Next set up the chroot env, create your directory, calling it what you like, if it doesn&#039;t exist.&lt;br /&gt;
 # mkdir raspbian_armhf_wheezy&lt;br /&gt;
&lt;br /&gt;
Bootstrap your new environment&lt;br /&gt;
 # qemu-debootstrap --arch armhf wheezy raspbian_armhf_wheezy http://archive.raspbian.org/raspbian&lt;br /&gt;
&lt;br /&gt;
Mount /proc and friends&lt;br /&gt;
 # mount -t proc proc raspbian_armhf_wheezy/proc&lt;br /&gt;
 # mount -t sysfs sysfs raspbian_armhf_wheezy/sys&lt;br /&gt;
 # mount -o bind /dev raspbian_armhf_wheezy/dev&lt;br /&gt;
&lt;br /&gt;
Not necessary, but you can also mount your existing src directory, if you have one, into your new chroot env.&lt;br /&gt;
 # mount --bind $HOME/path/to/my/src raspbian_armhf_wheezy/home/&amp;lt;user&amp;gt;/lmce/src&lt;br /&gt;
&lt;br /&gt;
Now you are ready to chroot into your new env and get going&lt;br /&gt;
 # LC_ALL=C chroot raspbian_armhf_wheezy&lt;br /&gt;
&lt;br /&gt;
Use &#039;&#039;apt-get update&#039;&#039; and &#039;&#039;apt-get install &amp;lt;pkg&amp;gt;&#039;&#039; to install needed packages in your chrooted env.&lt;br /&gt;
&lt;br /&gt;
==Cross Compilation setup==&lt;br /&gt;
Initially this section will have information specific to getting Qt on Pi going. Its pre-packaged and fairly easy to install.&lt;br /&gt;
&lt;br /&gt;
At the time of writing Qt on Pi tarball is at version 0.2.&lt;br /&gt;
Get the tarball here http://www.raspberrypi.org/downloads at the bottom of the page. This has a premade SD image plus the toolchain and sysroot install required for cross compilation.&lt;br /&gt;
&lt;br /&gt;
===If you are about to install this on your current machine with a working Qt development environment DON&#039;T===&lt;br /&gt;
You will need to either set up a VM or a chroot environment as the qt5 shipped with this image isn&#039;t setup to install alongside an x86 install. They plan on having these play nice in future releases.&lt;br /&gt;
&lt;br /&gt;
==Qt5, Toolchain and sysroot install==&lt;br /&gt;
This is documented on the QtonPi wiki but basically after you have downloaded the qtonpi tarball extract the three files within.&lt;br /&gt;
Then as root extract [opt-qt5-current.tar.bz2] and [toolchain-and-sysroot-armv5tel.tar.bz2] &lt;br /&gt;
 $ cd /&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/opt-qt5-current.tar.bz2&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/toolchain-and-sysroot-armv5tel.tar.bz2&lt;br /&gt;
&lt;br /&gt;
===Qt creator===&lt;br /&gt;
The tarball comes with a recent version of qtcreator, but since then qt2.5 RC has come out, Should be safe enough to use that instead. Just install that by executing the .bin installer. &#039;&#039;Hold that thought, qt2.5 creator RC doesn&#039;t have the deploy steps set up&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Within Qt creator you need to point it at your cross tool chain compiler+debugger:&lt;br /&gt;
#Tools-&amp;gt;Options-&amp;gt;Build&amp;amp;Run then Tool Chains&lt;br /&gt;
#then select add, in the drop-down pick GCC&lt;br /&gt;
#Select GCC and browse for compiler to&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gcc&lt;br /&gt;
and for the debugger&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gdb&lt;br /&gt;
Save these selections by clicking Apply and OK&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi Setup==&lt;br /&gt;
===Virtual using qemu===&lt;br /&gt;
As I don&#039;t have a rpi yet I used qemu to do some initial testing.&lt;br /&gt;
My setup was a 12.04 VM.&lt;br /&gt;
You can either install qemu&lt;br /&gt;
 sudo apt-get install qemu-system&lt;br /&gt;
Or you can build qemu from git. You only need to do this if the qemu on your distro doesn&#039;t support the Broadcom SOC (ARM1176 core) on the Pi.&lt;br /&gt;
In order to boot your image you will need a suitable kernel for your emulator, there is one available here http://dl.dropbox.com/u/45842273/zImage_3.1.9 &lt;br /&gt;
Boot your virtual Pi &lt;br /&gt;
 qemu-system-arm -kernel kernel-qemu -cpu arm1176 -m 256 -M versatilepb -no-reboot -serial stdio -append &amp;quot;root=/dev/sda2 rw panic=1&amp;quot; qtonpi-sdcard-0.2.img -redir tcp:5022::22&lt;br /&gt;
&lt;br /&gt;
add&lt;br /&gt;
 console=ttyAMA0&lt;br /&gt;
to the -append param to have the boot console re-directed to the terminal.&lt;br /&gt;
&lt;br /&gt;
the -redir tcp:5022::22 redirects port 22 (ssh) on the virtual Pi to port 5022 on the host enabling you to ssh in.&lt;br /&gt;
 ssh pi@localhost -p5022&lt;br /&gt;
===Raspberry Pi Setup===&lt;br /&gt;
I used the image I was using above and wrote it to an SD card.&#039;&#039;If you are on windows make sure your machine can handle larger cards&#039;&#039;&lt;br /&gt;
By default the qtonpi release doesn&#039;t have the network if enabled. On each boot you can run&lt;br /&gt;
 ifup eth0&lt;br /&gt;
or&lt;br /&gt;
 dhclient eth0&lt;br /&gt;
or&lt;br /&gt;
 just edit /etc/sysconfig/network-scripts/ifcfg-eth0 and set the ONBOOT option equal to YES and be done with it.&lt;br /&gt;
&lt;br /&gt;
Also you need to set the time and date after each boot - no RTC on the rPi&lt;br /&gt;
&lt;br /&gt;
==Code Changes==&lt;br /&gt;
According to the current Qt Documentation adding&lt;br /&gt;
 greaterThan(QT_MAJOR_VERSION, 4) {&lt;br /&gt;
        QT += widgets&lt;br /&gt;
        QT += quick1&lt;br /&gt;
    } else {&lt;br /&gt;
        QT += declarative&lt;br /&gt;
    }&lt;br /&gt;
to the pro file loads the correct modules for both Qt4/Qt5.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;04/07/2012&#039;&#039; - see ticket [http://svn.linuxmce.org/trac.cgi/ticket/1497 trac #1497] code checked into svn.&lt;br /&gt;
&lt;br /&gt;
===&amp;quot;Useful&amp;quot; Qt links===&lt;br /&gt;
http://qt-project.org/wiki/Transition_from_Qt_4.x_to_Qt5&lt;br /&gt;
&lt;br /&gt;
https://qt-project.org/wiki/New_Signal_Slot_Syntax&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/Qt-5Features&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/QML1-vs-QML2&lt;br /&gt;
&lt;br /&gt;
A recent but good addition http://doc-snapshot.qt-project.org/5.0/qtquick-porting-qt5.html#porting-c-code&lt;br /&gt;
&lt;br /&gt;
I don&#039;t know whether these apply to how Qt5 will be when it is released, but they don&#039;t completely correspond to it in its current state, so don&#039;t believe all you read.&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi distros==&lt;br /&gt;
Looking at http://elinux.org/RPi_Distributions there are quite a few to choose from.&lt;br /&gt;
&lt;br /&gt;
Which is the best fit? I don&#039;t know.&lt;br /&gt;
&lt;br /&gt;
I&#039;m starting with QtonPi but I don&#039;t know if a full fedora release is necessary.&lt;br /&gt;
&#039;&#039;This is actually a trimmed down fedora release no X, graphics written direct to fb&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Mer/Meego might be a good fit too.&lt;br /&gt;
&lt;br /&gt;
=qOrbiter on Pi=&lt;br /&gt;
==QtonPi 0.2 image==&lt;br /&gt;
trimmed down fedora remix with qt5 pre-installed, no gui.&lt;br /&gt;
====Status====&lt;br /&gt;
&#039;&#039;28/05/2012&#039;&#039; - Unfortunately I have not been able to get my compiled qOrbiter to run on my virtual setup.&lt;br /&gt;
Depending on the combination of kernel I use and/or SD image I either get an illegal instruction or and error creating a vchiq instance.&lt;br /&gt;
&lt;br /&gt;
And given that the vchiq lib stuff is to do with the GPU, which is initialised in firmware, this may be a bit of an impass until I get actual hardware.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;30/05/2012&#039;&#039; - Have just received my rPi and my previously compiled qOrbiter starts and gets past the vchiq/illegal instruction I had.&lt;br /&gt;
I have other issues before I get it going but all going in the right direction.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;02/06/2012&#039;&#039; - qOrbiter splash screen loads, communicates with dcerouter, gets config - then boom my network dies. I don&#039;t know if its rPi specific or some porting issue with qOrbiter. I see &#039;&#039;smsc95xx 1-1.1:1.0: eth0: kevent 2 may have been dropped&#039;&#039; scroll past me. My ssh connection dies as a result so I need to be logged in on the rPi. Needs more investigation...&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;06/06/2012&#039;&#039; - got past n/w problem, now home screen loads. Also had to disable qml screen saver. The shader effect component is supposed to be available via QtQuick 2.0 and not need the labs plugin, but this appears not to be the case. It is likely it is just not in the snapshot yet.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;08/06/2012&#039;&#039; - It seems there is no mouse support in the current 0.2 qtonpi SD image. This is a deal breaker until 0.3 image is released. Mouse support has been checked into git so is available if we roll our own qt5.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;28/08/2012&#039;&#039; - I don&#039;t think there will be an update for this - so am going to consider it parked.&lt;br /&gt;
&lt;br /&gt;
==Next image - Debian Wheezy==&lt;br /&gt;
Investigating a debian wheezy port at the moment - should eek out a bit more speed using hardfp. There are qt50-snapshots available for the target. May need to set up a separate toolchain.&lt;br /&gt;
===Status===&lt;br /&gt;
&#039;&#039;11/06/2012&#039;&#039; - existing qOrbiter won&#039;t run on target, need to link against newer qt5 sysroot on host.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;19/06/2012&#039;&#039; - have rebuilt and linked qOrbiter against qt5 from git. Up and running again on my Raspberry Pi. The default CPU/GPU split of 192/64 allows qOrbiter to run, lower one - 244/32 gives an error creating the display surface. Will bump up split to 128/128 if I get display issues.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;22/06/2012&#039;&#039; - as I thought, I had to move the split to 128/128 and now I get no GL memory errors and the background effects work on the home screen. I need to find out why switching threads away from the qml engine is failing.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;28/08/2012&#039;&#039; - Using the Raspbian image - (hardfp debian wheezy). Qt5 snapshots are being rolled for the target so apt can be used to install on Pi. In process of rolling qmake and friends for host to match. Next step build qOrbiter again.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;04/10/2012&#039;&#039; - Using the latest (Sept) Raspbian image - (hardfp debian wheezy). Qt5 snapshots were being rolled for the target so apt can be used to install on Pi, this seems to be in limbo at the moment, so may install version I&#039;ve just compiled. Have just built qmake and friends for host to match.&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31940</id>
		<title>RaspberryPi qOrbiter</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31940"/>
		<updated>2012-08-28T11:35:55Z</updated>

		<summary type="html">&lt;p&gt;Coley: parking investigation on this one.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Development]]&lt;br /&gt;
==Device Specification==&lt;br /&gt;
-The Raspberry Pi is an ARM based computer the size of a credit card.  700Mhz, 256MB RAM, Ethernet, 2xUSB, GPIO&lt;br /&gt;
&lt;br /&gt;
-256MB of RAM is insufficient to build lmce.  MakeRelease and MakeRelease_PrepFiles both fail with out of memory errors due to the limited memory available on the RPi.&lt;br /&gt;
-Cross-compiling will be required.  More notes to follow.&lt;br /&gt;
==Debian Chroot Environment==&lt;br /&gt;
One approach is to set up a debian chroot environment, and use qemu with pass though emulation.&lt;br /&gt;
See http://wiki.debian.org/EmDebian/CrossDebootstrap#QEMU.2BAC8-debootstrap_approach&lt;br /&gt;
===Specifically for the Pi with raspbian image===&lt;br /&gt;
&#039;&#039;sudo needed for all of these commands&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Install some necessaries&lt;br /&gt;
 # apt-get install binfmt-support qemu qemu-user-static debootstrap&lt;br /&gt;
&lt;br /&gt;
Next set up the chroot env, create your directory, calling it what you like, if it doesn&#039;t exist.&lt;br /&gt;
 # mkdir raspbian_armhf_wheezy&lt;br /&gt;
&lt;br /&gt;
Bootstrap your new environment&lt;br /&gt;
 # qemu-debootstrap --arch armhf wheezy raspbian_armhf_wheezy http://archive.raspbian.org/raspbian&lt;br /&gt;
&lt;br /&gt;
Mount /proc and friends&lt;br /&gt;
 # mount -t proc proc raspbian_armhf_wheezy/proc&lt;br /&gt;
 # mount -t sysfs sysfs raspbian_armhf_wheezy/sys&lt;br /&gt;
 # mount -o bind /dev raspbian_armhf_wheezy/dev&lt;br /&gt;
&lt;br /&gt;
Not necessary, but you can also mount your existing src directory, if you have one, into your new chroot env.&lt;br /&gt;
 # mount --bind $HOME/path/to/my/src raspbian_armhf_wheezy/home/&amp;lt;user&amp;gt;/lmce/src&lt;br /&gt;
&lt;br /&gt;
Now you are ready to chroot into your new env and get going&lt;br /&gt;
 # LC_ALL=C chroot raspbian_armhf_wheezy&lt;br /&gt;
&lt;br /&gt;
Use &#039;&#039;apt-get update&#039;&#039; and &#039;&#039;apt-get install &amp;lt;pkg&amp;gt;&#039;&#039; to install needed packages in your chrooted env.&lt;br /&gt;
&lt;br /&gt;
==Cross Compilation setup==&lt;br /&gt;
Initially this section will have information specific to getting Qt on Pi going. Its pre-packaged and fairly easy to install.&lt;br /&gt;
&lt;br /&gt;
At the time of writing Qt on Pi tarball is at version 0.2.&lt;br /&gt;
Get the tarball here http://www.raspberrypi.org/downloads at the bottom of the page. This has a premade SD image plus the toolchain and sysroot install required for cross compilation.&lt;br /&gt;
&lt;br /&gt;
===If you are about to install this on your current machine with a working Qt development environment DON&#039;T===&lt;br /&gt;
You will need to either set up a VM or a chroot environment as the qt5 shipped with this image isn&#039;t setup to install alongside an x86 install. They plan on having these play nice in future releases.&lt;br /&gt;
&lt;br /&gt;
==Qt5, Toolchain and sysroot install==&lt;br /&gt;
This is documented on the QtonPi wiki but basically after you have downloaded the qtonpi tarball extract the three files within.&lt;br /&gt;
Then as root extract [opt-qt5-current.tar.bz2] and [toolchain-and-sysroot-armv5tel.tar.bz2] &lt;br /&gt;
 $ cd /&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/opt-qt5-current.tar.bz2&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/toolchain-and-sysroot-armv5tel.tar.bz2&lt;br /&gt;
&lt;br /&gt;
===Qt creator===&lt;br /&gt;
The tarball comes with a recent version of qtcreator, but since then qt2.5 RC has come out, Should be safe enough to use that instead. Just install that by executing the .bin installer. &#039;&#039;Hold that thought, qt2.5 creator RC doesn&#039;t have the deploy steps set up&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Within Qt creator you need to point it at your cross tool chain compiler+debugger:&lt;br /&gt;
#Tools-&amp;gt;Options-&amp;gt;Build&amp;amp;Run then Tool Chains&lt;br /&gt;
#then select add, in the drop-down pick GCC&lt;br /&gt;
#Select GCC and browse for compiler to&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gcc&lt;br /&gt;
and for the debugger&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gdb&lt;br /&gt;
Save these selections by clicking Apply and OK&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi Setup==&lt;br /&gt;
===Virtual using qemu===&lt;br /&gt;
As I don&#039;t have a rpi yet I used qemu to do some initial testing.&lt;br /&gt;
My setup was a 12.04 VM.&lt;br /&gt;
You can either install qemu&lt;br /&gt;
 sudo apt-get install qemu-system&lt;br /&gt;
Or you can build qemu from git. You only need to do this if the qemu on your distro doesn&#039;t support the Broadcom SOC (ARM1176 core) on the Pi.&lt;br /&gt;
In order to boot your image you will need a suitable kernel for your emulator, there is one available here http://dl.dropbox.com/u/45842273/zImage_3.1.9 &lt;br /&gt;
Boot your virtual Pi &lt;br /&gt;
 qemu-system-arm -kernel kernel-qemu -cpu arm1176 -m 256 -M versatilepb -no-reboot -serial stdio -append &amp;quot;root=/dev/sda2 rw panic=1&amp;quot; qtonpi-sdcard-0.2.img -redir tcp:5022::22&lt;br /&gt;
&lt;br /&gt;
add&lt;br /&gt;
 console=ttyAMA0&lt;br /&gt;
to the -append param to have the boot console re-directed to the terminal.&lt;br /&gt;
&lt;br /&gt;
the -redir tcp:5022::22 redirects port 22 (ssh) on the virtual Pi to port 5022 on the host enabling you to ssh in.&lt;br /&gt;
 ssh pi@localhost -p5022&lt;br /&gt;
===Raspberry Pi Setup===&lt;br /&gt;
I used the image I was using above and wrote it to an SD card.&#039;&#039;If you are on windows make sure your machine can handle larger cards&#039;&#039;&lt;br /&gt;
By default the qtonpi release doesn&#039;t have the network if enabled. On each boot you can run&lt;br /&gt;
 ifup eth0&lt;br /&gt;
or&lt;br /&gt;
 dhclient eth0&lt;br /&gt;
or&lt;br /&gt;
 just edit /etc/sysconfig/network-scripts/ifcfg-eth0 and set the ONBOOT option equal to YES and be done with it.&lt;br /&gt;
&lt;br /&gt;
Also you need to set the time and date after each boot - no RTC on the rPi&lt;br /&gt;
&lt;br /&gt;
==Code Changes==&lt;br /&gt;
According to the current Qt Documentation adding&lt;br /&gt;
 greaterThan(QT_MAJOR_VERSION, 4) {&lt;br /&gt;
        QT += widgets&lt;br /&gt;
        QT += quick1&lt;br /&gt;
    } else {&lt;br /&gt;
        QT += declarative&lt;br /&gt;
    }&lt;br /&gt;
to the pro file loads the correct modules for both Qt4/Qt5.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;04/07/2012&#039;&#039; - see ticket [http://svn.linuxmce.org/trac.cgi/ticket/1497 trac #1497] code checked into svn.&lt;br /&gt;
&lt;br /&gt;
===&amp;quot;Useful&amp;quot; Qt links===&lt;br /&gt;
http://qt-project.org/wiki/Transition_from_Qt_4.x_to_Qt5&lt;br /&gt;
&lt;br /&gt;
https://qt-project.org/wiki/New_Signal_Slot_Syntax&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/Qt-5Features&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/QML1-vs-QML2&lt;br /&gt;
&lt;br /&gt;
A recent but good addition http://doc-snapshot.qt-project.org/5.0/qtquick-porting-qt5.html#porting-c-code&lt;br /&gt;
&lt;br /&gt;
I don&#039;t know whether these apply to how Qt5 will be when it is released, but they don&#039;t completely correspond to it in its current state, so don&#039;t believe all you read.&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi distros==&lt;br /&gt;
Looking at http://elinux.org/RPi_Distributions there are quite a few to choose from.&lt;br /&gt;
&lt;br /&gt;
Which is the best fit? I don&#039;t know.&lt;br /&gt;
&lt;br /&gt;
I&#039;m starting with QtonPi but I don&#039;t know if a full fedora release is necessary.&lt;br /&gt;
&#039;&#039;This is actually a trimmed down fedora release no X, graphics written direct to fb&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Mer/Meego might be a good fit too.&lt;br /&gt;
&lt;br /&gt;
=qOrbiter on Pi=&lt;br /&gt;
==QtonPi 0.2 image==&lt;br /&gt;
trimmed down fedora remix with qt5 pre-installed, no gui.&lt;br /&gt;
====Status====&lt;br /&gt;
&#039;&#039;28/05/2012&#039;&#039; - Unfortunately I have not been able to get my compiled qOrbiter to run on my virtual setup.&lt;br /&gt;
Depending on the combination of kernel I use and/or SD image I either get an illegal instruction or and error creating a vchiq instance.&lt;br /&gt;
&lt;br /&gt;
And given that the vchiq lib stuff is to do with the GPU, which is initialised in firmware, this may be a bit of an impass until I get actual hardware.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;30/05/2012&#039;&#039; - Have just received my rPi and my previously compiled qOrbiter starts and gets past the vchiq/illegal instruction I had.&lt;br /&gt;
I have other issues before I get it going but all going in the right direction.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;02/06/2012&#039;&#039; - qOrbiter splash screen loads, communicates with dcerouter, gets config - then boom my network dies. I don&#039;t know if its rPi specific or some porting issue with qOrbiter. I see &#039;&#039;smsc95xx 1-1.1:1.0: eth0: kevent 2 may have been dropped&#039;&#039; scroll past me. My ssh connection dies as a result so I need to be logged in on the rPi. Needs more investigation...&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;06/06/2012&#039;&#039; - got past n/w problem, now home screen loads. Also had to disable qml screen saver. The shader effect component is supposed to be available via QtQuick 2.0 and not need the labs plugin, but this appears not to be the case. It is likely it is just not in the snapshot yet.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;08/06/2012&#039;&#039; - It seems there is no mouse support in the current 0.2 qtonpi SD image. This is a deal breaker until 0.3 image is released. Mouse support has been checked into git so is available if we roll our own qt5.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;28/08/2012&#039;&#039; - I don&#039;t think there will be an update for this - so am going to consider it parked.&lt;br /&gt;
&lt;br /&gt;
==Next image - Debian Wheezy==&lt;br /&gt;
Investigating a debian wheezy port at the moment - should eek out a bit more speed using hardfp. There are qt50-snapshots available for the target. May need to set up a separate toolchain.&lt;br /&gt;
===Status===&lt;br /&gt;
&#039;&#039;11/06/2012&#039;&#039; - existing qOrbiter won&#039;t run on target, need to link against newer qt5 sysroot on host.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;19/06/2012&#039;&#039; - have rebuilt and linked qOrbiter against qt5 from git. Up and running again on my Raspberry Pi. The default CPU/GPU split of 192/64 allows qOrbiter to run, lower one - 244/32 gives an error creating the display surface. Will bump up split to 128/128 if I get display issues.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;22/06/2012&#039;&#039; - as I thought, I had to move the split to 128/128 and now I get no GL memory errors and the background effects work on the home screen. I need to find out why switching threads away from the qml engine is failing.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;28/08/2012&#039;&#039; - Using the Raspbian image - (hardfp debian wheezy). Qt5 snapshots are being rolled for the target so apt can be used to install on Pi. In process of rolling qmake and friends for host to match. Next step build qOrbiter again.&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31939</id>
		<title>RaspberryPi qOrbiter</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31939"/>
		<updated>2012-08-28T11:32:58Z</updated>

		<summary type="html">&lt;p&gt;Coley: Status update&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Development]]&lt;br /&gt;
==Device Specification==&lt;br /&gt;
-The Raspberry Pi is an ARM based computer the size of a credit card.  700Mhz, 256MB RAM, Ethernet, 2xUSB, GPIO&lt;br /&gt;
&lt;br /&gt;
-256MB of RAM is insufficient to build lmce.  MakeRelease and MakeRelease_PrepFiles both fail with out of memory errors due to the limited memory available on the RPi.&lt;br /&gt;
-Cross-compiling will be required.  More notes to follow.&lt;br /&gt;
==Debian Chroot Environment==&lt;br /&gt;
One approach is to set up a debian chroot environment, and use qemu with pass though emulation.&lt;br /&gt;
See http://wiki.debian.org/EmDebian/CrossDebootstrap#QEMU.2BAC8-debootstrap_approach&lt;br /&gt;
===Specifically for the Pi with raspbian image===&lt;br /&gt;
&#039;&#039;sudo needed for all of these commands&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Install some necessaries&lt;br /&gt;
 # apt-get install binfmt-support qemu qemu-user-static debootstrap&lt;br /&gt;
&lt;br /&gt;
Next set up the chroot env, create your directory, calling it what you like, if it doesn&#039;t exist.&lt;br /&gt;
 # mkdir raspbian_armhf_wheezy&lt;br /&gt;
&lt;br /&gt;
Bootstrap your new environment&lt;br /&gt;
 # qemu-debootstrap --arch armhf wheezy raspbian_armhf_wheezy http://archive.raspbian.org/raspbian&lt;br /&gt;
&lt;br /&gt;
Mount /proc and friends&lt;br /&gt;
 # mount -t proc proc raspbian_armhf_wheezy/proc&lt;br /&gt;
 # mount -t sysfs sysfs raspbian_armhf_wheezy/sys&lt;br /&gt;
 # mount -o bind /dev raspbian_armhf_wheezy/dev&lt;br /&gt;
&lt;br /&gt;
Not necessary, but you can also mount your existing src directory, if you have one, into your new chroot env.&lt;br /&gt;
 # mount --bind $HOME/path/to/my/src raspbian_armhf_wheezy/home/&amp;lt;user&amp;gt;/lmce/src&lt;br /&gt;
&lt;br /&gt;
Now you are ready to chroot into your new env and get going&lt;br /&gt;
 # LC_ALL=C chroot raspbian_armhf_wheezy&lt;br /&gt;
&lt;br /&gt;
Use &#039;&#039;apt-get update&#039;&#039; and &#039;&#039;apt-get install &amp;lt;pkg&amp;gt;&#039;&#039; to install needed packages in your chrooted env.&lt;br /&gt;
&lt;br /&gt;
==Cross Compilation setup==&lt;br /&gt;
Initially this section will have information specific to getting Qt on Pi going. Its pre-packaged and fairly easy to install.&lt;br /&gt;
&lt;br /&gt;
At the time of writing Qt on Pi tarball is at version 0.2.&lt;br /&gt;
Get the tarball here http://www.raspberrypi.org/downloads at the bottom of the page. This has a premade SD image plus the toolchain and sysroot install required for cross compilation.&lt;br /&gt;
&lt;br /&gt;
===If you are about to install this on your current machine with a working Qt development environment DON&#039;T===&lt;br /&gt;
You will need to either set up a VM or a chroot environment as the qt5 shipped with this image isn&#039;t setup to install alongside an x86 install. They plan on having these play nice in future releases.&lt;br /&gt;
&lt;br /&gt;
==Qt5, Toolchain and sysroot install==&lt;br /&gt;
This is documented on the QtonPi wiki but basically after you have downloaded the qtonpi tarball extract the three files within.&lt;br /&gt;
Then as root extract [opt-qt5-current.tar.bz2] and [toolchain-and-sysroot-armv5tel.tar.bz2] &lt;br /&gt;
 $ cd /&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/opt-qt5-current.tar.bz2&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/toolchain-and-sysroot-armv5tel.tar.bz2&lt;br /&gt;
&lt;br /&gt;
===Qt creator===&lt;br /&gt;
The tarball comes with a recent version of qtcreator, but since then qt2.5 RC has come out, Should be safe enough to use that instead. Just install that by executing the .bin installer. &#039;&#039;Hold that thought, qt2.5 creator RC doesn&#039;t have the deploy steps set up&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Within Qt creator you need to point it at your cross tool chain compiler+debugger:&lt;br /&gt;
#Tools-&amp;gt;Options-&amp;gt;Build&amp;amp;Run then Tool Chains&lt;br /&gt;
#then select add, in the drop-down pick GCC&lt;br /&gt;
#Select GCC and browse for compiler to&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gcc&lt;br /&gt;
and for the debugger&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gdb&lt;br /&gt;
Save these selections by clicking Apply and OK&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi Setup==&lt;br /&gt;
===Virtual using qemu===&lt;br /&gt;
As I don&#039;t have a rpi yet I used qemu to do some initial testing.&lt;br /&gt;
My setup was a 12.04 VM.&lt;br /&gt;
You can either install qemu&lt;br /&gt;
 sudo apt-get install qemu-system&lt;br /&gt;
Or you can build qemu from git. You only need to do this if the qemu on your distro doesn&#039;t support the Broadcom SOC (ARM1176 core) on the Pi.&lt;br /&gt;
In order to boot your image you will need a suitable kernel for your emulator, there is one available here http://dl.dropbox.com/u/45842273/zImage_3.1.9 &lt;br /&gt;
Boot your virtual Pi &lt;br /&gt;
 qemu-system-arm -kernel kernel-qemu -cpu arm1176 -m 256 -M versatilepb -no-reboot -serial stdio -append &amp;quot;root=/dev/sda2 rw panic=1&amp;quot; qtonpi-sdcard-0.2.img -redir tcp:5022::22&lt;br /&gt;
&lt;br /&gt;
add&lt;br /&gt;
 console=ttyAMA0&lt;br /&gt;
to the -append param to have the boot console re-directed to the terminal.&lt;br /&gt;
&lt;br /&gt;
the -redir tcp:5022::22 redirects port 22 (ssh) on the virtual Pi to port 5022 on the host enabling you to ssh in.&lt;br /&gt;
 ssh pi@localhost -p5022&lt;br /&gt;
===Raspberry Pi Setup===&lt;br /&gt;
I used the image I was using above and wrote it to an SD card.&#039;&#039;If you are on windows make sure your machine can handle larger cards&#039;&#039;&lt;br /&gt;
By default the qtonpi release doesn&#039;t have the network if enabled. On each boot you can run&lt;br /&gt;
 ifup eth0&lt;br /&gt;
or&lt;br /&gt;
 dhclient eth0&lt;br /&gt;
or&lt;br /&gt;
 just edit /etc/sysconfig/network-scripts/ifcfg-eth0 and set the ONBOOT option equal to YES and be done with it.&lt;br /&gt;
&lt;br /&gt;
Also you need to set the time and date after each boot - no RTC on the rPi&lt;br /&gt;
&lt;br /&gt;
==Code Changes==&lt;br /&gt;
According to the current Qt Documentation adding&lt;br /&gt;
 greaterThan(QT_MAJOR_VERSION, 4) {&lt;br /&gt;
        QT += widgets&lt;br /&gt;
        QT += quick1&lt;br /&gt;
    } else {&lt;br /&gt;
        QT += declarative&lt;br /&gt;
    }&lt;br /&gt;
to the pro file loads the correct modules for both Qt4/Qt5.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;04/07/2012&#039;&#039; - see ticket [http://svn.linuxmce.org/trac.cgi/ticket/1497 trac #1497] code checked into svn.&lt;br /&gt;
&lt;br /&gt;
===&amp;quot;Useful&amp;quot; Qt links===&lt;br /&gt;
http://qt-project.org/wiki/Transition_from_Qt_4.x_to_Qt5&lt;br /&gt;
&lt;br /&gt;
https://qt-project.org/wiki/New_Signal_Slot_Syntax&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/Qt-5Features&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/QML1-vs-QML2&lt;br /&gt;
&lt;br /&gt;
A recent but good addition http://doc-snapshot.qt-project.org/5.0/qtquick-porting-qt5.html#porting-c-code&lt;br /&gt;
&lt;br /&gt;
I don&#039;t know whether these apply to how Qt5 will be when it is released, but they don&#039;t completely correspond to it in its current state, so don&#039;t believe all you read.&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi distros==&lt;br /&gt;
Looking at http://elinux.org/RPi_Distributions there are quite a few to choose from.&lt;br /&gt;
&lt;br /&gt;
Which is the best fit? I don&#039;t know.&lt;br /&gt;
&lt;br /&gt;
I&#039;m starting with QtonPi but I don&#039;t know if a full fedora release is necessary.&lt;br /&gt;
&#039;&#039;This is actually a trimmed down fedora release no X, graphics written direct to fb&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Mer/Meego might be a good fit too.&lt;br /&gt;
&lt;br /&gt;
=qOrbiter on Pi=&lt;br /&gt;
==QtonPi 0.2 image==&lt;br /&gt;
trimmed down fedora remix with qt5 pre-installed, no gui.&lt;br /&gt;
====Status====&lt;br /&gt;
&#039;&#039;28/05/2012&#039;&#039; - Unfortunately I have not been able to get my compiled qOrbiter to run on my virtual setup.&lt;br /&gt;
Depending on the combination of kernel I use and/or SD image I either get an illegal instruction or and error creating a vchiq instance.&lt;br /&gt;
&lt;br /&gt;
And given that the vchiq lib stuff is to do with the GPU, which is initialised in firmware, this may be a bit of an impass until I get actual hardware.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;30/05/2012&#039;&#039; - Have just received my rPi and my previously compiled qOrbiter starts and gets past the vchiq/illegal instruction I had.&lt;br /&gt;
I have other issues before I get it going but all going in the right direction.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;02/06/2012&#039;&#039; - qOrbiter splash screen loads, communicates with dcerouter, gets config - then boom my network dies. I don&#039;t know if its rPi specific or some porting issue with qOrbiter. I see &#039;&#039;smsc95xx 1-1.1:1.0: eth0: kevent 2 may have been dropped&#039;&#039; scroll past me. My ssh connection dies as a result so I need to be logged in on the rPi. Needs more investigation...&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;06/06/2012&#039;&#039; - got past n/w problem, now home screen loads. Also had to disable qml screen saver. The shader effect component is supposed to be available via QtQuick 2.0 and not need the labs plugin, but this appears not to be the case. It is likely it is just not in the snapshot yet.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;08/06/2012&#039;&#039; - It seems there is no mouse support in the current 0.2 qtonpi SD image. This is a deal breaker until 0.3 image is released. Mouse support has been checked into git so is available if we roll our own qt5.&lt;br /&gt;
&lt;br /&gt;
==Next image - Debian Wheezy==&lt;br /&gt;
Investigating a debian wheezy port at the moment - should eek out a bit more speed using hardfp. There are qt50-snapshots available for the target. May need to set up a separate toolchain.&lt;br /&gt;
===Status===&lt;br /&gt;
&#039;&#039;11/06/2012&#039;&#039; - existing qOrbiter won&#039;t run on target, need to link against newer qt5 sysroot on host.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;19/06/2012&#039;&#039; - have rebuilt and linked qOrbiter against qt5 from git. Up and running again on my Raspberry Pi. The default CPU/GPU split of 192/64 allows qOrbiter to run, lower one - 244/32 gives an error creating the display surface. Will bump up split to 128/128 if I get display issues.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;22/06/2012&#039;&#039; - as I thought, I had to move the split to 128/128 and now I get no GL memory errors and the background effects work on the home screen. I need to find out why switching threads away from the qml engine is failing.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;28/08/2012&#039;&#039; - Using the Raspbian image - (hardfp debian wheezy). Qt5 snapshots are being rolled for the target so apt can be used to install on Pi. In process of rolling qmake and friends for host to match. Next step build qOrbiter again.&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31735</id>
		<title>RaspberryPi qOrbiter</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31735"/>
		<updated>2012-07-25T15:40:40Z</updated>

		<summary type="html">&lt;p&gt;Coley: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Development]]&lt;br /&gt;
==Device Specification==&lt;br /&gt;
-The Raspberry Pi is an ARM based computer the size of a credit card.  700Mhz, 256MB RAM, Ethernet, 2xUSB, GPIO&lt;br /&gt;
&lt;br /&gt;
-256MB of RAM is insufficient to build lmce.  MakeRelease and MakeRelease_PrepFiles both fail with out of memory errors due to the limited memory available on the RPi.&lt;br /&gt;
-Cross-compiling will be required.  More notes to follow.&lt;br /&gt;
==Debian Chroot Environment==&lt;br /&gt;
One approach is to set up a debian chroot environment, and use qemu with pass though emulation.&lt;br /&gt;
See http://wiki.debian.org/EmDebian/CrossDebootstrap#QEMU.2BAC8-debootstrap_approach&lt;br /&gt;
===Specifically for the Pi with raspbian image===&lt;br /&gt;
&#039;&#039;sudo needed for all of these commands&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Install some necessaries&lt;br /&gt;
 # apt-get install binfmt-support qemu qemu-user-static debootstrap&lt;br /&gt;
&lt;br /&gt;
Next set up the chroot env, create your directory, calling it what you like, if it doesn&#039;t exist.&lt;br /&gt;
 # mkdir raspbian_armhf_wheezy&lt;br /&gt;
&lt;br /&gt;
Bootstrap your new environment&lt;br /&gt;
 # qemu-debootstrap --arch armhf wheezy raspbian_armhf_wheezy http://archive.raspbian.org/raspbian&lt;br /&gt;
&lt;br /&gt;
Mount /proc and friends&lt;br /&gt;
 # mount -t proc proc raspbian_armhf_wheezy/proc&lt;br /&gt;
 # mount -t sysfs sysfs raspbian_armhf_wheezy/sys&lt;br /&gt;
 # mount -o bind /dev raspbian_armhf_wheezy/dev&lt;br /&gt;
&lt;br /&gt;
Not necessary, but you can also mount your existing src directory, if you have one, into your new chroot env.&lt;br /&gt;
 # mount --bind $HOME/path/to/my/src raspbian_armhf_wheezy/home/&amp;lt;user&amp;gt;/lmce/src&lt;br /&gt;
&lt;br /&gt;
Now you are ready to chroot into your new env and get going&lt;br /&gt;
 # LC_ALL=C chroot raspbian_armhf_wheezy&lt;br /&gt;
&lt;br /&gt;
Use &#039;&#039;apt-get update&#039;&#039; and &#039;&#039;apt-get install &amp;lt;pkg&amp;gt;&#039;&#039; to install needed packages in your chrooted env.&lt;br /&gt;
&lt;br /&gt;
==Cross Compilation setup==&lt;br /&gt;
Initially this section will have information specific to getting Qt on Pi going. Its pre-packaged and fairly easy to install.&lt;br /&gt;
&lt;br /&gt;
At the time of writing Qt on Pi tarball is at version 0.2.&lt;br /&gt;
Get the tarball here http://www.raspberrypi.org/downloads at the bottom of the page. This has a premade SD image plus the toolchain and sysroot install required for cross compilation.&lt;br /&gt;
&lt;br /&gt;
===If you are about to install this on your current machine with a working Qt development environment DON&#039;T===&lt;br /&gt;
You will need to either set up a VM or a chroot environment as the qt5 shipped with this image isn&#039;t setup to install alongside an x86 install. They plan on having these play nice in future releases.&lt;br /&gt;
&lt;br /&gt;
==Qt5, Toolchain and sysroot install==&lt;br /&gt;
This is documented on the QtonPi wiki but basically after you have downloaded the qtonpi tarball extract the three files within.&lt;br /&gt;
Then as root extract [opt-qt5-current.tar.bz2] and [toolchain-and-sysroot-armv5tel.tar.bz2] &lt;br /&gt;
 $ cd /&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/opt-qt5-current.tar.bz2&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/toolchain-and-sysroot-armv5tel.tar.bz2&lt;br /&gt;
&lt;br /&gt;
===Qt creator===&lt;br /&gt;
The tarball comes with a recent version of qtcreator, but since then qt2.5 RC has come out, Should be safe enough to use that instead. Just install that by executing the .bin installer. &#039;&#039;Hold that thought, qt2.5 creator RC doesn&#039;t have the deploy steps set up&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Within Qt creator you need to point it at your cross tool chain compiler+debugger:&lt;br /&gt;
#Tools-&amp;gt;Options-&amp;gt;Build&amp;amp;Run then Tool Chains&lt;br /&gt;
#then select add, in the drop-down pick GCC&lt;br /&gt;
#Select GCC and browse for compiler to&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gcc&lt;br /&gt;
and for the debugger&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gdb&lt;br /&gt;
Save these selections by clicking Apply and OK&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi Setup==&lt;br /&gt;
===Virtual using qemu===&lt;br /&gt;
As I don&#039;t have a rpi yet I used qemu to do some initial testing.&lt;br /&gt;
My setup was a 12.04 VM.&lt;br /&gt;
You can either install qemu&lt;br /&gt;
 sudo apt-get install qemu-system&lt;br /&gt;
Or you can build qemu from git. You only need to do this if the qemu on your distro doesn&#039;t support the Broadcom SOC (ARM1176 core) on the Pi.&lt;br /&gt;
In order to boot your image you will need a suitable kernel for your emulator, there is one available here http://dl.dropbox.com/u/45842273/zImage_3.1.9 &lt;br /&gt;
Boot your virtual Pi &lt;br /&gt;
 qemu-system-arm -kernel kernel-qemu -cpu arm1176 -m 256 -M versatilepb -no-reboot -serial stdio -append &amp;quot;root=/dev/sda2 rw panic=1&amp;quot; qtonpi-sdcard-0.2.img -redir tcp:5022::22&lt;br /&gt;
&lt;br /&gt;
add&lt;br /&gt;
 console=ttyAMA0&lt;br /&gt;
to the -append param to have the boot console re-directed to the terminal.&lt;br /&gt;
&lt;br /&gt;
the -redir tcp:5022::22 redirects port 22 (ssh) on the virtual Pi to port 5022 on the host enabling you to ssh in.&lt;br /&gt;
 ssh pi@localhost -p5022&lt;br /&gt;
===Raspberry Pi Setup===&lt;br /&gt;
I used the image I was using above and wrote it to an SD card.&#039;&#039;If you are on windows make sure your machine can handle larger cards&#039;&#039;&lt;br /&gt;
By default the qtonpi release doesn&#039;t have the network if enabled. On each boot you can run&lt;br /&gt;
 ifup eth0&lt;br /&gt;
or&lt;br /&gt;
 dhclient eth0&lt;br /&gt;
or&lt;br /&gt;
 just edit /etc/sysconfig/network-scripts/ifcfg-eth0 and set the ONBOOT option equal to YES and be done with it.&lt;br /&gt;
&lt;br /&gt;
Also you need to set the time and date after each boot - no RTC on the rPi&lt;br /&gt;
&lt;br /&gt;
==Code Changes==&lt;br /&gt;
According to the current Qt Documentation adding&lt;br /&gt;
 greaterThan(QT_MAJOR_VERSION, 4) {&lt;br /&gt;
        QT += widgets&lt;br /&gt;
        QT += quick1&lt;br /&gt;
    } else {&lt;br /&gt;
        QT += declarative&lt;br /&gt;
    }&lt;br /&gt;
to the pro file loads the correct modules for both Qt4/Qt5.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;04/07/2012&#039;&#039; - see ticket [http://svn.linuxmce.org/trac.cgi/ticket/1497 trac #1497] code checked into svn.&lt;br /&gt;
&lt;br /&gt;
===&amp;quot;Useful&amp;quot; Qt links===&lt;br /&gt;
http://qt-project.org/wiki/Transition_from_Qt_4.x_to_Qt5&lt;br /&gt;
&lt;br /&gt;
https://qt-project.org/wiki/New_Signal_Slot_Syntax&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/Qt-5Features&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/QML1-vs-QML2&lt;br /&gt;
&lt;br /&gt;
A recent but good addition http://doc-snapshot.qt-project.org/5.0/qtquick-porting-qt5.html#porting-c-code&lt;br /&gt;
&lt;br /&gt;
I don&#039;t know whether these apply to how Qt5 will be when it is released, but they don&#039;t completely correspond to it in its current state, so don&#039;t believe all you read.&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi distros==&lt;br /&gt;
Looking at http://elinux.org/RPi_Distributions there are quite a few to choose from.&lt;br /&gt;
&lt;br /&gt;
Which is the best fit? I don&#039;t know.&lt;br /&gt;
&lt;br /&gt;
I&#039;m starting with QtonPi but I don&#039;t know if a full fedora release is necessary.&lt;br /&gt;
&#039;&#039;This is actually a trimmed down fedora release no X, graphics written direct to fb&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Mer/Meego might be a good fit too.&lt;br /&gt;
&lt;br /&gt;
=qOrbiter on Pi=&lt;br /&gt;
==QtonPi 0.2 image==&lt;br /&gt;
trimmed down fedora remix with qt5 pre-installed, no gui.&lt;br /&gt;
====Status====&lt;br /&gt;
&#039;&#039;28/05/2012&#039;&#039; - Unfortunately I have not been able to get my compiled qOrbiter to run on my virtual setup.&lt;br /&gt;
Depending on the combination of kernel I use and/or SD image I either get an illegal instruction or and error creating a vchiq instance.&lt;br /&gt;
&lt;br /&gt;
And given that the vchiq lib stuff is to do with the GPU, which is initialised in firmware, this may be a bit of an impass until I get actual hardware.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;30/05/2012&#039;&#039; - Have just received my rPi and my previously compiled qOrbiter starts and gets past the vchiq/illegal instruction I had.&lt;br /&gt;
I have other issues before I get it going but all going in the right direction.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;02/06/2012&#039;&#039; - qOrbiter splash screen loads, communicates with dcerouter, gets config - then boom my network dies. I don&#039;t know if its rPi specific or some porting issue with qOrbiter. I see &#039;&#039;smsc95xx 1-1.1:1.0: eth0: kevent 2 may have been dropped&#039;&#039; scroll past me. My ssh connection dies as a result so I need to be logged in on the rPi. Needs more investigation...&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;06/06/2012&#039;&#039; - got past n/w problem, now home screen loads. Also had to disable qml screen saver. The shader effect component is supposed to be available via QtQuick 2.0 and not need the labs plugin, but this appears not to be the case. It is likely it is just not in the snapshot yet.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;08/06/2012&#039;&#039; - It seems there is no mouse support in the current 0.2 qtonpi SD image. This is a deal breaker until 0.3 image is released. Mouse support has been checked into git so is available if we roll our own qt5.&lt;br /&gt;
&lt;br /&gt;
==Next image - Debian Wheezy==&lt;br /&gt;
Investigating a debian wheezy port at the moment - should eek out a bit more speed using hardfp. There are qt50-snapshots available for the target. May need to set up a separate toolchain.&lt;br /&gt;
===Status===&lt;br /&gt;
&#039;&#039;11/06/2012&#039;&#039; - existing qOrbiter won&#039;t run on target, need to link against newer qt5 sysroot on host.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;19/06/2012&#039;&#039; - have rebuilt and linked qOrbiter against qt5 from git. Up and running again on my Raspberry Pi. The default CPU/GPU split of 192/64 allows qOrbiter to run, lower one - 244/32 gives an error creating the display surface. Will bump up split to 128/128 if I get display issues.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;22/06/2012&#039;&#039; - as I thought, I had to move the split to 128/128 and now I get no GL memory errors and the background effects work on the home screen. I need to find out why switching threads away from the qml engine is failing.&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Porting_Raspian&amp;diff=31714</id>
		<title>Porting Raspian</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Porting_Raspian&amp;diff=31714"/>
		<updated>2012-07-24T16:24:08Z</updated>

		<summary type="html">&lt;p&gt;Coley: Porting Raspian moved to Porting Raspbian: Typo in title.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Porting Raspbian]]&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=Porting_Raspbian&amp;diff=31713</id>
		<title>Porting Raspbian</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=Porting_Raspbian&amp;diff=31713"/>
		<updated>2012-07-24T16:24:08Z</updated>

		<summary type="html">&lt;p&gt;Coley: Porting Raspian moved to Porting Raspbian: Typo in title.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Development]]&lt;br /&gt;
This will attempt to highlight some of the requirements/process intended/followed for porting lmce to raspbian for use on the raspberry pi&lt;br /&gt;
New database data&lt;br /&gt;
# update the &#039;Distro&#039; table &lt;br /&gt;
# Update all the Packages related tables. &lt;br /&gt;
Linuxmce uses the database at build time when creating deb packages for depencies and later at install time to install those dependecies, add repositories and so on. Since on every release some packages tend to change names or split/merge into others, updating the packages tables is time consuming and as you need to do some install / fix cycles before figure them out.&lt;br /&gt;
&lt;br /&gt;
Conf files update&lt;br /&gt;
# Build dependencies list needs updating.&lt;br /&gt;
The list with packages needed for building linuxmce needs to be updated from one release to another so you can have the dependencies installed on the build machine. There is no automatic tool for doing this and is a time consuming task when package names change and split as you need to wait for the build to fail to intstall other packages.&lt;br /&gt;
&lt;br /&gt;
Other issues:&lt;br /&gt;
# diskless boot? net boot is not immediately possible from RPi, perhaps a netboot after kernel?&lt;br /&gt;
# disked boot? may be required&lt;br /&gt;
# avwizard - graphics setup is performed by gpu prior to the kernel boot.  new method of setting/determining graphics mode? changing resolution requires reboot for gpu init&lt;br /&gt;
# qOrbiter &lt;br /&gt;
# omxplayer device template&lt;br /&gt;
# arm libs required for pre-compiled libraries (usb-uirt, external media identifier?/id-my-disc?, more?)&lt;br /&gt;
# mythtv frontend is too heavy for RPi, recordings will need to be natively played by omxplayer&lt;br /&gt;
# install scripts for diskless or disked based systems &lt;br /&gt;
# boot scripts&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31711</id>
		<title>RaspberryPi qOrbiter</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31711"/>
		<updated>2012-07-24T15:18:33Z</updated>

		<summary type="html">&lt;p&gt;Coley: debian-&amp;gt;raspbian to avoid confusion&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Device Specification==&lt;br /&gt;
-The Raspberry Pi is an ARM based computer the size of a credit card.  700Mhz, 256MB RAM, Ethernet, 2xUSB, GPIO&lt;br /&gt;
&lt;br /&gt;
-256MB of RAM is insufficient to build lmce.  MakeRelease and MakeRelease_PrepFiles both fail with out of memory errors due to the limited memory available on the RPi.&lt;br /&gt;
-Cross-compiling will be required.  More notes to follow.&lt;br /&gt;
==Debian Chroot Environment==&lt;br /&gt;
One approach is to set up a debian chroot environment, and use qemu with pass though emulation.&lt;br /&gt;
See http://wiki.debian.org/EmDebian/CrossDebootstrap#QEMU.2BAC8-debootstrap_approach&lt;br /&gt;
===Specifically for the Pi with raspbian image===&lt;br /&gt;
&#039;&#039;sudo needed for all of these commands&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Install some necessaries&lt;br /&gt;
 # apt-get install binfmt-support qemu qemu-user-static debootstrap&lt;br /&gt;
&lt;br /&gt;
Next set up the chroot env, create your directory, calling it what you like, if it doesn&#039;t exist.&lt;br /&gt;
 # mkdir raspbian_armhf_wheezy&lt;br /&gt;
&lt;br /&gt;
Bootstrap your new environment&lt;br /&gt;
 # qemu-debootstrap --arch armhf wheezy raspbian_armhf_wheezy http://archive.raspbian.org/raspbian&lt;br /&gt;
&lt;br /&gt;
Mount /proc and friends&lt;br /&gt;
 # mount -t proc proc raspbian_armhf_wheezy/proc&lt;br /&gt;
 # mount -t sysfs sysfs raspbian_armhf_wheezy/sys&lt;br /&gt;
 # mount -o bind /dev raspbian_armhf_wheezy/dev&lt;br /&gt;
&lt;br /&gt;
Not necessary, but you can also mount your existing src directory, if you have one, into your new chroot env.&lt;br /&gt;
 # mount --bind $HOME/path/to/my/src raspbian_armhf_wheezy/home/&amp;lt;user&amp;gt;/lmce/src&lt;br /&gt;
&lt;br /&gt;
Now you are ready to chroot into your new env and get going&lt;br /&gt;
 # LC_ALL=C chroot raspbian_armhf_wheezy&lt;br /&gt;
&lt;br /&gt;
Use &#039;&#039;apt-get update&#039;&#039; and &#039;&#039;apt-get install &amp;lt;pkg&amp;gt;&#039;&#039; to install needed packages in your chrooted env.&lt;br /&gt;
&lt;br /&gt;
==Cross Compilation setup==&lt;br /&gt;
Initially this section will have information specific to getting Qt on Pi going. Its pre-packaged and fairly easy to install.&lt;br /&gt;
&lt;br /&gt;
At the time of writing Qt on Pi tarball is at version 0.2.&lt;br /&gt;
Get the tarball here http://www.raspberrypi.org/downloads at the bottom of the page. This has a premade SD image plus the toolchain and sysroot install required for cross compilation.&lt;br /&gt;
&lt;br /&gt;
===If you are about to install this on your current machine with a working Qt development environment DON&#039;T===&lt;br /&gt;
You will need to either set up a VM or a chroot environment as the qt5 shipped with this image isn&#039;t setup to install alongside an x86 install. They plan on having these play nice in future releases.&lt;br /&gt;
&lt;br /&gt;
==Qt5, Toolchain and sysroot install==&lt;br /&gt;
This is documented on the QtonPi wiki but basically after you have downloaded the qtonpi tarball extract the three files within.&lt;br /&gt;
Then as root extract [opt-qt5-current.tar.bz2] and [toolchain-and-sysroot-armv5tel.tar.bz2] &lt;br /&gt;
 $ cd /&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/opt-qt5-current.tar.bz2&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/toolchain-and-sysroot-armv5tel.tar.bz2&lt;br /&gt;
&lt;br /&gt;
===Qt creator===&lt;br /&gt;
The tarball comes with a recent version of qtcreator, but since then qt2.5 RC has come out, Should be safe enough to use that instead. Just install that by executing the .bin installer. &#039;&#039;Hold that thought, qt2.5 creator RC doesn&#039;t have the deploy steps set up&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Within Qt creator you need to point it at your cross tool chain compiler+debugger:&lt;br /&gt;
#Tools-&amp;gt;Options-&amp;gt;Build&amp;amp;Run then Tool Chains&lt;br /&gt;
#then select add, in the drop-down pick GCC&lt;br /&gt;
#Select GCC and browse for compiler to&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gcc&lt;br /&gt;
and for the debugger&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gdb&lt;br /&gt;
Save these selections by clicking Apply and OK&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi Setup==&lt;br /&gt;
===Virtual using qemu===&lt;br /&gt;
As I don&#039;t have a rpi yet I used qemu to do some initial testing.&lt;br /&gt;
My setup was a 12.04 VM.&lt;br /&gt;
You can either install qemu&lt;br /&gt;
 sudo apt-get install qemu-system&lt;br /&gt;
Or you can build qemu from git. You only need to do this if the qemu on your distro doesn&#039;t support the Broadcom SOC (ARM1176 core) on the Pi.&lt;br /&gt;
In order to boot your image you will need a suitable kernel for your emulator, there is one available here http://dl.dropbox.com/u/45842273/zImage_3.1.9 &lt;br /&gt;
Boot your virtual Pi &lt;br /&gt;
 qemu-system-arm -kernel kernel-qemu -cpu arm1176 -m 256 -M versatilepb -no-reboot -serial stdio -append &amp;quot;root=/dev/sda2 rw panic=1&amp;quot; qtonpi-sdcard-0.2.img -redir tcp:5022::22&lt;br /&gt;
&lt;br /&gt;
add&lt;br /&gt;
 console=ttyAMA0&lt;br /&gt;
to the -append param to have the boot console re-directed to the terminal.&lt;br /&gt;
&lt;br /&gt;
the -redir tcp:5022::22 redirects port 22 (ssh) on the virtual Pi to port 5022 on the host enabling you to ssh in.&lt;br /&gt;
 ssh pi@localhost -p5022&lt;br /&gt;
===Raspberry Pi Setup===&lt;br /&gt;
I used the image I was using above and wrote it to an SD card.&#039;&#039;If you are on windows make sure your machine can handle larger cards&#039;&#039;&lt;br /&gt;
By default the qtonpi release doesn&#039;t have the network if enabled. On each boot you can run&lt;br /&gt;
 ifup eth0&lt;br /&gt;
or&lt;br /&gt;
 dhclient eth0&lt;br /&gt;
or&lt;br /&gt;
 just edit /etc/sysconfig/network-scripts/ifcfg-eth0 and set the ONBOOT option equal to YES and be done with it.&lt;br /&gt;
&lt;br /&gt;
Also you need to set the time and date after each boot - no RTC on the rPi&lt;br /&gt;
&lt;br /&gt;
==Code Changes==&lt;br /&gt;
According to the current Qt Documentation adding&lt;br /&gt;
 greaterThan(QT_MAJOR_VERSION, 4) {&lt;br /&gt;
        QT += widgets&lt;br /&gt;
        QT += quick1&lt;br /&gt;
    } else {&lt;br /&gt;
        QT += declarative&lt;br /&gt;
    }&lt;br /&gt;
to the pro file loads the correct modules for both Qt4/Qt5.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;04/07/2012&#039;&#039; - see ticket [http://svn.linuxmce.org/trac.cgi/ticket/1497 trac #1497] code checked into svn.&lt;br /&gt;
&lt;br /&gt;
===&amp;quot;Useful&amp;quot; Qt links===&lt;br /&gt;
http://qt-project.org/wiki/Transition_from_Qt_4.x_to_Qt5&lt;br /&gt;
&lt;br /&gt;
https://qt-project.org/wiki/New_Signal_Slot_Syntax&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/Qt-5Features&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/QML1-vs-QML2&lt;br /&gt;
&lt;br /&gt;
A recent but good addition http://doc-snapshot.qt-project.org/5.0/qtquick-porting-qt5.html#porting-c-code&lt;br /&gt;
&lt;br /&gt;
I don&#039;t know whether these apply to how Qt5 will be when it is released, but they don&#039;t completely correspond to it in its current state, so don&#039;t believe all you read.&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi distros==&lt;br /&gt;
Looking at http://elinux.org/RPi_Distributions there are quite a few to choose from.&lt;br /&gt;
&lt;br /&gt;
Which is the best fit? I don&#039;t know.&lt;br /&gt;
&lt;br /&gt;
I&#039;m starting with QtonPi but I don&#039;t know if a full fedora release is necessary.&lt;br /&gt;
&#039;&#039;This is actually a trimmed down fedora release no X, graphics written direct to fb&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Mer/Meego might be a good fit too.&lt;br /&gt;
&lt;br /&gt;
=qOrbiter on Pi=&lt;br /&gt;
==QtonPi 0.2 image==&lt;br /&gt;
trimmed down fedora remix with qt5 pre-installed, no gui.&lt;br /&gt;
====Status====&lt;br /&gt;
&#039;&#039;28/05/2012&#039;&#039; - Unfortunately I have not been able to get my compiled qOrbiter to run on my virtual setup.&lt;br /&gt;
Depending on the combination of kernel I use and/or SD image I either get an illegal instruction or and error creating a vchiq instance.&lt;br /&gt;
&lt;br /&gt;
And given that the vchiq lib stuff is to do with the GPU, which is initialised in firmware, this may be a bit of an impass until I get actual hardware.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;30/05/2012&#039;&#039; - Have just received my rPi and my previously compiled qOrbiter starts and gets past the vchiq/illegal instruction I had.&lt;br /&gt;
I have other issues before I get it going but all going in the right direction.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;02/06/2012&#039;&#039; - qOrbiter splash screen loads, communicates with dcerouter, gets config - then boom my network dies. I don&#039;t know if its rPi specific or some porting issue with qOrbiter. I see &#039;&#039;smsc95xx 1-1.1:1.0: eth0: kevent 2 may have been dropped&#039;&#039; scroll past me. My ssh connection dies as a result so I need to be logged in on the rPi. Needs more investigation...&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;06/06/2012&#039;&#039; - got past n/w problem, now home screen loads. Also had to disable qml screen saver. The shader effect component is supposed to be available via QtQuick 2.0 and not need the labs plugin, but this appears not to be the case. It is likely it is just not in the snapshot yet.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;08/06/2012&#039;&#039; - It seems there is no mouse support in the current 0.2 qtonpi SD image. This is a deal breaker until 0.3 image is released. Mouse support has been checked into git so is available if we roll our own qt5.&lt;br /&gt;
&lt;br /&gt;
==Next image - Debian Wheezy==&lt;br /&gt;
Investigating a debian wheezy port at the moment - should eek out a bit more speed using hardfp. There are qt50-snapshots available for the target. May need to set up a separate toolchain.&lt;br /&gt;
===Status===&lt;br /&gt;
&#039;&#039;11/06/2012&#039;&#039; - existing qOrbiter won&#039;t run on target, need to link against newer qt5 sysroot on host.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;19/06/2012&#039;&#039; - have rebuilt and linked qOrbiter against qt5 from git. Up and running again on my Raspberry Pi. The default CPU/GPU split of 192/64 allows qOrbiter to run, lower one - 244/32 gives an error creating the display surface. Will bump up split to 128/128 if I get display issues.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;22/06/2012&#039;&#039; - as I thought, I had to move the split to 128/128 and now I get no GL memory errors and the background effects work on the home screen. I need to find out why switching threads away from the qml engine is failing.&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31710</id>
		<title>RaspberryPi qOrbiter</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31710"/>
		<updated>2012-07-24T11:11:50Z</updated>

		<summary type="html">&lt;p&gt;Coley: added chroot env setup details&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Device Specification==&lt;br /&gt;
-The Raspberry Pi is an ARM based computer the size of a credit card.  700Mhz, 256MB RAM, Ethernet, 2xUSB, GPIO&lt;br /&gt;
&lt;br /&gt;
-256MB of RAM is insufficient to build lmce.  MakeRelease and MakeRelease_PrepFiles both fail with out of memory errors due to the limited memory available on the RPi.&lt;br /&gt;
-Cross-compiling will be required.  More notes to follow.&lt;br /&gt;
==Debian Chroot Environment==&lt;br /&gt;
One approach is to set up a debian chroot environment, and use qemu with pass though emulation.&lt;br /&gt;
See http://wiki.debian.org/EmDebian/CrossDebootstrap#QEMU.2BAC8-debootstrap_approach&lt;br /&gt;
===Specifically for the Pi with raspbian image===&lt;br /&gt;
&#039;&#039;sudo needed for all of these commands&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Install some necessaries&lt;br /&gt;
 # apt-get install binfmt-support qemu qemu-user-static debootstrap&lt;br /&gt;
&lt;br /&gt;
Next set up the chroot env, create your directory, calling it what you like, if it doesn&#039;t exist.&lt;br /&gt;
 # mkdir debian_armhf_wheezy&lt;br /&gt;
&lt;br /&gt;
Bootstrap your new environment&lt;br /&gt;
 # qemu-debootstrap --arch armhf wheezy debian_armhf_wheezy http://archive.raspbian.org/raspbian&lt;br /&gt;
&lt;br /&gt;
Mount /proc and friends&lt;br /&gt;
 # mount -t proc proc debian_armhf_wheezy/proc&lt;br /&gt;
 # mount -t sysfs sysfs debian_armhf_wheezy/sys&lt;br /&gt;
 # mount -o bind /dev debian_armhf_wheezy/dev&lt;br /&gt;
&lt;br /&gt;
Not necessary, but you can also mount your existing src directory, if you have one, into your new chroot env.&lt;br /&gt;
 # mount --bind $HOME/path/to/my/src debian_armhf_wheezy/home/&amp;lt;user&amp;gt;/lmce/src&lt;br /&gt;
&lt;br /&gt;
Now you are ready to chroot into your new env and get going&lt;br /&gt;
 # LC_ALL=C chroot debian_armhf_wheezy&lt;br /&gt;
&lt;br /&gt;
Use &#039;&#039;apt-get update&#039;&#039; and &#039;&#039;apt-get install &amp;lt;pkg&amp;gt;&#039;&#039; to install needed packages in your chrooted env.&lt;br /&gt;
&lt;br /&gt;
==Cross Compilation setup==&lt;br /&gt;
Initially this section will have information specific to getting Qt on Pi going. Its pre-packaged and fairly easy to install.&lt;br /&gt;
&lt;br /&gt;
At the time of writing Qt on Pi tarball is at version 0.2.&lt;br /&gt;
Get the tarball here http://www.raspberrypi.org/downloads at the bottom of the page. This has a premade SD image plus the toolchain and sysroot install required for cross compilation.&lt;br /&gt;
&lt;br /&gt;
===If you are about to install this on your current machine with a working Qt development environment DON&#039;T===&lt;br /&gt;
You will need to either set up a VM or a chroot environment as the qt5 shipped with this image isn&#039;t setup to install alongside an x86 install. They plan on having these play nice in future releases.&lt;br /&gt;
&lt;br /&gt;
==Qt5, Toolchain and sysroot install==&lt;br /&gt;
This is documented on the QtonPi wiki but basically after you have downloaded the qtonpi tarball extract the three files within.&lt;br /&gt;
Then as root extract [opt-qt5-current.tar.bz2] and [toolchain-and-sysroot-armv5tel.tar.bz2] &lt;br /&gt;
 $ cd /&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/opt-qt5-current.tar.bz2&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/toolchain-and-sysroot-armv5tel.tar.bz2&lt;br /&gt;
&lt;br /&gt;
===Qt creator===&lt;br /&gt;
The tarball comes with a recent version of qtcreator, but since then qt2.5 RC has come out, Should be safe enough to use that instead. Just install that by executing the .bin installer. &#039;&#039;Hold that thought, qt2.5 creator RC doesn&#039;t have the deploy steps set up&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Within Qt creator you need to point it at your cross tool chain compiler+debugger:&lt;br /&gt;
#Tools-&amp;gt;Options-&amp;gt;Build&amp;amp;Run then Tool Chains&lt;br /&gt;
#then select add, in the drop-down pick GCC&lt;br /&gt;
#Select GCC and browse for compiler to&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gcc&lt;br /&gt;
and for the debugger&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gdb&lt;br /&gt;
Save these selections by clicking Apply and OK&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi Setup==&lt;br /&gt;
===Virtual using qemu===&lt;br /&gt;
As I don&#039;t have a rpi yet I used qemu to do some initial testing.&lt;br /&gt;
My setup was a 12.04 VM.&lt;br /&gt;
You can either install qemu&lt;br /&gt;
 sudo apt-get install qemu-system&lt;br /&gt;
Or you can build qemu from git. You only need to do this if the qemu on your distro doesn&#039;t support the Broadcom SOC (ARM1176 core) on the Pi.&lt;br /&gt;
In order to boot your image you will need a suitable kernel for your emulator, there is one available here http://dl.dropbox.com/u/45842273/zImage_3.1.9 &lt;br /&gt;
Boot your virtual Pi &lt;br /&gt;
 qemu-system-arm -kernel kernel-qemu -cpu arm1176 -m 256 -M versatilepb -no-reboot -serial stdio -append &amp;quot;root=/dev/sda2 rw panic=1&amp;quot; qtonpi-sdcard-0.2.img -redir tcp:5022::22&lt;br /&gt;
&lt;br /&gt;
add&lt;br /&gt;
 console=ttyAMA0&lt;br /&gt;
to the -append param to have the boot console re-directed to the terminal.&lt;br /&gt;
&lt;br /&gt;
the -redir tcp:5022::22 redirects port 22 (ssh) on the virtual Pi to port 5022 on the host enabling you to ssh in.&lt;br /&gt;
 ssh pi@localhost -p5022&lt;br /&gt;
===Raspberry Pi Setup===&lt;br /&gt;
I used the image I was using above and wrote it to an SD card.&#039;&#039;If you are on windows make sure your machine can handle larger cards&#039;&#039;&lt;br /&gt;
By default the qtonpi release doesn&#039;t have the network if enabled. On each boot you can run&lt;br /&gt;
 ifup eth0&lt;br /&gt;
or&lt;br /&gt;
 dhclient eth0&lt;br /&gt;
or&lt;br /&gt;
 just edit /etc/sysconfig/network-scripts/ifcfg-eth0 and set the ONBOOT option equal to YES and be done with it.&lt;br /&gt;
&lt;br /&gt;
Also you need to set the time and date after each boot - no RTC on the rPi&lt;br /&gt;
&lt;br /&gt;
==Code Changes==&lt;br /&gt;
According to the current Qt Documentation adding&lt;br /&gt;
 greaterThan(QT_MAJOR_VERSION, 4) {&lt;br /&gt;
        QT += widgets&lt;br /&gt;
        QT += quick1&lt;br /&gt;
    } else {&lt;br /&gt;
        QT += declarative&lt;br /&gt;
    }&lt;br /&gt;
to the pro file loads the correct modules for both Qt4/Qt5.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;04/07/2012&#039;&#039; - see ticket [http://svn.linuxmce.org/trac.cgi/ticket/1497 trac #1497] code checked into svn.&lt;br /&gt;
&lt;br /&gt;
===&amp;quot;Useful&amp;quot; Qt links===&lt;br /&gt;
http://qt-project.org/wiki/Transition_from_Qt_4.x_to_Qt5&lt;br /&gt;
&lt;br /&gt;
https://qt-project.org/wiki/New_Signal_Slot_Syntax&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/Qt-5Features&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/QML1-vs-QML2&lt;br /&gt;
&lt;br /&gt;
A recent but good addition http://doc-snapshot.qt-project.org/5.0/qtquick-porting-qt5.html#porting-c-code&lt;br /&gt;
&lt;br /&gt;
I don&#039;t know whether these apply to how Qt5 will be when it is released, but they don&#039;t completely correspond to it in its current state, so don&#039;t believe all you read.&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi distros==&lt;br /&gt;
Looking at http://elinux.org/RPi_Distributions there are quite a few to choose from.&lt;br /&gt;
&lt;br /&gt;
Which is the best fit? I don&#039;t know.&lt;br /&gt;
&lt;br /&gt;
I&#039;m starting with QtonPi but I don&#039;t know if a full fedora release is necessary.&lt;br /&gt;
&#039;&#039;This is actually a trimmed down fedora release no X, graphics written direct to fb&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Mer/Meego might be a good fit too.&lt;br /&gt;
&lt;br /&gt;
=qOrbiter on Pi=&lt;br /&gt;
==QtonPi 0.2 image==&lt;br /&gt;
trimmed down fedora remix with qt5 pre-installed, no gui.&lt;br /&gt;
====Status====&lt;br /&gt;
&#039;&#039;28/05/2012&#039;&#039; - Unfortunately I have not been able to get my compiled qOrbiter to run on my virtual setup.&lt;br /&gt;
Depending on the combination of kernel I use and/or SD image I either get an illegal instruction or and error creating a vchiq instance.&lt;br /&gt;
&lt;br /&gt;
And given that the vchiq lib stuff is to do with the GPU, which is initialised in firmware, this may be a bit of an impass until I get actual hardware.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;30/05/2012&#039;&#039; - Have just received my rPi and my previously compiled qOrbiter starts and gets past the vchiq/illegal instruction I had.&lt;br /&gt;
I have other issues before I get it going but all going in the right direction.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;02/06/2012&#039;&#039; - qOrbiter splash screen loads, communicates with dcerouter, gets config - then boom my network dies. I don&#039;t know if its rPi specific or some porting issue with qOrbiter. I see &#039;&#039;smsc95xx 1-1.1:1.0: eth0: kevent 2 may have been dropped&#039;&#039; scroll past me. My ssh connection dies as a result so I need to be logged in on the rPi. Needs more investigation...&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;06/06/2012&#039;&#039; - got past n/w problem, now home screen loads. Also had to disable qml screen saver. The shader effect component is supposed to be available via QtQuick 2.0 and not need the labs plugin, but this appears not to be the case. It is likely it is just not in the snapshot yet.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;08/06/2012&#039;&#039; - It seems there is no mouse support in the current 0.2 qtonpi SD image. This is a deal breaker until 0.3 image is released. Mouse support has been checked into git so is available if we roll our own qt5.&lt;br /&gt;
&lt;br /&gt;
==Next image - Debian Wheezy==&lt;br /&gt;
Investigating a debian wheezy port at the moment - should eek out a bit more speed using hardfp. There are qt50-snapshots available for the target. May need to set up a separate toolchain.&lt;br /&gt;
===Status===&lt;br /&gt;
&#039;&#039;11/06/2012&#039;&#039; - existing qOrbiter won&#039;t run on target, need to link against newer qt5 sysroot on host.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;19/06/2012&#039;&#039; - have rebuilt and linked qOrbiter against qt5 from git. Up and running again on my Raspberry Pi. The default CPU/GPU split of 192/64 allows qOrbiter to run, lower one - 244/32 gives an error creating the display surface. Will bump up split to 128/128 if I get display issues.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;22/06/2012&#039;&#039; - as I thought, I had to move the split to 128/128 and now I get no GL memory errors and the background effects work on the home screen. I need to find out why switching threads away from the qml engine is failing.&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31693</id>
		<title>RaspberryPi qOrbiter</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31693"/>
		<updated>2012-07-13T14:18:51Z</updated>

		<summary type="html">&lt;p&gt;Coley: /* &amp;quot;Useful&amp;quot; Qt links */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Device Specification==&lt;br /&gt;
-The Raspberry Pi is an ARM based computer the size of a credit card.  700Mhz, 256MB RAM, Ethernet, 2xUSB, GPIO&lt;br /&gt;
&lt;br /&gt;
-256MB of RAM is insufficient to build lmce.  MakeRelease and MakeRelease_PrepFiles both fail with out of memory errors due to the limited memory available on the RPi.&lt;br /&gt;
-Cross-compiling will be required.  More notes to follow.&lt;br /&gt;
&lt;br /&gt;
==Cross Compilation setup==&lt;br /&gt;
Initially this section will have information specific to getting Qt on Pi going. Its pre-packaged and fairly easy to install.&lt;br /&gt;
&lt;br /&gt;
At the time of writing Qt on Pi tarball is at version 0.2.&lt;br /&gt;
Get the tarball here http://www.raspberrypi.org/downloads at the bottom of the page. This has a premade SD image plus the toolchain and sysroot install required for cross compilation.&lt;br /&gt;
&lt;br /&gt;
===If you are about to install this on your current machine with a working Qt development environment DON&#039;T===&lt;br /&gt;
You will need to either set up a VM or a chroot environment as the qt5 shipped with this image isn&#039;t setup to install alongside an x86 install. They plan on having these play nice in future releases.&lt;br /&gt;
&lt;br /&gt;
==Qt5, Toolchain and sysroot install==&lt;br /&gt;
This is documented on the QtonPi wiki but basically after you have downloaded the qtonpi tarball extract the three files within.&lt;br /&gt;
Then as root extract [opt-qt5-current.tar.bz2] and [toolchain-and-sysroot-armv5tel.tar.bz2] &lt;br /&gt;
 $ cd /&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/opt-qt5-current.tar.bz2&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/toolchain-and-sysroot-armv5tel.tar.bz2&lt;br /&gt;
&lt;br /&gt;
===Qt creator===&lt;br /&gt;
The tarball comes with a recent version of qtcreator, but since then qt2.5 RC has come out, Should be safe enough to use that instead. Just install that by executing the .bin installer. &#039;&#039;Hold that thought, qt2.5 creator RC doesn&#039;t have the deploy steps set up&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Within Qt creator you need to point it at your cross tool chain compiler+debugger:&lt;br /&gt;
#Tools-&amp;gt;Options-&amp;gt;Build&amp;amp;Run then Tool Chains&lt;br /&gt;
#then select add, in the drop-down pick GCC&lt;br /&gt;
#Select GCC and browse for compiler to&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gcc&lt;br /&gt;
and for the debugger&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gdb&lt;br /&gt;
Save these selections by clicking Apply and OK&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi Setup==&lt;br /&gt;
===Virtual using qemu===&lt;br /&gt;
As I don&#039;t have a rpi yet I used qemu to do some initial testing.&lt;br /&gt;
My setup was a 12.04 VM.&lt;br /&gt;
You can either install qemu&lt;br /&gt;
 sudo apt-get install qemu-system&lt;br /&gt;
Or you can build qemu from git. You only need to do this if the qemu on your distro doesn&#039;t support the Broadcom SOC (ARM1176 core) on the Pi.&lt;br /&gt;
In order to boot your image you will need a suitable kernel for your emulator, there is one available here http://dl.dropbox.com/u/45842273/zImage_3.1.9 &lt;br /&gt;
Boot your virtual Pi &lt;br /&gt;
 qemu-system-arm -kernel kernel-qemu -cpu arm1176 -m 256 -M versatilepb -no-reboot -serial stdio -append &amp;quot;root=/dev/sda2 rw panic=1&amp;quot; qtonpi-sdcard-0.2.img -redir tcp:5022::22&lt;br /&gt;
&lt;br /&gt;
add&lt;br /&gt;
 console=ttyAMA0&lt;br /&gt;
to the -append param to have the boot console re-directed to the terminal.&lt;br /&gt;
&lt;br /&gt;
the -redir tcp:5022::22 redirects port 22 (ssh) on the virtual Pi to port 5022 on the host enabling you to ssh in.&lt;br /&gt;
 ssh pi@localhost -p5022&lt;br /&gt;
===Raspberry Pi Setup===&lt;br /&gt;
I used the image I was using above and wrote it to an SD card.&#039;&#039;If you are on windows make sure your machine can handle larger cards&#039;&#039;&lt;br /&gt;
By default the qtonpi release doesn&#039;t have the network if enabled. On each boot you can run&lt;br /&gt;
 ifup eth0&lt;br /&gt;
or&lt;br /&gt;
 dhclient eth0&lt;br /&gt;
or&lt;br /&gt;
 just edit /etc/sysconfig/network-scripts/ifcfg-eth0 and set the ONBOOT option equal to YES and be done with it.&lt;br /&gt;
&lt;br /&gt;
Also you need to set the time and date after each boot - no RTC on the rPi&lt;br /&gt;
&lt;br /&gt;
==Code Changes==&lt;br /&gt;
According to the current Qt Documentation adding&lt;br /&gt;
 greaterThan(QT_MAJOR_VERSION, 4) {&lt;br /&gt;
        QT += widgets&lt;br /&gt;
        QT += quick1&lt;br /&gt;
    } else {&lt;br /&gt;
        QT += declarative&lt;br /&gt;
    }&lt;br /&gt;
to the pro file loads the correct modules for both Qt4/Qt5.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;04/07/2012&#039;&#039; - see ticket [http://svn.linuxmce.org/trac.cgi/ticket/1497 trac #1497] code checked into svn.&lt;br /&gt;
&lt;br /&gt;
===&amp;quot;Useful&amp;quot; Qt links===&lt;br /&gt;
http://qt-project.org/wiki/Transition_from_Qt_4.x_to_Qt5&lt;br /&gt;
&lt;br /&gt;
https://qt-project.org/wiki/New_Signal_Slot_Syntax&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/Qt-5Features&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/QML1-vs-QML2&lt;br /&gt;
&lt;br /&gt;
A recent but good addition http://doc-snapshot.qt-project.org/5.0/qtquick-porting-qt5.html#porting-c-code&lt;br /&gt;
&lt;br /&gt;
I don&#039;t know whether these apply to how Qt5 will be when it is released, but they don&#039;t completely correspond to it in its current state, so don&#039;t believe all you read.&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi distros==&lt;br /&gt;
Looking at http://elinux.org/RPi_Distributions there are quite a few to choose from.&lt;br /&gt;
&lt;br /&gt;
Which is the best fit? I don&#039;t know.&lt;br /&gt;
&lt;br /&gt;
I&#039;m starting with QtonPi but I don&#039;t know if a full fedora release is necessary.&lt;br /&gt;
&#039;&#039;This is actually a trimmed down fedora release no X, graphics written direct to fb&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Mer/Meego might be a good fit too.&lt;br /&gt;
&lt;br /&gt;
=qOrbiter on Pi=&lt;br /&gt;
==QtonPi 0.2 image==&lt;br /&gt;
trimmed down fedora remix with qt5 pre-installed, no gui.&lt;br /&gt;
====Status====&lt;br /&gt;
&#039;&#039;28/05/2012&#039;&#039; - Unfortunately I have not been able to get my compiled qOrbiter to run on my virtual setup.&lt;br /&gt;
Depending on the combination of kernel I use and/or SD image I either get an illegal instruction or and error creating a vchiq instance.&lt;br /&gt;
&lt;br /&gt;
And given that the vchiq lib stuff is to do with the GPU, which is initialised in firmware, this may be a bit of an impass until I get actual hardware.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;30/05/2012&#039;&#039; - Have just received my rPi and my previously compiled qOrbiter starts and gets past the vchiq/illegal instruction I had.&lt;br /&gt;
I have other issues before I get it going but all going in the right direction.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;02/06/2012&#039;&#039; - qOrbiter splash screen loads, communicates with dcerouter, gets config - then boom my network dies. I don&#039;t know if its rPi specific or some porting issue with qOrbiter. I see &#039;&#039;smsc95xx 1-1.1:1.0: eth0: kevent 2 may have been dropped&#039;&#039; scroll past me. My ssh connection dies as a result so I need to be logged in on the rPi. Needs more investigation...&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;06/06/2012&#039;&#039; - got past n/w problem, now home screen loads. Also had to disable qml screen saver. The shader effect component is supposed to be available via QtQuick 2.0 and not need the labs plugin, but this appears not to be the case. It is likely it is just not in the snapshot yet.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;08/06/2012&#039;&#039; - It seems there is no mouse support in the current 0.2 qtonpi SD image. This is a deal breaker until 0.3 image is released. Mouse support has been checked into git so is available if we roll our own qt5.&lt;br /&gt;
&lt;br /&gt;
==Next image - Debian Wheezy==&lt;br /&gt;
Investigating a debian wheezy port at the moment - should eek out a bit more speed using hardfp. There are qt50-snapshots available for the target. May need to set up a separate toolchain.&lt;br /&gt;
===Status===&lt;br /&gt;
&#039;&#039;11/06/2012&#039;&#039; - existing qOrbiter won&#039;t run on target, need to link against newer qt5 sysroot on host.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;19/06/2012&#039;&#039; - have rebuilt and linked qOrbiter against qt5 from git. Up and running again on my Raspberry Pi. The default CPU/GPU split of 192/64 allows qOrbiter to run, lower one - 244/32 gives an error creating the display surface. Will bump up split to 128/128 if I get display issues.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;22/06/2012&#039;&#039; - as I thought, I had to move the split to 128/128 and now I get no GL memory errors and the background effects work on the home screen. I need to find out why switching threads away from the qml engine is failing.&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31679</id>
		<title>RaspberryPi qOrbiter</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31679"/>
		<updated>2012-07-04T16:57:09Z</updated>

		<summary type="html">&lt;p&gt;Coley: code checked into svn&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Device Specification==&lt;br /&gt;
-The Raspberry Pi is an ARM based computer the size of a credit card.  700Mhz, 256MB RAM, Ethernet, 2xUSB, GPIO&lt;br /&gt;
&lt;br /&gt;
-256MB of RAM is insufficient to build lmce.  MakeRelease and MakeRelease_PrepFiles both fail with out of memory errors due to the limited memory available on the RPi.&lt;br /&gt;
-Cross-compiling will be required.  More notes to follow.&lt;br /&gt;
&lt;br /&gt;
==Cross Compilation setup==&lt;br /&gt;
Initially this section will have information specific to getting Qt on Pi going. Its pre-packaged and fairly easy to install.&lt;br /&gt;
&lt;br /&gt;
At the time of writing Qt on Pi tarball is at version 0.2.&lt;br /&gt;
Get the tarball here http://www.raspberrypi.org/downloads at the bottom of the page. This has a premade SD image plus the toolchain and sysroot install required for cross compilation.&lt;br /&gt;
&lt;br /&gt;
===If you are about to install this on your current machine with a working Qt development environment DON&#039;T===&lt;br /&gt;
You will need to either set up a VM or a chroot environment as the qt5 shipped with this image isn&#039;t setup to install alongside an x86 install. They plan on having these play nice in future releases.&lt;br /&gt;
&lt;br /&gt;
==Qt5, Toolchain and sysroot install==&lt;br /&gt;
This is documented on the QtonPi wiki but basically after you have downloaded the qtonpi tarball extract the three files within.&lt;br /&gt;
Then as root extract [opt-qt5-current.tar.bz2] and [toolchain-and-sysroot-armv5tel.tar.bz2] &lt;br /&gt;
 $ cd /&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/opt-qt5-current.tar.bz2&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/toolchain-and-sysroot-armv5tel.tar.bz2&lt;br /&gt;
&lt;br /&gt;
===Qt creator===&lt;br /&gt;
The tarball comes with a recent version of qtcreator, but since then qt2.5 RC has come out, Should be safe enough to use that instead. Just install that by executing the .bin installer. &#039;&#039;Hold that thought, qt2.5 creator RC doesn&#039;t have the deploy steps set up&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Within Qt creator you need to point it at your cross tool chain compiler+debugger:&lt;br /&gt;
#Tools-&amp;gt;Options-&amp;gt;Build&amp;amp;Run then Tool Chains&lt;br /&gt;
#then select add, in the drop-down pick GCC&lt;br /&gt;
#Select GCC and browse for compiler to&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gcc&lt;br /&gt;
and for the debugger&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gdb&lt;br /&gt;
Save these selections by clicking Apply and OK&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi Setup==&lt;br /&gt;
===Virtual using qemu===&lt;br /&gt;
As I don&#039;t have a rpi yet I used qemu to do some initial testing.&lt;br /&gt;
My setup was a 12.04 VM.&lt;br /&gt;
You can either install qemu&lt;br /&gt;
 sudo apt-get install qemu-system&lt;br /&gt;
Or you can build qemu from git. You only need to do this if the qemu on your distro doesn&#039;t support the Broadcom SOC (ARM1176 core) on the Pi.&lt;br /&gt;
In order to boot your image you will need a suitable kernel for your emulator, there is one available here http://dl.dropbox.com/u/45842273/zImage_3.1.9 &lt;br /&gt;
Boot your virtual Pi &lt;br /&gt;
 qemu-system-arm -kernel kernel-qemu -cpu arm1176 -m 256 -M versatilepb -no-reboot -serial stdio -append &amp;quot;root=/dev/sda2 rw panic=1&amp;quot; qtonpi-sdcard-0.2.img -redir tcp:5022::22&lt;br /&gt;
&lt;br /&gt;
add&lt;br /&gt;
 console=ttyAMA0&lt;br /&gt;
to the -append param to have the boot console re-directed to the terminal.&lt;br /&gt;
&lt;br /&gt;
the -redir tcp:5022::22 redirects port 22 (ssh) on the virtual Pi to port 5022 on the host enabling you to ssh in.&lt;br /&gt;
 ssh pi@localhost -p5022&lt;br /&gt;
===Raspberry Pi Setup===&lt;br /&gt;
I used the image I was using above and wrote it to an SD card.&#039;&#039;If you are on windows make sure your machine can handle larger cards&#039;&#039;&lt;br /&gt;
By default the qtonpi release doesn&#039;t have the network if enabled. On each boot you can run&lt;br /&gt;
 ifup eth0&lt;br /&gt;
or&lt;br /&gt;
 dhclient eth0&lt;br /&gt;
or&lt;br /&gt;
 just edit /etc/sysconfig/network-scripts/ifcfg-eth0 and set the ONBOOT option equal to YES and be done with it.&lt;br /&gt;
&lt;br /&gt;
Also you need to set the time and date after each boot - no RTC on the rPi&lt;br /&gt;
&lt;br /&gt;
==Code Changes==&lt;br /&gt;
According to the current Qt Documentation adding&lt;br /&gt;
 greaterThan(QT_MAJOR_VERSION, 4) {&lt;br /&gt;
        QT += widgets&lt;br /&gt;
        QT += quick1&lt;br /&gt;
    } else {&lt;br /&gt;
        QT += declarative&lt;br /&gt;
    }&lt;br /&gt;
to the pro file loads the correct modules for both Qt4/Qt5.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;04/07/2012&#039;&#039; - see ticket [http://svn.linuxmce.org/trac.cgi/ticket/1497 trac #1497] code checked into svn.&lt;br /&gt;
&lt;br /&gt;
===&amp;quot;Useful&amp;quot; Qt links===&lt;br /&gt;
http://qt-project.org/wiki/Transition_from_Qt_4.x_to_Qt5&lt;br /&gt;
&lt;br /&gt;
https://qt-project.org/wiki/New_Signal_Slot_Syntax&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/Qt-5Features&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/QML1-vs-QML2&lt;br /&gt;
&lt;br /&gt;
I don&#039;t know whether these apply to how Qt5 will be when it is released, but they don&#039;t completely correspond to it in its current state, so don&#039;t believe all you read.&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi distros==&lt;br /&gt;
Looking at http://elinux.org/RPi_Distributions there are quite a few to choose from.&lt;br /&gt;
&lt;br /&gt;
Which is the best fit? I don&#039;t know.&lt;br /&gt;
&lt;br /&gt;
I&#039;m starting with QtonPi but I don&#039;t know if a full fedora release is necessary.&lt;br /&gt;
&#039;&#039;This is actually a trimmed down fedora release no X, graphics written direct to fb&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Mer/Meego might be a good fit too.&lt;br /&gt;
&lt;br /&gt;
=qOrbiter on Pi=&lt;br /&gt;
==QtonPi 0.2 image==&lt;br /&gt;
trimmed down fedora remix with qt5 pre-installed, no gui.&lt;br /&gt;
====Status====&lt;br /&gt;
&#039;&#039;28/05/2012&#039;&#039; - Unfortunately I have not been able to get my compiled qOrbiter to run on my virtual setup.&lt;br /&gt;
Depending on the combination of kernel I use and/or SD image I either get an illegal instruction or and error creating a vchiq instance.&lt;br /&gt;
&lt;br /&gt;
And given that the vchiq lib stuff is to do with the GPU, which is initialised in firmware, this may be a bit of an impass until I get actual hardware.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;30/05/2012&#039;&#039; - Have just received my rPi and my previously compiled qOrbiter starts and gets past the vchiq/illegal instruction I had.&lt;br /&gt;
I have other issues before I get it going but all going in the right direction.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;02/06/2012&#039;&#039; - qOrbiter splash screen loads, communicates with dcerouter, gets config - then boom my network dies. I don&#039;t know if its rPi specific or some porting issue with qOrbiter. I see &#039;&#039;smsc95xx 1-1.1:1.0: eth0: kevent 2 may have been dropped&#039;&#039; scroll past me. My ssh connection dies as a result so I need to be logged in on the rPi. Needs more investigation...&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;06/06/2012&#039;&#039; - got past n/w problem, now home screen loads. Also had to disable qml screen saver. The shader effect component is supposed to be available via QtQuick 2.0 and not need the labs plugin, but this appears not to be the case. It is likely it is just not in the snapshot yet.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;08/06/2012&#039;&#039; - It seems there is no mouse support in the current 0.2 qtonpi SD image. This is a deal breaker until 0.3 image is released. Mouse support has been checked into git so is available if we roll our own qt5.&lt;br /&gt;
&lt;br /&gt;
==Next image - Debian Wheezy==&lt;br /&gt;
Investigating a debian wheezy port at the moment - should eek out a bit more speed using hardfp. There are qt50-snapshots available for the target. May need to set up a separate toolchain.&lt;br /&gt;
===Status===&lt;br /&gt;
&#039;&#039;11/06/2012&#039;&#039; - existing qOrbiter won&#039;t run on target, need to link against newer qt5 sysroot on host.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;19/06/2012&#039;&#039; - have rebuilt and linked qOrbiter against qt5 from git. Up and running again on my Raspberry Pi. The default CPU/GPU split of 192/64 allows qOrbiter to run, lower one - 244/32 gives an error creating the display surface. Will bump up split to 128/128 if I get display issues.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;22/06/2012&#039;&#039; - as I thought, I had to move the split to 128/128 and now I get no GL memory errors and the background effects work on the home screen. I need to find out why switching threads away from the qml engine is failing.&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31651</id>
		<title>RaspberryPi qOrbiter</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31651"/>
		<updated>2012-06-22T11:48:04Z</updated>

		<summary type="html">&lt;p&gt;Coley: /* &amp;quot;Useful&amp;quot; Qt links */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Device Specification==&lt;br /&gt;
-The Raspberry Pi is an ARM based computer the size of a credit card.  700Mhz, 256MB RAM, Ethernet, 2xUSB, GPIO&lt;br /&gt;
&lt;br /&gt;
-256MB of RAM is insufficient to build lmce.  MakeRelease and MakeRelease_PrepFiles both fail with out of memory errors due to the limited memory available on the RPi.&lt;br /&gt;
-Cross-compiling will be required.  More notes to follow.&lt;br /&gt;
&lt;br /&gt;
==Cross Compilation setup==&lt;br /&gt;
Initially this section will have information specific to getting Qt on Pi going. Its pre-packaged and fairly easy to install.&lt;br /&gt;
&lt;br /&gt;
At the time of writing Qt on Pi tarball is at version 0.2.&lt;br /&gt;
Get the tarball here http://www.raspberrypi.org/downloads at the bottom of the page. This has a premade SD image plus the toolchain and sysroot install required for cross compilation.&lt;br /&gt;
&lt;br /&gt;
===If you are about to install this on your current machine with a working Qt development environment DON&#039;T===&lt;br /&gt;
You will need to either set up a VM or a chroot environment as the qt5 shipped with this image isn&#039;t setup to install alongside an x86 install. They plan on having these play nice in future releases.&lt;br /&gt;
&lt;br /&gt;
==Qt5, Toolchain and sysroot install==&lt;br /&gt;
This is documented on the QtonPi wiki but basically after you have downloaded the qtonpi tarball extract the three files within.&lt;br /&gt;
Then as root extract [opt-qt5-current.tar.bz2] and [toolchain-and-sysroot-armv5tel.tar.bz2] &lt;br /&gt;
 $ cd /&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/opt-qt5-current.tar.bz2&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/toolchain-and-sysroot-armv5tel.tar.bz2&lt;br /&gt;
&lt;br /&gt;
===Qt creator===&lt;br /&gt;
The tarball comes with a recent version of qtcreator, but since then qt2.5 RC has come out, Should be safe enough to use that instead. Just install that by executing the .bin installer. &#039;&#039;Hold that thought, qt2.5 creator RC doesn&#039;t have the deploy steps set up&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Within Qt creator you need to point it at your cross tool chain compiler+debugger:&lt;br /&gt;
#Tools-&amp;gt;Options-&amp;gt;Build&amp;amp;Run then Tool Chains&lt;br /&gt;
#then select add, in the drop-down pick GCC&lt;br /&gt;
#Select GCC and browse for compiler to&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gcc&lt;br /&gt;
and for the debugger&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gdb&lt;br /&gt;
Save these selections by clicking Apply and OK&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi Setup==&lt;br /&gt;
===Virtual using qemu===&lt;br /&gt;
As I don&#039;t have a rpi yet I used qemu to do some initial testing.&lt;br /&gt;
My setup was a 12.04 VM.&lt;br /&gt;
You can either install qemu&lt;br /&gt;
 sudo apt-get install qemu-system&lt;br /&gt;
Or you can build qemu from git. You only need to do this if the qemu on your distro doesn&#039;t support the Broadcom SOC (ARM1176 core) on the Pi.&lt;br /&gt;
In order to boot your image you will need a suitable kernel for your emulator, there is one available here http://dl.dropbox.com/u/45842273/zImage_3.1.9 &lt;br /&gt;
Boot your virtual Pi &lt;br /&gt;
 qemu-system-arm -kernel kernel-qemu -cpu arm1176 -m 256 -M versatilepb -no-reboot -serial stdio -append &amp;quot;root=/dev/sda2 rw panic=1&amp;quot; qtonpi-sdcard-0.2.img -redir tcp:5022::22&lt;br /&gt;
&lt;br /&gt;
add&lt;br /&gt;
 console=ttyAMA0&lt;br /&gt;
to the -append param to have the boot console re-directed to the terminal.&lt;br /&gt;
&lt;br /&gt;
the -redir tcp:5022::22 redirects port 22 (ssh) on the virtual Pi to port 5022 on the host enabling you to ssh in.&lt;br /&gt;
 ssh pi@localhost -p5022&lt;br /&gt;
===Raspberry Pi Setup===&lt;br /&gt;
I used the image I was using above and wrote it to an SD card.&#039;&#039;If you are on windows make sure your machine can handle larger cards&#039;&#039;&lt;br /&gt;
By default the qtonpi release doesn&#039;t have the network if enabled. On each boot you can run&lt;br /&gt;
 ifup eth0&lt;br /&gt;
or&lt;br /&gt;
 dhclient eth0&lt;br /&gt;
or&lt;br /&gt;
 just edit /etc/sysconfig/network-scripts/ifcfg-eth0 and set the ONBOOT option equal to YES and be done with it.&lt;br /&gt;
&lt;br /&gt;
Also you need to set the time and date after each boot - no RTC on the rPi&lt;br /&gt;
&lt;br /&gt;
==Code Changes==&lt;br /&gt;
According to the current Qt Documentation adding&lt;br /&gt;
 greaterThan(QT_MAJOR_VERSION, 4) {&lt;br /&gt;
        QT += widgets&lt;br /&gt;
        QT += quick1&lt;br /&gt;
    } else {&lt;br /&gt;
        QT += declarative&lt;br /&gt;
    }&lt;br /&gt;
to the pro file loads the correct modules for both Qt4/Qt5.&lt;br /&gt;
At the moment my code and svn differ and not in a nice way - once I get everything #ifdef&#039;d into place I&#039;ll either stick a patch here or check it in with golgoj4 approval :)&lt;br /&gt;
&lt;br /&gt;
===&amp;quot;Useful&amp;quot; Qt links===&lt;br /&gt;
http://qt-project.org/wiki/Transition_from_Qt_4.x_to_Qt5&lt;br /&gt;
&lt;br /&gt;
https://qt-project.org/wiki/New_Signal_Slot_Syntax&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/Qt-5Features&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/QML1-vs-QML2&lt;br /&gt;
&lt;br /&gt;
I don&#039;t know whether these apply to how Qt5 will be when it is released, but they don&#039;t completely correspond to it in its current state, so don&#039;t believe all you read.&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi distros==&lt;br /&gt;
Looking at http://elinux.org/RPi_Distributions there are quite a few to choose from.&lt;br /&gt;
&lt;br /&gt;
Which is the best fit? I don&#039;t know.&lt;br /&gt;
&lt;br /&gt;
I&#039;m starting with QtonPi but I don&#039;t know if a full fedora release is necessary.&lt;br /&gt;
&#039;&#039;This is actually a trimmed down fedora release no X, graphics written direct to fb&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Mer/Meego might be a good fit too.&lt;br /&gt;
&lt;br /&gt;
=qOrbiter on Pi=&lt;br /&gt;
==QtonPi 0.2 image==&lt;br /&gt;
trimmed down fedora remix with qt5 pre-installed, no gui.&lt;br /&gt;
====Status====&lt;br /&gt;
&#039;&#039;28/05/2012&#039;&#039; - Unfortunately I have not been able to get my compiled qOrbiter to run on my virtual setup.&lt;br /&gt;
Depending on the combination of kernel I use and/or SD image I either get an illegal instruction or and error creating a vchiq instance.&lt;br /&gt;
&lt;br /&gt;
And given that the vchiq lib stuff is to do with the GPU, which is initialised in firmware, this may be a bit of an impass until I get actual hardware.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;30/05/2012&#039;&#039; - Have just received my rPi and my previously compiled qOrbiter starts and gets past the vchiq/illegal instruction I had.&lt;br /&gt;
I have other issues before I get it going but all going in the right direction.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;02/06/2012&#039;&#039; - qOrbiter splash screen loads, communicates with dcerouter, gets config - then boom my network dies. I don&#039;t know if its rPi specific or some porting issue with qOrbiter. I see &#039;&#039;smsc95xx 1-1.1:1.0: eth0: kevent 2 may have been dropped&#039;&#039; scroll past me. My ssh connection dies as a result so I need to be logged in on the rPi. Needs more investigation...&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;06/06/2012&#039;&#039; - got past n/w problem, now home screen loads. Also had to disable qml screen saver. The shader effect component is supposed to be available via QtQuick 2.0 and not need the labs plugin, but this appears not to be the case. It is likely it is just not in the snapshot yet.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;08/06/2012&#039;&#039; - It seems there is no mouse support in the current 0.2 qtonpi SD image. This is a deal breaker until 0.3 image is released. Mouse support has been checked into git so is available if we roll our own qt5.&lt;br /&gt;
&lt;br /&gt;
==Next image - Debian Wheezy==&lt;br /&gt;
Investigating a debian wheezy port at the moment - should eek out a bit more speed using hardfp. There are qt50-snapshots available for the target. May need to set up a separate toolchain.&lt;br /&gt;
===Status===&lt;br /&gt;
&#039;&#039;11/06/2012&#039;&#039; - existing qOrbiter won&#039;t run on target, need to link against newer qt5 sysroot on host.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;19/06/2012&#039;&#039; - have rebuilt and linked qOrbiter against qt5 from git. Up and running again on my Raspberry Pi. The default CPU/GPU split of 192/64 allows qOrbiter to run, lower one - 244/32 gives an error creating the display surface. Will bump up split to 128/128 if I get display issues.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;22/06/2012&#039;&#039; - as I thought, I had to move the split to 128/128 and now I get no GL memory errors and the background effects work on the home screen. I need to find out why switching threads away from the qml engine is failing.&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31650</id>
		<title>RaspberryPi qOrbiter</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31650"/>
		<updated>2012-06-22T11:44:51Z</updated>

		<summary type="html">&lt;p&gt;Coley: Status Update&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Device Specification==&lt;br /&gt;
-The Raspberry Pi is an ARM based computer the size of a credit card.  700Mhz, 256MB RAM, Ethernet, 2xUSB, GPIO&lt;br /&gt;
&lt;br /&gt;
-256MB of RAM is insufficient to build lmce.  MakeRelease and MakeRelease_PrepFiles both fail with out of memory errors due to the limited memory available on the RPi.&lt;br /&gt;
-Cross-compiling will be required.  More notes to follow.&lt;br /&gt;
&lt;br /&gt;
==Cross Compilation setup==&lt;br /&gt;
Initially this section will have information specific to getting Qt on Pi going. Its pre-packaged and fairly easy to install.&lt;br /&gt;
&lt;br /&gt;
At the time of writing Qt on Pi tarball is at version 0.2.&lt;br /&gt;
Get the tarball here http://www.raspberrypi.org/downloads at the bottom of the page. This has a premade SD image plus the toolchain and sysroot install required for cross compilation.&lt;br /&gt;
&lt;br /&gt;
===If you are about to install this on your current machine with a working Qt development environment DON&#039;T===&lt;br /&gt;
You will need to either set up a VM or a chroot environment as the qt5 shipped with this image isn&#039;t setup to install alongside an x86 install. They plan on having these play nice in future releases.&lt;br /&gt;
&lt;br /&gt;
==Qt5, Toolchain and sysroot install==&lt;br /&gt;
This is documented on the QtonPi wiki but basically after you have downloaded the qtonpi tarball extract the three files within.&lt;br /&gt;
Then as root extract [opt-qt5-current.tar.bz2] and [toolchain-and-sysroot-armv5tel.tar.bz2] &lt;br /&gt;
 $ cd /&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/opt-qt5-current.tar.bz2&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/toolchain-and-sysroot-armv5tel.tar.bz2&lt;br /&gt;
&lt;br /&gt;
===Qt creator===&lt;br /&gt;
The tarball comes with a recent version of qtcreator, but since then qt2.5 RC has come out, Should be safe enough to use that instead. Just install that by executing the .bin installer. &#039;&#039;Hold that thought, qt2.5 creator RC doesn&#039;t have the deploy steps set up&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Within Qt creator you need to point it at your cross tool chain compiler+debugger:&lt;br /&gt;
#Tools-&amp;gt;Options-&amp;gt;Build&amp;amp;Run then Tool Chains&lt;br /&gt;
#then select add, in the drop-down pick GCC&lt;br /&gt;
#Select GCC and browse for compiler to&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gcc&lt;br /&gt;
and for the debugger&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gdb&lt;br /&gt;
Save these selections by clicking Apply and OK&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi Setup==&lt;br /&gt;
===Virtual using qemu===&lt;br /&gt;
As I don&#039;t have a rpi yet I used qemu to do some initial testing.&lt;br /&gt;
My setup was a 12.04 VM.&lt;br /&gt;
You can either install qemu&lt;br /&gt;
 sudo apt-get install qemu-system&lt;br /&gt;
Or you can build qemu from git. You only need to do this if the qemu on your distro doesn&#039;t support the Broadcom SOC (ARM1176 core) on the Pi.&lt;br /&gt;
In order to boot your image you will need a suitable kernel for your emulator, there is one available here http://dl.dropbox.com/u/45842273/zImage_3.1.9 &lt;br /&gt;
Boot your virtual Pi &lt;br /&gt;
 qemu-system-arm -kernel kernel-qemu -cpu arm1176 -m 256 -M versatilepb -no-reboot -serial stdio -append &amp;quot;root=/dev/sda2 rw panic=1&amp;quot; qtonpi-sdcard-0.2.img -redir tcp:5022::22&lt;br /&gt;
&lt;br /&gt;
add&lt;br /&gt;
 console=ttyAMA0&lt;br /&gt;
to the -append param to have the boot console re-directed to the terminal.&lt;br /&gt;
&lt;br /&gt;
the -redir tcp:5022::22 redirects port 22 (ssh) on the virtual Pi to port 5022 on the host enabling you to ssh in.&lt;br /&gt;
 ssh pi@localhost -p5022&lt;br /&gt;
===Raspberry Pi Setup===&lt;br /&gt;
I used the image I was using above and wrote it to an SD card.&#039;&#039;If you are on windows make sure your machine can handle larger cards&#039;&#039;&lt;br /&gt;
By default the qtonpi release doesn&#039;t have the network if enabled. On each boot you can run&lt;br /&gt;
 ifup eth0&lt;br /&gt;
or&lt;br /&gt;
 dhclient eth0&lt;br /&gt;
or&lt;br /&gt;
 just edit /etc/sysconfig/network-scripts/ifcfg-eth0 and set the ONBOOT option equal to YES and be done with it.&lt;br /&gt;
&lt;br /&gt;
Also you need to set the time and date after each boot - no RTC on the rPi&lt;br /&gt;
&lt;br /&gt;
==Code Changes==&lt;br /&gt;
According to the current Qt Documentation adding&lt;br /&gt;
 greaterThan(QT_MAJOR_VERSION, 4) {&lt;br /&gt;
        QT += widgets&lt;br /&gt;
        QT += quick1&lt;br /&gt;
    } else {&lt;br /&gt;
        QT += declarative&lt;br /&gt;
    }&lt;br /&gt;
to the pro file loads the correct modules for both Qt4/Qt5.&lt;br /&gt;
At the moment my code and svn differ and not in a nice way - once I get everything #ifdef&#039;d into place I&#039;ll either stick a patch here or check it in with golgoj4 approval :)&lt;br /&gt;
&lt;br /&gt;
===&amp;quot;Useful&amp;quot; Qt links===&lt;br /&gt;
http://qt-project.org/wiki/Transition_from_Qt_4.x_to_Qt5&lt;br /&gt;
&lt;br /&gt;
https://qt-project.org/wiki/New_Signal_Slot_Syntax&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/Qt-5Features&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/QML1-vs-QML2&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi distros==&lt;br /&gt;
Looking at http://elinux.org/RPi_Distributions there are quite a few to choose from.&lt;br /&gt;
&lt;br /&gt;
Which is the best fit? I don&#039;t know.&lt;br /&gt;
&lt;br /&gt;
I&#039;m starting with QtonPi but I don&#039;t know if a full fedora release is necessary.&lt;br /&gt;
&#039;&#039;This is actually a trimmed down fedora release no X, graphics written direct to fb&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Mer/Meego might be a good fit too.&lt;br /&gt;
&lt;br /&gt;
=qOrbiter on Pi=&lt;br /&gt;
==QtonPi 0.2 image==&lt;br /&gt;
trimmed down fedora remix with qt5 pre-installed, no gui.&lt;br /&gt;
====Status====&lt;br /&gt;
&#039;&#039;28/05/2012&#039;&#039; - Unfortunately I have not been able to get my compiled qOrbiter to run on my virtual setup.&lt;br /&gt;
Depending on the combination of kernel I use and/or SD image I either get an illegal instruction or and error creating a vchiq instance.&lt;br /&gt;
&lt;br /&gt;
And given that the vchiq lib stuff is to do with the GPU, which is initialised in firmware, this may be a bit of an impass until I get actual hardware.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;30/05/2012&#039;&#039; - Have just received my rPi and my previously compiled qOrbiter starts and gets past the vchiq/illegal instruction I had.&lt;br /&gt;
I have other issues before I get it going but all going in the right direction.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;02/06/2012&#039;&#039; - qOrbiter splash screen loads, communicates with dcerouter, gets config - then boom my network dies. I don&#039;t know if its rPi specific or some porting issue with qOrbiter. I see &#039;&#039;smsc95xx 1-1.1:1.0: eth0: kevent 2 may have been dropped&#039;&#039; scroll past me. My ssh connection dies as a result so I need to be logged in on the rPi. Needs more investigation...&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;06/06/2012&#039;&#039; - got past n/w problem, now home screen loads. Also had to disable qml screen saver. The shader effect component is supposed to be available via QtQuick 2.0 and not need the labs plugin, but this appears not to be the case. It is likely it is just not in the snapshot yet.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;08/06/2012&#039;&#039; - It seems there is no mouse support in the current 0.2 qtonpi SD image. This is a deal breaker until 0.3 image is released. Mouse support has been checked into git so is available if we roll our own qt5.&lt;br /&gt;
&lt;br /&gt;
==Next image - Debian Wheezy==&lt;br /&gt;
Investigating a debian wheezy port at the moment - should eek out a bit more speed using hardfp. There are qt50-snapshots available for the target. May need to set up a separate toolchain.&lt;br /&gt;
===Status===&lt;br /&gt;
&#039;&#039;11/06/2012&#039;&#039; - existing qOrbiter won&#039;t run on target, need to link against newer qt5 sysroot on host.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;19/06/2012&#039;&#039; - have rebuilt and linked qOrbiter against qt5 from git. Up and running again on my Raspberry Pi. The default CPU/GPU split of 192/64 allows qOrbiter to run, lower one - 244/32 gives an error creating the display surface. Will bump up split to 128/128 if I get display issues.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;22/06/2012&#039;&#039; - as I thought, I had to move the split to 128/128 and now I get no GL memory errors and the background effects work on the home screen. I need to find out why switching threads away from the qml engine is failing.&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31637</id>
		<title>RaspberryPi qOrbiter</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31637"/>
		<updated>2012-06-19T16:23:18Z</updated>

		<summary type="html">&lt;p&gt;Coley: Status update&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Device Specification==&lt;br /&gt;
-The Raspberry Pi is an ARM based computer the size of a credit card.  700Mhz, 256MB RAM, Ethernet, 2xUSB, GPIO&lt;br /&gt;
&lt;br /&gt;
-256MB of RAM is insufficient to build lmce.  MakeRelease and MakeRelease_PrepFiles both fail with out of memory errors due to the limited memory available on the RPi.&lt;br /&gt;
-Cross-compiling will be required.  More notes to follow.&lt;br /&gt;
&lt;br /&gt;
==Cross Compilation setup==&lt;br /&gt;
Initially this section will have information specific to getting Qt on Pi going. Its pre-packaged and fairly easy to install.&lt;br /&gt;
&lt;br /&gt;
At the time of writing Qt on Pi tarball is at version 0.2.&lt;br /&gt;
Get the tarball here http://www.raspberrypi.org/downloads at the bottom of the page. This has a premade SD image plus the toolchain and sysroot install required for cross compilation.&lt;br /&gt;
&lt;br /&gt;
===If you are about to install this on your current machine with a working Qt development environment DON&#039;T===&lt;br /&gt;
You will need to either set up a VM or a chroot environment as the qt5 shipped with this image isn&#039;t setup to install alongside an x86 install. They plan on having these play nice in future releases.&lt;br /&gt;
&lt;br /&gt;
==Qt5, Toolchain and sysroot install==&lt;br /&gt;
This is documented on the QtonPi wiki but basically after you have downloaded the qtonpi tarball extract the three files within.&lt;br /&gt;
Then as root extract [opt-qt5-current.tar.bz2] and [toolchain-and-sysroot-armv5tel.tar.bz2] &lt;br /&gt;
 $ cd /&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/opt-qt5-current.tar.bz2&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/toolchain-and-sysroot-armv5tel.tar.bz2&lt;br /&gt;
&lt;br /&gt;
===Qt creator===&lt;br /&gt;
The tarball comes with a recent version of qtcreator, but since then qt2.5 RC has come out, Should be safe enough to use that instead. Just install that by executing the .bin installer. &#039;&#039;Hold that thought, qt2.5 creator RC doesn&#039;t have the deploy steps set up&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Within Qt creator you need to point it at your cross tool chain compiler+debugger:&lt;br /&gt;
#Tools-&amp;gt;Options-&amp;gt;Build&amp;amp;Run then Tool Chains&lt;br /&gt;
#then select add, in the drop-down pick GCC&lt;br /&gt;
#Select GCC and browse for compiler to&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gcc&lt;br /&gt;
and for the debugger&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gdb&lt;br /&gt;
Save these selections by clicking Apply and OK&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi Setup==&lt;br /&gt;
===Virtual using qemu===&lt;br /&gt;
As I don&#039;t have a rpi yet I used qemu to do some initial testing.&lt;br /&gt;
My setup was a 12.04 VM.&lt;br /&gt;
You can either install qemu&lt;br /&gt;
 sudo apt-get install qemu-system&lt;br /&gt;
Or you can build qemu from git. You only need to do this if the qemu on your distro doesn&#039;t support the Broadcom SOC (ARM1176 core) on the Pi.&lt;br /&gt;
In order to boot your image you will need a suitable kernel for your emulator, there is one available here http://dl.dropbox.com/u/45842273/zImage_3.1.9 &lt;br /&gt;
Boot your virtual Pi &lt;br /&gt;
 qemu-system-arm -kernel kernel-qemu -cpu arm1176 -m 256 -M versatilepb -no-reboot -serial stdio -append &amp;quot;root=/dev/sda2 rw panic=1&amp;quot; qtonpi-sdcard-0.2.img -redir tcp:5022::22&lt;br /&gt;
&lt;br /&gt;
add&lt;br /&gt;
 console=ttyAMA0&lt;br /&gt;
to the -append param to have the boot console re-directed to the terminal.&lt;br /&gt;
&lt;br /&gt;
the -redir tcp:5022::22 redirects port 22 (ssh) on the virtual Pi to port 5022 on the host enabling you to ssh in.&lt;br /&gt;
 ssh pi@localhost -p5022&lt;br /&gt;
===Raspberry Pi Setup===&lt;br /&gt;
I used the image I was using above and wrote it to an SD card.&#039;&#039;If you are on windows make sure your machine can handle larger cards&#039;&#039;&lt;br /&gt;
By default the qtonpi release doesn&#039;t have the network if enabled. On each boot you can run&lt;br /&gt;
 ifup eth0&lt;br /&gt;
or&lt;br /&gt;
 dhclient eth0&lt;br /&gt;
or&lt;br /&gt;
 just edit /etc/sysconfig/network-scripts/ifcfg-eth0 and set the ONBOOT option equal to YES and be done with it.&lt;br /&gt;
&lt;br /&gt;
Also you need to set the time and date after each boot - no RTC on the rPi&lt;br /&gt;
&lt;br /&gt;
==Code Changes==&lt;br /&gt;
According to the current Qt Documentation adding&lt;br /&gt;
 greaterThan(QT_MAJOR_VERSION, 4) {&lt;br /&gt;
        QT += widgets&lt;br /&gt;
        QT += quick1&lt;br /&gt;
    } else {&lt;br /&gt;
        QT += declarative&lt;br /&gt;
    }&lt;br /&gt;
to the pro file loads the correct modules for both Qt4/Qt5.&lt;br /&gt;
At the moment my code and svn differ and not in a nice way - once I get everything #ifdef&#039;d into place I&#039;ll either stick a patch here or check it in with golgoj4 approval :)&lt;br /&gt;
&lt;br /&gt;
===&amp;quot;Useful&amp;quot; Qt links===&lt;br /&gt;
http://qt-project.org/wiki/Transition_from_Qt_4.x_to_Qt5&lt;br /&gt;
&lt;br /&gt;
https://qt-project.org/wiki/New_Signal_Slot_Syntax&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/Qt-5Features&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/QML1-vs-QML2&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi distros==&lt;br /&gt;
Looking at http://elinux.org/RPi_Distributions there are quite a few to choose from.&lt;br /&gt;
&lt;br /&gt;
Which is the best fit? I don&#039;t know.&lt;br /&gt;
&lt;br /&gt;
I&#039;m starting with QtonPi but I don&#039;t know if a full fedora release is necessary.&lt;br /&gt;
&#039;&#039;This is actually a trimmed down fedora release no X, graphics written direct to fb&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Mer/Meego might be a good fit too.&lt;br /&gt;
&lt;br /&gt;
=qOrbiter on Pi=&lt;br /&gt;
==QtonPi 0.2 image==&lt;br /&gt;
trimmed down fedora remix with qt5 pre-installed, no gui.&lt;br /&gt;
====Status====&lt;br /&gt;
&#039;&#039;28/05/2012&#039;&#039; - Unfortunately I have not been able to get my compiled qOrbiter to run on my virtual setup.&lt;br /&gt;
Depending on the combination of kernel I use and/or SD image I either get an illegal instruction or and error creating a vchiq instance.&lt;br /&gt;
&lt;br /&gt;
And given that the vchiq lib stuff is to do with the GPU, which is initialised in firmware, this may be a bit of an impass until I get actual hardware.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;30/05/2012&#039;&#039; - Have just received my rPi and my previously compiled qOrbiter starts and gets past the vchiq/illegal instruction I had.&lt;br /&gt;
I have other issues before I get it going but all going in the right direction.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;02/06/2012&#039;&#039; - qOrbiter splash screen loads, communicates with dcerouter, gets config - then boom my network dies. I don&#039;t know if its rPi specific or some porting issue with qOrbiter. I see &#039;&#039;smsc95xx 1-1.1:1.0: eth0: kevent 2 may have been dropped&#039;&#039; scroll past me. My ssh connection dies as a result so I need to be logged in on the rPi. Needs more investigation...&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;06/06/2012&#039;&#039; - got past n/w problem, now home screen loads. Also had to disable qml screen saver. The shader effect component is supposed to be available via QtQuick 2.0 and not need the labs plugin, but this appears not to be the case. It is likely it is just not in the snapshot yet.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;08/06/2012&#039;&#039; - It seems there is no mouse support in the current 0.2 qtonpi SD image. This is a deal breaker until 0.3 image is released. Mouse support has been checked into git so is available if we roll our own qt5.&lt;br /&gt;
&lt;br /&gt;
==Next image - Debian Wheezy==&lt;br /&gt;
Investigating a debian wheezy port at the moment - should eek out a bit more speed using hardfp. There are qt50-snapshots available for the target. May need to set up a separate toolchain.&lt;br /&gt;
===Status===&lt;br /&gt;
&#039;&#039;11/06/2012&#039;&#039; - existing qOrbiter won&#039;t run on target, need to link against newer qt5 sysroot on host.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;19/06/2012&#039;&#039; - have rebuilt and linked qOrbiter against qt5 from git. Up and running again on my Raspberry Pi. The default CPU/GPU split of 192/64 allows qOrbiter to run, lower one - 244/32 gives an error creating the display surface. Will bump up split to 128/128 if I get display issues.&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31553</id>
		<title>RaspberryPi qOrbiter</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31553"/>
		<updated>2012-06-11T21:19:58Z</updated>

		<summary type="html">&lt;p&gt;Coley: fix typo&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Device Specification==&lt;br /&gt;
-The Raspberry Pi is an ARM based computer the size of a credit card.  700Mhz, 256MB RAM, Ethernet, 2xUSB, GPIO&lt;br /&gt;
&lt;br /&gt;
-256MB of RAM is insufficient to build lmce.  MakeRelease and MakeRelease_PrepFiles both fail with out of memory errors due to the limited memory available on the RPi.&lt;br /&gt;
-Cross-compiling will be required.  More notes to follow.&lt;br /&gt;
&lt;br /&gt;
==Cross Compilation setup==&lt;br /&gt;
Initially this section will have information specific to getting Qt on Pi going. Its pre-packaged and fairly easy to install.&lt;br /&gt;
&lt;br /&gt;
At the time of writing Qt on Pi tarball is at version 0.2.&lt;br /&gt;
Get the tarball here http://www.raspberrypi.org/downloads at the bottom of the page. This has a premade SD image plus the toolchain and sysroot install required for cross compilation.&lt;br /&gt;
&lt;br /&gt;
===If you are about to install this on your current machine with a working Qt development environment DON&#039;T===&lt;br /&gt;
You will need to either set up a VM or a chroot environment as the qt5 shipped with this image isn&#039;t setup to install alongside an x86 install. They plan on having these play nice in future releases.&lt;br /&gt;
&lt;br /&gt;
==Qt5, Toolchain and sysroot install==&lt;br /&gt;
This is documented on the QtonPi wiki but basically after you have downloaded the qtonpi tarball extract the three files within.&lt;br /&gt;
Then as root extract [opt-qt5-current.tar.bz2] and [toolchain-and-sysroot-armv5tel.tar.bz2] &lt;br /&gt;
 $ cd /&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/opt-qt5-current.tar.bz2&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/toolchain-and-sysroot-armv5tel.tar.bz2&lt;br /&gt;
&lt;br /&gt;
===Qt creator===&lt;br /&gt;
The tarball comes with a recent version of qtcreator, but since then qt2.5 RC has come out, Should be safe enough to use that instead. Just install that by executing the .bin installer. &#039;&#039;Hold that thought, qt2.5 creator RC doesn&#039;t have the deploy steps set up&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Within Qt creator you need to point it at your cross tool chain compiler+debugger:&lt;br /&gt;
#Tools-&amp;gt;Options-&amp;gt;Build&amp;amp;Run then Tool Chains&lt;br /&gt;
#then select add, in the drop-down pick GCC&lt;br /&gt;
#Select GCC and browse for compiler to&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gcc&lt;br /&gt;
and for the debugger&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gdb&lt;br /&gt;
Save these selections by clicking Apply and OK&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi Setup==&lt;br /&gt;
===Virtual using qemu===&lt;br /&gt;
As I don&#039;t have a rpi yet I used qemu to do some initial testing.&lt;br /&gt;
My setup was a 12.04 VM.&lt;br /&gt;
You can either install qemu&lt;br /&gt;
 sudo apt-get install qemu-system&lt;br /&gt;
Or you can build qemu from git. You only need to do this if the qemu on your distro doesn&#039;t support the Broadcom SOC (ARM1176 core) on the Pi.&lt;br /&gt;
In order to boot your image you will need a suitable kernel for your emulator, there is one available here http://dl.dropbox.com/u/45842273/zImage_3.1.9 &lt;br /&gt;
Boot your virtual Pi &lt;br /&gt;
 qemu-system-arm -kernel kernel-qemu -cpu arm1176 -m 256 -M versatilepb -no-reboot -serial stdio -append &amp;quot;root=/dev/sda2 rw panic=1&amp;quot; qtonpi-sdcard-0.2.img -redir tcp:5022::22&lt;br /&gt;
&lt;br /&gt;
add&lt;br /&gt;
 console=ttyAMA0&lt;br /&gt;
to the -append param to have the boot console re-directed to the terminal.&lt;br /&gt;
&lt;br /&gt;
the -redir tcp:5022::22 redirects port 22 (ssh) on the virtual Pi to port 5022 on the host enabling you to ssh in.&lt;br /&gt;
 ssh pi@localhost -p5022&lt;br /&gt;
===Raspberry Pi Setup===&lt;br /&gt;
I used the image I was using above and wrote it to an SD card.&#039;&#039;If you are on windows make sure your machine can handle larger cards&#039;&#039;&lt;br /&gt;
By default the qtonpi release doesn&#039;t have the network if enabled. On each boot you can run&lt;br /&gt;
 ifup eth0&lt;br /&gt;
or&lt;br /&gt;
 dhclient eth0&lt;br /&gt;
or&lt;br /&gt;
 just edit /etc/sysconfig/network-scripts/ifcfg-eth0 and set the ONBOOT option equal to YES and be done with it.&lt;br /&gt;
&lt;br /&gt;
Also you need to set the time and date after each boot - no RTC on the rPi&lt;br /&gt;
&lt;br /&gt;
==Code Changes==&lt;br /&gt;
According to the current Qt Documentation adding&lt;br /&gt;
 greaterThan(QT_MAJOR_VERSION, 4) {&lt;br /&gt;
        QT += widgets&lt;br /&gt;
        QT += quick1&lt;br /&gt;
    } else {&lt;br /&gt;
        QT += declarative&lt;br /&gt;
    }&lt;br /&gt;
to the pro file loads the correct modules for both Qt4/Qt5.&lt;br /&gt;
At the moment my code and svn differ and not in a nice way - once I get everything #ifdef&#039;d into place I&#039;ll either stick a patch here or check it in with golgoj4 approval :)&lt;br /&gt;
&lt;br /&gt;
===&amp;quot;Useful&amp;quot; Qt links===&lt;br /&gt;
http://qt-project.org/wiki/Transition_from_Qt_4.x_to_Qt5&lt;br /&gt;
&lt;br /&gt;
https://qt-project.org/wiki/New_Signal_Slot_Syntax&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/Qt-5Features&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/QML1-vs-QML2&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi distros==&lt;br /&gt;
Looking at http://elinux.org/RPi_Distributions there are quite a few to choose from.&lt;br /&gt;
&lt;br /&gt;
Which is the best fit? I don&#039;t know.&lt;br /&gt;
&lt;br /&gt;
I&#039;m starting with QtonPi but I don&#039;t know if a full fedora release is necessary.&lt;br /&gt;
&#039;&#039;This is actually a trimmed down fedora release no X, graphics written direct to fb&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Mer/Meego might be a good fit too.&lt;br /&gt;
&lt;br /&gt;
=qOrbiter on Pi=&lt;br /&gt;
==QtonPi 0.2 image==&lt;br /&gt;
trimmed down fedora remix with qt5 pre-installed, no gui.&lt;br /&gt;
====Status====&lt;br /&gt;
&#039;&#039;28/05/2012&#039;&#039; - Unfortunately I have not been able to get my compiled qOrbiter to run on my virtual setup.&lt;br /&gt;
Depending on the combination of kernel I use and/or SD image I either get an illegal instruction or and error creating a vchiq instance.&lt;br /&gt;
&lt;br /&gt;
And given that the vchiq lib stuff is to do with the GPU, which is initialised in firmware, this may be a bit of an impass until I get actual hardware.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;30/05/2012&#039;&#039; - Have just received my rPi and my previously compiled qOrbiter starts and gets past the vchiq/illegal instruction I had.&lt;br /&gt;
I have other issues before I get it going but all going in the right direction.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;02/06/2012&#039;&#039; - qOrbiter splash screen loads, communicates with dcerouter, gets config - then boom my network dies. I don&#039;t know if its rPi specific or some porting issue with qOrbiter. I see &#039;&#039;smsc95xx 1-1.1:1.0: eth0: kevent 2 may have been dropped&#039;&#039; scroll past me. My ssh connection dies as a result so I need to be logged in on the rPi. Needs more investigation...&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;06/06/2012&#039;&#039; - got past n/w problem, now home screen loads. Also had to disable qml screen saver. The shader effect component is supposed to be available via QtQuick 2.0 and not need the labs plugin, but this appears not to be the case. It is likely it is just not in the snapshot yet.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;08/06/2012&#039;&#039; - It seems there is no mouse support in the current 0.2 qtonpi SD image. This is a deal breaker until 0.3 image is released. Mouse support has been checked into git so is available if we roll our own qt5.&lt;br /&gt;
&lt;br /&gt;
==Next image - Debian Wheezy==&lt;br /&gt;
Investigating a debian wheezy port at the moment - should eek out a bit more speed using hardfp. There are qt50-snapshots available for the target. May need to set up a separate toolchain.&lt;br /&gt;
===Status===&lt;br /&gt;
&#039;&#039;11/06/2012&#039;&#039; - existing qOrbiter won&#039;t run on target, need to link against newer qt5 sysroot on host.&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31548</id>
		<title>RaspberryPi qOrbiter</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31548"/>
		<updated>2012-06-11T11:07:23Z</updated>

		<summary type="html">&lt;p&gt;Coley: bit of a re-org of page.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Device Specification==&lt;br /&gt;
-The Raspberry Pi is an ARM based computer the size of a credit card.  700Mhz, 256MB RAM, Ethernet, 2xUSB, GPIO&lt;br /&gt;
&lt;br /&gt;
-256MB of RAM is insufficient to build lmce.  MakeRelease and MakeRelease_PrepFiles both fail with out of memory errors due to the limited memory available on the RPi.&lt;br /&gt;
-Cross-compiling will be required.  More notes to follow.&lt;br /&gt;
&lt;br /&gt;
==Cross Compilation setup==&lt;br /&gt;
Initially this section will have information specific to getting Qt on Pi going. Its pre-packaged and fairly easy to install.&lt;br /&gt;
&lt;br /&gt;
At the time of writing Qt on Pi tarball is at version 0.2.&lt;br /&gt;
Get the tarball here http://www.raspberrypi.org/downloads at the bottom of the page. This has a premade SD image plus the toolchain and sysroot install required for cross compilation.&lt;br /&gt;
&lt;br /&gt;
===If you are about to install this on your current machine with a working Qt development environment DON&#039;T===&lt;br /&gt;
You will need to either set up a VM or a chroot environment as the qt5 shipped with this image isn&#039;t setup to install alongside an x86 install. They plan on having these play nice in future releases.&lt;br /&gt;
&lt;br /&gt;
==Qt5, Toolchain and sysroot install==&lt;br /&gt;
This is documented on the QtonPi wiki but basically after you have downloaded the qtonpi tarball extract the three files within.&lt;br /&gt;
Then as root extract [opt-qt5-current.tar.bz2] and [toolchain-and-sysroot-armv5tel.tar.bz2] &lt;br /&gt;
 $ cd /&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/opt-qt5-current.tar.bz2&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/toolchain-and-sysroot-armv5tel.tar.bz2&lt;br /&gt;
&lt;br /&gt;
===Qt creator===&lt;br /&gt;
The tarball comes with a recent version of qtcreator, but since then qt2.5 RC has come out, Should be safe enough to use that instead. Just install that by executing the .bin installer. &#039;&#039;Hold that thought, qt2.5 creator RC doesn&#039;t have the deploy steps set up&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Within Qt creator you need to point it at your cross tool chain compiler+debugger:&lt;br /&gt;
#Tools-&amp;gt;Options-&amp;gt;Build&amp;amp;Run then Tool Chains&lt;br /&gt;
#then select add, in the drop-down pick GCC&lt;br /&gt;
#Select GCC and browse for compiler to&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gcc&lt;br /&gt;
and for the debugger&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gdb&lt;br /&gt;
Save these selections by clicking Apply and OK&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi Setup==&lt;br /&gt;
===Virtual using qemu===&lt;br /&gt;
As I don&#039;t have a rpi yet I used qemu to do some initial testing.&lt;br /&gt;
My setup was a 12.04 VM.&lt;br /&gt;
You can either install qemu&lt;br /&gt;
 sudo apt-get install qemu-system&lt;br /&gt;
Or you can build qemu from git. You only need to do this if the qemu on your distro doesn&#039;t support the Broadcom SOC (ARM1176 core) on the Pi.&lt;br /&gt;
In order to boot your image you will need a suitable kernel for your emulator, there is one available here http://dl.dropbox.com/u/45842273/zImage_3.1.9 &lt;br /&gt;
Boot your virtual Pi &lt;br /&gt;
 qemu-system-arm -kernel kernel-qemu -cpu arm1176 -m 256 -M versatilepb -no-reboot -serial stdio -append &amp;quot;root=/dev/sda2 rw panic=1&amp;quot; qtonpi-sdcard-0.2.img -redir tcp:5022::22&lt;br /&gt;
&lt;br /&gt;
add&lt;br /&gt;
 console=ttyAMA0&lt;br /&gt;
to the -append param to have the boot console re-directed to the terminal.&lt;br /&gt;
&lt;br /&gt;
the -redir tcp:5022::22 redirects port 22 (ssh) on the virtual Pi to port 5022 on the host enabling you to ssh in.&lt;br /&gt;
 ssh pi@localhost -p5022&lt;br /&gt;
===Raspberry Pi Setup===&lt;br /&gt;
I used the image I was using above and wrote it to an SD card.&#039;&#039;If you are on windows make sure your machine can handle larger cards&#039;&#039;&lt;br /&gt;
By default the qtonpi release doesn&#039;t have the network if enabled. On each boot you can run&lt;br /&gt;
 ifup eth0&lt;br /&gt;
or&lt;br /&gt;
 dhclient eth0&lt;br /&gt;
or&lt;br /&gt;
 just edit /etc/sysconfic/network-scripts/ifcfg-eth0 and set the ONBOOT option equal to YES and be done with it.&lt;br /&gt;
&lt;br /&gt;
Also you need to set the time and date after each boot - no RTC on the rPi&lt;br /&gt;
&lt;br /&gt;
==Code Changes==&lt;br /&gt;
According to the current Qt Documentation adding&lt;br /&gt;
 greaterThan(QT_MAJOR_VERSION, 4) {&lt;br /&gt;
        QT += widgets&lt;br /&gt;
        QT += quick1&lt;br /&gt;
    } else {&lt;br /&gt;
        QT += declarative&lt;br /&gt;
    }&lt;br /&gt;
to the pro file loads the correct modules for both Qt4/Qt5.&lt;br /&gt;
At the moment my code and svn differ and not in a nice way - once I get everything #ifdef&#039;d into place I&#039;ll either stick a patch here or check it in with golgoj4 approval :)&lt;br /&gt;
&lt;br /&gt;
===&amp;quot;Useful&amp;quot; Qt links===&lt;br /&gt;
http://qt-project.org/wiki/Transition_from_Qt_4.x_to_Qt5&lt;br /&gt;
&lt;br /&gt;
https://qt-project.org/wiki/New_Signal_Slot_Syntax&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/Qt-5Features&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/QML1-vs-QML2&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi distros==&lt;br /&gt;
Looking at http://elinux.org/RPi_Distributions there are quite a few to choose from.&lt;br /&gt;
&lt;br /&gt;
Which is the best fit? I don&#039;t know.&lt;br /&gt;
&lt;br /&gt;
I&#039;m starting with QtonPi but I don&#039;t know if a full fedora release is necessary.&lt;br /&gt;
&#039;&#039;This is actually a trimmed down fedora release no X, graphics written direct to fb&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Mer/Meego might be a good fit too.&lt;br /&gt;
&lt;br /&gt;
=qOrbiter on Pi=&lt;br /&gt;
==QtonPi 0.2 image==&lt;br /&gt;
trimmed down fedora remix with qt5 pre-installed, no gui.&lt;br /&gt;
====Status====&lt;br /&gt;
&#039;&#039;28/05/2012&#039;&#039; - Unfortunately I have not been able to get my compiled qOrbiter to run on my virtual setup.&lt;br /&gt;
Depending on the combination of kernel I use and/or SD image I either get an illegal instruction or and error creating a vchiq instance.&lt;br /&gt;
&lt;br /&gt;
And given that the vchiq lib stuff is to do with the GPU, which is initialised in firmware, this may be a bit of an impass until I get actual hardware.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;30/05/2012&#039;&#039; - Have just received my rPi and my previously compiled qOrbiter starts and gets past the vchiq/illegal instruction I had.&lt;br /&gt;
I have other issues before I get it going but all going in the right direction.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;02/06/2012&#039;&#039; - qOrbiter splash screen loads, communicates with dcerouter, gets config - then boom my network dies. I don&#039;t know if its rPi specific or some porting issue with qOrbiter. I see &#039;&#039;smsc95xx 1-1.1:1.0: eth0: kevent 2 may have been dropped&#039;&#039; scroll past me. My ssh connection dies as a result so I need to be logged in on the rPi. Needs more investigation...&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;06/06/2012&#039;&#039; - got past n/w problem, now home screen loads. Also had to disable qml screen saver. The shader effect component is supposed to be available via QtQuick 2.0 and not need the labs plugin, but this appears not to be the case. It is likely it is just not in the snapshot yet.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;08/06/2012&#039;&#039; - It seems there is no mouse support in the current 0.2 qtonpi SD image. This is a deal breaker until 0.3 image is released. Mouse support has been checked into git so is available if we roll our own qt5.&lt;br /&gt;
&lt;br /&gt;
==Next image - Debian Wheezy==&lt;br /&gt;
Investigating a debian wheezy port at the moment - should eek out a bit more speed using hardfp. There are qt50-snapshots available for the target. May need to set up a separate toolchain.&lt;br /&gt;
===Status===&lt;br /&gt;
&#039;&#039;11/06/2012&#039;&#039; - existing qOrbiter won&#039;t run on target, need to link against newer qt5 sysroot on host.&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31539</id>
		<title>RaspberryPi qOrbiter</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31539"/>
		<updated>2012-06-10T23:28:55Z</updated>

		<summary type="html">&lt;p&gt;Coley: parked one image investigation, onto new one.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Device Specification==&lt;br /&gt;
-The Raspberry Pi is an ARM based computer the size of a credit card.  700Mhz, 256MB RAM, Ethernet, 2xUSB, GPIO&lt;br /&gt;
&lt;br /&gt;
-256MB of RAM is insufficient to build lmce.  MakeRelease and MakeRelease_PrepFiles both fail with out of memory errors due to the limited memory available on the RPi.&lt;br /&gt;
-Cross-compiling will be required.  More notes to follow.&lt;br /&gt;
&lt;br /&gt;
==Cross Compilation setup==&lt;br /&gt;
Initially this section will have information specific to getting Qt on Pi going. Its pre-packaged and fairly easy to install.&lt;br /&gt;
&lt;br /&gt;
At the time of writing Qt on Pi tarball is at version 0.2.&lt;br /&gt;
Get the tarball here http://www.raspberrypi.org/downloads at the bottom of the page. This has a premade SD image plus the toolchain and sysroot install required for cross compilation.&lt;br /&gt;
&lt;br /&gt;
===If you are about to install this on your current machine with a working Qt development environment DON&#039;T===&lt;br /&gt;
You will need to either set up a VM or a chroot environment as the qt5 shipped with this image isn&#039;t setup to install alongside an x86 install. They plan on having these play nice in future releases.&lt;br /&gt;
&lt;br /&gt;
==Qt5, Toolchain and sysroot install==&lt;br /&gt;
This is documented on the QtonPi wiki but basically after you have downloaded the qtonpi tarball extract the three files within.&lt;br /&gt;
Then as root extract [opt-qt5-current.tar.bz2] and [toolchain-and-sysroot-armv5tel.tar.bz2] &lt;br /&gt;
 $ cd /&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/opt-qt5-current.tar.bz2&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/toolchain-and-sysroot-armv5tel.tar.bz2&lt;br /&gt;
&lt;br /&gt;
===Qt creator===&lt;br /&gt;
The tarball comes with a recent version of qtcreator, but since then qt2.5 RC has come out, Should be safe enough to use that instead. Just install that by executing the .bin installer. &#039;&#039;Hold that thought, qt2.5 creator RC doesn&#039;t have the deploy steps set up&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Within Qt creator you need to point it at your cross tool chain compiler+debugger:&lt;br /&gt;
#Tools-&amp;gt;Options-&amp;gt;Build&amp;amp;Run then Tool Chains&lt;br /&gt;
#then select add, in the drop-down pick GCC&lt;br /&gt;
#Select GCC and browse for compiler to&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gcc&lt;br /&gt;
and for the debugger&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gdb&lt;br /&gt;
Save these selections by clicking Apply and OK&lt;br /&gt;
&lt;br /&gt;
==Virtual Raspberry Pi Setup==&lt;br /&gt;
As I don&#039;t have a rpi yet I used qemu to do some initial testing.&lt;br /&gt;
My setup was a 12.04 VM.&lt;br /&gt;
You can either install qemu&lt;br /&gt;
 sudo apt-get install qemu-system&lt;br /&gt;
Or you can build qemu from git. You only need to do this if the qemu on your distro doesn&#039;t support the Broadcom SOC (ARM1176 core) on the Pi.&lt;br /&gt;
In order to boot your image you will need a suitable kernel for your emulator, there is one available here http://dl.dropbox.com/u/45842273/zImage_3.1.9 &lt;br /&gt;
Boot your virtual Pi &lt;br /&gt;
 qemu-system-arm -kernel kernel-qemu -cpu arm1176 -m 256 -M versatilepb -no-reboot -serial stdio -append &amp;quot;root=/dev/sda2 rw panic=1&amp;quot; qtonpi-sdcard-0.2.img -redir tcp:5022::22&lt;br /&gt;
&lt;br /&gt;
add&lt;br /&gt;
 console=ttyAMA0&lt;br /&gt;
to the -append param to have the boot console re-directed to the terminal.&lt;br /&gt;
&lt;br /&gt;
the -redir tcp:5022::22 redirects port 22 (ssh) on the virtual Pi to port 5022 on the host enabling you to ssh in.&lt;br /&gt;
 ssh pi@localhost -p5022&lt;br /&gt;
==Raspberry Pi Setup==&lt;br /&gt;
I used the image I was using above and wrote it to an SD card.&#039;&#039;If you are on windows make sure your machine can handle larger cards&#039;&#039;&lt;br /&gt;
By default the qtonpi release doesn&#039;t have the network if enabled. On each boot you can run&lt;br /&gt;
 ifup eth0&lt;br /&gt;
or&lt;br /&gt;
 dhclient eth0&lt;br /&gt;
or&lt;br /&gt;
 just edit /etc/sysconfic/network-scripts/ifcfg-eth0 and set the ONBOOT option equal to YES and be done with it.&lt;br /&gt;
&lt;br /&gt;
Also you need to set the time and date after each boot - no RTC on the rPi&lt;br /&gt;
=qOrbiter on Pi=&lt;br /&gt;
==QtonPi 0.2 image==&lt;br /&gt;
trimmed down fedora remix with qt5 pre-installed, no gui.&lt;br /&gt;
====Status====&lt;br /&gt;
&#039;&#039;28/05/2012&#039;&#039; - Unfortunately I have not been able to get my compiled qOrbiter to run on my virtual setup.&lt;br /&gt;
Depending on the combination of kernel I use and/or SD image I either get an illegal instruction or and error creating a vchiq instance.&lt;br /&gt;
&lt;br /&gt;
And given that the vchiq lib stuff is to do with the GPU, which is initialised in firmware, this may be a bit of an impass until I get actual hardware.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;30/05/2012&#039;&#039; - Have just received my rPi and my previously compiled qOrbiter starts and gets past the vchiq/illegal instruction I had.&lt;br /&gt;
I have other issues before I get it going but all going in the right direction.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;02/06/2012&#039;&#039; - qOrbiter splash screen loads, communicates with dcerouter, gets config - then boom my network dies. I don&#039;t know if its rPi specific or some porting issue with qOrbiter. I see &#039;&#039;smsc95xx 1-1.1:1.0: eth0: kevent 2 may have been dropped&#039;&#039; scroll past me. My ssh connection dies as a result so I need to be logged in on the rPi. Needs more investigation...&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;06/06/2012&#039;&#039; - got past n/w problem, now home screen loads. Also had to disable qml screen saver. The shader effect component is supposed to be available via QtQuick 2.0 and not need the labs plugin, but this appears not to be the case. It is likely it is just not in the snapshot yet.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;08/06/2012&#039;&#039; - It seems there is no mouse support in the current 0.2 qtonpi SD image. This is a deal breaker until 0.3 image is released. Mouse support has been checked into git so is available if we roll our own qt5.&lt;br /&gt;
&lt;br /&gt;
==Next image??==&lt;br /&gt;
Investigating a debian wheezy port at the moment - should eek out a bit more speed using hardfp. There are qt50-snapshots available for the target. May need to set up a separate toolchain.&lt;br /&gt;
===Status===&lt;br /&gt;
&#039;&#039;11/06/2012&#039;&#039; - existing qOrbiter won&#039;t run on target, need to link against newer qt5 sysroot.&lt;br /&gt;
===Code Changes===&lt;br /&gt;
According to the current Qt Documentation adding&lt;br /&gt;
 greaterThan(QT_MAJOR_VERSION, 4) {&lt;br /&gt;
        QT += widgets&lt;br /&gt;
        QT += quick1&lt;br /&gt;
    } else {&lt;br /&gt;
        QT += declarative&lt;br /&gt;
    }&lt;br /&gt;
to the pro file loads the correct modules for both Qt4/Qt5.&lt;br /&gt;
At the moment my code and svn differ and not in a nice way - once I get everything #ifdef&#039;d into place I&#039;ll either stick a patch here or check it in with golgoj4 approval :)&lt;br /&gt;
&lt;br /&gt;
===&amp;quot;Useful&amp;quot; Qt links===&lt;br /&gt;
http://qt-project.org/wiki/Transition_from_Qt_4.x_to_Qt5&lt;br /&gt;
&lt;br /&gt;
https://qt-project.org/wiki/New_Signal_Slot_Syntax&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/Qt-5Features&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/QML1-vs-QML2&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi distros==&lt;br /&gt;
Looking at http://elinux.org/RPi_Distributions there are quite a few to choose from.&lt;br /&gt;
&lt;br /&gt;
Which is the best fit? I don&#039;t know.&lt;br /&gt;
&lt;br /&gt;
I&#039;m starting with QtonPi but I don&#039;t know if a full fedora release is necessary.&lt;br /&gt;
&#039;&#039;This is actually a trimmed down fedora release no X, graphics written direct to fb&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Mer/Meego might be a good fit too.&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31538</id>
		<title>RaspberryPi qOrbiter</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31538"/>
		<updated>2012-06-10T23:20:42Z</updated>

		<summary type="html">&lt;p&gt;Coley: Status update&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Device Specification==&lt;br /&gt;
-The Raspberry Pi is an ARM based computer the size of a credit card.  700Mhz, 256MB RAM, Ethernet, 2xUSB, GPIO&lt;br /&gt;
&lt;br /&gt;
-256MB of RAM is insufficient to build lmce.  MakeRelease and MakeRelease_PrepFiles both fail with out of memory errors due to the limited memory available on the RPi.&lt;br /&gt;
-Cross-compiling will be required.  More notes to follow.&lt;br /&gt;
&lt;br /&gt;
==Cross Compilation setup==&lt;br /&gt;
Initially this section will have information specific to getting Qt on Pi going. Its pre-packaged and fairly easy to install.&lt;br /&gt;
&lt;br /&gt;
At the time of writing Qt on Pi tarball is at version 0.2.&lt;br /&gt;
Get the tarball here http://www.raspberrypi.org/downloads at the bottom of the page. This has a premade SD image plus the toolchain and sysroot install required for cross compilation.&lt;br /&gt;
&lt;br /&gt;
===If you are about to install this on your current machine with a working Qt development environment DON&#039;T===&lt;br /&gt;
You will need to either set up a VM or a chroot environment as the qt5 shipped with this image isn&#039;t setup to install alongside an x86 install. They plan on having these play nice in future releases.&lt;br /&gt;
&lt;br /&gt;
==Qt5, Toolchain and sysroot install==&lt;br /&gt;
This is documented on the QtonPi wiki but basically after you have downloaded the qtonpi tarball extract the three files within.&lt;br /&gt;
Then as root extract [opt-qt5-current.tar.bz2] and [toolchain-and-sysroot-armv5tel.tar.bz2] &lt;br /&gt;
 $ cd /&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/opt-qt5-current.tar.bz2&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/toolchain-and-sysroot-armv5tel.tar.bz2&lt;br /&gt;
&lt;br /&gt;
===Qt creator===&lt;br /&gt;
The tarball comes with a recent version of qtcreator, but since then qt2.5 RC has come out, Should be safe enough to use that instead. Just install that by executing the .bin installer. &#039;&#039;Hold that thought, qt2.5 creator RC doesn&#039;t have the deploy steps set up&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Within Qt creator you need to point it at your cross tool chain compiler+debugger:&lt;br /&gt;
#Tools-&amp;gt;Options-&amp;gt;Build&amp;amp;Run then Tool Chains&lt;br /&gt;
#then select add, in the drop-down pick GCC&lt;br /&gt;
#Select GCC and browse for compiler to&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gcc&lt;br /&gt;
and for the debugger&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gdb&lt;br /&gt;
Save these selections by clicking Apply and OK&lt;br /&gt;
&lt;br /&gt;
==Virtual Raspberry Pi Setup==&lt;br /&gt;
As I don&#039;t have a rpi yet I used qemu to do some initial testing.&lt;br /&gt;
My setup was a 12.04 VM.&lt;br /&gt;
You can either install qemu&lt;br /&gt;
 sudo apt-get install qemu-system&lt;br /&gt;
Or you can build qemu from git. You only need to do this if the qemu on your distro doesn&#039;t support the Broadcom SOC (ARM1176 core) on the Pi.&lt;br /&gt;
In order to boot your image you will need a suitable kernel for your emulator, there is one available here http://dl.dropbox.com/u/45842273/zImage_3.1.9 &lt;br /&gt;
Boot your virtual Pi &lt;br /&gt;
 qemu-system-arm -kernel kernel-qemu -cpu arm1176 -m 256 -M versatilepb -no-reboot -serial stdio -append &amp;quot;root=/dev/sda2 rw panic=1&amp;quot; qtonpi-sdcard-0.2.img -redir tcp:5022::22&lt;br /&gt;
&lt;br /&gt;
add&lt;br /&gt;
 console=ttyAMA0&lt;br /&gt;
to the -append param to have the boot console re-directed to the terminal.&lt;br /&gt;
&lt;br /&gt;
the -redir tcp:5022::22 redirects port 22 (ssh) on the virtual Pi to port 5022 on the host enabling you to ssh in.&lt;br /&gt;
 ssh pi@localhost -p5022&lt;br /&gt;
==Raspberry Pi Setup==&lt;br /&gt;
I used the image I was using above and wrote it to an SD card.&#039;&#039;If you are on windows make sure your machine can handle larger cards&#039;&#039;&lt;br /&gt;
By default the qtonpi release doesn&#039;t have the network if enabled. On each boot you can run&lt;br /&gt;
 ifup eth0&lt;br /&gt;
or&lt;br /&gt;
 dhclient eth0&lt;br /&gt;
or&lt;br /&gt;
 just edit /etc/sysconfic/network-scripts/ifcfg-eth0 and set the ONBOOT option equal to YES and be done with it.&lt;br /&gt;
&lt;br /&gt;
Also you need to set the time and date after each boot - no RTC on the rPi&lt;br /&gt;
==qOrbiter on Pi==&lt;br /&gt;
===Status===&lt;br /&gt;
&#039;&#039;28/05/2012&#039;&#039; - Unfortunately I have not been able to get my compiled qOrbiter to run on my virtual setup.&lt;br /&gt;
Depending on the combination of kernel I use and/or SD image I either get an illegal instruction or and error creating a vchiq instance.&lt;br /&gt;
&lt;br /&gt;
And given that the vchiq lib stuff is to do with the GPU, which is initialised in firmware, this may be a bit of an impass until I get actual hardware.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;30/05/2012&#039;&#039; - Have just received my rPi and my previously compiled qOrbiter starts and gets past the vchiq/illegal instruction I had.&lt;br /&gt;
I have other issues before I get it going but all going in the right direction.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;02/06/2012&#039;&#039; - qOrbiter splash screen loads, communicates with dcerouter, gets config - then boom my network dies. I don&#039;t know if its rPi specific or some porting issue with qOrbiter. I see &#039;&#039;smsc95xx 1-1.1:1.0: eth0: kevent 2 may have been dropped&#039;&#039; scroll past me. My ssh connection dies as a result so I need to be logged in on the rPi. Needs more investigation...&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;06/06/2012&#039;&#039; - got past n/w problem, now home screen loads. Also had to disable qml screen saver. The shader effect component is supposed to be available via QtQuick 2.0 and not need the labs plugin, but this appears not to be the case. It is likely it is just not in the snapshot yet.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;08/06/2012&#039;&#039; - It seems there is no mouse support in the current 0.2 qtonpi SD image. This is a deal breaker until 0.3 image is released. Mouse support has been checked into git so is available if we roll our own qt5.&lt;br /&gt;
&lt;br /&gt;
===Code Changes===&lt;br /&gt;
According to the current Qt Documentation adding&lt;br /&gt;
 greaterThan(QT_MAJOR_VERSION, 4) {&lt;br /&gt;
        QT += widgets&lt;br /&gt;
        QT += quick1&lt;br /&gt;
    } else {&lt;br /&gt;
        QT += declarative&lt;br /&gt;
    }&lt;br /&gt;
to the pro file loads the correct modules for both Qt4/Qt5.&lt;br /&gt;
At the moment my code and svn differ and not in a nice way - once I get everything #ifdef&#039;d into place I&#039;ll either stick a patch here or check it in with golgoj4 approval :)&lt;br /&gt;
&lt;br /&gt;
===&amp;quot;Useful&amp;quot; Qt links===&lt;br /&gt;
http://qt-project.org/wiki/Transition_from_Qt_4.x_to_Qt5&lt;br /&gt;
&lt;br /&gt;
https://qt-project.org/wiki/New_Signal_Slot_Syntax&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/Qt-5Features&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/QML1-vs-QML2&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi distros==&lt;br /&gt;
Looking at http://elinux.org/RPi_Distributions there are quite a few to choose from.&lt;br /&gt;
&lt;br /&gt;
Which is the best fit? I don&#039;t know.&lt;br /&gt;
&lt;br /&gt;
I&#039;m starting with QtonPi but I don&#039;t know if a full fedora release is necessary.&lt;br /&gt;
&#039;&#039;This is actually a trimmed down fedora release no X, graphics written direct to fb&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Mer/Meego might be a good fit too.&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31504</id>
		<title>RaspberryPi qOrbiter</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31504"/>
		<updated>2012-06-07T23:51:14Z</updated>

		<summary type="html">&lt;p&gt;Coley: Status update&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Device Specification==&lt;br /&gt;
-The Raspberry Pi is an ARM based computer the size of a credit card.  700Mhz, 256MB RAM, Ethernet, 2xUSB, GPIO&lt;br /&gt;
&lt;br /&gt;
-256MB of RAM is insufficient to build lmce.  MakeRelease and MakeRelease_PrepFiles both fail with out of memory errors due to the limited memory available on the RPi.&lt;br /&gt;
-Cross-compiling will be required.  More notes to follow.&lt;br /&gt;
&lt;br /&gt;
==Cross Compilation setup==&lt;br /&gt;
Initially this section will have information specific to getting Qt on Pi going. Its pre-packaged and fairly easy to install.&lt;br /&gt;
&lt;br /&gt;
At the time of writing Qt on Pi tarball is at version 0.2.&lt;br /&gt;
Get the tarball here http://www.raspberrypi.org/downloads at the bottom of the page. This has a premade SD image plus the toolchain and sysroot install required for cross compilation.&lt;br /&gt;
&lt;br /&gt;
===If you are about to install this on your current machine with a working Qt development environment DON&#039;T===&lt;br /&gt;
You will need to either set up a VM or a chroot environment as the qt5 shipped with this image isn&#039;t setup to install alongside an x86 install. They plan on having these play nice in future releases.&lt;br /&gt;
&lt;br /&gt;
==Qt5, Toolchain and sysroot install==&lt;br /&gt;
This is documented on the QtonPi wiki but basically after you have downloaded the qtonpi tarball extract the three files within.&lt;br /&gt;
Then as root extract [opt-qt5-current.tar.bz2] and [toolchain-and-sysroot-armv5tel.tar.bz2] &lt;br /&gt;
 $ cd /&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/opt-qt5-current.tar.bz2&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/toolchain-and-sysroot-armv5tel.tar.bz2&lt;br /&gt;
&lt;br /&gt;
===Qt creator===&lt;br /&gt;
The tarball comes with a recent version of qtcreator, but since then qt2.5 RC has come out, Should be safe enough to use that instead. Just install that by executing the .bin installer. &#039;&#039;Hold that thought, qt2.5 creator RC doesn&#039;t have the deploy steps set up&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Within Qt creator you need to point it at your cross tool chain compiler+debugger:&lt;br /&gt;
#Tools-&amp;gt;Options-&amp;gt;Build&amp;amp;Run then Tool Chains&lt;br /&gt;
#then select add, in the drop-down pick GCC&lt;br /&gt;
#Select GCC and browse for compiler to&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gcc&lt;br /&gt;
and for the debugger&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gdb&lt;br /&gt;
Save these selections by clicking Apply and OK&lt;br /&gt;
&lt;br /&gt;
==Virtual Raspberry Pi Setup==&lt;br /&gt;
As I don&#039;t have a rpi yet I used qemu to do some initial testing.&lt;br /&gt;
My setup was a 12.04 VM.&lt;br /&gt;
You can either install qemu&lt;br /&gt;
 sudo apt-get install qemu-system&lt;br /&gt;
Or you can build qemu from git. You only need to do this if the qemu on your distro doesn&#039;t support the Broadcom SOC (ARM1176 core) on the Pi.&lt;br /&gt;
In order to boot your image you will need a suitable kernel for your emulator, there is one available here http://dl.dropbox.com/u/45842273/zImage_3.1.9 &lt;br /&gt;
Boot your virtual Pi &lt;br /&gt;
 qemu-system-arm -kernel kernel-qemu -cpu arm1176 -m 256 -M versatilepb -no-reboot -serial stdio -append &amp;quot;root=/dev/sda2 rw panic=1&amp;quot; qtonpi-sdcard-0.2.img -redir tcp:5022::22&lt;br /&gt;
&lt;br /&gt;
add&lt;br /&gt;
 console=ttyAMA0&lt;br /&gt;
to the -append param to have the boot console re-directed to the terminal.&lt;br /&gt;
&lt;br /&gt;
the -redir tcp:5022::22 redirects port 22 (ssh) on the virtual Pi to port 5022 on the host enabling you to ssh in.&lt;br /&gt;
 ssh pi@localhost -p5022&lt;br /&gt;
==Raspberry Pi Setup==&lt;br /&gt;
I used the image I was using above and wrote it to an SD card.&#039;&#039;If you are on windows make sure your machine can handle larger cards&#039;&#039;&lt;br /&gt;
By default the qtonpi release doesn&#039;t have the network if enabled. On each boot you can run&lt;br /&gt;
 ifup eth0&lt;br /&gt;
or&lt;br /&gt;
 dhclient eth0&lt;br /&gt;
or&lt;br /&gt;
 just edit /etc/sysconfic/network-scripts/ifcfg-eth0 and set the ONBOOT option equal to YES and be done with it.&lt;br /&gt;
&lt;br /&gt;
Also you need to set the time and date after each boot - no RTC on the rPi&lt;br /&gt;
==qOrbiter on Pi==&lt;br /&gt;
===Status===&lt;br /&gt;
&#039;&#039;28/05/2012&#039;&#039; - Unfortunately I have not been able to get my compiled qOrbiter to run on my virtual setup.&lt;br /&gt;
Depending on the combination of kernel I use and/or SD image I either get an illegal instruction or and error creating a vchiq instance.&lt;br /&gt;
&lt;br /&gt;
And given that the vchiq lib stuff is to do with the GPU, which is initialised in firmware, this may be a bit of an impass until I get actual hardware.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;30/05/2012&#039;&#039; - Have just received my rPi and my previously compiled qOrbiter starts and gets past the vchiq/illegal instruction I had.&lt;br /&gt;
I have other issues before I get it going but all going in the right direction.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;02/06/2012&#039;&#039; - qOrbiter splash screen loads, communicates with dcerouter, gets config - then boom my network dies. I don&#039;t know if its rPi specific or some porting issue with qOrbiter. I see &#039;&#039;smsc95xx 1-1.1:1.0: eth0: kevent 2 may have been dropped&#039;&#039; scroll past me. My ssh connection dies as a result so I need to be logged in on the rPi. Needs more investigation...&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;06/06/2012&#039;&#039; - got past n/w problem, now home screen loads. Also had to disable qml screen saver. The shader effect component is supposed to be available via QtQuick 2.0 and not need the labs plugin, but this appears not to be the case. It is likely it is just not in the snapshot yet.&lt;br /&gt;
&lt;br /&gt;
===Code Changes===&lt;br /&gt;
According to the current Qt Documentation adding&lt;br /&gt;
 greaterThan(QT_MAJOR_VERSION, 4) {&lt;br /&gt;
        QT += widgets&lt;br /&gt;
        QT += quick1&lt;br /&gt;
    } else {&lt;br /&gt;
        QT += declarative&lt;br /&gt;
    }&lt;br /&gt;
to the pro file loads the correct modules for both Qt4/Qt5.&lt;br /&gt;
At the moment my code and svn differ and not in a nice way - once I get everything #ifdef&#039;d into place I&#039;ll either stick a patch here or check it in with golgoj4 approval :)&lt;br /&gt;
&lt;br /&gt;
===&amp;quot;Useful&amp;quot; Qt links===&lt;br /&gt;
http://qt-project.org/wiki/Transition_from_Qt_4.x_to_Qt5&lt;br /&gt;
&lt;br /&gt;
https://qt-project.org/wiki/New_Signal_Slot_Syntax&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/Qt-5Features&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/QML1-vs-QML2&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi distros==&lt;br /&gt;
Looking at http://elinux.org/RPi_Distributions there are quite a few to choose from.&lt;br /&gt;
&lt;br /&gt;
Which is the best fit? I don&#039;t know.&lt;br /&gt;
&lt;br /&gt;
I&#039;m starting with QtonPi but I don&#039;t know if a full fedora release is necessary.&lt;br /&gt;
&#039;&#039;This is actually a trimmed down fedora release no X, graphics written direct to fb&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Mer/Meego might be a good fit too.&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31339</id>
		<title>RaspberryPi qOrbiter</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31339"/>
		<updated>2012-06-03T12:58:09Z</updated>

		<summary type="html">&lt;p&gt;Coley: qml1 vs qml2 module includes&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Device Specification==&lt;br /&gt;
-The Raspberry Pi is an ARM based computer the size of a credit card.  700Mhz, 256MB RAM, Ethernet, 2xUSB, GPIO&lt;br /&gt;
&lt;br /&gt;
-256MB of RAM is insufficient to build lmce.  MakeRelease and MakeRelease_PrepFiles both fail with out of memory errors due to the limited memory available on the RPi.&lt;br /&gt;
-Cross-compiling will be required.  More notes to follow.&lt;br /&gt;
&lt;br /&gt;
==Cross Compilation setup==&lt;br /&gt;
Initially this section will have information specific to getting Qt on Pi going. Its pre-packaged and fairly easy to install.&lt;br /&gt;
&lt;br /&gt;
At the time of writing Qt on Pi tarball is at version 0.2.&lt;br /&gt;
Get the tarball here http://www.raspberrypi.org/downloads at the bottom of the page. This has a premade SD image plus the toolchain and sysroot install required for cross compilation.&lt;br /&gt;
&lt;br /&gt;
===If you are about to install this on your current machine with a working Qt development environment DON&#039;T===&lt;br /&gt;
You will need to either set up a VM or a chroot environment as the qt5 shipped with this image isn&#039;t setup to install alongside an x86 install. They plan on having these play nice in future releases.&lt;br /&gt;
&lt;br /&gt;
==Qt5, Toolchain and sysroot install==&lt;br /&gt;
This is documented on the QtonPi wiki but basically after you have downloaded the qtonpi tarball extract the three files within.&lt;br /&gt;
Then as root extract [opt-qt5-current.tar.bz2] and [toolchain-and-sysroot-armv5tel.tar.bz2] &lt;br /&gt;
 $ cd /&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/opt-qt5-current.tar.bz2&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/toolchain-and-sysroot-armv5tel.tar.bz2&lt;br /&gt;
&lt;br /&gt;
===Qt creator===&lt;br /&gt;
The tarball comes with a recent version of qtcreator, but since then qt2.5 RC has come out, Should be safe enough to use that instead. Just install that by executing the .bin installer. &#039;&#039;Hold that thought, qt2.5 creator RC doesn&#039;t have the deploy steps set up&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Within Qt creator you need to point it at your cross tool chain compiler+debugger:&lt;br /&gt;
#Tools-&amp;gt;Options-&amp;gt;Build&amp;amp;Run then Tool Chains&lt;br /&gt;
#then select add, in the drop-down pick GCC&lt;br /&gt;
#Select GCC and browse for compiler to&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gcc&lt;br /&gt;
and for the debugger&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gdb&lt;br /&gt;
Save these selections by clicking Apply and OK&lt;br /&gt;
&lt;br /&gt;
==Virtual Raspberry Pi Setup==&lt;br /&gt;
As I don&#039;t have a rpi yet I used qemu to do some initial testing.&lt;br /&gt;
My setup was a 12.04 VM.&lt;br /&gt;
You can either install qemu&lt;br /&gt;
 sudo apt-get install qemu-system&lt;br /&gt;
Or you can build qemu from git. You only need to do this if the qemu on your distro doesn&#039;t support the Broadcom SOC (ARM1176 core) on the Pi.&lt;br /&gt;
In order to boot your image you will need a suitable kernel for your emulator, there is one available here http://dl.dropbox.com/u/45842273/zImage_3.1.9 &lt;br /&gt;
Boot your virtual Pi &lt;br /&gt;
 qemu-system-arm -kernel kernel-qemu -cpu arm1176 -m 256 -M versatilepb -no-reboot -serial stdio -append &amp;quot;root=/dev/sda2 rw panic=1&amp;quot; qtonpi-sdcard-0.2.img -redir tcp:5022::22&lt;br /&gt;
&lt;br /&gt;
add&lt;br /&gt;
 console=ttyAMA0&lt;br /&gt;
to the -append param to have the boot console re-directed to the terminal.&lt;br /&gt;
&lt;br /&gt;
the -redir tcp:5022::22 redirects port 22 (ssh) on the virtual Pi to port 5022 on the host enabling you to ssh in.&lt;br /&gt;
 ssh pi@localhost -p5022&lt;br /&gt;
==Raspberry Pi Setup==&lt;br /&gt;
I used the image I was using above and wrote it to an SD card.&#039;&#039;If you are on windows make sure your machine can handle larger cards&#039;&#039;&lt;br /&gt;
By default the qtonpi release doesn&#039;t have the network if enabled. On each boot you can run&lt;br /&gt;
 ifup eth0&lt;br /&gt;
or&lt;br /&gt;
 dhclient eth0&lt;br /&gt;
or&lt;br /&gt;
 just edit /etc/sysconfic/network-scripts/ifcfg-eth0 and set the ONBOOT option equal to YES and be done with it.&lt;br /&gt;
&lt;br /&gt;
Also you need to set the time and date after each boot - no RTC on the rPi&lt;br /&gt;
==qOrbiter on Pi==&lt;br /&gt;
===Status===&lt;br /&gt;
&#039;&#039;28/05/2012&#039;&#039; - Unfortunately I have not been able to get my compiled qOrbiter to run on my virtual setup.&lt;br /&gt;
Depending on the combination of kernel I use and/or SD image I either get an illegal instruction or and error creating a vchiq instance.&lt;br /&gt;
&lt;br /&gt;
And given that the vchiq lib stuff is to do with the GPU, which is initialised in firmware, this may be a bit of an impass until I get actual hardware.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;30/05/2012&#039;&#039; - Have just received my rPi and my previously compiled qOrbiter starts and gets past the vchiq/illegal instruction I had.&lt;br /&gt;
I have other issues before I get it going but all going in the right direction.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;02/06/2012&#039;&#039; - qOrbiter splash screen loads, communicates with dcerouter, gets config - then boom my network dies. I don&#039;t know if its rPi specific or some porting issue with qOrbiter. I see &#039;&#039;smsc95xx 1-1.1:1.0: eth0: kevent 2 may have been dropped&#039;&#039; scroll past me. My ssh connection dies as a result so I need to be logged in on the rPi. Needs more investigation...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Code Changes===&lt;br /&gt;
According to the current Qt Documentation adding&lt;br /&gt;
 greaterThan(QT_MAJOR_VERSION, 4) {&lt;br /&gt;
        QT += widgets&lt;br /&gt;
        QT += quick1&lt;br /&gt;
    } else {&lt;br /&gt;
        QT += declarative&lt;br /&gt;
    }&lt;br /&gt;
to the pro file loads the correct modules for both Qt4/Qt5.&lt;br /&gt;
At the moment my code and svn differ and not in a nice way - once I get everything #ifdef&#039;d into place I&#039;ll either stick a patch here or check it in with golgoj4 approval :)&lt;br /&gt;
&lt;br /&gt;
===&amp;quot;Useful&amp;quot; Qt links===&lt;br /&gt;
http://qt-project.org/wiki/Transition_from_Qt_4.x_to_Qt5&lt;br /&gt;
&lt;br /&gt;
https://qt-project.org/wiki/New_Signal_Slot_Syntax&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/Qt-5Features&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/QML1-vs-QML2&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi distros==&lt;br /&gt;
Looking at http://elinux.org/RPi_Distributions there are quite a few to choose from.&lt;br /&gt;
&lt;br /&gt;
Which is the best fit? I don&#039;t know.&lt;br /&gt;
&lt;br /&gt;
I&#039;m starting with QtonPi but I don&#039;t know if a full fedora release is necessary.&lt;br /&gt;
&#039;&#039;This is actually a trimmed down fedora release no X, graphics written direct to fb&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Mer/Meego might be a good fit too.&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31330</id>
		<title>RaspberryPi qOrbiter</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31330"/>
		<updated>2012-06-02T16:56:43Z</updated>

		<summary type="html">&lt;p&gt;Coley: status update and links added for safe-keeping&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Device Specification==&lt;br /&gt;
-The Raspberry Pi is an ARM based computer the size of a credit card.  700Mhz, 256MB RAM, Ethernet, 2xUSB, GPIO&lt;br /&gt;
&lt;br /&gt;
-256MB of RAM is insufficient to build lmce.  MakeRelease and MakeRelease_PrepFiles both fail with out of memory errors due to the limited memory available on the RPi.&lt;br /&gt;
-Cross-compiling will be required.  More notes to follow.&lt;br /&gt;
&lt;br /&gt;
==Cross Compilation setup==&lt;br /&gt;
Initially this section will have information specific to getting Qt on Pi going. Its pre-packaged and fairly easy to install.&lt;br /&gt;
&lt;br /&gt;
At the time of writing Qt on Pi tarball is at version 0.2.&lt;br /&gt;
Get the tarball here http://www.raspberrypi.org/downloads at the bottom of the page. This has a premade SD image plus the toolchain and sysroot install required for cross compilation.&lt;br /&gt;
&lt;br /&gt;
===If you are about to install this on your current machine with a working Qt development environment DON&#039;T===&lt;br /&gt;
You will need to either set up a VM or a chroot environment as the qt5 shipped with this image isn&#039;t setup to install alongside an x86 install. They plan on having these play nice in future releases.&lt;br /&gt;
&lt;br /&gt;
==Qt5, Toolchain and sysroot install==&lt;br /&gt;
This is documented on the QtonPi wiki but basically after you have downloaded the qtonpi tarball extract the three files within.&lt;br /&gt;
Then as root extract [opt-qt5-current.tar.bz2] and [toolchain-and-sysroot-armv5tel.tar.bz2] &lt;br /&gt;
 $ cd /&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/opt-qt5-current.tar.bz2&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/toolchain-and-sysroot-armv5tel.tar.bz2&lt;br /&gt;
&lt;br /&gt;
===Qt creator===&lt;br /&gt;
The tarball comes with a recent version of qtcreator, but since then qt2.5 RC has come out, Should be safe enough to use that instead. Just install that by executing the .bin installer. &#039;&#039;Hold that thought, qt2.5 creator RC doesn&#039;t have the deploy steps set up&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Within Qt creator you need to point it at your cross tool chain compiler+debugger:&lt;br /&gt;
#Tools-&amp;gt;Options-&amp;gt;Build&amp;amp;Run then Tool Chains&lt;br /&gt;
#then select add, in the drop-down pick GCC&lt;br /&gt;
#Select GCC and browse for compiler to&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gcc&lt;br /&gt;
and for the debugger&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gdb&lt;br /&gt;
Save these selections by clicking Apply and OK&lt;br /&gt;
&lt;br /&gt;
==Virtual Raspberry Pi Setup==&lt;br /&gt;
As I don&#039;t have a rpi yet I used qemu to do some initial testing.&lt;br /&gt;
My setup was a 12.04 VM.&lt;br /&gt;
You can either install qemu&lt;br /&gt;
 sudo apt-get install qemu-system&lt;br /&gt;
Or you can build qemu from git. You only need to do this if the qemu on your distro doesn&#039;t support the Broadcom SOC (ARM1176 core) on the Pi.&lt;br /&gt;
In order to boot your image you will need a suitable kernel for your emulator, there is one available here http://dl.dropbox.com/u/45842273/zImage_3.1.9 &lt;br /&gt;
Boot your virtual Pi &lt;br /&gt;
 qemu-system-arm -kernel kernel-qemu -cpu arm1176 -m 256 -M versatilepb -no-reboot -serial stdio -append &amp;quot;root=/dev/sda2 rw panic=1&amp;quot; qtonpi-sdcard-0.2.img -redir tcp:5022::22&lt;br /&gt;
&lt;br /&gt;
add&lt;br /&gt;
 console=ttyAMA0&lt;br /&gt;
to the -append param to have the boot console re-directed to the terminal.&lt;br /&gt;
&lt;br /&gt;
the -redir tcp:5022::22 redirects port 22 (ssh) on the virtual Pi to port 5022 on the host enabling you to ssh in.&lt;br /&gt;
 ssh pi@localhost -p5022&lt;br /&gt;
==Raspberry Pi Setup==&lt;br /&gt;
I used the image I was using above and wrote it to an SD card.&#039;&#039;If you are on windows make sure your machine can handle larger cards&#039;&#039;&lt;br /&gt;
By default the qtonpi release doesn&#039;t have the network if enabled. On each boot you can run&lt;br /&gt;
 ifup eth0&lt;br /&gt;
or&lt;br /&gt;
 dhclient eth0&lt;br /&gt;
or&lt;br /&gt;
 just edit /etc/sysconfic/network-scripts/ifcfg-eth0 and set the ONBOOT option equal to YES and be done with it.&lt;br /&gt;
&lt;br /&gt;
Also you need to set the time and date after each boot - no RTC on the rPi&lt;br /&gt;
==qOrbiter on Pi==&lt;br /&gt;
===Status===&lt;br /&gt;
&#039;&#039;28/05/2012&#039;&#039; - Unfortunately I have not been able to get my compiled qOrbiter to run on my virtual setup.&lt;br /&gt;
Depending on the combination of kernel I use and/or SD image I either get an illegal instruction or and error creating a vchiq instance.&lt;br /&gt;
&lt;br /&gt;
And given that the vchiq lib stuff is to do with the GPU, which is initialised in firmware, this may be a bit of an impass until I get actual hardware.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;30/05/2012&#039;&#039; - Have just received my rPi and my previously compiled qOrbiter starts and gets past the vchiq/illegal instruction I had.&lt;br /&gt;
I have other issues before I get it going but all going in the right direction.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;02/06/2012&#039;&#039; - qOrbiter splash screen loads, communicates with dcerouter, gets config - then boom my network dies. I don&#039;t know if its rPi specific or some porting issue with qOrbiter. I see &#039;&#039;smsc95xx 1-1.1:1.0: eth0: kevent 2 may have been dropped&#039;&#039; scroll past me. My ssh connection dies as a result so I need to be logged in on the rPi. Needs more investigation...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Code Changes===&lt;br /&gt;
According to the current Qt Documentation adding&lt;br /&gt;
 greaterThan(QT_MAJOR_VERSION, 4) {&lt;br /&gt;
        QT += widgets&lt;br /&gt;
        QT += quick1&lt;br /&gt;
    } else {&lt;br /&gt;
        QT += declarative&lt;br /&gt;
    }&lt;br /&gt;
to the pro file loads the correct modules for both Qt4/Qt5.&lt;br /&gt;
At the moment my code and svn differ and not in a nice way - once I get everything #ifdef&#039;d into place I&#039;ll either stick a patch here or check it in with golgoj4 approval :)&lt;br /&gt;
&lt;br /&gt;
===&amp;quot;Useful&amp;quot; Qt links===&lt;br /&gt;
http://qt-project.org/wiki/Transition_from_Qt_4.x_to_Qt5&lt;br /&gt;
&lt;br /&gt;
https://qt-project.org/wiki/New_Signal_Slot_Syntax&lt;br /&gt;
&lt;br /&gt;
http://qt-project.org/wiki/Qt-5Features&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi distros==&lt;br /&gt;
Looking at http://elinux.org/RPi_Distributions there are quite a few to choose from.&lt;br /&gt;
&lt;br /&gt;
Which is the best fit? I don&#039;t know.&lt;br /&gt;
&lt;br /&gt;
I&#039;m starting with QtonPi but I don&#039;t know if a full fedora release is necessary.&lt;br /&gt;
&#039;&#039;This is actually a trimmed down fedora release no X, graphics written direct to fb&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Mer/Meego might be a good fit too.&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31294</id>
		<title>RaspberryPi qOrbiter</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31294"/>
		<updated>2012-05-31T23:36:49Z</updated>

		<summary type="html">&lt;p&gt;Coley: added some details on actual Raspberry Pi setup&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Device Specification==&lt;br /&gt;
-The Raspberry Pi is an ARM based computer the size of a credit card.  700Mhz, 256MB RAM, Ethernet, 2xUSB, GPIO&lt;br /&gt;
&lt;br /&gt;
-256MB of RAM is insufficient to build lmce.  MakeRelease and MakeRelease_PrepFiles both fail with out of memory errors due to the limited memory available on the RPi.&lt;br /&gt;
-Cross-compiling will be required.  More notes to follow.&lt;br /&gt;
&lt;br /&gt;
==Cross Compilation setup==&lt;br /&gt;
Initially this section will have information specific to getting Qt on Pi going. Its pre-packaged and fairly easy to install.&lt;br /&gt;
&lt;br /&gt;
At the time of writing Qt on Pi tarball is at version 0.2.&lt;br /&gt;
Get the tarball here http://www.raspberrypi.org/downloads at the bottom of the page. This has a premade SD image plus the toolchain and sysroot install required for cross compilation.&lt;br /&gt;
&lt;br /&gt;
===If you are about to install this on your current machine with a working Qt development environment DON&#039;T===&lt;br /&gt;
You will need to either set up a VM or a chroot environment as the qt5 shipped with this image isn&#039;t setup to install alongside an x86 install. They plan on having these play nice in future releases.&lt;br /&gt;
&lt;br /&gt;
===Qt5, Toolchain and sysroot install===&lt;br /&gt;
This is documented on the QtonPi wiki but basically after you have downloaded the qtonpi tarball extract the three files within.&lt;br /&gt;
Then as root extract [opt-qt5-current.tar.bz2] and [toolchain-and-sysroot-armv5tel.tar.bz2] &lt;br /&gt;
 $ cd /&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/opt-qt5-current.tar.bz2&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/toolchain-and-sysroot-armv5tel.tar.bz2&lt;br /&gt;
&lt;br /&gt;
===Qt creator===&lt;br /&gt;
The tarball comes with a recent version of qtcreator, but since then qt2.5 RC has come out, Should be safe enough to use that instead. Just install that by executing the .bin installer. &#039;&#039;Hold that thought, qt2.5 creator RC doesn&#039;t have the deploy steps set up&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Within Qt creator you need to point it at your cross tool chain compiler+debugger:&lt;br /&gt;
#Tools-&amp;gt;Options-&amp;gt;Build&amp;amp;Run then Tool Chains&lt;br /&gt;
#then select add, in the drop-down pick GCC&lt;br /&gt;
#Select GCC and browse for compiler to&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gcc&lt;br /&gt;
and for the debugger&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gdb&lt;br /&gt;
Save these selections by clicking Apply and OK&lt;br /&gt;
&lt;br /&gt;
==Virtual Raspberry Pi Setup==&lt;br /&gt;
As I don&#039;t have a rpi yet I used qemu to do some initial testing.&lt;br /&gt;
My setup was a 12.04 VM.&lt;br /&gt;
You can either install qemu&lt;br /&gt;
 sudo apt-get install qemu-system&lt;br /&gt;
Or you can build qemu from git. You only need to do this if the qemu on your distro doesn&#039;t support the Broadcom SOC (ARM1176 core) on the Pi.&lt;br /&gt;
In order to boot your image you will need a suitable kernel for your emulator, there is one available here http://dl.dropbox.com/u/45842273/zImage_3.1.9 &lt;br /&gt;
Boot your virtual Pi &lt;br /&gt;
 qemu-system-arm -kernel kernel-qemu -cpu arm1176 -m 256 -M versatilepb -no-reboot -serial stdio -append &amp;quot;root=/dev/sda2 rw panic=1&amp;quot; qtonpi-sdcard-0.2.img -redir tcp:5022::22&lt;br /&gt;
&lt;br /&gt;
add&lt;br /&gt;
 console=ttyAMA0&lt;br /&gt;
to the -append param to have the boot console re-directed to the terminal.&lt;br /&gt;
&lt;br /&gt;
the -redir tcp:5022::22 redirects port 22 (ssh) on the virtual Pi to port 5022 on the host enabling you to ssh in.&lt;br /&gt;
 ssh pi@localhost -p5022&lt;br /&gt;
==Raspberry Pi Setup==&lt;br /&gt;
I used the image I was using above and wrote it to an SD card.&#039;&#039;If you are on windows make sure your machine can handle larger cards&#039;&#039;&lt;br /&gt;
By default the qtonpi release doesn&#039;t have the network if enabled. On each boot you can run&lt;br /&gt;
 ifup eth0&lt;br /&gt;
or&lt;br /&gt;
 dhclient eth0&lt;br /&gt;
or&lt;br /&gt;
 just edit /etc/sysconfic/network-scripts/ifcfg-eth0 and set the ONBOOT option equal to YES and be done with it.&lt;br /&gt;
&lt;br /&gt;
Also you need to set the time and date after each boot - no RTC on the rPi&lt;br /&gt;
==qOrbiter on Pi==&lt;br /&gt;
===Status===&lt;br /&gt;
&#039;&#039;28/05/2012&#039;&#039; - Unfortunately I have not been able to get my compiled qOrbiter to run on my virtual setup.&lt;br /&gt;
Depending on the combination of kernel I use and/or SD image I either get an illegal instruction or and error creating a vchiq instance.&lt;br /&gt;
&lt;br /&gt;
And given that the vchiq lib stuff is to do with the GPU, which is initialised in firmware, this may be a bit of an impass until I get actual hardware.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;30/05/2012&#039;&#039; - Have just received my rPi and my previously compiled qOrbiter starts and gets past the vchiq/illegal instruction I had.&lt;br /&gt;
I have other issues before I get it going but all going in the right direction.&lt;br /&gt;
&lt;br /&gt;
===Code Changes===&lt;br /&gt;
According to the current Qt Documentation adding&lt;br /&gt;
 greaterThan(QT_MAJOR_VERSION, 4) {&lt;br /&gt;
        QT += widgets&lt;br /&gt;
        QT += quick1&lt;br /&gt;
    } else {&lt;br /&gt;
        QT += declarative&lt;br /&gt;
    }&lt;br /&gt;
to the pro file loads the correct modules for both Qt4/Qt5.&lt;br /&gt;
At the moment my code and svn differ and not in a nice way - once I get everything #ifdef&#039;d into place I&#039;ll either stick a patch here or check it in with golgoj4 approval :)&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi distros==&lt;br /&gt;
Looking at http://elinux.org/RPi_Distributions there are quite a few to choose from.&lt;br /&gt;
&lt;br /&gt;
Which is the best fit? I don&#039;t know.&lt;br /&gt;
&lt;br /&gt;
I&#039;m starting with QtonPi but I don&#039;t know if a full fedora release is necessary.&lt;br /&gt;
&#039;&#039;This is actually a trimmed down fedora release no X, graphics written direct to fb&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Mer/Meego might be a good fit too.&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31293</id>
		<title>RaspberryPi qOrbiter</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31293"/>
		<updated>2012-05-31T23:18:55Z</updated>

		<summary type="html">&lt;p&gt;Coley: /* Status */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Device Specification==&lt;br /&gt;
-The Raspberry Pi is an ARM based computer the size of a credit card.  700Mhz, 256MB RAM, Ethernet, 2xUSB, GPIO&lt;br /&gt;
&lt;br /&gt;
-256MB of RAM is insufficient to build lmce.  MakeRelease and MakeRelease_PrepFiles both fail with out of memory errors due to the limited memory available on the RPi.&lt;br /&gt;
-Cross-compiling will be required.  More notes to follow.&lt;br /&gt;
&lt;br /&gt;
==Cross Compilation setup==&lt;br /&gt;
Initially this section will have information specific to getting Qt on Pi going. Its pre-packaged and fairly easy to install.&lt;br /&gt;
&lt;br /&gt;
At the time of writing Qt on Pi tarball is at version 0.2.&lt;br /&gt;
Get the tarball here http://www.raspberrypi.org/downloads at the bottom of the page. This has a premade SD image plus the toolchain and sysroot install required for cross compilation.&lt;br /&gt;
&lt;br /&gt;
===If you are about to install this on your current machine with a working Qt development environment DON&#039;T===&lt;br /&gt;
You will need to either set up a VM or a chroot environment as the qt5 shipped with this image isn&#039;t setup to install alongside an x86 install. They plan on having these play nice in future releases.&lt;br /&gt;
&lt;br /&gt;
===Qt5, Toolchain and sysroot install===&lt;br /&gt;
This is documented on the QtonPi wiki but basically after you have downloaded the qtonpi tarball extract the three files within.&lt;br /&gt;
Then as root extract [opt-qt5-current.tar.bz2] and [toolchain-and-sysroot-armv5tel.tar.bz2] &lt;br /&gt;
 $ cd /&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/opt-qt5-current.tar.bz2&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/toolchain-and-sysroot-armv5tel.tar.bz2&lt;br /&gt;
&lt;br /&gt;
===Qt creator===&lt;br /&gt;
The tarball comes with a recent version of qtcreator, but since then qt2.5 RC has come out, Should be safe enough to use that instead. Just install that by executing the .bin installer. &#039;&#039;Hold that thought, qt2.5 creator RC doesn&#039;t have the deploy steps set up&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Within Qt creator you need to point it at your cross tool chain compiler+debugger:&lt;br /&gt;
#Tools-&amp;gt;Options-&amp;gt;Build&amp;amp;Run then Tool Chains&lt;br /&gt;
#then select add, in the drop-down pick GCC&lt;br /&gt;
#Select GCC and browse for compiler to&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gcc&lt;br /&gt;
and for the debugger&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gdb&lt;br /&gt;
Save these selections by clicking Apply and OK&lt;br /&gt;
&lt;br /&gt;
==Virtual Raspberry Pi Setup==&lt;br /&gt;
As I don&#039;t have a rpi yet I used qemu to do some initial testing.&lt;br /&gt;
My setup was a 12.04 VM.&lt;br /&gt;
You can either install qemu&lt;br /&gt;
 sudo apt-get install qemu-system&lt;br /&gt;
Or you can build qemu from git. You only need to do this if the qemu on your distro doesn&#039;t support the Broadcom SOC (ARM1176 core) on the Pi.&lt;br /&gt;
In order to boot your image you will need a suitable kernel for your emulator, there is one available here http://dl.dropbox.com/u/45842273/zImage_3.1.9 &lt;br /&gt;
Boot your virtual Pi &lt;br /&gt;
 qemu-system-arm -kernel kernel-qemu -cpu arm1176 -m 256 -M versatilepb -no-reboot -serial stdio -append &amp;quot;root=/dev/sda2 rw panic=1&amp;quot; qtonpi-sdcard-0.2.img -redir tcp:5022::22&lt;br /&gt;
&lt;br /&gt;
add&lt;br /&gt;
 console=ttyAMA0&lt;br /&gt;
to the -append param to have the boot console re-directed to the terminal.&lt;br /&gt;
&lt;br /&gt;
the -redir tcp:5022::22 redirects port 22 (ssh) on the virtual Pi to port 5022 on the host enabling you to ssh in.&lt;br /&gt;
 ssh pi@localhost -p5022&lt;br /&gt;
&lt;br /&gt;
==qOrbiter on Pi==&lt;br /&gt;
===Status===&lt;br /&gt;
&#039;&#039;28/05/2012&#039;&#039; - Unfortunately I have not been able to get my compiled qOrbiter to run on my virtual setup.&lt;br /&gt;
Depending on the combination of kernel I use and/or SD image I either get an illegal instruction or and error creating a vchiq instance.&lt;br /&gt;
&lt;br /&gt;
And given that the vchiq lib stuff is to do with the GPU, which is initialised in firmware, this may be a bit of an impass until I get actual hardware.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;30/05/2012&#039;&#039; - Have just received my rPi and my previously compiled qOrbiter starts and gets past the vchiq/illegal instruction I had.&lt;br /&gt;
I have other issues before I get it going but all going in the right direction.&lt;br /&gt;
&lt;br /&gt;
===Code Changes===&lt;br /&gt;
According to the current Qt Documentation adding&lt;br /&gt;
 greaterThan(QT_MAJOR_VERSION, 4) {&lt;br /&gt;
        QT += widgets&lt;br /&gt;
        QT += quick1&lt;br /&gt;
    } else {&lt;br /&gt;
        QT += declarative&lt;br /&gt;
    }&lt;br /&gt;
to the pro file loads the correct modules for both Qt4/Qt5.&lt;br /&gt;
At the moment my code and svn differ and not in a nice way - once I get everything #ifdef&#039;d into place I&#039;ll either stick a patch here or check it in with golgoj4 approval :)&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi distros==&lt;br /&gt;
Looking at http://elinux.org/RPi_Distributions there are quite a few to choose from.&lt;br /&gt;
&lt;br /&gt;
Which is the best fit? I don&#039;t know.&lt;br /&gt;
&lt;br /&gt;
I&#039;m starting with QtonPi but I don&#039;t know if a full fedora release is necessary.&lt;br /&gt;
&#039;&#039;This is actually a trimmed down fedora release no X, graphics written direct to fb&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Mer/Meego might be a good fit too.&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31292</id>
		<title>RaspberryPi qOrbiter</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31292"/>
		<updated>2012-05-31T23:16:25Z</updated>

		<summary type="html">&lt;p&gt;Coley: /* Raspberry Pi Setup */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Device Specification==&lt;br /&gt;
-The Raspberry Pi is an ARM based computer the size of a credit card.  700Mhz, 256MB RAM, Ethernet, 2xUSB, GPIO&lt;br /&gt;
&lt;br /&gt;
-256MB of RAM is insufficient to build lmce.  MakeRelease and MakeRelease_PrepFiles both fail with out of memory errors due to the limited memory available on the RPi.&lt;br /&gt;
-Cross-compiling will be required.  More notes to follow.&lt;br /&gt;
&lt;br /&gt;
==Cross Compilation setup==&lt;br /&gt;
Initially this section will have information specific to getting Qt on Pi going. Its pre-packaged and fairly easy to install.&lt;br /&gt;
&lt;br /&gt;
At the time of writing Qt on Pi tarball is at version 0.2.&lt;br /&gt;
Get the tarball here http://www.raspberrypi.org/downloads at the bottom of the page. This has a premade SD image plus the toolchain and sysroot install required for cross compilation.&lt;br /&gt;
&lt;br /&gt;
===If you are about to install this on your current machine with a working Qt development environment DON&#039;T===&lt;br /&gt;
You will need to either set up a VM or a chroot environment as the qt5 shipped with this image isn&#039;t setup to install alongside an x86 install. They plan on having these play nice in future releases.&lt;br /&gt;
&lt;br /&gt;
===Qt5, Toolchain and sysroot install===&lt;br /&gt;
This is documented on the QtonPi wiki but basically after you have downloaded the qtonpi tarball extract the three files within.&lt;br /&gt;
Then as root extract [opt-qt5-current.tar.bz2] and [toolchain-and-sysroot-armv5tel.tar.bz2] &lt;br /&gt;
 $ cd /&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/opt-qt5-current.tar.bz2&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/toolchain-and-sysroot-armv5tel.tar.bz2&lt;br /&gt;
&lt;br /&gt;
===Qt creator===&lt;br /&gt;
The tarball comes with a recent version of qtcreator, but since then qt2.5 RC has come out, Should be safe enough to use that instead. Just install that by executing the .bin installer. &#039;&#039;Hold that thought, qt2.5 creator RC doesn&#039;t have the deploy steps set up&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Within Qt creator you need to point it at your cross tool chain compiler+debugger:&lt;br /&gt;
#Tools-&amp;gt;Options-&amp;gt;Build&amp;amp;Run then Tool Chains&lt;br /&gt;
#then select add, in the drop-down pick GCC&lt;br /&gt;
#Select GCC and browse for compiler to&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gcc&lt;br /&gt;
and for the debugger&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gdb&lt;br /&gt;
Save these selections by clicking Apply and OK&lt;br /&gt;
&lt;br /&gt;
==Virtual Raspberry Pi Setup==&lt;br /&gt;
As I don&#039;t have a rpi yet I used qemu to do some initial testing.&lt;br /&gt;
My setup was a 12.04 VM.&lt;br /&gt;
You can either install qemu&lt;br /&gt;
 sudo apt-get install qemu-system&lt;br /&gt;
Or you can build qemu from git. You only need to do this if the qemu on your distro doesn&#039;t support the Broadcom SOC (ARM1176 core) on the Pi.&lt;br /&gt;
In order to boot your image you will need a suitable kernel for your emulator, there is one available here http://dl.dropbox.com/u/45842273/zImage_3.1.9 &lt;br /&gt;
Boot your virtual Pi &lt;br /&gt;
 qemu-system-arm -kernel kernel-qemu -cpu arm1176 -m 256 -M versatilepb -no-reboot -serial stdio -append &amp;quot;root=/dev/sda2 rw panic=1&amp;quot; qtonpi-sdcard-0.2.img -redir tcp:5022::22&lt;br /&gt;
&lt;br /&gt;
add&lt;br /&gt;
 console=ttyAMA0&lt;br /&gt;
to the -append param to have the boot console re-directed to the terminal.&lt;br /&gt;
&lt;br /&gt;
the -redir tcp:5022::22 redirects port 22 (ssh) on the virtual Pi to port 5022 on the host enabling you to ssh in.&lt;br /&gt;
 ssh pi@localhost -p5022&lt;br /&gt;
&lt;br /&gt;
==qOrbiter on Pi==&lt;br /&gt;
===Status===&lt;br /&gt;
&#039;&#039;28/05/2012&#039;&#039; - Unfortunately I have not been able to get my compiled qOrbiter to run on my virtual setup.&lt;br /&gt;
Depending on the combination of kernel I use and/or SD image I either get an illegal instruction or and error creating a vchiq instance.&lt;br /&gt;
&lt;br /&gt;
And given that the vchiq lib stuff is to do with the GPU, which is initialised in firmware, this may be a bit of an impass until I get actual hardware.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;30/05/2012&#039;&#039; - Have just receive my rPi and my previously compiled qOrbiter starts and gets past the vchiq/illegal instruction I had.&lt;br /&gt;
I have other issues before I get it going but all going in the right direction.&lt;br /&gt;
&lt;br /&gt;
===Code Changes===&lt;br /&gt;
According to the current Qt Documentation adding&lt;br /&gt;
 greaterThan(QT_MAJOR_VERSION, 4) {&lt;br /&gt;
        QT += widgets&lt;br /&gt;
        QT += quick1&lt;br /&gt;
    } else {&lt;br /&gt;
        QT += declarative&lt;br /&gt;
    }&lt;br /&gt;
to the pro file loads the correct modules for both Qt4/Qt5.&lt;br /&gt;
At the moment my code and svn differ and not in a nice way - once I get everything #ifdef&#039;d into place I&#039;ll either stick a patch here or check it in with golgoj4 approval :)&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi distros==&lt;br /&gt;
Looking at http://elinux.org/RPi_Distributions there are quite a few to choose from.&lt;br /&gt;
&lt;br /&gt;
Which is the best fit? I don&#039;t know.&lt;br /&gt;
&lt;br /&gt;
I&#039;m starting with QtonPi but I don&#039;t know if a full fedora release is necessary.&lt;br /&gt;
&#039;&#039;This is actually a trimmed down fedora release no X, graphics written direct to fb&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Mer/Meego might be a good fit too.&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31278</id>
		<title>RaspberryPi qOrbiter</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31278"/>
		<updated>2012-05-31T10:54:33Z</updated>

		<summary type="html">&lt;p&gt;Coley: /* Status */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Device Specification==&lt;br /&gt;
-The Raspberry Pi is an ARM based computer the size of a credit card.  700Mhz, 256MB RAM, Ethernet, 2xUSB, GPIO&lt;br /&gt;
&lt;br /&gt;
-256MB of RAM is insufficient to build lmce.  MakeRelease and MakeRelease_PrepFiles both fail with out of memory errors due to the limited memory available on the RPi.&lt;br /&gt;
-Cross-compiling will be required.  More notes to follow.&lt;br /&gt;
&lt;br /&gt;
==Cross Compilation setup==&lt;br /&gt;
Initially this section will have information specific to getting Qt on Pi going. Its pre-packaged and fairly easy to install.&lt;br /&gt;
&lt;br /&gt;
At the time of writing Qt on Pi tarball is at version 0.2.&lt;br /&gt;
Get the tarball here http://www.raspberrypi.org/downloads at the bottom of the page. This has a premade SD image plus the toolchain and sysroot install required for cross compilation.&lt;br /&gt;
&lt;br /&gt;
===If you are about to install this on your current machine with a working Qt development environment DON&#039;T===&lt;br /&gt;
You will need to either set up a VM or a chroot environment as the qt5 shipped with this image isn&#039;t setup to install alongside an x86 install. They plan on having these play nice in future releases.&lt;br /&gt;
&lt;br /&gt;
===Qt5, Toolchain and sysroot install===&lt;br /&gt;
This is documented on the QtonPi wiki but basically after you have downloaded the qtonpi tarball extract the three files within.&lt;br /&gt;
Then as root extract [opt-qt5-current.tar.bz2] and [toolchain-and-sysroot-armv5tel.tar.bz2] &lt;br /&gt;
 $ cd /&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/opt-qt5-current.tar.bz2&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/toolchain-and-sysroot-armv5tel.tar.bz2&lt;br /&gt;
&lt;br /&gt;
===Qt creator===&lt;br /&gt;
The tarball comes with a recent version of qtcreator, but since then qt2.5 RC has come out, Should be safe enough to use that instead. Just install that by executing the .bin installer. &#039;&#039;Hold that thought, qt2.5 creator RC doesn&#039;t have the deploy steps set up&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Within Qt creator you need to point it at your cross tool chain compiler+debugger:&lt;br /&gt;
#Tools-&amp;gt;Options-&amp;gt;Build&amp;amp;Run then Tool Chains&lt;br /&gt;
#then select add, in the drop-down pick GCC&lt;br /&gt;
#Select GCC and browse for compiler to&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gcc&lt;br /&gt;
and for the debugger&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gdb&lt;br /&gt;
Save these selections by clicking Apply and OK&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi Setup==&lt;br /&gt;
As I don&#039;t have a rpi yet I used qemu to do some initial testing.&lt;br /&gt;
My setup was a 12.04 VM.&lt;br /&gt;
You can either install qemu&lt;br /&gt;
 sudo apt-get install qemu-system&lt;br /&gt;
Or you can build qemu from git. You only need to do this if the qemu on your distro doesn&#039;t support the Broadcom SOC (ARM1176 core) on the Pi.&lt;br /&gt;
In order to boot your image you will need a suitable kernel for your emulator, there is one available here http://dl.dropbox.com/u/45842273/zImage_3.1.9 &lt;br /&gt;
Boot your virtual Pi &lt;br /&gt;
 qemu-system-arm -kernel kernel-qemu -cpu arm1176 -m 256 -M versatilepb -no-reboot -serial stdio -append &amp;quot;root=/dev/sda2 rw panic=1&amp;quot; qtonpi-sdcard-0.2.img -redir tcp:5022::22&lt;br /&gt;
&lt;br /&gt;
add&lt;br /&gt;
 console=ttyAMA0&lt;br /&gt;
to the -append param to have the boot console re-directed to the terminal.&lt;br /&gt;
&lt;br /&gt;
the -redir tcp:5022::22 redirects port 22 (ssh) on the virtual Pi to port 5022 on the host enabling you to ssh in.&lt;br /&gt;
 ssh pi@localhost -p5022&lt;br /&gt;
&lt;br /&gt;
==qOrbiter on Pi==&lt;br /&gt;
===Status===&lt;br /&gt;
&#039;&#039;28/05/2012&#039;&#039; - Unfortunately I have not been able to get my compiled qOrbiter to run on my virtual setup.&lt;br /&gt;
Depending on the combination of kernel I use and/or SD image I either get an illegal instruction or and error creating a vchiq instance.&lt;br /&gt;
&lt;br /&gt;
And given that the vchiq lib stuff is to do with the GPU, which is initialised in firmware, this may be a bit of an impass until I get actual hardware.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;30/05/2012&#039;&#039; - Have just receive my rPi and my previously compiled qOrbiter starts and gets past the vchiq/illegal instruction I had.&lt;br /&gt;
I have other issues before I get it going but all going in the right direction.&lt;br /&gt;
&lt;br /&gt;
===Code Changes===&lt;br /&gt;
According to the current Qt Documentation adding&lt;br /&gt;
 greaterThan(QT_MAJOR_VERSION, 4) {&lt;br /&gt;
        QT += widgets&lt;br /&gt;
        QT += quick1&lt;br /&gt;
    } else {&lt;br /&gt;
        QT += declarative&lt;br /&gt;
    }&lt;br /&gt;
to the pro file loads the correct modules for both Qt4/Qt5.&lt;br /&gt;
At the moment my code and svn differ and not in a nice way - once I get everything #ifdef&#039;d into place I&#039;ll either stick a patch here or check it in with golgoj4 approval :)&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi distros==&lt;br /&gt;
Looking at http://elinux.org/RPi_Distributions there are quite a few to choose from.&lt;br /&gt;
&lt;br /&gt;
Which is the best fit? I don&#039;t know.&lt;br /&gt;
&lt;br /&gt;
I&#039;m starting with QtonPi but I don&#039;t know if a full fedora release is necessary.&lt;br /&gt;
&#039;&#039;This is actually a trimmed down fedora release no X, graphics written direct to fb&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Mer/Meego might be a good fit too.&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31277</id>
		<title>RaspberryPi qOrbiter</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31277"/>
		<updated>2012-05-31T10:49:06Z</updated>

		<summary type="html">&lt;p&gt;Coley: /* Qt creator */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Device Specification==&lt;br /&gt;
-The Raspberry Pi is an ARM based computer the size of a credit card.  700Mhz, 256MB RAM, Ethernet, 2xUSB, GPIO&lt;br /&gt;
&lt;br /&gt;
-256MB of RAM is insufficient to build lmce.  MakeRelease and MakeRelease_PrepFiles both fail with out of memory errors due to the limited memory available on the RPi.&lt;br /&gt;
-Cross-compiling will be required.  More notes to follow.&lt;br /&gt;
&lt;br /&gt;
==Cross Compilation setup==&lt;br /&gt;
Initially this section will have information specific to getting Qt on Pi going. Its pre-packaged and fairly easy to install.&lt;br /&gt;
&lt;br /&gt;
At the time of writing Qt on Pi tarball is at version 0.2.&lt;br /&gt;
Get the tarball here http://www.raspberrypi.org/downloads at the bottom of the page. This has a premade SD image plus the toolchain and sysroot install required for cross compilation.&lt;br /&gt;
&lt;br /&gt;
===If you are about to install this on your current machine with a working Qt development environment DON&#039;T===&lt;br /&gt;
You will need to either set up a VM or a chroot environment as the qt5 shipped with this image isn&#039;t setup to install alongside an x86 install. They plan on having these play nice in future releases.&lt;br /&gt;
&lt;br /&gt;
===Qt5, Toolchain and sysroot install===&lt;br /&gt;
This is documented on the QtonPi wiki but basically after you have downloaded the qtonpi tarball extract the three files within.&lt;br /&gt;
Then as root extract [opt-qt5-current.tar.bz2] and [toolchain-and-sysroot-armv5tel.tar.bz2] &lt;br /&gt;
 $ cd /&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/opt-qt5-current.tar.bz2&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/toolchain-and-sysroot-armv5tel.tar.bz2&lt;br /&gt;
&lt;br /&gt;
===Qt creator===&lt;br /&gt;
The tarball comes with a recent version of qtcreator, but since then qt2.5 RC has come out, Should be safe enough to use that instead. Just install that by executing the .bin installer. &#039;&#039;Hold that thought, qt2.5 creator RC doesn&#039;t have the deploy steps set up&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Within Qt creator you need to point it at your cross tool chain compiler+debugger:&lt;br /&gt;
#Tools-&amp;gt;Options-&amp;gt;Build&amp;amp;Run then Tool Chains&lt;br /&gt;
#then select add, in the drop-down pick GCC&lt;br /&gt;
#Select GCC and browse for compiler to&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gcc&lt;br /&gt;
and for the debugger&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gdb&lt;br /&gt;
Save these selections by clicking Apply and OK&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi Setup==&lt;br /&gt;
As I don&#039;t have a rpi yet I used qemu to do some initial testing.&lt;br /&gt;
My setup was a 12.04 VM.&lt;br /&gt;
You can either install qemu&lt;br /&gt;
 sudo apt-get install qemu-system&lt;br /&gt;
Or you can build qemu from git. You only need to do this if the qemu on your distro doesn&#039;t support the Broadcom SOC (ARM1176 core) on the Pi.&lt;br /&gt;
In order to boot your image you will need a suitable kernel for your emulator, there is one available here http://dl.dropbox.com/u/45842273/zImage_3.1.9 &lt;br /&gt;
Boot your virtual Pi &lt;br /&gt;
 qemu-system-arm -kernel kernel-qemu -cpu arm1176 -m 256 -M versatilepb -no-reboot -serial stdio -append &amp;quot;root=/dev/sda2 rw panic=1&amp;quot; qtonpi-sdcard-0.2.img -redir tcp:5022::22&lt;br /&gt;
&lt;br /&gt;
add&lt;br /&gt;
 console=ttyAMA0&lt;br /&gt;
to the -append param to have the boot console re-directed to the terminal.&lt;br /&gt;
&lt;br /&gt;
the -redir tcp:5022::22 redirects port 22 (ssh) on the virtual Pi to port 5022 on the host enabling you to ssh in.&lt;br /&gt;
 ssh pi@localhost -p5022&lt;br /&gt;
&lt;br /&gt;
==qOrbiter on Pi==&lt;br /&gt;
===Status===&lt;br /&gt;
Unfortunately I have not been able to get my compiled qOrbiter to run on my virtual setup.&lt;br /&gt;
Depending on the combination of kernel I use and/or SD image I either get an illegal instruction or and error creating a vchiq instance.&lt;br /&gt;
&lt;br /&gt;
And given that the vchiq lib stuff is to do with the GPU, which is initialised in firmware, this may be a bit of an impass until I get actual hardware.&lt;br /&gt;
&lt;br /&gt;
===Code Changes===&lt;br /&gt;
According to the current Qt Documentation adding&lt;br /&gt;
 greaterThan(QT_MAJOR_VERSION, 4) {&lt;br /&gt;
        QT += widgets&lt;br /&gt;
        QT += quick1&lt;br /&gt;
    } else {&lt;br /&gt;
        QT += declarative&lt;br /&gt;
    }&lt;br /&gt;
to the pro file loads the correct modules for both Qt4/Qt5.&lt;br /&gt;
At the moment my code and svn differ and not in a nice way - once I get everything #ifdef&#039;d into place I&#039;ll either stick a patch here or check it in with golgoj4 approval :)&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi distros==&lt;br /&gt;
Looking at http://elinux.org/RPi_Distributions there are quite a few to choose from.&lt;br /&gt;
&lt;br /&gt;
Which is the best fit? I don&#039;t know.&lt;br /&gt;
&lt;br /&gt;
I&#039;m starting with QtonPi but I don&#039;t know if a full fedora release is necessary.&lt;br /&gt;
&#039;&#039;This is actually a trimmed down fedora release no X, graphics written direct to fb&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Mer/Meego might be a good fit too.&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
	<entry>
		<id>http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31276</id>
		<title>RaspberryPi qOrbiter</title>
		<link rel="alternate" type="text/html" href="http://wiki.linuxmce.org/index.php?title=RaspberryPi_qOrbiter&amp;diff=31276"/>
		<updated>2012-05-31T10:47:35Z</updated>

		<summary type="html">&lt;p&gt;Coley: /* Raspberry Pi distros */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Device Specification==&lt;br /&gt;
-The Raspberry Pi is an ARM based computer the size of a credit card.  700Mhz, 256MB RAM, Ethernet, 2xUSB, GPIO&lt;br /&gt;
&lt;br /&gt;
-256MB of RAM is insufficient to build lmce.  MakeRelease and MakeRelease_PrepFiles both fail with out of memory errors due to the limited memory available on the RPi.&lt;br /&gt;
-Cross-compiling will be required.  More notes to follow.&lt;br /&gt;
&lt;br /&gt;
==Cross Compilation setup==&lt;br /&gt;
Initially this section will have information specific to getting Qt on Pi going. Its pre-packaged and fairly easy to install.&lt;br /&gt;
&lt;br /&gt;
At the time of writing Qt on Pi tarball is at version 0.2.&lt;br /&gt;
Get the tarball here http://www.raspberrypi.org/downloads at the bottom of the page. This has a premade SD image plus the toolchain and sysroot install required for cross compilation.&lt;br /&gt;
&lt;br /&gt;
===If you are about to install this on your current machine with a working Qt development environment DON&#039;T===&lt;br /&gt;
You will need to either set up a VM or a chroot environment as the qt5 shipped with this image isn&#039;t setup to install alongside an x86 install. They plan on having these play nice in future releases.&lt;br /&gt;
&lt;br /&gt;
===Qt5, Toolchain and sysroot install===&lt;br /&gt;
This is documented on the QtonPi wiki but basically after you have downloaded the qtonpi tarball extract the three files within.&lt;br /&gt;
Then as root extract [opt-qt5-current.tar.bz2] and [toolchain-and-sysroot-armv5tel.tar.bz2] &lt;br /&gt;
 $ cd /&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/opt-qt5-current.tar.bz2&lt;br /&gt;
 $ sudo tar -jxvf /path to extracted image files/toolchain-and-sysroot-armv5tel.tar.bz2&lt;br /&gt;
&lt;br /&gt;
===Qt creator===&lt;br /&gt;
The tarball comes with a recent version of qtcreator, but since then qt2.5 RC has come out, Should be safe enough to use that instead. Just install that by executing the .bin installer.&lt;br /&gt;
&lt;br /&gt;
Within Qt creator you need to point it at your cross tool chain compiler+debugger:&lt;br /&gt;
#Tools-&amp;gt;Options-&amp;gt;Build&amp;amp;Run then Tool Chains&lt;br /&gt;
#then select add, in the drop-down pick GCC&lt;br /&gt;
#Select GCC and browse for compiler to&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gcc&lt;br /&gt;
and for the debugger&lt;br /&gt;
 /opt/qtonpi/bin/armv5tel-qtonpi-linux-gnueabi-gdb&lt;br /&gt;
Save these selections by clicking Apply and OK&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi Setup==&lt;br /&gt;
As I don&#039;t have a rpi yet I used qemu to do some initial testing.&lt;br /&gt;
My setup was a 12.04 VM.&lt;br /&gt;
You can either install qemu&lt;br /&gt;
 sudo apt-get install qemu-system&lt;br /&gt;
Or you can build qemu from git. You only need to do this if the qemu on your distro doesn&#039;t support the Broadcom SOC (ARM1176 core) on the Pi.&lt;br /&gt;
In order to boot your image you will need a suitable kernel for your emulator, there is one available here http://dl.dropbox.com/u/45842273/zImage_3.1.9 &lt;br /&gt;
Boot your virtual Pi &lt;br /&gt;
 qemu-system-arm -kernel kernel-qemu -cpu arm1176 -m 256 -M versatilepb -no-reboot -serial stdio -append &amp;quot;root=/dev/sda2 rw panic=1&amp;quot; qtonpi-sdcard-0.2.img -redir tcp:5022::22&lt;br /&gt;
&lt;br /&gt;
add&lt;br /&gt;
 console=ttyAMA0&lt;br /&gt;
to the -append param to have the boot console re-directed to the terminal.&lt;br /&gt;
&lt;br /&gt;
the -redir tcp:5022::22 redirects port 22 (ssh) on the virtual Pi to port 5022 on the host enabling you to ssh in.&lt;br /&gt;
 ssh pi@localhost -p5022&lt;br /&gt;
&lt;br /&gt;
==qOrbiter on Pi==&lt;br /&gt;
===Status===&lt;br /&gt;
Unfortunately I have not been able to get my compiled qOrbiter to run on my virtual setup.&lt;br /&gt;
Depending on the combination of kernel I use and/or SD image I either get an illegal instruction or and error creating a vchiq instance.&lt;br /&gt;
&lt;br /&gt;
And given that the vchiq lib stuff is to do with the GPU, which is initialised in firmware, this may be a bit of an impass until I get actual hardware.&lt;br /&gt;
&lt;br /&gt;
===Code Changes===&lt;br /&gt;
According to the current Qt Documentation adding&lt;br /&gt;
 greaterThan(QT_MAJOR_VERSION, 4) {&lt;br /&gt;
        QT += widgets&lt;br /&gt;
        QT += quick1&lt;br /&gt;
    } else {&lt;br /&gt;
        QT += declarative&lt;br /&gt;
    }&lt;br /&gt;
to the pro file loads the correct modules for both Qt4/Qt5.&lt;br /&gt;
At the moment my code and svn differ and not in a nice way - once I get everything #ifdef&#039;d into place I&#039;ll either stick a patch here or check it in with golgoj4 approval :)&lt;br /&gt;
&lt;br /&gt;
==Raspberry Pi distros==&lt;br /&gt;
Looking at http://elinux.org/RPi_Distributions there are quite a few to choose from.&lt;br /&gt;
&lt;br /&gt;
Which is the best fit? I don&#039;t know.&lt;br /&gt;
&lt;br /&gt;
I&#039;m starting with QtonPi but I don&#039;t know if a full fedora release is necessary.&lt;br /&gt;
&#039;&#039;This is actually a trimmed down fedora release no X, graphics written direct to fb&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Mer/Meego might be a good fit too.&lt;/div&gt;</summary>
		<author><name>Coley</name></author>
	</entry>
</feed>