45 minutes boot

Lately my boot украл is becoming very slow. I suspect that it - something to do with the nvidia драйверы. It is stuck in в loop for 45 minutes trying to detect GPU:

here is the tail of the boot log:

===========================================================
(2 of 2) A start job is running for Detect the available GPUs and deal with any system changes.
(2 of 2) A start job is running for Detect the available GPUs and deal with any system changes
(1 of 2) A start job is running for Wait for Plymouth Boot Screen to Quit (45min 13s / no limit
(1 of 2) A start job is running for Wait for Plymouth Boot Screen to Quit (45min 16s / no limit
[  OK  ] Started Detect the available GPUs and deal with any system changes.
Starting Light Display Manager...
======================================================================

And here is the gpu менеджер log:

sudo cat /var/log/gpu-manager.log
==============================================================
log_file: /var/log/gpu-manager.log 
last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot  
new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot  
grep dmesg status 0  
dmesg status 0 == 0? Yes  
grep dmesg status 256  
dmesg status 256 == 0? No  
Is nvidia loaded? no  
Was nvidia unloaded? yes  
Is nvidia blacklisted? no  
Is fglrx loaded? no  
Was fglrx unloaded? no  
Is fglrx blacklisted? no  
Is intel loaded? yes  
Is radeon loaded? no  
Is radeon blacklisted? no  
Is nouveau loaded? yes  
Is nouveau blacklisted? no  
Is fglrx kernel module available? no  
Is nvidia kernel module available? no  
Vendor/Device Id: 8086:416  
BusID "PCI:0@0:2:0"  
Is boot vga? yes  
Vendor/Device Id: 10de:1292  
BusID "PCI:1@0:0:0"  
Is boot vga? no  
Skipping "/dev/dri/card1", driven by "nouveau"  
Skipping "/dev/dri/card0", driven by "i915"  
Found "/dev/dri/card1", driven by "nouveau"  
Number of connected outputs for /dev/dri/card1: 0  
Skipping "/dev/dri/card1", driven by "nouveau"  
Found "/dev/dri/card0", driven by "i915"  
output 0:  
    eDP connector  
Number of connected outputs for /dev/dri/card0: 1  
Does it require offloading? yes  
last cards number = 2  
Has amd? no  
Has intel? yes  
Has nvidia? yes  
How many cards? 2  
Has the system changed? No  
main_arch_path x86_64-linux-gnu, other_arch_path i386-linux-gnu  
Current alternative: /usr/lib/x86_64-linux-gnu/mesa/ld.so.conf  
Current core alternative: (null)  
Is nvidia enabled? no  
Is fglrx enabled? no  
Is mesa enabled? yes  
Is pxpress enabled? no  
Is prime enabled? no  
Is nvidia available? no  
Is fglrx available? no  
Is fglrx-core available? no  
Is mesa available? yes  
Is pxpress available? no  
Is prime available? no  
Intel IGP detected  
Desktop system detected  
or laptop with open drivers  
Discrete NVIDIA card detected  
can't access /etc/X11/xorg.conf  
Driver not enabled or not in use  
Nothing to do  

=====================

not sure if relevant, lspci шоу nvidia 3D controller (and other things):

3D controller: NVIDIA Corporation GK208M [GeForce GT 740M] (rev a1)

again, not sure if relevent. systemctl статус gpu-manager.service шоу:

gpu-manager.service - Detect the available GPUs and deal with any system changes.
Loaded: loaded (/lib/systemd/system/gpu-manager.service; enabled; vendor preset: enabled)
Active: inactive (dead) since ד' 2015-11-11 00:07:08 IST; 13h ago
Main PID: 840 (code=exited, status=0/SUCCESS)

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

Update: I rebooted and again it took 45 minutes. What does this мочатся? I understand that some process is looking for the GPU and it cannot start the desktop until it finds it or gives up, and it seems like it gives up after 45 minutes. Is there some нравится where в time interval for "give up" is defined?

Please help я understand whats going on and how to fix it.

3
задан 11 November 2015 в 23:03

3 ответа

Проблема решена сама собой. Я не знаю почему или как. Последнее действие, которое я сделал перед последней перезагрузкой, было rm / var / log / syslog; rm /var/log/ufw.log и rm /var/log/auth.*, потому что у каждого по 100 ГБ. Если кто-нибудь может объяснить, что произошло, тогда, пожалуйста, оставьте комментарий.

2
ответ дан 1 December 2019 в 17:00

(Обновлено). После загрузки дистрибутива.

  1. . Загрузите последние версии драйверов с

    wget http://us.download.nvidia.com/XFree86/Linux-x86_64/352.55/NVIDIA-Linux-x86_64-352.55.run
    
  2. . 111]

    и нажмите OK на всем.

0
ответ дан 1 December 2019 в 17:00

Я нашел, что это происходило после включения проектора HDMI. Я использовал драйвер Intel. Презентация пошла прекрасная. Предыдущее включение не вызвало проблем. Хотя на этот раз на следующей начальной загрузке, менеджер окон не запустился бы. Найденный /var/log/gpu-manager.log был разбит в наличие необычного ACL и метки времени.

p--xrwsrwx  1 mail       1711       0 Jan 26  1971 gpu-manager.log

Удаленный файл журнала нулевых байтов и менеджер окон, запущенный хорошо.

0
ответ дан 1 December 2019 в 17:00

Другие вопросы по тегам:

Похожие вопросы: