upgrade from 2.6.31-2.17 leads to heavy screen flickering e.g. in gnome-terminal

Bug #401399 reported by DSHR
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Using a fully updates karmic on lenovo X60S mit kms enabled leads to screen flickering espacially noticable during scroll operations in gnome-terminal and firefox. Using 2.6.31-2 resolves the problem for me. Compiz effects are enabled.

# apt-cache policy linux-image-2.6.31-2-generic
linux-image-2.6.31-2-generic:
  Installiert: 2.6.31-2.17
  Kandidat: 2.6.31-2.17
  Versions-Tabelle:
 *** 2.6.31-2.17 0
        100 /var/lib/dpkg/status
# apt-cache policy linux-image-2.6.31-3-generic
linux-image-2.6.31-3-generic:
  Installiert: 2.6.31-3.19
  Kandidat: 2.6.31-3.19
  Versions-Tabelle:
 *** 2.6.31-3.19 0
        500 http://de.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

Revision history for this message
Matt Drake (mattduckman) wrote :

I also experience this problem in the newest kernel, and can confirm that it's not present in kernel 2.6.31-2.17.

Revision history for this message
Matt Drake (mattduckman) wrote :
Revision history for this message
Matt Drake (mattduckman) wrote :
Revision history for this message
Matt Drake (mattduckman) wrote :
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
DSHR (s-heuer) wrote :

The new 2.6.31-4 Kernel does not solve the problem ...

$ apt-cache policy linux-image-2.6.31-4-generic
linux-image-2.6.31-4-generic:
  Installiert: 2.6.31-4.22
  Kandidat: 2.6.31-4.22
  Versions-Tabelle:
 *** 2.6.31-4.22 0
        500 http://de.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

Revision history for this message
Matt Drake (mattduckman) wrote :

Right, the problem still exists.
But I discovered that it's caused by KMS, so booting with 'nomodeset' in the kernel config line is a good workaround.

Revision history for this message
DSHR (s-heuer) wrote :

Still not fixed in 2.6.31-5 ...

I can switch from the default 85Hz refresh rate to 75Hz to fix the problem.

Revision history for this message
DSHR (s-heuer) wrote :

Fixed with 2.6.31-6. Thanks a lot!

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.