Bug 1478536

(In reply to Alex Markley from comment #0)
> Description of problem:
> 
> When launching Blender, after switching the rendering engine to "Cycles
> Render", the terminal displays a large number of errors and warnings:
> 
> ---- SNIP ----
> 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
> ---- SNIP ----
This doesn't seems a good start for using blender on such hw environmment.

Can you please report which hardware is this, Desktop environment and if using Wayland or Xorg ?

Sorry for missing those basic stats.

Uname: 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
Integrated GPU: Intel® HD Graphics 620 (Kaby Lake GT2)
Discrete GPU: NVIDIA Corporation GM107M [GeForce GTX 950M] (rev a2)

I'm using Gnome, and the problem only occurs on Wayland. On Xorg, the errors do not appear.

I should say also that this issue did *not* appear in FC25 on the same hardware.

(In reply to Alex Markley from comment #2)
> Sorry for missing those basic stats.
> 
> Uname: 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
> Integrated GPU: Intel® HD Graphics 620 (Kaby Lake GT2)
> Discrete GPU: NVIDIA Corporation GM107M [GeForce GTX 950M] (rev a2)
> 
> I'm using Gnome, and the problem only occurs on Wayland. On Xorg, the errors
> do not appear.
> 
> I should say also that this issue did *not* appear in FC25 on the same
> hardware.


I failed to reproduce the bug with the hybrid laptop ASUS X550ZE featuring:

Integrated GPU: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R6 Graphics] 
Dedicated GPU: Advanced Micro Devices, Inc. [AMD/ATI] Jet PRO [Radeon R5 M230]  

 The issues seems a regression related to the nouveau driver on  Wayland session. Try to run "DRI_PRIME=1 blender" to use Nvidia and blender for Intel HD  in the terminal and submit the result.

(In reply to Luya Tshimbalanga from comment #3)
> The issues seems a regression related to the nouveau driver on  Wayland
> session.

I would agree with this assessment, since everything was working previously. All I did was a dnf system upgrade.

> Try to run "DRI_PRIME=1 blender" to use Nvidia and blender for
> Intel HD  in the terminal and submit the result.

To confirm, this is the result of using DRI_PRIME in my environment:

---- SNIP ----
[alex@obsidian ~]$ glxinfo | egrep 'renderer string|direct rendering'
direct rendering: Yes
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) 
[alex@obsidian ~]$ DRI_PRIME=1 glxinfo | egrep 'renderer string|direct rendering'
direct rendering: Yes
OpenGL renderer string: Gallium 0.4 on NV117
[alex@obsidian ~]$ 
---- SNIP ----

Unfortunately, DRI_PRIME=1 has no positive impact on this issue with Blender:

---- SNIP ----
[alex@obsidian ~]$ DRI_PRIME=1 /usr/bin/blender
Read new prefs: /home/alex/.config/blender/2.78/config/userpref.blend
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
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
Saved session recovery to '/tmp/quit.blend'

Blender quit
[alex@obsidian ~]$ 
---- SNIP ----

I should note that I have not observed any *functional* issues associated with these warnings, except delays during startup.

(I should also note that glxgears reports no issues with direct rendering on either GPU.)

Backup your user preference somewhere then delete it to use the default:
/home/alex/.config/blender/2.78/config/userpref.blend

Start blender both way including with DRI_PRIME=1. Should both method fail, let assign the issue to nouveau driver for further debugging.

After deleting userpref.blend, here were the results:

---- SNIP ----
[alex@obsidian RenderTemp]$ /usr/bin/blender 
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
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@obsidian RenderTemp]$ 
---- SNIP ----

And with DRI_PRIME...

---- SNIP ----
[alex@obsidian RenderTemp]$ DRI_PRIME=1 /usr/bin/blender 
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
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
---- SNIP ----

Thank you for testing. Let's assign the issue to xorg as the issue seems affecting hybrid graphic hardware Intel+Nvidia.

Hi Alex,
Blender 2.79 is just released. Could you test if the issue get resolved on your hardware?
Thanks.

I seem to have a similar issue, but I have an old ATI card:

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650]

Until recently it was working fine, but today I tried with blender-2.79-1.fc26.x86_64 and I do see a lot of those errors in the console:

DRM_IOCTL_I915_GEM_APERTURE failed: No such file or directory
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
DRM_IOCTL_I915_GEM_APERTURE failed: No such file or directory
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
cl_get_gt_device(): error, unknown device: 0
DRM_IOCTL_I915_GEM_APERTURE failed: No such file or directory
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
DRM_IOCTL_I915_GEM_APERTURE failed: No such file or directory
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
cl_get_gt_device(): error, unknown device: 0
DRM_IOCTL_I915_GEM_APERTURE failed: No such file or directory
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
cl_get_gt_device(): error, unknown device: 0

Seems to be repeating.

If I maximize the blender window, then it becomes unusable - the screen starts flickering and some areas get corrupted, I see bitmaps from other applications showing up in there; actually I managed to take a screenshot (see attachment).

When I go back to the window size that blender started with, the screen errors disappear.

Last time I tried was about a month ago and I did not experience such problems and could work with blender in a maximized window.

Created attachment 1339469 [details]
screenshot of the corrupt blender screen

The image shows corruption in the blender screen, this happens when the mouse is being moved around in blender that is running in a maximized window.

I forgot to mention that I am running xorg-x11-server-Xorg-1.19.3-4.fc26.x86_64 and the MATE window manager.

...and I was too early to say that it works in non-maximized window mode, unfortunately it doesn't :( It just does not corrupt using bitmaps of foreign applications, instead it messes up itself. It seems that anything related to tooltips/highliting is causing problems, i.e. when I hover the mouse over various buttons parts of the screen start to flicker and draw incorrectly.

Sorry for the "spam", one more note: I reviewed my update history and the most recent relevant changes was an update of mesa libraries from 17.1.7 to 17.2.2.

Unfortunately dnf did not allow me to undo or rollback (it was always saying that some packages were no longer available), so I was not able to retest against the mesa version before the update, but suspect that the problem is related to the new version.

Lets assign to wayland as it happened the bugs occurred at that component.

(In reply to Luya Tshimbalanga from comment #14)
> Lets assign to wayland as it happened the bugs occurred at that component.

"wayland" is not a server of any sort, it's more of an ipc library, so it is very unlikely the issue is in "wayland".

The issue is either in blender, xorg-x11-server or mesa, but not in wayland.

Seems that error is coming from beignet's libcl.so

Here: https://github.com/intel/beignet/blob/master/src/intel/intel_driver.c#L219

Please note that in my log output I do not have the dri error line, instead I have "cl_get_gt_device(): error, unknown device: 0". This is the only difference between my log and the log from Alex, of course I can't tell if it originates from the same problem.

I tried to downgrade beignet to 1.3.1-2.fc26.x86_64 from 1.3.1-3.git20170622.36f6a8b.fc26, but this did not make any difference with blender.

I tried to downgrade blender itself via dnf downgrade, but was not able to run it, the older version did not start because of some unresolved symbol.

I updated to Fedora 27 and the issue is still there. So basically, blender became unusable on Fedora on some configurations over half a year ago and nothing has changed :(

Can I do anything to speed up the fix, do you need more log or more testing?

(In reply to Sergey Bostandzhyan from comment #19)
> I updated to Fedora 27 and the issue is still there. So basically, blender
> became unusable on Fedora on some configurations over half a year ago and
> nothing has changed :(
> 
> Can I do anything to speed up the fix, do you need more log or more testing?

That would be nice.

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.

Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.

Reopening, this is present in f29 as well.

Reproducer steps:
* install beignet
* launch blender

Results:
$ blender
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 [2]
param: 4, val: 0
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 [2]
param: 4, val: 0
cl_get_gt_device(): error, unknown device: 0
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 [2]
param: 4, val: 0
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 [2]
param: 4, val: 0
cl_get_gt_device(): error, unknown device: 0
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 [2]
param: 4, val: 0
cl_get_gt_device(): error, unknown device: 0

Without beignet installed I get no error.

System details:
$ lspci
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:14.0 USB controller: Intel Corporation 9 Series Chipset Family USB xHCI Controller
00:16.0 Communication controller: Intel Corporation 9 Series Chipset Family ME Interface #1
00:1a.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2
00:1c.0 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 (rev d0)
00:1c.3 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 4 (rev d0)
00:1c.4 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 5 (rev d0)
00:1d.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #1
00:1f.0 ISA bridge: Intel Corporation Z97 Chipset LPC Controller
00:1f.2 SATA controller: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode]
00:1f.3 SMBus: Intel Corporation 9 Series Chipset Family SMBus Controller
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 560/560X] (rev cf)
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X]
03:00.0 PCI bridge: ASMedia Technology Inc. ASM1184e PCIe Switch Port
04:01.0 PCI bridge: ASMedia Technology Inc. ASM1184e PCIe Switch Port
04:03.0 PCI bridge: ASMedia Technology Inc. ASM1184e PCIe Switch Port
04:05.0 PCI bridge: ASMedia Technology Inc. ASM1184e PCIe Switch Port
04:07.0 PCI bridge: ASMedia Technology Inc. ASM1184e PCIe Switch Port
06:00.0 Audio device: Creative Labs EMU20k2 [Sound Blaster X-Fi Titanium Series] (rev 03)
09:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06)

This is essentially a z97/Haswell system with a Radeon RX 560 GPU. The Intel IGP is disabled in the BIOS, so that may be the issue.

Actually I'll close it NOTABUG as I don't think beignet should be installed if the IGP can't be found.

I know this is closed, but it came up for me when searching for a similar issue.  The issue is the Intel graphics driver.  Its OpenCL support (where the errors are coming from) is sadly lacking and/or non existent.  Unfortunately that is another closed source driver that Fedora or Red Hat cant do anything about.  The best thing I can suggest is remove beigenet support from Pocl so it will quit trying.