Error install LinuxCNC to Debian 12

I changed the boot order to first Ubuntu and second Debian to allow Ubuntu Secure Boot.  The Grub is ignored and Ubuntu automatically boots up.  

Visa versa the Grub automatically displays its menu.  Debian boots okay but Ubuntu does not when Secure Boot enabled.

Disabling Secure Boot as foregoing the Ubuntu boots from the Grub.

I guess it's not a requirement to configure Ubuntu in the Grub but suppose it'd be convenient if available in the menu and would try making the configuration.  

sudo cat /boot/grub/device.map
(hd0)    /dev/disk/by-id/nvme-Samsung_SSD_970_EVO_Plus_500GB_S58SNM0W323594T
(hd1)    /dev/disk/by-id/ata-CT500MX500SSD1_2307E6AF11B5

ls /dev/disk/by-id -lt
...
lrwxrwxrwx 1 root root 15 Jul 22 10:49 nvme-eui.002538533191bca8-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 Jul 22 10:49 nvme-eui.002538533191bca8-part2 -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 15 Jul 22 10:49 nvme-Samsung_SSD_970_EVO_Plus_500GB_S58SNM0W323594T-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 Jul 22 10:49 nvme-Samsung_SSD_970_EVO_Plus_500GB_S58SNM0W323594T-part2 -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 13 Jul 22 10:49 nvme-eui.002538533191bca8 -> ../../nvme0n1
lrwxrwxrwx 1 root root 13 Jul 22 10:49 nvme-Samsung_SSD_970_EVO_Plus_500GB_S58SNM0W323594T -> ../../nvme0n1

sudo fdisk -l
Device           Start       End   Sectors   Size Type
/dev/nvme0n1p1    2048   1050623   1048576   512M EFI System
/dev/nvme0n1p2 1050624 976771071 975720448 465.3G Linux filesystem

lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    0 465.8G  0 disk
├─sda1        8:1    0   512M  0 part /boot/efi
├─sda2        8:2    0 464.3G  0 part /
└─sda3        8:3    0   976M  0 part [SWAP]
nvme0n1     259:0    0 465.8G  0 disk
├─nvme0n1p1 259:1    0   512M  0 part
└─nvme0n1p2 259:2    0 465.3G  0 part

sudo parted -l
Model: ATA CT500MX500SSD1 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End    Size    File system     Name  Flags
 1      1049kB  538MB  537MB   fat32                 boot, esp
 2      538MB   499GB  499GB   ext4
 3      499GB   500GB  1023MB  linux-swap(v1)        swap


Model: Samsung SSD 970 EVO Plus 500GB (nvme)
Disk /dev/nvme0n1: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End    Size   File system  Name                  Flags
 1      1049kB  538MB  537MB  fat32        EFI System Partition  boot, esp
 2      538MB   500GB  500GB  ext4

grub> cat (hd0,2)/etc/issue    #hd0,gpt2
Debian GNU/Linux 12 \n \l

grub> cat (hd1,2)/etc/issue    #hd1,gpt2                     
Ubuntu 22.04.2 LTS \n \l

I see cat /boot/grub/device.map is (hd0) /dev/disk/by-id/nvme-Samsung_SSD_970_EVO_Plus_500GB_S58SNM0W3235694T but grub> cat (hd1,2)/etc/issue .

Is then?

grub> set root=(hd1,2)
grub> linux /boot/vmlinuz-3.13.0-29-generic root=/dev/nvme0n1p2
grub> initrd /boot/initrd.img-3.13.0-29-generic
grub> boot

I would probably bite the bullet and just reinstall Deban 12.1 netinstall from the very first link here.
www.debian.org/download 

The 2.9 docs have been updated with the updated download URLS to 12.1 (eg that link). The changes have just been pushed but it will take a while to get deployed on the website.

Debian has a chapter on UEFI (Secure Boot) wiki.debian.org/SecureBoot#What_is_UEFI.3F

I think  using Bookworm and its 6.1 kernel will solve any UEFI/Secure Boot issues as a lot of work with UEFI went into the 6.1 kernel
REF: www.phoronix.com/news/Linux-6.1-EFI-Features

I have not experienced any UEFI issues with bookworm and I have deliberately tested a UEFI install recently.

Thanks for the link. I installed Debian 12.1 and see it may require the GNOME Extension Manager to install desktop icons.

The Grub that came with Debian 12.1 still doesn't Secure Boot Ubuntu. Debian 12.1 Secure Boots okay from the Grub. Ubuntu 22.04.2 Secure Boots okay from it boot loader (AMI). It appears the Grub menu detects Ubuntu but requires manual configuration. Maybe the Ubuntu shouldn't be configured to the Grub that if I ever remove the SDD and boot it from another computer. I'd rather not configure Ubuntu to the Grub if it interferes with the boot loader (AMI) on the NVMe that boots Ubuntu.

I don't believe you will get secure boot working across both distros until Ubuntu adopts a later kernel that has better support for UEFI.
I just give Bookworm the full SSD volume to itself.