Bad screen flicker and screen offset in kernel 3.0.0-15-generic and later

Bug #955571 reported by Drew
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

NOTE: I tried to put the kernel in the package box above but it won't accept that, I DO know where the problem is, it is in kernel 3.0.0.-15.

Using an Asus ep121 (slate). Problem arose after auto update to kernel 3.0.0-15-generic.
Screen flickers badly, and is "rotated" to the right abut 1cm - by rotated I mean contents shifted right and the right hand edge appears at the left of the screen.
I noted display problems being reported with other machines where advice was given that 3.0.0-17 would contain a fix, so waited for 3.0.0-17 to be available, but both 3.0.0-16-generic and 3.0.0-17 do not fix this particular problem.
Using 3.0.0-14-generic still works fine, so it is definately in the kernel. Note also that the sceen is stable and not offset during boot while grub is displayed.
Attached is a photo of the screen (a software screen shot shows how the screen should look not how it is). Apologies the shot is not great, but you can see the left hand unity panel shifted right and the far right edge of the screen displayed to the left of that. Photo of curse doesn't show the flicker which is constant random movement about 1/2 mm. The touch screen is in the proper place, which means that the touch and vision are about 1cm apart.
Thanks heaps if you are able to do something about this problem.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: xorg 1:7.6+7ubuntu7.1
ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13
Uname: Linux 3.0.0-15-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 1.23-0ubuntu4
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,decor,vpswitch,mousepoll,regex,resize,compiztoolbox,animation,gnomecompat,imgpng,move,workarounds,snap,grid,unitymtgrabhandles,wall,place,fade,session,expo,ezoom,scale,unityshell]
CompositorRunning: None
Date: Thu Mar 15 09:04:28 2012
DistUpgraded: Fresh install
DistroCodename: oneiric
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:1be2]
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: ASUSTeK Computer Inc. EP121
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-15-generic root=UUID=f70ce386-0181-4584-b0f8-50604b167d90 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/26/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 501
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: EP121
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr501:bd01/26/2011:svnASUSTeKComputerInc.:pnEP121:pvr1.0:rvnASUSTeKComputerInc.:rnEP121:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: EP121
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu6.1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.26-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1

Revision history for this message
Drew (dkrix) wrote :
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

hello
If you have customized your kernel we cannot consider this a bug, so please refere to bugzilla
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Drew (dkrix) wrote : Re: [Bug 955571] Re: Bad screen flicker and screen offset in kernel 3.0.0-15-generic and later

Fabio,

Thanks for the time to reply, but I most certainly did NOT customise
anything. I booted into the mentioned kernels using the normal grub
system, choosing the latest or the recent ones from the standard, system
generated, grub boot menu.

The kernel numbered 3.0.0-14 provides a stable screen, the next upgrade
provided automatically through the standard upgrade system were 3.0.0-15
and 3.0.0-16 and these both fail to provide a stable screen.

The one numbered 17 was obtained from one of the Ubuntu websites and it
was primarily designed to fix someone else's screen bug in 3.0.0-14, I
just mentioned that to show that it was evidently not the same bug.
Please ignore any mention of 3.0.0-17 if that is the worry.

Please be assured I have not recoded, recompiled or otherwise altered
the kernels in any way, just let the automated system install them.

Drew

On 15/03/12 20:26, Fabio Marconi wrote:
> hello
> If you have customized your kernel we cannot consider this a bug, so please refere to bugzilla
> ---
> Ubuntu Bug Squad volunteer triager
> http://wiki.ubuntu.com/BugSquad
>
> ** Changed in: ubuntu
> Status: New => Incomplete
>

Revision history for this message
Drew (dkrix) wrote :

The kernels mentioned were not customised, not changed in any way. 3.0.0-14, 3.0.0-15 and 3.0.0-16 were downlaoed and installed automatically by the normal ubuntu update mechanism. Ignore 3.0.0-17, I just mentioned that to show it did not fix my bug (it was designed for someone else's) - I got that one from one of the ubuntu fix websites, perhaps it is not an official one?? But 3.0.-17 has nothing to do with the problem, it just doesn't fix it either.
The bug appeared in the stock standard, automatically provided, 3.0.0-15, and that is the basic issue.

Revision history for this message
Drew (dkrix) wrote :

Just noted that the screen photo attached to the original report evidently didn't make it for some reason. I'll attach it again.

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Hello,
sorry for misunderstood.
Have you got the possibility to test the new build of Precise in a live session to see if this bug is present witht he latest kernel ?
http://cdimage.ubuntu.com/daily-live/current/
Thanks
Fabio

---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

affects: ubuntu → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Incomplete → New
status: New → Incomplete
tags: removed: needs-reassignment
Revision history for this message
Julian Wiedmann (jwiedmann) wrote :

Might be bug 925350 - could you try booting with i915.lvds_use_ssc=0 on the command line (comment #35 in that bug)?

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Drew (dkrix) wrote :

thanks heaps for these suggestions - i'll try them as soon as i can.

Revision history for this message
Drew (dkrix) wrote :

Thanks, Fabio: the machine runs fine from a boot USB with Precise from the site you suggested.
(Joseph, I'll look into the 925350 next).

Revision history for this message
Drew (dkrix) wrote :

Joseph: also 3.0.0-15-generic works with the i915.lvds_use_ssc=0 added into grub.
Thanks you guys, sorry for all the trouble; I guess it was the same as that previous bug, I did try to check out previous recorded bugs but the other screen problems sounded so different.

Revision history for this message
Julian Wiedmann (jwiedmann) wrote :

Good to hear - so let's mark this one as duplicate. You should receive further messages from that bug when a fixed kernel is ready for testing, until then just keep using the boot parameter.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.