2.79-rc1 "dri2 connection failed" #52262

New Issue

Alex Markley · 2017-08-04T19:37:23+02:00

Alex Markley commented

2017-08-04 19:37:23 +02:00

System Information
Fedora 26 (Linux)
Linux obsidian.malexmedia.net 4.11.11-300.fc26.x86_64 #1 SMP Mon Jul 17 16:32:11 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
CPU: Intel® Core™ i7-7500U CPU @ 2.70GHz × 4
RAM: 16GB
GPU: Intel® HD Graphics 620 (Kaby Lake GT2)

Using wayland, not Xorg!

Blender Version
Broken: blender-2.79-rc1-linux-glibc219 5e9132b3b7
Worked: blender-2.79-testbuild2-linux-glibc219 248bba81e7

Short description of error

Extremely slow startup, and lots of warnings:

found bundled python: /home/alex/bin/blender-2.79-rc1-linux-glibc219-x86_64/2.79/python
X server found. dri2 connection failed! 
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
nvc0_screen_create:881 - Error allocating PGRAPH context for M2MF: -16
X server found. dri2 connection failed! 
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed! 
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed! 
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed! 
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed! 
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed! 
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed! 
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed! 
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed! 
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed! 
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed! 
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed! 
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0

Blender quit

**System Information** Fedora 26 (Linux) Linux obsidian.malexmedia.net 4.11.11-300.fc26.x86_64 #1 SMP Mon Jul 17 16:32:11 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux CPU: Intel® Core™ i7-7500U CPU @ 2.70GHz × 4 RAM: 16GB GPU: Intel® HD Graphics 620 (Kaby Lake GT2) Using wayland, not Xorg! **Blender Version** Broken: blender-2.79-rc1-linux-glibc219 5e9132b3b7d Worked: blender-2.79-testbuild2-linux-glibc219 248bba81e7a **Short description of error** Extremely slow startup, and lots of warnings: ``` found bundled python: /home/alex/bin/blender-2.79-rc1-linux-glibc219-x86_64/2.79/python X server found. dri2 connection failed! DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 nvc0_screen_create:881 - Error allocating PGRAPH context for M2MF: -16 X server found. dri2 connection failed! DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 X server found. dri2 connection failed! DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 X server found. dri2 connection failed! DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 X server found. dri2 connection failed! DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 X server found. dri2 connection failed! DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 X server found. dri2 connection failed! DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 X server found. dri2 connection failed! DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 X server found. dri2 connection failed! DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 X server found. dri2 connection failed! DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 X server found. dri2 connection failed! DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 X server found. dri2 connection failed! DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 X server found. dri2 connection failed! DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 Blender quit ```

Alex Markley commented

2017-08-04 19:37:23 +02:00

Changed status to: 'Open'

Alex Markley commented

2017-08-04 19:37:23 +02:00

Added subscriber: @Alex-Markley

Alex Markley commented

2017-08-04 19:51:00 +02:00

I also tried Xorg vs. Wayland. The issue is not reproducible under Xorg, only under Wayland.

As an additional data point here, my laptop also has a discrete NVIDIA Corporation GM107M [GeForce GTX 950M].

When I run 2.79-rc1 with DRI_PRIME=1, which engages the NVIDIA card, the "dri2 connection failed" issue still happens.

I also tried Xorg vs. Wayland. The issue is not reproducible under Xorg, only under Wayland. As an additional data point here, my laptop also has a discrete NVIDIA Corporation GM107M [GeForce GTX 950M]. When I run 2.79-rc1 with DRI_PRIME=1, which engages the NVIDIA card, the "dri2 connection failed" issue still happens.

Alex Markley commented

2017-08-04 20:30:58 +02:00

Changed status from 'Open' to: 'Resolved'

Alex Markley closed this issue

2017-08-04 20:30:58 +02:00

Alex Markley self-assigned this 2017-08-04 20:30:58 +02:00

Alex Markley commented

2017-08-04 20:30:58 +02:00

I'm going to call this closed because I see the same behavior on the previous build. (testbuild2)

What confused me is that testbuild2 does not start throwing errors until after you open a .blend file, whereas rc1 throws the errors immediately upon launch.

So the reason why these errors are appearing seems to have more to do with my transition from FC25 -> FC26, rather than blender itself.

Thanks!

I'm going to call this closed because I see the same behavior on the previous build. (testbuild2) What confused me is that testbuild2 does not start throwing errors until **after** you open a .blend file, whereas rc1 throws the errors immediately upon launch. So the reason why these errors are appearing seems to have more to do with my transition from FC25 -> FC26, rather than blender itself. Thanks!

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

2.79-rc1 "dri2 connection failed" #52262