[Bug 1069031] Re: intel gma3600: X unable to start

[Launchpad Bug Tracker]

This bug was fixed in the package xorg-server - 2:1.13.0-0ubuntu7

---------------
xorg-server (2:1.13.0-0ubuntu7) raring; urgency=low

  [ Maarten Lankhorst ]
  * Add 233-xf86events-valgrind.patch to fix a xserver corruption
    when acpid is stopped before Xorg is.
    (LP: #1070481)
  * Add 235-composite-tracking.patch to fix exa corruption.
    (LP: #1010794)

  [ Bryce Harrington ]
  * Add 236-use-fbdev-for-poulsbo-oaktrail-medfield.patch: Never use Intel
    driver on Poulsbo/Oaktrail/Medfield.  Thanks to Matthias Klumpp.
    (LP: #1069031)
  * Add 237-dix-set-the-device-transformation-matrix.patch: Fix pointer
    jumping with absolute pointing device.  Initializes device
    transformation matrix to an identity matrix.  Thanks to a7x.
    (LP: #1041063)

  [ Tim Lunn ]
  * 500_pointer_barrier_thresholds.diff: Update to fix gaps above
    barriers at edge of screen
    (LP: #1073724)
 -- Bryce Harrington <bryce at ubuntu.com>   Fri, 16 Nov 2012 11:37:26 -0800

** Changed in: xorg-server (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1069031

Title:
  intel gma3600: X unable to start

Status in X.Org X server:
  New
Status in “xorg-server” package in Ubuntu:
  Fix Released
Status in “xorg-server” source package in Quantal:
  Triaged

Bug description:
  X is unable to start on a Acer AOD270 intel atom netbook  with a
  gma3600 chipset when the gma500_gfx kernel driver is loaded.

  (xorg.0.log)

  [    41.352] (EE) intel(0): [drm] Failed to detect GEM.  Kernel 2.6.28 required.
  [    41.352] (EE) intel(0): Failed to become DRM master.
  [    41.352] (II) UnloadModule: "intel"
  [    41.353] (EE) Screen(s) found, but none have a usable configuration.
  [    41.353] Fatal server error:

  Workaround is to blacklist  the gma500_glx module, which  allows X to
  start by falling back to the vesa FB driver.

  Applying the patch described here fixes the problem without the need
  to blacklist.

  http://bugzillafiles.novell.org/attachment.cgi?id=499509

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: i386
  Date: Sat Oct 20 11:35:10 2012
  InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to quantal on 2012-10-19 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1069031/+subscriptions