Control: retitle -1 No display output on Intel NUC 12 on DP/HDMI on cold boot; works with CPU-integrated Intel Iris Xe (TB4)
On Saturday, 4 November 2023 10:19:49 CET kurom...@stodwa.org wrote: > On 2023-11-03 14:20, Diederik de Haas wrote: > > On Friday, 3 November 2023 13:49:01 CET Diederik de Haas wrote: > >> My findings are: > >> > 1. If I use Thunderbolt 4 output (usb-c at the back) everything works > >> > fine. > >> > 2. If I use one of DP or HDMI ports the issue occurs. > >> > > >> > Manual for this Intel NUC12 states that both DP and HDMI outputs are > >> > handled by Intel ARC A770M GPU, while Thunderbolt4 output is handled by > >> > CPU-integrated Intel Iris Xe. > > > > And does it really not boot or are you 'only' getting no display > > output? If the latter, can you ssh into your NUC and share `dmesg` output? > > Hopefully that'll give a clue as to why the DP/HDMI outputs aren't working > > properly. > > 2. That's a valid question :) It does boot after all, only display is stuck. Adjusted bug title accordingly. > I was able to get dmesg -> attached. > I don't remember if I mentioned that, but 'nomodeset' kernel param does > not help.. There are a few things that stood out to me from `dmesg`: [ 0.000000] x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks ... [ 2.977094] EDAC MC0: Giving out device to module igen6_edac controller Intel_client_SoC MC#0: DEV 0000:00:00.0 (INTERRUPT) [ 2.979900] EDAC MC1: Giving out device to module igen6_edac controller Intel_client_SoC MC#1: DEV 0000:00:00.0 (INTERRUPT) [ 2.979922] EDAC igen6 MC1: HANDLING IBECC MEMORY ERROR [ 2.979923] EDAC igen6 MC1: ADDR 0x7fffffffe0 [ 2.979925] EDAC igen6 MC0: HANDLING IBECC MEMORY ERROR [ 2.979926] EDAC igen6 MC0: ADDR 0x7fffffffe0 [ 2.980809] EDAC igen6: v2.5.1 Likely not relevant for this bug, but you may want to look into it anyway. [ 5.183228] NET: Registered PF_ALG protocol family [ 5.322597] i915 0000:03:00.0: [drm] *ERROR* Device is non-operational; MMIO access returns 0xFFFFFFFF! [ 5.325270] i915 0000:03:00.0: Device initialization failed (-5) [ 5.326526] i915: probe of 0000:03:00.0 failed with error -5 Pretty sure that *is* the relevant part. I _think_ it's best to get the upstream maintainers involved, but I don't know who they are. Hopefully one of the (actual) kernel-team members does know that. [ 66.579068] snd_hda_intel 0000:04:00.0: couldn't bind with audio component [ 66.579127] snd_hda_intel 0000:04:00.0: HSW/BDW HD-audio HDMI/DP requires binding with gfx driver My guess is that's a consequence of the earlier error. You can verify that by checking a 'normal' boot and it then likely won't have those lines.
signature.asc
Description: This is a digitally signed message part.
