Linux Mint Türkiye
Linux Mint Destek => Açılış, Kapanış ve Oturum Açma => Konuyu başlatan: HALDUNHİTAY - 15 Ocak 2020, 10:35:07
-
Değerli üstadım, ben de aynı dertten muzdaribim. Linux Mint'in açılması 3-4 dakika sürüyor.Yardımcı olursanız sevinirim.Çıktılar şöyle:
haldun[member=3507]Haldun[/member]-PU551LD:~$ systemd-analyze
Startup finished in 7.849s (kernel) + 3min 3.925s (userspace) = 3min 11.774s
graphical.target reached after 1min 37.791s in userspace
haldun[member=3507]Haldun[/member]-PU551LD:~$ systemd-analyze --no-pager critical-chain
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 @1min 37.791s
└─multi-user.target @1min 37.791s
└─getty.target @1min 37.790s
└─getty@tty1.service @1min 37.790s
└─system-getty.slice @1min 37.790s
└─setvtrgb.service @1min 37.684s +105ms
└─systemd-user-sessions.service @1min 36.656s +3ms
└─network.target @1min 36.654s
└─NetworkManager.service @1min 33.800s +2.853s
└─dbus.service @1min 33.750s
└─basic.target @1min 33.725s
└─sockets.target @1min 33.725s
└─acpid.socket @1min 33.725s
└─sysinit.target @1min 33.674s
└─systemd-timesyncd.service @19.418s +672ms
└─systemd-tmpfiles-setup.service @19.228s +188ms
└─systemd-journal-flush.service @4.124s +15.103s
└─systemd-journald.service @3.628s +494ms
└─systemd-journald-dev-log.socket @3.627s
└─system.slice @3.566s
└─-.slice @3.533s
haldun[member=3507]Haldun[/member]-PU551LD:~$ systemctl status NetworkManager.service --no-pager -l
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2020-01-15 10:00:23 +03; 28min ago
Docs: man:NetworkManager(8)
Main PID: 814 (NetworkManager)
Tasks: 4 (limit: 4501)
CGroup: /system.slice/NetworkManager.service
├─ 814 /usr/sbin/NetworkManager --no-daemon
└─1868 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/dhclient-wlp4s0.pid -lf /var/lib/NetworkManager/dhclient-e9190190-18f5-4a47-bef9-91c9239530a4-wlp4s0.lease -cf /var/lib/NetworkManager/dhclient-wlp4s0.conf wlp4s0
Oca 15 10:26:49 haldun-PU551LD NetworkManager[814]: <info> [1579073209.8451] dhcp4 (wlp4s0): state changed unknown -> bound
Oca 15 10:26:49 haldun-PU551LD NetworkManager[814]: <info> [1579073209.8484] device (wlp4s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Oca 15 10:26:49 haldun-PU551LD NetworkManager[814]: <info> [1579073209.8495] device (wlp4s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Oca 15 10:26:49 haldun-PU551LD NetworkManager[814]: <info> [1579073209.8500] device (wlp4s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Oca 15 10:26:49 haldun-PU551LD NetworkManager[814]: <info> [1579073209.8503] manager: NetworkManager state is now CONNECTED_LOCAL
Oca 15 10:26:49 haldun-PU551LD dhclient[1868]: bound to 192.168.0.13 -- renewal in 246691 seconds.
Oca 15 10:26:49 haldun-PU551LD NetworkManager[814]: <info> [1579073209.9222] manager: NetworkManager state is now CONNECTED_SITE
Oca 15 10:26:49 haldun-PU551LD NetworkManager[814]: <info> [1579073209.9224] policy: set 'Otomatik NetMASTER Uydunet-4F9C' (wlp4s0) as default for IPv4 routing and DNS
Oca 15 10:26:49 haldun-PU551LD NetworkManager[814]: <info> [1579073209.9231] device (wlp4s0): Activation: successful, device activated.
Oca 15 10:26:51 haldun-PU551LD NetworkManager[814]: <info> [1579073211.3110] manager: NetworkManager state is now CONNECTED_GLOBAL
haldun[member=3507]Haldun[/member]-PU551LD:~$ dmesg | nc termbin.com 9999
https://termbin.com/nw43
haldun[member=3507]Haldun[/member]-PU551LD:~$
-
[member=502]HALDUNHİTAY[/member] , sizin açtığınız konuyu bölerek yeni bir konu oluşturdum. Sorunlar benzer de olsa, ayrı başlıkta çözüm aranmasını istiyoruz. Zira sorunun nedeni farklı olabilir ve her soruna farklı çözüm önerisi sunulabilir.
[ 25.470367] USB Video Class driver (1.1.1)
[ 26.285865] FAT-fs (sda2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 101.687680] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Mesela sizin sistemde, sda olarak görünen disk ya da USB bellek de dosya sistemi sorunu olduğu anlaşılıyor. Sistemi USB belleği çıkartıp açmayı deneyiniz. Eğer sorun çözülmezse farklı çıktılar da isteyebiliriz.
USB bellekteki dosya sistemini ise aşağıdaki komutlarla düzeltmeyi deneyebilirsiniz.
sudo umount /dev/sdb1sudo dosfsck -t -a -w /dev/sdb1
-
Bluetooth ve ağ bağlantısını pasif duruma getirip , usb belleği verdiğiniz komutlarla formatladım. Sonra usb belleği çıkarıp sistemi yeniden başlattığımda , 2 dak. 20 sn. sonra giriş gerçekleşti. Bu süre normal midir ?
-
Süre normal değil, aşağaıdaki komutların çıktılarını paylaşın.
inxi -Fxxzdmesg | nc termbin.com 9999systemd-analyze timesystemd-analyze --no-pager blamesystemd-analyze --no-pager critical-chainjournalctl --no-pager -b -p3systemctl --no-pager --state=failedcat /etc/fstabsudo blkidcat /etc/initramfs-tools/conf.d/resume
-
Buyrun :
haldun[member=3507]Haldun[/member]-PU551LD:~$ inxi -Fxxz
System:
Host: haldun-PU551LD Kernel: 4.15.0-74-generic x86_64 bits: 64
compiler: gcc v: 7.4.0 Desktop: Cinnamon 4.4.8 wm: muffin dm: LightDM
Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic
Machine:
Type: Laptop System: ASUSTeK product: PU551LD v: 1.0 serial: <filter>
Mobo: ASUSTeK model: PU551LD v: 1.0 serial: <filter>
BIOS: American Megatrends v: PU551LD.211 date: 04/24/2019
Battery:
ID-1: BAT0 charge: 27.6 Wh condition: 28.3/37.4 Wh (76%) volts: 14.4/14.4
model: ASUSTeK PU45026 serial: <filter> status: Not charging
CPU:
Topology: Dual Core model: Intel Core i5-4210U bits: 64 type: MT MCP
arch: Haswell rev: 1 L2 cache: 3072 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19155
Speed: 898 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 854 2: 812
3: 853 4: 840
Graphics:
Device-1: Intel Haswell-ULT Integrated Graphics vendor: ASUSTeK
driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0a16
Device-2: NVIDIA GF117M [GeForce 610M/710M/810M/820M / GT
620M/625M/630M/720M]
vendor: ASUSTeK driver: nouveau v: kernel bus ID: 05:00.0
chip ID: 10de:1140
Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa
resolution: 1366x768~60Hz
OpenGL: renderer: Mesa DRI Intel Haswell Mobile v: 4.5 Mesa 19.0.8
compat-v: 3.0 direct render: Yes
Audio:
Device-1: Intel Haswell-ULT HD Audio driver: snd_hda_intel v: kernel
bus ID: 00:03.0 chip ID: 8086:0a0c
Device-2: Intel 8 Series HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel bus ID: 00:1b.0 chip ID: 8086:9c20
Sound Server: ALSA v: k4.15.0-74-generic
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK driver: r8169 v: 2.3LK-NAPI port: e000 bus ID: 03:00.0
chip ID: 10ec:8168
IF: enp3s0 state: down mac: <filter>
Device-2: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter
vendor: AzureWave driver: ath9k v: kernel port: e000 bus ID: 04:00.0
chip ID: 168c:0036
IF: wlp4s0 state: up mac: <filter>
Drives:
Local Storage: total: 465.76 GiB used: 98.07 GiB (21.1%)
ID-1: /dev/sda vendor: HGST (Hitachi) model: HTS545050A7E680
size: 465.76 GiB speed: 6.0 Gb/s serial: <filter>
Partition:
ID-1: / size: 185.44 GiB used: 53.33 GiB (28.8%) fs: ext4 dev: /dev/sda1
Sensors:
System Temperatures: cpu: 40.0 C mobo: N/A
Fan Speeds (RPM): cpu: 2200
Info:
Processes: 197 Uptime: 42m Memory: 3.73 GiB used: 942.7 MiB (24.7%)
Init: systemd v: 237 runlevel: 5 target: graphical.target Compilers:
gcc: 7.4.0 alt: 7 Shell: bash v: 4.4.20 running in: gnome-terminal
inxi: 3.0.32
haldun[member=3507]Haldun[/member]-PU551LD:~$ dmesg | nc termbin.com 9999
https://termbin.com/s7b8
haldun[member=3507]Haldun[/member]-PU551LD:~$ systemd-analyze time
Startup finished in 7.968s (kernel) + 3min 4.028s (userspace) = 3min 11.997s
graphical.target reached after 1min 40.921s in userspace
haldun[member=3507]Haldun[/member]-PU551LD:~$ systemd-analyze --no-pager blame
15.470s systemd-journal-flush.service
13.529s dev-sda1.device
12.989s lvm2-monitor.service
12.796s ufw.service
11.850s keyboard-setup.service
11.846s systemd-modules-load.service
11.727s systemd-tmpfiles-setup-dev.service
7.019s ubuntu-system-adjustments.service
4.209s networkd-dispatcher.service
3.522s udisks2.service
2.139s NetworkManager.service
1.829s ModemManager.service
1.809s accounts-daemon.service
1.667s dns-clean.service
1.654s gpu-manager.service
1.491s systemd-random-seed.service
969ms wpa_supplicant.service
847ms systemd-resolved.service
845ms systemd-timesyncd.service
760ms avahi-daemon.service
682ms mnt-0057\x2dAA27.mount
671ms grub-common.service
652ms networking.service
627ms colord.service
603ms polkit.service
394ms apparmor.service
347ms kmod-static-nodes.service
320ms thermald.service
310ms systemd-journald.service
306ms systemd-logind.service
302ms kerneloops.service
302ms lm-sensors.service
299ms lightdm.service
297ms plymouth-quit-wait.service
286ms systemd-sysctl.service
259ms rsyslog.service
201ms packagekit.service
196ms systemd-tmpfiles-setup.service
185ms systemd-remount-fs.service
179ms upower.service
152ms setvtrgb.service
144ms sys-kernel-debug.mount
141ms dev-hugepages.mount
132ms systemd-tmpfiles-clean.service
122ms user@1000.service
121ms hddtemp.service
105ms dev-mqueue.mount
95ms systemd-udev-trigger.service
86ms pppd-dns.service
84ms blk-availability.service
82ms bluetooth.service
80ms speech-dispatcher.service
68ms alsa-restore.service
66ms rng-tools.service
65ms systemd-update-utmp.service
58ms systemd-udevd.service
52ms systemd-rfkill.service
14ms plymouth-start.service
12ms plymouth-read-write.service
9ms rtkit-daemon.service
6ms systemd-update-utmp-runlevel.service
6ms sys-fs-fuse-connections.mount
5ms ureadahead-stop.service
4ms systemd-backlight@backlight:intel_backlight.service
4ms systemd-user-sessions.service
2ms sys-kernel-config.mount
2ms console-setup.service
1ms openvpn.service
haldun[member=3507]Haldun[/member]-PU551LD:~$ systemd-analyze --no-pager critical-chain
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 @1min 40.921s
└─multi-user.target @1min 40.921s
└─ubuntu-system-adjustments.service @1min 33.901s +7.019s
└─basic.target @1min 33.891s
└─sockets.target @1min 33.891s
└─dbus.socket @1min 33.891s
└─sysinit.target @1min 33.778s
└─systemd-timesyncd.service @19.620s +845ms
└─systemd-tmpfiles-setup.service @19.417s +196ms
└─systemd-journal-flush.service @3.946s +15.470s
└─systemd-journald.service @3.634s +310ms
└─systemd-journald-audit.socket @3.631s
└─system.slice @3.588s
└─-.slice @3.555s
haldun[member=3507]Haldun[/member]-PU551LD:~$ journalctl --no-pager -b -p3
-- Logs begin at Thu 2019-12-19 16:58:49 +03, end at Wed 2020-01-15 17:53:14 +03. --
Oca 15 17:10:02 haldun-PU551LD systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-34d220b0\x2d6f0a\x2d4054\x2dbd8d\x2dbec9a9355d41.device.
Oca 15 17:10:02 haldun-PU551LD systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-c38d6150\x2db268\x2d4f46\x2da8b1\x2d33b8731ff7b2.device.
Oca 15 17:10:02 haldun-PU551LD systemd[1]: Timed out waiting for device dev-disk-by\x2did-usb\x2dKingston_DataTraveler_3.0_C03FD5F2F334F260E99E0BA4\x2d0:0\x2dpart1.device.
Oca 15 17:10:02 haldun-PU551LD systemd[1]: Timed out waiting for device dev-disk-by\x2did-usb\x2dKingston_DataTraveler_3.0_C03FD5F2F334F260E99E0BA4\x2d0:0.device.
Oca 15 17:10:02 haldun-PU551LD systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-df0d3493\x2d4175\x2d4d42\x2da483\x2d13f5b82a94d2.device.
Oca 15 17:10:03 haldun-PU551LD bluetoothd[845]: Failed to set mode: Blocked through rfkill (0x12)
Oca 15 17:10:06 haldun-PU551LD wpa_supplicant[855]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
Oca 15 17:10:06 haldun-PU551LD wpa_supplicant[855]: dbus: Failed to construct signal
Oca 15 17:10:09 haldun-PU551LD kernel: nouveau 0000:05:00.0: bus: MMIO write of 0000041f FAULT at 6013d4 [ IBUS ]
Oca 15 17:10:09 haldun-PU551LD kernel: nouveau 0000:05:00.0: bus: MMIO write of badf1001 FAULT at 50405c [ IBUS ]
Oca 15 17:10:13 haldun-PU551LD pulseaudio[1238]: [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 15 17:10:13 haldun-PU551LD pulseaudio[1302]: [pulseaudio] pid.c: Daemon already running.
Oca 15 17:10:21 haldun-PU551LD bluetoothd[845]: Failed to set mode: Blocked through rfkill (0x12)
Oca 15 17:11:32 haldun-PU551LD systemd[1]: Timed out waiting for device dev-disk-by\x2did-usb\x2dKingston_DataTraveler_3.0_C03FD5F2F334F260E99E0BA4\x2d0:0\x2dpart1.device.
Oca 15 17:11:32 haldun-PU551LD systemd[1]: Timed out waiting for device dev-disk-by\x2did-usb\x2dKingston_DataTraveler_3.0_C03FD5F2F334F260E99E0BA4\x2d0:0.device.
Oca 15 17:11:32 haldun-PU551LD systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-df0d3493\x2d4175\x2d4d42\x2da483\x2d13f5b82a94d2.device.
Oca 15 17:11:32 haldun-PU551LD systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-34d220b0\x2d6f0a\x2d4054\x2dbd8d\x2dbec9a9355d41.device.
Oca 15 17:11:32 haldun-PU551LD systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-c38d6150\x2db268\x2d4f46\x2da8b1\x2d33b8731ff7b2.device.
Oca 15 17:22:12 haldun-PU551LD systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-c38d6150\x2db268\x2d4f46\x2da8b1\x2d33b8731ff7b2.device.
Oca 15 17:22:12 haldun-PU551LD systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-34d220b0\x2d6f0a\x2d4054\x2dbd8d\x2dbec9a9355d41.device.
Oca 15 17:22:12 haldun-PU551LD systemd[1]: Timed out waiting for device dev-disk-by\x2did-usb\x2dKingston_DataTraveler_3.0_C03FD5F2F334F260E99E0BA4\x2d0:0.device.
Oca 15 17:22:12 haldun-PU551LD systemd[1]: Timed out waiting for device dev-disk-by\x2did-usb\x2dKingston_DataTraveler_3.0_C03FD5F2F334F260E99E0BA4\x2d0:0\x2dpart1.device.
Oca 15 17:22:12 haldun-PU551LD systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-df0d3493\x2d4175\x2d4d42\x2da483\x2d13f5b82a94d2.device.
Oca 15 17:50:34 haldun-PU551LD kernel: nouveau 0000:05:00.0: bus: MMIO write of ffff951f FAULT at 6013d4 [ IBUS ]
Oca 15 17:50:34 haldun-PU551LD kernel: nouveau 0000:05:00.0: bus: MMIO write of badf1001 FAULT at 50405c [ IBUS ]
Oca 15 17:50:35 haldun-PU551LD sudo[3516]: haldun : a password is required ; TTY=pts/0 ; PWD=/home/haldun ; USER=root ; COMMAND=/usr/sbin/hddtemp -nq -u C /dev/sda
haldun[member=3507]Haldun[/member]-PU551LD:~$ systemctl --no-pager --state=failed
0 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
haldun[member=3507]Haldun[/member]-PU551LD:~$ cat /etc/fstab
# /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=f5fcd831-0d30-47df-9e80-c726f9d3e489 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda3 during installation
UUID=34d220b0-6f0a-4054-bd8d-bec9a9355d41 none swap sw 0 0
/dev/disk/by-uuid/c38d6150-b268-4f46-a8b1-33b8731ff7b2 /mnt/c38d6150-b268-4f46-a8b1-33b8731ff7b2 auto nosuid,nodev,nofail,x-gvfs-show 0 0
/dev/disk/by-uuid/0057-AA27 /mnt/0057-AA27 auto nosuid,nodev,nofail,x-gvfs-show 0 0
/dev/disk/by-uuid/df0d3493-4175-4d42-a483-13f5b82a94d2 /mnt/df0d3493-4175-4d42-a483-13f5b82a94d2 auto nosuid,nodev,nofail,x-gvfs-show 0 0
/dev/disk/by-id/usb-Kingston_DataTraveler_3.0_C03FD5F2F334F260E99E0BA4-0:0 /mnt/usb-Kingston_DataTraveler_3.0_C03FD5F2F334F260E99E0BA4-0:0 auto nosuid,nodev,nofail,x-gvfs-show 0 0
/dev/disk/by-id/usb-Kingston_DataTraveler_3.0_C03FD5F2F334F260E99E0BA4-0:0-part1 /mnt/usb-Kingston_DataTraveler_3.0_C03FD5F2F334F260E99E0BA4-0:0-part1 auto nosuid,nodev,nofail,x-gvfs-show 0 0
haldun[member=3507]Haldun[/member]-PU551LD:~$ sudo blkid
[sudo] password for haldun:
/dev/sda1: LABEL="Mint" UUID="f5fcd831-0d30-47df-9e80-c726f9d3e489" TYPE="ext4" PARTUUID="741d2acd-01"
/dev/sda2: LABEL="DM-DM-0SK2" UUID="0057-AA27" TYPE="vfat" PARTUUID="741d2acd-02"
/dev/sda3: UUID="17743a01-ee8e-4986-8e9e-f33aa68be507" TYPE="swap" PARTUUID="741d2acd-03"
/dev/sda4: LABEL="DEBIAN 10" UUID="fe3d283a-86b1-43e9-9e5e-9f7580db31a9" TYPE="ext4" PARTUUID="741d2acd-04"
haldun[member=3507]Haldun[/member]-PU551LD:~$ cat /etc/initramfs-tools/conf.d/resume
RESUME=none
-
/dev/disk/by-uuid/c38d6150-b268-4f46-a8b1-33b8731ff7b2 /mnt/c38d6150-b268-4f46-a8b1-33b8731ff7b2 auto nosuid,nodev,nofail,x-gvfs-show 0 0
/dev/disk/by-uuid/0057-AA27 /mnt/0057-AA27 auto nosuid,nodev,nofail,x-gvfs-show 0 0
/dev/disk/by-uuid/df0d3493-4175-4d42-a483-13f5b82a94d2 /mnt/df0d3493-4175-4d42-a483-13f5b82a94d2 auto nosuid,nodev,nofail,x-gvfs-show 0 0
/dev/disk/by-id/usb-Kingston_DataTraveler_3.0_C03FD5F2F334F260E99E0BA4-0:0 /mnt/usb-Kingston_DataTraveler_3.0_C03FD5F2F334F260E99E0BA4-0:0 auto nosuid,nodev,nofail,x-gvfs-show 0 0
/dev/disk/by-id/usb-Kingston_DataTraveler_3.0_C03FD5F2F334F260E99E0BA4-0:0-part1 /mnt/usb-Kingston_DataTraveler_3.0_C03FD5F2F334F260E99E0BA4-0:0-part1 auto nosuid,nodev,nofail,x-gvfs-show 0 0
Açılışta otomatik bağlanma için ayarladığınız disk bölümlerinin tümünü pasifleştirmeyi deneyiniz. Bazıları artık mevcut değil görünüyor, bazıları için çift girdi eklenmiş. Sorunun kaynağı bu olabilir. Özellikle USB bellek gibi aygıtların açılışta otomatik bağlanması ile ilgili ayarlar uygun olmaz. Bu aygıtlar takılı olmadığında fstab dosyası sebebiyle açılış sorunları yaşanabilir.
-
Ne yaptıysam olmadı.Tricia'yı yeniden kurdum ve şu anda sorun yok. İlginize teşekkür ederim.