Comment 16 for bug 899244

Hi Bodhi,

Apologies for this still being an issue with Beta-1. As you've noticed, no solution has been committed at the moment.

I'd actually committed the original idea of completely disabling the poulsbo driver. At the time the team was physically together for a face to face meeting and one of the other Ubuntu kernel team developers voiced their concern of completely disabling the poulsbo driver. In the event the psb_gfx driver was not sufficiently working (as it is/was a staging driver) we would prevent a user from falling back to use the poulsbo driver as it would be completely disabled. By blacklisting the poulsbo driver in module-init-tools, they at least still have the option to manually load the poulsbo driver. Unfortunately this conversation took place face to face so there wasn't anything written/documented for me to point you at.

I completely agree that if there are issues with either driver, we should be notifying upstream.

If you could point me to your LKML thread about this that would be great. Especially if there is a newer patch upstream with

Also, just curious what the specific vendor:device id is for your GMA500? Is it's either of the 8086:8108 or 8086:8109 which overlaps with both drivers? If so, I think I could have a much stronger argument to convince the other devs on the team that completely disabling the poulsbo driver in favor of psb_gfx should be realitvely safe as I'd have your test confirmation to prove it.

Thanks. I do want to get this fixed one way or another before Beta-2.