Mageia forum

by **Erik** » Sep 27th, '17, 15:09

Since Mageia 6 came out, I have been using Plasma now and in spite of many updates the login is still very, very slow. It takes up one minute to login! Rosa 9 with the new Plasma is much faster. I even deleted all Plasma settings that I could find: .kde, .kde4, .kded, .cache, the settings in .local/share, and in .config. Thus I got a fresh Plasma installation, but the login time is still the same. What kind of setting must I change? My graphics card is "Intel 810 and later".

Besides the boot time is 45 seconds. Is not that too slow also? My Rosa 8.1 installation on the same computer uses 35 seconds for boot and 25 for login; the Mint Mate installation uses 20 seconds for both.

Is there some setting that is wrong for Plasma?

Greetings.

Erik

by **doktor5000** » Sep 27th, '17, 16:25

Well, as you don't provide any other details, my reply would be: no, neither boot time nor login time are slow here, boot time is 10 seconds and login time is something slightly above 10 seconds.

by **Erik** » Sep 27th, '17, 16:50

Dear Doktor,

I have no idea what information would be helpful to you. Please enlighten me, and I shall give you all information yo may need.

Greetings,

Erik

by **benmc** » Sep 27th, '17, 20:57

Hi Erik,

you may want to try

Code: Select all: systemd-analyze blame

it should return a list of services and their time to load at boot.

by **Erik** » Sep 27th, '17, 23:30

Dear Ben,

the result of systemd-analyze blame is:

Code: Select all: [erikjan@ejvw ~]$ systemd-analyze blame 11.557s shorewall.service 9.639s systemd-journal-flush.service 9.185s teamviewerd.service 8.267s postfix.service 6.904s NetworkManager-wait-online.service 4.925s mandriva-everytime.service 4.778s systemd-udev-settle.service 4.454s dev-sda1.device 4.076s NetworkManager.service 3.939s network-up.service 3.700s proc-fs-nfsd.mount 3.533s fedora-loadmodules.service 2.736s fedora-readonly.service 2.211s gssproxy.service 2.141s cups.service 1.750s mga-bg-res.service 1.668s upower.service 1.560s systemd-logind.service 1.559s resolvconf.service 1.558s nscd.service 1.521s rpcbind.service 1.481s fedora-storage-init.service 1.477s bluetooth.service 1.248s network.service 987ms systemd-resolved.service 976ms chronyd.service 904ms avahi-daemon.service lines 1-27

All these services are necessary, I suppose, and I don't know which one are unnecessary.

I am more surprised by the fact that plasma needs so much time. Is there a log of login too?

Thank you for your suggestion.

Erik

by **benmc** » Sep 28th, '17, 00:59

as a comparison, heres mine:

Code: Select all: $ systemd-analyze blame 12.454s shorewall.service 11.201s shorewall6.service 7.408s plymouth-quit-wait.service 6.863s systemd-udev-settle.service 5.627s cups.service 3.662s mandriva-everytime.service 3.658s network.service 3.651s network-up.service 3.301s upower.service 3.301s udisks.service 3.299s chronyd.service 3.281s acpid.service 3.211s systemd-journal-flush.service 3.136s cpupower.service 3.136s mga-bg-res.service 3.115s ksm.service 3.104s systemd-logind.service 3.085s capi4linux.service 3.057s saslauthd.service 3.049s avahi-daemon.service 2.452s resolvconf.service 2.133s systemd-journald.service 1.535s systemd-fsck@dev-disk-by\x2duuid-6994c3e9\x2da383\x2d41d5\x2db8e2\x2d1543c964b902.service 1.259s virtualbox.service 1.251s colord.service 1.216s postfix.service 1.200s fedora-readonly.service 1.200s systemd-udevd.service 1.181s udisks2.service 1.021s systemd-vconsole-setup.service 995ms polkit.service 990ms systemd-tmpfiles-setup-dev.service 554ms tmp.mount 534ms sys-kernel-debug.mount 534ms dev-hugepages.mount 533ms dev-mqueue.mount 502ms systemd-udev-trigger.service 501ms systemd-remount-fs.service 410ms iptables.service 376ms systemd-backlight@backlight:acpi_video0.service 303ms systemd-sysctl.service 235ms mandriva-save-dmesg.service 201ms media-win_d.mount 177ms systemd-user-sessions.service 165ms partmon.service 151ms systemd-modules-load.service 140ms user@500.service 126ms ip6tables.service 125ms home.mount 115ms ksmtuned.service 88ms systemd-update-utmp.service 72ms plymouth-read-write.service 64ms fedora-loadmodules.service 59ms msec.service 50ms systemd-random-seed.service 43ms dev-disk-by\x2duuid-e1450db3\x2d1cd9\x2d417b\x2d99a4\x2d512be6c1db9c.swap 34ms rtkit-daemon.service 30ms systemd-tmpfiles-setup.service 24ms systemd-tmpfiles-clean.service 21ms kmod-static-nodes.service 3ms plymouth-start.service 2ms fedora-wait-storage.service 1ms systemd-update-utmp-runlevel.service 816us sys-fs-fuse-connections.mount

System is Core i5, 8G ram, onboard intel Graphics, spinning disk, auto login enabled, Mga5 KDE4 (still thinking about upgrading

)
I power the unit up in the morning, go away to do stuff and then come back to unit and leave running all day, so for me, boot time is not an issue.

I am sure others here will advise which (if any) services can be disabled at boot/login

edit: you may want to try that command in both mint and rosa, to see which services are (or not) running.

by **janpihlgren** » Sep 28th, '17, 04:37

I also have a very slow start.
Here is my result:

Code: Select all: [jan@Humlan ~]$ systemd-analyze blame 1min 3.017s webmin.service 34.091s mysqld.service 30.631s vmware-workstation-server.service 29.196s httpd.service 26.885s libvirtd.service 24.943s nmb.service 18.497s dkms-autorebuild.service 17.425s systemd-journal-flush.service 17.352s teamviewerd.service 14.216s mandriva-everytime.service 14.039s cups.service 11.245s shorewall.service 11.051s network-up.service 10.450s postfix.service 10.369s systemd-udev-settle.service 5.732s ModemManager.service 5.612s dev-sda7.device 5.370s dev-sda5.device 4.982s upower.service 4.528s network.service 4.524s rsyslog.service 4.524s nscd.service 4.523s acpid.service 4.424s shorewall6.service 4.385s systemd-logind.service 4.283s sshd.service 4.146s lm_sensors.service 4.139s bluetooth.service 4.059s saslauthd.service 4.025s avahi-daemon.service 3.858s hostapd.service 3.732s systemd-fsck@dev-disk-by\x2duuid-eb452795\x2d7d78\x2d4d75\x2d8296\x2d843eb7719009.ser 3.726s cpupower.service 3.716s rpcbind.service 3.716s virtualbox.service 3.715s resolvconf.service 3.715s partmon.service 3.714s gssproxy.service 3.703s msec.service 3.703s mga-bg-res.service 2.717s systemd-fsck@dev-disk-by\x2duuid-0ce7a917\x2d23b5\x2d4b12\x2d8d4d\x2dbeed9e99ba72.ser 2.599s systemd-resolved.service 2.333s udisks2.service 2.227s sensord.service 2.202s squeezeboxserver.service 2.064s systemd-fsck@dev-disk-by\x2duuid-16a3e249\x2d6a17\x2d4b95\x2d840b\x2d67305e56a8de.ser 1.998s fedora-readonly.service 1.923s systemd-fsck@dev-disk-by\x2duuid-4a645cf2\x2db059\x2d4018\x2d98a3\x2ded2b0030736c.ser 1.620s fedora-loadmodules.service 1.256s fedora-storage-init.service 1.116s drakxtools_http.service 917ms systemd-vconsole-setup.service 912ms systemd-journald.service 828ms systemd-networkd.service 778ms polkit.service 671ms systemd-fsck-root.service 658ms systemd-udevd.service 646ms systemd-tmpfiles-setup-dev.service 641ms systemd-random-seed.service 589ms plymouth-quit.service 589ms plymouth-quit-wait.service 537ms tmp.mount 494ms mandriva-save-dmesg.service 463ms dev-disk-by\x2duuid-56bb3f65\x2d3e42\x2d4177\x2d83f7\x2d42d06e37b4f4.swap 438ms sys-kernel-debug.mount 408ms systemd-timesyncd.service 355ms fedora-storage-init-late.service 355ms plymouth-read-write.service 339ms vmware-USBArbitrator.service 331ms proftpd.service 314ms systemd-hostnamed.service 305ms misc.mount 301ms colord.service 278ms systemd-fsck@dev-disk-by\x2duuid-6d9d731b\x2db169\x2d485e\x2d9a8c\x2dc82c0c971d5f.ser 243ms systemd-tmpfiles-setup.service 210ms user@970.service 185ms systemd-sysctl.service 181ms kmod-static-nodes.service 180ms systemd-modules-load.service 147ms storage.mount 139ms systemd-user-sessions.service 101ms systemd-update-utmp.service 89ms systemd-udev-trigger.service 89ms user@10001.service 86ms systemd-remount-fs.service 77ms var-www.mount 70ms systemd-backlight@backlight:acpi_video0.service 55ms systemd-tmpfiles-clean.service 54ms home.mount 51ms systemd-backlight@backlight:nv_backlight.service 47ms systemd-rfkill.service 42ms libvirt-guests.service 26ms dracut-shutdown.service 17ms rtkit-daemon.service 15ms plymouth-start.service 7ms fedora-wait-storage.service 6ms dev-hugepages.mount 6ms systemd-update-utmp-runlevel.service 5ms dev-mqueue.mount 4ms sys-fs-fuse-connections.mount 4ms systemd-fsck@dev-disk-by\x2duuid-2aab70ef\x2d0865\x2d4dfe\x2d8aaa\x2d88014416ebf3.ser

Whats wrong?

by **isadora** » Sep 28th, '17, 08:54

Please use {Code]-tags for command-output, NOT [Quote]-tags.
Changed it for you, thanks ahead.

by **unklar** » Sep 28th, '17, 11:10

Here are my values from the current cauldron on a desktop.

: systemd.png (1.5 MiB) Viewed 5054 times

There is no generally binding rule for a slow start. Everyone has to decide for himself whether he needs the services.
It is imperative that the systemd-analyze critical-chain command is also used for the decision. This shows in red which services require additional time.
There is also a fundamental difference between the services used on a desktop and a laptop!

After that, I can decide if I can "disable" a service or if I can use a "mask" service
It always means reading a lot and having a lot of time....

According to taste
https://www.certdepot.net/rhel7-get-started-systemd/
https://freedesktop.org/wiki/Software/systemd/
http://0pointer.de/blog/projects/blame-game.html
https://freedesktop.org/wiki/Software/s ... Debugging/

by **doktor5000** » Sep 28th, '17, 12:31

janpihlgren wrote:I also have a very slow start.
[...]
Whats wrong?

Please don't highjack other threads and start a separate one for your issues. This one is about slow login time, or at least that was what OP asked about primarily.

In your case the problem is obviously webmin which takes over a minute to start up.

by **wintpe** » Oct 2nd, '17, 15:33

my four year old laptop is about 10 seconds to boot and about 6 seconds to login (I7, 2 core, 4 gig ram, SSD)

my 5 year old desktop is about the same. (Phenom2-1100T, 16gig ram, SSD x 2)

the longest services to start up are network-up and mandriva -everytime at 4 and 2 seconds.

otherwise the rest are all sub 500ms.

So what hardware are you running Eric, (harddisk, CPU, memory, Chipset, all have a part to play in the time an OS takes to start)

you startup times look like something or everything is not performing very well.

it might be one component acting as a bottleneck.

I noticed everyone posting problems, seems to think us helpers are psychic, and can work out what you are running on, hence why i started the help us to help you thread, which seems to be ignored, or you have already decided it cant be a problem with my PC.

If we had at least a basic knowledge of you platform we could instantly see if the performance is expected for the hardware or way bellow par and hence an issue.

perhaps install sysstat package and run iostat -xN

as disk is now one of the slowest devices and can impact on performance, especially if its IDE.

It could be that a driver in the later kernels has an issue with a specific bit of hardware, and is going into a wait, I know if i connect one of my external disks incorrectly and the OS tries to probe it, the whole os boot up time gets lengthened, just because that disk is not coming on line and is hanging.
so look at /var/log/messages or dmesg and see if there are any io errors reported

regards peter

by **Erik** » Oct 2nd, '17, 16:57

Dear Peter,
thank you for your remarks. I have downloaded lshw and sysstat. For good measure I added systemd-analyze time and blame. The results are:

Code: Select all: -bash-4.3# lshw ejvw.maincomputer description: Desktop Computer product: To Be Filled By O.E.M. (To Be Filled By O.E.M.) vendor: To Be Filled By O.E.M. version: To Be Filled By O.E.M. serial: To Be Filled By O.E.M. width: 4294967295 bits capabilities: smbios-2.7 dmi-2.7 smp vsyscall32 configuration: boot=normal chassis=desktop family=To Be Filled By O.E.M. sku=To Be Filled By O.E.M. uuid=00020003-0004-0005-0006-000700080009 *-core description: Motherboard product: H81M-HDS vendor: ASRock physical id: 0 serial: M80-4B025503402 *-firmware description: BIOS vendor: American Megatrends Inc. physical id: 0 version: P1.90 date: 07/02/2014 size: 64KiB capacity: 4032KiB capabilities: pci upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification uefi *-cache description: L1 cache physical id: 8 slot: CPU Internal L1 size: 128KiB capacity: 128KiB capabilities: internal write-back configuration: level=1 *-cpu description: CPU product: Intel(R) Pentium(R) CPU G3220 @ 3.00GHz vendor: Intel Corp. physical id: 9 bus info: cpu@0 version: Intel(R) Pentium(R) CPU G3220 @ 3.00GHz slot: CPUSocket size: 3GHz capacity: 3800MHz width: 64 bits clock: 100MHz capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer xsave rdrand lahf_lm abm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust erms invpcid xsaveopt dtherm arat pln pts cpufreq configuration: cores=2 enabledcores=2 threads=2 *-cache:0 description: L2 cache physical id: a slot: CPU Internal L2 size: 512KiB capacity: 512KiB capabilities: internal write-back unified configuration: level=2 *-cache:1 description: L3 cache physical id: b slot: CPU Internal L3 size: 3MiB capacity: 3MiB capabilities: internal write-back unified configuration: level=3 *-memory description: System Memory physical id: c slot: System board or motherboard size: 4GiB *-bank:0 description: DIMM DDR3 Synchronous 1333 MHz (0,8 ns) product: CT51264BA160BJ.C8F vendor: Conexant (Rockwell) physical id: 0 serial: 16082108 slot: ChannelA-DIMM0 size: 4GiB width: 64 bits clock: 1333MHz (0.8ns) *-bank:1 description: DIMM [empty] product: [Empty] vendor: [Empty] physical id: 1 serial: [Empty] slot: ChannelB-DIMM0 *-pci description: Host bridge product: 4th Gen Core Processor DRAM Controller vendor: Intel Corporation physical id: 100 bus info: pci@0000:00:00.0 version: 06 width: 32 bits clock: 33MHz configuration: driver=hsw_uncore resources: irq:0 *-display description: VGA compatible controller product: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@0000:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:25 memory:f0000000-f03fffff memory:e0000000-efffffff ioport:f000(size=64) memory:c0000-dffff *-usb:0 description: USB controller product: 8 Series/C220 Series Chipset Family USB xHCI vendor: Intel Corporation physical id: 14 bus info: pci@0000:00:14.0 version: 05 width: 64 bits clock: 33MHz capabilities: pm msi xhci bus_master cap_list configuration: driver=xhci_hcd latency=0 resources: irq:26 memory:f0600000-f060ffff *-usbhost:0 product: xHCI Host Controller vendor: Linux 4.9.50-desktop-1.mga6 xhci-hcd physical id: 0 bus info: usb@1 logical name: usb1 version: 4.09 capabilities: usb-2.00 configuration: driver=hub slots=10 speed=480Mbit/s *-usb:0 description: Video product: Webcam C310 vendor: Logitech, Inc. physical id: 1 bus info: usb@1:1 version: 0.12 serial: D4BD09A0 capabilities: usb-2.00 configuration: driver=snd-usb-audio maxpower=500mA speed=480Mbit/s *-usb:1 description: Printer product: DCP-J152W vendor: Brother physical id: 2 bus info: usb@1:2 version: 1.00 serial: BROM3F262965 capabilities: usb-2.00 bidirectional configuration: driver=usblp maxpower=2mA speed=480Mbit/s *-usb:2 description: Printer product: HL-2130 series vendor: Brother physical id: 5 bus info: usb@1:5 version: 1.00 serial: D4N166651 capabilities: usb-2.00 bidirectional configuration: driver=usblp maxpower=2mA speed=480Mbit/s *-usb:3 description: Mass storage device product: Mass Storage Device vendor: Generic physical id: 9 bus info: usb@1:9 version: 1.00 serial: 058F63666471 capabilities: usb-2.00 scsi configuration: driver=usb-storage maxpower=100mA speed=480Mbit/s *-usbhost:1 product: xHCI Host Controller vendor: Linux 4.9.50-desktop-1.mga6 xhci-hcd physical id: 1 bus info: usb@2 logical name: usb2 version: 4.09 capabilities: usb-3.00 configuration: driver=hub slots=2 speed=5000Mbit/s *-communication description: Communication controller product: 8 Series/C220 Series Chipset Family MEI Controller #1 vendor: Intel Corporation physical id: 16 bus info: pci@0000:00:16.0 version: 04 width: 64 bits clock: 33MHz capabilities: pm msi bus_master cap_list configuration: driver=mei_me latency=0 resources: irq:30 memory:f061a000-f061a00f *-usb:1 description: USB controller product: 8 Series/C220 Series Chipset Family USB EHCI #2 vendor: Intel Corporation physical id: 1a bus info: pci@0000:00:1a.0 version: 05 width: 32 bits clock: 33MHz capabilities: pm debug ehci bus_master cap_list configuration: driver=ehci-pci latency=0 resources: irq:16 memory:f0618000-f06183ff *-usbhost product: EHCI Host Controller vendor: Linux 4.9.50-desktop-1.mga6 ehci_hcd physical id: 1 bus info: usb@3 logical name: usb3 version: 4.09 capabilities: usb-2.00 configuration: driver=hub slots=2 speed=480Mbit/s *-usb description: USB hub vendor: Intel Corp. physical id: 1 bus info: usb@3:1 version: 0.05 capabilities: usb-2.00 configuration: driver=hub slots=4 speed=480Mbit/s *-multimedia description: Audio device product: 8 Series/C220 Series Chipset High Definition Audio Controller vendor: Intel Corporation physical id: 1b bus info: pci@0000:00:1b.0 version: 05 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=snd_hda_intel latency=0 resources: irq:32 memory:f0610000-f0613fff *-pci:0 description: PCI bridge product: 8 Series/C220 Series Chipset Family PCI Express Root Port #1 vendor: Intel Corporation physical id: 1c bus info: pci@0000:00:1c.0 version: d5 width: 32 bits clock: 33MHz capabilities: pci pciexpress msi pm normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:16 ioport:2000(size=4096) memory:dfa00000-dfbfffff ioport:dfc00000(size=2097152) *-pci:1 description: PCI bridge product: 8 Series/C220 Series Chipset Family PCI Express Root Port #4 vendor: Intel Corporation physical id: 1c.3 bus info: pci@0000:00:1c.3 version: d5 width: 32 bits clock: 33MHz capabilities: pci pciexpress msi pm normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:19 ioport:e000(size=4096) memory:f0500000-f05fffff *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@0000:02:00.0 logical name: enp2s0 version: 0c serial: d0:50:99:59:84:c5 size: 100Mbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 ip=192.168.178.15 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s resources: irq:31 ioport:e000(size=256) memory:f0504000-f0504fff memory:f0500000-f0503fff *-pci:2 description: PCI bridge product: 8 Series/C220 Series Chipset Family PCI Express Root Port #5 vendor: Intel Corporation physical id: 1c.4 bus info: pci@0000:00:1c.4 version: d5 width: 32 bits clock: 33MHz capabilities: pci pciexpress msi pm normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:16 memory:f0400000-f04fffff *-usb description: USB controller product: ASM1042A USB 3.0 Host Controller vendor: ASMedia Technology Inc. physical id: 0 bus info: pci@0000:03:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: msi msix pm pciexpress xhci bus_master cap_list configuration: driver=xhci_hcd latency=0 resources: irq:16 memory:f0400000-f0407fff *-usbhost:0 product: xHCI Host Controller vendor: Linux 4.9.50-desktop-1.mga6 xhci-hcd physical id: 0 bus info: usb@4 logical name: usb4 version: 4.09 capabilities: usb-2.00 configuration: driver=hub slots=2 speed=480Mbit/s *-usb description: Bluetooth wireless interface product: CSR8510 A10 vendor: Cambridge Silicon Radio, Ltd physical id: 2 bus info: usb@4:2 version: 88.91 capabilities: bluetooth usb-2.00 configuration: driver=btusb maxpower=100mA speed=12Mbit/s *-usbhost:1 product: xHCI Host Controller vendor: Linux 4.9.50-desktop-1.mga6 xhci-hcd physical id: 1 bus info: usb@6 logical name: usb6 version: 4.09 capabilities: usb-3.00 configuration: driver=hub slots=2 speed=5000Mbit/s *-usb:2 description: USB controller product: 8 Series/C220 Series Chipset Family USB EHCI #1 vendor: Intel Corporation physical id: 1d bus info: pci@0000:00:1d.0 version: 05 width: 32 bits clock: 33MHz capabilities: pm debug ehci bus_master cap_list configuration: driver=ehci-pci latency=0 resources: irq:23 memory:f0617000-f06173ff *-usbhost product: EHCI Host Controller vendor: Linux 4.9.50-desktop-1.mga6 ehci_hcd physical id: 1 bus info: usb@5 logical name: usb5 version: 4.09 capabilities: usb-2.00 configuration: driver=hub slots=2 speed=480Mbit/s *-usb description: USB hub vendor: Intel Corp. physical id: 1 bus info: usb@5:1 version: 0.05 capabilities: usb-2.00 configuration: driver=hub slots=6 speed=480Mbit/s *-isa description: ISA bridge product: C220 Series Chipset Family H81 Express LPC Controller vendor: Intel Corporation physical id: 1f bus info: pci@0000:00:1f.0 version: 05 width: 32 bits clock: 33MHz capabilities: isa bus_master cap_list configuration: driver=lpc_ich latency=0 resources: irq:0 *-storage description: SATA controller product: 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] vendor: Intel Corporation physical id: 1f.2 bus info: pci@0000:00:1f.2 version: 05 width: 32 bits clock: 66MHz capabilities: storage msi pm ahci_1.0 bus_master cap_list configuration: driver=ahci latency=0 resources: irq:24 ioport:f0b0(size=8) ioport:f0a0(size=4) ioport:f090(size=8) ioport:f080(size=4) ioport:f060(size=32) memory:f0616000-f06167ff *-serial description: SMBus product: 8 Series/C220 Series Chipset Family SMBus Controller vendor: Intel Corporation physical id: 1f.3 bus info: pci@0000:00:1f.3 version: 05 width: 64 bits clock: 33MHz configuration: driver=i801_smbus latency=0 resources: irq:18 memory:f0615000-f06150ff ioport:f040(size=32) *-scsi physical id: 1 bus info: scsi@5 logical name: scsi5 capabilities: scsi-host configuration: driver=usb-storage -bash-4.3# iostat -xN Linux 4.9.50-desktop-1.mga6 (ejvw.maincomputer) 02-10-17 _x86_64_ (2 CPU) avg-cpu: %user %nice %system %iowait %steal %idle 1,07 0,58 0,44 3,86 0,00 94,05 Device: rrqm/s wrqm/s r/s w/s rkB/s wkB/s avgrq-sz avgqu-sz await r_await w_await svctm %util sda 0,32 1,08 58,55 0,98 1767,28 22,61 60,14 0,18 2,98 2,55 28,27 1,20 7,14 sdb 0,00 0,00 0,07 0,00 2,08 0,00 58,88 0,00 0,40 0,40 0,00 0,19 0,00 -bash-4.3# systemd-analyze time Startup finished in 3.186s (kernel) + 33.663s (userspace) = 36.850s -bash-4.3# systemd-analyze blame 9.534s postfix.service 7.156s NetworkManager-wait-online.service 4.168s systemd-udev-settle.service 3.778s network-up.service 3.772s dev-sda1.device 3.362s mandriva-everytime.service 3.304s NetworkManager.service 3.079s teamviewerd.service 2.178s mga-bg-res.service 2.154s cups.service 2.030s fedora-readonly.service 1.903s upower.service 1.869s gssproxy.service 1.423s fedora-loadmodules.service 1.411s resolvconf.service 1.396s systemd-vconsole-setup.service 1.292s network.service 1.283s proc-fs-nfsd.mount 1.236s nfs-server.service 1.144s fedora-storage-init.service 1.090s chronyd.service 1.010s udisks2.service 1.003s iptables.service 1.003s nscd.service 989ms cpupower.service 980ms rsyslog.service 832ms systemd-tmpfiles-setup-dev.service 758ms systemd-logind.service 733ms bluetooth.service 721ms rpcbind.service 593ms systemd-fsck-root.service 489ms avahi-daemon.service 453ms systemd-udevd.service 413ms systemd-networkd.service 409ms systemd-rfkill.service 393ms systemd-fsck@dev-disk-by\x2duuid-b3677ebc\x2d9510\x2d44bd\x2d97de\x2d6c6cc90b1ae9.service 391ms home.mount 359ms systemd-sysctl.service 348ms nfs-idmapd.service 276ms user@492.service 276ms msec.service 263ms systemd-tmpfiles-setup.service 258ms systemd-journald.service 253ms dev-disk-by\x2duuid-36f42edc\x2d7181\x2d4d30\x2d9e1d\x2d141556393a2a.swap 235ms partmon.service 190ms rpc-statd.service 182ms systemd-timesyncd.service 172ms systemd-journal-flush.service 168ms systemd-random-seed.service 164ms polkit.service 162ms dev-hugepages.mount 156ms nfs-config.service 151ms mandriva-save-dmesg.service 148ms systemd-udev-trigger.service 142ms fedora-storage-init-late.service 140ms systemd-resolved.service 137ms rtkit-daemon.service 126ms user@500.service 107ms xinetd.service 105ms systemd-remount-fs.service 104ms systemd-hostnamed.service 88ms plymouth-read-write.service 85ms nfs-mountd.service 83ms systemd-update-utmp.service 79ms plymouth-quit.service 73ms systemd-backlight@backlight:acpi_video0.service 72ms systemd-modules-load.service 71ms ip6tables.service 68ms plymouth-quit-wait.service 64ms acpid.service 52ms kmod-static-nodes.service 50ms systemd-tmpfiles-clean.service 43ms rpc-statd-notify.service 39ms dev-mqueue.mount 38ms sys-kernel-debug.mount 23ms var-lib-nfs-rpc_pipefs.mount 16ms systemd-user-sessions.service 14ms dracut-shutdown.service 12ms plymouth-start.service 5ms fedora-wait-storage.service 3ms systemd-update-utmp-runlevel.service 1ms sys-fs-fuse-connections.mount 1ms tmp.mount

All this is about boot time. I hope you can conclude from all this why login takes a long time too.

I hope all this will tell you what you need to know.

Thank for your offer to help.

Greetings,

Erik.

by **doktor5000** » Oct 3rd, '17, 02:04

You should also run

Code: Select all: systemd-analyze plot > boot.svg

and attach the resulting file boot.svg here.
And you should take a look at the services that take the most time to start, from your earlier output:

[erikjan@ejvw ~]$ systemd-analyze blame
11.557s shorewall.service
9.639s systemd-journal-flush.service
9.185s teamviewerd.service
8.267s postfix.service
6.904s NetworkManager-wait-online.service

Those make up for for ~45 seconds, the question being whether some of those are started in parallel or not.

by **Erik** » Oct 3rd, '17, 07:50

Here is boot.svg:

https://www.dropbox.com/s/hm35o4sn4hibdtg/boot.svg?dl=0

Thank you for your help.

Erik

by **wintpe** » Oct 3rd, '17, 10:45

not all that i asked, but I can conclude from the hw it should be performing similar to my laptop.

what hard disks do you have ?

and dmesg output, something is slowing that system down alot.

install rsyslog, if its not installed already, and check /var/log/messages for any thing complaining .

I know first time login to mga6 can be slow, but once the dot files/directories are created its usually very quick from then on.

regards peter

by **Erik** » Oct 3rd, '17, 14:27

Dear Peter,

my HDD is just a run of the mill disk drive, no SSD, SATA connection.

Here is dmesg and messages of the latest boot and login:

https://www.dropbox.com/s/puama1u559vvj ... n.txt?dl=0

I had a look myself; there are a lot off errors. I made a new user; the login took about 8 seconds. I copied all my documents, pictures (a lot) and videos to the new user, and after this the login took about thirty seconds. so possibly there are too many files in my home. I did not yet copy my Thunderbird and Firefox directories.

thank you for your help.

Greetings,

Erik

by **wintpe** » Oct 3rd, '17, 16:58

OK just a run of the mill.

many of the modern high capacity drives are no longer optimized for performance, but size instead, older sata drives can be pretty bad.

even though linux is a very efficient OS compared to say windows, as later versions come along, hw requirements do go up.

with a empty home drive login was 30 seconds, was that the first time, or second, as I said first time is usually much slower as it initializes all the dot files.

it should be much quicker, on second time, my laptop on SSD is 6 seconds.

I know I should not push buying hardware as a solution to your problem, but you would be amazed (if it is related to HD performance) how much faster things are with an SSD.

you dont need a big one, a 128gig to host the OS, then make your run of the mill one your data drive.

anyway do a speed test of your harddisk.

i just ran this on a redhat 6 one at work with a 10K sas on mirrored raid and this is the reading I got.

you need a reasonable size otherwise you get a buffered reading which is inaccurate.

you should expect similar from a modern sata, whereas SSD will be 2.5 times faster.

run this as root

dd if=/dev/zero of=/home/test count=1024M
^C46676593+0 records in
46676593+0 records out
23898415616 bytes (24 GB) copied, 170.451 s, 140 MB/s

I control C's it as i got fed up waiting.

regards peter

by **Erik** » Oct 3rd, '17, 21:16

Dear Peter,

the result is:

Code: Select all: -bash-4.3# dd if=/dev/zero of=/home/test count=1024M dd: schrijven naar '/home/test': Geen ruimte meer over op apparaat 516795161+0 records gelezen 516795160+0 records geschreven 264599121920 bytes (265 GB, 246 GiB) copied, 2108,23 s, 126 MB/s -bash-4.3#

Is your conclusion that one minute to boot and one minute to login are normal?

Is there no remedy for all the errors in "messages"?

Thank you for your help.

Greetings.

Erik

by **wintpe** » Oct 4th, '17, 11:33

OK nothing wrong with your disk, could be a little faster but its not the problem.

the problem is multiple fold from what I can see.

network mangler is having issues with your ethernet network cards, and is taking way too long to initialise them.

also looks like you have some visualized network device that is also taking time.

Are you running some visualization, or did you try some at some point. as it looks like its still hanging around.

i would suggest looking in /etc/sysconfig/network-scripts and seeing what ifup-xxxxx files there are.

also run "ifconfig -a" see if there are more network devices than you expect, as according to dmesg you should just have one nic, an r8619.

networkmanager keeps complaining about a wlp3s0u2 device which would be a dlink dwa-192.

all these messages are probably part of the problem, and eliminating them will be a good start.

regards peter

by **Erik** » Oct 5th, '17, 12:11

Dear Peter,

I removed the wireless files from /etc/sysconfig/network.d and gained twenty seconds! Thank you very much! Boot time is now 35 seconds.

I do not know what a "visualized network device" is; please enlighten me.

There are also a lot of plasma errors, do you have a remedy for these also?

Thank you for your help; it is much appreciated.

Greetings,

Erik.

by **isadora** » Oct 5th, '17, 13:00

Erik, in general it is advised to create separate topics for different issues.
It makes searching in the forum easier for somebody else, who might run into the same problem in future, and chances people are picking up your issue is bigger.

by **isadora** » Oct 5th, '17, 13:01

Please, don't forget to mark the topic [SOLVED].
You can do so, by editing the subject/title in the first message in this topic.
Write [SOLVED] to the left of subject/title, thanks ahead.

by **wintpe** » Oct 5th, '17, 14:46

And im going to sum up with, there are many errors in that log file.
youve solved one.
I would ask you to think about the history your system has been through and why this solved error and the remaining ones came about.
should you rebuild and get them all solved in one hit.
well i would, but I can build and fully configure my system in a matter of 1 or two hours.

if you can id say its worth it, you should be seeing boot times on that hardware like my laptop, ie 10 and 6 seconds login or there about.

regards peter

by **Erik** » Oct 5th, '17, 20:46

Dear Peter,

thank you very much for your help. I learned a lot from you. I followed your suggestion to do a clean install of Mageia 6. When it became available I did an online upgrade instead of a clean installation, as I did with all upgrades since Mandrake 10. This, I see now, was a mistake. After the clean installation the boot time is reduced to 31 seconds, and the login to 32 seconds. My home directory being what it is, I suppose these are reasonable times.

In the mean time I also googled for plasma and its slow login. I understand that the problem is due to bugs in plasma itself, and not due to my configuration or too slow computer.

Tanks again and greetings.

Erik

by **wintpe** » Oct 9th, '17, 12:19

one last post on this Erik

consider what i said about SSD.

https://www.amazon.co.uk/DREVO-128GB-In ... 128Gig+SSD

ive bought one of these, for one of my older systems.

only £46

this is not a high end make, but still boasts 500 meg read.

that will realy boost you boot and login times, and generaly make your system more responsive.

not alot to pay, keep your spinning harddisk just for home, or maybe just make it data and keep /home on the SSD, and keep it small.

regards peter

Mageia forum

[SOLVED] superslow login with Plasma

[SOLVED] superslow login with Plasma

Re: superslow login with Plasma

Re: superslow login with Plasma

Re: superslow login with Plasma

Re: superslow login with Plasma

Re: superslow login with Plasma

Re: superslow login with Plasma

Re: superslow login with Plasma

Re: superslow login with Plasma

Re: superslow login with Plasma

Re: superslow login with Plasma

Re: superslow login with Plasma

Re: superslow login with Plasma

Re: superslow login with Plasma

Re: superslow login with Plasma

Re: superslow login with Plasma

Re: superslow login with Plasma

Re: superslow login with Plasma

Re: superslow login with Plasma

Re: superslow login with Plasma

Re: superslow login with Plasma

Re: superslow login with Plasma

Re: superslow login with Plasma

Re: superslow login with Plasma

Re: [SOLVED] superslow login with Plasma

Who is online