Driver and OpenGL problem with OBS-studio

[Maybe]

Hello everyone!

When trying to work with OBS-studio (I tried it on FossaPup64, VanillaPUP, EasyOS, Antix in live mode) I faced this problem, OBS won't start. Opening OBS in the terminal I found this:

Code: Select all

error: X Error: GLXBadFBConfig, Major opcode: 150, Minor opcode: 34, Serial: 25
error: Failed to create OpenGL context.
error: Failed to create context!
error: device_create (GL) failed
error: Failed to initialize video.  Your GPU may not be supported, or your graphics drivers may need to be updated.

This is what the command

Code: Select all

glxinfo | grep OpenGL

output shows:

Code: Select all

# glxinfo | grep OpenGL
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics (ILK)
OpenGL version string: 2.1 Mesa 20.0.2
OpenGL shading language version string: 1.20
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 20.0.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16
OpenGL ES profile extensions:

Here is information about the CPU:

Code: Select all

info: CPU Name: Intel(R) Core(TM) i5 CPU       M 520  @ 2.40GHz
info: CPU Speed: 1647.045MHz
info: Physical Cores: 2, Logical Cores: 4
info: Physical Memory: 3740MB Total, 967MB Free
info: Kernel Version: Linux 5.10.83
info: Distribution: Missing /etc/os-release !
info: Window System: X11.0, Vendor: The X.Org Foundation, Version: 1.20.8

On the OBS-studio forum, one of the moderators answered a question related to a similar problem: Your driver or GPU does not support OpenGL x.x, so you cannot use OBS.

Dear community, can you help me understand what's wrong with the driver? Please tell me how can I fix this?

From Dmitry (Russia)

[williams2]

I think that I asked you in another thread,
to run tail /var/log/Xorg.0.log
which showed that you were using the modesetting driver.

But that may not have been you, it may have been someone else.

Anyway, I read somewhere that the newest Intel drivers work properly, and 3d acceleration works.
But Intel drivers that are a little bit older are broken and 3d acceleration does not work.
And that older Intel drivers also work properly.

For the broken intel drivers, they recommend using the modesetting driver instead of the Intel driver.
I think the modesetting driver can be enabled with a kernel option, and/or blacklisting the Intel driver.

The modesetting driver is a generic driver like the vesa driver but the vesa driver is more limited than the modesetting driver. AFAIK, the modesetting driver supports 2d and 3d acceleration.

tail /var/log/Xorg.0.log should show which driver you are using.

[Maybe]

Hello, dear @williams2

Thanks you so much fot your participation!

Code: Select all

tail /var/log/Xorg.0.log

show this:

Code: Select all

r[ 46.330] (**) Option "xkb_layout" "us,ru"
[ 46.330] (**) Option "xkb_options" "grp:alt_shift_toggle"
[ 696.245] (II) modeset(0): EDID vendor "LEN", prod id 16401
[ 696.245] (II) modeset(0): Printing DDC gathered Modelines:
[ 696.245] (II) modeset(0): Modeline "1280x800"x0.0 69.30 1280 1328 1360 1403 800 803 809 821 -hsync -vsync (49.4 kHz eP)
[ 696.245] (II) modeset(0): Modeline "1280x800"x0.0 57.59 1280 1328 1360 1403 800 803 809 821 -hsync -vsync (41.0 kHz e)
[ 696.248] (II) modeset(0): EDID vendor "LEN", prod id 16401
[ 696.248] (II) modeset(0): Printing DDC gathered Modelines:
[ 696.248] (II) modeset(0): Modeline "1280x800"x0.0 69.30 1280 1328 1360 1403 800 803 809 821 -hsync -vsync (49.4 kHz eP)
[ 696.248] (II) modeset(0): Modeline "1280x800"x0.0 57.59 1280 1328 1360 1403 800 803 809 821 -hsync -vsync (41.0 kHz e)

What's next?

From Dmitry (Russia)

[williams2]

What's next?

You are using the modesetting driver, which supports 3d acceleration.

I would test that 3d acceleration is really working
by running glxgears

if the 3d acceleration is really working, the frames per second should be about the same as the refresh rate of the monitor (about 60 hz for my flat screen monitor.)

Like this:

Code: Select all

303 frames in 5.0 seconds = 60.480 FPS
301 frames in 5.0 seconds = 59.994 FPS
300 frames in 5.0 seconds = 59.998 FPS
301 frames in 5.0 seconds = 60.009 FPS
300 frames in 5.0 seconds = 59.997 FPS
301 frames in 5.0 seconds = 60.004 FPS

Running glxgears -info shows:

Code: Select all

GL_RENDERER   = AMD PALM (DRM 2.50.0 / 4.19.23, LLVM 7.0.0)
GL_VERSION    = 3.1 Mesa 18.2.2
GL_VENDOR     = X.Org

I read somewhere that the modesetting driver uses PALM for 3d acceleration.

glxgears --help says: -info display OpenGL renderer info

AFAIK, this shows that OpenGL is working properly on my machine.

and, of course the information from glxinfo.

Code: Select all

OpenGL vendor string: X.Org
OpenGL renderer string: AMD PALM (DRM 2.50.0 / 4.19.23, LLVM 7.0.0)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.2
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.1 Mesa 18.2.2
OpenGL shading language version string: 1.40
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 18.2.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
OpenGL ES profile extensions:

Does your video card have enough ram? glxinfo | grep MB

[Maybe]

I would test that 3d acceleration is really working
by running glxgears

if the 3d acceleration is really working, the frames per second should be about the same as the refresh rate of the monitor (about 60 hz for my flat screen monitor.)

OK @williams2 I'll try:

Code: Select all

# glxgears
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
304 frames in 5.0 seconds = 60.624 FPS
301 frames in 5.0 seconds = 60.153 FPS

Running glxgears -info shows:

Code: Select all

GL_RENDERER   = Mesa DRI Intel(R) HD Graphics (ILK)
GL_VERSION    = 2.1 Mesa 20.0.2
GL_VENDOR     = Intel Open Source Technology Center

Does your video card have enough ram? glxinfo | grep MB

Here:

Code: Select all

glxinfo | grep MB
    Video memory: 1536MB

[williams2]

Video memory: 1536MB should be enough memory for most purposes, I think.

There is a gl benchmark program called glmark2 which tests some things that glxgears does not.
I searched for glmark2 in ppm, and installed the first package in the list. (about 7MB)

Then I ran glmark2 in a terminal.

If it finishes running without error, I would say that OpenGL seems to be running properly on your machine.

[williams2]

Will it run without hardware acceleration?

For example, if you start the app by typing obs then what does this do:

LIBGL_ALWAYS_SOFTWARE=1 obs

[bigpup]

When trying to work with OBS-studio (I tried it on FossaPup64, VanillaPUP, EasyOS, Antix in live mode) I faced this problem,

Give us some specific details on how you got OBS-studio and installed it.

Doing a search for this error, provides no output.
So, lets make sure you are trying to use a correct download, install, of OBS-Studio.

[bigpup]

When trying to work with OBS-studio (I tried it on FossaPup64, VanillaPUP, EasyOS, Antix in live mode) I faced this problem,

Give us some specific details on how you got OBS-studio and installed it.

Are you getting it from this topic:
viewtopic.php?t=4152

Doing a search for this error, provides no output.
So, lets make sure you are trying to use a correct download, install, of OBS-Studio.

[Maybe]

When trying to work with OBS-studio (I tried it on FossaPup64, VanillaPUP, EasyOS, Antix in live mode) I faced this problem,

Give us some specific details on how you got OBS-studio and installed it.

Doing a search for this error, provides no output.
So, lets make sure you are trying to use a correct download, install, of OBS-Studio.

Hey! On my laptop, I've tried:
1) portable version of OBS-studio from @mikewalsh on different puppies.
2) Also I tried OBS installed from PPM in FossaPUP and
3) OBS installed from quick installation in FossaPup
4) finally I tried OBS out of the box in the latest version of EasyOS

[Phoenix]

The primary issue here is trying to run OBS on an outdated platform. The latest OBS requires OpenGL 3.3 or higher. Software rendering, or changing the version string to mimic a supported version might work initially, but it might produce unexpected results.

[bigpup]

Have you tried OBS-Studio offered here:
viewtopic.php?t=4152

Do not use what is in the first post.

Look at the different posts in this topic.
Several packages of OBS-Studio are offered for different Puppy versions.

[williams2]

You can force it to ignore the OpenGl version number like this:

Code: Select all

export MESA_GL_VERSION_OVERRIDE=4.6
export MESA_GLSL_VERSION_OVERRIDE=460
obs

But it might not work properly.
It might crash frequently.
It might not start at all.

[Maybe]

You can force it to ignore the OpenGl version number like this:

Code: Select all

export MESA_GL_VERSION_OVERRIDE=4.6
export MESA_GLSL_VERSION_OVERRIDE=460
obs

But it might not work properly.
It might crash frequently.
It might not start at all.

Hooray! Thank you @williams2 so much! It worked!!!!

I did it on EasyOS and OBS started up! But it looks like these commands will need to be entered every time before starting OBS.

[mikewalsh]

@Maybe :-

Perhaps - instead of "forcing" OBS to run in an environment where it clearly isn't happy - it might be better to run a dedicated Puppy where it's already known to work correctly?

Puppies don't take up a lot of room, after all....

Just a thought.

Mike.

[norgo]

Perhaps - instead of "forcing" OBS to run in an environment where it clearly isn't happy - it might be better to run a dedicated Puppy where it's already known to work correctly?

[Maybe]

@Maybe :-

Perhaps - instead of "forcing" OBS to run in an environment where it clearly isn't happy - it might be better to run a dedicated Puppy where it's already known to work correctly?

Puppies don't take up a lot of room, after all....

Just a thought.

Mike.

It looks like the drivers for my Intel Corporation Core Processor Integrated Graphics Controller [8086: 0046] (rev 02) do not support the OpenGL version required for OBS studio. For this reason, no matter what Puppy I try OBS-studio on, it always gives an error due to the driver.

Вот здесь viewtopic.php?p=45377#p45377 @williams2 suggests to deceive the system and inform before starting OBS that OpenGL version is not 2.1 like mine, but 4.6.

How would I upgrade OpenGL to 3.0 or 3.1? It would be great!

[Phoenix]

It would be best to look it up at Intel's site, with your CPU model or integrated graphic device name. For example, the GM45 Chipset on my Toshiba Satellite is stated by Intel to only support up to OpenGL 2.1. Modern puppies, such as BionicPup64 already come with the drivers needed for OpenGL 3+.

[BarryK]

You can force it to ignore the OpenGl version number like this:

Code: Select all

export MESA_GL_VERSION_OVERRIDE=4.6
export MESA_GLSL_VERSION_OVERRIDE=460
obs

But it might not work properly.
It might crash frequently.
It might not start at all.

Hooray! Thank you @williams2 so much! It worked!!!!

I did it on EasyOS and OBS started up! But it looks like these commands will need to be entered every time before starting OBS.

The OBS Studio in EasyOS was compiled in EasyOS, so is compatible with all of the software, including the openGL that ships in EasyOS.

If you are running EasyOS, and have played with other OBS's, it might be a good idea to get rid of all traces of them before using the inbuilt OBS Studio in EasyOS 3.1.17. You could chose to erase the session, via the Shutdown menu, or delete where ever it has created something ...let's see... /root/.config/obs-studio

[Maybe]

You can force it to ignore the OpenGl version number like this:

Code: Select all

export MESA_GL_VERSION_OVERRIDE=4.6
export MESA_GLSL_VERSION_OVERRIDE=460
obs

But it might not work properly.
It might crash frequently.
It might not start at all.

Hooray! Thank you @williams2 so much! It worked!!!!

I did it on EasyOS and OBS started up! But it looks like these commands will need to be entered every time before starting OBS.

The OBS Studio in EasyOS was compiled in EasyOS, so is compatible with all of the software, including the openGL that ships in EasyOS.

If you are running EasyOS, and have played with other OBS's, it might be a good idea to get rid of all traces of them before using the inbuilt OBS Studio in EasyOS 3.1.17. You could chose to erase the session, via the Shutdown menu, or delete where ever it has created something ...let's see... /root/.config/obs-studio

Network controller [0280]: Intel Corporation Centrino Ultimate-N 6300 [8086:4238] (rev 35)
• Kernel Driver: iwlwifi
• Memory Used: 119.31 KB
• Path: /lib/modules/4.9.58/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko
• Description: Intel(R) Wireless WiFi driver for Linux

[davisbruce1996]

Hi Everyone,

It looks like the main issue is that your Intel HD Graphics (ILK) only supports up to OpenGL 2.1, while newer versions of OBS Studio require at least OpenGL 3.3. Setting the MESA_GL_VERSION_OVERRIDE environment variable is a workaround to bypass this check, but as others have mentioned, it may lead to instability or improper functioning.

Rather than forcing an unsupported OpenGL version, I'd recommend one of the following:

Use an older version of OBS Studio that is compatible with OpenGL 2.1. You can find legacy releases here: https://github.com/obsproject/obs-studio/releases
If possible, upgrade your graphics drivers to a version that supports OpenGL 3.3+. Check Intel's website for the latest compatible drivers for your specific GPU.
Use a Linux distribution that includes up-to-date Intel drivers out of the box, such as a recent version of Ubuntu or Fedora. This will likely give you OpenGL 3.3+ support without needing to install custom drivers.

For more detailed troubleshooting steps and information on getting OBS Studio working on Linux, check out my OBS Studio on Linux guide:

https://www.obsstudio.net/obs-studio-linux-guide/