[X3lectric]

What I can do is rerun your proposed steps, but I have the impression that these are the same steps I've done a hundred times, I know them by heart

Those are the only way XCI will work best, because of minimal karmic installer bugs, e.g. you end up with open office installed amongst other program a HTPC does NOT need.
Besides its been tested to death by dozens of beta testers.

I wouldn't have bothered writing a how to if there weren't any problems with the NORMAL way of installing it which affect everything.

Dunno exactly what the backport means...
Fact is: that you're running with 1.0.20 drivers. I've read some weeks ago something about that, saying it has something to do with your linux kernel. As I understood it, having the driver version still on 1.0.20. means you're still running your old version of the kernel.

Its apparent you have little knowledge of common Linux terminology, maybe a language barrier? I never asked where your from.

You just say it doesn't work... when it could be simply error on my part, (because I am inexperienced and noone helps me do anything e.g. backporting) Or it could be the version I backported was buggy to begin with.

without YOU knowing the processes you will never understand how it works and why its broken.

https://help.ubuntu.com/community/UbuntuBackports

Please don't say fact is, when you don't understand what a backport is and why its may not work ok. which I know its not running ok...

I invite you to read ubuntu documentation

I've tried to explain to you that maverick where I took alsa 1.0.23 and alsa-utils and some other critical alsa component I forget now. in a development environment changed files so they would compile in karmic. (they did with no warning or errors)

Now karmic generally handles alsa in a different way to maverick, (see dependencies or initializing code) (i cant tell you specifics google has it somewhere)

Karmic alsa doesn't support multichannel audio hence the need to have updated packages.

The way maverick requires calls on alsa and uses alsa is clearly VERY different from karmic I mean its like comparing a jet plane (maverick) and a Cessna (propeller powered) they both use fule and both fly but they use different methods of propulsion.

I can post here my script, it's quite simple.
The way it works: wget from alsa site and make, configure & install the stuff.
My solution would be to kick out the ppa solution, and paste in my script.
But that would break your efforts for the ppa's which is always a nicer solution I think.
Though the results should be the same: a full 1.0.23 version.

Compile any package manually by downloading the source is a temporary solution. a script should avoid temporary solutions, or offer the choice of using ppa or compiling. (this is where the menu system starts to show its power in XCI)

problem is with ever major update you need to re-run these things manually so they become available to system again.

This is why using PPA over manual compile is better because its automatic.

Alos there already is a PROPER manual compile script, both in xbmc source and http://ubuntuforums.org/showthread.php?p=6589810

Can you give me access to the code?

What code? XCI code you mean? or something else? if you want XCI code here it is

Another problem is still the xorg.
So if the there is no solution for that, giving me svn access is useless, since xbmc doesn't evens start

Ive already said to you there is no SVN for XCI because its way too small and only 1 person working with it, so you just download script and edit it with nano, vim, or if your using a desktop gedit

And there is no problem with xorg, its video drivers or the grubpc bootline. BTW XCI needs XBMC as user and needs grub2 all is explained in guide.

regards.