Manjaro nach Update sehr langsam
-
Themen Author - Neues Foren Mitglied
- Beiträge: 13
- Registriert: Donnerstag 4. April 2019, 21:07
- CPU: Intel Core 2 Duo CP E8400 3.00GHz
- GPU: Sapphire 11166-67-20G ATI Radeon HD 5450 Grafik Prozessor
- Kernel: 5.0.5-1
- Desktop-Variante: Manjaro KDE 5
- GPU Treiber: Free
- Hat sich bedankt: 2 Mal
Manjaro nach Update sehr langsam
Hallo,
nach dem letzten Kernelupdaten auf Kernel 5.7.9-1 ist Manjaro (KDE) plötzlich sehr langsam. Mit meiner SSD dauert der Bootvorgang (ab Grub-Menü) inkl. Anmeldung bis zum einsatzbereiten Desktop normalerweise keine 10 Sekunden. Jetzt dauert es alleine bis der Anmeldebildschirm erscheint auf die Sekunde genau 90 Sekunden. Nach Eingabe des Passworts weitere 58 Sekunden bis der Desktop da ist und z.B. nach Starten von Dolphin weitere 38 Sekunden bis sich der Dateimanager geöffnet hat, auch das Aufwachen aus dem Bildschirmschoner dauert 33 Sekunden. Selbst auf meinem alten Rechner mit HDD lief Manjaro schneller.
Ich habe den Rechner seit ca. 1 Jahr und noch nie solche Probleme gehabt.
Kann mir einer einen Tipp geben, woran das liegen kann?
Gruß
KDE-Plasma: 5.19.3
KDE-Framework: 5.72.0
Qt-Version 5.15.0
Kernel: 5.7.9-1 (64 Bit)
Prozessor: 16 x AMD Ryzen 7 1700X Eight-Core-Processor
Arbeitsspeicher 16 GB
Grafikprozessor: GeForce GTX 1660 TI/PCIe/SSE2
SSD Samsung 500 GB
Ich habe noch eine 500GB HDD mit Win10 und eine 1TB HDD zur Datensicherung beider Systeme
nach dem letzten Kernelupdaten auf Kernel 5.7.9-1 ist Manjaro (KDE) plötzlich sehr langsam. Mit meiner SSD dauert der Bootvorgang (ab Grub-Menü) inkl. Anmeldung bis zum einsatzbereiten Desktop normalerweise keine 10 Sekunden. Jetzt dauert es alleine bis der Anmeldebildschirm erscheint auf die Sekunde genau 90 Sekunden. Nach Eingabe des Passworts weitere 58 Sekunden bis der Desktop da ist und z.B. nach Starten von Dolphin weitere 38 Sekunden bis sich der Dateimanager geöffnet hat, auch das Aufwachen aus dem Bildschirmschoner dauert 33 Sekunden. Selbst auf meinem alten Rechner mit HDD lief Manjaro schneller.
Ich habe den Rechner seit ca. 1 Jahr und noch nie solche Probleme gehabt.
Kann mir einer einen Tipp geben, woran das liegen kann?
Gruß
KDE-Plasma: 5.19.3
KDE-Framework: 5.72.0
Qt-Version 5.15.0
Kernel: 5.7.9-1 (64 Bit)
Prozessor: 16 x AMD Ryzen 7 1700X Eight-Core-Processor
Arbeitsspeicher 16 GB
Grafikprozessor: GeForce GTX 1660 TI/PCIe/SSE2
SSD Samsung 500 GB
Ich habe noch eine 500GB HDD mit Win10 und eine 1TB HDD zur Datensicherung beider Systeme
-
Themen Author - Neues Foren Mitglied
- Beiträge: 13
- Registriert: Donnerstag 4. April 2019, 21:07
- CPU: Intel Core 2 Duo CP E8400 3.00GHz
- GPU: Sapphire 11166-67-20G ATI Radeon HD 5450 Grafik Prozessor
- Kernel: 5.0.5-1
- Desktop-Variante: Manjaro KDE 5
- GPU Treiber: Free
- Hat sich bedankt: 2 Mal
Re: Manjaro nach Update sehr langsam
hier noch die Ausgabe von
inxi -Fxxxza --no-host
System: Kernel: 5.7.9-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.1.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.7-x86_64 root=UUID=87f0b710-05cd-4c66-8d85-8a40cd256d62 rw
quiet resume=UUID=98e490fa-af2b-4c8e-bb08-c9820ebcf4c0
Desktop: KDE Plasma 5.19.3 tk: Qt 5.15.0 wm: kwin_x11 dm: SDDM Distro: Manjaro Linux
Machine: Type: Desktop Mobo: ASUSTeK model: PRIME A320M-K v: Rev X.0x serial: <filter>
UEFI: American Megatrends v: 4027 date: 11/04/2018
(upower:2227): UPower-WARNING **: 17:35:27.771: Cannot connect to upowerd: Error calling StartServiceByName for org.freedesktop.UPower: Failed to activate service 'org.freedesktop.UPower': timed out (service_start_timeout=25000ms)
Battery: Device-1: hidpp_battery_0 model: Logitech M585/M590 Multi-Device Mouse serial: <filter> charge: Full
status: Discharging
CPU: Topology: 8-Core model: AMD Ryzen 7 1700X bits: 64 type: MT MCP arch: Zen family: 17 (23) model-id: 1
stepping: 1 microcode: 8001137 L2 cache: 4096 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 108627
Speed: 2813 MHz min/max: 2200/3400 MHz boost: enabled Core speeds (MHz): 1: 2797 2: 2808 3: 1746
4: 1745 5: 1744 6: 1744 7: 1746 8: 1739 9: 1746 10: 1743 11: 1743 12: 1739 13: 1746 14: 1743 15: 2790
16: 2813
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: NVIDIA TU116 [GeForce GTX 1660 Ti] driver: nvidia v: 430.64 bus ID: 07:00.0
chip ID: 10de:2182
Display: x11 server: X.Org 1.20.8 driver: nvidia compositor: kwin_x11 resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce GTX 1660 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 430.64 direct render: Yes
Audio: Device-1: NVIDIA TU116 High Definition Audio driver: snd_hda_intel v: kernel bus ID: 07:00.1
chip ID: 10de:1aeb
Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel bus ID: 09:00.3 chip ID: 1022:1457
Sound Server: ALSA v: k5.7.9-1-MANJARO
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8168
v: 8.048.03-NAPI port: f000 bus ID: 05:00.0 chip ID: 10ec:8168
IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 1.83 TiB used: 147.86 GiB (7.9%)
ID-1: /dev/sda vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB block size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> rev: CC43
scheme: GPT
ID-2: /dev/sdb vendor: Samsung model: HD501LJ size: 465.76 GiB block size: physical: 512 B
logical: 512 B speed: 1.5 Gb/s serial: <filter> rev: 0-13 scheme: GPT
ID-3: /dev/sdc vendor: Intenso model: TOP M.2 SATA size: 476.94 GiB block size: physical: 512 B
logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 61.2 scheme: GPT
Partition: ID-1: / raw size: 64.00 GiB size: 62.50 GiB (97.65%) used: 21.29 GiB (34.1%) fs: ext4 dev: /dev/sdc2
ID-2: /home raw size: 376.90 GiB size: 369.99 GiB (98.16%) used: 119.19 GiB (32.2%) fs: ext4
dev: /dev/sdc5
ID-3: /var raw size: 19.53 GiB size: 19.10 GiB (97.79%) used: 7.38 GiB (38.6%) fs: ext4
dev: /dev/sdc4
ID-4: swap-1 size: 16.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 8 (default 60)
cache pressure: 100 (default) dev: /dev/sdc3
Sensors: System Temperatures: cpu: 50.1 C mobo: N/A gpu: nvidia temp: 45 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 42%
Info: Processes: 351 Uptime: 5m Memory: 15.63 GiB used: 1.66 GiB (10.6%) Init: systemd v: 245 Compilers:
gcc: 10.1.0 clang: 10.0.0 Shell: bash v: 5.0.18 running in: konsole inxi: 3.0.37
inxi -Fxxxza --no-host
System: Kernel: 5.7.9-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.1.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.7-x86_64 root=UUID=87f0b710-05cd-4c66-8d85-8a40cd256d62 rw
quiet resume=UUID=98e490fa-af2b-4c8e-bb08-c9820ebcf4c0
Desktop: KDE Plasma 5.19.3 tk: Qt 5.15.0 wm: kwin_x11 dm: SDDM Distro: Manjaro Linux
Machine: Type: Desktop Mobo: ASUSTeK model: PRIME A320M-K v: Rev X.0x serial: <filter>
UEFI: American Megatrends v: 4027 date: 11/04/2018
(upower:2227): UPower-WARNING **: 17:35:27.771: Cannot connect to upowerd: Error calling StartServiceByName for org.freedesktop.UPower: Failed to activate service 'org.freedesktop.UPower': timed out (service_start_timeout=25000ms)
Battery: Device-1: hidpp_battery_0 model: Logitech M585/M590 Multi-Device Mouse serial: <filter> charge: Full
status: Discharging
CPU: Topology: 8-Core model: AMD Ryzen 7 1700X bits: 64 type: MT MCP arch: Zen family: 17 (23) model-id: 1
stepping: 1 microcode: 8001137 L2 cache: 4096 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 108627
Speed: 2813 MHz min/max: 2200/3400 MHz boost: enabled Core speeds (MHz): 1: 2797 2: 2808 3: 1746
4: 1745 5: 1744 6: 1744 7: 1746 8: 1739 9: 1746 10: 1743 11: 1743 12: 1739 13: 1746 14: 1743 15: 2790
16: 2813
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: NVIDIA TU116 [GeForce GTX 1660 Ti] driver: nvidia v: 430.64 bus ID: 07:00.0
chip ID: 10de:2182
Display: x11 server: X.Org 1.20.8 driver: nvidia compositor: kwin_x11 resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce GTX 1660 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 430.64 direct render: Yes
Audio: Device-1: NVIDIA TU116 High Definition Audio driver: snd_hda_intel v: kernel bus ID: 07:00.1
chip ID: 10de:1aeb
Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel bus ID: 09:00.3 chip ID: 1022:1457
Sound Server: ALSA v: k5.7.9-1-MANJARO
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8168
v: 8.048.03-NAPI port: f000 bus ID: 05:00.0 chip ID: 10ec:8168
IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 1.83 TiB used: 147.86 GiB (7.9%)
ID-1: /dev/sda vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB block size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> rev: CC43
scheme: GPT
ID-2: /dev/sdb vendor: Samsung model: HD501LJ size: 465.76 GiB block size: physical: 512 B
logical: 512 B speed: 1.5 Gb/s serial: <filter> rev: 0-13 scheme: GPT
ID-3: /dev/sdc vendor: Intenso model: TOP M.2 SATA size: 476.94 GiB block size: physical: 512 B
logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 61.2 scheme: GPT
Partition: ID-1: / raw size: 64.00 GiB size: 62.50 GiB (97.65%) used: 21.29 GiB (34.1%) fs: ext4 dev: /dev/sdc2
ID-2: /home raw size: 376.90 GiB size: 369.99 GiB (98.16%) used: 119.19 GiB (32.2%) fs: ext4
dev: /dev/sdc5
ID-3: /var raw size: 19.53 GiB size: 19.10 GiB (97.79%) used: 7.38 GiB (38.6%) fs: ext4
dev: /dev/sdc4
ID-4: swap-1 size: 16.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 8 (default 60)
cache pressure: 100 (default) dev: /dev/sdc3
Sensors: System Temperatures: cpu: 50.1 C mobo: N/A gpu: nvidia temp: 45 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 42%
Info: Processes: 351 Uptime: 5m Memory: 15.63 GiB used: 1.66 GiB (10.6%) Init: systemd v: 245 Compilers:
gcc: 10.1.0 clang: 10.0.0 Shell: bash v: 5.0.18 running in: konsole inxi: 3.0.37
-
Themen Author - Neues Foren Mitglied
- Beiträge: 13
- Registriert: Donnerstag 4. April 2019, 21:07
- CPU: Intel Core 2 Duo CP E8400 3.00GHz
- GPU: Sapphire 11166-67-20G ATI Radeon HD 5450 Grafik Prozessor
- Kernel: 5.0.5-1
- Desktop-Variante: Manjaro KDE 5
- GPU Treiber: Free
- Hat sich bedankt: 2 Mal
Re: Manjaro nach Update sehr langsam
und...
journalctl -xn
-- Logs begin at Wed 2020-06-24 12:12:24 CEST, end at Sun 2020-08-02 17:38:36 CEST. --
Aug 02 17:37:50 Manjaro-PC kwin_x11[1225]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 36632,>
Aug 02 17:37:50 Manjaro-PC kwin_x11[1225]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 36635, r>
Aug 02 17:37:50 Manjaro-PC kwin_x11[1225]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 36636,>
Aug 02 17:38:05 Manjaro-PC dbus-daemon[1161]: [session uid=1000 pid=1161] Activating via systemd: service name='org>
Aug 02 17:38:05 Manjaro-PC systemd[1127]: tracker-store.service: Failed to add control inotify watch descriptor for>
Aug 02 17:38:05 Manjaro-PC systemd[1127]: Starting Tracker metadata database store and lookup manager...
-- Subject: A start job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-i ... assistance
--
-- A start job for unit UNIT has begun execution.
--
-- The job identifier is 206.
Aug 02 17:38:05 Manjaro-PC dbus-daemon[1161]: [session uid=1000 pid=1161] Successfully activated service 'org.freed>
Aug 02 17:38:05 Manjaro-PC systemd[1127]: Started Tracker metadata database store and lookup manager.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-i ... assistance
--
-- A start job for unit UNIT has finished successfully.
--
-- The job identifier is 206.
Aug 02 17:38:36 Manjaro-PC tracker-store[2551]: OK
Aug 02 17:38:36 Manjaro-PC systemd[1127]: tracker-store.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-i ... assistance
--
-- The unit UNIT has successfully entered the 'dead' state.
journalctl -xn
-- Logs begin at Wed 2020-06-24 12:12:24 CEST, end at Sun 2020-08-02 17:38:36 CEST. --
Aug 02 17:37:50 Manjaro-PC kwin_x11[1225]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 36632,>
Aug 02 17:37:50 Manjaro-PC kwin_x11[1225]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 36635, r>
Aug 02 17:37:50 Manjaro-PC kwin_x11[1225]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 36636,>
Aug 02 17:38:05 Manjaro-PC dbus-daemon[1161]: [session uid=1000 pid=1161] Activating via systemd: service name='org>
Aug 02 17:38:05 Manjaro-PC systemd[1127]: tracker-store.service: Failed to add control inotify watch descriptor for>
Aug 02 17:38:05 Manjaro-PC systemd[1127]: Starting Tracker metadata database store and lookup manager...
-- Subject: A start job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-i ... assistance
--
-- A start job for unit UNIT has begun execution.
--
-- The job identifier is 206.
Aug 02 17:38:05 Manjaro-PC dbus-daemon[1161]: [session uid=1000 pid=1161] Successfully activated service 'org.freed>
Aug 02 17:38:05 Manjaro-PC systemd[1127]: Started Tracker metadata database store and lookup manager.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-i ... assistance
--
-- A start job for unit UNIT has finished successfully.
--
-- The job identifier is 206.
Aug 02 17:38:36 Manjaro-PC tracker-store[2551]: OK
Aug 02 17:38:36 Manjaro-PC systemd[1127]: tracker-store.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-i ... assistance
--
-- The unit UNIT has successfully entered the 'dead' state.
Re: Manjaro nach Update sehr langsam
Poste mal die Ausgabe von
Code: Alles auswählen
systemd-analyze blame
-
- Moderator
- Beiträge: 2345
- Registriert: Donnerstag 19. Mai 2016, 15:49
- CPU: AMD Quad Core A8 3,6GHz
- GPU: AMD/ATI Radeon R7
- Kernel: 6.1
- Desktop-Variante: XFCE und KDE Stable, Testing, Unstable
- GPU Treiber: Free
- Hat sich bedankt: 28 Mal
- Danksagung erhalten: 151 Mal
Re: Manjaro nach Update sehr langsam
Hallo marlor,
probier es mal mit
Danach das System neu starten.
probier es mal mit
Code: Alles auswählen
sudo pacman -S haveged
Code: Alles auswählen
sudo systemctl enable haveged --now
-
Themen Author - Neues Foren Mitglied
- Beiträge: 13
- Registriert: Donnerstag 4. April 2019, 21:07
- CPU: Intel Core 2 Duo CP E8400 3.00GHz
- GPU: Sapphire 11166-67-20G ATI Radeon HD 5450 Grafik Prozessor
- Kernel: 5.0.5-1
- Desktop-Variante: Manjaro KDE 5
- GPU Treiber: Free
- Hat sich bedankt: 2 Mal
Re: Manjaro nach Update sehr langsam
Hallo Blueriver,Blueriver hat geschrieben: ↑Sonntag 2. August 2020, 18:49 Hallo marlor,
probier es mal mitCode: Alles auswählen
sudo pacman -S haveged
Danach das System neu starten.Code: Alles auswählen
sudo systemctl enable haveged --now
das hatte ich schon gemacht, aber leider ohne Auswirkungen...
-
Themen Author - Neues Foren Mitglied
- Beiträge: 13
- Registriert: Donnerstag 4. April 2019, 21:07
- CPU: Intel Core 2 Duo CP E8400 3.00GHz
- GPU: Sapphire 11166-67-20G ATI Radeon HD 5450 Grafik Prozessor
- Kernel: 5.0.5-1
- Desktop-Variante: Manjaro KDE 5
- GPU Treiber: Free
- Hat sich bedankt: 2 Mal
Re: Manjaro nach Update sehr langsam
Josef_K hat geschrieben: ↑Sonntag 2. August 2020, 18:25 Poste mal die Ausgabe vonCode: Alles auswählen
systemd-analyze blame
Code: Alles auswählen
8.999s NetworkManager-wait-online.service
1.783s lvm2-monitor.service
1.268s systemd-logind.service
573ms org.cups.cupsd.service
532ms dev-sdc2.device
477ms tlp.service
334ms systemd-udevd.service
320ms systemd-journald.service
293ms systemd-modules-load.service
264ms systemd-fsck@dev-disk-by\x2duuid-5e7019cd\x2d69ae\x2d4a6d\x2d8422\x2d0b9cb1fe1557.service
261ms systemd-fsck@dev-disk-by\x2duuid-a8ea9596\x2df2e2\x2d4247\x2d9871\x2da1ad199b2c49.service
253ms systemd-fsck@dev-disk-by\x2duuid-8B4C\x2d4FCE.service
246ms boot-efi.mount
244ms upower.service
228ms home.mount
220ms udisks2.service
187ms var.mount
177ms polkit.service
134ms avahi-daemon.service
131ms systemd-journal-flush.service
130ms NetworkManager.service
115ms user@1000.service
83ms dev-disk-by\x2duuid-98e490fa\x2daf2b\x2d4c8e\x2dbb08\x2dc9820ebcf4c0.swap
61ms systemd-udev-trigger.service
47ms ModemManager.service
36ms systemd-tmpfiles-setup.service
27ms systemd-tmpfiles-setup-dev.service
25ms colord.service
20ms rtkit-daemon.service
18ms systemd-random-seed.service
14ms systemd-binfmt.service
13ms user-runtime-dir@1000.service
9ms dev-hugepages.mount
9ms dev-mqueue.mount
9ms systemd-remount-fs.service
8ms systemd-update-utmp.service
8ms sys-kernel-debug.mount
8ms systemd-sysctl.service
8ms sys-kernel-tracing.mount
8ms kmod-static-nodes.service
7ms modprobe@drm.service
5ms systemd-user-sessions.service
4ms sys-fs-fuse-connections.mount
4ms proc-sys-fs-binfmt_misc.mount
3ms tmp.mount
1ms sys-kernel-config.mount
[\code]
-
Themen Author - Neues Foren Mitglied
- Beiträge: 13
- Registriert: Donnerstag 4. April 2019, 21:07
- CPU: Intel Core 2 Duo CP E8400 3.00GHz
- GPU: Sapphire 11166-67-20G ATI Radeon HD 5450 Grafik Prozessor
- Kernel: 5.0.5-1
- Desktop-Variante: Manjaro KDE 5
- GPU Treiber: Free
- Hat sich bedankt: 2 Mal
Re: Manjaro nach Update sehr langsam
und hier noch:
journalctl -p err -b
journalctl -p err -b
Code: Alles auswählen
-- Logs begin at Wed 2020-06-24 12:12:24 CEST, end at Mon 2020-08-03 09:45:41 CEST. --
Aug 03 09:41:07 Manjaro-PC kernel: sp5100-tco sp5100-tco: Watchdog hardware is disabled
Aug 03 09:41:09 Manjaro-PC kernel: nvidia-gpu 0000:07:00.3: i2c timeout error e0000000
Aug 03 09:41:09 Manjaro-PC kernel: ucsi_ccg 0-0008: i2c_transfer failed -110
Aug 03 09:41:09 Manjaro-PC kernel: ucsi_ccg 0-0008: ucsi_ccg_init failed - -110
Aug 03 09:41:13 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:41:13 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:41:14 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:41:15 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:41:15 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:41:16 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:41:38 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:41:38 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:41:39 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:41:39 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:41:40 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:41:40 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:42:03 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:42:03 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:42:04 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:42:04 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:42:05 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:42:05 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:42:34 Manjaro-PC systemd[1081]: Failed to start Virtual filesystem service - Apple File Conduit monitor.
Aug 03 09:42:34 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:42:35 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:42:35 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:42:35 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:42:36 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:42:36 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:42:59 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:43:00 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:43:00 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:43:01 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:43:01 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:43:01 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:43:24 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:43:25 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:43:25 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:43:26 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:43:26 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:43:26 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:43:49 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:43:50 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:43:50 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:43:51 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:43:51 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:43:51 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:43:56 Manjaro-PC systemd[1081]: tracker-store.service: Failed to add control inotify watch descriptor for>
Aug 03 09:44:08 Manjaro-PC kwin_x11[1179]: inotify_add_watch(/home/marc/.config/plasmarc) failed: (No space left on>
Aug 03 09:44:08 Manjaro-PC kwin_x11[1179]: inotify_add_watch(/usr/share/plasma/desktoptheme/oxygen/metadata.desktop>
Aug 03 09:44:08 Manjaro-PC kwin_x11[1179]: inotify_add_watch(/home/marc/.local/share/icons/buuf-icons-for-plasma/in>
Aug 03 09:44:14 Manjaro-PC org_kde_powerdevil[1268]: inotify_add_watch(/etc) failed: (No space left on device)
Aug 03 09:44:14 Manjaro-PC org_kde_powerdevil[1268]: inotify_add_watch(/etc/fstab) failed: (No space left on device)
Aug 03 09:44:14 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:44:15 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:44:15 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:44:16 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:44:16 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:44:16 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:44:39 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:44:40 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:44:40 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:44:41 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:44:41 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Aug 03 09:44:41 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
[\code]
Re: Manjaro nach Update sehr langsam
Ist wahrscheinlich nicht gestartet.
Code: Alles auswählen
systemctl enable upower.service && systemctl start upower.service
Das kann man anscheinend deaktivieren mit
Code: Alles auswählen
sudo systemctl disable NetworkManager-wait-online.service
-
Themen Author - Neues Foren Mitglied
- Beiträge: 13
- Registriert: Donnerstag 4. April 2019, 21:07
- CPU: Intel Core 2 Duo CP E8400 3.00GHz
- GPU: Sapphire 11166-67-20G ATI Radeon HD 5450 Grafik Prozessor
- Kernel: 5.0.5-1
- Desktop-Variante: Manjaro KDE 5
- GPU Treiber: Free
- Hat sich bedankt: 2 Mal
Re: Manjaro nach Update sehr langsam
Das wird abgebrochen mit Fehlermeldung.Josef_K hat geschrieben: ↑Montag 3. August 2020, 14:28Ist wahrscheinlich nicht gestartet.Sollte zumindest dieses Problem beheben.Code: Alles auswählen
systemctl enable upower.service && systemctl start upower.service
Failed to add a watch for /run/systemd/ask-password: inotify watch limit reached Job for upower.service failed because the control process exited with error code. See "systemctl status upower.service" and "journalctl -xe" for details.
systemctl status upower.service:
Code: Alles auswählen
upower.service - Daemon for power management
Loaded: loaded (/usr/lib/systemd/system/upower.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2020-08-04 09:31:37 CEST; 59s ago
Docs: man:upowerd(8)
Process: 3146 ExecStart=/usr/lib/upowerd (code=exited, status=127)
Main PID: 3146 (code=exited, status=127)
Aug 04 09:31:37 Manjaro-PC systemd[1]: upower.service: Scheduled restart job, restart counter is at 5.
Aug 04 09:31:37 Manjaro-PC systemd[1]: Stopped Daemon for power management.
Aug 04 09:31:37 Manjaro-PC systemd[1]: upower.service: Start request repeated too quickly.
Aug 04 09:31:37 Manjaro-PC systemd[1]: upower.service: Failed with result 'exit-code'.
Aug 04 09:31:37 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
Code: Alles auswählen
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-issues-and-assistance
--
-- Automatic restarting of the unit upower.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Aug 04 09:19:24 Manjaro-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=upower comm>
Aug 04 09:19:24 Manjaro-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=upower comm=>
Aug 04 09:19:24 Manjaro-PC systemd[1]: Stopped Daemon for power management.
-- Subject: A stop job for unit upower.service has finished
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-issues-and-assistance
--
-- A stop job for unit upower.service has finished.
--
-- The job identifier is 5878 and the job result is done.
Aug 04 09:19:24 Manjaro-PC systemd[1]: upower.service: Start request repeated too quickly.
Aug 04 09:19:24 Manjaro-PC systemd[1]: upower.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-issues-and-assistance
--
-- The unit upower.service has entered the 'failed' state with result 'exit-code'.
Aug 04 09:19:24 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
-- Subject: A start job for unit upower.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-issues-and-assistance
--
-- A start job for unit upower.service has finished with a failure.
--
-- The job identifier is 5878 and the job result is failed.
Aug 04 09:19:28 Manjaro-PC dbus-daemon[685]: [system] Failed to activate service 'org.freedesktop.UPower': timed ou>
Aug 04 09:19:28 Manjaro-PC dbus-daemon[685]: [system] Activating via systemd: service name='org.freedesktop.UPower'>
Aug 04 09:19:28 Manjaro-PC systemd[1]: upower.service: Start request repeated too quickly.
Aug 04 09:19:28 Manjaro-PC systemd[1]: upower.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-issues-and-assistance
--
-- The unit upower.service has entered the 'failed' state with result 'exit-code'.
Aug 04 09:19:28 Manjaro-PC systemd[1]: Failed to start Daemon for power management.
-- Subject: A start job for unit upower.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-issues-and-assistance
--
-- A start job for unit upower.service has finished with a failure.
--
-- The job identifier is 5970 and the job result is failed.
habe ich auch schon gemacht, bringt auch leider nichts...Das kann man anscheinend deaktivieren mithttps://forum.manjaro.org/t/networkmana ... fix/150120Code: Alles auswählen
sudo systemctl disable NetworkManager-wait-online.service
Re: Manjaro nach Update sehr langsam
Mein Fehler. Sollte mit sudo ausgeführt werden:
Code: Alles auswählen
sudo systemctl start upower.service
-
Themen Author - Neues Foren Mitglied
- Beiträge: 13
- Registriert: Donnerstag 4. April 2019, 21:07
- CPU: Intel Core 2 Duo CP E8400 3.00GHz
- GPU: Sapphire 11166-67-20G ATI Radeon HD 5450 Grafik Prozessor
- Kernel: 5.0.5-1
- Desktop-Variante: Manjaro KDE 5
- GPU Treiber: Free
- Hat sich bedankt: 2 Mal
Re: Manjaro nach Update sehr langsam
das hatte ich natürlich getanJosef_K hat geschrieben: ↑Dienstag 4. August 2020, 13:49Mein Fehler. Sollte mit sudo ausgeführt werden:Code: Alles auswählen
sudo systemctl start upower.service
Vielen Dank für deine/eure Hilfe. Ich habe den PC neu aufgesetzt, da ich so nicht produktiv arbeiten konnte. Jetzt läuft wieder alles normal.