Annoying Screen Flickering with Intel GM45 Chipset

[SteveRiley]

Do yourself a favor... change your habit away from apt-get upgrade and instead use apt-get dist-upgrade.

Anyway...now that these drivers are in fact installed, is the problem still there after a reboot? Can I see your Xorg.0.log now?

Oh, and a favor for me... when you post the output of a command like the apt-cache policy might I urge you to use the "[ CODE ]" tag rather than "[ QUOTE ]"? Preserving indents helps to parse the text. Thanky.

[PJK]

Okay, what the hell. I swear to God, I added that repo, and did update and upgrade. I re-added it though, did update, then upgrade, which returned:

The following packages have been kept back:
libgl1-mesa-dri xserver-xorg-core xserver-xorg-input-evdev xserver-xorg-input-mouse xserver-xorg-input-synaptics xserver-xorg-input-vmmouse xserver-xorg-video-ati
xserver-xorg-video-cirrus xserver-xorg-video-fbdev xserver-xorg-video-intel xserver-xorg-video-mach64 xserver-xorg-video-mga xserver-xorg-video-neomagic
xserver-xorg-video-nouveau xserver-xorg-video-openchrome xserver-xorg-video-qxl xserver-xorg-video-r128 xserver-xorg-video-radeon xserver-xorg-video-s3
xserver-xorg-video-savage xserver-xorg-video-siliconmotion xserver-xorg-video-sis xserver-xorg-video-sisusb xserver-xorg-video-tdfx xserver-xorg-video-trident
xserver-xorg-video-vesa xserver-xorg-video-vmware
0 upgraded, 0 newly installed, 0 to remove and 27 not upgraded.

Doing dist-upgrade downloaded all those 27 packages, but I swear I had em. Next answer:

xserver-common:
Installed: 2:1.12.1+git20120502+server-1.12-branch.ed33772a-0ubuntu0ricotz~precise
Candidate: 2:1.12.1+git20120502+server-1.12-branch.ed33772a-0ubuntu0ricotz~precise
Version table:
*** 2:1.12.1+git20120502+server-1.12-branch.ed33772a-0ubuntu0ricotz~precise 0
500 http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu/ precise/main amd64 Packages
100 /var/lib/dpkg/status
2:1.11.4-0ubuntu10.1 0
500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages
2:1.11.4-0ubuntu10 0
500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
xserver-xorg-core:
Installed: 2:1.12.1+git20120502+server-1.12-branch.ed33772a-0ubuntu0ricotz~precise
Candidate: 2:1.12.1+git20120502+server-1.12-branch.ed33772a-0ubuntu0ricotz~precise
Version table:
*** 2:1.12.1+git20120502+server-1.12-branch.ed33772a-0ubuntu0ricotz~precise 0
500 http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu/ precise/main amd64 Packages
100 /var/lib/dpkg/status
2:1.11.4-0ubuntu10.1 0
500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages
2:1.11.4-0ubuntu10 0
500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
xserver-xorg-video-intel:
Installed: 2:2.19.0+git20120501.7e09babb-0ubuntu0sarvatt~precise
Candidate: 2:2.19.0+git20120501.7e09babb-0ubuntu0sarvatt~precise
Version table:
*** 2:2.19.0+git20120501.7e09babb-0ubuntu0sarvatt~precise 0
500 http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu/ precise/main amd64 Packages
100 /var/lib/dpkg/status
2:2.17.0-1ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
jan@Latitude:/var/log$

[SteveRiley]

Hm. Are you sure you're using the Xorg-Edgers PPA? Your log file shows X Server version 1.11.3 and Intel driver 2.17.0. The Xorg-Edgers repo currently has X Server 1.12.1 and Intel driver 2.19.0.

Let me see the output of:

apt-cache policy xserver-common xserver-xorg-core xserver-xorg-video-intel

I have another suggestion, but let's wait for just a moment.

[PJK]

Attached.

Xorg.0.txt

[SteveRiley]

Whoa, wait a sec...why is the VESA driver loading, rather than the Intel driver? Hrm... slap that entire log file up here, please. Lemme take a look.

[PJK]

I believe so, weird it would choose 1280x768 since:

[ 15.282] (II) VESA(0): Supported detailed timing:
[ 15.282] (II) VESA(0): clock: 69.3 MHz Image Size: 331 x 2070 mm
[ 15.282] (II) VESA(0): h_active: 1280 h_sync: 1328 h_sync_end 1352 h_blank_end 1416 h_border: 0
[ 15.282] (II) VESA(0): v_active: 800 v_sync: 803 v_sync_end 809 v_blanking: 816 v_border: 0
[ 15.282] (II) VESA(0): Supported detailed timing:
[ 15.282] (II) VESA(0): clock: 46.2 MHz Image Size: 331 x 2070 mm
[ 15.282] (II) VESA(0): h_active: 1280 h_sync: 1328 h_sync_end 1352 h_blank_end 1416 h_border: 0
[ 15.282] (II) VESA(0): v_active: 800 v_sync: 803 v_sync_end 809 v_blanking: 816 v_border: 0
[ 15.282] (II) VESA(0): X397H€154WX5
[ 15.282] (II) VESA(0): Unknown vendor-specific block 0
[ 15.282] (II) VESA(0): EDID (in hex):
[ 15.282] (II) VESA(0): 00ffffffffffff00320c000000000000
[ 15.282] (II) VESA(0): 00120103902115780ab7859959538d27
[ 15.282] (II) VESA(0): 25505400000001010101010101010101
[ 15.282] (II) VESA(0): 010101010101121b0088502010303018
[ 15.282] (II) VESA(0): 36004bcf1000001b0e12008850201030
[ 15.282] (II) VESA(0): 301836004bcf1000001b000000fe0058
[ 15.282] (II) VESA(0): 33393748803135345758350a00000000
[ 15.282] (II) VESA(0): 0026343e446489a4ff01010a20200018
[ 15.282] (II) VESA(0): EDID vendor "LPL", prod id 0
[ 15.282] (II) VESA(0): EDID quirk: Detailed timings give vertical size in cm.
[ 15.282] (II) VESA(0): Printing DDC gathered Modelines:
[ 15.282] (II) VESA(0): Modeline "1280x800"x0.0 69.30 1280 1328 1352 1416 800 803 809 816 +hsync -vsync (48.9 kHz)
[ 15.282] (II) VESA(0): Modeline "1280x800"x0.0 46.22 1280 1328 1352 1416 800 803 809 816 +hsync -vsync (32.6 kHz)

[SteveRiley]

Hey, sounds better than anything so far! Alas, "nomodeset" is not so ideal, because now you're relying on X to set video modes. KMS (kernel mode setting) is the way of the future.

Take a look at your latest /var/log/Xorg.0.log. Do you see any probe attempts for 1200x800?

[PJK]

Right, removed custom kernels, using Xedgers drivers, changed "i915.powersave=0" to "nomodeset". NO SCREEN FLICKER 2 REBOOTS IN A ROW!

Another problem, I'm running at 1280x768 as opposed to 1280x800, so screen is rather blurry, and my cursor occasionally disappears. xrandr -s 1280x800 says 1280x800 not found in modes.

[SteveRiley]

PS: Doing sudo update-grub still maintains the custom kernel, right?

Yup, that kernel will stick around unless you delete it, and because its version number is higher, it will remain the default even when 3.2 is updated.

If you want to get rid of it:

dpkg -P linux-image-3.4.0-994-generic linux-headers-3.4.0-994 linux-headers-3.4.0-994-generic

[SteveRiley]

One last thing, I'm gonna add Xedgers repos and upgrade to their drivers, see what happens.

Ah, I thought you had still kept that. There was an update just today in Edgers, so let's hope for the best!

[PJK]

Yeah tell me about it bro. At this point, I think I'm just gonna deal with the occasional flickering, I've installed 11.10 and within 5 minutes I've gotten multiple crashes, and even after installing all upgrades I couldn't open Muon Software Center because it crashed on launch and I can't have that in a development system. Kubuntu 12.04 is super stable, so like I said, I'll just stick with it, and I'm hoping the issue gets resolved down the road.

PS: Doing sudo update-grub still maintains the custom kernel, right?

EDIT: Yeah it does, believe it or not, the flickering is actually worse with the custom kernel. It actually flashes white and black now as opposed to just white. One last thing, I'm gonna add Xedgers repos and upgrade to their drivers, see what happens.

[SteveRiley]

Waaah! I'm totally stumped! :mad:

[PJK]

Wait now, before I installed the kernels I realized I haven't performed any upgrades yet, so I just did apt-get update && apt-get upgrade, when finished, I did apt-get dist-upgrade and it installed new kernels:

Setting up linux-image-generic (3.2.0.24.26) ...
Setting up linux-generic (3.2.0.24.26) ...
Setting up linux-headers-3.2.0-24 (3.2.0-24.37) ...
Setting up linux-headers-3.2.0-24-generic (3.2.0-24.37) ...
Setting up linux-headers-generic (3.2.0.24.26) ...

Rebooting Now.
Rebooted, same sh*t.

Results of dpkg command for custom kernels:

jan@Latitude:~/Downloads/Custom Intel Kernel$ sudo dpkg -i linux-*.deb
[sudo] password for jan:
Selecting previously unselected package linux-headers-3.4.0-994.
(Reading database ... 115542 files and directories currently installed.)
Unpacking linux-headers-3.4.0-994 (from linux-headers-3.4.0-994_3.4.0-994.201205020451_all.deb) ...
Selecting previously unselected package linux-headers-3.4.0-994-generic.
Unpacking linux-headers-3.4.0-994-generic (from linux-headers-3.4.0-994-generic_3.4.0-994.201205020451_amd64.deb) ...
Selecting previously unselected package linux-image-3.4.0-994-generic.
Unpacking linux-image-3.4.0-994-generic (from linux-image-3.4.0-994-generic_3.4.0-994.201205020451_amd64.deb) ...
Done.
Setting up linux-headers-3.4.0-994 (3.4.0-994.201205020451) ...
Setting up linux-headers-3.4.0-994-generic (3.4.0-994.201205020451) ...
Setting up linux-image-3.4.0-994-generic (3.4.0-994.201205020451) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.4.0-994-generic /boot/vmlinuz-3.4.0-994-generic
update-initramfs: Generating /boot/initrd.img-3.4.0-994-generic
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.4.0-994-generic /boot/vmlinuz-3.4.0-994-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 3.4.0-994-generic /boot/vmlinuz-3.4.0-994-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.4.0-994-generic /boot/vmlinuz-3.4.0-994-generic
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.4.0-994-generic
Found initrd image: /boot/initrd.img-3.4.0-994-generic
Found linux image: /boot/vmlinuz-3.2.0-24-generic
Found initrd image: /boot/initrd.img-3.2.0-24-generic
Found linux image: /boot/vmlinuz-3.2.0-23-generic
Found initrd image: /boot/initrd.img-3.2.0-23-generic
Found memtest86+ image: /boot/memtest86+.bin
done

I'm assuming everything's just jolly, rebooting... yet again.
Rebooted, same effect. Gonna try adding i915.powersave=0 to GRUB again.

[SteveRiley]

Download these three files:

* http://kernel.ubuntu.com/~kernel-ppa...0451_amd64.deb
* http://kernel.ubuntu.com/~kernel-ppa...0451_amd64.deb
* http://kernel.ubuntu.com/~kernel-ppa...020451_all.deb

Then open a console window, go to your download directory, and run:

sudo dpkg -i linux-*.deb

This will not replace your existing kernel, but it will alter your GRUB menu so that this kernel is the default. After installation, reboot. Then let us know whether the flickering is still there.

[PJK]

I would be running either one, I literally just finished installing Kubuntu 11.10, but it's not running so good. 2nd install and I can't open Software Center, crashes on open, I get some "Waiting for Disk" message before login... etc, BUT no flickering. Anyway, yeah let me call it, 64bit, and no, I have never manually installed a kernel.

EDIT: Okay, back in Kubuntu 12.04 64bit, what do I need to do now dude? I'm clueless.