System booting slowly

LMDE-Newbie · Post by **LMDE-Newbie** » Sat Sep 11, 2021 5:03 pm

Hello,
My system is booting very slowly. Linux Mint starts nice and fast, it's just the time the system spends on the initial "Gigabyte" screen (as my Motherboard is from Gigabyte).
Running systemd-analyze resulted in

Code: Select all

Startup finished in 31.496s (firmware) + 656ms (loader) + 7.696s (kernel) + 1min 30.281s (userspace) = 2min 10.131s 
graphical.target reached after 4.186s in userspace

My problem is the firmware part. It doesn't seem logical to me that the system would need 30s before even showing the GRUB bootloader.
I have a Kingston A2000 PCIe SSD as boot drive and my CPU is a Ryzen 5 2600, so I don't think I should be limited by hardware here.

I'd be grateful for any ideas, thanks in advance

Post by **SMG** » Tue Sep 14, 2021 7:50 pm

LMDE-Newbie wrote: ⤴Sat Sep 11, 2021 5:03 pmHello,
My system is booting very slowly. Linux Mint starts nice and fast, it's just the time the system spends on the initial "Gigabyte" screen (as my Motherboard is from Gigabyte).

If you go into your computer's BIOS/UEFI, are you seeing the Gigabyte screen before the BIOS screen? Or both before and after BIOS?

LMDE-Newbie wrote: ⤴Sat Sep 11, 2021 5:03 pm Running systemd-analyze resulted in
Code: Select all
Startup finished in 31.496s (firmware) + 656ms (loader) + 7.696s (kernel) + 1min 30.281s (userspace) = 2min 10.131s 
graphical.target reached after 4.186s in userspace
My problem is the firmware part. It doesn't seem logical to me that the system would need 30s before even showing the GRUB bootloader.

There is the BIOS/UEFI firmware which gets ready, then grub shows up, and then after grub selects an operating system the operating system starts up. All the times you listed are for the time period after grub selects the operating system. All of what you listed happens after grub.

Please provide the output of systemd-analyze critical-chain and inxi -Fxxxrz

SimonPeter · Post by **SimonPeter** » Wed Sep 15, 2021 3:46 am

Please provide the output of this command too:
cat /etc/fstab

LMDE-Newbie · Post by **LMDE-Newbie** » Wed Sep 15, 2021 6:17 am

SMG wrote: ⤴Tue Sep 14, 2021 7:50 pm If you go into your computer's BIOS/UEFI, are you seeing the Gigabyte screen before the BIOS screen? Or both before and after BIOS?

It only shows up before the UEFI. So immediately after powering on it shows up and always stays there for 30 seconds or so (measured manually). Even if I press Delete to enter BIOS (or F10 to enter the boot menu), it waits the full 30s before showing BIOS.
If I don't enter BIOS, grub shows up after that 30s and from there everything is perfectly normal.

SMG wrote: ⤴Tue Sep 14, 2021 7:50 pm All of what you listed happens after grub.

OK, that's good to know. I thought that 31s firmware part corresponded to my measured 30 seconds, because after that it only takes 10-15 seconds to get to the login screen.

Code: Select all

systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @4.692s
└─multi-user.target @4.692s
  └─lxc.service @4.660s +31ms
    └─lxc-net.service @4.650s +7ms
      └─network-online.target @4.643s
        └─NetworkManager-wait-online.service @1.750s +2.892s
          └─NetworkManager.service @1.688s +59ms
            └─dbus.service @1.684s
              └─basic.target @1.662s
                └─sockets.target @1.662s
                  └─dbus.socket @1.662s
                    └─sysinit.target @1.655s
                      └─brltty.service @1.634s +21ms
                        └─systemd-udev-settle.service @319ms +1.312s
                          └─systemd-udev-trigger.service @262ms +56ms
                            └─systemd-udevd-kernel.socket @262ms
                              └─system.slice @253ms
                                └─-.slice @253ms

Code: Select all

inxi -Fxxxrz
System:
  Host: my-pc Kernel: 4.19.0-17-amd64 x86_64 bits: 64 compiler: gcc 
  v: 8.3.0 Desktop: Cinnamon 5.0.5 wm: muffin 5.0.1 dm: LightDM 1.26.0 
  Distro: LMDE 4 Debbie base: Debian 10.2 buster 
Machine:
  Type: Desktop System: Gigabyte product: B450M DS3H v: N/A serial: <filter> 
  Mobo: Gigabyte model: B450M DS3H-CF v: x.x serial: <filter> 
  UEFI: American Megatrends v: F1 date: 06/06/2018 
CPU:
  Topology: 6-Core model: AMD Ryzen 5 2600 bits: 64 type: MT MCP arch: Zen+ 
  rev: 2 L2 cache: 3072 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 81438 
  Speed: 1496 MHz min/max: 1550/3400 MHz boost: enabled Core speeds (MHz): 
  1: 1376 2: 1442 3: 1547 4: 1546 5: 1378 6: 1382 7: 1378 8: 1381 9: 1547 
  10: 1546 11: 1546 12: 1547 
Graphics:
  Device-1: AMD Ellesmere [Radeon RX 470/480] vendor: Sapphire Limited 
  driver: amdgpu v: kernel bus ID: 07:00.0 chip ID: 1002:67df 
  Display: x11 server: X.Org 1.20.4 driver: amdgpu,ati 
  unloaded: fbdev,modesetting,vesa tty: N/A 
  OpenGL: renderer: Radeon RX 580 Series (POLARIS10 DRM 3.27.0 
  4.19.0-17-amd64 LLVM 7.0.1) 
  v: 4.5 Mesa 18.3.6 direct render: Yes 
Audio:
  Device-1: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] 
  vendor: Sapphire Limited driver: snd_hda_intel v: kernel bus ID: 07:00.1 
  chip ID: 1002:aaf0 
  Device-2: AMD Family 17h HD Audio vendor: Gigabyte driver: snd_hda_intel 
  v: kernel bus ID: 09:00.3 chip ID: 1022:1457 
  Device-3: C-Media type: USB driver: hid-generic,snd-usb-audio,usbhid 
  bus ID: 1-4:2 chip ID: 0d8c:0134 serial: <filter> 
  Sound Server: ALSA v: k4.19.0-17-amd64 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Gigabyte driver: r8169 v: kernel port: f000 bus ID: 05:00.0 
  chip ID: 10ec:8168 
  IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 1.36 TiB used: 496.56 GiB (35.5%) 
  ID-1: /dev/nvme0n1 vendor: Kingston model: SA2000M81000G size: 931.51 GiB 
  speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: S5Z42105 scheme: GPT 
  ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB 
  speed: 6.0 Gb/s serial: <filter> rev: 020 scheme: MBR 
Partition:
  ID-1: / size: 377.47 GiB used: 116.03 GiB (30.7%) fs: ext4 
  dev: /dev/nvme0n1p5 
Sensors:
  System Temperatures: cpu: 33.2 C mobo: N/A gpu: amdgpu temp: 40 C 
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 781 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/additional-repositories.list 
  1: deb [trusted=yes] https://repo.protonvpn.com/debian unstable main
  2: deb https://dl.winehq.org/wine-builds/debian/ buster main
  Active apt repos in: /etc/apt/sources.list.d/linuxuprising-java.list 
  1: deb http://ppa.launchpad.net/linuxuprising/java/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/mono-official-stable.list 
  1: deb https://download.mono-project.com/repo/debian stable-buster main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://ftp.halifax.rwth-aachen.de/linuxmint debbie main upstream import backport
  2: deb https://deb.debian.org/debian/ buster main contrib non-free
  3: deb https://deb.debian.org/debian/ buster-updates main contrib non-free
  4: deb http://security.debian.org/ buster/updates main contrib non-free
  5: deb https://deb.debian.org/debian/ buster-backports main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/official-source-repositories.list 
  1: deb-src http://ftp.halifax.rwth-aachen.de/linuxmint debbie main upstream import backport
  2: deb-src https://deb.debian.org/debian/ buster main contrib non-free
  3: deb-src https://deb.debian.org/debian/ buster-updates main contrib non-free
  4: deb-src http://security.debian.org/ buster/updates main contrib non-free
  5: deb-src https://deb.debian.org/debian/ buster-backports main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/protonvpn-stable.list 
  1: deb [signed-by=/usr/share/keyrings/protonvpn-stable-archive-keyring.gpg] https://repo.protonvpn.com/debian stable main
  Active apt repos in: /etc/apt/sources.list.d/teams.list 
  1: deb [arch=amd64] https://packages.microsoft.com/repos/ms-teams stable main
  Active apt repos in: /etc/apt/sources.list.d/teamviewer.list 
  1: deb https://linux.teamviewer.com/deb stable main
  Active apt repos in: /etc/apt/sources.list.d/vscode.list 
  1: deb [arch=amd64,arm64,armhf] http://packages.microsoft.com/repos/code stable main
Info:
  Processes: 281 Uptime: 7m Memory: 15.68 GiB used: 2.86 GiB (18.3%) 
  Init: systemd v: 241 runlevel: 5 Compilers: gcc: 8.3.0 alt: 8 
  clang: 7.0.1-8+deb10u2 Shell: bash v: 5.0.3 running in: gnome-terminal 
  inxi: 3.0.32

And finally:

Code: Select all

cat /etc/fstab
# UNCONFIGURED FSTAB FOR BASE SYSTEM
proc	/proc	proc	defaults	0	0
# /dev/sda2
UUID=D0CD-21E7	/boot/efi	vfat	defaults	0	0
# /dev/sda5
UUID=61efc9ef-c7df-4a78-a487-03236f4f676a	/	ext4	rw,errors=remount-ro	0	1
/dev/disk/by-uuid/6DA8-C63B /media/cab/Shared auto nosuid,nodev,nofail,x-gvfs-show 0 0
/dev/disk/by-uuid/4f96a0a0-32a6-45f3-8adc-52489addf7d4 /mnt/4f96a0a0-32a6-45f3-8adc-52489addf7d4 auto nosuid,nodev,nofail,x-gvfs-show 0 0
/dev/disk/by-uuid/78B32CB8573E1F98 /mnt/78B32CB8573E1F98 auto nosuid,nodev,nofail,x-gvfs-show 0 0

Post by **SMG** » Wed Sep 15, 2021 11:02 am

LMDE-Newbie wrote: ⤴Wed Sep 15, 2021 6:17 am
SMG wrote: ⤴Tue Sep 14, 2021 7:50 pm If you go into your computer's BIOS/UEFI, are you seeing the Gigabyte screen before the BIOS screen? Or both before and after BIOS?
It only shows up before the UEFI. So immediately after powering on it shows up and always stays there for 30 seconds or so (measured manually). Even if I press Delete to enter BIOS (or F10 to enter the boot menu), it waits the full 30s before showing BIOS.
If I don't enter BIOS, grub shows up after that 30s and from there everything is perfectly normal.

If that show for 30 seconds even before you are able to get into BIOS, then that is a hardware setting/issue. That is not related to grub or Mint because grub and Mint happen after the hardware is initialized.

The critical chain output does not indicate any particularly long services.

The B450M DS3H (rev. 1.x): Support : BIOS indicates there are newer versions available. I do not know if any of them would reduce the 30 seconds delay you are experiencing.

I believe Gigabyte also has a community forum. Perhaps others have run into this issue and might have ideas of what could cause it to happen.

LMDE-Newbie · Post by **LMDE-Newbie** » Wed Sep 15, 2021 11:45 am

I see, thank you very much for looking into it, though.
You are probably right that this isn't exactly the right forum to ask, so I'll look around elsewhere

Aztaroth · Post by **Aztaroth** » Wed Sep 15, 2021 12:34 pm

Hello,
I don't know if it was SimonPeter's idea when he asked for etc/fstab but are the last three disks beginning with /dev/disk/by-uuid... present at boot ? Searching for an absent disk or partition can sometimes explain those slow boots.
Perhaps try editing the etc/fstab in administrator mode :

Code: Select all

xed admin:///etc/fstab

and adding a hashtag (#) in front of these lines to disable them and see if the next boot comes quicker.
If it does, use the same command to enable them one by one by deleting the hashtag and see who's the culprit.

Another try could be to upgrade your kernel. A Ryzen 5 with NVME disk is far from being optimized by LMDE4's native 4.19 kernel. However this procedure is sometimes shaky with a proprietary graphic driver (it's well known for Nvidia, perhaps AMD is more compliant). The obvious consequence is to take a Timeshift snap and backing up personal files before trying anything.
On my laptop, I had some 'red lines' in my kernel messages when using 4.19 after installing a M2 520Gb SSD. Upgrading kernel fixed it.
PS : the command invoked for the 'red lines' is :

Code: Select all

dmesg --level=err -T

Eventually, if you have some you can't decipher, post them below.

SimonPeter · Post by **SimonPeter** » Wed Sep 15, 2021 2:36 pm

Aztaroth wrote: ⤴Wed Sep 15, 2021 12:34 pm Hello,
I don't know if it was SimonPeter's idea when he asked for etc/fstab but are the last three disks beginning with /dev/disk/by-uuid... present at boot ? Searching for an absent disk or partition can sometimes explain those slow boots.
Perhaps try editing the etc/fstab in administrator mode :
Code: Select all
xed admin:///etc/fstab
and adding a hashtag (#) in front of these lines to disable them and see if the next boot comes quicker.
If it does, use the same command to enable them one by one by deleting the hashtag and see who's the culprit.

Yes this was what I thought of when I asked to cat /etc/fstab

Aztaroth wrote: ⤴Wed Sep 15, 2021 12:34 pm Another try could be to upgrade your kernel. A Ryzen 5 with NVME disk is far from being optimized by LMDE4's native 4.19 kernel. However this procedure is sometimes shaky with a proprietary graphic driver (it's well known for Nvidia, perhaps AMD is more compliant). The obvious consequence is to take a Timeshift snap and backing up personal files before trying anything.
On my laptop, I had some 'red lines' in my kernel messages when using 4.19 after installing a M2 520Gb SSD. Upgrading kernel fixed it.
PS : the command invoked for the 'red lines' is :
Code: Select all
dmesg --level=err -T
Eventually, if you have some you can't decipher, post them below.

Why not use Linux Mint 20.2 ? (LMDE 4 has a 4.19 kernel, which may be a bit old for your hardware).

Aztaroth · Post by **Aztaroth** » Wed Sep 15, 2021 3:13 pm

SimonPeter wrote: ⤴Wed Sep 15, 2021 2:36 pm Why not use Linux Mint 20.2 ? (LMDE 4 has a 4.19 kernel, which may be a bit old for your hardware).

Yes, but that can be changed :

Code: Select all

~$ inxi -S
System:
  Host: asus Kernel: 5.11.15-051115-generic x86_64 bits: 64 
  Desktop: Cinnamon 5.0.5 Distro: LMDE 4 Debbie

And you may even end with a more recent kernel than LM20
Works fine, although I'm not using the nvidia graphic driver but kernel's nouveau. I'm perhaps lucky with that kernel, but then I'm lucky 5 times : desktop, laptop, wife, kids.
LMDE4's kernel limitation is 5.11.x ; starting from 5.12, a newer lib6c is required but apps using the native version could cease running if a lib6c upgrade.
On another hand, checking myself (always a good idea

), I noticed on the Debian Wiki that a free driver for AMD/ATI GPU is available. So, AMD/ATI may effectively be more compliant when upgrading the kernel.
https://wiki.debian.org/AtiHowTo

Of course, this is only relevant if the OP wants to stick with LMDE4. The other options are LM20 or wait for LMDE5 which will probably be shipped with Debian 11's 5.10 kernel, especially if, as we guessed, his problems may be caused by an absent disk or partition.

Post by **SMG** » Wed Sep 15, 2021 3:20 pm

Aztaroth wrote: ⤴Wed Sep 15, 2021 3:13 pmOf course, this is only relevant if the OP wants to stick with LMDE4. The other options are LM20 or wait for LMDE5 which will probably be shipped with Debian 11's 5.10 kernel, especially if, as we guessed, his problems may be caused by an absent disk or partition.

I think the information you and Simon Peter have provided may be valuable to the OP, but the delay of 30 seconds happens even when booting into BIOS just to change the boot order. How is what is in fstab affect the time it takes BIOS to boot?

SimonPeter · Post by **SimonPeter** » Wed Sep 15, 2021 3:28 pm

SMG wrote: ⤴Wed Sep 15, 2021 3:20 pm
Aztaroth wrote: ⤴Wed Sep 15, 2021 3:13 pmOf course, this is only relevant if the OP wants to stick with LMDE4. The other options are LM20 or wait for LMDE5 which will probably be shipped with Debian 11's 5.10 kernel, especially if, as we guessed, his problems may be caused by an absent disk or partition.
I think the information you and Simon Peter have provided may be valuable to the OP, but the delay of 30 seconds happens even when booting into BIOS just to change the boot order. How is what is in fstab affect the time it takes BIOS to boot?

Startup finished in 31.496s (firmware) + 656ms (loader) + 7.696s (kernel) + 1min 30.281s (userspace) = 2min 10.131s

31.496s (firmware) + 656ms (loader) + 7.696s (kernel) = For experts like SMG
1min 30.281s (userspace) = For common people like Aztaroth and me.

I don't know very advanced things like BIOS, kernel etc., That is for experts like you (SMG).

I only know that lot of /etc/fstab entries increases boot time.

Post by **SMG** » Wed Sep 15, 2021 3:37 pm

SimonPeter wrote: ⤴Wed Sep 15, 2021 3:28 pm31.496s (firmware) + 656ms (loader) + 7.696s (kernel) = For experts like SMG

That is not the boot time into BIOS. That is the firmware loading section of the operating system which happens after BIOS.

The below time was the issue for the OP. It is possible the boot time of LMDE4 can be faster, but I am not aware that will not change the below (but I am open to learning something new if it will).

SMG wrote: ⤴Wed Sep 15, 2021 11:02 am
LMDE-Newbie wrote: ⤴Wed Sep 15, 2021 6:17 am
SMG wrote: ⤴Tue Sep 14, 2021 7:50 pm If you go into your computer's BIOS/UEFI, are you seeing the Gigabyte screen before the BIOS screen? Or both before and after BIOS?
It only shows up before the UEFI. So immediately after powering on it shows up and always stays there for 30 seconds or so (measured manually). Even if I press Delete to enter BIOS (or F10 to enter the boot menu), it waits the full 30s before showing BIOS.
If I don't enter BIOS, grub shows up after that 30s and from there everything is perfectly normal.
If that show for 30 seconds even before you are able to get into BIOS, then that is a hardware setting/issue. That is not related to grub or Mint because grub and Mint happen after the hardware is initialized.

SimonPeter · Post by **SimonPeter** » Wed Sep 15, 2021 3:50 pm

SMG wrote: ⤴Wed Sep 15, 2021 3:37 pm That is not the boot time into BIOS. That is the firmware loading section of the operating system which happens after BIOS.

I learned a new fact!

BTW: Sorry for my ignorance.

LMDE-Newbie · Post by **LMDE-Newbie** » Wed Sep 15, 2021 4:36 pm

Hello again,
thanks for all your replies. I have already made some progress due to your advice.
I noticed if I ran systemd-analyze quickly after logging in, I'd get the following:

Code: Select all

systemd-analyze 
Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0).
Please try again later.
Hint: Use 'systemctl list-jobs' to see active jobs

systemctl list-jobs 
JOB UNIT                                    TYPE  STATE  
 21 media-cab-Shared.mount                  start waiting
 22 dev-disk-by\x2duuid-6DA8\x2dC63B.device start running
2 jobs listed.

//some time later
systemd-analyze 
Startup finished in 31.284s (firmware) + 1.171s (loader) + 7.477s (kernel) + 1min 30.264s (userspace) = 2min 10.199s 
graphical.target reached after 4.550s in userspace

and after commenting out the line /dev/disk/by-uuid/6DA8-C63B /media/cab/Shared auto nosuid,nodev,nofail,x-gvfs-show 0 0 in fstab the situation already improved:

Code: Select all

systemd-analyze 
Startup finished in 27.516s (firmware) + 1.352s (loader) + 7.460s (kernel) + 4.216s (userspace) = 40.546s 
graphical.target reached after 4.203s in userspace

The other two lines don't make a difference, and those are partitions I definitely want auto-mounted anyway.
Now, the "Gigabyte screen" still remains on screen roughly the same amount of time, I'd say. But if the line isn't needed anyway, any improvement is welcome.

The low kernel version has bugged me for some time, and I am actually thinking of switching to LM 20.2, but I can't get around to doing so right now (and my username wouldn't be that accurate anymore

).
I haven't really dared upgrading the kernel, but do you think this tutorial is useful if I decide to do so? (https://hostadvice.com/how-to/how-to-up ... ux-kernel/) Or do you have any other recommendations?
And is my assumption correct that upgrading the kernel won't impact me in upgrading to LMDE5 once it's released, or do I have to look out for pitfalls?

Thank you all for your time and advice.

Oh, and

Code: Select all

dmesg --level=err -T
[Mi Sep 15 22:14:40 2021] hid-generic 0003:0D8C:0134.0001: No inputs registered, leaving

doesn't seem problematic to me, but what do I know

LMDE-Newbie · Post by **LMDE-Newbie** » Wed Sep 15, 2021 5:13 pm

LMDE-Newbie wrote: ⤴Wed Sep 15, 2021 4:36 pm I haven't really dared upgrading the kernel, but do you think this tutorial is useful if I decide to do so? (https://hostadvice.com/how-to/how-to-up ... ux-kernel/)

I just looked how the described steps would look like in LMDE, but I can't seem to find out how it works. Perhaps the tutorial is only works for Ubuntu/Ubuntu-derivates?
After more looking I found https://wiki.debian.org/HowToUpgradeKernel. The highest version apt-cache search linux-image lists is 5.10.0, though.

Code: Select all

apt-cache search linux-image
linux-image-686-pae - Linux für moderne PCs (Metapaket)
linux-image-rt-686-pae - Linux für moderne PCs (Metapaket), PREEMPT_RT
linux-image-amd64-signed-template - Template for signed linux-image packages for amd64
linux-image-i386-signed-template - Template for signed linux-image packages for i386
linux-image-686 - Linux for older PCs (meta-package)
linux-image-686-dbg - Debugging symbols for Linux 686 configuration (meta-package)
linux-image-686-pae-dbg - Debugging symbols for Linux 686-pae configuration (meta-package)
linux-image-amd64 - Linux for 64-bit PCs (meta-package)
linux-image-amd64-dbg - Debugging symbols for Linux amd64 configuration (meta-package)
linux-image-cloud-amd64 - Linux for x86-64 cloud (meta-package)
linux-image-cloud-amd64-dbg - Debugging symbols for Linux cloud-amd64 configuration (meta-package)
linux-image-rt-686-pae-dbg - Debugging symbols for Linux rt-686-pae configuration (meta-package)
linux-image-rt-amd64 - Linux for 64-bit PCs (meta-package), PREEMPT_RT
linux-image-rt-amd64-dbg - Debugging symbols for Linux rt-amd64 configuration (meta-package)
linux-headers-5.10.0-0.bpo.8-686 - Header files for Linux 5.10.0-0.bpo.8-686
linux-headers-5.10.0-0.bpo.8-686-pae - Header files for Linux 5.10.0-0.bpo.8-686-pae
linux-headers-5.10.0-0.bpo.8-amd64 - Header files for Linux 5.10.0-0.bpo.8-amd64
linux-headers-5.10.0-0.bpo.8-cloud-amd64 - Header files for Linux 5.10.0-0.bpo.8-cloud-amd64
linux-headers-5.10.0-0.bpo.8-rt-686-pae - Header files for Linux 5.10.0-0.bpo.8-rt-686-pae
linux-headers-5.10.0-0.bpo.8-rt-amd64 - Header files for Linux 5.10.0-0.bpo.8-rt-amd64
linux-image-5.10.0-0.bpo.8-686-dbg - Debug symbols for linux-image-5.10.0-0.bpo.8-686
linux-image-5.10.0-0.bpo.8-686-pae-dbg - Debug symbols for linux-image-5.10.0-0.bpo.8-686-pae
linux-image-5.10.0-0.bpo.8-686-pae-unsigned - Linux 5.10 for modern PCs
linux-image-5.10.0-0.bpo.8-686-unsigned - Linux 5.10 for older PCs
linux-image-5.10.0-0.bpo.8-amd64-dbg - Debug symbols for linux-image-5.10.0-0.bpo.8-amd64
linux-image-5.10.0-0.bpo.8-amd64-unsigned - Linux 5.10 for 64-bit PCs
linux-image-5.10.0-0.bpo.8-cloud-amd64-dbg - Debug symbols for linux-image-5.10.0-0.bpo.8-cloud-amd64
linux-image-5.10.0-0.bpo.8-cloud-amd64-unsigned - Linux 5.10 for x86-64 cloud
linux-image-5.10.0-0.bpo.8-rt-686-pae-dbg - Debug symbols for linux-image-5.10.0-0.bpo.8-rt-686-pae
linux-image-5.10.0-0.bpo.8-rt-686-pae-unsigned - Linux 5.10 for modern PCs, PREEMPT_RT
linux-image-5.10.0-0.bpo.8-rt-amd64-dbg - Debug symbols for linux-image-5.10.0-0.bpo.8-rt-amd64
linux-image-5.10.0-0.bpo.8-rt-amd64-unsigned - Linux 5.10 for 64-bit PCs, PREEMPT_RT
linux-image-5.10.0-0.bpo.3-amd64 - Linux 5.10 for 64-bit PCs (signed)
linux-image-5.10.0-0.bpo.3-cloud-amd64 - Linux 5.10 for x86-64 cloud (signed)
linux-image-5.10.0-0.bpo.3-rt-amd64 - Linux 5.10 for 64-bit PCs, PREEMPT_RT (signed)
linux-image-5.10.0-0.bpo.4-amd64 - Linux 5.10 for 64-bit PCs (signed)
linux-image-5.10.0-0.bpo.4-cloud-amd64 - Linux 5.10 for x86-64 cloud (signed)
linux-image-5.10.0-0.bpo.4-rt-amd64 - Linux 5.10 for 64-bit PCs, PREEMPT_RT (signed)
linux-image-5.10.0-0.bpo.5-amd64 - Linux 5.10 for 64-bit PCs (signed)
linux-image-5.10.0-0.bpo.5-cloud-amd64 - Linux 5.10 for x86-64 cloud (signed)
linux-image-5.10.0-0.bpo.5-rt-amd64 - Linux 5.10 for 64-bit PCs, PREEMPT_RT (signed)
linux-image-5.10.0-0.bpo.7-amd64 - Linux 5.10 for 64-bit PCs (signed)
linux-image-5.10.0-0.bpo.7-cloud-amd64 - Linux 5.10 for x86-64 cloud (signed)
linux-image-5.10.0-0.bpo.7-rt-amd64 - Linux 5.10 for 64-bit PCs, PREEMPT_RT (signed)
linux-image-5.10.0-0.bpo.8-amd64 - Linux 5.10 for 64-bit PCs (signed)
linux-image-5.10.0-0.bpo.8-cloud-amd64 - Linux 5.10 for x86-64 cloud (signed)
linux-image-5.10.0-0.bpo.8-rt-amd64 - Linux 5.10 for 64-bit PCs, PREEMPT_RT (signed)
linux-image-5.10.0-0.bpo.3-686 - Linux 5.10 for older PCs (signed)
linux-image-5.10.0-0.bpo.3-686-pae - Linux 5.10 for modern PCs (signed)
linux-image-5.10.0-0.bpo.3-rt-686-pae - Linux 5.10 for modern PCs, PREEMPT_RT (signed)
linux-image-5.10.0-0.bpo.4-686 - Linux 5.10 for older PCs (signed)
linux-image-5.10.0-0.bpo.4-686-pae - Linux 5.10 for modern PCs (signed)
linux-image-5.10.0-0.bpo.4-rt-686-pae - Linux 5.10 for modern PCs, PREEMPT_RT (signed)
linux-image-5.10.0-0.bpo.5-686 - Linux 5.10 for older PCs (signed)
linux-image-5.10.0-0.bpo.5-686-pae - Linux 5.10 for modern PCs (signed)
linux-image-5.10.0-0.bpo.5-rt-686-pae - Linux 5.10 for modern PCs, PREEMPT_RT (signed)
linux-image-5.10.0-0.bpo.7-686 - Linux 5.10 for older PCs (signed)
linux-image-5.10.0-0.bpo.7-686-pae - Linux 5.10 for modern PCs (signed)
linux-image-5.10.0-0.bpo.7-rt-686-pae - Linux 5.10 for modern PCs, PREEMPT_RT (signed)
linux-image-5.10.0-0.bpo.8-686 - Linux 5.10 for older PCs (signed)
linux-image-5.10.0-0.bpo.8-686-pae - Linux 5.10 for modern PCs (signed)
linux-image-5.10.0-0.bpo.8-rt-686-pae - Linux 5.10 for modern PCs, PREEMPT_RT (signed)

(I removed the 4.19 and 5.9 ones from the log to make it a bit shorter) Should I go for 5.10 (and which one?) or is it worth trying to get 5.11?

Post by **SMG** » Wed Sep 15, 2021 5:27 pm

LMDE-Newbie wrote: ⤴Wed Sep 15, 2021 5:13 pm(I removed the 4.19 and 5.9 ones from the log to make it a bit shorter) Should I go for 5.10 or is it worth trying to get 5.11?

For a 2nd-gen Ryzen, I would not think there is a significant difference between them. It's my understanding Bullseye is using the 5.10, so I think that would be the preferred option given you do not need specific hardware drivers available in the 5.11.

Aztaroth · Post by **Aztaroth** » Wed Sep 15, 2021 7:31 pm

Hi again,
A previous reply of mine has not been taken in account because the topic experienced an issue. I guess it's because I sent it while the topic has migrated in the more accurate LMDE section.
It was mostly an answer to SMG about her remark about /etc/fstab

SMG wrote: ⤴Wed Sep 15, 2021 3:20 pm I think the information you and Simon Peter have provided may be valuable to the OP, but the delay of 30 seconds happens even when booting into BIOS just to change the boot order. How is what is in fstab affect the time it takes BIOS to boot?

She was of course right. It's just that I overlooked the OP's concern of the firmware delay. I just quickly read the title and the systemd-analyze output and concluded the problem was mainly the time spent in userspace (1mn 38) and gave some advice to solve it. But I agree that even if it helped, it wasn't a proper answer to the OP, because it fixed userspace.

Now, I can join the effort to solve the firmware delay

.

What is this media-cab-Shared.mount ? I mean physically of course. I'm not inquiring about its content.
I had an issue like this with an external HDD when plugged before power on. Firmware delay increased dramatically because (my guess) BIOS was checking if there was a operating system on that disk to add to the boot sequence. And an external disk is not so fast than a HDD, not speaking of SSD.
Perhaps I could rephrase my query like this : is something (USB, external HDD or DVD...) plugged in before power on ?

About upgrading the kernel and LMDE4 :
- I'd first agree with SMG's staement : 5.10 or 5.11 would not make a big difference for your hardware.
- about LMDE5, I won't upgrade from LMDE4 to LMDE5, even if made possible by the developers. It will probably have a lot of major changes, so I'll install it from fresh, probably dual-boot with LMDE4 at the beginning or only on one of my computers to see what it looks like. But this is of course a personal choice. However it means that the kernel under which LMDE4 would be running at the time would be irrelevant for me.
- last thing about kernels. Depending on the hardware they may fit, solve problems or create new ones. I think about kernels like oysters : you can open up thousands but the day you find the one that has a pearl, keep it. For me it was 5.11.15, but I won't make it a rule for the world. However, having 5 computers running fine with it, a fresh beer will always be available for any developer of kernel 5.11.15

SimonPeter · Post by **SimonPeter** » Thu Sep 16, 2021 2:37 am

SMG wrote: ⤴Wed Sep 15, 2021 5:27 pm It's my understanding Bullseye is using the 5.10

Yes, I'm currently on Debian 11 Bullseye (with the default 5.10 kernel)
5.10 is LTS (supported for atleast 2 years) while 5.11 isn't.

LMDE-Newbie · Post by **LMDE-Newbie** » Thu Sep 16, 2021 4:09 am

SimonPeter wrote: ⤴Thu Sep 16, 2021 2:37 am Yes, I'm currently on Debian 11 Bullseye (with the default 5.10 kernel)
5.10 is LTS (supported for atleast 2 years) while 5.11 isn't.

OK, I guess I'll go for 5.10 then.

Aztaroth wrote: ⤴Wed Sep 15, 2021 7:31 pm What is this media-cab-Shared.mount ?

It's an internal SATA-SSD, it was my main drive before I bought the NVMe SSD. While I transitioned from Windows to LMDE, I started using it as a shared drive for both OSes (it's formatted with NTFS if that's of any concern).
Actually, Shared is only a partition on the SSD, as I have a second partition for Timeshift on that SSD.
Apart from that, I have a (basically always empty) (SATA) DVD drive, USB mouse, keyboard and microphone and a USB-Hub plugged in to the computer.
So I don't think there is anything BIOS could want to boot off of.

I'll definitely consider your point on not upgrading directly to LMDE5. At least this will finally make me separate home to a new partition

LMDE-Newbie · Post by **LMDE-Newbie** » Thu Sep 16, 2021 4:36 am

So, I just upgraded to kernel 5.10. So far, I didn't encounter any abnormalities.
As SMG already explained and expected, the amount of time spent before grub shows up did not decrease.
At least my PulseAudio issues seem to be somewhat resolved, but that's a different topic.

Thank you all for your help again. I'll still be watching this thread if you have any more ideas and be happy to provide more information if necessary.

Linux Mint Forums

System booting slowly

System booting slowly

Re: System booting slowly

Re: System booting slowly

Re: System booting slowly

Re: System booting slowly

Re: System booting slowly

Re: System booting slowly

Re: System booting slowly

Re: System booting slowly

Re: System booting slowly

Re: System booting slowly

Re: System booting slowly

Re: System booting slowly

Re: System booting slowly

Re: System booting slowly

Re: System booting slowly

Re: System booting slowly

Re: System booting slowly

Re: System booting slowly

Re: System booting slowly