I’ve recently installed Endevouros Kde Plasma so is there something can i do to reduce the wait time
saibot@SpiKenDouh ~]$ systemd-analyze
Startup finished in 21.242s (firmware) + 33.605s (loader) + 3.724s (kernel) + 21.106s (userspace) = 1min 19.679s
graphical.target reached after 21.106s in userspace
[saibot@SpiKenDouh ~]$ inxi --full --verbosity=7 --filter --no-host
System:
Kernel: 5.10.88-2-lts x86_64 bits: 64 compiler: gcc v: 11.1.0
Desktop: KDE Plasma 5.23.4 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11
vt: 1 dm: SDDM Distro: EndeavourOS base: Arch Linux
Machine:
Type: Desktop Mobo: ASRock model: Z370 Gaming K6
serial: <superuser required> UEFI: American Megatrends v: P1.20
date: 10/26/2017
Battery:
Message: No system battery data found. Is one present?
Memory:
RAM: total: 15.55 GiB used: 4.68 GiB (30.1%)
RAM Report:
permissions: Unable to run dmidecode. Root privileges required.
CPU:
Info: 6-core model: Intel Core i7-8700K bits: 64 type: MT MCP smt: enabled
arch: Coffee Lake rev: A cache: L1: 384 KiB L2: 1.5 MiB L3: 12 MiB
Speed (MHz): avg: 1207 high: 3375 min/max: 800/4700 cores: 1: 807 2: 813
3: 801 4: 982 5: 829 6: 1141 7: 1309 8: 844 9: 3375 10: 998 11: 1167
12: 1419 bogomips: 88796
Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat arch_perfmon
art avx avx2 bmi1 bmi2 bts clflush clflushopt cmov constant_tsc cpuid
cpuid_fault cx16 cx8 de ds_cpl dtes64 dtherm dts epb ept ept_ad erms est
f16c flexpriority flush_l1d fma fpu fsgsbase fxsr hle ht hwp
hwp_act_window hwp_epp hwp_notify ibpb ibrs ida intel_pt invpcid
invpcid_single lahf_lm lm mca mce md_clear mmx monitor movbe mpx msr mtrr
nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge pln
pni popcnt pse pse36 pti pts rdrand rdseed rdtscp rep_good rtm sdbg sep
smap smep smx ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2
tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx vnmi vpid x2apic
xgetbv1 xsave xsavec xsaveopt xsaves xtopology xtpr
Graphics:
Device-1: NVIDIA GP104 [GeForce GTX 1080] vendor: Micro-Star MSI
driver: nvidia v: 495.46 bus-ID: 01:00.0 chip-ID: 10de:1b80 class-ID: 0300
Display: x11 server: X.Org 1.21.1.2 compositor: kwin_x11 driver:
loaded: nvidia unloaded: modesetting alternate: fbdev,nouveau,nv,vesa
resolution: 1920x1080~60Hz s-dpi: 81
OpenGL: renderer: NVIDIA GeForce GTX 1080/PCIe/SSE2
v: 4.6.0 NVIDIA 495.46 direct render: Yes
Audio:
Device-1: Intel 200 Series PCH HD Audio vendor: ASRock
driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a2f0
class-ID: 0403
Device-2: NVIDIA GP104 High Definition Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel bus-ID: 01:00.1 chip-ID: 10de:10f0
class-ID: 0403
Device-3: Creative Sound BlasterX H7 type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-1:2 chip-ID: 041e:3242
class-ID: 0300 serial: <filter>
Sound Server-1: ALSA v: k5.10.88-2-lts running: yes
Sound Server-2: JACK v: 1.9.19 running: no
Sound Server-3: PulseAudio v: 15.0 running: no
Sound Server-4: PipeWire v: 0.3.42 running: yes
Network:
Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
IF: enp0s31f6 state: down mac: <filter>
Device-2: Intel I211 Gigabit Network vendor: ASRock driver: igb v: kernel
port: c000 bus-ID: 05:00.0 chip-ID: 8086:1539 class-ID: 0200
IF: enp5s0 state: up speed: 100 Mbps duplex: full mac: <filter>
IP v4: <filter> type: dynamic noprefixroute scope: global
broadcast: <filter>
IP v6: <filter> type: noprefixroute scope: link
WAN IP: <filter>
Bluetooth:
Message: No bluetooth data found.
Logical:
Message: No logical block device data found.
RAID:
Message: No RAID data found.
Drives:
Local Storage: total: 1.38 TiB used: 13.13 GiB (0.9%)
ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB512HAJQ-000H1
size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: EXA72H1Q temp: 39.9 C scheme: GPT
ID-2: /dev/sda vendor: Western Digital model: WD10EZRZ-00HTKB0
size: 931.51 GiB speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
rev: 1A01 scheme: MBR
Message: No optical or floppy data found.
Partition:
ID-1: / size: 271.79 GiB used: 13.13 GiB (4.8%) fs: ext4 dev: /dev/sda4
label: N/A uuid: 6be0fa0e-68a9-44a8-8ebc-5e08f0d82390
ID-2: /boot/efi size: 499 MiB used: 308 KiB (0.1%) fs: vfat
dev: /dev/sda2 label: NO_LABEL uuid: C108-B007
Swap:
ID-1: swap-1 type: partition size: 16 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/sda3 label: N/A uuid: 2a94d231-78c8-469c-a145-ed2a901ce465
Unmounted:
ID-1: /dev/nvme0n1p1 size: 100 MiB fs: vfat label: N/A uuid: 1A2A-5125
ID-2: /dev/nvme0n1p2 size: 16 MiB fs: <superuser required> label: N/A
uuid: N/A
ID-3: /dev/nvme0n1p3 size: 476.23 GiB fs: ntfs label: N/A
uuid: 6E3C47583C471B0B
ID-4: /dev/nvme0n1p4 size: 604 MiB fs: ntfs label: N/A
uuid: 0492EC7892EC701A
ID-5: /dev/sda1 size: 637.81 GiB fs: ntfs label: Karim
uuid: 9C700C9E700C816E
USB:
Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 16 rev: 2.0
speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
Device-1: 1-1:2 info: Creative Sound BlasterX H7 type: Audio,HID
driver: hid-generic,snd-usb-audio,usbhid interfaces: 4 rev: 2.0
speed: 12 Mb/s power: 100mA chip-ID: 041e:3242 class-ID: 0300
serial: <filter>
Hub-2: 1-3:3 info: ASMedia ASM1074 High-Speed hub ports: 4 rev: 2.1
speed: 480 Mb/s power: 100mA chip-ID: 174c:2074 class-ID: 0900
Device-1: 1-9:4 info: Corsair K95 RGB Platinum Keyboard [RGP0056]
type: Keyboard,HID driver: hid-generic,usbhid interfaces: 2 rev: 2.0
speed: 12 Mb/s power: 500mA chip-ID: 1b1c:1b2d class-ID: 0300
serial: <filter>
Device-2: 1-11:5 info: Cooler Master ARGB LED Controller
type: HID,Keyboard driver: hid-generic,usbhid interfaces: 2 rev: 2.0
speed: 12 Mb/s power: 100mA chip-ID: 2516:1011 class-ID: 0300
serial: <filter>
Hub-3: 2-0:1 info: Super-speed hub ports: 10 rev: 3.0 speed: 5 Gb/s
chip-ID: 1d6b:0003 class-ID: 0900
Hub-4: 2-7:2 info: ASMedia ASM1074 SuperSpeed hub ports: 4 rev: 3.0
speed: 5 Gb/s power: 8mA chip-ID: 174c:3074 class-ID: 0900
Hub-5: 3-0:1 info: Hi-speed hub with single TT ports: 2 rev: 2.0
speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
Device-1: 3-2:2 info: ASUSTek ROG Gladius II Origin type: Mouse,HID
driver: hid-generic,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s
power: 98mA chip-ID: 0b05:1877 class-ID: 0300
Hub-6: 4-0:1 info: Super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s
chip-ID: 1d6b:0003 class-ID: 0900
Sensors:
System Temperatures: cpu: 32.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 283 Uptime: 3h 20m wakeups: 0 Init: systemd v: 250 Compilers:
gcc: 11.1.0 Packages: 1018 pacman: 1010 snap: 8 Shell: Bash v: 5.1.12
running-in: konsole inxi: 3.3.11
Please us code tags before and after what you post from the terminal. It makes it much easier to read.
2 Likes
KDen
December 31, 2021, 4:19pm
3
You can use can use journalctl, dmesg, and systemd-analyze to help diagnose boot lag. These logs can help narrow down what might be taking up time
To find out what services are taking the longest:systemd-analyze blamesystemd-analyze timejournalctl -bsudo dmesg -H
2 Likes
Actually i don’t know what to do next
KDen
December 31, 2021, 6:41pm
5
Well, you have to use your logs and check their time markings to find out what process is taking a long time to boot. Looking at your first post all I can tell you is that your loader is taking 33 seconds and your userspace is taking 21 seconds. Your firmware and kernel times look pretty normal to me.
You didn’t provide any logs or sections of logs with services that include time markings. So we can only speculate.
Check this wiki page:https://wiki.archlinux.org/title/Improving_performance/Boot_process
I imagine you’re using grub as your loader. So for that you could post your grub config or try rEFIndhttps://wiki.archlinux.org/title/REFInd
For your userspace; again you need to look through your systemd-analyze, journalctl, and dmesg. Look at the time marks and see where you have large jumps or gaps in time. Creating an svg plot with systemd-analyze can help as well. Check the Wiki page I linked to see how to do that.
1 Like
Did you install EOS in UEFI Mode? As it looks like it’s on the same disk sda which is MBR?
ID-1: / size: 271.79 GiB used: 13.13 GiB (4.8%) fs: ext4 dev: /dev/sda4
label: N/A uuid: 6be0fa0e-68a9-44a8-8ebc-5e08f0d82390
ID-2: /boot/efi size: 499 MiB used: 308 KiB (0.1%) fs: vfat
dev: /dev/sda2 label: NO_LABEL uuid: C108-B007
Swap:
ID-1: swap-1 type: partition size: 16 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/sda3 label: N/A uuid: 2a94d231-78c8-469c-a145-ed2a901ce465
Unmounted:
1 Like
Yes i install EOS in uefi mode !
ID-2: /dev/sda vendor: Western Digital model: WD10EZRZ-00HTKB0
size: 931.51 GiB speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
rev: 1A01 scheme: MBR
Message: No optical or floppy data found.
Partition:
ID-1: / size: 271.79 GiB used: 13.23 GiB (4.9%) fs: ext4 dev: /dev/sda4
label: N/A uuid: 6be0fa0e-68a9-44a8-8ebc-5e08f0d82390
ID-2: /boot/efi size: 499 MiB used: 308 KiB (0.1%) fs: vfat
dev: /dev/sda2 label: NO_LABEL uuid: C108-B007
Swap:
ID-1: swap-1 type: partition size: 16 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/sda3 label: N/A uuid: 2a94d231-78c8-469c-a145-ed2a901ce465
Unmounted:
systemd-analyze blame
6.691s snapd.service
5.761s power-profiles-daemon.service
5.390s dev-sda4.device
3.931s systemd-modules-load.service
3.801s polkit.service
3.037s systemd-journal-flush.service
2.743s systemd-random-seed.service
2.741s ldconfig.service
2.553s dev-loop6.device
2.224s dev-loop4.device
2.197s dev-loop5.device
2.149s dev-loop1.device
2.123s dev-loop0.device
2.059s dev-loop2.device
1.864s avahi-daemon.service
1.863s NetworkManager.service
1.743s systemd-sysusers.service
1.719s systemd-logind.service
1.692s dev-loop3.device
1.528s systemd-tmpfiles-setup-dev.service
1.401s var-lib-snapd-snap-snapd-14295.mount
1.301s var-lib-snapd-snap-chromium-1854.mount
1.301s var-lib-snapd-snap-core18-2253.mount
1.286s var-lib-snapd-snap-gnome\x2d3\x2d28\x2d1804-161.mount
1.017s systemd-tmpfiles-setup.service
961ms systemd-journal-catalog-update.service
934ms var-lib-snapd-snap-bare-5.mount
911ms var-lib-snapd-snap-discord-131.mount
907ms var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1519.mount
894ms udisks2.service
806ms systemd-fsck@dev-disk-by\x2duuid-C108\x2dB007.service
743ms systemd-udevd.service
680ms lvm2-monitor.service
592ms user@1000.service
582ms wpa_supplicant.service
388ms modprobe@drm.service
314ms systemd-udev-trigger.service
271ms boot-efi.mount
251ms systemd-timesyncd.service
232ms pamac-daemon.service
227ms dev-disk-by\x2duuid-2a94d231\x2d78c8\x2d469c\x2da145\x2ded2a901ce465.swap
221ms upower.service
205ms modprobe@fuse.service
197ms systemd-journald.service
158ms rtkit-daemon.service
145ms alsa-restore.service
135ms dev-hugepages.mount
133ms dev-mqueue.mount
131ms sys-kernel-debug.mount
129ms sys-kernel-tracing.mount
128ms tmp.mount
127ms kmod-static-nodes.service
123ms modprobe@configfs.service
67ms systemd-sysctl.service
57ms systemd-update-utmp.service
53ms systemd-remount-fs.service
53ms systemd-update-done.service
48ms systemd-user-sessions.service
6ms user-runtime-dir@1000.service
5ms sys-kernel-config.mount
1ms sys-fs-fuse-connections.mount
419us snapd.socket
lines 7-62/62 (END)
$ systemd-analyze time
Startup finished in 13.481s (firmware) + 2.709s (loader) + 3.913s (kernel) + 20.550s (userspace) = 40.655s
graphical.target reached after 20.550s in userspace
$ sudo dmesg -H
[sudo] password for saibot:
[Jan 1 18:19] microcode: microcode updated early to revision 0xea, date = 2021-01-05
[ +0.000000] Linux version 5.10.88-2-lts (linux-lts@archlinux) (gcc (GCC) 11.1.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP Wed, 22 Dec 2021 19:16:31 +0000
[ +0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-linux-lts root=UUID=6be0fa0e-68a9-44a8-8ebc-5e08f0d82390 rw quiet resume=UUID=2a94d231-78c8-469c-a145-ed2a901ce465 loglevel=3 nowatchdog nvme_load=YES nvidia-drm.modeset=1
[ +0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[ +0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[ +0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[ +0.000000] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
[ +0.000000] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[ +0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
[ +0.000000] x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64
[ +0.000000] x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64
[ +0.000000] x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
[ +0.000000] BIOS-provided physical RAM map:
[ +0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
[ +0.000000] BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
[ +0.000000] BIOS-e820: [mem 0x0000000000059000-0x000000000009efff] usable
[ +0.000000] BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
[ +0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000083701fff] usable
[ +0.000000] BIOS-e820: [mem 0x0000000083702000-0x0000000083702fff] ACPI NVS
[ +0.000000] BIOS-e820: [mem 0x0000000083703000-0x0000000083703fff] reserved
[ +0.000000] BIOS-e820: [mem 0x0000000083704000-0x000000008bbc5fff] usable
[ +0.000000] BIOS-e820: [mem 0x000000008bbc6000-0x000000008e7e4fff] reserved
[ +0.000000] BIOS-e820: [mem 0x000000008e7e5000-0x000000008e898fff] usable
[ +0.000000] BIOS-e820: [mem 0x000000008e899000-0x000000008ec66fff] ACPI NVS
[ +0.000000] BIOS-e820: [mem 0x000000008ec67000-0x000000008f70cfff] reserved
[ +0.000000] BIOS-e820: [mem 0x000000008f70d000-0x000000008f7fdfff] type 20
[ +0.000000] BIOS-e820: [mem 0x000000008f7fe000-0x000000008f7fefff] usable
[ +0.000000] BIOS-e820: [mem 0x000000008f7ff000-0x000000008fffffff] reserved
[ +0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
[ +0.000000] BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
[ +0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ +0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
[ +0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[ +0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[ +0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000046effffff] usable
[ +0.000000] NX (Execute Disable) protection: active
[ +0.000000] efi: EFI v2.60 by American Megatrends
[ +0.000000] efi: TPMFinalLog=0x8ec37000 ACPI 2.0=0x8e899000 ACPI=0x8e899000 SMBIOS=0x8f67e000 SMBIOS 3.0=0x8f67d000 ESRT=0x8a46ee18 MEMATTR=0x8866d018
[ +0.000000] SMBIOS 3.0.0 present.
[ +0.000000] DMI: To Be Filled By O.E.M. To Be Filled By O.E.M./Z370 Gaming K6, BIOS P1.20 10/26/2017
[ +0.000000] tsc: Detected 3700.000 MHz processor
[ +0.000000] tsc: Detected 3699.850 MHz TSC
[ +0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[ +0.000002] e820: remove [mem 0x000a0000-0x000fffff] usable
[ +0.000005] last_pfn = 0x46f000 max_arch_pfn = 0x400000000
[ +0.000003] MTRR default type: write-back
[ +0.000001] MTRR fixed ranges enabled:
[ +0.000001] 00000-9FFFF write-back
[ +0.000000] A0000-BFFFF uncachable
[ +0.000001] C0000-FFFFF write-protect
[ +0.000001] MTRR variable ranges enabled:
[ +0.000001] 0 base 00C0000000 mask 7FC0000000 uncachable
[ +0.000000] 1 base 00A0000000 mask 7FE0000000 uncachable
[ +0.000001] 2 base 0090000000 mask 7FF0000000 uncachable
[ +0.000000] 3 disabled
[ +0.000001] 4 disabled
$ journalctl -b
Jan 01 18:19:08 SpiKenDouh kernel: microcode: microcode updated early to revision 0xea, date = 2021-01-05
Jan 01 18:19:08 SpiKenDouh kernel: Linux version 5.10.88-2-lts (linux-lts@archlinux) (gcc (GCC) 11.1.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP Wed, 22 Dec 2021 19:16:31 +0000
Jan 01 18:19:08 SpiKenDouh kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux-lts root=UUID=6be0fa0e-68a9-44a8-8ebc-5e08f0d82390 rw quiet resume=UUID=2a94d231-78c8-469c-a145-ed2a901ce465 loglevel=3 nowatchdog nvme_load=YES nvidia-drm>
Jan 01 18:19:08 SpiKenDouh kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Jan 01 18:19:08 SpiKenDouh kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Jan 01 18:19:08 SpiKenDouh kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Jan 01 18:19:08 SpiKenDouh kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
Jan 01 18:19:08 SpiKenDouh kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
Jan 01 18:19:08 SpiKenDouh kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Jan 01 18:19:08 SpiKenDouh kernel: x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64
Jan 01 18:19:08 SpiKenDouh kernel: x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64
Jan 01 18:19:08 SpiKenDouh kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
Jan 01 18:19:08 SpiKenDouh kernel: BIOS-provided physical RAM map:
Jan 01 18:19:08 SpiKenDouh kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
Jan 01 18:19:08 SpiKenDouh kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
Jan 01 18:19:08 SpiKenDouh kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009efff] usable
Jan 01 18:19:08 SpiKenDouh kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
Jan 01 18:19:08 SpiKenDouh kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000083701fff] usable
Jan 01 18:19:08 SpiKenDouh kernel: BIOS-e820: [mem 0x0000000083702000-0x0000000083702fff] ACPI NVS
Jan 01 18:19:08 SpiKenDouh kernel: BIOS-e820: [mem 0x0000000083703000-0x0000000083703fff] reserved
Jan 01 18:19:08 SpiKenDouh kernel: BIOS-e820: [mem 0x0000000083704000-0x000000008bbc5fff] usable
Jan 01 18:19:08 SpiKenDouh kernel: BIOS-e820: [mem 0x000000008bbc6000-0x000000008e7e4fff] reserved
Jan 01 18:19:08 SpiKenDouh kernel: BIOS-e820: [mem 0x000000008e7e5000-0x000000008e898fff] usable
Jan 01 18:19:08 SpiKenDouh kernel: BIOS-e820: [mem 0x000000008e899000-0x000000008ec66fff] ACPI NVS
Jan 01 18:19:08 SpiKenDouh kernel: BIOS-e820: [mem 0x000000008ec67000-0x000000008f70cfff] reserved
Jan 01 18:19:08 SpiKenDouh kernel: BIOS-e820: [mem 0x000000008f70d000-0x000000008f7fdfff] type 20
Jan 01 18:19:08 SpiKenDouh kernel: BIOS-e820: [mem 0x000000008f7fe000-0x000000008f7fefff] usable
Jan 01 18:19:08 SpiKenDouh kernel: BIOS-e820: [mem 0x000000008f7ff000-0x000000008fffffff] reserved
Jan 01 18:19:08 SpiKenDouh kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Jan 01 18:19:08 SpiKenDouh kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Jan 01 18:19:08 SpiKenDouh kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Jan 01 18:19:08 SpiKenDouh kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Jan 01 18:19:08 SpiKenDouh kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Jan 01 18:19:08 SpiKenDouh kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jan 01 18:19:08 SpiKenDouh kernel: BIOS-e820: [mem 0x0000000100000000-0x000000046effffff] usable
Jan 01 18:19:08 SpiKenDouh kernel: NX (Execute Disable) protection: active
Jan 01 18:19:08 SpiKenDouh kernel: efi: EFI v2.60 by American Megatrends
Jan 01 18:19:08 SpiKenDouh kernel: efi: TPMFinalLog=0x8ec37000 ACPI 2.0=0x8e899000 ACPI=0x8e899000 SMBIOS=0x8f67e000 SMBIOS 3.0=0x8f67d000 ESRT=0x8a46ee18 MEMATTR=0x8866d018
Jan 01 18:19:08 SpiKenDouh kernel: SMBIOS 3.0.0 present.
Jan 01 18:19:08 SpiKenDouh kernel: DMI: To Be Filled By O.E.M. To Be Filled By O.E.M./Z370 Gaming K6, BIOS P1.20 10/26/2017
Jan 01 18:19:08 SpiKenDouh kernel: tsc: Detected 3700.000 MHz processor
Jan 01 18:19:08 SpiKenDouh kernel: tsc: Detected 3699.850 MHz TSC
Jan 01 18:19:08 SpiKenDouh kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jan 01 18:19:08 SpiKenDouh kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Jan 01 18:19:08 SpiKenDouh kernel: last_pfn = 0x46f000 max_arch_pfn = 0x400000000
Jan 01 18:19:08 SpiKenDouh kernel: MTRR default type: write-back
Jan 01 18:19:08 SpiKenDouh kernel: MTRR fixed ranges enabled:
Jan 01 18:19:08 SpiKenDouh kernel: 00000-9FFFF write-back
Jan 01 18:19:08 SpiKenDouh kernel: A0000-BFFFF uncachable
Jan 01 18:19:08 SpiKenDouh kernel: C0000-FFFFF write-protect
Jan 01 18:19:08 SpiKenDouh kernel: MTRR variable ranges enabled:
Jan 01 18:19:08 SpiKenDouh kernel: 0 base 00C0000000 mask 7FC0000000 uncachable
Jan 01 18:19:08 SpiKenDouh kernel: 1 base 00A0000000 mask 7FE0000000 uncachable
Jan 01 18:19:08 SpiKenDouh kernel: 2 base 0090000000 mask 7FF0000000 uncachable
Jan 01 18:19:08 SpiKenDouh kernel: 3 disabled
Jan 01 18:19:08 SpiKenDouh kernel: 4 disabled
lines 1-56
KouKouMani:
rev: 1A01 scheme: MBR
This disk shows MBR and not GPT. Is there a reason you are using MBR instead of installing UEFI using a GPT partition scheme on the disk?
1 Like
No there is no reason i just following installation steps
pebcak
January 1, 2022, 7:15pm
11
I would think the time you’re getting is pretty normal considering the speed of the harddisk but I might be wrong.
@KouKouMani systemd-analyze critical-chain
1 Like
$ systemd-analyze critical-chain
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 @20.550s
└─multi-user.target @20.550s
└─snapd.service @13.857s +6.691s
└─basic.target @13.716s
└─sockets.target @13.716s
└─snapd.socket @13.715s +419us
└─sysinit.target @13.700s
└─systemd-update-done.service @13.646s +53ms
└─ldconfig.service @10.901s +2.741s
└─local-fs.target @10.899s
└─boot-efi.mount @10.626s +271ms
└─systemd-fsck@dev-disk-by\x2duuid-C108\x2dB007.service @9.764s +806ms
└─dev-disk-by\x2duuid-C108\x2dB007.device @9.764s
I use KDE and have no issues. I think part of your issue is related to use of snaps and having snapd installed. It is also a slower HD @5400 RPM which the transfer rate is quite slow in comparison to an m.2 drive or even an SSD. If you were to install EOS on the nvme drive I’m sure it would be much faster. I’m not sure if you have Windows installed on that disk but it is plenty big enough to support both and you could use the HD as storage instead. This is an option you could do.
Edit: This is KDE on an SSD drive
[ricklinux@eos-kde ~]$ systemd-analyze critical-chain
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 @1.952s
└─multi-user.target @1.952s
└─vmware-networks.service @1.249s +701ms
└─basic.target @1.239s
└─sockets.target @1.239s
└─dbus.socket @1.239s
└─sysinit.target @1.236s
└─systemd-timesyncd.service @1.210s +25ms
└─systemd-tmpfiles-setup.service @1.184s +24ms
└─local-fs.target @1.184s
└─tmp.mount @1.180s +3ms
└─swap.target @478ms
└─swap-swapfile.swap @444ms +33ms
└─swap.mount @441ms +2ms
└─dev-sda2.device @180ms +259ms
[ricklinux@eos-kde ~]$
1 Like
[ricklinux@eos-kde ~]$ systemd-analyze time
Startup finished in 16.025s (firmware) + 9.819s (loader) + 2.054s (kernel) + 1.953s (userspace) = 29.853s
graphical.target reached after 1.952s in userspace
[ricklinux@eos-kde ~]$
These are on an SSD drive which is a lot slower than an m.2
Yes i have Windows installed on that nvme just for games@pebcak @ricklinux thx for replying i really appreciate it
1 Like
You could do that also as an SSD 500GB is not too expensive.
1 Like
