I've had some troulbe too with getting nvidia drivers to cooperate. When you boot your md and finally the x-setup failed, try ctrl+alt+f1 or f2..it should give you the login
login there with linuxmce then do sudo apt-get update then sudo apt-get dist-upgrade. when you're done with that, reboot and if thex-setup fails yet again, go again to the console like before and do a sudo nvidia-xconfig.
lets see if that will help

@Thingie,

okay...lets take this one at a time....
can I assume you have the core running so far, or do you have issues with the avwizard there too?
Then, what kind of MD are you running? I didn't see your hardware so far. Perhaps if you can elaborate on that one, maybe we can figure out, what drivers you need...or what causes your issues.

@Thingie
If I am not mistaken, the thread you referred to  was for 7.10. I don't think you need to do any of this on 8.10. But one thing after another...if you don't want to use your core for playback, then you don't need to invest too much work with drivers there. For starters, I would suggest you use basic skin and the UI1 with static images for your core. Should you decide later on to use it, you can still try this later. I used to have an eee-box before, which also used an Intel graphics chipset, but that handled only UI2 with overlay.
About your MD, I suggest also for start ui1 and static images. Use this to setup your MD. Once your orbiter is setup completely, you can go to KDE-desktop and check with your restricted drivers. I also had some trouble at first with my ASROCK Ion 330- I couldn't even activate the restricted drivers.
I put the avenard release repository, did apt-get update, apt-get dist-upgrade and reboot. After that, I went to the KDE-Desktop again, opened a terminal and did nvidia-xconfig, which wrote me a new xorg.conf. With the next reboot I forced the AVWizard and set it up to fullHD and UI2 with alpha-blending.
Try it out and let me know if it helped.
----------
Now I have a question of my own: When I'm watching TV or movie, after some minutes the screensaver seems to kick in and blacks out my TV..how can I keep this from happening?

Right now everything is running A-okay again, even the windows orbiter - don't know why it didn't show the media buttons right away.
Anyways, I had some minor issue with Mythtv on the MD, but I could resolve it again with this one:

Code:

http://forum.linuxmce.org/index.php?topic=8971.msg61434#msg61434

in case someone runs into this problem again

of course, my mistake :-)
-------------------------------
since I cracked my system accidentally last Friday with the updated mythtv I became a bit hesitant, but I can't help but wonder....how the existing installs from the alpha will make the shift to that one. If I could backup my exisiting install completely, I would like to try again. I think what caused most of the headache was the fact, that my MD first got the new version and I was scrambling to get my core to comply. Before I killed the beta-install I made a dump of the mythconverg, so that in case I could restore it again in a new install...I got pretty tired watching the progressbar for the tuning grow ever so slowly :-)
In theory I could just change the avenard repo to "release testing", drop the current mythconverg and do a aptitude update and aptitude dist-upgrade,reboot,restore my backup of the mythconverg and then proceed with the update of the MD
Right now I have a spare 200Gb hdd sitting around, which I could use to do a complete backup....any suggestion, what to use for that?

hmm, thats interesting...I will try the mobile orbiter on my n810....the onscreen orbiters are also fine...only the ones on windows are behaving oddly.
On a positive side, the didn't produce an error message unlike with the alpha on windows7

Did anyone of you try the windows orbiter? In the latest alpha as well as in the beta-dvd, there are no media buttons...the only thing visible is telecom and security.

thats what I did..anything else is probably not a good idea, since it will break a lot of things.

Well, I found this very interesting, because I thought the  new mythtv was more like an "accident", especially considering the trouble it causes with the generation of  the initial boot image for the Md in the beta.
Anyways, I'm in the middle of setting up with the alpha-script, hopefully this works better and lets me setup my MD  successfully again. By the way, does anybody know if the v4l package has been updated too? The repo I found and  described in the wiki (for the nova hd s2) seems pretty interesting and is supposed to get you s2-channels...if there is something  similar included already, shouldn't it be enough to just put the firmware in its proper place and reboot?

I'm not really an expert on this, but did you perhaps get the new mythtv 0.22 installed? This could be the source of your problem. It is very new and as far as speculation goes, probably not intended.

After a while I of fiddling around I got the core working again, but only with basic skin and static ui. I checked out the nvidia-drivers, but I could not activate any of them. I will most probably make a new install tonight and go back to alpha. After seeing the new mythtv, i am a little reluctant though to go back to the "old" one..it looked quite nifty so far....too bad.
-------------------------
I just saw this on trac :

http://svn.linuxmce.org/trac.cgi/ticket/379

very interesting, I just wonder how this will affect the building of the bootimage for the MD, since there seems to be a problem with those packages, at least in the beta...don't know about the alpha

okay...now even the core is acting up...yesterday I could at least watch something there...now it seems the nvidia drivers crashed or somthing like that.

if I use the alpha-installer, will I run into the same problems, or will it be working without the hiccups from the DVD- because now I'm really in for another install it seems.

so I guess we'll have to wait for a while, because I don't think a reinstall would fix it, because the sources are coded in the installerscripts, right?

did you also check this

Code:

:http://avenard.com/media/Ubuntu_Repository/Entries/2009/8/27_Trunk___MythTV.html

?
to go back, you'd have to do some major work....I tried that one before last Friday and it didn't really work out...that was exactly the reason, why I did try the DVD.
I imagine quite a number of people have the same problem right now and I don't think that this is really a solution. In this situation I'd rather wait for the devs to come up with something.
Either they can modify the setup to avoid going to mythtv 0.22 or they find a way to go with it. The first alternative would make me do a new install, the second might be a dist-upgrade.
Right now I'd rather not try the above mentioned method, because there is a high chance of screwing up more while trying to fix it and then having to reinstall everything again- something I'm not looking forward to.
My bet is, we will be seeing a new dvd soon or something like it, because there are a number of things missing or not working properly, unlike with the last alpha.

well, to change to 0.21 would be quite problematic. The core already runs on 0.22 by default now. I ran into this problem when I last did an upgrade with the alpha. I was quite surprised, when I suddenly had a totally different mythtv... then I was dismayed, because it screwed around with the database. It wanted to upgrade the database, because the installed database was 29 versions behind...the upgrade didn't go through, so I dropped the database in mysql and created a new one...from there things didn't really go any better...
Essentially you proposal would mean to probably reinstall the whole core and change the sources there, which might have further implications, because I assume the developers thought about something, when they included the avenard repo testing...from there you will also get the latest nvidia-drivers. As I also saw there are some problems with nvidia-180-glx, which is also broken.
As far as I understand, currently there is no easy solution for this...except if you switch from mythtv to vdr, perhaps.