LinuxMCE - User contributions [en]

Talk:Core

2012-01-29T21:38:40Z

JoakimL: Created page with ""as only the Core software needs to be upgraded." That's not correct, since all MDs need their own update. // JoakimL"

"as only the Core software needs to be upgraded." That's not correct, since all MDs need their own update. // JoakimL

Motion

2012-01-29T19:14:13Z

JoakimL: Clean-up

{{Versioninfo}}
[[Category: Security]]
[[Category: Cameras]]
[[Category: Tutorials]]
[[Category: Software components]]

{| align="right"
| __TOC__
|}

'''Motion''' is a program that monitors the video signal from one or more cameras and is able to detect if a significant part of the picture has changed; in other words, it can detect motion. Motion is the perfect tool for keeping an eye on your property, keeping only those images that are interesting.

LinuxMCE has a wrapper that connects to Motion, called "Motion Wrapper". This wrapper is added as a "device" on the "Interfaces" page. You must have this interface installed before setting up cameras.

The program is written in C for the Linux operating system. Motion is a command line based tool whose output can be jpeg or ppm files, or mpeg video sequences.

For detailed info see the [http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome Motion website].

==Features==
*Takes snapshots of movement
*Watches multiple video devices at the same time
*Watches multiple inputs on one capture card at the same time
*Live streaming webcam (using multipart/x-mixed-replace)
*Real time creation of mpeg movies using libraries from ffmpeg
*Take automated snapshots on regular intervals
*Take automated snapshots at irregular intervals using cron
*Execute external commands when detecting movement (and e.g. send SMS or email)
*Motion tracking (camera follow motion - special hardware required)
*Feed events to a MySQL or PostgreSQL database.
*Feed video back to a video4linux loopback for real time viewing
*Lots of user contributed related projects with web interfaces etc.
*User configurable and user defined on screen display.
*Controlled via the browser (older versions used xml-rpc)
*Automatic noise and threshold control
*Motion is a daemon with low CPU consumption and a small memory footprint.

===Changing the Motion Wrapper settings===

*[[LinuxMCE Admin Website]]--> Advanced --> [[Advanced Pages Devices| Devices]]
*My Devices-->CORE-->Motion Wrapper
*Under Device Data-->Motion Parameters can be found the actual parameters. The correspond to the [http://www.lavrsen.dk/twiki/bin/view/Motion/ConfigFileOptions Motion config options] found on the Motion wiki.
:*My surveillance camera already has automatic light leveling and I don't need the Motion module to do it for me, so I set auto-brightness off.
:*I wanted my camera to detect movement when just two frames showed a difference, so I set minimum_motion_frames to 2.
:*also need to set snapshot_interval to 2 ('''snapshot_interval 2''')
*After making all my changes, I saved and did a [[quick reload router]].

==Interesting related projects==

Since there will probably be some discussion about the future of video surveillance under LinuxMCE, I'll enumerate here few interesting projects, which I hope will one day be incorporated into LinuxMCE.

*[http://www.lavrsen.dk/twiki/bin/view/Motion/KmotionWebViewer Kmotion Web Viewer]
*[http://www.zoneminder.com/ Zoneminder]

Squid as ad blocker

2011-12-23T15:44:48Z

JoakimL:

This ad blocking is using [http://pgl.yoyo.org/adservers/ http://pgl.yoyo.org/adservers/] blocking lists.

Install Squid as laid out in [[How to setup secure outbound web access]]

Find the following line: # INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS using:
nano /etc/squid/squid.conf
Add these two lines below:
acl ads dstdom_regex -i "/etc/squid/squid.adservers.regex"
http_access deny ads

Create a script file, e.g.
nano /etc/cron.daily/getadblock.sh

#!/bin/sh

### short script that downloads a list of ad servers for use with squid to block ads.
###
### details on configuring squid itself can be found here:
###
### http://pgl.yoyo.org/adservers/#withsquid
###
### - originally by Stephen Patterson <steve@lexx.uklinux.net>
### - butchered by Peter Lowe <pgl@yoyo.org>
### - LMCE 10.04 adjustments by Joakim Lindbom

## set things

# URL of the ad server list to download
listurl='http://pgl.yoyo.org/adservers/serverlist.php?hostformat=squid-dstdom-regex;showintro=0&mimetype=plaintext'

# location of the list of ad servers used by Squid
targetfile='/etc/squid/squid.adservers.regex'

# location of a file where hostnames not listed can be added
extrasfile='/etc/squid/squid-extra.adservers'

# command to reload squid - change according to your system
reloadcmd='restart squid'

# temp file to use
tmpfile="/tmp/.adlist.$$"

# command to fetch the list (alternatives commented out)
fetchcmd="wget -q $listurl -O $tmpfile"

# log file
logfile='/var/log/pluto/ad-blocker'

## do things
##
echo "$(date -R) Getting new refuse list" >> "$logfile"

# get a fresh list of ad server addresses for squid to refuse
$fetchcmd

# add the extras
[ -f "$extrasfile" ] && cat $extrasfile >> $tmpfile

# check the temp file exists OK before overwriting the existing list
if [ ! -s $tmpfile ]
then
echo "$(date -R) temp file '$tmpfile' either doesn't exist or is empty; quitting" >> "$logfile"
exit
fi

cp $tmpfile $targetfile

# clean up
rm $tmpfile

# restart Squid
$reloadcmd

Make it executable:
chmod 755 /etc/cron.daily/getadblock.sh

To add auto configure (i.e. no config needed in your browser to make this work):
Add a PAC auto config file to the Apache directory:

nano /var/www/wpad.pac
function FindProxyForURL(url, host)
{
return "PROXY 192.168.80.1:3128 ; DIRECT";
}

Add PAC function to the DHCP daemon:

sudo nano /etc/dhcp3/dhcpd.conf
add these lines after "option subnet-mask 255.255.255.0;"

option wpad code 252 = text;
option wpad "http://192.168.80.1/wpad.pac";

class "MSFT" {
match if substring(option vendor-class-identifier, 0, 4) = "MSFT";
option dhcp-parameter-request-list =
concat(option dhcp-parameter-request-list, fc);
}

Restart the DHCP daemon

sudo restart dhcp-server

Squid as ad blocker

2011-12-23T15:41:04Z

JoakimL:

This ad blocking is using [http://pgl.yoyo.org/adservers/] blocking lists.

Install Squid as laid out in [[How to setup secure outbound web access]]

Find the following line: # INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS using:
nano /etc/squid/squid.conf
Add these two lines below:
acl ads dstdom_regex -i "/etc/squid/squid.adservers.regex"
http_access deny ads

Create a script file, e.g.
nano /etc/cron.daily/getadblock.sh

#!/bin/sh

### short script that downloads a list of ad servers for use with squid to block ads.
###
### details on configuring squid itself can be found here:
###
### http://pgl.yoyo.org/adservers/#withsquid
###
### - originally by Stephen Patterson <steve@lexx.uklinux.net>
### - butchered by Peter Lowe <pgl@yoyo.org>
### - LMCE 10.04 adjustments by Joakim Lindbom

## set things

# URL of the ad server list to download
listurl='http://pgl.yoyo.org/adservers/serverlist.php?hostformat=squid-dstdom-regex;showintro=0&mimetype=plaintext'

# location of the list of ad servers used by Squid
targetfile='/etc/squid/squid.adservers.regex'

# location of a file where hostnames not listed can be added
extrasfile='/etc/squid/squid-extra.adservers'

# command to reload squid - change according to your system
reloadcmd='restart squid'

# temp file to use
tmpfile="/tmp/.adlist.$$"

# command to fetch the list (alternatives commented out)
fetchcmd="wget -q $listurl -O $tmpfile"

# log file
logfile='/var/log/pluto/ad-blocker'

## do things
##
echo "$(date -R) Getting new refuse list" >> "$logfile"

# get a fresh list of ad server addresses for squid to refuse
$fetchcmd

# add the extras
[ -f "$extrasfile" ] && cat $extrasfile >> $tmpfile

# check the temp file exists OK before overwriting the existing list
if [ ! -s $tmpfile ]
then
echo "$(date -R) temp file '$tmpfile' either doesn't exist or is empty; quitting" >> "$logfile"
exit
fi

cp $tmpfile $targetfile

# clean up
rm $tmpfile

# restart Squid
$reloadcmd

Make it executable:
chmod 755 /etc/cron.daily/getadblock.sh

To add auto configure (i.e. no config needed in your browser to make this work):
Add a PAC auto config file to the Apache directory:

nano /var/www/wpad.pac
function FindProxyForURL(url, host)
{
return "PROXY 192.168.80.1:3128 ; DIRECT";
}

Add PAC function to the DHCP daemon:

sudo nano /etc/dhcp3/dhcpd.conf
add these lines after "option subnet-mask 255.255.255.0;"

option wpad code 252 = text;
option wpad "http://192.168.80.1/wpad.pac";

class "MSFT" {
match if substring(option vendor-class-identifier, 0, 4) = "MSFT";
option dhcp-parameter-request-list =
concat(option dhcp-parameter-request-list, fc);
}

Restart the DHCP daemon

sudo restart dhcp-server

Squid as ad blocker

2011-12-23T15:35:04Z

JoakimL:

This ad blocking is using [http://pgl.yoyo.org/adservers/] blocking lists.

Install Squid as laid out in [[How to setup secure outbound web access]]

Find the following line: # INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
Add these two lines below:
acl ads dstdom_regex -i "/etc/squid/squid.adservers.regex"
http_access deny ads

Create a script file, e.g.
nano /etc/cron.daily/getadblock.sh

#!/bin/sh

### short script that downloads a list of ad servers for use with squid to block ads.
###
### details on configuring squid itself can be found here:
###
### http://pgl.yoyo.org/adservers/#withsquid
###
### - originally by Stephen Patterson <steve@lexx.uklinux.net>
### - butchered by Peter Lowe <pgl@yoyo.org>
### - LMCE 10.04 adjustments by Joakim Lindbom

## set things

# URL of the ad server list to download
listurl='http://pgl.yoyo.org/adservers/serverlist.php?hostformat=squid-dstdom-regex;showintro=0&mimetype=plaintext'

# location of the list of ad servers used by Squid
targetfile='/etc/squid/squid.adservers.regex'

# location of a file where hostnames not listed can be added
extrasfile='/etc/squid/squid-extra.adservers'

# command to reload squid - change according to your system
reloadcmd='restart squid'

# temp file to use
tmpfile="/tmp/.adlist.$$"

# command to fetch the list (alternatives commented out)
fetchcmd="wget -q $listurl -O $tmpfile"

# log file
logfile='/var/log/pluto/ad-blocker'

## do things
##
echo "$(date -R) Getting new refuse list" >> "$logfile"

# get a fresh list of ad server addresses for squid to refuse
$fetchcmd

# add the extras
[ -f "$extrasfile" ] && cat $extrasfile >> $tmpfile

# check the temp file exists OK before overwriting the existing list
if [ ! -s $tmpfile ]
then
echo "$(date -R) temp file '$tmpfile' either doesn't exist or is empty; quitting" >> "$logfile"
exit
fi

cp $tmpfile $targetfile

# clean up
rm $tmpfile

# restart Squid
$reloadcmd

Make it executable:
chmod 755 /etc/cron.daily/getadblock.sh

To add auto configure (i.e. no config needed in your browser to make this work):
Add a PAC auto config file to the Apache directory:

nano /var/www/wpad.pac
function FindProxyForURL(url, host)
{
return "PROXY 192.168.80.1:3128 ; DIRECT";
}

Add PAC function to the DHCP daemon:

sudo nano /etc/dhcp3/dhcpd.conf
add these lines after "option subnet-mask 255.255.255.0;"

option wpad code 252 = text;
option wpad "http://192.168.80.1/wpad.pac";

class "MSFT" {
match if substring(option vendor-class-identifier, 0, 4) = "MSFT";
option dhcp-parameter-request-list =
concat(option dhcp-parameter-request-list, fc);
}

Restart the DHCP daemon

sudo restart dhcp-server

Squid as ad blocker

2011-12-23T15:29:22Z

JoakimL:

This ad blocking is using [http://pgl.yoyo.org/adservers/] blocking lists.

Install Squid as laid out in [[How to setup secure outbound web access]]

Find the following line: # INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
Add these two lines below:
acl ads dstdom_regex -i "/etc/squid/squid.adservers.regex"
http_access deny ads

Create a script file, e.g.
nano /etc/cron.daily/getadblock.sh

#!/bin/sh

### short script that downloads a list of ad servers for use with squid to block ads.
###
### details on configuring squid itself can be found here:
###
### http://pgl.yoyo.org/adservers/#withsquid
###
### - originally by Stephen Patterson <steve@lexx.uklinux.net>
### - butchered by Peter Lowe <pgl@yoyo.org>
### - LMCE 10.04 adjustments by Joakim Lindbom

## set things

# URL of the ad server list to download
listurl='http://pgl.yoyo.org/adservers/serverlist.php?hostformat=squid-dstdom-regex;showintro=0&mimetype=plaintext'

# location of the list of ad servers used by Squid
targetfile='/etc/squid/squid.adservers.regex'

# location of a file where hostnames not listed can be added
extrasfile='/etc/squid/squid-extra.adservers'

# command to reload squid - change according to your system
reloadcmd='restart squid'

# temp file to use
tmpfile="/tmp/.adlist.$$"

# command to fetch the list (alternatives commented out)
fetchcmd="wget -q $listurl -O $tmpfile"

# log file
logfile='/var/log/pluto/ad-blocker'

## do things
##
echo "$(date -R) Getting new refuse list" >> "$logfile"

# get a fresh list of ad server addresses for squid to refuse
$fetchcmd

# add the extras
[ -f "$extrasfile" ] && cat $extrasfile >> $tmpfile

# check the temp file exists OK before overwriting the existing list
if [ ! -s $tmpfile ]
then
echo "$(date -R) temp file '$tmpfile' either doesn't exist or is empty; quitting" >> "$logfile"
exit
fi

cp $tmpfile $targetfile

# clean up
rm $tmpfile

# restart Squid
$reloadcmd

Make it executable:
chmod 755 /etc/cron.daily/getadblock.sh

To add auto configure (i.e. no config needed in your browser to make this work):
Add a PAC auto config file to the Apache directory:

nano /var/www/wpad.pac
function FindProxyForURL(url, host)
{
return "PROXY 192.168.80.1:3128 ; DIRECT";
}

Add PAC function to the DHCP daemon:
sudo nano /etc/dhcp3/dhcpd.conf
add these lines after "option subnet-mask 255.255.255.0;"

option wpad code 252 = text;
option wpad "http://192.168.80.1/wpad.pac";

class "MSFT" {
match if substring(option vendor-class-identifier, 0, 4) = "MSFT";
option dhcp-parameter-request-list =
concat(option dhcp-parameter-request-list, fc);
}

Restart the DHCP daemon

sudo restart dhcp-server

Squid as ad blocker

2011-12-23T15:28:33Z

JoakimL: Added auto config

This ad blocking is using [http://pgl.yoyo.org/adservers/] blocking lists.

Install Squid as laid out in [[How to setup secure outbound web access]]

Find the following line: # INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
Add these two lines below:
acl ads dstdom_regex -i "/etc/squid/squid.adservers.regex"
http_access deny ads

Create a script file, e.g.
nano /etc/cron.daily/getadblock.sh

#!/bin/sh

### short script that downloads a list of ad servers for use with squid to block ads.
###
### details on configuring squid itself can be found here:
###
### http://pgl.yoyo.org/adservers/#withsquid
###
### - originally by Stephen Patterson <steve@lexx.uklinux.net>
### - butchered by Peter Lowe <pgl@yoyo.org>
### - LMCE 10.04 adjustments by Joakim Lindbom

## set things

# URL of the ad server list to download
listurl='http://pgl.yoyo.org/adservers/serverlist.php?hostformat=squid-dstdom-regex;showintro=0&mimetype=plaintext'

# location of the list of ad servers used by Squid
targetfile='/etc/squid/squid.adservers.regex'

# location of a file where hostnames not listed can be added
extrasfile='/etc/squid/squid-extra.adservers'

# command to reload squid - change according to your system
reloadcmd='restart squid'

# temp file to use
tmpfile="/tmp/.adlist.$$"

# command to fetch the list (alternatives commented out)
fetchcmd="wget -q $listurl -O $tmpfile"

# log file
logfile='/var/log/pluto/ad-blocker'

## do things
##
echo "$(date -R) Getting new refuse list" >> "$logfile"

# get a fresh list of ad server addresses for squid to refuse
$fetchcmd

# add the extras
[ -f "$extrasfile" ] && cat $extrasfile >> $tmpfile

# check the temp file exists OK before overwriting the existing list
if [ ! -s $tmpfile ]
then
echo "$(date -R) temp file '$tmpfile' either doesn't exist or is empty; quitting" >> "$logfile"
exit
fi

cp $tmpfile $targetfile

# clean up
rm $tmpfile

# restart Squid
$reloadcmd

Make it executable:
chmod 755 /etc/cron.daily/getadblock.sh

To add auto configure (i.e. no config needed in your browser to make this work):
Add a PAC auto config file to the Apache directory:
nano /var/www/wpad.pac
function FindProxyForURL(url, host)
{
return "PROXY 192.168.80.1:3128 ; DIRECT";
}

Add PAC function to the DHCP daemon:
sudo nano /etc/dhcp3/dhcpd.conf
add these lines after "option subnet-mask 255.255.255.0;"

option wpad code 252 = text;
option wpad "http://192.168.80.1/wpad.pac";

class "MSFT" {
match if substring(option vendor-class-identifier, 0, 4) = "MSFT";
option dhcp-parameter-request-list =
concat(option dhcp-parameter-request-list, fc);
}

Restart the DHCP daemon

sudo restart dhcp-server

Squid as ad blocker

2011-12-22T20:53:35Z

JoakimL:

This ad blocking is using [http://pgl.yoyo.org/adservers/] blocking lists.

Install Squid as laid out in [[How to setup secure outbound web access]]

Find the following line: # INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
Add these two lines below:
acl ads dstdom_regex -i "/etc/squid/squid.adservers.regex"
http_access deny ads

Create a script file, e.g.
nano /etc/cron.daily/getadblock.sh

#!/bin/sh

### short script that downloads a list of ad servers for use with squid to block ads.
###
### details on configuring squid itself can be found here:
###
### http://pgl.yoyo.org/adservers/#withsquid
###
### - originally by Stephen Patterson <steve@lexx.uklinux.net>
### - butchered by Peter Lowe <pgl@yoyo.org>
### - LMCE 10.04 adjustments by Joakim Lindbom

## set things

# URL of the ad server list to download
listurl='http://pgl.yoyo.org/adservers/serverlist.php?hostformat=squid-dstdom-regex;showintro=0&mimetype=plaintext'

# location of the list of ad servers used by Squid
targetfile='/etc/squid/squid.adservers.regex'

# location of a file where hostnames not listed can be added
extrasfile='/etc/squid/squid-extra.adservers'

# command to reload squid - change according to your system
reloadcmd='restart squid'

# temp file to use
tmpfile="/tmp/.adlist.$$"

# command to fetch the list (alternatives commented out)
fetchcmd="wget -q $listurl -O $tmpfile"

# log file
logfile='/var/log/pluto/ad-blocker'

## do things
##
echo "$(date -R) Getting new refuse list" >> "$logfile"

# get a fresh list of ad server addresses for squid to refuse
$fetchcmd

# add the extras
[ -f "$extrasfile" ] && cat $extrasfile >> $tmpfile

# check the temp file exists OK before overwriting the existing list
if [ ! -s $tmpfile ]
then
echo "$(date -R) temp file '$tmpfile' either doesn't exist or is empty; quitting" >> "$logfile"
exit
fi

cp $tmpfile $targetfile

# clean up
rm $tmpfile

# restart Squid
$reloadcmd

Make it executable:
chmod 755 /etc/cron.daily/getadblock.sh

Configure your browser to use a proxy on 192.168.80.1, port 3128 and try to access some sites. Use tail on /var/log/squid/access.log to ensure squid was used. If all is ok, proceed to the next line.

Squid as ad blocker

2011-12-22T20:50:05Z

JoakimL:

This ad blocking is using [http://pgl.yoyo.org/adservers/] blocking lists.

Install Squid as laid out in [[How to setup secure outbound web access]]

Find the following line: # INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
Add these two lines below:
acl ads dstdom_regex -i "/etc/squid/squid.adservers.regex"
http_access deny ads

Create a script file, e.g.
nano /etc/cron.daily/getadblock.sh

#!/bin/sh

### short script that downloads a list of ad servers for use with squid to block ads.
###
### details on configuring squid itself can be found here:
###
### http://pgl.yoyo.org/adservers/#withsquid
###
### - originally by Stephen Patterson <steve@lexx.uklinux.net>
### - butchered by Peter Lowe <pgl@yoyo.org>
### - LMCE 10.04 adjustments by Joakim Lindbom

## set things

# URL of the ad server list to download
listurl='http://pgl.yoyo.org/adservers/serverlist.php?hostformat=squid-dstdom-regex;showintro=0&mimetype=plaintext'

# location of the list of ad servers used by Squid
targetfile='/etc/squid/squid.adservers.regex'

# location of a file where hostnames not listed can be added
extrasfile='/etc/squid/squid-extra.adservers'

# command to reload squid - change according to your system
reloadcmd='restart squid'

# temp file to use
tmpfile="/tmp/.adlist.$$"

# command to fetch the list (alternatives commented out)
fetchcmd="wget -q $listurl -O $tmpfile"

# log file
logfile='/var/log/pluto/ad-blocker'

## do things
##
echo "$(date -R) Getting new refuse list" >> "$logfile"

# get a fresh list of ad server addresses for squid to refuse
$fetchcmd

# add the extras
[ -f "$extrasfile" ] && cat $extrasfile >> $tmpfile

# check the temp file exists OK before overwriting the existing list
if [ ! -s $tmpfile ]
then
echo "$(date -R) temp file '$tmpfile' either doesn't exist or is empty; quitting" >> "$logfile"
exit
fi

cp $tmpfile $targetfile

# clean up
rm $tmpfile

# restart Squid
$reloadcmd

Make it executable:
chmod 755 /etc/cron.daily/getadblock.sh

Squid as ad blocker

2011-12-22T20:48:27Z

JoakimL: Created page with "This ad blocking is using [http://pgl.yoyo.org/adservers/] blocking lists. Install Squid as laid out in How to setup secure outbound web access Find the following line: # I..."

This ad blocking is using [http://pgl.yoyo.org/adservers/] blocking lists.

Install Squid as laid out in [[How to setup secure outbound web access]]

Find the following line: # INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
Add these two lines below:
acl ads dstdom_regex -i "/etc/squid/squid.adservers.regex"
http_access deny ads

Create a script file, e.g.
nano /etc/cron.daily/getadblock.sh

#!/bin/sh

### short script that downloads a list of ad servers for use with squid to block ads.
###
### details on configuring squid itself can be found here:
###
### http://pgl.yoyo.org/adservers/#withsquid
###
### - originally by Stephen Patterson <steve@lexx.uklinux.net>
### - butchered by Peter Lowe <pgl@yoyo.org>
### - LMCE 10.04 adjustments by Joakim Lindbom

## set things

# URL of the ad server list to download
listurl='http://pgl.yoyo.org/adservers/serverlist.php?hostformat=squid-dstdom-regex;showintro=0&mimetype=plaintext'

# location of the list of ad servers used by Squid
targetfile='/etc/squid/squid.adservers.regex'

# location of a file where hostnames not listed can be added
extrasfile='/etc/squid/squid-extra.adservers'

# command to reload squid - change according to your system
reloadcmd='restart squid'

# temp file to use
tmpfile="/tmp/.adlist.$$"

# command to fetch the list (alternatives commented out)
fetchcmd="wget -q $listurl -O $tmpfile"

# log file
logfile='/var/log/pluto/ad-blocker'

## do things
##
echo "$(date -R) Getting new refuse list" >> "$logfile"

# get a fresh list of ad server addresses for squid to refuse
$fetchcmd

# add the extras
[ -f "$extrasfile" ] && cat $extrasfile >> $tmpfile

# check the temp file exists OK before overwriting the existing list
if [ ! -s $tmpfile ]
then
echo "$(date -R) temp file '$tmpfile' either doesn't exist or is empty; quitting" >> "$logfile"
exit
fi

cp $tmpfile $targetfile

# clean up
rm $tmpfile

# restart Squid
$reloadcmd

Make it executable:
chmod 755 /etc/cron.daily/getadblock.sh

How to setup secure outbound web access

2011-12-22T20:13:46Z

JoakimL:

[[Category: Tutorials]]
{| align="right"
| __TOC__
|}
=Background=
This tutorial has come about as a result of a discussion on the [http://forum.linuxmce.org/index.php?topic=8692.0 forums]. It details setting up a chain of security devices on the core which should help optimize web browsing from the internal network.

''Please note, much of this is shamelessly plagarised from others. What I have done is to try to bring their work together and provide a comprehensive end-to-end solution. If you are one of those whose work has been used, please take it as a compliment and feel free to add appropriate credits at the end!''

==How Browsing Works==
Without wishing to state the obvious, a basic understanding of web browsing helps us to understand the setup described here. Browsing is a fairly simple process. The client (known as a browser) sends a request using a protocol called HTTP to a server. By default, this request is sent to port 80. The server responds with the requested file. This file may well contain HTML, which the browser will display and will result in the browser making further requests for graphics files, etc.

It is also possible to put a third entity in the middle of this chain. This entity is known as a proxy.

In this case, the requests from the browser are sent to the proxy. The proxy sends the requests to the server, which responds to the proxy. Finally, the proxy responds to the browser. Proxys are used for many reasons, often security-related.

The system we will be setting up will consist of a chain of 3 proxies which will perform the following functions:
* Caching. This allows the proxy to store a copy of the files requested. If a second request is received for the same file, it is already held locally and a second request does not need to be sent to the server. This reduces traffic on the external network and also improves performance overall. The Caching proxy we will be using is known as Squid.

* Virus Scanning. As the file will be passing through the proxy, that proxy can examine its contents. In this case, viruses can be scanned for and blocked. The virus scanning proxy we will be using is called HavP and is used in conjunction with a regular scanner, in our case ClamAV.

*Content Scanning. As well as being examined for viruses, the text of the HTML can be processed and scored. This allows inappropriate (for example sexual) content to be blocked. We will be setting up using one of the best known content scanners, Dan's Guardian.

==Transparent Proxying==
There was much discussion on the forum thread concerning this. It is an additional feature which is entirely optional. In order for a proxy to be used, the browser has to "know" to send its requests to the proxy rather than to the actual server. This is achieved by configuring the browser with the proxy's details. There are, however, one or two problems with this.
#Each browser must be individually configured. Not too much of a problem with a home network and not many browsers, but particularly with portable devices which may or may not be used elsewhere (for example at work) it can be inconvenient to have to keep turning the proxy on and off.
#It can be easy to bypass. Without additional firewall rulesc to prevent direct browsing of the internet, bypassing the proxy (and therefore gaining access to blocked content) is as simple as turning it off in the browser.
The solution to this is known as transparent proxying. This works by having the proxy running on the router (in our case the core) and configuring it to intercept all outbound web traffic (i.e. destined for port 80) and redirect it to the proxy. The process is transparent to the end browser / user, hence the name.

'''NOTE''' Transparent proxying should not be seen as an alternative to setting a proxy on static machines, only as an addition. There are still ways to circumvent the system (for example, some webservers don't operate on port 80) so transparent proxying should be seen as an additional layer of security, not an alternative!

=The Software=
We will be installing a series of packages. The full details of configuring each will not be discussed here. For an in depth discussion, please visit the respective websites.
==Squid==
Squid is a very powerful caching web proxy server. This means that it keeps a copy of all files it is asked to retrieve (unless the various http headers dictate that the file cannot be cached). When a file is requested, Squid first checks to see if it has a cached copy. If so, that is returned, if not, it is fetched from the webserver. It is common for certain websites to be visited frequently and Squid will rapidly build up cached copies of things like logo graphics etc. which can (in some cases) drasticly reduce the requests to the internet with resulting speed advantages. If you also pay for data useage, Squid can save money as well! Full details can be found on the [http://www.squid-cache.org/ Squid website]. In our configuration, Squid will be the proxy that actually makes the requests to the internet and is, therefore, the "end" of the chain. You can optionally configure Squid to block ads as well.
==ClamAV==
ClamAV is a linux-based virus scanning solution. It is not ''directly'' part of the proxy chain, but will be used by HavP. It will be configured to download updates on a regular basis and anecdotal evidence is that it is often "first to press" with new virus definitions. Further information at the [http://www.clamav.net/ ClamAV website].
==HavP==
HavP (Http Anti Virus Proxy) is used to scan each file being downloaded using a standard AV scanner. In our case, we are going to use ClamAV (above) to scan. HavP will be configured to use Squid as is proxy. It is important that this order is used as a new virus may otherwise end up in the cache (before ClamAV is updated) and then continue to be served up even after the virus database is updated. Once again, full details on the [http://www.server-side.de/ HavP website.]
==Dan's Guardian==
The final stage in the Proxy chain is Dan's Guardian. This is the proxy that the clients will connect to and it will, in turn, pass the requests on to HavP. Dan's Guardian is a well known content scanner that can control access to websites based not only on the URL, but also on the actual content of the files. It, like Squid, is hugely flexible and a full discussion is beyond the scope of this document, but if you need more, point your browser at the [http://dansguardian.org/ Dan's Guardian Website].
==Shorewall==
=Installation=
'''I am writing this as I perform the steps on my own core. So, while this line is here, it's a work in progress and as yet unfinished!!!!'''

We are going to work "backwards" testing each link in the chain as we go. I am going to assume you have a browser-enabled device on the "inside" network that you can easily re-configure with proxies (a PSP is NOT ideal for this!!) I also accessed my core from an ssh session on my client.
==Squid==
Firstly, we install Squld. There is already a wiki page on [[Squid|installing Squid]] which works pretty well. The only differences I experienced concerned the squid configuration file. This is located in /etc/squid/squid.conf. Locate the lines that say(Lines 607, 608 & 609 in mine):
acl localnet src 10.0.0.0/8 # RFC1918 possible internal network
acl localnet src 172.16.0.0/12 # RFC1918 possible internal network
acl localnet src 192.168.0.0/16 # RFC1918 possible internal network
comment them out(put a # at the beginning) and insert a single line which says:
acl localnet src 192.168.80.0/24
Then uncomment the line (remove the initial #) from the line(675)
#http_access allow localnet

To use Squid as an ad blocker, follow this configuration: [[Squid as ad blocker ]]

Configure your browser to use a proxy on 192.168.80.1, port 3128 and try to access some sites. Use tail on /var/log/squid/access.log to ensure squid was used. If all is ok, proceed to the next line. (Note, you may want to reverse the changes to squid.conf to prevent this proxy being used directly.)

==ClamAv==
Next, we need a virus scanner. If you want to install without AV scanning, skip this step.

ClamAV is part of the repositories, so install using:
apt-get install clamav-daemon
We ant the virus definition databases to download automatically. This is performed by freshclam. Quick test: run freshclam (as superuser) with no parameters and check the output. If everything is OK you may create the log file in /var/log (owned by clamav or another user freshclam will be running as):

touch /var/log/freshclam.log
chmod 600 /var/log/freshclam.log
chown clamav /var/log/freshclam.log

I have set mine up to use cron, so add the following to crontab:
12 * * * * /usr/local/bin/freshclam --quiet
(This will update at 12 minutes past the hour).

==HavP==
Next we install a proxy that will scan using ClamAV. This can be obtained from the main HavP website on [http://www.server-side.de/] and should be unpacked with tar. As this isn't available as a package, the installation is the usual:
./configure --disable-clamav (if you don't want /usr/local, use --prefix=/other/path)
make
make install
Note: I couldn't get it to detaect the ClamAV libraries, possibly die to using a packaged ClamAV. If you manage to fix this, please update here!
also, a havp user and group should be created:
groupadd havp
useradd -g havp havp
Finally, edit /usr/local/etc/havp.conf.
=Setting up Transparent Proxying=
--[[User:Wierdbeard65|Wierdbeard65]] 13:31, 8 September 2009 (CEST)

How to setup secure outbound web access

2011-12-22T20:13:04Z

JoakimL: Added ad blocking

[[Category: Tutorials]]
{| align="right"
| __TOC__
|}
=Background=
This tutorial has come about as a result of a discussion on the [http://forum.linuxmce.org/index.php?topic=8692.0 forums]. It details setting up a chain of security devices on the core which should help optimize web browsing from the internal network.

''Please note, much of this is shamelessly plagarised from others. What I have done is to try to bring their work together and provide a comprehensive end-to-end solution. If you are one of those whose work has been used, please take it as a compliment and feel free to add appropriate credits at the end!''

==How Browsing Works==
Without wishing to state the obvious, a basic understanding of web browsing helps us to understand the setup described here. Browsing is a fairly simple process. The client (known as a browser) sends a request using a protocol called HTTP to a server. By default, this request is sent to port 80. The server responds with the requested file. This file may well contain HTML, which the browser will display and will result in the browser making further requests for graphics files, etc.

It is also possible to put a third entity in the middle of this chain. This entity is known as a proxy.

In this case, the requests from the browser are sent to the proxy. The proxy sends the requests to the server, which responds to the proxy. Finally, the proxy responds to the browser. Proxys are used for many reasons, often security-related.

The system we will be setting up will consist of a chain of 3 proxies which will perform the following functions:
* Caching. This allows the proxy to store a copy of the files requested. If a second request is received for the same file, it is already held locally and a second request does not need to be sent to the server. This reduces traffic on the external network and also improves performance overall. The Caching proxy we will be using is known as Squid.

* Virus Scanning. As the file will be passing through the proxy, that proxy can examine its contents. In this case, viruses can be scanned for and blocked. The virus scanning proxy we will be using is called HavP and is used in conjunction with a regular scanner, in our case ClamAV.

*Content Scanning. As well as being examined for viruses, the text of the HTML can be processed and scored. This allows inappropriate (for example sexual) content to be blocked. We will be setting up using one of the best known content scanners, Dan's Guardian.

==Transparent Proxying==
There was much discussion on the forum thread concerning this. It is an additional feature which is entirely optional. In order for a proxy to be used, the browser has to "know" to send its requests to the proxy rather than to the actual server. This is achieved by configuring the browser with the proxy's details. There are, however, one or two problems with this.
#Each browser must be individually configured. Not too much of a problem with a home network and not many browsers, but particularly with portable devices which may or may not be used elsewhere (for example at work) it can be inconvenient to have to keep turning the proxy on and off.
#It can be easy to bypass. Without additional firewall rulesc to prevent direct browsing of the internet, bypassing the proxy (and therefore gaining access to blocked content) is as simple as turning it off in the browser.
The solution to this is known as transparent proxying. This works by having the proxy running on the router (in our case the core) and configuring it to intercept all outbound web traffic (i.e. destined for port 80) and redirect it to the proxy. The process is transparent to the end browser / user, hence the name.

'''NOTE''' Transparent proxying should not be seen as an alternative to setting a proxy on static machines, only as an addition. There are still ways to circumvent the system (for example, some webservers don't operate on port 80) so transparent proxying should be seen as an additional layer of security, not an alternative!

=The Software=
We will be installing a series of packages. The full details of configuring each will not be discussed here. For an in depth discussion, please visit the respective websites.
==Squid==
Squid is a very powerful caching web proxy server. This means that it keeps a copy of all files it is asked to retrieve (unless the various http headers dictate that the file cannot be cached). When a file is requested, Squid first checks to see if it has a cached copy. If so, that is returned, if not, it is fetched from the webserver. It is common for certain websites to be visited frequently and Squid will rapidly build up cached copies of things like logo graphics etc. which can (in some cases) drasticly reduce the requests to the internet with resulting speed advantages. If you also pay for data useage, Squid can save money as well! Full details can be found on the [http://www.squid-cache.org/ Squid website]. In our configuration, Squid will be the proxy that actually makes the requests to the internet and is, therefore, the "end" of the chain. You can optionally configure Squid to block ads as well.
==ClamAV==
ClamAV is a linux-based virus scanning solution. It is not ''directly'' part of the proxy chain, but will be used by HavP. It will be configured to download updates on a regular basis and anecdotal evidence is that it is often "first to press" with new virus definitions. Further information at the [http://www.clamav.net/ ClamAV website].
==HavP==
HavP (Http Anti Virus Proxy) is used to scan each file being downloaded using a standard AV scanner. In our case, we are going to use ClamAV (above) to scan. HavP will be configured to use Squid as is proxy. It is important that this order is used as a new virus may otherwise end up in the cache (before ClamAV is updated) and then continue to be served up even after the virus database is updated. Once again, full details on the [http://www.server-side.de/ HavP website.]
==Dan's Guardian==
The final stage in the Proxy chain is Dan's Guardian. This is the proxy that the clients will connect to and it will, in turn, pass the requests on to HavP. Dan's Guardian is a well known content scanner that can control access to websites based not only on the URL, but also on the actual content of the files. It, like Squid, is hugely flexible and a full discussion is beyond the scope of this document, but if you need more, point your browser at the [http://dansguardian.org/ Dan's Guardian Website].
==Shorewall==
=Installation=
'''I am writing this as I perform the steps on my own core. So, while this line is here, it's a work in progress and as yet unfinished!!!!'''

We are going to work "backwards" testing each link in the chain as we go. I am going to assume you have a browser-enabled device on the "inside" network that you can easily re-configure with proxies (a PSP is NOT ideal for this!!) I also accessed my core from an ssh session on my client.
==Squid==
Firstly, we install Squld. There is already a wiki page on [[Squid|installing Squid]] which works pretty well. The only differences I experienced concerned the squid configuration file. This is located in /etc/squid/squid.conf. Locate the lines that say(Lines 607, 608 & 609 in mine):
acl localnet src 10.0.0.0/8 # RFC1918 possible internal network
acl localnet src 172.16.0.0/12 # RFC1918 possible internal network
acl localnet src 192.168.0.0/16 # RFC1918 possible internal network
comment them out(put a # at the beginning) and insert a single line which says:
acl localnet src 192.168.80.0/24
Then uncomment the line (remove the initial #) from the line(675)
#http_access allow localnet

To use Squid as a ad blocker, follow this configuration: [[Squid as ad blocker ]]

Configure your browser to use a proxy on 192.168.80.1, port 3128 and try to access some sites. Use tail on /var/log/squid/access.log to ensure squid was used. If all is ok, proceed to the next line. (Note, you may want to reverse the changes to squid.conf to prevent this proxy being used directly.)

==ClamAv==
Next, we need a virus scanner. If you want to install without AV scanning, skip this step.

ClamAV is part of the repositories, so install using:
apt-get install clamav-daemon
We ant the virus definition databases to download automatically. This is performed by freshclam. Quick test: run freshclam (as superuser) with no parameters and check the output. If everything is OK you may create the log file in /var/log (owned by clamav or another user freshclam will be running as):

touch /var/log/freshclam.log
chmod 600 /var/log/freshclam.log
chown clamav /var/log/freshclam.log

I have set mine up to use cron, so add the following to crontab:
12 * * * * /usr/local/bin/freshclam --quiet
(This will update at 12 minutes past the hour).

==HavP==
Next we install a proxy that will scan using ClamAV. This can be obtained from the main HavP website on [http://www.server-side.de/] and should be unpacked with tar. As this isn't available as a package, the installation is the usual:
./configure --disable-clamav (if you don't want /usr/local, use --prefix=/other/path)
make
make install
Note: I couldn't get it to detaect the ClamAV libraries, possibly die to using a packaged ClamAV. If you manage to fix this, please update here!
also, a havp user and group should be created:
groupadd havp
useradd -g havp havp
Finally, edit /usr/local/etc/havp.conf.
=Setting up Transparent Proxying=
--[[User:Wierdbeard65|Wierdbeard65]] 13:31, 8 September 2009 (CEST)

Category:DVB-T2

2011-12-19T14:15:34Z

JoakimL:

[[Category: Video]]
[[Category: TV Cards]]
[[Category: Video Capture Boards]]

To utilize DVB-T2 with LinuxMCE you need to add the kernel modules that your card requires to function (and also sometimes a firmware file too). To find out, what cards are supported look at the LinuxTVWiki.

Please add <nowiki>[[Category: DVB-T2]]</nowiki> to the top of a page you wish to have listed here.

Category:DVB-T2

2011-12-19T14:14:52Z

JoakimL: Created page with "Category: Video Category: TV Cards Category: Video Capture Boards To utilize DVB-T2 with LinuxMCE you need a DVB-T2 card supported by the 2.6.22 kernel or you need t..."

[[Category: Video]]
[[Category: TV Cards]]
[[Category: Video Capture Boards]]

To utilize DVB-T2 with LinuxMCE you need a DVB-T2 card supported by the 2.6.22 kernel or you need to add the kernel modules that your card requires to function (and also sometimes a firmware file too). To find out, what cards are supported look at the LinuxTVWiki.

Please add <nowiki>[[Category: DVB-T2]]</nowiki> to the top of a page you wish to have listed here.

Hauppauge PCTV nanoStick HD 290e

2011-12-19T14:13:52Z

JoakimL: Created page with "Category: Hardware Category: DVB-T Category: DVB-T2 {{versioninfo}} Category: USB Category: TV_Cards Category: Video This product is not automatically co..."

[[Category: Hardware]]
[[Category: DVB-T]]
[[Category: DVB-T2]]
{{versioninfo}}
[[Category: USB]]
[[Category: TV_Cards]]
[[Category: Video]]

This product is not automatically compatible at the moment. http://stevekerrison.com/290e/index.html contains info for adding support on pre 3.0 kernel - but I've not tested it yet.

User:JoakimL

2011-12-04T11:30:06Z

JoakimL:

{| align="right"
| __TOC__
|}
=Who am I=
I'm a long time IT guy from Sweden, started programming at age 9, first Unix exposure in -93 (NetBSD) and soon after also some Linux. I've done loads of system programming on IBM mainframe, S/38, AS/400, MS-DOS, Windows C++/DCOM, heavy duty Java J2EE on Linux, you name it. Most of it having to do with communications and middleware; actually I've developed something similar to DCE in the 80s and 90s... ;-) Today I'm an Enterprise Architect but try to get some dirt under the nails by digging in the dirt, I mean Linux.

-Joakim
aka '''JoakimL''' on the forums and in IRC

=Software=
Have run LMCE 8.10 successfully with this setup, now running LMCE 10.04. Impressions so far: Faster, better, more stable.

=Hardware=
==Media Directors==
===Moon39===
[[AsRock 330 ION HT]]
*Intel Atom 330 dual core
*2 GB main memory
*Hauppauge USB-DVB Nova-T Stick (DBV-T) (with HD support! I can receive DR DH from Denmark. Some lagging, but very good picture quality)
*Ping IT IR receiver
*MS MCE Remote (Branded AsRock)

Problems:
*Onboard IR receiver not supported by Linux Kernel in 8.10, I'll soon investigate for 10.04 (there is kernel and driver support available)
*WiFi card interfered with LMCE setup, fixed by disabling it in BIOS

==Core / Hybrid==
Home built AMD Athlon dual core 2.0 GHz
*Processor - Intel P4 2.0 GHz
*2 GB main memory
*1 x 400gb SATA disk
*1 * 2 TB SATA disk
*1 * 1.5 TB SATA disk in USB enclosure

==Orbiters==
===WinOrbiter===
*2 running from the outer network on WiFi connected Windows 7 laptops.
*1 running from the inner network on Ubuntu 9.10 and Wine

===Mobile===
*1 iPad with RoamingOrb
*2 iPhone2 with RoamingOrb
*1 iPod Touch with RoamingOrb

=Home control=
I've added support for [[Tellstick]] and use this to control some lights with cheap Nexa wall warts and two built in switches. I've got some dimmers in the drawer waiting to be integrated as well.

=Music=
One Squeezebox 3

=Setup=
Problems to solve:
*Keyboard with US layout, change to Swedish
*Remote not working due to IR receiver still not in place. Trying to use /dev/input/event in lirc, not OK yet

=Network=
Two networks, with wired and wireless in both.
*Outer network 100 Mbps 192.168.1.x - including VOIP gateway, to be replaced by Asterix when I get some time
*Inner network 1000 Mbps 192.168.80.x
Mostly loose cable, I have started to install Cat6 in a few walls.

=Old equipment, just for reference=
==Core / Hybrid==
Old Compaq P4
*Processor - Intel P4 2.0 GHz
*512 MB main memory
*1 x 200gb IDE disk

==Setup==
Some notes on setting up 8.10 B2 (daily build 22828)
===Core===
Nothing special, followed the standard procedure.

===Media Directors===
Firmware file for DBV-T missing, solved with:
<pre>cd /usr/pluto/diskless/39/lib/firmware/
sudo cp /lib/firmware/dvb-usb-dib0700-1.20.fw /usr/pluto/diskless/39/lib/firmware/ .

or:
cd /usr/pluto/diskless/39/lib/firmware/
sudo wget http://www.linuxtv.org/downloads/firmware/dvb-usb-dib0700-1.20.fw
</pre>

DVD not playable, even though the SW was installed at the Core
<pre>
sudo apt-get update
sudo apt-get install libdvdcss2 w32codecs
</pre>

[[category:Standard Definition Setups]]
[[Category:User Setups]]
[[Category:Swedish Setups]]
[[Category:Networking Setups]]
[[Category: ION]]

Tellstick

2011-11-26T22:36:58Z

JoakimL: Plug'n Play update

[[Category: Hardware]]
{{Versioninfo|810Status=Working, semi plug'n play supported|810UpdatedDate=7 january 2011|810UpdatedBy=[[User:JoakimL|JoakimL]]|1004Status=Working, full plug'n play supported|1004UpdatedDate=14 november 2011|1004UpdatedBy=[[User:JoakimL|JoakimL]]}}
{| align="right"
| __TOC__
|}
[[Category: Automation]]
[[Category: RF Control]]
[[Category: Tellstick]]

== Description ==
The Tellstick is a power controller for cheap RF devices like the Nexa line. It's detected with LMCE's Plug-n Play.
Currently only basic support is added, namely power on, power off and dimlevel.
N.B. this is an RF tranmsmitter, it cannot read the state of the devices, nor can it receive data from remotes, sensors or other equipment sending an RF signal. Telldus have developed a device for this (Tellstick Duo) which is not supported at this time.

== Setup ==
The device is plug and play for LMCE, software automatically downloaded and installed when you plug it into an USB port.

== Adding lights ==
# [http://192.168.80.1/ web admin] -> Show devices tree -> Telldus USB RF controller
# Create Child Device -> Pick device template -> ''take your pick'' (I added "Light Switch (on/off)")
# Device data -> Port/Channel Number -> ''Device ID'' -> '''save''' (codes correspond to the Device ID or Device Name you've set in /etc/tellstick.conf)

== Troubleshooting ==

== Reference Info ==
[http://www.telldus.se/products/tellstick Manufacturer website]

== Reference for 8.10 until P'nP is verified ==
At this point you'll need to add the driver software yourself. Install the telldus-core package as described [http://developer.telldus.se/wiki/TellStickInstallationUbuntu here]

Add the following lines to your /etc/apt/sources.list: (This is pointing to 2.0 repos, 2.1 currently break functionality)
deb http://download.telldus.com/debian/ 2.0 main

If you want to try the latest beta software, also add the following:
deb http://download.telldus.com/debian/ unstable main

The Telldus public key for apt-secure is added with
wget -q http://download.telldus.se/debian/telldus-public.key -O- | sudo apt-key add -
The key fingerprint is
70C4 10C9 D73D 53E8 38B3 1C58 5A94 9181 E501 EA76
Telldus Technologies AB <info.tech@telldus.se>

To install telldus-core
sudo apt-get update
sudo apt-get install telldus-core

If you install telldus-core version 2.1 you need to downgrade. If you get any trouble (like cannot connect to Telldus service or lib missing), install the correct libtelldus by:
wget http://download.telldus.com/debian/pool/2.0/libtelldus-core2_2.0.4-2_i386.deb
sudo dpkg -i libtelldus-core2_2.0.4-2_i386.deb

Tellstick

2011-11-17T20:31:50Z

JoakimL:

[[Category: Hardware]]
{{Versioninfo|810Status=Working, semi plug'n play supported|810UpdatedDate=7 january 2011|810UpdatedBy=[[User:JoakimL|JoakimL]]|1004Status=Working, semi plug'n play supported|1004UpdatedDate=14 november 2011|1004UpdatedBy=[[User:JoakimL|JoakimL]]}}
{| align="right"
| __TOC__
|}
[[Category: Automation]]
[[Category: RF Control]]
[[Category: Tellstick]]

== Description ==
The Tellstick is a power controller for cheap RF devices like the Nexa line. It's detected with LMCE's Plug-n Play.
Currently only basic support is added, namely power on, power off and dimlevel.
N.B. this is an RF tranmsmitter, it cannot read the state of the devices, nor can it receive data from remotes, sensors or other equipment sending an RF signal. Telldus have developed a device for this (Tellstick Duo) which is not supported at this time.

== Setup ==
The device is plug and play for LMCE, but at this point you'll need to add the driver software yourself. Install the telldus-core package as described [http://developer.telldus.se/wiki/TellStickInstallationUbuntu here]

Add the following lines to your /etc/apt/sources.list: (This is pointing to 2.0 repos, 2.1 currently break functionality)
deb http://download.telldus.com/debian/ 2.0 main

If you want to try the latest beta software, also add the following:
deb http://download.telldus.com/debian/ unstable main

The Telldus public key for apt-secure is added with
wget -q http://download.telldus.se/debian/telldus-public.key -O- | sudo apt-key add -
The key fingerprint is
70C4 10C9 D73D 53E8 38B3 1C58 5A94 9181 E501 EA76
Telldus Technologies AB <info.tech@telldus.se>

To install telldus-core
sudo apt-get update
sudo apt-get install telldus-core

If you install telldus-core version 2.1 you need to downgrade. If you get any trouble (like cannot connect to Telldus service or lib missing), install the correct libtelldus by:
wget http://download.telldus.com/debian/pool/2.0/libtelldus-core2_2.0.4-2_i386.deb
sudo dpkg -i libtelldus-core2_2.0.4-2_i386.deb

== Adding lights ==
# [http://192.168.80.1/ web admin] -> Show devices tree -> Telldus USB RF controller
# Create Child Device -> Pick device template -> ''take your pick'' (I added "Light Switch (on/off)")
# Device data -> Port/Channel Number -> ''Device ID'' -> '''save''' (codes correspond to the Device ID or Device Name you've set in /etc/tellstick.conf)

== Troubleshooting ==

== Reference Info ==
[http://www.telldus.se/products/tellstick Manufacturer website]

Dianemo iOS Orbiter

2011-11-17T11:25:58Z

JoakimL:

[[Category:Orbiters]]
{{versioninfo|810Status=works|810UpdatedDate=2nd May 2011|810UpdatedBy=totallymaxed}}

 
== About ==
[[Image:IOS_Orb_Home_Screen.JPG|left|200px]]
The Dianemo iOS Orbiter is a touch orbiter based on [[RoamingOrb]] by Foxi352. It uses the same techniques as [[Web Orbiter 2.0]] and [[Touch Orbiter]] in that it connects with an instance of Proxy_Orbiter running on your Dianemo NerveCentre or LinuxMCE Core. Dianemo iOS Orbiter is compatible with both Dianemo NerveCentre's & LinuxMCE Core's but will offer a number of additional features and capabilities when used in conjunction with a NerveCentre. The Dianemo iOS Orbiter is compatible with iPhone3G, iPhone3GS, iPhone4, all models of iPod Touch and iPad.

 
== Config needed in LMCE ==
Check [[Web_Orbiter_2.0|Web Orbiter 2.0]] for config. Here you will find the Device Number needed for configureing the App.

== Current Version - Dianemo iOS Orbiter v1.4 ==
This version has the interactive layer implemented and has some fixes for selections & hilights while using the interactive layer.

== Dianemo iOS Orbiter V1.2 (*Preview*) ==
Version 1.2 has just been submitted to Apple for review (07-07-2011) and should be available from the iOS App store shortly. Below are some videos that show off some of the new features/capabilities in this release;

http://youtu.be/y_vBXAZHqdY 
http://www.youtube.com/watch?v=5nXoRJ9RaN4

This version implements [[Enhanced UI]].

== Dianemo iOS Orbiter V1.1 ==
Version 1.1 of the Dianemo iOS Orbiter App includes a number of new features and capabilities;
* Supports landscape rotation on iPhone, iPod Touch, iPad & iPad2
* New Tab Bar UI with swipe up/down gesture to display/hide Tab bar in the Orbiter view - allows Orbiter to stay full screen all the time.
** Use the Tab Bar to switch between Orbiter, Configuration & Help views.
** Swipe down in the Orbiter view to hide & swipe up to display.
* Ability to store multiple connection settings and switch between them easily.
* If you are a Dianemo user then v1.1 also supports secure encrypted remote access to your NerveCentre via Dianemo's remote access portal too and allows you to swap between 'Local' & 'Remote' mode for any number of installations.
* Help tab displays online help & info pages
 

<gallery widths=300px caption="iOS Orbiter v1.1 screen images">
Image:IOS Orbiter Home.jpg|Home screen with new Tab UI displayed
Image:IOS Orbiter Help Connection Details.jpg|New connection details screen
Image:IOS Orbiter Connections.jpg|Store any No. of connection profiles
Image:IOS Orbiter Connection Manager.jpg|Each connection supports 'External' & 'Internal' mode
</gallery>

 

=== New Features in Dianemo v1.1 ===

Dianemo v1.1 has support for rotation in either landscape orientation, supports multiple connection profiles and secure remote access via the Dianemo remote access portal. The most obvious new feature in Dianemo 1.1 is the new Tab Bar UI that is displayed across the bottom of the screen. The Tab Bar provides access to the new in-app features and settings.

==== The Tab Bar - What the Tabs do ====

* '''Orbiter Tab'''
** The Orbiter Tab displays the Orbiter view which is the remote control UI for your Dianemo Home Automation System. For the Orbiter view to work correctly you need to have setup a Connection to your Dianemo system in the Configuration Tab (see below). The orbiter View is the only view that allows you to Show/Hide the Tab bar. To hide the Tab bar swipe you finger downwards on your devices screen above the Tab Bar - the Tab Bar should slide off the bottom of the screen. To Display the Tab Bar again swipe your finger upwards on your devices screen - the Tab Bar will will slide back on to the screen. Hiding the Tab Bar is useful when you are using the Orbiter View to access and control your Dianemo system.
* '''Configuration Tab'''
** The Configuration Tab displays the Configuration View on your devices display. The Configuration View is where you setup & manage the connection between your iOS device and you Dianemo System. You can create as many connections as you need in the Connection View - for example if you have more than one home with a Dianemo System installed then you can have a connection for each. Or you might be visiting a friends home who also has a Dianemo System and you can have a connection for that system too.
** The Configuration Tab will display each of your connections by name. At the bottom of the Configuration Tab list you will see ‘<New Connection>’ touch this to create a new connection. If you touch ‘<New Connection>’ then you see the Configuration Settings view for your new connection - this is where you enter the details about your Dianemo System. The only optional fields below are User Name & Password - you can omitt these if you do not have a Dianemo remote portal account.
*** Description - enter a unique name for this connection in this field.
*** Installation No. - enter your Dianemo Systems 5 digit installation id or your LinuxMCE installation number in this field.
*** Device No. - enter the device number of the 'Generic Web Device' here ** Not a port number as in v1.0 **.
*** User name - enter your Dianemo remote portal user name here.
*** Password - enter your Dianemo remote portal password here.
*** NerveCentre IP - enter the LAN IP address of your Dianemo NerveCentre here.
** If you touch an existing connection the screen will display the configuration view for that connection. In this view you can switch from a ‘Local’ connection ie using your Dianemo Systems Wifi to allow your device to connect or a ‘Remote’ connection that allows you to connect securely to your Dianemo System when away from home. When you touch either ‘Connect locally’ or ‘Connect remotely’ your device will switch back to the Connections view and you will see either ‘Internal’ or ‘External’ indicated for the connection you are using.
** You can also ‘Edit’ the connection and ‘Delete’ it.
** The Connections View also allows you to set Global Settings. These are settings that apply to whatever Connection you are currently using. To access your Global settings touch the ‘Settings’ button in the top right corner of the Connections View screen. The Global Settings View has three settings.
*** Wifi only - if this setting is switched to ‘ON’ then the Dianemo App will only use Wifi for its data connection. If this setting is switched to ‘OFF’ and your device also has a mobile or cellular data connection then the Dianemo App will use that connection if it needs to.
*** Load Indicator - this setting determines whether the Dianemo App displays its load indicator whe it is communicating with your Dianemo System when in the Orbiter View. If this setting is ‘ON’ then the load indicator will be displayed. If this setting is ‘OFF’ then no load indicator will be displayed.
*** Polling Frequency - this slider allows you to control how frequently the Dianemo App will check back with your Dianemo System to see if there are things it should alert you to or display on-screen in the Orbiter View.
*** Touch ‘Save Settings’ to save any changes you have made in the Global Settings view. Touch ‘Back’ if you do not want to save any changes you have made.
* '''Help Tab'''
** Touch the ‘Help’ Tab to display online Help about the Dianemo App and also a quick overview of the Dianemo Home Automation system itself for those of you who have not installed Dianemo in your home yet.
* '''About Tab'''
** The About Tab displays the About View which contains information about the App, CHT Ltd and the development team behind the Dianemo App.

== Availability ==
The v1.1 App is available now in the Apple App store as a Free download for all iOS device users. As previously this App contains NO advertising.
 

== Installation ==
Installation is simple and is carried out the same way as for any other iOS app.
*Connect to the app store either from your PC or Laptop or your iOS device..
*Search for the app "Dianemo"
*On the description page touch on "Free" to install it (you may be required to enter your iTunes store account details - the App is however Free).
*If you downloaded the App on your PC or Laptop you will need to sync your iOS device to install it.

 
== Configuration for v1.0==
[[Image:IOS_Orb_Settings.JPG|left|200px]]
 After having installed the app you first have to set your preferences. Dianemo iOS Orbiter integrates into the standard "Settings" app of your iOS device. Touch the Settings app and scroll down to the "Dianemo" entry. Touch "Dianemo" to change the settings You should at least set the server IP and the server port of the proxy orbiter for your iOS device. If you have installed the App on an iPhone then setting the 'Restrict to WiFi' setting to 'On' will stop your iPhone from using the mobile network accidentally. Poll delay will adjust how frequently the App checks back with the Core to see if there are any updates for the currently displayed screen (usually it is best to leave this setting at its default '1 sec' setting). The 'Image reload on shake' option allows you to trigger a screen reload by shaking your iOS device (useful if the 'Poll delay' setting is set to longer than a few secs). The 'Image load indicator' setting determines whether the App displays am animated progress 'wheel' in the centre of the screen when ever an update is underway.

Dianemo iOS Orbiter

2011-11-17T11:23:59Z

JoakimL:

[[Category:Orbiters]]
{{versioninfo|810Status=works|810UpdatedDate=2nd May 2011|810UpdatedBy=totallymaxed}}

 
== About ==
[[Image:IOS_Orb_Home_Screen.JPG|left|200px]]
The Dianemo iOS Orbiter is a touch orbiter based on [[RoamingOrb]] by Foxi352. It uses the same techniques as [[Web Orbiter 2.0]] and [[Touch Orbiter]] in that it connects with an instance of Proxy_Orbiter running on your Dianemo NerveCentre or LinuxMCE Core. Dianemo iOS Orbiter is compatible with both Dianemo NerveCentre's & LinuxMCE Core's but will offer a number of additional features and capabilities when used in conjunction with a NerveCentre. The Dianemo iOS Orbiter is compatible with iPhone3G, iPhone3GS, iPhone4, all models of iPod Touch and iPad.

 
== Config needed in LMCE ==
Check [[Web_Orbiter_2.0]Web Orbiter 2.0] for config. Here you will find the Device Number needed for configureing the App.

== Current Version - Dianemo iOS Orbiter v1.4 ==
This version has the interactive layer implemented and has some fixes for selections & hilights while using the interactive layer.

== Dianemo iOS Orbiter V1.2 (*Preview*) ==
Version 1.2 has just been submitted to Apple for review (07-07-2011) and should be available from the iOS App store shortly. Below are some videos that show off some of the new features/capabilities in this release;

http://youtu.be/y_vBXAZHqdY 
http://www.youtube.com/watch?v=5nXoRJ9RaN4

This version implements [[Enhanced UI]].

== Dianemo iOS Orbiter V1.1 ==
Version 1.1 of the Dianemo iOS Orbiter App includes a number of new features and capabilities;
* Supports landscape rotation on iPhone, iPod Touch, iPad & iPad2
* New Tab Bar UI with swipe up/down gesture to display/hide Tab bar in the Orbiter view - allows Orbiter to stay full screen all the time.
** Use the Tab Bar to switch between Orbiter, Configuration & Help views.
** Swipe down in the Orbiter view to hide & swipe up to display.
* Ability to store multiple connection settings and switch between them easily.
* If you are a Dianemo user then v1.1 also supports secure encrypted remote access to your NerveCentre via Dianemo's remote access portal too and allows you to swap between 'Local' & 'Remote' mode for any number of installations.
* Help tab displays online help & info pages
 

<gallery widths=300px caption="iOS Orbiter v1.1 screen images">
Image:IOS Orbiter Home.jpg|Home screen with new Tab UI displayed
Image:IOS Orbiter Help Connection Details.jpg|New connection details screen
Image:IOS Orbiter Connections.jpg|Store any No. of connection profiles
Image:IOS Orbiter Connection Manager.jpg|Each connection supports 'External' & 'Internal' mode
</gallery>

 

=== New Features in Dianemo v1.1 ===

Dianemo v1.1 has support for rotation in either landscape orientation, supports multiple connection profiles and secure remote access via the Dianemo remote access portal. The most obvious new feature in Dianemo 1.1 is the new Tab Bar UI that is displayed across the bottom of the screen. The Tab Bar provides access to the new in-app features and settings.

==== The Tab Bar - What the Tabs do ====

* '''Orbiter Tab'''
** The Orbiter Tab displays the Orbiter view which is the remote control UI for your Dianemo Home Automation System. For the Orbiter view to work correctly you need to have setup a Connection to your Dianemo system in the Configuration Tab (see below). The orbiter View is the only view that allows you to Show/Hide the Tab bar. To hide the Tab bar swipe you finger downwards on your devices screen above the Tab Bar - the Tab Bar should slide off the bottom of the screen. To Display the Tab Bar again swipe your finger upwards on your devices screen - the Tab Bar will will slide back on to the screen. Hiding the Tab Bar is useful when you are using the Orbiter View to access and control your Dianemo system.
* '''Configuration Tab'''
** The Configuration Tab displays the Configuration View on your devices display. The Configuration View is where you setup & manage the connection between your iOS device and you Dianemo System. You can create as many connections as you need in the Connection View - for example if you have more than one home with a Dianemo System installed then you can have a connection for each. Or you might be visiting a friends home who also has a Dianemo System and you can have a connection for that system too.
** The Configuration Tab will display each of your connections by name. At the bottom of the Configuration Tab list you will see ‘<New Connection>’ touch this to create a new connection. If you touch ‘<New Connection>’ then you see the Configuration Settings view for your new connection - this is where you enter the details about your Dianemo System. The only optional fields below are User Name & Password - you can omitt these if you do not have a Dianemo remote portal account.
*** Description - enter a unique name for this connection in this field.
*** Installation No. - enter your Dianemo Systems 5 digit installation id or your LinuxMCE installation number in this field.
*** Device No. - enter the device number of the 'Generic Web Device' here ** Not a port number as in v1.0 **.
*** User name - enter your Dianemo remote portal user name here.
*** Password - enter your Dianemo remote portal password here.
*** NerveCentre IP - enter the LAN IP address of your Dianemo NerveCentre here.
** If you touch an existing connection the screen will display the configuration view for that connection. In this view you can switch from a ‘Local’ connection ie using your Dianemo Systems Wifi to allow your device to connect or a ‘Remote’ connection that allows you to connect securely to your Dianemo System when away from home. When you touch either ‘Connect locally’ or ‘Connect remotely’ your device will switch back to the Connections view and you will see either ‘Internal’ or ‘External’ indicated for the connection you are using.
** You can also ‘Edit’ the connection and ‘Delete’ it.
** The Connections View also allows you to set Global Settings. These are settings that apply to whatever Connection you are currently using. To access your Global settings touch the ‘Settings’ button in the top right corner of the Connections View screen. The Global Settings View has three settings.
*** Wifi only - if this setting is switched to ‘ON’ then the Dianemo App will only use Wifi for its data connection. If this setting is switched to ‘OFF’ and your device also has a mobile or cellular data connection then the Dianemo App will use that connection if it needs to.
*** Load Indicator - this setting determines whether the Dianemo App displays its load indicator whe it is communicating with your Dianemo System when in the Orbiter View. If this setting is ‘ON’ then the load indicator will be displayed. If this setting is ‘OFF’ then no load indicator will be displayed.
*** Polling Frequency - this slider allows you to control how frequently the Dianemo App will check back with your Dianemo System to see if there are things it should alert you to or display on-screen in the Orbiter View.
*** Touch ‘Save Settings’ to save any changes you have made in the Global Settings view. Touch ‘Back’ if you do not want to save any changes you have made.
* '''Help Tab'''
** Touch the ‘Help’ Tab to display online Help about the Dianemo App and also a quick overview of the Dianemo Home Automation system itself for those of you who have not installed Dianemo in your home yet.
* '''About Tab'''
** The About Tab displays the About View which contains information about the App, CHT Ltd and the development team behind the Dianemo App.

== Availability ==
The v1.1 App is available now in the Apple App store as a Free download for all iOS device users. As previously this App contains NO advertising.
 

== Installation ==
Installation is simple and is carried out the same way as for any other iOS app.
*Connect to the app store either from your PC or Laptop or your iOS device..
*Search for the app "Dianemo"
*On the description page touch on "Free" to install it (you may be required to enter your iTunes store account details - the App is however Free).
*If you downloaded the App on your PC or Laptop you will need to sync your iOS device to install it.

 
== Configuration for v1.0==
[[Image:IOS_Orb_Settings.JPG|left|200px]]
 After having installed the app you first have to set your preferences. Dianemo iOS Orbiter integrates into the standard "Settings" app of your iOS device. Touch the Settings app and scroll down to the "Dianemo" entry. Touch "Dianemo" to change the settings You should at least set the server IP and the server port of the proxy orbiter for your iOS device. If you have installed the App on an iPhone then setting the 'Restrict to WiFi' setting to 'On' will stop your iPhone from using the mobile network accidentally. Poll delay will adjust how frequently the App checks back with the Core to see if there are any updates for the currently displayed screen (usually it is best to leave this setting at its default '1 sec' setting). The 'Image reload on shake' option allows you to trigger a screen reload by shaking your iOS device (useful if the 'Poll delay' setting is set to longer than a few secs). The 'Image load indicator' setting determines whether the App displays am animated progress 'wheel' in the centre of the screen when ever an update is underway.

Dianemo iOS Orbiter

2011-11-17T11:23:09Z

JoakimL: Link to config page added

[[Category:Orbiters]]
{{versioninfo|810Status=works|810UpdatedDate=2nd May 2011|810UpdatedBy=totallymaxed}}

 
== About ==
[[Image:IOS_Orb_Home_Screen.JPG|left|200px]]
The Dianemo iOS Orbiter is a touch orbiter based on [[RoamingOrb]] by Foxi352. It uses the same techniques as [[Web Orbiter 2.0]] and [[Touch Orbiter]] in that it connects with an instance of Proxy_Orbiter running on your Dianemo NerveCentre or LinuxMCE Core. Dianemo iOS Orbiter is compatible with both Dianemo NerveCentre's & LinuxMCE Core's but will offer a number of additional features and capabilities when used in conjunction with a NerveCentre. The Dianemo iOS Orbiter is compatible with iPhone3G, iPhone3GS, iPhone4, all models of iPod Touch and iPad.

 
== Config needed in LMCE ==
Check [[Web_Orbiter_2.0]] for config. Here you will find the Device Number needed for configureing the App.

== Current Version - Dianemo iOS Orbiter v1.4 ==
This version has the interactive layer implemented and has some fixes for selections & hilights while using the interactive layer.

== Dianemo iOS Orbiter V1.2 (*Preview*) ==
Version 1.2 has just been submitted to Apple for review (07-07-2011) and should be available from the iOS App store shortly. Below are some videos that show off some of the new features/capabilities in this release;

http://youtu.be/y_vBXAZHqdY 
http://www.youtube.com/watch?v=5nXoRJ9RaN4

This version implements [[Enhanced UI]].

== Dianemo iOS Orbiter V1.1 ==
Version 1.1 of the Dianemo iOS Orbiter App includes a number of new features and capabilities;
* Supports landscape rotation on iPhone, iPod Touch, iPad & iPad2
* New Tab Bar UI with swipe up/down gesture to display/hide Tab bar in the Orbiter view - allows Orbiter to stay full screen all the time.
** Use the Tab Bar to switch between Orbiter, Configuration & Help views.
** Swipe down in the Orbiter view to hide & swipe up to display.
* Ability to store multiple connection settings and switch between them easily.
* If you are a Dianemo user then v1.1 also supports secure encrypted remote access to your NerveCentre via Dianemo's remote access portal too and allows you to swap between 'Local' & 'Remote' mode for any number of installations.
* Help tab displays online help & info pages
 

<gallery widths=300px caption="iOS Orbiter v1.1 screen images">
Image:IOS Orbiter Home.jpg|Home screen with new Tab UI displayed
Image:IOS Orbiter Help Connection Details.jpg|New connection details screen
Image:IOS Orbiter Connections.jpg|Store any No. of connection profiles
Image:IOS Orbiter Connection Manager.jpg|Each connection supports 'External' & 'Internal' mode
</gallery>

 

=== New Features in Dianemo v1.1 ===

Dianemo v1.1 has support for rotation in either landscape orientation, supports multiple connection profiles and secure remote access via the Dianemo remote access portal. The most obvious new feature in Dianemo 1.1 is the new Tab Bar UI that is displayed across the bottom of the screen. The Tab Bar provides access to the new in-app features and settings.

==== The Tab Bar - What the Tabs do ====

* '''Orbiter Tab'''
** The Orbiter Tab displays the Orbiter view which is the remote control UI for your Dianemo Home Automation System. For the Orbiter view to work correctly you need to have setup a Connection to your Dianemo system in the Configuration Tab (see below). The orbiter View is the only view that allows you to Show/Hide the Tab bar. To hide the Tab bar swipe you finger downwards on your devices screen above the Tab Bar - the Tab Bar should slide off the bottom of the screen. To Display the Tab Bar again swipe your finger upwards on your devices screen - the Tab Bar will will slide back on to the screen. Hiding the Tab Bar is useful when you are using the Orbiter View to access and control your Dianemo system.
* '''Configuration Tab'''
** The Configuration Tab displays the Configuration View on your devices display. The Configuration View is where you setup & manage the connection between your iOS device and you Dianemo System. You can create as many connections as you need in the Connection View - for example if you have more than one home with a Dianemo System installed then you can have a connection for each. Or you might be visiting a friends home who also has a Dianemo System and you can have a connection for that system too.
** The Configuration Tab will display each of your connections by name. At the bottom of the Configuration Tab list you will see ‘<New Connection>’ touch this to create a new connection. If you touch ‘<New Connection>’ then you see the Configuration Settings view for your new connection - this is where you enter the details about your Dianemo System. The only optional fields below are User Name & Password - you can omitt these if you do not have a Dianemo remote portal account.
*** Description - enter a unique name for this connection in this field.
*** Installation No. - enter your Dianemo Systems 5 digit installation id or your LinuxMCE installation number in this field.
*** Device No. - enter the device number of the 'Generic Web Device' here ** Not a port number as in v1.0 **.
*** User name - enter your Dianemo remote portal user name here.
*** Password - enter your Dianemo remote portal password here.
*** NerveCentre IP - enter the LAN IP address of your Dianemo NerveCentre here.
** If you touch an existing connection the screen will display the configuration view for that connection. In this view you can switch from a ‘Local’ connection ie using your Dianemo Systems Wifi to allow your device to connect or a ‘Remote’ connection that allows you to connect securely to your Dianemo System when away from home. When you touch either ‘Connect locally’ or ‘Connect remotely’ your device will switch back to the Connections view and you will see either ‘Internal’ or ‘External’ indicated for the connection you are using.
** You can also ‘Edit’ the connection and ‘Delete’ it.
** The Connections View also allows you to set Global Settings. These are settings that apply to whatever Connection you are currently using. To access your Global settings touch the ‘Settings’ button in the top right corner of the Connections View screen. The Global Settings View has three settings.
*** Wifi only - if this setting is switched to ‘ON’ then the Dianemo App will only use Wifi for its data connection. If this setting is switched to ‘OFF’ and your device also has a mobile or cellular data connection then the Dianemo App will use that connection if it needs to.
*** Load Indicator - this setting determines whether the Dianemo App displays its load indicator whe it is communicating with your Dianemo System when in the Orbiter View. If this setting is ‘ON’ then the load indicator will be displayed. If this setting is ‘OFF’ then no load indicator will be displayed.
*** Polling Frequency - this slider allows you to control how frequently the Dianemo App will check back with your Dianemo System to see if there are things it should alert you to or display on-screen in the Orbiter View.
*** Touch ‘Save Settings’ to save any changes you have made in the Global Settings view. Touch ‘Back’ if you do not want to save any changes you have made.
* '''Help Tab'''
** Touch the ‘Help’ Tab to display online Help about the Dianemo App and also a quick overview of the Dianemo Home Automation system itself for those of you who have not installed Dianemo in your home yet.
* '''About Tab'''
** The About Tab displays the About View which contains information about the App, CHT Ltd and the development team behind the Dianemo App.

== Availability ==
The v1.1 App is available now in the Apple App store as a Free download for all iOS device users. As previously this App contains NO advertising.
 

== Installation ==
Installation is simple and is carried out the same way as for any other iOS app.
*Connect to the app store either from your PC or Laptop or your iOS device..
*Search for the app "Dianemo"
*On the description page touch on "Free" to install it (you may be required to enter your iTunes store account details - the App is however Free).
*If you downloaded the App on your PC or Laptop you will need to sync your iOS device to install it.

 
== Configuration for v1.0==
[[Image:IOS_Orb_Settings.JPG|left|200px]]
 After having installed the app you first have to set your preferences. Dianemo iOS Orbiter integrates into the standard "Settings" app of your iOS device. Touch the Settings app and scroll down to the "Dianemo" entry. Touch "Dianemo" to change the settings You should at least set the server IP and the server port of the proxy orbiter for your iOS device. If you have installed the App on an iPhone then setting the 'Restrict to WiFi' setting to 'On' will stop your iPhone from using the mobile network accidentally. Poll delay will adjust how frequently the App checks back with the Core to see if there are any updates for the currently displayed screen (usually it is best to leave this setting at its default '1 sec' setting). The 'Image reload on shake' option allows you to trigger a screen reload by shaking your iOS device (useful if the 'Poll delay' setting is set to longer than a few secs). The 'Image load indicator' setting determines whether the App displays am animated progress 'wheel' in the centre of the screen when ever an update is underway.

Tellstick

2011-11-14T13:41:29Z

JoakimL:

[[Category: Hardware]]
{{Versioninfo|810Status=Working, plug'n play supported|810UpdatedDate=7 january 2011|810UpdatedBy=[[User:JoakimL|JoakimL]]|1004Status=Working, plug'n play supported|1004UpdatedDate=14 november 2011|1004UpdatedBy=[[User:JoakimL|JoakimL]]}}
{| align="right"
| __TOC__
|}
[[Category: Automation]]
[[Category: RF Control]]
[[Category: Tellstick]]

== Description ==
The Tellstick is a power controller for cheap RF devices like the Nexa line. It's detected with LMCE's Plug-n Play.
Currently only basic support is added, namely power on, power off and dimlevel.
N.B. this is an RF tranmsmitter, it cannot read the state of the devices, nor can it receive data from remotes, sensors or other equipment sending an RF signal. Telldus have developed a device for this (Tellstick Duo) which is not supported at this time.

== Setup ==
The device is plug and play for LMCE, but at this point you'll need to add the driver software yourself. Install the telldus-core package as described [http://developer.telldus.se/wiki/TellStickInstallationUbuntu here]

Add the following lines to your /etc/apt/sources.list: (This is pointing to 2.0 repos, 2.1 currently break functionality)
deb http://download.telldus.com/debian/ 2.0 main

If you want to try the latest beta software, also add the following:
deb http://download.telldus.com/debian/ unstable main

The Telldus public key for apt-secure is added with
wget -q http://download.telldus.se/debian/telldus-public.key -O- | sudo apt-key add -
The key fingerprint is
70C4 10C9 D73D 53E8 38B3 1C58 5A94 9181 E501 EA76
Telldus Technologies AB <info.tech@telldus.se>

To install telldus-core
sudo apt-get update
sudo apt-get install telldus-core

If you install telldus-core version 2.1 you need to downgrade. If you get any trouble (like cannot connect to Telldus service or lib missing), install the correct libtelldus by:
wget http://download.telldus.com/debian/pool/2.0/libtelldus-core2_2.0.4-2_i386.deb
sudo dpkg -i libtelldus-core2_2.0.4-2_i386.deb

== Adding lights ==
# [http://192.168.80.1/ web admin] -> Show devices tree -> Telldus USB RF controller
# Create Child Device -> Pick device template -> ''take your pick'' (I added "Light Switch (on/off)")
# Device data -> Port/Channel Number -> ''Device ID'' -> '''save''' (codes correspond to the Device ID or Device Name you've set in /etc/tellstick.conf)

== Troubleshooting ==

== Reference Info ==
[http://www.telldus.se/products/tellstick Manufacturer website]

Tellstick

2011-11-14T13:40:55Z

JoakimL: 10.04 info and Telldus 2.0/2.1 issues

[[Category: Hardware]]
{{Versioninfo|810Status=Working, plug'n play supported|810UpdatedDate=7 january 2011|810UpdatedBy=[[User:JoakimL|JoakimL]]|1004Status=Working, plug'n play supported|1004UpdatedDate=14 november 2011|1004UpdatedBy=[[User:JoakimL|JoakimL]]}}
{| align="right"
| __TOC__
|}
[[Category: Automation]]
[[Category: RF Control]]
[[Category: Tellstick]]

== Description ==
The Tellstick is a power controller for cheap RF devices like the Nexa line. It's detected with LMCE's Plug-n Play.
Currently only basic support is added, namely power on, power off and dimlevel.
N.B. this is an RF tranmsmitter, it cannot read the state of the devices, nor can it receive data from remotes, sensors or other equipment sending an RF signal. Telldus have developed a device for this (Tellstick Duo) which is not supported at this time.

== Setup ==
The device is plug and play for LMCE, but at this point you'll need to add the driver software yourself. Install the telldus-core package as described [http://developer.telldus.se/wiki/TellStickInstallationUbuntu here]

Add the following lines to your /etc/apt/sources.list: (This is pointing to 2.0 repos, 2.1 currently break functionality)
deb http://download.telldus.com/debian/ 2.0 main

If you want to try the latest beta software, also add the following:
deb http://download.telldus.com/debian/ unstable main

The Telldus public key for apt-secure is added with
wget -q http://download.telldus.se/debian/telldus-public.key -O- | sudo apt-key add -
The key fingerprint is
70C4 10C9 D73D 53E8 38B3 1C58 5A94 9181 E501 EA76
Telldus Technologies AB <info.tech@telldus.se>

To install telldus-core
sudo apt-get update
sudo apt-get install telldus-core

If you install telldus-core version 2.1 you need to downgrade. If you get any trouble (like cannot connect to Telldus service or lib missing), install the correct libtelldus by:
- wget http://download.telldus.com/debian/pool/2.0/libtelldus-core2_2.0.4-2_i386.deb
- sudo dpkg -i libtelldus-core2_2.0.4-2_i386.deb

== Adding lights ==
# [http://192.168.80.1/ web admin] -> Show devices tree -> Telldus USB RF controller
# Create Child Device -> Pick device template -> ''take your pick'' (I added "Light Switch (on/off)")
# Device data -> Port/Channel Number -> ''Device ID'' -> '''save''' (codes correspond to the Device ID or Device Name you've set in /etc/tellstick.conf)

== Troubleshooting ==

== Reference Info ==
[http://www.telldus.se/products/tellstick Manufacturer website]

Tellstick

2011-11-14T10:23:25Z

JoakimL:

[[Category: Hardware]]
{{Versioninfo|810Status=Working, plug'n play supported|810UpdatedDate=7 january 2011|810UpdatedBy=[[User:JoakimL|JoakimL]]|1004Status=Being verified|1004UpdatedDate=14 november 2011|1004UpdatedBy=[[User:JoakimL|JoakimL]]}}
{| align="right"
| __TOC__
|}
[[Category: Automation]]
[[Category: RF Control]]
[[Category: Tellstick]]

== Description ==
The Tellstick is a power controller for cheap RF devices like the Nexa line. It's detected with LMCE's Plug-n Play.
Currently only basic support is added, namely power on, power off and dimlevel.
N.B. this is an RF tranmsmitter, it cannot read the state of the devices, nor can it receive data from remotes, sensors or other equipment sending an RF signal. Telldus have developed a device for this (Tellstick Duo) which is not supported at this time.

== Setup ==
The device is plug and play for LMCE, but at this point you'll need to add the driver software yourself. Install the telldus-core package as described [http://developer.telldus.se/wiki/TellStickInstallationUbuntu here]

Add the following lines to your /etc/apt/sources.list: (This is pointing to 2.0 repos, 2.1 currently break functionality)
deb http://download.telldus.com/debian/ 2.0 main

If you want to try the latest beta software, also add the following:
deb http://download.telldus.com/debian/ unstable main

The Telldus public key for apt-secure is added with
wget -q http://download.telldus.se/debian/telldus-public.key -O- | sudo apt-key add -
The key fingerprint is
70C4 10C9 D73D 53E8 38B3 1C58 5A94 9181 E501 EA76
Telldus Technologies AB <info.tech@telldus.se>

To install telldus-core
sudo apt-get update
sudo apt-get install telldus-core

== Adding lights ==
# [http://192.168.80.1/ web admin] -> Show devices tree -> Telldus USB RF controller
# Create Child Device -> Pick device template -> ''take your pick'' (I added "Light Switch (on/off)")
# Device data -> Port/Channel Number -> ''Device ID'' -> '''save''' (codes correspond to the Device ID or Device Name you've set in /etc/tellstick.conf)

== Troubleshooting ==

== Reference Info ==
[http://www.telldus.se/products/tellstick Manufacturer website]

Tellstick

2011-11-14T10:14:56Z

JoakimL:

[[Category: Hardware]]
{{Versioninfo|810Status=Working, plug'n play supported|810UpdatedDate=7 january 2011|810UpdatedBy=JoakimL
|1040Status=Being verified|810UpdatedDate=14 november 2011|1004UpdatedBy=JoakimL}}
{| align="right"
| __TOC__
|}
[[Category: Automation]]
[[Category: RF Control]]
[[Category: Tellstick]]

== Description ==
The Tellstick is a power controller for cheap RF devices like the Nexa line. It's detected with LMCE's Plug-n Play.
Currently only basic support is added, namely power on, power off and dimlevel.
N.B. this is an RF tranmsmitter, it cannot read the state of the devices, nor can it receive data from remotes, sensors or other equipment sending an RF signal. Telldus have developed a device for this (Tellstick Duo) which is not supported at this time.

== Setup ==
The device is plug and play for LMCE, but at this point you'll need to add the driver software yourself. Install the telldus-core package as described [http://developer.telldus.se/wiki/TellStickInstallationUbuntu here]

Add the following lines to your /etc/apt/sources.list: (This is pointing to 2.0 repos, 2.1 currently break functionality)
deb http://download.telldus.com/debian/ 2.0 main

If you want to try the latest beta software, also add the following:
deb http://download.telldus.com/debian/ unstable main

The Telldus public key for apt-secure is added with
wget -q http://download.telldus.se/debian/telldus-public.key -O- | sudo apt-key add -
The key fingerprint is
70C4 10C9 D73D 53E8 38B3 1C58 5A94 9181 E501 EA76
Telldus Technologies AB <info.tech@telldus.se>

To install telldus-core
sudo apt-get update
sudo apt-get install telldus-core

== Adding lights ==
# [http://192.168.80.1/ web admin] -> Show devices tree -> Telldus USB RF controller
# Create Child Device -> Pick device template -> ''take your pick'' (I added "Light Switch (on/off)")
# Device data -> Port/Channel Number -> ''Device ID'' -> '''save''' (codes correspond to the Device ID or Device Name you've set in /etc/tellstick.conf)

== Troubleshooting ==

== Reference Info ==
[http://www.telldus.se/products/tellstick Manufacturer website]

Tellstick

2011-11-14T10:14:24Z

JoakimL:

[[Category: Hardware]]
{{Versioninfo|810Status=Working, plug'n play supported|810UpdatedDate=7 january 2011|810UpdatedBy=JoakimL}}
{{Versioninfo|1040Status=Being verified|810UpdatedDate=14 november 2011|1004UpdatedBy=JoakimL}}
{| align="right"
| __TOC__
|}
[[Category: Automation]]
[[Category: RF Control]]
[[Category: Tellstick]]

== Description ==
The Tellstick is a power controller for cheap RF devices like the Nexa line. It's detected with LMCE's Plug-n Play.
Currently only basic support is added, namely power on, power off and dimlevel.
N.B. this is an RF tranmsmitter, it cannot read the state of the devices, nor can it receive data from remotes, sensors or other equipment sending an RF signal. Telldus have developed a device for this (Tellstick Duo) which is not supported at this time.

== Setup ==
The device is plug and play for LMCE, but at this point you'll need to add the driver software yourself. Install the telldus-core package as described [http://developer.telldus.se/wiki/TellStickInstallationUbuntu here]

Add the following lines to your /etc/apt/sources.list: (This is pointing to 2.0 repos, 2.1 currently break functionality)
deb http://download.telldus.com/debian/ 2.0 main

If you want to try the latest beta software, also add the following:
deb http://download.telldus.com/debian/ unstable main

The Telldus public key for apt-secure is added with
wget -q http://download.telldus.se/debian/telldus-public.key -O- | sudo apt-key add -
The key fingerprint is
70C4 10C9 D73D 53E8 38B3 1C58 5A94 9181 E501 EA76
Telldus Technologies AB <info.tech@telldus.se>

To install telldus-core
sudo apt-get update
sudo apt-get install telldus-core

== Adding lights ==
# [http://192.168.80.1/ web admin] -> Show devices tree -> Telldus USB RF controller
# Create Child Device -> Pick device template -> ''take your pick'' (I added "Light Switch (on/off)")
# Device data -> Port/Channel Number -> ''Device ID'' -> '''save''' (codes correspond to the Device ID or Device Name you've set in /etc/tellstick.conf)

== Troubleshooting ==

== Reference Info ==
[http://www.telldus.se/products/tellstick Manufacturer website]

Tellstick

2011-11-14T10:14:01Z

JoakimL: Changed to 2.0 repos

[[Category: Hardware]]
{{Versioninfo|810Status=Working, plug'n play supported|810UpdatedDate=7 january 2011|810UpdatedBy=JoakimL}
{Versioninfo|1040Status=Being verified|810UpdatedDate=14 november 2011|1004UpdatedBy=JoakimL}}
{| align="right"
| __TOC__
|}
[[Category: Automation]]
[[Category: RF Control]]
[[Category: Tellstick]]

== Description ==
The Tellstick is a power controller for cheap RF devices like the Nexa line. It's detected with LMCE's Plug-n Play.
Currently only basic support is added, namely power on, power off and dimlevel.
N.B. this is an RF tranmsmitter, it cannot read the state of the devices, nor can it receive data from remotes, sensors or other equipment sending an RF signal. Telldus have developed a device for this (Tellstick Duo) which is not supported at this time.

== Setup ==
The device is plug and play for LMCE, but at this point you'll need to add the driver software yourself. Install the telldus-core package as described [http://developer.telldus.se/wiki/TellStickInstallationUbuntu here]

Add the following lines to your /etc/apt/sources.list: (This is pointing to 2.0 repos, 2.1 currently break functionality)
deb http://download.telldus.com/debian/ 2.0 main

If you want to try the latest beta software, also add the following:
deb http://download.telldus.com/debian/ unstable main

The Telldus public key for apt-secure is added with
wget -q http://download.telldus.se/debian/telldus-public.key -O- | sudo apt-key add -
The key fingerprint is
70C4 10C9 D73D 53E8 38B3 1C58 5A94 9181 E501 EA76
Telldus Technologies AB <info.tech@telldus.se>

To install telldus-core
sudo apt-get update
sudo apt-get install telldus-core

== Adding lights ==
# [http://192.168.80.1/ web admin] -> Show devices tree -> Telldus USB RF controller
# Create Child Device -> Pick device template -> ''take your pick'' (I added "Light Switch (on/off)")
# Device data -> Port/Channel Number -> ''Device ID'' -> '''save''' (codes correspond to the Device ID or Device Name you've set in /etc/tellstick.conf)

== Troubleshooting ==

== Reference Info ==
[http://www.telldus.se/products/tellstick Manufacturer website]

Tellstick

2011-11-14T08:08:41Z

JoakimL:

[[Category: Hardware]]
{{Versioninfo|810Status=Working, plug'n play supported|810UpdatedDate=7 january 2011|810UpdatedBy=JoakimL}}
{| align="right"
| __TOC__
|}
[[Category: Automation]]
[[Category: RF Control]]
[[Category: Tellstick]]

== Description ==
The Tellstick is a power controller for cheap RF devices like the Nexa line. It's detected with LMCE's Plug-n Play.
Currently only basic support is added, namely power on, power off and dimlevel.
N.B. this is an RF tranmsmitter, it cannot read the state of the devices, nor can it receive data from remotes, sensors or other equipment sending an RF signal. Telldus have developed a device for this (Tellstick Duo) which is not supported at this time.

== Setup ==
The device is plug and play for LMCE, but at this point you'll need to add the driver software yourself. Install the telldus-core package as described [http://developer.telldus.se/wiki/TellStickInstallationUbuntu here]

Add the following lines to your /etc/apt/sources.list:
deb http://download.telldus.com/debian/ stable main

If you want to try the latest beta software, also add the following:
deb http://download.telldus.com/debian/ unstable main

The Telldus public key for apt-secure is added with
wget -q http://download.telldus.se/debian/telldus-public.key -O- | sudo apt-key add -
The key fingerprint is
70C4 10C9 D73D 53E8 38B3 1C58 5A94 9181 E501 EA76
Telldus Technologies AB <info.tech@telldus.se>

To install telldus-core
sudo apt-get update
sudo apt-get install telldus-core

== Adding lights ==
# [http://192.168.80.1/ web admin] -> Show devices tree -> Telldus USB RF controller
# Create Child Device -> Pick device template -> ''take your pick'' (I added "Light Switch (on/off)")
# Device data -> Port/Channel Number -> ''Device ID'' -> '''save''' (codes correspond to the Device ID or Device Name you've set in /etc/tellstick.conf)

== Troubleshooting ==

== Reference Info ==
[http://www.telldus.se/products/tellstick Manufacturer website]

Installing 1004

2011-11-13T10:20:14Z

JoakimL:

Installing LinuxMCE-1004 is a fairly easy process that involves:

"THIS VERSION IS CURRENTLY UNDER DEVELOPMENT. IT KIND OF WORKS, BUT MAY DRIVE YOU INSANE. :)"

"PACKAGES ARE BEING BUILT, BUT WE HAVE ONLY BEGUN TO DEBUG THE ISSUES PRESENT. DO NOT ATTEMPT THIS UNLESS YOU WISH TO FIX BUGS, AND WILL FIX BUGS WITH US. THANKS."

"WE WILL NOT PROVIDE SUPPORT FOR THIS VERSION AT THIS TIME. DO NOT ASK. IF YOU CAN'T FIX STUFF, THIS IS NOT FOR YOU."

Since this is a pre-release version, we need your help to make it better. If you notice a problem, please do not just add a workaround here. Create a ticket in trac with plenty of detail on what the issue is and how to reproduce it, as well as any information you have on how to fix it. If there is a workaround, it is ok to post it here as long as you link to the ticket you just created.

* Installing Kubuntu 1004
* Updating Kubuntu 1004
* Installing LinuxMCE-1004 on top of the updated Kubuntu 1004

Before proceeding its wise to read the FAQ.
Because of the fact that it's a delicate installation small things make a huge difference.

Please see below for details on Internet Installation and DVD Installation methods.

'''Note: an active internet connection is required regardless of installation method.

==Internet Installation==
# Install Lucid Lynx desktop and update it. (download Kubuntu 1004 '''desktop''' release from http://releases.ubuntu.com/kubuntu/10.04/kubuntu-10.04.3-desktop-i386.iso
'''Currently, only the 32bit version of LinuxMCE is available. Only download the i386 version of 1004 Kubuntu, even if your system can support 64bit versions.''' Note: If Kubuntu asks whether you would like to install/activate 'Restricted Drivers' for your video card, ignore it and continue to step 2.
# Grab the latest installer script from [http://svn.linuxmce.org/svn/branches/LinuxMCE-0810/src/new-installer/mce-install.sh our servers].
# Run the following script (as root): mce-install.sh
# Reboot, wait for the activity to stop (see progress on console).

In other words, after installing Kubuntu:
# Run the following:
sudo -i
wget -q http://svn.linuxmce.org/svn/branches/LinuxMCE-1004/src/new-installer/mce-install.sh && chmod +x mce-install.sh
./mce-install.sh
reboot

If you have problems running Diskless_CreateTBZ.sh, check [[Error Running Diskless CreateTBZ.sh|this article]]. Otherwise please log a trac ticket.

If you then have problems netbooting your diskless media directors because you are receiving the error message "Diskless Setup Failed", check [[Diskless setup failed error in 0810 beta|this article]].

== Keeping Up-to-date with updates ==
'''Note''' It is strongly recommended that you do not update/upgrade a stable, working system. Also check /etc/apt/sources.list for accuracy after install. [[user:L3mce]]

Once you have installed LinuxMCE-1004, all you need to do to keep up-to-date with the latest and greatest, is run the following from a terminal on the core and each MD:
sudo apt-get update
sudo apt-get upgrade
Note: You should NOT run apt-get dist-upgrade after LinuxMCE is installed, as it can cause several problems, including having different kernel versions on your core and media directors, and the installation of new Kubuntu packages that can break some features!

== Outstanding issues ==
* The diskless image kernel package has a broken dependency.
* Orbiter and OrbiterGen might race a bit
* at least in one occasion the UI1 Orbiter didn't come back from the screen saver when keys and mouse were pressed

[[Category:Tutorials]]

SlimDevices / Logitech Squeezebox

2011-11-12T13:38:23Z

JoakimL:

[[Category: Hardware]]
[[Category: Audio]]
{{versioninfo}}
{{stub}}

[[Image:logitech-squeezebox-duet.jpg|right]]
= Status =
Supported with plug and play.

All Squeezeboxes with a display are plug and play. The Squeezebox receiver, when used without the accompanying remote Duet, needs to have some special treatment before it can be detected.

= Hardware =
This is list of current Logitech Squeezebox devices as of 06/2010:
* [http://www.logitech.com/en-gb/speakers-audio/wireless-music-systems/devices/4098 Squeezebox Receiver (150$)]
* [http://www.logitech.com/en-us/speakers_audio/wireless_music_systems/devices/5847 Squeezebox Radio (200$)]
* [http://www.logitech.com/en-us/speakers_audio/wireless_music_systems/devices/4707 Squeezebox Boom (300$)]
* [http://www.logitech.com/en-us/speakers_audio/wireless_music_systems/devices/5745 Squeezebox Touch (300$)]
* [http://www.logitech.com/en-us/speakers_audio/wireless_music_systems/devices/3817 Squeezebox Duet (400$)]
* [[Squeezebox 3 / Classic (100$ used)]]

= Software =
* SoftSqueeze 3.8 Software client for several platforms
**[http://softsqueeze.sourceforge.net Main page]
**[http://sourceforge.net/projects/softsqueeze/files/softsqueeze/softsqueeze-3.8 Direct download]

= Features =
* See for more information and setup: [[Use network audio players for a whole-house music solution]]
* Manufacturer product link: http://www.logitech.com/en-us/speakers_audio/wireless_music_systems
= Adding Squeezebox Receiver =
The Squeezebox Receiver needs to be configured before it can be used. The utility [http://projects.robinbowes.com/Net-UDAP/trac Net::UDAP] is used to configure the Squeezebox Receiver with the relevant IP configuration.

You can download a Windows standalone version of the Net:UDAP Utility here [http://slim2lirc.myown.mailcan.com/udap_shell_1_0_0.exe NET:UDAP Exe] You can find examples of the command set and usage here [http://projects.robinbowes.com/Net-UDAP/trac/wiki/SampleUsage Sample Command usage]

For a Receiver connected to a CAT5 network use the following commands in NET:UDAP to configure your SB Receiver;

Before entering the commands below into NET:UDAP you need to get your Receiver into 'Init mode' by pressing the button on the front for 6 secs - release the button when it flashes quickly in 'Red'. After a few seconds the button will start to flash slowly in 'Red'...now you are ready for the steps below (enter these commands into NET:UDAP);

discover
conf 1
set interface=1 lan_ip_mode=1 squeezecenter_address=192.168.80.1
save_data
reset

As soon as you enter the 'save_data' command above your Orbiters should display the announcement that a Squeezebox has been detected (accept it and add it to a room as usual). Now after you enter the 'reset' command above you should see that the Receivers button will change from 'Red' to 'Green'...and if this is the first time you have attached your Receiver to a Network it will probably download new updated firmware...the button will flash 'White' for about 30 secs...then it will change to a solid white. Now you should add your new SB Receiver to your Core's Floorplan (this is optional of course) and then do a 'Full Regen' from Web Admin...and your done!

Note: the above may refer to v710. See also http://wiki.linuxmce.org/index.php/Use_network_audio_players_for_a_whole-house_music_solution for adding a squeezebox to v810. After slimserver is downloaded and installed, don't forget to configure it at port 9000.

= Squeezebox remote stuff =
Just in case you misplaced your remote, but have a gc100 with IR emittors handy (like I did).
*[http://wiki.slimdevices.com/index.cgi?PluginRemoteControls Remote Control Plugins]
*[http://www.slimdevices.com/downloads/pronto/SqueezeboxCodes.xls IR code spreadsheet]

SlimDevices / Logitech Squeezebox

2011-11-12T13:37:51Z

JoakimL: Added SB3

[[Category: Hardware]]
[[Category: Audio]]
{{versioninfo}}
{{stub}}

[[Image:logitech-squeezebox-duet.jpg|right]]
= Status =
Supported with plug and play.

All Squeezeboxes with a display are plug and play. The Squeezebox receiver, when used without the accompanying remote Duet, needs to have some special treatment before it can be detected.

= Hardware =
This is list of current Logitech Squeezebox devices as of 06/2010:
* [http://www.logitech.com/en-gb/speakers-audio/wireless-music-systems/devices/4098 Squeezebox Receiver (150$)]
* [http://www.logitech.com/en-us/speakers_audio/wireless_music_systems/devices/5847 Squeezebox Radio (200$)]
* [http://www.logitech.com/en-us/speakers_audio/wireless_music_systems/devices/4707 Squeezebox Boom (300$)]
* [http://www.logitech.com/en-us/speakers_audio/wireless_music_systems/devices/5745 Squeezebox Touch (300$)]
* [http://www.logitech.com/en-us/speakers_audio/wireless_music_systems/devices/3817 Squeezebox Duet (400$)]
* [Squeezebox 3 / Classic (100$ used)]

= Software =
* SoftSqueeze 3.8 Software client for several platforms
**[http://softsqueeze.sourceforge.net Main page]
**[http://sourceforge.net/projects/softsqueeze/files/softsqueeze/softsqueeze-3.8 Direct download]

= Features =
* See for more information and setup: [[Use network audio players for a whole-house music solution]]
* Manufacturer product link: http://www.logitech.com/en-us/speakers_audio/wireless_music_systems
= Adding Squeezebox Receiver =
The Squeezebox Receiver needs to be configured before it can be used. The utility [http://projects.robinbowes.com/Net-UDAP/trac Net::UDAP] is used to configure the Squeezebox Receiver with the relevant IP configuration.

You can download a Windows standalone version of the Net:UDAP Utility here [http://slim2lirc.myown.mailcan.com/udap_shell_1_0_0.exe NET:UDAP Exe] You can find examples of the command set and usage here [http://projects.robinbowes.com/Net-UDAP/trac/wiki/SampleUsage Sample Command usage]

For a Receiver connected to a CAT5 network use the following commands in NET:UDAP to configure your SB Receiver;

Before entering the commands below into NET:UDAP you need to get your Receiver into 'Init mode' by pressing the button on the front for 6 secs - release the button when it flashes quickly in 'Red'. After a few seconds the button will start to flash slowly in 'Red'...now you are ready for the steps below (enter these commands into NET:UDAP);

discover
conf 1
set interface=1 lan_ip_mode=1 squeezecenter_address=192.168.80.1
save_data
reset

As soon as you enter the 'save_data' command above your Orbiters should display the announcement that a Squeezebox has been detected (accept it and add it to a room as usual). Now after you enter the 'reset' command above you should see that the Receivers button will change from 'Red' to 'Green'...and if this is the first time you have attached your Receiver to a Network it will probably download new updated firmware...the button will flash 'White' for about 30 secs...then it will change to a solid white. Now you should add your new SB Receiver to your Core's Floorplan (this is optional of course) and then do a 'Full Regen' from Web Admin...and your done!

Note: the above may refer to v710. See also http://wiki.linuxmce.org/index.php/Use_network_audio_players_for_a_whole-house_music_solution for adding a squeezebox to v810. After slimserver is downloaded and installed, don't forget to configure it at port 9000.

= Squeezebox remote stuff =
Just in case you misplaced your remote, but have a gc100 with IR emittors handy (like I did).
*[http://wiki.slimdevices.com/index.cgi?PluginRemoteControls Remote Control Plugins]
*[http://www.slimdevices.com/downloads/pronto/SqueezeboxCodes.xls IR code spreadsheet]

WTR610N

2011-11-11T13:46:04Z

JoakimL: WTR610N moved to WRT610N: Miss-spelling

#REDIRECT [[WRT610N]]

WRT610N

2011-11-11T13:46:04Z

JoakimL: WTR610N moved to WRT610N: Miss-spelling

[[Category: Hardware]]
See [[Linksys WRT54G]]

Linksys WRT610N

2011-11-11T13:45:03Z

JoakimL: Created page with "Category: Hardware See Linksys WRT54G"

[[Category: Hardware]]
See [[Linksys WRT54G]]

WRT610N

2011-11-11T13:44:40Z

JoakimL:

[[Category: Hardware]]
See [[Linksys WRT54G]]

WRT610N

2011-11-11T13:31:32Z

JoakimL:

[[Category: Hardware]]
See [[Linksys WTR54G]]

Linksys WRT54G

2011-11-11T13:31:09Z

JoakimL:

[[Category: Hardware]]
{{versioninfo|710Status=relevant|710UpdatedDate=27Aug2011|710UpdatedBy=Techstyle|810Status=relevant|810UpdatedDate=27Aug2011|810UpdatedBy=Techstyle}}
[[category:Networking]]
== Overview ==

Linksys WRT54G (and variants WRT54GS, WRT54GL, and WRTSL54GS) as well as WRTR610N is a Wi-Fi capable residential gateway from Linksys. The device is capable of sharing Internet connections among several computers via 802.3 Ethernet and 802.11b/g wireless data links.

The WRT54G is notable for being the first consumer-level network device that had its firmware source code released to satisfy the obligations of the GNU GPL. This allows programmers to modify the firmware to change or add functionality to the device. Several third-party firmware projects provide the public with enhanced firmware for the WRT54G

The original WRT54G was first released in December 2002. It comes with a 4+1 port network switch (the Internet/WAN port is also in the same internal network switch, but on a different VLAN). The devices have two removable antennas connected through Reverse Polarity TNC connectors. The WRT54GC router is an exception and has an internal antenna with optional external antenna. As a cost-cutting measure, the design of the latest version of the WRT54G no longer has detachable antennas or TNC connectors. Instead, version 8 routers simply route thin wires into antenna 'shells' eliminating the connector. As a result, Linksys HGA7T and similar external antennas are no longer compatible with this model.

== How to Configure this Device as a Switch ==

Do these steps in order:

1. Connect directly to the router and log on (default IP is 192.168.1.1, leave the username blank and type 'admin' in the password field)

2. Go to the Security page and disable the firewall (disable all items in the 'block WAN requests' section) - hit the save settings button
[[Image:WRT54G_Security.jpg]]

3. Go to 'Setup' page and change the local IP adress to something within the Core's Range. The Default range for a LinuxMCE Core is 192.168.80.2 to 192.168.90.128 for Pluto Devices and 192.168.80.129 to 192.168.80.254 for non-pluto devices. set the router's local IP to be in the non-Pluto range - mine is 192.168.80.130. - Again Save Settings
[[Image:WRT54G_IP.jpg]]

4. you will now have to re-logon to the new IP address (192.168.80.130 for me).

5. On the setup page again, below the local IP address, Disable the DHCP server - Save Settings.
(See above)

Reconnect the device to the Eth1 port on the core (to a LAN port not the WAN port) and power cycle it and you are all set.

WRT610N

2011-11-11T13:29:29Z

JoakimL:

See [[Linksys WTR54G]]

WRT610N

2011-11-11T13:29:14Z

JoakimL: Created page with "See WTR54G"

See [[WTR54G]]

Linksys WRT54G

2011-11-11T13:26:57Z

JoakimL:

[[Category: Hardware]]
{{versioninfo|710Status=relevant|710UpdatedDate=27Aug2011|710UpdatedBy=Techstyle|810Status=relevant|810UpdatedDate=27Aug2011|810UpdatedBy=Techstyle}}
[[category:Networking]]
== Overview ==

Linksys WRT54G (and variants WRT54GS, WRT54GL, and WRTSL54GS) as well as WTR610N is a Wi-Fi capable residential gateway from Linksys. The device is capable of sharing Internet connections among several computers via 802.3 Ethernet and 802.11b/g wireless data links.

The WRT54G is notable for being the first consumer-level network device that had its firmware source code released to satisfy the obligations of the GNU GPL. This allows programmers to modify the firmware to change or add functionality to the device. Several third-party firmware projects provide the public with enhanced firmware for the WRT54G

The original WRT54G was first released in December 2002. It comes with a 4+1 port network switch (the Internet/WAN port is also in the same internal network switch, but on a different VLAN). The devices have two removable antennas connected through Reverse Polarity TNC connectors. The WRT54GC router is an exception and has an internal antenna with optional external antenna. As a cost-cutting measure, the design of the latest version of the WRT54G no longer has detachable antennas or TNC connectors. Instead, version 8 routers simply route thin wires into antenna 'shells' eliminating the connector. As a result, Linksys HGA7T and similar external antennas are no longer compatible with this model.

== How to Configure this Device as a Switch ==

Do these steps in order:

1. Connect directly to the router and log on (default IP is 192.168.1.1, leave the username blank and type 'admin' in the password field)

2. Go to the Security page and disable the firewall (disable all items in the 'block WAN requests' section) - hit the save settings button
[[Image:WRT54G_Security.jpg]]

3. Go to 'Setup' page and change the local IP adress to something within the Core's Range. The Default range for a LinuxMCE Core is 192.168.80.2 to 192.168.90.128 for Pluto Devices and 192.168.80.129 to 192.168.80.254 for non-pluto devices. set the router's local IP to be in the non-Pluto range - mine is 192.168.80.130. - Again Save Settings
[[Image:WRT54G_IP.jpg]]

4. you will now have to re-logon to the new IP address (192.168.80.130 for me).

5. On the setup page again, below the local IP address, Disable the DHCP server - Save Settings.
(See above)

Reconnect the device to the Eth1 port on the core (to a LAN port not the WAN port) and power cycle it and you are all set.

Linksys WRT54G

2011-11-11T13:26:43Z

JoakimL: Added WTR610N

[[Category: Hardware]]
{{versioninfo|710Status=relevant|710UpdatedDate=27Aug2011|710UpdatedBy=Techstyle|810Status=relevant|810UpdatedDate=27Aug2011|810UpdatedBy=Techstyle}}
[[category:Networking]]
== Overview ==

Linksys WRT54G (and variants WRT54GS, WRT54GL, and WRTSL54GS)as well as WTR610N is a Wi-Fi capable residential gateway from Linksys. The device is capable of sharing Internet connections among several computers via 802.3 Ethernet and 802.11b/g wireless data links.

The WRT54G is notable for being the first consumer-level network device that had its firmware source code released to satisfy the obligations of the GNU GPL. This allows programmers to modify the firmware to change or add functionality to the device. Several third-party firmware projects provide the public with enhanced firmware for the WRT54G

The original WRT54G was first released in December 2002. It comes with a 4+1 port network switch (the Internet/WAN port is also in the same internal network switch, but on a different VLAN). The devices have two removable antennas connected through Reverse Polarity TNC connectors. The WRT54GC router is an exception and has an internal antenna with optional external antenna. As a cost-cutting measure, the design of the latest version of the WRT54G no longer has detachable antennas or TNC connectors. Instead, version 8 routers simply route thin wires into antenna 'shells' eliminating the connector. As a result, Linksys HGA7T and similar external antennas are no longer compatible with this model.

== How to Configure this Device as a Switch ==

Do these steps in order:

1. Connect directly to the router and log on (default IP is 192.168.1.1, leave the username blank and type 'admin' in the password field)

2. Go to the Security page and disable the firewall (disable all items in the 'block WAN requests' section) - hit the save settings button
[[Image:WRT54G_Security.jpg]]

3. Go to 'Setup' page and change the local IP adress to something within the Core's Range. The Default range for a LinuxMCE Core is 192.168.80.2 to 192.168.90.128 for Pluto Devices and 192.168.80.129 to 192.168.80.254 for non-pluto devices. set the router's local IP to be in the non-Pluto range - mine is 192.168.80.130. - Again Save Settings
[[Image:WRT54G_IP.jpg]]

4. you will now have to re-logon to the new IP address (192.168.80.130 for me).

5. On the setup page again, below the local IP address, Disable the DHCP server - Save Settings.
(See above)

Reconnect the device to the Eth1 port on the core (to a LAN port not the WAN port) and power cycle it and you are all set.

How to add your own GSD device

2011-02-16T13:01:22Z

JoakimL:

[[Category: Programmer's Guide]]
[[Category: Serial]]
[[Category: Tutorials]]
[[Category: GSD]]

Generic_Serial_Device (also known as [[GSD]]) is a LinuxMCE device that allows an end-user to do simple programming for RS232, serial USB or network connected devices.
This enables them to quickly and easily write drivers for such devices.

Note, however, that a GSD device driver is more limited than a compiled driver. The GSD driver allows only a single communication channel with the device (RS232, serial USB or a TCP connection across a network).
If your device has other communication channels (an UDP connection for example), you will have to write a driver in another language and compile it.

It is also possible to use a GSD device to send DCE commands to other devices. See for instance the Toshiba RAS series template, which acts as a sort of message translator, translating DCE thermostat command to IR commands sent through a IR transmitter.

== How to add your own GSD device ==

=== Examples ===

For those of you who like to learn by example, there are some already in the LinuxMCE database.
In the LinuxMCE web admin interface go to Advanced-->Configuration-->Device Templates and pick one of the following device templates:
* Panasonic IP camera: A simple driver that enables the retrieval of video frames from this network enabled camera
* Proliphix NT series thermostat: A more elaborate driver for a network enabled thermostat. This driver also sends events to the LMCE system in case, for example, the ambient temperature changes.
* Toshiba RAS series air condition: Another kind of GSD device, just receiving and sending DCE commands

=== Creating a new GSD device ===

The steps to add GSD device are following:

==== Install the necessary packages ====
Be sure that you have installed GSD package -
<pre>dpkg -l 'pluto-generic-serial-device'</pre>
(it should be there). This shouldn't normally be necessary as LMCE should automatically install the package when you have added such a device.

==== Create a device template ====
Created a device template for your system and specify that it should use GSD. The [[Edit_Device_Template]] page may be of help here.

Some things you should take into account:
* Add your template under the proper category; add it under category lighting interfaces if you want to control lighting devices only. To control all kind of devices (security, climate etc) it's better to use Interface::Specialize.
* Specify a communication type - RS232, Ethernet etc. and do not forget to specify the way to connect to the device, i.e.:
** For an Ethernet device, add the TCP Port (#69) to the device data.
* Specify that your device is controlled via category "Device Category:Core" ("Computers - Core"). Otherwise the driver will not be started on the core.

Furthermore you should add the commands implemented by your device, and the events it can generate. If possible, try to fill in the Plug & Play section to ensure that your device will be automatically detected.
Also, fill in the comment fields provide others with information about your device template.

==== Adding the device ====
If you have added Plug & Play information to your device template, a quick reload of the router, followed by the connection of your device will result in the device being detected and added automatically.

If auto-detection is not possible, however, you will have to add your device manually.
This is done on the GSD page: Wizard --> Devices --> Generic Serial Devices.

After installing the device, and a quick reload of your router you should see GSD process in the console:
<code>ps -elf|grep Generic_Serial_Device</code>

<pre>5 S root 10085 1 0 76 0 - 683 - Jul17 ? 00:00:00 SCREEN -d -m -S LinCon_8000-30 /usr/pluto/bin/Spawn_Device.sh 30 localhost Generic_Serial_Device
5 S root 10086 10085 0 75 0 - 646 wait Jul17 pts/8 00:00:00 /bin/bash /usr/pluto/bin/Spawn_Device.sh 30 localhost Generic_Serial_Device
0 S root 31800 10086 0 79 0 - 123146 295621 Jul17 pts/8 00:00:00 ./Generic_Serial_Device -d 30 -r localhost -l /var/log/pluto/30_Generic_Serial_Device.log
</pre>

This tells you that a Generic_Serial_Device driver is running. The line containing "./Generic_Serial_Device" shows you the process is running and that this instance of the driver has been given device id 30, and that the logging will be written to the file "/var/log/pluto/30_Generic_Serial_Device.log". In this log you can find all Ruby errors, connection status and other useful information.

==== Adding the Ruby code ====
From the Device Template page and from the GSD page you can edit the Ruby codes for your device. There you can write the actual code for the methods implemented by your device.

You should implement the commands you selected for your device, and you should also implement the "Ruby Internal Commands". These commands consist of the following 6 functions:
;Private Method Listing:
: This is not really a function in itself, but rather a section in your Ruby script where you may define common functions that are used in the rest of your driver. A good example would be a function to write a line to the device's log file:
<pre>
def log(line)
# This function logs a line to the log file of the device
log = File.open("/var/log/pluto/" + device_.devid_.to_s + "_Generic_Serial_Device.log", "a")
log.puts Time.now.to_s + " (Ruby script):" + line.to_s
log.close
end
</pre>

;Process IDLE: This function is executed each one - two seconds. It may be useful to check for a connection between your device and LinuxMCE, or to poll your device for updates.
:See the Proliphix NT series thermostat driver for an example of polling, where the time between polls is reduced to once every 5 minutes, instead of once every few seconds.

;Process Incoming Data: This function is called when some data comes from your device:
<pre>recv = conn_.Recv(100,500);</pre>
:recv contains now the data received from the physical device (say some switch is OFF). You can parse it to update a status of that switch in LinuxMCE:
<pre>cmd = Command.new(device_.devid_, -1001, 1, 2, 48)
cmd.params_[10] = 0
SendCommand(cmd)</pre>

;Process Receive Command For Child: if your device is a parent device for some other devices, this function is called when a command is send to one of the child devices.
:This function should therefore forward the command to it's children. For example, a GSD device that controls dimmer or switches might receive a some command like: ON, OFF or SET LEVEL for one of it's children. It should then send these commands in the desired format to the physical device:
<pre>
cmdId = cmd.id_ # Command ID: ON, OFF, SET LEVEL
cmdTo = cmd.devidto_ # Device ID in LinuxMCE
devPort = device_.childdevices_[cmdTo].devdata_[12] # 12 contains a port/channel
childType = device_.childdevices_[cmdTo].devtemplid_ # Template ID to know type of device: switch or dimmer

case cmdId
when 192 #192 is ON
command = '<your ON command format>'
when 193 #193 is OFF
command = '<your OFF command format>'
when 184 #184 is Level of dimmer
command = '<your SET LEVEL command format>'
end

conn_.Send(command)
</pre>
: In this example the command includes following parameters: cmdTo - the LinuxMCE ID of the child device - to update the status in LinuxMCE, devPort - Port Number - to know where send actual command, cmdId - command type - ON, OFF, SET LEVEL, level value for SET LEVEL. It might be good idea to push unsuccessful commands into array in the GSD device to run them once again.

:NOTE: From trial and error, I have come to the assumption that ON/OFF and SETLEVEL, internally, have seperate values. Be careful as you can have a device that is OFF with a setlevel of 100%. This results in a pretty UGLY message when to attempt the following: Use cmd[184]=100 to turn a device ON. (but don't actually send a cmd[192].. when you attempt to turn the device OFF, you'll get an ugly message in the GSD device saying that the 'CMD[193] won't be processed because it is useless'. (I'm paraphrasing.. you get the idea...) What makes this worse, is when you use an orbiter to turn a device on, it will send you a cmd[184], not a cmd[192]. You will need to watch for this and send a cmd[192] as needed.

:NOTE FOR ABOVE: I have found a way to force the command through. a bit of history first:
The reason we get the infamous 'won't be processed because it is useless' is because DCE has to deal with NON Discrete codes.
for instance: a device that has a power toggle. IF we turn it on, it turns on.
Now, if we turn it ON again, DCE thinks it's on and because it's a toggle, it won't send the command. That is why we get this message.
I dug pretty deep to find this next piece: params[120]=1
this parameter, when set inside a command, will FORCE DCERouter to send the command regardless of what it thinks the state is.
Hope this helps other GSD programmers. DDamron

;Process Initialize: This function is called when GSD device is starting. It's good point to initialize common variables. It is also a good place get the actual status of your device and notify LinuxMCE of it, since the state might have changed while the GSD driver was down.

;Process Release: This function is called when the GSD device is closing.

Note: LinuxMCE caches your Ruby code, so you should do a quick reload of your router each time when you modify your Ruby code!

=== Other Ruby code examples ===

==== Sending an event ====

To send an event to the LinuxMCE system you can use the following snippet:
<pre>
cmd = Command.new(device_.devid_, -1001, 1, 2, 25)
cmd.params_[30] = 20
SendCommand(cmd)
</pre>

This will send the command from your device (device_.devid_) to the LinuxMCE event handler (-1001), identifying it as a priority 1 message, of the event type (2).
Furthermore the event has id 25, which means it's a "Temperature Changed" event (the device template page shows the ids of the events you have added to the device).

Additional parameters of the event can be set by using the cmd.params_ mapping. The device template page has an edit button for each event that enables you to see the parameters associated with that event, including a description of its use.
In our example it shows that the parameter with index 30 is the current ambient temperature in degrees Celcius.

After the cmd object has been initialized it is send to the LinuxMCE system using the SendCommand function.

Note that the same piece of code can be used to send commands instead of events. The only changes are that the message type will be 1 (command) instead of 2 (event), and that the destination will probably differ from the event handler device -1001.

Note that the GSD framework currently does not allow you to get any return(out) parameters from commands.

== Troubleshooting ==

This section contains some tips on troubleshooting your new driver.

=== Viewing the logs ===

The best way to test the new GSD device is to edit the file /etc/pluto.conf and comment out the LogLevels filter, so the logging is verbose. You can do this by typing:

vim /etc/pluto.conf

Then move to the start of the line that starts with LogLevels, press 'i' for Insert mode in vim, type a # character, then press [ESC]:wq
The # at the start of a line means it's commented out, or ignored.

now do a reload router. You can do this from the console with: /usr/pluto/bin/MessageSend dcerouter 0 -1000 7 1

Then go to the log directory:

cd /var/log/pluto

ls

ls will list the contents of the directory: There will be a log file that starts with the device number of the gsd device. To follow it type:

tail -f [filename]

rather than typing in the full filename, you can just type the first letters (ie the device number) and press tab, which does an auto complete.

Now send commands to the device. You can do this through the web site or the console. For example, assuming your GSD device has the device id 57, you can send it an ON command (ON is command #192), you could type: /usr/pluto/bin/MessageSend dcerouter 0 57 1 192

The log will show a bunch of data. The lines that start with 40 and 41 are the serial data that is being sent to/from the device. To filter the tail so it only shows the serial data, type:

tail -f [filename] | grep '^40\|^41'

=== Getting the device to start ===
If your device will not start (anymore) as described in section [[How to add your own GSD device#Adding the device]] there can be several causes.

Check that your device is controlled by the core, as described in [[How to add your own GSD device#Create a device template]]. Otherwise the core assumes another device will start the driver.

If your Ruby code contains an error, LinuxMCE may decide to disable the device. So, check that your device is not disabled: on Wizard-->Devices-->Generic Serial Devices click on "Advanced" for your device and make sure the Disabled box is NOT ticked. If it is, untick it, save, and do a quick reload of the router.

Sometimes a quick reload of the router does not suffice. In that case you can run:
<pre>
/usr/pluto/bin/Start_LocalDevices.sh
</pre>
This should start your device. If not, the output of that script is a good place to look for further clues.

== Sharing your driver ==

Once your driver is working properly, you can share it with the rest of the LinuxMCE community.
The procedure for this is as follows:
* Do an sqlCVS update from the web-admin to ensure that your database is up-to-date (Advanced --> sqlCVS --> Update, select all sections)
** If it just returns without any reply, you're most likelly being tricked by your browser's pop-up blocker.
* Create a Trac ticked describing your device (http://svn.linuxmce.org)
* Do a check-in of your changes: Use the sqlCVS diff function (Advanced --> sqlCVS --> Diff) to determine the updates to the "dce" and "ir" sections of your database and check them in anonymously. The comment of your check-in should mention the Trac ticket number. You should only check in the items related to your device template.
* The developers will verify this and check the driver into the database

== See also ==

<ul>
<li>[[GSD Ruby Interface]]</li>
<li>[[GSD - Ruby codes ]]</li>
<li>[[Generic Serial Device]]</li>
</ul>

Installing LinuxMCE on VM via KVM on Ubuntu 10.10 Server

2011-02-15T19:33:16Z

JoakimL:

[[Category: Virtualization]]
[[Category: Documentation]]
[[Category: Tutorials]]

{{versioninfo|810Status=still testing|810UpdatedDate=9th february 20101|810UpdatedBy=JoakimL}}

This is based on daballiemo's [[http://wiki.linuxmce.org/index.php/Installing_LinuMCE_on_Virtual_Machine_via_KVM
== '''KVM: To baldly go where (almost) no man has gone before''' ==]]

<<< This is not complete yet, follow at own risk>>>

In this overview I will try to follow the installation path to get LCME 8.10 into a virtual machine on Ubuntu 10.10 which uses USB devices from the host.

Machine details first:

* Motherboard: MSI K9N Neo V3 with BIOS 2.61
* CPU: AMD AM2 4400+
* 2 Gb DDR-2 Memory
* 1 onboard GbE Nic
* 1 PCI-E GbE Nic
* 1 Hauppauge WinStick Nova T2

lspci
00:00.0 RAM memory: nVidia Corporation MCP65 Memory Controller (rev a3)
00:01.0 ISA bridge: nVidia Corporation MCP65 LPC Bridge (rev a3)
00:01.1 SMBus: nVidia Corporation MCP65 SMBus (rev a1)
00:01.2 RAM memory: nVidia Corporation MCP65 Memory Controller (rev a1)
00:02.0 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3)
00:02.1 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3)
00:07.0 Audio device: nVidia Corporation MCP65 High Definition Audio (rev a1)
00:08.0 PCI bridge: nVidia Corporation MCP65 PCI bridge (rev a1)
00:09.0 IDE interface: nVidia Corporation MCP65 IDE (rev a1)
00:0a.0 IDE interface: nVidia Corporation MCP65 SATA Controller (rev a3)
00:0b.0 PCI bridge: nVidia Corporation Device 045b (rev a1)
00:0c.0 PCI bridge: nVidia Corporation MCP65 PCI Express bridge (rev a1)
00:0d.0 PCI bridge: nVidia Corporation MCP65 PCI Express bridge (rev a1)
00:0e.0 PCI bridge: nVidia Corporation MCP65 PCI Express bridge (rev a1)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
04:00.0 VGA compatible controller: nVidia Corporation G86 [GeForce 8500 GT] (rev a1)

Step 1) Install Ubuntu 10.10 server 64 bit

Step 2) Make the system current:

sudo apt-get update
sudo apt-get upgrade

Step 3) Add some management tools:

I use webmin to give my server a fixed ip address and perform other administrative tasks.

apt-get install libnet-ssleay-perl libauthen-pam-perl libio-pty-perl
wget http://mirrors.kernel.org/ubuntu/pool/universe/libm/libmd5-perl/libmd5-perl_2.03-1_all.deb
sudo dpkg -i libmd5-perl_2.03-1_all.deb
sudo wget http://sourceforge.net/projects/webadmin/files/webmin/1.520/webmin_1.520_all.deb/download
sudo dpkg -i download
sudo apt-get install -f

I use MidNight Commander for file stuff

apt-get install mc

Step 4) Getting the right kernel and parameters

Install the required tools and packages, so open a terminal and type the following,

sudo apt-get install fakeroot kernel-wedge build-essential makedumpfile kernel-package libncurses5 libncurses5-dev

Step 7) Booting with the new kernel

Add the options to enable IOMMU in the kernel commandline

edit /etc/default/grub

new: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash amd_iommu=on,igfx_off,pass-through"
old: #GRUB_CMDLINE_LINUX_DEFAULT="quiet"

update the booting menu

update-grub

and reboot

sudo reboot

Step 8) Deinstall networkmanager

sudo apt-get remove network-manager

Step 9) Setup your network, change /etc/network/interfaces to look like this

<< this needs modification, remote console cannot be used during setup if there's no local network >>

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The first bridge interface
auto bridge_ext
iface bridge_ext inet static
address 0.0.0.0 #no external access without going through DCERouter first
netmask 255.255.255.0
broadcast 10.0.0.255
gateway 10.0.0.138
bridge_ports eth0
bridge_stp off
bridge_maxwait 5
# The second bridge interface
auto bridge_int
iface bridge_int inet static
address 192.168.80.240
netmask 255.255.255.0
broadcast 192.168.80.255
gateway 192.168.80.1
bridge_ports eth1
bridge_stp off
bridge_maxwait 5

With the above the host will use dcerouter as its way into the internet and thus the protection offered by the firewall. The host has no direct access to the 10.0.0.0 network.

Step 10) Install Linuxmce
sudo apt-get install virt-manager

Add user to administer you virtual machines to the libvirtd group
sudo adduser xxx libvirtd

Since there's no GUI on the server, run Virtual machine manager on another computer. Enable SSH connection for the manager by running this on the client:
ssh-keygen -t rsa
ssh-copy-id -i ~/.ssh/id_rsa.pub xxx@your_server

Install viewer on the client
sudo apt-get install virt-viewer

Download the LMCE ISO file with:
mkdir /home/xxx/lmce
cd /home/xxx/lmce
wget http://linuxmce.iptp.org/snapshots/LinuxMCE-8.10-23645-i386.iso^C

Start installation
sudo virt-install --connect qemu:///system --name DCErouter --ram 1024 --file /var/lib/libvirt/images/lmce810.img --cdrom /home/joakim/lmce/LinuxMCE-8.10-23645-i386.iso --os-type linux --os-variant generic24 -k sv --vnc --vncport 5901

Start a VNC viewer on you other computer:
virt-viewer -c qemu+ssh://192.168.1.78/system DCErouter

<< This is as far as I get. There's obviously a bug which makes Ubuntu 8.10 go into a 100% CPU loop, causing my CPU to become too hot.>>

Using virt-manager you can now install LinuxMCE. As we are all experts on that I will only give away my xml config file (should be enough ;-))

<domain type='kvm'>
<name>DCERouter</name>
<uuid>xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx</uuid>
<memory>2097152</memory>
<currentMemory>2097152</currentMemory>
<vcpu>2</vcpu>
<os>
<type arch='x86_64' machine='pc-0.11'>hvm</type>
<boot dev='hd'/>
</os>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/bin/kvm</emulator>
<disk type='block' device='disk'>
<source dev='/dev/sdc'/>
<target dev='hda' bus='ide'/>
</disk>
<disk type='file' device='cdrom'>
<target dev='hdc' bus='ide'/>
<readonly/>
</disk>
<interface type='bridge'>
<mac address='xx:xx:xx:xx:xx:xx'/>
<source bridge='bridge_ext'/>
</interface>
<interface type='bridge'>
<mac address='xx:xx:xx:xx:xx:xx'/>
<source bridge='bridge_int'/>
<model type='virtio'/>
</interface>
<serial type='pty'>
<target port='0'/>
</serial>
<console type='pty'>
<target port='0'/>
</console>
<input type='tablet' bus='usb'/>
<input type='mouse' bus='ps2'/>
<graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/>
<video>
<model type='cirrus' vram='9216' heads='1'/>
</video>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x03' slot='0x08' function='0x0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x03' slot='0x09' function='0x0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='yes'>
<source>
<vendor id='0x0403'/>
<product id='0xf2d0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/>
</source>
</hostdev>
</devices>
</domain>

Step 11) Enjoying building a test enviroment, inline upgrade etc.

Step 12) I chose to put my media on the host via a Samba share which will be detected as a NAS. This will simplify things when performing upgrades and test. Because I am using LVM also expansion is easy ;-)

[[Image:Lmce_kvm.png]]

'''
== Hints/Known Issues/Working Hardware ==
'''

'''AMD/ATI Hardware''' 
- NVidia Chipset 3600 with Opteron Socket F has full KVM support and works fine with LMCE 8.10. 
- ATI-driver 9.8 supports kernel 2.6.30 

'''Keyboard Layout''' 
- As you can't choose the keyboard-layout in virtual-manager, simply change the keymap in the xml-file e.g. from "en-us" to "de".

'''Networking''' 
- Step 11) is not needed if the physical network devices are configured as 'auto ethx \ iface ethx inet manual' 
- The virtual LMCE runs fine with only one NIC provided to it. The setup automatically configures a sub-NIC which works well. I would suggest to have the host provide the internet-access, so vLMCE can't mess it up at the installation.

'''PCI-Passthrough at KVM''' 
- PCI-Passthrough only works if the full PCI-device is transferred to the virtual machine. So if the PCI-Slot has sub-functions (e.g. Firewire) all of the 'functions' have to be adressed to the virtual machine with the <hostdev> section of Step 12). To look up your PCI-device-tree, use 'lspci -t'. 

(Tyan S2915-E)
[0000:00]-+-00.0
+-01.0
+-01.1
+-02.0
+-02.1
+-04.0
+-05.0
+-05.1
+-06.0-[0000:01]----04.0 (<- PCI-Slot = DVB-card)
\-04.1 (<- Firewire, either disable in Bios or ->KVM)
+-06.1
+-08.0
+-09.0
+-0d.0-[0000:02-04]--+-00.0-[0000:03]----04.0
| \-00.1-[0000:04]--
+-0f.0-[0000:05]--+-00.0
| \-00.1
+-18.0
+-18.1
+-18.2
+-18.3
\-18.4

- PCIe-devices do not have this restriction. 

- Please note that each change in the .xml-files is activated only after rebooting the libvirtd. You can do this manually by killing and restarting the process "libvirtd" or by a host reboot.

'''Problems with PVR-150 not responding'''

During usage it turned out that sometimes recordings failed having a total size of 0 B. Live TV has not worked stable at all. Checking the mythbackend logs shows that /dev/video0 was not responding as expected.
Furthermore I detected DMA errors in the log of the host.

I am now testing the commandline option iommu=on,igfx_off,pass-through, where pass-through should be able to iron out the DMA errors.

Because the behaviour was not stable I also installed the mercurial ivtv drivers (within the VM ofcourse!!!!):

sudo apt-get install mercurial
cd /usr/src
sudo hg clone http://linuxtv.org/hg/v4l-dvb
cd v4l-dvb
sudo make
sudo make install
sudo make unload
sudo make load

You will have to rebuild after a kernel change.

'''Clicking sound on Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02)'''

When passing-through my audio card I noticed hick ups in the MP3's and a message in kern.log;

hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.

edit alsa-base.conf;

vim /etc/modprobe.dalsa-base.conf

add the following line at the bottom;

options snd-hda-intel model=3stack-dig
options snd-hda-intel enable_msi=1
options snd-hda-intel single_cmd=1

and reboot (reload alsa does not seem to have the full effect)

Tip from [https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/274424 Bugs Launchpad]

Installing LinuxMCE on VM via KVM on Ubuntu 10.10 Server

2011-02-15T08:37:02Z

JoakimL:

[[Category: Virtualization]]
[[Category: Documentation]]
[[Category: Tutorials]]

{{versioninfo|810Status=still testing|810UpdatedDate=9th february 20101|810UpdatedBy=JoakimL}}

This is based on daballiemo's [[http://wiki.linuxmce.org/index.php/Installing_LinuMCE_on_Virtual_Machine_via_KVM
== '''KVM: To baldly go where (almost) no man has gone before''' ==]]

<<< This is not complete yet, follow at own risk>>>

In this overview I will try to follow the installation path to get LCME 8.10 into a virtual machine on Ubuntu 10.10 which uses USB devices from the host.

Machine details first:

* Motherboard: MSI K9N Neo V3 with BIOS 2.61
* CPU: AMD AM2 4400+
* 2 Gb DDR-2 Memory
* 1 onboard GbE Nic
* 1 PCI-E GbE Nic
* 1 Hauppauge WinStick Nova T2

lspci
00:00.0 RAM memory: nVidia Corporation MCP65 Memory Controller (rev a3)
00:01.0 ISA bridge: nVidia Corporation MCP65 LPC Bridge (rev a3)
00:01.1 SMBus: nVidia Corporation MCP65 SMBus (rev a1)
00:01.2 RAM memory: nVidia Corporation MCP65 Memory Controller (rev a1)
00:02.0 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3)
00:02.1 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3)
00:07.0 Audio device: nVidia Corporation MCP65 High Definition Audio (rev a1)
00:08.0 PCI bridge: nVidia Corporation MCP65 PCI bridge (rev a1)
00:09.0 IDE interface: nVidia Corporation MCP65 IDE (rev a1)
00:0a.0 IDE interface: nVidia Corporation MCP65 SATA Controller (rev a3)
00:0b.0 PCI bridge: nVidia Corporation Device 045b (rev a1)
00:0c.0 PCI bridge: nVidia Corporation MCP65 PCI Express bridge (rev a1)
00:0d.0 PCI bridge: nVidia Corporation MCP65 PCI Express bridge (rev a1)
00:0e.0 PCI bridge: nVidia Corporation MCP65 PCI Express bridge (rev a1)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
04:00.0 VGA compatible controller: nVidia Corporation G86 [GeForce 8500 GT] (rev a1)

Step 1) Install Ubuntu 10.10 server 64 bit

Step 2) Make the system current:

sudo apt-get update
sudo apt-get upgrade

Step 3) Add some management tools:

I use webmin to give my server a fixed ip address and perform other administrative tasks.

apt-get install libnet-ssleay-perl libauthen-pam-perl libio-pty-perl
wget http://mirrors.kernel.org/ubuntu/pool/universe/libm/libmd5-perl/libmd5-perl_2.03-1_all.deb
sudo dpkg -i libmd5-perl_2.03-1_all.deb
sudo wget http://sourceforge.net/projects/webadmin/files/webmin/1.520/webmin_1.520_all.deb/download
sudo dpkg -i download
sudo apt-get install -f

I use MidNight Commander for file stuff

apt-get install mc

Step 4) Getting the right kernel and parameters

Install the required tools and packages, so open a terminal and type the following,

sudo apt-get install fakeroot kernel-wedge build-essential makedumpfile kernel-package libncurses5 libncurses5-dev

Get the right kernel, at the time of writing 2.6.37 was the best kernel source.

wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.37.tar.bz2
tar -jxvf linux-2.6.37.tar.bz2 -C /usr/src

Go to the unpack directory

cd /usr/src/linux-2.6.37

It is a good idea to start with the same .config as the currently running kernel, so type the following,

sudo cp -vi /boot/config-`uname -r` .config

Now we are ready to customize the build and kernel options.

sudo make menuconfig

* set "Bus options (PCI etc.)" -> "Support for DMA Remapping Devices" to "*"
* set "Bus options (PCI etc.)" -> "Enable DMA Remapping Devices" to "*"
* set "Bus options (PCI etc.)" -> "PCI Stub driver" to "*"
This line broke my setup so I took it out * optional setting: set "Bus options (PCI etc.)" -> "Support for Interrupt Remapping" to "*"

Once you have finished, save and exit. It is now time to compile. However to speed up the build if you have a dual/triple/quad core processor type (one more than the number of cores you have).

export CONCURRENCY_LEVEL=3

The general rule is 1 + the number of processor cores.

Step 5) Build the new kernel.

sudo make-kpkg clean
fakeroot make-kpkg --initrd --append-to-version=-iommu kernel-image kernel-headers

You can grab a coffee, make a hot meal, have a sleep ;-)

Step 6) Install The New Kernel

After the successful kernel build, you can find two .deb packages in the /usr/src directory.
cd ..
ls -l linux*

Install them:
dpkg -i linux-image-2.6.33-custom_2.6.33-custom-10.00.Custom_amd64.deb
dpkg -i linux-headers-2.6.33-custom_2.6.33-custom-10.00.Custom_amd64.deb

Step 7) Booting with the new kernel

Add the options to enable IOMMU in the kernel commandline

edit /etc/default/grub

new: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_iommu=on,igfx_off,pass-through"
old: #GRUB_CMDLINE_LINUX_DEFAULT="quiet"

update the booting menu

update-grub

and reboot

sudo reboot

Step 8) Deinstall networkmanager

sudo apt-get remove network-manager

Step 9) Setup your network, change /etc/network/interfaces to look like this

<< this needs modification, remote console cannot be used during setup if there's no local network >>

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The first bridge interface
auto bridge_ext
iface bridge_ext inet static
address 0.0.0.0 #no external access without going through DCERouter first
netmask 255.255.255.0
broadcast 10.0.0.255
gateway 10.0.0.138
bridge_ports eth0
bridge_stp off
bridge_maxwait 5
# The second bridge interface
auto bridge_int
iface bridge_int inet static
address 192.168.80.240
netmask 255.255.255.0
broadcast 192.168.80.255
gateway 192.168.80.1
bridge_ports eth1
bridge_stp off
bridge_maxwait 5

With the above the host will use dcerouter as its way into the internet and thus the protection offered by the firewall. The host has no direct access to the 10.0.0.0 network.

Step 10) Install Linuxmce
sudo apt-get install virt-manager

Add user to administer you virtual machines to the libvirtd group
sudo adduser xxx libvirtd

Since there's no GUI on the server, run Virtual machine manager on another computer. Enable SSH connection for the manager by running this on the client:
ssh-keygen -t rsa
ssh-copy-id -i ~/.ssh/id_rsa.pub xxx@your_server

Install viewer on the client
sudo apt-get install virt-viewer

Download the LMCE ISO file with:
mkdir /home/xxx/lmce
cd /home/xxx/lmce
wget http://linuxmce.iptp.org/snapshots/LinuxMCE-8.10-23645-i386.iso^C

Start installation
sudo virt-install --connect qemu:///system --name DCErouter --ram 1024 --file /var/lib/libvirt/images/lmce810.img --cdrom /home/joakim/lmce/LinuxMCE-8.10-23645-i386.iso --os-type linux --os-variant generic24 -k sv --vnc --vncport 5901

Start a VNC viewer on you other computer:
virt-viewer -c qemu+ssh://192.168.1.78/system DCErouter

Using virt-manager you can now install LinuxMCE. As we are all experts on that I will only give away my xml config file (should be enough ;-))

<domain type='kvm'>
<name>DCERouter</name>
<uuid>xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx</uuid>
<memory>2097152</memory>
<currentMemory>2097152</currentMemory>
<vcpu>2</vcpu>
<os>
<type arch='x86_64' machine='pc-0.11'>hvm</type>
<boot dev='hd'/>
</os>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/bin/kvm</emulator>
<disk type='block' device='disk'>
<source dev='/dev/sdc'/>
<target dev='hda' bus='ide'/>
</disk>
<disk type='file' device='cdrom'>
<target dev='hdc' bus='ide'/>
<readonly/>
</disk>
<interface type='bridge'>
<mac address='xx:xx:xx:xx:xx:xx'/>
<source bridge='bridge_ext'/>
</interface>
<interface type='bridge'>
<mac address='xx:xx:xx:xx:xx:xx'/>
<source bridge='bridge_int'/>
<model type='virtio'/>
</interface>
<serial type='pty'>
<target port='0'/>
</serial>
<console type='pty'>
<target port='0'/>
</console>
<input type='tablet' bus='usb'/>
<input type='mouse' bus='ps2'/>
<graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/>
<video>
<model type='cirrus' vram='9216' heads='1'/>
</video>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x03' slot='0x08' function='0x0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x03' slot='0x09' function='0x0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='yes'>
<source>
<vendor id='0x0403'/>
<product id='0xf2d0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/>
</source>
</hostdev>
</devices>
</domain>

Step 11) Enjoying building a test enviroment, inline upgrade etc.

Step 12) I chose to put my media on the host via a Samba share which will be detected as a NAS. This will simplify things when performing upgrades and test. Because I am using LVM also expansion is easy ;-)

[[Image:Lmce_kvm.png]]

'''
== Hints/Known Issues/Working Hardware ==
'''

'''AMD/ATI Hardware''' 
- NVidia Chipset 3600 with Opteron Socket F has full KVM support and works fine with LMCE 8.10. 
- ATI-driver 9.8 supports kernel 2.6.30 

'''Keyboard Layout''' 
- As you can't choose the keyboard-layout in virtual-manager, simply change the keymap in the xml-file e.g. from "en-us" to "de".

'''Networking''' 
- Step 11) is not needed if the physical network devices are configured as 'auto ethx \ iface ethx inet manual' 
- The virtual LMCE runs fine with only one NIC provided to it. The setup automatically configures a sub-NIC which works well. I would suggest to have the host provide the internet-access, so vLMCE can't mess it up at the installation.

'''PCI-Passthrough at KVM''' 
- PCI-Passthrough only works if the full PCI-device is transferred to the virtual machine. So if the PCI-Slot has sub-functions (e.g. Firewire) all of the 'functions' have to be adressed to the virtual machine with the <hostdev> section of Step 12). To look up your PCI-device-tree, use 'lspci -t'. 

(Tyan S2915-E)
[0000:00]-+-00.0
+-01.0
+-01.1
+-02.0
+-02.1
+-04.0
+-05.0
+-05.1
+-06.0-[0000:01]----04.0 (<- PCI-Slot = DVB-card)
\-04.1 (<- Firewire, either disable in Bios or ->KVM)
+-06.1
+-08.0
+-09.0
+-0d.0-[0000:02-04]--+-00.0-[0000:03]----04.0
| \-00.1-[0000:04]--
+-0f.0-[0000:05]--+-00.0
| \-00.1
+-18.0
+-18.1
+-18.2
+-18.3
\-18.4

- PCIe-devices do not have this restriction. 

- Please note that each change in the .xml-files is activated only after rebooting the libvirtd. You can do this manually by killing and restarting the process "libvirtd" or by a host reboot.

'''Problems with PVR-150 not responding'''

During usage it turned out that sometimes recordings failed having a total size of 0 B. Live TV has not worked stable at all. Checking the mythbackend logs shows that /dev/video0 was not responding as expected.
Furthermore I detected DMA errors in the log of the host.

I am now testing the commandline option iommu=on,igfx_off,pass-through, where pass-through should be able to iron out the DMA errors.

Because the behaviour was not stable I also installed the mercurial ivtv drivers (within the VM ofcourse!!!!):

sudo apt-get install mercurial
cd /usr/src
sudo hg clone http://linuxtv.org/hg/v4l-dvb
cd v4l-dvb
sudo make
sudo make install
sudo make unload
sudo make load

You will have to rebuild after a kernel change.

'''Clicking sound on Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02)'''

When passing-through my audio card I noticed hick ups in the MP3's and a message in kern.log;

hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.

edit alsa-base.conf;

vim /etc/modprobe.dalsa-base.conf

add the following line at the bottom;

options snd-hda-intel model=3stack-dig
options snd-hda-intel enable_msi=1
options snd-hda-intel single_cmd=1

and reboot (reload alsa does not seem to have the full effect)

Tip from [https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/274424 Bugs Launchpad]

Installing LinuxMCE on VM via KVM on Ubuntu 10.10 Server

2011-02-15T07:20:10Z

JoakimL:

[[Category: Virtualization]]
[[Category: Documentation]]
[[Category: Tutorials]]

{{versioninfo|810Status=still testing|810UpdatedDate=9th february 20101|810UpdatedBy=JoakimL}}

This is based on daballiemo's [[http://wiki.linuxmce.org/index.php/Installing_LinuMCE_on_Virtual_Machine_via_KVM
== '''KVM: To baldly go where (almost) no man has gone before''' ==]]
<<< This is not complete yet, follow at own risk>>>

In this overview I will try to follow the installation path to get LCME 8.10 into a virtual machine on Ubuntu 10.10 which uses USB devices from the host.

Machine details first:

* Motherboard: MSI K9N Neo V3 with BIOS 2.61
* CPU: AMD AM2 4400+
* 2 Gb DDR-2 Memory
* 1 onboard GbE Nic
* 1 PCI-E GbE Nic
* 1 Hauppauge WinStick Nova T2

lspci
00:00.0 RAM memory: nVidia Corporation MCP65 Memory Controller (rev a3)
00:01.0 ISA bridge: nVidia Corporation MCP65 LPC Bridge (rev a3)
00:01.1 SMBus: nVidia Corporation MCP65 SMBus (rev a1)
00:01.2 RAM memory: nVidia Corporation MCP65 Memory Controller (rev a1)
00:02.0 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3)
00:02.1 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3)
00:07.0 Audio device: nVidia Corporation MCP65 High Definition Audio (rev a1)
00:08.0 PCI bridge: nVidia Corporation MCP65 PCI bridge (rev a1)
00:09.0 IDE interface: nVidia Corporation MCP65 IDE (rev a1)
00:0a.0 IDE interface: nVidia Corporation MCP65 SATA Controller (rev a3)
00:0b.0 PCI bridge: nVidia Corporation Device 045b (rev a1)
00:0c.0 PCI bridge: nVidia Corporation MCP65 PCI Express bridge (rev a1)
00:0d.0 PCI bridge: nVidia Corporation MCP65 PCI Express bridge (rev a1)
00:0e.0 PCI bridge: nVidia Corporation MCP65 PCI Express bridge (rev a1)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
04:00.0 VGA compatible controller: nVidia Corporation G86 [GeForce 8500 GT] (rev a1)

Step 1) Install Ubuntu 10.10 server 64 bit

Step 2) Make the system current:

sudo apt-get update
sudo apt-get upgrade

Step 3) Add some management tools:

I use webmin to give my server a fixed ip address and perform other administrative tasks.

apt-get install libnet-ssleay-perl libauthen-pam-perl libio-pty-perl
wget http://mirrors.kernel.org/ubuntu/pool/universe/libm/libmd5-perl/libmd5-perl_2.03-1_all.deb
sudo dpkg -i libmd5-perl_2.03-1_all.deb
sudo wget http://sourceforge.net/projects/webadmin/files/webmin/1.520/webmin_1.520_all.deb/download
sudo dpkg -i download
sudo apt-get install -f

I use MidNight Commander for file stuff

apt-get install mc

Step 4) Getting the right kernel and parameters

Install the required tools and packages, so open a terminal and type the following,

sudo apt-get install fakeroot kernel-wedge build-essential makedumpfile kernel-package libncurses5 libncurses5-dev

Get the right kernel, at the time of writing 2.6.37 was the best kernel source.

wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.37.tar.bz2
tar -jxvf linux-2.6.37.tar.bz2 -C /usr/src

Go to the unpack directory

cd /usr/src/linux-2.6.37

It is a good idea to start with the same .config as the currently running kernel, so type the following,

sudo cp -vi /boot/config-`uname -r` .config

Now we are ready to customize the build and kernel options.

sudo make menuconfig

* set "Bus options (PCI etc.)" -> "Support for DMA Remapping Devices" to "*"
* set "Bus options (PCI etc.)" -> "Enable DMA Remapping Devices" to "*"
* set "Bus options (PCI etc.)" -> "PCI Stub driver" to "*"
This line broke my setup so I took it out * optional setting: set "Bus options (PCI etc.)" -> "Support for Interrupt Remapping" to "*"

Once you have finished, save and exit. It is now time to compile. However to speed up the build if you have a dual/triple/quad core processor type (one more than the number of cores you have).

export CONCURRENCY_LEVEL=3

The general rule is 1 + the number of processor cores.

Step 5) Build the new kernel.

sudo make-kpkg clean
fakeroot make-kpkg --initrd --append-to-version=-iommu kernel-image kernel-headers

You can grab a coffee, make a hot meal, have a sleep ;-)

Step 6) Install The New Kernel

After the successful kernel build, you can find two .deb packages in the /usr/src directory.
cd ..
ls -l linux*

Install them:
dpkg -i linux-image-2.6.33-custom_2.6.33-custom-10.00.Custom_amd64.deb
dpkg -i linux-headers-2.6.33-custom_2.6.33-custom-10.00.Custom_amd64.deb

Step 7) Booting with the new kernel

Add the options to enable IOMMU in the kernel commandline

edit /etc/default/grub

new: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_iommu=on,igfx_off,pass-through"
old: #GRUB_CMDLINE_LINUX_DEFAULT="quiet"

update the booting menu

update-grub

and reboot

sudo reboot

Step 8) Deinstall networkmanager

sudo apt-get remove network-manager

Step 9) Setup your network, change /etc/network/interfaces to look like this

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The first bridge interface
auto bridge_ext
iface bridge_ext inet static
address 0.0.0.0 #no external access without going through DCERouter first
netmask 255.255.255.0
broadcast 10.0.0.255
gateway 10.0.0.138
bridge_ports eth0
bridge_stp off
bridge_maxwait 5
# The second bridge interface
auto bridge_int
iface bridge_int inet static
address 192.168.80.240
netmask 255.255.255.0
broadcast 192.168.80.255
gateway 192.168.80.1
bridge_ports eth1
bridge_stp off
bridge_maxwait 5

With the above the host will use dcerouter as its way into the internet and thus the protection offered by the firewall. The host has no direct access to the 10.0.0.0 network.

Step 10) Install Linuxmce
sudo apt-get install virt-manager

Add user to administer you virtual machines to the libvirtd group
sudo adduser xxx libvirtd

Since there's no GUI on the server, run Virtual machine manager on another computer. Enable SSH connection for the manager by running this on the client:
ssh-keygen -t rsa
ssh-copy-id -i ~/.ssh/id_rsa.pub xxx@your_server

Install viewer on the client
sudo apt-get install virt-viewer

Download the LMCE ISO file with:
mkdir /home/xxx/lmce
cd /home/xxx/lmce
wget http://linuxmce.iptp.org/snapshots/LinuxMCE-8.10-23645-i386.iso^C

Start installation
sudo virt-install --connect qemu:///system --name DCErouter --ram 1024 --file /var/lib/libvirt/images/lmce810.img --cdrom /home/joakim/lmce/LinuxMCE-8.10-23645-i386.iso --os-type linux --os-variant generic24 -k sv --vnc --vncport 5901

Start a VNC viewer on you other computer:
virt-viewer -c qemu+ssh://192.168.1.78/system DCErouter

Using virt-manager you can now install LinuxMCE. As we are all experts on that I will only give away my xml config file (should be enough ;-))

<domain type='kvm'>
<name>DCERouter</name>
<uuid>xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx</uuid>
<memory>2097152</memory>
<currentMemory>2097152</currentMemory>
<vcpu>2</vcpu>
<os>
<type arch='x86_64' machine='pc-0.11'>hvm</type>
<boot dev='hd'/>
</os>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/bin/kvm</emulator>
<disk type='block' device='disk'>
<source dev='/dev/sdc'/>
<target dev='hda' bus='ide'/>
</disk>
<disk type='file' device='cdrom'>
<target dev='hdc' bus='ide'/>
<readonly/>
</disk>
<interface type='bridge'>
<mac address='xx:xx:xx:xx:xx:xx'/>
<source bridge='bridge_ext'/>
</interface>
<interface type='bridge'>
<mac address='xx:xx:xx:xx:xx:xx'/>
<source bridge='bridge_int'/>
<model type='virtio'/>
</interface>
<serial type='pty'>
<target port='0'/>
</serial>
<console type='pty'>
<target port='0'/>
</console>
<input type='tablet' bus='usb'/>
<input type='mouse' bus='ps2'/>
<graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/>
<video>
<model type='cirrus' vram='9216' heads='1'/>
</video>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x03' slot='0x08' function='0x0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x03' slot='0x09' function='0x0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='yes'>
<source>
<vendor id='0x0403'/>
<product id='0xf2d0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/>
</source>
</hostdev>
</devices>
</domain>

Step 11) Enjoying building a test enviroment, inline upgrade etc.

Step 12) I chose to put my media on the host via a Samba share which will be detected as a NAS. This will simplify things when performing upgrades and test. Because I am using LVM also expansion is easy ;-)

[[Image:Lmce_kvm.png]]

'''
== Hints/Known Issues/Working Hardware ==
'''

'''AMD/ATI Hardware''' 
- NVidia Chipset 3600 with Opteron Socket F has full KVM support and works fine with LMCE 8.10. 
- ATI-driver 9.8 supports kernel 2.6.30 

'''Keyboard Layout''' 
- As you can't choose the keyboard-layout in virtual-manager, simply change the keymap in the xml-file e.g. from "en-us" to "de".

'''Networking''' 
- Step 11) is not needed if the physical network devices are configured as 'auto ethx \ iface ethx inet manual' 
- The virtual LMCE runs fine with only one NIC provided to it. The setup automatically configures a sub-NIC which works well. I would suggest to have the host provide the internet-access, so vLMCE can't mess it up at the installation.

'''PCI-Passthrough at KVM''' 
- PCI-Passthrough only works if the full PCI-device is transferred to the virtual machine. So if the PCI-Slot has sub-functions (e.g. Firewire) all of the 'functions' have to be adressed to the virtual machine with the <hostdev> section of Step 12). To look up your PCI-device-tree, use 'lspci -t'. 

(Tyan S2915-E)
[0000:00]-+-00.0
+-01.0
+-01.1
+-02.0
+-02.1
+-04.0
+-05.0
+-05.1
+-06.0-[0000:01]----04.0 (<- PCI-Slot = DVB-card)
\-04.1 (<- Firewire, either disable in Bios or ->KVM)
+-06.1
+-08.0
+-09.0
+-0d.0-[0000:02-04]--+-00.0-[0000:03]----04.0
| \-00.1-[0000:04]--
+-0f.0-[0000:05]--+-00.0
| \-00.1
+-18.0
+-18.1
+-18.2
+-18.3
\-18.4

- PCIe-devices do not have this restriction. 

- Please note that each change in the .xml-files is activated only after rebooting the libvirtd. You can do this manually by killing and restarting the process "libvirtd" or by a host reboot.

'''Problems with PVR-150 not responding'''

During usage it turned out that sometimes recordings failed having a total size of 0 B. Live TV has not worked stable at all. Checking the mythbackend logs shows that /dev/video0 was not responding as expected.
Furthermore I detected DMA errors in the log of the host.

I am now testing the commandline option iommu=on,igfx_off,pass-through, where pass-through should be able to iron out the DMA errors.

Because the behaviour was not stable I also installed the mercurial ivtv drivers (within the VM ofcourse!!!!):

sudo apt-get install mercurial
cd /usr/src
sudo hg clone http://linuxtv.org/hg/v4l-dvb
cd v4l-dvb
sudo make
sudo make install
sudo make unload
sudo make load

You will have to rebuild after a kernel change.

'''Clicking sound on Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02)'''

When passing-through my audio card I noticed hick ups in the MP3's and a message in kern.log;

hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.

edit alsa-base.conf;

vim /etc/modprobe.dalsa-base.conf

add the following line at the bottom;

options snd-hda-intel model=3stack-dig
options snd-hda-intel enable_msi=1
options snd-hda-intel single_cmd=1

and reboot (reload alsa does not seem to have the full effect)

Tip from [https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/274424 Bugs Launchpad]

Installing LinuxMCE on VM via KVM on Ubuntu 10.10 Server

2011-02-15T07:04:01Z

JoakimL:

[[Category: Virtualization]]
[[Category: Documentation]]
[[Category: Tutorials]]

{{versioninfo|810Status=still testing|810UpdatedDate=9th february 20101|810UpdatedBy=JoakimL}}

This is based on daballiemo's [[http://wiki.linuxmce.org/index.php/Installing_LinuMCE_on_Virtual_Machine_via_KVM
== '''KVM: To baldly go where (almost) no man has gone before''' ==]]
<<< This is not complete yet, follow at own risk>>>

In this overview I will try to follow the installation path to get LCME 8.10 into a virtual machine on Ubuntu 10.10 which uses USB devices from the host.

Machine details first:

* Motherboard: MSI K9N Neo V3 with BIOS 2.61
* CPU: AMD AM2 4400+
* 2 Gb DDR-2 Memory
* 1 onboard GbE Nic
* 1 PCI-E GbE Nic
* 1 Hauppauge WinStick Nova T2

lspci
00:00.0 RAM memory: nVidia Corporation MCP65 Memory Controller (rev a3)
00:01.0 ISA bridge: nVidia Corporation MCP65 LPC Bridge (rev a3)
00:01.1 SMBus: nVidia Corporation MCP65 SMBus (rev a1)
00:01.2 RAM memory: nVidia Corporation MCP65 Memory Controller (rev a1)
00:02.0 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3)
00:02.1 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3)
00:07.0 Audio device: nVidia Corporation MCP65 High Definition Audio (rev a1)
00:08.0 PCI bridge: nVidia Corporation MCP65 PCI bridge (rev a1)
00:09.0 IDE interface: nVidia Corporation MCP65 IDE (rev a1)
00:0a.0 IDE interface: nVidia Corporation MCP65 SATA Controller (rev a3)
00:0b.0 PCI bridge: nVidia Corporation Device 045b (rev a1)
00:0c.0 PCI bridge: nVidia Corporation MCP65 PCI Express bridge (rev a1)
00:0d.0 PCI bridge: nVidia Corporation MCP65 PCI Express bridge (rev a1)
00:0e.0 PCI bridge: nVidia Corporation MCP65 PCI Express bridge (rev a1)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
04:00.0 VGA compatible controller: nVidia Corporation G86 [GeForce 8500 GT] (rev a1)

Step 1) Install Ubuntu 10.10 server 64 bit

Step 2) Make the system current:

sudo apt-get update
sudo apt-get upgrade

Step 3) Add some management tools:

I use webmin to give my server a fixed ip address and perform other administrative tasks.

apt-get install libnet-ssleay-perl libauthen-pam-perl libio-pty-perl
wget http://mirrors.kernel.org/ubuntu/pool/universe/libm/libmd5-perl/libmd5-perl_2.03-1_all.deb
sudo dpkg -i libmd5-perl_2.03-1_all.deb
sudo wget http://sourceforge.net/projects/webadmin/files/webmin/1.520/webmin_1.520_all.deb/download
sudo dpkg -i download
sudo apt-get install -f

I use MidNight Commander for file stuff

apt-get install mc

Step 4) Getting the right kernel and parameters

Install the required tools and packages, so open a terminal and type the following,

sudo apt-get install fakeroot kernel-wedge build-essential makedumpfile kernel-package libncurses5 libncurses5-dev

Get the right kernel, at the time of writing 2.6.37 was the best kernel source.

wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.37.tar.bz2
tar -jxvf linux-2.6.37.tar.bz2 -C /usr/src

Go to the unpack directory

cd /usr/src/linux-2.6.37

It is a good idea to start with the same .config as the currently running kernel, so type the following,

sudo cp -vi /boot/config-`uname -r` .config

Now we are ready to customize the build and kernel options.

sudo make menuconfig

* set "Bus options (PCI etc.)" -> "Support for DMA Remapping Devices" to "*"
* set "Bus options (PCI etc.)" -> "Enable DMA Remapping Devices" to "*"
* set "Bus options (PCI etc.)" -> "PCI Stub driver" to "*"
This line broke my setup so I took it out * optional setting: set "Bus options (PCI etc.)" -> "Support for Interrupt Remapping" to "*"

Once you have finished, save and exit. It is now time to compile. However to speed up the build if you have a dual/triple/quad core processor type (one more than the number of cores you have).

export CONCURRENCY_LEVEL=3

The general rule is 1 + the number of processor cores.

Step 5) Build the new kernel.

sudo make-kpkg clean
fakeroot make-kpkg --initrd --append-to-version=-iommu kernel-image kernel-headers

You can grab a coffee, make a hot meal, have a sleep ;-)

Step 6) Install The New Kernel

After the successful kernel build, you can find two .deb packages in the /usr/src directory.
cd ..
ls -l linux*

Install them:
dpkg -i linux-image-2.6.33-custom_2.6.33-custom-10.00.Custom_amd64.deb
dpkg -i linux-headers-2.6.33-custom_2.6.33-custom-10.00.Custom_amd64.deb

Step 7) Booting with the new kernel

Add the options to enable IOMMU in the kernel commandline

edit /etc/default/grub

new: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_iommu=on,igfx_off,pass-through"
old: #GRUB_CMDLINE_LINUX_DEFAULT="quiet"

update the booting menu

update-grub

and reboot

sudo reboot

Step 8) Deinstall networkmanager

sudo apt-get remove network-manager

Step 9) Setup your network, change /etc/network/interfaces to look like this

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The first bridge interface
auto bridge_ext
iface bridge_ext inet static
address 0.0.0.0 #no external access without going through DCERouter first
netmask 255.255.255.0
broadcast 10.0.0.255
gateway 10.0.0.138
bridge_ports eth0
bridge_stp off
bridge_maxwait 5
# The second bridge interface
auto bridge_int
iface bridge_int inet static
address 192.168.80.240
netmask 255.255.255.0
broadcast 192.168.80.255
gateway 192.168.80.1
bridge_ports eth1
bridge_stp off
bridge_maxwait 5

With the above the host will use dcerouter as its way into the internet and thus the protection offered by the firewall. The host has no direct access to the 10.0.0.0 network.

Step 10) Install Linuxmce
sudo apt-get install virt-manager

Add user to administer you virtual machines to the libvirtd group
sudo adduser xxx libvirtd

Since there's no GUI on the server, run Virtual machine manager on another computer. Enable SSH connection for the manager by running this on the client:
ssh-keygen -t rsa
ssh-copy-id -i ~/.ssh/id_rsa.pub xxx@your_server

Install viewer on the client
sudo apt-get install virt-viewer

Download the LMCE ISO file with:
mkdir /home/xxx/lmce
cd /home/xxx/lmce
wget http://linuxmce.iptp.org/snapshots/LinuxMCE-8.10-23645-i386.iso^C

Start installation
sudo virt-install --connect qemu:///system --name DCErouter --ram 1024 --file /var/lib/libvirt/images/lmce810.img --cdrom /home/joakim/lmce/LinuxMCE-8.10-23645-i386.iso --os-type linux --os-variant generic26 -k sv --vnc --vncport 5901

Start a VNC viewer on you other computer:
virt-viewer -c qemu+ssh://192.168.1.78/system DCErouter

Using virt-manager you can now install LinuxMCE. As we are all experts on that I will only give away my xml config file (should be enough ;-))

<domain type='kvm'>
<name>DCERouter</name>
<uuid>xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx</uuid>
<memory>2097152</memory>
<currentMemory>2097152</currentMemory>
<vcpu>2</vcpu>
<os>
<type arch='x86_64' machine='pc-0.11'>hvm</type>
<boot dev='hd'/>
</os>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/bin/kvm</emulator>
<disk type='block' device='disk'>
<source dev='/dev/sdc'/>
<target dev='hda' bus='ide'/>
</disk>
<disk type='file' device='cdrom'>
<target dev='hdc' bus='ide'/>
<readonly/>
</disk>
<interface type='bridge'>
<mac address='xx:xx:xx:xx:xx:xx'/>
<source bridge='bridge_ext'/>
</interface>
<interface type='bridge'>
<mac address='xx:xx:xx:xx:xx:xx'/>
<source bridge='bridge_int'/>
<model type='virtio'/>
</interface>
<serial type='pty'>
<target port='0'/>
</serial>
<console type='pty'>
<target port='0'/>
</console>
<input type='tablet' bus='usb'/>
<input type='mouse' bus='ps2'/>
<graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/>
<video>
<model type='cirrus' vram='9216' heads='1'/>
</video>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x03' slot='0x08' function='0x0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x03' slot='0x09' function='0x0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='yes'>
<source>
<vendor id='0x0403'/>
<product id='0xf2d0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/>
</source>
</hostdev>
</devices>
</domain>

Step 11) Enjoying building a test enviroment, inline upgrade etc.

Step 12) I chose to put my media on the host via a Samba share which will be detected as a NAS. This will simplify things when performing upgrades and test. Because I am using LVM also expansion is easy ;-)

[[Image:Lmce_kvm.png]]

'''
== Hints/Known Issues/Working Hardware ==
'''

'''AMD/ATI Hardware''' 
- NVidia Chipset 3600 with Opteron Socket F has full KVM support and works fine with LMCE 8.10. 
- ATI-driver 9.8 supports kernel 2.6.30 

'''Keyboard Layout''' 
- As you can't choose the keyboard-layout in virtual-manager, simply change the keymap in the xml-file e.g. from "en-us" to "de".

'''Networking''' 
- Step 11) is not needed if the physical network devices are configured as 'auto ethx \ iface ethx inet manual' 
- The virtual LMCE runs fine with only one NIC provided to it. The setup automatically configures a sub-NIC which works well. I would suggest to have the host provide the internet-access, so vLMCE can't mess it up at the installation.

'''PCI-Passthrough at KVM''' 
- PCI-Passthrough only works if the full PCI-device is transferred to the virtual machine. So if the PCI-Slot has sub-functions (e.g. Firewire) all of the 'functions' have to be adressed to the virtual machine with the <hostdev> section of Step 12). To look up your PCI-device-tree, use 'lspci -t'. 

(Tyan S2915-E)
[0000:00]-+-00.0
+-01.0
+-01.1
+-02.0
+-02.1
+-04.0
+-05.0
+-05.1
+-06.0-[0000:01]----04.0 (<- PCI-Slot = DVB-card)
\-04.1 (<- Firewire, either disable in Bios or ->KVM)
+-06.1
+-08.0
+-09.0
+-0d.0-[0000:02-04]--+-00.0-[0000:03]----04.0
| \-00.1-[0000:04]--
+-0f.0-[0000:05]--+-00.0
| \-00.1
+-18.0
+-18.1
+-18.2
+-18.3
\-18.4

- PCIe-devices do not have this restriction. 

- Please note that each change in the .xml-files is activated only after rebooting the libvirtd. You can do this manually by killing and restarting the process "libvirtd" or by a host reboot.

'''Problems with PVR-150 not responding'''

During usage it turned out that sometimes recordings failed having a total size of 0 B. Live TV has not worked stable at all. Checking the mythbackend logs shows that /dev/video0 was not responding as expected.
Furthermore I detected DMA errors in the log of the host.

I am now testing the commandline option iommu=on,igfx_off,pass-through, where pass-through should be able to iron out the DMA errors.

Because the behaviour was not stable I also installed the mercurial ivtv drivers (within the VM ofcourse!!!!):

sudo apt-get install mercurial
cd /usr/src
sudo hg clone http://linuxtv.org/hg/v4l-dvb
cd v4l-dvb
sudo make
sudo make install
sudo make unload
sudo make load

You will have to rebuild after a kernel change.

'''Clicking sound on Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02)'''

When passing-through my audio card I noticed hick ups in the MP3's and a message in kern.log;

hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.

edit alsa-base.conf;

vim /etc/modprobe.dalsa-base.conf

add the following line at the bottom;

options snd-hda-intel model=3stack-dig
options snd-hda-intel enable_msi=1
options snd-hda-intel single_cmd=1

and reboot (reload alsa does not seem to have the full effect)

Tip from [https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/274424 Bugs Launchpad]

Installing LinuxMCE on VM via KVM on Ubuntu 10.10 Server

2011-02-14T21:43:27Z

JoakimL:

[[Category: Virtualization]]
[[Category: Documentation]]
[[Category: Tutorials]]

{{versioninfo|810Status=still testing|810UpdatedDate=9th february 20101|810UpdatedBy=JoakimL}}

This is based on daballiemo's [[http://wiki.linuxmce.org/index.php/Installing_LinuMCE_on_Virtual_Machine_via_KVM
== '''KVM: To baldly go where (almost) no man has gone before''' ==]]
<<< This is not complete yet, follow at own risk>>>

In this overview I will try to follow the installation path to get LCME 8.10 into a virtual machine on Ubuntu 10.10 which uses USB devices from the host.

Machine details first:

* Motherboard: ASUS P5E VM DO with bios 10.1
* CPU: AMD AM2 4400+
* 2 Gb DDR-2 Memory
* 1 onboard GbE Nic
* 1 PCI-E GbE Nic
* 1 Hauppauge WinStick Nova T2

lspci
00:00.0 RAM memory: nVidia Corporation MCP65 Memory Controller (rev a3)
00:01.0 ISA bridge: nVidia Corporation MCP65 LPC Bridge (rev a3)
00:01.1 SMBus: nVidia Corporation MCP65 SMBus (rev a1)
00:01.2 RAM memory: nVidia Corporation MCP65 Memory Controller (rev a1)
00:02.0 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3)
00:02.1 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3)
00:07.0 Audio device: nVidia Corporation MCP65 High Definition Audio (rev a1)
00:08.0 PCI bridge: nVidia Corporation MCP65 PCI bridge (rev a1)
00:09.0 IDE interface: nVidia Corporation MCP65 IDE (rev a1)
00:0a.0 IDE interface: nVidia Corporation MCP65 SATA Controller (rev a3)
00:0b.0 PCI bridge: nVidia Corporation Device 045b (rev a1)
00:0c.0 PCI bridge: nVidia Corporation MCP65 PCI Express bridge (rev a1)
00:0d.0 PCI bridge: nVidia Corporation MCP65 PCI Express bridge (rev a1)
00:0e.0 PCI bridge: nVidia Corporation MCP65 PCI Express bridge (rev a1)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
04:00.0 VGA compatible controller: nVidia Corporation G86 [GeForce 8500 GT] (rev a1)

Step 1) Install Ubuntu 10.10 server 64 bit

Step 2) Make the system current:

sudo apt-get update
sudo apt-get upgrade

Step 3) Add some management tools:

I use webmin to give my server a fixed ip address and perform other administrative tasks.

apt-get install libnet-ssleay-perl libauthen-pam-perl libio-pty-perl
wget http://mirrors.kernel.org/ubuntu/pool/universe/libm/libmd5-perl/libmd5-perl_2.03-1_all.deb
sudo dpkg -i libmd5-perl_2.03-1_all.deb
sudo wget http://sourceforge.net/projects/webadmin/files/webmin/1.520/webmin_1.520_all.deb/download
sudo dpkg -i download
sudo apt-get install -f

I use MidNight Commander for file stuff

apt-get install mc

Step 4) Getting the right kernel and parameters

Install the required tools and packages, so open a terminal and type the following,

sudo apt-get install fakeroot kernel-wedge build-essential makedumpfile kernel-package libncurses5 libncurses5-dev

Get the right kernel, at the time of writing 2.6.37 was the best kernel source.

wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.37.tar.bz2
tar -jxvf linux-2.6.37.tar.bz2 -C /usr/src

Go to the unpack directory

cd /usr/src/linux-2.6.37

It is a good idea to start with the same .config as the currently running kernel, so type the following,

sudo cp -vi /boot/config-`uname -r` .config

Now we are ready to customize the build and kernel options.

sudo make menuconfig

* set "Bus options (PCI etc.)" -> "Support for DMA Remapping Devices" to "*"
* set "Bus options (PCI etc.)" -> "Enable DMA Remapping Devices" to "*"
* set "Bus options (PCI etc.)" -> "PCI Stub driver" to "*"
This line broke my setup so I took it out * optional setting: set "Bus options (PCI etc.)" -> "Support for Interrupt Remapping" to "*"

Once you have finished, save and exit. It is now time to compile. However to speed up the build if you have a dual/triple/quad core processor type (one more than the number of cores you have).

export CONCURRENCY_LEVEL=3

The general rule is 1 + the number of processor cores.

Step 5) Build the new kernel.

sudo make-kpkg clean
fakeroot make-kpkg --initrd --append-to-version=-iommu kernel-image kernel-headers

You can grab a coffee, make a hot meal, have a sleep ;-)

Step 6) Install The New Kernel

After the successful kernel build, you can find two .deb packages in the /usr/src directory.
cd ..
ls -l linux*

Install them:
dpkg -i linux-image-2.6.33-custom_2.6.33-custom-10.00.Custom_amd64.deb
dpkg -i linux-headers-2.6.33-custom_2.6.33-custom-10.00.Custom_amd64.deb

Step 7) Booting with the new kernel

Add the options to enable IOMMU in the kernel commandline

edit /etc/default/grub

new: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_iommu=on,igfx_off,pass-through"
old: #GRUB_CMDLINE_LINUX_DEFAULT="quiet"

update the booting menu

update-grub

and reboot

sudo reboot

Step 8) Deinstall networkmanager

sudo apt-get remove network-manager

Step 9) Setup your network, change /etc/network/interfaces to look like this

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The first bridge interface
auto bridge_ext
iface bridge_ext inet static
address 0.0.0.0 #no external access without going through DCERouter first
netmask 255.255.255.0
broadcast 10.0.0.255
gateway 10.0.0.138
bridge_ports eth0
bridge_stp off
bridge_maxwait 5
# The second bridge interface
auto bridge_int
iface bridge_int inet static
address 192.168.80.240
netmask 255.255.255.0
broadcast 192.168.80.255
gateway 192.168.80.1
bridge_ports eth1
bridge_stp off
bridge_maxwait 5

With the above the host will use dcerouter as its way into the internet and thus the protection offered by the firewall. The host has no direct access to the 10.0.0.0 network.

Step 10) Install Linuxmce
sudo apt-get install virt-manager

Add user to administer you virtual machines to the libvirtd group
sudo adduser xxx libvirtd

Since there's no GUI on the server, run Virtual machine manager on another computer. Enable SSH connection for the manager by running this on the client:
ssh-keygen -t rsa
ssh-copy-id -i ~/.ssh/id_rsa.pub xxx@your_server

Install viewer on the client
sudo apt-get install virt-viewer

Download the LMCE ISO file with:
mkdir /home/xxx/lmce
cd /home/xxx/lmce
wget http://linuxmce.iptp.org/snapshots/LinuxMCE-8.10-23645-i386.iso^C

Start installation
sudo virt-install --connect qemu:///system --name DCErouter --ram 1024 --file /var/lib/libvirt/images/lmce810.img --cdrom /home/joakim/lmce/LinuxMCE-8.10-23645-i386.iso --os-type linux --os-variant generic26 -k sv --vnc --vncport 5901

Start a VNC viewer on you other computer:
virt-viewer -c qemu+ssh://192.168.1.78/system DCErouter

Using virt-manager you can now install LinuxMCE. As we are all experts on that I will only give away my xml config file (should be enough ;-))

<domain type='kvm'>
<name>DCERouter</name>
<uuid>xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx</uuid>
<memory>2097152</memory>
<currentMemory>2097152</currentMemory>
<vcpu>2</vcpu>
<os>
<type arch='x86_64' machine='pc-0.11'>hvm</type>
<boot dev='hd'/>
</os>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/bin/kvm</emulator>
<disk type='block' device='disk'>
<source dev='/dev/sdc'/>
<target dev='hda' bus='ide'/>
</disk>
<disk type='file' device='cdrom'>
<target dev='hdc' bus='ide'/>
<readonly/>
</disk>
<interface type='bridge'>
<mac address='xx:xx:xx:xx:xx:xx'/>
<source bridge='bridge_ext'/>
</interface>
<interface type='bridge'>
<mac address='xx:xx:xx:xx:xx:xx'/>
<source bridge='bridge_int'/>
<model type='virtio'/>
</interface>
<serial type='pty'>
<target port='0'/>
</serial>
<console type='pty'>
<target port='0'/>
</console>
<input type='tablet' bus='usb'/>
<input type='mouse' bus='ps2'/>
<graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/>
<video>
<model type='cirrus' vram='9216' heads='1'/>
</video>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x03' slot='0x08' function='0x0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x03' slot='0x09' function='0x0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='yes'>
<source>
<vendor id='0x0403'/>
<product id='0xf2d0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/>
</source>
</hostdev>
</devices>
</domain>

Step 11) Enjoying building a test enviroment, inline upgrade etc.

Step 12) I chose to put my media on the host via a Samba share which will be detected as a NAS. This will simplify things when performing upgrades and test. Because I am using LVM also expansion is easy ;-)

[[Image:Lmce_kvm.png]]

'''
== Hints/Known Issues/Working Hardware ==
'''

'''AMD/ATI Hardware''' 
- NVidia Chipset 3600 with Opteron Socket F has full KVM support and works fine with LMCE 8.10. 
- ATI-driver 9.8 supports kernel 2.6.30 

'''Keyboard Layout''' 
- As you can't choose the keyboard-layout in virtual-manager, simply change the keymap in the xml-file e.g. from "en-us" to "de".

'''Networking''' 
- Step 11) is not needed if the physical network devices are configured as 'auto ethx \ iface ethx inet manual' 
- The virtual LMCE runs fine with only one NIC provided to it. The setup automatically configures a sub-NIC which works well. I would suggest to have the host provide the internet-access, so vLMCE can't mess it up at the installation.

'''PCI-Passthrough at KVM''' 
- PCI-Passthrough only works if the full PCI-device is transferred to the virtual machine. So if the PCI-Slot has sub-functions (e.g. Firewire) all of the 'functions' have to be adressed to the virtual machine with the <hostdev> section of Step 12). To look up your PCI-device-tree, use 'lspci -t'. 

(Tyan S2915-E)
[0000:00]-+-00.0
+-01.0
+-01.1
+-02.0
+-02.1
+-04.0
+-05.0
+-05.1
+-06.0-[0000:01]----04.0 (<- PCI-Slot = DVB-card)
\-04.1 (<- Firewire, either disable in Bios or ->KVM)
+-06.1
+-08.0
+-09.0
+-0d.0-[0000:02-04]--+-00.0-[0000:03]----04.0
| \-00.1-[0000:04]--
+-0f.0-[0000:05]--+-00.0
| \-00.1
+-18.0
+-18.1
+-18.2
+-18.3
\-18.4

- PCIe-devices do not have this restriction. 

- Please note that each change in the .xml-files is activated only after rebooting the libvirtd. You can do this manually by killing and restarting the process "libvirtd" or by a host reboot.

'''Problems with PVR-150 not responding'''

During usage it turned out that sometimes recordings failed having a total size of 0 B. Live TV has not worked stable at all. Checking the mythbackend logs shows that /dev/video0 was not responding as expected.
Furthermore I detected DMA errors in the log of the host.

I am now testing the commandline option iommu=on,igfx_off,pass-through, where pass-through should be able to iron out the DMA errors.

Because the behaviour was not stable I also installed the mercurial ivtv drivers (within the VM ofcourse!!!!):

sudo apt-get install mercurial
cd /usr/src
sudo hg clone http://linuxtv.org/hg/v4l-dvb
cd v4l-dvb
sudo make
sudo make install
sudo make unload
sudo make load

You will have to rebuild after a kernel change.

'''Clicking sound on Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02)'''

When passing-through my audio card I noticed hick ups in the MP3's and a message in kern.log;

hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.

edit alsa-base.conf;

vim /etc/modprobe.dalsa-base.conf

add the following line at the bottom;

options snd-hda-intel model=3stack-dig
options snd-hda-intel enable_msi=1
options snd-hda-intel single_cmd=1

and reboot (reload alsa does not seem to have the full effect)

Tip from [https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/274424 Bugs Launchpad]

Installing LinuxMCE on VM via KVM on Ubuntu 10.10 Server

2011-02-14T20:28:45Z

JoakimL:

[[Category: Virtualization]]
[[Category: Documentation]]
[[Category: Tutorials]]

{{versioninfo|810Status=still testing|810UpdatedDate=9th february 20101|810UpdatedBy=JoakimL}}

This is based on daballiemo's [[http://wiki.linuxmce.org/index.php/Installing_LinuMCE_on_Virtual_Machine_via_KVM
== '''KVM: To baldly go where (almost) no man has gone before''' ==]]
<<< This is not complete yet, follow at own risk>>>

In this overview I will try to follow the installation path to get LCME 8.10 into a virtual machine on Ubuntu 10.10 which uses USB devices from the host.

Machine details first:

* Motherboard: ASUS P5E VM DO with bios 10.1
* CPU: AMD AM2 4400+
* 2 Gb DDR-2 Memory
* 1 onboard GbE Nic
* 1 PCI-E GbE Nic
* 1 Hauppauge WinStick Nova T2

lspci
00:00.0 RAM memory: nVidia Corporation MCP65 Memory Controller (rev a3)
00:01.0 ISA bridge: nVidia Corporation MCP65 LPC Bridge (rev a3)
00:01.1 SMBus: nVidia Corporation MCP65 SMBus (rev a1)
00:01.2 RAM memory: nVidia Corporation MCP65 Memory Controller (rev a1)
00:02.0 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3)
00:02.1 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3)
00:07.0 Audio device: nVidia Corporation MCP65 High Definition Audio (rev a1)
00:08.0 PCI bridge: nVidia Corporation MCP65 PCI bridge (rev a1)
00:09.0 IDE interface: nVidia Corporation MCP65 IDE (rev a1)
00:0a.0 IDE interface: nVidia Corporation MCP65 SATA Controller (rev a3)
00:0b.0 PCI bridge: nVidia Corporation Device 045b (rev a1)
00:0c.0 PCI bridge: nVidia Corporation MCP65 PCI Express bridge (rev a1)
00:0d.0 PCI bridge: nVidia Corporation MCP65 PCI Express bridge (rev a1)
00:0e.0 PCI bridge: nVidia Corporation MCP65 PCI Express bridge (rev a1)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
04:00.0 VGA compatible controller: nVidia Corporation G86 [GeForce 8500 GT] (rev a1)

Step 1) Install Ubuntu 10.10 server 64 bit

Step 2) Make the system current:

sudo apt-get update
sudo apt-get upgrade

Step 3) Add some management tools:

I use webmin to give my server a fixed ip address and perform other administrative tasks.

apt-get install libnet-ssleay-perl libauthen-pam-perl libio-pty-perl
wget http://mirrors.kernel.org/ubuntu/pool/universe/libm/libmd5-perl/libmd5-perl_2.03-1_all.deb
sudo dpkg -i libmd5-perl_2.03-1_all.deb
sudo wget http://sourceforge.net/projects/webadmin/files/webmin/1.520/webmin_1.520_all.deb/download
sudo dpkg -i download
sudo apt-get install -f

I use MidNight Commander for file stuff

apt-get install mc

Step 4) Getting the right kernel and parameters

Install the required tools and packages, so open a terminal and type the following,

sudo apt-get install fakeroot kernel-wedge build-essential makedumpfile kernel-package libncurses5 libncurses5-dev

Get the right kernel, at the time of writing 2.6.37 was the best kernel source.

wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.37.tar.bz2
tar -jxvf linux-2.6.37.tar.bz2 -C /usr/src

Go to the unpack directory

cd /usr/src/linux-2.6.37

It is a good idea to start with the same .config as the currently running kernel, so type the following,

sudo cp -vi /boot/config-`uname -r` .config

Now we are ready to customize the build and kernel options.

sudo make menuconfig

* set "Bus options (PCI etc.)" -> "Support for DMA Remapping Devices" to "*"
* set "Bus options (PCI etc.)" -> "Enable DMA Remapping Devices" to "*"
* set "Bus options (PCI etc.)" -> "PCI Stub driver" to "*"
This line broke my setup so I took it out * optional setting: set "Bus options (PCI etc.)" -> "Support for Interrupt Remapping" to "*"

Once you have finished, save and exit. It is now time to compile. However to speed up the build if you have a dual/triple/quad core processor type (one more than the number of cores you have).

export CONCURRENCY_LEVEL=3

The general rule is 1 + the number of processor cores.

Step 5) Build the new kernel.

sudo make-kpkg clean
fakeroot make-kpkg --initrd --append-to-version=-iommu kernel-image kernel-headers

You can grab a coffee, make a hot meal, have a sleep ;-)

Step 6) Install The New Kernel

After the successful kernel build, you can find two .deb packages in the /usr/src directory.
cd ..
ls -l linux*

Install them:
dpkg -i linux-image-2.6.33-custom_2.6.33-custom-10.00.Custom_amd64.deb
dpkg -i linux-headers-2.6.33-custom_2.6.33-custom-10.00.Custom_amd64.deb

Step 7) Booting with the new kernel

Add the options to enable IOMMU in the kernel commandline

edit /etc/default/grub

new: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_iommu=on,igfx_off,pass-through"
old: #GRUB_CMDLINE_LINUX_DEFAULT="quiet"

update the booting menu

update-grub

and reboot

sudo reboot

Step 8) Deinstall networkmanager

sudo apt-get remove network-manager

Step 9) Setup your network, change /etc/network/interfaces to look like this

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The first bridge interface
auto bridge_ext
iface bridge_ext inet static
address 0.0.0.0 #no external access without going through DCERouter first
netmask 255.255.255.0
broadcast 10.0.0.255
gateway 10.0.0.138
bridge_ports eth0
bridge_stp off
bridge_maxwait 5
# The second bridge interface
auto bridge_int
iface bridge_int inet static
address 192.168.80.240
netmask 255.255.255.0
broadcast 192.168.80.255
gateway 192.168.80.1
bridge_ports eth1
bridge_stp off
bridge_maxwait 5

With the above the host will use dcerouter as its way into the internet and thus the protection offered by the firewall. The host has no direct access to the 10.0.0.0 network.

Step 10) Install Linuxmce
sudo apt-get install virt-manager

Add user to administer you virtual machines to the libvirtd group
sudo adduser xxx libvirtd

Since there's no GUI on the server, run Virtual machine manager on another computer. Enable SSH connection for the manager by running this on the client:
ssh-keygen -t rsa
ssh-copy-id -i ~/.ssh/id_rsa.pub xxx@your_server

Using virt-manager you can now install LinuxMCE. As we are all experts on that I will only give away my xml config file (should be enough ;-))

<domain type='kvm'>
<name>DCERouter</name>
<uuid>xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx</uuid>
<memory>2097152</memory>
<currentMemory>2097152</currentMemory>
<vcpu>2</vcpu>
<os>
<type arch='x86_64' machine='pc-0.11'>hvm</type>
<boot dev='hd'/>
</os>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/bin/kvm</emulator>
<disk type='block' device='disk'>
<source dev='/dev/sdc'/>
<target dev='hda' bus='ide'/>
</disk>
<disk type='file' device='cdrom'>
<target dev='hdc' bus='ide'/>
<readonly/>
</disk>
<interface type='bridge'>
<mac address='xx:xx:xx:xx:xx:xx'/>
<source bridge='bridge_ext'/>
</interface>
<interface type='bridge'>
<mac address='xx:xx:xx:xx:xx:xx'/>
<source bridge='bridge_int'/>
<model type='virtio'/>
</interface>
<serial type='pty'>
<target port='0'/>
</serial>
<console type='pty'>
<target port='0'/>
</console>
<input type='tablet' bus='usb'/>
<input type='mouse' bus='ps2'/>
<graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/>
<video>
<model type='cirrus' vram='9216' heads='1'/>
</video>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x03' slot='0x08' function='0x0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x03' slot='0x09' function='0x0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='yes'>
<source>
<vendor id='0x0403'/>
<product id='0xf2d0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/>
</source>
</hostdev>
</devices>
</domain>

Step 11) Enjoying building a test enviroment, inline upgrade etc.

Step 12) I chose to put my media on the host via a Samba share which will be detected as a NAS. This will simplify things when performing upgrades and test. Because I am using LVM also expansion is easy ;-)

[[Image:Lmce_kvm.png]]

'''
== Hints/Known Issues/Working Hardware ==
'''

'''AMD/ATI Hardware''' 
- NVidia Chipset 3600 with Opteron Socket F has full KVM support and works fine with LMCE 8.10. 
- ATI-driver 9.8 supports kernel 2.6.30 

'''Keyboard Layout''' 
- As you can't choose the keyboard-layout in virtual-manager, simply change the keymap in the xml-file e.g. from "en-us" to "de".

'''Networking''' 
- Step 11) is not needed if the physical network devices are configured as 'auto ethx \ iface ethx inet manual' 
- The virtual LMCE runs fine with only one NIC provided to it. The setup automatically configures a sub-NIC which works well. I would suggest to have the host provide the internet-access, so vLMCE can't mess it up at the installation.

'''PCI-Passthrough at KVM''' 
- PCI-Passthrough only works if the full PCI-device is transferred to the virtual machine. So if the PCI-Slot has sub-functions (e.g. Firewire) all of the 'functions' have to be adressed to the virtual machine with the <hostdev> section of Step 12). To look up your PCI-device-tree, use 'lspci -t'. 

(Tyan S2915-E)
[0000:00]-+-00.0
+-01.0
+-01.1
+-02.0
+-02.1
+-04.0
+-05.0
+-05.1
+-06.0-[0000:01]----04.0 (<- PCI-Slot = DVB-card)
\-04.1 (<- Firewire, either disable in Bios or ->KVM)
+-06.1
+-08.0
+-09.0
+-0d.0-[0000:02-04]--+-00.0-[0000:03]----04.0
| \-00.1-[0000:04]--
+-0f.0-[0000:05]--+-00.0
| \-00.1
+-18.0
+-18.1
+-18.2
+-18.3
\-18.4

- PCIe-devices do not have this restriction. 

- Please note that each change in the .xml-files is activated only after rebooting the libvirtd. You can do this manually by killing and restarting the process "libvirtd" or by a host reboot.

'''Problems with PVR-150 not responding'''

During usage it turned out that sometimes recordings failed having a total size of 0 B. Live TV has not worked stable at all. Checking the mythbackend logs shows that /dev/video0 was not responding as expected.
Furthermore I detected DMA errors in the log of the host.

I am now testing the commandline option iommu=on,igfx_off,pass-through, where pass-through should be able to iron out the DMA errors.

Because the behaviour was not stable I also installed the mercurial ivtv drivers (within the VM ofcourse!!!!):

sudo apt-get install mercurial
cd /usr/src
sudo hg clone http://linuxtv.org/hg/v4l-dvb
cd v4l-dvb
sudo make
sudo make install
sudo make unload
sudo make load

You will have to rebuild after a kernel change.

'''Clicking sound on Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02)'''

When passing-through my audio card I noticed hick ups in the MP3's and a message in kern.log;

hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.

edit alsa-base.conf;

vim /etc/modprobe.dalsa-base.conf

add the following line at the bottom;

options snd-hda-intel model=3stack-dig
options snd-hda-intel enable_msi=1
options snd-hda-intel single_cmd=1

and reboot (reload alsa does not seem to have the full effect)

Tip from [https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/274424 Bugs Launchpad]

Installing LinuxMCE on VM via KVM on Ubuntu 10.10 Server

2011-02-14T18:27:59Z

JoakimL:

[[Category: Virtualization]]
[[Category: Documentation]]
[[Category: Tutorials]]

{{versioninfo|810Status=still testing|810UpdatedDate=9th february 20101|810UpdatedBy=JoakimL}}

This is based on daballiemo's [[http://wiki.linuxmce.org/index.php/Installing_LinuMCE_on_Virtual_Machine_via_KVM
== '''KVM: To baldly go where (almost) no man has gone before''' ==]]
<<< This is not complete yet, follow at own risk>>>

In this overview I will try to follow the installation path to get LCME 8.10 into a virtual machine on Ubuntu 10.10 which uses USB devices from the host.

Machine details first:

* Motherboard: ASUS P5E VM DO with bios 10.1
* CPU: AMD AM2 4400+
* 2 Gb DDR-2 Memory
* 1 onboard GbE Nic
* 1 PCI-E GbE Nic
* 1 Hauppauge WinStick Nova T2

lspci
00:00.0 RAM memory: nVidia Corporation MCP65 Memory Controller (rev a3)
00:01.0 ISA bridge: nVidia Corporation MCP65 LPC Bridge (rev a3)
00:01.1 SMBus: nVidia Corporation MCP65 SMBus (rev a1)
00:01.2 RAM memory: nVidia Corporation MCP65 Memory Controller (rev a1)
00:02.0 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3)
00:02.1 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3)
00:07.0 Audio device: nVidia Corporation MCP65 High Definition Audio (rev a1)
00:08.0 PCI bridge: nVidia Corporation MCP65 PCI bridge (rev a1)
00:09.0 IDE interface: nVidia Corporation MCP65 IDE (rev a1)
00:0a.0 IDE interface: nVidia Corporation MCP65 SATA Controller (rev a3)
00:0b.0 PCI bridge: nVidia Corporation Device 045b (rev a1)
00:0c.0 PCI bridge: nVidia Corporation MCP65 PCI Express bridge (rev a1)
00:0d.0 PCI bridge: nVidia Corporation MCP65 PCI Express bridge (rev a1)
00:0e.0 PCI bridge: nVidia Corporation MCP65 PCI Express bridge (rev a1)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
04:00.0 VGA compatible controller: nVidia Corporation G86 [GeForce 8500 GT] (rev a1)

Step 1) Install Ubuntu 10.10 server 64 bit

Step 2) Make the system current:

sudo apt-get update
sudo apt-get upgrade

Step 3) Add some management tools:

I use webmin to give my server a fixed ip address and perform other administrative tasks.

apt-get install libnet-ssleay-perl libauthen-pam-perl libio-pty-perl
wget http://mirrors.kernel.org/ubuntu/pool/universe/libm/libmd5-perl/libmd5-perl_2.03-1_all.deb
sudo dpkg -i libmd5-perl_2.03-1_all.deb
sudo wget http://sourceforge.net/projects/webadmin/files/webmin/1.520/webmin_1.520_all.deb/download
sudo dpkg -i download
sudo apt-get install -f

I use MidNight Commander for file stuff

apt-get install mc

Step 4) Getting the right kernel and parameters

Install the required tools and packages, so open a terminal and type the following,

sudo apt-get install fakeroot kernel-wedge build-essential makedumpfile kernel-package libncurses5 libncurses5-dev

Get the right kernel, at the time of writing 2.6.37 was the best kernel source.

wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.37.tar.bz2
tar -jxvf linux-2.6.37.tar.bz2 -C /usr/src

Go to the unpack directory

cd /usr/src/linux-2.6.37

It is a good idea to start with the same .config as the currently running kernel, so type the following,

sudo cp -vi /boot/config-`uname -r` .config

Now we are ready to customize the build and kernel options.

sudo make menuconfig

* set "Bus options (PCI etc.)" -> "Support for DMA Remapping Devices" to "*"
* set "Bus options (PCI etc.)" -> "Enable DMA Remapping Devices" to "*"
* set "Bus options (PCI etc.)" -> "PCI Stub driver" to "*"
This line broke my setup so I took it out * optional setting: set "Bus options (PCI etc.)" -> "Support for Interrupt Remapping" to "*"

Once you have finished, save and exit. It is now time to compile. However to speed up the build if you have a dual/triple/quad core processor type (one more than the number of cores you have).

export CONCURRENCY_LEVEL=3

The general rule is 1 + the number of processor cores.

Step 5) Build the new kernel.

sudo make-kpkg clean
fakeroot make-kpkg --initrd --append-to-version=-iommu kernel-image kernel-headers

You can grab a coffee, make a hot meal, have a sleep ;-)

Step 6) Install The New Kernel

After the successful kernel build, you can find two .deb packages in the /usr/src directory.
cd ..
ls -l linux*

Install them:
dpkg -i linux-image-2.6.33-custom_2.6.33-custom-10.00.Custom_amd64.deb
dpkg -i linux-headers-2.6.33-custom_2.6.33-custom-10.00.Custom_amd64.deb

Step 7) Booting with the new kernel

Add the options to enable IOMMU in the kernel commandline

edit /etc/default/grub

new: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_iommu=on,igfx_off,pass-through"
old: #GRUB_CMDLINE_LINUX_DEFAULT="quiet"

update the booting menu

update-grub

and reboot

sudo reboot

Step 8) Deinstall networkmanager

sudo apt-get remove network-manager

Step 9) Setup your network, change /etc/network/interfaces to look like this

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The first bridge interface
auto bridge_ext
iface bridge_ext inet static
address 0.0.0.0 #no external access without going through DCERouter first
netmask 255.255.255.0
broadcast 10.0.0.255
gateway 10.0.0.138
bridge_ports eth0
bridge_stp off
bridge_maxwait 5
# The second bridge interface
auto bridge_int
iface bridge_int inet static
address 192.168.80.240
netmask 255.255.255.0
broadcast 192.168.80.255
gateway 192.168.80.1
bridge_ports eth1
bridge_stp off
bridge_maxwait 5

With the above the host will use dcerouter as its way into the internet and thus the protection offered by the firewall. The host has no direct access to the 10.0.0.0 network.

Step 10) Install Linuxmce
sudo apt-get install virt-manager

Add user to administer you virtual machines to the libvirtd group
sudo adduser xxx libvirtd

Using virt-manager you can now install LinuxMCE. As we are all experts on that I will only give away my xml config file (should be enough ;-))

<domain type='kvm'>
<name>DCERouter</name>
<uuid>xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx</uuid>
<memory>2097152</memory>
<currentMemory>2097152</currentMemory>
<vcpu>2</vcpu>
<os>
<type arch='x86_64' machine='pc-0.11'>hvm</type>
<boot dev='hd'/>
</os>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/bin/kvm</emulator>
<disk type='block' device='disk'>
<source dev='/dev/sdc'/>
<target dev='hda' bus='ide'/>
</disk>
<disk type='file' device='cdrom'>
<target dev='hdc' bus='ide'/>
<readonly/>
</disk>
<interface type='bridge'>
<mac address='xx:xx:xx:xx:xx:xx'/>
<source bridge='bridge_ext'/>
</interface>
<interface type='bridge'>
<mac address='xx:xx:xx:xx:xx:xx'/>
<source bridge='bridge_int'/>
<model type='virtio'/>
</interface>
<serial type='pty'>
<target port='0'/>
</serial>
<console type='pty'>
<target port='0'/>
</console>
<input type='tablet' bus='usb'/>
<input type='mouse' bus='ps2'/>
<graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/>
<video>
<model type='cirrus' vram='9216' heads='1'/>
</video>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x03' slot='0x08' function='0x0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x03' slot='0x09' function='0x0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='yes'>
<source>
<vendor id='0x0403'/>
<product id='0xf2d0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/>
</source>
</hostdev>
</devices>
</domain>

Step 11) Enjoying building a test enviroment, inline upgrade etc.

Step 12) I chose to put my media on the host via a Samba share which will be detected as a NAS. This will simplify things when performing upgrades and test. Because I am using LVM also expansion is easy ;-)

[[Image:Lmce_kvm.png]]

'''
== Hints/Known Issues/Working Hardware ==
'''

'''AMD/ATI Hardware''' 
- NVidia Chipset 3600 with Opteron Socket F has full KVM support and works fine with LMCE 8.10. 
- ATI-driver 9.8 supports kernel 2.6.30 

'''Keyboard Layout''' 
- As you can't choose the keyboard-layout in virtual-manager, simply change the keymap in the xml-file e.g. from "en-us" to "de".

'''Networking''' 
- Step 11) is not needed if the physical network devices are configured as 'auto ethx \ iface ethx inet manual' 
- The virtual LMCE runs fine with only one NIC provided to it. The setup automatically configures a sub-NIC which works well. I would suggest to have the host provide the internet-access, so vLMCE can't mess it up at the installation.

'''PCI-Passthrough at KVM''' 
- PCI-Passthrough only works if the full PCI-device is transferred to the virtual machine. So if the PCI-Slot has sub-functions (e.g. Firewire) all of the 'functions' have to be adressed to the virtual machine with the <hostdev> section of Step 12). To look up your PCI-device-tree, use 'lspci -t'. 

(Tyan S2915-E)
[0000:00]-+-00.0
+-01.0
+-01.1
+-02.0
+-02.1
+-04.0
+-05.0
+-05.1
+-06.0-[0000:01]----04.0 (<- PCI-Slot = DVB-card)
\-04.1 (<- Firewire, either disable in Bios or ->KVM)
+-06.1
+-08.0
+-09.0
+-0d.0-[0000:02-04]--+-00.0-[0000:03]----04.0
| \-00.1-[0000:04]--
+-0f.0-[0000:05]--+-00.0
| \-00.1
+-18.0
+-18.1
+-18.2
+-18.3
\-18.4

- PCIe-devices do not have this restriction. 

- Please note that each change in the .xml-files is activated only after rebooting the libvirtd. You can do this manually by killing and restarting the process "libvirtd" or by a host reboot.

'''Problems with PVR-150 not responding'''

During usage it turned out that sometimes recordings failed having a total size of 0 B. Live TV has not worked stable at all. Checking the mythbackend logs shows that /dev/video0 was not responding as expected.
Furthermore I detected DMA errors in the log of the host.

I am now testing the commandline option iommu=on,igfx_off,pass-through, where pass-through should be able to iron out the DMA errors.

Because the behaviour was not stable I also installed the mercurial ivtv drivers (within the VM ofcourse!!!!):

sudo apt-get install mercurial
cd /usr/src
sudo hg clone http://linuxtv.org/hg/v4l-dvb
cd v4l-dvb
sudo make
sudo make install
sudo make unload
sudo make load

You will have to rebuild after a kernel change.

'''Clicking sound on Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02)'''

When passing-through my audio card I noticed hick ups in the MP3's and a message in kern.log;

hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.

edit alsa-base.conf;

vim /etc/modprobe.dalsa-base.conf

add the following line at the bottom;

options snd-hda-intel model=3stack-dig
options snd-hda-intel enable_msi=1
options snd-hda-intel single_cmd=1

and reboot (reload alsa does not seem to have the full effect)

Tip from [https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/274424 Bugs Launchpad]

Installing LinuxMCE on VM via KVM on Ubuntu 10.10 Server

2011-02-14T18:12:11Z

JoakimL:

[[Category: Virtualization]]
[[Category: Documentation]]
[[Category: Tutorials]]

{{versioninfo|810Status=still testing|810UpdatedDate=9th february 20101|810UpdatedBy=JoakimL}}

This is based on daballiemo's [[http://wiki.linuxmce.org/index.php/Installing_LinuMCE_on_Virtual_Machine_via_KVM
== '''KVM: To baldly go where (almost) no man has gone before''' ==]]
<<< This is not complete yet, follow at own risk>>>

In this overview I will try to follow the installation path to get LCME 8.10 into a virtual machine on Ubuntu 10.10 which uses USB devices from the host.

Machine details first:

* Motherboard: ASUS P5E VM DO with bios 10.1
* CPU: AMD AM2 4400+
* 2 Gb DDR-2 Memory
* 1 onboard GbE Nic
* 1 PCI-E GbE Nic
* 1 Hauppauge WinStick Nova T2

lspci
00:00.0 RAM memory: nVidia Corporation MCP65 Memory Controller (rev a3)
00:01.0 ISA bridge: nVidia Corporation MCP65 LPC Bridge (rev a3)
00:01.1 SMBus: nVidia Corporation MCP65 SMBus (rev a1)
00:01.2 RAM memory: nVidia Corporation MCP65 Memory Controller (rev a1)
00:02.0 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3)
00:02.1 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3)
00:07.0 Audio device: nVidia Corporation MCP65 High Definition Audio (rev a1)
00:08.0 PCI bridge: nVidia Corporation MCP65 PCI bridge (rev a1)
00:09.0 IDE interface: nVidia Corporation MCP65 IDE (rev a1)
00:0a.0 IDE interface: nVidia Corporation MCP65 SATA Controller (rev a3)
00:0b.0 PCI bridge: nVidia Corporation Device 045b (rev a1)
00:0c.0 PCI bridge: nVidia Corporation MCP65 PCI Express bridge (rev a1)
00:0d.0 PCI bridge: nVidia Corporation MCP65 PCI Express bridge (rev a1)
00:0e.0 PCI bridge: nVidia Corporation MCP65 PCI Express bridge (rev a1)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
04:00.0 VGA compatible controller: nVidia Corporation G86 [GeForce 8500 GT] (rev a1)

Step 1) Install Ubuntu 10.10 server 64 bit

Step 2) Make the system current:

sudo apt-get update
sudo apt-get upgrade

Step 3) Add some management tools:

I use webmin to give my server a fixed ip address and perform other administrative tasks.

apt-get install libnet-ssleay-perl libauthen-pam-perl libio-pty-perl
wget http://mirrors.kernel.org/ubuntu/pool/universe/libm/libmd5-perl/libmd5-perl_2.03-1_all.deb
sudo dpkg -i libmd5-perl_2.03-1_all.deb
sudo wget http://sourceforge.net/projects/webadmin/files/webmin/1.520/webmin_1.520_all.deb/download
sudo dpkg -i download
sudo apt-get install -f

I use MidNight Commander for file stuff

apt-get install mc

Step 4) Getting the right kernel and parameters

Install the required tools and packages, so open a terminal and type the following,

sudo apt-get install fakeroot kernel-wedge build-essential makedumpfile kernel-package libncurses5 libncurses5-dev

Get the right kernel, at the time of writing 2.6.37 was the best kernel source.

wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.37.tar.bz2
tar -jxvf linux-2.6.37.tar.bz2 -C /usr/src

Go to the unpack directory

cd /usr/src/linux-2.6.37

It is a good idea to start with the same .config as the currently running kernel, so type the following,

sudo cp -vi /boot/config-`uname -r` .config

Now we are ready to customize the build and kernel options.

sudo make menuconfig

* set "Bus options (PCI etc.)" -> "Support for DMA Remapping Devices" to "*"
* set "Bus options (PCI etc.)" -> "Enable DMA Remapping Devices" to "*"
* set "Bus options (PCI etc.)" -> "PCI Stub driver" to "*"
This line broke my setup so I took it out * optional setting: set "Bus options (PCI etc.)" -> "Support for Interrupt Remapping" to "*"

Once you have finished, save and exit. It is now time to compile. However to speed up the build if you have a dual/triple/quad core processor type (one more than the number of cores you have).

export CONCURRENCY_LEVEL=3

The general rule is 1 + the number of processor cores.

Step 5) Build the new kernel.

sudo make-kpkg clean
fakeroot make-kpkg --initrd --append-to-version=-iommu kernel-image kernel-headers

You can grab a coffee, make a hot meal, have a sleep ;-)

Step 6) Install The New Kernel

After the successful kernel build, you can find two .deb packages in the /usr/src directory.
cd ..
ls -l linux*

Install them:
dpkg -i linux-image-2.6.33-custom_2.6.33-custom-10.00.Custom_amd64.deb
dpkg -i linux-headers-2.6.33-custom_2.6.33-custom-10.00.Custom_amd64.deb

Step 7) Booting with the new kernel

Add the options to enable IOMMU in the kernel commandline

edit /etc/default/grub

new: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_iommu=on,igfx_off,pass-through"
old: #GRUB_CMDLINE_LINUX_DEFAULT="quiet"

update the booting menu

update-grub

and reboot

sudo reboot

Step 8) Deinstall networkmanager

sudo apt-get remove network-manager

Step 9) Setup your network, change /etc/network/interfaces to look like this

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The first bridge interface
auto bridge_ext
iface bridge_ext inet static
address 0.0.0.0 #no external access without going through DCERouter first
netmask 255.255.255.0
broadcast 10.0.0.255
gateway 10.0.0.138
bridge_ports eth0
bridge_stp off
bridge_maxwait 5
# The second bridge interface
auto bridge_int
iface bridge_int inet static
address 192.168.80.240
netmask 255.255.255.0
broadcast 192.168.80.255
gateway 192.168.80.1
bridge_ports eth1
bridge_stp off
bridge_maxwait 5

With the above the host will use dcerouter as its way into the internet and thus the protection offered by the firewall. The host has no direct access to the 10.0.0.0 network.

Step 10) Install Linuxmce
sudo apt-get install virt-manager

Using virt-manager you can now install LinuxMCE. As we are all experts on that I will only give away my xml config file (should be enough ;-))

<domain type='kvm'>
<name>DCERouter</name>
<uuid>xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx</uuid>
<memory>2097152</memory>
<currentMemory>2097152</currentMemory>
<vcpu>2</vcpu>
<os>
<type arch='x86_64' machine='pc-0.11'>hvm</type>
<boot dev='hd'/>
</os>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/bin/kvm</emulator>
<disk type='block' device='disk'>
<source dev='/dev/sdc'/>
<target dev='hda' bus='ide'/>
</disk>
<disk type='file' device='cdrom'>
<target dev='hdc' bus='ide'/>
<readonly/>
</disk>
<interface type='bridge'>
<mac address='xx:xx:xx:xx:xx:xx'/>
<source bridge='bridge_ext'/>
</interface>
<interface type='bridge'>
<mac address='xx:xx:xx:xx:xx:xx'/>
<source bridge='bridge_int'/>
<model type='virtio'/>
</interface>
<serial type='pty'>
<target port='0'/>
</serial>
<console type='pty'>
<target port='0'/>
</console>
<input type='tablet' bus='usb'/>
<input type='mouse' bus='ps2'/>
<graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/>
<video>
<model type='cirrus' vram='9216' heads='1'/>
</video>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x03' slot='0x08' function='0x0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x03' slot='0x09' function='0x0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='yes'>
<source>
<vendor id='0x0403'/>
<product id='0xf2d0'/>
</source>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/>
</source>
</hostdev>
</devices>
</domain>

Step 11) Enjoying building a test enviroment, inline upgrade etc.

Step 12) I chose to put my media on the host via a Samba share which will be detected as a NAS. This will simplify things when performing upgrades and test. Because I am using LVM also expansion is easy ;-)

[[Image:Lmce_kvm.png]]

'''
== Hints/Known Issues/Working Hardware ==
'''

'''AMD/ATI Hardware''' 
- NVidia Chipset 3600 with Opteron Socket F has full KVM support and works fine with LMCE 8.10. 
- ATI-driver 9.8 supports kernel 2.6.30 

'''Keyboard Layout''' 
- As you can't choose the keyboard-layout in virtual-manager, simply change the keymap in the xml-file e.g. from "en-us" to "de".

'''Networking''' 
- Step 11) is not needed if the physical network devices are configured as 'auto ethx \ iface ethx inet manual' 
- The virtual LMCE runs fine with only one NIC provided to it. The setup automatically configures a sub-NIC which works well. I would suggest to have the host provide the internet-access, so vLMCE can't mess it up at the installation.

'''PCI-Passthrough at KVM''' 
- PCI-Passthrough only works if the full PCI-device is transferred to the virtual machine. So if the PCI-Slot has sub-functions (e.g. Firewire) all of the 'functions' have to be adressed to the virtual machine with the <hostdev> section of Step 12). To look up your PCI-device-tree, use 'lspci -t'. 

(Tyan S2915-E)
[0000:00]-+-00.0
+-01.0
+-01.1
+-02.0
+-02.1
+-04.0
+-05.0
+-05.1
+-06.0-[0000:01]----04.0 (<- PCI-Slot = DVB-card)
\-04.1 (<- Firewire, either disable in Bios or ->KVM)
+-06.1
+-08.0
+-09.0
+-0d.0-[0000:02-04]--+-00.0-[0000:03]----04.0
| \-00.1-[0000:04]--
+-0f.0-[0000:05]--+-00.0
| \-00.1
+-18.0
+-18.1
+-18.2
+-18.3
\-18.4

- PCIe-devices do not have this restriction. 

- Please note that each change in the .xml-files is activated only after rebooting the libvirtd. You can do this manually by killing and restarting the process "libvirtd" or by a host reboot.

'''Problems with PVR-150 not responding'''

During usage it turned out that sometimes recordings failed having a total size of 0 B. Live TV has not worked stable at all. Checking the mythbackend logs shows that /dev/video0 was not responding as expected.
Furthermore I detected DMA errors in the log of the host.

I am now testing the commandline option iommu=on,igfx_off,pass-through, where pass-through should be able to iron out the DMA errors.

Because the behaviour was not stable I also installed the mercurial ivtv drivers (within the VM ofcourse!!!!):

sudo apt-get install mercurial
cd /usr/src
sudo hg clone http://linuxtv.org/hg/v4l-dvb
cd v4l-dvb
sudo make
sudo make install
sudo make unload
sudo make load

You will have to rebuild after a kernel change.

'''Clicking sound on Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02)'''

When passing-through my audio card I noticed hick ups in the MP3's and a message in kern.log;

hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.

edit alsa-base.conf;

vim /etc/modprobe.dalsa-base.conf

add the following line at the bottom;

options snd-hda-intel model=3stack-dig
options snd-hda-intel enable_msi=1
options snd-hda-intel single_cmd=1

and reboot (reload alsa does not seem to have the full effect)

Tip from [https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/274424 Bugs Launchpad]