Пробовал переустанавливать тоже самое - устанавливал с флэшки.
После установки всегда возникала проблема с запуском ОС - решал с помощью - параметра загрузки nomodeset, а потом устанавливал проприетарный драйвер nvidia, после этого все норм запускается - только долгая загрузка.
Гуглил, но не смог решить свою проблему с долгой загрузкой.
LM 19.2 x64 Cinnamon
System: Host: PC Kernel: 4.15.0-54-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Cinnamon 4.2.3 Distro: Linux Mint 19.2 Tina base: Ubuntu 18.04 bionic Machine: Type: Laptop System: HP product: OMEN by HP Laptop 15-ce0xx v: N/A serial: <filter> Mobo: HP model: 838F v: 40.20 serial: <filter> UEFI: American Megatrends v: F.04 date: 05/10/2017 Battery: ID-1: BAT0 charge: 46.8 Wh condition: 46.8/46.8 Wh (100%) model: Hewlett-Packard Primary status: Full CPU: Topology: Quad Core model: Intel Core i5-7300HQ bits: 64 type: MCP arch: Kaby Lake rev: 9 L2 cache: 6144 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19968 Speed: 900 MHz min/max: 800/3500 MHz Core speeds (MHz): 1: 900 2: 900 3: 900 4: 900 Graphics: Device-1: Intel HD Graphics 630 vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 Device-2: NVIDIA GP107M [GeForce GTX 1050 Mobile] vendor: Hewlett-Packard driver: nvidia v: 430.26 bus ID: 01:00.0 Display: x11 server: X.Org 1.19.6 driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa resolution: 1920x1080~60Hz OpenGL: renderer: GeForce GTX 1050/PCIe/SSE2 v: 4.6.0 NVIDIA 430.26 direct render: Yes Audio: Device-1: Intel CM238 HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Sound Server: ALSA v: k4.15.0-54-generic Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard driver: r8169 v: 2.3LK-NAPI port: c000 bus ID: 03:00.0 IF: enp3s0 state: down mac: <filter> Device-2: Intel Wireless 7265 driver: iwlwifi v: kernel port: c000 bus ID: 04:00.0 IF: wlp4s0 state: up mac: <filter> Drives: Local Storage: total: 931.51 GiB used: 8.47 GiB (0.9%) ID-1: /dev/sda vendor: HGST (Hitachi) model: HTS721010A9E630 size: 931.51 GiB Partition: ID-1: / size: 915.40 GiB used: 8.47 GiB (0.9%) fs: ext4 dev: /dev/sda2 Sensors: System Temperatures: cpu: 64.5 C mobo: N/A gpu: nvidia temp: 58 C Fan Speeds (RPM): N/A Info: Processes: 207 Uptime: 52m Memory: 7.68 GiB used: 1.48 GiB (19.3%) Init: systemd runlevel: 5 Compilers: gcc: 7.4.0 Shell: bash v: 4.4.19 inxi: 3.0.32
Startup finished in 3.043s (firmware) + 4.692s (loader) + 5.529s (kernel) + 18.709s (userspace) = 31.975s
graphical.target reached after 18.695s in userspace
graphical.target reached after 18.695s in userspace
10.318s dev-sda2.device
9.743s systemd-journal-flush.service
8.539s lvm2-monitor.service
8.029s keyboard-setup.service
7.146s systemd-sysctl.service
7.133s systemd-udevd.service
5.146s gpu-manager.service
4.134s udisks2.service
4.093s NetworkManager.service
3.204s accounts-daemon.service
2.931s ModemManager.service
2.578s grub-common.service
2.258s ubuntu-system-adjustments.service
1.954s networkd-dispatcher.service
1.862s polkit.service
1.844s thermald.service
1.525s systemd-fsck@dev-disk-by\x2duuid-E390\x2d0CB4.service
1.256s dns-clean.service
889ms systemd-tmpfiles-setup-dev.service
874ms systemd-logind.service
796ms systemd-modules-load.service
757ms dev-hugepages.mount
757ms dev-mqueue.mount
757ms sys-kernel-debug.mount
730ms systemd-remount-fs.service
667ms iio-sensor-proxy.service
667ms lm-sensors.service
659ms pppd-dns.service
653ms networking.service
627ms bluetooth.service
496ms nvidia-persistenced.service
426ms systemd-random-seed.service
419ms avahi-daemon.service
404ms systemd-journald.service
335ms swapfile.swap
332ms apparmor.service
330ms systemd-backlight@backlight:intel_backlight.service
329ms ufw.service
317ms packagekit.service
305ms colord.service
258ms blk-availability.service
215ms plymouth-read-write.service
204ms systemd-timesyncd.service
203ms systemd-resolved.service
201ms wpa_supplicant.service
196ms speech-dispatcher.service
193ms boot-efi.mount
172ms kmod-static-nodes.service
164ms upower.service
144ms kerneloops.service
127ms rsyslog.service
123ms setvtrgb.service
112ms lightdm.service
98ms systemd-tmpfiles-setup.service
87ms systemd-update-utmp.service
80ms systemd-udev-trigger.service
73ms user@1000.service
37ms systemd-tmpfiles-clean.service
34ms hddtemp.service
33ms alsa-restore.service
13ms systemd-rfkill.service
11ms systemd-update-utmp-runlevel.service
7ms console-setup.service
7ms rtkit-daemon.service
5ms sys-fs-fuse-connections.mount
4ms ureadahead-stop.service
4ms sys-kernel-config.mount
3ms systemd-user-sessions.service
1ms openvpn.service
1ms plymouth-quit-wait.service
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 @18.695s
└─lightdm.service @18.583s +112ms
└─systemd-user-sessions.service @18.393s +3ms
└─network.target @18.391s
└─NetworkManager.service @14.297s +4.093s
└─dbus.service @13.920s
└─basic.target @13.432s
└─sockets.target @13.430s
└─acpid.socket @13.429s
└─sysinit.target @13.379s
└─systemd-timesyncd.service @13.172s +204ms
└─systemd-tmpfiles-setup.service @13.040s +98ms
└─local-fs.target @13.031s
└─boot-efi.mount @12.836s +193ms
└─systemd-fsck@dev-disk-by\x2duuid-E390\x2d0CB4.service @11.256s +1.525s
└─dev-disk-by\x2duuid-E390\x2d0CB4.device @11.254s
).
У меня намного меньше. Конечно, у меня не Минт 19.2, а Минт 18.3 Мате. И не HDD, а SSD, но не в этом дело. Дело в том, принимает ли душа 1 минуту. Если нет, то ведь можно легко поменять компоненты.