Linux Lite Forums

Full Version: kernel boot parameter
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I recently upgraded to a HP laptop and my profile has changed. I'm a novice when it comes to Linux Lite but I'm trying to learn new stuff.  I'm confused about "add the kernel boot parameter" as shown below.  How do I add it? I'm able to get into the terminal and enter the first sudo line but after that I'm lost. Any help is appreciated. I have a slow boot time of six minutes which I'm trying to change with the following:
  • sudo nano /etc/default/grub
Then add the kernel boot parameter: video=SVIDEO-1:d, so it will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video=SVIDEO-1:d"
  • sudo update-grub
  • sudo reboot
You are copying someone else's solution from another thread, ignore it. You need to start from the beginning. Open a Terminal, run the following command and paste the results here:

Code:
systemd-analyze blame




systemd-analyze blame

Here's is the result of the above.


1min 21.908s nmbd.service
        46.656s vboxadd.service
        42.123s plymouth-quit-wait.service
        28.556s systemd-journal-flush.service
        28.375s dev-sda1.device
        25.944s ufw.service
        22.637s systemd-tmpfiles-setup-dev.service
        22.525s lvm2-monitor.service
        22.269s keyboard-setup.service
        21.161s systemd-sysctl.service
          9.495s NetworkManager-wait-online.service
          6.860s snapd.service
          4.753s NetworkManager.service
          4.346s preload.service
          4.071s apparmor.service
          3.940s networkd-dispatcher.service
          3.772s ModemManager.service
          3.326s thermald.service
          3.224s udisks2.service
          3.110s grub-common.service
          2.383s wpa_supplicant.service
          2.241s dev-loop3.device
          2.172s bluetooth.service
          2.049s rsyslog.service
          2.031s accounts-daemon.service
          1.755s dev-loop5.device
          1.664s dev-loop7.device
          1.652s dev-loop6.device
          1.608s dev-loop2.device
          1.601s dev-loop1.device
          1.580s dev-loop0.device
          1.549s dev-loop4.device
          1.229s console-kit-log-system-start.service
          1.216s avahi-daemon.service
          1.186s lm-sensors.service
          1.167s phpsessionclean.service
          1.162s alsa-restore.service
          1.107s gpu-manager.service
          1.042s binfmt-support.service
          1.017s smbd.service
          1.009s systemd-rfkill.service
          998ms networking.service
          984ms polkit.service
          811ms systemd-modules-load.service
          693ms console-setup.service
          680ms apport.service
          670ms systemd-logind.service
          643ms snap-gimp-189.mount
          621ms systemd-udevd.service
          586ms ubiquity.service
          585ms dns-clean.service
          547ms snap-snapd-3646.mount
          538ms pppd-dns.service
          491ms systemd-remount-fs.service
          467ms dev-hugepages.mount
          465ms sys-kernel-debug.mount
          461ms dev-mqueue.mount
          409ms snap-core18-1013.mount
          401ms systemd-udev-trigger.service
          378ms snap-kde\x2dframeworks\x2d5\x2dcore18-29.mount
          372ms systemd-journald.service
          354ms systemd-backlight@backlight:amdgpu_bl0.service
          353ms snap-core18-1049.mount
          322ms snap-gtk\x2dcommon\x2dthemes-1198.mount
          322ms lightdm.service
          297ms upower.service
          267ms packagekit.service
          241ms resolvconf.service
          226ms swapfile.swap
          222ms systemd-user-sessions.service
          181ms snap-kmag-18.mount
          177ms systemd-timesyncd.service
          153ms systemd-resolved.service
          152ms snap-core-7270.mount
          147ms blk-availability.service
          138ms systemd-update-utmp.service
          129ms console-kit-daemon.service
          117ms kmod-static-nodes.service
          106ms systemd-random-seed.service
          103ms [email protected]
            90ms systemd-tmpfiles-setup.service
            88ms setvtrgb.service
            74ms snapd.seeded.service
            38ms hddtemp.service
            17ms plymouth-start.service
            16ms resolvconf-pull-resolved.service
            12ms proc-sys-fs-binfmt_misc.mount
            11ms ureadahead-stop.service
            10ms plymouth-read-write.service
            10ms systemd-update-utmp-runlevel.service
            9ms rtkit-daemon.service
            5ms sys-fs-fuse-connections.mount
            4ms sys-kernel-config.mount
            3ms openvpn.service
            1ms snapd.socket

Now:

Code:
systemd-analyze critical-chain

and:

Code:
systemd-analyze

then attach /var/log/boot.log to your post.
I entered what you mentioned in the terminal and I got this:
/var/log/boot.log
bash: /var/log/boot.log: Permission denied
(07-09-2019, 12:41 AM)diskrod link Wrote: [ -> ]I entered what you mentioned in the terminal and I got this:
/var/log/boot.log
bash: /var/log/boot.log: Permission denied

Read very carefully the instructions, I asked to attach it to your post, not paste it.