-
unRAID plugin for iGPU SR-IOV support
Hi, Running unraid version 6.12.2 with an Intel® Core™ i5-13600K but I'm not having any luck since installing the plugin. The plugin settings list SR-IOV as supported but I don't have any vf's available to use. I've installed the plugin and rebooted with no luck. Here's my output of lspci -vs 00:02.0 00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-S GT1 [UHD Graphics 770] (rev 04) (prog-if 00 [VGA controller]) DeviceName: Onboard - Video Subsystem: Gigabyte Technology Co., Ltd Device d000 Flags: bus master, fast devsel, latency 0, IRQ 151, IOMMU group 0 Memory at 41000000 (64-bit, non-prefetchable) Memory at 50000000 (64-bit, prefetchable) I/O ports at 5000 Expansion ROM at 000c0000 [virtual] [disabled] Capabilities: [40] Vendor Specific Information: Len=0c <?> Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable+ 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [100] Process Address Space ID (PASID) Capabilities: [200] Address Translation Service (ATS) Capabilities: [300] Page Request Interface (PRI) Capabilities: [320] Single Root I/O Virtualization (SR-IOV) Kernel driver in use: i915 Kernel modules: i915 here's the output of dmesg | grep i915 [ 70.146936] i915: loading out-of-tree module taints kernel. [ 70.228321] i915 0000:00:02.0: [drm] VT-d active for gfx access [ 70.228338] i915 0000:00:02.0: vgaarb: deactivate vga console [ 70.228519] i915 0000:00:02.0: [drm] Using Transparent Hugepages [ 70.229118] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 70.230389] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915]) [ 70.231056] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adls_dmc_ver2_01.bin (v2.1) [ 70.322006] i915 0000:00:02.0: [drm] Missing GuC-Err-Cap reglist Class(1):Compute(4)! [ 70.322008] i915 0000:00:02.0: [drm] Missing GuC-Err-Cap reglist Instance(2):Compute(4)! [ 70.323120] i915 0000:00:02.0: [drm] Missing GuC-Err-Cap reglist Class(1):Compute(4)! [ 70.323121] i915 0000:00:02.0: [drm] Missing GuC-Err-Cap reglist Instance(2):Compute(4)! [ 70.323521] i915 0000:00:02.0: [drm] GuC firmware i915/tgl_guc_70.bin version 70.5.1 [ 70.323522] i915 0000:00:02.0: [drm] HuC firmware i915/tgl_huc.bin version 7.9.3 [ 70.323954] i915 0000:00:02.0: [drm] Missing GuC-Err-Cap reglist Class(1):Compute(4)! [ 70.323955] i915 0000:00:02.0: [drm] Missing GuC-Err-Cap reglist Instance(2):Compute(4)! [ 70.326961] i915 0000:00:02.0: [drm] HuC authenticated [ 70.327409] i915 0000:00:02.0: [drm] GuC submission enabled [ 70.327410] i915 0000:00:02.0: [drm] GuC SLPC enabled [ 70.327779] i915 0000:00:02.0: [drm] GuC RC: enabled [ 70.328522] mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915]) [ 70.328578] i915 0000:00:02.0: [drm] Protected Xe Path (PXP) protected content support initialized [ 70.329367] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0 [ 70.341265] i915 0000:00:02.0: [drm] Cannot find any crtc or sizes [ 70.341387] i915 0000:00:02.0: [drm] Cannot find any crtc or sizes and the output of cat /sys/devices/pci0000:00/0000:00:02.0/sriov_totalvfs just returns 0. Any idea what might be wrong here? Thanks!
-
[Support] Fantucie App's
Hi, I've been trying to log into the panel but no matter what I do I can't get past the error "An unexpected error was encountered while processing this request, please try again." I have the panel on the br0 network and it does connect to the database to do the initial database seeding. I've created my user as well but it seems no matter what I enter into the login page it will give me this error. I've tried clean reinstalls with no luck so I have no idea what the issue is, any help would be appreciated. - Edit The problem was my dns server for the docker container as I use unifi to force devices to use my pihole server but as the pterodactyl docker was on br0 it wasn't on my firewall's allowed ip range. I'm not sure how that causes the login page to not allow access but once I manually specified the dns for the docker container to my pihole server I was able to login without any issues.
Crunch41
Members
-
Joined
-
Last visited