Startup finished in 4.632s (firmware) + 7.612s (loader) + 437ms (kernel) + 12.812s (initrd) + 3min 9.028s (userspace) = 3min 34.523s
graphical.target reached after 2min 19.323s in userspace.
First, no garuda-inxi (why?)
Maybe a solution (WAIT for others suggestions too) is changing kernels can help. Try changing to linux-cachyos-bore or linux-xanmod.
Edit your post with inxi (or no one is likely to help and also the thread will be moved)
7 Likes
Hmm did someone suggest kernel. 
Lately Norbert (someone I know on telegram) found nitrous kernel it’s really good too. 
sudo pacman -S linux-nitrous-headers linux-nitrous
Choose it from grub → advanced settings and see if you like it? If it’s something you like and would like to be default go to garuda boot options and do the needful.
Btw, look at
systemd-analyze blame
And
systemd-analyze critical-chain
To take a look at what’s taking up so much time and disable it as per your discretion (be careful here !!)
don’t be lazyfollow template provide garuda-inxi
7 Likes
here’s garuda-inxi
System:
Kernel: 6.7.2-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc available: acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=6dfa7961-f821-48b4-aaa1-22588228c2be rw rootflags=subvol=@
loglevel=3 splash sysrq_always_enabled=1
systemd.unified_cgroup_hierarchy=1 ibt=off
Desktop: KDE Plasma v: 5.27.10 tk: Qt v: 5.15.12 wm: kwin_wayland vt: 1
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Laptop System: LENOVO product: 82H8 v: IdeaPad 3 15ITL6
serial: <superuser required> Chassis: type: 10 v: IdeaPad 3 15ITL6
serial: <superuser required>
Mobo: LENOVO model: LNVNB161216 v: NO DPK serial: <superuser required>
UEFI: LENOVO v: GGCN32WW date: 01/15/2022
Battery:
ID-1: BAT0 charge: 15.8 Wh (48.9%) condition: 32.3/38.0 Wh (84.9%)
power: 23.8 W volts: 8.3 min: 7.7 model: Celxpert L20C2PF0 type: Li-poly
serial: <filter> status: charging cycles: 338
CPU:
Info: model: 11th Gen Intel Core i5-1135G7 bits: 64 type: MT MCP
arch: Tiger Lake gen: core 11 level: v4 note: check built: 2020
process: Intel 10nm family: 6 model-id: 0x8C (140) stepping: 1
microcode: 0xB4
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
L1: 320 KiB desc: d-4x48 KiB; i-4x32 KiB L2: 5 MiB desc: 4x1.2 MiB L3: 8 MiB
desc: 1x8 MiB
Speed (MHz): avg: 528 high: 1046 min/max: 400/4200 scaling:
driver: intel_pstate governor: powersave cores: 1: 400 2: 400 3: 400 4: 400
5: 400 6: 784 7: 400 8: 1046 bogomips: 38707
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] vendor: Lenovo
driver: i915 v: kernel arch: Gen-12.1 process: Intel 10nm built: 2020-21
ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 0000:00:02.0
chip-ID: 8086:9a49 class-ID: 0300
Device-2: Bison Integrated Camera driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-5:2 chip-ID: 5986:2137
class-ID: 0e02
Display: wayland server: X.org v: 1.21.1.11 with: Xwayland v: 23.2.4
compositor: kwin_wayland driver: X: loaded: modesetting
alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: 0
Monitor-1: eDP-1 res: 1920x1080 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
device: 1 drv: swrast surfaceless: drv: iris wayland: drv: iris x11:
drv: iris inactive: gbm
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 23.3.4-arch1.2
glx-v: 1.4 direct-render: yes renderer: Mesa Intel Xe Graphics (TGL GT2)
device-ID: 8086:9a49 memory: 7.38 GiB unified: yes display-ID: :1.0
API: Vulkan v: 1.3.276 layers: 8 device: 0 type: integrated-gpu name: Intel
Xe Graphics (TGL GT2) driver: mesa intel v: 23.3.4-arch1.2
device-ID: 8086:9a49 surfaces: xcb,xlib,wayland device: 1 type: cpu
name: llvmpipe (LLVM 16.0.6 256 bits) driver: mesa llvmpipe
v: 23.3.4-arch1.2 (LLVM 16.0.6) device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Audio:
Device-1: Intel Tiger Lake-LP Smart Sound Audio vendor: Lenovo
driver: sof-audio-pci-intel-tgl
alternate: snd_hda_intel,snd_sof_pci_intel_tgl bus-ID: 0000:00:1f.3
chip-ID: 8086:a0c8 class-ID: 0401
API: ALSA v: k6.7.2-zen1-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.0.1 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 Wi-Fi 6 AX201 driver: iwlwifi v: kernel bus-ID: 0000:00:14.3
chip-ID: 8086:a0f0 class-ID: 0280
IF: wlp0s20f3 state: up mac: <filter>
Bluetooth:
Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) driver: btusb
v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-10:3
chip-ID: 8087:0aaa class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 2 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: <filter> bt-v: 5.1 lmp-v: 10
status: discoverable: no pairing: no
RAID:
Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd
v: 0.6 port: N/A bus-ID: 0000:00:0e.0 chip-ID: 8086:9a0b rev: class-ID: 0104
Drives:
Local Storage: total: 931.51 GiB used: 824.3 GiB (88.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: MQ04ABF100
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5400 serial: <filter> fw-rev: 2E scheme: GPT
Partition:
ID-1: / raw-size: 921.45 GiB size: 921.45 GiB (100.00%)
used: 824.3 GiB (89.5%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 921.45 GiB size: 921.45 GiB (100.00%)
used: 824.3 GiB (89.5%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 921.45 GiB size: 921.45 GiB (100.00%)
used: 824.3 GiB (89.5%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 921.45 GiB size: 921.45 GiB (100.00%)
used: 824.3 GiB (89.5%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: partition size: 9.77 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/sda3 maj-min: 8:3
ID-2: swap-2 type: zram size: 7.56 GiB used: 1.12 GiB (14.8%)
priority: 100 comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 8
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 43.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Processes: 338 Uptime: 4h 48m wakeups: 1 Memory: total: 8 GiB
available: 7.56 GiB used: 4.58 GiB (60.6%) Init: systemd v: 255
default: graphical tool: systemctl Compilers: gcc: 13.2.1 Packages: 4100
pm: dpkg pkgs: 1 tools: apt,apt-get,gnome-software pm: pacman pkgs: 2034
libs: 546 tools: octopi,pamac,paru,yay pm: rpm pkgs: N/A note: see --rpm
tools: dnf pm: snap pkgs: 31 Shell: fish v: 3.7.0 running-in: konsole
inxi: 3.3.31
Garuda (2.6.22-1):
System install date: 2023-11-21
Last full system update: 2024-02-08
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut
Windows dual boot: No/Undetected
Failed units: nmb.service
What should I disable?
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @2min 19.323s
└─multi-user.target @2min 19.323s
└─smb.service @2min 18.406s +916ms
└─network-online.target @48.195s
└─NetworkManager-wait-online.service @43.955s +4.238s
└─NetworkManager.service @40.759s +3.184s
└─network-pre.target @40.746s
└─firewalld.service @33.495s +7.251s
└─polkit.service @25.065s +8.416s
└─basic.target @25.049s
└─dbus-broker.service @24.329s +717ms
└─dbus.socket @24.280s
└─sysinit.target @23.785s
└─systemd-timesyncd.service @23.610s +174ms
└─systemd-tmpfiles-setup.service @21.742s +1.858s
└─systemd-journal-flush.service @15.271s +6.456s
└─var-log.mount @14.946s +314ms
└─dev-sda2.device @584542y 2w 2d 20h 1min 38.131s +26.355s
The first thing I’d try is to change this, also because it’s for NVMe but you have
(which is slower, but shouldn’t be that much slow).
Change in your BIOS the SATA controller from vmd to AHCI (or something like that).
3 Likes
Have you fixed this yet?
6 Likes
the garuda-inxi indicates that your cpu is only hitting 1046mhz. try doing something heavy(play a game, there are plenty of free games available through pacman/pamac/octopi/etc… or run a heavy application like blender or something you use for work) and then run garuda-inxi(and post here) again. if your cpu isn’t turboing up to what it says it can(4200mhz according to your garuda-inxi) the problem may lay elsewhere.
3 Likes
No 
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.