I have the same issue. Brave was working perfectly until a couple weeks ago. Initially everything pointed to hardware acceleration and rendering. On further investigation and troubleshooting. Here is my summary via chatgpt:
1. Brave Rendering and GPU Acceleration Problems
Symptoms:
Brave fails to leverage hardware acceleration effectively.
Errors during GPU initialization:
GBM: "Failed to get fd for plane" errors, indicating problems with Generic Buffer Management (GBM) for rendering.
EGL: "eglCreateContext failed with EGL_BAD_ATTRIBUTE," pointing to unsupported configurations or driver mismatches.
Vulkan: "vkCreateInstance: Found no drivers!" indicates Vulkan runtime issues.
Implications:
Brave falls back to software rendering, significantly degrading performance.
Hardware-accelerated video decoding and rendering are unavailable.
2. Missing or Misconfigured VA-API Drivers
Symptoms:
vainfo reports: va_openDriver() returns -1 and "unknown libva error."
The critical file /usr/lib/aarch64-linux-gnu/dri/vc4_drv_video.so is missing.
Implications:
VA-API (Video Acceleration API) cannot initialize, preventing hardware-accelerated video decoding (e.g., H.264 and H.265).
The absence of vc4_drv_video.so limits the system's ability to leverage the Raspberry Pi's GPU for media tasks.
Related Logs:
Brave GPU logs show "Video Decode: Software Only" despite capable hardware.
3. GBM and DRM Issues
Symptoms:
Repeated errors: "Failed to export buffer to dma_buf."
DRM (Direct Rendering Manager) logs show potential driver or overlay misconfigurations.
Implications:
The GPU cannot allocate or manage buffers for compositing or rendering.
This issue breaks rendering pipelines that rely on GBM for hardware acceleration.
4. Vulkan Configuration Problems
Symptoms:
vulkaninfo shows skipped ICDs and no driver being loaded:
"libvulkan: No drivers could be loaded."
"vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER."
GPU capabilities (V3D 7.1.7) show limited Vulkan support (e.g., maxImageDimension1D is capped at 4096).
Implications:
Vulkan-based rendering or compute tasks fail.
Applications reliant on Vulkan (e.g., modern Brave pipelines) cannot function optimally.
5. Kernel and Overlay Configuration
Symptoms:
/boot/config.txt initially lacked or misconfigured dtoverlay=vc4-kms-v3d.
No hardware decoding or rendering without proper kernel overlay settings.
Implications:
Without the correct overlay, the GPU operates in a limited mode, breaking VA-API, Vulkan, and EGL pipelines.
6. Brave-Specific Issues
Symptoms:
Brave's "Graphite" backend was disabled with errors: Enabling Graphite on a not-yet-supported platform is disallowed for safety.
Extensions throw runtime errors: "Unchecked runtime.lastError."
Implications:
Brave-specific rendering optimizations (e.g., Graphite) are unavailable.
The browser’s fallback to software rendering suggests deeper compatibility issues with ARM64.
7. Debugging Findings
Tools and Commands Used:
vainfo: Confirms the absence of VA-API driver support.
vulkaninfo: Highlights Vulkan runtime issues and driver incompatibility.
Brave GPU Logs (brave://gpu): Reveal that hardware acceleration is either disabled or falls back to software rendering.
dmesg: Shows DRM and GBM-related kernel logs, highlighting buffer export failures.
ffmpeg: Confirms that hardware-accelerated video decoding is unavailable.
8. Attempts to Resolve
Steps Taken:
Driver Updates:
Installed the latest Mesa drivers, VA-API, and Vulkan tools (mesa-va-drivers, mesa-vulkan-drivers, libva).
Verified that all installed packages were the latest versions.
Overlay Configuration:
Ensured /boot/config.txt included dtoverlay=vc4-kms-v3d and gpu_mem=256.
Fallback Tests:
Forced Brave to use OpenGL (--use-gl=desktop) or LLVMpipe (LIBGL_ALWAYS_SOFTWARE=1).
Tested video decoding and rendering performance with FFmpeg and Chromium.
Reinstallation:
Reinstalled Brave and Raspberry Pi OS, confirming the issue persists even on a clean setup.
Compilation Consideration:
Explored the feasibility of compiling Brave locally to resolve compatibility issues.
Brave Rendering and Hardware Acceleration Issues on Raspberry Pi (RPi 5, ARM64, Vulkan/VA-API/GBM Problems)
-Hardware acceleration disabled.
-Missing VA-API driver (vc4_drv_video.so).
-Vulkan runtime errors.
-GBM/EGL buffer management failures.
Steps Taken:
List troubleshooting actions (e.g., driver updates, overlay adjustments, fallback tests).
Include logs (vainfo, vulkaninfo, brave://gpu, dmesg).
Environment:
Raspberry Pi 5.
OS: Raspberry Pi OS Bookworm (64-bit).
Brave Version: Include exact version.
Relevant configurations (e.g., /boot/config.txt settings).
Logs: Attach or link detailed logs:
Brave GPU logs.
Vulkan and VA-API outputs.
Relevant dmesg entries.
1. Brave Rendering and GPU Acceleration Problems
Symptoms:
Brave fails to leverage hardware acceleration effectively.
Errors during GPU initialization:
GBM: "Failed to get fd for plane" errors, indicating problems with Generic Buffer Management (GBM) for rendering.
EGL: "eglCreateContext failed with EGL_BAD_ATTRIBUTE," pointing to unsupported configurations or driver mismatches.
Vulkan: "vkCreateInstance: Found no drivers!" indicates Vulkan runtime issues.
Implications:
Brave falls back to software rendering, significantly degrading performance.
Hardware-accelerated video decoding and rendering are unavailable.
2. Missing or Misconfigured VA-API Drivers
Symptoms:
vainfo reports: va_openDriver() returns -1 and "unknown libva error."
The critical file /usr/lib/aarch64-linux-gnu/dri/vc4_drv_video.so is missing.
Implications:
VA-API (Video Acceleration API) cannot initialize, preventing hardware-accelerated video decoding (e.g., H.264 and H.265).
The absence of vc4_drv_video.so limits the system's ability to leverage the Raspberry Pi's GPU for media tasks.
Related Logs:
Brave GPU logs show "Video Decode: Software Only" despite capable hardware.
3. GBM and DRM Issues
Symptoms:
Repeated errors: "Failed to export buffer to dma_buf."
DRM (Direct Rendering Manager) logs show potential driver or overlay misconfigurations.
Implications:
The GPU cannot allocate or manage buffers for compositing or rendering.
This issue breaks rendering pipelines that rely on GBM for hardware acceleration.
4. Vulkan Configuration Problems
Symptoms:
vulkaninfo shows skipped ICDs and no driver being loaded:
"libvulkan: No drivers could be loaded."
"vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER."
GPU capabilities (V3D 7.1.7) show limited Vulkan support (e.g., maxImageDimension1D is capped at 4096).
Implications:
Vulkan-based rendering or compute tasks fail.
Applications reliant on Vulkan (e.g., modern Brave pipelines) cannot function optimally.
5. Kernel and Overlay Configuration
Symptoms:
/boot/config.txt initially lacked or misconfigured dtoverlay=vc4-kms-v3d.
No hardware decoding or rendering without proper kernel overlay settings.
Implications:
Without the correct overlay, the GPU operates in a limited mode, breaking VA-API, Vulkan, and EGL pipelines.
6. Brave-Specific Issues
Symptoms:
Brave's "Graphite" backend was disabled with errors: Enabling Graphite on a not-yet-supported platform is disallowed for safety.
Extensions throw runtime errors: "Unchecked runtime.lastError."
Implications:
Brave-specific rendering optimizations (e.g., Graphite) are unavailable.
The browser’s fallback to software rendering suggests deeper compatibility issues with ARM64.
7. Debugging Findings
Tools and Commands Used:
vainfo: Confirms the absence of VA-API driver support.
vulkaninfo: Highlights Vulkan runtime issues and driver incompatibility.
Brave GPU Logs (brave://gpu): Reveal that hardware acceleration is either disabled or falls back to software rendering.
dmesg: Shows DRM and GBM-related kernel logs, highlighting buffer export failures.
ffmpeg: Confirms that hardware-accelerated video decoding is unavailable.
8. Attempts to Resolve
Steps Taken:
Driver Updates:
Installed the latest Mesa drivers, VA-API, and Vulkan tools (mesa-va-drivers, mesa-vulkan-drivers, libva).
Verified that all installed packages were the latest versions.
Overlay Configuration:
Ensured /boot/config.txt included dtoverlay=vc4-kms-v3d and gpu_mem=256.
Fallback Tests:
Forced Brave to use OpenGL (--use-gl=desktop) or LLVMpipe (LIBGL_ALWAYS_SOFTWARE=1).
Tested video decoding and rendering performance with FFmpeg and Chromium.
Reinstallation:
Reinstalled Brave and Raspberry Pi OS, confirming the issue persists even on a clean setup.
Compilation Consideration:
Explored the feasibility of compiling Brave locally to resolve compatibility issues.
Brave Rendering and Hardware Acceleration Issues on Raspberry Pi (RPi 5, ARM64, Vulkan/VA-API/GBM Problems)
-Hardware acceleration disabled.
-Missing VA-API driver (vc4_drv_video.so).
-Vulkan runtime errors.
-GBM/EGL buffer management failures.
Steps Taken:
List troubleshooting actions (e.g., driver updates, overlay adjustments, fallback tests).
Include logs (vainfo, vulkaninfo, brave://gpu, dmesg).
Environment:
Raspberry Pi 5.
OS: Raspberry Pi OS Bookworm (64-bit).
Brave Version: Include exact version.
Relevant configurations (e.g., /boot/config.txt settings).
Logs: Attach or link detailed logs:
Brave GPU logs.
Vulkan and VA-API outputs.
Relevant dmesg entries.
Statistics: Posted by latlongpi — Fri Nov 29, 2024 12:53 am