Linux Mint Türkiye

Linux Mint Destek => Açılış, Kapanış ve Oturum Açma => Konuyu başlatan: sebastianhawk - 31 Aralık 2019, 17:14:50

Başlık: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: sebastianhawk - 31 Aralık 2019, 17:14:50: Linux Mint 19.3 Cinnamon kullanıyorum.Bilgisayarım açılırken 4-5 dakikadan uzun sürede açılıyor.Bu forumdaki bir başlığa baktım fakat işe yaramadı.Linux Mint kullanmada da yeniyim.Yardım eder misiniz?

^{_{Düzenleme: Konu başlığı}}
Başlık: Ynt: Cinnamon'un başlatılmasında sorunlar var
Gönderen: Butterfly - 31 Aralık 2019, 18:04:49: Sorun oturum açmada mı yoksa, oturum açma ekranına kadar ulaşılan sürede mi? Yazdıklarınızdan ve konu başlığından tam anlaşılmıyor.

Ayrıca sistem ile ilgili hiç bir şey paylaşmamışsınız. Açtığınız konuda aşağıdaki hususlara özen gösteriniz ve konuda belirtilen hususları tamamlayınız.

[warning]Konu Açarken Dikkat Edilmesi Gerekenler (https://forum.linuxmint.net.tr/index.php?topic=3067.0)[/warning]
Başlık: Ynt: Cinnamon'un başlatılmasında sorunlar var
Gönderen: sebastianhawk - 31 Aralık 2019, 18:33:58: Bilgisayarın power tuşuna bastıktan sonra linux mintin simgesi çıkıyor.Çıkan simgeyle birlikte linux masaüstünün gelmesi 3-4 dakikayı buluyor.Açıldıktan sonra da "Cinnamon'un başlatılmasında sorunlar var eklentileri,masaüstü uygulamacıklarını düzeltiniz vb."gibi bir bildirim geliyor.Son 3 gündür durum bu şekilde biraz araştırma yaptım ama hiç bir şey bulamadım.

Kod: [Seç]
System: Host: SEBASTIAN Kernel: 5.3.0-24-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Cinnamon 4.4.6 wm: muffin dm: LightDM Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic Machine: Type: Laptop System: ASUSTeK product: X55A v: 1.0 serial: <filter> Mobo: ASUSTeK model: X55A v: 1.0 serial: <filter> BIOS: American Megatrends v: X55A.415 date: 11/09/2012 Battery: ID-1: BAT0 charge: 0 Wh condition: 10.9/48.6 Wh (22%) volts: 10.8/10.8 model: ASUSTeK K55--44 serial: <filter> status: Charging CPU: Topology: Dual Core model: Intel Pentium B980 bits: 64 type: MCP arch: Sandy Bridge rev: 7 L2 cache: 2048 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 9578 Speed: 952 MHz min/max: 800/2400 MHz Core speeds (MHz): 1: 952 2: 980 Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: ASUSTeK driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0106 Display: x11 server: X.Org 1.20.4 driver: intel resolution: 1366x768~60Hz OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 19.3.1 - kisak-mesa PPA compat-v: 3.0 direct render: Yes Audio: Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1e20 Sound Server: ALSA v: k5.3.0-24-generic Network: Device-1: Qualcomm Atheros AR9485 Wireless Network Adapter vendor: AzureWave driver: ath9k v: kernel port: f060 bus ID: 02:00.0 chip ID: 168c:0032 IF: wlp2s0 state: up mac: <filter> Device-2: Qualcomm Atheros AR8161 Gigabit Ethernet vendor: ASUSTeK driver: alx v: kernel port: e000 bus ID: 03:00.0 chip ID: 1969:1091 IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: <filter> Device-3: IMC Networks Atheros AR3012 Bluetooth 4.0 Adapter type: USB driver: btusb bus ID: 1-1.1:5 chip ID: 13d3:3362 Drives: Local Storage: total: 149.05 GiB used: 27.45 GiB (18.4%) ID-1: /dev/sda vendor: Seagate model: ST9160314AS size: 149.05 GiB speed: 3.0 Gb/s serial: <filter> Partition: ID-1: / size: 145.71 GiB used: 27.45 GiB (18.8%) fs: ext4 dev: /dev/sda1 Sensors: System Temperatures: cpu: 70.0 C mobo: N/A Fan Speeds (RPM): cpu: 25500 Info: Processes: 191 Uptime: 1h 01m Memory: 3.55 GiB used: 1.62 GiB (45.8%) Init: systemd v: 237 runlevel: 5 Compilers: gcc: 7.4.0 alt: 7 Shell: bash v: 4.4.20 running in: gnome-terminal inxi: 3.0.32
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: Butterfly - 31 Aralık 2019, 19:52:35: Bu konuda sadece yavaş açılma ile ilgili sorunu konuşalım. Diğer sorun bundan farklı bir husus olduğu için, bu konudan ayrı olarak yeni bir konu açabilirsiniz. Forumda aynı başlıkta farklı soru ya da sorunlar hakkında konuşmuyoruz. Konu başlığını bu duruma göre güncelledim.

Yavaş açılma sorunu ile ilgili olarak, aşağıdaki komutların çıktılarını da paylaşınız. İlk komutun çıktısı için internet bağlantınızın olması gerekecek.

Kod: [Seç]
dmesg | nc termbin.com 9999
Kod: [Seç]
systemd-analyze time
Kod: [Seç]
systemd-analyze --no-pager blame
Kod: [Seç]
systemd-analyze --no-pager critical-chain
Kod: [Seç]
journalctl --no-pager -b -p3
Kod: [Seç]
systemctl --no-pager --state=failed
Kod: [Seç]
cat /etc/fstab
Kod: [Seç]
sudo blkid
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: sebastianhawk - 31 Aralık 2019, 20:47:06: Sorunumla uğraştığınız için çok teşekkür ederim.Buyrun ;
Kod: [Seç]
https://termbin.com/5jt1
Kod: [Seç]
Startup finished in 50.597s (kernel) + 53.140s (userspace) = 1min 43.738s graphical.target reached after 53.119s in userspace
Kod: [Seç]
25.586s ModemManager.service 23.645s dev-sda1.device 21.995s networkd-dispatcher.service 19.738s accounts-daemon.service 19.650s udisks2.service 16.926s networking.service 14.674s grub-common.service 13.497s lightdm.service 13.493s plymouth-quit-wait.service 12.985s avahi-daemon.service 12.985s thermald.service 12.281s kerneloops.service 12.029s NetworkManager.service 11.980s lm-sensors.service 11.933s gpu-manager.service 11.820s pppd-dns.service 11.640s zram-config.service 11.635s rsyslog.service 11.460s systemd-logind.service 10.412s ubuntu-system-adjustments.service 7.536s ufw.service 6.311s wpa_supplicant.service 6.040s systemd-udevd.service 5.572s apparmor.service 5.387s polkit.service 4.622s systemd-journal-flush.service 4.334s lvm2-monitor.service 3.478s systemd-tmpfiles-setup-dev.service 2.897s systemd-tmpfiles-setup.service 2.645s dns-clean.service 1.918s preload.service 1.840s systemd-modules-load.service 1.668s keyboard-setup.service 1.556s apt-daily.service 1.487s systemd-sysctl.service 1.334s user@1000.service 1.264s bluetooth.service 1.067s swapfile.swap 1.063s speech-dispatcher.service 1.026s systemd-backlight@backlight:intel_backlight.service 1.005s systemd-random-seed.service 994ms dev-zram1.device 994ms dev-zram0.device 978ms systemd-rfkill.service 801ms systemd-journald.service 749ms plymouth-read-write.service 733ms systemd-user-sessions.service 485ms systemd-resolved.service 457ms systemd-timesyncd.service 447ms systemd-remount-fs.service 415ms sys-kernel-debug.mount 414ms dev-mqueue.mount 414ms kmod-static-nodes.service 394ms hddtemp.service 374ms upower.service 370ms systemd-udev-trigger.service 309ms dev-hugepages.mount 308ms console-setup.service 307ms blk-availability.service 223ms setvtrgb.service 186ms systemd-tmpfiles-clean.service 182ms plymouth-start.service 124ms packagekit.service 108ms systemd-update-utmp.service 21ms motd-news.service 16ms ureadahead-stop.service 15ms colord.service 8ms systemd-update-utmp-runlevel.service 6ms sys-kernel-config.mount 5ms sys-fs-fuse-connections.mount 5ms openvpn.service 4ms rtkit-daemon.service
Kod: [Seç]
The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @53.119s └─multi-user.target @53.119s └─getty.target @53.118s └─getty@tty1.service @53.118s └─system-getty.slice @53.116s └─setvtrgb.service @52.891s +223ms └─systemd-user-sessions.service @38.658s +733ms └─network.target @38.653s └─NetworkManager.service @26.623s +12.029s └─dbus.service @15.874s └─basic.target @15.103s └─sockets.target @15.103s └─cups.socket @15.102s └─sysinit.target @14.775s └─systemd-backlight@backlight:intel_backlight.service @28.441s +1.026s └─system-systemd\x2dbacklight.slice @28.439s └─system.slice @4.649s └─-.slice @4.612s
Kod: [Seç]
-- Logs begin at Sun 2018-01-28 18:58:22 +03, end at Tue 2019-12-31 20:43:52 +03. -- Ara 31 17:29:03 SEBASTIAN kernel: mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 1) Ara 31 17:29:03 SEBASTIAN kernel: ACPI Error: Needed type [Reference], found [Integer] (____ptrval____) (20190703/exresop-69) Ara 31 17:29:03 SEBASTIAN kernel: ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Store] (20190703/dswexec-427) Ara 31 17:29:03 SEBASTIAN kernel: ACPI Error: Aborting method \_PR.CPU0._PDC due to previous error (AE_AML_OPERAND_TYPE) (20190703/psparse-531) Ara 31 17:29:31 SEBASTIAN bluetoothd[933]: Failed to set mode: Blocked through rfkill (0x12) Ara 31 17:29:48 SEBASTIAN wpa_supplicant[868]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none Ara 31 17:29:48 SEBASTIAN wpa_supplicant[868]: dbus: Failed to construct signal Ara 31 17:30:05 SEBASTIAN pulseaudio[2006]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Ara 31 17:30:06 SEBASTIAN pulseaudio[2054]: [pulseaudio] pid.c: Daemon already running. Ara 31 17:30:14 SEBASTIAN bluetoothd[933]: Failed to set mode: Blocked through rfkill (0x12) Ara 31 17:31:30 SEBASTIAN sudo[4041]: sebastian : a password is required ; TTY=unknown ; PWD=/home/sebastian ; USER=root ; COMMAND=/usr/sbin/hddtemp -nq -u C /dev/sda Ara 31 17:33:15 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 526) Ara 31 17:33:15 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 524) Ara 31 17:36:11 SEBASTIAN kernel: INFO: task kworker/u4:1:33 blocked for more than 120 seconds. Ara 31 17:36:11 SEBASTIAN kernel: Not tainted 5.3.0-24-generic #26~18.04.2-Ubuntu Ara 31 17:36:11 SEBASTIAN kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Ara 31 17:38:12 SEBASTIAN kernel: INFO: task kworker/u4:1:33 blocked for more than 241 seconds. Ara 31 17:38:12 SEBASTIAN kernel: Not tainted 5.3.0-24-generic #26~18.04.2-Ubuntu Ara 31 17:38:12 SEBASTIAN kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Ara 31 17:39:40 SEBASTIAN kernel: mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 3264) Ara 31 17:39:40 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 16940) Ara 31 17:39:40 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 16942) Ara 31 17:40:13 SEBASTIAN kernel: INFO: task kworker/u4:1:33 blocked for more than 362 seconds. Ara 31 17:40:13 SEBASTIAN kernel: Not tainted 5.3.0-24-generic #26~18.04.2-Ubuntu Ara 31 17:40:13 SEBASTIAN kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Ara 31 17:42:14 SEBASTIAN kernel: INFO: task kworker/u4:1:33 blocked for more than 483 seconds. Ara 31 17:42:14 SEBASTIAN kernel: Not tainted 5.3.0-24-generic #26~18.04.2-Ubuntu Ara 31 17:42:14 SEBASTIAN kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Ara 31 17:44:15 SEBASTIAN kernel: INFO: task kworker/u4:1:33 blocked for more than 604 seconds. Ara 31 17:44:15 SEBASTIAN kernel: Not tainted 5.3.0-24-generic #26~18.04.2-Ubuntu Ara 31 17:44:15 SEBASTIAN kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Ara 31 17:46:16 SEBASTIAN kernel: INFO: task kworker/u4:1:33 blocked for more than 724 seconds. Ara 31 17:46:16 SEBASTIAN kernel: Not tainted 5.3.0-24-generic #26~18.04.2-Ubuntu Ara 31 17:46:16 SEBASTIAN kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Ara 31 17:48:16 SEBASTIAN kernel: INFO: task kworker/u4:1:33 blocked for more than 845 seconds. Ara 31 17:48:16 SEBASTIAN kernel: Not tainted 5.3.0-24-generic #26~18.04.2-Ubuntu Ara 31 17:48:16 SEBASTIAN kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Ara 31 17:50:17 SEBASTIAN kernel: INFO: task kworker/u4:1:33 blocked for more than 966 seconds. Ara 31 17:50:17 SEBASTIAN kernel: Not tainted 5.3.0-24-generic #26~18.04.2-Ubuntu Ara 31 17:50:17 SEBASTIAN kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Ara 31 17:52:18 SEBASTIAN kernel: mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 3410) Ara 31 17:52:18 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 17096) Ara 31 17:52:18 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 17098) Ara 31 17:52:18 SEBASTIAN kernel: INFO: task kworker/u4:1:33 blocked for more than 1087 seconds. Ara 31 17:52:18 SEBASTIAN kernel: Not tainted 5.3.0-24-generic #26~18.04.2-Ubuntu Ara 31 17:52:18 SEBASTIAN kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Ara 31 17:54:19 SEBASTIAN kernel: INFO: task kworker/u4:1:33 blocked for more than 1208 seconds. Ara 31 17:54:19 SEBASTIAN kernel: Not tainted 5.3.0-24-generic #26~18.04.2-Ubuntu Ara 31 17:54:19 SEBASTIAN kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Ara 31 17:57:18 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 24708) Ara 31 17:57:18 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 24708) Ara 31 18:01:48 SEBASTIAN kernel: blk_update_request: I/O error, dev sda, sector 13925699 op 0x0:(READ) flags 0x80700 phys_seg 7 prio class 0 Ara 31 18:01:53 SEBASTIAN kernel: blk_update_request: I/O error, dev sda, sector 13925699 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Ara 31 18:01:53 SEBASTIAN kernel: blk_update_request: I/O error, dev sda, sector 13925699 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Ara 31 18:02:06 SEBASTIAN kernel: blk_update_request: I/O error, dev sda, sector 13925699 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Ara 31 18:02:09 SEBASTIAN kernel: blk_update_request: I/O error, dev sda, sector 13925699 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Ara 31 18:02:18 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 29724) Ara 31 18:02:19 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 29725) Ara 31 18:05:26 SEBASTIAN wpa_supplicant[868]: Using interface wlp2s0 with hwaddr dc:85:de:9b:e6:c3 and ssid "SEBASTIAN" Ara 31 18:08:12 SEBASTIAN kernel: mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 6370) Ara 31 18:08:12 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 32978) Ara 31 18:08:15 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 32977) Ara 31 18:13:18 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 33301) Ara 31 18:13:18 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 33302) Ara 31 18:18:18 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 34083) Ara 31 18:18:18 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 34084) Ara 31 18:25:03 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 35957) Ara 31 18:25:03 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 35958) Ara 31 18:29:24 SEBASTIAN sudo[8870]: sebastian : a password is required ; TTY=pts/0 ; PWD=/home/sebastian ; USER=root ; COMMAND=/usr/sbin/hddtemp -nq -u C /dev/sda Ara 31 18:31:11 SEBASTIAN kernel: mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 7647) Ara 31 18:31:11 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 40039) Ara 31 18:31:11 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 40038) Ara 31 18:36:54 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 40743) Ara 31 18:36:54 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 40742) Ara 31 18:41:55 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 47197) Ara 31 18:41:55 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 47196) Ara 31 18:42:07 SEBASTIAN kernel: mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 9535) Ara 31 19:02:35 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 49622) Ara 31 19:02:35 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 49621) Ara 31 19:08:16 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 66193) Ara 31 19:08:16 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 66193) Ara 31 19:13:28 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 72111) Ara 31 19:13:28 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 72111) Ara 31 19:19:04 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 76278) Ara 31 19:19:04 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 76278) Ara 31 19:20:45 SEBASTIAN kernel: mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 16848) Ara 31 19:26:07 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 79252) Ara 31 19:26:07 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 79252) Ara 31 19:40:39 SEBASTIAN kernel: mce: CPU1: Core temperature above threshold, cpu clock throttled (total events = 8613) Ara 31 19:40:39 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 82173) Ara 31 19:40:39 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 82173) Ara 31 19:45:39 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 87721) Ara 31 19:45:39 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 87721)
Kod: [Seç]
0 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'.
Kod: [Seç]
# /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sda1 during installation UUID=c99d2dd2-bbaa-4a7e-a914-325bdb762d35 / ext4 errors=remount-ro 0 1 /swapfile none swap sw 0 0
Kod: [Seç]
/dev/sda1: UUID="c99d2dd2-bbaa-4a7e-a914-325bdb762d35" TYPE="ext4" PARTUUID="b4d9d050-01" /dev/zram0: UUID="9bf1a3cd-02bc-4bf0-bbc6-8b0197174d58" TYPE="swap" /dev/zram1: UUID="67c39678-8ae4-41da-a394-c805a162235b" TYPE="swap"
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: Butterfly - 31 Aralık 2019, 23:29:48: Alıntı
[ 5.834047] Btrfs loaded, crc32c=crc32c-intel
[ 41.342131] random: crng init done

Aşağıdaki komutla rng-tools paketini kurup,

Kod: [Seç]
sudo apt install rng-tools
ardından aşağıdaki komutu çalıştırmayı dener misiniz?

Kod: [Seç]
sudo update-initramfs -u
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: sebastianhawk - 01 Ocak 2020, 00:21:05: Çalıştırdım ve kod çıktısı ;
Kod: [Seç]
update-initramfs: Generating /boot/initrd.img-5.3.0-24-generic I: The initramfs will attempt to resume from /dev/zram1 I: (UUID=67c39678-8ae4-41da-a394-c805a162235b) I: Set the RESUME variable to override this.
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: Butterfly - 01 Ocak 2020, 00:48:27: Çıktı paylaşmanıza gerek yoktu. Gerektiğinde çıktı paylaşmanızı ayrıca belirtiyoruz. Sadece sistemi yeniden başlatıp durumu gözlemleyiniz.
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: sebastianhawk - 01 Ocak 2020, 01:54:39: Link paylaşmak kural ihlali mi bilmiyorum ama sorun hala devam ediyor.
Kod: [Seç]
https://i.hizliresim.com/86Bmnd.png
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: Butterfly - 01 Ocak 2020, 12:36:13: Paylaştığınız resimdeki husus, doğrudan açılış ile ilgili değil. Cinnamon masaüstü eklentileri ile ilgili husus için yeni bir konu açabilirsiniz.

Bu konuya yavaş açılma sorunu çerçevesinde devam edelim. Aşağıdaki komutların çıktısını son duruma göre yeniden paylaşınız. Değişen bir şey olmuş mu kontrol edelim.

Kod: [Seç]
systemd-analyze time
Kod: [Seç]
systemd-analyze --no-pager blame
Kod: [Seç]
systemd-analyze --no-pager critical-chain
Kod: [Seç]
sudo cat /var/log/boot.log | nc termbin.com 9999
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: sebastianhawk - 01 Ocak 2020, 17:39:12: Kod: [Seç]
Startup finished in 40.180s (kernel) + 55.670s (userspace) = 1min 35.850s graphical.target reached after 55.659s in userspace
Kod: [Seç]
16.450s dev-sda1.device 15.238s udisks2.service 14.795s lightdm.service 14.791s plymouth-quit-wait.service 14.271s systemd-journal-flush.service 13.122s ubuntu-system-adjustments.service 12.392s ModemManager.service 12.022s networkd-dispatcher.service 11.682s NetworkManager.service 8.768s accounts-daemon.service 8.462s preload.service 7.503s gpu-manager.service 6.874s ufw.service 6.748s grub-common.service 6.735s rsyslog.service 6.209s wpa_supplicant.service 6.160s apparmor.service 6.092s lm-sensors.service 5.980s avahi-daemon.service 5.980s thermald.service 5.894s systemd-udevd.service 5.560s apt-daily-upgrade.service 5.380s apt-daily.service 4.138s networking.service 3.975s lvm2-monitor.service 3.721s zram-config.service 3.659s polkit.service 3.133s systemd-tmpfiles-setup-dev.service 3.080s systemd-tmpfiles-setup.service 2.806s bluetooth.service 2.106s keyboard-setup.service 2.024s dns-clean.service 1.982s systemd-logind.service 1.785s systemd-modules-load.service 1.656s rng-tools.service 1.637s speech-dispatcher.service 1.402s systemd-sysctl.service 1.357s hddtemp.service 1.334s kerneloops.service 1.327s pppd-dns.service 1.068s systemd-random-seed.service 908ms systemd-rfkill.service 894ms swapfile.swap 677ms kmod-static-nodes.service 675ms dev-mqueue.mount 674ms blk-availability.service 671ms sys-kernel-debug.mount 671ms systemd-journald.service 651ms alsa-restore.service 488ms user@1000.service 452ms upower.service 340ms dev-hugepages.mount 317ms console-setup.service 314ms systemd-backlight@backlight:intel_backlight.service 294ms systemd-timesyncd.service 237ms systemd-tmpfiles-clean.service 220ms systemd-remount-fs.service 213ms systemd-resolved.service 212ms setvtrgb.service 181ms packagekit.service 152ms colord.service 87ms systemd-udev-trigger.service 86ms systemd-user-sessions.service 64ms systemd-update-utmp.service 14ms plymouth-start.service 12ms ureadahead-stop.service 12ms plymouth-read-write.service 8ms systemd-update-utmp-runlevel.service 6ms motd-news.service 5ms sys-fs-fuse-connections.mount 4ms rtkit-daemon.service 3ms sys-kernel-config.mount 2ms openvpn.service
Kod: [Seç]
The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @55.659s └─multi-user.target @55.659s └─getty.target @55.659s └─getty@tty1.service @55.658s └─system-getty.slice @55.656s └─setvtrgb.service @55.443s +212ms └─systemd-user-sessions.service @40.559s +86ms └─network.target @40.554s └─NetworkManager.service @28.871s +11.682s └─dbus.service @23.548s └─basic.target @23.434s └─sockets.target @23.434s └─cups.socket @23.434s └─sysinit.target @23.249s └─systemd-timesyncd.service @22.954s +294ms └─systemd-tmpfiles-setup.service @19.777s +3.080s └─systemd-journal-flush.service @5.504s +14.271s └─systemd-remount-fs.service @5.281s +220ms └─systemd-journald.socket @4.605s └─system.slice @4.605s └─-.slice @4.579s
Kod: [Seç]
https://termbin.com/18j8
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: Butterfly - 01 Ocak 2020, 18:38:03: Alıntı
Startup finished in 40.180s (kernel)

Çekirdek başlatma süresi pek kısalmamış, aşağıdaki komutla haveged paketini kurup sistemi yeniden başlatmayı deneyiniz.

Kod: [Seç]
sudo apt install haveged sudo systemctl enable haveged
Sistemi yeniden başlattıktan sonra aşağıdaki komutların çıktılarını paylaşırsınız.

Kod: [Seç]
dmesg | nc termbin.com 9999 systemd-analyze time cat /etc/initramfs-tools/conf.d/resume

Cinnamon masaüstündeki sorun için yeni konu açabilirsiniz. Cinnamon masaüstü ile ilgili husus, bu konudan bağımsız çözümlenebilir.
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: sebastianhawk - 02 Ocak 2020, 00:43:00: Kod: [Seç]
https://termbin.com/b90n
Kod: [Seç]
Startup finished in 39.601s (kernel) + 54.877s (userspace) = 1min 34.479s graphical.target reached after 54.865s in userspace
Kod: [Seç]
cat: /etc/initramfs-tools/conf.d/resume: Böyle bir dosya ya da dizin yok (conf.d klasörüne baktım herhangi bir dosya yok)
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: Butterfly - 02 Ocak 2020, 17:13:06: Güncelleme Yöneticisi => Görünüm menüsü => Linux çekirdekleri aracı ile, Linux çekirdeğinin 4.15.x serisinin son sürümünü kurup, ardından sistemi burada (https://forum.linuxmint.net.tr/index.php?topic=9944.0) bahsedildiği gibi 4.15.x sürüm çekirdekle açmayı dener misiniz?

Sistemi 4.15.x sürüm çekirdekle açıp, aşağıdaki komutun çıktısını yeniden paylaşınız. Böylece sorunun çekirdek serisi/sürümü ile ilgili olma olasılığını değerlendirebiliriz.

Kod: [Seç]
systemd-analyze time
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: sebastianhawk - 02 Ocak 2020, 18:43:19: Kod: [Seç]
Startup finished in 40.350s (kernel) + 39.333s (userspace) = 1min 19.684s graphical.target reached after 39.310s in userspace
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: Butterfly - 02 Ocak 2020, 21:06:03: Sistemi 4.15.x serisi çekirdekle açtınız değil mi? Aşağıdaki komutla kontrol edilebilir.

Kod: [Seç]
uname -r
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: sebastianhawk - 02 Ocak 2020, 23:23:50: Evet hatta 4.15.0-72-generic ile açtım.
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: Butterfly - 03 Ocak 2020, 14:37:55: Aşağıdaki komutları uçbirimde çalıştırıp, sistemi yeniden başlatmayı deneyiniz.

Kod: [Seç]
echo -e 'RESUME=none' | sudo tee /etc/initramfs-tools/conf.d/resume
Kod: [Seç]
sudo update-initramfs -u
Ardından aşağıdaki komutun çıktısına bir daha bakalım. Komutun çıktısı, açılış sürecinde değişiklik olup olmadığını anlamamızı sağlıyor.

Kod: [Seç]
systemd-analyze time
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: sebastianhawk - 03 Ocak 2020, 16:52:30: Kod: [Seç]
Startup finished in 7.124s (kernel) + 1min 6.539s (userspace) = 1min 13.664s graphical.target reached after 1min 6.528s in userspace
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: Butterfly - 03 Ocak 2020, 17:00:12: Alıntı
Öncesi
Startup finished in 40.350s (kernel) + 39.333s (userspace) = 1min 19.684s
Şimdi
Startup finished in 7.124s (kernel) + 1min 6.539s (userspace) = 1min 13.664s

Şu an çekirdek ile ilgili gecikme sorunu çözülmüş görünüyor. Şimdi Systemd ile ilgili hususlara bakalım. Bunun için aşağıdaki komutların çıktıarını paylaşınız.

Kod: [Seç]
systemd-analyze --no-pager blame
Kod: [Seç]
systemd-analyze --no-pager critical-chain
Kod: [Seç]
journalctl --no-pager -b -p3
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: sebastianhawk - 03 Ocak 2020, 19:07:44: Kod: [Seç]
29.696s networkd-dispatcher.service 27.132s dev-sda1.device 25.245s udisks2.service 22.624s ModemManager.service 22.335s networking.service 17.289s NetworkManager.service 14.623s speech-dispatcher.service 14.550s preload.service 12.808s hddtemp.service 12.783s lm-sensors.service 12.421s rng-tools.service 11.891s accounts-daemon.service 11.039s lightdm.service 11.034s plymouth-quit-wait.service 10.534s wpa_supplicant.service 8.723s thermald.service 8.117s ufw.service 7.758s rsyslog.service 6.841s gpu-manager.service 6.575s ubuntu-system-adjustments.service 6.341s apparmor.service 6.340s systemd-udevd.service 4.811s zram-config.service 4.700s systemd-journal-flush.service 4.283s lvm2-monitor.service 4.278s grub-common.service 4.255s bluetooth.service 4.054s avahi-daemon.service 3.442s systemd-tmpfiles-setup-dev.service 3.211s systemd-logind.service 2.843s dns-clean.service 2.837s systemd-rfkill.service 2.467s systemd-modules-load.service 2.456s systemd-tmpfiles-setup.service 2.325s polkit.service 2.052s systemd-sysctl.service 1.923s keyboard-setup.service 1.151s kmod-static-nodes.service 1.146s systemd-journald.service 958ms pppd-dns.service 804ms systemd-backlight@backlight:intel_backlight.service 727ms user@1000.service 694ms kerneloops.service 679ms plymouth-read-write.service 603ms swapfile.swap 575ms console-setup.service 534ms systemd-random-seed.service 494ms systemd-resolved.service 379ms alsa-restore.service 376ms upower.service 355ms systemd-tmpfiles-clean.service 334ms systemd-remount-fs.service 320ms systemd-timesyncd.service 303ms plymouth-start.service 294ms systemd-update-utmp.service 282ms dev-mqueue.mount 255ms blk-availability.service 181ms setvtrgb.service 155ms packagekit.service 88ms systemd-udev-trigger.service 32ms systemd-user-sessions.service 21ms colord.service 11ms ureadahead-stop.service 9ms systemd-update-utmp-runlevel.service 7ms dev-hugepages.mount 6ms sys-kernel-debug.mount 5ms openvpn.service 5ms sys-fs-fuse-connections.mount 4ms rtkit-daemon.service 2ms sys-kernel-config.mount
Kod: [Seç]
graphical.target @56.735s └─multi-user.target @56.735s └─getty.target @56.735s └─getty@tty1.service @56.734s └─system-getty.slice @56.732s └─setvtrgb.service @56.549s +181ms └─systemd-user-sessions.service @45.476s +32ms └─network.target @45.474s └─NetworkManager.service @28.183s +17.289s └─dbus.service @15.875s └─basic.target @15.763s └─systemd-ask-password-plymouth.path @15.763s └─-.mount @4.260s └─system.slice @4.296s └─-.slice @4.260s
Kod: [Seç]
-- Logs begin at Sun 2018-01-28 18:58:22 +03, end at Fri 2020-01-03 19:06:41 +03. -- Oca 28 18:58:22 SEBASTIAN kernel: ACPI Error: Needed type [Reference], found [Integer] (____ptrval____) (20190703/exresop-69) Oca 28 18:58:22 SEBASTIAN kernel: ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Store] (20190703/dswexec-427) Oca 28 18:58:22 SEBASTIAN kernel: ACPI Error: Aborting method \_PR.CPU0._PDC due to previous error (AE_AML_OPERAND_TYPE) (20190703/psparse-531) Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: read error Oca 03 16:53:23 SEBASTIAN rngd[616]: No entropy sources working, exiting rngd Oca 03 16:53:44 SEBASTIAN bluetoothd[864]: Failed to set mode: Blocked through rfkill (0x12) Oca 03 16:54:00 SEBASTIAN wpa_supplicant[784]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none Oca 03 16:54:00 SEBASTIAN wpa_supplicant[784]: dbus: Failed to construct signal Oca 03 16:54:17 SEBASTIAN pulseaudio[1934]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Oca 03 16:54:17 SEBASTIAN pulseaudio[1965]: [pulseaudio] pid.c: Daemon already running. Oca 03 16:54:25 SEBASTIAN bluetoothd[864]: Failed to set mode: Blocked through rfkill (0x12) Oca 03 18:40:19 SEBASTIAN kernel: mce: CPU1: Core temperature above threshold, cpu clock throttled (total events = 1) Oca 03 18:40:19 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 1) Oca 03 18:40:19 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 1) Oca 03 18:45:19 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 46549) Oca 03 18:45:19 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 46551) Oca 03 18:50:19 SEBASTIAN kernel: mce: CPU1: Core temperature above threshold, cpu clock throttled (total events = 82951) Oca 03 18:50:19 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 94871) Oca 03 18:50:19 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 94875) Oca 03 18:55:19 SEBASTIAN kernel: mce: CPU1: Core temperature above threshold, cpu clock throttled (total events = 123631) Oca 03 18:55:19 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 138143) Oca 03 18:55:19 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 138145) Oca 03 19:00:19 SEBASTIAN kernel: mce: CPU1: Core temperature above threshold, cpu clock throttled (total events = 168069) Oca 03 19:00:19 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 186078) Oca 03 19:00:19 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 186077) Oca 03 19:02:10 SEBASTIAN kernel: blk_update_request: I/O error, dev sda, sector 13925699 op 0x0:(READ) flags 0x80700 phys_seg 9 prio class 0 Oca 03 19:02:13 SEBASTIAN kernel: blk_update_request: I/O error, dev sda, sector 13925699 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Oca 03 19:02:15 SEBASTIAN kernel: blk_update_request: I/O error, dev sda, sector 13925699 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Oca 03 19:02:24 SEBASTIAN kernel: blk_update_request: I/O error, dev sda, sector 13925699 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Oca 03 19:02:27 SEBASTIAN kernel: blk_update_request: I/O error, dev sda, sector 13925699 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0Dipnot: Bugün bilgisayarcıya götürüp termal macun ve fan temizliği yaptırdım.
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: Butterfly - 03 Ocak 2020, 19:18:32: Alıntı
└─systemd-ask-password-plymouth.path @15.763s

Şifrelenmiş disk bölümümü kullanıyorsunuz.
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: sebastianhawk - 03 Ocak 2020, 20:18:11: Ne kullandığımı bilmiyorum daha önce Windows yüklüydü yanına kurmak istedim ama bir türlü beceremedim bende Windowsu kaldırıp Linuxu kurdum.Belki dediğiniz şey windowstan kalma bir şey olabilir.Cidden ne olduğunu bilmiyorum.
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: Butterfly - 03 Ocak 2020, 20:37:42: Açılış sırasında size giriş parolası haricinde bir parola soruluyor mu? Bunun Windows ile ilgili bulunmuyor. Kurulum sırasında disk bölümünün şifrelenmesi ile ilgili bir seçenek seçip seçmediğiniz ile alakalı bir durum.
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: sebastianhawk - 04 Ocak 2020, 03:45:30: Açılış sırasında bir parola soruyor fakat ben o kısma parola bile girmeden direkt giriş yapıyor.Başka da bir parola sorulmuyor.Ayrıca öyle bir seçenek seçtiğimi hatırlamıyorum.
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: Butterfly - 05 Ocak 2020, 00:51:46: Aşağıdaki komutla, daha önce kurmanızı önerdiğim rng-tools paketini kaldırıp,

Kod: [Seç]
sudo apt purge rng-tools
Sistemi yeniden başlatınız ve aşağıdaki komutların çıktısını yeniden paylaşınız.

Kod: [Seç]
dmesg | nc termbin.com 9999
Kod: [Seç]
journalctl -b --no-pager | nc termbin.com 9999
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: sebastianhawk - 05 Ocak 2020, 13:47:52: Kod: [Seç]
https://termbin.com/mr58
Kod: [Seç]
https://termbin.com/qh0bc
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: Butterfly - 05 Ocak 2020, 22:43:10: Alıntı
[ 36.520514] Bluetooth: BNEP socket layer initialized
[ 49.844584] alx 0000:03:00.0 enp3s0: NIC Up: 100 Mbps Full
[ 49.844815] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
[ 73.880978] Bluetooth: RFCOMM TTY layer initialized

Bluetooth aygıtını pasifleştirip, sistemi bu şekilde başlatınca durum ne oluyor? Bluetooth aygıtı pasif olduğu halde sistemi başlattıktan sonra, aşağıdaki komutun çıktısı ile açılış süresine bakalım.

Kod: [Seç]
systemd-analyze
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: sebastianhawk - 05 Ocak 2020, 23:03:15: Kod: [Seç]
Startup finished in 7.140s (kernel) + 59.516s (userspace) = 1min 6.657s graphical.target reached after 59.506s in userspace
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: Butterfly - 06 Ocak 2020, 22:56:31: Açılış süresi bir miktar azalmış görünüyor. Aşağıdaki komutların çıktılarına yeniden bakalım. Buna göre farklı öneriler sunabiliriz.

Kod: [Seç]
systemd-analyze --no-pager blame systemd-analyze --no-pager critical-chain journalctl --no-pager -b -p3 dmesg | nc termbin.com 9999
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: sebastianhawk - 06 Ocak 2020, 23:27:21: Kod: [Seç]
25.638s ModemManager.service 20.860s networkd-dispatcher.service 19.453s dev-sda1.device 18.326s systemd-journal-flush.service 17.545s udisks2.service 16.928s NetworkManager.service 16.742s accounts-daemon.service 8.652s systemd-resolved.service 8.057s apparmor.service 8.008s grub-common.service 7.796s systemd-udevd.service 7.759s ubuntu-system-adjustments.service 7.707s ufw.service 7.288s polkit.service 7.151s networking.service 6.895s lightdm.service 6.890s plymouth-quit-wait.service 6.657s preload.service 5.967s wpa_supplicant.service 5.732s systemd-logind.service 5.688s avahi-daemon.service 5.686s bluetooth.service 5.685s zram-config.service 5.681s thermald.service 5.675s hddtemp.service 5.644s pppd-dns.service 5.204s rsyslog.service 5.012s gpu-manager.service 4.581s lm-sensors.service 3.856s lvm2-monitor.service 3.077s systemd-tmpfiles-setup-dev.service 2.967s dnsmasq.service 2.939s dns-clean.service 2.588s systemd-timesyncd.service 1.763s keyboard-setup.service 1.700s systemd-sysctl.service 1.645s systemd-tmpfiles-setup.service 1.631s systemd-modules-load.service 1.136s user@1000.service 1.001s systemd-random-seed.service 953ms swapfile.swap 702ms systemd-udev-trigger.service 670ms systemd-rfkill.service 635ms dev-mqueue.mount 631ms systemd-journald.service 586ms systemd-backlight@backlight:intel_backlight.service 568ms systemd-update-utmp.service 544ms systemd-remount-fs.service 523ms blk-availability.service 520ms dev-hugepages.mount 520ms sys-kernel-debug.mount 497ms kmod-static-nodes.service 398ms console-setup.service 290ms speech-dispatcher.service 282ms kerneloops.service 249ms upower.service 209ms setvtrgb.service 141ms systemd-tmpfiles-clean.service 137ms packagekit.service 121ms systemd-user-sessions.service 97ms motd-news.service 26ms dev-zram0.device 24ms alsa-restore.service 22ms dev-zram1.device 21ms colord.service 15ms plymouth-start.service 11ms plymouth-read-write.service 8ms systemd-update-utmp-runlevel.service 7ms ureadahead-stop.service 6ms rtkit-daemon.service 6ms openvpn.service 4ms sys-kernel-config.mount 3ms sys-fs-fuse-connections.mount
Kod: [Seç]
graphical.target @58.463s └─multi-user.target @58.463s └─getty.target @58.463s └─getty@tty1.service @58.462s └─system-getty.slice @58.460s └─setvtrgb.service @58.249s +209ms └─systemd-user-sessions.service @51.230s +121ms └─network.target @51.221s └─NetworkManager.service @34.292s +16.928s └─dbus.service @29.821s └─basic.target @28.557s └─paths.target @28.557s └─cups.path @28.557s └─sysinit.target @28.242s └─systemd-timesyncd.service @25.653s +2.588s └─systemd-tmpfiles-setup.service @23.812s +1.645s └─systemd-journal-flush.service @5.482s +18.326s └─systemd-remount-fs.service @4.935s +544ms └─systemd-journald.socket @4.507s └─system.slice @4.506s └─-.slice @4.460s
Kod: [Seç]
-- Logs begin at Sun 2018-01-28 18:58:22 +03, end at Mon 2020-01-06 23:26:44 +03. -- Oca 06 20:38:16 SEBASTIAN kernel: ACPI Error: Needed type [Reference], found [Integer] (____ptrval____) (20190703/exresop-69) Oca 06 20:38:16 SEBASTIAN kernel: ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Store] (20190703/dswexec-427) Oca 06 20:38:16 SEBASTIAN kernel: ACPI Error: Aborting method \_PR.CPU0._PDC due to previous error (AE_AML_OPERAND_TYPE) (20190703/psparse-531) Oca 06 20:38:48 SEBASTIAN bluetoothd[841]: Failed to set mode: Blocked through rfkill (0x12) Oca 06 20:39:06 SEBASTIAN dnsmasq[1604]: failed to create listening socket for port 53: Adres zaten kullanımda Oca 06 20:39:06 SEBASTIAN dnsmasq[1604]: FAILED to start up Oca 06 20:39:06 SEBASTIAN systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. Oca 06 20:39:08 SEBASTIAN wpa_supplicant[931]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none Oca 06 20:39:08 SEBASTIAN wpa_supplicant[931]: dbus: Failed to construct signal Oca 06 20:39:29 SEBASTIAN pulseaudio[2554]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Oca 06 20:39:29 SEBASTIAN pulseaudio[2581]: [pulseaudio] pid.c: Daemon already running. Oca 06 21:40:28 SEBASTIAN kernel: mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 1) Oca 06 21:40:28 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 1) Oca 06 21:40:28 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 1) Oca 06 21:45:28 SEBASTIAN kernel: mce: CPU1: Core temperature above threshold, cpu clock throttled (total events = 3516) Oca 06 21:45:28 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 5166) Oca 06 21:45:28 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 5166) Oca 06 21:53:19 SEBASTIAN kernel: mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 4455) Oca 06 21:53:19 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 8955) Oca 06 21:53:19 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 8955) Oca 06 21:58:19 SEBASTIAN kernel: mce: CPU1: Core temperature above threshold, cpu clock throttled (total events = 16549) Oca 06 21:58:19 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 23696) Oca 06 21:58:19 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 23696) Oca 06 22:03:19 SEBASTIAN kernel: mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 13222) Oca 06 22:03:20 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 33007) Oca 06 22:03:20 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 33007) Oca 06 22:10:13 SEBASTIAN kernel: mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 16067) Oca 06 22:10:13 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 40714) Oca 06 22:10:13 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 40714) Oca 06 22:15:29 SEBASTIAN kernel: mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 18214) Oca 06 22:15:29 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 46061) Oca 06 22:15:29 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 46061) Oca 06 22:21:27 SEBASTIAN kernel: mce: CPU1: Core temperature above threshold, cpu clock throttled (total events = 34055) Oca 06 22:21:27 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 50181) Oca 06 22:21:27 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 50181) Oca 06 22:29:01 SEBASTIAN kernel: mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 23146) Oca 06 22:29:01 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 57243) Oca 06 22:29:01 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 57244) Oca 06 22:34:07 SEBASTIAN kernel: mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 39307) Oca 06 22:34:07 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 83402) Oca 06 22:34:07 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 83403) Oca 06 22:39:27 SEBASTIAN kernel: mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 43936) Oca 06 22:39:28 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 92186) Oca 06 22:39:28 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 92185) Oca 06 22:44:46 SEBASTIAN kernel: mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 45862) Oca 06 22:44:46 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 95417) Oca 06 22:44:46 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 95418) Oca 06 22:49:58 SEBASTIAN kernel: mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 45900) Oca 06 22:49:58 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 95460) Oca 06 22:49:58 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 95461) Oca 06 22:53:22 SEBASTIAN kernel: mce: CPU1: Core temperature above threshold, cpu clock throttled (total events = 58362) Oca 06 22:54:58 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 97042) Oca 06 22:54:58 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 97041) Oca 06 23:03:39 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 97096) Oca 06 23:03:39 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 97097) Oca 06 23:08:43 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 102756) Oca 06 23:08:43 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 102757) Oca 06 23:10:38 SEBASTIAN kernel: mce: CPU1: Core temperature above threshold, cpu clock throttled (total events = 61542) Oca 06 23:14:07 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 104383) Oca 06 23:14:07 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 104382) Oca 06 23:16:35 SEBASTIAN kernel: mce: CPU1: Core temperature above threshold, cpu clock throttled (total events = 62527) Oca 06 23:20:22 SEBASTIAN kernel: mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 51754) Oca 06 23:20:23 SEBASTIAN kernel: mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 106028) Oca 06 23:20:23 SEBASTIAN kernel: mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 106029) Oca 06 23:21:35 SEBASTIAN kernel: mce: CPU1: Core temperature above threshold, cpu clock throttled (total events = 64539)
Kod: [Seç]
https://termbin.com/hawt
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: Butterfly - 07 Ocak 2020, 19:10:27: Alıntı
└─NetworkManager.service @34.292s +16.928s

Ağ servisi çok bekleme yapıyor, aşağıdaki komutun çıktsına bakalım.

Kod: [Seç]
systemctl status NetworkManager.service

Bu arada, Cinnamon masaüstündeki eklenti ile ilgili sorunu çözemediyseniz, yeni bir konu açabilirsiniz. Daha önce belirttiğimi gibi, bu konudan bağımsız bir husus.
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: sebastianhawk - 07 Ocak 2020, 20:51:04: Kod: [Seç]
● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2020-01-07 16:00:06 +03; 4h 47min ago Docs: man:NetworkManager(8) Main PID: 794 (NetworkManager) Tasks: 4 (limit: 4269) CGroup: /system.slice/NetworkManager.service ├─ 794 /usr/sbin/NetworkManager --no-daemon └─1741 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/dhclient-enp3s0.pid -lf /var/lib/NetworkManager/dhclient-436cafb2-bd35-4cb6-91 Oca 07 20:15:40 SEBASTIAN dhclient[1741]: bound to 192.168.1.104 -- renewal in 1474 seconds. Oca 07 20:40:15 SEBASTIAN dhclient[1741]: DHCPREQUEST of 192.168.1.104 on enp3s0 to 192.168.1.1 port 67 (xid=0x1870a414) Oca 07 20:40:15 SEBASTIAN dhclient[1741]: DHCPACK of 192.168.1.104 from 192.168.1.1 Oca 07 20:40:18 SEBASTIAN NetworkManager[794]: <info> [1578418818.1457] dhcp4 (enp3s0): address 192.168.1.104 Oca 07 20:40:18 SEBASTIAN NetworkManager[794]: <info> [1578418818.2901] dhcp4 (enp3s0): plen 24 (255.255.255.0) Oca 07 20:40:18 SEBASTIAN NetworkManager[794]: <info> [1578418818.2902] dhcp4 (enp3s0): gateway 192.168.1.1 Oca 07 20:40:18 SEBASTIAN NetworkManager[794]: <info> [1578418818.2903] dhcp4 (enp3s0): lease time 3600 Oca 07 20:40:19 SEBASTIAN dhclient[1741]: bound to 192.168.1.104 -- renewal in 1779 seconds. Oca 07 20:40:18 SEBASTIAN NetworkManager[794]: <info> [1578418818.2903] dhcp4 (enp3s0): nameserver '192.168.1.1' Oca 07 20:40:18 SEBASTIAN NetworkManager[794]: <info> [1578418818.2903] dhcp4 (enp3s0): state changed bound -> bound lines 1-20/20 (END)
O sorunu hallettim.Bilmediğim bir şekilde ama yaptım.Yukardaki kod çıktısında
Alıntı
lines 1-20/20 (END)
bu vardı.Umarım eksik bir şey atmamışımdır.
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: Butterfly - 07 Ocak 2020, 22:03:31: Aşağıdaki komutla ya da menüden aratarak "Ağ Bağlantıları" aracını açın.

Kod: [Seç]
nm-connection-editor
Bağlantınızı seçip çift tıklayın ve açılan düzenleme penceresinde IPV4 sekmesini açın.
Yöntem kısmından Elle seçeneğini seçin ve Ekle düğmesine tıklayın.
Eklenen kısmı aşağıdaki şekillde doldurup, düzenlemeleri kaydedersiniz.

Adres: 192.168.1.104
Ağ Maskesi: 255.255.255.0
Ağ Geçidi: 192.168.1.1
DNS Sunucuları: İsterseniz belilediğiniz DNS sunucusunu yazabilirsiniz.

Bu şekilde ağ servisi ile ilgili gecikmeyi önlemeyi deneyebilirsiniz.
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: sebastianhawk - 08 Ocak 2020, 02:04:28: O ayarları yaptığımda internet bağlantımda sorun oluştu.Eski haline getirdim.Hızlandırmak için başka yapabileceğim bir şey var mı yoksa bu kadar mı?
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: Butterfly - 08 Ocak 2020, 12:30:33: Alıntı
dnsmasq[1604]: failed to create listening socket for port 53: Adres zaten kullanımda
dnsmasq[1604]: FAILED to start up
systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.

Ağ yöneticisi ile ilgili durumu anlamaya çalışıyorum, klasik HDD cihazlarda açılış süresinin 35-45 saniye aralığında olması normal sayılabilir. Sizin sistemde bunun biraz üstünde bir sürede açıldığını görüyoruz. Çıktılardan edindiğim intibaya göre bunun ağ yöneticisi ile ilgili bir husus olabileceğinden şüphelendim, daha doğrusu DNS/DHCP ile ilgili bir husus olabilir. Bu sebeple yukarıda otomatik DHCP yerine elle IP atamayı önerdim. Eğer ayarları bahsettiğim şekilde yaptıysanız, internetle ilgili bir sorun yaşanmaması gerekirdi. Ama ağ yönetimi ile ilgili olarak, daha önce yaptığınız düzenlemeler varsa, bunlar sebebiyle IP atama ile ilgili bir olumsuzluk yaşanmış olabilir. Eğer bu tür düzenlemeler varsa bunları foruma aktarınız.
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: sebastianhawk - 08 Ocak 2020, 16:36:32: Daha önce hiçbir düzenleme yapmadım.İşletim sistemimi kurduğumdan beri ağ ile ilgili bir sorun yaşamadım.Geçenlerde Kablosuz erişim noktasının adını değiştirmeyle ilgili bir sorun yaşamıştım onuda farklı bir programla düzelttim.Şuan tekrardan elle yapılandırdım dün gece hata veriyordu.Tekrardan test ediyorum.

Maalesef hala hata alıyorum.Ayarları yaptıktan sonra kısa süreli bir bağlantı sağlıyor fakat anlamadığım şekilde sonra bağlantım gidiyor.
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: Butterfly - 09 Ocak 2020, 18:07:38: Aynı modeme bağlı farklı aygıtlar varsa, sizden önce sabitlediğiniz IP farklı bir aygıta atanıyor olabilir. Bu durumda IP çakışması sebebiyle erişim sorunu yaşıyor olabilirsiniz. IPV4 ayarlarında adres kısmını değiştirmeyi deneyebilirsiniz, örneğin DHCP tarafından atanması daha zor olabilecek aşağıdaki IP adresi denenebilir. Tabii modeme bağlanan çok sayıda aygıt varsa, bu adreste DHCP tarafından farklı bir aygıta atanabilir, eğer aygıt sayısı azsa uygun olacaktır.

Adres: 192.168.1.120
Ağ Maskesi: 255.255.255.0
Ağ Geçidi: 192.168.1.1

Aslında burada aygıtın IP alma sürecinin açılışı nasıl etkilelediğini görmek istiyoruz. Alternatif olarak, ağ yöneticisinden bağlantınızı silip sistemi bu şekilde açın. Yani kablolu ya da kablosuz olarak tanımlı, otomatik olarak bağlantı kurmaya çalışacak bir bağlantınız olmasın. Sistemi bu şekilde açtıktan sonra, aşağıdaki komutların çıktılarına bir daha bakabiliriz. Sonuca göre araştırma yapıp çöüzm önerisi sunulabilir.

Kod: [Seç]
systemd-analyze --no-pager blame systemd-analyze --no-pager critical-chain journalctl --no-pager -b -p3 systemctl status NetworkManager.service --no-pager dmesg | nc termbin.com 9999
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: sebastianhawk - 09 Ocak 2020, 23:15:32: Kod: [Seç]
24.691s networkd-dispatcher.service 23.295s ModemManager.service 19.078s dev-sda1.device 19.018s NetworkManager.service 16.284s ubuntu-system-adjustments.service 13.505s systemd-journal-flush.service 12.254s udisks2.service 10.527s accounts-daemon.service 9.919s systemd-tmpfiles-setup.service 9.564s lightdm.service 9.559s plymouth-quit-wait.service 8.413s ufw.service 7.726s apparmor.service 7.642s systemd-udevd.service 6.944s networking.service 6.833s wpa_supplicant.service 6.666s thermald.service 6.091s rsyslog.service 5.801s gpu-manager.service 5.471s avahi-daemon.service 4.533s dnsmasq.service 4.178s grub-common.service 3.447s lvm2-monitor.service 3.398s systemd-tmpfiles-setup-dev.service 3.327s polkit.service 2.995s preload.service 2.857s dns-clean.service 2.285s zram-config.service 2.081s bluetooth.service 2.009s systemd-sysctl.service 1.983s systemd-modules-load.service 1.880s speech-dispatcher.service 1.759s lm-sensors.service 1.488s keyboard-setup.service 1.344s systemd-rfkill.service 1.250s systemd-journald.service 1.207s systemd-logind.service 1.009s hddtemp.service 866ms kerneloops.service 712ms swapfile.swap 711ms pppd-dns.service 597ms user@1000.service 513ms console-setup.service 474ms systemd-remount-fs.service 384ms systemd-timesyncd.service 368ms sys-kernel-debug.mount 366ms blk-availability.service 356ms systemd-random-seed.service 350ms systemd-resolved.service 342ms upower.service 314ms kmod-static-nodes.service 244ms systemd-user-sessions.service 230ms dev-hugepages.mount 228ms dev-mqueue.mount 182ms systemd-backlight@backlight:intel_backlight.service 181ms systemd-update-utmp.service 180ms setvtrgb.service 89ms systemd-udev-trigger.service 18ms colord.service 15ms ureadahead-stop.service 14ms plymouth-start.service 11ms alsa-restore.service 11ms plymouth-read-write.service 8ms systemd-update-utmp-runlevel.service 5ms sys-fs-fuse-connections.mount 4ms rtkit-daemon.service 3ms openvpn.service 2ms sys-kernel-config.mount
Kod: [Seç]
graphical.target @59.827s └─multi-user.target @59.827s └─getty.target @59.827s └─getty@tty1.service @59.826s └─system-getty.slice @59.824s └─setvtrgb.service @59.643s +180ms └─systemd-user-sessions.service @49.834s +244ms └─network.target @49.833s └─NetworkManager.service @30.814s +19.018s └─dbus.service @29.917s └─basic.target @29.916s └─sockets.target @29.916s └─cups.socket @29.916s └─sysinit.target @29.809s └─systemd-timesyncd.service @29.425s +384ms └─systemd-tmpfiles-setup.service @19.469s +9.919s └─systemd-journal-flush.service @5.963s +13.505s └─systemd-journald.service @4.711s +1.250s └─syslog.socket @4.709s └─system.slice @4.572s └─-.slice @4.526s
Kod: [Seç]
-- Logs begin at Sun 2018-01-28 18:58:22 +03, end at Thu 2020-01-09 23:09:09 +03. -- Oca 09 23:03:55 SEBASTIAN kernel: ACPI Error: Needed type [Reference], found [Integer] (____ptrval____) (20190703/exresop-69) Oca 09 23:03:55 SEBASTIAN kernel: ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Store] (20190703/dswexec-427) Oca 09 23:03:55 SEBASTIAN kernel: ACPI Error: Aborting method \_PR.CPU0._PDC due to previous error (AE_AML_OPERAND_TYPE) (20190703/psparse-531) Oca 09 23:04:25 SEBASTIAN bluetoothd[886]: Failed to set mode: Blocked through rfkill (0x12) Oca 09 23:04:44 SEBASTIAN dnsmasq[1433]: failed to create listening socket for port 53: Adres zaten kullanımda Oca 09 23:04:44 SEBASTIAN dnsmasq[1433]: FAILED to start up Oca 09 23:04:44 SEBASTIAN systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. Oca 09 23:05:07 SEBASTIAN pulseaudio[2492]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Oca 09 23:05:07 SEBASTIAN pulseaudio[2521]: [pulseaudio] pid.c: Daemon already running.
Kod: [Seç]
NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2020-01-09 23:04:39 +03; 4min 58s ago Docs: man:NetworkManager(8) Main PID: 848 (NetworkManager) Tasks: 3 (limit: 4269) CGroup: /system.slice/NetworkManager.service └─848 /usr/sbin/NetworkManager --no-daemon Oca 09 23:04:45 SEBASTIAN NetworkManager[848]: <info> [1578600285.5867] dev…l') Oca 09 23:04:45 SEBASTIAN NetworkManager[848]: <info> [1578600285.6264] wif…rol Oca 09 23:04:45 SEBASTIAN NetworkManager[848]: <info> [1578600285.6270] dev…ode Oca 09 23:04:45 SEBASTIAN NetworkManager[848]: <info> [1578600285.6296] man…/3) Oca 09 23:04:45 SEBASTIAN NetworkManager[848]: <info> [1578600285.6317] dev…l') Oca 09 23:04:45 SEBASTIAN NetworkManager[848]: <info> [1578600285.7209] mod…ble Oca 09 23:04:45 SEBASTIAN NetworkManager[848]: <info> [1578600285.7213] blu…n 5 Oca 09 23:04:45 SEBASTIAN NetworkManager[848]: <info> [1578600285.7231] sup…ing Oca 09 23:04:45 SEBASTIAN NetworkManager[848]: <info> [1578600285.7244] blu…:C2 Oca 09 23:04:51 SEBASTIAN NetworkManager[848]: <info> [1578600291.6006] man…ete Hint: Some lines were ellipsized, use -l to show in full.
Kod: [Seç]
https://termbin.com/e26bh
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: Butterfly - 10 Ocak 2020, 00:48:13: Aşğaıdaki komutla, açtığınız diğer konuda önerdiğim Create-ap-gui uygulamasını kaldırmayı dener misiniz? Sanırım bununla birlikte kurulan dnsmasq ile ilgili bir sorun yaşanıyor. Burada (https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1778073) da bununla ilgili bir hata kaydı da açılmış.

Kod: [Seç]
sudo apt purge bridge-utils create-ap create-ap-gui dnsmasq hostapd
Ardından sistemi yeniden başlatıp aşağıdaki komutların çıktılarını yeniden paylaşırsınız.

Kod: [Seç]
systemd-analyze systemd-analyze --no-pager critical-chain systemctl status NetworkManager.service --no-pager -l
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: sebastianhawk - 10 Ocak 2020, 16:47:01: Kod: [Seç]
Startup finished in 7.085s (kernel) + 53.081s (userspace) = 1min 166ms graphical.target reached after 53.063s in userspace
Kod: [Seç]
graphical.target @53.063s └─multi-user.target @53.063s └─getty.target @53.063s └─getty@tty1.service @53.062s └─system-getty.slice @53.060s └─setvtrgb.service @52.686s +371ms └─systemd-user-sessions.service @38.282s +75ms └─network.target @38.276s └─NetworkManager.service @28.013s +10.262s └─dbus.service @22.389s └─basic.target @22.289s └─sockets.target @22.289s └─uuidd.socket @22.289s └─sysinit.target @22.136s └─systemd-timesyncd.service @21.666s +470ms └─systemd-tmpfiles-setup.service @19.642s +1.900s └─systemd-journal-flush.service @5.514s +14.123s └─systemd-journald.service @4.756s +756ms └─systemd-journald-audit.socket @4.755s └─system.slice @4.473s └─-.slice @4.427s
Kod: [Seç]
● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2020-01-10 16:39:16 +03; 7min ago Docs: man:NetworkManager(8) Main PID: 887 (NetworkManager) Tasks: 5 (limit: 4269) CGroup: /system.slice/NetworkManager.service ├─ 887 /usr/sbin/NetworkManager --no-daemon └─1634 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/dhclient-enp3s0.pid -lf /var/lib/NetworkManager/dhclient-7179f7d4-718d-4107-947b-94e1443765c6-enp3s0.lease -cf /var/lib/NetworkManager/dhclient-enp3s0.conf enp3s0 Oca 10 16:39:34 SEBASTIAN NetworkManager[887]: <info> [1578663574.9284] dhcp4 (enp3s0): state changed unknown -> bound Oca 10 16:39:34 SEBASTIAN NetworkManager[887]: <info> [1578663574.9306] device (enp3s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Oca 10 16:39:34 SEBASTIAN NetworkManager[887]: <info> [1578663574.9319] device (enp3s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Oca 10 16:39:34 SEBASTIAN NetworkManager[887]: <info> [1578663574.9323] device (enp3s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Oca 10 16:39:34 SEBASTIAN NetworkManager[887]: <info> [1578663574.9325] manager: NetworkManager state is now CONNECTED_LOCAL Oca 10 16:39:35 SEBASTIAN dhclient[1634]: bound to 192.168.1.104 -- renewal in 1576 seconds. Oca 10 16:39:35 SEBASTIAN NetworkManager[887]: <info> [1578663575.0234] manager: NetworkManager state is now CONNECTED_SITE Oca 10 16:39:35 SEBASTIAN NetworkManager[887]: <info> [1578663575.0237] policy: set 'Otomatik Ethernet' (enp3s0) as default for IPv4 routing and DNS Oca 10 16:39:35 SEBASTIAN NetworkManager[887]: <info> [1578663575.0260] device (enp3s0): Activation: successful, device activated. Oca 10 16:39:47 SEBASTIAN NetworkManager[887]: <info> [1578663587.3784] manager: NetworkManager state is now CONNECTED_GLOBALKaldırdım ama benim böyle bir yazılıma ihtiyacım var.Önerebileceğiniz başka yazılım var mı?
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: Butterfly - 10 Ocak 2020, 17:23:15: Alıntı
└─systemd-journal-flush.service @5.514s +14.123s

Şu an günlükleme servisi ile ilgili gecikme kalmış görünüyor. Aşağıdaki komutlarla günlükleme dosyalarını temizleyip,

Kod: [Seç]
sudo journalctl --vacuum-time=2d sudo journalctl --vacuum-size=200M
aşağıdaki şekilde günlükleme ile ilgili dosya sınırlaması yapmayı deneyiniz. Bunun için aşağıdaki komutları uçbirimde çalıştırınız.

Kod: [Seç]
sudo mkdir -p /etc/systemd/journald.conf.d/
Kod: [Seç]
sudo xed /etc/systemd/journald.conf.d/00-journal-size.conf
Açılan dosyaya aşağıdaki satırları ekleyip, dosyayı kaydediniz.

Kod: [Seç]
SystemMaxFileSize=200M SystemMaxFiles=5

Create-ap-gui uygulaması ile kurulan dnsmasq ile systemd-resolve servisinin kullandığı portlar çakışıyormuş (https://computingforgeeks.com/install-and-configure-dnsmasq-on-ubuntu-18-04-lts/). Bunu aşamak için aşağıdaki komutla systemd-resolved servisini pasifleştirebilirsiniz.

Kod: [Seç]
sudo systemctl disable systemd-resolved
Ardından Create-ap-gui uygulamasını kurabilirsiniz.

Tüm bu işlemlerden ardından, sistemi yeniden başlattıktan sonra, bir önceki mesajda istenen komutların çıktılarını paylaşırsanız, sonucu kontrol edebiliriz.
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: sebastianhawk - 10 Ocak 2020, 21:16:47: Kod: [Seç]
sudo systemctl disable systemd-resolved Bu komutu çalıştırdıktan sonra yeniden başlattım.Açıldığında internet bağlantım kesilmişti.Enable yaparak düzelttim.Çalıştırdığımda internete bağlanamıyorum.
Kod: [Seç]
Startup finished in 7.203s (kernel) + 56.519s (userspace) = 1min 3.723s graphical.target reached after 56.505s in userspace
Kod: [Seç]
graphical.target @56.505s └─multi-user.target @56.505s └─getty.target @56.505s └─getty@tty1.service @56.504s └─system-getty.slice @56.502s └─setvtrgb.service @56.308s +191ms └─systemd-user-sessions.service @39.825s +95ms └─network.target @39.817s └─NetworkManager.service @25.448s +14.368s └─dbus.service @16.337s └─basic.target @16.203s └─sockets.target @16.203s └─acpid.socket @16.203s └─sysinit.target @15.510s └─systemd-backlight@backlight:intel_backlight.service @28.062s +1.083s └─system-systemd\x2dbacklight.slice @28.061s └─system.slice @4.594s └─-.slice @4.558s
Kod: [Seç]
● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2020-01-10 20:57:32 +03; 18min ago Docs: man:NetworkManager(8) Main PID: 821 (NetworkManager) Tasks: 4 (limit: 4269) CGroup: /system.slice/NetworkManager.service ├─ 821 /usr/sbin/NetworkManager --no-daemon └─1667 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/dhclient-enp3s0.pid -lf /var/lib/NetworkManager/dhclient-9b6b288b-1f48-49b5-bf58-782e658b7fc8-enp3s0.lease -cf /var/lib/NetworkManager/dhclient-enp3s0.conf enp3s0 Oca 10 20:57:56 SEBASTIAN NetworkManager[821]: <info> [1578679076.7659] manager: NetworkManager state is now CONNECTED_SITE Oca 10 20:57:56 SEBASTIAN NetworkManager[821]: <info> [1578679076.7666] policy: set 'Otomatik Ethernet' (enp3s0) as default for IPv4 routing and DNS Oca 10 20:57:56 SEBASTIAN NetworkManager[821]: <info> [1578679076.7684] device (enp3s0): Activation: successful, device activated. Oca 10 20:57:58 SEBASTIAN NetworkManager[821]: <info> [1578679078.0857] manager: NetworkManager state is now CONNECTED_GLOBAL Oca 10 21:04:01 SEBASTIAN NetworkManager[821]: <info> [1578679441.8711] wifi-nl80211: (ap0): using nl80211 for WiFi device control Oca 10 21:04:01 SEBASTIAN NetworkManager[821]: <info> [1578679441.8713] device (ap0): driver supports Access Point (AP) mode Oca 10 21:04:01 SEBASTIAN NetworkManager[821]: <info> [1578679441.8726] manager: (ap0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/4) Oca 10 21:04:01 SEBASTIAN NetworkManager[821]: <info> [1578679441.8899] devices added (path: /sys/devices/pci0000:00/0000:00:1c.1/0000:02:00.0/net/ap0, iface: ap0) Oca 10 21:04:01 SEBASTIAN NetworkManager[821]: <info> [1578679441.8899] device added (path: /sys/devices/pci0000:00/0000:00:1c.1/0000:02:00.0/net/ap0, iface: ap0): no ifupdown configuration found. Oca 10 21:14:04 SEBASTIAN NetworkManager[821]: <info> [1578680044.8989] devices removed (path: /sys/devices/pci0000:00/0000:00:1c.1/0000:02:00.0/net/ap0, iface: ap0)
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: Butterfly - 10 Ocak 2020, 22:56:55: Aşağıdaki komutlarla systemd-resolved servisini pasifleştirin ve durdurun.

Kod: [Seç]
sudo systemctl disable systemd-resolved sudo systemctl stop systemd-resolved
Ardından aşağıdaki komutla ağ yöneticisinin ayar dosyasını açın.

Kod: [Seç]
sudo xed /etc/NetworkManager/NetworkManager.conf
Açılan yapılandırma dosyasının [main] kısmına aşağıdaki satırı ekleyin.

Kod: [Seç]
dns=default
Dosya aşağıdaki gibi görünecek.

Kod: [Seç]
[main] plugins=ifupdown,keyfile dns=default [ifupdown] managed=false [device] wifi.scan-rand-mac-address=no
En son olarak, aşğaıdaki komutla /etc/resolv.conf dosyasını silin.

Kod: [Seç]
sudo rm -f /etc/resolv.conf
Sistemi yeniden başlattığınızda ya da aşağıdaki komutla ağ yöneticisini yeniden başlattığınızda, DNS işlevini ağ yöneticisi üstlenecektir.

Kod: [Seç]
sudo systemctl restart NetworkManager
Kaynak (https://askubuntu.com/a/907249)
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: sebastianhawk - 13 Ocak 2020, 17:24:59: Yaptım, şimdi eski attığınız ayarları tekrar mı uygulayayım ?
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: Butterfly - 13 Ocak 2020, 18:42:52: Alıntı yapılan: sebastianhawk - 13 Ocak 2020, 17:24:59
Yaptım, şimdi eski attığınız ayarları tekrar mı uygulayayım ?

Ayarladan kastınız, sonuçları görmek için istediğimiz çıktılarsa; en istediklerimizi paylaşabilirsiniz.
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: sebastianhawk - 14 Ocak 2020, 02:40:14: Bu ayarlardan bahsediyorum.
Alıntı yapılan: Butterfly - 07 Ocak 2020, 22:03:31
Aşağıdaki komutla ya da menüden aratarak "Ağ Bağlantıları" aracını açın.

Kod: [Seç]
nm-connection-editor
Bağlantınızı seçip çift tıklayın ve açılan düzenleme penceresinde IPV4 sekmesini açın.
Yöntem kısmından Elle seçeneğini seçin ve Ekle düğmesine tıklayın.
Eklenen kısmı aşağıdaki şekillde doldurup, düzenlemeleri kaydedersiniz.

Adres: 192.168.1.104
Ağ Maskesi: 255.255.255.0
Ağ Geçidi: 192.168.1.1
DNS Sunucuları: İsterseniz belilediğiniz DNS sunucusunu yazabilirsiniz.

Bu şekilde ağ servisi ile ilgili gecikmeyi önlemeyi deneyebilirsiniz.
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: Butterfly - 14 Ocak 2020, 03:34:59: Alıntı yapılan: sebastianhawk - 14 Ocak 2020, 02:40:14
Bu ayarlardan bahsediyorum.

Bunları uygulamanıza gerek yok. Bu ayarları sadece sistemin otomatik IP almasını önleyerek, ağ yöneticisi ile ilgili sorunun kaynağını görmeye çalışmak için önerdim. Bu ayarlar modemden sabit IP atanmasına yarıyor sadece. systemd-resolved ile ilgili düzenlemeleri yaptıysanız, Create-AP ile kurulan dnsmasq ile port çakışması sorununu çözmüş olmanız gerekir. Son durumu görmek için aşağıdaki komutların çıktılarını yeniden paylaşabilirsiniz.

Kod: [Seç]
systemd-analyze systemd-analyze --no-pager critical-chain systemctl status NetworkManager.service --no-pager -l dmesg | nc termbin.com 9999
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: sebastianhawk - 14 Ocak 2020, 04:53:10: Kod: [Seç]
Startup finished in 7.335s (kernel) + 57.199s (userspace) = 1min 4.535s graphical.target reached after 57.187s in userspace
Kod: [Seç]
graphical.target @57.187s └─multi-user.target @57.187s └─getty.target @57.187s └─getty@tty1.service @57.186s └─system-getty.slice @57.184s └─setvtrgb.service @56.853s +329ms └─systemd-user-sessions.service @41.672s +246ms └─network.target @41.666s └─wpa_supplicant.service @30.753s +7.239s └─dbus.service @19.756s └─basic.target @18.624s └─paths.target @18.624s └─acpid.path @18.624s └─sysinit.target @18.324s └─systemd-backlight@backlight:intel_backlight.service @32.005s +1.421s └─system-systemd\x2dbacklight.slice @32.004s └─system.slice @4.957s └─-.slice @4.921s
Kod: [Seç]
● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2020-01-13 17:24:21 +03; 11h ago Docs: man:NetworkManager(8) Main PID: 15404 (NetworkManager) Tasks: 4 (limit: 4269) CGroup: /system.slice/NetworkManager.service ├─15404 /usr/sbin/NetworkManager --no-daemon └─15417 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/dhclient-enp3s0.pid -lf /var/lib/NetworkManager/dhclient-9b6b288b-1f48-49b5-bf58-782e658b7fc8-enp3s0.lease -cf /var/lib/NetworkManager/dhclient-enp3s0.conf enp3s0 Oca 14 04:14:47 SEBASTIAN dhclient[15417]: bound to 192.168.1.104 -- renewal in 1724 seconds. Oca 14 04:43:32 SEBASTIAN dhclient[15417]: DHCPREQUEST of 192.168.1.104 on enp3s0 to 192.168.1.1 port 67 (xid=0xb6cbbf3) Oca 14 04:43:32 SEBASTIAN dhclient[15417]: DHCPACK of 192.168.1.104 from 192.168.1.1 Oca 14 04:43:32 SEBASTIAN NetworkManager[15404]: <info> [1578966212.3281] dhcp4 (enp3s0): address 192.168.1.104 Oca 14 04:43:32 SEBASTIAN NetworkManager[15404]: <info> [1578966212.3287] dhcp4 (enp3s0): plen 24 (255.255.255.0) Oca 14 04:43:32 SEBASTIAN NetworkManager[15404]: <info> [1578966212.3290] dhcp4 (enp3s0): gateway 192.168.1.1 Oca 14 04:43:32 SEBASTIAN NetworkManager[15404]: <info> [1578966212.3292] dhcp4 (enp3s0): lease time 3600 Oca 14 04:43:32 SEBASTIAN NetworkManager[15404]: <info> [1578966212.3294] dhcp4 (enp3s0): nameserver '192.168.1.1' Oca 14 04:43:32 SEBASTIAN NetworkManager[15404]: <info> [1578966212.3301] dhcp4 (enp3s0): state changed bound -> bound Oca 14 04:43:32 SEBASTIAN dhclient[15417]: bound to 192.168.1.104 -- renewal in 1390 seconds.
Kod: [Seç]
https://termbin.com/ih8g
Başlık: Ynt: Linux Mint 19.3 Yavaş Açılış Sorunu
Gönderen: Butterfly - 14 Ocak 2020, 15:40:40: Alıntı
└─systemd-backlight@backlight:intel_backlight.service @32.005s +1.421s
└─system-systemd\x2dbacklight.slice @32.004s
└─system.slice @4.957s

Şimdi de arka ışıklandırma servisi ile ilgili bir gecikme görünüyor. Bunu bir araştıralım. Bu arada aşağıdaki komutun çıktısını sistemi yeniden başlattığınızda paylaşın, en son paylaştığınız çıktı da sistem açılışındakiler görünmüyor.

Kod: [Seç]
dmesg | nc termbin.com 9999
Not: Bu uçbirimdeki sınırlamadan kaynaklanmıştır, Uçbirim => Düzenle menüsü => Tercihler => Kaydırma sekmesi => Geriye kaydırmayı şu sayıyla sınırla seçeneğindeki işareti kaldırırsanız, bu sınırlama kalkar.