I deleted the MD copletely and let it build from scratch. Of course with the guideline from the link to prevent the problem with fglrx.I will try your last posting later this week and keep you informed what happened.best regardsRoman

Hi,at least I changed the core to 10.04 because of HW support. Until now I can not say if the VESA stuff got better because I did not get any MD to self register at the new core. As soon as I have the DELL laptop with the VESA issue online again I will post the rensult here.best regardsRoman

Hey l3mce, just wanted to say a big thanks to you for this thread because the link below and Roman's response to it prompted me to try this method with my IBM T30 notebook and finally I have it up and running as a media director. I'm super chuffed about that, thanks a stack. It was also getting to the "failed to setup X" stage and the steps outlined below sorted it out. Thanks again.

I just did an apt-get update && apt-get upgrade and then created the MD. I then tried copying the code from the 1st post into a new Utils.sh file and rebuilt the MD. Any thoughts? Running 10.04 with latest updates.

I appreciate the testing guys. This round is over. It is clear that fglrx needs to not be preloaded as it currently is, as it conflicts with the intel driver. We must only install it if ATI is detected... then in the AVWizard_Run.sh, if ATI is detected and fglrx fails, to replace that with the native radeon driver.

I appreciate folks confirming the problem to uncover a possible solution.