Take a look at https://launchpad.net/~xorg-edgers/+archive/ppa

*ppa:xorg-edgers/ppa*




2011/2/3 aftertaf <email address hidden>

> Do you have the apt:add link?
> On Feb 3, 2011 9:31 AM, "Oddbjørn Hansen" <email address hidden>
> wrote:
> >
> > I have an E6410 ATG with i7-640M running Maveric with kernel and xorg
> from
> > xorg-edgers. The 2.6.38-1 kernel seems to solve all the addressed issues.
> >
> >
> > Oddbjørn Hansen
> >
> >
> >
> > 2011/2/2 Chris Halse Rogers <email address hidden>
> >
> > > Backporting the fix as an SRU to the Lucid or Maverick kernels is
> > > unlikely to fly, as there's simply been too many patches over too many
> > > kernel releases for it to be easy to extract a minimal safe fix.
> > >
> > > There should be no problems with using the Natty kernel on an otherwise
> > > Lucid or Maverick system, though, and for Lucid at least I think this
> > > should be possible with the lts-backport kernels.
> > >
> > > --
> > > You received this bug notification because you are a direct subscriber
> > > of the bug.
> > > https://bugs.launchpad.net/bugs/561802
> > >
> > ...
> >
> > --
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> > https://bugs.launchpad.net/bugs/561802
> >
> > Title:
> >  [i915] blank screen on Latitude E6410 (NOT E6510)
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/561802
>
> Title:
>  [i915] blank screen on Latitude E6410 (NOT E6510)
>
> Status in The Linux Kernel:
>  Fix Released
> Status in “linux” package in Ubuntu:
>  Triaged
> Status in “linux” source package in Lucid:
>  In Progress
> Status in “linux” source package in Maverick:
>  New
>
> Bug description:
>  Binary package hint: xorg
>
>  NOTE: The E6410 and E6510 have different hardware.  There's a bug with
>  similar *symptoms* but a *different cause* on E6510+intel hardware,
>  which is bug #600453.
>
>  During installation, bootup (plymouth) and while inside X, screen
>  remains blank. Switching VTs yields no results (screen remains blank).
>
>  This was done with today's daily desktop image, amd64: 10.04
>  (20100412).
>
>  I've been able to isolate the issue to possibly somewhere in
>  modesetting with the i915 driver, here are the tested cases:
>
>   - Disabling modesetting with 'nomodeset' as a kernel parameter: boot
> messages visible in 'verbose', otherwise nothing on screen, X remains blank.
>   - Disabling modesetting with 'i915.modeset=0' as a kernel parameter:
> results in a kernel oops, after briefly showing a simple "text" splash and
> showing corruption of that splash screen. X clearly never comes up,
> caps/scroll/num blink.
>   - Disabling modesetting with 'nomodeset' and switching X drivers to
> 'vesa': nothing on screen during boot, up to a working, visible desktop.
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 10.04
>  Package: xorg 1:7.5+5ubuntu1
>  ProcVersionSignature: Ubuntu 2.6.32-20.29-generic 2.6.32.11+drm33.2
>  Uname: Linux 2.6.32-20-generic x86_64
>  Architecture: amd64
>  Date: Mon Apr 12 16:14:04 2010
>  DkmsStatus: Error: [Errno 2] No such file or directory
>  GdmLog:
>   Error: command ['gksu', '-D', 'Apport', '--', 'cat',
> '/var/log/gdm/:0.log'] failed with exit code 1:
>   (gksu:2847): Gtk-WARNING **: cannot open display: localhost:10.0
>  GdmLog1:
>   Error: command ['gksu', '-D', 'Apport', '--', 'cat',
> '/var/log/gdm/:0.log.1'] failed with exit code 1:
>   (gksu:2851): Gtk-WARNING **: cannot open display: localhost:10.0
>  GdmLog2:
>   Error: command ['gksu', '-D', 'Apport', '--', 'cat',
> '/var/log/gdm/:0.log.2'] failed with exit code 1:
>   (gksu:2855): Gtk-WARNING **: cannot open display: localhost:10.0
>  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100412)
>  Lsusb:
>   Bus 002 Device 003: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure
> Applications Processor
>   Bus 002 Device 002: ID 8087:0020
>   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   Bus 001 Device 002: ID 8087:0020
>   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>  MachineType: Dell Inc. Latitude E6410
>  PccardctlIdent:
>   Socket 0:
>     no product info available
>  PccardctlStatus:
>   Socket 0:
>     no card
>  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-20-generic
> root=UUID=be2ee00c-b05e-4412-84d5-fc61a62388de ro verbose
>  ProcEnviron:
>   SHELL=/bin/bash
>   LANG=en_US.UTF-8
>  SourcePackage: xorg
>  Symptom: display
>  Xrandr: Error: command ['xrandr', '--verbose'] failed with exit code 1:
> Can't open display localhost:10.0
>  dmi.bios.date: 01/30/2010
>  dmi.bios.vendor: Dell Inc.
>  dmi.bios.version: X51
>  dmi.board.name: RAMDEL
>  dmi.board.vendor: Dell Inc.
>  dmi.board.version: 0001
>  dmi.chassis.type: 9
>  dmi.chassis.vendor: Dell Inc.
>  dmi.modalias:
> dmi:bvnDellInc.:bvrX51:bd01/30/2010:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rnRAMDEL:rvr0001:cvnDellInc.:ct9:cvr:
>  dmi.product.name: Latitude E6410
>  dmi.product.version: 0001
>  dmi.sys.vendor: Dell Inc.
>  glxinfo: Error: [Errno 2] No such file or directory
>  setxkbmap: Error: command ['setxkbmap', '-print'] failed with exit code
> 255: Cannot open display "localhost:10.0"
>  system:
>   distro:             Ubuntu
>   codename:           lucid
>   architecture:       x86_64
>   kernel:             2.6.32-20-generic
>  xdpyinfo: Error: command ['xdpyinfo'] failed with exit code 1: xdpyinfo:
>  unable to open display "localhost:10.0".
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/linux/+bug/561802/+subscribe
>