No Vulkan, and no Intel hardware video decoding #31

New issue

Closed

opened 2026-09-26 07:28:11 +08:00 by Breadway · 2 comments

Breadway commented

2026-09-26 07:28:11 +08:00

Owner

Problem

The packages comment (around lines 241-246 of iso/packages.x86_64) says Mesa covers VA-API. That's true for AMD (radeonsi), but Intel's VA-API driver is intel-media-driver (or libva-intel-driver for pre-Broadwell), which isn't installed. No Vulkan ICDs are shipped either (vulkan-radeon, vulkan-intel), so Vulkan apps, Steam and some Electron/Chromium GPU paths fall back or fail. The site says AMD and Intel "just work".

Fix

Add vulkan-radeon, vulkan-intel, intel-media-driver and vulkan-icd-loader (optional: lib32-* from multilib, since [multilib] is already enabled). Correct the comment.

Acceptance

vainfo shows a working driver on an Intel VM/host, and vulkaninfo --summary lists a device.

Source: BOS v0.6.2 source review (tag dated 2026-09-19); line numbers refer to that tree. Read AGENTS.md first. One issue per branch/PR. Add a CHANGELOG [Unreleased] entry.

## Problem The packages comment (around lines 241-246 of `iso/packages.x86_64`) says Mesa covers VA-API. That's true for AMD (radeonsi), but Intel's VA-API driver is `intel-media-driver` (or `libva-intel-driver` for pre-Broadwell), which isn't installed. No Vulkan ICDs are shipped either (`vulkan-radeon`, `vulkan-intel`), so Vulkan apps, Steam and some Electron/Chromium GPU paths fall back or fail. The site says AMD and Intel "just work". ## Fix Add `vulkan-radeon`, `vulkan-intel`, `intel-media-driver` and `vulkan-icd-loader` (optional: `lib32-*` from multilib, since `[multilib]` is already enabled). Correct the comment. ## Acceptance `vainfo` shows a working driver on an Intel VM/host, and `vulkaninfo --summary` lists a device. --- Source: BOS v0.6.2 source review (tag dated 2026-09-19); line numbers refer to that tree. Read AGENTS.md first. One issue per branch/PR. Add a CHANGELOG `[Unreleased]` entry.

Breadway added the

hardware

packages

graphics

labels

2026-09-26 07:28:12 +08:00

Breadway referenced this issue from a pull request that will close it,

2026-09-30 18:51:24 +08:00

No Vulkan, and no Intel hardware video decoding #72

Breadway commented

2026-09-30 18:51:28 +08:00

Author

Owner

#72

Added Intel VA-API and Intel/AMD Vulkan packages plus vulkaninfo, corrected the driver comment, and added changelog. Manifest assertions and diff checks pass; package names were verified against official Arch package pages. This worker has no /dev/dri, so hardware acceptance is explicitly outstanding and coordinated with the headless acceptance worker.

https://git.breadway.dev/Breadway/bos/pulls/72 Added Intel VA-API and Intel/AMD Vulkan packages plus vulkaninfo, corrected the driver comment, and added changelog. Manifest assertions and diff checks pass; package names were verified against official Arch package pages. This worker has no /dev/dri, so hardware acceptance is explicitly outstanding and coordinated with the headless acceptance worker.

Breadway commented

2026-09-30 23:50:23 +08:00

Author

Owner

Independent source review PASS at c9626098ac. The manifest includes Intel media driver, Intel/AMD Vulkan ICDs, Vulkan loader and diagnostic tools once each; the corrected comment distinguishes AMD Mesa VA-API from Intel's separate driver. Diff check passes and no CI statuses are configured. Intel vainfo and vulkaninfo hardware acceptance remain outstanding; package inclusion alone does not prove decoding or a working device. PR: #72

Independent source review PASS at c9626098acebb98c4d669e31e2f09ec644dcebdf. The manifest includes Intel media driver, Intel/AMD Vulkan ICDs, Vulkan loader and diagnostic tools once each; the corrected comment distinguishes AMD Mesa VA-API from Intel's separate driver. Diff check passes and no CI statuses are configured. Intel vainfo and vulkaninfo hardware acceptance remain outstanding; package inclusion alone does not prove decoding or a working device. PR: https://git.breadway.dev/Breadway/bos/pulls/72

Breadway closed this issue

2026-10-02 14:33:25 +08:00