Slow, and inconsistent, boot

Hello,

Installed Manjaro alongside Win11 in a dual boot setup on a new Asus ROG Strix. System specs at end.
At power on, there is an Asus ROG splash screen immediately followed by the boot loader list on a Manjaro page. I select Manjaro. Screen goes black for almost a solid minute. Then ROG splash again but this time with Manjaro at the bottom of the screen. I’ve timed this screen displayed for nearly 2 minutes. Then I’ll get the login window.

Most of the time login goes fine. But about 25% of the time a few things can go wrong. I’ve got an external monitor attached to laptop with HDMI. Sometimes the external monitor is not found. Other times both monitors come on but the laptop monitor shows the pointer/cursor and it is locked up. In the first case, monitor not found, a log out and back in will sometimes fix it. But sometimes a re-boot is required. In the second case, locked pointer, a re-boot is required. As mention above, boot takes a long time.

Once the system is up and running I don’t have any problems. Where would I begin to trouble shoot this?

Thanks much!

System specs:

RESULT OF COMMAND "inxi -zv8"

System:
  Kernel: 6.12.63-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.12-x86_64
    root=UUID=590de9b8-1931-42e2-a421-064d563c9d0f rw rootflags=subvol=@
    quiet splash udev.log_priority=3
  Desktop: KDE Plasma v: 6.5.4 tk: Qt v: N/A info: frameworks v: 6.21.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: ROG Strix G18 G814PM_G814PM v: 1.0
    serial: <superuser required>
  Mobo: ASUSTeK model: G814PM v: 1.0 serial: <superuser required>
    uuid: <superuser required> Firmware: UEFI vendor: American Megatrends LLC.
    v: G814PM.303 date: 04/29/2025
Battery:
  ID-1: BAT0 charge: 90 Wh (100%) condition: 90/90 Wh (100%) volts: 17.46
    min: 15.99 model: AS3GYFG3KC R220358 type: Unknown serial: <filter>
    charging: status: full control: start: N/A end: 100% cycles: N/A
  Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard
    serial: <filter> charge: 55% (should be ignored) rechargeable: yes
    status: discharging
Memory:
  System RAM: total: 32 GiB available: 30.55 GiB used: 4.27 GiB (14.0%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 128 GiB slots: 2 modules: 2 EC: None
    max-module-size: 64 GiB note: est.
  Device-1: Channel-A DIMM 0 type: DDR5 detail: synchronous unbuffered
    (unregistered) size: 16 GiB speed: spec: 5600 MT/s actual: 5200 MT/s
    volts: note: check curr: 1 min: 1 max: 1 width (bits): data: 64 total: 64
    manufacturer: Micron Technology part-no: MTC8C1084S1SC56BD1 K
    serial: <filter>
  Device-2: Channel-B DIMM 0 type: DDR5 detail: synchronous unbuffered
    (unregistered) size: 16 GiB speed: spec: 5600 MT/s actual: 5200 MT/s
    volts: note: check curr: 1 min: 1 max: 1 width (bits): data: 64 total: 64
    manufacturer: Micron Technology part-no: MTC8C1084S1SC56BD1 K
    serial: <filter>
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: AMD Ryzen 9 8940HX with Radeon Graphics bits: 64 type: MT MCP
    arch: Zen 4 gen: 4 level: v4 note: check built: 2022+ process: TSMC n5 (5nm)
    family: 0x19 (25) model-id: 0x61 (97) stepping: 2 microcode: 0xA60120C
  Topology: cpus: 1x dies: 2 clusters: 2x1 cores: 16 threads: 32 tpc: 2
    smt: enabled cache: L1: 1024 KiB desc: d-16x32 KiB; i-16x32 KiB L2: 16 MiB
    desc: 16x1024 KiB L3: 64 MiB desc: 2x32 MiB
  Speed (MHz): avg: 3551 min/max: 400/5385 boost: enabled scaling:
    driver: amd-pstate-epp governor: powersave cores: 1: 3551 2: 3551 3: 3551
    4: 3551 5: 3551 6: 3551 7: 3551 8: 3551 9: 3551 10: 3551 11: 3551 12: 3551
    13: 3551 14: 3551 15: 3551 16: 3551 17: 3551 18: 3551 19: 3551 20: 3551
    21: 3551 22: 3551 23: 3551 24: 3551 25: 3551 26: 3551 27: 3551 28: 3551
    29: 3551 30: 3551 31: 3551 32: 3551 bogomips: 153403
  Flags: 3dnowprefetch abm adx aes amd_lbr_pmc_freeze amd_lbr_v2 aperfmperf
    apic arat avic avx avx2 avx512_bf16 avx512_bitalg avx512_vbmi2
    avx512_vnni avx512_vpopcntdq avx512bw avx512cd avx512dq avx512f
    avx512ifma avx512vbmi avx512vl bmi1 bmi2 bpext cat_l3 cdp_l3 clflush
    clflushopt clwb clzero cmov cmp_legacy constant_tsc cpb cppc cpuid cqm
    cqm_llc cqm_mbm_local cqm_mbm_total cqm_occup_llc cr8_legacy cx16 cx8 de
    decodeassists erms extapic extd_apicid f16c flush_l1d flushbyasid fma fpu
    fsgsbase fsrm fxsr fxsr_opt gfni ht hw_pstate ibpb ibrs ibrs_enhanced ibs
    invpcid irperf lahf_lm lbrv lm mba mca mce misalignsse mmx mmxext monitor
    movbe msr mtrr mwaitx nonstop_tsc nopl npt nrip_save nx ospke osvw
    overflow_recov pae pat pausefilter pclmulqdq pdpe1gb perfctr_core
    perfctr_llc perfctr_nb perfmon_v2 pfthreshold pge pku pni popcnt pse
    pse36 rapl rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep sha_ni
    skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 stibp
    succor svm svm_lock syscall tce topoext tsc tsc_scale umip user_shstk
    v_spec_ctrl vaes vgif vmcb_clean vme vmmcall vnmi vpclmulqdq wbnoinvd wdt
    x2apic x2avic xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves xtopology
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: Safe RET
  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: Enhanced / Automatic IBRS; IBPB:
    conditional; STIBP: always-on; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds status: Not affected
  Type: tsa mitigation: Clear CPU buffers
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: NVIDIA GB206M [GeForce RTX 5060 Max-Q / Mobile] vendor: ASUSTeK
    driver: nvidia v: 590.48.01 alternate: nouveau,nvidia_drm
    non-free: 550-580.xx+ status: current (as of 2025-11) arch: Lovelace
    code: AD1xx process: TSMC n4 (5nm) built: 2022+ pcie: gen: 5
    speed: 32 GT/s lanes: 8 link-max: lanes: 16 ports: active: HDMI-A-1
    empty: DP-4,DP-5,eDP-2 bus-ID: 01:00.0 chip-ID: 10de:2d59 class-ID: 0300
  Device-2: Advanced Micro Devices [AMD/ATI] Raphael vendor: ASUSTeK
    driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm)
    built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: eDP-1
    empty: DP-1, DP-2, DP-3, Writeback-1 bus-ID: 69:00.0 chip-ID: 1002:164e
    class-ID: 0300 temp: 41.0 C
  Device-3: Sonix USB2.0 FHD UVC WebCam driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 7-1:2 chip-ID: 3277:0010
    class-ID: fe01 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
    compositor: kwin_wayland driver: X: loaded: amdgpu,nvidia
    unloaded: modesetting,nouveau alternate: fbdev,nv,vesa dri: radeonsi
    gpu: amdgpu,nv_platform,nvidia,nvidia-nvswitch d-rect: 3840x1080
    display-ID: 0
  Monitor-1: HDMI-A-1 pos: right model: ASUS PA279CV serial: <filter>
    built: 2025 res: mode: 1920x1080 hz: 60 scale: 75% (0.75) to: 2560x1440
    dpi: 82 gamma: 1.2 chroma: red: x: 0.659 y: 0.314 green: x: 0.263 y: 0.663
    blue: x: 0.141 y: 0.055 white: x: 0.314 y: 0.329
    size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9
    modes: 1920x1080, 1680x1050, 1280x1024, 1440x900, 1280x960, 1280x720,
    1024x768, 800x600, 640x480
  Monitor-2: eDP-1 pos: primary,left model: BOE Display NE180QDM-NZC
    built: 2024 res: mode: 1920x1080 hz: 240 scale: 75% (0.75) to: 2560x1440
    dpi: 168 gamma: 1.2 chroma: red: x: 0.682 y: 0.314 green: x: 0.263
    y: 0.690 blue: x: 0.145 y: 0.055 white: x: 0.314 y: 0.329
    size: 388x242mm (15.28x9.53") diag: 457mm (18") ratio: 16:10
    modes: 2560x1600, 1920x1200, 1920x1080, 1600x1200, 1680x1050, 1280x1024,
    1440x900, 1280x800, 1280x720, 1024x768, 800x600, 640x480
  EDID-Warnings: 1: parse_edid: unknown tag 112
  API: EGL v: 1.5 hw: drv: nvidia drv: amd radeonsi platforms: device: 0
    drv: nvidia device: 2 drv: radeonsi device: 3 drv: swrast gbm: drv: nvidia
    surfaceless: drv: nvidia wayland: drv: radeonsi x11: drv: radeonsi
    inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: amd mesa v: 25.3.2-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon 610M (radeonsi
    raphael_mendocino LLVM 21.1.6 DRM 3.61 6.12.63-1-MANJARO)
    device-ID: 1002:164e memory: 500 MiB unified: no display-ID: :1.0
  API: Vulkan v: 1.4.335 layers: 4 device: 0 type: integrated-gpu name: AMD
    Radeon 610M (RADV RAPHAEL_MENDOCINO) driver: mesa radv v: 25.3.2-arch1.1
    device-ID: 1002:164e surfaces: N/A device: 1 type: discrete-gpu
    name: NVIDIA GeForce RTX 5060 Laptop GPU driver: nvidia v: 590.48.01
    device-ID: 10de:2d59 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: NVIDIA GB206 High Definition Audio driver: snd_hda_intel v: kernel
    pcie: gen: 5 speed: 32 GT/s lanes: 8 link-max: lanes: 16 bus-ID: 01:00.1
    chip-ID: 10de:22eb class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Audio Coprocessor vendor: ASUSTeK
    driver: snd_rpl_pci_acp6x v: kernel alternate: snd_pci_acp3x,
    snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x, snd_acp_pci, snd_pci_ps,
    snd_sof_amd_renoir, snd_sof_amd_rembrandt, snd_sof_amd_vangogh,
    snd_sof_amd_acp63, snd_sof_amd_acp70 pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 69:00.5 chip-ID: 1022:15e2 class-ID: 0480
  Device-3: Advanced Micro Devices [AMD] Ryzen HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 69:00.6 chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.12.63-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.4.9 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: e000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp3s0 state: down mac: <filter>
  Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
    vendor: Foxconn driver: mt7921e v: kernel pcie: gen: 2 speed: 5 GT/s
    lanes: 1 bus-ID: 04:00.0 chip-ID: 14c3:0616 class-ID: 0280
  IF: wlp4s0 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  Device-3: Realtek RTL8153 Gigabit Ethernet Adapter driver: r8152 type: USB
    rev: 3.2 speed: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 bus-ID: 2-1.3:3
    chip-ID: 0bda:8153 class-ID: 0000 serial: <filter>
  IF: enp103s0u1u3 state: down mac: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Device-1: Foxconn / Hon Hai Wireless_Device driver: btusb v: 0.8 type: USB
    rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-2:3 chip-ID: 0489:e0f6
    class-ID: e001 serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 953.87 GiB used: 210.18 GiB (22.0%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Micron
    model: MTFDKBA1T0QGN-1BN1AABGA size: 953.87 GiB block-size: physical: 512 B
    logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: V8MA000 temp: 32.9 C scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 407.78 GiB size: 407.78 GiB (100.00%)
    used: 210.11 GiB (51.5%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:7
    label: N/A uuid: 590de9b8-1931-42e2-a421-064d563c9d0f
  ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.46%)
    used: 72.4 MiB (28.3%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
    label: SYSTEM uuid: B4C9-EBBE
  ID-3: /home raw-size: 407.78 GiB size: 407.78 GiB (100.00%)
    used: 210.11 GiB (51.5%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:7
    label: N/A uuid: 590de9b8-1931-42e2-a421-064d563c9d0f
  ID-4: /var/cache raw-size: 407.78 GiB size: 407.78 GiB (100.00%)
    used: 210.11 GiB (51.5%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:7
    label: N/A uuid: 590de9b8-1931-42e2-a421-064d563c9d0f
  ID-5: /var/log raw-size: 407.78 GiB size: 407.78 GiB (100.00%)
    used: 210.11 GiB (51.5%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:7
    label: N/A uuid: 590de9b8-1931-42e2-a421-064d563c9d0f
Swap:
  Alert: No swap data was found.
Unmounted:
  ID-1: /dev/nvme0n1p2 maj-min: 259:2 size: 16 MiB fs: <superuser required>
    label: N/A uuid: N/A
  ID-2: /dev/nvme0n1p3 maj-min: 259:3 size: 516.83 GiB fs: ntfs label: OS
    uuid: 10C4CB93C4CB7A0C
  ID-3: /dev/nvme0n1p4 maj-min: 259:4 size: 750 MiB fs: ntfs label: RECOVERY
    uuid: 9AA02CECA02CD115
  ID-4: /dev/nvme0n1p5 maj-min: 259:5 size: 28 GiB fs: ntfs label: RESTORE
    uuid: 188057BE8057A154
  ID-5: /dev/nvme0n1p6 maj-min: 259:6 size: 260 MiB fs: vfat label: MYASUS
    uuid: E457-D78D
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 1-1:2 info: VIA Labs USB2.0 Hub ports: 5 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 2109:2817
    class-ID: 0900
  Hub-3: 1-1.3:3 info: Genesys Logic Hub ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0608 class-ID: 0900
  Device-1: 1-1.3.1:5 info: Synaptics VMM7100 type: HID,billboard
    driver: N/A interfaces: 2 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1
    mode: 2.0 power: 100mA chip-ID: 06cb:7100 class-ID: 1100 serial: <filter>
  Device-2: 1-1.5:4 info: Anker 364 USB C Hub(10-in-1 Dual 4K HDMI)
    type: billboard driver: N/A interfaces: 1 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 291a:83a2 class-ID: 1100 serial: <filter>
  Hub-4: 2-0:1 info: super-speed hub ports: 2 rev: 3.1
    speed: 20 Gb/s (2.33 GiB/s) lanes: 2 mode: 3.2 gen-2x2 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-5: 2-1:2 info: VIA Labs USB3.0 Hub ports: 4 rev: 3.2
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 2109:0817
    class-ID: 0900
  Device-1: 2-1.3:3 info: Realtek RTL8153 Gigabit Ethernet Adapter
    type: Network driver: r8152 interfaces: 1 rev: 3.2
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 power: 112mA
    chip-ID: 0bda:8153 class-ID: 0000 serial: <filter>
  Hub-6: 3-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 3-1:2 info: ASUSTek N-KEY Device type: keyboard,mouse
    driver: asus,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 100mA chip-ID: 0b05:19b6 class-ID: 0301
  Device-2: 3-2:3 info: Foxconn / Hon Hai Wireless_Device type: bluetooth
    driver: btusb interfaces: 3 rev: 2.1 speed: 480 Mb/s (57.2 MiB/s) lanes: 1
    mode: 2.0 power: 100mA chip-ID: 0489:e0f6 class-ID: e001 serial: <filter>
  Hub-7: 4-0:1 info: super-speed hub ports: 2 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-8: 5-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 5-1:2 info: Logitech Nano Receiver type: keyboard,mouse
    driver: logitech-djreceiver,usbhid interfaces: 2 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 98mA
    chip-ID: 046d:c534 class-ID: 0301
  Device-2: 5-2:3 info: Pixart Imaging Optical Mouse type: mouse
    driver: hid-generic,usbhid interfaces: 1 rev: 2.0
    speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA
    chip-ID: 093a:2510 class-ID: 0301
  Hub-9: 6-0:1 info: super-speed hub ports: 2 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-10: 7-0:1 info: hi-speed hub with single TT ports: 1 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 7-1:2 info: Sonix USB2.0 FHD UVC WebCam type: video
    driver: uvcvideo interfaces: 3 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s)
    lanes: 1 mode: 2.0 power: 500mA chip-ID: 3277:0010 class-ID: fe01
    serial: <filter>
Sensors:
  System Temperatures: cpu: 48.6 C mobo: 32.0 C gpu: amdgpu temp: 43.0 C
  Fan Speeds (rpm): cpu: 2200 fan-1: 2280
Repos:
  Packages: 1523 pm: pacman pkgs: 1502 libs: 393 tools: pamac pm: flatpak
    pkgs: 21
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://mirror.it4i.cz/manjaro/stable/$repo/$arch
    2: https://muug.ca/mirror/manjaro/stable/$repo/$arch
    3: https://www.mirrorservice.org/sites/repo.manjaro.org/repos/stable/$repo/$arch
    4: https://coresite.mm.fcix.net/manjaro/stable/$repo/$arch
    5: https://mirror.xeonbd.com/manjaro/stable/$repo/$arch
    6: https://mirror.phoepsilonix.love/manjaro/stable/$repo/$arch
    7: https://linorg.usp.br/manjaro/stable/$repo/$arch
    8: https://ziply.mm.fcix.net/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 538
  1: cpu: 7.1% command: firefox pid: 3868 mem: 885.8 MiB (2.8%)
  2: cpu: 3.7% command: kwin_wayland pid: 1243 mem: 258.2 MiB (0.8%)
  3: cpu: 1.6% command: firefox pid: 6743 mem: 312.1 MiB (0.9%)
  4: cpu: 1.0% command: konsole pid: 7193 mem: 320.3 MiB (1.0%)
  5: cpu: 0.9% command: firefox pid: 4004 mem: 216.5 MiB (0.6%)
  Memory top: 5 of 538
  1: mem: 885.8 MiB (2.8%) command: firefox pid: 3868 cpu: 7.1%
  2: mem: 520.4 MiB (1.6%) command: firefox pid: 5325 cpu: 0.5%
  3: mem: 433.9 MiB (1.3%) command: plasmashell pid: 1545 cpu: 0.1%
  4: mem: 410.8 MiB (1.3%) command: firefox pid: 4397 cpu: 0.7%
  5: mem: 361.0 MiB (1.1%) command: firefox pid: 4491 cpu: 0.2%
Info:
  Processes: 538 Power: uptime: 44m states: freeze,mem,disk suspend: s2idle
    wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume
    image: 12.18 GiB services: org_kde_powerdevil, power-profiles-daemon,
    upowerd Init: systemd v: 258 default: graphical tool: systemctl
  Compilers: clang: 21.1.6 gcc: 15.2.1 Shell: Zsh v: 5.9 running-in: konsole
    inxi: 3.3.40

First, try to find out exactly what’s happening.

That way you can better understand the timing. (UEFI, RAM init, GRUB, KERNEL ..) Most of this is currently running without you seeing anything on the screen.

  • Make the GRUB boot visible (menu instead of hidden)
  • Display the kernel boot messages (instead of silent)

Log messages only start when the kernel starts. You’ll need to time everything that happens before that with a stopwatch.
:footprints:

There are some tools which can show information about the time spent in various stages of booting, for instance:

systemd-analyze blame
systemd-analyze critical-chain

Additionally, maybe try inspecting the output from journalctl for the current boot for any errors (-b on its own means the current session):

journalctl -b

or if the previous boot failed, you can look at its journalctl output by adding a -1 offset to the -b option:

journalctl -b-1

I am thinking the Windows Fast Startup is enabled.

When the feature is active it may lock devices which may cause a long delay while the kernel probes the hardware.

  • Boot into Windows
  • Open a terminal as administrator
  • Execute powercfg /h off
  • Close terminal and reboot
2 Likes

Or worse: hide hardware from the Linux kernel. :roll_eyes:

1 Like

Thanks all for your responses.
I had turned off Win fast boot and Bitlocker before I did the Manjaro install. There is also a fast boot option in the Bios which I disabled. However, I did boot into Windows just to verify I had shut it off. When I re-booted and selected Manjaro it took 3 restarts before the boot completed.

I ran systemd-analyze critical-chain and got the following output:

TL4 edit - remove screenshots of text

Then ran journalctl -b-1 These are screen grabs of ‘highlights’ from that output:

TL4 edit - remove screenshots of text

I’m not sure what to make of all this info except that it doesn’t look good. If there is anything in all this that jumps out to anyone as a “known” problem it would be helpful to hear it.

I’m also thinking maybe a fresh install. Ultimately I don’t want Windows on it at all, so maybe a full wipe and reinstall? Any thoughts greatly appreciated! Thanks again!

Please don’t post screenshots of text. Such screenshots don’t help the searchability of the forum. They also mean I can’t copy and paste a line from a screen shot, which I would like to do here.

In your first screenshot there is a reference to Plymouth which appears to add several seconds to the boot time. Plymouth is for the splash screen and it is possible to remove it to see if that helps you.

Removal instructions here: [HowTo] Disable or Remove Plymouth (boot splash)

2 Likes

Please do not post screenshots of text. I have removed the screenshots.

Instead copy use your mouse to highlight text and copy to clipboard. Then create a code fence in the topic - using the </> button.

Paste the content of the clipboard between the fence - like the illustrative example below.

```
type or paste code here
```

I will assume you have disabled Windows Fast Startup feature.

When a laptop like yours have issues finding which screen to use it is often caused by the driver.

Do you have the supergfxctl utility installed? It is a tool made by ASUS to provide switching between iGPU and dGPU.

Are you using the video-hybrid-amd-nvidia-prime driver combination configured by mhwd?

sudo pacman -Syu
sudo mhwd -i pci video-hybrid-amd-nvidia-prime
sudo pacman -S supergfxctl

I note that you are using two different refresh rates 60Hz and 240Hz and that you have a fractional scale of 0.75.

I don’t know if this could cause the display configuration to slow the whole startup process - but I suggest you start troubleshooting by setting the refresh rate equally and use the default resolution of your monitors -

3 Likes

Again, thank you for your responses. Sorry about the screen captures. I thought the color coding might be helpful but I understand why text is preferred.

Windows fast start is disabled.

video-hybrid-amd-nvidia-prime

Was installed.

 supergfxctl

Is now installed
Monitors resolution, refresh and scale are now set the same.

After above did a reboot and got similar problem as before: one active screen, (laptop), and locked cursor.
Reboot, then both screens came up but locked cursor on laptop.
Log out/in - all good, both screens active and cursor responsive.

Disabled plymouth as described in article by editing and updating grub config..

Reboot, still a long time, 1.5 -2 min, from boot menu to log in screen.
just the laptop screen came up with responsive cursor. Log out and in, no change.
Reboot, after boot menu screen filled with code and locked up.
Forced shut down and reboot. Got both screens up with responsive cursor.

Ran some diagnostics:
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 @2.684s
└─multi-user.target @2.684s
  └─cups.service @2.524s +160ms
    └─network.target @2.523s
      └─NetworkManager.service @2.237s +285ms
        └─basic.target @2.236s
          └─dbus-broker.service @2.210s +16ms
            └─dbus.socket @2.207s +19us
              └─sysinit.target @2.203s
                └─systemd-sysctl.service @2.141s +61ms
                  └─systemd-modules-load.service @358ms +1.782s
                    └─systemd-journald.socket @349ms +26us
                      └─-.mount @323ms
                        └─-.slice @323ms

systemd-analyze blame

1.782s systemd-modules-load.service
 826ms systemd-rfkill.service
 824ms systemd-vconsole-setup.service
 396ms boot-efi.mount
 389ms home.mount
 388ms tmp.mount
 388ms var-cache.mount
 388ms var-log.mount
 383ms dev-nvme0n1p7.device
 285ms NetworkManager.service
 234ms systemd-udev-trigger.service
 160ms cups.service
 140ms upower.service
 139ms user@1000.service
 118ms lvm2-monitor.service
  73ms systemd-journald.service
  71ms udisks2.service
  68ms accounts-daemon.service
  66ms systemd-journal-flush.service
  64ms systemd-fsck@dev-disk-by\x2duuid-B4C9\x2dEBBE.service
  62ms systemd-tmpfiles-setup-dev-early.service
  61ms systemd-sysctl.service
  61ms systemd-backlight@backlight:nvidia_wmi_ec_backlight.service
  53ms systemd-timesyncd.service
  53ms systemd-user-sessions.service
  48ms user-runtime-dir@1000.service
  48ms systemd-backlight@leds:asus::kbd_backlight.service
  46ms systemd-tmpfiles-setup.service
  41ms ModemManager.service
  36ms systemd-udevd.service
  35ms polkit.service
  30ms wpa_supplicant.service
  29ms systemd-random-seed.service
  29ms systemd-logind.service
  28ms geoclue.service
  27ms systemd-hostnamed.service
  27ms power-profiles-daemon.service
  26ms colord.service
  20ms systemd-tmpfiles-setup-dev.service
  17ms bluetooth.service
  17ms bolt.service
  16ms dbus-broker.service
  15ms plymouth-read-write.service
  14ms systemd-userdbd.service
  13ms plymouth-quit.service
  10ms dev-hugepages.mount
  10ms modprobe@dm_mod.service
  10ms dev-mqueue.mount
   9ms sys-kernel-debug.mount
   9ms sys-kernel-tracing.mount
   8ms kmod-static-nodes.service
   7ms supergfxd.service
   7ms sys-kernel-config.mount
   7ms systemd-udev-load-credentials.service
   7ms rtkit-daemon.service
   6ms modprobe@loop.service
   6ms sys-fs-fuse-connections.mount
   6ms systemd-remount-fs.service
   6ms systemd-userdb-load-credentials.service
   6ms systemd-update-utmp.service
   4ms alsa-restore.service
   3ms plymouth-quit-wait.service
 673us polkit-agent-helper.socket
 566us sshd-unix-local.socket
 466us systemd-bootctl.socket
 432us systemd-coredump.socket
 403us systemd-ask-password.socket
 332us systemd-factory-reset.socket
 315us systemd-sysext.socket
 238us systemd-creds.socket
  78us dirmngr@etc-pacman.d-gnupg.socket
  41us gpg-agent@etc-pacman.d-gnupg.socket
  40us gpg-agent-ssh@etc-pacman.d-gnupg.socket
  37us gpg-agent-browser@etc-pacman.d-gnupg.socket
  36us gpg-agent-extra@etc-pacman.d-gnupg.socket
  34us keyboxd@etc-pacman.d-gnupg.socket
  34us cups.socket
  30us systemd-machined.socket
  30us systemd-journald-dev-log.socket
  26us systemd-journald.socket
  25us systemd-importd.socket
  22us lvm2-lvmpolld.socket
  19us systemd-udevd-control.socket
  19us dbus.socket
  17us dm-event.socket
  17us systemd-userdbd.socket
  14us systemd-udevd-varlink.socket
  13us systemd-hostnamed.socket
  11us systemd-logind-varlink.socket
   8us systemd-rfkill.socket
   7us systemd-udevd-kernel.socket

I ran the “journalctl -b” and "journalctl -b-1 commands. I uploaded them to my Google Drive as text files. here is the link:
https://drive.google.com/drive/folders/1QSV4g1LaSbaaBtug4rrFkJu1sF9IcyAv?usp=drive_link

If you want the full text of those files here I’ll include them. They are each over 2500 lines however.

Thanks !