[Bug 250325] graphics/mesa-gallium-va: libva error: /usr/local/lib/dri/radeonsi_drv_video.so init failed

[email protected]
Newsgroups gmane.os.freebsd.devel.x11
Message-ID <[email protected]/bugzilla/>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250325

            Bug ID: 250325
           Summary: graphics/mesa-gallium-va: libva error:
                    /usr/local/lib/dri/radeonsi_drv_video.so init failed
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: [email protected]
          Reporter: [email protected]
          Assignee: [email protected]
             Flags: maintainer-feedback?([email protected])

Hello,

i saw the new mesa update and i have rebuilt mesa-libs, mesa-dri and installed
gallium-va and gallium-vdpau.

Now i wanted to confirm if its working but i get:

libva info: VA-API version 1.9.0
libva info: Trying to open /usr/local/lib/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_9
libva error: /usr/local/lib/dri/radeonsi_drv_video.so init failed
libva info: va_openDriver() returns 2
vaInitialize failed with error code 2 (resource allocation failed),exit

and with vdpauinfo i get:

display: :0   screen: 0
Error creating VDPAU device: 23

Have i forgotten something? I using an RX 570

[ 42742.925] (II) AMDGPU(0): [DRI2] Setup complete
[ 42742.925] (II) AMDGPU(0): [DRI2]   DRI driver: radeonsi
[ 42742.925] (II) AMDGPU(0): [DRI2]   VDPAU driver: radeonsi

Before the update, it have worked perfectly. 

Many thanks in advance.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-x11
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.