LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   I update to Mint 19 , booting for a very long time ... (https://www.linuxquestions.org/questions/linux-newbie-8/i-update-to-mint-19-booting-for-a-very-long-time-4175636126/)

thejoseph 08-10-2018 06:45 PM

I update to Mint 19 , booting for a very long time ...
 
I update my Mint to 18.3 after that to Mint 19 , And now when I turn PC on or off take a very long time and I don't know what to do ??? And is any option I come back to Mint 17. ??
>> I don't know very well about Linux <<

Ztcoracat 08-10-2018 08:14 PM

It sounds like you are going to need help with finding out why Mint is taking so long at booting up and shutting down.

I'm sorry I'm not good with booting but I'm sure that there are skilled members here that are good with that.

The closest I came to booting any Ubuntu system faster is here in my blog:
https://www.linuxquestions.org/quest...-faster-37621/

mrmazda 08-10-2018 08:35 PM

If booting is sufficiently succeeding, you can access various tools and discover clues to delays using various means in an xterm or login shell doing Ctrl-Alt-F2, including:
Code:

systemd-analyze blame
journalctl -b | egrep -i 'failed|warn'
dmesg | egrep -i 'failed|warn'
inxi -Gxx

To use them may require prepending sudo to each, or logging in as root. If you are unable to discern from their output how to proceed, post those messages here by saving their output to one or more files by appending '>>somefilename' to each command, then copying the file(s) here using code (#) tags.

JeremyBoden 08-10-2018 08:37 PM

You won't get any updates for Mint 17 beyond mid-2019.

colorpurple21859 08-10-2018 09:11 PM

at the grub prompt press e to edit the mint grub entry, delete quiet and splash on the linux line then boot to see what is happening to cause booting to take so long

AwesomeMachine 08-11-2018 01:16 AM

How long is it taking to boot? Do you ever get to the gui login?

JeremyBoden 08-11-2018 09:44 AM

Does booting the Mint 19 live distro (from USB) take an unusually long time (for a live USB boot)?

thejoseph 08-11-2018 10:55 AM

thanks very much to all friends send me answer, Unfortunately I'm under zero with Linux , If possible show me like this please >>> 1- do this 2- do that . 3- & 4- <<<<<< my dear friend mrmazda I don't no what to do I just copy and paste to terminal and still working, and coming to many written in terminal when i want to close the message still working ,,, dear friend colorpurple21859 I don't no where is grub prompt .. dear friend AwesomeMachine when I start take 2:45 minutes to ask me password after put password take 3 or 4 minutes to get ready .. dear friend JeremyBoden no any usb ..And Mint 17.1 really works very good .. dear friend Ztcoracat thanks for show me what to do ...

JeremyBoden 08-11-2018 11:44 AM

When you reboot,
( As per @colorpurple21859 )
Press and hold Shift during initial startup to see the Grub menu.
Press the 'e' key
You can now use the arrow keys to position and delete the words quiet splash.
Press enter to boot the PC - you will see many messages on the screen - something (probably containing the word error) may indicate the problem.

Note: these changes are not permanent - your changes will disappear from Grub on the next reboot.

thejoseph 08-11-2018 12:41 PM

when I copy journalctl -b | egrep -i 'failed|warn'
dmesg | egrep -i 'failed|warn'
inxi -Gxx and paste to terminal coming these >>> user@user ~/Desktop $ journalctl -b | egrep -i 'failed|warn'
Aug 12 00:26:47 user kernel: ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20170831/tbfadt-658)
Aug 12 00:26:47 user kernel: tsc: Marking TSC unstable due to check_tsc_sync_source failed
Aug 12 00:27:05 user cgmanager[746]: cgmanager: failed to collect cgroup subsystems
Aug 12 00:27:05 user systemd[1]: cgmanager.service: Failed with result 'exit-code'.
Aug 12 00:27:05 user cgmanager[806]: cgmanager: failed to collect cgroup subsystems
Aug 12 00:27:05 user cgmanager[845]: cgmanager: failed to collect cgroup subsystems
Aug 12 00:27:06 user cgmanager[847]: cgmanager: failed to collect cgroup subsystems
Aug 12 00:27:06 user cgmanager[854]: cgmanager: failed to collect cgroup subsystems
Aug 12 00:27:05 user systemd[1]: cgmanager.service: Failed with result 'exit-code'.
Aug 12 00:27:05 user systemd[1]: cgmanager.service: Failed with result 'exit-code'.
Aug 12 00:27:05 user systemd[1]: cgmanager.service: Failed with result 'exit-code'.
Aug 12 00:27:06 user systemd[1]: cgmanager.service: Failed with result 'exit-code'.
Aug 12 00:27:06 user systemd[1]: cgmanager.service: Failed with result 'exit-code'.
Aug 12 00:27:06 user systemd[1]: Failed to start Cgroup management daemon.
Aug 12 00:27:07 user udisksd[780]: failed to load module crypto: libbd_crypto.so.2: cannot open shared object file: No such file or directory
Aug 12 00:27:07 user udisksd[780]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Aug 12 00:27:07 user thermald[725]: THD engine start failed
Aug 12 00:27:08 user udisksd[780]: Failed to load the 'mdraid' libblockdev plugin
Aug 12 00:27:08 user udisksd[780]: Failed to load the 'crypto' libblockdev plugin
Aug 12 00:27:11 user wpa_supplicant[777]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed
Aug 12 00:27:11 user wpa_supplicant[777]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
Aug 12 00:27:11 user wpa_supplicant[777]: dbus: Failed to construct signal
Aug 12 00:27:11 user wpa_supplicant[777]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed
Aug 12 00:27:14 user ntpd[865]: bind(24) AF_INET6 fe80::7720:f72f:dd40:a53b%3#123 flags 0x11 failed: Cannot assign requested address
Aug 12 00:27:14 user ntpd[865]: failed to init interface for address fe80::7720:f72f:dd40:a53b%3
Aug 12 00:27:17 user /slick-greeter-set-keyboard-layout[1189]: Result: Warning! Multiple definitions of keyboard model
Warning! Multiple definitions of keyboard layout
Aug 12 00:27:36 user cinnamon-session[1281]: WARNING: t+0.75303s: Gsettings key org.gnome.Vino enabled could not be found!
Aug 12 00:35:46 user gnome-terminal-[2495]: g_menu_insert_item: assertion 'G_IS_MENU_ITEM (item)' failed
user@user ~/Desktop $ dmesg | egrep -i 'failed|warn'
[ 0.000000] ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20170831/tbfadt-658)
[ 0.043714] tsc: Marking TSC unstable due to check_tsc_sync_source failed
user@user ~/Desktop $ inxi -Gxx
Graphics: Card: Advanced Micro Devices [AMD/ATI] Wrestler [Radeon HD 7310]
bus-ID: 00:01.0 chip-ID: 1002:9809
Display Server: x11 (X.Org 1.19.6 )
drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
Resolution: 1366x768@60.06hz
OpenGL: renderer: AMD PALM (DRM 2.50.0 / 4.15.0-30-generic, LLVM 6.0.0)
version: 3.3 Mesa 18.0.5 (compat-v: 3.0) Direct Render: Yes
user@user ~/Desktop $
I don't know what is that ..

thejoseph 08-11-2018 12:53 PM

dear JeremyBoden I did nothing happen

JeremyBoden 08-11-2018 07:10 PM

That was a reasonable boot time (but lots of subsystems failing) - did you reduce the timeout period as per https://www.linuxquestions.org/quest...-faster-37621/ ?

thejoseph 08-11-2018 09:36 PM

dear JeremyBoden I did nothing happen >> user@user ~/Desktop $ #DefaultTimeoutStartSec=90s
user@user ~/Desktop $
AND .... user@user ~/Desktop $ DefaultTimeoutStartSec=10s
user@user ~/Desktop $

thejoseph 08-11-2018 10:56 PM

dear friends how can I do this ???

Run uname -r in a terminal. If it says 4.15.0-24 then reboot, after the bios screen/logo press shift to get into GRUB boot menu, select advanced, select a lower version kernel (likely you only have 4.15.0-20).

Assuming the boot now went fine, open Update Manager > View > Linux Kernels and remove the -24 kernel. Don't install that version again, wait until -26 or higher gets released.

AwesomeMachine 08-12-2018 03:14 AM

It looks like one of two things: old hardware or incorrect architecture for the OS. What kind of hardware are you using; how old is it? Are you using 32-bit or 64-bit Linux? I wouldn't worry about the errors. Everything probably succeeded later in the process.


All times are GMT -5. The time now is 11:02 AM.