FS#58551 - [nvidia] nvidia-drm error when launching Blender 17:2.79.b.git2.0385b33f-12
Attached to Project:
Arch Linux
Opened by Bruno d'Arcangeli (arcangeli) - Saturday, 12 May 2018, 08:14 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Monday, 14 May 2018, 08:59 GMT
Opened by Bruno d'Arcangeli (arcangeli) - Saturday, 12 May 2018, 08:14 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Monday, 14 May 2018, 08:59 GMT
|
Details
Description: Some time when i'm launching Blender
(17:2.79.b.git2.0385b33f-12) since last update of linux
(4.16.8-1) with nvidia driver (396.24-2), dmesg report this
error many time:
[drm:nv_drm_gem_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to lookup gem object for fence attach: 0x00000004 Additional info: Computer is an Alienware 13 R3 OLED. Optimus configured for Prime as "Discrete card as primary GPU" (as described in the arch wiki). Problem appeared only since last upgrade yesterday. Never seen this problem with linux 4.16.7-1, nvidia 390.48-13 and blender 17:2.79.b-7. Blender report in terminal: blender Read prefs: /home/bruno/.config/blender/2.79/config/userpref.blend Registered Animation Nodes with 497 modules. pyluxcore version: 2.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] Steps to reproduce: Launch blender. |
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Monday, 14 May 2018, 08:59 GMT
Reason for closing: Not a bug
Monday, 14 May 2018, 08:59 GMT
Reason for closing: Not a bug
I can not reproduce the error anymore.