Черный экран при загрузке

Правила форума
Как правильно задавать вопросы Правильно сформулированный вопрос и его грамотное оформление способствует высокой вероятности получения достаточно содержательного и по существу ответа. Общая рекомендация по составлению тем: 1. Версия ОС вместе с разрядностью. Пример: LM 18.1 x64, LM Sarah x32 2. DE. Если вопрос касается двух, то через запятую. (xfce, KDE, cinnamon, mate) 3. Какое железо. (достаточно вывод inxi -Fxz в спойлере (как пользоваться спойлером смотрим здесь)) или же дать ссылку на hw-probe 4. Суть. Желательно с выводом консоли, логами. 5. Скрин. Просьба указывать 1, 2 и 3 независимо от того, имеет ли это отношение к вопросу или нет. Так же не забываем об общих правилах Как пример вот
Аватара пользователя

Автор темы
FliXis
Сообщения: 319
Зарегистрирован: 31 авг 2016, 11:01
Решено: 8
Благодарил (а): 75 раз
Поблагодарили: 21 раз

Черный экран при загрузке

Сообщение FliXis » 01 окт 2017, 01:07

Добрый день!

Mint 18.2 x64 cinnamon
4.10.0-35-generic

Внезапно, после граба черный экран, ни единой надписи, в tty не переключалось. Удалось зайти с ядра 4.8.0-53, после чего я поставил обновы к видеодрайверу(как раз вышли пару дней назад) и перезагрузился. Ядро при загрузке не менял, т.е. 4.10 грузанулось по дефолту, но все стартануло нормально.
Что это было и как можно узнать? Впервые с таким сталкиваюсь.

Аватара пользователя

Автор темы
FliXis
Сообщения: 319
Зарегистрирован: 31 авг 2016, 11:01
Решено: 8
Благодарил (а): 75 раз
Поблагодарили: 21 раз

Черный экран при загрузке

Сообщение FliXis » 01 окт 2017, 14:08

Сегодня вот опять тоже самое сейчас произошло. Зашел с 4.8, но при загрузке системы много строк со статусом фейл было. :sad:

Аватара пользователя

Автор темы
FliXis
Сообщения: 319
Зарегистрирован: 31 авг 2016, 11:01
Решено: 8
Благодарил (а): 75 раз
Поблагодарили: 21 раз

Черный экран при загрузке

Сообщение FliXis » 01 окт 2017, 14:18

В smartctl нашел вот такое вот на харде под файловую помойку, что у меня в /mnt примонтирован. Но как я понимаю, это старые ошибки, да и система у меня стоит совсем на другом диске, на ssd.

Код: Выделить всё

Complete error log:

SMART Error Log Version: 1
ATA Error Count: 3
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 3 occurred at disk power-on lifetime: 4203 hours (175 days + 3 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 51 01 2f 39 64 00  Error: ICRC, ABRT at LBA = 0x0064392f = 6568239

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 00 28 39 64 40 00      00:04:03.938  WRITE FPDMA QUEUED
  ec 00 00 00 00 00 00 00      00:04:03.927  IDENTIFY DEVICE
  ef 10 03 00 00 00 00 00      00:04:03.917  SET FEATURES [Enable SATA feature]
  ef 10 02 00 00 00 00 00      00:04:03.907  SET FEATURES [Enable SATA feature]
  b1 c1 00 00 00 00 00 00      00:04:03.897  DEVICE CONFIGURATION FREEZE LOCK [OBS-ACS-3]

Error 2 occurred at disk power-on lifetime: 4203 hours (175 days + 3 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 51 01 2f 39 64 00  Error: ICRC, ABRT at LBA = 0x0064392f = 6568239

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 00 28 39 64 40 00      00:04:03.796  WRITE FPDMA QUEUED
  ec 00 00 00 00 00 00 00      00:04:03.785  IDENTIFY DEVICE
  ef 10 03 00 00 00 00 00      00:04:03.775  SET FEATURES [Enable SATA feature]
  ef 10 02 00 00 00 00 00      00:04:03.765  SET FEATURES [Enable SATA feature]
  b1 c1 00 00 00 00 00 00      00:04:03.755  DEVICE CONFIGURATION FREEZE LOCK [OBS-ACS-3]

Error 1 occurred at disk power-on lifetime: 4203 hours (175 days + 3 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 51 01 2f 39 64 00  Error: ICRC, ABRT at LBA = 0x0064392f = 6568239

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 00 28 39 64 40 00      00:04:03.664  WRITE FPDMA QUEUED
  ea 00 00 00 00 00 00 00      00:04:03.664  FLUSH CACHE EXT
  61 08 00 50 59 5f 40 00      00:03:58.112  WRITE FPDMA QUEUED
  ea 00 00 00 00 00 00 00      00:03:58.100  FLUSH CACHE EXT
  61 08 00 d8 59 5f 40 00      00:03:58.099  WRITE FPDMA QUEUED

Аватара пользователя

slant
Сообщения: 1891
Зарегистрирован: 21 июн 2017, 15:09
Решено: 31
Благодарил (а): 15 раз
Поблагодарили: 822 раза

Черный экран при загрузке

Сообщение slant » 01 окт 2017, 14:23

FliXis писал(а):
Что это было и как можно узнать? Впервые с таким сталкиваюсь.
Читать логи и журналы. Как же еще?

И это... Телепаты в перманентном отпуске... Хотите внятной помощи здесь - конфиг железа, и подробности ошибок в студию.

Аватара пользователя

Автор темы
FliXis
Сообщения: 319
Зарегистрирован: 31 авг 2016, 11:01
Решено: 8
Благодарил (а): 75 раз
Поблагодарили: 21 раз

Черный экран при загрузке

Сообщение FliXis » 01 окт 2017, 14:26

Код: Выделить всё

System:    Host: host Kernel: 4.8.0-53-generic x86_64 (64 bit gcc: 5.4.0)
           Desktop: Cinnamon 3.4.6 (Gtk 3.18.9-1ubuntu3.3)
           Distro: Linux Mint 18.2 Sonya
Machine:   Mobo: ASUSTeK model: G750JH v: 1.0
           Bios: American Megatrends v: G750JH.206 date: 12/02/2013
CPU:       Quad core Intel Core i7-4700HQ (-HT-MCP-) cache: 6144 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 19156
           clock speeds: max: 3400 MHz 1: 2400 MHz 2: 2407 MHz 3: 2399 MHz
           4: 2400 MHz 5: 2412 MHz 6: 2485 MHz 7: 2435 MHz 8: 2400 MHz
Graphics:  Card: NVIDIA GK104M [GeForce GTX 780M] bus-ID: 01:00.0
           Display Server: X.Org 1.18.4 drivers: nouveau (unloaded: fbdev,vesa)
           Resolution: 1920x1080@59.99hz
           GLX Renderer: Gallium 0.4 on NVE4
           GLX Version: 3.0 Mesa 17.0.7 Direct Rendering: Yes
Audio:     Card-1 Intel 8 Series/C220 Series High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 NVIDIA GK104 HDMI Audio Controller
           driver: snd_hda_intel bus-ID: 01:00.1
           Sound: Advanced Linux Sound Architecture v: k4.8.0-53-generic
Network:   Card-1: Qualcomm Atheros AR9462 Wireless Network Adapter
           driver: ath9k bus-ID: 03:00.0
           IF: wlp3s0 state: up mac: <filter>
           Card-2: Qualcomm Atheros QCA8171 Gigabit Ethernet
           driver: alx port: d000 bus-ID: 04:00.0
           IF: enp4s0 state: down mac: <filter>
Drives:    HDD Total Size: 1756.4GB (21.9% used)
           ID-1: /dev/sda model: HGST_HTS541515A9 size: 1500.3GB
           ID-2: /dev/sdb model: LITEONIT_LCS size: 256.1GB
Partition: ID-1: / size: 36G used: 7.4G (21%) fs: btrfs dev: /dev/dm-0
           ID-2: /boot size: 473M used: 123M (28%) fs: ext2 dev: /dev/sdb8
           ID-3: /home size: 87G used: 18G (21%) fs: btrfs dev: /dev/dm-1
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 46.0C mobo: N/A
           Fan Speeds (in rpm): cpu: 2300
Info:      Processes: 336 Uptime: 30 min Memory: 2147.2/24060.4MB
           Init: systemd runlevel: 5 Gcc sys: 5.4.0
           Client: Shell (bash 4.3.481) inxi: 2.2.35 

Аватара пользователя

Автор темы
FliXis
Сообщения: 319
Зарегистрирован: 31 авг 2016, 11:01
Решено: 8
Благодарил (а): 75 раз
Поблагодарили: 21 раз

Черный экран при загрузке

Сообщение FliXis » 01 окт 2017, 14:28

Опаньки, почему-то пишет драйвер ноувеау хотя должен стоять проприетарный.

/var/log/dmesg - (Nothing has been logged yet.)

Аватара пользователя

slant
Сообщения: 1891
Зарегистрирован: 21 июн 2017, 15:09
Решено: 31
Благодарил (а): 15 раз
Поблагодарили: 822 раза

Черный экран при загрузке

Сообщение slant » 01 окт 2017, 14:43

Все-таки тут надо еще журналы загрузки с ошибками смотреть. Те что в /var/log. Можно еще через journalctl. Помогут две команды:
journalctl --list-boot - покажет список загрузок в журналах. (самое первое число в каждой строке - номер загрузки для следующей команды)
journalctl -b <x> - покажет журнал загрузки с номером x. Если без x - покажет журнал самой последней загрузки.

Аватара пользователя

Автор темы
FliXis
Сообщения: 319
Зарегистрирован: 31 авг 2016, 11:01
Решено: 8
Благодарил (а): 75 раз
Поблагодарили: 21 раз

Черный экран при загрузке

Сообщение FliXis » 01 окт 2017, 14:46

Код: Выделить всё

flixis@host ~ $ journalctl -b -p err
-- Logs begin at Sun 2017-10-01 16:55:41 MSK, end at Sun 2017-10-01 17:43:07 MSK
Oct 01 16:55:41 host kernel: usb 3-5: string descriptor 0 read error: -22
Oct 01 16:55:41 host systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx2
Oct 01 16:55:41 host kernel: usb 3-5: string descriptor 0 read error: -22
Oct 01 16:55:42 host systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx2
Oct 01 16:55:42 host systemd[1]: dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserv
Oct 01 16:55:42 host systemd[1]: Failed to start Braille Device Support.
Oct 01 16:55:42 host systemd[1]: Failed to start Braille Device Support.
Oct 01 16:55:43 host systemd[1]: Failed to start Braille Device Support.
Oct 01 16:55:43 host systemd[1]: Failed to start Braille Device Support.
Oct 01 16:55:43 host systemd[1]: Failed to start Braille Device Support.
Oct 01 16:55:43 host systemd[1]: Failed to start Braille Device Support.
Oct 01 16:55:44 host bluetoothd[1282]: Failed to obtain handles for "Service Cha
Oct 01 16:55:44 host bluetoothd[1282]: Not enough free handles to register servi
Oct 01 16:55:44 host bluetoothd[1282]: Error adding Link Loss service
Oct 01 16:55:44 host bluetoothd[1282]: Not enough free handles to register servi
Oct 01 16:55:44 host bluetoothd[1282]: Not enough free handles to register servi
Oct 01 16:55:44 host bluetoothd[1282]: Not enough free handles to register servi
Oct 01 16:55:44 host bluetoothd[1282]: Current Time Service could not be registe
Oct 01 16:55:44 host bluetoothd[1282]: gatt-time-server: Input/output error (5)
Oct 01 16:55:44 host bluetoothd[1282]: Not enough free handles to register servi
Oct 01 16:55:44 host bluetoothd[1282]: Not enough free handles to register servi
Oct 01 16:55:44 host bluetoothd[1282]: Sap driver initialization failed.
lines 1-23...skipping...
-- Logs begin at Sun 2017-10-01 16:55:41 MSK, end at Sun 2017-10-01 17:43:07 MSK. --
Oct 01 16:55:41 host kernel: usb 3-5: string descriptor 0 read error: -22
Oct 01 16:55:41 host systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000
Oct 01 16:55:41 host kernel: usb 3-5: string descriptor 0 read error: -22
Oct 01 16:55:42 host systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000
Oct 01 16:55:42 host systemd[1]: dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device appeared twice with different sysfs paths /sys/devices
Oct 01 16:55:42 host systemd[1]: Failed to start Braille Device Support.
Oct 01 16:55:42 host systemd[1]: Failed to start Braille Device Support.
Oct 01 16:55:43 host systemd[1]: Failed to start Braille Device Support.
Oct 01 16:55:43 host systemd[1]: Failed to start Braille Device Support.
Oct 01 16:55:43 host systemd[1]: Failed to start Braille Device Support.
Oct 01 16:55:43 host systemd[1]: Failed to start Braille Device Support.
Oct 01 16:55:44 host bluetoothd[1282]: Failed to obtain handles for "Service Changed" characteristic
Oct 01 16:55:44 host bluetoothd[1282]: Not enough free handles to register service
Oct 01 16:55:44 host bluetoothd[1282]: Error adding Link Loss service
Oct 01 16:55:44 host bluetoothd[1282]: Not enough free handles to register service
Oct 01 16:55:44 host bluetoothd[1282]: Not enough free handles to register service
Oct 01 16:55:44 host bluetoothd[1282]: Not enough free handles to register service
Oct 01 16:55:44 host bluetoothd[1282]: Current Time Service could not be registered
Oct 01 16:55:44 host bluetoothd[1282]: gatt-time-server: Input/output error (5)
Oct 01 16:55:44 host bluetoothd[1282]: Not enough free handles to register service
Oct 01 16:55:44 host bluetoothd[1282]: Not enough free handles to register service
Oct 01 16:55:44 host bluetoothd[1282]: Sap driver initialization failed.
Oct 01 16:55:44 host bluetoothd[1282]: sap-server: Operation not permitted (1)
Oct 01 16:55:44 host nvidia-persistenced[1233]: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 118 has read and write permissions for those files.
Oct 01 16:55:44 host systemd-udevd[1420]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host ntpdate[1475]: name server cannot be used: Temporary failure in name resolution (-3)
Oct 01 16:55:44 host systemd[1505]: nvidia-persistenced.service: Failed at step EXEC spawning /usr/bin/nvidia-persistenced: No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1515]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1536]: nvidia-persistenced.service: Failed at step EXEC spawning /usr/bin/nvidia-persistenced: No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1542]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1551]: nvidia-persistenced.service: Failed at step EXEC spawning /usr/bin/nvidia-persistenced: No such file or directory
Oct 01 16:55:44 host NetworkManager[1322]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1556]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1563]: nvidia-persistenced.service: Failed at step EXEC spawning /usr/bin/nvidia-persistenced: No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1568]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1579]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1588]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1597]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1607]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1616]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1625]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1634]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host wpa_supplicant[1570]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
Oct 01 16:55:44 host wpa_supplicant[1570]: dbus: Failed to construct signal
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1643]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1652]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1661]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1670]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1679]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1688]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1697]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1706]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1715]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1724]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1733]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1742]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1751]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1760]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1769]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1778]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1787]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1796]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1805]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1814]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1832]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1845]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1854]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1863]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1872]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1881]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1890]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1899]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1908]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1917]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:44 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 16:55:44 host systemd-udevd[1926]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 16:55:45 host lightdm[1971]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Oct 01 16:55:45 host lightdm[1971]: PAM adding faulty module: pam_kwallet.so
Oct 01 16:55:45 host lightdm[1971]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Oct 01 16:55:45 host lightdm[1971]: PAM adding faulty module: pam_kwallet5.so
Oct 01 16:55:46 host lightdm[2050]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Oct 01 16:55:46 host lightdm[2050]: PAM adding faulty module: pam_kwallet.so
Oct 01 16:55:46 host lightdm[2050]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Oct 01 16:55:46 host lightdm[2050]: PAM adding faulty module: pam_kwallet5.so
Oct 01 16:55:54 host pulseaudio[2281]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
Oct 01 16:55:54 host pulseaudio[2637]: [pulseaudio] pid.c: Daemon already running.
Oct 01 16:55:55 host ntpdate[2610]: the NTP socket is in use, exiting
Oct 01 16:55:57 host ntpd[2510]: bind(25) AF_INET6 2a02:2168:1a2c:1a00:74dc:64d1:94d8:62f1#123 flags 0x11 failed: Cannot assign requested address
Oct 01 16:55:57 host ntpd[2510]: unable to create socket on wlp3s0 (6) for 2a02:2168:1a2c:1a00:74dc:64d1:94d8:62f1#123
Oct 01 16:55:59 host bluetoothd[1282]: Failed to set mode: Blocked through rfkill (0x12)
Oct 01 17:25:47 host sudo[6216]:   flixis : a password is required ; TTY=pts/0 ; PWD=/home/flixis ; USER=root ; COMMAND=/usr/sbin/hddtemp -nq -u C /dev/sda
Oct 01 17:25:47 host sudo[6235]:   flixis : a password is required ; TTY=pts/0 ; PWD=/home/flixis ; USER=root ; COMMAND=/usr/sbin/hddtemp -nq -u C /dev/sdb
lines 70-134/134 (END)

Аватара пользователя

slant
Сообщения: 1891
Зарегистрирован: 21 июн 2017, 15:09
Решено: 31
Благодарил (а): 15 раз
Поблагодарили: 822 раза

Черный экран при загрузке

Сообщение slant » 01 окт 2017, 15:18

Как минимум, дрова встали криво. "failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory". Исправляйте сначала это.

И проверьте, на счет активности карты nvidia в UEFI ноутбука. Вроде бы у вас не гибридное видео, но все-же.

Аватара пользователя

Автор темы
FliXis
Сообщения: 319
Зарегистрирован: 31 авг 2016, 11:01
Решено: 8
Благодарил (а): 75 раз
Поблагодарили: 21 раз

Черный экран при загрузке

Сообщение FliXis » 01 окт 2017, 15:43

В дровах выбрал свободный драйвер и перезагрузился. Мне на нем конечно оставаться особо нельзя - изображение раз-два в день зависает намертво, только reisub помогает, но пока хватит. В данный момент такие ошибки:

Код: Выделить всё

flixis@host ~ $ journalctl -b -p err
flixis@host ~ $ journalctl -b -p err
-- Logs begin at Sun 2017-10-01 18:41:18 MSK, end at Sun 2017-10-01 18:41:35 MSK
Oct 01 18:41:18 host kernel: usb 3-5: string descriptor 0 read error: -22
Oct 01 18:41:18 host systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx2
Oct 01 18:41:18 host systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx2
Oct 01 18:41:18 host systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx2
Oct 01 18:41:18 host systemd[1]: dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserv
Oct 01 18:41:21 host bluetoothd[1172]: Failed to obtain handles for "Service Cha
Oct 01 18:41:21 host bluetoothd[1172]: Not enough free handles to register servi
Oct 01 18:41:21 host bluetoothd[1172]: Error adding Link Loss service
Oct 01 18:41:21 host bluetoothd[1172]: Not enough free handles to register servi
Oct 01 18:41:21 host bluetoothd[1172]: Not enough free handles to register servi
Oct 01 18:41:21 host bluetoothd[1172]: Not enough free handles to register servi
Oct 01 18:41:21 host bluetoothd[1172]: Current Time Service could not be registe
Oct 01 18:41:21 host bluetoothd[1172]: gatt-time-server: Input/output error (5)
Oct 01 18:41:21 host bluetoothd[1172]: Not enough free handles to register servi
Oct 01 18:41:21 host bluetoothd[1172]: Not enough free handles to register servi
Oct 01 18:41:21 host bluetoothd[1172]: Sap driver initialization failed.
Oct 01 18:41:21 host bluetoothd[1172]: sap-server: Operation not permitted (1)
Oct 01 18:41:21 host ntpdate[1336]: name server cannot be used: Temporary failur
Oct 01 18:41:21 host NetworkManager[1182]: nm_device_get_device_type: assertion 
Oct 01 18:41:21 host wpa_supplicant[1407]: dbus: wpa_dbus_get_object_properties:
Oct 01 18:41:21 host wpa_supplicant[1407]: dbus: Failed to construct signal
Oct 01 18:41:21 host lightdm[1434]: PAM unable to dlopen(pam_kwallet.so): /lib/s
lines 1-23...skipping...
-- Logs begin at Sun 2017-10-01 18:41:18 MSK, end at Sun 2017-10-01 18:41:35 MSK. --
Oct 01 18:41:18 host kernel: usb 3-5: string descriptor 0 read error: -22
Oct 01 18:41:18 host systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000
Oct 01 18:41:18 host systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000
Oct 01 18:41:18 host systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000
Oct 01 18:41:18 host systemd[1]: dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device appeared twice with different sysfs paths /sys/devices
Oct 01 18:41:21 host bluetoothd[1172]: Failed to obtain handles for "Service Changed" characteristic
Oct 01 18:41:21 host bluetoothd[1172]: Not enough free handles to register service
Oct 01 18:41:21 host bluetoothd[1172]: Error adding Link Loss service
Oct 01 18:41:21 host bluetoothd[1172]: Not enough free handles to register service
Oct 01 18:41:21 host bluetoothd[1172]: Not enough free handles to register service
Oct 01 18:41:21 host bluetoothd[1172]: Not enough free handles to register service
Oct 01 18:41:21 host bluetoothd[1172]: Current Time Service could not be registered
Oct 01 18:41:21 host bluetoothd[1172]: gatt-time-server: Input/output error (5)
Oct 01 18:41:21 host bluetoothd[1172]: Not enough free handles to register service
Oct 01 18:41:21 host bluetoothd[1172]: Not enough free handles to register service
Oct 01 18:41:21 host bluetoothd[1172]: Sap driver initialization failed.
Oct 01 18:41:21 host bluetoothd[1172]: sap-server: Operation not permitted (1)
Oct 01 18:41:21 host ntpdate[1336]: name server cannot be used: Temporary failure in name resolution (-3)
Oct 01 18:41:21 host NetworkManager[1182]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
Oct 01 18:41:21 host wpa_supplicant[1407]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
Oct 01 18:41:21 host wpa_supplicant[1407]: dbus: Failed to construct signal
Oct 01 18:41:21 host lightdm[1434]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Oct 01 18:41:21 host lightdm[1434]: PAM adding faulty module: pam_kwallet.so
Oct 01 18:41:21 host lightdm[1434]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Oct 01 18:41:21 host lightdm[1434]: PAM adding faulty module: pam_kwallet5.so
Oct 01 18:41:22 host lightdm[1513]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Oct 01 18:41:22 host lightdm[1513]: PAM adding faulty module: pam_kwallet.so
Oct 01 18:41:22 host lightdm[1513]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Oct 01 18:41:22 host lightdm[1513]: PAM adding faulty module: pam_kwallet5.so
Oct 01 18:41:29 host pulseaudio[1709]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
И что еще за dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserv - при чем тут майкрософт? Но у меня дуалбут стоит, если что.
Последний раз редактировалось пользователем 1 FliXis; всего редактировалось раз: 1

Аватара пользователя

darkfenix
Сообщения: 5612
Зарегистрирован: 27 июн 2017, 10:36
Решено: 62
Откуда: Нижний Тагил
Благодарил (а): 309 раз
Поблагодарили: 1038 раз

Черный экран при загрузке

Сообщение darkfenix » 01 окт 2017, 15:46

Если драйвер ставил из родных реп, то попробуй поставить от сюда
Изображение

Аватара пользователя

Автор темы
FliXis
Сообщения: 319
Зарегистрирован: 31 авг 2016, 11:01
Решено: 8
Благодарил (а): 75 раз
Поблагодарили: 21 раз

Черный экран при загрузке

Сообщение FliXis » 01 окт 2017, 15:49

Драйвер ставил не из родных, а из ppa:graphics-drivers/ppa

Аватара пользователя

Unborn
Сообщения: 1778
Зарегистрирован: 03 сен 2016, 10:36
Решено: 24
Благодарил (а): 4 раза
Поблагодарили: 253 раза

Черный экран при загрузке

Сообщение Unborn » 01 окт 2017, 15:55

FliXis писал(а): Внезапно, после граба черный экран, ни единой надписи, в tty не переключалось. Удалось зайти с ядра 4.8.0-53, после чего я поставил обновы к видеодрайверу(как раз вышли пару дней назад) и перезагрузился. Ядро при загрузке не менял, т.е. 4.10 грузанулось по дефолту, но все стартануло нормально.
Что это было и как можно узнать? Впервые с таким сталкиваюсь.
Драйвер не собрался под 4.10. Вывод нужно сразу смотреть было. Нормальное явление, когда dkms не собирается по другую версию ядра. Подробности сразу открывать и смотреть весь процесс установки нового ядра, а не пялиться на ползунок, чтобы потом глупых вопросов не задавать.
Может и еще чего тоже не собралось. Смотри лог dkms.
И зачем тебе дисплей брайля? Или со зрением не порядок?

Аватара пользователя

Автор темы
FliXis
Сообщения: 319
Зарегистрирован: 31 авг 2016, 11:01
Решено: 8
Благодарил (а): 75 раз
Поблагодарили: 21 раз

Черный экран при загрузке

Сообщение FliXis » 01 окт 2017, 16:30

Хм, но я драйвер ставил вчера ночью, когда уже возникла проблема с черным экраном после граба. А учитывая, что я две недели нормально сидел на 4.10 + проприетарные nvidia, и я постоянно проверял, что запущен именно проприетарный, а не nouveau т.е. в прошлый раз драйвер собрался.
Может ядро как-то полетело? Наверно стоит удалить 4.10 и установить заново, потом глянуть ошибки и уже после этого накатить nvidia из оф-реп. Но как могло полететь ядро?
И зачем тебе дисплей брайля? Или со зрением не порядок?
Со зрением ок, я его не ставил, даже не знаю что это

Аватара пользователя

Автор темы
FliXis
Сообщения: 319
Зарегистрирован: 31 авг 2016, 11:01
Решено: 8
Благодарил (а): 75 раз
Поблагодарили: 21 раз

Черный экран при загрузке

Сообщение FliXis » 01 окт 2017, 16:40

Лог dkms от 4.10, если я тот нашел конечно.

Код: Выделить всё

DKMS make.log for ndiswrapper-1.60 for kernel 4.10.0-35-generic (x86_64)
Tue Sep 19 05:07:38 MSK 2017
make: Entering directory '/usr/src/linux-headers-4.10.0-35-generic'
  LD      /var/lib/dkms/ndiswrapper/1.60/build/built-in.o
  MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/crt_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/hal_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ndis_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/rtl_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/usb_exports.h
  MKSTUBS /var/lib/dkms/ndiswrapper/1.60/build/win2lin_stubs.h
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/crt.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/hal.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/iw_ndis.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/loader.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/ndis.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/pe_linker.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/pnp.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/proc.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/rtl.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/wrapmem.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/wrapndis.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/wrapper.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/usb.o
  AS [M]  /var/lib/dkms/ndiswrapper/1.60/build/win2lin_stubs.o
  AS [M]  /var/lib/dkms/ndiswrapper/1.60/build/lin2win.o
  LD [M]  /var/lib/dkms/ndiswrapper/1.60/build/ndiswrapper.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /var/lib/dkms/ndiswrapper/1.60/build/ndiswrapper.mod.o
  LD [M]  /var/lib/dkms/ndiswrapper/1.60/build/ndiswrapper.ko
make: Leaving directory '/usr/src/linux-headers-4.10.0-35-generic'

Аватара пользователя

Автор темы
FliXis
Сообщения: 319
Зарегистрирован: 31 авг 2016, 11:01
Решено: 8
Благодарил (а): 75 раз
Поблагодарили: 21 раз

Черный экран при загрузке

Сообщение FliXis » 01 окт 2017, 17:24

Поставил более свежее ядро 4.8, чем было у меня. 4.10 удалил. Затем пуржанул нвидиа-драйвер, перезагрузкился и установил драйвер из дефолтных реп 375. Перезагружаюсь - nouveau почему. Добавил nouveau в блеклист, перезагрузился. При загрузке показало одну строку с красным статусом.

Код: Выделить всё

flixis@host ~ $ journalctl -b -p err
-- Logs begin at Sun 2017-10-01 20:18:36 MSK, end at Sun 2017-10-01 20:19:42 MSK
Oct 01 20:18:37 host kernel: usb 3-5: string descriptor 0 read error: -22
Oct 01 20:18:37 host systemd-udevd[830]: failed to execute '/usr/bin/nvidia-smi'
Oct 01 20:18:37 host systemd[1]: dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserv
Oct 01 20:18:37 host systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx2
Oct 01 20:18:41 host systemd[1111]: nvidia-persistenced.service: Failed at step 
Oct 01 20:18:41 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 20:18:41 host bluetoothd[1173]: Failed to obtain handles for "Service Cha
Oct 01 20:18:41 host bluetoothd[1173]: Not enough free handles to register servi
Oct 01 20:18:41 host bluetoothd[1173]: Error adding Link Loss service
Oct 01 20:18:41 host bluetoothd[1173]: Not enough free handles to register servi
Oct 01 20:18:41 host bluetoothd[1173]: Not enough free handles to register servi
Oct 01 20:18:41 host bluetoothd[1173]: Not enough free handles to register servi
Oct 01 20:18:41 host bluetoothd[1173]: Current Time Service could not be registe
Oct 01 20:18:41 host bluetoothd[1173]: gatt-time-server: Input/output error (5)
Oct 01 20:18:41 host bluetoothd[1173]: Not enough free handles to register servi
Oct 01 20:18:41 host bluetoothd[1173]: Not enough free handles to register servi
Oct 01 20:18:41 host bluetoothd[1173]: Sap driver initialization failed.
Oct 01 20:18:41 host bluetoothd[1173]: sap-server: Operation not permitted (1)
Oct 01 20:18:41 host ntpdate[1324]: name server cannot be used: Temporary failur
Oct 01 20:18:41 host NetworkManager[1134]: nm_device_get_device_type: assertion 
Oct 01 20:18:41 host wpa_supplicant[1380]: dbus: wpa_dbus_get_object_properties:
Oct 01 20:18:41 host wpa_supplicant[1380]: dbus: Failed to construct signal
lines 1-23...skipping...
-- Logs begin at Sun 2017-10-01 20:18:36 MSK, end at Sun 2017-10-01 20:19:42 MSK. --
Oct 01 20:18:37 host kernel: usb 3-5: string descriptor 0 read error: -22
Oct 01 20:18:37 host systemd-udevd[830]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Oct 01 20:18:37 host systemd[1]: dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device appeared twice with different sysfs paths /sys/devices
Oct 01 20:18:37 host systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000
Oct 01 20:18:41 host systemd[1111]: nvidia-persistenced.service: Failed at step EXEC spawning /usr/bin/nvidia-persistenced: No such file or directory
Oct 01 20:18:41 host systemd[1]: Failed to start NVIDIA Persistence Daemon.
Oct 01 20:18:41 host bluetoothd[1173]: Failed to obtain handles for "Service Changed" characteristic
Oct 01 20:18:41 host bluetoothd[1173]: Not enough free handles to register service
Oct 01 20:18:41 host bluetoothd[1173]: Error adding Link Loss service
Oct 01 20:18:41 host bluetoothd[1173]: Not enough free handles to register service
Oct 01 20:18:41 host bluetoothd[1173]: Not enough free handles to register service
Oct 01 20:18:41 host bluetoothd[1173]: Not enough free handles to register service
Oct 01 20:18:41 host bluetoothd[1173]: Current Time Service could not be registered
Oct 01 20:18:41 host bluetoothd[1173]: gatt-time-server: Input/output error (5)
Oct 01 20:18:41 host bluetoothd[1173]: Not enough free handles to register service
Oct 01 20:18:41 host bluetoothd[1173]: Not enough free handles to register service
Oct 01 20:18:41 host bluetoothd[1173]: Sap driver initialization failed.
Oct 01 20:18:41 host bluetoothd[1173]: sap-server: Operation not permitted (1)
Oct 01 20:18:41 host ntpdate[1324]: name server cannot be used: Temporary failure in name resolution (-3)
Oct 01 20:18:41 host NetworkManager[1134]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
Oct 01 20:18:41 host wpa_supplicant[1380]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
Oct 01 20:18:41 host wpa_supplicant[1380]: dbus: Failed to construct signal
Oct 01 20:18:45 host lightdm[1498]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Oct 01 20:18:45 host lightdm[1498]: PAM adding faulty module: pam_kwallet.so
Oct 01 20:18:45 host lightdm[1498]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Oct 01 20:18:45 host lightdm[1498]: PAM adding faulty module: pam_kwallet5.so
Oct 01 20:18:55 host pulseaudio[1858]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
Oct 01 20:18:55 host pulseaudio[2063]: [pulseaudio] pid.c: Daemon already running.
Беспокоят строки

Код: Выделить всё

failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
nvidia-persistenced.service: Failed at step EXEC spawning /usr/bin/nvidia-persistenced: No such file or directory
Oct 01 20:18:41 host systemd[1]: Failed to start NVIDIA Persistence Daemon.

Аватара пользователя

Автор темы
FliXis
Сообщения: 319
Зарегистрирован: 31 авг 2016, 11:01
Решено: 8
Благодарил (а): 75 раз
Поблагодарили: 21 раз

Черный экран при загрузке

Сообщение FliXis » 01 окт 2017, 17:32

Сделал sudo apt install --reinstall nvidia-375

Код: Выделить всё

                                      
flixis@host ~ $ journalctl -b -p err
-- Logs begin at Sun 2017-10-01 20:31:05 MSK, end at Sun 2017-10-01 20:31:32 MSK
Oct 01 20:31:05 host kernel: usb 3-5: string descriptor 0 read error: -22
Oct 01 20:31:06 host systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx2
Oct 01 20:31:06 host systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx2
Oct 01 20:31:06 host systemd[1]: dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserv
Oct 01 20:31:06 host systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx2
Oct 01 20:31:09 host bluetoothd[1194]: Failed to obtain handles for "Service Cha
Oct 01 20:31:09 host bluetoothd[1194]: Not enough free handles to register servi
Oct 01 20:31:09 host bluetoothd[1194]: Error adding Link Loss service
Oct 01 20:31:09 host bluetoothd[1194]: Not enough free handles to register servi
Oct 01 20:31:09 host bluetoothd[1194]: Not enough free handles to register servi
Oct 01 20:31:09 host bluetoothd[1194]: Not enough free handles to register servi
Oct 01 20:31:09 host bluetoothd[1194]: Current Time Service could not be registe
Oct 01 20:31:09 host bluetoothd[1194]: gatt-time-server: Input/output error (5)
Oct 01 20:31:09 host bluetoothd[1194]: Not enough free handles to register servi
Oct 01 20:31:09 host bluetoothd[1194]: Not enough free handles to register servi
Oct 01 20:31:09 host bluetoothd[1194]: Sap driver initialization failed.
Oct 01 20:31:09 host bluetoothd[1194]: sap-server: Operation not permitted (1)
Oct 01 20:31:09 host ntpdate[1348]: name server cannot be used: Temporary failur
Oct 01 20:31:09 host NetworkManager[1189]: nm_device_get_device_type: assertion 
Oct 01 20:31:09 host wpa_supplicant[1417]: dbus: wpa_dbus_get_object_properties:
Oct 01 20:31:09 host wpa_supplicant[1417]: dbus: Failed to construct signal
Oct 01 20:31:11 host lightdm[1479]: PAM unable to dlopen(pam_kwallet.so): /lib/s
lines 1-23...skipping...
-- Logs begin at Sun 2017-10-01 20:31:05 MSK, end at Sun 2017-10-01 20:31:32 MSK. --
Oct 01 20:31:05 host kernel: usb 3-5: string descriptor 0 read error: -22
Oct 01 20:31:06 host systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000
Oct 01 20:31:06 host systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000
Oct 01 20:31:06 host systemd[1]: dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device appeared twice with different sysfs paths /sys/devices
Oct 01 20:31:06 host systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000
Oct 01 20:31:09 host bluetoothd[1194]: Failed to obtain handles for "Service Changed" characteristic
Oct 01 20:31:09 host bluetoothd[1194]: Not enough free handles to register service
Oct 01 20:31:09 host bluetoothd[1194]: Error adding Link Loss service
Oct 01 20:31:09 host bluetoothd[1194]: Not enough free handles to register service
Oct 01 20:31:09 host bluetoothd[1194]: Not enough free handles to register service
Oct 01 20:31:09 host bluetoothd[1194]: Not enough free handles to register service
Oct 01 20:31:09 host bluetoothd[1194]: Current Time Service could not be registered
Oct 01 20:31:09 host bluetoothd[1194]: gatt-time-server: Input/output error (5)
Oct 01 20:31:09 host bluetoothd[1194]: Not enough free handles to register service
Oct 01 20:31:09 host bluetoothd[1194]: Not enough free handles to register service
Oct 01 20:31:09 host bluetoothd[1194]: Sap driver initialization failed.
Oct 01 20:31:09 host bluetoothd[1194]: sap-server: Operation not permitted (1)
Oct 01 20:31:09 host ntpdate[1348]: name server cannot be used: Temporary failure in name resolution (-3)
Oct 01 20:31:09 host NetworkManager[1189]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
Oct 01 20:31:09 host wpa_supplicant[1417]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
Oct 01 20:31:09 host wpa_supplicant[1417]: dbus: Failed to construct signal
Oct 01 20:31:11 host lightdm[1479]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Oct 01 20:31:11 host lightdm[1479]: PAM adding faulty module: pam_kwallet.so
Oct 01 20:31:11 host lightdm[1479]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Oct 01 20:31:11 host lightdm[1479]: PAM adding faulty module: pam_kwallet5.so
Oct 01 20:31:18 host pulseaudio[1762]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
Oct 01 20:31:18 host pulseaudio[1965]: [pulseaudio] pid.c: Daemon already running.
Строки про nvidia вроде пропали. Буду наблюдать.

Аватара пользователя

Автор темы
FliXis
Сообщения: 319
Зарегистрирован: 31 авг 2016, 11:01
Решено: 8
Благодарил (а): 75 раз
Поблагодарили: 21 раз

Черный экран при загрузке

Сообщение FliXis » 06 окт 2017, 19:27

Теперь все вроде бы нормально. Как я прочитал - если делать purge для nvidia драйвера, то после его установки не создается что-то там и потому требуется sudo apt install --reinstall nvidia-375. Сейчас перед стартом системы появляется на пару секунд заставка nvidia на весь экран, раньше такого не было точно. Но вот как оно до этого работало, фик его знает, видимо, просто везло.
Но я таки остался на 4.8 ядре.

Аватара пользователя

Unborn
Сообщения: 1778
Зарегистрирован: 03 сен 2016, 10:36
Решено: 24
Благодарил (а): 4 раза
Поблагодарили: 253 раза

Черный экран при загрузке

Сообщение Unborn » 07 окт 2017, 05:19

FliXis, издержки всех твоих экспериментов. В Убунту - Минт фича - если собираешься использовать блоб, то нужно установить ОС, драйвер, только потом все обновления. И не экспериментировать руками с ядрами и графическим стеком.
В чём ты сам убедился.


DJOKER93
Сообщения: 11
Зарегистрирован: 09 янв 2018, 11:22
Благодарил (а): 4 раза

Черный экран при загрузке

Сообщение DJOKER93 » 15 янв 2018, 16:05

помогите при загрузке чёрный экран

Код: Выделить всё

System:    Host: alex-HP-Pavilion-g6-Notebook-PC Kernel: 4.13.0-26-generic x86_64 (64 bit gcc: 5.4.0)
           Desktop: Cinnamon 3.6.7 (Gtk 3.18.9-1ubuntu3.3) dm: lightdm Distro: Linux Mint 18.3 Sylvia
Machine:   System: Hewlett-Packard (portable) product: HP Pavilion g6 Notebook PC v: 0691130000204610000610100
           Mobo: Hewlett-Packard model: 3566 v: 21.39 Bios: Insyde v: F.46 date: 02/22/2012
           Chassis: type: 10
CPU:       Dual core AMD A4-3305M APU with Radeon HD Graphics (-MCP-) cache: 1024 KB
           flags: (lm nx sse sse2 sse3 sse4a svm) bmips: 7586
           clock speeds: min/max: 800/1900 MHz 1: 1000 MHz 2: 1000 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Sumo [Radeon HD 6480G]
           bus-ID: 00:01.0 chip-ID: 1002:9649
           Display Server: X.Org 1.18.4 drivers: ati,radeon (unloaded: fbdev,vesa)
           Resolution: 1366x768@59.99hz
           GLX Renderer: AMD SUMO2 (DRM 2.50.0 / 4.13.0-26-generic, LLVM 5.0.0)
           GLX Version: 3.0 Mesa 17.2.4 Direct Rendering: Yes
Audio:     Card-1 Advanced Micro Devices [AMD] FCH Azalia Controller
           driver: snd_hda_intel bus-ID: 00:14.2 chip-ID: 1022:780d
           Card-2 Advanced Micro Devices [AMD/ATI] BeaverCreek HDMI Audio [Radeon HD 6500D and 6400G-6600G series]
           driver: snd_hda_intel bus-ID: 00:01.1 chip-ID: 1002:1714
           Sound: Advanced Linux Sound Architecture v: k4.13.0-26-generic
Network:   Card-1: Qualcomm Atheros AR9485 Wireless Network Adapter
           driver: ath9k bus-ID: 01:00.0 chip-ID: 168c:0032
           IF: wlo1 state: up mac: <filter>
           Card-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
           driver: r8169 v: 2.3LK-NAPI port: 2000 bus-ID: 02:00.0 chip-ID: 10ec:8136
           IF: eno1 state: down mac: <filter>
           Card-3: Atheros usb-ID: 006-002 chip-ID: 0cf3:311d
           IF: null-if-id state: N/A speed: N/A duplex: N/A mac: N/A
Drives:    HDD Total Size: 500.1GB (2.2% used)
           ID-1: /dev/sda model: ST500LM012_HN size: 500.1GB serial: S2SVJ9AC506478
Partition: ID-1: / size: 167G used: 6.8G (5%) fs: ext4 dev: /dev/sda5
           ID-2: swap-1 size: 3.73GB used: 0.00GB (0%) fs: swap dev: /dev/sda6
RAID:      System: supported: N/A
           No RAID devices: /proc/mdstat, md_mod kernel module present
           Unused Devices: none
Sensors:   System Temperatures: cpu: 77.0C mobo: N/A gpu: 76.0
           Fan Speeds (in rpm): cpu: N/A
Repos:     Active apt sources in file: /etc/apt/sources.list.d/official-package-repositories.list
           deb http: //mirror.yandex.ru/linuxmint-packages sylvia main upstream import backport
           deb http: //archive.ubuntu.com/ubuntu xenial main restricted universe multiverse
           deb http: //archive.ubuntu.com/ubuntu xenial-updates main restricted universe multiverse
           deb http: //archive.ubuntu.com/ubuntu xenial-backports main restricted universe multiverse
           deb http: //security.ubuntu.com/ubuntu/ xenial-security main restricted universe multiverse
           deb http: //archive.canonical.com/ubuntu/ xenial partner
Info:      Processes: 177 Uptime: 8:58 Memory: 2079.8/3419.1MB
           Init: systemd v: 229 runlevel: 5 default: 2 Gcc sys: 5.4.0
           Client: Unknown python2.7 client inxi: 2.2.35
Последний раз редактировалось пользователем 1 darkfenix; всего редактировалось раз: 15
Причина: BBcode

Вернуться в «Загрузка системы, бэкапы и восстановление»