14.04 cannot complete boot (black screen)

GT-Force · 04-18-2016, 07:13 PM

Hi,

I am attaching a screenshot of a part of my bootlog which I think contains info about the culprit(s).

https://photos.google.com/share/AF1Q...1udTNwYXpvbTZ3

Any suggestions to try are appreciated.

Thank you.
GT

widget · 04-18-2016, 09:00 PM

That is too crappy to read. Could be because I am a grumpy geezer and can't see as well as at one time.

I take it you logged in at the tty. What did it say when you tried;

Code:

startx

?

You might want to try logging in as root from the tty. Would give you some information. If it goes to a desktop with "startx" then the problem is with your user. Do not stay there long as root unless you disconnect from the internet. Do not open a web browser as cookies with root privileges are not a good idea.

Did you try booting "recovery mode"? This will actaully help a lot of times as there are more stringent checks done and some optional corrective measures run that are not run in the regular boot cycle.

I believe you will get, with no password, a # (root) prompt under the wonderful Ubuntu so called security model. Running;

Code:

dpkg --configure -a

at that prompt may help if something isn't configured as it should be from the install script.

You could also try;

Code:

apt-get -f install

which will attempt to fix any broken packages.

It would be useful to know under what circumstances this took place. Had you just done a package update/upgrade cycle? Had you just removed something? Added something? Used some tool with "tweak" in its name? Run any system cleaning application? Had a major crash of the system? Had the system shutdown due to power failure (can be common in rural Montana)?

Be nice to know for sure what DE you are using although assuming Unity is probably safe. Some other info on your hardware would be nice too.

Emerson · 04-18-2016, 09:12 PM

There is a possibility the boot actually finishes and loading X fails due to driver error. Does switching over to the console work?

GT-Force · 04-19-2016, 01:13 PM

Thanks for the replies.

startx does not work.

tty works. Well, kind of. I also do not have networking, so I cannot do any of the apt-get, if it needs to connect to the repositories.

So, I don't know what must have gone wrong to corrupt both the GUI and the networking.

I dumped the boot log into a text file, and once I figure out how to pull it out of that machine, I will post it here as text.

I tried resinstalling the nVidia driver, but that did not fix anything.

GT-Force · 04-19-2016, 01:23 PM

Code:

* Starting Mount filesystems on boot[314G[ OK ]
 * Starting Populate /dev filesystem[314G[ OK ]
 * Starting Populate and link to /run filesystem[314G[ OK ]
 * Stopping Populate /dev filesystem[314G[ OK ]
 * Stopping Populate and link to /run filesystem[314G[ OK ]
 * Stopping Track if upstart is running in a container[314G[ OK ]
 * Starting Initialize or finalize resolvconf[314G[ OK ]
 * Starting set console keymap[314G[ OK ]
 * Starting Signal sysvinit that virtual filesystems are mounted[314G[ OK ]
 * Starting Signal sysvinit that virtual filesystems are mounted[314G[ OK ]
 * Starting Bridge udev events into upstart[314G[ OK ]
 * Starting Signal sysvinit that remote filesystems are mounted[314G[ OK ]
 * Stopping set console keymap[314G[ OK ]
 * Starting device node and kernel event manager[314G[ OK ]
 * Starting load modules from /etc/modules[314G[ OK ]
 * Starting load modules from /etc/modules[314G[ OK ]
 * Starting cold plug devices[314G[ OK ]
 * Starting log initial device creation[314G[ OK ]
 * Stopping load modules from /etc/modules[314G[ OK ]
 * Stopping load modules from /etc/modules[314G[ OK ]
 * Starting Signal sysvinit that the rootfs is mounted[314G[ OK ]
 * Starting Clean /tmp directory[314G[ OK ]
 * Starting Uncomplicated firewall[314G[ OK ]
 * Starting configure network device security[314G[ OK ]
 * Starting configure network device[314G[ OK ]
 * Stopping Clean /tmp directory[314G[ OK ]
 * Stopping Read required files in advance[314G[ OK ]
 * Starting configure network device security[314G[ OK ]
 * Starting configure network device[314G[ OK ]
 * Starting configure network device security[314G[ OK ]
 * Starting configure network device[314G[ OK ]
 * Stopping Read required files in advance (for other mountpoints)[314G[ OK ]
 * Starting configure network device security[314G[ OK ]
 * Starting configure network device[314G[ OK ]
 * Starting configure network device security[314G[ OK ]
 * Starting Mount network filesystems[314G[ OK ]
 * Stopping Mount network filesystems[314G[ OK ]
 * Stopping Read required files in advance (for other mountpoints)[314G[ OK ]
 * Starting configure network device[314G[ OK ]
 * Starting Bridge socket events into upstart[314G[ OK ]
 * Stopping Read required files in advance (for other mountpoints)[314G[ OK ]
 * Starting Signal sysvinit that local filesystems are mounted[314G[ OK ]
 * Starting restore software rfkill state[314G[ OK ]
 * Stopping restore software rfkill state[314G[ OK ]
 * Starting SMB/CIFS File Server[314G[ OK ]
 * Starting Enabling additional executable binary formats[314G[ OK ]
 * Starting flush early job output to logs[314G[ OK ]
 * Stopping Failsafe Boot Delay[314G[ OK ]
 * Stopping Mount filesystems on boot[314G[ OK ]
 * Starting System V initialisation compatibility[314G[ OK ]
 * Starting D-Bus system message bus[314G[ OK ]
 * Stopping flush early job output to logs[314G[ OK ]
 * Starting modem connection manager[314G[ OK ]
 * Starting configure network device security[314G[ OK ]
 * Starting SMB/CIFS File and Active Directory Server[314G[ OK ]
 * Starting SystemD login management service[314G[ OK ]
 * Starting system logging daemon[314G[ OK ]
 * Starting SystemD login management service[314G[ OK ]
 * Starting modem connection manager[314G[ OK ]
 * Starting SystemD login management service[314G[ OK ]
 * Starting modem connection manager[314G[ OK ]
 * Starting mDNS/DNS-SD daemon[314G[ OK ]
 * Starting network connection manager[314G[ OK ]
Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
 * Starting SMB/CIFS File and Active Directory Server[314G[[31mfail[39;49m]
 * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[314G[ OK ]
 * Starting modem connection manager[314G[ OK ]
 * Stopping cold plug devices[314G[ OK ]
 * Starting SystemD login management service[314G[ OK ]
 * Stopping log initial device creation[314G[ OK ]
 * Starting modem connection manager[314G[ OK ]
 * Starting load fallback graphics devices[314G[ OK ]
 * Starting configure network device security[314G[ OK ]
 * Stopping load fallback graphics devices[314G[ OK ]
 * Starting save udev log and update rules[314G[ OK ]
 * Starting SystemD login management service[314G[ OK ]
 * Starting modem connection manager[314G[ OK ]
 * Starting network connection manager[314G[ OK ]
 * Stopping save udev log and update rules[314G[ OK ]
 * Stopping Reload cups, upon starting avahi-daemon to make sure remote queues are populated[314G[ OK ]
 * Starting set console font[314G[ OK ]
 * Stopping set console font[314G[ OK ]
 * Starting userspace bootsplash[314G[ OK ]
 * Starting modem connection manager[314G[ OK ]
 * Starting SystemD login management service[314G[ OK ]
 * Starting Send an event to indicate plymouth is up[314G[ OK ]
 * Starting configure virtual network devices[314G[ OK ]
 * Starting modem connection manager[314G[ OK ]
 * Starting mDNS/DNS-SD daemon[314G[ OK ]
 * Stopping userspace bootsplash[314G[ OK ]
 * Starting network connection manager[314G[ OK ]
 * Stopping Send an event to indicate plymouth is up[314G[ OK ]
 * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[314G[ OK ]
 * Starting SystemD login management service[314G[ OK ]
 * Starting modem connection manager[314G[ OK ]
 * Starting modem connection manager[314G[ OK ]
 * Starting SystemD login management service[314G[ OK ]
 * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[314G[[31mfail[39;49m]
 * Starting modem connection manager[314G[ OK ]
 * Starting network connection manager[314G[ OK ]
 * Starting modem connection manager[314G[[31mfail[39;49m]
 * Stopping modem connection manager[314G[ OK ]
 * Starting SystemD login management service[314G[ OK ]
 * Starting modem connection manager[314G[ OK ]
 * Starting mDNS/DNS-SD daemon[314G[ OK ]
 * Starting AppArmor profiles       [320G 
[314G[ OK ]
 * Starting modem connection manager[314G[ OK ]
 * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[314G[ OK ]
 * Starting network connection manager[314G[ OK ]
 * Starting SystemD login management service[314G[ OK ]
 * Starting modem connection manager[314G[ OK ]
 * Setting sensors limits       [320G 
[314G[ OK ]
 * Starting modem connection manager[314G[ OK ]
 * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[314G[[31mfail[39;49m]
 * Starting SystemD login management service[314G[ OK ]
 * Starting modem connection manager[314G[ OK ]
 * Starting SystemD login management service[314G[[31mfail[39;49m]
 * Setting up X socket directories...        * Starting modem connection manager[314G[ OK ]
 * Stopping SystemD login management service[314G[ OK ]
[320G 
[314G[ OK ]
 * Starting network connection manager[314G[ OK ]
 * Starting modem connection manager[314G[ OK ]
 * Starting mDNS/DNS-SD daemon[314G[ OK ]
 * Stopping System V initialisation compatibility[314G[ OK ]
Starting spacenavd daemon
 * speech-dispatcher disabled; edit /etc/default/speech-dispatcher
saned disabled; edit /etc/default/saned
 * Starting System V runlevel compatibility[314G[ OK ]
 * Starting OpenSSH server[314G[ OK ]
 * Starting save kernel messages[314G[ OK ]
 * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[314G[ OK ]
 * Starting modem connection manager[314G[ OK ]
 * Starting crash report submission daemon[314G[ OK ]
 * Starting anac(h)ronistic cron[314G[ OK ]
 * Starting regular background program processing daemon[314G[ OK ]
 * Starting deferred execution scheduler[314G[ OK ]
 * Stopping save kernel messages[314G[ OK ]
 * Restoring resolver state...       [320G 
[314G[ OK ]
/etc/rc2.d/S70maldet: line 10: /etc/init.d/functions: No such file or directory
error no default monitor mode defined, set $MONITOR_MODE in /etc/sysconfig/maldet or $default_monitor_mode in /usr/local/maldetect/conf.maldet
 * Starting network connection manager[314G[ OK ]
 * Starting CPU interrupts balancing daemon[314G[ OK ]
 * Stopping anac(h)ronistic cron[314G[ OK ]
 * Starting modem connection manager[314G[ OK ]
 * Starting modem connection manager[314G[ OK ]
 * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[314G[[31mfail[39;49m]
 * Starting modem connection manager[314G[ OK ]
 * Starting network connection manager[314G[ OK ]
 * Starting cups-browsed - Bonjour remote printer browsing daemon[314G[ OK ]
 * Starting modem connection manager[314G[[31mfail[39;49m]
 * Starting automatic crash report generation[314G[ OK ]
 * Stopping modem connection manager[314G[ OK ]
 * Stopping System V runlevel compatibility[314G[ OK ]
 * Starting ACPI daemon[314G[ OK ]
 * Stopping Restore Sound Card State[314G[ OK ]
 * Starting mDNS/DNS-SD daemon[314G[ OK ]
 * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[314G[ OK ]
 * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[314G[[31mfail[39;49m]
 * Starting mDNS/DNS-SD daemon[314G[ OK ]
 * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[314G[ OK ]
 * Starting bluetooth daemon[314G[[31mfail[39;49m]
 * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[314G[[31mfail[39;49m]
 * Starting mDNS/DNS-SD daemon[314G[ OK ]
 * Stopping bluetooth daemon[314G[ OK ]
 * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[314G[ OK ]
 * Starting CUPS printing spooler/server[314G[ OK ]
 * Starting Samba Auto-reload Integration[314G[ OK ]
 * Stopping Reload cups, upon starting avahi-daemon to make sure remote queues are populated[314G[ OK ]
 * Starting mDNS/DNS-SD daemon[314G[ OK ]
 * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated[314G[ OK ]
 * Starting modem connection manager[314G[ OK ]

GT-Force · 04-19-2016, 01:24 PM

Here's the part towrds the end of the log that contains the errors:

Code:

[   11.906101] init: plymouth-upstart-bridge main process (494) terminated with status 1
[   11.907539] init: plymouth-upstart-bridge main process ended, respawning
[   11.914214] init: plymouth-upstart-bridge main process (504) terminated with status 1
[   11.915402] init: plymouth-upstart-bridge main process ended, respawning
[   11.920267] init: plymouth-upstart-bridge main process (513) terminated with status 1
[   11.921478] init: plymouth-upstart-bridge main process ended, respawning
[   11.924700] init: plymouth-upstart-bridge main process (516) terminated with status 1
[   11.925894] init: plymouth-upstart-bridge main process ended, respawning
[   11.928755] init: plymouth-upstart-bridge main process (518) terminated with status 1
[   11.929939] init: plymouth-upstart-bridge main process ended, respawning
[   12.059127] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   12.059132] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[   12.059137] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
[   12.059143] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
[   12.093608] systemd-udevd[624]: starting version 204
[   12.114058] lp: driver loaded but no devices found
[   12.122409] ppdev: user-space parallel port driver
[   12.140777] wmi: Mapper loaded
[   12.143275] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[   12.190148] EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro
[   12.225509] mei_me 0000:00:16.0: irq 172 for MSI/MSI-X
[   12.225722] [drm] Initialized drm 1.1.0 20060810
[   12.233892] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
[   12.233900] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   12.233903] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
[   12.233907] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   12.234030] lpc_ich: Resource conflict(s) found affecting gpio_ich
[   12.263727] snd_hda_intel 0000:00:1b.0: irq 173 for MSI/MSI-X
[   12.268205] systemd-udevd[649]: renamed network interface eth3 to rename5
[   12.279308] SKU: Nid=0x1d sku_cfg=0x40400001
[   12.279310] SKU: port_connectivity=0x1
[   12.279311] SKU: enable_pcbeep=0x0
[   12.279313] SKU: check_sum=0x00000000
[   12.279314] SKU: customization=0x00000000
[   12.279315] SKU: external_amp=0x0
[   12.279316] SKU: platform_type=0x0
[   12.279317] SKU: swap=0x0
[   12.279318] SKU: override=0x1
[   12.279576] autoconfig: line_outs=1 (0x1b/0x0/0x0/0x0/0x0) type:line
[   12.279579]    speaker_outs=1 (0x14/0x0/0x0/0x0/0x0)
[   12.279580]    hp_outs=1 (0x15/0x0/0x0/0x0/0x0)
[   12.279582]    mono: mono_out=0x0
[   12.279583]    inputs:
[   12.279585]      Front Mic=0x1a
[   12.279587]      Rear Mic=0x18
[   12.279589] realtek: No valid SSID, checking pincfg 0x40400001 for NID 0x1d
[   12.279590] realtek: Enabling init ASM_ID=0x0001 CODEC_ID=10ec0280
[   12.284363] input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
[   12.284565] input: HDA Intel PCH Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
[   12.284673] input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
[   12.284892] input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
[   12.287456] hda_intel: Disabling MSI
[   12.287501] hda-intel 0000:03:00.1: Handle VGA-switcheroo audio client
[   12.287545] hda-intel 0000:03:00.1: Disabling 64bit DMA
[   12.297692] hda-intel 0000:03:00.1: Enable delay in RIRB handling
[   12.301041] type=1400 audit(1461080152.446:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=849 comm="apparmor_parser"
[   12.301048] type=1400 audit(1461080152.446:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=849 comm="apparmor_parser"
[   12.301051] type=1400 audit(1461080152.446:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=849 comm="apparmor_parser"
[   12.301406] type=1400 audit(1461080152.446:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=849 comm="apparmor_parser"
[   12.301410] type=1400 audit(1461080152.446:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=849 comm="apparmor_parser"
[   12.301574] type=1400 audit(1461080152.446:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=849 comm="apparmor_parser"
[   12.308201] systemd-udevd[687]: renamed network interface eth1 to eth3
[   12.332216] systemd-udevd[648]: renamed network interface eth2 to eth1
[   12.361064] nvidia: module license 'NVIDIA' taints kernel.
[   12.361068] Disabling lock debugging due to kernel taint
[   12.364963] nvidia: module verification failed: signature and/or  required key missing - tainting kernel
[   12.372200] systemd-udevd[649]: renamed network interface rename5 to eth2
[   12.417738] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[   12.419973] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2)
[   12.514544] EXT4-fs (sdd): mounted filesystem with ordered data mode. Opts: (null)
[   12.655429] EXT4-fs (sdc): mounted filesystem with ordered data mode. Opts: (null)
[   12.709569] init: failsafe main process (1116) killed by TERM signal
[   12.710327] init: dbus main process (1130) terminated with status 1
[   12.710336] init: dbus main process ended, respawning
[   12.720659] init: Unable to connect to the D-Bus system bus: Failed to connect to socket /usr/local/var/run/dbus/system_bus_socket: Connection refused
[   12.744211] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:02.0/0000:03:00.1/sound/card1/input15
[   12.744321] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:02.0/0000:03:00.1/sound/card1/input14
[   12.744378] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:02.0/0000:03:00.1/sound/card1/input13
[   12.744821] vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=none:owns=none
[   12.745027] nvidia-nvlink: Nvlink Core is being initialized, major device number 248
[   12.745152] [drm] Initialized nvidia-drm 0.0.0 20150116 for 0000:03:00.0 on minor 0
[   12.745165] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  361.28  Wed Feb  3 15:48:04 PST 2016
[   12.748400] init: bluetooth main process (1169) terminated with status 1
[   12.748411] init: bluetooth main process ended, respawning
[   12.759776] init: systemd-logind main process (1187) terminated with status 1
[   12.759783] init: systemd-logind main process ended, respawning
[   12.762025] Bluetooth: Core ver 2.17
[   12.762041] NET: Registered protocol family 31
[   12.762043] Bluetooth: HCI device and connection manager initialized
[   12.762052] Bluetooth: HCI socket layer initialized
[   12.762054] Bluetooth: L2CAP socket layer initialized
[   12.762059] Bluetooth: SCO socket layer initialized
[   12.765579] Bluetooth: RFCOMM TTY layer initialized
[   12.765586] Bluetooth: RFCOMM socket layer initialized
[   12.765589] Bluetooth: RFCOMM ver 1.11
[   12.768417] init: modemmanager main process ended, respawning
[   12.779959] init: systemd-logind main process (1211) terminated with status 1
[   12.779973] init: systemd-logind main process ended, respawning
[   12.788769] init: modemmanager main process ended, respawning
[   12.791030] type=1400 audit(1461080152.934:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=1242 comm="apparmor_parser"
[   12.791035] type=1400 audit(1461080152.934:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cupsd" pid=1242 comm="apparmor_parser"
[   12.791384] type=1400 audit(1461080152.934:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=1242 comm="apparmor_parser"
[   12.795465] init: samba-ad-dc main process (1176) terminated with status 1
[   12.807997] init: network-manager main process (1223) killed by ABRT signal
[   12.808032] init: network-manager main process ended, respawning
[   12.808193] init: modemmanager main process ended, respawning
[   12.808278] init: avahi-daemon main process (1246) terminated with status 255
[   12.808284] init: avahi-daemon main process ended, respawning
[   12.809964] init: systemd-logind main process (1264) terminated with status 1
[   12.809972] init: systemd-logind main process ended, respawning
[   12.810151] init: bluetooth main process (1270) terminated with status 1
[   12.810158] init: bluetooth main process ended, respawning
[   12.812677] type=1400 audit(1461080152.958:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1297 comm="apparmor_parser"
[   12.824606] init: modemmanager main process ended, respawning
[   12.830264] init: systemd-logind main process (1324) terminated with status 1
[   12.830273] init: systemd-logind main process ended, respawning
[   12.837188] init: modemmanager main process ended, respawning
[   12.841631] init: cups main process (1258) killed by ABRT signal
[   12.841638] init: cups main process ended, respawning
[   12.844435] init: bluetooth main process (1343) terminated with status 1
[   12.844443] init: bluetooth main process ended, respawning
[   12.850159] init: network-manager main process (1329) killed by ABRT signal
[   12.850167] init: network-manager main process ended, respawning
[   12.850307] init: modemmanager main process ended, respawning
[   12.851416] init: systemd-logind main process (1346) terminated with status 1
[   12.851424] init: systemd-logind main process ended, respawning
[   12.863406] init: modemmanager main process ended, respawning
[   12.877229] init: systemd-logind main process (1370) terminated with status 1
[   12.877238] init: systemd-logind main process ended, respawning
[   12.877339] init: modemmanager main process ended, respawning
[   12.877432] init: avahi-daemon main process (1372) terminated with status 255
[   12.877440] init: avahi-daemon main process ended, respawning
[   12.889337] init: network-manager main process (1375) killed by ABRT signal
[   12.889345] init: network-manager main process ended, respawning
[   12.891807] init: modemmanager main process ended, respawning
[   12.891968] init: bluetooth main process (1400) terminated with status 1
[   12.891976] init: bluetooth main process ended, respawning
[   12.901340] init: systemd-logind main process (1407) terminated with status 1
[   12.901348] init: systemd-logind main process ended, respawning
[   12.901443] init: modemmanager main process ended, respawning
[   12.907557] init: avahi-cups-reload main process (1385) terminated with status 1
[   12.914779] init: modemmanager respawning too fast, stopped
[   12.924741] init: network-manager main process (1419) killed by ABRT signal
[   12.924748] init: network-manager main process ended, respawning
[   12.924901] init: systemd-logind main process (1434) terminated with status 1
[   12.924907] init: systemd-logind main process ended, respawning
[   12.930711] init: bluetooth main process (1441) terminated with status 1
[   12.930719] init: bluetooth main process ended, respawning
[   12.934309] init: modemmanager main process ended, respawning
[   12.942317] init: avahi-daemon main process (1452) terminated with status 255
[   12.942324] init: avahi-daemon main process ended, respawning
[   12.943580] init: systemd-logind main process (1457) terminated with status 1
[   12.943589] init: systemd-logind main process ended, respawning
[   12.949654] init: modemmanager main process ended, respawning
[   12.961224] init: modemmanager main process ended, respawning
[   12.962947] init: systemd-logind main process (1489) terminated with status 1
[   12.962954] init: systemd-logind main process ended, respawning
[   12.963129] init: bluetooth main process (1491) terminated with status 1
[   12.963136] init: bluetooth main process ended, respawning
[   12.972079] init: network-manager main process (1473) killed by ABRT signal
[   12.972087] init: network-manager main process ended, respawning
[   12.972210] init: modemmanager main process ended, respawning
[   12.972308] init: avahi-cups-reload main process (1462) terminated with status 1
[   12.987082] init: systemd-logind main process (1511) terminated with status 1
[   12.987091] init: systemd-logind respawning too fast, stopped
[   12.987325] init: modemmanager main process ended, respawning
[   12.994027] init: bluetooth main process (1523) terminated with status 1
[   12.994035] init: bluetooth main process ended, respawning
[   12.998107] init: modemmanager main process ended, respawning
[   13.005596] init: modemmanager main process ended, respawning
[   13.012953] init: network-manager main process (1526) killed by ABRT signal
[   13.012961] init: network-manager main process ended, respawning
[   13.013178] init: avahi-daemon main process (1540) terminated with status 255
[   13.013188] init: avahi-daemon main process ended, respawning
[   13.021599] init: modemmanager main process ended, respawning
[   13.026829] init: bluetooth main process (1588) terminated with status 1
[   13.026836] init: bluetooth main process ended, respawning
[   13.028971] init: modemmanager main process ended, respawning
[   13.038868] init: modemmanager main process ended, respawning
[   13.039137] init: avahi-cups-reload main process (1556) terminated with status 1
[   13.046346] init: network-manager main process (1600) killed by ABRT signal
[   13.046354] init: network-manager main process ended, respawning
[   13.051937] init: modemmanager respawning too fast, stopped
[   13.056074] init: bluetooth main process (1658) terminated with status 1
[   13.056082] init: bluetooth main process ended, respawning
[   13.106929] init: avahi-daemon main process (1663) terminated with status 255
[   13.106938] init: avahi-daemon main process ended, respawning
[   13.109964] init: nvidia-prime main process (1696) terminated with status 127
[   13.137861] init: network-manager main process (1666) killed by ABRT signal
[   13.137869] init: network-manager main process ended, respawning
[   13.177576] init: modemmanager main process ended, respawning
[   13.185317] init: bluetooth main process (1922) terminated with status 1
[   13.185324] init: bluetooth main process ended, respawning
[   13.188135] init: modemmanager main process ended, respawning
[   13.188362] init: avahi-cups-reload main process (1692) terminated with status 1
[   13.206886] init: modemmanager main process ended, respawning
[   13.226052] init: network-manager main process (1937) killed by ABRT signal
[   13.226061] init: network-manager main process ended, respawning
[   13.246758] init: modemmanager main process ended, respawning
[   13.257151] init: bluetooth main process (2000) terminated with status 1
[   13.257170] init: bluetooth respawning too fast, stopped
[   13.261501] init: modemmanager main process ended, respawning
[   13.272906] init: avahi-daemon main process (2007) terminated with status 255
[   13.272922] init: avahi-daemon main process ended, respawning
[   13.280129] init: modemmanager main process ended, respawning
[   13.287566] init: modemmanager main process ended, respawning
[   13.297467] init: modemmanager main process ended, respawning
[   13.297649] init: avahi-cups-reload main process (2017) terminated with status 1
[   13.307398] init: modemmanager main process ended, respawning
[   13.314794] init: modemmanager main process ended, respawning
[   13.317581] init: plymouth-upstart-bridge main process ended, respawning
[   13.317858] init: lightdm main process (2056) terminated with status 1
[   13.326831] init: plymouth-ready (startup) main process (492) terminated with status 1
[   13.327033] init: modemmanager respawning too fast, stopped
[   13.336171] init: avahi-daemon main process (2090) terminated with status 255
[   13.336179] init: avahi-daemon main process ended, respawning
[   13.340322] init: avahi-cups-reload main process (2098) terminated with status 1
[   13.350699] nvidia 0000:03:00.0: irq 174 for MSI/MSI-X
[   13.359232] init: avahi-daemon main process (2115) terminated with status 255
[   13.359239] init: avahi-daemon main process ended, respawning
[   13.374521] init: avahi-daemon main process (2137) terminated with status 255
[   13.374537] init: avahi-daemon main process ended, respawning
[   13.388442] init: network-manager main process (2009) killed by ABRT signal
[   13.388448] init: network-manager main process ended, respawning
[   13.388608] init: avahi-daemon main process (2150) terminated with status 255
[   13.388617] init: avahi-daemon main process ended, respawning
[   13.397190] init: modemmanager main process ended, respawning
[   13.403269] init: modemmanager main process ended, respawning
[   13.411806] init: modemmanager main process ended, respawning
[   13.418853] init: modemmanager main process ended, respawning
[   13.427015] init: avahi-daemon main process (2188) terminated with status 255
[   13.427021] init: avahi-daemon respawning too fast, stopped
[   13.427214] init: modemmanager main process ended, respawning
[   13.434798] init: modemmanager main process ended, respawning
[   13.440546] init: modemmanager main process ended, respawning
[   13.446629] init: modemmanager main process ended, respawning
[   13.448144] init: cups main process (2110) killed by ABRT signal
[   13.448151] init: cups main process ended, respawning
[   13.452158] init: modemmanager main process ended, respawning
[   13.457287] init: modemmanager main process ended, respawning
[   13.462064] init: modemmanager respawning too fast, stopped
[   13.514102] init: network-manager main process (2171) killed by ABRT signal
[   13.514109] init: network-manager respawning too fast, stopped
[   14.146312] init: plymouth-splash main process (2278) terminated with status 1
[   14.194239] NVRM: Your system is not currently configured to drive a VGA console
[   14.194243] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
[   14.194244] NVRM: requires the use of a text-mode VGA console. Use of other console
[   14.194245] NVRM: drivers including, but not limited to, vesafb, may result in
[   14.194246] NVRM: corruption and stability problems, and is not supported.
[   14.203913] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  361.28  Wed Feb  3 15:15:17 PST 2016
[   14.204457] nvidia-modeset: Allocated GPU:0 (GPU-738c958d-df75-12f5-30e8-d6cebcb39b91) @ PCI:0000:03:00.0
[   34.324844] init: failsafe-x main process (2313) terminated with status 1

Emerson · 04-19-2016, 01:25 PM

You can use SystemRescueCD (on USB or CD), it has wgetpaste utility which will load up anything you want and give you a URL to it.

Emerson · 04-19-2016, 01:29 PM

Looking at the log you've provided I'd say there is a framebuffer driver loaded that grabs your nvidia card so nvidia driver cannot load. Just a guess though. Did you attempt nVidia proprietary driver install?

GT-Force · 04-19-2016, 01:31 PM

Quote:

Originally Posted by Emerson

Looking at the log you've provided I'd say there is a framebuffer driver loaded that grabs your nvidia card so nvidia driver cannot load. Just a guess though. Did you attempt nVidia proprietary driver install?

I was already using those, and I tried reinstalling them to no avail.

Do you have any ideas about how I can fix this "framebuffer driver loaded that grabs your nvidia card so nvidia driver cannot load." issue?

Thanks.

Emerson · 04-19-2016, 01:36 PM

Not really. I'm spoiled by Gentoo where nothing happens in the system without administrator knowing it. Ubuntu on the contrary hides changes it helpfully performs for operator. I'd try reinstalling nvidia drivers from command line, hopefully it will blacklist conflicting framebuffer modules. Also make sure your card actually is supported by the driver version you are installing.

GT-Force · 04-19-2016, 01:38 PM

Once again, I was already using the latest proprietary nVidia driver, which was working fine; and I tried reinstalling (at the tty) but that did not change anything.

Emerson · 04-19-2016, 01:48 PM

Posting full dmesg in a pastebin using wgetpaste as I recommended above would help further.

widget · 04-19-2016, 02:12 PM

Did you try booting to recovery mode.

There are a number of different things that happen there than with the normal boot process. This will, possibly give more info.

The dmesg output would be a great thing indeed.

GT-Force · 04-19-2016, 02:27 PM

Here it is:

https://drive.google.com/file/d/0B1b...w?usp=drivesdk

Emerson · 04-19-2016, 03:20 PM

OK, it shows vesafb loaded. It may interfere with newest nvidia blob which comes with its own KMS driver. Your computer probably autoloads X upon boot? The failure to load X will be in Xorg log, can you post the full log, please?