Display scrambled with Intel GMA HD graphics after update

[CirclingTheSun]

I'm running 64bit Ubuntu 11.10 on my Asus UL20FT A1 laptop (http://www.newegg.com/Product/Product.aspx?Item=N82E16834220773) . After upgrading my kernel from 3.0.0.14 to 3.0.015 I saw the following noise on my display following the grub screen: http://imgur.com/a/DCdNy

Upgrading to the pre release 3.0.0.16 kernel did not resolve the issue. The display works perfectly when booting the 3.0.0.14 kernel.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-16-generic 3.0.0-16.28
ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
Uname: Linux 3.0.0-16-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: rickert 1804 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf4000000 irq 43'
   Mixer name : 'Intel IbexPeak HDMI'
   Components : 'HDA:10ec0269,10431133,00100100 HDA:80862804,80860101,00100000'
   Controls : 18
   Simple ctrls : 10
Date: Thu Feb 2 02:29:46 2012
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=f078707a-dc15-405c-af15-541bcbac3a1a
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110913)
MachineType: ASUSTeK Computer Inc. UL20FT
ProcEnviron:
 LANGUAGE=en_ZA:en
 PATH=(custom, user)
 LANG=en_ZA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-16-generic root=UUID=0f96003e-52d5-45cf-9a5b-f98f957bdba3 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-16-generic N/A
 linux-backports-modules-3.0.0-16-generic N/A
 linux-firmware 1.60.1
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 217
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UL20FT
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.:bvr217:bd06/22/2010:svnASUSTeKComputerInc.:pnUL20FT:pvr1.0:rvnASUSTeKComputerInc.:rnUL20FT:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: UL20FT
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.3 kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.3-rc2 fixed the issue, the tag would be: 'kernel-fixed-upstream-v3.3-rc2'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[CirclingTheSun (circlingthesun)]

Cool, I installed and booted the upstream 3.3-rc2 kernel without any problems.

[Julian Wiedmann (jwiedmann)]

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

[mabawsa (mabawsa)]

I had this issue adding i915.lvds_use_ssc=0 to the boot worked great. Marking this as a duplicate.