Description of problem: Severe diagonal tearing of the display when using Fedora 22 beta on an Asus W2JC laptop (ATI Radeon Mobility X1600 RV530/M56-P). The open source 'radeon' driver is being used.The cursor appears normal, only the desktop itself is corrupt. The torn display reacts to mouse events producing similarly corrupted and unreadable drop down menus. Removing wayland by disabling it in /etc/gdm/custom.conf results in a normal, uncorrupt X11 display. Version-Release number of selected component (if applicable): gnome shell 3.16.1-1.fc22.i686 How reproducible: Always Steps to Reproduce: 1. Boot Fedora 22 beta into the default login screen 2. 3. Actual results: Corrupted display Expected results: Uncorrupted display. Additional info: [ 3.150140] [drm] radeon kernel modesetting enabled. [ 3.150280] fb: switching to radeondrmfb from VESA VGA [ 3.151887] radeon 0000:01:00.0: VRAM: 256M 0x0000000000000000 - 0x000000000FFFFFFF (256M used) [ 3.151894] radeon 0000:01:00.0: GTT: 512M 0x0000000010000000 - 0x000000002FFFFFFF [ 3.155354] [drm] radeon: 256M of VRAM memory ready [ 3.155358] [drm] radeon: 512M of GTT memory ready. [ 3.157710] [drm] radeon: power management initialized [ 3.172025] [drm] radeon: 1 quad pipes, 2 z pipes initialized. [ 3.174130] radeon 0000:01:00.0: WB enabled [ 3.174140] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000010000000 and cpu addr 0xf68f1000 [ 3.174154] radeon 0000:01:00.0: radeon: MSI limited to 32-bit [ 3.174212] radeon 0000:01:00.0: radeon: using MSI. [ 3.174250] [drm] radeon: irq initialized. [ 3.174721] [drm] radeon: ring at 0x0000000010001000 [ 3.178245] [drm] Radeon Display Connectors [ 3.579491] fbcon: radeondrmfb (fb0) is primary device [ 3.992949] radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device [ 3.992953] radeon 0000:01:00.0: registered panic notifier [ 3.998171] [drm] Initialized radeon 2.41.0 20080528 for 0000:01:00.0 on minor 0
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.