Author Topic: Peppermint 10 Respin Boot Time..  (Read 1392 times)

Offline rayzer

  • Trusted User
  • Member
  • *****
  • Posts: 389
  • Karma: 154
  • Graphics n Stuff
    • View Profile
  • Peppermint version(s): 10 Respin
Peppermint 10 Respin Boot Time..
« on: April 19, 2020, 03:00:54 am »
When i ran the original peppermint 10 on my laptop it booted up in roughly 6 second, so did mint mate and windows10..
However since i installed the Respin edition its taking much longer to boot (10-15 seconds longer), im wondering is there a way to disable the blank peppermint splash screen that shows because that appears to be the culprit.
Ive tried installing the plymouth disabler and also removing the peppermint plymouth theme but it still shows up after a reboot. any ideas on what i can do?
Ive also looked into the quiet splash options but havent done anything yet as i dont want to break this setup since i have nothing on it backed up yet, just want some ideas before i go hacking at things. These things always tend to end badly for me :D

edit: ran systemd-analyze blame and this is what my current boot times are

Code: [Select]
rayzer@rayzer-XPS-13-9343 ~ $ systemd-analyze blame
         10.105s nmbd.service
          2.278s dev-sda1.device
          1.460s snapd.service
           857ms dev-loop3.device
           803ms dev-loop6.device
           782ms systemd-backlight@backlight:intel_backlight.service
           764ms dev-loop4.device
           609ms dev-loop1.device
           606ms dev-loop2.device
           575ms dev-loop0.device
           547ms dev-loop5.device
           537ms mintsystem.service
           499ms networkd-dispatcher.service
           466ms NetworkManager-wait-online.service
           458ms udisks2.service
           387ms ModemManager.service
           377ms NetworkManager.service
           335ms systemd-journal-flush.service
           323ms accounts-daemon.service
           301ms ufw.service
           280ms systemd-rfkill.service
           228ms apparmor.service
           192ms rpcbind.service
           186ms systemd-resolved.service
           156ms pppd-dns.service
...skipping...
          1.460s snapd.service
           857ms dev-loop3.device
           803ms dev-loop6.device
           782ms systemd-backlight@backlight:intel_backlight.service
           764ms dev-loop4.device
           609ms dev-loop1.device
           606ms dev-loop2.device
           575ms dev-loop0.device
           547ms dev-loop5.device
           537ms mintsystem.service
           499ms networkd-dispatcher.service
           466ms NetworkManager-wait-online.service
           458ms udisks2.service
           387ms ModemManager.service
           377ms NetworkManager.service
           335ms systemd-journal-flush.service
           323ms accounts-daemon.service
           301ms ufw.service
           280ms systemd-rfkill.service
           228ms apparmor.service
           192ms rpcbind.service
           186ms systemd-resolved.service
           156ms pppd-dns.service
           152ms grub-common.service
           152ms avahi-daemon.service
           151ms keyboard-setup.service
           147ms systemd-backlight@leds:dell::kbd_backlight.service
           133ms upower.service
           133ms swapfile.swap
           130ms thermald.service
           128ms snap-core18-1705.mount
           128ms gpu-manager.service
           121ms systemd-udev-trigger.service
           119ms snapd.seeded.service
           106ms polkit.service
           101ms snap-gnome\x2d3\x2d26\x2d1604-98.mount
           101ms systemd-journald.service
           100ms systemd-logind.service
            99ms wpa_supplicant.service
            92ms systemd-udevd.service
            90ms snap-gtk\x2dcommon\x2dthemes-1502.mount
            86ms snap-core-8935.mount
            83ms rsyslog.service
            82ms lightdm.service
            82ms snap-core-8689.mount
            79ms plymouth-quit-wait.service
            70ms user@1000.service
            66ms systemd-modules-load.service
            60ms smbd.service
            57ms snap-core18-1668.mount
            54ms snap-gtk\x2dcommon\x2dthemes-1474.mount
            53ms plymouth-start.service
            52ms lm-sensors.service
            52ms run-rpc_pipefs.mount
            47ms ntp.service
            38ms systemd-tmpfiles-setup-dev.service
            36ms linuxlogo.service
            32ms systemd-sysctl.service
            31ms hddtemp.service
            28ms systemd-tmpfiles-setup.service
            27ms plymouth-read-write.service
            21ms nfs-config.service
            20ms console-setup.service
            19ms kerneloops.service
            17ms systemd-update-utmp.service
            15ms systemd-tmpfiles-clean.service
            14ms systemd-remount-fs.service
            13ms ureadahead-stop.service
            13ms sys-kernel-debug.mount
            13ms systemd-user-sessions.service
            11ms dev-mqueue.mount
            11ms systemd-random-seed.service
            11ms openvpn.service
             9ms dev-hugepages.mount
             9ms bluetooth.service
             7ms sys-kernel-config.mount
             7ms kmod-static-nodes.service
             7ms systemd-update-utmp-runlevel.service
             3ms sys-fs-fuse-connections.mount
             2ms setvtrgb.service
           889us snapd.socket
lines 61-83/83 (END)
« Last Edit: April 19, 2020, 03:19:29 am by rayzer »
For wallpapers ive made you can download them here

Offline rayzer

  • Trusted User
  • Member
  • *****
  • Posts: 389
  • Karma: 154
  • Graphics n Stuff
    • View Profile
  • Peppermint version(s): 10 Respin
Re: Peppermint 10 Respin Boot Time..
« Reply #1 on: April 19, 2020, 04:04:50 am »
having looked around i think i might know where the problem lies but im just wondering whether to remove theses lines in /boot/grub/grub.cfg (lines 108-114)

Code: [Select]
insmod png
if background_image /boot/grub/grub-background.png; then
  true
else
  set menu_color_normal=light-gray/black
  set menu_color_highlight=white/red
fi

let me know what you think
For wallpapers ive made you can download them here

Offline The Omen

  • Member
  • ***
  • Posts: 131
  • Karma: 31
  • New Forum User
    • View Profile
  • Peppermint version(s): Peppermint 9 respin
Re: Peppermint 10 Respin Boot Time..
« Reply #2 on: April 20, 2020, 08:16:17 am »
Hi rayzer,

I notice that samba, snapd, as well as a few other loadups on start are in play here that can sap your boot-up time.

If you do not use either samba or snaps, they can be completely removed as i have done here.

If you do not use these, i will post the terminal commands here for you if you wish along with a few other things you do not need on boot-up.

My cold boot time with SSD is at 5 secs.

Regards,

The Omen

Offline spence

  • Administrator
  • Hero
  • *****
  • Posts: 2954
  • Karma: 335
  • peppermint user since 2010
    • View Profile
  • Peppermint version(s): PMVII, PMVIII, PMIX, PMX Respins
Re: Peppermint 10 Respin Boot Time..
« Reply #3 on: April 20, 2020, 05:52:09 pm »
I am looking forward to the answer/resolution to this... my main install feels like it takes forever to load, despite purging apparmor, bluez, btrfs-tools, cups, flatpak, guvcview, libflatpak0, nemo-dropbox, rsync, samba, snapd & transmission-gtk

 >:(

Spoiler (click here to view / hide)
[close]
« Last Edit: April 20, 2020, 05:56:03 pm by spence »
spence
PeppermintOS 8,9 & 10 Respins currently installed  on:
'16 Antec Aria rebuild
PMX Respin on '18 Asus VivoBook


Do not despair, grasshopper...
    with patience all will be revealed...
       Through pain, enlightenment will come.

Offline The Omen

  • Member
  • ***
  • Posts: 131
  • Karma: 31
  • New Forum User
    • View Profile
  • Peppermint version(s): Peppermint 9 respin
Re: Peppermint 10 Respin Boot Time..
« Reply #4 on: April 21, 2020, 10:59:12 am »
Things I do to minimize boot time:

List of Items to Stop, Disable, Mask, etc. from Start-Up: just copy and paste commands one at a time into your terminal and follow the prompts that are given:

 
Code: [Select]
sudo systemctl disable ModemManager.service
 
Code: [Select]
sudo systemctl disable NetworkManager-wait-online.service
 
Code: [Select]
sudo systemctl disable pppd-dns.service
 
Code: [Select]
sudo systemctl stop avahi-daemon.service
 
Code: [Select]
sudo systemctl disable avahi-daemon.service
 
Code: [Select]
sudo systemctl mask avahi-daemon.service
 
Code: [Select]
sudo systemctl mask plymouth-quit-wait.service
 
Code: [Select]
sudo systemctl mask postfix.service


Purge Snapd

 
Code: [Select]
sudo apt purge snapd

Purge Gnome-Software Repository (SNAP)

 
Code: [Select]
sudo apt-get remove --purge gnome-software gnome-software-plugin-snap

Remove Flatpak remotes

To show remote sources:

 
Code: [Select]
flatpak remotes

Delete the sources as in this example:

 
Code: [Select]
flatpak remote-delete flathub
 
Purge Samba

 
Code: [Select]
sudo apt purge samba

Purge telnet

 
Code: [Select]
sudo apt purge telnet

Purge btrfs

 
Code: [Select]
sudo apt-get purge btrfs-progs && sudo update-initramfs -uk all

Change Grub Timeout

 
Code: [Select]
sudo nano /etc/default/grub
Edit the line listed (GRUB_TIMEOUT=10) to read ("arrow" down and then "arrow" over to the number 10) and change it to 0...(GRUB_TIMEOUT=0)(this is a zero)

GRUB_TIMEOUT_STYLE=hidden

Press Ctrl-O (note that this is an O and not a zero)...then press "enter"...then press "save" from the "tab" in that same box...then Ctrl-X to exit the editor...then run in the terminal,

 
Code: [Select]
sudo update-grub

Apt-Daily Timer Service: You will still get your updates as usual, just wont waste time during boot up:

 
Code: [Select]
sudo systemctl disable apt-daily.service
 
Code: [Select]
sudo systemctl disable apt-daily.timer
 
Code: [Select]
sudo systemctl disable apt-daily-upgrade.timer
 
Code: [Select]
sudo systemctl disable apt-daily-upgrade.service

Then reboot your system.

Warm regards,

The Omen
« Last Edit: May 14, 2020, 04:45:31 pm by The Omen »

Offline The Omen

  • Member
  • ***
  • Posts: 131
  • Karma: 31
  • New Forum User
    • View Profile
  • Peppermint version(s): Peppermint 9 respin
Re: Peppermint 10 Respin Boot Time..
« Reply #5 on: April 21, 2020, 11:32:00 am »
Hi Rayzer and Spence,

Below are my results if you care to see my proof of concept results from my previous post just before this one:

Regards,

The Omen


Quote
$ systemd-analyze
Startup finished in 1.818s (kernel) + 2.786s (userspace) = 4.605s
graphical.target reached after 2.780s in userspace

Quote
$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @2.780s
└─lightdm.service @2.675s +104ms
  └─systemd-user-sessions.service @2.665s +5ms
    └─network.target @2.664s
      └─NetworkManager.service @2.398s +266ms
        └─dbus.service @2.383s
          └─basic.target @2.382s
            └─sockets.target @2.382s
              └─acpid.socket @2.382s
                └─sysinit.target @2.359s
                  └─apparmor.service @368ms +1.990s
                    └─local-fs.target @367ms
                      └─local-fs-pre.target @367ms
                        └─systemd-tmpfiles-setup-dev.service @213ms +153ms
                          └─kmod-static-nodes.service @201ms +9ms
                            └─systemd-journald.socket @199ms
                              └─system.slice @199ms
                                └─-.slice @185ms
Quote
$ systemd-analyze blame
          1.990s apparmor.service
          1.318s dev-sda1.device
          1.290s ufw.service
           900ms systemd-journal-flush.service
           305ms systemd-tmpfiles-setup.service
           266ms NetworkManager.service
           240ms systemd-logind.service
           231ms mintsystem.service
           202ms udisks2.service
           178ms systemd-udevd.service
           153ms systemd-tmpfiles-setup-dev.service
           149ms networkd-dispatcher.service
           127ms systemd-resolved.service
           122ms keyboard-setup.service
           122ms plymouth-read-write.service
           114ms nfs-config.service
           111ms run-rpc_pipefs.mount
           111ms console-setup.service
           104ms lightdm.service
            95ms systemd-modules-load.service
            92ms systemd-journald.service
            88ms rpcbind.service
            80ms upower.service
            66ms swapfile.swap
            57ms gpu-manager.service
            56ms accounts-daemon.service
            48ms systemd-udev-trigger.service
            40ms grub-common.service
            37ms systemd-remount-fs.service
            28ms user@1000.service
            25ms alsa-restore.service
            24ms packagekit.service
            22ms lm-sensors.service
            20ms plymouth-start.service
            20ms wpa_supplicant.service
            18ms systemd-sysctl.service
            17ms polkit.service
            17ms systemd-random-seed.service
            13ms hddtemp.service
            12ms ntp.service
            12ms rsyslog.service
            10ms ureadahead-stop.service
             9ms systemd-update-utmp.service
             9ms systemd-tmpfiles-clean.service
             9ms kmod-static-nodes.service
             9ms kerneloops.service
             9ms sys-kernel-debug.mount
             8ms dev-mqueue.mount
             5ms systemd-user-sessions.service
             4ms dev-hugepages.mount
             3ms systemd-update-utmp-runlevel.service
             3ms sys-kernel-config.mount
             2ms sys-fs-fuse-connections.mount
             2ms setvtrgb.service
lines 30-54/54 (END)
« Last Edit: April 21, 2020, 12:28:53 pm by The Omen »

Offline spence

  • Administrator
  • Hero
  • *****
  • Posts: 2954
  • Karma: 335
  • peppermint user since 2010
    • View Profile
  • Peppermint version(s): PMVII, PMVIII, PMIX, PMX Respins
Re: Peppermint 10 Respin Boot Time..
« Reply #6 on: May 12, 2020, 12:11:29 pm »
Messing about with my desktop while everyone else is at work... While it feels faster, I'm not yet approaching the onboarding as quickly as you and @VinDSL are attaining @TheOmen:

Code: [Select]
spence@antec ~ $ systemd-analyze
Startup finished in 12.798s (firmware) + 2.673s (loader) + 1.899s (kernel) + 594ms (userspace) = 17.965s
graphical.target reached after 590ms in userspace


spence@antec ~ $ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @590ms
└─multi-user.target @590ms
  └─mintsystem.service @406ms +183ms
    └─remote-fs.target @405ms
      └─remote-fs-pre.target @405ms
        └─rpcbind.service @353ms +47ms
          └─systemd-tmpfiles-setup.service @337ms +13ms
            └─local-fs.target @337ms
              └─boot-efi.mount @317ms +19ms
                └─systemd-fsck@dev-disk-by\x2duuid-9ACE\x2d414B.service @291ms +25ms
                  └─dev-disk-by\x2duuid-9ACE\x2d414B.device @277ms

and then:
spence@antec ~ $  systemd-analyze blame

         
Spoiler (click here to view / hide)
[close]
spence
PeppermintOS 8,9 & 10 Respins currently installed  on:
'16 Antec Aria rebuild
PMX Respin on '18 Asus VivoBook


Do not despair, grasshopper...
    with patience all will be revealed...
       Through pain, enlightenment will come.

Offline spence

  • Administrator
  • Hero
  • *****
  • Posts: 2954
  • Karma: 335
  • peppermint user since 2010
    • View Profile
  • Peppermint version(s): PMVII, PMVIII, PMIX, PMX Respins
Re: Peppermint 10 Respin Boot Time..
« Reply #7 on: May 12, 2020, 12:18:26 pm »
 >:(

And then mysteriously, I get this kind of readout on 2nd reboot:
Code: [Select]
spence@antec ~ $ systemd-analyze
Startup finished in 11min 50.452s (firmware) + 2.123s (loader) + 1.868s (kernel) + 1.032s (userspace) = 11min 55.476s
graphical.target reached after 1.028s in userspace

or, is that because I rebooted... instead of a shut down then restart? In some ways, I feel very much like a n00b...

 ::)

Code: [Select]
spence@antec ~ $ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @1.028s
└─lightdm.service @667ms +359ms
  └─systemd-user-sessions.service @566ms +5ms
    └─network.target @563ms
      └─NetworkManager.service @484ms +78ms
        └─dbus.service @421ms
          └─basic.target @416ms
            └─sockets.target @416ms
              └─acpid.socket @416ms
                └─sysinit.target @414ms
                  └─systemd-timesyncd.service @384ms +30ms
                    └─systemd-tmpfiles-setup.service @364ms +17ms
                      └─local-fs.target @364ms
                        └─boot-efi.mount @323ms +40ms
                          └─systemd-fsck@dev-disk-by\x2duuid-9ACE\x2d414B.service @287
                            └─dev-disk-by\x2duuid-9ACE\x2d414B.device @282ms
lines 1-19/19 (END)...skipping...
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @1.028s
└─lightdm.service @667ms +359ms
  └─systemd-user-sessions.service @566ms +5ms
    └─network.target @563ms
      └─NetworkManager.service @484ms +78ms
        └─dbus.service @421ms
          └─basic.target @416ms
            └─sockets.target @416ms
              └─acpid.socket @416ms
                └─sysinit.target @414ms
                  └─systemd-timesyncd.service @384ms +30ms
                    └─systemd-tmpfiles-setup.service @364ms +17ms
                      └─local-fs.target @364ms
                        └─boot-efi.mount @323ms +40ms
                          └─systemd-fsck@dev-disk-by\x2duuid-9ACE\x2d414B.service @287ms +30ms
                            └─dev-disk-by\x2duuid-9ACE\x2d414B.device @282ms

spence
PeppermintOS 8,9 & 10 Respins currently installed  on:
'16 Antec Aria rebuild
PMX Respin on '18 Asus VivoBook


Do not despair, grasshopper...
    with patience all will be revealed...
       Through pain, enlightenment will come.

Online VinDSL

  • Administrator
  • Hero
  • *****
  • Posts: 5846
  • Karma: 1132
  • Team Peppermint
    • View Profile
  • Peppermint version(s): Developmental Builds
Re: Peppermint 10 Respin Boot Time..
« Reply #8 on: May 12, 2020, 07:26:12 pm »
Ive tried installing the plymouth disabler and also removing the peppermint plymouth theme but it still shows up after a reboot. any ideas on what i can do?

Plymouth seems to be intertwined with all sorts of things, in the operating system. It causes no end of grief, and its a PITA to remove, without breaking something. Plus, successfully removing Plymouth is a moving target and changes, from release-to-release.

What I do is simply mask the 'plymouth-quit-wait.service' at boot. IMO, Plymouth itself doesn't cause the problem - it's the 'plymouth-quit-wait.service' hanging for seconds, minutes, or hours (before timing out) that causes the lag. Sometimes it hangs for so long, the machine can't even be shutdown normally, e.g shutdown hangs too.

Here's a screenie of my PM10R test machine - a Dell PCI-only i686 (32bit) machine that's so old and under-powered nobody would take it, if I gave it away. It repeatedly boots in 11-12 seconds, in large part because I mask the 'plymouth-quit-wait.service' at boot. When I unmask Plymouth, it's lucky if it boots in 25-30 seconds.

You can see the command at the bottom of my "Neofetch" window (click to enlarge)

EDIT

I don't mask Plymouth, on the machine I'm currently on. I leave it up for months at a time, so what difference does it make, you know? Anyway, I just ran the command in CLI, Here ya go:

Code: [Select]
╭─vindsl@Boogaloo-6 ~
╰─$ sudo systemctl mask plymouth-quit-wait.service
[sudo] password for vindsl:
Created symlink /etc/systemd/system/plymouth-quit-wait.service → /dev/null.
╭─vindsl@Boogaloo-6 ~
╰─$


« Last Edit: May 12, 2020, 07:50:26 pm by VinDSL »

Offline spence

  • Administrator
  • Hero
  • *****
  • Posts: 2954
  • Karma: 335
  • peppermint user since 2010
    • View Profile
  • Peppermint version(s): PMVII, PMVIII, PMIX, PMX Respins
Re: Peppermint 10 Respin Boot Time..
« Reply #9 on: May 12, 2020, 10:15:51 pm »
This is the before on my little mini ASUS, surprises me that it's faster than my blown out desktop, though the desktop is quintuple booting (cue a view of VinDSL's 20 partition boot), while mini ASUS is single boot

Code: [Select]
spence@Asus-VivoBook-12 ~ $ systemd-analyze
Startup finished in 2.936s (kernel) + 7.578s (userspace) = 10.515s
graphical.target reached after 7.567s in userspace,

spence@Asus-VivoBook-12 ~ $ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @7.567s
└─multi-user.target @7.567s
  └─kerneloops.service @7.541s +26ms
    └─network-online.target @7.533s
      └─NetworkManager-wait-online.service @2.785s +4.747s
        └─NetworkManager.service @2.453s +329ms
          └─dbus.service @2.395s
            └─basic.target @2.232s
              └─sockets.target @2.232s
                └─uuidd.socket @2.232s
                  └─sysinit.target @2.220s
                    └─systemd-backlight@backlight:intel_backlight.service @2.679s +38m
                      └─system-systemd\x2dbacklight.slice @2.674s
                        └─system.slice @514ms
                          └─-.slice @511ms

spence@Asus-VivoBook-12 ~ $ systemd-analyze blame
Spoiler (click here to view / hide)
[close]

 ::)

and then again after The Omen's list:

Code: [Select]
spence@Asus-VivoBook-12 ~ $ systemd-analyze
Startup finished in 2.479s (kernel) + 3.814s (userspace) = 6.293s
graphical.target reached after 3.798s in userspace

spence@Asus-VivoBook-12 ~ $ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @3.798s
└─multi-user.target @3.798s
  └─mintsystem.service @2.269s +1.528s
    └─basic.target @2.225s
      └─paths.target @2.225s
        └─cups.path @2.224s
          └─sysinit.target @2.217s
            └─systemd-backlight@backlight:intel_backlight.service @2.704s +94ms
              └─system-systemd\x2dbacklight.slice @2.693s
                └─system.slice @542ms
                  └─-.slice @512ms


spence@Asus-VivoBook-12 ~ $ systemd-analyze blame
Spoiler (click here to view / hide)
[close]

 8)
« Last Edit: May 12, 2020, 10:44:38 pm by spence »
spence
PeppermintOS 8,9 & 10 Respins currently installed  on:
'16 Antec Aria rebuild
PMX Respin on '18 Asus VivoBook


Do not despair, grasshopper...
    with patience all will be revealed...
       Through pain, enlightenment will come.

Online VinDSL

  • Administrator
  • Hero
  • *****
  • Posts: 5846
  • Karma: 1132
  • Team Peppermint
    • View Profile
  • Peppermint version(s): Developmental Builds
Re: Peppermint 10 Respin Boot Time..
« Reply #10 on: May 12, 2020, 10:36:35 pm »
Looking at your critical-chain' stats, you can probably lower your boot time by 4 seconds, by dumping NM and switching to WiCD...   ;)







Offline spence

  • Administrator
  • Hero
  • *****
  • Posts: 2954
  • Karma: 335
  • peppermint user since 2010
    • View Profile
  • Peppermint version(s): PMVII, PMVIII, PMIX, PMX Respins
Re: Peppermint 10 Respin Boot Time..
« Reply #11 on: May 12, 2020, 10:48:21 pm »
Looking at your critical-chain' stats, you can probably lower your boot time by 4 seconds, by dumping NM and switching to WiCD...   ;)

last time I tried WiCD, I ended up needing a complete reinstall... guess I need a better guide... or needed a cooler head...

 >:(
spence
PeppermintOS 8,9 & 10 Respins currently installed  on:
'16 Antec Aria rebuild
PMX Respin on '18 Asus VivoBook


Do not despair, grasshopper...
    with patience all will be revealed...
       Through pain, enlightenment will come.

Online VinDSL

  • Administrator
  • Hero
  • *****
  • Posts: 5846
  • Karma: 1132
  • Team Peppermint
    • View Profile
  • Peppermint version(s): Developmental Builds
Re: Peppermint 10 Respin Boot Time..
« Reply #12 on: May 12, 2020, 11:08:53 pm »
last time I tried WiCD, I ended up needing a complete reinstall... guess I need a better guide... or needed a cooler head...

 >:(

Not suggesting, just saying   :)

I've got a long history with WiCD: https://is.gd/cGJ7T1

Offline rayzer

  • Trusted User
  • Member
  • *****
  • Posts: 389
  • Karma: 154
  • Graphics n Stuff
    • View Profile
  • Peppermint version(s): 10 Respin
Re: Peppermint 10 Respin Boot Time..
« Reply #13 on: May 13, 2020, 02:40:30 am »
since i posted this ive just got into the habit of powering up, leaving the system alone for min or 2 then come back to it booted. was just curious about the longer boot thats all
For wallpapers ive made you can download them here

Offline Johan

  • Member
  • ***
  • Posts: 193
  • Karma: 46
  • New Forum User
    • View Profile
  • Peppermint version(s): Peppermint 10
Re: Peppermint 10 Respin Boot Time..
« Reply #14 on: May 13, 2020, 04:53:03 am »
Can you savely delete Samba? Won't it harm Peppermint? And what is Samba needed for anyway? :-\
Once Peppermint, always Peppermint.