Bug 1331060

Summary: Xorg failed to load glamor module (eglInitialize() failed) on RADEON VERDE chipset
Product: [Fedora] Fedora Reporter: Helmut Schlattl <helmut.schlattl>
Component: xorg-x11-serverAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 25CC: xgl-maint
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-21 08:27:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Output of 'journalctl -b _COMM=gdm-x-session'
none
Output of 'lspci -vvv -s 01:00.0' none

Description Helmut Schlattl 2016-04-27 15:04:40 UTC
Created attachment 1151441 [details]
Output of 'journalctl -b _COMM=gdm-x-session'

Description of problem:
The 2D graphics acceleration on radeon VERDE card (ChipID = 0x683d) does not work, since it fails to load the glamor module.

Version-Release number of selected component (if applicable):
xorg-x11-server-Xorg-1.18.3-1.fc23
mesa-dri-drivers-11.1.0-2.20151218.fc23
mesa-libEGL-11.1.0-2.20151218.fc23

How reproducible:
ALways

Steps to Reproduce:
1. Boot into gdm
2.
3.

Actual results:
No 2D graphics acceleration

Expected results:
2D graphics acceleration

Additional info:
The critical lines in the X-log file is probably:
(EE) RADEON(0): eglInitialize() failed
(EE) RADEON(0): glamor detected, failed to initialize EGL.

There is no xorg.conf, only a 00-keyboard.conf in /etc/X11/xorg.conf.d with soley a "InputClass' section.

Output of 'lspci | grep VGA':
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X]

Comment 1 Helmut Schlattl 2016-04-27 15:05:47 UTC
Created attachment 1151442 [details]
Output of 'lspci -vvv -s 01:00.0'

Comment 2 Fedora End Of Life 2016-11-25 07:29:14 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2016-12-20 20:09:44 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.

Comment 4 Helmut Schlattl 2017-03-23 09:04:33 UTC
Recently upgraded to Fedora 25, where the problem still exists. Thus, reopen the bug.

Comment 5 Fedora End Of Life 2017-11-16 19:51:26 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 6 Helmut Schlattl 2017-11-21 08:27:23 UTC
I finally got the reason for the failure. 

I had libgbm.so.1 linked to an outdated version. Must be some remnant of old days. So it was not a bug, but a problem with my installation. 

After removing the link and reinstalling mesa-libgbm glamor is now operating.