putting Intel Rocket Lake PC into service via cloned NVME

Bought LGA1200 Asus motherboard with B560 chipset, and Rocket Lake/11th Gen i5-11400 CPU/IGP (announced Q1’21).

I cloned an NVME stick from my Kaby Lake Asus. When installed in the new Rocket Lake, result of boot attempt without removable device to boot from was:

Welcome to GRUB!
error: symbol "'grub_is_lockdown'" not found".
Entering rescue mode...
grub rescue>

I surmised “lockdown” had something to do with absent security WRT booting on the cloned NVME stick. Google hits searching the error line found didn’t prove helpful as to the details why this particular message gets produced, as it ultimately turned out the BIOS doesn’t automatically show any option that would try the UEFI fallback process, and something needs to create a firmware entry for getting the installed OS’s Grub started up.

I tried booting a 15.3 stick to chroot from to run yast bootloader, but the chrooted system didn’t have os-prober installed, so yast wanted to install it, but couldn’t either because 15.3 firmware for the NIC is apparently absent, or ???. I tried same with TW20211209 USB stick. It locked up at “Starting udev…” So does selecting boot linux system, check installation media and installation. Trying "boot installed system from TW stick opened BIOS setup.

Results from booting rescue image TW20211209 burned to USB were no better for boot installed system. Normal mode rescue caused I/O lockup on switch to i915 from EFI VGA. I reached a login prompt in failsafe mode. From there I chrooted to TW and apparently ran yast bootloader without error to change timeout from 15 to 14. Then I collected this:

inxi -bayz
System:
  Kernel: 5.15.6-1-default x86_64 bits: 64 compiler: gcc v: 11.2.1
  parameters: BOOT_IMAGE=(hd0)/boot/x86_64/loader/linux splash=silent quiet
  systemd.show_status=yes ide=nodma apm=off noresume edd=off nomodeset 3
  root=live:CDLABEL=openSUSE_Tumbleweed_Rescue_CD rd.live.image
  rd.live.overlay.persistent rd.live.overlay.cowfs=ext4
  Console: tty 3 Distro: openSUSE Tumbleweed 20211207
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: N/A
  Mobo: ASUSTeK model: PRIME B560M-A v: Rev 1.xx serial: <filter>
  UEFI: American Megatrends v: 1203 date: 10/27/2021
CPU:
  Info: 6-Core 11th Gen Intel Core i5-11400 [MT MCP] arch: Rocket Lake
  speed: 800 MHz min/max: 800/4400 MHz
Graphics:
  Device-1: Intel RocketLake-S GT1 [UHD Graphics 730] vendor: ASUSTeK
  driver: N/A bus-ID: 00:02.0 chip-ID: 8086:4c8b class-ID: 0300
  Display: server: X.org 1.21.1.1 driver: loaded: modesetting
  unloaded: fbdev,vesa alternate: intel tty: 128x48
  Message: Advanced graphics data unavailable in console for root.
Network:
  Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
  port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15fa class-ID: 0200
Drives:
  Local Storage: total: 240.35 GiB used: 29.02 GiB (12.1%)
Info:
  Processes: 214 Uptime: 0h 8m wakeups: 1131 Memory: 15.39 GiB
  used: 609.7 MiB (3.9%) Init: systemd v: 249 target: graphical.target
  tool: systemctl Compilers: gcc: N/A Packages: N/A note: see --pkg
  Shell: Bash v: 5.1.12 running-in: tty 3 inxi: 3.3.09
# lsmod | grep vid
video                  57344  2 asus_wmi,i915
# ls -l /boot/efi/EFI/opensusetw
total 140
-rwxr-xr-x 1 root root 143360 Dec  8 16:44 grubx64.efi
# efibootmgr -v
BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0001,0002
Boot0001* UEFI OS	HD(1,GPT,5b331d7f-9488-4df5-9eed-c7250696b833,0x800,0xa0000)/File(\EFI\BOOT\BOOTX64.EFI)..BO
Boot0002* UEFI: Flash	PciRoot(0x0)/Pci(0x14,0x0)/USB(9,0)/USB(2,0)/CDROM(1,0x12daa8,0x28000)..BO
# efibootmgr -c -L "opensusetw" -l '\EFI\opensusetw\grubx64.efi'
# efibootmgr -v
BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0000,0001,0002
Boot0000* opensusetw	HD(1,MBR,0x0,0x40,0x12da68)/File(\EFI\opensusetw\grubx64.efi)
Boot0001* UEFI OS	HD(1,GPT,5b331d7f-9488-4df5-9eed-c7250696b833,0x800,0xa0000)/File(\EFI\BOOT\BOOTX64.EFI)..BO
Boot0002* UEFI: Flash	PciRoot(0x0)/Pci(0x14,0x0)/USB(9,0)/USB(2,0)/CDROM(1,0x12daa8,0x28000)..BO

On reboot, normal Grub menu appeared. Choosing default selection locked it up at daily man-db regeneration. Adding nomodeset on next try got me a login prompt. Then I did a zypper dup, which added 5.15.6 kernel. Reboot still locks it up, now at “Started OpenSSH Daemon”. Nomodeset still gets a prompt, but hardware seems to need something that isn’t installed, as KMS is obviously not engaged, and there’s no /dev/fb0. Kernel-firmware-intel and ucode-intel are installed. Is there something else that needs to be installed? Is Rocket Lake video not included in kernel-firmware-intel? Any ideas what to try next, besides 15.4Alpha, some command line option required?

At this point, X is awful due at least to nomodeset requirement:

# inxi -Sy
System:
  Host: ab250 Kernel: 5.15.6-1-default x86_64 bits: 64
  Desktop: Trinity R14.0.11 Distro: openSUSE Tumbleweed 20211209
# inxi -Gayz
Graphics:
  Device-1: Intel RocketLake-S GT1 [UHD Graphics 730] vendor: ASUSTeK
  driver: N/A alternate: i915 bus-ID: 00:02.0 chip-ID: 8086:4c8b
  class-ID: 0300
  Display: x11 server: X.Org 1.21.1.1 driver: loaded: N/A
  unloaded: fbdev,modesetting,vesa alternate: intel display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 271x203mm (10.7x8.0")
  s-diag: 339mm (13.3")
  Monitor-1: default res: 1024x768 hz: 76
  OpenGL: renderer: llvmpipe (LLVM 13.0.0 256 bits) v: 4.5 Mesa 21.3.1
  direct render: Yes

:stuck_out_tongue:

What about testing fresh install?

That comes later. It’s one of the reasons I built it.

I reported a bug against the installation system that got triage moved to kernel 78 minutes after I reported it.

Upstream bug is tagged priority::high severity::major.

So Asus mobo with 3 monitor outputs cannot use more than 1 monitor at a time… Wonderful…

Asus has been notified. If it doesn’t come up with a BIOS update that fixes it before 30th day since purchase, it will get returned, and I’ll get a Gigabyte.

Why you want to disable modesetting (using “nomodeset” boot parameter)?
Intel Xe graphics works OK with TW.

https://wiki.archlinux.org/title/Kernel_mode_setting#Disabling_modesetting

Disabling modesetting

You may want to disable KMS for various reasons. To disable KMS add nomodeset as a kernel parameter. See Kernel parameters for more info.
Along with nomodeset kernel parameter, for Intel graphics card you need to add i915.modeset=0 and for Nvidia graphics card you need to add nouveau.modeset=0. For Nvidia Optimus dual-graphics system, you need to add all the three kernel parameters (i.e. “nomodeset i915.modeset=0 nouveau.modeset=0”).

I don’t. Whatever gives you such an idea?

That archwiki paragraph is nonsense. Nomodeset is global. The others are specific to GPU class (AMD, Intel, NVidia, etc.) only.