LinuxMCE - User contributions [en]

LinuxMCE8.10 Alpha

2009-02-13T07:31:07Z

RichardP: New page: {| align="right" | __TOC__ |} Currently (as of Feb 2009), the team is working hard on LinuxMCE-0810-Alpha2. The current alpha is available for download. Anyone wishing to do so, howe...

{| align="right"
| __TOC__
|}

Currently (as of Feb 2009), the team is working hard on LinuxMCE-0810-Alpha2.

The current alpha is available for download. Anyone wishing to do so, however, should understand that alpha-releases are a work in progress to be used by those who are willing to test a system and provide feedback to the team. It should not be used in an environment that you depend on to be reliable.

For more information, see the Alpha1 page at [[LinuxMCE-0810_alpha1]]

The instructions below are expected to remain the same for all alpha releases from Alpha2 onwards.

==Installation==
# Install Kubuntu Intrepid, update it and enable the restricted (video) drivers if needed. ([http://www.kubuntu.org/getkubuntu/download download Kubuntu 8.10 release])
# Run aptitude update and aptitude dist-upgrade to get the latest Kubuntu updates.
# Grab the latest installer script from [http://deb.linuxmce.org/ubuntu/new-installer-alpha-latest.tar.gz here], unpack them and change into the freshly created ''new-installer'' directory.
# Run the following scripts (as root, in order): pre-install-from-repo.sh, mce-install.sh, post-install.sh.
# Reboot, wait for the activity to stop (see progress on console 8).

In other words, after installing Kubuntu and upgrading it etcetera:
sudo su - #This might ask for the password you specified earlier during the install of kubuntu.
wget -c http://deb.linuxmce.org/ubuntu/new-installer-alpha-latest.tar.gz
tar xvf new-installer-alpha-latest.tar.gz
cd new-installer
./pre-install-from-repo.sh
./mce-install.sh
./post-install.sh
reboot

== Setup Diskless MD ==
# On core from a terminal run sudo /usr/pluto/bin/Diskless_BuildDefaultImage.sh
# Boot MD
# Rundiskless setup fails, but the device gets created
# Change md to i386 in webadmin -> rebuild image
# On the core
## Set a password for root on MD
###chroot /usr/pluto/diskless/<##>
### run passwd.... enter password for root
#On MD Switch to a terminal session
## Login to MD as root
## apt-get install nvividia-glx-177
#From core copy valid xorg.conf from etc/X11 to /usr/pluto/diskless/##/etc/X11
# Reboot MD. Now, the AV Wizard should come up
# After the AV Wizard it takes a longer time to launch devices. No not need to reboot.

=== Note ===
If you don't happen to have a running xorg.conf, copy over the existing /etc/X11/xorg.conf.pluto-avwizard to /etc/X11/xorg.conf.

You have to remove a single line RgbPath from the xorg.conf file, and change the line
driver nv

to
driver nvidia

== Known Problems ==
=== Upgrading pluto-storage-devices ===
If apt-get upgrade does cause problems with pluto-boot-scripts, do the following
dpkg -r --force-all pluto-storage-devices
apt-get install pluto-storage-devices
apt-get upgrade

=== VDR Installation ===
VDR does not yet install a working setup. Follow [[VDR Manual Install]] regarding configuration files.

=== VDR and sqlCVS Update ===
A sqlCVS update will reset the selection from VDR back to MythTV. Re-running the Setup wizard and re-selecting VDR rectifies this glitch.

AMP Configuration Guide

2008-01-24T03:12:32Z

RichardP:

<h1>How to configure Asterisk with AMP (Asterisk management portal)</h1>
AMP is a separate web based configuration tool for Asterisk. It is no longer being actively developed as a seperate project. Instead, it has been integrated into [http://www.freepbx.org Freepbx]. More information can be found on the [http://www.voip-info.org/wiki/view/freePBX VoIP Wiki].
Here is a quick intro as it relates to LinuxMCE. Note the AMP integration is not fully complete. In time this process will become more seamless.
Step 1: Add your phones
The phones in your home will be stored in 2 places: Once in LinuxMCE's database as LinuxMCE devices. This is where the orbiters retrieve the list of phones in the house to display on the screens, and also the phones you can position on the floorplan. Secondly, AMP also maintains its own list of phone extensions that it uses to configure Asterisk. Normally LinuxMCE's list and AMP's list will stay in sync automatically. You can verify this by checking Wizard, Devices, Phones to see LinuxMCE's list.
It should look like this include/images/amp/amp-00.jpg" target="_blank"><img src="include/images/amp/t-amp-00.jpg

Go to include/images/amp/amp-01.jpg" target="_blank">Wizard, Devices, Phone Setup</a>, you will see <a href="include/images/amp/amp-02.jpg" target="_blank
click 'Setup', then include/images/amp/amp-03.jpg" target="_blank
and you'll be be able to include/images/amp/amp-04.jpg" target="_blank an extension (usefull if your phone is not plug-and-play), but take a look at extension list in the right. The 'Extension' in AMP's list should equal the 'PhoneNumber' in LinuxMCE's list, and in LinuxMCE's list if you click the 'ADV' button, you will see LinuxMCE's IP address, which should correspond to AMP's.
include/images/amp/amp-05.jpg" target="_blank"><img src="include/images/amp/t-amp-05.jpg"></a><a href="include/images/amp/amp-05a.jpg" target="_blank"><img src="include/images/amp/t-amp-05a.jpg

LinuxMCE has its own plug & play back end. If you have IP based phones, just plug them in. If we have that model in our plug & play database it should appear automatically in AMP's phone extension table and also in LinuxMCE's Device list. Otherwise you must add the phones manually to both lists. For each phone specify the IP address of the phone and a give each phone a unique phone extension (the 'Phone Number' on LinuxMCE's list).

Check that device is listed as child of 'Asterisk' device.
Goto AMP's config site include/images/amp/amp-05.jpg" target="_blank section...
<ul><li>if your phone is plug&play it should be listed
on the right, select it and just check if all data are ok.</li>
<li>otherwise include/images/amp/amp-04.jpg" target="_blank (specify phone type(SIP/IAX2),
Extention, Password and later IP address.
</ul>

Don't forget to regenerate screens on orbiters and quick reload
for dcerouter.
If you added more than one phone, try to call between them
It's a good idea to setup a default phone in include/images/amp/amp-15.jpg" target="_blank section

Step 2: Add your phone lines and VOIP providers
Next step is to setup external lines...Please follow your VOIP
provider's instructions.

Implementing Clipsal Interface using Generic Serial Device

2008-01-17T02:21:58Z

RichardP:

Clipsal CBus Switches are used for controlling lights, curtains and temperature controls. They can be connected to the Serial Port and can be controlled via a PC. In the following tutorial, we will add Clipsal Switches using Generic Serial Device and implement Lights and Shutter control through the Linux MCE.

== Steps to Add Clipsal Interface ==

* Create a Device Template 'Clipsal Interface' in Device Category: "Interfaces - Lighting Interface #81"
* Check Implements DCE - Command Line - Generic Serial Device
* In the packages, add "Pluto Generic Serial Device"
* In Device Data, add "#37 COM Port on PC(string)"
* In Commands Section, create and select "Ruby Internal Commands"

This Clipsal Interface will act as a parent device to all the child devices (eg. Lights, Curtains) that are controlled via the serial port to which Clipsal Switch is connected. Now create a device from the device template Clipsal Interface.

== Ruby Commands for Lighting ==

The Clipsal Interface will have all the lighting and curtains as its child devices. The commands from child devices will be directed to Clipsal Interface and this interface will send these commands to the serial port to which clipsal switch is connected.

For the Clipsal Interface, following ruby commands will be implemented:

* #Private Method Listing #373
* #Process IDLE #351
* #Process Incoming Data #350
* #Process Initialize #355
* #Process Receive Command For Child #384
* #Process Release #356

The most important of this command is #Process Receive Command For Child #384, which is process incoming data from child devices. When we receive any command from child device such as Light or Shutter, the ruby commands in this section are invoked and we need to send relevant commands to the serial port to carry out the action on lights or shutters.

To edit the Ruby Commands for #384 Process Receive Command For Child, Edit the Clipsal Interface and click on 'Edit Ruby Codes' besides Implements DCE on the top.

== Ruby Code ==

group_no = device_.childdevices_[cmd.devidto_].devdata_[12]

if cmd.id_ == 192
serial_on = "\\05380079"+group_no+"\r"
log( "Sending " + serial_on + " \n" )
sendCmd(serial_on)
end

if cmd.id_ == 193
serial_off = "\\05380001"+group_no+"\r"
log( "Sending " + serial_off + " \n" )
sendCmd(serial_off)
end

log("We got cmd : " + cmd.id.to_s)

if cmd.id_ == 184
dim_level = cmd.params_[76]
serial_dim = "\\05380002"+group_no+""+dim_level+"\r"
log( "Sending " + serial_dim + " \n")
sendCmd(serial_dim)
end

== Explanation ==

In the ruby code, what is happening is when we receive a command from any of the child devices (such as lights, curtains), we also get its port number. Then, using that port number we make a binary string to be sent to the serial port. That binary string is sent to the serial port defined in the Clipsal Interface Device Data.

eg. Command # 192 is the command to switch light ON. The binary string to switch a light ON to be sent to the serial port is:

\05380079 + Port Number + \r

So, we receive the port number from child device (group_no), concatenate it in the binary string and send it to the serial port defined in the Clipsal Interface.
[[Category: Tutorials]]

Creative Audigy 2 Value

2008-01-07T13:31:31Z

RichardP:

[[Category: Hardware]]
[[Category: Audio]]
[[Category: Soundcards]]

The Creative Audigy 2 Value, also sold as Creative Value LS, is a fairly decent budget soundcard. Creative's page can be found here: http://au.creative.com/products/product.asp?category=1&subcategory=205&product=14189
Be aware this link will most probably expire when the card is no longer current.

The card seems to work fully in LinuxMCE, although there is some configuration to do before it does. On initial installation in both 0704 and 0710 Beta 2, Appserver would not start up. As a result, Myth would not work. The problem seems to be that Appserver tries to access a sound mixer device upon startup. This card does not have one, and Appserver exits with an errorcode of 139. To fix this issue, install a software sound mixer.

For more general detail on installing the software mixer, see:
http://alsa.opensrc.org/index.php/Softvol
http://alsa.opensrc.org/index.php/How_to_use_softvol_to_control_the_master_volume

For more specific detail with a working example, see the link off this page:
http://www.pillayfamily.com/LinuxMCE/index.html

Creative Audigy 2 Value

2008-01-07T13:29:39Z

RichardP:

[[Category: Hardware]]
[[Category: Audio]]
[[Category: Soundcards]]

The Creative Audigy 2 Value, also sold as Creative Value LS, is a fairly decent budget soundcard. Creative's page can be found here: http://au.creative.com/products/product.asp?category=1&subcategory=205&product=14189
Be aware this link will most probably expire when the card is no longer current.

The card seems to work fully in LinuxMCE, although there is some configuration to do before it does. On initial installation in both 0704 and 0710 Beta 2, Appserver would not start up. As a result, Myth would not work. The problem seems to be that Appserver tries to access a sound mixer device upon startup. This card does not have one, and Appserver exits with an errorcode of 139. To fix this issue, install a software sound mixer.

For more general detail on installing the software mixer, see:
http://alsa.opensrc.org/index.php/Softvol
http://alsa.opensrc.org/index.php/How_to_use_softvol_to_control_the_master_volume

For more specefic detail, see the link off this page:
http://www.pillayfamily.com/LinuxMCE/index.html

Creative Audigy 2 Value

2008-01-04T23:47:54Z

RichardP:

[[Category: Hardware]]
[[Category: Audio]]
[[Category: Soundcards]]

The Creative Audigy 2 Value, also sold as Creative Value LS, is a fairly decent budget soundcard. Creative's page can be found here: http://au.creative.com/products/product.asp?category=1&subcategory=205&product=14189
Be aware this link will most probably expire when the card is no longer current.

The card seems to work fully in LinuxMCE, although there is some configuration to do before it does. On initial installation in both 0704 and 0710 Beta 2, Appserver would not start up. As a result, Myth would not work. Appserver tries to access a sound mixer device upon startup. This card does not have one, and Appserver exits with an errorcode of 139. To fix this issue, install a software sound mixer.

For more detail on installing the software mixer, see:
http://alsa.opensrc.org/index.php/Softvol
http://alsa.opensrc.org/index.php/How_to_use_softvol_to_control_the_master_volume

Creative Audigy 2 Value

2008-01-04T16:54:53Z

RichardP: Creative Audigy soundcard.

Sound Cards

2008-01-04T16:42:04Z

RichardP:

[[Category: Hardware| ]]
[[Category: Audio]]
[[Category: Hardware Lists]]
'''''This page is obsolete, please use a single page for each piece of hardware and add it to the relevant categories as described here: [[Adding your own hardware]]'''''

== This is a list of sound cards and our experiences with them ==

{| border="1" cellspacing="0" cellpadding="5" align="center"
! Card
! Chip
! Type
! PCI ID
! Subsystem
! Notes
|-
| Creative Audigy Value
Creative Audigy LS
| Unknown
| PCI
| ?
| ?
| Analog Stereo
S/PDIF: PCM, AC3/DTS passthrough
This card works fully. However, it need some setup. It lacks a hardware sound mixer, so a sound mixer has to be provided in software. Until this is done, Appserver and Myth will not start up under LMCE.
|-
|-
| VIA 8237
| Realtek ALC655 rev 0
| on-board
| 1106:3059
| 1565:8212
| Analog Stereo
S/PDIF: PCM, AC3/DTS passthrough
|-
| HDA NVidia
| Analog Devices AD1986A
| on-board (ASUS M2NPV-VM)
| 10DE:026C
| 10DE:CB84
| Analog Stereo: this driver is 5.1 native, not stereo. One of the speakers probably gets the LFE and that gives a high pitched sound in the headphones
S/PDIF: PCM, AC3/DTS passthrough
|-
| Intel ICH5
| Analog Devices AD1888
| on-board
| 8086:24D5
| 1043:810D
| Analog Stereo
S/PDIF: PCM, AC3/DTS passthrough
|-
| SB Live [Unknown]
| SigmaTel STAC9708,11
| PCI
| 1102:0002
| 1102:8067
| Analog Stereo works
S/PDIF is not reliable. At first, there was no S/PDIF output, but, at some point, passthrough started working, but not PCM. On another variation of this card (different subsystem), PCM worked (but not passthrough) after enabling the AC97 loopback (snd-ac97-codec module parameter) and unmuting the ADC/DAC control in alsamixer, but not on this one. When trying to play PCM through S/PDIF, this card clicks once every few seconds (once S/PDIF started to work that is) until the playing is stopped.
|-
| NVidia CK804
| Realtek ALC850 rev 0
| on-board (ASUS A8N-E)
| 10de:0059
| 1043:812a
| Analog Stereo works
S/PDIF output works with additional configuration (see below)
|-
|}

==NVidia CK804==
In the pluto-admin website under "Wizard:Devices:Media Directors" set the audio to "Manual settings" with "AC3 pass-through" checked for the desired Media Director.
===asound.state===
Info to come
===asound.conf===
Info to come
===xine.conf===
Make the following change to /etc/pluto/xine.conf 
Change "#audio.speaker_arrangement:Stereo 2.0" 
To read "audio.speaker_arrangement:Pass Through"

If you still do not have success with your CK804 chip, but the KDE sounds come out just fine, change /etc/pluto/xine.conf
Change "audio.alsa_front_device:asym_spdif"
To read "audio.alsa_front_device:default"