Solved. Huge MX Logo apearing during start-up. How to stop it? [Solved]

[LateJunction]

During the last few days my MX PC shows a very large MX Logo, on a plain dark background, occupying about 40% of the width of my 40" monitor running at 3840 x 2160. This phase of start up - after grub has been 'processed' but before the xfce desktop is displayed - is taking about 30 seconds. Previously it took about 2 seconds. I assume it's my fault - I must have inadvertently fiddled with something; how do I revert to the previous, much faster start up procedure?

Code: Select all

System:
  Kernel: 6.9.12-2-liquorix-amd64 [6.9-12~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable BOOT_IMAGE=/boot/vmlinuz-6.9.12-2-liquorix-amd64 root=UUID=<filter> ro
    quiet iommu=off splash init=/lib/systemd/systemd
  Desktop: Xfce v: 4.20.0 tk: Gtk v: 3.24.38 info: xfce4-panel wm: xfwm v: 4.20.0 vt: 7
    dm: LightDM v: 1.32.0 Distro: MX-23.6_x64 Libretto October 15  2023 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop Mobo: Gigabyte model: H81M-S2H v: x.x serial: <superuser required>
    UEFI: American Megatrends v: F2 date: 08/11/2015
CPU:
  Info: model: Intel Core i7-4790 bits: 64 type: MT MCP arch: Haswell gen: core 4 level: v3
    note: check built: 2013-15 process: Intel 22nm family: 6 model-id: 0x3C (60) stepping: 3
    microcode: 0x28
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB
    desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 1336 high: 2395 min/max: 800/3601 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 1796 2: 1303 3: 1796 4: 2395 5: 800 6: 800
    7: 800 8: 1000 bogomips: 57471
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: conditional; RSB
    filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GP107 [GeForce GTX 1050] vendor: ZOTAC driver: nvidia v: 535.247.01
    non-free: 530.xx+ status: current (as of 2023-03) arch: Pascal code: GP10x process: TSMC 16nm
    built: 2016-21 pcie: gen: 2 speed: 5 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:1c81
    class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.20.0 driver: X: loaded: nvidia
    gpu: nvidia display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 3072x1728 s-dpi: 96 s-size: 813x458mm (32.01x18.03") s-diag: 933mm (36.74")
  Monitor-1: HDMI-0 res: 3072x1728 dpi: 88 size: 890x500mm (35.04x19.69") diag: 1021mm (40.19")
    modes: N/A
  API: OpenGL v: 4.6.0 NVIDIA 535.247.01 renderer: NVIDIA GeForce GTX 1050/PCIe/SSE2
    direct-render: Yes
Audio:
  Device-1: Intel 8 Series/C220 Series High Definition Audio vendor: Gigabyte 8
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8c20 class-ID: 0403
  Device-2: NVIDIA GP107GL High Definition Audio vendor: ZOTAC driver: snd_hda_intel v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:0fb9 class-ID: 0403
  API: ALSA v: k6.9.12-2-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 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: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte driver: r8169
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 03:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 1.47 TiB used: 587.29 GiB (38.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD10EZEX-75ZF5A0 size: 931.51 GiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: N/A serial: <filter> rev: 0A80
    scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST3500312CS size: 465.76 GiB block-size:
    physical: 512 B logical: 512 B speed: 1.5 Gb/s type: HDD rpm: 5900 serial: <filter> rev: SC13
    scheme: MBR
  ID-3: /dev/sdc maj-min: 8:32 vendor: SanDisk model: SDSSDA120G size: 111.79 GiB block-size:
    physical: 512 B logical: 512 B speed: 3.0 Gb/s type: SSD serial: <filter> rev: 00RL scheme: GPT
Partition:
  ID-1: / raw-size: 83.66 GiB size: 81.79 GiB (97.77%) used: 33.06 GiB (40.4%) fs: ext4
    dev: /dev/sdc3 maj-min: 8:35
  ID-2: /boot/efi raw-size: 7.62 GiB size: 7.6 GiB (99.80%) used: 288 KiB (0.0%) fs: vfat
    dev: /dev/sdc1 maj-min: 8:33
  ID-3: /home raw-size: 465.76 GiB size: 457.38 GiB (98.20%) used: 224.02 GiB (49.0%) fs: ext4
    dev: /dev/sdb1 maj-min: 8:17
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 20.51 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdc2
    maj-min: 8:34
Sensors:
  System Temperatures: cpu: 37.0 C mobo: N/A gpu: nvidia temp: 34 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 46%
Repos:
  Packages: 3491 pm: dpkg pkgs: 3456 libs: 2005 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 35
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [arch=amd64 signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https://brave-browser-apt-release.s3.brave.com/ stable main
  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
  No active apt repos in: /etc/apt/sources.list.d/graphics:darktable.list
  No active apt repos in: /etc/apt/sources.list.d/graphics:darktable:master.list
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb https://mirrors.ukfast.co.uk/sites/MX_antiX_packages/mx/repo/ bookworm main non-free
  Active apt repos in: /etc/apt/sources.list.d/qgis.sources
    1: deb deb-src [arch=amd64] https://qgis.org/debian bookworm main
  Active apt repos in: /etc/apt/sources.list.d/winehq-bookworm.sources
    1: deb [arch=amd64 i386] https://dl.winehq.org/wine-builds/debian bookworm main
Info:
  Processes: 353 Uptime: 2h 44m wakeups: 1 Memory: 15.65 GiB used: 2.39 GiB (15.3%) Init: systemd
  v: 252 target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

[j2mcgreg]

Some have reported performance hits when running SystemD. Try rebooting and at the grub screen select Advanced Options then select a standard kernel as the boot choice for the session. If this delay disappears, you can make the switch permanent with Boot Options in MX Tools.

[CharlesV]

You can start by hitting esc at start up (as soon as the logo is on screen) and then reading / watching the terminal output... you should see a long lag between the last working startup process and then the next one which is most likely the issue. ( You may need to record the screen on your phone to see it all if its too fast.)

Also you can use the following in a terminal to see the boot logs.

Code: Select all

sudo more  /var/log/boot.log.1

The files are listed as .1, .2, .3 set for previous boots

Check your date and time entries on the log(s) to see when the lag occurred.

Also, you can use the QSI tool, clicking on the left log displays it, with a time sequence. kern, xorg & syslog may help you find the culprit.

[siamhie]

During the last few days my MX PC shows a very large MX Logo, on a plain dark background, occupying about 40% of the width of my 40" monitor running at 3840 x 2160. This phase of start up - after grub has been 'processed' but before the xfce desktop is displayed - is taking about 30 seconds. Previously it took about 2 seconds. I assume it's my fault - I must have inadvertently fiddled with something; how do I revert to the previous, much faster start up procedure?

What do you remember doing before the boot times changed?

[Eadwine Rose]

Moved to correct forum. Has nothing to do with installing MX Linux. Please be mindful where you post.

[LateJunction]

Moved to correct forum. Has nothing to do with installing MX Linux. Please be mindful where you post.

With respect I did spend some time thinking about which would be the most appropriate forum, bearing in mind I am no expert in such matters, I believed that I very much had an MX install issue, confusing 'install' with 'start'. So where then is the correct forum?

[Eadwine Rose]

As I said.. I moved it, it is already in a better spot. When in doubt just put it in MX Help.

[LateJunction]

What do you remember doing before the boot times changed?

Post deleted by user

[LateJunction]

You can start by hitting esc at start up (as soon as the logo is on screen) and then reading / watching the terminal output... you should see a long lag between the last working startup process and then the next one which is most likely the issue. ( You may need to record the screen on your phone to see it all if its too fast.)

Also you can use the following in a terminal to see the boot logs.

Code: Select all

sudo more  /var/log/boot.log.1

The files are listed as .1, .2, .3 set for previous boots

Check your date and time entries on the log(s) to see when the lag occurred.

Also, you can use the QSI tool, clicking on the left log displays it, with a time sequence. kern, xorg & syslog may help you find the culprit.

I notice a lot of the following in that boot.log.1:

Code: Select all

----------- Tue Aug 05 17:53:44 BST 2025 ------------
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: error opening /dev/md?*: No such file or directory
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
Gave up waiting for suspend/resume device

Bit of a disappointment that I have no idea what it means.

[CharlesV]

I dont see any RAID setup on your machine in QSI, but that is what the mdadm package is all about

Check your /etc/mdadm/mdadm.conf file and see if it is specifying an raid, and if it is, then you need to figure out why it is.

And if your not running any raid, you should be able to just remove mdadm and that should resolve this.