February 24, 20224 yr Hi, I'm using Unraid 6.9.2 with Intel 12th gen 12600k which has UHD 770. After searching quite a while, I found a method saying about i915.force_probe=4680 and followed the instruction but it didn't work. In the syslog, below is all that looks about i915 (also attached full syslog) Starts with: Feb 23 04:07:33 Tower kernel: Linux version 5.10.28-Unraid (root@Develop) (gcc (GCC) 9.3.0, GNU ld version 2.33.1-slack15) #1 SMP Wed Apr 7 08:23:18 PDT 2021 Feb 23 04:07:33 Tower kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot i915.force_probe=4680 Feb 23 04:07:33 Tower kernel: x86/split lock detection: warning about user-space split_locks Feb 23 04:07:33 Tower kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Feb 23 04:07:33 Tower kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Feb 23 04:07:33 Tower kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Feb 23 04:07:33 Tower kernel: x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers' Feb 23 04:07:33 Tower kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Feb 23 04:07:33 Tower kernel: x86/fpu: xstate_offset[9]: 832, xstate_sizes[9]: 8 Feb 23 04:07:33 Tower kernel: x86/fpu: Enabled xstate features 0x207, context size is 840 bytes, using 'compacted' format. Feb 23 04:07:33 Tower kernel: BIOS-provided physical RAM map: omitted Feb 23 04:07:33 Tower kernel: percpu: Embedded 45 pages/cpu s145240 r8192 d30888 u262144 Feb 23 04:07:33 Tower kernel: pcpu-alloc: s145240 r8192 d30888 u262144 alloc=1*2097152 Feb 23 04:07:33 Tower kernel: pcpu-alloc: [0] 00 01 02 03 04 05 06 07 [0] 08 09 10 11 12 13 14 15 Feb 23 04:07:33 Tower kernel: Built 1 zonelists, mobility grouping on. Total pages: 8205059 Feb 23 04:07:33 Tower kernel: Policy zone: Normal Feb 23 04:07:33 Tower kernel: Kernel command line: BOOT_IMAGE=/bzimage initrd=/bzroot i915.force_probe=4680 Feb 23 04:07:33 Tower kernel: Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes, linear) Feb 23 04:07:33 Tower kernel: Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear) Feb 23 04:07:33 Tower kernel: mem auto-init: stack:off, heap alloc:off, heap free:off In BIOS it's set to use 'IGD'. I tried the other one 'PEG' but no difference. I tried using intel_gpu_top plugin with no luck. Along with this, I cannot boot into GUI mode, it just blinks a single underscore character after lots of messages that appear when you boot in the default mode. I also tried putting nomodeset into syslinux but didn't work. I just ignored it and decided not to use that mode at first, but it seems it's somehow related to this one too. (being not able to utilize iGPU). I thought it might be solved when the RC3 comes out but since no one was complaing about this, I might be the only one with this problem so I came up with idea that it might not be solved in RC3 and that is why I'm posting this. Edited February 25, 20224 yr by trick.tar attachment deletion
February 25, 20224 yr Post your diagnostics.zip file. Tools > Diagnostics > Download (make sure "Anonymize diagnostics" is checked to remove any personal info)
February 25, 20224 yr Author 32 minutes ago, smcw said: Post your diagnostics.zip file. Tools > Diagnostics > Download (make sure "Anonymize diagnostics" is checked to remove any personal info) Thanks for your reply! I just attached that file.
February 25, 20224 yr Community Expert Solution 4 hours ago, trick.tar said: Thanks for your reply! I just attached that file. System can see the card, but the support of this iGPU is not in the kernel on 6.9.2 you will need to be running 6.10rc2 00:02.0 VGA compatible controller [0300]: Intel Corporation AlderLake-S GT1 [8086:4680] (rev 0c) DeviceName: Onboard - Video Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d42]
February 25, 20224 yr Author 6 minutes ago, SimonF said: System can see the card, but the support of this iGPU is not in the kernel on 6.9.2 you will need to be running 6.10rc2 00:02.0 VGA compatible controller [0300]: Intel Corporation AlderLake-S GT1 [8086:4680] (rev 0c) DeviceName: Onboard - Video Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d42] Oooh it needed 6.10 even with the force probe trick. I didn't know that. Thank you so much for the clarification! Hope you have a great day!
February 25, 20224 yr Community Expert 17 minutes ago, trick.tar said: Oooh it needed 6.10 even with the force probe trick. I didn't know that. Thank you so much for the clarification! Hope you have a great day! The force probe is to initiate "pre-release" functions within the driver. It will be added as a standard support gpu at some point and the force probe will no longer be required. its just 6.9.2 doesn't have the driver with the prerelease support.
May 18, 20224 yr Specs: Intel 12700K (UHD770) Asus Z690 Maximus Hero Hey! I just installed 6.10 on a brand new system. I have been able to create a VM, passthrough my 3070 and system is running super smooth. As a side quest I wanted to create an Ubuntu VM with the igpu passthrough but I haven't been able to get it working. Since I already done this with windows on 6.9 with an older gen cpu (8th) I thought the process would be the same, but I'm not managing to get it working. I created the VM and installed windows and all the virtio drivers and all of that, when I go and switch VNC for the iGPU I've been able to install the display drivers, but they failed and after a reboot I get error 43. All of this was done via RDP Cuz I can't get any signal on the monitor. I tried with and without the vbios_gvt_uefi.rom and also passing through the audio device. No luck. Error 43 in device manager and no signal on my monitor. Hope someone can enlighten me, cuz it´s driving me crazy haha Here's the VM XML <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 11</name> <uuid>2e2ad6f5-6e87-4c33-fb14-2fe31eb70576</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="windows11.png" os="windowstpm"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-6.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram>/etc/libvirt/qemu/nvram/2e2ad6f5-6e87-4c33-fb14-2fe31eb70576_VARS-pure-efi-tpm.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='2' threads='2'/> <cache mode='passthrough'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 11/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Win11_English_x64v1.iso'/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.217.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:e4:fb:34'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> </tpm> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </source> <rom file='/mnt/user/isos/vbios/vbios_gvt_uefi.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> </domain> patos-pc-diagnostics-20220518-1946.zip
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.