[SOLVED]Black Screen Z590 Chipset i7-10700k Intel UHD 630 Graphics

[clD11]

I have setup a new machine and tried to install Linux Mint 20.1 Ulyssa but I am getting a black screen on boot. It works when booting into compatibility mode but says no hardware acceleration setup. I have run update manager and everything has been updated.

I have tried -

• Kernels 5.4.0-67 and 5.8.0-45

• Setting in grub:

  Code: Select all

   GRUB_CMDLINE_LINUX_DEFAULT="i915.alpha_support=1" 

CPU: i7-10700k
Mobo: Asus Prime M590-PLUS (Z590 Chipset)
Graphics: Intel UHD 630

inxi -Fxz

Code: Select all

System:
  Kernel: 5.8.0-45-generic x86_64 bits: 64 compiler: N/A
  Desktop: Cinnamon 4.8.6 Distro: Linux Mint 20.1 Ulyssa
  base: Ubuntu 20.04 focal
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <filter>
  Mobo: ASUSTeK model: PRIME Z590M-PLUS v: Rev 1.xx serial: <filter>
  UEFI: American Megatrends v: 0406 date: 01/15/2021
CPU:
  Topology: 8-Core model: Intel Core i7-10700K bits: 64 type: MT MCP
  arch: N/A L2 cache: 16.0 MiB
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  bogomips: 121596
  Speed: 1055 MHz min/max: 800/5100 MHz Core speeds (MHz): 1: 800 2: 800
  3: 801 4: 800 5: 800 6: 799 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800
  13: 800 14: 800 15: 800 16: 800
Graphics:
  Device-1: Intel vendor: ASUSTeK driver: N/A bus ID: 00:02.0
  Display: x11 server: X.Org 1.20.9 driver: fbdev unloaded: modesetting,vesa
  resolution: 1920x1080~77Hz
  OpenGL: renderer: llvmpipe (LLVM 11.0.0 256 bits) v: 4.5 Mesa 20.2.6
  direct render: Yes
Audio:
  Device-1: Intel vendor: ASUSTeK driver: snd_hda_intel v: kernel
  bus ID: 00:1f.3
  Device-2: Logitech HD Webcam C525 type: USB driver: snd-usb-audio,uvcvideo
  bus ID: 1-2.2:6
  Device-3: GN Netcom type: USB driver: jabra,snd-usb-audio,usbhid
  bus ID: 1-2.1:4
  Sound Server: ALSA v: k5.8.0-45-generic
Network:
  Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: 3.2.6-k
  port: efa0 bus ID: 00:1f.6
  IF: eno1 state: up speed: 100 Mbps duplex: full mac: <filter>
  Device-2: Edimax EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]
  type: USB driver: rtl8192cu bus ID: 1-9:3
  IF: wlx801f029bb7ed state: up mac: <filter>
Drives:
  Local Storage: total: 931.51 GiB used: 10.13 GiB (1.1%)
  ID-1: /dev/nvme0n1 vendor: Western Digital model: WDS100T1X0E-00AFY0
  size: 931.51 GiB
Partition:
  ID-1: / size: 423.74 GiB used: 10.10 GiB (2.4%) fs: ext4
  dev: /dev/nvme0n1p6
Sensors:
  System Temperatures: cpu: 31.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 311 Uptime: 36m Memory: 15.45 GiB used: 2.47 GiB (16.0%)
  Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17
  inxi: 3.0.38

What can I try to get this working?

[roblm]

Do you get the same output from the inxi command when running a live session using the Mint installation USB/DVD?

[SMG]

Similar issue with a Gigabyte Z490 with the same i7-10700K [solved] Black screen -booting from Mint 20.1 USB stick. That person decided to "solve" the issue by installing a GeForce GT 710 graphics card they had available and switching off the onboard graphics.

I later found a thread where the opposite was happening with Z490's -- the iGPU was working, but not the external GPU.

[arthurIII]

i have the same problem with ASUS PRIME Z590 A

when add nomodeset to grub i can boot but X falls to VGA 1024x768

Xorg.0.log.old (.old not the actual log file this is show that im using 1024x768)
shows that no outputs are connected

Code: Select all

No outputs definitely connected, trying again...

Seems the i915 driver cant access the edid information
Tried other Monitor and HMDI cable also tested on displayport
Same issue


snipset of Xorg.0.log.old

Code: Select all

[    20.647] (II) Loading sub module "glamoregl"
[    20.647] (II) LoadModule: "glamoregl"
[    20.647] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
[    20.650] (II) Module glamoregl: vendor="X.Org Foundation"
[    20.650] 	compiled for 1.20.10, module version = 1.0.1
[    20.650] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    20.669] (II) modeset(0): glamor X acceleration enabled on Mesa DRI Intel(R) UHD Graphics 630 (CML GT2)
[    20.669] (II) modeset(0): glamor initialized


[    20.669] (WW) modeset(0): No outputs definitely connected, trying again...


[    20.669] (WW) modeset(0): Unable to find connected outputs - setting 1024x768 initial framebuffer
[    20.669] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0)

[    20.669] (EE) modeset(0): No modes.

[    20.670] (II) UnloadModule: "modesetting"
[    20.670] (II) UnloadSubModule: "glamoregl"
[    20.670] (II) Unloading glamoregl
[    20.670] (EE) Screen(s) found, but none have a usable configuration.
[    20.670] (EE) 

Fatal server error:
[    20.670] (EE) no screens found(EE) 

[    20.670] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[    20.670] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    20.670] (EE) 
[    20.670] (EE) Server terminated with error (1). Closing log file.

[SMG]

Xorg.0.log.old (.old not the actual log file this is show that im using 1024x768)
shows that no outputs are connected

Since it seems your prior boot was one that failed, what does journalctl -b -1 | grep -i "drm\|i915" produce?
That command checks the log of the prior boot for anything with drm or i915 (the Intel driver) in it.

[arthurIII]

Since it seems your prior boot was one that failed, what does journalctl -b -1 | grep -i "drm\|i915" produce?

At the end you see

Mär 21 18:49:29 localhost kernel: i915 0000:00:02.0: [drm] Cannot find any crtc or sizes

journalctl -b -1 | grep -i "drm\|i915"

Mär 21 18:49:29 localhost kernel: i915 0000:00:02.0: drm_WARN_ON(!IS_PLATFORM(dev_priv, INTEL_TIGERLAKE) && !IS_PLATFORM(dev_priv, INTEL_ROCKETLAKE))
Mär 21 18:49:29 localhost kernel: WARNING: CPU: 10 PID: 370 at drivers/gpu/drm/i915/intel_pch.c:123 intel_pch_type+0x82e/0x950 [i915]
Mär 21 18:49:29 localhost kernel: Modules linked in: i915(+) i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec xhci_pci xhci_pci_renesas rc_core xhci_hcd crct10dif_pclmul drm crc32_pclmul ghash_clmulni_intel aesni_intel usbcore nvme nvme_core glue_helper crypto_simd cryptd wmi video pinctrl_tigerlake btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua msr efivarfs
Mär 21 18:49:29 localhost kernel: RIP: 0010:intel_pch_type+0x82e/0x950 [i915]
Mär 21 18:49:29 localhost kernel: intel_detect_pch+0x5b/0x2e0 [i915]
Mär 21 18:49:29 localhost kernel: i915_driver_probe+0x2c1/0xca0 [i915]
Mär 21 18:49:29 localhost kernel: ? i915_pci_probe+0x3f/0x150 [i915]
Mär 21 18:49:29 localhost kernel: i915_init+0x62/0x7c [i915]
Mär 21 18:49:29 localhost kernel: fb0: switching to inteldrmfb from EFI VGA
Mär 21 18:49:29 localhost kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
Mär 21 18:49:29 localhost kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Mär 21 18:49:29 localhost kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
Mär 21 18:49:29 localhost kernel: i915 0000:00:02.0: [drm] *ERROR* crtc 51: Can't calculate constants, dotclock = 0!
Mär 21 18:49:29 localhost kernel: i915 0000:00:02.0: drm_WARN_ON_ONCE(drm_drv_uses_atomic_modeset(dev))
Mär 21 18:49:29 localhost kernel: WARNING: CPU: 10 PID: 370 at drivers/gpu/drm/drm_vblank.c:728 drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x316/0x330 [drm]
Mär 21 18:49:29 localhost kernel: Modules linked in: i915(+) i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec xhci_pci xhci_pci_renesas rc_core xhci_hcd crct10dif_pclmul drm crc32_pclmul ghash_clmulni_intel aesni_intel usbcore nvme nvme_core glue_helper crypto_simd cryptd wmi video pinctrl_tigerlake btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua msr efivarfs
Mär 21 18:49:29 localhost kernel: RIP: 0010:drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x316/0x330 [drm]
Mär 21 18:49:29 localhost kernel: ? drm_property_destroy+0xd0/0xd0 [drm]
Mär 21 18:49:29 localhost kernel: drm_get_last_vbltimestamp+0xaa/0xc0 [drm]
Mär 21 18:49:29 localhost kernel: drm_reset_vblank_timestamp+0x5b/0xd0 [drm]
Mär 21 18:49:29 localhost kernel: drm_crtc_vblank_on+0x7b/0x130 [drm]
Mär 21 18:49:29 localhost kernel: intel_modeset_setup_hw_state+0xcde/0x1a10 [i915]
Mär 21 18:49:29 localhost kernel: ? drm_modeset_lock_all_ctx+0x120/0x2e0 [drm]
Mär 21 18:49:29 localhost kernel: intel_modeset_init_nogem+0x5f8/0x1da0 [i915]
Mär 21 18:49:29 localhost kernel: ? intel_irq_postinstall+0x1aa/0x500 [i915]
Mär 21 18:49:29 localhost kernel: i915_driver_probe+0x5ce/0xca0 [i915]
Mär 21 18:49:29 localhost kernel: ? i915_pci_probe+0x3f/0x150 [i915]
Mär 21 18:49:29 localhost kernel: i915_init+0x62/0x7c [i915]
Mär 21 18:49:29 localhost kernel: i915 0000:00:02.0: drm_WARN_ON(!pll_active)
Mär 21 18:49:29 localhost kernel: WARNING: CPU: 10 PID: 370 at drivers/gpu/drm/i915/display/intel_display.c:11181 hsw_get_pipe_config+0x10aa/0x1570 [i915]
Mär 21 18:49:29 localhost kernel: Modules linked in: i915(+) i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec xhci_pci xhci_pci_renesas rc_core xhci_hcd crct10dif_pclmul drm crc32_pclmul ghash_clmulni_intel aesni_intel usbcore nvme nvme_core glue_helper crypto_simd cryptd wmi video pinctrl_tigerlake btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua msr efivarfs
Mär 21 18:49:29 localhost kernel: RIP: 0010:hsw_get_pipe_config+0x10aa/0x1570 [i915]
Mär 21 18:49:29 localhost kernel: ? skl_ddi_pll_get_hw_state+0xa7/0xf0 [i915]
Mär 21 18:49:29 localhost kernel: ? verify_single_dpll_state+0x91/0x330 [i915]
Mär 21 18:49:29 localhost kernel: intel_atomic_commit_tail+0xa04/0x1380 [i915]
Mär 21 18:49:29 localhost kernel: intel_atomic_commit+0x333/0x3b0 [i915]
Mär 21 18:49:29 localhost kernel: intel_modeset_init+0x183/0x250 [i915]
Mär 21 18:49:29 localhost kernel: i915_driver_probe+0x5f4/0xca0 [i915]
Mär 21 18:49:29 localhost kernel: ? i915_pci_probe+0x3f/0x150 [i915]
Mär 21 18:49:29 localhost kernel: i915_init+0x62/0x7c [i915]
Mär 21 18:49:29 localhost kernel: WARNING: CPU: 10 PID: 370 at drivers/gpu/drm/i915/display/intel_display.c:14705 intel_atomic_commit_tail+0x133b/0x1380 [i915]
Mär 21 18:49:29 localhost kernel: Modules linked in: i915(+) i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec xhci_pci xhci_pci_renesas rc_core xhci_hcd crct10dif_pclmul drm crc32_pclmul ghash_clmulni_intel aesni_intel usbcore nvme nvme_core glue_helper crypto_simd cryptd wmi video pinctrl_tigerlake btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua msr efivarfs
Mär 21 18:49:29 localhost kernel: RIP: 0010:intel_atomic_commit_tail+0x133b/0x1380 [i915]
Mär 21 18:49:29 localhost kernel: intel_atomic_commit+0x333/0x3b0 [i915]
Mär 21 18:49:29 localhost kernel: intel_modeset_init+0x183/0x250 [i915]
Mär 21 18:49:29 localhost kernel: i915_driver_probe+0x5f4/0xca0 [i915]
Mär 21 18:49:29 localhost kernel: ? i915_pci_probe+0x3f/0x150 [i915]
Mär 21 18:49:29 localhost kernel: i915_init+0x62/0x7c [i915]
Mär 21 18:49:29 localhost kernel: [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
Mär 21 18:49:29 localhost kernel: i915 0000:00:02.0: [drm] Cannot find any crtc or sizes
Mär 21 18:49:29 dataserver systemd[1]: Starting Load Kernel Module drm...
Mär 21 18:49:29 dataserver systemd[1]: modprobe@drm.service: Succeeded.
Mär 21 18:49:29 dataserver systemd[1]: Finished Load Kernel Module drm.
Mär 21 18:49:29 dataserver kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
Mär 21 18:49:30 dataserver kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])

[SMG]

At the end you see

Mär 21 18:49:29 localhost kernel: i915 0000:00:02.0: [drm] Cannot find any crtc or sizes

I was expecting to see that or something similar, but I was not really expecting the rest. The issue here is not one about monitors, but about the i915 driver not working as we want it to work.

There is an expression in the English-speaking world when someone dies that others say "may they Rest In Peace" or RIP for short. When you see that in log messages, that means something crashed. It's there four times in what you posted.

Code: Select all

Mär 21 18:49:29 localhost kernel: RIP: 0010:intel_pch_type+0x82e/0x950 [i915]
Mär 21 18:49:29 localhost kernel: RIP: 0010:drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x316/0x330 [drm]
Mär 21 18:49:29 localhost kernel: RIP: 0010:hsw_get_pipe_config+0x10aa/0x1570 [i915]
Mär 21 18:49:29 localhost kernel: RIP: 0010:intel_atomic_commit_tail+0x133b/0x1380 [i915]

I will have to do some research to see how to best to get the driver to work as this is the first time I am seeing this issue with i915. It's possible others have seen it and will know what works and will post here.

[SMG]

I found this Ubuntu kernel team topic [PATCH 00/10][SRU][OEM-5.10][Unstable] Support CML-S CPU + TGP PCH which has the same message (below) as the first line in arthurIII's journalctl output.

Code: Select all

kernel: i915 0000:00:02.0: drm_WARN_ON(!IS_PLATFORM(dev_priv, INTEL_TIGERLAKE) && !IS_PLATFORM(dev_priv, INTEL_ROCKETLAKE)) 

In the email chain there is mention of receiving a patch from Intel. There is also a link to Bug #1909457: Support CML-S CPU + TGP PCH which indicates a fix was released for focal. Comment #5 on that bug report indicates, "This bug was fixed in the package linux - 5.10.0-14.15".

That kernel is available in the Ubuntu repository according to the Ubuntu Changelogs webpage. I believe it is the latest 5.10-oem kernel.

[clD11]

I am seeing the same issue -

journalctl -b -1 | grep -i "drm\|i915"

Code: Select all

Mar 22 17:10:46 Z590 kernel: i915 0000:00:02.0: drm_WARN_ON(!IS_PLATFORM(dev_priv, INTEL_TIGERLAKE))
Mar 22 17:10:46 Z590 kernel: WARNING: CPU: 15 PID: 267 at drivers/gpu/drm/i915/intel_pch.c:110 intel_pch_type+0x1ee/0x9a0 [i915]
Mar 22 17:10:46 Z590 kernel: Modules linked in: i915(+) i2c_algo_bit drm_kms_helper syscopyarea crct10dif_pclmul sysfillrect crc32_pclmul ghash_clmulni_intel sysimgblt aesni_intel fb_sys_fops cec fjes(-) crypto_simd rc_core intel_lpss_pci(+) cryptd nvme i2c_i801 glue_helper e1000e(+) intel_lpss drm nvme_core ahci(+) i2c_smbus idma64 xhci_pci libahci virt_dma xhci_pci_renesas wmi video pinctrl_tigerlake pinctrl_intel
Mar 22 17:10:46 Z590 kernel: RIP: 0010:intel_pch_type+0x1ee/0x9a0 [i915]
Mar 22 17:10:46 Z590 kernel:  intel_detect_pch+0x58/0x2b0 [i915]
Mar 22 17:10:46 Z590 kernel:  i915_driver_early_probe+0x193/0x310 [i915]
Mar 22 17:10:46 Z590 kernel:  i915_driver_probe+0x130/0x500 [i915]
Mar 22 17:10:46 Z590 kernel:  i915_pci_probe+0x5a/0x140 [i915]
Mar 22 17:10:46 Z590 kernel:  i915_init+0x61/0x75 [i915]
Mar 22 17:10:46 Z590 kernel: fb0: switching to inteldrmfb from EFI VGA
Mar 22 17:10:46 Z590 kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
Mar 22 17:10:46 Z590 kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Mar 22 17:10:46 Z590 kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Mar 22 17:10:46 Z590 kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
Mar 22 17:10:46 Z590 kernel: [drm:drm_calc_timestamping_constants [drm]] *ERROR* crtc 51: Can't calculate constants, dotclock = 0!
Mar 22 17:10:46 Z590 kernel: WARNING: CPU: 15 PID: 267 at drivers/gpu/drm/drm_vblank.c:717 drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x22f/0x330 [drm]
Mar 22 17:10:46 Z590 kernel: Modules linked in: i915(+) i2c_algo_bit drm_kms_helper syscopyarea crct10dif_pclmul sysfillrect crc32_pclmul ghash_clmulni_intel sysimgblt aesni_intel fb_sys_fops cec fjes(-) crypto_simd rc_core intel_lpss_pci cryptd nvme i2c_i801 glue_helper e1000e(+) intel_lpss drm nvme_core ahci i2c_smbus idma64 xhci_pci libahci virt_dma xhci_pci_renesas wmi video pinctrl_tigerlake pinctrl_intel
Mar 22 17:10:46 Z590 kernel: RIP: 0010:drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x22f/0x330 [drm]
Mar 22 17:10:46 Z590 kernel:  intel_crtc_get_vblank_timestamp+0x18/0x20 [i915]
Mar 22 17:10:46 Z590 kernel:  drm_get_last_vbltimestamp+0xad/0xc0 [drm]
Mar 22 17:10:46 Z590 kernel:  drm_reset_vblank_timestamp+0x63/0xd0 [drm]
Mar 22 17:10:46 Z590 kernel:  drm_crtc_vblank_on+0x84/0xe0 [drm]
Mar 22 17:10:46 Z590 kernel:  intel_crtc_vblank_on+0x3b/0x40 [i915]
Mar 22 17:10:46 Z590 kernel:  intel_modeset_setup_hw_state+0x1e3/0xf70 [i915]
Mar 22 17:10:46 Z590 kernel:  ? drm_modeset_lock+0x35/0xb0 [drm]
Mar 22 17:10:46 Z590 kernel:  ? drm_modeset_lock_all_ctx+0xa8/0xe0 [drm]
Mar 22 17:10:46 Z590 kernel:  ? drm_warn_on_modeset_not_all_locked.part.0+0x5e/0x90 [drm]
Mar 22 17:10:46 Z590 kernel:  intel_modeset_init+0x21d/0xae0 [i915]
Mar 22 17:10:46 Z590 kernel:  ? ibx_irq_postinstall+0x8d/0xb0 [i915]
Mar 22 17:10:46 Z590 kernel:  ? intel_irq_postinstall+0x398/0x6b0 [i915]
Mar 22 17:10:46 Z590 kernel:  i915_driver_probe+0x275/0x500 [i915]
Mar 22 17:10:46 Z590 kernel:  i915_pci_probe+0x5a/0x140 [i915]
Mar 22 17:10:46 Z590 kernel:  i915_init+0x61/0x75 [i915]
Mar 22 17:10:46 Z590 kernel: [drm] Initialized i915 1.6.0 20200515 for 0000:00:02.0 on minor 0
Mar 22 17:10:46 Z590 kernel: i915 0000:00:02.0: [drm] Cannot find any crtc or sizes
Mar 22 17:10:46 Z590 systemd[1]: Condition check resulted in Load Kernel Module drm being skipped.
Mar 22 17:10:46 Z590 kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
Mar 22 17:10:46 Z590 kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
Mar 22 17:10:46 Z590 systemd[1]: Condition check resulted in Load Kernel Module drm being skipped.

[clD11]

I have tried using both kernel 5.10.25-051025 and 5.11.8-051108-generic and have the same issue.

When updating installing the above kernels I got

5.11.8-051108-generic
update-initramfs: Generating /boot/initrd.img-5.11.8-051108-generic
W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for module i915

Does /lib/firmware/i915/cml_guc_49.0.1.bin refer to comet lake i.e. i7-10700k?

[SMG]

Here is some explanatory information on OEM Kernels.

I found the 5.10-oem kernels in Synaptic Package Manager. Package linux-image-5.10.0-1014-oem is the one specifically mentioned in the bug report I referenced earlier in this thread and is the last one showing on the Ubuntu Changelog page I linked.

However, it appears that is not the latest released. USN-4884-1: Linux kernel (OEM) vulnerabilities indicates on March 20th the 5.10.0.1017.18 was released. Here is the linux-oem-5.10 package in Ubuntu page with the change.log for 5.10.0-1017.18.

You can install the latest 5.10-oem with sudo apt install linux-oem-20.04b. The b must be appended to the end or you will end up installing the 5.6-oem kernel. It is in Synaptic Package Manager as linux-image-oem-20.04b if you prefer to install through Synaptic to avoid any typing errors.

The error messages clD11 and arthurIII are seeing are not exactly the same (arthurIII's list was slightly longer), but I'm hopeful that installing this kernel will be what is needed to get the i915 driver installed properly.

If for some reason the kernel change does not install the driver and you want to revert back to your current kernel, boot into grub and select the Advanced Options to boot into the 5.8 kernel and then delete the 5.10 kernel.

[SMG]

I have tried using both kernel 5.10.25-051025 and 5.11.8-051108-generic and have the same issue.

There are kernels and then there are Ubuntu maintained kernels. They are different branches of the multiple trees in the Linux kernel forest.

The kernel I referenced in the bug report is an Ubuntu maintained kernel. There are different branches to all the kernel versions, so it is not always true that a higher number version has more than what the lower number versions have even among the branches on the Ubuntu tree.

Try the specific kernel version branch I listed in my prior post. You can either install it and then boot into grub so you are specifically booting into that kernel, or you can remove the kernels you installed so the 5.10-oem is the highest number.

[clD11]

It appears 5.10.0-1017-oem installed using sudo apt install linux-oem-20.04b has fixed the problem and it is now running and dual screen using DP daisy chain is working

Thank you for your help SMG

[SMG]

It appears 5.10.0-1017-oem installed using sudo apt install linux-oem-20.04b has fixed the problem and it is now running and dual screen using DP daisy chain is working

Thank you for your help SMG

You're welcome. Please go to your first post in this thread and click the pencil icon to edit the title and add [SOLVED] at the beginning to help others in a similar situation.

Does /lib/firmware/i915/cml_guc_49.0.1.bin refer to comet lake i.e. i7-10700k?

My guess is that it would refer to Comet Lake. However, the error message for i915 in your log referenced Tiger Lake which I presume is tgl in that list. It's possible adding the firmware may have gotten those kernels to work, but I encourage people to try and stay with currently supported Ubuntu kernels when possible.

@arthurIII: If the 5.10-oem kernel does not clear the issues you were seeing, please post an updated journalctl -b -1 | grep -i "drm\|i915" output.

[random_string]

Ok. Newbie here. Sorry if this is a dumb question.

If one has the blank screen issue on a Z590 motherboard, how does one install the correct kernel without seeing the screen? I can boot into compatibility mode on the usb, but not sure how to change the kernel on the linux mint version on the hard drive.

I only recently jumped ship from windows, and I really don't want to go back.

[SMG]

If one has the blank screen issue on a Z590 motherboard, how does one install the correct kernel without seeing the screen? I can boot into compatibility mode on the usb, but not sure how to change the kernel on the linux mint version on the hard drive.

See if my explanation in this post answers your question. That thread is for a different MoBo, but the same graphics driver issue.

[i9user]

I have tried using both kernel 5.10.25-051025 and 5.11.8-051108-generic and have the same issue.

Well then clearly this cannot be a kernel issue right???

When updating installing the above kernels I got

5.11.8-051108-generic
update-initramfs: Generating /boot/initrd.img-5.11.8-051108-generic
W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module i915
Does /lib/firmware/i915/cml_guc_49.0.1.bin refer to comet lake i.e. i7-10700k?

I got the same error using mint 20.1! And updating to the very latest kernel did not solve the issue either. I did install ubuntu and Kubuntu and that works fine, but I do not like Unity and Kubuntu is very chaotic compared to Mint and there are way more crashes...

I just do not understand what the problem is ... to be honest. If installing the latest kernel does not solve the issue... then it might not be a kernel issue! That i915 driver is nothing new, so why would that be a problem??

Problem with fiddling with alternative kernels is that you run into those "missing module" issues, and that is just something that is not easy to solve for somebody who is not really into computers. I just want a stable system and I do not have time to tinker with the computer endlessly...

With me the problem is not so much a black screen.. the problem is that the monitor starts changing sources, obviously while there is just no more signal on the HDMI port.... I just do not get why a the intel graphics chipset should be the problem.... that chipset is nothing new right???

Somehow Kubuntu works, with kernel 5.11 running. The only thing I could do to prove it is not a kernel issue is by installing an older kernel and then seeing if works... but then you run into it already.. there is no easy way to install a kernel in (k)ubuntu.... in linux mint you just go into the update manager. In ubuntu you gotta use .deb packages, well I already tried that and got the aforementioned missing module error.... That just seems to be a package manager problem inherent in the .deb system then because Kubuntu is working just fine without having to search for missing drivers. So clearly the chipset is already mainstream!!

Up till now I have relied on Mint to just "make things work". If Mint does not work with my setup, then I really do not know what to to, because Kubuntu is just not as reliable as Mint, and I do not wanna change. but what on earth is causing these black screens?? If even mint with the latest kernel keeps doing it... maybe it is the missing driver for i915? But why doesn't the standard mint installer install that driver then, if that is the problem??? That driver is not new!! I just do not get it!

Somebody help!

[i9user]

Similar issue with a Gigabyte Z490 with the same i7-10700K [solved] Black screen -booting from Mint 20.1 USB stick. That person decided to "solve" the issue by installing a GeForce GT 710 graphics card they had available and switching off the onboard graphics.

Ok, so this cannot be an issue with the kernel, because z-490 has been around a long time... it is most probably an issue with the graphics drivers... but WHY.... the integrated graphics are on the chip and the i7 is nothing new either.. I have an i9-10850, and it gives black screens too... AARG. I really do not know what is going on.

Oh btw, I just checked the system info in Kubuntu and it DOES show that the graphics device is a cometlake-S GT2/UHD graphics 630, kernel module i915 and the driver that is installed is the mesa Intel UHD graphics 630 driver. So this is probably a kernel module issue and/or driver issue.

But why doesn't mint load the correct kernel module and driver then, where kubuntu does??? Usually Mint is master when it comes to installing all the right modules right out of the box, unlike Debian, which does not even manage to recognize my network card. I honestly gotta manually install a network card driver, and that is like the 3rd screen of the installation for debian... totally useless....

[SMG]

With me the problem is not so much a black screen.. the problem is that the monitor starts changing sources, obviously while there is just no more signal on the HDMI port...

You have a different problem which means you should be creating your own thread per forum rules. Section 5 of READ: How To Get Help! explains the data we need to be able to help you. Please provide that system data in the first post of your own thread.

I just do not understand what the problem is ... to be honest. If installing the latest kernel does not solve the issue... then it might not be a kernel issue! That i915 driver is nothing new, so why would that be a problem??

The i915 driver is constantly updated to meet the needs and requirements of newer Intel processors and to fix bugs. The name i915 is not new, but the i915 driver in not the same in every kernel version.

Oh btw, I just checked the system info in Kubuntu and it DOES show that the graphics device is a cometlake-S GT2/UHD graphics 630, kernel module i915 and the driver that is installed is the mesa Intel UHD graphics 630 driver. So this is probably a kernel module issue and/or driver issue.

But why doesn't mint load the correct kernel module and driver then, where kubuntu does???

Are you really asking why the Kubuntu release which is not even a week old and has the 5.11 kernel has the drivers for your newer hardware when Mint, which is based on Ubuntu 20.04 which came out a year ago and is based on the 5.4 kernel, does not? That is a rhetorical question, so please do not respond to it. Please follow the forum rules and create your own thread.

Edited to add: The Linux Mint 20.1 "Ulyssa" - Cinnamon (Edge, 64-bit) ISO was specifically created for those with newer hardware and it has the 5.8 kernel.

[i9user]

Please provide that system data in the first post of your own thread.

I already told you I have a I9-10850 with integrated UHD graphics intel 630. The fact that I have a z-590 chipset is obvious from the titel of this thread.

This is NOT a different problem, and that is why I am not starting a new thread. It is the same problem, and the fact that my monitor starts to look for a signal when the screen remains black is probably just becuase other people have different monitors, possibly without the automatic search feature.

The i915 driver is constantly updated to meet the needs and requirements of newer Intel processors and to fix bugs. The name i915 is not new, but the i915 driver in not the same in every kernel version.

Well. That is a good point. But the 10th generation chipset has been around for a long time, I really cannot imagine that the i915 module would not be supporting it. There are windows drivers which supported gen 10 already in the beginning of 2020. But it cannot be totally ruled out, I agree. However, that edge version that you linked doesn't work either.

Are you really asking why the Kubuntu release which is not even a week old and has the 5.11 kernel has the drivers for your newer hardware when Mint, which is based on Ubuntu 20.04 which came out a year ago and is based on the 5.4 kernel, does not? That is a rhetorical question, so please do not respond to it. Please follow the forum rules and create your own thread.

I am really doubting that the problem is an old i915 driver. I do not have a 11th gen processor, I have a 10th and they have been around for a longer time. Is there a way to check which version of the i915 driver is used in mint 20.1??

I already used the edge version, I have the 5.11 kernel, i915 driver installed, mesa driver installed, just like in the (k)ubuntu version. The solution that was given above (sudo apt install linux-oem-20.04b) just installs a different kernel, but I already installed an even newer kernel in mint, and it still does not work. It must be some other factor... something that ubuntu put in, and mint does not. Like I said, unlikely that the update of the i915 driver would be so slow, because 10th gen has been around since ages.. So I really do not get it. Unless there is a way to find out which gen of the 630 graphics set is supported by the module used by mint 20.1...

Edited to add: The Linux Mint 20.1 "Ulyssa" - Cinnamon (Edge, 64-bit) ISO was specifically created for those with newer hardware and it has the 5.8 kernel.

Thanks for the suggestion...