This is a bug report on the intel gma500 There is a staging driver, psb_gfx and it conflicts with the poulsbo driver. CONFIG_STUB_POULSBO=m Conflicts with the (staging) psb_gfx CONFIG_DRM_GMA500=y If you build both drivers, either as modules or built in, as is default with most major distros, the graphics (psb_gfx) fails. You then have to manually remove the poulsbo driver and load the psb_gfx rmmod poulsbo modprobe psb_gfx And the psb_gfx module loads. What information can be provided to resolve this conflict ? Related bug reports https://bugs.launchpad.net/ubuntu/+source/linux/+bug/899244 https://bugzilla.redhat.com/show_bug.cgi?id=785053
Please see this comment "The poulsbo driver is just a stub module that enables the acpi video support for the panel brightness. This feature is already present inside the psb_gfx driver. The poulsbo module is loaded before the psb_gfx 'stealing' the pciid and not allowing the psb_gfx module to start up and open the framebuffer. that's why there is a conflict. I don't see any reason to preserve the stub poulsbo, psb_gfx already provides brightness support for every gma500/600 device. Is not useful also for the EMGD binary drivers provided by Intel." From https://bugs.launchpad.net/ubuntu/+source/linux/+bug/899244
The stub driver is on track to get removed, marking as fixed.