[BUG] Intel Arc QSV broken again (qsv=qs@va → child device handle -17) on 12.1+ / 12.2 tags (worked on 12.0ubu2604-ls48)
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 48/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- docker, dockerfile, linux
- Área
- devops
Línea de trabajo
Start by comparing the Jellyfin image and bundled FFmpeg changes between the reported working 12.0ubu2604-ls48 tag and the failing 12.1/12.2 tags. Reproduce the supplied ffmpeg device initialization command in the container with the Arc A310 passed through, then trace the QSV initialization failure; done means QSV device creation and hardware transcoding work on the affected tags.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
On linuxserver/jellyfin tags 12.1ubu2604-ls51 and 12.2ubu2604-ls5x (tested ls52, ls53, ls54), Intel Quick Sync fails to initialize on an Intel Arc A310.
VA-API opens successfully, but creating the QSV device from it fails:
[QSV @ ...] Error setting child device handle: -17
Device creation failed: -1313558101.
Failed to set value 'qsv=qs@va' for option 'init_hw_device': Unknown error occurred
Error parsing global options: Unknown error occurred
This happens at device init, before any frames are processed. Playback that requires QSV therefore fails immediately.
Workaround that works: Switch Hardware Acceleration to VAAPI. OpenCL tone mapping also initializes correctly.
Expected Behavior
-init_hw_device vaapi=va:... -init_hw_device qsv=qs@va should succeed and allow full QSV hardware transcoding (including HDR→SDR), as it did on 12.0ubu2604-ls48.
Steps To Reproduce
Run lscr.io/linuxserver/jellyfin:12.2ubu2604-ls54 (or 12.1ubu2604-ls51) with Arc A310 devices passed through.
Enable QSV in Jellyfin.
Attempt any hardware transcode, or run the minimal test inside the container:
/usr/lib/jellyfin-ffmpeg/ffmpeg -hide_banner \
-init_hw_device vaapi=va:,driver=iHD \
-init_hw_device qsv=qs@va \
-f lavfi -i nullsrc=s=640x360:d=1 -frames:v 1 -f null -
Environment
OS: TrueNAS Scale 25.10.x
GPU: Intel Arc A310 (Alchemist)
Image: lscr.io/linuxserver/jellyfin:12.2ubu2604-ls54 (also reproduces on 12.1ubu2604-ls51 and other 12.2 ls tags)
Last known good: lscr.io/linuxserver/jellyfin:12.0ubu2604-ls48 (verified working after #335)
Devices passed: Arc render node + card (not renderD128)
FFmpeg: 8.1.3-Jellyfin (bundled)
OpenCL: Works (Arc A310 detected, mapping functions present)
VAAPI: Works
CPU architecture
x86-64
Docker creation
services:
jellyfin:
container_name: jellyfin
image: lscr.io/linuxserver/jellyfin:${JELLYFIN_VERSION}
hostname: jellyfin
restart: unless-stopped
devices:
- ${ARC_CARD_2}
- ${ARC_RENDER_2}
environment:
- PUID=1000
- PGID=4000
- TZ=${TZ}
- DOCKER_MODS=linuxserver/mods:jellyfin-opencl-intel
volumes:
- ${JELLYFIN_CONFIG}:/config
- ${JELLYFIN_MEDIA}:/data/media:ro
- ${TESTMEDIALIB}:/data/testmedialib:ro
tmpfs:
- /tmptranscode:uid=1000,gid=4000,mode=1777,size=25g
networks:
proxy:
ipv4_address: 172.24.1.100
expose:
- 8096
labels:
- traefik.enable=true
- traefik.http.routers.jellyfin.entrypoints=websecure
- traefik.http.routers.jellyfin.rule=Host(`${JELLYFIN_DN}`)
- traefik.http.routers.jellyfin.tls=true
- traefik.http.services.jellyfin.loadbalancer.server.port=8096
security_opt:
- no-new-privileges:true
cpus: 8
mem_limit: 32g
jellyfin-jfa-go:
container_name: jellyfin-jfa-go
image: hrfee/jfa-go:${JFA_VERSION}
hostname: jellyfin-jfa-go
restart: unless-stopped
user: 568:568
environment:
- TZ=${TZ}
- JFA_SECRET=${JFA_SECRET}
- JFA_SERVER_NAME=jfa-go
volumes:
- ${JFA_CONFIG}:/data
- ${JELLYFIN_CONFIG}:/jf:ro
networks:
proxy: null
expose:
- 8056
depends_on:
- jellyfin
labels:
- traefik.enable=true
- traefik.http.routers.jfa-go.entrypoints=websecure
- traefik.http.routers.jfa-go.rule=Host(`${JFA_DN}`)
- traefik.http.routers.jfa-go.tls=true
- traefik.http.services.jfa-go.loadbalancer.server.port=8056
security_opt:
- no-new-privileges:true
cpus: 1
mem_limit: 2g
networks:
proxy:
name: proxy
external: true
x-dockge:
urls:
- https://hub.docker.com/r/linuxserver/jellyfin
- https://hub.docker.com/r/hrfee/jfa-go
Container logs
[QSV @ ...] Error setting child device handle: -17
Device creation failed: -1313558101.
Failed to set value 'qsv=qs@va' for option 'init_hw_device': Unknown error occurred
Error parsing global options: Unknown error occurred
- Lenguaje dominante
- Dockerfile
- Estrellas
- 909
- Forks
- 136
- Merge medio
- 4 h 31 min
- PR fusionados (30 d)
- 1
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de linuxserver/docker-jellyfin
-
no-issue-activity
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
linuxserver/docker-jellyfin#336 · 3 comentarios · 1 reacción ·
-
no-issue-activity
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
linuxserver/docker-jellyfin#341 · 2 comentarios ·
-
Critical Bug: Core migration initiated on V12 but resulted in 0-byte database truncation on UGOS ProAbiertono-issue-activity
Dificultad 5/5 Más de una semana Aptitud para principiantes 30/100
linuxserver/docker-jellyfin#339 · 6 comentarios ·
Todos los issues de linuxserver/docker-jellyfin
Issues similares
-
area: doc-engine area: infrastructure bug community-request
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
snapotter-hq/SnapOtter#4834 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
soroswap/token-list#125 ·
Los mantenedores suelen responder en 1 día
-
enhancement roadmap: next
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
nekko-labs/nekko-agent#2998 ·
Los mantenedores suelen responder en 1 día