Worked! XBMC is more responsive on Raspbian than it is in RaspBMC. I've edited Mr. Gorven's instructions and stolen some of the comments to make an attempt at a howto:
This page describes how to install XBMC on a Raspberry Pi running Raspbian. You can either install packages on an existing Raspbian installation, or you can download a prebuilt image and flash it to an SD card.
Installing packages on an existing installation
I've published a Debian archive containing packages for XBMC and some dependencies which it requires. This can be setup on an existing Raspbian installation (including the foundation image).
The easiest way to install the package is to add my archive to your system. To do this, store the following in /etc/apt/sources.list.d/mene.list:
(you will have to create the file by running sudo pcmanfm)
and import the archive signing key:
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-key 5243CDED
Then update the package lists:
sudo apt-get update
You can then install it as you would with any other package, for example, with apt-get:
sudo apt-get install xbmc
The user which you're going to run XBMC as needs to be a member of the following groups:
audio video input dialout plugdev
If the input group doesn't exist, you need to create it:
addgroup --system input
and setup some udev rules to grant it ownership of input devices (otherwise the keyboard won't work in XBMC), by placing the following in /etc/udev/rules.d/99-input.rules:
SUBSYSTEM=="input", GROUP="input", MODE="0660"
(Note: found all this intact)
Make sure you have at least 128 megs associated to the gpu:
sudo raspi-config >Advanced Options>A3: Memory Split
Steps to creating script on Raspbian desktop:
On raspbian desktop:
*right-mouse button -> create new -> blank file
*Open file with leafpad or other text-editing program, write script and save
Script for desktop file:
sudo chvt 1
sudo chvt 7
...and now script automatically does Ctrl+Alt+F1 and Ctrl+Alt+F7 after exiting xbmc. This fixes the blank-screen-on-exit problem.
*Right-click file on desktop -> properties -> permissions -> make the file executable -> ok
*Double-click file on desktop and choose "execute" to execute script
To check that you can use this command line (replace "pi" by your user name) :
and it should return something like this:
uid=1000(pi) gid=1000(pi) groupes=1000(pi),4(adm),20(dialout),24(cdrom),27(sudo),29(audio),44(video),46(plugdev),60(games),100(users),105(netdev),999(input)
To run XBMC:
Use desktop file above, or:
run xbmc-standalone from a VT (i.e. not under X). XBMC accesses the display directly and not via Xorg.
If you want XBMC to automatically start when the system boots, edit /etc/default/xbmc and change ENABLED to 1:
You also need to set the user which XBMC should run as (the xbmc user is not automatically created at the moment). Run sudo service xbmc start to test this.
· 12.2-1: Frodo 12.2 release.
· 12.1-1: Frodo 12.1 release. Requires newer libcec (also in my archive).
· 12.0-1: Frodo 12.0 release. This build requires newer firmware than the raspberrypi.org archive or image contains. Either install the packages from the raspberrypi.org untested archive, the twolife archive or use rpi-update. (Not necessary as of 2013/02/11.)
· 12.0~git20130102.7a6cb7f-1: Frodo RC 3.
· 12.0~git20121219.74b907c-1: Frodo RC 2.
· 11.0~git20121114.25bb46a-1: Frodo Beta 1. This includes a database schema upgrade, so make sure to backup your userdata folder before upgrading.
· 11.0~git20121027.99da926-1: Fixes the issue of the last few seconds of video being cut off.
· 11.0~git20121018.ff434fe-1: Upgrading to this version will probably result in the GUI resolution being zoomed as described in this forum post. To fix this edit userdata/guisettings.xml and remove the contents of the <resolutions> element.
· 11.0~git20120728.365953fb-4: Initial release
This page modified 20130623 by Kevin Bowers (kevinthefixer) for ease-of-use from Michael Gorvin: http://michael.gorven.za.net/raspberrypi/xbmc
. Most modifications are copied directly from the comments. Most of the system errors found in the same comments were directly attributed to typographical errors; I strongly recommend using copy-and-paste to avoid this.
I hope this helps someone else out. Thanks to all for all the hard work: Good Job!