14.04 cannot complete boot (black screen)

GT-Force · 04-25-2016, 02:11 PM

Quote:

Originally Posted by Emerson

You can get online very easy, just use ifconfig and route command line tools.
This will tell you what is the name of interface (eth0 in my case):

Code:

ifconfig -a
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.2.4  netmask 255.255.255.0  broadcast 192.168.2.255
        inet6 fe80::d250:99ff:fe87:d1a4  prefixlen 64  scopeid 0x20<link>
        ether d0:50:99:87:d1:a4  txqueuelen 1000  (Ethernet)
        RX packets 15999171  bytes 21905308763 (20.4 GiB)
        RX errors 0  dropped 2199  overruns 0  frame 0
        TX packets 3157410  bytes 459486765 (438.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  memory 0xdf100000-df120000

Then give it an IP address, broadcast and netmask - valid ones for your LAN:

Code:

ifconfig eth0 ${IP_ADDR} broadcast ${BROADCAST} netmask ${NETMASK} up

Now set route and you are connected - again, use valid gateway for your LAN:

Code:

route add default gw ${GATEWAY}

See, easy! Will take minute or two at most.

This did not work.

GT-Force · 04-25-2016, 02:24 PM

Quote:

Originally Posted by widget

Yep. But if we can simply run "dpkg -reconfigure dbus dbus-x11" and have a running system we won't have to do that

This does not work, as it seems like "reconfigure" is not a dpkg option. I also tried just reconfigure or --reconfigure, not working.

Then, I've found out that it is "dpkg-reconfigure dbus", which gives me the error:

Code:

Failed to open connection to "system" message bus: Failed to connect to socket /usr/local/var/run/dbus/system_bus_socket: Connection refused

dpkg-reconfigure dbus-x11

does not spit out any output.

Emerson · 04-25-2016, 03:05 PM

Quote:

Originally Posted by GT-Force

This did not work.

What did not work? Works for me every time.

Edit: You did define the variables or use numeric addresses, correct?

GT-Force · 04-25-2016, 03:28 PM

Quote:

Originally Posted by Emerson

What did not work? Works for me every time.

Edit: You did define the variables or use numeric addresses, correct?

Yes, I did put in the actual numbers. It says nothing (positive or negative), when I look at whether they were implemented, I see that they are, but I still do not have network access. I cannot ping anything, apt-get does not work, etc., etc...

Emerson · 04-25-2016, 03:32 PM

For ping by hostname to work you need to set up at least one DNS.

Code:

echo 'nameserver 8.8.8.8' > /etc/resolv.conf

GT-Force · 04-25-2016, 04:03 PM

I came across these posts:

http://ubuntuforums.org/showthread.php?t=819551

https://bugs.launchpad.net/ubuntu/+s...us/+bug/811441

Do you think this may be related? If so, can you explain what the last post means in the first link, and how to do it?

Thanks.

GT-Force · 04-25-2016, 04:39 PM

Quote:

Originally Posted by Emerson

For ping by hostname to work you need to set up at least one DNS.

Code:

echo 'nameserver 8.8.8.8' > /etc/resolv.conf

This is not a DNS issue, as it says "Destination host unreachable" even if I ping by using an IP address.

Emerson · 04-25-2016, 04:41 PM

Try it, remove the stale pid file and try restarting dbus, if it starts everything else that depends on it will work, too.

Emerson · 04-25-2016, 04:42 PM

Quote:

Originally Posted by GT-Force

This is not a DNS issue, as it says "Destination host unreachable" even if I ping by using an IP address.

That means your route is incorrect, working example below:

Code:

~ $ route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         turtle          0.0.0.0         UG    2      0        0 eth0
loopback        0.0.0.0         255.0.0.0       U     0      0        0 lo
192.168.2.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0

GT-Force · 04-25-2016, 04:43 PM

Quote:

Originally Posted by Emerson

Try it, remove the stale pid file and try restarting dbus, if it starts everything else that depends on it will work, too.

"remove the stale pid file and try restarting dbus" unfortunately does not mean anything to me.

If you could include the terminal commands, that would be a great help to try things quickly and report back.

Thanks.

Emerson · 04-25-2016, 04:45 PM

This tells you where the pid file is, run rm command on pid file.
https://bugs.launchpad.net/ubuntu/+s...441/comments/2

GT-Force · 04-25-2016, 05:03 PM

Quote:

Originally Posted by Emerson

This tells you where the pid file is, run rm command on pid file.
https://bugs.launchpad.net/ubuntu/+s...441/comments/2

Did this. No changes in behavior.

Actually, it said that dbus is a folder and it cannot remove it, so I had to use rmdir instead of rm

Emerson · 04-25-2016, 05:08 PM

There seems to be discrepancy in that post, the actual pid file is /var/run/dbus.pid, remove it and restart dbus.

GT-Force · 04-25-2016, 05:08 PM

Below is what I was referring to, when I wrote "can you explain what the last post means in the first link, and how to do it":

"For some reason (probably related to the unchecking of dbus in the Services app), in /etc/rc2.d the startup script for dbus was S50dbus while hal was S24hal. I didn't know run level 2 was used but just trying anything I mv'ed S50dbus to S12dbus and all works fine again."

GT-Force · 04-25-2016, 05:09 PM

Quote:

Originally Posted by Emerson

Code:

~ $ ls -l /var/run/dbus
total 0
srwxrwxrwx 1 root root 0 Apr 18 17:41 system_bus_socket

/var/run/dbus is the directory, system_bus_socket is the pid file.

Did you restart dbus after you removed the pid file?

I did not have a system_bus_socket file under the dbus folder. The folder was there, but it was empty.

I did restart it.