Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: debsid 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?
-
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?
-
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.
uname -r: 6.6.11-amd64
And /etc/default/grub:
# 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"
-
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)
(https://i.imgur.com/nEbLKnft.png) (https://i.imgur.com/nEbLKnf.png)
-
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.
-
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.
-
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.
-
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.
-
[...]
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.
-
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.
-
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.
-
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.
-
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!
-
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?
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
-
[,,,]
This is output. Does it help?
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.
-
three things that don't go together for me
/etc/default/grub:
#GRUB_DISABLE_OS_PROBER=false
This is output. Does it help?
Timeout: 0 seconds
...
Boot0013* Windows Boot Manager ...
If you want to see the grub menu (after updating grub), you should change that or choose a method ?
-
Mine is also set to 0 seconds in efibootmgr and I boot fine with the grubmenu showing for 5 seconds so I don't think this is the issue.
-
I just set the timeout value to 0 in /etc/default/grub and rebooted after an update-grub. The grub menu no longer appeared!
edlin
-
I just set the timeout value to 0 in /etc/default/grub and rebooted after an update-grub. The grub menu no longer appeared!
edlin
Yes, and?
In his /etc/default/grub it says 5 :-*
-
Better would be to see, what is the content of the files in /etc/default/grub.d/.
-
Thank you for the feedbacks. I've been looking and not finding. I did some of the usual stuff I found in various forums, such as repairing the boot manager with boot-repair, which doesn't seem to be doing anything fancy beside 'grub-install' and 'update-grub'. To make sure that nothing had gone wrong along the way, I even removed and re-installed grub. With the newly installed grub, /etc/default/grub.d/ is blissfully empty.
-
[...] I even removed and re-installed grub. With the newly installed grub, /etc/default/grub.d/ is blissfully empty.
The latter is really disturbing. Although I am still not sure that it is a question of "just grub", its proper installation is, of course, mandatory. Did you just "remove" or really "purge" grub before reinstalling? The /etc/default/grub.d directory must be correctly populated!
Edit: Sorry, it is /etc/grub.d/, that must be populated, but /etc/default/{grub,grub.d/} should.
-
[...] I even removed and re-installed grub. With the newly installed grub, /etc/default/grub.d/ is blissfully empty.
The latter is really disturbing. Although I am still not sure that it is a question of "just grub", its proper installation is, of course, mandatory. Did you just "remove" or really "purge" grub before reinstalling? The /etc/default/grub.d directory must be correctly populated!
Edit: Sorry, it is /etc/grub.d/, that must be populated, but /etc/default/{grub,grub.d/} should.
Yes, @towo had asked for /etc/default/grub.d/. /etc/grub.d/ has
00_header 05_debian_theme 10_linux 20_linux_xen 25_bli 30_os-prober 30_uefi-firmware 35_fwupd 40_custom 41_custom
Do you want to see the contents of all of these files?
-
I just set the timeout value to 0 in /etc/default/grub and rebooted after an update-grub. The grub menu no longer appeared!
edlin
I started thinking irrationally to see whether I can narrow down the problem. I had not edited any of the configuration files manually, so I did not expect the problem to have been introduced by me. Maybe something had gone wrong during the postinstall process after a kernel update? So, I set the value of GRUB_TIMEOUT=5 to zero, update-grub, restart, set back to 5, update-grub, restart. Nothing.
Next was #GRUB_TERMINAL=console Uncomment, grub-update, restart, and boom. grub's blue, console screen shows up and works as expected if other values are changed. If I understand it correctly, with this option commented and no theme installed, the black more fancy screen should show. So, does this bring us closer to an understanding what could have gone wrong?
-
If I remember correctly you moved the system from siduction to debian sid.
Could it be, that you removed all the siduction-theme things.
Maybe you should investigate your search time in that direction.
-
[...] With the newly installed grub, /etc/default/grub.d/ is blissfully empty.
and
Yes, @towo had asked for /etc/default/grub.d/. /etc/grub.d/ has
00_header 05_debian_theme 10_linux 20_linux_xen 25_bli 30_os-prober 30_uefi-firmware 35_fwupd 40_custom 41_custom
Edit:
This is a mismatch. Sorry, I didn't look closely.
But still:
Do you have more than one HD?
If so, post the output of 'lsblk'.
-
[...]
Yes, @towo had asked for /etc/default/grub.d/. /etc/grub.d/ has
00_header 05_debian_theme 10_linux 20_linux_xen 25_bli 30_os-prober 30_uefi-firmware 35_fwupd 40_custom 41_custom
Do you want to see the contents of all of these files?
You are right concerning @towo.
I did look-up the latest Debian-Live ISO and there /etc/default/grub.d is not empty, but has a single file in it, which only contains workaround comments to (outdated) problems. From this point of view, the directory may also be empty.
Regarding the /etc/grub.d directory, only the 25-bli entry is missing. So probably no, no file-contents necessary at this time.
On the other hand, Siduction has a file /etc/grub and a file in /etc/grub.d/, and also the file 25-bli.
So, are you sure, you do not have mix between Siduction an Debian, leading to your problem?
-
If I remember correctly you moved the system from siduction to debian sid.
Could it be, that you removed all the siduction-theme things.
Maybe you should investigate your search time in that direction.
Yes, that's right, I moved from Siduction. But the system had been fine until a recent upgrade which must have caused the menu to disappear, which is now back by enabling the console feature. I had not noticed the disappearance as I often don't sit in front of the system while it boots. And it has been booting just fine.
[...]
Do you have more than one HD?
If so, post the output of 'lsblk'.
No, one HD. Note that grub is working in console mode. So, no real fault with the grub installation as such. And the Lenovo logo time is now reduced to 'normal' again, which suggests the length was due to the 5 seconds for grub. So, even when it was not there, it was working fine, just not showing.
[...]
You are right concerning @towo.
I did look-up the latest Debian-Live ISO and there /etc/default/grub.d is not empty, but has a single file in it, which only contains workaround comments to (outdated) problems. From this point of view, the directory may also be empty.
Regarding the /etc/grub.d directory, only the 25-bli entry is missing. So probably no, no file-contents necessary at this time.
On the other hand, Siduction has a file /etc/grub and a file in /etc/grub.d/, and also the file 25-bli.
So, are you sure, you do not have mix between Siduction an Debian, leading to your problem?
You might be onto something there. As I said, the system had been working fine, and the boot process was apparently functional, just not visible, but working fine in the background. But something might have changed in the meantime and caused grub's disappearance in the graphical mode. I will see what else I can find out on Debian's side.
-
I have been comparing the file and folder structures between my two laptops. Both are migrations from siduction > debian sid. It seems that the contents of the relevant folders are mostly the same, meaning they have the exact same files.
However, /etc/default/grub.d/ has 'siduction.cfg' (see below) in the one with the working grub, while the one with the problem has an empty folder here.
And a diff (see below) between the two /boot/grub/grub.cfg shows some interesting differences, which could be the culprits.
/etc/default/grub.d/siduction.cfg:
GRUB_TERMINAL_OUTPUT=gfxterm
GRUB_GFXMODE=1920x1080,1280x1024,1280x800,1280x720,1024x768, 800x688,text
GRUB_GFXPAYLOAD_LINUX=keep
#GRUB_THEME=/usr/share/grub/themes/mow/theme.txt
#GRUB_DISTRIBUTOR="siduction 2022.1.0 Masters of War"
GRUB_DISABLE_OS PROBER=false
Diff:
--- ideapad_grub.cfg [Working GRUB]
+++ /boot/grub/grub.cfg [non-Working GRUB]
@@ -55,24 +55,8 @@
fi
}
-if [ x$feature_default_font_path = xy ] ; then
- font=unicode
-else
-insmod part_gpt
-insmod ext2
-search --no-floppy --fs-uuid --set=root 39689532-2a77-460a-b60f-0d158f162012
- font="/usr/share/grub/unicode.pf2"
-fi
-
-if loadfont $font ; then
- set gfxmode=1920x1080,1280x1024,1280x800,1280x720,1024x768,800x600,text
- load_video
- insmod gfxterm
- set locale_dir=$prefix/locale
- set lang=en_GB
- insmod gettext
-fi
-terminal_output gfxterm
+terminal_input console
+terminal_output console
if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
@@ -87,77 +71,102 @@
fi
### END /etc/grub.d/00_header ###
+### BEGIN /etc/grub.d/05_debian_theme ###
+set menu_color_normal=cyan/blue
+set menu_color_highlight=white/blue
+### END /etc/grub.d/05_debian_theme ###
+
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
-set linux_gfx_mode=keep
+set linux_gfx_mode=
export linux_gfx_mode
-menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-39689532-2a77-460a-b60f-0d158f162012' {
+menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-31c430e1-9e6a-4543-ae3b-cc4128af9021' {
load_video
- gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
- search --no-floppy --fs-uuid --set=root 0f76e1fb-5f53-421b-9c26-685ee52dbfe8
- echo 'Loading Linux 6.6.11-amd64 ...'
- linux /vmlinuz-6.6.11-amd64 root=UUID=39689532-2a77-460a-b60f-0d158f162012 ro quiet resume=UUID=7c5ebc0c-56ba-446a-b5d6-b3e7cae81b69 systemd.show_status=1 snd_hda_intel.dmic_detect=0
+ set root='hd0,gpt2'
+ if [ x$feature_platform_search_hint = xy ]; then
+ search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 31c430e1-9e6a-4543-ae3b-cc4128af9021
+ else
+ search --no-floppy --fs-uuid --set=root 31c430e1-9e6a-4543-ae3b-cc4128af9021
+ fi
+ echo 'Loading Linux 6.6.13-amd64 ...'
+ linux /boot/vmlinuz-6.6.13-amd64 root=UUID=31c430e1-9e6a-4543-ae3b-cc4128af9021 ro quiet
echo 'Loading initial ramdisk ...'
- initrd /initrd.img-6.6.11-amd64
+ initrd /boot/initrd.img-6.6.13-amd64
}
-submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option 'gnulinux-advanced-39689532-2a77-460a-b60f-0d158f162012' {
- menuentry 'Debian GNU/Linux, with Linux 6.6.11-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.6.11-amd64-advanced-39689532-2a77-460a-b60f-0d158f162012' {
+submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option 'gnulinux-advanced-31c430e1-9e6a-4543-ae3b-cc4128af9021' {
+ menuentry 'Debian GNU/Linux, with Linux 6.6.13-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.6.13-amd64-advanced-31c430e1-9e6a-4543-ae3b-cc4128af9021' {
load_video
- gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
- search --no-floppy --fs-uuid --set=root 0f76e1fb-5f53-421b-9c26-685ee52dbfe8
- echo 'Loading Linux 6.6.11-amd64 ...'
- linux /vmlinuz-6.6.11-amd64 root=UUID=39689532-2a77-460a-b60f-0d158f162012 ro quiet resume=UUID=7c5ebc0c-56ba-446a-b5d6-b3e7cae81b69 systemd.show_status=1 snd_hda_intel.dmic_detect=0
+ set root='hd0,gpt2'
+ if [ x$feature_platform_search_hint = xy ]; then
+ search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 31c430e1-9e6a-4543-ae3b-cc4128af9021
+ else
+ search --no-floppy --fs-uuid --set=root 31c430e1-9e6a-4543-ae3b-cc4128af9021
+ fi
+ echo 'Loading Linux 6.6.13-amd64 ...'
+ linux /boot/vmlinuz-6.6.13-amd64 root=UUID=31c430e1-9e6a-4543-ae3b-cc4128af9021 ro quiet
echo 'Loading initial ramdisk ...'
- initrd /initrd.img-6.6.11-amd64
+ initrd /boot/initrd.img-6.6.13-amd64
}
- menuentry 'Debian GNU/Linux, with Linux 6.6.11-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.6.11-amd64-recovery-39689532-2a77-460a-b60f-0d158f162012' {
+ menuentry 'Debian GNU/Linux, with Linux 6.6.13-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.6.13-amd64-recovery-31c430e1-9e6a-4543-ae3b-cc4128af9021' {
load_video
- gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
- search --no-floppy --fs-uuid --set=root 0f76e1fb-5f53-421b-9c26-685ee52dbfe8
- echo 'Loading Linux 6.6.11-amd64 ...'
- linux /vmlinuz-6.6.11-amd64 root=UUID=39689532-2a77-460a-b60f-0d158f162012 ro single single dis_ucode_ldr
+ set root='hd0,gpt2'
+ if [ x$feature_platform_search_hint = xy ]; then
+ search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 31c430e1-9e6a-4543-ae3b-cc4128af9021
+ else
+ search --no-floppy --fs-uuid --set=root 31c430e1-9e6a-4543-ae3b-cc4128af9021
+ fi
+ echo 'Loading Linux 6.6.13-amd64 ...'
+ linux /boot/vmlinuz-6.6.13-amd64 root=UUID=31c430e1-9e6a-4543-ae3b-cc4128af9021 ro single single dis_ucode_ldr
echo 'Loading initial ramdisk ...'
- initrd /initrd.img-6.6.11-amd64
+ initrd /boot/initrd.img-6.6.13-amd64
}
- menuentry 'Debian GNU/Linux, with Linux 6.5.0-1-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.5.0-1-amd64-advanced-39689532-2a77-460a-b60f-0d158f162012' {
+ menuentry 'Debian GNU/Linux, with Linux 6.6.11-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.6.11-amd64-advanced-31c430e1-9e6a-4543-ae3b-cc4128af9021' {
load_video
- gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
- search --no-floppy --fs-uuid --set=root 0f76e1fb-5f53-421b-9c26-685ee52dbfe8
- echo 'Loading Linux 6.5.0-1-amd64 ...'
- linux /vmlinuz-6.5.0-1-amd64 root=UUID=39689532-2a77-460a-b60f-0d158f162012 ro quiet resume=UUID=7c5ebc0c-56ba-446a-b5d6-b3e7cae81b69 systemd.show_status=1 snd_hda_intel.dmic_detect=0
+ set root='hd0,gpt2'
+ if [ x$feature_platform_search_hint = xy ]; then
+ search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 31c430e1-9e6a-4543-ae3b-cc4128af9021
+ else
+ search --no-floppy --fs-uuid --set=root 31c430e1-9e6a-4543-ae3b-cc4128af9021
+ fi
+ echo 'Loading Linux 6.6.11-amd64 ...'
+ linux /boot/vmlinuz-6.6.11-amd64 root=UUID=31c430e1-9e6a-4543-ae3b-cc4128af9021 ro quiet
echo 'Loading initial ramdisk ...'
- initrd /initrd.img-6.5.0-1-amd64
+ initrd /boot/initrd.img-6.6.11-amd64
}
- menuentry 'Debian GNU/Linux, with Linux 6.5.0-1-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.5.0-1-amd64-recovery-39689532-2a77-460a-b60f-0d158f162012' {
+ menuentry 'Debian GNU/Linux, with Linux 6.6.11-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.6.11-amd64-recovery-31c430e1-9e6a-4543-ae3b-cc4128af9021' {
load_video
- gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
- search --no-floppy --fs-uuid --set=root 0f76e1fb-5f53-421b-9c26-685ee52dbfe8
- echo 'Loading Linux 6.5.0-1-amd64 ...'
- linux /vmlinuz-6.5.0-1-amd64 root=UUID=39689532-2a77-460a-b60f-0d158f162012 ro single single dis_ucode_ldr
+ set root='hd0,gpt2'
+ if [ x$feature_platform_search_hint = xy ]; then
+ search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 31c430e1-9e6a-4543-ae3b-cc4128af9021
+ else
+ search --no-floppy --fs-uuid --set=root 31c430e1-9e6a-4543-ae3b-cc4128af9021
+ fi
+ echo 'Loading Linux 6.6.11-amd64 ...'
+ linux /boot/vmlinuz-6.6.11-amd64 root=UUID=31c430e1-9e6a-4543-ae3b-cc4128af9021 ro single single dis_ucode_ldr
echo 'Loading initial ramdisk ...'
- initrd /initrd.img-6.5.0-1-amd64
+ initrd /boot/initrd.img-6.6.11-amd64
}
}
Edited to remove mistakes of text recognition
-
Sections that I see as relevant for (non-)display:
--- ideapad_grub.cfg [Working GRUB]
+++ /boot/grub/grub.cfg [non-Working GRUB]
@@ -55,24 +55,8 @@
[...]
- font=unicode
[code]
May be, no (proper) text display, but unlikely
[...]
-if loadfont $font ; then
- set gfxmode=1920x1080,1280x1024,1280x800,1280x720,1024x768,800x600,text
- load_video
- insmod gfxterm
Different display modes, loading of kind of graphics/display.
[...]
[code]
- insmod gettext
-fi
-terminal_output gfxterm
+terminal_input console
+terminal_output console
very critical regarding display, selection of console(?!) for output.
[...]
### END /etc/grub.d/00_header ###
+### BEGIN /etc/grub.d/05_debian_theme ###
+set menu_color_normal=cyan/blue
+set menu_color_highlight=white/blue
+### END /etc/grub.d/05_debian_theme ###
+
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
-set linux_gfx_mode=keep
+set linux_gfx_mode=
export linux_gfx_mode
Mode (change/no change) for display.
"keep" comes from /etc/default/grub.d/siduction.cfg
Nowhere seems to be the module load for (U)EFI-display modules.
[...]
Try to change entries to your advantage.
-
Sections that I see as relevant for (non-)display:
[...]
Try to change entries to your advantage.
Thank you. I posted the grub.cfg that is working now in console mode. That is, the last working version I had. But I have tried incorporating those settings from the other laptop to absolutely no avail. I now have three scenarios, and none of which is actually really OK:
- I enable console mode, then I see the blue screen grub of that mode and everything works
- I disable console mode hoping to achieve a graphical mode, grub menu disappears, but grub itself seems to be working in hidden mode
- This is new: after the latest round of playing with settings, I can enable the console mode that gives me the blue screen. But if I chose to see the available booting options, the screen changes to the chromatic setting with the black background, which indicates a mixed scenario.
The last version happened yesterday, after I tried a couple of settings. The strange thing is, I marked all my changes and made sure they are all removed, and the simple console mode enabled. Still, I get this mixed state!!! Really confused with what's going on here.
-
Thanks. May be, my concerns are irrelevant, but what I am missing in your configuration - with regard to the display - is something like what is appended here:
### BEGIN /etc/grub.d/00_header ###
[...]
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
if [ x$grub_platform = xefi ]; then
insmod efi_gop
insmod efi_uga
else
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
fi
}
[...]
### END /etc/grub.d/00_header ###
i.e. loading efi driver modules.
which is afterwards called like
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
if [ "${1}" = "keep" ]; then
set vt_handoff=vt.handoff=1
else
set vt_handoff=
fi
}
[...]
menuentry "Debian GNU/Linux Live ${debian12_vers} (nomodeset) [bookworm] (ISO)" --class debian --class gnu-linux --class gnu --class os {
recordfail
load_video
gfxmode $linux_gfx_mode
[...]
}
[...]
### END /etc/grub.d/10_linux ###
The colour-scheme should be something like
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
if background_color 44,0,30,0; then
clear
fi
### END /etc/grub.d/05_debian_theme ###
I do hope, it helps a little.
-
Thanks. May be, my concerns are irrelevant, but what I am missing in your configuration - with regard to the display - is something like what is appended here:
### BEGIN /etc/grub.d/00_header ###
[...]
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
if [ x$grub_platform = xefi ]; then
insmod efi_gop
insmod efi_uga
[...]
### END /etc/grub.d/00_header ###
[...]
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
if [ "${1}" = "keep" ]; then
set vt_handoff=vt.handoff=1
else
set vt_handoff=
fi
}
[...]
menuentry "Debian GNU/Linux Live ${debian12_vers} (nomodeset) [bookworm] (ISO)" --class debian --class gnu-linux --class gnu --class os {
recordfail
load_video
gfxmode $linux_gfx_mode
[...]
}
[...]
### END /etc/grub.d/10_linux ###
The colour-scheme should be something like
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
if background_color 44,0,30,0; then
clear
fi
### END /etc/grub.d/05_debian_theme ###
I do hope, it helps a little.
With a slightly different syntax, I have all that you point out. I suppose it was not shown in the diff because both laptops have it.
I'll continue to investigate.