ensnare

Members
  • Posts

    33
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

ensnare's Achievements

Newbie

Newbie (1/14)

1

Reputation

  1. That worked, thanks. I added a dummy HDMI key to the on-board GPU and now both are working. Also as a follow-up for anyone else enabling a UHD 720/750 iGPU, I added these two lines to: /boot/config/modprobe.d/i915.conf options i915 force_probe=4c8a options i915 enable_guc=2 The second was required to enable hardware VP9 encoding and additional HEVC encoding profiles root@9362b3a147fb:~# vainfo error: XDG_RUNTIME_DIR not set in the environment. error: can't connect to X server! libva info: VA-API version 1.11.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_11 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.11 (libva 2.11.0) vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 21.1.3 (bec8e13) vainfo: Supported profile and entrypoints VAProfileNone : VAEntrypointVideoProc VAProfileNone : VAEntrypointStats VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Simple : VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointFEI VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointFEI VAProfileH264High : VAEntrypointEncSliceLP VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointFEI VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointFEI VAProfileHEVCMain : VAEntrypointEncSliceLP VAProfileHEVCMain10 : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointEncSlice VAProfileHEVCMain10 : VAEntrypointEncSliceLP VAProfileVP9Profile0 : VAEntrypointVLD VAProfileVP9Profile0 : VAEntrypointEncSliceLP VAProfileVP9Profile1 : VAEntrypointVLD VAProfileVP9Profile1 : VAEntrypointEncSliceLP VAProfileVP9Profile2 : VAEntrypointVLD VAProfileVP9Profile2 : VAEntrypointEncSliceLP VAProfileVP9Profile3 : VAEntrypointVLD VAProfileVP9Profile3 : VAEntrypointEncSliceLP VAProfileHEVCMain12 : VAEntrypointVLD VAProfileHEVCMain12 : VAEntrypointEncSlice VAProfileHEVCMain422_10 : VAEntrypointVLD VAProfileHEVCMain422_10 : VAEntrypointEncSlice VAProfileHEVCMain422_12 : VAEntrypointVLD VAProfileHEVCMain422_12 : VAEntrypointEncSlice VAProfileHEVCMain444 : VAEntrypointVLD VAProfileHEVCMain444 : VAEntrypointEncSliceLP VAProfileHEVCMain444_10 : VAEntrypointVLD VAProfileHEVCMain444_10 : VAEntrypointEncSliceLP VAProfileHEVCMain444_12 : VAEntrypointVLD VAProfileHEVCSccMain : VAEntrypointVLD VAProfileHEVCSccMain : VAEntrypointEncSliceLP VAProfileHEVCSccMain10 : VAEntrypointVLD VAProfileHEVCSccMain10 : VAEntrypointEncSliceLP VAProfileHEVCSccMain444 : VAEntrypointVLD VAProfileHEVCSccMain444 : VAEntrypointEncSliceLP VAProfileAV1Profile0 : VAEntrypointVLD VAProfileHEVCSccMain444_10 : VAEntrypointVLD VAProfileHEVCSccMain444_10 : VAEntrypointEncSliceLP root@9362b3a147fb:~#
  2. Adding "i915.force_probe=4c8b" to "/boot/config/modprobe.d/i915.conf" worked for me, until I added an additional discrete Nvidia card, a Quadro RTX 4000, and installed the Nvidia Driver package. The Intel iGPU no longer appears in syslog or lspci, yet devices are created in /dev/dri. root@photon:/dev/dri# modprobe i915 root@photon:/dev/dri# lspci | grep i915 -i root@photon:/dev/dri# modprobe -r i915 root@photon:/dev/dri# modprobe i915 root@photon:/dev/dri# ls /dev/dri by-path/ card0 renderD128 root@photon:/dev/dri# intel_gpu_top No device filter specified and no discrete/integrated i915 devices found root@photon:/dev/dri# lspci -v | grep gpu -i root@photon:/dev/dri# lspci -v | grep nvidia -i 01:00.0 VGA compatible controller: NVIDIA Corporation TU104GL [Quadro RTX 4000] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device 12a0 Kernel driver in use: nvidia Kernel modules: nvidia_drm, nvidia 01:00.1 Audio device: NVIDIA Corporation TU104 HD Audio Controller (rev a1) Subsystem: NVIDIA Corporation Device 12a0 01:00.2 USB controller: NVIDIA Corporation TU104 USB 3.1 Host Controller (rev a1) (prog-if 30 [XHCI]) Subsystem: NVIDIA Corporation Device 12a0 01:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU104 USB Type-C UCSI Controller (rev a1) Subsystem: NVIDIA Corporation Device 12a0 root@photon:/dev/dri# lspci -v | grep vga -i 01:00.0 VGA compatible controller: NVIDIA Corporation TU104GL [Quadro RTX 4000] (rev a1) (prog-if 00 [VGA controller]) root@photon:/dev/dri# lsmod | grep i915 i915 1712128 0 video 45056 1 i915 iosf_mbi 16384 1 i915 i2c_algo_bit 16384 1 i915 intel_gtt 20480 1 i915 drm_kms_helper 163840 2 nvidia_drm,i915 drm 356352 4 drm_kms_helper,nvidia_drm,i915 i2c_core 45056 7 drm_kms_helper,i2c_algo_bit,nvidia,i2c_smbus,i2c_i801,i915,drm backlight 16384 3 video,i915,drm
  3. I am running Unraid 6.9.2. When I use Safari browser, and the color theme has been changed to black, the console launches another login window. To repeat bug: use Safari browser. Change Settings --> Display Settings --> Dynamix color theme to Black. Launch "console" from DOCKER tab on top. Even after restoring to the default White theme, the error persists. Clearing cookies, launching private tabs, etc.. does not work. Google Chrome and Firefox operate as expected.
  4. Yes, cleared cookies, tried private windows - even tried on a different machine that never accessed Unraid. Something weird going on with a non-reversible change
  5. I just did a fresh install on a new machine and it works on Safari. Once I enable the dynamix dark theme ("black") it breaks. Then when I revert to "white" it remains broken. Strange - any way to reset the appearance to defaults?
  6. Looks like an Unraid UI browser incompatibility bug as Safari was working on 6.8 but recently introduced in 6.9. What is the best way to report to Unraid team?
  7. sounds like a bug. do you happen to know the procedure to report it?
  8. Having an issue with Unraid 6.9.2 where when I click "console" from the docker page for a running container, a popup appears with a login window instead of the actual console. This happens in the latest version of Safari. I am not running an ad-blocker or anything like that. Any ideas?
  9. Very interested in replacing a FreeNAS box w/ Unraid running ZFS. Is it possible to get Quickassist (gzip-qat) hardware acceleration working? I'm using an Atom processor w/ integrated QAT acceleration, and offloading the compression has a significant impact on performance: https://github.com/openzfs/zfs/pull/5846
  10. Maybe this is a stupid question, but how do I set up a headless VM w/ GPU passthrough? Do I start with VNC to set it up, then change the GPU to the Nvidia card?
  11. Trying to create a headless VM that passes through an Nvidia GPU. I use the GPU for compute and not for display. Is there a way to create a VM where the VNC video interface is primary, and pass-through GPU a secondary video interface? When I try to do this the VM won't start.
  12. Super-helpful again, thanks. Is there is a way to hardcode a mac address when creating a container?
  13. This was super helpful. Thanks. I encountered the same call traces on br1. I don't really want to vlan my whole network, so I just gave up and went back to host/bridge networking. What a weird bug.
  14. Experiencing a delay when I open a terminal through the web console. The window opens to a black screen, and it takes 30-60 seconds until the bash prompt appears. Anyone experience something like this? No errors in syslog. Rebooting does not resolve.
  15. Is there another way to safely assign a static IP to a docker container?