alex711 Posted April 1 Share Posted April 1 (edited) I know i915 is supported so is there any way we could get the new UHD 750 i915 drivers supported in Unraid? Specifically the new Rocket Lake line of processors and the new UHD 750 IGP. Maybe I'm just doing it wrong, but trying to load the i915 drivers i get this error message: [ 636.077251] i915 0000:00:02.0: Your graphics device 4c8a is not properly supported by the driver in this kernel version. To force driver probe anyway, use i915.force_probe=4c8a module parameter or CONFIG_DRM_I915_FORCE_PROBE=4c8a configuration option, or (recommended) check for kernel updates. Edited April 1 by alex711 1 Quote Link to comment
ChatNoir Posted April 1 Share Posted April 1 Is there an available driver ? I think I read earlier that Intel did not yet provide that. I might have skimmed through the article too quick and be wrong. (plus it was an article in french, so not too much use here ) 1 Quote Link to comment
xXx Posted April 4 Share Posted April 4 (edited) Yo también estoy esperando. (UHD 730-I5 11400) [8086: 4c8b] 00: 02.0 Controlador compatible con VGA: Dispositivo Intel Corporation 4c8b (rev 04) Edited April 7 by xXx Quote Link to comment
SimonF Posted April 4 Share Posted April 4 Windows ones drop tomorrow. Not seen anything for linux yet. https://wccftech.com/intel-releases-first-graphics-card-driver-for-rocket-lake-desktop-cpus/ 1 Quote Link to comment
fahmietalife Posted April 5 Share Posted April 5 desperate for UHD750 to be supported by unraid..... 1 Quote Link to comment
SimonF Posted April 6 Share Posted April 6 (edited) 17 hours ago, fahmietalife said: desperate for UHD750 to be supported by unraid..... @xXxFound this, looks like support is already there, but needs to be triggered at present. You should be able to add to the i915 conf file in modprobe.d With Rocket Lake, the Linux support is all in order once again. But there is one sort of exception: the Gen12 Xe Graphics might not be working out-of-the-box depending upon your kernel. When I first booted up the Rocket Lake test system with Linux 5.12 + Mesa Git previously already installed, I was startled to find accelerated graphics not working... LLVMpipe was at play. This was a big surprise given Intel's track record and Gen12 Linux graphics support being out for a while now. Checking dmesg though quickly revealed that the PCI ID was still hidden behind the early support flag. Re-booting the system while having "i915.force_probe=4c8a" avoided the issue and accelerated graphics were quickly working. All was well on both the i5-11600K and i9-11900K processors when booting the stable Linux kernel with the force_probe option. While the patch to remove Rocket Lake from requiring the force probe has been on the mailing list for several months, as of writing it hasn't landed in the stable upstream Linux kernel. At the moment that is queued into DRM-Next ahead of Linux 5.13... We'll see if one of the "fixes" pull request soon removes this restriction. Some distribution kernels including the likes of Ubuntu are already carrying the patch for providing the Rocket Lake support out-of-the-box. I am not 100% sure if this is correct. But I think you should be able to add the following to i915.conf options i915 force_probe=4c8a Removal of support flag not in kernel as yet. Edited April 6 by SimonF 1 Quote Link to comment
arturovf Posted April 7 Share Posted April 7 On 4/4/2021 at 3:17 PM, xXx said: Yo también estoy esperando. (UHD 730- I5 11400) me too waiting support desperately ! Quote Link to comment
xXx Posted April 8 Share Posted April 8 (edited) Any news on the unRAID driver, Intel gpu ???. I'm sorry for my English Edited April 8 by xXx Quote Link to comment
SimonF Posted April 8 Share Posted April 8 Windows ones are here. https://downloadcenter.intel.com/download/30266/Intel-Graphics-Windows-10-DCH-Drivers Quote Link to comment
xXx Posted April 8 Share Posted April 8 16 minutes ago, SimonF said: Los de Windows están aquí. https://downloadcenter.intel.com/download/30266/Intel-Graphics-Windows-10-DCH-Drivers Thanks, but the ones I need are the ones from unRAID. Quote Link to comment
SimonF Posted April 8 Share Posted April 8 9 minutes ago, xXx said: Thanks, but the ones I need are the ones from unRAID. Have you tried adding options i915 force_probe=4c8a to file /boot/config/modprobe.d/i915.conf and rebooting? Quote Link to comment
xXx Posted April 8 Share Posted April 8 5 hours ago, SimonF said: Have you tried adding options i915 force_probe=4c8a to file /boot/config/modprobe.d/i915.conf and rebooting? Quote Link to comment
SimonF Posted April 8 Share Posted April 8 (edited) 46 minutes ago, xXx said: Just to confirm you have the following root@computenode:~# cat /boot/config/modprobe.d/i915.conf options i915 force_probe=4c8a root@computenode:~# I dont have a new gen cpu, but dont get any errors. root@computenode:~# modprobe -c | grep 4c8a options i915 force_probe=4c8a Edited April 8 by SimonF 1 Quote Link to comment
SimonF Posted April 8 Share Posted April 8 On 4/4/2021 at 9:17 PM, xXx said: [8086: 4c8b] 00: 02.0 Controlador compatible con VGA: Dispositivo Intel Corporation 4c8b (rev 04) Sorry just noticed looks like you have 4c8b, update to this. I was using the OP vers and didnt notice yours was different. Quote Link to comment
xXx Posted April 8 Share Posted April 8 I realized just when I made the capture, it is changed to 4c8b, but it keeps giving me the same error Quote Link to comment
ich777 Posted April 8 Share Posted April 8 24 minutes ago, xXx said: I realized just when I made the capture, it is changed to 4c8b, but it keeps giving me the same error Please try to append 'force_probe=4c8a' to your syslinux.config and reboot (if you do it like that then please remove the contents of the i915.conf file). Please don't double post, you also can mention me here. Your i915.conf file has to be empty or at least have only the middle line in it, the first and the last line are wrong. 1 1 Quote Link to comment
SimonF Posted April 8 Share Posted April 8 @xXx File should look like this. except change to 4c8b for your system. 1 Quote Link to comment
xXx Posted April 8 Share Posted April 8 30 minutes ago, ich777 said: Intente agregar 'force_probe = 4c8a' a su syslinux.config y reinicie (si lo hace así, elimine el contenido del archivo i915.conf). Por favor, no publiques dos veces, también puedes mencionarme aquí. Su archivo i915.conf debe estar vacío o al menos tener solo la línea media, la primera y la última línea son incorrectas. yes, I have added only one line: options i915 force_probe = 4c8b Sorry to mention in two, Quote Link to comment
SimonF Posted April 8 Share Posted April 8 What output to you get from lspci -v for your gpu. Example: 00:02.0 VGA compatible controller: Intel Corporation Device 9ba8 (rev 03) (prog-if 00 [VGA controller]) DeviceName: Onboard - Video Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7c88 Flags: bus master, fast devsel, latency 0, IRQ 127, IOMMU group 2 Memory at c2000000 (64-bit, non-prefetchable) [size=16M] Memory at a0000000 (64-bit, prefetchable) [size=256M] I/O ports at 5000 [size=64] Expansion ROM at 000c0000 [virtual] [disabled] [size=128K] 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) Kernel driver in use: i915 Kernel modules: i915 1 Quote Link to comment
xXx Posted April 8 Share Posted April 8 Hace 5 minutos, SimonF dijo: 00:02.0 VGA compatible controller: Intel Corporation Device 4c8b (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Device 4c8b Flags: bus master, fast devsel, latency 0, IRQ 159, IOMMU group 1 Memory at 6000000000 (64-bit, non-prefetchable) [size=16M] Memory at 4000000000 (64-bit, prefetchable) [size=256M] I/O ports at 5000 [size=64] Expansion ROM at 000c0000 [virtual] [disabled] [size=128K] 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) Kernel driver in use: i915 Kernel modules: i915 Quote Link to comment
xXx Posted April 8 Share Posted April 8 (edited) Yes now. Thanks a lot Edited April 8 by xXx It already works albeit half, when I use plex pass, it only transcodes H264 the integrated igpu, but if I run H265 it does not transcode the igpu 1 Quote Link to comment
ich777 Posted April 8 Share Posted April 8 55 minutes ago, xXx said: Yes now. Thanks a lot 1 hour ago, xXx said: force_probe = 4c8b You can also add this as said to your syslinux.conf file so that you don't have to do anything or create a file if you installed the Intel-GPU-TOP plugin. But I was wrong above you have to do it in this format: i915.force_probe=4c8b Simply append this to your syslinux.conf file and this is appended when the Intel-GPU-TOP plugin loads the drivers, so no need to create the file with the contents (Main -> Click on 'Flash' and append it like that and click Apply at the bottom): 57 minutes ago, xXx said: It already works albeit half, when I use plex pass, it only transcodes H264 the integrated igpu, but if I run H265 it does not transcode the igpu From what I know this is a problem with Plex and you can only solve this if you run a custom script but you have to run it on every update of the container otherwise it will stop working again. I would post an issue an the Plex Forums about that. 2 Quote Link to comment
ensnare Posted April 22 Share Posted April 22 (edited) 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 Edited April 22 by ensnare Quote Link to comment
SimonF Posted April 22 Share Posted April 22 (edited) I think on my motherboard, I had to set to iGPU other wise uses the pGPU(PEG). So you may need to check BIOS. root@computenode:~# lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Device 9ba8 (rev 03) 01:00.0 VGA compatible controller: NVIDIA Corporation GK106GL [Quadro K4000] (rev a1) This is for a MSI taken from a youtube video, you will need to change Primary from PEG or enable IGD Multi. Not sure which Motherboard you have. Edited April 22 by SimonF Quote Link to comment
ensnare Posted April 22 Share Posted April 22 (edited) 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:~# Edited April 22 by ensnare 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.