distorted graphics

[ankit360]

i m using ubuntu 14.04 on my office desktop . now want to switch to fedora 22

but i m getting distorted graphics . desktop has intel g41 integrated graphics card

posting some screenshot

lspci output

00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM Controller (rev 03)
00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)

[dwbarros]

i m having the same problem with my intel g41 too.
i installed spin KDE e had the same problem.

[atreyu]

same problem here, too.

i recently did an update from F21 to F22. i get the fuzzy artifacts like the OP posted. I tried GNOME, GNOME Classic and MATE, all with the same effect. did a "dnf update" and rebooted, too.

i'd try the Intel Graphics stack (v1.0.8), but it is not released for F22 yet (still on F21).

$ uname -a;rpm -qv xorg-x11-drv-intel xorg-x11-server-Xorg;lspci|grep -i vga
Linux localhost 4.0.4-301.fc22.x86_64 #1 SMP Thu May 21 13:10:33 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
xorg-x11-drv-intel-2.99.917-9.20150520.fc22.x86_64
xorg-x11-server-Xorg-1.17.1-12.fc22.x86_64
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)

$ grep \]\ \(WW /var/log/Xorg.0.log -B1|grep intel -A1
[  2817.492] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20141121
[  2817.492] (WW) Falling back to old probe method for modesetting

[djl47]

Did any of you pick up this update:
xorg-x11-drv-intel.x86_64 2.99.917-9.20150520.fc22 @System
This landed on my systems yesterday evening.

[atreyu]

yeah, i'm running that ver. it's in my previous post.

[antikythera]

I got that. It fixed a blacked out and obscured popup issue in Chrome Browser for me. I had nothing on the scale of this corruption though.

[ankit360]

Did any of you pick up this update:
xorg-x11-drv-intel.x86_64 2.99.917-9.20150520.fc22 @System
This landed on my systems yesterday evening.

i have this update in my machine

[sumitbhardwaj]

Guys...have you tried using the wayland session? Just to see if its a problem with X only.

[atreyu]

I tried running GNOME on Wayland..for about 5 minutes. it was way too slow, and CPU usage spiked to 50%. in that 5 minutes i did not see the original problem, but that's hardly a test...

[dwbarros]

I solved the problem installing kernel 3.19.8-200.fc21.x86_64,
but i don't know if i'll have new problems.

[oconnell99]

Hi. The same problem here. I found this issue in F22 Alpha & Beta releases (Live and Install, Gnome or KDE). I report it at that moment in bugzilla.freedesktop and a few days ago in bugzilla.redhat.

I think its a xorg-intel or Wayland Experimental issue with some specific hardware and Intel graphic cards in this F22 release. F21 and prior releases worked fine!

You will find my reports in (see in this order):

in FreeDesktop.org

Bug 90127

------

in bugzilla.redhat.com

Bug 1225248 (My registered issue)

Bug 1225731 (Related)

Bug 1199890 (Maybe related, i have the same GDM flickered screen)

See U

[DBelton]

Same issue using LightDM and Xfce in Fedora 22.

Pretty much makes F22 unusable for me.

[sumitbhardwaj]

I tried running GNOME on Wayland..for about 5 minutes. it was way too slow, and CPU usage spiked to 50%. in that 5 minutes i did not see the original problem, but that's hardly a test...

The increased CPU usage definitely points towards non working 3D acceleration. While using Wayland/X, the compositor is not able to enable full GPU assisted 3D acceleration and falling back to SSE2 based CPU assisted acceleration using llvm pipe or something, don't know exactly how that works.

Anyway, the problem seems to be coming from the xorg driver. This needs to be reported properly and is quite serious.

Can any of you having the issue attach the output.txt file from below command:

sudo journalctl -b > output.txt

Do this after logging into Gnome and opening at least one application.

[ankit360]

The increased CPU usage definitely points towards non working 3D acceleration. While using Wayland/X, the compositor is not able to enable full GPU assisted 3D acceleration and falling back to SSE2 based CPU assisted acceleration using llvm pipe or something, don't know exactly how that works.

Anyway, the problem seems to be coming from the xorg driver. This needs to be reported properly and is quite serious.

Can any of you having the issue attach the output.txt file from below command:

sudo journalctl -b > output.txt

Do this after logging into Gnome and opening at least one application.

attaching log

https://drive.google.com/file/d/0BxR...ew?usp=sharing

[oconnell99]

The increased CPU usage definitely points towards non working 3D acceleration. While using Wayland/X, the compositor is not able to enable full GPU assisted 3D acceleration and falling back to SSE2 based CPU assisted acceleration using llvm pipe or something, don't know exactly how that works.

Anyway, the problem seems to be coming from the xorg driver. This needs to be reported properly and is quite serious.

Can any of you having the issue attach the output.txt file from below command:

sudo journalctl -b > output.txt

Do this after logging into Gnome and opening at least one application.

Im sure is xorg issue. If you read bug #90127 in bugzilla.freedesktop.org you will see the cause of problem:

"sna: Implement missing 9^10^11 swizzle mode"

" As found on my gm45..."

wrote Chris about this issue. In fact thiat missing swizzle modes refers to xorg-intel-drv package line codes.
Anyway, i opened that issue maybe one month ago, i talked with everyone implicated in Fedora team, and they know this issue. But now, im with yours, its a serious thing, because a lot of people installing F22 have that problem.

I provided my log in bugzilla.redhat and (obviously) now im using the latest Linux Mint to work with it. I think this will take a long time to dev team could solve the problem. I know Fedora team have a lot of work, but this issue is high rated priority. Anyway, i can reinstall F22 to post my output.

PS: Someone reply to me about kernel version and recommend to update at least version 4.0.4-301?
You can check that using uname -a command

Fedora 22, Fedora 22