You are not logged in.
Pages: 1
Hey Everyone,
I've recently bought Minisforum HX99G model (AMD Ryzen 6900HX + Radeon 6600M repuposed mobile board as minipc), I've absolutely loved it, compared to my old, large and loud Desktop, amazing mini pc. As soon as it arrived, I've added 2TB nvme ssd along with existing one, and got rid of pre-installed Windows. Installed Linux on it, everything worked out of the box including suspend/resume. But I have a very slow boot time, looks like 20 secs delayed, according to systemd-analyze, it's because of initrd. My UEFI Bios is on optimized defaults. Did not really change anything apart from secure boot.
Startup finished in 12.229s (firmware) + 4.525s (loader) + 770ms (kernel) + 23.856s (initrd) + 2.940s (userspace) = 44.323s
graphical.target reached after 2.571s in userspace.
Dmesg: https://pastebin.com/CfQsswBq
Cmd line: root=UUID=a88e4ba7-XXXX-XXXX-XXXX-2d17ab78c16b rw initrd=\amd-ucode.img tsc=unstable trace_clock=local initrd=\initramfs-linux.img
╰─ 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.571s
└─multi-user.target @2.571s
└─libvirtd.service @2.410s +109ms
└─network.target @2.371s
└─NetworkManager.service @2.043s +327ms
└─dbus.service @1.784s +87ms
└─basic.target @1.737s
└─sockets.target @1.737s
└─virtlogd.socket @1.737s
└─sysinit.target @1.735s
└─systemd-vconsole-setup.service @1.631s +101ms
└─systemd-journald.socket
└─system.slice
└─-.slice
systemd-analyze boot output:
https://pasteboard.co/7T8tya48sgUI.jpg
What I have done so far, creating a shutdown task with systemd to fsck my pretty big EFI partition then unmount it properly. I had the impression that fsck during boot was slowing it down, but clearly not. Also added `tsc=unstable` as dmesg suggested, but it does not have any impact on boot time. I've tried linux-lts kernel and linux-amd kernel but no luck. Tried to disable xhci/usb ports from bios, PCIE power settings, did not get any result. Tried to change hooks order or even removing some of them. But so far nothing helped with 20secs delayed boot. Also I have some xhci/usb module errors that I don't understand :confused:
My modules and hooks list:
MODULES=(amdgpu nvme usbhid)
HOOKS=(base consolefont block filesystems fsck modconf udev systemd kms keyboard keymap)
I am using refind as boot loader with manual booting with `graphics on` option. I have kmscon which works just fine with my HiDPI monitor. Altho amdgpudrmfb (fb0) does not really print systemd status messages or work with plymouth.
Hardware details:
System:
Kernel: 6.5.6-arch2-1 arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
Desktop: GNOME v: 44.5 Distro: Arch Linux
Machine:
Type: Desktop System: Micro (HK) Tech product: HX99G v: N/A
serial: <superuser required>
Mobo: Shenzhen Meigao Equipment model: F7BAA serial: <superuser required>
UEFI: American Megatrends LLC. v: 0.18 date: 03/02/2023
CPU:
Info: 8-core model: AMD Ryzen 9 6900HX with Radeon Graphics bits: 64
type: MT MCP arch: Zen 3+ rev: 1 cache: L1: 512 KiB L2: 4 MiB L3: 16 MiB
Speed (MHz): avg: 636 high: 2053 min/max: 400/4935 cores: 1: 1397 2: 400
3: 400 4: 400 5: 400 6: 400 7: 400 8: 400 9: 2053 10: 400 11: 1534 12: 400
13: 400 14: 400 15: 400 16: 400 bogomips: 105440
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: AMD Navi 23 [Radeon RX 6600/6600 XT/6600M] driver: amdgpu
v: kernel arch: RDNA-2 bus-ID: 03:00.0
Device-2: AMD Rembrandt [Radeon 680M] driver: amdgpu v: kernel
arch: RDNA-2 bus-ID: e9:00.0 temp: 36.0 C
Display: wayland server: X.org v: 1.21.1.8 with: Xwayland v: 23.2.1
compositor: gnome-shell driver: gpu: amdgpu resolution: 2560x1440~60Hz
API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel
bus-ID: 03:00.1
Device-2: AMD Rembrandt Radeon High Definition Audio driver: snd_hda_intel
v: kernel bus-ID: e9:00.1
Device-3: AMD ACP/ACP3X/ACP6x Audio Coprocessor driver: snd_pci_acp6x
v: kernel bus-ID: e9:00.5
Device-4: AMD Family 17h/19h HD Audio vendor: Realtek
driver: snd_hda_intel v: kernel bus-ID: e9:00.6
Device-5: C-Media Audio Adapter (Unitek Y-247A)
driver: cmedia_hs100b,snd-usb-audio,usbhid type: USB bus-ID: 5-3:2
API: ALSA v: k6.5.6-arch2-1 status: kernel-api
Server-1: PipeWire v: 0.3.81 status: active
Network:
Device-1: Intel Ethernet I225-V driver: igc v: kernel port: N/A
bus-ID: 05:00.0
IF: enp5s0 state: down mac: <filter>
Device-2: MEDIATEK MT7921K Wi-Fi 6E 80MHz driver: mt7921e v: kernel
bus-ID: 07:00.0
IF: wlp7s0 state: up mac: <filter>
IF-ID-1: virbr0 state: down mac: <filter>
Bluetooth:
Device-1: MediaTek Wireless_Device driver: btusb v: 0.8 type: USB
bus-ID: 7-3:3
Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Drives:
Local Storage: total: 2.78 TiB used: 358.22 GiB (12.6%)
ID-1: /dev/nvme0n1 vendor: Crucial model: CT2000P3PSSD8 size: 1.82 TiB
temp: 43.9 C
ID-2: /dev/nvme1n1 vendor: Kingston model: OM8PGP41024Q-A0
size: 953.87 GiB temp: 39.9 C
ID-3: /dev/sda model: N/A size: 29.3 GiB type: USB
Partition:
ID-1: / size: 1.39 TiB used: 351.5 GiB (24.6%) fs: ext4 dev: /dev/nvme0n1p2
ID-2: /boot size: 1.43 GiB used: 500.7 MiB (34.1%) fs: vfat
dev: /dev/nvme0n1p1
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 40.9 C mobo: N/A
Fan Speeds (rpm): N/A
GPU: device: amdgpu temp: 36.0 C device: amdgpu temp: 38.0 C fan: 0
Info:
Processes: 449 Uptime: 2h 33m Memory: total: 32 GiB note: est.
available: 30.63 GiB used: 9.2 GiB (30.0%) Init: systemd Compilers:
gcc: 13.2.1 clang: 16.0.6 Packages: 1634 Shell: Zsh v: 5.9 inxi: 3.3.30
Do you have any idea where to look for this problem? Thank you in advance.
Last edited by risyasin (2023-10-10 18:55:20)
Offline
Did you read :
https://wiki.archlinux.org/title/mkinitcpio ?
Check the order of the hook entries.
Perhaps the autodetect hook can speed up your boot.
In effect, in the fallback preset the autodetect is missing, causing the load of a lot of modules.
From the manual :
the default ramdisk image created following the directives specified in the mkinitcpio #Configuration, and
the fallback ramdisk image, same as above except that the autodetect hook is skipped during creation, thus including a full range of modules which supports most systems.
Moreover, using journalctl -b -o short-monotonic
can give you a better understanding of the boot process.
Offline
Pages: 1
