[Solved] Long boot time Cinnamon Linux Mint 19

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
titimoi

[Solved] Long boot time Cinnamon Linux Mint 19

Post by titimoi »

Hello,

I've spent several hours to try all the things I've seen on the forum to try to understand why my PC needs so long to boot without identifying what the problem is.
Here are some info about my configuration:

My configuration:

Code: Select all

$ inxi -Fxz
System:    Host: thib-desktop-mint Kernel: 4.15.0-36-generic x86_64 bits: 64 gcc: 7.3.0
           Desktop: Cinnamon 3.8.9 (Gtk 3.22.30-1ubuntu1) Distro: Linux Mint 19 Tara
Machine:   Device: desktop System: Gigabyte product: Z87X-UD3H serial: N/A
           Mobo: Gigabyte model: Z87X-UD3H-CF v: x.x serial: N/A BIOS: American Megatrends v: F9 date: 03/18/2014
Battery    hidpp__0: charge: N/A condition: NA/NA Wh
           model: Logitech Wireless Mobile Mouse MX Anywhere 2 status: Discharging
CPU:       Quad core Intel Core i5-4670K (-MCP-) arch: Haswell rev.3 cache: 6144 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 27137
           clock speeds: max: 3800 MHz 1: 2429 MHz 2: 2195 MHz 3: 2203 MHz 4: 2195 MHz
Graphics:  Card-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller bus-ID: 00:02.0
           Card-2: NVIDIA GM107 [GeForce GTX 750 Ti] bus-ID: 02:00.0
           Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting,nvidia (unloaded: fbdev,vesa,nouveau)
           Resolution: 2560x1440@59.95hz
           OpenGL: renderer: llvmpipe (LLVM 6.0, 256 bits) version: 3.3 Mesa 18.0.5 Direct Render: Yes
Audio:     Card-1 Intel 8 Series/C220 Series High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
           driver: snd_hda_intel bus-ID: 00:03.0
           Card-3 NVIDIA Device 0fbc driver: snd_hda_intel bus-ID: 02:00.1
           Card-4 Logitech Webcam C270 driver: USB Audio usb-ID: 003-005
           Sound: Advanced Linux Sound Architecture v: k4.15.0-36-generic
Network:   Card: Intel Ethernet Connection I217-V driver: e1000e v: 3.2.6-k port: f080 bus-ID: 00:19.0
           IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 2500.5GB (50.8% used)
           ID-1: /dev/sda model: CT500MX500SSD1 size: 500.1GB temp: 33C
           ID-2: /dev/sdb model: ST2000DM001 size: 2000.4GB temp: 31C
Partition: ID-1: / size: 458G used: 29G (7%) fs: ext4 dev: /dev/sda1
           ID-2: swap-1 size: 2.15GB used: 0.00GB (0%) fs: swap dev: /dev/dm-0
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 29.8C mobo: 27.8C gpu: 0.0:27C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 236 Uptime: 37 min Memory: 2374.7/7864.4MB Init: systemd runlevel: 5 Gcc sys: 7.3.0
           Client: Shell (bash 4.4.191) inxi: 2.3.56 

Code: Select all

$ systemd-analyze
Startup finished in 39.240s (kernel) + 33.992s (userspace) = 1min 13.233s
graphical.target reached after 33.988s in userspace
I couldn't take anything out of this command:

Code: Select all

$ systemd-analyze blame
         26.052s NetworkManager.service
          5.690s NetworkManager-wait-online.service
          1.201s mnt-My\x2dNAS-dir1.mount
          1.199s mnt-My\x2dNAS-dir2.mount
           846ms ufw.service
           706ms udisks2.service
           691ms ModemManager.service
           667ms accounts-daemon.service
           665ms systemd-logind.service
           665ms thermald.service
           657ms ubuntu-system-adjustments.service
           646ms networkd-dispatcher.service
           641ms lm-sensors.service
           541ms mnt-Surplus.mount
           504ms apt-daily.service
           494ms alsa-restore.service
           441ms gpu-manager.service
           441ms pppd-dns.service
           436ms rsyslog.service
           381ms apt-daily-upgrade.service
           367ms systemd-cryptsetup@cryptswap1.service
           312ms dev-sda1.device
           230ms grub-common.service
           225ms wpa_supplicant.service
           224ms avahi-daemon.service
           219ms systemd-journal-flush.service
           138ms upower.service
           111ms systemd-timesyncd.service
           102ms systemd-resolved.service
            97ms keyboard-setup.service
            93ms networking.service
            87ms apparmor.service
            65ms lvm2-monitor.service
            55ms systemd-tmpfiles-setup-dev.service
            52ms systemd-udev-trigger.service
            49ms plymouth-quit-wait.service
            49ms lightdm.service
            44ms systemd-udevd.service
            42ms systemd-journald.service
            37ms systemd-sysctl.service
            34ms packagekit.service
            32ms dns-clean.service
            29ms user@1000.service
            23ms systemd-tmpfiles-setup.service
            22ms systemd-tmpfiles-clean.service
            19ms systemd-modules-load.service
            15ms plymouth-start.service
            15ms speech-dispatcher.service
            14ms apport.service
            14ms colord.service
            12ms systemd-random-seed.service
            12ms hddtemp.service
            11ms polkit.service
            11ms ureadahead-stop.service
            11ms plymouth-read-write.service
            10ms dev-mqueue.mount
             9ms dev-hugepages.mount
             9ms systemd-remount-fs.service
             7ms kerneloops.service
             7ms blk-availability.service
             7ms sys-kernel-debug.mount
             6ms kmod-static-nodes.service
             6ms systemd-update-utmp.service
             6ms sys-fs-fuse-connections.mount
             4ms systemd-user-sessions.service
             3ms dev-mapper-cryptswap1.swap
             3ms systemd-update-utmp-runlevel.service
             2ms swapfile.swap
             2ms rtkit-daemon.service
             2ms openvpn.service
             2ms sys-kernel-config.mount
             2ms console-setup.service
             1ms setvtrgb.service
             1ms nvidia-persistenced.service

Code: Select all

$ 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 @33.988s
└─multi-user.target @33.988s
  └─getty.target @33.988s
    └─getty@tty1.service @33.988s
      └─system-getty.slice @33.988s
        └─setvtrgb.service @33.986s +1ms
          └─systemd-user-sessions.service @33.922s +4ms
            └─remote-fs.target @33.921s
              └─mnt-THIB\x2dNAS-Bureau.mount @32.721s +1.199s
                └─network-online.target @32.718s
                  └─NetworkManager-wait-online.service @27.028s +5.690s
                    └─NetworkManager.service @974ms +26.052s
                      └─dbus.service @553ms
                        └─basic.target @533ms
                          └─sockets.target @533ms
                            └─cups.socket @533ms
                              └─sysinit.target @531ms
                                └─systemd-timesyncd.service @420ms +111ms
                                  └─systemd-tmpfiles-setup.service @394ms +23ms
                                    └─systemd-journal-flush.service @173ms +219ms
                                      └─systemd-journald.service @130ms +42ms
                                        └─systemd-journald.socket @128ms
                                          └─system.slice @127ms
                                            └─-.slice @125ms

Code: Select all

$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=faa0233c-ede8-40cb-87fb-209833f0578c /               ext4    errors=remount-ro 0       1
/swapfile                                 none            swap    sw              0       0
/dev/mapper/cryptswap1 none swap sw 0 0
/dev/disk/by-uuid/1A6EC47C6EC45265 /mnt/Surplus auto nosuid,nodev,nofail,x-gvfs-show 0 0
#NAS
//192.168.x.xx/dir1 /mnt/My-NAS/dir1/ cifs iocharset=utf8,file_mode=0777,dir_mode=0777,uid=1000,gid=1000  0 0
//192.168.x.xx/dir2 /mnt/My-NAS/dir2/ cifs iocharset=utf8,file_mode=0777,dir_mode=0777,uid=1000,gid=1000  0 0

Code: Select all

$ blkid
/dev/sda1: UUID="faa0233c-ede8-40cb-87fb-209833f0578c" TYPE="ext4" PARTUUID="70dd7b2b-01"
/dev/sdb1: LABEL="Surplus" UUID="1A6EC47C6EC45265" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="287b58be-4a8f-4978-bde7-b4291861fe15"
The UUID between blkid and my fstab match. I did try to comment the auto mounting of my drives (all of them) without any change.
I've tried to remove "splash quiet" and add "nomodeset" in my grub without noticeable improvements.

The linux mint splash screen is particularly big (and renders badly) on the boot, so that I thought it could be a driver problem. I switched between nouveau, nvidia-340 and nvidia-390 without success.
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 4 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
DAMIEN1307

Re: Long boot time

Post by DAMIEN1307 »

you should be able to disable at least the items im listing below from startup without any ill effects and should cut down your startup times...you can look them up on "google" but you should find that they shouldnt effect your systems operations...just copy and paste them into your terminal and then reboot for "fixes" to take effect...then rerun your systemd checks again to see results...DAMIEN

Code: Select all

sudo systemctl disable ModemManager.service

Code: Select all

 sudo systemctl disable NetworkManager-wait-online.service

Disable Dialup Modem

Code: Select all

sudo systemctl disable pppd-dns.service

Disable lvm-2-monitor

Code: Select all

 sudo systemctl disable lvm2-monitor
titimoi

Re: Long boot time

Post by titimoi »

Thanks a lot for your help Damien. I removed the systemctl items and rebooted, here are my logs now.

Code: Select all

$ 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 @27.145s
└─multi-user.target @27.145s
  └─getty.target @27.145s
    └─getty@tty1.service @27.145s
      └─system-getty.slice @27.144s
        └─setvtrgb.service @27.142s +1ms
          └─systemd-user-sessions.service @26.905s +4ms
            └─network.target @26.885s
              └─NetworkManager.service @946ms +25.937s
                └─dbus.service @587ms
                  └─basic.target @565ms
                    └─sockets.target @565ms
                      └─uuidd.socket @565ms
                        └─sysinit.target @554ms
                          └─systemd-timesyncd.service @436ms +117ms
                            └─systemd-tmpfiles-setup.service @397ms +28ms
                              └─systemd-journal-flush.service @166ms +230ms
                                └─systemd-journald.service @124ms +41ms
                                  └─systemd-journald-dev-log.socket @122ms
                                    └─system.slice @117ms
                                      └─-.slice @116ms

Code: Select all

$ systemd-analyze blame
         26.347s systemd-logind.service
         26.302s udisks2.service
         25.937s NetworkManager.service
          1.008s ufw.service
           540ms mnt-Surplus.mount
           517ms grub-common.service
           506ms accounts-daemon.service
           491ms networkd-dispatcher.service
           489ms lm-sensors.service
           487ms gpu-manager.service
           479ms ubuntu-system-adjustments.service
           477ms avahi-daemon.service
           473ms alsa-restore.service
           472ms rsyslog.service
           389ms systemd-cryptsetup@cryptswap1.service
           345ms dev-sda1.device
           232ms lightdm.service
           230ms systemd-journal-flush.service
           229ms plymouth-quit-wait.service
           138ms upower.service
           117ms systemd-timesyncd.service
           115ms systemd-resolved.service
            96ms thermald.service
            82ms networking.service
            76ms apparmor.service
            74ms keyboard-setup.service
            55ms systemd-udevd.service
            53ms systemd-udev-trigger.service
            42ms dns-clean.service
            41ms systemd-journald.service
            29ms systemd-sysctl.service
            28ms systemd-tmpfiles-setup.service
            27ms user@1000.service
            27ms polkit.service
            25ms systemd-tmpfiles-setup-dev.service
            25ms systemd-modules-load.service
            22ms mnt-My\x2dNAS-dir1.mount
            18ms systemd-update-utmp.service
            18ms colord.service
            17ms apport.service
            17ms wpa_supplicant.service
            17ms hddtemp.service
            16ms mnt-My\x2dNAS-dir2.mount
            13ms kerneloops.service
            13ms blk-availability.service
            13ms plymouth-start.service
            13ms sys-kernel-debug.mount
            11ms dev-hugepages.mount
            10ms plymouth-read-write.service
            10ms kmod-static-nodes.service
             8ms speech-dispatcher.service
             8ms dev-mqueue.mount
             8ms systemd-remount-fs.service
             7ms ureadahead-stop.service
             4ms systemd-user-sessions.service
             4ms systemd-update-utmp-runlevel.service
             3ms console-setup.service
             3ms dev-mapper-cryptswap1.swap
             2ms sys-fs-fuse-connections.mount
             2ms systemd-random-seed.service
             2ms swapfile.swap
             2ms openvpn.service
             2ms rtkit-daemon.service
             1ms nvidia-persistenced.service
             1ms setvtrgb.service
             1ms sys-kernel-config.mount
            

Code: Select all

$ systemd-analyze
Startup finished in 39.108s (kernel) + 27.150s (userspace) = 1min 6.258s
graphical.target reached after 27.145s in userspace
from the following:

Code: Select all

         25.937s NetworkManager.service
          1.008s ufw.service
          
should I understand that the network manager is taking a while or is that the firewall (ufw)?
edit: answering to myself, it's the network manager that is slow.. but he's not alone

Code: Select all

26.347s systemd-logind.service
26.302s udisks2.service
25.937s NetworkManager.service
DAMIEN1307

Re: Long boot time

Post by DAMIEN1307 »

the only other thing i see is very minor but is not needed...its "apport" service...all it does is send error reports back to ubuntu or whoever, it doesnt fix anything...also have you checked the driver update to see if you have the current recommended driver for your NVIDIA?...im also listing a couple of cleaning operations to remove old residue from uninstalls etc...dont forget to reboot after these are done...DAMIEN

Purge Apport Service

Code: Select all

sudo apt purge apport
Kernel and other Cleanups after Deletions

Code: Select all

sudo apt autoremove


do these one at a time, dont worry if the first "dpkg -l" says error etc...just means nothing is there is all...

Code: Select all

dpkg -l | grep '^rc' | awk '{print $2}' | sudo xargs dpkg --purge

Code: Select all

dpkg -l | grep '^rc' | awk '{print $2}' | xargs sudo apt-get purge
titimoi

Re: Long boot time

Post by titimoi »

Thanks Damian, I did what you suggested, my installation were clean already.

As I removed the splash screen from the boot I could tell that the pc spent a long time looking for btrfs file system, I followed the instruction found here viewtopic.php?f=46&t=272960

As I have an encrypted home, it seems that I had troubles with swap, I followed (yesterday already, so before posting) the instructions given here: viewtopic.php?t=274157

It's still slow.. not sure where to look..
DAMIEN1307

Re: Long boot time

Post by DAMIEN1307 »

look it up on google for your own specs but to my knowledge, most do not use btrfs at all so some, like myself just purge it from their systems...DAMIEN

Purge btrfs

Code: Select all

 sudo apt-get purge btrfs-progs && sudo update-initramfs -uk all
User avatar
sigmalion
Level 1
Level 1
Posts: 4
Joined: Thu Oct 11, 2018 9:40 am

Re: Long boot time

Post by sigmalion »

titimoi wrote: Wed Oct 10, 2018 4:27 pm It's still slow.. not sure where to look..
I might have found "where" inside the topic you linked about swap.

Try this: Delete /etc/initramfs-tools/conf.d/resume (make a backup somewhere for safety) and run sudo update-initramfs -u
Then reboot.

It should fix boot issues due to encryption and swap if you have run the fix from the topic you linked previously.
titimoi

Re: Long boot time

Post by titimoi »

DAMIEN1307 wrote: Wed Oct 10, 2018 5:11 pm look it up on google for your own specs but to my knowledge, most do not use btrfs at all so some, like myself just purge it from their systems...DAMIEN

Purge btrfs

Code: Select all

 sudo apt-get purge btrfs-progs && sudo update-initramfs -uk all
Thanks, I've done it before (before posting here) as this was one of the scripts I could see hanging when I removed the boot splash screen
sigmalion wrote: Thu Oct 11, 2018 9:48 am
titimoi wrote: Wed Oct 10, 2018 4:27 pm It's still slow.. not sure where to look..
I might have found "where" inside the topic you linked about swap.

Try this: Delete /etc/initramfs-tools/conf.d/resume (make a backup somewhere for safety) and run sudo update-initramfs -u
Then reboot.

It should fix boot issues due to encryption and swap if you have run the fix from the topic you linked previously.
I've played with it yesterday also, as I was still looking on my favourite search engine, I do not have any /etc/initramfs-tools/conf.d/resume anymore, and update-initramfs gave me (apparently non harming) warnings:

Code: Select all

$ cat /etc/initramfs-tools/conf.d/resume
cat: /etc/initramfs-tools/conf.d/resume: No such file or directory

Code: Select all

$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.15.0-36-generic
W: initramfs-tools configuration sets RESUME=UUID=95308c66-becb-44ba-83e8-b7069cb6fa10
W: but no matching swap device is available.
I've spent some time trying to understand those, my swap file looks ok and this comment suggests that those are just warnings.. and can be ignored.

By swap ok I mean:

Code: Select all

$ swapon --show
NAME      TYPE      SIZE USED PRIO
/dev/dm-0 partition   2G   0B   -2

Code: Select all

$  ls /home/.ecryptfs
thib

Code: Select all

$ cat /etc/crypttab 
cryptswap1 /swapfile /dev/urandom swap,offset=1024,cipher=aes-xts-plain64
User avatar
sigmalion
Level 1
Level 1
Posts: 4
Joined: Thu Oct 11, 2018 9:40 am

Re: Long boot time

Post by sigmalion »

titimoi wrote: Thu Oct 11, 2018 1:57 pm

I've played with it yesterday also, as I was still looking on my favourite search engine, I do not have any /etc/initramfs-tools/conf.d/resume anymore, and update-initramfs gave me (apparently non harming) warnings:

Code: Select all

$ cat /etc/initramfs-tools/conf.d/resume
cat: /etc/initramfs-tools/conf.d/resume: No such file or directory

Code: Select all

$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.15.0-36-generic
W: initramfs-tools configuration sets RESUME=UUID=95308c66-becb-44ba-83e8-b7069cb6fa10
W: but no matching swap device is available.
if you didn't delete it, it should be there. The initramfs-tools tells there is a resume.
Try: sudo rm /etc/initramfs-tools/conf.d/resume
copy it somewhere before removing it if you need a back up.
titimoi

Re: Long boot time

Post by titimoi »

if you didn't delete it, it should be there.
it's not there, only my backup. sudo, or not, it doesn't change anything.

Code: Select all

$ ls /etc/initramfs-tools/conf.d/
resume.old
User avatar
sigmalion
Level 1
Level 1
Posts: 4
Joined: Thu Oct 11, 2018 9:40 am

Re: Long boot time

Post by sigmalion »

Hmm try to check the UUID of your disk, if it's not the same one, it will be a clue.
titimoi

Re: Long boot time

Post by titimoi »

The culprit was in the fact that although I did not have a "resume" file, I had a "resume.old".
I removed the file and had a resume file with the following.

Code: Select all

cat /etc/initramfs-tools/conf.d/resume
RESUME=none
I do not have any warning anymore when doing "sudo update-initramfs -u -k all"

Now my boot is much quicker:

Code: Select all

graphical.target @3.260s
└─multi-user.target @3.251s
  └─getty.target @3.242s
    └─getty@tty1.service @3.233s
      └─system-getty.slice @3.224s
        └─setvtrgb.service @3.194s +10ms
          └─systemd-user-sessions.service @3.094s +33ms
            └─network.target @2.810s
              └─NetworkManager.service @2.441s +353ms
                └─dbus.service @2.432s
                  └─basic.target @2.339s
                    └─sockets.target @2.332s
                      └─dbus.socket @2.324s
                        └─sysinit.target @2.242s
                          └─systemd-timesyncd.service @1.792s +313ms
                            └─systemd-tmpfiles-setup.service @1.695s +75ms
                              └─systemd-journal-flush.service @819ms +865ms
                                └─systemd-remount-fs.service @606ms +122ms
                                  └─systemd-journald.socket @456ms
                                    └─system.slice @228ms
dj23rus

Re: [Solved] Long boot time Cinnamon Linux Mint 19

Post by dj23rus »

Same problem on laptop ASUS VivoBook E406SA-BV011T.
The laptop booted quickly on Windows 10, but I hate it, since Mac is home. I decided to remove Windows 10 and install Linux. Currently installed Linux Mint 19 64-bit from a DVD disc, UEFI partition option in the boot menu. The OS loads long compared to Win 10, the Mint logo appears 10 seconds after the manufacturer's logo, and then another 30 seconds wait until it is fully launched.
Thanks for any suggestions.

inxi -Fxz

Code: Select all

System: Host: mrx-VivoBook-14-ASUS-Laptop-E406SA Kernel: 4.15.0-36-generic x86_64
bits: 64 gcc: 7.3.0
Desktop: Cinnamon 3.8.9 (Gtk 3.22.30-1ubuntu1)
Distro: Linux Mint 19 Tara
Machine: Device: laptop System: ASUSTeK product: VivoBook 14_ASUS Laptop E406SA v: 1.0 serial: N/A
Mobo: ASUSTeK model: E406SA v: 1.0 serial: N/A
UEFI: American Megatrends v: E406SA.303 date: 03/21/2018
Battery BAT0: charge: 21.7 Wh 40.5% condition: 53.6/57.0 Wh (94%)
model: ASUSTeK X550A26 status: Discharging
CPU: Dual core Intel Celeron N3060 (-MCP-)
arch: Airmont rev.4 cache: 1024 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 6400
clock speeds: max: 2480 MHz 1: 1378 MHz 2: 1145 MHz
Graphics: Card: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller
bus-ID: 00:02.0
Display Server: x11 (X.Org 1.19.6 )
drivers: modesetting (unloaded: fbdev,vesa)
Resolution: 1366x768@60.00hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 400 (Braswell)
version: 4.5 Mesa 18.0.5 Direct Render: Yes
Audio: Card Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Def. Audio Controller
driver: snd_hda_intel bus-ID: 00:1b.0
Sound: Advanced Linux Sound Architecture v: k4.15.0-36-generic
Network: Card: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter
driver: ath9k bus-ID: 02:00.0
IF: wlp2s0 state: up mac: <filter>
Drives: HDD Total Size: NA (-)
ID-1: /dev/mmcblk1 model: N/A size: 62.5GB
Partition: ID-1: / size: 57G used: 11G (20%) fs: ext4 dev: /dev/mmcblk1p2
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 50.0C mobo: 42.0C
Fan Speeds (in rpm): cpu: 0
Info: Processes: 178 Uptime: 1:31 Memory: 655.3/3836.8MB
Init: systemd runlevel: 5 Gcc sys: 7.3.0
Client: Shell (bash 4.4.191) inxi: 2.3.56
Locked

Return to “Installation & Boot”