How to Modify the GRUB Splash Screen  [Solved]

Help for Current Versions of MX
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Forum rules
Post Reply
Message
Author
User avatar
operadude
Posts: 1057
Joined: Tue Nov 05, 2019 12:08 am

How to Modify the GRUB Splash Screen

#1 Post by operadude »

Just re-installed my MX23-Xfce install from a good MX-Snapshot/LUM.
All MD5s (on both snapshot and Live USB) verified as good.

Upon reflection, I did make a minor change during the snapshot:
When creating the snapshot, there is a section at the bottom called "Optional Customization". In that box, by "Release Version", I added "Xfce", so it now reads: "23 - Xfce" (without the quotes). Not sure if that could have messed things up. Anyway...

Here's my QSI:

Code: Select all

Snapshot created on: 20231012_1725
System:
  Kernel: 6.1.0-13-amd64 [6.1.55-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-13-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel, plank wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23 - Xfce_x64 Libretto October 12  2023 base: Debian GNU/Linux
    12 (bookworm)
Machine:
  Type: Desktop System: Gigabyte product: H270-HD3 v: N/A serial: <superuser required>
  Mobo: Gigabyte model: H270-HD3-CF v: x.x serial: <superuser required> UEFI: American Megatrends
    v: F5 date: 04/24/2017
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse PID:0080 serial: N/A
    charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
  Info: model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake gen: core 7 level: v3
    note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 9
    microcode: 0x42
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
    desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 800 min/max: 800/3900 scaling: driver: intel_pstate governor: powersave
    cores: 1: 800 2: 800 3: 800 4: 800 bogomips: 31199
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Vulnerable: No microcode
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT
    vulnerable
  Type: retbleed status: Vulnerable
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass status: Vulnerable
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not
    affected
  Type: srbds status: Vulnerable: No microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Oland PRO [Radeon R7 240/340 / Radeon 520] vendor: Micro-Star MSI driver: radeon
    v: kernel alternate: amdgpu arch: GCN-1 code: Southern Islands process: TSMC 28nm built: 2011-20
    pcie: gen: 3 speed: 8 GT/s lanes: 8 ports: active: HDMI-A-1 empty: DVI-D-1,VGA-1
    bus-ID: 01:00.0 chip-ID: 1002:6613 class-ID: 0300 temp: 40.0 C
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: radeon
    unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: radeon display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
  Monitor-1: HDMI-A-1 mapped: HDMI-0 model: Samsung built: 2007 res: 1920x1080 hz: 60 dpi: 305
    gamma: 1.2 size: 160x90mm (6.3x3.54") diag: 184mm (7.2") ratio: 16:9 modes: max: 1920x1080
    min: 640x480
  API: OpenGL v: 4.5 Mesa 22.3.6 renderer: OLAND ( LLVM 15.0.6 DRM 2.50 6.1.0-13-amd64)
    direct-render: Yes
Audio:
  Device-1: Intel 200 Series PCH HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel
    bus-ID: 00:1f.3 chip-ID: 8086:a2f0 class-ID: 0403
  Device-2: AMD Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series]
    vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 8
    bus-ID: 01:00.1 chip-ID: 1002:aab0 class-ID: 0403
  API: ALSA v: k6.1.0-13-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I219-V vendor: Gigabyte driver: e1000e v: kernel port: N/A
    bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Drives:
  Local Storage: total: 7.72 TiB used: 5.42 TiB (70.1%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 250GB size: 232.89 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 1B2QEXE7 temp: 32.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 model: SATA SSD size: 111.79 GiB block-size: physical: 512 B
    logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 61.3 scheme: GPT
  ID-3: /dev/sdb maj-min: 8:16 vendor: Kingston model: SA400S37120G size: 111.79 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 61K1 scheme: MBR
  ID-4: /dev/sdc maj-min: 8:32 vendor: Seagate model: ST3000DM001-1ER166 size: 2.73 TiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: CC25 scheme: GPT
  ID-5: /dev/sdd maj-min: 8:48 vendor: Toshiba model: DT01ACA050 size: 465.76 GiB block-size:
    physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: A750
    scheme: GPT
  ID-6: /dev/sde maj-min: 8:64 vendor: Western Digital model: WD5000AADS-00S9B0 size: 465.76 GiB
    block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> rev: 0A01
    scheme: GPT
  ID-7: /dev/sdf maj-min: 8:80 type: USB vendor: Seagate model: Expansion Desk size: 3.64 TiB
    block-size: physical: 4096 B logical: 4096 B type: N/A serial: <filter> rev: 0739 scheme: MBR
Partition:
  ID-1: / raw-size: 25 GiB size: 24.44 GiB (97.76%) used: 9.34 GiB (38.2%) fs: ext4
    dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 1.6 MiB (0.7%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 25 GiB size: 24.44 GiB (97.76%) used: 9.11 GiB (37.3%) fs: ext4
    dev: /dev/nvme0n1p3 maj-min: 259:3
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 32 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p10
    maj-min: 259:10
Sensors:
  System Temperatures: cpu: 40.0 C mobo: N/A gpu: radeon temp: 40.0 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2358 libs: 1233 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mxrepo.com/mx/repo/ bookworm main non-free
  Active apt repos in: /etc/apt/sources.list.d/skype-stable.list
    1: deb [arch=amd64] https://repo.skype.com/deb stable main
Info:
  Processes: 277 Uptime: 2m wakeups: 3 Memory: 31.3 GiB used: 2.16 GiB (6.9%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12 Client: shell wrapper
  v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
When GRUB starts (splash screen), at the top, it says:
"Debian", and not the familiar: "MX 23 Libretto"

Is there a way to edit/modify the GRUB splash screen so that it says "MX 23 Libretto" ?

I did try using the "e" option and changing the name from "Debian" to "MX 23...", but that change doesn't stick: upon re-boot, I get "Debian" again.

A very minor thing, but I would like to know how to alter/edit the GRUB splash screen.

Also, tried MX Tools -> Boot Options, but the drop-down "Boot to" menu only lists the entries that already exist, and does not allow me to change or edit them.

Awaiting some Pro Tips... :crossfingers:
Top
User avatar
fehlix
Developer
Posts: 12888
Joined: Wed Apr 11, 2018 5:09 pm

Re: How to Modify the GRUB Splash Screen  [Solved]

#2 Post by fehlix »

Suggest this:
Open /etc/lsb-release , e.g with featherpad like this:
Open terminal as nomal user:

Code: Select all

fpad  /etc/lsb-release
And change this line:
from

Code: Select all

DISTRIB_RELEASE=23 - Xfce
to

Code: Select all

DISTRIB_RELEASE=23
And maybe adjust those two lines. so they look like this to:

Code: Select all

PRETTY_NAME="MX 23 - Xfce Libretto"
DISTRIB_DESCRIPTION="MX 23 - Xfce Libretto"
when done. To save you will be asked to enter the authentication password.
Close featherpad and run

Code: Select all

sudo update-grub
HTH
Top
User avatar
operadude
Posts: 1057
Joined: Tue Nov 05, 2019 12:08 am

Re: How to Modify the GRUB Splash Screen

#3 Post by operadude »

@fehlix : Thanks for the quick reply!

First time in a while, but hit the sack early.

Will try your suggestion now, and get back to you.

:crossfingers:
Top
User avatar
operadude
Posts: 1057
Joined: Tue Nov 05, 2019 12:08 am

Re: How to Modify the GRUB Splash Screen

#4 Post by operadude »

We Have a Winner:

@fehlix :number1:

Perfect: Now GRUB splash screen is back to the more familiar "MX 23 - Xfce Libretto" :exclamation:

BTW, earlier, I modified /etc/lsb-release , since I noticed on my QSI (before posting) a strange line at the top, which read something like "/etc/lsb-release, line 3, command not found", and so, I changed it back to what I thought were the defaults. If memory serves correct, something like this:

Code: Select all

PRETTY_NAME="MX 23 Libretto"
DISTRIB_ID="MX"
DISTRIB_RELEASE=23
DISTRIB_CODENAME="Libretto"
DISTRIB_DESCRIPTION="MX 23 Libretto"
For some reason, that didn't seem to work, and I kept getting the (default?) "Debian" for PRETTY_NAME. Maybe I just forgot to update GRUB, but I'm pretty sure I did. Anyway...

Fehlix, as per your suggestions in the past, I am using a bootloader-id ("MX23-Xfce") in conjunction with "rEFInd". Just out of curiosity, does the EFI bootloader-id have any relationship/impact on the GRUB variables in /etc/lsb-release, such as, "PRETTY_NAME"?

I see that in my: /boot/efi/EFI/MX23-Xfce directory, there is "grubx64.efi", but it still has yesterday's date, even after modifying /etc/lsb-release just now (today) and updating GRUB; so, I'm not sure how this is all working.

Any enlightenment from you would be wonderful :p

And, as per usual: Thank You SO Much :exclamation:

:cool:
Top
User avatar
fehlix
Developer
Posts: 12888
Joined: Wed Apr 11, 2018 5:09 pm

Re: How to Modify the GRUB Splash Screen

#5 Post by fehlix »

operadude wrote: Thu Oct 12, 2023 9:03 pm Fehlix, as per your suggestions in the past, I am using a bootloader-id ("MX23-Xfce") in conjunction with "rEFInd". Just out of curiosity, does the EFI bootloader-id have any relationship/impact on the GRUB variables in /etc/lsb-release, such as, "PRETTY_NAME"?
No.
operadude wrote: Thu Oct 12, 2023 9:03 pm I see that in my: /boot/efi/EFI/MX23-Xfce directory, there is "grubx64.efi", but it still has yesterday's date, even after modifying /etc/lsb-release just now (today) and updating GRUB; so, I'm not sure how this is all working.
EFI is "running" before GRUB menu "handling". update-grub is "only" about GRUB menu. EFI would take what evener GRUB menu have been generated.
Top
User avatar
operadude
Posts: 1057
Joined: Tue Nov 05, 2019 12:08 am

Re: How to Modify the GRUB Splash Screen

#6 Post by operadude »

@fehlix
fehlix wrote: Fri Oct 13, 2023 2:52 am
operadude wrote: Thu Oct 12, 2023 9:03 pm Fehlix, as per your suggestions in the past, I am using a bootloader-id ("MX23-Xfce") in conjunction with "rEFInd". Just out of curiosity, does the EFI bootloader-id have any relationship/impact on the GRUB variables in /etc/lsb-release, such as, "PRETTY_NAME"?
No.
operadude wrote: Thu Oct 12, 2023 9:03 pm I see that in my: /boot/efi/EFI/MX23-Xfce directory, there is "grubx64.efi", but it still has yesterday's date, even after modifying /etc/lsb-release just now (today) and updating GRUB; so, I'm not sure how this is all working.
EFI is "running" before GRUB menu "handling". update-grub is "only" about GRUB menu. EFI would take what evener GRUB menu have been generated.
Thanks for the clarification :exclamation:

It is slowly sinking in :happy:

:cool:
Top
User avatar
operadude
Posts: 1057
Joined: Tue Nov 05, 2019 12:08 am

Re: How to Modify the GRUB Splash Screen

#7 Post by operadude »

For posterity, just want to add these recent comments, from a separate thread:

https://forum.mxlinux.org/viewtopic.ph ... 5#p748425

In that post, I found @fehlix's comments very enlightening regarding my issue:
GRUB booting goes broadly speaking in two parts:
A* loading the grub-boot loader, which finally...
B* loads the grub-menu
The grub-menu is for both UEFI- and BIOS booting nearly identical, with small exceptions like memory test entry
and an entry to "boot" into UEFI-system setup (aka PC-BIOS/UEFI firmware setup).
And the GRUB-menu can be "loaded" from both BIOS-/ and UEFI-grub boot loader.

The GRUB boot-loader used in step A is "generated" with the so called "grub-install" step -internally running "grub-install".

The GRUB menu generation used in step B is separate and generated with update-grub (aka grub-mkconfig).
When new kernels got installed, the installation triggers within post-install step via grub-mkconfig the re-generation of the GRUB menu so it will hold the new kernel entries, which is ready to provide a GRUB menu for both UEFI- and BIOS booting.
That's it.
HTH
I think Fehlix's comments explain some of my earlier confusion regarding the GRUB menu, and the separate GRUB file that is in my "refind" directory, which gets executed BEFORE the grub menu. Fehlix summed-it-up best from his post on this thread (edited slightly):
EFI is "running" before GRUB menu "handling". update-grub is "only" about GRUB menu. EFI would take whatever GRUB menu has been generated.
As I said before, "slowly sinking in"... ;)
Top
Post Reply

Return to “MX Help”