Open konradmb opened 3 years ago
I am experiencing this same problem on the slightly older Ivy Bridge, here's the verbose log:
[2021:07:22:17:42:49]: Debug: EGL: [Mesa Project]: version [1.4]
[2021:07:22:17:42:49]: Debug: API's supported: [OpenGL OpenGL_ES ]
[2021:07:22:17:42:49]: Debug: GL: vendor: Intel Open Source Technology Center
[2021:07:22:17:42:49]: Debug: GL: renderer: Mesa DRI Intel(R) HD Graphics 4000 (IVB GT2)
[2021:07:22:17:42:49]: Debug: GL: version: 3.0 Mesa 21.1.5 - kisak-mesa PPA
[2021:07:22:17:42:49]: Debug: GL: shader: 1.30
[2021:07:22:17:42:49]: Info: Color coding [Rec. 601]
[2021:07:22:17:42:49]: Info: Color range: [JPEG]
libva info: VA-API version 1.7.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: va_openDriver() returns -1
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_6
libva info: va_openDriver() returns 0
[AVHWDeviceContext @ 0x559e61905e80] Format 0x32315659 -> yuv420p.
[AVHWDeviceContext @ 0x559e61905e80] Format 0x30323449 -> yuv420p.
[AVHWDeviceContext @ 0x559e61905e80] Format 0x3231564e -> nv12.
[AVHWDeviceContext @ 0x559e61905e80] Format 0x32595559 -> yuyv422.
[AVHWDeviceContext @ 0x559e61905e80] Format 0x59565955 -> uyvy422.
[AVHWDeviceContext @ 0x559e61905e80] Format 0x48323234 -> yuv422p.
[AVHWDeviceContext @ 0x559e61905e80] Format 0x58424752 -> rgb0.
[AVHWDeviceContext @ 0x559e61905e80] Format 0x58524742 -> bgr0.
[AVHWDeviceContext @ 0x559e61905e80] Format 0x30313050 -> p010le.
[AVHWDeviceContext @ 0x559e61905e80] VAAPI driver: Intel i965 driver for Intel(R) Ivybridge Desktop - 2.4.0.
[AVHWDeviceContext @ 0x559e61905e80] Driver not found in known nonstandard list, using standard behaviour.
[AVHWFramesContext @ 0x559e61915b40] Created surface 0x4000000.
[AVHWFramesContext @ 0x559e61915b40] Direct mapping possible.
[h264_vaapi @ 0x559e618f99c0] [2021:07:22:17:42:49]: Debug: vaapi vendor: Intel i965 driver for Intel(R) Ivybridge Desktop - 2.4.0
Input surface format is nv12.
[h264_vaapi @ 0x559e618f99c0] Using VAAPI profile VAProfileH264High (7).
[h264_vaapi @ 0x559e618f99c0] Using VAAPI entrypoint VAEntrypointEncSlice (6).
[h264_vaapi @ 0x559e618f99c0] Using VAAPI render target format YUV420 (0x1).
[h264_vaapi @ 0x559e618f99c0] Driver supports RC modes CQP, CBR, VBR.
[h264_vaapi @ 0x559e618f99c0] RC mode: CBR.
[h264_vaapi @ 0x559e618f99c0] RC target: 100% of 1000000 bps over 16 ms.
[h264_vaapi @ 0x559e618f99c0] RC buffer: 16666 bits, initial fullness 12499 bits.
[h264_vaapi @ 0x559e618f99c0] RC framerate: 60/1 (60.00 fps).
[h264_vaapi @ 0x559e618f99c0] Using intra and P-frames (supported references: 1 / 1).
[h264_vaapi @ 0x559e618f99c0] All wanted packed headers available (wanted 0xd, found 0x1f).
[h264_vaapi @ 0x559e618f99c0] Using nv12 as format of reconstructed frames.
[AVHWFramesContext @ 0x559e61917f00] Created surface 0x4000001.
[AVHWFramesContext @ 0x559e61917f00] Direct mapping possible.
[h264_vaapi @ 0x559e618f99c0] Using level 4.2.
[2021:07:22:17:42:49]: Error: GL: line 645: [00000502]
[2021:07:22:17:42:49]: Error: Pass 0: CheckFramebufferStatus() --> [0x00008CD7]
[2021:07:22:17:42:49]: Info: Encoder [vaapi] failed
So I have figured out the exact line of code causing the GL error, but I don't know enough about OpenGL to figure out why it doesn't work. Specifically, this:
ctx.FramebufferTexture(GL_FRAMEBUFFER, GL_COLOR_ATTACHMENT0 + x, tex, 0);
on line 295 in sunshine/platform/linux/vaapi.cpp
. The docs for the glBindTexture
function (which is what gets called under the covers here) seem to imply that we shouldn't be getting a Invalid Operation error here, but it's possible I just don't understand something.
Intel(R) Core(TM) i5-4200U CPU Renderer: Mesa DRI Intel(R) HD Graphics 4400 (HSW GT2)