Lentidão ao Ligar e Desligar Note com Linux Endless com SSD

#1

Boa noite

Adquiri faz duas semanas um Acer Nitro 5, i5, GEFORCE GTX, 128SSD e 1TB de HD com o \linux Endless. É minha primeira experiência com este sistema, estou gostando bastante, porém ficou um gosto bem amargo no ligar e desligar o equipamento. O tempo para ambos passa de 70 segundos, o que para mim foi uma enorme decepção, pois entendi que o SSD faria o boot o qual deveria ser muito rápido e depois a vida seguiria seu rumo no HD.

Eu neste período só fiz algumas planilhas e instalei um game (pequeno) do que já veio instalado de fábrica.

Há algo “estranho” ou este seria o comportamento normal?

#2

Can you please provide us with two informations:

  1. A diagnostic, obtained by running eos-diagnostics (upload the generated file here into this thread)
  2. Run the following command and post it’s output here in this thread:
systemd-analyze critical-chain
#3

Thank you for your support. If you need more informations or details about this issue, please let me know.

best regards

eos-diagnostic-210916_202110_UTC-0300.txt (1.23 MB)

(Attachment systemd-analyze critical-chain_20210916_2025 is missing)

#4

Please copy and paste the output of the 2nd command, systemd-analyze critical-chain. Should look something like:

graphical.target @4.154s
└─multi-user.target @4.154s
  └─eos-enable-zram.service @420ms +2.990s
    └─basic.target @409ms
      └─sockets.target @409ms
        └─uuidd.socket @409ms
          └─sysinit.target @405ms
            └─systemd-udevd.service @338ms +65ms
              └─systemd-tmpfiles-setup-dev.service @237ms +8ms
                └─kmod-static-nodes.service @227ms +5ms
                  └─systemd-journald.socket
                    └─-.mount
                      └─system.slice
                        └─-.slice
#5

Follow the filés as required. Neste regardseos-diagnostic-210916_202110_UTC-0300.txt (1,2,MB)

#6

systemd-analyze critical-chain_20210916_2025.txt (469,Bytes)

#7

Can you please run the following commands:

sudo systemctl stop mogwai-scheduled.service
sudo systemctl mask mogwai-scheduled.service

Then, reboot your PC and check if startup times have improved. If not, please run systemd-analyze blame and post it’s output. If it helps, please also let us know for further analysis as this is just a workaround in any case.

#8

Hello

After the execution I’m not felt a great improve on “up” process, but I’ll pay attention next time of turn on. Independent of the result very thankful for your help.

#9

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.