Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic: [EN] GRUB menu has disappeared  (Read 6164 times)

Offline debsid

  • User
  • Posts: 23
[EN] GRUB menu has disappeared
« on: 2024/01/17, 11:47:11 »
Hi everyone,

I noticed yesterday that my grub menu has disappeared, meaning, the system shows the Lenovo logo for a bit longer than usual--I guess adding the 5 seconds of the regular grub menu--and then boots right into 6.6.11.

I noticed the disappearance after I saw that the new upgrade wants to remove the running kernel (6.6.9), installing 6.6.9-unsigned while also marking 6.6.8 for deletion. This is very unusual. Note that I don't have any other OSs installed, just different kernels. I have done the usual grub-install and update-grub without any action. Does anyone know what could have caused this?

Online eriefisher

  • User
  • Posts: 282
Re: GRUB menu has disappeared
« Reply #1 on: 2024/01/17, 12:56:16 »
The kernels shouldn't be marked for removal. They will be autoremovable after the latest two are in place but you need to remove them deliberately. Can you post /etc/default/grub and uname -r?

Offline debsid

  • User
  • Posts: 23
Re: GRUB menu has disappeared
« Reply #2 on: 2024/01/17, 13:29:44 »
I should have mentioned that I am on a Debian Sid that I transitioned from Siduction. 6.6.9 was removed and replaced by 6.6.9-unsigned, which I found very strange. linux-image-6.6.8-amd64 will be removed if I do a full-upgrade now.

Code: [Select]
uname -r: 6.6.11-amd64
And /etc/default/grub:
Code: [Select]
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""

# If your computer has multiple operating systems installed, then you
# probably want to run os-prober. However, if your computer is a host
# for guest OSes installed via LVM or raw disk devices, running
# os-prober can cause damage to those guest OSes as it mounts
# filesystems to look for things.
#GRUB_DISABLE_OS_PROBER=false

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

Offline unklarer

  • User
  • Posts: 841
Re: GRUB menu has disappeared
« Reply #3 on: 2024/01/17, 14:13:25 »
I can confirm the behavior under sid.

A warning was issued not to remove 6.6.9.
But since apt shows what it would do (replace with 'unsigned), nothing could go wrong. Everything went correctly.    8)


Offline debsid

  • User
  • Posts: 23
Re: GRUB menu has disappeared
« Reply #4 on: 2024/01/17, 14:34:03 »
I am unsure the two issues are corrected, but thanks for confirming that you have the unsigned replacement too. Do you know why all of a sudden an unsigned kernel has been introduced replacing the signed 6.6.9? Why not also for 6.6.11?

As I said, my system boots fine into 6.6.11 and unsigned has been installed fine. The problem is that the grub menu has disappeared, which I have not been able to bring back.

Offline towo

  • Administrator
  • User
  • *****
  • Posts: 2.955
Re: GRUB menu has disappeared
« Reply #5 on: 2024/01/17, 15:09:04 »
We do not ship kernels which have signed or unsigned in the package-name, such packages are from debian.
In siduction, we do not have signed kernels, since we do not support secureboot.
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

Offline ro_sid

  • User
  • Posts: 248
Re: GRUB menu has disappeared
« Reply #6 on: 2024/01/17, 15:28:14 »
Hello,
Hi everyone,

I noticed yesterday that my grub menu has disappeared, meaning, the system shows the Lenovo logo for a bit longer than usual--I guess adding the 5 seconds of the regular grub menu--and then boots right into 6.6.11.
I believe to remember that this is grub standard behaviour if there is only one bootable entry at all. Do you have any alternatives (like Memtest) configured?
The actual grub file is /boot/grub/grub.cfg. It can be somewhat large(r), though. Have a look for defined boot-entries, there. And have a look, that the timeout-constant is not too short; although the screen should at least "flash" then.

Offline debsid

  • User
  • Posts: 23
Re: GRUB menu has disappeared
« Reply #7 on: 2024/01/17, 17:06:26 »
We do not ship kernels which have signed or unsigned in the package-name, such packages are from debian.
In siduction, we do not have signed kernels, since we do not support secureboot.

I mentioned the signed/unsigned only as I thought it might be related to or might have caused the problem. But as I will explain below, I don't think that it is.

Hello,
Hi everyone,

I noticed yesterday that my grub menu has disappeared, meaning, the system shows the Lenovo logo for a bit longer than usual--I guess adding the 5 seconds of the regular grub menu--and then boots right into 6.6.11.
I believe to remember that this is grub standard behaviour if there is only one bootable entry at all. Do you have any alternatives (like Memtest) configured?
The actual grub file is /boot/grub/grub.cfg. It can be somewhat large(r), though. Have a look for defined boot-entries, there. And have a look, that the timeout-constant is not too short; although the screen should at least "flash" then.

I don't believe that that is the default behaviour. I have another system, also transitioned from Siduction (Masters of War) to Debian Sid, where the grub menu is always shown. I full-upgraded that one right now, and the grub menu is still shown.

I just found out by chance that on the system, where grub is no longer shown, I can go into the BIOS and exit immediately without making any changes, in which case the grub menu shows up?!?! I will investigate further by comparing the grub files of the two systems.

Offline ro_sid

  • User
  • Posts: 248
Re: GRUB menu has disappeared
« Reply #8 on: 2024/01/17, 18:06:09 »
[...]
I just found out by chance that on the system, where grub is no longer shown, I can go into the BIOS and exit immediately without making any changes, in which case the grub menu shows up?!?! I will investigate further by comparing the grub files of the two systems.
In this case, and when your system uses UEFI-Boot, may be, the boot order changes with the BIOS exit.
In an (automatically) booting Siduction, look what "efibootmgr -v" tells you/us.

Offline dpanter

  • User
  • Posts: 61
Re: GRUB menu has disappeared
« Reply #9 on: 2024/01/17, 19:27:56 »
Quote from: debsid
I should have mentioned that I am on a Debian Sid that I transitioned from Siduction

So you're not using Siduction on this or that other system you mentioned, seems like upgrade issues then should be directed to Debian channels instead. Siduction users would typically have  linux-image-siduction-amd64  installed to ensure proper kernel upgrades as per the default distro policies.
<< insert signature here >>

Offline debsid

  • User
  • Posts: 23
Re: GRUB menu has disappeared
« Reply #10 on: 2024/01/18, 00:32:36 »
My apologies. I asked here as I couldn't find anything relevant elsewhere, but there had been a couple of grub related issues on here. The problem does not seem to be related to the kernel anyway. Haven't been able to find out what might have caused disappearance of grub, at this point it doesn't even seem to be related to the upgrade. Sorry, it was not my intention to 'misuse' the forum, I found out most of this as the day progressed.

Offline dpanter

  • User
  • Posts: 61
Re: GRUB menu has disappeared
« Reply #11 on: 2024/01/18, 00:51:54 »
No worries. It's difficult to help with systems that have migrated away from the base Siduction and run into quirky issues one wouldn't otherwise experience. No harm in asking.
<< insert signature here >>

Offline hendrikL

  • Administrator
  • User
  • *****
  • Gravatar
  • Posts: 986
Re: GRUB menu has disappeared
« Reply #12 on: 2024/01/18, 07:14:28 »
I would question if grub is correctly installed, the software, or if something broken or missing.
The kernel is not the issue, for sure!
The other question would be, for me, did grub-install installed it in the right place!

Offline debsid

  • User
  • Posts: 23
Re: GRUB menu has disappeared
« Reply #13 on: 2024/01/18, 10:02:00 »
I would question if grub is correctly installed, the software, or if something broken or missing.
The kernel is not the issue, for sure!
The other question would be, for me, did grub-install installed it in the right place!

That's what I have been thinking too. But would a bad installation explain that grub is shown correctly after I exit the BIOS? The other question of course is then, why was the installation of grub messed with? I certainly didn't do anything before I noticed that it was gone. At any rate, I do think that this is unrelated to any upgrade, sid, and possibly even debian.

In this case, and when your system uses UEFI-Boot, may be, the boot order changes with the BIOS exit.
In an (automatically) booting Siduction, look what "efibootmgr -v" tells you/us.

This is output. Does it help?
Code: [Select]
BootCurrent: 0014
Timeout: 0 seconds
BootOrder: 0014,0013,0007,0008,0009,000A,000B,000C,000D
Boot0000  Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
      dp: 04 06 14 00 66 8b 1c 72 6c 42 86 4e 8e 99 34 57 c4 6a b0 b9 / 7f ff 04 00
Boot0001  Boot Menu FvFile(126a762d-5758-4fca-8531-201a7f57f850)
      dp: 04 06 14 00 2d 76 6a 12 58 57 ca 4f 85 31 20 1a 7f 57 f8 50 / 7f ff 04 00
Boot0002  Diagnostic Splash Screen FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
      dp: 04 06 14 00 a6 d9 d8 a7 b0 6a eb 4a ad 9d 16 3e 59 a7 a3 80 / 7f ff 04 00
Boot0003  Lenovo Diagnostics FvFile(3f7e615b-0d45-4f80-88dc-26b234958560)
      dp: 04 06 14 00 5b 61 7e 3f 45 0d 80 4f 88 dc 26 b2 34 95 85 60 / 7f ff 04 00
Boot0004  Startup Interrupt Menu FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479)
      dp: 04 06 14 00 f4 e6 6e f4 85 47 a3 43 92 3d 7f 78 6c 3c 84 79 / 7f ff 04 00
Boot0005  Rescue and Recovery FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)
      dp: 04 06 14 00 60 3f 5d 66 3e ad ad 4c 8e 26 db 46 ee e9 f1 b5 / 7f ff 04 00
Boot0006  MEBx Hot Key FvFile(ac6fd56a-3d41-4efd-a1b9-870293811a28)
      dp: 04 06 14 00 6a d5 6f ac 41 3d fd 4e a1 b9 87 02 93 81 1a 28 / 7f ff 04 00
Boot0007* USB CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 86 70 12 96 aa 5a 78 48 b6 6c d4 9d d3 ba 6a 55 / 7f ff 04 00
Boot0008* USB FDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 6f f0 15 a2 88 30 b5 43 a8 b8 64 10 09 46 1e 49 / 7f ff 04 00
Boot0009* ATA HDD0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
      dp: 03 0a 25 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 91 af 62 59 56 44 9f 41 a7 b9 1f 4f 89 2a b0 f6 00 / 7f ff 04 00
Boot000A* ATA HDD1 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f601)
      dp: 03 0a 25 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 91 af 62 59 56 44 9f 41 a7 b9 1f 4f 89 2a b0 f6 01 / 7f ff 04 00
Boot000B* ATA HDD2 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f602)
      dp: 03 0a 25 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 91 af 62 59 56 44 9f 41 a7 b9 1f 4f 89 2a b0 f6 02 / 7f ff 04 00
Boot000C* USB HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 33 e8 21 aa af 33 bc 47 89 bd 41 9f 88 c5 08 03 / 7f ff 04 00
Boot000D* PCI LAN VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 78 a8 4a af 2b 2a fc 4e a7 9c f5 cc 8f 3d 38 03 / 7f ff 04 00
Boot000E* IDER BOOT CDROM PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,1,0)
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 02 16 / 03 01 08 00 00 01 00 00 / 7f ff 04 00
Boot000F* IDER BOOT Floppy PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,0,0)
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 02 16 / 03 01 08 00 00 00 00 00 / 7f ff 04 00
Boot0010* ATA HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 91 af 62 59 56 44 9f 41 a7 b9 1f 4f 89 2a b0 f6 / 7f ff 04 00
Boot0011* ATAPI CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b ae a2 09 0a df de 21 4e 8b 3a 5e 47 18 56 a3 54 / 7f ff 04 00
Boot0012* PCI LAN VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 78 a8 4a af 2b 2a fc 4e a7 9c f5 cc 8f 3d 38 03 / 7f ff 04 00
Boot0013* Windows Boot Manager HD(1,GPT,4ee60c1e-62c8-4d9b-a5e1-940581cbcc39,0x800,0x100000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000006000100000010000000040000007fff0400
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 00 10 00 00 00 00 00 1e 0c e6 4e c8 62 9b 4d a5 e1 94 05 81 cb cc 39 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 69 00 63 00 72 00 6f 00 73 00 6f 00 66 00 74 00 5c 00 42 00 6f 00 6f 00 74 00 5c 00 62 00 6f 00 6f 00 74 00 6d 00 67 00 66 00 77 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
    data: 57 49 4e 44 4f 57 53 00 01 00 00 00 88 00 00 00 78 00 00 00 42 00 43 00 44 00 4f 00 42 00 4a 00 45 00 43 00 54 00 3d 00 7b 00 39 00 64 00 65 00 61 00 38 00 36 00 32 00 63 00 2d 00 35 00 63 00 64 00 64 00 2d 00 34 00 65 00 37 00 30 00 2d 00 61 00 63 00 63 00 31 00 2d 00 66 00 33 00 32 00 62 00 33 00 34 00 34 00 64 00 34 00 37 00 39 00 35 00 7d 00 00 00 06 00 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00
Boot0014* debian HD(1,GPT,6c0bccb2-aff1-4ef6-85b8-370a80766d5f,0x800,0x100000)/File(\EFI\debian\grubx64.efi)
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 00 10 00 00 00 00 00 b2 cc 0b 6c f1 af f6 4e 85 b8 37 0a 80 76 6d 5f 02 02 / 04 04 34 00 5c 00 45 00 46 00 49 00 5c 00 64 00 65 00 62 00 69 00 61 00 6e 00 5c 00 67 00 72 00 75 00 62 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00

Offline ro_sid

  • User
  • Posts: 248
Re: GRUB menu has disappeared
« Reply #14 on: 2024/01/18, 11:10:53 »
[,,,]
This is output. Does it help?
Code: [Select]
BootCurrent: 0014
Timeout: 0 seconds
BootOrder: 0014,0013,0007,0008,0009,000A,000B,000C,000D
Boot0000  Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
      dp: 04 06 14 00 66 8b 1c 72 6c 42 86 4e 8e 99 34 57 c4 6a b0 b9 / 7f ff 04 00
Boot0001  Boot Menu FvFile(126a762d-5758-4fca-8531-201a7f57f850)
      dp: 04 06 14 00 2d 76 6a 12 58 57 ca 4f 85 31 20 1a 7f 57 f8 50 / 7f ff 04 00
Boot0002  Diagnostic Splash Screen FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
      dp: 04 06 14 00 a6 d9 d8 a7 b0 6a eb 4a ad 9d 16 3e 59 a7 a3 80 / 7f ff 04 00
Boot0003  Lenovo Diagnostics FvFile(3f7e615b-0d45-4f80-88dc-26b234958560)
      dp: 04 06 14 00 5b 61 7e 3f 45 0d 80 4f 88 dc 26 b2 34 95 85 60 / 7f ff 04 00
Boot0004  Startup Interrupt Menu FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479)
      dp: 04 06 14 00 f4 e6 6e f4 85 47 a3 43 92 3d 7f 78 6c 3c 84 79 / 7f ff 04 00
Boot0005  Rescue and Recovery FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)
      dp: 04 06 14 00 60 3f 5d 66 3e ad ad 4c 8e 26 db 46 ee e9 f1 b5 / 7f ff 04 00
Boot0006  MEBx Hot Key FvFile(ac6fd56a-3d41-4efd-a1b9-870293811a28)
      dp: 04 06 14 00 6a d5 6f ac 41 3d fd 4e a1 b9 87 02 93 81 1a 28 / 7f ff 04 00
Boot0007* USB CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 86 70 12 96 aa 5a 78 48 b6 6c d4 9d d3 ba 6a 55 / 7f ff 04 00
Boot0008* USB FDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 6f f0 15 a2 88 30 b5 43 a8 b8 64 10 09 46 1e 49 / 7f ff 04 00
Boot0009* ATA HDD0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
      dp: 03 0a 25 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 91 af 62 59 56 44 9f 41 a7 b9 1f 4f 89 2a b0 f6 00 / 7f ff 04 00
Boot000A* ATA HDD1 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f601)
      dp: 03 0a 25 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 91 af 62 59 56 44 9f 41 a7 b9 1f 4f 89 2a b0 f6 01 / 7f ff 04 00
Boot000B* ATA HDD2 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f602)
      dp: 03 0a 25 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 91 af 62 59 56 44 9f 41 a7 b9 1f 4f 89 2a b0 f6 02 / 7f ff 04 00
Boot000C* USB HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 33 e8 21 aa af 33 bc 47 89 bd 41 9f 88 c5 08 03 / 7f ff 04 00
Boot000D* PCI LAN VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 78 a8 4a af 2b 2a fc 4e a7 9c f5 cc 8f 3d 38 03 / 7f ff 04 00
Boot000E* IDER BOOT CDROM PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,1,0)
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 02 16 / 03 01 08 00 00 01 00 00 / 7f ff 04 00
Boot000F* IDER BOOT Floppy PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,0,0)
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 02 16 / 03 01 08 00 00 00 00 00 / 7f ff 04 00
Boot0010* ATA HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 91 af 62 59 56 44 9f 41 a7 b9 1f 4f 89 2a b0 f6 / 7f ff 04 00
Boot0011* ATAPI CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b ae a2 09 0a df de 21 4e 8b 3a 5e 47 18 56 a3 54 / 7f ff 04 00
Boot0012* PCI LAN VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 78 a8 4a af 2b 2a fc 4e a7 9c f5 cc 8f 3d 38 03 / 7f ff 04 00
Boot0013* Windows Boot Manager HD(1,GPT,4ee60c1e-62c8-4d9b-a5e1-940581cbcc39,0x800,0x100000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000006000100000010000000040000007fff0400
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 00 10 00 00 00 00 00 1e 0c e6 4e c8 62 9b 4d a5 e1 94 05 81 cb cc 39 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 69 00 63 00 72 00 6f 00 73 00 6f 00 66 00 74 00 5c 00 42 00 6f 00 6f 00 74 00 5c 00 62 00 6f 00 6f 00 74 00 6d 00 67 00 66 00 77 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
    data: 57 49 4e 44 4f 57 53 00 01 00 00 00 88 00 00 00 78 00 00 00 42 00 43 00 44 00 4f 00 42 00 4a 00 45 00 43 00 54 00 3d 00 7b 00 39 00 64 00 65 00 61 00 38 00 36 00 32 00 63 00 2d 00 35 00 63 00 64 00 64 00 2d 00 34 00 65 00 37 00 30 00 2d 00 61 00 63 00 63 00 31 00 2d 00 66 00 33 00 32 00 62 00 33 00 34 00 34 00 64 00 34 00 37 00 39 00 35 00 7d 00 00 00 06 00 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00
Boot0014* debian HD(1,GPT,6c0bccb2-aff1-4ef6-85b8-370a80766d5f,0x800,0x100000)/File(\EFI\debian\grubx64.efi)
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 00 10 00 00 00 00 00 b2 cc 0b 6c f1 af f6 4e 85 b8 37 0a 80 76 6d 5f 02 02 / 04 04 34 00 5c 00 45 00 46 00 49 00 5c 00 64 00 65 00 62 00 69 00 61 00 6e 00 5c 00 67 00 72 00 75 00 62 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
Yes, thank you, but to my dismay only in that it shows, that grub has been called correctly (entry 00014) (- if the grubx64.efi does belong to your last grub update/version, that is. This is rather likely though, since otherwise grub would throw an error message).
It is Debian's grub, as Siduction uses an \EFI\siduction\ path instead of \EFI\debian. You might inspect the UEFI-partition, if the \EFI\siduction path is still there. The reason I am mentioning this is, because grubx64.efi keeps a path of where to look for the grub.cfg-file hardcoded inside - most often /boot/grub, but not necessarily so.
Now the only idea that I have left is the grub.cfg file itself. The UEFI display drivers are different from the legacy boot ones. Normally, there is a fork for the different display drivers in grub.cfg. May be your system does not initialize the display system, as long as you do not call the BIOS beforehand. I have no idea, why the behaviour should have changed from the prior one, though, sorry.