Initial start/desktop loads unbelievably slow WITH VIDEO / Fast Hardware / Need help

English Install/Boot/Login
1

Hi, My OPENSUSE gnome desktop/starting screen loads unbelievably slow and I know it’s an easy fix but I don’t know what to do as I am new to Linux.
I really want to make this linux distro my main OS. Just have to fix these minor problems.
It’s as if the screen is an animation the boot is waiting for (progressively getting brighter) before starting?
Have been noticing kvm: disabled by bios in top left of boot lately. tried removing it from kernel. didn’t work.

Hardware:
4.4Ghz processor
Nvidia GTX980
250GB SSD (OPENSUSE gnome installed on this drive)
4TB HDD (Currently unallocated space)
32gb ram
VIPER crosshair motherboard
sleek case

Running gnome desktop from initial OPENSUSE install
I am not running any other operating systems. JUST OPENSUSE

Drivers:
Installed latest NVIDIA drivers 352 from nvidia site using the “hard way” (RUNS VERY SMOOTH after that initial startup screen)
Default OPENSUSE drivers

Video of problem in action because words can’t accurately describe this:
[video=youtube_share;j0oHvv8ZhJo]http://youtu.be/j0oHvv8ZhJo[/video]

MANY Thanks in advance! Please help :open_mouth:

2

Hello and welcome here.

Can you please always at least explain which version of openSUSE you use.

3

If I interprete the movie correct, you have automatic login switched on. Thus it is a bit difficult to see where booting stops and login starts. Thus it is a bit difficult to decide where to look for speeding up.

4

systemd-analyze blame

will show what is taking time. It does appear the problem is before loading of gnome. Better to use the login screen rather then auto login to trace problems. Also a bit more secure

You can stop auto login from Yast - system - sysconfig editor - desktop - display manager.
I recommend it until at least you find the problem

Have you installed the propriety NVIDIA driver??

5

I see where you are coming from however I already tried disabling auto login before I posted the original problem. I thought whatever was loading so slow during startup would load prior while on log in screen. Nope! It loads that slow screen… WITH auto login disabled AND THEN loads the login screen… It’s weird. I will run that diagnostic tool and post what I see.

I installed NVIDIA drivers from the NVIDIA website. I’m not sure I need any other drivers. It was difficult to do. Had to get a few dependencies but after initial screen… The system is perfectly fine.

6

From the video it does not look like the graphic splash screen is working right. there should be an image that fades in or out. t should not be just a background. perss esc immediately after selecting the boot option to kill the splash and see the boot process

7

From systemd-analyze blame:

systemd-analyze blame
18.332s wicked.service
4.343s systemd-udev-settle.service
730ms display-manager.service
233ms apparmor.service
169ms postfix.service
131ms SuSEfirewall2_init.service
91ms SuSEfirewall2.service
45ms ModemManager.service
31ms systemd-udev-trigger.service
31ms packagekit.service
30ms systemd-udev-root-symlink.service
29ms plymouth-read-write.service
29ms systemd-tmpfiles-setup-dev.service
27ms home.mount
25ms alsa-restore.service
21ms systemd-user-sessions.service
21ms nscd.service
20ms avahi-daemon.service
19ms plymouth-start.service
19ms sys-kernel-debug.mount
18ms polkit.service
17ms dev-hugepages.mount
17ms wpa_supplicant.service

I did notice it hanging on initd for a while during splash and a problem mounting hubs of some sorts near the bottom?
Is there a command to load last boot config from opensuse terminal so I can display that info for you?

8

does not look bad how long to the login screen?

might want to look at

systemd-analyze critical-chain

it may give a better picture

wicked by the way is the new network manager. So most of the time is spent on bringing up the network

BTW you should use the code tags around any computer output. this will stop any reformatting that the forum software may do. Use the # button in the editor

9

I looked at what is taking a really long time with escape during slowwww splash screen and I see:

A start job is running for udev wait for complete device utilization

I see this when I run:

systemd-analyze critical-chain

graphical.target @51.192s
└─multi-user.target @51.192s
└─cron.service @51.192s
└─postfix.service @51.021s +170ms
└─network.target @51.020s
└─wicked.service @32.678s +18.342s
└─wickedd-nanny.service @32.673s +2ms
└─wickedd.service @32.668s +2ms
└─wickedd-dhcp6.service @32.659s +7ms
└─SuSEfirewall2_init.service @32.579s +74ms
└─basic.target @32.558s
└─timers.target @32.558s
└─systemd-tmpfiles-clean.timer @32.558s
└─sysinit.target @32.558s
└─sys-fs-fuse-connections.mount @33.978s +1ms
└─systemd-modules-load.service @118ms +4ms
└─systemd-readahead-replay.service @108ms +7ms
└─system.slice
└─-.slice

10

On 2015-07-04 14:36, uhwok3n wrote:

> Video of problem in action because words can’t accurately describe this:
>
> http://youtu.be/j0oHvv8ZhJo

It doesn’t look slow to me. It looks normal.
1 minute 12 seconds, from bios screen to desktop.

Well, you see a splash display without a progress bar, so it may seem
that it is stuck; but it is not. You can press ESC to see the text
messages that show what it is being done. Me, I disable the splash, I
prefer to see those messages. They are beautiful to me.

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

11

On 2015-07-05 01:26, uhwok3n wrote:
>
> I looked at what is taking a really long time with escape during slowwww
> splash screen and I see:
>
> #A start job is running for udev wait for complete device utilization
>
> I see this when I run:
>> systemd-analyze critical-chain

Please use code tags.


>> └─wicked.service @32.678s +18.342s

That’s the only slow thing, network: 18 seconds. And the typical culprit
is the dhcp dialog between your machine and the router. If you set up a
fixed IP it should go faster.

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

12

Sounds slow to me for his hardware

Here is my current critical


graphical.target @13.914s
└─multi-user.target @13.914s
  └─smb.service @13.875s +38ms
    └─nmb.service @3.856s +10.018s
      └─network.target @3.853s
        └─NetworkManager.service @3.817s +35ms
          └─SuSEfirewall2_init.service @3.723s +93ms
            └─basic.target @3.695s
              └─timers.target @3.694s
                └─systemd-tmpfiles-clean.timer @3.694s
                  └─sysinit.target @3.694s
                    └─apparmor.service @3.445s +248ms
                      └─systemd-tmpfiles-setup.service @3.436s +6ms
                        └─local-fs.target @3.428s
                          └─vm.mount @649ms +19ms
                            └─systemd-fsck@dev-disk-by\x2duuid-3bd79acb\x2d9f73\x2d411b\x2dacae\x2dd5c1f8debf48.service @423ms +224ms
                              └─dev-disk-by\x2duuid-3bd79acb\x2d9f73\x2d411b\x2dacae\x2dd5c1f8debf48.device @422ms

I do have a SSD so the boot is pretty fast but even before that it was in the 30 sec range

AMD 6 core FX cpu NVIDIA 630 GPU 8 gig memory

I use Networkmanager because wicked has never worked for me

I have done nothing to optimize boot speed because I so seldom boot

13

Are there certain settings I can use to optimize boot on SSD? Also had did you trade out network manager for wicked? I want to use that and then set up a static ip address. Maybe this will address my issue.

Thanks for the help so far btw. Still trying to boot faster.

14

UPDATE:

OK! I have progress in getting my boot time lowered and my splash screen in somewhat of a normal state.
Currently I disabled wicked network services, enabled Network Manager services and was very happy with the results:


systemd-analyze blame

         32.153s systemd-udev-settle.service
          8.371s NetworkManager-wait-online.service
           744ms display-manager.service
           229ms apparmor.service
           175ms postfix.service
            95ms SuSEfirewall2.service
            94ms NetworkManager.service
            68ms SuSEfirewall2_init.service
            40ms ModemManager.service
            32ms lvm2-activation-early.service
            25ms udisks2.service
            23ms systemd-udev-root-symlink.service
            21ms plymouth-read-write.service
            21ms home.mount
            20ms systemd-udev-trigger.service
            19ms alsa-restore.service
            19ms nscd.service
            18ms systemd-user-sessions.service
            18ms sys-kernel-debug.mount
            18ms systemd-fsck@dev-disk-by\x2duuid-f59ffcbc\x2d1638\x2d4c83\x2d95
            16ms dev-hugepages.mount

This shaved 9 seconds!

However… if you notice udev is taking a very very long time to load. I’ve never had this long of a boot on any OS or other linux distros, usually they are quite snappy. There must be a way to shorten this. I’m not sure if it has something to do with using XFS filesystems for / and /home. Could use some help :slight_smile:

15

On 2015-07-06 12:46, uhwok3n wrote:

> Code:
> --------------------
>
> systemd-analyze blame
> --------------------

It is best to use the critical chain option.

> However… if you notice udev is taking a very very long time to load.

This is not necessarily important, if it is not in the critical path.
That is, a service may take even minutes to complete, waiting, using low
or no cpu, if it is not impeding other services from starting.

The “systemd-analyze critical-chain” command will tell you best what is
delaying your boot.

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

16

Was just about to post that :wink:

systemd-analyze critical chain:

graphical.target @41.302s
└─multi-user.target @41.302s
  └─cron.service @41.302s
    └─postfix.service @41.125s +175ms
      └─network.target @41.125s
        └─NetworkManager.service @32.658s +94ms
          └─SuSEfirewall2_init.service @32.586s +68ms
            └─basic.target @32.567s
              └─timers.target @32.566s
                └─systemd-tmpfiles-clean.timer @32.566s
                  └─sysinit.target @32.566s
                    └─sys-fs-fuse-connections.mount @33.996s +1ms
                      └─systemd-modules-load.service @118ms +3ms
                        └─systemd-readahead-replay.service @108ms +7ms
                          └─system.slice
                            └─-.slice

Seems sys-fs-fuse-connections.mount is the culprit. Any suggestions on how to speed this process up and/or substitute this with sometime less time consuming?

17

You have any none Linux partition mounting?

Do you have fast boot turned OFF in windows??

18

On 2015-07-06 13:16, uhwok3n wrote:
>
> Was just about to post that :wink:
>
> systemd-analyze critical chain:

Thanks.

> Code:
> --------------------
> graphical.target @41.302s
> └─multi-user.target @41.302s
> └─cron.service @41.302s
> └─postfix.service @41.125s +175ms
> └─network.target @41.125s
> └─NetworkManager.service @32.658s +94ms
> └─SuSEfirewall2_init.service @32.586s +68ms
> └─basic.target @32.567s
> └─timers.target @32.566s
> └─systemd-tmpfiles-clean.timer @32.566s
> └─sysinit.target @32.566s
> └─sys-fs-fuse-connections.mount @33.996s +1ms
> └─systemd-modules-load.service @118ms +3ms
> └─systemd-readahead-replay.service @108ms +7ms
> └─system.slice
> └─-.slice
> --------------------
>
>
> Seems sys-fs-fuse-connections.mount is the culprit.

Nope. It takes one millisecond. :stuck_out_tongue:

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

19

I did have fast boot enabled. I disabled it. Still slow.
However some of these items now show up in red bold text?

systemd-analyze critical-chain:

graphical.target @42.679s
└─multi-user.target @42.679s
  └─cron.service @41.298s
    └─**postfix.service @41.124s +173ms**
      └─network.target @41.123s
        └─**NetworkManager.service @32.729s +58ms**
          └─**SuSEfirewall2_init.service @32.658s +69ms**
            └─basic.target @32.637s
              └─timers.target @32.637s
                └─systemd-tmpfiles-clean.timer @32.637s
                  └─sysinit.target @32.637s
                    └─**sys-fs-fuse-connections.mount @34.039s +1ms**
                      └─**systemd-modules-load.service @119ms +3ms**
                        └─**systemd-readahead-replay.service @107ms +7ms**
                          └─system.slice
                            └─-.slice

systemd-analyze blame:

         32.155s systemd-udev-settle.service
          8.333s NetworkManager-wait-online.service
          1.552s avast.service
           712ms display-manager.service
           236ms apparmor.service
           173ms postfix.service
            91ms SuSEfirewall2.service
            89ms lvm2-activation-early.service
            69ms SuSEfirewall2_init.service
            58ms NetworkManager.service
            49ms ModemManager.service
            25ms udisks2.service
            21ms systemd-udev-trigger.service
            21ms systemd-udev-root-symlink.service
            20ms alsa-restore.service
            20ms nscd.service
            20ms systemd-fsck-root.service
            20ms systemd-user-sessions.service
            20ms home.mount
            19ms polkit.service
            19ms rc-local.service
            18ms plymouth-start.service
            18ms systemd-fsck@dev-disk-by\x2duuid-f59ffcbc\x2d1638\x2d4c83\x2d9593\x2d0ef7e99f8c8b.service
            16ms avahi-daemon.service
            16ms sys-kernel-debug.mount
            15ms wpa_supplicant.service
            14ms plymouth-read-write.service
            14ms dev-hugepages.mount
            14ms dev-mqueue.mount
            13ms rtkit-daemon.service
            13ms ntpd.service
            12ms systemd-tmpfiles-setup-dev.service
            11ms cycle.service
            10ms user@1000.service
             9ms colord.service
             8ms accounts-daemon.service
             7ms systemd-readahead-replay.service
             7ms systemd-logind.service
             7ms systemd-readahead-collect.service
             7ms systemd-vconsole-setup.service
             6ms dev-disk-by\x2duuid-c255c89c\x2d3afd\x2d4eae\x2da9e1\x2d6e80ce4539ad.swap
             6ms lvm2-activation.service
             6ms boot-efi.mount
             5ms kmod-static-nodes.service
             4ms systemd-tmpfiles-setup.service
             4ms upower.service
             3ms systemd-modules-load.service
             3ms systemd-sysctl.service
             3ms systemd-update-utmp.service
             3ms lvm2-lvmetad.service
             3ms systemd-journal-flush.service
             3ms dm-event.service
             3ms iscsi.service
             3ms systemd-backlight@backlight:eeepc-wmi.service
             2ms systemd-remount-fs.service
             2ms auditd.service
             2ms bluetooth.service
             2ms systemd-update-utmp-runlevel.service
             1ms sys-fs-fuse-connections.mount

Hmmmm…

20

On 2015-07-06 14:46, uhwok3n wrote:
>
> I did have fast boot enabled. I disabled it. Still slow.
> However some of these items now show up in red bold text?

Well, they are the slowest things, relatively. But the worst one takes
less than 0.2 seconds…

Please notice that the @number indicates when the job starts. It is the
+number which indicates how long it takes to end. That is the important
figure, and none takes even a second. You can not scrap even a second!

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))