• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support Troubleshooting QSV not working after restart

    Pages (2): 1 2 Next »

     
    • 0 Vote(s) - 0 Average

    QSV not working after restart

    After a restart of the host system (proxmox) hardware decoding does not seem to work anymore.
    Feuerqualle
    Offline

    Junior Member

    Posts: 3
    Threads: 2
    Joined: 2024 Jan
    Reputation: 0
    #1
    2024-01-13, 07:03 PM
    I recently rebooted my host system (Proxmox VE 8.0.4).
    This is where I am running my Jellyfin LXC (installed via this script: https://tteck.github.io/Proxmox/ ). I added hardware acceleration following the official documentation (although most of that was already done by the install script as I discovered while adding it). It was working for a while but after I restarted the host (unrelated issues) I got playback errors and the logs seem to imply that the decoder cannot be accessed:

    {"Protocol":0,"Id":"a10e8df8f4ba733cd250b95b274671ec","Path":"[episode].mkv","EncoderPath":null,"EncoderProtocol":null,"Type":0,"Container":"mkv,webm","Size":5009373696,"Name":"S01_E06","IsRemote":false>

    /usr/lib/jellyfin-ffmpeg/ffmpeg -analyzeduration 200M -ss 00:00:15.000 -init_hw_device vaapi=va:,driver=iHD,kernel_driver=i915 -init_hw_device qsv=qs@va -filter_hw_device qs -hwaccel vaapi -hwaccel_output_format vaapi -autorotate 0 -i >


    ffmpeg version 5.1.3-Jellyfin Copyright © 2000-2022 the FFmpeg developers
      built with gcc 11 (Ubuntu 11.4.0-1ubuntu1~22.04)
      configuration: --prefix=/usr/lib/jellyfin-ffmpeg --target-os=linux --extra-libs=-lfftw3f --extra-version=Jellyfin --disable-doc --disable-ffplay --disable-ptx-compression --disable-static --disable-libxcb --disable-sdl2 --disable-xli>
      libavutil      57. 28.100 / 57. 28.100
      libavcodec    59. 37.100 / 59. 37.100
      libavformat    59. 27.100 / 59. 27.100
      libavdevice    59.  7.100 / 59.  7.100
      libavfilter    8. 44.100 /  8. 44.100
      libswscale      6.  7.100 /  6.  7.100
      libswresample  4.  7.100 /  4.  7.100
      libpostproc    56.  6.100 / 56.  6.100
    [AVHWDeviceContext @ 0x55a3ff155240] No VA display found for any default device.
    Device creation failed: -22.
    Failed to set value 'vaapi=va:,driver=iHD,kernel_driver=i915' for option 'init_hw_device': Invalid argument
    Error parsing global options: Invalid argument

    but the device seems to be mounted:

    root@jellyfin:/dev/dri# ls       
    by-path  card0  renderD128

    and intel_gpu_top also returns my CPU (12thGen) as an available device although its utilization is at 0% along all categories even when attempting to play back a video.

    Would love some help on this, all other threads online point to issues specific to their setup where I don't see an immediate connection to my system.
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #2
    2024-01-13, 09:33 PM
    What kernel is your Proxmox currently running?
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    Feuerqualle
    Offline

    Junior Member

    Posts: 3
    Threads: 2
    Joined: 2024 Jan
    Reputation: 0
    #3
    2024-01-14, 08:57 PM (This post was last modified: 2024-01-14, 09:00 PM by Feuerqualle. Edited 2 times in total.)
    Proxmox is running on Debian 12 with the Linux kernel 6.2.16-15-pve x86_64.
    The Jellyfin container is build on a Ubuntu 22.04.3 LTS base (with the same kernel, I think that is shared between host and containers)
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #4
    2024-01-14, 09:19 PM
    On the host, go through the bare metal setup for Intel HWA.

    https://jellyfin.org/docs/general/admini...linux-host

    The official Jellyfin docker container contains all the needed Intel drivers, but I am pretty sure whatever you have going on doesn't.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    krukkpl
    Offline

    Junior Member

    Posts: 1
    Threads: 0
    Joined: 2024 Mar
    Reputation: 0
    Country:Poland
    #5
    2024-03-21, 08:42 AM
    Hello,
    I have similar setup and similar issue: QSV not working after Proxmox restart but only if Jellyfin LXC is auto-started without delay...
    If I start Jellyfin LXC manually some time after Proxmox boot - QSV works just fine.
    As a workaround I set 30sec delay for auto-starting Jellyfin container but... yeah... I would like to solve the root cause.
    Any ideas how to troubleshoot this?
    I have run mentioned methods when Jellyfin was in "corrupted" state but didn't find any obvious issue...
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #6
    2024-03-21, 07:54 PM
    (2024-03-21, 08:42 AM)krukkpl Wrote: Hello,
    I have similar setup and similar issue: QSV not working after Proxmox restart but only if Jellyfin LXC is auto-started without delay...
    If I start Jellyfin LXC manually some time after Proxmox boot - QSV works just fine.
    As a workaround I set 30sec delay for auto-starting Jellyfin container but... yeah... I would like to solve the root cause.
    Any ideas how to troubleshoot this?
    I have run mentioned methods when Jellyfin was in "corrupted" state but didn't find any obvious issue...

    That is very strange.  I'm not aware of any services specifically tied to Intel media drivers that LXC would need to wait on.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    Iacov
    Offline

    Member

    Posts: 64
    Threads: 22
    Joined: 2024 Feb
    Reputation: 0
    Country:Austria
    #7
    2024-04-01, 10:08 PM
    could anyone of you solve their respective issue? I'm in a similar position (just in a VM and not lxc) and can't wrap my head around what could be the root cause
    Lainol
    Offline

    Junior Member

    Posts: 2
    Threads: 0
    Joined: 2024 Apr
    Reputation: 0
    Country:Spain
    #8
    2024-04-05, 09:23 AM (This post was last modified: 2024-04-05, 10:07 AM by Lainol. Edited 1 time in total.)
    Same here, after restart QSV don't work, have to re-do the chmod, usermod and systemctl restart. Tried the delay method without success.
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #9
    2024-04-05, 10:50 AM
    Are both of you chmod-ing the /dev/dri devices? If that is the case, the proper solution is to add the user running the LXC to the render group. That will persist between reboots.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    Lainol
    Offline

    Junior Member

    Posts: 2
    Threads: 0
    Joined: 2024 Apr
    Reputation: 0
    Country:Spain
    #10
    2024-04-09, 02:59 PM
    (2024-04-05, 10:50 AM)TheDreadPirate Wrote: Are both of you chmod-ing the /dev/dri devices?  If that is the case, the proper solution is to add the user running the LXC to the render group.  That will persist between reboots.

    Thank so much for your advice! Maybe someone can try it and post instructions how to do this? I'm afraid I'm not smart enough to do this xd
    Pages (2): 1 2 Next »

    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode