My boot time is 2+ minutes

, then just select the uefi and click upgrade.

Aka select LENOVO system firmware, and you should see a button to upgrade. Under “releases available”

Then either you have newest UEFI, or linux firmware update (LVFS) does not support your version of motherboard.

So I cant do anything basically?

you can manually go check lenovo webpages and make sure you have latest UEFI firmware.

Other than that i am out of ideas.

But if I dont have the latest firmware I still cant do anything about it? Then why bother checking?

you can install it in other ways. Like using their boot medium, or windows

even linux has other ways to flash firmwares low-level if you have the firmware file from lenovo. But i highly recommend you don’t look into this method as just one wrong command can leave your motherboard bricked.

1 Like

Found this not sure if it is newer, because Im not sure which version im on.

gnome.firmware did not show that kind of version number, so either you need to look for it at during when you boot the computer, or when you enter UEFI settings at boot.

Alternatively just make a bootable media using that file, and try it. If you have latest it does nothing. If you don’t it will update.

1 Like

You appear to have encrypted your system.

Due to grub and luks2 decryption - boot is taking a long time when you are using full disk encryption.

There is nothing that is going to change that.

It is possible to migrate your system to use systemd boot instead - this will cut down on your loading time - but it requires a little work - and there is tradeoffs.

1 Like

How much faster would it be? How much time would you estimate it would take? And could any future problems arise from this?

let’s be real here, encryption does not make the boot take 2 minutes.

you can expect <5 second improvement by removing encryption. Changing to systemd instead of grub? Maybe 4 at best.

If you have 2 minute boot time, the issue is entirely somewhere else.

How are you measuring the two minutes? The logs don’t show this.

Idk its just the time from pressing the button to desktop showing, measured on my phone.

And where do you think the additional time is spent?
Before grub, after grub, during loading the system, login screen, or after logging in?

If you have a splash screen like plymouth, you can press ESC and see a bit more detailed what’s happening currently.

i suggest to backup all important data and do a clean new install.

15 seconds lenovo logo, 50 seconds one line on the screen /dev/sda… 57 seconds some logo appearing in the corner made by plasma KDE, 16 seconds desktop appears and then the icons appear finishes with a time 2:20

please make sure that your bios is up to date, things like secure boot are disabled and think about a clean install. whatever the problem might be it’s too vague to encounter with the informations you’re delivering. update the bios, disable things as secure-boot and make a clean install.

I don’t think the Thinkpad BIOS update brings better performance.

You use HDD RPM 5400

Can you show us if you use full encryption disk?

$ lsblk -f

Are there any error messages when booting?

$ journalctl -p err -b 0 --no-pager
NAME FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                         
├─sda1
│    ntfs         WINRE_DRV
│                       AE800CFD800CCDB1                                    
├─sda2
│    vfat   FAT32 SYSTEM_DRV
│                       8C0D-E4E6                             197,7M    23% /boot/efi
├─sda3
│                                                                           
├─sda4
│    ntfs         Windows8_OS
│                       D2BE0F9DBE0F796D                      101,5G    83% /run/media/admin_/Windows8_OS
├─sda5
│    ext4   1.0         01a339bf-1b65-42a9-adec-e0ab1d401eca  177,2G    39% /
└─sda6
     ntfs         Lenovo_Recovery
                        B6440AF1440AB3E1                                    
sr0    
dub 08 08:38:57 winzar-20df004nmc kernel: x86/cpu: VMX (outside TXT) disabled by BIOS
dub 08 08:38:57 winzar-20df004nmc kernel: ACPI Error: Needed type [Reference], found [Integer] (____ptrval____) (20220331/exresop-66)
dub 08 08:38:57 winzar-20df004nmc kernel: ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Store] (20220331/dswexec-431)
dub 08 08:38:57 winzar-20df004nmc kernel: ACPI Error: Aborting method \_PR.CPU0._PDC due to previous error (AE_AML_OPERAND_TYPE) (20220331/psparse-529)
dub 08 08:39:00 winzar-20df004nmc kernel: ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [TBF3] at bit offset/length 262144/32768 exceeds size of target Buffer (262144 bits) (20220331/dsopcode-198)
dub 08 08:39:00 winzar-20df004nmc kernel: ACPI Error: Aborting method \_SB.PCI0.VID.GETB due to previous error (AE_AML_BUFFER_LIMIT) (20220331/psparse-529)
dub 08 08:39:00 winzar-20df004nmc kernel: ACPI Error: Aborting method \_SB.PCI0.VID.ATRM due to previous error (AE_AML_BUFFER_LIMIT) (20220331/psparse-529)
dub 08 08:39:07 winzar-20df004nmc bluetoothd[682]: src/plugin.c:plugin_init() Failed to init vcp plugin
dub 08 08:39:07 winzar-20df004nmc bluetoothd[682]: src/plugin.c:plugin_init() Failed to init mcp plugin
dub 08 08:39:07 winzar-20df004nmc bluetoothd[682]: src/plugin.c:plugin_init() Failed to init bap plugin
dub 08 08:39:09 winzar-20df004nmc kernel: debugfs: File 'radeon_ring_gfx' in directory '0' already present!
dub 08 08:39:09 winzar-20df004nmc kernel: debugfs: File 'radeon_ring_cp1' in directory '0' already present!
dub 08 08:39:09 winzar-20df004nmc kernel: debugfs: File 'radeon_ring_cp2' in directory '0' already present!
dub 08 08:39:09 winzar-20df004nmc kernel: debugfs: File 'radeon_ring_dma1' in directory '0' already present!
dub 08 08:39:09 winzar-20df004nmc kernel: debugfs: File 'radeon_ring_dma2' in directory '0' already present!
dub 08 08:39:09 winzar-20df004nmc kernel: debugfs: File 'radeon_ring_uvd' in directory '0' already present!
dub 08 08:39:19 winzar-20df004nmc systemd[1]: Failed to start pkgfile database update.
dub 08 08:39:43 winzar-20df004nmc systemd[903]: Failed to start Powerdevil.
dub 08 08:39:49 winzar-20df004nmc systemd[903]: Failed to start Powerdevil.
dub 08 08:39:52 winzar-20df004nmc kernel: ntfs3: Unknown parameter 'windows_names'
dub 08 08:40:19 winzar-20df004nmc bluetoothd[682]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
dub 08 09:49:31 winzar-20df004nmc konsole[2161]: kf.xmlgui: Shortcut for action  "" "Show SSH Manager" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
dub 08 09:49:31 winzar-20df004nmc konsole[2161]: kf.xmlgui: Shortcut for action  "" "Show Quick Commands" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.