I'm not trying to be difficult,... I'm just trying to point out that it was working before but didn't later...
You say the limitation would be compositing,... But the Intel driver supports compositing,... Compiz, Native compositing in KDE, XFCE, LXDE, etc (and it seemed to be working before in LinuxMCE). What is LinuxMCE doing differently that you say compositing won't work in LinuxMCE???
Again, I'm not trying to be a P.I.TA., I really just want to know. I've configured X-server configs for a decade, so I could actually be a little help here... I've got motivation to help make this work, as 2/3rds of my finished network will be running on similar Intel grafics chipsets. And I solved graphics issues surrounding various Intel chipsets before. I've got old Xorg.config files that work laying around.
P.S. I'll give the new build a spin tonight and post the results.
The reason it was working before, and then didn't, is because I broke it trying to get to this point where it will work again, hopefully better than ever.
I was replying to your statement that it shouldn't matter to lmce. I did not say that compositing WOULDN'T work, I only meant to say that compositing does matter to the system. All that has changed on that front is detection and adding the newer libva-driver-i965. If you had compositing going, that is not an issue unless you added it yourself, which disrupts my ability to determine if our side is doing it right... which is the only reason I asked you not add any drivers on your side.
Our xorg.conf generation is complicated and the pieces each happen in several different places before coming together. I have nothing to indicate that it will NOT work for you, so as of yet I do not know that any help is needed. I try not to make changes to the process for a single chipset because it makes it more likely to break everything around it, and typically migrating to new distro's, the change becomes irrelevant except to cause problems. However if it is not particularly invasive, I am willing to generate specific modlines based on oddball cases.
Thus far, out of 8 Intel machines that never gotten to AVWizard before, all but the hd3000 have... and it is just too spanking new for Lucid, requiring natty backports and too much work in general to deal with.
I am sorry if I am curt with you. It seems like I try being nice to you, and you come back nasty at me. You begin posting in the thread, not reading where posde said:
A note: The built producing the new debs is currently under way. Please wait a bit. As soon as you see a version with 25659 at the end, you know you've got the right stuff. Also, we will have a 1004 snapshot iso with those changes. A big thanks to l3mce!
and then say
OK simply downloading the libva driver is a no go... I've re-run the script and will see if that does the trick,... But I doubt it...
... Yep,... Just like I figured avwizard fails with "failed to setup X" message in ASCII...
I have hundreds of hours in this. Your attitude is pessimistic and rude. Still I am polite. Then you come back, after not following directions, telling me it isn't going to work, not understanding that the new code has not been available until I posted saying it was ready (as I said I would do). I don't want to be unpleasant to you. It isn't constructive in any way. I don't want people kissing my ass either... but if we could find a happy medium between asshole and thankful, it would be much better for everyone.