September 10, 20232 yr Hello all, I just put together a new NAS using a Asrock N100 mini-ITX mainboard with an integrated GPU. Unraid runs just fine in headless mode using the web GUI. But when I connect a monitor, there's no HDMI signal if I want to boot into GUI or console. I can see the blue option box right after boot and the text running across the screen, but then the connection is lost. I can see that the i915 has been loaded under 'system devices' and I also installed intel_gpu_top, but no luck. The one thing that makes a difference is using 'nomodeset' in the config file. This gets me to a blinking cursor but still no GUI. Does anyone recognise the problem and can help me? Or is my 13th generation mainboard with the N100 chip still too new to be fully supported? Many thanks!
September 10, 20232 yr Community Expert 34 minutes ago, insurmountable-pretension4409 said: Hello all, I just put together a new NAS using a Asrock N100 mini-ITX mainboard with an integrated GPU. Unraid runs just fine in headless mode using the web GUI. But when I connect a monitor, there's no HDMI signal if I want to boot into GUI or console. I can see the blue option box right after boot and the text running across the screen, but then the connection is lost. I can see that the i915 has been loaded under 'system devices' and I also installed intel_gpu_top, but no luck. The one thing that makes a difference is using 'nomodeset' in the config file. This gets me to a blinking cursor but still no GUI. Does anyone recognise the problem and can help me? Or is my 13th generation mainboard with the N100 chip still too new to be fully supported? Many thanks! I suspect you will need to blacklist i915 for top to work or add force probe. what do you see in syslog for i915? This is the value for my 12600K if you run cat /var/log/syslog | grep i915 it should state force probe to use or enter blacklist in the modprobe.d file so intelgputop does it for you.
September 10, 20232 yr Author Thank you for looking into this. I tried force_probe=46d1 which is the ID for Alder Lake N. But unfortunately no luck. Same with blacklisting and using intelgputop. Syslog shows the following including some mysterious error codes ... root@tower:~# cat /var/log/syslog | grep i915 Sep 10 13:36:06 tower kernel: i915 0000:00:02.0: [drm] VT-d active for gfx access Sep 10 13:36:06 tower kernel: i915 0000:00:02.0: vgaarb: deactivate vga console Sep 10 13:36:06 tower kernel: i915 0000:00:02.0: [drm] Using Transparent Hugepages Sep 10 13:36:06 tower kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Sep 10 13:36:06 tower kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915]) Sep 10 13:36:06 tower kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adlp_dmc_ver2_16.bin (v2.16) Sep 10 13:36:06 tower kernel: i915 0000:00:02.0: [drm] GuC firmware i915/tgl_guc_70.bin version 70.5.1 Sep 10 13:36:06 tower kernel: i915 0000:00:02.0: [drm] HuC firmware i915/tgl_huc.bin version 7.9.3 Sep 10 13:36:06 tower kernel: i915 0000:00:02.0: [drm] HuC authenticated Sep 10 13:36:06 tower kernel: i915 0000:00:02.0: [drm] GuC submission enabled Sep 10 13:36:06 tower kernel: i915 0000:00:02.0: [drm] GuC SLPC enabled Sep 10 13:36:06 tower kernel: i915 0000:00:02.0: [drm] GuC RC: enabled Sep 10 13:36:06 tower kernel: mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915]) Sep 10 13:36:06 tower kernel: i915 0000:00:02.0: [drm] Protected Xe Path (PXP) protected content support initialized Sep 10 13:36:06 tower kernel: [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0 Sep 10 13:36:06 tower kernel: fbcon: i915drmfb (fb0) is primary device Sep 10 13:36:06 tower kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device Sep 10 13:36:21 tower kernel: i915 0000:00:02.0: [drm] *ERROR* Unexpected DP dual mode adaptor ID 7f Sep 10 13:36:27 tower kernel: i915 0000:00:02.0: [drm] *ERROR* Unexpected DP dual mode adaptor ID 7f Sep 10 13:36:46 tower kernel: i915 0000:00:02.0: [drm] *ERROR* Unexpected DP dual mode adaptor ID 7f Sep 10 13:36:59 tower kernel: i915 0000:00:02.0: [drm] *ERROR* Unexpected DP dual mode adaptor ID 7f root@tower:~# Any idea what's wrong here? Thank you again!
September 10, 20232 yr Community Expert 32 minutes ago, insurmountable-pretension4409 said: Thank you for looking into this. I tried force_probe=46d1 which is the ID for Alder Lake N. But unfortunately no luck. Same with blacklisting and using intelgputop. Syslog shows the following including some mysterious error codes ... root@tower:~# cat /var/log/syslog | grep i915 Sep 10 13:36:06 tower kernel: i915 0000:00:02.0: [drm] VT-d active for gfx access Sep 10 13:36:06 tower kernel: i915 0000:00:02.0: vgaarb: deactivate vga console Sep 10 13:36:06 tower kernel: i915 0000:00:02.0: [drm] Using Transparent Hugepages Sep 10 13:36:06 tower kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Sep 10 13:36:06 tower kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915]) Sep 10 13:36:06 tower kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adlp_dmc_ver2_16.bin (v2.16) Sep 10 13:36:06 tower kernel: i915 0000:00:02.0: [drm] GuC firmware i915/tgl_guc_70.bin version 70.5.1 Sep 10 13:36:06 tower kernel: i915 0000:00:02.0: [drm] HuC firmware i915/tgl_huc.bin version 7.9.3 Sep 10 13:36:06 tower kernel: i915 0000:00:02.0: [drm] HuC authenticated Sep 10 13:36:06 tower kernel: i915 0000:00:02.0: [drm] GuC submission enabled Sep 10 13:36:06 tower kernel: i915 0000:00:02.0: [drm] GuC SLPC enabled Sep 10 13:36:06 tower kernel: i915 0000:00:02.0: [drm] GuC RC: enabled Sep 10 13:36:06 tower kernel: mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915]) Sep 10 13:36:06 tower kernel: i915 0000:00:02.0: [drm] Protected Xe Path (PXP) protected content support initialized Sep 10 13:36:06 tower kernel: [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0 Sep 10 13:36:06 tower kernel: fbcon: i915drmfb (fb0) is primary device Sep 10 13:36:06 tower kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device Sep 10 13:36:21 tower kernel: i915 0000:00:02.0: [drm] *ERROR* Unexpected DP dual mode adaptor ID 7f Sep 10 13:36:27 tower kernel: i915 0000:00:02.0: [drm] *ERROR* Unexpected DP dual mode adaptor ID 7f Sep 10 13:36:46 tower kernel: i915 0000:00:02.0: [drm] *ERROR* Unexpected DP dual mode adaptor ID 7f Sep 10 13:36:59 tower kernel: i915 0000:00:02.0: [drm] *ERROR* Unexpected DP dual mode adaptor ID 7f root@tower:~# Any idea what's wrong here? Thank you again! Maybe experimemt with. Share Memory Allows you to configure the size of memory that is allocated to the integrated graphics processor when the system boots up. Configuration options: [Auto] [32M] [64M] [128M] [256M] [512M] [1024M] Options vary depending on the memory you use on your motherboard.
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.