hi All.
Долгая за грузка началась после того как мне захотелось bluetooth.
Поменял я модуль на AR5B225.
bluetooth появился, но грузиться стал намного тупее.
Что имеем:
Distributor ID: Linuxmint Description: Linux Mint 21.2 Release: 21.2 Codename: victoria
Linux hbars-Aspire-5740 6.4.13-zabbly+ #ubuntu22.04 SMP PREEMPT_DYNAMIC Wed Aug 30 22:09:58 UTC 2023 x86_64 x86_64 x86_64 GNU/LinuxЯдро значения не имеет. С родным 5.15.0 то же самое.
Bus 002 Device 006: ID 0cf3:3004 Qualcomm Atheros Communications AR3012 Bluetooth 4.0
05:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01)
Ну и результат до замены модуля:
913ms blueman-mechanism.service
911ms e2scrub_reap.service
856ms dev-sda1.device
540ms networkd-dispatcher.service
458ms user@1000.service
458ms udisks2.service
382ms accounts-daemon.service
355ms ModemManager.service
327ms systemd-journal-flush.service
307ms lightdm.service
283ms systemd-udevd.service
283ms ubuntu-system-adjustments.service
269ms polkit.service
268ms plymouth-quit-wait.service
257ms NetworkManager.service
222ms switcheroo-control.service
222ms gpu-manager.service
210ms systemd-logind.service
208ms thermald.service
206ms wpa_supplicant.service
206ms systemd-resolved.service
168ms smartmontools.service
147ms systemd-udev-trigger.service
116ms rsyslog.service
112ms networking.service
112ms systemd-modules-load.service
109ms keyboard-setup.service
98ms systemd-journald.service
96ms grub-common.service
92ms colord.service
83ms upower.service
78ms modprobe@chromeos_pstore.service
67ms systemd-fsck@dev-disk-by\x2duuid-488cf1fe\x2d0e0f\x2d4186\x2dbd53\x2d821b15f5f925.service
67ms ntp.service
63ms systemd-sysctl.service
58ms lm-sensors.service
43ms systemd-tmpfiles-setup.service
40ms kerneloops.service
39ms alsa-restore.service
36ms dev-hugepages.mount
36ms grub-initrd-fallback.service
35ms dev-mqueue.mount
34ms sys-kernel-debug.mount
33ms sys-kernel-tracing.mount
33ms systemd-update-utmp.service
28ms plymouth-start.service
28ms kmod-static-nodes.service
25ms modprobe@configfs.service
25ms systemd-binfmt.service
25ms systemd-backlight@backlight:acpi_video0.service
24ms modprobe@drm.service
24ms systemd-tmpfiles-setup-dev.service
23ms modprobe@fuse.service
22ms systemd-sysusers.service
21ms dns-clean.service
21ms user-runtime-dir@1000.service
20ms dev-disk-by\x2duuid-90076be5\x2ddf6c\x2d48c9\x2d8601\x2dcd16a1a95d69.swap
18ms systemd-random-seed.service
17ms systemd-remount-fs.service
16ms systemd-update-utmp-runlevel.service
14ms plymouth-read-write.service
14ms home.mount
11ms console-setup.service
11ms proc-sys-fs-binfmt_misc.mount
10ms systemd-user-sessions.service
10ms ifupdown-pre.service
10ms sys-fs-fuse-connections.mount
9ms finalrd.service
8ms sys-kernel-config.mount
7ms modprobe@efi_pstore.service
7ms openvpn.service
7ms modprobe@pstore_blk.service
6ms rtkit-daemon.service
5ms modprobe@pstore_zone.service
3ms setvtrgb.service
3ms modprobe@ramoops.service
44us blk-availability.service
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.912s
└─multi-user.target @2.912s
└─blueman-mechanism.service @1.987s +913ms
└─basic.target @1.942s
└─sockets.target @1.942s
└─uuidd.socket @1.942s
└─sysinit.target @1.934s
└─systemd-update-utmp.service @1.842s +33ms
└─systemd-tmpfiles-setup.service @1.767s +43ms
└─local-fs.target @1.755s
└─home.mount @1.741s +14ms
└─systemd-fsck@dev-disk-by\x2duuid-488cf1fe\x2d0e0f\x2d4186\x2dbd53\x2d821b15f5f925.service @1.647s +67ms
└─dev-disk-by\x2duuid-488cf1fe\x2d0e0f\x2d4186\x2dbd53\x2d821b15f5f925.device @1.603s
И после:
25.604s dev-sda1.device
1.024s blueman-mechanism.service
1.017s e2scrub_reap.service
625ms networkd-dispatcher.service
526ms udisks2.service
482ms accounts-daemon.service
405ms ModemManager.service
352ms systemd-journal-flush.service
345ms user@1000.service
337ms ubuntu-system-adjustments.service
331ms lightdm.service
326ms systemd-resolved.service
326ms NetworkManager.service
307ms plymouth-quit-wait.service
304ms polkit.service
297ms systemd-udevd.service
269ms networking.service
269ms switcheroo-control.service
264ms gpu-manager.service
262ms systemd-logind.service
258ms thermald.service
254ms wpa_supplicant.service
204ms smartmontools.service
164ms systemd-udev-trigger.service
149ms grub-common.service
133ms upower.service
129ms rsyslog.service
107ms keyboard-setup.service
105ms systemd-journald.service
101ms systemd-modules-load.service
92ms colord.service
87ms modprobe@chromeos_pstore.service
71ms bluetooth.service
65ms lm-sensors.service
50ms systemd-fsck@dev-disk-by\x2duuid-488cf1fe\x2d0e0f\x2d4186\x2dbd53\x2d821b15f5f925.service
46ms home.mount
44ms systemd-backlight@backlight:acpi_video0.service
41ms systemd-sysctl.service
40ms alsa-restore.service
39ms systemd-tmpfiles-setup-dev.service
38ms kerneloops.service
34ms grub-initrd-fallback.service
34ms dev-hugepages.mount
33ms dev-mqueue.mount
32ms systemd-tmpfiles-setup.service
32ms sys-kernel-debug.mount
32ms systemd-binfmt.service
31ms sys-kernel-tracing.mount
27ms plymouth-start.service
27ms modprobe@ramoops.service
26ms kmod-static-nodes.service
24ms dns-clean.service
23ms systemd-sysusers.service
23ms modprobe@configfs.service
23ms systemd-remount-fs.service
23ms modprobe@drm.service
22ms modprobe@efi_pstore.service
22ms modprobe@fuse.service
21ms modprobe@pstore_blk.service
20ms modprobe@pstore_zone.service
20ms user-runtime-dir@1000.service
17ms ntp.service
17ms dev-disk-by\x2duuid-90076be5\x2ddf6c\x2d48c9\x2d8601\x2dcd16a1a95d69.swap
15ms proc-sys-fs-binfmt_misc.mount
15ms systemd-random-seed.service
14ms console-setup.service
14ms systemd-user-sessions.service
14ms systemd-update-utmp.service
13ms plymouth-read-write.service
12ms ifupdown-pre.service
12ms systemd-update-utmp-runlevel.service
11ms finalrd.service
9ms systemd-rfkill.service
8ms openvpn.service
8ms sys-fs-fuse-connections.mount
7ms setvtrgb.service
6ms sys-kernel-config.mount
5ms rtkit-daemon.service
50us blk-availability.service
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 @27.625s
└─multi-user.target @27.625s
└─blueman-mechanism.service @26.588s +1.024s
└─basic.target @26.576s
└─sockets.target @26.576s
└─uuidd.socket @26.576s
└─sysinit.target @26.567s
└─systemd-update-utmp.service @26.553s +14ms
└─systemd-tmpfiles-setup.service @26.514s +32ms
└─local-fs.target @26.462s
└─home.mount @26.416s +46ms
└─systemd-fsck@dev-disk-by\x2duuid-488cf1fe\x2d0e0f\x2d4186\x2dbd53\x2d821b15f5f925.service @26.363s +50ms
└─dev-disk-by\x2duuid-488cf1fe\x2d0e0f\x2d4186\x2dbd53\x2d821b15f5f925.device @26.359s
Что еще посмотреть и можно ли решить? Оно конечно не критично, но все же. Где косяк?
Причем задумывается уже после того как светодиод bluetooth уже загорается.