(Solved) RocketLake-S GT1 [UHD Graphics 750] not working on LinuxMint 20.3

[blockhead47]

Has anyone been successful getting the Intel RocketLake-S GT1 [UHD Graphics 750] chipset working on MintLinux 20.?.
I have it working on kernel 5.11.0-46-generic x86_64 using a recommendation from this forum.
But support for that kernel ends next month.

I have googled for a solution but nothing I have tried has worked.
My efforts have mainly centered around trying newer kernels.

There are 2 symptoms, based on which kernel I try.
1) System boots, but is running in software rendering mode.
2) System does not boot and hangs on BIOS Logo screen.

Generally, if I attempt to boot the recovery kernel for symptom 2 above, the system will boot into software rendering mode.

Any suggestions would be appreciated.

Code: Select all

inxi -Fxxxrz
System:
  Kernel: 5.11.0-46-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
    Desktop: Cinnamon 5.2.7 tk: GTK 3.24.20 info: plank wm: muffin 5.2.0 vt: 7
    dm: LightDM 1.30.0 Distro: Linux Mint 20.3 Una base: Ubuntu 20.04 focal
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: PRIME Z590-A v: Rev 1.xx
    serial: <superuser required> UEFI: American Megatrends v: 1202
    date: 10/27/2021
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard K330
    serial: <filter> charge: 55% (should be ignored) rechargeable: yes
    status: Discharging
  Device-2: hidpp_battery_1 model: Logitech Wireless Mouse M510
    serial: <filter> charge: 55% (should be ignored) rechargeable: yes
    status: Discharging
CPU:
  Info: 8-core model: 11th Gen Intel Core i7-11700K bits: 64 type: MT MCP
    smt: enabled arch: Rocket Lake rev: 1 cache: L1: 640 KiB L2: 4 MiB
    L3: 16 MiB
  Speed (MHz): avg: 800 high: 801 min/max: 800/4900:5000 cores: 1: 801
    2: 801 3: 801 4: 801 5: 801 6: 801 7: 801 8: 801 9: 800 10: 801 11: 800
    12: 801 13: 800 14: 801 15: 801 16: 800 bogomips: 115200
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel RocketLake-S GT1 [UHD Graphics 750] vendor: ASUSTeK
    driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:4c8a class-ID: 0300
  Device-2: Logitech Webcam C260 type: USB driver: snd-usb-audio,uvcvideo
    bus-ID: 1-12:6 chip-ID: 046d:081a class-ID: 0102 serial: <filter>
  Display: x11 server: X.Org 1.20.13 driver: loaded: modesetting
    unloaded: fbdev,vesa resolution: 1: 1920x1080~60Hz 2: 1280x1024~60Hz
    s-dpi: 96
  OpenGL: renderer: Mesa Intel Graphics (RKL GT1) v: 4.6 Mesa 21.0.3
    direct render: Yes
Audio:
  Device-1: Intel Tiger Lake-H HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus-ID: 00:1f.3 chip-ID: 8086:43c8 class-ID: 0403
  Device-2: Logitech Webcam C260 type: USB driver: snd-usb-audio,uvcvideo
    bus-ID: 1-12:6 chip-ID: 046d:081a class-ID: 0102 serial: <filter>
  Sound Server-1: ALSA v: k5.11.0-46-generic running: yes
  Sound Server-2: PulseAudio v: 13.99.1 running: yes
Network:
  Device-1: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel
    port: N/A bus-ID: 02:00.0 chip-ID: 8086:15f3 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 9.54 TiB used: 3.95 TiB (41.4%)
  ID-1: /dev/sda vendor: SanDisk model: SSD PLUS 240GB size: 223.58 GiB
    speed: 6.0 Gb/s type: SSD serial: <filter> rev: 00RL temp: 32 C scheme: GPT
  ID-2: /dev/sdb vendor: Samsung model: SSD 850 EVO M.2 250GB
    size: 232.89 GiB speed: 6.0 Gb/s type: SSD serial: <filter> rev: 1B6Q
    scheme: GPT
  ID-3: /dev/sdc vendor: Seagate model: ST2000DM001-1CH164 size: 1.82 TiB
    speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: CC29 temp: 27 C
  ID-4: /dev/sdd vendor: Seagate model: ST2000DM008-2FR102 size: 1.82 TiB
    speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: 0001 temp: 29 C
  ID-5: /dev/sde type: USB vendor: Western Digital model: WD Elements 25A3
    size: 5.46 TiB type: N/A serial: <filter> rev: 1030 scheme: GPT
Partition:
  ID-1: / size: 36.42 GiB used: 12.63 GiB (34.7%) fs: ext4 dev: /dev/sdb5
  ID-2: /boot/efi size: 96 MiB used: 30.2 MiB (31.5%) fs: vfat
    dev: /dev/sdb1
  ID-3: /home size: 28.71 GiB used: 2.9 GiB (10.1%) fs: ext4 dev: /dev/sda1
Swap:
  ID-1: swap-1 type: file size: 1.72 GiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
Sensors:
  System Temperatures: cpu: 27.8 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: note: see --pkg apt: 2451
  Active apt repos in: /etc/apt/sources.list
    1: deb http://gmusicbrowser.org/deb ./
    2: deb [arch=amd64] http://download.virtualbox.org/virtualbox/debian eoan non-free contrib
  Active apt repos in: /etc/apt/sources.list.d/cappelikan-ppa-focal.list
    1: deb http://ppa.launchpad.net/cappelikan/ppa/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb http://packages.linuxmint.com una main upstream import backport
    2: deb http://mirrors.gigenet.com/ubuntuarchive focal main restricted universe multiverse
    3: deb http://mirrors.gigenet.com/ubuntuarchive focal-updates main restricted universe multiverse
    4: deb http://mirrors.gigenet.com/ubuntuarchive focal-backports main restricted universe multiverse
    5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
    6: deb http://archive.canonical.com/ubuntu/ focal partner
  Active apt repos in: /etc/apt/sources.list.d/scootersoftware.list
    1: deb https://www.scootersoftware.com/ bcompare4 non-free
  Active apt repos in: /etc/apt/sources.list.d/teamviewer.list
    1: deb https://linux.teamviewer.com/deb stable main
  Active apt repos in: /etc/apt/sources.list.d/tuxinvader-lts-mainline-focal.list
    1: deb http://ppa.launchpad.net/tuxinvader/lts-mainline/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
    1: deb [arch=amd64] https://repo.vivaldi.com/stable/deb/ stable main
Info:
  Processes: 393 Uptime: 17m wakeups: 6 Memory: 15.39 GiB
  used: 2.13 GiB (13.8%) Init: systemd v: 245 runlevel: 5 Compilers:
  gcc: 9.3.0 alt: 9 Shell: Bash v: 5.0.17 running-in: gnome-terminal
  inxi: 3.3.12

[SMG]

My efforts have mainly centered around trying newer kernels.

There are 2 symptoms, based on which kernel I try.
1) System boots, but is running in software rendering mode.
2) System does not boot and hangs on BIOS Logo screen.

Please give more specifics about what kernels you have tried and what the results are from each. Multiple 5.13 and 5.14-oem kernels are available for use with Linux Mint.

[blockhead47]

I have not kept good documentation on exactly what I have tried. Most all version of the kernels available through Update Manager plus linux-oem-20.04d.

I am willing to (re)try any kernel recommendations you might suggest and any additional troubleshooting procedures as well.

[SMG]

I just went and checked and found intel RocketLake UHD-750 Mint 20.2 - no driver support where the person said they got stuck on the ASUS BIOS screen when using the 5.13. That was back in November so they switched to using the 5.11.

So I would suggest trying the latest 5.14-oem again sudo apt install linux-oem-20.04d as perhaps that was the one which permitted you to boot, but was in software rendering mode.

If that happens, you could get log messages which would hopefully give us a clue as to what is happening. To get the boot messages related to the graphics run:

Code: Select all

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

and let us know the output.

[blockhead47]

5.14.0-1020-oem would only boot in recovery mode. Output of commands shown below. Trying to boot 5.14.0-1020-oem normally results is a hang at BIOS boot logo screen.

Code: Select all

$ uname -r
5.14.0-1020-oem

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

Jan 22 21:50:31 sys76 kernel: ata2.00: supports DRM functions and may not be fully accessible
Jan 22 21:50:31 sys76 kernel: ata2.00: supports DRM functions and may not be fully accessible
Jan 22 21:50:38 sys76 systemd[1]: Condition check resulted in Load Kernel Module drm being skipped.
Jan 22 21:50:38 sys76 systemd[1]: Condition check resulted in Load Kernel Module drm being skipped.
Jan 22 21:51:34 sys76 kernel: snd_hda_codec_hdmi hdaudioC0D2: No i915 binding for Intel HDMI/DP codec

I have the following kernels installed and available on my system. Only 5.11.0-46 boots normally in hardware rendering mode.

Code: Select all

aptitude search linux-image | grep "^i"
i  linux-image-5.11.0-46-generic - Signed kernel image generic
i A linux-image-5.14.0-1020-oem - Signed kernel image oem
i A linux-image-5.4.0-96-generic - Signed kernel image generic
i A linux-image-oem-20.04d - OEM Linux kernel image

[SMG]

5.14.0-1020-oem would only boot in recovery mode. Output of commands shown below. Trying to boot 5.14.0-1020-oem normally results is a hang at BIOS boot logo screen.

When one boots in recovery mode that automatically disables the graphics so the command I gave you would not give us any useful information.

However, if you try to boot and it hangs and then you boot into recovery (or you boot normally using the 5.11.0-46), we can try and get the info from the "hang" by running:

Code: Select all

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

The -1 says to go back and get the information from the prior boot cycle.

Or you can see if one of the 5.13 kernels was one which booted normally, but did not give you hardware rendering. If that happens you could use the original command I suggested:

Code: Select all

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

Without the -1 gives information from the current boot cycle.
With the -1 gives information from the prior boot cycle.
With -2 gives information from two boot cycles ago.

I have some ideas of what to try, but I'd rather see some error messages rather than blindly telling you to try something. It's getting late for me, but I will check back tomorrow.

[blockhead47]

ok - 5.4.0-96-generic boots normally into software rendering mode so here is the output from the commands.

Code: Select all

$ uname -r
5.4.0-96-generic

$ journalctl -b | grep -i "drm\|i915"
Jan 22 22:18:55 sys76 kernel: ata2.00: supports DRM functions and may not be fully accessible
Jan 22 22:18:55 sys76 kernel: ata2.00: supports DRM functions and may not be fully accessible
Jan 22 22:18:55 sys76 systemd[1]: Starting Load Kernel Module drm...
Jan 22 22:18:55 sys76 systemd[1]: modprobe@drm.service: Succeeded.
Jan 22 22:18:55 sys76 systemd[1]: Finished Load Kernel Module drm.

[blockhead47]

While I am awaiting any further replies, I think I will try the Edge version of Mint 20.3.

[SMG]

ok - 5.4.0-96-generic boots normally into software rendering mode so here is the output from the commands.

The 5.4 kernel was released long before UHD 750 came out. That kernel does not have the graphics drivers for Rocket Lake and never did. I'm actually surprised you were able to get any graphics with it.

We're going to need information from one of the kernels which is causing a problem.

While I am awaiting any further replies, I think I will try the Edge version of Mint 20.3.

That has one of the 5.13 kernels. The only difference between Edge and "regular" is the kernel version.

[SMG]

Please boot with the 5.14-oem kernel again. Give it some time to make sure things are truly stuck before killing the process and booting into either Recovery Mode or the 5.11 kernel. Then run the following in a terminal:

Code: Select all

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

That will get the information from the prior boot cycle. If that does not show us useful information, then we'll want to get all the info instead of just the drm and i915 info.

[blockhead47]

Understood. OK this is what I know:
Kernel 5.4.0-96 boots ok, but only in software rendering mode.
Kernel 5.11.0-46 boots ok and works in HARDWARE rendering mode. This is the kernel that I currently use. (Unsupported as of next month)
Any other kernel I have tried, including 5.14.0120-oem fails to boot and hangs at the BIOS boot logo screen.

So I only have 2 kernels that will boot up. 5.11 is the only on that boots with hardware rendering.

How do we proceed to troubleshoot this issue?

[blockhead47]

anticipating your next question:

Code: Select all

uname -r
5.11.0-46-generic

journalctl -b | grep -i "drm\|i915"
Jan 23 12:54:26 sys76 kernel: fb0: switching to inteldrmfb from EFI VGA
Jan 23 12:54:26 sys76 kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
Jan 23 12:54:26 sys76 kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Jan 23 12:54:26 sys76 kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/rkl_dmc_ver2_02.bin (v2.2)
Jan 23 12:54:26 sys76 kernel: [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
Jan 23 12:54:26 sys76 kernel: ata2.00: supports DRM functions and may not be fully accessible
Jan 23 12:54:26 sys76 kernel: ata2.00: supports DRM functions and may not be fully accessible
Jan 23 12:54:26 sys76 kernel: fbcon: i915drmfb (fb0) is primary device
Jan 23 12:54:26 sys76 kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
Jan 23 12:54:26 sys76 systemd[1]: Condition check resulted in Load Kernel Module drm being skipped.
Jan 23 12:54:26 sys76 kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
Jan 23 12:54:27 sys76 kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
Jan 23 12:54:30 sys76 systemd[1]: Condition check resulted in Load Kernel Module drm being skipped.

[SMG]

anticipating your next question:

I need to see the error messages of when the system is NOT working. Then when I see those error messages I can go investigate what a possible solution might be. Messages of when the system is working (as in the case of 5.11) or turned off (as in the case of 5.4 or using recovery mode) doesn't give me to go on.

Do you normally see grub when you boot? Are you not seeing grub and that is why you are telling me it is stuck on the BIOS logo screen?

Some people see the BIOS logo screen both before grub and after grub (twice during boot up), so I do not know the exact significance of you seeing that screen.

[blockhead47]

Code: Select all

I need to see the error messages of when the system is NOT working.

And there is the problem. I cannot get any kernel to boot (other than those mentioned below) so therefore we cannot see any error messages.

Do you normally see grub when you boot? Are you not seeing grub and that is why you are telling me it is stuck on the BIOS logo screen?

Yes I see the grub menu when I boot. I have a dual boot (Windows/LinuxMint) system. I see the BIOS logo screen before the grub menu selection screen. Then once again after I make the grub menu selection. This second time I see the BIOS logon screen (after selection the grub menu item to boot) is when it hangs, if I select a boot option other than Windows 10, kernel 5.11 (hardware rendering) or 5.4 (software rendering).

So I am not sure how we troubleshoot this issue as I can never get a kernel to boot, other that those mentioned above.
And that apparently does not help.

It is frustrating.

[SMG]

Yes I see the grub menu when I boot. I have a dual boot (Windows/LinuxMint) system. I see the BIOS logo screen before the grub menu selection screen. Then once again after I make the grub menu selection. This second time I see the BIOS logon screen (after selection the grub menu item to boot) is when it hangs

Good! This means the message to boot the operating system was sent and Mint booting has begun.

So I am not sure how we troubleshoot this issue as I can never get a kernel to boot, other that those mentioned above.
And that apparently does not help.

It is frustrating.

It is a very common misunderstanding that if you are not seeing something on the screen then the system is not working. It is 100% possible for the operating system to completely boot up and you never see anything on the screen. If you have ever heard the term "headless server" that is what they are, a computer booting and running with with no graphics.

The problem with your computer seems to be with the graphics (obviously), but just because there is no graphics does not mean nothing is happening. That is why I requested:

Please boot with the 5.14-oem kernel again. Give it some time to make sure things are truly stuck before killing the process and booting into either Recovery Mode or the 5.11 kernel. Then run the following in a terminal:

Code: Select all

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

That will get the information from the prior boot cycle. If that does not show us useful information, then we'll want to get all the info instead of just the drm and i915 info.

I want you to select that option in the grub menu for Linux Mint and stare at that BIOS logo knowing the computer is doing its thing to start Linux Mint (even though you can not see it doing that). I do not know how fast your computer normally is to get to the login screen (or the desktop if you automatically log in), but give it that much time before you kill the power and then boot with the 5.11 kernel so you can go get the log info from the "black screen" boot.

[blockhead47]

I do not know how fast your computer normally is to get to the login screen (or the desktop if you automatically log in), but give it that much time before you kill the power and then boot with the 5.11 kernel so you can go get the log info from the "black screen" boot.

System usually boots in under 1 minute. I have waited 5 minutes while it tried to boot the 5.14-oem kernel. So while I was looking and the "black screen" (BIOS logo) I went to another PC on my LAN and tried to ping this system with the graphics issue. No response. I think we can reasonably assume it is hung and not running like a "headless" server.

Do you agree? Or should I try something else?

[SMG]

System usually boots in under 1 minute. I have waited 5 minutes while it tried to boot the 5.14-oem kernel. So while I was looking and the "black screen" (BIOS logo) I went to another PC on my LAN and tried to ping this system with the graphics issue. No response. I think we can reasonably assume it is hung and not running like a "headless" server.

Do you agree? Or should I try something else?

Please boot into the 5.11 kernel and run the following command:
journalctl -b -1 | nc termbin.com 9999
It will return with a url address that you should post in your next reply. That command prints the journal log information of the prior boot cycle (the one which you stopped with the power button) and sends it to termbin.

I will be able to tell from it what kernel was used to know whether the system began booting or not.

[blockhead47]

ok here it is:
journalctl -b -1 | nc termbin.com 9999
https://termbin.com/aj7u

[SMG]

That is a boot cycle with the 5.11 kernel so it would seem the system is not booting. I am going through it anyways to see if there might be any clues.

In the meantime, I have searched for others with a similar issue. The person I mentioned earlier in this topic (with 5.13 and LM20.2) did file a Bug #1958347: kernel 5.13.0-25 - (linux Mint 20.3) - stuck at bios welcome screen after and it is listed as confirmed, but only that one person had it. (They have an ASUS PRIME Z590-P mobo while you have PRIME Z590-A.)

Considering how many people I helped with Rocket Lake last spring, the fact I'm finding very little mention of others having issues is leading me to believe this issue may relate to something other than the graphics.

I even searched the bug reports for mainline kernels, which I would assume would be a larger pool of users than just ones posting on this forum. I did find this one [Rocket Lake UHD 730] absent nomodeset, booting 5.14, 5.15 & 5.16rc hard locks at "Starting udev...." with >1 connected displays where the person also has an ASUS board. Discussion in that topic mentioned BIOS settings and also the fact that how many displays were attached seemed to make a difference. What is currently the last post indicates:

If I boot to the Grub menu with only one display connected, and connect another while Grub is waiting for a response, operation from then on is as expected for the remainder of the boot.

That person (who was the originator of the bug report) is currently planning to return the mobo due to possible "bad motherboard BIOS" and not being able to get three screens working in Linux-based distros. They do all work in Windows.

I also found this bug report Unable to boot with HDMI connected on UHD 750. The ensuing investigation results with "In essence, the issue "system hangs at boot" only exists with the old monitor connected to DP-1." That was with a ASRock H570M-ITX/ac mobo.

So at this point, try booting with just one monitor attached. Completely remove the cable for the other. Try different combos with regards to which port one monitor is connected and then switch which one monitor you are attaching. See if one of those combos works?

I'll continue going through the log to see if I can come up with any other ideas.

[SMG]

Tried a couple more variations on search terms and found this 20.04 & 21.04: With Display Port & HDMI in use for dual monitors, both grub and Windows hang (stop) before login which is also with a UHD 750. That person also found booting with just one monitor worked.