The PowerVR Poulsbo, Oaktrail, Medfield, CDV are detected as Intel manufactured chips, so xserver chooses to try booting -intel on them. This won't work, and led to boot failures in the past. The -intel driver has been fixed to bail out when it detects these, but xserver really should not be attempting to use -intel in these cases. The attached patch was originally created by Stefan Dirsch for OpenSUSE. It makes xserver use fbdev for these devices. We have included it in our stable release (Ubuntu "quantal" 12.10) since December.
Created attachment 74450 [details] [review] 236-use-fbdev-for-poulsbo-oaktrail-medfield.patch This is the patch we currently include in Ubuntu.
Comment on attachment 74450 [details] [review] 236-use-fbdev-for-poulsbo-oaktrail-medfield.patch Review of attachment 74450 [details] [review]: ----------------------------------------------------------------- Will this patch work for SGX545/powervr boards ?
commit 5e91054aa070ea09b61325b7ec479d767b02730e Author: Bryce Harrington <bryce@canonical.com> Date: Fri Feb 8 15:56:01 2013 -0800 xfree86: Use fbdev/vesa driver on Oaktrail, Medfield, CDV rather than -intel Instead of defaulting to -intel for Oaktrail, Medfield, and CDV chips, default to -fbdev. For Poulsbo (only), attempt to use -psb if it's installed, and fallback to fbdev otherwise. All other Intel chips should use -intel. This fixed an issue where -intel would load on these chips and cause a boot failure. Newer -intel drivers avoid the boot hang, but it's still the wrong driver to load, so why take chances. The patch was originally created by Stefan Dirsch for OpenSUSE. We have included it in our stable release (Ubuntu "quantal" 12.10) since December. ref: https://bugzilla.novell.com/show_bug.cgi?id=772279 ref: https://bugs.launchpad.net/ubuntu/+bug/1069031 Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=60514 Signed-off-by: Bryce Harrington <bryce@canonical.com> Signed-off-by: Keith Packard <keithp@keithp.com>
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.