• Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

dglb99's Achievements


Newbie (1/14)



  1. After removing the VM backup plugin everything is working as it should.
  2. Here are some pictures showing the scaling issue I am talking about. First picture is when the webui is bugged out, second is normal after a reboot.
  3. I am having the exact same issue. I upgraded from 6.9-RC2 and after a day or so part of the webui stops working just as you described. I could access dockers and vms but most of the settings and tools stuff cannot be clicked on. I am able to hit restart and it works fine after that. I also noticed that things are scaled up to be larger when this happens.
  4. I get to the low 60 degrees C under load. Low 50's is fine I wouldn't worry about it.
  5. Would you mind posting what the suggested fix was? I don't believe we have access to that channel.
  6. It looks like only one person got it working, everyone else is having issues, including the same as mine where /dev/dri shows up but the docker container cannot access VAAPI.
  7. Just wanted to add another report of /dev/dri showing up but VAAPI not being accessed inside the docker containers with my i5 10400. I plan on trying to get the new intel media-driver working once I get a chance.
  8. I'm starting to think that I am not the only one with quicksync issues on 10th gen intel (comet lake) cpus. I've found a few other posts of people having issues as well, and then I cam across this. From my limited knowledge of computing it looks like people had issues with the vaapi driver and comet lake processors, and they basically are saying comet lake isn't support and to use intel media-driver. Is it possible to see what intel driver unmanic is using? Or is that packaged into the unRAID kernel?
  9. Has anyone gotten Intel quicksync transcoding to work with 10th gen Intel? I have to use the 6.9 rc2 due to 2.5g lan drivers but I've really been struggling getting this to work.
  10. Yes, I have passed through the iGPU in the docker template per the docker template instructions using the extra parameters section. The card shows up under /dev/dri.
  11. I downloaded intel gpu top, intel gpu tools, and gpu statistics. I understand that with gpu statistics I don't need intel gpu tools, correct? Should I revert my changes to the go file? Or is there no harm in leaving them? From the FFMPEG Command Log it looks like it is failing because it can't access the intel gpu still. The iGPU should be the primary graphics adapter since there is no other gpu in the system. ffmpeg version 4.3 Copyright (c) 2000-2020 the FFmpeg developers built with gcc 7 (Ubuntu 7.5.0-3ubuntu1~18.04) configuration: --disable-debug --disable-doc --disable-ffplay --enable-ffprobe --enable-avresample --enable-cuvid --enable-gpl --enable-libaom --enable-libass --enable-libfdk_aac --enable-libfreetype --enable-libkvazaar --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libtheora --enable-libv4l2 --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvpx --enable-libxml2 --enable-libx264 --enable-libx265 --enable-libxvid --enable-nonfree --enable-nvdec --enable-nvenc --enable-openssl --enable-small --enable-stripping --enable-vaapi --enable-vdpau --enable-version3 libavutil 56. 51.100 / 56. 51.100 libavcodec 58. 91.100 / 58. 91.100 libavformat 58. 45.100 / 58. 45.100 libavdevice 58. 10.100 / 58. 10.100 libavfilter 7. 85.100 / 7. 85.100 libavresample 4. 0. 0 / 4. 0. 0 libswscale 5. 7.100 / 5. 7.100 libswresample 3. 7.100 / 3. 7.100 libpostproc 55. 7.100 / 55. 7.100 [AVHWDeviceContext @ 0x556aac880700] libva: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed [AVHWDeviceContext @ 0x556aac880700] Failed to initialise VAAPI connection: -1 (unknown libva error). Device creation failed: -5. Failed to set value '/dev/dri/renderD128' for option 'vaapi_device': Input/output error Error parsing global options: Input/output error
  12. How did you get quick sync going? I've been having a hard time getting it going myself. So far I have edited the go file to include "modprobe i915", added "--device=/dev/dri" to the docker container's extra parameters, and added the lines -vaapi_device /dev/dri/renderD128 -vf format=nv12|vaapi,hwupload to the additional command line options. Did I miss a step? As far as I was able to find that should be everything required.