I continue from another post:
After startup I have the following message:
BC_DisplayInfo::gl_fb_config failed
Do you know what it could be?
something between mesa and X server?
I fixed my mesa3d version to 22.1.7 due to breakage on nouveau with my specific low end card (gt710) so I am not following latest mesa changes ...
Another problem, if I load one or more media, when I set the X11-OpenGL driver, I get the following warning:
void AWindowGUI::update_asset_list(): Warning: /home/paz/test/sad_woman.mxf dimensions 1920x1080 exceed OpenGL texture limit 0 void AWindowGUI::update_asset_list(): Warning: /home/paz/test/Unusual_Habitat.wav dimensions 0x0 exceed OpenGL texture limit 0 void AWindowGUI::update_asset_list(): Warning: /home/paz/test/video (2160p)HDR_01.mp4 dimensions 3840x2160 exceed OpenGL texture limit 0 void AWindowGUI::update_asset_list(): Warning: /home/paz/test/vp.webm dimensions 512x288 exceed OpenGL texture limit 0 Decoder dnxhd does not support device type vaapi. HW device init failed, using SW decode. file:/home/paz/test/sad_woman.mxf err: Operation not permitted FFMPEG::open_decoder: some stream times estimated: /home/paz/test/vp.webm
editing on the timeline more or less works, but I often have freezes that force me to reboot.
If I use the X11 driver everything works fine and I don't have the freezes.
I've tried several tests, but I can't get to the bottom of the problem. On my system I have the following packages involving OpenGL: freeglut 3.6 glu 9.0.3 glslang 14.3 libepoxy 1.5.10 libglvnd 1.7 qt6-shadertools 6.7 and mesa 24.2.3 xf86-video-amdgpu 23.0.0 (for the 2D and opengl) I also have the same errors in Wayland (which, I imagine, uses xwayland) however I have better performance in timeline and no crashes. I too think it is some mesa update or, even more likely, amd drivers. However the problem is not only in the latest CinGG release but also in the previous one and also in a different distro (however always rolling and Arch based).
чт, 3 окт. 2024 г., 13:05 Andrea paz via Cin <[email protected]>:
I continue from another post:
After startup I have the following message:
BC_DisplayInfo::gl_fb_config failed
Do you know what it could be?
something between mesa and X server?
I fixed my mesa3d version to 22.1.7 due to breakage on nouveau with my specific low end card (gt710) so I am not following latest mesa changes ...
Another problem, if I load one or more media, when I set the X11-OpenGL driver, I get the following warning:
void AWindowGUI::update_asset_list(): Warning: /home/paz/test/sad_woman.mxf dimensions 1920x1080 exceed OpenGL texture limit 0 void AWindowGUI::update_asset_list(): Warning: /home/paz/test/Unusual_Habitat.wav dimensions 0x0 exceed OpenGL texture limit 0 void AWindowGUI::update_asset_list(): Warning: /home/paz/test/video (2160p)HDR_01.mp4 dimensions 3840x2160 exceed OpenGL texture limit 0 void AWindowGUI::update_asset_list(): Warning: /home/paz/test/vp.webm dimensions 512x288 exceed OpenGL texture limit 0 Decoder dnxhd does not support device type vaapi. HW device init failed, using SW decode. file:/home/paz/test/sad_woman.mxf err: Operation not permitted FFMPEG::open_decoder: some stream times estimated: /home/paz/test/vp.webm
editing on the timeline more or less works, but I often have freezes that force me to reboot.
If I use the X11 driver everything works fine and I don't have the freezes.
I've tried several tests, but I can't get to the bottom of the problem. On my system I have the following packages involving OpenGL:
freeglut 3.6 glu 9.0.3 glslang 14.3 libepoxy 1.5.10 libglvnd 1.7 qt6-shadertools 6.7 and mesa 24.2.3 xf86-video-amdgpu 23.0.0 (for the 2D and opengl)
I also have the same errors in Wayland (which, I imagine, uses xwayland) however I have better performance in timeline and no crashes. I too think it is some mesa update or, even more likely, amd drivers. However the problem is not only in the latest CinGG release but also in the previous one and also in a different distro (however always rolling and Arch based).
may be you can rebuild earlier mesa, like 24.1.x, 23.x.x ? --
Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
чт, 3 окт. 2024 г., 17:40 Andrea paz <[email protected]>:
may be you can rebuild earlier mesa, like 24.1.x, 23.x.x ?
By downgrading to mesa version 24.1.6 there are no more problems; returning to mesa 24.2.3 the problem returns.
Then I am afraid you need to bring it to https://gitlab.freedesktop.org/mesa/mesa/-/issues/?sort=created_date&state=o... mesa3d's issue tracker. Hopefully for radeonsi driver response will be more supportive compared to nouveau. Be prepared for git bisect ....
Then I am afraid you need to bring it to https://gitlab.freedesktop.org/mesa/mesa/-/issues/?sort=created_date&state=o... mesa3d's issue tracker. Hopefully for radeonsi driver response will be more supportive compared to nouveau. Be prepared for git bisect ....
@Andrew Do you think a request like that will do? Anyway, I'm not able to participate in the discussion about a bug; I don't even know what a “git bisect” is... I use Cinelerra-GG (CinGG) as a video editing program on Arch linux, KDE and XOrg graphics server. CinGG can run either with OpenGL or with X11. In switching from mesa 24.1 to 24.2, the OpenGL mode of CinGG no longer works: I have warning messages and frequent freezes. After startup the program I have the following message: BC_DisplayInfo::gl_fb_config failed If I load one or more media in CinGG, when I set the X11-OpenGL driver, I get the following warning: void AWindowGUI::update_asset_list(): Warning: /home/paz/test/sad_woman.mxf dimensions 1920x1080 exceed OpenGL texture limit 0 void AWindowGUI::update_asset_list(): Warning: /home/paz/test/Unusual_Habitat.wav dimensions 0x0 exceed OpenGL texture limit 0 void AWindowGUI::update_asset_list(): Warning: /home/paz/test/video (2160p)HDR_01.mp4 dimensions 3840x2160 exceed OpenGL texture limit 0 void AWindowGUI::update_asset_list(): Warning: /home/paz/test/vp.webm dimensions 512x288 exceed OpenGL texture limit 0 In X11 mode the errors do not occur. In Wayland the errors do not occur. In mesa 24.1.6 the errors do not occur. Glxgears and glmark2 work without problems. Arch linux is a rolling and everything is up to date. I have an AMD Radeon RX5700X (Navi10) with amdgpu drivers. I am a simple user of CinGG and have no ability to operate on the code. If you want to try CinGG there is appimage that works on many different linux distros (https://cinelerra-gg.org/download/images/).
чт, 3 окт. 2024 г., 19:03 Andrea paz <[email protected]>:
Then I am afraid you need to bring it to
https://gitlab.freedesktop.org/mesa/mesa/-/issues/?sort=created_date&state=o...
mesa3d's issue tracker. Hopefully for radeonsi driver response will be more supportive compared to nouveau. Be prepared for git bisect ....
@Andrew Do you think a request like that will do? Anyway, I'm not able to participate in the discussion about a bug; I don't even know what a “git bisect” is...
basically you download mesa's source code with git clone , then set good/bad points in git history, and rebuild/install/test until bad commit will be found. Of course some commits might introduce more errors or break build itself .... But hopefully developers will at least run cingg on their end first, may be this is something simple and obvious for them. I think report as written below is ok. You might need to leave few more details like kernel version etc, but last time I was there we had template to fill in .....
I use Cinelerra-GG (CinGG) as a video editing program on Arch linux, KDE and XOrg graphics server. CinGG can run either with OpenGL or with X11. In switching from mesa 24.1 to 24.2, the OpenGL mode of CinGG no longer works: I have warning messages and frequent freezes. After startup the program I have the following message:
BC_DisplayInfo::gl_fb_config failed
If I load one or more media in CinGG, when I set the X11-OpenGL driver, I get the following warning:
void AWindowGUI::update_asset_list(): Warning: /home/paz/test/sad_woman.mxf dimensions 1920x1080 exceed OpenGL texture limit 0 void AWindowGUI::update_asset_list(): Warning: /home/paz/test/Unusual_Habitat.wav dimensions 0x0 exceed OpenGL texture limit 0 void AWindowGUI::update_asset_list(): Warning: /home/paz/test/video (2160p)HDR_01.mp4 dimensions 3840x2160 exceed OpenGL texture limit 0 void AWindowGUI::update_asset_list(): Warning: /home/paz/test/vp.webm dimensions 512x288 exceed OpenGL texture limit 0
In X11 mode the errors do not occur. In Wayland the errors do not occur. In mesa 24.1.6 the errors do not occur. Glxgears and glmark2 work without problems. Arch linux is a rolling and everything is up to date. I have an AMD Radeon RX5700X (Navi10) with amdgpu drivers. I am a simple user of CinGG and have no ability to operate on the code. If you want to try CinGG there is appimage that works on many different linux distros (https://cinelerra-gg.org/download/images/).
Done! I don't have much hope that it will do any good. https://gitlab.freedesktop.org/mesa/mesa/-/issues/11976
чт, 3 окт. 2024 г., 20:03 Andrea paz <[email protected]>:
Done! I don't have much hope that it will do any good. https://gitlab.freedesktop.org/mesa/mesa/-/issues/11976
thanks!
чт, 3 окт. 2024 г., 20:07 Andrew Randrianasulu <[email protected]>:
чт, 3 окт. 2024 г., 20:03 Andrea paz <[email protected]>:
Done! I don't have much hope that it will do any good. https://gitlab.freedesktop.org/mesa/mesa/-/issues/11976
thanks!
two random ideas about that: 1) test (if possible) if disabling glvnd for mesa fixes that. 2) test if using zink driver (opengl via Vulkan) fixes this error
I have tried to explore your suggestions, but I don't think I am able to implement them. GLVND: glvnd is a vendor neutral libgl library that was made by nvidia so that nvidia proprietary drivers can co-exist with mesa on the same system. The use-case for this is usually desktops or laptops with an intel iGPU and an nvidia dGPU. If you are running intel/amd or all amd, you don’t need libglvnd. Here is a patch to compile mesa-git without glvnd: https://www.reddit.com/r/archlinux/comments/hwhouh/how_to_build_mesa_without... Manually: PART 3: Compiling mesa-git without libglvnd I have two of my own gitlab repositories that makes this easy to do. First let’s clone them: git clone http://gitlab.com/gloriouseggroll/mesa-git-noglvnd git clone http://gitlab.com/gloriouseggroll/lib32-mesa-git-noglvnd Now lets make both packages: cd mesa-git-noglvnd makepkg cd ../lib32-mesa-git-noglvnd makepkg They need to be installed at the same time, which is why we compiled them both first. Now lets move them to the same folder and install them: cp *.pkg.tar.xz ../mesa-git-noglvnd/ cd ../mesa-git-noglvnd sudo pacman -U *.pkg.tar.xz When you do this, it’s going to ask you to replace vulkan-radeon and/or vulkan-intel packages, as well as remove libglvnd. This is because mesa-git provides all of those when compiled from this package, libglvnd being replaced with mesa’s libgl. If compiled from the AUR, it replaces just the vulkan packages. It says here that there might be problems by not installing glvnd and so the best solution is to create a glvnd installation-fake: https://forums.gentoo.org/viewtopic-t-1170273.html I don't understand how to do all these things. Also, I used mesa-git in the past but had so many problems that I didn't want to put it back. ZINK: I tried this: __GLX_VENDOR_LIBRARY_NAME=mesa MESA_LOADER_DRIVER_OVERRIDE=zink GALLIUM_DRIVER=zink /home/paz/cinelerra5/cinelerra-5.1/bin/./cin CinGG starts but with the following errors: $ __GLX_VENDOR_LIBRARY_NAME=mesa MESA_LOADER_DRIVER_OVERRIDE=zink GALLIUM_DRIVER=zink /home/paz/cinelerra5/cinelerra-5.1/bin/./cin Cinelerra Infinity - built: Oct 23 2024 13:17:21 git://git.cinelerra-gg.org/goodguy/cinelerra.git (c) 2006-2019 Heroine Virtual Ltd. by Adam Williams 2007-2020 mods for Cinelerra-GG by W.P.Morrow aka goodguy 2003-2017 mods for Cinelerra-CV by CinelerraCV team 2015-2024 mods for Cinelerra-GG by Cinelerra-GG team Libav version: Lavc61.3.100 Cinelerra is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. There is absolutely no warranty for Cinelerra. DRI3 not available DRI3 not available DRI3 not available DRI3 not available DRI3 not available BC_WindowBase::glx_window_fb_configs: opengl initialization failed failed DRI3 not available DRI3 not available DRI3 not available DRI3 not available BC_DisplayInfo::gl_fb_config failed DRI3 not available DRI3 not available DRI3 not available DRI3 not available DRI3 not available BC_WindowBase::glx_window_fb_configs: opengl initialization failed failed DRI3 not available DRI3 not available DRI3 not available DRI3 not available DRI3 not available BC_WindowBase::glx_window_fb_configs: opengl initialization failed failed DRI3 not available DRI3 not available DRI3 not available DRI3 not available DRI3 not available BC_WindowBase::glx_window_fb_configs: opengl initialization failed failed DRI3 not available DRI3 not available DRI3 not available DRI3 not available DRI3 not available BC_WindowBase::glx_window_fb_configs: opengl initialization failed failed DRI3 not available DRI3 not available DRI3 not available DRI3 not available DRI3 not available BC_WindowBase::glx_window_fb_configs: opengl initialization failed failed DRI3 not available DRI3 not available DRI3 not available DRI3 not available DRI3 not available BC_WindowBase::glx_window_fb_configs: opengl initialization failed failed DRI3 not available DRI3 not available DRI3 not available DRI3 not available DRI3 not available BC_WindowBase::glx_window_fb_configs: opengl initialization failed failed Instead starting without Zink's environment variables I get the only, usual, error: BC_DisplayInfo::gl_fb_config failed In both cases X11-OpenGL does not work. I couldn't find any other info on getting Zink to work.
пн, 16 дек. 2024 г., 15:32 Andrea paz <[email protected]>:
I have tried to explore your suggestions, but I don't think I am able to implement them.
GLVND:
glvnd is a vendor neutral libgl library that was made by nvidia so that nvidia proprietary drivers can co-exist with mesa on the same system. The use-case for this is usually desktops or laptops with an intel iGPU and an nvidia dGPU. If you are running intel/amd or all amd, you don’t need libglvnd.
Here is a patch to compile mesa-git without glvnd:
https://www.reddit.com/r/archlinux/comments/hwhouh/how_to_build_mesa_without...
Manually:
PART 3: Compiling mesa-git without libglvnd
I have two of my own gitlab repositories that makes this easy to do.
First let’s clone them:
git clone http://gitlab.com/gloriouseggroll/mesa-git-noglvnd git clone http://gitlab.com/gloriouseggroll/lib32-mesa-git-noglvnd
Now lets make both packages:
cd mesa-git-noglvnd makepkg cd ../lib32-mesa-git-noglvnd makepkg
They need to be installed at the same time, which is why we compiled them both first. Now lets move them to the same folder and install them:
cp *.pkg.tar.xz ../mesa-git-noglvnd/ cd ../mesa-git-noglvnd sudo pacman -U *.pkg.tar.xz
When you do this, it’s going to ask you to replace vulkan-radeon and/or vulkan-intel packages, as well as remove libglvnd. This is because mesa-git provides all of those when compiled from this package, libglvnd being replaced with mesa’s libgl. If compiled from the AUR, it replaces just the vulkan packages.
It says here that there might be problems by not installing glvnd and so the best solution is to create a glvnd installation-fake: https://forums.gentoo.org/viewtopic-t-1170273.html
I don't understand how to do all these things. Also, I used mesa-git in the past but had so many problems that I didn't want to put it back.
*I think* you can just edit mesa3d PKGBUILD ? And then run makepkg ... never tried Arch packaging but it *supposed* to be simple enough ;)) well, we probably can shelf this for now ....
ZINK:
I tried this: __GLX_VENDOR_LIBRARY_NAME=mesa MESA_LOADER_DRIVER_OVERRIDE=zink GALLIUM_DRIVER=zink /home/paz/cinelerra5/cinelerra-5.1/bin/./cin
CinGG starts but with the following errors:
$ __GLX_VENDOR_LIBRARY_NAME=mesa MESA_LOADER_DRIVER_OVERRIDE=zink GALLIUM_DRIVER=zink /home/paz/cinelerra5/cinelerra-5.1/bin/./cin Cinelerra Infinity - built: Oct 23 2024 13:17:21 git://git.cinelerra-gg.org/goodguy/cinelerra.git (c) 2006-2019 Heroine Virtual Ltd. by Adam Williams 2007-2020 mods for Cinelerra-GG by W.P.Morrow aka goodguy 2003-2017 mods for Cinelerra-CV by CinelerraCV team 2015-2024 mods for Cinelerra-GG by Cinelerra-GG team
Libav version: Lavc61.3.100
Cinelerra is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. There is absolutely no warranty for Cinelerra.
DRI3 not available
hm, I thought dri3 by itself is default for xf86-video- amdgpu driver? But may be you use modesetting? Try to look in X.org.log to see what driver actually drive your card? And change it from -modesetting to -amdgpu or other way around? LIBGL_DEBUG=verbose with say glxingo should say if you have DRI3 .. (from memory). Sorry for such inconvenience :( DRI3 not available
DRI3 not available DRI3 not available DRI3 not available BC_WindowBase::glx_window_fb_configs: opengl initialization failed failed DRI3 not available DRI3 not available DRI3 not available DRI3 not available BC_DisplayInfo::gl_fb_config failed DRI3 not available DRI3 not available DRI3 not available DRI3 not available DRI3 not available BC_WindowBase::glx_window_fb_configs: opengl initialization failed failed DRI3 not available DRI3 not available DRI3 not available DRI3 not available DRI3 not available BC_WindowBase::glx_window_fb_configs: opengl initialization failed failed DRI3 not available DRI3 not available DRI3 not available DRI3 not available DRI3 not available BC_WindowBase::glx_window_fb_configs: opengl initialization failed failed DRI3 not available DRI3 not available DRI3 not available DRI3 not available DRI3 not available BC_WindowBase::glx_window_fb_configs: opengl initialization failed failed DRI3 not available DRI3 not available DRI3 not available DRI3 not available DRI3 not available BC_WindowBase::glx_window_fb_configs: opengl initialization failed failed DRI3 not available DRI3 not available DRI3 not available DRI3 not available DRI3 not available BC_WindowBase::glx_window_fb_configs: opengl initialization failed failed DRI3 not available DRI3 not available DRI3 not available DRI3 not available DRI3 not available BC_WindowBase::glx_window_fb_configs: opengl initialization failed failed
Instead starting without Zink's environment variables I get the only, usual, error:
BC_DisplayInfo::gl_fb_config failed
In both cases X11-OpenGL does not work.
I couldn't find any other info on getting Zink to work.
*I think* you can just edit mesa3d PKGBUILD ? And then run makepkg ... never tried Arch packaging but it *supposed* to be simple enough ;))
The mesa pkgbuild is here: https://gitlab.archlinux.org/archlinux/packaging/packages/mesa/-/blob/main/P... Unfortunately I am so incompetent that I don't know how to work with pkgbuild. I tried to comment out the 2 “libglvnd” entries but when I compile it crashes with a signature validation error (unknow public key).
hm, I thought dri3 by itself is default for xf86-video- amdgpu driver? But may be you use modesetting? Try to look in X.org.log to see what driver actually drive your card? And change it from -modesetting to -amdgpu or other way around?
Yes, amdgpu uses DRI3 in Arch and no, you cannot use nomodeset with amd because it would not work (not having nomodeset is a requirement to install amdgpu drivers). With your last suggestion the errors with dri3 disappear but the X1-OpenGL error remains, which continues to fail. glxinfo works, as does glmark2 and every program that uses opengl. I only have the problem with CinGG.
пн, 16 дек. 2024 г., 23:03 Andrea paz <[email protected]>:
*I think* you can just edit mesa3d PKGBUILD ? And then run makepkg ... never tried Arch packaging but it *supposed* to be simple enough ;))
The mesa pkgbuild is here:
https://gitlab.archlinux.org/archlinux/packaging/packages/mesa/-/blob/main/P... Unfortunately I am so incompetent that I don't know how to work with pkgbuild. I tried to comment out the 2 “libglvnd” entries but when I compile it crashes with a signature validation error (unknow public key).
o.O may be ask on Arch forums then?
hm, I thought dri3 by itself is default for xf86-video- amdgpu driver? But may be you use modesetting? Try to look in X.org.log to see what driver actually drive your card? And change it from -modesetting to -amdgpu or other way around?
Yes, amdgpu uses DRI3 in Arch and no, you cannot use nomodeset
note, I said modesetting, X.org userspace driver that uses amdgpu kernel module. Not "nomodeset" kernel parameter .... with
amd because it would not work (not having nomodeset is a requirement to install amdgpu drivers). With your last suggestion the errors with dri3 disappear but the X1-OpenGL error remains, which continues to fail.
glxinfo works, as does glmark2 and every program that uses opengl. I only have the problem with CinGG.
yeah, cingg uses GLX pbuffers and I guess few other opensource programs do. May be ping mesa3d developers in their den ^w irc channel? May be adding apitrace to bugreport you already filled will help somehow.
About glvnd: I tried compiling mesa (via pkgbuild) with the --skippgpcheck option and everything works. CinGG however has the usual freezes (especially if you do the normal reverse). With X11 such freezes do not occur. The error (BC_DisplayInfo::gl_fb_config failed) remains even with X11, however.
About X.org.log: [...] [ 6.673] (II) Applying OutputClass "AMDgpu" to /dev/dri/card1 [ 6.673] loading driver: amdgpu [ 6.673] (==) Matched amdgpu as autoconfigured driver 0 [ 6.673] (==) Matched ati as autoconfigured driver 1 [ 6.673] (==) Matched modesetting as autoconfigured driver 2 [ 6.673] (==) Matched fbdev as autoconfigured driver 3 [ 6.673] (==) Matched vesa as autoconfigured driver 4 [ 6.673] (==) Assigned the driver to the xf86ConfigLayout [ 6.673] (II) LoadModule: "amdgpu" [...] Il giorno mar 17 dic 2024 alle ore 15:53 Andrea paz <[email protected]> ha scritto:
About glvnd: I tried compiling mesa (via pkgbuild) with the --skippgpcheck option and everything works. CinGG however has the usual freezes (especially if you do the normal reverse). With X11 such freezes do not occur. The error (BC_DisplayInfo::gl_fb_config failed) remains even with X11, however.
пн, 16 дек. 2024 г., 15:32 Andrea paz <[email protected]>:
I have tried to explore your suggestions, but I don't think I am able to implement them.
GLVND:
glvnd is a vendor neutral libgl library that was made by nvidia so that nvidia proprietary drivers can co-exist with mesa on the same system. The use-case for this is usually desktops or laptops with an intel iGPU and an nvidia dGPU. If you are running intel/amd or all amd, you don’t need libglvnd.
Here is a patch to compile mesa-git without glvnd:
https://www.reddit.com/r/archlinux/comments/hwhouh/how_to_build_mesa_without...
Manually:
PART 3: Compiling mesa-git without libglvnd
I have two of my own gitlab repositories that makes this easy to do.
First let’s clone them:
git clone http://gitlab.com/gloriouseggroll/mesa-git-noglvnd git clone http://gitlab.com/gloriouseggroll/lib32-mesa-git-noglvnd
Now lets make both packages:
cd mesa-git-noglvnd makepkg cd ../lib32-mesa-git-noglvnd makepkg
They need to be installed at the same time, which is why we compiled them both first. Now lets move them to the same folder and install them:
cp *.pkg.tar.xz ../mesa-git-noglvnd/ cd ../mesa-git-noglvnd sudo pacman -U *.pkg.tar.xz
When you do this, it’s going to ask you to replace vulkan-radeon and/or vulkan-intel packages, as well as remove libglvnd. This is because mesa-git provides all of those when compiled from this package, libglvnd being replaced with mesa’s libgl. If compiled from the AUR, it replaces just the vulkan packages.
It says here that there might be problems by not installing glvnd and so the best solution is to create a glvnd installation-fake: https://forums.gentoo.org/viewtopic-t-1170273.html
I don't understand how to do all these things. Also, I used mesa-git in the past but had so many problems that I didn't want to put it back.
ZINK:
I tried this: __GLX_VENDOR_LIBRARY_NAME=mesa MESA_LOADER_DRIVER_OVERRIDE=zink GALLIUM_DRIVER=zink /home/paz/cinelerra5/cinelerra-5.1/bin/./cin
CinGG starts but with the following errors:
$ __GLX_VENDOR_LIBRARY_NAME=mesa MESA_LOADER_DRIVER_OVERRIDE=zink GALLIUM_DRIVER=zink /home/paz/cinelerra5/cinelerra-5.1/bin/./cin Cinelerra Infinity - built: Oct 23 2024 13:17:21 git://git.cinelerra-gg.org/goodguy/cinelerra.git (c) 2006-2019 Heroine Virtual Ltd. by Adam Williams 2007-2020 mods for Cinelerra-GG by W.P.Morrow aka goodguy 2003-2017 mods for Cinelerra-CV by CinelerraCV team 2015-2024 mods for Cinelerra-GG by Cinelerra-GG team
Libav version: Lavc61.3.100
Cinelerra is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. There is absolutely no warranty for Cinelerra.
DRI3 not available
another suggestion from https://forum.manjaro.org/t/mesa-zink-trouble-since-23-3-3/158317 "LIBGL_KOPPER_DRI2=1" DRI3 not available
DRI3 not available DRI3 not available DRI3 not available BC_WindowBase::glx_window_fb_configs: opengl initialization failed failed DRI3 not available DRI3 not available DRI3 not available DRI3 not available BC_DisplayInfo::gl_fb_config failed DRI3 not available DRI3 not available DRI3 not available DRI3 not available DRI3 not available BC_WindowBase::glx_window_fb_configs: opengl initialization failed failed DRI3 not available DRI3 not available DRI3 not available DRI3 not available DRI3 not available BC_WindowBase::glx_window_fb_configs: opengl initialization failed failed DRI3 not available DRI3 not available DRI3 not available DRI3 not available DRI3 not available BC_WindowBase::glx_window_fb_configs: opengl initialization failed failed DRI3 not available DRI3 not available DRI3 not available DRI3 not available DRI3 not available BC_WindowBase::glx_window_fb_configs: opengl initialization failed failed DRI3 not available DRI3 not available DRI3 not available DRI3 not available DRI3 not available BC_WindowBase::glx_window_fb_configs: opengl initialization failed failed DRI3 not available DRI3 not available DRI3 not available DRI3 not available DRI3 not available BC_WindowBase::glx_window_fb_configs: opengl initialization failed failed DRI3 not available DRI3 not available DRI3 not available DRI3 not available DRI3 not available BC_WindowBase::glx_window_fb_configs: opengl initialization failed failed
Instead starting without Zink's environment variables I get the only, usual, error:
BC_DisplayInfo::gl_fb_config failed
In both cases X11-OpenGL does not work.
I couldn't find any other info on getting Zink to work.
participants (2)
-
Andrea paz -
Andrew Randrianasulu