Page 1 of 5 123 ... LastLast
Results 1 to 10 of 44

Thread: After nvidia display driver install -- long boot times (minutes)

  1. #1
    Join Date
    Apr 2011
    Location
    Texas USA
    Posts
    224

    Default After nvidia display driver install -- long boot times (minutes)

    After installing nvidia proprietary drivers, I am now experiencing excessively long boot times. The time to get to grub login screen is normal. The time to complete the screen with the three little squares is also normal.

    After completing the 3 square sequence, the screen goes black (no blinking cursor), and the drive light comes on. Drive light is on for 1min 15 seconds before going out. Black screen persists for another minute, then the normal login screen appears. That makes it about 2 1/2 minutes from time screen with 3 squares is completed to login screen. Toward the end of the black screen period some text flashes by too quickly to read. From login screen, the system boots properly into the various desktops installed.

    Perusal of the log files shows no period where system looks idle, i.e., waiting for something. It is continually reporting activity.

    This boot period is completely different then when using the prior nouveau drivers.

    Computer is moderately fast so hardware should not be the issue. Asus x99 mb, i7 upper speed cpu chip, 32 gig memory, lots of free disk space in root partition.

    Anyone have a solution or diagnostic ideas? This is just an inconvenience but it is radical change from before nvidia drivers and I would like to resolve it

    thanks, tom kosvic

  2. #2
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    16,173

    Default Re: After nvidia display driver install -- long boot times (minutes)

    Show

    systemd-analyze blame

    this shows times for each unit to start

  3. #3
    Join Date
    Apr 2011
    Location
    Texas USA
    Posts
    224

    Default Re: After nvidia display driver install -- long boot times (minutes)

    Results of systemd analyze blame. Hope this is not too long. Looks like 1 minute @ plymouth service. This does not fully explain the 2 1/2 minutes overall.


    Code:
    localhost:/home/tom # systemd-analyze blame
        1min 34.399s plymouth-quit-wait.service
             30.096s wicked.service
              5.546s systemd-udev-settle.service
              4.318s libvirtd.service
              3.910s lvm2-monitor.service
              3.223s initrd-switch-root.service
              2.577s rsyslog.service
              2.011s mcelog.service
              1.977s udisks2.service
              1.910s nscd.service
              1.904s systemd-machined.service
              1.902s kbdsettings.service
              1.900s alsa-restore.service
              1.865s bluetooth.service
              1.863s avahi-daemon.service
              1.780s smartd.service
              1.304s apparmor.service
              1.163s postfix.service
              1.065s firewalld.service
               979ms display-manager.service
               768ms systemd-udevd.service
               748ms systemd-fsck@dev-disk-by\x2duuid-e748b401\x2d3a8f\x2d4152\x2da9ea\x2def540efb0230.service
               675ms polkit.service
               603ms dracut-initqueue.service
               438ms upower.service
               429ms plymouth-start.service
               398ms systemd-tmpfiles-setup-dev.service
               379ms boot-efi.mount
               333ms klog.service
               314ms systemd-fsck@dev-disk-by\x2duuid-C93A\x2dC87E.service
               306ms ModemManager.service
               285ms accounts-daemon.service
               260ms systemd-tmpfiles-setup.service
               246ms systemd-sysctl.service
               238ms auditd.service
               229ms wickedd-dhcp6.service
               228ms wickedd-auto4.service
               228ms wickedd-dhcp4.service
               224ms user@461.service
               192ms systemd-journald.service
               185ms user@1000.service
               180ms systemd-udev-trigger.service
               177ms plymouth-switch-root.service
               173ms colord.service
               147ms dev-disk-by\x2duuid-732223f6\x2db4fa\x2d4fa0\x2d9d5a\x2d78ced9984c72.swap
               122ms systemd-rfkill.service
               115ms initrd-parse-etc.service
               101ms chronyd.service
                95ms systemd-modules-load.service
                91ms dev-hugepages.mount
                79ms systemd-tmpfiles-clean.service
                79ms systemd-remount-fs.service
                79ms sys-kernel-debug.mount
                77ms wickedd-nanny.service
                76ms systemd-logind.service
                73ms systemd-fsck-root.service
                70ms systemd-journal-flush.service
                64ms wpa_supplicant.service
                45ms systemd-vconsole-setup.service
                41ms home.mount
                37ms dracut-cmdline.service
                34ms rtkit-daemon.service
                34ms dev-mqueue.mount
                32ms iscsi.service
                31ms wickedd.service
                31ms systemd-random-seed.service
                26ms systemd-update-utmp.service
                22ms kmod-static-nodes.service
                17ms dracut-pre-udev.service
                13ms dracut-shutdown.service
                13ms user-runtime-dir@461.service
                13ms sysroot.mount
                11ms plymouth-read-write.service
                10ms systemd-user-sessions.service
                 7ms user-runtime-dir@1000.service
                 6ms initrd-cleanup.service
                 5ms systemd-update-utmp-runlevel.service
                 4ms initrd-udevadm-cleanup-db.service
                 2ms sys-fs-fuse-connections.mount

  4. #4
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    16,173

    Default Re: After nvidia display driver install -- long boot times (minutes)

    systemd-analyze critical-chain

    Read more at: https://www.commandlinux.com/man-pag...analyze.1.html

    systemd-analyze critical-chain

    may give more insight

    Are you timing boot or to working desktop??

    30 seconds for wicked is pretty high.
    systemd-analyze critical-chain

    Read more at: https://www.commandlinux.com/man-pag...analyze.1.html

    systemd-analyze critical-chain

    Read more at: https://www.commandlinux.com/man-pag...analyze.1.html
    systemd-analyze critical-chain

    Read more at: https://www.commandlinux.com/man-pag...analyze.1.html


    systemd-analyze critical-chain

    Read more at: https://www.commandlinux.com/man-pag...analyze.1.html

  5. #5
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    16,173

    Default Re: After nvidia display driver install -- long boot times (minutes)

    systemd-analyze critical-chain

    Read more at: https://www.commandlinux.com/man-pag...analyze.1.html

    may give more insight

    Are you timing boot or to working desktop??

    30 seconds for wicked is pretty high.


    439ms plymouth-quit-wait.service here

    At boot try e then line starting linuxefi add quiet to stop plymouth.

  6. #6
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    31,298
    Blog Entries
    15

    Default Re: After nvidia display driver install -- long boot times (minutes)

    Quote Originally Posted by gogalthorp View Post
    systemd-analyze critical-chain

    Read more at: https://www.commandlinux.com/man-pag...analyze.1.html

    may give more insight

    Are you timing boot or to working desktop??

    30 seconds for wicked is pretty high.


    439ms plymouth-quit-wait.service here

    At boot try e then line starting linuxefi add quiet to stop plymouth.
    Hi
    It's actually plymouth.enable=0
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  7. #7
    Join Date
    Apr 2011
    Location
    Texas USA
    Posts
    224

    Default Re: After nvidia display driver install -- long boot times (minutes)

    I added plymouth.enable=0 at end of linux commandline in grub boot and then initiated boot with f10.

    I got pages of text messages about what it was doing.

    It stopped for about a minute on:

    "Started Update UTMP about System Runlevel Changes" . Also disk activity light was on during this time.

    Over all boot was somewhat faster but I dont have a timing.

    I have no knowledge about UTMP.

    Any guidance would be appreciated.

    tom kosvic

  8. #8
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    5,906

    Default AW: After nvidia display driver install -- long boot times (minutes)

    Please post:
    Code:
    zypper se -si kernel nvidia
    Code:
    uname -a

  9. #9
    Join Date
    Apr 2011
    Location
    Texas USA
    Posts
    224

    Default Re: After nvidia display driver install -- long boot times (minutes)

    Code:
    localhost:/home/tom # zypper se -si kernel nvidia
    Loading repository data...
    Reading installed packages...
    
    S  | Name                      | Type    | Version                               | Arch   | Repository
    ---+---------------------------+---------+---------------------------------------+--------+------------------------
    i  | jupyter-ipykernel         | package | 5.2.1-lp152.1.2                       | noarch | Main Repository
    i+ | kernel-default            | package | 5.3.18-lp152.75.1                     | x86_64 | Main Update Repository
    i+ | kernel-default            | package | 5.3.18-lp152.72.1                     | x86_64 | Main Update Repository
    i  | kernel-default-devel      | package | 5.3.18-lp152.75.1                     | x86_64 | Main Update Repository
    i  | kernel-devel              | package | 5.3.18-lp152.75.1                     | noarch | Main Update Repository
    i  | kernel-firmware           | package | 20200107-lp152.2.6.1                  | noarch | Main Update Repository
    i  | kernel-macros             | package | 5.3.18-lp152.75.1                     | noarch | Main Update Repository
    i  | kernel-preempt-devel      | package | 5.3.18-lp152.75.1                     | x86_64 | Main Update Repository
    i  | nfs-kernel-server         | package | 2.1.1-lp152.9.6.1                     | x86_64 | Main Update Repository
    i  | nvidia-computeG05         | package | 460.73.01-lp152.39.1                  | x86_64 | nVidia Graphics Drivers
    i+ | nvidia-gfxG05-kmp-default | package | 460.73.01_k5.3.18_lp152.19-lp152.39.1 | x86_64 | nVidia Graphics Drivers
    i+ | nvidia-glG05              | package | 460.73.01-lp152.39.1                  | x86_64 | nVidia Graphics Drivers
    i  | purge-kernels-service     | package | 0-lp152.4.1                           | noarch | Main Repository
    i  | python3-ipykernel         | package | 5.2.1-lp152.1.2                       | noarch | Main Repository
    i  | x11-video-nvidiaG05       | package | 460.73.01-lp152.39.1                  | x86_64 | nVidia Graphics Drivers
    localhost:/home/tom #
    Code:
    localhost:/home/tom # uname -a
    Linux localhost 5.3.18-lp152.75-default #1 SMP Wed May 5 09:22:56 UTC 2021 (16c42c8) x86_64 x86_64 x86_64 GNU/Linux
    localhost:/home/tom #

  10. #10
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    16,173

    Default Re: After nvidia display driver install -- long boot times (minutes)

    You have a kernel-preempt-devel Package so at some point you must have been hit by the preempt bug.
    This may cause problems with the nvidia-kmp since it does a recompile on first run of new kernel or nvidia packages.
    in any case it is not needed remove it
    see if that helps let us know.

Page 1 of 5 123 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •