Bug 1478733 - Hardware accelerated OpenGL fails on Intel Sandy Bridge IGP
Hardware accelerated OpenGL fails on Intel Sandy Bridge IGP
Status: NEW
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-modesetting (Show other bugs)
x86_64 Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Dave Airlie
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2017-08-06 12:53 EDT by Gerik Huland
Modified: 2018-05-03 04:23 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Gerik Huland 2017-08-06 12:53:50 EDT
Description of problem:
After updating from F25 to F26 modesetting driver is default now. Glamor initialization fails.

Version-Release number of selected component (if applicable):

How reproducible:
standard Xorg settings, no files in /etc/X11/xorg.conf*
Mobile Platform, Dell XPS 15
Intel Core i5-2520M (Sandy Bridge)
Dual Graphics:
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT 540M] (rev ff)
Nvidia device disabled by bbswitch

Steps to Reproduce:
1. startx, xinit, start any display manager
2. glxinfo shows software renderer

Actual results:
[  6661.966] (II) Loading sub module "glamoregl"
[  6661.966] (II) LoadModule: "glamoregl"
[  6661.966] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
[  6661.967] (II) Module glamoregl: vendor="X.Org Foundation"
[  6661.968]    compiled for 1.19.3, module version = 1.0.0
[  6661.968]    ABI class: X.Org ANSI C Emulation, version 0.4
[  6661.968] (II) glamor: OpenGL accelerated X.org driver based.
[  6661.980] (EE) modeset(0): eglInitialize() failed
[  6661.981] (EE) modeset(0): glamor initialization failed
[  6662.171] (II) AIGLX: Screen 0 is not DRI2 capable
[  6662.171] (EE) AIGLX: reverting to software rendering

$ glxinfo
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: VMware, Inc. (0xffffffff)
    Device: llvmpipe (LLVM 4.0, 256 bits) (0xffffffff)
    Version: 17.1.5
    Accelerated: no
    Video memory: 7876MB
    Unified memory: no
    Preferred profile: compat (0x2)
    Max core profile version: 0.0
    Max compat profile version: 2.1
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 2.0
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 4.0, 256 bits)

Expected results:
Xorg.0.log (not sure, this is with intel driver)
[     6.574] (II) AIGLX: Loaded and initialized i965

$ glxinfo
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel Open Source Technology Center (0x8086)
    Device: Mesa DRI Intel(R) Sandybridge Mobile  (0x126)
    Version: 17.1.5
    Accelerated: yes
    Video memory: 1536MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 3.3
    Max compat profile version: 3.0
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.0
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Mobile

Additional info:
Comment 1 Fedora End Of Life 2018-05-03 04:23:40 EDT
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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.

Note You need to log in before you can comment on or make changes to this bug.